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+.
140 Send operation times: 1000 Receive response times: 1000 \ Min/Max/Average round trip time: 31/1328/33 Square-Sum of round trip time: 2844813 Last succeeded probe time: 2011-01-13 09:49:31.1 Extended results: Packet loss in test: 0% Failures due to timeout: 0 Failures due to disconnect: 0 Failures due to no connection: 0 Failures due to sequence error: 0 Failures due to internal error: 0 Failures due to other errors: 0 Packet(s) arrived late: 0 Voice results: RTT number: 1000 Min positive SD: 1 Min positive DS: 1 Max positive SD: 204 Max positive DS: 1297 Positive SD number: 257 Positive DS number: 259 Positive SD sum: 759 Positive DS sum: 1797 Positive SD average: 2 Positive DS average: 6 Positive SD square sum: 54127 Positive DS square sum: 169\ 1967 Min negative SD: 1 Min negative DS: 1 Max negative SD: 203 Max negative DS: 1297 Negative SD number: 255 Negative DS number: 259 Negative SD sum: 759 Negative DS sum: 1796 Negative SD average: 2 Negative DS average: 6 Negative SD square sum: 53655 Negative DS square sum: 169\ 1776 One way results: Max SD delay: 343 Max DS delay: 985 Min SD delay: 343 Min DS delay: 985 Number of SD delay: 1 Number of DS delay: 1 Sum of SD delay: 343 Sum of DS delay: 985 Square sum of SD delay: 117649 Square sum of DS delay: 970\ 225 SD lost packet(s): 0 DS lost packet(s): 0 Lost packet(s) for unknown reason: 0 Voice scores: MOS value: 4.38 ICPIF value: 0 # Display the statistics of voice tests. [DeviceA] display nqa statistics admin test NQA entry (admin admin, tag test) test statistics: NO. : 1 Destination IP address: 10.2.2.2 Start time: 2011-01-13 09:45:37.8 Life time: 331 seconds Send operation times: 4000 Receive response times: 4000 \ Min/Max/Average round trip time: 15/1328/32 Square-Sum of round trip time: 7160528 Extended results:
141 Packet loss in test: 0% Failures due to timeout: 0 Failures due to disconnect: 0 Failures due to no connection: 0 Failures due to sequence error: 0 Failures due to internal error: 0 Failures due to other errors: 0 Packet(s) arrived late: 0 Voice results: RTT number: 4000 Min positive SD: 1 Min positive DS: 1 Max positive SD: 360 Max positive DS: 1297 Positive SD number: 1030 Positive DS number: 1024 Positive SD sum: 4363 Positive DS sum: 5423 Positive SD average: 4 Positive DS average: 5 Positive SD square sum: 497725 Positive DS square sum: 225\ 4957 Min negative SD: 1 Min negative DS: 1 Max negative SD: 360 Max negative DS: 1297 Negative SD number: 1028 Negative DS number: 1022 Negative SD sum: 1028 Negative DS sum: 1022 Negative SD average: 4 Negative DS average: 5 Negative SD square sum: 495901 Negative DS square sum: 541\ 9 One way results: Max SD delay: 359 Max DS delay: 985 Min SD delay: 0 Min DS delay: 0 Number of SD delay: 4 Number of DS delay: 4 Sum of SD delay: 1390 Sum of DS delay: 1079 Square sum of SD delay: 483202 Square sum of DS delay: 973\ 651 SD lost packet(s): 0 DS lost packet(s): 0 Lost packet(s) for unknown reason: 0 Voice scores: Max MOS value: 4.38 Min MOS value: 4.38 Max ICPIF value: 0 Min ICPIF value: 0 NOTE: The display nqa history command cannot show you the results of voice tests. To know the result of a voice test, use the display nqa result command to view the probe results of the latest NQA test, or use the display nqa statistics command to view the statistics of NQA tests. DLSw test configuration example Network requirements As shown in Figure 50, conf igure NQA DLSw tests to test the response time of the DLSw device.
142 Figure 50 Network diagram Configuration procedure Before you make the configuration, make sure the devices can reach each other. # Create a DLSw test group, and configure DLSw probe packets to use 10.2.2.2 as the destination IP address. system-view [DeviceA] nqa entry admin test [DeviceA-nqa-admin-test] type dlsw [DeviceA-nqa-admin-test-dlsw] destination ip 10.2.2.2 # Enable the saving of history records. [DeviceA-nqa-admin-test-dlsw] history-record enable [DeviceA-nqa-admin-test-dlsw] quit # Start DLSw tests. [DeviceA] nqa schedule admin test start-time now lifetime forever # Stop the DLSw tests after a period of time. [DeviceA] undo nqa schedule admin test # Display the result of the last DLSw test. [DeviceA] display nqa result admin test NQA entry (admin admin, tag test) test results: Destination IP address: 10.2.2.2 Send operation times: 1 Receive response times: 1 Min/Max/Average round trip time: 19/19/19 Square-Sum of round trip time: 361 Last succeeded probe time: 2011-01-22 10:40:27.7 Extended results: Packet loss in test: 0% Failures due to timeout: 0 Failures due to disconnect: 0 Failures due to no connection: 0 Failures due to sequence error: 0 Failures due to internal error: 0 Failures due to other errors: 0 Packet(s) arrived late: 0 # Display the history of DLSw tests. [DeviceA] display nqa history admin test NQA entry (admin admin, tag test) history record(s): Index Response Status Time 1 19 Succeeded 2011-01-22 10:40:27.7
143 NQA collaboration configuration example Network requirements As shown in Figure 51, configure a static route to Device C on Device A, with Device B as the next hop. Associate the static route, track entr y, and NQA test group to verify whether static route is active in real time. Figure 51 Network diagram Configuration procedure 1. Assign each interface an IP address. (Details not shown.) 2. On Device A, configure a unicast static route an d associate the static route with a track entry. # Configure a static route, whose destination addr ess is 10.2.1.1, and associate the static route with track entry 1. system-view [DeviceA] ip route-static 10.1.1.2 24 10.2.1.1 track 1 3. On Device A, create an NQA test group: # Create an NQA test group with the administrator name being admin and operation tag being test . [DeviceA] nqa entry admin test # Configure the test type of the NQA test group as ICMP echo. [DeviceA-nqa-admin-test] type icmp-echo # Configure ICMP echo requests to use 10.2.1.1 as their destination IP address. [DeviceA-nqa-admin-test-icmp-echo] destination ip 10.2.1.1 # Configure the device to perform test s at an interval of 100 milliseconds. [DeviceA-nqa-admin-test-icmp-echo] frequency 100 # Create reaction entry 1. If the number of co nsecutive probe failures reaches 5, collaboration with other modules is triggered. [DeviceA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail\ threshold-type consecutive 5 action-type trigger-only [DeviceA-nqa-admin-test-icmp-echo] quit # Configure the test start time and test duration for the test group. [DeviceA] nqa schedule admin test start-time now lifetime forever 4. On Device A, create the track entry: # Create track entry 1, and associate it with reac tion entry 1 of the NQA test group (admin-test). [DeviceA] track 1 nqa entry admin test reaction 1
144 Verifying the configuration # On Device A, display information about all the track entries. [DeviceA] display track all Track ID: 1 Status: Positive Notification delay: Positive 0, Negative 0 (in seconds) Reference object: NQA entry: admin test Reaction: 1 # Display brief information about active ro utes in the routing table on Device A. [DeviceA] display ip routing-table Routing Tables: Public Destinations : 5 Routes : 5 Destination/Mask Proto Pre Cost NextHop Interface 10.1.1.0/24 Static 60 0 10.2.1.1 Vlan3 10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan3 10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0 127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0 The output shows that the static route with the ne xt hop 10.2.1.1 is active, and the status of the track entry is positive. The static route configuration works. # Remove the IP address of VLAN-interface 3 on Device B. system-view [DeviceB] interface vlan-interface 3 [DeviceB-Vlan-interface3] undo ip address # On Device A, display information about all the track entries. [DeviceA] display track all Track ID: 1 Status: Negative Notification delay: Positive 0, Negative 0 (in seconds) Reference object: NQA entry: admin test Reaction: 1 # Display brief information about active ro utes in the routing table on Device A. [DeviceA] display ip routing-table Routing Tables: Public Destinations : 4 Routes : 4 Destination/Mask Proto Pre Cost NextHop Interface 10.2.1.0/24 Direct 0 0 10.2.1.2 Vlan3 10.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0 127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
145 The output shows that the next hop 10.2.1.1 of the static route is not reachable, and the status of the track entry is negative. Th e static route does not work.
146 Configuring sFlow Both bridge mode (Layer 2) and route mode (Layer 3) Ethernet ports support sFlow. The term interface i n t h i s ch a p t e r c o l l e c t ive ly refe r s t o t h e s e t wo t yp e s o f p o r t s. Yo u c a n u s e t h e port link-mode command to set an Ethernet port to operate in bridge or route mode (see Layer 2—LAN Switching Configuration Guide). sFlow overview Introduction to sFlow Sampled Flow (sFlow) is a traffic monitoring technology mainly used to collect and analyze traffic statistics. As shown in Figure 52, the sF low system involves an sFlow agent embedded in a device and a remote sFlow collector. The sFlow agent collects traffic stat istics and packet information from the sFlow-enabled interfaces and encapsulates them into sFlow packets . When the sFlow packet buffer is full, or the age time of sFlow packets is reached, (the age time is one second), the sFlow agent sends the packets to a specified sFlow collector. The sFlow collector anal yzes the sFlow packets and displays the results. sFlow has the following two sampling mechanisms: • Flow sampling: Packet-based sampling, used to obtain packet content information. • Counter sampling: Time-based sampling, used to obtain port traffic statistics. Figure 52 sFlow system As a traffic monitoring technology, sFlow has the following advantages: • Supporting traffic monitoring on Gigabit and higher-speed networks. • Providing good scalability to allow one sFlow collector to monitor multiple sFlow agents. • Saving cost by embedding the sFlow agent in a device, instead of using a dedicated sFlow agent device. NOTE: Only the sFlow agent function is supported on the switch. Device sFlow collector Ethernet headerUDPheadersFlow DatagramIPheaderFlow sampling Counter sampling sFlow agent
147 sFlow operation sFlow operates in the following ways: 1. Before enabling the sFlow function, configure the sFlow agent and sFlow collector on the device. 2. With flow sampling enabled on an Ethernet interface, the sFlow agent samples packets and encapsulates them into sFlow packe ts. For the configuration, see Configuring flow sampling. 3. With counter sampling enabled on an Ethernet inte rface, the sFlow agent periodically collects the statistics of the interface and encapsulates the statistics into sFlow packets. For the configuration, see Configuring flow sampling . Configuring sFlow Before configuring sFlow, complete the following tasks: • Configure the IP address, flow sampling, and counter sampling of the sFlow collector on the device. • Configure the sFlow collector. Configuring the sFlow agent and sFlow collector The sFlow feature enables the remote sFlow collecto r to monitor the network and analyze sFlow packet statistics. To configure the sFlow agent and sFlow collector: Step Command Remarks 1. Enter system view. system-view N/A 2. Specify the IP address for the sFlow agent. sflow agent { ip ip-address | ipv6 ipv6-address } Optional Not specified by default. The device periodically checks the existence of the sFlow agent address. If the sFlow agent has no IP address configured, the device automatically selects an interface IP address for the sFlow agent but does not save the selected IP address. NOTE: • HP recommends configuring an IP address manually for the sFlow agent. • Only one IP address can be specified for the sFlow agent on the device. 3. Configure the sFlow collector. sflow collector collector-id { { ip ip-address | ipv6 ipv6-address } | datagram-size size | description text | port port-number | time-out seconds } * By default, the device presets a number of sFlow collectors. Use the display sflow command to display the parameters of the preset sFlow collectors. 4. Specify the source IP address of sent sFlow packets. sflow source { ip ip-address | ipv6 ipv6-address } * Optional Not specified by default.
148 Configuring flow sampling Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet interface view/Layer 3 Ethernet interface view. interface interface-type interface-number Only the HP 5500 EI switch series supports this command on Layer 3 Ethernet interfaces. 3. Set the Flow sampling mode. sflow sampling-mode { determine | random } Optional random by default. 4. Set the interval for flow sampling. sflow sampling-rate interval Not set by default. 5. Set the maximum copied length of a sampled packet. sflow flow max-header length Optional By default, up to 128 bytes of a sampled packet can be copied. You are recommended to use the default value. 6. Specify the sFlow collector for flow sampling. sflow flow collector collector-id No collector is specified for flow sampling by default. NOTE: The switch does not support the flow sampling mode determine. Configuring counter sampling Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 interface view/Layer 3 Ethernet interface view. interface interface-type interface-number Only the HP 5500 EI switch series supports Layer 3 Ethernet interface view. 3. Set the interval for counter sampling. sflow counter interval seconds Counter sampling is disabled by default. 4. Specify the sFlow collector for counter sampling. sflow counter collector collector-id No collector is specified for counter sampling by default. Displaying and maintaining sFlow Task Command Remarks Display sFlow configuration information. display sflow [ slot slot-number ] [ | { begin | exclude | include } regular-expression ] Available in any view
149 sFlow configuration example Network requirements As shown in Figure 53, Ho st A is connected with the server through the device (sFlow agent). Enable sFlow (including flow sampling and counter sampling) on GigabitEthernet 1/0/1 to monitor traffic on the port. The device sends sFlow packets through GigabitEthernet 1/0/3 to the sFlow collector, which analyzes the sFlow packets and displays results. Figure 53 Network diagram Configuration procedure 1. Configure the sFlow agent and sFlow collector: # Configure the IP address of vlan-int erface 1 on Device as 3.3.3.1/16. system-view [Device] interface vlan-interface 1 [Device-Vlan-interface1] ip address 3.3.3.1 16 [Device-Vlan-interface1] quit # Specify the IP address for the sFlow agent. [Device] sflow agent ip 3.3.3.1 # Specify sFlow collector ID 2, IP address 3.3.3. 2, the default port number, and description of netserver for the sFlow collector. [Device] sflow collector 2 ip 3.3.3.2 description netserver 2. Configure counter sampling: # Set the counter sampling interval to 120 seconds. [Device] interface gigabitethernet 1/0/1 [Device-GigabitEthernet1/0/1] sflow counter interval 120 # Specify sFlow collector 2 for counter sampling. [Device-GigabitEthernet1/0/1] sflow counter collector 2 3. Configure flow sampling: # Set the Flow sampling mode and sampling interval. [Device-GigabitEthernet1/0/1] sflow sampling-mode random [Device-GigabitEthernet1/0/1] sflow sampling-rate 4000 # Specify sFlow collector 2 for flow sampling. [Device-GigabitEthernet1/0/1] sflow flow collector 2 3.3.3.2/16 Host A1.1.1.1/16 VLAN 1 3.3.3.1/16 GE1/0/2 2.2.2.1/16 GE1/0/1 1.1.1.2/16Server2.2.2.2/16Device sFlow Collector