Hp Session Allocation Manager (Sam); Hp Sam Minimum Network Requirements - HP Bc1500 - BladeSystem - Blade PC Supplementary Manual

Registering the configuration file with HP SIM:
1. Execute the command: mxmib -a RADLAN-MIB.cfg
2. To verify RADLAN-MIB mib was loaded, execute the command: mxmib -l
3. To verify that the SNMP traps are available and enabled in HP SIM:
In HP SIM, select Options > Events > SNMP Trap Settings.
•
• Verify that the newly registered MIB file RADLAN-MIB.mib is in the Mib Name box.
NOTE: By default, the traps in this MIB may not be enabled for trap handling and severity because the
level is not configured. Review each trap and configure Enable Trap Handling and Severity based on
business requirements.

HP Session Allocation Manager (SAM)

The HP PC Session Allocation Manager (SAM) manages allocation of the RDP connection from a user's
access device to the blade PC. Upon receipt of the user request for a blade PC, HP SAM checks for an
active or disconnected blade PC session allocated for that user. If one active session exists, the user is
reallocated that blade PC. Users without active blade PC sessions are allocated to an available blade PC.
To provide redundancy for the blade PC allocation function, HP SAM is installed on multiple servers that
share one central SQL database. Each of the HP SAM servers can manage and allocate shared blade
PCs. Once the HP SAM clients are configured to utilize the redundant HP SAM servers in the unlikely
event of an error condition causing the HP SAM server to not respond, the HP SAM client automatically
attempts to communicate with the next HP SAM server for the blade PC allocation (if configured to do so).

HP SAM minimum network requirements

•
A simplified CCI deployment, the HP SAM server requires only one network connection.
•
Network connectivity must exist between the HP SAM server and Active Directory server, SQL Server
database, blade PC, and Remote Access device.
20