Hi Cristian, As requested please see outputs below: UCS1-A(nxos)# sh run int e1/22 interface Ethernet1/22   description S: Server   no pinning server sticky   switchport mode trunk   switchport trunk native vlan xxx4   switchport trunk allowed vlan xxx4,xxx7   no shutdown UCS1-A(nxos)# show int fex-fabric      Fabric      Fabric       Fex                FEX Fex  Port      Port State    Uplink    Model         Serial ---------------------------------------------------------------   1    Eth1/1        Active     1         N20-C6508  xx   1    Eth1/2        Active     2         N20-C6508  xx   2    Eth1/3        Active     1         N20-C6508  xx   2    Eth1/4        Active     2         N20-C6508  xx   3    Eth1/5        Active     1         N20-C6508  xx   3    Eth1/6        Active     2         N20-C6508  xx   4    Eth1/7        Active     1         N20-C6508  xx   4    Eth1/8        Active     2         N20-C6508  xx   5    Eth1/9        Active     1         N20-C6508  xx   5   Eth1/10        Active     2         N20-C6508  xx   6   Eth1/11        Active     1         N20-C6508  xx   6   Eth1/12        Active     2         N20-C6508  xx   7   Eth1/13        Active     1         N20-C6508  xx   7   Eth1/14        Active     2         N20-C6508  xx   8   Eth1/15        Active     1         N20-C6508  xx   8   Eth1/16        Active     2         N20-C6508  xx   9   Eth1/17        Active     1         N20-C6508  xx   9   Eth1/18        Active     2         N20-C6508  xx 10   Eth1/19        Active     1         N20-C6508  xx 10   Eth1/20        Active     2         N20-C6508  xx 11   Eth1/21        Active     1         N20-C6508  xx 12   Eth1/23        Active     1         N20-C6508  xx 12   Eth1/24        Active     2         N20-C6508  xx 13   Eth1/25        Active     1         N20-C6508  xx 13   Eth1/26        Active     2         N20-C6508  xx 14   Eth1/27        Active     1         N20-C6508  xx 14   Eth1/28        Active     2         N20-C6508  xx UCS1-A(nxos)# show fex 1 detail FEX: 1 Description: FEX0001   state: Online   FEX version: 5.0(3)N2(2.11.3a) [Switch version: 5.0(3)N2(2.11.3a)]   FEX Interim version: 5.0(3)N2(2.11.3a)   Switch Interim version: 5.0(3)N2(2.11.3a)   Chassis Model: N20-C6508,  Chassis Serial: XXX   Extender Model: UCS-IOM-2204XP,  Extender Serial: XXX   Part No: 73-14488-03   Card Id: 184, Mac Addr: c0:67:af:84:a6:5a, Num Macs: 38   Module Sw Gen: 21  [Switch Sw Gen: 21]   post level: complete pinning-mode: static    Max-links: 1   Fabric port for control traffic: Eth1/1   Fabric interface state:     Po1025 - Interface Up. State: Active     Eth1/1 - Interface Up. State: Active     Eth1/2 - Interface Up. State: Active   Fex Port        State  Fabric Port          Eth1/1/1  Down      Po1025          Eth1/1/2  Down      Po1025          Eth1/1/3  Down        None          Eth1/1/4  Down        None          Eth1/1/5  Down        None                 Eth1/1/6  Down        None          Eth1/1/7  Down        None          Eth1/1/8  Down        None          Eth1/1/9  Down      Po1025         Eth1/1/10  Down      Po1025         Eth1/1/11  Down        None         Eth1/1/12  Down        None         Eth1/1/13  Down        None         Eth1/1/14  Down        None         Eth1/1/15  Down        None         Eth1/1/16  Down        None         Eth1/1/17    Up      Po1025 Logs: 01/03/2014 11:23:14.295257: Module register received 01/03/2014 11:23:14.296133: Registration response sent 01/03/2014 11:23:14.580311: Module Online Sequence 01/03/2014 11:23:17.47105: Module Online If possible would you be free to discuss this on a WebEx? Kind Regards, Paul ... View more

Thanks Zaira for getting back to me. I have tried your suggested steps to resolve this and unfortunately this has not resolved the problem. However to confirm when we moved the "faulty" optic/cable to new ports to a new location and it worked so would indicate this is not an issue with the optics or cables. The chassis discovery policy is 1 link and there are 2 links between the IOMs/FIs. ... View more

Hi Jeff, The request has come directly from the SAN team who are looking to pre-define and create the association between the UCS vHBAs (WWPNs) and the Boot LUNs on the storage array. Having tested this in the lab, if I create a Global Service Profile Template with Global WWPN Pools on creation of the Service Profiles at present the WWPN are allocated out randomly from the pool. This means that the SAN association can not be completed until the Service Profiles are created. Any other suggestions on how to get around this? On a seperate note: My intention was to create a single global WWPN pool and create multiple blocks (one per UCS domain/site), this will all be done in a Global Service Profile Template. To match a UCS domain/site with a specific WWPN block of address I was going to use the "ID Range Qualification Policy" however reading a previous thread its indicating that this matching can only be done in Local Service Profile Templates, have I read this correctly? Can the ID Range Qualification Policy not be used in a Global Service Profile Template? Thanks, Paul ... View more

Thanks Walter, I have read through your thread and this has lead to another concer... My intention was to create a single global WWPN pool and create multiple blocks (one per UCS domain/site), this will all be done in a Global Service Profile Template. To match a UCS domain/site with a specific WWPN block of address I was going to use the "ID Range Qualification Policy" however in the thread you provided its indicating that this matching can only be done in Local Service Profile Templates, have I read this correctly? Paul ... View more

Thanks Eric, is there any timelines on when this will be available? My customer has requested this functionality for their environment. Paul ... View more