No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - Device Management

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of Device Management, including device status query, hardware management, Information Center Configuration, NTP, Synchronous Ethernet Configuration, Fault Management Configuration, Energy-Saving Management Configuration, Performance Management Configuration, Maintenance Assistant Configuration, and OPS Configuration.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring NTP Operating Modes

Configuring NTP Operating Modes

Context

The following NTP operating modes are supported by a device:

Operating Mode

Usage Scenario

Deployment Location and Synchronization Direction

Unicast client/server mode

The unicast client/server mode is used on a higher stratum on a synchronization subnet. In this mode, the IP address of the server needs to be obtained in advance.

You only need to configure the client. The server only needs to be configured with an NTP primary clock.

Note that the client can be synchronized to the server but the server cannot be synchronized to the client.

Symmetric peer mode

The symmetric peer mode is used on a lower stratum on the synchronization subnet. In this mode, a symmetric active peer and a symmetric passive peer can be synchronized with each other.

You only need to configure the symmetric active peer. The symmetric passive peer does not need to be configured with an NTP command.

In symmetric peer mode, a symmetric peer of a higher stratum is synchronized to a symmetric peer of a lower stratum.

Broadcast mode

When the IP address of a server or a symmetric peer is not determined, or when the clocks of a large number of devices need to be synchronized on a network, clock synchronization can be implemented in the broadcast mode.

Relevant commands need to be run on the server and the client.

Note that the client can be synchronized to the server but the server cannot be synchronized to the client.

Multicast mode

The multicast mode applies to the high-speed network that has multiple clients and does not require high precision. In a typical scenario, one or more clock servers on the network periodically send multicast packets to clients, and the clients synchronize time based on the multicast packets.

Relevant commands need to be run on the server and the client.

Note that the client can be synchronized to the server but the server cannot be synchronized to the client.

Manycast mode

The manycast mode applies to the scenario where servers are scattered on a network. The client can discover and synchronize to the closest manycast server. The manycast mode applies to the scenario where the servers are not stable and clients on the entire network do not need to be configured again due to a change of the server.

Relevant commands need to be run on the server and the client.

Note that the client can be synchronized to the server but the server cannot be synchronized to the client.

NOTE:

If a source address from which NTP packets are sent is specified on the server, the address must be the same as the server IP address configured on the client. Otherwise, the client cannot process the NTP packets sent by the server, resulting in failed clock synchronization.

Procedure

  • Unicast Client/Server Mode

    In the unicast client/server mode, you need to configure only the client. Only an NTP primary clock needs to be configured on the server.

    Only after the clock on the server is synchronized, the server can function as a clock server to which other devices can be synchronized. When the clock stratum of the server is greater than or equal to the clock stratum of the client, the client is not synchronized to the server.

    Configure the unicast client.

    1. Run system-view

      The system view is displayed.

    2. Run any of the following commands:

      • ntp unicast-server ip-address [ version number | authentication-keyid key-id | source-interface interface-type interface-number | vpn-instance vpn-instance-name | preferred | port port-number ] *

        An NTP server with a specified IPv4 address is configured.

      • ntp unicast-server ipv6 ipv6-address [ authentication-keyid key-id | source-interface interface-type interface-number | vpn-instance vpn-instance-name | preferred | port port-number ] *

        An NTP server with a specified IPv6 address is configured.

      • ntp unicast-server { domain domain-name } [ version number | authentication-keyid key-id | source-interface interface-type interface-number | vpn-instance vpn-instance-name | preferred | maxpoll max-number | minpoll min-number | burst | iburst | preempt | port port-number ] *

        An NTP server with a specified domain name is configured.

      The value of ip-address or ipv6-address is the IP address of the NTP server. It can be the address of a host instead of being a broadcast address or a multicast address.

      To specify the parameter authentication-keyid, see Configuring NTP Authentication.

      If the port parameter is specified, you must specify the same port number on the server by using the ntp port port-value command.

      You can run the ntp unicast-server command repeatedly to configure multiple servers. The client selects the optimal clock source by selecting a preferred clock.

    3. (Optional) Run ntp unsync max-poll-interval poll-interval-value dec-step step-value

      The maximum polling interval in unsynchronized state and the step length to be decreased in the actual polling interval are configured.

      By default, the maximum polling interval in unsynchronized state and the step length to be decreased in the actual polling interval are 10 (1024s) and 6 (64s), respectively.

      In unsynchronized mode, when the maximum polling interval (poll-interval-value) is set to 10, the step length to be decreased in the actual polling interval (step-value) must be set to 6.

    4. Run commit

      The configuration is committed.

  • Symmetric Peer Mode

    You only need to specify the IP address of the symmetric passive peer on the symmetric active peer, and both symmetric peers use this IP address to exchange NTP packets.

    Either of the symmetric active peer or the symmetric passive peer must be in the synchronized state. Otherwise, they cannot be synchronized.

    Configure the symmetric active peer.

    1. Run system-view

      The system view is displayed.

    2. Run any of the following commands:

      • ntp unicast-peer ip-address [ version number | authentication-keyid key-id | source-interface interface-type interface-number | vpn-instance vpn-instance-name | preferred | port port-number ] *

        The NTP peer with a specified IPv4 address is configured.

      • ntp unicast-peer ipv6 ipv6-address [ authentication-keyid key-id | source-interface interface-type interface-number | vpn-instance vpn-instance-name | preferred | port port-number ] *

        The NTP peer with a specified IPv6 address is configured.

      • ntp unicast-peer { domain domain-name } [ version number | authentication-keyid key-id | source-interface interface-type interface-number | vpn-instance vpn-instance-name | preferred | maxpoll max-number | minpoll min-number | preempt | port port-number ] *

        The NTP peer with a specified domain name is configured.

      The values of ip-address or ipv6-address must be a unicast address, and cannot be a broadcast address or a multicast address.

      To specify the parameter authentication-keyid, see Configuring NTP Authentication.

      If the port parameter is specified, you must specify the same port number on the server by using the ntp port port-value command.

      You can run the ntp unicast-peer command repeatedly to configure multiple symmetric passive peers. When a symmetric active peer has multiple symmetric passive peers configured, the synchronization direction follows the principle that a symmetric peer of a larger stratum is synchronized with a symmetric peer of a smaller stratum.

    3. (Optional) Run ntp unsync max-poll-interval poll-interval-value dec-step step-value

      The maximum polling interval in unsynchronized state and the step length to be decreased in the actual polling interval are configured.

      By default, the maximum polling interval in unsynchronized state and the step length to be decreased in the actual polling interval are 10 (1024s) and 6 (64s), respectively.

      In unsynchronized mode, when the maximum polling interval (poll-interval-value) is set to 10, the step length to be decreased in the actual polling interval (step-value) must be set to 6.

    4. Run commit

      The configuration is committed.

  • Broadcast Mode

    The broadcast mode can be used only on a local area network (LAN).

    Only after the clock of the broadcast server is synchronized, the broadcast client can be synchronized with the broadcast server.

    Configure the NTP broadcast server.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface for sending NTP broadcast packets is specified, and the interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run ntp broadcast-server [ version number | authentication-keyid key-id | port port-number ] *

      The local switch is configured as the NTP broadcast server.

      To specify the parameter authentication-keyid, see Configuring NTP Authentication.

      If the port parameter is specified, you must specify the same port number on the server by using the ntp port port-value command.

    5. Run commit

      The configuration is committed.

    Configure the NTP broadcast client.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface for receiving NTP broadcast packets is specified, and the interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run ntp broadcast-client

      The local switch is configured as the NTP broadcast client.

    5. Run commit

      The configuration is committed.

  • Multicast Mode

    Only after the clock of the multicast server is synchronized, the multicast client can be synchronized with the multicast server.

    Currently a maximum of 1024 multicast clients can be configured. However, only 128 of these multicast clients can work simultaneously.

    Configure the NTP multicast server.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface for sending NTP multicast packets is specified, and the interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run any of the following commands:

      • ntp multicast-server [ ip-address ] [ version number | authentication-keyid key-id | ttl ttl-number | port port-number ] *

        The local switch is configured as the NTP multicast server on an IPv4 network.

      • ntp multicast-server [ ipv6 [ ipv6-address ] ] [ authentication-keyid key-id | ttl ttl-number | port port-number ] *

        The local switch is configured as the NTP multicast server on an IPv6 network.

      To specify the parameter authentication-keyid, see Configuring NTP Authentication.

      If the port parameter is specified, you must specify the same port number on the server by using the ntp port port-value command.

    5. Run commit

      The configuration is committed.

    Configure the NTP multicast client.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface for receiving NTP multicast packets is specified, and the interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run ntp multicast-client [ ip-address | ipv6 [ ipv6-address ] ]

      The local switch is configured as the NTP multicast client.

    5. Run commit

      The configuration is committed.

  • Manycast Mode

    Configure the NTP manycast server.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface for receiving NTP manycast packets is specified, and the interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run ntp manycast-server [ ip-address | ipv6 [ ipv6-address ] ]

      The local switch is configured as the NTP manycast server.

    5. Run commit

      The configuration is committed.

    Configure the NTP manycast client.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface for sending NTP manycast packets is specified, and the interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run ntp manycast-client [ ip-address | ipv6 [ ipv6-address ] ] [ authentication-keyid key-id | ttl ttl-number | port port-number ] *

      The local switch is configured as the NTP manycast client.

      To specify the parameter authentication-keyid, see Configuring NTP Authentication.

      If the port parameter is specified, you must specify the same port number on the manycast server by using the ntp port port-value command.

    5. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074722

Views: 10947

Downloads: 10

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next