Configuring Logical Interfaces

You can define one or more logical interfaces for managing the unit; the types of interfaces available include standard IPv4 or IPv6, bridges and VLANs. Once the interface is defined, you can also define a route to access the unit from outside the unit's subnet.

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 unit 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.

• 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.
• Management: This interface (Interface type Standard) enables access to the Management Web Interface and the 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).

To view the list of logical interfaces

1. Access the page System ▶Configuration ▶Interface.

Adding or Editing a Logical Interface

When the unit is initially installed (or 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 unit with multiple management options.

1. Access the page System ▶Configuration ▶Interface.

2. Click Add to create a new interface or click the Interface Name of an existing interface to edit its settings.

3. Complete the required fields, then click Apply.

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.

Auto Interface Settings (System ▶Configuration ▶Interface)
All Interface Types

IPv4

IPv6

Bridge Interface Type Only

VLAN Settings (VLAN and VLANinVLAN Interface Types Only)

Beacon Settings (All Interface Types Except Auto)

Discovery Settings (Auto Interface Only)

Forwarding Settings (Auto Interface Only)

Advertisement Settings (All Interface Types)

ACL Settings (All Interface Types)

Setting Up a Beacon Instance at Layer 3

You can configure a logical interface to send beacon frames. 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 beacon frames at Layer 2 if the remote units are within the same subnet. Configure the unit to send beacon frames 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 beacon frames. Configure the auto interface of the remote units to listen for beacon frames by modifying the Discovery Settings parameters.

To set up a beacon interface at Layer 3, see Setting Up a Beacon Instance at Layer 3.

To set up a beacon interface at Layer 2, see Configuring Logical Interfaces.

Adding or Editing an IPv4 Route

You can define an IPv4 route that is outside the subnet defined by each interface in order to access a unit that does not reside in 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

1. Access the page System ▶Configuration ▶Interface.

2. 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.

3. Complete the required fields, then click Apply.

For more information on specific parameters, refer to the following table.

IPv4 Route (System ▶Configuration ▶Interface)

Adding or Editing an IPv6 Route
You can define an IPv6 route that is outside of the subnet defined by each interface to access a unit 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

1. Access the page System ▶Configuration ▶Interface.

2. 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.

3. Complete the required fields, then click Apply.

For more information on specific parameters, refer to the following table.

IPv6 Route (System ▶Configuration ▶Interface)

ICMP Redirect Configuration State

The redirect configuaration states include:

• /forwarding: is to allow IP forwarding
• all/accept_redirects: is the global ICMP redirect configuration in IPv4 options
• /accept_redirects: is the interface/Allow ICMP redirect
• The final /accept_redirects: is the Resulting ICMP redirect configuration applied

The following table provides all possible cases for ICMP Redirect configuration states.