So a little more context around the question. I am trying to solve the problem that occurs when you want to egress from a VDC to some place that is not the Internet. So as an example if you have a VDC within a CloudStack managed environment with Internet access which will also connect to another physical environment within the same datacenter (or not) that is layer 3 separated from the virtualized environment.
I can see two options for solving this issue. One would be to get a second external interface configured on the CloudStack managed gateway that would route me to a private VRF somewhere on the provider core while the second way which is the one that spawned this question would be to bring up a separate gateway (This now involves having two routers/firewalls within the same VDC). With the second gateway we can now add routes directly to the VMs themselves using option 121 (or 33/249 pending some of the OS differences) on the DHCP server to control what egress point the VM would choose. Jeffrey S. McGovern SunGard Availability Services 401 N. Broad Street - Mezzanine Philadelphia, PA 19108 Desk: 215-446-2722 Fax: 215-408-4700 jeffrey.mcgov...@sungard.com On Tue, Feb 5, 2013 at 9:29 AM, Chip Childers <chip.child...@sungard.com>wrote: > On Mon, Feb 4, 2013 at 2:59 PM, Jeffrey McGovern > <jeffrey.mcgov...@sungard.com> wrote: > > Hello, > > I was wondering if there is a way to configure static routes on a guest > VM > > after it has been provisioned via Cloudstack? > > Jeff, > > It may help if you provide a little more context to the question to > help folks understand what you're looking to do. > > -chip > >
