HP 5920 User manual
HP 5920 & 5900 Switch Series
Network Management and Monitoring
Configuration Guide
Part number: 5998-5309a
Software version: Release 23xx
Document version: 6W101-20150320
Legal and notice information
© Copyright 2015 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·····································································4
Tracert example························································································································································4
System debugging ····························································································································································6
Debugging information control switches················································································································6
Debugging a feature module ··································································································································7
Configuring NTP ·························································································································································· 8
Overview············································································································································································8
How NTP works························································································································································8
NTP architecture ·······················································································································································9
Association modes ················································································································································ 10
NTP security ··························································································································································· 12
NTP for MPLS VPNs ·············································································································································· 13
Protocols and standards ······································································································································· 13
Configuration restrictions and guidelines···················································································································· 13
Configuration task list ···················································································································································· 14
Enabling the NTP service ·············································································································································· 14
Configuring NTP association modes···························································································································· 14
Configuring NTP in client/server mode·············································································································· 14
Configuring NTP in symmetric active/passive mode ························································································ 15
Configuring NTP in broadcast mode ·················································································································· 16
Configuring NTP in multicast mode····················································································································· 17
Configuring access control rights································································································································· 18
Configuring NTP authentication ··································································································································· 18
Configuring NTP authentication in client/server mode····················································································· 18
Configuring NTP authentication in symmetric active/passive mode ······························································· 20
Configuring NTP authentication in broadcast mode ························································································· 23
Configuring NTP authentication in multicast mode ··························································································· 24
Configuring NTP optional parameters························································································································· 27
Specifying the source interface for NTP messages···························································································· 27
Disabling an interface from processing NTP messages ···················································································· 27
Configuring the maximum number of dynamic associations············································································ 28
Configuring a DSCP value for NTP packets······································································································· 28
Configuring the local clock as a reference source ····································································································· 29
Displaying and maintaining NTP ································································································································· 29
NTP client/server mode configuration example ········································································································· 29
IPv6 NTP client/server mode configuration example································································································· 31
NTP symmetric active/passive mode configuration example ··················································································· 32
IPv6 NTP symmetric active/passive mode configuration example··········································································· 34
NTP broadcast mode configuration example ············································································································· 36
NTP multicast mode configuration example················································································································ 37
IPv6 NTP multicast mode configuration example ······································································································· 40
Configuration example for NTP client/server mode with authentication································································· 43
ii
Configuration example for NTP broadcast mode with authentication····································································· 45
Configuration example for MPLS VPN time synchronization in client/server mode ·············································· 48
Configuration example for MPLS VPN time synchronization in symmetric active/passive mode························· 49
Configuring SNTP ······················································································································································52
Configuration restrictions and guidelines···················································································································· 52
Configuration task list ···················································································································································· 52
Enabling the SNTP service ············································································································································ 52
Specifying an NTP server for the device ····················································································································· 52
Configuring SNTP authentication ································································································································· 53
Displaying and maintaining SNTP ······························································································································· 54
SNTP configuration example ········································································································································ 54
Configuring PTP··························································································································································56
Overview········································································································································································· 56
Basic concepts ······················································································································································· 56
Synchronization mechanism································································································································· 58
Protocols and standards ······································································································································· 61
Configuring clock nodes ··············································································································································· 61
Configuration task list ··········································································································································· 61
Specifying a PTP standard···································································································································· 62
Specifying the clock node type···························································································································· 62
Specifying a PTP domain······································································································································ 63
Configuring an OC to operate as only a member clock ·················································································· 63
Configuring the role of a PTP port······················································································································· 63
Configuring the mode for carrying timestamps·································································································· 64
Specifying a delay measurement mechanism for a BC or OC ········································································ 64
Configuring the port type for a TC+OC ············································································································· 65
Configuring the interval for sending announce messages················································································ 65
Specifying the number of announcement intervals before the receiving node stops receiving announce
messages································································································································································ 66
Configuring the interval for sending Pdelay_Req messages············································································· 66
Configuring the interval for sending Sync messages ························································································ 66
Configuring the minimum interval for sending Delay_Req messages······························································ 67
Configuring the MAC address for non-pdelay messages ················································································· 67
Specifying the protocol for encapsulating PTP messages as UDP (IPv4) ························································· 68
Specifying the source IP address for UDP packets····························································································· 68
Configuring the delay correction value··············································································································· 68
Configuring the cumulative offset between the UTC and TAI··········································································· 69
Configuring the correction date of the UTC ······································································································· 69
Configuring the parameters of the Bits clock······································································································ 69
Configuring a priority of the clock ······················································································································ 70
Specifying the system time source as PTP··········································································································· 70
Enabling PTP on a port ········································································································································· 70
Displaying and maintaining PTP··································································································································· 71
PTP configuration example (IEEE 1588 Version 2) ···································································································· 71
PTP configuration example (IEEE 802.1AS)················································································································ 73
Configuring the information center···························································································································77
Overview········································································································································································· 77
Log types ································································································································································ 77
Log levels································································································································································ 77
Log destinations ····················································································································································· 78
Default output rules for logs·································································································································· 78
Default output rules for diagnostic logs··············································································································· 78
Default output rules for security logs ··················································································································· 79
iii
Default output rules for hidden logs····················································································································· 79
Default output rules for trace logs························································································································ 79
Log formats····························································································································································· 79
FIPS compliance ····························································································································································· 82
Information center configuration task list····················································································································· 82
Outputting logs to the console ······································································································································ 83
Outputting logs to the monitor terminal ······················································································································· 83
Outputting logs to a log host ········································································································································ 84
Outputting logs to the log buffer ·································································································································· 84
Saving logs to the log file·············································································································································· 85
Managing security logs················································································································································· 86
Saving security logs into the security log file······································································································ 86
Managing the security log file ····························································································································· 87
Saving diagnostic logs to the diagnostic log file········································································································ 87
Configuring the maximum size of the trace log file ··································································································· 88
Enabling synchronous information output ··················································································································· 88
Enabling duplicate log suppression ····························································································································· 89
Disabling an interface from generating link up or link down logs ··········································································· 89
Displaying and maintaining information center ········································································································· 90
Configuration example for outputting logs to the console························································································· 90
Configuration example for outputting logs to a UNIX log host················································································· 91
Configuration example for outputting logs to a Linux log host ················································································· 92
Configuring SNMP·····················································································································································94
Overview········································································································································································· 94
FIPS compliance ····························································································································································· 94
SNMP framework·················································································································································· 94
MIB and view-based MIB access control ············································································································ 94
SNMP operations ·················································································································································· 95
Protocol versions···················································································································································· 95
Configuring SNMP basic parameters·························································································································· 95
Configuring SNMPv1 or SNMPv2c basic parameters······················································································ 96
Configuring SNMPv3 basic parameters············································································································· 97
Configuring SNMP logging ········································································································································100
Configuring SNMP notifications·································································································································101
Enabling SNMP notifications ·····························································································································101
Configuring the SNMP agent to send notifications to a host ·········································································101
Displaying the SNMP settings·····································································································································104
SNMPv1/SNMPv2c configuration example·············································································································104
SNMPv3 configuration example ································································································································106
Configuring RMON ················································································································································ 109
Overview·······································································································································································109
RMON groups ·····················································································································································109
Sample types for the alarm group and the private alarm group ···································································111
Protocols and standards ·····································································································································111
Configuring the RMON statistics function ·················································································································111
Creating an RMON Ethernet statistics entry·····································································································111
Creating an RMON history control entry··········································································································112
Configuring the RMON alarm function ·····················································································································112
Displaying and maintaining RMON settings ············································································································113
Ethernet statistics group configuration example ·······································································································114
Network requirements·········································································································································114
Configuration procedure ····································································································································114
History group configuration example ························································································································115
iv
Network requirements·········································································································································115
Configuration procedure ····································································································································115
Alarm function configuration example·······················································································································116
Network requirements·········································································································································116
Configuration procedure ····································································································································117
Configuring NQA ··················································································································································· 119
Overview·······································································································································································119
NQA operation ···················································································································································119
Collaboration·······················································································································································120
Threshold monitoring ··········································································································································120
NQA configuration task list ········································································································································121
Configuring the NQA server ······································································································································121
Enabling the NQA client·············································································································································122
Configuring NQA operations on the NQA client ····································································································122
NQA operation configuration task list··············································································································122
Configuring the ICMP echo operation ··············································································································123
Configuring the DHCP operation·······················································································································124
Configuring the DNS operation·························································································································124
Configuring the FTP operation ···························································································································125
Configuring the HTTP operation ························································································································126
Configuring the UDP jitter operation·················································································································127
Configuring the SNMP operation······················································································································128
Configuring the TCP operation ··························································································································129
Configuring the UDP echo operation················································································································130
Configuring the voice operation························································································································131
Configuring the DLSw operation ·······················································································································132
Configuring the path jitter operation·················································································································133
Configuring optional parameters for the NQA operation··············································································134
Configuring the collaboration function ·············································································································135
Configuring threshold monitoring······················································································································136
Configuring the NQA statistics collection function ··························································································139
Configuring the saving of NQA history records······························································································139
Scheduling the NQA operation on the NQA client·································································································140
Configuring NQA templates on the NQA client ······································································································140
Configuring the ICMP template ·························································································································141
Configuring the DNS template···························································································································141
Configuring the TCP template ····························································································································142
Configuring the HTTP template ··························································································································143
Configuring the FTP template ·····························································································································145
Configuring optional parameters for the NQA template················································································145
Displaying and maintaining NQA·····························································································································146
NQA configuration examples ····································································································································147
ICMP echo operation configuration example ··································································································147
DHCP operation configuration example···········································································································148
DNS operation configuration example·············································································································149
FTP operation configuration example ···············································································································151
HTTP operation configuration example·············································································································152
UDP jitter operation configuration example ·····································································································153
SNMP operation configuration example ··········································································································156
TCP operation configuration example ··············································································································157
UDP echo operation configuration example ····································································································158
Voice operation configuration example ···········································································································159
DLSw operation configuration example············································································································162
Path jitter operation configuration example ·····································································································163
v
NQA collaboration configuration example······································································································165
ICMP template configuration example··············································································································167
DNS template configuration example···············································································································168
TCP template configuration example ················································································································169
HTTP template configuration example···············································································································170
FTP template configuration example ·················································································································170
Configuring port mirroring ····································································································································· 172
Overview·······································································································································································172
Terminology ·························································································································································172
Port mirroring classification and implementation·····························································································173
Configuring local port mirroring ································································································································175
Local port mirroring configuration task list ·······································································································175
Creating a local mirroring group ······················································································································175
Configuring source ports for the local mirroring group ··················································································175
Configuring the monitor port for the local mirroring group············································································176
Configure local port mirroring with multiple monitor ports·············································································177
Configuring Layer 2 remote port mirroring ···············································································································178
Configuring a remote destination group on the destination device ······························································179
Configuring a remote source group on the source device ·············································································181
Configuring Layer 3 remote port mirroring ···············································································································183
Layer 3 remote port mirroring configuration task list ······················································································183
Configuration prerequisites ································································································································184
Configuring local mirroring groups···················································································································184
Configuring source ports for a local mirroring group ·····················································································184
Configuring the monitor port for a local mirroring group···············································································185
Displaying and maintaining port mirroring···············································································································186
Local port mirroring configuration example··············································································································186
Network requirements·········································································································································186
Configuration procedure ····································································································································186
Verifying the configuration·································································································································187
Layer 2 remote port mirroring configuration example ·····························································································187
Network requirements·········································································································································187
Configuration procedure ····································································································································187
Verifying the configuration·································································································································189
Local port mirroring with multiple monitor ports configuration example ·······························································189
Network requirements·········································································································································189
Configuration procedure ····································································································································190
Layer 3 remote port mirroring configuration example ·····························································································191
Network requirements·········································································································································191
Configuration procedure ····································································································································191
Verifying the configuration·································································································································193
Configuring flow mirroring····································································································································· 194
Flow mirroring configuration task list·························································································································194
Configuring match criteria ··········································································································································194
Configuring a traffic behavior ····································································································································195
Configuring a QoS policy···········································································································································195
Applying a QoS policy ···············································································································································196
Applying a QoS policy to an interface·············································································································196
Applying a QoS policy to a VLAN····················································································································196
Applying a QoS policy globally························································································································196
Applying a QoS policy to the control plane ····································································································196
Flow mirroring configuration example·······················································································································197
Network requirements·········································································································································197
vi
Configuration procedure ····································································································································197
Verifying the configuration·································································································································198
Configuring sFlow··················································································································································· 199
Protocols and standards ··············································································································································199
sFlow configuration task list ········································································································································199
Configuring the sFlow agent and sFlow collector information················································································200
Configuring flow sampling··········································································································································200
Configuring counter sampling ····································································································································201
Displaying and maintaining sFlow·····························································································································201
sFlow configuration example······································································································································202
Network requirements·········································································································································202
Configuration procedure ····································································································································202
Verifying the configuration·································································································································203
Troubleshooting sFlow configuration ·························································································································203
The remote sFlow collector cannot receive sFlow packets ··············································································203
Monitoring and maintaining processes················································································································· 205
Displaying and maintaining processes······················································································································205
Displaying and maintaining user processes··············································································································205
Monitoring kernel threads ···········································································································································206
Configuring kernel thread deadloop detection································································································206
Configuring kernel thread starvation detection································································································207
Displaying and maintaining kernel threads······································································································207
Configuring EAA····················································································································································· 209
Overview·······································································································································································209
EAA framework ···················································································································································209
Elements in a monitor policy ······························································································································210
EAA environment variables································································································································211
Configuring a user-defined EAA environment variable ···························································································212
Configuring a monitor policy······································································································································213
Configuration restrictions and guidelines ·········································································································213
Configuring a monitor policy from the CLI ·······································································································213
Configuring a monitor policy by using Tcl ·······································································································215
Suspending monitor policies·······································································································································216
Displaying and maintaining EAA settings ·················································································································216
Configuration examples ··············································································································································216
CLI-defined policy configuration example ········································································································216
Tcl-defined policy configuration example ·········································································································218
Configuring CWMP················································································································································ 219
Overview·······································································································································································219
CWMP network framework································································································································219
Basic CWMP functions ·······································································································································220
How CWMP works ·············································································································································221
Configuration task list ··················································································································································222
Enabling CWMP from the CLI ····································································································································223
Configuring ACS attributes ·········································································································································224
Configuring the preferred ACS attributes ·········································································································224
Configuring the default ACS attributes from the CLI························································································225
Configuring CPE attributes··········································································································································225
Configuring ACS authentication parameters ···································································································226
Configuring the provision code ·························································································································226
Configuring the CWMP connection interface ··································································································226
Configuring autoconnect parameters················································································································227
vii
Enabling NAT traversal for the CPE ··················································································································228
Specifying an SSL client policy for HTTPS connection to ACS ·······································································228
Displaying and maintaining CWMP··························································································································229
CWMP configuration example···································································································································229
Network requirements·········································································································································229
Configuration procedure ····································································································································231
Verifying the configuration·································································································································239
Configuring NETCONF ·········································································································································· 240
Overview·······································································································································································240
NETCONF structure ············································································································································240
NETCONF message format ·······························································································································241
How to use NETCONF ·······································································································································242
Protocols and standards ·····································································································································242
FIPS compliance ···························································································································································243
NETCONF configuration task list ·······························································································································243
Enabling NETCONF over SOAP································································································································243
Enabling NETCONF over SSH ···································································································································244
Establishing a NETCONF session ······························································································································244
Entering XML view···············································································································································244
Exchanging capabilities ·····································································································································244
Subscribing to event notifications·······························································································································245
Subscription procedure·······································································································································245
Example for subscribing to event notifications ·································································································246
Locking/unlocking the configuration··························································································································247
Locking the configuration ···································································································································248
Unlocking the configuration ·······························································································································248
Example for locking the configuration ··············································································································248
Performing service operations ····································································································································249
Performing the get/get-bulk operation··············································································································250
Performing the get-config/get-bulk-config operation ·······················································································251
Performing the edit-config operation·················································································································252
All-module configuration data retrieval example·····························································································252
Syslog configuration data retrieval example····································································································254
Example for retrieving a data entry for the interface table·············································································255
Example for changing the value of a parameter ·····························································································256
Saving, rolling back, and loading the configuration ·······························································································257
Saving the configuration·····································································································································257
Rolling back the configuration ···························································································································258
Loading the configuration···································································································································258
Example for saving the configuration ···············································································································259
Filtering data·································································································································································259
Example for filtering data with regular expression match ··············································································261
Example for filtering data by conditional match······························································································263
Performing CLI operations through NETCONF·········································································································264
Configuration procedure ····································································································································264
CLI operation example········································································································································265
Retrieving NETCONF session information ················································································································266
Terminating another NETCONF session····················································································································267
Configuration example ·······································································································································268
Returning to the CLI······················································································································································268
Appendix ································································································································································· 269
Appendix A Supported NETCONF operations ········································································································269
viii
Support and other resources ·································································································································· 279
Contacting HP ······························································································································································279
Subscription service ············································································································································279
Related information······················································································································································279
Documents····························································································································································279
Websites·······························································································································································279
Conventions ··································································································································································280
Index ········································································································································································ 282
1
Using ping, tracert, and system debugging
This chapter covers ping, tracert, and information about debugging the system.
Ping
Use the ping utility to determine if a specific address is reachable.
Ping 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
Execute ping commands in any view.
Task Command
Determine if a specified address in an IP
network is reachable.
When you configure the ping command for a low-speed
network, set a larger value for the timeout timer (indicated by the
-t keyword in the command).
•For IPv4 networks:
ping [ ip ] [ -a source-ip | -c count | -f | -httl | -i
interface-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 IPv6 networks:
ping ipv6 [ -a source-ipv6 | -c count | -m interval |-q|-s
packet-size | -t timeout | -v |-tc traffic-class | -vpn-instance
vpn-instance-name ] * host [ -i interface-type
interface-number ]
For more information about the ping mpls command, see MPLS Command Reference.
Ping example
Network requirements
As shown in Figure 1, determine if Device A and Device C can reach each other. If they can reach each
other, get detailed information about routes from Device A to Device C.
2
Figure 1 Network diagram
Configuration procedure
# Use the ping command on Device A to test connectivity to Device C.
Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break
56 bytes from 1.1.2.2: icmp_seq=0 ttl=254 time=2.137 ms
56 bytes from 1.1.2.2: icmp_seq=1 ttl=254 time=2.051 ms
56 bytes from 1.1.2.2: icmp_seq=2 ttl=254 time=1.996 ms
56 bytes from 1.1.2.2: icmp_seq=3 ttl=254 time=1.963 ms
56 bytes from 1.1.2.2: icmp_seq=4 ttl=254 time=1.991 ms
--- Ping statistics for 1.1.2.2 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.963/2.028/2.137/0.062 ms
The output shows that Device A sends five ICMP packets to Device C and Device A receives five ICMP
packets, no ICMP packet is lost, and the route is reachable.
# Get detailed information about routes from Device A to Device C.
<DeviceA> ping -r 1.1.2.2
Ping 1.1.2.2 (1.1.2.2): 56 data bytes, press CTRL_C to break
56 bytes from 1.1.2.2: icmp_seq=0 ttl=254 time=4.685 ms
RR: 1.1.2.1
1.1.2.2
1.1.1.2
1.1.1.1
56 bytes from 1.1.2.2: icmp_seq=1 ttl=254 time=4.834 ms (same route)
56 bytes from 1.1.2.2: icmp_seq=2 ttl=254 time=4.770 ms (same route)
56 bytes from 1.1.2.2: icmp_seq=3 ttl=254 time=4.812 ms (same route)
56 bytes from 1.1.2.2: icmp_seq=4 ttl=254 time=4.704 ms (same route)
--- Ping statistics for 1.1.2.2 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 4.685/4.761/4.834/0.058 ms
The test procedure of ping –r is as shown in Figure 1:
1. The source device (Device A) sends an ICMP echo request to the destination device (Device C) with
the RR option blank.
3
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. The detailed information of routes from Device A to Device C is formatted as:
1.1.1.1 <-> {1.1.1.2; 1.1.2.1} <-> 1.1.2.2.
Tracert
Tracert (also called "Traceroute") enables retrieval of the IP addresses of Layer 3 devices in the path to a
specific destination. In the event of network failure, use tracert to test network connectivity and identify
failed nodes.
Figure 2 Tracert operation
Tracert uses received ICMP error messages to get the IP addresses of devices. Tracert works as shown
in Figure 2:
1. The source device sends a UDP packet with a TTL value of 1 to the destination device. 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 (1.1.1.2) encapsulated. 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. This process continues until a packet sent by the source device reaches the ultimate destination
device. Because no application uses the destination port specified in the packet, the destination
device responds with a port-unreachable ICMP message to the source device, with its IP address
encapsulated. This way, the source device gets the IP address of the destination device (1.1.3.2).
Device A Device B Device DDevice C
1.1.1.1/24
1.1.1.2/24
Hop Lmit=1
TTL exceeded
1.1.2.1/24 1.1.3.1/24
1.1.2.2/24 1.1.3.2/24
Hop Lmit=2
TTL exceeded
UDP port unreachable
Hop Lmit=n
4
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 (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.
•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.
For an IPv6 network:
•Enable sending of ICMPv6 timeout packets on the intermediate devices (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
Execute tracert commands in any view.
Task Command
Display the routes from source to
destination.
•For IPv4 networks:
tracert [ -a source-ip | -f first-ttl |-m max-ttl | -p port | -q packet-number
| -t tos | -vpn-instance vpn-instance-name |-w timeout ] * host
•For IPv6 networks:
tracert ipv6 [ -f first-hop | -m max-hops | -p port | -q packet-number | -t
traffic-class | -vpn-instance vpn-instance-name | -w timeout ] * host
For more information about the tracert mpls ipv4 command, see MPLS Command Reference.
Tracert example
Network requirements
As shown in Figure 3, Device A failed to Telnet Device C.
5
Test the network connectivity between Device A and Device C. If they cannot reach each other, locate the
failed nodes in the network.
Figure 3 Network diagram
Configuration procedure
1. Configure the IP addresses for devices as shown in Figure 3.
2. Configure a static route on Device A.
<DeviceA> system-view
[DeviceA] ip route-static 0.0.0.0 0.0.0.0 1.1.1.2
[DeviceA] quit
3. Use the ping command to test connectivity between Device A and Device C.
<DeviceA> ping 1.1.2.2
Ping 1.1.2.2(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
--- Ping statistics for 1.1.2.2 ---
5 packet(s) transmitted,0 packet(s) received,100.0% packet loss
The output shows that Device A and Device C cannot reach each other.
4. 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 at most,40 bytes each packet, press CTRL_C to
break
1 1.1.1.2 (1.1.1.2) 1 ms 2 ms 1 ms
2 * * *
3 * * *
4 * * *
5
<DeviceA>
The output shows that Device A can reach Device B but cannot reach Device C, which indicates
that an error has occurred on the connection between Device B and Device C.
Device A Device B Device C
1.1.1.1/24 1.1.1.2/24 1.1.2.1/24 1.1.2.2/24
6
5. 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 that there
is a route from Device A to Device C.
System debugging
The device supports debugging for the majority of protocols and features and provides debugging
information to help users diagnose errors.
Debugging information control switches
The following switches control the display of debugging information:
•Module debugging switch—Controls whether to generate the module-specific debugging
information.
•Screen output switch—Controls whether to display the debugging information on a certain screen.
Use terminal monitor and terminal logging level commands to turn on the screen output switch. For
more information about these two commands, see Network Management and Monitoring
Command Reference.
As shown in Figure 4, 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 module debugging switch
and the screen output switch are turned on.
Debugging information is typically displayed on a console. You can also send debugging information to
other destinations. For more information, see "Configuring the information center."
Figure 4 Relationship between the module and screen output switch
7
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.
To debug a feature module:
Ste
p
Command
Remarks
1. Enable debugging for a
specified module in user view.
debugging { all [ timeout time ] |
module-name [ option ] }
By default, all debugging functions
are disabled.
2. (Optional.) Display the
enabled debugging in any
view.
display debugging
[module-name ] N/A
8
Configuring NTP
Synchronize your device with a trusted time source by using the Network Time Protocol (NTP) or
changing the system time before you run it on a live network. Various tasks, including network
management, charging, auditing, and distributed computing depend on an accurate system time setting,
because the timestamps of system messages and logs use the system time.
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.
How NTP works
Figure 5 shows how NTP synchronizes the system time between two devices, in this example, Device A
and Device B. Assume that:
•Prior to the time synchronization, the time of Device A is set to 10:00:00 am and that of Device B
is set to 11:00:00 am.
•Device B is used as the NTP server. Device A is to be synchronized to Device B.
•It takes 1 second for an NTP message to travel from Device A to Device B, and from Device B to
Device A.
•It takes 1 second for Device B to process the NTP message.
Figure 5 Basic work flow
9
The synchronization process is as follows:
1. Device A sends Device B an NTP message, which is timestamped when it leaves Device A. The
time stamp is 10:00:00 am (T1).
2. When this NTP message arrives at Device B, Device B adds a timestamp showing the time when
the message arrived at Device B. The timestamp is 11:00:01 am (T2).
3. When the NTP message leaves Device B, Device B adds a timestamp showing the time when the
message left Device B. The timestamp is 11:00:02 am (T3).
4. When Device A receives the NTP message, the local time of Device A is 10:00:03 am (T4).
Up to now, Device A can calculate the following parameters based on the timestamps:
•The roundtrip delay of the NTP message: Delay = (T4 – T1) – (T3 – T2) = 2 seconds.
•Time difference between Device A and Device B: Offset = ((T2 – T1) + (T3 – T4)) /2 = 1 hour.
Based on these parameters, Device A can be synchronized to Device B.
This is only a rough description of the work mechanism of NTP. For more information, see the related
protocols and standards.
NTP architecture
NTP uses stratums 1 to 16 to define clock accuracy, as shown in Figure 6. A lower stratum value
represents higher accuracy. Clocks at stratums 1 through 15 are in synchronized state, and clocks at
stratum 16 are not synchronized.
Figure 6 NTP architecture
Typically, a stratum 1 NTP server gets its time from an authoritative time source, such as an atomic clock,
and provides time for other devices as the primary NTP server. The accuracy of each server is the stratum,
with the topmost level (primary servers) assigned as one and each level downwards in the hierarchy
assigned as one greater than the preceding level. NTP uses a stratum to describe how many NTP hops
away a device is from the primary time server. A stratum 2 time server receives its time from a stratum 1
time server, and so on.
Primary servers
(Stratum 1)
Authoritative
clock
Server
Secondary servers
(Stratum 2)
Tertiary servers
(Stratum 3)
Quaternary servers
(Stratum 4)
Client Symmetric
peer
Symmetric
peer
Broadcast/multicast
server
Broadcast/multicast
client
10
To ensure time accuracy and availability, you can specify multiple NTP servers for a device. The device
selects an optimal NTP server as the clock source based on parameters such as stratum. The clock that
the device selects is called the reference source. For more information about clock selection, see the
related protocols and standards.
If the devices in a network cannot synchronize to an authoritative time source, you can select a device that
has a relatively accurate clock from the network, and use the local clock of the device as the reference
clock to synchronize other devices in the network.
Association modes
NTP supports the following association modes:
•Client/server mode
•Symmetric active/passive mode
•Broadcast mode
•Multicast mode
Table 1 NTP association modes
Mode Workin
g
p
rocess
Princi
p
le
A
pp
lication scenario
Client/server
On the client, specify the IP
address of the NTP server.
A client sends a clock
synchronization message to the
NTP servers. Upon receiving the
message, the servers
automatically operate in server
mode and send a reply.
If the client can be synchronized
to multiple time servers, it selects
an optimal clock and
synchronizes its local clock to the
optimal reference source after
receiving the replies from the
servers.
A client can be
synchronized to a server,
but a server cannot be
synchronized to a client.
As Figure 6 shows, this
mode is intended for
configurations where
devices of a higher stratum
are synchronized to
devices with a lower
stratum.
Other manuals for 5920
18
This manual suits for next models
1
Table of contents
Other HP Switch manuals
HP
HP ProCurve 2824 User manual
HP
HP 6200YL User manual
HP
HP FlexFabric 5700-48G-4XG-2QSFP+ TAA User manual
HP
HP 5120-48G-PoE+ EI User instructions
HP
HP flexnetwork 5510 hi series User manual
HP
HP Officejet Pro 7500 Series User manual
HP
HP 3600 v2 Series User manual
HP
HP JC106A User manual
HP
HP StorageWorks 2/16-EL User instructions
HP
HP 3500 Series User manual
HP
HP FlexFabric 7900 Series User manual
HP
HP 6125XLG User manual
HP
HP ProLiant BL p-Class GbE2 Operating manual
HP
HP StorageWorks 8/24 - SAN Switch Quick user guide
HP
HP 316095-B21 - StorageWorks Edge Switch 2/24 Instruction Manual
HP
HP 5920 User manual
HP
HP ProCurve J4863A User manual
HP
HP 1810 series User manual
HP
HP Compaq Presario,Presario 1905 User manual
HP
HP ProCurve 8108fl Assembly instructions
