MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 10 (ciscoExperiment). 9 (ciscoDlswMIB). 1 (ciscoDlswMIBObjects). 2 (ciscoDlswTConn). 2 (ciscoDlswTConnConfigTable). 1 (ciscoDlswTConnConfigEntry). 9 (ciscoDlswTConnConfigSapList)
OID : 1.3.6.1.4.1.9.10.9.1.2.2.1.9
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoExperiment. ciscoDlswMIB. ciscoDlswMIBObjects. ciscoDlswTConn. ciscoDlswTConnConfigTable. ciscoDlswTConnConfigEntry. ciscoDlswTConnConfigSapList
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.4.1.9.10.9.1.2.2.1.9
Module CISCO-DLSW-MIB (CISCO)
NomciscoDlswTConnConfigSapList
Accesreadonly
Statuscurrent
Description The SAP list indicates which SAPs are advertised to the transport connection defined by the local peer whose transport address is given by ciscoDlswTConnConfigLocalTAddr. The SAP list is configured on the local peer, and the SAP list is sent to other peers via capabilities exchange. The SAP list represents the SAPs specified via the configuration command: dlsw icanreach saps X or dlsw icannotreach saps X Where X is in the range 0-FE. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in ciscoDlswIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. It is up to the implementation exactly when to start the run-time capabilities exchange. The DEFVAL below indicates support for all SAPs.
SyntaxeOctetString (16...16)