Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

Internet Connectivity Architecture

Hi All,

Hope all of you doing great !!!!

I have a scenario here where a customer got 36 remote locations and 1 Hub location.Hub location is connected to Internet using STM-x bandwidth pipe.All the remote location traffic need to be routedthrough hub location.Half of the remote location are able to connectd via point to point ethernet links and half of them can be connected via MPLS.Remote location bandwidth requirements areof 2M ,4M,6m etc...

Please answer my following queries---

1)  is this a feasible solution to connected half of them via PtP links and half via MPLS VPN?what will be the achitecture look like?

2)what are the impotant things to keep in mind here.

3)when comapring ERS (ethernet Relay Service) to MPLS , what would be better option to connect remote locatons ? and why ?

Cheers,

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Blue

Re: Internet Connectivity Architecture

vicky.dhas@bt.com

Hi All,

Hope all of you doing great !!!!

I have a scenario here where a customer got 36 remote locations and 1 Hub location.Hub location is connected to Internet using STM-x bandwidth pipe.All the remote location traffic need to be routedthrough hub location.Half of the remote location are able to connectd via point to point ethernet links and half of them can be connected via MPLS.Remote location bandwidth requirements areof 2M ,4M,6m etc...

Please answer my following queries---

1)  is this a feasible solution to connected half of them via PtP links and half via MPLS VPN?what will be the achitecture look like?

2)what are the impotant things to keep in mind here.

3)when comapring ERS (ethernet Relay Service) to MPLS , what would be better option to connect remote locatons ? and why ?

Cheers,

1) Perfectly feasible. Architecture depends on where you are terminating the P2P links but as long as routing is setup correctly in your hub site there shouldn't be any problems.

2) Same as with any hub/spoke setup ie. do you have enough bandwidth at hub site for all spokes and do you have enough internet bandwidth for all sites. Also do you need to prioritise traffic from spokes so that internet traffic does not consume all bandwidth.

3) Difficult to say without knowing your requirements. In a hub/spoke P2Ps work fine but if you suddenly need spokes to talk to spokes then with P2P links you have to go via the hub. With MPLS you would not need to go via the hub ie. MPLS can be any to any.

Also if you need to move your hub office there is a lot more work in repointing all the P2Ps than simply provisioning a new connection to the MPLS network.

Jon

3 REPLIES
Hall of Fame Super Blue

Re: Internet Connectivity Architecture

vicky.dhas@bt.com

Hi All,

Hope all of you doing great !!!!

I have a scenario here where a customer got 36 remote locations and 1 Hub location.Hub location is connected to Internet using STM-x bandwidth pipe.All the remote location traffic need to be routedthrough hub location.Half of the remote location are able to connectd via point to point ethernet links and half of them can be connected via MPLS.Remote location bandwidth requirements areof 2M ,4M,6m etc...

Please answer my following queries---

1)  is this a feasible solution to connected half of them via PtP links and half via MPLS VPN?what will be the achitecture look like?

2)what are the impotant things to keep in mind here.

3)when comapring ERS (ethernet Relay Service) to MPLS , what would be better option to connect remote locatons ? and why ?

Cheers,

1) Perfectly feasible. Architecture depends on where you are terminating the P2P links but as long as routing is setup correctly in your hub site there shouldn't be any problems.

2) Same as with any hub/spoke setup ie. do you have enough bandwidth at hub site for all spokes and do you have enough internet bandwidth for all sites. Also do you need to prioritise traffic from spokes so that internet traffic does not consume all bandwidth.

3) Difficult to say without knowing your requirements. In a hub/spoke P2Ps work fine but if you suddenly need spokes to talk to spokes then with P2P links you have to go via the hub. With MPLS you would not need to go via the hub ie. MPLS can be any to any.

Also if you need to move your hub office there is a lot more work in repointing all the P2Ps than simply provisioning a new connection to the MPLS network.

Jon

New Member

Re: Internet Connectivity Architecture

Jon,

thanks for your quick reply.Few clarifications.

The connectivity to remote sites are only for Internet acces .so no bandwidth reservation for voice/data required.

MPLS topology will also be Hub-Spoke rather htan any to any

Please answer :

static routing will suffice ? or do we need to use any dynamic routing like BGP  for point to point and MPLS network ?.Here there is single link to internet

NATing is rquied anywhere?

Basically the customer is a local  ISP he want to cater different customers in 36 remote locations.

Hall of Fame Super Silver

Re: Internet Connectivity Architecture

Hello Vicky,

>> NATing is rquied anywhere?

you will need to NAT in the central site and NAT configuration has to be able to handle all IP subnets of remote sites.

I strongly suggest to use a dynamic protocol over MPLS links: eBGP sessions with SP PE nodes is easy and lightweight.

Central site can generate a default route 0.0.0.0/0 when internet link is active, and this can be passed to SP PE node.

SP will propagate this default route to all remote sites using its signalling infrastructure.

each remote site needs to advertise in BGP the local IP subnets to provide return path for packets coming from central site

On point to point links you can use iBGP or OSPF with no problems. iBGP would allow you to do not introduce a second routing process.

all this under the hyphotesis that you are not going to interconnect the two types of remote sites.

Hope to help

Giuseppe

192
Views
0
Helpful
3
Replies
CreatePlease to create content