| Asset ID: |
1-75-1361963.1 |
| Update Date: | 2011-10-29 |
| Keywords: | |
Solution Type
Troubleshooting Sure
Solution
1361963.1
:
VTL - How to troubleshoot VTL Console GUI connectivity issues
| Related Items |
- Sun StorageTek VTL Value System
- Sun StorageTek VTL Prime System
- Sun StorageTek VTL Plus Storage Appliance
- Sun StorageTek VTL Storage Appliance
|
| Related Categories |
- PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VTL
- .Old GCS Categories>Sun Microsystems>Storage - Tape>Tape Virtualization
|
In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
Applies to:
Sun StorageTek VTL Storage Appliance - Version: 4.0 - Build 1221 to 4.0 - Build 1221 - Release: 4.0 to 4.0
Sun StorageTek VTL Value System - Version: 1.0 - Build 1323 to 1.0 - Build 1323 [Release: 1.0 to 1.0]
Sun StorageTek VTL Plus Storage Appliance - Version: 1.0 - Build 1323 to 2.0 - Build 1656 [Release: 1.0 to 2.0]
Sun StorageTek VTL Prime System - Version: 1.0 - Build 1813 to 1.1 - Build 2076 [Release: 1.0 to 1.0]
Information in this document applies to any platform.
Purpose
Provide troubleshooting steps when remote VTL Console GUI will not connect to VTL server.
Scenario: The VTL Console GUI comes up when started from the console server, but it does not see/connect to the VTL server nodes.
Last Review Date
September 26, 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
- Close VTL Console and restart, then retry connecting.
- Can connection be made to other VTL servers?
- If this a failover config, can connection be made to failover partner? If so, has a failover occurred?
- If failover has occurred, stop here and refer to failover/failback procedure (doc id 1013440.1).
- If it can connect to some servers and not to other VTL servers, then troubleshoot to make sure the IP address for the server in question is correct in the configuration.
- Ping VTL server using IP (or server name if DNS is setup) to see if network is OK.
- If ping unsuccessful, stop here and check/resolve network issue.
- Check backup application and see if backups or other processing is being completed successfully to VTL node in question.
- If backups are not running successfully, stop here and have VTL server checked out. If necessary, open a case with Oracle VTL Support.
- If items 2, 3, & 4 are true/good, then restart VTL Communication module from the VTL server command line:
# vtl restart comm
NOTE: Recommend doing this during low activity as to not impact jobs in process.
- If all above doesn't resolve issue, open problem case with Oracle VTL Support.
Attachments
This solution has no attachment
