SCSI Targets return the following status codes to indicate the “status” of a request made to in by a SCSI Initiator.
Value Description
00h GOOD
02h CHECK CONDITION
04h CONDITION MET
08h BUSY
10h INTERMEDIATE
14h INTERMEDIATE-CONDITION MET
18h RESERVATION CONFLICT
22h Obsolete
28h TASK SET FULL
30h ACA ACTIVE
40h TASK ABORTED
Others Reserved
The Fibre Channel Login process is a simple mechanism of an N_Port (node port) discovering the entity it is attached to and sequentially requesting the owner of each entity to pass thru till it has established a session with another N_Port.
1. The Initiator Sends our an FLOGI (Fabric Login Request)
2. If the FLOGI response is LS_RJT, the initiator resends FLOGI (till the max retry count expires).
3. If the FLOGI response is ACCEPT, that indicates that the initiator has a link to a fabric/target. Initiator issues a PLOGI (Port Login Request).
4. If the PLOGI response is LS_RJT, the initiator resends PLOGI (till the max retry count expires).
5. If the PLOGI response is ACCEPT, this indicates that the initiator is now permitted to talk to the process (or service) that is being hosted on this port. So the initiator sends out a PRLI (Process Login Request).
6. If the PRLI response is LS_RJT, the initiator resends PRLI (till the max retry count expires).
7. If the PRLI response is ACCEPT, that indicates that the initiator is successfully connected to the target, and now SCSI FCP operations can be performed. This is like the full feature phase where the initiator can issue SCSI commands, send and receive data, and receive SCSI command response & status issued by the target device.
Once the initiator is done, it can gracefully perform a logout as follows:
8. The initiator sends a PRLO (Process Logout Request) to the target.
9. If the PRLO response is LS_RJT, the initiator retries the Logout.
10. If the PRLO response is ACCEPT, the initiator sends our LOGO (Port logout Request).
11. If the LOGO response is LS_RJT, the initiator retries the Logout.
12. If the LOGO response is ACCEPT, the session ends.
This is a simplified version of the login logout process, and doesn’t take into consideration the operations that happen when the initiator is typically connected in a fabric environment (in which case the initiator logs into different fabric services like the management server, directory server and queries the fabric to get target information).
I’ll try to put up the login sequence of such an environment with details on all the associated process soon.
Switch# config t
Switch(config)# service unsupported-transceiver
Switch(config)# copy running-config startup-config
Switch(config)# reload
Steps to Configure FCoE Port Mirroring
Example:
Source(monitored) Port: 35
Destination(monitoring) Port: 6
Monitor session id: 2
Commands:
———
switch# configure terminal
switch(config)# no monitor session all
switch(config)# monitor session 2
switch(config)# interface ethernet 1/6
switch(config-if)# lldp transmit
switch(config-if)# lldp receive
switch(config-if)# priority-flow-control mode auto
switch(config-if)# switchport mode trunk
switch(config-if)# spanning-tree port type edge trunk
switch(config-if) # switchport trunk allowed vlan 1,1002
switch(config-if) # no shut
switch (config)# interface vfc 6
switch (config-if)# no bind interface ethernet 1/6
switch(config-if)# exit
switch(config)# interface ethernet 1/6
switch(config-if)# switchport monitor
switch(config-if)# exit
switch(config)# monitor session 2
switch(config-monitor)# destination interface ethernet 1/6
switch(config-monitor)# source interface vfc 35
switch(config-monitor)# source vlan 1002
switch(config-monitor)# no shut
Reference: Click Here.
1. Create qos class in switch.
FCF4(config)# class-map type qos
2. Create network-qos class in switch.
FCF4(config-cmap-qos)# class-map type network-qos
FCF4(config-cmap-nq)# pollicy-map type network-qos
FCF4(config-cmap-nq)# class type network-qos class-default
3. Change the MTU size
FCF4(config-cmap-nq-c)# mtu 9216
FCF4(config-cmap-nq-c)# system qos
FCF4(config-sys-qos)# service-policy type network-qos
1. Create a zone and add ports.
FCF4(config)# zone name zone1 vsan 1
For WWN zoning, add port name of storage and CNA (recommended)
FCF4(config)# member pwwn < WWN of storage and/or CNA >
For port zoning, add the fc port as member of the zone
FCF4(config)# member interface fc x/1 < x is FC port you want to include in zone >
FCF4(config)# member fwwn < WWN of VFC X created above >
2. Add zone to zoneset and activate.
FCF4(config)# zoneset name zoneset1 vsan 1
FCF4(config)# member zone1
FCF4(config)# zoneset activate name zoneset1 vsan 1
Script to Configure the Ethernet Port for FCoE traffic and enable DCBX for all the ports in the FCoE Switch
#!/bin/sh
SWITCH=172.35.10.129
(
sleep 5
echo admin
sleep 5
echo <password>
sleep 5
echo “configure”
sleep 5
for (( i = 1 ; i < = 20; i++ ))
do
echo “interface ethernet 1/$i”
sleep 5
echo “lldp transmit”
sleep 5
echo “lldp receive”
sleep 5
echo “priority-flow-control mode auto”
sleep 5
echo “switchport mode trunk”
sleep 5
echo “no shutdown”
sleep 5
echo “interface vfc $i”
sleep 5
echo “bind interface Ethernet 1/$i”
sleep 5
echo “no shutdown”
sleep 5
echo “exit”
sleep 5
done
) | telnet $SWITCH
Steps to Create FCoE Ports
1. Enable fcoe and NPIV.
FCF4# Config terminal
FCF4(config)# feature fcoe
2. Create VLAN for FcoE traffic and map it to VSAN.
FCF4(config)# vlan 1002
FW-FCF4(config-vlan)# fcoe vsan 1
3. Reboot the switch
FCF4# copy running-config startup-config
FCF4# reload
4. Configure the Ethernet port for FcoE traffic and enable DCBX
FW-FCF1(config)# interface ethernet 1/x
FW-FCF1(config-if)# lldp transmit
FW-FCF1(config-if)# lldp receive
FW-FCF1(config-if)# priority-flow-control mode auto
FW-FCF1(config-if)# switchport mode trunk
FW-FCF1(config-if)# spanning-tree port type edge trunk
FW-FCF1(config-if)# switchport trunk allowed vlan 1,1002
FW-FCF1(config-if)# no shutdown
5. Create a VFC and bind it to Ethernet port.
FW-FCF1(config)# interface vfc x
FW-FCF1(config-if)# bind interface Ethernet 1/x
FW-FCF1(config-if)# no shutdown
1. Configure adapter and target/lun in zone (Configuration required on Switch & Target side so that the host can access the LUN)
2. After installing adapter, during system POST at the QLE8042 BIOS info press control-Q when prompted
3. At adapter menu select adapter (function 0 is port0, function 1 port1)
4. At Fast!UTIL menu select configuration settings -> adapter settings and enable Host Adapter BIOS, escape key back to Fast!UTIL menu
5. Select Selectable Boot Settings, Enable Selectable Boot
6. Arrow down to Boot Port Name, Lun: and enter
7. Zoned target should now be listed in available Fibre Channel Devices, enter
8. Available luns should now be listed, select lun
9. Escape out and save changes
10. Reboot -> now when QLE8042 BIOS POSTS you should see target information
11. Once system recognizes target in POST, run system setup and set primary boot device as the FCoE adapter, or slot FCoE adapter is installed (depending on system BIOS how the boot device is defined and saved varies from system to system)
12. Save and reboot
13. At this point we PXE boot to an OS install server or CD/DVD Media to install OS
Configuring Newly Added Initiator
1. Add the target IP (ABC.DEF.GH.IJ) via the application and save the configuration
2. The initiator IQN will appear in Navisphere at Storage Domains -> Local Domain -> CKM…[CX4-120] -> Connectivity status
3. Creating Storage group for the first time. Storage Domains -> Local Domain -> CKM…[CX4-120] -> Storage Groups -> Create storage group
4. Newly created storage group will have Hosts and LUNS fields
Mapping LUNs to the Initiator
1. Add new host storage group -> Connect Hosts -> select host(s) -> add
2. Add new luns to host storage group -> connect LUNS -> select luns to add via SPA or SPB
