• September 24, 2020, 06:50:23 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: ERS 8310 fail over  (Read 2956 times)

0 Members and 1 Guest are viewing this topic.

Offline kevins

  • Rookie
  • **
  • Posts: 5
ERS 8310 fail over
« on: April 16, 2015, 07:50:13 AM »
Hi
I have inherited a Nortel 8310 with two 8394SF Mgmt cards, running on code ver 4.2.3.6, using Device manager Ver 6.2.1.4.

In device Manager I did Actions>save boot config and an Actions>save running config, however the Box decided to fail over CPU's.

Have any of you experienced this or can perhaps shed any light on this problem?

I have since repeated the exercise with no fail overs happening (out of hours)

I did find a reference to a bug fix in code 4.2.3.2.

 On dual CPU system, the rcSysGrpDoSaveConfigData MIB object will cause a crash when saving configuration via JDM [wi00733215]

The log files only showed me "system boot", (I have a good boss he did not ask if I rebooted the CPU, bet he was thinking it)

Log files

CPU6 [2014-04-29 20:25:57] SW INFO Loading configuration from /flash/config.cfg
CPU6 [2014-04-29 20:25:58] SW INFO PCMCIA card detected in Stand-by CPU "new-cogf-8310-01" slot 6, Chassis S/N SSPNEK02BA
CPU6 [2014-04-29 20:26:00] HW INFO Received RTC update from master CPU
<NP>000:</NP> [2015-04-08 20:41:19The previous message repeated 344 time(s).       
 CPU6 [2015-04-09 13:22:37] HW INFO Stand-by CPU in slot # 6 becoming master...
 CPU6 [2015-04-09 13:22:37] HW INFO resetting all I/O cards
 CPU6 [2015-04-09 13:22:39] SW INFO Killing task 620d238 after timeout
 CPU6 [2015-04-09 13:22:42] HW INFO Fan Tray 1 up
 CPU6 [2015-04-09 13:22:42] HW INFO Fan Tray 2 up
 CPU6 [2015-04-09 13:22:43] SNMP INFO Fan Up(FanId=1, OperStatus=2)
 CPU6 [2015-04-09 13:22:43] SNMP INFO Fan Up(FanId=2, OperStatus=2)
 CPU6 [2015-04-09 13:22:44] HW INFO Finished insertion for slot 6
 CPU6 [2015-04-09 13:22:44] SW INFO Load configuration started
 CPU6 [2015-04-09 13:22:44] SNMP INFO 2k card up(CardNum=6 AdminStatus=0 OperStatus=3)
 CPU6 [2015-04-09 13:22:44] SNMP INFO 2k card up(CardNum=1 AdminStatus=0 OperStatus=3)
 CPU6 [2015-04-09 13:22:44] SNMP INFO 2k card up(CardNum=2 AdminStatus=0 OperStatus=3)
 CPU6 [2015-04-09 13:22:46] SNMP INFO 2k card up(CardNum=3 AdminStatus=0 OperStatus=3)
 CPU6 [2015-04-09 13:22:46] SNMP INFO 2k card up(CardNum=10 AdminStatus=0 OperStatus=3)
 CPU6 [2015-04-09 13:22:46] SW INFO Slot  2: Loading 127.0.1.6:/pcmcia/p83r4236.dld
 CPU6 [2015-04-09 13:22:46] SW INFO Slot  1: Loading 127.0.1.6:/pcmcia/p83r4236.dld
 CPU6 [2015-04-09 13:22:50] SW INFO Slot  3: Loading 127.0.1.6:/pcmcia/p83r4236.dld
 CPU6 [2015-04-09 13:22:50] SW INFO Slot 10: Loading 127.0.1.6:/pcmcia/p83r4236.dld
 CPU6 [2015-04-09 13:23:00] SW INFO Slot  2: Starting software version 4.2.3.6
 CPU6 [2015-04-09 13:23:00] SW INFO Slot  1: Starting software version 4.2.3.6
 CPU6 [2015-04-09 13:23:04] SW INFO Slot  3: Starting software version 4.2.3.6
 CPU6 [2015-04-09 13:23:04] SW INFO Slot 10: Starting software version 4.2.3.6
 CPU6 [2015-04-09 13:23:08] HW INFO Finished insertion for slot 1
 CPU6 [2015-04-09 13:23:09] HW INFO Finished insertion for slot 2
 CPU6 [2015-04-09 13:23:12] HW INFO Finished insertion for slot 3
 CPU6 [2015-04-09 13:23:14] HW INFO Finished insertion for slot 10
 CPU6 [2015-04-09 13:23:21] SW INFO Software version query from 127.0.1.5 version 4.2.3.6/003, running 4.2.3.6/003
 CPU6 [2015-04-09 13:23:27] HW INFO Finished insertion for slot 5
 CPU6 [2015-04-09 13:23:27] SNMP INFO 2k card up(CardNum=5 AdminStatus=0 OperStatus=3)
 CPU6 [2015-04-09 13:23:27] SW INFO Loading configuration from /flash/config.cfg
 CPU6 [2015-04-09 13:23:36] SW INFO Load configuration done

CPU5 [2014-04-29 20:25:53] SW INFO Loading configuration from /flash/config.cfg
 CPU5 [2014-04-29 20:26:00] SW INFO Load configuration done
 CPU5 [2015-04-09 13:23:22] SW INFO System boot
 CPU5 [2015-04-09 13:23:22] SW INFO Ethernet Routing Switch System Software Release 4.2.3.6
 CPU5 [2015-04-09 13:23:33] SW INFO CPU card entering warm-standby mode...
 CPU5 [2015-04-09 13:23:33] SW INFO Loading configuration from /flash/config.cfg
 CPU5 [2015-04-09 13:23:34] SW INFO PCMCIA card detected in Stand-by CPU "new-cogf-8310-01" slot 5, Chassis S/N SSPNEK02BA
 CPU5 [2015-04-09 13:23:38] HW INFO Received RTC update from master CPU
 CPU5 [2015-04-09 14:51:42] SW INFO user rwa connected from 127.0.1.6 via telnet
 CPU5 [2015-04-09 15:27:31] SW INFO Closed telnet connection from 127.0.1.6, user rwa



 


Offline Jeroen

  • Full Member
  • ***
  • Posts: 56
Re: ERS 8310 fail over
« Reply #1 on: April 24, 2015, 06:44:03 AM »
Hi,

I've been running several ERS8300 with dual CPU (8393) and in cluster mode (IST) for many years now but I've never experienced the issue that you have described.
Currently I'm runing the latest 4.2.3.12 on all 8393's (256MB) without any issues for at least 1 year now.

Your issue might be solved as soon as you do a software upgrade to this code.

Offline kevins

  • Rookie
  • **
  • Posts: 5
Re: ERS 8310 fail over
« Reply #2 on: April 24, 2015, 11:09:17 AM »
Thanks for the feedback

Offline gbeaudoin

  • Rookie
  • **
  • Posts: 1
Re: ERS 8310 fail over
« Reply #3 on: April 24, 2015, 05:52:17 PM »
I have been having issue with memory exhaustion on those devices. I do have a cluster in IST with dual 8393 w/256MB on each side.

I've been switching from active to dormant quite a few time in the last year, the trick is to make sure to save the configuration regularly with the savetostandby flag at true.

Look at the pcmicia card from CPU5, you should get find a copy of the old system old. Filename usualy end with .000.

Offline kevins

  • Rookie
  • **
  • Posts: 5
Re: ERS 8310 fail over
« Reply #4 on: April 27, 2015, 05:36:47 AM »
I did get some feed back from Avaya about a couple of bugs which according to them give similar symptoms “wi01087451 and wi00733215”.

Checked the boot and config they are in sync across the slots, however did notice that the config and boot on the PCMCIA cards are out of sync with the flash.

The consensus seems to be upgrade to the latest and greatest, if it happens again I will take the upgrade route.

Thanks again for the feedback :-)