Reset Search
 

 

Article

SLX ospf daemon crash during snmpwalk of ospfAreaTable OID

« Go Back

Information

 
TitleSLX ospf daemon crash during snmpwalk of ospfAreaTable OID
Symptoms
  • SLX ospf daemon crash during snmpwalk of ospfAreaTable OID
    -bash-4.2$ snmpwalk -v 2c -c public 10.26.143.54 1.3.6.1.2.1.14.2.1.7.0.0.0.0    // 0.0.0.0 represents Area 0
    SNMPv2-SMI::mib-2.14.2.1.7.0.0.0.0 = No Such Instance currently exists at this OID 
    
    2018/09/10-14:28:27, [HASM-1200], 5408, FFDC, WARNING, SLX9540, Detected termination of process ospfd:4940.
    2018/09/10-14:28:27, [HASM-1000], 5409,, CRITICAL, SLX9540, Daemon ospf terminated. System initiated reload/failover for recovery.
    
    
    
  • snmpwalk times out
    -bash-4.2$ snmpwalk -v 2c -c public 10.26.143.54 1.3.6.1.2.1.14.2.1.7.0.0.0.0
    Timeout: No Response from 10.26.143.54
  • SLX chassis subsequently reboots 
    2018/09/10-14:31:02, [HASM-1004], 5579,, INFO, SLX9540, Processor reloaded - Software Fault: KSWD.
  • SNMP context is mgmt-vrf
    SLX-1# show running-config snmp-server 
    snmp-server sys-descr "Brocade BR-SLX9540 Router"
    snmp-server community public groupname admin
    snmp-server host 10.20.30.1 public
     version 2c
    snmp-server community public groupname admin
    snmp-server context context-public
     vrf-name mgmt-vrf
    snmp-server mib community-map public context context-public
    
Environment
  • SLX Series
  • SLX OS
  • SNMP
  • OSPF
Cause
Engineering have advised that the OSPF daemon crash was as a result of accessing the NULL value.
Resolution
Workaround
  • Configure the snmp-server context in the default-vrf or any user-vrf you have OSPF configured
Additional notes
Fix
  • A software fix to avoid this issue will be available in future SLX-OS releases under DEFECT000666065

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255