Asset ID:	1-72-1019515.1
Update Date:	2010-08-05
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1019515.1 :   SunMC Agent will not start on a M8000/M9000 XSCF  


PreviouslyPublishedAs
240405

Symptoms
SunMC Agent will not start on a M8000/M9000 XSCF
If you see one of the following:

• Error returned from the XSCF 'setsunmc' command -- "Could not start Agent"
  
• The XSCF command 'showroute -a' takes a long time (i.e. more than 10s) to complete, but 'showroute -an' is fine.
  
• An XSCF snapshot has an empty *showroute_-a.out file and the *showroute_-a.err file contains the message "SNAPSHOT MSG: Command Timeout: Exit Signal: 15".
  

Resolution
If there is no configured nameserver or no valid nameserver available, the SunMC Agent will fail to start on the XSCF.

• A valid name server is required for all network connected XSCF.
• Use the XSCF command 'setnameserver' to configure the IP address of a DNS.
• Do not forget to run 'applynetwork' and 'rebootxscf' to apply the configuration.

Alternatively, you can leave the lan#0 and lan#1 takeover addresses unconfigured.



Additional Information
Debug:

• Use 'shownameserver' to check if the IP address of a name server is configured.
• You may wish to configure multiple nameservers for redundancy.
• If there is a name server configured, confirm the specified IP address is for a valid name server.
• Make certain you have an operable network path to the nameserver.

Product
Sun SPARC Enterprise M8000 Server
Sun SPARC Enterprise M9000 Server


Internal Comments
Regarding the mentioned SunMC issue, see also RFE 6679158 "RFE: allow M9000
XSCF SunMC agent to start without DNS host name resolution"

From 6679158: (see references)

On the M8000/M9000 platforms it is possible to configure a take over address
for the XSCF-LAN#0, this take over address is called lan#0 (there is also
lan#1 used for the other ethernet ports).

When SunMC is configured it uses the lan#0 takeover IP address for the agent.
This address does not have an entry in the local /etc/host file, so cannot be
DNS reverse lookup'd, so SunMC fails to start.

This is not a problem on the M4000 or M5000 as these platforms do not use the
lan#0 interfaces, they use the local IP address for the XSCF-LAN#0, which has
an entry in the local /etc/host file.

If a DNS nameserver is configured on the XSCF and the lan#0 IP is added, the
reverse lookup will then be succesful so this worksaround the problem.


setsunmc agent start xscf

Change History

Date: 5th Aug 2010
User Name: 113240
Action: submit
Comment:  Added M9000-32 and M9000-64 products, cleaned up internal
comment formatting


Attachments

This solution has no attachment

Attachments

This solution has no attachment