wilson2468
Technical User
I have the following situation:
HW site connected to remote sites through MPLS cloud. All sites running OSPF.
All sites have static mapped default gateway (0.0.0.0 0.0.0.0 )with next hop
pointing back into the cloud.
The reason is the service provider has injected a route for all of the sites to
go to the Internet via the MPLS cloud, if the destination of the traffic is not
one of the company sites.
I have a failover situation where I need to make the default gateway dynamic.
Since the HQ site (where I am going to put the "default-information
originate command) is also pointing back into the MPLS cloud, can I use the
default-information originate as the dynamic default gateway?
My goal is to have all sites point into MPLS cloude unless there is a link
failure, then there will be a static route with higher AD pointing to the
failover link.
The main thing, is to make sure all remote sites point back into MPLS cloud for
gateway of last resort, so they can get Internet.
Is it ok to do this?
HW site connected to remote sites through MPLS cloud. All sites running OSPF.
All sites have static mapped default gateway (0.0.0.0 0.0.0.0 )with next hop
pointing back into the cloud.
The reason is the service provider has injected a route for all of the sites to
go to the Internet via the MPLS cloud, if the destination of the traffic is not
one of the company sites.
I have a failover situation where I need to make the default gateway dynamic.
Since the HQ site (where I am going to put the "default-information
originate command) is also pointing back into the MPLS cloud, can I use the
default-information originate as the dynamic default gateway?
My goal is to have all sites point into MPLS cloude unless there is a link
failure, then there will be a static route with higher AD pointing to the
failover link.
The main thing, is to make sure all remote sites point back into MPLS cloud for
gateway of last resort, so they can get Internet.
Is it ok to do this?