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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Software logs on SX2000

Status
Not open for further replies.

marty6strings

Programmer
Mar 28, 2006
14
US
Anybody have any skinny on where I can get documentation for reading software logs on a 2000? Seems T/S has a death grip on this and I'm curious if there is any documentation out there.
TIA
Marty
 
I've never seen anything. I have found that even a lot of the T/S guys don't even understand all the logs.
 

I've been servicing SX2000's since 1986 and can attest most of what you see in the software logs is pretty cryptic. No level 3 tech (product support) I've ever met has a clue. They have to take the dumps to the product design guys.

The bulk of the S/W logs you see is just meaningless spew.

Tracebacks are usually important, even more important are any trap events, but I still cannot tell you how to read them.

If you want to watch what the machine is doing you can log in with the SYSTEM password and enable kernel process monitoring and kernel queue monitoring, neither of which is advisable since there are commands there which if improperly used can bring the machine to its knees.
 
Thanks guys for the try - I had a sense it was cryptic stuff brought to the design guys - never had a t/s person able to give me anything off the cuff.
MitelInMyBlood, it happens to be a trap issue that I've got going with a specific PLID affecting message lights off an Octel on T1 trunks. I think I've got a workaround using timing on the Octel.
L8R!
Marty

Out of my mind - back in 5 minutes -
 
If the TRAP event always reports the same PLID then quite possibly the fix would be to replace the associated card.

An Octel on T1 trunks? I've never seen that particular type of Octel integration before. I have a big site using SS4/COV integration to an Octel Overture 250 w/48 ports and a smaller site using SS430/DNIC integration to another Overture 250. Believe it or not the old COV integration gives far less headaches. It just works and works and works.

...and the Octel 250 will probably still be running when I'm dead & buried. That thing has to be mil. grade.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top