This attribute is used only when splitting or merging existing
topology regions. It specifies which topology regions are in a
migration status. A node will only exchange topological
information with a connected node under the following conditions:
(i) the nodes belong to the same topology region, (ii) one of the
nodes is provisioned with the default regionId of 0, (iii) the
connected node's splittingRegionIds attribute is provisioned to
contain the local node's regionId value and the local node's
splittingRegionIds is also provisioned to contain the connected
node's regionId value when both two nodes' regionIds are different
and non-zero.
When this attribute is used during migration of regions, values for
the attribute are normally the old and new regionIds for the node.
Use of this attribute makes it possible to migrate existing topology
regions in the following cases: (i) splitting a topology region into
two without isolating a node, (ii) merging two different topology
regions into one without introducing an extra topological barrier.
The attribute should be cleaned when all migration activities are
complete. At this point, the region boundary will take effect.
Parsed from file nortelPP-baseRoutingV1_BG00S4C.mib.txt
Company: None
Module: Nortel-Magellan-Passport-BaseRoutingMIB
This attribute is used only when splitting or merging existing
topology regions. It specifies which topology regions are in a
migration status. A node will only exchange topological
information with a connected node under the following conditions:
(i) the nodes belong to the same topology region, (ii) one of the
nodes is provisioned with the default regionId of 0, (iii) the
connected node's splittingRegionIds attribute is provisioned to
contain the local node's regionId value and the local node's
splittingRegionIds is also provisioned to contain the connected
node's regionId value when both two nodes' regionIds are different
and non-zero.
When this attribute is used during migration of regions, values for
the attribute are normally the old and new regionIds for the node.
Use of this attribute makes it possible to migrate existing topology
regions in the following cases: (i) splitting a topology region into
two without isolating a node, (ii) merging two different topology
regions into one without introducing an extra topological barrier.
The attribute should be cleaned when all migration activities are
complete. At this point, the region boundary will take effect.
Parsed from file Nortel-Magellan-Passport-BaseRoutingMIB.mib
Module: Nortel-Magellan-Passport-BaseRoutingMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-Magellan-Passport-BaseRoutingMIB
[Automatically extracted from oidview.com]
rtgSplittingRegionIdsTable OBJECT-TYPE SYNTAX SEQUENCE OF RtgSplittingRegionIdsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This attribute is used only when splitting or merging existing topology regions. It specifies which topology regions are in a migration status. A node will only exchange topological information with a connected node under the following conditions: (i) the nodes belong to the same topology region, (ii) one of the nodes is provisioned with the default regionId of 0, (iii) the connected node's splittingRegionIds attribute is provisioned to contain the local node's regionId value and the local node's splittingRegionIds is also provisioned to contain the connected node's regionId value when both two nodes' regionIds are different and non-zero. When this attribute is used during migration of regions, values for the attribute are normally the old and new regionIds for the node. Use of this attribute makes it possible to migrate existing topology regions in the following cases: (i) splitting a topology region into two without isolating a node, (ii) merging two different topology regions into one without introducing an extra topological barrier. The attribute should be cleaned when all migration activities are complete. At this point, the region boundary will take effect." ::= { rtg 407 }
rtgSplittingRegionIdsTable OBJECT-TYPE SYNTAX SEQUENCE OF RtgSplittingRegionIdsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This attribute is used only when splitting or merging existing topology regions. It specifies which topology regions are in a migration status. A node will only exchange topological information with a connected node under the following conditions: (i) the nodes belong to the same topology region, (ii) one of the nodes is provisioned with the default regionId of 0, (iii) the connected node's splittingRegionIds attribute is provisioned to contain the local node's regionId value and the local node's splittingRegionIds is also provisioned to contain the connected node's regionId value when both two nodes' regionIds are different and non-zero. When this attribute is used during migration of regions, values for the attribute are normally the old and new regionIds for the node. Use of this attribute makes it possible to migrate existing topology regions in the following cases: (i) splitting a topology region into two without isolating a node, (ii) merging two different topology regions into one without introducing an extra topological barrier. The attribute should be cleaned when all migration activities are complete. At this point, the region boundary will take effect." ::= { rtg 407 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.2.4.1.40.407.1 | rtgSplittingRegionIdsEntry | 2 | 2 | An entry in the rtgSplittingRegionIdsTable. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.2.4.1.40.1 | rtgRowStatusTable | 1 | 5 | This entry controls the addition and deletion of rtg components. |
| 1.3.6.1.4.1.562.2.4.1.40.2 | rtgRs | 7 | 53 | None |
| 1.3.6.1.4.1.562.2.4.1.40.3 | rtgVns | 9 | 88 | None |
| 1.3.6.1.4.1.562.2.4.1.40.4 | rtgDpn | 13 | 205 | None |
| 1.3.6.1.4.1.562.2.4.1.40.5 | rtgTop | 3 | 58 | None |
| 1.3.6.1.4.1.562.2.4.1.40.6 | rtgPors | 5 | 66 | None |
| 1.3.6.1.4.1.562.2.4.1.40.12 | rtgProvTable | 1 | 2 | This group contains the provisioning data for the routing system. |