README FILE

*****************************************
FlexPod Plug-in for Config Advisor
-----------------------------------------
Release date:11/12/2015 
-----------------------------------------
Version: 1.0
*****************************************

--------
CONTENTS
--------
I. NEW FEATURES IN THIS RELEASE
II. FIXED ISSUES
III. KNOWN ISSUES

I. NEW FEATURES IN THIS RELEASE

 * FlexPod profile is moved from being a fixed profile in Config Advisor and has been added as a plug-in
 * Supports Cisco Nexus 9000
 * Firmware Recommendations from NetApp Interoperability Matrix Tool is added to FlexPod clustered Data ONTAP profile

III. KNOWN ISSUES

You must be aware of the known issues in the FlexPod checks and their workarounds (where available) so that you can run the FlexPod checks more effectively.

1. Issue: When the service profile is in the Associating state, FlexPod FC Zoning Check reports the following incorrect error message:
no initiator in the zone
Description: When a service profile is in Associating state, a definitive value (for example, WWPN, MAC, vNIC) is not available, resulting in the incorrect error message.
Workaround: None.

2. Issue: FlexPod VLAN Correlation Check does not report an error when an undefined VLAN is created on the Virtual Port Channels (vPC) peer link.
Description: If an unidentified VLAN is created on the vPC peer link (for example, FCoE VLAN), then it causes unwanted packet forwarding and does not report an error.
Workaround: None.

3. Issue: FlexPod VLAN Correlation Check reports an error incorrectly on all targets when LACP is not enabled.
Workaround: Check if LACP is enabled, then run FlexPod VLAN Correlation Check (precondition rule).

4. Issue: If the IP and credentials of Nexus Fabric A and Nexus Fabric B are interchanged while providing the inputs on the GUI, Fabric A would be interpreted as Fabric B and vice versa. Though the switches might have the right configurations on them, this would show up as an incorrect configuration.
Description: If the configurations on Nexus Fabric A and Nexus Fabric B are interchanged on the GUI, Nexus Fabric A would be interpreted as Nexus Fabric B and Nexus Fabric B would be interpreted as Nexus Fabric A. Even though the cabling and configurations are correct, this interchange results in errors.
Note: The uplinks have to be validated taking into account the last VSAN IDs of the links.
Workaround: None.

5. Issue: Config Advisor error message lists both the Service Profile WWPNs as not added to the same Initiator Group on the Storage Controller when one of them is added.
Description: Only one of the two Service Profile WWPN's are added to an Initiator Group on the Storage Controller. Config Advisor requires that both the Service Profile WWPN's are added to the same Initiator Group on the Storage Controller. Config Advisor error message lists both the Service Profile WWPN's that is not added to the Initiator Group instead of just the one WWPN which is not added to the Initiator Group.
Workaround: Manually find out which WWPN out of the two is not added to the Initiator Group on the Storage Controller.

6. Issue: FlexPod Storage FC Uplink Rule does not error when port is not configured as target on Cluster Mode.
Description: Config Advisor checks for the port under node scope command system node run * fcadmin config in Cluster Mode for ports configured as target/initiator.
Because the physical ports when configured as target/initiator move under cluster scope Config Advisor does not find the port details under this node scope command.
Hence it does not error for FlexPod Storage FC Uplink Rule when ports are configured as initiator on Cluster Mode.
Workaround: Manually verify that the port is configured as target on the Cluster using fcp adapter show instance on Cluster Shell.

7. Issue: FlexPod Storage Switch Correlation Check should passes incorrectly when vlan on ifgrp is disabled on Cluster Mode.
Description: Config Advisor does not check for the vlan-enabled status on the ifgrp for FlexPod Storage Switch Correlation Check on Cluster Mode.
It just checks the physical connectivity of the interfaces configured in Storage controller ifgrp connected to the Nexus Switch.
Workaround: Manually verify if the vlan configured on Storage controller interfaces in the ifgrp connected to the Nexus Switch is UP.

8. Issue: FlexPod FC Zoning rule fails incorrectly for WWPNs from different Service Profiles grouped into same initiator group on Storage on a Virtual Storage Console (VSC) for VMware setup.
Description: Config Advisor FlexPod FC Zoning rule check fails if WWPNs from different Service Profiles are grouped into same initiator group on Storage.
VSC for VMware when installed on the host creates an Initiator group with WWPNs from different Service Profiles together on the Storage.
Workaround: Ignore the FlexPod FC Zoning rule failure for WWPNs from different Service Profiles grouped into same initiator group on Storage for that corresponding VSC Initiator Group on a setup with Virtual Storage Console (VSC) for VMware installed.

9. Issue: When there is a Service Profile with One vHBA which is zoned and is in igroup and LUN is mapped, Config Advisor throws an error WWPN<<ServiceProfile WWPN>> is associated to Service Profile<<ServiceProfile Name>> and in the igroup<<Igroup Name>> but not zoned
Description: Because there is only one vHBA which goes through a Nexus Fabric and not found on another Nexus Fabric, Config Advisor throws an error.
Workaround: Service Profile HA Check checks for 2 vHBA in Service Profile, if it is not available then Config Advisor throws an error. It is recommended to have 2vHBA for each Service Profile, if not modify the Service Profile to have 2 vHBAs
If Service Profile HA Check failure is encountered and fixed, then the error is fixed automatically.
