just to close this out -- we were able to get the circuit up and running -- the issue was with how the Ciena gear was configured. I've never done work on Ciena gear but it had something to do with a "GFP" setting. Whatever it was set to, they changed it and up popped the circuit and the BGP session.
I did end up using OAM LFM to help figure this out -- when they looped the local interface, LFM came up and I saw myself as a peer as expected -- when he moved the loop to the other end of the Ciena ring (at least if I was understanding correctly that's what they did), LFM did not come up. Thanks all that replied on and off list with ideas! Will > > > Date: Wed, 1 Aug 2012 09:35:21 -0400 > From: William McLendon <[email protected]> > To: [email protected] > Subject: [j-nsp] EX to Cat6500 link? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > all, > > this is an odd issue i'm having in turning up a new circuit, and hoping for > some input / ideas -- > > the link between the EX and the Cat6500 is provided by a 3rd party provider > (I think via DWDM - Sienna and Infinera gear). Both the EX and the Cat6500 > GigE interfaces are configured as routed interfaces. > > I don't know enough about how DWDM gear operates, but if I set my side to > Auto, while the far-side Cat6500 is fixed 1g/full, I successfully complete > auto negotiation and negotiate to gig/full. I don't know how transparent the > transport equipment is, if i'm negotiating with their equipment, or something > else . . . anyone have any ideas there? The provider says they're basically > just providing light signal transport, and should be auto negotiating with > the far side Cat6500 (which i'm clearly not). > > If the far side (Cat6500) sets his side also to Auto, both sides of the links > go down. If we both hard-set to gig/full, we both show link up, but no > connectivity occurs. We have checked and double checked the interface > configs and IP reachability should be occurring. At this time I still > believe its something wrong with the transport equipment / configuration of > the circuit, but I don't really have a way to prove it right now. I was > thinking about trying Ethernet OAM LFM, and if that comes up then we at least > know L2 is working, and that we've clearly overlooked something on the IP > side; and if it does not come up, then to me that points to the transport > provider (or some very odd software bug somewhere). > > Does anyone have some recommendations on troubleshooting this? I'm at my > wits end trying to bring this circuit online. > > Thanks, > > Will > > > ------------------------------ > > _______________________________________________ > juniper-nsp mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > End of juniper-nsp Digest, Vol 117, Issue 2 > ******************************************* _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
