Date and Time 2

[PhoneGuyy]

I just want to reconfirm a thought... I got a asked a question about date and time change.

Do you have to have level 2 ability

 

[acewarlock]

It all depends on the access that the level password has been given, but normaly level should be able to access ld 2.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[PhoneGuyy]

ok for some reason I thought I heard that you had to have different level acces to change the date and time now

 

[MagnaRGP]

Rls 5 requires L2 access to change the date and time.

Seems stupid, but given that system time is CRITICAL to a properly functioning Symposium, I'm guessing that this was done on the assumption that only people with a certain level of skill/training will have access to an L2 password.

 

[mlmtmatt]

Level 2 (PWD2) passwords and any "end user passwords" (LAPW) PWnn configured with OPT TADA and access to OVL 2, can do STAD (Set Time And Date).

 

[a12ozbottle]

I had a 4.5 switch require me to have level 2 as well.

 

[seahawk04]

I'm trying to change the time a new Option 81C Rls 5.0. I log in as admin2 go to LD 2 to change the time, but I get the following error "ERR193 Invalid NTP table" Has anyone seen this before?

 

[1Rita1]

Found this on Nortel website:
BULLETIN ID: 022727-01, Rev 1
PUBLISHED: 2007-09-01
STATUS: Active
REGION: APAC
CALA
EMEA
GC
NA
PRIORITY: Major
TYPE: Alert
Background:
ERR193 caused by pNtpTable not being initialized during original installation, COLD_START, WARM_START process
Analysis:
Design in review of isolation: CR# Q01690518
Recommendations:
ERR193 is not service impacting, but is miss-leading. See example below on setting TIME / DATE
>ld 2
TFC000
.ttad THUR 30 08 2007 10 47 28
.
TFC000
.
TFC000
.stad 30 08
ERR193 Invalid NTP table
2007
ERR193 Invalid NTP table
ERR193 Invalid NTP table
10 48 10
ERR193 Invalid NTP table
TFC000
.
TFC000
.ttad
ERR193 Invalid NTP table
THUR 30 08 2007 10 48 12
.A work around patch MPLR24629 for all processors is avaliable. This is a debug patch and has been set to VO. This
takes care of handling ERR0193 during EDD/STAD.
Required Actions:
.
>TECHNICAL SUPPORT
. TECHNICAL BULLETIN
.
.
Comm. Server 1000 (CS1K): ERR 193 during System Data Dump and when trying
to use OVL#2 to STAD causing installation confusion
If the patch is installed GNTS should capture debug infomation and attach to CR Q01690518. Patch is in VO status and
will not go public until completion of design investagation. GNTS should link the case to the CR and hold the case in thier
WIP Bin.

 

[seahawk04]

Thanks for the info Rita

 

[johnpoole]

i saw the nortel email that said with rls 5+ time and date required pwd2.. i guess no one told them the same is true in rls 3.. i set up pwd1's for local techs and they have access to ld 2 allowed, and they can ttad in ld 2, but not stad.. here's a script i post from time to time.. it does a sync from your pc to the switch.. i call it from a login script.. but it can run standalone..

proc main
integer iDay, iMonth, iYear, iMin, iHour, iSec
   string sSend
  
   ltimeints $LTIME iYear iMonth iDay iHour iMin iSec
   
   strfmt sSend "STAD %02d %02d %d %02d %02d %02d" iDay iMonth iYear iHour iMin iSec
   set txpace 20
   transmit "****^M"
   pause 1
 transmit "john^M"    ;logs off current user
 pause 1
   transmit "logi admin1^M"
  
                  ;script waits for password


   waitfor ">" forever
   
   transmit "ld 2^M"
   waitfor "."
   transmit "TTAD^M"
   waitfor "."
   transmit sSend
   transmit "^M"
   waitfor "."
   mspause 20
   transmit "TTAD^M"
   waitfor "."
   mspause 20
   transmit "****^M"
   
   
   
   endproc

this one keeps the 81 in sync with network time..

john poole
bellsouth business
columbia,sc

 

[x11tech]

http://www.datarave.net/zfh/?page_id=108

My set time script is pretty nice also, it does not do the log in portion like John Pooles example above, because I (like him) usually call it from another script. But it does have a constant in it that allows you to offset your time by any difference in time zone.

I maintain multiple systems across the US and find that adjusting the TZ is easier when you code for it.

 

[Aishac]

If you only have to stad one system, then go to

http://tycho.usno.navy.mil/simpletime.html

and type in your line a few seconds ahead and then press enter when the clock catches up to you.

 

[CanGoalie]

I am upgrading a number of switches to Rls 5.0. I had an automated script that polled all my switches to set the time and date. Now, the LAPW I use is not allowed to do its thing. I saw the following on this thread.

mlmtmatt (TechnicalUser) 12 Mar 08 19:02
Level 2 (PWD2) passwords and any "end user passwords" (LAPW) PWnn configured with OPT TADA and access to OVL 2, can do STAD (Set Time And Date).

I tried to set TADA on a LAPW password but it is not allowed. SCH8835 - Invalid LAPW password option selected.

I see the option as available in the Rls 5.0 NTP

(TADD) Deny Set Time and Date (administrator and
installer access)
adminset-21
TADA Allow Set Time and Date (administrator and
installer access)

I cannot configure it though.

Does not seem complicated but I am definitely missing something.
Any ideas?

Thanks