Solved

HP 2810 Vyatta and ESX Vlan Trunking

Posted on 2011-09-15
2
1,326 Views
Last Modified: 2012-05-12
Hello everyone...

Having a bit of an odd issue that I just cant seem to figure out.

I have an HP 2810 switch with (4) trunks connected to (4) ESX ports.

They are set up as (4) non LACP trunks that are plugged in to the host.

On the host I have a Vyatta router with (5) interfaces that are connected to (5) Port groups (VLANS)

These trunks are set up as follows:

Default VLAN (1) Untagged
VLAN 10 Tagged
VLAN 20 Tagged, etc..

This is all set up in the host using VSwitch 2.

There are various VMs with nics assigned to port groups (10, 20 etc.) along with each interface of the router.

The Vyatta router is pointing to the gateway outside of the network and has the appropriate route back into the router to get access to the VMs back on the LAN.

Routing works and VMs have access to all the subnets and such.. All is good..

However, I wanted to be able to take a physical machine, tag its port to a corresponding VLAN on the physical switch and share the collision space with the VMs.

While the VMs can get out and back no problem, when i try to drop a physical machine on the subnet and VLAN, it wont see the router gateway.

Is there some sort of limitation that i am not aware of?

I am not an expert with Vyatta but it has been reasonably easy to set up and is not doing anything but routing.

So its set up like this:

                                        -------------Phy Machine 1 --------------
                                                          10.10.10.101
                                                                     |
                                                                     |  Port on switch
                                                                     |  VLAN 1 (Native), VLAN 20 Tagged
                                                                     |
                                               --------------2810--------------
                                                                    |
                                                                    | TRUNK VLAN1, 10, 20 Tagged
                                               -------------ESX----------------
                                                                    |
                                                                    |
                                                    VSwitch Port Groups

                                         Native    |        10               |            20           |                                
                                  -----------------------------------------------------------------
      Vyatta Int 10.1                                     |  Vyatta Int 20.1     |
          ----------------------------------------------                                |              
          |                            ----------------------------------------------
          |                            |
          |                            |
      VM1                      VM2
10.10.10.100          10.10.20.100                    


VM1 can see VM 2 and can see any machines reachable in the routing tables.

Phy Machine 1 Cannot see anything and nothing can see it. (not even the 10.1 interface on the Vyatta router.

The way i was thinking was that with the Vyatta router and its interfaces on the VSwitch trunked up with the 2810, that all of its interfaces would be in the same collision space as the physical machines.

The only way they can talk to each other is if i move all the interfaces into the native port group. Then everything sees everything as it should.

Not sure what Im doing wrong here but i could use some assistance.

Much appreciated!

Best
0
Comment
Question by:pacman_d
  • 2
2 Comments
 

Author Comment

by:pacman_d
ID: 36547256
Added note,

I also wanted to serve up DHCP off of a physical machine on the native VLAn and have its port tagged up with all the VLANs i want to serve addresses to.

Maybe something to do with trunking possibly.

0
 

Accepted Solution

by:
pacman_d earned 0 total points
ID: 36559543
Too many experts looking for the easy points I guess.

Figured it out my self, as it increasingly seems to be the case lately.

Hard to understand why I am paying when it is becoming easier to find answers on the boards.
I am a long time customer of EE.

PAQ me please..

Thanks...
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Join & Write a Comment

Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
HOW TO: Connect to the VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere (HTML5 Web) Host Client 6.5, and perform a simple configuration task of adding a new VMFS 6 datastore.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now