G3V11 Uptime

[1a22ip]

Is there a screen or command other than list measurements ds1 log xxxxx to get when the system was last reset.


Thanks in advance
ED

1a2 to ip I seen it all

 

[irisngen]

i think it's "display init":
display initcauses

INITIALIZATION CAUSES
Cause Action Escalated Mode Time
Interchange 2 no Active 04/03 08:46
Interchange 1 no Active 07/08 04:08
Software Request 1 no Active 07/12 16:55
Interchange 2 no Active 07/16 22:32
Interchange 1 no Active 09/17 23:48
Interchange 2 no Active 09/18 00:43
Initialized 4 no Active 09/18 00:49
Interchange 1 no Active 09/18 00:50
Interchange 1 no Active 09/18 00:56
Interchange 1 no Active 09/18 00:58
Software Request 1 no Active 12/13 13:12
Interchange 2 no Active 03/25 18:21
Initialized 4 no BUSY OUT 03/25 18:41
Internal Request 1 no BUSY OUT 03/25 18:42
Internal Request 1 no Standby 03/25 19:07
Interchange-Craft 1 no Active 09/07 08:54

i'm sure someone here can tell you which is for a reset

 

[irisngen]

as an example, this pbx below i did a reset system 4 this morning & this is what the "display init" shows:
display initcauses

INITIALIZATION CAUSES
Cause Action Escalated Carrier Time
Initialized 4 no 1A 11/20 22:34
Craft Request 4 no 1A 01/17 07:33
Craft Request 4 no 1A 02/22 06:52

 

[irisngen]

display initcauses [print | schedule]
Use display initcauses to see a history of recovery steps taken by the system. Display
initcauses shows information for restarts of the active processor only. When the processor
resets and the system is restarted, either by a technician command or by system software,
information about the recovery is stored. If the reset is escalated, only the reset that
successfully completes is recorded. The error log contains information about the reset. When a
reset 4 (reload) occurs, the error log is saved on the disk.
Records of the last 16 restarts are retained in the initcauses log in chronological order. A power
failure results in loss of every record in the initcauses log.

display initcauses field descriptions 1 of 2
Field Description
Cause This gives the reason for the system reset, as follows:
Craft Request: The reset was manually initiated using reset system.
Initialized: This represents a power-up, and is always the first entry in the log
unless more than 15 restarts have occurred since the last power up.
Internal Request: A fault has triggered the system to automatically reset.
Software Request: Software requested the system restart.
Unknown: The reason for the system reset is unknown. The Software Error Log
may contain more information about the restart.
Bad Memory: A defective memory circuit pack generating too many errors
caused a restart.
System Technician Request: The restart was performed because of system
technician demand. A system technician-requested reset system 4 command
entry should always precede an upgrade software command entry.
Maintenance Reset: This refers to resets of the SPE by maintenance in SPE
Down mode in which maintenance periodically tries to awaken the SPE.
Action The level of recovery performed by the system.
Reset system 1 (Warm)
Reset system 2 (Cold-2)
Reset system 3 (Defaults to Reset system 4)
Reset system 4 (Reload)
Reset system 5 (Extended reboot)
1 of 2
Maintenance SAT Commands
296 Maintenance Commands for Avaya Communication Manager 2.2, Media Gateways and Servers
ip-board
S8700 | 8710 | S8500 | S8300
See:
status ip-board on page 296
status ip-board
S8700 | 8710 | S8500 | S8300
status ip-board UUCss
Status ip-board has the same syntax and output as status clan-ip except the list of
allowed boards is larger.
Note:
Note: status ip-board UUCss is a SAT command that cannot be run on the MAPD
board.
Use status ip-board UUCss to see the data in the first two columns of the following table.
The screen also shows the time of the last port reset, the last hour start time and end time for
the error counter statistics.
Escalated Whether the restart was escalated to a higher level than originally attempted.
The system’s software escalation strategy can perform a higher level restart
than the one initiated if problems prevent or conditions interfere with normal
execution.
Carrier The carrier on which the recovery was performed, if applicable.
Time The month, day and time of the restart.

 

[irisngen]

sorry my copy & paste gave ya a little more info then you needed (i am speaking of the IP board info)

 

[1a22ip]

Thanks for the replies. The init display does not go far enough back. My G3R11 has been up and stable since 2004. I was looking for a display that would be easier that list measurements ds1 log to get this date.

Thanks
ED

1a2 to ip I seen it all