Ok, what about:
vserver fc show ? is fc actually on at the svm?

and:
system node run -node na101node-* fcadmin config
network fcp adapter modify -node na101node-* -adapter port -state up

What is the output from these command?

--tmac

On Fri, Nov 28, 2014 at 8:09 AM, <basilberntsen@gmail.com> wrote:
The portcfgreport says that NPIV is enabled on that port.

Sent from my BlackBerry 10 smartphone on the Bell network.
From: tmac
Sent: Friday, November 28, 2014 7:53 AM
To: Vladimir Zhigulin
Subject: Re: FCP Ports operational down

Are you absolutely sure you NPIV enabled at the switch?
This is mandatory and mentioned in the admin guide and probably other places as being needed.



--tmac

On Fri, Nov 28, 2014 at 5:39 AM, Momonth <momonth@gmail.com> wrote:
I've got exactly the same issue with FAS8040 4 nodes cluster, running
8.2.1 and 8.2.2

However it's not HBA HW related as I've got similar cluster in 2nd DC
and it works just fine with the same HBA on filers.

On-board ports (I don't have any SAN svm configured):

na101::*> network fcp adapter show -node na101node-* -fields
switch-port,fc-wwpn -adapter 0e
node         adapter fc-wwpn                 switch-port
------------ ------- ----------------------- --------------
na101node-1a 0e      50:0a:09:87:80:71:20:df fca-core-101:0
na101node-1b 0e      50:0a:09:87:80:01:21:93 fca-core-101:1
na101node-2a 0e      50:0a:09:87:80:01:1f:7f fca-core-101:40
na101node-2b 0e      50:0a:09:87:80:01:20:9e fca-core-101:41
4 entries were displayed.

Slot 3 ports:

na101::*> network fcp adapter show -node na101node-* -fields
switch-port,fc-wwpn -adapter 3a
node         adapter fc-wwpn                 switch-port
------------ ------- ----------------------- -----------
na101node-1a 3a      50:0a:09:81:80:71:20:df :
na101node-1b 3a      50:0a:09:81:80:01:21:93 :
na101node-2a 3a      50:0a:09:81:80:01:1f:7f :
na101node-2b 3a      50:0a:09:81:80:01:20:9e :
4 entries were displayed.

I just upgraded to 8.2.2 and it didn't resolve the issue.

Some more details:

fcb-core-101:FID128:admin> portcfgshow 40
Area Number:  40
Octet Speed Combo:  1(16G|8G|4G|2G)
Speed Level:  AUTO(SW)
AL_PA Offset 13:  OFF
Trunk Port  ON
Long Distance  OFF
VC Link Init  OFF
Locked L_Port  OFF
Locked G_Port  OFF
Disabled E_Port  OFF
Locked E_Port  OFF
ISL R_RDY Mode  OFF
RSCN Suppressed  OFF
Persistent Disable  OFF
LOS TOV enable  OFF
NPIV capability  ON
QOS E_Port  AE
Port Auto Disable:  OFF
Rate Limit  OFF
EX Port  OFF
Mirror Port  OFF
Credit Recovery  ON
F_Port Buffers  OFF
Fault Delay:  0(R_A_TOV)
NPIV PP Limit:  255
CSCTL mode:  OFF
D-Port mode:  OFF
Compression:  OFF
Encryption:  OFF
FEC:  ON

fcb-core-101:FID128:admin> portshow 40
portIndex:  40
portName: na101node-2a_3a
portHealth: No Fabric Watch License

Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE
LOGIN NOELP LED ACCEPT FLOGI
LocalSwcFlags: 0x0
portType:  24.0
POD Port: Port is licensed
portState: 1 Online
Protocol: FC
portPhys:  6 In_Sync   portScn:   32 F_Port
port generation number:    114
state transition count:    7

portId:    c92800
portIfId:    4302001e
portWwn:   20:28:00:27:f8:bd:ec:1c
portWwn of device(s) connected:
21:00:00:24:ff:73:20:73
Distance:  normal
portSpeed:  N8Gbps

FEC: Inactive
LE domain: 0
FC Fastwrite: OFF
Interrupts:        0          Link_failure: 3          Frjt:         0
Unknown:           0          Loss_of_sync: 4          Fbsy:         0
Lli:               31         Loss_of_sig:  7
Proc_rqrd:         32         Protocol_err: 0
Timed_out:         0          Invalid_word: 0
Rx_flushed:        0          Invalid_crc:  0
Tx_unavail:        0          Delim_err:    0
Free_buffer:       0          Address_err:  0
Overrun:           0          Lr_in:        4
Suspended:         0          Lr_out:       4
Parity_err:        0          Ols_in:       4
2_parity_err:      0          Ols_out:      4
CMI_bus_err:       0

na101::*> ucadmin show -node na101node-2a -adapter 3a -instance

               Node: na101node-2a
            Adapter: 3a
       Current Mode: fc
       Current Type: target
       Pending Mode: -
       Pending Type: -
             Status: online
    Supported Modes: fc
 Supported FC Types: initiator, target
Supported CNA Types: -

It feels like Im missing something obvious .. any help is appreciated.

Cheers,
Vladimir

On Tue, Jun 17, 2014 at 7:40 AM, Alexander Griesser <ag@anexia.at> wrote:
> No part numbers on them, I did also check.
> You can just see the SFP manufacturer + model in the sysconfig -a output, but that's about it - no indication of whether they're compatible with what card or something like this.
>
> Support is working through the new CA output now and will update me if on the SAS cabling issue afterwards, all other warnings in CA 3.5 are just related to firmware (new one got released) and port mismatch which is to be expected at the moment since I'm running an asymmetric configuration right now.
>
> Best,
>
> Alexander Griesser
> System-Administrator
>

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters



_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters