- Print
- PDF
You can define one or more logical interfaces for managing the Skylight sensor: control instance; the types of interfaces available include standard IPv4, IPv6, VLAN or VLAN-in- VLAN interfaces. Once the interface is defined, you can also define a route to access the Skylight sensor: control from outside its management subnet.
CAUTION: IP addresses are shared by both interfaces of a remote device.
The following types of logical interface are available:
- Standard: This interface type is associated with a single port. You could use a standard interface to manage the Skylight sensor: control from a single untagged port.
- VLAN: Like standard interfaces, this interface type is also associated with a single port. One use of a VLAN interface would be if you wanted to separate the management traffic from the client traffic. In this example, you would create a VLAN for the management and another VLAN for the customer traffic.
Note: Setting up policies and filters in this manner does not prevent the Management VLAN traffic from communicating with the Skylight sensor: control.
- VLAN-in-VLAN (.1q in .1q): This interface type is also associated with a single port. You can use this interface type when you want to use sub-VLAN. With a VLAN-in-VLAN interface, you can assign priority, as well as choose the Ethertype and VLAN.
By default, the following logical interface is defined:
- Management: The default interface (Standard type) that enables access to the Management Web Interface and CLI via the management port
You can configure interfaces for dual homing by specifying a second IP address (an IP address alias). When specifying an alias, only the address, network mask and gateway parameters can be defined. An alias interface is always set up as a static IP address (DHCP cannot be used).
Note: An interface can also be used for other purposes, such as for loopbacks or test set interaction.
▶ To view a logical interface
Access the page System ▶ Configuration ▶ Interface.
A listing of all logical interfaces associated with this instance of the Skylight sensor: control is displayed.(Optional) To limit the view to only certain interfaces, enter a value on which to filter, then click Search. You can filter by the interface name, interface state, IP address, netmask, the info field value, ACL, the device name or whether or not DHCP has been enabled.
Note: Enter an asterisk ( * ) as a wildcard to replace one or several characters.
System ▶ Configuration ▶ Interface
For information on specific parameters, refer to the table "Interface Settings (System ▶ Configuration ▶ Interface)".
Adding or Editing a Logical Interface
After a factory default reset, a logical interface named Management is bound to a port. You can add and edit more logical interfaces to provide the Skylight sensor: control with multiple management options.
CAUTION: If you modify a Management interface, you or another user may lose access to the management Web interface and/or the CLI.
▶ To add or edit a logical interface
Access the page System ▶ Configuration ▶ Interface.
Click Add to create a new interface or click the Interface Name of an existing interface to edit its settings.
Note: You cannot modify a remote interface’s IP settings when adding a new interface.Complete the required fields, then click Apply.
Notes:
The fields displayed will vary, depending on the Interface type you select.You can set the IP address for an interface to 0.0.0.0 when the interface is not required to be an IP interface, such as when the interface is used for loopback or test set interaction.
For more information on specific parameters, refer to the following table.
Interface Settings (System ▶ Configuration ▶ Interface)
All Interface Types
Parameter | Description |
---|---|
Management | Select this box to identify the remote device interface for management (UNI or NNI). |
State | Enabled or disabled. |
Interface name | A name to identify the interface |
Interface type | The type of interface to create. Available options are:
|
On Port(s) | The port on which the interface is active Note: The list provided corresponds to the local ports on the Skylight sensor: control, as well as the remote devices' ports. |
IPv4
Parameter | Description |
---|---|
Allow ICMP redirect | Select this box to enable IPv4 accept/send ICMP redirects. Default value is enabled for local interfaces. |
Automatic IP (DHCP) | Allows the interface to act as a DHCP client and automatically obtain its IP address, DNS server and gateway settings from a DHCP server. Note: For a remote device, you can only enable DHCP on its management interface. |
Use this interface for DHCP requests from the device | Select this box to make the Skylight sensor: control use this interface when handling DHCP requests from the device. Note: Applies to remote interfaces only. |
Use DHCP Unicast Mode | Select this box to enable DHCP Unicast mode. In this mode, the Skylight sensor: control sends a broadcast DHCP server request message. The response returned by a DHCP server will include the server’s unicast address, which will be used for subsequent messages. If DHCP Unicast mode is not enabled, all messages from the Skylight sensor: control will be sent in broadcast mode. Note: Applies to remote interfaces only. |
Use DHCP Route Information | Allows the Skylight sensor: control to obtain routing information from the DHCP server.
Note: Applies to remote interfaces only. |
Use Static IP Until DHCP Response | Uses the manually configured IP address on the interface until an address is resolved by DHCP. Note: Available only when using Automatic IP (DHCP) mode; not available with the Auto interface. Applies to local interfaces only. |
Manual Configuration | Check this box if you want to manually define the IP address for the interface. |
IP Address | The IP address assigned to the interface, if required. |
Network Mask | The network mask associated with the IP address, if required. |
Default Gateway | A default gateway address provides a shortcut to creating a default gateway through the route configuration. Only one default gateway can be set per Skylight sensor: control. |
IP Address Alias | A second IP address that you may assign to the interface if dual homing is required. This address must belong to a different subnet than the primary IP address. Note: Applies to remote interfaces only. |
Network Mask Alias | The network mask associated with the IP address alias, if required. Note: Applies to remote interfaces only. |
Default Gateway Alias | The default gateway associated with the IP address alias, if required. Note: Applies to remote interfaces only. |
IPv6
Parameter | Description |
---|---|
IPv6 Enable | Enable or disable IPv6 on the interface. |
Allow ICMP redirect | Select this box to enable IPv6 accept ICMP redirects. Default value is enabled for local interfaces. Note: IPv6 ICMP send redirects are always enabled. |
DHCPv6 | Make a selection from the drop-down list to indicate the implementation of DHCPv6 (only used if IPv6 is enabled) Note: DHCPv6 is supported for sensor: control local interfaces only and not for remote device interfaces. Acceptable values are:
|
Static Address | Enable or disable IPv6 static addresses (used if IPv6 is enabled) |
Router Advertisement Prefix | Enable or disable IPv6 router advertisement auto-configuration (used if IPv6 is enabled) Note: This is supported for sensor: control local interfaces only and not for remote device interfaces. |
Static IPv6 Address / Prefix Length | Static interface IPv6 addresses (used if IPv6 and IPv6 static addresses are enabled) Note: Can be reinitialized by setting the value to :: /0 |
IPv6 Default Gateway | IPv6 default gateway addresses (used if IPv6 and IPv6 static addresses are enabled) Note: Can be reinitialized by setting the value to :: . |
VLAN Settings (VLAN and VLANinVLAN Interface Types Only)
Parameter | Description |
---|---|
VLAN ID | The VLAN ID assigned to the interface |
VLAN Priority | The VLAN priority. Acceptable values range from 0 to 7. |
Ethertype | The Ethertype value for the first or second VLAN ID. The Ethertype may vary, depending on the equipment to which the Skylight sensor: control is connected:
|
ACL Settings (Local Interfaces Only)
Parameter | Description |
---|---|
ACL State | Enable or disable the use of Access Control List (ACL) for this interface |
ACL | The ACL assigned to this interface |
ACL Types | Enable or disable the use of ACL for each management type:
|
Adding or Editing an IPv4 Route
You can define an IPv4 route that is outside the subnet defined by each interface (that is bound locally to a Skylight sensor: control instance) in order to access a remote device that is outside of the management station’s subnet.
Access the page System ▶ Configuration ▶ Interface to view the existing, active IPv4 routes and update their settings.
▶To add or edit an IPv4 route
Access the page System ▶ Configuration ▶ Interface.
In the IPv4 Routes section of the screen, click the Add button to add a new route or click the route Name to edit an existing route.
Complete the required fields, then click Apply.
Note: A route can also be added to a remote device by selecting a remote interface in the IPv4 Interfaces section of the screen.
For more information on specific parameters, refer to the following table.
IPv4 Route (System ▶ Configuration ▶ Interface)
Parameter | Description |
---|---|
Name | The name to assign to the route. It can also be a brief description of the route, such as Default Route. |
Type | The route type may be either Network (for a range of addresses) or Host (for a specific IP address). |
Interface | The interface with which the route is associated. The list of interfaces includes the local interfaces that have been bound to the Skylight sensor: control itself. |
Destination | The route's network or host address. The default IPv4 destination is 0.0.0.0. |
Network Mask / Netmask | The mask assigned to the route. Note: Only used for Network routes. |
Gateway | The gateway associated with this route. |
Adding or Editing an IPv6 Route
You can define an IPv6 route that is outside the subnet defined by each interface (that is bound locally to a Skylight sensor: control instance) in order to access a remote device that is outside of the management station’s subnet.
Access the page System ▶ Configuration ▶ Interface to view the existing, active IPv6 routes and update their settings.
▶ To add or edit an IPv6 route
Access the page System ▶ Configuration ▶ Interface.
In the IPv6 Routes section of the screen, click the Add button to add a new route or click the route Name to edit an existing route.
Complete the required fields, then click Apply.
Note: A route can also be added to a remote device by selecting a remote interface in the IPv6 Interfaces section of the screen.
For more information on specific parameters, refer to the following table.
IPv6 Route (System ▶ Configuration ▶ Interface)
Parameter | Description |
---|---|
Name | The name of the IPv6 route. It can be a brief description of the route, e.g. Default. |
Type | The route type may be either Network (for a range of addresses) or Host (for a specific IP address). |
Interface | The interface with which the route is associated. This parameter is only for specific situations when a target exists on a different network for that interface. In most situations, the interface is determined automatically. |
Destination | The route's network or host address. Use ::/0 to indicate the default route. |
Network Mask / Netmask | The mask assigned to the route. Note: Only used for Network routes. |
Gateway | The gateway address associated with this route or default gateway address. |
© 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