 |
 |
Thanks, I will try to turn one of the two route-reflector sessions up this morning. Frank -----Original Message----- From: MICE Discuss <[log in to unmask]> On Behalf Of Doug McIntyre Sent: Sunday, September 08, 2019 11:32 PM To: [log in to unmask] Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? Sure, I have commented out AS53347 for you now. Both IPv4 and IPv6 sessions. On Mon, Sep 09, 2019 at 02:15:18AM +0000, Frank Bulk wrote: >Doug, > >Thanks. We have been transitioning from AS53347 to AS18883 .... so if you can remove the AS55347 configuration on MICE's RR's, that would be great. > >Frank > >-----Original Message----- >From: MICE Discuss <[log in to unmask]> On Behalf Of Doug McIntyre >Sent: Saturday, September 7, 2019 4:15 PM >To: [log in to unmask] >Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? > >On Fri, Sep 06, 2019 at 11:51:41PM +0000, Frank Bulk wrote: >>For some reason at 5:38 pm we (AS18883, FiberNet) lost IPv4 and IPv6 peering with both of MICE RR's and Hurricane Electric and it's been unstable since then. >> >>All our other peers with MICE are fine. >> >>I didn't change any configuration, even though the "bad AS number" note in some of the error messages would suggest that. > > >We've been getting a lot of these.. > >Sep 3 18:02:14 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:18 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:23 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:28 micemn-01 bird6: NASN_18883: Received: Connection collision resolution > > >And these > >2019-09-07 16:08:15NASN_53347: Error: Bad peer AS: 18883 > >As well as I suppose the expected > >2019-09-07 16:08:16 NASN_18883: Received: Administrative shutdown >2019-09-07 16:08:20 NASN_18883: Received: Administrative shutdown >2019-09-07 16:08:24 NASN_18883: Received: Administrative shutdown > >If you have 18883 link shutdown. > >But with the first and second errors, I see you have two AS's, and two >IPs coming across Eth10 on the switch. The middle error message seems >to imply that the configuration we have setup for AS 53347 on >206.108.255.67 is receiving a peer attempt for 18883 which is >configured to talk on 206.108.255.133 on our side. > >Could these two be mixed up at all? > > > > >-- >Doug McIntyre <[log in to unmask]> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades > -- Doug McIntyre <[log in to unmask]> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades