Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"backupRestoreLogURI",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"0",
".",
".",
"254",
")",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"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: <protocol>://<userid:password>@<hostname:port>/<pathname> 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:<protocol>://<hostname>/<pathname>. Note: When using SFTP, only an RSA fingerprint is supported. An example of a qualified location can be: <protocol>://[<user>[:password][;fingerprint=<host>]@]<host> [:<port>]/<path>/<to>/<file> NOTE: This function is available only for SNMPv3.\"",
"::=",
"{",
"backupRestore",
"6",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
0,
254
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"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: <protocol>://<userid:password>@<hostname:port>/<pathname> 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:<protocol>://<hostname>/<pathname>. Note: When using SFTP, only an RSA fingerprint is supported. An example of a qualified location can be: <protocol>://[<user>[:password][;fingerprint=<host>]@]<host> [:<port>]/<path>/<to>/<file> NOTE: This function is available only for SNMPv3."
],
null,
null,
null,
null
]
}