05-27-2014
VIOS - fibre adapters not seeing luns
Hi guys,
I've been trying to tackle this issue for days and I'm stumped. Hopefully someone can give more light on what else I can do.
I have a p7 series box, with dual VIOS and 10 lpars and everything was working fine until I had to move the box to another location in the data centre. Ensured I labelled where each cable went etc.
Upon powering on the p7 server, it came up fine into standby mode. Then powered on the system. After that, I then powered on the VIOS (Primary) server and that came up fine and booted into the OS. (Each VIOS server has 2 x dual ports dedicated fibre adapters) I then proceeded to boot each lpar successfully. Now, when I ran lspath on VIOS (Primary) it showed that the second adapter has failed path. I tried to re-enable it to no success. I thought I'd continue with VIOS (Secondary) and continue along, to my suprise, no luns were accessible to the server. I even tried to go to SMS Menu to use the SAN Zone support, and Open firmware prompt for ioinfo and no luns were displaying. (I am using SCSI adapters for the luns)
The list below is what I have tried and unsuccessful.
1 - have changed over the fibre cables to the adapter and no success
2 - have bypassed the fibre patch panel and directly to the fibre switch and no success
3 - confirmed we can see light coming through the fibre cables
4 - Changed switched ports on the fibre adapters
5 - wrap plug test and no success
6 - Used the fibre cable that is plugged into the working fibre adapter and used in the fibre adapter that has issues and still no success.
7 - I have confirmed that I can see the fibre adapters as available on the VIOS server
8 - I have removed the fibre adapters from the system and re configured them
9 - I have shutdown the system completely, removed power and reattached power and started up the system and no success
10 - I have physically removed the fibre adapters and reseated them
11 - I have provided IBM with a 'snap' which is the system configuration of the VIOS server - so far hardware support can't find any fault.
12 - I have screenshot my VIOS configuration profile to IBM - no issues here
13 - I have ran an exe program from IBM to determine transmit and receive and noise on the port and the ones not working don't output any information.
14 - I have moved the fibre adapters from the VIOS server to another LPAR and still have the same issues.
15 - On the back on the server, I can see there is power to the adapters with green flash lights, but no link activity.
16 - I have checked with IBM documentation that Green LED slow flash and no Yellow LED indicates - Normal, link inactive or not started.
Any input would be appreciated. Thanks.
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have variables like mentioned below and want to separate as mentioned in output.
var1="4 x fibre cards"
var2="2 fibre cards"
var3="6 - fibre cards"
var4="4 x dual-port"
I have variables like this.I want to separate numbers from this and fibre cards from this.
output has to be... (4 Replies)
Discussion started by: ajilesh
4 Replies
2. AIX
Hello,
When I try to upgrade AIX from 5.1 to 5.3 I get this error message
20EE0008 : No adapters found Adapter, Riser, System Bd.
Anyone know anything about it ? (1 Reply)
Discussion started by: filosophizer
1 Replies
3. Red Hat
Hi
I have 4 NIC's connected to my RHEL 5.3 server. Two on one subnet creating bond0, and two on a second subnet which create bond1. Both bonds are set to use DHCP to obtain IP addresses. Here is the config file for ifcfg-bond0:
DHCP_HOSTNAME=rrnltshckvmx001
DEVICE=bond0
BOOTPROTO=dhcp... (2 Replies)
Discussion started by: Padow
2 Replies
4. Windows & DOS: Issues & Discussions
I am trying to get my boss' ipad to print on our local printers, and rapidly coming to loathe the product.
After several false starts I'm attempting to use the free WePrint application, running on a Windows machine, to "forward" our printers from it to the ipad over the local network. I've hit... (2 Replies)
Discussion started by: Corona688
2 Replies
5. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
6. AIX
hi guys
BTW pretty new to VIO
I inherited 2 I BM Power Server - blades PS701 - One is already configured using en8
# lsdev -Cc adapter | grep ent
ent0 Available Logical Host Ethernet Port (lp-hea)
ent1 Available Logical Host Ethernet Port (lp-hea)
ent2 Available 04-20... (8 Replies)
Discussion started by: karlochacon
8 Replies
fp(7d) Devices fp(7d)
NAME
fp - Sun Fibre Channel port driver
DESCRIPTION
The fp driver is a Sun fibre channel nexus driver that enables fibre channel topology discovery, device discovery, fibre channel adapter
port management and other capabilities through well-defined fibre channel adapter driver interfaces.
The fp driver requires the presence of a fabric name server in fabric and public loop topologies to discover fibre channel devices. In pri-
vate loop topologies, the driver discovers devices by performing PLOGI to all valid AL_PAs, provided that devices do not participate in
LIRP and LILP stages of loop initialization.
CONFIGURATION
The fp driver is configured by defining properties in the fp.conf file. The fp driver supports the following properties:
mpxio-disable
Solaris I/O multipathing is enabled or disabled on fibre channel devices with the mpxio-disable property. Specifying mpxio-disable="no"
activates I/O multipathing, while mpxio-disable="yes" disables the feature.
Solaris I/O multipathing may be enabled or disabled on a per port basis. Per port settings override the global setting for the specified
ports. The following example shows how to disable multipathing on port 0 whose parent is /pci@8,600000/SUNW,qlc@4:
name="fp" parent="/pci@8,600000/SUNW,qlc@4" port=0
mpxio-disable="yes";
manual_configuration_only
Automatic configuration of SCSI devices in the fabric is enabled by default and thus allows all devices discovered in the SAN zone to be
enumerated in the kernel's device tree automatically. The manual_configuration_only property may be configured to disable the default
behavior and force the manual configuration of the devices in the SAN. Specifying manual_configuration_only=1 disables the automatic con-
figuration of devices.
FILES
/kernel/drv/fp
32-bit ELF kernel driver (x86)
/kernel/drv/amd64/fp
64-bit ELF kernel driver (x86)
/kernel/drv/sparcv9/fp
64-bit ELF kernel driver (SPARC)
/kernel/drv/fp.conf
fp driver configuration file.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|mpxio-disable |Unstable |
+-----------------------------+-----------------------------+
|manual_configuration_only |Obsolete |
+-----------------------------+-----------------------------+
|Availability |SUNWfctl |
+-----------------------------+-----------------------------+
SEE ALSO
cfgadm_fp(1M), prtconf(1M), stmsboot(1M), driver.conf(4), attributes(5), fcp(7D), fctl(7D), scsi_vhci(7D)
Writing Device Drivers
Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994
Fibre Channel Generic Services (FC-GS-2) Project 1134-D
Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996
Fibre Channel Protocol for SCSI (FCP) ANSI X3.269-1996
SCSI-3 Architecture Model (SAM) Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996
SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996
SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998
Fabric Loop Attachment (FC-FLA), NCITS TR-20:1998
SunOS 5.10 2 Dec 2004 fp(7d)