Hi have a problem whit one FC-port on a 7200 2 node system.
The port 1:2:1 doesnt show in MC?
In cli it shows as below
1:2:1 target loss_sync 2FF70002AC004C78 21210002AC004C78 iport FC - -
Tried to set mode to target and topology to fabric and type to host whit controlport .....
Port type = iport
-
PearMotion
- Posts: 12
- Joined: Wed Jan 02, 2013 8:13 am
- Location: UK
Re: Port type = iport
Its a bug where the port can get itself into a crazy factory test state. The Gui does not recgnise the port type property.
To fix it remove the SFP's then use the control port command in the CLi to change the port type. Then put the SFP's back in.
This bug can occur if you set up your 3par (smartstart OR out of box via serial) with the SFP's plugged in, (best to remove ALL connections apart from cat to management ports when settng up) or it can come from factory in that mode, especially in the early build models or on demo units.
To fix it remove the SFP's then use the control port command in the CLi to change the port type. Then put the SFP's back in.
This bug can occur if you set up your 3par (smartstart OR out of box via serial) with the SFP's plugged in, (best to remove ALL connections apart from cat to management ports when settng up) or it can come from factory in that mode, especially in the early build models or on demo units.
PEAR-Motion
2xNode 3PAR StoreServ 7200
4xNode 3PAR Storeserv 7400 with LFF and SFF
2xNode 3PAR Storeserv 10400
2xNode 3PAR StoreServ 7200
4xNode 3PAR Storeserv 7400 with LFF and SFF
2xNode 3PAR Storeserv 10400
Re: Port type = iport
We had the same problem while we were configuring a new SAN-switch our 3PAR V400 was connected to. Temporary the default zoning on this switch was set to all access! So all ports (host+rcfc) could see eachother and went into this weird iport-state.
A port type change in the CLI didn't solve the problem. Only a reboot of the whole array fixed it.
A port type change in the CLI didn't solve the problem. Only a reboot of the whole array fixed it.