Avatar of sunhux
sunhux

asked on 

VMWare Redhat vswif0 nic - setup for 4 NICs bonded/teamed to connect to network (link up/down)

Hi,

We've just installed Redhat Linux server 5.1 on VMWare ESX server & the
VMWare host boots up on the Linux.

However, the console kept giving "link up/down" - don't know which NIC is this.

Also, "ifconfig -a" showed there's several links :
vmnic0  vmnic1 vmnic2  vmnic3   vswif0

Only vmswif0 has an IP addr (& this is the address specified
during installation)

We still can't get the VMWare reachable from other servers
& from this VMWare server, I still can't ping to other servers
or other servers can't ping to this vswif0 IP addr

Is bonding/teaming of the vmnic's needed.

The hardware is HP Proliant 480C & it comes built-in with a
Gbe2c switch (you can't see the physical NICs of the server,
only the switch's ports which we connect up cables to the
Cisco core switch)
What's the next steps
Linux DistributionsVMware

Avatar of undefined
Last Comment
sunhux
SOLUTION
Avatar of larstr
larstr
Flag of Norway image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
ASKER CERTIFIED SOLUTION
Avatar of larstr
larstr
Flag of Norway image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of sunhux
sunhux

ASKER

Thanks Lars, appreciate it.

I would like to just zoom into my specific problem here :

The HP Proliant 480C comes with a Layer3 switch built in :

a)we have succeeded in building a Windows guest client  inside this VMWare
   server earlier.  The Windows client has an  IP addr 10.51.x.y  &  it uses the
   very same switch & is able to get connected to other LANs.  So from this
   Windows client, I'm able to ping to other servers on other subnets & vice-
   versa

b)however, after building this Linux ESX inside the same VMWare, it's able to
   to boot up fine, just that it's unable to even reach the built-in Layer 3 switch:
   From this Layer3 switch, I'm able to ping to the Windows guest client
   10.51.x.y  but  from this built-in Layer3 switch, I'm unable to ping to the
   Linux client (172.17.y.z) (with vswif0 interface up & running)

c) I then tried to configure an IP addr for eth2 (172.17.y.t) in this Linux client
   but it did not help make this Linux client reachable from anywhere

Is there a firewall within Linux which could have prevented these connectivity
& if so how do we disable it?
Avatar of sunhux
sunhux

ASKER


It's solved after googling around :

In ESX Linux, issue :
esxcfg-vswitch -v 16 -p "Service Console"

Go to the admin of the switch to tag the VLAN to the ports
(using the GUI)
VMware
VMware

VMware, a software company founded in 1998, was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies. VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture. Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.

39K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo