• May 21, 2018, 02:47:55 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Avaya 5698 Trunk-Port and ESXi  (Read 802 times)

0 Members and 1 Guest are viewing this topic.

Offline streetfighter12

  • Rookie
  • **
  • Posts: 4
Avaya 5698 Trunk-Port and ESXi
« on: April 03, 2017, 06:52:54 AM »
Hi,

First off, I would say thank you for this great forum. I read already a lot in it and got very useful stuff, but  actually I have a problem and don't know how to fix it.

I can't ping from my core switch our esxi which is connected to a trunk-uplink.

Network topology:
From the switch I can ping any client (vlan 1, access port) and from any computer in vlan 1 I can ping the switch ip, too. I have one trunk port connected to our ESXi (10GB XFP Uplink, Port 97) -> Any user can ping the esx and all of it's guests. So far, all is working.

But the switch itself and the ESXi (+guests) can't ping each other.

The ESX-port is setup as "tagALL". The IPs are all in same subnet and I setup the global default gateway (Is a ESXi guest, so actually not reachable). IP routing is disabled.


Actually I researched the internet a lot and running out of idea's. I would be really thankful if someone had a hint for me.

If you need my switch configuration or something else, please let it me know.

Regards Yannik


Offline MatzeKS

  • Sr. Member
  • ****
  • Posts: 286
    • matzeks
    • Controlware GmbH - Germany
Re: Avaya 5698 Trunk-Port and ESXi
« Reply #1 on: April 03, 2017, 08:15:13 AM »
Hi Yannik,

I guess it make sense to provide the "running-config" of your ERS5698.

Thanks
------------------------------------------------------
ACE-Fx #00050

Offline streetfighter12

  • Rookie
  • **
  • Posts: 4
Re: Avaya 5698 Trunk-Port and ESXi
« Reply #2 on: April 03, 2017, 09:03:50 AM »
Hi,

you can find my config in the attachments.

Thank you

Yannik

Offline MatzeKS

  • Sr. Member
  • ****
  • Posts: 286
    • matzeks
    • Controlware GmbH - Germany
Re: Avaya 5698 Trunk-Port and ESXi
« Reply #3 on: April 03, 2017, 09:13:23 AM »
Ok, you've IP routing enabled, and your uplink-port 1/97 is in default vlan and set to tagAll.
So far so good - all clients in vlan 1 should be able to reach each other.
If you have issues for your clients "inside" your virtual environment reaching each other and the ERS5698, seems there is an mismatch inside your virtual switch with settings in tagging/untagging.

Additionally you can try to figure out if all of your "guests" are visible on your uplink 1/97 in vlan 1 by:

# CLI:
show mac-address-table port 1/97

good luck
« Last Edit: April 03, 2017, 09:21:13 AM by MatzeKS »
------------------------------------------------------
ACE-Fx #00050

Offline streetfighter12

  • Rookie
  • **
  • Posts: 4
Re: Avaya 5698 Trunk-Port and ESXi
« Reply #4 on: April 03, 2017, 09:42:27 AM »
Thank you!

The interesting thing is that the output of "show mac-address-table port 1/97" shows every guest of the esxi.

Here are some test results:
ERS <-> ESXi = not working
ERS <-> Computer (vlan 125) = not working (Cause it cannot reach pfSense Gateway?)
Computer (vlan 1) <-> Computer (vlan 1) = working
Computer (vlan 1) <-> Computer (vlan 125) = working
ESXi Guest <-> ESXi Guest = working
ESXi Guest <-> Computer (vlan 1) = working
ESXi Guest <-> ERS = not working

Only the connection between ERS (10.0.1.31) and ESXi (+Guests) doesn't work.

It seems so, that the ERS cannot ping through the trunk, for some reasons.

I will check the virtual switch on the esxi again and do some tests.
« Last Edit: April 03, 2017, 10:43:47 AM by streetfighter12 »

Offline streetfighter12

  • Rookie
  • **
  • Posts: 4
Re: Avaya 5698 Trunk-Port and ESXi
« Reply #5 on: April 04, 2017, 11:32:26 AM »
Got it fixed  - More or less :)

I think the problem was that the management interface of the switch sends only untagged packages. So, they won't go through my trunked port to my vsphere server.

Now I setup a new vSwitch on ESXi and connect it to an access port on our core switch (Avaya 5698). Then I put a new interface on our Gateway and connect it to the vSwitch, too.

On the Avaya I disabled ip routing completly (Layer 2 capability is enough for me). I changed the management network on the switch to my management vlan and the ip of the switch, too.

Result = Anything is working and anything is pingable.

Last question's: Am I right, that the switch management interface only sends untagged packages or is there a way to get working with my trunking port?

Thanks very much for your help.

Regards Yannik