An example below is a servrer that had issues.
Note that this server / initiator is only configured on filer-prod-201 and not on the filers that had maintenecane going on:
$ ssh root@filer-prod-201 igroup show -v mc202bpmdb-01-ports mc202bpmdb-01-ports (FCP): OS Type: linux Member: 50:01:43:80:18:6a:f7:6c (logged in on: vtic, 0c) Member: 50:01:43:80:18:6a:f7:6e (not logged in) Member: 50:01:43:80:18:6b:00:2c (logged in on: vtic, 0d) Member: 50:01:43:80:18:6b:00:2e (not logged in) UUID: 437bce6a-f8c7-11e1-8651-00a0981ad474 ALUA: Yes
$ ssh root@filer-prod-204 igroup show -v | egrep "50:01:43:80:18:6a:f7:6c|50:01:43:80:18:6b:00:2c"
$ ssh root@filer-prod-203 igroup show -v | egrep "50:01:43:80:18:6a:f7:6c|50:01:43:80:18:6b:00:2c"
On Mon, Feb 2, 2015 at 1:09 PM, Basil basilberntsen@gmail.com wrote:
I'd like to see what your nodes think the WWNs of the servers are. If you do an igroup show -v on each ones, do you see the same WWNs for each host?
On Mon, Feb 2, 2015 at 5:25 AM, Momonth momonth@gmail.com wrote:
Hi All,
I hit the following bug on one of the filer (FAS3260) I manage:
http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=659544
This filer (filer-prod-204) works in HA mode with filer-prod-203. They are connected to two redundant FC SAN fabrics (one connection from each filer per fabric). There are more HA pairs connected to the same fabrics, eg filer-prod-201 / filer-prod-202. All of the filers we have are running in 'single-image' mode. We run FC SAN fabrics in "hard zoning mode".
NetApp support conclusion was to replace motherboard on the filer and we proceeded with that.
Here is an issue we had and I have no explanation to that, I hope you guys can help me with that:
Once the filer-prod-204 got the motherboard replaced, powered on and entered HW diagnostics mode I've seen the messages as below *on every other filer* (eg. filer-prod-201), connected to the same fabric, causing issues on hosts (CentOS 6.4 mainly) attached to them:
Fri Jan 30 20:07:45 CET [filer-prod-201: scsitarget.ispfct.targetReset:notice]: FCP Target 0c: Target was Reset by the Initiator at Port Id: 0x11000 (WWPN 5001438021e071ec) Fri Jan 30 20:07:46 CET [filer-prod-201: scsitarget.ispfct.targetReset:notice]: FCP Target 0c: Target was Reset by the Initiator at Port Id: 0x10200 (WWPN 50014380186abac4) ...
Fri Jan 30 20:08:14 CET [filer-prod-201: scsitarget.ispfct.portLogin:notice]: FCP login on Fibre Channel adapter '0c' from '50:01:43:80:21:e0:71:ec', address 0x11000. Fri Jan 30 20:08:14 CET [filer-prod-201: scsitarget.ispfct.portLogin:notice]: FCP login on Fibre Channel adapter '0c' from '50:01:43:80:18:6a:ba:c4', address 0x10200.
So every single initiator on the filer *not involved* in the maintenance were reset, then tried to login back, reset again and it looped like that until I disabled filer-prod-204's target ports on the FC switches. Once the filer-prod-204 booted up with OnTAP, the issue was gone. I know it because when I tried to re-enabled the filer-prod-204's target ports, I didn't see any message like above and everything is running fine since then.
Does anyone have an idea what was happing here and why?
Cheers, Vladimir _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters