CME-MIB :: backupRestoreLogURI

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCME-MIBbackupRestoreLogURI

backupRestoreLogURI

Module: CME-MIB

OID (symbolic): CME-MIB::backupRestoreLogURI

OID (numeric): 1.3.6.1.4.1.2.3.51.2.22.42.6

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-write

Description: Indicates the URI address where the log file will be put. It will be used only if the backupRestoreLogPush will be set on push. 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 will reside, 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/restore.log 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/restore.log. 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 available only for SNMPv3.

What is backupRestoreLogURI?

This object holds the fully qualified remote location where a restore operation's log file will be uploaded, used only when backupRestoreLogPush is set to push. An admin who wants a record of how a restore operation went, without restarting the CMM to view it locally, configures this URI ahead of time so the log lands on a server they control. For example, an admin performing a remote-hands restore would set this object before the operation so they can retrieve the log afterward without console access.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.42.6
snmpwalk -v2c -c public <target> CME-MIB::backupRestoreLogURI

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.42.6.1
snmpget -v2c -c public <target> CME-MIB::backupRestoreLogURI.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.2.3.51.2.22.42.6.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::backupRestoreLogURI 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.6backupRestoreLogURICME-MIB