Re: IVR E_DEBUG message explanation

mello_mello · ‎02-20-2010

Hello, colleagues.

Kindly ask you for help in explanation of this IVR E_DEBUG message on MDS 9506:

1) Event:E_DEBUG, length:56, at 63433 usecs after Tue Feb 16 18:08:47 2010
    [825307441] 10:00:00:00:c9:89:9b:ca recvd DU_OFFLINE on vsan 5
2) Event:E_DEBUG, length:56, at 503246 usecs after Tue Feb 16 17:49:59 2010
    [825307441] 10:00:00:00:c9:89:9b:d0 recvd DU_OFFLINE on vsan 5
3) Event:E_DEBUG, length:56, at 113231 usecs after Tue Feb 16 17:03:51 2010
    [825307441] 10:00:00:00:c9:89:9c:2c recvd DU_OFFLINE on vsan 5
4) Event:E_DEBUG, length:58, at 810466 usecs after Tue Feb 16 15:21:28 2010
    [825307441] 50:01:43:80:01:33:07:80 recvd DU_OFFLINE on vsan 225
5) Event:E_DEBUG, length:58, at 612426 usecs after Tue Feb 16 15:21:28 2010
    [825307441] 50:01:43:80:01:33:06:80 recvd DU_OFFLINE on vsan 226
6) Event:E_DEBUG, length:58, at 741304 usecs after Tue Feb 16 14:46:40 2010
    [825307441] 50:01:43:80:01:33:06:80 recvd DU_OFFLINE on vsan 226
7) Event:E_DEBUG, length:58, at 699085 usecs after Tue Feb 16 14:46:40 2010
    [825307441] 50:01:43:80:01:33:07:80 recvd DU_OFFLINE on vsan 225
8) Event:E_DEBUG, length:56, at 306934 usecs after Tue Feb 16 12:44:32 2010
    [825307441] 10:00:00:00:c9:89:9c:2c recvd DU_OFFLINE on vsan 5
9) Event:E_DEBUG, length:56, at 740764 usecs after Tue Feb 16 12:26:07 2010
    [825307441] 10:00:00:00:c9:89:9c:2c recvd DU_OFFLINE on vsan 5
10) Event:E_DEBUG, length:58, at 421776 usecs after Tue Feb 16 12:23:24 2010
    [825307441] 10:00:00:00:c9:82:0d:7c recvd DU_OFFLINE on vsan 220
11) Event:E_DEBUG, length:58, at 807075 usecs after Tue Feb 16 12:22:20 2010
    [825307441] 10:00:00:00:c9:82:11:e2 recvd DU_OFFLINE on vsan 220

What does it mean: DU_OFFLINE?

Additional information:

Software
BIOS:      version 1.1.0
loader:    version 1.2(2)
kickstart: version 3.3(3)
system:    version 3.3(3)

BIOS compile time:       10/24/03
kickstart image file is: bootflash:/m9500-sf1ek9-kickstart-mz.3.3.3.bin
kickstart compile time: 12/11/2008 14:00:00 [03/24/2009 10:46:57]
system image file is:    bootflash:/m9500-sf1ek9-mz.3.3.3.bin
system compile time:     12/11/2008 14:00:00 [03/24/2009 11:23:05]

Hardware
cisco MDS 9506 ("Supervisor/Fabric-1")
Intel(R) Pentium(R) III CPU with 1028596 kB of memory.
Processor Board ID JAE1006VCK6

bootflash: 250880 kB
slot0: 0 kB

mds-c9506-sw-vc kernel uptime is 40 days 7 hours 1 minute(s) 9 second(s)

Last reset at 509441 usecs after Thu Jan 7 11:47:04 2010
    Reason: Reset triggered due to Switchover Request by User
    System version: 3.3(1a)
    Service: SAP(93): Swover due to install

`show module`
Mod Ports Module-Type                      Model              Status
--- ----- -------------------------------- ------------------ ------------
1    32     1/2 Gbps FC Module               DS-X9032           ok
2    32     1/2 Gbps FC Module               DS-X9032           ok
3    32     1/2 Gbps FC Module               DS-X9032           ok
4    48     1/2/4 Gbps FC Module             DS-X9148           ok
5    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    active *
6    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    ha-standby

Any ideas are highly appreciated!!!

Thank you in advance.

emcprateek_2 · ‎03-03-2010

IVR DU is a new database after 3.2(x), which is constructed by the name server response and maintains the online status for IVR devices in the fabric.

From the debug messages it appears as if the devices are logging out of the DU database. Do you have a Zoneset that is stuck in activation ?

Did you recently upgrade ?

Please do share "sh run | i ivr"

Thanks,
Prateek

mello_mello · ‎03-04-2010

Hello Prateek

Thank you for your reply, but this case is no longer relevant.

And i can not provide you with the requested information.

Once again - thank you!

Mello