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!

Mitel SX2000 Logsys - Who has logname list?

Status
Not open for further replies.

ClarkTelTom

Technical User
Oct 30, 2008
9
US
I'm trying to look at the maintenance logs on an SX2000 using the logsys read (LOGS REA) command.

The documentation shows how to use the qualifier <logname> but no where does it seem to give a list what they all are. I've been able to guess at MAINT and SMDR but does anyone have a full list?
 
The logname may be abbreviated to the first two characters. Valid lognames are MAintenance, SEcurity, or SMdr.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Thanks. SEcurity was one I didn't have but groping around I also found SOftware as another valid logname. So that makes four...I'm looking for a comprehensive list.

I need to see if/when the last time the system re-booted itself. PROG R DISP shows PROGRAMMED REBOOT IS ON and PROGRAMMED REBOOT MEMORY: DAILY 02:15:00 but according to the command manual this doesn't necessarily mean it's going to re-boot everyday.

Maybe there's another command that shows when it last re-booted?
 
The list I provided was a direct quote from the manual.

What your looking for would be in the Maintenance Logs.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
reboot from memory only reboots when the memory gets so corrupted that the system proabaly isn't running anyway. run schedule reboot weekly at 2 am

NO GOOD DEED GOES UNPUNISHED!
 
NYTalkin, this is a 2K

I wouldn't recommend a Sched Reboot on a 2K

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
I.ve been doing it for years.....particularly on high traffic MLs. Usually scheduled for Sunday nights at 215am. On newer releases running IIIe contollers I backed off the practice. The older controllers really needed the refresh.

NO GOOD DEED GOES UNPUNISHED!
 
NyTalkin,

My experience with the 2K is quite limited and in almost all cases I worked with redundant systems running R-Stream or better. These systems typically only got reset on upgrades. Solid as rocks.

I'll nod to your experience in this matter.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
The reduns switch planes everyday and the newly inactive plane reloads (refreshes). The reboot on memory option came out in LW29 (I think). I found that if you programmed that option that by the time the memory got corrupted enough to actually start the reboot routine that there were many other problems going on.

Sometimes I get confused with the discussions here because I remember struggling with SG's and the like. Those were some very labor intensive machines.......they did however put all of my children through college and bought a few new cars as well.

NO GOOD DEED GOES UNPUNISHED!
 
I've seen ML's running anything from T-stream to LW34 with *daily* scheduled reboots, never caused a problem. But yeah, weekly should be more than adequate.
 
Referring to your original goal, the command you would most likely want to use is 'logs re maint all mat "reboot"' I beleive. The match string may be "restart", I just can't remeber off the top of my head.


Dale
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top