Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Retired after 40+ years experience in IT / Computer Networking, including:
- 24 years as Cisco SE
- 19 years Enterprise IT, as both customer and Cisco SE
- 22 years SP experience, as both customer and Cisco SE
CCIExpired #5286
https://www.linkedin.com/in/jimberg/
Retired after 40+ years experience in IT / Computer Networking, including:
- 24 years as Cisco SE
- 19 years Enterprise IT, as both customer and Cisco SE
- 22 years SP experience, as both customer and Cisco SE
CCIExpired #5286
https://www.linkedin.com/in/jimberg/ ...
Without having access to the remote link-partner, we can only speculate as to its state (governed by 802.3 Clause 37) and the root cause when the link was not working. My speculation: since the Nexus and NCS have different h/w and NOS, they were beha...
Which device had this config:
interface Ethernet1/11switchport mode dot1q-tunnelswitchport access vlan 822spanning-tree port type edgespanning-tree bpdufilter enablespeed 1000no negotiate auto
Was this the old device that the NCS5500 replaced, or the...
I have not looked at the latest yaml yet, but initial observations on the first version:
ping from A1 to IPv4 VIP (10.11.0.254) did not work until I added "vlan 11" to each of D1 and D2ping from A1 to IPv6 VIP (auto-config'ed as FE80::5:73FF:FEA0:74 ...
Your observations are consistent with microbursts. If the remote peer will not shape, then increasing the burst size [B(c)] is a way to mitigate against ingress discards. Another option might be to use a 2- or 3-color policer to allow bursts up to a ...
In the context of RSVP-TE, LSP paths are indeed "tunnels", as it is even in the name of RFC 3209 "RSVP-TE: Extensions to RSVP for LSP Tunnels". The bold-face type in the RFC's abstract below is my own emphasis:
Abstract
This document describes the us...