Puertas y ventanas

This section describes VLAN configuration and options to access to the internal management agent for Web and SNMP access using the VLAN of the internal switch. Management traffic can either be contained (in-band) in the payload traffic, or completely isolated from the payload traffic (out-of-band).

The Primary and Secondary radio ports cannot be part of the same VLAN.

Any port configured as AdaptPath(Backup) in the LSP configuration pull- down menu must match the VLAN configuration of the Radio primary port.

User Manual NE Management by software application 9500 MPR for ANSI and ETSI

3DB19025AAAA Issue 2

62/234

To access the VLAN Setup screen, select the VLAN link under the Configuration menu.

3.4.4.1 VLAN configuration overview

Configuring VLANs for a radio involves:

1) Configuring management and global port VLAN settings using the upper portion of the VLAN Setup screen:

– Management configuration includes specifying untagged or tagged management and specifying a VLAN ID and port for management.

– Global port configuration includes: selecting C-Tagged, (S-Tagged via license), or VLAN Unaware radio operation, enabling or disabling MAC learning, and specifying MAC aging. – Submitting the settings.

2) Configuring individual port VLAN settings using the middle portion of the VLAN Setup screen: – Selecting the port.

– Specifying the default port VLAN ID (PVID).

– Enabling or disabling ingress filtering. – Adding the membership.

Configuration settings are displayed in the lower portion of the screen.

3.4.4.2 2+0 VLAN Configuration

Figure 5. and Figure 6. show some examples of a Station A and Station B in the 2+0 VLAN configuration. It is mandatory to use two different VLAN numbers for Management/TMN in-band ports in both ODUs of the station.

Warning: In the same station, the two ODUs must use different VLANs.

Warning: Do not set the same VLAN value or range on different ports. This value or range is valid for all

configurations (1+0, 1+1, 2+0).

Figure 5. System 2+0 Station A VLAN configuration ODU #1 A

User Manual NE Management by software application 9500 MPR for ANSI and ETSI

3DB19025AAAA Issue 2

64/234

Figure 6. System 2+0 Station A VLAN configuration ODU #2 A

Figure 7. and Figure 8. show some examples of a Station B 2+0 VLAN configuration. It is mandatory to use two different VLAN numbers for Management/TMN in-band ports in both the ODUs of the station.

Figure 8. System 2+0 Station B VLAN configuration example for ODU #2 B

3.4.4.3 VLAN type

Use the VLAN Type menu to select one of the following modes.

– C-Tagged: The radio operates as an IEEE 802.1q node. This mode supports full Layer-2 function- ality, for example, QoS and Carrier Ethernet.

– S-Tagged is under licence: The radio operates within the service provider network and interprets Ser- vice VLANs.

– VLAN Unaware: The radio passes traffic without any interpretation of VLAN C-Tags and S-Tags. The QinQ (Double Tag) license is set to NO as the factory default.

User Manual NE Management by software application 9500 MPR for ANSI and ETSI

3DB19025AAAA Issue 2

66/234

3.4.4.4 Management access options

If any port other than Copper port is configured as a management port, an Ethernet cable must be inserted into that port, and then the port must be set as a management port on the VLAN Setup page. If the cable is not inserted before setting the port as a management port, the system will lose the connection. Any port, except the Radio Primary and Radio Secondary ports, and SyncE port, is configured as a man- agement port using the Mgt Port drop-down menu. After selecting the port, then selecting the Submit but- ton, the Management VID is automatically displayed in the lower half of the screen in the VLAN Membership Details area.

If any ports are members of the management VLAN, management access is possible through those ports. In the example below, the management access is possible through the Copper#9 port, as well as Ethernet Port 5.

3.4.4.4.1 Tagged / untagged management access

Use the ‘Mgt Access menu to select whether management is handled via Untagged or Tagged frames.

3.4.4.4.1.1 Management access Untagged ingress packets

When the ingress packets are untagged:

– The switch checks the destination address (DA).

– If the DA equals the host management MAC address, the packet is trapped to the CPU port. – If the DA does not equal the host management MAC address, the packet is forwarded to all ports

that have the same port VLAN ID (PVID) as the ingress port.

Tagged ingress packets

When the ingress packets are tagged:

– The switch checks the DA and the VLAN ID

– If the DA equals the host management MAC address, and if the VLAN ID equals the management VLAN ID, the packet is trapped to the CPU port.

– Otherwise, the packet is forwarded to all ports that are members of VLAN ID (according to the tag).

3.4.4.4.1.2 VLAN configuration – tagged/untagged

Each port can be configured to function as tagged or untagged. Untagged is the default.

Tagged egress port

On the egress port – the tagged packet will be forwarded without any changes. However, for untagged packets, the tag will be inserted in the packet as per VLAN classification at the ingress (PVID).

Untagged egress port

On the egress port – for a tagged packet, the tag will be stripped. An untagged packet will be forwarded as is.

Ingress filtering

When VLAN ingress filtering is disabled on a port, all packets are accepted by the ingress port, and for- warding of the packets is determined by egress VLAN rules.

When VLAN ingress filtering is enabled, and if the port is not a member of the VLAN carried in the packet, the packet will be dropped at the ingress and will not be forwarded to the bridge. However, all untagged packets are forwarded to the bridge, regardless of whether or not VLAN ingress filtering is enabled. Table 6. describes how tagged and untagged packets are handled at the ingress and egress ports.

User Manual NE Management by software application 9500 MPR for ANSI and ETSI

3DB19025AAAA Issue 2

68/234

Table 6. How tagged and untagged packets are handled at the ingress and egress ports

When are packets dropped?

– Untagged packets: The switch’s internal forwarding engine will forward according to the ingress port’s PVID (that is, it will forward to all egress ports that have the same PVID). If no egress port is a member of that VLAN, the packet will be dropped by the forwarding engine.

– Tagged packets: The switch’s internal forwarding engine will drop the packet if no egress port is a member of the VLAN tag.

– Enforcing tagged membership consumes radio capacity if passing untagged packets. For full Gigabit untagged traffic, the capacity achieved is:

• 64 bytes - 96.132%

3.4.4.4.2 Copper port isolated for management

This option allows for management of each radio terminal through the copper interface or any port, while keeping the management traffic isolated from the core network traffic.

The copper, and management interfaces are configured onto the same internal VLAN.

This effectively places the copper or other port into its own broadcast domain (LAN segment). The exam- ple below shows the connections on the VLAN screen for out-band management. The Mgt. Access and Copper Port#9 are the only ports configured on VLAN 4.

An example of this is depicted below, in which an 802.1Q VLAN trunk is used to allow the management station to access the remote radio's copper port.

The switches keep the core network traffic and the management network traffic secure and separate from one another.

User Manual NE Management by software application 9500 MPR for ANSI and ETSI

3DB19025AAAA Issue 2

70/234

3.4.4.4.3 Management access setup procedure

Use the following steps to configure the management access:

1) Connect to the Web interface of the unit and select the VLAN Setup page.

2) Specify whether management is handled via untagged or tagged frames using the Mgt Access menu.

3) Type in the VLAN ID to be used for management in the Mgt VID field.

4) Select the port to be used for management from the Mgt Port drop-down menu. 5) Click Submit.

6) To provide management access to additional ports, select the port from the Ethernet Port drop- down menu, and type in the VLAN ID used for management in the PVID field (same VLAN ID as entered in the Mgt VID field). Then click Add Membership.

3.4.4.5 MAC learning enable / disable

The MPT-GC radio link acts as a network bridge. The MPT-GC contains a bridging or forwarding table. The MPT-GC examines the source addresses in received packet headers to locate unknown devices. A device will either be local, or local to the far end of the link. Use the Mac Learning menu to enable or disable MAC Learning.

When MAC learning is enabled, the switch dynamically learns the MAC addresses and directs the traffic to a target port, provided the destination MAC address is already learned. If the MAC address is not learned (that is, no entry in the forwarding database) the packet will be forwarded to all egress ports within the VLAN.

When MAC learning is disabled, all packets will be forwarded to all ports within the VLAN.

3.4.4.6 MAC ageing

Use the MAC Ageing field to set the maximum age of a dynamically learned entry in the MAC address table. The range is 10 - 630 seconds. When the maximum age is reached, the MAC address entries are removed, given that the packet with the learned MAC entry as source does not enter the switch in this period.

3.4.4.7 VLAN addition and deletion

An Ethernet port can be assigned one VLAN ID or multiple VLAN IDs. Multiple VLAN IDs can be assigned to a port simultaneously, for example, 2,3, 100-200.

To add a VLAN IDs to a port:

1) Select the port using the Ethernet Port drop-down menu.

2) Specify the VLAN number (1-4095).

For Tagged, enter the VLAN number(s) in the Tagged in VLAN(s) field. For Untagged, enter the VLAN number(s) in the Untagged in VLAN(s) field.

3) Use the PVID field to enter the port default VLAN ID.

4) Use the Ingress Filtering drop-down menu to enable or disable ingress filtering for the port.

5) Click the Add Membership button.

The VLAN IDs and tagged/untagged status for the port is displayed in the lower half of the screen in the VLAN Membership Details area, if the Refresh button is clicked after adding or deleting VLAN IDs. To delete a VLAN ID from a port:

1) Type the VLAN ID number(s) to be deleted in the Tagged in VLAN(s) or Untagged in VLAN(s) field. (You can refer to the VLAN Membership Details area for port VLAN ID numbers.). 2) Select the Delete Membership button.

User Manual NE Management by software application 9500 MPR for ANSI and ETSI

3DB19025AAAA Issue 2

72/234