Each entry in this table defines a filter to match against incoming/outgoing setups on inter-domain interfaces. Each entry also contains the configuration of the rerouting services for a call matching the filter. Matching is performed on incoming setup indications and Outgoing setup requests of svcs and svps when the switching system is the edge switch for the call. The matching is done on the inter-domain interface. A setup message is matching a filter entry, if all the attributes contained in the filter match the setup message. The matching criteria is contained in the description of each object. The entry is also used to configure the rerouting services for soft pvcs or soft pvps whose terminating legs are located on an interface of this switch. A new entry can be created by specifying an atmTraceFilterIndex value that is currently not being used and also using an appropriate value (createAndGo or createAndWait) for the reroutingFilterRowStatus object. The reroutingFilterIndex is used as the instance ID to Uniquely identify a filter configured on this switching system.
OID reference
reroutingFilterEntry
1.3.6.1.4.1.353.5.9.3.1.1.2.1
Description
Each entry in this table defines a filter to match against incoming/outgoing setups on inter-domain interfaces. Each entry also contains the configuration of the rerouting services for a call matching the filter. Matching is performed on incoming setup indications and Outgoing setup requests of svcs and svps when the …
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.353.5.9.3.1.1.2 (reroutingFilterTable)
- Node code
- 1
- Node name
- reroutingFilterEntry
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.353.5.9.3.1.1.2.1
- URN notation
- urn:oid:1.3.6.1.4.1.353.5.9.3.1.1.2.1
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 353 5 9 3 1 1 2 1}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfRerouting(3) atmfreroutingMIB(1) reroutingMIBObjects(1) reroutingFilterTable(2) reroutingFilterEntry(1)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/353/5/9/3/1/1/2/1
- /ISO/Identified-Organization/6/1/4/1/353/5/9/3/1/1/2/1
- /ISO/3/6/1/4/1/353/5/9/3/1/1/2/1
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/atmForum/atmForumNetworkManagement/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/identified-organization/dod/internet/private/enterprise/atmForum/atmForumNetworkManagment/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/identified-organization/dod/internet/private/enterprises/atmForum/atmForumNetworkManagement/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/identified-organization/dod/internet/private/enterprises/atmForum/atmForumNetworkManagment/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/identified-organization/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagement/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/identified-organization/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagment/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/identified-organization/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagement/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/identified-organization/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagment/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/org/dod/internet/private/enterprise/atmForum/atmForumNetworkManagement/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/org/dod/internet/private/enterprise/atmForum/atmForumNetworkManagment/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/org/dod/internet/private/enterprises/atmForum/atmForumNetworkManagement/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/org/dod/internet/private/enterprises/atmForum/atmForumNetworkManagment/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/org/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagement/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/org/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagment/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/org/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagement/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- /iso/org/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagment/atmfSignalling/atmfRerouting/atmfreroutingMIB/reroutingMIBObjects/reroutingFilterTable/reroutingFilterEntry
- Additional combinations skipped.
SNMP properties
- Value type
- ReroutingFilterEntry
- 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.
Published definition
The displayed source records contain one distinct definition. Compare its source records.
reroutingFilterEntry OBJECT-TYPE
SYNTAX ReroutingFilterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry in this table defines a filter to match against
incoming/outgoing setups on inter-domain interfaces. Each
entry also contains the configuration of the rerouting
services for a call matching the filter.
Matching is performed on incoming setup indications and
Outgoing setup requests of svcs and svps when the switching
system is the edge switch for the call. The matching is done
on the inter-domain interface.
A setup message is matching a filter entry, if all the
attributes contained in the filter match the setup message.
The matching criteria is contained in the description of each
object.
The entry is also used to configure the rerouting services for
soft pvcs or soft pvps whose terminating legs are located on
an interface of this switch.
A new entry can be created by specifying an atmTraceFilterIndex
value that is currently not being used and also using an
appropriate value (createAndGo or createAndWait) for the
reroutingFilterRowStatus object.
The reroutingFilterIndex is used as the instance ID to
Uniquely identify a filter configured on this switching
system."
INDEX { reroutingFilterIndex}
::= { reroutingFilterTable 1 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1ATM Forum official specifications
reroutingFilterEntry · currentATM Forum official specifications
Status in source: current.
Names: reroutingFilterEntry
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"reroutingFilterEntry",
"OBJECT-TYPE",
"SYNTAX",
"ReroutingFilterEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"Each entry in this table defines a filter to match against incoming/outgoing setups on inter-domain interfaces. Each entry also contains the configuration of the rerouting services for a call matching the filter. Matching is performed on incoming setup indications and Outgoing setup requests of svcs and svps when the switching system is the edge switch for the call. The matching is done on the inter-domain interface. A setup message is matching a filter entry, if all the attributes contained in the filter match the setup message. The matching criteria is contained in the description of each object. The entry is also used to configure the rerouting services for soft pvcs or soft pvps whose terminating legs are located on an interface of this switch. A new entry can be created by specifying an atmTraceFilterIndex value that is currently not being used and also using an appropriate value (createAndGo or createAndWait) for the reroutingFilterRowStatus object. The reroutingFilterIndex is used as the instance ID to Uniquely identify a filter configured on this switching system.\"",
"INDEX",
"{",
"reroutingFilterIndex",
"}",
"::=",
"{",
"reroutingFilterTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"ReroutingFilterEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Each entry in this table defines a filter to match against incoming/outgoing setups on inter-domain interfaces. Each entry also contains the configuration of the rerouting services for a call matching the filter. Matching is performed on incoming setup indications and Outgoing setup requests of svcs and svps when the switching system is the edge switch for the call. The matching is done on the inter-domain interface. A setup message is matching a filter entry, if all the attributes contained in the filter match the setup message. The matching criteria is contained in the description of each object. The entry is also used to configure the rerouting services for soft pvcs or soft pvps whose terminating legs are located on an interface of this switch. A new entry can be created by specifying an atmTraceFilterIndex value that is currently not being used and also using an appropriate value (createAndGo or createAndWait) for the reroutingFilterRowStatus object. The reroutingFilterIndex is used as the instance ID to Uniquely identify a filter configured on this switching system."
],
null,
null,
[
"INDEX",
[
[
0,
"reroutingFilterIndex"
]
]
],
null
]
}- ATM Forum official specifications
· Publisher's source file: ATM Forum rerouting MIB — text extracted from the original PDF
Module: ATM-REROUTING-MIB
See published definition above
· Download ATM Forum rerouting MIB — text extracted from the original PDFModule imports
{'IF-MIB': ['InterfaceIndex', 'ifIndex'], 'ATM-MIB': ['atmVplVpi', 'atmVclVpi', 'atmVclVci'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus'], 'ATM-TC-MIB': ['AtmAddr'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Integer32', 'Unsigned32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Related source files and packages:
Registration
Registration authorities
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.353)
Direct children (13)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.1 | reroutingFilterIndex | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.2 | reroutingFilterIfDirection | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.3 | reroutingFilterInterface | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.4 | reroutingFilterConnKind | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.5 | reroutingFilterServiceCategory | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.6 | reroutingFilterCallingPartyPrefix | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.7 | reroutingFilterCallingPartyLength | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.8 | reroutingFilterCalledPartyPrefix | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.9 | reroutingFilterCalledPartyLength | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.10 | reroutingFilterNetworkServicesAvailable | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.11 | reroutingFilterHardReroutingServiceRequest | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.12 | reroutingFilterSoftReroutingServiceRequest | 0 | 0 | |
| 1.3.6.1.4.1.353.5.9.3.1.1.2.1.13 | reroutingFilterRowStatus | 0 | 0 |