Posts tagged ERS8600

Ethernet Routing Switch 8600 High-speed Fan Tray (8010CMHS)

9
October 18, 2011
by Michael McNamara in ,

I ran into an interesting oversight on my part today. We have a cluster of Avaya Ethernet Routing Switch 8600s which are running dual 8692SFs w/Mezz and a combination E and R cards on 5.1.3.1 software. We’re growing the network (when are we not) and we’ve outgrown the two 8630GBRs we have in each switch. So we purchased a 8648GBRS for each switch along with an 8648GTRS to replace the legacy 8648TXE card.

Upon inserting the 8648GBRS module in slot 9 we received the following alarm from the console;

CPU5 [10/18/11 12:48:29] SNMP INFO Chassis running on low fan cooling.Please change the fan. Note that if the switch is booted with fan check enabled, then to power up,
1. R module requires a fan (regular or high speed) in running state.
2. RS module requires a high speed fan in running state.
CPU5 [10/18/11 12:48:29] HW ERROR Card in Slot=9, Type=8648GBRS, not powered on due to fan requirements.
CPU5 [10/18/11 12:48:48] HW INFO Card removed: Slot=9 Type=8648GBRS

I immediately knew what the problem was, I had overlooked the high-speed fan tray requirement for any RS modules. We have legacy chassis’s at this location so I knew that slots 1 and 10 couldn’t be populated by an R/RS module, I also knew the power supplies had already been upgraded to 8005PS’s so there was adequate power. However, I overlooked the cooling requirement so today I had to order a bunch of 8010CMHS fan trays.

Cheers!

Ethernet Routing Switch 8600 Software Release v5.1.6.0

3
June 18, 2011
by Michael McNamara in ,

Avaya Ethernet Routing Switch 8600Avaya has released software v5.1.6.0 for the Ethernet Routing Switch 8600. This release has no new features but instead addresses a number of software bugs. Please refer to the release notes for all the details. There is one bug in particular that I’ve personally seen;

  • Broadcast and multicast traffic that should be flooded within a VLAN is no longer forwarded out the same MLT as it arrived if the ingress port is in the port range 41-48 on an 8648GTR or 8648GTRS card. (wi00867614)

I stumbled across this problem while reviewing the port utilization (MRTG) for a number of switch ports. The ifInOctets and IfOutOctets for the ports didn’t look right so after running a packet capture from the standby CPU/SF and reviewing the trace we could see Multicast frames that were being sourced from the closet being sent back out to the closet.

I’m still working through a high CPU utilization issue with Avaya on an ERS 8600 IST/SMLT cluster running 5.1.5.1 software although I’ll probably try to load 5.1.6.0 in our testlab and see how it runs. I’d love to hear comments back from anyone running 5.1.6.0 software.

Cheers!

Upgrading DPC FPGA firmware – Part 2

0
April 30, 2011
by Michael McNamara in ,

I recently upgraded a number of Ethernet Routing Switch 8600s to v5.1.5.1 software and had to upgrade the DPC FPGA firmware on the R modules (8630GBR, 8683XLR) within the chassis. I previously covered how to upgrade the DPC FPGA firmware but in the last few upgrades I noticed a recurring error message while the upgrade was in progress. I noticed this problem when upgrading both the 8630GBR and 8683XLR modules when the switch at had dual 8692SF w/SuperMezz daughter cards. I don’t previously recall this error message but I believe it started with 5.1.3.1 software or later. The error message can be safely ignored… although they are annoying as they constantly fill the console screen output.

sw-8600.acme.org:5# config diag fpga dpc update 1 /pcmcia/dpc194.xsvf
Found /pcmcia/dpc194.xsvf

WARNING: Starting the FPGA update process. DO NOT reset the card or  box during
this process. Please wait for FPGA UPDATE SUCCESS message. (Command prompt will
be returned but update process will take several minutes)
This Message will get appended to the log file upon completion of the update.
The command prompt will return after the upgrade is complete.                                                                       -

sw-8600.acme.org:5# CPU5 [04/27/11 05:59:15] COP-SW ERROR SyncTransportLayer: msgState=1, ltrStatus=LTR_SYNC_MSG_SLOT_INUSE, Slot=1

sw-8600.acme.org:5# CPU5 [04/27/11 05:59:15] COP-SW ERROR SyncTransportLayer: msgState=1, ltrStatus=LTR_SYNC_MSG_SLOT_INUSE, Slot=1

sw-8600.acme.org:5# CPU5 [04/27/11 05:59:15] COP-SW ERROR SyncTransportLayer: msgState=1, ltrStatus=LTR_SYNC_MSG_SLOT_INUSE, Slot=1

sw-8600.acme.mlhs.org:5# CPU5 [04/27/11 05:59:15] COP-SW ERROR SyncTransportLayer: msgState=1, ltrStatus=LTR_SYNC_MSG_SLOT_INUSE, Slot=1

sw-8600.acme.mlhs.org:5# CPU5 [04/27/11 05:59:15] COP-SW ERROR SyncTransportLayer: msgState=1, ltrStatus=LTR_SYNC_MSG_SLOT_INUSE, Slot=1

sw-8600.acme.mlhs.org:5# CPU5 [04/27/11 05:59:31] COP-SW INFO Slot 1: FPGA UPDATE SUCCESS - You will need to reboot the switch or re-insert/reset the slot for FPGA to take effect.

There’s reference to this issue in the 7.0 and 7.1 release notes.

wi00518565 - When upgrading FPGA firmware on R or RS modules, the following message can appear: Router-C:5#/CPU5 [03/08/10 15:04:15] COP-SW ERROR 27894800: LtrId = 152,LtrPrio=0,ltrStatus = 15 LTR_SYNC_MSG_SLOT_INUSE),msgId=53,msgState=1,Slot=3 This message has no negative effect on the FPGAupgrade. There are no specific FPGA upgrades required with release 7.0.

Cheers!

Go to Top