MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 34 (snanauMIB). 4 (appnMIB). 1 (appnObjects). 1 (appnNode). 5 (appnLinkStationInformation). 1 (appnLsTable). 1 (appnLsEntry). 12 (appnLsMigration)
OID : 1.3.6.1.2.1.34.4.1.1.5.1.1.12
TXT : iso. org. dod. internet. mgmt. mib-2. snanauMIB. appnMIB. appnObjects. appnNode. appnLinkStationInformation. appnLsTable. appnLsEntry. appnLsMigration
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.2.1.34.4.1.1.5.1.1.12
Module APPN-MIB (CISCO)
NomappnLsMigration
Accesreadonly
Statuscurrent
DescriptionIndicates whether this link station will be used for connections to down-level or migration partners. In general, migration nodes do not append their CP names on XID3. Such nodes: (1) will not support parallel TGs, (2) should be sent an ACTIVATE PHYSICAL UNIT (ACTPU), provided that the partner supports ACTPUs, and (3) should not be sent segmented BINDs. However, if this node receives an XID3 with an appended CP name, then the partner node will not be treated as a migration node. In the case of DYNAMIC TGs this object should be set to 'no'.
SyntaxeTruthValue (SNMPv2-TC)
Module APPN-MIB (ietf)
NomappnLsMigration
Accesreadonly
Statuscurrent
DescriptionIndicates whether this link station will be used for connections to down-level or migration partners. In general, migration nodes do not append their CP names on XID3. Such nodes: (1) will not support parallel TGs, (2) should be sent an ACTIVATE PHYSICAL UNIT (ACTPU), provided that the partner supports ACTPUs, and (3) should not be sent segmented BINDs. However, if this node receives an XID3 with an appended CP name, then the partner node will not be treated as a migration node. In the case of DYNAMIC TGs this object should be set to 'no'.
SyntaxeTruthValue (SNMPv2-TC)