Picon
Favicon

subscriber mib version-06


docsSubMgtPktFilterEntry is indexed by docsSubMgtPktFilterGroup & docsSubMgtPktFilterIndex. Is the
filter index unique to a filter group or entire system? If there are 2 filter groups X & Y using filter index
A, does this mean that they are referencing the same filter?

Also, does DOCSIS define the maximum number of filters that should be supported on the system?

Thanks,
Shrini
Picon
Favicon

subscriber mib version-06 -clarification on DoscSubMgtPktFilterEn try

Hi,
DoscSubMgtPktFilterEntry has several fields as follows.

DocsSubMgtPktFilterEntry ::= SEQUENCE
       {
       docsSubMgtPktFilterGroup        Integer32,
       docsSubMgtPktFilterIndex        Integer32,
       docsSubMgtPktFilterSrcAddrType  InetAddressType,
       docsSubMgtPktFilterSrcAddr      InetAddress,
       docsSubMgtPktFilterSrcMaskType  InetAddressType,
       docsSubMgtPktFilterSrcMask      InetAddress,
       docsSubMgtPktFilterDstAddrType  InetAddressType,
       docsSubMgtPktFilterDstAddr      InetAddress,
       docsSubMgtPktFilterDstMaskType  InetAddressType,
       docsSubMgtPktFilterDstMask      InetAddress,
       docsSubMgtPktFilterUlp          Integer32,
       docsSubMgtPktFilterTosValue     OCTET STRING,
       docsSubMgtPktFilterTosMask      OCTET STRING,
       docsSubMgtPktFilterAction       INTEGER,
       docsSubMgtPktFilterMatches      Counter32,
       docsSubMgtPktFilterStatus       RowStatus
}

When a new filter entry is created and if all the fields are not specified, should these unspecified fields
be set to default values or be treated as unused fields (Don't care) in the filter.

Thanks,
Shrini
--------------------------------------------
Shrinivas Samant
(Continue reading)

Wilson.Sawyer | 17 Sep 2002 22:51
Favicon

Re: subscriber mib version-06


docsSubMgtPktFilterIndex is qualified by the group - so, no, no
relationship is implied between {group1,A} and {group2,A}.

Check your OSSI spec for minimum # of filters supported - last time I
checked it was 30 groups of twenty.

Regards,
Wilson Sawyer
ARRIS

                                                                                                                          
                      "Samant,                                                                                            
                      Shrinivas                To:       "'ipcdn <at> ietf.org'" <ipcdn <at> ietf.org>                              
                      (Shrinivas)"             cc:                                                                        
                      <ssamant <at> lucent.c        Fax to:                                                                    
                      om>                      Subject:  [ipcdn] subscriber mib version-06                                
                      Sent by:                                                                                            
                      ipcdn-admin <at> ietf.                                                                                   
                      org                                                                                                 

                                                                                                                          
                      09/17/02 03:32 PM                                                                                   

docsSubMgtPktFilterEntry is indexed by docsSubMgtPktFilterGroup &
docsSubMgtPktFilterIndex. Is the filter index unique to a filter group or
entire system? If there are 2 filter groups X & Y using filter index A,
does this mean that they are referencing the same filter?

Also, does DOCSIS define the maximum number of filters that should be
(Continue reading)

Wilson.Sawyer | 17 Sep 2002 22:56
Favicon

Re: subscriber mib version-06 -clarification on DoscSubMgtPktFilterEn try


use the DEFVALs

- Wilson Sawyer, ARRIS

                                                                                                                          
                      "Samant,                                                                                            
                      Shrinivas                To:       "'ipcdn <at> ietf.org'" <ipcdn <at> ietf.org>                              
                      (Shrinivas)"             cc:                                                                        
                      <ssamant <at> lucent.c        Fax to:                                                                    
                      om>                      Subject:  [ipcdn] subscriber mib version-06 -clarification on              
                      Sent by:                  DoscSubMgtPktFilterEn try                                                 
                      ipcdn-admin <at> ietf.                                                                                   
                      org                                                                                                 

                                                                                                                          
                      09/17/02 04:41 PM                                                                                   

Hi,
DoscSubMgtPktFilterEntry has several fields as follows.

DocsSubMgtPktFilterEntry ::= SEQUENCE
       {
       docsSubMgtPktFilterGroup        Integer32,
       docsSubMgtPktFilterIndex        Integer32,
       docsSubMgtPktFilterSrcAddrType  InetAddressType,
       docsSubMgtPktFilterSrcAddr      InetAddress,
       docsSubMgtPktFilterSrcMaskType  InetAddressType,
       docsSubMgtPktFilterSrcMask      InetAddress,
       docsSubMgtPktFilterDstAddrType  InetAddressType,
(Continue reading)

Woundy, Richard | 19 Sep 2002 18:28
Picon

SMICng and our IPCDN MIBs

Folks,

The good news is that I finally have SMICng operational in my work
environment.

The bad news is that I tried it out on many of the MIBs written for our
working group, and found a number of issues that need to be resolved.

A simple example is the Subscriber Management MIB,
<http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscriber-mib-06.txt>
, which passed working group last-call. SMICng caught the fact that the date
strings in the module-identity are not in the post-2000 "extended UTCTime
format" of RFC 2578. Fortunately, that was the only error that SMICng
discovered (so this minor fix can wait until after the MIB doctor review).

More complicated are the errors caught by SMICng for the recent PacketCable
MIBs. I'll send the specific errors in separate emails. Here are some common
problems:
- Not using the extended UTCTime format for the LAST-UPDATED and REVISION
clauses in MODULE-IDENTITY, just like above
- Double quotes converted to stylized quotes in the ASCII version, e.g. ææ
and ÆÆ
- Incorrect IMPORT clauses

-- Rich

P.S. Here's a fix for the Subscriber Management MIB date typos:

   docsSubMgt MODULE-IDENTITY
           LAST-UPDATED    "200202280000Z" -- February 28, 2002
(Continue reading)

Woundy, Richard | 19 Sep 2002 19:47
Picon

SMICng and the PacketCable MTA MIB

Folks,

I ran SMICng against the PacketCable MTA MIB,
<http://www.ietf.org/internet-drafts/draft-osman-pktc-ipcdn-mtamib-00.txt>.

Prior to compiling, I had to change the ææ and ÆÆ into double quotes, and
had to fix the LAST-UPDATED time in the MODULE-IDENTITY object. I have
attached the edited version of the MIB, so you can match the (line number,
column number) references in the SMICng error output.

Below are the errors that SMICng found in the edited version. Also note that
the MIB doctors strongly discourage the use of "IpAddress" and
"DisplayString" (use "InetAddressType" + "InetAddress" and "SnmpAdminString"
instead, respectively).

E: f(PKTC-MTA-MIB.mi2), (14,14) Item "OBJECT-GROUP" not defined in module
"INET-ADDRESS-MIB"
E: f(PKTC-MTA-MIB.mi2), (15,14) Item "MODULE-COMPLIANCE" not defined in
module "INET-ADDRESS-MIB"
W: f(PKTC-MTA-MIB.mi2), (61,41) REVISION value "0206240000Z" is not a valid
extended UTC time
W: f(PKTC-MTA-MIB.mi2), (684,18) Name of item
"PktcMtaDevServProviderCertificate" must start with lowercase letter
Item name changed to "pktcMtaDevServProviderCertificate"
W: f(PKTC-MTA-MIB.mi2), (685,18) Name of item
"PktcMtaDevTelephonyCertificate" must start with lowercase letter
Item name changed to "pktcMtaDevTelephonyCertificate"
W: f(PKTC-MTA-MIB.mi2), (686,18) Name of item "PktcMtaDevKerberosRealm" must
start with lowercase letter
Item name changed to "pktcMtaDevKerberosRealm"
(Continue reading)

Woundy, Richard | 19 Sep 2002 20:21
Picon

SMICng and the PacketCable/IPCablecom MIB Framework

Folks,

I ran SMICng against the PacketCable/IPCablecom MIB Framework,
<http://www.ietf.org/internet-drafts/draft-channabasappa-pktc-ipcdn-mib-fram
ework-00.txt>.

Before discussing the SMICng errors, we MUST fix the OID assignment in this
MIB. The object "cableLabs" is assigned the OID { mib-2 70 }. This is the
same OID as the root of the Ethernet Chip Set MIB, RFC 2666
<http://www.ietf.org/rfc/rfc2666.txt>. Prior to IETF publication, I would
recommend using rooting at an OID under the CableLabs enterprise OID {
enterprises 4491 } -- just like
<http://www.packetcable.com/downloads/specs/PKT-SP-MIBS-I03-020116.pdf>. For
IETF publication, IANA will assign an OID <http://www.iana.org/>.

Prior to compiling, I had to fix the LAST-UPDATED time in the
MODULE-IDENTITY object. I have attached the edited version of the MIB, so
you can match the (line number, column number) references in the SMICng
error output.

Below are the errors that SMICng found in the edited version. The first and
third errors are IMPORT issues that would be fixed by following my
recommended fixes for the OID root; the second error is a typo in the OID
for "clabprojCableHome".

E: f(CLAB-DEF-MIB.mi2), (35,20) Leading sub-Id "mib-2" is not known in
current module
E: f(CLAB-DEF-MIB.mi2), (44,57) Leading sub-Id "calbProject" is not known in
current module
W: f(CLAB-DEF-MIB.mi2), (5,15) "enterprises" imported but not used
(Continue reading)

Woundy, Richard | 19 Sep 2002 20:49
Picon

SMICng and the PacketCable/IPCablecom Management Event MIB

Folks,

I ran SMICng against the PacketCable/IPCablecom Management Event MIB,
<http://www.ietf.org/internet-drafts/draft-deketelaere-pktc-ipcdn-eventmess-
00.txt>.

Prior to compiling, I had to change the ææ and ÆÆ into double quotes, and
had to fix the LAST-UPDATED time in the MODULE-IDENTITY object. I have
attached the edited version of the MIB, so you can match the (line number,
column number) references in the SMICng error output.

Below are the errors that SMICng found in the edited version. Also note that
the MIB doctors strongly discourage the use of "DisplayString" (use
"SnmpAdminString"
instead).

E: f(PKTC-EVENT-MIB.mi2), (9,11) Pseudo type BITS is not valid in the
IMPORTS clause
E: f(PKTC-EVENT-MIB.mi2), (13,10) Item "OBJECT-GROUP" not defined in module
"INET-ADDRESS-MIB"
E: f(PKTC-EVENT-MIB.mi2), (14,10) Item "MODULE-COMPLIANCE" not defined in
module "INET-ADDRESS-MIB"
W: f(PKTC-EVENT-MIB.mi2), (52,34) REVISION value "0206240000Z" is not a
valid extended UTC time
E: f(PKTC-EVENT-MIB.mi2), (1,1) Construct "MODULE-COMPLIANCE" used in
PKTC-EVENT-MIB, but not defined or imported
E: f(PKTC-EVENT-MIB.mi2), (1,1) Construct "OBJECT-GROUP" used in
PKTC-EVENT-MIB, but not defined or imported
E: f(PKTC-EVENT-MIB.mi2), (709,17) Item "pktcDevEvControlState" is not known
in current module
(Continue reading)

Eugene Nechamkin | 19 Sep 2002 20:06
Favicon

RE: SMICng and the PacketCable MTA MIB

Rich,

Before submitting MTA MIB, I as able to compile it with Epilogue MIB
Compiler, no problem. I'll look into that and fix the problems.

Is "SMICng" the MIB compiler which you used ? Where can I get it ?

Eugene.

-----Original Message-----
From: Woundy, Richard [mailto:RWoundy <at> broadband.att.com]
Sent: Thursday, September 19, 2002 10:48 AM
To: IPCDN (E-mail)
Cc: PacketCable Provisioning and OSS (E-mail)
Subject: SMICng and the PacketCable MTA MIB

Folks,

I ran SMICng against the PacketCable MTA MIB,
<http://www.ietf.org/internet-drafts/draft-osman-pktc-ipcdn-mtamib-00.txt>.

Prior to compiling, I had to change the ææ and ÆÆ into double quotes, and
had to fix the LAST-UPDATED time in the MODULE-IDENTITY object. I have
attached the edited version of the MIB, so you can match the (line number,
column number) references in the SMICng error output.

Below are the errors that SMICng found in the edited version. Also note that
the MIB doctors strongly discourage the use of "IpAddress" and
"DisplayString" (use "InetAddressType" + "InetAddress" and "SnmpAdminString"
instead, respectively).
(Continue reading)

Woundy, Richard | 20 Sep 2002 00:18
Picon

SMICng and the PacketCable/IPCablecom NCS Signaling MIB

Folks,

I ran SMICng against the PacketCable/IPCablecom NCS Signaling MIB,
<http://www.ietf.org/internet-drafts/draft-schell-pktc-ipcdn-signaling-00.tx
t>.

Prior to compiling, I had to change the ææ and ÆÆ into double quotes
(throughout this MIB in particular), and had to fix the LAST-UPDATED time in
the MODULE-IDENTITY object. This MIB also had a special syntactical problem
with the binary DEFVAL's -- we have to define a binary number in the form
'11110000'B rather than just 11110000, per RFC 2578 section 11.1. These were
the original binary value syntax errors:

E: f(PKTC-SIG-MIB.mi2), (313,20) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (325,21) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (336,22) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (538,20) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (549,20) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (560,22) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (571,22) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (582,21) number too big (max is
18446744073709551615), using max value
E: f(PKTC-SIG-MIB.mi2), (594,21) number too big (max is
(Continue reading)


Gmane