Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    View all the pages
    Page
    of 2513
    Add page 381 to Favourites
    image text
    Enable zoom 
    							 170 
•  If you want to restore the default settings of the ti mers, restore the Hold timer first, followed by the 
Join, Leave, and LeaveAll timers. 
Table 20  Dependencies of the GARP timers 
Timer Lower limit  U
pper limit 
Hold  10 centiseconds  No greater than half of the Join timer 
Join  No less than twice the Hold timer Less than half of the Leave timer 
Leave  Greater than twice the Join timer Less than the LeaveAll timer 
LeaveAll  Greater than the Leave timer  32,765 centiseconds 
 
 NOTE: 
To keep the dynamic VLANs learned through GVRP stab le, do not set the LeaveAll timer smaller than its
 
default value, 1000 centiseconds.  
Displaying and maintaining GVRP 
 
Task Command Remarks 
Display statistics about GARP on 
ports.
  display garp statistics
 [ interface interface-list  ] [ | 
{  begin |  exclude | include  } regular-expression  ] Available in 
any view  
Display GARP timers on ports.
 display garp timer
 [ interface interface-list  ] [ | { begin  | 
exclude  | include  } regular-expression ]  Available in 
any view  
Display the local VLAN 
information that GVRP maintains 
on ports. display gvrp local-vlan
 interface  interface-type 
interface-number  [ | { begin |  exclude | include  } 
regular-expression  ]   Available in 
any view  
Display the current GVRP state in 
the specified VLANs on ports. display gvrp state
 interface  interface-type 
interface-number vlan  vlan-id  [ | { begin |  exclude | 
include  } regular-expression ]   Available in 
any view  
Display GVRP statistics on ports.
 display gvrp statistics
 [ interface interface-list  ] [ | 
{  begin |  exclude | include  } regular-expression  ] Available in 
any view  
Display the global GVRP state.
 display gvrp status
 [ | { begin  | exclude |  include } 
regular-expression  ]   Available in 
any view  
Display the information about 
dynamic VLAN operations on 
ports. display gvrp vlan-operation
 interface  interface-type 
interface-number  [ | { begin |  exclude | include  } 
regular-expression  ]   Available in 
any view  
Clear the GARP statistics on ports.
 reset garp statistics
 [ interface interface-list ]  Available in 
user view 
 
GVRP configuration examples 
GVRP normal registration mode configuration example 
Network requirements 
As shown in 
Figure 54:
    Add page 382 to Favourites
    image text
    Enable zoom 
    							 171 
•  Device A and Device B are connected through their ports GigabitEthernet 1/0/1. 
•   Enable GVRP and configure the normal registration  mode on ports to enable the registration and 
deregistration of dynamic and static VLAN information between the two devices.  
Figure 54  Network diagram 
 
 
Configuration procedure 
1.  Configure Device A: 
# Enable GVRP globally.  
 system-view 
[DeviceA] gvrp 
# Configure port GigabitEthernet 1/0/1 as a  trunk port, and assign it to all VLANs.  
[DeviceA] interface gigabitethernet 1/0/1 
[DeviceA-GigabitEthernet1/0/1] port link-type trunk 
[DeviceA-GigabitEthernet1/0/1] port trunk permit vlan all 
# Enable GVRP on trunk port GigabitEthernet 1/0/1. 
[DeviceA-GigabitEthernet1/0/1] gvrp 
[DeviceA-GigabitEthernet1/0/1] quit 
# Create VLAN 2 (a static VLAN). 
[DeviceA] vlan 2 
[DeviceA-vlan2] quit 
2. Configure Device B: 
# Enable GVRP globally.  
 system-view 
[DeviceB] gvrp 
# Configure port GigabitEthernet 1/0/1 as a  trunk port, and assign it to all VLANs.  
[DeviceB] interface gigabitethernet 1/0/1 
[DeviceB-GigabitEthernet1/0/1] port link-type trunk 
[DeviceB-GigabitEthernet1/0/1] port trunk permit vlan all 
# Enable GVRP on trunk port GigabitEthernet 1/0/1. 
[DeviceB-GigabitEthernet1/0/1] gvrp 
[DeviceB-GigabitEthernet1/0/1] quit 
# Create VLAN 3 (a static VLAN). 
[DeviceB] vlan 3 
[DeviceB-vlan3] quit 
3. Verify the configuration: 
Use the  display gvrp local-vlan  command to display the local VLAN information that GVRP 
maintains on ports. For example: 
# Display the local VLAN information that GVRP  maintains on port GigabitEthernet 1/0/1 of 
Device A. 
[DeviceA] display gvrp local-vlan interface gigabitethernet 1/0/1 
 Following VLANs exist in GVRP local database:
    Add page 383 to Favourites
    image text
    Enable zoom 
    							 172 
  1(default),2-3 
According to the output, information about VLAN 1, static VLAN information of VLAN 2 on the 
local device, and dynamic VLAN information of VLAN 3 on Device B are all registered through 
GVRP. 
# Display the local VLAN information that GVRP  maintains on port GigabitEthernet 1/0/1 of 
Device B. 
[DeviceB] display gvrp local-vlan interface gigabitethernet 1/0/1 
 Following VLANs exist in GVRP local database: 
  1(default),2-3 
According to the output, information about VLAN 1, static VLAN information of VLAN 3 on the 
local device, and dynamic VLAN information of VL AN 2 on Device A are all registered through 
GVRP. 
GVRP fixed registration mode configuration example 
Network requirements 
As shown in  Figure 55:  
•   D
evice A and Device B are connected through their ports GigabitEthernet 1/0/1. 
•   Enable GVRP and configure the fixed registration  mode on ports to enable the registration and 
deregistration of static VLAN info rmation between the two devices.  
Figure 55  Network diagram 
 
 
Configuration procedure  
1.  Configure Device A: 
# Enable GVRP globally.  
 system-view 
[DeviceA] gvrp 
# Configure port GigabitEthernet 1/0/1 as a  trunk port, and assign it to all VLANs.  
[DeviceA] interface gigabitethernet 1/0/1 
[DeviceA-GigabitEthernet1/0/1] port link-type trunk 
[DeviceA-GigabitEthernet1/0/1] port trunk permit vlan all 
# Enable GVRP on GigabitEthernet 1/0/1 and set  the GVRP registration mode to fixed on the 
port.  
[DeviceA-GigabitEthernet1/0/1] gvrp 
[DeviceA-GigabitEthernet1/0/1] gvrp registration fixed 
[DeviceA-GigabitEthernet1/0/1] quit 
# Create VLAN 2 (a static VLAN). 
[DeviceA] vlan 2 
[DeviceA-vlan2] quit 
2.  Configure Device B: 
# Enable GVRP globally.  
 system-view
    Add page 384 to Favourites
    image text
    Enable zoom 
    							 173 
[DeviceB] gvrp 
# Configure port GigabitEthernet 1/0/1 as a trunk port, and assign it to all VLANs.  
[DeviceB] interface gigabitethernet 1/0/1 
[DeviceB-GigabitEthernet1/0/1] port link-type trunk 
[DeviceB-GigabitEthernet1/0/1] port trunk permit vlan all 
# Enable GVRP on GigabitEthernet 1/0/1, and set  the GVRP registration mode to fixed on the 
port.  
[DeviceB-GigabitEthernet1/0/1] gvrp 
[DeviceB-GigabitEthernet1/0/1] gvrp registration fixed 
[DeviceB-GigabitEthernet1/0/1] quit 
# Create VLAN 3 (a static VLAN). 
[DeviceB] vlan 3 
[DeviceB-vlan3] quit 
3.  Verify the configuration: 
Use the  display gvrp local-vlan  command to display the local VLAN information that GVRP 
maintains on ports. For example: 
# Display the local VLAN information that GVRP  maintains on port GigabitEthernet 1/0/1 of 
Device A. 
[DeviceA] display gvrp local-vlan interface gigabitethernet 1/0/1 
 Following VLANs exist in GVRP local database: 
  1(default), 2 
According to the output, information about VLAN 1  and static VLAN information of VLAN 2 on the 
local device are registered through GVRP, but dynamic VLAN information of VLAN 3 on Device B 
is not.  
# Display the local VLAN information that GVRP  maintains on port GigabitEthernet 1/0/1 of 
Device B. 
[DeviceB] display gvrp local-vlan interface gigabitethernet 1/0/1 
 Following VLANs exist in GVRP local database: 
  1(default), 3 
According to the output, information about VLAN 1  and static VLAN information of VLAN 3 on the 
local device are registered through GVRP, but dy namic VLAN information of VLAN 2 on Device A 
is not.  
GVRP forbidden registration mode configuration example 
Network requirements 
As shown in  Figure 56:  
•   D
evice A and Device B are connected through their ports GigabitEthernet 1/0/1. 
•   Enable GVRP and configure the forbidden registration mode on ports to prevent the registration and 
deregistration of all VLANs but  VLAN 1 between the two devices. 
Figure 56  Network diagram
    Add page 385 to Favourites
    image text
    Enable zoom 
    							 174 
Configuration procedure  
1. Configure Device A: 
# Enable GVRP globally.  
 system-view 
[DeviceA] gvrp 
# Configure port GigabitEthernet 1/0/1 as a  trunk port, and assign it to all VLANs.  
[DeviceA] interface gigabitethernet 1/0/1 
[DeviceA-GigabitEthernet1/0/1] port link-type trunk 
[DeviceA-GigabitEthernet1/0/1] port trunk permit vlan all 
# Enable GVRP on GigabitEthernet 1/0/1, and set  the GVRP registration mode to forbidden on 
the port.  
[DeviceA-GigabitEthernet1/0/1] gvrp 
[DeviceA-GigabitEthernet1/0/1] gvrp registration forbidden 
[DeviceA-GigabitEthernet1/0/1] quit 
# Create VLAN 2 (a static VLAN). 
[DeviceA] vlan 2 
[DeviceA-vlan2] quit 
2.  Configure Device B: 
# Enable GVRP globally.  
 system-view 
[DeviceB] gvrp 
# Configure port GigabitEthernet 1/0/1 as a  trunk port, and assign it to all VLANs.  
[DeviceB] interface gigabitethernet 1/0/1 
[DeviceB-GigabitEthernet1/0/1] port link-type trunk 
[DeviceB-GigabitEthernet1/0/1] port trunk permit vlan all 
# Enable GVRP on GigabitEthernet 1/0/1, and set  the GVRP registration mode to forbidden on 
the port.  
[DeviceB-GigabitEthernet1/0/1] gvrp 
[DeviceB-GigabitEthernet1/0/1] gvrp registration forbidden 
[DeviceB-GigabitEthernet1/0/1] quit 
# Create VLAN 3 (a static VLAN). 
[DeviceB] vlan 3 
[DeviceB-vlan3] quit 
3.  Verify the configuration: 
Use the  display gvrp local-vlan  command to display the local VLAN information that GVRP 
maintains on ports. For example: 
# Display the local VLAN information that GVRP  maintains on port GigabitEthernet 1/0/1 of 
Device A. 
[DeviceA] display gvrp local-vlan interface gigabitethernet 1/0/1 
 Following VLANs exist in GVRP local database: 
  1(default) 
According to the output, information about VLAN  1 is registered through GVRP, but static VLAN 
information of VLAN 2 on the local device and  dynamic VLAN information of VLAN 3 on Device 
B are not.
    Add page 386 to Favourites
    image text
    Enable zoom 
    							 175 
# Display the local VLAN information that GVRP maintains on port GigabitEthernet 1/0/1 of 
Device B. 
[DeviceB] display gvrp local-vlan interface gigabitethernet 1/0/1 
 Following VLANs exist in GVRP local database: 
  1(default) 
According to the output, information about VLAN  1 is registered through GVRP, but static VLAN 
information of VLAN 3 on the local device and  dynamic VLAN information of VLAN 2 on Device 
A are not.
    Add page 387 to Favourites
    image text
    Enable zoom 
    							 176 
Configuring QinQ 
Throughout this document, customer network VLANs (CVLANs), also called inner VLANs, refer to the 
VLANs that a customer uses on the private network; and service provider network VLANs (SVLANs), also 
called outer VLANs, refer to the VLANs that a service provider uses to carry VLAN tagged traffic for 
customers. 
Overview 
802.1Q-in-802.1Q (QinQ) is a flexible, easy-to- implement Layer 2 VPN technology based on IEEE 
8 02.1 Q .  Q i n Q  e n a b l e s  t h e  e d g e  d e vi c e  o n  a  s e r vi c e  p ro vi d e r  n e t wo r k  t o  i n s e r t  a n  o u t e r  V L A N  t a g  i n  t h e  
Ethernet frames from customer netw orks, so that the Ethernet frames travel across the service provider 
network (public network) with double VLAN tags.  QinQ enables a service provider to use a single 
SVLAN to serve customers who have multiple CVLANs.  
Background and benefits 
The IEEE 802.1Q VLAN tag uses 12 bits for VLAN IDs. A device supports a maximum of 4094 VLANs. 
This is far from enough for isolating users in actual networks, especially in metropolitan area networks 
(MANs). 
By tagging tagged frames, QinQ expands the availa ble VLAN space from 4094 to 4094 × 4094. QinQ 
delivers the following benefits: 
•   Releases the stress on the SVLAN resource.  
•   Enables customers to plan their CVLANs without conflicting with SVLANs.  
•   Provides an easy-to-implement Layer 2 VPN solution for small-sized MANs or intranets. 
•   Enables the customers to keep their VLAN assignment schemes unchanged when the service 
provider upgrades the service provider network.  
How QinQ works 
The devices in the public network forward a frame only according to its outer VLAN tag and obtain its 
source MAC address into the MAC address table of th e outer VLAN. The inner VLAN tag of the frame is 
transmitted as the payload.
    Add page 388 to Favourites
    image text
    Enable zoom 
    							 177 
Figure 57  Typical QinQ application scenario 
 
 
As shown in Figure 57, customer network A has CVLANs 1 through 10, and customer network B has 
CVLANs 1 through 20. The service provider assign s SVLAN 3 for customer network A, and assigns 
SVLAN 4 for customer network B.  
When a tagged Ethernet frame from customer network A arrives at a provider edge device (PE), the PE 
tags the frame with outer VLAN 3. When a tagged Ethernet frame from customer network B arrives at a 
PE, the PE tags the frame with outer VLAN 4. There is no overlap of VLAN IDs among customers, and 
traffic from different customers can be identified separately.  
The double-tagged Ethernet frame is then transmitted over the service provider network and arrives at the 
other PE. The PE removes the SVLAN of the frame before sending it to the target customer edge device 
(CE). 
QinQ frame structure 
A QinQ frame is transmitted double-tagged over  the service provider network. As shown in Figure 58, 
the inne
r VLAN tag is the CVLAN tag, and the outer one is the SVLAN tag that the service provider has 
allocated to the customer. 
QinQ uses CVLAN tags to transmit frames over the  private network, and uses SVLAN tags to transmit 
frames over the public network. When a QinQ frame is transmitted over the public network, its CVLAN 
tag is transmitted as the payload.
    Add page 389 to Favourites
    image text
    Enable zoom 
    							 178 
Figure 58  Single-tagged Ethernet fr ame header and double-tagge d Ethernet frame header 
 
The default maximum transmission unit (MTU) of an interface is 1500 bytes. The size of an outer VLAN 
tag is 4 bytes. HP recommends you to increase the MTU of each interface on the service provider network 
to at least 1504 bytes.  
Implementations of QinQ 
HP provides the following QinQ implementations: basic QinQ and selective QinQ.  
•   Basic QinQ 
Basic QinQ enables a port to tag any incoming fram es with its port VLAN ID (PVID) tag, regardless 
of whether they have been tagged or not. If an  incoming frame has been tagged, it becomes a 
double-tagged frame. If not, it become s a frame tagged with the PVID tag.  
•   Selective QinQ 
Selective QinQ is more flexible  than basic QinQ. In addition to  all the functions of basic QinQ, 
selective QinQ enables a port to perform the fo llowing per-CVLAN actions for incoming frames: 
{ Tag frames from different CVLANs with different SVLAN tags. 
{ Mark the outer VLAN 802.1p priority based on the existing inner VLAN 802.1p priority. 
{ Modify the inner VLAN ID (available only on the 5500 EI). 
Besides being able to separate the service provider  network from the customer networks, selective 
QinQ provides abundant service features and enables more flexible networking. 
Modifying the TPID in a VLAN tag 
A VLAN tag uses the tag protocol identifier (TPID) field  to identify the protocol type of the tag. The default 
value of this field, as defined in IEEE 802.1Q, is 0x8100.  
Figure 59  sh
 ows the 802.1Q-defined tag structure of an Ethernet frame.  
Figure 59  VLAN tag structure of an Ethernet frame
    Add page 390 to Favourites
    image text
    Enable zoom 
    							 179 
The device determines whether a received frame carries an SVLAN or CVLAN tag by checking the TPID 
value. For example, if a frame carries an SVLAN tag with TPID value 0x9100 and a CVLAN tag with TPID 
value 0x8100 and the configured TPID value of the SVLAN tag is 0x9100 and that of the CVLAN tag is 
0x8200, the device considers that the frame carries only the SVLAN tag but not the CVLAN tag.  
Devices of different vendors may set the TPID of the outer VLAN tag of QinQ frames to different values. 
For compatibility with these devices, modify the TPID value so that the QinQ frames, when sent to the 
public network, carry the TPID value identical to the value of a particular vendor, allowing 
interoperability with the devices of that vendor.  
The TPID in an Ethernet frame has the same position as the protocol type field in a frame without a VLAN 
tag. To avoid problems in packet forwarding and handling in the network, do not set the TPID value to 
any of the reserved values.  
Table 21  Reserved protocol type values 
Protocol t
ype Value 
ARP 0x0806 
PUP 0x0200 
RARP 0x8035 
IP 0x0800 
IPv6 0x86DD 
PPPoE 0x8863/0x8864 
MPLS 0x8847/0x8848 
IPX/SPX 0x8137 
IS-IS 0x8000 
LACP 0x8809 
802.1X 0x888E 
Cluster 0x88A7 
Reserved 0xFFFD/0xFFFE/0xFFFF 
 
Protocols and standards 
IEEE 802.1Q:  IEEE standard for local and metropolitan area networks: Virtual Bridged Local Area 
Networks  
QinQ configuration task list 
When you configure QinQ, follow these guidelines: 
•  QinQ requires configurations only on the service provider network. 
•   Q i n Q  c o n fi g u r a t i o n s  m a d e  i n  E t h e r n e t  i n t e r f a c e  vi e w  t a ke  e f f e c t  o n  t h e  cu r re n t  i n t e r f a c e  o n l y.  T h o s e  
made in Layer 2 aggregate interface view take effe ct on the current aggregate interface and all the 
member ports in the aggregation group. Those made  in por t group view take effect on all member 
ports in the current port group.  
•   Do not configure QinQ on a reflector port. Fo r more information about reflector ports, see Network 
Management and Monitoring Configuration Guide .
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide