Adapter FEX vs VM-FEX

Having a hard time wrapping my head around the difference and particulars of Adapter FEX and VM-FEX.
I come from the networking side of the house and not the visualization so my misunderstanding may be on the vert side.

Hi Eric
Have a look at this new CVD document, which has a lot of information about VM-FEX
FlexPod Datacenter with VMware vSphere 5.5 Update 1 Design Guide
Last Updated: August 11, 2014
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/UCS_CVDs/flexpod_esxi55u1_design.pdf
Walter.

Similar Messages

Adapter FEX and VM Fex

Hi!
I have a questions about Cisco Adapter FEX and VM Fex.
As i understand, Cisco Adapter FEX gives multiple vNIC on one mezzanine card, and each of them appears as virtual port on Fabric Interconnect.
Also, same thing for VM-FEX, each VM NIC appears as virtual port on Fabric Interconnect.
Am i right?
Thank you!

Adaptor FEX is I/O adaptor virtualization, which is agnostic to the OS and therefore works in virtualized as well as non virtualized environments.
VM-FEX (also called Hypervisor Bypass) is available for different Hypervisors
Cisco UCS Manager VM-FEX for Hyper-V CLI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for KVM CLI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for VMware CLI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for Hyper-V GUI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for KVM GUI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for Hyper-V CLI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for KVM CLI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for VMware CLI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for Hyper-V GUI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for KVM GUI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for KVM CLI Configuration Guide
Cisco UCS Manager VM-FEX for KVM GUI Configuration Guide
Cisco UCS Manager VM-FEX for VMware CLI Configuration Guide
Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide
example VM-FEX for VMware ESX
VM-FEX (previously known as VN-link) is a method to extend the network fabric completely down to the VMs. With VM-FEX, the Fabric Interconnects handle switching for the ESXi host's VMs. UCSM utilizes the vCenter dVS Application Programming Interfaces (API) to this end. Therefore, VM-FEX shows as a dVS in the ESXi host.
There are many benefits to VM-FEX:
Reduced CPU overhead on the ESX host
Faster performance
VMware DirectPath I/O with vMotion support
Network management moved up to the FIs rather than on the ESXi host
Visibility into vSphere with UCSM

Fex 1 Nexus 2148 to 2 Nexus 5010 problem?

hi all
I'm having trouble when fex(ing) 1 nexus 2000 to 2 nexus 5000.
I've configured as dual home from 1 nexus 2k. But after success config, just 1 nexus 5k can see 48 port on it. other cannot see it and it showed as module offline
Here's is results:
N5K-01(config-if)# sh int e1/4 fex-intf
Fabric           FEX
Interface        Interfaces
Eth1/4
N5K-01(config-if)#
N5K-02# sh int e1/4 fex-intf
Fabric           FEX
Interface        Interfaces
Eth1/4          Eth100/1/48   Eth100/1/47   Eth100/1/46   Eth100/1/45
                 Eth100/1/44   Eth100/1/43   Eth100/1/42   Eth100/1/41
                 Eth100/1/40   Eth100/1/39   Eth100/1/38   Eth100/1/37
                 Eth100/1/36   Eth100/1/35   Eth100/1/34   Eth100/1/33
                 Eth100/1/32   Eth100/1/31   Eth100/1/30   Eth100/1/29
                 Eth100/1/28   Eth100/1/27   Eth100/1/26   Eth100/1/25
                 Eth100/1/24   Eth100/1/23   Eth100/1/22   Eth100/1/21
                 Eth100/1/20   Eth100/1/19   Eth100/1/18   Eth100/1/17
                 Eth100/1/16   Eth100/1/15   Eth100/1/14   Eth100/1/13
                 Eth100/1/12   Eth100/1/11   Eth100/1/10   Eth100/1/9
                 Eth100/1/8    Eth100/1/7    Eth100/1/6    Eth100/1/5
                 Eth100/1/4    Eth100/1/3    Eth100/1/2    Eth100/1/1
===============================
N5K-01(config-if)# sh fex 100 detail
FEX: 100 Description: FEX0100   state: Offline
FEX version: 4.1(3)N2(1a) [Switch version: 4.1(3)N2(1a)]
FEX Interim version: 4.1(3)N2(1a)
Switch Interim version: 4.1(3)N2(1a)
Extender Model: N2K-C2148T-1GE, Extender Serial: JAF1405CKHC
Part No: 73-12009-06
Card Id: 70, Mac Addr: 00:0d:ec:fd:48:82, Num Macs: 64
Module Sw Gen: 12594 [Switch Sw Gen: 21]
pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth1/4
Fabric interface state:
    Eth1/4 - Interface Up. State: Active
Fex Port        State Fabric Port Primary Fabric
       Eth100/1/1 Down      Eth1/4      Eth1/4
       Eth100/1/2 Down      Eth1/4      Eth1/4
       Eth100/1/3 Down      Eth1/4      Eth1/4
       Eth100/1/4 Down      Eth1/4      Eth1/4
       Eth100/1/5 Down      Eth1/4      Eth1/4
       Eth100/1/6 Down      Eth1/4      Eth1/4
       Eth100/1/7 Down      Eth1/4      Eth1/4
       Eth100/1/8 Down      Eth1/4      Eth1/4
       Eth100/1/9 Down      Eth1/4      Eth1/4
      Eth100/1/10 Down      Eth1/4      Eth1/4
      Eth100/1/11 Down      Eth1/4      Eth1/4
      Eth100/1/12 Down      Eth1/4      Eth1/4
      Eth100/1/13 Down      Eth1/4      Eth1/4
      Eth100/1/14 Down      Eth1/4      Eth1/4
      Eth100/1/15 Down      Eth1/4      Eth1/4
      Eth100/1/16 Down      Eth1/4      Eth1/4
      Eth100/1/17 Down      Eth1/4      Eth1/4
      Eth100/1/18 Down      Eth1/4      Eth1/4
      Eth100/1/19 Down      Eth1/4      Eth1/4
      Eth100/1/20 Down      Eth1/4      Eth1/4
      Eth100/1/21 Down      Eth1/4      Eth1/4
      Eth100/1/22 Down      Eth1/4      Eth1/4
      Eth100/1/23 Down      Eth1/4      Eth1/4
      Eth100/1/24 Down      Eth1/4      Eth1/4
      Eth100/1/25 Down      Eth1/4      Eth1/4
      Eth100/1/26 Down      Eth1/4      Eth1/4
      Eth100/1/27 Down      Eth1/4      Eth1/4
      Eth100/1/28 Down      Eth1/4      Eth1/4
      Eth100/1/29 Down      Eth1/4      Eth1/4
      Eth100/1/30 Down      Eth1/4      Eth1/4
      Eth100/1/31 Down      Eth1/4      Eth1/4
      Eth100/1/32 Down      Eth1/4      Eth1/4
      Eth100/1/33 Down      Eth1/4      Eth1/4
      Eth100/1/34 Down      Eth1/4      Eth1/4
      Eth100/1/35 Down      Eth1/4      Eth1/4
      Eth100/1/36 Down      Eth1/4      Eth1/4
      Eth100/1/37 Down      Eth1/4      Eth1/4
      Eth100/1/38 Down      Eth1/4      Eth1/4
      Eth100/1/39 Down      Eth1/4      Eth1/4
      Eth100/1/40 Down      Eth1/4      Eth1/4
      Eth100/1/41 Down      Eth1/4      Eth1/4
      Eth100/1/42 Down      Eth1/4      Eth1/4
      Eth100/1/43 Down      Eth1/4      Eth1/4
      Eth100/1/44 Down      Eth1/4      Eth1/4
      Eth100/1/45 Down      Eth1/4      Eth1/4
      Eth100/1/46 Down      Eth1/4      Eth1/4
      Eth100/1/47 Down      Eth1/4      Eth1/4
      Eth100/1/48 Down      Eth1/4      Eth1/4
Logs:
[11/24/2010 03:16:20.624283] Module register received
[11/24/2010 03:16:20.627639] Registration response sent
[11/24/2010 03:16:21.115021] Module Online Sequence
[11/24/2010 03:16:22.379395] Module Online
[11/24/2010 03:52:09.779773] Module disconnected
[11/24/2010 03:52:09.781691] Offlining Module
[11/24/2010 03:52:09.782231] Module Offline Sequence
[11/24/2010 03:52:11.735462] Module Offline
[11/24/2010 04:06:25.258659] Module disconnected
[11/24/2010 04:06:25.259890] Offlining Module
=================
N5K-02# sh fex 100 detail
FEX: 100 Description: FEX0100   state: Online
FEX version: 4.1(3)N2(1a) [Switch version: 4.1(3)N2(1a)]
FEX Interim version: 4.1(3)N2(1a)
Switch Interim version: 4.1(3)N2(1a)
Extender Model: N2K-C2148T-1GE, Extender Serial: JAF1405CKHC
Part No: 73-12009-06
Card Id: 70, Mac Addr: 00:0d:ec:fd:48:82, Num Macs: 64
Module Sw Gen: 12594 [Switch Sw Gen: 21]
pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth1/4
Fabric interface state:
    Eth1/4 - Interface Up. State: Active
Fex Port        State Fabric Port Primary Fabric
       Eth100/1/1 Down      Eth1/4      Eth1/4
       Eth100/1/2 Down      Eth1/4      Eth1/4
       Eth100/1/3 Down      Eth1/4      Eth1/4
       Eth100/1/4 Down      Eth1/4      Eth1/4
       Eth100/1/5 Down      Eth1/4      Eth1/4
       Eth100/1/6 Down      Eth1/4      Eth1/4
       Eth100/1/7 Down      Eth1/4      Eth1/4
       Eth100/1/8 Down      Eth1/4      Eth1/4
       Eth100/1/9 Down      Eth1/4      Eth1/4
      Eth100/1/10 Down      Eth1/4      Eth1/4
      Eth100/1/11 Down      Eth1/4      Eth1/4
      Eth100/1/12 Down      Eth1/4      Eth1/4
      Eth100/1/13 Down      Eth1/4      Eth1/4
      Eth100/1/14 Down      Eth1/4      Eth1/4
      Eth100/1/15 Down      Eth1/4      Eth1/4
      Eth100/1/16 Down      Eth1/4      Eth1/4
      Eth100/1/17 Down      Eth1/4      Eth1/4
      Eth100/1/18 Down      Eth1/4      Eth1/4
      Eth100/1/19 Down      Eth1/4      Eth1/4
      Eth100/1/20 Down      Eth1/4      Eth1/4
      Eth100/1/21 Down      Eth1/4      Eth1/4
      Eth100/1/22 Down      Eth1/4      Eth1/4
      Eth100/1/23 Down      Eth1/4      Eth1/4
      Eth100/1/24 Down      Eth1/4      Eth1/4
      Eth100/1/25 Down      Eth1/4      Eth1/4
      Eth100/1/26 Down      Eth1/4      Eth1/4
      Eth100/1/27 Down      Eth1/4      Eth1/4
      Eth100/1/28 Down      Eth1/4      Eth1/4
      Eth100/1/29 Down      Eth1/4      Eth1/4
      Eth100/1/30 Down      Eth1/4      Eth1/4
      Eth100/1/31 Down      Eth1/4      Eth1/4
      Eth100/1/32 Down      Eth1/4      Eth1/4
      Eth100/1/33 Down      Eth1/4      Eth1/4
      Eth100/1/34 Down      Eth1/4      Eth1/4
      Eth100/1/35 Down      Eth1/4      Eth1/4
      Eth100/1/36 Down      Eth1/4      Eth1/4
      Eth100/1/37 Down      Eth1/4      Eth1/4
      Eth100/1/38 Down      Eth1/4      Eth1/4
      Eth100/1/39 Down      Eth1/4      Eth1/4
      Eth100/1/40 Down      Eth1/4      Eth1/4
      Eth100/1/41 Down      Eth1/4      Eth1/4
      Eth100/1/42 Down      Eth1/4      Eth1/4
      Eth100/1/43 Down      Eth1/4      Eth1/4
      Eth100/1/44 Down      Eth1/4      Eth1/4
      Eth100/1/45 Down      Eth1/4      Eth1/4
      Eth100/1/46 Down      Eth1/4      Eth1/4
      Eth100/1/47 Down      Eth1/4      Eth1/4
      Eth100/1/48 Down      Eth1/4      Eth1/4
Logs:
[11/24/2010 03:49:38.824900] Module timed out
[11/24/2010 03:54:08.225000] Module register received
[11/24/2010 03:54:08.226093] Registration response sent
[11/24/2010 03:54:08.540805] Module Online Sequence
[11/24/2010 03:54:10.7287] Module Online
Anyone can help me with this?
Thanks.

I already configured vPC between 2 Nexus 5010
N5K-01# sh vpc brief
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link
vPC domain id                   : 1
Peer status                     : peer adjacency formed ok
vPC keep-alive status           : peer is alive
Configuration consistency status: success
vPC role                        : primary
vPC Peer-link status
id   Port   Status Active vlans
1    Po1    up     1
vPC status
id     Port        Status Consistency Reason                     Active vlans
100    Po100       down   success     success                    -
N5K-02# sh vpc
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link
vPC domain id                   : 1
Peer status                     : peer adjacency formed ok
vPC keep-alive status           : peer is alive
Configuration consistency status: success
vPC role                        : secondary
vPC Peer-link status
id   Port   Status Active vlans
1    Po1    up     1
vPC status
id     Port        Status Consistency Reason                     Active vlans
100    Po100       down* success     success                    -
N5K-02#
may i miss some config ?

FEX 2232TM not recognized by Nexus 5010P

Hi there,
I don't have any clue what this problem might be so please help.
I have a brandnew FEX 2232TM which is connected to a NEXUS 5010P running the following firmware:
oftware
BIOS:      version 1.5.0
loader:    version N/A
kickstart: version 5.2(1)N1(1)
system:    version 5.2(1)N1(1)
power-seq: Module 1: version v1.2
BIOS compile time:       11/30/10
kickstart image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.1.bin
kickstart compile time: 7/12/2012 19:00:00 [07/13/2012 02:08:13]
system image file is:    bootflash:///n5000-uk9.5.2.1.N1.1.bin
system compile time:     7/12/2012 19:00:00 [07/13/2012 03:23:16]
According to the Cisco download page it is the latest version and should definitely support the 2232TM.
The problem is that the FEX is completely not recognized by the parent Nexus.
It is connected via 8 FET modules. But when ich check the light on both sides I only have light on the NEXUS side never on the FEX side on all modules.
From my understanding this should be the root cause of the issue because no light = no link.
I tried standard 10GBase-SR and Twinax cables as well. Same behavior - the FEX is not recognized.
The status LED if of course orange on the FEX.
This is the FEX related config ont he NEXUS:
feature fex
fex 101
pinning max-links 8
description "FEX0101"
interface Ethernet1/1
switchport mode fex-fabric
fex associate 101
interface Ethernet1/2
switchport mode fex-fabric
fex associate 101
interface Ethernet1/3
switchport mode fex-fabric
fex associate 101
interface Ethernet1/4
switchport mode fex-fabric
fex associate 101
interface Ethernet1/5
switchport mode fex-fabric
fex associate 101
interface Ethernet1/6
switchport mode fex-fabric
fex associate 101
interface Ethernet1/7
switchport mode fex-fabric
fex associate 101
interface Ethernet1/8
switchport mode fex-fabric
fex associate 101
Can anyone give me a hint what I am missing here??
Any help is really appreciated.
Thanks a lot!

I have a two lab switches running 5.2.1.N1.1 and connected in vpc with 2232TM and I am able to see the fex online without any problems. One side I have SFP-10G-SR and other side I have 3M Cisco Twinax cable.
here is the output from my lab,
5010-1# show fex
FEX         FEX           FEX                       FEX
Number    Description      State            Model            Serial
100        FEX0100                Online    N2K-C2232TM-10GE   SSI15380CPM
5010-1# show fex 100 detail
FEX: 100 Description: FEX0100   state: Online
FEX version: 5.2(1)N1(1) [Switch version: 5.2(1)N1(1)]
FEX Interim version: 5.2(1)N1(1)
Switch Interim version: 5.2(1)N1(1)
Extender Serial: SSI15380CPM
Extender Model: N2K-C2232TM-10GE, Part No: 73-13626-03
Card Id: 164, Mac Addr: 28:94:0f:2e:12:82, Num Macs: 64
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
Pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth1/1
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
    Po100 - Interface Up. State: Active
    Eth1/1 - Interface Up. State: Active
Fex Port        State Fabric Port
5010-1# show interface e1/1 transceiver details
Ethernet1/1
    transceiver is present
    type is SFP-H10GB-CU3M rev A
    name is CISCO-MOLEX INC
    part number is 74752-9026
    revision is A
    serial number is MOL12240343
    nominal bitrate is 12000 MBit/sec
    Link length supported for copper is 3 m
    cisco id is --
     cisco extended id number is 4
DOM is not supported
5010-2# show fex
FEX         FEX           FEX                       FEX
Number    Description      State            Model            Serial
100        FEX0100                Online    N2K-C2232TM-10GE   SSI15380CPM
5010-2# show fex 100 detail
FEX: 100 Description: FEX0100   state: Online
FEX version: 5.2(1)N1(1) [Switch version: 5.2(1)N1(1)]
FEX Interim version: 5.2(1)N1(1)
Switch Interim version: 5.2(1)N1(1)
Extender Serial: SSI15380CPM
Extender Model: N2K-C2232TM-10GE, Part No: 73-13626-03
Card Id: 164, Mac Addr: 28:94:0f:2e:12:82, Num Macs: 64
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
Pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth1/1
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
    Po100 - Interface Up. State: Active
    Eth1/1 - Interface Up. State: Active
Fex Port        State Fabric Port
5010-2# show interface e1/1 transceiver details
Ethernet1/1
    transceiver is present
    type is 10Gbase-SR
    name is CISCO-AVAGO
    part number is SFBR-7700SDZ-CS2
    revision is B5
    serial number is AGD133133S4
    nominal bitrate is 10300 MBit/sec
    Link length supported for 50/125um OM2 fiber is 82 m
    Link length supported for 50/125um OM3 fiber is 300 m
    Link length supported for 62.5/125um fiber is 26 m
    cisco id is --
    cisco extended id number is 4
           SFP Detail Diagnostics Information (internal calibration)
                Current              Alarms                  Warnings
                Measurement     High        Low         High          Low
Temperature   44.18 C        75.00 C     -5.00 C     70.00 C        0.00 C
Voltage        3.26 V         3.63 V      2.97 V      3.46 V        3.13 V
Current        6.48 mA       10.50 mA     2.50 mA    10.50 mA       2.50 mA
Tx Power       -2.62 dBm       1.69 dBm -11.30 dBm   -1.30 dBm     -7.30 dBm
Rx Power       -2.80 dBm --    1.99 dBm -13.97 dBm   -1.00 dBm     -9.91 dBm
Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning
So dont believe we have any interoperability issue with 5010 and 2232TM here. Before we swap out this fex, can you please open a case with Cisco support or let me know when you are available and I can do a webex to look at this switch to see if there is something more to this problem than what we already know ?
Thanks,
Vinayak

FEX-Uplink failover, loadbalancing

I wish to understand more the technology within a vblock
I will progressively have a few questions
So here I go. pls be patient and thanks in advance...
VBlock 720 with the following generic config
2x Cisco 5000 Series Switch
2x FI 6248
6x Chassis 5108
FEX 2204
VIC 1240 (no Mezzanine Card)
8x M3 Blade, 2 CPU
4 x 10 G uplinks from each FEX to FI (port channel)
8 x 10 G uplink from each FI to Ciso 5000 series swith (vpc)
Assumptions:
All Chassis are fully populate
Each blade has consistient bandwidth thoroughput but of 6 GB
When the blades connect to FEX A and FEX B, are the connections active active?
For exampleIs blades 1 and 5 pinned to the same FEX port(s) on the same FEX?
What is the method that load balances blade pinging?
Assume Uplink 1 fails between FEX A and FI A, is Uplink 1 on FEX B overutilized.
How does the VM decide which CNA port to send traffic?
That it for now...

see inline
When the blades connect to FEX A and FEX B, are the connections active active?
I assume you mean FEX=IOM in the chassis;
Yes both fabrics are active; all VIC are dual homed to fabric a and b
For exampleIs blades 1 and 5 pinned to the same FEX port(s) on the same FEX?
You have the choice of static pinning (done by UCS Manager) blade slot to a IOM Uplink, or define a port channel between IOM and fabric Interconnect; port channel is the preferred mode.
Static pinning depends on IOM model, 2204 / 2208 and the number of uplinks, e.g.
2204 and 4 uplinks
chassis slot 1 and 5 -> uplink 1
chassis slot 2 and 6 -> uplink 2
2208 and 8 uplinks
chassis slot 1 -> uplink 1
chassis slot 2 -> uplink 2
With static pinning, if a uplinks fails, the corresponding slots fabric a or b, are down; there is no repinning to the remaining uplinks; teaming and multipathing will take appropriate action.
If you have a port channel, and you loose a link, no problem, as long as there is at least one link up; your bandwith will decrease, but th vnic/vhba are still up
What is the method that load balances blade pinging?
Don't understand; please be more specific
Assume Uplink 1 fails between FEX A and FI A, is Uplink 1 on FEX B overutilized.
Yes, in principle ! but you have to design oversubscription end to end anyway !
How does the VM decide which CNA port to send traffic?
This depends on the hypervisor; take e.g. VMware ESXi and vswitch: load balancing can be configured per switch and / or port-group; important caveat: don't use IP hash, because fabric interconnect doesn't support LACP; by default its originating virtual¨port id.

SNMP Trap if a FEX goes down

hello,
need some assistance or help. I have a Nexus 7009 with a FEX N2K-C2248PQ connected. If the N2K goes down (e.g. power down) a syslog event is generated but no snmp-trap from the N7K to the snmp server. Interface up/downs or power supply failures are traped. This is the syslog event:
2014 Feb 13 10:47:47.594 n7009 %FEX-2-NOHMS_ENV_FEX_OFFLINE: FEX-113 Off-line (Serial Number xxxxxxxxx)
is there anybody with an idea?

We've found no solution out-of-the-box, even after some intense research.
But we implemented a simple workaround: Embedded Event Manager Applet. (EEM)
event manager applet EM-CHECK-FEX
description "Checks FEX for availability because no trap would be send"
event syslog occurs 1 pattern "FEX-2-NOHMS_ENV_FEX_OFFLINE"
action 100 snmp-trap strdata "FEX changed to OFFLINE"
action 101 syslog priority notifications msg TRAP_SEND: FEX changed to OFFLINE
The EEM tracks the occurence of the specific syslog-pattern.
If the syslog-pattern in question appears, a snmp-trap will be send.

Fex and VPC

I'm am new to the whole datacenter design and I've recently taken over a data center set up. I'm trying to determine if my vPCs and port-channels are set up correctly. I've attached a drawing of the network set up. It seems pretty straight forward:
NIC teamed server with each NIC going to a separate FEX.
The FEX are straight through to the 5596s.
Using LACP on the switches and servers.
NX-OS 5.0(3)
My questions are 1) Is the FEX number only locally significant to the 5596 it's attached to? Should this number be the same or different on each 5596 or does it not matter? I haven't been able to find anything specifiying what this is supposed to be for this setup.
2) How can I verify the vPCs/portchannels are working properly?
Doing a 'show vpc' shows up/success on both switches.
'show port-channel summary' shows my channel as SU and my port as P.
Doing a 'show interface pXXX' shows my port-channel and vPC if I run the command on both 5596s but they each only show one member in the channel, which is the locally connected interface. I would think I'm supposed to see both interfaces channled together here.
If I take one interface down I don't get any messages on the other switch that the other side of the port-channel has dropped. It also seems like traffic isn't being equally distributed.
I hope this makes sense. I've been trying to figure this environment out for weeks. Just when I think I've got it, it doesn't act the way I'm expecting it to.

1) It does not matter if you have same FEX number on both switches. However, This will be a problem when you decide to implement Enhanced vpC where both FEX connected to both 5596 and servers are also connected to both FEXes.
2) show vpc is perfact command to verify. Another usefull command is show vpc consistancy-paramenter vpc 1902. If you have port down on any switch then you will see consitency parameter failed here.

Fex to Fex connection

Hello,
As per my understanding we can connect Fex with Fex but I don't have any device to check it. Can somebody please test it in the lab and confirm whether is will increase the port number of the fex or other fex will be identified as separate fex?

Hi Joris,
I see the same questions was answered already:
https://supportforums.cisco.com/discussion/12140711/connection-fex-n2k-c2232pp-10ge-nexus-7000
HTH
Regards
Inayath

Adapter-fex Supported VICs and Nexus Switches

HI,
I am thinking of using C220M4 in standalone mode. I have been reading about adapter-fex and I am wondering which Cisco VIC supports adapter-fex and which Nexus Switch will support adapter-fex.
I am thinking of using a VIC1225 and Nexus 3000.
Thanks.

I believe that adaptor fex is supported only with Nexus 5k and N2k:
Network Adapter Virtualization Design (Adapter-FEX) with Cisco Nexus 5500 Switches and Cisco Nexus 2232 Fabric Extenders
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/guide_c07-690080.html
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/data_sheet_c78-657397.html

Macvtap over Cisco Nexus ...

Hi everybody!
First all my apologizes for my english language!
I have a standard server running linux (centos 6.5) with kvm to install and configure virtual machines. I tried to use macvtap driver to setup the virutal network interfaces. I not use ucs Cisco servers or Nexus 1000v switches!
The physical ethernet is connected to Cisco Nexus 2000 (with a Cisco Nexus 5548up). To default a standard switch not working with the macvtap configuration because the swith to be support "reflective relay" or "hair pinning" propierties for to this works.
Is possible configure the Cisco Nexus 5548up/2000 to this works? Capabilities how to Adapter-FEX, veheternet, VM-FEX o similars can help me?
Know you some docs over this?
Thank you all.

Hi Tony,
You do not have to worry about PFC. Priority-Flow-Control is something which is related to FCOE or DCBX protocol. With iSCSI as this is a TCP traffic, you have to make sure that you have a proper QOS for the IP Subnet or VLAN that has your iSCSI hosts transmitting the data. As iSCSI rides over TCP this is the major issue that I have seen related to the valid QOS config for the traffic. There is not best practice for it but you have make sure that you added it to a class other than BE or Scavanger class.
Hope this helps.
Cheers,
-amit singh

N2K port speed set

My N2K connected to N5K, why some ports can set the port speed, and some cann't set the port speed?
int eth102/1/25     ！！！No speed command
(config-if)# ?
beacon          Disable/enable the beacon for an interface
cdp             Configure CDP interface parameters
channel-group   Configure port channel parameters
description     Enter description of maximum 80 characters
inherit         Inherit a port-profile
ip              Configure IP features
ipv6            Configure IPv6 features
lacp            Configure LACP parameters
link            Configure link
lldp            Configure Interface LLDP parameters
logging         Configure logging for interface
mvr-group       MVR interface config
mvr-type        MVR interface config
mvr-vlan        Interface MVR Config
no              Negate a command or set its defaults
rate-limit      Set packet per second rate limit
service-policy Configure service policy for an interface
service-policy Policy Map
shutdown        Enable/disable an interface
snmp            Modify SNMP interface parameters
spanning-tree   Spanning Tree Subsystem
switchport      Configure switchport parameters
untagged        Default to use for untagged packets on interface
end             Go to exec mode
exit            Exit from command interpreter
pop             Pop mode from stack or restore from name
push            Push current mode to stack or save it under name
where           Shows the cli context you are in
(config-if)# int eth102/1/48       ！！！ include speed command
(config-if)# ?
bandwidth              Set bandwidth informational parameter
beacon                 Disable/enable the beacon for an interface
cdp                    Configure CDP interface parameters
channel-group          Configure port channel parameters
default                Set a command to its defaults
delay                  Specify interface throughput delay
description            Enter description of maximum 80 characters
duplex                 Enter the port duplex mode
fex                    Configure FEX fabric
flowcontrol            Configure interface flowcontrol
hardware               FEX Card type
inherit                Inherit a port-profile
ip                     Configure IP features
ipv6                   Configure IPv6 features
lacp                   Configure LACP parameters
link                   Configure link
lldp                   Configure Interface LLDP parameters
load-interval          Specify interval for load calculation for an interface
logging                Configure logging for interface
mac                    MAC
mac-address            Configure interface mac address
mvr-group              MVR interface config
mvr-type               MVR interface config
mvr-vlan               Interface MVR Config
negotiate              Configure link negotiation parameters
no                     Negate a command or set its defaults
priority-flow-control Enable/Disable PFC
rate-limit             Set packet per second rate limit
service-policy         Configure service policy for an interface
service-policy         Policy Map
shutdown               Enable/disable an interface
snmp                   Modify SNMP interface parameters
spanning-tree          Spanning Tree Subsystem
speed                  Enter the port speed
storm-control          Configure Interface storm control
switchport             Configure switchport parameters
untagged               Default to use for untagged packets on interface
vpc                    Virtual Port Channel configuration
vtp                    Enable VTP on this interface
end                    Go to exec mode
exit                   Exit from command interpreter
pop                    Pop mode from stack or restore from name
push                   Push current mode to stack or save it under name
where                  Shows the cli context you are in
1,N5K version:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS:      version 3.6.0
loader:    version N/A
kickstart: version 6.0(2)N1(2)
system:    version 6.0(2)N1(2)
Power Sequencer Firmware:
             Module 1: version v5.0
Microcontroller Firmware:        version v1.0.0.2
SFP uC:    Module 1: v1.1.0.0
QSFP uC:   Module not detected
BIOS compile time:       05/09/2012
kickstart image file is: bootflash:///n5000-uk9-kickstart.6.0.2.N1.2.bin
kickstart compile time: 3/14/2013 1:00:00 [03/14/2013 16:53:55]
system image file is:    bootflash:///n5000-uk9.6.0.2.N1.2.bin
system compile time:     3/14/2013 1:00:00 [03/14/2013 19:28:50]
Hardware
cisco Nexus 5596 Chassis ("O2 48X10GE/Modular Supervisor")
Intel(R) Xeon(R) CPU         with 8262944 kB of memory.
2,N5K port
Eth102/1/1    --                 connected 101       full    1000    --
Eth102/1/2    --                 connected 101       full    1000    --
Eth102/1/3    --                 connected 101       full    1000    --
Eth102/1/4    --                 connected 101       full    1000    --
Eth102/1/5    --                 connected 101       full    1000    --
Eth102/1/6    --                 connected 101       full    1000    --
Eth102/1/7    --                 connected 101       full    1000    --
Eth102/1/8    --                 connected 101       full    1000    --
Eth102/1/9    --                 connected 101       full    1000    --
Eth102/1/10   --                 connected 101       full    1000    --
Eth102/1/11   --                 connected 101       full    1000    --
Eth102/1/12   --                 connected 101       full    1000    --
Eth102/1/13   --                 connected 101       full    1000    --
Eth102/1/14   --                 connected 101       full    1000    --
Eth102/1/15   --                 connected 104       full    1000    --
Eth102/1/16   --                 connected 104       full    1000    --
Eth102/1/17   --                 connected 104       full    1000    --
Eth102/1/18   --                 connected 104       full    1000    --
Eth102/1/19   --                 connected 104       full    1000    --
Eth102/1/20   --                 connected 104       full    1000    --
Eth102/1/21   --                 connected 104       full    1000    --
Eth102/1/22   --                 connected 104       full    1000    --
Eth102/1/23   --                 connected 104       full    1000    --
Eth102/1/24   --                 connected 104       full    1000    --
Eth102/1/25   --                 notconnec 102       auto    auto    --
Eth102/1/26   --                 notconnec 102       auto    auto    --
Eth102/1/27   --                 connected 106       full    1000    --
Eth102/1/28   --                 connected 106       full    1000    --
Eth102/1/29   --                 connected 104       full    1000    --
Eth102/1/30   --                 connected 104       full    1000    --
Eth102/1/31   --                 connected 104       full    1000    --
Eth102/1/32   --                 connected 104       full    1000    --
Eth102/1/33   --                 connected 104       full    1000    --
Eth102/1/34   --                 connected 104       full    1000    --
Eth102/1/35   --                 connected 104       full    1000    --
Eth102/1/36   --                 connected 104       full    1000    --
Eth102/1/37   --                 connected 104       full    1000    --
Eth102/1/38   --                 connected 104       full    1000    --
Eth102/1/39   --                 notconnec 1         auto    auto    --
Eth102/1/40   --                 notconnec 1         auto    auto    --
Eth102/1/41   --                 notconnec 1         auto    auto    --
Eth102/1/42   --                 notconnec 1         auto    auto    --
Eth102/1/43   --                 notconnec 1         auto    auto    --
Eth102/1/44   --                 notconnec 1         auto    auto    --
Eth102/1/45   --                 notconnec 1         auto    auto    --
Eth102/1/46   --                 notconnec 1         auto    auto    --
Eth102/1/47   --                 notconnec 1         auto    auto    --
Eth102/1/48   ZTC-Switch-48      connected 105       full    100     --
3,Fex
show fex 102 det
FEX: 102 Description: AO4-N2K-FEX102   state: Online
FEX version: 6.0(2)N1(2) [Switch version: 6.0(2)N1(2)]
FEX Interim version: 6.0(2)N1(2)
Switch Interim version: 6.0(2)N1(2)
Extender Serial: FOX1742G09B
Extender Model: N2K-C2248TP-E-1GE, Part No: 73-13671-02
Card Id: 149, Mac Addr: 64:e9:50:16:08:02, Num Macs: 64
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
Pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth1/3
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
    Po102 - Interface Up. State: Active
    Eth1/1 - Interface Up. State: Active
    Eth1/2 - Interface Up. State: Active
    Eth1/3 - Interface Up. State: Active
    Eth1/4 - Interface Up. State: Active
Fex Port        State Fabric Port
       Eth102/1/1    Up       Po102
       Eth102/1/2    Up       Po102
       Eth102/1/3    Up       Po102
       Eth102/1/4    Up       Po102
       Eth102/1/5    Up       Po102
       Eth102/1/6    Up       Po102
       Eth102/1/7    Up       Po102
       Eth102/1/8    Up       Po102
       Eth102/1/9    Up       Po102
      Eth102/1/10    Up       Po102
      Eth102/1/11    Up       Po102
      Eth102/1/12    Up       Po102
      Eth102/1/13    Up       Po102
      Eth102/1/14    Up       Po102
      Eth102/1/15    Up       Po102
      Eth102/1/16    Up       Po102

show run int eth102/1/25 all
!Command: show running-config interface Ethernet102/1/25 all
!Time: Tue Apr 14 14:33:38 2009
version 6.0(2)N1(2)
interface Ethernet102/1/25
no description
lacp port-priority 32768
lacp rate normal
priority-flow-control mode auto
lldp transmit
lldp receive
no switchport block unicast
no switchport block multicast
no hardware multicast hw-hash
no hardware vethernet mac filtering per-vlan
cdp enable
switchport
switchport mode access
no switchport dot1q ethertype
no switchport priority extend
switchport access vlan 102
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
spanning-tree port type edge
spanning-tree bpduguard enable
no spanning-tree bpdufilter
speed auto
duplex auto
flowcontrol receive off
flowcontrol send on
no link debounce
no beacon
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
mdix auto
storm-control broadcast level 100.00
storm-control multicast level 100.00
storm-control unicast level 100.00
no shutdown lan
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
medium broadcast
channel-group 2025 mode active
no shutdown
show run int eth102/1/48 all
!Command: show running-config interface Ethernet102/1/48 all
!Time: Tue Apr 14 14:35:08 2009
version 6.0(2)N1(2)
interface Ethernet102/1/48
description ZTC-Switch-48
lacp port-priority 32768
lacp rate normal
priority-flow-control mode auto
lldp transmit
lldp receive
no switchport block unicast
no switchport block multicast
no hardware multicast hw-hash
no hardware vethernet mac filtering per-vlan
cdp enable
switchport
switchport mode access
no switchport dot1q ethertype
no switchport priority extend
switchport access vlan 105
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
spanning-tree port type edge
spanning-tree bpduguard enable
no spanning-tree bpdufilter
speed auto
duplex auto
flowcontrol receive off
flowcontrol send on
no link debounce
no beacon
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
mdix auto
storm-control broadcast level 100.00
storm-control multicast level 100.00
storm-control unicast level 100.00
no shutdown lan
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
medium broadcast
no shutdown
Ports are connected, there is no relationship with the speed option, such as port 102/1/1 is connected, but no speed option, port 102/1/47 is notconnected, there speed options.
show int eth102/1/1
Ethernet102/1/1 is up
Belongs to Po2001
Hardware: 100/1000 Ethernet, address: 64e9.5016.0802 (bia 64e9.5016.0802)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 1000 Mb/s
Beacon is turned off
Input flow-control is off, output flow-control is on
Switchport monitor is off
EtherType is 0x8100
Last link flapped 1d02h
int eth102/1/1
(config-if)# ?
beacon          Disable/enable the beacon for an interface
cdp             Configure CDP interface parameters
channel-group   Configure port channel parameters
description     Enter description of maximum 80 characters
inherit         Inherit a port-profile
ip              Configure IP features
ipv6            Configure IPv6 features
lacp            Configure LACP parameters
link            Configure link
lldp            Configure Interface LLDP parameters
logging         Configure logging for interface
mvr-group       MVR interface config
mvr-type        MVR interface config
mvr-vlan        Interface MVR Config
no              Negate a command or set its defaults
rate-limit      Set packet per second rate limit
service-policy Configure service policy for an interface
service-policy Policy Map
shutdown        Enable/disable an interface
snmp            Modify SNMP interface parameters
spanning-tree   Spanning Tree Subsystem
switchport      Configure switchport parameters
untagged        Default to use for untagged packets on interface
end             Go to exec mode
exit            Exit from command interpreter
pop             Pop mode from stack or restore from name
push            Push current mode to stack or save it under name
where           Shows the cli context you are in
show int eth102/1/47
Ethernet102/1/47 is down (Link not connected)
Hardware: 100/1000 Ethernet, address: 64e9.5016.0830 (bia 64e9.5016.0830)
MTU 1500 bytes, BW 0 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
auto-duplex, auto-speed
Beacon is turned off
Input flow-control is off, output flow-control is on
Switchport monitor is off
EtherType is 0x8100
int eth102/1/47
(config-if)# ?
bandwidth              Set bandwidth informational parameter
beacon                 Disable/enable the beacon for an interface
cdp                    Configure CDP interface parameters
channel-group          Configure port channel parameters
default                Set a command to its defaults
delay                  Specify interface throughput delay
description            Enter description of maximum 80 characters
duplex                 Enter the port duplex mode
fex                    Configure FEX fabric
flowcontrol            Configure interface flowcontrol
hardware               FEX Card type
inherit                Inherit a port-profile
ip                     Configure IP features
ipv6                   Configure IPv6 features
lacp                   Configure LACP parameters
link                   Configure link
lldp                   Configure Interface LLDP parameters
load-interval          Specify interval for load calculation for an interface
logging                Configure logging for interface
mac                    MAC
mac-address            Configure interface mac address
mvr-group              MVR interface config
mvr-type               MVR interface config
mvr-vlan               Interface MVR Config
negotiate              Configure link negotiation parameters
no                     Negate a command or set its defaults
priority-flow-control Enable/Disable PFC
rate-limit             Set packet per second rate limit
service-policy         Configure service policy for an interface
service-policy         Policy Map
shutdown               Enable/disable an interface
snmp                   Modify SNMP interface parameters
spanning-tree          Spanning Tree Subsystem
speed                  Enter the port speed
storm-control          Configure Interface storm control
switchport             Configure switchport parameters
untagged               Default to use for untagged packets on interface
vpc                    Virtual Port Channel configuration
vtp                    Enable VTP on this interface
end                    Go to exec mode
exit                   Exit from command interpreter
pop                    Pop mode from stack or restore from name
push                   Push current mode to stack or save it under name
where                  Shows the cli context you are in

How to replace Nexus5596 with dual-homing N2K

What is the correct process to replace a FEX parent switch with dual-homing fex?
Traffic should not be interrupted.

Hi
Do you have VPC between Parent Switches & are you running VPC on dual homed FEX fabric ports. ?
If yes Below is the procedure,
1) boot the replacement switch without VPC, peer-links & FEX ports connected to it.
2) Make sure it has same Software version matches with the peer switch.
3) enable Pre-Provisioning for slots with appropriate FEX model.
, here find the guide:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5000/sw/system_management/521_n1_1/b_5k_System_Mgmt_Config_521N11_chapter_0100.html#task_05BB53AD7AFB49CF9A8E4A5C6C37CB38
So, on the replacement switch you will pre-provision the Fabric Extender and configure the ports so it will be ready when you add the module to the RMA SW.
Please make sure you put the appropriate FEX model on the provision slot, otherwise, when connected it will not come Online
Example, FEX 110:
N5K(config)# slot 110
N5K(config-slot)#provision model N2K-C2248T
4) Now keep all ports at Shut down state Then Configure Entire switch that includes FEX host ports, FEX Fabric Ports & VPC peer-link, VPC Domain Configuration.
keep FEX host ports in shut state.
5) keep VPC Role priority on existing switch lower than , new switch
6) Connect Peer-link ports to Peer switch & wait till VPC Comes up-
7) Then connect Fabric ports from FEX to the pre-configured ports on replacement switch
After it comes online Unshut FEX host ports.
I got similar steps here as well
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/operations/n5k_vpc_ops.html#wp425197
NOTE: I followed same process however, few ping drops were seen....arnd ( 5- 6 ping loss) only on few hosts...
Mazhar

Load-balancing Algorithm for NX-OS Port Channels

Hi, all
I do not understand description of port-channel load-balance ethernet command.
switch(config)# port-channel load-balance ethernet ?
destination-ip         Destination IP address
destination-mac        Destination MAC address
destination-port       Destination TCP/UDP port
source-dest-ip         Source & Destination IP address (includes l2)
source-dest-ip-only    Source & Destination IP addresses only
source-dest-mac        Source & Destination MAC address
source-dest-port       Source & Destination TCP/UDP port (includes l2 and l3)
source-dest-port-only Source & Destination TCP/UDP port only
source-ip              Source IP address
source-mac             Source MAC address
source-port            Source TCP/UDP port
Please tell me what the following descriptions mean.
Source & Destination IP address (includes l2)
Source & Destination TCP/UDP port (includes l2 and l3)
What are the meaning of "includes l2" and "includes l2 and l3" ?
Thank you for your cooperation in advance.

Hi Satoru,
On the Nexus 5000/6000 platforms, all FEXs will inherit the global hashing algorithm from the parent device.
On the Nexus 7000 platform, hashing algorithms can be assigned on a per FEX basis (all load balancing changes must be made from the Admin VDC):
N7K-A(config)# port-channel load-balance src-dst ip-l4port fex 134
Any FEX without a hashing algorithm configured with inherit the global hash. Making changes to the modular/global hash will not alter FEX specific hashing algorithms.
To verify the configuration applied you can use this command:
N5K_A# show port-channel load-balance
On the Nexus 7000, the per FEX algorithm can be checked by appending the ‘fex <#>’ to the end of the command in the Admin VDC or the FEX’s respective VDC:
N7K-A(config)# show port-channel load-balance fex 134
Regards,
Richard

N5548P with NX-OS 5.0(3)N2(1) wont work with 2248TP and 2232PP with pre-installed Fabric Extender OS

Hi,
We recently bought 2 N5K and 4 N2K Fabric extenders, now we are having problem installing the fabric extenders as the FEX just wont go up.
switch(config-fex)# sh fex 100 detail
FEX: 100 Description: ADM/128-SVF-NS302   state: Offline
FEX version: 4.2(1)N1(1) [Switch version: 5.0(3)N2(1)]
FEX Interim version: 4.2(1)N1(0.002)
Switch Interim version: 5.0(3)N2(1)
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
pinning-mode: static    Max-links: 1
Fabric port for control traffic:
Fabric interface state:
    Po3 - Interface Down. State: Configured
    Eth1/7 - Interface Down. State: Configured
    Eth1/8 - Interface Down. State: Configured
    Eth1/9 - Interface Down. State: Configured
    Eth1/10 - Interface Down. State: Configured
Fex Port        State Fabric Port
Logs:
11/22/2011 07:49:23.536463: Offlining Module
11/22/2011 07:49:23.564858: Deleting route to FEX
11/22/2011 07:49:23.572372: Module disconnected
11/22/2011 07:49:23.573795: Offlining Module
11/22/2011 07:50:34.741573: Module register received
11/22/2011 07:50:34.742363: Image Version Mismatch
11/22/2011 07:50:34.742496: Registration response sent
11/22/2011 07:50:34.742741: Requesting satellite to download image
11/22/2011 07:52:55.922414: Image preload failed.
11/22/2011 07:52:57.91269: Deleting route to FEX
11/22/2011 07:52:57.106904: Module disconnected
11/22/2011 07:52:57.108092: Module Offline
11/22/2011 07:52:57.110203: Deleting route to FEX
11/22/2011 07:52:57.115149: Module disconnected
11/22/2011 07:52:57.116546: Offlining Module
11/22/2011 07:52:57.150559: Deleting route to FEX
11/22/2011 07:52:57.155607: Module disconnected
11/22/2011 07:52:57.156970: Offlining Module
11/22/2011 07:52:57.189131: Deleting route to FEX
11/22/2011 07:52:57.193969: Module disconnected
11/22/2011 07:52:57.195342: Offlining Module
11/22/2011 07:52:57.234153: Deleting route to FEX
11/22/2011 07:52:57.239023: Module disconnected
11/22/2011 07:52:57.240432: Offlining Module
11/22/2011 07:54:40.815191: Module register received
ADM_128-SVF-NS102(config-fex)# sh fex 101 detail
FEX: 101 Description: ADM/128-SVF-NS304   state: Offline
FEX version: 4.2(1)N1(1) [Switch version: 5.0(3)N2(1)]
FEX Interim version: 4.2(1)N1(0.002)
Switch Interim version: 5.0(3)N2(1)
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
pinning-mode: static    Max-links: 1
Fabric port for control traffic:
Fabric interface state:
    Po4 - Interface Down. State: Configured
    Eth1/11 - Interface Down. State: Configured
    Eth1/12 - Interface Down. State: Configured
    Eth1/13 - Interface Down. State: Configured
    Eth1/14 - Interface Down. State: Configured
Fex Port        State Fabric Port
Logs:
11/22/2011 07:49:46.163035: Module disconnected
11/22/2011 07:49:46.164468: Offlining Module
11/22/2011 07:49:46.213737: Deleting route to FEX
11/22/2011 07:49:46.219043: Module disconnected
11/22/2011 07:49:46.220454: Offlining Module
11/22/2011 07:49:46.250091: Deleting route to FEX
11/22/2011 07:49:46.255026: Module disconnected
11/22/2011 07:49:46.256417: Offlining Module
11/22/2011 07:51:09.395617: Module register received
11/22/2011 07:51:09.396381: Image Version Mismatch
11/22/2011 07:51:09.396511: Registration response sent
11/22/2011 07:51:09.396756: Requesting satellite to download image
11/22/2011 07:55:08.409032: Image preload failed.
11/22/2011 07:55:09.671589: Deleting route to FEX
11/22/2011 07:55:09.682174: Module disconnected
11/22/2011 07:55:09.683181: Module Offline
11/22/2011 07:55:09.702525: Deleting route to FEX
11/22/2011 07:55:09.710557: Module disconnected
11/22/2011 07:55:09.711930: Offlining Module
11/22/2011 07:55:09.741583: Deleting route to FEX
11/22/2011 07:55:09.746544: Module disconnected
11/22/2011 07:55:09.747934: Offlining Module
11/22/2011 07:55:09.786138: Deleting route to FEX
11/22/2011 07:55:09.791026: Module disconnected
11/22/2011 07:55:09.792426: Offlining Module
I am seeing "image mismatch" definitely because our N5K is pre-installed with 5.0(3) while fex is using 4.2(1) pre-installed.
Is upgrading the N2K possible? Hope someone can help
Thanks,
Ramon

Hi All,
Using the N7K to install the Nexus 2000 yielded the same result as connecting to our N5K.
switch(config-if)# sh fex 101 detail
FEX: 101 Description: FEX0101   state: Image Download
FEX version: 4.2(1)N1(1) [Switch version: 5.1(3)]
FEX Interim version: 4.2(1)N1(0.002)
Switch Interim version: 5.1(3)
Module Sw Gen: 21 [Switch Sw Gen: 21]
pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth1/11
Fabric interface state:
    Po101 - Interface Up. State: Active
    Eth1/9 - Interface Up. State: Active
    Eth1/11 - Interface Up. State: Active
    Eth1/13 - Interface Up. State: Fabric Up
    Eth1/15 - Interface Down. State: Configured
Fex Port        State Fabric Port Primary Fabric
Logs:
11/28/2011 06:27:09.662264: Requesting satellite to download image
11/28/2011 06:29:15.232681: Image preload failed.
11/28/2011 06:29:16.459514: Deleting route to FEX
11/28/2011 06:29:16.464452: Module disconnected
11/28/2011 06:29:16.465542: Module Offline
11/28/2011 06:29:16.502250: Deleting route to FEX
11/28/2011 06:29:16.507315: Module disconnected
11/28/2011 06:29:16.520566: Offlining Module
11/28/2011 06:30:27.820404: Module register received
11/28/2011 06:30:27.821854: Image Version Mismatch
11/28/2011 06:30:27.822322: Registration response sent
11/28/2011 06:30:27.822512: Requesting satellite to download image
11/28/2011 06:33:01.789172: Image preload failed.
11/28/2011 06:33:03.21324: Deleting route to FEX
11/28/2011 06:33:03.26651: Module disconnected
11/28/2011 06:33:03.27635: Module Offline
11/28/2011 06:33:03.60441: Deleting route to FEX
11/28/2011 06:33:03.64871: Module disconnected
11/28/2011 06:33:03.68626: Offlining Module
11/28/2011 06:34:14.640167: Module register received
11/28/2011 06:34:14.640895: Image Version Mismatch
11/28/2011 06:34:14.641367: Registration response sent
11/28/2011 06:34:14.641546: Requesting satellite to download image
11/28/2011 06:37:33.144396: Image preload failed.
11/28/2011 06:37:34.373433: Deleting route to FEX
11/28/2011 06:37:34.378391: Module disconnected
11/28/2011 06:37:34.379795: Module Offline
11/28/2011 06:37:34.429214: Deleting route to FEX
11/28/2011 06:37:34.433627: Module disconnected
11/28/2011 06:37:34.436989: Offlining Module
11/28/2011 06:38:45.746477: Module register received
11/28/2011 06:38:45.747175: Image Version Mismatch
11/28/2011 06:38:45.747841: Registration response sent
11/28/2011 06:38:45.748041: Requesting satellite to download image
11/28/2011 06:41:57.68356: Deleting route to FEX
11/28/2011 06:41:57.80615: Module disconnected
11/28/2011 06:41:57.83824: Module Offline
11/28/2011 06:41:57.98377: Deleting route to FEX
11/28/2011 06:41:57.102731: Module disconnected
11/28/2011 06:41:57.106928: Offlining Module
11/28/2011 06:41:57.151366: Deleting route to FEX
11/28/2011 06:41:57.155672: Module disconnected
11/28/2011 06:41:57.158411: Offlining Module
11/28/2011 06:43:08.457500: Module register received
11/28/2011 06:43:08.458280: Image Version Mismatch
11/28/2011 06:43:08.458874: Registration response sent
11/28/2011 06:43:08.459069: Requesting satellite to download image
11/28/2011 06:47:41.719070: Image preload failed.
11/28/2011 06:47:42.949044: Deleting route to FEX
11/28/2011 06:47:42.954394: Module disconnected
11/28/2011 06:47:42.955658: Module Offline
11/28/2011 06:47:42.973122: Deleting route to FEX
11/28/2011 06:47:42.978185: Module disconnected
11/28/2011 06:47:42.981593: Offlining Module
11/28/2011 06:47:43.26743: Deleting route to FEX
11/28/2011 06:47:43.31820: Module disconnected
11/28/2011 06:47:43.35748: Offlining Module
11/28/2011 06:48:48.755085: Deleting route to FEX
11/28/2011 06:48:48.760546: Module disconnected
11/28/2011 06:48:48.764950: Offlining Module
11/28/2011 06:48:54.260037: Module register received
11/28/2011 06:48:54.260794: Image Version Mismatch
11/28/2011 06:48:54.261268: Registration response sent
11/28/2011 06:48:54.261452: Requesting satellite to download image
switch(config-if)# 2011 Nov 28 06:51:43 switch %FEX-2-NOHMS_ENV_FEX_OFFLINE: FEX-101 Off-line (Serial Number XXXXXXXXXXXX)
It's very frustrating.
Regards,
Ramon

Class java.sql.SQLException

I am getting the followig error when i m executing the following SQL..Plz help
try
String sql1="Delete from wh.WHRECTEMP where sessionid='"+session[0][0].trim()+"' and SUPPINVNO='"+txtSuppInvNo.getText()+"' ";
del = bean.getACNData(sql1);
catch(FrontEndException fEx)
MessageBox.show(fEx.getMessage());
catch(Exception e){
System.out.println("DELETED" +e.getMessage());
System Exception Class: class java.sql.SQLException
Database Error Code: 900
SQL Error message:
invalid SQL statement
Cause: The statement is not recognized as a valid SQL statement. This error can
occur if the Procedural Option is not installed and a SQL statement is issued th
at requires this option (for example, a CREATE PROCEDURE statement). You can det
ermine if the Procedural Option is installed by starting SQL*Plus. If the PL/SQL
banner is not displayed, then the option is not installed.
Action: Correct the syntax or install the Procedural Option.
-->FrontEndException in invoking method getACNData(java.lang.String) of WHReceip
tCtrl
===> FrontEndException in DispatcherServ: SQL Error in getting meta data for que
ry.

the method getACNData inside the bean is like this.And i have used this method many times in code for firing select queries but while using delete stmt it is givivng above error at the server side console but it is deleting the records correctly.
public String[][] getACNData(String sql)
throws FrontEndException
String result[][] = executeSQL(sql);
if(result != null && result.length > 0)
return result;
else
return null;
}

Adapter FEX vs VM-FEX

Similar Messages

Maybe you are looking for