Have a look at TR-101 & TR-144 from broadband forum (ex dsl forum).
http://www.broadband-forum.org/technical/trlist.php
Also, Cisco provides some design guides; you just have to ask your account
manager.
--
Tassos
sheaujiun wrote on 26/11/2008 01:48:
Yes, it seems subjective but is there possibly a general idea that can be
provided? For now, I do not have give a detail plan, just introduce a
general concept.
On Wed, Nov 26, 2008 at 2:56 AM, raymondh (NSP) <[EMAIL PROTECTED]>wrote:
It's very subjective to one's environment.
On Nov 25, 2008, at 10:53 PM, sheaujiun wrote:
Hi,
I have a customer in a DSLAM/BRAS environment where they have 4 main
groups
of Vlans assignments - Data, Voice, Management and Other services.
Currently there is not fixed rules as to how vlan ids are assigned to the
4
main groups. It has come to a time the network has grown to a rather huge
size and they are trying to reassign the vlan assignments.
Generally, the network is as such:
DSLAM --> aggregation switch --> BRAS
Is there a standard guideline as to how vlan assignments are to be
designed?
What considerates are needed?
e.g. Is there a need to consider how different vlans are to be terminated
into the the aggregation switch if they are running VPLS?
How the BRAS will handle the vlans coming from the aggregation?
Sheau Jiun
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
