An MSH chassis is logically comprised of a number of services, e.g. a
repeater, bridge etc. Each service is implemented by one or more
physical entities. This table contains an entry for each service,
providing a name for that service type.
Note that every entry in the physical configuration table MUST belong
to a service. For example there may NOT be an entry in the
phyConfigTable for which the value of phyServiceId does not provide
an index into this table of an existent row.
Parsed from file msh100.mib.txt
Company: None
Module: LBMSH-MIB
An MSH chassis is logically comprised of a number of services, e.g. a
repeater, bridge etc. Each service is implemented by one or more
physical entities. This table contains an entry for each service,
providing a name for that service type.
Note that every entry in the physical configuration table MUST belong
to a service. For example there may NOT be an entry in the
phyConfigTable for which the value of phyServiceId does not provide
an index into this table of an existent row.
Parsed from file LBHUB-MSH-MIB.mib
Module: LBHUB-MSH-MIB
Vendor: 3Com
Module: LBHUB-MSH-MIB (lbhub-msh.mib)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF
Automatically extracted from www.mibdepot.com
serviceTable OBJECT-TYPE SYNTAX SEQUENCE OF ServiceEntry ACCESS not-accessible STATUS mandatory DESCRIPTION " An MSH chassis is logically comprised of a number of services, e.g. a repeater, bridge etc. Each service is implemented by one or more physical entities. This table contains an entry for each service, providing a name for that service type. Note that every entry in the physical configuration table MUST belong to a service. For example there may NOT be an entry in the phyConfigTable for which the value of phyServiceId does not provide an index into this table of an existent row." ::= { logicalConfig 1 }
serviceTable OBJECT-TYPE SYNTAX SEQUENCE OF ServiceEntry ACCESS not-accessible STATUS mandatory DESCRIPTION " An MSH chassis is logically comprised of a number of services, e.g. a repeater, bridge etc. Each service is implemented by one or more physical entities. This table contains an entry for each service, providing a name for that service type. Note that every entry in the physical configuration table MUST belong to a service. For example there may NOT be an entry in the phyConfigTable for which the value of phyServiceId does not provide an index into this table of an existent row." ::= { logicalConfig 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.43.10.14.3.1.1 | serviceEntry | 3 | 3 | This is an entry in the Service Table which is indexed by the Service Index for that service. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.43.10.14.3.2 | addressTable | 1 | 5 | An MSH chassis contains a number of services. Each service is implemented by one or more cards. A number of services are 'intell… |
| 1.3.6.1.4.1.43.10.14.3.3 | facilityTable | 1 | 5 | The MSH chassis can simultaneously maintain a number of different sub-networks. Examples of these are the independent repeaters … |