[cisco-voip] Monitoring H323 Gateways

[Tim Reimers]

heh. 

Had I seen this, I'd have posted EEM before you did
;-)

I'd also have to wonder about the possibilities of kron and a "sh isdn status"
looking for "multiple frame established"


-----Original Message-----
From: cisco-voip-bounces at puck.nether.net on behalf of Jim McBurnett
Sent: Sun 11/29/2009 9:15 PM
To: Chris Hill; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Monitoring H323 Gateways
 
Guys,
There are 2 methods I use to configure this for customers:
1. EEM-- embedded event manager..  
	http://www.cisco.com/en/US/products/ps6815/products_ios_protocol_group_home.html 
	It can watch syslog and send an email from the router--  
	and even issue commands to the router as a triggered event...
2. Kiwi syslog..- for those non-Linux types.
	It has a scripting engine where you can do some amazing things.
	www.kiwisyslog.com

Take a gander and see what ideas you can come up with for your needs.....


Jim



>From the EEM datasheet:


The applications are endless and only limited by your imagination.

Suppose, for example, you would like to automatically configure a switch interface depending on the device that is connected to a port or interface, an IP phone. A script can be devised that is triggered on the interface up condition and determines the details of the connected device. Upon discovery and verification of a newly connected IP phone, the port can be automatically configured according to prescribed parameters.

Another example might be to react to an abnormal condition such as the detection of a high error rate on an interface by forcing transit traffic over a more stable and error-free path. EEM can watch for the increased error rate and trigger a policy into action. The policy could notify network operations personnel and take immediate action to reroute traffic.

A third example might be to collect detailed data upon detection of a specific failure condition in order to gather information that can allow the root cause of the problem to be determined faster leading to a lower mean time to repair and higher availability. EEM could detect a specific Syslog message and trigger a script to collect detailed data using a series of show commands. After automatically collecting the data, it can be saved to flash memory or sent to an external management system or via email to a network operator.

The control is in the network administrator's hands. You control what events to detect and what actions to take. EEM is optional-it is up to the network administrator if and when it should be used and only takes the actions you program it to take.



-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Chris Hill
Sent: Sunday, November 29, 2009 9:12 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Monitoring H323 Gateways


Hi All,

I ran into scenario were we had 2 PRIs down but and all the syslogs had was some netclock errors and the interfaces bouncing. Believe this was caused by a provider issue.
But to of the PRIs did not come back, had to bounce the interface to get them back. 

The only thing that indicated a problem 6 hours after the bounce was when i debugged the isdn q.921 traffic...here i saw the bad frames.

I would like to know a way can monitor these PRIs. These PRIs are only used for incoming 1800 calls.

Can a syslog server be configured to send out emails based on isdn debug data?

Any suggestions?

Thanks

Chris Hill - CCNA, CCNA Voice, CCVP
chrishill.work at gmail.com



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091130/4cdf4c2b/attachment.html>