TP5000E
This MIB is the equipment-specific subset MIB for the TP5000e system.
Main OID:
tp5000e.1.3.6.1.4.1.9070.1.2.5.7.1
264
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
264 total| Object Name |
|---|
tp5000eThis MIB is the equipment-specific subset MIB for the TP5000e system. MODULE-IDENTITY .1.3.6.1.4.1.9070.1.2.5.7.1 |
tp5000eSystemStatus OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.1 |
tp5000eLedTableThis is a table of the front panel LED status for a specified module. The module can be IMC, IOC1, IOC2, or an expansion shelf. SEQUENCE OF Tp5000eLedEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.1 |
tp5000eLedEntryAn entry of the LED table contains status for one of the LEDs in a specified module. This table has a double index: entPhysicalIndex and tp5000LEDID. Tp5000eLedEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.1.1 |
tp5000eLedIDLED ID are LED names on the module front panel. Currently, the TP5000E system has 14 unique LED names. Some LED names (ALM and MGMT) are used on different module types. IMC LEDs: 1) BT A (battery terminal A-bus power) 2) BT B (battery terminal B-bus power) 3) SYS (system health) 4) ALM (IMC alarm) 5) GNSS/GPS (GNSS/GPS status) 6) MGMT (Ethernet management port) IOC LEDs: 7) ACT (active IOC) 8) Alarm (IOC alarm) 9) ETH1 (Ethernet port 1) 10) ETH2 (Ethernet port 2) 11) Holdover (IOC oscillator status) Expansion shelf LEDs: 13) PWR A (A-bus power) 14) PWR B (B-bus power) 4) ALM (expansion shelf alarm) 6) MGMT (Ethernet management port) 12) REF (reference tracking status)ro TP5000LEDID .1.3.6.1.4.1.9070.1.2.5.7.1.1.1.1.1 |
tp5000eLedStatusLED status can be one of the following: Off(0), On(1), Red(2), Redblink(3), Green(4), Greenblink(5), Amber(6), Amberblink(7)ro TP5000LEDTYPE .1.3.6.1.4.1.9070.1.2.5.7.1.1.1.1.2 |
tp5000eHWStatusTableTable of hardware status for a specified module (IMC, IOC1, IOC2, or an expansion shelf). It includes power supply voltages and other status information for the module hardware. SEQUENCE OF Tp5000eHWStatusEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.2 |
tp5000eHWStatusEntryAn entry of hardware status table. The table index is entPhysicalIndex. Tp5000eHWStatusEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.2.1 |
tp5000eHWStatusIndexLocal index of the TP5000E hardware status table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.1.2.1.1 |
tp5000eHWStatusInfoFor each module, the hardware status information is DisplayString type, and has a list of hardware status (power supply voltages, etc.). Example for IMC: -48V-A : ok -48V-B : ok +1.2V : 1.211V +1.8V : 1.843V +2.5V : 2.526V +5.5V : 5.490V VCXO : 2.526V GPS Power : 5.464V GPS Current : 24mA GPS Antenna : ok FPGA : ok Example for an IOC: +1.8V : 1.805V 10M EFC : 1.116V 20M EFC : 0.872V 25M EFC : 1.155V 24.5M EFC : 1.155V 24.7M EFC : 1.253V OSC Current : 173mA FPGA VCCint : 1.005V FPGA VCCaux : 2.499V FPGA Temp : 60C FPGA Temp High : 61C FPGA Temp Low : 54C Example for an Ethernet expansion shelf: +1.8V : 1.805V 12V : 12.116V 2.5V : 2.572V 1.2V : 1.17V 0.9V : 1.0V 1.0V : 1.1V 5V : 5.01V 1.1A: 1.5A: 2.5A: 1.1B: 1.5B: 2.5B: Temperature : 54C Example for an E1/TOD expansion shelf: +1.8V : 1.805V 5 V : 5.016V 2.5 V : 2.520V 1.2 V : 1.1805V TIM2.5 V : 2.505V 1.0V : 1.053V TIM1.2V : 1.990Vro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.1.2.1.2 |
tp5000eModUpTimeTableModule up time for a specified module (IMC, IOC1, IOC2, or an expansion shelf). SEQUENCE OF Tp5000eModUpTimeEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.3 |
tp5000eModUpTimeEntryAn entry of the module up time table. The table index is entPhysicalIndex. Tp5000eModUpTimeEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.3.1 |
tp5000eModUpTimeIndexLocal index of the module up time table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.1.3.1.1 |
tp5000eModuleUpTimeModule up time status for the module is a DisplayString type. Example for IMC: IMC uptime: 7 days 2 hrs 18 minsro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.1.3.1.2 |
tp5000eModWarmUpTableTable of warm-up status for a specified module (IMC, IOC1, IOC2, or an expansion shelf). SEQUENCE OF Tp5000eModWarmUpEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.4 |
tp5000eModWarmUpEntryAn entry of the module warm-up status table. The table index is entPhysicalIndex. Tp5000eModWarmUpEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.4.1 |
tp5000eModWarmUpIndexLocal index of the module warm-up status table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.1.4.1.1 |
tp5000eModWarmUpStatusModule warm-up status for the module is a DisplayString type. Example for an IOC: IOC1 warm-up status: complete (total 1651 secs)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.1.4.1.2 |
tp5000eModStatusTableTable of operating status for a specified module in the system (IMC, IOC1, IOC2, or an expansion shelf). SEQUENCE OF Tp5000eModStatusEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.5 |
tp5000eModStatusEntryAn entry of the module operating status table. The table index is entPhysicalIndex. Tp5000eModStatusEntry .1.3.6.1.4.1.9070.1.2.5.7.1.1.5.1 |
tp5000eModStatusIndexLocal index of the module general status table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.1.5.1.1 |
tp5000eModStatusInfoA list of operating status parameters for the module. Example for main shelf status information: System name: TP5000 IMC time: 2010-03-08 20:33:30 IMC uptime: 7 days 2 hrs 18 mins IOC1 warmup status: complete (total 1651 secs) IOC1 state: active IOC1 uptime: 7 days 2 hrs 18 mins IOC2 warmup status: n/a IOC2 state: card not present IOC2 uptime: card not present Reference mode: time Current reference input: GPS Phase offset: 0 ns Clock status: normal track PTP mode eth1: multicast grandmaster PTP mode eth2: multicast grandmaster Active alarms: 1 Exp connections: 1,3,6,9 Example for an Ethernet expansion shelf status information: Expansion shelf: PTP-SyncE Shelf time: 2010-03-08 20:33:30 Shelf uptime: 7 days 2 hrs 18 mins Phase Offset: 0 ns Main Clock status: normal track Shelf clock status: normal track Combined Clock status: normal track PTP mode: multicast grandmaster SyncE output PQL: 2 Example of an E1/TOD expansion shelf status information: Expansion shelf: E1-TOD shelf time : 2010-03-08 20:33:30 shelf uptime : 7 days 2 hrs 18 mins Phase offset : 0 ns Main clock status : normal track Shelf clock status: normal track Combined Clock status: normal track E1 output PQL: 2ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.1.5.1.2 |
tp5000eAlarmAndEvent OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.2 |
tp5000eActAlarmTableList of alarms that are still active in the TP5000E system. SEQUENCE OF Tp5000eActAlarmEntry .1.3.6.1.4.1.9070.1.2.5.7.1.2.1 |
tp5000eActAlarmEntryEntry for one active alarm in the active alarm table. The table index is the local index. Tp5000eActAlarmEntry .1.3.6.1.4.1.9070.1.2.5.7.1.2.1.1 |
tp5000eActAlarmIndexThe access (local) index of the active alarm table. The range of the table index is 1 to 500.ro INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.2.1.1.1 |
tp5000eActAlarmModIDName of the hardware module that generated this active alarm. In TP5000E system, the module name can be one of the following: SYS, IMC, IOC1, IOC2, IO, Exp0, Exp1,... Exp9. The module ID is only used to show the module name of a physical entity, but it is never used as an index. Indexing is done using entPhysicalIndex.ro TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.2.1.1.2 |
tp5000eActAlarmIDThe alarm ID uniquely identifies an alarm type. All alarm IDs are listed and described in the User Guide.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.2.1.1.3 |
tp5000eActAlarmInternalIndexSee alarm second index in User Guide.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.2.1.1.4 |
tp5000eActAlarmDateTimeThe date and time stamp for this active alarm. It is the time when the alarm was reported.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.2.1.1.5 |
tp5000eActAlarmSeverityThe alarm severity level can be one of the following: -critical(2), critical condition -major(3), error condition -minor(4), warning condition -event(5), normal but significant conditionro ALARMLEVELTYPE .1.3.6.1.4.1.9070.1.2.5.7.1.2.1.1.6 |
tp5000eActAlarmDescA description for the alarm. For a complete description of all alarms, please see the User Guide. A portion of the alarm and event table is shown below: ID Level State Delay transient Descriptions --------------------------------------------------- 0 critical enable 0 no Communication to peer card failed 1 minor enable 0 no GNSS receiver communications failed 2 minor enable 0 no GNSS receiver not tracking satellite 3 major enable 0 no TOD source invalid 4 event enable 0 yes TOD has been set by TOD source 5 event enable 0 yes System log time has been updatedro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.2.1.1.7 |
tp5000eActEventTableList of events that are still active in the TP5000E system. SEQUENCE OF Tp5000eActEventEntry .1.3.6.1.4.1.9070.1.2.5.7.1.2.2 |
tp5000eActEventEntryAn entry for one active event in the active event table. The table index is the local index. Tp5000eActEventEntry .1.3.6.1.4.1.9070.1.2.5.7.1.2.2.1 |
tp5000eActEventIndexThe access (local) index of the active event table. The range of the table index is 1 to 500.ro INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.2.2.1.1 |
tp5000eActEventModIDName of the hardware module that reported the event. Module ID can be one of the following: SYS, IMC, IOC1, IOC2, or Exp0, Exp1,... Exp9. The module ID is only used to show the module name of a physical entity, but it is never used as an index. Indexing is done using entPhysicalIndex.ro TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.2.2.1.2 |
tp5000eActEventIDThe event ID uniquely identifies an event type. All event IDs are listed and described in the User Guide.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.2.2.1.3 |
tp5000eActEventInternlIndexSee alarm second index in User Guide.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.2.2.1.4 |
tp5000eActEventDateTimeThe date and time stamp for this active event. It is the time when the event was reported.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.2.2.1.5 |
tp5000eActEventDescA description for the event. For a complete description of all events, please see the User Guide.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.2.2.1.6 |
tp5000eAlarmConfigTableThe alarm configuration table. Each alarm is defined by five alarm configuration parameters: alarm id, alarm severity level, delay time, enable state, and a description. SEQUENCE OF Tp5000eAlarmConfigEntry .1.3.6.1.4.1.9070.1.2.5.7.1.2.3 |
tp5000eAlarmConfigEntryEntries of the alarm configuration table. Table index is a local index. Tp5000eAlarmConfigEntry .1.3.6.1.4.1.9070.1.2.5.7.1.2.3.1 |
tp5000eAlarmConfigIndexThe index of the alarm configuration table. The range of the table index is 1 to 500.ro INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.2.3.1.1 |
tp5000eAlarmConfigAIDThis 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.5.7.1.2.3.1.2 |
tp5000eAlarmLevelSettingThe alarm severity level can be one of the following: 2 Critical: critical condition 3 Major: error condition 4 Minor: warning condition 5 Event: normal but significant conditionrw ALARMLEVELTYPE .1.3.6.1.4.1.9070.1.2.5.7.1.2.3.1.3 |
tp5000eAlarmSettingDelayAlarm delay in seconds. The alarm is not reported if the alarm condition disappears before this delay time is up. The purpose of the alarm delay is to prevent reporting intermittent conditions. The range of the alarm delay is 0 to 84,600 seconds. Default value is 0.rw Integer32 UNITS "second" .1.3.6.1.4.1.9070.1.2.5.7.1.2.3.1.4 |
tp5000eEnableAlarmStateAlarm state control flag. The flag can be Enable (1) or Disable (2). The default value is Enable. If an alarm is disabled, the system will never report conditions associated with this alarm.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.2.3.1.5 |
tp5000eAlarmConfigDescAlarm description (from hardcoded alarm definition table).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.2.3.1.6 |
tp5000eNumofStandingAlarmThe total number of currently active alarms in the TP5000E system, including those generated by the expansion shelves.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.2.4 |
tp5000eMessageGenerateThis flag is used to generate all TP5000E alarm and event messages with this one action. The messages are sent to the alarm and event logs. This feature is used for testing purposes. For a message that specifies a port, only one message is generated instead of generating a message for each possible port. This object is actually write-only, but SNMP does not have write-only.rw ONVALUETYPE .1.3.6.1.4.1.9070.1.2.5.7.1.2.5 |
tp5000eGlobalConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.3 |
tp5000eLogFileConfigTableThe log file table is used to configure the sizes of various log files. There are four log files: alarm log, event log, command log, and security log. SEQUENCE OF Tp5000eLogFileConfigEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.1 |
tp5000eLogFileConfigEntryAn entry of the log file configuration table. Table index is the local index. Tp5000eLogFileConfigEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.1.1 |
tp5000eLogFileConfigIndexThe local index of the log file configuration table.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.3.1.1.1 |
tp5000eLogFileTypeNameThe log file name can be one of the following: Alarm, Event, Command, or Security. All alarm messages go into the alarm log. All event messages go into the event log. All user entered commands are recorded in the command log, except those commands related to user login and logout. All user login and logout commands are stored in the security log.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.3.1.1.2 |
tp5000eLogFileBufferSizeThe size for the specified log file. Log file size is specified in unit of Kbytes. The default and the maximum size is 100 KB per log.rw Unsigned32 UNITS "Kbyte" .1.3.6.1.4.1.9070.1.2.5.7.1.3.1.1.3 |
tp5000eRemoteSyslogTableRemote syslog file control table. It is used to configure a remote syslog server to receive log messages from TP5000K system. Only one remote syslog server is supported at this time. SEQUENCE OF Tp5000eRemoteSyslogEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.2 |
tp5000eRemoteSyslogEntryAn entry of the remote syslog file control table. Tp5000eRemoteSyslogEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.2.1 |
tp5000eRemoteSyslogIndexThe local index of the remote syslog file control table. At this time only the index value of 1 is supported.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.3.2.1.1 |
tp5000eRemoteSyslogStateThe remote syslog state control. The setting can be either Enable (1) or Disable (2). Once this is set to Enable, all TP5000E log messages (intended for any of the four built-in logs) will be sent to the remote syslog server.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.3.2.1.2 |
tp5000eRemoteSyslogAddrThe IP address of the remote syslog machine. The format is xxx.xxx.xxx.xxx. It suports only IPv4 format. 0.0.0.0 denotes remote-syslog address is IPv6rw IpAddress .1.3.6.1.4.1.9070.1.2.5.7.1.3.2.1.3 |
tp5000eRedundTableThe port redundancy table for IOC modules. Currently the system is hardcoded for card redundancy. The only redundancy selection is whether to enable port redundancy within a module (port bonding). SEQUENCE OF Tp5000eRedundEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.3 |
tp5000eRedundEntryAn entry of the IOC port redundancy table. Table index is module index Tp5000eRedundEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.3.1 |
tp5000eRedundModuleIDThe module ID can be either IOC1 or IOC2. The system is currently hardcoded for card redundancy (if two IOC cards are present, they are always configured as a redundancy pair, with one active and one on standby). Whichever module ID is used to access this table, the configuration will apply to both IOC cards. In the future when the two IOC cards can be independent, configuration will only apply to the current IOC module.ro TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.3.3.1.1 |
tp5000eRedundModStatePort redundancy state can be either Enable (1) or Disable (2). When it is Enable, the two Ethernet ports on the specified IOC module will form a bonded pair. When two ports are bonded, they share the same IP address, but only one port is active; the other port is in standby mode.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.3.3.1.2 |
tp5000eRedundActivePortThe port ID of the active port on an IOC module. The active port ID is either Eth1 (1) or Eth2 (2). This object can be used to set the desired port to be the active port; the other port automatically becomes the standby port.rw TP5000IOCPORTID .1.3.6.1.4.1.9070.1.2.5.7.1.3.3.1.3 |
tp5000eImageTableFirmware image information for the selected module (IMC, IOC1, IOC2, or an expansion shelf). In TP5000E, each module can store two firmware images. The image that is selected as the active image will be used when the module is booted up next time. Two images are used in upgrading or downgrading. Image downloading is done through CLI only. SEQUENCE OF Tp5000eImageEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.4 |
tp5000eImageEntryEntry of the firmware image table. Each entry contains objects of each module image information. The image table index is the entPhysicalIndex. Tp5000eImageEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.4.1 |
tp5000eImageIndexLocal index of the firmware image table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.3.4.1.1 |
tp5000eImageNextBootThis field indicates whether the board will be booted from this firmware image next time. Values can be either 'yes' or 'no.' Only one of the images can be selected for next boot. The field for the other image is automatically updated accordingly.rw YESVALUETYPE .1.3.6.1.4.1.9070.1.2.5.7.1.3.4.1.2 |
tp5000eImageIDFor each module, there are up to two images. The range of image ID is 1 and 2.ro INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.3.4.1.3 |
tp5000eImageCurrStateThe current state of whether an image active or not. The value is either active (1) or inactive (2).ro TP5000IMAGEACTIVE .1.3.6.1.4.1.9070.1.2.5.7.1.3.4.1.4 |
tp5000eImageInfoMsgThe information message for an image.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.3.4.1.5 |
tp5000eRebootTableThe action to reboot a specified module (IMC, IOC1, IOC2, or an expansion shelf). SEQUENCE OF Tp5000eRebootEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.5 |
tp5000eRebootEntryAn entry contains objects of the module reboot information. The table index is entPhysicalIndex. Depending on the entPhysicalIndex, reboot can apply to the whole system (stack), a chassis, or a module. Tp5000eRebootEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.5.1 |
tp5000eRebootIndexLocal index of the module reboot table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.3.5.1.1 |
tp5000eRebootActionThe action to reboot the module. Value is either Apply (1) or Nonapply (2). The active firmware image is used when the module is rebooted. Use tp5000eImageTable to select the active image.rw ACTIONONLY .1.3.6.1.4.1.9070.1.2.5.7.1.3.5.1.2 |
tp5000eAuthRADIUSTableThis table contains IP addresses and access keys for the Radius authentication server. Radius enable state is set in tp5000eRadiusState outside of this table. SEQUENCE OF Tp5000eAuthRADIUSEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.6 |
tp5000eAuthRADIUSEntryAn entry of the RADIUS table. Tp5000eAuthRADIUSEntry .1.3.6.1.4.1.9070.1.2.5.7.1.3.6.1 |
tp5000eAuthRADIUSIndexA local index to the RADIUS table. Currently the system only supports RADIUS index value of 1.ro INTEGER (1) .1.3.6.1.4.1.9070.1.2.5.7.1.3.6.1.1 |
tp5000eServerRADIUSIPAddressThe RADIUS server's IP address. Format for IPv4 address is xxx.xxx.xxx.xxx. An IP address cannot be set up if authRADIUS key value is none.rw IpAddress .1.3.6.1.4.1.9070.1.2.5.7.1.3.6.1.2 |
tp5000eAuthRADIUSKeyAuthentication key for RADIUS server access.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.3.6.1.3 |
tp5000eAssetNumUser assigned inventory asset number for the system.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.3.7 |
tp5000eIntraCommIPSetIntra-communication IP set between IMC, IOCs and Expansion shelves. Value can be class A (1), B (2), C (3). Their ranges are: A: IP address range 10.0.250.8 to 10.0.250.47 B: IP address range 172.16.250.8 to 172.16.250.47, C: IP address range 192.168.250.8 to 192.168.250.47 The selected address set cannot be used for external Ethernet ports in this TP5000 system. Therefore, choose a set that does not conflict with the external network configuration. After the value is changed, IMC and IOC or expansion shelves will establish a new connection in 1 to 2 minutes.rw TP5000INTRAIPSET .1.3.6.1.4.1.9070.1.2.5.7.1.3.8 |
tp5000eRadiusStateThe RADIUS state can be either Enable (1) or Disable (2). Use tp5000eAuthRadiusTable to configure access to the Radius server.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.3.9 |
tp5000eLastConfigThe Last Config Update.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.3.10 |
tp5000eGlobalService OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.4 |
tp5000ePacketServiceTableThis table defines packet service for the specified Ethernet interface on the IOC (main shelf). Currently, this table only applies to the main shelf IOC ports (Eth1 and Eth2); the Ethernet expansion shelves are currently fixed to provide 'PTP grandmaster over Ethernet.' SEQUENCE OF Tp5000ePacketServiceEntry .1.3.6.1.4.1.9070.1.2.5.7.1.4.1 |
tp5000ePacketServiceEntryAn entry of the packet service table. Table index is ifIndex (index for interfaces and ports). The system is currently hardcoded for card redundancy (if two IOC cards are present, they are always configured as a redundancy pair, with one active and one on standby). Regardless of which IOC card ifIndex is used, the configuration will apply to both IOC cards. In the future when the two IOC cards can be independent, configuration will only apply to the IOC module with the current ifIndex. Tp5000ePacketServiceEntry .1.3.6.1.4.1.9070.1.2.5.7.1.4.1.1 |
tp5000ePacketServiceIndexLocal index of the packet service selection table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.4.1.1.1 |
tp5000ePacketServiceModeThe packet service for this port. Value can be PTP Grandmaster (1), PTP probe (2), NTP server (3), or NTP probe (4). Note that packet service selection is done for each port, and the two Ethernet ports on the IOC can have different services.rw TP5000PACKETSERVICE .1.3.6.1.4.1.9070.1.2.5.7.1.4.1.1.2 |
tp5000eSSMOptionTableThis is the table for selecting SSM network option for a specified shelf (IOC or Expansion shelf). Main shelf and expansion shelves can each have its own selection of SSM network options. SEQUENCE OF Tp5000eSSMOptionEntry .1.3.6.1.4.1.9070.1.2.5.7.1.4.2 |
tp5000eSSMOptionEntryAn entry of the SSM option table. Table index is entPhysicalIndex. Tp5000eSSMOptionEntry .1.3.6.1.4.1.9070.1.2.5.7.1.4.2.1 |
tp5000eSSMOptionIndexLocal index of the SSM option selection table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.4.2.1.1 |
tp5000eSSMOptionNetwork option for SSM can be Option 1 (1) or Option 2 (2). Option 1 is for E1 based network. Option 2 is for DS1 based network. ITU-T G.781 and G.8265.1 specifies different SSM (QL) values for Option 1 and Option 2 networks.rw TP5000SSMOPTION .1.3.6.1.4.1.9070.1.2.5.7.1.4.2.1.2 |
tp5000ePTPClientDataTableLockThe ptpClientDataTableLock will control the internal semaphore to lock or unlock the ptpClientDataTable. The table must be locked before it can be read. When the ptpClientDataTable is locked, the data in the table will not change. The ptpClientDataTableLock can be set up 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.rw Enumeration .1.3.6.1.4.1.9070.1.2.5.7.1.4.3 |
tp5000ePacketServiceExtendedModeFixed configuration. IOC1-1: PTP-GM IOC1-2: NTP-Serverrw Enumeration .1.3.6.1.4.1.9070.1.2.5.7.1.4.4 |
tp5000ePTPClientMgmt OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.5 |
tp5000eReferenceStatus OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.6 |
tp5000eInputPQLTableStatus table for a specified reference input. PQL (priority quality level) is reference quality used internally by the TP5000E system. Input SSM and other reference quality indicators are first mapped to PQL, and further processing is carried out using PQL. SEQUENCE OF Tp5000eInputPQLEntry .1.3.6.1.4.1.9070.1.2.5.7.1.6.1 |
tp5000eInputPQLEntryAn entry of the reference input status table. Index of the table is ifIndex. Tp5000eInputPQLEntry .1.3.6.1.4.1.9070.1.2.5.7.1.6.1.1 |
tp5000eInputRefNameThe name of the reference. Currently supported references are GNSS, GPS, 1PPS+TOD1, 1PPS+TOD2, Span input 1, and Span input 2.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.6.1.1.1 |
tp5000eInputRefActualPQLThis PQL value either corresponds to the actual SSM value in the reference (when SSM is available) or the default PQL value for the reference.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.6.1.1.2 |
tp5000eInputRefQualifiedThis is the selection status for the reference. Its value is one of the following: Disabled, Disqualified, Qualified, or Selected.ro TP5000REFQUALIFICATION .1.3.6.1.4.1.9070.1.2.5.7.1.6.1.1.3 |
tp5000eSymmMetrics OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.6.2 |
tp5000eRefConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.7 |
tp5000eRefTimingModeThe timing mode of the entire TP5000E system, and it can be either Time (1) or Frequency (2). Whether the system is in Time or Frequency mode affects how time and frequency references are used in reference selection. A time reference has both frequency and time-of-day (TOD) information and can be used for both time and frequency synchronization. Examples of time references are: GNSS, GPS, 1PPT+TOD, and PTP. A frequency reference does not have TOD information and can be used only for frequency synchronization. Examples of frequency references are: 2048 kHz, 2048 kbps, 1544 kHz, 1544 kbps, SyncE, and 10 MHz.rw TP5000REFTIMINGMODE .1.3.6.1.4.1.9070.1.2.5.7.1.7.1 |
tp5000eRefSelectionCriteriaReference selection criteria applies to the entire TP5000E system, and it can be Priority based (2) or SSM based (3). Manual mode (1) is currently not supported. References are assigned priorities and PQL values, either by default or by user input. PQL values used to relate only to SSM values of E1/T1/SynE signals, but now PQL also covers time signals such as GNSS, GPS, and 1PPS+TOD. For a mapping for currently supported references, please see the user guide.rw TP5000REFSELECTMODE .1.3.6.1.4.1.9070.1.2.5.7.1.7.2 |
tp5000eRefConfigTableThe reference configuration table is used to configure reference selection parameters for a specified reference input. Configuration parameters include reference name, reference enable state, reference priority, reference PQL enable state, and user configured PQL value. PQL (priority quality level) is reference quality used internal by the TP5000E system. Input SSM and other reference quality indicators are first mapped to PQL, and further processing is carried out using PQL. SEQUENCE OF Tp5000eRefConfigEntry .1.3.6.1.4.1.9070.1.2.5.7.1.7.3 |
tp5000eRefConfigEntryAn entry of the reference configuration table. Table index is the ifIndex (port index). Tp5000eRefConfigEntry .1.3.6.1.4.1.9070.1.2.5.7.1.7.3.1 |
tp5000eRefNameName of the reference. Examples: GNSS, GPS, E1, 1PPS+TOD.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.7.3.1.1 |
tp5000eRefStateReference input state can be either Enable (1) or Disable (2). Only enabled references are used in reference selection.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.7.3.1.2 |
tp5000eRefPriorityPriority value assigned to a reference. Its range is 1 to 16. It is used as one of the selection criteria for reference selection.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.7.3.1.3 |
tp5000eRefPQLStateThe PQL state of a reference can be either Enable (1) or Disable (2). If PQL is enabled for a reference, the actual PQL value that the system uses either corresponds to the reference SSM value (when SSM is available) or is the default PQL value (when SSM is not available). If the PQL is disabled, the actual PQL value that the system uses matches the user configured reference PQL value (tp5000eRefPQL).rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.7.3.1.4 |
tp5000eRefPQLConfigured reference PQL value. Its range is 1 to 3, with 1 indicating the highest quality level. This PQL value is used when the reference PQL state is disabled, meaning 'do not use the PQL that comes with the reference but use this value.' This value along with disabling the PQL state is used to override the input PQLrw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.7.3.1.5 |
tp5000eClock OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.8 |
tp5000eClockStatus OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.8.1 |
tp5000eClockStatusTableThis table contains status information for the clock in each shelf. SEQUENCE OF Tp5000eClockStatusEntry .1.3.6.1.4.1.9070.1.2.5.7.1.8.1.1 |
tp5000eClockStatusEntryAn entry in the Clock Status Table. Table index is entPhysicalIndex (a shelf or a module). Tp5000eClockStatusEntry .1.3.6.1.4.1.9070.1.2.5.7.1.8.1.1.1 |
tp5000eClockStatusIndexLocal index of the module clock status table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.8.1.1.1.1 |
tp5000eServoControlStatusThe clock servo status of clock module (IOC or expansion). This status is also called clock status in CLI. For expansion shelves, the clock status is the combined status of the cascaded main shelf clock and the expansion shelf clock. The clock status can be one of the following: (1) Warm-up (2) Free-run (3) Fast-track (4) Normal track (5) Holdover (6) Bridging (7) Fail (8) Offline (9) Extended holdover (10) Local free-run (11) Local holdoverro TP5000SERVOCTL .1.3.6.1.4.1.9070.1.2.5.7.1.8.1.1.1.2 |
tp5000ePhaseOffsetThis is the phase offset in ns between the reference and output. This is applicable only when the selected reference is a time reference.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.8.1.1.1.3 |
tp5000eClockConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.8.2 |
tp5000eBridgingTimeBridging time in seconds. Range 100-200000. Default value Bridging is a clock state between normal tracking and holdover. When all references are lost, the clock declares that it is going into holdover after the bridging time has elapsed. During bridging, the clock maintains its specification for tracking. Default value is 900rw Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.8.2.1 |
tp5000eAutoSyncThe auto sync state can be either Enable (1) or Disable (2). Auto sync allows IOC time and IMC time to synchronize when IOC is in time mode passed warmup. If auto sync is disabled, an alarm will be generated when IOC and IMC times are not synchronized. Use tp5000eSync to remove this alarm condition.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.8.2.2 |
tp5000eSyncThis object is used to force system time and phase to synchronize to the selected reference (synchronize between IMC and IOC). This object is write-only, and the value must be 'now.'rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.8.2.3 |
tp5000eHoldoverExceededTimeQzholdover time in seconds for holdover-exceeded-time-qz, Range (0|900-3000000). 0 is disablerw Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.8.2.4 |
tp5000eHoldoverExceededTimeRbholdover time in seconds for holdover-exceeded-time-rb, Range (0|900-3000000). 0 is disablerw Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.8.2.5 |
tp5000eHardwareHierarchy OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.9 |
tp5000eIfTableThis table describes physical hierarchy of TP5000E system down to the individual logical interface which can be a physical interface (like GPS port) or a virtual interface (like VLANs at an Ethernet port). SEQUENCE OF Tp5000eIfEntry .1.3.6.1.4.1.9070.1.2.5.7.1.9.1 |
tp5000eIfEntryAn entry of the TP5000E interface table. Table index is ifIndex. Tp5000eIfEntry .1.3.6.1.4.1.9070.1.2.5.7.1.9.1.1 |
tp5000eIfIndexLocal index of this table.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.9.1.1.1 |
tp5000eIfModuleIDModule ID is the name of the physical module. Its value can be one of the following: IMC (2), IOC1 (3), IOC2 (4), IO (5), exp0 (6),... exp9 (15). Module ID is only used to show the name of a physical module. It is not used as an index or sorting key.ro TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.9.1.1.2 |
tp5000eIfPortIDThe current inventory port ID. The range depends on the module ID and P/N index that together uniquely identify port configuration for each module. Example: range for IOC port ID is {1, 2}, and range for E1 expansion shelf is {1... 28}.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.9.1.1.3 |
tp5000eIfTableIndexThe current interface index from ifTable. Each local index is mapped to a corresponding index in the ifTable.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.9.1.1.4 |
tp5000eEntPhysicalTableThis table describes physical hierarchy of TP5000K system down to the module (container) level. SEQUENCE OF Tp5000eEntPhysicalEntry .1.3.6.1.4.1.9070.1.2.5.7.1.9.2 |
tp5000eEntPhysicalEntryAn entry of the TP5000E physical entity table. Each entry uniquely identifies the connector configuration (a module may have multiple versions with different connectors). Tp5000eEntPhysicalEntry .1.3.6.1.4.1.9070.1.2.5.7.1.9.2.1 |
tp5000eEntPhysicalIndexLocal index of the TP5000E physical entity table.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.9.2.1.1 |
tp5000eEntPhysicalModuleIDModule ID is the name of the physical module. Its value can be one of the following: IMC (2), IOC1 (3), IOC2 (4), IO (5), exp0 (6),... exp9 (15). Module ID is only used to show the name of a physical module. It is not used as an index or sorting key.ro TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.9.2.1.2 |
tp5000eEntPhysicalStackIDStack ID is the ID of the TP5000E system that the current module resides in. Stack ID is currently hardcoded to 1, and NMS needs to use other means (such as IP address) to identify each TP5000E system.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.9.2.1.3 |
tp5000eEntPhysicalChassisIDChassis ID is the equipment shelf ID. In TP5000E system, there is one main shelf (chassis ID = 1) and up to ten expansion shelves (chassis ID range 2 to 11).ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.9.2.1.4 |
tp5000eEntPhysicalPartIndexPart number index uniquely identifies the connector configuration of a given module type. Currently, there are four versions of IMC, and the valid part number index value for IMC are IMC-1 (1), IMC-2 (2), IMC-3 (3), and IMC-4 (4). IOC only has two versions (Rb or Qz), and the valid part number index values for IOC are IOC-Rb (1) and IOC-Qz (2). There are four versions of I/O module, and therefore the range of the I/O module part number index is {1... 4}. Each type of expansion shelf currently does not have multiple versions, so their valid part number index value is only 1 at this time.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.9.2.1.5 |
tp5000eEntPhysicalTableIndexEach entry (module) in this table is mapped to an entity index in the entityPhysicalTable in the Entity-MIB.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.9.2.1.6 |
tp5000eVlanConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.10 |
tp5000eNonfixedVlanTableIn the non-fixed VLAN table, VLANs can be added or removed. As a VLAN is added or removed, the table index is updated. The non-fixed VLAN table can hold 484 VLANs (with IfIndex 17 to 500). SEQUENCE OF Tp5000eNonfixedVlanEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.1 |
tp5000eNonfixedVlanEntryAn entry of the non-fixed VLAN table. Table index is the local index, but each entry uniquely identifies a VLAN through the IfIndex. Tp5000eNonfixedVlanEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1 |
tp5000eNonfixedVlanIndexLocal index of the non-fixed VLAN table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.1 |
tp5000eNonfixedVlanIfIndexIfIndex of the current non-fixed VLAN (17-500).ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.2 |
tp5000eNonfixedVlanModuleIDModule ID is the name of the physical module (the inventory module ID) in which the current non-fixed VLAN is defined. Module ID is the name of the physical module. Its value can be one of the following: IMC (2), IOC1 (3), IOC2 (4), IO (5), exp0 (6),... exp9 (15). Module ID is only used to show the name of a physical module. It is not used as an index or sorting key.rw TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.3 |
tp5000eNonfixedVlanPortIDPhysical port ID where the current non-fixed VLAN is defined. The range depends on the module ID and P/N index which together uniquely identify port configuration for each module. Example: range for IOC port ID is {1, 2}, and range for E1 expansion shelf is {1... 28}.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.4 |
tp5000eNonfixedVlanIdThe VLAN ID of the current VLAN interface. The range is 0~4094. If a VLAN ID is set to 0, the associated VLAN interface of this VLAN index will be removed from the internal VLAN table. The default VLAN ID of each VLAN interface in the VLAN table is 0. The VLAN ID can be set up only once. The VLAN ID and VLAN Priority must be configured at same time when a VLAN interface row is added. Once a VLAN ID is defined, it cannot be modified. To change it, set the VLAN ID to 0 (deleting the VLAN from the VLAN table) and create a new VLAN row.rw INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.5 |
tp5000eNonfixedVlanPriorityThe priority of the VLAN ID. The range is 0 to 7. VLAN priority and VLAN ID must be configured at same time when a VLAN interface row is added. Once a VLAN priority is defined, it cannot be modified. To change it, set the VLAN ID to 0 (deleting the VLAN from the VLAN table), and create a new VLAN row.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.6 |
tp5000eNonfixedVlanIPv4AddrThe IPv4 address to which this entry's addressing information pertains. Implementers need to be aware that if the size of ipAddressAddr exceeds 116 octets, OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.rw IpAddress .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.7 |
tp5000eNonfixedVlanNetmaskThe mask of an IPv4 interface. The address format is : xxx.xxx.xxx.xxx.rw IpAddress .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.8 |
tp5000eNonfixedVlanStateThis is the state of an individual non-fixed VLAN. Value can be Enable (1) or Disable (2). Setting an individual VLAN state to Enable is not enough for the VLAN to become active. The physical VLAN mode must also be set to Enable (see tp5000eVlanModeTable).rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.10.1.1.9 |
tp5000eNonfixedVlanRowStatusThe row status of non-fixed VLAN table is used to control row actions. The status column has six defined actions (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; -`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.5.7.1.10.1.1.10 |
tp5000eFixedVlanTableIn the fixed VLAN table, VLANs are pre-assigned to the VLAN table index. They cannot be added or removed from the table. SEQUENCE OF Tp5000eFixedVlanEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.2 |
tp5000eFixedVlanEntryAn entry of the fixed VLAN table. Table index is ifIndex and local index. Tp5000eFixedVlanEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.2.1 |
tp5000eFixedVlanIndexLocal index of the fixed VLAN table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.2.1.1 |
tp5000eFixedVlanIdThe VLAN ID of the current VLAN interface. The range is 0~4094. If a VLAN ID is set to 0, the associated VLAN interface of this VLAN index will be removed from the internal VLAN table. The default VLAN ID of each VLAN interface in the VLAN table is 0. The VLAN ID can be setup only once. The VLAN ID and VLAN Priority must be configured at same time when a VLAN interface row is added. Once a VLAN ID is defined, it cannot be modified. To change it, set the VLAN ID to 0 (deleting the VLAN from the VLAN table) and create a new VLAN row.rw INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.10.2.1.2 |
tp5000eFixedVlanPriorityThe priority of the VLAN ID. The range is 0 to 7. VLAN priority and VLAN ID must be configured at same time when a VLAN interface row is added. Once a VLAN priority is defined, it cannot be modified. To change it, set the VLAN ID to 0 (deleting the VLAN from the VLAN table), and create a new VLAN row.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.2.1.3 |
tp5000eFixedVlanIPv4AddrThe IPv4 address to which this entry's addressing information pertains. Implementers need to be aware that if the size of ipAddressAddr exceeds 116 octets, OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.rw IpAddress .1.3.6.1.4.1.9070.1.2.5.7.1.10.2.1.4 |
tp5000eFixedVlanNetmaskThe mask of an IPv4 interface. The address format is : xxx.xxx.xxx.xxx.rw IpAddress .1.3.6.1.4.1.9070.1.2.5.7.1.10.2.1.5 |
tp5000eFixedVlanGatewayThe gateway of an IPv4 interface. The address format is : xxx.xxx.xxx.xxx.rw IpAddress .1.3.6.1.4.1.9070.1.2.5.7.1.10.2.1.6 |
tp5000eFixedVlanStateThis is the state of an individual fixed VLAN. Value can be Enable (1) or Disable (2). Setting an individual VLAN state to Enable is not enough for the VLAN to become active. The physical port VLAN mode must also be set to Enable (see tp5000eVlanModeTable).rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.10.2.1.7 |
tp5000eVlanModeTableVLAN mode table. The VLAN mode table is used to enable or disable all VLANs in a physical port. SEQUENCE OF Tp5000eVlanModeEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.3 |
tp5000eVlanModeEntryAn entry of the VLAN mode table. Table index is ifIndex (port and interface index) and local index. Tp5000eVlanModeEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.3.1 |
tp5000eVlanModeIndexLocal index of the VLAN mode table. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.3.1.1 |
tp5000eVlanModeModuleIDModule ID is the name of the physical module (the inventory module ID) in which the current VLAN is defined. Module ID is the name of the physical module. Its value can be one of the following: IMC (2), IOC1 (3), IOC2 (4), IO (5), exp0 (6),... exp9 (15). Module ID is only used to show the name of a physical module. It is not used as an index or sorting key.ro TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.10.3.1.2 |
tp5000eVlanModePortIDPhysical port ID where the current VLAN is defined.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.3.1.3 |
tp5000eVlanModeValueVLAN mode for the specified physical port. Value can be Enable or Disable. This parameter can enable or disable all VLANs in this physical port, but setting the physical port VLAN mode to Enable is not enough for an individual VLAN to become active. That individual VLAN must also be enabled (see tp5000eVlanNonfixedVlanPortState and tp5000eVlanFixedVlanPortState).rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.10.3.1.4 |
tp5000eIPv6NonfixedVlanTableDescription. SEQUENCE OF Tp5000eIPv6NonfixedVlanEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.4 |
tp5000eIPv6NonfixedVlanEntryDescription. Tp5000eIPv6NonfixedVlanEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1 |
tp5000eIPv6NonfixedVlanIndexDescription. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.1 |
tp5000eIPv6NonfixedVlanIfIndexDescription.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.2 |
tp5000eIPv6NonfixedVlanModuleIDDescription.rw TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.3 |
tp5000eIPv6NonfixedVlanPortIDDescription.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.4 |
tp5000eIPv6NonfixedVlanIdDescription.rw INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.5 |
tp5000eIPv6NonfixedVlanPriorityDescription.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.6 |
tp5000eIPv6NonfixedVlanAddrDescription.rw InetAddressIPv6 (INET-ADDRESS-MIB) .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.7 |
tp5000eIPv6NonfixedVlanPrefixDescription.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.8 |
tp5000eIPv6NonfixedVlanStateDescription.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.9 |
tp5000eIPv6NonfixedVlanRowStatusDescription.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.10.4.1.10 |
tp5000eIPv6FixedVlanTableDescription. SEQUENCE OF Tp5000eIPv6FixedVlanEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.5 |
tp5000eIPv6FixedVlanEntryDescription. Tp5000eIPv6FixedVlanEntry .1.3.6.1.4.1.9070.1.2.5.7.1.10.5.1 |
tp5000eIPv6FixedVlanIndexDescription. Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.5.1.1 |
tp5000eIPv6FixedVlanIdDescription.rw INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.10.5.1.2 |
tp5000eIPv6FixedVlanPriorityDescription.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.5.1.3 |
tp5000eIPv6FixedVlanAddrDescription.rw InetAddressIPv6 (INET-ADDRESS-MIB) .1.3.6.1.4.1.9070.1.2.5.7.1.10.5.1.4 |
tp5000eIPv6FixedVlanPrefixDescription.rw Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.10.5.1.5 |
tp5000eIPv6FixedVlanDefaultRouterDescription.rw InetAddressIPv6 (INET-ADDRESS-MIB) .1.3.6.1.4.1.9070.1.2.5.7.1.10.5.1.6 |
tp5000eIPv6FixedVlanStateDescription.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.10.5.1.7 |
tp5000eAlarmNotification OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.11 |
tp5000eNotifyElements OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.11.1 |
tp5000eNotifyModuleIdModule ID is the name of the physical module that generated the notification.ro TP5000MODULEID .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.1 |
tp5000eNotifyAlarmEventIDThe alarm or event ID of the notification.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.2 |
tp5000eNotifyIndexInternal alarm index for a notification.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.3 |
tp5000eNotifySeverityAlarm severity: 0 - clear alarm or event 2 - critical alarm (set, if non-transient) 3 - major alarm (set, if non-transient) 4 - minor alarm (set, if non-transient) 5 - report event (set, if non-transient)ro ALARMLEVELTYPE .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.4 |
tp5000eNotifyTransientThe transient state of an alarm or event. It is either a state event (non-transient) or a transient event (transient).ro TP5000TRANSIENT .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.5 |
tp5000eNotifyDateTimeDate and time of the notification.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.6 |
tp5000eNotifyDescriptionDescription of this alarm or event (from the TP5000 internal alarm/event definition table).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.7 |
tp5000eNotifyClientAddrThe IPv4 address of TP5000's PTP client that generated the notification.ro IpAddress .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.8 |
tp5000eNotifySequenceNumThe sequence number of a notification. Each notification OID (tp5000TrapAlarm, tp5000TrapEvent, and tp5000ClientNotification) has an independently incrementing sequence number. These are reset when the IMC is rebooted.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.9 |
tp5000eNotifyClientClockIDClock ID of the TP5000's PTP client that generated the notification.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.11.1.10 |
tp5000eTrapAlarmTimeProvider 5000 alarm trap for the current notification. It contains the OID and value for module ID, alarm ID, notify index, severity, transient, date and time, severity, descriptions, and sequence number. OID names are defined in tp5000eNotifyElements. NOTIFICATION-TYPE .1.3.6.1.4.1.9070.1.2.5.7.1.11.2 |
tp5000eTrapEventTimeProvider 5000 event trap for the current notification. It contains the OIDs and values for module ID, event ID, notify index, severity, transient, date and time, severity, descriptions, and sequence number. OID names are defined in tp5000eNotifyElements. NOTIFICATION-TYPE .1.3.6.1.4.1.9070.1.2.5.7.1.11.3 |
tp5000eClientNotificationTimeProvider 5000 PTP client trap for the current client notification. It contains the OID and value for alarm ID, index, severity, transient, date and time and descriptions, client IP address, client clock id, sequence number. OID names are defined in tp5000eNotifyElements. NOTIFICATION-TYPE .1.3.6.1.4.1.9070.1.2.5.7.1.11.4 |
tp5000ePtpMgmtEventDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.9070.1.2.5.7.1.11.5 |
tp5000eIPv6GlobalConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.12 |
snmpIPv4IPv6ManagerTableThis 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 SnmpIPv4IPv6ManagerEntry .1.3.6.1.4.1.9070.1.2.5.7.1.12.1 |
snmpIPv4IPv6ManagerEntryThis is an entry in the Manager table. SnmpIPv4IPv6ManagerEntry .1.3.6.1.4.1.9070.1.2.5.7.1.12.1.1 |
snmpIPv4IPv6ManagerIndexA unique value for each user entry. This value ranges should be from 1 to 3. INTEGER .1.3.6.1.4.1.9070.1.2.5.7.1.12.1.1.1 |
snmpIPv4IPv6ManagerIDSNMP 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.5.7.1.12.1.1.2 |
snmpIPv4IPv6ManagerAddressSNMP manager IP address. It can be IPv4 IPv6rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.12.1.1.3 |
snmpIPv4IPv6ManagerEngineIDThe SNMP management engineID. The format should be 0xDDDDDDDDDDDDDDDD, and minimum length is 14 and maximum length is 32 (including 0x as prefix).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.12.1.1.4 |
snmpIPv4IPv6ManagerRowStatusThe 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.5.7.1.12.1.1.5 |
tp5000eIPv4IPv6RemoteSyslogTableRemote syslog file control table. It is used to configure a remote syslog server to receive log messages from TP5000K system. Only one remote syslog server is supported at this time. SEQUENCE OF Tp5000eIPv4IPv6RemoteSyslogEntry .1.3.6.1.4.1.9070.1.2.5.7.1.12.2 |
tp5000eIPv4IPv6RemoteSyslogEntryAn entry of the remote syslog file control table. Tp5000eIPv4IPv6RemoteSyslogEntry .1.3.6.1.4.1.9070.1.2.5.7.1.12.2.1 |
tp5000eIPv4IPv6RemoteSyslogIndexThe local index of the remote syslog file control table. At this time only the index value of 1 is supported.ro Integer32 .1.3.6.1.4.1.9070.1.2.5.7.1.12.2.1.1 |
tp5000eIPv4IPv6RemoteSyslogStateThe remote syslog state control. The setting can be either Enable (1) or Disable (2). Once this is set to Enable, all TP5000E log messages (intended for any of the four built-in logs) will be sent to the remote syslog server.rw EnableValue .1.3.6.1.4.1.9070.1.2.5.7.1.12.2.1.2 |
tp5000eIPv4IPv6RemoteSyslogAddrThe IP address of the remote syslog machine. It can be IPv4 or IPv6rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.12.2.1.3 |
tp5000eIPv4IPv6AuthRADIUSTableThis table contains IP addresses and access keys for the Radius authentication server. Radius enable state is set in tp5000eRadiusState outside of this table. SEQUENCE OF Tp5000eIPv4IPv6AuthRADIUSEntry .1.3.6.1.4.1.9070.1.2.5.7.1.12.3 |
tp5000eIPv4IPv6AuthRADIUSEntryAn entry of the RADIUS table. Tp5000eIPv4IPv6AuthRADIUSEntry .1.3.6.1.4.1.9070.1.2.5.7.1.12.3.1 |
tp5000eIPv4IPv6AuthRADIUSIndexA local index to the RADIUS table. Currently the system only supports RADIUS index value of 1.ro INTEGER (1) .1.3.6.1.4.1.9070.1.2.5.7.1.12.3.1.1 |
tp5000eIPv4IPv6ServerRADIUSIPAddressThe RADIUS server's IP address. It can be IPv4 or IPv6. An IP address cannot be set up if authRADIUS key value is none.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.12.3.1.2 |
tp5000eIPv4IPv6AuthRADIUSKeyAuthentication key for RADIUS server access.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9070.1.2.5.7.1.12.3.1.3 |
tp5000eConformanceThis subtree contains conformance statements for the Tp5000e MIB module. OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.13 |
tp5000eCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.13.1 |
tp5000eBasicComplianceDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.1.1 |
tp5000eUocGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.5.7.1.13.2 |
tp5000eLEDGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.1 |
tp5000eHWGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.2 |
tp5000eModeUpTimeGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.3 |
tp5000eModWarmUpGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.4 |
tp5000eModStatusGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.5 |
tp5000eActiveAlarmGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.6 |
tp5000eActiveEventGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.7 |
tp5000eAlarmConfigGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.8 |
tp5000eGeneralAlarmGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.9 |
tp5000eLogFileConfigGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.10 |
tp5000eRemoteSyslogGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.11 |
tp5000eRedundGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.12 |
tp5000eImageGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.13 |
tp5000eRebootGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.15 |
tp5000eRadiusGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.16 |
tp5000eAssetGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.17 |
tp5000ePacketServiceGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.18 |
tp5000eReferenceStatusGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.19 |
tp5000eReferenceConfigGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.20 |
tp5000eClockStatusGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.21 |
tp5000eClockConfigGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.22 |
tp5000eModuleIfGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.23 |
tp5000eModuleEntityGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.24 |
tp5000eFixedVlanGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.25 |
tp5000eNonfixedVlanGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.26 |
tp5000eNotifyGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.27 |
tp5000eNotificationGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.28 |
tp5000eVlanModeGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.29 |
tp5000eLastConfigGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.30 |
tp5000eIPv6NonfixedVlanGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.31 |
tp5000eIPv6FixedVlanGroupDescription. Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.32 |
tp5000eIPv4IPv6SnmpManagerGroupElements of tp5000eIPv4IPv6SnmpManagerTable Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.33 |
tp5000eIPv4IPv6RemoteSyslogGroupElements of tp5000eIPv4IPv6RemoteSyslogTable Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.34 |
tp5000eIPv4IPv6AuthRADIUSGroupElements of tp5000eIPv4IPv6ServerRADIUSTable Unknown .1.3.6.1.4.1.9070.1.2.5.7.1.13.2.35 |