Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clocks

Status
Not open for further replies.

btrain8

IS-IT--Management
Feb 24, 2005
405
US
I have a few older switches that uses CM2.0 that do not have the patch so we have to remove our NTS IP addresses for a few weeks and go to local clock until this weekend. When I put back the IP addresses the clocks went back an hour. How does this happen.. all my other switches that use this are fine. In addition, I tried to revert back to local clock and the change keeps failing
 
hardware platform and software version?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
S8300 -- cm 2.0 and S8300 cm 3.0

both are not DST patched, hence why we need to manually do this during this time period.
 
if you post the sofware version I might be able to help you with the DST patch.

2.0 and 3.0 are not complete

R012x.01.0.411.7 CM 2.1.0 QPPCN 1434B s8x00 Sup 1
R012x.01.1.414.1 CM 2.1.1 QPPCN 1434B s8x00
R012x.02.0.111.4 CM 2.2.0 QPPCN 1434B s8x00
R012x.02.1.118.1 CM 2.2.1 QPPCN 1434B s8x00 Sup 8
R012x.02.2.122.0 CM 2.2.2 QPPCN 1434B s8x00 Sup 9

R013x.00.0.340.3 CM 3.0.0 QPPCN 1523B s8x00
R013x.00.1.346.0 CM 3.0.1 QPPCN 1523B s8x00
R013x.01.0.628.6 CM 3.1.0 QPPCN 1523B s8x00
R013x.01.1.628.7 CM 3.1.1 QPPCN 1523B s8x00
R013x.01.2.632.1 CM 3.1.2 QPPCN 1523B s8x00
R013x.01.3.640.2 CM 3.1.3 QPPCN 1523B s8x00
R013x.01.4.642.1 CM 3.1.4 QPPCN 1523B s8x00
R013x.01.5.642.3 CM 3.1.5 QPPCN 1523B s8x00


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
1 site is: R013x.00.1.346.0
the other is: R12x.00.1.221.1
 
Communication Software DST Patch Latest tzdata
Manager Release Load version*
2.0.1 221.1 00.1.221.1-12514.tar.gz 2006g
3.0.1 346.0 00.1.346.0-12514.tar.gz 2006g




To download the correct version of the Daylight Saving Time patch from
support.avaya.com:
1. From click on Downloads
2. Click on Latest TN Circuit Pack, Media Server, and Media Gateway Firmware and
Software Updates
3. In the Daylight Saving Time Patches for Media Servers running Communication
Manager table click on the appropriate load of Communication Manager
4. Download the appropriate patch for the specific release of Communication
Manager
NOTE: With some web browsers the characters [1] are erroneously added to the
file name of the download (e.g., 00[1].1.346.0-12514.tar.gz). If this
occurs the file name must be renamed to remove the erroneous [1]
characters. The rest of the file name must be retained. For example,
rename the file in the example used above to 00.1.346.0-12514.tar.gz prior
to unpacking and activating it on the Media Server.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
Looking though the FAQ section, i was able to find this FAQ on how to install the DST patches for you.

faq690-6507

"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953

For the best response to a question, read faq690-6594


 

Avaya said on the 2.0 switch that an upgrade would be required to 2.2 and then the patch can be applied. We will be upgrading all our switches and LSP'ng them in the 2nd quarter so we aren't going to do this. It's been this way for quite some time. Avaya indicated that we should wait until this coming Sunday to try adding back the IP addresses of the NTS as the system will look to follow the old dst rules which is first sunday on or after 4/1. Does that make any sense?
 
rpm -qa tzdata
/usr/sbin/zdump -v /etc/localtime | grep 2009

That does make sense and will when you run the above commands from linux command line.
The patches change the dates you will see on the zdump from April and October to March and November.

If you put the patch on and run the commands again. You will see the difference and your issue will be resolved.

I don't agree with the person you are talking to at Avaya
The links to the patches I gave you will work and will fix your problem.
read below - You are on 2.0.1 and this patch will work for you
R012x.00.1.221.1 CM 2.0.1
It takes two minutes to put it on and does not affect service.

DST patches are available for Communication Manager 2.0.1, 2.1, 2.1.1, 2.2 and 2.2.2 releases.
All other 2.x releases (2.0 and 2.2.1) must upgrade to Communication Manager 2.2.2 and apply the patch,
or use a manual workaround. Please read PCN 1585P for additional information.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top