Avocent MergePoint SP5340 Installer/user Manual

MERGEPOINT® SP MANAGER
Installer/User Guide
European Union Notification
WARNING: This is a class A product. In a domestic environment this product may cause
radio interference in which case the user may be required to take adequate measures.
USA Notification
responsible for compliance could void the user’s authority to operate the equipment.
NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his/her own expense.
Canadian Notification
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
Japanese Notification
Korean Notification
MergePoint® SP Manager
Installer/User Guide
Avocent, the Avocent logo, The Power of Being There, DSView and MergePoint are registered trademarks of Avocent Corporation or its affiliates in the U.S. and other countries. All other mar ks are the property of their respective owners.
© 2010 Avocent Corporation. 590-989-501C
Instructions
This symbol is intended to alert the user to the presence of important operating and
maintenance (servicing) instructions in the literature accompanying the appliance.
Dangerous Voltage
This symbol is intended to alert the user to the presence of uninsulated dangerous
voltage within the product’s enclosure that may be of sufficient magnitude to constitute
a risk of electric shock to persons.
Power On
This symbol indicates the principal on/off switch is in the on position.
Power Off
This symbol indicates the principal on/off switch is in the off position.
Protective Grounding Terminal
This symbol indicates a terminal which must be connected to earth ground prior to
making any other connections to the equipment.
T A B L E  O F  C O N T E N T S
Product Overview 1
Features and Benefits 1
Supported SPs 2
MergePoint SP5x00 Manager Configuration 3
LEDs on the MergePoint SP5x00 manager 4
MergePoint SP5x24/SP5x40 Manager Configuration 5
Safety Precautions 6
Rack mount safety considerations 8
Cabling installation, maintenance and safety tips 8
Installation and Setup 11
Configuring Power for the MergePoint SP manager 11
Connecting to the Network 13
Configuring the MergePoint SP Manager Basic Settings 13
Activating the MergePoint SP5x00 Manager License 15
Adding the MergePoint SP Manager to a DSView 3 SoftwareInstallation 16
MergePoint SP Manager Configuration Wizard 16
Saving the wizard settings in a config file 17
Modifying the config file settings (Admin users only) 17
Configuring the MergePoint SP Manager Network Settings 19
Ethernet ports on the MergePoint SP5x00 manager 19
Ethernet ports on the MergePoint SP5x24/SP5x40 manager 20
Configuring MergePoint SP5x00 manager network settings 21
Configuring MergePoint SP5x24/SP5x40 manager network settings 22
Private Subnets on the MergePoint SP5x24/SP5x40 Manager 24
Firewall/Packet Filtering 25
Chains 25
Rules 25
BMC Provisioning (IPMI Targets Only) 26
Starting or stopping the BMC provisioning service (Admin users only) 27
Configuring PXE parameters for IPMI BMC provisioning (Admin users only) 27
iii
BMC log 29
Managing MergePoint SP Manager User Accounts 29
DHCP on the MergePoint SP Manager 32
Service Processor Licenses 33
Automatically Manage SPs 34
Discovering and Adding SPs (Admin Users Only) 34
Manually Adding a Single SP 36
Adding blade chassis and blades 37
Managed and Unmanaged SP Lists (Admin users only) 38
Managing SP Groups (Admin users only) 40
Managing SP Profiles (Admin users only) 41
Managing Default Users (Admin users only) 43
Managing user accounts on SPs 45
Configuring the MergePoint SP Manager System Settings (Admin Users Only) 46
Completing the MergePoint SP Manager Installation 48
Operations 49
Using the MergePoint SP Manager 49
MergePoint SP manager web interface 49
Remote Power and Chassis Management 51
Performing SP Group Operations 53
Monitoring and Management 55
Viewing sensor status 55
Viewing SEL events 55
Viewing IML events 56
Viewing the accounting log 56
Import/export data 57
Accessing FRU information 57
Using the Alerts Viewer 58
Syslog 60
Configuring PET alerts 62
iv MergePoint® SP Manager Installer/User Guide
Schedules 62
Schedule a task (Admin users only) 62
SNMP Access 63
Configuring SNMP on the MergePoint SPmanager 64
Configuring SNMP on the service processor 66
SP Operations 68
Viewing SP information 69
Synchronizing blades for a blade chassis 69
Changing the SoL port number 69
Changing the access account of an SP 70
Changing SP parameters 70
Accessing system information 71
Recovering provisioning 71
Changing LAN parameters 72
Host table 72
Static routes 73
Configuring SoL parameters 74
NFS 74
Remote Control 75
Diagnostics 75
Appliance Operations 76
MergePoint SP manager sessions 76
Firmware version and upgrade 76
Boot configuration for the MergePoint SP5x24/SP5x40 manager 77
Unbinding the MergePoint SP manager from the DSView 3 server 78
SP Sessions and Connections 79
System Sessions 79
Active sessions 80
SoL Sessions 81
SP Console Sessions 82
Table of Contents v
Telnet Sessions 82
SSH Sessions 83
Choosing DirectCommand Sessions or Native IP Connections 83
DirectCommand Sessions 86
Native IP Connections 89
Native IP operations using the web interface 90
Native IP operations using SSH Commands 92
Configuring External Authentication Services 95
Configuring a Kerberos Authentication Server 96
Configuring an LDAP Authentication Server 97
Configuring an NIS Authentication Server 98
Configuring a RADIUS Authentication Server 98
Configuring an SMB Authentication Server 99
Configuring a TACACS+ Authentication Server 100
Configuring an Authentication Method for the MergePoint SP Manager 100
Administration Tasks Not Performed in the Web Interface 103
Using MindTerm to Create an SSH Tunnel 103
Using SSH with the MergePoint SP Manager 104
The SSH command line format 104
User shell 105
MgpShell 106
SSH Passthrough 106
SSH Passthrough commands 106
Telnet 108
Displaying the MergePoint SP Manager Firmware Version 108
Configuring the Users’ Console Login Menu 108
Configuring Routes With CLI 110
Backing Up Configuration Files 111
Restoring backed up configuration files 111
Restoring factory default configuration files 112
vi MergePoint® SP Manager Installer/User Guide
Shutting down the MergePoint SP Manager 112
Configuring Groups for Use with Authentication Servers 112
Configuring group authorization for LDAP authentication 113
Configuring group authorizations on an AD server 113
Defining groups on an LDAP server running OpenLDAP 115
Configuring group authorization for RADIUS authentication 116
Configuring group authorization for TACACS+ authentication 118
Using the CLI Utility 121
CLI Utility Overview 121
Execution Modes 121
Command line mode 121
Interactive mode 122
Batch mode 122
CLI Options 122
CLI Parameters and Arguments 123
Entering a command in interactive mode 124
Entering a command in command code 124
Entering a command in batch mode 124
Autocompletion 125
CLI Commands 126
add 126
cd 131
commit 132
delete 132
get | show 132
list 133
quit | exit 134
quit! 134
rename 134
set 135
Table of Contents vii
shell 135
revert 136
version 136
Summary of How to Configure the Top Level Parameters 136
Using SMASH Command Line Protocol 149
SMASH CLP Overview 150
SMASH CLP implementation 150
Supported profiles 151
Terms 152
General command syntax 153
Targets 154
Starting a SMASHCLP session 155
Using Commands 156
Viewing targets, properties and commands for a target 156
Setting properties on a target 156
Associations 157
MergePoint SP appliance commands 157
Server commands 163
Using WS-Management 171
Automatic Discovery Management 172
Examples 174
Power Management 176
Examples 177
Telnet and SSHSession Management 179
Examples 181
WinRM Examples 183
Openwsman CLI Examples 186
Appendix A: Technical Support 193
Appendix B: Technical Specifications 194
Appendix C: Troubleshooting 197
viii MergePoint® SP Manager Installer/User Guide
Appendix D: Access Privileges 200
Appendix E: Configuring the BIOS Settings for SoL 204
Appendix F: Configuring a Virtual Serial Port 205
Appendix G: Profile Configuration 206
Appendix H: Glossary and Acronyms 218
License Information 221
Table of Contents ix
x MergePoint® SP Manager Installer/User Guide
Product Overview
1
1
The MergePoint service processor (SP) manager is a secure, centralized enterprise management solution for target devices equipped with IPMI, HP®, Dell®, IBM®, Sun® and Fujitsu Technology Solutions (FTS) service processors (SPs). You can remotely perform server management tasks, including power control and console access, on managed target devices.
The MergePoint SP manager provides a standardized interface independent of the management protocols used to manage each SP. Management operations can be performed using the following three methods:
The DSView® 3 management software interface.
The MergePoint SP manager web interface from a standard web browser.
Commands or scripts over a Telnet, command line interface (CLI) utility, Systems Management Architecture for Server Hardware Command Line Protocol (SMASH CLP), Secure Shell (SSH) session or Web Service for Management (WS-MAN).
SMASH CLP is a standards-based user and scripting interface defined by the Distributed Management Task Force (DMTF). This interface provides a single command line interface to manage servers from multiple manufacturers, simplifying management and streamlining interoperability while providing scripting and automation capabilities.
NOTE: MergePoint SP manager refers to the SP5200/SP5300/SP5224/SP5324/SP5240/SP5340 models. For features supported only by specificmodels, the supported model is noted.
Features and Benefits
The MergePoint SP manager provides secure Serial over LAN (SoL) console access, power control and server hardware monitoring. With easy-to-use IPMI provisioning capabilities and an auto discovery mechanism for server management technologies within the network, the MergePoint manager is ideal for enterprise data centers as well as for high performance computing (HPC) and other clustering environments.
The MergePoint SP manager allows enterprise-class authentication, authorization and auditing (AAA) security and encryption, and extends this functionality to all servers. Other standard features include data logging, event detection and notification, SNMP proxy, graphing and alarm events for sensors and shared access to management ports. Also, simultaneous power control of multiple servers boosts the already existing power management capabilities of service processors, including graceful shutdown support for IPMI.
With multiple Ethernet ports, the MergePoint SP5x24/SP5x40 manager connects point-to-point with Ethernet-based service processors. By isolating and protecting the connected service processors from the external production network, the MergePoint SP5x24/SP5x40 manager provides secure and efficient rack-level management with seamless integration into the management infrastructure.
Supported SPs
A variety of service processors are supported by the MergePoint SP manager. For a complete list of SPs supported by the version of firmware on your appliance, see the release notes or visit www.avocent.com to check for the latest release notes and firmware update.
2 MergePoint® SP Manager Installer/User Guide
MergePoint SP5x00 Manager Configuration
Figure 1.1: MergePoint SP5x00 Manager Configuration
Number Description Number Description
1 Remote User Web Interface 6 RJ-45 Ethernet Ports
2 LAN 7 Power
3 Target Device 8 Connection to the Serial Port
Table 1.1: Descriptions for MergePoint 00 Manager Configuration
Chapter 1: Product Overview 3
Number Description Number Description
4 CAT 5 Cables 9 Terminal or Workstation (for Configuration)
5 MergePoint SP5x00 Manager
LEDs on the MergePoint SP5x00 manager
On the front of the MergePoint SP5x00 manager, the LAN LED provides information about the LAN activity; the LED blinks to indicate activity. The power LED is green if the MergePoint SP5x00 manager is turned on.
4 MergePoint® SP Manager Installer/User Guide
MergePoint SP5x24/SP5x40 Manager Configuration
Figure 1.2: MergePoint SP5x24/SP5x40 Manager Configu ration (SP5340 model shown)
Chapter 1: Product Overview 5
Number Description Number Description
1 Private ethernet ports (24 or 40) 5
10/100 secondary public Ethernet port - (Optional)
For connection to a second network connection or for
failover connection to the primary network
2
10/100/GE (Gigabit Ethernet) primary
publicEthernet port
6 Blade or service processor
3 Auxiliary (AUX) port (disabled) 7 Remote user web interface
4
Console port - For connecting either a
terminal or a computer running a
terminal emulation program
8 Console user
Table 1.2: Descriptions for MergePoint 24/40 Manager Configuration
Safety Precautions
To avoid potentially fatal shock hazard and possible damage to equipment, please observe the following precautions:
Do not use a 2-wire power cord in any Avocent product configuration.
Test AC outlets at the target device and monitor for proper polarity and grounding.
Use only with grounded outlets.
NOTE: The AC inlet is the main power disconnect.
Failure to observe the precautions in this section may result in personal injury or damage to equipment.
Observe the following general safety precautions when setting up and using Avocent equipment.
Follow all cautions and instructions marked on the equipment.
Follow all cautions and instructions in the installation documentation or on any cautionary cards shipped with the product.
Do not push objects through the openings in the equipment. Dangerous voltages may be present. Objects with conductive properties can cause fire, electric shock or damage to the equipment.
Do not make mechanical or electrical modifications to the equipment.
Do not block or cover openings on the equipment.
6 MergePoint® SP Manager Installer/User Guide
Choose a location that avoids excessive heat, direct sunlight, dust or chemical exposure, all of which can cause the product to fail. For example, do not place an Avocent product near a radiator or heat register, which can cause overheating.
Connect products that have dual power supplies to two separate power sources, for example, one commercial circuit and one uninterruptible power supply (UPS). The power sources must be independent of each other and must be controlled by separate circuit breakers.
For products that have AC power supplies, ensure that the voltage and frequency of the power source match the voltage and frequency on the label on the equipment.
Products with AC power supplies have grounding-type three-wire power cords. Make sure the power cords are plugged into single-phase power systems that have a neutral ground.
Do not use household extension power cords with Avocent equipment because household extension cords are not designed for use with computer systems and do not have overload protection.
Make sure to connect DC power supplies to a grounded return.
Ensure that air flow is sufficient to prevent extreme operating temperatures. Provide a minimum space of 6 inches (15 cm) in front and back for adequate airflow.
Keep power and interface cables clear of foot traffic. Route cables inside walls, under the floor, through the ceiling or in protective channels or raceways.
Route interface cables away from motors and other sources of magnetic or radio frequency interference.
Stay within specified cable length limitations.
Leave enough space in front and back of the equipment to allow access for servicing.
When installing Avocent equipment in a rack or cabinet, observe the following precautions:
Ensure that the floor’s surface is level.
Load equipment starting at the bottom first and fill the rack or cabinet from the bottom to the top.
Exercise caution to ensure that the rack or cabinet does not tip during installation and use an anti-tilt bar.
When using a desk or table, observe the following precautions:
Choose a desk or table sturdy enough to hold the equipment.
Chapter 1: Product Overview 7
Place the equipment so that at least 50% of the equipment is inside the table or desk’s leg support area to avoid tipping of the table or desk.
Rack mount safety considerations
Elevated Ambient Temperature: If installed in a closed rack assembly, the operating temperature of the rack environment may be greater than room ambient. Use care not to exceed the rated maximum ambient temperature of the switch.
Reduced Air Flow: Installation of the equipment in a rack should be such that the amount of airflow required for safe operation of the equipment is not compromised.
Mechanical Loading: Mounting of the equipment in the rack should be such that a hazardous condition is not achieved due to uneven mechanical loading.
Circuit Overloading: Consideration should be given to the connection of the equipment to the supply circuit and the effect that overloading of circuits might have on overcurrent protection and supply wiring. Consider equipment nameplate ratings for maximum current.
Reliable Earthing: Reliable earthing of rack mounted equipment should be maintained. Pay particular attention to supply connections other than direct connections to the branch circuit (for example, use of power strips).
Cabling installation, maintenance and safety tips
The following is a list of important safety considerations that should be reviewed prior to installing or maintaining your cables:
Keep all CAT 5 runs to a maximum of 10 meters each.
Maintain the twists of the pairs all the way to the point of termination, or no more than one half inch untwisted. Do not skin off more than one inch of jacket while terminating.
If bending the cable is necessary, make it gradual with no bend sharper than a one inch radius. Allowing the cable to be sharply bent or kinked can permanently damage the cable’s interior.
Dress the cables neatly with cable ties, using low to moderate pressure. Do not overtighten ties.
Cross-connect cables where necessary, using rated punch blocks, patch panels and components. Do not splice or bridge cable at any point.
Keep CAT 5 cable as far away as possible from potential sources of EMI, such as electrical cables, transformers and light fixtures. Do not tie cables to electrical conduits or lay cables on electrical fixtures.
8 MergePoint® SP Manager Installer/User Guide
Always test every installed segment with a cable tester. “Toning” alone is not an acceptable test.
Always install jacks so as to prevent dust and other contaminants from settling on the contacts. The contacts of the jack should face up on the flush mounted plates, or left/right/down on surface mount boxes.
Always leave extra slack on the cables, neatly coiled in the ceiling or nearest concealed location. Leave at least five feet at the work outlet side and 10 feet at the patch panel side.
Choose either 568A or 568B wiring standard before beginning. Wire all jacks and patch panels for the same wiring scheme. Don’t mix 568A and 568B wiring in the same installation.
Always obey all local and national fire and building codes. Be sure to firestop all cables that penetrate a firewall. Use plenum rated cable where it is required.
CAUTION: ThisMergePoint SP manager contains an internal battery that isused for the real time clock. This
battery is not a field replaceable item, and replacement should not be attempted by a user. If real time clockerrors
occur and the battery is suspected, visit http://www.avocent.com/support or contact the Avocent Technical Support
location nearest you.
WARNING: For Service Personnel Only - There is a riskof explosion if the battery is replaced with an incorrect
type. Dispose of used batteriesaccording to the manufacturer’s instructions.
Chapter 1: Product Overview 9
10 MergePoint® SP Manager Installer/User Guide
Installation and Setup
2
11
Configuring Power for the MergePoint SP manager
The MergePoint SP manager is supplied with single or dual AC or DC power supplies.
To configure AC power:
1. Make sure that the power switch on the MergePoint SP manager is turned off.
2. Plug the power cable into the MergePoint SP manager and into a power source.
3. Turn on the MergePoint SP manager.
To configure DC power:
DC power is connected to DC-powered MergePoint SP managers by way of three wires: Return (RTN), Ground (GND) and -48VDC.
WARNING: It is criticalthat the power source supports the DC power requirements of your appliance. Make sure that
your power source is the correct type and that your DC power cables are in good condition before proceeding. F ailure
to do so could result in damage to the equipment or in personal injury.
The following diagram shows the connector configuration for connecting DC power. You may use either a flat-blade or Phillips screwdriver for this procedure.
Figure 2.1: DC Power Connectio n Terminal Block
Number Description
1 RTN (Return)
2 GND (Ground)
3 -48VDC
Table 2.1: DC Power Connection Details
1. Make sure that the power switch on the appliance is turned off.
2. Make sure that DC power cables are not connected to a power source.
3. Remove the protective cover from the DC power block by sliding it to the left or right.
4. Loosen all three DC power connection terminal screws.
5. Connect your return lead to the RTN terminal and tighten the screw.
6. Connect your ground lead to the GND terminal and tighten the screw.
7. Connect your -48VDC lead to the -48VDC terminal and tighten the screw.
8. Slide the protective cover back into place over the DC terminal block.
12 MergePoint® SP Manager Installer/User Guide
9. If your MergePoint SP manager has dual-input DC terminals, repeat steps 3 - 8 for the second terminal.
10. Connect the DC power cables to the DC power source and turn on the DC power source.
11. Turn on the MergePoint SP manager.
Connecting to the Network
To connect the MergePoint SP manager and service processors to the network:
1. Rack mount or place the MergePoint SP manager at the top of your server rack.
2. For a MergePoint SP5x00 manager: Using Ethernet cables, connect the LAN1 (eth0) network port on the back of the appliance to the external network, and connect the LAN2 (eth1) port to the internal network. In a typical installation, the LAN1 port provides access to the web interface, and the LAN2 port provides access to the service processors.
-or-
For a MergePoint SP5x24/SP5x40 manager: Connect an Ethernet cable from the primary Ethernet 10/100/GE (Gigabit Ethernet) port to the network. If desired, connect an Ethernet cable to the secondary Ethernet 10/100 port and configure the port for failover (see Configuring MergePoint SP5x24/SP5x40 manager network settings on page 22).
Connect an Ethernet cable from any private Ethernet port on the MergePoint SP5x24/SP5x40 manager to dedicated Ethernet ports on a service processor or a dedicated Ethernet port on a blade chassis that manages multiple blades.
3. Turn on the power switches of the connected devices.
NOTE: Service processors should be configured according to their manufacturer’s instructions.
Configuring the MergePoint SP Manager Basic Settings
The MergePoint SP manager is DHCP enabled by default. When you turn on the MergePoint SP manager for the first time, it attempts to obtain eth0 and eth1 IP addresses from the DHCP server. For installations where a DHCP server is not present or is unavailable, the following IP addresses are automatically assigned: 192.168.0.10 for eth0 and 192.168.0.20 for eth1.
To configure the MergePoint SP manager IP address through a serial connection:
1. Connect a terminal or a workstation that is running a terminal emulation program to the serial port.
Chapter 2: Installation and Setup 13
2. Start a session with the port settings of serial speed as 9600 bps, data length as 8 data bits, parity as none, stop bits as 1, flow control as none and emulation as ANSI.
Once a connection is established, a prompt appears.
3. Enter the username and password. The preset values is admin for both the username and password.
4. For the MergePoint SP5x00 manager:
a. Type 2 (Network Config).
b. Type a number from 1 to 5 to configure the corresponding network settings specific to
your network. For example, type 1 to config eth0 IPv4; type 3 to config eth1 IPv4.
NOTE: If you wish to restore the default configuration parameters, enter 8 from the top-levelmenu.
-or-
For a MergePoint SP5x24/SP5x40 manager:
a. Log into the console port as root with the default password Sydney.
b. Enter the passwd command, and enter and confirm a new password for the root user.
c. Type cli to load the CLI utility.
d. Configure the primary Ethernet interface (eth0) by setting the method to static and
assigning a static IP address, a gateway and a netmask:
cli> set network interface eth0 method static address
<SPmanager_IPaddress> gateway <gateway_IP_address> netmask
<netmask>
e. Specify a hostname, a domain, a DNS server IP address, and an optional secondary
DNS server IP address:
cli> set network hostname <appliance_name> resolv domain
<domain_name> dns0 <DNS_server_IPaddress> dns1 <secondary_DNS_
server_IPaddress>
f. Confirm the configuration for the interface:
cli> get network interface eth0
g. Confirm the name server configuration:
cli> get network resolv
h. Save the changes:
cli> commit
14 MergePoint® SP Manager Installer/User Guide
i. Exit from the CLI utility:
cli> quit
NOTE: To restore default configuration parameters, type restorefactory.
NOTE: For more information on configuring IP address, see Summary of How to Configure the Top Level
Parameters on page 136.
Activating the MergePoint SP5x00 Manager License
You must register your MergePoint SP5x00 manager online at www.avocent.com to obtain a master license key. Use the master key to activate the MergePoint SP5x00 manager before discovering SPs.
NOTE: Registration is not required for the MergePoint SP5x24/SP5x40 manager.
To activate the MergePoint SP5x00 manager license:
1. Follow the instructions on the registration card included with the MergePoint SP5x00 manager to activate the appliance serial number. Once completed, you will receive a master license key.
2. Open a web browser and enter the IP address (http://<appliance IP address>) of the appliance.
3. The MergePoint SP5x00 manager web interface window appears. Type the master key in the fields provided and click Add.
4. The User Login window appears. Type admin as the username and password. To change the admin password, see Managing MergePoint SP Manager User Accounts on page 29.
To add a master key:
1. Click the System tab.
2. In the top navigation bar, click Licenses. The License window appears.
3. Click Add Master Key and enter the key.
4. Click Apply.
To view license information (Admin users only):
1. Click System – Licenses for a license summary and list of license keys and descriptions.
NOTE: Licensesare also required for each SP you wish to manage; see Service Processor Licenseson page 33.
Chapter 2: Installation and Setup 15
Adding the MergePoint SP Manager to a DSView 3 Software Installation
If you will be using the MergePoint SP manager within a DSView 3 software installation, you may now use the DSView 3 software Add Appliance wizard to add the MergePoint SP manager and finish configuration. For detailed instructions, refer to the DSView 3 software installer/user guide.
MergePoint SP Manager Configuration Wizard
Use the configuration wizard to quickly set up a new MergePoint SP manager. The wizard window opens automatically the first time you log in to the appliance, or after you reset a MergePoint SP5x00 manager through the serial port and log in again; see Restarting the
MergePoint SP5x00 manager on page 197. You can also open the wizard by selecting System ­Wizard.
The wizard allows you to configure appliance settings such as alias, default user account, discovery range, appliance network, provisioning, SNMP, host table and so on. These settings can be saved as an XML file for future use when you configure an appliance using the wizard.
To configure a MergePoint SP manager using the wizard (Admin users only):
1. Click the System tab.
2. In the top navigation bar, click Wizard.
3. (MergePoint SP5x00 manager only) In the Add-On License Key panel, enter the new slave key, then click Next. For more information, see Service Processor Licenses on page 33.
4. Click Load Config File if you wish to import a previously saved configuration file (see Saving the wizard settings in a config file on page 17).
-or-
Click Next to enter the Wizard Parameters Settings page.
5. In the Appliance Alias field, type the new name for the appliance.
6. Configure the settings displayed and follow the on-screen instructions. For more information about how to configure settings, see the corresponding reference in MergePoint SP Manager Configuration Wizard on page 16.
7. Click OK to reboot the appliance. The configuration takes effect after the reboot is complete.
16 MergePoint® SP Manager Installer/User Guide
Setting or Panel Reference
Default User Accounts Managing Default Users (Admin users only) on page 43
Authentication Configuring External Authentication Services on page 95
Alert Action Using the Alerts Viewer on page 58
User Roles Managing MergePoint SP Manager User Accountson page 29
Appliance Network Configuring the MergePoint SP Manager Network Settings on page 19
SNMP SNMP Access on page 63
Host Table Host table on page 72
Static Routes Static routes on page 73
Set Discovery Range Discovering and Adding SPs (Admin Users Only) on page 34
Provisioning BMC Provisioning (IPMI Targets Only) on page 26
Table 2.2: References for Configuration Settings
Saving the wizard settings in a config file
Once you have completed the configuration wizard, you can save the settings for future use. Some settings, such as appliance alias, are specific to each MergePoint SP manager. These appliance-specific settings can be modified before applying the configuration.
To save a config file:
1. Complete the steps in MergePoint SP Manager Configuration Wizard on page 16.
2. Click Save Config File to Disk. All wizard data is compiled and a download link appears below the Save Config File to Disk button.
3. Right-click Download and select Save Target As to save the data file, or click Download to view the data file.
Modifying the config file settings (Admin users only)
You can modify the config file from the wizard interface or from an XML editor. Modifying a config file using an XML editor is only recommended for advanced users who are familiar with XML.
To modify a config file from the wizard interface:
1. Click the System - Wizard.
Chapter 2: Installation and Setup 17
2. Click Load Config File.
3. In the Filename field, type the path to the file you wish to open or click Browse to locate the file.
4. Click Upload to import the data in the file to the wizard. The settings stored in the config appear on screen. Optionally, use this interface to modify any settings that need to be changed for this appliance.
5. Click Apply Current Config to configure the appliance.
To manually modify the config file using an XML editor:
CAUTION: The following procedure is recommended for advanced users only; if you inadvertently corrupt the XML
code, the config file may become unusable or cause error messages when loaded in the wizard.
1. Download and save a config file. For more information, see Saving the wizard settings in a config file on page 17.
2. Open the config file with an XML editor.
3. Modify the property values as you desire. See Modifying the config file settings (Admin users only) on page 17 for more information.
4. Validate the config file with an XML-compliant browser or an XML validation tool.
5. Save the config file.
18 MergePoint® SP Manager Installer/User Guide
Sample code from config file Description
......
- <optionlist optionlistId="network_ device_name">
<option value="eth0" /> <option value="eth1" /> <option value="bond0" /> <option value="br0" /> </optionlist>
......
<elements elementsId="MP_Network_Device">
- <element elementId="Network_Device_ Eth0">
<property propertyId="Interface_Name"
classification="SingleSelect" optionlistId="network_device_name"
value="eth0" />
......
</element>
....
</elements>
<optionlist> defines a value scope in a <property>.
In the example <optionlist> “network_device_
name” determines the value of o ptionlistId
“network_device_name” in the <property>
“Interface_Name.
classification= “SingleSelect” means the value of
this property can only be the <option> value in the
corresponding <optionlist>.
NOTE: You are not allowed to add, delete or modify any of the <optionlist>parameters.
- <elements elementsId="MP_User">
- <element> <property propertyId="Name" unique="true"
classification="String" size="64" value="admin" />
- <!-- The value of Password can't be edited.
--> <property propertyId="Password"
classification="String" size="64"
value="$1$FMKp84sM$K.L1haftQaeznWLB7T/6S."
/>
....
</element>
......
</elements>
The password of an MP_User is encrypted and
cannot be changed.
Each MergePoint SP manager should have at
least one Admin user. An Admin user account
cannot be deleted if it is the only Admin user
account configured.
unique="true" means the value of this property
cannot be duplicated.
Table 2.3: Samples of the Con fig File for the MergePoint 24/40 Manager
Configuring the MergePoint SP Manager Network Settings
Ethernet ports on the MergePoint SP5x00 manager
The MergePoint SP5x00 manager has two public Ethernet ports (eth0 and eth1), which are labeled LAN1 and LAN2. The eth0 port is for connecting to the external network and eth1 is for connecting to service processors on the internal network.
Chapter 2: Installation and Setup 19
NOTE: Connecting service processors to eth0 is not recommended because some services, like BMC provisioning or DHCP servers, only listen to eth1.
Ethernet ports on the MergePoint SP5x24/SP5x40 manager
The MergePoint SP5x24/SP5x40 manager has two public Ethernet ports (eth0 and eth1) and 24 or 40 Ethernet private ports. The public ports are used for connecting to the public (or management) network and the private ports are used for connecting to service processors on the private network. Therefore, the managed private side of the MergePoint SP manager is isolated from the public side to ensure security. Access to all connected service processor servers is consolidated through the one publicly known IP address.
Private Ethernet ports
The MergePoint SP5x24/SP5x40 manager is aware of only a single interface to the private network, priv0, for communicating with the SPs. Packets are sent and received by priv0 through the private Ethernet ports.
Each private Ethernet port may be connected to one or to multiple service processors. For example, an Ethernet port may be connected to a blade manager with multiple service processors, and in those cases a single private Ethernet port may require multiple IP addresses.
All communication among private Ethernet ports is blocked unless priv0 is the sending or receiving port.
Public Ethernet ports
On the public side of the MergePoint SP5x24/SP5x40 manager, the primary and secondary Ethernet ports are referred to as eth0 and eth1.
Failover
Failover is important for high-availability environments where constant accessibility is required to support mission-critical applications. The secondary Ethernet port on the MergePoint SP5x24/SP5x40 manager can optionally be configured for failover. Failover automatically redirects traffic from the primary Ethernet port to the secondary Ethernet port should the primary interface fail.
The primary Ethernet port continues to be monitored, and when it starts functioning again, traffic is then automatically redirected back through the primary Ethernet port. All connection sessions continue without interruption.
With failover, both the primary and secondary Ethernet ports are assigned a single IP and single MAC [Ethernet] address. After failover is enabled, the bonded Ethernet interfaces are referred to as bond0.
20 MergePoint® SP Manager Installer/User Guide
Bridge mode
Bridge mode bridges the private Ethernet ports with the public Ethernet ports, allowing traffic to go through the MergePoint SP5x24/SP5x40 manager from a host on the external network to a service processor on the internal network and vice-versa, with no interference from the MergePoint SP manager itself.
After Bridge mode is enabled, the bridged Ethernet interfaces are referred to as br0; the eth0, eth1 and priv0 are not accessible at the same time.
NOTE: If Bridge mode is enabled, securitysettings are no longer managed by the MergePoint SP manager. Instead, the user must configure any required security settings from the service processor attached to the MergePoint SP manager.
Configuring MergePoint SP5x00 manager network settings
In the Appliance Network Setting window, you can set IP addresses for the Ethernet ports and configure a DNS server.
A primary and a secondary DNS server may be configured to allow the use of SP names instead of IP addresses.
You can also set VLAN for each Ethernet interface.
To configure network settings for the MergePoint SP5x00 manager (Admin users only):
1. Click the Network tab.
2. In the top navigation bar, click Network.
3. Select Eth0 or Eth1 as the default gateway and click Apply.
4. Configure the following fields for the Domain Name System (DNS) server:
a. In the Primary server field, type the IP address of the primary server.
b. In the Secondary server field, type the IP address of the secondary server.
c. In the Domain name field, type the domain name.
d. Click Apply.
5. Click a device link. Configure IPv4 and/or IPv6 addresses by entering the following information in the respective areas.
a. In the MTU field, accept or change the existing value.
b. For the DHCP method, select DHCP.
-or-
Chapter 2: Installation and Setup 21
For the Static method, select Static and enter the address, subnet mask, gateway in the fields provided. For IPv4 only, also enter the broadcast in the field provided.
c. Click Apply.
To enable VLAN for the MergePoint SP5x00 manager (Admin users only):
1. Click the Network tab.
2. Click a device link. Configure VLAN for the device:
a. In the ID field, type the ID for the VLAN.
b. In the Status drop-down menu, select Yes to enable VLAN.
c. Click Apply.
Configuring MergePoint SP5x24/SP5x40 manager network settings
When configuring Ethernet ports, be aware of the following conditions:
In Normal mode, eth0 and eth1 are separate network interface cards and all standard networking rules apply. When each Ethernet port is active and assigned a different IP address, both ports are reachable through either IP address even if the cable is disconnected from one of the interfaces.
In Failover mode, the secondary Ethernet interface becomes bonded to the primary Ethernet interface and both are referred to as a single bond0 interface. The bond0 IP address is used for both eth0 and eth1 physical network interface cards. As a result, the same set of values applies to the single bond0 interface.
In Bridge mode, both the primary and secondary Ethernet interface become disabled. The Br0 IP address is used as the host address for the MergePoint SP manager and is accessible from any of the physical ports, including the private ports. In addition, security settings are no longer managed by the MergePoint SP manager. Instead, the user must configure any required security settings from the service processor attached to the MergePoint SP manager.
To configure network settings for the MergePoint SP5x24/SP5x40 manager (Admin users only):
1. Click the Network tab.
2. In the top navigation bar, click Network. The Appliance Network Setting window appears.
3. In the mode drop-down menu, select the mode and click Apply.
4. Select eth0 or eth1 as the default gateway and click Apply.
22 MergePoint® SP Manager Installer/User Guide
5. Configure the following fields for the Domain Name System (DNS) server:
a. In the Primary server field, type the IP address of the primary server.
b. In the Secondary server field, type the IP address of the secondary server.
c. In the Domain name field, type the domain name.
d. Click Apply.
6. Click a device link. Configure IPv4 and/or IPv6 addresses by entering the following information in the respective areas.
a. In the MTU field, accept or change the existing value.
b. For the DHCP method, select DHCP.
-or-
For the Static method, select Static and enter the address, subnet mask, gateway in the fields provided. For IPv4 only, also enter the broadcast in the field provided.
c. Click Apply.
NOTE: For Normal mode, you may configure either eth0 or eth1, or both. For Failover mode, you only need to configure Ethernet port bond0. For Bridge mode, you only need to configure Ethernet port br0.
NOTE: Network settings may also be changed using the CLI utility. See related CLI commands in Summary of How to Configure the Top Level Parameters on page 136.
You may set a switch port speed individually, or retrieve the current port speed from the MergePoint SP5x24/SP5x40 manager.
To set the switch port speed:
1. Log into the MergePoint SP manager console as root.
2. Set the port speed using the following command:
sysctl marvell.xxx=value
(Value=auto/10f/10h/100f/100h/10F/10H/100F/100H)
NOTE: The definitionsfor the values are: - auto: Auto mode. The system selects an appropriate speed for the switch port. - 10f / 10h / 100f / 100h: Mandatory mode. The system cannot change the value. This setting may cause
operations to failif the value is not appropriate for the switch port. - 10F / 10H / 100F / 100H: Negotiable mode. The
system may use this value, or set another value if this value is not appropriate for the switch port.
To get the individual port speed:
1. Log into the MergePoint SP manager console as root.
2. Retrieve the current speech of the switch port using the following command:
Chapter 2: Installation and Setup 23
sysctl –n marvell.xxx
NOTE: The xxxvalue is the switch port number. The output is the current speed of the switch port. The current speed may differ from the speed you set if you chose auto mode or negotiable mode for the speed value.
Private Subnets on the MergePoint SP5x24/SP5x40 Manager
Service processors connecting to the private subnets on a MergePoint SP5x24/SP5x40 manager can be isolated on a management network that is separate from the production and public networks. To enable communications between the SPs and the MergePoint SP5x24/SP5x40 manager, an Admin user must configure at least one private subnet. The Admin user then assigns each private subnet the following:
A name
An address within the private subnet’s address range to be used by the SP when communicating with the MergePoint SP manager
Any number of private subnets may be configured. Multiple private subnets may be needed if IP addresses for SPs are not in the same range.
NOTE: If changing or deleting a private subnet, reassign all affected devices to another private subnet to avoid making them unavailable.
NOTE: If you are using DHCP and plan to assign a 192.168.0.x address to the MergePoint SP manager, see Setting up a private subnet and DHCP service in the 192.168.0.x range on page 198 to avoid IPaddress conflicts.
To add a private subnet:
1. Click Network - Private subnet.
2. Click Add.
3. Enter a name in the Private subnet name field.
4. In the Appliance side IP address field, enter an IP address for the MergePoint SP5x24/SP5x40 manager within the private subnet’s network address range.
5. In the Subnet Mask field, enter a netmask for the private subnet.
6. Click Apply.
To edit a private subnet:
1. Click Network - Private subnet.
2. Click the name link of the private subnet you want to edit.
3. Modify the fields as needed.
4. Click Apply.
24 MergePoint® SP Manager Installer/User Guide
To delete a private subnet:
1. Click Network - Private subnet.
2. Check the private subnet you want to delete and click Delete.
Firewall/Packet Filtering
Packet filtering on the MergePoint SP manager is controlled by chains and rules that are configured in iptables. By default, the MergePoint SP manager does not forward any traffic between private and public networks. Rules can be added to allow limited communications between specific SPs on the private network and the public network.
NOTE: It is possible for an Admin user to create rules that circumvent the access controls on an SP.
Chains
A chain is a type of named profile that defines rules for sorting packets.
The MergePoint SP manager has a number of built-in chains with hidden rules that are preconfigured to control communications between SPs connected to the private Ethernet ports and devices on the public side of the MergePoint SP manager.
The default chains are defined in filter and NAT (network address translation) iptables. The mangle table is not used. The built-in chains are named according to the type of packets they handle. The first three chains, INPUT, OUTPUT and FORWARD are in the iptables filter table.
PREROUTING, POSTROUTING and OUTPUT are in the NAT table and implement NAT. This includes redirecting packets addressed to a virtual IP to the SP's real IP address and then hiding the SP's real IP address when the SP sends packets to a user.
Rules
Each chain can have one or more rules that define the following:
The packet characteristics being filtered. The packet is checked for characteristics defined in the rule, for example, a specific IP header, input and output interfaces and protocol.
What action is performed when the packet characteristics match the rule. The packet is handled according to the specified action (called a Rule Target, Target Action or Policy).
Rules are listed in order of priority. You can change the rule order by clicking the arrow on the rule line. The arrow appears when there are at least two rules in a list.
When a packet is filtered, its characteristics are compared against each rule in the list until a match is found. Once a match is found, the packet is processed and no attempt is made to match lower priority rules.
Chapter 2: Installation and Setup 25
To add a new packet filtering (firewall) rule:
1. Click Network - Firewall.
2. Click Add for the chain to which you wish to add a rule.
3. Configure one or more of the following filtering options, as desired.
a. In the Protocol drop-down menu, select a protocol.
b. In the Source IP/mask field, type a source IP and subnet mask in the form:
hostIPaddress or networkIPaddress/NN.
c. In the Destination IP/mask field, type a destination IP and subnet mask in the form:
hostIPaddress or networkIPaddress/NN.
d. In the Input interface or Output interface drop-down menu, select an input or output
interface depending on which chain you select.
e. In the Fragments drop-down menu, choose the type of packets to be filtered.
f. In the Rule target drop-down menu, select a target.
4. Click Apply.
To edit a packet filtering (firewall) rule:
1. Click Network - Firewall.
2. Select the rule you want to change.
3. Modify the fields as needed.
4. Click Apply.
To delete a packet filtering (firewall) rule:
1. Click Network - Firewall.
2. Select the rule you want to delete and click the corresponding Delete button.
NOTE: Rules may also be changed using the CLI utility. See related CLI commands in Summary of How to Configure the Top Level Parameters on page 136.
BMC Provisioning (IPMI Targets Only)
NOTE: Before setting up BMC provisioning, create a private subnet. See Private Subnets on the MergePoint
SP5x24/SP5x40 Manager on page 24.
The default status of the BMC on an SP is disabled and should be provisioned before it can be discovered by the MergePoint SP manager.
26 MergePoint® SP Manager Installer/User Guide
The MergePoint SP manager provides a PXE (Preboot Execution Environment) based solution for provisioning the BMC and can be configured to automatically provision the IPMI BMC of a target device. The network interface card (NIC) on the BMC must support PXE to the NIC interface. If you have a dedicated IPMI NIC, your system may not support PXE to that device or port.
There are two modes of provisioning available: dynamic and static. For static provisioning, when the SP manager receives a PXE request from an SP, it can obtain its MAC address from the request and use it for comparison with the MAC address and IP address pairs in the static provisioning table. If a MAC address in the table meets this request, the MergePoint SP manager will assign the corresponding IP address to the SP.
Dynamic provisioning occurs when no match is found and the MergePoint SP manager selects an IP address from a specified range for the SP.
Once you have provisioned the BMC successfully, the SP is automatically initialized with the specified provisioning parameters and added to the Managed SP list and side navigation bar where it can then be accessed with the MergePoint SP manager. The number of in use and free license is re-calculated.
NOTE: Automatic provisioning is an optional feature that is only available for target devices that have IPMI BMCs.
Starting or stopping the BMC provisioning service (Admin users only)
You may start or stop the BMC provisioning service through the Provisioning window. If the Stop button is clicked, the BMC provisioning service stops and the MergePoint SP manager will no longer accept PXE boot requests from SPs on the LAN. However, previously provisioned SPs that have IPMI BMCs can still be discovered.
To stop or start the BMC provisioning service:
1. Click SP - Provisioning.
2. In the Provisioning window, click Stop or Start as appropriate.
Configuring PXE parameters for IPMI BMC provisioning (Admin users only)
You must configure provisioning parameters for a BMC that will be initialized and managed by the MergePoint SP manager.
To set basic provisioning parameters in the MergePoint SP5x00 manager:
1. Click SP - Provisioning.
2. Enter the username and gateway address in the fields provided.
3. In both the Password and Confirm Password fields, enter the password.
Chapter 2: Installation and Setup 27
4. Check the VLAN Enable field if you need to use VLAN on BMC, and specify the following VLAN parameters:
a. In the VLAN ID field, type the VLAN ID.
b. In the VLAN Priority field, type the VLAN priority.
5. Click Apply.
NOTE: For the MergePoint SP5x00 manager, it is strongly recommended that the VLAN ID on the BMC and the MergePoint SP5x00 manager are the same; otherwise, the BMC cannot communicate with the MergePoint SP manager in the VLAN mode.
To set basic provisioning parameters in the MergePoint SP5x24/SP5x40 manager:
1. Click SP - Provisioning.
2. In the Subnet drop-down menu, select a subnet.
3. Enter the username and gateway address in the fields provided.
4. In both the Password and Confirm Password field, enter the password.
5. Select VLAN Enable to use VLAN on the BMC, and specify the following parameters:
a. In the VLAN ID field, type the VLAN ID.
b. In the VLAN Priority field, type the VLAN priority.
6. Click Apply.
To set dynamic provisioning parameters:
1. Click SP - Provisioning.
2. In the Dynamic Provisioning area, enter the Start and End IP addresses of a range of optional BMC IP addresses.
3. Click Apply.
To set static provisioning parameters:
1. Click SP - Provisioning.
2. In the Static Provisioning area, click Add and specify the requested PXE parameters.
3. Click Apply.
NOTE: To modify the static IP address, click the name link and follow the on-screen instructions. To delete a static IP address, select the name link and clickDelete.
28 MergePoint® SP Manager Installer/User Guide
BMC log
Once BMC provisioning starts, an activity log is displayed in the Provisioning window listing all IP addresses which have been assigned to SPs. A status of Confirmed or Unconfirmed is displayed for each SP in the specified IP address range. A status of Confirmed in the State column indicates that the BMC provisioning for that SP is complete and the SP can now be managed by the MergePoint SP manager.
To delete the provisioning log (Admin users only):
1. Click SP- Provisioning.
2. In the Provisioning Log area, select the desired line(s) and click Delete.
Managing MergePoint SP Manager User Accounts
The default user account username and password are both admin. Each MergePoint SP manager should have at least one Admin user. An Admin user account cannot be deleted if it is the only Admin user account configured.
You may specify a role of Admin, Operator, User or a customized role for each user and/or group account. Each role is associated with specific privileges. The Admin role allows the user to modify all settings, perform all appliance operations and manage all SPs. The Operator role allows the user to perform basic operations, modify a limited number of settings and manage assigned SPs. The User role allows the user to view and query information of assigned SPs but prevents the user from performing most operations and modifying most settings. Customized roles are created under the Group Role tab. An Admin can specify privileges for the customized roles and assign users and groups to customized roles.
User accounts can also be managed in groups. A user is allowed to manage both SPs assigned to his or her user account and SPs assigned to any group to which the user belongs. The role assigned to the user account takes precedence of the roles assigned to groups to which the user belongs.
Additionally, if you are using an external authentication server to manage MergePoint SP manager users, you can use roles to manage permissions for external users. First, create a group on the external authentication server that has the same name as a group on the MergePoint SP manager. Next, assign a role to the MergePoint SP manager group. Now when externally authenticated users who are members of the group log in to the MergePoint SPmanager, their privileges are determined by the role assigned to the group.
Chapter 2: Installation and Setup 29
Reserved words (do not use as usernames)
Reserved words are predefined words that have special meaning to the MergePoint SP manager. Do not use the following reserved words when configuring usernames.
adm daemon gnats news src utmp
admin dialout ip nobody sshd video
apache disk irc operator sudo voice
audio dip kmem postgres sync wheel
backup fax lisy proxy tape wwwdata
bin floppy mail root tty
cdrom games man shadow uucp
Table 2.4: Reserved Word
To add an appliance user (Admin users only):
1. Click Users - User Roles.
2. Click Add.
3. Specify the following information for the new user:
a. In the User Name field, type the username.
b. In the Password field, type the password.
c. From the Role menu, select the role you wish to assign to the user: Admin, Operator,
User or a customized role.
d. For Operator, User or customized role privilege users, select the SPs which can be
managed by the user. For Admin privilege users, skip this step (by default, Admin users are permitted to access all devices).
4. Click Apply.
To edit an appliance user (Admin users only):
1. Click Users - Users.
2. Click the username link for the user you wish to edit.
3. To change the password, select Change Password. Type the new password in the New Password and Confirm Password fields.
30 MergePoint® SP Manager Installer/User Guide
4. To change the privileges assigned to the user, select the desired privilege from the Privilege drop-down menu: Admin, Operator, User or customized roles.
5. For Operator, User or customized role privilege users, select the SPs which can be managed by the user. For Admin privilege users, skip this step.
6. Click Apply.
To delete an appliance user (Admin users only):
1. Click Users - Users.
2. Click the username link for the user you wish to delete and click Delete.
To customize a new role (Admin users only):
1. Click Users - Roles.
2. Click Add.
3. In the Role Name field, type the name of the user role you want to create.
4. Check the operation(s) which you want this user role to access.
5. Click Apply.
To change the password for the user account (for Operator and User users only):
1. Click Users - Users.
2. Type the new password in the New Password and Confirm Password fields and click Apply.
To create a new user group (Admin users only):
1. Click Users - Groups.
2. Click Add.
a. Specify the following information for the new user:
b. In the User Group Name field, type the group name.
c. From the Role menu, select the role you wish to assign to the user: Admin, Operator,
User or a customize roles.
NOTE: If the user group is for users managed by an external authentication server, ensure that a role of the same name existson the authentication server.
d. In the Users area, select the users for the group.
e. In the SP area, select the SPs for the group.
3. Click Apply.
Chapter 2: Installation and Setup 31
To edit a user group (Admin users only):
1. Click Users - Groups.
2. Click the link of the group name you want to edit.
3. Edit the settings as needed and click Apply.
To delete a user group (Admin users only):
1. Click Users - Groups.
2. Select the user group you want to delete and click Delete.
DHCP on the MergePoint SP Manager
The MergePoint SP manager has a Dynamic Host Configuration Protocol (DHCP) server to quickly and efficiently configure new devices on the Ethernet. It supports Dynamic and Static DHCP; static DHCP is performed before dynamic DHCP.
DHCP-assigned SPs can be added to a managed SP list automatically if the username and password of the device match the default username and password.
DHCP on the MergePoint SP manager supports DHCP relay. The DHCP relay is a Bootstrap Protocol (BOOTP) relay agent that sends DHCP messages between DHCP clients and DHCP servers on different IP networks. After enabling DHCP relay, you must configure a DHCP relay server in another physical network.
Once DHCP starts, an activity log is displayed in the DHCP window listing all IP addresses which have been assigned to SPs.
To set the DHCP parameters in the MergePoint SP5x00 manager:
1. Click SP - DHCP.
2. For dynamic DHCP, specify the Start and End IP range of addresses in the dynamic DHCP area.
-or­For static DHCP, click Add in the Static IP area and specify the requested parameters.
3. Click Apply.
To set the DHCP parameters in the MergePoint SP5x24/SP5x40 manager:
1. Click SP - DHCP.
2. In the Subnet drop-down menu, select a subnet.
32 MergePoint® SP Manager Installer/User Guide
3. For dynamic DHCP, specify the Start and End IP range of addresses in the dynamic DHCP area.
-or-
For static DHCP, click Add in the Static IP area and specify the requested parameters.
4. Click Apply.
NOTE: To modify a static IP address, click on the name of the IP addressand follow the on-screen instructions. To delete a static IP address, select the check box next to the name and click Delete.
To stop or start the DHCP service:
1. Click SP - DHCP.
2. Click Stop or Start as appropriate.
To configure the DHCP relay server:
1. Click SP - DHCP.
2. In the Status area, select Enable to activate DHCP relay.
3. In the Server field, enter the IP address or the name of the DHCP relay server.
4. Click Apply.
NOTE: DHCP settings may also be changed using the CLI utility. See the related CLI commands in Summary of How to Configure the Top Level Parameters on page 136.
Service Processor Licenses
A license is required for each SP managed by the MergePoint SP manager. Blade chassis require a license for the chassis itself and for each blade housed in the chassis.
The MergePoint SP5x24/SP5x40 manager includes 64 SP licenses and additional licenses cannot be purchased. The MergePoint SP5x00 manager includes 64 SP licenses and additional license keys (slave keys) can be purchased in increments of 64 or 128, with a maximum of 256 SP licenses per appliance.
To add service processor license keys (slave keys) to the MergePoint SP5x00 manager:
1. Click the System tab.
2. In the top navigation bar, click Licenses. The License window appears.
3. Click Add Slave Key and enter the key.
4. Click Apply.
Chapter 2: Installation and Setup 33
To view the number of in use and free SP licenses:
Click the SP tab. The Managed SP list displays how many service processors are currently managed by the appliance and the number of remaining free licenses.
NOTE: An appliance license is also required to activate the MergePoint SP5x00 manager; see Activating the MergePoint SP5x00 Manager License on page 15.
Automatically Manage SPs
By default, you must add newly discovered service processors to the Managed SP list before you can access the device using the MergePoint SP manager; see Managed and Unmanaged SP Lists (Admin users only) on page 38. However, you may configure the System Settings to automatically add all newly discovered serviceprocessors to the Managed SPlist.
To enable automatic management of SPs:
1. Click System - Setting.
2. If you want to automatically manage DHCP devices, select Yes for the related option.
3. If you want to automatically manage devices discovered from an IP address range, select Yes for the related option.
4. Click Apply.
Next steps:
It's recommended to set the discovery time interval to five minutes. See Discovering and Adding SPs (Admin Users Only) on page 34.
If you chose to automatically manage DHCPdevices but have not configured the DHCP service, see DHCP on the MergePoint SP Manager on page 32.
Discovering and Adding SPs (Admin Users Only)
You can configure the MergePoint SP manager web interface to discover SPs that reside on the same LAN as the appliance by specifying up to two IP address ranges either for automatic or manual discovery. Discovered service processors are either displayed in the Unmanaged SP list or, if automatic management is enabled, added to the Managed SP list; see Automatically Manage SPs on page 34. Service processors in the Unmanaged SP list can be transferred to the Managed SP list.
You may designate up to two IP address ranges for discovery. The first time you access the SP window, the IP address ranges for the discovery setting are blank and may be modified by clicking Edit. You can also manually add an SP if you know its IP address.
34 MergePoint® SP Manager Installer/User Guide
For most SPs, you can view the type of SPs from the SP Profile column in the Unmanaged SP list. In a few cases, the SP profiles cannot be recognized until the SPs are managed and verified. For more details, see Managed and Unmanaged SP Lists (Admin users only) on page 38.
NOTE: To avoid MergePoint SPmanager discover errors, ensure the following:
- RSA II, IBMBlade Center, and Sun ALOM servers must have SSH interfaces enabled.
- Dell iDrac 6 and DRAC 5 servers must have IPMI over LANenabled.
- Since authentication is attempted for every Default SP User, ensure that this list contains only those users necessary to discover your servers. If the number of Default SP Users is not limited, some servers will lock out the discovery process after too many failed attempts.
To set discovery time interval:
1. Click the SP tab, then click SP in the top navigation bar.
2. Select Discovery Setting.
3. In the Time Interval field, type the value of minutes for the time interval.
4. Click Apply.
NOTE: The time interval is only used for the automatic discovery. The value of the time interval may be between 5 and 65535 minutes. The preset value is 30 minutes.
To discover SPs:
1. Click the SP tab, then click SP in the top navigation bar.
2. Select Discovery Setting, then click Edit next to the IP address range you wish to modify.
3. In the Subnet Edit window, define the range of IP addresses that will be searched during discovery.
4. Select either of the following start modes:
For the MergePoint SP manager to automatically search for SPs in the specified IP address range at the specified time interval, select Automatic. If you wish to repeat the discovery sooner, click the Start link next to the IP address range.
- or -
If you want the MergePoint SP manager to search for SPs in the specified IP address range one time, select Manual.
5. Click Apply.
6. (Recommended for best system performance) Once all SPs are discovered, click Stop to end the automatic discovery process.
Chapter 2: Installation and Setup 35
If you enabled automatic management (see Automatically Manage SPs on page 34), then discovery results are displayed in the Managed SPlist. Otherwise, discovery results are displayed in the Unmanaged SPlist. See Managed and Unmanaged SP Lists (Admin users only) on page 38.
Manually Adding a Single SP
If you already know the IP address of an SP, you may add it manually. In addition, you can require verification of a specified username and password when a user connects to the SP. Added SPs are displayed in the Managed SP list. A green checkmark indicates a verified SP, while a red X indicates an unverified SP. After SPs are added, the number of in use and free licenses is re-calculated.
To manually add an SP:
1. Click the SP tab, then click SP in the top navigation bar. The SP window appears.
2. Click Manually Add SP. The Manually Add SP window appears.
3. In the IP field, type the IP address of the new SP.
4. In the Alias field, type the alias for the new SP.
5. If you want to require a username and password when connecting to the SP, select Verify
username and password.
a. To use the preset credentials configured by the manufacturer, select Use default
username and password.
- or ­To use a new username and password, select Do not use default username and password and enter the username and password in the corresponding fields.
b. Select or deselect Data Buffering as desired. [To set SoL data buffering size, see
Configuring the MergePoint SP Manager System Settings (Admin Users Only) on page 46].
-or-
If you do not want to require a username and password when connecting to the SP, select Don’t verify username and password. You may specify the username and password in the corresponding fields for accessing other functions.
NOTE: If Verify username and password is selected, the username and password are checked when adding an SP and the Serial over LAN (SoL) session starts automatically. If Verify username and password is deselected, the username and password are not checked when adding an SP and the SoL session is not started.
NOTE: From the SP Profile drop-down menu, select the SP profile of the new SP.
6. (Optional) In the KG field, type the BMC key.
36 MergePoint® SP Manager Installer/User Guide
NOTE: The KG field only appears when you select IPMI from the SP Profile drop-down menu. A BMC key is required by IPMI 2.0 and RMCP+ (Remote Mail Checking Protocol).
7. (Optional) From the Cipher drop-down menu, select a value for the new SP.
NOTE: The Cipher drop-down menu only appears when you select IPMI(HP), IPMI(IBM), IPMI(Dell), FTS iRMC or FTS iRMC S2 from the SP Profile drop-down menu.
8. (Optional) From the Group Name drop-down menu, select a group for the new SP. The target device will be listed in the group folder in the side navigation bar.
9. From the SoL access type drop-down menu, select the SoL access type for the new target device.
NOTE: The SoL accesstype drop-down menu onlyappears when you select iLO from the SP Profile drop-down menu.
10. Click Apply. Discovery results are displayed in the Managed SP list in the SP window.
The settings of an SP can be modified on the Properties page of the SP. For more information, see Changing SP parameters on page 70.
NOTE: When an SP with a directcommnd-only SP profile is added to the MergePoint SP manager, a username and password is not required. In this case, you are not permitted to edit username and password related settings or require SP verification.
NOTE: The MergePoint SP manager connects an IBM RSA II SP through the Telnet protocol. Whenever an RSA II SP is managed by a MergePoint SP manager, one Telnet session remainsopen in the background for the SoL connection. A maximum of 2 concurrent Telnet connections may be open to an RSA II SP. To prevent session conflicts, you are not permitted to add a managed RSA II SP to another MergePoint SP manager.
Adding blade chassis and blades
You can manually add a blade chassis, such as an IBM BladeCenter, as an SP by entering the IP address of the blade chassis (see Manually Adding a Single SP on page 36). A blade chassis is server architecture that houses multiple server modules (blades) in a single chassis. The chassis provides the power supply and may have its own service processor, while each blade it contains may also have its own service processor.
When adding a blade chassis, all of its blades are added simultaneously if the following conditions are met:
You specified that a verified username and password is required
The username and password were successfully verified by the appliance
Adequate free licenses for each blade are available
Chapter 2: Installation and Setup 37
If these conditions are not met, only the blade chassis is added and the blades are not available. If more licenses are needed, you can first acquire the additional licenses and then click Resync to add the blades under the blade chassis.
Or, if an individual blade contains a supported service processor, you can add it to the MergePoint SP manager separately. In this case, the blade operates as an independent SP, not a subset of the blade chassis SP.
Managed and Unmanaged SP Lists (Admin users only)
If you enabled automatic management (see Automatically Manage SPs on page 34) or manually added an SP, then the service processors are displayed in the Managed SPlist. Otherwise, discovery results are displayed in the Unmanaged SPlist. You may add a service processor to the Managed SP list at any time, provided there is a free license. When you manage an SP, you can require verification of a specified username and password when a user connects to the device.
If the managed SP is part of a group or groups, it is displayed in the side navigation bar as part of the group folder(s).
NOTE: Users that do not have Administrator access will only see devicesto which they have access.
For most SPs, you can view the type of SPs from the SP Profile column in the Managed/Unmanaged SP list. In a few cases, the SP profiles cannot be recognized until the SPs are managed and verified. See the following table for details.
SP Profile Display SP Profile - Unmanaged
Display SP Profile -
Managed (Unverified)
Display SP Profile –
Managed (Verified)
DELL 10G IPMI2.0 IPMI 2.0 Dell 10G
HP IPMI IPMI2.0 IPMI 2.0 IPMI(HP)
Table 2.5: SP Profiles Displayed in the Managed/Unmanaged SP Lists
To add an SP to the Managed SP list:
1. Click the SP tab, then click SP in the top navigation bar. The SP window appears.
2. In the Unmanaged SP list, select the SP you wish to add and click Manage. The Input SP window appears.
3. If you want to require a username and password when connecting to the SP, select Verify
username and password.
38 MergePoint® SP Manager Installer/User Guide
a. To use the preset credentials configured by the manufacturer, select Use default
username and password.
- or ­To use a new username and password, select Do not use default username and password and enter the username and password in the corresponding fields.
b. Select or deselect Data Buffering as desired. (To set SoL data buffering size, see
Configuring the MergePoint SP Manager System Settings (Admin Users Only) on page
46).
-or-
If you do not want to require a username and password when connecting to the SP, select Don’t verify username and password. You may specify the username and password in the corresponding fields for accessing other functions.
NOTE: If Verify username and password is selected, the username and password are checked when adding an SP and the Serial over LAN (SoL) session starts automatically. If Verify username and password is deselected, the username and password are not checked when adding an SP and the SoL session is not started.
4. (Optional) Select Group Name. From the Group Name drop-down menu, select a group for the new SP. The SP appears in the group folder in the side navigation bar.
5. Click Apply.
NOTE: SP settings can be modified on the Properties page. For more information, see Changing SP parameters on page 70.
To delete an SP from the Managed/Unmanaged SP list:
1. Click the SP tab, then click SP in the top navigation bar. The SP window appears.
2. In the appropriate SP list, select the SP you wish to delete and click Delete.
NOTE: When a managed SP is deleted, a license is set free. The number of in use and free license is re-calculated.
To remove an SP from the side navigation bar:
1. In the side navigation bar, click an SP name.
2. Click the Properties tab.
3. In the top navigation bar, click Target. A window displaying SP information appears.
4. Click Remove. When prompted, confirm the remove action. The selected SP is removed from the side navigation bar.
To add an SP to a group:
1. In the side navigation bar, click an SP name.
Chapter 2: Installation and Setup 39
2. Click the Properties tab.
3. In the top navigation bar, click Target. A window displaying SP information appears.
4. To add the SP to a group, click Copy To. From the Group drop-down menu, select a group. The SP is added to the new group and remains in the current group.
-or-
To move the SP to a new group, click Move To. From the Group drop-down menu, select a group. The SP is added to the new group and removed from the current group.
5. Click Apply.
Managing SP Groups (Admin users only)
You may create groups for managed SPs, which allows you to perform operations on all devices in a group at the same time. You may create an unlimited number of groups, and the same SP may be a part of multiple groups.
A default SP group with the same name as the MergePoint SP manager alias is automatically created for you. In the side navigation bar, the appliance, SPs and SP groups are displayed in the explorer tree according to hierarchy. Group folders and SPs that are part of the appliance alias group are displayed one level below the MergePoint SP manager. SPs that are members of groups are displayed one level below the corresponding group folder.
To add a new SP group:
1. Click the SP tab, then click Groups in the top navigation bar.
2. Click Add.
3. In the Group Name field, type a name for the group, then click Apply.
To modify an SP group name:
1. Click the SP tab, then click Groups in the top navigation bar.
2. In the Group list, click the name link you wish to modify.
- or -
Click a group name from the explorer tree in the side navigation bar, click Configuration in the top navigation bar, then click Modify Name.
3. In the Group Name field, type a name for the group, then click Apply.
To delete an device group:
1. Click the SP tab, then click Groups in the top navigation bar.
2. In the Group list, select the group you wish to delete, then click Delete.
40 MergePoint® SP Manager Installer/User Guide
- or -
Click a group name from the explorer tree in the side navigation bar, click Configuration in the top navigation bar, then click Delete.
To add a managed SP to an SP group:
1. Click the SP tab, then click SP in the top navigation bar.
2. In the Managed SP list, select the SP you wish to add to a group, then click Add SP to Group.
3. From the Group Name drop-down menu, select the group to which you wish to add the SP, then click Apply.
To configure SP group actions:
1. Click System - Setting.
2. Enter the number of SPs to power on simultaneously in a group.
3. Enter the time interval in seconds to elapse between power on each SP in a series of grouped SPs.
4. Enter the number of SPs to turn off simultaneously in a group.
5. Enter a command delay to turn off units in a series (seconds).
6. Click Apply.
Managing SP Profiles (Admin users only)
The MergePoint SP manager supports two types of SP profiles: default and user. Default SP profiles define 18 default profiles of SPs, while user SP profiles define new SP profiles. The Admin user can view the settings of the default SP profiles and create, modify or delete a user SP profile. You may need to create a new SP profile if an SP does not work properly with any of the default SP profiles.
The SP profile provides parameters, values or functions of SPs, such as:
Protocol: used for communications between the MergePoint SP manager and SPs.
Family: contains a list of pre-defined SP profiles and customX (X=1, 2, 3) SP profiles.
NOTE: The customX family needs a new Expect script which has been created using the name talk_customX.exp. (For more on creating new Expect scripts, see Profile Configuration on page 206.
Command Template: contains a list of templates for SP profiles. You may create a new template by clicking SP Templates Configuration. A MindTerm session will activate the sptemplate utility. See To use the sptemplate utility to create a new template: on page 211.
Chapter 2: Installation and Setup 41
The new template is added to lists of command templates and becomes available for using when configuring SPs. The following SP profiles do not need a template:
IPMI SPs.
SPs being configured only for Native IP access.
SPs being configured only for DirectCommand access.
DirectCommand Options: contains values to be used when DirectCommand is launched. The DirectCommand feature allows transparent access to native TCP services on an SP, such as a Virtual Media interface or a native KVM implementation. You may configure up to 20 TCP service ports to set up port forwarding for DirectCommand.
When adding a new SP, an Admin user should follow the procedure under To find out if an existing command template works with a new SP: on page 210to see if one of the default command templates works with the new SP. If not, an Admin user can use the MergePoint SP manager to either modify an existing user SP profile or create a new one.
To configure a new SP profile:
1. Click SP - SP Profiles.
2. In the User SP Profiles area, click Add.
3. In the SP Profile window, specify the name, protocol, family and SP template for the new SP profile.
NOTE: SP profile names may only contain letters and numbers. Special characters, such as a space or slash, are not permitted.
NOTE: The SP template for the profile must be the same template used for the familyyou chose. New SP templates that you create will appear here. For more information, see To use the sptemplate utility to create a new template: on page 211
4. Configure the DirectCommand parameters for the accessing the web interface of the SP profile by selecting a web scheme of http or https, entering a web port and entering the web address.
5. Configure TCP parameters for accessing TCP service on the new SP profile:
a. In the TCP Port field, type the TCP service port you want to access.
b. In the Description field, type the description of the service you are configuring.
c. In the Warning drop-down menu, select Yes or No.
NOTE: You may configure up to 20 TCP ports.
6. Click Apply. The new SP profile will be displayed in the User SP Profiles list.
42 MergePoint® SP Manager Installer/User Guide
To view the settings of the default SP profiles:
1. Click SP - SP Profiles.
2. Select the desired SP profile in the Default SP Profiles area.
To delete user SP profiles:
1. Click SP - SP Profiles.
2. In the User SP Profiles list, select the SP profile you wish to delete and click Delete.
To modify a user SP profile:
1. Click SP - SP Profiles.
2. In the User SP Profiles list, click the name link for the SP profile you wish to modify and enter the new information.
3. Click Apply.
Managing Default Users (Admin users only)
To perform management operations through a MergePoint SP manager, a username and password are required to access the SP. To simplify the authentication process, you may configure a default username and password for specific SPs. When a management operation is requested, the MergePoint SP manager searches the entire list of default usernames to see if there is an appropriate one for accessing the SP. You may create multiple entries of the same username with a different password for each. One preset username and password for each type of SP is created by default.
Type Username Password
IPMI 1.5 admin admin
IPMI 2.0 admin admin
IBM RSA II USERID PASSW0RD
IBM BladeCenter USERID PASSW0RD
DELL DRAC 3 root calvin
DELL DRAC 4 root calvin
Table 2.6: Default Service Processor Usernames
and Passwords
Chapter 2: Installation and Setup 43
Type Username Password
DELL DRAC 5 root calvin
DELL 10G root calvin
HP IPMI admin admin
HP iLo1 admin opensource
HP iLo2 [no default] [no default]
SUN iLom root changeme
SUN Alom admin admin
Fujitsu Siemens iRMC admin admin
DELL DRAC MC root calvin
DELL iDRAC SP root calvin
DELL m1000e CMC root calvin
HP BladeCenter Administrator admin
SUN ELOM root changeme
Fujitsu Siemens iRMC S2 root password
NOTE: Thisfeature is not supported on target devicesequipped with iLO.
NOTE: The maximum number of default SP users is eight.
NOTE: Do not use reserved words for usernames. Reserved words that have special meaning for the MergePoint
SP manager are listed in Managing MergePoint SP Manager User Accounts on page 29.
To add a default user:
1. Click SP - Default SP User - Add.
2. Specify the information for the default SP user and click Apply.
To delete a default user:
1. Click SP - Default SP User.
2. Select the user you wish to delete and click Delete.
44 MergePoint® SP Manager Installer/User Guide
To edit a default user:
1. Click SP - Default SP User.
2. Click the username you want to modify.
Managing user accounts on SPs
The Users window lists all user accounts for the selected SP. MergePoint SP manager users with Admin privileges may change user account information on SPs.
NOTE: Thisfeature is available for SPs that have user management functions. Different types of deviceshave different user management systems. For example, while some may allow adding, editing and deleting user accounts, others may only allow editing user accounts.
To edit a user account:
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click Users.
4. Click the name of the user you want to modify or the Edit link next to the user.
5. Enter the desired changes, then click Apply.
To create a new user account:
NOTE: Some SPs support limited users. In thiscase, you are not able to add a new line of user information.
However, you may create a new user account by defining a username, password and user privilege to a user that does not have a username.
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click Users.
4. Click Add or click Edit next to a user without a username.
5. Enter the desired changes, then click Apply.
To remove a user account:
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click Users. The Users window appears.
4. Select the user to be deleted and click Delete.
-or-
Chapter 2: Installation and Setup 45
Click Remove User next to the user you wish to remove.
NOTE: The line of the removed user will not disappear from the user list. Instead, it will become a user without a username that has Guest user privilege (no matter which user privilege it had before).
Configuring the MergePoint SP Manager System Settings (Admin Users Only)
To change the MergePoint SP manager alias:
1. Click System - Setting.
2. In the Alias field, type the new name for the MergePoint SP manager and click Apply.
To set target BMC time (for IPMI SPs only):
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, select Time. The Set Time window appears.
4. To synchronize the BMC time with the appliance time clock, select Sync with Appliance.
-or-
To synchronize the BMC time with the console time clock, select Sync with Client PC.
-or-
To specify the BMC time, select Other and select the time from the pop-up calendar.
5. Click Apply.
To set the session time interval and SoL history size:
1. Click System - Advanced Setting.
2. Input the desired settings in the fields provided and click Apply.
NOTE: The minimum session time interval is 600 seconds (10 minutes) and the maximum is 18,000 seconds (5 hours). The maximum SoL buffer size is 2 GB.
To set the MergePoint SP manager time:
1. Click System - Advanced Setting.
2. Select Synchronize with Client PC to synchronize the MergePoint SP manager time with the client PC.
- or -
Select Other and specify the MergePoint SP manager time from the pop-up calendar.
3. Click Apply.
46 MergePoint® SP Manager Installer/User Guide
To set the Internet time server:
1. Click System - Advanced Setting.
2. In the Internet time server field, enter the Internet time server address.
3. (Optional) Click Update Now to immediately synchronize the MergePoint SP manager with the Internet time server.
4. (Optional) Select Automatically synchronize with an Internet time server to synchronize the MergePoint SP manager with the Internet time server every 36 hours.
5. Click Apply.
To set MergePoint SP manager time zone:
1. Click System - Advanced Setting.
2. Select a time zone other than Custom from the Appliance Time Zone drop-down menu.
3. Click Apply.
NOTE: The Appliance Current Time field displays the current appliance time in the localtime zone, based on the time zone location settings on your client PC. If you change the MergePoint SP manager time zone, but do not change any other time settings such as the appliance time or client PC time zone, the Appliance Current Time is not affected and the value in the field does not change.
To configure the MergePoint SP manager for a customized time zone:
1. Click System - Advanced Setting.
2. Select Custom from the Appliance Time Zone drop-down menu.
3. Click Edit Custom.
4. In the Timezone name field, type the name of the time zone.
5. In the Standard Time Acronym field, type a standard acronym for the time zone.
6. In the GMT offset drop-down menu, select the GMT offset.
7. (Optional) Select Enable daylight saving time if you would like to configure the MergePoint SP manager with DST.
a. In the DST Acronym field, type the daylight saving time (DST) acronym of your
choice.
b. In the Saving time drop-down menu, select the number of hours and minutes in the
HH:MM format. The clock will be reset at the beginning of the daylight saving time period.
Chapter 2: Installation and Setup 47
c. In the DST start fields, select the start dates of daylight saving time from the pop-up
calendar.
d. In the DST end fields, select the end dates of daylight saving time from the pop-up
calendar.
8. Click Apply.
To enable or disable the Telnet or SSH protocol:
1. Click System - Setting.
2. Select or deselect Telnet or SSH to enable/disable the respective protocol.
3. Click Apply.
NOTE: (For the MergePoint SP5x24/SP5x40 manager ONLY) In some cases, such as soon after an upgrade, enabling the SSH protocol may be delayed while the service processor initiates.
Completing the MergePoint SP Manager Installation
Whatever method is used to enable access to the web interface, the root user should always log into the MergePoint SP manager console and change the password from the default. The admin user cannot change the root user password, and the root user cannot log into the web interface to change the root password. The following options are available:
Until an IP address is available for the MergePoint SP manager, the root user can only change the root user password by logging in locally through the console port.
After an IP address is available for the MergePoint SP manager, the remote root user can use SSH to connect to the console and log in from a remote location and change the password.
48 MergePoint® SP Manager Installer/User Guide
Operations
3
49
The operations in this chapter are performed using the MergePoint SP manager web interface. For instructions on using the MergePoint SP manager with DSView 3 software, please see the DSView 3 Software Installer/User Guide.
When the MergePoint SP manager is selected in the side navigation bar, a line of tabs and sub­tabs appears in the tab bar. They vary according to the user access level. For users without administrator access, only the SP, Users and Alerts tabs are available.
SP: Used to display and manage discovered SPs.
System: Used to define or change MergePoint SP manager settings.
Network: Used to configure MergePoint SP manager network settings.
Users: Used to manage MergePoint SP manager user accounts.
Alerts: Used to view, query and activate system alerts.
Accounting Log: Used to view all MergePoint SP manager operations.
Diagnostic: Used to collect all network packets between an SP and a MergePoint SP manager for troubleshooting and problem resolution.
Using the MergePoint SP Manager
The operations described in this chapter are performed through the MergePoint SP manager web interface. For installations involving multiple MergePoint SP managers, the same functions can be accessed through the DSView 3 software. For information on using the DSView 3 software with the MergePoint SP manager, please see the DSView 3 software installer/user guide and the online help for the MergePoint SP manager plug-in.
MergePoint SP manager web interface
You can connect to the MergePoint SP manager web interface using any of the following web browsers or their later releases: Internet Explorer 6.0 SP1 or later, Internet Explorer 7, Firefox 2.0
or later, Mozilla 32-bit version 1.7.3 or later, or Mozilla 64-bit.
To access the MergePoint SP manager web interface:
1. Open a web browser and enter the IP address of the MergePoint SP manager.
2. Enter your username and password and click Login.
NOTE: When following any of the MergePoint SP manager configuration procedures in this document, start by clicking the name of the MergePoint SP manager in the side navigation bar. Click Apply to save changes. To cancel changes, clickBack to return to the previous screen or clickanother navigation element, such as the name of a tab, window or target.
Figure 3.1: MergePoint SP Manager Web Interface
50 MergePoint® SP Manager Installer/User Guide
Number
Window
Area
Description
1
Top
Option Bar
Use the top option bar to log out or access online help. If any alerts occur, a yellow icon is
displayed. The name of the logged in user appears on the left side of the top option bar.
2
Side
Navigation
Bar
Use the side navigation bar to select the appliance or SPs and access or edit
corresponding information in the content area.
3 Tab Bar
Use the tab bar to displayand manage the MergePoint SP manager, managed groups
and SPs.
4
Top
Navigation
Bar
The selections in the top navigation bar vary, depending on the active tab in the tab bar.
5
Content
Area
The content area displays information relative to your selectionsand allows you to make
changes to the MergePoint SP manager, managed groups or SPs.
Table 3.1: MergePoint SP Manager Web Interface Descriptions
Remote Power and Chassis Management
Using the MergePoint SP manager, you may view the power status and the status of the chassis indicator LED (if available) on managed target devices, manage power and turn the LED on and off remotely. You may also initiate cold reset and BMC self test operations on certain types of SPs.
The effects of Power Off and Power Cycle commands differ among service processor vendors. For a hard power command, power is turned off immediately, while a soft command shuts down the operating system before turning off the SP. If a service processor provides more than one of the options, the MergePoint SP manager performs the hard power option by default.
The options for the reset command also differ, and are defined as warm reset and cold boot. For a warm reset, only the operating system is restarted while a cold boot issues a power cycle command. In cases where both options are available, the MergePoint SP manager will use cold boot.
NOTE: In addition, for Dell 10G SPs, you can view power tracking statistics and peak statisticsby clicking Power Monitoring.
To view and control the power status:
1. In the side navigation bar, click an SP name.
Chapter 3: Operations 51
2. Click the System tab.
3. In the top navigation bar, click Power. The Power Information window appears and displays the current power status of the target device.
4. Following the instructions on the page, select the desired power action: Power On, Power Off, Graceful Shutdown, Power Reset, Power Cycle and Soft Reset.
To monitor power for a Dell 10G SP:
1. In the side navigation bar, click an SP name.
2. Click the System tab.
3. In the top navigation bar, click Power Monitoring.
NOTE: Make sure the correct SP profile is selected for the Dell 10G SP; otherwise, the Power Monitoring tab is not visible. To modify the SP profile, see Changing SP parameters on page 70.
To turn on, turn off or reset all selected SPs:
1. Click the SP tab, then click SP in the top navigation bar. The SP window appears.
2. In the Managed SP list, select the SP(s) you wish to manage and click the desired power operation.
To view and control the chassis status (LED):
1. In the side navigation bar, click an SP name.
2. Click the System tab.
3. In the top navigation bar, click Chassis. The Chassis Information window appears and the current chassis status of the target device is displayed.
4. To modify how often the LED flashes, enter the number of seconds in the Indicator ON Seconds field.
5. To change the chassis indicator status of the target device, complete any of the following steps:
To turn the LED on and leave the LED flashing for a specified number of seconds, click Indicator On Seconds. The LED flashes for the time specified in the Indicator On seconds field.
- or -
To turn the LED on and leave the LED flashing permanently, click Indictor On.
- or -
To turn the LED off, click Indicator Off.
52 MergePoint® SP Manager Installer/User Guide
6. Click Apply.
To perform a cold reset on an SP:
1. In the side navigation bar, click an SP name.
2. Click the System tab.
3. In the top navigation bar, click Advanced Tools. The Setting window appears.
4. Click Cold Reset to perform a cold reset on the selected SP. A message will appear to indicate the success status of the cold reset.
To reboot the MergePoint SP manager:
Click System – Setting - Apply Reboot.
NOTE: If the network setting mode is DHCP, when you reboot the appliance it attempts to obtain an IP address from the DHCP server. If a DHCP server is not present or is unavailable, the following IP address are automatically assigned: 192.168.0.10 for eth0 and 192.168.0.20 for eth1.
To shut down the MergePoint SP manager (Admin users only):
CAUTION: Clicking Shutdown immediatelystops all active servicesand sessions.
1. Select System - Setting, then click Shutdown.
2. (Optional) Wait one minute, or until you see the shutdown message in the console interface or hear a beeping noise, then unplug the appliance.
Performing SP Group Operations
Admin users may perform the following operations for all SPs in a group at the same time: turn on, turn off or reset the devices, turn the target device LED indicators on or off, and configure time, Platform Event Trap (PET) alert settings, usernames and passwords.
You can also move or copy SPs from one group to another, and remove SPs from a group.
NOTE: A group must contain at least one SP before you can perform a group operation.
To turn on, turn off or reset all SPs in a group:
1. Click SP - Group.
2. Select the group(s) you wish to modify and click the desired power operation.
- or -
Click a group name from the explorer tree in the side navigation bar, click Action in the top navigation bar, then click the desired power operation.
Chapter 3: Operations 53
To turn LED indicators on or off for all SPs in a group:
1. Click SP - Group.
2. Select the group(s) you wish to modify and click the desired indicator state.
- or -
Click a group name from the explorer tree in the side navigation bar, click Action in the top navigation bar, then click the desired indicator state.
To set the time for all SPs in a group:
1. Click SP - Group.
2. Select the group(s) you wish to modify and click Set Time.
- or -
Click a group name from the explorer tree in the side navigation bar, click Action in the top navigation bar, then click Set Time.
3. To synchronize the SPs with the MergePoint SP manager time clock, select Synchronize with Appliance.
-or-
To synchronize the SPs with the client PC time clock, select Synchronize with Client PC.
-or-
To specify the time, select Other and select the time from the pop-up calendar.
4. Click Apply.
To change the PET alert settings for all SPs in a group:
1. Click SP - Group.
2. In the Group list, select the group(s) you wish to modify and click PET Setting.
- or -
Click a group name from the explorer tree in the side navigation bar, click Action in the top navigation bar, then click PET Setting.
3. Perform any of the following steps:
a. Enable or disable Send Alerts. Enabling this function allows the BMC to send alerts
when events occur.
b. In the Community String field, type the value that will be displayed in the PET trap
community string field.
54 MergePoint® SP Manager Installer/User Guide
c. Type up to four IP addresses in the Alert Destination IP Address fields.
NOTE: To allow the MergePoint SP manager to receive alerts from the SP, one field should contain the IP address of the MergePoint SP manager.
4. Click Apply.
To set a user and password for all SPs in a group:
1. Click SP - Group.
2. In the Group list, select the group(s) you wish to modify and click Set User and Password.
- or -
Click a group name from the explorer tree in the side navigation bar, click Action in the top navigation bar, then click Set User and Password.
3. Enter the requested information and click Apply.
To manage SP groups:
1. Click a group name from the explorer tree in the side navigation bar.
2. Select the SP(s) you wish to copy or move.
3. Click the corresponding button and follow the on-screen instructions.
Monitoring and Management
Viewing sensor status
The MergePoint SP manager can detect the status of fan, temperature and voltage sensors on managed SPs. By clicking the Sensor tab, you may view a detailed report of a device’s sensors that includes the sensor name, type, current reading and status.
NOTE: For some types of SPs, you can change a temperature scale to view sensor information.
To view sensor status:
1. In the side navigation bar, click an SP name.
2. Click the Sensor tab.
3. In the top navigation bar, click Sensor. The Sensor window and a detailed list of sensors and corresponding information appears.
Viewing SEL events
You may use the MergePoint SP manager to view the SEL (System Event Log) on a managed SP.
Chapter 3: Operations 55
To view SEL events:
1. In the side navigation bar, click an SP name.
2. Click the SEL tab.
3. In the top navigation bar, click SEL. The SEL window and a detailed SEL event list appears.
To clear the SEL events:
1. In the side navigation bar, click an SP name.
2. Click the SEL tab.
3. In the top navigation bar, click SEL. The SEL window appears.
4. Click Clear All. All currently listed events are removed from the list.
Viewing IML events
You may use the MergePoint SP manager to view the IML (iLO Management Log) on a managed iLO SP.
To view IML events:
1. In the side navigation bar, click an iLO SP name.
2. Click the IML tab.
3. In the top navigation bar, click IML. The IML window and a detailed IML event list appears.
To clear the IML events:
1. In the side navigation bar, click an iLO SP name.
2. Click the IML tab.
3. In the top navigation bar, click IML. The IML window appears.
4. Click Clear All. All currently listed events are removed from the list.
Viewing the accounting log
The accounting log records and displays all MergePoint SP manager operations. The WEB accounting log displays operations performed using the MergePoint SP manager web interface. The Mgpshell accounting log displays operations performed using Mgpshell. Detailed information including operation time, login username, operation type, SP and console IP are displayed in the accounting log.
56 MergePoint® SP Manager Installer/User Guide
To view the accounting log (Admin users only):
1. Click the Accounting Log tab.
2. Click WEB to view operations performed through the MergePoint SP manager web interface.
-or-
Click Mgpshell to view operations performed through the Mgpshell.
Import/export data
This function allows you to backup and restore the MergePoint SP manager by exporting the data to the client PC or a storage location on the network.
NOTE: See the MergePoint SP manager release notes for more information about restoring data in MergePoint SP manager.
To export data from the MergePoint SP manager (Admin users only):
1. Click the System - Import/Export.
2. Click Export. All MergePoint SP manager data will be compiled and a download link will appear next to the Export button.
3. Click download to save the data file to the desired location.
To import data to the MergePoint SP manager (Admin users only):
1. Click System - Import/Export.
2. In the Filename field, type the path to the file you wish to import or click Browse to locate the file.
3. Click Import to restore the data in the file to the MergePoint SP manager.
Accessing FRU information
The MergePoint SP manager can find and display some Field Replaceable Unit (FRU) information for the selected SP, including chassis type, board language code and product name.
NOTE: Not all service processors support or log FRU information. If the FRUinformation report does not appear, ensure that the server manufacturer supports and/or has logged F RUdata.
To retrieve FRU information:
1. In the side navigation bar, click an SP name.
2. Click the Properties tab.
Chapter 3: Operations 57
3. In the top navigation bar, click FRU Information. A detailed FRU information report appears.
Using the Alerts Viewer
The MergePoint SP manager logs user-defined alerts that occur on managed SPs in the Alert Viewer window. You may configure the MergePoint SP manager to send a notification by email, MSN, SNMP Forward or Yahoo! message when specific alerts occur.
The Alerts Viewer window displays alerts and the corresponding date/time, source, IP address, event type and severity level. Alerts set as read will be listed in black; alerts not set as read will be listed in red. Click Detail next to an alert to view additional information.
To locate specific alerts, you may specify parameters to query the list of alerts. Users can also search alert messages through a query analyzer. The query parameters include occurrence period, IP address, event type, severity level and read status.
Setting an alert action
You may create an alert action by configuring action parameters to your specifications. You may also configure the MergePoint SP manager to send email, MSN messages or Yahoo! messages to specific users, or forward SNMP messages to specific SNMP trap browsers or management software once an alert occurs.
Before creating an alert action, configure the action settings to allow for alert notifications.
To configure action settings (Admin users only):
1. Click the Alerts tab.
2. In the top navigation bar, click Action.
3. Click Action Setting.
4. Specify the following parameters:
a. In the SMTP Server field, type the Simple Mail Transfer Protocol (SMTP) server
address for sending email.
b. In the SMTP Server Account field, type the account used as the email sender.
c. In the SMTP Server Password field, type the password for the SMTP server account.
d. In the SMTP Sender field, type the display name of the email sender.
e. In the MSN User field, type the MSN account used as the MSN message sender.
f. In the MSN Password field, type the password for the MSN user.
58 MergePoint® SP Manager Installer/User Guide
g. In the YAHOO IM User field, type the YAHOO IM account used as the YAHOO IM
message sender.
h. In the YAHOO IM Password field, type the password for the YAHOO IM account.
5. Click Apply.
To create an alert action (Admin users only):
1. Click the Alerts tab.
2. In the top navigation bar, click Action.
3. Click Add.
4. In the Action Configuration area, specify the following information:
a. Select the Action Type from the drop-down menu: Email, MSN, YAHOO or SNMP
Forward.
b. If you selected Email, type the email address of the receiver in the Email Address field.
-or-
If you selected MSN, type the MSN account of the receiver in the Email Address field.
-or-
If you selected SNMP Forward, type the IP address of the destination machine in the Receiver field.
-or-
If you selected YAHOO, type the YAHOO IM account of the receiver in the YAHOO field.
5. Click Apply.
To delete an alert action (Admin users only):
1. Click the Alerts - Action.
2. From the list, select the action(s) you wish to delete and click Delete.
To query an alert (for all users):
1. Click the Alerts tab.
2. In the Alert Viewer area, select Show Alert Query.
3. In the Alert Query area, specify any or all of the following parameters for the query:
a. Select Period From to enable date range fields.
Chapter 3: Operations 59
b. In the Period From and To fields, type the date range for the alerts you wish to be
included in the query results. The default value of the To field is the current date.
c. From the IP address drop-down menu, select either All or a specific IP address for the
SPs you wish to be included in the query results.
d. From the Severity drop-down menu, select the severity of the alerts you wish to be
included in the query results: All, Specified, Monitor, Information, OK, NonCritical, Critical or Non-Recoverable.
e. From the Read Status drop-down menu, select the read status of the alerts you wish to
be included in the query results: All, Read or Unread.
4. Click Query to search the alerts. The qualifying alerts will be displayed in a list below the Alert Query area.
To set an alert as read (Admin users only):
1. Click the Alerts tab.
2. From the list, select the unread alerts you wish to modify.
3. Click Set Selected Read to mark the selected alerts as read. The alerts change from red to black text to indicate the read status.
To delete an alert (Admin users only):
1. Click the Alerts tab.
2. From the list, select the alerts you wish to delete.
3. Click Delete Selected to remove the alerts from the Alerts Viewer list.
Syslog
The Admin user can set up logging of messages about the following types of events:
Events of interest from the MergePoint SP manager
Events of interest obtained by filtering data during device console connections with connected devices
Sensor alarms generated by sensors on SPs
Messages can be sent to a user defined destination. Messages can also be sent to the console, the root user or both.
60 MergePoint® SP Manager Installer/User Guide
Message filtering levels
Messages can be filtered according to their severity, based on any or all of the levels from the following list.
0 - Emergency
1 - Alert
2 - Critical
3 - Error
4 - Warning
5 - Notice
6 - Info
7 - Debug
Configuring syslog messages
To configure syslog message filtering:
1. Click System - Syslog.
2. Select the link of the filter name which you want to modify.
3. Click the checkboxes next to the desired severity levels.
4. Click Apply to finish.
To configure the syslog destination:
1. Click System - Syslog.
2. In the System Destination area, select Console to send the system kernel log (such as [date] src_kernel@MergePoint ...or [date] scr_dev_log@MergePoint...) to the console.
-and/or-
Click Root user to send messages to the root user.
3. In the User Define Destination area, configure messages to be sent to a defined syslog server as follows.
a. Click Add.
b. In the Syslog Destination field, type a syslog server’s IP address.
c. Click Apply.
d. To add additional syslog servers, repeat steps a through c.
Chapter 3: Operations 61
NOTE: You can edit or delete syslog servers by selecting the corresponding destination and clicking Delete.
Configuring PET alerts
Users with Admin privileges may configure PET alerts separately for each SP.
To configure PET alerts:
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click Event Destination. The PET Setting window appears.
4. Select Enable or Disable for sending or not sending alerts when specific events occur.
5. In the Community String field, enter the value to be displayed in the community string field of the PET trap.
6. Enter up to four IP addresses in the Alert Destination IP Address fields.
7. Click Apply.
NOTE: To configure the MergePoint SP manager to receive alerts for the SP, make sure to enter the IP address of the MergePoint SP manager in one of the Alert Destination IP Address fields.
Schedules
Tasks can be scheduled to simultaneously turn on or off or reset the power on all SPs in a group. The results of each scheduled task display in the Schedule Task Result list in the Schedule Task window. To clear this list, click Clear All.
Schedule a task (Admin users only)
To schedule a task:
1. Click System - Schedules.
2. Click Add and select Group to display all SP groups or SPs to display all SPs.
3. Specify the following information:
a. Select the group(s) or SP(s) for which you wish to schedule tasks.
b. Type the task name into the Task Name field.
c. From the Operate drop-down menu, select: Power On, Power Off or Power Reset.
d. From the Schedule Task drop-down menu, select: Once, Daily, Weekly or Monthly.
62 MergePoint® SP Manager Installer/User Guide
e. From the Time menu(s), select the day, hour and minute for the task to occur. Options
in the Time menus vary according to your selections.
f. Choose Once, Daily, Weekly or Monthly, then specify the task schedule accordingly.
4. Click Apply.
To edit a scheduled task:
1. Click System - Schedules.
2. Click Edit next to the task you wish to edit and follow the on-screen instructions.
To delete a scheduled task:
1. Click System - Schedules.
2. Select the task to delete and click Delete.
SNMP Access
The SNMP agent provides access to the MergePoint SP manager through an SNMP management application, such as HP Openview, Novell NMS, IBM NetView or Sun Net Manager, and provides proxy access to SNMP data from connected service processors that implement SNMP agents.
NOTE: The SNMP agent can also be configured to send notifications (also known as traps) about significant events on the MergePoint SP manager and on SPs. See Using the Alerts Viewer on page 58.
The administrator must configure the SNMP agent to use the version of SNMP supported by the management application, SNMP v1, v2c or v3. The use of v3 is strongly encouraged wherever possible because it provides authentication and encryption of data that is lacking in v1 and v2c.
Access to information provided by the MergePoint SP manager and its proxy SPs can be obtained in either of the two following ways:
The recommended access method for agents which support only SNMP version 1 or 2c is through a proxy on the MergePoint SP manager. The MergePoint SP manager provides the authentication and encryption lacking in those protocol versions. The SNMP management application can then be used for SNMP management of the SP.
NOTE: Running the SNMP daemon (snmpd) on the MergePoint SP manager allows you to access the proxy data using the v1 and 2c protocolswithout going through a VPN tunnel. However, thismethod isinherently unsecure.
The access method agent which supports version 3 is via a local Net-SNMP daemon. The proxying of traps is not supported by Net-SNMP.
Chapter 3: Operations 63
If SNMP is used as recommended, no public client is allowed unauthenticated access to either managed clients or to the MergePoint SP manager. For compatibility with other clients, unencrypted transfer of data is possible with SNMP v3 connections, but strongly discouraged.
User and group information for v3 connections must be different from the user and group names used for accessing the MergePoint SP manager.
The administrator can configure the following:
General information provided by the MergePoint SP manager, including location and contact fields
Who has access to SNMP information
Configuring SNMP on the MergePoint SPmanager
The Admin user can configure SNMP access for the MergePoint SP manager by clicking Network - SNMP.
To configure the MergePoint appliance SNMP settings:
1. Click Network - SNMP.
2. In the SysContact field, type the contact information of the MergePoint SP manager administrator.
3. In the SysLocation field, type the location of the MergePoint SP manager.
4. Click Apply.
To configure views:
NOTE: Use the view settings to determine what information is shown when the SNMP request is returned. Multiple
views can be created. The views configured in this procedure for the MergePoint appliance are also used for the SNMP requests to the SP.
1. Click Network - SNMP.
2. In the View area, click Add, then enter a name for the view.
3. Select Include or Exclude from the drop-down menu to include or exclude the defined OID subtree.
4. Enter an OID for the object to be viewed and enter a mask to create an OID subtree in the fields provided. Repeat to create more OID subtrees as desired.
NOTE: If the OID is numeric, a prefixof a decimalpoint is required. For example, type .1.3 instead of 1.3.
5. Click Apply.
64 MergePoint® SP Manager Installer/User Guide
NOTE: You may edit or delete an existing view by clicking the view name linkand following the on-screen instructions.
To configure users with SNMP v3:
1. Click Network - SNMP.
2. In the Users area, click Add, then type a username.
3. Select an authentication method from the Auth method drop-down menu, then enter an optional authentication password.
4. Select an encryption method from the Encryption drop-down menu, then enter an optional encryption password.
5. Click Apply.
NOTE: You may edit or delete an existing user by clicking the username link and following the on-screen instructions.
To configure access settings for SNMP users:
Perform this procedure to configure how users on the public side authenticate themselves to the MergePoint SP manager.
1. Click Network - SNMP.
2. In the Access settings area, click Add.
3. From the SNMP version drop-down menu, select a version.
4. If either the v1 or v2c version is selected in step 3, perform the following steps:
a. In the Community field, type the public community name to be used by the external
SNMP application.
b. Select either Default or Use IP for the source.
NOTE: The Source field limits the IP address permitted to access the MergePoint SPmanager through SNMP. If Default is selected, any IP address can access the appliance, but if Use IP isselected, only the specified IP address can access the appliance.
c. If Use IP is selected, type a source IP address.
d. Select an appropriate view for the Read and Write view settings. If the list is empty, no
view has been configured; see To configure views: on page 64.
-or-
If the v3 version is selected in step 3, perform the following steps:
Chapter 3: Operations 65
a. Select a user from User drop-down menu. See To configure users with SNMP v3: on
page 65 for more information.
b. For each security level, select a read view and write view under the Read view and
Write view columns. If the list is empty, no view has been configured; see To configure views: on page 64.
5. Click Apply.
NOTE: You may edit or delete an existing access setting by clicking the Community/User link and then following the on-screen instructions.
Configuring SNMP on the service processor
The Admin user can configure SNMPaccess on SPs by selecting the SPand then selecting the Configuration - SNMPtab. If the SPdoes not support SNMP, the SNMPtab is not displayed on the SPconfiguration page.
To configure service processor SNMP settings:
NOTE: The following settings must match the SNMPconfiguration of the SP. The MergePoint SPmanager does
not automaticallyset or configure the SNMPsettings in the SP.
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click SNMP. The SNMP window appears.
4. In the OID field, type the identifier for the object to be managed. An OID may be provided for you as starting point, but ensure that the correct OID for the SPis entered in this field.
NOTE: If the OID is numeric, a prefixof a decimalpoint is required. For example, type .1.3 instead of 1.3.
5. From the SNMP version drop-down menu, select v1, v2c or v3. The version you select must match the version configured on and supported by the SP.
6. If you selected either v1 or v2c, type the community name in the Community field. When the MergePoint SPmanager receives SNMPrequests, the community name is used to identify the associated SP.
-or-
If you selected v3, enter the username required for authentication, the authentication method, the authentication password, the encryption method and, optionally, the encryption password in the fields provided.
7. Click Apply.
66 MergePoint® SP Manager Installer/User Guide
To configure SNMP access settings for an SP:
Perform this procedure to configure how users on the public side authenticate themselves to the MergePoint SP manager.
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click SNMP. The SNMP window appears.
4. In the Access settings area, click Add.
5. From the SNMP version drop-down menu, select a version.
6. If either the v1 or v2c version is selected in step 3, perform the following steps:
a. In the Community field, type the public community name to be used by the external
SNMP application.
b. Select either Default or Use IP for the source.
NOTE: The Source field limits the IP address permitted to access the MergePoint SPmanager through SNMP. If
Default is selected, any IP address can access the appliance, but if Use IP isselected, only the specified IP address can access the appliance.
c. If Use IP is selected, type a source IP address.
d. Select an appropriate view for the Read and Write view settings. If the list is empty, no
view has been configured; see To configure views: on page 64.
-or-
If the v3 version is selected in step 3, perform the following steps:
a. Select a user from User drop-down menu. See To configure users with SNMP v3: on
page 65 for more information.
b. For each security level, select a read view and write view under the Read view and
Write view columns. If the list is empty, no view has been configured; see To configure views: on page 64.
7. Click Apply.
NOTE: You may edit or delete an existing access setting by clicking the Community/User link and then following the on-screen instructions.
Example
The following example describes a typical flow of SNMP requests.
Chapter 3: Operations 67
In an SNMP request to a SP from a client server, the SNMP request is issued to the MergePoint SPmanager public IP address. The request contains the unique community name as defined in the SPs access settings section (see To configure SNMP access settings for an SP: on page 67). Once the request is received, the MergePoint SPmanager initiates the same request to the SP using its own appliance IP address, which is either public or private depending on the network location of the SP, and using the community name as defined in the Service Processor SNMP setting window. (The community name must match the community name configured on the SP.) The SP must be configured with SNMP management applications pointing to the MergePoint SP manager's public or private IP address. When the response is received from the SP, the MergePoint SPmanager sends it back to the client server using the appliance's public IPaddress and the community name as defined in the access settings for the SP.
Accessing a service processor’s SNMP through the MergePoint SP manager
You can use third party utilities, such as “snmpwalk,” to access a service processor’s SNMP through the MergePoint SP manager. When using third party utilities, remember to add the context parameter (the service processor alias).
For example, you want to use the snmpwalk utility to access the SNMP of a MergePoint SP manager with an IP address of 172.26.25.99 and a community string of public158. The service processor alias is 172.26.25.158. To retrieve all SNMP information, enter the following command:
snmpwalk -v 1 -c public158 -n 172.26.25.158 172.26.25.99 .1.3.
The -n parameter is required prior to the service processor alias to specify which service processor you want to access.
NOTE: Visit www.net-snmp.org for more information about the snmpwalkutility.
SP Operations
NOTE: As noted throughout thissection, the available features vary according to the types of service processors.
For example, accessing system information is only available for IPMI, ILOM, HP IPMI, FTS iRMC, Dell iDRAC blade and Dell DRAC 5 devices; for other SPs, this feature cannot be viewed or accessed.
To perform any of these operations, access the MergePoint SP manager web interface. In the side navigation bar, click the name of the SP you wish to manage.
The following tabs are available:
Properties: Use this tab to access system information and FRU, change the alias and copy or move the SP to a group. For a blade chassis that is managed as an SP, you can synchronize the blades with the SP.
68 MergePoint® SP Manager Installer/User Guide
System: Use this tab to remotely perform system operations, including power, chassis and other advanced operations.
Configuration: Use this tab to remotely configure managed SPs, including changing LAN parameters, managing user accounts, configuring PET settings, configuring SoL, setting BMC time, performing provisioning recovery and setting up SNMP and Native IP.
SEL: Use this tab to view SP SEL information.
Sensor: Use this tab to view the sensor output from managed target.
System Sessions: Use this tab to activate and use SoL or the SP, Telnet, or SSH consoles for accessing managed SPs. You can also transparently access native TCP services on an SP through DirectCommand.
Remote Control: Use this tab to connect to Remote Desktop Protocol (RDP) and Virtual Network Computing (VNC) servers.
Viewing SP information
To view the SP information:
1. In the side navigation bar, click an SP name.
2. Click the Properties tab.
3. In the top navigation bar, click SP. A window displaying SP information appears.
Synchronizing blades for a blade chassis
NOTE: The following procedure is only for SPs with blade chassis.
To synchronize the blades:
1. In the side navigation bar, click an SP name.
2. Click the Properties tab.
3. In the top navigation bar, click SP.
4. Click Synchronize BladeCenter. The blades on the side navigation bar are synchronized with the selected SP.
Changing the SoL port number
To change the SoL port number:
1. In the side navigation bar, click an SP name.
2. Click the Properties tab.
3. In the top navigation bar, click SP.
Chapter 3: Operations 69
4. In the SoL Port field, type a SoL port number and click Apply.
Changing the access account of an SP
To change the access account of an SP:
1. Click the SP tab. The SP window appears.
2. In the Managed SP list, click the desired SP link.
3. In the Username and Password field, type the username and password you would like to use to access the SP.
4. Click Apply.
NOTE: For an unverified SP, you can select Verify the username and password to verify the SP with the username and password you enter.
Changing SP parameters
You can modify SP parameters, including username and password, verification status, SP profiles and SoL access.
To change SP parameters:
1. In the side navigation bar, click an SP name.
2. Click the Properties tab.
3. In the top navigation bar, click SP. A window displaying SP information appears.
4. Click Edit. The Edit SP window appears.
5. In the Alias field, type the new name for the SP.
6. For an unverified SP, if you want to require a username and password when connecting to the SP, select Verify username and password.
a. To use the preset credentials configured by the manufacturer, deselect Change
username and password.
- or ­To use a new username and password, select Change username and password and enter the username and password in the corresponding fields.
b. Select or deselect Data Buffering as desired. (To set SoL data buffering size, see
Configuring the MergePoint SP Manager System Settings (Admin Users Only) on page
46).
70 MergePoint® SP Manager Installer/User Guide
NOTE: If Verify username and password is selected, the username and password are verified when adding an SP and the Serial over LAN (SoL) session starts automatically. If Verify username and password is deselected, the username and password are not verified when adding an SP and the SoL session is not started.
For a verified SP, you may change the username and password in the corresponding fields for accessing other functions.
7. From the SP Profile drop-down menu, select the SP profile of the new SP.
NOTE: For more information on configuring SP profiles, see Managing SP Profiles (Admin users only) on page 41 and Profile Configuration on page 206.
8. From the SoL access type drop-down menu, select the SoL access type for the new iLO target device.
NOTE: Thisfield only appears when you select iLO from the SP Profile drop-down menu.
9. Click Apply.
NOTE: For an SP with directcommnd-only SP profile, a username and password is not required. In this case, the username and password fields and SP verification fields are not shown.
To BMC self test an SP:
1. In the side navigation bar, click an SP name.
2. Click the System tab.
3. In the top navigation bar, click Advanced Tools. The Setting window appears.
4. Click BMC Self Test to perform a BMC self test on the selected SP. A message will appear to indicate the success status of the self test.
Accessing system information
The MergePoint SP manager can find and display certain system information for the selected SP, including device ID, firmware version, IPMI version and manufacturer ID.
To retrieve system information:
1. In the side navigation bar, click an SP name.
2. Click the Properties tab.
3. In the top navigation bar, click Information. A detailed system information report appears.
Recovering provisioning
You can recover the original provisioning based on the configuration already in place at the SP.
Chapter 3: Operations 71
To recover provisioning for an SP:
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click Recover. The Provisioning Recover window appears.
4. Click Provisioning Recover.
NOTE: The Provisioning Recover button is only available after the provisioning on this SP is performed successfully and confirmed.
Changing LAN parameters
To change LAN parameters:
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click LAN. The LAN window appears.
4. From the IP Address Source drop-down menu, select Static or DHCP as the source type. If you select Static as the source type, specify the SP’s IP address, subnet mask and gateway IP address in the fields provided.
NOTE: If you select DHCP, the SP’s IP address is dynamicallydistributed from a DHCP server and the fieldsfor configuring a static IP cannot be edited.
5. Click Apply.
Host table
The host table is a simple text file that allows Admin user to associate IP addresses with hostnames and alias.
To change the host name of the MergePoint SP manager:
1. Select Network - Host Table.
2. Enter a host name for the MergePoint SP manager in the Name field.
3. Click Apply.
To add an entry:
1. Select Network - Host Table, then click Add.
2. Enter the required information in the fields provided, then click Apply.
72 MergePoint® SP Manager Installer/User Guide
To edit an entry:
1. Select Network - Host Table.
2. Click the IP address link of the entry you would like to edit and follow the on-screen instructions.
To delete an entry:
1. Select Network - Host Table.
2. Select the entry(s) you would like to delete and click Delete.
Static routes
Admin users can use the Static routes feature to manually add, edit or delete existing static routes.
To add a static route:
1. Click Network - Static Routes.
2. Click Add.
3. In the Network Address field, type a network IP address of the destination host or specify a network in the form networkIPaddress/mask_length (also referred to as prefix/length).
4. From the Type drop-down menu, select Interface or Gateway as you desire.
5. If you select Interface, then choose an interface from the Interface/Gateway drop-down menu.
-or­If you select Gateway, then in the Interface/Gateway field, type the IP of the gateway.
6. In the Metric field, type the number of hops to the destination.
7. Click Apply.
NOTE: To set a default route, select Network - Network Settings.
To edit a static route:
1. Click Network - Static Routes.
2. Click the network address link of the static route you want to edit and follow the on-screen instructions.
To delete a static route:
1. Click Network - Static Routes.
2. Click the network address link of the static route you want to delete and click Delete.
Chapter 3: Operations 73
Configuring SoL parameters
The MergePoint SP manager allows you to define SoL parameters for certain types of SPs, including Enable/Disable Serial over LAN, baud rate and channel privilege limitlevel.
To configure SoL parameters:
1. In the side navigation bar, click an SP name.
2. Click the Configuration tab.
3. In the top navigation bar, click Serial over LAN. The Serial over LAN Configuration windowappears.
4. Specify any of the following information:
a. Select or deselect Enable Serial over LAN as desired.
b. From the Baud Rate drop-down menu, select the baud rate.
c. From the Channel Privilege Level Limit drop-down menu, select Administrator,
Operator or User as the privilege level.
d. From the Retry Count drop-down menu, select the number of times for a retry to occur,
from 0 to 7 times.
e. In the Retry Interval field, enter the number of 10 milliseconds to elapse between each
retry.
5. Click Apply.
NFS
Network File System (NFS) provides remote access to SoL history information across networks. By default, SoL history information is saved to the MergePoint SP manager. To free memory space on the MergePoint SP manager, you may configure the SoL history data to be saved to another network location and access the SoL directories from anywhere on the network.
To configure NFS storage of SoL history data (Admin users only):
1. Click System - NFS.
2. Select Enable and specify the following information:
a. In the Server IP field, type the IP address of the NFS server.
b. In the Mount Directory field, type the directory pathname exported from the NFS
server.
c. From the Protocol drop-down menu, select the mount protocol.
3. Click Apply.
74 MergePoint® SP Manager Installer/User Guide
Remote Control
You may connect to a Remote Desktop Protocol (RDP) or Virtual Network Computing (VNC) server remotely through the MergePoint SP manager.
To connect to an RDP server:
1. In the side navigation bar, click an SP name.
2. Click the Remote Control tab.
3. In the top navigation bar, click RDP. The RDP window appears.
4. In the Server field, type the host operating system IP address (or hostname).
5. Click Connect.
To connect to a VNC server:
1. In the side navigation bar, click an SP name.
2. Click the Remote Control tab.
3. In the top navigation bar, click VNC. The VNC window appears.
4. In the Server field, type the host operating system IP address (or hostname).
5. In the Port field, type the port of VNC server.
6. Click Connect.
Diagnostics
The Diagnostics tab provides network trace and debugging tools by collecting all IP packets from an exchange between a network interface of the MergePoint SP manager and an SP. Traced information is saved to a trace file that can be downloaded. If needed, the downloaded trace file can be sent to Avocent technical support for troubleshooting assistance.
This trace and debug tool is implemented by tcpdump (see http://www.tcpdump.org/ for more information). First set up the data collection parameters before starting the tracing process. When the debug stops, click the Download button to create a download link.
To start the network debug:
1. Click the Diagnostic tab.
2. In the top navigation bar, click Debug.
3. Configure the interface, protocol, source IP, source port destination IP and destination port filtering options as needed.
Chapter 3: Operations 75
4. Click Start.
NOTE: You must stop the debug manually; otherwise the debug process continues indefinitely. When the trace file size reaches to the maximum size (preset maximum is 1M), the trace file willbe rewritten.
To stop the network debug:
1. Click the Diagnostic tab.
2. In the top navigation bar, click Debug.
3. Click Stop. Once stopped, you may download the trace file.
To download the trace file:
1. Click the Diagnostic tab.
2. In the top navigation bar, click Debug.
3. Click Download. All trace data is compiled and a download link appears next to the Download button.
4. Click the Download link to save the trace file.
NOTE: The trace file is stored on the server until the next debug starts.
NOTE: Diagnosticsmay also be configured using the CLI utility. See the tcdump commands in Summary of How to
Configure the Top Level Parameters on page 136.
Appliance Operations
MergePoint SP manager sessions
By selecting the System - Sessions option, the Admin user can view and manage MergePoint SP manager sessions and SSH/Telnet sessions.
Current MergePoint SP manager sessions are listed in the upper table of the session window.
To activate the session window and view a session:
Click System - Session. The current user session will be listed in green text.
To delete a session:
1. Click System – Session.
2. Select the session you wish to delete and click Delete.
Firmware version and upgrade
Visit www.avocent.com to download the latest MergePoint SP manager firmware files.
76 MergePoint® SP Manager Installer/User Guide
To upgrade firmware on the MergePoint SP manager (Admin users only):
1. Click System - Upgrade.
2. In the Filename field, type the path to the firmware file or click Browse to locate the file.
3. Click Upgrade.
NOTE: If the upgrade fails, you may use the serialport to restore the MergePoint SP manager to the previous firmware version. For more information see Configuring the MergePoint SP Manager Basic Settings on page 13.
To check the firmware version on the MergePoint SPmanager (Admin users only):
1. Start an SSHsession. See Using SSH with the MergePoint SP Manager on page 104.
2. Enter the version command. The version is displayed.
Example
root@MergePoint:~# version
MergePoint Application version:1.5.0.0
root@MergePoint:~# _
Boot configuration for the MergePoint SP5x24/SP5x40 manager
The Boot from drop-down menu lists options for booting the MergePoint SP manager. You can choose to use either the current image file or the image file stored on the network.
CAUTION: Network boots should be reserved only for troubleshooting.
Local boot options
In the Unit boot from drop-down menu, the entry for the current boot image is selected by default.
After a software upgrade, the boot file location choices are:
Network
Image:image_filename
The word “image” is followed by a colon (:), followed by the name of the file, including the version number. The menu item has the following format:
image: uImage.<version>-<build date>
Network boot options
For a network boot, the following prerequisites must be met.
A TFTP server must be available to the MergePoint SP manager.
An upgraded boot image file must be available on the boot server.
Chapter 3: Operations 77
The MergePoint SP manager must have a fixed IP address.
Configuring boot characteristics
The boot configuration feature allows the Admin user to configure the MergePoint SP5x24/SP5x40 manager boot characteristics, including the location of the MergePoint SP manager boot file, the watchdog timer state, the console speed and the speed of the Ethernet interfaces.
To configure boot options (Admin users only):
1. Click System - Boot configuration.
2. In the Appliance IP Address field, type the IP address for the MergePoint SP manager.
3. In the Watchdog Timer drop-down menu, select Active or Inactive option as you desire.
NOTE: If the watchdog timer is active, the MergePoint SP manager reboots if the software crashes.
4. In the Unit boot from drop-down menu, select the desired boot method.
5. To configure the unit boot from network:
a. Enter the filename of the network boot program in the Network boot filename field.
b. Enter the IP address of the TFTP server in the Server’s IP address field.
c. Select your desired console speed from the Console speed drop-down menu.
NOTE: The Network boot file must be in the /tftpboot directory on the TFTP server.
6. Select the desired speed for the eth0 and eth1 interfaces from the menus provided.
7. Click Apply.
NOTE: The system reboots automatically after you change the Unit boot file and apply it.
Unbinding the MergePoint SP manager from the DSView 3 server
To unbind the MergePoint SP manager from the DSView 3 server:
1. Click System - Advanced Setting.
2. Click Unbind from DSView 3 Server.
78 MergePoint® SP Manager Installer/User Guide
SP Sessions and Connections
4
79
The MergePoint SP manager provides access to SPs through a variety of session types and connections. From an SoL (Serial over LAN), SP console, Telnet or SSH session, you can access the serial controller, access the console or perform management actions, respectively. Alternatively, DirectCommand sessions and Native IP sessions provide direct, transparent access to the native applications on the SP. The Sessions window allows you to start and manage all session types, with the exception of Native IP connections, which are available from the Network tab.
System Sessions
You may connect five types of sessions on an SP from the Sessions window: SoL sessions, SP console sessions, Telnet sessions, SSH sessions and DirectCommand sessions. When you connect an SoL session, SP console session, Telnet session or SSH session successfully, a corresponding window opens through a MindTerm client.
NOTE: Before using the MergePoint SP manager system sessions features, installthe Java Runtime Environment (JRE) version 1.5.0_07 orlater (1.5 series), or version 1.6.0_02 orlater (1.6 series).
MindTerm client is a third party client that supports a variety of terminal emulation programs. Enter <Ctrl> + <[mouse right-click]> for the MindTerm menu. From the menu, you can configure terminal settings, define tunnels and modify other settings. For example, to change the terminal emulation program, select Settings - Terminal - Terminal Type. For more information on MindTerm client, seeUsing MindTerm to Create an SSH Tunnel on page 103
NOTE: Not all terminal emulation programs support function keysor special characters, so certain keystroke sequences may be required for some commands. For example, in some applications, the function key F1 may be performed by entering <Esc>1 on the keyboard. For more information, see the user guide for your terminal
emulation program.
Session types
The following system session types are available:
SoL (Serial over LAN) Session - SoL provides a mechanism that enables the serial controller of a managed SP to be redirected through a service processor session over IP. This enables remote console applications to provide access to text-based interfaces for BIOS, utilities, operating systems and management services while simultaneously providing access to service processor functions. See SoL Sessions on page 81.
SP Console Session - This connection allows you to directly access the SP console. You can then launch the management application from the service processor’s command line. See SP Console Sessions on page 82.
Telnet Session - This connection uses the Telnet protocol to access the service processor’s console and then perform SP management actions. After logging into the SP through the Telnet client, an admin user can send commands to the SP. See Telnet Sessions on page 82.
SSH Session - This connection uses the SSH protocol to access the service processor’s console and then perform SP management actions. After logging into the SP through the SSH client, an admin user can send commands to the SP. See SSH Sessions on page 83.
DirectCommand Session - This connection is a unique session provided by the MergePoint SP manager. It allows transparent access to a service processor through the MergePoint SP manager’s web interface. For more information, see DirectCommand Sessions on page 86. Native IP connections provide similar direct access functionality but are not operated through the Sessions window. For more information, see Choosing DirectCommand Sessions or Native IP Connections on page 83.
After selecting an SP and entering the Sessions window, all the supported sessions of the selected SP are displayed in different panels. There are two columns in each panel. The Action column lists the available actions for that session; click an action link to perform the corresponding action. The Status column shows the current state of the session. An “In-Use (N)” status (N=the number of connected sessions) indicates that the corresponding session is connected to the SP for the specified number of times, while the “Idle” status indicates that there is no connection to the corresponding session. A yellow icon is displayed next to an SP in the side navigation bar when there is at least one session connected with this SP.
The Active Session panel shows all the active sessions of the selected SP. You can disconnect a session by deleting it.
Active sessions
All currently active sessions are listed in the Active Session panel. Start time, duration, user, SP name and SP type session information is displayed. You can also disconnect active sessions from this window.
80 MergePoint® SP Manager Installer/User Guide
To view the Active Sessions panel and disconnect sessions:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. In the Active Sessions panel, select the session(s) you want to disconnect.
5. Click Delete. The corresponding session(s) window are closed. When all the connections to a session are deleted, the status of the corresponding session(s) is changed to Idle.
NOTE: You may also disconnect a session by closing the session window.
SoL Sessions
You may open an SoL session after setting up a serial over LAN connection.
NOTE: A maximum of four simultaneous sessionsare allowed from the DRAC/MC Web-based remote access interface. For DRAC/MC SPs, onlyone SoL connection to one blade is allowed at a time.
NOTE: For HP BladeCenter SPs, firmware version v1.3 or later is required for SoL.
To start an SoL session:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. In the SoL Session panel, click SoL Session to open the SoL window through a MindTerm client.
If the SP is a Windows server, an EMS/SAC prompt is returned. If the SP is a Linux server, the Linux serial console prompt is returned. Type valid SAC commands or Linux console commands in the MindTerm client to conduct SoL operations, such as BIOS configuration and power reset.
NOTE: For SoL sessionsonly, the Ctrl+c interrupt is inactive and willnot pass through to the SP processor from a MindTerm screen.
NOTE: Certain SP processors output some history information by default during an SoL session. Be sure that any scriptswritten are expecting this extra information.
NOTE: For the information on the SoL configuration, see Configuring SoL parameters on page 74.
To view SoL session history:
1. In the side navigation bar, click an SP name.
Chapter 4: SP Sessions and Connections 81
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. In the SoL Session panel, click SoL Session History to display all the commands entered in SoL mode and theiroutput.
NOTE: Dell DRAC/MC SPs and iDRAC blade SPs do not support SoL session history.
NOTE: To save the SoL session history on the network file system, see NFS on page 74.
To replay SoL:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. In the SoL Session panel, click SoL Sessions Replay to replay SoL actions and results, including the BIOS result. Click and drag the speed bar to control replay speed.
SP Console Sessions
You can open an SP console session to the selected SP.
To start an SP console session:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. In the SP Console Session panel, click SP Console Session to open the SP console window through a MindTerm client. After connecting to the service processor console session, you can run any corresponding service processor console commands.
Telnet Sessions
You can open a Telnet session to the selected SP.
To start a Telnet session:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
82 MergePoint® SP Manager Installer/User Guide
4. In the Telnet Session panel, click Telnet Session to open the Telnet console window through a MindTerm client.
After connecting to the Telnet session and logging into the SP with SP’s username and password, you can launch the management application from the service processor’s command line.
SSH Sessions
You can open an SSH session to the selected SP.
To connect SSH session:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. In the SSH Session panel, click SSH Session to open the SSH console window.
After connecting to the SSH session and logging into the SP with SP’s username and password, you can launch the management application from the service processor’s command line.
Choosing DirectCommand Sessions or Native IP Connections
You can connect directly to native applications on the SP through either DirectCommand sessions or Native IP connections. These applications are proprietary interfaces or command lines provided by the service processor vendor; examples include HP InSight, IBM Director and Dell Open Manage®.
With DirectCommand, users can gain access to native applications, integrated web servers and other proprietary interfaces that are available over TCP/IP. You can use the MergePoint web interface to launch a browser, vKVM or virtual media (vMedia) session on a service processor. DirectCommand only provides native access to pre-defined TCP ports on a service processor through a mapped local address.
Alternatively, Native IP (MergePoint SP5x24/SP5x40 manager only) allows access to native applications using the native IP address of the service processor. Once enabled and configured, Native IP allows external user traffic to selectively pass through the MergePoint SP5x24/SP5x40 manager and directly connect to a service processor on the internal server network. To configure Native IP, enable Selective mode, which creates an open trust, or define Native IP trusts with specific IP addresses that are permitted to establish Native IP connections.
Examples of cases where Native IP should be used instead of DirectCommand:
Chapter 4: SP Sessions and Connections 83
If you want an application like HP Systems Insight Manager (SIM) or IBM Director to connect to the native IP address of a service processor connected to the MergePoint SP5x24/SP5x40 manager, use Native IP. The Native IP feature allows access to the related programmatic interface and network protocols, where as DirectCommand only allows interaction with the configured TCP ports of a service processor through a mapped local loopback address (such as 127.x.x.x).
If you want to expose SNMP traps coming from a service processor to an SNMP trap agent on the user network, so that they can be collected directly by the SNMP agent, use Native IP. This applies to any other network protocol that needs to selectively pass to/from the service processor, through the MergePoint SP5x24/SP5x40 manager, and to/from trusted hosts in the user network. Another example of this type of protocol is Active Directory (AD), which may be needed if you want to authenticate iLOs with AD credentials instead of with local credentials.
If you want to provide direct user access to a service processor that has hard-coded IP addresses, use Native IP. (DirectCommand would automatically translate the hard-coded IP address to a local loopback address, which would prevent a successful connection).
The following figure illustrates a DirectCommand or Native IP connection to an SP.
84 MergePoint® SP Manager Installer/User Guide
Figure 4.1: MergePoint SP5x24/SP5x40 SP Manager Native IP Configuration
Number Description Number Description
1 Remote user 5 MergePoint SP5x24/SP5x40 manager
2 LAN 6 MergePoint SP manager web interface
Table 4.1: Descriptions for MergePoint 24/40 SP Manager Native IP Configuration
Chapter 4: SP Sessions and Connections 85
Number Description Number Description
3
DirectCommand or Native IP connection to the
service processor
7 SP
4
Connection to the MergePoint SP manager web
interface
8
Native interface, application or command
line on the SP
DirectCommand Sessions
DirectCommand sessions allows transparent access to a service processor through the MergePoint SP manager’s web interface. The DirectCommand Auto Login feature provides a configurable option to log in automatically to the remote SP management web interface without needing to enter a username or password. The vKVM interface or vMedia interface allows you to launch a vKVM or vMedia session on the SP.
NOTE: DirectCommand requires Java SE Runtime Environment version 1.6.0_02 or later. Visit www.sun.com to download the Java SE Runtime Environment.
A DirectCommand connection builds a set of TCP port forwarding tunnels between a user's workstation and a service processor managed by the MergePoint SP manager. All TCP packets that arrive at the user's workstation are forwarded directly to the service processor. The detailed information for the tunnels can be viewed from the DirectCommmand connection list window.
To use DirectCommand, first set up a DirectCommand connection between the user's workstation and the service processor to be accessed. Second, use the Browser Session, vKVM interface or vMedia interface provided by the DirectCommand connection.
NOTE: When you launch a DirectCommand session to a BladeCenter SP, you cannot access the corresponding blades from the session. However, if a blade server has the abilityto communicate with the MergePoint SP manager and was added as an independent SP, you can launch a separate DirectCommand session to that blade server. To add a blade server to the appliance, see Adding blade chassis and blades on page 37.
To start a DirectCommand session:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. In the DirectCommand Session panel, click Connect.
If the connection is successful, session links will appear below the connection status. From these links you can go to the Browser Session interface, Browser Session (Auto Login)
86 MergePoint® SP Manager Installer/User Guide
interface, vKVM interface or vMedia interface. A DirectCommand Connected link appears on the top option bar on the upper-right side of the page, where you can access the DirectCommand connection list window.
If the connection fails, the related diagnostic information and error message is shown.
NOTE: The number of session linksdepends on the type of SP. For example, currently onlyiLO has the vMedia interface. Most SPs support the Browser Session (Auto Login) interface and the vKVM interface.
NOTE: For RSA-II SPs, the vKVM session interface and vMedia session interface are in the same window.
CAUTION: For proper operation, the vKVM port for RSAII device should be TCP port 2000.
DirectCommand connection list
When you select an SP and successfully connect DirectCommand, a DirectCommand Connected link appears on the top option bar on the upper-right side of the page. Clicking this link displays the DirectCommand connection list showing all currently active DirectCommand connections. From this window you can access Browser session interface, Browser session Auto Login interface, vKVM interface or vMedia interface of a connected SP by selecting the SP and clicking the corresponding button. You may also view the device connection information and forwarded ports from this window.
NOTE: The forwarded port information is retrieved from the TCP ports table in the SP profile. See DirectCommand Options in Managing SP Profiles(Admin users only) on page 41.
To open the DirectCommand connection list window:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. In the DirectCommand Session panel, click Connect.
5. From the Top Option bar, click Connected. The DirectCommand connection list window appears.
6. The list displays all currently active DirectCommand connections with the corresponding SP IP addresses.
To start a Browser session:
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
Chapter 4: SP Sessions and Connections 87
4. If DirectCommand is not already connected, click Connect in the DirectCommand Session panel.
5. Click Browser Session.
-or-
From the Top Option bar, click Connected. The DirectCommand connection list window appears. Select the alias of the desired SP from the window, then click
DirectCommand.
To start a Browser session (Auto Login):
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. If DirectCommand is not already connected, click Connect in the DirectCommand Session panel.
5. Click Browser Session (Auto Login).
-or-
From the Top Option bar, click Connected. Select the alias of the desired SP, then click Browser Session.
To start a vKVM session:
NOTE: Close any other open network applications, such as VNC, to avoid a port number conflict.
1. In the side navigation bar, click an SP name.
2. Click the System Sessions tab.
3. In the top navigation bar, click Sessions.
4. If DirectCommand is not already connected, click Connect in the DirectCommand Session panel.
5. Click the vKVM Session link.
-or-
From the Top Option bar, click Connected. Select the alias of the desired SP, then click vKVM Session.
NOTE: If a vKM session is opened to an iLO or iLO 2 SP through DirectCommand, another vKVM session cannot be started and the current vKVM session cannot be shared.
88 MergePoint® SP Manager Installer/User Guide
Loading...