This is logical port number.
If we have T1 card then the maximum port number is 192
and if we have E1 card the maximum port number can be 248.
For FRSM-2CT3 card, the maximum port number is 256 and
for unchannelized FRSM-VHS cards (FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI),
the maximum port number is 2
For FRSM-HS2B-12IN1 card, the maximum port number is 8
For FRSM12 card:
The ifIndex of the port's corresponding row in ifTable.
Byte 3 = Chassis Number, Byte 2 = Slot Number,
Byte 1 & 0 = Encoded unique number for Port.
Parsed from file CISCO-WAN-AXIPOP-MIB.mib
Module: CISCO-WAN-AXIPOP-MIB
This is the frame relay(logical) port number.
For Service Modules, supporting ifTable, this
must be the ifIndex value of the frame relay port.
The port number value supported depends upon the
following for each Service Module:
- type(Channelized, Unchannelized, Fractional etc)
of physical line and number of physical lines
- Number of physical line supported
- Limitations due to Service Module Hardware components.
Port Number mapping is as follows:
(NOTE: All the Supported Service Module information is
not provided here).
T1(channelized) : 24 Time Slots * Max #Lines Supported.
Example: 8 Port Service Module - 1..192(24*8)
E1(channelized) : 31 Time Slots * Max #Lines Supported.
Example: 8 Port Service Module - 1..248(31*8)
T3 Channelized :
Example: 2CT3 Service Module: 1-256(Limited by hardware)
Unchannelized VHS : Range is 1-2
(T3/E3/HS2/T3B/E3B/HS2B-HSSI)
FRSM-HS2B-12IN1 : Range is 1-8
FRSM-12 : same as ifIndex value.
With the above convention, Port Number mapping
is as follows:
T1 Service Module : Range is 1-192.
E1 Service Module : Range is 1-248.
2CT3 Service Module : Range is 1-256
NOTE:
For other Service Modules(Where ifTable is supported):
This value for this object must be same as the
ifIndex value for the frame relay port ifTable.
The frame relay ports identified by ifType values
frameRelayService(44) and frForward(158) are
valid for this object.
Since, Frame Relay Port table is used for creating
entries in ifTable, it sounds odd to specify ifIndex
value for this object, even before creating the
ifTable entries!.
The reason(s) for this is as follows:
- There are tables in other frame relay mibs,
which are indexed by auxiliary objects(objects
which are both specified in the INDEX clause
and columnar objects of the same row) whose
value is supposed to be same as 'portNum'.
These MIBs have been used earlier by NMS Applications
for the other product lines(MGX8250, MGX8220 etc).
- The same frame relay tables in used in other
products has been decided to use in new
products(for example MGX8850 with FRSM-12 Service Module).
It is a requirement that ifTable must be supported
in New Service Modules.
If we use ifIndex value of the frame relay port
(after creation) in other tables(FR Port Stats, FR R
Resource Partition or FR Connection etc), and if ifIndex
value is different than 'portNum', then it will
break the NMS applications which have been
using this MIB with the assumptions that 'portNum'
and INDEXes(For example: frResPartPortNum,
lmiCnfPortNum, etc) are same.
To avoid this confusion, it is required that
'portNum' value must be same as 'ifIndex' of
the frame relay port.
This is the frame relay(logical) port number.
For Service Modules, supporting ifTable, this
must be the ifIndex value of the frame relay port.
The port number value supported depends upon the
following for each Service Module:
- type(Channelized, Unchannelized, Fractional etc)
of physical line and number of physical lines
- Number of physical line supported
- Limitations due to Service Module Hardware components.
Port Number mapping is as follows:
(NOTE: All the Supported Service Module information is
not provided here).
T1(channelized) : 24 Time Slots * Max #Lines Supported.
Example: 8 Port Service Module - 1..192(24*8)
E1(channelized) : 31 Time Slots * Max #Lines Supported.
Example: 8 Port Service Module - 1..248(31*8)
T3 Channelized :
Example: 2CT3 Service Module: 1-256(Limited by hardware)
Unchannelized VHS : Range is 1-2
(T3/E3/HS2/T3B/E3B/HS2B-HSSI)
FRSM-HS2B-12IN1 : Range is 1-8
FRSM-12 : same as ifIndex value.
With the above convention, Port Number mapping
is as follows:
T1 Service Module : Range is 1-192.
E1 Service Module : Range is 1-248.
2CT3 Service Module : Range is 1-256
NOTE:
For other Service Modules(Where ifTable is supported):
This value for this object must be same as the
ifIndex value for the frame relay port ifTable.
The frame relay ports identified by ifType values
frameRelayService(44) and frForward(158) are
valid for this object.
Since, Frame Relay Port table is used for creating
entries in ifTable, it sounds odd to specify ifIndex
value for this object, even before creating the
ifTable entries!.
The reason(s) for this is as follows:
- There are tables in other frame relay mibs,
which are indexed by auxiliary objects(objects
which are both specified in the INDEX clause
and columnar objects of the same row) whose
value is supposed to be same as 'portNum'.
These MIBs have been used earlier by NMS Applications
for the other product lines(MGX8250, MGX8220 etc).
- The same frame relay tables in used in other
products has been decided to use in new
products(for example MGX8850 with FRSM-12 Service Module).
It is a requirement that ifTable must be supported
in New Service Modules.
If we use ifIndex value of the frame relay port
(after creation) in other tables(FR Port Stats, FR R
Resource Partition or FR Connection etc), and if ifIndex
value is different than 'portNum', then it will
break the NMS applications which have been
using this MIB with the assumptions that 'portNum'
and INDEXes(For example: frResPartPortNum,
lmiCnfPortNum, etc) are same.
To avoid this confusion, it is required that
'portNum' value must be same as 'ifIndex' of
the frame relay port.
Parsed from file CISCO-WAN-FR-PORT-MIB.my.txt
Company: None
Module: CISCO-WAN-FR-PORT-MIB
This is the frame relay(logical) port number.
For Service Modules, supporting ifTable, this
must be the ifIndex value of the frame relay port.
The port number value supported depends upon the
following for each Service Module:
- type(Channelized, Unchannelized, Fractional etc)
of physical line and number of physical lines
- Number of physical line supported
- Limitations due to Service Module Hardware components.
Port Number mapping is as follows:
(NOTE: All the Supported Service Module information is
not provided here).
T1(channelized) : 24 Time Slots * Max #Lines Supported.
Example: 8 Port Service Module - 1..192(24*8)
E1(channelized) : 31 Time Slots * Max #Lines Supported.
Example: 8 Port Service Module - 1..248(31*8)
T3 Channelized :
Example: 2CT3 Service Module: 1-256(Limited by hardware)
Unchannelized VHS : Range is 1-2
(T3/E3/HS2/T3B/E3B/HS2B-HSSI)
FRSM-HS2B-12IN1 : Range is 1-8
FRSM-12 : same as ifIndex value.
With the above convention, Port Number mapping
is as follows:
T1 Service Module : Range is 1-192.
E1 Service Module : Range is 1-248.
2CT3 Service Module : Range is 1-256
NOTE:
For other Service Modules(Where ifTable is supported):
This value for this object must be same as the
ifIndex value for the frame relay port ifTable.
The frame relay ports identified by ifType values
frameRelayService(44) and frForward(158) are
valid for this object.
Since, Frame Relay Port table is used for creating
entries in ifTable, it sounds odd to specify ifIndex
value for this object, even before creating the
ifTable entries!.
The reason(s) for this is as follows:
- There are tables in other frame relay mibs,
which are indexed by auxiliary objects(objects
which are both specified in the INDEX clause
and columnar objects of the same row) whose
value is supposed to be same as 'portNum'.
These MIBs have been used earlier by NMS Applications
for the other product lines(MGX8250, MGX8220 etc).
- The same frame relay tables in used in other
products has been decided to use in new
products(for example MGX8850 with FRSM-12 Service Module).
It is a requirement that ifTable must be supported
in New Service Modules.
If we use ifIndex value of the frame relay port
(after creation) in other tables(FR Port Stats, FR R
Resource Partition or FR Connection etc), and if ifIndex
value is different than 'portNum', then it will
break the NMS applications which have been
using this MIB with the assumptions that 'portNum'
and INDEXes(For example: frResPartPortNum,
lmiCnfPortNum, etc) are same.
To avoid this confusion, it is required that
'portNum' value must be same as 'ifIndex' of
the frame relay port.
portNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "This is logical port number. If we have T1 card then the maximum port number is 192 and if we have E1 card the maximum port number can be 248. For FRSM-2CT3 card, the maximum port number is 256 and for unchannelized FRSM-VHS cards (FRSM-T3/E3/HS2/T3B/E3B/HS2B-HSSI), the maximum port number is 2 For FRSM-HS2B-12IN1 card, the maximum port number is 8 For FRSM12 card: The ifIndex of the port's corresponding row in ifTable. Byte 3 = Chassis Number, Byte 2 = Slot Number, Byte 1 & 0 = Encoded unique number for Port. " ::= { frPortCnfPortGrpEntry 1}
portNum OBJECT-TYPE SYNTAX INTEGER(1..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION "This is the frame relay(logical) port number. For Service Modules, supporting ifTable, this must be the ifIndex value of the frame relay port. The port number value supported depends upon the following for each Service Module: - type(Channelized, Unchannelized, Fractional etc) of physical line and number of physical lines - Number of physical line supported - Limitations due to Service Module Hardware components. Port Number mapping is as follows: (NOTE: All the Supported Service Module information is not provided here). T1(channelized) : 24 Time Slots * Max #Lines Supported. Example: 8 Port Service Module - 1..192(24*8) E1(channelized) : 31 Time Slots * Max #Lines Supported. Example: 8 Port Service Module - 1..248(31*8) T3 Channelized : Example: 2CT3 Service Module: 1-256(Limited by hardware) Unchannelized VHS : Range is 1-2 (T3/E3/HS2/T3B/E3B/HS2B-HSSI) FRSM-HS2B-12IN1 : Range is 1-8 FRSM-12 : same as ifIndex value. With the above convention, Port Number mapping is as follows: T1 Service Module : Range is 1-192. E1 Service Module : Range is 1-248. 2CT3 Service Module : Range is 1-256 NOTE: For other Service Modules(Where ifTable is supported): This value for this object must be same as the ifIndex value for the frame relay port ifTable. The frame relay ports identified by ifType values frameRelayService(44) and frForward(158) are valid for this object. Since, Frame Relay Port table is used for creating entries in ifTable, it sounds odd to specify ifIndex value for this object, even before creating the ifTable entries!. The reason(s) for this is as follows: - There are tables in other frame relay mibs, which are indexed by auxiliary objects(objects which are both specified in the INDEX clause and columnar objects of the same row) whose value is supposed to be same as 'portNum'. These MIBs have been used earlier by NMS Applications for the other product lines(MGX8250, MGX8220 etc). - The same frame relay tables in used in other products has been decided to use in new products(for example MGX8850 with FRSM-12 Service Module). It is a requirement that ifTable must be supported in New Service Modules. If we use ifIndex value of the frame relay port (after creation) in other tables(FR Port Stats, FR R Resource Partition or FR Connection etc), and if ifIndex value is different than 'portNum', then it will break the NMS applications which have been using this MIB with the assumptions that 'portNum' and INDEXes(For example: frResPartPortNum, lmiCnfPortNum, etc) are same. To avoid this confusion, it is required that 'portNum' value must be same as 'ifIndex' of the frame relay port. " REFERENCE "CISCO-MGX8800-IF-MAPPING-MIB.my to get the ifIndex value of a port even before it appears in ifTable." ::= { frPortCnfPortGrpEntry 1 }
Vendor: Stratacom
Module: CISCO-WAN-AXIPOP-MIB
[Automatically extracted from oidview.com]
portNum OBJECT-TYPE SYNTAX Integer32(1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This is the frame relay(logical) port number. For Service Modules, supporting ifTable, this must be the ifIndex value of the frame relay port. The port number value supported depends upon the following for each Service Module: - type(Channelized, Unchannelized, Fractional etc) of physical line and number of physical lines - Number of physical line supported - Limitations due to Service Module Hardware components. Port Number mapping is as follows: (NOTE: All the Supported Service Module information is not provided here). T1(channelized) : 24 Time Slots * Max #Lines Supported. Example: 8 Port Service Module - 1..192(24*8) E1(channelized) : 31 Time Slots * Max #Lines Supported. Example: 8 Port Service Module - 1..248(31*8) T3 Channelized : Example: 2CT3 Service Module: 1-256(Limited by hardware) Unchannelized VHS : Range is 1-2 (T3/E3/HS2/T3B/E3B/HS2B-HSSI) FRSM-HS2B-12IN1 : Range is 1-8 FRSM-12 : same as ifIndex value. With the above convention, Port Number mapping is as follows: T1 Service Module : Range is 1-192. E1 Service Module : Range is 1-248. 2CT3 Service Module : Range is 1-256 NOTE: For other Service Modules(Where ifTable is supported): This value for this object must be same as the ifIndex value for the frame relay port ifTable. The frame relay ports identified by ifType values frameRelayService(44) and frForward(158) are valid for this object. Since, Frame Relay Port table is used for creating entries in ifTable, it sounds odd to specify ifIndex value for this object, even before creating the ifTable entries!. The reason(s) for this is as follows: - There are tables in other frame relay mibs, which are indexed by auxiliary objects(objects which are both specified in the INDEX clause and columnar objects of the same row) whose value is supposed to be same as 'portNum'. These MIBs have been used earlier by NMS Applications for the other product lines(MGX8250, MGX8220 etc). - The same frame relay tables in used in other products has been decided to use in new products(for example MGX8850 with FRSM-12 Service Module). It is a requirement that ifTable must be supported in New Service Modules. If we use ifIndex value of the frame relay port (after creation) in other tables(FR Port Stats, FR R Resource Partition or FR Connection etc), and if ifIndex value is different than 'portNum', then it will break the NMS applications which have been using this MIB with the assumptions that 'portNum' and INDEXes(For example: frResPartPortNum, lmiCnfPortNum, etc) are same. To avoid this confusion, it is required that 'portNum' value must be same as 'ifIndex' of the frame relay port. " REFERENCE "CISCO-MGX8800-IF-MAPPING-MIB.my to get the ifIndex value of a port even before it appears in ifTable." ::= { frPortCnfPortGrpEntry 1}
portNum OBJECT-TYPE SYNTAX Integer32(1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This is the frame relay(logical) port number. For Service Modules, supporting ifTable, this must be the ifIndex value of the frame relay port. The port number value supported depends upon the following for each Service Module: - type(Channelized, Unchannelized, Fractional etc) of physical line and number of physical lines - Number of physical line supported - Limitations due to Service Module Hardware components. Port Number mapping is as follows: (NOTE: All the Supported Service Module information is not provided here). T1(channelized) : 24 Time Slots * Max #Lines Supported. Example: 8 Port Service Module - 1..192(24*8) E1(channelized) : 31 Time Slots * Max #Lines Supported. Example: 8 Port Service Module - 1..248(31*8) T3 Channelized : Example: 2CT3 Service Module: 1-256(Limited by hardware) Unchannelized VHS : Range is 1-2 (T3/E3/HS2/T3B/E3B/HS2B-HSSI) FRSM-HS2B-12IN1 : Range is 1-8 FRSM-12 : same as ifIndex value. With the above convention, Port Number mapping is as follows: T1 Service Module : Range is 1-192. E1 Service Module : Range is 1-248. 2CT3 Service Module : Range is 1-256 NOTE: For other Service Modules(Where ifTable is supported): This value for this object must be same as the ifIndex value for the frame relay port ifTable. The frame relay ports identified by ifType values frameRelayService(44) and frForward(158) are valid for this object. Since, Frame Relay Port table is used for creating entries in ifTable, it sounds odd to specify ifIndex value for this object, even before creating the ifTable entries!. The reason(s) for this is as follows: - There are tables in other frame relay mibs, which are indexed by auxiliary objects(objects which are both specified in the INDEX clause and columnar objects of the same row) whose value is supposed to be same as 'portNum'. These MIBs have been used earlier by NMS Applications for the other product lines(MGX8250, MGX8220 etc). - The same frame relay tables in used in other products has been decided to use in new products(for example MGX8850 with FRSM-12 Service Module). It is a requirement that ifTable must be supported in New Service Modules. If we use ifIndex value of the frame relay port (after creation) in other tables(FR Port Stats, FR R Resource Partition or FR Connection etc), and if ifIndex value is different than 'portNum', then it will break the NMS applications which have been using this MIB with the assumptions that 'portNum' and INDEXes(For example: frResPartPortNum, lmiCnfPortNum, etc) are same. To avoid this confusion, it is required that 'portNum' value must be same as 'ifIndex' of the frame relay port. " REFERENCE "CISCO-MGX8800-IF-MAPPING-MIB.my to get the ifIndex value of a port even before it appears in ifTable." ::= { frPortCnfPortGrpEntry 1}
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.2 | portLineNum | 0 | 0 | This represents the line number For FRSM12 card: The ifIndex of the physical line on which this port is provisioned. |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.3 | portRowStatus | 0 | 0 | This variable enables or modifies the port 1- add 2 - del 3 - mod For FRSM12 card: For Snmp GET operations, only mod is returned. |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.4 | portDs0ConfigBitMap | 0 | 0 | This respesents bit map of DS0s for a line which are used to form this logical port. Bit 0 represents DS0-1. This entry is not use… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.5 | portDs0Speed | 0 | 0 | This represents port speed of 64 or 56 1 - speed56k 2 - speed64k 3 - unUsed. This field is not used for unchannelised FRSM-VHS (FRS… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.6 | portFlagsBetweenFrames | 0 | 0 | Number of flags transmitted between FR frames For FRSM12 card: Only the values 1 to 8 are supported. The mapping is as follows: MI… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.7 | portEqueueServiceRatio | 0 | 0 | Number of times queue 1 is serviced for every time queue 2 is serviced. The value 0 is supported only by FRSM-VHS. FRSM-VHS suppo… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.8 | portSpeed | 0 | 0 | Configured speed of port in kbps |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.9 | portAdmin | 0 | 0 | used to up and down the port For FRSM12 card: This variable will be equivalent to ifAdminStatus of of ifTable. The write-only is … |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.10 | portType | 0 | 0 | This represents port type For FRSM12 card: frFUNI not Applicable. For frame-relay the ifType is frameRelayService(44) and for fram… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.11 | portSvcStatus | 0 | 0 | This represents SVC status For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.12 | portSvcInUse | 0 | 0 | This represents port svc in use For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.13 | portSvcShareLcn | 0 | 0 | This represents port type For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.14 | portSvcLcnLow | 0 | 0 | This represents low end of reserved LCN for svc For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.15 | portSvcLcnHigh | 0 | 0 | This represents high end of reserved LCN for svc For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.16 | portSvcDlciLow | 0 | 0 | This represents low end of reserved DLCI for svc For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.17 | portSvcDlciHigh | 0 | 0 | This represents high end of reserved DLCI for svc For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.18 | portDeleteSvcs | 0 | 0 | Setting this object to 1 indicates that all the SVC connections on the given port has to be deleted For FRSM12 card: Not Supporte… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.19 | portIngrSvcBandW | 0 | 0 | This represents Ingress Bandwidth reserve for SVC For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.20 | portEgrSvcBandW | 0 | 0 | This represents Egress Bandwidth reserve for SVC For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.21 | portBERTEnable | 0 | 0 | This variable enables BERT For FRSM12 card: Not Supported |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.22 | portEnhancedSIW | 0 | 0 | This variable enables/disables enhanced SIW feature. Enabling this permits support for SIW translation of Appletalk. This feature… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.23 | portM32EgrQueueThresh | 0 | 0 | This represents the M32 logical port Egress Queue threshold in bytes. Frames will not be queued until the number of bytes in the … |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.24 | portHeaderLen | 0 | 0 | This object is added for FRSM12. The value of this object identifies the Q.922 Address field length and DLCI length for this UNI/N… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.25 | portFrameChkSumType | 0 | 0 | This object is added for FRSM12. The value of this object identifies the CRC Length in the HDLC Packet. Applicable for FrameForwa… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.26 | portFileId | 0 | 0 | The ID of the SCT file that holds module specific configuration parameters for this FR virtual interface. This object is not app… |
1.3.6.1.4.1.351.110.5.1.1.1.1.1.1.27 | portOverSubEnable | 0 | 0 | The value of this object enables/disables the port to be over subscribed. This object is not applicable to MGX Release 1.x. |