Jeff, The SCH options don't really alert you. But the ability to use profiles is the only way to keep aware of the SLA status. Outside of scripting, I don't think you have any other options to monitor the SLA status.
Regards, Rama On Thu, Oct 13, 2011 at 8:40 AM, Jeff Cartier <[email protected]> wrote: > I took a look at the configuration examples of Smart Call Home and I don't > really see how it could alert me if the Internet goes down. I understand > that I could send me periodic outputs of the SLA statistics, but that would > mean I would be getting these outputs regularly at specific internals. > > Ideally I would like an alert only when the service goes down. > > > -----Original Message----- > From: Rama Darbha [mailto:[email protected]] > Sent: Wednesday, October 12, 2011 8:48 PM > To: Jeff Cartier > Subject: Re: [c-nsp] Monitoring Internet Reachability w/ ASA > > Jeff, > > SLA is the only option. But you're right, it doesn't support SNMP MIBs for > monitoring the SLA status. > > Instead of using SNMP you can use Smart Call Home and set up a profile to > email you regular output of the SLA status. This is outline here: > https://supportforums.cisco.com/docs/DOC-14958 > > Those are examples of monitoring other features. But you can tweak those > settings to work with monitoring SLA status. > > Regards, > Rama > > On Tue, Sep 27, 2011 at 8:26 AM, Jeff Cartier > <[email protected]> wrote: >> Hi Guys, >> >> Just a general question to the group on how one monitors Internet >> availability/reachability via an ASA. >> >> The scenario right now is we have a number of offices with Internet feeds >> (primarily DSL/Cable/T1) connected to ASAs and we have the goal of being >> able to monitor if the Internet connected to the ASA is UP or DOWN. My >> first thought was to configure an IP SLA and monitor the reachability of an >> upstream IP; however, all documentation I've read suggests that the ASA >> doesn't support the SLA MIBs yet. So I won't be able to use SNMP to track >> its availability. >> >> Just throwing the feeler out there for comments. >> >> Thanks everyone. >> >> >> >> __________________________________________________________________ >> DISCLAIMER: This e-mail contains proprietary information some or all of >> which may be legally privileged. It is for the intended recipient only. If >> an addressing or transmission error has misdirected this e-mail, please >> notify the author by replying to this e-mail. If you are not the intended >> recipient you must not use, disclose, distribute, copy, print, or rely on >> this e-mail. >> >> This message has been scanned for the presence of computer viruses, Spam, >> and Explicit Content. >> >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > __________________________________________________________________ > DISCLAIMER: This e-mail contains proprietary information some or all of which > may be legally privileged. It is for the intended recipient only. If an > addressing or transmission error has misdirected this e-mail, please notify > the author by replying to this e-mail. If you are not the intended recipient > you must not use, disclose, distribute, copy, print, or rely on this e-mail. > > This message has been scanned for the presence of computer viruses, Spam, and > Explicit Content. > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
