Reference record for OID 1.3.6.1.4.1.9.9.786.1.2.1.1

parent

1.3.6.1.4.1.9.9.786.1.2.1 (csubAggStatsTable)

node code

1

node name

csubAggStatsEntry

dot oid

1.3.6.1.4.1.9.9.786.1.2.1.1

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoSubscriberSessionMIB(786) ciscoSubscriberSessionMIBObjects(1) csubAggStats(2) csubAggStatsTable(1) csubAggStatsEntry(1)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoSubscriberSessionMIB(786) ciscoSubscriberSessionMIBObjects(1) csubAggStats(2) csubAggStatsTable(1) csubAggStatsEntry(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoSubscriberSessionMIB(786) ciscoSubscriberSessionMIBObjects(1) csubAggStats(2) csubAggStatsTable(1) csubAggStatsEntry(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoSubscriberSessionMIB(786) ciscoSubscriberSessionMIBObjects(1) csubAggStats(2) csubAggStatsTable(1) csubAggStatsEntry(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoSubscriberSessionMIB(786) ciscoSubscriberSessionMIBObjects(1) csubAggStats(2) csubAggStatsTable(1) csubAggStatsEntry(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoSubscriberSessionMIB(786) ciscoSubscriberSessionMIBObjects(1) csubAggStats(2) csubAggStatsTable(1) csubAggStatsEntry(1)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoSubscriberSessionMIB/ciscoSubscriberSessionMIBObjects/csubAggStats/csubAggStatsTable/csubAggStatsEntry

/iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoSubscriberSessionMIB/ciscoSubscriberSessionMIBObjects/csubAggStats/csubAggStatsTable/csubAggStatsEntry

/iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoSubscriberSessionMIB/ciscoSubscriberSessionMIBObjects/csubAggStats/csubAggStatsTable/csubAggStatsEntry

/iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoSubscriberSessionMIB/ciscoSubscriberSessionMIBObjects/csubAggStats/csubAggStatsTable/csubAggStatsEntry

/iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoSubscriberSessionMIB/ciscoSubscriberSessionMIBObjects/csubAggStats/csubAggStatsTable/csubAggStatsEntry

/iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoSubscriberSessionMIB/ciscoSubscriberSessionMIBObjects/csubAggStats/csubAggStatsTable/csubAggStatsEntry

Description by cisco_v1

An entry contains a set of aggregated statistics relating to
those subscriber sessions that fall into a 'scope of
aggregation'.

A 'scope of aggregation' is the set of subscriber sessions
that meet specified criteria. For example, a 'scope of
aggregation' may be the set of all PPPoE subscriber sessions
maintained by the system. The following criteria define the
'scope of aggregation':

1) Aggregation Point type
Aggregation point type identifies the format of the
csubAggStatsPoint for this entry.

2) Aggregation Point
'Physical' Aggregation Point type case:
In a distributed system, a 'node' represents a physical
entity capable of maintaining the context representing
a subscriber session.

If the 'scope of aggregation' specifies a physical
entity having an entPhysicalClass of 'chassis', then
the set of subscriber sessions in the 'scope of
aggregation' may contain the subscriber sessions maintained by all
the nodes contained in the system.

If the 'scope of aggregation' specifies a physical
entity having an entPhysicalClass of 'module' (e.g., a
line card), then the set of subscriber sessions in the
'scope of aggregation' may contain the subscriber
sessions maintained by the nodes contained by the
module.

If the 'scope of aggregation' specifies a physical
entity having an entPhysicalClass of 'cpu', then the
set of subscriber sessions in the 'scope of aggregation'
may contain the subscriber sessions maintained by the node
running on that processor.

Observe that a centralized system (i.e., a system
that essentially contains a single node) can only
support a 'scope of aggregation' that specifies a
physical entity classified as a 'chassis'.

If the scope of aggregation specifies 'interface',
then the scope is the set of subscriber sessions carried
by the interface identified the ifIndex value
represented in the csubAggStatsPoint value.

2) Subscriber Session Type
If the 'scope of aggregation' specifies the value 'all'
for the subscriber session type, then the set of
subscriber sessions in the 'scope of aggregation' may
contain all subscriber sessions, regardless of type.

If the 'scope of aggregation' specifies a value other
than 'all' for the subscriber session type, then the
set of subscriber sessions in the 'scope of aggregation may
contain only those subscriber sessions of the specified
type.

Implementation Guidance
=======================
A system MUST maintain a set of statistics with a 'scope of
aggregation' that contains all subscriber sessions maintained
by the system. The system creates this entry during the
initialization of the SNMP entity.

A system SHOULD maintain a set of statistics for each 'scope of
aggregation' containing subscriber sessions of each subscriber
session type the system is capable of providing access. If the
system supports these sets of statistics, then it creates these
entries during the initialization of the SNMP entity.

A system MAY maintain sets of node-specific statistics. if the
system supports sets of node-specific statistics, then it
creates the appropriate entries upon detection of a physical
entity (resulting from system restart or insertion) containing
those nodes. Likewise, the system destroys these entries
upon removal of the physical entity.

Description by cisco

An entry contains a set of aggregated statistics relating to
those subscriber sessions that fall into a 'scope of
aggregation'.

A 'scope of aggregation' is the set of subscriber sessions
that meet specified criteria. For example, a 'scope of
aggregation' may be the set of all PPPoE subscriber sessions
maintained by the system. The following criteria define the
'scope of aggregation':

1) Aggregation Point type
Aggregation point type identifies the format of the
csubAggStatsPoint for this entry.

2) Aggregation Point
'Physical' Aggregation Point type case:
In a distributed system, a 'node' represents a physical
entity capable of maintaining the context representing
a subscriber session.

If the 'scope of aggregation' specifies a physical
entity having an entPhysicalClass of 'chassis', then
the set of subscriber sessions in the 'scope of
aggregation' may contain the subscriber sessions maintained by all
the nodes contained in the system.

If the 'scope of aggregation' specifies a physical
entity having an entPhysicalClass of 'module' (e.g., a
line card), then the set of subscriber sessions in the
'scope of aggregation' may contain the subscriber
sessions maintained by the nodes contained by the
module.

If the 'scope of aggregation' specifies a physical
entity having an entPhysicalClass of 'cpu', then the
set of subscriber sessions in the 'scope of aggregation'
may contain the subscriber sessions maintained by the node
running on that processor.

Observe that a centralized system (i.e., a system
that essentially contains a single node) can only
support a 'scope of aggregation' that specifies a
physical entity classified as a 'chassis'.

If the scope of aggregation specifies 'interface',
then the scope is the set of subscriber sessions carried
by the interface identified the ifIndex value
represented in the csubAggStatsPoint value.

2) Subscriber Session Type
If the 'scope of aggregation' specifies the value 'all'
for the subscriber session type, then the set of
subscriber sessions in the 'scope of aggregation' may
contain all subscriber sessions, regardless of type.

If the 'scope of aggregation' specifies a value other
than 'all' for the subscriber session type, then the
set of subscriber sessions in the 'scope of aggregation may
contain only those subscriber sessions of the specified
type.

Implementation Guidance
=======================
A system MUST maintain a set of statistics with a 'scope of
aggregation' that contains all subscriber sessions maintained
by the system. The system creates this entry during the
initialization of the SNMP entity.

A system SHOULD maintain a set of statistics for each 'scope of
aggregation' containing subscriber sessions of each subscriber
session type the system is capable of providing access. If the
system supports these sets of statistics, then it creates these
entries during the initialization of the SNMP entity.

A system MAY maintain sets of node-specific statistics. if the
system supports sets of node-specific statistics, then it
creates the appropriate entries upon detection of a physical
entity (resulting from system restart or insertion) containing
those nodes. Likewise, the system destroys these entries
upon removal of the physical entity.

Information by cisco_v1

csubAggStatsEntry OBJECT-TYPE
    SYNTAX CsubAggStatsEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "An entry contains a set of aggregated statistics relating to
        those subscriber sessions that fall into a 'scope of 
        aggregation'. 
        
        A 'scope of aggregation' is the set of subscriber sessions 
        that meet specified criteria.  For example, a 'scope of 
        aggregation' may be the set of all PPPoE subscriber sessions 
        maintained by the system.  The following criteria define the 
        'scope of aggregation': 
        
        1)  Aggregation Point type 
                Aggregation point type identifies the format of the 
                csubAggStatsPoint for this entry. 
        
        2)  Aggregation Point 
                'Physical' Aggregation Point type case: 
                In a distributed system, a 'node' represents a physical 
                entity capable of maintaining the context representing 
                a subscriber session. 
        
                If the 'scope of aggregation' specifies a physical 
                entity having an entPhysicalClass of 'chassis', then 
                the set of subscriber sessions in the 'scope of 
                aggregation' may contain the subscriber sessions maintained by all 
                the nodes contained in the system. 
        
                If the 'scope of aggregation' specifies a physical 
                entity having an entPhysicalClass of 'module' (e.g., a 
                line card), then the set of subscriber sessions in the 
                'scope of aggregation' may contain the subscriber 
                sessions maintained by the nodes contained by the 
                module. 
        
                If the 'scope of aggregation' specifies a physical 
                entity having an entPhysicalClass of 'cpu', then the 
                set of subscriber sessions in the 'scope of aggregation' 
                may contain the subscriber sessions maintained by the node 
                running on that processor. 
        
                Observe that a centralized system (i.e., a system 
                that essentially contains a single node) can only 
                support a 'scope of aggregation' that specifies a 
                physical entity classified as a 'chassis'. 
        
                If the scope of aggregation specifies 'interface', 
                then the scope is the set of subscriber sessions carried 
                by the interface identified the ifIndex value 
                represented in the csubAggStatsPoint value. 
        
        2)  Subscriber Session Type 
                If the 'scope of aggregation' specifies the value 'all' 
                for the subscriber session type, then the set of 
                subscriber sessions in the 'scope of aggregation' may 
                contain all subscriber sessions, regardless of type. 
        
                If the 'scope of aggregation' specifies a value other 
                than 'all' for the subscriber session type, then the 
                set of subscriber sessions in the 'scope of aggregation may 
                contain only those subscriber sessions of the specified 
                type. 
        
        Implementation Guidance 
        ======================= 
        A system MUST maintain a set of statistics with a 'scope of 
        aggregation' that contains all subscriber sessions maintained 
        by the system.  The system creates this entry during the 
        initialization of the SNMP entity. 
        
        A system SHOULD maintain a set of statistics for each 'scope of 
        aggregation' containing subscriber sessions of each subscriber 
        session type the system is capable of providing access.  If the 
        system supports these sets of statistics, then it creates these 
        entries during the initialization of the SNMP entity. 
        
        A system MAY maintain sets of node-specific statistics.  if the 
        system supports sets of node-specific statistics, then it 
        creates the appropriate entries upon detection of a physical 
        entity (resulting from system restart or insertion) containing 
        those nodes.  Likewise, the system destroys these entries 
        upon removal of the physical entity."
    REFERENCE
        "A. Bierman and K. McCloghrie, 'Entity MIB (Version 3)',
        RFC-4133, August 2005."
    INDEX { csubAggStatsPointType, csubAggStatsPoint, csubAggStatsSessionType }
    ::= { csubAggStatsTable 1 }

Information by cisco

csubAggStatsEntry OBJECT-TYPE
    SYNTAX          CsubAggStatsEntry
    MAX-ACCESS      not-accessible
    STATUS          current
    DESCRIPTION
        "An entry contains a set of aggregated statistics relating to
        those subscriber sessions that fall into a 'scope of 
        aggregation'. 

        A 'scope of aggregation' is the set of subscriber sessions 
        that meet specified criteria.  For example, a 'scope of 
        aggregation' may be the set of all PPPoE subscriber sessions 
        maintained by the system.  The following criteria define the 
        'scope of aggregation': 

        1)  Aggregation Point type 
                Aggregation point type identifies the format of the 
                csubAggStatsPoint for this entry. 

        2)  Aggregation Point 
                'Physical' Aggregation Point type case: 
                In a distributed system, a 'node' represents a physical 
                entity capable of maintaining the context representing 
                a subscriber session. 

                If the 'scope of aggregation' specifies a physical 
                entity having an entPhysicalClass of 'chassis', then 
                the set of subscriber sessions in the 'scope of 
                aggregation' may contain the subscriber sessions maintained by all 
                the nodes contained in the system. 

                If the 'scope of aggregation' specifies a physical 
                entity having an entPhysicalClass of 'module' (e.g., a 
                line card), then the set of subscriber sessions in the 
                'scope of aggregation' may contain the subscriber 
                sessions maintained by the nodes contained by the 
                module. 

                If the 'scope of aggregation' specifies a physical 
                entity having an entPhysicalClass of 'cpu', then the 
                set of subscriber sessions in the 'scope of aggregation' 
                may contain the subscriber sessions maintained by the node 
                running on that processor. 

                Observe that a centralized system (i.e., a system 
                that essentially contains a single node) can only 
                support a 'scope of aggregation' that specifies a 
                physical entity classified as a 'chassis'. 

                If the scope of aggregation specifies 'interface', 
                then the scope is the set of subscriber sessions carried 
                by the interface identified the ifIndex value 
                represented in the csubAggStatsPoint value. 

        2)  Subscriber Session Type 
                If the 'scope of aggregation' specifies the value 'all' 
                for the subscriber session type, then the set of 
                subscriber sessions in the 'scope of aggregation' may 
                contain all subscriber sessions, regardless of type. 

                If the 'scope of aggregation' specifies a value other 
                than 'all' for the subscriber session type, then the 
                set of subscriber sessions in the 'scope of aggregation may 
                contain only those subscriber sessions of the specified 
                type. 

        Implementation Guidance 
        ======================= 
        A system MUST maintain a set of statistics with a 'scope of 
        aggregation' that contains all subscriber sessions maintained 
        by the system.  The system creates this entry during the 
        initialization of the SNMP entity. 

        A system SHOULD maintain a set of statistics for each 'scope of 
        aggregation' containing subscriber sessions of each subscriber 
        session type the system is capable of providing access.  If the 
        system supports these sets of statistics, then it creates these 
        entries during the initialization of the SNMP entity. 

        A system MAY maintain sets of node-specific statistics.  if the 
        system supports sets of node-specific statistics, then it 
        creates the appropriate entries upon detection of a physical 
        entity (resulting from system restart or insertion) containing 
        those nodes.  Likewise, the system destroys these entries 
        upon removal of the physical entity."
    REFERENCE
        "A. Bierman and K. McCloghrie, 'Entity MIB (Version 3)',
        RFC-4133, August 2005."
    INDEX           {
                        csubAggStatsPointType,
                        csubAggStatsPoint,
                        csubAggStatsSessionType
                    } 
    ::= { csubAggStatsTable 1 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Children (36)