RS-XX8000-COMMON-MIB

All MIBs › RS-XX8000-COMMON-MIB

Organization: Rohde&Schwarz GmbH & Co. KG

Last Updated: 2011-05-11

Category: Broadcast and Media

Description: Manages common hardware and system parameters for Rohde and Schwarz SX8000 series equipment.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is RS-XX8000-COMMON-MIB?

RS-XX8000-COMMON-MIB is a vendor-specific MIB from Rohde & Schwarz that defines the common, product-line-wide objects shared across the XX8000 family of broadcast transmitting systems, layered on top of RS-COMMON-MIB. It exposes basic product-identity objects (serialNumber, identNumberSW/HW, versionNumberSW/HW), an SNMP-management configuration group with trapSinkTable (trap destination address, port, community, and inform-retry/timeout behavior) and NTP client objects (ntpMode, ntpServerAddrTable, ntpState, ntpLastSync), and an extensive logbook/event subsystem — eventsTxTable and eventHistoryTable — that records transmitter-module-scoped fault and warning events with severity, timestamp, and acknowledgement state. This makes it primarily a platform-identity, event-history, and management-plane MIB rather than a signal-quality MIB, useful for confirming a transmitter's firmware/hardware identity, verifying trap delivery is configured correctly, and reviewing the logbook of historical faults across transmitter racks. It depends on RS-COMMON-MIB for shared registration and product objects and is deployed across R&S XX8000-series TV/radio transmitters. Broadcast engineers consult the RS-XX8000-COMMON-MIB MIB to confirm trap-sink configuration and review transmitter event history.

IPNetwork Monitor allows you to monitor SNMP objects defined in RS-XX8000-COMMON-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Rohde & Schwarz XX8000 series broadcast transmitters

Monitoring Examples

An operator polls eventHistoryTable after a reported outage and filters by eventHistoryModule and eventHistoryEventState to find the fault entry, then checks trapSinkTable to confirm the NMS trap destination was correctly configured to have received the corresponding notification; a fault event present in eventHistoryTable with no matching trap delivery would point to a misconfigured or unreachable trapSinkAddress.

What Can Be Monitored

software/hardware identity and version objects
trap sink destination/community configuration
NTP synchronization state
transmitter event/logbook history
event severity and acknowledgement state

Imported Objects

From RS-COMMON-MIB

rsProdBroadcastTransmitter	OBJECT-IDENTITY
rsRegModules	OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DateAndTime
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
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
STR 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.
STR 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.
STR 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.
STR 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).
STR 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		not-accessible	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		not-accessible	An entry for a trapsink.
I32 trapSinkNumber	1.3.6.1.4.1.2566.127.1.2.167.1.1.2.2.1.1	Integer32	not-accessible	The arbitrary number in the list.
INT 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
IP 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.
I32 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.
STR 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
I32 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
I32 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
I32 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
T/F 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
TRI 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.
TRI 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.
TRI 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.
TRI 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 - EventsTable 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.).
TRI 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 - EventsTable 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.
TRI 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 - EventsTable 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.
TRI 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 - EventsTable in column event*Mask all 'fault'-OIDs are set to '2'. These traps include the value 'fault(1)' in binding 'eventAlarmClass'.
TRI 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 - EventsTable 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.)...
TRI 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 - EventsTable 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
DAT 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
INT 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.
I32 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		not-accessible	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		not-accessible	An entry for a ntpServerAddrTable.
I32 ntpServerAddrIdx	1.3.6.1.4.1.2566.127.1.2.167.1.1.3.2.3.1.1	Integer32	not-accessible	index for table entry.
STR 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.
INT 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.
DAT 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
TRI 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
TRI 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.
INT 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.
STR 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.
STR 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
NTF 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.
NTF 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).
NTF 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		not-accessible	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		not-accessible	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)
EVE eventTxNameIdx	1.3.6.1.4.1.2566.127.1.2.167.1.2.0.10.1.1.1	EventMaxEntryNumber	not-accessible	The event number as integer. This is a helper column and therefore not-accessible.
INT 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.
EVE 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.
EVE 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.
EVE 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.
C32 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		not-accessible	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		not-accessible	An event entry.
I32 eventHistoryNumber	1.3.6.1.4.1.2566.127.1.2.167.1.2.1.2.1.1	Integer32	not-accessible	The trap number.
INT 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.
I32 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.
EVE 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.
DAT 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.
IND 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
EVE eventAlarmPriority	1.3.6.1.4.1.2566.127.1.2.167.1.2.3.1	EventPriority	accessible-for-notify	This OID holds the value for the priority when sending out a notification.
EVE eventAlarmClass	1.3.6.1.4.1.2566.127.1.2.167.1.2.3.2	EventClass	accessible-for-notify	See TextualConvention for details.
EVE eventEvent	1.3.6.1.4.1.2566.127.1.2.167.1.2.3.3	EventState	accessible-for-notify	This OID holds the value for the event itself when sending out a notification.
IND indexTransmitter	1.3.6.1.4.1.2566.127.1.2.167.1.2.3.4	IndexTransmitter	accessible-for-notify	This OID holds the value for the transmitter when sending out a notification.
IND indexAB	1.3.6.1.4.1.2566.127.1.2.167.1.2.3.5	IndexAB	accessible-for-notify	This OID holds the value for the module A (exciterA, outputstageA) or B (exciterB, outputstageB) when sending out a notification.
IND indexRack	1.3.6.1.4.1.2566.127.1.2.167.1.2.3.6	IndexRack	accessible-for-notify	This OID holds the value for the rack when sending out a notification.
IND indexAmplifier	1.3.6.1.4.1.2566.127.1.2.167.1.2.3.7	IndexAmplifier	accessible-for-notify	This OID holds the value for the amplifier when sending out a notification.
IND indexProgram	1.3.6.1.4.1.2566.127.1.2.167.1.2.3.8	IndexProgram	accessible-for-notify	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.

RFC description

Manages Rohde & Schwarz broadcast transmitter system configuration, logbook events, and status.

Start monitoring Rohde & Schwarz XX8000 series broadcast transmitters (identity/trap-sink/event-log configuration) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download RS-XX8000-COMMON-MIB

What Is RS-XX8000-COMMON-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description