Console access to the router and Router must be running release 5.3.2 or (5.3.1 with engineering SMU)
System must not have 800G (tomahawk) line cards, (see caveat (a) in list below)
RSP1 is the active RSP440 (see caveat(b) in list below)
This process only works when upgrading RSP-440-TR/SE to RSP-880. This process does NOT apply to A9K-RSP-4G or A9K-RSP-8G(AKA RSP2), an upgrade from RSP2 to RSP880 is not graceful.
Before the upgrade process starts, and prior to removing any RSP from the chassis, make sure that “show redundancy” shows NSR and standby card is ready.
Make sure any none 5.3.x software is removed from the system (ie install remove *4.3.4*)
Enable console logging on the router and on the terminal application (optional)
The system must NOT have Tomahawk (400G or 800G) Line cards in the chassis prior to attempting this as the EOBC link between Tomahawk and newly inserted RSP880 will be down which will interfere with the failover from RSP440 to RSP880. If there are Tomahawk cards in the chassis, they need to be removed or powered down for the upgrade to be successful. ‘admin-config #hw-module power disable location 0/1/cpu0’
While doing RSP440 to RSP880 upgrade, Active RSP440 must be in slot 1, else the user will observe online diag fabric punt failure to LC on the newly standby RSP880.
Remove Trident Linecards from the system as they are incompatible with the RSP880.
3) Upgrade process:
RSP1 is the active RSP440 running 5.3.2 or 5.3.1 + SMU
If RSP0 slot is active and RSP1 is standby then first OIR/Remove RSP0 slot card (or do redundancy switchover from RSP0 to RSP1) to make RSP1 as active and then insert RSP880 in slot0.
Issue show redundancy and make sure NSR and Standby card is ready
Today I was studying the seamless MPLS approach from this page:https://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/mpls/116127-configure-technology-00.html But there is a point where I really struggle.See the picture below.H...
Quick Question please, In MPLS network with VRFs, there are two labels on the packet, one is the MP-BGP label and the other is LDP label. Does the MP-BGP label have EXP bit? Or it's only on the LDP label? Thank you
Having an issue where the amount of radius sessions are not in sync with the BNG sessions. We use IPoE for authentication, so any COAs that need to sent from radius to the bng need to be known by radius and that is where the issue lies. ...
I'm reviewing our hardware for replacement planning, and have most of the EoS dates, except for the following:ASR-9001A9K-MPA-20X1GEA9K-MPA-4X10GEA9K-MPA-8X10GE Any info or references are appreciated. Thanks,Phil