MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 473 (ciscoCcaMIB). 1 (ciscoCcaMIBObjects). 2 (cccaComponents). 3 (cccaComponentElmtTable)
OID : 1.3.6.1.4.1.9.9.473.1.2.3
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoCcaMIB. ciscoCcaMIBObjects. cccaComponents. cccaComponentElmtTable
Enfants
D├ętails
OID1.3.6.1.4.1.9.9.473.1.2.3
Module CISCO-CONTACT-CENTER-APPS-MIB (CISCO)
NomcccaComponentElmtTable
Statuscurrent
DescriptionThe component element table provides a list of component (operating system) services or processes that are elements of an enterprise contact center application functional component. Each entry identifies a single process that is a necessary element of the functional component. This table also provides a one-to-one mapping of entries to a corresponding entry in IETF standard host and application MIB tables. The HOST-RESOURCES and SYSAPPL MIBs expose tables that provide additional instrumentation for software and applications and for the processes that make up that software or those applications. The HOST-RESOURCES-MIB entries in 'hrSWRunTable' and 'hrSWRunPerfTable' and the SYSAPPL-MIB entries in 'sysApplElmtRunTable' have a one-to-one relationship to entries in the component element table. The entries in these standard MIB tables are solely or partially indexed by the operating system process identifier (ID). The process ID is an integer value that uniquely identifies a single process that is currently running on the host. Entries in the component element table maintain its process ID; this value is used to relate the entry to a corresponding entry in the referenced tables of HOST-RESOURCES-MIB and SYSAPPL-MIB. Entries in these tables of the HOST-RESOURCES and SYSAPPL MIBs expose similar information about each process; in some cases, objects are duplicated. However, while the HOST-RESOURCES-MIB lists processes with no further relationship, the SYSAPPL-MIB relates these same processes to installed software packages and the elements that make up those packages. Entries in the component element table cannot be similarly indexed as the referenced standard MIB tables because, should the process terminate (expectedly or unexpectedly), the entry would need to be removed from the table since its index or process ID is thus unknown. This behavior diminishes the agent's ability to express a component element's current status since the entry no longer exists. However, to relate this table to the referenced standard MIB tables, entries in the component element table maintain the current process ID of the element. This provides the one-to-one relationship that allows the management station to drill down further on each functional component and present instrumentation related to each element of that component from these standard MIB tables. This table has a expansion relationship with the component table; there will be one or many entries in this table that relate to a single entry in the component table. Because the set of elements of a contact center functional component are finite and static, this table is constructed by the SNMP agent at startup; entries cannot be added or deleted at run time. The object values of each element entry may change periodically if the run state of the process changes. The SNMP agent will alter the RunID and Status object values to reflect the correct process ID and run status of that process. All objects in this table are read-only to the management station.