Monitoring Tandberg VCS Codecs with HP SIM

[Evgeniy.Glazkov]

Hello!

How can I directly catch and decode traps from Tandberg VCS Codecs with HP SIM 6.3?

MIB file, supplied with TMS, does not contain many traps descriptions, which understood by TMS.

[Paula Talamo]

Hello Evgeniy,

I am not sure I understand your question completely but if you are looking to monitor C-Series codecs outside of TMS, please reference the API guides http://www.cisco.com/en/US/products/ps11422/prod_command_reference_list.html as it is possible to retrieve configuration and status over HTTP/HTTPS.

Thank you,

Paula

[Evgeniy.Glazkov]

I found this:

http://www.cisco.com/en/US/docs/telepresence/system_messages/ct_syslog_snmp.html

and this:

ftp://ftp.cisco.com/pub/mibs/supportlists/cts/cts-supportlist.html

I think, this is what I need.

[epicolo]

Well, if the VCS mencioned is the Cisco Video Communication Server, it is not a Codec, it is a SIP Server/Gatekeeper.

This Cisco VCS don´t send SNMP traps and don´t have specific MIBs.

The TMS MIBs are user for TMS traps.

You can get information from VCS using SNMP based in MIB-2 RFC 1213 OIDs

PS: Regarding Cisco TAC, the C-Series Codecs don´t send SNMP traps either.

Regards

[Mahmoud Simrin]

Hello Elter,

Do you have a list of the thresholds/metrics of the alerts generated by the TMS ?

Thank you

[epicolo]

Hi Mahmoud,

here are some info:

The TMS receive a HTTP/HTTPS feedback from a device or generate its own status regarding that device and generate a SNMP Trap to its NMS on behalf of the device. The source will be the TMS Server, but inside the trap you have the device identification.

All traps use OID .1.3.6.1.4.1.5596.110.6.1 as attribute

Each device have its own ID inside TMS that inside the Trap, togheter with its system name.

The variable tmsEventTypeId (OID .1.3.6.1.4.1.5596.110.1.1) have these options :

boot(1)

linkDown(2)

linkUp(3)

lowBattery(6)

lostResponse(7)

gotResponse(8)

downspeeding(9)

authenticationFailure(18)

flowControl(21) - informational

ipConflict(22)

userAssistanceRequested(23)

rogueSystemFound(118)

preregisteredSystemActivated(119)

systemChangedType(120)

packetLossOccurred(121)

What is configured on TMS arrives with OID .1.3.6.1.4.1.5596.110.1.4

noAlert(0),

critical(1),

major(2),

minor(3),

warning(4),

cleared(5)

The traps with Clear Notification (to clear the last state) came with OID .1.3.6.1.4.1.5596.110.1.7

no(0)

yes(1)

Ex: A GotResponse(8) will have the clear flag yes(1).

Hope it helps.

regards

[Mahmoud Simrin]

Hello Elter,

How can I get to the to the TMS.MIB please ?