> # Monitoring FlexAttach Virtual pWWN

> Table 13-2 lists the errors that might be displayed and provides the workarounds.

> Table 13-2

> Error | Description | Workaround
> --- | --- | ---
> fc1/1 : interface is not down | FlexAttach configuration fails because the configuration is enabled for an active interface with the operation state as up. | To move the port to the shut state, enable the FlexAttach configuration, and then move the port to no shut state.
> FlexAttach configuration is not distributed to the peers | The FlexAttach configuration on one peer NPV is not available to any other peer NPV. | FlexAttach configuration will not be distributed if cfs ipv4 distribute, or cfs ipv6 distribute is disabled. Enable cfs ipv4 distribute, or cfs ipv6 distribute.
> Even with CFS distribution enabled Inagua does not become a peer with other NPVs | CFS over IP is enabled, and the Inagua in one blade center is not the peer NPV for other NPVs. | CFS over IP uses IP multicast to discover the NPV peers in the network. IBM MM does not support multicast and cannot act as a peer with NPV. This prevents the FlexAttach configuration from getting distributed to other peer NPVs in the network.
> NP port uses physical pWWN instead of virtual pWWN configured through FlexAttach | This occurs when NP port uses physical pWWN instead of virtual pWWN, that is configured through FlexAttach. | FlexAttach is supported on server interfaces such as F ports, and not on external interfaces such as NP ports.
> real port WWN and virtual WWN cannot be same | This occurs when you try to configure FlexAttach with a similar value for pWWN and virtual pWWN. | Use different values for pWWN and virtual pWWN, as similar values for pWWN and virtual pWWn are not allowed.
> Virtual port WWN already exists | This occurs when you try to configure an already defined pWWN to a different interface. | Use an undefined virtual pWWN for a new interface.

> FlexAttach Errors and Workarounds

> Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.