This documents describes an issue of SDVs getting black screen because of difference of bandwidth between VSRM and RFGW10 (SQB1) release. This difference was caused mainly due to some bandwidth getting reserved without having a video session on it.
Problem Description & Troubleshooting:
End user STB is seeing black screens on all SDV channels Many Service Groups were affected Debugs on VSRM show RmCmdFail, RmBwReqResSelectFail, RmResourceFail which means blocking events and no bandwidth available Debugs on RFGW show 'rfgw_gqi_session_create -> Tx [-805306363]: Unable to create Video Session [INSUFFICIENT QAM BANDWIDTH]' It was found that there is a difference in actual bandwidth on the RFGW and stated bandwidth on the VSRM Linecard switch over was performed to rule out issues with the card giving the wrong computations, but it did not resolve the issue. It found that QAM consumed reserved BW value of 3.75Mbps without having any video session on it
Qam-red 8/7.27 Downstream is down
RF Profile is not assigned
LQAM Group is not assigned
Annex B, Power: 35.0 dBmV
Frequency: 0 Hz , lane: -1, block: -1
Modulation: 256QAM, TSID: 0, QAM IDB_State: UP
Bandwidth Reserved for Video: 3750000 bps
Bandwidth Used: 0 bps
Bandwidth Total: 38810700 bps
Transport Mode: QAM_MODE_OFF Qam Owner: NONE
Qam License: Exists
Interleave Level: 2, FEC I: 32 FEC J: 4
SNMP LINK TRAP: Disabled
BW denial during session creation for the QAM might result in Video blackout as the session is not established in RFGW10 Removing QAM from QP did not help to resolve the issue Defaulting QAM configuration did not release the QAM reserved BW in RFGW10
Workaround: Below are the steps provided as a work around for time being:
Reload the peer SUP (redundancy reload peer), to remove the QAM stale BW entry in the standby SUP Do SUP switchover (redundancy force-switchover), to recover the system
It is found to be a BUG and solution will be available in SQD Release.
... View more
Introduction: This document describes the procedure to configure PID Reservation, Program Remap, PID and Program Filtering using the RFGW10 GUI in SQC release. Configuring the PID Reservation: PID reservation is a feature to ensure that the remapped sessions does not use PIDs in the reserved PID range. There are some limitations to PID reservations like minimum 2048 PID should be left unreserved, a maximum of 2 ranges can be configured, PIDs should lie in the range 256 to 8175 and PID range overlap is not allowed. To Configure Go to Video -> Video Reserved-PID To reserve the PIDs Enter Minimum and Maximum PID ranges and click on apply. Configuring and Verifying the MPTS RemapSession: MPTS Remap is a feature by which an output program number can be assigned to a program in the local unicast/multicast input MPTS stream to setup a remapped MPTS session. All the programs for which an output program number is not explicitly mentioned will be dropped at the input. Using this feature at the QAM sub interface mode a maximum of 64 input programs from a local unicast/multicast MPTS can be remapped to different output program numbers. To Configure the Remap Sessions, we need to go to Video-> Local Session -> Line card on which the remap session to be configured in this example DS384 3-> RF Port -> QAM Channel. In below example we are configuring MPTS Remap Session and we are mapping only 3 Programs. Step 1: Configure the Sessions per channel. Maximum 1 session per channel can be configured. Step 2: Select the input type to be Multicast and then select the multicast labels. Here we are selecting ssmmpts2. Step 3: Select the start value for I/P and O/P Program Number and also the increment value of I/P and O/P Program Number. In this example, we have selected the Start value for I/P program number is 2 and O/P program number is 3. Increment value selected 1 for I/P and O/P. In the below example I/P Program number 2 and 3 are showing red because O/P program number 3 and 4 are already in use. So we change the O/P program numbers to 8, 6 and 7 and click on apply. Step 4: To verify the remapped session go to Local Session and select the Line Card and click on details and then click on the particular Session ID. We can see that input side we had 4 Programs 2,3,4 and 5. But on the output we have only 8,6 and 7 because we had selected to remap only 3 programs. Configuring and Verifying PID and Program Filtering: PID Filtering feature allows the user to filter the well known PIDs in the local unicast/multicast passthrough session. Filtering happens on at the output, this ensures that user can filter different PIDs on different cloned sessions. Program filtering feature when used at the QAM sub interface mode allows the user to filter programs from the local unicast/multicast passthrough session. Filtering happens at the output, this ensures that user can filter different programs on different cloned sessions. While dropping a program all the PIDs associated with that program are dropped. To configure PID and Program Filtering go to that particular QAM channel in Filtering. In the below example we see that Program Filter is grayed out because for remapped session program filtering is not possible. Program filtering can be done only in Pass Thru sessions. Here we will select session ID 201394993 for our configuration example. Step 1: Let's check which PIDs are available for session id 201394993. Step 2: Filtering the PID in PID filter box. Let’s try to filter PID 129. Make the entry 129 in PID filter box of session id 201394993 and click on apply. Step 3: To verify, click on the session id and look in to output Session Information. We can see that PID Filter has Value 129. In the same way, we can do Program Filtering. Below is configuration example of PID and Program Filtering.
... View more