Sun Microsystems 3900, 6900 manual To Failback the Virtualization Engine

▼To Failback the Virtualization Engine

In the event of a Sun StorEdge T3+ array LUN failover, the virtualization engine will route all I/O through the failover port on the Sun StorEdge T3+ array. After you isolate and check the cause of the failover, the virtualization engine continues to send I/O through the failover path. To restore the I/O to the primary path and fail the LUN back to its original controller, use the following procedure:

1.Verify that the T3+ array active path needs to be restored by viewing a live snapshot of the virtualization engine map, as shown in “Viewing the Virtualization Engine Map” on page 118.

If there has been a failover, the Multipath Drive Summary will show the same Sun StorEdge T3+ array active path WWN for all LUNs associated with one Sun StorEdge T3+ array, as shown in CODE EXAMPLE 9-3.

CODE EXAMPLE 9-3Multipath Drive Summary

Disk pool MP Drive	T3+ Active	Controller Serial
Target	Path WWN	Number

-------------------------------------------------------

t3b00	T49152	50020F230000725B	60020F2000006DFA
t3b01	T49153	50020F230000725B	60020F2000006DFA

2.If the Sun StorEdge T3+ array LUNS have failed over, run the command found in CODE EXAMPLE 9-5for that specific Sun StorEdge T3+ array.

Note –The Sun StorEdge T3+ array name is the same as the disk pool name—but with the last digit (equal to the Sun StorEdge T3+ array LUN number) removed, as shown in CODE EXAMPLE 9-4.

For example, the LUNs in disk pools t3b00 and t3b01 are named t3b0 on the Sun StorEdge T3+ array device.

CODE EXAMPLE 9-4Sun StorEdge T3+ array and Disk Pool Name

#/opt/SUWNsecfg/bin/failbackt3path -n t3b0

120Sun StorEdge 3900 and 6900 Series 2.0 Troubleshooting Guide • March 2003

Sun Proprietary/Confidential: Internal Use Only