![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Troubleshooting Sure Solution 1392845.1 : Sun Storage 7000 Unified Storage System: How to Troubleshoot Loss of Network Connection to the Management Interface
This document covers troubleshooting the loss of network connectivity to the Administration Interface only of the 7000 series Unified Storage Systems. In this Document
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] PurposeTo 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
Troubleshooting StepsThere 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 BUIIt 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 : -> start /SP/console If necessary log in again at the login prompt to access the appliance CLI. appliance:> configuration net routing show Default routes will show as 0.0.0.0/0. ROUTE DESTINATION GATEWAY INTERFACE TYPE 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. appliance:> configuration net interfaces select nge0 show should show "admin = true". appliance:> configuration net routing 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.
2. CLI is available via ssh but unable to access BUIIt 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. 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 The BUI should now be accessible. # 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. # 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. 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 |
||||||||||||||||||||
|