Ridgeline Reports; Role-Based Access Management; Distributed Server Mode - Extreme Networks Ridgeline Guide Manual

Ridgeline Reports

Ridgeline Reports are HTML pages that can be accessed separately from the main Ridgeline user
interface, without logging on to Ridgeline. Ridgeline reports do not require Java, so reports can be
loaded quickly, even over a dial-up connection, and can be viewed on systems that cannot run the
Ridgeline client. Reports can be printed using your browser's Print function.
The Reports capability provides a large number of predefined HTML reports that present a variety of
types of information from the Ridgeline database. You can also create your own reports by writing Tcl
scripts. Further, within the Reports Module are several useful tools such as a MIB Browser and other
tools that can provide Ridgeline system information.
Reports can also be accessed from within Ridgeline. A Summary report is displayed on the Ridgeline
Home page, which provides basic information on the status of Ridgeline devices and alarms. From this
report you can access other more detailed reports.

Role-based Access Management

All Ridgeline users must log on with a user name and password in order to access Ridgeline features.
Ridgeline initially provides four user roles:
Monitor role: users who can view status information only.
●
Manager role: users who can modify device parameters as well as view status information.
●
Administrator role: users who can create, modify and delete Ridgeline user accounts as well as
●
perform all the functions of a user with Manager access.
Disabled role: users whose account information is maintained, but who have no access to any
●
features of the product.
An Administrator user can create additional roles, can modify the capabilities available under each role,
and can add and delete Ridgeline users, as well as enable or disable access for individual users.
By default, Ridgeline provides its own authentication and authorization for Ridgeline users. However,
through Ridgeline Administration, Ridgeline can be configured to act as a Remote Authentication Dial
In User Service (RADIUS) client, allowing it to use an external RADIUS server to authenticate Ridgeline
users. As an option, the external RADIUS server can be configured to return user role information as
well as the user authentication.
As an alternative, Ridgeline can be configured to act as a RADIUS server, providing authentication for
Ridgeline users as well as for other devices such as Extreme switches. However, the RADIUS server
built into Ridgeline should only be used for demonstration or testing purposes, and should not be used
to provide primary authentication services in a production environment. The Ridgeline RADIUS server
is not sufficiently robust to perform as the authentication server in a production environment.

Distributed Server Mode

To manage very large numbers of network devices, or devices that are geographically distributed, the
management task can be divided up between multiple Ridgeline servers. Each server in the server
group is updated at regular intervals with network summary and status information from the other
servers in the group. From the Ridgeline home page, a client attached to any one of the servers in the
server group can view summary status information from the other servers in the group in addition to
the standard Network Summary report. The Ridgeline client also lets the user easily navigate between
the different servers in the group to see detailed management information about the devices managed
by those servers.
Ridgeline Concepts and Solutions Guide
1
19