asked on

Cisco 3560G to 2811 Router through OPT-E-Man Multilink

First OPT-E-Man circuit, no tagging. I can not ping across the router to the switch, I know it has to be something simple I am missing please help me spot it.

:::: 3560G ::::

class-map match-all IP
  match access-group 100
class-map match-all OPT_E_MAN_TRUNK
  match input-interface  GigabitEthernet0/45

policy-map VLAN601-POLICER
  class OPT_E_MAN_TRUNK
    police 10000000 750000 exceed-action drop
policy-map VLAN601-PARENT
  class IP
   set ip precedence 1
   service-policy VLAN601-POLICER

interface GigabitEthernet0/45
switchport trunk encapsulation dot1q
switchport mode trunk
duplex full
speed 100
mls qos vlan-based

interface Vlan601
ip address 10.1.252.17 255.255.255.252
service-policy input VLAN601-PARENT

ip route 10.50.0.0 255.255.0.0 10.1.252.18

access-list 100 permit ip any any

Open in new window

:::: 2811 :::: (typing this out so some things will be abbreviated)

class-map match-any VLAN601
match access-group 1

policy-map TRACKER
class VLAN601

int FE0/0
ip address 10.1.252.18 255.255.255.252
duplex full
speed 100
service-policy input TRACKER

interface FE0/1
no ip address
duplex full
speed auto

interface FE0/1.1
encapsulation dot1q 1 native 
 ip address 10.50.1.1 255.255.255.0

int FE 0/1.2
encap dot1q 2
ip address 10.50.2.1 255.255.255.0

ip route 0.0.0.0 0.0.0.0 10.1.252.17

access-list 1 permit any

Open in new window

So I have VLAN 601 as the VLAN of choice for all of my traffic between this router and switch. On the router side of things it will have 5 local vlans for various types of traffic (I only listed 2 because you get the picture without me boring you to death).

I have the OPT-E-Man circuit plugging into 3560G on gig0/45, and on the 2811 on fe0/0. While logged into the 2811 via console, I can not ping across to 10.1.252.17.

Thanks for the assistance.

rauenpc

On the switch the native vlan on a trunk is, by default, 1. Since you have vlan 601 defined with the IP address, that traffic is actually hitting the opteman with vlan 601 tagged. the router is using untagged traffic currently

you can do this one of two ways.

int gig0/45
sw trunk native vlan 601

or

configure the router interface fe0/0 to have subinterfaces with one being fe0/0.601 tagging vlan 601.

Going the switch method is the easiest for now, but the router subinterface gives you more options for the future as you can easily add additional subinterfaces/vlans as needed across the opteman.

Todd_Bain

ASKER

Thank you for the update, I originally thought that is what I did wrong so I put in

int fe0/0
no ip address
speed 100
duplex full

int fe0/0.601
ip address 10.1.252.18 255.255.255.252
encap dot1q 601 native
service-policy input TRACKER

Open in new window

But still had no joy. I will definitely put it back in come Monday of next week when I can get back out to the location and see if I can at least talk across (maybe I had something else goofy that I just didn't see).

And I agree I would love to native the switch but I can't because that one port will (just like you said) eventually be shooting out to VLAN 602, 603 and 604 based upon other physical router locations. This is just my first one to hit.

Thanks for the update, again will try this next week and update if it solved or not.

ASKER CERTIFIED SOLUTION

rauenpc

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Todd_Bain

ASKER

Thank you very much, that definitely helps me. What you said does make sense to me now *duh I should have saw that* and I am betting come Monday this will get me fixed up.

Thank you again, I do appreciate it. Gives me something to look forward to for next week!

Todd_Bain

ASKER

Drove out Monday to the site and it still didn't work, so brought the router back with me plugged a CAT5 cable to it and the switch (to eliminate the OPT-E-MAN Circuit) and worked just like it should.

So the config is good now it is just figuring out the OPT-E-MAN Circuit from ATT, thank you again.