The value of this object indicates how the
equipment will try to use this logical port (or
this couple [logical port, channel]) which
composes this route.
The following combinations are possible :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|Route|LP|Type| Routing description |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 1 | 1| n | -> on one LP |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 2 | 1| n | -> 1 : on one main LP |
| 2 | 2| b1 | \ |
| 2 | 3| b1 | > 2 : on three equal |
| 2 | 4| b1 | / priority backup LPs |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 3 | 1| n | \ |
| 3 | 2| n | | |
| 3 | 3| n | > on five equal priority LPs |
| 3 | 4| n | | |
| 3 | 5| n | / |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 4 | 1| n | -> 1 : on one main LP |
| 4 | 2| b1 | -> 2 : on one first backup LP |
| 4 | 3| b2 | -> 3 : on one second backup LP |
| 4 | 4| b3 | -> 4 : on one third backup LP |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 5 | 1| n | \ on three equal |
| 5 | 2| n | > 1 : priority main LPs |
| 5 | 3| n | / |
| 5 | 4| b1 | -> 2 : on one backup LP |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 8 | 1| nM | each module of the equipment |
| 8 | 2| b1 | considers its own LPs as having |
| 8 |11| b2 | a higher priority than the |
| 8 | 3| b3 | LPs of the other modules |
| 8 |21| b4 | (see below) |
| 8 |12| b5 | |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 9 | 1| nC | -> 1 : on one main LP |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 10 | 1| nC | -> 1 : on one main LP |
| 10 | 2| b1 | -> 2 : on one first backup LP |
| 10 | 3| b2 | -> 3 : on one second backup LP |
| 10 | 4| b3 | -> 4 : on one third backup LP |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Types : n : normal, nM : normalPriorityModule, b1
: backup1, b2 : backup2, b3 : backup3, b4 :
backup4, b5 : backup5, dynamic, backupDynamic,
nC : normalClear1.
Interpretation of the route 8 : In this example
let us suppose that LP 1, 2 and 3 belongs to
the module 0, 11 and 12 to the module 1, and 21
to the module 2. The route 8 becomes :
on the module 0 :
LP : 1 2 3 11 21 12
Type : n b1 b2 b3 b4 b5
on the module 1 :
LP : 11 12 1 2 3 21
Type : n b1 b2 b3 b4 b5
on the module 2 :
LP : 21 1 2 11 3 12
Type : n b1 b2 b3 b4 b5
Interpretation of the route 9 : there must be at
least 1 valid entry with try on = normalClear1
(or all) in the Clear cause/diagnostic table.
The address is converted according to that
entry.
Interpretation of the route 10 : there must be at
least 1 valid entry with try on = normalClear1
and 1 with try on = backup (or 1 with all) in
the Clear cause/diagnostic table. The address
is converted according to that entry.
The default value is 'normal'.
Parsed from file v42ami1e.mib.txt
Company: None
Module: PCE-MIB
The value of this object indicates how the
equipment will try to use this logical port (or
this couple [logical port, channel]) which
composes this route.
The following combinations are possible :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|Route|LP|Type| Routing description |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 1 | 1| n | -> on one LP |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 2 | 1| n | -> 1 : on one main LP |
| 2 | 2| b1 | \ |
| 2 | 3| b1 | > 2 : on three equal |
| 2 | 4| b1 | / priority backup LPs |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 3 | 1| n | \ |
| 3 | 2| n | | |
| 3 | 3| n | > on five equal priority LPs |
| 3 | 4| n | | |
| 3 | 5| n | / |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 4 | 1| n | -> 1 : on one main LP |
| 4 | 2| b1 | -> 2 : on one first backup LP |
| 4 | 3| b2 | -> 3 : on one second backup LP |
| 4 | 4| b3 | -> 4 : on one third backup LP |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 5 | 1| n | \ on three equal |
| 5 | 2| n | > 1 : priority main LPs |
| 5 | 3| n | / |
| 5 | 4| b1 | -> 2 : on one backup LP |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 8 | 1| nM | each module of the equipment |
| 8 | 2| b1 | considers its own LPs as having |
| 8 |11| b2 | a higher priority than the |
| 8 | 3| b3 | LPs of the other modules |
| 8 |21| b4 | (see below) |
| 8 |12| b5 | |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 9 | 1| nC | -> 1 : on one main LP |
|~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| 10 | 1| nC | -> 1 : on one main LP |
| 10 | 2| b1 | -> 2 : on one first backup LP |
| 10 | 3| b2 | -> 3 : on one second backup LP |
| 10 | 4| b3 | -> 4 : on one third backup LP |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Types : n : normal, nM : normalPriorityModule, b1
: backup1, b2 : backup2, b3 : backup3, b4 :
backup4, b5 : backup5, dynamic, backupDynamic,
nC : normalClear1.
Interpretation of the route 8 : In this example
let us suppose that LP 1, 2 and 3 belongs to
the module 0, 11 and 12 to the module 1, and 21
to the module 2. The route 8 becomes :
on the module 0 :
LP : 1 2 3 11 21 12
Type : n b1 b2 b3 b4 b5
on the module 1 :
LP : 11 12 1 2 3 21
Type : n b1 b2 b3 b4 b5
on the module 2 :
LP : 21 1 2 11 3 12
Type : n b1 b2 b3 b4 b5
Interpretation of the route 9 : there must be at
least 1 valid entry with try on = normalClear1
(or all) in the Clear cause/diagnostic table.
The address is converted according to that
entry.
Interpretation of the route 10 : there must be at
least 1 valid entry with try on = normalClear1
and 1 with try on = backup (or 1 with all) in
the Clear cause/diagnostic table. The address
is converted according to that entry.
The default value is 'normal'.
Parsed from file PCE-MIB.mib
Module: PCE-MIB
Vendor: Philips Communication d'Entreprise Claude Lubin
Module: PCE-MIB
[Automatically extracted from oidview.com]
fcwRoutType OBJECT-TYPE SYNTAX INTEGER { normal(1), normalPriorityModule(2), backup1(3), backup2(4), backup3(5), backup4(6), backup5(7), dynamic(8), backupDynamic(9), normalClear1(10) } ACCESS read-write STATUS mandatory DESCRIPTION "The value of this object indicates how the equipment will try to use this logical port (or this couple [logical port, channel]) which composes this route. The following combinations are possible : ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |Route|LP|Type| Routing description | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 1 | 1| n | -> on one LP | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 2 | 1| n | -> 1 : on one main LP | | 2 | 2| b1 | \ | | 2 | 3| b1 | > 2 : on three equal | | 2 | 4| b1 | / priority backup LPs | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 3 | 1| n | \ | | 3 | 2| n | | | | 3 | 3| n | > on five equal priority LPs | | 3 | 4| n | | | | 3 | 5| n | / | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 4 | 1| n | -> 1 : on one main LP | | 4 | 2| b1 | -> 2 : on one first backup LP | | 4 | 3| b2 | -> 3 : on one second backup LP | | 4 | 4| b3 | -> 4 : on one third backup LP | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 5 | 1| n | \ on three equal | | 5 | 2| n | > 1 : priority main LPs | | 5 | 3| n | / | | 5 | 4| b1 | -> 2 : on one backup LP | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 8 | 1| nM | each module of the equipment | | 8 | 2| b1 | considers its own LPs as having | | 8 |11| b2 | a higher priority than the | | 8 | 3| b3 | LPs of the other modules | | 8 |21| b4 | (see below) | | 8 |12| b5 | | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 9 | 1| nC | -> 1 : on one main LP | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 10 | 1| nC | -> 1 : on one main LP | | 10 | 2| b1 | -> 2 : on one first backup LP | | 10 | 3| b2 | -> 3 : on one second backup LP | | 10 | 4| b3 | -> 4 : on one third backup LP | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Types : n : normal, nM : normalPriorityModule, b1 : backup1, b2 : backup2, b3 : backup3, b4 : backup4, b5 : backup5, dynamic, backupDynamic, nC : normalClear1. Interpretation of the route 8 : In this example let us suppose that LP 1, 2 and 3 belongs to the module 0, 11 and 12 to the module 1, and 21 to the module 2. The route 8 becomes : on the module 0 : LP : 1 2 3 11 21 12 Type : n b1 b2 b3 b4 b5 on the module 1 : LP : 11 12 1 2 3 21 Type : n b1 b2 b3 b4 b5 on the module 2 : LP : 21 1 2 11 3 12 Type : n b1 b2 b3 b4 b5 Interpretation of the route 9 : there must be at least 1 valid entry with try on = normalClear1 (or all) in the Clear cause/diagnostic table. The address is converted according to that entry. Interpretation of the route 10 : there must be at least 1 valid entry with try on = normalClear1 and 1 with try on = backup (or 1 with all) in the Clear cause/diagnostic table. The address is converted according to that entry. The default value is 'normal'." ::= { fcwRouteEntry 5 }
fcwRoutType OBJECT-TYPE SYNTAX INTEGER { normal(1), normalPriorityModule(2), backup1(3), backup2(4), backup3(5), backup4(6), backup5(7), dynamic(8), backupDynamic(9), normalClear1(10) } ACCESS read-write STATUS mandatory DESCRIPTION "The value of this object indicates how the equipment will try to use this logical port (or this couple [logical port, channel]) which composes this route. The following combinations are possible : ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |Route|LP|Type| Routing description | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 1 | 1| n | -> on one LP | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 2 | 1| n | -> 1 : on one main LP | | 2 | 2| b1 | \ | | 2 | 3| b1 | > 2 : on three equal | | 2 | 4| b1 | / priority backup LPs | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 3 | 1| n | \ | | 3 | 2| n | | | | 3 | 3| n | > on five equal priority LPs | | 3 | 4| n | | | | 3 | 5| n | / | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 4 | 1| n | -> 1 : on one main LP | | 4 | 2| b1 | -> 2 : on one first backup LP | | 4 | 3| b2 | -> 3 : on one second backup LP | | 4 | 4| b3 | -> 4 : on one third backup LP | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 5 | 1| n | \ on three equal | | 5 | 2| n | > 1 : priority main LPs | | 5 | 3| n | / | | 5 | 4| b1 | -> 2 : on one backup LP | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 8 | 1| nM | each module of the equipment | | 8 | 2| b1 | considers its own LPs as having | | 8 |11| b2 | a higher priority than the | | 8 | 3| b3 | LPs of the other modules | | 8 |21| b4 | (see below) | | 8 |12| b5 | | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 9 | 1| nC | -> 1 : on one main LP | |~~~~~|~~|~~~~|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | 10 | 1| nC | -> 1 : on one main LP | | 10 | 2| b1 | -> 2 : on one first backup LP | | 10 | 3| b2 | -> 3 : on one second backup LP | | 10 | 4| b3 | -> 4 : on one third backup LP | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Types : n : normal, nM : normalPriorityModule, b1 : backup1, b2 : backup2, b3 : backup3, b4 : backup4, b5 : backup5, dynamic, backupDynamic, nC : normalClear1. Interpretation of the route 8 : In this example let us suppose that LP 1, 2 and 3 belongs to the module 0, 11 and 12 to the module 1, and 21 to the module 2. The route 8 becomes : on the module 0 : LP : 1 2 3 11 21 12 Type : n b1 b2 b3 b4 b5 on the module 1 : LP : 11 12 1 2 3 21 Type : n b1 b2 b3 b4 b5 on the module 2 : LP : 21 1 2 11 3 12 Type : n b1 b2 b3 b4 b5 Interpretation of the route 9 : there must be at least 1 valid entry with try on = normalClear1 (or all) in the Clear cause/diagnostic table. The address is converted according to that entry. Interpretation of the route 10 : there must be at least 1 valid entry with try on = normalClear1 and 1 with try on = backup (or 1 with all) in the Clear cause/diagnostic table. The address is converted according to that entry. The default value is 'normal'." ::= { fcwRouteEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.866.20.1.25.50.1.1 | fcwRoutRouteId | 0 | 0 | The value of this object identifies one and only one route. One route may be composed of one or several logical ports. The possib… |
| 1.3.6.1.4.1.866.20.1.25.50.1.2 | fcwRoutLogPortId | 0 | 0 | The value of this object identifies one of the logical ports which compose the route defined by fcwRoutRouteId. The possible valu… |
| 1.3.6.1.4.1.866.20.1.25.50.1.3 | fcwRoutChannelId | 0 | 0 | The value of this object identifies one of the channels available on the logical port defined by fcwRoutLogPortId. Most of times … |
| 1.3.6.1.4.1.866.20.1.25.50.1.4 | fcwRoutStatus | 0 | 0 | The value of this object indicates the state of the entry of this table. The default value is 'valid'. It must be set to 'invalid… |