User guide
430
pmp-0229 (Mar 2013)
Managing Module Access by Passwords Securing Your Network
However, if encryption is disabled, AES modules can communicate with DES modules.
Managing Module Access by Passwords
Adding a User for Access to a Module
From the factory, each module has a preconfigured administrator-level account in the name root,
which initially requires no associated password. This is the same root account that you may have
used for access to the module by telnet or ftp. When you upgrade a module
• an account is created in the name admin.
• both admin and root inherit the password that was previously used for access to the
module:
o the Full Access password, if one was set.
o the Display-Only Access password, if one was set and no Full Access password was set.
IMPORTANT!
If you use Prizm, do not delete the root account from any module. If you use an
NMS that communicates with modules through SNMP, do not delete the root
account from any module unless you first can confirm that the NMS does not rely
on the
root
account for access to the modules.
Each module supports four or fewer user accounts, regardless of account levels. The available
levels are
• ADMINISTRATOR, who has full read and write permissions. This is the level of the root
and admin users, as well as any other administrator accounts that one of them creates.
• INSTALLER, who has permissions identical to those of ADMINISTRATOR except that the
installer cannot add or delete users or change the password of any other user.
• GUEST, who has no write permissions and only a limited view of General Status tab, as
shown in Figure 147, and can log in as a user.
From the factory default state, configure passwords for both the root and admin account at the
ADMINISTRATOR permission level, using the Account => Change Users Password tab. (If you
configure only one of these, then the other will still require no password for access into it and thus
remain a security risk.) If you are intent on configuring only one of them, delete the admin
account. The root account is the only account that CNUT uses to update and Prizm uses to
manage the module.