08-05-2015 12:15 AM - edited 03-18-2019 04:49 AM
hi, guys
As we have deployed the cisco VCS system for our customer for their video conference, we want to find some solution to
monitor the devices like VCS-C , VCS-E and MCU now, but we still failed to monitor the device even if we had configure the
MIB and OID to the SNMP server, just the network interface can be found on the system.
the information about SNMP monitor of VCS we can only find as following , can anyone help us and provide more useful
information?
VCS SNMP MIBS
VCS only supports basic SNMP mib .1.3.6.1.2.1
Does not support SNMP traps or sets
Sample SNMP Walk of VCS:
# snmpwalk -v 2c -c public vcs-03-rtp.tbtp2.com
SNMPv2-MIB::sysDescr.0 = STRING: TANDBERG Video Communication Server
SNMPv2-MIB::sysObjectID.0 = OID: ccitt.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (53280498) 6 days, 4:00:04.98
SNMPv2-MIB::sysContact.0 = STRING: Scott Page
SNMPv2-MIB::sysName.0 = STRING: vcs-03-rtp
SNMPv2-MIB::sysLocation.0 = STRING: RTP
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORID.1 = OID: SNMP-MPD-MIB::snmpMPDMIBObjects.3.1.1
SNMPv2-MIB::sysORID.2 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance
SNMPv2-MIB::sysORID.3 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.4 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.5 = OID: TCP-MIB::tcpMIB
SNMPv2-MIB::sysORID.6 = OID: IP-MIB::ip
SNMPv2-MIB::sysORID.7 = OID: UDP-MIB::udpMIB
SNMPv2-MIB::sysORID.8 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
SNMPv2-MIB::sysORDescr.1 = STRING: The MIB for Message Processing and Dispatching.
SNMPv2-MIB::sysORDescr.2 = STRING: The MIB for Message Processing and Dispatching.
SNMPv2-MIB::sysORDescr.3 = STRING: The SNMP Management Architecture MIB.
SNMPv2-MIB::sysORDescr.4 = STRING: The MIB module for SNMPv2 entities
SNMPv2-MIB::sysORDescr.5 = STRING: The MIB module for managing TCP implementations
SNMPv2-MIB::sysORDescr.6 = STRING: The MIB module for managing IP and ICMP implementations
SNMPv2-MIB::sysORDescr.7 = STRING: The MIB module for managing UDP implementations
SNMPv2-MIB::sysORDescr.8 = STRING: View-based Access Control Model for SNMP.
SNMPv2-MIB::sysORUpTime.1 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.2 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.3 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.4 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.5 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.6 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.7 = Timeticks: (1) 0:00:00.01
SNMPv2-MIB::sysORUpTime.8 = Timeticks: (1) 0:00:00.01
What are the SNMP System OIDs for Cisco TelePresence infrastructure products?
This article applies to the following products:
Cisco TelePresence MCU product family
Cisco TelePresence IP VCR product family
Cisco TelePresence ISDN GW product family
Cisco TelePresence IP GW product family
Cisco TelePresence Advanced Media Gateway 3610
Cisco TelePresence Supervisor MSE 8050
Cisco TelePresence Serial Gateway Series
Some of the products in this article were formerly manufactured by TANDBERG/Codian. The System Object IDs (OIDs) for these products follow the format:
1.2.826.0.1.4616240.1.<Product ID>.<Model Number>
where the product IDs are:
MCU: 1
IP VCR: 2
ISDN GW: 3
IP GW: 4
AM GW: 5
Supervisor: 7
Serial GW: 8
Product name System OID
Cisco TelePresence MCU 4203 1.2.826.0.1.4616240.1.1.4203
Cisco TelePresence MCU 4205 1.2.826.0.1.4616240.1.1.4205
Cisco TelePresence MCU 4210 1.2.826.0.1.4616240.1.1.4210
Cisco TelePresence MCU 4215 1.2.826.0.1.4616240.1.1.4215
Cisco TelePresence MCU 4220 1.2.826.0.1.4616240.1.1.4220
Cisco TelePresence MCU 4501 1.2.826.0.1.4616240.1.1.4501
Cisco TelePresence MCU 4505 1.2.826.0.1.4616240.1.1.4505
Cisco TelePresence MCU 4510 1.2.826.0.1.4616240.1.1.4510
Cisco TelePresence MCU 4515 1.2.826.0.1.4616240.1.1.4515
Cisco TelePresence MCU 4520 1.2.826.0.1.4616240.1.1.4520
Cisco TelePresence MCU 5310 1.3.6.1.4.1.9.1.1540
Cisco TelePresence MCU 5320 1.3.6.1.4.1.9.1.1541
Cisco TelePresence MCU MSE 8420 1.2.826.0.1.4616240.1.1.8420
Cisco TelePresence MCU MSE 8510 1.2.826.0.1.4616240.1.1.8510
Cisco TelePresence IP VCR 2210 1.2.826.0.1.4616240.1.2.2210
Cisco TelePresence IP VCR 2220 1.2.826.0.1.4616240.1.2.2220
Cisco TelePresence IP VCR 2240 1.2.826.0.1.4616240.1.2.2240
Cisco TelePresence VCR MSE 8220 1.2.826.0.1.4616240.1.2.8220
Cisco TelePresence ISDN GW 3421 1.2.826.0.1.4616240.1.3.3421
Cisco TelePresence ISDN GW MSE 8321 1.2.826.0.1.4616240.1.3.8321
Cisco TelePresence IP GW 3510 1.2.826.0.1.4616240.1.4.3510
Cisco TelePresence IP GW 3520 1.2.826.0.1.4616240.1.4.3520
Cisco TelePresence IP GW 3540 1.2.826.0.1.4616240.1.4.3540
Cisco TelePresence IP GW MSE 8350 1.2.826.0.1.4616240.1.4.8350
Cisco TelePresence Advanced Media Gateway 3610 1.2.826.0.1.4616240.1.5.3610
Cisco TelePresence Supervisor MSE 8050 1.2.826.0.1.4616240.1.7.8050
Cisco TelePresence Serial GW 3340 1.2.826.0.1.4616240.1.8.3340
Cisco TelePresence Serial GW MSE 8330 1.2.826.0.1.4616240.1.8.8330
08-05-2015 12:32 AM
Hi Qiyu,
The best solution is to introduce a Cisco Telepresence Management Suite (TMS) on your network to manage your videoconference infrastructure as well as your video endpoints.
Regards,
Ace
04-20-2016 01:16 AM
Hi Acevirgil,
Careful, TMS does not monitor as SNMP can do.
Cisco Prime Collaboration Assurance Advanced does it very deeply, but its really expensive.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide