CME-MIB :: backupRestoreURI

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCME-MIBbackupRestoreURI

backupRestoreURI

Module: CME-MIB

OID (symbolic): CME-MIB::backupRestoreURI

OID (numeric): 1.3.6.1.4.1.2.3.51.2.22.42.4

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-write

Description: Contains the fully qualified remote location of the file. A fully qualified remote location contains a supported protocol followed by a colon and two slashes (//), userid and password separated by a colon for login authentication, an @ sign, followed by the hostname or IP address of the server where the packet file resides, followed by an optional port number to the hostname, and the full pathname to the file. Note that if the port number is specified, it must be separated with the hostname (or IP address) by a colon. The MM currently supports the following protocols: TFTP, FTP, HTTP and HTTPS. The complete format of a fully qualified remote location is: ://@/ An example of a fully qualified remote location can be: ftp://USERID:PASSW0RD@192.168.0.2:30045/tmp/cmd.bkp where the ftp protocol will be used for transferring the file in this location, username is USERID, password is PASSW0RD, host IP address is 192.168.0.2, port number is 30045, and the full pathname for the packet file is /tmp/cmd.bkp. Some protocols do not need the username, password, and the port number, so the minimum requirement for a fully qualified location can be::///. Note:When using SFTP, only an RSA fingerprint is supported. An example of a qualified location can be: ://[[:password][;fingerprint=]@] [:]/// NOTE: This function is only available for SNMPv3.

What is backupRestoreURI?

This object holds the fully qualified remote location, including protocol, credentials, host, optional port, and pathname, where a backup or restore file is read from or written to. An admin configuring an automated configuration-backup job sets this object to point at the correct FTP, TFTP, or similar server location before triggering backupRestoreAction. For example, an admin would set this to an sftp URI including a username and password before initiating a backup so the CMM knows exactly where to send the file.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.42.4
snmpwalk -v2c -c public <target> CME-MIB::backupRestoreURI

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.42.4.1
snmpget -v2c -c public <target> CME-MIB::backupRestoreURI.1

Set instance 1 (SNMPv2c):

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

Start monitoring Cisco Communications Manager Express (CME) router/gateway with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CME-MIB::backupRestoreURI OID value, configure state conditions and alerts, and monitor any Cisco Communications Manager Express (CME) router/gateway 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2ibmBLADE-MIB
1.3.6.1.4.1.2.3ibmAgentsBLADE-MIB
1.3.6.1.4.1.2.3.51netfinitySupportProcessorAgentBLADE-MIB
1.3.6.1.4.1.2.3.51.2bladeCenterSnmpMIBBLADE-MIB
1.3.6.1.4.1.2.3.51.2.22bladeCenterBLADE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2.3.51.2.22.42backupRestoreCME-MIB
1.3.6.1.4.1.2.3.51.2.22.42.4backupRestoreURICME-MIB