Sun Network Switch
 

PLA-Support>Sun Systems>SAND>Network>SN-SND: Sun Network Ethernet Switches
 

In this Document

Goal

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Customer could brick the switch with improper uboot settings
Created from <SR 3-9975493516>

Applies to:

Goal

The following are manual steps that can be followed to restore a "hung"  ES1-24 switch.  Normally this would be done by an Oracle Field Engineer if the switch has power but ILOM IP and console port is not responsive. We have seen this symptom in the past due to older SEFOS versions with known memory leaks, but there may be other causes where this could be useful.

Solution

Here are the steps that can fix this in many cases:

 - connect to the serial console of the ES1-24 and then power-cycle
 - press enter when the following msg is seen to get to uBoot =>

 Hit any key to stop autoboot: 3

 - execute the following steps:

 => setenv preserve_conf no
 => setenv set_factory_defaults all
 => saveenv
 => boot

 - Once the Es1-24 reboots, it will have factory-default config for
 ILOM/SEFOS which should fix the login and hang issue.

 Now configure the ILOM IP and netmask to allow remote access to restore
 the backup and upgrade firmware
 -> set pendingipaddress=##.##.##.## (use correct IP address)
 ->set pendingipnetmask=##.##.##.## (use correct netmask)
 ->set pendingipgateway=##.##.##.## (use correct GW IP)

 -> set commitpending=true
 Set 'commitpending' to 'true'


 Verify that you can ping the ILOM IP and log in via remote session.

 Restore the original configuration from your backup.

 You must upgrade to version 1.3.1.7 or higher to avoid a repeat of this
 hang . Download Patch 17050841: ORACLE SWITCH ES1-24 1.3 and update the firmware.

This solution has no attachment