Currently, the registrar validates the new devices based on an optional list of UDIs that is specified when configuring the registrar.
The list specifies a set of devices that are allowed to join the network.
Figure 3: Provisioning Registrar in an Autonomic Network
The registrar maintains a database of all devices that join or fail to join the domain. The failed devices can try to join the domain
again. The registrar database tracks all devices in the domain and associates each device with the following states:
• Accepted—Devices that successfully join the domain.
• Pending—Devices that are in the process of joining the domain.
• Quarantine—Devices that failed to join the domain.
Channel Discovery in Autonomic Networking
Service Discovery in Autonomic Networking
Autonomic networking uses the multicast Domain Name System (mDNS) infrastructure to discover various services required by the
devices in the autonomic networking domain. Few of the services discovered by the network using the mDNS infrastructure are: the
AAA server, the configuration server, the syslog server, and the autonomic networking registrar. Autonomic networking listens to
the mDNS advertisements on all the devices in the domain. Autonomic networking initiates the mDNS advertisements from the
devices hosting the services.
Autonomic Control Plane
When a new device in the domain receives a domain certificate, it exchanges the domain certificate in the hello messages with its
neighbors. This creates an autonomic control plane between two autonomic devices of the same domain. There are different types of
6
To Next Page
Loading...
Need help?
General
