Here’s a question that I’ve been asked over and over again.
How can I upgrade the software of a Nortel ERS 8600 Switch?
It’s actually very easy and only takes a few minutes (along with a reboot). If you have dual CPUs (8690SF, 8691SF, 8692SF) your going to need to upgrade both CPUs. If your running in a HA (High Availability) configuration you probably shouldn’t be reading this. I’ll assume that anyone with dual CPUs is running them in a standby configuration. I generally like to upgrade the standby CPU first and then upgrade the primary CPU, the switch will fail over to the standby CPU once the primary CPU starts to reboot.
You’ll need a TFTP server to host the software files. I generally use the TFTP server that comes with Linux (CentOS), however, you can use TFTPD32 by Philippe Jounin on Windows XP/2003. Just drop the TFTPD32 files in the same directory with the Nortel ERS 8600 software release and run the executable.
For this example let’s assume that the primary (active) CPU is in slot 5 and the standby CPU is in slot 6. Once you have the TFTP server setup we can telnet into the switch. If you don’t have telnet enabled in the boot.cfg file you’ll need to console up to the switch. You may also need to clean up the /flash/ filesystem depending on which switch fabric you have installed in the chassis. I believe the 8692SF comes with 64Mb of flash memory and a 64Mb PCMCIA card.
Trying 10.1.1.10…
Connected to 10.1.1.10 (10.1.1.10).
Escape character is ‘^]’.**************************************************
* Copyright (c) 2007 Nortel, Inc. *
* All Rights Reserved *
* Ethernet Routing Switch 8010 *
* Software Release 4.1.5.4 *
**************************************************Login: rwa
Password: ***ERS-8610:5#
If your not sure which files you need you should consult the Nortel documentation. You will definitely need the boot (p80b4154.img) and agent (p80a5145.img) files at a minimum. I have daughter processors (SuperMezz cards) in my 8692SFs so I also need that software (p80m4154.img). I also have R cards in my chassis so I need the image for those (p80j4154.dld). I don’t have any ATM cards so I don’t have that software included below. The TFTP server I’m using has the IP address of 10.101.20.1.
Copy software to primary CPU
ERS-8610:5# copy 10.101.20.1:p80a4154.img /flash/p80a4154.img
ERS-8610:5# copy 10.101.20.1:p80b4154.img /flash/p80b4154.img
ERS-8610:5# copy 10.101.20.1:p80c4154.img /flash/p80c4154.img
ERS-8610:5# copy 10.101.20.1:p80c4154.aes /flash/p80c4154.aes
ERS-8610:5# copy 10.101.20.1:p80j4154.dld /flash/p80j4154.dld
ERS-8610:5# copy 10.101.20.1:p80m4154.img /flash/p80m4154.img
We make the configuration changes to the boot.cfg file;
ERS-8610:5# config bootconfig choice primary image-file “/flash/p80a4154.img”
ERS-8610:5# config bootconfig choice secondary image-file “/flash/p80a4150.img”
ERS-8610:5# save config
Save config to file /flash/config.cfg successful.
Save to standby file /flash/config.cfg successful.
ERS-8610:5# save bootconfig
Save bootconfig to file /flash/boot.cfg successful.
Save to standby file /flash/boot.cfg successful.
Copy software to standby CPU and upgrade
With the software now on the primary CPU in the /flash directory we can transfer the software to the standby CPU and upgrade that component. We’ll telnet from the primary CPU to the standby CPU so we can issue our commands. Alternately we could also console up to the standby CPU.
ERS-8610:5# peer telnet
Trying 127.0.0.6 …
Connected to 127.0.0.6
Escape character is ‘^]’
**************************************************
* Copyright (c) 2007 Nortel, Inc. *
* All Rights Reserved *
* Ethernet Routing Switch 8010 *
* Software Release 4.1.5.4 * **************************************************
Login: rwa
Password: ***
@ERS-8610:6#
Now that we’re connected to the standby CPU let’s copy the files from the primary CPU. It’s important to note tftpd must be enabled on the primary CPU in the boot.cfg file; “flags tftpd true”.
@ERS-8610:6# copy 127.0.0.5:p80a4154.img /flash/p80a4154.img
@ERS-8610:6# copy 127.0.0.5:p80b4154.img /flash/p80b4154.img
@ERS-8610:6# copy 127.0.0.5:p80c4154.img /flash/p80c4154.img
@ERS-8610:6# copy 127.0.0.5:p80c4154.aes /flash/p80c4154.aes
@ERS-8610:6# copy 127.0.0.5:p80j4154.dld /flash/p80j4154.dld
@ERS-8610:6# copy 127.0.0.5:p80m4154.img /flash/p80m4154.img
Now that we have the files let’s perform the actual upgrade and reset the CPU.
@ERS-8610:6# boot /flash/p80b4154.img
Are you sure you want to re-boot the switch (y/n) ? y
@ERS-8610:6#
You should wait until the standby CPU upgraded the boot code and then loads the new agent code before doing anything with the primary CPU. It’s also a great idea to confirm that the standby is up and operational before you do anything with the primary CPU.
Now all you need to-do is upgrade the primary CPU
ERS-8610:5# boot /flash/p80b4154.img
Are you sure you want to re-boot the switch (y/n) ? y
ERS-8610:5#
The switch will boot the boot image and upgrade the boot PROM afterwhich it will reboot again and load the new agent code we specified in the boot.cfg file. If you have a standby CPU the standby CPU will become the active CPU. If you don’t have a standby CPU in the switch you’ll just need to wait for the switch to come back online. This should only able about 3 minutes.
Cheers!
Michael McNamara says
I guess it should be noted that anyone upgrading the software on a Nortel ERS 8600 should, at a minimum, review the release notes of all prior software releases to make sure that there have been no changes that may adversely affect specific configuration.
michael gagnon says
could you create a post wrt upgrading the ERS-8300 w/ dual-CPUs?
i am still having to manually go to all of my 8300s when upgrading. the issue generally tends to be loading the p83jxxxx.dld firmware for the I/O modules that are flashed with the new code. the problem arises when one CPU is being upgraded and something happens to the boot-config where the modules aren’t flashed properly (and upon boot, keep looking for the old-code ‘j.dld’ file).
i’ve followed nortel’s install guide many times (remotely), and always end up having a problem where i have to manually console to the box.
thanks,
Michael McNamara says
Hi Michael,
It sounds as though the switch is not booting the new agent code after the boot prom upgrades. Are you changing/saving your boot configuration with the new agent software as I do in the post above? Do you have the flag “save to standby” enabled or do you need to manually sync the configuration files between the primary and standby CPUs? The only explanation I can offer is that you are still booting the old agent software which is in turn looking for the old download files. If you watch the switch boot up after you upgrade the boot proms what version of the software does it load?
Good Luck!
michael gagnon says
well, with the ERS-8300s, you have to enter in -manually- the command to point to the new I/O files, or select default.
config boot bootp image-name p83rxxxx.dld
or
config boot bootp image-name default
so i think there is an issue with this boot being copied over or not being saved properly. it’s a little tricky, but i’ll try things out again in the lab.
QAZ says
Nice post, people allways seems to be struggling reading the Nortel manual. In fact upgrading is as easy as you describe. Maybe usefull to add is that when you perform a ‘save config’ with save to standby on true, also some hidden files are copied over. Like the usm/snmp_comms/passwords/ospfkeys etc files, which are hidden as you probably know.
Something other usefull is a guide how to go through the hwDumpAll command. Became very handy since it’s from 4.1.4.0 in the target shell (as you needed priveledge passwords on earlier versions). We have seen several issues with bouncing ist and ports which had their root cause at having hardware errors.
cheers
Rick S says
After issueing the hwDumpAll command and recording the information, one ought to clear the hardware error logs. Nortel suggested doing with the hwClearAll command, but that isn’t working. Do you know the correct command to accomplish this?
Rick
Michael McNamara says
Hi Rick,
I believe you need to be in priv and shell mode to issue the hwDumpAll and hwClearAll commands. You’ll need a support ticket with Nortel to have the passwords generated.
Cheers!
Sheldon Caines says
I am planning to upgrade my 8600 from 3.5 to 4.x and would like to know if there are any issues I may encounter in doing so. I have a document called: Nortel Ethernet Routing Switch 8600 Upgrades — Software Release 4.1.x.x, but there are no mentions in it of glitches that can happen. Anyone has recommendations?
Michael McNamara says
Hi Sheldon,
I would advise that you review the release notes of all the intermediate software releases between 3.5 and 4.x just to be safe.
You will most certainly have issues with your SNMP configuration so be prepared to re-configure your SNMP strings and lock down your SNMPv3 configuration (remove the default strings and users).
I’m happy to report that 4.1.8.2 is the best software release I’ve seen from Nortel in quite some time. I have it running and multiple large and small locations with no problems whatsoever.
Good Luck!
Steve Davies says
Hi Michael ,
As a newbie to 8600’s am a bit confused by the notes before upgrade process. “If your running in a HA (High Availability) configuration you probably shouldn’t be reading this”…. Our 8600’s do run in HA mode..does this mean that the procedure would not work for HA ??? and is HA not recommended as the assumption was that everyone with dual CPU’s was operating in standby mode which i assume you to mean non- HA mode ??? Sorry for such basic questions but i am fairly new to Nortel kit but am finding your site an absolute goldmine of great information .
Cheers …Steve
Michael McNamara says
Hi Steve,
There are special procedures to follow when updating a switch that is running in HA mode. In the original post I was inferring that anyone running in an HA configuration would probably already understand the procedures and steps involved.
I don’t recall right now but it’s not as straight forward as the original post. I believe you need to disable HA, upgrade the CPUs one at a time and then enable HA mode when your all finished. There are several documents available on Nortel’s website that should be helpful. I’ll see if I can dig any of those documents up for you.
Cheers!
Stuart Taylor says
I upgraded 15 ERS8600 recently. All but one were running with HA enabled. When upgrading to 5.1.1.1 I did so with HA still enabled and it worked a treat.
After installing the code and changing boot config etc.., I booted the standby cpu of the new code first and then whilst it was doing this I did the same on the primary cpu (Nortel recommend booting the primary within 15 secs of the standby being booted if upgrading with HA enabled).
In all cases the standby booted up nicely, coming up as the primary and the original primary cpu did likewsise coming up as secondary.
Within seconds I then received all the approriate HA synchronisation messages.
Doing the upgrades with HA enabled saved me a lot of time as it avoided extra reboots of the cpu cards which occur when disabling/enabling HA.
Regards
Michael McNamara says
Thanks for sharing that information Stuart!
Sergey says
Dear Michael!
I’m network administrator of the one Ukrainian institution. We are using Nortel Passport-8006 ERS and mostly equipment produced by Nortel. After the Nortel’s became bunkrupped, our regional dealer can’t support us anymore and there fore we are havent access to the new firmware.
Moreover we need to upgrade our ERS8600 for installation of second CPU unit.
As far as i know, the second unit won’t work with old firmware.
So, can you help us and share the stable new Software release for the Nortel ERS 8600?
Looking forward to hear you soon.
Best regards
#less /tftpboot/10-10-250-1.cfg
#
# FRI FEB 26 11:22:21 2010 UTC
# box type : Passport-8006
# software version : 3.5.1.0
# monitor version : 3.5.1.0/000
#
#
# Asic Info :
# SlotNum|Name |CardType |MdaType |Parts Description
#
# Slot 1 8624FXE 0x20310118 0x00000000 IOM: PLRO=3 BFM: OP=3 TMUX=2 RARU=4 CPLD=9
# Slot 2 8608GTE 0x20220108 0x00000000 IOM: GMAC=5 BFM: OP=3 TMUX=2 RARU=4 CPLD=9
# Slot 3 8616SXE 0x20320110 0x00000000 BFM: OP=3 TMUX=2 RARU=4 CPLD=9
# Slot 4 8608SXE 0x20320108 0x00000000 IOM: GMAC=5 BFM: OP=3 TMUX=2 RARU=4 CPLD=5
# Slot 5 — 0x00000001 0x00000000
# Slot 6 8691SF 0x200e0100 0x00000000 CPU: CPLD=19 SFM: OP=3 TMUX=2 SWIP=3 FAD=1 CF=16
Michael McNamara says
Hi Sergey,
You can purchase support/maintenance contracts for data products directly from Nortel, you don’t need a reseller. I would suggest you try contacting Nortel/Avaya. Once you have a maintenance/support contract you are entitled to all software upgrades.
As you mentioned 3.5.1.0 software is very very old. With the hardware you have I believe you can run 4.1.8.3 without issue. I would suggest you upgrade to 4.1.8.3 as that’s the most stable release in the 4.x software development branch.
You may want to upgrade your 8691SF to an 8692SF. Is there any reason you believe you need a second CPU/SF?
Good Luck!
Rick says
Per Sergey’s post, I believe his “E” blades are not compatible with the new Nortel ERS version 5 code. Plus Nortel indicated that 8691SF’s are not supported in their new code–8692SF’s are required moving forward.
I was in his same place–8691SF’s and all “E” blades in our Core and Distribution closets, as well as in the Data Centers. Our Nortel SE told us it was time for the forklift upgrade to 92’s and R-modules, due to the age of our existing hardware.
Unfortunately for Nortel, we’d already had two years of FDB / MLT / SMLT problems in our fully meshed core. That meant we were primed for a new solution.
Nortel tried hard to help identify and fix our problems. They assigned their “Tiger Team” to review our design/implementation, but could find no faults in the configs or the layout. They admitted it was a problem both in their support of L2 spanned VLAN’s through a fully meshed square core, and to bugs in the 8600 4.7x code that was causing our outages.
We redesigned our layout to avoid the L2 spans through the core, but that didn’t fix the FDB problems. Nortel released version 4.1.8.3, saying it should help with our MLT/SMLT/Mesh issues, but they also told us the FDB problems wouldn’t be fixed in firmware that could run on our “E” blades and 8691SF’s. We needed to move to 92’s and R modules to use the version 5 code fixes.
Shortly after this they went into bankruptcy. We are in the middle of migrating our data center core and all distribution 8600’s to Cisco 6500’s and Nexus 7K’s. It is a big price to pay, but Cisco guaranteed the stability problems would disappear, and we’d have had to replace all our Nortel legacy hardware anyway to use the new code.
I’ve kept up on the Release Notes for version 5, and been disappointed to see the FDB issues are still not fixed, even though early 5.x releases claimed to have the problem resolved.
Nortel says the new stable version of firmware is 7.x. And the 8692SF’s have to have the Mezzanine card, or they’re not supported. Instead, the 8695SF is the recommended blade to replace the 8691 and 8692SF’s.
Along with this, Java Device Manager is no longer supported on the new 8695SF’s running 7.x. A replacement called EDM is provided, which runs as code loaded on the switch. Before it will work, the web server flag must be enabled to manage the switch via GUI.
I LOVED managing Nortel switches with Enterprise Switch Manager and JDM. It beat any other management tool I’ve used or heard of, hands down.
But reliability and stability are king for my network–a hospital system with 7,000+ employees, spanning across multiple states. It was difficult finding experienced staff to run the Nortel gear; that shouldn’t be a problem now that we’re drinking the Cisco Kool-Aid.
Good luck, Sergey! And thanks, Michael, for this forum.
Rick
Michael McNamara says
Hi Rick,
I’m sorry to hear about all the problems that you’ve experienced. I’ve had my fair share of problems but in general I’ve found Nortel/Avaya to be very supportive (aside from needing a gentle nudge every once-n-while) and the products very effective. I’m getting ready to deploy a new data center using Cisco’s Nexus 7010, 5010 and 2148s so we might have some stories to trade soon. I’m hoping the grass is greener on the Cisco side of the street but I’ve already started to see some issues.
The E modules are not supported in 5.x but work fine. In the upcoming 7.x software release the code of the E modules has been removed so they won’t boot up at all. You also need 8692SF with SuperMezz cards and all R/RS cards to run 7.x software.
I have quite a few ERS 8600s right now and have no plan to forklift or replace them. With the 5.1.1.1 software upgrade they are running great and have plenty of capacity. I’m not sure we’ll every get to 7.x software on the majority of our ERS 8600 switches. We’ll probably look at the VSP9000 eventually.
We’ll need to get together in 6 months and trade notes… was the Cisco price worth it? I’ll try to keep an open mind but it was a big mark-up for our data center gear.
Good luck with your Cisco deployment and thanks for the comment!
Chris Taylor says
Can the image be transfered via direct connection to the CPU through the management port or it’s must be through normal switch ports?
Michael McNamara says
Hi Chris,
That’s a very good question and I’m not sure of the answer. You can of course use the PCMCIA card, just pop it in your laptop and copy of the software, then pop it back into the switch.
I’m guessing you might not be able to use the management port since it’s primarily designed to assist in out-of-band management and not transferring files via TFTP.
If you find out why not let us know?
Good Luck!
Chris Taylor says
ok, i’ll try next week. I’ve been experiencing an error using the CPU management port, but since the error detail isnt quite explanatory, i’ll use the switch ports.
By the way, does V7 support this hardware?
# box type : ERS-8010
# software version : 4.1.0.0
# monitor version : 4.1.0.0/118
#
#
# Asic Info :
# SlotNum|Name |CardType |MdaType |Parts Description
#
# Slot 1 ERS WSM 0x71320104 0x00000000 BFM: OP=3 TMUX=2 RARU=4 CPLD=5
# Slot 2 — 0x00000001 0x00000000
# Slot 3 — 0x00000001 0x00000000
# Slot 4 — 0x00000001 0x00000000
# Slot 5 8692SF 0x200e0100 0x00000000 CPU: CPLD=19 MEZZ=2 SFM: OP=3 TMUX=2 SWIP=23 FAD=16 CF=240
# Slot 6 8692SF 0x200e0100 0x00000000 CPU: CPLD=19 MEZZ=2 SFM: OP=3 TMUX=2 SWIP=23 FAD=16 CF=2
# Slot 7 — 0x00000001 0x00000000
# Slot 8 — 0x00000001 0x00000000
# Slot 9 — 0x00000001 0x00000000
# Slot 10 8648GTR 0x24220130 0x00000000 RSP=25 CLUE=0 F2I=4 F2E=3 FTMUX=17 CC=3 FOQ=267 DPC=184 BMC=776 MAC=2
Card Info :
Slot# FrontType FrontHw Oper Admin BackType BackHw
Version Status Status Version
1 ERS WSM 50 up up BFM4 50
5 CPU 51 up up FSFM 51
6 CPU 51 dormant up FSFM 51
10 48X1000BaseTX-R 50 up up DPM2 51
MezzCard Info :
Slot#5: MezzCard is notpresent Admin status: enabled Oper Status: down
Slot#6: MezzCard is notpresent Admin status: enabled Oper Status: down
Michael McNamara says
Hi Chris,
The WSM module isn’t supported and you’ll need to purchase a SuperMezz card for each 8629SF if you want to upgrade to 7.x software.
I’m sure there will be a number of customers and don’t see the need to upgrade to 7.x software. If you have all the features you need and everything is running fine then why upgrade? Nortel/Avaya will tell you (eventually) that you need to upgrade in order to maintain a support/maintenance contract, I’ll cross that bridge personally when I get to it.
Cheers!
Chris Taylor says
Damn. I can’t get rid of the WSM, i need it for load balancing tasks, so i hope they maintain V5 for some time and not leave old customers in the dust. This hardware is only 1.5 years old.
Michael McNamara says
I believe 5.1.x software will still support the WSM so that’s still an option should you need to consider upgrading.
Good Luck!
Chris Taylor says
Ok, i’ve done the upgrade in the lab and the image can only be transfered via the switchports.
the WSM is supported as it seems.
Shouldn’t we force the switchover between the last 2 steps of your guide?
@ERS-8610:6# boot /flash/p80b4154.img
Are you sure you want to re-boot the switch (y/n) ? y
@ERS-8610:6#
ERS-8610:5# config sys set action cpuswitchover
ERS-8610:5# boot /flash/p80b4154.img
Are you sure you want to re-boot the switch (y/n) ? y
ERS-8610:5#
Michael McNamara says
You can force it if you want… otherwise the standby will just pickup just as if you had forced a failover. I personally don’t bother with it and I just allow it to failover when I reset the primary CPU/SF.
If you force the failover you may need to physically cable up to the CPU/SF in order to reset it.
Good Luck!
Ray Miller says
Hi Michael
We have two passport 8600’s running in VRRP mode using ver 4.1.3 software over the last fe weeks we have experienced situations where the CPU goes to 100% and the IST link drops causing the dual connected edge switches to go into a loop. When i review the logs we are seeing reports of congestion. I have aggressively tweaked the CP limits on the box in an effort to track loops within the envrionment as well as implemented SLPP however we still experience the problem. I have just upgraded to Ver 5.1.1.1 in an effort to resolve some of these issues. My questios are as follows. 1. Have you ever experience this behaviour on 8600’s and 2. I saw a request in the startup log for a license dat file..how do i get this file ?
Thanks for the help in advance..
Michael McNamara says
Hi Ray,
I’ve seen this behavior in the past and have always tracked it down to either a loop or some mis-configuration within the network. What values are you using for cp-limit? I would use 2500 if you are continually having issues. You might also want to enable broadcast/multicast rate-limiting if your edge switches support it. Do you have unique VRRP IDs across each switch?
You need to load a license file in 5.x software to get the Advanced and Premium features enabled. Here’s a post about the Grandfather License for a legacy ERS 8600 switches (prior to the introduction of 5.x software).
You may want to post over in the discussion forums. There have already been quite a few discussions around IST/SMLT stability and best practice values for cp-limit and rate-limiting.
Chris Taylor says
Is there any reason why every 20 or so days our WSM loses connectivity with the chassis?
CPU6 [11/29/09 03:48:19] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:48:19] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:48:19] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:48:19] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:48:20] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:48:20] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:48:21] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:48:21] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:48:29] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:48:29] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:48:29] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:48:29] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:48:44] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:48:44] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:48:44] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:48:44] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:48:45] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:48:45] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:48:46] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:48:46] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:48:54] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:48:54] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:48:54] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:48:54] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:49:09] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:49:09] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:49:09] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:49:09] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:49:10] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:49:10] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:49:11] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:49:11] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:49:19] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:49:19] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:49:19] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:49:19] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:49:34] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:49:34] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:49:35] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:49:35] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:49:36] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:49:36] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:49:36] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:49:36] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:49:44] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:49:44] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:49:44] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:49:44] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:49:59] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:49:59] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:50:00] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:50:00] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:50:01] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:50:01] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:50:01] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:50:01] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:50:10] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:50:10] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:50:10] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:50:10] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:50:24] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:50:24] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:50:25] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:50:25] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:50:26] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:50:26] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:50:27] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:50:27] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:50:35] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:50:35] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:50:35] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:50:35] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:50:49] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:50:49] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:50:50] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:50:50] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:50:51] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:50:51] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:50:52] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:50:52] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:51:00] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:51:00] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:51:00] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:51:00] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:51:14] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:51:14] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:51:15] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:51:15] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:51:16] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:51:16] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:51:17] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:51:17] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:51:25] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:51:25] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:51:25] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:51:25] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:51:40] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:51:40] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:51:40] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:51:40] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:51:41] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:51:41] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:51:42] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:51:42] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:51:50] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:51:50] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:51:50] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:51:50] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:52:05] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:52:05] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:52:05] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:52:05] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:52:06] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:52:06] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:52:07] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:52:07] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:52:15] SNMP INFO Link Up(1/1)
CPU6 [11/29/09 03:52:15] SNMP INFO Link Down(1/1)
CPU6 [11/29/09 03:52:15] SNMP INFO Port 1/1 is a trunk port
CPU6 [11/29/09 03:52:15] HW WARNING portPollGbitEther: port 1/1 down, link is unstable!
CPU6 [11/29/09 03:52:15] SNMP INFO Link Up(1/2)
CPU6 [11/29/09 03:52:15] SNMP INFO Link Down(1/2)
CPU6 [11/29/09 03:52:15] SNMP INFO Port 1/2 is a trunk port
CPU6 [11/29/09 03:52:15] HW WARNING portPollGbitEther: port 1/2 down, link is unstable!
CPU6 [11/29/09 03:52:15] SNMP INFO Link Up(1/3)
CPU6 [11/29/09 03:52:15] SNMP INFO Link Down(1/3)
CPU6 [11/29/09 03:52:15] SNMP INFO Port 1/3 is a trunk port
CPU6 [11/29/09 03:52:15] HW WARNING portPollGbitEther: port 1/3 down, link is unstable!
CPU6 [11/29/09 03:52:16] SNMP INFO Link Up(1/4)
CPU6 [11/29/09 03:52:16] SNMP INFO Link Down(1/4)
CPU6 [11/29/09 03:52:16] SNMP INFO Port 1/4 is a trunk port
CPU6 [11/29/09 03:52:16] HW WARNING portPollGbitEther: port 1/4 down, link is unstable!
CPU6 [11/29/09 03:52:16] SNMP INFO Link Oscillation(1/1)
CPU6 [11/29/09 03:52:16] SNMP INFO Link Oscillation(1/2)
CPU6 [11/29/09 03:52:16] SNMP INFO Link Oscillation(1/3)
CPU6 [11/29/09 03:52:16] SNMP INFO Link Oscillation(1/4)
CPU6 [11/29/09 03:53:00] IP INFO ******************************************
CPU6 [11/29/09 03:53:00] IP INFO Warning –
CPU6 [11/29/09 03:53:00] IP INFO The WSM in slot 1 has missed 6 heartbeats,
CPU6 [11/29/09 03:53:00] IP INFO and communication may have been lost.
CPU6 [11/29/09 03:53:00] IP INFO You may need to reset the WSM in slot 1.
CPU6 [11/29/09 03:53:00] IP INFO ******************************************
Michael McNamara says
Hi Chris,
Your post really isn’t on-topic… please post future questions/problems over on the discussion forums.
You posted the log to the 8600 but you didn’t post the log for the WSM. Is the WSM rebooting itself? Are you experiencing an outage on the WSM?
I would start by examining the WSM logs.
Good Luck!
Mohamed Ghani says
I need to know can we upgrade the software image 3.7.1.x to 5.1.x in 8600 directly or do we need intermediate image
please suggest me which IOS recommended to upgrade in full mesh network with OSPF routing
Regards,
Mohamed Ghani
Michael McNamara says
Hi Mohamed,
You can upgrade straight from 3.7.x to 5.1.x without any major issues. If you are running in an IST/SMLT configuration then you’ll want to review the 4.1.8.3 release notes as there are some significant changes under the hood in that version and in later versions.
If you’re looking for a good resource I would suggest the forums; http://forums.networkinfrastructure.info/nortel-ethernet-switching/
Good Luck!
Hashim says
Hello Im New to Avaya Switches and I have few questions
1.We have 8306 Avaya Core switch with 2 CPU/SF. Is there any special configuration for the automataic failover (redundancy) or it is by default from Avaya
2. We have to configure both CPU/SF with VLANs and other stuff or onl in the Master CPU/SF.
3. If we need to configure even the standby CPU/SF. Can we transfer the Config from Master to standby?
Michael McNamara says
Hi Hashim,
I haven’t worked with the ERS 8300 series but on the ERS 8600 series multiple CPU/SF will operate in a cold standby mode (the switch will essentially reboot if there’s a failover). You can enable HA (High Availability) with a configuration change to the bootconfig. You can manually copy the configuration files between the primary and standby CPU/SF or you can enable a configuration option on the switch so it will automatically save any configuration changes to both CPU/SFs.
Good Luck!
Hashim says
I have created 7 VLANs in Core 8306 Switch and do we need to create each time the same VLAN’s in Edge 45xx Series or we can just add ports to Vlans using CLI because in JDM I fell we need to create VLANS similar to Core switch and then add ports to it.?
Hashim says
Thanks Mr.Micheal
But can I have the procedure to Transfer the Config files to standby CPU/SF. How can I test whether standby CPU/SF is working fine during Failover.
Michael McNamara says
Hi Hashim,
On the ERS 8600 you need to set the following bootconfig flag in order for the switch to automatically save the configuration file to both CPU/SFs when a “save config” is issued;
flags savetostandby true
You can also save the configuration to the standby/backup CPU/SF manually with this command;
save config standby /flash/config.cfg
You can have a look at this post for a list of default options that I use on my switches.
Good Luck!
Sid says
Hello Sir,
I have a 8310 I need upgrade the firmware. Actually I have the 4.1.2.0 version and I need upgrade from 4.1.2.0 to 4.2.3.4. I have gone through the release notes of v4.2 but could not find anything related to this.
Can I upgrade it directly to the firmware of 4.2.3.4? If not, can you please guide me through the progression steps (upgrade path)?
Michael McNamara says
Hi Sid,
You should review the release notes of all the intermediate software releases between 4.1.2.0 to 4.2.3.4 to understand all the implications and possible issues.
http://support.avaya.com/css/Products/P0832
Good Luck!
rahul says
I am getting console logs at nortel 8600 switches..could you expalain any reason for this.
JAKSNCSR002:5# show log file tail
CPU5 [02/16/12 06:26:51] SW WARNING Code=0x1ff0009 Blocked unauthorized cli access
CPU5 [02/16/12 06:25:28] SW INFO user Manager connected from 10.103.11.204 via telnet
CPU5 [02/16/12 06:06:46] SW INFO Closed telnet connection from 10.103.11.204, user Manager rcmd -2
CPU5 [02/16/12 06:02:44] HW INFO System activity performed
CPU5 [02/16/12 05:56:57] SW WARNING Code=0x1ff0009 Blocked unauthorized cli access
CPU5 [02/16/12 05:41:09] SW INFO user Manager connected from 10.103.11.204 via telnet
CPU5 [02/16/12 05:36:47] SW INFO Closed telnet connection from 10.103.11.204, user Manager rcmd -2
CPU5 [02/16/12 05:26:54] SW WARNING Code=0x1ff0009 Blocked unauthorized cli access
nicademus says
Hello Mike,
do you know what could cause this logout put
P8310_24th:5# show log file tail severity |warning|fatal
Invalid category
CPU5 [09/22/12 11:18:08] HW WARNING portPollPpe: port=3/42,link is unstable!
CPU5 [01/30/12 13:19:15] HW WARNING portPollPpe: port=2/40,link is unstable!
CPU5 [01/26/12 15:31:02] HW WARNING portPollPpe: port=2/40,link is unstable!
CPU5 [10/19/11 08:33:51] HW WARNING portPollPpe: port=9/11,link is unstable!
CPU5 [08/01/11 09:26:51] HW WARNING portPollPpe: port=9/32,link is unstable!
CPU5 [05/02/11 14:36:33] HW WARNING portPollPpe: port=3/9,link is unstable!
CPU5 [02/22/11 08:19:55] HW WARNING portPollPpe: port=9/32,link is unstable!
CPU5 [12/31/10 12:03:47] HW WARNING portPollPpe: port=2/4,link is unstable!
CPU5 [12/27/10 09:43:49] SW WARNING Code=0x1ff0009 Blocked unauthorized cli acc
ess
CPU5 [12/27/10 09:40:50] SW WARNING Code=0x1ff0009 Blocked unauthorized cli acc
ess
CPU5 [12/25/10 20:04:30] HW WARNING portPollPpe: port=9/42,link is unstable!
CPU5 [11/25/10 16:37:54] HW WARNING portPollPpe: port=7/18,link is unstable!
CPU5 [11/19/10 15:39:43] HW WARNING portPollPpe: port=9/18,link is unstable!
CPU5 [10/11/10 16:06:48] SW WARNING Code=0x1ff0009 Blocked unauthorized cli acc
ess
CPU5 [08/29/10 05:55:49] HW WARNING portPollPpe: port=9/14,link is unstable!
CPU5 [08/02/10 07:22:09] HW WARNING portPollPpe: port=9/40,link is unstable!
CPU5 [06/20/10 10:41:08] HW WARNING portPollPpe: port=4/4,link is unstable!
CPU5 [03/28/10 07:01:47] SW WARNING Code=0x1ff0009 Blocked unauthorized cli acc
ess
CPU5 [03/27/10 19:58:01] HW WARNING portPollPpe: port=4/13,link is unstable!
P8310_24th:5#
Michael McNamara says
Hi Nicademus,
I’m not really that familiar with the ERS 8300 so I can’t really say. It looks like you have messages from multiple line cards or modules. Are the messages continually occurring?
Good Luck!
Raj says
Hi Michael,
Greetings for your great works. i found your blog quite useful.
I have following query.in my current setup ,we are running 4.1.0.0 code on two ERS-8010.
Can we directly upgrade to 5.1.5.1 release .or suggest any upgrade path.
Cards Details : 1 8648GTR, 2 8692SF , 3 8683XLR
Thanks .
Michael McNamara says
With the details provided you should be fine from a hardware perspective.
Cheers!
LeAnn says
Hi Michael,
We upgraded our CSLAN ERS8600 from 5.1.1.10 load to 5.1.8.3 with TXE card. After upgrade done, the monitor version still shows as 5.1.1.10. Do you know how to manually update the monitor version to the latest one?
Thanks,
LeAnn
Michael McNamara says
Hi LeAnn,
You forgot to upgrade the boot code on the CPU/SF.
Good Luck!
joshua martin says
Hello Michael,
Do you have the port settings to console into the ERS8600? I have been unable to get it working.
Sivakumar says
Can we upgrade directly from 4.1.4 to 5.1.8.3
Michael McNamara says
You can certainly upgrade from 4.1.x to 5.1.x you just need to take a full outage (both core switches need to be down at the same time).
Good Luck!
Steve Holland says
Hi Michael
We have several 8600 Passports running 3.7.7 and 3.7.14 can you please tell me when the support will run out. We dont have a direct contract with Avaya. Also which Cisco switch would you recommend if we swap them out.
Thanks
Steve
Michael McNamara says
Hi Steve,
The answer will depend greatly on what you are using them for… If you just need switch ports you could look at stackable switches. If you are looking for a new core switch with all the latest bells and whistles you could checked out the Avaya VSP 9000 or the Cisco Nexus 7000.
Good Luck!
Peter Lyndley says
After all these years – I cant believe you are finally swapping out those beloved 8600’s ! Look me up sometime…Peter
James Vallejo Mejia says
Hi, I Have problems, you can Say whats is this Error in the port 1/24, 1/25 and 1/27:
CPU6 [02/20/17 04:45:20] SNMP INFO Link Down(1/24)
CPU6 [02/20/17 04:45:20] SNMP INFO Port 1/24 is an access port
CPU6 [02/20/17 04:45:20] RSTP INFO Port Role Change Port 1/24, DESIGNATED->DISABLED
CPU6 [02/20/17 04:45:20] HW WARNING portPollPowerRanger: port=1/24, link is unstable!
CPU6 [02/20/17 04:45:20] SNMP INFO Link Down(1/25)
CPU6 [02/20/17 04:45:20] HW WARNING portPollPowerRanger: port=1/25, link is unstable!
CPU6 [02/20/17 04:45:20] SNMP INFO Link Down(1/27)
CPU6 [02/20/17 04:45:20] HW WARNING portPollPowerRanger: port=1/27, link is unstable!
CPU6 [02/20/17 04:45:20] SNMP INFO Link Oscillation(1/24)
CPU6 [02/20/17 04:45:20] SNMP INFO Link Oscillation(1/25)
CPU6 [02/20/17 04:45:20] SNMP INFO Link Oscillation(1/27)