[cisco-voip] Monitoring IPCC Express / Enterprise components

[Johnny Crothers]

Thanks Matt and Jonathan,

What about for prior releases? I think, I'll have to confirm but the
customer is running IPCC Enterprise 2.3? also we have a IPCC Express
4.0(4) implementation that i would also like to setup for monitoring.


-----Original Message-----
From: Matthew Saskin [mailto:matt at saskin.net] 
Sent: 21 March 2007 16:54
To: Johnny Crothers
Cc: Jonathan Charles; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Monitoring IPCC Express / Enterprise
components

ICM/IPCC Enterprise is relatively easy to monitor remotely. With both 
4.6.x and 6.x on the HDS you can keep an eye on the 
t_Peripheral_Real_Time table in the AWDB database. It has two fields 
that are useful:
'Online' - 0 or 1, which indicates whether the peripheral is fully 
functioning or not
'Status' - Numeric code from 0-127 (iirc) which have different meanings 
depending on what type of peripheral you have.

The same table also can give you general statistical information (agents

logged in, calls in progress, calls handled today, etc...)

This is pulling status from the HDS database which is kept up to date in

real-time by the routers/loggers. Unavailability of the database as a 
whole would indicate HDS problems, updates to this table not occuring 
would indicate replication failures or potentially central controller 
troubles, and specific peripherals can be watched one at a time. In the 
specific case of a PG running a VRU PIM for example, the 'Status' codes 
are either 0 (working fine), 33 (1 subsystem out of service), 66 (I 
think, multiple subsystems out of service), or 127 (peripheral 
completely offline)

-Matt

Johnny Crothers wrote:
>
> Yeah, the services are fine (monitoring them at the moment), its just 
> when they change to a partial etc, windows services don't show a 
> partial service.
>
>
------------------------------------------------------------------------
>
> *From:* Jonathan Charles [mailto:jonvoip at gmail.com]
> *Sent:* 21 March 2007 16:37
> *To:* Johnny Crothers
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Monitoring IPCC Express / Enterprise 
> components
>
> Either set up Syslog or SNMP and you will be told when the services
die...
>
>
>
> Jonathan
>
> On 3/21/07, *Johnny Crothers* < Johnny.Crothers at vanco.co.uk 
> <mailto:Johnny.Crothers at vanco.co.uk>> wrote:
>
> I meant from a monitoring platform, instead of checking things on a 
> daily/weekly basis I would like to set this up so if we do get a 
> failure, its alerted rather than having to find out manually if you 
> get my gist?
>
>
------------------------------------------------------------------------
>
> *From:* Jonathan Charles [mailto:jonvoip at gmail.com 
> <mailto:jonvoip at gmail.com>]
> *Sent:* 21 March 2007 16:27
> *To:* Johnny Crothers
> *Cc:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] Monitoring IPCC Express / Enterprise 
> components
>
> Which version of Express?
>
> It is pretty simple, left menu, control center ... see what the status

> is...
>
>
>
> Jonathan
>
> On 3/21/07, *Johnny Crothers *<Johnny.Crothers at vanco.co.uk 
> <mailto:Johnny.Crothers at vanco.co.uk>> wrote:
>
> I've been asked to investigate how to monitor the engine status of 
> IPCC Express and Enterprise.
>
> Is there somewhere where I can find out if a service is in 
> "partial_service or "out_of_service" etc other than having to monitor 
> the log files to see if it fails? Is the status stored in a CRS DB 
> table? Anyone have any details on this?
>
> We are currently using Prognosis to monitor VoIP implementations 
> although it seems to be lacking in the ability to monitor IPCC. Any 
> suggestions?
>
> Thanks for the help!
>
>
>
> **********************************************************************
> Any opinions expressed in the email are those of the individual and 
> not necessarily the company. This email and any files transmitted with

> it are confidential and solely for the use of the intended recipient. 
> If you are not the intended recipient or the person responsible for 
> delivering it to the intended recipient, be advised that you have 
> received this email in error and that any dissemination, distribution,

> copying or use is strictly prohibited.
>
> If you have received this email in error, or if you are concerned with

> the content of this email please e-mail to: 
> e-security.support at vanco.info <mailto:e-security.support at vanco.info>
>
> The contents of an attachment to this e-mail may contain software 
> viruses which could damage your own computer system. While the sender 
> has taken every reasonable precaution to minimise this risk, we cannot

> accept liability for any damage which you sustain as a result of 
> software viruses. You should carry out your own virus checks before 
> opening any attachments to this e-mail.
>
> Vanco UK Ltd Registered in England No: 2296733 Registered Office: John

> Busch House, 277 London Road, Isleworth, Middlesex TW7 5AX
> **********************************************************************
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto: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
>