Configuration and management
152
4.8
Managing administrators rights
BAT54-Rail/F..
Release
7.54
06/08
U Access with TFTP
In TFTP, the user name and password are coded in the source (TFTP read
request) or target file names (TFTP write request). The file name is either
made up of the master password and the command to be executed, or of the
combined user name and password separated by a colon, plus with the com-
mand as a suffix. Thus a command sent by TFTP resembles the following:
D <Master password><Command> or
D <Username>:<Password>@<Command>
Examples (the BAT has the address mybat.intern, the master password is
'RootPwd' and a user has been set up named 'LocalAdmin' with the pass-
word 'Admin'):
D Read the configuration from the device (supervisor only)
tftp mybat.intern GET RootPwdreadconfig mybat.lcf
D Write the configuration to the device (supervisor only)
tftp mybat.intern PUT mybat.lcf RootPwdwriteconfig
D Read out the device MIB (for the local administrator)
tftp mybat.intern GET localadmin:Adminreadmib
mybat.lcf mybat.mib
For the menus and available commands, the same limitations on rights apply
as with Telnet.
U Access with SNMP management systems
For the administration of networks with the help of SNMP tools such as HP
OpenView, the various levels of administrator access can be used for the
precise control of rights.
Under SNMP, user name and password are coded in the "community". Here,
the 'public' community can be selected or one of either the master password
or a combination of user name and password divided by a colon can be se-
lected.
Note: The community 'public' corresponds with the rights of a local adminis-
trator with read-only access, as long as the SNMP read access without
password is enabled (’Password protection for SNMP read-only access.’
→ page 175). If this access is not allowed, then the 'public' community will
have access to no menus at all.
Otherwise, the same limitations on rights apply for the menus as with Telnet.
To Next Page
Loading...
