Configuring VLAN termination Overview VLAN termination typically processes packets that include VLAN tags. A VLAN termination-enabled interface performs the following tasks when receiving a VLAN-tagged packet: Assigns the packet to an interface according to its VLAN tags. Removes the VLAN tags of the packet. Delivers the packet to Layer 3 forwarding or other processing pipelines.
Page 6
As shown in Figure 1, Host A and Host B are in dif ferent VLANs. The two host s can communicate with each other after you perform the following tasks: Specify 1.1.1.1/24 and 1.1.2.1/24 as the gateway IP addresses for Host A and Host B, respectively.
Configuration restrictions and guidelines When you configure VLAN termination, follow these restrictions and guidelines: • On a portal-enabled interface, log off all portal users before you change the VLAN termination type, for example, from Dot1q termination to QinQ termination. Any portal users who remain online after the change cannot be logged off or reauthenticated.
Configuring Dot1q termination Based on the range of outermost VLAN IDs in the VLAN-tagged packets that can be terminated by a subinterface, the following types of Dot1q termination are available: • Ambiguous Dot1q termination—Terminates VLAN-tagged packets whose outermost VLAN IDs are in the specified range. Any other VLAN-tagged packets are not allowed to pass through this subinterface.
• When you use the vlan-type dot1q vid second-dot1q command to configure ambiguous QinQ termination multiple times, one of the following conditions occurs: If the most recently specified Layer 1 ID is the same as the current Layer 1 ID, the specified Layer 2 IDs in both configurations take effect.
This command prohibits transmission of broadcast packets and other types of multicast packets, and consumes less CPU resources than the vlan-termination broadcast enable command. To enable a VLAN termination-enabled interface to transmit broadcasts and multicasts: Step Command Remarks Enter system view. system-view •...
Step Command Remarks • Enter Layer 3 Ethernet interface view: Configurations made in the interface interface-type following views take effect on interface-number all the subinterfaces: • Enter Layer 3 aggregate interface Layer 3 Ethernet • view: interface view. Enter interface view. interface route-aggregation •...
Page 14
# On Host C, specify 3.3.3.3/8 and 3.0.0.1/8 as its IP address and gateway IP address, respectively. (Details not shown.) # On Host D, specify 4.4.4.4/8 and 4.0.0.1/8 as its IP address and gateway IP address, respectively. (Details not shown.) Configure Layer 2 Switch A: # Create VLAN 10.
[Device-GigabitEthernet2/0/1.20] quit Verifying the configuration # Verify that Host A, Host B, Host C, and Host D can ping each other. (Details not shown.) Ambiguous Dot1q termination configuration example Network requirements As shown in Figure 4, configure ambiguous Dot1q termination, so that hosts in different VLANs can communicate with the server group.
[L2_SwitchA] vlan 13 # Assign GigabitEthernet 1/0/3 to VLAN 13. [L2_SwitchA-vlan13] port gigabitethernet 1/0/3 [L2_SwitchA-vlan13] quit # Configure GigabitEthernet 1/0/7 as a trunk port, and assign the port to VLANs 11 through 13. [L2_SwitchA] interface gigabitethernet 1/0/7 [L2_SwitchA-GigabitEthernet1/0/7] port link-type trunk [L2_SwitchA-GigabitEthernet1/0/7] port trunk permit vlan 11 to 13 Configure the device: # Create Ethernet subinterface GigabitEthernet 1/0/1.10, and assign an IP address to the...
Figure 5 Network diagram Configuration procedure # Configure VLANs and Dot1q termination. For the configuration procedure, see "Ambiguous Dot1q termination configuration example." (Details not shown.) # Configure the router as the PPPoE server. Configure PPPoE settings on GigabitEthernet 1/0/1.10 on the router. For more information about the PPPo E configuration, see Layer 2—WAN Configuration Guide.
Page 18
Figure 6 Network diagram Router L2 Switch B GE1/0/1 Service provider network VLAN 100 GE1/0/2 GE1/0/1.10 GE1/0/2 QinQ enabled 1.1.1.11/24 1.1.2.11/24 GE1/0/1 L2 Switch A L2 Switch C GE1/0/2 VLAN 11 Host A Host B 1.1.1.1/24 1.1.2.1/24 Configuration procedure In this example, Layer 2 Switch C uses the factory configuration. Configure Host A and Host B: # On Host A, specify 1.1.1.1/24 and 1.1.1.11/24 as its IP address and gateway IP address, respectively.
[L2_SwitchB] interface gigabitethernet 1/0/1 [L2_SwitchB-GigabitEthernet1/0/1] port link-type trunk [L2_SwitchB-GigabitEthernet1/0/1] port trunk permit vlan 100 Configure the router: # Create Ethernet subinterface GigabitEthernet 1/0/1.10, and assign an IP address to the subinterface. <Router> system-view [Router] interface gigabitethernet 1/0/1.10 [Router-GigabitEthernet1/0/1.10] ip address 1.1.1.11 255.255.255.0 # Enable QinQ termination on GigabitEthernet 1/0/1.10 to terminate the VLAN-tagged packets with the Layer 1 VLAN ID 100 and the Layer 2 VLAN ID 11.
Page 20
# Assign IP addresses 1.1.1.1/24, 1.1.1.2/24, and 1.1.1.3/24 to Host A, Host B, and Host C, respectively. (Details not shown.) # Specify 1.1.1.11/24 as the gateway address for the hosts. (Details not shown.) Configure Layer 2 Switch A: # Create VLAN 11. <L2_SwitchA>...
# Configure GigabitEthernet 1/0/1.10 to terminate VLAN-tagged packets whose Layer 1 VLAN ID is 100 and Layer 2 VLAN ID is 11, 12, or 13. [Router-GigabitEthernet1/0/1.10] vlan-type dot1q vid 100 second-dot1q 11 to 13 # Enable GigabitEthernet 1/0/1.10 to transmit broadcasts and multicasts. [Router-GigabitEthernet1/0/1.10] vlan-termination broadcast enable [Router-GigabitEthernet1/0/1.10] quit # Assign an IP address to GigabitEthernet 1/0/2.
# Configure the router as the PPPoE server. Configure PPPoE settings on GigabitEthernet 1/0/1.10 on the router. For more inf ormation about PPPoE c onfiguration, see Layer 2—WAN Configuration Guide. (Details not shown.) Configuration example for QinQ termination supporting DHCP relay Network requirements As shown in Figure...
Page 23
# Configure GigabitEthernet 1/0/1.100 to terminate packets whose Layer 1 ID is 100 and Layer 2 VLAN ID is 10 or 20. [ProviderA-GigabitEthernet1/0/1.100] vlan-type dot1q vid 100 second-dot1q 10 20 # Enable GigabitEthernet 1/0/1.100 to transmit broadcast and multicast packets. [ProviderA-GigabitEthernet1/0/1.100] vlan-termination broadcast enable # Enable DHCP relay on GigabitEthernet 1/0/1.100 and specify 10.2.1.1 as the DHCP server address.
Page 24
# Set the PVID of GigabitEthernet 1/0/2 to VLAN 100. [SwitchA-GigabitEthernet1/0/2] port trunk pvid vlan 100 # Enable QinQ on GigabitEthernet1/0/2. [SwitchA-GigabitEthernet1/0/2] qinq enable [SwitchA-GigabitEthernet1/0/2] quit # Configure the downlink port GigabitEthernet 1/0/3 as a trunk port, and assign the port to VLANs 20 and 100.
Configuring LLDP Overview In a hete rogeneous network, a standard configuration exchange platform e nsures that dif ferent types of net work devices from different vendors can discover one another and exchange configuration. The Link Layer Discovery Protocol (LLDP) is specified in IEEE 802.1AB. The protocol operates on the data link layer to exchange device information between directly connected devices.
Page 26
LLDP frame formats LLDP sends device information in LLDP frames. LLDP frames are encapsulated in Ethernet II or Subnetwork Access Protocol (SNAP) frames. • LLDP frame encapsulated in Ethernet II Figure 11 Ethernet II-encapsulated LLDP frame Table 1 Fields in an Ethernet II-encapsulated LLDP frame Field Description MAC address to which the LLDP frame is advertised.
Page 27
Figure 12 SNAP-encapsulated LLDP frame Table 2 Fields in a SNAP-encapsulated LLDP frame Field Description MAC address to which the LLDP frame is advertised. It is the same as Destination MAC address that for Ethernet II-encapsulated LLDP frames. Source MAC address MAC address of the sending port.
Page 28
Table 3 Basic management TLVs Type Description Remarks Chassis ID Specifies the bridge MAC address of the sending device. Specifies the ID of the sending port: • If the LLDPDU carries LLDP-MED TLVs, the port ID Port ID Mandatory. TLV carries the MAC address of the sending port. •...
Page 29
NOTE: • HPE devices support only receiving protocol identity TLVs and VID usage digest TLVs. • Layer 3 Ethernet ports support only link aggregation TLVs. • IEEE 802.3 organizationally specific TLVs Table 5 IEEE 802.3 organizationally specific TLVs Type Description...
Type Description Allows a network device or terminal device to advertise power Extended Power-via-MDI supply capability. This TLV is an extension of the Power Via MDI TLV. Hardware Revision Allows a terminal device to advertise its hardware version. Firmware Revision Allows a terminal device to advertise its firmware version.
the token bucket mechanism to rate limit LLDP frames. For more information about the token bucket mechanism, see ACL and QoS Configuration Guide. LLDP automatically enables the fast LLDP frame transmission mechanism in either of the following cases: • A new LLDP frame is received and carries device information new to the local device. •...
Performing basic LLDP configurations Enabling LLDP To make LLDP take effect on specific ports, you must enable LLDP both globally and on these ports. To use LLDP together with OpenFlow, you must enable LLDP globally on OpenFlow switches. As a best practice to prevent L LDP from affecting topology discovery of OpenFlow controllers, disable LLDP on ports of Ope nFlow instances.
Step Command Remarks • In Layer 3 Ethernet interface view: lldp [ agent { nearest-customer | nearest-nontpmr } ] management-address-format Set the encoding format of By default, the encoding string the management address format of the management • In Layer 3 aggregate interface to string.
To set the encapsulation format for LLDP frames to SNAP: Step Command Remarks Enter system view. system-view Enter Layer 3 Ethernet interface view or Layer 3 interface interface-type interface-number aggregate interface view. • In Layer 3 Ethernet interface view: lldp [ agent { nearest-customer | nearest-nontpmr } ] encapsulation Set the encapsulation By default, Ethernet II...
You can enable the device to generate both ARP and ND entries. If the management address TLV contains an IPv4 addre ss, the device generates an ARP entry. If the mana gement address TLV contains an IPv6 address, the device generates an ND entry. To enable the device to g enerate an ARP or ND entry for a recei ved management address LLDP TLV: Step...
Page 40
• Monitor the link between Device A and the MED device on the NMS. Figure 14 Network diagram Configuration procedure Configure Device A: # Enable LLDP globally. <DeviceA> system-view [DeviceA] lldp global enable # Enable LLDP on GigabitEthernet 1/0/1. By default, LLDP is enabled on ports. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] lldp enable # Set the LLDP operating mode to Rx on GigabitEthernet 1/0/1.
Page 41
Global status of LLDP: Enable Bridge mode of LLDP: customer-bridge The current number of LLDP neighbors: 2 The current number of CDP neighbors: 0 LLDP neighbor information last changed time: 0 days, 0 hours, 4 minutes, 40 seconds Transmit interval : 30s Fast transmit interval : 1s...
Page 42
Number of sent optional TLV : 21 Number of received unknown TLV : 3 LLDP agent nearest-nontpmr: Port status of LLDP : Enable Admin status : Disable Trap flag : No MED trap flag : No Polling interval : 0s Number of LLDP neighbors Number of MED neighbors Number of CDP neighbors...
Page 43
Number of LLDP neighbors Number of MED neighbors Number of CDP neighbors Number of sent optional TLV Number of received unknown TLV : 5 LLDP agent nearest-nontpmr: Port status of LLDP : Enable Admin status : Disable Trap flag : No MED trap flag : No Polling interval...
Page 44
Polling interval : 0s Number of LLDP neighbors Number of MED neighbors Number of CDP neighbors Number of sent optional TLV : 16 Number of received unknown TLV : 0...
Document conventions and icons Conventions This section describes the conventions used in the documentation. Command conventions Convention Description Bold text represents commands and keywords that you enter literally as shown. Boldface Italic text represents arguments that you replace with actual values. Italic Square brackets enclose syntax choices (keywords or arguments) that are optional.
Network topology icons Convention Description 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.
Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...
Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Do cumentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
Page 49
part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.