Sun StorEdge T3+ Arrays May Experience Performance Degradation When the NTP Feature is Enabled |
|
| Category : | Availability |
| Release Phase : | Resolved |
| Product : | Sun StorageTek T3 Array Sun StorageTek T3+ Array
|
| Bug Id : | 4798293
|
| Date of Resolved Release : | 22-APR-2005
|
Impact
Sun StorEdge T3+ Arrays with the Network Time Protocol (NTP) feature enabled may experience performance degradation. This could cause applications to run slowly, hang, or encounter a reset.
Contributing Factors
This issue can occur in the following configurations:
Note: This issue only occurs on Sun StorEdge T3+ Arrays with the NTP feature enabled. Use the "ntp" command from the T3+ prompt to determine if NTP is enabled:
t3:/:<4> ntp
server 999.999.99.9 <--- sample IP address of an NTP server
poll unicast <---- this means NTP is enabled
interval 10
Symptoms
Typical StorEdge T3+ syslog messages associated with this issue are shown below:
Jan 12 06:50:11 psc0[1]: N: refresh -s
Jan 12 06:50:11 TZD[1]: N: Daylight saving transition happened.
Jan 12 06:50:24 TZD[1]: N: Daylight saving transition happened.
Jan 12 06:50:38 TZD[1]: N: Daylight saving transition happened.
Jan 12 06:50:51 TZD[1]: N: Daylight saving transition happened.
In addition, error messages in /var/adm/messages or on the host console may indicate I/O timeouts for a particular application.
Workaround
To work around the described issue, disable the NTP function on affected Sun StorEdge T3+ arrays with the following command from a T3+ prompt:
t3:/:<1> ntp poll off
If synchronizing the time clock on the Sun StorEdge T3+ is required, this can be accomplished by manually running the NTP function during intervals of low system activity. NTP should be disabled once the time clock on the Sun StorEdge T3+ has been synchronized. The following command will turn NTP on:
t3:/:<1> ntp poll unicast
The polling time interval may be set with
t3:/:<2> ntp interval time
(where time is a value from 1 to 60 minutes; the default value is 10)
Resolution
-
Sun StorEdge T3+ with patch 112276-08 or later
Modification HistoryDate: 22-APR-2005
-
State: Resolved
-
Resolution: Workaround, Patch
-
Updated Contributing Factors
-
Updated Resolution
AttachmentsThis solution has no attachment