Re: [c-nsp] [j-nsp] Stange issue on 100 Gbs interconnection Juniper - Cisco

[Havard Eidnes via cisco-nsp]

> DC technicians states cable are the same in both DCs and
> direct, no patch panel

Things I would look at:

 * Has all the connectors been verified clean via microscope?

 * Optical levels relative to threshold values (may relate to the
   first).

 * Any end seeing any input errors?  (May relate to the above
   two.)  On the Juniper you can see some of this via PCS
   ("Physical Coding Sublayer") unexpected events independently
   of whether you have payload traffic, not sure you can do the
   same on the Nexus boxes.

Regards,

- Håvard
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[c-nsp] RPL -- testing unicast/multicast BGP routes?

[Havard Eidnes via cisco-nsp]

--- Begin Message ---
Hi,

I've tried googling and came up empty, so I turn here...

As you may know, in IOS-XR one can do

   show bgp ipv4 multicast
and
   show bgp ipv4 unicast

to see the routes from the different ... sub-address families(?)

However, I have been unable to find a test in RPL which is able
to distinguish between the two.  Is it simply missing from the
language?  It seems like a rather obvious oversight in the RPL
design...  (However, it's way too late to fix that now to resolve
my immediate issue on any reasonable time scale.)

I am guessing that my second best bet is to implement community
tagging on all relevant inbound edges to make it possible to
distinguish between the two in RPL.

Comments?

Regards,

- Håvard
--- End Message ---
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/