7. Administration (continued)
7.3.4ANMS (continued)
5.Select the Attribute Editor tab of the screen that appears. Select
6.Replace the value shown with the desired KVM permission attribute value. (See table below for details.)
Permission Attribute Value
The Permission Attribute Value is made up of two parts; the IP address of the KVM switch that the user will be accessing and a string of characters that indicates the access rights the user has. The following rules apply to the makeup of the permission attribute value entry:
•An ampersand (&) connects the KVM represented by the IP address to the access rights represented by the string of characters.
•The characters of the access rights string can be entered in either upper or lower case. The available characters and what access rights they represent are listed in the following table.
•Each character in the access rights string is separated by a comma
(,). There are no spaces before or after the comma.
•If a user has access rights to more than one KVM, each permission segment is separated by a semicolon (;). There are no spaces before or after the semicolon.
Character | Description |
|
|
C | Gives the corresponding account administrator privileges. |
WGives the corresponding account access to the KVM switch via the Windows browser and
JGives the corresponding account access to the KVM switch via the Java browser and
LGives the corresponding account access to the log server on the Web Management Interface.
VGives the corresponding account
PN/xxxx | Denies the corresponding account access to a port. |
|
|
SN/xx | Denies the corresponding account access to a station. |
|
|
PV/xxxx | Gives the corresponding account |
| port. |
|
|
SV/xx | Gives the corresponding account |
| station. |
|
|
PF/xxxx | Gives the corresponding account full access to a port. |
|
|
SF/xx | Gives the corresponding account full access to a station. |
LDAP Server access rights examples are given in the following table:
Access Rights | Description |
|
|
10.0.0.168&c | The corresponding account has administrator |
| access to the KVM assigned to IP address |
| 10.0.0.168. The account does not have access |
| to any other KVMs administered by the LDAP/S |
| server. |
|
|
10.0.0.164&c; | The corresponding account has administrator |
10.0.0.166&w,j | access to the KVM assigned to IP address |
| 10.0.0.164. The corresponding account can |
| access the KVM assigned to IP address |
| 10.0.0.166 via the Windows and Java |
| browser and |
| corresponding account does not have access |
| to any other KVMs administered by the LDAP/S |
| server. |
|
|
v,l;10.0.0.164&j | The corresponding account has |
| and log server access rights on all KVMs |
| administered by the LDAP/S server. The |
| corresponding account can access the KVM |
| assigned to IP address 10.0.0.164 via the Java |
| browser and |
|
|
10.0.0.168&PN/0102 | The corresponding account is denied access to |
| port 2 on station 1 of the KVM chain assigned |
| to IP address 10.0.0.168. The corresponding |
| account does not have access to any other |
| KVMs administered by the LDAP/S server. |
|
|
10.0.0.168&PF/A | The corresponding account is given full access |
| to all ports on the KVM assigned to IP address |
| 10.0.0.168. The corresponding account |
| does not have access to any other KVMs |
| administered by the LDAP/S server. |
|
|
10.0.0.168&SV/02 | The corresponding account is given |
| access to station 2 of the KVM chain assigned |
| to IP address 10.0.0.168. The corresponding |
| account does not have access to any other |
| KVMs administered by the LDAP/S server. |
|
|
48