Does anyone have a favorite "sysmonitorsettings.ini" they apply for a monitor running 24x7

[BWB8771]

(note: we have a PRI)

I'd like to strike a happy balance between logging too much (as a network engineer, "too much" is either never enough, or just right) and missing out on key logging information.

Do any of you seasoned troubleshooters have a favorite group of settings you'd be willing to share with me, either in the form of INI file, or via text here that I could paste into a copy of my own?

Thanks!

IP 500 V2
IPOMgr/VMPro v9.1.0.437
46/5610s, 46/5621+25s
9640Gs

 

[holdmusic34]

Print
Error
Ars
Targeting
Tftp

'The shopping make you not happy place, please forgive me. Thanks for looking, you mix order. Good luck for you'

 

[BWB8771]

Sooo, this (below) is too extreme?

cmcallevt=1
cmextntx=1
cmextnrx=1
cmextnevt=1
cmlinetx=1
cmlinerx=1
cmcalldelta=1
cmextntxp=1
cmextnrxp=1
cmmap=1
cmtargetting=1
cmlogging=1
cmars=1
cmlrq=1
cmsortIEs=1
siptxevents=1
siprxevents=1
frevenm=1
frmgmtm=1
h323ev=1
stuninfo=1
ifacequeue=1
iftcp=1
ifudp=1
ifarpallow=1
ifmcast=1
isdnl1ev=1
isdnl2ev=1
isdnl3ev=1
ppperrmsg=1
MonR2Line=1
MonR2Channel=1
MonR2Dialler=1
MonR2DSP=1
MonR2CAS=1
systemerror=1
systemprint=1
systemresource=1
systemlicencing=1
systemdevtracedefault=1
showtime=1
showms=1
sslvpnSession=1
sslvpnSessionState=1
secRegsCmdError=1
wanev=1


IP 500 V2
IPOMgr/VMPro v9.1.0.437
46/5610s, 46/5621+25s
9640Gs

 

[sizbut]

The question would be "why are you running 24-hour logging"?

Stuck in a never ending cycle of file copying.

 

[BWB8771]

Because I'll get a call or email about a problem, and I like to be able to go back and see what happened at the time. It's a holdover from my network engineering days...

IP 500 V2
IPOMgr/VMPro v9.1.0.437
46/5610s, 46/5621+25s
9640Gs

 

[derfloh]

Then you will need a script that deletes older log files.

I usually start SysMon if the customer calls about a problem and let him write down informations about occurances. Let them also use the log stamp function to find the relevant part in the logs.

 

[BWB8771]

Yurp.. gotta love FORFILES ;-)

IP 500 V2
IPOMgr/VMPro v9.1.0.437
46/5610s, 46/5621+25s
9640Gs

 

[Westi]

I agree with derfloh, log stamp is important and I usually inform the users that they HAVE TO LOG STAMP otherwise I will not be able to find the problem. I still can find it but it costs me extra time and I don't support laziness.

If I have to find problems with PRI's then I definitely check on all layers in the ISDN tab
the call and print options and I let it rollover every hour so that I can find the problem within a few hundred pages of log but normally I try to turn it off when there is no acute problem that needs troubleshooting.

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[IPGuru]

I am wit Westi (I think) & would not bother to leave Monitor running unless the customer is experiencing a regular problem that cannot be identified
The majority of IPO faults I investigate do not require the use of montor logging
when I do use monitor it is usaly for live monitoring t confirm my suspicians of wy customers outbound calls are failing (almost always incorrect digits beeing sent or provider issue).

My advise for anyone responsible for managing an IP Office is "Dont't go looking for trouble"



Do things on the cheap & it will cost you dear

 

[amriddle01]

There is no magic formula for monitor really, the filters and amount you need is dictated by the issue you're having or what you're trying to spot