| Asset ID: |
1-75-1020372.1 |
| Update Date: | 2011-02-22 |
| Keywords: | |
Solution Type
Troubleshooting Sure
Solution
1020372.1
:
Network information of Auto Service Request for Sun Systems
| Related Items |
- Sun Blade T6300 Server Module
- Sun Blade X6220 Server Module
- Sun Blade X6440 Server Module
- Sun SPARC Enterprise T5440 Server
- Sun Fire X4140 Server
- Sun Fire X4200 M2 Server
- Sun SPARC Enterprise M9000-32 Server
- Sun Blade X6240 Server Module
- Sun Fire V240 Server
- Sun Fire V245 Server
- Sun Fire V440 Server
- Sun Fire V480 Server
- Sun Fire X4170 Server
- Sun Fire X4440 Server
- Sun Fire E25K Server
- Sun SPARC Enterprise M5000 Server
- Sun Fire V215 Server
- Sun Fire X4270 Server
- Sun Fire E20K Server
- Sun SPARC Enterprise M9000-64 Server
- Sun SPARC Enterprise T1000 Server
- Sun Blade T6320 Server Module
- Sun Blade X6275 Server Module
- Sun SPARC Enterprise T5220 Server
- Sun SPARC Enterprise T5240 Server
- Sun Fire V445 Server
- Sun Fire X4275 Server
- Sun Fire X4600 Server
- Sun SPARC Enterprise M3000 Server
- Sun Blade T6340 Server Module
- Sun Blade X6270 Server Module
- Sun Fire V210 Server
- Sun Fire V890 Server
- Sun Fire X4100 Server
- Sun Fire X4500 Server
- Sun SPARC Enterprise T2000 Server
- Sun Fire V880 Server
- Sun Fire X2270 Server
- Sun SPARC Enterprise T5140 Server
- Sun Fire X4100 M2 Server
- Sun Fire X4540 Server
- Sun SPARC Enterprise M4000 Server
- Sun Fire 15K Server
- Sun SPARC Enterprise T5120 Server
- Sun Fire V490 Server
- Sun Fire X4200 Server
- Sun Fire X4600 M2 Server
- Sun SPARC Enterprise M8000 Server
|
| Related Categories |
- GCS>Sun Microsystems>Sun Tools
|
PreviouslyPublishedAs
257048
Applies to:
Sun SPARC Enterprise T1000 Server
Sun Blade T6300 Server Module
Sun Blade T6320 Server Module
Sun Blade T6340 Server Module
Sun Blade X6220 Server Module
All Platforms
Purpose
This documents helps to understand the network ports involved in Auto Service Request for systems and simple troubleshooting steps
Last Review Date
February 22, 2011
Instructions for the Reader
A Troubleshooting Guide is provided to assist
in debugging a specific issue. When possible, diagnostic tools are included in the document
to assist in troubleshooting.
Troubleshooting Details
Network ports involved in ASR systems
The 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
1691 - port through which client sends the SNMP traps
162 - ASR client receives the snmp trap
** ASR client receives the assets service tag and configuration information on any ephermal port
During the activation of the asset (asr activate_asset command), Service tag information is fetched from the client on port 6481
service responsible responsible
" svc:/network/stlisten:default "
If either of the following is not available
- service tag (installed and running)
svcs -a | grep reg
- serial number in /var/run/psn file and sneep command should give correct SN
- stlisten in ASSET
- stdiscover in SASM
we will get the following error messages
"Unable to contact Service Tags on asset. Please check if Service Tags is installed, running, and network accessible."
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:
Add a trap-destination to Sun Mangement Center
Simple trouble shooting commands
To 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
