Cisco Rfgw1d Manual
Have a look at the manual Cisco Rfgw1d Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 53 Cisco manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
78-4025112-01 Rev H0 237 This chapter provides information for provisioning the RF Gateway 1 for NGOD operation. The reader is assumed to have knowledge of the NGOD protocol. 16 Chapter 16 NGOD Specific Operation In This Chapter Provisioning ......................................................................................... 238 Status Monitoring ............................................................................... 241 Troubleshooting .................................................................................. 242 Logs ....................................................................................................... 243
Chapter 16 NGOD Specific Operation 238 78-4025112-01 Rev H0 Provisioning This section provides information for provisioning the RF Gateway 1 for NGOD operation. Prerequisite configurations: GbE input ports, including Video/Data IP address QAM outputs Channel Application Mode Channel Application Mode To Verify Channel Application Mode Navigate to the Qams page. 1 Select the QAM channels and set the App Mode to NGOD. 2 Set the TSID appropriately Result: App Mode is displayed for each output carrier. NGOD Settings Navigate to the System tab and from there to the NGOD configuration on the left hand side of the tab. RFGW-1 is Configured with the following NGOD Settings VREP Version – This should be set to 2. Region Name – This is the Region Name that this RFGW-1 belongs to. Local Name – This is the local name of the RFGW-1. When the region and local name is appended together, this identifies the RFGW-1 location.
Provisioning 78-4025112-01 Rev H0 239 Component Name Local – Region Name and Local NameComponent Name – The Name of the RFGW-1 QAM RF Port 1-12 names - These are used to advertise the QAM Ports to the ERM Names of the GigE ports Bw Interval and Bw Threshold The RFGW-1 checks every QAM to see if during a Bw Interval, there was a change in the bandwidth that is equal to or greater than the Threshold. This is used by the ERM to maintain Bandwidth. To disable the reporting, one should set the Bw Interval to 0. D6/R6 Communication Provide the information of the ERM and the ports that they are listening on 1 Navigate to the System Tab. 2 Select D6/R6 Comm. Config under the NGOD configuration menu. 3 Setup ERM IPAddress, Port, Timeouts, R6 Listening Port etc. a IP Address and Port – ERM IP Address and Port. Up to 4 different ERMs can be configured with one RFGW-1 b Connection Timeout – Time out in secs to accommodate network delays c Hold Time out – Keep Alive messages are sent 3 times during a Hold time and no faster than once every 3 seconds d BEGIN and END RF ports – These are the port numbers/QAM channels that the ERM can configure e State – Read only Field – Provides the current state information of the RFGW- 1 f Listening Port – R6 Listening Port. This is the port where the RFGW is listening for R6 messages.
Chapter 16 NGOD Specific Operation 240 78-4025112-01 Rev H0 g Connection Time out – This is how long the RFGW-1 waits for an R6 message before resetting the connection. h Session Time out – This is how long a session is kept alive by the RFGW-1 without receiving a R6 session refresh (Ping) from the ERM i Announce Time out – This is how long the RFGW-1 waits before resending an Announce Message.
Status Monitoring 78-4025112-01 Rev H0 241 Status Monitoring Status monitoring of the R6/D6 messages between the ERM and the RFGW-1 is shown on the Monitor tab of the RFGW. The types of messages and the protocol are shown in the tab. The IP Address in the first column is the address of the ERM and the number with a dash represents the time the connection has been on. For e.g. in the figure below 10.90.146.108 ERM has been in the connected state for the last 4555 minutes. NGOD LOG Messages Under the System tab, System Configuration menu and Log submenu, Logs Configuration can be set. NGOD Manager logs can be set to different levels. When selecting the Logs submenu, you can see the logs from the NGOD module. The logs can be used to troubleshoot NGOD issues.
Chapter 16 NGOD Specific Operation 242 78-4025112-01 Rev H0 Troubleshooting RFGW-1 QAMs are not recognized by the ERM. Check the “State” on the D6/R6 comm. Config page. If it is in StartUp/Establish connection state for more than a few minutes, the RFGW-1 is unable to communicate with the ERM. Check the TCP connections between the RFGW-1 and the ERM. Check if the Streaming Zone (RegionName.LocalName) is correct. Ensure that the ERM is configured in the same Streaming Zone as the RFGW-1. Make sure that QAMs on the RFGW-1 are configured for NGOD and are enabled If the RFGW-1 “State” is in Send Periodic Keep Alives then its connected to the ERM and ready If it still does not recognize the QAMs, check the RFGW-1 logs. RFGW-1 QAMs are recognized by the ERM but no sessions are created Check R6 Connection is established at the ERM if there is a provision to do so. Check the R6 Listening port and make sure the ERM is requesting a connection on that port. Check RFGW-1 logs for any errors during R6 communication.
Logs 78-4025112-01 Rev H0 243 Logs NGOD System logs allow the operator to determine the correct behavior of the RFGW-1. Following is the list of some of the important logs. R6[] Session creation failed: Bad id format: Session creation from the USRM failed due to bad id provided by the USRM during session creation R6[] Session creation failed: Bad destipaddr Output: ProgNo.: DestIp: for ERM: Destination IPAddress used to create the session by the USRM is invalid causing the Session Creation to fail. R6[] Session creation failed: Could not add session Output: : ProgNo.: for ERM: Generic session creation failed message R6[] Session creation failed, TSId not found: Output: TsId: ERM: TSID specified by the USRM to create a session was invalid. R6[] CreateSession Invalid number of multicast addresses More than two multicast sources were specified during session creation R6[] CreateSession Invalid dest multicast address. Can not have different dest for multiple mc address. MC Count: Dest multicast addresses were different for each of the multicasts specified. R6[]: - Send Failed. Length: ReturnVal: Error: Generic TCP send to the USRM failed. Typically occurs if the network connection is down. R6[]: Teardown failed. Sess not found. Sess: SessId: IP: Teardown was requested for a session that does not exist. R6 Opened a new connection for ERM: [] A new connection the Resource Manager was made. R6MsgRecv[]: %s - Unknown Message ==>
Chapter 16 NGOD Specific Operation 244 78-4025112-01 Rev H0 Received> An unknown message was received from the USRM R6[]: - Connection Timed out. Now: LastMsgTime: Timeout: No messages were received for a period of time. Last message time received is mentioned in the log. Connection time out is also shown in the log. R6[] Closing connection for ERM:< IP Address of USRM> There are 4 worker threads processing the ERM connections for a max of 4 different ERMs. This message indicates that a connection is being closed. Once a worker thread has closed the connection, the worker thread will become available for a new connection. R6 GenIPSrvr:Got a new Accept: from A new connection was accepted. R6[] No worker available All the 4 worker threads are in use and there are no working threads available to process the connection from the USRM. NGOD session timeout reached for sessionID = Session Timeout on the session is reached and the session is closed. D6State[]: ESTABLISH IP: SZ: D6 connection is established. ERM instance number, there are 4 of them. D6State[]: RECVOPEN IP: Waiting for receiving an OPEN message from the ERM D6State[]: SENDFIRSTKEEPALIVE IP: Starting to send the First Keep Alive message. D6State[]: RECVFIRSTKEEPALIVE IP: Sent the first Keep Alive message, waiting to receive the First Keep Alive message D6State[]: INITUPDATE IP: First update message is being sent to the ERM D6State[]: ERRORNOTIFICATION IP: There was an error during the message exchange with the ERM
Logs 78-4025112-01 Rev H0 245 D6[]: Error (sent != tx bytes) errno: TCP IP connection failure would cause the sent bytes to not match what was intended to be transmitted. D6[]: Error receiving errno: Error while receiving the data from the ERM. D6 Error[]: SendOpen Failed This means that the RFGW failed to send the OPEN message to the ERM D6 Error[]: ReceiveOpen Failed RFGW did not receive an OPEN message from the ERM D6 Error[]: Waiting for ReceiveOpen timedout. Hold time expired. Receive open was not received from the ERM. Hold timer expired. D6 Error[]: ReceiveOpen parsing open message Failed Parsing the OPEN message that was received from the server failed. D6 Error[]: SendKeepAlive Failed Sending Keep Alive message failed. D6 Error[]: ReceiveKeepAlive -- Error receiving message Error while receiving the Keep Alive message from the ERM D6 Error[]: ReceiveKeepAlive -- Nothing received While waiting for a Keep Alive nothing was received. D6 Error[]: ReceiveKeepAlive -- HoldTime Expired While waiting for a Keep Alive Hold timer expired. D6 Error[]: SendInitialUpdate -- Send failed Sending initial update failed D6 QAMUPDATE[]: ADD QAM: Freq: Mod TSID Adding QAMs to the ERM. D6[] QAMUPDATE: WITHDRAW QAM: TSID Removing QAMs from the ERM D6Update[]: BW Update ERROR Qam:
Chapter 16 NGOD Specific Operation 246 78-4025112-01 Rev H0 BW updates are sent periodically to the ERM if enabled. This message indicates that there was an error while sending these messages. D6[]: ERROR no keepAlives () seen, now holdTime ()