[c-nsp] Frame PVC -> 802.1q VLAN
Joe Freeman
joe at netbyjoe.com
Tue Dec 19 18:11:59 EST 2006
Adtran picked up the Whiterock stuff recently. I haven't heard yet what
their plans are for it.
Joe
On 12/19/06, Matthew Crocker <matthew at crocker.com> wrote:
>
>
> Seranoa had a product which did that (Frame Relay Frames -> dot1q
> VLAN tagging) called the WANPort. Their techology was purchased by
> Whiterock (www.whiterock.com) and is now sold as the VLX300 &
> VLX400. I have one of the old Seranoa boxes, works great, too bad
> they never survived. It can do FR-PVC, PPP, MLPP, HDLC framing to
> 802.1q, terminate an OC-12 worth of DS-1s into 336 vlans on a GigE
> trunk going to a router.
>
>
> On Dec 19, 2006, at 4:53 PM, David Freedman wrote:
>
> >> Hmm, above you say "...at the IP level" and here you say
> >> "bridge". So
> >> which do really want; layer 2 interworking or layer 3 forwarding?
> >
> > I actually want to bridge raw IP packets , I know that sounds strange
> > but would be the terminology I would use when configuring IRB
> > between a
> > serial interface and an ethernet one (i.e Frame-Relay frames
> > arriving on
> > serial interface have their IP payload stripped out, and put in an
> > ethernet frame and sent over the ethernet)
> > I'm reluctant to call it "routed" since no IP routing is taking place.
> >
> >
> >
> >> I think you are more looking for L2VPN Interworking. It's generally
> >> used
> >> between PE devices but I suppose could be done local to the same PE
> >
> > I didn't try L2VPN interworking (we use this already to achieve the
> > same
> > thing across the network) simply because I assumed that it would not
> > work locally on the same box.
> >
> > Having just tried it, I can confirm it does not work, allthough saying
> > that the looped back pseudowire seems to have established itself:
> >
> > Router#show l2tun
> > Tunnel and Session Information Total tunnels 2 sessions 2
> >
> > LocID RemID Remote Name State Remote Address Port Sessions
> > L2TPclass
> > 11333 52675 R4 est 10.8.8.8 0 1
> > interworking-cl
> >
> > LocID RemID TunID Username, Intf/
> > State
> > Vcid, Circuit
> > 42051 42053 11333 1, Fa2/0.200:200
> > est
> >
> > LocID RemID Remote Name State Remote Address Port Sessions
> > L2TPclass
> > 52675 11333 R4 est 10.9.9.9 0 1
> > interworking-cl
> >
> > LocID RemID TunID Username, Intf/
> > State
> > Vcid, Circuit
> > 42053 42051 52675 1, Se1/0:200
> > est
> >
> >
> > Router#show l2tun session all | in sent
> > 8 Packets sent, 0 received
> > 1402 Bytes sent, 0 received
> > 0 Packets sent, 7 received
> > 0 Bytes sent, 1028 received
> >
> >
> >
> >> If can tell us a little more about exactly what you need to do,
> >> perhaps I
> >> can figure out some other alternatives.
> >
> > I've two WAN circuits that I'd like to be able to interconnect with
> > eachother in a location for a few weeks, one is delivered as frame
> > relay
> > NNI bundle and the other is a VLAN bundle over Gigabit Ethernet,
> > neither
> > circuit can be changed such that they are the same technology and the
> > goal is to be able to use the bridged link to carry IP traffic on
> > behalf
> > of a service requiring a full IPv4 routing table (hence VRF out of the
> > question).
> >
> > Many thanks,
> >
> > Dave.
> >
> >
> > - --
> > =========
> > bep
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.4 (MingW32)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> --
> Matthew S. Crocker
> Vice President
> Crocker Communications, Inc.
> Internet Division
> PO BOX 710
> Greenfield, MA 01302-0710
> http://www.crocker.com
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list