HP FlexFabric 7900 Switch Series Layer 2—LAN Switching Configuration Guide Part number: 5998-4281 Software version: Release 2109 Document version: 6W100-20140122
Legal and notice information © Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents Configuring Ethernet interfaces ··································································································································· 1 Configuring a management Ethernet interface ·············································································································· 1 Ethernet interface naming conventions ··························································································································· 1 Configuring comm
Network requirements ··········································································································································· 27 Configuration restrictions and guidelines ··········································································································· 28 Configuration procedure ······································································································································ 28 Configuring Ethernet link aggreg
MSTP················································································································································································ 62 MSTP features ························································································································································ 62 MSTP basic concepts ··········································································································································
Configuring TC-BPDU transmission restriction ···································································································· 90 Enabling TC-BPDU guard······································································································································ 90 Displaying and maintaining the spanning tree ··········································································································· 91 Spanning tree configuration example············
Setting the LLDP re-initialization delay ·············································································································· 121 Enabling LLDP polling·········································································································································· 121 Configuring the advertisable TLVs ····················································································································· 122 Configuring the management address a
Configuring Ethernet interfaces The switch series supports Ethernet interfaces, management Ethernet interfaces, and Console interfaces. For the interface types and the number of interfaces supported by a switch model, see the installation guide. This document describes how to configure management Ethernet interfaces and Ethernet interfaces. Configuring a management Ethernet interface A management interface uses an RJ-45 connector.
Splitting a 40-GE interface and combining 10-GE breakout interfaces Splitting a 40-GE interface into four 10-GE breakout interfaces You can use a 40-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 40-GE interface into four 10-GE breakout interfaces. For example, you can split a 40-GE interface FortyGigE 1/0/16 into four 10-GE breakout interfaces Ten-GigabitEthernet 1/0/16:1 through Ten-GigabitEthernet 1/0/16:4.
Step Command Remarks By default, a 40-GE interface is not split and operates as a single interface. 3. 4. Combine the four 10-GE breakout interfaces into a 40-GE interface. using fortygige Reboot the card that houses the interface. N/A The 40-GE interface combined from the four 10-GE breakout interfaces must use a dedicated 1-to-1 cable or a 40-GE transceiver module and fiber. For more information about the cable and transceiver module, see the installation guide.
Configuring the link mode of an Ethernet interface CAUTION: After you change the link mode of an Ethernet interface, all commands (except the shutdown command) on the Ethernet interface are restored to their defaults in the new link mode. On the switch, Ethernet interfaces can operate either as Layer 2 or Layer 3 Ethernet interfaces (you can set the link mode to bridge or route). To change the link mode of an Ethernet interface: Step Command Remarks 1. Enter system view. system-view N/A 2.
packet forwarding, and automatically generates traps and logs, informing the user to take corresponding actions. To prevent frequent physical link flapping from affecting system performance, configure physical state change suppression to suppress the reporting of physical link state changes. The system reports physical layer changes only when the suppression interval expires. To configure physical state change suppression on an Ethernet interface: Step Command Remarks 1. Enter system view.
• With TxRx mode generic flow control enabled, an interface can both send and receive flow control frames. When congestion occurs, the interface sends a flow control frame to its peer. When the interface receives a flow control frame from the peer, it suspends sending packets. • With Rx flow mode generic control enabled, an interface can receive flow control frames, but it cannot send flow control frames.
You can enable PFC for the specified 802.1p priorities at the two ends of a link. When network congestion occurs, the local device checks the PFC status for the 802.1p priority carried in each arriving packet. The device processes the packet depending on the PFC status as follows: • If PFC is enabled for the 802.1p priority, the local device accepts the packet and sends a PFC pause frame to the peer. The peer stops sending packets carrying this 802.
flow-control priority-flo w-control enable priority-flow-contr ol no-drop dot1p Remarks • On a port configured with the flow-control command, you can enable PFC, but you cannot enable PFC for specific 802.1p priorities. Configured Configurable Unconfigurable • Enabling both generic flow control and PFC on a port disables the port from sending common or PFC pause frames to inform the peer of congestion conditions. However, the port can still handle common and PFC pause frames from the peer.
Step Enable unknown unicast suppression and set the unknown unicast suppression threshold. 5. Command Remarks unicast-suppression { ratio | pps max-pps | kbps max-kbps } By default, unknown unicast traffic is allowed to pass through an interface. Configuring storm control on an Ethernet interface About storm control Storm control compares broadcast, multicast, and unknown unicast traffic regularly with their respective traffic thresholds on an Ethernet interface.
Step Command Remarks The default setting is 10 seconds. (Optional.) Set the traffic polling interval of the storm control module. storm-constrain interval seconds 3. Enter Ethernet interface view. interface interface-type interface-number N/A 4. (Optional.) Enable storm control, and set the lower and upper thresholds for broadcast, multicast, or unknown unicast traffic.
Task Command Clear the interface statistics. reset counters interface [ interface-type [ interface-number ] ] Clear the statistics of dropped packets on the specified interfaces. reset packet-drop interface [ interface-type [ interface-number ] ] Clear the Ethernet module statistics.
Configuring loopback, null, and inloopback interfaces This chapter describes how to configure a loopback interface, a null interface, and an inloopback interface. Configuring a loopback interface A loopback interface is a virtual interface. The physical layer state of a loopback interface is always up unless the loopback interface is manually shut down.
Configuring a null interface A null interface is a virtual interface and is always up, but you can neither use it to forward data packets nor can you configure it with an IP address or link layer protocol. The null interface provides a simpler way to filter packets than ACL. You can filter undesired traffic by transmitting it to a null interface instead of applying an ACL.
Task Command Clear the statistics on the inloopback interface.
Bulk configuring interfaces You can enter interface range view to bulk configure multiple interfaces with the same feature instead of configuring them one by one. For example, you can execute the shutdown command in interface range view to shut down a range of interfaces. If a command fails to take effect on the first interface in an interface range, the command does not take effect on all the other member interfaces.
Step 4. 5. Command Remarks Use available commands to configure the interfaces. Available commands vary by interface. N/A (Optional.) Verify the configuration. display this N/A Displaying and maintaining bulk interface configuration Execute display commands in any view. Task Command Display information about interface ranges configured through the interface range name command.
Configuring the MAC address table Overview An Ethernet device uses a MAC address table to forward frames. A MAC address entry contains a destination MAC address, an outgoing interface, and a VLAN ID. Upon receiving a frame, the device uses the destination MAC address of the frame to look for a match in the MAC address table. If a match is found, the device forwards the frame out of the outgoing interface in the matching entry.
• Static entries—Static entries are manually added in order to forward frames with a specific destination MAC address out of their associated interfaces and never age out. A static entry has higher priority than a dynamically learned one. • Dynamic entries—Dynamic entries can be manually configured or dynamically learned in order to forward frames with a specific destination MAC address out of their associated interfaces and might age out.
Type Description • Learns the MAC address of the frame entered on a different interface from Dynamic MAC address entry that in the entry and overwrites the original entry. • Forwards the frame entered on the same interface with that in the entry and updates the aging timer for the entry. Adding or modifying a static or dynamic MAC address entry globally Step Command Remarks N/A 1. Enter system view. system-view 2. Add or modify a static or dynamic MAC address entry.
Adding or modifying a multiport unicast MAC address entry You can configure a multiport unicast MAC address entry to associate a unicast destination MAC address with multiple ports, so that the frame with a destination MAC address matching the entry is forwarded out of multiple ports. For example, in NLB unicast mode, all servers within the cluster uses the cluster's MAC address as their own address, and frames destined for the cluster are forwarded to every server.
Step Command Remarks • Enter Layer 2 Ethernet interface 2. Enter interface view. view: interface interface-type interface-number • Enter Layer 2 aggregate N/A interface view: interface bridge-aggregation interface-number By default, no multiport unicast MAC address entry is configured on an interface. 3. Add the interface to a multiport unicast MAC address entry. mac-address multiport mac-address vlan vlan-id Make sure you have created the VLAN and assigned the interface to the VLAN.
Step 1. Enter system view. Command Remarks system-view N/A • Enter Layer 2 Ethernet interface 2. Enter interface view. view: interface interface-type interface-number • Enter Layer 2 aggregate interface N/A view: interface bridge-aggregation interface-number 3. Disable MAC address learning on the interface. undo mac-address mac-learning enable By default, MAC address learning on the interface is enabled.
To avoid unnecessary floods and improve forwarding speed, make sure all cards possess the same MAC address table. After you enable MAC address table synchronization, each card advertises learned MAC address entries to other cards of all member devices. (In IRF mode.) As shown in Figure 3, Device A and Device B form an IRF fabric enabled with MAC address synchronization. They connect to AP C and AP D, respectively.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enable MAC address synchronization. mac-address mac-roaming enable By default, MAC address synchronization is disabled. Displaying and maintaining the MAC address table Execute display commands in any view. Task Command Display MAC address table information.
# Set the aging timer for dynamic MAC address entries to 500 seconds. [Device] mac-address timer aging 500 Verifying the configuration # Display the static MAC address entry for interface FortyGigE 1/0/1. [Device] display mac-address static interface fortygige 1/0/1 MAC Address VLAN ID State Port/NickName 000f-e235-dc71 1 Static FGE1/0/1 Aging N # Display information about the blackhole MAC address entries.
Configuring MAC Information The MAC Information feature can generate syslog messages or SNMP notifications when MAC address entries are learned or deleted. You can use these messages to monitor users leaving or joining the network and analyze network traffic. The MAC Information feature buffers the MAC change syslog messages or SNMP notifications in a queue.
Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the MAC Information mode. mac-address information mode { syslog | trap } Optional. The default setting is trap. Configuring the MAC change sending interval To prevent syslog messages or SNMP notifications from being sent too frequently, you can set the MAC change sending interval. To set the MAC change sending interval: Step Command Remarks 1. Enter system view. system-view N/A 2. Set the MAC change sending interval.
Figure 5 Network diagram Configuration restrictions and guidelines When you edit the file /etc/syslog.conf, follow these restrictions and guidelines: • Comments must be on a separate line and must begin with a pound sign (#). • No redundant spaces are allowed after the file name. • The logging facility name and the severity level specified in the /etc/syslog.conf file must be identical to those configured on the device by using the info-center loghost and info-center source commands.
# touch /var/log/Device/info.log c. Edit the file syslog.conf in directory /etc/ and add the following contents: # Device configuration messages local4.info /var/log/Device/info.log In this configuration, local4 is the name of the logging facility that the log host uses to receive logs, and info is the informational level. The UNIX system records the log information that has a severity level of at least informational to the file /var/log/Device/info.log. d.
Configuring Ethernet link aggregation Ethernet link aggregation bundles multiple physical Ethernet links into one logical link, called an aggregate link. Link aggregation has the following benefits: • Increased bandwidth beyond the limits of any single link. In an aggregate link, traffic is distributed across the member ports. • Improved link reliability. The member ports dynamically back up one another. When a member port fails, its traffic is automatically switched to other member ports.
• Unselected—An Unselected port cannot forward traffic. Operational key When aggregating ports, the system automatically assigns each port an operational key based on port information, such as port rate and duplex mode. Any change to this information triggers a recalculation of the operational key. In an aggregation group, all Selected ports are assigned the same operational key. Configuration types Every configuration setting on a port might affect its aggregation state.
• Dynamic aggregation mode—The peering system automatically maintains the aggregation state of the member ports, thus reducing the workload of administrators. An aggregation group in static mode is called a "static aggregation group" and an aggregation group in dynamic mode is called a "dynamic aggregation group.
Figure 7 Setting the aggregation state of a member port in a static aggregation group The maximum number of Selected ports in a static aggregation group is 16. To ensure stable aggregation state and service continuity, do not change port attributes or class-two configurations on any member port. If you need to make this change, make sure you understand its impact on the live network.
LACP functions LACP offers basic LACP functions and extended LACP functions, as described in Table 3. Table 3 Basic and extended LACP functions Category Description Basic LACP functions Implemented through the basic LACPDU fields, including the system LACP priority, system MAC address, port priority, port number, and operational key. Extended LACP functions Implemented by extending the LACPDU with new TLV fields. This is how the LACP MAD mechanism of the IRF feature is implemented.
The local system (the actor) and the remote system (the partner) negotiate a reference port by using the following workflow: 1. The systems compare their system IDs. (A system ID contains the system LACP priority and the system MAC address.) The lower the LACP priority, the smaller the system ID. If LACP priority values are the same, the two systems compare their MAC addresses. The lower the MAC address, the smaller the system ID. 2.
Figure 8 Setting the state of a member port in a dynamic aggregation group Meanwhile, the system with the higher system ID, being aware of the aggregation state changes on the remote system, sets the aggregation state of local member ports the same as their peer ports. When you aggregate interfaces in dynamic mode, follow these guidelines: • The maximum number of Selected ports in a dynamic aggregation group is 16.
A port that joins a dynamic aggregation group after the Selected port limit has been reached is placed in Selected state if it is more eligible to be selected than a current member port. • Load sharing criteria for link aggregation groups In a link aggregation group, traffic may be load-shared across the selected member ports based on a set of criteria, depending on your configuration.
• Removing an aggregate interface also removes its aggregation group and causes all member ports to leave the aggregation group. • You must configure the same aggregation mode on the two ends of an aggregate link. Configuring a Layer 2 static aggregation group To guarantee a successful static aggregation, make sure that the ports at both ends of each link are in the same aggregation state. Avoid assigning ports to a static aggregation group that has reached the limit on Selected ports.
Step Command Remarks 3. Create a Layer 2 aggregate interface and enter Layer 2 aggregate interface view. interface bridge-aggregation interface-number When you create a Layer 2 aggregate interface, the system automatically creates a Layer 2 static aggregation group numbered the same. 4. Configure the aggregation group to operate in dynamic aggregation mode. link-aggregation mode dynamic By default, an aggregation group operates in static aggregation mode. Exit to system view. quit N/A 5.
Step Configure the description of the aggregate interface. 3. Command Remarks description text By default, the description of an interface is in the format of interface-name Interface. Specifying ignored VLANs on a Layer 2 aggregate interface By default, the member ports cannot become Selected ports when the permit state and tagging mode of each VLAN are not same for the member ports and the Layer 2 aggregate interface.
only one Selected port is allowed in the aggregation group at any point in time, while the Unselected port serves as a backup port. To set the minimum and maximum numbers of Selected ports for an aggregation group: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 aggregate interface view. interface bridge-aggregation interface-number N/A 3. Set the minimum number of Selected ports for the aggregation group.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 aggregate interface view. interface bridge-aggregation interface-number N/A 3. Shut down the aggregate interface. shutdown By default, aggregate interfaces are up. Restoring the default settings for an aggregate interface You can return all configurations on an aggregate interface to default settings. To restore the default settings for an aggregate interface: Step Command 1. Enter system view. system-view 2.
• Destination IP address • Source MAC address • Destination MAC address • Source IP address and destination IP address • Source IP address and source port • Destination IP address and destination port • Source IP address, source port, destination IP address, and destination port • Any combination of ingress port, source MAC address, and destination MAC address Enabling local-first load sharing for link aggregation Use the local-first load sharing mechanism in a multi-device link aggregation
NOTE: Local-first load sharing for link aggregation takes effect on only known unicast packets. Enabling link-aggregation traffic redirection Link-aggregation traffic redirection prevents traffic interruption. With this feature, when you restart a card that contains Selected ports, traffic can be redirected to other cards. (In standalone mode.
Task Command Display the global or group-specific link-aggregation load sharing criteria. display link-aggregation load-sharing mode [ interface [ bridge-aggregation interface-number ] ] Display detailed link aggregation information for link aggregation member ports. display link-aggregation member-port [ interface-list ] Display summary information about all aggregation groups. display link-aggregation summary Display detailed information about specific or all aggregation groups.
# Create VLAN 20, and assign port FortyGigE 1/0/5 to VLAN 20. [DeviceA] vlan 20 [DeviceA-vlan20] port fortygige 1/0/5 [DeviceA-vlan20] quit # Create Layer 2 aggregate interface Bridge-Aggregation 1. [DeviceA] interface bridge-aggregation 1 [DeviceA-Bridge-Aggregation1] quit # Assign ports FortyGigE 1/0/1 through FortyGigE 1/0/3 to link aggregation group 1.
Layer 2 dynamic aggregation configuration example Network requirements As shown in Figure 11, configure a Layer 2 dynamic aggregation group on both Device A and Device B, enable VLAN 10 at one end of the aggregate link to communicate with VLAN 10 at the other end, and VLAN 20 at one end to communicate with VLAN 20 at the other end. Figure 11 Network diagram Configuration procedure 1. Configure Device A: # Create VLAN 10, and assign the port FortyGigE 1/0/4 to VLAN 10.
[DeviceA-FortyGigE1/0/3] quit # Configure Layer 2 aggregate interface Bridge-Aggregation 1 as a trunk port and assign it to VLANs 10 and 20. [DeviceA] interface bridge-aggregation 1 [DeviceA-Bridge-Aggregation1] port link-type trunk [DeviceA-Bridge-Aggregation1] port trunk permit vlan 10 20 [DeviceA-Bridge-Aggregation1] quit 2. Configure Device B in the same way Device A is configured. Verifying the configuration # Display detailed information about all aggregation groups on Device A.
Figure 12 Network diagram Configuration procedure 1. Configure Device A: # Create VLAN 10, and assign the port FortyGigE 1/0/5 to VLAN 10. system-view [DeviceA] vlan 10 [DeviceA-vlan10] port fortygige 1/0/5 [DeviceA-vlan10] quit # Create VLAN 20, and assign the port FortyGigE 1/0/6 to VLAN 20. [DeviceA] vlan 20 [DeviceA-vlan20] port fortygige 1/0/6 [DeviceA-vlan20] quit # Create Layer 2 aggregate interface Bridge-Aggregation 1.
[DeviceA-FortyGigE1/0/3] port link-aggregation group 2 [DeviceA-FortyGigE1/0/3] quit [DeviceA] interface fortygige 1/0/4 [DeviceA-FortyGigE1/0/4] port link-aggregation group 2 [DeviceA-FortyGigE1/0/4] quit # Configure Layer 2 aggregate interface Bridge-Aggregation 2 as a trunk port and assign it to VLAN 20.
Bridge-Aggregation2 Load-Sharing Mode: source-mac address The output shows that the load sharing criteria for both link aggregation group 1 and link aggregation group 2 are the source MAC addresses of packets.
Configuring port isolation The port isolation feature isolates Layer 2 traffic for data privacy and security without using VLANs. You can also use this feature to isolate the hosts in a VLAN from one another. You can manually create isolation groups on the switch, but only the isolation group numbered 1 is valid. The number of ports assigned to an isolation group is not limited. Within the same VLAN, ports in an isolation group can communicate with those outside the isolation group at Layer 2.
Port isolation configuration example Network requirements As shown in Figure 13, LAN users Host A, Host B, and Host C are connected to FortyGigE 1/0/1, FortyGigE 1/0/2, and FortyGigE 1/0/3 on the device, respectively. The device connects to the Internet through FortyGigE 1/0/4. Configure the device to provide Internet access for the hosts, and isolate them from one another at Layer 2. Figure 13 Network diagram Configuration procedure # Create isolation group 1.
Group ID: 1 Group members: FortyGigE1/0/1 FortyGigE1/0/2 FortyGigE1/0/3 54
Configuring spanning tree protocols Spanning tree protocols eliminate loops in a physical link-redundant network by selectively blocking redundant links and putting them in a standby state. The recent versions of STP include the Rapid Spanning Tree Protocol (RSTP) and the Multiple Spanning Tree Protocol (MSTP). STP STP was developed based on the 802.1d standard of IEEE to eliminate loops at the data link layer in a LAN.
Basic concepts in STP Root bridge A tree network must have a root bridge. The entire network contains only one root bridge, and all the other bridges in the network are called "leaf nodes". The root bridge is not permanent, but can change with changes of the network topology. Upon initialization of a network, each device generates and periodically sends configuration BPDUs, with itself as the root bridge. After network convergence, only the root bridge generates and periodically sends configuration BPDUs.
Calculation process of the STP algorithm The spanning tree calculation process described in the following sections is a simplified process for example only. Calculation process The STP algorithm uses the following calculation process: 1. Network initialization. Upon initialization of a device, each port generates a BPDU with the port as the designated port, the device as the root bridge, 0 as the root path cost, and the device ID as the designated bridge ID. 2. Root bridge selection.
Step Actions 2 The device compares the configuration BPDUs of all the ports and chooses the optimum configuration BPDU. The following are the principles of configuration BPDU comparison: a. The configuration BPDU with the lowest root bridge ID has the highest priority. b. If configuration BPDUs have the same root bridge ID, their root path costs are compared. For example, the root path cost in a configuration BPDU plus the path cost of a receiving port is S.
Device Device C 2. Port name Configuration BPDU on the port Port B2 {1, 0, 1, Port B2} Port C1 {2, 0, 2, Port C1} Port C2 {2, 0, 2, Port C2} Configuration BPDUs comparison on each device. In Table 7, each configuration BPDU contains the following fields: root bridge ID, root path cost, designated bridge ID, and designated port ID.
Device Configuration BPDU on ports after comparison Comparison process • Port C1 receives the configuration BPDU of Port A2 {0, 0, 0, Port A2}, finds that the received configuration BPDU is superior to its existing configuration BPDU {2, 0, 2, Port C1}, and updates its configuration BPDU.
Figure 16 The final calculated spanning tree The configuration BPDU forwarding mechanism of STP The configuration BPDUs of STP are forwarded according to these guidelines: • Upon network initiation, every device regards itself as the root bridge, generates configuration BPDUs with itself as the root, and sends the configuration BPDUs at a regular hello interval.
RSTP RSTP achieves rapid network convergence by allowing a newly elected root port or designated port to enter the forwarding state much faster than STP. If the old root port on the device has stopped forwarding data and the upstream designated port has started forwarding data, a newly elected RSTP root port rapidly enters the forwarding state.
Figure 17 Basic concepts in MSTP VLAN 1 MSTI 1 MSTI 2 VLAN 2 MSTI 0 Other VLANs VLAN 1 MSTI 1 MSTI 2 VLAN 2 MSTI 0 Other VLANs MST region 1 MST region 4 MST region 2 MST region 3 VLAN 1 MSTI 1 MSTI 2 VLAN 2 MSTI 0 Other VLANs CST VLAN 1 MSTI 1 MSTI 2 VLAN 2&3 MSTI 0 Other VLANs To MST region 2 Figure 18 Network diagram and topology of MST region 3 MST region A multiple spanning tree region (MST region) consists of multiple devices in a switched network and the network segments among them.
• Same VLAN-to-instance mapping configuration • Same MSTP revision level • Physically linked together Multiple MST regions can exist in a switched network. You can assign multiple devices to the same MST region. In Figure 17, the switched network comprises four MST regions, MST region 1 through MST region 4, and all devices in each MST region have the same MST region configuration.
Port roles A port can play different roles in different MSTIs. As shown in Figure 19, an MST region comprises Device A, Device B, Device C, and Device D. Port A1 and port A2 of Device A connect to the common root bridge. Port B2 and Port B3 of Device B form a loop. Port C3 and Port C4 of Device C connect to other MST regions. Port D3 of Device D directly connects to a host.
• Forwarding—The port receives and sends BPDUs, learns MAC addresses, and forwards user traffic. • Learning—The port receives and sends BPDUs, learns MAC addresses, but does not forward user traffic. Learning is an intermediate port state. • Discarding—The port receives and sends BPDUs, but does not learn MAC addresses or forward user traffic. NOTE: When in different MSTIs, a port can be in different states. A port state is not exclusively associated with a port role.
MSTP implementation on devices MSTP is compatible with STP and RSTP. Devices that are running MSTP and that are used for spanning tree calculation can identify STP and RSTP protocol packets.
Though the member ports of an aggregation group do not participate in spanning tree calculation, the ports still reserve their spanning tree configurations for participating in spanning tree calculation after leaving the aggregation group. • STP configuration task list Tasks at a glance Configuring the root bridge: • • • • • • • • • (Required.) Setting the spanning tree mode (Optional.) Configuring the root bridge or a secondary root bridge (Optional.) Configuring the device priority (Optional.
Tasks at a glance Configuring the leaf nodes: • • • • • • • • • • (Required.) Setting the spanning tree mode (Optional.) Configuring the device priority (Optional.) Configuring the timeout factor (Optional.) Configuring the BPDU transmission rate (Optional.) Configuring edge ports (Optional.) Configuring path costs of ports (Optional.) Configuring the port priority (Optional.) Configuring the port link type (Optional.) Enabling outputting port state transition information (Required.
Tasks at a glance Configuring the leaf nodes: • • • • • • • • • • • • (Required.) Setting the spanning tree mode (Required.) Configuring an MST region (Optional.) Configuring the device priority (Optional.) Configuring the timeout factor (Optional.) Configuring the BPDU transmission rate (Optional.) Configuring edge ports (Optional.) Configuring path costs of ports (Optional.) Configuring the port priority (Optional.) Configuring the port link type (Optional.
NOTE: • In STP or RSTP mode, do not specify an MSTI. Otherwise, the spanning tree configuration does not take effect. • In MSTP mode, if you specify an MSTI, the spanning tree configuration takes effect on the specified MSTI. If you do not specify an MSTI, the spanning tree configuration takes effect on the CIST.
Configuring the root bridge or a secondary root bridge You can have the spanning tree protocol determine the root bridge of a spanning tree through MSTP calculation, or you can specify the current device as the root bridge or as a secondary root bridge. A device has independent roles in different spanning trees. It can act as the root bridge in one spanning tree and as a secondary root bridge in another. However, one device cannot be the root bridge and a secondary root bridge in the same spanning tree.
Configuring the device priority Device priority is a factor in calculating the spanning tree. The priority of a device determines whether the device can be elected as the root bridge of a spanning tree. A lower value indicates a higher priority. You can set the priority of a device to a low value to specify the device as the root bridge of the spanning tree. A spanning tree device can have different priorities in different MSTIs.
devices. The network diameter is a parameter that indicates the network size. A bigger network diameter indicates a larger network size. Based on the network diameter you configured, the system automatically sets an optimal hello time, forward delay, and max age for the device. Each MST region is considered a device and the configured network diameter is effective only on the CIST (or the common root bridge) but not on other MSTIs.
loss for a link failure and triggers a new spanning tree calculation process. If the hello time is too short, the device frequently sends the same configuration BPDUs, which waste device and network resources. HP recommends using the default setting. If the max age timer is too short, the device frequently begins spanning tree calculations and might mistake network congestion as a link failure.
Configuring the BPDU transmission rate The maximum number of BPDUs a port can send within each hello time equals the BPDU transmission rate plus the hello timer value. Configure an appropriate BPDU transmission rate based on the physical status of the port and the network structure. The higher the BPDU transmission rate, the more BPDUs are sent within each hello time, and the more system resources are used.
Configuring path costs of ports Path cost is a parameter related to the rate of a port. On a spanning tree device, a port can have different path costs in different MSTIs. Setting appropriate path costs allows VLAN traffic flows to be forwarded along different physical links, achieving VLAN-based load balancing. You can have the device automatically calculate the default path cost, or you can configure the path cost for ports.
Table 9 Mappings between the link speed and the path cost Path cost Link speed Port type IEEE 802.1d-1998 IEEE 802.
Step Command • In STP/RSTP mode: 3. Configure the path cost of the ports. stp cost cost • In MSTP mode: stp [ instance instance-list ] cost cost Remarks By default, the system automatically calculates the path cost of each port. NOTE: When the path cost of a port changes, the system re-calculates the role of the port and initiates a state transition. Configuration example # In MSTP mode, configure the device to calculate the default path costs of its ports by using IEEE 802.
Configuring the port link type A point-to-point link directly connects two devices. If two root ports or designated ports are connected over a point-to-point link, they can rapidly transit to the forwarding state after a proposal-agreement handshake process. Configuration restrictions and guidelines • You can configure the link type as point-to-point for a Layer 2 aggregate interface or a port that operates in full duplex mode.
A port in auto mode sends 802.1s MSTP packets by default. When the port receives an MSTP packet of a legacy format, the port starts to send packets only of the legacy format. This prevents the port from frequently changing the format of sent packets. To configure the port to send 802.1s MSTP packets, shut down and then bring up the port. To configure the MSTP packet format to be supported on a port: Step Command Remarks 1. Enter system view. system-view N/A 2.
Step Command Remarks • If the device starts up with the initial settings (or empty configuration), the spanning tree feature is disabled globally. 2. Enable the spanning tree feature. • If the device starts up with the default configuration file (or factory defaults), the spanning tree feature is enabled globally. stp global enable For more information about the startup configuration, see Fundamentals Configuration Guide. 3. 4. Enter Layer 2 Ethernet or aggregate interface view.
Step Command 2. Enter Layer 2 Ethernet or aggregate interface view. interface interface-type interface-number 3. Perform mCheck. stp mcheck NOTE: An mCheck operation takes effect on a device that operates in MSTP or RSTP mode. Configuring Digest Snooping As defined in IEEE 802.1s, connected devices are in the same region only when their MST region-related configurations (region name, revision level, and VLAN-to-instance mappings) are identical.
Configuration procedure You can enable Digest Snooping only on the HP device that is connected to a third-party device that uses its private key to calculate the configuration digest. To configure Digest Snooping: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet or aggregate interface view. interface interface-type interface-number N/A 3. Enable Digest Snooping on the interface. stp config-digest-snooping By default, Digest Snooping is disabled on ports. 4.
[DeviceA] interface fortygige 1/0/1 [DeviceA-FortyGigE1/0/1] stp config-digest-snooping [DeviceA-FortyGigE1/0/1] quit [DeviceA] stp global config-digest-snooping # Enable Digest Snooping on FortyGigE 1/0/1 of Device B and enable global Digest Snooping on Device B.
Figure 22 Rapid state transition of an RSTP designated port If the upstream device is a third-party device, the rapid state transition implementation might be limited. For example, when the upstream device uses a rapid transition mechanism similar to that of RSTP, and the downstream device adopts MSTP and does not operate in RSTP mode, the root port on the downstream device receives no agreement packet from the upstream device and sends no agreement packets to the upstream device.
No Agreement Check configuration example Network requirements As shown in Figure 23: • Device A connects to a third-party device that has a different spanning tree implementation. Both devices are in the same region. • The third-party device (Device B) is the regional root bridge, and Device A is the downstream device. Figure 23 Network diagram Configuration procedure # Enable No Agreement Check on FortyGigE 1/0/1 of Device A.
protocol. The device reactivates the closed ports after a detection interval. For more information about this detection interval, see Fundamentals Configuration Guide. BPDU guard does not take effect on loopback-testing-enabled ports. For more information about loopback testing, see "Configuring Ethernet interfaces." Configure BPDU guard on a device with edge ports configured. To enable BPDU guard: Step Command Remarks 1. Enter system view. system-view N/A 2.
forwarding state, resulting in loops in the switched network. The loop guard function can suppress the occurrence of such loops. The initial state of a loop guard-enabled port is discarding in every MSTI. When the port receives BPDUs, it transits its state. Otherwise, it stays in the discarding state to prevent temporary loops. Do not enable loop guard on a port that connects user terminals. Otherwise, the port stays in the discarding state in all MSTIs because it cannot receive BPDUs.
Configuring TC-BPDU transmission restriction CAUTION: Enabling TC-BPDU transmission restriction on a port might cause the previous forwarding address table to fail to be updated when the topology changes. The topology change to the user access network might cause the forwarding address changes to the core network. When the user access network topology is unstable, the user access network might affect the core network. To avoid this problem, you can enable TC-BPDU transmission restriction on a port.
Displaying and maintaining the spanning tree Execute display commands in any view and reset command in user view. Task Command Display information about ports blocked by spanning tree protection functions. display stp abnormal-port Display BPDU statistics on ports. display stp bpdu-statistics [ interface interface-type interface-number [ instance instance-list ] ] Display information about ports shut down by spanning tree protection functions.
VLAN 10 and VLAN 30 are terminated on the distribution layer devices, and VLAN 40 is terminated on the access layer devices. The root bridges of MSTI 1 and MSTI 3 are Device A and Device B, respectively, and the root bridge of MSTI 4 is Device C.
3. Configure Device B: # Enter MST region view, and configure the MST region name as example. system-view [DeviceB] stp region-configuration [DeviceB-mst-region] region-name example # Map VLAN 10, VLAN 30, and VLAN 40 to MSTI 1, MSTI 3, and MSTI 4, respectively. [DeviceB-mst-region] instance 1 vlan 10 [DeviceB-mst-region] instance 3 vlan 30 [DeviceB-mst-region] instance 4 vlan 40 # Configure the revision level of the MST region as 0.
# Configure the revision level of the MST region as 0. [DeviceD-mst-region] revision-level 0 # Activate MST region configuration. [DeviceD-mst-region] active region-configuration [DeviceD-mst-region] quit # Enable the spanning tree feature globally. [DeviceD] stp global enable Verifying the configuration In this example, suppose that Device B has the lowest root bridge ID. As a result, Device B is elected as the root bridge in MSTI 0.
MSTID Port Role STP State Protection 0 FortyGigE1/0/1 ROOT FORWARDING NONE 0 FortyGigE1/0/2 ALTE DISCARDING NONE 0 FortyGigE1/0/3 ALTE DISCARDING NONE 3 FortyGigE1/0/1 ROOT FORWARDING NONE 3 FortyGigE1/0/2 ALTE DISCARDING NONE 4 FortyGigE1/0/3 ROOT FORWARDING NONE Based on the output, you can draw each MSTI mapped to each VLAN, as shown in Figure 25.
Configuring loop detection Overview Incorrect network connections or configurations can create Layer 2 loops, which results in repeated transmission of broadcasts, multicasts, or unknown unicasts, waste network resources, and sometimes even paralyze networks. The loop detection mechanism immediately generates a log when a loop occurs so that you are promptly notified to adjust network connections and configurations. You can even configure loop detection to shut down the looped port.
• Version—Protocol version, which is always 0x0000. • Length—Length of the frame. The value includes the inner header, but excludes the Ethernet header. • Reserved—This field is reserved. Frames for loop detection are encapsulated as TLV triplets. Table 10 TLVs supported by loop detection TLV Description Remarks End of PDU End of a PDU. Optional. Device ID Bridge MAC address of the sending device. Required. Port ID ID of the PDU sending port. Optional.
Loop detection configuration task list Tasks at a glance (Required.) Enabling loop detection (Optional.) Configuring the loop protection action (Optional.) Setting the loop detection interval Enabling loop detection You can enable loop detection globally or on specific ports. The global configuration applies to all ports in the specified VLAN. The per-port configuration applies to the individual port only when the port belongs to the specified VLAN.
Configuring the global loop protection action Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the global loop protection action. loopback-detection global action shutdown By default, the device generates a log but performs no action on the port on which a loop is detected. Configuring the loop protection action on a Layer 2 Ethernet interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet interface view.
Step Command Remarks 1. Enter system view. system-view N/A 2. Set the loop detection interval. loopback-detection interval-time interval The default setting is 30 seconds. Displaying and maintaining loop detection Execute display commands in any view. Task Command Display the loop detection configuration and status.
[DeviceA] loopback-detection global enable vlan 100 # Configure FortyGigE 1/0/1 and FortyGigE 1/0/2 as trunk ports, and assign them to VLAN 100.
Verifying the configuration After the configurations are complete, Device A detects loops on ports FortyGigE 1/0/1 and FortyGigE 1/0/2 within a loop detection interval. Consequently, Device A automatically shuts down the ports and generates the following log messages: [DeviceA] %Feb 24 15:04:29:663 2011 DeviceA LPDT/4/LOOPED:Slot=1; Loopback exists on FortyGigE 1/0/1. %Feb 24 15:04:29:667 2011 DeviceA LPDT/4/LOOPED:Slot=1; Loopback exists on FortyGigE 1/0/2.
Configuring VLANs This chapter provides an overview of VLANs and explains how to configure them. Overview Ethernet is a family of shared-media LAN technologies based on the CSMA/CD mechanism. An Ethernet LAN is both a collision domain and a broadcast domain. Because the medium is shared, collisions and broadcasts are common in an Ethernet LAN. Typically, bridges and Layer 2 switches can reduce collisions in an Ethernet LAN.
Figure 30 VLAN tag placement and format A VLAN tag includes the following fields: • TPID—16-bit tag protocol identifier that indicates whether a frame is VLAN-tagged. By default, the TPID value is 0x8100, indicating that the frame is VLAN-tagged. However, device vendors can set TPID to different values. For compatibility with neighbor devices, configure the TPID value on the device to be the same as the neighbor device. • Priority—3-bit long 802.1p priority of the frame.
Step Configure the description of the VLAN. 5. Command Remarks description text The default setting is VLAN vlan-id, which is the ID of the VLAN. For example, the description of VLAN 100 is VLAN 0100 by default. NOTE: • As the system default VLAN, VLAN 1 cannot be created or removed. • You cannot use the undo vlan command to delete a dynamic VLAN, a VLAN with a QoS policy applied, or a VLAN locked by an application. To delete such a VLAN, first remove the configuration from the VLAN.
Step Command Remarks 7. Configure the expected bandwidth of the interface. bandwidth bandwidth-value By default, the expected bandwidth (in kbps) is the interface baud rate divided by 1000. 8. (Optional.) Restore the default settings for the VLAN interface. default N/A undo shutdown By default, a VLAN interface is not manually shut down. The VLAN interface is up if one or more ports in the VLAN is up, and goes down if all ports in the VLAN go down. 9. (Optional.
Make sure a port is assigned to its PVID. Otherwise, when the port receives frames tagged with the PVID or untagged frames, the port filters out these frames. • How ports of different link types handle frames Actions Access In the inbound direction for an untagged frame Tags the frame with the PVID tag. In the inbound direction for a tagged frame Trunk Hybrid • If the PVID is permitted on the port, tags the frame with the PVID tag. • If not, drops the frame.
Step Command Remarks • The configuration made in Layer 2 Ethernet interface view applies only to the port. • Enter Layer 2 Ethernet interface view: interface interface-type interface-number Enter interface view. 2. • Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number • The configuration made in Layer 2 aggregate interface view applies to the aggregate interface and its aggregation member ports.
Step Command Remarks • The configuration made in Layer 2 Ethernet interface view applies only to the port. • The configuration made in • Enter Layer 2 Ethernet interface Enter interface view. 2. view: interface interface-type interface-number • Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number Layer 2 aggregate interface view applies to the aggregate interface and its aggregation member ports.
Step Command Remarks • The configuration made in Layer 2 Ethernet interface view applies only to the port. • The configuration made in • Enter Layer 2 Ethernet interface 2. Enter interface view. view: interface interface-type interface-number • Enter Layer 2 aggregate interface view: interface bridge-aggregation interface-number Layer 2 aggregate interface view applies to the aggregate interface and its aggregation member ports.
• Host A and Host C belong to Department A. VLAN 100 is assigned to Department A. • Host B and Host D belong to Department B. VLAN 200 is assigned to Department B. Configure port-based VLANs so that hosts only in the same department can communicate with each other. Figure 31 Network diagram Configuration procedure 1. Configure Device A: # Create VLAN 100, and assign FortyGigE 1/0/1 to VLAN 100.
VLAN ID: 100 VLAN type: Static Route interface: Not configured Description: VLAN 0100 Name: VLAN 0100 Tagged ports: FortyGigE1/0/3 Untagged ports: FortyGigE1/0/1 [DeviceA-FortyGigE1/0/3] display vlan 200 VLAN ID: 200 VLAN type: Static Route interface: Not configured Description: VLAN 0200 Name: VLAN 0200 Tagged ports: FortyGigE1/0/3 Untagged ports: FortyGigE1/0/2 112
Configuring LLDP You can set an Ethernet port as a Layer 3 interface by using the port link-mode route command (see "Configuring Ethernet interfaces"). Overview In a heterogeneous network, a standard configuration exchange platform ensures that different types of network devices from different vendors can discover one another and exchange configuration for the sake of interoperability and management. The Link Layer Discovery Protocol (LLDP) is specified in IEEE 802.1AB.
LLDPDU formats LLDP sends device information in LLDPDUs. LLDPDUs are encapsulated in Ethernet II or SNAP frames. 1. LLDPDU encapsulated in Ethernet II Figure 33 Ethernet II-encapsulated LLDPDU Table 11 Fields in an Ethernet II-encapsulated LLDPDU Field Description Destination MAC address MAC address to which the LLDPDU is advertised.
Table 12 Fields in a SNAP-encapsulated LLDPDU Field Description Destination MAC address MAC address to which the LLDPDU is advertised. It is the same as that for Ethernet II-encapsulated LLDPDUs. Source MAC address MAC address of the sending port. Type SNAP type for the upper layer protocol. It is 0xAAAA-0300-0000-88CC for LLDP. Data LLDPDU. FCS Frame check sequence, a 32-bit CRC value used to determine the validity of the received Ethernet frame.
Type Description Time to Live Specifies the life of the transmitted information on the receiving device. End of LLDPDU Marks the end of the TLV sequence in the LLDPDU. Port Description Specifies the port description of the sending port. System Name Specifies the assigned name of the sending device. System Description Specifies the description of the sending device. System Capabilities Identifies the primary functions of the sending device and the enabled primary functions.
Table 15 IEEE 802.3 organizationally specific TLVs Type Description MAC/PHY Configuration/Status Contains the bit-rate and duplex capabilities of the sending port, support for autonegotiation, enabling status of autonegotiation, and the current rate and duplex mode. Power Via MDI Contains the power supply capability of the port, including the PoE type (PSE or PD), PoE mode, whether PSE power supply is supported, whether PSE power supply is enabled, and whether the PoE mode is controllable.
Type Description Location Identification Allows a network device to advertise the appropriate location identifier information for a terminal device to use in the context of location-based applications. NOTE: If the MAC/PHY configuration/status TLV is not advertisable, none of the LLDP-MED TLVs will be advertised even if they are advertisable. If the LLDP-MED capabilities TLV is not advertisable, the other LLDP-MED TLVs will not be advertised even if they are advertisable.
Receiving LLDPDUs An LLDP agent that is operating in TxRx mode or Rx mode checks the validity of TLVs carried in every received LLDPDU. If valid, the information is saved and an aging timer is set for it based on the TTL value in the TTL TLV carried in the LLDPDU. If the TTL value is zero, the information ages out immediately. Protocols and standards • IEEE 802.1AB-2005, Station and Media Access Control Connectivity Discovery • IEEE 802.
Step 3. 4. Command Remarks Enter Layer 2 or Layer 3 Ethernet interface view or Layer 2 aggregate interface view. interface interface-type interface-number N/A (Optional.) Enable LLDP. lldp enable By default, LLDP is enabled on a port. Configuring the LLDP bridge mode The following LLDP bridge modes are available: service bridge mode and customer bridge mode. • In service bridge mode, LLDP supports nearest bridge agents and nearest non-TPMR bridge agents.
Step Command Remarks • In Layer 2 or Layer 3 Ethernet interface 3. Set the LLDP operating mode. view: lldp [ agent { nearest-customer | nearest-nontpmr } ] admin-status { disable | rx | tx | txrx } • In Layer 2 aggregate interface view: lldp agent { nearest-customer | nearest-nontpmr } admin-status { disable | rx | tx | txrx } By default, the nearest bridge agent operates in txrx mode, and the nearest customer bridge agent and nearest non-TPMR bridge agent operate in disable mode.
Step Command Remarks • In Layer 2 or Layer 3 Ethernet interface 3. Enable LLDP polling and set the polling interval. view: lldp [ agent { nearest-customer | nearest-nontpmr } ] check-change-interval interval • In Layer 2 aggregate interface view: By default, LLDP polling is disabled. lldp agent { nearest-customer | nearest-nontpmr } check-change-interval interval Configuring the advertisable TLVs Step Command Remarks 1. Enter system view. system-view N/A 2.
Step 4. Configure the advertisable TLVs (in Layer 3 Ethernet interface view).
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 or Layer 3 Ethernet interface view or Layer 2 aggregate interface view. interface interface-type interface-number N/A • In Layer 2 or Layer 3 Ethernet 3. Allow LLDP to advertise the management address in LLDPDUs and configure the advertised management address.
Step Command Remarks 3. Set the LLDPDU transmit interval. lldp timer tx-interval interval The default setting is 30 seconds. 4. Set the token bucket size for sending LLDPDUs. lldp max-credit credit-value The default setting is 5. 5. Set the LLDPDU transmit delay. lldp timer tx-delay delay The default setting is 2 seconds. 6. Set the number of LLDPDUs sent each time fast LLDPDU transmission is triggered. lldp fast-count count The default setting is 4.
device. The packets that the switch sends to the neighboring CDP device carry the device ID, the ID of the port connecting to the neighboring device, the port IP address, the PVID, and the TTL. The port IP address is the main IP address of the VLAN interface that is in up state and whose corresponding VLAN ID is the lowest among the VLANs permitted on the port.
To configure LLDP trapping and LLDP-MED trapping: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 or Layer 3 Ethernet interface view or Layer 2 aggregate interface view. interface interface-type interface-number N/A • In Layer 2 or Layer 3 Ethernet interface 3. Enable LLDP trapping. view: lldp [ agent { nearest-customer | nearest-nontpmr } ] notification remote-change enable • In Layer 2 aggregate interface view: By default, LLDP trapping is disabled.
LLDP configuration example Network requirements As shown in Figure 36, the NMS and Switch A are located in the same Ethernet network. An MED device and Switch B are connected to FortyGigE1/0/1 and FortyGigE1/0/2 of Switch A. Enable LLDP globally on Switch A and Switch B to monitor the link between Switch A and Switch B and the link between Switch A and the MED device on the NMS. Figure 36 Network diagram MED FGE1/0/1 NMS FGE1/0/2 FGE1/0/1 Switch A Switch B Configuration procedure 1.
[SwitchB-FortyGigE1/0/1] lldp enable # Set the LLDP operating mode to Tx. [SwitchB-FortyGigE1/0/1] lldp admin-status tx [SwitchB-FortyGigE1/0/1] quit Verifying the configuration # Verify that: • FortyGigE1/0/1 of Switch A connects to an MED device. • FortyGigE1/0/2 of Switch A connects to a non-MED device. • Both ports operate in Rx mode, and they can receive LLDPDUs but cannot send LLDPDUs.
Number of sent optional TLV : 16 Number of received unknown TLV : 0 LLDP status information of port 2 [FortyGigE1/0/2]: LLDP agent nearest-bridge: Port status of LLDP : Enable Admin status : RX_Only Trap flag : No MED trap flag : No Polling interval : 0s Number of LLDP neighbors : 1 Number of MED neighbors : 0 Number of CDP neighbors : 0 Number of sent optional TLV : 21 Number of received unknown TLV : 3 LLDP agent nearest-nontpmr: Port status of LLDP : Enable Admin status : Disable
Transmit credit max : 5 Hold multiplier : 4 Reinit delay : 2s Trap interval : 30s Fast start times : 4 LLDP status information of port 1 [FortyGigE1/0/1]: LLDP agent nearest-bridge: Port status of LLDP : Enable Admin status : RX_Only Trap flag : No MED trap flag : No Polling interval : 0s Number of LLDP neighbors : 1 Number of MED neighbors : 1 Number of CDP neighbors : 0 Number of sent optional TLV : 0 Number of received unknown TLV : 5 LLDP agent nearest-nontpmr: Port status o
MED trap flag : No Polling interval : 0s Number of LLDP neighbors : 0 Number of MED neighbors : 0 Number of CDP neighbors : 0 Number of sent optional TLV : 1 Number of received unknown TLV : 0 LLDP agent nearest-customer: Port status of LLDP : Enable Admin status : Disable Trap flag : No MED trap flag : No Polling interval : 0s Number of LLDP neighbors : 0 Number of MED neighbors : 0 Number of CDP neighbors : 0 Number of sent optional TLV : 16 Number of received unknown TLV :
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. [] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x | y | ... } Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features. Represents an access controller, a unified wired-WLAN module, or the switching engine on a unified wired-WLAN switch. Represents an access point.
Index port-based VLAN trunk port, 108 Numerics 802.x 802.1 LLDPDU TLV types, 115 802.
STP secondary root bridge configuration, 72 Ethernet link aggregation group, 37 interface configuration, 15 Ethernet link aggregation group load sharing criteria, 42 interface configuration display, 16 Ethernet link aggregation load sharing, 42 bulk inloopback interface, 12, 13 C Layer 2 Ethernet interface, 8 calculating Layer 2 Ethernet interface storm control, 9 MSTI calculation, 66 Layer 2 Ethernet interface storm suppression, 8 MSTP CIST calculation, 66 Layer 2 Ethernet link aggregation (
Ethernet link aggregate interface default settings, 42 MSTP secondary root bridge, 72 MSTP secondary root bridge device, 72 null interface, 12, 13 designated MST port, 65 port isolation, 52 port isolation (on LAN), 53 STP bridge, 56 RSTP, 55, 67, 91 STP port, 56 RSTP device priority, 73 device Ethernet interface configuration, 1 RSTP root bridge, 72 LLDP basic configuration, 119, 128 RSTP root bridge device, 72 RSTP secondary root bridge, 72 LLDP CDP compatibility, 125 RSTP secondary root bridg
MAC address table, 24 interface. See Ethernet interface MSTP, 91 link aggregation.
basic concepts, 30 frame configuration, 30, 37, 45 Ethernet interface jumbo frame support, 4 configuration types, 31 loop detection, 96 displaying, 44 loop detection (Ethernet frame header), 96 dynamic mode, 33 loop detection (inner frame header), 96 dynamic process, 34 loop detection interval, 97 group configuration, 37 MAC address learning, 17 group load sharing criteria, 42 MAC address table blackhole entry, 19 interface configuration (expected bandwidth), 41 MAC address table configurat
Ethernet link aggregation load sharing criteria, 37 maintaining, 13 Ethernet link aggregation static mode, 32 interface Ethernet link aggregation traffic redirection, 44 bulk configuration, 15 configuring inloopback, 12 Layer 2 configuring loopback, 12 Ethernet aggregate interface (description), 39 configuring null, 12 Ethernet aggregate interface configuration, 39 Ethernet aggregate interface (description), 39 Ethernet link aggregate group min/max number Selected ports, 40 Ethernet aggregate i
LLDPDU format, 114 storm suppression configuration, 8 LLDPDU management address TLV, 118 Layer 3 LLDP basic configuration, 128 LLDPDU reception, 119 LLDP trapping, 126 LLDPDU TLV types, 115 LLDP-MED trapping, 126 LLDPDU TLVs, 115 port-based VLAN access port assignment, 107 LLDPDU transmission, 118 port-based VLAN access port assignment (in interface view), 107 LLDP-MED trapping configuration, 126 port-based VLAN access port assignment (in VLAN view), 107 management address encoding format, 123
entry types, 17 Layer 2 Ethernet link aggregation configuration, 48 MAC address learning disable, 21 local Ethernet link aggregation local-first load sharing, 43 logging manual entries, 17 multiport unicast entry, 20 MAC Information change send interval, 27 loop detection configuration, 96, 98, 100 configuration, 26, 27 loop enable, 26 MSTP configuration, 55, 67, 91 mode configuration, 26 RSTP configuration, 55, 67, 91 STP configuration, 55, 67, 91 STP loop guard, 88 loop detection queue length
LLDP disable, 118, 120 STP max age timer, 74 LLDP Rx, 118, 120 STP port mode configuration, 80 LLDP service bridge mode, 120 VLAN-to-instance mapping table, 64 LLDP Tx, 118, 120 multiport unicast entry (MAC address table), 17, 20 LLDP TxRx, 118, 120 N MAC Information syslog, 26 MAC Information trap, 26 network Ethernet interface basic settings configuration, 3 modifying Ethernet interface common settings configuration, 1 MAC address table blackhole entry, 19 Ethernet interface generic flow co
port-based VLAN access port assignment, 107 LLDP basic concepts, 113 port-based VLAN access port assignment (in interface view), 107 LLDP basic configuration, 119, 128 port-based VLAN access port assignment (in VLAN view), 107 loop detection, 96 port-based VLAN hybrid port assignment, 109 loopback interface configuration, 12 LLDP configuration, 113, 119 loop detection configuration, 98, 100 port-based VLAN trunk port assignment, 108 MAC address table configuration, 17, 18, 24 RSTP mode set, 70 M
Layer 2 Ethernet link aggregation group (static), 38 physical Ethernet interface physical state change suppression, 4 Layer 2 Ethernet link aggregation load sharing, 48 LLDP basic configuration, 119, 128 polling LLDP configuration, 113, 119 LLDP enable, 121 LLDP disable operating mode, 118, 120 Ethernet aggregate interface (description), 39 LLDP operating mode, 120 port LLDP enable, 119 Ethernet aggregate interface configuration, 39 LLDP polling, 121 Ethernet link aggregate group min/max number
configuring Ethernet interface basic settings, 3 STP root guard, 88 STP root port, 56 configuring Ethernet interface common settings, 1 STP TC-BPDU guard, 90 configuring Ethernet interface generic flow control, 5 STP TC-BPDU transmission restriction, 90 configuring Ethernet interface jumbo frame support, 4 VLAN port link type, 106 port isolation configuring Ethernet interface link mode, 4 configuration, 52 configuring Ethernet interface PFC, 6 configuration (on LAN), 53 configuring Ethernet inte
configuring STP protection functions, 87 configuring loop detection protection action (global), 99 configuring STP root bridge, 72 configuring loop detection protection action (Layer 2 aggregate interface), 99 configuring STP root bridge device, 72 configuring STP secondary root bridge, 72 configuring loop detection protection action (Layer 2 Ethernet interface), 99 configuring STP secondary root bridge device, 72 configuring STP switched network diameter, 73 configuring loopback interface, 12 confi
LLDP, 119 enabling STP port state transition information output, 81 MSTP, 67 enabling STP root guard, 88 STP protocol packets, 55 enabling STP TC-BPDU guard, 90 VLAN, 104 maintaining Ethernet interface, 10 maintaining Ethernet link aggregation, 44 maintaining inloopback interface, 13 maintaining loopback interface, 13 maintaining MSTP, 91 maintaining null interface, 13 PVID (port-based VLAN), 106 Q QinQ loop detection configuration, 96, 98, 100 queuing MAC Information queue length, 27 maintaining R
STP root bridge, 56 LLDPDU encapsulated in SNAP format, 114 STP root bridge configuration, 72 STP root guard, 88 LLDPDU encapsulation format, 125 SNMP STP root port, 56 STP secondary root bridge configuration, 72 MAC Information configuration, 26, 27 snooping RSTP, 55, See also STP STP Digest Snooping, 83, 84 configuration, 55, 67, 68, 91 spanning tree.
Ethernet interface physical state change suppression, 4 mCheck, 82 mCheck (global), 82 Layer 2 Ethernet interface storm control configuration, 9 mCheck (interface view), 82 mode set, 70 Layer 2 Ethernet interface storm suppression configuration, 8 MST common root bridge, 64 MST port roles, 65 MST port states, 65 switching Ethernet interface configuration, 1 MST region, 63 inloopback interface configuration, 12, 13 MST region configuration, 71 loopback interface configuration, 12, 12 MST regional
STP max age, 61, 74 MSTP VLAN-to-instance mapping table, 64 LLDP advertisable TLV configuration, 122 port link type, 106 LLDP management address configuration, 123 port-based configuration, 106, 110 LLDP management address encoding format, 123 port-based VLAN access port assignment, 107 port isolation configuration, 52 TLV port-based VLAN access port assignment (in interface view), 107 LLDP parameters, 124 LLDPDU LLDP-MED types, 115 port-based VLAN access port assignment (in VLAN view), 107 LLD
