HP 5500 EI series User manual
HP 5500 EI & 5500 SI Switch Series
Network Management and Monitoring
Configuration Guide
Part number: 5998-1722
Software version: Release 2220
Document version: 6W100-20130810
Legal and notice information
© Copyright 2013 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained
herein.
i
Contents
Using ping, tracert, and system debugging··············································································································· 1
Ping·····················································································································································································1
Using a ping command to test network connectivity ····························································································1
Ping example ····························································································································································1
Tracert ················································································································································································3
Prerequisites ······························································································································································4
Using a tracert command to identify failed or all nodes in a path·····································································5
System debugging ····························································································································································5
Debugging information control switches················································································································5
Debugging a feature module ··································································································································6
Ping and tracert example ·················································································································································7
Configuring NTP ·························································································································································· 9
Overview············································································································································································9
NTP application························································································································································9
NTP advantages ·······················································································································································9
How NTP works····················································································································································· 10
NTP message format ············································································································································· 11
Operation modes ·················································································································································· 12
NTP configuration task list············································································································································· 15
Configuring NTP operation modes ······························································································································ 15
Configuring the client/server mode ···················································································································· 15
Configuring the symmetric peers mode ·············································································································· 16
Configuring the broadcast mode························································································································· 17
Configuring the multicast mode ··························································································································· 18
Configuring optional parameters ································································································································· 19
Specifying the source interface for NTP messages···························································································· 19
Disabling an interface from receiving NTP messages······················································································· 19
Configuring the allowed maximum number of dynamic sessions···································································· 20
Configuring the DSCP value for NTP messages································································································· 20
Configuring access-control rights ································································································································· 21
Configuration prerequisites ·································································································································· 21
Configuration procedure ······································································································································ 21
Configuring NTP authentication ··································································································································· 22
Configuring NTP authentication in client/server mode····················································································· 22
Displaying and maintaining NTP ································································································································· 23
NTP configuration examples········································································································································· 24
Configuring the client/server mode ···················································································································· 24
Configuring the NTP symmetric mode ················································································································ 25
ii
Configuring NTP broadcast mode······················································································································· 27
Configuring NTP multicast mode ························································································································· 28
Configuring NTP client/server mode with authentication················································································· 31
Configuring NTP broadcast mode with authentication ····················································································· 32
Configuring the information center···························································································································36
Overview········································································································································································· 36
Classification of system information ···················································································································· 37
System information levels ····································································································································· 37
Output channels and destinations ······················································································································· 37
Outputting system information by source module······························································································ 38
Default output rules of system information ·········································································································· 38
System information formats ·································································································································· 39
FIPS compliance ····························································································································································· 43
Information center configuration task list····················································································································· 43
Outputting system information to the console ············································································································· 43
Outputting system information to the monitor terminal ······························································································ 44
Outputting system information to a log host ··············································································································· 45
Outputting system information to the trap buffer ········································································································ 46
Outputting system information to the log buffer·········································································································· 46
Outputting system information to the SNMP module ································································································· 47
Outputting system information to the Web interface·································································································· 48
Managing security logs and the security log file········································································································ 49
Saving security logs into the security log file······································································································ 49
Managing the security log file ····························································································································· 50
Enabling synchronous information output ··················································································································· 52
Disabling an interface from generating link up or link down logging information ················································ 52
Displaying and maintaining information center ········································································································· 53
Information center configuration examples ················································································································· 53
Outputting log information to a UNIX log host ·································································································· 53
Outputting log information to a Linux log host··································································································· 55
Outputting log information to the console ·········································································································· 56
Saving security logs into the security log file······································································································ 57
Configuring SNMP·····················································································································································61
Overview········································································································································································· 61
SNMP framework·················································································································································· 61
MIB and view-based MIB access control ············································································································ 61
SNMP operations ·················································································································································· 62
SNMP protocol versions ······································································································································· 62
SNMP configuration task list········································································································································· 63
Configuring SNMP basic parameters·························································································································· 63
Configuring SNMPv3 basic parameters············································································································· 63
Configuring SNMPv1 or SNMPv2c basic parameters······················································································ 64
Switching the NM-specific interface index format······································································································ 66
iii
Configuration guidelines ······································································································································ 67
Configuration procedure ······································································································································ 67
Configuring SNMP logging ·········································································································································· 68
Configuring SNMP traps··············································································································································· 68
Enabling SNMP traps ··········································································································································· 68
Configuring the SNMP agent to send traps to a host ······················································································· 69
Displaying and maintaining SNMP ····························································································································· 70
SNMP configuration examples····································································································································· 71
SNMPv1/SNMPv2c configuration example ······································································································ 71
SNMPv3 configuration example·························································································································· 73
SNMP logging configuration example ··············································································································· 74
Configuring RMON ···················································································································································77
Overview········································································································································································· 77
Working mechanism············································································································································· 77
RMON groups ······················································································································································· 77
Configuring the RMON statistics function ··················································································································· 79
Configuring the RMON Ethernet statistics function···························································································· 80
Configuring the RMON history statistics function ······························································································ 80
Configuring the RMON alarm function ······················································································································· 81
Displaying and maintaining RMON ···························································································································· 82
Ethernet statistics group configuration example ········································································································· 82
History group configuration example ·························································································································· 83
Alarm group configuration example···························································································································· 85
Configuring port mirroring ········································································································································87
Introduction to port mirroring········································································································································ 87
Terminologies of port mirroring ··························································································································· 87
Port mirroring classification and implementation······························································································· 88
Configuring local port mirroring ·································································································································· 90
Local port mirroring configuration task list ········································································································· 90
Creating a local mirroring group ························································································································ 90
Configuring source ports for the local mirroring group ···················································································· 90
Configuring the monitor port for the local mirroring group·············································································· 91
Using the remote probe VLAN to enable local mirroring to support multiple monitor ports························· 92
Configuring Layer 2 remote port mirroring ················································································································· 94
Layer 2 remote port mirroring configuration task list ························································································ 94
Configuring a remote destination group (on the destination device) ······························································ 95
Configuring a remote source group (on the source device) ············································································· 96
Displaying and maintaining port mirroring················································································································· 99
Port mirroring configuration examples························································································································· 99
Local port mirroring configuration example ······································································································· 99
Local port mirroring with multiple monitor ports configuration example·······················································100
Layer 2 remote port mirroring configuration example ····················································································102
iv
Configuring traffic mirroring ·································································································································· 105
Introduction to traffic mirroring···································································································································105
Traffic mirroring configuration task list ······················································································································105
Configuring match criteria ··········································································································································105
Configuring traffic mirroring of different types ·········································································································106
Mirroring traffic to a port ···································································································································106
Mirroring traffic to the CPU································································································································106
Configuring a QoS policy···········································································································································107
Applying a QoS policy ···············································································································································107
Apply a QoS policy to a port ····························································································································107
Apply a QoS policy to a VLAN·························································································································107
Apply a QoS policy globally ·····························································································································108
Apply a QoS policy to the control plane··········································································································108
Displaying and maintaining traffic mirroring············································································································108
Traffic mirroring configuration example ····················································································································109
Traffic mirroring configuration example ···········································································································109
Configuring NQA ··················································································································································· 112
Overview·······································································································································································112
NQA features ······················································································································································112
NQA concepts·····················································································································································114
NQA probe operation procedure ·····················································································································115
NQA configuration task list ········································································································································116
Configuring the NQA server ······································································································································117
Enabling the NQA client·············································································································································117
Creating an NQA test group······································································································································117
Configuring an NQA test group ································································································································118
Configuring ICMP echo tests······························································································································118
Configuring DHCP tests ······································································································································119
Configuring DNS tests ········································································································································120
Configuring FTP tests···········································································································································121
Configuring HTTP tests ········································································································································122
Configuring UDP jitter tests·································································································································123
Configuring SNMP tests ·····································································································································124
Configuring TCP tests··········································································································································125
Configuring UDP echo tests································································································································126
Configuring voice tests ·······································································································································127
Configuring DLSw tests ·······································································································································129
Configuring the collaboration function ······················································································································130
Configuring threshold monitoring·······························································································································130
Configuration prerequisites ································································································································130
Configuration guidelines ····································································································································130
Configuration procedure ····································································································································131
Configuring the NQA statistics collection function···································································································133
v
Configuring the history records saving function ·······································································································133
Configuring optional parameters for an NQA test group·······················································································134
Configuring a schedule for an NQA test group·······································································································135
Configuration prerequisites ································································································································135
Configuration guidelines ····································································································································136
Configuration procedure ····································································································································136
Displaying and maintaining NQA·····························································································································136
NQA configuration examples ····································································································································137
ICMP echo test configuration example ·············································································································137
DHCP test configuration example······················································································································139
DNS test configuration example························································································································140
FTP test configuration example ··························································································································141
HTTP test configuration example························································································································142
UDP jitter test configuration example ················································································································144
SNMP test configuration example ·····················································································································146
TCP test configuration example ·························································································································148
UDP echo test configuration example ···············································································································149
Voice test configuration example ······················································································································150
DLSw test configuration example·······················································································································153
NQA collaboration configuration example······································································································154
Configuring sFlow··················································································································································· 157
sFlow configuration task list ········································································································································158
Configuring the sFlow agent and sFlow collector ····································································································158
Configuring flow sampling··········································································································································158
Configuring counter sampling ····································································································································159
Displaying and maintaining sFlow·····························································································································159
sFlow configuration example······································································································································160
Network requirements·········································································································································160
Configuration procedure ····································································································································160
Troubleshooting sFlow configuration ·························································································································161
Symptom·······························································································································································161
Analysis ································································································································································161
Solution·································································································································································162
Configuring IPC······················································································································································· 163
Overview·······································································································································································163
Node·····································································································································································163
Link········································································································································································163
Channel ································································································································································163
Packet sending modes ········································································································································164
Enabling IPC performance statistics ···························································································································164
Displaying and maintaining IPC·································································································································165
vi
Configuring PoE ······················································································································································ 166
Overview·······································································································································································166
PoE configuration task list ···········································································································································166
Enabling PoE for a PoE interface································································································································167
Detecting PDs································································································································································168
Enabling the PSE to detect nonstandard PDs ···································································································168
Configuring a PD disconnection detection mode ····························································································169
Configuring the maximum PoE interface power ·······································································································169
Configuring PoE interface power management········································································································169
Configuring the PoE monitoring function···················································································································170
Configuring PSE power monitoring···················································································································171
Monitoring PD······················································································································································171
Configuring PoE interface through PoE profile ·········································································································171
Configuring PoE profile ······································································································································171
Applying a PoE profile········································································································································172
Upgrading PSE processing software in service ········································································································172
Displaying and maintaining PoE ································································································································173
PoE configuration example ·········································································································································174
Troubleshooting PoE ····················································································································································175
Setting the priority of a PoE interface to critical fails·······················································································175
Failure to apply a PoE profile to a PoE interface·····························································································175
Configuring cluster management··························································································································· 176
Overview·······································································································································································176
Roles in a cluster··················································································································································176
How a cluster works············································································································································177
Configuration restrictions and guidelines··················································································································180
Cluster management configuration task list···············································································································181
Configuring the management switch ·························································································································182
Enabling NDP globally and for specific ports··································································································182
Configuring NDP parameters ····························································································································182
Enabling NTDP globally and for specific ports································································································183
Configuring NTDP parameters···························································································································183
Manually collecting topology information ········································································································184
Enabling the cluster function ······························································································································184
Establishing a cluster···········································································································································185
Enabling management VLAN autonegotiation·································································································185
Configuring communication between the management switch and the member switches within a cluster
··············································································································································································186
Configuring cluster management protocol packets ·························································································187
Cluster member management ····························································································································188
Configuring the member switches ······························································································································188
Enabling NDP ······················································································································································188
Enabling NTDP ····················································································································································188
vii
Manually collecting topology information ········································································································189
Enabling the cluster function ······························································································································189
Deleting a member switch from a cluster··········································································································189
Toggling between the CLIs of the management switch and a member switch······················································189
Adding a candidate switch to a cluster·····················································································································190
Configuring advanced cluster management functions ·····························································································190
Configuring topology management ··················································································································190
Configuring interaction for a cluster··················································································································191
Configuring the SNMP configuration synchronization function·····································································192
Configuring Web user accounts in batches ·····································································································193
Displaying and maintaining cluster management ····································································································193
Cluster management configuration example ············································································································194
Network requirements·········································································································································194
Configuration procedure ····································································································································195
Configuring a stack················································································································································· 198
Hardware compatibility and other restrictions··········································································································198
Stack configuration task list·········································································································································198
Configuring the stack master device··························································································································199
Configuring a private IP address pool for the stack ························································································199
Configuring stack ports·······································································································································199
Creating a stack ··················································································································································199
Configuring stack ports on a member device···········································································································200
Logging in to the CLI of a member from the master ·································································································200
Displaying and maintaining stack configuration ······································································································200
Stack configuration example ······································································································································201
Configuring CWMP················································································································································ 203
Hardware compatibility···············································································································································203
Overview·······································································································································································203
CWMP network framework································································································································203
Basic CWMP functions ·······································································································································204
CWMP mechanism ·············································································································································205
CWMP configuration methods ···································································································································208
Configuring ACS and CPE attributes through DHCP·······················································································208
Configuring the DNS server·······························································································································209
Configuring ACS and CPE attributes through ACS ·························································································209
Configuring CWMP at the CLI···························································································································209
Enabling CWMP ··························································································································································210
Configuring ACS attributes ·········································································································································210
Configuring the ACS URL ···································································································································210
Configuring the ACS username and password ·······························································································211
Configuring CPE attributes··········································································································································211
Configuring the CPE username and password ································································································211
Configuring the CWMP connection interface ··································································································212
viii
Sending Inform messages···································································································································212
Configuring the maximum number of attempts made to retry a connection·················································213
Configuring the close-wait timer of the CPE ·····································································································213
Configuring the CPE working mode··················································································································214
Specifying an SSL client policy for HTTPS connection to ACS ·······································································214
Displaying and maintaining CWMP··························································································································215
CWMP configuration example···································································································································215
Configuration guidelines ····································································································································215
Network requirements·········································································································································215
Configuration procedure ····································································································································216
Verifying the configuration on the ACS server·································································································222
Support and other resources ·································································································································· 224
Contacting HP ······························································································································································224
Subscription service ············································································································································224
Related information······················································································································································224
Documents····························································································································································224
Websites·······························································································································································224
Conventions ··································································································································································225
Index ········································································································································································ 227
1
Using ping, tracert, and system debugging
Use the ping, tracert, and system debugging utilities to test network connectivity and identify network
problems.
Ping
The ping utility sends ICMP echo requests (ECHO-REQUEST) to the destination device. Upon receiving
the requests, the destination device responds with ICMP echo replies (ECHO-REPLY) to the source device.
The source device outputs statistics about the ping operation, including the number of packets sent,
number of echo replies received, and the round-trip time. You can measure the network performance by
analyzing these statistics.
Using a ping command to test network connectivity
Task Command
Remarks
Check whether a specified
address in an IP network is
reachable.
•For an IPv4 network:
ping [ ip ] [ -asource-ip | -c count | -f | -h
ttl | -iinterface-type interface-number | -m
interval | -n | -p pad | -q | -r | -s
packet-size | -t timeout | -tos tos | -v |
-vpn-instance vpn-instance-name ] * host
•For an IPv6 network:
ping ipv6 [ -a source-ipv6 | -c count | -m
interval | -s packet-size | -t timeout |-tos
tos| -vpn-instance vpn-instance-name ] *
host [ -i interface-type interface-number ]
Use one of the commands.
Available in any view.
Only the HP 5500 EI Switch
Series supports the vpn-instance
keyword.
IMPORTANT:
W
hen you configure the ping command for a low-speed network, HP recommends that you set a lar
g
er
v
alue for the timeout timer (indicated by the -t keyword in the command).
Ping example
Network requirements
Test the network connectivity between Device A and Device C in Figure 1. If they can reach each other,
get detailed information about routes from Device A to Device C.
2
Figure 1 Network diagram
Test procedure
# Use the ping command on Device A to test connectivity to Device C.
<DeviceA> ping 1.1.2.2
PING 1.1.2.2: 56 data bytes, press CTRL_C to break
Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=205 ms
Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms
Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/41/205 ms
# Get detailed information about routes from Device A to Device C.
<DeviceA> ping -r 1.1.2.2
PING 1.1.2.2: 56 data bytes, press CTRL_C to break
Reply from 1.1.2.2: bytes=56 Sequence=1 ttl=254 time=53 ms
Record Route:
1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
Reply from 1.1.2.2: bytes=56 Sequence=2 ttl=254 time=1 ms
Record Route:
1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
Reply from 1.1.2.2: bytes=56 Sequence=3 ttl=254 time=1 ms
Record Route:
1.1.2.1
1.1.2.2
3
1.1.1.2
1.1.1.1
Reply from 1.1.2.2: bytes=56 Sequence=4 ttl=254 time=1 ms
Record Route:
1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
Reply from 1.1.2.2: bytes=56 Sequence=5 ttl=254 time=1 ms
Record Route:
1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/11/53 ms
The test procedure with the ping –r command (see Figure 1) is as follows:
1. The source (Device A) sends an ICMP echo request with the RR option being empty to the
destination (Device C).
2. The intermediate device (Device B) adds the IP address of its outbound interface (1.1.2.1) to the RR
option of the ICMP echo request, and forwards the packet.
3. Upon receiving the request, the destination device copies the RR option in the request and adds the
IP address of its outbound interface (1.1.2.2) to the RR option. Then the destination device sends
an ICMP echo reply.
4. The intermediate device adds the IP address of its outbound interface (1.1.1.2) to the RR option in
the ICMP echo reply, and then forwards the reply.
5. Upon receiving the reply, the source device adds the IP address of its inbound interface (1.1.1.1)
to the RR option. Finally, you can get detailed information about routes from Device A to Device C:
1.1.1.1 <-> {1.1.1.2; 1.1.2.1} <-> 1.1.2.2.
Tracert
Tracert (also called "Traceroute") enables you to get the IP addresses of Layer 3 devices in the path to a
specific destination. You can use tracert to test network connectivity and identify failed nodes.
4
Figure 2 Network diagram
Tracert uses received ICMP error messages to get the IP addresses of devices. As shown in Figure 2,
tracert works as follows:
1. The source device (Device A) sends a UDP packet with a TTL value of 1 to the destination device
(Device D). The destination UDP port is not used by any application on the destination device.
2. The first hop (Device B, the first Layer 3 device that receives the packet) responds by sending a
TTL-expired ICMP error message to the source, with its IP address encapsulated. In this way, the
source device can get the address of the first Layer 3 device (1.1.1.2).
3. The source device sends a packet with a TTL value of 2 to the destination device.
4. The second hop (Device C) responds with a TTL-expired ICMP error message, which gives the
source device the address of the second Layer 3 device (1.1.2.2).
5. The process continues until the packet sent by the source device reaches the ultimate destination
device. Because no application uses the destination port specified in the packet, so the destination
device responds with a port-unreachable ICMP message to the source device, with its IP address
1.1.3.2 encapsulated. This way, the source device gets the IP address of the destination device
(1.1.3.2).
6. The source device thinks that the packet has reached the destination device after receiving the
port-unreachable ICMP message, and the path to the destination device is 1.1.1.2 to 1.1.2.2 to
1.1.3.2.
Prerequisites
Before you use a tracert command, perform the tasks in this section.
For an IPv4 network:
•Enable sending of ICMP timeout packets on the intermediate devices (the devices between the
source and destination devices). If the intermediate devices are HP devices, execute the ip
ttl-expires enable command on the devices. For more information about this command, see Layer
3—IP Services Command Reference.
5
•Enable sending of ICMP destination unreachable packets on the destination device. If the
destination device is an HP device, execute the ip unreachables enable command. For more
information about this command, see Layer 3—IP Services Command Reference.
•If there is an MPLS network between the source and destination devices and you need to display the
MPLS information during the tracert process, enable support for ICMP extensions on the source and
intermediate devices. If the source and intermediate devices are HP devices, execute the ip
icmp-extensions compliant command on the devices. For more information about this command,
see Layer 3—IP Services Command Reference.
For an IPv6 network:
•Enable sending of ICMPv6 timeout packets on the intermediate devices (the devices between the
source and destination devices). If the intermediate devices are HP devices, execute the ipv6
hoplimit-expires enable command on the devices. For more information about this command, see
Layer 3—IP Services Command Reference.
•Enable sending of ICMPv6 destination unreachable packets on the destination device. If the
destination device is an HP device, execute the ipv6 unreachables enable command. For more
information about this command, see Layer 3—IP Services Command Reference.
Using a tracert command to identify failed or all nodes in a
path
Task Command
Remarks
Display the routes from
source to destination.
•For an IPv4 network:
tracert [ -a source-ip | -f first-ttl |-m max-ttl |
-p port | -q packet-number | -tos tos |
-vpn-instance vpn-instance-name |-w
timeout ] * host
•For an IPv6 network:
tracert ipv6 [ -f first-ttl | -m max-ttl | -p port |
-q packet-number | -tos tos | -vpn-instance
vpn-instance-name | -w timeout ] * host
Use one of the commands.
Available in any view.
Only the HP 5500 EI Switch
Series supports the
vpn-instance keyword.
System debugging
The device supports various debugging for the majority of protocols and features and provides
debugging information to help users diagnose errors.
Debugging information control switches
The following two switches control the display of debugging information:
•Protocol debugging switch—Controls protocol-specific debugging information.
6
•Screen output switch—Controls whether to display the debugging information on a certain screen.
As shown in Figure 3, assume that the device can provide debugging for the three modules 1, 2, and 3.
The debugging information can be output on a terminal only when both the protocol debugging switch
and the screen output switch are turned on.
Output of debugging information depends on the configurations of the information center and the
debugging commands of each protocol and functional module. Debugging information is typically
displayed on a terminal (including console or VTY) for display. You can also send debugging
information to other destinations. For more information, see "Configuring the information center."
Figure 3 Relationship between the protocol and screen output switch
Debugging a feature module
Output of debugging commands is memory intensive. To guarantee system performance, enable
debugging only for modules that are in an exceptional condition. When debugging is complete, use the
undo debugging all command to disable all the debugging functions.
Configure the debugging,terminal debugging, and terminal monitor commands before you can display
detailed debugging information on the terminal. For more information about the terminal debugging
and terminal monitor commands, see Network Management and Monitoring Command Reference.
To debug a feature module and display the debugging information on a terminal:
7
Ste
p
Command
Remarks
1. Enable the terminal
monitoring of system
information.
terminal monitor
Optional.
The terminal monitoring on the
console is enabled by default and
the terminal monitoring on the
monitoring terminal is disabled by
default.
Available in user view.
2. Enable the terminal display of
debugging information. terminal debugging Disabled by default.
Available in user view.
3. Enable debugging for a
specified module. debugging module-name [ option ]
Disabled by default.
Available in user view.
4. Display the enabled
debugging functions.
display debugging [ interface
interface-type interface-number ]
[module-name ] [ | { begin |
exclude | include }
regular-expression ]
Optional.
Available in any view.
Ping and tracert example
Network requirements
As shown in Figure 4, Device A failed to Telnet Device C. Determine whether Device A and Device C can
reach each other. If they cannot reach each other, locate the failed nodes in the network.
Figure 4 Network diagram
Test procedure
1. Use the ping command to test connectivity between Device A and Device C.
<DeviceA> ping 1.1.2.2
PING 1.1.2.2: 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out
--- 1.1.2.2 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss
The output shows that Device A and Device C cannot reach each other.
8
2. Use the tracert command to identify failed nodes:
# Enable sending of ICMP timeout packets on Device B.
<DeviceB> system-view
[DeviceB] ip ttl-expires enable
# Enable sending of ICMP destination unreachable packets on Device C.
<DeviceC> system-view
[DeviceC] ip unreachables enable
# Execute the tracert command on Device A.
<DeviceA> tracert 1.1.2.2
traceroute to 1.1.2.2(1.1.2.2) 30 hops max,40 bytes packet, press CTRL_C to break
1 1.1.1.2 14 ms 10 ms 20 ms
2 * * *
3 * * *
4 * * *
5
<DeviceA>
The output shows that Device A and Device C cannot reach other, Device A and Device B can
reach each other, and an error has occurred on the connection between Device B and Device C.
3. Use the debugging ip icmp command on Device A and Device C to verify that they can send and
receive the specific ICMP packets, or use the display ip routing-table command to verify the
availability of active routes between Device A and Device C.
9
Configuring NTP
The term Layer 3 Ethernet port refers to route-mode (or Layer 3) Ethernet ports. You can set an Ethernet
port to operate in route mode by using the port link-mode route command (see Layer 2—LAN Switching
Configuration Guide).
Overview
NTP is typically used in large networks to dynamically synchronize time among network devices. It
guarantees higher clock accuracy than manual system clock setting. In a small network that does not
require high clock accuracy, you can keep time synchronized among devices by changing their system
clocks one by one.
NTP runs over UDP and uses UDP port 123.
NTP application
An administrator is unable to keep time synchronized among all devices within a network by changing
the system clock on each station, because this is a huge work and does not guarantee clock precision.
NTP, however, allows quick clock synchronization within the entire network and ensures high clock
precision.
NTP is used when all devices within the network must keep consistent time. For example:
•In analyzing log and debugging information collected from different devices in network
management, time must be used as a reference basis.
•All devices must use the same reference clock in a charging system.
•To implement certain functions, such as a scheduled restart of all devices within the network, all
devices must keep consistent time.
•If multiple systems process a complex event in cooperation, these systems must use the same
reference clock to ensure the correct execution sequence.
•For incremental backup between a backup server and clients, timekeeping must be synchronized
between the backup server and all clients.
NTP advantages
•NTP uses a stratum to describe clock accuracy. The stratum ranges from 1 to 16. Clock accuracy
decreases as the stratum number increases. The stratum of a reference clock ranges from 1 to 15. A
stratum 16 clock is in unsynchronized state.
10
•The local clock of this Switch Series cannot operate as a reference clock. It can serve as an NTP
server only after it is synchronized.
•NTP supports access control and MD5 authentication.
•NTP can unicast, multicast, or broadcast protocol messages.
How NTP works
Figure 5 shows the basic workflow of NTP. Device A and Device B are connected over a network. They
have their own independent system clocks, which need to be automatically synchronized through NTP.
Assume that:
•Prior to system clock synchronization between Device A and Device B, the clock of Device A is set
to 10:00:00 am while that of Device B is set to 11:00:00 am.
•Device B is used as the NTP time server, so Device A synchronizes to Device B.
•It takes 1 second for an NTP message to travel from one device to the other.
Figure 5 Basic workflow of NTP
The synchronization process is as follows:
•Device A sends Device B an NTP message, which is timestamped when it leaves Device A. The
timestamp is 10:00:00 am (T1).
•When this NTP message arrives at Device B, it is timestamped by Device B. The timestamp is
11:00:01 am (T2).
Other manuals for 5500 EI series
3
This manual suits for next models
1
Table of contents
Other HP Switch manuals
HP
HP StorageWorks T5518A User manual
HP
HP 6125XLG User manual
HP
HP 5920 User manual
HP
HP A7533A - Brocade 4Gb SAN Switch Base Operating and maintenance manual
HP
HP Compaq Presario,Presario 1910 User manual
HP
HP Compaq Presario,Presario 1905 User manual
HP
HP ProCurve 8100fl User manual
HP
HP Brocade 8Gb User manual
HP
HP FlexFabric 12900 series User manual
HP
HP Procurve Series 4100GL User manual
HP
HP A7533A - Brocade 4Gb SAN Switch Base Service manual
HP
HP ProLiant BL p-Class GbE2 User manual
HP
HP Officejet Pro 7500 Series User manual
HP
HP 5920 User manual
HP
HP S7500E Instruction Manual
HP
HP 6125XLG User manual
HP
HP 339674-001 User manual
HP
HP AK241A - StorageWorks 8Gb Simple SAN... User manual
HP
HP AdvanceStack Switch 2000 User manual
HP
HP 279720-B21 - ProLiant BL p-Class F-GbE... Installation guide
