Home/Catalog/TP5000

TP5000

AI MIB Summary

The TP5000 MIB module provides management and monitoring capabilities for the Symmetricom TimeProvider 5000 hardware, enabling the retrieval of precise time synchronization status, clock discipline parameters, and internal sensor telemetry such as temperature and voltage levels.

Symmetricom, Inc. TimeProvider 5000 Device
Main OID:
tp5000.1.3.6.1.4.1.9070.1.2.4.6
545
Objects
Active
Status
5
Dependencies

Imported Objects

IF-MIB
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC
SYMM-SMI

Objects

545 total
Object Name
tp5000Symmetricom, Inc. TimeProvider 5000 Device
MODULE-IDENTITY
.1.3.6.1.4.1.9070.1.2.4.6
inventory
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.1
assetNumInventory asset value is assigned by the user.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.1
ioModuleTypeThe I/O module type installed in the I/O slot.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.2
systemModelThe device model value is read-only. Symmetricom will provide the TP5000 model.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.3
chassisTypeThe chassis type as given by Symmetricom.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.4
inventoryInfoTableA list of inventory of each IMC, IOC1 and IOC2.
SEQUENCE OF InventoryInfoEntry
.1.3.6.1.4.1.9070.1.2.4.6.1.5
inventoryInfoEntryAn inventory entry containing objects of each module inventory management information.
InventoryInfoEntry
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1
invIndexThe inventory index.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.1
invModuleIDThe module ID should be one of imc, ioc1 or ioc2. No default value.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.2
invPartNumberThe current part number is given.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.3
invCLEINumThe current CLEI number is given, if assigned.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.4
invSerialThe current serial number is given.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.5
invHWVersionThe current hardware version is given.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.6
invFPGAVersionThe current FPGA version is given.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.7
invFwVersionThe current firmware version is given.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.8
invSlotThe slot should be the position or location of a module in a chassis.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.9
invCountryOfOriginCountry of Origin of a module in a chassis.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.10
invManufacturerIDManufacturer ID of a module in a chassis.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.5.1.11
compatibilityTableA list of compatibility info of each IMC, IOC1 and IOC2.
SEQUENCE OF CompatibilityEntry
.1.3.6.1.4.1.9070.1.2.4.6.1.6
compatibilityEntryA compatibility entry containing objects of each module compatibility information.
CompatibilityEntry
.1.3.6.1.4.1.9070.1.2.4.6.1.6.1
compatiIndexThe compatibility index.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.1.6.1.1
compatiModuleIDThe module ID should be one of imc, ioc1 or ioc2. No default value.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.1.6.1.2
compatiHWThe HW compatible value is a value to indicate the compatibility with the previous hardware.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.6.1.3
compatiSWThe SW compatible value is a value to indicate the compatibility with the previous software.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.6.1.4
compatiIMCIOCThe IMC-IOC compatibile value is a value to indicate the compatibility between the current IMC and IOC.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.6.1.5
compatiIOCIOCThe IOC-IOC compatibile value is a value to indicate the compatibility between the current IOC1 and IOC2.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.1.6.1.6
status
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2
sysStatus
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2.1
uptimeofIMCThe IMC uptime is defined as the length of time since the IMC booted.ro
TimeTicks UNITS "Second"
.1.3.6.1.4.1.9070.1.2.4.6.2.1.1
dateAndTimeThe date and time is UTC time in the system. The IMC and IOC date and time are shown.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.1.2
numofStandingAlarmThe current number of the standing active alarms in the system.ro
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.1.3
selectedToDSourceThe ToD source. The definition of ToD source is as follow: gps(1), sys(2), ntp(3), ptp(4), uti(5).ro
ToDSource
.1.3.6.1.4.1.9070.1.2.4.6.2.1.4
systemReferenceThe system reference. The definition of reference is as follow: gps(0), port1(1), port2(2), uti1(3), uti2(4)ro
TPReference
.1.3.6.1.4.1.9070.1.2.4.6.2.1.5
servoControlStatusActiveIOCThe servo control status of IOC. This status is also defined as clock status in CLI's show status command. It should be defined as follow: warmup(1), acquire(2), locked(3), holdover(4), freerun(5).ro
TPServoControl
.1.3.6.1.4.1.9070.1.2.4.6.2.1.6
autoSyncThe auto SYNC state. It has the two states: enable(1) and disable(2).ro
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.2.1.7
ledTableThe table of TP5000 front panel LEDs
SEQUENCE OF LedEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.1.8
ledEntryThe entry of led table.
LedEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.1.8.1
ledIndexThe index of led table.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.1.8.1.1
ledModuleIDThe LED module ID should be one of imc, ioc1 or ioc2. This is read-only feild.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.2.1.8.1.2
ledIDThe LED ID. The LED ID is as follows: 1) IMC A-Bus power 2) IMC B-Bus power 3) IMC system 4) IMC alarm 5) IMC GPS 6) IMC management ethernet port 7) IOC active 8) IOC alarm 9) IOC eth1 port 10) IOC eth2 port 11) IOC holdro
TPLEDID
.1.3.6.1.4.1.9070.1.2.4.6.2.1.8.1.3
ledStatusLED status. The LED status is defined as follows: Off(0), On(1), Red(2), Redblink(3), Green(4), Greenblink(5), Amber(6), Amberblink(7)ro
LEDType
.1.3.6.1.4.1.9070.1.2.4.6.2.1.8.1.4
hardwareStatusTableThe table of hardware status of each IMC and IOC module.
SEQUENCE OF HardwareStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.1.9
hardwareStatusEntryThe entry of hardware status table.
HardwareStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.1.9.1
hardwareStatusIndexThe index of hardware status table.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.1.9.1.1
hardwareStatusModuleIDThe hardware status module ID should be one of imc, ioc1 or ioc2. This is read-only feild.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.2.1.9.1.2
hardwareStatusInfoHardware status information. It includes voltages and other information of each sub-system.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.1.9.1.3
uptimeofIOC1The IOC1 uptime is defined as the length of time since IOC1 booted.ro
TimeTicks UNITS "Second"
.1.3.6.1.4.1.9070.1.2.4.6.2.1.10
uptimeofIOC2The IOC2 uptime is defined as the length of time since IOC2 booted.ro
TimeTicks UNITS "Second"
.1.3.6.1.4.1.9070.1.2.4.6.2.1.11
ptpSystemModeOnEth1PTP System Mode on Eth1ro
PTPSystemMode
.1.3.6.1.4.1.9070.1.2.4.6.2.1.12
ptpSystemModeOnEth2PTP Mode: Grandmaster, or Probero
PTPSystemMode
.1.3.6.1.4.1.9070.1.2.4.6.2.1.13
warmupStatusIOC1The IOC1 warmup status.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.1.14
warmupStatusIOC2The IOC2 warmup status.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.1.15
phaseOffsetThe Phase offset in ns between reference and output, only applicable in GPS mode.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.1.16
leapPendingAndleapSecondThe leap pending info and leap second.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.1.17
activeAlarmAndEvent
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2.2
activeAlarmTableThe list of current active alarms of the TP5000 device.
SEQUENCE OF ActiveAlarmEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1
activeAlarmEntryAn alarm entry containing objects of the specified alarm value.
ActiveAlarmEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1.1
activeAlarmIndexThe access index of the active alarm table. The range should be 1~500.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1.1.1
activeAlarmModuleIDThe module ID should be one of SYS, IMC, IOC1 or IOC2. No default value.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1.1.2
activeAlarmIDThis value is the alarm ID. The alarm id definition is defined in the user manual.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1.1.3
activeAlarmInternalIndexThis value is the alarm internal index. The alarm internal index should be defined in user manual.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1.1.4
activeAlarmDateAndTimeThe alarm's date and time stamp.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1.1.5
activeAlarmSeverityThe alarm severity level of the current alarm. The definition is as follows: 2 Critical: critical conditions 3 Major: error conditions 4 Minor: warning conditions 5 Event: normal but significant conditionro
AlarmLevel
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1.1.6
activeAlarmDescThe descriptions of the current active alarm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.2.1.1.7
activeEventTableThe list of current active events of the TP5000 device.
SEQUENCE OF ActiveEventEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.2.2
activeEventEntryAn event entry containing objects of the specified event value.
ActiveEventEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.2.2.1
activeEventIndexThe access index of the active event table. The range should be 1~500.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.2.2.1.1
activeEventModuleIDThe module ID should be one of SYS, IMC, IOC1 or IOC2. No default value.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.2.2.2.1.2
activeEventIDThis value is the event ID. The event ID definition should be defined in user manual.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.2.2.2.1.3
activeEventInternalIndexThis value is the event internal index. The event internal index should be defined in user manual.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.2.2.2.1.4
activeEventDateAndTimeThe active event's date and time stamp.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.2.2.1.5
activeEventDescThe description of the current active event.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.2.2.1.6
networkStatus
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2.3
ipStatusTableThe IP status information table of each port in IMC and IOC modules.
SEQUENCE OF IpStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.3.1
ipStatusEntryThe entry of IP status table.
IpStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.3.1.1
ipStatusIndexThe index of IP status table.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.3.1.1.1
ipStatusModuleIDThe module ID should be one of imc, ioc1 or ioc2. No default value.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.2.3.1.1.2
ipStatusPortIDThe port ID on the module. Note: For IMC, port ID is eth2ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.3.1.1.3
ipStatusHwaddrHW address, type and other info of an ethernet port.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.3.1.1.4
ipStatusNetInfoIP address, mask, gateway and other info of an ethernet portro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.3.1.1.5
ipStatusInfoGeneral operational status of an ethernet portro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.3.1.1.6
ethLinkTableThe Ethernet port link table of the TP5000 device.
SEQUENCE OF EthLinkEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.3.2
ethLinkEntryThe ethernet link table.
EthLinkEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.3.2.1
ethLinkIndexThe index of ethernet link table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.3.2.1.1
ethLinkModuleIDThe module ID of Tp5000 boards. The module is as follows: ioc1(3), ioc2(4)ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.2.3.2.1.2
ethLinkPortIDIP Port ID on each board. The value should be one of eth1(1), eth2(2), none(5)ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.2.3.2.1.3
ethLinkSpeedThe ethernet auto-negotiation speed. The defined speeds are 100M, 1000M, or nonero
AutoSpeedType
.1.3.6.1.4.1.9070.1.2.4.6.2.3.2.1.4
gpsInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2.4
gpsModeGPS position survey modes. They are defined as follows: Auto(1), Manual(2).ro
GPSPosMode
.1.3.6.1.4.1.9070.1.2.4.6.2.4.1
gpsElevationMaskGPS elevation mask. The range is from 0 to 45 degrees.ro
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.4.2
gpsCableDelayThe GPS antenna cable delay. The units are nanosecondsro
Integer32 UNITS "ns"
.1.3.6.1.4.1.9070.1.2.4.6.2.4.3
gpsPositionTableGPS position info.
SEQUENCE OF GpsPositionEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.4.4
gpsPositionEntryThe entry of GPS position table.
GpsPositionEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.4.4.1
gpsPositionIndexThe index of gps position table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.4.4.1.1
gpsPositionLatThe latitude value of GPS position. The format should be as follows: Ndd:mm:ss.ss or Sdd:mm:ss.ssro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.4.4.1.2
gpsPositionLongThe longitude of the GPS position. The format should be as follows: Eddd:mm:ss.ss or Wddd:mm:ss.ssro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.4.4.1.3
gpsPositionHeightThe altitude of GPS position in meters. The format should be as follows: +/-hhhh.hro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.4.4.1.4
gpsSVTableThe tracked satellites table which provides the information about the satellites being tracked .
SEQUENCE OF GpsSVEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.4.5
gpsSVEntryThe entry of the satellites being tracked.
GpsSVEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.4.5.1
gpsIndexThe index of tracked satellites table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.4.5.1.1
gpsSVNumSatellite Vehicle Number - This is the identification number of the satellite being trackedro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.4.5.1.2
gpsSNRSignal to Noise Ratioro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.4.5.1.3
gpsHealthIndicates the health of the satellite. States are as follows: healthy(1), unhealthy(2)ro
GPSHealthy
.1.3.6.1.4.1.9070.1.2.4.6.2.4.5.1.4
gpsAzimuthSatellites horizontal position measured in degrees clockwise from the northro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.4.5.1.5
gpsElevationVertical position of satellite in degrees from the horizonro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.4.5.1.6
ptpStatus
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2.5
commonPtpStatusTableThe PTP common status table
SEQUENCE OF CommonPtpStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1
commonPtpStatusEntryThe entry of common PTP ports
CommonPtpStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1
ptpStatusIndexPTP ports index: 1-4
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.1
ptpStatusModuleIDThe module ID should be one of ioc1 or ioc2. No default value.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.2
ptpStatusPortIDThe PTP port id.ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.3
ptpStatusPortEnableThe PTP port state control flag. The value could be: Enable(1), Disable(2).ro
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.4
ptpStatusClockIDThe clock ID of a PTP port, a 64-bit identifier.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.5
ptpStatusProfilePTP common profile. 0: unicast; 1:Multicast.ro
PTPProfileType
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.6
ptpStatusClockClassThe clock class on a PTP port.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.7
ptpStatusClockAccuracyThe clock accuracy on a PTP portro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.8
ptpStatusTimescaleThe timescale on a PTP port.ro
PTPTimeScaleValue
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.9
ptpStatusNumClientThe number of clients on a PTP port.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.10
ptpStatusClientLoadThe percentage of client load on a PTP port.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.11
ptpStatusPacketLoadThe percentage of packet load on a PTP port.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.12
ptpStatusPortStateThe port state of PTP port. Either it is master or probe mode.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.1.1.13
ptpClientTableThis table is obsolete and no longer supported.
SEQUENCE OF PtpClientEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2
ptpClientEntryThe entry of ptp client table (obsolete)
PtpClientEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1
ptpClientIndexPTP clients index. (obsolete)
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.1
ptpClientModuleIDThe module ID should be one of ioc1 or ioc2. No default value. (obsolete)ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.2
ptpClientPortIDThe PTP port ID. (obsolete)ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.3
ptpClientAddrThe PTP dynamic or static client's IP address (obsolete)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.4
ptpClientModeThe PTP client mode. (obsolete)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.5
ptpClientAnnounceIntvThe PTP client announce interval (obsolete)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.6
ptpClientSyncIntvThe PTP client sync interval (obsolete)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.7
ptpClientDelayIntvThe PTP client delay interval. (obsolete)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.8
ptpClientvlanIdThe vlan id of the current vlan interface. The range should 0~4094. (obsolete)ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.9
ptpClientClockIDPTP unicast Clock ID. The valid format should be xx:xx:xx:xx:xx:xx:xx:xx (obsolete)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.2.1.10
ptpClientDataTableThe PTP client raw data info table. It includes dynamic and static PTP clients.
SEQUENCE OF PtpClientDataEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.5.3
ptpClientDataEntryThe entry of ptp client raw data
PtpClientDataEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.5.3.1
ptpClientDataIndexPTP clients index.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.5.3.1.1
ptpClientDataThe PTP client information. It contains the followings: module-id port-id client-ip-address vlan-id vlan-priority client-clock-id client-mode announce-interval sync-interval delay-intervalro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.5.3.1.2
craftPort
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2.6
craftObject
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2.6.1
eia232BaudrateEIA-232 baudrate. It is read-only.ro
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.6.1.1
eia232StopBitEIA-232 number of stop bits. It is read-only.ro
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.6.1.2
eia232ParityEIA-232 parity. It is read-only.ro
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.6.1.3
eia232DataLengthEIA-232 data length. It is read-only.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.2.6.1.4
eia232FlowControlEIA-232 flow control. It is read-only.ro
FlowControl
.1.3.6.1.4.1.9070.1.2.4.6.2.6.1.5
inOutStatus
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.2.7
inOutTableThe input/output status table of TP5000 device. This table is used to report the I/O port types.
SEQUENCE OF InOutEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.7.1
inOutEntryThe entry of input/output status table.
InOutEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.7.1.1
inOutIndexThe index of input/output status table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.7.1.1.1
inOutPortIDThe port ID. The port id should be defined as follows: port1(1), port2(2), port3(3), port4(4), or none(5).ro
TPIOPortID
.1.3.6.1.4.1.9070.1.2.4.6.2.7.1.1.2
inOutPortTypeThe input/output port type. It should be one of the input(1) or output(2).ro
TPIOType
.1.3.6.1.4.1.9070.1.2.4.6.2.7.1.1.3
inOutOutputTypeThe output port type. It shows the current output type of the io port.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.7.1.1.4
ioOutPortStatusThe input/output port current status.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.2.7.1.1.5
inOutSSMValueTableThe input/output SSM value table of TP5000 device. This table is used to report the I/O port SSM current value.
SEQUENCE OF InOutSSMValueEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.7.2
inOutSSMValueEntryThe entry of input/output status table.
InOutSSMValueEntry
.1.3.6.1.4.1.9070.1.2.4.6.2.7.2.1
inOutSSMValueIndexThe index of input/output SSM value table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.2.7.2.1.1
inOutSSMValuePortIDThe port ID. The port id should be defined as follows: port1(1), port2(2), port3(3), port4(4), or none(5).ro
TPIOPortID
.1.3.6.1.4.1.9070.1.2.4.6.2.7.2.1.2
ioOutSSMValueThe SSM current value of the input. The valid reading should be 1~9. See user's guide for definition of SSM quality level value.ro
TPSSMValue
.1.3.6.1.4.1.9070.1.2.4.6.2.7.2.1.3
configuration
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3
inventoryConfig
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3.1
assetSettingNumInventory asset number is assigned by the user.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.1.1
alarmConfig
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3.2
alarmConfigTableThe alarm configuration table. It includes the alarm id, alarm severity level, delay, enable state, and alarm description for each alarm.
SEQUENCE OF AlarmConfigEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.2.1
alarmConfigEntryThe entry of alarm configuration table.
AlarmConfigEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.2.1.1
alarmConfigIndexThe index of alarm configuration table. Its range will be 1~256.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.3.2.1.1.1
alarmConfigAIDThis value is the alarm id. The alarm definition for each ID is defined in the User Guide.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.3.2.1.1.2
alarmLevelSettingThe alarm severity level of the current alarm. The severity of an alarm is as follows: 2 Critical: critical conditions 3 Major: error conditions 4 Minor: warning conditions 5 Event: normal but significant conditionrw
AlarmLevel
.1.3.6.1.4.1.9070.1.2.4.6.3.2.1.1.3
alarmSettingDelayThe alarm delay in seconds.rw
Integer32 UNITS "second"
.1.3.6.1.4.1.9070.1.2.4.6.3.2.1.1.4
enableAlarmStateThe alarm state control flag. The flag could be enable(1) or disable(2). The default value is enable.rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.2.1.1.5
alarmConfigDescThe alarm description of an alarm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.2.1.1.6
sysGeneral
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3.3
bridgingTimeThe bridging time in seconds.rw
Unsigned32 UNITS "Second"
.1.3.6.1.4.1.9070.1.2.4.6.3.3.1
sysDateTimeThe date and time of IMC module. The date and time setting can not be accepted in GPS mode. The format of date and time is: YYYY-MM-DD,HH:MM:SSrw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.3.2
leapSecondThe accumulated leap seconds between TAI and UTC time.rw
Unsigned32 UNITS "Second"
.1.3.6.1.4.1.9070.1.2.4.6.3.3.3
messageGenerateThe flag is defined as to generate all messages. For messages that specify a port, only one message will be generated instead of a message for all possible ports. This item is write-only.rw
OnValue
.1.3.6.1.4.1.9070.1.2.4.6.3.3.4
sysRefCriteriaThe reference criteria: manual(1), priority(2) and ssm(3).rw
TPReferenceMode
.1.3.6.1.4.1.9070.1.2.4.6.3.3.5
sysRefOverrideThe input reference override: gps(0), port1(1), port2(2), uti1(3) and uti2(4). For the current firmware release, only port1(1) and port2(2) are applicable.rw
TPReference
.1.3.6.1.4.1.9070.1.2.4.6.3.3.6
sysToDSourceToD source: gps, sys, ntp, ptp or uti. The detailed definition is as following: gps(1), sys(2), ntp(3), ptp(4), uti(5). For the current firmware release, only gps(1) and sys(2) are applicable.rw
ToDSource
.1.3.6.1.4.1.9070.1.2.4.6.3.3.7
sysSyncSync phase and time to current reference. This item is write-only. A read of this item is invalid. Only 'now' is accepted.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.3.8
sysAutoSyncThe auto sync state: enable(1) or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.3.9
logFileSettingTableThe log file table is used to configure the log file size.
SEQUENCE OF LogFileSettingEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.3.10
logFileSettingEntryThe log file table to define the buffer size.
LogFileSettingEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.3.10.1
logFileSettingIndexThe index of log file table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.3.10.1.1
logFileTypeNameThe log type name. This item is read only. It has the following names: Alarm, Event, Command, Securityro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.3.10.1.2
logFileBufferSizeThe size for the log file. The max value is 100 KB.rw
Unsigned32 UNITS "Kbyte"
.1.3.6.1.4.1.9070.1.2.4.6.3.3.10.1.3
remoteSyslogTableThe remote syslog file control table.
SEQUENCE OF RemoteSyslogEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.3.11
remoteSyslogEntryThe entry of remote log file control table.
RemoteSyslogEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.3.11.1
remoteSyslogIndexThe index of remote log file table. Only an index value of 1 is supported.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.3.11.1.1
remoteSyslogStateThe remote syslog state control. The setting could be enable(1), or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.3.11.1.2
remoteSyslogAddressThe IP address of remote syslog machine. The format should be xxx.xxx.xxx.xxxrw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.3.3.11.1.3
redundancyTableThe port redundancy table of IOC modules.
SEQUENCE OF RedundancyEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.3.12
redundancyEntryThe entry of port redundancy table.
RedundancyEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.3.12.1
redundancyIndexThe index of port redundancy table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.3.12.1.1
redundancyModuleIDThe module ID should be one of ioc1 or ioc2. This is a read-only field.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.3.12.1.2
redundancyModuleStatePort redundancy state: enable(1) or disable(2) .rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.3.12.1.3
redundancyActivePortPort redundancy active state port id, only eth1(1) or eth2(2) can be selected. This can be used to set the selected port as the active port.rw
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.3.12.1.4
iocStateTableThe IOC state table for configuring the state of IOC.
SEQUENCE OF IocStateEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.3.13
iocStateEntryThe IOC state table to configure the state of IOC.
IocStateEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.3.13.1
iocStateIndexIOC index: 1~2
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.3.13.1.1
iocModuleIDThe IOC module ID: ioc1, ioc2. This field is read-only.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.3.13.1.2
iocStateIOC state. The reading value could be : active(1), standby(2), nonexisting(3), failed(4), disable(5), activeWarmup, or standbyWarmup. To change state, a value of active(1) should be sent to the IOC which is in standby. All other values and actions are not supported.rw
IOCMode
.1.3.6.1.4.1.9070.1.2.4.6.3.3.13.1.3
network
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3.4
sysHostNameThe system hostname of TP5000 device.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.4.1
intraCommIPSetIntra-communication IP set between IOCs and IMC. The IP sets are defined as class A (10.0.250.x), class B (172.16.250.x) and class C(192.168.250.x). See user's guide for more details. The definition is as follows: A(1), B(2), C(3). This value should not be changed unless it is necessary. After the value is changed, the IMC and IOC will establish a new connection in 1~2 minutes.rw
IntraIPSet
.1.3.6.1.4.1.9070.1.2.4.6.3.4.2
ipIMCModeIMC IP mode. The valid values are: dhcp(1), static(2.) If the dhcp mode is set for IMC management port, the ip port info of IMC will not be shown. After changing mode, user must restart interface by setting ipPortState to restart in ipPortTable.rw
IPPortMode
.1.3.6.1.4.1.9070.1.2.4.6.3.4.3
vlanStateTableThe vlan state table of TP5000 device. Controls overall VLAN enable for each port.
SEQUENCE OF VlanStateEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.4
vlanStateEntryThe vlan state table entry.
VlanStateEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.4.1
vlanStateIndexThe index of VLAN state table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.4.4.1.1
vlanStateModuleIDThe vlan module ID. The valid ID should be one of IOC1(3) or IOC2(4).ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.4.1.2
vlanStatePortIDThe Ethernet Port ID on IOC board. The port definition is as follows: eth1(1), eth(2)ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.4.1.3
vlanPortStateThe vlan state of IOC port. The definition is as follows: enable(1), disable(2)rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.4.1.4
vlanTableThe vlan table of TP5000 device.
SEQUENCE OF VlanEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5
vlanEntryThe vlan table entry.
VlanEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1
vlanIndexThe index of VLAN table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.1
vlanModuleIDThe vlan module ID. The valid ID should be one of ioc1(3) or ioc2(4).ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.2
vlanPortIDThe Ethernet Port ID on IOC board. The detailed definition is as follows: eth1(1), eth2(2)ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.3
vlanTableIndexThe table index for each vlan interface. The index range will be 1 ~ 16.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.4
vlanStateThe state for this vlan index. The state definition is as follows: enable(1), disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.5
vlanIdThe vlan id of the current vlan interface. The range should 0~4094. If a vlanid is set to 0, the associated vlan interface of this vlan index will be removed from the internal vlan table. The default vlanid of each vlan interface in the vlan table is 0. The vlanid can be setup once only. A vlanId and vlanPriority should be configured at same time if a vlan interface row is added. Once vlanId is defined, it can not be modified unless it is set to 0 (deleting this vlan interface from the vlan table).rw
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.6
vlanPriorityThe priority of vlan id. The range should be 0 to 7. A vlanPriority and vlanId should be configured at same time if a vlan interface row is added. Once vlanPriority is defined, it can not be modified unless this vlanId is set to 0 (deleting this vlan interface from the vlan table).rw
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.7
vlanIPAddrressIP address of an vlan interface. The format should be xxx.xxx.xxx.xxx. Each VLAN must be in a separate subnet. After changing value, user must restart interface by setting ipPortState to restart in ipPortTable.rw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.8
vlanSubnetMaskThe IP mask of a vlan interface. The format should be xxx.xxx.xxx.xxx. After changing value, user must restart interface by setting ipPortState to restart in ipPortTable.rw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.9
vlanGatewayAddressIP address of gateway of vlan interface. The format should be xxx.xxx.xxx.xxx. Use 0.0.0.0 if no gateway is required. After changing value, user must restart interface by setting ipPortState to restart in ipPortTable.rw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.3.4.5.1.10
ipPortTableThe IP port configuration table of TP5000 device.
SEQUENCE OF IpPortEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6
ipPortEntryThe IP port configuration table.
IpPortEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1
ipPortIndexThe index of IP port configuration table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1.1
ipModuleIDThe module ID of TP5000 boards. The module is as follows: imc(2), ioc1(3), ioc2(4)ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1.2
ipPortIDIP Port ID on each board. The value should be one of eth1(1), eth2(2), none(5)ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1.3
ipPortModeIP port mode of an ethernet port. The detailed definition is as follows: dhcp(1), static(2). Use ipIMCMode to change the mode of the IMC port.ro
IPPortMode
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1.4
ipPortIPAddressThe address of the IP port of each board. The address format is : xxx.xxx.xxx.xxx. After changing value, user must restart interface by setting ipPortState to restart in ipPortTable.rw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1.5
ipPortGatewayAddressThe gateway address of each IP port. The address format is : xxx.xxx.xxx.xxx. Use 0.0.0.0 if no gateway is required. After changing value, user must restart interface by setting ipPortState to restart in ipPortTable.rw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1.6
ipPortSubnetMaskThe mask of an IP port. The address format is : xxx.xxx.xxx.xxx. After changing value, user must restart interface by setting ipPortState to restart in ipPortTable.rw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1.7
ipPortStateThe state of an IP port. The definition is as follows: enable(1), disable(2), restart(3).rw
IPPortState
.1.3.6.1.4.1.9070.1.2.4.6.3.4.6.1.8
imcFirewallTableThe firewall table of IMC module of TP5000 device.
SEQUENCE OF ImcFirewallEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7
imcFirewallEntryThe entry of IMC firewall table.
ImcFirewallEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1
imcFirewallIndexThe IMC firewall index.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.1
imcFirewallModuleIDThe module ID of IMC module.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.2
imcFirewallPortIDIP Port ID on IMC.ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.3
imcFirewallICMPThe firewall flag of IMCP. The setting could be allow(1), or block(2).rw
FirewallValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.4
imcFirewallTelnetThe firewall flag of TELNET. The setting could be allow(1), or block(2).rw
FirewallValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.5
imcFirewallSSHThe firewall flag of SSH. The setting could be allow(1), or block(2).rw
FirewallValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.6
imcFirewallSFTPThe firewall flag of SFTP. The setting could be allow(1), or block(2).rw
FirewallValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.7
imcFirewallSNMPThe firewall flag of SNMP. The setting could be allow(1), or block(2).rw
FirewallValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.8
imcFirewallFTPThe firewall flag of IMCP. The setting could be allow(1), or block(2).rw
FirewallValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.7.1.9
ethAutoNegTableThe IP port auto-negotiation table of TP5000 device.
SEQUENCE OF EthAutoNegEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.8
ethAutoNegEntryThe ethernet auto-negotiation table.
EthAutoNegEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.4.8.1
ethAutoNegIndexThe index of ethernet auto-negotiation table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.4.8.1.1
ethAutoNegModuleIDThe module ID of TP5000 boards. The module is as follows: ioc1(3), ioc2(4)ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.8.1.2
ethAutoNegPortIDIP Port ID on each board. The value should be one of eth1(1), eth2(2), none(5)ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.4.8.1.3
ethAutoNegStateThe IP port auto-negotiation state. The definition is as follows: enable(1), disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.4.8.1.4
ethAutoNegSpeedThe ethernet auto-negotiation advertised speed. The defined speeds are 100M, 1000M, allrw
AutoSpeedType
.1.3.6.1.4.1.9070.1.2.4.6.3.4.8.1.5
inputOutput
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3.5
inputOutputTableThe input/output configuration table of TP5000 device. This table is used to configure the I/O port types.
SEQUENCE OF InputOutputEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.1
inputOutputEntryThe entry of input/output configuration table.
InputOutputEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.1.1
inputOutputIndexThe index of input/output table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.5.1.1.1
ioPortIDThe port ID. The port id should be defined as follows: port1(1), port2(2), port3(3),or port4(4). Only ports 1 and 2 can be configured as inputs.ro
TPIOPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.5.1.1.2
ioPortTypeThe input/output port type. It should be one of the input(1) or output(2).rw
TPIOType
.1.3.6.1.4.1.9070.1.2.4.6.3.5.1.1.3
inputTableThe Input port configuration table of TP5000 device.
SEQUENCE OF InputEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2
inputEntryThe entry of input table.
InputEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1
inputIndexThe index of input table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.1
inputPortIDThe port ID. It should be one of port1(1), port2(2).ro
TPIOPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.2
inputStateIndicates if the port is enabled or disabled. The valid setting should be enable(1) or disable(2).rw
PortState
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.3
inputPriorityIndicates the priority level setting 1 through 2 - a lower number indicates a higher priority.rw
TPInputPriority
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.4
inputFrameTypeIndicates the Frame type - The valid value should be one of following: freq1544khz(1), freq2048khz(2), ccs(3), cas(4), d4(5), esf(6). Check SRN and user's guide for supported frame types. Proper I/O module must also be installed in chassis.rw
InputFrameType
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.5
inputCRCStateIndicates if CRC control state. The valid setting should be one of enable(1) or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.6
inputSSMStateIndicates SSM state. The valid setting is enable(1) or disable(2)rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.7
inputSSMBitSets the SSM bit position to 4, 5, 6, 7, or 8. Only used for CCS or CAS framing typerw
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.8
inputSSMValueThe SSM value. The valid setting should be 1~9. See user's guide for definition of SSM quality level value.rw
TPSSMValue
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.9
inputSSMCurrValueThe SSM current value of the input. The valid reading should be 1~9. See user's guide for definition of SSM quality level value.ro
TPSSMValue
.1.3.6.1.4.1.9070.1.2.4.6.3.5.2.1.10
outputTableThe output port configuration table of TP5000. The current output port only supports the following type: output-10MHz and output-pps
SEQUENCE OF OutputEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.3
outputEntryThe entry of 10MHz and PPS output table.
OutputEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.3.1
outputIndexThe index of 10 MHz and PPS output table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.5.3.1.1
outputPortIDThe port ID. It should be one of port1(1), port2(2), port3(3), port4(4).ro
TPIOPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.5.3.1.2
outputPortTypeThe output port type. The detailed definition is as follows: output10Mhz(2) or outputPPS(3).ro
TPOutputType
.1.3.6.1.4.1.9070.1.2.4.6.3.5.3.1.3
outputStateIndicates if the port is enabled or disabled. The valid setting should be enable(1), or disable(2).rw
PortState
.1.3.6.1.4.1.9070.1.2.4.6.3.5.3.1.4
outputGenerationThe output generation is now obsolete and deprecatedrw
TPOutputGeneration
.1.3.6.1.4.1.9070.1.2.4.6.3.5.3.1.5
e1T1OutputTableThe E1 and T1 output port configuration table of TP5000.
SEQUENCE OF E1T1OutputEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4
e1T1OutputEntryThe entry of E1 and T1 output table.
E1T1OutputEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1
e1T1OutputIndexThe index of E1 and T1 output table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.1
e1T1OutputPortIDThe port ID. It should be one of port1(1), port2(2), port3(3), port4(4).ro
TPIOPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.2
e1T1OutputPortTypeThe output port type. The detailed definition is as follows: outputGeneral(1).ro
TPOutputType
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.3
e1T1OutputStateIndicates if the port is enabled or disabled. The valid setting should be enable(1), or disable(2).rw
PortState
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.4
e1T1OutputGenerationThe output generation is now obsolete and deprecatedrw
TPOutputGeneration
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.5
e1T1OutputFrameTypeIndicates the Frame type. The detailed definition is as follows: frame1544hz(1), frame2048hz(2), ccs(3), cas(4), esf(5), d4(6). Check SRN or user's guide for supported frame types.rw
OutputFrameType
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.6
e1T1OutputCRCStateIndicates if CRC is enabled or disabled. The valid value should be one of Enable(1) or Disable(2)rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.7
e1T1OutputSSMStateIndicates if the T1 (ESF) or E1 (CCS) input is provisioned to generate (Enabled) or not to generate (Disabled) SSM.rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.8
e1T1OutputSSMBitSets the SSM bit position to 4, 5, 6, 7, or 8.rw
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.5.4.1.9
pps10MOutGenTable1PPS and 10 Mhz output generation table.
SEQUENCE OF Pps10MOutGenEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.5
pps10MOutGenEntryThe entry of 10MHz and PPS output table.
Pps10MOutGenEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.5.1
pps10MOutIndexThe index of 10 MHz and PPS output generation table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.5.5.1.1
pps10MOutGenPortIDThe port ID. It should be one of port3(3), port4(4).ro
TPIOPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.5.5.1.2
pps10MOutGenWarmup1PPS and 10 Mhz output generation on warm-up staterw
PPS10MOutGenMode
.1.3.6.1.4.1.9070.1.2.4.6.3.5.5.1.3
pps10MOutGenFreerun1PPS and 10 Mhz output generation on free-run staterw
PPS10MOutGenMode
.1.3.6.1.4.1.9070.1.2.4.6.3.5.5.1.4
pps10MOutGenHoldover1PPS and 10 Mhz output generation on holdover staterw
PPS10MOutGenMode
.1.3.6.1.4.1.9070.1.2.4.6.3.5.5.1.5
pps10MOutGenFasttrack1PPS and 10 Mhz output generation on holdover staterw
PPS10MOutGenMode
.1.3.6.1.4.1.9070.1.2.4.6.3.5.5.1.6
e1T1OutGenTableE1 or T1 output generation table.
SEQUENCE OF E1T1OutGenEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.6
e1T1OutGenEntryThe entry of E1 and T1 output generation table.
E1T1OutGenEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.5.6.1
e1T1OutGenIndexThe index of E1 and T1 output generation table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.5.6.1.1
e1T1OutGenPortIDThe port ID. It should be one of port1(1), port2(2), port3(3), port4(4).ro
TPIOPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.5.6.1.2
e1T1OutGenWarmupThe E1 and T1 output generation on warm-up staterw
E1T1OutGenMode
.1.3.6.1.4.1.9070.1.2.4.6.3.5.6.1.3
e1T1OutGenFreerunE1 and T1 output generation on free-run staterw
E1T1OutGenMode
.1.3.6.1.4.1.9070.1.2.4.6.3.5.6.1.4
e1T1OutGenHoldoverE1 and T1 output generation on holdover staterw
E1T1OutGenMode
.1.3.6.1.4.1.9070.1.2.4.6.3.5.6.1.5
e1T1OutGenFasttrackE1 and T1 output generation on holdover staterw
E1T1OutGenMode
.1.3.6.1.4.1.9070.1.2.4.6.3.5.6.1.6
ptp
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3.6
ptpCommonTablePTP common table of TP5000 device.
SEQUENCE OF PtpCommonEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1
ptpCommonEntryThe entry of PTP common table
PtpCommonEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1
ptpCommonIndexThe index of PTP common table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.1
ptpCommonModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.2
ptpCommonPortIDPort ID (ethernet port ID) on board. It should be one of eth1(1) or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.3
ptpCommonProfilePTP common profile. The definition is as follows: unicast(0), multicast(1). The current release is read-only.ro
PTPProfileType
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.4
ptpCommonClockIDPTP common ClockID for the TP5000. The valid setting format should be xx:xx:xx:xx:xx:xx:xx:xxrw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.5
ptpCommonPriority1PTP common priority 1. The valid range should be: 0~255.rw
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.6
ptpCommonPriority2PTP common priority 2. The valid value should be:0~255.rw
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.7
ptpCommonDomainPTP common domain. The range should be 0~255rw
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.8
ptpCommonDSCPStatePTP common DSCP state. The value should be enable(1), or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.9
ptpCommonDSCPValuePTP common DSCP value. The range should be 0~63.rw
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.10
ptpCommonStatePTP common state. The value should be enable(1), or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.11
ptpCommonMaxClientPTP common MAX client number. The current range should be 1~500rw
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.12
ptpCommonAnnounceLimitPTP common announce limit. The default value should be -3 and the range should be -3 ~ 3.rw
INTEGER (-4..4)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.13
ptpCommonSyncLimitPTP common sync limit. The default value should be -7 and the range should be -7 ~ 7.rw
INTEGER (-7..7)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.14
ptpCommonDelayLimitPTP common delay limit. The default value should be -7 and the range should be -7 ~ 7.rw
INTEGER (-7..7)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.1.1.15
ptpUnicastTablePTP unicast table of TP5000 device.
SEQUENCE OF PtpUnicastEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.2
ptpUnicastEntryThe entry of PTP unicast table
PtpUnicastEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.2.1
ptpUnicastIndexThe index of PTP unicast table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.2.1.1
ptpUnicastModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.2.1.2
ptpUnicastPortIDPTP multicast Port ID. It should be one of eth1(1), or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.2.1.3
ptpUnicastNegotiatePTP unicast negotiate value. The valid setting should be enable(1), or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.2.1.4
ptpUnicastLeaseDurationPTP unicast lease duration. The valid setting range should be 10 ~ 1000.rw
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.2.1.5
ptpUnicastClientTablePTP unicast static client table of TP5000 device.
SEQUENCE OF PtpUnicastClientEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3
ptpUnicastClientEntryThe entry of PTP unicast client table.
PtpUnicastClientEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1
ptpUnicastClientIndexThe index of PTP unicast table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.1
ptpUnicastClientModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-only.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.2
ptpUnicastClientPortIDPTP multicast Port ID. It should be one of eth1(1) or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.3
ptpUnicastClientIDPTP unicast client ID. The range will be 1~10.ro
TPClientID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.4
ptpUnicastClientStatePTP unicast client state. The valid value should be enable(1) or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.5
ptpUnicastClientAddrPTP unicast static client IP address. The format should be xxx.xxx.xxx.xxx. If the address 0.0.0.0 is set, the associated static ptp client will be removed from the ptp unicast client table internally. By default, all static ptp client's address is 0.0.0.0.rw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.6
ptpUnicastClientSyncIntPTP unicast sync interval value. The range is -7 to 7.rw
INTEGER (-7..7)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.7
ptpUnicastClientAnnounceIntPTP unicast Announce Int value. The range is -3 to 3.rw
INTEGER (-4..4)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.8
ptpUnicastClientDelayIntPTP unicast Delay value. The range is -7 to 7.rw
INTEGER (-7..7)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.9
ptpUnicastClientVlanIdPTP unicast VLAN ID. The valid range should be 0~4094rw
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.10
ptpUnicastClientClockIDPTP unicast Clock ID. The valid format should be xx:xx:xx:xx:xx:xx:xx:xxrw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.3.1.11
ptpCardCommonTablePTP card common parameters table of TP5000 device.
SEQUENCE OF PtpCardCommonEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.4
ptpCardCommonEntryThe entry of PTP card common parameters table
PtpCardCommonEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.4.1
ptpCardCommonIndexThe index of PTP card common table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.4.1.1
ptpCardCommonModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.4.1.2
ptpCardCommonTimeScalePTP card common Time scale. The valid setting should be: auto(1), arb(2), ptp(3)rw
PTPTimeScaleValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.4.1.3
ptpCardCommonDitherPTP card common dither state. The value should be enable(1), or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.4.1.4
ptpCommonExtTableThe second PTP common table of TP5000 device.
SEQUENCE OF PtpCommonExtEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5
ptpCommonExtEntryThe entry of PTP common table
PtpCommonExtEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1
ptpCommonExtIndexThe index of PTP common #2 table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1.1
ptpCommonExtModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1.2
ptpCommonExtPortIDPort ID (ethernet port ID) on board. It should be one of eth1(1) or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1.3
ptpCommonExtTwoStepPTP Two-Step clock flag. The valid value should be Enable(1), or Disable(2)rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1.4
ptpCommonExtMgmtAddrModePTP management addressing mode for communication between tp5000 and clients: unicast, or multicastrw
PTPMgmtAddrMode
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1.5
ptpCommonExtAddrModePTP addressing mode (profile): unicast, multicast, or multicast-hybridrw
PTPAddrMode
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1.6
ptpCommonExtTTLIP TTL (Time to live). The valid value should be:1~64.rw
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1.7
ptpCommonExtAlternateGMPTP alternate master flag. The value should be enable(1), or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.5.1.8
ptpMulticastTablePTP unicast table of TP5000 device.
SEQUENCE OF PtpMulticastEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6
ptpMulticastEntryThe entry of PTP unicast table
PtpMulticastEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1
ptpMulticastIndexThe index of PTP unicast table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.1
ptpMulticastModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.2
ptpMulticastPortIDPTP multicast Port ID. It should be one of eth1(1), or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.3
ptpMulticastAnnounceIntPTP multicast Announce Interval value. The range is -4 to 4.rw
INTEGER (-4..4)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.4
ptpMulticastSyncIntPTP multicast sync interval value. The range is -7 to 7.rw
INTEGER (-7..7)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.5
ptpMulticastDelayIntPTP multicast delay interval value. The range is -7 to 7.rw
INTEGER (-7..7)
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.6
ptpMulticastAnnounceTimeoutPTP multicast announce receipt timeout. The valid value should be 2 ~ 10.rw
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.7
ptpMulticastVlanIdPTP multicast VLAN ID. The valid range should be 0~4094rw
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.8
ptpMulticastClientTimeoutPTP multicast client timeout. The valid value should be 10~3600.rw
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.3.6.6.1.9
ptpG82751TablePTP itu-g8276-1 table of TP5000 device.
SEQUENCE OF PtpG82751Entry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.7
ptpG82751EntryThe entry of PTP G82751 table
PtpG82751Entry
.1.3.6.1.4.1.9070.1.2.4.6.3.6.7.1
ptpG82751IndexThe index of PTP G82751 table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.7.1.1
ptpG82751ModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.7.1.2
ptpG82751PortIDPTP multicast Port ID. It should be one of eth1(1), or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.3.6.7.1.3
ptpG82751MulticastAddrPTP G82751 Multicast Address. The valid setting should be mac011b19000000 (1) or mac0180c200000e (2)rw
G82751McAddrValue
.1.3.6.1.4.1.9070.1.2.4.6.3.6.7.1.4
ptpG82751LocalPriorityPTP G82751 local priority. The valid setting range should be 1 ~ 255.rw
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.6.7.1.5
gps
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3.7
posModeGPS operation mode. It is defined as follows: auto(1), manual(2). When the auto mode is selected, manually setting gps position is prohibited.rw
GPSPosMode
.1.3.6.1.4.1.9070.1.2.4.6.3.7.1
posElevationMaskThe GPS elevation mask in degrees from 0 to 45rw
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.7.2
antennaCableDelayThe GPS antenna cable delay. The unit is nanosecondsrw
Integer32 UNITS "ns"
.1.3.6.1.4.1.9070.1.2.4.6.3.7.3
gpsPOSTableThe configuration table of initial GPS position. Before the gps position is configured, GPS position mode should be setup as manual mode.
SEQUENCE OF GpsPOSEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.7.4
gpsPOSEntryThe entry of GPS table.
GpsPOSEntry
.1.3.6.1.4.1.9070.1.2.4.6.3.7.4.1
gpsPOSIndexThe index of gps position table.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.3.7.4.1.1
gpsLatitudeThe latitude value of GPS position. The format of latitude: Ndd:mm:ss.ss or Sdd:mm:ss.ss Before the gps position is configured,GPS position mode should be setup as manual mode.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.7.4.1.2
gpsLongitudeThe longitude value of the GPS position. The format of longitude: Eddd:mm:ss.ss or Wddd:mm:ss.ss Before the gps position is configured,GPS position mode should be setup as manual mode.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.7.4.1.3
gpsHeightThe altitude value of GPS position in meters. The format of height: +/-hhhh.h Before the gps position is configured,GPS position mode should be setup as manual mode.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.3.7.4.1.4
ptpLock
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.3.8
ptpClientDataTableLockThe ptpClientDataTableLock will control the internal semaphore to lock or unlock the ptpClientDataTable. When the ptpClientDataTable is locked, the data in the table will not change. The ptpClientDataTableLock can be setup to be locked or to be unlocked. When the locked signal is issued, the internal semaphore will be increased and start to lock the ptpClientDataTable. When the unlocked signal is issued, the internal semaphore will be decreased. When the semaphore reaches zero (0), the ptpClientDataTable will be unlocked. The ptpClientDataTableLock can be read as the locked or unlocked to determine the current lock state.rw
Enumeration
.1.3.6.1.4.1.9070.1.2.4.6.3.8.1
ptpClientManagement
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.4
ptpNodeInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.4.1
ptpNodeTableThe PTP node table will define node address (IP) and identifier (VLAN ID). These will be used in querying accMasterTable, NodeStatusTable, nodeClockDescTable and nodeNullMgmtTable.
SEQUENCE OF PtpNodeEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.1
ptpNodeEntryThis is an entry in the ptp node table.
PtpNodeEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.1.1
ptpNodeIndexA unique value for each ptp node entry.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.1.1.1
ptpNodeModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.4.1.1.1.2
ptpNodePortIDPort ID (ethernet port ID) on board. It should be one of eth1(1) or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.4.1.1.1.3
ptpNodeIPAddrThe assigned IP address for ptp node. This IP address will be applied to ptpnodeACCMasterTable, iocXXnodeStatusTable, iocXXnodeClockDescTable, iocXXnodeNullMGMTable. The format should be xxx.xxx.xxx.xxxrw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.4.1.1.1.4
ptpNodeVlanIdPTP node (client) VLAN ID. The valid range should be 0~4094. This vlan id will be applied to ptpnodeACCMasterTable, iocXXnodeStatusTable, iocXXnodeClockDescTable, iocXXnodeNullMGMTable. The value should be 0 if no VLAN is being used.rw
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.1.1.5
ptpNodeReservedThis variable is designed to separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.2
ioc11NodeStatusTableThe ptp node status table. It will provide the ptp node status info of the client(slave) on ioc and port1. The requested IP address and vlan id of client node is pre-defined in ptpNodeTable .
SEQUENCE OF Ioc11NodeStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.3
ioc11NodeStatusEntryThe ptp node status table on ioc and port1.
Ioc11NodeStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.3.1
ioc11NodeStatusIndexThe index of ptp node status table with the assigned IP on ioc and port1.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.4.1.3.1.1
ioc11NodeStatusNameThe status name (status item description) of the ptp client with the assigned IP on ioc and port1.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.3.1.2
ioc11NodeStatusValueThe status item value of the ptp client with the assigned IP on ioc and port1.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.3.1.3
ioc11NodeStatusIdThe status item Id of the ptp client with the assigned IP on ioc and port1. The status id is 0 if there is no valid status id.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.4.1.3.1.4
ioc11NodeStatusReservedThis variable is designed to separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.4
ioc12NodeStatusTableThe ptp node status table. It will provide the ptp node status info of the client(slave) side on ioc and port2. The requested IP address and vlan id of client node is pre-defined in ptpNodeTable .
SEQUENCE OF Ioc12NodeStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.5
ioc12NodeStatusEntryThe ptp node status table on ioc and port2.
Ioc12NodeStatusEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.5.1
ioc12NodeStatusIndexThe index of ptp node status table with the assigned IP on ioc and port2.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.4.1.5.1.1
ioc12NodeStatusNameThe status name (status item description) of the ptp client with the assigned IP on ioc and port2ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.5.1.2
ioc12NodeStatusValueThe status item value of the ptp client with the assigned IP on ioc and port2.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.5.1.3
ioc12NodeStatusIdThe status item Id of the ptp client with the assigned IP on ioc and port1. The status id is 0 if there is no valid status id.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.4.1.5.1.4
ioc12NodeStatusReservedThis variable is designed to separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.6
ioc11NodeClockDescTableThe clock description table of ptp node(client) on ioc and port1. The requested IP address and vlan id of client node is pre-defined in ptpNodeTable .
SEQUENCE OF Ioc11NodeClockDescEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.7
ioc11NodeClockDescEntryThe ptp node clock description table on ioc and port1.
Ioc11NodeClockDescEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.7.1
ioc11NodeClockDescIndexThe index of clock description table with the assigned IP on ioc and port1.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.4.1.7.1.1
ioc11NodeClockDescNameThe clock description name of the ptp client with the assigned IP on ioc and port1.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.7.1.2
ioc11NodeClockDescValueThe clock description value of the ptp client with the assigned IP on ioc and port1.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.7.1.3
ioc11NodeClockDescReservedThis variable is designed to separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.8
ioc12NodeClockDescTableThe clock description table of ptp node(client) on ioc and port2. The requested IP address and vlan id of client node is pre-defined in ptpNodeTable .
SEQUENCE OF Ioc12NodeClockDescEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.9
ioc12NodeClockDescEntryThe ptp node clock description table on ioc and port2.
Ioc12NodeClockDescEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.9.1
ioc12NodeClockDescIndexThe index of clock description table with the assigned IP on ioc and port2.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.4.1.9.1.1
ioc12NodeClockDescNameThe clock description name of the ptp client with the assigned IP on ioc and port2.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.9.1.2
ioc12NodeClockDescValueThe clock description value of the ptp client with the assigned IP on ioc and port2.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.9.1.3
ioc12NodeClockDescReservedThis variable is designed to separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.10
ioc11NodeNullMgmtTableThe null management table of ptp node(client) on ioc and port1. The requested IP address and vlan id of client node is pre-defined in ptpNodeTable .
SEQUENCE OF Ioc11NodeNullMgmtEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.11
ioc11NodeNullMgmtEntryThe ptp node null management table on ioc and port1.
Ioc11NodeNullMgmtEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.11.1
ioc11NodeNullMgmtIndexThe index of the null management table with assigned IP on ioc and port1.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.4.1.11.1.1
ioc11NodeNullMgmtInfoThe null info of the ptp client with the assigned IP on ioc and port1.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.11.1.2
ioc11NodeNullMgmtReservedThis variable is designed as a separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.12
ioc12NodeNullMgmtTableThe null management table of ptp node(client) on and port2. The requested IP address and vlan id of client node is pre-defined in ptpNodeTable .
SEQUENCE OF Ioc12NodeNullMgmtEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.13
ioc12NodeNullMgmtEntryThe ptp node ack management table on ioc and port2.
Ioc12NodeNullMgmtEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.13.1
ioc12NodeNullMgmtIndexThe index of the null management table with assigned IP on ioc and port2.
Integer32
.1.3.6.1.4.1.9070.1.2.4.6.4.1.13.1.1
ioc12NodeNullMgmtInfoThe null info of the ptp client with the assigned IP on ioc and port2ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.13.1.2
ioc12NodeNullMgmtReservedThis variable is designed to separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.14
accMasterTableThe ptp node acc-master table with assigned IP.
SEQUENCE OF AccMasterEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15
accMasterEntryThe ptp node acc-master table.
AccMasterEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1
accMasterIndexThe index of ptp node acc-master table.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.1
accMasterModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.2
accMasterPortIDPort ID (ethernet port ID) on board. It should be one of eth1(1) or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.3
accPtpNodeIPAddrThe assigned IP address for ptp node(client). This IP address is pre-defined in ptpNodeTable in same portID and moduleID row .ro
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.4
accPtpNodeVlanIdPTP node (client) vlan id. The valid range should be 0~4094. This vlan id is pre-defined in ptpNodeTable in same portID and moduleID row.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.5
accPtpNodeClockIDPTP node (client) Clock ID. The valid format should be xx:xx:xx:xx:xx:xx:xx:xxro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.6
accMaster1IPAddressThe address of the master1 in the ptp client under the assigned IP.ro
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.7
accMaster1Priority1The ptp node master1's priority1 under the assigned IP.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.8
accMaster2IPAddressThe address of the master2 in the ptp client under the assigned IP.ro
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.9
accMaster2Priority1The ptp node master2's priority1 under the assigned IP.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.15.1.10
accMasterReservedThis variable is designed to separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.16
singleClientDataInfoEth1This variable returns information on a single client by using the IP address set in ptpNodeTable.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.17
singleClientDataInfoEth2This variable returns information on a single client by using the IP address set in ptpNodeTable.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.1.18
lastReservedThis variable is designed to separate tables.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.1.19
ptpNodeControl
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.4.2
accMasterSetupTableThe acceptable master table to setup ptp client acceptable master.
SEQUENCE OF AccMasterSetupEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.2.1
accMasterSetupEntryThis is an entry in the acceptable master table.
AccMasterSetupEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.2.1.1
accMasterSetupIndexA unique value for each acceptable master entry.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.2.1.1.1
accMasterSetupModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.4.2.1.1.2
accMasterSetupPortIDPort ID (ethernet port ID) on board. It should be one of eth1(1) or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.4.2.1.1.3
accMasterSetupCMDSetup the acceptable master table by the following command string (write-only): client-ip-address,vlanid, gm1_ip_address,gm1_priority,gm2_ip_address,gm2_priority For example: 192.168.1.9,200,192.168.1.11,2,192.168.1.12,1 The vlanid range is 0~4095. Zero(0) means no vlan idrw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.2.1.1.4
upgradeClientFirmwareTableThe table will be used to upgrade the ptp client firmware.
SEQUENCE OF UpgradeClientFirmwareEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.2.2
upgradeClientFirmwareEntryThis is an entry in the upgrade ptp client firmware table.
UpgradeClientFirmwareEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.2.2.1
upgradeClientFirmwareIndexA unique value for each upgrade client firmware entry.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.2.2.1.1
upgradeClientFirmwareModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.4.2.2.1.2
upgradeClientFirmwarePortIDPort ID (ethernet port ID) on board. It should be one of eth1(1) or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.4.2.2.1.3
upgradeClientFirmwareCMDThe ptp client upgrade server info. This entry is write-only. The server info format: client-ip-address vlanid file-path [sftp|ftp]:server-ip-address user-name password For example: 192.168.1.9 200 /tmp/client_firmware sftp:192.168.1.20 user-1 my-password The vlanid range is 0~4095. Zero(0) means no vlan idrw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.2.2.1.4
rebootClientTableThis table will be used to reboot a ptp client.
SEQUENCE OF RebootClientEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.2.3
rebootClientEntryThis is an entry in the reboot ptp client table.
RebootClientEntry
.1.3.6.1.4.1.9070.1.2.4.6.4.2.3.1
rebootClientIndexA unique value for each reboot ptp client entry.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.4.2.3.1.1
rebootClientModuleIDThe module ID should be one of ioc1(3) or ioc2(4). The value is read-onlyro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.4.2.3.1.2
rebootClientPortIDPort ID (ethernet port ID) on board. It should be one of eth1(1) or eth2(2).ro
TPPortID
.1.3.6.1.4.1.9070.1.2.4.6.4.2.3.1.3
rebootClientCMDThe reboot the specified ptp client. This entry is write-only. The server info format: client-ip-address,vlanid For example: 192.168.1.9,2 The vlanid range is 0~4095. Zero(0) means no vlan idrw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.4.2.3.1.4
administration
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.5
trapVersionSetup the trap version to SNMP agent. The valid setting should be v2c(1) and v3(2).rw
TrapVer
.1.3.6.1.4.1.9070.1.2.4.6.5.1
snmpV2StateEnable or disable the SNMP V2 facility in device. The valid setting should be either enable(1), or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.5.2
radius
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.5.3
radiusStateThe RADIUS state. The valid setting could be enable(1), or disable(2).rw
EnaValue
.1.3.6.1.4.1.9070.1.2.4.6.5.3.1
authRADIUSTableThe RADIUS table for Radius authentication server IP address and key settings.
SEQUENCE OF AuthRADIUSEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.3.2
authRADIUSEntryThis is an entry in the radius table.
AuthRADIUSEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.3.2.1
authRADIUSIndexA unique value for each radius entry.
INTEGER (1)
.1.3.6.1.4.1.9070.1.2.4.6.5.3.2.1.1
serverRADIUSIPAddressThe radius server IP address. The format should be xxx.xxx.xxx.xxx. An IP address can not setup if authRADIUSkey is none.rw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.5.3.2.1.2
authRADIUSKeyAuthentication key for radius server access.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.3.2.1.3
boardConfiguration
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.5.4
backupConfigLocalBackup the configurations of imc, ioc1 and ioc2 board to local file system. Please select apply(1) or nonapply(2). This field is write-only.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.4.1
restoreFactoryConfigRestore a factory configuration to system. All configuration parameters are reset. Please select apply(1) or nonapply(2). This field is write-only.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.4.2
restoreDefaultConfigRestore a default configuration to system. User logins and IP port configurations are not affected. Please select apply(1) or nonapply(2). This field is write-only.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.4.3
backupConfigIOCtoIMCBackup a configuration of ioc to imc board. Please select apply(1) or nonapply(2). This field is write-only.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.4.4
backupConfigIMCtoIOCBackup a configuration of imc to ioc board. Please select apply(1) or nonapply(2). This field is write-only.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.4.5
restoreConfigIOCtoIMCRestore configuration from ioc to imc board. Please select apply(1) or nonapply(2). This field is write-only.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.4.6
restoreConfigIMCtoIOCRestore configuration from imc to ioc. Please select apply(1) or nonapply(2). This field is write-only.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.4.7
reboot
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.5.5
sysRebootReboot whole system. This item is write-only. The read of this item is invalid. Only apply(1) can be set.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.5.1
sysIMCRebootReboot IMC board. This value is write-only. The read value is invalid. Only apply(1) can be set.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.5.2
sysIOC1RebootReboot IOC1 board. This item is write-only. The read of item is invalid. Only apply(1) can be set.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.5.3
sysIOC2RebootReboot IOC2 board. This item is write-only. The read of item is invalid. Only apply(1) can be set.rw
ActionApply
.1.3.6.1.4.1.9070.1.2.4.6.5.5.4
imageActive
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.5.6
imcImageActiveIMC image active control. This controls which image will be used to boot from. The valid setting should be either image1(1) or image2(2).rw
ImageActive
.1.3.6.1.4.1.9070.1.2.4.6.5.6.1
ioc1ImageActiveIOC1 image active control. This controls which image will be used to boot from. The valid setting should be either image1(1) or image2(2).rw
ImageActive
.1.3.6.1.4.1.9070.1.2.4.6.5.6.2
ioc2ImageActiveIOC2 image active control. This controls which image will be used to boot from. The valid setting should be either image1(1) or image2(2).rw
ImageActive
.1.3.6.1.4.1.9070.1.2.4.6.5.6.3
imageInfoTableA list of image information of each IMC, IOC1 and IOC2.
SEQUENCE OF ImageInfoEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.6.4
imageInfoEntryAn entry containing objects of each module's image information.
ImageInfoEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.6.4.1
imageInfoIndexThe index to represent the number of image info ID.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.5.6.4.1.1
imageInfoModuleIDThe module ID should be one of imc, ioc1 or ioc2. No default value.ro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.5.6.4.1.2
imageIDThe image ID range should be 1 to 2.ro
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.5.6.4.1.3
imageCurrentStateThe image current state should yes or no.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.6.4.1.4
imageInfoMsgThe image information will show the detailed current image message.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.6.4.1.5
cliUserTableThis table is used to display the valid user names and their associated user access level.This user list is used for connecting the CLI command parser via RS232 or Ethernet port (telnet or CLI port). This table's row only can be added or deleted. The existing row can not be modified.
SEQUENCE OF CliUserEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.7
cliUserEntryThis is an entry in the user table.
CliUserEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.7.1
cliUserIndexA unique value for each user entry. This value ranges should be 1 to 20.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.5.7.1.1
cliUserNameCLI user name. The max length of CLI user name is 20 characters. Only alphanumeric characters and chars {- , _} are acceptable. Leading characters can't be (- or _).rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.7.1.2
cliUserLevelThe number represents the user access level. The user level: user(1) - can retrieve status information only. config(2) - Configure most settings and parameters in TP5000. admin(3) - administration user, has control over all settings.rw
UserAccessLevel
.1.3.6.1.4.1.9070.1.2.4.6.5.7.1.3
cliUserPasswordCLI user password to access the CLI. The max length of password is 32 characters. Only chars {a-z, A-Z, 0-9, ! ( ) - _ . ? ~ *} are acceptable.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.7.1.4
cliUserRowStatusThe row status of CLI user table to control row actions. It has the following actions: The status column has six defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `notInService(2)', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady(3)', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo(4)', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait(5)', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy(6)', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.7.1.5
snmpUserTableThis table is used to display the valid SNMP V3 user info. All SNMP V3 users except trap users should be defined in this table. This table's row only can be added or deleted. The existing row can not be modified.
SEQUENCE OF SnmpUserEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.8
snmpUserEntryThis is an entry in the SNMP V3 user table. It contains username, user type, and keys.
SnmpUserEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.8.1
snmpUserIndexA unique value for each user entry. This value ranges should be from 1 to 10.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.5.8.1.1
snmpUserNameSNMP V3 user name. The max length of SNMP V3 user name is 20 characters. Only alphanumeric characters and chars {- , _} are acceptable. Leading characters can't be (- or _).rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.8.1.2
snmpUserTypeSNMP V3 User type is defined as the follow types: 1 2 3 4 5 6 7rw
UserType
.1.3.6.1.4.1.9070.1.2.4.6.5.8.1.3
snmpAuthKeySNMP V3 user authentication key. Only chars {a-z,A-Z,0-9, ! ( ) - _ . ? ~ * @ ^ + = : / %} are acceptable. Minimum key length is 8 chars.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.8.1.4
snmpPrivatekeyPrivate key of SNMP V3 user. Only chars {a-z,A-Z,0-9, ! ( ) - _ . ? ~ * @ ^ + = : / %} are acceptable. Minimum key length is 8 chars.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.8.1.5
snmpUserRowStatusThe row status of SNMP user table to control row actions. It has the following actions: The status column has six defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `notInService(2)', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady(3)', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo(4)', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait(5)', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy(6)', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.8.1.6
snmpManagerTableThis table is used to display SNMP manager info, such as managerID, EngineID, manager IP addresses, etc. This table's row only can be added or deleted. The existing row can not be modified.
SEQUENCE OF SnmpManagerEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.9
snmpManagerEntryThis is an entry in the Manager table.
SnmpManagerEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.9.1
snmpManagerIndexA unique value for each user entry. This value ranges should be from 1 to 5.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.5.9.1.1
snmpManagerIDSNMP manager ID or name which is used for SNMP v2 or v3 trap or notification.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.9.1.2
snmpManagerAddressSNMP manager IP address. The format should be xxx.xxx.xxx.xxxrw
IpAddress
.1.3.6.1.4.1.9070.1.2.4.6.5.9.1.3
snmpManagerEngineIDThe SNMP management engineID. The format should be 0xDDDDDDDDDDDDDDDD, and minimum length is 14 and maximum length is 32 (including 0x as prefix).rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.9.1.4
snmpManagerRowStatusThe row status of SNMP manager table to control row actions. It has the following actions: The status column has six defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `notInService(2)', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady(3)', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo(4)', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait(5)', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy(6)', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.9.1.5
trapUserTableTrap/Notification user setup. The trap user name should be only for SNMP v3 notification. This table's row only can be added or deleted. The existing row can not be modified.
SEQUENCE OF TrapUserEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.10
trapUserEntryTrap/Notification setup entry.
TrapUserEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.10.1
trapUserIndexA unique value for trapTable entry. This value ranges should be from 1 to 10.
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.5.10.1.1
trapUserNameThe trap user name. The max length of trap user name is 20 characters. Only alphanumeric characters and chars {- , _} are acceptable. Leading characters can't be (- or _).rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.10.1.2
trapUserTypeTrap User type is defined as the follow types: 1 2 3 4 5 6 7rw
UserType
.1.3.6.1.4.1.9070.1.2.4.6.5.10.1.3
trapAuthKeyTrap user authentication key. The max length is 32 characters. Only chars {a-z,A-Z,0-9, ! ( ) - _ . ? ~ * @ ^ + = : / %} are acceptable. Minimum key length is 8 chars.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.10.1.4
trapPrivatekeyTrap user's private key. The max length is 32 characters. Only chars {a-z,A-Z,0-9, ! ( ) - _ . ? ~ * @ ^ + = : / %} are acceptable. Minimum key length is 8 chars.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.10.1.5
trapUserRowStatusTrap User Row Status to control row actions. It has the following actions: The status column has six defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `notInService(2)', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady(3)', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo(4)', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait(5)', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy(6)', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.10.1.6
snmpv2CommunityTableThis table is used to display the valid SNMPv2 community info. All SNMPv2's community should be defined in this table. This table's row only can be added or deleted. The existing row can not be modified.
SEQUENCE OF Snmpv2CommunityEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.11
snmpv2CommunityEntryThis is an entry in the community table. It contains community name and access level.
Snmpv2CommunityEntry
.1.3.6.1.4.1.9070.1.2.4.6.5.11.1
snmpv2IndexA unique value for each user entry. The range of index should be 1 to 10
INTEGER
.1.3.6.1.4.1.9070.1.2.4.6.5.11.1.1
snmpv2CommunityNameSNMPv2 community name. The max length of v2-community is 20 characters. Only alphanumeric characters and chars {- , _} are acceptable. Leading characters can't be (- or _).rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.11.1.2
snmpv2AccessLevelThe number represents the access level. The snmpv2 access level: read(1) (status group), readWrite(2) (status, configuration group).rw
Snmpv2AccessLevel
.1.3.6.1.4.1.9070.1.2.4.6.5.11.1.3
snmpv2UserRowStatusThe row status of SNMP user table to control row actions. It has the following actions: The status column has six defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `notInService(2)', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady(3)', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo(4)', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait(5)', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy(6)', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.11.1.4
trapCommunityDefault trap community for TP5K. Range (1-20) characters. Only alphanumeric characters, '-' and '_' are accepted, except '-' and '_' cannot be leading character. TP5K SNMPv2c and snmpd initiated traps will use this community in the trapsrw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9070.1.2.4.6.5.12
alarmevent
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.6
notifyElements
OBJECT IDENTIFIER
.1.3.6.1.4.1.9070.1.2.4.6.6.1
notifyModuleIdNotification Module IDro
TPModuleID
.1.3.6.1.4.1.9070.1.2.4.6.6.1.1
notifyAlarmEventIDThe alarm or event ID of a notification. These ID values are described in the user's guidero
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.6.1.2
notifyIndexThe internal alarm index of a notification.ro
Unsigned32
.1.3.6.1.4.1.9070.1.2.4.6.6.1.3
notifySeverityAlarm or event severity. 0 2 3 4 5 ::= { notifyElements 4 } notifyTransient OBJECT-TYPE SYNTAX TransientValue MAX-ACCESS read-only STATUS current DESCRIPTIONro
AlarmLevel
.tp50000UocGroups.16
TP5000 - SNMP MIB Reference | MIBs Explorer