Attempting to migrate service from T1 to Opt-E-Man service with 2811 router

[Thedocfox]

First - While my cisco experience is limited I'm attempting to learn. I becamse the default Cisco guy at our shop and while I do ok with the switches routers give me an issue. Any help for a newbie that's trying is greatly appreciated!!

We recently upgraded one of our remote facilities from their T1 line to bring them into our already existent ATT Opt-e-man service. I'm trying to get some assistance configuring the 2811 router at the remote location to flow the traffic across the opteman. I attempted to compare the port settings from one of our remote locations that's arleady on opteman to the port I"m trying to configure on the 2811, but since I'm comparing a 2960 switch to the 2811 there are some glaring differences and difficulties. Here's what I got, what I think I need to do, and where I"m failing will be conspicuously obvious

Remote site 1 - 2811. Trying to configure for opteman service

Remote site 2 - 2960. Already configured for Opteman, and using as a point of reference for configuration

(IP Address changed to protect the innocent)

Remote site 1 fa0/1 port config (for opteman):

interface FastEthernet0/1

ip address 10.10.10.106 255.255.255.252

ip pim sparse-dense-mode

duplex full

speed 10

end

Remote site 1 s0/3/0 config  (for current t1)

description T1 to MAIN

ip address 10.10.10. 255.255.255.252

ip pim sparse-dense-mode

encapsulation ppp

service-module t1 timeslots 1-24

service-policy output WAN

end

Remote site 1 desired configuration:

description UPLINK TO MAIN

switchport trunk encapsulation dot1q

switchport trunk native vlan 999

switchport trunk allowed vlan 76

switchport mode trunk

switchport nonegotiate

srr-queue bandwidth share 10 10 60 20

srr-queue bandwidth shape 10 0 0 0

priority-queue out

mls qos trust cos

auto qos voip trust

spanning-tree guard root

Remote site 2 configuraiton is the same as remote site 1 desired configuration except the allowed vlan is 84 instead of 76:

interface FastEthernet0/1

description UPLINK TO MAIN

switchport trunk encapsulation dot1q

switchport trunk native vlan 999

switchport trunk allowed vlan 84

switchport mode trunk

switchport nonegotiate

srr-queue bandwidth share 10 10 60 20

srr-queue bandwidth shape 10 0 0 0

priority-queue out

mls qos trust cos

auto qos voip trust

spanning-tree guard root

Unfortunately I"m missing the switchport command because I"m working on the router. I can't even get the encapsulation to work on the port. Is what I"m attempting to do even possible or do I just need to quit and call in a Cisco engineer for configuration assistance? I'd rather not and get the pride from learning the right way to do it.

Thanks again in advance!

THanks
Dustin

P.S. My first post to cisco forums. Apologies if I'm in the wrong thread.

[Giuseppe Larosa]

Hello Dustin,

.You cannot configure a router port exactly as a switch port.

However, the router fas0/1 can use Vlan based subinterface and this may be enough for the provider.

They expect your device to send ethernet frames with 802.1Q vlan tag and vlan-id=76

So you should try the following

interface fas0/1

no ip address

duplex full

speed 10

interface fas0/1.76

encapsulation dot1q 76

ip address 10.10.10.106 255.255.255.252

ip pim sparse-dense-mode

In this way you create a Vlan based subinterface that uses tagged frames with the expected vlan-id.

This should be enough to achieve basic connectivity on the new service.

Hope to help

Giuseppe

[Thedocfox]

Ok that makes sense! I'll give that a shot. It's an hour drive down there to swap out the cable and obviously have to do it after hours. I've already changed the config and will try it tonight to see how it comes across. Thank you for your fast response!!

Leads me to one more question - Now that I see what the sub interfaces are (never dealt with them before) I was looking at the configuration for the other ethernet port that currently feeds the T1 connectivity to the rest of the network. I assume I will need a sub interface for fa0/1 for all the sub interfaces for fa0/0?

interface FastEthernet0/0.1

description native interface

encapsulation dot1Q 1 native

!

interface FastEthernet0/0.200

description Default Gateway for the Data VLAN

encapsulation dot1Q 200

ip address 10.10.11.254 255.255.255.0

ip pim sparse-dense-mode

!

interface FastEthernet0/0.250

description CallManager Express Interface

encapsulation dot1Q 250

ip address 10.10.11.254 255.255.255.0

ip pim sparse-dense-mode

service-policy output output-L3-to-L2

!

interface Service-Engine0/0

ip unnumbered FastEthernet0/0.250

shutdown

service-module ip address 10.10.10.250 255.255.255.0

service-module ip default-gateway 10.10.10.254

Thanks

Dustin

[Giuseppe Larosa]

Hello Dustin,

>>  I assume I will need a sub interface for fa0/1 for all the sub interfaces for fa0/0?

No, they are not needed because fas0/0 faces the internal network in the remote site and has some vlan based subinterfaces.

The device is a router and not a switch so a single L3 interface is enough to route from/to multiple IP subnets over the new service.

fas0/0 configuration will be left unchanged and fas0/1 points to the new service. (to outer world)

Hope to help

Giuseppe

[Thedocfox]

Ok great!! THank you for your help! I will post the results tomorrow and the credit as well! Thanks again!!

Thanks
Dustin

[Giuseppe Larosa]

Hello Dustin,

you may need additional configuration to make the new service working.

For example a default static route using the new link

like

ip route 0.0.0.0 0.0.0.0 10.10.10.105

We have focused only on the basic IP connectivity.

Check how the routing is perfomed on the already working remote site 2

you can use

show ip route

show run | inc ip route

show run | inc default-gateway

the C2960 may be configured with an

ip default-gateway

if ip routing is disabled; on the router you need a default route like the one I have provided above

Hope to help

Giuseppe

[Thedocfox]

Ahh good catch. That may changes things. Or at least cause some more configuration edits on my end.. Here's a truncated view of the show ip route on the remote location 1:

Gateway of last resort is 10.10.255.105 to network 0.0.0.0

     1.1.101.0/28 is subnetted, 1 subnets

R       1.1.101.176 [120/3] via 10.10.255.105, 00:00:01, Serial0/3/0

     10.10.0.0/30 is subnetted, 1 subnets

R       10.10.5.0 [120/1] via 10.10.255.105, 00:00:01, Serial0/3/0

     10.10.0.0/16 is variably subnetted, 23 subnets, 3 masks

C       10.10.255.104/30 is directly connected, Serial0/3/0

C       10.10.255.105/32 is directly connected, Serial0/3/0

R       10.10.255.100/30 [120/1] via 10.10.255.105, 00:00:01, Serial0/3/0

R       10.10.255.0/30 [120/1] via 10.10.255.105, 00:00:01, Serial0/3/0

R       10.10.254.0/24 [120/2] via 10.10.255.105, 00:00:01, Serial0/3/0

Also:

show run | inc default-gateway

service-module ip default-gateway 10.10.250.254

Also:

show run | inc ip route

ip route 0.0.0.0 0.0.0.0 10.10.255.105 222

ip route 10.10.250.250 255.255.255.255 Service-Engine0/0

The IP route for the 2960 at remote location 2 shows the same, however it's via is 10.10.5.1, via vlan84:

R       10.10.255.106/32 [120/2] via 10.10.5.1, 00:00:27, Vlan84

R       10.10.255.104/30 [120/2] via 10.10.5.1, 00:00:27, Vlan84

R       10.10.255.100/30 [120/2] via 10.10.5.1, 00:00:27, Vlan84

Also:

show run | inc ip route

ip route 0.0.0.0 0.0.0.0 172.24.5.1 222

The show run | inc default-gateway does not return a response.

So I'm assuming that I will need to change each route on the 2811 to send it through the fa0/1 port correct? If you need more configuration info please don't hesitate to let me know!

THanks
Dustin

[Giuseppe Larosa · Accepted solution]

Hello Dustin,

from the show output that you have provided I understand that both remote sites use the RIP protocol as dynamic routing protocol.

If so all you need to check is that the IP subnet of new service is covered by network command under router rip process.

a)

Example:

if the router configuration for RiP is

router rip

version 2

network 10.0.0.0

!

and the IP subnet of new service is within 10/8 block the router configuration is fine and it will send and receive RIP updates on the new link.

you can check with

show run | begin router rip

b)

>> ip route 0.0.0.0 0.0.0.0 10.10.255.105 222

This is a floating static route to be changed in

ip route 0.0.0.0 0.0.0.0 10.10.10.105 222

This route is used only when RIP is not working. The primary default route should be a RIP route you can check with

show ip route 0.0.0.0

c)

>> service-module ip default-gateway 10.10.250.254

>>ip route 10.10.250.250 255.255.255.255 Service-Engine0/0

no change is needed for these two lines  as they refer to a service module present in the router.

Hope to help

Giuseppe

[Thedocfox]

Yes we are using RIP. I apologize for not stating that earlier. I make it an unfortunate habit to forget the finer details sometimes.

Ok I *think* I understand...

show run | begin router rip

router rip

version 2

network 10.10.0.0

network 10.10..200.0

network 10.10..250.0

network 10.10.251.0

no auto-summary

!

So if I got it right: Since all of our subnets are within that class 16 the RIP advertisements should be updated correctly after I switch the cable and unshut the fa0/1 interface correct? How quickly do the RIP advertisements take to make their notifications and changes? Is it pretty instant or should I expect a few minute delay before packets start flowing properly?

Sorry about not answering right away - Ran into a hiccup with one of our domain controllers.

Thanks
Dustin

[Giuseppe Larosa]

Hello Dustin,

you should be fine.

The router rip config  covers the new interface

RIP convergence should happen in no more then 30 seconds as the neighbor has to send all the RIP routes every hello interval (that is 30 seconds).

You should compare the RIP routes that you receive on the serial interface with those you later receive on the new interface.

IF the received set of routes is the same your migration is successful

Try also to ping some targets in HQ before (with serial interface)   and after ( with the new interface) to check effective IP connectivity.

Hope to help

Giuseppe

[Thedocfox]

Thank you! I will hopefully head out there tomorrow unless you can think of anything else I may have missed. I will try the show ip route 0.0.0.0 command as I missed that instruction earlier before I go.

I also wanted to etend a lot of gratitude! I see from your profile how much experience you have. It's a true credit to you sir to have that much experience and still be willing to help out the probably greenest cisco guy (well, trying to be a cisco guy) on these boards.

Thanks!

Dustin

[Thedocfox]

One other thing.. I'm just trying to nail this one. I've tried setting up one other cisco switch and I got close but wasn't right on day 1 and I'd like to knock this one out of the park.

The opteman network architecture recomendations suggest bandwidth shaping or risk packet loss. We already have traffic shaping across all of our switches at all locations, so can I add it to the 2811 fa0/1 port? I'm assuming even if it's not recommendend I should anyway for consistency..?

The current traffic shaping on a standard data port:

srr-queue bandwidth share 10 10 60 20

srr-queue bandwidth shape 10 0 0 0

I know when I was setting up the 2960 I did and comparing it to the 3750 some of the shaping commands were different. That's what took me a minute to figure out last time. I haven't found any for the 2811. Is that possible? Necessary?

Thanks

Dustin

[Giuseppe Larosa]

Hello Dustin,

this is something I had left uncovered.

on the router interface you cannot apply the same set of commands.

You can use modular QoS to shape all traffic exiting the interface fas0/1 pointing to the new service.

Example:

shaping to 6 Mbps

policy-map SHAPE-6Mbps

class class-default

shape average 6000000

int fas0/1

service-policy output SHAPE-6Mbps

Hope to help

Giuseppe

[Thedocfox]

Good morning Giuseppe..

I also should have posted the current QOS. I apologize for not doing so.. This is what's currently in the run config:

class-map match-any VOIP_RTP

match ip dscp ef

class-map match-any L3-to-L2_VoIP-Cntrl

match ip dscp af31

match ip dscp cs3

class-map match-all L3-to-L2_VoIP-RTP

match ip dscp ef

class-map match-any VOIP_SIGNAL

match ip dscp cs3

match ip dscp af31

class-map match-all VOIP_PAGING

match ip dscp af42

!

!

policy-map output-L3-to-L2

class L3-to-L2_VoIP-RTP

  set cos 5

class L3-to-L2_VoIP-Cntrl

  set cos 3

policy-map WAN

class VOIP_RTP

  priority percent 27

class VOIP_SIGNAL

  priority percent 5

class VOIP_PAGING

  priority percent 10

class class-default

  fair-queue

  random-detect

The configuration you posted isn't going to mess with that correct? Sorry my QOS knowledge is even less than my cisco knowledge

Thanks
Dusitn

[Thedocfox]

And as soon as I have that answer I'm going to head down there and make the switch. We don't want to wait any longer to get it on the new service and there aren't many people there today. So hopefully soon you won't have to deal with it anymore!

Thanks
Dustin