For us at Cisco it is very important to deliver the new features and hardware that your network requires, while at the same time maintain the high software quality. We are continuously investing efforts to improve the quality of our software and hardware. We are adjusting our culture, processes and practices to achieve that goal.
One of the key concepts in the software quality plan is the Extended Maintenance Release (EMR) introduced in IOS XR for the first time with the release 4.3.4.
Extended Maintenance Release (EMR) criteria:
No new software features
No new HW support
Incoming bug rate to drop by at least 90% from peak rate for that release.
Zero critical bugs.
By choosing the EMR for deployment, you are making the optimal choice. We will be happy to work with you on EMR early field trials or any other way to help synchronise your upgrade/migration plan with the EMR release schedule.
By selecting the EMR you are not only making sure that you are getting the best quality release, you are also selecting a release with the highest deployment rate.
Manual SMU and SP install is a thing of the past since the introduction of the CSM Server. CSM Server is a web based server side automation and orchestration framework designed to ease the SW maintenance for all IOS XR platforms.
To get the glimpse of the CSM Server we highly recommend to watch the _video_. CSM Server distribution comes with a documentation included, but you can also read more about it on _supportforums_.
Another benefit of deploying EMR is that more software patches are available compared to other releases. Number of software patches (SMUs) available per release is directly proportional to the number of our customers running the release. Also, on EMR we try to provide, when technically feasible, SMUs for issues affecting the usability of IOS XR, not only for critical issues directly impacting the services. Service Packs (SPs) are also built more frequently compared to non-EMR releases.
Service Packs on are built on EMR every 8 weeks. On non-EMR builds are on-demand, but never more frequent than on EMR.
64-bit vs 32-bit IOS XR
The 64-bit flavour of IOS XR is available for ASR9000 starting from XR release 6.1.2. There is no different release number for the 32-bit and 64-bit IOS XR. The 64-bit software packages are designated by the 'x64' in the package name (e.g. ASR9K-x64-iosxr-px-6.1.2.tar).
CSM Server contains a module that seamlessly performs the migration from 32-bit XR to 64-bit XR. We highly recommend you to watch this short demo video.
New IOS XR platforms NCS500, NCS5000 and NCS5500 only support the 64-bit flavour.
Suggestions For Year 2019
For year 2019 our aim is to continue cutting down on the time between the first feature release (e.g. 6.2.1) and its corresponding EMR. At the same time, we want the EMR to meet our internal quality criteria.
Suggested releases for validation and deployment in calendar year 2019 are:
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...
I work in a large enterprise. We run our own MPLS environment for macrosegmentation. See attached diagram.We are converting from EIGRP to OSPFv2 at our remote sites. Remote sites are running their own single-area OSPF instances (no area ...
Today we have a fiber ring that houses our Layer 2 traffic with a single egress to the outside world. I'm trying to add an additional that will be primary for the closest nodes off the ring and redundant for everyone else. The single egress is on an ASR90...