Management - Sun/Solaris LOM for 'V' Series
Wed, 02/17/2010 - 17:56 — racastan.ncsu.edu
How to Configure Sun ‘V’ Series SUN Machine:
For example the machine being set up will be called ‘machinename’
Obtain and set up in DNS an IP for the LOM:
In DC1 use VLAN 13( 172.27.2.0 – 172.27.3.0 )
In DC2 use VLAN 2101( 172.27.130.0 )
Set DNS forward lookup name to machinename-nm.oit.ncsu.edu
If you do not know how to set up DNS or have access to DNS then submit a ticket to Comtech (email@example.com.
1) Login to the Serial Console(machinename-c) and then move over to Network Management via ‘#.’
Login as user ‘admin’ and type ‘setupsc’ to start configuration; follow the prompts and answer as lited below. If the ‘admin’ password isn’t known then see the section below entitled ‘Overriding LOM password on V Series Solaris machine.’
Entering Interactive setup mode. To exit and discard changes to that point, use Ctrl-C or to exit and save changes to that point, use Ctrl-Z.
Do you wish to configure the enabled interfaces [y]? y
Should the SC network interface be enabled [y]? y
Should the SC email alerts be enabled [y]? n
Do you wish to configure the network interface [y]? y
Should the SC use DHCP to obtain its network configuration [n]? n
Enter the SC IP address [100.100.100.100]? 172.27.x.x
Enter the SC IP netmask [255.255.255.0]? 255.255.254.0
NOTE: If the netmask fails, just set it to 255.255.255.0 and then change it after setup using command ‘setsc netsc_ipnetmask 255.255.254.0’
Enter the SC IP gateway address [100.100.100.100]? 172.x.x.x
NOTE: Gateway information depends on the datacenter of machine:
In DC1 use VLAN 13( 172.27.2.1 )
In DC2 use VLAN 2101( 172.27.130.1 )
Should the TPE link test be enabled [y]? y
Do you wish to configure the managed system interface [y]? y
What level of SC events should be reported to the managed system where valid settings are 0 (none), 1 (critical), 2 (critical and major) and 3 (critical, major and minor) ? 2
What action should the SC invoke if the OS is hung. The available options are 'none', 'xir' or 'reset' where an xir will attempt to collect diagnosis data before invoking a reset [xir]? xir
How many seconds should be allowed for an XIR to complete (maximum timeout of 10800s) ? 900
Do you wish to configure the network management interfaces [y]? y
Enter the number of mail servers to configure ? 0
Do you wish to configure the SC parameters [y]? y
Enter any customer data for this platform (maximum of 40 characters) ?
Enter the console session escape sequence (2 characters). The first character can be any printable characters or control-A through control-Y except for control-C, control-D, control-H, control-J, or control-M. The second character must be a ".". [#.]? #.
Enter level of events to be displayed over the CLI where valid settings are 0 (none), 1 (critical), 2 (critical and major) and 3 (critical, major and minor) ? 2
Should poweron sequencing be enabled [y]? y
Enter the SC cli prompt (maximum of 16 characters) [sc]? machinename-nm
Enter the SC CLI timeout in seconds (maximum of 10000s) ? 0
Should password entry echo '*'s [y]? y
2) Set the following extra fields from the sc prompt:
setsc if_connection ssh
How to update the LOM to latest version:
1) Login to server via ssh and become user root.
Verify the OBP(Open Boot Prompt Level) by typing the following commands as root:
Type ‘uname –i’ to verify the class of machine as you’ll need that to get correct obp upgrade software. Example Output for a V240: SUNW,Sun-Fire-V240
To verify the OBP level type ‘/usr/sbin/prtconf –V’
Example Output: OBP 4.22.33 2007/06/18 12:45
Use the above information to obtain a copy of the latest obp for your model machine. On
pxe00.unity.ncsu.edu under /tftpboot/solaris/model#/obp/ will be a zip file of the latest obp patch for
that machine. Copy over the .zip file into /tmp/ , unzip, and follow the readme instructions that come with package. A reboot will be required so make sure and be on the console of machine.
The README file for LOM upgrade procedure below will contain the minimum OBP level required in order to run LOM software. OBP MUST BE UPGRADED first if below minimum level otherwise LOM won’t work properly. Once new OBP is applied(if needed), continue on with the LOM update.
2. cd into the update directory library path: cd /usr/platform/`uname -i`/lib
3. If there is no images subdirectory, create one:
4. Change to the images directory:
5. ftp(or scp using port 24) over a copy of the lom update files and ‘README’
pxe00.unity.ncsu.edu has a copy of the LOM update files and README
Copy over ALL update files in directory and README into the local machines /usr/platform/`uname –i`/lib/images/ directory
For V240 model machines look in /solaris/tftpboot/solaris/v240/lom/
For V215 model machines look in /solaris/tftpboot/solaris/v215/lom/
For V210/V245 machines look in /solaris/tftpbooot/solaris/v210/lom/
Follow the ‘README’ instructions per that model of V series machine.
Overriding LOM password on V Series Solaris machine:
To overide the ALOM password on the system you will need to:
1) Attach console to Serial Console Port directly or from digi if system doesn’t have an operating system already installed.
2) Power on the server via the front power button. Once POST has
completed, you will need to wait 1 to 2 minutes for a timeout to
occur and the system to drop to the "ok>" prompt.
If you do not get the "Please login:" prompt (you will likely see the
SC prompt) then you must power the system off remove the battery from
the LOM board, wait a minute, and re-install everything).
Below is an example of what you might see on the console:
SC Alert: Host System has Reset
[wait one two minutes]
Serial line login timeout, returns to console stream.
3) Boot the system to the OS level. If Solaris is not currently
installed on the server, you will need to install it at this point.
4) Use the scadm command to reset the admin password:
a) cd /usr/platform/`uname -i`/sbin
b) ./scadm userpassword admin
5) Use the escape sequence "#." to get system back to the alom login
6) You can now log into the admin account using the password from
step 4 b).