[alcatel-nsp] configuring SAP on STM/OC3 interface
andhy.indarto at indosat.com
Thu Sep 30 21:07:48 EDT 2010
First of all, you should use the MDA that support VPRN services, MDA CES
can not support L3 VPN services.
The config is like this for STM-1 SDH technology :
A:CORE# configure port 3/2/1
framing sdh -> encap the port with sdh and
group tug3-1 payload vt2 -> channelised with E1/VC-12
e1 1.1.1 -> create subinterface with KLM
timeslots 2-17 -> remember ALU SR start with ts
A:CORE>config# service vprn 184
interface "to-test" create
sap 3/2/22.214.171.124.1 create
I encapsulated the sub interface channel-group 1 with cisco-hdlc because
the customer is using cisco router.
Hope this help.
From: alcatel-nsp-bounces at puck.nether.net
[mailto:alcatel-nsp-bounces at puck.nether.net] On Behalf Of Iyke Ben
Sent: Friday, October 01, 2010 4:46 AM
To: alcatel-nsp at puck.nether.net
Subject: [alcatel-nsp] configuring SAP on STM/OC3 interface
What is the correct encapsulation when configuring SAP on an OC3/Stm1
interface inside VPRN. I attempted creating a SAP in my VPRN logical
interface but get the SAP-Id and encapsulation error .
alcatel-nsp mailing list
alcatel-nsp at puck.nether.net
"This message is intended only for recipients who are authorized to receive it.
It contains confidential and/ or legally priveleged information belong to PT INDOSAT Tbk ("INDOSAT"), therefore the authorized recipients shall protect this confidential information disclosed pursuant to provisions of Indosat's policy.
If you are not a valid recipient of this message, please delete it from your system and/ or destroy all of the tangible material produced from the information herein together with all copies or reproductions thereof and notify the sender immediately.
Please also be notified that any disclosure, copying, distribution or taking any action based on the contents of this message is strictly prohibited and may be unlawful".
More information about the alcatel-nsp