Hitachi GR2000 Series manual Operation Management Information Related Standards

Operation Management Information

Related Standards

The NTP specifications of GR2000 are based on RFC1305.

Precautions

Depending on the type of the connected NTP server, the usable authentication key length may be shorter than 32 bits. In such a case, adjust the key contents to

￿match the usable key length of the connected NTP server.

If a host name is specified to the <address> parameter where applicable (e.g., peer, server, and broadcast) and such host name is wrong, no error checking will be performed. Once the definition operation is complete, make sure that the host name specified with this object is displayed on the console. Incidentally, if a host name is initially specified with this ntp object and thereafter another host name is added with the hosts object, the change does not promptly take effect. To force the change to take effect, restart the NTP server with the command string GR2000 Operations Commands, Vol. 1, restart ntp command.

If the difference of internal clocks between the referenced server and this GR2000

￿router is 1000 seconds (approx. 16 minutes) or more, the time data synchronization does not take place because the server is regarded as invalid. If the server’s time (i.e., the time of the host containing the time server to which this router references as the time source) turns out to be correct, then adjust the router’s time to the server’s time using GR2000 Operations Commands, Vol. 1, set calendar or rdate command.

In a configuration where this router references multiple time servers and any time difference among the time servers is 16 seconds or more, this router can synchronize with its time servers but devices subordinately connected to this router cannot synchronize with this router acting as their time server. In such a case, make sure that the said configuration is as expected and see if the time settings of the defined time servers are correct.

When this router and multiple time servers employ peer-to-peer connections, there may be cases when a very long time is required before this router completes time synchronization with all these time servers. If this could happen, it is

￿recommended to decrease the number of peers.

When this router refers to multiple time servers and one time server fails to provide time data within the allowable range (less than 1000 seconds), the server for the time synchronization target automatically switches to any other server available. If such occurrence is left without an appropriate action, however, the synchronization target will be eventually disconnected. To avoid this, you must disable the router’s referencing the failing time server. Incidentally, while the said synchronization is off and the failing time server setting is adjusted to fall within the allowable range, the synchronization with the time server is automatically recovered.

This function can be used only with IPv6. Therefore, if the host name with the IPv6 only defined is specified with hosts (host name information) in the peer server, the peer server is nullified.

If this command is inputted in the cases where changes are made on the IP routing protocol information, the IP multicast protocol information, and the MPLS information, and the apply command is not being executed, the apply subcommand is executed before the command is executed, and the changed IP routing protocol information, IP multicast routing protocol information, and

￿MPLS information are reflected to the operation.

If using this device as NTP server, set the number of synchronized clients at a maximum of 10.

GR2K-GA-0014	4-25
Ver. 07-02