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 221 to Favourites
    image text
    Enable zoom 
    							10 
To avoid congestion on GigabitEthernet 1/0/4, set 100 Mbps as the only option available for speed 
negotiation on port GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, and GigabitEthernet 1/0/3. As a 
result, the transmission rate on each port connected to a server is limited to 100 Mbps. 
To set speed options for auto negotiation on an Ethernet interface: 
 
Step Command Remarks 
1.   Enter system view.  system-view  N/A 
2.  Enter Ethernet interface view. 
interface interface-type interface-number  N/A 
3.  Set speed options for auto negotiation. speed  auto  { 10 |  100 | 1000 } *   Optional. 
 
 NOTE: 
•  This function is available only for Layer 2 copper GE ports that support speed auto negotiation.  
•   The  speed  and speed auto  commands supersede each other, and whichever is configured last takes 
effect. 
 
Configuring storm suppression 
You can use the storm suppression function to limit the size of a particular type of traffic (broadcast, 
multicast, or unknown unicast traffic) as a whole globally in system view or on a per-interface basis in 
Ethernet interface view or port group view.  
In interface or port group view,  you set the maximum size of broadcast, multicast or unknown unicast 
traffic allowed to pass through an interface or each  interface in a port group. When the broadcast, 
multicast, or unknown unicast traffic on the interface exceeds this threshold, the system discards packets 
until the traffic drops below this threshold.  
The storm suppression thresholds configured for an Et hernet interface might become invalid if you enable 
the storm control function for the interface. For information about the storm control function, see 
 Configuring storm control on an Ethernet interface .
  
To set storm suppression thresholds on one or multiple Ethernet interfaces: 
 
Step Command  Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter Ethernet interface 
view or port group view. 
• Enter Ethernet interface view: 
interface  interface-type 
interface-number 
•  Enter port group view: 
port-group  manual 
port-group-name   Use either command. 
To configure storm suppression 
on an Ethernet interface, enter 
Ethernet interface view. 
To configure storm suppression 
on a group of Ethernet interfaces, 
enter port group view.  
3.
  Set the broadcast 
suppression threshold ratio.  broadcast-suppression 
{ ratio  | pps  
max-pps  | kbps  max-kbps  }  Optional. 
By default, all broadcast traffic is 
allowed to pass through. 
4.
  Set the multicast 
suppression threshold ratio.  multicast-suppression 
{ ratio  | pps  
max-pps  | kbps  max-kbps  }  Optional. 
By default, all multicast traffic is 
allowed to pass through.
    Add page 222 to Favourites
    image text
    Enable zoom 
    							11 
Step Command  Remarks 
5.  Set the unknown unicast 
suppression threshold ratio.  unicast-suppression
 { ratio | pps  
max-pps  | kbps  max-kbps  }  Optional. 
By default, all unknown unicast 
traffic is allowed to pass through. 
 
 
 
NOTE: 
For an Ethernet interface that belongs to a port grou p, if you set a traffic suppression threshold for the 
interface in both Ethernet interface view and port gr oup view, the threshold configured last takes effect.
  
Setting the statistics polling interval 
To set the statistics polling interval globally or on an Ethernet interface:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter Ethernet interface view.  interface 
interface-type 
interface-number   N/A 
3.
  Set the statistics polling 
interval on the Ethernet 
interface.  flow-interval 
interval  Optional. 
The default interface statistics 
polling interval is 300 seconds. 
 
To display the interface statistics collec
ted in the last polling interval, use the display interface command.   
To clear interface statistics, use the  reset counters interface command. 
Enabling loopback detection on an Ethernet interface 
If a switch receives a packet that it sent, a loop ha s occurred to the switch. Loops might cause broadcast 
storms, which degrade network performance. You can  use this feature to detect whether a loop has 
occurred.  
Depending on whether the receiving interface is the same as the sending interface, loops fall into the 
following types: 
•   Single-port loopback—Occurs when an interface receives a packet that it sent out and the receiving 
interface is the same as the sending interface, as shown in  Figure 2.  
•   M

ulti-port loopback —Occurs when a switch receives a packet that it sent out but the receiving 
interface might not be the sending interface, as shown in  Figure 3. 
Figure 2  Single-port lo

opback
    Add page 223 to Favourites
    image text
    Enable zoom 
    							12 
Figure 3 Multi-port loopback 
 
 
You can enable loopback detection to detect loops on an interface and, if the interface supports the 
loopback-detection action  command, configure the protective action to take on the receiving interface 
when a loop is detected, for example, to shut down  the interface. Depending on whether a protective 
action is configured, the switch takes the actions in  Tabl e 1 to 
alleviate the impact of the loop condition.  
Table 1  Actions to take upon detection of a loop condition  
Port type  Actions 
No protective action is configured A protective action is configured 
Access port 
•
 Place the receiving interface in controlled mode. 
The interface does not receive or send packets. 
 
• Generate traps and log messages. 
• Delete all MAC address entries of the interface. 
• Perform the configured protective 
action. 
• Generate traps and log messages. 
• Delete all MAC address entries of the 
interface. 
Hybrid or 
trunk port 
• Generate traps and log messages. 
• If loopback detection control is enabled, place 
the receiving interface in controlled mode. The 
interface does not receive or send packets.  
• Delete all MAC address entries of the interface. 
• Generate traps and log messages. 
• If loopback detection control is 
enabled, take the configured 
protective action on the interface.  
• Delete all MAC address entries of the 
interface.  
 
Configuration restrictions and guidelines 
•  To use loopback detection on an Ethernet interface,  you must enable the function both globally and 
on the interface. 
•   To disable loopback detection  on all interfaces, run the undo loopback-detection enable  command 
in system view. 
•   To enable a hybrid or trunk port to take the administratively specified protective action, you must use 
the loopback-detection control enable  command on the port. 
•   When you change the link type of an Ethernet interface by using the  port link-type command, the 
switch removes the protective action configured on the interface. For more information about the 
port link-type  command, see  Layer 2—LAN Switching Command Reference . 
Configuration procedure 
To configure loopback detection:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A
    Add page 224 to Favourites
    image text
    Enable zoom 
    							13 
Step Command Remarks 
2.  Enable global 
loopback detection.  loopback-detection enable 
Disabled by default. 
3.  Enable multi-port 
loopback detection.  loopback-detection 
multi-port-mode enable  Optional. 
By default, multi-port loopback detection is 
disabled, and the switch can only detect 
single-port loopback. 
4.
  Set the loopback 
detection interval.  loopback-detection interval-time
 
time   Optional. 
30 seconds by default. 
5.
  Enter Ethernet 
interface view or port 
group view. 
• Enter Ethernet interface view: 
interface  interface-type 
interface-number 
•  Enter port group view: 
port-group  manual 
port-group-name  Use either command. 
To configure loopback detection on one 
interface, enter Ethernet interface view. 
To configure loopback detection on a group 
of Ethernet interfaces, enter port group view.
 
6.
  Enable loopback 
detection on the 
interface.  loopback-detection enable 
Disabled by default. 
7.  Enable loopback 
detection control on a 
trunk port or a hybrid 
port.  loopback-detection control 
enable 
Optional. 
Disabled by default. 
8.
  Enable loopback 
detection in all the 
VLANs on the trunk or 
hybrid port.  loopback-detection per-vlan 
enable  Optional. 
By default, a trunk or hybrid port performs 
loopback detection only in its port VLAN ID 
(PVID). 
9.
  Set the protective 
action to take on the 
interface when a loop 
is detected.  loopback-detection action
 
{  no-learning  | semi-block  | 
shutdown }   Optional. 
By default, a looped interface does not 
receive or send packets; the system 
generates traps and log messages, and 
deletes all MAC address entries of the 
looped interface. 
With the shutdown keyword specified, the 
switch shuts down the looped ports and set 
their physical state to Loop down. When a 
looped port recovers, you must use the 
undo 
shutdown command to restore its forwarding 
capability. 
 
Setting the MDI mode of an Ethernet interface  
  IMPORTANT: 
Fiber ports do not support the MDI mode setting. 
 
You can use both crossover and straight-through Ethe
rnet cables to connect copper Ethernet interfaces. 
To accommodate these types of cables, a copper Ethern et interface can operate in one of the following 
Medium Dependent Inte rface (MDI) modes: 
•   Across mode
    Add page 225 to Favourites
    image text
    Enable zoom 
    							14 
•  Normal mode 
•   Auto mode 
A copper Ethernet interface uses an RJ-45 connector,  which comprises eight pins, each of which plays a 
dedicated role. For example, pins 1 and 2 transmit signals, and pins 3 and 6 receive signals. The pin 
role varies by the MDI modes as follows:  
•   In normal mode, pins 1 and 2 are transmit pins, and pins 3 and 6 are receive pins.  
•   In across mode, pins 1 and 2 are receive pins, and pins 3 and 6 are transmit pins.  
•   In auto mode, the interface negotiates pin roles with its peer.  
To enable the interface to communicate with its peer, ma ke sure that its transmit pins are connected to the 
remote receive pins. If the interface can detect the connection cable type, set the interface in auto MDI 
mode. If not, set its MDI mode by using the following guidelines: 
•   When a straight-through cable is used, set the interface to operate in the  MDI mode different than 
its peer. 
•   When a crossover cable is used, set the interface to operate in the same MDI mode as its peer, or 
set either end to operate in auto mode.  
To set the MDI mode of an Ethernet interface: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter Ethernet interface view.  interface
 interface-type 
interface-number   N/A 
3.
  Set the MDI mode of the 
Ethernet interface.  mdi 
{ across  | auto  | normal }  Optional. 
By default, a copper Ethernet 
interface operates in auto mode to 
negotiate pin roles with its peer. 
 
Enabling bridging on an Ethernet interface 
When an incoming packet arrives, the device looks up the destination MAC address of the packet in the 
MAC address table. If an entry is found, but the outgoing interface is the same as the receiving interface, 
the device discards the packet.  
To enable the device to forward such packets rather 
than drop them, enable the bridging function on the 
Ethernet interface.  
To enable bridging on an Ethernet interface:  
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter Ethernet interface view.  interface 
interface-type 
interface-number   N/A 
3.
  Enable bridging on the 
Ethernet interface.  port bridge enable 
Disabled by default. 
 
Testing the cable connection of an Ethernet interface
    Add page 226 to Favourites
    image text
    Enable zoom 
    							15 
 IMPORTANT: 
•
  Fiber ports do not support this feature. 
 
•  I f  t h e  l i n k  o f  a n  E t h e r n e t  p o r t  i s  u p,  t e s t i ng its cable connection will cause the link to come down and then
go up.
  
You can test the cable connection of an Ethernet interf ace for a short or open circuit. The switch displays 
cable test results within five seconds. If any fault is de tected, the test results include the length of the faulty 
cable segment. 
To test the cable connection of an Ethernet interface: 
 
Step Command 
1.   Enter system view.  system-view 
2.  Enter Ethernet interface view. 
interface interface-type interface-number  
3.  Test the cable connected to the Ethernet 
interface.  virtual-cable-test 
 
Configuring storm control on an Ethernet interface 
Storm control compares broadcast, multicast, and unknown unicast traffic regularly with their respective 
traffic thresholds on an Ethernet interface. For ea
ch type of traffic, storm control provides a lower 
threshold and a higher threshold.  
For management purposes, you can configure the in terface to send threshold event traps and log 
messages when monitored traffic exceeds the upper  threshold or drops below the lower threshold from 
the upper threshold. 
When a particular type of traffic exceeds its upper thre shold, the interface does either of the following, 
depending on your configuration:  
•   Blocks this type of traffic, while forwarding other  types of traffic. Even though the interface does not 
forward the blocked traffic, it still counts the traffic. When the blocked traffic drops below the lower 
threshold, the port begins to forward the traffic.  
•   Shuts down automatically. The interface shuts down  automatically and stops forwarding any traffic. 
When the blocked traffic drops below the lower threshold, the port does not forward the traffic. To 
bring up the interface, use the  undo shutdown command or disable the storm control function. 
Alternatively, you can configure the storm suppression function to control a specific type of traffic. Do not 
enable them both on an Ethernet interface at th e same time because the storm suppression and storm 
control functions are mutually exclusive. For example, with an unknown unicast suppression threshold set 
on an Ethernet interface, do not enable storm cont rol for unknown unicast traffic on the interface. For 
more information about storm suppression, see  Configuring storm suppression. 
Configuration restrictions and guidelines 
•  For network stability, use the default or set a higher traffic polling interval. 
•   Storm control uses a complete polling cycle to collect traffic data, and analyzes the data in the next 
cycle. It takes a port at least one polling interval  and at most two polling intervals to take a storm 
control action. 
•   The storm control function allows you to set the upper and lower thresholds for all three types of 
packets respectively on the same interface.
    Add page 227 to Favourites
    image text
    Enable zoom 
    							16 
Configuration procedure 
To configure storm control on an Ethernet interface:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Set the traffic polling interval 
of the storm control module.  storm-constrain interval seconds
 Optional. 
10 seconds by default. 
3.
  Enter Ethernet interface view.  interface
 interface-type 
interface-number   N/A 
4.
  Enable storm control, and set 
the lower and upper 
thresholds for broadcast, 
multicast, or unknown unicast 
traffic.  storm-constrain 
{ broadcast  | 
multicast  | unicast  } {  pps |  kbps | 
ratio  } max-pps-values 
min-pps-values   Disabled by default. 
5.
  Set the control action to take 
when monitored traffic 
exceeds the upper threshold.  storm-constrain control 
{ block  | 
shutdown  }  Optional. 
Disabled by default. 
6.
  Enable the interface to send 
storm control threshold event 
traps..  storm-constrain enable trap  Optional. 
By default, the interface sends 
traps when monitored traffic 
exceeds the upper threshold or 
drops below the lower threshold 
from the upper threshold. 
7.
  Enable the interface to log 
storm control threshold 
events..  storm-constrain enable log  Optional. 
By default, the interface outputs log 
messages when monitored traffic 
exceeds the upper threshold or 
drops below the lower threshold 
from the upper threshold. 
 
Setting the MTU for a Layer 3 Ethernet interface 
(available only on the 5500 EI) 
The maximum transmission unit (MTU) affects the fragmentation and re-assembly of IP packets. 
To set the MTU for a Layer 3 Ethernet interface: 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter Ethernet interface 
view.  interface 
interface-type interface-number  N/A 
3.  Set the MTU.  
mtu size   Optional. 
1500 bytes by default.
    Add page 228 to Favourites
    image text
    Enable zoom 
    							17 
Displaying and maintaining an Ethernet interface 
 
Task Command Remarks 
Display Ethernet interface 
information.  display interface 
[ interface-type  ]  brief  [ down  ] [ | { begin  
|  exclude  | include  } regular-expression ] 
display interface interface-type interface-number  [ brief ] 
[ |  { begin |  exclude | include  } regular-expression ]  Available in 
any view
 
Display traffic statistics for the 
specified interfaces.  display counters {
 inbound | outbound  } interface 
[ interface-type  ] [ | { begin  | exclude  | include  } 
regular-expression  ]  Available in 
any view 
Display traffic rate statistics over 
the last sampling interval. display counters rate 
{ inbound  | outbound  } interface 
[ interface-type  ] [ | { begin  | exclude  | include  } 
regular-expression  ]  Available in 
any view 
Display information about 
discarded packets on the 
specified interfaces. display packet-drop interface 
[ interface-type 
[ interface-number  ] ] [ | { begin  | exclude  | include  } 
regular-expression  ]  Available in 
any view 
Display summary information 
about discarded packets on all 
interfaces. display packet-drop summary
 [ | { begin |  exclude | 
include  } regular-expression  ]  Available in 
any view 
Display the combo interfaces 
and the fiber and copper combo 
ports.  display port 
combo [ | { begin  | exclude |  include } 
regular-expression  ]   Available in 
any view 
Display information about a 
manual port group or all manual 
port groups. display port-group manual 
[ all  | name  port-group-name  ] 
[ |  { begin |  exclude | include } regular-expression  ]  Available in 
any view 
Display information about the 
loopback function.  display loopback-detection
 [ | { begin | exclude  | include } 
regular-expression  ]   Available in 
any view 
Clear the interface statistics. 
reset counters interface
 [  interface-type 
[ interface-number  ] ]  Available in 
user view 
Clear the statistics of discarded 
packets on the specified 
interfaces. reset packet-drop interface 
[ interface-type 
[ interface-number  ] ]  Available in 
user view
    Add page 229 to Favourites
    image text
    Enable zoom 
    							 18 
Configuring loopback and null interfaces 
Configuring a loopback interface 
Introduction to the loopback interface 
A loopback interface is a software-only virtual interface. It delivers the following benefits: 
•  The physical layer state and link-layer protocols  of a loopback interface are always up unless the 
loopback interface is manually shut down.  
•   To save IP address resources, you can assign an IP address with an all-F mask to a loopback 
interface. When you assign an IPv4 address whos e mask is not 32-bit, the system automatically 
changes the mask into a 32-bit mask. When you assign an IPv6 address whose mask is not 128-bit, 
the system automatically changes the mask into a 128-bit mask.  
•   You can enable routing protocols on a loopback in terface, and a loopback interface can send and 
receive routing protocol packets. 
Because of the benefits mentioned above, loopbac k interfaces are widely used in the following 
scenarios: 
•   You can configure a loopback interface address as the source address of the IP packets that the 
device generates. Because loopback interface addr esses are stable unicast addresses, they are 
usually used as device identifications. When you configure a rule on an authentication or security 
server to permit or deny packets generated by a de vice, you can simplify the rule by configuring it 
to permit or deny packets that carry the loopback interface address identifying the device. When 
you use a loopback interface address as the source address of IP packets, be sure to perform any 
necessary routing configuration to make sure that  the route from the loopback interface to the peer 
is reachable. All data packets sent to the loopbac k interface are treated as packets sent to the 
device itself, so the device does not forward these packets. 
•   Because a loopback interface is always up, it can be used in dynamic routing protocols. For 
example, if you do not configure a router ID fo r a dynamic routing protocol, the highest loopback 
interface IP address is selected as the router ID. In BGP, to prevent physical port failure from 
interrupting BGP sessions, you can use a loopback interface as the source interface of BGP packets.   
Configuration procedure  
Step Command Remarks 
1.   Enter system view. 
system-view N/A 
2.  Create a loopback interface 
and enter loopback interface 
view.  interface loopback
 
interface-number  N/A 
3.
  Set the interface description. 
description text  Optional 
By default, the description of a loopback 
interface is 
interface name  Interface.
    Add page 230 to Favourites
    image text
    Enable zoom 
    							 19 
Step Command Remarks 
4.  Shut down the loopback 
interface.  shutdown Optional 
By default, a loopback interface is up. 
5.
  Restore the default settings for 
the loopback interface.  default 
Optional 
 
 NOTE: 
You can configure settings such as IP addresses  and IP routes on loopback interfaces. For more 
information, see 
Layer 3—IP Services Configuration Guide and Layer 3—IP Routing Configuration Guide. 
Configuring a null interface 
Introduction to the null interface 
A null interface is a completely software-based logica l interface, and is always up. However, you cannot 
use it to forward data packets or configure an IP addres s or link-layer protocol on it. With a null interface 
specified as the next hop of a static route to a sp ecific network segment, any packets routed to the 
network segment are dropped. The null interface provid es a simpler way to filter packets than ACL. You 
can filter uninteresting traffic by transmitting it  to a null interface instead of applying an ACL.  
For example, by executing the ip route-static 92.101.0.0 255.255.0.0 null 0  command (which configures 
a static route that leads to null interface 0), you can  have all the packets destined to the network segment 
92.101.0.0/16 discarded. 
O n l y  o n e  n u l l  i n t e r f a c e ,  N u l l  0 ,  i s  s u p p o r t e d  o n  y o u r  s w i t c h .  Yo u  c a n n o t  r e m o v e  o r  c re a t e  a  n u l l  i n t e r f a c e .    
Configuration procedure  
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter null interface 
view.  interface null 0  The Null 0 interface is the default null interface on 
your switch. It cannot be manually created or 
removed. 
3.
  Set the interface 
description.  description 
text  Optional 
By default, the description of a null interface is 
interface name
 Interface. 
4.  Restore the default 
settings for the null 
interface.  default 
Optional 
 
Displaying and maintaining loopback and null 
interfaces
    All HP manuals Comments (0)

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