Hi!
Hi!
I'm having more strange issues with my GRE-based isolated networks:
While investigating my other issues, I noticed this output from "ovs-vsctl
show" on the xenservers:
Bridge "xapi29"
fail_mode: standalone
Port "t1546-4-3"
Interface "t1546-4-3"
type: gre
options: {key="1546", remote_ip="10.33.2.6"}
Port "vif28.0"
Interface "vif28.0"
Port "xapi29"
Interface "xapi29"
type: internal
I wonder why this IP address for the GRE tunnel was chosen? The IP belongs to
one of my iSCSI storage networks, and should never be used for guest or public
traffic.
While thinking about it, I noticed that I never assigned IP addresses to the
"correct" guest interfaces (neither via XenServer nor via cloudstack), as the
documentation did not mention it... but of course GRE won't work without IP
connectivity between the OpenVSwitch instances on the XenServers.
So I wonder why CloudStack (or XenServer?) chose one of the iSCSI networks for
GRE traffic instead of e.g. printing an error message or chosing at least the
management network...
I also see that the OVSTunnelXXX networks on the XenServer cluster are not
removed when I remove a Network from CloudStack, so during my experiments some
stale OVSTunnel interface pile up on the cluster.
Ciao
Martin
