To allow for a new instance of the XR operating system, running the target XR release, to be created while the base XR release is still active, a second XR VM has to be spawned on all line cards. While on 32-bit IOS XR the total physical RAM is available to LC CPU, on 64-bit IOS XR the total physical RAM must be distributed between 4 entities:
XR VM v2
All flavours of Tomahawk line cards have 24GB physical RAM available to LC CPU. On 64-bit IOS XR, the XR VM has access to 10GB.
As 32-bit IOS XR runs directly on hardware, you can see the size of physical RAM by running the "show memory summary" command:
RP/0/RSP1/CPU0:ariad#sh platform | i "Node|100GE-TR" Node Type State Config State 0/3/CPU0 A9K-8X100GE-TR IOS XR RUN PWR,NSHUT,MON
In some deployment scenarios XR VM on LC CPU may require more RAM, e.g.: combination of full Internet table and large netflow cache. If your topology doesn't support ISSU or if you simply need more RAM and do not care about ISSU, you can double the amount of RAM available to XR VM by disabling ISSU.
ISSU is disabled globally, affecting all line cards. You cannot selectively enable/disable ISSU on individual line cards. Command for disabling ISSU is available in the Admin VM Configuration mode:
RP/0/RSP0/CPU0:ios#admin sysadmin-vm:0_RSP0# config sysadmin-vm:0_RSP0(config)# sdr default-sdr issu disable sysadmin-vm:0_RSP0(config)# commit The following warnings were generated: '': SDR issu-flag is being changed. Affected SDR might reload. Proceed? [yes,no] yes Commit complete. sysadmin-vm:0_RSP0(config)#
At this point all LCs are reloaded. After the XR VM on line cards boots up, it you should see almost a double amount of RAM available.
CARE must be taken when you want to re-enable ISSU
If you simply configure 'no sdr default-sdr' followed by a commit, then all XR VMs will disappear from every node except the Active RSP. Recovery is laborious and time consuming.
If there is a mix of Lightspeed and Tomahawk line card in the chassis, you need a SMU for CSCvk63470.
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...
So I have attempted the below config: l2vpn
backup disable never
xconnect group Xconns
In one of the discuss, it was initiated to us that there is a specific DB size for example:1 GB and breaching of which will led to crash of Iedge process.I want to replicate the scenario by creating load of user by tool in the lab and track the CDM db uti...
Some 15 years ago we had implemented a PWLAN service by deploying SSG on IOS and Cisco SESM (Subscriber Edge Services Manager) as the web interface (i.e. captive portal). Fast forward, SESM becomes EOL, gets replaced by Broadhop SME. Some years later...