- Print
- PDF
Plug & Go enables you to quickly install a factory-reset Cisco Provider Connectivity Assurance Sensor (formerly Skylight performance element) unit on the network and remotely manage it without requiring further unit configuration. The unit discovers and configures its own service ports, automatically configures its management settings, and then adds itself to a centralized inventory-tracking database (the inventory-tracking unit). The purpose of the inventory-tracking unit is to view a network inventory of all units that have advertisement settings enabled.
Plug & Go is supported on both Layer-2 and Layer-3 networks.
This article explains the general steps required to enable the automatic configuration of factory-reset units on the network. These steps are as follows:
- Enable the beaconer and set its ACP level.
- Enable units in the path so that they will forward beacon and advertisement frames. The required configuration will vary, depending on whether the intermediate units are running firmware release 5.2 and higher or 5.1 and lower.
- Configure an inventory-tracking unit.
Beacon and Advertisement Frames
Plug & Go uses multicast frames with Ethertype (0x88fc), referred to as beacons. You need to configure one unit to be the “beaconer” to send the beacons to all remote units that are used by the auto interface for auto-provisioning. You only need to configure one beaconer on your network.
The beacon frame needs to reach the final destination: the remote unit. The remote unit responds by sending an advertisement―a frame of the same type as the beacon―back to the beaconer. Both beacons and advertisements must be transmitted in each direction. If there are any units in the path of the beacon on its way to the remote unit, you must configure each unit to be able to forward beacon and advertisement frames.
CAUTION: Because Plug & Go relies on UDP port 9065 for advertisements, and UDP ports 67 and 68 for beacons, you must ensure that these ports are not blocked by a firewall.
Note: The use of /31 interfaces is not supported with Layer-3 beaconing when the "IP Config Mode" parameter is set to either "Auto" or "Auto-Static". Layer-3 Plug & Go uses the subnet's broadcast address to transmit beacon and advertisement frames. However, /31 subnets do not have a broadcast address because they contain only two IP addresses and are therefore reserved for point-to-point links.
ACP Level
Complying with Service OAM standards, Plug & Go is based on a common multi-domain network model. This model accommodates services delivered by multiple providers at different levels. It is used to ensure that networks using ACP (Accedian Control Protocol) are maintained within defined maintenance levels.
The ACP level is used in transmitting beacon and advertisement frames. A unit receiving a beacon will automatically set its system ACP level to the one included in the beacon frame.
The ACP level defines how far the ACP frames can go. A unit requires a higher level to be able to transmit frames through a unit with a lower level. For example, a unit using ACP frames level 3 will be able to reach another unit if each unit in between has an ACP frame level of 2 or lower.
Configuring a Unit for Beacon
You can configure a logical interface to send beacons. A frame is sent by the central unit (or another unit configured as the beaconer) to all remote units that are used by the auto interface for auto-provisioning. This can be done at Layer 2 or Layer 3. Configure the unit to send beacons at Layer 2 if the remote units are within the same subnet. Configure the unit to send beacons at Layer 3 if the remote units are outside the beaconer's subnet.
Only configure one unit on your network―either the central unit or a separate beaconer―for sending beacons. Configure the auto interface of the remote units to listen for beacons by modifying the Discovery Settings parameters.
- Managing the Unit
- Managing Alarms and System Messages
Setting Up a Beacon Instance at Layer 2
When the beaconer is configured at Layer 2, a frame is sent by the beaconer unit to all remote units that have the auto interface enabled for auto-provisioning.
Note: If the interface configured for beacon is part of a bridge, be sure to disable the advertisement frame filtering on the Plug & Go ▶Inventory page if you want to be able to see the inventory of all units advertising on this interface. Refer to Managing Network Inventory.
To configure a logical interface for sending beacons at Layer 2
Access the page System ▶Configuration ▶Interface.
Click an Interface Name to edit it.
Complete the required fields in the Beacon Settings section, then click Apply.
Setting Up a Beacon Instance at Layer 3
There are two ways to set up a beacon at Layer 3:
Use Interface Settings to specify the interface on which to send the beacons. This method can be used, for example, when units to be configured with Plug & Go are on the same subnet as the interface used to send the beacons (e.g. a network interface with IP of 192.168.10.10/24 and units to be configured on the subnet 192.168.10.0/24).
Use DHCP Relay to send the beacons via a DHCP relay (e.g. a router). This method can be used when the units to be configured with Plug & Go are on other subnets (no interface in the unit is in this subnet). If this method is used, the beacons will be sent using the interface that has a predefined route leading to the DHCP Relay IP address. If no predefined route leads to this IP address, the default gateway address is used. If this method is used with the Use interface settings option, the beacons are sent using this specific interface.
To set up a beacon instance for sending beacons at Layer 3
Access the page Plug & Go ▶Layer-3.
Click Add to add a new Layer-3 Beaconer or click the Layer-3 Beaconer Name to edit an existing beaconer.
Complete the required fields, then click Apply.
For more information on specific parameters, refer to the following table.
Beacon Layer-3 Configuration (Plug & Go ▶Layer-3)
Parameter | Description |
---|---|
Name | A name to identify the Layer-3 beacon instance |
State | Enable or disable the transmission of beacons for this instance. |
Beacon Rate | The interval at which the beacons will be sent:
|
Transmission Settings
Parameter | Description |
---|---|
Destination IP | When neither the Use Interface Settings nor the Use DHCP Relay option is selected, the beacons are sent to the address you specify here. The value you enter is typically a directed-broadcast address that enables all remote devices to receive the beacon frame. When remote devices are not directly connected to the beaconing device, all intermediate network devices (e.g. routers) must be configured to allow directed-broadcast IP addresses to pass through to the destination subnet. Furthermore, it is up to the operator of the beaconing device to locally configure the necessary route for the beacons to be transmitted out from the appropriate physical port. |
Use Interface Settings | Enables or disables the use of a specific interface for sending the beacons. |
Interface | Specify which interface to use for sending beacons by making a selection in the drop-down list. Note: Only available when Use Interface Settings is enabled. |
Use DHCP Relay | Enable or disable the use of a DHCP relay (e.g. a router) for sending the beacons. Note: You can also enable the use of the interface settings if you want to send the beacon from a specific interface. |
DHCP Relay IP | The IP address of the DHCP relay toward which beacons are sent. Note: Only available when Use DHCP Relay is enabled. |
DHCP Relay Destination Subnet | The subnet of the DHCP relay interface that faces the client network. Note: Only available when Use DHCP Relay is enabled. |
Beacon Settings
Parameter | Description |
---|---|
Domain ID | In the discovery process, the domain ID can be matched by remote devices to select which beacons it should process. See the Domain ID and ID Matching parameters in the Discovery Settings parameters. |
IP Config Mode | Indicates which IP configuration mode the receiver should use:
|
Advertisement IP | Instructs the remote device to send Layer-3 advertisements to this destination IP address. |
Authorize ID Mismatch | When enabled, it tells the receiver to accept beacons even if the beacon's domain ID does not match the local domain ID when ID matching is enabled at the receiver. This is useful for troubleshooting Domain entry errors. |
IP Subnet | The IP subnet used by the units receiving the beacons. Note: Only applies to the Auto and Auto-Static IP config modes. |
Mask | The subnet mask used by the units receiving the beacons. Note: Only applies to the Auto and Auto-Static IP config modes. |
Gateway | The gateway used by the units receiving the beacons. Note: Only applies to the Auto and Auto-Static IP config modes. |
IP Exclusion List | Indicate a list of IP addresses, if any, to be excluded from the remote units. You can specify both single IP addresses and ranges of addresses, each separated by commas. For example, a range of 172.16.1.2-172.16.1.5 spans four IP addresses. A total of 100 IP addresses can be specified here, including both address ranges and single IP addresses. Note: Only applies to the Auto and Auto-Static IP config modes. |
DHCP Host Name | The name assigned to the DHCP host. Possible values are:
|
Field to the right of the DHCP Host Name | Enter the DHCP hostname or serial number value here after making a selection in the DHCP Host Name drop-down list. Note: Only applies to the DHCP IP config mode. |
DHCP Client ID | The ID assigned to the DHCP client. Possible values are:
|
Field to the right of the DHCP Client ID | Enter the DHCP client's serial number or custom client ID value here after making a selection in the DHCP Client ID drop-down list. Note: Only applies to the DHCP IP config mode. |
One-Shot Beacon | When you press Send, the system sends a single beacon frame with the information that has previously been configured and applied. If changes to the beacon settings were made without clicking Apply, they would not be effective in the beacon frame. |
Deleting a Beacon Instance at Layer 3
To delete a beacon instance at Layer 3
Access the page Plug & Go ▶Layer-3.
Select the beacon instance to delete by clicking its name in the list.
The Layer-3 beacon configuration page opens.Click Delete.
Modifying a Beacon Instance at Layer 3
To modify a beacon instance at Layer 3
Access the page Plug & Go ▶ Layer-3.
Select the beacon instance to modify by clicking its name in the list.
The Layer-3 beacon configuration page opens.Update the beacon's setting as required.
Click Apply to save your changes.
Configuring the Forwarding Settings of Intermediate Units
To configure the forwarding settings of each intermediate unit
Access the page System ▶Configuration ▶Interface.
Click the Auto interface to edit its settings.
In Forwarding Settings, set the level to All or to a value lower than the one set in the beaconer. Doing so allows beacon and advertisement frames to pass through this unit.
Set all other fields as required, then click Apply.
Managing Network Inventory
Viewing Network Inventory
You can view the network inventory of all Accedian units that have advertisement settings enabled. For more information about advertisement settings, refer to Configuring the Logical Interfaces.
To view the network inventory
Access the page Plug & Go ▶Inventory.
Click Enable Inventory Tracking, then click Apply.
For more information on specific parameters, refer to the following table.
Discovery Config and Inventory (Plug & Go ▶Inventory)
Parameter | Description |
---|---|
Enable Inventory Tracking | Enables the gathering of discovery inventory. A table of all units that have advertisement enabled to send an information frame on the network is displayed. |
Enable Advertisement Filtering | Filters advertisements based on the beacon configuration state of the unit interfaces. The advertisements are added to inventory only if they are received on a port that has an interface with the beacon state enabled. Note: If the interface configured for beacon is part of a bridge, you must disable the advertisement frame in order to see the inventory of all units advertising on this interface. |
Inventory Warning Threshold | The inventory NIDs are limited to 4000 devices. This field allows the user to set an inventory almost full value, which then delivers a notification alarm when this value is approaching. Default setting is 3000. If this value is reached the almost full alarm is raised, and then inventory full alarm is raised if the inventory NIDs reach the 4000 devices limited. |
Inventory
Parameter | Description |
---|---|
Remote NID IP | The IP address assigned to the remote unit. |
System Description | The type of remote equipment, such as . |
Serial Number | The serial number assigned to the remote unit. |
FW Version | The firmware version of the remote unit. |
Hostname | The hostname of the remote unit. |
IP Interfaces | The list of enabled IP interfaces configured on the remote equipment. |
Domain ID | The domain ID that was used in the discovery process to configure this unit. |
Base MAC Address | The MAC address associated with the unit as displayed in the Home tab. |
Interface MAC Address | The MAC address of the remote unit port that sends advertisements. |
Remote Port | The name of the remote unit port that sends advertisements. |
Local Port | The name of the local unit port that receives advertisements |
SNMP Port | The UDP port of the SNMP agent for the remote unit, if configured |
Web Server Port | The remote unit Web port used. |
Config Status | Indicates whether the remote unit is running with the Default configuration or is User configured. |
Last Update | Last time the information for this remote unit was updated. |
Unicast Beacon Configuration
Parameter | Description |
---|---|
Domain ID | In the discovery process, the domain ID can be matched by remote devices to select which beacons it should process. |
IP Config Mode | Tells the receiver the IP configuration mode that the receiver should use:
|
IP Subnet | Subnet used by the receiver when Auto or Auto Static IP config mode is selected. |
Mask | Mask used by the remote device when Auto or **Auto Static IP config mode is selected. |
Gateway | Gateway used by the remote device when Auto or Auto Static IP config mode is selected. |
Authorize ID Mismatch | When enabled, it tells the receiver to accept beacons even if the beacon's domain ID does not match the local domain ID when ID matching is enabled at the receiver. Useful for troubleshooting Domain entry errors. |
Beacon Type | The only choice is Renew config. It renews the configuration of all remote units that have the advertisement settings set to enable. |
Send Beacon | When you press Send beacon, the system sends a single beacon with the information that has previously been configured. |
You can also view more information on a specific unit by clicking on the link in the Serial Number column.
For more information on specific parameters, refer to the table Discovery config and inventory (Plug & Go ▶Inventory).
Logging In to a Remote Unit
You can connect and manage a remote unit by logging in to the Web server of the remote unit.
To connect to the remote unit
Access the page Plug & Go ▶Inventory.
Click the hyperlink in the Remote NID IP column.
The login page for the remote unit is displayed.Enter your user name and password to start managing the remote unit.
For more information on specific parameters, refer to the table Discovery config and inventory
(Plug & Go ▶Inventory).
Sending a Beacon
To send one beacon to the remote units
Access the page Plug & Go ▶Inventory.
Click Send Beacon.
For more information, refer to the table Discovery Config and Inventory (Plug & Go ▶ Inventory).
You can also configure a logical interface for beacon on the Interface Settings page. Refer to Configuring the Logical Interfaces.
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks