Issue Description
This case applies to situation when, when deploying
U2000 server on SUN Solaris platform, in both single-server and High
Availability configuration.
This solution was deployed with U2000 V100R002C01SPC100, but it will most certainly work with other versions.
Standard NTP configuration, with MSuite, allows us to configure just one time server. However client can request to have his server (servers) have more than one NTP sources configured, for redundancy purpose.
In this case we have to manually edit Solaris NTP configuration file.
This solution was deployed with U2000 V100R002C01SPC100, but it will most certainly work with other versions.
Standard NTP configuration, with MSuite, allows us to configure just one time server. However client can request to have his server (servers) have more than one NTP sources configured, for redundancy purpose.
In this case we have to manually edit Solaris NTP configuration file.
Alarm Information
Null
Handling Process
In SUN Solaris OS NTP configuration file is in
directory /etc/inet/ntp.conf. If it's not there, an example file exist in
/etc/inet/ntp.server, which can be used as a template.
In the file we can put our lists of time servers in a format:
server X.X.X.X
server Y.Y.Y.Y
...
If we have more than one server with same STRATUM level, we can configure it as a proffered one, using keyword "prefer".
server X.X.X.X prefer
In case when we have U2000 in HA configuration, we can set master and stand-by servers as peers. This is helpful when all configured time servers will become unavailable. Both U2000 server can then configure right time between themselves. Example configuration:
peer Z.Z.Z.Z
In the file we can put our lists of time servers in a format:
server X.X.X.X
server Y.Y.Y.Y
...
If we have more than one server with same STRATUM level, we can configure it as a proffered one, using keyword "prefer".
server X.X.X.X prefer
In case when we have U2000 in HA configuration, we can set master and stand-by servers as peers. This is helpful when all configured time servers will become unavailable. Both U2000 server can then configure right time between themselves. Example configuration:
peer Z.Z.Z.Z
Root Cause
Null
Suggestions
Important thing to remember is that from all time
servers on the list system will choose the one with lowers (more reliable)
STRATUM level. If we have few server on the same level, and no server with
better value then we can use keyword "prefer" to force one servers to
be used.
In configuration file we can also find server with ip address 127.127.1.0. This is LOCAL time, server's time. To make sure this time source is used as a last one, we should set its STRATUM value to less preferable. This can be done by using keyword "fudge".
server 127.127.1.0
fudge 127.127.1.0 stratum 10
Same method can by used to change STRATUM value of any real server but only to less preferable value. For instance, when server is broadcasting its time with STRATUM value of 3, we can change it locally to 4,5,6 etc, but never 0,1 or 2.
Summing up, an example file in situation when we have U2000 in HA configuration and two time servers with same STRATUM level in out network should look like this.
server 172.16.1.15 prefer
server 172.16.2.15
server 127.127.1.0
fudge 127.127.1.0 stratum 10
peer 172.16.10.10
In HA configuration each U2000 server needs to have his NTP configured separately, which means it has to have its own ntp.conf file with proper settings.
MA5600T Series Networking Protection FeatureIn configuration file we can also find server with ip address 127.127.1.0. This is LOCAL time, server's time. To make sure this time source is used as a last one, we should set its STRATUM value to less preferable. This can be done by using keyword "fudge".
server 127.127.1.0
fudge 127.127.1.0 stratum 10
Same method can by used to change STRATUM value of any real server but only to less preferable value. For instance, when server is broadcasting its time with STRATUM value of 3, we can change it locally to 4,5,6 etc, but never 0,1 or 2.
Summing up, an example file in situation when we have U2000 in HA configuration and two time servers with same STRATUM level in out network should look like this.
server 172.16.1.15 prefer
server 172.16.2.15
server 127.127.1.0
fudge 127.127.1.0 stratum 10
peer 172.16.10.10
In HA configuration each U2000 server needs to have his NTP configured separately, which means it has to have its own ntp.conf file with proper settings.
MA5600T Series Maintenance Feature Glance
MA5600T&MA5603T&MA5608T 10G GPON Feature Glance
How to Configure the H.248-based Voice Service?
How to Login Huawei Equipment Through the Local Serial Port
No comments:
Post a Comment