Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-75-1392845.1
Update Date:2012-06-25
Keywords:

Solution Type  Troubleshooting Sure

Solution  1392845.1 :   Sun Storage 7000 Unified Storage System: How to Troubleshoot Loss of Network Connection to the Management Interface  


Related Items
  • Sun Storage 7310 Unified Storage System
  •  
  • Sun Storage 7410 Unified Storage System
  •  
  • Sun ZFS Storage 7120
  •  
  • Sun Storage 7110 Unified Storage System
  •  
  • Sun ZFS Storage 7320
  •  
  • Sun ZFS Storage 7420
  •  
  • Sun Storage 7210 Unified Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>NAS>SN-DK: 7xxx NAS
  •  
  • .Old GCS Categories>Sun Microsystems>Storage - Disk>Unified Storage
  •  


This document covers troubleshooting the loss of network connectivity to the Administration Interface only of the 7000 series Unified Storage Systems.

In this Document
Purpose
Troubleshooting Steps
 1. The CLI is available via the console from the SP but there is no access to the BUI
 2. CLI is available via ssh but unable to access BUI
References


Applies to:

Sun Storage 7210 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 7310 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 7110 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun ZFS Storage 7320 - Version Not Applicable to Not Applicable [Release N/A]
Sun ZFS Storage 7120 - Version Not Applicable to Not Applicable [Release N/A]
7000 Appliance OS (Fishworks)
NAS head revision : [not dependent]
BIOS revision : [not dependent]
ILOM revision : [not dependent]
JBODs Model : [not dependent]
CLUSTER related : [not dependent]


Purpose

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - 7000 Series ZFS Appliances


This document is intended to cover the causes of loss of network connectivity to the Administration Interface only of the 7000 series Unified Storage appliance, and to provide solutions for those problems.
The Administration Interface covers both Browser User Interface (BUI) and Command Line Interface (CLI) access to the appliance.

This document is only intended to apply to loss of network access. If the CLI for the Administration Interface is not available via the console run from the Service Processor (SP or ILOM) then the problem is elsewhere. In this situation see <Document 1401282.1> "Sun Storage 7000 Unified Storage System: How to Troubleshoot Unresponsive Administrative Interface" for more information.

Troubleshooting Steps

There are two basic failure modes for network access to the Management Interface. Either both BUI and CLI are unavailable via the network (but the CLI is still available via the console from the SP), or the CLI is accessible via ssh but the BUI is unavailable.

If the CLI is not available at all from the SP console then the problem is not network related.  If this is the case please see <Document 1401282.1> "Sun Storage 7000 Unified Storage System: How to Troubleshoot Unresponsive Administrative Interface (BUI/CLI hang)" for further information.

1. The CLI is available via the console from the SP but there is no access to the BUI

It is likely that the cause of this problem is the absence of a correct network route between the local system and the appliance. To check if there is a fixed route, or a default route set do the following :

Connect to the SP either via ssh to the SP network administration interface, or by serial access to the serial management port on the SP.
Log in as root using the same password as root access to the appliance Mangement Interface.
Start the console

-> start /SP/console

If necessary log in again at the login prompt to access the appliance CLI.

To show the routes currently set

appliance:> configuration net routing show

Default routes will show as 0.0.0.0/0.
Manually added routes show as static whereas those automatically added will show as system or dynamic. Only static routes can be removed or edited manually.

There will need to be a route either directly to the local system's network or via a default route, via a gateway that is accessible to both the appliance and local system, and to the correct interface on the appliance that is enabled for admin.
e.g.

ROUTE      DESTINATION                      GATEWAY         INTERFACE TYPE
route-001  0.0.0.0/0                        10.163.224.1    nge0      static

For a client to access the Management Interface on the appliance above, it must be on a network from where it can reach the gateway of 10.163.224.1. On the appliance the nge0 interface should have the "Allow Administration" checkbox ticked in the BUI. Check this via the "Configuration > NETWORK" screen and click the "Edit" pencil icon next to the appropriate interface.
Alternatively using the CLI :

appliance:> configuration net interfaces select nge0 show

should show "admin = true".

If no appropriate route is set then one should be added, either a static route to the local system's network, or a default route via a mutually accessible gateway.
e.g. to add the default route seen above:

appliance:> configuration net routing
appliance:configuration net route (uncommitted)> set family=IPv4
                        family = IPv4 (uncommitted)
appliance:configuration net route (uncommitted)> set destination=0.0.0.0
                   destination = 0.0.0.0 (uncommitted)
appliance:configuration net route (uncommitted)> set mask=0
                          mask = 0 (uncommitted)
appliance:configuration net route (uncommitted)> set gateway=10.163.224.1
                       gateway = 10.163.224.1 (uncommitted)
appliance:configuration net route (uncommitted)> set interface=nge0
                     interface = nge0 (uncommitted)
appliance:configuration net route (uncommitted)> commit

For further information on adding routes, see the "Configuration: Network: Routing" section of the online HELP available via the BUI, or the appropriate Administration Guide available from Oracle Unified Storage Systems Documentation.
For best practice recommendations on configuring routes check <Document 1395461.1> "Sun Storage 7000 Unified Storage System: Best Practice Recommendations for Network Configuration".

 

2. CLI is available via ssh but unable to access BUI

It is possible that the appliance kit http server that acts as the web server for the BUI has faulted or has been prevented from starting.
There may be an alert for this, to check this use the CLI:

appliance:> maintenance problems
appliance:maintenance problems> show
Problems:

COMPONENT DIAGNOSED TYPE DESCRIPTION
problem-000 2012-1-10 11:55:19 Major Defect The service
                                            'appliance/kit/http:default'
                                            failed and could not be
                                            restarted.

If there is a problem simply select it and mark it repaired :

appliance:maintenance problems> select problem-000
appliance:maintenance problem-000> markrepaired
Marking a problem repaired indicates that an administrator has fixed the
underlying problem and restored any affected components to their normal state.
This is typically only performed by Oracle service personnel or a documented
Oracle repair procedure.

Are you sure you want to mark this problem repaired?

Are you sure? (Y/N)
Y
Problem "43444af6-89cd-6381-db31-f55aaa9219fe" has been marked repaired.

The BUI should now be accessible.
If not, further troubleshooting will need to be carried out by an Oracle TSC engineer, please raise a Service Request to facilitate this.


Check the status of the appliance kit http server from the OS shell:

# svcs -xv kit/http

Check that the system is listening for requests on port 215 on the correct IP address:

# netstat -an | grep 215

If the appliance kit http service is not online and there is no entry for LISTEN on port 215 for the IP address associated with the interface that administration is allowed from then it may be the case that another service on which the svc:/appliance/kit/http:default depends has not started up. Check this by looking at the state of all the services:

# svcs -xv

If there are other services that have not started up yet it may be that the system was booted via a different milestone and then booted to milestone all using the svcadm command whilst in a shell, which may now stopping some services completing.  This can also happen if you have accessed the system before boot was complete by using the "ESC 9" hidden option to access aktty.
To fix the problem simply exiting the shell you are in should allow the services to complete and the svc:/appliance/kit/http:default service to be started.
If the svc:/appliance/kit/http:default is the only service that is not started then you should just be able to start it up simply by typing:

# svcadm enable kit/http

If after this the svc:/appliance/kit/http:default service still does not start or there are other services not started up please contact the TSC for further assistance. If an SR has not already been raised for the problem, please raise a new one and have it assigned to a member of the NAS team.

Back to <Document 1392086.1> Sun Storage 7000 Unified Storage System: How to Troubleshoot Network Problems.

This document contains normalized content and is managed by the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es)

References

<NOTE:1392086.1> - Sun Storage 7000 Unified Storage System: How to Troubleshoot Network Problems
<NOTE:1395461.1> - Sun Storage 7000 Unified Storage System: Best Practice Recommendations for Network Configuration
<NOTE:1401282.1> - Sun Storage 7000 Unified Storage System: How to Troubleshoot Unresponsive Administrative Interface (BUI/CLI hang)

Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback