I have something similar in our lab.
Use irb to bridge the ATM
in global config:
~~~~~~~~~~~~
bridge irb
bridge 1 protocol ieee
bridge 1 route ip
on the ATM interface:
~~~~~~~~~~~~~~~~~
interface ATM1/0.826 multipoint
ip address 172.16.1.1 255.255.255.0
atm pvc 826 0 826 aal5snap inarp 1
map-group VLAN826
bridge-group 1
create a BVI:
~~~~~~~~~~
interface BVI1
mtu 1500
ip address 198.103.240.25 255.255.255.252
hope this gives you a few ideas..........
Kevin Wigle
----- Original Message -----
From: "Travis Gamble" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 09, 2001 12:02 AM
Subject: LANE over PVCs
> Hi all,
>
> I've run into a problem using a LANE blade to carry VLAN traffic over
PVCs.
> Normally, you would have LANE blades in SwitchA and in SwitchB, both of
them
> with corresponding statements like:
> atm pvc 826 0 826 aal5snap
> atm bind pvc vlan 826 826
>
> So then, any traffic for VLAN 826 is carried over a PVC on 0/826. All of
> the devices in the two switches can talk happily.
>
> The problem I have is that the other end of my tunnel is not a second LANE
> blade, but the ATM interface of a 7204 router.
>
> We have several devices in a VLAN on one switch, and they all need to talk
> to the router at the other end. Is there a way to terminate these PVCs on
> the router, and have it communicate correctly with the VLAN?
>
> So on SwitchA, we have a VLAN, 826 with several IP devices on it... the
VLAN
> is sent through to the LANE blade, and is bound to a PVC with statements
> like:
> atm pvc 826 0 826 aal5snap
> atm bind pvc vlan 826 826
>
> Then PVC 0/826 runs through an ATM network, and arrives at the ATM 1/0
> interface of a router. All of that works fine.... but once it gets there,
> the router doesn't seem to know what to do with this traffic. If it were
an
> Ethernet interface I would say "encapsulation isl 826"... but that doesn't
> apply on an ATM interface. Any ideas?
>
> The way I tried, was to make a sub-interface on the ATM interface of the
> router
> interface ATM1/0.826 multipoint
> ip address 172.16.1.1 255.255.255.0
> atm pvc 826 0 826 aal5snap inarp 1
> map-group VLAN826
>
> map-list VLAN826
> 172.16.1.2 atm-vc 826 broadcast
>
> Then try to ping across it... traffic shows up on the PVC, but doesn't
ever
> reach the VLAN correctly. Any ideas? Should that configuration have
> worked? If so, maybe I made a dumb mistake, because traffic was
definitely
> flowing to the PVC.
>
> By the way... we are unable to implement a full-scale LANE system (with a
> LECS and a LES and a BUS and all that jive). I know that would fix it,
but
> it would introduce new problems in our configuration.
>
> I definitely would appreciate any input.
>
> Regards,
> Travis Gamble
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
