OID reference

bgpAggregateTable

1.2.826.0.1.1578918.5.65.1.5.10

Description

This table is used to control how DC-BGP aggregates addresses. Each entry in the table results in one aggregate address being created. This will result in an aggregate entry in the routing table when at least one more specific route matching the address specified is learnt. If the aggregate is marked as 'permanent', t…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.0.1.1578918.5.65.1.5 (bgpPib)
Node code
10
Node name
bgpAggregateTable
Category
SNMP management object
Numeric OID
1.2.826.0.1.1578918.5.65.1.5.10
URN notation
urn:oid:1.2.826.0.1.1578918.5.65.1.5.10
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 2 826 0 1 1578918 5 65 1 5 10}

  • {iso(1) member-body(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpAggregateTable(10)}
  • {iso(1) member-body(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpAggregateTable(10)}
  • {iso(1) member-body(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpAggregateTable(10)}
  • {iso(1) member-body(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpAggregateTable(10)}
  • {iso(1) memberBody(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpAggregateTable(10)}
  • {iso(1) memberBody(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpAggregateTable(10)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpAggregateTable(10)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpAggregateTable(10)}
OID-IRI notation
  • /1/2/826/0/1/1578918/5/65/1/5/10
  • /ISO/Member-Body/GB/0/1/1578918/5/65/1/5/10
  • /ISO/Member-Body/826/0/1/1578918/5/65/1/5/10
  • /ISO/2/826/0/1/1578918/5/65/1/5/10
Named path variants
  • /iso/member-body/gb/national/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/member-body/gb/national/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/member-body/gb/national/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/member-body/gb/national/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/member-body/gb/gbNational/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/member-body/gb/gbNational/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/member-body/gb/gbNational/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/member-body/gb/gbNational/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/memberBody/gb/national/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/memberBody/gb/national/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/memberBody/gb/national/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/memberBody/gb/national/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/memberBody/gb/gbNational/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/memberBody/gb/gbNational/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/memberBody/gb/gbNational/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpAggregateTable
  • /iso/memberBody/gb/gbNational/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpAggregateTable

SNMP properties

Value type
SEQUENCE OF BgpAggregateEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

bgpAggregateTable OBJECT-TYPE
  -- FAMILY-SHORT-NAME BGP_AGA
    SYNTAX      SEQUENCE OF BgpAggregateEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "This table is used to control how DC-BGP aggregates
                 addresses.  Each entry in the table results in one aggregate
                 address being created.  This will result in an aggregate
                 entry in the routing table when at least one more specific
                 route matching the address specified is learnt.  If the
                 aggregate is marked as 'permanent', then an aggregate entry
                 is created in the routing table even if no more specific
                 matching routes are known.

                 The options allow configuration as to whether the AS_PATH
                 attribute keeps full information or not, and whether the more
                 specfic route is also entered in the routing table (the
                 summary only option).  These options can also be chosen on
                 a per route basis by matching on the advertise and suppress
                 route maps.

                 The attribute route map is used to set attributes of the
                 aggregated route if required.

                 It is possible to create overlapping entries in the table.
                 This can result in routes that match more than one
                 table entry.

                 -  If a route matches multiple aggregate addresses,
                 then it is suppressed any of the matching aggregates would
                 cause the route to be suppressed.

                 -  If a route matches the advertise map of an aggregate
                 address, then it is not aggregated by that aggregate address.
                 However, it may still be aggregated by other overlapping
                 aggregate addresses."
    ::= { bgpPib 10 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This table is used to control how DC-BGP aggregates addresses. Each entry in the table results in one aggregate address being created. This will result in an aggregate entry in the routing table when at least one more specific route matching the address specified is learnt. If the aggregate is marked as 'permanent', then an aggregate entry is created in the routing table even if no more specific matching routes are known. The options allow configuration as to whether the AS_PATH attribute keeps full information or not, and whether the more specfic route is also entered in the routing table (the summary only option). These options can also be chosen on a per route basis by matching on the advertise and suppress route maps. The attribute route map is used to set attributes of the aggregated route if required. It is possible to create overlapping entries in the table. This can result in routes that match more than one table entry. - If a route matches multiple aggregate addresses, then it is suppressed any of the matching aggregates would cause the route to be suppressed. - If a route matches the advertise map of an aggregate address, then it is not aggregated by that aggregate address. However, it may still be aggregated by other overlapping aggregate addresses.

Sources for this description

Data Connection / MetaSwitch MIB copies (MibBrowser.online)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Data Connection / MetaSwitch MIB copies (MibBrowser.online)1 record · 1 source

Description 1

bgpAggregateTable · currentData Connection / MetaSwitch MIB copies (MibBrowser.online)1 source

Status in source: current.

Names: bgpAggregateTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpAggregateTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "BgpAggregateEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table is used to control how DC-BGP aggregates addresses. Each entry in the table results in one aggregate address being created. This will result in an aggregate entry in the routing table when at least one more specific route matching the address specified is learnt. If the aggregate is marked as 'permanent', then an aggregate entry is created in the routing table even if no more specific matching routes are known. The options allow configuration as to whether the AS_PATH attribute keeps full information or not, and whether the more specfic route is also entered in the routing table (the summary only option). These options can also be chosen on a per route basis by matching on the advertise and suppress route maps. The attribute route map is used to set attributes of the aggregated route if required. It is possible to create overlapping entries in the table. This can result in routes that match more than one table entry. - If a route matches multiple aggregate addresses, then it is suppressed any of the matching aggregates would cause the route to be suppressed. - If a route matches the advertise map of an aggregate address, then it is not aggregated by that aggregate address. However, it may still be aggregated by other overlapping aggregate addresses.\"",
    "::=",
    "{",
    "bgpPib",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "BgpAggregateEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table is used to control how DC-BGP aggregates addresses. Each entry in the table results in one aggregate address being created. This will result in an aggregate entry in the routing table when at least one more specific route matching the address specified is learnt. If the aggregate is marked as 'permanent', then an aggregate entry is created in the routing table even if no more specific matching routes are known. The options allow configuration as to whether the AS_PATH attribute keeps full information or not, and whether the more specfic route is also entered in the routing table (the summary only option). These options can also be chosen on a per route basis by matching on the advertise and suppress route maps. The attribute route map is used to set attributes of the aggregated route if required. It is possible to create overlapping entries in the table. This can result in routes that match more than one table entry. - If a route matches multiple aggregate addresses, then it is suppressed any of the matching aggregates would cause the route to be suppressed. - If a route matches the advertise map of an aggregate address, then it is not aggregated by that aggregate address. However, it may still be aggregated by other overlapping aggregate addresses."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.2.826.0.1)

None (see information above)

Current Registration Authority (inferred from ancestor 1.2.826.0)

Telecoms CSC

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.2.826.0.1.1578918.5.65.1.5.10.1 bgpAggregateEntry1010

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.2.826.0.1.1578918.5.65.1.5.1 bgpRouteMapTable151
1.2.826.0.1.1578918.5.65.1.5.2 bgpIpPreTable111
1.2.826.0.1.1578918.5.65.1.5.7 bgpPeergrTable113
1.2.826.0.1.1578918.5.65.1.5.8 bgpConfigTable119
1.2.826.0.1.1578918.5.65.1.5.9 bgpFlapConfigTable110
1.2.826.0.1.1578918.5.65.1.5.11 bgpOrfCapabilityTable16
1.2.826.0.1.1578918.5.65.1.5.12 bgpPeergrAfiSafiTable19