cancel
Showing results for 
Search instead for 
Did you mean: 

I/G/C/B/A-Series f/w 6.61.06.0009 Reset with "lldpXMedRemCapabilitiesEntry_get" error

I/G/C/B/A-Series f/w 6.61.06.0009 Reset with "lldpXMedRemCapabilitiesEntry_get" error

FAQ_User
Extreme Employee
Article ID: 14702

Products
I-Series, firmware 6.42.10.0016 through 6.61.06.0009
G-Series, firmware 6.42.10.0016 through 6.61.06.0009
C5-Series, firmware 6.42.10.0016 through 6.61.06.0009
C3-Series, firmware 6.42.10.0016 through 6.61.06.0009
B5-Series, firmware 6.42.10.0016 through 6.61.06.0009
B3-Series, firmware 6.42.10.0016 through 6.61.06.0009
A4-Series, firmware 6.61.02.0007 through 6.61.06.0009

Changes
Exposed the system to LLDP traffic, for instance as a result of a NetSight Topology Manager topology scan.

Symptoms
System reboot event.

With firmware 6.51.02.0018 and lower...
The current.log (5487) displays a generic "
code:
l7_prepareSystemDump
" Backtrace; for example: <57> JUN 19 11:41:17 2012 STK1 BOOT[268430624]: bootos.c(1398) 253 %%
Start of Code - Build:06.42.11.0006 Date:Tue Feb 7 16:20:11 2012
BackTrace-0x0078a484: sysReboot (0x78a484) + 0x0
BackTrace-0x0104c2c0: SwitchReset (0x104c228) + 0x98
BackTrace-0x00b7c324: l7_prepareSystemDump (0xb7b880) + 0xaa4
BackTrace-0x00b7c904: l7MonitorTask (0xb7c82c) + 0xd8
BackTrace-0x011658c0: vxTaskEntry (0x1165864) + 0x5c
BackTrace-r0 = 0x07caa2b4 r1 = 0x07c7c980 r2 = 0x00000000
BackTrace-r3 = 0x00000000 r4 = 0x0000002f r5 = 0x00000000
BackTrace-r6 = 0x00000000 r7 = 0xa13a0204 r8 = 0x00000000
BackTrace-r9 = 0x07caa2b4 r10 = 0x00000026 r11 = 0x00000000
BackTrace-r12 = 0x0000002e r13 = 0x00000000 r14 = 0x00000000
BackTrace-r15 = 0x00000000 r16 = 0x00000000 r17 = 0x00000000
BackTrace-r18 = 0x00000000 r19 = 0x00000000 r20 = 0x00000000
BackTrace-r21 = 0xffffffff r22 = 0x00000000 r23 = 0x00000000
BackTrace-r21 = 0xffffffff r22 = 0x00000000 r23 = 0x00000000
BackTrace-r24 = 0x019ac0d4 r25 = 0x01b0416c r26 = 0x00000000
BackTrace-r27 = 0x00000000 r28 = 0x019b3224 r29 = 0xffffffff
BackTrace-r30 = 0x07c7df50 r31 = 0x0000b030
BackTrace-lr = 0x01162ae8 pc = 0x012098fc msr = 0x0000b030
<110> JUN 19 11:42:21 2012 STK1 BOOT[129197792]: edb_bxs_api.c(786) 273 %%
Last switch reset caused by Fault(0x00001100) SRR0(0x01162ae8) SRR1(0x4002b030) MSR(0x00001030) DMISS(0x12916988) IMISS(0x00000000)With firmware 6.61.02.0007 and higher...
The current.log (5487) displays a "
code:
Task SNMPTask(
<
address
>
code:
) is suspended...
" message; for example:Task SNMPTask(0xcfff980) is suspended with error 2, creating file sysDmp1May2512.zWith all (except 6.51) firmware...
The sysDmp (13650) file states "
code:
Task Name: SNMPTask
" and displays a "
code:
lldpXMedRemCapabilitiesEntry_get
" diagnostic; for example:Detailed erred task information
---------------------------------
Calling Stack:

------------
Task ID: 0x7c7ccd0
Task Name: SNMPTask
PC: 0x120ecec
PendQ: 0x7c7dfd4
SP: 0x7c7c3f0

0x120ecec: taskSuspend (0x120e8b0) + 0x43c
0x103d91c: log_fault_nvram (0x103d698) + 0x284
0x104c6dc: event_dTLB_miss (0x104c68c) + 0x50
0x104c68c: event_dTLB_miss (0x104c68c) + 0x0
0x1162ae8: bcopy (0x1162994) + 0x154
0x5b6184: lldpXMedRemCapCurrentGet (0x5b60fc) + 0x88
0x699790: usmDbLldpXMedRemCapCurrentGet (0x699780) + 0x10
0xe4ed70: snmpLldpXMedRemCapCurrentGet (0xe4ed28) + 0x48
0xe4bae0: k_lldpXMedRemCapabilitiesEntry_get (0xe4b888) + 0x258
0xeb522c: lldpXMedRemCapabilitiesEntry_get (0xeb5044) + 0x1e8
0xe30954: GetNextObjectInstance (0xe307f8) + 0x15c
0xe32c88: do_response (0xe32b80) + 0x108
0xe271f0: SrDoSnmp (0xe26830) + 0x9c0
0xe2ce28: SrDoMgmt (0xe2cd68) + 0xc0
0xe2c948: snmpd_main (0xe2bc44) + 0xd04
0xe2cd58: L7_snmp_task (0xe2cd1c) + 0x3c
0x11658c0: vxTaskEntry (0x1165864) + 0x5cCause
This is an apparent variation of the LLDP reboot issue as described in 13872.

Solution/Workaround
Upgrade to firmware 6.61.07.0010 or higher (14480).
Release notes state, in the '
code:
Changes and Enhancements in 6.61.06.0009
' section:
code:
17048
code:
Resolved a code exception in SNMPTask with reset "BOOT[141143864]:

code:
edb_bxs.c(1226) 108 %% Last switch reset caused by Fault(0x00001100) SRR0(0x01162ae8) SRR1(0x4000b030) MSR(0x00001030) DMISS(0xc914d6d0) IMISS(0x00000000)".

Release notes
state, in the '
code:
Changes and Enhancements in 6.61.07.0010
' section:
code:
17017/17027
code:
Resolved a code exception in SNMP task with reset "BOOT[141143864]: edb_bxs.c(1226) 108 %% Last switch reset caused by Fault(0x00001100) SRR0(0x01162ae8) SRR1(0x4000b030) MSR(0x00001030) DMISS(0xc914d6d0) IMISS(0x00000000)".

code:
17530
&
code:
17773
code:
Addressed an issue in LLDP with reset and error similar to "Last switch reset caused by Fault(0x00001100) SRR0(0x0126BB0C) SRR1(0x4002B030) DMISS(0x19DFE888) IMISS(0x00000000) DAR(0x00000000) DSISR(0x00000000)".


Pre-upgrade workaround:
This issue is related to LLDP processing, so disabling it ('
code:
set lldp port status disabled *.*.*'
) should prevent recurrence.

If LLDP is necessary to network functionality, rather than disabling LLDP you may exclude the LLDP MIB:
code:
set snmp view viewname All subtree 1.0.8802.1.1.2 excluded

This allows LLDP to function in terms of advertisements, but prevents SNMP retrieval of LLDP information - which is what triggers the reset event. To remove this command at a later time:
code:
clear snmp view All 1.0.8802.1.1.2
0 REPLIES 0
GTM-P2G8KFN