Sun StorageTek VTL Value System
 
Sun StorageTek VTL Prime System
 
Sun StorageTek VTL Plus Storage Appliance
 
Sun StorageTek VTL Storage Appliance
 

GCS>Sun Microsystems>Storage - Tape>Tape Virtualization
 

In this Document
  Goal
  Solution

Created from <SR 3-3247315791>

Applies to:

Goal

Solution

1. Select/highlight the node you are performing a health check on.
   
   
2. Review information under "General" tab on right hand side of screen (this is the default tab to be displayed).  For example, verify "Server Status" is "Online", "VTL Up Time" is appropriate (not been reset), "Failover Mode" is "Normal".
   Note: If failover has occurred, the server name will be red and message will be displayed on status line at bottom of screen. 
   
   
3. Click on the "Event Log" tab (the tab next to General on the top-right of the screen) and review/verify any messages that logged process has failed or errors been logged.
   Note: Typically the errors will have a red "E" to the left of the messages.
   
   
4. Click on the "Attention Required" tab, and review for any actionable items
   
   The following 4 items may not be needed, as any errors shoul d be reported in Event Log, but the following can be used to further troubleshoot/pinpoint an error listed in event log if needed:
   
   
• Open/expand the "VirtualTape Library System>Virtual Tape Library" tree to view vlib, vdrives and vtapes looking for for yellow or red icons, which inicate a problem.
  
  
• Open "Physical Tape Libraries" or "Replica Resources" tree and check for problems, if applicable
  
  
• Open "VirtualTape Library System>Physical Resources" tree and look for yellow or red icons (down HBAs, or offline LUNs).
  
  
• Open "SAN Clients" tree to verify no backup application clients are offline
  
  
5. Check Backup Application logs for errors
   
   
6. OPTIONAL (If familiar with the Disk Software): Check SANtricity or CAM for disk array health status Note: If familiar with All supportdata files, can review those instead
   
   

1. Enter 'vtl status' command. You should see "Running" for all process, as the following shows:
   
   Sun Microsystems VTL Server v4.00 (Build 1323)
   Copyright 2001-2007 by FalconStor Software. All Rights Reserved.
   Status of VTL SNMPD Module................ [RUNNING]
   Status of VTL QLogic Module............... [RUNNING]
   Status of VTL Authentication Module....... [RUNNING]
   Status of VTL Server (Compression) Module. [RUNNING]
   Status of VTL Server (FSNBase) Module..... [RUNNING]
   Status of VTL Server (Upcall) Module...... [RUNNING]
   Status of VTL Server (Event) Module....... [RUNNING]
   Status of VTL Server (Path Manager) Module [RUNNING]
   Status of VTL Server (Application)........ [RUNNING]
   Status of VTL FC Target Module............ [RUNNING]
   Status of VTL Server VTL Upcall Module.... [RUNNING]
   Status of VTL Server VTL Upcall Daemon.... [RUNNING]
   Status of VTL Server VTL Module........... [RUNNING]
   Status of VTL Communication Module........ [RUNNING]
   Status of VTL Logger Module............... [RUNNING]
   Status of VTL Self Monitor Module......... [RUNNING]
   Status of VTL Failover Module............. [RUNNING]
   
   
2. Enter 'sms -v' command.  Check for "FailOverStatus: 1(UP)", status' of "OK" and "0" or  "NO" in other fields, as the following shows:
   
   Usage: sms {force|nas|nasc|fm|sm|bmr|bmrreset|setroot (sm/fm)|clearreboot(sm/fm)} {value}
       bmr - to set the BMR health status
       bmrreset - to reset BMR value
       nas - to reset the NAS failure status
       nasc - to set nas health check
       force - enable force up fm - to set ipstorfm debug level
       sm - to set ipstorsm debug level
   
   Last Update by SM: Tue Mar 29 06:45:17 2011
   Last Access by RPC: Tue Mar 29 06:45:27 2011
   FailOverStatus: 1(UP)
   Status of IPStor Server (Transport) : OK
   Status of IPStor Server (Application) : OK
   Status of IPStor Authentication Module : OK
   Status of IPStor Logger Module : OK
   Status of IPStor Communication Module : OK
   Status of IPStor Self-Monitor Module : OK
   Status of IPStor NAS Modules: OK(0)
   Status of IPStor Fsnupd Module: OK
   Status of IPStor ISCSI Module: OK
   Status of IPStor BMR Module: OK( 0)
   Status of FC Link Down : OK
   Status of Network Connection: OK
   Status of force up: 0
   Broadcast Arp : NO
   Number of reported failed devices : 0
   NAS health check : NO
   XML Files Modified : NO
   IPStor Failover Debug Level : 0
   IPStor Self-Monitor Debug Level : 0
   Do We Need To Reboot Machine(SM): NO
   Do We Need To Reboot Machine(FM): NO
   Nas Started: NO
   
   
3. Enter 'ifconfig -a' command. Make sure all Ethernet interfaces are up
   <IP Configuration : "/sbin/ifconfig -a">
   lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 82 32 index 1
   inet 127.0.0.1 netmask ff000000
   bge0:flags=1001000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,FIXEDMTU> mtu 1500 index 2
   inet 10.0.0.21 netmask ffffff00 broadcast 10.0.0.255
   ether 0:9:3d:15:0:d
   bge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
   inet 10.0.0.20 netmask ffffff00 broadcast 10.0.0.255
   bge1:flags=1001000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,FIXEDMTU> mtu 1500 index 3
   inet 177.nnn.nnn.nnn netmask ffffff00 broadcast 177.nnn.255.255
   ether 0:9:3d:15:0:e
   bge1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
   inet 177.nnn.nnn.nnn netmask ffffff00 broadcast 177.nnn.nnn.255
   
   
4. Run Xray and review for errors (specifically messages file)
   See KM doc id 1146464.1 for instructions on running Xray from command line.
   
   

This solution has no attachment