Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    View all the pages
    Page
    of 2513
    Add page 2321 to Favourites
    image text
    Enable zoom 
    							 20 
•  A client can synchronize to the server only when you configure all the required tasks on both the 
client and server. 
•   On the client, if NTP authentication is not enabled or no key is specified to associate with the NTP 
server, the client is not authenticated. No matter  whether NTP authentication is enabled or not on 
the server, the clock synchronization between the server and client can be performed. 
•   On the client, if NTP authentication is enabled and a key is specified to associate with the NTP 
server, but the key is not a trusted key, the client does not synchronize to the server no matter whether 
NTP authentication is enabled or not on the server. 
Configuring NTP authentication for client 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enable NTP authentication. 
ntp-service authentication enable  By default, NTP authentication is 
disabled. 
3.
  Configure an NTP 
authentication key.  ntp-service authentication-keyid 
keyid
 authentication-mode md5  
[ cipher |  simple ] value  By default, no NTP authentication 
key is configured. 
Configure the same authentication 
key on the client and server. 
4.
  Configure the key as a trusted 
key.  ntp-service reliable 
authentication-keyid 
keyid  By default, the authentication key is 
not configured as a trusted key. 
5.
  Associate the specified key 
with an NTP server. 
• Client/server mode: 
ntp-service  unicast-server  
{  ip-address |  server-name } 
authentication-keyid  keyid  
• Symmetric peers mode: 
ntp-service unicast-peer 
{  ip-address |  peer-name } 
authentication-keyid  keyid   You can associate a non-existing 
key with an NTP server. To make 
NTP authentication effective, you 
must configure the key as an 
authentication key and specify it as 
a trusted key after associating the 
key with the NTP server. 
 
Configuring NTP authentication for a server 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enable NTP authentication. 
ntp-service authentication  enable  By default, NTP authentication is 
disabled. 
3.
  Configure an NTP 
authentication key.  ntp-service authentication-keyid
 
keyid  authentication-mode md5  
[ cipher |  simple ] value   By default, no NTP authentication 
key is configured. 
Configure the same authentication 
key on the client and server. 
4.
  Configure the key as a trusted 
key.  ntp-service reliable 
authentication-keyid 
keyid  By default, the authentication key is 
not configured as a trusted key. 
5.
  Enter Layer 3 Ethernet port 
view or VLAN interface view.  interface
 interface-type 
interface-number   You can configure an Ethernet port 
as a Layer 3 Ethernet port only on 
the HP 5500 EI switch.
    Add page 2322 to Favourites
    image text
    Enable zoom 
    							 21 
Step Command Remarks 
6.  Associate the specified key 
with an NTP server. 
• Broadcast server mode: 
ntp-service  broadcast-server 
authentication-keyid  keyid  
• Multicast server  mode:  
ntp-service  multicast-server 
authentication-keyid  keyid   You can associate a non-existing 
key with an NTP server. To enable 
NTP authentication, you must 
configure the key and specify it as 
a trusted key after associating the 
key with the NTP server. 
 
Displaying and maintaining NTP 
 
Task Command Remarks 
Display information about 
NTP service status. 
display ntp-service status
 [ | { begin | 
exclude  | include  } 
regular-expression  ]  Available in any view 
Display information about 
NTP sessions.  display ntp-service sessions 
[
 verbose  ] [ | { begin |  exclude | 
include  } regular-expression ]  Available in any view
 
Display the brief information 
about the NTP servers from the 
local device back to the 
primary reference source.  display ntp-service trace
 [ | { begin | 
exclude  | include  } 
regular-expression  ]  Available in any view
 
 
NTP configuration examples 
This section provides configuration examples for NTP. 
Configuring the client/server mode 
Network requirements 
As shown in Figure 11, co nfigure Device A as a reference source, with the stratum level 2. Configure 
Device B to operate in client/server mode and use Device A as its NTP server. 
Figure 11  Network diagram 
 
 
Configuration procedure 
1. Set the IP address for each interface as shown in  Figure 11. (Details  not shown.) 
2. Configure Device B:  
# Display the NTP status of Device  B before clock synchronization.  
 display ntp-service status 
 Clock status: unsynchronized 
 Clock stratum: 16 
 Reference clock ID: none
    Add page 2323 to Favourites
    image text
    Enable zoom 
    							 22 
 Nominal frequency: 64.0000 Hz 
 Actual frequency: 64.0000 Hz 
 Clock precision: 2^7 
 Clock offset: 0.0000 ms 
 Root delay: 0.00 ms 
 Root dispersion: 0.00 ms 
 Peer dispersion: 0.00 ms 
 Reference time: 00:00:00.000 UTC Jan 1 1900 (00000000.00000000) 
# Specify Device A as the NTP server of Device B so Device B synchronizes to Device A.  
 system-view 
[DeviceB] ntp-service unicast-server 1.0.1.11 
# Display the NTP status of Device B after clock synchronization.  
[DeviceB] display ntp-service status 
 Clock status: synchronized 
 Clock stratum: 3 
 Reference clock ID: 1.0.1.11 
 Nominal frequency: 64.0000 Hz 
 Actual frequency: 64.0000 Hz 
 Clock precision: 2^7 
 Clock offset: 0.0000 ms 
 Root delay: 31.00 ms 
 Root dispersion: 1.05 ms 
 Peer dispersion: 7.81 ms 
 Reference time: 14:53:27.371 UTC Sep 19 2005 (C6D94F67.5EF9DB22) 
The output shows that Device B has synchronized to  Device A because it has a higher stratum than 
Device A. 
# Display the NTP session information of Device B. 
[DeviceB] display ntp-service sessions 
      source      reference   stra  reach  poll  now  offset  delay  dis\
per 
************************************************************************\
** 
[12345] 1.0.1.11  127.127.1.0    2    63    64    3    -75.5    31.0  16\
.5 
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 confi\
gured 
Total associations :  1 
The output shows that an association has b een set up between Device B and Device A. 
Configuring the NTP symmetric mode  
Network requirements 
•  As shown in  Figure 12, configure Device A as a reference source, with the stratum level 2. 
•   Configure Device B to operate in client mode and use Device A as its NTP server. 
•   Configure Device C to operate in symmetric-active mode and use Device B as its symmetric-passive 
peer.
    Add page 2324 to Favourites
    image text
    Enable zoom 
    							 23 
Figure 12 Network diagram 
 
 
Configuration procedure 
1. Configure IP addresses for inte rfaces. (Details not shown.) 
2. Configure Device B:  
# Specify Device A as the NTP server of Device B.  
 system-view 
[DeviceB] ntp-service unicast-server 3.0.1.31 
3. Display the NTP status of Device B after clock synchronization.  
[DeviceB] display ntp-service status 
 Clock status: synchronized 
 Clock stratum: 3  
 Reference clock ID: 3.0.1.31 
 Nominal frequency: 100.0000 Hz  
 Actual frequency: 100.0000 Hz  
 Clock precision: 2^18 
 Clock offset: -21.1982 ms 
 Root delay: 15.00 ms  
 Root dispersion: 775.15 ms  
 Peer dispersion: 34.29 ms  
 Reference time: 15:22:47.083 UTC Sep 19 2005 (C6D95647.153F7CED) 
The output shows that Device B has synchronized to  Device A because it has a higher stratum than 
Device A. 
4.  Configure Device C (after Device  B is synchronized to Device A): 
# Configure Device C as a symmetric  peer after local synchronization.  
[DeviceC] ntp-service unicast-peer 3.0.1.32 
The output shows that Device B and Device C are co nfigured as symmetric peers, with Device C in 
symmetric-active mode and Device  B in symmetric-passive mode. Because the stratus level of 
Device C is 16 while that of  Device B is 3, Device B synchronizes to Device C.  
# Display the NTP status of Device  C after clock synchronization.  
[DeviceC] display ntp-service status 
 Clock status: synchronized 
 Clock stratum: 4  
 Reference clock ID: 3.0.1.32
    Add page 2325 to Favourites
    image text
    Enable zoom 
    							 24 
 Nominal frequency: 100.0000 Hz  
 Actual frequency: 100.0000 Hz  
 Clock precision: 2^18 
 Clock offset: -21.1982 ms 
 Root delay: 15.00 ms  
 Root dispersion: 775.15 ms  
 Peer dispersion: 34.29 ms  
 Reference time: 15:22:47.083 UTC Sep 19 2005 (C6D95647.153F7CED) 
The output shows that Device C has synchronized to Device B because it has a higher stratum than 
Device B. 
# Display the NTP session information of Device C. 
[DeviceC] display ntp-service sessions 
       source          reference       stra reach poll  now offset  dela\
y disper 
************************************************************************\
******** 
[12345] 3.0.1.32       3.0.1.31        3     3    64    16   -6.4    4.8\
    1.0 
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 confi\
gured 
Total associations :  1 
The output shows that an association has b een set up between Device B and Device C. 
Configuring NTP broadcast mode 
Network requirements 
•  As shown in  Figure 13, c onfigure Switch C as a reference source, with the stratum level 2. 
•   Configure Switch C to operate in broadcast se rver mode and send broadcast messages from 
VLAN-interface 2. 
•   Configure Switch A and Switch B to operate in  broadcast client mode, and listen to broadcast 
messages through their VLAN-interface 2 respectively. 
Figure 13  Network diagram 
 
 
Configuration procedure 
1. Set the IP address for each interface as shown in  Figure 13. (Details  not shown.) 
2. Configure Switch C:
    Add page 2326 to Favourites
    image text
    Enable zoom 
    							 25 
# Configure Switch C to operate in broadcast server mode and send broadcast messages through 
VLAN-interface 2.  
[SwitchC] interface vlan-interface 2 
[SwitchC-Vlan-interface2] ntp-service broadcast-server 
3.  Configure Switch A: 
# Configure Switch A to operate in broadcast client mode and receive  broadcast messages on 
VLAN-interface 2.  
 system-view 
[SwitchA] interface vlan-interface 2 
[SwitchA-Vlan-interface2] ntp-service broadcast-client 
4.  Configure Switch B: 
# Configure Switch B to operate in broadcast client mode and receive  broadcast messages on 
VLAN-interface 2. 
 system-view 
[SwitchB] interface vlan-interface 2 
[SwitchB-Vlan-interface2] ntp-service broadcast-client 
Switch A and Switch B get synchronized upon re ceiving a broadcast message from Switch C.  
# Take Switch A as an example. Display the NTP st atus of Switch A after clock synchronization.  
[SwitchA-Vlan-interface2] display ntp-service status 
 Clock status: synchronized 
 Clock stratum: 3  
 Reference clock ID: 3.0.1.31 
 Nominal frequency: 64.0000 Hz  
 Actual frequency: 64.0000 Hz  
 Clock precision: 2^7 
 Clock offset: 0.0000 ms  
 Root delay: 31.00 ms  
 Root dispersion: 8.31 ms  
 Peer dispersion: 34.30 ms  
 Reference time: 16:01:51.713 UTC Sep 19 2005 (C6D95F6F.B6872B02) 
The output shows that Switch A has synchronized to Switch C because it has a higher stratum than 
Switch C. 
# Display the NTP session information of Switch A.  
[SwitchA-Vlan-interface2] display ntp-service sessions 
      source    reference    stra  reach  poll  now  offset   delay  disper 
************************************************************************\
** 
[1234] 3.0.1.31  127.127.1.0   2   254     64    62   -16.0    32.0   16\
.6 
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 confi\
gured 
Total associations :  1 
The output shows that an association has b een set up between Switch A and Switch C. 
Configuring NTP multicast mode 
Network requirements 
As shown in Figure 14, configure Device C as a reference source, with the stratum level 2.
    Add page 2327 to Favourites
    image text
    Enable zoom 
    							 26 
•  Configure Device C to operate in multicast server mode and send multicast messages from 
VLAN-interface 2. 
•   Configure Device A and Device D to operate in multicast client mode and receive multicast 
messages through VLAN-interface 3 and VLAN-interface 2 respectively. 
 
  NOTE: 
In this example, Switch B must be a Layer 3 switch that supports multicast routing. 
 
Figure 14  Network diagram 
 
 
Configuration procedure 
1. Set the IP address for each interface as shown in  Figure 14. (Details  not shown.) 
2. Configure Device C: 
# Configure Device C to operate in multicast se rver mode and send multicast messages through 
VLAN-interface 2.  
[DeviceC] interface vlan-interface 2 
[DeviceC-Vlan-interface2] ntp-service multicast-server 
3.  Configure Device D: 
# Configure Device D to operate in multicast cl ient mode and receive multicast messages on 
VLAN-interface 2.  
 system-view 
[DeviceD] interface vlan-interface 2  
[DeviceD-Vlan-interface2] ntp-service multicast-client 
Because Device D and Device C are on the same  subnet, Device D can receive the multicast 
messages from Device C without being enabled with the mult icast functions and can synchronize 
to Device C.  
# Display the NTP status of Device  D after clock synchronization.  
[DeviceD-Vlan-interface2] display ntp-service status 
 Clock status: synchronized 
 Clock stratum: 3  
 Reference clock ID: 3.0.1.31 
 Nominal frequency: 64.0000 Hz  
 Actual frequency: 64.0000 Hz  
 Clock precision: 2^7
    Add page 2328 to Favourites
    image text
    Enable zoom 
    							 27 
 Clock offset: 0.0000 ms  
 Root delay: 31.00 ms  
 Root dispersion: 8.31 ms  
 Peer dispersion: 34.30 ms  
 Reference time: 16:01:51.713 UTC Sep 19 2005 (C6D95F6F.B6872B02) 
The output shows that Device D has synchronized to Device C because it has a higher stratum than 
Device C.  
# Display the NTP session in formation of Device D.  
[DeviceD-Vlan-interface2] display ntp-service sessions 
      source    reference    stra  reach  poll  now  offset   delay  disper 
************************************************************************\
** 
[1234] 3.0.1.31  127.127.1.0   2   254     64    62   -16.0    31.0   16\
.6 
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 confi\
gured 
Total associations :  1 
The output shows that an association has b een set up between Device D and Device C. 
4. Configure Device B: 
Because Device A and Device C are on different  subnets, you must enable the multicast functions 
on Device B before Device A can receiv e multicast messages from Device C.  
# Enable IP multicast routing and IGMP. For more  information about how to configure IGMP and 
PIM, see IP Multicast  Configuration Guide . 
 system-view 
[DeviceB] multicast routing-enable 
[DeviceB] interface vlan-interface 2 
[DeviceB-Vlan-interface2] pim dm 
[DeviceB-Vlan-interface2] quit 
[DeviceB] vlan 3 
[DeviceB-vlan3] port gigabitethernet 1/0/1 
[DeviceB-vlan3] quit 
[DeviceB] interface vlan-interface 3 
[DeviceB-Vlan-interface3] igmp enable 
[DeviceB-Vlan-interface3] igmp static-group 224.0.1.1 
[DeviceB-Vlan-interface3] quit 
[DeviceB] interface gigabitethernet 1/0/1 
[DeviceB-GigabitEthernet1/0/1] igmp-snooping static-group 224.0.1.1 vlan\
 3 
5. Configure Device A: 
 system-view 
[DeviceA] interface vlan-interface 3 
# Configure Device A to operate in multicast cl ient mode and receive multicast messages on 
VLAN-interface 3.  
[DeviceA-Vlan-interface3] ntp-service multicast-client 
# Display the NTP status of Device  A after clock synchronization.  
[DeviceA-Vlan-interface3] display ntp-service status 
 Clock status: synchronized 
 Clock stratum: 3  
 Reference clock ID: 3.0.1.31 
 Nominal frequency: 64.0000 Hz  
 Actual frequency: 64.0000 Hz
    Add page 2329 to Favourites
    image text
    Enable zoom 
    							 28 
 Clock precision: 2^7 
 Clock offset: 0.0000 ms  
 Root delay: 40.00 ms  
 Root dispersion: 10.83 ms  
 Peer dispersion: 34.30 ms  
 Reference time: 16:02:49.713 UTC Sep 19 2005 (C6D95F6F.B6872B02) 
The output shows that Device A has synchronized to Device C because it has a higher stratum than 
Device C.  
# Display the NTP session in formation of Device A.  
[DeviceA-Vlan-interface3] display ntp-service sessions 
      source    reference    stra  reach  poll  now  offset   delay  disper 
************************************************************************\
** 
[1234] 3.0.1.31  127.127.1.0    2   255     64    26   -16.0    40.0   1\
6.6 
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 confi\
gured 
Total associations :  1 
The output shows that an association has b een set up between Device A and Device C. 
Configuring NTP client/server mode with authentication 
Network requirements 
•  As shown in  Figure 15, configure Device A as a reference source, with the stratum level 2. 
•   Configure Device B to operate in client mode and use Device A as its NTP server. 
•   Enable NTP authentication on both Device A and Device B. 
Figure 15  Network diagram 
 
 
Configuration procedure 
1. Set the IP address for each interface as shown in  Figure 15. (Details  not shown.) 
2. Configure Device B:  
 system-view 
# Enable NTP authentication on Device B.  
[DeviceB] ntp-service authentication enable 
# Set an authentication key.  
[DeviceB] ntp-service authentication-keyid 42 authentication-mode md5 aN\
iceKey 
# Specify the key as a trusted key.  
[DeviceB] ntp-service reliable authentication-keyid 42 
# Specify Device A as the NTP server of Device B.  
[DeviceB] ntp-service unicast-server 1.0.1.11 authentication-keyid 42 
Before Device B can synchroniz e to Device A, enable NTP authentication for Device A.  
3. Configure Device A: 
# Enable NTP authentication.  
[DeviceA] ntp-service authentication enable
    Add page 2330 to Favourites
    image text
    Enable zoom 
    							 29 
# Set an authentication key.  
[DeviceA] ntp-service authentication-keyid 42 authentication-mode md5 aN\
iceKey 
# Specify the key as a trusted key.  
[DeviceA] ntp-service reliable authentication-keyid 42 
# Display the NTP status of Device B after clock synchronization.  
[DeviceB] display ntp-service status 
 Clock status: synchronized 
 Clock stratum: 3 
 Reference clock ID: 1.0.1.11 
 Nominal frequency: 64.0000 Hz 
 Actual frequency: 64.0000 Hz 
 Clock precision: 2^7 
 Clock offset: 0.0000 ms 
 Root delay: 31.00 ms 
 Root dispersion: 1.05 ms 
 Peer dispersion: 7.81 ms 
 Reference time: 14:53:27.371 UTC Sep 19 2005 (C6D94F67.5EF9DB22) 
The output shows that Device B has synchronized to  Device A because it has a higher stratum than 
Device A.  
# Display the NTP session in formation of Device B.  
[DeviceB] display ntp-service sessions 
      source      reference   stra  reach  poll  now  offset  delay  dis\
per 
************************************************************************\
** 
[12345] 1.0.1.11  127.127.1.0    2    63    64    3    -75.5    31.0  16\
.5 
note: 1 source(master),2 source(peer),3 selected,4 candidate,5 confi\
gured 
Total associations :  1 
The output shows that an association has been set up Device B and Device A. 
Configuring NTP broadcast mode with authentication  
Network requirements 
•  As shown in  Figure 16, configure Device C as a reference source, with the stratum level 3. 
•   Configure Device C to operate in broadcast server mode and send broadcast messages from 
VLAN-interface 2. 
•   Configure Device A and Device B to operate in broadcast client mode and receive broadcast 
messages through VLAN-interface 2. 
•   Enable NTP authentication on both Device B and Device C.
    All HP manuals Comments (0)

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