The find command in nsterm fails with Error-FindDevices exception.

Issue

The "find" command in nsterm fails with Error-FindDevices exception. See below:


NT: Searching for nsx devices ...
NT: ERROR - FindDevices exception: <error> <eResult>-1</eResult> <source>
<type>0</type> </source> <throwLine>91</throwLine>
<throwSrcFile>SocketUtil.cpp</throwSrcFile>
<text>
<objGuid>85c840c7-9653-4c19-8386-bb2a7f3e10cc</objGuid>
<texts>
<entry>
<objGuid>3d047f46-5112-408b-aaa7-d8a19c4564f3</objGuid>
<mfi>System/MsgSystemGen</mfi>
<msgId>318797142</msgId>
</entry>
<entry>
<objGuid>f77a3580-df8f-4498-adce-b51cb46bf434</objGuid>
<text>107</text>
</entry>
</texts>
</text>
</error>

 

Product Line

Pelco Video Management

Environment

Endura NSM5200: All versions

Cause

This error is an indication that the NSM has not joined the multicast group 230.10.10.8. This is the group that handles all NSM searches.

Resolution

To verify that the NSM has indeed not joined the multicast group, enter netstat -ng from the NSM command line. Something similar to the output below should be seen.

IPv6/IPv4 Group Memberships
Interface RefCnt Group
--------------- ------ ---------------------
lo 1 224.0.0.1
eth0 4 239.255.255.250
eth0 1 224.0.0.1
eth1 1 224.0.0.1

To resolve this issue, first check the output of the route command. Most likely the gateway is incorrect.

To check IP settings enter: more /etc/sysconfig/network-scripts/ifcfg-eth0

For the procedure on how to edit the IP settings please see LL#11678. Please note that if configuring the IP over a network connection use the command reboot instead of using the ifdown eth0/ifup eth0 commands.