MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 351 (stratacom). 110 (basis). 5 (basisServices). 5 (voice). 5 (vismXgcpExtensionGrp). 1 (vismXgcpCoreObjects). 3 (vismXgcpPeerTable). 1 (vismXgcpPeerEntry)
OID : 1.3.6.1.4.1.351.110.5.5.5.1.3.1
TXT : iso. org. dod. internet. private. enterprises. stratacom. basis. basisServices. voice. vismXgcpExtensionGrp. vismXgcpCoreObjects. vismXgcpPeerTable. vismXgcpPeerEntry
Enfants
Détails
OID1.3.6.1.4.1.351.110.5.5.5.1.3.1
Module CISCO-VISM-XGCP-EXT (CISCO)
NomvismXgcpPeerEntry
Statuscurrent
DescriptionEach row is identified by XGCP peer name and peer XGCP protocol number combination. This means, if an MGC uses more than one variant of XGCP (i.e MGCP, SGCP 1.0, SGCP 1.1 etc), an entry will be maintained for each of the protocols. mgcNumber and mgcProtocolNumber from MGMIB are used as foreign index to this table. Entries in this table are implicitly created by the agent. An entry shall be created when an entry is created in the mgcProtocolTable and when mgcProtocolNumber refers to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as supported protocol. An entry shall be deleted if the corresponding entry in the mgcProtocolTable is deleted. As both mgcProtocolTable and vismXgcpPeerTable have mgcNumber and mgcProtocolNumber as index, referential integrity between the two tables is automatically ensured.