This chapter describes how the UCS controller performs Auto Discovery
of Cisco ME 1200 NIDs which are reachable in the network. The UCS controller
has to maintain the device information and monitor the notifications sent by
the discovered NIDs. Key steps performed during Auto Discovery are:
Auto Discovery of NID Devices after ZTP using ProvisionNotifications
Addition of dynamic entries for each registered NID in UCS
Monitoring the health of each NID using Heartbeat Notifications
The sequence of steps
that lead to Auto Discovery and monitoring of NIDs is as follows:
NID acquires IP
address using ZTP and downloads the configuration XML file from TFTP server.
To perform Auto
Discovery, operator needs to first manually edit the two configuration XML
files applicable to each Cisco ME 1200 NID and described in ZTP chapter, steps
7 and 8 (for example, <fqdn>.xml and <NID_MAC_ADDR_CFG>.xml). This
step needs to be performed prior to ZTP trigger so that there is no manual
intervention during ZTP process. These files are usually stored on TFTP server
and downloaded at the end of the ZTP process. For more details about these
configuration files, see
Zero Touch Provisioning
Open the XML
configuration file stored on the TFTP server using any XML editor, and search
for the <notification_client_register_config> XML tag with
<soap_action>setNotificationReceiver</soap_action>. Replace this
XML tag as follows by filling details of the UCS Controller IP address, login
username and password. A sample XML is provided for better understanding below.
Once ZTP is
triggered, after the above configurations are added to configuration XML files
stored in TFTP server for a specific NID, the Cisco ME 1200 NIDs will register
themselves for sending notifications to the UCS controller.
sending HTTP POST notifications periodically.
The UCS controller
will process the notification messages. If the notification is discovery
message, it adds an entry into NID database for the first time. Subsequent
messages are considered as heart beat messages.
A timer will
start after receiving the first discovery message. If three consecutive
discovery messages are not received, the connection to that particular NID will
be torn down and entry in NID database will be removed.
On NID reload, it
has to register for notifications on boot up and should start sending discovery
reload, it waits for the notifications. It has to start the heartbeat timer for
the NIDs present in database.