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: to understand how to correct the pilot netmask configuration
Created from <SR 3-10443352871>

Applies to:

Goal

This document explains how to recover from an incorrect netmask configuration on the Pilots.  Network access to the Pilots has been lost and connectivity to the Pilots using a computer connected directly to the NET-3 ports does not work.

Solution

Correcting the netmask configuration requires a connection to the active Pilot.  There are two methods that can accomplish this:

• Attaching a VGA monitor & USB keyboard to the Pilot.
  
  
• Using the ILOM connections via one of the Controllers.

VGA Monitor and USB Keyboard Method

1. Make sure the NET-3 ports on both Pilots are connected on the customer network as the NET-3 port links must be up.
   
   
2. Connect the VGA monitor and USB keyboard directly attached to a Pilot and login as root user.
   
   
3. Connect to active Pilot:
   
   
   [root@pilot2 ~]# ssh 172.30.80.1
   [root@pilot2 ~]#
     
   
   
   NOTE: This command uses the Private Management Interface (PMI) shared IP address to guarantee you are on the active Pilot.  In this example you were already on the active Pilot so the prompt stayed the same.
    
   
   

ILOM Connection Method

1. Connect a serial NULL Modem cable with an RJ45 connector to the Controller SER MGT port located in the rear of the Controller:
   
   
   
   and the other end to a laptop. 
   
   
2. Using PuTTY (or similar program), use the following settings to establish the connection:
   
   Speed: 9600
   Data bits: 8
   Stop bits: 1
   Parity: None
   Flow Control: XON/XOFF
   
   
   ORACLESP-1315FM2009 login: root
   Password:
   
   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.
   
   ->
    
   
   
3. From the Controller ILOM, access the Controller console and log in:
   
   
   -> start /HOST/console
   Are you sure you want to start /HOST/console (y/n)? y
   
   Serial console started.  To stop, type ESC (
   
   WN508002000158BA51 login: root
   WN508002000158BA51 #

    

4. From the Controller console, SSH to IP 172.30.80.1, which will connect to the active Pilot by default:
   
   
   WN508002000158BA51 # ssh 172.30.80.1
   Unauthorized use is prohibited and can have significant adverse system impact.
   
   Contact Technical Support
   
   [root@pilot2 ~]#

Correct the Netmask

1. On the active Pilot, change the netmask using the pcli utility found at /var/lib/pillar/apps/AxiomCLI/src/pcli.
   
   
2. Display the current network settings running the following command:
   
   
   [root@pilot2 ~]# /var/lib/pillar/apps/AxiomCLI/src/pcli sub -H localhost -u administrator GetNetworkSettings
   Password:
   Message
     Response
       CorrelationID: 1426961889
       BeginStreamResponse
         TaskGuid: 414B303031323639A13FDCFDED52EFE2
         TaskFqn: /GetNetworkSettings/207598/administrator
   Message
     Response
       CorrelationID: 1426961889
       GetNetworkSettingsResponse
         NetworkSettingsInformation
           PublicIpAddress: 10.0.0.2
           PublicNetmask: 255.255.255.252
           DefaultRoute: 10.0.0.1
           Pilot1IpAddress: 10.0.0.3
           Pilot2IpAddress: 10.0.0.4
           PrimaryDNS:
           SecondaryDNS:
           TertiaryDNS:
           DhcpEnabled: false
           DuplexSetting: AUTO
           ManagementInterfaceSpeed: AUTO
           MacAddress: 00:10:E0:2A:01:B7
   Message
     Response
       CorrelationID: 1426961889
       EndStreamResponse
         TaskGuid: 414B303031323639A13FDCFDED52EFE2
         TaskFqn: /GetNetworkSettings/207598/administrator
   
   
   
3. Review the network settings. To change the netmask, run the following command:
   
   
   [root@pilot2 ~]# /var/lib/pillar/apps/AxiomCLI/src/pcli sub -H localhost -u administrator ModifyNetworkSettings PublicNetmask=255.255.255.0

    

   NOTE: In this example the netmask has changed from 255.255.255.252 to 255.255.255.0.
   
   
   
4. Execute the GetNetworkSettings command again to verify the change has been made:
   
   
   [root@pilot2 ~]# /var/lib/pillar/apps/AxiomCLI/src/pcli sub -H localhost -u administrator GetNetworkSettings
   Password:
   Message
     Response
       CorrelationID: 1426961889
       BeginStreamResponse
         TaskGuid: 414B303031323639A13FDCFDED52EFE2
         TaskFqn: /GetNetworkSettings/207598/administrator
   Message
     Response
       CorrelationID: 1426961889
       GetNetworkSettingsResponse
         NetworkSettingsInformation
           PublicIpAddress: 10.0.0.2
           PublicNetmask: 255.255.255.0
           DefaultRoute: 10.0.0.1
           Pilot1IpAddress: 10.0.0.3
           Pilot2IpAddress: 10.0.0.4
           PrimaryDNS:
           SecondaryDNS:
           TertiaryDNS:
           DhcpEnabled: false
           DuplexSetting: AUTO
           ManagementInterfaceSpeed: AUTO
           MacAddress: 00:10:E0:2A:01:B7
   Message
     Response
       CorrelationID: 1426961889
       EndStreamResponse
         TaskGuid: 414B303031323639A13FDCFDED52EFE2
         TaskFqn: /GetNetworkSettings/207598/administrator
   
   
   
5. Verify connectivity to the Pilots on the customer network.
   
   
6. If the ILOM method was used, type exit repeatedly until the Controller login prompt is seen, and then type ESC + ( (escape key and shift 9) to exit and stop the /HOST/console.

This solution has no attachment