Contexts, Configuring rbm – Brocade Virtual ADX Administration Guide (Supporting ADX v03.1.00) User Manual
Page 117
Brocade Virtual ADX Administration Guide
105
53-1003249-01
Configuring RBM
3
Contexts
Within a context, a user can be a:
•
Manager
•
Operator
•
Viewer of items and their respective child configuration items
•
None
The child configuration items are:
•
Real name or IP address.
•
Server virtual name or IP address.
•
CSW rule
•
CSW Policy
•
Health check
•
Server port policy
Contexts have the following properties:
•
All contexts have unique names.
•
A maximum of 256 contexts are supported.
•
For backward compatibility, the context-oriented configurations that are not assigned to a
context belong to a built-in default context.
•
A context cannot be deleted if it is referenced.
•
A resource in a context cannot be bound to a resource in a different context. For example, a
virtual server in context C1 cannot be bound to a real server in context C2.
•
A resource in a context cannot be deleted if the user is in a different context at the time.
•
One default context can be configured for a user, if the user has privileges for more than one
context.
A default context can be associated with a template. If a default context is configured at both
template and user level, the user level configuration takes precedence. If a user is not associated
with any templates or roles, he has no privileges. The super user can create a default template with
a set of privileges, which is assigned to anyone who does not have templates or privileges.
Upon login, the user is automatically associated with the configured context if only one context has
been configured. The user is associated with the default context-if there is more than one context
and a default context is also configured.
Configuring RBM
The tasks to configure RBM are as follows:
•
•
•
•