Sun Storage 6920 System
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
 

Content will be limited to a basic usage using the CLI or BUI interfaces for creating initiators, and provide help with some usage failure scenarios for this activity. Consider reviewing some of the following documents if you are looking to perform actions beyond the scope of this document:

• Best Practices for the Sun StorEdge 6920 System, Version 3.0.1
• Sun StorEdge 6920 System CLI Quick Reference Guide, Release 3.0
•  <Document: 1009915.1> Troubleshooting Sun StorEdge[TM] 6920 Configuration Problems
• Sun StorEdge 6920 System Administration Guide For the Browser Interface Management Software, Release 3.0

for help with other object creation activities.

A. Get the Host HBA WWN

For Solaris[TM] Operating System, you can get the Host BUS Adapter(HBA), World Wide Name (WWN) whether the HBA is connected into an existing Storage Area Network (SAN) or not.

Reference document < Solution: 216801 > Sun StorEdge[TM] SAN Software: How to Get the WWN of Sun FiberChannel HBAs for LUN Masking

For Microsoft Windows?, you can get the HBA WWN from the manufacturers utilities. Reference document <Document: 1006608.1> Microsoft Windows? operating system: How to obtain troubleshooting information for storage issues

For other operating systems, you will have to reference your HBA manufacturers user guides.

A WWN is a 16 Character, alphanumeric string that can be listed in the following
formats:

0123456789abcdef

or

01:23:45:67:89:ab:cd:ef

And is unique to each Fibre Channel port on an HBA.

Once you have collected the HBA WWN, continue to Step B

B. Creating the Initiator

SSCS

sscs create -w <WWN> initiator <initiator name>

example:

sscs create -w 0123456789abcdef initiator myhost_port1

This will create a single initiator, myhost_port1, with a WWN of 0123456789abcdef, in the DEFAULT storage domain, with an OS Type of Standard.

NOTE 1: The Storage Domain is assumed to be DEFAULT when it is not specified by the -S switch in the usage.

NOTE 2: The Standard OS Type is assumed when the -o is not specified.

NOTE 3: The WWN must be of the format 0123456789abcdef. A ":" in the name will not be accepted.

BUI

We consider basic Initiator creation as creating an initiator without mapping a volume.

1. Click Configuration Service or Common Array Manager link.
2. Click Physical Storage tab or menu tree.
3. Click the New button. This will open a pop-up window. You will need to have pop-ups enabled to complete this task. If a new window does NOT appear or if an error message appears on the main page, go to Step C.
4. Select the Storage Domain, and click Next.
5. Fill in the name, OS Type, and the WWN. WWN only accepts 16 characters. Make sure to remove any ":" characters.
6. Click Next.
7. Click Next again to skip mapping to this new initiator.
8. Click Finish after reviewing the Summary page

At this point the Pop-Up window will disappear, and the main browser screen will refresh, and a success or failure message will be displayed in the Initiator Summary page, and the volume will be listed in this page, sorted alphanumerically.

• If you received a failure notification, continue to Step C.
• If you received a success notification, you have validated that Initiator creation is complete.

C. Creation Failure.

BUI
Message:
<initiator> - Initiator WWN must be specified as 16 characters.

Action:
The initiator string was too short. Make sure that the initiator is 16 characters with no ":"'s, and repeat Step B.

Message:
An error occurred. Please contact your system administrator

Action:
Please go to Step D.

SSCS
Message:
An internal error occurred; Operation failed

Action:
Check the WWN entered in the CLI for the correct characters numeric characters. Characters can any combination of 16 characters 0-9 and a-f. Remove them, and repeat Step B.

Message:
<initiator> Initiator wwn must be specified as 16 characters.

Action:
The WWN is too long or too short. It must be exactly 16 characters in length.

Message:
<domain>: The resource was not found.

Action:
Make sure that the domain is typed correctly, or exists(sscs list sdomain)

Message:
Error: operation failed

Action:
Please go to Step D.

If a message is not listed or the actions did not work, go to Step D.

D. Data Collection

• 6920 Solution Extract, Reference document <Document: 1003756.1>  Sun StorEdge[TM] 6920 Health Checklist
• Solaris Explorer, Reference document <Document: 1006990.1> Sun[TM] Explorer Implementation Best Practice
• Windows data, Reference document <Document: 1006608.1>  Microsoft Windows? operating system: How to obtain troubleshooting information for storage issues
• The message given by SSCS or BUI(screen capture if possible)
• The command used, if by SSCS
• The input and selections for the new initiator wizard in the BUI
• The following sscs output:

sscs list sdomain
sscs list -S sdomain initiator

NOTE 4: Screen captures of the summary page for each object could be used, as well, for BUI related creations.

Once this information is collected, please contact Sun Support

E. Validate command provided

Validate command provided against examples in the Sun StorEdge 6920 System CLI Quick Reference Guide, Release 3.0.

Ensure that options are valid based on the usage available in reference guide.

F. error occurred

If the customer reports:

An error occurred. Please contact your system administrator

OR

Error: The operation failed.

Validate the services on the Service Processor. Reference document <Document: 1007129.1> Validating Services on a Sun StorEdge 6920 Service Processor

G. Escalate

Please have collected:

• Everything in Step D.


• Which step in this document you stopped at

and Escalate to your next level of support.

This solution has no attachment