How would you route traffic between these 3 sites?

[nowwhatnapster]

I'm starting to delve into more complex networks and I am looking for some feedback on this setup.

Flat network, no vlans
Subnets X, Y, & Z need to talk to each other.
ISP A also does PRI for voice at all 3 sites on the shared pipe

• Site X (subnet x) (firewall x)
  • Interface 0: MPLS (ISP A) (10M shared)
  • Interface 1: WAN (ISP A) (10M shared)
  • Interface 2: LAN (subnet X)
• Site Y (subnet y) (firewall y)
  • Interface 0: MPLS (ISP A) (10M shared)
  • Interface 1: WAN (ISP A) (10M shared)
  • Interface 2: MPLS (ISP B) (100M)
  • Interface 3: Cable (ISP B) (30/8M)
  • Interface 4: LAN (subnet y)
• Site Z (subnet z) (firewall z)
  • Interface 0: MPLS (ISP A) (10M shared)
  • Interface 1: WAN (ISP A) (10M shared)
  • Interface 2: MPLS (ISP B) (100M)
  • Interface 3: Cable (ISP B) (30/8M)
  • Interface 4: LAN (subnet z)

I assume it makes sense to have site Y and Z to utilize the 100M pipe and reserve the 10M for backup. Would routing statements like this work?.

• Firewall X
  • Route: Subnet Y, Gateway (ISPA MPLS), metric 1
  • Route: Subnet Z, Gateway (ISPA MPLS), metric 1
• Firewall Y
  • Route: Subnet X, Gateway (ISPA MPLS), metric 1
  • Route: Subnet Z, Gateway (ISPB MPLS), metric 1
  • Route: Subnet Z, Gateway (ISPA MPLS), metric 2
• Firewall Z
  • Route: Subnet X, Gateway (ISPA MPLS), metric 1
  • Route: Subnet Y, Gateway (ISPB MPLS), metric 1
  • Route: Subnet Y, Gateway (ISPA MPLS), metric 2

 

[stormy1]

Sorry we can not do your homework for you.

 

[DermicSavage]

You need to use a routing protocol or tracked routes to support the ability to fail over.

From your design, it suggests you are using static routes with different metrics. If that is the case, you need to add tracking to the primary MPLS circuit so that if it goes down, it will remove that route from the routing table and then use the fail over circuit with the metric of 2. The alternative to this is using a routing protocol like iBGP to handle the routing changes

 

[austeze]

You need to use a routing protocol or tracked routes to support the ability to fail over.

From your design, it suggests you are using static routes with different metrics. If that is the case, you need to add tracking to the primary MPLS circuit so that if it goes down, it will remove that route from the routing table and then use the fail over circuit with the metric of 2. The alternative to this is using a routing protocol like iBGP to handle the routing changes

Agreed +1