Sun Virtual Library Extension (VLE)
 
Sun StorageTek VSM5 System
 

PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VLE
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-4419135621>

Applies to:

Symptoms

Example error message when customer issued VARY RTD(xxxx) online from a VLE:
   SLS0000I VARY RTD(V022) ONLINE
   SLS6684I RTD VML2V022 on VTSS VTAPEM Returned UUIREQ error CC=30 RC=1

Display of RTD's, NOTE the RTD report failed/Offline
VT DISPLAY RTD

Note the following messages can occur when there is a communication failure on the customer network.  When a communication issue occurs, then perform a path validation from the connecting VSM.  If the path validates and the customer network is restored or working fine, a reset of the associated IFF cards might need reset.  Check the procedure on the referenced document 1399524.1 to reset the IFF card.

SLS6684I RTD VLE1RTD7 ON VTSS VSM01 RETURNED UUIREQ ERROR CC=30 RC=1        
SLS6693I RTD VLE1RTD7 FAILED, DRIVE WILL BE RETRIED LATER                      
SLS6628E RTD VLE1RTD7 ON VTSS VSM01 FAILED TO MOUNT MVC 600000             

SLS6684I RTD VLE1RTD7 ON VTSS VSM01 RETURNED ECAM ERROR CC=5 RC=109          
SLS6627E FAILED TO VARY ONLINE RTD VLE1RTD7 ON VTSS VSM01

Cause

Hardware failure in VLE causing VRTD failure and to not come online.

Explanation of CC=30 RC=1, return code UUI Command Description
30/1 query-device The Value for the DEVICEID connection is not known.

A network communication failure between VSM IFF and the VLE port.

Solution

1.) Issue command to find out what the RTD names are in the VLE box.

VT Display CONFIG or VT Query CONFIG, same command.

Here is output to look for. Note RTD NAME is what you are looking for.

2.) Issue command
     VT VARY PATH(rtdname) OFFLINE Note the name is what is recorded in the VLE        hardware. 

 Example RTD NAME V2L2V012 and for
DEVNO V022, which is what is in VTCS config

3.) Issue command
VT VARY PATH(rtdname) ONLINE. If path comes back online the proceed with next commands In this example PATH(V2LV012)

4.) Issue command
VT VARY RTD(devno) OFFLINE. It if comes offline, then issue next command. In this example RTD(V022)
VT VARY RTD(devno) ONLINE. If comes online, then you are good,

Display RTD's make sure RTD is now online.

For network communication issues between the VLE and VSM, check the vlelog file and search for "fail" or "error" or if you know the VMVC that would not mount, perform a search on this value.  Below is an example of what you see in the vlelog.

2013-05-19 19:59:32,157 [UuiReqHdlr-192.168.x.x:20268] INFO  messaging.uui.UuiMessageFactory - UUI Received: VOLUME_REPORT, VMVC=600000.
2013-05-19 19:59:32,161 [UuiReqHdlr-192.168.x.x:20268] INFO  messaging.uui.UuiMessageFactory - UUI Sending: VOLUME_REPORT_RESPONSE, RequestedVMVC=600000, RC=0/0-SUCCESS.
2013-05-19 19:59:38,579 [UuiReqHdlr-192.168.x.x:20274] INFO  messaging.uui.UuiMessageFactory - UUI Received: MOUNT_VMVC, Volume=600000, DeviceId=5670000000000001, RTD=15, StorageAttribute=DEDUP:NO, StorageClass=TWLSBVL1.
2013-05-19 19:59:38,585 [UuiReqHdlr-192.168.x.x:20274] ERROR vle.manager.VleManagerClient - Unable to process request: Affinity resource not found: VleResource: NAME = 5670000000000001 TYPE = DEVICE
2013-05-19 19:59:38,590 [UuiReqHdlr-192.168.x.x:20274] ERROR messaging.uui.UuiRequestHandler - VLE Request MOUNT_VMVC failed. Response: MountVmvcVleResponse: REQUEST_ID: R861320, COMPLETION_CODE: FAILURE, REASON_CODE: DEVICE_UNKNOWN, MOUNTED_VMVC: none
2013-05-19 19:59:38,594 [UuiReqHdlr-192.168.x.x:20274] INFO  messaging.uui.UuiMessageFactory - UUI Sending: MOUNT_VMVC_RESPONSE, DeviceId=5670000000000001, RTD=15, Requested Volume=600000, RC=30/1-DEVICE_ID_UNKNOWN.

Once you have determined what VSM is affected, then gather VSM base files and look for communication errors in the nlkout.txt file.  You should see the following messages around the same time frame that the customer experienced issues with vRTDs going offline and the vlelog messages (vlelog messages may not match the exact time).  There may also be FSC D142, D120, D14F and D0A3 messages for the same IFF card.  Make note of these and update the service request.

REC:  9796 13/05/19 at 17:45:03    IFF3    d142 FSCD142_IP_PHY_INTERRUPT ests (0120) isr(0030):  Remote Receiver Stat Chg(Not OK):Local Recver Stat Chg(Not OK):
REC:  9797 13/05/19 at 17:45:03    IFF3    d142 FSCD142_IP_PHY_INTERRUPT ests (0001) isr(000e):  Duplex Mode Chg(FULL):Link Speed Chg(1000Base-T):Link Stat Chg(Link Fail:Lo
cal Rcvr Not OK

References

This solution has no attachment