So to recap. ONLY onboard FC cards can have their personality changed. here is a step by step procedure we have written and used. use at your own risk of course 😉
Also, this is only a cut and paste so you will have to format it youself.
Cheers,
Eric
High Level Steps:
Check Cluster state
Login to contoller RLM (important as reboot will occur)
Cluster failover to cluster partner
Check configuration
Change configuration
Reboot
Check configuration
Cluster giveback
Check cluster status from controller 01B:
01B> cf status > Look for “Cluster enabled, 1A is up.”
On the partner of the controller that will have its FC port(s) change issue a cluster failover.
01B> cf takeover > wait unil completed
Wait until takover has been completed, check failover is complete:
01B> cf status > Look for message stating failover has completed and in takeovermode
1.1.1 Login to RLM/BMC on 01A
1. SSH to RLM/BMC IP of 01A
2. Login to RLM/BMC
3. Issue “system console” > will send you to controller login
4. Login to controller
You are now logged into to controller over RLM/BMC.
1.1.2 Check FC port personality/configuration
01A> fcadmin config 0c > see below for 0c config.
Local
Adapter Type State Status
---------------------------------------------------
0c initiator UNDEFINED online
1.1.3 Change Port Personality
Take the adapter offline using the "storage disable command"
01A> fcadmin offline 0c
Use Fcadmin command to change the port from initiator to target:
Syntax: fcadmin config -d : Disables the adapters drive -t {target|initiator|unconfigured}
01A> fcadmin config -d -t target 0c
Reboot the controller
01A> reboot
Make sure you are connected to RLM/BMC at this point
1.2 Post-Implementation Steps
1.2.1 Verify Port 0c is a target
Plug port 0c into a SAN (switched fabric).
01A> fcp config
01A> fcp show adapter
1.2.2 Bring adapter back online
01A> fcadmin offline 0c
1.2.3 Check Configuration
01A> fcadmin config
Local
Adapter Type State Status
---------------------------------------------------
0c target configured online
1.2.4 Cluster giveback
Check cluster status from controller 01B:
01B> cf status > Look for message stating cluster is in takeovermode
Issue a cluster giveback on controller 01B
01B> cf giveback
Wait until giveback has completed, check cluster state is normal:
01B> cf status > Look for “Cluster enabled, 1A is up.”