SERVICE-LOCATION-PROTOCOL-MIB :: slpAgentMessageTypesSupported

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SERVICE-LOCATION-PROTOCOL-MIB › slpAgentMessageTypesSupported

slpAgentMessageTypesSupported

Module: SERVICE-LOCATION-PROTOCOL-MIB

OID (symbolic): SERVICE-LOCATION-PROTOCOL-MIB::slpAgentMessageTypesSupported

OID (numeric): 1.3.6.1.2.1.999.1.1.1.1.8

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: The SLP message types supported by this SLP agent, expressed as an array of binary Function-ID values (RFC 2608). For example '0102'H means 'SrvRqst, SrvRply'.

See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608).

What is slpAgentMessageTypesSupported?

This object is an array of binary Function-ID values, up to 64 bytes, listing which SLP message types this agent supports. An admin or management tool decodes this to confirm the agent implements the required message set for basic service discovery before depending on it. For example, the octet string '0102'H indicates the agent handles both SrvRqst and SrvRply messages.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.999.1.1.1.1.8
snmpwalk -v2c -c public <target> SERVICE-LOCATION-PROTOCOL-MIB::slpAgentMessageTypesSupported

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.999.1.1.1.1.8.1
snmpget -v2c -c public <target> SERVICE-LOCATION-PROTOCOL-MIB::slpAgentMessageTypesSupported.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> slpAgentMessageTypesSupported.1

Start monitoring systems running an SLP (Service Location Protocol) implementation (directory/service/user agent status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SERVICE-LOCATION-PROTOCOL-MIB::slpAgentMessageTypesSupported OID value, configure state conditions and alerts, and monitor any systems running an SLP (Service Location Protocol) implementation (directory/service/user agent status) from a single console.

OID Breakdown

Upper-level ancestors (11 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.999bfdMIBBFD-DRAFT-00-MIB
1.3.6.1.2.1.999.1bfdObjectsBFD-DRAFT-00-MIB
1.3.6.1.2.1.999.1.1bfdScalarObjectsBFD-DRAFT-00-MIB
1.3.6.1.2.1.999.1.1.1bfdAdminStatusBFD-DRAFT-00-MIB
1.3.6.1.2.1.999.1.1.1.1ipfixCollectorTableIPFIX-EXPORTER-MIB
Numeric OIDNameModule
1.3.6.1.2.1.999.1.1.1.1.8slpAgentMessageTypesSupportedSERVICE-LOCATION-PROTOCOL-MIB