Oracle FS1-2 Flash Storage System
 

PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
 

In this Document

Goal

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Customers should not be ssh to the pilot

Applies to:

Goal

Oracle Integrated Lights Out Manager (ILOM) is firmware that runs on a chip called the Service Processor (SP) in an Oracle Sun server, that is separate from the server CPU(s). ILOM allows for remote monitoring and management of an Oracle Sun server.
The FS1-2 uses Oracle Sun servers for it's Pilots and Controllers.

The ILOM SP's are connected on an internal network in the FS1-2 (169.254.2.xxx), that is separate from the PMI network (172.30.80.xxx).
In certain circumstances, you may need to access the Pilot or Controller ILOM using ssh, i.e.:  if the fscli or GUI ILOM access does not work (if the Pilot or Controller is failed for example).

Solution

The following diagrams illustrate the layout of the Pilot and Controller ILOM networks:

In the FS1-2, you cannot directly access the Pilot ILOM from the customer's network, first you must ssh to the Pilot. And, you cannot directly access a Controller ILOM from the Pilot (or the customer's network), first you must ssh from the Pilot to the Controller on the PMI network (172.30.80.xxx) in order to access the Controller ILOM.

Examples

• To access the Active Pilot ILOM:
  1. ssh to the shared Pilot IP address from the customer's network and log into the Pilot.
  2. ssh to 169.254.2.5 (the local Pilot's ILOM). The password is "changeme".
  3. You are now logged into the ILOM on the Active Pilot.
     
     
• To access the Standby Pilot ILOM:
  1. ssh to the shared Pilot IP address from the customer's network and log into the Pilot.
  2. ssh to 169.254.2.9 (the remote Pilot's ILOM). The password is "changeme".
  3. You are now logged into the Standby Pilot ILOM.
     
     
• To access the CONTROLLE-01 ILOM from CONTROLLER-02 (useful if CONTROLLER-01 is failed):
  1. ssh to the shared Pilot IP address from the customer's network and log into the Pilot.
  2. cat /etc/nodenames and you will get output similar to this (your actual WWN's will be different):
     
     
     [root@pilot2 ~]# cat /etc/nodenames
     172.30.80.3 WN2009fffffffffffa WN2008000101000000 mgmtnode
     172.30.80.2 WN2008fffffffffff2
     172.30.80.128 WN508002000158ba50
     172.30.80.129 WN508002000158ba51 WN2008000101000001
     [root@pilot2 ~]#
      
     
     The IP addresses ending in .128 and .129 correspond to the two controllers on the PMI network. Note the "WN" after the IP.  The "WN" ending in '0' is CONTROLLER-01 and the "WN" ending in '1' is CONTROLLER-02. This should match with the CONTROLLER-01 and -02 WWN found in the chsh.xml or SystemConfiguration.txt file.
      
  3. ssh from the Pilot to CONTROLLER-02 on the PMI network:
     
     
     [root@pilot2 ~]# ssh 172.30.80.129
     WN508002000158BA51 #
      
     You are now on the CONTROLLER-02 console.
     
     
  4. Next, ssh to the CONTROLLER-01 ILOM from CONTROLLER-02, the password is "changeme":
     
     
     WN508002000158BA51 # ssh 169.254.2.9  <<--- IP address for the opposite controller's ILOM
     Password: changeme
     
     Oracle(R) Integrated Lights Out Manager
     
     Version 3.1.2.40 r93718
     
     Copyright (c) 2014, Oracle and/or its affiliates. All rights reserved.
     
     Warning: password is set to factory default.
     
     ->
      
  5. To end your session, type exit 3 times.
     
     
     -> exit
     WN508002000158BA51 # exit
     [root@pilot2 ~]# exit
      
     
     
     Note that you could access the CONTROLLER-02 ILOM by following this same procedure above, but instead of ssh to the CONTROLLER-01 ILOM, ssh to the CONTROLLER-02 ILOM from the CONTROLLER-02 console instead:
     
     ssh 169.254.2.5  <<---ILOM on local controller
      
     
     

Some useful ILOM troubleshooting commands (output supressed):

This solution has no attachment