Users Guide

Device Prerequisites | Troubleshooting
OMNM 6.5.3 User Guide 731
Device Prerequisites
Often, devices require pre-configuration before they are manage-able by this software. For example,
the management system application server must have access to the device, and often must be listed
on the access control list for the managed device.
Common Device Prerequisites
The following are common prerequisites:
Credentials —WBEM credentials have a role in discovering the device. Your system must have
access to the computer using Administrative only credentials. These are the same credentials
as the user installing WBEM on the device.
Telnet/SSH credentials are necessary for other supported applications.
For full functionality, this WBEM device driver requires administrative (root) access. Many
devices may only allow root logins on a local console.
In such cases, configure the Telnet/SSH authentication for these devices to login as a non-root
user—and, in Authentication Manager, enter
su in the Enable User ID field and enter the
root user’s password in
Enable User Password in that same authentication. This enables full
device management functionality with root access.
NOTE:
Credentials for Telnet/SSH should have a privilege level sufficient to stop services and to restart the
computer system.
Firewall — Some firewalls installed on the computer may block Web-Based Enterprise
Management requests. Allow those you want to manage.
License —Make sure you have the correct WBEM driver license installed. Licenses come in the
following types:
• Major Vendor by Name - Such as Dell, Compaq, HP, Gateway.
• Server/Desktop individual license support.
• Generic computers - non-major vendors.
• ALL - this gives the driver all capabilities for any computer system.
Aruba Devices
By default, only SSH interactions work on these devices. If you want to use telnet you have to
configure the device through the console or through an SSH session and turn it on.
Cut through or direct access sessions are only supported for SSHv2. You must create an SSHv2
management interface for the device and use it when attempting direct access. If you use SSHv1
the session does not connect (the ArubaOS does not support SSHv1), and if you select telnet, the
driver cannot log into the device automatically, and must login manually.