The port number.
For DXC:
For external ports the convention used will be:
- first two digits will be: (IO slot number+10)
- last one/two digits will be the port number within the
card, in odd numbers:
port1 = 1
port2 = 3
port3 = 5
etc...
Example: port2 of IO slot 11 will be: 213 .
For internal ports the convention used will be:
- first two digits will be: (IO slot number+10)
- last one/two digits will be the port number within the
card, in even numbers:
port1 = 2
port2 = 4
port3 = 6
etc...
Example: port2 of IO slot 11 will be: 214 .
For MP:
For external ports, the value will be as that of the port in the
card. Example: external-3 -> 3
external-4 -> 4
For internal ports, the value will be 100 + the port in the
card. Example: internal-1 -> 101
internal-4 -> 104
For IP Bundles, the value will be the Bundle ifIndex.
For other products - refer to product specification.
100=notApplicable (when Redundancy is at card level).
Parsed from file Rad0485.MIB.txt
Company: None
Module: RAD-MIB
The port number.
For DXC:
For external ports the convention used will be:
- first two digits will be: (IO slot number+10)
- last one/two digits will be the port number within the
card, in odd numbers:
port1 = 1
port2 = 3
port3 = 5
etc...
Example: port2 of IO slot 11 will be: 213 .
For internal ports the convention used will be:
- first two digits will be: (IO slot number+10)
- last one/two digits will be the port number within the
card, in even numbers:
port1 = 2
port2 = 4
port3 = 6
etc...
Example: port2 of IO slot 11 will be: 214 .
For MP:
For external ports, the value will be as that of the port in the
card. Example: external-3 -> 3
external-4 -> 4
For internal ports, the value will be 100 + the port in the
card. Example: internal-1 -> 101
internal-4 -> 104
For IP Bundles, the value will be the Bundle ifIndex.
For other products - refer to product specification.
100=notApplicable (when Redundancy is at card level).
Parsed from file RAD-MIB.mib
Module: RAD-MIB
Vendor: Rad Data Communications Ltd.
Module: DACS-MIB
[Automatically extracted from oidview.com]
sysCRdnSecPort OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The port number. For DXC: For external ports the convention used will be: - first two digits will be: (IO slot number+10) - last one/two digits will be the port number within the card, in odd numbers: port1 = 1 port2 = 3 port3 = 5 etc... Example: port2 of IO slot 11 will be: 213 . For internal ports the convention used will be: - first two digits will be: (IO slot number+10) - last one/two digits will be the port number within the card, in even numbers: port1 = 2 port2 = 4 port3 = 6 etc... Example: port2 of IO slot 11 will be: 214 . For MP: For external ports, the value will be as that of the port in the card. Example: external-3 -> 3 external-4 -> 4 For internal ports, the value will be 100 + the port in the card. Example: internal-1 -> 101 internal-4 -> 104 For IP Bundles, the value will be the Bundle ifIndex. For other products - refer to product specification. 100=notApplicable (when Redundancy is at card level)." ::= { sysCRdnEntry 5 }
sysCRdnSecPort OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The port number. For DXC: For external ports the convention used will be: - first two digits will be: (IO slot number+10) - last one/two digits will be the port number within the card, in odd numbers: port1 = 1 port2 = 3 port3 = 5 etc... Example: port2 of IO slot 11 will be: 213 . For internal ports the convention used will be: - first two digits will be: (IO slot number+10) - last one/two digits will be the port number within the card, in even numbers: port1 = 2 port2 = 4 port3 = 6 etc... Example: port2 of IO slot 11 will be: 214 . For MP: For external ports, the value will be as that of the port in the card. Example: external-3 -> 3 external-4 -> 4 For internal ports, the value will be 100 + the port in the card. Example: internal-1 -> 101 internal-4 -> 104 For IP Bundles, the value will be the Bundle ifIndex. For other products - refer to product specification. 100=notApplicable (when Redundancy is at card level)." ::= { sysCRdnEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.164.3.3.1.6.3.1.1 | sysCRdnCnfgIdx | 0 | 0 | This object indicates the Idx of the Cnfg(1..255) being accessed ; Idx of 255 relates to the TmpCnfg. |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.2 | sysCRdnPrimeSlot | 0 | 0 | The slot number of the Primary card of Redundancy. The Primary card should be the card that user wishes to be the online card (us… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.3 | sysCRdnPrimePort | 0 | 0 | The port number. For DXC: For external ports the convention used will be: - first two digits will be: (IO slot number+10) - last on… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.4 | sysCRdnSecSlot | 0 | 0 | The slot number of the Secondary card of Redundancy matching the Primary slot. |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.6 | sysCRdnMode | 0 | 0 | Redundancy Mode. DXC supports: yCable(3), singleSlotProtection(6) and dualCableParallelTx(4) MP supports: dualCableAIS(2), yCabl… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.7 | sysCRdnRecMode | 0 | 0 | Recovery Mode. This object determines if after recovery of the failed card/port it will become on-line again or not: auto - autom… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.8 | sysCRdnRecTime | 0 | 0 | Redundancy Recovery Time (sec). After switching to the current online card, the next switch can be performed only after a minimum… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.9 | sysCRdnHwSwFlip | 0 | 0 | HW or SW decision for Redundancy Flip. This object is applicable only for sysCRdnMode=singleSlotProtection. HW - decision is by I… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.10 | sysCRdnRowStatus | 0 | 0 | This parameter allows NMS to create/delete entries of this table. The only possible supported RowStatus vaules are active (1) and… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.11 | sysCRdnOnline | 0 | 0 | Status - who is the Online (current) Redundancy Slot/Port. This object shows only the Online Slot/Port regarding the Redundancy.… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.12 | sysCRdnSwitchingMode | 0 | 0 | This object defines which Self Healing Ring (SHR) SDH ring is used: Uni Directional or BiDirectional. The type of the ring is def… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.13 | sysCRdnFlipUponEvent | 0 | 0 | This object allows user to define if Flip to the other port will be performed (or not), for certain possible events. Each event i… |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.14 | sysCRdnLosOrLofTime | 0 | 0 | sysCRdnLosOrLoftime |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.15 | sysCRdnEventsTimeWindow | 0 | 0 | This parameter determines the time window in which to count events to trigger protection switching. For Ipmux time is counted in … |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.16 | sysCRdnSequenceNumberThreshold | 0 | 0 | This parameter determines the number of Sequence Number errors that should occur in the time window in order to cause switching. |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.17 | sysCRdnBufferErrorsThreshold | 0 | 0 | This parameter determines the number of Buffer undeflow/ overflow events occured in the time window that cause switching. |
| 1.3.6.1.4.1.164.3.3.1.6.3.1.18 | sysCRdnBuffUnderrunTime | 0 | 0 | This parameter determines how much time to wait before switching, after jitter buffer underrun. Switching occurs if no frame arri… |