Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

VLAN issue between two ESXi hosts

Hello

I have two VMs based on VMware and some VLAN configuration

 

VM1 - VLAN 130 on ESXi01

VM2 - VLAN 135 on ESXi02

 

Per exemple, a machine from the ESX1 vlan 130 can't ping an another VM in the ESX2 vlan 130. But if I move the second VM to the ESX1, it's working.

From VM1 im going via vSwitch on VLAN 130 via ESXi01 box, which that ESXi is going via vmnic11 on port Vethernet910 on FABRIC

 

FABRIC-001-B# connect nxos
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
FABRIC-001-B(nxos)# sh ver

 

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-2014, 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 5.2(3)N2(2.21c)
  system:    version 5.2(3)N2(2.21c)
  power-seq: Module 1: version v2.0
             Module 2: version v1.0
             Module 3: version v2.0
  uC:        version v1.2.0.1
  SFP uC:    Module 1: v1.1.0.0
  BIOS compile time:       05/09/2012
  kickstart image file is: bootflash:///installables/switch/ucs-6100-k9-kickstart.5.2.3.N2.2.21c.bin
  kickstart compile time:  2/5/2014 11:00:00 [02/05/2014 19:47:41]
  system image file is:    bootflash:///installables/switch/ucs-6100-k9-system.5.2.3.N2.2.21c.bin
  system compile time:     2/5/2014 11:00:00 [02/05/2014 21:42:39]


Hardware
  cisco UCS 6248 Series Fabric Interconnect ("O2 32X10GE/Modular Universal Platform Supervisor")
  Intel(R) Xeon(R) CPU         with 16553964 kB of memory.
  Processor Board ID

  Device name: FABRIC-001-B
  bootflash:   31266648 kB

Kernel uptime is 147 day(s), 15 hour(s), 15 minute(s), 46 second(s)

Last reset
  Reason: Unknown
  System version: 5.2(3)N2(2.21c)
  Service:

plugin
  Core Plugin, Ethernet Plugin, Fc Plugin, Virtualization Plugin
FABRIC-001-B(nxos)#

 

on NXOS i can see

 

FABRIC-001-B(nxos)# show run interface vethernet 910

interface Vethernet910
  description server 1/3, VNIC VNIC9
  switchport mode trunk
  switchport trunk allowed vlan 1,108-109,115-119,150-151
  pinning server sticky border-interface port-channel13
  pinning server pinning-failure link-down
  service-policy type queuing input default-in-policy
  bind interface port-channel1282 channel 910
  no shutdown

 

and portchannel information

 

FABRIC-001-B(nxos)# sh 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)
        M - Not in use. Min-links not met
--------------------------------------------------------------------------------
Group Port-       Type     Protocol  Member Ports
      Channel
--------------------------------------------------------------------------------
11    Po11(SU)    Eth      LACP      Eth1/15(P)   Eth1/16(P)   Eth1/31(P) Eth1/32(P)
13    Po13(SU)    Eth      LACP      Eth1/14(P)   Eth1/30(P)
1280  Po1280(SU)  Eth      NONE      Eth1/1/13(P)  Eth1/1/14(P)  Eth1/1/15(P)  Eth1/1/16(P)
1281  Po1281(SU)  Eth      NONE      Eth1/1/1(P)  Eth1/1/3(P)
1282  Po1282(SU)  Eth      NONE      Eth1/1/9(P)  Eth1/1/11(P)
1283  Po1283(SU)  Eth      NONE      Eth1/1/5(P)  Eth1/1/7(P)
1284  Po1284(SU)  Eth      NONE      Eth2/1/1(P)  Eth2/1/3(P)
1285  Po1285(SU)  Eth      NONE      Eth3/1/1(P)  Eth3/1/3(P)
1286  Po1286(SU)  Eth      NONE      Eth3/1/5(P)  Eth3/1/7(P)
1287  Po1287(SU)  Eth      NONE      Eth3/1/9(P)  Eth3/1/11(P)
1288  Po1288(SU)  Eth      NONE      Eth3/1/13(P)  Eth3/1/14(P)  Eth3/1/15(P) Eth3/1/16(P)
1289  Po1289(SU)  Eth      NONE      Eth4/1/1(P)  Eth4/1/3(P)
1300  Po1300(SU)  Eth      NONE      Eth1/1/17(P)  Eth1/1/19(P)

 

I have missing VLANs, how can i edit and put information about vlan ?

From UCS Manager ? I dont have 1000v.

1 ACCEPTED SOLUTION

Accepted Solutions

Hi, To add VLANs, you need to

Hi,

 

To add VLANs, you need to go to the LAN tab and create them and after that, add them to the vNIC of the blades you want to pass traffic for that/those VLAN(s).

Did you set up a Native VLAN in UCSM?

Are both, ESXi01 & ESXi02 using the same Fabric Interconnect to pass traffic?  If one host is passing traffic through A and the other through B, the traffic will need to travel to the upstream switch to be switches cause the fabrics do not switch traffic between them.

Try the commands below and paste them here:

*show service-profile circuit server X/Y  << chassis/server in question

*connect nxos a|b   << first try "a" then "b" and the output of the below command for both

*sh pinning border-interfaces

*show platform soft enm inter info vlandb id #   <<<< "#"meaning the vlan number

 

-Kenny

 

 

1 REPLY

Hi, To add VLANs, you need to

Hi,

 

To add VLANs, you need to go to the LAN tab and create them and after that, add them to the vNIC of the blades you want to pass traffic for that/those VLAN(s).

Did you set up a Native VLAN in UCSM?

Are both, ESXi01 & ESXi02 using the same Fabric Interconnect to pass traffic?  If one host is passing traffic through A and the other through B, the traffic will need to travel to the upstream switch to be switches cause the fabrics do not switch traffic between them.

Try the commands below and paste them here:

*show service-profile circuit server X/Y  << chassis/server in question

*connect nxos a|b   << first try "a" then "b" and the output of the below command for both

*sh pinning border-interfaces

*show platform soft enm inter info vlandb id #   <<<< "#"meaning the vlan number

 

-Kenny

 

 

164
Views
0
Helpful
1
Replies
CreatePlease to create content