[c-nsp] Bridging Ethernet VLANs over T1

Mon Jun 2 08:27:22 EDT 2008

I haven't used it either, but vlan-bridge is designed to bridge non-IP
traffic between VLANs on Catalyst switches.  Theoretically, you are supposed
to be able to bridge all VLANs together for non-IP traffic.  For example,
say you have a "legacy" network with Appletalk or IPX on it that you are
upgrading to Cisco Catalyst hardware.  You don't have "Enterprise" software
for edge switches, say 3750 stacks, but yet want/need to do Layer-3 to the
edge and still support IPX.  You can use vlan-bridge to bride together all
the VLANs for non-IP traffic.  At least that is my understanding.  I've
never met anyone that actually implemented it.

Fred Reimer, CISSP, CCNP, CQS-VPN, CQS-ISS
Senior Network Engineer
Coleman Technologies, Inc.
954-298-1697

> -----Original Message-----
> From: Ziv Leyes [mailto:zivl at gilat.net]
> Sent: Monday, June 02, 2008 3:30 AM
> To: Fred Reimer; Joe Freeman
> Cc: cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] Bridging Ethernet VLANs over T1
> 
> What about using "bridge 1 protocol vlan-bridge"
> 
> Just a wild guess, never used it...
> 
> Ziv
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Fred Reimer
> Sent: Friday, May 30, 2008 9:27 PM
> To: Joe Freeman
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Bridging Ethernet VLANs over T1
> 
> If it were me I'd use L2TPv3 xconnects.
> 
> 
> 
> 
> 
> Fred Reimer, CISSP, CCNP, CQS-VPN, CQS-ISS
> 
> Senior Network Engineer
> 
> Coleman Technologies, Inc.
> 
> 954-298-1697
> 
> 
> 
> From: Joe Freeman [mailto:joe at netbyjoe.com]
> Sent: Friday, May 30, 2008 2:24 PM
> To: Fred Reimer
> Cc: giesen at snickers.org; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Bridging Ethernet VLANs over T1
> 
> 
> 
> If it were me, I'd look at using frame encaps on the T1, then use a
> seperate dlci for each vlan.
> 
> On Fri, May 30, 2008 at 12:45 PM, Fred Reimer <freimer at ctiusa.com>
> wrote:
> 
> By using the same bridge group number for both VLANs would you not be
> merging the two VLANs into one bridge group?  That's not what you want,
> is it?  You may want to use a separate bridge group number for the two
> VLANs, like the example in the document you quoted.
> 
> bridge 1 protocol ieee
> bridge 2 protocol ieee
> !
> interface ethernet 0
>  vlan-range dot1q 1 600
>  bridge-group 1
>  vlan-range dot1q 800 4000
>  bridge-group 2
> !
> interface serial 0
>  encapsulation ppp
>  bridge-group 1
> !
> interface serial 1
>  encapsulation ppp
>  bridge-group 2
> 
> Two bridge groups, two serial interfaces, for two separate VLANs.
> 
> Fred Reimer, CISSP, CCNP, CQS-VPN, CQS-ISS Senior Network Engineer
> Coleman Technologies, Inc.
> 954-298-1697
> 
> 
> 
> > -----Original Message-----
> > From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> > bounces at puck.nether.net] On Behalf Of Gary T. Giesen
> > Sent: Friday, May 30, 2008 12:11 PM
> > To: cisco-nsp at puck.nether.net
> > Subject: Re: [c-nsp] Bridging Ethernet VLANs over T1
> >
> > Jay,
> >
> > Thanks for the reply. Unfortunately that doesn't seem to work, I
> > assume because there's no way to specify which VLAN that IP actually
> > resides on. Normally bridge-groups/BVI's are only used to bridge one
> > VLAN, but in this case it's bridging multiple VLANs.
> >
> > GG
> >
> > On Fri, May 30, 2008 at 12:05 PM, Jay Hennigan <jay at west.net> wrote:
> > > Gary T. Giesen wrote:
> > >>
> > >> Hi all,
> > >>
> > >> I have an application that requires us to bridge Ethernet VLANs
> > >> over
> > a
> > >> T1. I've previously done this using Nortel/Tasman boxes, and have
> > got
> > >> it working with a Cisco 1841 w/T1 WIC (per
> > >>
> > >>
> >
> http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gt_bcp.
> > h
> > tml),
> > >> but I'm having one issue. The Tasman/Nortel boxes allow me to
> > >> inject an IP address into one of the VLANs for management
> purposes,
> > >> whereas
> > I
> > >> can't for the life of me figure out how to do it in Cisco-land.
> > >>
> > >> Cisco config snippet:
> > >>
> > >> bridge 1 protocol ieee
> > >>
> > >> interface FastEthernet0/0
> > >>  no ip address
> > >>  duplex auto
> > >>  speed auto
> > >>  vlan-id dot1q 10
> > >>  description Data VLAN
> > >>  bridge-group 1
> > >>  exit-vlan-config
> > >>  !
> > >>  vlan-id dot1q 20
> > >>  description Management VLAN
> > >>  bridge-group 1
> > >>  exit-vlan-config
> > >>  !
> > >> !
> > >>
> > >> interface Serial0/1/0
> > >>  no ip address
> > >>  encapsulation ppp
> > >>  service-module t1 clock source internal  bridge-group 1
> > >
> > > bridge irb
> > >
> > > bridge 1 proto ieee
> > > bridge 1 route ip
> > >
> > > int bvi1
> > >  ip address 10.10.10.11 255.255.255.0
> > >
> > >
> > >
> > > --
> > > Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
> > > Impulse Internet Service  -  http://www.impulse.net/ Your local
> > > telephone and internet company - 805 884-6323 - WB6RDV
> > >
> > >
> > _______________________________________________
> > 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/
> 
> 
> _______________________________________________
> 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/
> 
> 
> 
> 
> 
> 
> 
> 
> ***********************************************************************
> *************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals &
> computer viruses.
> ***********************************************************************
> *************
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3080 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20080602/a174cfd6/attachment-0001.bin>