User`s guide
iv. Search for the fp entry with pci@ hex where hex is the number you derived in Step iii.
The following table shows the elements of the device path for a PCI single FC network
adapter device that has the following path:
"/pci@b,2000/SUNW,qlc@2/fp@0,0" 7 "fp"
Entry Item Entry Value
Physical Name /pci@b,2000/SUNW,qlc@2/fp@0,0
Instance Number 7
Driver Binding Name fp
c. Manually plumb each FP instance.
Use the ifconfig interface-number plumb command. In this example, the value of
interface-number is fcip7.
# ifconfig fcip7 plumb
When the command is successful, a message appears on both the console and in the
messages le. For example:
Sep 13 15:52:30 bytownite ip: ip: joining multicasts failed (7) on fcip0 -
will use link layer brocasts for multicast
▼
To Plumb an IPFC Instance
Each FP instance on the system has an entry in /dev/fc. If HBAs have been removed, some
stale links might exist. Use this procedure to load and plumb IPFC.
For each entry in /dev/fc, issue a luxadm -e dump_map command to view all the devices that
are visible through that HBA port:
# luxadm -e dump_map /dev/fc/fp0
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 610100 0 210000e08b049f53 200000e08b049f53 0x1f (Unknown Type)
1 620d02 0 210000e08b02c32a 200000e08b02c32a 0x1f (Unknown Type)
2 620f00 0 210000e08b03eb4b 200000e08b03eb4b 0x1f (Unknown Type)
3 620e00 0 210100e08b220713 200100e08b220713 0x1f (Unknown Type,Host Bus Adapter)
# luxadm -e dump_map /dev/fc/fp1
No FC devices found. - /dev/fc/fp1
Based on the list of devices, determine which destination HBAs are visible to the remote host
with which you want to establish IPFC communications.
In the example for this procedure, the destination HBAs have port IDs 610100 and 620d02. The
originating HBA’s port ID is 620e00.
1
2
IPFC Considerations
Chapter 7 • Conguring IPFC SAN Devices 61