Welcome to the Cisco Networking Professionals Ask the Expert conversation. This is an opportunity to discuss Cisco IOS Software Release 12.3 with Cisco expert Errol Hayward. Errol is a Product manager of the Internet Technologies Division (ITD). He is responsible for setting the marketing strategy, developing the marketing plan, creating the messaging and positioning, and working with cross-functional / cross-BU teams to implement this plan for software releases. Feel free to post any questions relating to Cisco IOS Software Release 12.3. Remember to use the rating system to let Errol know if youve received an adequate response.
Errol might not be able to answer each question due to the volume expected during this event. Our moderators will post many of the unanswered questions in other discussion forums shortly after the event. This event lasts through August 1. Visit this forum often to view responses to your questions and the questions of other community members.
We had understood that based on the supported features and hardware I found in 12.3-1a that we would be able to upgrade 3620 routers with NM-4T1-IMA modules to this version to deal with the IPv4 bug recently announced.
However we find that the module does not function under this version (we have been running c3620-is-mz.122-12a successfully in these routers). While the routers have the additional RAM needed to run the code, and the code does load, (all other interfaces come up) the NM-4T1-IMA does not function at all in the new version.
So when will you have this fixed?
This question is outside my area of expertise. But I sent it over to the group who can address this issue. They requested the following information: Please provide a show tech, or at minimum show ver and show diag as well as console boot up log for the 3620 on the 12.3 version of code. If there is a TAC case number, please send as well.
I have the sh tech from the 12.2-12a load (where the atm circuits work) and will load the 12.3-1a code during our maintenance window tonight and run it again. Since these are long text files how do you want me to post them?
I have not opened a TAC case - the routers run fine with 12.2-12a. We have the work around in place for the IPv4 bug.
This shows up in the controllers on the down IMA link:
Tx link id is 0, Tx link state is unusableNoGivenReason
Rx link id is 0, Rx link state is usable
Rx link failure status is noFailure,
This may or may not be an IOS problem; more information is required, particularly if you want root cause. Some similar issues have been resolved by resetting equipment at the remote end. Please have a TAC case opened so we can track and expedite this issue more efficiently, and provide me with the case number so that we can follow through.
Well, OK I will do that...
...but with all due deference, if it is was hardware, it wouldn't come right back up as soon as I reload 12.2-12a. The problems follows the IOS exactly and specifically.
I called Qwest (the remote ATM link) and asked them to bounce the IMA link once I was rebooted. That did it. So your observation was right on target.
Qwest is running Cisco equipment as well on their side.
So, IMHO, Cisco has a bug. It should not require a reboot of the remote end just because I change IOS versions on my end.
You are correct. The best way to get this issue resolved is to open a TAC case so it can be tracked and expedited appropriately. Let me know the case number once assigned so I can follow the progress.
In cisco Bug toolkit, I found the following information for the bug id CSCea26995: First Fixed-in Version:12.3(1), 12.3(1.3), 12.3(1.2)T. But I can't find 12.3(1.2)T from CCO software centre. May I know what's the difference betwwen12.3(1) and 12.3(1.2)T? We are running on 18.104.22.168.T. Will it be better for us to stay on T train?
Thanks and Regards
Difference between 12.3(1) and 12.3(1.2)T?
First let me explain the difference and the relationship between Major Release 12.3(1) and New Technology Release 12.3(x)T. (Ill explain what 12.3(1.2)T is in the next section.) Major release 12.3 is consolidation of earlier Technology release 12.2T, software fixes, with an added level of integration testing and more validation at customer sites. It's feature content is fixed at FCS or First Commercial Shipment. Maintenance updates are provided typically every 8-10 weeks until it reaches General Deployment Status.
Technology Release 12.3T is kicked off at the same time as the Major Release 12.3. It contains the same functionality as the Major Release, plus it adds new functionality in each update. Bug fixes in release 12.3 are also applied to 12.3T.
I have a diagram that shows this. Send me your email address and I will forward the slide.
Release 12.3(1.2)T is an interim release. This is a working software build that contains recent software fixes but is not fully tested. Interim releases are generally not available to customers. Only in extreme cases or emergencies will an interim build be made available to customers. The first fully tested 12.3T release available to customers is 12.3(2)T. It will be available in the late-July / early-August time frame.
Running 12.2(16.5)T better to stay on T train?
As far as whether you should stay on a T train or a move to a Major release train this is not a question that neither you nor I can answer additional information. My recommendation is to start by talking to your Cisco SE and Account manager, Cisco consulting team, and/or Cisco TAC about this. Make sure they understand your present and future network requirements and goals. Work with them to determine the best course of action. For example, if you are satisfied with the features/functionality presently in your network and you dont foresee upgrading to new features anytime in the near future, you may wish to test and deploy Major Release 12.3. On the other hand if you plan to add some of the new productivity increasing features in 12.3T, then you would likely want to test and deploy a 12.3T train. Not knowing the specifics of your network and your future network plans, I cannot accurately recommend a release train.
Also consult the available Cisco tools like:
IOS Upgrade Planner - www.cisco.com/pcgi-bin/Software/Iosplanner/Planner-tool/iosplanner.cgi?
Feature Navigator - www.cisco.com/go/fn
Cisco IOS Software Selector - www.cisco.com/go/ciss
MIB Locater - www.cisco.com/go/mibs
TAC Tools and Utilities - www.cisco.com/kobayashi/support/tac/tools.shtml
These tools along with your Cisco consultants can definitely steer you in the right direction.
My email address is email@example.com, approciate that you can send me the diagram. Because we found some bugs in our previous IOS and those bugs are solved finally in 12.2(16)T. Can I confirm with you that all bugs solved in 12.2(16)T are solved in 12.3 main line? And when will the General Deployment will be available? Will it be better for us to wait for General Deployment available since it's more stable and we are not hurry in upgrading to 12.3?
Thanks and Regards
Hi Deng Qi,
I sent the diagram to your personal email. Let me know if you have additional questions.
I need some clarification...you said that you are running 12.2(16)T in your network. But the last 12.2T release was 12.2(15)T, 12.2(16)T does not exist. Please clarify, could you be running 12.2(16) mainline instead of "T"?
So, to answer your question, yes, all the software fixes that are resolved in 12.2(x)T are also resolved in Release 12.3(1).
When you asked about General Deployment (GD) above, if you are running 12.2T, I assume you mean 12.3GD. If you are running 12.2 mainline, then 12.2GD is applicable. So I will address both.
12.2GD is planned for the August/September 2003 timeframe.
The 12.3GD posting is far off. As a reference, Release 12.2 FCS was in May 2001, and GD is planned for ~27 months later. Although, it may not take 24+ months to reach 12.3GD, it is not planned for the near future.
With regards to waiting for GD, if you are running 12.2(16) maniline, the 12.2GD release is a viable option. If you are running 12.2T, to match the functionality in 12.2T you will have to wait for 12.3GD.
Again, I recommend that you also talk with your Cisco Account team and/or Consulting staff.
I was wondering if there is a command in IOS 12.3 that is comparable to the PIX OS's OBJECT-GROUP command. If not is there any consideration for adding this functinality as it does help in access-list management when the denied list gets extremely long...