Who Should Read This User’s Manual ....................................................................................................... 6
Additional Information ................................................................................................................................. 6
Contacting SmartRG Inc. ............................................................................................................................. 6
Advanced Features ....................................................................................................................................... 7
Cisco Prime Home™ ACS ........................................................................................................................ 8
SmartRG™ Product Family .......................................................................................................................... 9
Front Panel LEDs ......................................................................................................................................... 10
Configure Time Settings ............................................................................................................................ 59
Configure User Logins ................................................................................................................................ 61
Reset the Gateway ...................................................................................................................................... 62
Accessing System Logs .............................................................................................................................. 63
Figure 15 WAN Service Configuration (With or Without VLAN Tagging Support) ................................. 24
Figure 16 PPP Username and Password .................................................................................................... 25
Figure 17 WAN IP Settings ............................................................................................................................ 26
Figure 18 WAN NAT, Firewall and IGMP Settings ...................................................................................... 27
This document describes the features, functions and administration of SmartRG™ residential
gateways.
Who Should Read This User’s Manual
The information in this document is intended for Network Architects, NOC Administrators, Field
Service Technicians and other networking professionals responsible for deploying and managing
broadband access networks.
Additional Information
You may find the following documents to be helpful during your access network deployment:
SmartRG Data Sheets
SmartRG Product Release Notes
Deployment and Provisioning Presentation
Contacting SmartRG Inc.
Contact SmartRG Inc. for further assistance.
Hours of operation: Monday – Friday, 5am-6pm Pacific Time (UTC-8:00)
If you prefer to configure your SmartRG’s WAN interface manually, connect a laptop to
any of the LAN ports and follow the instructions in the “Logging in to Your SmartRG™
Gateway” and “Use Case: Creating WAN Connections for Internet Access and Remote
Management” sections. Do NOT connect the WAN interface cable until after the
configuration is completed.
NOTE
Activation server support is provided for ALL SmartRG gateways at no additional cost.
SmartRG Inc. enters gateway MAC addresses into the activation server prior to
shipment.
The Connect-and-Surf feature automatically establishes a WAN connection for default configured
gateways obviating the need for manual or custom configurations. The active physical layer is
detected (ADSL, VDSL or GigE) and layer 3 connectivity is established using PPP authentication or
DHCP.
SmartRG gateways are designed to discover their service provider specific ACS management
settings without the use of custom firmware. SmartRG Inc. maintains an activation server that
associates a device’s MAC address with its service provider’s ACS settings. SmartRG gateways
contact the activation server to have their ACS settings modified upon initial power up (or after
being reset to factory default settings).
TR-069 Remote Management – Automated Configuration Server Support
With a rich TR-069 heritage and a strong commitment to standards based, remote management,
SmartRG gateways are designed for maximum interoperability with industry leading, TR-069 based
remote management systems. SmartRG gateways provide maximum remote manageability and
the highest level of visibility into the connected home yielding:
shorter integration times
lower system integration costs
improved customer support –and-
reduced operational expenses
SmartRG works closely with industry-leading, TR-069 automated configuration server (ACS)
solutions providers to ensure “plug-n-play“ interoperability.
Affinegy ACS
SmartRG gateways have been tested to confirm maximum interoperability with the Affinegy ACS
solution.
Calix Compass/Consumer Connect ACS
In addition to being Calix physical layer certified (to ensure Calix access equipment compatibility),
SmartRG gateways have been tested to confirm maximum interoperability with the Calix
Compass/Consumer Connect ACS solution.
Cisco Prime Home™ ACS
SmartRG gateways have a long history of Prime Home™ (formerly ClearVision) ACS interoperability.
SmartRG residential gateways combine WAN connectivity with a firewall protected router and
industry leading TR-069 remote management support. Most variants provide 802.11n, Wi-Fi
connectivity, as well. See the SmartRG feature details below:
Contact SmartRG Support for detailed descriptions and management of the features listed above.
The gateway’s UI can be accessed via the WAN connection by entering the WAN IP
address in your browser’s address bar and entering the default username and password:
support/support. WAN HTTP access MUST be enabled to access the gateway’s UI via the
WAN connection. See the “Configure Access Controls (HTTP, Telnet, SSH, etc.)” section
for instructions on enabling WAN HTTP access.
IMPORTANT
If your SmartRG gateway is configured for “bridge mode” (modem) operation, your
PC will NOT be able to acquire an address via DHCP. Instead, manually configure
your PC’s interface with an IP address on the default network (e.g. 192.168.1.100).
Logging in to Your SmartRG™ Gateway’s UI
To manually configure the SmartRG access the gateway’s embedded web UI:
1. attach your computer’s RJ45 connection to any of the SmartRG’s LAN ports (1-4)
2. configure your computer’s IP interface to acquire an IP address using DHCP (See the
IMPORTANT note below for instructions on logging in to a SmartRG gateway configured for
“bridge mode” operation.)
3. open a browser and enter the gateway’s default address http://192.168.1.1/admin in the
address bar
Figure 8 Login Username and Password
4. Enter the default username and password: admin/admin and click OK to display the Device
At login the Device Info page will appear. In addition to the basic identification info shown, the
Device Info menu item can be expanded (by clicking the text) to reveal:
WAN connection information
WAN and LAN statistics
Routing table entries
ARP table entries –and-
LAN host DHCP lease information
Con fig u rin g Y our Sm a rtR G ™ - C o mm on U se C ase s
To simplify your deployment of SmartRG gateways this document is structured around specific use
cases designed to illustrate meaningful, service supporting configurations like:
Creating WAN interfaces for Internet data access and remote gateway management
Provisioning the SmartRG for remote management via TR-069
Setting up the LAN
Managing wireless
Creating IPTV service configurations (bridged and routed)
Classifying LAN traffic and applying QoS to support IPTV and VoIP applications
Enabling secure communications (IPSec)
Given the breadth of a SmartRG residential gateway’s features and the diversity of applications,
only the most common use cases are detailed here. Please contact SmartRG Support to inquire
about additional use cases.
Use Case: Creating WAN Connections for Internet Access and Remote
Management
SmartRG residential gateways are commonly deployed to provide Internet access for LAN hosts
such as workstations, gaming consoles, IP cameras and myriad other IP enabled devices
increasingly found in the home or office. Packets routed between LAN hosts and the Internet pass
through the gateway’s routed WAN connection. Remote management (via TR-069) is also
performed through this connection. The typical Internet access/remote management connection
configuration is diagramed below.
Figure 10 Internet / TR-069 Management WAN Connection
WAN connection creation is a two-step process beginning with the configuration of a layer 2
interface (Ethernet or DSL) followed by the creation of a layer 3, WAN service. Common WAN
services include PPPoE, DHCP and Static IP.
Configuring the Layer 2 Interface (Ethernet)
To configure an Ethernet layer 2 interface:
1. Select Advanced Setup -> Layer2 Interface. The default Ethernet WAN interface
802.1P (priority) and 802.1Q (VLAN tag) values will be set at the time of WAN Service
creation as detailed in, “Creating the WAN Service.”
SmartRG™ Residential Gateways
No further configuration is necessary.
Configuring the Layer 2 Interface (Ethernet with VLAN Tags)
In some applications it may be necessary to segment the Ethernet WAN interface into separate
VLANs. A common application for a VLAN segmented WAN interface is bridged IPTV as detailed in
the “Bridged IPTV Configuration” section. To configure the layer 2 Ethernet interface to support
VLAN tagged traffic:
1. Select Advanced Setup -> Layer2 Interface. The default Ethernet WAN interface
Enabling QoS for routed IPTV service configurations will improve channel change
performance.
NOTE
802.1P (priority) and 802.1Q (VLAN tag) values will be set at the time of WAN Service
creation as detailed in, “Creating the WAN Service.”
5. IMPORTANT - Check “Enable Quality of Service” if you intend to support QoS classified
traffic through the WAN service.
6. Click Apply/Save.
Configuring the Layer 2 Interface (VDSL/PTM with VLAN Tags)
In some applications it may be necessary to segment the PTM WAN interface into separate VLANs.
A common application for a VLAN segmented WAN interface is bridged IPTV as detailed in the
“Bridged IPTV Configuration” section. To configure the layer 2 PTM interface to support VLAN
tagged traffic select “VLAN MUX Mode” for “Connection Mode” in step 4 of the “Configuring the
Layer 2 Interface (PTM – Supported on ADSL and VDSL)” section.
8. Select the WAN interface to be used by this WAN service. Click Next.
9. Select “Obtain DNS info from a WAN interface” and select the desired WAN interface from
the drop down list (a single WAN interface is common unless you are creating bridged IPTV
configurations) –or- select “Use the following Static DNS IP address” and enter the IP addresses of your network’s primary and secondary DNS servers. Click Next.
10. Review the WAN service summary. If you are satisfied click Apply/Save.
This step is not required for production SmartRG gateways. SmartRG maintains an
“Activation Server” that associates MAC addresses with service providers’ ACS
management URLs. After the SmartRG has established its WAN connection (using the
Connect-and-Surf algorithm) it connects to the SmartRG Activation Server and reports its
MAC. The Activation Server changes the ACS management URL to point to the service
provider’s ACS.
NOTE
Configure less and deploy more. Manage subscriber services and your entire gateway
fleet with the ClearVision® management system. Contact SmartRG to start your trial
SmartRG™ Residential Gateways
Use Case: Provisioning Your SmartRG for Remote ACS Management
To manually provision your SmartRG for management by a TR-069 enabled Automated
Configuration Server:
1. Select Management -> Management Server -> TR-069 Client.
Figure 19 TR-069 Management Settings
2. Enter the following parameter values:
Enable “Informs”
Set the “Inform Interval” to 7200 seconds
Set the “ACS URL” (e.g. http://myISP.acs.com/)
Leave the “ACS User Name” and “ACS Password” blank
Enable “Connection Request Authentication”
Set the “Connection Request User Name and Password” to admin/admin
Use Case: Setting Up Wireless Distribution System (WDS)
When deployed in a larger home or office, a single wireless access point may not be able to provide
adequate Wi-Fi coverage. Wireless Distribution Systems (WDS) provides a solution for this
problem. WDS combines multiple gateways to act as a single larger wireless access point allowing
Wi-Fi clients to seamlessly roam all access points plus it provides wired access to the entire
network.
Two or more SmartRG gateways can be configured for WDS operation. The example below depicts
a WDS deployment with three SmartRG gateways in a large home or office – one primary gateway
in the center of the building and one remote gateway at either end of the building.
Figure 24 Wireless Distribution System
Configuring the SmartRG gateways for WDS operation requires the setting of WAN, LAN and
WIRELESS parameters on all gateways included in the WDS system.
At this point your web browser session will terminate as the LAN IP address has
changed from 192.168.1.1 to 192.168.1.x. Reconnect your web browser to the
remote SmartRG referencing the new LAN IP address.
IMPORTANT
When configuring more than two gateways for WDS operation, the remote gateways
MUST NOT be partnered together to avoid creating an Ethernet loop.
SmartRG™ Residential Gateways
To configure the WAN connections…
1. On the primary SmartRG gateway: configure the routed WAN connection following the
instructions in the “Use Case: Creating WAN Connections for Internet Access and Remote
Management” section.
2. On the remote SmartRG gateway(s): no WAN configuration is required as the WAN connection
is unused.
To configure the LAN interfaces…
3. On the primary SmartRG gateway:
a) configure the LAN interface following the instructions in the “Use Case: Setting Up the LAN”
section.
b) ensure the DHCP Server is ENABLED and set the End IP Address such that enough LAN IP
addresses are left for static allocation to the remote gateway(s) included in the WDS
system.
4. On the remote SmartRG gateway(s):
a) configure the LAN interface following the instructions in the “Use Case: Setting Up the LAN”
section. It is IMPORTANT to disable the DHCP server.
b) ensure the LAN IPaddress(es) are assigned from the remaining IP addresses not included in
the DHCP server pool on the primary SmartRG gateway.
To configure the WIRELESS interfaces…
5. On the primary SmartRG gateway: configure the WIRELESS interface following the instructions
in the “Use Case: Setting Up Wireless” section. Do NOT select “Auto” for the Channel value.
6. On the remote SmartRG gateway(s): configure the WIRELESS interface following the
instructions in the “Use Case: Setting Up Wireless” section. Select the same SSID, Security
settings and Channel configured on the primary gateway.
7. On the primary and remote SmartRG gateways:
1. select Wireless -> Wireless Bridge and set “AP Mode” to Access Point
2. set “Bridge Restrict” to Enabled(SCAN)
3. click Apply/Save and wait for the page to refresh
4. select the partner gateway (which has the same SSID as the primary gateway) by checking
The SR350N, SR350NE, SR500N and SR500NE SmartRG gateways are designed to meet the
demands of IPTV service deployments.
Typically IPTV services have been deployed using bridged architectures with public IP addresses
assigned to the IPTV Set-top-boxes (STBs) connected to the gateway’s LAN ports. A typical bridged
IPTV service configuration is shown below.
Figure 25 Bridged IPTV Configuration
Recently service providers have begun deploying routed IPTV services with STBs being assigned
private LAN IP addresses by the gateway. A typical routed IPTV service configuration is shown
below.
SmartRG gateways are designed to exceed the high bandwidth demands of either IPTV service
architecture. Refer to the appropriate section below to configure the SmartRG gateway for your
particular IPTV deployment architecture.
Bridged IPTV Configuration
A bridged IPTV configuration is comprised of:
one (or more) WAN connections
one (or more) LAN connections –and-
an interface grouping structure to bind all of the connections together
The more generalized bridged IPTV service configuration with multiple WAN connections is shown
below.
To configure the SmartRG for bridged IPTV service deployments (with one or more WAN
connections) start by creating the bridged WAN connections:
1. Create a Layer 2 interface following the instructions detailed in:
a. “Configuring the Layer 2 Interface (Ethernet)”
b. “Configuring the Layer 2 Interface (ADSL)” or
c. “Configuring the Layer 2 Interface (PTM – Supported on ADSL and VDSL)”
as appropriate for your particular SmartRG (Ethernet or DSL).
2. Select Advanced Setup -> WAN Service.
Figure 28 Selecting a Bridged WAN Service’s Layer 2 Interface
3. Select the Layer 2 Interface (created in step 1 above) from the drop down list and click
The generalized (more complex) IPTV bridge group is detailed here. The majority of
DSLAMs require only a single WAN connection to support IPTV services. In that typical
case:
The “atm0” interface would provide routed WAN access for Internet services and
remote management –and-
The “atm1” interface would provide bridged WAN access for all IPTV related
services (multi-cast streams, middleware server access and IGMP signaling)
At the conclusion of step 9 your Layer 2 Interface summary (Advanced Setup -> Layer 2 Interface)
will look similar to:
Creating Vendor ID Based Interface (Bridge) Groupings
To provide greater flexibility when connecting set-top-boxes to LAN ports SmartRG gateways
support “Vendor ID Based” bridge groupings. Instead of adding specific LAN ports to the bridge
group, you can specify the Vendor ID of the set-top-box. Any traffic received on any LAN port
containing the specified Vendor ID will be bridged to the designated bridged WAN connection.
To configure Vendor ID based interface groupings, add only the WAN interface(s) to the bridge
group and then specify the required Vendor ID(s) in the following list:
The SmartRG family of gateways employs “Differentiated Services” (RFC 2474) to
provide IP traffic QoS. When configuring QoS for various traffic categories the following
Differentiated Services Code Point (DSCP) values or suggested:
Internet data – Best Effort (DSCP 0)
IPTV – AF21 (DSCP 18)
VoIP – Expedited Forwarding (DSCP 46)
NOTE
Some STBs pre-mark their IP traffic making classification a relatively straightforward
task for the gateway. If your STB pre-marks its traffic, passing the DSCP mark through
Routed IPTV Configuration (Single WAN Connection)
The common routed IPTV configuration is virtually identical to the WAN connection configuration
for Internet data services with one notable exception; the addition of quality of service (QoS).
While not an absolute requirement, applying QoS to LAN traffic (with higher priority given to STBs)
ensures the timely and deterministic delivery of IPTV related uni-cast requests and IGMP signaling
through the gateway. This provides repeatable, shortest time possible channel changes in the
presence of other LAN traffic. A typical routed IPTV service configuration with only one WAN
connection is shown below.
Figure 36 Routed IPTV Configuration (Single WAN Connection)
To configure the SmartRG for routed IPTV service deployments:
1. Ensure “IGMP Snooping” has been enabled on the LAN as detailed in, “Use Case: Setting Up
the LAN.”
2. Create a routed WAN connection as detailed in, “Use Case: Creating WAN Connections for
Internet Access and Remote Management.”
3. (Optional) Create traffic classifiers and priority queues for the various traffic categories on
your LAN (e.g. Internet data, IPTV and VoIP) as detailed in, “Use Case: Applying Quality of S.”
Routed IPTV Configuration (Multiple WAN Connections)
It is also possible to create routed IPTV configurations with multiple WAN connections. The notable
difference to typical routed IPTV configurations is the addition of one or more bridged WAN
connections to support multiple multicast IPTV streams. Again QoS is suggested. A typical multiWAN connection, routed IPTV service configuration is shown below.
Figure 37 Routed IPTV Configuration (Multiple WAN Connection)
To configure the SmartRG for multi-WAN connection, routed IPTV service deployments, follow the
single WAN connection, routed IPTV configuration instructions above –plus- add bridged WAN
connections using the instructions detailed in, “Creating Bridged WAN Connections.”
The residential gateway plays no part in the prioritization of downstream traffic.
NOTE
Mediaroom based IPTV STBs place the DSCP18 mark on all upstream traffic.
Use Case: Applying Quality of Service (QoS) to VoIP and IPTV LAN Traffic
When deploying time critical services such as VoIP and IPTV comingled with common data services,
it becomes necessary to prioritize the time critical, upstream LAN traffic over common data traffic
(e.g Internet data and file transfers). Time critical traffic commonly includes SIP signaling (VoIP call
setup/teardown) and IGMP signaling (IPTV channel change). The SmartRG line of gateways
prioritizes time critical traffic using the “Differentiated Services Code Point” field in the IP header
as defined by RFC 2474.
Traffic generated by LAN hosts such as VoIP phones, IPTV STBs and PCs is identified by “classifiers”
and placed into prioritization “queues.” Queues are emptied through the routed WAN connection
based on queue priority. Classifiers can identify traffic based on a number of criteria including:
source/destination MAC address, source/destination IP address, protocol, DSCP mark, etc. This
section describes a typical QoS configuration to prioritized upstream VoIP and IPTV traffic.
A typical VoIP/IPTV/data QoS configuration is shown below:
Figure 38 Typical QoS Configuration to Support VoIP and IPTV Services
VoIP traffic is identified by its source MAC/Mask (VoIP user agent OUI) and IPTV traffic is identified
by the DSCP mark in its IP header. All remaining traffic is placed in the data (default) queue.
The QoS configuration process is comprised of three main steps:
Enable QoS on the routed WAN connection and enable QoS processing
Create traffic queues to prioritize the different types of traffic –and-
Create traffic classifiers to identify the different types of traffic
The default data queue depicted in the QoS architecture diagram above does not need
to be specifically created.
SmartRG™ Residential Gateways
11. Leave the “DSL Latency” value set to Path0 and Click Apply/Save.
12. Enable the newly created queues by selecting Advanced Setup -> Quality of Service -> QoS
Queue Config, check the “Enable” boxes for the new queues and click Enable. The correct
queue configuration for VoIP and IPTV services should look like:
When configuring an IPSec tunnel both ends of the tunnel must be configured with
identical encryption and authentication methods.
SmartRG™ Residential Gateways
Use Case: Configuring IP Security (IPSec) in Support of VPNs
IP Security (IPSec) is a suite of IETF standards developed to provide data integrity and privacy, key
management and data authentication at the IP layer. Typically IPSec is deployed to create Virtual
Private Networks (VPNs) between communicating peers.
header by encapsulating it in an additional IP header. The outer IP header remains
unprotected.
5. Enter the IP address of the tunnel’s remote IPSec gateway.
6. Select either a single IP address or a subnet of IP addresses for the local end of the IPSec
tunnel.
7. Enter either the single local IP address or the local subnet definition.
8. Select either a single IP address or a subnet of IP addresses for the remote end of the
IPSec tunnel.
9. Enter either the single remote IP address or the remote subnet definition.
10. Select the Key Exchange Method. Keys can be exchanged manually (set identically on both
ends) or automatically using “Internet Key Exchange” (IKE). This example assumes the
selection of IKE.
11. Select the Authentication Method. Authentication can be performed either with a “Pre-
Shared Key” or a certificate. This example assumes the selection of a Pre-Shared Key.
12. Enter the Pre-Shared Key value. Both character and hexadecimal values are acceptable
(e.g. 0x123abc456def789 or VPN@tunnel_123)
13. Enable/Disable Perfect Forward Secrecy. PFS ensures the same key will not be generated
again forcing a new Diffie-Hellman key exchange. This prohibits hackers from snooping a
present transmission to decipher a key and then use that key to observe future data
transmissions.
14. Set the Phase 1 Advanced IKE Settings (establish a secure, authenticated channel):
a. Select the Mode: “Main” mode is more secure but adds delay. “Aggressive” mode is
faster but less secure.
b. Select the Encryption Algorithm: AES-256 is the most secure.
c. Select the Integrity Algorithm: MD5 is a one way hash with a 128 bit digest. SHA1 is
a one way hash with a 160 bit digest.
d. Select the Diffie-Hellman Group for Key Exchange. Diffie-Hellman is a cryptography
protocol enabling two devices to establish a shared secret via unsecured channels.
More bits provide greater security but come with increased time for key
computation.
e. Specify the Key Life Time. Keys will be renewed after this interval.
15. Set the Phase 2 Advanced IKE Settings (generate keys and negotiate the IPSec Security
Pressing the reset switch for more than 10 seconds causes the SmartRG gateway to
reset into its boot image rendering the gateway non-functional. This condition can be
detected by:
the inability to access the SmartRG gateway’s user interface using your
web browser –and-
the inability to properly establish a WAN connection
To correct this condition simply cycle power on the gateway.
NOTE
Software resets, hardware resets and power cycles behave identically.
SmartRG™ Residential Gateways
Reset the Gateway
Hardware Reset
Reset the gateway by inserting a paper clip or similar tool into the reset switch hole located on
either the rear or the bottom of the gateway (depending upon model). Press the switch briefly to
reset the device.
Hardware Reset (to Factory Default Settings)
To reset the gateway to its factory default settings press the reset switch for 6 to 8 seconds. After
releasing the reset switch the gateway will continue booting with a factory default configuration.
Software Reset
To reset the gateway using the SmartRG gateway’s web UI:
Monitoring Traffic on the WAN Interface (Port Mirroring)
Monitoring traffic on the WAN interface can be difficult as intervening equipment between the
access gear and the gateway is necessary to provide a monitoring point for your work station. To
simplify WAN traffic monitoring SmartRG gateways provide the capability of “mirroring” WAN traffic to any of the gateway’s Ethernet LAN ports.
To configure the SmartRG gateway for port mirroring:
1. Enter the URL for the “Port Mirroring” hidden page into your browser: <LAN IP
Address>/admin/engdebug.cmd.
2. Click the Enable check box.
3. Select the target LAN port from the Mirror Interface dropdown box.
4. Click Apply/Save.
Figure 49 Configuring Port Mirroring to Monitor WAN Interface Traffic