Hi Folks,
I'm using CS 4.2 with KVM and basic network.
This mail is pretty long, but my questions is quite short. I'm trying to
figure out how I could change which bridge my SSVM uses when it to connects
to my SAN server.
Including some of my thoughts and details below for this
-------------------------------------------------
When the agent creates the SSVM it seems to be using the default gateway
route for configuring all of the SSVM network interfaces.
This causes my SSVM not to be able to connect to my SAN server. As the SAN
server is on a completely different network (dedicated network
segment&switch).
My agent.properties file contains the following rows:
guest.network.device=cloudbr0
private.network.device=cloudbr0
public.network.device=cloudbr0
I would like my storage network communication to go over cloudbr1, which is
my agent network interface for my SAN network.
I'm very unsure about which, if any of these, that I should change. And I'm
also unsure if changing them would solve this issue.
Of course I could go ahead and do some manual NIC and route changes over at
my SSVM but that feels like the wrong solution to this issue.
========
Agent interfaces
========
cloudbr0 - addr: 10.100.38.150 mask:255.255.255.128
cloudbr1 - addr: 172.30.11.200 mask:255.255.255.0
cloud0 - inet addr:169.254.0.1 mask:255.255.0.0
eth0 - bridged to cloudbr0
eth1 - bridge to cloudbr1
========
Agent default route
========
$ip route|grep default
default via 10.100.38.129 dev cloudbr0
============
SSVM network interfaces
============
root@s-1-VM:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 0e:00:a9:fe:00:f7
inet addr:169.254.0.247 Bcast:169.254.255.255 Mask:255.255.0.0
eth1 Link encap:Ethernet HWaddr 06:11:d0:00:00:02
inet addr:10.100.38.131 Bcast:10.100.38.255 Mask:255.255.255.128
eth2 Link encap:Ethernet HWaddr 06:f5:ce:00:00:07
inet addr:10.100.38.136 Bcast:10.100.38.255 Mask:255.255.255.128
eth3 Link encap:Ethernet HWaddr 06:df:14:00:00:01
inet addr:10.100.38.130 Bcast:10.100.38.255 Mask:255.255.255.128
============
Manual mount test from SSVM, will reach timeout as it can't route to the
destination ip
============
root@s-1-VM:/tmp# mount -v -t nfs 172.30.11.20:/mnt/vg2/vol2/nfs2 /tmp/test
mount.nfs: timeout set for Wed Nov 20 16:19:50 2013
mount.nfs: trying text-based options
'vers=4,addr=172.30.11.20,clientaddr=10.100.38.131'
Best Regards,
Magnus
