PEA-EQUIPMENT

File: PEA-EQUIPMENT.mib (120915 bytes)

Imported modules

PEA-SMI PEM-STANDARD SNMPv2-TC
IF-MIB SNMPv2-SMI SNMPv2-CONF

Imported symbols

pea managedObjectClass managedObjectInstance
sequenceNumber perceivedSeverity eventTime
eventTypePem probableCause TruthValue
DisplayString MacAddress TEXTUAL-CONVENTION
InterfaceIndex ifIndex MODULE-IDENTITY
OBJECT-TYPE NOTIFICATION-TYPE Integer32
Unsigned32 IpAddress OBJECT-GROUP
NOTIFICATION-GROUP

Defined Types

PhyModeType  
Represent the Ethernet PHY Mode.
TEXTUAL-CONVENTION    
  OCTET STRING Size(1)  

PeaMultilinkInterfaceEntry  
SEQUENCE    
  peaMultilinkInterfaceIndex InterfaceIndex
  peaMultilinkIsForwarding TruthValue
  peaMultilinkIsUp TruthValue

Defined Values

peaEquipment 1.3.6.1.4.1.193.72.600.1
The public ethernet access software supports a number of standard and proprietary MIBs. This MIB module defines objects for reading/writing common equipment information.
MODULE-IDENTITY    

commonObjects 1.3.6.1.4.1.193.72.600.1.1
OBJECT IDENTIFIER    

commonTraps 1.3.6.1.4.1.193.72.600.1.2
OBJECT IDENTIFIER    

traps 1.3.6.1.4.1.193.72.600.1.2.0
OBJECT IDENTIFIER    

trapsParameters 1.3.6.1.4.1.193.72.600.1.2.1
OBJECT IDENTIFIER    

versions 1.3.6.1.4.1.193.72.600.1.1.1
OBJECT IDENTIFIER    

mainProcessor 1.3.6.1.4.1.193.72.600.1.1.2
OBJECT IDENTIFIER    

temperature 1.3.6.1.4.1.193.72.600.1.1.3
OBJECT IDENTIFIER    

fansStatus 1.3.6.1.4.1.193.72.600.1.1.4
OBJECT IDENTIFIER    

alarmFilter 1.3.6.1.4.1.193.72.600.1.1.5
OBJECT IDENTIFIER    

configurationData 1.3.6.1.4.1.193.72.600.1.1.6
OBJECT IDENTIFIER    

upgradeSW 1.3.6.1.4.1.193.72.600.1.1.7
OBJECT IDENTIFIER    

identificationData 1.3.6.1.4.1.193.72.600.1.1.15
OBJECT IDENTIFIER    


deviceIdData 1.3.6.1.4.1.193.72.600.1.1.15.1
OBJECT IDENTIFIER    

microProcessorIdData 1.3.6.1.4.1.193.72.600.1.1.15.2
OBJECT IDENTIFIER    

analogueFrontEndIdData 1.3.6.1.4.1.193.72.600.1.1.15.3
OBJECT IDENTIFIER    

dcDcConverterIdData 1.3.6.1.4.1.193.72.600.1.1.15.4
OBJECT IDENTIFIER    

ifObjects 1.3.6.1.4.1.193.72.600.1.5
OBJECT IDENTIFIER    

ifNotifications 1.3.6.1.4.1.193.72.600.1.6
OBJECT IDENTIFIER    

ifNotificationTypes 1.3.6.1.4.1.193.72.600.1.6.0
OBJECT IDENTIFIER    

peaEquipmentMibGroups 1.3.6.1.4.1.193.72.600.1.7
OBJECT IDENTIFIER    

snmpv2Notifications 1.3.6.1.4.1.193.72.600.1.8
OBJECT IDENTIFIER    

snmpv2NotificationsTypes 1.3.6.1.4.1.193.72.600.1.8.0
OBJECT IDENTIFIER    

bridgeNotifications 1.3.6.1.4.1.193.72.600.1.9
OBJECT IDENTIFIER    

bridgeNotificationsTypes 1.3.6.1.4.1.193.72.600.1.9.0
OBJECT IDENTIFIER    

rmonNotifications 1.3.6.1.4.1.193.72.600.1.10
OBJECT IDENTIFIER    

rmonNotificationsTypes 1.3.6.1.4.1.193.72.600.1.10.0
OBJECT IDENTIFIER    

sysId 1.3.6.1.4.1.193.72.600.1.1.1.1
This value includes the full name and version identification of the node software.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

bootSwId 1.3.6.1.4.1.193.72.600.1.1.1.2
This value includes the full name and version identification of the BOOT software.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

cfgVer 1.3.6.1.4.1.193.72.600.1.1.1.3
The CfgVer will initially be zero, but is set to the version number defined in the configuration file received from the tftp server at system start-up. The management system may use this version number to verify that the unit contains the correct configuration parameter values. The management system may update the version number when configuration parameters are modified.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

activeSwInfo 1.3.6.1.4.1.193.72.600.1.1.1.4
This value represents the software version of the active software part of the node.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

passiveSwInfo 1.3.6.1.4.1.193.72.600.1.1.1.5
This value represents the software version of the passive software part of the node.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

processorLoad 1.3.6.1.4.1.193.72.600.1.1.2.1
The percentage of time that the main processor was not idle. Average over 10 seconds. (almost like hrProcessorLoad in RFC1514).
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32 0..100  

memFree 1.3.6.1.4.1.193.72.600.1.1.2.2
The amount of free memory on main processor in percent.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32 0..100  

memFreeBytes 1.3.6.1.4.1.193.72.600.1.1.2.3
The amount of free memory on main processor in bytes.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

memBuffersUsed 1.3.6.1.4.1.193.72.600.1.1.2.4
The total number of memory buffers currently used (Ethernet, ATM & local IP-stack).
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

tempControlState 1.3.6.1.4.1.193.72.600.1.1.3.1
The state of the temperature control can be: 0 - Low 1 - Normal 2 - High 3 - TooHigh
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER low(0), normal(1), high(2), tooHigh(3)  

tempValue 1.3.6.1.4.1.193.72.600.1.1.3.2
The temperature value in the node in deg. Celsius.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..150  

greenFanStatus 1.3.6.1.4.1.193.72.600.1.1.4.1
The status of the fan which is placed closest to the green LED. For ESN310/ECN320/ECN330, green fan is the fan placed near the front. Made deprecated. Use the greenFanPerfStatus parameter instead.
Status: deprecated Access: read-only
OBJECT-TYPE    
  INTEGER failed(0), working(1)  

redFanStatus 1.3.6.1.4.1.193.72.600.1.1.4.2
The status of the fan which is placed closest to the red LED. For ESN310/ECN320/ECN330, red fan is the fan placed near the rear. Made deprecated. Use the redFanPerfStatus parameter instead.
Status: deprecated Access: read-only
OBJECT-TYPE    
  INTEGER failed(0), working(1)  

greenFanSpeed 1.3.6.1.4.1.193.72.600.1.1.4.3
The speed of the fan, which is placed closest to the green LED, measured in rpm (revolutions per minute). For ESN310/ECN320/ECN330, green fan is the fan placed near the front.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

redFanSpeed 1.3.6.1.4.1.193.72.600.1.1.4.4
The speed of the fan, which is placed closest to the red LED, measured in rpm (revolutions per minute). For ESN310/ECN320/ECN330, red fan is the fan placed near the rear.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

greenFanPerfStatus 1.3.6.1.4.1.193.72.600.1.1.4.5
The performance status of the fan which is placed closest to the green LED. For ESN310/ECN320/ECN330, green fan is the fan placed near the front.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER failed(1), poor(2), good(3)  

redFanPerfStatus 1.3.6.1.4.1.193.72.600.1.1.4.6
The performance status of the fan which is placed closest to the red LED. For ESN310/ECN320/ECN330, red fan is the fan placed near the rear.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER failed(1), poor(2), good(3)  

hideInternalInterfaces 1.3.6.1.4.1.193.72.600.1.1.8
The management system can chose to hide all interfaces (RFC1233/RFC2233) that are irrelevant in the PEM network view (HP OpenView issue). If 0, Don't hide any interfaces. If 1, Hide internal interfaces (for example loopback and ATM interfaces).
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER off(0), on(1)  

restart 1.3.6.1.4.1.193.72.600.1.1.9
When set to 'restart' the node restarts, which includes loading the SW image and configuration data from the server. In this way a new SW version can be loaded and/or the configu- ration data can be updated.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER restart(1)  


startCfgVerification 1.3.6.1.4.1.193.72.600.1.1.11
When startCfgVerification is set to verify(1) the node makes a DHCP renew and retrieves the configuration file from the address of the server just received from DHCP. The parameters contained in the configuration file overwrites the current settings. The status of the last issued verification can be read out by reading this MIB variable.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER success(0), verify(1), verificationInProgress(2), noAnswerFromDHCP(3), noAnswerFromTFTP(4)  

saveCfgToNvm 1.3.6.1.4.1.193.72.600.1.1.12
When saveCfgToNvm is set to start(1) the device saves the configuration data parameters to NVM. Using GET command the current (inProgress) or last known state (success or failure) are displayed.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER success(0), start(1), saveInProgress(2), failure(3)  

cfgVerificationInterval 1.3.6.1.4.1.193.72.600.1.1.13
This is the time in minutes between configuration file verification. If the value is zero the configuration verification is disabled.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

notifyType 1.3.6.1.4.1.193.72.600.1.1.14
Set the type of the notify sent by the node: 1. Trap 2. Inform
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER trap(1), inform(2)  

sntpServerIP 1.3.6.1.4.1.193.72.600.1.1.16
The IP address of SNTP server used for time synchronization.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

snmpKeepAliveTimerTime 1.3.6.1.4.1.193.72.600.1.1.17
The interval between SNMP KeepAlive checks.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

allowBroadcastToDux 1.3.6.1.4.1.193.72.600.1.1.18
Enables/disables broadcast to DUX (broadcast beacons). When the IP DSLAM is restarted one broadcast to DUX is always sent, hereafter allowBroadcastToDux determines whether broadcast to DUX are sent on a regular basis. In default settings the broadcast to DUX is enabled. Note: It is not recommended to disable broadcast to DUX because it might result in reboot of EDA nodes due to expire of the 'Keep-alive Timer'. For more details consult the Users Guide.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER false(0), true(1)  

comboConnector 1.3.6.1.4.1.193.72.600.1.1.21
Tell if a combo connector is mounted for this board.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER mounted(1), notMounted(2)  

blockUnit 1.3.6.1.4.1.193.72.600.1.1.22
Block this unit. When blocked: - no user traffic is carried out - no alarms are issued - it does not allow any configuration Getting a card out of blocked state can be done by either sending a restart request to it (MIB or Reset-On-Lan) or by dismouting and mounting it again. Setting state to unblock will be ignored.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER block(1), unblock(2)  

comAlarmFilter 1.3.6.1.4.1.193.72.600.1.1.5.1
This alarm filter will filter out all communication alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER warning(0), minor(1), major(2), critical(3)  

envAlarmFilter 1.3.6.1.4.1.193.72.600.1.1.5.2
This alarm filter will filter out all environment alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER warning(0), minor(1), major(2), critical(3)  

equipAlarmFilter 1.3.6.1.4.1.193.72.600.1.1.5.3
This alarm filter will filter out all equipment alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER warning(0), minor(1), major(2), critical(3)  

processAlarmFilter 1.3.6.1.4.1.193.72.600.1.1.5.4
This alarm filter will filter out all processing alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER warning(0), minor(1), major(2), critical(3)  

qosAlarmFilter 1.3.6.1.4.1.193.72.600.1.1.5.5
This alarm filter will filter out all quality alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER warning(0), minor(1), major(2), critical(3)  

alarmFilterThres 1.3.6.1.4.1.193.72.600.1.1.5.6
The threshold value indicates how many alarms that can be filtered by the node in the time interval indicated by the alarmFilterInterval parameter before an alarm is sent. If set to 0, the functionality is disabled.
Status: obsolete Access: read-write
OBJECT-TYPE    
  Unsigned32  

alarmFilterInterval 1.3.6.1.4.1.193.72.600.1.1.5.7
The value of this parameter indicates the time interval in which the node can filter a number of alarms indicated by the alarmFilterThres parameter before an alarm is sent. If set to 0, the functionality is disabled.
Status: obsolete Access: read-write
OBJECT-TYPE    
  Unsigned32  

localMacAddr 1.3.6.1.4.1.193.72.600.1.1.6.1
Unique MAC address of the node.
Status: current Access: read-only
OBJECT-TYPE    
  MacAddress  

phyMode 1.3.6.1.4.1.193.72.600.1.1.6.2
Ethernet PHY Mode setting. The Phy Mode is coded as a bitfield: * Bit 0: Auto-negotiation. If set, auto-negotiation is OFF else ON. * Bit 2: Full Duplex control. If set, full duplex operation is NOT allowed. * Bit 3: 100 Mbit/s control. If set, 100 Mbit/s operation is NOT allowed. * Bit 4: Half Duplex control. If set, half duplex operation is NOT allowed * Bit 5: 10 Mbit/s control. If set, 10 Mbit/s operation is NOT allowed. Examples of PHY Mode values: * 0x00: Full auto-negotiation. * 0x20: 100 Mbit/s only. Auto-negotiation between half & full duplex. * 0x31: Fixed 100 Mbit/s, full duplex only operation. * 0x25: Fixed 100 Mbit/s, half duplex only operation
Status: current Access: read-write
OBJECT-TYPE    
  PhyModeType  

watchDogEnable 1.3.6.1.4.1.193.72.600.1.1.6.3
Enabling of the HW Watchdog. If 0 (zero), the watchdog is OFF, else the watchdog is ON.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER off(0), on(1)  

vlanId 1.3.6.1.4.1.193.72.600.1.1.6.5
The VLAN ID setting for the management VLAN.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32 0..4095  

vlanPrio 1.3.6.1.4.1.193.72.600.1.1.6.6
Specifies the IEEE 802.1Q priority used for the management VLAN.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32 0..7  

vlanTagging 1.3.6.1.4.1.193.72.600.1.1.6.7
If 0, VLAN tagging is off, meaning that VLAN is not used. If 1, VLAN tagging is used, with the given ID and Prio.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER off(0), on(1)  

bootString 1.3.6.1.4.1.193.72.600.1.1.6.8
Text commands for the bootloader.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..255)  

swFileName 1.3.6.1.4.1.193.72.600.1.1.7.1
The filename to upload to the node. The path to this file is in the root directory that is specified in the FTP server
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString  

uploadSW 1.3.6.1.4.1.193.72.600.1.1.7.2
Upload new application software to device. The file which is loaded is indicated by the swFileName parameter. 1 - upload SW to the device and restart afterwards. 2 - upload SW to the device without restarting. Using GET command the current (inProgress) or last known state (success or failure) are displayed.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER success(0), uploadSwWithRestart(1), uploadSwWithoutRestart(2), uploadInProgress(3), failure(4)  

bootSwFileName 1.3.6.1.4.1.193.72.600.1.1.7.3
The filename of a boot sw image located on the domain file server. This file name is used by the uploadBootSw.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString  

uploadBootSw 1.3.6.1.4.1.193.72.600.1.1.7.4
Upload new boot software to this device. The boot sw image must be named by the bootSwFileName parameter and located on the domain file server, which is the next-server in the DHCP offer. Using GET command the current (inProgress) or last known state (success or failure) are displayed.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER success(0), start(1), uploadInProgress(2), failure(3)  

productNumber 1.3.6.1.4.1.193.72.600.1.1.15.1.1
Index number that identifies the node.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..24)  

revisionState 1.3.6.1.4.1.193.72.600.1.1.15.1.2
Revision State or 'R-state' declaring minor versions. For example: different types of components or new boot SW.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..7)  

functionDesignation 1.3.6.1.4.1.193.72.600.1.1.15.1.3
Number with reference to the handling and use of the product.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..12)  

dateOfProduction 1.3.6.1.4.1.193.72.600.1.1.15.1.4
Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

dateOfRepair 1.3.6.1.4.1.193.72.600.1.1.15.1.5
Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

productionSerialNumber 1.3.6.1.4.1.193.72.600.1.1.15.1.6
Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(13)  

layoutVersionCode 1.3.6.1.4.1.193.72.600.1.1.15.1.7
The data layout version that allows the possibility to interpret stored data differently.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

idCheckSum 1.3.6.1.4.1.193.72.600.1.1.15.1.8
CRC32 Checksum of identification data structure of the node.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

productNumberMicroProcessor 1.3.6.1.4.1.193.72.600.1.1.15.2.1
Index number that identifies the MicroProcessor board.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..24)  

revisionStateMicroProcessor 1.3.6.1.4.1.193.72.600.1.1.15.2.2
Revision State or 'R-state' declaring minor versions. For example: different types of components or new boot SW.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..7)  

functionDesignationMicroProcessor 1.3.6.1.4.1.193.72.600.1.1.15.2.3
Number with reference to the handling and use of the product.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..12)  

dateOfProductionMicroProcessor 1.3.6.1.4.1.193.72.600.1.1.15.2.4
Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

dateOfRepairMicroProcessor 1.3.6.1.4.1.193.72.600.1.1.15.2.5
Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

productionSerialNumberMicroProcessor 1.3.6.1.4.1.193.72.600.1.1.15.2.6
Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(13)  

layoutVersionCodeMicroProcessor 1.3.6.1.4.1.193.72.600.1.1.15.2.7
The data layout version that allows the possibility to interpret stored data differently.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

idCheckSumMicroProcessor 1.3.6.1.4.1.193.72.600.1.1.15.2.8
CRC32 Checksum of identification data structure for the MicroProcessor board.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

productNumberAnalogueFrontEnd 1.3.6.1.4.1.193.72.600.1.1.15.3.1
Index number that identifies the AFE board.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..24)  

revisionStateAnalogueFrontEnd 1.3.6.1.4.1.193.72.600.1.1.15.3.2
Revision State or 'R-state' declaring minor versions. For example: different types of components or new boot SW.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..7)  

functionDesignationAnalogueFrontEnd 1.3.6.1.4.1.193.72.600.1.1.15.3.3
Number with reference to the handling and use of the product.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..12)  

dateOfProductionAnalogueFrontEnd 1.3.6.1.4.1.193.72.600.1.1.15.3.4
Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

dateOfRepairAnalogueFrontEnd 1.3.6.1.4.1.193.72.600.1.1.15.3.5
Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

productionSerialNumberAnalogueFrontEnd 1.3.6.1.4.1.193.72.600.1.1.15.3.6
Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(13)  

layoutVersionCodeAnalogueFrontEnd 1.3.6.1.4.1.193.72.600.1.1.15.3.7
The data layout version that allows the possibility to interpret stored data differently.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

idCheckSumAnalogueFrontEnd 1.3.6.1.4.1.193.72.600.1.1.15.3.8
CRC32 Checksum of identification data structure for the Analogue Front End board.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

productNumberDcDcConverter 1.3.6.1.4.1.193.72.600.1.1.15.4.1
Index number that identifies the DC-DC Converter board.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..24)  

revisionStateDcDcConverter 1.3.6.1.4.1.193.72.600.1.1.15.4.2
Revision State or 'R-state' declaring minor versions. For example: different types of components or new boot SW.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..7)  

functionDesignationDcDcConverter 1.3.6.1.4.1.193.72.600.1.1.15.4.3
Number with reference to the handling and use of the product.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(0..12)  

dateOfProductionDcDcConverter 1.3.6.1.4.1.193.72.600.1.1.15.4.4
Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

dateOfRepairDcDcConverter 1.3.6.1.4.1.193.72.600.1.1.15.4.5
Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

productionSerialNumberDcDcConverter 1.3.6.1.4.1.193.72.600.1.1.15.4.6
Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString Size(13)  

layoutVersionCodeDcDcConverter 1.3.6.1.4.1.193.72.600.1.1.15.4.7
The data layout version that allows the possibility to interpret stored data differently.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

idCheckSumDcDcConverter 1.3.6.1.4.1.193.72.600.1.1.15.4.8
CRC32 Checksum of identification data for the DC-DC Converter board.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(4)  

peaMultilinkMode 1.3.6.1.4.1.193.72.600.1.1.20.1
This defines the mode the multiple network-side links operate in. singleLink(1) - only one link is used for active data transfer. This is the only possible value for devices with a single network-side link. linkAggregation(2) - the multiple links are used as one trunk aggregating the traffic. redundantConfiguration(3) - only one of the the multiple links is used for active data transfer, but the other are kept stand by for resilience (uses RSTP protocol). Note: the read value may not match the actual mode during switch over.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER singleLink(1), linkAggregation(2), redundantConfiguration(3)  

peaMultilinkPreferredInterface 1.3.6.1.4.1.193.72.600.1.1.20.2
Shows the index of the interface (link) selected for traffic forwarding whenever there is no other explicit indication on which one to choose. The interface is selected during boot - it is the interface the device was booted from. The value is the same as used for interfaces in the IF-MIB (1-based).
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..2147483646  

peaMultilinkInterfaceTable 1.3.6.1.4.1.193.72.600.1.1.20.3
This is a table of interfaces (links) on the network-side. The table is indexed by the same interface numbers as used in the IF-MIB (1-based).
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    PeaMultilinkInterfaceEntry

peaMultilinkInterfaceEntry 1.3.6.1.4.1.193.72.600.1.1.20.3.1
This is an entry of the multilinkInterfaceTable
Status: current Access: not-accessible
OBJECT-TYPE    
  PeaMultilinkInterfaceEntry  

peaMultilinkInterfaceIndex 1.3.6.1.4.1.193.72.600.1.1.20.3.1.1
This is the index to the multilinkInterfaceTable. The values are the same as used in the IF-MIB (1-based).
Status: current Access: not-accessible
OBJECT-TYPE    
  InterfaceIndex  

peaMultilinkIsForwarding 1.3.6.1.4.1.193.72.600.1.1.20.3.1.2
This shows if the corresponding interface (link) is forwarding traffic - true(1) or not - false(2). An interface that is not forwarding may still carry some service data (e.g. PDUs).
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

peaMultilinkIsUp 1.3.6.1.4.1.193.72.600.1.1.20.3.1.3
This shows if the corresponding interface (link) is up true(1) or down - false(2). The true(1) value is returned if the ifOperState of the corresponding port is up. The false(1) value is returned if the ifOperState of the corresponding port is NOT up (e.g. down, testing, etc.).
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

peaMultilinkForceManagementToUsePreferredInterface 1.3.6.1.4.1.193.72.600.1.1.20.4
Setting this value to 'enabled (1)' forces the management traffic to be sent on the interface towards the Active ECN thereby overruling the RSTP protocol for management traffic towards this node. This enables the node controller to stay in contact with the DSLAM, even if the link is switched to the other interface by RSTP.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

Generation date: July 28, 2023, 16:18:13, Copyright © 2007 - 2022 - Circitor