Junos OS

The way vmware works you can configure both as normal vlan either access or trunk ports.  Naturally with access you only get one vlan and trunk allows multiple vlans to be available to you VMs.  With nic teaming they both back each other up inside the server.

With multiple vlan you would create virtual networks and assign matching tags in vsphere and each vlan would have their own vSwitch for the VMs to connect.

Thanks a lot for the answer and what about Mikrotik part ? 

I have also one mikrotik router , I connected two interfaces from this router to Juniper for redundancy so can I assign the two ports from Mikortik to the same VLAN on the same Juniper  using the following commands 


set interfaces ge-0/0/12 unit 0 family ethernet-switching vlan members public

set interfaces ge-0/0/13 unit 0 family ethernet-switching vlan members public

The way vmware works you can configure both as normal vlan either access or trunk ports.  Naturally with access you only get one vlan and trunk allows multiple vlans to be available to you VMs.  With nic teaming they both back each other up inside the server.

With multiple vlan you would create virtual networks and assign matching tags in vsphere and each vlan would have their own vSwitch for the VMs to connect.

Having the two ports active in the same vlan on the Microtik will depend on what that configuration is on the other side.  As long as the configuration there does not create a loop it would be fine.  I'm not sure what role the Microtik is playing here.

If you are looking for link redundancy the more typical solution would be to make an AE (aggregated ethernet) link between the Mikrotik and Juniper switch with two members.

Thanks a lot for the answer and what about Mikrotik part ? 

I have also one mikrotik router , I connected two interfaces from this router to Juniper for redundancy so can I assign the two ports from Mikortik to the same VLAN on the same Juniper  using the following commands 


set interfaces ge-0/0/12 unit 0 family ethernet-switching vlan members public

set interfaces ge-0/0/13 unit 0 family ethernet-switching vlan members public

The way vmware works you can configure both as normal vlan either access or trunk ports.  Naturally with access you only get one vlan and trunk allows multiple vlans to be available to you VMs.  With nic teaming they both back each other up inside the server.

With multiple vlan you would create virtual networks and assign matching tags in vsphere and each vlan would have their own vSwitch for the VMs to connect.

Hello @spuluka 

The two ports from the Mikrotik are a part of a bridge , and it's connected as well to VMware server .

Having the two ports active in the same vlan on the Microtik will depend on what that configuration is on the other side.  As long as the configuration there does not create a loop it would be fine.  I'm not sure what role the Microtik is playing here.

If you are looking for link redundancy the more typical solution would be to make an AE (aggregated ethernet) link between the Mikrotik and Juniper switch with two members.

Thanks a lot for the answer and what about Mikrotik part ? 

I have also one mikrotik router , I connected two interfaces from this router to Juniper for redundancy so can I assign the two ports from Mikortik to the same VLAN on the same Juniper  using the following commands 


set interfaces ge-0/0/12 unit 0 family ethernet-switching vlan members public

set interfaces ge-0/0/13 unit 0 family ethernet-switching vlan members public

The way vmware works you can configure both as normal vlan either access or trunk ports.  Naturally with access you only get one vlan and trunk allows multiple vlans to be available to you VMs.  With nic teaming they both back each other up inside the server.

With multiple vlan you would create virtual networks and assign matching tags in vsphere and each vlan would have their own vSwitch for the VMs to connect.