Nexus 7010 and ESX Host

Hi,
We are currently seeing issues on a ESX Host using 10G Fibre dual connectivity to a pair of Nexus 7010's using vPC for the port channel to this ESX host which was working fine , up to this weekend. No changes had been made on the Nexus or ESX host.
We have changed the hardware path for the believed fault on a vmnic which when part of the virtual switch cause VM's on the Host to stop pinging, although we still see a CDP neighborship with the ESX from the Nexus, but changing fibre and Nexus ports has not worked.
As part of the testing , the vmware guy was removing this 'faulty' vmnic from the Virtual switch , which is part of an ether channel bundle his end. My first question is, how does the Nexus detect a link leaving the bundle for the ESX host , when the actual physical link is still up , and all they have done is software removed it from on the ESX, as the Nexus will still attempt to push traffic across both bundled links. I know there is the Cisco 1000V software , which can be used at an extra price, but is this the only option.
Any help will be gladly welcome.

Hi
How the switch detects a link 'moving out' of the Etherchannel would depend on how you have configured it...
If you have used 'channel-group x mode on' under the physical ports in the channel, then it will not detect the change, and you will get problems. The solution is to ensure the config of the channel on both ends (server/switch) is consistent in this case. An inconsistent config will cause you connectivity issues.
If the switch automatically negotiates the Etherchannel (i.e. you are using LACP, and the server supports LACP) then it should detect the change.
Regards
Aaron
Please rate helpful posts...

Similar Messages

How to download MIB for NXOS or platform Nexus 7010 and Nexus 7004

Hello,
I need to monitor my Nexus 7004 and 7010 by my SNMP Agent, but I can't find the way to donload the required MIBs.
For information I'm running the folling images:
bootflash:///n7000-s2-dk9.6.2.6b.bin
bootflash:///n7000-s1-dk9.6.1.5.bin
By advance thanks for the support
Gildas

The module you are running requires a minimum software version of 5.1.
You are currently running 5.0.3 which is why the module is not
recognized.
Below is a link that explains this:
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/data_s
heet_c78-605482.html
Product Specification
Table 3 lists the specifications for the Cisco Nexus 7000 32-Port 10 Gigabit Ethernet
Module with XL Option.
Table 3. Product Specifications
Item
Specifications
System
Product compatibility
Supported in all Cisco Nexus 7000 Series chassis
Software compatibility
Cisco NX-OS Software Release 5.1 or later (minimum requirement)
You would need to upgrade you software.
Hope this helps.
Regards
Muhammed M

Private-VLAN using Nexus 7010 and 2248TP FEX

I have a Nexus 7010 with several 2248TP FEX modules.
I am trying to configure a Private VLAN on one of the FEX host ports.
I see in the documentation you can't do promiscous but I can't even get the host only configuration to take.
Software
BIOS:      version 3.22.0
kickstart: version 6.0(2)
system:    version 6.0(2)
sho run | inc private
feature private-vlan
vlan 11
name PVLAN_Primary
private-vlan primary
private-vlan association 12
vlan 12
name PVLAN_Secondary
private-vlan isolated
7010(config)# int e101/1/48
7010(config-if)#
7010(config-if)# switchport mode ?
access        Port mode access
dot1q-tunnel Port mode dot1q tunnel
fex-fabric    Port mode FEX fabric
trunk         Port mode trunk
Switchport mode private-vlan doesn't even show up!!!!!!
If I try this command it says its not allowed on the FEX port.
7010(config-if)# switchport private-vlan host-association 11 12
ERROR: Requested config not allowed on fex port
What am I doing wrong?????
Todd

Have you found a solution to this?
-Jeremy

How to get the details of a LUN (Storage Logical Units) presented to an ESX host thru SCVMM 2012

Hi,
We are working with a UI Add-in for SCVMM 2012 where we should support both Hyper-v and ESX hosts. When added the ESX host and presented few LUNs (out of band operation) from the HP 3PAR array,
we are unable to view the Storage details like Storage Logical unit, Storage Pool and Storage Array when we select the same LUN in the Classification and Pools section of SCVMM.
We tried even with the PowerShell, but couldn’t help. Can you please guide us, how we can get the storage details of a LUN presented to the ESX host which is added in the SCVMM 2012.
Thanking you.
Regards,
Hari

Hi Jiannan,
No worries, you can go to UDDI client from the main page of PI i.e. http://<serverName>:<serverPort>/
And you use the search function for the TModel for your Physical System. Search parameters can use the % wildcard.
Hit the search and you find the UDDI Key for the Physical System.
Cheers.
Hemant Chahal

Nexus 7010 fabric extender timing out

Hello -
We have a Nexus 7010 and we are testing out using the fabric extenders for a need. We have a demo 2224 unit and have it connected to our M132XP-12 10G blade in the 7K but the FEX won't come online. I would have figured a possible software incompatability but looking at the supported list for that as well as hardware everything seems to be in order. This is what the status shows after it spends about 15 mins in the image download state.
FEX: 111 Description: FEX0111   state: Offline
FEX version: 4.2(1)N2(1a) [Switch version: 5.1(2)]
FEX Interim version: 4.2(1)N2(1a)
Switch Interim version: 5.1(2)
Module Sw Gen: 21 [Switch Sw Gen: 21]
pinning-mode: static    Max-links: 1
Fabric port for control traffic: Eth2/20
Fabric interface state:
    Po11 - Interface Up. State: Active
    Eth2/20 - Interface Up. State: Active
Fex Port        State Fabric Port Primary Fabric
This is looped in the log details until it times out:
04/25/2011 15:31:41.986978: Module register received
04/25/2011 15:31:41.987713: Registration response sent
04/25/2011 15:31:41.987889: Requesting satellite to download image
04/25/2011 15:32:00.105031: Module register received
04/25/2011 15:32:00.105779: Registration response sent
04/25/2011 15:32:00.105956: Requesting satellite to download image
04/25/2011 15:32:20.191181: Module register received
04/25/2011 15:32:20.191957: Registration response sent
04/25/2011 15:32:20.192144: Requesting satellite to download image
We ran a debug during this and these entries are displayed when looking for errors.
2011 Apr 25 15:30:31.443745 fex: Reg resp: Failed to get card info for swcardid 132
2011 Apr 25 15:30:35.472721 fex: Cardinfo: Unknown card id to get (132)
2011 Apr 25 15:30:35.472753 fex: Reg resp: Failed to get card info for swcardid 132
2011 Apr 25 15:30:41.495302 fex: Cardinfo: Unknown card id to get (132)
I'm still doing some more searching which so far hasn't turned up much, wanted to see if anyone has some other insight??
Thanks!

Hi Jack -
Thanks for the response. Unfortunately, yes that is already complete. I was hoping that would be an easy fix. When we upgraded to 5.1(2) we did the 5.1 EPLD. I ran the install all impact command noted below for the 5.1 EPLD just to make sure it didn't report anything else as needing upgrade.
sho install all impact epld bootflash:n7000-s1-epld.5.1.1.img
Compatibility check:
Module Type Upgradable        Impact   Reason
     1    LC         Yes    disruptive   Module Upgradable
     2    LC         Yes    disruptive   Module Upgradable
     5   SUP         Yes    disruptive   Module Upgradable
     1 Xbar         Yes    disruptive   Module Upgradable
     2 Xbar         Yes    disruptive   Module Upgradable
     3 Xbar         Yes    disruptive   Module Upgradable
     1   FAN         Yes    disruptive   Module Upgradable
     2   FAN         Yes    disruptive   Module Upgradable
     3   FAN         Yes    disruptive   Module Upgradable
     4   FAN         Yes    disruptive   Module Upgradable
Copy complete, now saving to disk (please wait)...
Retrieving EPLD versions... Please wait.
Images will be upgraded according to following table:
Module Type           EPLD      Running-Version   New-Version Upg-Required
     1    LC Power Manager              4.008       4.008           No
     1    LC IO                         1.006       1.006           No
     1    LC Forwarding Engine          1.006       1.006           No
     1    LC SFP                        1.004       1.004           No
     2    LC Power Manager              4.008       4.008           No
     2    LC IO                         1.016       1.016           No
   2    LC Forwarding Engine          1.006       1.006           No
     2    LC FE Bridge(1)              186.006      186.006           No
     2    LC FE Bridge(2)              186.006      186.006           No
     2    LC Linksec Engine(1)        2.006       2.006           No
     2    LC Linksec Engine(2)          2.006       2.006           No
     2    LC Linksec Engine(3)          2.006       2.006           No
     2    LC Linksec Engine(4)          2.006       2.006           No
     2    LC Linksec Engine(5)          2.006       2.006           No
     2    LC Linksec Engine(6)          2.006       2.006           No
     2    LC Linksec Engine(7)          2.006       2.006           No
     2    LC Linksec Engine(8)          2.006       2.006           No
     5   SUP Power Manager              3.009       3.009           No
     5   SUP IO                         3.028       3.028           No
     5   SUP Inband                     1.008       1.008           No
     5   SUP Local Bus CPLD             3.000       3.000           No
     5   SUP CMP CPLD                   6.000       6.000           No
     1 Xbar Power Manager              2.010       2.010           No
     2 Xbar Power Manager              2.010       2.010           No
     3 Xbar Power Manager              2.010       2.010           No
     1   FAN Fan Controller (1)         0.007       0.007           No
     1   FAN Fan Controller (2)         0.007       0.007           No
     2   FAN Fan Controller (1)         0.007       0.007           No
     2   FAN Fan Controller (2)         0.007       0.007           No
     3   FAN Fan Controller (1)         0.007       0.007           No
     3   FAN Fan Controller (2)        0.007       0.007           No
     4   FAN Fan Controller (1)         0.007       0.007           No
     4   FAN Fan Controller (2)         0.007       0.007           No

Nexus 7010 Slot 3 problem

Hello everyone,
Here is my issue. We have a Nexus 7010 and for the third time now slot 3 will not allow a module to run in it. This is what we have done so far. RMA'd the module and the chassis. When the module is put into another slot it comes up without any issue. The only difference between this chassis and the other one we have is that we only have 2 of the 3 power supplies in it. The chassis itself has 2 sup mods and 3 48 port 10 gig mods. On a side note after we RMA'd the chassis slot 3 worked fine until we configured the new VDC and allocated the card to it. Any help will be appreciated.

Yes I am still have this issue. Here is the output you asked for.
show diagnostic result module all
Current bootup diagnostic level: complete
Module 1: 1/10 Gbps Ethernet Module
        Test results: (. = Pass, F = Fail, I = Incomplete,
        U = Untested, A = Abort, E = Error disabled)
         1) ASICRegisterCheck-------------> .
         2) PrimaryBootROM----------------> .
         3) SecondaryBootROM--------------> .
         4) EOBCPortLoopback--------------> .
         5) OBFL--------------------------> .
         6) PortLoopback:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
                 U U U U U U U U U U U U U U U U
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                 U U U U U U U U U U U U U U . .
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                 . . . . . . . . . . . U U U . U
         7) RewriteEngineLoopback:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
                 . U U U U U U U U U U U U U U U
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                 U U U U U U U U U U U U U U U U
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                 U U U U U U U U U U U U U U U U
         8) SnakeLoopback:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
         9) FIPS:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
                 U U U U U U U U U U U U U U U U
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                 U U U U U U U U U U U U U U U U
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                 U U U U U U U U U U U U U U U U
        10) BootupPortLoopback:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Current bootup diagnostic level: complete
Module 5: Supervisor Module-2 (Active)
        Test results: (. = Pass, F = Fail, I = Incomplete,
        U = Untested, A = Abort, E = Error disabled)
         1) ASICRegisterCheck-------------> U
         2) USB---------------------------> .
         3) NVRAM-------------------------> .
         4) RealTimeClock-----------------> .
         5) PrimaryBootROM----------------> .
         6) SecondaryBootROM--------------> .
         7) CompactFlash------------------> .
         8) ExternalCompactFlash----------> U
         9) PwrMgmtBus--------------------> .
        10) SpineControlBus---------------> .
        11) SystemMgmtBus-----------------> .
        12) StatusBus---------------------> .
        13) StandbyFabricLoopback---------> U
        14) ManagementPortLoopback--------> .
        15) EOBCPortLoopback--------------> .
        16) OBFL--------------------------> .
Current bootup diagnostic level: complete
Module 6: Supervisor Module-2 (Standby)
        Test results: (. = Pass, F = Fail, I = Incomplete,
        U = Untested, A = Abort, E = Error disabled)
         1) ASICRegisterCheck-------------> .
         2) USB---------------------------> .
         3) NVRAM-------------------------> .
         4) RealTimeClock-----------------> .
         5) PrimaryBootROM----------------> .
         6) SecondaryBootROM--------------> .
         7) CompactFlash------------------> .
         8) ExternalCompactFlash----------> U
         9) PwrMgmtBus--------------------> U
        10) SpineControlBus---------------> .
        11) SystemMgmtBus-----------------> U
        12) StatusBus---------------------> U
        13) StandbyFabricLoopback---------> .
        14) ManagementPortLoopback--------> .
        15) EOBCPortLoopback--------------> .
        16) OBFL--------------------------> .
Current bootup diagnostic level: complete
Module 8: 1/10 Gbps Ethernet Module
        Test results: (. = Pass, F = Fail, I = Incomplete,
        U = Untested, A = Abort, E = Error disabled)
         1) ASICRegisterCheck-------------> U
         2) PrimaryBootROM----------------> .
         3) SecondaryBootROM--------------> .
         4) EOBCPortLoopback--------------> .
         5) OBFL--------------------------> .
         6) PortLoopback:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
                 U U U U . . U U U U U U . . U .
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                 U U . . . . . . . . . . . . . .
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                 . . . . . . . . U U U U U U U U
         7) RewriteEngineLoopback:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
                 . U U U U U U U U U U U U U U U
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                 U U U U U U U U U U U U U U U U
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                 U U U U U U U U U U U U U U U U
         8) SnakeLoopback:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                 . . . . . . . . U U U U U U U U
         9) FIPS:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
                 U U U U U U U U U U U U U U U U
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
                 U U U U U U U U U U U U U U U U
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                 U U U U U U U U U U U U U U U U
        10) BootupPortLoopback:
          Port   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
          Port 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
          Port 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
                 . . . . . . . . U U U U U U U U
show module
Mod Ports Module-Type                         Model              Status
1    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
3    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     testing
5    0      Supervisor Module-2                 N7K-SUP2           active *
6    0      Supervisor Module-2                 N7K-SUP2           ha-standby
8    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
Mod Sw              Hw
1    6.2(2a)         1.0
3    6.2(2a)         1.0
5    6.2(2a)         1.1
6    6.2(2a)         1.0
8    6.2(2a)         1.0
ISSCSW7010RE-4# show module
Mod Ports Module-Type                         Model              Status
1    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
3    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     testing
5    0      Supervisor Module-2                 N7K-SUP2           active *
6    0      Supervisor Module-2                 N7K-SUP2           ha-standby
8    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     ok
Mod Sw              Hw
1    6.2(2a)         1.0
3    6.2(2a)         1.0
5    6.2(2a)         1.1
6    6.2(2a)         1.0
8    6.2(2a)         1.0
Mod Online Diag Status
1    Pass
3    Untested
5    Pass
6    Pass
8    Pass
Xbar Ports Module-Type                         Model              Status
1    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
2    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
3    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
4    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
5    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
Xbar Sw              Hw
1    NA              1.5
2    NA              1.5
3    NA              1.5
4    NA              1.5
5    NA              1.5
3    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     testing
3    48     1/10 Gbps Ethernet Module           N7K-F248XP-25E     initializing
Mod Ports Module-Type                         Model                Status
1    48     1/10 Gbps Ethernet Module    N7K-F248XP-25E          ok
3    48     1/10 Gbps Ethernet Module                                pwr-cycld
5    0      Supervisor Module-2                 N7K-SUP2          active *
6    0      Supervisor Module-2                 N7K-SUP2                      ha-standby
8    48     1/10 Gbps Ethernet Module    N7K-F248XP-25E         ok
Mod Power-Status Reason
3    pwr-cycld      Unknown. Issue show system reset mod ...
Mod Sw              Hw
1    6.2(2a)         1.0
5    6.2(2a)         1.1
6    6.2(2a)         1.0
8    6.2(2a)         1.0
Mod MAC-Address(es)                         Serial-Num
1    e4-c7-22-17-c0-8c to e4-c7-22-17-c0-bf JAF1802ANEA
5    84-78-ac-1c-fa-0f to 84-78-ac-1c-fa-21 JAF1721AQPC
6    84-78-ac-14-cb-16 to 84-78-ac-14-cb-28 JAF1713BAKS
8    e8-ed-f3-38-7b-08 to e8-ed-f3-38-7b-3b JAF1733ARPG
Mod Online Diag Status
1    Pass
5    Pass
6    Pass
8    Pass
Xbar Ports Module-Type                         Model              Status
1    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
2    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
3    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
4    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
5    0      Fabric Module 2                     N7K-C7010-FAB-2    ok
Xbar Sw              Hw
1    NA              1.5
2    NA              1.5
3    NA              1.5
4    NA              1.5
5    NA              1.5
2014 Aug 5 11:49:19 -MAF %$ VDC-2 %$ %PLATFORM-2-MOD_DETECT: Module 3 detected () Module-Type 1/10 Gbps Ethernet Module Model N7K-F248XP-25E
2014 Aug 5 11:49:19 MAF %$ VDC-2 %$ %PLATFORM-2-MOD_PWRUP: Module 3 powered up (
2014 Aug 5 11:49:19 %$ VDC-1 %$ %PLATFORM-2-MOD_DETECT: Module 3 detected ) Module-Type 1/10 Gbps Ethernet Module Model N7K-F248XP-25E
2014 Aug 5 11:49:19 %$ VDC-1 %$ %PLATFORM-2-MOD_PWRUP: Module 3 powered up ()

Nexus 1000v, VMWare ESX and Microsoft SC VMM

Hi,
Im curious if anybody has worked up any solutions managing network infrastructure for VMWare ESX hosts/vms with the Nexus 1000v and Microsoft's System Center Virtual Machine Manager.
There currently exists support for the 1000v and ESX and SCVMM using the Cisco 1000v software for MS Hyper-V and SCVMM. There is no suck support for VMWare ESX.
Im curious as to what others with VMWare, Nexus 1000v or equivalent and SCVMM have done to work around this issue.
Trying to get some ideas.
Thanks

Aaron,
The steps you have above are correct, you will need steps 1 - 4 to get it working correctly. Normally people will create a separate VLAN for their NLB interfaces/subnet, to prevent uncessisary flooding of mcast frames within the network.
To answer your questions
1) I've seen multiple customer run this configuration
2) The steps you have are correct
3) You can't enable/disable IGMP snooping on UCS. It's enabled by default and not a configurable option. There's no need to change anything within UCS in regards to MS NLB with the procedure above. FYI - the ability to disable/enable IGMP snooping on UCS is slated for an upcoming release 2.1.
This is the correct method untill the time we have the option of configuring static multicast mac entries on
the Nexus 1000v. If this is a feature you'd like, please open a TAC case and request for bug CSCtb93725 to be linked to your SR.
This will give more "push" to our develpment team to prioritize this request.
Hopefully some other customers can share their experience.
Regards,
Robert

Can a Nexus 1000v be configured to NOT do local switching in an ESX host?

Before the big YES, use an external Nexus switch and use VN-Tag. The question is when there is a 3120 in a blade chassis that connects to the ESX hosts that have a 1000v installed on the ESX host. So, first hop outside the ESX host is not a Nexus box.
Looking for if this is possible, if so how, and if not, where that might be documented. I have a client who's security policy prohibits switching (yes, even on the same VLAN) within a host (in this case blade server). Oh and there is an insistance to use 3120s inside the blade chassis.
Has to be the strangest request I have had in a while.
Any data would be GREATY appreciated!

Thanks for the follow up.
So by private VLANs, are you referring to "PVLAN":
"PVLANs: PVLANs are a new feature available with the VMware vDS and the Cisco Nexus
1000V Series. PVLANs provide a simple mechanism for isolating virtual machines in the
same VLAN from each other. The VMware vDS implements PVLAN enforcement at the
destination host. The Cisco Nexus 1000V Series supports a highly efficient enforcement
mechanism that filters packets at the source rather than at the destination, helping ensure
that no unwanted traffic traverses the physical network and so increasing the network
bandwidth available to other virtual machines"

Nexus 7010 No route to host

Hi,
I needed to add vlans on the bladecenter, So added to ports on the bladecenter and then to the main trunk port of BC as well as i created the vlan on BC.
This BC connects to two main NEXUS 7010 core switch, I added to trunk port of these switches as well and vlan was already created in the nexus core switch.
but i was unable to ping the subnet gateway from the nexus core switch and gets the error as "no route to host"
Is this something there is no routing define for this subnet. As OSPF is running on the core switch.
Thanks
Sagar

Thanks Alex
VLAN was allowed on the trunk, everything related vlan is fine.
but there was no static route defined on the switch as the routing for the subnet was done on the firewall
so what i thought is to give a static route for network with next hop as firewall interface and guess what it started to work
Thanks
Sagar

Nexus 7010 - redistribute host routes in to OSPF

In my Nexus 7010 infrastructure, I have a requirement to redistribute host routes in to OSPF so that the other connected sites receive the host routes through OSPF.
These hosts are part of the connected network (192.168.100.0/24) on Nexus, I dont want this network to be advertised in to OSPF but I want the hosts inside this subnet (192.168.100.11 and 192.168.100.12) to be advertised.
I tried to create a prefix list with these two hosts and added them to a route-map and then using the "redistribute direct" command called this route-map in to OSPF, but this is not working.
However, if I add the entire subnet (the connected network) in to this route-map, it shows up in OSPF.
Is there a way I could have only the hosts to be part of the OSPF database?

Hello, There is no need for VDC or VRF I think. are we missing a trick here. I also just tested for my own sanity. (Or am I completely under-thinking this)
N7K-1 has vlan 24 and the host route will be to 172.25.24.20
N7K-1 Config:
conf t
ip route 172.25.24.20/32 Vlan24
ip prefix-list TEST seq 5 permit 172.25.24.20/32
route-map STATIC_TO_OSPF permit 10
match ip address prefix-list TEST
router ospf 1
bfd
router-id 192.168.101.1
redistribute static route-map STATIC_TO_OSPF
here is what I see on its neighbour N7K2:
DC1-N7K2# show ip route 172.25.24.20
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
172.25.24.20/32, ubest/mbest: 1/0
    *via 192.168.102.5, Eth8/1, [110/20], 00:00:07, ospf-1, type-2
DC1-N7K2#
                Type-5 AS External Link States
Link ID         ADV Router      Age        Seq#       Checksum Tag
172.25.24.20    192.168.101.1   479        0x80000002 0x0eed    0
So in essence point the host routes statically to the directly connected interface.
hth.
Bilal

Nexus 1000v: Control VLAN must be same VLAN as ESX hosts?

Hello,
I'm trying to install nexus 1000v and came across the below prerequisite.
The below release notes for Nexus 1000v states
VMware and Host Prerequisites
The VSM VM control interface must be on the same Layer 2 VLAN as the ESX 4.0 host that it manages. If you configure Layer 3, then you do not have this restriction. In each case however, the two VSMs must run in the same IP subnet.
What I'm trying to do is to create 2 VLANs - one for management and the other for control & Data (as per latest deployment guide, we can put control & data in the same vlan).
However, I wanted to have all ESX host management same VLAN as the VSM management as well as the vCenter Management. Essentially, creating a management network.
However, from the above "VMWare and Host Prerequisites", does this means I cannot do this?
I need to have the ESX host management same VLAN as the control VLAN?
This means that my ESX host will reside in a different VLAN than my management subnet?
Thanks...

Control vlan is a totally seperate VLAN then your System Console. The VLAN just needs to be available to the ESX host through the upstream physical switch and then make sure the VLAN is passed on the uplink port-profile that you assign the ESX host to.
We only need an interface on the ESX host if you decide to use L3 control. In that instance you would create or use an existing VMK interface on the ESX host.

Nexus 5000/2000 connected to ESX host with 2 teamed NICS

Hi,
I have a question regarding a configuration we have in our Datacenter (see above)
The issue is with the Server configuration on the switch (Please note this is an ESX host with 2 NICs (active/active, same vSwitch), 1 NIC each connected to a different FEX)
Currently we have removed the 'channel-group x' from under the individual ports on each FEX and have full connectivity, i.e. no vPC configuration, how can this be working?
Rgds
Jake

ESX uses per default the following NIC-teaming method:
"Route based on the originating port ID" - Also know as vSwitch port-based load-balancing, this method chooses an uplink based on the virtual port where the traffic entered the virtual switch
(check out this PDF: http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf)
With this method you don't need to configure a channel on your Nexus switches. If you configure a port-channel (vPC) you should reconfigure the ESX vSwitch teaming to "Route based on IP hash" and make sure your port-channels on the nexus are configured as static ports (mode on) because ESX is not able to do LACP.
HTH
Marcel

Port-channel L2 problem with Fabric Interconnect and Nexus 7010

Hi,
i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
I was trying :
1. I using non dedicated port in Nexus 7010.
      - rate-mode share
      - channel-group 1 mode active
      - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
2. I using non dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode on
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
3. I using dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
4. I using dedicated port in Nexus 7010
     - rate-mode dedicated
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up and running well.
but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
i attach the topology of N7K with Fabric interconnect.
regards,
Berwin H

Hi Manish,
the issue was solved, i was fix it last week.
the solution is:
i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2) so i allocate the interface on all module
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
So here the result of my port-channel :
SVRN7KFARM-HO-01# show port-channel summary
Flags: D - Down        P - Up in port-channel (members)
        I - Individual H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
Group Port-       Type     Protocol Member Ports
      Channel
1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                     Eth1/4(P)    Eth1/25(P)
2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                     Eth1/12(P)   Eth1/26(P)
3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)
4     Po4(SU)     Eth      NONE      Eth10/32(P) Eth10/34(P) Eth10/35(P)
                                     Eth10/36(P)
Thanks.
Berwin H

Nexus 7010 bgp state change alert not triggered to NNM

Hi ,
BGP state change alert not triggered to NNM on Nexus -7010 for Monitoring.
Details of the Device:
Nexus 7010 :
Software
BIOS:      version 3.22.0
kickstart: version 5.1(3)
system:    version 5.1(3)
BGP neighbor status :
Neighbor        V    AS MsgRcvd MsgSent   TblVer InQ OutQ Up/Down State/PfxRcd
172.16.1.2      4 65505 5089234 5194515    51359    0    0     6w2d 391
172.16.1.3      4 65505 5044293 5146859    51359    0    0    30w4d 378
172.31.11.3     4 15404 120744 114811    51359    0    0     1w6d 1
172.31.42.3     4 65501 5261796 5264413    51359    0    0    2d06h 0
Snmp trap enabled:
snmp-server user admin network-admin auth md5 0x690c4ede8a88ba7f2de791dbe7a77f0a
priv 0x690c4ede8a88ba7f2de791dbe7a77f0a localizedkey
snmp-server host 172.30.0.55 traps version 2c xxxx
snmp-server enable traps bgp
Downloaded cisco-bgp4-mib version, bgp4-mib tried and performed snmpwalk as given below
nnmsnmpwalk.ovpl -c xxx 172.31.15.130 .1.3.6.1.4.1.9.9.187.0.6
Error : No MIB objects contained under subtree
nnmsnmpwalk.ovpl -v 2 -c xxx 172.31.15.130 .1.3.6.1.2.1.15.3.
No MIB objects contained under subtree
Kindly advise to resolve the issue
Regards
Hari

You can set an alert for Warning State. This is feasible.
Juke Chou
TechNet Community Support

Nexus 1000v and vcenter domain admin account

I changed out domain admin account on our domain in which vcenter services runs as and now its using a different services account. I am wondering if I need to update anything on the nexus 1000v switch side between the 1000v and venter

Hi Dan,
You are on the right track. However you can perform some of these function "online".
First you want to ensure that you are running at a minimum, Nexus 1000v SV1(4a) as ESXi 5.0 only began support on this release. With SV1(4a), it provides support for both ESXi 5.0 and ESX/i 4.1.
Then you can follow the procedure documented here:
Upgrading from VMware Release 4.0/4.1 to VMware Release 5.0.0
This document walks you through upgrading your ESX infrastructure to VMware Release 5.0.0 when Cisco Nexus 1000V is installed. It is required to be completed in the following order:
1. Upgrade the VSMs and VEMs to Release 4.2(1)SV1(4a).
2. Upgrade the VMware vCenter Server to VMware Release 5.0.0.
3. Upgrade the VMware Update Manager to VMware Release 5.0.0.
4. Upgrade your ESX hosts to VMware Release 5.0.0 with a custom ESXi image that includes the VEM bits.
Upgrading the ESX/ESXi hosts consists of the following procedures:
–Upgrading the vCenter Server
–Upgrading the vCenter Update Manager
–Augmenting the Customized ISO
–Upgrading the ESXi Hosts
There is also a 3 part video highlighting the procedure to perfrom the last two steps above (customized ISO and upgrading ESXi hosts)
Video: Upgrading the VEM to VMware ESXi Release 5.0.0
Hope that helps you with your upgrade.
Thanks,
Michael

Nexus 7010 and ESX Host

Similar Messages

Maybe you are looking for