L2VPN on Cisco EPC3940

8 posts / 0 new

Fri, 10/10/2014 - 04:01

ggonzalez

Hi,

We have a CASA CMTS and a CISCO EPC3940 and we would like to setup a few VLANs using L2VPN but we have struggled so far.

To our working CM config files we have added the configurations found in this forum:

UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
GenericTLV TlvCode 43 TlvLength 14 TlvValue 0x0803ffffff050701050234560001;
}
DsServiceFlow
{
DsServiceFlowRef 2;
QosParamSetType 7;
}
VendorSpecific
{
VendorIdentifier 0xffffff;
GenericTLV TlvCode 5 TlvLength 13 TlvValue 0x01050234560001020402020003;
/* 01050234560001 is network number and the trailing 003 is the VLAN number (in hex I presume)*/
}

But the modems doesn't like this new parameters and it resets itself after retrieving it.

Could anyone please point to any documentation where we could get information / examples / etc for the specific hex values found in this piece of config file.

We are pretty lost at the meantime, any help be really useful.

Cheers

Sat, 10/18/2014 - 19:01

mbowe

This is a tricky topic, but

This is a tricky topic, but it isn't too hard once you have a working example

-------------

First step is to create the VPN, which is your section :

VendorSpecific
{
VendorIdentifier 0xffffff;
GenericTLV TlvCode 5 TlvLength 13 TlvValue 0x01050234560001020402020003;
}

Your example is saying :

VendorSpecific
{
VendorIdentifier 0xffffff;
L2VPNEncoding
{
VPNId 0234560001;
NSIEncapsulation
{
802.1Q 3;
}
}
}

Notes :

VendorSpecific = TLV 43

L2VPNEncoding = TLV 43.5

01050234560001 defines the VPN name. (TLV 43.5, subtype 1, length 5, value 0234560001)
This is OK, but it would probably be more typical to use an ASCII string for the VPNId eg
01084d794c3256504e31 (subtype 1, length 8, value "MyL2VPN1")

020402020003 defines the Dot1Q VLAN number (TLV 43.5, subtype 2, length 4, code 2, code length 2, value 3)

-------------

Second step is to associate upstream flows with the VPN, which is your section :

UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
GenericTLV TlvCode 43 TlvLength 14 TlvValue 0x0803ffffff050701050234560001;
}

Your example is saying :

UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
VendorSpecific
{
VendorIdentifier 0xffffff;
L2VPNEncoding
{
VPNId 01050234560001; /* WRONG! */
}
}
}

This is wrong, you can see the VPNId does not match (you cut-pasted type SubType/Length/Value rather than just the value).

It should be :

GenericTLV TlvCode 43 TlvLength 14 TlvValue 0x0803ffffff05050234560001;

Which would translate to :

UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
VendorSpecific
{
VendorIdentifier 0xffffff;
L2VPNEncoding
{
VPNId 0234560001;
}
}
}

Or if you want to use the ASCII string style it would be

GenericTLV TlvCode 43 TlvLength 14 TlvValue 0x0803ffffff05084d794c3256504e31

Which would translate to :

UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
VendorSpecific
{
VendorIdentifier 0xffffff;
L2VPNEncoding
{
VPNId "MyL2VPN1";
}
}
}

-------------

Hope that helps!

Wed, 10/22/2014 - 09:05

(Reply to #2) #3

Nazario

Hi mbowe!

Hi mbowe!
Thanks for your answer.
Do you know how could I insert the L2VPNEncoding inside the VendorIdentifier?
Now I am using the software excentis, however when I press in EuroDocsisVendorSpecific, and press Add, It does not give me the option to add L2VPNEncoding.
It only appears the same options than when I press add in UpStreamServiceFlow Encodings (where I can add EuroDocsisVendorSpecific).
See image attached.
Thanks and Best Regards.

File attachments:

vlan.jpg

Thu, 10/23/2014 - 19:29

(Reply to #3) #4

mbowe

I haven't used excentis

I haven't used excentis before. I see it is free, I might have to give it a try!

One trick I have used in the past when I couldn't work out how to create a complex stanza in a particular docsis editor is to create the file by hand (using the GenericTLV type entries if needed), then compile it (I use the linux docsis editor http://docsis.sourceforge.net), then open the compiled file in the other editor of your choice and look at how the fields are set out.

Unfortunately some editors don't have support for some of this complex stuff like L2VPN.

I actually modified the source of the linux docsis editor so I could work with these complex L2VPN fields.

Fri, 10/24/2014 - 02:57

(Reply to #4) #5

Nazario

cheat

Thanks mbowe,
Excentis have the cheat option, and if you select it, you can modify the config file.
I added the generic tlv 43 there.
Which program do you usually use to config?
Thanks!

Sat, 10/25/2014 - 00:18

(Reply to #5) #6

mbowe

Excentis

Hi, I downloaded this and it looks pretty decent.

Here is the example in Excentis format

Network Access Control:on

Maximum Number of CPEs:254

Privacy Enable:on

Euro-DOCSIS Extension Field
  L2VPN Encoding
    VPN Identifier:0234560001
    NSI Encapsulation Subtype
      Service Multiplexing Value IEEE 802.1Q:0003

Downstream Service Flow Encodings
  Service Flow Reference:1
  Service Class Name:4M-DS-BE
  Quality of Service Parameter Set:provisioned admitted active
  Traffic Priority:3

Upstream Service Flow Encodings
  Service Flow Reference:2
  Service Class Name:4M-US-BE
  Quality of Service Parameter Set:provisioned admitted active
  Traffic Priority:3
  Euro-DOCSIS QoS Extension Field
    L2VPN Encoding
      VPN Identifier:0234560001

Downstream Unencrypted Traffic Filtering
DUT Control:on

---

I use the docsis.sourceforge.net compiler mainly, because it is Linux based as is my DHCP/TFTP and provisioning servers. Thus makes it easier to script the compile of cm and mta config files. I sometimes use Arris PacketAce if I want to have a gui. Although this Excentis software doesn't look too bad also.

Wed, 10/29/2014 - 06:32

(Reply to #6) #7

Nazario

3 Vlans

First, really, thanks for your help,

Second, the thing is that we are trying to have 3 vlans (382,450,500) with a range of ip (10.63.254.0, 10.63.253.0 and 192.168.0.0).
We modified our config file as you said, however our CM does not accept this config. Here is it:

------------------------------------------------------
Network Access Control:on
Maximum Number of CPEs:5
Privacy Enable:on

Upstream Service Flow Encodings
Service Flow Reference:1
Quality of Service Parameter Set:provisioned admitted active
Traffic Priority:4
Service Flow Scheduling Type:Best Effort
Euro-DOCSIS QoS Extension Field
L2VPN Encoding
VPN Identifier:01020304
Upstream Service Flow Encodings
Service Flow Reference:2
Quality of Service Parameter Set:provisioned admitted active
Traffic Priority:4
Service Flow Scheduling Type:Best Effort
Euro-DOCSIS QoS Extension Field
L2VPN Encoding
VPN Identifier:01020305
Upstream Service Flow Encodings
Service Flow Reference:3
Quality of Service Parameter Set:provisioned admitted active
Traffic Priority:4
Service Flow Scheduling Type:Best Effort
Euro-DOCSIS QoS Extension Field
L2VPN Encoding
VPN Identifier:01020306

Downstream Service Flow Encodings
Service Flow Reference:4
Quality of Service Parameter Set:provisioned admitted active
Traffic Priority:4
Downstream Service Flow Encodings
Service Flow Reference:5
Quality of Service Parameter Set:provisioned admitted active
Traffic Priority:4
Downstream Service Flow Encodings
Service Flow Reference:6
Quality of Service Parameter Set:provisioned admitted active
Traffic Priority:4

Upstream Packet Classification Encoding
Classifier Reference:3
Service Flow Reference:1
Classifier Activation State:on
IP Packet Classification Encodings
IP Source Address:10.63.254.0
IP Source Mask:255.255.255.0
Upstream Packet Classification Encoding
Classifier Reference:2
Service Flow Reference:2
Classifier Activation State:on
IP Packet Classification Encodings
IP Source Address:10.63.253.0
IP Source Mask:255.255.255.0
Upstream Packet Classification Encoding
Classifier Reference:1
Service Flow Reference:3
Classifier Activation State:on
IP Packet Classification Encodings
IP Source Address:192.168.0.0
IP Source Mask:255.255.255.0

Euro-DOCSIS Extension Field
L2VPN Encoding
VPN Identifier:01020304
NSI Encapsulation Subtype
Service Multiplexing Value IEEE 802.1Q:017E
Euro-DOCSIS Extension Field
L2VPN Encoding
VPN Identifier:01020305
NSI Encapsulation Subtype
Service Multiplexing Value IEEE 802.1Q:01C2
Euro-DOCSIS Extension Field
L2VPN Encoding
VPN Identifier:01020306
NSI Encapsulation Subtype
Service Multiplexing Value IEEE 802.1Q:01F4
--------------------------------------------------------------------------------------------
What do you thing about it? Thanks

Wed, 10/29/2014 - 10:46

(Reply to #7) #8

Nazario

3 vlans

Hi Mbowe!
First, thanks for your answer!
We are trying to create 3 vlans, (382,450 and 500) with ips (10.63.254.0, 10.63.253.0 and 192.168.0.0), however when I tried to create the config as yours, it does not work. My Config is this:
-------------------------------------------------------

Network Access Control:on
Maximum Number of CPEs:5
Privacy Enable:on

--------------------------------------------
What do you think about it?
Thanks

Main menu

Navigation

You are here

L2VPN on Cisco EPC3940

Main menu

Navigation

User login

You are here

L2VPN on Cisco EPC3940