I've searched the forums and docs and I find some different answers so I'm looking to try and confirm what I'm seeing.
I'm looking to use mgmt 0/RSP0/CPU0/0 for OOB mgt. and running 5.3.3.
My control-plane config leverages 'interface all' for config simplicity.
However this seems to catch the mgmt interface as well.
I could create/leverage a group config but the # of interfaces and needed addresses create a much larger config when I consider
Gig*, TenGig*, Hundred*, Loop* interfaces.
a) am I correct that 'interface all' is capturing my mgmt interface?
b) if so, a feature request here to change it so that any specific interface config'd as OOB would override that behavior. This would allow for a simpler, more maintainable config. Would there be any reason not to take this approach?
When my mgmt interface is up, it's prefix is added to the global table.
I see docs that differ on whether the vrf statement is needed or not.
I'd thought by default, that mgmt interfaces were not involved with any forwarding decisions.
With or without it, when up, my mgmt interface prefix ends up in the global table - is this behavior I'm seeing related to the inband 'interface all' issue above?
In scaled EVPN deployments it can be wise to name ESI that way to represent the site/physical port/etc it is attached to. Thus on some remote location you can easily verify where particular route/MAC is coming from. Similar to phone numbers, where...
Want to enable Feature EPFT with “routing-protocols-enable”. However ,it is throwing an error and ask to configure the following command: “non-subscriber-interfaces mac” which once enabled drops the traffic without any penalty.
XR-vm - CLI's
look for any process crash, review time stamp[if it is too old, then no immediate action needed]
verify if standby state is Ready and NSR-Ready
show proc cpu | exclude " 0%"
It's been a long standing ask for XR to support conditional route advertisements in BGP.
The expected option of using the
option in RPL currently can only be used at the default-inf...
On IOS-XR, Quality of Service has an extension to WRED (Weighted Random Early Detection) called Explicit Congestion Notification (ECN). ECN will mark packets instead of dropping them when the average queue length exceeds a specific threshold value. When c...