Adding Remote Devices

Each instance of the Skylight sensor: control must know which remote devices are under its control, since it might discover devices that are intended for another Skylight sensor: control. Use this page to add remote devices to the Skylight sensor: control, then connect and disconnect them as necessary.

There are three ways in which you can associate a remote device with the appropriate instance of the Skylight sensor: control:

• Manual Definition: Remote device parameters are entered in the Skylight sensor: control one at a time.

• Remote Device Definition List: Parameters for multiple remote devices are imported as a batch using a CSV (Comma-Separated Value) file.

• Via the Discovery Inventory: Remote devices that have been discovered by the Skylight sensor: control(using the remote device discovery instances that were created in the Discovery ▶ Configuration page) can be added here individually or in groups of up to 25 devices.

The list of all remote devices that have previously been added to the Skylight sensor: control appears here when you first open the page. For more information, see the section below.

Remote Devices ▶ Configuration page

Details are provided for each device:

• Device: The name provided when the remote device was added to the Skylight sensor: control.
• Serial Number: The unique serial number assigned to the remote device.
• MAC Address: The device’s primary MAC address (a device has two MAC addresses, one per port).

• Linked: Indicates if this remote device has been linked to the Skylight sensor: control. If a link has been established, that means that Skylight sensor: control is controlling the device.
• Yes: The remote device is linked to Skylight sensor: control.
• No: The remote device is not linked to Skylight sensor: control.
• Initializing: The remote device is being initialized prior to linking to Skylight sensor: control.
• Updating: The remote device is linked to Skylight sensor: control and the firmware update is in-progress.
• Update failed: The remote device is linked to Skylight sensor: control and the firmware update failed.

• State: Indicates the state of the remote device.
• Managed: The device is actively managed by this Skylight sensor: control instance.
• Connecting: Skylight sensor: control is attempting to connect to the device (interim state before Connected).
• Connected: The device is connected (interim state before Managed).
• Disconnected: The device is disconnected (temporary state prior to rehoming the device to another Skylight sensor: control).
• Hold: Device on hold (awaiting override-config authorization or firmware update).

• Admin State: Indicates whether the remote device is In Service or Out of Service.
• IS: The device is operational and locked on the active feature load (cannot switch to the alternative feature load).
• OOS: The device is operational and can switch to the alternative load (e.g., TGEN) or be updated to a new firmware.

• Active Feature: The current feature load used on the remote device.
• Current Feature Suite: The version of the current feature suite used on the remote device.

• Update Status: Indicates the state of the last firmware upgrade attempted on the remote device.
• Completed
• Idle: No action is required; the device's firmware is up to date
• Fail: A failure occurred during the firmware upgrade
• Erasing: Currently erasing a section of the device's flash
• Downloading: Currently downloading the firmware onto the remote device
• < progress % >: % of the firmware download actually completed
• Activating: Currently enabling the newly-updated firmware
• Rebooting: The remote device is currently rebooting
• Reboot fail: The remote device rebooting attempts has failed
• Unsupported: The module cannot be updated with the chosen firmware suite or the module's current firmware version is not supported, or the module's hardware is not supported.
• Unsup. Device: The module is not supported. As an example, if a 1st generation module is added to the current version of sensor: control.
• Cancelled: The firmware upgrade was cancelled by the user
• Factory resetting: The device is being reset to its factory settings.
• Reset fail: The attempt to reset the device to its factory settings failed.
• Reset timeout: The factory reset has timed out.
• Rebooting: The factory reset has been successful and the device is rebooting.
• Rebooting timeout: The factory reset has timed out
• Hold: The remote device state is on hold.
• ?: The remote device's update status is unknown

• Vendor: Indicates whether the device is a Cisco-branded or Accedian-branded remote device.

You can quickly manage all the remote devices listed on this page by clicking the following buttons:

• Add: Opens a dialog to configure a new remote device.
• Delete All: Deletes all the devices displayed on the page.
• Connect All: Puts all devices that are in Disconnected state to Managed state.
• Disconnect All: Puts all devices that are in Managed state to Disconnected state.
• Override-Config All: Authorizes configuration override for all devices that are on hold and awaiting it.

To edit or add a remote device to the Skylight sensor: control

1. Access the page Remote Devices ▶ Configuration.
   A listing of all remote devices currently associated with this instance of the Skylight sensor: control is displayed.

   The total number of remote devices found in the system is given in the lower-left corner of the page. Use the page navigation links in the lower-right corner of the page to move between the pages of results.

2. (Optional) To limit the view to only certain remote devices, enter a value on which to filter, then click Search. You can filter by the device name, device serial number, MAC address, admin state, active feature, current feature suite, or whether or not the device has been linked or authorized.
   

   ---

   Note: Enter an asterisk ( * ) as a wildcard to replace one or several characters.

   ---

3. Click Add or Add and Override confirm to add a new remote device or click the name
   of an existing remote device to edit its settings.
   The Remote Device Configuration page is displayed.

4. Do one of these actions:

   • To add or edit a single remote device: Enter the device details, using the information in the following table as a guide. Click Apply to save your changes.
   • To add multiple remote devices: Click Browse (in the Import Remote Devices section at the bottom of the page) to navigate to the CSV file containing the device details, then click Import to upload the file.

The CSV file you select must contain the first four parameters listed in the header (an example is given below):

Serial Number,MAC,Grain Key,Module Type
S001 0000,00:15:01:00:00:00,00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f,00:32

Accedian Skylight sensor: control devices, are described in the following table which lists the types and corresponding names.

Accedian Module Types and Device Names

For information on specific parameters, refer to the following section.

Remote Device Parameters (Remote Devices ▶ Configuration)

Remote Device Name: A name that uniquely identifies the remote device across the network. (Max 25 characters.)

MAC Address: The base MAC address of the remote device (for example 00:15:AD:1D:72:00). This address value is incremented by 1 to assign a MAC address to the second port of the device (for example 00:15:AD:1D:72:01).
Serial Number: The unique serial number assigned to the remote device.
Security Key: The device-specific Grain-128a security key that is associated with each device. The expected format is 00:11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FF

The security key is used to establish a secured session between the Skylight sensor: control and the remote device. These sessions are used to report the link state, as well as to ensure that the parameter and register settings on the remote device can be managed from the Skylight sensor: control instance.

To use the Accedian Management Key (AMK) as the security key, leave this field blank. The AMK ensures a universal authentication mechanism on Accedian devices; its value can be used to connect to all newly-shipped devices that have never been managed.

Regardless of the type of security key being used to protect the remote device, the key value is periodically changed to prevent the management sessions with the Skylight sensor: control from being spoofed.

Linked: Indicates whether or not the remote device is currently linked to this instance of the Skylight sensor: control.

Vendor: Indicates whether the device is a Cisco-branded or Accedian-branded remote device.

Type: The type of remote device.

Supported values are:

• Nano Copper: SFP compute 1G Copper
• Nano 2 Optical: SFP compute 1G optical
• Ant 2 Combo: Module 1G - combo ports (copper and optical)
• Ant 2 Copper: Module 1G - copper ports
• Ant 10G SFP-SFP: Module 10G
• Ant 2 Ext SFP-RJ45: Module SC
• Nano 10G: SFP compute 10G

Connect all: Click this button to connect all remote devices to the Skylight sensor: control.

Disconnect all: Click this button to disconnect all remote devices from the Skylight sensor: control.

Connect: Select this box to allow this Skylight sensor: control instance to establish a link to the remote device.

State Description: Message indicating the cause of the Hold state, detailed as follows in the GUI output:

• Select feature-suite: User intervention required; a feature-suite must be selected for the sensor: module in order to continue.
• Override Configuration: User intervention required; configuration override must be activated on the sensor: module in order to continue.
• sensor: module not compatible: The sensor: module is not compatible or is unsupported by the sensor: control.
• Firmware update failed: The sensor: module could not be updated with it's assigned feature-suite.
• sensor: module integrity error: The integrity of the
  sensor: module is at risk of causing erratic behavior.

State:
Possible states:

• Managed
• Connecting
• Connected
• Disconnected
• Hold

Admin State: Indicates the current admin state (In Service or Out of Service) of the remote device.

Extra Reconnection Delay: Select this box to make the Skylight sensor: control wait longer when reconnecting to this remote device before declaring it unreachable

Tunnel TCP Port: The TCP port to use for the tunnel between the Skylight sensor: control and the linked remote device. The TCP tunnel is used to support advanced features on Skylight modules.

Tunnel DSCP: The DSCP value to use for the tunnel between the Skylight sensor: control and the linked remote device. The DSCP tunnel is used to support advanced features on Skylight modules.

FlexMonitor: Select this box to enable the FlexMonitor on the remote device.

When FlexMonitor is enabled, the remote device is used in out-of-line mode and will be able to activate advanced features on both ports.

Override config: If this field is checked, when adding a remote device there will be no confirmation requested from the user when the sensor: control will link with the device.

Factory Reset: Resets the module's configuration to factory default settings. The factory configuration is the SKU configuration only, and once reset, any configuration done using AMD or by professional services will be lost.

Default Traffic Forwarding: This drop-down list allows the user to select the setting for automatic traffic forwarding at the remote device. Possible values are:

• Permit traffic: Incoming traffic is automatically forwarded between ports when the remote device is powered on. This is the default value.
• Drop traffic: Incoming traffic is automatically dropped when the remote device is powered on.

Parameters used to manually define link to remote device

Static Entry: Select this box to if you want to manually define a Layer- 2 or Layer-3 link to the remote device.

If you check this box, you must complete one or both of these parameters (see below in this table):

• Layer-2 Interface (to link by Layer 2)
• Destination IP (to link by Layer 3)

If this box is not selected, the Skylight sensor: control will search for the remote device in the discovered inventory and attempt to establish a link to it using the MAC address and other information in the top section of the page.

Layer-2 Interface: Used to select an interface of the Skylight sensor: control to use for linking to the remote device.

If you want to manually define a Layer 2 link to the remote device:

1. Enable the Static Entry check box.

2. Select an item in the Layer-2 Interface drop-down list.
   The list includes the interfaces that are bound to the local ports of the Skylight sensor: control.

3. Click Apply at the bottom of the page.
   If you want to manually define a Layer 3 link, see the Destination IP field.

Destination IP: Used to manually enter the IP address of the remote device that you want to add as a managed remote device. You can also add the address of another network device behind the module as an alternative.

If you want to manually define a Layer-3 link to the remote device:

1. Enable the Static Entry check box.

2. Select None as the Layer-2 Interface.

3. Enter the IP address of the Skylight sensor: SFP compute 1G or Skylight sensor: module 1G module (or the address of another network device behind the module) in the Destination IP field.

If you want to manually define a Layer 2 link, see the Layer-2 Interface field.

Information obtained after successful link to remote device

Discovery VLAN: The type of the Discovery VLAN is displayed here, such as C-VLAN:10.

Discovery VCX MAC: The Discovery sensor: control MAC address is displayed here, such as 00:0C:29:F0:17:D9

Discovery VCX IP: The Discovery sensor: control IP address is provided here, if known.

Discovery Destination MAC: The Discovery Destination MAC address is displayed here, such as 00:15:AD:18:CF:1A

Discovery Destination IP: The Discovery Destination IP address is provided here, if known.

Update Status Commands

Apply: Applies changes to the remote device configuration.

Refresh: Refreshes the remote device configuration.

Delete: Deletes the remote device configuration. The device is removed from the sensor: control's span of control.

Reboot: Reboots the remote device within the span of control of the sensor: control, removes the non-persistent configuration from the module and re-starts the remote device. All non-persistent configurations are discarded by the module. However, after the reboot, the sensor: control re-applies many non-persistent configuration back to the device. Persistent configurations (such as interface, policies and TWAMP stateful) are maintained.

Reboot-Delete: Deletes and reboots the device within the span of control of the sensor: control. All non-persistent configurations are discarded. Persistent configurations (such as interface, policies and TWAMP stateful) are maintained. After the reboot, the device is removed from the span of control of the sensor: control.

Logs: Displays the Diagnostic logs for the selected remote device.

Override-Config: Confirmation to push the local sensor: control configuration and override the TWAMP and Policy module configuration.

Factory reset: Resets the sensor: control configuration to factory default settings.

The factory configuration is the SKU configuration only, and once reset, any configuration done using AMD or by professional services will be lost.

Linking Devices to the Skylight sensor: control

The Linked column of the summary table indicates whether or not the remote device has been linked to this instance of the Skylight sensor: control.

The Linked column will display one of four possible statuses:

• No: The remote device is not linked to the Skylight sensor: control
• Yes: The remote device is linked to the Skylight sensor: control
• Initializing: The remote device is being initialized prior to linking to the Skylight sensor: control
• Updating: The remote device is linked to Skylight sensor: control and the firmware update is in-progress
• Update failed: The remote device is linked to Skylight sensor: control and the firmware update failed

A remote device is considered linked to a Skylight sensor: control when the following are true:

• It has been added to the Skylight sensor: control and configured properly, including authorization.
• It has been discovered by the Skylight sensor: control and a management session between the remote device and the Skylight sensor: control has been successfully established.

No direct intervention on your part is required to link a device to a Skylight sensor: control. Once linked, the remote device’s physical ports are added to the list of ports available on the Skylight sensor: control.

Unlinking Devices From the Skylight sensor: control

You can unlink a remote device from its Controller simply by revoking the Skylight sensor: control 's authorization over the device.

To unlink a remote device from the Skylight sensor: control

1. Access the page Remote Devices ▶Configuration.
   A listing of all devices currently associated with this instance of the Skylight sensor: control is displayed.

2. Click the name of the remote device that you want to unlink from the Skylight sensor: control.
   The Remote Device Configuration page is displayed. Details related to the selected device are provided.

3. Revoke the Skylight sensor: control's authorization over the remote device by clearing the Connect check box.
   The selected device is automatically unlinked from the Skylight sensor: control.

Using the FlexMonitor

The FlexMonitor check box is used to enable the FlexMonitor feature. The FlexMonitor instance with the UNI port connected receives monitored traffic for the flowmeter and flow broker.

Enable this feature when the remote device is not in-line with network traffic. By using a mirror port and sending monitoring traffic on the UNI port, management is performed on an NNI port. The FlexMonitor feature disables the port and prevents it from forwarding traffic from the NNI to the UNI port, as well as from the NNI to the UNI port.

When the UNI port is not connected, the FlexMonitor feature is not in use.