Create service flow for Cable Modem Management | docsis.org

You are here

Create service flow for Cable Modem Management

6 posts / 0 new
Last post
faissaal
Create service flow for Cable Modem Management

Hello All,

We want to create a service flow for Cable Modem management where all cable modem management traffic goes through this service flow and does not affect data traffic.

We have added a new service flow but when pinging the modem management IP from a remote management server to the CM it does not seems to be going through this management service flow.

CMTS-Test-Lab-uBR10k-01#scm 10.44.80.10 qos
Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate Throughput
State Type
139 US act 42 BE 0 1024000 512000 0 1659
6614 US act 3077 BE 6 65536 3044 0 0
6615 US act 3078 BE 5 300000 512000 0 0
140 DS act N/A N/A 0 11264000 512000 0 306
6616 DS act N/A N/A 6 65536 3044 0 0
6617 DS act N/A N/A 5 300000 512000 0 0

CMTS-Test-Lab-uBR10k-01#

Downstream Service Flow Encodings

Service Flow Reference:7
Service Class Name:DS_CM_MGT
Quality of Service Parameter Set:provisioned admitted active
Traffic Priority:5
Downstream Maximum Sustained Traffic Rate:300000
Maximum Traffic Burst:512000

1 classifier(s) present:

Downstream Packet Classification Encoding
Classifier Reference:6
Service Flow Reference:7
Rule Priority:255
Classifier Activation State:on
IP Packet Classification Encodings
IP Source Address:10.0.0.0
IP Source Mask:255.0.0.0
IP Destination Address:10.44.0.0
IP Destination Mask:255.255.0.0

Upstream Service Flow Encodings

Service Flow Reference:5
Service Class Name:US_CM_MGT
Quality of Service Parameter Set:provisioned admitted active
Traffic Priority:5
Upstream Maximum Sustained Traffic Rate:300000
Maximum Traffic Burst:512000

1 classifier(s) present:

Upstream Packet Classification Encoding
Classifier Reference:3
Service Flow Reference:5
Rule Priority:255
Classifier Activation State:on
IP Packet Classification Encodings
IP Source Address:10.44.0.0
IP Source Mask:255.255.0.0
IP Destination Address:10.0.0.0
IP Destination Mask:255.0.0.0

mbowe
What is the IP of the remote

What is the IP of the remote management server?

faissaal
Hello,

Hello,

Its in the range 10.x.x.x

kwesibrunee
one thing that seems to be

one thing that seems to be missing is traffic type called IpProto by sourceforge docsis

don't recognize your config format but you need a ipproto statement
1 = tcp
7 = udp
257= all protocols

in sourceforge docsis it looks like this

DsPacketClass
{
ClassifierRef 6;
ServiceFlowRef 7;
RulePriority 255;
ActivationState 1;
IpPacketClassifier
{
IpProto 257;
IpSrcAddr 10.0.0.0;
IpSrcMask 255.0.0.0;
IpDstAddr 10.44.0.0;
IpDstMask 255.255.0.0;
}
}

UsPacketClass
{
ClassifierRef 3;
ServiceFlowRef 5;
ActivationState 1;
IpPacketClassifier
{
IpProto 257;
IpSrcAddr 10.44.0.0;
IpSrcMask 255.255.0.0;
IpDstAddr 10.0.0.0;
IpDstMask 255.0.0.0;
}
RulePriority 255;
}

darkng
service flow for snmp

Hello @AllUsers,

I hope anyone can help me in the same case like this thread.
I'm trying to setup one service flow for SNMP request that are comming to the modem and to the server.
But somehow everything is going agian through the first service flow.
Please can somebody help me what i'm doing wrong
Server ip 172.22.0.0/24
Modem CM 172.22.8.0/24
CPE : 172.22.10.0/24

Main
{
NetworkAccess 1;
MaxCPE 6;
GlobalPrivacyEnable 1;

DsServiceFlow
{
DsServiceFlowRef 1;
QosParamSetType 7;
TrafficPriority 1;
MaxRateSustained 10240000;
}

UsServiceFlow
{
UsServiceFlowRef 2;
QosParamSetType 7;
TrafficPriority 1;
MaxRateSustained 1024000;
MaxTrafficBurst 3044;
SchedulingType 2;
}

DsServiceFlow
{
DsServiceFlowRef 3;
QosParamSetType 7;
TrafficPriority 7;
MaxRateSustained 10000;
MinReservedRate 1000; /*min downstream transfer rate - 10 kb/s */
}

UsServiceFlow
{
UsServiceFlowRef 4;
QosParamSetType 7;
TrafficPriority 7;
MaxRateSustained 1024000;
MinReservedRate 1000; /*min upstream */
SchedulingType 2;
}

DsPacketClass
{
ClassifierRef 5;
ServiceFlowRef 3;
RulePriority 255;
ActivationState 1;
IpPacketClassifier
{
IpProto 257;
IpSrcAddr 172.22.0.0;
IpSrcMask 255.255.255.0;
IpDstAddr 172.22.8.0;
IpDstMask 255.255.255.0;
}
}

UsPacketClass
{
ServiceFlowRef 4;
ClassifierRef 6;
RulePriority 255;
ActivationState 1;
IpPacketClassifier
{
IpProto 257;
IpSrcAddr 172.22.8.0;
IpSrcMask 255.255.255.0;
IpDstAddr 172.22.0.0;
IpDstMask 255.255.255.0;
}
}

SnmpMibObject docsDevNmAccessIp.1 IPAddress 0.0.0.0 ;
SnmpMibObject docsDevNmAccessIpMask.1 IPAddress 0.0.0.0 ;
SnmpMibObject docsDevNmAccessCommunity.1 String "public" ;
SnmpMibObject docsDevNmAccessControl.1 Integer 3; /* readWrite */
SnmpMibObject docsDevNmAccessInterfaces.1 HexString 0xc0 ;
SnmpMibObject docsDevNmAccessStatus.1 Integer 4; /* createAndGo */
}

clefranc
service flow for snmp

Hi darkng,
Don't know if you found a solution for your packet classifiers, because yours seems find to me, except your server mask (see below).

Here's a more defined ones:

DsPacketClass
{
ClassifierRef 5;
ServiceFlowRef 3;
RulePriority 255;
ActivationState 1;
IpPacketClassifier
{
IpProto 17; /* UDP */
IpSrcAddr 172.22.0.0;
IpSrcMask 255.255.0.0; /* SERVER MASK??? */
IpDstAddr 172.22.8.0;
IpDstMask 255.255.255.0;
SrcPortStart 0;
SrcPortEnd 65535;
DstPortStart 161; /* SNMP */
DstPortEnd 161; /* SNMP */
}
}

UsPacketClass
{
ServiceFlowRef 4;
ClassifierRef 6;
RulePriority 255;
ActivationState 1;
IpPacketClassifier
{
IpProto 17; /* UDP */
IpSrcAddr 172.22.8.0;
IpSrcMask 255.255.255.0;
IpDstAddr 172.22.0.0;
IpDstMask 255.255.0.0; /* SERVER MASK??? */
SrcPortStart 161; /* SNMP */
SrcPortEnd 161; /* SNMP */
DstPortStart 0;
DstPortEnd 65535;
}
}

Also, you should use TLV 53 (SNMPv1v2cCoexistenceConfig) instead of docsDevNmAccess:

This object specifies the SNMPv1v2c Coexistence Access Control configuration of the CM. This object does not preclude using TLV-11 to configure directly SNMPv3 tables. The CM MUST support a minimum of 10 SNMPv1v2c Coexistence TLVs. This TLV creates entries in SNMPv3 tables as specified in [DOCSIS OSSIv3.0].

The CM MUST reject the config file if sub-TLV SNMPv1v2c Community Name and SNMPv1v2c Transport Address Access are not present. The CM MUST support multiple instances of sub-TLV 53.2 SNMPv1v2c Transport Address Access. The CM MUST reject a config file if a TLV includes repeated sub-TLVs other than sub-TLV 53.2. The CM MUST reject the config file if a CM created entry in a SNMP table is rejected for syntax conflicts or reaches the limit in the number of entries the CM support for that table or the mapped SNMPv3 entry already exist.

Note: The number of entries a CM can support in SNMPv3 tables is independent of the number of TLVs the CM must support to be processed as SNMP tables entries.