Nov 27, 2009
I am trying to setup a HP blade (BL460) server with 2 nics on sles10sp3. I want one nic to connect to a management vlan and and second to connect to the standard network. It should be possible for a desktop in the standard network to connect to either nic by providing the correct ip address.use this server as our first virtualisation hosts server using Xen. I dont want traffic used to upload / download images to the server through nic1 to effect the users traffic on the standard network on nic2. However any attempt at routing (which Im not good at) has led to the tx traffic all going out the default route (users subnet).
View 3 Replies
Each time I setup the nics via yast2 lan I can get the standard lan nic working ok. but cannot get the management nic working correctly. The server can ping a workstation on another vlan, but the workstation cannot ping the management nic. The default route appears to be forcing all traffic on the host out through this route, which I presume is normal behaviour. Using tcpdump I can see the ping packets received by the server, the server then responds through the default gateway, which the workstation does not see.
However, this normal behaviour will result in extra traffic on the users network when image downloads are initiated from the management interface.If I use a 172.24.1.0 network routed through 172.24.1.1 router setup as our management vlan , and 188.8.131.52 with router 184.108.40.206 as our lan for general users. Where server ips are nic1 10.1.1.10 and nic2 220.127.116.11 My workstation would be 18.104.22.168. If I ping the server at 10.1.1.10
I get no response. If I ping the server at 22.214.171.124 no problem.
Basically I used the network setup recommended by vmware to manage a virtual server. I actually have 4 nics, I thought by just talking about 2 nics the problem would be easier to explain. vmware specify that two nics should be used for management and two for the Lan. This is what I am trying to achieve, but both subnets must operate independently.