Cisco

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco FRU Power Supply Group	cisco.fru.total.availablecurrent	FRU Total Available Current	amps	Total current available for FRU usage.[OID: 1.3.6.1.4.1.9.9.117.1.1.1.1.3]
Cisco FRU Power Supply Group	cisco.fru.total.drawncurrent	FRU Total Drawn Current	amps	Total current drawn by powered-on FRUs.[OID: 1.3.6.1.4.1.9.9.117.1.1.1.1.4]
Cisco System Performance - CISCO-SYSTEM-EXT-MIB	nexus.cpu.utilization	CPU Utilization	%	The average utilization of CPU on the active supervisor.[OID - 1.3.6.1.4.1.9.9.305.1.1.1]
	nexus.memory.utilization	Memory Utilization	%	The average utilization of memory on the active supervisor.[OID - 1.3.6.1.4.1.9.9.305.1.1.2.0]
	system.uptime	System Uptime	s	The time (in seconds) since the entire system was last re-initialized as a result of reload.[CISCO-SYSTEM-EXT-MIB] - cseSysUpTime(1.3.6.1.4.1.9.9.305.1.1.10)
FRU Fan Status	cisco.fru.fan.status	FRU Fan Status		FRU Fan Status. Possible status values are 1 -Unknown,2 -Up,3 -Down,4 -Warning. Alerts if fan status in 3(Down) or 4(Warning) [OID: 1.3.6.1.4.1.9.9.117.1.4.1.1.1,1.3.6.1.2.1.47.1.1.1.1.2]
FRU Module Status	cisco.fru.module.status	FRU Module Status		FRU Module Status. Possible status values are 1 -Unknown,2 -OK,3 -Disabled,4 -OK,but diagnostics failed,5 -Boot,6 -Selftest,7 -Failed,8 -Missing,9 -Mismatch with parent,10 -Mismatch config,11 -Diagnostics failed,12 -Dormant,13 -Out of service admin,14 -Out of service env temp,15 -Powered down,16 -Powered up,17 -Power denied,18 -Power cycled,19 -OK,but power over warning,20 -OK,but power over critical,21 -Sync in progress,22 -Upgrading,23 -OK,but authfailed.[OID: 1.3.6.1.4.1.9.9.117.1.2.1.1.2,1.3.6.1.2.1.47.1.1.1.1.2]
FRU Power Status	cisco.fru.power.status	FRU Power Status		FRU Power Status. 1 -FRU powered off,2 -FRU powered on,3 -FRU power off by admin,4 -FRU powered off-denied,5 -FRU powered off-environment issue,6 -FRU powered off temperature problem,7 -FRU powered off - fan problem,8 -FRU powered off - failed,9 -
Virtual Device Context(VDC) Resource Usage - Across all VDCs	nexus.vdc.resource.usage	VDC Resource Usage	%	Monitors the utilization of VDC resource.[1.3.6.1.4.1.9.9.774.1.4.1.1.3,1.3.6.1.4.1.9.9.774.1.4.1.1.7]
Virtual Device Context(VDC) status	nexus.vdc	Nexus VDC		Current operational state of the virtual device. Possible values are 1=Active,2=Suspended,3=NonConfigured,4=Configured,5=Creating,6=Deleting,7=Failed,8=Pending,9=Updating,10=Restarting,11=Suspending,12=Resuming,13=Failing.[OID: 1.3.6.1.4.1.9.9.774.1.1.1.2,1.3.6.1.4.1.9.9.774.1.1.1.3]

Cisco NTP Peer Stats

Description

Template to monitor Cisco NTP Peers statistics like Peer OFFSET,Round-trip DELAY and DISPERSION irrespective of local clock and ROOT DELAY,ROOT DISPERSION irrespective of primary reference source at the root of the synchronization subnet.

Metric details:
1. cisco.ntp.peer.offset – The estimated offset of the peer clock relative to the local clock,in seconds.
2. cisco.ntp.peer.delay – The estimated round-trip delay of the peer clock relative to the local clock over the network path between them,in seconds.
3. cisco.ntp.peer.dispersion – The estimated maximum error of the peer clock relative to the local clock over the network path between them,in seconds.
4. cisco.ntp.peer.root.delay – A signed fixed-point number indicating the total round-trip delay in seconds,from the peer to the primary reference source at the root of the synchronization subnet.
5. cisco.ntp.peer.root.dispersion – The maximum error in seconds,of the peer clock relative to the primary reference source at the root of the synchronization subnet.
6. cisco.ntp.peer.mode – The association mode of the NTP server. Possible mode values
- 0 - unspecified
- 1 - symmetricActive
- 2 - symmetricPassive
- 3 - client
- 4 - server
- 5 - broadcast
- 6 - reservedControl
- 7 - reservedPrivate.
1. cisco.ntp.peer.mode.change – It represents whether NTP Peer mode changed or not. Defined some custom states to alert when NTP Peer mode changed from one state to another state.
- Here are those custom states
  - 0 - MODE_NOT_CHANGED
  - 1 - MODE_CHANGED.
- Here are actual NTP Peer modes
  - 0 - unspecified
  - 1 - symmetricActive
  - 2 - symmetricPassive
  - 3 - client
  - 4 - server
  - 5 - broadcast
  - 6 - reservedControl
  - 7 - reservedPrivate.
1. cisco.ntp.peer.org.time – The local time at the peer,when its latest NTP message was sent. This time is in seconds relative to 00:00 on 1 January 1900. If the peer becomes unreachable the value is set to zero.
Note: Implemented this template by taking CISCO-NTP-MIB as a reference. And that MIB was defined by referring to: D.L. Mills,‘Network Time Protocol (Version 3)',RFC-1305,March 1992,Sections 2,3.2.1.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco NTP Peer Stats - Ext	cisco.ntp.peer.offset	NTP Peer Offset (Seconds)	s	The estimated offset of the peer clock relative to the local clock,in seconds.[CISCO-NTP-MIB::cntpPeersPeerAddress - 1.3.6.1.4.1.9.9.168.1.2.1.1.3,cntpPeersOffset - 1.3.6.1.4.1.9.9.168.1.2.1.1.23,cntpPeersPeerName - 1.3.6.1.4.1.9.9.168.1.2.1.1.31]
	cisco.ntp.peer.delay	NTP Peer Delay (Seconds)	s	The estimated round-trip delay of the peer clock relative to the local clock over the network path between them,in seconds.[CISCO-NTP-MIB::cntpPeersPeerAddress - 1.3.6.1.4.1.9.9.168.1.2.1.1.3,cntpPeersDelay - 1.3.6.1.4.1.9.9.168.1.2.1.1.24,cntpPeersPeerName - 1.3.6.1.4.1.9.9.168.1.2.1.1.31]
	cisco.ntp.peer.dispersion	NTP Peer Dispersion (Seconds)	s	The estimated maximum error of the peer clock relative to the local clock over the network path between them,in seconds.[CISCO-NTP-MIB::cntpPeersPeerAddress - 1.3.6.1.4.1.9.9.168.1.2.1.1.3,cntpPeersDispersion - 1.3.6.1.4.1.9.9.168.1.2.1.1.25,cntpPeersPeerName - 1.3.6.1.4.1.9.9.168.1.2.1.1.31]
	cisco.ntp.peer.root.delay	NTP Peer Root Delay (Seconds)	s	The total round-trip delay in seconds,from the peer to the primary reference source at the root of the synchronization subnet.[CISCO-NTP-MIB::cntpPeersPeerAddress - 1.3.6.1.4.1.9.9.168.1.2.1.1.3,cntpPeersRootDelay - 1.3.6.1.4.1.9.9.168.1.2.1.1.13,cntpPeersPeerName - 1.3.6.1.4.1.9.9.168.1.2.1.1.31]
	cisco.ntp.peer.root.dispersion	NTP Peer Root Dispersion (Seconds)	s	The maximum error in seconds,of the peer clock relative to the primary reference source at the root of the synchronization subnet.[CISCO-NTP-MIB::cntpPeersPeerAddress - 1.3.6.1.4.1.9.9.168.1.2.1.1.3,cntpPeersRootDispersion - 1.3.6.1.4.1.9.9.168.1.2.1.1.14,cntpPeersPeerName - 1.3.6.1.4.1.9.9.168.1.2.1.1.31]
	cisco.ntp.peer.mode	NTP Peer Mode		The association mode of the NTP server. Possible values and their descriptions are 0 - unspecified,1 - symmetric active (A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer),2 - symmetric passive (This type of association is ordinarily created upon arrival of a message from a peer operating in the symmetric active mode and persists only as long as the peer is reachable and operating at a stratum level less than or equal to the host; otherwise,the association is dissolved. However,the association will always persist until at least one message has been sent in reply. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer),3 - client (A host operating in this mode sends periodic messages regardless of the reachability state or stratum of its peer. By operating in this mode the host,usually a LAN workstation,announces its willingness to be synchronized by,but not to synchronize the peer),4 - server (This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request,after which the association is dissolved. By operating in this mode the host,usually a LAN time server,announces its willingness to synchronize,but not to be synchronized by the peer),5 - broadcast (A host operating in this mode sends periodic messages regardless of the reachability state or stratum of the peers. By operating in this mode the host,usually a LAN time server operating on a high-speed broadcast medium,announces its willingness to synchronize all of the peers,but not to be synchronized by any of them),6 - reserved for NTP control messages,7 - reserved for private use.[CISCO-NTP-MIB::cntpPeersMode - 1.3.6.1.4.1.9.9.168.1.2.1.1.8]
	cisco.ntp.peer.mode.change	NTP Peer Mode Change		It represents whether NTP Peer mode changed or not. Defined some custom states to alert when NTP Peer mode changed from one state to another state. Here are those custom states,0 - MODE_NOT_CHANGED,1 - MODE_CHANGED. And here are actual NTP Peer modes,0 - unspecified,1 - symmetricActive,2 - symmetricPassive,3 - client,4 - server,5 - broadcast,6 - reservedControl,7 - reservedPrivate.[CISCO-NTP-MIB::cntpPeersMode - 1.3.6.1.4.1.9.9.168.1.2.1.1.8]
	cisco.ntp.peer.org.time	NTP Peer Time	s	The local time at the peer,when its latest NTP message was sent. This time is in seconds relative to 00:00 on 1 January 1900. If the peer becomes unreachable the value is set to zero.[CISCO-NTP-MIB::cntpPeersOrgTime - 1.3.6.1.4.1.9.9.168.1.2.1.1.17]
Cisco NTP Peer Stratum and Reachability	cisco.ntp.peer.stratum	NTP Peer Stratum		It monitors the stratum of the peer clock.[CISCO-NTP-MIB::cntpPeersPeerAddress - 1.3.6.1.4.1.9.9.168.1.2.1.1.3,cntpPeersStratum - 1.3.6.1.4.1.9.9.168.1.2.1.1.9]
Cisco NTP Peer Stratum and Reachability	cisco.ntp.peer.reachability	NTP Peer Reachability		A shift register of used to determine the reachability status of the peer,with bits entering from the least significant (rightmost) end. A peer is considered reachable if at least one bit in this register is set to one i.e,if the value of this object is non-zero. The data in the shift register would be populated by the NTP protocol procedures.[CISCO-NTP-MIB::cntpPeersPeerAddress - 1.3.6.1.4.1.9.9.168.1.2.1.1.3,cntpPeersReach - 1.3.6.1.4.1.9.9.168.1.2.1.1.21]

Cisco Presence Server - G2

Description

Monitors the Cisco Presence server performance metrics like CPU Utilization,Memory Utilization,Disk Utilization,Virtual Memory Usage and monitors statistics like IM sessions,Inbound SIP Subscriptions,Outbound SIP Subscriptions,Connected XMPP clients.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco Presence Server	xmpp.connected.count	Number of connected XMPP clients		Current number of XMPP clients connected to the Cisco XCP Connection Manager on an individual IM and Presence server.
	sip.activeoutbound.count	Number of active outbound SIP subscriptions		View the current number of active outgoing SIP Subscriptions being maintained by the Cisco XCP SIP Federation Connection Manager service on the IM and Presence server.
	sip.activeinbound.count	Number of active inbound SIP subscriptions		View the current number of active inbound SIP Subscriptions being maintained by the Cisco XCP SIP Federation Connection Manager service on the IM and Presence server.
	im.sessions.count	Number of IM sessions		This counter gives the total number of IM sessions on the IM and Presence node across all users.
	cisco.presence.memory.free	Cisco Presence Memory Free	KB	Cisco Presence Memory Free
	cisco.presence.db.replication.failure	State of Replication		This counter represents the state of replication. An alert will be created when the replication state is equal to 3. The following list provides possible values: 0-Initializing. The counter equals 0 when the server is not defined or when the server is defined but realizes the template has not completed. 1-Replication setup script fired from this node. Cisco recommends that you run utils dbreplication status on the CLI to determine the location and cause of the failure. 2-Good Replication. 3-Bad Replication. A counter value of 3 indicates replication in the cluster is bad. It does not mean that replication failed on a particular server in the cluster. Cisco recommends that you run utils dbreplication status on the CLI to determine the location and cause of the failure. 4-Replication setup did not succeed. An alert is generated when the replication state is equal to 3 or 4.
	cisco.presence.disk.swap.util	Cisco Presence Disk Swap Utilization	%	Cisco Presence disk swap utilization.
	cisco.presence.disk.utilization	Cisco Presence Disk Utilization	%	The total amout of disk space used on this file system.
	cisco.presence.virtual.memory.free	Cisco Presence Virtual Memory Free	KB	Cisco Presence Virtual Memory Free.
	cisco.presence.memory.utilization	Cisco Presence Memory Utilization	%	This counter displays the system physical memory utilization as a percentage. The value of this counter equals (Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes) / Total KBytes,which also corresponds to the Used KBytes/Total KBytes.
	cisco.presence.virtual.memory.util	Cisco Presence Virtual Memory Utilization	%	This counter displays the system virtual memory utilization as a percentage. The value of this counter equals (Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes + Used Swap KBytes) / (Total KBytes + Total Swap KBytes),which also corresponds to Used VM KBytes/Total VM KBytes.

Cisco QoS ClassMap Statistics

Description

It monitors Cisco QoS ClassMap Statistics like Pre Policy Bitrate per second,Traffic sent after QoS processing,Dropped Packets count and Traffic dropped as a result of QoS processing.

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco QoS ClassMap Statistics	cisco.qos.classmap.pre.policy.rate	QoS ClassMap Pre Policy Bit Rate	bps	It monitors QoS Class map inbound octets prior to executing any QoS policies. It counts the inbound octets and evaluates bit rate(bits per second).[CISCO-CLASS-BASED-QOS-MIB::1.3.6.1.4.1.9.9.166.1.15.1.1.5 or 1.3.6.1.4.1.9.9.166.1.15.1.1.6]
	cisco.qos.classmap.post.policy.rate	QoS ClassMap Post Policy Bit Rate	bps	It monitors QoS Class map outbound octets after executing QoS policies. It counts the outbound octets and evaluates bit rate(bits per second).[CISCO-CLASS-BASED-QOS-MIB::1.3.6.1.4.1.9.9.166.1.15.1.1.9 or 1.3.6.1.4.1.9.9.166.1.15.1.1.10]
	cisco.qos.classmap.drop.packets.count	QoS ClassMap Drop Packets Count		It monitors QoS Class map dropped packets per class as the result of all features that can produce drops (e.g.,police,random detect,etc.). It evaluates the metric value by subtracting previous monitoring poll value from current monitoring poll value [i.e Current_Poll_Drop_Packets - Prev_Poll_Drop_Packets].[CISCO-CLASS-BASED-QOS-MIB::1.3.6.1.4.1.9.9.166.1.15.1.1.13 or 1.3.6.1.4.1.9.9.166.1.15.1.1.14]
	cisco.qos.classmap.drop.rate	QoS ClassMap Drop Bit Rate	bps	It monitors QoS Class map dropped bytes per class as the result of all features that can produce drops (e.g.,police,random detect,etc.). Traffic dropped as a result of QoS processing. It counts the dropped bytes in the monitoring period and evaluates metric value in bps (bits per second).[CISCO-CLASS-BASED-QOS-MIB::1.3.6.1.4.1.9.9.166.1.15.1.1.16 or 1.3.6.1.4.1.9.9.166.1.15.1.1.17]

Cisco SB (Small Business) Hardware

Description

Monitors Cisco SB (Small Business) products main power supply status,temperature sensor status,fan status. Validated on CISCO SB switches with model : SG200,SG300 - 52,SG300-28P,SG500X-24P.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Description
Cisco SB Hardware - Fan	cisco.sb.fan.state	Cisco SB Fan Status	Provides the mandatory state of the fan being instrumented. Possible status values are 1- Normal,2- Warning,3- Critical,4- Shutdown,5- Not Present,6- Not Functioning. Alert is generated when status is equal to 2- Warning,3- Critical,4- Shutdown,6- Not Functioning.[OID: 1.3.6.1.4.1.9.6.1.101.83.1.1.1.3].
Cisco SB Hardware - Power Supply	cisco.sb.power.supply.state	Cisco SB Power Supply Status	Provides the mandatory state of the power supply being instrumented. Possible status values are 1- Normal,2- Warning,3- Critical,4- Shutdown,5- Not Present,6- Not Functioning. Alert is generated when status is equal to 2- Warning,3- Critical,4- Shutdown,6- Not Functioning.[OID: 1.3.6.1.4.1.9.6.1.101.83.1.2.1.3]
Cisco SB Hardware - Temperature	cisco.sb.temperature.sensor.status	Cisco SB Temperature Sensor Status	Provides the status value for the Sensor being instrumented.Possible status values are 1- Ok,2- Unavailable,3- Non Operational. Alert is generated when status is equal to 3- Non Operational.[OID: 1.3.6.1.4.1.9.6.1.101.53.15.1.10].

Cisco SB (Small Business) System Performance

Description

Monitors Cisco SB (Small Business) product CPU utilization and uptime. Validated on SG200,SG300 - 52,SG300-28P and SG500X-24P.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco SB Switch System Performance	cisco.sb.cpu.util.5min	Cisco SB CPU Utilization	%	Percentage of the device CPU utilization during the last 5 minutes. Alert is generated when this value exceeds the given threshold. If rlCpuUtilEnable == true then only returning CPU utilization else returning zero.[OID : 1.3.6.1.4.1.9.6.1.101.1.6,1.3.6.1.4.1.9.6.1.101.1.9].
SNMP Engine Uptime	system.uptime	SNMP Engine Uptime	s	The number of seconds since the value of the snmpEngineBoots object last changed.[OID : 1.3.6.1.6.3.10.2.1.3.0]

Cisco Sensor Status - G2

Description

This template monitors sensor data for environmental monitors such as temperature gauges.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco Sensor Status	cisco.entity.sensor.status	Sensor Status		This monitor indicates the present operational status of the sensor. Possible values are 1- Ok,2- Unavailable,3- Non Operational. It generates critical alert only if sensor operational status is 3(Non Operational) and generated warning alert if sensor operational status in 2(unavailable)

Cisco Site-to-Site VPN Tunnel Status

Description

Monitors the Cisco Phase-1 IKE Site-to-Site VPN Tunnel Status. This template will be supported by VG v2.70 or above [CISCO-IPSEC-FLOW-MONITOR-MIB.mib]

Prerequisites

SNMP should be enabled in end device and device should support CISCO-IPSEC-FLOW-MONITOR-MIB OIDs and SNMP credentials should be attached against the device in portal.

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco Site-to-Site VPN Tunnel (IKE) Status	cisco.vpn.ike.tunnel.status	VPN IKE Phase-1 tunnel status		Monitors the Cisco Phase-1 (IKE) Site-to-Site VPN Tunnel Status.[OID: 1.3.6.1.4.1.9.9.171.1.2.3.1.7]

Cisco Stack Switch Port Status - G2

Description

Applicable on Cisco Stack wise devices,monitors the stack wise switch status,port operation status,power port status etc.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Description
Cisco Stackwise Stack Port Operational Status	cisco.stackwise.stackport.operationalstatus	Cisco Stackwise Stack Port Operational Status	Provides the state of the stackport. Up - Connected and operational. down - Not connected to a neighbouring switch or administrative down. forcedDown - Shut down by stack manager due to mismatch or stackport errors. Possible value status are 1- Up,2- Down. { CISCO-STACKWISE-MIB::cswStackPortOperStatus[OID: 1.3.6.1.4.1.9.9.500.1.2.2.1.1] }
Cisco Stackwise Stack Power Port Status	cisco.stackwise.stackpowerport.operationalstatus	Cisco Stackwise Stack Power Port Oper Status	Provides the object is used to either set or unset the operational status of the stack port. Possible value status are 1- Enabled,2- Disabled. { CISCO-STACKWISE-MIB::cswStackPowerPortOperStatus[OID: 1.3.6.1.4.1.9.9.500.1.3.2.1.2] }
Cisco Stackwise Stack Power Port Status	cisco.stackwise.stackpowerport.linkstatus	Cisco Stackwise Stack Power Port Link Status	Provides the object is used to describe the link status of the stack port. Possible value status are 1- Up,2- Down. { CISCO-STACKWISE-MIB::cswStackPowerPortLinkStatus [OID:1.3.6.1.4.1.9.9.500.1.3.2.1.5] }
Cisco Stackwise Switch State	cisco.stackwise.switch.state	Cisco Stackwise Switch State	The current state of a switch: waiting - Waiting for a limited time on other switches in the stack to come online. progressing - Master election or mismatch checks in progress. added - The switch is added to the stack. ready - The switch is operational. sdmMismatch - The SDM template configured on the master is not supported by the new member. verMismatch - The operating system version running on the master is different from the operating system version running on this member. featureMismatch - Some of the features configured on the master are not supported on this member. newMasterInit - Waiting for the new master to finish initialization after master switchover (Master Re-Init). provisioned - The switch is not an active member of the stack. invalid - The switchs state machine is in an invalid state. removed - The switch is removed from the stack. Possible value staus are 1- Waiting,2- Progressing 3- added,4 - Ready,5 -SdmMismatch,6 - VerMismatch,7 - Feature Mismatch 8 - New MasterInit,9 - provisioned,10 - Invalid,11 - Removed. { CISCO-STACKWISE-MIB::cswSwitchState[OID: 1.3.6.1.4.1.9.9.500.1.2.1.1.6] }.

Cisco Stack Switch Status - G2

Description

Monitors runtime status for chassis,modules,ports,alarms etc.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Description
Cisco Stack Switch Chassis Monitors	cisco.stack.minor.alarm	Minor Alarm	The chassis minor alarm status. Possible values for this monitor (1: off,2: on).[OID: 1.3.6.1.4.1.9.5.1.2.11.0]
	cisco.stack.major.alarm	Major Alarm	The chassis major alarm status. Possible values for this monitor (1: off,2: on).[OID: 1.3.6.1.4.1.9.5.1.2.12.0]
	cisco.stack.temp.alarm	Temperature Alarm	The chassis temperature alarm status. Possible values for this monitor (1: off,2: on,3: critical).[OID: 1.3.6.1.4.1.9.5.1.2.13.0]
Cisco Stack Switch Chassis Ps1 Status	cisco.stack.chassis.ps1.status	Chassis PS 1 Status	Status of power supply number 1. Possible values for this monitor (1: other,2: ok,3: minorFault,4: majorFault).[OID: 1.3.6.1.4.1.9.5.1.2.4.0]
Cisco Stack Switch Chassis Ps2 Status	cisco.stack.chassis.ps2.status	Chassis PS 2 Status	Status of power supply number 2. Possible values for this monitor (1: other,2: ok,3: minorFault,4: majorFault).[OID: 1.3.6.1.4.1.9.5.1.2.7.0]
Cisco Stack Switch Chassis Ps3 Status	cisco.stack.chassis.ps3.status	Chassis PS 3 Status	Status of power supply number 3. Possible values for this monitor (1: other,2: ok,3: minorFault,4: majorFault). This object is only supported by systems that can have 3 or more power supplies.[OID: 1.3.6.1.4.1.9.5.1.2.21.0]
Cisco Stack Switch Fan Status	cisco.stack.chassis.fan.status	Chassis Fan Status	Status of the chassis fan. Possible values for this monitor (1: other,2: ok,3: minorFault,4: majorFault).[OID: 1.3.6.1.4.1.9.5.1.2.9.0]
Cisco Stack Switch HA Status	cisco.stack.ha.status	HA Status	Indicates the operational status of High System Availability feature. Possible values for this monitor (1: running,2: notRunning).[OID: 1.3.6.1.4.1.9.5.1.1.60,1.3.6.1.4.1.9.5.1.1.61]
Cisco Stack Switch Module Status	cisco.stack.module.status	Module Status	The operational status of the module. Possible values for this monitor (1: other,2: ok,3: minorFault,4: majorFault).[OID: 1.3.6.1.4.1.9.5.1.3.1.1.10,1.3.6.1.4.1.9.5.1.3.1.1.13]
Cisco Stack Switch Operational Status	cisco.stack.status	Stack Status	The operational status of the system. Possible values for this monitor (1: other,2: ok,3: minorFault,4: majorFault).[OID: 1.3.6.1.4.1.9.5.1.1.67.0]
Cisco Stack Switch Port Oper Status	cisco.stack.port.oper.status	Port Oper Status	The current operational status of the port. Possible values for this monitor (1: other,2: ok,3: minorFault,4: majorFault).[OID: 1.3.6.1.4.1.9.5.1.4.1.1.6]

Cisco Switch Cluster Status - G2

Description

Monitors the status of cluster management connectivity between the command switch and a cluster member in Cisco switches.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco Switch Cluster Status	cisco.switch.cluster.status	Switch Cluster Status		Monitors the status of cluster management connectivity between the command switch and a cluster member. Cluster management connectivity is determined by the exchange of cluster management messages between the command switch and a cluster member. A member that has failed to exchange cluster management messages with the command switch is deemed to be inactive. Otherwise,it is deemed to be active. Possible Values are 1- active,2- inactive.[OIDs: 1.3.6.1.4.1.9.9.134.1.2.1.1.2,1.3.6.1.4.1.9.9.134.1.2.1.1.3]

Cisco System Performance - G2

Description

This template can be applied on all Cisco devices. Monitors uptime,CPU usage,Memory usage and Contiguous Memory free. New template using new SNMP monitoring engine.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco CPU Utilization	cisco.cpu.utilization	CPU Utilization	%	CPU utilization is a key performance metric. It is the percentage of time the processor spends doing work (as opposed to being idle). It can be used to track CPU performance regressions or improvements and is a useful data point for performance problem investigations.[OIDs: 1.3.6.1.4.1.9.9.109.1.1.1.1.8]
Cisco Memory	cisco.memory.pool.util.percent	Memory Utilization	%	Monitors the memory utilization of all memory pools like processor pool,I/O pool,Fast pool etc.[OID: 1.3.6.1.4.1.9.9.48.1.1.1.2,1.3.6.1.4.1.9.9.48.1.1.1.4,1.3.6.1.4.1.9.9.48.1.1.1.5,1.3.6.1.4.1.9.9.48.1.1.1.6]
Cisco Memory	cisco.memory.pool.largest.free	Largest Memory Free	KB	Monitors the largest contiguous block of memory free.[OID: 1.3.6.1.4.1.9.9.48.1.1.1.2,1.3.6.1.4.1.9.9.48.1.1.1.7]
SNMP Engine Uptime	system.uptime	SNMP Engine Uptime	s	The number of seconds since the value of the snmpEngineBoots object last changed.[OID : 1.3.6.1.6.3.10.2.1.3.0]

Cisco System Performance - Old IOS Release

Description

Monitors parameters like cpu utilization,memory utilization and uptime. It applies on Cisco IOS software release later to 12.0(3)T and prior to 12.2(3.5).

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco CPU Utilization - Old IOS Release	cisco.cpu.utilization	CPU Utilization	%	CPU utilization is a key performance metric. It is the percentage of time the processor spends doing work (as opposed to being idle). It can be used to track CPU performance regressions or improvements and is a useful data point for performance problem investigations.[OIDs: 1.3.6.1.4.1.9.9.109.1.1.1.1.5]
Cisco Memory	cisco.memory.pool.util.percent	Memory Utilization	%	Monitors the memory utilization of all memory pools like processor pool,I/O pool,Fast pool etc.[OID: 1.3.6.1.4.1.9.9.48.1.1.1.2,1.3.6.1.4.1.9.9.48.1.1.1.4,1.3.6.1.4.1.9.9.48.1.1.1.5,1.3.6.1.4.1.9.9.48.1.1.1.6]
Cisco Memory	cisco.memory.pool.largest.free	Largest Memory Free	KB	Monitors the largest contiguous block of memory free.[OID: 1.3.6.1.4.1.9.9.48.1.1.1.2,1.3.6.1.4.1.9.9.48.1.1.1.7]
SNMP Engine Uptime	system.uptime	SNMP Engine Uptime	s	The number of seconds since the value of the snmpEngineBoots object last changed.[OID : 1.3.6.1.6.3.10.2.1.3.0]

Cisco System Performance Using Enhanced Memory MIB - G2

Description

Monitors Cisco parameters like Cisco IDS total CPU 1 minute and Cisco IDS memory pool utilization.[CISCO-PROCESS-MIB] - cpmCPUTotal1minRev(1.3.6.1.4.1.9.9.109.1.1.1.1.7); [CISCO-ENHANCED-MEMPOOL-MIB] - cempMemPoolName,cempMemPoolUsed,cempMemPoolFree.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco CPU Utilization - CISCO-PROCESS-MIB	cisco.cpu.total.1.minute	CPU Utilization in Last 1 Minute	%	The overall CPU busy percentage in the last 1 minute period.[OID: 1.3.6.1.4.1.9.9.109.1.1.1.1.7]
Cisco Memory Utilization - CISCO-ENHANCED-MEMPOOL-MIB	cisco.memory.pool.util.percent	Memory Utilization	%	It monitors the memory utilization of each memory pool except lsmpi_io memory pool.[OIDs: cempMemPoolUsed - 1.3.6.1.4.1.9.9.221.1.1.1.1.7,cempMemPoolFree - 1.3.6.1.4.1.9.9.221.1.1.1.1.8]
System Uptime	system.uptime	System Uptime	s	The time since the SNMP agent in the system was last re-initialized.[OID : 1.3.6.1.2.1.1.3.0]

Cisco System Performance Using Old Cisco MIBS - G2

Description

Monitors Cisco system performance parameters like CPU Utilization using old cisco mib,Memory utilizatilization and uptime. It is applicable on Cisco IOS Software releases prior to 12.0(3)T.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco IOSd CPU Utilization	cisco.cpu.utilization	CPU Utilization	%	5 minute exponentially-decayed moving average of the CPU busy percentage.[OID - 1.3.6.1.4.1.9.2.1.58.0]
Cisco Memory Utilization - 64 bit	cisco.memory.pool.util.percent	Memory Utilization	%	It monitors the memory utilization of each memory pool except pool type lsmpi_io.[OIDs: cempMemPoolHCUsed - 1.3.6.1.4.1.9.9.221.1.1.1.1.18,cempMemPoolHCFree - 1.3.6.1.4.1.9.9.221.1.1.1.1.20]
Cisco Memory Utilization - 64 bit	cisco.memory.pool.largest.free	Largest Memory Free	KB	Monitors the largest contiguous block of memory free.[OID: cempMemPoolHCLargestFree - 1.3.6.1.4.1.9.9.221.1.1.1.1.22]
SNMP Engine Uptime	system.uptime	SNMP Engine Uptime	s	The number of seconds since the value of the snmpEngineBoots object last changed.[OID : 1.3.6.1.6.3.10.2.1.3.0]

Cisco System Performance Using System EXT MIB - G2

Description

Monitors Cisco parameters like average utilization of memory,average utilization of CPU on the active supervisor and uptime since the entire system was last re-initialized.[CISCO-SYSTEM-EXT-MIB] - cseSysCPUUtilization(1.3.6.1.4.1.9.9.305.1.1.1.0); [CISCO-SYSTEM-EXT-MIB] - cseSysMemoryUtilization(1.3.6.1.4.1.9.9.305.1.1.2.0); [CISCO-SYSTEM-EXT-MIB] - cseSysUpTime(1.3.6.1.4.1.9.9.305.1.1.10)

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco System Performance - CISCO-SYSTEM-EXT-MIB	nexus.cpu.utilization	CPU Utilization	%	The average utilization of CPU on the active supervisor.[OID - 1.3.6.1.4.1.9.9.305.1.1.1]
	nexus.memory.utilization	Memory Utilization	%	The average utilization of memory on the active supervisor.[OID - 1.3.6.1.4.1.9.9.305.1.1.2.0]
	system.uptime	System Uptime	s	The time (in seconds) since the entire system was last re-initialized as a result of reload.[CISCO-SYSTEM-EXT-MIB] - cseSysUpTime(1.3.6.1.4.1.9.9.305.1.1.10)

Cisco UCM SNMP - Consolidated

Description

SNMP based template to monitor Cisco UCM components like CCM Availability,CCM Phone Registration Status,CCM Gateway Registration Status,CCM Inventory Monitoring,CCM Media Device Registration Status,CCM CTI Device Registration Status,CTI Device Status and CCM VMD Registration Status.

Prerequisites

Device should support all tables in CISCO-CCM-MIB

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Description
CCM Availability	ccm.avaiability	CCM Availability	Provides the current status of the call manager [OID: 1.3.6.1.4.1.9.9.156.1.1.2.1.2,1.3.6.1.4.1.9.9.156.1.1.2.1.3, 1.3.6.1.4.1.9.9.156.1.1.2.1.4,1.3.6.1.4.1.9.9.156.1.1.2.1.5,1.3.6.1.4.1.9.9.156.1.1.2.1.7,1.3.6.1.4.1.9.9.156.1.1.2.1.8]
CCM CTI Device Registration Status	ccm.ctidevice.inventory.status	CCM CTI Device Registration Status	Provides the registration status of a CTI device with the local call manager. The CTI device status changes from Unknown to Registered when the CTI device registers itself with the local CUCM. Possible values are :- unknown(1): The registration status of the CTI device is unknown,registered (2): The CTI device has successfully registered with the local call manager,unregistered (3): The CTI device is no longer registered with the local call manager, rejected(4): Registration request from the CTI device was rejected by the local call manager, partiallyregistered(5): At least one but not all of the lines are successfully registered to the local call manager(applicable only to SIP phones). [OIDs: 1.3.6.1.4.1.9.9.156.1.8.1.1.2,1.3.6.1.4.1.9.9.156.1.8.1.1.5]
CCM Gateway Registration Status	ccm.gateway.inventory.status	CCM Gateway Registration Status	Provides the registration status of a gateway with the local call manager. The Gateway status changes from Unknown to Registered when the Gateway registers itself with the local CUCM. Possible values are :- unknown(1): The registration status of the gateway is unknown,registered (2): The gateway has successfully registered with the local call manager, unregistered(3): The gateway is no longer registered with the local call manager, rejected(4): Registration request from the gateway was rejected by the local call manager, partiallyregistered(5): At least one but not all of the lines are successfully registered to the local call manager (applicable only to SIP phones). [OIDs: 1.3.6.1.4.1.9.9.156.1.3.1.1.2,1.3.6.1.4.1.9.9.156.1.3.1.1.5]
CCM Inventory Monitoring	cisco.ccm.registered.gateways	CCM Registered Gateways Count	Provides the number of gateways that are registered and actively in communication with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.8.0]
	cisco.ccm.unregistered.gateways	CCM Unregistered Gateways Count	Provides the number of gateways that are unregistered or have lost contact with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.9.0]
	cisco.ccm.rejected.gateways	CCM Rejected Gateways Count	Provides the number of gateways whose registration requests were rejected by the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.10.0]
	cisco.ccm.registered.vmds	CCM Registered VMDs Count	Provides the number of voice messaging devices that are registered and actively in communication with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.17.0]
	cisco.ccm.unregistered.vmds	CCM Unregistered VMDs Count	Provides the number of voice messaging devices that are unregistered or have lost contact with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.18.0]
	cisco.ccm.rejected.vmds	CCM Rejected VMDs Count	Provides the umber of voice messaging devices whose registration requests were rejected by the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.19.0]
	cisco.ccm.registered.ctidevices	CCM Registered CTI Devices Count	Provides the number of CTI devices that are registered and actively in communication with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.14.0]
	cisco.ccm.unregistered.ctidevices	CCM Unregistered CTI Devices Count	Provides the number of CTI devices that are unregistered or have lost contact with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.15.0]
	cisco.ccm.rejected.ctidevices	CCM Rejected CTI Devices Count	Provides the number of CTI devices whose registration requests were rejected by the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.16.0]
	cisco.ccm.registered.mediadevices	CCM Registered Media Devices Count	Provides the number of media devices that are registered and actively in communication with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.11.0]
	cisco.ccm.unregistered.mediadevices	CCM Unregistered Media Devices Count	Provides the number of media devices that are unregistered or have lost contact with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.12.0]
	cisco.ccm.rejected.mediadevices	CCM Rejected Media Devices Count	Provides the number of media devices whose registration requests were rejected by the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.13.0]
	cisco.ccm.registered.phones	CCM Registered Phones Count	Provides the number of phones that are registered and actively in communication with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.5.0]
	cisco.ccm.unregistered.phones	CCM Unregistered Phones Count	Provides the number of phone that are unregistered or have lost contact with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.6.0]
	cisco.ccm.rejected.phones	CCM Rejected Phones Count	Provides the number of phones whose registration requests were rejected by the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.7.0]
	cisco.ccm.partialregistered.phones	CCM Partially Registered Phones Count	Provides the number of phones that are partially registered with the local call manager.[OID: 1.3.6.1.4.1.9.9.156.1.5.31.0]
CCM Media Device Registration Status	ccm.mediadevice.inventory.status	CCM Media Device Registration Status	Provides the registration status of a Media device with the local call manager. The Media device status changes from Unknown to Registered when the Media device registers itself with the local CUCM. Possible values are: unknown(1): The registration status of the Media device is unknown, registered(2): The Media device has successfully registered with the local call manager, unregistered(3): The Media device is no longer registered with the local call manager, rejected(4): Registration request from the Media device was rejected by the local call manager,partiallyregistered (5): At least one but not all of the lines are successfully registered to the local call manager(applicable only to SIP phones). [OIDs: 1.3.6.1.4.1.9.9.156.1.6.1.1.2,1.3.6.1.4.1.9.9.156.1.6.1.1.5]
CCM Phone Registration Status	ccm.phone.inventory.status	CCM Phone Registration Status	Provides the registration status of a phone with the local call manager. The phone status changes from Unknown to Registered when the phone registers itself with the local CUCM. Possible values are: unknown(1): The registration status of the phone is unknown, registered(2): The phone has successfully registered with the local call manager, unregistered(3): The phone is no longer registered with the local call manager, rejected(4): Registration request from the phone was rejected by the local call manager, partiallyregistered(5): At least one but not all of the lines are successfully registered to the local call manager(applicable only to SIP phones). [OIDs: 1.3.6.1.4.1.9.9.156.1.2.1.1.20,1.3.6.1.4.1.9.9.156.1.2.1.1.7,1.3.6.1.4.1.9.9.156.1.2.1.1.21,1.3.6.1.4.1.9.9.156.1.2.1.1.22,1.3.6.1.4.1.9.9.156.1.2.1.1.26,1.3.6.1.4.1.9.9.156.1.2.1.1.27]Additional Info: 1) The name of the phone can be + MAC Address,where is SEP for Cisco SCCP and SIP Phones. In the case of other phones such as communicator (soft phone) it can be free-form name,a string which uniquely identifies the phone. 2) Phone Unregistered Reason: The reason code associated with unregistered phone. This is applicable only when phone registration status is unregistered(3). Unregistered reason can be one of the following: noError(0),unknown(1),noEntryInDatabase(2), databaseConfigurationError(3),deviceNameUnresolveable(4), maxDevRegExceeded(5),connectivityError(6),initializationError(7),deviceInitiatedReset(8), callManagerReset(9),deviceUnregistered(10),malformedRegisterMsg(11),sccpDeviceThrottling(12), keepAliveTimeout(13),configurationMismatch(14), callManagerRestart(15),duplicateRegistration(16), callManagerApplyConfig(17),deviceNoResponse(18),emLoginLogout(19),emccLoginLogout(20),energywisePowerSavePlus(21), callManagerForcedRestart(22),sourceIPAddrChanged(23),sourcePortChanged(24),registrationSequenceError(25), invalidCapabilities(26),fallbackInitiated(28),deviceSwitch(29) 3) Phone Registration Failure Reason: The reason code associated with registration failed phone. This is applicable only when phone registration status is unregistered(3). Registration failure reason can be one of the following: noError(0),unknown(1),noEntryInDatabase(2), databaseConfigurationError(3),deviceNameUnresolveable(4),maxDevRegExceeded(5),connectivityError(6), initializationError(7),deviceInitiatedReset(8), callManagerReset(9),authenticationError(10),invalidX509NameInCertificate(11),invalidTLSCipher(12), directoryNumberMismatch(13),malformedRegisterMsg(14), protocolMismatch(15),deviceNotActive(16), authenticatedDeviceAlreadyExists(17),obsoleteProtocolVersion(18), databaseTimeout(23),registrationSequenceError(25) ,invalidCapabilities(26),capabilityResponseTimeout(27), securityMismatch(28),autoRegisterDBError(29), dbAccessError(30),autoRegisterDBConfigTimeout(31), deviceTypeMismatch(32),addressingModeMismatch(33)
CCM VMD Registration Status	ccm.vmd.inventory.status	CCM VMD Registration Status	Provides the registration status of a Voice Messaging Device (VMD) with the local call manager. The VMD status changes from Unknown to Registered when the VMD registers itself with the local CUCM. Possible values are:- unknown(1): The registration status of the VMD is unknown,registered(2): The VMD has successfully registered with the local call manager, unregistered(3): The VMD is no longer registered with the local call manager, rejected(4): Registration request from the VMD was rejected by the local call manager, partiallyregistered(5): At least one but not all of the lines are successfully registered to the local call manager(applicable only to SIP phones). [OIDs: 1.3.6.1.4.1.9.9.156.1.12.1.1.2,1.3.6.1.4.1.9.9.156.1.12.1.1.5]
CTI Device Status	ccm.cti.device.status	CCM CTI Device Status	Provides the status of the CTI (Computer Telephony Integration) Device. The CTI Device status changes from unknown to registered when it registers itself with the local CCM. Possible status values are : unknown(1),registered(2),unregistered(3),rejected(4),partiallyregistered(5) . Alert is generated when the metric value is NOT EQUAL to 2 (registered).[OIDs : 1.3.6.1.4.1.9.9.156.1.8.1.1.2,1.3.6.1.4.1.9.9.156.1.8.1.1.4,1.3.6.1.4.1.9.9.156.1.8.1.1.5]

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco UCS B-Series NetworkElement Performance	ucs.sys.switch.operability	CISCO UCS Switch operability	NULL	CISCO UCS Switch operability
	ucs.sys.switch.psu.operability	CISCO UCS Switch PSU operability	NULL	CISCO UCS Switch PSU operability
	ucs.sys.switch.psu.operstate	CISCO UCS Switch PSU operstate	NULL	CISCO UCS Switch PSU operstate
	ucs.sys.switch.psu.power	CISCO UCS Switch PSU power	NULL	CISCO UCS Switch PSU power
	ucs.sys.switch.psu.presence	CISCO UCS Switch PSU presence	NULL	CISCO UCS Switch PSU presence
	ucs.sys.switch.psu.thermal	CISCO UCS Switch PSU thermal	NULL	CISCO UCS Switch PSU thermal
	ucs.sys.switch.psu.voltage	CISCO UCS Switch PSU voltage	NULL	CISCO UCS Switch PSU voltage
	ucs.sys.switch.switchcard.operability	CISCO UCS SwitchCard operability	NULL	CISCO UCS SwitchCard operability
	ucs.sys.switch.switchcard.operstate	CISCO UCS SwitchCard operstate	NULL	CISCO UCS SwitchCard operstate
	ucs.sys.switch.switchcard.power	CISCO UCS SwitchCard power	NULL	CISCO UCS SwitchCard power
	ucs.sys.switch.switchcard.presence	CISCO UCS SwitchCard presence	NULL	CISCO UCS SwitchCard presence
	ucs.sys.switch.switchcard.state	CISCO UCS SwitchCard state		CISCO UCS SwitchCard state
	ucs.sys.switch.switchcard.thermal	CISCO UCS SwitchCard thermal	NULL	CISCO UCS SwitchCard thermal
	ucs.sys.switch.switchcard.voltage	CISCO UCS SwitchCard voltage	NULL	CISCO UCS SwitchCard voltage
	ucs.sys.switch.thermal	CISCO UCS Switch thermal	NULL	CISCO UCS Switch thermal
	ucs.sys.switch.slot.switchether.port.operstate	ucs.sys.switch.slot.switchether.port.operstate	NULL	ucs.sys.switch.slot.switchether.port.operstate
	ucs.sys.switch.slot.switchfc.port.operstate	ucs.sys.switch.slot.switchfc.port.operstate	NULL	ucs.sys.switch.slot.switchfc.port.operstate
	ucs.sys.switch.fanmodule.fan.operability	CISCO UCS Switch Fan operability	NULL	CISCO UCS Switch Fan operability
	ucs.sys.switch.fanmodule.fan.operstate	CISCO UCS Switch Fan operstate	NULL	CISCO UCS Switch Fan operstate
	ucs.sys.switch.fanmodule.fan.power	CISCO UCS Switch Fan power	NULL	CISCO UCS Switch Fan power
	ucs.sys.switch.fanmodule.fan.presence	CISCO UCS Switch Fan presence	NULL	CISCO UCS Switch Fan presence
	ucs.sys.switch.fanmodule.fan.thermal	CISCO UCS Switch Fan thermal	NULL	CISCO UCS Switch Fan thermal
	ucs.sys.switch.fanmodule.fan.voltage	CISCO UCS Switch Fan voltage	NULL	CISCO UCS Switch Fan voltage

Monitor Name	Metric Name	Metric Display Name	Description
Cisco UCS Chassis Status	ucs.chassis.status	UCS Chassis Operational State	Provides the Cisco UCS equipment chassis distinguished name (DN),admin state and the operational status. Possible admin states are 1- Acknowledged,2- Re Acknowledge,3- Decommission,4- Remove,5- Enable Port Channel,6- Disable Port Channel,7- Auto Acknowledge. Possible equipment chassis operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.15.7.1.2,1.3.6.1.4.1.9.9.719.1.15.7.1.4,1.3.6.1.4.1.9.9.719.1.15.7.1.27]
Cisco UCS Fan Module Status	ucs.fan.module.status	UCS Fan Module Operational State	Provides the Cisco UCS equipment fan module distinguished name (DN) and the operational status. Possible equipment fan module operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.15.13.1.2,1.3.6.1.4.1.9.9.719.1.15.13.1.7]
Cisco UCS Fan Status	ucs.fan.status	UCS Fan Operational State	Provides the Cisco UCS equipment fan distinguished name (DN) and the operational status. Possible equipment fan operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.15.12.1.2,1.3.6.1.4.1.9.9.719.1.15.12.1.9]
Cisco UCS FEX Status	ucs.fabric.extender.status	UCS Fabric Extender Operational State	Provides the Cisco UCS equipment Fabric Extender (FEX) distinguished name (DN),admin state and the operational status. Possible admin states are 1- Acknowledged,2- Re Acknowledge,3- Decommission,4- Remove,5- Enable Port Channel,6- Disable Port Channel,7- Auto Acknowledge. Possible equipment fex operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.15.19.1.2,1.3.6.1.4.1.9.9.719.1.15.19.1.5,1.3.6.1.4.1.9.9.719.1.15.19.1.21]
Cisco UCS IO Card Status	ucs.iocard.status	UCS IO Card Operational State	Provides the Cisco UCS equipment IOCard distinguished name (DN) and the operational status. Possible equipment IOCard operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.15.30.1.2,1.3.6.1.4.1.9.9.719.1.15.30.1.25]
Cisco UCS Memory Array Status	ucs.memory.array.status	UCS Memory Array Operational State	Provides the Cisco UCS memory array distinguished name (DN) and the operational status. Possible memory array operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.30.1.1.2,1.3.6.1.4.1.9.9.719.1.30.1.1.11]
Cisco UCS Memory Buffer Unit Status	ucs.memory.buffer.unit.status	UCS Memory Buffer Unit Operational State	Provides the Cisco UCS memory buffer unit distinguished name (DN) and the operational status. Possible memory buffer unit operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.30.4.1.2,1.3.6.1.4.1.9.9.719.1.30.4.1.6]
Cisco UCS Memory Unit Status	ucs.memory.unitstatus	UCS Memory Unit Operational State	Provides the Cisco UCS memory unit distinguished name (DN) and the operational status. Possible memory unit operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.30.11.1.2,1.3.6.1.4.1.9.9.719.1.30.11.1.13]
Cisco UCS Processor Unit Status	ucs.proessor.unit.status	UCS Processor Operational State	Provides the Cisco UCS processor unit distinguished name (DN) and the operational status. Possible processor unit operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.41.9.1.2,1.3.6.1.4.1.9.9.719.1.41.9.1.9]
Cisco UCS PSU Status	ucs.power.supply.unit.status	UCS PSU Operational State	Provides the Cisco UCS equipment Power Supply Unit (PSU) distinguished name (DN) and the operational status. Possible equipment PSU operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.15.56.1.2,1.3.6.1.4.1.9.9.719.1.15.56.1.7]
Cisco UCS Storage Controller Status	ucs.storage.controller.status	UCS Storage Controller Operational State	Provides the Cisco UCS storage controller distinguished name (DN) and the operational status. Possible storage controller operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.45.1.1.2,1.3.6.1.4.1.9.9.719.1.45.1.1.6]
Cisco UCS Storage Local LUNs Status	ucs.storage.local.logical.unit.number.status	UCS Storage Local LUNs Status	Provides the Cisco UCS storage local logical unit numbers (LUNs) distinguished name (DN) and the operational status. Possible storage local logical unit numbers (LUNs) operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.45.8.1.2,1.3.6.1.4.1.9.9.719.1.45.8.1.9]
Cisco UCS Storage Logical Disk Slot Status	ucs.storage.logical.disk.slot.status	UCS Storage Logical Disk Slot Status	Provides the Cisco UCS storage logical disk slot distinguished name (DN) and the operational status. Possible storage logical disk slot operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.45.13.1.2,1.3.6.1.4.1.9.9.719.1.45.13.1.6]
Cisco UCS Storage Logical Disk Status	ucs.storage.logical.disk.status	UCS Storage Logical Disk Status	Provides the Cisco UCS storage logical disk distinguished name (DN) and the operational status. Possible storage logical disk operational states are 0-Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7- Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed FRU,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.45.4.1.2,1.3.6.1.4.1.9.9.719.1.45.4.1.9]
Cisco UCS Storage Raid Battery Status	ucs.storage.raid.battery.status	UCS Storage Raid Battery Operational Status	Provides the Cisco UCS storage raid battery distinguished name (DN) and the operational status. Possible storage raid battery operational states are 0- Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7-Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed Fru,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto Upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.45.11.1.2,1.3.6.1.4.1.9.9.719.1.45.11.1.9]
Cisco UCS Switch Card Status	ucs.switch.card.status	UCS Switch Card Operational State	Provides the Cisco UCS equipment switch card distinguished name (DN) and the operational status. Possible equipment switch card operational states are 0-Unknown,1- Operable,2- Inoperable,3- Degraded,4- Powered Off,5- Power Problem,6- Removed,7- Voltage Problem,8- Thermal Problem,9- Performance Problem,10- Accessibility Problem,11- Identity Unestablishable,12- Bios Post Timeout,13- Disabled,14- Malformed FRU,51- Fabric Connection Problem,52- Fabric Unsupported Connection,81- Config,82- Equipment Problem,83- Decomissioning,84- Chassis Limit Exceeded,100- Not Supported,101- Discovery,102- Discovery Failed,103- Identify,104- Post Failure,105- Upgrade Problem,106- Peer Communication Problem,107- Auto upgrade,108- Link Activate Blocked.[OIDs: 1.3.6.1.4.1.9.9.719.1.15.70.1.2,1.3.6.1.4.1.9.9.719.1.15.70.1.9]

Cisco UCS C-Series Rack Server Health

Description

Monitors the cisco UCS C-Series rack server parameters power supply status,admin state,availability state,operation status,memory used.

Prerequisites

No prerequisite

Supported Metric

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco UCS C-Series Rack Server Health	cisco_ucs_RackUnitAvailability	Cisco UCS Rack Unit Availability		Monitors the availability state of rack unit.[CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeRackUnitAvailability:1.3.6.1.4.1.9.9.719.1.9.35.1.8]
	cisco_ucs_RackUnitMemoryUsed	Cisco UCS Rack Unit Memory Used	Bytes	Monitors the cisco UCS rack unit memory used.[CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeRackUnitTotalMemory:1.3.6.1.4.1.9.9.719.1.9.35.1.49,cucsComputeRackUnitAvailableMemory:1.3.6.1.4.1.9.9.719.1.9.35.1.9]
	cisco_ucs_RackUnitAdminPower	Cisco UCS Rack Unit Admin Power		Monitors the power state of the Rack Unit.[CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeRackUnitAdminPower:1.3.6.1.4.1.9.9.719.1.9.35.1.4]
	cisco_ucs_RackUnitOperState	Cisco UCS Rack Unit Operating State		Monitors the cisco UCS rack unit operating state.[CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeRackUnitOperState:1.3.6.1.4.1.9.9.719.1.9.35.1.42]
	cisco_ucs_RackUnitAdminState	Cisco UCS Rack Unit Admin State		Monitors the cisco UCS rack unit admin state.[CISCO-UNIFIED-COMPUTING-TC-MIB::cucsComputeRackUnitAdminState:1.3.6.1.4.1.9.9.719.1.9.35.1.5]

Cisco UCS C-Series RackServer Performance

Description

Cisco UCS C-Series RackServer Performance

Prerequisites

No prerequisite

Monitor Name	Metric Name	Metric Display Name	Unit	Description
Cisco UC Performance Monitor	cisco.uc.mem.util	Memory Utilization	%	Cisco unified communications memory utilization.
	cisco.uc.cpu.utilization	CPU Utilization	%	Cisco unfied communcations CPU Utilization.
	cisco.uc.disk.util	Disk Utilization	%	Cisco unified communications disk utilization.
	cisco.uc.disk.swap.util	Disk Swap Utilization	%	Cisco unified communications disk swap utilization.
	cisco.uc.disk.queue.length	Disk Queue Length	NULL	Disk queue length.
	cisco.uc.virtual.mem.free	Virtual Memory Free	KB	Cisco unified communications virtual memory free.
	cisco.uc.mem.free	Memory Free	KB	Cisco unified communications memory free.
	cisco.uc.virtual.mem.util	Virtual Memory Usage	%	Cisco unified communications virtual memory usage.
Cisco UC Standard Monitor	cisco.uc.interface.tx.errors	Tx Errors	pmin	Metrics calculates transmitted errors rate per minute [Rate = (CurrPollValue - PrevPollValue) / (CurrPollTime - PrevPollTime)]
	cisco.uc.interface.rx.errors	Rx Errors	pmin	Metrics calculates transmitted errors rate per minute [Rate = (CurrPollValue - PrevPollValue) / (CurrPollTime - PrevPollTime)]
	cisco.uc.replication.state	DB Replication State	NULL	This counter represents the state of replication. The following list provides possible values: 0-Initializing. The counter equals 0 when the server is not defined or when the server is defined but realizes the template has not completed. 1-Replication setup script fired from this node. Cisco recommends that you run utils dbreplication status on the CLI to determine the location and cause of the failure. 2-Good Replication. 3-Bad Replication. A counter value of 3 indicates replication in the cluster is bad. It does not mean that replication failed on a particular server in the cluster. Cisco recommends that you run utils dbreplication status on the CLI to determine the location and cause of the failure. 4-Replication setup did not succeed.
	cisco.uc.db.change.notification.reqs.queued	DB Change Notification Requests Queued	NULL	Cisco unified communications express db change notification requests queued.
	cisco.uc.db.change.notification.reqs.queued.mem	DB Change Notification Requests Queued Memory	NULL	Cisco unified communications db change notification requests queued memory.
	cisco.uc.active.client.connections	Active Client Connections	NULL	Cisco unified communications active client connections.
	cisco.uc.db.cn.processed	DB Change Notifications Processed	NULL	This counter represents the number of change notification messages processed by the server since reboot.
	cisco.uc.db.queue.delay	DB Queue Delay	s	This counter represents the number of seconds that the change notification process has to process messages,but is not processing them. This condition is true if either Change Notification Requests Queued in Database (QueuedRequestsInDB) and Change Notification Requests Queued in Memory (QueuedRequestsInMemory) are set to a value of non-zero or the Latest Change Notification Messages Processed count is not changing.
	cisco.uc.shared.memory.used	DB Local DSN Shared Memory Used	NULL	This counter represents the shared memory that is used.
	cisco.uc.ccm.db.space.used	Ccm DB Space Used	NULL	This counter represents the amount of Ccm DbSpace that is being consumed.
	cisco.uc.cn.db.space.used	Change Notifications DB Space Used	%	This counter represents the percentage of change notification (CN) DSspace that is being consumed.
	cisco.uc.ccmtemp.db.space.used	Ccmtemp DB Space Used	NULL	This counter represents the amount of Ccmtemp DbSpace that is being consumed.
	cisco.uc.shared.memory.free	DB Local DSN Shared Memory Free	NULL	This counter represents the shared memory that is free.
	cisco.uc.root.db.space.used	Root Database Space Used	NULL	This counter represents the amount of RootDbSpace that is being consumed.
	cisco.uc.er.db.space.used	Enterprise Replication DB Space Used	NULL	This counter represents the amount of enterprise replication DbSpace that was consumed.
	cisco.uc.ersb.db.space.used	ERDbSpace Used	NULL	This counter represents the amount of ERDbSpace that was consumed.
Cisco UC Unity Connection	cisco.uc.database.disk.free.chunk	Database Disk Free Chunk	NULL	The amount of free space available[in kilobytes]in the selected data chunk.
	cisco.uc.cuc.msg.bad.mail.total	Bad Mail Total	NULL	This metirc computes Delta value for the counter Bad Mail Total. The Bad Mail Total counter represents total number of messages sent to the Bad Mail folder since the last restart of the MTA server.
	cisco.uc.cuc.phone.call.count.current	Call Count Current	NULL	The current number of incoming and outgoing calls to the Cisco Unity Connection server.
	cisco.uc.imap.server.errors.total	IMAP Errors Total	NULL	This metirc computes Delta value for the counter Errors Total.The Errors Total counter represents total number of IMAP errors that the IMAP server returned since the last restart of the IMAP server.
	cisco.uc.cuc.msg.non.delivery.receipts.total	Non Delivery Receipts Total	NULL	This metirc computes Delta value for the counter Non-delivery Receipts Total.The Non-delivery Receipts Total counter represents total number of non-delivery receipts since the last restart of the MTA server.
	cisco.uc.cuc.phone.in.calls.cfb.total	Incoming Calls CFB Total	NULL	The total number of incoming calls that were received as Call Forward No Answer.
	cisco.uc.cuc.phone.in.calls.cfna.total	Incoming Calls CFNA Total	NULL	The total number of incoming calls that were received as Call Forward No Answer.
	cisco.uc.cuc.phone.in.calls.current	Incoming Calls Current	NULL	The current number of incoming calls.
	cisco.uc.cuc.phone.mwi.reqs.failed.total	MWI Requests Failed Total	NULL	This metirc computes Delta value for the counter MWI Requests Failed Total. The MWI Requests Failed Total counter represents total number of MWI requests that failed to connect to a destination number or complete MWI operation.
	cisco.uc.cuc.phone.out.calls.release.transfers.failed	Outgoing Calls Release Transfers Failed	NULL	This metric computes Delta value for the counter Outgoing Calls Release Transfers Failed. The Outgoing Calls Release Transfers Failed counter represents number of release transfers from the Cisco Unity Connection server that failed to connect to a destination number.
	cisco.uc.cuc.phone.pager.notifications.failed	Pager Notifications Failed	NULL	This metric computes Delta value for the counter Pager Notifications Failed. The Pager Notifications Failed counter represents total number of pager notifications that failed to connect to a destination number.
	cisco.uc.cuc.phone.port.idle.duration.avg	Port Idle Duration Average in Seconds	NULL	The average time [in seconds]that any port remains idle between incoming calls to the Cisco Unity Connection server.
	cisco.uc.cuc.phone.ports.idle.current	Ports Idle Current	NULL	The current number of integration ports that are not in use by the Cisco Unity Connection server.
	cisco.uc.cuc.phone.ports.in.use.current	Ports In Use Current	NULL	The current number of integration ports that are in use by the Cisco Unity Connection server.
	cisco.uc.cuc.personal.call.rules.transfer.failed	Transfer Failed	NULL	This metric computes Delta value for the counter Transfer Failed. The Transfer Failed counter represents number of times that Cisco Unity Connection fails to transfer a call to a destination while personal call transfer rules were applied. Transfer failures include all conditions except when the called destination is connected,busy,or RNA or times out. A caller hanging up during a transfer gets considered a transfer failure.