![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Troubleshooting Sure Solution 1020372.1 : Network information of Auto Service Request for Sun Systems
PreviouslyPublishedAs 257048 Applies to:Sun SPARC Enterprise T1000 ServerSun Blade T6300 Server Module Sun Blade T6320 Server Module Sun Blade T6340 Server Module Sun Blade X6220 Server Module All Platforms PurposeThis documents helps to understand the network ports involved in Auto Service Request for systems and simple troubleshooting steps Troubleshooting StepsNetwork ports involved in ASR systemsThe following diagram shows the default network ports used for Auto Service Request for systems (ASR systems): Asset SASM (Sun Automated Service Manager) ============ ==================================== | |--1691------162-| | | | | |-------->443 / proxy | |--6481--------**| | ============ ==================================== <-------------Local network---------------> <-----Internet-------> 6481 - port through service tag information is received by SASM During the activation of the asset (asr activate_asset command), Service tag information is fetched from the client on port 6481
If either of the following is not available
we will get the following error messages
The reverse is not true. In other words, if we deactivate the asset it will not look for the asset's information. No network communication will happen between SASM and asset during deactivation. Even during a fault SASM will fetch the asset information from it's local resource and send to transport.sun.com for logging Service request Port 162 and 1691 are used for SNMP communication We can reconfigure the SNMP ports using asrassetmenu.sh script available in option:
Simple trouble shooting commandsTo see traffic between the SASM and assets: # snoop host (hostip) port (portnumber) To check the connection and the port status #netstat -an | grep (port number) Attachments This solution has no attachment |
||||||||||||
|