LUM-SYSTEM-MIB :: sysSecurityFileSystemAccessRestrictions

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LUM-SYSTEM-MIB › sysSecurityFileSystemAccessRestrictions

sysSecurityFileSystemAccessRestrictions

Module: LUM-SYSTEM-MIB

OID (symbolic): LUM-SYSTEM-MIB::sysSecurityFileSystemAccessRestrictions

OID (numeric): 1.3.6.1.4.1.8708.2.2.2.11.7

Node type: OBJECT-TYPE

Type: EnableDisable

Access: read-only

Description: Access rights to the file system of the node element. When 'restricted', restrictions to the file system are activated, these restrictions depends on the user authority profile.

disabled - Default access rights: 1. Administrators (including root) and operators can execute CLI commands bash and telnet. 2. All users have full file system access using SFTP or FTP (if enabled).

enabled - Restricted access rights to the file system. The following restrictions are applied: 1. Only administrator users (including root) can execute CLI commands bash and telnet. 2. When using SFTP: Readonly and operator users can only access /tftpboot/ and its subdirectories. Administrator users (including root) have full file system access. 3. When using FTP (if enabled): Readonly, operator and all administrator users except root can only access /tftpboot/ and its subdirectories. The root user have full file system access.

When changed, the updated restrictions will be used at following FTP/SFTP sessions. On CU-SFP/III, active FTP sessions will be aborted at the point when file system access is changed.

Only administrator can change the file system access restriction settings.

What is sysSecurityFileSystemAccessRestrictions?

Toggles restricted file-system access mode: when disabled, administrators and operators get CLI shell/telnet access and all users get full SFTP/FTP file access, but when enabled, only administrators can use CLI shell/telnet and non-admin users are confined to /tftpboot and its subdirectories over SFTP/FTP; changes take effect on the next FTP/SFTP session, and only an administrator can change this setting.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.8708.2.2.2.11.7
snmpwalk -v2c -c public <target> LUM-SYSTEM-MIB::sysSecurityFileSystemAccessRestrictions

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.8708.2.2.2.11.7.1
snmpget -v2c -c public <target> LUM-SYSTEM-MIB::sysSecurityFileSystemAccessRestrictions.1

Start monitoring Infinera optical transport network nodes with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LUM-SYSTEM-MIB::sysSecurityFileSystemAccessRestrictions OID value, configure state conditions and alerts, and monitor any Infinera optical transport network nodes 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.8708lumentisLUM-REG
1.3.6.1.4.1.8708.2lumGenericLUM-REG
1.3.6.1.4.1.8708.2.2lumSystemMIBLUM-REG
Numeric OIDNameModule
1.3.6.1.4.1.8708.2.2.2lumSystemMIBObjectsLUM-SYSTEM-MIB
1.3.6.1.4.1.8708.2.2.2.11sysSecurityLUM-SYSTEM-MIB
1.3.6.1.4.1.8708.2.2.2.11.7sysSecurityFileSystemAccessRestrictionsLUM-SYSTEM-MIB