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)

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!

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

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!

Hi LeAnn,

You forgot to upgrade the boot code on the CPU/SF.

boot /flash/p80b5183.img

Good Luck!

Thanks,
LeAnn

With the details provided you should be fine from a hardware perspective.

Cheers!

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 .

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!

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

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!

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)?

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!

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.

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!

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?

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!

please suggest me which IOS recommended to upgrade in full mesh network with OSPF routing

Regards,
Mohamed Ghani

Thanks for sharing that information Stuart!

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