Example 2:
Define an access type with the name ―user‖, with read-only maximum access, and with restriction to the
10.10.20.0 sub-net for the SNMP request source.
# device snmp community user ro 10.10.20.0 255.255.255.0
# device snmp show
SNMP management access:
-----------------------
Community String Access IpAddress Subnet
normal-user Read only 10.10.20.0 255.255.255.0
public Read/Write 0.0.0.0 0.0.0.0
Example 3:
Remove the access type with the name ―user‖.
# device snmp delcommunity user
# device snmp show
SNMP management access:
-----------------------
Community String Access IpAddress Subnet
public Read/Write 0.0.0.0 0.0.0.0
Example 4:
Only allow SNMP access from subnet 10.10.10.0/255.255.255.0 via the satellite interface.
# device manager add snmp 3 10.10.10.0 255.255.255.0
# device manager show
Management access:
------------------
Access Interface IpAddress Subnet
SNMP 3 10.10.10.0 255.255.255.0
E.5 Setting a MIB Object and Saving the Configuration
When the VSAT is shipped from the factory, the essential MIB objects of the VSAT MIB are given
default values.
When changing the value of a MIB object with write access, the new value will generally be activated
when they are set. The value will apply as long as the VSAT is powered on. If no special action is taken
to save the new MIB value, the value will revert to the default value upon power-on.
To save a new value so that it will survive a VSAT power off/on, one must explicitly issue a MIB save
command by setting the MIB object sysCmdSaveConfig to 1.
To Next Page
Loading...