Re-built it and everything looks good now. The crash/reload is a little disturbing though. I'll try to make it a point to remember to save my config before doing anything FCOE related on a 5K in the lab...
5K-2# sh npv status
npiv is disabled
disruptive load balancing is disabled
External Interfaces:
====================
Interface: vfc6, State: Trunking
VSAN: 1, State: Waiting For VSAN Up
VSAN: 10, State: Up
VSAN: 20, State: Up, FCID: 0x330000
Number of External Interfaces: 1
Server Interfaces:
==================
Number of Server Interfaces: 0
5K-2# sh npv status
npiv is disabled
disruptive load balancing is disabled
External Interfaces:
====================
Interface: vfc6, State: Trunking
VSAN: 1, State: Waiting For VSAN Up
VSAN: 10, State: Up
VSAN: 20, State: Up, FCID: 0x330000
Number of External Interfaces: 1
Server Interfaces:
==================
Number of Server Interfaces: 0
On Sun, Mar 23, 2014 at 3:39 PM, Gregg Malcolm <gregg.malcolm@gmail.com> wrote:
Thanks, GreggAll VLANs and VSANs configured properly. Any thoughts? I going to try to re-build before my session ends.Second 5K is FCOE-NPV. VFC is NP mode with trunk in and VFC bound to PC.I was working on figuring out why the VFC wouldn't come up (trunked VSANs not in an up state). I tried a shut of the associated port-channel and got this:Pretty basic NPV config.
5K-2(config-if)# int po 120
5K-2(config-if)# sh
2014 Mar 23 18:50:29 SW3 %ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface port-channel120 is down(Config change)
2014 Mar 23 18:50:29 SW3 %PORT-5-IF_DOWN_NONE: %$VSAN 1%$ Interface vfc6 is down (None)
2014 Mar 23 18:50:30 SW3 %PORT-5-IF_DOWN_NONE: %$VSAN 1%$ Interface vfc6 is down (None)
2014 Mar 23 18:50:30 SW3 %SYSMGR-2-SERVICE_CRASHED: Service "fwm" (PID 3107) hasn't caught signal 11 (core will be saved).
Broadcast message from root (console) (Sun Mar 23 18:50:40 2014):
The system is going down for reboot NOW!
First 5K is FCOE,NPIV and f-portchannel trunk. VFC is F mode with trunk on and VFC bound to PC.