cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5263
Views
0
Helpful
6
Replies

Multi Site Set up over MPLS

ismaelcolon
Level 1
Level 1

i am trying to set up a multi-site configuration on our UC500 over an mpls network. Our main office has the UC500 the offsite location will have a catalyst 3560. How do i set up the ip phones attached to the 3560 in the offsite location to be able to register with the UC500 at the main office? i know i have to set up ip routes in the uc500, which i think will look like this.( default voice vlan on uc500 is 10.1.1.0)

ip route 10.1.2.0 255.255.255.0 192.168.2.15 --------> first set of ip is voice vlan for offsite the second is the mpls router in main location

so i am not sure what routes to configure in the 3560 in the offsite location so the the attached phones can register and use voicemail from the main office UC500?

3 Accepted Solutions

Accepted Solutions

Maulik Shah
Level 5
Level 5

I assume this is a private MPLS network where you can reach internal networks between the sites. If so would add a couple of routes on the 3560 (which I assume is in L3 mode):

ip route 10.1.1.0 255.255.255.0 x.x.x.x where x.x.x.x is the UC520 WAN IP address

ip route 192.168.10.0 255.255.255.0 x.x.x.x where 192.168.10.0 is the data IP subnet on the UC520 and x.x.x.x is the UC520 WAN IP address

Also, you may need another route for internet traffic for PCs at off site location.

Also, on the DHCP pool on the offsite location - make sure option 150 is set to 10.1.1.1 (UC520 voice vlan IP address)

View solution in original post

It sounds like this is a L3 MPLS VPN, meaning you have different IP subnets at each side of your connection (PE - CE link). If that is the case, your UC500 and your 3500 should have routes to each other's LANs, that point to the PE IP locally (next hop), and the PE needs to know about these routes too and redistribute them to other PE's.


Also notice that Maulik's commands assume that NAT is disabled on the UC500 and the 3500.

I hope this helps.


Marcos

View solution in original post

You also need to add a route for the CUE subnet on the UC520. This is necessary because the phones at the other site need to talk to the CUE module. In addition, some of the new features present in CUE 7.0 and later require this route to be present.

If your CUE module is configured with the factory default settings, you should add the following route:

ip route 10.1.10.0 255.255.255.252 x.x.x.x (where x.x.x.x is the IP address of the UC520 WAN interface)

View solution in original post

6 Replies 6

Maulik Shah
Level 5
Level 5

I assume this is a private MPLS network where you can reach internal networks between the sites. If so would add a couple of routes on the 3560 (which I assume is in L3 mode):

ip route 10.1.1.0 255.255.255.0 x.x.x.x where x.x.x.x is the UC520 WAN IP address

ip route 192.168.10.0 255.255.255.0 x.x.x.x where 192.168.10.0 is the data IP subnet on the UC520 and x.x.x.x is the UC520 WAN IP address

Also, you may need another route for internet traffic for PCs at off site location.

Also, on the DHCP pool on the offsite location - make sure option 150 is set to 10.1.1.1 (UC520 voice vlan IP address)

yes, this is a private mpls network, and yes the 3560 is L3.

Ok, so at my offsite location i will have the voice subnet of 10.1.2.0.

the mpls router at both of my locations will have routes for 10.1.1.0, 192.168.10.0, 10.1.2.0, and whatever internet/data traffic we will have

set up UC500 with

ip route 10.1.2.0 255.255.255 x.x.x.x

set up at remote site on 3560

ip route 10.1.1.0 255.255.255.0 x.x.x.x where x.x.x.x is the UC520 WAN IP address ( should this be the ip add. of the mpls router since it has to go there to ge to main location)

ip route 192.168.10.0 255.255.255.0 x.x.x.x where 192.168.10.0 is the data IP subnet on the UC520 and x.x.x.x is the UC520 WAN IP address ( should this be the ip add. of the mpls router since it has to go there to ge to main location)

Also, on the DHCP pool on the offsite location - make sure option 150 is set to 10.1.1.1 (UC520 voice vlan IP address)( this is for tftp server correct?)

then my phones at the off site locations should register with the uc500 just like if they where at the main office?

thank you for your response Maulik i think i am headed in the right direction.

It sounds like this is a L3 MPLS VPN, meaning you have different IP subnets at each side of your connection (PE - CE link). If that is the case, your UC500 and your 3500 should have routes to each other's LANs, that point to the PE IP locally (next hop), and the PE needs to know about these routes too and redistribute them to other PE's.


Also notice that Maulik's commands assume that NAT is disabled on the UC500 and the 3500.

I hope this helps.


Marcos

You also need to add a route for the CUE subnet on the UC520. This is necessary because the phones at the other site need to talk to the CUE module. In addition, some of the new features present in CUE 7.0 and later require this route to be present.

If your CUE module is configured with the factory default settings, you should add the following route:

ip route 10.1.10.0 255.255.255.252 x.x.x.x (where x.x.x.x is the IP address of the UC520 WAN interface)

yes,  this is exactly what i wanted to confirm. thanks guys.

thanks again

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: