[c-nsp] G.SHDSL Bonding

Charles J. Boening charlieb at cot.net
Thu Jan 25 18:29:40 EST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Per,

Thanks for the suggestions.  Unfortunately, getting the Telco side of
the house to upgrade an antiquated (IMHO) DSLAM is easier said than
done.  The DSLAM this customer is off is part of a five node ring so
upgrading is just more than on DSLAM.

Thanks,
Charlie


 

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Per Carlson
> Sent: Thursday, January 25, 2007 10:07 AM
> To: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] G.SHDSL Bonding
> 
> On Wed, Jan 24, 2007 at 08:55:45AM -0800, Charles J. Boening wrote:
> 
> > I'm wondering if I could put in a 2600 router at the customer site 
> > with two G.SHDSL WIC cards and somehow (PPP multilink?) bond two 
> > G.SHDSL circuits together?  I'm guessing that I'd want a "static" 
> > vpi/vci in this situation.
> 
> If your DSLAM supports 4-wire mode, you can use a v2 or v3 
> G.SHDSL WIC.
> This way the DSL chips will automagically bond the 2 pairs 
> together and create a single physical ATM-interface.
> 
> <comment>
> If not, you should probably start looking around for a new 
> DSLAM. +2-wire G.SHDSL have been around for a long time now.
> </comment>
> 
> --
> Per Carlson, Sr. Network Developer
> _______________________________________________
> 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/
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFFuPuDcGGHuFdGSWARAkZnAKCIIVqWzMXCTYRiNIqHJTskWyA07gCeOzbW
iTEQabbpbqAqTr8s3DZatr4=
=kXR0
-----END PGP SIGNATURE-----



More information about the cisco-nsp mailing list