Ruckus Wireless SmartCell Gateway 200 User manual

Ruckus Wireless™
SmartCell Gateway™200
Tunneling Interface Reference Guide
for SmartZone 3.4.1
Part Number 800-71380-001 Rev A
Published July 2016
www.ruckuswireless.com

SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 2
Copyright Notice and Proprietary Information
Copyright 2016. Ruckus Wireless, Inc. All rights reserved.
No part of this documentation may be used, reproduced, transmitted, or translated, in any form or by any means,
electronic, mechanical, manual, optical, or otherwise, without prior written permission of Ruckus Wireless, Inc.
(“Ruckus”), or as expressly provided by under license from Ruckus.
Destination Control Statement
Technical data contained in this publication may be subject to the export control laws of the United States of America.
Disclosure to nationals of other countries contrary to United States law is prohibited. It is the reader’s responsibility to
determine the applicable regulations and to comply with them.
Disclaimer
THIS DOCUMENTATION AND ALL INFORMATION CONTAINED HEREIN (“MATERIAL”) IS PROVIDED FOR GENERAL
INFORMATION PURPOSES ONLY. RUCKUS AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, WITH REGARD TO THE MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OR THAT THE
MATERIAL IS ERROR-FREE, ACCURATE OR RELIABLE. RUCKUS RESERVES THE RIGHT TO MAKE CHANGES OR
UPDATES TO THE MATERIAL AT ANY TIME.
Limitation of Liability
IN NO EVENT SHALL RUCKUS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUEN-
TIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY YOU OR ANY
THIRD PARTY, WHETHER IN AN ACTION IN CONTRACT OR TORT, ARISING FROM YOUR ACCESS TO, OR USE
OF, THE MATERIAL.
Trademarks
Ruckus Wireless, Ruckus, the bark logo, ZoneFlex, FlexMaster, ZoneDirector, SmartMesh, Channelfly, Smartcell,
Dynamic PSK, and Simply Better Wireless are trademarks of Ruckus Wireless, Inc. in the United States and other
countries. All other product or company names may be trademarks of their respective owners.

Contents
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 3
Contents
About This Guide
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Impacted Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Online Training Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Documentation Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 Core Network Protocols
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Core Network Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
L2oGRE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
L2oGRE with TTG PDG Profile with 802.1x Authentication. . . . . . . . . . . . . . . . . . . . . . 14
Bridge Mode - (0-2 tags) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GTP Tunnel with GGSN (GTPv1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
GTP Tunnel with PGW (GTPv2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
PMIPv6 Tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2 3rd Party Access Network Protocol
Access Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3rd Party AP Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
L2oGRE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
L2oGRE and Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
QinQ (L2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QinQ and TTG+PDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3rd Party Session Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3 Tunnel Combinations and DHCP Processing
Tunnel Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
DHCP Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
DHCP Relay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Contents
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 4
DHCP Option 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Index

SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 5
About This Guide
This Ruckus Wireless™ SmartCell Gateway™ (SCG) 200 Tunneling Interface
Reference Guide describes the AP networking protocols supported in the access
and core networks.
This guide is written for service operators and system administrators who are
responsible for managing, configuring, and troubleshooting Ruckus Wireless
devices. Consequently, it assumes a basic working knowledge of local area
networks, wireless networking, and wireless devices. .
NOTE If release notes are shipped with your product and the information there
differs from the information in this guide, follow the instructions in the release notes.
Most user guides and release notes are available in Adobe Acrobat Reader Portable
Document Format (PDF) or HTML on the Ruckus Wireless Support Web site at
https://support.ruckuswireless.com/contact-us.

About This Guide
Document Conventions
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 6
Document Conventions
Tabl e 1 and Table 2 list the text and notice conventions that are used throughout
this guide.
Terminology
Tabl e 3 lists the terms used in this guide.
Table 1. Text conventions
Convention Description Example
monospace Represents information as it
appears on screen
[Device name]>
monospace bold Represents information that
you enter
[Device name]> set
ipaddr 10.0.0.12
default font bold Keyboard keys, software
buttons, and field names
On the Start menu, click All
Programs.
italics Screen or page names Click Advanced Settings.
The Advanced Settings page
appears.
Table 2. Notice conventions
Notice Type Description
NOTE Information that describes important features or instructions
CAUTION! Information that alerts you to potential loss of data or potential
damage to an application, system, or device
WARNING! Information that alerts you to potential personal injury
Table 3. Terms used in this guide
Term Description
BRI Binding Revocation Indication
Control Plane SCG Control Plane
CVLAN Customer VLAN
Data Plane SCG Data Plane
DHCP Dynamic Host Configuration Protocol (DHCP)
DM Disconnect Message

About This Guide
Terminology
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 7
EPC Evolved Packet Core
EPS Evolved Packet System
fwd_policy Forwarding policy to identify one of the supported network
protocol types
G-PDU GTP Packet Data Unit
GGSN Gateway GPRS Support Node
GTP GPRS Tunneling Protocol
ICMP Internet Control Message Protocol
L2oGRE Standard GRE (version 0 no options) of Ethernet packets
L2oGRE Layer 2 over GRE
LBO Local Breakout Traffic
LMA Local Mobility Anchor
MAG Mobile Access Gateway
MAG Mobile Access Gateway
MN Mobile Node
PDG Packet Data Gateway
PDN Packet Data Network
PGW PDN Gateway
PMIPv6 Proxy Mobile IPv6
RADIUS Remote Access Dial-Up User Service
SGW Serving Gateway
SVLAN Service VLAN
TEIDs Tunnel End Point Identifiers
TTG Tunnel Termination Gateway
Table 3. Terms used in this guide
Term Description

About This Guide
References
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 8
References
Tabl e 4 lists the specifications and standards that are referred to in this guide.
Impacted Systems
Tabl e 5 lists the impacted systems.
Table 4. References used
No. Reference Description
1 RFC 2784 Generic Routing Encapsulation (GRE)
2 IEEE 802.1ad Provider Bridges
Table 5. Impacted Systems
Term Description
Controlplane • User Interface – Configuration and statistics reporting
• Configuration - For core network tunnel destinations
• New access - Network type configuration for 3rd Party AP
Zones
• Session Manager – Supports additional core network tunnel
types
• ICD Message - Enhancements to support additional
forwarding policy
• AAA Proxy - Supports additional forward policy – L2oGRE
and QinQ
Dataplane • Statistics reporting per:
User per forward policy
Access network type
Core network type
• Datacore for:
New forward policy
I/O modules for L2oGRE (both access and core)
QinQ for core network side traffic
Access Point (AP) Host pad - New forward policy support for L2oGRE

About This Guide
Legend
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 9
Legend
Tabl e 6 lists the legends used in this guide.
Related Documentation
For a complete list of documents that accompany this release, refer to the Release
Notes.
Online Training Resources
To access a variety of online Ruckus Wireless training modules, including free
introductory courses to wireless networking essentials, site surveys, and Ruckus
Wireless products, visit the Ruckus Wireless Training Portal at:
https://training.ruckuswireless.com
Documentation Feedback
Ruckus Wireless is interested in improving its documentation and welcomes your
comments and suggestions. You can email your comments to Ruckus Wireless at:
[email protected]
When contacting us, please include the following information:
• Document title
• Document part number (on the cover page)
• Page number (if appropriate)
For example:
• SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone
3.4.1
• Part number: 800-71380-001
• Page 280
Table 6. Legend used
Legend Description
M Mandatory
O Optional
C Conditional

SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 10
1
Core Network Protocols
In this chapter:
•Overview
•Core Network Protocols

Core Network Protocols
Overview
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 11
Overview
This interface reference guide describes the enhancements that support additional
protocols for access and core network traffic. This includes supporting additional
tunnel types (both access and core), core network forwarding rules and new
networking protocols (both access and core).
On the core network, UE traffic from APs along with next-hop destinations based
on forwarding policy supports:
• L2oGRE, which establishes a GRE tunnel to the core network forwarding
gateway along with an Ethernet payload. That is, the client's MAC is available
to the next hop gateway. In addition, data plane supports in sending non-
tunneled packets to the core network with optional VLAN or QinQ tags.
• PMIP tunneling is between the SCG (MAG) and LMA and is per session. The
tunneling to carry the payload is IPv4 over GRE over IPv4 type.
On the access network, UE traffic from 3rd Party APs is sent to the data plane via
an L2oGRE tunnel, or alternatively a QinQ tunnel configuration on the access
network. This is in addition to QinQ packets on the access network. The configu-
ration is per zone with specifications of the IP range of the connecting tunnel
endpoint. The tunnel is accepted and the UE packet is accepted (based on per zone
authentication settings) as long as the IP address of the GRE tunnel endpoint is
within that range.
Figure 1 shows the tunneling interface and its various tunneling interfaces.

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 12
Figure 1. Tunneling interface for the SCG
•
NOTE: Refer to About This Guide for the conventions used in this guide.
Core Network Protocols
Each UE is mapped to one single core network protocol type. A maximum of 64
core gateways is supported, which translates to supporting 32 GGSNs and 64 GRE
core gateways including L2oGRE in any combination.
This section covers:
•L2oGRE
•L2oGRE with TTG PDG Profile with 802.1x Authentication
•Bridge Mode - (0-2 tags)
•GTP Tunnel with GGSN (GTPv1)
•GTP Tunnel with PGW (GTPv2)
•PMIPv6 Tunnelling

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 13
L2oGRE
L2oGRE is a core network tunneling protocol, with the following features:
• The GRE header protocol type is 0x6558
• The GRE payload includes Ethernet header for the UE
• The only supported combination of access network protocol type is L2, which
includes Ruckus GRE and L2oGRE.
• ARPs are forwarded to the L2oGRE tunnel
• DHCP relay function is optionally configured. If it is not configured, the DHCP
packets are forwarded in the L2oGRE tunnel.
KeepAlive can be configured to L2oGRE gateway. The only KeepAlive mechanism
supported is ICMP echo/reply messages, which are sent or received from L2oGRE
gateway. The period for sending KeepAlive is mseconds (default = 10
seconds) and the total number of retries is n(default counter is 3). The
values for mand nare configurable from the CLI.
KeepAlive will always be answered, if it is received from the L2oGRE gateway. The
data plane sends a KeepAlive packet only if no user traffic is received from the
L2oGRE gateway within the KeepAlive period. An event is generated indicating that
the L2oGRE gateway is unreachable when the maximum number of retries exceeds.
This event occurs when L2oGRE does not receive an ICMP reply to an ICMP request
sent from the datablade. Figure 2 displays the L2oGRE traffic flow.

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 14
Figure 2. L2oGRE control and data traffic flow.
NOTE: For information on how to configure L2oGRE, refer to the SmartCell
Gateway 200 Administrator Guide (PDF) or the SmartCell Gateway 200 Online Help,
which is accessible from the SCG Web interface.
L2oGRE with TTG PDG Profile with 802.1x
Authentication
This network protocol supports authentication of UE tunnel traffic from 3rd party
APs using 802.1X, via L2oGRE tunnels. 3rd party AP UE's using 802.1X authenti-
cation is already supported with QinQ access and LBO core forwarding by config-
uring the TTG+PDG profile.
The UE authentication is similar to QinQ and LBO expects that the UE packet is
seen at the data plane from an L2oGRE tunnel. This means that the L2oGRE and
LBO path is already supported for the parameter auth_type.

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 15
In this particular path, as long as the L2oGRE AP can be mapped to a configured
zone (based on IP address range), the UE packet will be accepted and forwarded.
The datacore verifies the unknown UE's coming from the AP in the L2oGRE LBO
zone before forwarding the UE packets. The following are the UE packet processing
steps.
1UE associated with AP successfully is authenticated through 802.1X.
2The authenticated UE traffic is sent to data plane through the L2oGRE tunnel.
3The data blade receives the first UE packet (L2oGRE encapsulated). This could
either be the DHCP packet or any other IP packet (roaming to another data plane)
4If the UE entry is not found, a message to GTpmgr is sent about the unknown
UE status.
5GTpmgr sends an ICD message (D-C-DATA-TRIG-MSG) to the UE using the UE
Mac address.
6The AUT indicates the UE is authenticated with the message C-D-DATA-TRIG-
MSG (status=22), The UE authentication state will be set to
UE_AUTH_NORMAL.
7Subsequent UE packets are bridged out, VLAN/QinQ tagging rules will be as
per the configuration.
8If the UE IP address is later identified, it is tracked through DHCP ACK. The AUT
will receive a D-C-NTFY-MSG, which include the UE IP address.
9If the UE exists, the data plane UE entry is timed-out and marked as inactive.
The GTpmgr sends a D-C-NTFY-MSG (cause=1) to the AUT notifying the UE
timed out event.
10 If the UE returns or moves to another datablade, the status query process for
unknown UE is called again.

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 16
Bridge Mode - (0-2 tags)
Traffic from UE's are QinQ tagged and bridged out to the core network as seen in
Figure 3. The core VLAN type can be either QinQ or preserve the access VLAN
(1 tag). For core network traffic, the QinQ traffic is considered as a type of LBO traffic
or VLAN (single) or untagged traffic.
Figure 3. QinQ core network
NOTE: For information on how to configure QinQ, refer to the SmartCell Gateway
200 Administrator Guide (PDF) or the SmartCell Gateway 200 Online Help, which
is accessible from the SCG Web interface.
The bridge mode now supports optional DHCP relay function. If it is enabled the
user equipment’s DHCP packets are relayed to a configured DHCP server. Option
82 sub-option configurations are the same as before.

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 17
GTP Tunnel with GGSN (GTPv1)
Gn interface is used in controlling the signal between the SCG and GGSN as well
as for tunneling end user data payload within the backbone network between both
the nodes.
GTP transmits user data packets and signaling between SCG and GGSN. GTP
encapsulates traffic and creates GTP tunnels, which act as virtual data channels for
transmission of packet data between SCG and GGSN. A GTP tunnel is established
between SCG and GGSN through create PDP context procedure for a data session
initiated from UE.
A GTP tunnel is identified by a pair of IP addresses and a pair of GTP Tunnel End
Point Identifiers (TEIDs), where one IP address and TEID is for the SGSN and the
other is for the GGSN. TEID is a session identifier used by GTP protocol entities in
the SGSN and in the GGSN.
The two TEID are defined each for GTP-C and GTP-U. GTP-U is a tunneling
mechanism that provides a service for carrying user data packets. On both planes,
a GTP header encapsulates the data package, called G-PDU, and a path imple-
mented by UDP/IP is used as bearer of the GTP traffic. GTP-C is a tunnel control
and management protocol and is used to create, modify and delete tunnels.
The SCG supports the following categories of GTP signaling traffic:
• Path management messages - The main purpose of these messages is to
supervise an UDP/IP path to ensure that connectivity failure can be detected on
time. This is managed by frequently sending GTP echo request or response
packets between the SCG and the GGSN.
• Tunnel management messages - These contain messages that establish, modify
and release GTP tunnels.
Figure 4 shows the message flow between the SCG and the GGSN for establishing
a GTP tunnel. Figure 5 shows the Gn interface flow.

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 18
Figure 4. Message flow between the SCG and GGSN

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 19
Figure 5. Gn interface flow
NOTE: For information on tunnel and path messages, refer to the SmartCell
Gateway 200 Gn Interface Reference Guide (PDF).

Core Network Protocols
Core Network Protocols
SmartCell Gateway 200 Tunneling Interface Reference Guide for SmartZone 3.4.1, 800-71380-001 Rev A 20
GTP Tunnel with PGW (GTPv2)
This is the interface between the SCG with PGW. It is the control plane GPRS
tunneling protocol messages v2 for EPS interfaces (GTPv2-C) from the SCG and
PGW.
The S2a interface is used in controlling the signal between the SCG and PGW. It
also acts as a tunnel for end user data payload within the EPC network.
The GTP transmits user data packets and signaling messages between the SCG
and PGW. GTP encapsulates traffic and creates GTP tunnels, which act as virtual
data channels. A GTP tunnel is established between the SCG and PGW through
Create Session Request procedure for a data session initiated from the UE.
The SCG acts as trusted non-3GPP access network (TWAN) towards PGW with
S2a (GTPv2) interface. In case the operator EPC network, does not support the S2a
interface, the SCG can be statically configured to support S5 (GTPv2) interface, in
which case the SCG acts as serving gateway.
A GTP tunnel is identified by a pair of IP addresses and a pair of GTP TEIDs, where
one IP address and TEID is for the SCG (TWAN) and the other is for the PGW. The
TEID is a session identifier used by GTP protocol entities in the SCG and in the PGW.
GTP separates signaling from payload. Traffic is sorted onto a control plane (GTP-
C) for signaling and a user plane (GTP-U) for user data. GTP-C is a tunnel control
and management protocol and is used to create, modify and delete tunnels. GTP-
U is a tunneling mechanism, which provides a service for carrying user data packets.
On both planes, a GTP header encapsulates the data package, called GPDU, and
a path implemented by UDP/IP is used as bearer of the GTP traffic. The SCG
supports the following categories of GTP signaling traffic:
• Path management messages - The main purpose of these messages is to
supervise an UDP/IP path to ensure that connectivity failure can be detected on
time. This is managed by frequently sending GTP echo request or response
packets between the SCG and PGW.
• Tunnel management messages - These contain messages that establish, modify
and release GTP tunnels.
Figure 6 shows the deployment of the SCG in operator networks with 3G and EPC.