C H A P T E R 6 |
Configuring IPFC SAN Devices |
Configuring IPFC on the host system, describes host recognition of IPFC devices and implementation of IP over FC in a SAN. The IPFC driver is based on RFC 2625 and it allows IP traffic to run over FC.
This chapter contains the following topics:
The following table shows the supported features available for IPFC.
Fabric zone (with the HBA configured as an F-port point-to-point connection) |
|
The following restrictions apply:
This section explains how to configure the desired host system for IPFC. It includes the procedures to determine the port instance and to plumb an IPFC instance.
To Determine Port Instances |
1. Determine the HBA PCI adapter slot and the I/O board PCI slot.
You need this information to perform the calculation in Step 2.
For example, assume you have an array with an HBA card located in PCI adapter slot 5, and the PCI adapter is in slot 1 of the I/O board.
2. Determine the instance number.
a. Use an editor to search for the fp driver binding name in the
/etc/path_to_inst file.
b. Narrow the search by using the I/O board and slot information from Step 1.
Note - The following method of deriving the Solaris 10 device path of an HBA from its physical location in server may not work for all Sun server hardware. |
i. Multiply the PCI adapter slot number by the number of adapter ports.
For example, if the HBA has two ports, multiply by 2. Using the array with an HBA in the PCI adapter slot 5, multiply 5 by 2 to get 10.
ii. Add the PCI adapter I/O board slot number to the number derived in Step i.
Using an HBA in PCI adapter slot 5 and PCI slot 1 of the I/O board, add 1 to 10 for a sum of 11.
iii. Convert the number derived in Step ii to hexadecimal.
The number 11 converts to b in hexadecimal.
iv. Search for the fp entry with pci@hex where hex is the number you derived in Step iii.
The following Table 1-2, shows a single FC network adapter device path and describes the elements of the device path.
PCI Single FC Network Adapter Device Path.
3. Manually plumb each FP instance.
Use the ifconfig <interface_number> plumb command. In this example, the value of <interface_number> is fcip7.
When the command is successful, a message appears on both the console and in the messages file. For example:
Sep 13 15:52:30 bytownite ip: ip: joining multicasts failed (7) on fcip0 - will use link layer broadcasts 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.
1. 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:
2. 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.
3. List the physical path of the originating HBA port from which you can see the destination HBA port, where originating-hba-link is a variable for the link determined in Step 2.
For example, here 0 is the number for the originating-hba-link:
# ls -l /dev/fc/fp0 lrwxrwxrwx 1 root root 51 Sep 4 08:23 /dev/fc/fp0 -> ../../devices/pci@8,600000/SUNW,qlc@1/fp@0,0:devctl |
4. Search the physical path identified in Step 3.
You must remove the leading ../../devices from the path name output. For example
5. Determine the fp instance for the originating HBA port from the output of the command in Step 4.
The instance number precedes "fp" in the output. In the following example output, the instance number is 0.
6. Use the instance number from Step 5 to load IPFC and plumb the IPFC interface.
In this example, the instance is 0.
Immediately upon installation, start IPFC manually with the ifconfig command. You can configure the host so that on subsequent reboot, the IPFC network interface starts automatically. This section describes the procedures to start a network interface manually and to configure the host for automatic plumbing upon reboot.
To Start a Network Interface Manually |
Use this procedure when you want to plumb IPFC with specific netmask values and get the IPFC interface up and running.
1. Use the ifconfig command with the appropriate interface.
Ask your network administrator for an appropriate IP address and netmask information. For example, to enable an IPFC interface associated with fp instance 0 and an IP address of 192.9.201.10, type:
The ifconfig command is described in more detail in the ifconfig(1M) manpage.
2. Use the command ifconfig -a to verify the network is functioning.
The output of ifconfig -a should look like this:
To Configure the Host for Automatic Plumbing Upon Reboot |
Each network interface must have an /etc/hostname.interface file defining the name of the IP address associated with it. For example, IPFC network interface fcip0 has a file named /etc/hostname.fcip0.
1. Manually create a /etc/hostname.interface file with a text editor so it contains a single line that identifies the host name or interface IP address.
2. Use a text editor to make any additional entries to the /etc/inet/hosts file.
The Solaris 10 installation program creates the /etc/inet/hosts file with minimum entries. You must manually make additional entries with a text editor. (See the hosts(4) man page for additional information.)
The /etc/inet/hosts file contains the hosts database. This file contains the host names and the primary network interface IP addresses, as well as the IP addresses of other network interfaces attached to the system and of any other network interfaces that the machine must know about.
The following code shows an example of an etc/inet/host file.
127.0.0.1 localhost loghost 192.9.200.70 sun1 #This is the local host name 192.9.201.10 fcip0 #Interface to network 192.9.201.10 |
3. Edit the /etc/nsswitch.conf file so that all un-commented entries have the word files before any other name service.
The /etc/nsswitch.conf specifies which name service to use for a particular machine. The following code shows an example of an /etc/nsswitch.conf file.
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.