RE: [WhatsUp Forum] Service levels alerting

[Steven Williams]

Depends on what technology your network is running.   If you were running on frame relay, another way of doing this is to use traps based off the frDLCIStatusChange OID .1.3.6.1.2.1.10.32.0.1 to notify of a PVC status change or you could poll the frCiruitState OID .1.3.6.1.2.1.10.32.2.1.3 per PVC.   If you are extra paranoid, you could also monitor frCircuitSentOctects / frReceivedOctets per PVC and do some threshold alerts on the secondary PVC once traffic exceeds a certain value. This would be more accurate of a link / service issue than relying on latency as a large file copy could blow these figures out.   You could apply a similar method for any service….   Steve   Steve Williams Communications Support Engineer Computershare Technology Services Melbourne Australia [EMAIL PROTECTED] +61 3 9235 5651   www.computershare.com       -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 11:20 PM To: [EMAIL PROTECTED] Subject: [WhatsUp Forum] Service levels alerting   Does anyone know if it is possible to set different thresholds for alerting on a device (without creating a duplicate device)?  In other words a device's timeout may be set to 5 seconds as a worst case scenario but the average response is around 400ms, but in the case of a WAN link running on its backup circuit the line will still be functioning but performance will be degraded and the response times could average above 1 second.  What I would like is an alert warning that the WAN may be running on the backup circuit so that someone can follow up and log a call. Thanks James This e-mail, including attachments, is intended for the person(s) or company named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender --- This email and any files transmitted with it are solely intended for the use of the addressee(s) and may contain information that is confidential and privileged. If you receive this email in error, please advise us by return email immediately. Please also disregard the contents of the email, delete it and destroy any copies immediately. Computershare Limited and its subsidiaries do not accept liability for the views expressed in the email or for the consequences of any computer viruses that may be transmitted with this email. This email is also subject to copyright. No part of it should be reproduced, adapted or transmitted without the written consent of the copyright owner.