Asset ID:	1-72-1007787.1
Update Date:	2010-08-26
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1007787.1 :   SANbox switch shows additional Sun StorEdge[TM] T3 as 'initiator' on Segment Loop (SL) port  


PreviouslyPublishedAs
210773

Symptoms
SANbox (1G) Qlogic/Sun switch shows additional Sun StorEdge[TM] T3 as 'initiator' rather than 'target' in Segmented Loop (SL) configurations (in addition to the T3 not being seen by the host).
A T3 with a duplicate 'targetid' will show up as 'initiator' when a capture.sparc output is obtained from the switch.

In the following capture.sparc output (from explorer run), port 7 is a T3 device with the same configured targetid as the device already connected to port 1.

 Port #   Port Type       Admin State     Oper State      Status          Loop Mode
------   ---------       -----------     ----------      ------          -------   ---
1      SL_Port          online         online        logged-in         Target
Devices:  1   Address: 0x00
0xe8    

    2      SL_Port          online         online        logged-in         Target
Devices:  1   Address: 0x00
0x01   

    3      SL_Port          online         online        logged-in         Target
Devices:  1   Address: 0x00
0xe4   

    4      SL_Port          online         online        logged-in         Target
Devices:  1   Address: 0x00
0x02   

    5      SL_Port          online         offline       Not-logged-in
6      SL_Port          online         offline       Not-logged-in
7      SL_Port          online         online        logged-in      Initiator
Devices:  0   Address: 0x00

From the new T3, the following 'port list' output shows the targetid.

 port list

 port   targetid   addr_type   status   host   wwn
u1p1      1        hard       online   sun    50020f2300001234

targetid 1 = al_pa 0xe8 (which is already used by port 1).

Resolution
Because al_pa's are unique, the new T3 could not obtain the al_pa it was configured to use. Since it was not configured to obtain a soft address in this situation, the T3 couldn't join the loop. The switch shows this state as 'initiator' rather than the usual 'target'.

The resolution is to change the targetid (to an unused value) on the new T3 and issue a reset command.
example:

 port set u1p1 targetid 5
reset

Additional Information
Although the need for unique targetid's is well documented in the T3 manuals, the symptom of 'initiator' on a SL is not.


Product
Sun StorageTek Network 1 Gb FC Switch-8
Sun StorageTek 1 GB 16-Port Switch
Sun StorageTek T3+ Array
Sun StorageTek T3 Array

Internal Comments
For internal Sun use only.

Service Request ID: 37231380

Escalation ID: 1-3694237

Solution ID: 1-4190256

Owner GEO: EMEA

Customer GEO: EMEA

initiator, capture.sparc, SL, sanbox, T3
Previously Published As
78497

Change History
Date: 2004-10-13
User Name: 7058
Action: Approved
Comment: Added trademark info.
Much of the problem info was in the solution area. Moved it up to the problem area.
Added needed punctuation in right places and fixed a few small grammar problems.
Enabled STM to offset preformatted text.
Spellcheck OK
Publishing.
Version: 4
Date: 2004-10-12
User Name: 7058
Action: Accept
Comment:
Version: 0
Date: 2004-10-11
User Name: 92689
Action: Approved
Comment: thanks brian
Version: 0
Product_uuid
0e4a2a4f-d43b-11d8-ab52-080020a9ed93|Sun StorageTek Network 1 Gb FC Switch-8
ad1234c3-d43b-11d8-ab52-080020a9ed93|Sun StorageTek 1 GB 16-Port Switch
2a714b10-0a18-11d6-86e2-d56b387d4fbf|Sun StorageTek T3+ Array
2a6d7d50-0a18-11d6-8e0b-f0bd33b24928|Sun StorageTek T3 Array

Attachments

This solution has no attachment