Incorrect fabric WWN and path_to_inst Solaris 9


 
Thread Tools Search this Thread
Operating Systems Solaris Incorrect fabric WWN and path_to_inst Solaris 9
# 1  
Old 08-03-2011
Incorrect fabric WWN and path_to_inst Solaris 9

Hi,

Over a period of time we gradually migrated all LUN's from our HP EVA array over to our EMC array. From the server it would appear some files require a tidy up and was wondering what the impact it would have if changes were to be made to the fabric_WWN_map and path_to_inst files and if there is a correct procedure in doing this.

The fabric_WWN_map file is still configured with entries to the HP array.

Code:
 
/devices/pci@9,600000/SUNW,qlc@1/fp@0,0:fc::100000e00202b56f
/devices/pci@9,600000/SUNW,qlc@1/fp@0,0:fc::50001fe15000de38 HP
/devices/pci@9,600000/SUNW,qlc@1/fp@0,0:fc::50001fe15000de39
/devices/pci@9,600000/SUNW,qlc@1/fp@0,0:fc::50001fe15000de3b
/devices/pci@9,600000/SUNW,qlc@1/fp@0,0:fc::50001fe15000de3d
/devices/pci@9,600000/SUNW,qlc@1/fp@0,0:fc::50001fe15000de3f
/devices/pci@9,600000/SUNW,qlc@1/fp@0,0:fc::500601633b202f83 EMC
/devices/pci@9,600000/SUNW,qlc@1/fp@0,0:fc::5006016a3b202f83
/devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::100000e00202b570
/devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::50001fe15000de38 HP
/devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::50001fe15000de39
/devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::50001fe15000de3a
/devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::50001fe15000de3c
/devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::50001fe15000de3e
/devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::500601623b202f83
/devices/pci@9,600000/SUNW,qlc@2/fp@0,0:fc::5006016b3b202f83 EMC

The path_to_inst file still has the following entries

Code:
 
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,2d" 4523 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,2c" 4524 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,2b" 4525 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,2a" 4526 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,29" 4527 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,28" 4528 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,15" 4529 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,e" 4530 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,d" 4531 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,b" 4532 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,a" 4533 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,5" 4534 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,3" 4535 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,2" 4536 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de39,1" 4537 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,2d" 4538 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,2c" 4539 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,2b" 4540 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,2a" 4541 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,29" 4542 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,28" 4543 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,15" 4544 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,e" 4545 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,d" 4546 "ssd"
"/pci@9,600000/SUNW,qlc@1/fp@0,0/ssd@w50001fe15000de3b,b" 4547 "ssd"

truncated

Is it safe to manually remove these entries? There is no device files in /dev/dsk


The path_to_inst also contains the following

Code:
 
"/scsi_vhci/ssd@g600508b400074464000100000a620000" 422 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000a790000" 423 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000a7d0000" 424 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000a810000" 425 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000a920000" 426 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000a960000" 427 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000a9a0000" 428 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000aab0000" 429 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000aaf0000" 430 "ssd"
"/scsi_vhci/ssd@g600508b400074464000100000ab30000" 431 "ssd"

What are these and can they be removed?


All other configuration looks ok, there are no old occupants for the HP array.

[
Code:
root@sperprod01 /etc/cfg/fp]# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c0                             scsi-bus     connected    configured   unknown
c0::dsk/c0t0d0                 CD-ROM       connected    configured   unknown
c1                             fc-private   connected    configured   unknown
c1::2100000c501b902e           disk         connected    configured   unknown
c1::2100000c501b95a0           disk         connected    configured   unknown
c1::2100000c501b97ac           disk         connected    configured   unknown
c1::2100000c501b9841           disk         connected    configured   unknown
c1::21000011c6e4f23e           disk         connected    configured   unknown
c1::2100001d387c6d65           disk         connected    configured   unknown
c1::50800200001e41c9           ESI          connected    configured   unknown
c2                             fc-fabric    connected    configured   unknown
c2::500601633b202f83           disk         connected    configured   unknown
c2::5006016a3b202f83           disk         connected    configured   unknown
c3                             fc-fabric    connected    configured   unknown
c3::500601623b202f83           disk         connected    configured   unknown
c3::5006016b3b202f83           disk         connected    configured   unknown
pcisch0:hpc1_slot0             unknown      empty        unconfigured unknown
pcisch0:hpc1_slot1             unknown      empty        unconfigured unknown
pcisch0:hpc1_slot2             unknown      empty        unconfigured unknown
pcisch0:hpc1_slot3             ethernet/hp  connected    configured   ok
pcisch2:hpc2_slot4             ethernet/hp  connected    configured   ok
pcisch2:hpc2_slot5             unknown      empty        unconfigured unknown
pcisch2:hpc2_slot6             unknown      empty        unconfigured unknown
pcisch3:hpc0_slot7             fibre/hp     connected    configured   ok
pcisch3:hpc0_slot8             fibre/hp     connected    configured   ok

Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Need WWN

How do I identify the WWN of associated SAN through a logical volume that is mounted on a RHEL 6 system (2 Replies)
Discussion started by: nixhead
2 Replies

2. AIX

How to ssh from an AIX OS server to a Fabric OS server without password?

Hi I'd like to ssh from an AIX OS server ( v5.3) to a Fabric OS server ( v6.1.2 ) without password. I tried using dsa or rsa keys but it didn't work, the aix server still asked for the password. Somebody help, please :(:(:( (8 Replies)
Discussion started by: bobochacha29
8 Replies

3. Solaris

How to get LUN WWN in Solaris?

How to get LUN WWN (i.e LUN mapped from a storage box say Symmetrix or clariion) in Solaris. fcinfo command does give the Target port wwn but what i'm looking for is the LUN WWN. Any help is appreciated. (2 Replies)
Discussion started by: Manish00712
2 Replies

4. Solaris

[Solved] Solaris 10 - Ftp Login incorrect

Hey everyone, I am trying to get a 2GB patch cluster FTP'd to a solaris 10 server. I have tried logging in via ftp, and both with root as well as my personal account, I get "Login Incorrect." I have verified that I can log in using telnet. -bash-3.00$ netstat -a |grep ftp *.ftp ... (10 Replies)
Discussion started by: msarro
10 Replies

5. Solaris

path_to_inst file question

When path_to_inst file get created? Can we manually edit it? Thanks (2 Replies)
Discussion started by: mokkan
2 Replies

6. UNIX for Dummies Questions & Answers

path_to_inst output for usb storage device

Hello, I have a sun blade 100 with solaris 10 and am perplexed by the instances of devices that I see when I attach a usb flash stick to one of the ports in the back of the chassis. Here is what I see for USB storage in /etc/path_to_inst: "/pci@1f,0/usb@c,3/storage@3" 0 "scsa2usb"... (0 Replies)
Discussion started by: montana77
0 Replies

7. Filesystems, Disks and Memory

Fabric Operating System

Would any of your gentlemen have come across a decent reference for the FOS in your wanderings? Brocade just seems to want to sell me classes and FAN books :/ (0 Replies)
Discussion started by: Eronysis
0 Replies

8. Filesystems, Disks and Memory

/etc/path_to_inst

Hello Friends I was using V490 server with StoreEdge 3500 on Solaris 5.8 platform. It got crashed when the optical link between 3500 and V490 got failed. After a long effort it is now getting messege like below, Rebooting with command: boot Boot device:... (6 Replies)
Discussion started by: ailnilanjan
6 Replies

9. Solaris

Wwn

hiho peeps, is there a possibility to see the WWNs of your SAN-HBAs, like in ifconfig the MAC-addresse.....??? greetings Pressy (1 Reply)
Discussion started by: pressy
1 Replies

10. Solaris

cannot open /etc/path_to_inst file

In trouble... booted system and error on prom is "cannot open /etc/path_to_inst file" Any suggestions? (4 Replies)
Discussion started by: frustrated1
4 Replies
Login or Register to Ask a Question