With XR 4.2.0 the ASR9000 is releasing a new line of hardware models. This amongst others is the RSP440, the next generation RSP with faster switch fabric along with Typhoon based Linecards, the next generation network processor.
In the TAR file from CCO there are files like asr9k-mini-p.pie or asr9k-mini-px.pie. The reason why there are 2 sets of files is because there are 2 hardware versions of the RSP.
The RSP2, the "old" RSP is based on a dual core PPC. The new RSP440 has an 4 core Intel processor.
Because PPC and INTEL handle endians differently, there are compiler differences to generate sw for the different PPC and the INTEL.
Features and functionality are the same between RSP2 and RSP3. Scale might be different.
The trident based linecards (2T20G, 40GE, 4T, 8T, 8T/4) as well as the new typhoon linecards (24x10GE, MOD80, MOD160, 100G) are all
What that means is that Only when you have an RSP3 in your system, you need to load the PX images.
When you have an RSP2 based system you need to load the P images.
The precense of a Trident or Typhoon linecard doesn't matter. So an RSP2 with a typhoon LC, still runs the -p images.
When you are upgrading from RSP to RSP440, this can't be done "hot". RSP2 and RSP440 can't coexist in the same system.
This simple table helps in the selection process, note that this applies for XR 4.2.0 and later.
RP CPU type
Trident Based (PPC)
Typhoon Based (PPC)
Tomahawk Based (x86)
If you are considering downgrading RSP2 or ASR9001 from 513 to 43 or earlier, take note of the following stipulation:
Hi, We have a POP with ASR 1002 for BNG and CGNAT.The problem is with the configuration of cgnat, we can't access the cpe from outside of asr by interface of uplink.We tried to accept by using an access list, but without success. Follow the conf...
Hi,Previous we were using Cisco 7606 as BRAS and the issue was Router keeps on rebooted automatically.OLD Details about Cisco 7606Router 7606 #show versionCisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVENTERPRISEK9-M), Version 15.2(2)S...
I have successfully registered my SIP endpoints (which we have developed) with Broadsoft sandbox environment. I can make basic calls without problems. When I try to conduct feature tests like Call Waiting (CW), Call Hold (CH), and Call Transfer (CT)...
I am trying to find if there is any Pros or Cons in deploying MPLS with separate customer AS for each site as opposed to one AS. The end goal is to be able to inject default routes from two DCs and be able to make a subset of sites follow one default rout...