APEX-MIB: View SNMP OID List / Download MIB

The MIB module for the APEX.

This trap is issued if configuration of a single variable with integer type was changed (via ANY interface). TrapChangedValueInteger variable may contain current reading of that variable. trapPerceivedSeverity - 'indeterminate'

This trap is issued if configuration of a single variable with DisplayString type was changed (via ANY interface). TrapChangedValueDisplayString variable may contain current reading of that variable. trapPerceivedSeverity - 'indeterminate'

This trap is issued if configuration of a single variable with OID type was changed (via ANY interface). TrapChangedValueOID variable may contain current reading of that variable. trapPerceivedSeverity - 'indeterminate'

This trap is issued if configuration of a single variable with IpAddress type was changed (via ANY interface). TrapChangedValueIpAddress variable may contain current reading of that variable. trapPerceivedSeverity - 'indeterminate'

This trap is issued if a condition is being cleared and it is not in the condition list. trapAdditionalInfoInteger1 : Task and Function ID (task and function generates the error condition) trapAdditionalInfoInteger2 : Condition number trapAdditionalInfoInteger3 : Condition severity

This trap is issued if a condition is being set and it is already in the condition list. trapAdditionalInfoInteger1 : Task and Function ID (task and function generates the error condition) trapAdditionalInfoInteger2 : Condition number trapAdditionalInfoInteger3 : Condition severity

This trap is issued if a condition is being set and the condition list is full. trapAdditionalInfoInteger1 : Task and Function ID (task and function generates the error condition) trapAdditionalInfoInteger2 : Condition number trapAdditionalInfoInteger3 : Condition severity

This trap is issued when in a switch statement the default case is reached. The trapAdditionalInfoInteger1 will contain the task and Function ID. The trapAdditionalInfoInteger2 will contain value of the switch. The trapAdditionalInfoInteger3 is not used.

This trap is issued when a semaphore cannot be created. The trapAdditionalInfoInteger1 will contain the task and Function ID, the trapAdditionalInfoInteger2 and trapAdditionalInfoInteger3 will not be used.

This trap is issued when a socket cannot be opened. The trapAdditionalInfoInteger1 will contain the task and Function ID. The trapAdditionalInfoInteger2 will contain the errno returned by the call to socket(). The trapAdditionalInfoInteger3 is not used.

This trap is issued when an unknown message is received. The trapAdditionalInfoInteger1 will contain the task and Function ID. The trapAdditionalInfoInteger2 will contain the message ID and the trapAdditionalInfoInteger3 is not used.

This trap is issued when an invalid message is received. The trapAdditionalInfoInteger1 will contain the task and Function ID. The trapAdditionalInfoInteger2 will contain the message ID and the trapAdditionalInfoInteger3 is not used.

See corresponding alarm apexAlarmHardwareFault. Additional Info 1 carries HW Error Code (refer to HW Event Log for details). Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmInvalidInitData. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmTemperatureFault. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmFanFault. This trap is sent on summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmPowerFault. Additional Info 1 carries the apexPsStatusTable index (1 to 2). Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGbeLossOfPhysicalInput. Additional Info 1 carries the Gigabit Ethernet Interface Number (1 to 4). Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGbeBufferFullness. Additional Info 1 carries the Gigabit Ethernet Processor Number (1 to 2). Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGbeInputStreamLowBitRate. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGbeInputStreamHighBitRate. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGbeMptsRedundPrimaryThreshold. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGbeMptsRedundFailOver. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmServiceInError. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGbeLossOfInputStream. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGigeToHostCommFault. This trap is sent on a summary basis. Additional Info 1 is not used. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmGbeInterfaceRedundFailOver. This trap is sent on a GbE Redundant Pair basis. Additional Info 1 contains the GbE interface number that lost link. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmOutputUtilizationFault. This trap is sent on an Output Transport Stream basis. Additional Info 1 carries the Output Transport Stream number (1 to 48). Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmOutputOverflow. This trap is sent on an Output Transport Stream basis. Additional Info 1 carries the Output Transport Stream number (1 to 48). Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmQamModuleFault. This trap is sent on a QAM Module basis. Additional Info 1 carries the QAM Module number (1 to 3). Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmQamRfPortFault. This trap is sent on a QAM RF Port basis. Additional Info 1 carries the QAM RF Port number: RF Port 1 = QAM Module 1, RF 1 RF Port 2 = QAM Module 1, RF 2 RF Port 3 = QAM Module 2, RF 1 RF Port 4 = QAM Module 2, RF 2 RF Port 5 = QAM Module 3, RF 1 RF Port 6 = QAM Module 3, RF 2 Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmQamChannelFault. This trap is sent on a QAM Channel basis. Additional Info 1 carries the QAM Channel number. 1 to 8 = QAM Module 1, RF 1, QAM Channel A to H 9 to 16 = QAM Module 1, RF 2, QAM Channel A to H 17 to 24 = QAM Module 2, RF 1, QAM Channel A to H 25 to 32 = QAM Module 2, RF 2, QAM Channel A to H 33 to 40 = QAM Module 3, RF 1, QAM Channel A to H 41 to 48 = QAM Module 3, RF 2, QAM Channel A to H Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmQamRfRedundFailOver. This trap is sent on a Primary QAM RF Port basis. Additional Info 1 carries the Primary QAM RF Port number. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmQamRfRedundMismatch. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmRtspControllerCommFault. This trap is sent on a controller basis. Additional Info 1 carries the controller number. Additional Info 2 is not used. Additional Info 3 is not used.

See corresponding alarm apexAlarmRdsCommFault. Additional Info is not used.

See corresponding alarm apexAlarmRemCommFault. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmRemFault. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmDepiControlConnectionFault. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmDepiSessionSetupFault. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmDtiSyncLossFault. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmChassisRedundancyPrimaryFailover. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmChassisRedundancySecondaryFailover. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmChassisRedundancyAvailabilityFault. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmChassisRedundancyLinkFault. This trap is sent on a summary basis. Additional Info is not used.

See corresponding alarm apexAlarmChassisRedundancyConfigurationFault. This trap is sent on a summary basis. Additional Info is not used.

See corresponding event apexEventEmUserLoginFailed. Additional Info is not used.

See corresponding event apexEventQamModuleUpgraded. Additional Info is not used.

See corresponding event apexEventChassisRedunPrimaryForceFailover. Additional Info is not used.

See corresponding event apexEventChassisRedunSecondaryForceFailover. Additional Info is not used.

See corresponding event apexEventChassisRedunFirmwareVersionMismatch. Additional Info is not used.

See corresponding event apexEventChassisRedunQAMVersionMismatch. Additional Info is not used.

Writing this object will commit the current configuration to Flash. While a read returns the value savingConfigToFlash, the flash is being saved; the save may not have been initiated by an SNMP set. Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no) Enumeration: 'saveNotInProgress': 1, 'savingConfigToFlash': 3, 'startSaveToFlash': 2.

This is the Product Name of the APEX loaded at initialization from the config.ini file. Specific configurations of the APEX have specific purposes and are identified by their product name. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2, default=yes) @File(config.ini, type='ini')

This parameter is used to set the boot method for the APEX. Selection of noDhcpOrBootp means the APEX will not use DHCP or BOOTP - this will result in about a 10 second savings in boot time. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') Enumeration: 'noDhcpOrBootp': 1, 'bootpOnly': 3.

Setting to 'enabled' allows the APEX to automatically reboot when specific APEX hardware errors occur. Setting this to Enabled will cause the APEX to automatically reboot upon specific HW faults, such as a GigE processor crash, or upon a Host processor watchdog event. When disabled, HW faults and watchdog events will not cause an automatic reboot. This is useful when it is necessary to debug the event (to allow time to gather status prior to manually rebooting). Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Specify the mode in which MediaCipher EMMs are inserted, out of band or full in band. Once written, the change to this parameter will only take immediate effect after apexMcEmmInsertionApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexMcEmmInsertionApplyChange , value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') Enumeration: 'outOfBand': 1, 'fullInBand': 2.

Enable/disable first EMM PID to include in the CAT for MediaCipher Full In Band mode. Default value is enabled. Once written, the change to this parameter will only take immediate effect after apexMcEmmInsertionApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexMcEmmInsertionApplyChange , value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

First EMM PID to include in the CAT for MediaCipher Full In Band mode. Allowed values: from 0x1C00 to 0x1FFE. Default value is 0x1C02. Once written, the change to this parameter will only take immediate effect after apexMcEmmInsertionApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexMcEmmInsertionApplyChange , value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Enable/disable first EMM PID to include in the CAT for MediaCipher Full In Band mode. Default value is disabled. Once written, the change to this parameter will only take immediate effect after apexMcEmmInsertionApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexMcEmmInsertionApplyChange , value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Second EMM PID to include in the CAT for MediaCipher Full In Band mode. Allowed values: from 0x1C00 to 0x1FFE. Default value is 0x1C03. Once written, the change to this parameter will only take immediate effect after apexMcEmmInsertionApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexMcEmmInsertionApplyChange , value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

The Apply for the MediaCipher EMM Insertion group. This parameter MUST be set to 'apply' in order for any of the data in the MC EMM Insertion group to take effect in the device. This parameter MUST be set LAST after all other data in the MC Emm Insertion group has been configured. @Config(config=no, reboot=no)

Indicates reason for APEX boot: 'powerCycle' - Power-up or power cycled. 'operatorReboot' - Operator commanded reboot (refer to manual). 'hwFault' - Automatic reboot occurred as per apexAutoRebootEnable. 'wdFault' - Automatic Watchdog reboot as per apexAutoRebootEnable. Enumeration: 'wdFault': 3, 'hwFault': 2, 'powerCycle': 0, 'operatorReboot': 1.

Maximum number of service mappings supported by the APEX.

APEX Host Processor Boot Code Version.

APEX MUX FPGA Version.

APEX MUX FPGA Encryption type currently loaded. Enumeration: 'noEncryption': 0, 'des': 1, 'csa': 2, 'aes': 3.

APEX Main Board Version. This is the revision of the apexMainBoardType.

APEX Host Processor Application Creation Date.

APEX Product Type. The corresponding product name text setting can be found in identUnitModel. Enumeration: 'invalid': 0, 'apex1000': 1.

APEX Main Board Type. The revision is found in apexMainBoardVersion.

APEX Glue FPGA Version.

APEX Glue CPLD Version.

APEX DTI FPGA Version.

APEX MPC2 FPGA Version.

APEX DPM Version.

The source for system time. The time source can be configured to come from an SNTP time source, or be generated internally. When configured as internal: - The APEX will internally keep time starting at GPS time 0. A user can set the time to a valid GPS time in this mode. - The system time and UTC offset in internal mode are not updated and therefore are not valid. When configured to receive time via SNTP the SntpServerSpecified object and SntpServiceIP objects can be used to optionally define the SNTP server. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') Enumeration: 'internal': 2, 'sntp': 1.

The value of this object is the Universal Time Coordinated (UTC) offset from GPS time. Subtract this from GPS time to convert from GPS to UTC. Units are seconds. When time source is SNTP, this object can be set to specify the UTC offset that the APEX will use in calculating GPS time. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

When the TimeSource is SNTP, this object specifies whether the APEX will only accept time for a single SNTP server or from any server that broadcasts time. When notSpecified, the APEX will accept time from any SNTP server. When specified, the APEX will poll for time from the address of the SNTP server specified by the SntpServerIP address object. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') Enumeration: 'notSpecified': 1, 'specified': 2.

This contains the IP address of the specified SNTP server. If apexTimeSource is SNTP and apexSntpServerSpecified is set to specified, then the apex will poll for time from this IP address. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

The value of this object is the GPS Time the APEX is given via user entry. The time is reported in GPS seconds. This time is ONLY used when the APEX is set to Internal time mode. Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no)

The value of this object is the current System Time of the APEX. The system time is reported in GPS seconds. To determine the APEXs system time in UTC the apexSntpUtcOffset object must also be read and used in the calculation.

The Operational Time is the time in seconds since the APEX completed the boot sequence. It is the time that the APEX has been operational.

Ambient temperature at the intake vent at the front of the unit. Measured in whole number degrees Celsius.

Ambient temperature at the MUX FPGAs. Measured in whole number degrees Celsius.

Ambient temperature at the ACP Module location. This reading is valid for all models whether an ACP Module is standard on the model. Measured in whole number degrees Celsius.

Ambient temperature at the Host Processor. Measured in whole number degrees Celsius.

Fault status of ambient temperature at the intake vent at the front of the unit. Enumeration: 'overTemp': 2, 'notApplicable': 0, 'ok': 1.

Fault status of ambient temperature at the MUX FPGAs. Enumeration: 'overTemp': 2, 'notApplicable': 0, 'ok': 1.

Fault status of ambient temperature at the ACP Module location. Enumeration: 'overTemp': 2, 'notApplicable': 0, 'ok': 1.

Fault status of ambient temperature at the Host Processor. Enumeration: 'overTemp': 2, 'notApplicable': 0, 'ok': 1.

This is a table of status parameters for the two Power Supplies.

Power Supply Status Table Entry.

PS Number.

This parameter indicates installed status of the PS. Enumeration: 'fanModuleInstalled': 4, 'installedAcInput': 2, 'notInstalled': 1, 'unsupported': 5, 'notApplicable': 0, 'installedDcInput': 3.

PS measured output voltage in milli-Volts.

PS measured output current in milli-Amps.

The fan speed in RPM an installed Power Supply or Fan Module. Zero if not installed.

PS Fan Status. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

Indicates whether the power supply is in protection mode due to an over temperature condition. The PS is shut down while in 'overTemp' and will recover when the temperature returns to normal operating range. A power cycle is not required for recovery. Note that Output Power Status will be 'error' when Temperature status is 'overTemp'. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

Indicates whether AC Input is within specification. Note that Output Power Status will be 'error' when Input Power status is 'error' Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

Indicates whether the +12V and +3.3V output power are within specification. If the output power error occurs with an Input Power error, apply input power to recover. If the output power error occurs with an Over Temperature error, a power cycle is not required for recovery. Otherwise, a power cycle is required for recovery. If the problem persists after the power cycle, the PS must be replaced for recovery. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

Summary of errors reported on a power supply basis. The reported error will be the most severe. Enumeration: 'psUnsupported': 3, 'ok': 1, 'inputPower': 4, 'outputPower': 7, 'overTemp': 6, 'psNotInstalled': 2, 'commLost': 8, 'fanFault': 5.

Current fault condition of the power supply errors. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

Diagnostic data word 1 (HP) - Contents for Motorola diagnostic purposes.

Diagnostic data word 2 (PS) - Contents for Motorola diagnostic purposes.

Communication with the Power Supply has failed and status cannot be determined. Only applies when valid PS installed. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

This is a table of version status parameters for the two Power Supplies.

Power Supply Version Status Table Entry.

PS Number.

PS Model.

PS serial number.

The number of the output transport stream to route to the ASI Monitor Port. Zero indicates that no stream is to be routed to the ASI Monitor port. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Selects pre or post encryption for the ASI monitor port. This parameter is only applicable to APEXs with encryption capability. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') Enumeration: 'postEncryption': 2, 'preEncryption': 1.

This is the IP address of the default gateway for the Fast Ethernet interfaces. This should be zero or a valid Class A, B, or C IP address. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This is a table of configuration parameters for Output Transport Rate of Fast Ethernet MPEG data Insertion.

Output Transport Rate of Fast Ethernet MPEG Insertion Configuration Table Entry.

Output Transport Stream Number.

Insertion Rate for the transport stream for Fast Ethernet MPEG data. Maximum MPEG data rate to insert data received via Fast Ethernet interfaces. Range is 0 Kbps to 2500 Kbps for each transport stream. Total for all transport streams must not exceed 10000 Kbps. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Range(min=0, max=2500) @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

The Apply for the Fast Ethernet Static Routing Table. This parameter MUST be set to 'apply' in order for any of the data in the apexFastEnetRoutingTable to take effect. This parameter MUST be set LAST after all other data in the apexFastEnetRoutingTable has been configured. Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no)

This table is the configuration Static Routing table for the Fast Ethernet Interface. @Commit(param=apexFastEnetRoutingApplyChange, value=2) @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Fast Ethernet Interface Configuration Static Routing Table Entry.

The index of the Routing table entry. Currently limited to 16.

The Fast Ethernet Routing Destination IP address. Once written, the change to this parameter will only take immediate effect after apexFastEnetRoutingApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter.

The Fast Ethernet Routing Gateway IP address. Once written, the change to this parameter will only take immediate effect after apexFastEnetRoutingApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter.

The Fast Ethernet Routing Subnet Mask. Once written, the change to this parameter will only take immediate effect after apexFastEnetRoutingApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter.

Maximum number of Fast Ethernet input UDP ports that can be opened on this APEX.

Table of Fast Ethernet Insert Packet Statistics for each Fast Ethernet interface. Indexed by FE interface port number.

A row in the FE Insert Packets table.

Fast Ethernet interface port Number.

Number of MPEG packets inserted during the last monitoring period (currently 5 seconds) on this FE interface port.

Total number of MPEG packets inserted on this FE interface port.

Number of MPEG packets discarded during the last monitoring period (currently 5 seconds) on this FE interface port. This may be due to a buffer overflow or incorrect configuration of the FE output stream insertion rate.

Total number of FE MPEG packets discarded on this Output Transport Stream. Discarded packets on an FE interface port are those packets discarded due to an overflow condition.

Table of Output Transport Stream FE Insert Packet Statistics. Indexed by Output Transport Stream number.

A row in the Output Transport Stream FE Insert Packets table.

Output Transport Stream Number.

Number of MPEG packets inserted during the last monitoring period (currently 5 seconds) on this Output Transport Stream.

Total number of MPEG packets inserted on this Output Transport Stream.

Number of MPEG packets discarded during the last monitoring period (currently 5 seconds) on this Output Transport Stream. This may be due to a buffer overflow or incorrect configuration of the FE output stream insertion rate.

Total number of FE MPEG packets discarded on this Output Transport Stream. Discarded packets on an output stream are those packets discarded due to an overflow condition.

This is the IP address of the OAMP IP (Enet1) interface of the APEX. This IP address is set via a BootP when connected to a Bootp server. When not connected to a BootP server, the IP address may directly be changed by setting this parameter. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This is subnet mask of the OAMP IP (Enet1) interface of the APEX. The subnet mask is normally via a BootP when connected to a BootP server. When not connected to a Bootp Server, the Subnet Mask may directly be changed by setting this parameter. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

OAMP IP (Enet1) Ethernet Auto-Negotiation setting. 'disabled' is not supported. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This is the MAC address of the APEX OAMP IP (Enet1) Interface. It is set at the factory and cannot be changed. The string length is 17 characters in the format 'hh:hh:hh:hh:hh:hh' where 'hh' is a hexadecimal number.

OAMP IP (Enet1) Ethernet speed (10Mbps or 100Mbps). This is determined by the results of the auto-negotiation process. If auto-negotiation fails, the default speed is 100Mbps. Enumeration: 'notApplicable': 0, 'interfaceSpeed10Mbps': 1, 'interfaceSpeed100Mbps': 2.

OAMP IP (Enet1) Ethernet Duplex Mode (full or half) This is determined by the results of the auto-negotiation process. If auto-negotiation fails, the default mode is Full. Enumeration: 'notApplicable': 0, 'fullDuplex': 2, 'halfDuplex': 1.

Number of input transport streams assigned to the OAMP IP interface (Enet1).

This indicates if the OAMP (ENET1) link is active.

This is the IP address of the Data IP (Enet2) interface of this APEX. The data IP address may directly be changed by setting this parameter. The Data IP address must be configured such that the Data IP interface and the OAMP interface are on different networks. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This is subnet mask of the Data IP (Enet2) interface of this APEX. The data IP Subnet Mask may directly be changed by setting this parameter. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Data IP (Enet2) Ethernet Auto-Negotiation setting. 'disabled' is not supported. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This is the MAC address of the APEX Data IP (Enet2) Interface. It is set at the factory and cannot be changed. The string length is 17 characters in the format 'hh:hh:hh:hh:hh:hh' where 'hh' is a hexadecimal number.

Data IP (Enet2) Ethernet speed (10Mbps or 100Mbps). This is determined by the results of the auto-negotiation process. If auto-negotiation fails, the default speed is 100Mbps. This status item is only valid when the Data IP port is enabled and properly configured. Enumeration: 'notApplicable': 0, 'interfaceSpeed10Mbps': 1, 'interfaceSpeed100Mbps': 2.

Data IP (Enet2) Ethernet Duplex Mode (full or half) This is determined by the results of the auto-negotiation process. If auto-negotiation fails, the default mode is Full. This status item is only valid when the Data IP port is enabled and properly configured. Enumeration: 'notApplicable': 0, 'fullDuplex': 2, 'halfDuplex': 1.

Number of input transport streams assigned to the Data IP interface.

Indicates the IP Address currently being used by the Data IP port (Enet2). This parameter will be either apexDataIpAddr or an APEX selected IP address. Refer to apexDataIpInUseReason for more information.

Indicates the Subnet Mask currently being used by the Data IP port (Enet2). This parameter will be either apexDataIpSubnetMask or an APEX selected mask. Refer to apexDataIpInUseReason for more information.

Reason for apexDataIpAddrInUse and apexDataIpSubnetMaskInUse Data IP (Enet2) parameters. 'notApplicable' - Enet2 not configured by user or for REM connection. 'userConfig' - APEX is not overriding user configured parameters. 'directRemConnection' - The DATA IP port (Enet2) is in use for QAM RF Redundancy so the APEX has overridden the user configured parameters. Enumeration: 'notApplicable': 0, 'directRemConnection': 2, 'userConfig': 1.

This indicates if the DataIP (ENET2) link is active.

This is the IP address of the default gateway for Gigabit Ethernet interfaces 1 and 2. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This is the IP address of the default gateway for Gigabit Ethernet interfaces 3 and 4. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This object is obsolete. Jitter Absorption setting in range of 0 to 200 milliseconds in increments of 5 ms. A change to this parameter will cause the Gigabit Ethernet processor to reset all of its internal Ethernet frame buffers. This will result in a momentary loss of data causing a minor glitch on all output streams. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Range(step=5) @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Gratuitous ARP period in range of 20 to 300 seconds. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

The Apply for the Gigabit Ethernet Configuration Table. This parameter MUST be set to 'apply' in order for any of the data in the apexGbeConfigTable to take effect. This parameter MUST be set LAST after all other data in the apexGbeConfigTable has been configured. @Config(config=no, reboot=no)

Gigabit Ethernet Nominal Buffer Level. Range of 50 to 475 milliseconds in increments of 5 ms. A change to this parameter will cause the Gigabit Ethernet processor to reset all of its internal Ethernet frame buffers. This will result in a momentary loss of data causing a minor glitch on all output streams. The buffer level is the normal standard starting level for an input stream buffer. It is highly recommended that this level not be changed from its default setting. The buffer level needs to be set at an appropriate amount to allow for network jitter, clock skew between the APEX and input source, and for maximum time between PCRs (100ms). In addition, the level must not be set too high as the buffer needs to be able to grow as packets are received and PCR processing is applied. This buffer level is the initial level the APEX will attempt to maintain at all times. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Input Data stream smoothing period. Amount of time in milliseconds over which the GigE will smooth out input streams that do not contain PCRs. This allows the GigE to play out the input streams with the packets equally spaced out over this period. This helps to reduce network jitter and bursts of data to the output. The smoothing period is used in conjunction with the data stream buffer depth to perform this smoothing algorithm. The smoothing period must be equal to or less than the data stream buffer depth. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(bcmr.ini, type='ini')

GBE Input Data stream buffer depth. Amount of time in milliseconds that the GigE will buffer input streams that do not contain PCRs. This allows the GigE to buffer these streams to remove network jitter and then play them out with the packets equally spaced out. The buffer depth must be equal to or greater than the data stream smoothing period. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(bcmr.ini, type='ini')

When apexGbeConfigInputDataTsApplyChange is set to 'applyNotInProgressInvalidData' this entry may contain a text description of what was wrong with the data. This entry contains the description for the most recent apply of a related entry that was invalid.

Loss of input stream timeout value (in milliseconds) for unicast inputs. This determines the amount of time a unicast input stream is missing before the APEX will declare the input stream lost. Loss of input is used for determining all SDV failover conditions. It is also used for Manual Routing failover conditions when using hot/warm transport stream redundancy. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Range(step=200) @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Loss of input stream timeout value (in milliseconds) for multicast inputs. This determines the amount of time a unicast input stream is missing before the APEX will declare the input stream lost. Loss of input is used for determining all SDV failover conditions. It is also used for Manual Routing failover conditions when using hot/warm transport stream redundancy. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Range(step=200) @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Loss of input stream type. Determines if detection of loss of an input stream is based on data rate or stream rate. Data rate includes only non-null MPEG packets (such as video and audio packets). Stream rate includes all packets, including null packets. The loss of an input stream uses the timeout value for the specific input (unicast or multicast) and the input type. If no packets are received within the specified timeout value, taking into account the loss of input type checking, then the input stream is determined to be missing. Data rate should be used for detecting loss of input when the input stream is normally null filled. When a user requires notification of a loss of input stream when there is no content streamed, data rate should be selected. Stream rate should be used for detecting loss of input stream when the user requires to be notified when there is no input stream at all being received. Loss of input is used for determining all SDV failover conditions. It is also used for Manual Routing failover conditions when using hot/warm transport stream redundancy. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This is a table of configuration parameters for the Gigabit Ethernet Interfaces. Once written, the change to this table will only take immediate effect after apexGbeConfigTableApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexGbeConfigTableApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Gigabit Ethernet Interface Configuration Table Entry.

Gigabit Ethernet Interface Number.

This parameter enables the Gigabit Ethernet Interface.

This is the IP address of this Gigabit Ethernet interface. It is recommended that each Gigabit Ethernet interface be on a different subnet. Each must be given a unique IP address. 0.0.0.0 indicates the interface is not in use.

This is subnet mask of this Gigabit Ethernet interface.

Auto negotiation enabled or disabled.

This is a table of configuration parameters related to Gigabit Ethernet Frame Buffer statistics gathering. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Gigabit Ethernet Frame Buffer Configuration Table Entry.

Gigabit Ethernet Processor Number. Proc 1 = GBE Interfaces 1 and 2 Proc 2 = GBE Interfaces 3 and 4

Maximum Gigabit Ethernet MPEG input data rate in bps. This is the total amount of MPEG data expected to be received by Gigabit Ethernet frame interfaces on the processor. This data rate is used to determine the frame buffer reset limit. The expected data rate should always be set equal to or greater than the actual input data rate. The value of apexGbeJitterAbsorption can limit the valid range of this data rate. It is highly recommended that the user consult with Motorola prior to changing the expected data rate.

User defined threshold representing a percentage of frame buffer depth. The frame buffer level is monitored by the APEX and the maximum level is based on the actual input data rate. The threshold percentage is used to determine when to issue a Gigabit Ethernet Frame Buffer Fullness alarm (apexAlarmGbeBufferFullness).

This is the time in seconds over which Redundant Gigabit Ethernet Input Transport Stream Pairs will be monitored. Range is 1 to 30 seconds. Primary to Secondary Fail Over - The monitored data rate of the Primary must be below the Secondary by apexManRteGbeInRedThreshold (for Manual Routing) percent for apexGbeConfInRedundMonitorPeriod before fail over to Secondary will occur. Fail over to Secondary will not occur if fail over is suspended for the Primary. Secondary to Primary Switch Back - The monitored data rate of the Primary must have returned above apexManRteGbeInRedThreshold (for Manual Routing) percent below the Secondary for apexGbeConfInRedundMonitorPeriod before switch back to Primary will occur. Switch back to Primary will not occur if fail over is suspended for the Secondary. Once the Primary is restored, switch back to Primary will be delayed by apexGbeConfInRedundSwitchTime when apexGbeConfInRedundAutoSwitchBack is 'enabled'. Note that if apexGbeConfInRedundAutoSwitchBack is 'disabled' switch back will not occur. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini')

This is the time in seconds to wait before switching back to the Primary of a Redundant Gigabit Ethernet Input TS pair after the Primary is healthy. Range is 0 to 3600. This time is in addition to apexGbeConfInRedundMonitorPeriod. Switch back to Primary will not occur if fail over is suspended for the Secondary. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini')

This is the enable/disable of automatic switch back from Secondary to Primary for Gigabit Ethernet redundancy. When 'enabled', switch back to the Primary will automatically occur when the Primary is restored. When 'disabled', the user must force back to the Primary using apexGbeConfInRedundForceToPrimary or apexManRteGbeInRedForceSwitch. This parameter applies to all configured redundant pairs. Auto switch back to the primary will not occur if the user forced a failover to the secondary. Auto switch back only occurs after a non-forced failover event. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini')

The Gigabit Ethernet Redundant Pair force switch any pair that is currently on the Primary to the Secondary. This will have no effect if the corresponding row setting of apexManRteGbeInRedEnable is 'disabled'. This will only have an effect when the Primary is the In-Use Input TS of a Redundant Pair (apexInputTsStatPriState or apexInputTsStatSecState is 'openedInUse'). Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no) Enumeration: 'switchNotInProgress': 1, 'forceSwitch': 2.

The Gigabit Ethernet Redundant Pair force switch any pair that is currently on the Secondary to the Primary. This will have no effect if the corresponding row setting of apexManRteGbeInRedEnable is 'disabled'. This will only have an effect when the Secondary is the In-Use Input TS of a Redundant Pair (apexInputTsStatPriState or apexInputTsStatSecState is 'openedInUse'). Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no) Enumeration: 'switchNotInProgress': 1, 'forceSwitch': 2.

The redundancy type for output streams in Manual Routing operating mode. - hotWarm indicates only 1 input stream, primary or secondary, is open at any one time. For multicast streams, primary will be joined initially. The secondary is joined after a failover (the primary will be dropped prior to joining the secondary). When falling back to the primary, the secondary is dropped (closed), then the primary is joined (opened). - hotHot indicates both the primary and secondary streams are opened at the same time. For multicast streams, both streams are joined immediately. Changes to the redundancy type cannot be made while there are active routes. All routes must be deleted prior to changing the redundancy type. Once written, a save must be performed via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini') Enumeration: 'hotHot': 2, 'hotWarm': 1.

Table of data for GBE input data stream identification. Each entry in this table identifies a Gigabit Ethernet input stream that is a data stream only. Data streams are streams without PCR. These streams require special processing to avoid overflowing the output. There are 128 rows in this table. Once written, the change to this table will only take immediate effect after apexGbeConfigInputDataTsApplyChange is set to 'apply'. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Commit(param=apexGbeConfigInputDataTsApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(bcmr.ini, type='ini')

GBE Input Data Stream Table Entry.

Index of GBE Input Data Stream Table.

Indicates whether this GBE Input Data Stream entry is enabled or disabled.

Number of the input interface (Port number). Range: '0' = Not Applicable GBE = 1-4

GBE Input UDP Port. Range: 0-65535

The Multicast receive IP address. An IP address of 0.0.0.0 indicates singlecast only. Multicast IP addresses 224.0.0.0 to 224.0.0.255 are reserved.

This is the IP address of the source device. This field is only used when a multicast IP address is also specified.

Table of Apply Change for the GBE Input Data Stream Table. A row in this table corresponds to the same row index in the GBE Input Data Stream table (apexGbeConfigInputDataTsTable).

GBE Input Data Stream Apply Table Entry.

The index of the GBE Input Data Stream Apply Table.

The Apply for the row of data in the GBE Input Data Stream Table. A row in this table corresponds to the same row index in the GBE Input Data Stream table. This parameter MUST be set to 'apply' in order for any of the data in the GBE Input Data Stream Table row to take effect in the APEX. This parameter MUST be set LAST after all other data in the GBE Input Data Stream Table row has been configured. @Config(config=no, reboot=no)

Enables the ability for the secondary interface to switch back when link is re-detected on the primary interface. Auto switch back to the primary interface will not occur if the user forced a failover to the secondary. Auto switch back only occurs after a non-forced failover. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini')

Timer for determining that the primary interface is OK for auto- switchback. The primary interface must have link for the configured amount of time. Valid time is 1-30 seconds. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini')

This is a table of configuration parameters for GbE Interface Redundancy.

GbE Interface Redundancy Configuration Table Entry.

GbE Interface Pair number. Value of 1 is GbE1 and GbE2 pair. Value of 2 is GbE3 and GbE4 pair.

Enables GbE Interface Redundancy for ports pair. Failover is based on link status. If the primary GbE fails, the secondary GbE will become active and will start receiving content. There is no data rate comparison, as only one interface in the redundancy pair is active. The secondary GbE cannot be in use prior to enabling redundancy. TS redundancy may not be used at the same time as interface redundancy. Interface redundancy is not applicable when chassis redundancy is enabled. Once written, the change to this table will only take immediate effect after apexGbeConfIfRedundApplyChange is set to 'apply'. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Commit(param=apexGbeConfIfRedundApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini')

When set to failover(2), this results in the APEX switching to the interface that is currently not in use. If the primary GbE is in use and this is set to failover(2) mappings will be then routed to the secondary GbE. If the secondary GbE is in use and this is set to failover(2) mappings will then be routed back to the primary GbE. Once written, the change to this table will take immediate @Config(config=no, reboot=no) Enumeration: 'failover': 2, 'failoverNotInProgress': 1.

Enables and disables suspending of Interface failover. Prevents failovers to or from backup. Force failover (apexGbeConfIfRedundForceFailover) overrides this setting. Once written, the change to this table will only take immediate effect after apexGbeConfIfRedundApplyChange is set to 'apply'. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Commit(param=apexGbeConfIfRedundApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini')

Table of Apply Change for the GBE Interface Redundancy Configuration Table. A row in this table corresponds to the same row index in the GBE Config Interface Redundancy table (apexGbeConfigInterfaceRedundancyTable).

GBE Config Interface Redundancy Table Entry.

The index of the GBE Config Interface Redundancy Table.

The Apply for the row of data in the GBE Config Interface Redundancy Table. A row in this table corresponds to the same row index in the GBE Config Interface Redundancy table. This parameter MUST be set to 'apply' in order for any of the data in the GBE Input Data Stream Table row to take effect in the APEX. This parameter MUST be set LAST after all other data in the GBE Input Data Stream Table row has been configured. @Config(config=no, reboot=no)

APEX Gigabit Ethernet Processor Boot Code Version.

APEX Gigabit Ethernet Processor Application Code Version.

Maximum number of Gigabit Ethernet input transport streams that can be opened on this APEX. This is the maximum across all installed GigE interfaces. One GigE interface can use all Input TS.

Time in seconds between Gigabit Ethernet Routed Packet Count updates. The count during this time is defined as one sample. This time applies to packet counts contained in apexGbeStatusRoutedPacketTable. To compute rate from packet count for the last update interval: Rate(bps) = (Packet_Count * 188 bytes/packet * 8 bits/byte) / Update_Interval This value is set by the APEX at startup and is constant.

This is a table of status parameters for the Gigabit Ethernet Interface.

Gigabit Ethernet Interface Status Table Entry.

Gigabit Ethernet Interface Number.

This is the MAC address of the Gigabit Ethernet Interface. It is set at the factory and cannot be changed. The string length is 17 characters in the format 'hh:hh:hh:hh:hh:hh' where 'hh' is a hexadecimal number.

This indicates if the Gigabit Ethernet optical link is active.

This indicates the IGMP Version being used on this interface. Enumeration: 'igmpV3': 3, 'notApplicable': 0, 'igmpV1': 1, 'igmpV2': 2.

The current severity of apexAlarmGbeLossOfPhysicalInput for this interface. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

Table of Gigabit Ethernet Input TS Assigned data.

Gigabit Ethernet Interface Input TS Assigned Table Entry.

The index of the Gigabit Ethernet Input TS Assigned Table. Represents the Gigabit Ethernet interface number.

Number of input transport streams assigned to the GigE interface.

Table of Gigabit Ethernet Input Open UDP Port data.

Gigabit Ethernet Interface Input Open UDP Port Table Entry.

The index of the Gigabit Ethernet Input Open UDP Port Table. Represents the Gigabit Ethernet interface number.

Number of open Input UDP Ports on the GigE interface.

This table contains Gigabit Ethernet MPEG packet counts for each Output Transport Stream of this APEX. Update interval is apexGbeRoutedPacketUpdateInterval.

Gigabit Ethernet Interface Status Routed Packet Table Entry.

The index of the Gigabit Ethernet Routed Packet Status Table. Represents Output Transport Stream number.

Total number of Gigabit Ethernet MPEG packets routed to this Output Transport Stream.

Number of Gigabit Ethernet MPEG packets routed to this Output Transport Stream during the last monitoring period (apexGbeRoutedPacketUpdateInterval).

Reset Ethernet Frame Counter Totals for all GigE interfaces: - apexGbeTotalRxSinglecastFrames - apexGbeTotalRxMulticastFrames - apexGbeTotalRxBroadcastFrames - apexGbeTotalRxErrorFrames - apexGbeTotalRxFrames - apexGbeTotalTxGoodFrames - apexGbeTotalTxErrorFrames Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no)

Time in seconds between Gigabit Ethernet Frame Counter updates. The count during this time is defined as one sample. This time applies to packet counts contained in apexGbeStatusFrameCounterTable. To compute rate from frame count for the last update interval: Rate(bps) = (Frame_Count * 7 packets/frame 188 bytes/packet * 8 bits/byte) / Update_Interval This value is set by the APEX at startup and is constant.

Table of Gigabit Ethernet Frame Counter Statistics.

Gigabit Ethernet Interface Frame Counter Table Entry.

The index of the Gigabit Ethernet Frame Counter Table. Represents the Gigabit Ethernet interface number.

Reset Ethernet Frame Counter Statistics totals for a single GigE interface: - apexGbeTotalRxSinglecastFrames - apexGbeTotalRxMulticastFrames - apexGbeTotalRxBroadcastFrames - apexGbeTotalRxErrorFrames - apexGbeTotalRxFrames - apexGbeTotalTxGoodFrames - apexGbeTotalTxErrorFrames Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no)

Total number of singlecast Ethernet frames received since last reset. Reset using apexGbeStatusFrameCounterTableResetAll or apexGbeFrameCounterReset.

Total number of multicast Ethernet frames received since last reset. Reset using apexGbeStatusFrameCounterTableResetAll or apexGbeFrameCounterReset.

Total number of broadcast Ethernet frames received since last reset. Reset using apexGbeStatusFrameCounterTableResetAll or apexGbeFrameCounterReset.

Total number of bad Ethernet frames received since last reset. Reset using apexGbeStatusFrameCounterTableResetAll or apexGbeFrameCounterReset.

Total number of Ethernet frames received since last reset. This is the sum of apexGbeTotalRxSinglecastFrames, apexGbeTotalRxMulticastFrames, apexGbeTotalRxBroadcastFrames, and apexGbeTotalRxErrorFrames. Reset using apexGbeStatusFrameCounterTableResetAll or apexGbeFrameCounterReset.

Number of singlecast Ethernet frames received during last status checking interval. Status checking interval is apexGbeFrameCounterUpdateInterval.

Number of multicast Ethernet frames received during last status checking interval. Status checking interval is apexGbeFrameCounterUpdateInterval.

Number of broadcast Ethernet frames received during last status checking interval. Status checking interval is apexGbeFrameCounterUpdateInterval.

Number of bad Ethernet frames received during last status checking interval. Status checking interval is apexGbeFrameCounterUpdateInterval.

Number of Ethernet frames received during last status checking interval. This is the sum of apexGbeRxSinglecastFrames, apexGbeRxMulticastFrames, apexGbeRxBroadcastFrames, and apexGbeRxErrorFrames. Status checking interval is five seconds.

Total number of good Ethernet frames (singlecast, multicast, and broadcast) transmitted since last reset. Reset using apexGbeStatusFrameCounterTableResetAll or apexGbeFrameCounterReset.

Total number of bad Ethernet frames transmitted since last reset. Reset using apexGbeStatusFrameCounterTableResetAll or apexGbeFrameCounterReset.

Number of good Ethernet frames (singlecast, multicast, and broadcast) transmitted during last status checking interval. Status checking interval is five seconds.

Number of bad Ethernet frames transmitted during last status checking interval. Status checking interval is five seconds.

Number of good Ethernet frames containing DOCSIS (singlecast, multicast, and broadcast) received during last status checking interval. Status checking interval is five seconds.

Total number of good Ethernet frames containing DOCSIS(singlecast, multicast, and broadcast) received since last reset. Reset using apexGbeStatusFrameCounterTableResetAll or apexGbeFrameCounterReset.

Number of MPEG packets generated from DOCSIS data (singlecast, multicast, and broadcast) received during last status checking interval. Status checking interval is five seconds.

Number of IP fragmented packets received during last status checking interval. Status checking interval is five seconds.

Total number of IP fragmented packets received during last status checking interval. Status checking interval is five seconds.

Table of Gigabit Ethernet Frame Buffer Statistics for each GBE processor.

Gigabit Ethernet Frame Buffer Statistics Table Entry.

Index of the Gigabit Ethernet Buffer Statistics Table. Gigabit Ethernet Processor Number. Proc 1 = GBE Interfaces 1 and 2 Proc 2 = GBE Interfaces 3 and 4

The point at which the GigE frame buffer will be reset, in milliseconds. This value is equal to (maximum buffer depth - 5). The maximum buffer depth is calculated based on the expected input data rate (apexGbeConfigFrameBufferMaxInDataRate).

Current highest Gigabit Ethernet Frame Buffer level in milliseconds.

Current highest Gigabit Ethernet Frame Buffer fullness as a percentage of the buffer depth available for a given aggregate rate. This percentage is calculated using the current buffer level (apexGbeFrameBufferCurrMsLevel) and the actual input data rate.

The point at which the GigE frame buffer will underflow, in milliseconds. This value is calculated based on the sum of the number of received frames per second for all interfaces.

The point at which the GigE frame buffer will overflow, in milliseconds. This value is calculated based on the sum of the number of received frames per second for all interfaces.

The current highest severity of apexAlarmGbeBufferFullness for the GBE Processor. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

Table of Gigabit Ethernet Frame Buffer Statistics. There can be up to 24 entries in the table for each GBE Processor. Each entry represents one hour. The newest entry is placed at the beginning of the table and, if necessary, the oldest entry is pushed off the end of the table. The table will not be full until 24 hours have passed.

Gigabit Ethernet Interface Frame Buffer Table Entry.

First index of the Gigabit Ethernet Buffer Status Table. Gigabit Ethernet Processor Number. Proc 1 = GBE Interfaces 1 and 2 Proc 2 = GBE Interfaces 3 and 4

Second index of the Gigabit Ethernet Buffer Status Table. Each index represents one hour. There can be up to 24 entries in the table. The most recent entry is always at the beginning of the table.

Number of the input interface for the Gigabit Ethernet interface that experienced the highest buffer level for the hour.

Input UDP Port for the Gigabit Ethernet interface that experienced the highest buffer level for the hour.

Input Multicast IP address for the Gigabit Ethernet interface that experienced the highest buffer level for the hour.

Input IGMP v3 Source IP for the Gigabit Ethernet interface that experienced the highest buffer level for the hour.

The maximum Gigabit Ethernet frame buffer level (in milliseconds) recorded for the hour.

The maximum Gigabit Ethernet frame buffer level percentage recorded for the hour.

The GPS time when the maximum Gigabit Ethernet frame buffer level was reached.

The number of overflows recorded on Gigabit Ethernet interface for the hour.

The number of resets reported by the GigE processor during the hour.

Time in seconds between Gigabit Ethernet Input Transport Stream Packet Count updates. The count during this time is defined as one sample. This time applies to packet counts contained in apexGbeStatusInputTsTable. To compute rate from packet count for the last update interval: Rate(bps) = (Packet_Count * 188 bytes/packet * 8 bits/byte) / Update_Interval This value is set by the APEX at startup and is constant.

Table of Gigabit Ethernet Input Transport Stream status. A row in this table corresponds to the same index row in apexInputTsStatTable and apexGbeStatusInputTsErrorTable. Packet Counts are updated every apexGbeStatusInputTsUpdateInterval. The count during a apexGbeStatusInputTsUpdateInterval is a sample. The samples are accumulated into a set of rolling statistics that cover a maximum of a 15 minute sampling time period. The sampling period is the amount of time over which the data in the corresponding row has been collected. When the sampling period reaches 15 minutes, old data is removed from the accumulated statistics and new data is rolled in. In this way, the average, minimum, and peak rates for the sampling period are maintained.

Gigabit Ethernet Input Transport Stream Status Table Entry.

The Gigabit Ethernet Input Transport Stream Status table index. A row in this table corresponds to the same index row in apexInputTsStatTable and apexGbeStatusInputTsErrorTable.

The total time, in seconds, over which the packet counts statistics in this row have been collected. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Data Packet Count of the most recent sample for the primary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Average Data Packet Count per sample during apexGbeStatInTsSamplingPeriod for the primary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Minimum Data Packet Count sample during apexGbeStatInTsSamplingPeriod for the primary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Peak Data Packet Count sample during apexGbeStatInTsSamplingPeriod for the primary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Transport Stream Packet Count of the most recent sample for the primary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Average Transport Stream Packet Count per sample during apexGbeStatInTsSamplingPeriod for the primary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Minimum Transport Stream Packet Count sample during apexGbeStatInTsSamplingPeriod for the primary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Peak Transport Stream Packet Count sample during apexGbeStatInTsSamplingPeriod for the primary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Data Packet Count of the most recent sample for the secondary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Average Data Packet Count per sample during apexGbeStatInTsSamplingPeriod for the secondary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Minimum Data Packet Count sample during apexGbeStatInTsSamplingPeriod for the secondary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Peak Data Packet Count sample during apexGbeStatInTsSamplingPeriod for the secondary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Transport Stream Packet Count of the most recent sample for the secondary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Average Transport Stream Packet Count per sample during apexGbeStatInTsSamplingPeriod for the secondary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Minimum Transport Stream Packet Count sample during apexGbeStatInTsSamplingPeriod for the secondary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

The Peak Transport Stream Packet Count sample during apexGbeStatInTsSamplingPeriod for the secondary. Refer to the description of apexGbeStatusInputTsTable for an explanation of packet counting. Refer to the description of apexGbeStatusInputTsUpdateInterval for an explanation of update interval and computing rates.

Table of Gigabit Ethernet Input Transport Stream Error status. A row in this table corresponds to the same index row in apexInputTsStatTable and apexGbeStatusInputTsTable.

Gigabit Ethernet Input Transport Stream Status Table Entry.

The Gigabit Ethernet Input Transport Stream Error Status table index. A row in this table corresponds to the same index row in apexInputTsStatTable and apexGbeStatusInputTsTable.

The current highest error of the following errors for the primary input transport stream: apexGbeStatInTsPriLowBitRateError apexGbeStatInTsPriHighBitRateError apexGbeStatInTsMptsRedundPriError apexGbeStatInTsMptsRedundFailError apexGbeStatInTsPriLossInputError Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current low bit rate state for the primary input stream. Ok indicates no errors or not checking low bit rate. Error indicates primary input stream is below the low bit rate specified. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current high bit rate state for the primary input stream. Ok indicates no errors or not checking high bit rate. Error indicates primary input stream is above the high bit rate specified. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current redundant threshold state for the primary input stream. Ok indicates no errors or input stream is not part of a redundant pair. Error indicates primary input stream is below the threshold level specified. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current fail over state for a redundancy pair. Ok indicates no errors or input stream is not part of a redundant pair. Error indicates primary input stream is no longer in use and the APEX has fallen over to use the secondary input stream. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current highest error state of the following for the secondary input transport stream: apexGbeStatInTsSecLowBitRateError apexGbeStatInTsSecHighBitRateError apexGbeStatInTsSecLossInputError Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current low bit rate state for the secondary input stream. Ok indicates no errors or not checking low bit rate. Error indicates secondary input stream is below the low bit rate specified. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current high bit rate state for the secondary input stream. Ok indicates no errors or not checking high bit rate. Error indicates secondary input stream is above the high bit rate specified. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current loss of input stream state for the primary input stream. Ok indicates no errors or not checking for loss of input stream. Error indicates primary input stream is missing. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

The current loss of input stream state for the secondary input stream. Ok indicates no errors or not checking for loss of input stream. Error indicates secondary input stream is missing. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

This is a table of status parameters for GbE Interface Redundancy.

GbE Interface Redundancy Status Table Entry.

GbE Interface Pair number. Value of 1 is GbE1 and GbE2 pair. Value of 2 is GbE3 and GbE4 pair.

The current active interface for the redundant pair. This is only applicable if GbE Interface Redundancy is enabled for the pair. If GbE Interface Redundancy is not enabled it will be set to zero.

When apexGbeConfIfRedundApplyChange is set to applyNotInProgressInvalidData this entry may contain a text description of what was wrong with the data. This entry contains the description for the most recent apply of an entry that was invalid.

Current fault condition of the GbE Interface pair. Reflects apexAlarmGbeInterfaceRedundFailOver for this redundant pair. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

When set to 'update' the APEX will update the apexGbeSfpStatusTable by performing an one-time read of SFP memory. APEX sets back to 'updateNotInProgress' when complete. Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no) Enumeration: 'notApplicable': 0, 'updateNotInProgress': 1, 'update': 2.

Table of SFP status parameters. Indexed by Gigabit Ethernet Interface Number.

SFP status table entry.

Gigabit Ethernet Interface Number.

ASCII format of bytes 0-127 from SFP-MSA ID Memory Map address A0h. Zero-length indicates that no SFP module is installed.

ASCII format of bytes 96-127 from SFP Diagnostic Memory address A2h. Zero-length indicates that diagnostic information is not available.

This is the QAM Transmission Mode as defined in: Series J: Transmission of Television, Sound Programme and other Multimedia Signals, ITU-T J.83. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') Enumeration: 'annexB-ATSC-DCII': 1, 'annexC-Asia-Pacific': 3, 'annexA-DVB': 2.

This is the QAM slot number of the QAM Module that is being upgraded from a 2x4 channel module to a 2x8 channel module. Zero indicates no slot selected. Once written, the change to this table will only take immediate effect after apexQamModuleUpgradeApplyChange is set to 'apply'. @Config(config=no, reboot=no) @Commit(param=apexQamModuleUpgradeApplyChange, value=2)

This is the encrypted upgrade code for the QAM Module that is being upgraded from a 2x4 channel module to a 2x8 channel module. The Upgrade Code is specific to a QAM Module and can only be used for the QAM Module with the serial number for which the Upgrade Code was created. Once written, the change to this parameter will only take immediate effect after the corresponding apexQamModuleUpgradeApplyChange is set to 'apply'. This parameter is cleared by the APEX after the apply is complete. @Config(config=no, reboot=no) @Commit(param=apexQamModuleUpgradeApplyChange, value=2)

This is the Apply for QAM Module Upgrade Slot and Code. This parameter MUST be set to 'apply' in order for apexQamModuleUpgradeSlot and apexQamModuleUpgradeCode to take effect. This parameter MUST be set LAST after apexQamModuleUpgradeSlot and apexQamModuleUpgradeCode has been configured. The APEX will set this to applyNotInProgressInvalidData if the Upgrade Code is incorrect and the QAM Module is not upgraded. @Config(config=no, reboot=no)

Table of Apply Change for the data for apexQamRfConfigTable.

QAM Configuration Apply Table Entry.

The QAM RF Port number. Port 1,2,7,8 is Slot 1 Port 3,4,9,10 is Slot 2 Port 5,6,11,12 is Slot 3

The Apply for a row of data in apexQamRfConfigTable. A row in this table corresponds to the same row index in the apexQamRfConfigTable. This parameter MUST be set to 'apply' in order for any of the data in the rows to take effect in the APEX. This parameter MUST be set LAST after all other data in the configuration table rows has been configured. @Config(config=no, reboot=no)

Table of configuration items configurable on a QAM RF Port basis. There can be up to 12 RF Ports on an APEX1000 depending on how the 3 QAM slots are populated. There can be 2 or 4 RF Ports in each QAM slot. The 2 RF Ports in a 2x8(2x4) QAM module (1,2) in a QAM slot are mapped to table rows as follows: Slot Rows (RF port) 1 1,2 2 3,4 3 5,6 If a QAM Module in a slot only has 2 RF ports, the first three rows in this table for that slot are to be used. For example, if there is a 2x4 or 2x8 module in slot 3, port 5 and 6 are to be used for configuring the RF Ports of the module. The 4 RF Ports in a 4x4 QAM module (1,2,7,8) in a QAM slot are mapped to table rows as follows: Slot Rows (RF port) 1 1,2,7,8 2 3,4,9,10 3 5,6,11,12 All entries/rows in this table are used for the 4x4 QAM Module with any exceptions noted in the descriptions for the table entries. All entries in this table have the same ranges for the 4x4 QAM Module with any exceptions noted in the descriptions for the table entries. Refer to the description of apexQamChannelConfigTable for information on QAM Channel to RF Port mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules. Once written, the change to this table will only take immediate effect after apexQamConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

QAM RF Port Configuration Table Entry.

The QAM RF Port number.

The number of QAM Channels enabled on the RF Port. APEX will not allow enabling of more channels than the installed QAM Module will support. Note that when this parameter is changed and applied there will be an interruption in service on all active channels on this RF Port. When QAM Transmission Mode is 'annexA-DVB', enabled channels is also limited by the Channel Spacing such that the total bandwidth of the RF must not exceed 48 MHz.

The QAM Modulation mode for the QAM RF Port. This is the QAM Modulation mode of all QAM Channels enabled on the RF Port. For 4x4 QAM Modules: This parameter applies on an RF pair basis, 1-2 and 7-8. APEX1000 will use only odd table indices. Even index of pair will be ignored and set to value for odd index of pair. Enumeration: 'qam256': 2, 'qam64': 1.

The Symbol Rate Setting of the QAM Channels enabled on the RF Port. It is in symbols per second (sps). When QAM Transmission Mode is 'annexA-DVB' the range is 800,000 sps to 6,980,000 sps in 1000 sps steps. When QAM Transmission Mode is 'annexC-Asia-Pacific' the range is 800,000 sps to 5,310,000 sps in 1000 sps steps. The APEX will correct values not on a 1000 sps boundary so the user or management system does not need to enforce the step size. When QAM Transmission Mode is 'annexB-ATSC-DCII' this parameter is not configurable and is set by the APEX based on QAM Modulation Mode. For 4x4 QAM Modules: This parameter applies on an RF pair basis, 1-2 and 7-8. APEX1000 will use only odd table indices. Even index of pair will be ignored and set to value for odd index of pair. @Range(step=1000)

The Spectrum Inversion Setting of the QAM Channels enabled on the RF Port. Enumeration: 'invert': 2, 'normal': 1.

The tuning mode of the QAM Channels enabled on the RF Port. 'frequency' - The APEX tunes based on frequency as configured in RF Center Frequency for QAM Channel A and channel spacing as configured in RF Channel Spacing to determine the frequency of the B - H channels. 'channel' - The APEX tunes based on channel as configured in Channel Number for QAM Channel A using the selected Frequency Plan. The APEX will set the B - H channels to the next sequential channels. Applies only when QAM Transmission Mode is 'annexB-ATSC-DCII'. Enumeration: 'frequency': 1, 'channel': 2.

This is the frequency plan to use for tuning of the QAM Channels enabled on the RF Port. Frequency plans are as per CEA Standard: Cable Television Channel Identification Plan (CEA-542-B). This parameter is valid only when QAM Transmission Mode is 'annexB-ATSC-DCII'. 'std' - Standard (STD) North American frequency plan. 'hrc' - Harmonic Related Carrier (HRC) frequency plan. 'irc' - Incremental Related Carrier (IRC) frequency plan. Enumeration: 'std': 1, 'irc': 3, 'hrc': 2.

The Channel Number for QAM Channel A. Range is 0 to 158, with valid channels being 1 to 158 and 0 indicating 'not applicable'. This parameter is valid only when QAM Transmission Mode is 'annexB-ATSC-DCII'. This parameter is configurable only when Tuning Mode is 'channel'. When Tuning Mode is 'channel', this is the Channel Number used to determine the output frequency of QAM Channel A using the selected Frequency Plan. When Tuning Mode is 'frequency', this value is determined by the APEX using the selected Frequency Plan. If there is no channel number for the frequency, the value is set to zero. This parameter is not configurable for Transmission Modes of 'annexA-DVB' or 'annexC-Asia-Pacific' and the value is set to zero by the APEX. Channel 1 is not defined in CEA Standard: Cable Television Channel Identification Plan (CEA-542-B) for the Standard (STD) North American frequency plan. Channel 1 cannot be selected when apexQamRfConfigEiaFrequencyPlan is 'std'. Channel 2 as defined in defined in CEA Standard: Cable Television Channel Identification Plan (CEA-542-B) for the Harmonic Related Carrier (HRC) frequency plan is below the APEX 57 MHz minimum frequency. Channel 2 cannot be selected when apexQamRfConfigEiaFrequencyPlan is 'hrc'. For 4x4 QAM Modules: Channels with frequencies below 69 MHz may not be available. This limitation is dependent upon the HW version installed and number of channels enabled.

The RF Center Frequency for QAM Channel A. When QAM Transmission Mode is 'annexA-DVB' the range is 85,000,000 Hz to 999,000,000 Hz in 250,000 Hz steps. For 2x4/2x8 QAM Modules: When QAM Transmission Mode is 'annexB-ATSC-DCII' or 'annexC-Asia-Pacific' the range is 57,000,000 Hz to 999,000,000 Hz in 250,000 Hz steps. For 4x4 QAM Modules: When QAM Transmission Mode is 'annexB-ATSC-DCII' or 'annexC-Asia-Pacific' the range may be limited to 69,000,000 Hz to 999,000,000 Hz in 250,000 Hz steps. This limitation is dependent upon the HW version installed and number of channels enabled. The APEX will correct values not on a 250 kHz boundary so the user or management system does not need to enforce the step size. This parameter is configurable ONLY when Tuning Mode is 'frequency'. When Tuning Mode is 'channel', the value is set by the APEX using the selected Frequency Plan. @Range(step=250000)

The Channel spacing for the QAM Channels enabled on the RF Port. This value must be in Hz in the range 1,000,000 Hz to 8,000,000 Hz in 500,000 Hz steps. The APEX will correct values not on a 500,000 Hz boundary so the user or management system does not need to enforce the step size. For 2x4/2x8 QAM Modules: When Transmission Mode is 'annexA-DVB' this value is configurable. Note that number of channels enabled can be affected by changing channel spacing. The total bandwidth of the RF must not exceed 48 MHz. For 2x4/2x8 QAM Modules: When Transmission Mode is 'annexB-ATSC-DCII' or 'annexC-Asia-Pacific' this value is fixed and is set by the APEX. For 4x4 QAM Modules: This value is fixed and is set by the APEX. @Range(step=500000)

The RF level attenuation setting of each enabled channel on the RF Port. Range is -300 to 800 representing -3 to 8 dB attenuation in 0.01 dB steps. (See 'Note' below.) Positive values are the amount below the nominal RF output level for the number of channels enabled on the RF Port. Negative values are the amount above the nominal. Number Nominal dBmV dBmV Channels dBmV W/-300 W/800 1 60 63 52 2 56 59 48 4 52 55 44 6 50 53 42 8 49 52 41 Note: Early APEX only supported attenuation. Gain was added later, hence the negative attenuation values for this parameter. For clarity, the APEX Element Manager display indicates 'RF Level Adjust', with a user selectable range of -8.00 to +3.00 dB, rather than 'Attenuation'. The APEX EM then sets this MIB parameter appropriately.

The threshold delta relative to the configured RF level that will indicate an RF Low condition. The measured output must drop this amount for RF Low condition. Range is 0 to 100 representing 0 to 10 dB in 0.1 dB steps.

The threshold delta relative to the configured RF level that will indicate an RF High condition. The measured output must rise this amount for RF High condition. Range is 0 to 100 representing 0 to 10 dB in 0.1 dB steps.

Mute the RF Port. This will mute all QAM channels enabled on the RF Port. Enumeration: 'unmute': 1, 'mute': 2.

The first of two Interleaver settings that can be assigned to the QAM Channels of this RF Port. Configurable only for Transmission Mode 'annexB-ATSC-DCII'. Values 1 to 12 used only for Transmission Mode 'annexB-ATSC-DCII'. Value 13 (i12-j17) used only for Transmission Modes 'annexA-DVB' and 'annexC-Asia-Pacific' and is set by the APEX. Enumeration: 'i16-j8': 3, 'i64-j2': 1, 'i32-j4': 2, 'i12-j17': 13, 'i128-j4': 8, 'i128-j5': 9, 'i128-j6': 10, 'i128-j7': 11, 'i128-j1': 5, 'i128-j2': 6, 'i128-j3': 7, 'i8-j16': 4, 'i128-j8': 12.

The second of two Interleaver settings that can be assigned to the QAM Channels of this RF Port. Configurable only for Transmission Mode 'annexB-ATSC-DCII'. Values 1 to 12 used only for Transmission Mode 'annexB-ATSC-DCII'. Value 13 (i12-j17) used only for Transmission Modes 'annexA-DVB' and 'annexC-Asia-Pacific' and is set by the APEX. Enumeration: 'i16-j8': 3, 'i64-j2': 1, 'i32-j4': 2, 'i12-j17': 13, 'i128-j4': 8, 'i128-j5': 9, 'i128-j6': 10, 'i128-j7': 11, 'i128-j1': 5, 'i128-j2': 6, 'i128-j3': 7, 'i8-j16': 4, 'i128-j8': 12.

Table of configuration items configurable on a QAM Channel basis. There are 48 Output Transport Streams (OTS) on an APEX1000. There can be up to 48 QAM Channels on an APEX1000 depending on how the 3 QAM slots are populated. There is a one-to-one mapping between QAM Channels and Output Transport Streams. QAM Channel (OTS) ranges are mapped to QAM slots as follows: Slot Channels 1 1..15 2 15..32 3 33..48 There can be either 4 or 8 QAM channels (OTS) on each RF Port. The slot and RF Port to QAM Channel (OTS) mappings for each QAM Module type are shown below. For a 2x4 or 2x8 QAM Module, QAM Channels (OTS) are mapped to RF Ports in a QAM Slot and table rows as follows: QAM Channel RF Port and OTS Slot/Port Table Row Table Rows 1/1 1 1..8 1/2 2 9..16 2/1 5 17..24 2/2 6 25..32 3/1 9 33..40 3/2 10 41..48 If a 2x4 QAM Module is in a slot, only the first four rows in this table for the slot/port are to be used. For example, if there is a 2x4 module in slot 3, rows 8..12 are to be used for configuring the QAM Channels of RF Port 1 on the module. For a 4x4 QAM Module, QAM Channels (OTS) are mapped to RF Ports in a QAM Slot and table rows as follows: QAM Channel RF Port and OTS Slot/Port Table Row Table Rows 1/1 1 1..4 1/2 2 5..8 1/3 7 9..12 1/4 8 13..16 2/1 3 17..20 2/2 4 21..24 2/3 9 25..28 2/4 10 29..32 3/1 5 33..36 3/2 6 37..40 3/3 11 41..44 3/4 12 45..48 Note that the QAM Channels on an RF Port are designated with the letters 'A'..'H' on the APEX Element Manager. Refer to the description of apexQamChannelConfigTable for information on QAM Channel to RF Port mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules. Once written, the change to this table will only take immediate effect after apexQamConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamChannelConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

QAM Channel Configuration Table Entry.

The QAM RF Port number.

The interleaver selection for this Channel. Will use either apexQamRfConfigInterleaverDepth1 or apexQamRfConfigInterleaverDepth2. Enumeration: 'interleaverDepth2': 2, 'interleaverDepth1': 1.

Test mode setting for the QAM Channel. Setting to other than 'off' will cause a service interruption. Enumeration: 'prbs79': 16, 'off': 0, 'cwtest': 2, 'suppress': 9, 'prbs73': 15, 'prbs71': 14, 'prbs23m': 3, 'prbs81': 17, 'prbs65': 12, 'prbs63': 11, 'prbs60': 10, 'prbs23': 5, 'mpegNull': 6, 'prbs68': 13.

The Apply for QAM RF Redundancy Configuration parameters. This parameter MUST be set to 'apply' in order for the data to take effect. This parameter MUST be set LAST after all QAM RF Redundancy parameters affected by this parameter have been configured. @Config(config=no, reboot=no)

Enables RF redundancy mode, allowing the APEX to failover to backup RF port and communicate with the REM1000. Allows for failover/ switching without requiring a REM1000 connection. Cannot be 'enabled' if the backup port (RF Port 6) is not present (there is no QAM Module in QAM slot 3). Cannot be 'enabled' if there are any mappings to any QAM Channel on the backup port. RF Port 6, QAM Channels 6A to 6H (Output Transport Streams 41 to 48). Once written, the change to this parameter will only take immediate effect after apexQamRfRedundConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamRfRedundConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Configures how the APEX is connected to the REM1000. 'none' - Not connecting to REM1000. 'direct' - Connected to REM1000 dedicated IP interface through APEX Data IP (Enet2). Broadcast connection is always used in this case. Cannot be set to 'direct' if the QAM RF Redundancy UDP Port is in use on the Data IP Port (Enet2). QAM RF Redundancy UDP Port value is found in apexQamRfRedundStatusUdpPort. 'common' - Connected to REM1000 OAM&P interface through APEX OAM&P IP (Enet 1). Requires user to configure REM1000 IP address in apexQamRfRedundConfigRemCommonIpAddr. Cannot be set to 'common' if the QAM RF Redundancy UDP Port is in use on the OAM&P IP (Enet 1). QAM RF Redundancy UDP Port value is found in apexQamRfRedundStatusUdpPort. Once written, the change to this parameter will only take immediate effect after apexQamRfRedundConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamRfRedundConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') Enumeration: 'none': 0, 'direct': 1, 'common': 2.

Identifies which set of RF inputs on the REM1000 are associated with this APEX. Once written, the change to this parameter will only take immediate effect after apexQamRfRedundConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamRfRedundConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Target REM1000 IP address. Must be singlecast address. Only used when apexQamRfRedundConfigRemConnection is set to 'common'. Once written, the change to this parameter will only take immediate effect after apexQamRfRedundConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamRfRedundConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

This is the enable/disable of automatic switch back to the previous RF port from backup for QAM RF redundancy. When 'enabled', switch back to the previous RF port will automatically occur when the RF port comes back online. When 'disabled', the user must force back to the previous RF port using apexQamRfRedundConfigForceSwitch. Once written, the change to this parameter will only take immediate effect after apexQamRfRedundConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamRfRedundConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Enables and disables suspending of RF failover. Prevents failovers to or from backup. Force failover (apexQamRfRedundConfigForceSwitch) overrides this setting. Once written, the change to this parameter will only take immediate effect after apexQamRfRedundConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamRfRedundConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Force a switch of an RF Port to or from the backup. Selects which RF Port to switch from. Overrides Suspend Failover (apexQamRfRedundConfigSuspendFailover). Parameter is ignored when: - apexQamRfRedundConfigEnable is 'disabled'. - backup is active and other than 'forceFromBackup' is selected. - backup is not active and 'forceFromBackup' is selected. 'forceFromBackup' will force back to the failed primary indicated in apexQamRfRedundStatusFailedPort. APEX sets back to 'switchNotInProgress' when complete. Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no) Enumeration: 'forceFrom5': 5, 'forceFromBackup': 6, 'switchNotInProgress': 0, 'forceFrom4': 4, 'forceFrom1': 1, 'forceFrom3': 3, 'forceFrom2': 2.

Target REM1000 IP address first octet. Only used when apexQamRfRedundConfigRemConnection is set to 'direct'. The remainder of the IP address will be filled in by the APEX. The IP address used will be reflected in apexDataIpAddrInUse. Once written, the change to this parameter will only take immediate effect after apexQamRfRedundConfigApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexQamRfRedundConfigApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini')

Table of Apply Change for the data for apexQamChannelConfigTable.

QAM Channel Configuration Apply Table Entry.

The QAM Channel number.

The Apply for a row of data in apexQamChannelConfigTable. A row in this table corresponds to the same row index in the apexQamChannelConfigTable. This parameter MUST be set to 'apply' in order for any of the data in the rows to take effect in the APEX. This parameter MUST be set LAST after all other data in the configuration table rows has been configured. @Config(config=no, reboot=no)

This is the QAM Transmission Mode that is currently in use. QAM Transmission Mode is defined in: Series J: Transmission of Television, Sound Programme and other Multimedia Signals, ITU-T J.83. Enumeration: 'annexB-ATSC-DCII': 1, 'annexC-Asia-Pacific': 3, 'annexA-DVB': 2.

Number of hot swappable QAM Modules currently installed.

Number of Fan-Only Modules currently installed in QAM Module slots.

Number of QAM Channels that are present (QAM Module installed) and enabled for use.

Table of QAM Module Status. Refer to the descriptions of apexQamRfConfigTable and apexQamChannelConfigTable for information on QAM slot, RF Port mapping, and QAM Channel mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules.

QAM Module Status Table Entry.

QAM Module slot number.

Indicates if a module is installed and what type. notApplicable - When APEX does not boot properly. notInstalled - No QAM or Fan Module detected in slot. Reported in apexAlarmQamModuleFault. qam2x4Channel - A 2x4 Channel QAM Module installed. qam2x8Channel - A 2x8 Channel QAM Module installed. fanModule - A Fan Module installed. unsupported - Unknown module installed. Reported in apexAlarmQamModuleFault. removed - A QAM Module removed when there are active QAM channels. Reported in apexAlarmQamModuleFault. qamDiscovery - A QAM Module is present and type is being determined. qam4x4Channel - A 4x4 Channel QAM Module is installed. Enumeration: 'qam2x4Channel': 2, 'qam4x4Channel': 8, 'qam2x8Channel': 3, 'fanModule': 4, 'notInstalled': 1, 'unsupported': 5, 'qamDiscovery': 7, 'notApplicable': 0, 'removed': 6.

The fan speed in RPM for installed QAM or Fan Module. Zero if not installed.

Fan Fault. This fault is reported in apexAlarmFanFault not apexAlarmQamModuleFault. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

Temperature at sensor near the fan of the QAM Module or Fan Module in degrees Celsius.

Temperature fault. This fault is reported in apexAlarmTemperatureFault not apexAlarmQamModuleFault. Enumeration: 'overTemp': 2, 'notApplicable': 0, 'ok': 1.

Summary of errors reported on an QAM Module basis. These errors are reported in apexAlarmQamModuleFault. ok - No errors. removed - Reflects apexQamModuleStatInstalled. unsupported - Reflects apexQamModuleStatInstalled. notInstalled - Reflects apexQamModuleStatInstalled. powerFault - Reflects apexQamModuleStatPowerFault. offline - Indicates the QAM Module and the RF Ports on it are being brought to operational mode after module is inserted or the module has recovered from a power fault. dc5VoltError - 5 Vdc error, see also apexQamModuleStat5VdcSupply and apexQamModuleStat5VdcFault. dc3-3VoltError - 3.3 Vdc error, see also apexQamModuleStat3dot3VdcSupply and apexQamModuleStat3dot3VdcFault. commLost - Communication Lost, see also apexQamModuleStatCommError. codeVersions - Incorrect Code Versions on module, see also apexQamModuleStatCodeInitError, apexQamQrmRevisionTable, and apexQamQrmRevisionStatusTable. codeDownload - Code Download In Progress, see also apexQrmDownloadStatusTable. codeDownloadError - Code Download Error, see also apexQrmDownloadStatusTable. Enumeration: 'powerFault': 5, 'ok': 1, 'dc5VoltError': 7, 'notInstalled': 4, 'unsupported': 3, 'codeDownload': 11, 'notApplicable': 0, 'codeVersions': 10, 'dc3-3VoltError': 8, 'offline': 6, 'removed': 2, 'commLost': 9, 'codeDownloadError': 12.

Current fault condition of the QAM Module errors. Reflects apexAlarmQamModuleFault for this QAM Module. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

Roll-up of QAM RF Port and QAM Channel fault conditions for this QAM Module. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

Power fault. notApplicable - No module installed. ok - Power good. lowVoltageMainboard - Low voltage detected on Mainboard side of connector. lowVoltageQamModule - Low voltage detected on QAM Module side of connector. overCurrent - Over current detected on QAM Module. This fault is reported in apexAlarmQamModuleFault. Enumeration: 'lowVoltageQamModule': 3, 'notApplicable': 0, 'lowVoltageMainboard': 2, 'ok': 1, 'overCurrent': 4.

Temperature of the 4x4 QAM module board ('plate' temp) in degrees Celsius. Used only for 4x4 QAM Modules.

Board temperature fault of the 4x4 QAM module board ('plate' temp). Used only for 4x4 QAM Modules. This fault is reported in apexAlarmTemperatureFault not apexAlarmQamModuleFault. Enumeration: 'overTemp': 2, 'notApplicable': 0, 'ok': 1.

Measured level of the +5 VDC supply input of the 4x4 QAM module board. Used only for 4x4 QAM Modules. Range is 0 to 1000 representing 0 to 10 Volts in 0.01 Volt steps.

The +5 VDC supply fault of the 4x4 QAM module board. Used only for 4x4 QAM Modules. Indicates there is a problem with the direct 5 VDC supply or any internal module supply derived from the 5 VDC supply. Indicates voltage problem that can impair module function. Enumeration: 'high': 3, 'notApplicable': 0, 'ok': 1, 'low': 2.

Measured level of the +3.3 VDC supply input of the 4x4 QAM module board. Used only for 4x4 QAM Modules. Range is 0 to 1000 representing 0 to 10 Volts in 0.01 Volt steps.

The +3.3 VDC supply fault of the 4x4 QAM module board. Used only for 4x4 QAM Modules. Indicates there is a problem with the direct 3.3 VDC supply or any internal module supply derived from the 3.3 VDC supply. Indicates voltage problem that can impair module function. Enumeration: 'high': 3, 'notApplicable': 0, 'ok': 1, 'low': 2.

Communication with the 4x4 QAM Module has failed. Used only for 4x4 QAM Modules. Enumeration: 'notApplicable': 0, 'commLost': 2, 'inComm': 1.

Code initialization error of the 4x4 QAM Module. Used only for 4x4 QAM Modules. Indicates a code, firmware, or FPGA startup issue. The module failed to load the FW/FPGA files to the devices or valid FW/FPGA files could not be found in the module. Code download is required to restore the module. Enumeration: 'notApplicable': 0, 'ok': 1, 'error': 2.

Table of QAM Module Serial Numbers.

QAM Module Serial Number Table Entry.

QAM Module slot number.

The serial number of an installed QAM Module. Zero if not installed.

Table of QAM Module hardware and software revisions. There are 2 QRM modules on each 2x4/2x8 QAM Module. QRMs in QAM Module slots are mapped to table rows as follows: Slot/QRM Table Row 1/1 1 1/2 2 2/1 3 2/2 4 3/1 5 3/2 6 4x4 QAM Modules do not use QRM boards. There is only one board. These will be found in the odd indexed rows of this table. The even indexed rows of the table are not used for 4x4 QAM Modules. 4x4 QAM Modules in QAM Module slots are mapped to table rows as follows: Slot Table Row 1 1 2 3 3 5

QAM Module Revision Table Entry.

QAM Module Revision Table index.

Model ID of the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Hex XXYY.

Application firmware version of the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Hex XXYY where XX is major version and YY is minor version. 'FFFF' indicates no valid application code is present.

Boot loader firmware version of the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Hex XXYY where XX is major version and YY is minor version.

FPGA version of the 2x4/2x8 QAM Module's QRM board or FPGA1 version of the 4x4 QAM Module. Hex XXYY where XX is major version and YY is minor version.

Hardware version of the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Hex XXYY where XX is major version and YY is minor version.

The serial number of the 2x4/2x8 QAM Module's QRM board. Used only for 2x4/2x8 QAM Modules. Zero if not installed.

FPGA2 version of the 4x4 QAM Module. Used only for 4x4 QAM Modules. Hex XXYY where XX is major version and YY is minor version.

Table of QAM RF Port Status. Refer to the descriptions of apexQamRfConfigTable and apexQamChannelConfigTable for information on QAM slot, RF Port mapping, and QAM Channel mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules.

QAM RF Port Status Table Entry.

RF Port number.

The information rate of the QAM channels on this RF Port in bits per second.

Number of QAM Channels that are present (QAM Module installed) and enabled for use on this RF Port.

Measured per channel RF Output Level. Range is 0 to 8000 representing 0 to 80 dBmV in 0.01 dBmV steps.

RF Output Level fault. Indicates if the user configured apexQamRfConfigRfLevelLowThreshold or apexQamRfConfigRfLevelHighThreshold has been reached. Enumeration: 'high': 3, 'notApplicable': 0, 'ok': 1, 'low': 2.

Temperature of the 2x4/2x8 QAM Module's QRM board ('plate' temp) in degrees Celsius. Used only for 2x4/2x8 QAM Modules.

Temperature fault of the 2x4/2x8 QAM Module's QRM board ('plate' temp). Used only for 2x4/2x8 QAM Modules. This fault is reported in apexAlarmTemperatureFault not apexAlarmQamRfPortFault. Enumeration: 'overTemp': 2, 'notApplicable': 0, 'ok': 1.

Measured level of the +5 VDC supply input of the 2x4/2x8 QAM Module's QRM board. Used only for 2x4/2x8 QAM Modules. Range is 0 to 1000 representing 0 to 10 Volts in 0.01 Volt steps.

The +5 VDC supply fault of the 2x4/2x8 QAM Module's QRM board. Used only for 2x4/2x8 QAM Modules. Indicates voltage problem that can impair QRM function. Enumeration: 'high': 3, 'notApplicable': 0, 'ok': 1, 'low': 2.

Measured level of the +3.3 VDC supply input of the 2x4/2x8 QAM Module's QRM board. Used only for 2x4/2x8 QAM Modules. Range is 0 to 1000 representing 0 to 10 Volts in 0.01 Volt steps.

The +3.3 VDC supply fault of the 2x4/2x8 QAM Module's QRM board. Used only for 2x4/2x8 QAM Modules. Indicates voltage problem that can impair QRM function. Enumeration: 'high': 3, 'notApplicable': 0, 'ok': 1, 'low': 2.

Frequency tuning PLL lock status. Enumeration: 'notLocked': 2, 'notApplicable': 0, 'locked': 1.

External reference clock present indication. Enumeration: 'notApplicable': 0, 'notPresent': 2, 'present': 1.

Board not phase-locked to the External reference clock. Enumeration: 'notLocked': 2, 'notApplicable': 0, 'locked': 1.

Data clock present indication. Enumeration: 'notApplicable': 0, 'notPresent': 2, 'present': 1.

One or more of the QAM Channel data interfaces is not synchronized. Enumeration: 'notApplicable': 0, 'syncLost': 2, 'inSync': 1.

Communication with the 2x4/2x8 QAM Module's QRM board has failed. Enumeration: 'notApplicable': 0, 'commLost': 2, 'inComm': 1.

Error status on an RF Port basis. These errors are reported in apexAlarmQamRfPortFault. 'major' for: 'outputRfLevel', 'dc5VoltError', 'dc3-3VoltError'. 'critical' for: 'freqPllNotLocked', 'extClkNotPresent', 'extClkNotLocked', 'dataClkNotPresent', 'dataSyncLost', 'commLost', 'codeVersions', 'codeDownload', 'codeDownloadError', 'unsupportedQrm', or 'configFailed'. outputRfLevel - RF Output Level error, see also apexQamRfPortStatOutputLevel and apexQamRfPortStatOutputLevelFault. dc5VoltError - 5 Vdc error, see also apexQamRfPortStat5VdcSupply and apexQamRfPortStat5VdcFault. dc3-3VoltError - 3.3 Vdc error, see also apexQamRfPortStat3dot3VdcSupply and apexQamRfPortStat3dot3VdcFault. freqPllNotLocked - Frequency PLL not locked, see also apexQamRfPortStatFreqPllLock. extClkNotPresent - External Reference Clock Not Present, see also apexQamRfPortStatRefClockPresent. extClkNotLocked - Not Locked to External Reference Clock, see also apexQamRfPortStatRefClockLock. dataClkNotPresent - Data Clock Not Present, see also apexQamRfPortStatDataClockPresent. dataSyncLost - Data Synchronization Lost, see also apexQamRfPortStatDataSyncFault. commLost - Communication Lost, see also apexQamRfPortStatCommError. unsupportedQrm - QRM Revision Not Supported, see also apexQamQrmRevisionTable and apexQamQrmRevisionStatusTable. configFailed - RF Port Configuration Failed. codeVersions - Incorrect Code Versions on QRM, see also apexQamRfPortStatCodeInitError, apexQamQrmRevisionTable, and apexQamQrmRevisionStatusTable. codeDownload - Code Download In Progress, see also apexQrmDownloadStatusTable. codeDownloadError - Code Download Error, see also apexQrmDownloadStatusTable. Enumeration: 'ok': 1, 'dc5VoltError': 3, 'configFailed': 12, 'dataSyncLost': 9, 'codeDownloadError': 15, 'extClkNotPresent': 6, 'notApplicable': 0, 'codeDownload': 14, 'extClkNotLocked': 7, 'dataClkNotPresent': 8, 'freqPllNotLocked': 5, 'codeVersions': 13, 'dc3-3VoltError': 4, 'commLost': 10, 'unsupportedQrm': 11, 'outputRfLevel': 2.

Current fault condition of the RF Port errors. Reflects apexAlarmQamRfPortFault for this RF Port. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

Roll-up of Channel fault conditions for this RF Port. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

Code initialization error of the 2x4/2x8 QAM Module's QRM board. Indicates a code, firmware, or FPGA startup issue. 'fpgaInitError' - FPGA not loaded. Caused by incompatible code images or corrupted FPGA image on the QRM. 'calDataError' - Working copy of calibration data was corrupted and needs to be restored by code download process. Caused by interruption of previous code download process. Enumeration: 'notApplicable': 0, 'calDataError': 3, 'fpgaInitError': 2, 'ok': 1.

Table of QAM Channel Status. Refer to the descriptions of apexQamRfConfigTable and apexQamChannelConfigTable for information on QAM slot, RF Port mapping, and QAM Channel mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules.

QAM Channel Status Table Entry.

QAM Channel number.

'active' indicates that mappings can be made to the channel. This means that either: 1) The channel is present (apexQamModuleStatInstalled 'qam2x4Channel' or 'qam2x8Channel') and enabled for use (apexQamRfConfigNumChannelsEnabled); 2) Or, the channel is on the backup RF port when QAM RF Redundancy is enabled (apexQamRfRedundConfigEnable).

The center frequency for the QAM Channel in Hz.

The EIA Channel number for the QAM Channel. Will be zero if there is no EIA Channel number corresponding to the frequency in use.

Indication of MPEG data activity on the interface for this QAM channel. This includes MPEG null packets. Enumeration: 'notApplicable': 0, 'noData': 2, 'data': 1.

Summary of errors reported on a QAM channel. This is enumerated and the reported error will be the most severe. Enumeration: 'notApplicable': 0, 'noData': 2, 'ok': 1.

Current fault condition of the QAM channel errors. Reflects apexAlarmQamChannelFault for this QAM Channel. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

State of configured backup port. 'disabled' - QAM RF Redundancy is disabled. 'standby' - QAM RF Redundancy is enabled but backup is inactive. No failure has occurred. 'active' - Failover has occurred and backup is active. Refer to apexQamRfRedundStatusFailedPort for port being backed up. 'failed' - Backup port has failed. APEX cannot provide RF redundancy. 'removed' - QAM Module with Backup port has been removed. APEX cannot provide RF redundancy. Enumeration: 'disabled': 0, 'standby': 1, 'removed': 4, 'active': 2, 'failed': 3.

Indicates which port (1 to 5) has failed over to the backup port. Zero indicates backup port is not active.

Indicates whether there is a potential for channels being lost when failing to the backup or when switching back to a primary due to a mixture of 2x4 and 2x8 QAM Modules. Indicates whether RF redundancy is unavailable due to a 4x4 QAM Module installed. A 2x4 QAM Module is capable of supporting a maximum of 4 channels per RF port. A 2x8 QAM Module is capable of supporting a maximum of 8 channels per RF port. The number of channels enabled (apexQamRfConfigNumChannelsEnabled) is not considered. 'notApplicable' - QAM RF Redundancy is disabled. 'noMismatch' - Indicates no channels would be lost because there is no mismatch. 'backup2x4' - Indicates a loss of channels could occur on failover to the backup because the backup RF Port is in a 2x4 module and at least one primary RF Port is in a 2x8 module. 'primary2x4' - Indicates a loss of channels could occur on switch- back from the backup to the primary because the backup RF Port is in a 2x8 module and the primary RF Port is in a 2x4 module. This would occur if the failed 2x8 primary is replaced with a 2x4. 'any4x4' - Indicates a 4x4 QAM Module is installed in any slot and RF Redundancy is not available. Failover and/or switchback are suspended until the 4x4 is replaced. Enumeration: 'notApplicable': 0, 'primary2x4': 3, 'noMismatch': 1, 'any4x4': 4, 'backup2x4': 2.

UDP Port that is used for QAM RF Redundancy communication between the APEX and REM. When apexQamRfRedundConfigRemConnection is: 'direct' - APEX sends/receives broadcast on this UDP Port. 'common' - APEX sends/receives singlecast on this UDP Port.

State of communication with REM. 'notApplicable' - QAM RF Redundancy is not enabled and/or the connection to the REM is not enabled. 'notConnected' - Initial condition. APEX has not sent a switch_port() message yet. 'connected' - received ack() message from REM for current switch_port() message. 'connectionLost' - REM has not replied to last 3 heartbeat switch_port() messages. Enumeration: 'notConnected': 1, 'notApplicable': 0, 'connectionLost': 3, 'connected': 2.

Status of REM1000 taken from error_code field in REM1000 ack() response (defined in REM1000 Message Stream Protocol). Valid only when apexQamRfRedundConfigRemConnection is other than 'none'. Values as defined in REM1000 MSP: 0x00 - No Errors. No problems switching, parsing switch_port() message, or with HW. 0x01 - Invalid apex_id value in prior switch_port() message. 0x02 - Invalid msg_type value in prior switch_port() message. 0x03 - Invalid port value in prior switch_port() message. 0x04 - Error switching after receiving valid switch_port() message. 0x05 - Minor HW error. REM can still switch. 0x81 - Apex_id Conflict. Switch_port() messages with the same apex_id have been received from multiple APEXs. Switch reset to pass- through configuration. 0x85 - Major HW error. REM failure. Switch reset to pass-through configuration.

Status of the REM1000 switches indicated through ack() response from REM1000 (e.g. pass-through or switching port 'x'). Valid only when apexQamRfRedundConfigRemConnection is other than 'none'. Zero indicates REM is in passing inputs 1 to 5 straight through to outputs 1 to 5. Values of 1 to 5 indicate REM backup input port is switched to output port 1 to 5 and other ports are passed through.

When apexQamRfRedundConfigApplyChange is set to 'applyNotInProgressInvalidData' this entry may contain a text description of what was wrong with the data. This entry contains the description for the most recent apply of a related entry that was invalid.

Table of QAM RF Port Mute Status.

QAM RF Port Mute Status Table Entry.

RF Port number.

Indicates whether the QAM channels on the RF port are muted or unmuted. Enumeration: 'muted': 2, 'unmuted': 1.

Table of status of QRM hardware and software revisions. Indications of whether they are supported, current, etc.. There are 2 QRM modules on each 2x4/2x8 QAM Module. QRMs in QAM Module slots are mapped to table rows as follows: Slot/QRM Table Row 1/1 1 1/2 2 2/1 3 2/2 4 3/1 5 3/2 6 4x4 QAM Modules do not use QRM boards. There is only one board. These will be found in the odd indexed rows of this table. The even indexed rows of the table are not used for 4x4 QAM Modules. 4x4 QAM Modules in QAM Module slots are mapped to table rows as follows: Slot Table Row 1 1 2 3 3 5

QRM Revision Status Table Entry

QRM Revision Status Table index.

Status of the Model ID of the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Refer to apexQamQrmRevisionTable for the revisions of each QRM. Enumeration: 'supported': 2, 'notApplicable': 0, 'notSupported': 1.

Status of Application firmware version of the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Refer to apexQamQrmRevisionTable for the revisions of each 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Refer to apexQrmFileRevisionTable for the revisions of files in the APEX release resident on the device. Enumeration: 'notApplicable': 0, 'aboveRelease': 4, 'notSupported': 1, 'atRelease': 3, 'belowRelease': 2.

Status of Boot loader firmware version of the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Refer to apexQamQrmRevisionTable for the revisions of each 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Enumeration: 'supported': 2, 'notApplicable': 0, 'notSupported': 1.

Status of FPGA version of the 2x4/2x8 QAM Module's QRM board or FPGA1 version of the 4x4 QAM Module. Refer to apexQamQrmRevisionTable for the revisions of each 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Refer to apexQrmFileRevisionTable for the revisions of files in the APEX release resident on the device. Enumeration: 'notApplicable': 0, 'aboveRelease': 4, 'notSupported': 1, 'atRelease': 3, 'belowRelease': 2.

Status of Hardware version of the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Refer to apexQamQrmRevisionTable for the revisions of each 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board. Enumeration: 'supported': 2, 'notApplicable': 0, 'notSupported': 1.

Indicates if the 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board is supported. Summary of above status. If any 4x4 QAM Module or the 2x4/2x8 QAM Module's QRM board revision status is 'notSupported' this parameter will indicate 'notSupported' and apexQamRfPortStatError will report 'unsupportedQrm'. Enumeration: 'supported': 2, 'notApplicable': 0, 'notSupported': 1.

Status of FPGA2 version of the 4x4 QAM Module. Refer to apexQamQrmRevisionTable for the revisions of each 4x4 QAM Module. Refer to apexQrmFileRevisionTable for the revisions of files in the APEX release resident on the device. Enumeration: 'notApplicable': 0, 'aboveRelease': 4, 'notSupported': 1, 'atRelease': 3, 'belowRelease': 2.

Table of QAM Channel information for each QAM RF Port. Refer to the descriptions of apexQamRfConfigTable and apexQamChannelConfigTable for information on QAM slot, RF Port mapping, and QAM Channel mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules.

QAM RF Port Channel Information Table Entry.

RF Port number.

QAM Channel number (Output Transport number) of QAM Channel 'A' on this RF port. This may be used to access data in tables indexed by QAM Number or Output Transport Stream. Used in combination with apexQamRfPortChannelInfoChanCount, data for all QAM Channels on this RF Port may be accessed. '0' - Indicates RF Port is not present.

The number of QAM Channels on the RF port. '0' - Indicates RF Port is not present. '4' - RF Port has 4 QAM Channels, 'A'-'D'. '8' - RF Port has 8 QAM Channels, 'A'-'H'.

Table of QAM Channel Identification data. Identifies the physical location of the QAM Channel (Output Transport Stream) in the APEX chassis. Refer to the descriptions of apexQamRfConfigTable and apexQamChannelConfigTable for information on QAM slot, RF Port mapping, and QAM Channel mapping. Tables apexQamRfPortChannelInfoTable and apexQamChannelIdTable can be used to assist in referencing between QAM slots, RF Ports, and QAM Channels (Output Transport Streams) for the installed modules.

QAM Channel Identification Table Entry.

QAM Channel number (Output Transport number).

QAM Slot number of the channel.

RF Port number of the channel. This may be used to access data in tables indexed by RF Port Number. '0' - Indicates QAM Channel is not present.

Module RF Port number of the channel. Corresponds to RF Port numbering on the back of physical QAM Module. '0' - Indicates QAM Channel is not present.

The letter symbol ('A'..'H') for the channel. String will be empty if QAM Channel not present.

Text description for the QAM Channel (Output Transport Stream). Format is as follows where brackets and bracketed descriptions are replaced by a number/letter as appropriate: [QAM Channel / TS Num]:Slot[QAM Slot Num]-[Module Rf Port Num][Channel Letter] Examples: TS 9, in QAM Slot 1, on RF Port 2: '09:Slot1-2A' TS 17, in QAM Slot 2, on RF Port 1: '17:Slot2-1A' TS 48, in QAM Slot 3, on RF Port 2: '48:Slot3-2H' TS 48, in QAM Slot 3, on RF Port 4: '48:Slot3-4D' This may be used for display purposes on a management system. String will be empty or contain '[QAM Channel / TS Num]:Inactive' if apexQamChanStatActive is not set to 'active', i.e. if QAM Channel is not present and/or not enabled.

Table of QAM Module Code Download Configuration. There are 2 QRM modules on each 2x4/2x8 QAM Module. QRMs in QAM Module slots are mapped to table rows as follows: Slot/QRM Table Row 1/1 1 1/2 2 2/1 3 2/2 4 3/1 5 3/2 6 4x4 QAM Modules do not use QRM boards. There is only one board. These will be found in the odd indexed rows of this table. The even indexed rows of the table are not used for 4x4 QAM Modules. 4x4 QAM Modules in QAM Module slots are mapped to table rows as follows: Slot Table Row 1 1 2 3 3 5

QAM Code Download Configuration Table Entry.

QAM Code Download Configuration Table index.

User initiated manual 4x4 QAM Module or 2x4/2x8 QAM Module QRM board Code Download request. Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no) Enumeration: 'requestDownload': 1, 'requestNotInProgress': 0.

Table of QAM Module Code Download Status. Refer to apexQrmDownloadConfigTable description for table indexing information.

QRM Code Download Status Table Entry.

QAM Code Download Status Table index.

Text description of the current state of 4x4 QAM Module or 2x4/2x8 QAM Module QRM board Code Download.

Completion percentage of Code Download. '-1' indicates failure.

Indicates if the module HW and SW will support Code Download. 'notSupported' if the module is unsupported or the code download might downgrade the code resident on the module. Refer to apexQamQrmRevisionTable, apexQamQrmRevisionStatusTable, and apexQrmDownloadFileSet for additional status. The user cannot initiate a manual download (apexQrmDownloadConfigRequest) when download 'notSupported'. Enumeration: 'supported': 2, 'notApplicable': 0, 'notSupported': 1.

Indicates if the module requires Code Download. Code download is needed if the versions are not up to date with the resident APEX FW Release. Refer to apexQamQrmRevisionTable, apexQamQrmRevisionStatusTable, and apexQrmDownloadFileSet for additional status. The user can initiate a manual download (apexQrmDownloadConfigRequest) when download 'notRequired'. Enumeration: 'notApplicable': 0, 'required': 2, 'notRequired': 1.

Indicates which file set will be used for this module. Enumeration: 'notApplicable': 0, 'fileSet2': 2, 'fileSet3': 3, 'fileSet1': 1.

Table of revisions of QAM Module files released with the resident APEX FW Release. Refer to identSoftwareVersion in BCS-IDENT-MIB for the release number.

QRM File Revision Table Entry.

QAM file set number.

Revision of the Application firmware file of the 2x4/2x8 QAM Module's QRM board or revision of the Application firmware portion of the 4x4 QAM Module Code File. Hex XXYY where XX is major version and YY is minor version.

Revision of the Calibration data file of the 2x4/2x8 QAM Module's QRM board. Used only for 2x4/2x8 QAM Module QRM board file sets. Hex XXYY where XX is major version and YY is minor version.

Revision of FPGA firmware file of the 2x4/2x8 QAM Module's QRM board or revision of the FPGA1 firmware portion of the 4x4 QAM Module Code File. Hex XXYY where XX is major version and YY is minor version.

Revision of FPGA2 firmware portion of the 4x4 QAM Module Code File. Used only for 4x4 QAM Module file sets. Hex XXYY where XX is major version and YY is minor version.

Date and time the 4x4 QAM Module code file was created. Used only for 4x4 QAM Module file sets. Format: 'MM/DD/YYYY HH:MM' Where HH is a 24 hour clock.

The communication protocol for output streams in Session Control operating mode. This determines the type of protocol the APEX will use to communicate with an Edge Resource Manager/Switch Digital Video Manager. This parameter cannot be changed when there are any active Session Control mappings. All Session Control mappings must be removed prior to changing this protocol. Once written, a save must be performed via the apexSaveConfig parameter and the APEX must be rebooted for the change to take effect. @Config(config=yes, reboot=yes) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini') Enumeration: 'none': 0, 'rtsp': 2, 'rpc': 1, 'mha-ermi': 3.

The Apply for the apexSesContConfTable. This parameter MUST be set to 'apply' in order for any of the data in the apexSesContConfTable to take effect. This parameter MUST be set LAST after all other data in the apexSesContConfTable has been configured. @Config(config=no, reboot=no)

This is the rate to use for comparing input streams. It is either Information rate or Stream rate. This applies to monitoring for Bit Rate alarming and monitoring of Redundant Pairs. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

This object is obsolete. Session Control Redundancy Threshold. This is the percent used to determine Fail Over from Primary to Secondary, and Switch Back from Secondary to Primary. If a value of zero is specified, Fail Over or Switch Back will not occur. Range is 0 to 100%. Primary Fail Over to Secondary: FailOver = (PrimaryRate) < (Threshold * SecondaryRate) The Primary must remain below the threshold for apexGbeConfInRedundMonitorPeriod. Secondary Switch Back to Primary: SwitchBack = (PrimaryRate) >= (Threshold * SecondaryRate) The Primary must remain at or above the threshold for apexGbeConfInRedundMonitorPeriod seconds. The APEX will delay Switch Back an additional apexGbeConfInRedundSwitchTime seconds. Switch Back will not occur when apexGbeConfInRedundAutoSwitchBack is 'disabled'. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

Session Control Pre-Encryption Checking. Indicates if the APEX is to check if the input service is pre-encrypted or clear. Pre-encrypted is determined by examining the input PMT for a CA ECM descriptor (any CA ECM descriptor). If pre-encrypted, setting this flag will cause the APEX to pass through ECM PID for this service. For input services that have a GI CA ECM descriptor, the APEX will also pass through the PIT message (extract and re-insert the PIT). The output PMT for pre-encrypted services will contain a CA ECM descriptor (referencing the ECM PID). When PID Remapping is enabled, pre-encryption for a service is only valid when the input ECM PID is on a different PID than the associated PMT PID. If this flag is set to pre-encryption and the input service is not pre-encrypted, then the setting of this flag has no affect on the output service. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

The redundancy type for output streams in Session Control operating mode. - hotWarm indicates only 1 input stream, primary or secondary, is open at any one time. For multicast streams, primary will be joined initially. The secondary is joined after a failover (the primary will be dropped prior to joining the secondary). - hotHot indicates both the primary and secondary streams are opened at the same time. For multicast streams, both streams are joined immediately. Changes to the redundancy type cannot be made while there are active routes or sessions. All routes and sessions must be deleted prior to changing the redundancy type. Once written, a save must be performed via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini') Enumeration: 'hotHot': 2, 'hotWarm': 1.

Determines how the copy protection settings (CCI, APS, and CIT) within the PRK will be set. All outputs in Session Control (SDV) mode will use this setting for following input DTCP. Disabled - Use ERM Configuration settings if encryption blob provided. Use CTE settings when in CTE encryption mode and no ERM encryption blob provided. Enabled - Follow input DTCP Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

This is a table of Session Control configuration parameters for each output transport stream. This table defines the primary and secondary Gigabit Ethernet interfaces for each output stream in Session Control operating mode. The primary and secondary interfaces cannot be changed for an output stream when there are active Session Control mappings. All Session Control mappings on an output stream must be removed prior to changing the primary or secondary interface settings. Once written, the change to this table will only take immediate effect after apexSesContConfTableApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexSesContConfTableApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

Session Control Configuration Table Entry.

Output transport stream number (index).

The primary Gbe interface for Session Control. Zero indicates not available. This parameter cannot be changed for any output stream if there is at least 1 active session control mapping. Not configurable for RTSP.

The secondary Gbe interface for RPC SDV. Zero indicates not available. This parameter cannot be changed for any output stream if there is at least 1 active session control mapping. Secondary selection is restricted based on Primary as follows: - Primary 1 or 2: Secondary must be 1 or 2 - Primary 3 or 4: Secondary must be 3 or 4 Not configurable for RTSP.

The communication protocol in use for output streams in Session Control operating mode. Enumeration: 'none': 0, 'rtsp': 2, 'rpc': 1, 'mha-ermi': 3.

Indicates which Input Program Number to use for the Data Carousel. The data carousel in SDV mode (RPC or RTSP) is on a fixed PMT PID along with a fixed component PID. In order to maintain these PID values, the APEX will check for a specific input service number defined by this parameter. This service mapping is assumed to be the Data Carousel mapping. The APEX will maintain the PMT PID value along with the component PID value. To facilitate this mapping, the Data Carousel input/output program number is configurable. - Data Carousel Service Number Default: 0xF38F (62351) The PMT PID and component PID will be determined by the APEX by analyzing the PAT and PMT based on the program number configured. A program number of zero (0) indicates that there is no data carousel. Once written, the change to this parameter will take immediate effect. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

Session reporting mode. Indicates what sessions will be reported when the APEX is requested to report sessions to a manager. When 'enabled', the APEX will report all sessions. When 'disabled', the APEX will report only the sessions for the requesting manager. Once written, the change to this parameter will take immediate effect. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

The device name of this APEX. This variable is only used to generate an XML configuration file via the EM. Once written, the change to this parameter will take immediate effect. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

The device type string reported in XML configuration file. This variable is only used to generate an XML configuration file via the EM. Once written, the change to this parameter will take immediate effect. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

The Enet interface that will be used to set the IP address attribute in the generated XML file. This variable is only used to generate an XML configuration file via the EM. Once written, the change to this parameter will only take immediate effect after apexRpcApplyChange is changed to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRpcApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

The number of shell sessions to be created on each channel marked for session control mode. This variable is only used to generate an XML configuration file via the EM. Once written, the change to this parameter will only take immediate effect after apexRpcApplyChange is changed to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRpcApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

When enabled the APEX populates the sessionRate in the QuerySessionInfo Response message with groupRate divided by the number of sessionIds in the group. The value reported makes no distinction between bound and unbound sessions. Once written, the change to this parameter will take immediate effect. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

The Apply for RPC Settings. This applies to apexRpcControlInterface, apexRpcNumShellSessions, apexRpcRfPortServiceGroup. @Config(config=no, reboot=no)

Table of Configuration data for RPC Session RF Ports. This variable is only used to generate an XML configuration file via the EM.

RPC RF Port Configuration Table Entry.

The RF Port number.

The RF Port name. Once written, the change to this parameter will take immediate effect. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

The RF Port service group. Once written, the change to this parameter will only take immediate effect after apexRpcApplyChange is changed to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRpcApplyChange , value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

Table of Configuration data for RPC Session RF Channels. This variable is only used to generate an XML configuration file via the EM. Once written, the change to this parameter will take immediate effect. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

RPC RF Channel Configuration Table Entry.

The RF Channel number.

The name of this RF Channel.

Table of RPC Switched Digital Video Session status. This table contains 1 row up to the maximum number of service mappings supported.

RPC Switched Digital Video Session Status Table Entry.

The RPC Switched Digital Video Session Status table index.

The index into the apexInputTsStatTable.

The Gigabit Ethernet Input Program Number. A value of zero (0) indicates that the input is an SPTS and the first program listed in the input PAT will be mapped by the APEX.

The Gigabit Ethernet IGMP v3 Source IP Address 3. This IP address is currently unsupported by the APEX.

The Output QAM Channel.

The Output Program Number (1 - 65535).

The Expected Program Bandwidth (bps). This is the bandwidth of the program as defined in the service mapping. A value of 0 indicates that the program BW is unknown.

The Type of session (SDV binding or VOD/Broadcast session). 1 = Switched Digital Video (SDV) 2 = VOD or Broadcast Enumeration: 'noSession': 0, 'sdv': 1, 'vodOrBroadcast': 2.

The Session ID Word 1. Session IDs are 10 byte character arrays. Session IDs are be stored as 3 4-byte words (3 ulongs) in this MIB. First 2 Bytes are always 0, next 10 contain the session ID. Session ID is broken up as follows: Word 1: 00:01 = 0x0000 (unused) Word 1: 02:03 = 1st 2 bytes of session ID (1st 2 bytes of MAC address) Word 2: 00:03 = Next 4 bytes (these 4 plus 1st 2 are the MAC address of manager) Word 3: 00:03 = Last 4 bytes (unique number assigned by manager)

The Session ID Word 2. Session IDs are 10 byte character arrays. Session IDs are be stored as 3 4-byte words (3 Unsigned32) in this MIB. First 2 Bytes are always 0, next 10 contain the session ID. Session ID is broken up as follows: Word 1: 00:01 = 0x0000 (unused) Word 1: 02:03 = 1st bytes of session ID (1st 2 bytes of MAC address) Word 2: 00:03 = Next 4 bytes (these 4 plus 1st 2 are the MAC address of manager) Word 3: 00:03 = Last 4 bytes (unique number assigned by manager)

The Session ID Word 3. Session IDs are 10 byte character arrays. Session IDs are be stored as 3 4-byte words (3 Unsigned32) in this MIB. First 2 Bytes are always 0, next 10 contain the session ID. Session ID is broken up as follows: Word 1: 00:01 = 0x0000 (unused) Word 1: 02:03 = 1st bytes of session ID (1st 2 bytes of MAC address) Word 2: 00:03 = Next 4 bytes (these 4 plus 1st 2 are the MAC address of manager) Word 3: 00:03 = Last 4 bytes (unique number assigned by manager)

The IP address of the RPC SDV, VOD, or Broadcast manager sending session commands.

Table of RPC Switched Digital Video QAM status. This table is indexed by output stream number and 48 rows.

RPC Switched Digital Video QAM Status Table Entry.

The RPC Switched Digital Video QAM Status table index.

The Number of reserved SDV sessions on this QAM Channel. This is the number of SDV sessions that have been reserved by the manager. Each SDV session requires that a manager reserve a QAM. This is the count of SDV sessions reserved (not the actual number of active SDV sessions).

The Number of VOD/Broadcast sessions on this QAM Channel. This is the number of VOD/Broadcast sessions active on a QAM Channel. Since VOD and Broadcast sessions are not required to be reserved for an output, this is the count of active VOD and Broadcast sessions on a specific QAM.

The Group BW for SDV sessions (not used for VOD/Broadcast sessions). This is the total amount of BW allocated for all SDV sessions on a channel. The total SDV BW for a channel is defined by the session manager. The manager reserves this BW for future SDV sessions. This is not the BW of current active SDV sessions, but the total BW reserved by the manager for SDV sessions.

This selects which pair of GBE interfaces are to be reported to the RTSP controller (ERM) via VREP. The pairedPortAssignment selection allows for both pairs of GBE interfaces to be reported to the ERM. This allows for all 4 GBE interfaces to be used by the ERM for session mappings. This effectively splits the APEX into 2x24 QAM devices where the first GBE interface pair (1&2) are assigned to the first 24 output QAM streams (output TS 1 - 24) and the second GBE pair (3&4) are assigned to the second 24 output QAM streams (output TS 25-48). Selecting reportGbe1and2 or reportGbe3and4 limits the ERM to 2 GBE interfaces only. Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini') Enumeration: 'reportGbe3and4': 2, 'none': 0, 'reportGbe1and2': 1, 'pairedPortAssignment': 3.

Table of Apply Change for the data for apexRtspConfControllerTable. A row of this table corresponds to a row in apexRtspConfControllerTable.

RTSP Controller Configuration Apply Table Entry.

The RTSP Session Controller number.

The Apply for a row of data in apexRtspConfControllerTable and apexRtspConfControlNamesTable. A row in this table corresponds to the same row index in the apexRtspConfControllerTable and apexRtspConfControlNamesTable. This parameter MUST be set to 'apply' in order for any of the data in the rows to take effect in the APEX. This parameter MUST be set LAST after all other data in the configuration table rows has been configured. @Config(config=no, reboot=no)

Table of RTSP configuration items configurable on a Controller basis. Once written, the change to this table will only take immediate effect after apexRtspConfControllerApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfControllerApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

RTSP Controller Configuration Table Entry.

The Controller Number. APEX currently supports only one controller.

The IP Address of the RTSP session controller.

Port for the RTSP session controller.

The session hold time in seconds. If the APEX does not receive a keep session alive message from the controller in this time the APEX will close the session. The APEX will transmit keep session alive messages at one-third of this time. Zero indicates that the APEX should not send keep session alive messages.

The Bandwidth Delta, in kilobits per second (kbps), for sending an Update Message. Whenever a QAM Channel's output utilization changes by more than the bandwidth delta, the APEX will send a update message providing the current BW being utilized. Zero indicates that the APEX should not send update messages based on bandwidth changes.

Table of RTSP configuration items configurable on a Controller basis. Contains the control names. This table is a row-for-row index match to the apexRtspConfControllerTable. Once written, the change to this table will only take immediate effect after apexRtspConfControllerApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfControllerApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

RTSP Controller Names Configuration Table Entry.

The Controller Number. APEX currently supports only one controller.

The streaming zone that the APEX is a member of.

The device name of this APEX.

Table of Apply Change for the data for apexRtspConfQamChannelTable. A row of this table corresponds to a row in apexRtspConfQamChannelTable.

RTSP QAM Configuration Apply Table Entry.

The QAM Channel number.

The Apply for a row of data in apexRtspConfQamChannelTable. A row in this table corresponds to the same row index in the apexRtspConfQamChannelTable. This parameter MUST be set to 'apply' in order for any of the data in the rows to take effect in the APEX. This parameter MUST be set LAST after all other data in the configuration table rows has been configured. @Config(config=no, reboot=no)

Table of Configuration data for RTSP Session QAM Channels. Once written, the change to this table will only take immediate effect after apexRtspConfQamChannelApplyChange to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfQamChannelApplyChange , value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

RTSP QAM Configuration Table Entry.

The QAM Channel number.

The QAM Group Name that this QAM Channel is a member of.

Table of Configuration data for RTSP Session GigE Interfaces. Once written, the change to this table will take immediate effect. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

RTSP GigE Edge Group Configuration Table Entry.

The GigE Edge Group Interface number.

The Name of this GigE Interface.

Table of MHA RTSP configuration items configurable on a Controller basis. Once written, the change to this table will only take immediate effect after apexRtspConfControllerApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfControllerApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

MHA RTSP Configuration Table Entry.

The MHA Controller Number. APEX currently supports only one controller.

Address Domain of the sender used in ERRP. Address Domain of the ERM and APEX must match in order to establish an ERRP connection. Zero is used as the global address domain, which is interpreted to mean that any advertised address can be reached from any address domain.

Port for the MHA session controller.

Indicates if the UDP Map is populated in the Update message sent by the APEX to the ERM when in MHA mode. When 'enabled', the APEX will report UDP ports available. When 'disabled', the APEX will include the UDP Map field but will not populate it with data. Once written, the change to this table will only take immediate effect after apexRtspConfControllerApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfControllerApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini')

This parameter is used to set the Session based Encryption Mode. It applies to all session based encryption sessions. - 'full' - The APEX will use Full encryption. - 'fwk' - The APEX will use Fixed Working Key (FWK) encryption. - 'fpk' - The APEX will use Fixed Program Key (FPK) encryption. The APEX will not attempt to get EMMs. Once written, the change to this parameter will only take immediate effect after apexRtspConfMhaSbeApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfMhaSbeApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini') Enumeration: 'full': 1, 'fpk': 3, 'fwk': 2.

Copy Control Information (CCI) Level setting for session based PRK messages if CCI is not defined in the XML encryption blob. - notDefined - CCI is not defined, settop box applications can configure CCI - copyFreely - program can be copied - copyOnce - program can be copied once - copyNever - program can never be copied - noMoreCopies - Once written, the change to this parameter will only take immediate effect after apexRtspConfMhaSbeApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfMhaSbeApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini') Enumeration: 'notDefined': 1, 'noMoreCopies': 5, 'copyNever': 4, 'copyOnce': 3, 'copyFreely': 2.

Analog Protection System (APS) Level setting for session based PRK messages if APS is not defined in the XML encryption blob. Defines what copy protection encoding will be applied to the analog composite output by the settop box. - notDefined - analog protection is not defined, settop box applications can configure APS - off - no analog protection - splitBurstOff - AGC on, split burst off - splitBurst2Line - AGC on, 2 line split burst on - splitBurst4Line - AGC on, 4 line split burst on Once written, the change to this parameter will only take immediate effect after apexRtspConfMhaSbeApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfMhaSbeApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini') Enumeration: 'notDefined': 1, 'splitBurstOff': 3, 'splitBurst4Line': 5, 'off': 2, 'splitBurst2Line': 4.

Copy protection Constraint Image Trigger setting. This is only applicable when the session is being encrypted and the CIT setting was not contained in the XML encryption blob. Once written, the change to this parameter will only take immediate effect after apexRtspConfMhaSbeApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexRtspConfMhaSbeApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(sdv.ini, type='ini') Enumeration: 'disabled': 1, 'enabled': 2.

The Apply for the MHA session based encryption settings. This parameter MUST be set to 'apply' in order for any of the data in MHA SBE to take effect in the APEX. This parameter MUST be set LAST after all other data in the MHA SBE has been configured. @Config(config=no, reboot=no)

Table of RTSP Session status. This table contains 768 rows.

RTSP Session Status Table Entry.

The RTSP Session Status table index.

The index into the apexInputTsStatTable.

The Gigabit Ethernet Input Program Number. A value of zero (0) indicates that the input is an SPTS and the first program listed in the input PAT will be mapped by the APEX.

The Output QAM Channel.

The Output Program Number.

The Expected Program Bandwidth (bps). This is the bandwidth of the program as defined in the service mapping. A value of 0 indicates that the program BW is unknown.

The IP address of the manager sending session commands.

Table of RTSP Session Ids. This table contains 768 rows and is a row-for-row index match to apexRtspSessionStatTable.

RTSP Session ID Table Entry.

The RTSP Session ID table index. This is a row-for-row match to the RTSP Session Status table index.

The Session ID.

Table of RTSP Session QAM status. This table is indexed by QAM channel number and contains 48 rows.

RTSP Session QAM status Table Entry.

The RTSP Session Control Video QAM Status table index.

The Number of active sessions on this QAM Channel.

This is the total amount of BW allocated for all sessions on a channel.

Table of RTSP status items configurable on a Controller basis.

RTSP Controller Status Table Entry.

The Controller Number. APEX currently supports only one controller.

Status of Controller to APEX discovery. Enumeration: 'discoveredConnectionLost': 3, 'discovered': 2, 'notApplicable': 0, 'notDiscovered': 1, 'discoveredBnotA': 5, 'discoveredAnotB': 4.

Status of the connection between the APEX and the Controller. 'notConnected' causes apexAlarmRtspControllerCommFault. Enumeration: 'notConnected': 1, 'notApplicable': 0, 'connectedPort554': 3, 'connectedPort2048': 4, 'connected': 2.

Current fault condition of apexRtspStatControllerConnection. This is the apexAlarmRtspControllerCommFault level for this controller. Enumeration: 'major': 5, 'ok': 1, 'indeterminate': 2, 'warning': 3, 'critical': 6, 'minor': 4.

Table of Status data for RTSP Session QAM Channels.

RTSP QAM Configuration Table Entry.

The QAM Channel number.

The Name of this QAM Channel.

Table of MPTS Mode Status data for RTSP Session QAM Channels.

RTSP QAM MPTS Mode Configuration Table Entry.

The QAM Channel number.

The MPTS mode of this QAM Channel. The first session established on the QAM channel defines the MPTS mode. Each new session must have the same mode as long as one session is still active. Enumeration: 'multiplexing': 2, 'notApplicable': 0, 'passthrough': 1.

Clear all RMD information from DRAM and flash. Note that apexManualRouteEnable must be set to disabled for all rows before RMD information will be cleared by this parameter. If RMD information was cleared, the APEX will set this parameter to applyNotInProgressValidData. If RMD information was not cleared, the APEX will set this parameter to applyNotInProgressInvalidData. Once written, the change to this parameter will take effect immediately. @Config(config=no, reboot=no)

Table of Apply Change for the data for Manual Route Table. A row in this table corresponds to the same row index in the Manual Route table.

Manual Route Apply Table Entry.

The index of the Manual Route Apply Table.

The Apply for the row of data in the Manual Route Table. A row in this table corresponds to the same row index in the Manual Route table. This parameter MUST be set to 'apply' in order for any of the data in the Manual Route Table row to take effect in the APEX. This parameter MUST be set LAST after all other data in the Manual Route Table row has been configured. @Config(config=no, reboot=no)

Table of data for Manual Routes. Once written, the change to a row this table will only take immediate effect after the appropriate apexManualRouteApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexManualRouteApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(bcmr.ini, type='ini')

Manual Route Table Entry.

The index of the Manual Route Table.

Indicates that this Manual Route is enabled or disabled.

Input Type of input from which to obtain data. Enumeration: 'gbe': 1, 'fastEnet': 2.

Number of the input interface, of type configured by Input Type, from which to obtain data. Range: '0' = Not Applicable GBE = 1-4 FastEnet = 1-2

Input UDP Port from which to obtain data. Range: GBE = 0-65535 FastEnet = 1024-65535

Input Multicast IP address from which to obtain data. An IP address of 0.0.0.0 indicates table entry not in use. Multicast IP addresses 224.0.0.0 to 224.0.0.255 are reserved.

Input IGMP v3 Source IP from which to obtain data. If the router supports IGMP v3 the GBE will only receive data from this source IP. If Source IP is not specified or the router does not support IGMP v3 the GBE will receive data from any source device. Source IP address must be a valid singlecast address.

Input MPEG Program Number to multiplex. A value of 0 can be used as a wild card. This will cause the APEX to map the first program listed in the input PAT to the specified output (regardless of input program number). Input program number zero should only be used when mapping Single Program Transport Streams (SPTS).

Manual Routing Pre-Encryption Checking. Indicates if the APEX is to check if the input service is pre-encrypted or clear. Pre-encrypted is determined by examining the input PMT for a CA ECM descriptor (any CA ECM descriptor). If pre-encrypted, setting this flag will cause the APEX to pass through ECM PID for this service. For input services that have a GI CA ECM descriptor, the APEX will also pass through the PIT message (extract and re-insert the PIT). The output PMT for pre-encrypted services will contain a CA ECM descriptor (referencing the ECM PID). When PID Remapping is enabled, pre-encryption for a service is only valid when the input ECM PID is on a different PID than the associated PMT PID. If this flag is set to pre-encryption and the input service is not pre-encrypted, then the setting of this flag has no affect on the output service.

Output Transport Stream Number of the output on which to place data. Zero = NotApplicable and is only valid if the apexManualRouteTable entry is not being used.

Output Program number to use for the program. Zero = NotApplicable and is only valid if the apexManualRouteTable entry is not being used.

Encryption Mode. Not supported. Enumeration: 'clear': 1.

Copy Protection Source. Not supported. Enumeration: 'configuredSource': 2, 'followInputDtcp': 1.

Broadcast Encryption Source ID. Only applies to programs if the input type is Gbe and the output encryption mode is Broadcast Encryption. (apexOutputTsConfEncryptionType set to 'broadcastEncryption')

Broadcast Encryption Provider ID. Only applies to programs if the input type is Gbe and the output encryption mode is Broadcast Encryption. (apexOutputTsConfEncryptionType set to 'broadcastEncryption')

Table of Apply Change for the data for Manual Route Pass Through Table. A row in this table corresponds to the same row index in the Manual Route Pass Through table.

Manual Route Apply Table Entry.

The index of the Manual Route Pass Through Apply Table.

The Apply for the row of data in the Manual Route Pass Through Table. A row in this table corresponds to the same row index in the Manual Route Pass Through table. This parameter MUST be set to 'apply' in order for any of the data in the Manual Route Pass Through Table row to take effect in the APEX. This parameter MUST be set LAST after all other data in the Manual Route Pass Through Table row has been configured. @Config(config=no, reboot=no)

Table of data for Manual Route Pass Through. This table is used to pass through an entire input stream to an output stream. Once written, the change to a row this table will only take immediate effect after the appropriate apexManRtePassThroughApplyChange is set to 'apply'. In order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Commit(param=apexManRtePassThroughApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(bcmr.ini, type='ini')

Manual Route Pass Through Table Entry.

The index of the Manual Route Pass Through Table.

Indicates that this Manual Route Pass Through is enabled or disabled. An input stream can only be passed through to an output stream when there are no active service or PID mappings to the output stream.

Input Type of input from which to obtain data. Enumeration: 'gbe': 1, 'fastEnet': 2.

Number of the input interface, of type configured by Input Type, from which to obtain data. Range: '0' = Not Applicable GBE = 1-4 FastEnet = 1-2

Input UDP Port from which to obtain data. Range: GBE = 0-65535 FastEnet = 1024-65535

Input Multicast IP address from which to obtain data. An IP address of 0.0.0.0 indicates table entry not in use. Multicast IP addresses 224.0.0.0 to 224.0.0.255 are reserved.

Input IGMP v3 Source IP address from which to obtain data. If the router supports IGMP v3 the GBE will only receive data from this source IP. If Source IP is not specified or the router does not support IGMP v3 the GBE will receive data from any source device. Source IP address must be a valid singlecast address.

Table of Apply Change for the data for Manual Route Table. A row in this table corresponds to the same row index in the Manual Route table.

Manual Routing Gbe Input Ts Configuration Apply Table Entry.

The index of the Manual Routing Gbe Input Ts Configuration Apply Table.

The Apply for the row of data in the Manual Routing Gbe Input Ts Configuration Table. A row in this table corresponds to the same row index in the Manual Routing Gbe Input Ts Configuration table. This parameter MUST be set to 'apply' in order for any of the data in the Manual Routing Gbe Input Ts Configuration Table row to take effect in the APEX. This parameter MUST be set LAST after all other data in the Manual Routing Gbe Input Ts Configuration Table row has been configured. @Config(config=no, reboot=no)

This table is the Manual Routing Gigabit Ethernet Input Transport Stream Configuration Table. This table contains 768 rows. For Force Switching a Redundancy pair for an Input TS configured in this table, refer to the same row index in apexManRteGbeInRedForceSwitchTable. Once written, the change to this table will only take immediate effect after apexManRteGbeInRedApplyChange is set to 'apply'. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Commit(param=apexManRteGbeInRedApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(gige_red.ini, type='ini')

Manual Routing Gigabit Ethernet Input Transport Stream Configuration Table Entry.

The Manual Routing Gbe Input Ts Configuration table index.

The primary Gigabit Ethernet Interface. Zero indicates this row of the table is not in use.

The primary Gigabit Ethernet Input UDP Port.

The primary Multicast receive IP address. An IP address of 0.0.0.0 indicates table entry not in use. Multicast IP addresses 224.0.0.0 to 224.0.0.255 are reserved.

This is the IP address of the source device for the primary interface. If the router supports IGMP v3 the GBE will only receive data from this source IP. If Source IP is not specified or the router does not support IGMP v3 the GBE will receive data from any source device. Source IP address must be a valid singlecast address.

This is the bit rate, in bits per second, below which the APEX will issue the apexAlarmGbeInputStreamLowBitRate alarm for the primary interface. The APEX will compare either the current Information rate or Stream rate as configured in apexManRteGbeInRedRateCompareType. Setting to zero disables the bit rate alarming. The APEX updates the bit rate statistics every five seconds.

This is the bit rate, in bits per second, above which the APEX will issue the apexAlarmGbeInputStreamHighBitRate alarm for the primary interface. The APEX will compare either the current Information rate or Stream rate as configured in apexManRteGbeInRedRateCompareType. Setting to zero disables the bit rate alarming. The APEX updates the bit rate statistics every five seconds. Not supported.

This is the rate to use for comparing input streams. It is either Information rate or Stream rate. This applies to monitoring for Bit Rate alarming and monitoring of Redundant Pairs.

This entry is used to enable Redundancy.

Manual Routing Gigabit Ethernet Redundancy Threshold. This is the percent used to determine Fail Over from Primary to Secondary, and Switch Back from Secondary to Primary. If a value of zero is specified, Fail Over or Switch Back will not occur. Range is 0 to 100%. Primary Fail Over to Secondary: FailOver = (PrimaryRate) < (Threshold * SecondaryRate) The Primary must remain below the threshold for apexGbeConfInRedundMonitorPeriod. Fail Over will not occur when apexManRteGbeInRedSuspend is set to 'suspended'. Secondary Switch Back to Primary: SwitchBack = (PrimaryRate) >= (Threshold * SecondaryRate) The Primary must remain at or above the threshold for apexGbeConfInRedundMonitorPeriod seconds. The APEX will delay Switch Back an additional apexGbeConfInRedundSwitchTime seconds. Switch Back will not occur when apexManRteGbeInRedSuspend is set to 'suspended' or apexGbeConfInRedundAutoSwitchBack is 'disabled'.

This suspends Redundant Pair switching when set to 'suspended'. This has no effect when redundancy is disabled. Forced switching of Redundant Pairs is not prevented when this is set to 'suspended'. Enumeration: 'suspended': 2, 'notSuspended': 1.

The secondary Gigabit Ethernet Interface for redundancy. Zero is invalid when redundancy is enabled.

The secondary Gigabit Ethernet Input UDP Port for redundancy.

The secondary Multicast receive IP address for redundancy. An IP address of 0.0.0.0 indicates singlecast only. Multicast IP addresses 224.0.0.0 to 224.0.0.255 are reserved.

This is the IP address of the source device for the secondary interface. If the router supports IGMP v3 the GBE will only receive data from this source IP. If Source IP is not specified or the router does not support IGMP v3 the GBE will receive data from any source device. Source IP address must be a valid singlecast address.

This is the bit rate, in bits per second, below which the APEX will issue the apexAlarmGbeInputStreamLowBitRate alarm for the secondary interface. The APEX will compare either the current Information rate or Stream rate as configured in apexManRteGbeInRedRateCompareType. Setting to zero disables the bit rate alarming. The APEX updates the bit rate statistics every five seconds.

This is the bit rate, in bits per second, above which the APEX will issue the apexAlarmGbeInputStreamHighBitRate alarm for the secondary interface. The APEX will compare either the current Information rate or Stream rate as configured in apexManRteGbeInRedRateCompareType. Setting to zero disables the bit rate alarming. The APEX updates the bit rate statistics every five seconds. Not supported.

This is not currently supported and is reserved for future use. Enumeration: 'noJoinOnOpen': 1, 'joinOnOpen': 2.

This table is the Manual Routing Gigabit Ethernet Input Transport Stream Redundancy Configuration Table. This table contains 768 rows. A row in this table corresponds to the same index in the apexManRteGbeInRedTable.

Gigabit Ethernet Input Stream Redundancy Configuration Table Entry.

The Manual Routing Gbe Input Ts Redundancy Configuration table index. A row in this table corresponds to the same index in the apexManRteGbeInRedTable.

The Gigabit Ethernet Redundant Pair force switch. This will have no effect if the corresponding row setting of apexManRteGbeInRedEnable is 'disabled'. The corresponding row setting apexManRteGbeInRedSuspend is ignored when 'forceSwitch' is set. The switch will occur even if apexManRteGbeInRedSuspend is 'suspended'. When forced to the Secondary of the pair, the APEX will stay on the Secondary until the user forces back to the Primary. The APEX will not automatically switch back to the Primary when the Primary is restored above the failover threshold. The APEX will not allow a force to the Primary unless the Primary is above the failover threshold. Once written, the change to this parameter will take immediate effect. @Config(config=no, reboot=no) Enumeration: 'switchNotInProgress': 1, 'forceSwitch': 2.

When apexManualRouteApplyChange is set to applyNotInProgressInvalidData this entry may contain a text description of what was wrong with the data. This entry contains the description for the most recent apply of a table entry that was invalid.

When apexManRtePassThroughApplyChange is set to applyNotInProgressInvalidData this entry may contain a text description of what was wrong with the data. This entry contains the description for the most recent apply of a table entry that was invalid.

When apexManRteGbeInRedTableApplyChange is set to applyNotInProgressInvalidData this entry may contain a text description of what was wrong with the data. This entry contains the description for the most recent apply of a table entry that was invalid.

This table provides the mapping between the indexes in Manual Routing Gigabit Ethernet Input Transport Stream Redundancy Configuration and Input TS Status. This table contains 768 rows. The index in this table corresponds to the same index in the apexManRteGbeInRedTable.

Gigabit Ethernet Input Stream Redundancy Configuration and Status Mapping Table Entry.

The Manual Routing Gbe Input Ts Redundancy Configuration and status mapping table index. A index in this table corresponds to the same index in the apexManRteGbeInRedTable.

The Manual Routing Gbe Input TS Status index. This provides the mapping between the entries in apexManRteGbeInRedTable and apexInputTsStatTable. The range of the index is 0 - 784, where 0 indicates no direct association between configuration and status and the 1-784 is the actual Input Stream status row (relative 1). @Config(config=no, reboot=no)

Table of data for Ancillary Pid Mapping. There are 480 rows in this table (APEX supports up to 480 ancillary PID mappings). Once written, the change to this table will only take immediate effect after apexPidMapApplyChange is set to 'apply'. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via apexSaveConfig. @Config(config=yes, reboot=no) @Commit(param=apexPidMapApplyChange, value=2) @Save(apexSaveConfig, value=2) @File(bcmr.ini, type='ini')

Pid Mapping Table Entry.

Index of Pid Mapping Table.

Indicates whether this PID Mapping is enabled or disabled.

Input Type of input from which to obtain data. Enumeration: 'gbe': 1, 'fastEnet': 2.

Number of the input, of type configured by Input Type, from which to obtain data. Range: '0' = Not Applicable GBE = 1-4 FastEnet = 1-2

Input UDP Port from which to obtain data. Range: GBE = 0-65535 FastEnet = 1024-65535

The Multicast receive IP address on which to receive data. An IP address of 0.0.0.0 indicates singlecast only. Multicast IP addresses 224.0.0.0 to 224.0.0.255 are reserved.

This is the IP address of the source device. If the router supports IGMP v3 the GBE will only receive data from this source IP. If Source IP is not specified or the router does not support IGMP v3 the GBE will receive data from any source device. Source IP address must be a valid singlecast address.

Input MPEG PID to multiplex. When PID Remapping for an output is enabled, the input PID value and output PID value can be different. When PID Remapping for an output is disabled, the input and output PIDs must be the same. Input PID 0 (PAT PID) cannot be mapped by the user.

Output Transport Stream Number of the output on which to place data. Zero is only valid if the apexPidMapTable entry is not being used.

Output PID to use for the data. This output PID value must match the input PID value when PID Remapping for the output stream is disabled. Zero is only valid if the apexPidMapTable entry is not being used.

Table of Apply Change for the data for PID Map Table. A row in this table corresponds to the same row index in the PID Map table.

PID Map Apply Table Entry.

The index of the PID Map Apply Table.

The Apply for the row of data in the PID Map Table. A row in this table corresponds to the same row index in the PID Map table. This parameter MUST be set to 'apply' in order for any of the data in the PID Map Table row to take effect in the APEX. This parameter MUST be set LAST after all other data in the PID Map Table row has been configured. @Config(config=no, reboot=no)

Maximum number of Ancillary PID mappings supported.

When apexPidMapApplyChange is set to applyNotInProgressInvalidData this entry may contain a text description of what was wrong with the data. This entry contains the description for the most recent apply of a table entry that was invalid.

This parameter is used to set the insertion mode for the APEX. The APEX may be configured to insert messages as efficiently as possible (efficient) or restrict insertion to a single section starting per packet (singleSection). Once written, the change to this parameter will take immediate effect. However, in order for the change to persist through subsequent reboots or power cycles, the change must be saved via the apexSaveConfig parameter. @Config(config=yes, reboot=no) @Save(apexSaveConfig, value=2) @File(config.ini, type='ini') Enumeration: 'efficient': 1, 'singleSection': 2.

Table of Output Transport Stream Insert Packet Statistics. Indexed by Output Transport Stream number.