DEVICE WILL NOT AUTO-DISCOVER

Symptoms:

Discover all devices on system
Device will not auto-discover

Facts:

SuperStack 3 NBX
NBX 100
NBX 25
NBX CALL PROCESSOR
NBX Cards and Adapters
NBX Phones
3C10110
3C10116
3C10116B
3C10116C
3C10121
3C10122
3C10123
3C10124
3C10114

Causes:

Bad LAN connection/cable
Connected to wrong VLAN
Auto-Discover disabled
More than one NBX NCP on the segment
Device is bound/dedicated to a different NCP
Network difficulties
IP address conflict
No recovery after a power failure
Hardware fault

Fixes: Possible Reasons for Auto-Discovery not working:

Test the LAN connection with a known good NBX device to make sure that the cable and the VLAN are good and working.
Enable the corresponding Auto-Discover option in System Settings / System Wide.
Be sure there are NO other NBX telephone systems (NCPs) on the network segment. When a card or phone is installed, it beacons for any available NCP, if more than one is found, it will not boot up. This is easily seen on phones as the display will read “Pick an NBoss” which means there are at least two NCPs seen at layer 2. If this is a card device, the same thing happens, but there is no message. Remove or unplug all other NCPs from the Network, and power down the card or phone, and reboot it.
Be sure the device is not BOUND to a specific NCP. Devices can be bound to an NCP so that instead of looking for any available NCP upon boot up (ff:ff:ff:ff:ff:ff), they look for a specific MAC address. On phones, this is configurable through the LUI (local user interface). On T1 cards, this is done through the CONSOLE port on the T1 card after boot-up. Dilemma: if a T1 card is BOUND, you must either UNBIND it or BIND it to new NCP while it is up and running on the old one. If you have a card bound to an NCP not present, this card will not boot up to be able to unbind it, so the card is “dead”. The TLIM cards may be bound with specific DSP tools run juxtaposed on a PC.
HARDWARE ONCE USED ON A DIFFERENT SYSTEM: If a telephone will not auto discover, it is possible it was once used as a layer 3 (IP) telephone and configured for a prior NBX system. If this is the case and you are now looking to use this phone as a layer 2 phone, access LUI (LCD User Interface) on the phone, manually set the NCP mac address to match the NCP on the system, and reboot the phone after saving settings. If this phone was a layer 3 phone on a different system, use the LUI to change the NCP MAC address, and reboot the phone again.
Shutdown the NBX via NetSet, then power down the box. Bring the box back up with NO CARDS installed, and try to auto discover them one at a time. Also disconnect the NBX chassis from “the network” and isolate just your Admin. PC and the NBX to a single hub, ruling out possible problems with network traffic, or conflicting layer2 / layer3 issues.
IP Addresses 192.0.0.1 and 192.168.1.192 are used by the NCP and DLC temporarily during boot-up. Do NOT use these IP addresses on any other network device, including the PC that you are using to access NetSet. If your PC is set to either of these addresses, there will be a temporary duplicate IP address. Change the PC's address to another on the same sub-net as the NBX, and power down and back up the NBX box AND the PC to clear all arp cache and duplicate table entries. POWER OFF is the only way to clear arp and table caches on the NBX.
Power Failure. After power failure, certain telephones and/or DSS/BLF consoles may not work. If this is the case, first reboot the device, it that does not work, remove the device from NetSet, and Auto-Discover it again as a new device, and associate the user profile to that device so that all voice mail an/or personal information is retained. May need to boot the device again after auto discover is turned back on.
If you still cannot auto-discover one or more cards, the next step is to try a different card and/or NCP, or call Tech Support.

Product(s): NBX
Sub Product(s): NBX 25, NBX 100, NBX Analog Line Card, NBX Call Processor, NBX Phones, SuperStack 3 NBX

— David Gonzalez 2021/04/13 10:41