Cisco Rfgw1d Manual

							 
 
 Release Management 
 
78-4025112-01 Rev H0 77 
 
Release Management 
Software and firmware upgrades to the RF Gateway 1 are controlled via system 
release.  Using the System/Release Management web page, the operator can 
provision the RF Gateway 1 to perform system release upgrades via FTP from a 
release directory on an upgrade server. 
Each unique system release directory on the upgrade server contains the necessary 
software and firmware components to upgrade an RF Gateway 1 device from any 
previous revision. 
The components of a system release include: 
 application software image 
 programmable firmware images 
 boot code 
 system release file (.xml) 
The FTP server should be on a network that is accessible from the management port 
of the RF Gateway 1.  When a software download is initiated, the RF Gateway 1 
retrieves the system release file which contains the file names of the software and 
firmware components of the system release.  The RF Gateway 1 then determines 
which files of the system release differ from those already resident on its flash file 
system.  If file names do not match, they are automatically FTPed from the upgrade 
server. 
A system release may include changes to any or all of the software or firmware 
components.  As a result, the software application image may change for a new 
release and a firmware image may not.  Likewise, a firmware image may change and 
the application image may not.  The RF Gateway 1 retrieves the software and 
firmware images that changed since the last system release upgrade.  
						

							 
Chapter 3    General Configuration and Monitoring  
 
 
78 78-4025112-01 Rev H0 
  
Downloading System Release Images 
To Download Images 
1 Navigate to the System/Release Management page. 
Result: The following screen is displayed. 
 
2 Click Show FTP Settings at the bottom of the window. 
Result: The FTP window is displayed. 
 
 
3 Enter the upgrade server’s IP address. 
4 Enter the FTP username. 
5 Enter the FTP password. 
6 Click Apply.   
Result: The FTP Settings Applied Successfully pop-up appears. 
7 Click OK to continue. 
8 Click Test FTP Connection.  Verify your connection with the FTP Login Success 
pop-up. 
Note: If a failure occurs while verifying FTP connection, recheck your upgrade 
server IP address, username and password. 
9 Click Save. 
Note: Changes will be lost if not saved. 
10 Locate the Release File Path field and enter the full path to the upgrade directory. 
Example: /SW_Releases/RevA/V01.02.00 
11 Enter the Release File name. 
Example: rfgw1_rel_06_01_02.xml  
						

							 
 
 Release Management 
 
78-4025112-01 Rev H0 79 
 
12 Click the Download Release button to initiate download process.   
Result: The RF Gateway 1 will FTP all necessary files (application & firmware) 
from the upgrade server as dictated in the system release file. 
Note: If download failure occurs, recheck the path and filename of the system 
release file. 
13 After the download process completes successfully, select Activate.   
Result: The device automatically reboots to the new release. 
14 Close the browser after the device begins rebooting. 
A single previous system release is retained by the system after an upgrade.  Once 
the system release upgrade is activated from the GUI, the previously active system 
release is retained as inactive. If the operator wishes to restore the inactive release at 
a later time, a revert capability is available using the System/Release Management 
web view.   
						

							 
Chapter 3    General Configuration and Monitoring  
 
 
80 78-4025112-01 Rev H0 
Configuring, Monitoring, and Fault Management 
via SNMP 
The RFGW-1 supports a set of proprietary and standard MIBs via SNMPv2. Through 
SNMP, the RFGW-1 can be configured and monitored. In addition, Fault 
Management is supported through the generation of SNMP traps for all system 
alarms and events.   
The following table shows the MIBs supported.  
MIB Name Description 
CISCO-RFGW-1-MIB (proprietary) This MIB module contains objects necessary for 
management of the RFGW-1 device. This includes status, 
statistics, equipment inventory, remote 
download/upload, table definition, and other 
configurations as needed for the QAM. 
CISCO-RFGW-1-TRAP-MIB.mib 
(proprietary) 
Trap control MIB for the RFGW-1. 
DOCS-IF-MIB  This is the MIB Module for DOCSIS 2.0 compliant Radio 
Frequency (RF) interfaces in Cable Modems (CM) and 
Cable Modem Termination Systems (CMTS). 
ENTITY-MIB  The MIB module for representing multiple logical 
entities supported by a single SNMP agent. 
SNMPv2-MIB  The MIB module for SNMP entities. 
IF-MIB  The MIB module to describe generic objects for network 
interface sub-layers.  This MIB is an updated version of 
MIB-IIs ifTable, and incorporates the extensions defined 
in RFC 1229.  
						

							 
 
 Configuring, Monitoring, and Fault Management via SNMP 
 
78-4025112-01 Rev H0 81 
 
 
Monitoring Capability 
The RFGW-1 can be monitored to evaluate network and other operational statistics 
by utilizing any MIB browser or other tool (for example, snmpget, snmpwalk) that 
collects SNMP information. Output bandwidth statistics can be retrieved using the 
CISCO-RFGW-1-MIB. See the following screen. 
  
						

							 
Chapter 3    General Configuration and Monitoring  
 
 
82 78-4025112-01 Rev H0 
Input Statistics can be accessed using the IF-MIB. See the following screen. 
 
  
						

							 
 
78-4025112-01 Rev H0 83 
 
This chapter provides information for provisioning the RF Gateway 1 
for table-based video operation.  
 
 
4 Chapter 4 
Table-Based Video Specific 
Operation 
In This Chapter 
 Provisioning ........................................................................................... 84 
 Status Monitoring ................................................................................. 97  
						

							 
Chapter 4    Table-Based Video Specific Operation  
 
 
84 78-4025112-01 Rev H0 
Provisioning 
The following sections provide information for provisioning the RF Gateway 1 for 
table-based video operation. 
Prerequisite Configurations:  
 GbE input ports, including Video/Data IP address 
 QAM outputs 
 Channel Application Mode = Video 
Once a carrier is in video mode, the video stream map becomes active for that 
carrier.  The video stream map serves as a routing table, which maps incoming video 
to unique output carriers.  
Channel Application Mode 
To Verify Channel Application Mode 
1 Navigate to the Maps page. 
2 In the tree menu, select Map Configuration. 
Result: Channel Application Mode is revealed for each output carrier.  
Note: The correct setting is Data. 
  
Video Stream Map Configuration 
For a specific output carrier, using the Maps/Video Stream Map page, the following 
can be configured: 
 Input Stream Destination IP address and UDP port 
 Allowable ingress port or port-pair  
						

							 
 
 Provisioning 
 
78-4025112-01 Rev H0 85 
 
 Stream Type (i.e., SPTS, MPTS) 
 Program Number 
  WARNING: 
The user is responsible for making sure there are no program number or 
PMVs on a given  carrier as well as making sure all replicated transport 
streams have identical advanced settings. If not, the system may have to be 
reset to default settings to recover. 
To Configure the Video Stream Map 
1 Navigate to the Maps page. 
2 In the tree menu, select Video Stream Map. 
Result: The Stream Map Table is displayed. 
 
3 Locate the rows corresponding to the desired Output QAM Channel. 
Note: The RF Gateway 1 web pages use the notation Card/Port. Channel to 
refer to individual carriers. 
4 In the Destination IP Address field, enter the IP address.    
						

							 
Chapter 4    Table-Based Video Specific Operation  
 
 
86 78-4025112-01 Rev H0 
 For unicast streams, entering 0.0.0.0 is equivalent to specifying the GbE 
Video/Data IP address configured for the port pair (port-pair mode) or the 
physical address GbE port (independent mode) selected in step 7.  
Alternatively, the Video/Data IP address (port-pair mode) or GbE port 
address (independent mode) of the desired GbE port or port-pair may be 
explicitly entered. 
 For multicast streams, enter the multicast address of the desired stream.  
5 In the UDP Port field, enter the destination UDP port of the desired stream. For 
unicast streams, the UDP port number uniquely identifies the stream.  For 
multicast streams, this field is ignored. 
6 In the Active field, select the appropriate setting.   
 True - forward (route) the stream to the corresponding QAM output channel 
 False - block the stream to the corresponding QAM channel  
 Delete - deletes the entire routing entry (row) from the stream map. 
7 In the Allowed Ingress Ports field, select the allowed ingress port-pair (port pair 
mode) or allowed ingress GbE port (independent mode). 
 Pair 1 (Ports 1 and 2) - available in port pair mode 
 Pair 2 (Ports 3 and 4) - available in port pair mode 
 Port 1 - available in independent mode 
 Port 2 - available in independent mode 
 Port 3 - available in independent mode 
 Port 4 - available in independent mode 
8 In the Stream Type field, select the stream type. 
 SPTS - Single program encapsulated in the input flow 
 MPTS - Multiple programs encapsulated in the input flow 
 Data - A data stream does not include a PAT or PSI.  A data stream is played 
out at a constant configured rate. 
 Plant - One or more elementary streams without timing information.   A 
plant stream may include a PAT and is played out at a constant configured 
rate. 
9 In the Program Number field, enter the Input or Output program number.   
 For MPTS streams, no input or output  program number may be entered. 
 For SPTS streams, entering a 0 input program number will permit any 
incoming stream to be routed to the port.  Entering a non-zero input program 
number will require the program number of the corresponding input stream 
to match before forwarding (routing) the stream to the corresponding QAM 
channel.   
 For SPTS streams, a unique output program number must be entered for 
each QAM Output Channel.