A table that contains information linking
physical backplane allocation to logical
networks. This information is useful:
(1) to determine the physical allocation
of networks on the backplane, and
(2) to determine the remaining capacity of
the backplane for future network growth.
Since unknown modules are managed via dip
switches, this is useful in order to set the
dips to the appropriate settings.
Ethernet is a bus architecture. Once a path is
allocated, all modules and ports can access that
path.
Token Ring and FDDI are ring architectures.
Each module on a ring requires a path. Therefore,
4 paths could be used to link 4 modules together
on one ring, or 2 modules on 2 separate rings.
It is possible to have a module allocated to
a ring (and thus a data path) without linking
to another module.
These rules can be used to determine the remaining
capacity for network growth.
Parsed from file chipcom-emm.mib.txt
Company: None
Module: ChpCom-EMM
A table that contains information linking
physical backplane allocation to logical
networks. This information is useful:
(1) to determine the physical allocation
of networks on the backplane, and
(2) to determine the remaining capacity of
the backplane for future network growth.
Since unknown modules are managed via dip
switches, this is useful in order to set the
dips to the appropriate settings.
Ethernet is a bus architecture. Once a path is
allocated, all modules and ports can access that
path.
Token Ring and FDDI are ring architectures.
Each module on a ring requires a path. Therefore,
4 paths could be used to link 4 modules together
on one ring, or 2 modules on 2 separate rings.
It is possible to have a module allocated to
a ring (and thus a data path) without linking
to another module.
These rules can be used to determine the remaining
capacity for network growth.
Parsed from file CHIPCOMMIB.mib
Module: CHIPCOMMIB
Vendor: Chippcom
Module: CHIPCOMMIB
[Automatically extracted from oidview.com]
olNetDPTable OBJECT-TYPE SYNTAX SEQUENCE OF OlNetDPEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table that contains information linking physical backplane allocation to logical networks. This information is useful: (1) to determine the physical allocation of networks on the backplane, and (2) to determine the remaining capacity of the backplane for future network growth. Since unknown modules are managed via dip switches, this is useful in order to set the dips to the appropriate settings. Ethernet is a bus architecture. Once a path is allocated, all modules and ports can access that path. Token Ring and FDDI are ring architectures. Each module on a ring requires a path. Therefore, 4 paths could be used to link 4 modules together on one ring, or 2 modules on 2 separate rings. It is possible to have a module allocated to a ring (and thus a data path) without linking to another module. These rules can be used to determine the remaining capacity for network growth." ::= { olNet 1 }
olNetDPTable OBJECT-TYPE SYNTAX SEQUENCE OF OlNetDPEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table that contains information linking physical backplane allocation to logical networks. This information is useful: (1) to determine the physical allocation of networks on the backplane, and (2) to determine the remaining capacity of the backplane for future network growth. Since unknown modules are managed via dip switches, this is useful in order to set the dips to the appropriate settings. Ethernet is a bus architecture. Once a path is allocated, all modules and ports can access that path. Token Ring and FDDI are ring architectures. Each module on a ring requires a path. Therefore, 4 paths could be used to link 4 modules together on one ring, or 2 modules on 2 separate rings. It is possible to have a module allocated to a ring (and thus a data path) without linking to another module. These rules can be used to determine the remaining capacity for network growth." ::= { olNet 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.49.2.3.1.5.1.1.1 | olNetDPEntry | 2 | 2 | A list of information about each data path in the concentrator. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.49.2.3.1.5.1.2 | olNetSecurityMACTable | 1 | 6 | A table of security configuration parameters and MAC addresses associated with every port with security configured in the concent… |
| 1.3.6.1.4.1.49.2.3.1.5.1.3 | olNetOlSec | 7 | 45 | None |
| 1.3.6.1.4.1.49.2.3.1.5.1.4 | ocNetOCSec | 7 | 48 | None |