ENTERASYS-CONFIGURATION-MANAGEMENT-MIB :: etsysConfigMgmtChangeSupportedURLs

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › ENTERASYS-CONFIGURATION-MANAGEMENT-MIB › etsysConfigMgmtChangeSupportedURLs

etsysConfigMgmtChangeSupportedURLs

Module: ENTERASYS-CONFIGURATION-MANAGEMENT-MIB

OID (symbolic): ENTERASYS-CONFIGURATION-MANAGEMENT-MIB::etsysConfigMgmtChangeSupportedURLs

OID (numeric): 1.3.6.1.4.1.5624.1.2.16.2.4

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: The URLs that this entity supports for transferring files. These define the transfer protocols and remote file names. etsysConfigMgmtFtp - As per rfc1738 ftp://:@:/ url-path: //...//;type= user defaults to anonymous, password to snmp@, port to 21, and type to ASCII. binary and image are both valid types which have the same meaning. domain-name would be the IP address or domain name of the managed entity. etsysConfigMgmtRcp - rcp://@:///...// port defaults to 514. etsysConfigMgmtHttp - As per rfc1738 http://:/? port defaults to 80. etsysConfigMgmtTftp - tftp://:///...// port defaults to 69. etsysConfigMgmtFile - As per rfc1738 file:/// host can only be specified as localhost or the empty string. This will only be used to specify a file on the managed entity. This indicates that the managed entity supports some form of a user file system. etsysConfigMgmtBootP - bootp:// host specifies the default gateway, or bootp server that the bootp request should be directed to. etsysConfigMgmtScp - scp://:@:///...// host as defined in RFC1738. port defaults to 22.

What is etsysConfigMgmtChangeSupportedURLs?

This read-only BITS value enumerates which file-transfer URL schemes (FTP, RCP, HTTP, TFTP, local file, BootP, and SCP) this entity supports for configuration and image transfers, each with its own URL syntax as defined in the description. Admins check this before scripting a configuration push or image upgrade so they choose a URL scheme the device actually understands. For example, if the scp bit is set but ftp is not, an admin would build change requests using scp://user:pass@host:22/path rather than an ftp:// URL that the device would reject.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.16.2.4
snmpwalk -v2c -c public <target> ENTERASYS-CONFIGURATION-MANAGEMENT-MIB::etsysConfigMgmtChangeSupportedURLs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.16.2.4.1
snmpget -v2c -c public <target> ENTERASYS-CONFIGURATION-MANAGEMENT-MIB::etsysConfigMgmtChangeSupportedURLs.1

Start monitoring Enterasys Networks switch (legacy, later Extreme Networks)/router (firmware/config file management) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ENTERASYS-CONFIGURATION-MANAGEMENT-MIB::etsysConfigMgmtChangeSupportedURLs OID value, configure state conditions and alerts, and monitor any Enterasys Networks switch (legacy, later Extreme Networks)/router (firmware/config file management) 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.5624enterasysENTERASYS-MIB-NAMES
1.3.6.1.4.1.5624.1etsysMibsENTERASYS-MIB-NAMES
1.3.6.1.4.1.5624.1.2etsysModulesENTERASYS-MIB-NAMES
Numeric OIDNameModule
1.3.6.1.4.1.5624.1.2.16etsysConfigurationManagementMIBENTERASYS-CONFIGURATION-MANAGEMENT-MIB
1.3.6.1.4.1.5624.1.2.16.2etsysConfigMgmtChangeENTERASYS-CONFIGURATION-MANAGEMENT-MIB
1.3.6.1.4.1.5624.1.2.16.2.4etsysConfigMgmtChangeSupportedURLsENTERASYS-CONFIGURATION-MANAGEMENT-MIB

Module

This MIB depends on