Nexus 7000 w/ 2000 FEX - Interface Status When N7K has power issues

I have multiple nexus 2Ks connected to two N7Ks with my servers connecting to multiple N2Ks accordingly with dual NIC failover capability.
What happens, or what state do the N2K interfaces go into if one of my N7K's looses power given the N2K is effectivly still receiving power?

Hi Ans,
You are rigth, I have defaulted againt the port, now configured with switchport mode FEX, and now the FET-10G is validated
NX7K-1-VDC-3T-S1-L2FP(config-if)#  description FEX-101
NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport
NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport mode fex-fabric
NX7K-1-VDC-3T-S1-L2FP(config-if)#   fex associate 101
NX7K-1-VDC-3T-S1-L2FP(config-if)#   medium p2p
NX7K-1-VDC-3T-S1-L2FP(config-if)#   channel-group 101
NX7K-1-VDC-3T-S1-L2FP(config-if)#   no shutdown
NX7K-1-VDC-3T-S1-L2FP(config-if)#
NX7K-1-VDC-3T-S1-L2FP(config-if)# sh int e7/33 status
Port             Name            Status    Vlan      Duplex  Speed   Type
Eth7/33          FEX-101         notconnec 1         auto    auto    Fabric Exte
NX7K-1-VDC-3T-S1-L2FP(config-if)#
Thanks for your help, and have a nice weekend.
Atte,
EF

Similar Messages

  • Nexus 7000 and 2000. Is FEX supported with vPC?

    I know this was not supported a few months ago, curious if anything has changed?

    Hi Jenny,
    I think the answer will depend on what you mean by is FEX supported with vPC?
    When connecting a FEX to the Nexus 7000 you're able to run vPC from the Host Interfaces of a pair of FEX to an end system running IEEE 802.1AX (802.3ad) Link Aggregation. This is shown is illustration 7 of the diagram shown on the post Nexus 7000 Fex Supported/Not Supported Topologies.
    What you're not able to do is run vPC on the FEX Network Interface that connect up to the Nexus 7000 i.e., dual-homing the FEX to two Nexus 7000. This is shown in illustrations 8 and 9 of under the FEX topologies not supported on the same page.
    There's some discussion on this in the forum post DualHoming 2248TP-E to N7K that explains why it's not supported, but essentially it offers no additional resilience.
    From that post:
    The view is that when connecting FEX to the Nexus 7000, dual-homing does not add any level of resilience to the design. A server with dual NIC can attach to two FEX  so there is no need to connect the FEX to two parent switches. A server with only a single NIC can only attach to a single FEX, but given that FEX is supported by a fully redundant Nexus 7000 i.e., SE, fabrics, power, I/O modules etc., the availability is limited by the single FEX and so dual-homing does not increase availability.
    Regards

  • Interface status when connected to an ADM?

    I have a couple of quick questions, maybe someone can help me with them.
    These are the facts:
    - I have a fiber optic running about 20km between two sites.
    - On one end I have an ASR1006 with a SIP-10G and in one of its sub-slots it has a SPA-5x1GE. This SPA has a 1000BASE-ZX SFP installed.
    - There's a smf jumper running from the SFP to the ODF an this ODF goes to an ADM.
    - I know that the other end (at 20km aprox) is disconnected.
    - The A/L led on the SPA, next to the SFP port is steady orange.
    So, what status should be shown on the "show interface" output? Right now it's "interface down, line procotol down"
    If all is set correctly (logs are clean) should the line protocol be up?
    Should the interface be up?
    At the ODF there are 2 connectors (RX and TX) so they might be inverted and I cannot access that, I would need to call the provider and don't want to do it unless if it necessary.
    Thanks.

    The problem is probably the result of an mismatch between the optical transceiver (SFP) in the ASR1006 and the service provider's ADM. 
    You need to know from the service provider what type of interface (speed, reach [1000BASE-?X]) they have installed in their ADM connecting to your equipment.  Typically, for an in-building interconnection, between the termination equipment and the service provider's equipment, they would be using a short reach interface (1000BASE-SX), which would operate over multimode fiber or maybe a long reach interface (100BASE-LX), which can run over MMF or SMF. The 1000BASE-ZX SFP is designed for very long links (up to 70 kilometers) and operates at 1550nm over SMF fiber. I'm guessing your link between the ASR and ADM is <500 meters. 
    If everything is functioning properly, the "show interface" would be Interface UP, Line Protocol UP. If their is a transceiver mismatch, the devices may be unable to read the bits to bring the link up.  The client ADM port (facing you) may be shut down as you mentioned the other end of the backbone fiber (20km) is not connected.    
    http://www.cisco.com/en/US/products/hw/modules/ps4999/products_tech_note09186a00807a30d6.shtml
    http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/installation/note/78_15160.html
    I hope I am understanding your network topology. 

  • Nexus 7000 SNMP Polling of interfaces within VDC's ?

    Hi all,
    I hope this is a relatively easy question to answer.
    I have some Nexus 7010's that I need to monitor via SNMP.  Currently, we can poll the switch and get some info back, however we only see physical interfaces that belong to the Admin VDC.
    In order to be able to poll interfaces within a non-Admin VDC, do I have to configure SNMP communities (and an IP to respond to the poll) within each VDC ?  Or is there a way to poll them from the Admin VDC?
    bash-2.05$ snmpwalk -v 2c -c public <ipaddr-in-admin-vdc> .1.3.6.1.2.1.31.1.1.1.1
    IF-MIB::ifName.83886080 = STRING: mgmt0
    < **** Eth 8/1 - 8/15 assigned to other VDC's ****>
    IF-MIB::ifName.439939072 = STRING: Ethernet8/16
    IF-MIB::ifName.439943168 = STRING: Ethernet8/17
    IF-MIB::ifName.439947264 = STRING: Ethernet8/18
    IF-MIB::ifName.439951360 = STRING: Ethernet8/19
    IF-MIB::ifName.439955456 = STRING: Ethernet8/20
    IF-MIB::ifName.439959552 = STRING: Ethernet8/21
    IF-MIB::ifName.439963648 = STRING: Ethernet8/22
    IF-MIB::ifName.439967744 = STRING: Ethernet8/23
    IF-MIB::ifName.439971840 = STRING: Ethernet8/24
    IF-MIB::ifName.439975936 = STRING: Ethernet8/25
    IF-MIB::ifName.439980032 = STRING: Ethernet8/26
    Thanks,
    Anthony

    Hi  Anthony,
    Think of each VDC as a separate switch.  So you need to configure SNMP per VDC.
    HTH

  • PO status when PI has failed

    Hello,
    We are implementing SRM7 with ECS and we use PI to send XML PO to vendor systems.
    We would like the PO status to be updated when there is an error in PI like "error in Process".
    How can we implement that?
    Thanks

    Hi Le,
    Its not supported by standard.
    Regards
    Sam

  • My iPad is turning on and off randomly when it has power Why? and how do I stop this from happening?

    Do I need to send this back to the apple store?
    When I have it plugged into the main power supply it only goes up to 3% of power and when I plug it into iTunes it runs out of power in about 2 minuites.

    I think you may need to book an appointment with a genius! They will fix it or replace it for you, for free!!! You can book an appointment at your local apple store at http://www.apple.com/retail
    Hope this helps
    Conchuir

  • Nexus 7000 supervisor replacement

         I'm trying to get my head around how to replace a supervisor module on a nexus 7000 with a single supervisor.  The setup has the default vdc and one other defined.  So if a sup  was faulty  what is the best way to handle this? I have the default vdc config and the other vdc on a tftpboot server. Whats the easiest  and fastest way to hand this .  In the default vdc add address    and copy  the default vdc config and then when that's in copy the other vdc config file.    Just used to IOS where you normally had a single file and you got the box on the air enough to copy the config file into startup and reloaded .  Hope this makes sense.   Tried to read some  of the docs but it's still not clear what exactly needs to be done.   Thanks for any help...

    That makes sense.
    1. Restore the default VDC config.
    2. Create your second VDC.
    3. Restore the second VDC config.
    Don't forget to have a backup of any license files that you may have purchased, for example MPLS.

  • Dell Servers with Nexus 7000 + Nexus 2000 extenders

    << Original post by smunzani. Answered by Robert. Moving from Document section to Discussions>>
    Team,
    I would like to use some of the existing Dell Servers for new network design of Nexus 7000 + Nexus 2000 extenders. What are my options for FEC to the hosts? All references of M81KR I found on CCO are related to UCS product only.
    What's best option for following setup?
    N7K(Aggregation Layer) -- N2K(Extenders) -- Dell servers
    Need 10G to the servers due to dense population of the VMs. The customer is not up for dumping recently purchased dell boxes in favor of UCS. Customer VMware license is Enterprise Edition.
    Thanks in advance.

    To answer your question, the M81KR-VIC is a Mezz card for UCS blades only.  For Cisco rack there is a PCIe version which is called the P81.  These are both made for Cisco servers only due to the integration with server management and virtual interface functionality.
    http://www.cisco.com/en/US/prod/collateral/ps10265/ps10493/data_sheet_c78-558230.html
    More information on it here:
    Regards,
    Robert

  • LMS 4.2.2 Interface utilisation on Nexus 7000

    Hi All,
    I'm trying to poll some interfaces for their utilization on a nexus 7000 through LMS 4.2.2.
    When I create a poller fot the specific instances, the LMS recognises the instances, but after activating the poller I get the error "No Such Instance - The specified instance is not available".
    No info is displayed when I generate an interface utilization report for the specific nexus.
    When I activate the automonitor for interface utilization, the interfaces on the nexus are polled.
    On the cisco website there are some features listed which LMS does not support on the Nexus 7000, but polling is not in that list (neither in the supported feature list).
    Any tips?
    Thanks for your help.
    Joris

    Any Idea..??

  • Connecting IBM B22 FEXes to Nexus 7000

    Hello everybody,
    Could someone give an definite answer, better to based on personal experience - is it possible to attach B22 FEX going to the IBM chassis to Nexus 7000 via F2 series 48-port 10G card?
    NXOS is currently running 6.1.5a but we plan to upgrade to 6.2.8 or 6.2.12 once we get new 4GB DIMMs for SUP1 modules.
    Thanks.

    In my case, I was getting this error on a interface of a Nexus C6001 with the FET-10G transceiver.  I was able to clear it up by temorarily replacing and configuring a slower GLC-T which worked as expected.  I then removed all the settings an got the FET-10G to link.

  • Nexus 7000, 2000, FCOE and Fabric Path

    Hello,
    I have a couple of design questions that I am hoping some of you can help me with.
    I am working on a Dual DC Upgrade. It is pretty standard design, customer requires a L2 extension between the DC for Vmotion etc. Customer would like to leverage certain features of the Nexus product suite, including:
    Trust Sec
    VDC
    VPC
    High Bandwidth Scalability
    Unified I/O
    As always cost is a major issue and consolidation is encouraged where possible. I have worked on a couple of Nexus designs in the past and have levergaed the 7000, 5000, 2000 and 1000 in the DC.
    The feedback that I am getting back from Customer seems to be mirrored in Cisco's technology roadmap. This relates specifically to the features supported in the Nexus 7000 and Nexus 5000.
    Many large enterprise Customers ask the question of why they need to have the 7000 and 5000 in their topologies as many of the features they need are supported in both platforms and their environments will never scale to meet such a modular, tiered design.
    I have a few specific questions that I am hoping can be answered:
    The Nexus 7000 only supports the 2000 on the M series I/O Modules; can FCOE be implemented on a 2000 connected to a 7000 using the M series I/O Module?
    Is the F Series I/O Module the only I/O Module that supports FCOE?
    Are there any plans to introduce the native FC support on the Nexus 7000?
    Are there any plans to introduce full fabric support (230 Gbps) to the M series I/O module?
    Are there any plans to introduce Fabric path to the M series I/O module?
    Are there any plans to introduce L3 support to the F series I/O Module?
    Is the entire 2000 series allocated to a single VDC or can individual 2000 series ports be allocated to a VDC?
    Is Trust Sec only support on multi hop DCI links when using the ASR on EoMPLS pwire?
    Are there any plans to inroduce Trust Sec and VDC to the Nexus 5500?
    Thanks,
    Colm

    Hello Allan
    The only IO card which cannot co-exist with other cards in the same VDC is F2 due to specific hardware realisation.
    All other cards can be mixed.
    Regarding the Fabric versions - Fabric-2 gives much bigger throughoutput in comparing with Fabric-1
    So in order to get full speed from F2/M2 modules you will need Fab-2 modules.
    Fab2 modules won't give any advantages to M1/F1 modules.
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/data_sheet_c78-685394.html
    http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/prodcut_bulletin_c25-688075.html
    HTH,
    Alex

  • Frame generated by Nexus 7000 contains unexpected trailer when using GRE

    I have observed some unexpected behaviour on a Nexus 7000 running 6.1(2) in respect of the Ethernet II frame generated when the Nexus 7000 is a GRE Tunnel endpoint.
    The device receiving the Frame is discarding it and I waiting for the vendor to confirm the reason for this discard. However in case the reason is due to the Ethernet frame being "unusual" I am curious if any one else has come across this.
    To generate the Frame I perform a ping (on a workstation) which the Nexus 7000 in encapsulating in a GRE tunnel. Using Wireshark on the Nexus 7000 egress interface I observed that the Frame contains the following protocols as expected; ETH:IP:GRE:IP:ICMP:data
    When I issue the command "ping -l 1" on the workstation the Frame details from Wireshark are:
    Frame 84 bytes on wire
    Total IP payload = 53 bytes
     Outer IP header (20 bytes)
     GRE ( 4 bytes)
     Inner IP header (20 bytes)
     ICMP (header 8 bytes  payload 1 byte)
    Ethernet Trailer length = 17 bytes
    What is curious about this Frame is that;
    a) No Ethernet Trailer is needed as the IP payload exceeds 46 bytes
    b) The amount of padding applied is what would be needed if the Inner IP datagram were encapsulated directly in an Ethernet II Frame. The Inner ip datagram is 29 bytes octets and hence padding needed = 46 - 29  = 17.
    By doing ping sweep from length 1 to 18 the observed padding was;
    1,17
    2,16
    3,15
    17,1
    18,0
    So it would appear that the Nexus is adding padding to the Ethernet frame as though it were containing the pre GRE payload only.

    What module are you using?
    Ron

  • Nexus 5548 fex interface configuration in vPC scenario

    Hello Forum Team!
    I have a pair of Nexus 5548UP configured as a vPC domain active-standby couple with six Nexus 2248TP Fex's in a dual-homed scenario (each fex is connected to each 5548UP). At the same time, both 5548UP are dual-homed to a pair of VSS Catalyst 6509.
    I have a couple of questions regarding performance and configuration:
    1. When configuring a fex interface, I've noticed that if the configuration is not the same or replicated on both 5548UP, the fex interface won't come up; is this normal behaviour? For now I am replicating manually the configuration on both 5548UP (not confyg-sync).
    2. When performing ICMP tests from the 2248TP to the VSS, the response time is around 1ms to 2ms; from the 5548UP to the VSS pair is approximately 0.5ms. Is that normal delay response time from the 2248TP? I was expecting less response time from the 2248TP (the fex's have 20 Gigs of uplink bandwidth to the 5548UP pair and the 5548UP pair have 40 gig's of bandwidth to the VSS pair).
    Thanks in advanced team!

    Hi,
    1. When configuring a fex interface, I've noticed that if the configuration is not the same or replicated on both 5548UP, the fex interface won't come up; is this normal behaviour?
    Yes, that is a normal behavior.  Since yours FEXes are connected to BOTH 5ks, you have to configure both 5Ks in order for the FEX to come up. If you connect your FEX physically to only one 5k, then you only configurethat one 5k, but in your case you need to configure both 5ks exactly the same.
    2. When performing ICMP tests from the 2248TP to the VSS, the response time is around 1ms to 2ms; from the 5548UP to the VSS pair is approximately 0.5ms. Is that normal delay response time from the 2248TP? I was expecting less response time from the 2248TP (the fex's have 20 Gigs of uplink bandwidth to the 5548UP pair and the 5548UP pair have 40 gig's of bandwidth to the VSS pair).
    I have never tested this, but I would think since the 2k needs to to 5k for every packet including talking to another host on the same 2k, the delay would slightly be higher then when you ping directly from the 5k.
    HTH

  • Query Nexus 7000 Enviroment Status

    Hi,
    I am trying to figure out how to query a Nexus 7010 Chassis about its enviroment. For our IOS Switches we use SNMP and OID 1.3.6.1.4.1.9.9.13.1 and the related sub OIDs. But this does not work on the Nexus 7010 with version 5.1. Is querying the information not supported or is there another OID?

    Hi,I am trying to figure out how to query a Nexus 7010 Chassis about its enviroment. For our IOS Switches we use SNMP and OID 1.3.6.1.4.1.9.9.13.1 and the related sub OIDs. But this does not work on the Nexus 7010 with version 5.1. Is querying the information not supported or is there another OID?
    Hi,
    Check out the below link for nexus 7000 MIB reference ..
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/mib/quickreference/Cisco_Nexus_7000_Series_NX-0S_MIB_Quick_Reference_chapter1.html#con_40545
    Hope to Help !!
    Ganesh.H

  • NEXUS 7000 xcvrInval

    Hi,
    I have some Nexus 7000 with FET-10G with xcvrInval status
    Eth7/33          N5k-S1-3T-1/3   xcvrInval trunk     auto    auto    Fabric Exte
    and some other FET-10G with notconn status
    Eth7/8           FEX-101         notconnec 1         auto    auto    Fabric Exte
    If I inter exchange the position of both FET-10G the status port doesn´t change
    FET-10G from 7/8 to 7/33
    FET-10G from 7/33 to 7/8
    7/33 holds xcvrInval status
    7/8 holds notconnec status
    I have reconfigured from default interface with same results
    Next you´ll find the same serial number in deferent port, the diference is the current
    when is xcvrInva or when is notconnec
    What can I do to get FET10G in e7/33 validated?
    sh interface e7/33   transceiver details
    Ethernet7/33
          transceiver is present
          type is Fabric Extender Transceiver
          name is CISCO-FINISAR  
          part number is FTLX8570D3BCL-C2
          revision is A  
          serial number is FNS17201TE5    
          nominal bitrate is 10300 MBit/sec
          Link length supported for 62.5/125um fiber is 10 m
          Link length supported for 50/125um OM3 fiber is 100 m
          cisco id is --
          cisco extended id number is 4
          cisco part number is 10-2566-02
          cisco product id is FET-10G            
          cisco vendor id is V02
          number of lanes 1
                 SFP Detail Diagnostics Information (internal calibration)
                    Current              Alarms                  Warnings
                    Measurement     High        Low         High          Low
        Temperature   19.30 C        75.00 C      5.00 C     70.00 C       10.00 C
    [7m--More-- [m
        Voltage        3.31 V         3.63 V      2.97 V      3.46 V        3.13 V
        Current        0.06 mA  --     11.80 mA     4.00 mA    10.80 mA       5.00 mA
        Tx Power          N/A        22.69 dBm    8.69 dBm     18.69 dBm     12.69 dBm
        Rx Power          N/A        22.99 dBm    6.09 dBm     18.99 dBm     10.09 dBm
        Transmit Fault Count = 0
        Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    now in slot 7/8
    Ethernet7/8
          transceiver is present
          type is Fabric Extender Transceiver
          name is CISCO-FINISAR  
          part number is FTLX8570D3BCL-C2
          revision is A  
          serial number is FNS17201TE5    
          nominal bitrate is 10300 MBit/sec
          Link length supported for 62.5/125um fiber is 10 m
          Link length supported for 50/125um OM3 fiber is 100 m
          cisco id is --
          cisco extended id number is 4
          cisco part number is 10-2566-02
          cisco product id is FET-10G            
          cisco vendor id is V02
          number of lanes 1
                 SFP Detail Diagnostics Information (internal calibration)
                    Current              Alarms                  Warnings
                    Measurement     High        Low         High          Low
        Temperature   23.17 C        75.00 C      5.00 C     70.00 C       10.00 C
    [7m--More-- [m
        Voltage        3.30 V         3.63 V      2.97 V      3.46 V        3.13 V
        Current        7.50 mA       11.80 mA     4.00 mA    10.80 mA       5.00 mA
        Tx Power      17.65 dBm      22.69 dBm    8.69 dBm     18.69 dBm     12.69 dBm
        Rx Power     -12.21 dBm --   22.99 dBm    6.09 dBm     18.99 dBm     10.09 dBm
        Transmit Fault Count = 0
        Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning
    NX7K-1-VDC-3T-S1-L2FP# sh int e7/33
    Ethernet7/33 is down (Transceiver validation failed)
    admin state is up, Dedicated Interface
      Belongs to Po51
      Hardware: 1000/10000 Ethernet, address: 8478.ac23.6cec (bia 8478.ac23.6cec)
      Description: N5k-S1-3T-1/3
      MTU bytes (CoS values):  MTU  1500(0-2,4-7) bytes  MTU  2112(3) bytes
      BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, medium is broadcast
      Port mode is trunk
    auto-speed  auto-duplex,, media type is 10G
      Beacon is turned off
      Auto-Negotiation is turned on
      Input flow-control is off, output flow-control is off
      Auto-mdix is turned on
      Rate mode is dedicated
      Switchport monitor is off
      EtherType is 0x8100
      EEE (efficient-ethernet) : n/a
      Last link flapped never
      Last clearing of "show interface" counters 07:22:09
      0 interface resets
      Load-Interval #1: 30 seconds
        30 seconds input rate 0 bits/sec, 0 packets/sec
        30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        300 seconds input rate 0 bits/sec, 0 packets/sec
        300 seconds output rate 0 bits/sec, 0 packets/sec
      RX
        88 unicast packets  0 multicast packets  0 broadcast packets
        0 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC/FCS  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        88 unicast packets  0 multicast packets  0 broadcast packets
        0 output packets  0 bytes
        0 jumbo packets
        0 output error  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble  0 output discard
        0 Tx pause
    NX7K-1-VDC-3T-S1-L2FP# sh int e7/33
    Ethernet7/8 is down (Link not connected)
    admin state is up, Dedicated Interface
      Belongs to Po101
      Hardware: 1000/10000 Ethernet, address: 8478.ac23.6cd3 (bia 8478.ac23.6cd3)
      Description: FEX-101
      MTU bytes (CoS values):  MTU  1500(0-2,4-7) bytes  MTU  2112(3) bytes
      BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, medium is p2p
      Port mode is fex-fabric
    auto-speed  auto-duplex,, media type is 10G
      Beacon is turned off
      Auto-Negotiation is turned on
      Input flow-control is off, output flow-control is off
      Auto-mdix is turned on
      Rate mode is dedicated
      Switchport monitor is off
      EtherType is 0x8100
      EEE (efficient-ethernet) : n/a
      Last link flapped 5week(s) 1day(s)
      Last clearing of "show interface" counters never
      0 interface resets
      Load-Interval #1: 30 seconds
        30 seconds input rate 0 bits/sec, 0 packets/sec
    [7m--More-- [m
        30 seconds output rate 0 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        300 seconds input rate 0 bits/sec, 0 packets/sec
        300 seconds output rate 0 bits/sec, 0 packets/sec
      RX
        10588 unicast packets  0 multicast packets  0 broadcast packets
        4 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC/FCS  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        10588 unicast packets  1 multicast packets  0 broadcast packets
        4 output packets  5688 bytes
        0 jumbo packets
        0 output error  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble  0 output discard
        0 Tx pause

    Hi Ans,
    You are rigth, I have defaulted againt the port, now configured with switchport mode FEX, and now the FET-10G is validated
    NX7K-1-VDC-3T-S1-L2FP(config-if)#  description FEX-101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   switchport mode fex-fabric
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   fex associate 101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   medium p2p
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   channel-group 101
    NX7K-1-VDC-3T-S1-L2FP(config-if)#   no shutdown
    NX7K-1-VDC-3T-S1-L2FP(config-if)#
    NX7K-1-VDC-3T-S1-L2FP(config-if)# sh int e7/33 status
    Port             Name            Status    Vlan      Duplex  Speed   Type
    Eth7/33          FEX-101         notconnec 1         auto    auto    Fabric Exte
    NX7K-1-VDC-3T-S1-L2FP(config-if)#
    Thanks for your help, and have a nice weekend.
    Atte,
    EF

Maybe you are looking for