VMware Cloud Community
ravargs
Contributor
Contributor
Jump to solution

Multiple vmkernal interfaces with different gateways?

Hello,

I am trying to setup a homelab with multiple vswitchs and vmknics.

I have my management network on 10.10.1.0/24(vSwitch0,vmnic0) and ISCSI on 10.10.2.0/24 (vSwitch1, vmnic1).

Issue I am facing is not able to configure the gateway for the iscsi vmkernal interface. It always default to the management networks gateway.

Thanks

RV

Reply
0 Kudos
1 Solution

Accepted Solutions
ravargs
Contributor
Contributor
Jump to solution

The issue was cause by the vmnet interfaces of workstation not listening on promiscuous mode. I changed that and now everything works perfectly.

Thanks all for the suggestions.

View solution in original post

Reply
0 Kudos
7 Replies
a_p_
Leadership
Leadership
Jump to solution

Welcome to the Community,

although it is basically possible to configure static routes, there should actually be no need for this in your case. The only VMkernel which might require a gateway is the Management Network. For the iSCSI network, both - the ESXi hosts as well as the iSCSI storage - should be in the same subnet, so no routing/gateway is required (routing is not supported for iSCSI anyway).

André

Reply
0 Kudos
rcporto
Leadership
Leadership
Jump to solution

Totally agree with André and about multiple gateways, take a look on this KB article: VMware KB: Configuring static routes for vmkernel ports on an ESXi host

Unlike ESX, ESXi does not have a service console. The management network is on a vmkernel port and, therefore, uses the default vmkernel gateway. Only one vmkernel default gateway can be configured on an ESXi/ESX host. You can, however, add static routes to additional gateways/routers from the command line.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
ravargs
Contributor
Contributor
Jump to solution

Hi

Thanks for the replies.

What I was trying to achieve was to keep the management, iscsi and vmotion vmkernal interfaces in different vswitchs and physical nics.

iscsi network - 10.10.2.0/24 and gw 10.10.2.1.

Problem is vmware is not allowing me to change the gateway for the new vmkernal interface(iscsi). So even though the route is there ip will not be reachable once the vmk interface is created.

The gateway for iscsi network will be reachable before creating the vmk interface but not after.

1.png

2.png

4.png

3.png

Thanks

RV

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

What I was trying to achieve was to keep the management, iscsi and vmotion vmkernal interfaces in different vswitchs and physical nics.

That's ok, but again, you don't usually need a gateway for iSCSI and/or vMotion as the traffic stays within the subnet and doesn't need to be routed.

André

Reply
0 Kudos
ravargs
Contributor
Contributor
Jump to solution

Ok I understand that. But what I am confused is the ips on the  new vmk interface range are not reachable.

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

So are you saying that although the iSCSI VMkernel port group as well as the iSCSI storage system are both in the 10.10.2.x subnet, they can't ping each other? Remember that without the gateway, you can only ping within the iSCSI subnet.

André

Reply
0 Kudos
ravargs
Contributor
Contributor
Jump to solution

The issue was cause by the vmnet interfaces of workstation not listening on promiscuous mode. I changed that and now everything works perfectly.

Thanks all for the suggestions.

Reply
0 Kudos