HH3C-SNA-DLSW-EXT-MIB :: hh3cdeNodeConfigSapList

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HH3C-SNA-DLSW-EXT-MIB › hh3cdeNodeConfigSapList

hh3cdeNodeConfigSapList

Module: HH3C-SNA-DLSW-EXT-MIB

OID (symbolic): HH3C-SNA-DLSW-EXT-MIB::hh3cdeNodeConfigSapList

OID (numeric): 1.3.6.1.4.1.25506.2.62.1.1.15

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-write

Description: The SAP list indicates which SAPs are allowed. 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 hh3cdeIfSapList 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. When to start the run-time capabilities exchange is implementation-specific.

The DEFVAL below indicates support for SAPs 0, 2, 4, 6, 8, A, C and E.

What is hh3cdeNodeConfigSapList?

This read-write 16-byte OCTET STRING is a bitmap of which even-numbered SAPs (0 through 254) this device permits for data link switching, with a 1 bit meaning that SAP is allowed; the default enables SAPs 0, 2, 4, 6, 8, A, C, and E. An admin edits this bitmap to restrict certain remote partners from seeing all locally supported SAPs, for example running NetBIOS with some peers but not others.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.25506.2.62.1.1.15
snmpwalk -v2c -c public <target> HH3C-SNA-DLSW-EXT-MIB::hh3cdeNodeConfigSapList

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.25506.2.62.1.1.15.1
snmpget -v2c -c public <target> HH3C-SNA-DLSW-EXT-MIB::hh3cdeNodeConfigSapList.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.25506.2.62.1.1.15.1 s <value>

Start monitoring H3C router providing SNA/DLSw over IP (extended config) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HH3C-SNA-DLSW-EXT-MIB::hh3cdeNodeConfigSapList OID value, configure state conditions and alerts, and monitor any H3C router providing SNA/DLSw over IP (extended config) from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.25506hh3cHH3C-OID-MIB
1.3.6.1.4.1.25506.2hh3cCommonHH3C-OID-MIB
1.3.6.1.4.1.25506.2.62hh3cDlswExtHH3C-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.25506.2.62.1hh3cDlswExtMIBObjectsHH3C-SNA-DLSW-EXT-MIB
1.3.6.1.4.1.25506.2.62.1.1hh3cdeNodeHH3C-SNA-DLSW-EXT-MIB
1.3.6.1.4.1.25506.2.62.1.1.15hh3cdeNodeConfigSapListHH3C-SNA-DLSW-EXT-MIB