Solved

HP 2810 Vyatta and ESX Vlan Trunking

Posted on 2011-09-15
2
1,339 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

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

HOW TO: Install and Configure VMware vSphere Hypervisor 6.5 (ESXi 6.5), Step by Step Tutorial with screenshots. From Download, Checking Media, to Completed Installation.
In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…

685 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