Reset Search
 

 

Article

Track network 0.0.0.0/0 results in VDX crash

« Go Back

Information

 
TitleTrack network 0.0.0.0/0 results in VDX crash
Symptoms
  • Unexpected reload upon enabling "track network 0.0.0.0/0 priority 100"
TEST-B#
TEST-B# conf t
TEST-B(config)# rb 1  
TEST-B(config-rbridge-id-1)# int ve 511
TEST-B(config-rbridge-Ve-511)# 
TEST-B(config-rbridge-Ve-511)# vrrp-extended-group 100 track network 0.0.0.0/0 priority 100
  •  Daemon dcm terminated seen in the RAS logs

2018/05/01-09:55:45 , [HASM-1200], 271, SW/1 | Active | FFDC, WARNING, TEST-B, Detected termination of process Dcmd.Linux.powe:3005. 
2018/05/01-09:55:48 , [HASM-1000], 272, SW/1 | Active, CRITICAL, TEST-B, Daemon dcm terminated. System initiated reload/failover for recovery. 
2018/05/01-09:55:48 update_master_rtr_list: Session [100] Added new Master router entry IP: 192.168.1.2 advt_intvl: 60 
2018/05/01-09:56:00 , [RAS-1001], 273, SW/1 | Active, INFO, TEST-B, First failure data capture (FFDC) event occurred.
  •  Backtrace below is seen.
(gdb) bt
#0  0x05f9cd64 in raise () from /lib/libc.so.6
#1  0x05fa2260 in abort () from /lib/libc.so.6
#2  0x05f946f0 in __assert_fail () from /lib/libc.so.6
#3  0x0b4e7b44 in DcmNs::VRRPTrackNetworkVlanCallpointWorker::commitTransaction(confd_trans_ctx*, std::vector<confd_tr_item*, std::allocator<confd_tr_item*> >&, std::vector<WaveNs::Attribute*, std::allocator<WaveNs::Attribute*> >&) () from /fabos/lib/libDcm.so
#4  0x0b315300 in DcmNs::RangeCliUtil::commitRangeBasedTransaction(DcmNs::ConfdCallpointWorker*, confd_trans_ctx*, std::vector<confd_tr_item*, std::allocator<confd_tr_item*> >&, std::vector<WaveNs::Attribute*, std::allocator<WaveNs::Attribute*> >&) () from /fabos/lib/libDcm.so
#5  0x0ad8cb88 in DcmNs::ConfdInterfaceObjectManager::commitTransactionAtCallpointWorkers(confd_trans_ctx*) () from /fabos/lib/libDcm.so
#6  0x0ad95fac in DcmNs::ConfdInterfaceObjectManager::s_prepare(confd_trans_ctx*) () from /fabos/lib/libDcm.so
#7  0x077fd934 in confd_fd_ready () from /usr/confd/lib/libconfd.so
#8  0x0ad9a3c4 in DcmNs::ConfdInterfaceObjectManager::readControlAndWorkerSockets() () from /fabos/lib/libDcm.so
#9  0x0adb3188 in DcmNs::ConfdInterfaceObjectManager::bootCompleteForThisLocationEventHandler(WaveNs::BootCompleteForThisLocationEvent const*&) () from /fabos/lib/libDcm.so
#10 0x0f3f6500 in WaveNs::WaveObjectManager::PrismEventMapContext::executeEventHandler(WaveNs::PrismEvent const*&) () from /fabos/lib/libWave.so
#11 0x0f40287c in WaveNs::WaveObjectManager::handlePrismEvent(WaveNs::PrismEvent const*&) () from /fabos/lib/libWave.so
#12 0x0f97e8c8 in WaveNs::PrismThread::start() () from /fabos/lib/libWave.so
#13 0x0f982300 in WaveNs::PrismPosixThread::pthreadStartMethod(WaveNs::PrismPosixThread*) () from /fabos/lib/libWave.so
#14 0x0e041e98 in start_thread (arg=<value optimized out>) at pthread_create.c:302
#15 0x06049554 in clone () from /lib/libc.so.6
(gdb)


 
Environment
  • Network OS
  • VDX series
  • VRRP
Cause
This issue is observed only when an invalid address 0.XXX/X is entered on the switch.  
The cli leads to DCMD termination instead of blocking it with "invalid Ip address/mask" informational message to user.
Resolution
  • Workaround
    • Do not use 0.0.0.0/0 as it is not valid address.
  • Permanent Solution
    • Upgrade to NOS 7.1.0a, 7.0.2a, 7.2.0 or any release that has the fix for DEFECT000633219
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255