HP 5500 Ei 5500 Si Switch Series Configuration Guide
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+.
![Page 2116
53
[DeviceA-GigabitEthernet1/0/49] quit
[DeviceA] interface gigabitethernet 1/0/50
[DeviceA-GigabitEthernet1/0/50] shutdown
%Jan 18 18:18:03:583 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
0/50 link
status is DOWN.
The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50
is down.
Assume that in this example, the unidirectional links are caused by cross- connected fibers. Correct
the fiber connections, and then brin g up the ports shut down...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2115.png "Page 2116
53
[DeviceA-GigabitEthernet1/0/49] quit
[DeviceA] interface gigabitethernet 1/0/50
[DeviceA-GigabitEthernet1/0/50] shutdown
%Jan 18 18:18:03:583 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/\
0/50 link
status is DOWN.
The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50
is down.
Assume that in this example, the unidirectional links are caused by cross- connected fibers. Correct
the fiber connections, and then brin g up the ports shut down...")
58 VLANs and sending Common-Flush-FDB packets to instruct all transit no des to update their own MAC entries and ARP/ND entries. Link down alarm mechanism The transit node, the edge node or the assistant-edge node sends Link-Down packets to the master node immediately when they find any of its own ports belonging to an RRPP domain are down. Upon the receipt of a Link-Down packet, the master node releases the secondary port from blocking data VLANs and sending Common-Flush-FDB packet to instruct al l the transit nodes, the edge nodes, and the assistant-edge nodes to update th eir own MAC entries and ARP/ND entrie s. After each node updates its own entries, traffic is switched to the normal link. Ring recovery The master node may find that the ring is restored af ter a period of time after the ports belonging to the RRPP domain on the transit nodes, the edge nodes, or the assistant-edge nodes are brought up again. A temporary loop may arise in the data VLAN during this period. As a result, broadcast storm occurs. To prevent temporary loops, non-master nodes block them immediately (and permit only the packets of the control VLAN to pass through) when they find their ports accessing the ring are brought up again. The blocked ports are activated only when the nodes are sure that no loop will be brought forth by these ports. Broadcast storm suppression mechanism in a multi-homed subring in case of SRPT failure As shown in Figure 17, Ring 1 is the primary ring, and Ring 2 and Ring 3 are subrings. When the two SRPTs between the edge node and the assistant-edge node are down, the master nodes of Ring 2 and Ring 3 will open their respective secondary ports, generating a loop among Device B, Device C, Device E, and Device F. As a result, a broadcast storm occurs. To prevent generating this loop, the edge node will block the edge port temporarily. The blocked edge port is activated only when the edge node is sure th at no loop will be brought forth when the edge port is activated. Load balancing In a ring network, maybe traffic of multiple VLANs is transmitted at the same time. RRPP can implement load balancing for the traffic by transmitting traffic of different VLANs along different paths. By configuring an individual RRPP domain for transmitting the traffic of the specified VLANs (protected VLANs) in a ring network, traffic of different VLANs can be transmitted according to different topologies in the ring network. In this way, load balancing is achieved. As shown in Figure 18, R ing 1 is configured as the primary ring of Domain 1 and Domain 2, which are configured with different protected VLANs. Device A is the master node of Ring 1 in Domain 1, and Device B is the master node of Ring 1 in Domain 2. With such configurations, traffic of different VL ANs can be transmitted on different links to achiev e load balancing in the single-ring network. RRPP ring group In an edge node RRPP ring group, only an activated subring with the lowest domain ID and ring ID can send Edge-Hello packets. In an assistant-edge node RRPP ring group, any activated subring that has received Edge-Hello packets will forward these packets to the other activated subrings. With an edge node RRPP ring group and an assi stant-edge node RRPP ring group configured, only one subring sends Edge-Hello packets on the edge node, and only one subring receives Edge-Hello packets on the assistant-edge node, reducing CPU workload. As shown in Figure 17, D evice B is the edge node of Ring 2 and Ring 3, and Device C is the assistant-edge node of Ring 2 and Ring 3. Device B and Device C must send or receive Edge-Hello
59 packets frequently. If more subrings are configured or if load balancing is configured for multiple domains, Device B and Device C will send or receive a mass of Edge-Hello packets. To reduce Edge-Hello traffic, you can assign Ring 2 and Ring 3 to an RRPP ring group configured on the edge node Device B and assign Ring 2 and Ring 3 to an R RPP ri ng g roup c onfigu re d on D evice C. Af ter such configurations, if all rings are activated, only Ring 2 on Device B sends Edge-Hello packets. Typical RRPP networking Here are several typical networking applications. Single ring As shown in Figure 14 , only a single ring exists in the network topology. You only need to define an RRPP domain. Figure 14 Schematic diagram for a single-ring network Tangent rings As shown in Figure 15, two or more rings are in the network topology and only one common node exists between rings. You must define an RRPP domain for each ring.
60 Figure 15 Schematic diagram for a tangent-ring network Intersecting rings As shown in Figure 16, two or more rings are in the network topology and two common nodes exist between rings. You only need to define an RRPP domain and configure one ring as the primary ring and the other rings as subrings. Figure 16 Schematic diagram for an intersecting-ring network Dual homed rings As shown in Figure 17, two or more rings are in the network topology and two similar common nodes exist between rings. You only need to define an RRPP domain and configure one ring as the primary ring and the other rings as subrings. Device A Master node Device D Transit node Domain 1 Ring 1 Device C Assistant edge node Device B Edge node Ring 2 Device E Master node
61 Figure 17 Schematic diagram for a dual-homed-ring network Single-ring load balancing In a single-ring network, you can achieve load balancing by configuring multiple domains. As shown in Figure 18, Ring 1 is configured as the primary ring of both Domain 1 and Domain 2. Domain 1 and Domain 2 are configured with differ ent protected VLANs. In Domain 1, Device A is c o n fig u re d a s t h e m a s te r n o d e o f Ri n g 1. I n D o m a i n 2, D evic e B i s c o n fi g u re d a s t h e m a s te r n o d e o f Ri n g 1. Such configurations enable the ring to block different links based on VLANs, and single-ring load balancing is achieved. Figure 18 Schematic diagram for a single-ring load balancing network Intersecting-ring load balancing In an intersecting-ring network, you can also achieve load balancing by configuring multiple domains. As shown in Figure 19, R ing 1 is the primary ring, and Ring 2 is the subring in both Domain 1 and Domain 2. Domain 1 and Domain 2 are configured with different protected VLANs. Device A is c o n fig u re d as t h e m as te r no d e of Ri n g 1 i n D o m a i n 1. D evic e D i s c o n fig u re d as t he m as te r no de of Ri ng 1 in Domain 2. Device E is configured as the master node of Ring 2 in both Domain 1 and Domain 2. However, different ports on Device E are blocked in Domain 1 and Domain 2. With the configurations, you can enable traffic of different VLANs to travel over different paths in the subring and primary ring to achieve intersecting-ring load balancing. Device A Master node Device D Transit node Domain 1 Ring 1 Device C Assistant edge node Device B Edge node Ring 2 Device E Master node Device F Master node Ring 3
62 Figure 19 Schematic diagram for an intersecting-ring load balancing network Protocols and standards RFC 3619 Extreme Networks Ethernet Automatic Protection Switching (EAPS) Version 1 is related to RRPP. RRPP configuration task list You can create RRPP domains based on service planning, specify control VLANs and data VLANs for each RRPP domain, and then determine the ring roles and node roles based on the traffic paths in each RRPP domain. Complete the following tasks to configure RRPP: Task Remarks Creating an RRPP domain Required Perform this task on all nodes in the RRPP domain. Configuring control VLANs Required Perform this task on all nodes in the RRPP domain. Configuring protected VLANs Required Perform this task on all nodes in the RRPP domain. Configuring RRPP rings Configuring RRPP ports Required Perform this task on all nodes in the RRPP domain. Configuring RRPP nodes Required Perform this task on all nodes in the RRPP domain Activating an RRPP domain Required Perform this task on all nodes in the RRPP domain. Configuring RRPP timers Optional Perform this task on the master node in the RRPP domain.
63 Task Remarks Configuring an RRPP ring group Optional Perform this task on the edge node and assistant-edge node in the RRPP domain. NOTE: • RRPP does not have an auto election mechanism, so you must confi gure each node in the ring network properly for RRPP to monitor and protect the ring network. • Before configuring RRPP, you must construct a ring-shaped Ethernet topology physically. Creating an RRPP domain When creating an RRPP domain, specify a domain ID , which uniquely identifies an RRPP domain. All devices in the same RRPP domain must be configured with the same domain ID. Perform this configuration on devices you want to configure as nodes in the RRPP domain. To create an RRPP domain: Step Command 1. Enter system view. system-view 2. Create an RRPP domain, and enter RRPP domain view. rrpp domain domain-id Configuring control VLANs Before configuring RRPP rings in an RRPP domain, configure the same control VLANs for all nodes in the RRPP domain first. Perform this configuration on all nodes in the RRPP domain to be configured. Configuration guidelines • When you configure existing VLANs as control VLANs, the system prompts errors. • To ensure proper forwarding of RRPPDUs, do no t enable 802.1Q in 802.1Q (QinQ) or VLAN mapping on the control VLANs. • To make sure RRPPDUs can be sent and received correctly, do not configure the default VLAN of a port accessing an RRPP ring as the primary control VLAN or the secondary control VLAN. • To transparently transmit RRPPDUs on a device not configured with RRPP, you must ensure only the two ports connecting the device to the RRPP ring permit the packets of the control VLANs. Otherwise, the packets from other VLANs may go into the cont rol VLANs in transparent transmission mode and strike the RRPP ring. Configuration procedure To c o n fig u re c o nt ro l V L A N s :
64 Step Command 1. Enter system view. system-view 2. Enter RRPP domain view. rrpp domain domain-id 3. Configure the primary control VLAN for the RRPP domain. control-vlan vlan-id Configuring protected VLANs Before configuring RRPP rings in an RRPP domain, co nfigure the same protected VLANs for all nodes in the RRPP domain first. All VLANs that the RRPP port s are assigned to should be protected by the RRPP domains. You can configure protected VLANs through referencing Multiple Spanning Tree Instances (MSTIs). Before configuring protected VLANs, configure the mappings between MSTIs and the VLANs to be protected (a device working in PVST mode automatically maps VLANs to MSTIs). For more information about MSTIs and PVST, see Layer 2—LAN Switching Configuration Guide . Perform this configuration on all nodes in the RRPP domain to be configured. To configure protected VLANs: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter MST region view. stp region-configuration Not required if the device is operating in PVST mode. For more information about the command, see Layer 2—LAN Switching Command Reference . 3. Configure the VLAN-to-instance mapping table. Approach 1: instance instance-id vlan vlan-list Approach 2: vlan-mapping modulo modulo Optional. Use either approach. All VLANs in an MST region are mapped to MSTI 0 (the CIST) by default. Not required if the device is operating in PVST mode. For more information about the commands, see Layer 2—LAN Switching Command Reference . 4. Activate MST region configuration manually. active region-configuration Not required if the device is operating in PVST mode. For more information about the command, see Layer 2—LAN Switching Command Reference .
65
Step Command Remarks
5. Display the currently activated
configuration information of
the MST region. display stp region-configuration
[ |
{ begin | exclude | include }
regular-expression ] Optional.
Available in any view.
The command output includes
VLAN-to-instance mappings.
For more information about the
command, see
Layer 2—LAN
Switching Command Reference .
6. Return to system view.
quit Not required if the device is
operating in PVST mode.
7.
Enter RRPP domain view.
rrpp domain domain-id N/A
8. Configure protected VLANs
for the RRPP domain. protected-vlan reference-instance
instance-id-list By default, no protected VLAN is
configured for an RRPP domain.
NOTE:
When configuring load balancing, you must configure different pr otected VLANs for different RRPP
domains.
Configuring RRPP rings
Wh e n c o n fi g u ri n g a n R R PP ri n g, yo u m u s t m a ke s o m e configurations on the ports connecting each node
to the RRPP ring before configuring the nodes.
RRPP ports (connecting devices to an RRPP ring) must be Layer-2 Ethernet ports or Layer-2 aggregate
interfaces and cannot be member po rts of any aggregation group, service loopback group, or smart link
group.
After configuring a Layer-2 aggregate interface as an RRPP port, you can still assign ports to or remove
ports from the aggregation group corresponding to the interface.
Configuring RRPP ports
Perform this configuration on each node’s ports intended for accessing RRPP rings.
Configuration guidelines
• RRPP ports always allow packets of the control VLANs to pass through.
• For more information about the port link-type trunk, port trunk permit vlan , and undo stp enable
commands, see Layer 2—LAN Switching Command Reference .
• The 802.1p priority of trusted packets on the RRPP ports must be configured, so that RRPP packets
take higher precedence than data packets when passing through the RRPP ports. For more
information about the qos trust dot1p command, see ACL and QoS Command Reference .
• Do not enable OAM remote loopback function on an RRPP port. Otherwise, it may cause a
temporary broadcast storm.
• Do not configure a port accessing an RRPP ring as the destination port of a mirroring group.
• Do not configure physical-link-state change suppressi on time on a port accessing an RRPP ring to
accelerate topology convergence. For more information, see the undo link-delay command (Layer
2—LAN Switching Command Reference ).
66
Configuration procedure
To c o n fig u re R R PP p o r ts :
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter Layer 2 Ethernet
interface view or Layer 2
aggregation interface view. interface
interface-type
interface-number N/A
3.
Configure the link type of the
interface as trunk. port link-type trunk By default, the link type of an
interface is access.
4.
Assign the trunk port to the
protected VLANs of the RRPP
domain. port trunk permit vlan
{ vlan-id-list
| all } By default, a trunk port allows only
packets of VLAN 1 to pass through.
5.
Disable the spanning tree
feature. undo stp enable
Enabled by default.
6. Configure the port to trust the
802.1p precedence of the
received packets. qos trust
dot1p By default, the port priority is
trusted.
Configuring RRPP nodes
If a device carries multiple RRPP rings in an RRPP domain, only one ring can be configured as the primary
ring on the device, and the role of the device on a subring can only be an edge node or an
assistant-edge node.
Specifying a master node
Perform this configuration on a device to be configured as a master node.
To specify a master node:
Step Command
1.
Enter system view.
system-view
2. Enter RRPP domain view. rrpp domain domain-id
3. Specify the current device as the master node of
the ring, and specify the primary port and the
secondary port. ring
ring-id node-mode master [ primary-port
interface-type interface-number ] [ secondary-port
interface-type interface-number ] level level-value
Specifying a transit node
Perform this configuration on a device to be configured as a transit node.
To specify a transit node:
Step Command
1. Enter system view.
system-view
2. Enter RRPP domain view.
rrpp domain domain-id
3. Specify the current device as a transit node of the
ring, and specify the primary port and the
secondary port. ring
ring-id node-mode transit [ primary-port
interface-type interface-number ] [ secondary-port
interface-type interface-number ] level level-value
67 Specifying an edge node When configuring an edge node, you must first configure the primary ring before configuring the subrings. Perform this configuration on a device to be configured as an edge node. To specify an edge node: Step Command 1. Enter system view. system-view 2. Enter RRPP domain view. rrpp domain domain-id 3. Specify the current device as a transit node of the primary ring, and specify the primary port and the secondary port. ring ring-id node-mode transit [ primary-port interface-type interface-number ] [ secondary-port interface-type interface-number ] level level-value 4. Specify the current device as the edge node of a subring, and specify the edge port. ring ring-id node-mode edge [ edge-port interface-type interface-number ] Specifying an assistant-edge node When configuring an assistant-edge node, you must first configure the primary ring before configuring the subrings. Perform this configuration on a device to be configured as an assistant-edge node. To specify an assistant-edge node: Step Command 1. Enter system view. system-view 2. Enter RRPP domain view. rrpp domain domain-id 3. Specify the current device as a transit node of the primary ring, and specify the primary port and the secondary port. ring ring-id node-mode transit [ primary-port interface-type interface-number ] [ secondary-port interface-type interface-number ] level level-value 4. Specify the current device as the assistant-edge node of the subring, and specify an edge port. ring ring-id node-mode assistant-edge [ edge-port interface-type interface-number ] Activating an RRPP domain To activate an RRPP domain on the current device, enable the RRPP protocol and RRPP rings for the RRPP domain on the current device. To prevent Hello packets of subrings from being looped on the primary ring, enable the primary ring on its master node before enabling the subrings on th eir separate master nodes. On an edge node or assistant-edge node, enable/disable the primary ring and subrings separately: • Enable the primary ring of an RRPP domain before enabling the subrings of the RRPP domain. • Disable the primary ring of an RRPP domain after disabling all subrings of the RRPP domain. Perform this operation on all nodes in the RRPP domain. To activate an RRPP domain: