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

Asset ID: 1-72-1017475.1
Update Date:2009-09-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  1017475.1 :   Sun Enterprise[TM] 10000: netcon fails to get connected.  


Related Items
  • Sun Enterprise 10000 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>High-End Servers
  •  

PreviouslyPublishedAs
228589


Symptoms
Sometimes when attempting to start a netcon session to a Starfire[TM]
domain, you just get a "trying to connect" message without seeing
"connected." even if you wait several minutes.

Example:
starfire-ssp:Starfire1% netcon
trying to connect...

You may find that you can telnet to the domain ok, that the OS is working
without problems, and that the cvcd is running.

Resolution
If this is the case, then the most common cause is that the netcon_server
process for that domain which runs on the SSP has died.
netcon_server is started by bringup and should remain running as long as
there is either an OBP or an OS on the domain. During an SSP reboot it is
automatically restarted by startup.tcl, but other than that it is not
monitored by the startup.tcl script.
If you want to be sure which netcon_server process relates to which domain
(there should only be one per domain), you can use the following
command:
/usr/ucb/ps -axwwe | grep netcon_server | grep -v grep
{ NOTE: The output of this command is extremely verbose, as you get about
16 lines per process, and you can't reliably use grep to shorten it further! }
Check the value of SUNW_HOSTNAME which is displayed for each
netcon_server process.
To restart the netcon_server for a domain, use:
domain_switch <domainname>
netcon_server -r
This is the same way startup.tcl *reconnects* to netcon_server to the
domai


Product
Sun Enterprise 10000 Server

netcon, netcon_server, Starfire[TM], ssp
Previously Published As
16764

Change History
Date: 2008-01-08
User Name: 95826
Action: Update Canceled
Comment: *** Restored Published Content *** canceling update to allow migration to IBIS
Version: 0
Date: 2008-01-08
User Name: 95826
Action: Reassign
Comment: reassigning document to release it in order to allow migration to IBIS
Version: 0
Date: 2005-02-14
User Name: 114013
Action: Add Comment
Comment: please publish doc
thanks,
john chalk
Version: 0
Date: 2005-01-31
User Name: 114013
Action: Update Started
Comment: I was able to use the information in this document just moments ago.
I would like to see it stay as an active document
I want this article to stay valid
Version: 0
Date: 2003-11-19
User Name: 43660
Action: Approved
Comment: Reviewed comments about possible duplication. Checked 70018 and it refers to cases where netcon does connect but doesn't display a prompt. Although the cause of that may be also be the netcon server dying, the error in this case is different.

Added trademarks, minor formatting and grammatical changes. Ready to publish.
Version: 0
Date: 2003-11-15
User Name: 116819
Action: Approved
Comment: Still moderately useful.
Version: 0
Date: 2003-11-14
User Name: 8662
Action: Approved
Comment: reviewed as part of KM&O kccp project; possible duplicate
Version: 0
Date: 2003-09-19
User Name: 72607
Action: Rejected
Comment: I think the information explained in this SRDB is included in SRDB 70018. Please review that SRDB
Version: 0
Date: 2003-09-19
User Name: 8662
Action: Approved
Comment: Please review. Updated keywords, technology area.
Version: 0
Date: 2003-09-19
User Name: 8662
Action: Updated
Comment:
Version: 0
Date: 2003-05-20
User Name: Administrator
Action: Migration from KMSCreator
Comment: updated by : No owner
comment : No comment
date : Apr 2, 1998
Version: 0
Product_uuid
29ddef46-0a18-11d6-92de-ae47474f0f6c|Sun Enterprise 10000 Server

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