RS-XX8000-COMMON-MIB: View SNMP OID List / Download MIB

VENDOR: ROHDE N SCHWARZ


 Home MIB: RS-XX8000-COMMON-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, RS-COMMON-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
     rsXx8000 1.3.6.1.4.1.2566.127.1.2.167
The subtree for all transmitters of series 8000.
             rsXx8000Common 1.3.6.1.4.1.2566.127.1.2.167.1
This is the subtree for values which every equipement of series 8000 suports.
                 rsXx8000CommonObjs 1.3.6.1.4.1.2566.127.1.2.167.1.1
                     productInformation 1.3.6.1.4.1.2566.127.1.2.167.1.1.1
                         serialNumber 1.3.6.1.4.1.2566.127.1.2.167.1.1.1.2 readablestring read-only
The serial number of the device.
                         identNumberSW 1.3.6.1.4.1.2566.127.1.2.167.1.1.1.3 readablestring read-only
The Rohde&Schwarz identification number of the software, for example 2094.2090.02.
                         versionNumberSW 1.3.6.1.4.1.2566.127.1.2.167.1.1.1.4 readablestring read-only
The Rohde&Schwarz revision number of the software, for example 1.2.1.
                         identNumberHW 1.3.6.1.4.1.2566.127.1.2.167.1.1.1.5 readablestring read-only
The Rohde&Schwarz identification number of the hardware, for example 2095.8007.02 (NetCCU).
                         versionNumberHW 1.3.6.1.4.1.2566.127.1.2.167.1.1.1.6 readablestring read-only
The Rohde&Schwarz revision number (product index) of the hardware, for example 03.03.
                     snmpConfig 1.3.6.1.4.1.2566.127.1.2.167.1.1.2
                         trapSinkTable 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2 no-access
This table is for configuration of trapsinks - the IP-addresses where traps/informs are sent to. This table gives you possibility for easier remote configuration of trapsinks. Another way, which is predefined by IETF, is to use the MIBs SNMP-TARGET and SNMP-NOTIFICATION.
                             trapSinkEntry 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1 no-access
An entry for a trapsink.
                                 trapSinkNumber 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.1 integer32 no-access
The arbitrary number in the list.
                                 trapSinkVersion 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.2 integer read-write
The SNMP-version of sent out alarm. 1: v1Trap 2: v2Trap 3: v2Inform Enumeration: 'v2Inform': 3, 'v1Trap': 1, 'v2Trap': 2.
                                 trapSinkAddress 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.3 ipaddress read-write
The IP-Address of the SNMP manager to which the alarms are sent to.
                                 trapSinkPort 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.4 integer32 read-write
The port of the SNMP manager to which the alarms are sent to.
                                 trapSinkCommunity 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.5 readablestring read-write
community used in alarm
                                 trapSinkInformRetry 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.6 integer32 read-write
only used for informs: number of times to resend the inform
                                 trapSinkInformTimeout 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.7 integer32 read-write
only used for informs: timeout between retries
                                 trapSinkInformUnacknowledged 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.8 integer32 read-write
only used for informs: maximum number of waiting informs if this is reached, the oldest pending inform is discarded
                                 trapSinkUse 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.9 truthvalue read-write
on/off-switch for this sink
                         sendTestTrap 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.3 trigger read-write
1: idle 2: Agent generates the trap 'testTrap', which is useful when checking the connection between agent (NetCCU) and your trapsink.
                         irtTrapsAllOn 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.4 trigger read-write
This switches all IRT-traps on - traps for all events are sent out. In detail, this means in the IRT-MIBs under branches *EventEnable all OIDs are set to 1. Caution! Setting this value influences remote controlling of devices. Too many alarms may flood your network. Use this only for testing - for operation, we suggest switch on only a few important traps.
                         irtTrapsAllOff 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.5 trigger read-write
This switches all IRT-traps off - no traps are sent out. In detail, this means in the IRT-MIBs under branches *EventEnable all OIDs are set to 2. Note: This is typically set when using only R&S-MIBs and you don't need IRT-MIBs.
                         rsTrapsAllOn 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.6 trigger read-write
This switches all R&S-traps on - traps for all events (info, warning, fault) are sent out. In detail, this means in the R&S-MIBs under *Events - Events*Table in column event*Mask all OIDs are set to 1. Caution! Enabling all traps is not recommended! Caution! Setting this value influences remote controlling of devices! Too many alarms may flood your network. Use this only for testing - for operation, we suggest switch on only a few important traps. Caution! This enables absolutely all R&S alarms! Make sure you can handle it (network speed, routers, firewalls, NOC database performance etc.).
                         rsTrapsAllOff 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.7 trigger read-write
This switches all R&S-traps off - no traps are sent out. In detail, this means in the R&S-MIBs under *Events - Events*Table in column event*Mask all OIDs are set to 2. Note: This is typically set when using only IRT-MIBs and you don't need R&S-MIBs.
                         rsTrapsAllFaultsOn 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.8 trigger read-write
This switches all R&S-traps for faults on - traps for all 'faults' are sent out. In detail, this means in the R&S-MIBs under *Events - Events*Table in column event*Mask all 'fault'-OIDs are set to '1'. These traps include the value 'fault(1)' in binding 'eventAlarmClass'. Note: This is the recommended setting when using R&S-MIBs. It gives you an overview of the device state.
                         rsTrapsAllFaultsOff 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.9 trigger read-write
This switches all R&S-traps for faults off - no traps for 'faults' are sent out. In detail, this means in the R&S-MIBs under *Events - Events*Table in column event*Mask all 'fault'-OIDs are set to '2'. These traps include the value 'fault(1)' in binding 'eventAlarmClass'.
                         rsTrapsAllWarningsOn 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.10 trigger read-write
This switches all R&S-traps for warnings on - traps for all 'warnings' are sent out. In detail, this means in the R&S-MIBs under *Events - Events*Table in column event*Mask all 'warning'-OIDs are set to '1'. These traps include the value 'warning(2)' in binding 'eventAlarmClass'. Note: This is the recommended setting when using R&S-MIBs and you want much more informations from the device than only faults. Caution! This enables lots of alarms. Make sure you can handle it (network speed, NOC database performance etc.)...
                         rsTrapsAllWarningsOff 1.3.6.1.4.1.2566.127.1.2.167.1.1.2.11 trigger read-write
This switches all R&S-traps for warnings off - no traps for 'warnings' are sent out. In detail, this means in the R&S-MIBs under *Events - Events*Table in column event*Mask all 'warning'-OIDs are set to '2'. These traps include the value 'warning(2)' in binding 'eventAlarmClass'.
                     transmitterConfig 1.3.6.1.4.1.2566.127.1.2.167.1.1.3
                         dateTime 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.1 dateandtime read-write
The date and time for the transmitter. Notes: Deci-seconds different from 0 are ignored. The range of distance from UTC is -12h..+14h. Omitting the optional UTC fields in a set-request results in keeping the old UTC offset values.
                         ntp 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2
                             ntpMode 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.1 integer read-write
Configures the working mode of the NTP client. disabled: no ntp synchronisation will be done step: the time will synchronized every NTP sync-time unknown: NTP mode is currently not determinable. This value must not be written. Enumeration: 'disabled': 2, 'unknown': 1, 'stepAdjust': 4.
                             ntpSyncTimeInterval 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.2 integer32 read-write
Set the intervall, how often the NTP client will be synchronized to the NTP server. Note: this is useful in step mode only .
                             ntpServerAddrTable 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.3 no-access
Table with server adresses. Currently maximal one entry is allowed.
                                 ntpServerAddrEntry 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.3.1 no-access
An entry for a ntpServerAddrTable.
                                     ntpServerAddrIdx 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.3.1.1 integer32 no-access
index for table entry.
                                     ntpServerAddress 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.3.1.2 readablestring read-write
host name or IP address of server.
                             ntpState 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.4 integer read-only
Shows the actual state of the NTP synchronisation. Enumeration: 'syncFailed': 5, 'unknown': 1, 'enabled': 3, 'synchronizing': 6, 'disabled': 2, 'syncOk': 7, 'notRunning': 4.
                             ntpLastSync 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.5 dateandtime read-only
The date/time of the last successful synchronisation.
                         swMaintenance 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.5
                             restart 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.5.1 trigger read-write
Restart the software of transmitter's control unit.
                             swUpdate 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.5.5
                                 swUpdateStart 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.5.5.2 trigger read-write
Start software update tool at transmitter side in manual mode. The PC tool can only connect to transmitter's control unit if the software update tool on the transmitter is started.
                                 swUpdateMode 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.5.5.3 integer read-write
Run mode of the software update tool at the transmitter side. manual: Software update can be started with the Start button. It will stop automaticly after an idle period of 90 seconds. permanent: Software update is always running and will never stop. Enumeration: 'permanent': 2, 'manual': 1.
                                 swUpdateDeviceName 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.5.5.4 readablestring read-write
The Device Name is dedicated to this control unit. It will be shown in the software update tool on the PC to differ devices.
                                 swUpdateDeviceGroup 1.3.6.1.4.1.2566.127.1.2.167.1.1.3.5.5.5 readablestring read-write
The Device Group can be used to separate devices in large networks. It must match the Device Group in software update tool on the PC.
                 rsXx8000CommonEvents 1.3.6.1.4.1.2566.127.1.2.167.1.2
                     rsXx8000EventsV2 1.3.6.1.4.1.2566.127.1.2.167.1.2.0
                         testTrap 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.1
This trap is sent to check whether the trapsink is receiving any traps from this agent. To trigger this trap, set 'sendTestTrap' to '2'.
                         eventTx 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10
                               eventsTxV2 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.0
Compatibility to SMIv1.
                                   swUpdateStarted 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.0.1
Software update started. The PC tool can only connect to transmitter's control unit if the software update tool on the transmitter is started. It uses the network 17 (TCP and UDP).
                                   ntpSyncFailed 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.0.2
NTP synchronisation failed.
                               eventsTxTable 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.1 no-access
This table contains necessary information for handling alarms. For each alarm you have the following information: - name (get), - mask to enable/disable sending out (set/get), - priority (set/get) and - the current state (get only).
                                   eventsTxEntry 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.1.1 no-access
An event entry always consists of 3 values: - name: an enumerated list of all possible notifications - mask: the corresponding mask (enable/disable) - priority: the corresponding priority (value in range 0..255) - event: the event itself (active/inactive)
                                       eventTxNameIdx 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.1.1.1 eventmaxentrynumber no-access
The event number as integer. This is a helper column and therefore not-accessible.
                                       eventTxName 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.1.1.2 integer read-only
The event number as integer and the value as readable text. The enumeration correlates with the notifications under eventsTxV2. Enumeration: 'ntpSyncFailed': 2, 'swUpdateStarted': 1.
                                       eventTxMask 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.1.1.3 eventmask read-write
See TextualConvention for details.
                                       eventTxPriority 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.1.1.4 eventpriority read-write
See TextualConvention for details.
                                       eventTxEvent 1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.1.1.5 eventstate read-only
See TextualConvention for details.
                     eventHistory 1.3.6.1.4.1.2566.127.1.2.167.1.2.1
Information about sent out events.
                         counterEvents 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.1 counter32 read-only
The total number of traps sent out. This is an increasing value.
                         eventHistoryTable 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2 no-access
The table of the last 100 messages sent out.
                             eventHistoryEntry 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2.1 no-access
An event entry.
                                 eventHistoryNumber 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2.1.1 integer32 no-access
The trap number.
                                 eventHistoryModule 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2.1.2 integer read-only
This column indicates the physical module the corresponding message is for. Enumeration: 'dvbRecMon': 12, 'netcc': 2, 'pumpB': 9, 'pumpA': 8, 'exciterA': 3, 'exciterB': 4, 'dvbReceiver': 7, 'program': 14, 'switchoverUnit': 1, 'antenna': 10, 'outputstageA': 5, 'gpParIO': 13, 'outputstageB': 6, 'gps': 11.
                                 eventHistoryEvent 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2.1.3 integer32 read-only
This column indicates the event. In correlation with column eventHistoryModule, you can see the name of the event here. For this, you need to have a look at the event definitions of the corresponding MIB. Example: For a DVB transmitter an entry in eventHistoryModule is netccu(2) and the value in eventHistoryEvent is 1. A look at eventsTxV2 of RS-XX8000-DVB-TX-MIB shows, 1 is txSummaryFault.
                                 eventHistoryEventState 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2.1.4 eventstate read-only
See TextualConvention for details.
                                 eventHistoryEventDate 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2.1.5 dateandtime read-only
This column indicates the date and time of the event.
                                 eventHistoryTx 1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2.1.101 indextransmitter read-only
The transmitter index in case of NTx or Np1 systems. For variants with one transmitter only (SingleTx) this index is always transmitterB(1).
                     eventMapObjects 1.3.6.1.4.1.2566.127.1.2.167.1.2.3
                         eventAlarmPriority 1.3.6.1.4.1.2566.127.1.2.167.1.2.3.1 eventpriority no-access
This OID holds the value for the priority when sending out a notification.
                         eventAlarmClass 1.3.6.1.4.1.2566.127.1.2.167.1.2.3.2 eventclass no-access
See TextualConvention for details.
                         eventEvent 1.3.6.1.4.1.2566.127.1.2.167.1.2.3.3 eventstate no-access
This OID holds the value for the event itself when sending out a notification.
                         indexTransmitter 1.3.6.1.4.1.2566.127.1.2.167.1.2.3.4 indextransmitter no-access
This OID holds the value for the transmitter when sending out a notification.
                         indexAB 1.3.6.1.4.1.2566.127.1.2.167.1.2.3.5 indexab no-access
This OID holds the value for the module A (exciterA, outputstageA) or B (exciterB, outputstageB) when sending out a notification.
                         indexRack 1.3.6.1.4.1.2566.127.1.2.167.1.2.3.6 indexrack no-access
This OID holds the value for the rack when sending out a notification.
                         indexAmplifier 1.3.6.1.4.1.2566.127.1.2.167.1.2.3.7 indexamplifier no-access
This OID holds the value for the amplifier when sending out a notification.
                         indexProgram 1.3.6.1.4.1.2566.127.1.2.167.1.2.3.8 indexprogram no-access
This object holds the value for the program when sending out a notification.
                 rsXx8000CommonConf 1.3.6.1.4.1.2566.127.1.2.167.1.3
                     rsXx8000CommonGroups 1.3.6.1.4.1.2566.127.1.2.167.1.3.1
                         groupNotifyTest 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.1
test notifications.
                         groupNotify 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.2
notifications for all transmitters.
                         groupEventTest 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.6
The objects sent with testTrap.
                         groupEventHistory 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.8
Contains all objects from 'eventHistory'.
                         groupEventObjects 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.9
Contains all objects from 'eventMapObjects'.
                         groupProductInformation 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.11
Contains all objects from 'productInformation' (R&S typeplate).
                         groupSnmpConfig 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.12
Contains all objects from 'snmpConfig'.
                         groupTransmitterConfig 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.13
objects from 'transmitterConfig'.
                         groupNTP 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.14
objects from 'ntp'
                         groupSwMaintenance 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.15
objects from 'swMaintenance'
                         groupNotifyNTP 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.16
Notifications from the NTP client.
                         groupObsoletedObjects 1.3.6.1.4.1.2566.127.1.2.167.1.3.1.17
Description.
                     rsXx8000CommonCompls 1.3.6.1.4.1.2566.127.1.2.167.1.3.2
                         xx8000BasicCompliance 1.3.6.1.4.1.2566.127.1.2.167.1.3.2.1
The compliance statement for XX8000 entities which implement this MIB module.
 rsXx8000MibModule 1.3.6.1.4.1.2566.149.1.163
This MIB defines general objects of XX8000 transmitting systems from Rohde & Schwarz. Use this MIB for things all transmitters support via SNMP, e.g.: - product information - installation / configuration issues (trapsinks, managers aso.) The following MIBs are related to this: - RS-COMMON-MIB - mandatory for this MIB.