Calix E7 R2.3 GPON Applications Guide

Calix E7 R2.3 GPON Applications Guide
Calix E7 R2.3
GPON Applications Guide
February 2015
#220-00650, Rev 13
Contents
About This Guide...................................................................... 7
Chapter 1: GPON Solution .................................................... 11
Calix E7 GPON Solution Overview ......................................................................... 12
GPON Network Components .................................................................................. 14
Supported GPON Equipment.................................................................................. 16
Supported GPON Services ..................................................................................... 25
Home Gateway Overview ........................................................................................ 27
Home Gateway Concepts ............................................................................... 28
HGW Services ................................................................................................ 30
Home Gateway Port Assignments .................................................................. 32
RG Management Modes ................................................................................. 34
HGW Management Interfaces ........................................................................ 37
Chapter 2: Service Provisioning Overviews ....................... 41
Overview: GPON L2 Data Services ........................................................................ 42
To configure L2 data services ................................................................................ 43
Overview: GPON L2 IP Video Services .................................................................. 44
To configure L2 video services .............................................................................. 45
Overview: GPON L2 MVR Video Service ............................................................... 46
To configure L2 MVR video services ..................................................................... 47
Overview: HGW Applications - External Mode ..................................................... 48
To configure HGW applications using an RG configuration file via GPON OMCI53
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
4
Overview: HGW Applications - Native Mode (P-Series Only) .............................. 54
To configure HGW applications with P-series in native mode ............................ 56
Overview: HGW Applications - TR-069 .................................................................. 57
To configure an HGW application using TR-069 ................................................... 58
Overview: GPON Voice Services............................................................................ 59
To configure GPON voice services for P-series ONTs ......................................... 60
Overview: SIP Gateway Service with Configuration File...................................... 61
To configure SIP gateway service with OMCI provisioning ................................. 63
Chapter 3: Configuring GPON Applications ....................... 65
Step 1. Configure the Network Uplink(s) for GPON Services .............................. 66
Overview: Configuring the Network Uplink(s) ................................................. 66
Configuring the Ethernet Uplink Port............................................................... 67
Configuring an E7 Ethernet or LAG Interface ................................................. 73
Creating the Service VLAN(s) ......................................................................... 86
Additional multicast addressing considerations .............................................. 89
Adding the Uplink Interface(s) to VLAN Memberships .................................. 107
Step 2. Create GPON-Related Profiles ................................................................. 110
Overview: GPON-Related Profiles ................................................................ 110
Creating an ONT Profile................................................................................ 115
Creating QoS Profiles ................................................................................... 116
Traffic management recommendations ............................................................... 164
Applying shaping and policing ............................................................................ 165
Traffic shaping on P-Series ONTs........................................................................ 166
Creating Data and Video Service Profiles ..................................................... 166
Creating Voice Service Profiles .................................................................... 201
Creating T1/E1 Service Profiles .................................................................... 221
Managing Global Profiles in CMS ................................................................. 226
Step 3. Configure a PON ....................................................................................... 231
Overview: Configuring a PON ....................................................................... 232
Configuring an E7 GPON Port ...................................................................... 232
Scheduling an RG Configuration Retrieve Task in CMS ............................... 235
Retrieving and Applying a Configuration File ................................................ 238
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
5
Creating GPON ONTs .................................................................................. 244
Adding PON Upstream CoS Profiles to an ONT ........................................... 256
Applying an ONT Template........................................................................... 257
Configuring an ONT Ethernet Port ................................................................ 257
Configuring an ONT Voice Port .................................................................... 260
Configuring an ONT Residential Gateway Interface ..................................... 262
Configuring an ONT Full Bridge Interface ..................................................... 266
Step 4. Configure Subscriber Services................................................................ 269
Configuring Data Services ............................................................................ 269
Configuring IP Video Services ...................................................................... 285
Configuring Voice Services ........................................................................... 307
Configuring RF Overlay Video Services........................................................ 330
Configuring T1/E1 Services .......................................................................... 336
Chapter 4: Service Provisioning Examples ....................... 349
Example: Data Services ........................................................................................ 350
Example: Video Services ...................................................................................... 358
Example: MVR Video Services ............................................................................. 366
Example: SIP GW Voice Services ........................................................................ 373
Example: HGW Service - External Mode.............................................................. 380
Example: Multicast IPTV over L2 Bridge Wi-Fi ................................................... 389
Example: Multicast IPTV over RG Wi-Fi............................................................... 401
Example: HGW Service - P-Series Native Mode .................................................. 413
Example: HGW Service - TR-069 .......................................................................... 422
QoS Service Model Examples .............................................................................. 431
Multiple services, same traffic class (CoS), shared BW Service Model ........ 431
Multiple services, same traffic class (CoS), independent BW Service Model436
Multiple services, same traffic class (CoS), different P-Bits Service Model .. 441
Multiple services, same traffic class (CoS), independent BW, prioritized
scheduling on the PON Service Model ........................................................ 445
Single service with prioritization of flows within the service .......................... 449
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
6
Chapter 5: Quick Start E7 GPON RSG Use Cases ............ 450
E7 GPON RSG Smart Activate Turn-up ............................................................... 450
Turning Up a GPON RSG Using Smart Activate .......................................... 450
Launching Smart Activate for a GPON RSG................................................. 451
Home Gateway GPON RSG Services Turn-up .................................................... 453
About Service Tag Actions for RG-based Services ...................................... 453
Configuring a GPON RSG in Native Mode Using Default RG Values ........... 454
Configuring a GPON RSG in Native Mode Using RG Values Defined via
Consumer Connect ....................................................................................... 463
Configuring an E7 GPON RSG in External Mode (GPON OMCI Download) 467
Creating a Custom RG Configuration File Via the EWI for External Mode
Deployments ................................................................................................. 473
Managing a Custom RG Configuration File from CMS ................................. 475
Chapter 6: Reference Information ...................................... 479
System Support Capacities .................................................................................. 480
GPON Capacities ................................................................................................... 484
Using the Cut-Through Telnet or Web Interface ................................................. 487
HPNA Services Deployment ................................................................................. 488
ONT Power Shedding ............................................................................................ 489
E7 LED Behavior .................................................................................................... 490
E7 Line Card Additional Status Descriptions...................................................... 492
Resetting an ONT .................................................................................................. 493
Restarting a SIP Remote Configuration Profile .................................................. 495
CPE Vendor-Defined Fault Codes for TR-069 ..................................................... 496
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
7
About This Guide
This Calix E7 Ethernet service access platform supports ITU G.984 Gigabit Passive Optical
Network (GPON)-based Fiber-to-the-Premises (FTTP) applications for residential and
business services.
This document describes how to configure Calix standalone E7-2, Modular Chassis, and E720 GPON services, where E7 is used to refer to the set of products in the platform.


See Calix E7 User Guide for instructions on initial turnup for the standalone E7-2,
modular chassis, and E7-20 systems.
See "Configuring Transport and Aggregation Support" in the Calix E7 User Guide for
instructions on configuring transport rings and aggregation links.
Intended Audience
This document is intended for use by network planning engineers, CO technicians, and craft
and support personnel responsible for network equipment turn-up, service configuration,
and maintenance. The procedures in this guide are of a technical nature and should only be
performed by qualified personnel. Familiarity with standard telecom and datacom
terminology and practices, as well as standards-based Ethernet technologies and conventions,
is recommended.
Related Documentation
You can access Calix product documentation from the Calix Resource Center online at
www.calix.com (https://www.calix.com/portal/site/resourcecenter/).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
8
The Calix E7 documentation set includes:
Engineering and Planning

Calix E7 Engineering and Planning Guide
This document provides high-level engineering and planning information for
building secure, reliable, resilient, and scalable Layer 2 switched Ethernet
access networks using Calix products to deliver data, voice, and video services.
It describes all aspects of Ethernet access network design—from physical
topologies to network bandwidth requirements in the context of Calix
products, describing an access network where the traffic terminates at the edge
router.

Calix Ethernet Access Networks Engineering & Planning Guide
This document provides engineering and planning information for the Calix
E7 Ethernet Service Access Platform (ESAP) and Calix E3-48C Ethernet
Service Access Node (ESAN). It describes the features and capabilities of each
system, and provides engineering guidelines to assist engineers and network
planners effectively deploy the E7 and E3-48C.
Installation




Calix E7-2 Installation Guide
Calix E7-20 Installation Guide
Calix E3-48C Installation Guide
Calix E5-48/E5-48C Installation Guide
These documents provide a general installation practice for the Calix Ethernet
service access platform, including guidance for planning, power installation,
cabling, and maintenance.
User Guide


Calix E7 User Guide
Calix E3-48C, E5-48/E5-48C R2.3 User Guide
These guides are intended for initial turnup and also show you how to set up
management access, system attributes, administrative tasks, and configure
transport and aggregation applications.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
9
Software Upgrade

Calix E7/E5-48/E3-48C System Upgrade Guide
This document describes how to perform software/firmware upgrades as well
as database backup and restore operations.

Calix E7 GPON ONT Upgrade Guide
For E7 GPON systems, this document describes how to perform upgrades for
compatible P-Series, GigaCenter, and T-Series GPON ONTs.
Application Provisioning



Calix E7 GPON Applications Guide
Calix E7-2/E5-48/E3-48C xDSL Applications Guide
Calix E7 Active Ethernet Applications Guide
These application guides show you how to provision subscriber services using
specific technologies, assuming that the system is already installed and turned
up.
Maintenance and Troubleshooting

Calix E7 Maintenance and Troubleshooting Guide
This guide includes procedures for monitoring E7 network operation, general
troubleshooting, and replacing or installing equipment.
Command Line Interface

Calix E3-48C, E5-48/E5-48C CLI Reference
This document provides a comprehensive command reference for the E-series
Command-Line Interface (CLI) and describes how to perform key system
management and operational functions from the CLI. The embedded
command-line interface (CLI) for system management access can be used over
local or remote TCP/IP connections and local console connections.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
10
Related Documentation

P-Series/T-Series ONT Software Matrix for E7 GPON

Calix P-Series ONT Model/Feature Matrix

Calix 800G GigaCenter Embedded Web Interface (EWI) User's Guide

Calix T1 Pseudowire Applications Guide

Calix C7 VoIP Services Guide

Calix Application Note: Using the ONT VoIP Configuration File

Completing Residential Gateway and SIP Configuration File Intake Forms

Calix P-Series VoIP Configuration File - Template

Calix 836GE RSG Wi-Fi Best Practices Guide

Calix GPON RF Overlay Deployment Guidelines

Calix Application Note: GPON Interface Adaptor

Calix E7 Pluggable Transceiver Module Support

CAB-12-023 - Pairing Bidirectional SFPs (to Support Single-Fiber Ethernet Links)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Chapter 1
GPON Solution
This chapter describes Gigabit Passive Optical Network (GPON) applications and the Calix
E7 GPON solution.
Topics Covered
This chapter covers the following topics:





A description of the Gigabit Passive Optical Networks (GPON) technology and standard
An overview of components comprising the E7 GPON solution
Descriptions of supported equipment used in the E7 GPON solution
Descriptions of supported services in the E7 GPON solution
An overview of Home Gateway concepts and objects
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
12
Calix E7 GPON Solution Overview
GPON overview
A Gigabit Passive Optical Network (GPON) is a point-to-multipoint fiber network as
defined in the ITU G.984 family of standards. Each subscriber is connected into the optical
network via fiber from a passive optical splitter. There are no active electronics in the
distribution network, and bandwidth is shared from the feeder to the drop.
A GPON fiber-to-the-premises (FTTP) deployment consists of the following primary
components:



OLT: The optical line terminal (OLT) provides GPON network terminations.
ONTs: The optical network terminal (ONT) provides an optical termination at the
subscriber premises, and provides subscriber interfaces (POTS, Ethernet, DS1, etc.).
ODN: The optical distribution network (ODN) provides the optical connection between
the OLT and ONTs. The ODN contains the following:

Optical fiber

Optical splitters: To passively split the PON, located in the central office, remote
terminal, outside plant, or any combination of the above. The GPON specification
allows up to 64 splits per PON.

EDFA/combiner (for RF overlay): Third-party equipment that injects the RF video
overlay signal into the PON and amplifies the signal.
E7 GPON solution
With a wire-speed Ethernet architecture supporting delivery of a full 2.5 Gbps to every
GPON port, the Calix E7 GPON cards provide capacity to meet the requirements of current
and future needs for business and residential services. Multiple E7 systems can be linked
together using industry standard 10GE SFP+ copper cables resulting in a very high-density,
high bandwidth configuration of over 2500 potential subscriber endpoints in a 10RU space
(up to 1:64 split).
Note: For information on configuring a set of Operation, Administration, and Maintenance
(OAM) functions that monitor network operation, detect and localize network faults, and
provide a measure of network performance within the Calix 760 ONT series, see
"Configuring Ethernet OAM" in the Calix E7 Maintenance and Troubleshooting Guide.
The key attributes of the E7 GPON solution are listed below:



Uses the E7 GPON cards as GPON OLTs.
Supports the full family of Calix 700-Series ONTs, including SFU, SBU, and MDU
models.
GPON technology in compliance with the ITU G.984 family of standards
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
13











2.5 Gbps (2.488 Gbps) downstream, 1.25 Gbps (1.244 Gbps) upstream GPON interfaces
GEM-based PON for efficient packet switched network services
Up to 64:1 splits per PON
Class B+ ODN (minimum 32 dB link budget) with a 20Km reach (1:32 split)
Extended reach GPON with a 40Km reach (1:8 split)
Integrated 10GE and GE transport and aggregation
Ethernet data services support, including High-speed Internet access and MEFcompliant Transparent LAN Service (TLS)
Voice services support, including ONT SIP and circuit-switched (GR-303, TR-8) services
via a Calix C7 TDM voice gateway
Multicast IPTV video services support
CATV RF video overlay: 1550 nm video overlay and 1610 nm RF return
Integrated ONT-based T1 leased line and private line services
The following diagram depicts a high level architectural view of the Calix E7 GPON FTTP
solution.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
14
GPON Network Components
A Gigabit Passive Optical Network (GPON) is a point-to-multi-point network. Each
subscriber is connected into the optical network via a passive optical splitter. There are no
active electronics in the distribution network. Bandwidth is shared from the feeder to the
drop.
E7 GPON networks have the following primary components:



OLT: The Optical Line Terminal (OLT) provides GPON network terminations. The E7
GPON cards serve as the OLT for Calix ONTs.
ONT: The Optical Network Terminal (ONT) mounts at the subscriber premises. It
terminates the PON and provides subscriber interfaces for voice, data, and video services
from the PON. The E7 GPON solution uses Calix 700/700G/700GX/700GE model
ONTs.
ODN: The Optical Distribution Network (ODN) includes all passive equipment, plus an
optional active EDFA/combiner for RF video overlay, between the GPON card and the
subscriber ONT.
The ODN contains:

Optical fiber: The E7 supports a single fiber Class C+ (2.4 GPON) ODN with a
reach of up to 40 km.
Note: The extended-reach GPON Optical Interface Module (OIM) provides up to a 40km reach with up to 8 splits, and up to 32 splits total.

Optical splitters: Passively splits the PON. The GPON specification allows up to 64
splits per PON. You can install the splitters in the central office, remote terminal,
outside plant, or any combination of the above.

EDFA/combiner: Third-party equipment that injects the analog video overlay signal
into the PON and amplifies the signal. It resides between the GPON card and the
subscriber ONT.
The ODN supports:

Supports single-fiber Class B+ (28 dB link margin) optical distribution network

Standard Reach OIM


Up to 64 passive optical splits per PON

Up to 20 km reach with 32 way split

Up to 11 km reach with 64 way split
Extended Reach OIM

Up to 32 passive optical splits per PON

Up to 40 km reach with 8 way split
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
15


GPON with one-way video overlay - three wavelengths per PON:

GPON digital downstream: 1490 nm

GPON digital upstream 1310 nm

Video overlay downstream: 1550 nm
GPON with two-way video overlay - four wavelengths per PON:

GPON digital downstream: 1490 nm

GPON digital upstream 1310 nm

Video overlay downstream: 1550 nm

Return path upstream: 1610 nm
Refer to Supported Equipment (on page 16) for a description of each component listed above.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
16
Supported GPON Equipment
E7-2 GPON-4 Line Card
Interfaces:



Four ITU G.984-compliant Gigabit Passive Optical Network (GPON) interfaces
Eight Gigabit Ethernet (GE) interfaces
Four ports of integrated 10-Gigabit Ethernet
The Calix E7-2 GPON-4 line card can be installed into one or both of the two universal slots
within a Calix E7-2 shelf. Each PON supports up to 64 Optical Network Terminations
(ONTs) for a total of 512 GPON and 16 point-to-point Ethernet subscribers per 1RU E7-2
chassis. The E7-2 GPON-4 card supports a full set of Ethernet services and network
topology protocols on the Ethernet ports and can be used interchangeably with other E7-2
line cards to create a redundant system configuration.
Note: E7-2 supports 2.5 Gbps pluggable module interfaces on the SFP ports of the GPON4 cards. The 2.5GE interfaces support equivalent functions and networking protocols as GE
and 10GE interfaces.
E7-2 GPON-4 r2 Line Card
Interfaces:



Four ITU G.984-compliant Gigabit Passive Optical Network (GPON) interfaces
Eight Gigabit Ethernet (GE) interfaces
Four ports of integrated 10-Gigabit Ethernet
This card is backward compatible with the original GPON-4 line card. In addition, it
provides C+ optics and forward error correction (FEC).
E7-2 GPON-8 Line Card
Interfaces:



Eight ITU G.984-compliant Gigabit Passive Optical Network (GPON) interfaces
Four Gigabit Ethernet (1GE/2.5GE) interfaces
Two ports of integrated 10-Gigabit Ethernet
The Calix E7-2 GPON-8 line card can be installed into one or both of the two universal slots
within a Calix E7-2 shelf. Each PON supports up to 64 Optical Network Terminations
(ONTs) for a total of 512 subscribers per card. The E7-2 GPON-8 card supports a full set of
Ethernet services and network topology protocols on the Ethernet ports and can be used
interchangeably with other E7-2 line cards to create a redundant system configuration. The
GPON-8 card supports single-fiber Class C+ (32 dB link margin) optical distribution
network and forward error correction (FEC).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
17
E7-20 GPON-4x Line Card
Interfaces:

Four ITU G.984-compliant Gigabit Passive Optical Network (GPON) interfaces
The Calix E7-20 GPON-4x service access card provides multiservice capability over four
GPON OLT ports, used to subtend up to 64 ONTs per OLT port, with a card capacity of
256 GPON ONTs. The GPON-4x card supports single-fiber Class B+ (28 dB link margin)
optical distribution network:


Standard Reach OIM

Up to 64 passive optical splits per PON

Up to 20 km reach with 32 way split

Up to 11 km reach with 64 way split
Extended Reach OIM

Up to 32 passive optical splits per PON

Up to 40 km reach with 8 way split
E7-20 GPON-8x Line Card
Interfaces:

Eight ITU G.984-compliant Gigabit Passive Optical Network (GPON) interfaces
The Calix E7-20 GPON-8x service access card provides multiservice capability over eight
GPON OLT ports, used to subtend up to 64 ONTs per OLT port, with a card capacity of
512 GPON ONTs. The GPON-8x card supports single-fiber Class C+ (32 dB link margin)
optical distribution network and forward error correction (FEC):

Maximum 64:1 split per PON
ONTs can be distributed on any PON or card in any number as long as those two limits are
not exceeded.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
18
Pluggable optics
The E7 platform supports industry standard pluggable modules for all service and network
interfaces, including ITU G.984 compliant GPON, SFP GE, XFP 10GE ports, and SFP+
10GE ports.
Note: The 10GE SFP+ port on the E7-20 SCP card does not support GE SFP modules.
See the following Calix Quick Tip bulletins on the Calix website for information on the
support for SFP modules and direct-attach cables:


Calix E7 Pluggable Transceiver Module Support
CAB-12-023 - Pairing Bidirectional SFPs (to Support Single-Fiber Ethernet Links)
Module restrictions
The following module restrictions apply:




Unless otherwise specified, SFP sockets in all Calix products accept any SFP module.
GE-12 cards (E7-2) support any Calix-keyed 1GE SFP module in the SFP sockets.
Copper SFP modules should be purchased from Calix to ensure correct operational
behavior.
The 10GE, 2.5GE, GPON OIM, and CSFP modules must always be purchased from
Calix.
Equipment Upgrades
Before configuring an ONT for a subscriber service, you must download, activate, and
commit the applicable system and ONT software, if not already done. For more information
about E7 system upgrades, refer to the following guides:


This Calix E7 Software Upgrade Guide describes how to perform software/firmware
upgrades as well as database backup and restore operations.
The Calix E7 GPON ONT Upgrade Guide describes how to perform upgrades for
compatible P-Series and T-Series GPON ONTs. This document contains a subset of the
information in the Calix E7 Software Upgrade Guide.
Calix ONTs
See the following matrices for information on the available models of Calix ONTs:



P-Series/T-Series ONT Software Matrix for E7 GPON
Calix P-Series ONT Model/Feature Matrix
Calix P-Series ONTs: Minimum Platform Software
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
19
Calix Home Gateway
The following ONTs support Calix Home Gateway: Calix 700GE , 836GE, 800G, and Tseries HGW ONTs. You can determine which ONT models support home gateway
operation by the following methods:


Using the CLI command show ont-profile from the E7 Command Line Interface, to
view the ONT port types list, where a value of "1" in the "G" column for a given model
represents support for "residential-gateway" operation.
Using CMS or the E7 embedded web interface (EWI) Navigation Tree, select ONTs,
and then in the Work Area select Profiles to view all of the profiles for the system
ONTs, where a value of "1" in the "Residential Gateway" column for a given model
represents support for "residential-gateway" operation.
700 Optical Network Terminal (ONT)
Calix 700 ONTs are available in a number of configurations:








Single Family Unit or Multi-Dwelling/Small Business Unit configurations
ONT Enclosure with a conventional splice tray
ONT Enclosure with an Opti-Tap Connectorized Fiber System from Corning
ONT Enclosure with Primary Protector Modules included, in either conventional or
Opti-Tap fiber termination systems
A number of “Enclosure-less” options dependent upon the environment where the
ONT is to be installed
A slack storage option for safely storing excess fiber optic cable behind the ONT
Enclosure
The 760GX and its variants can deliver line rate performance down to 64 byte packets on
a single GE port, specifically, 1.3 million packets per second aggregate throughput
performance.
Options to install the 700 ONT main electronics into third-party enclosures
Note: Only the Calix GX ONTs support the E7 ‘convert-mcast’ feature in multicast
profiles. Also, the 765G ONT is not supported on the E7.
Data Configuration Guidelines
When deploying Calix 700 ONTs or 800 Series RSGs, keep the following information in
mind when provisioning data services:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
20
ONT
TYPE
Data Service Configuration
Example
When configuring multiple services on a single
subscriber port, and the security settings are
such that MAC Forced-Forwarding (MACFF) is
enabled and not IP Source Verify (IPSV), STB
unicast traffic will fail upstream if the access
router DMAC is the same for both services.
That is, only one forwarding entry is created
for multiple services, resulting in the traffic not
being forward correctly upstream.
Enable IPSV for each service that exist on the same ONT Ethernet
port, forcing the ONT to create a hardware forwarding entry for
each service.
7xxGE,
8xxGE
Shaping (versus policing) is compatible with all
types of data models on the ONT; Residential
Gateway (RG), Full Bridge, or Half-Bridge.
When using shaping, it can be used on ONLY one of the data
model types.
7xxGE,
8xxGE
When applying a traffic shaper, all upstream
traffic is rate limited, regardless of service
type.
When multiple services are using different rates, shaping should
be disabled (policing in effect). However, upstream
multicast/broadcast rate limiters are still applied.
In addition, the upstream shaper enforces
QoS based on the upstream packets p-bit
settings ensuring higher priority traffic is
queued/sent accordingly.
Note: If two bridged internet services on different ports are in use,
the last bridge creation event (and its associated rates) are
remembered by the ONT.
7xxGX,
76xGX,
7xxGE
Double-tagged traffic at the ONT level does
not support security protocols.
MACFF and IP Source Verify are currently not supported with
double-tagged traffic at the ONT.
7xxGX,
76xGX,
7xxGE
Double-tagged traffic at the ONT level for
video services.
Double-tagged traffic at the ONT level is currently not supported
for video services.
7xxGX,
76xGX,
7xxGE
24-bit and 48-bit MAC Address matching is
supported by the ONT. Additional masked
values are currently not supported.
With OUI Match, 24 bit numbering is supported. With complete
MAC address filtering, 48 bit is supported.
7xxGX,
76xGX,
7xxGE
Static IP provisioning on an ONT subscriber
port.
When using STATIC IP hosting on an ONT subscriber port, if the
MAC address is not specified, you must enable MACFF
7xxGX,
76xGX,
7xxGE
Video service tag actions rules.
Mixed video service tag actions are not allowed on the same
service within a single ONT port. For example, a single subscriber
port cannot be tagged and untagged at the same time. Similar rule
applies for subscriber port VLANs.
7xxGX,
76xGX,
7xxGE
MAC Address limits
In a 1:1 (Port to VLAN) VLAN environment, the same MAC
address is allowed on separate subscriber ports on an ONT
because in this scenario, VLAN + MAC forwarding is enabled.
However, the same MAC address is not supported on multiple
ports ian N:1 ONT environment.
7xxGX,
76xGX,
7xxGE
Full-Bridge Learning without security.
If MACFF or IPSV is disabled, any attached devices must
periodically ARP to maintain the Full Bridge Learning table. If
MACFF or IPSV is enabled, learning continuously occurs as
frames ingress the Ethernet ports without the need for ARP.
7xxGE
ONT Frame Size
GE ONTs support jumbo frames of 9728 (Ethernet frame) in the
Hardware fast path. However, if any options are configured that
required slow path protocol (ARP, IGMP, and the like), frame size
is limited to 2024.
76xGX,
7xxGE
Hardware Forwarding Tables
76xGX ONTs are limited to 16 entries per subscriber port. 7xxGE
ONTs provide 32 entries per port.
7xxGE
IPV4 Rate Limiting
Rate limiting with policing occurs with valid IP Header data-lengths
only when using the meter attach vlan method with shaping is not
used. (This guideline applies to AE, only.)
7xxGE,
76xGX
or
Both services MUST have IPSV and MACFF disabled.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
21
ONT
TYPE
7xxGE
Data Service Configuration
PBit Promotion Tables
Example
There is a limit of 16 total p-bit promotions in either direction
supported by the ONT.
PBIT promotion occurs as follows:

Transparent VLAN or TLS (one per port, upstream and
downstream)

Downstream, one per VLAN

Any tag action where PBIT promotion is specified (one per tag
action)

DSCP to PBIT tag actions
74xGE
OAM support on the 74x is restricted to TLS
services only. The 74x cannot do certain OAM
loss measurement(s) for all other services.
If OAM is enabled on a 74x port, the only service supported is TLS
(no Layer-2 security). In other words, no slow path snooping
options can be enabled in the service VLAN on the ONT. Tag
actions can only be TLS type allowed.
All
ONTs do not use any form of spanning tree.
Any variation of spanning tree protocol is not supported by the
ONT to detect loops.
836GE RSG Residential Services Gateway
The Calix 836GE Residential Services Gateway (RSG) is a next generation service delivery
device that supports broadband connections into the home and manages subscriber voice,
data and video services. This high-performance services gateway integrates an auto-detect 2.5
GPON or 1Gbps Active Ethernet (AE) optical WAN interface with switching and routing
functions that manage premises network traffic at speeds up to 1Gbps.
Gateway interfaces include:




Four Gigabit Ethernet (GE) ports for IPTV video and data services
Two integrated voice lines supporting carrier grade VOIP and network-based TDM
voice circuits
Wireless networking with 802.11n Wi-Fi
USB port for future home interconnect services
Calix GigaCenter
The Calix 844G and 854G GigaCenter are the first in a family of Premises delivery platforms
optimized to extend the network demarcation inside the subscribers home. They are the first
Calix products to support carrier class Wi-Fi using 802.11ac technology, allowing all services
to be delivered over wireless including IPTV. Carrier class Wi-Fi incorporates 4x4 MultipleInput-Multiple-Output (MIMO) at 5GHz, support of the entire 5GHz band including
Dynamic Frequency Selection (DFS) channels, universal beamforming, use of 80MHz
combined channels at 5GHz, as well as software management tools and quality of service
capabilities.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
22
The 844G and 854G GigaCenters also includes a Home Gateway functionality first
introduced in Calix’ 836GE Residential Service Gateway (RSG). The 836GE supports the
802.11n standard at either 2.4GHz or 5GHz selectable. GigaCenters support dual-band
concurrent, allowing continued usage of the 2.4GHz band for data and legacy consumer
devices while supporting IPTV and high-speed data at 5GHz. The GigaCenters are designed
to meet service providers’ and end-users’ requirements for ubiquitous broadband access
throughout the residence driven by the growth of smart mobile devices and media rich
content. These Wi-Fi devices range from low bandwidth IP cameras, security sensors, smart
phones, tablets, and printers, and even includes support for bandwidth intensive, Quality Of
Service (QoS) sensitive Wi-Fi capable Set Top Boxes (STBs) and TVs. To meet these user
requirements, some of GigaCenter highlights include:
GigaCenter supports the latest 802.11ac standard for the 5GHz radio. Some basic 802.11ac
enhancements include:



Dynamic beamforming for high performance and longer reaches.
80Mhz channels for greater speeds,
QoS support allowing prioritization of Video SSID over lower priority best effort HSI
data SSIDs
For more information, see Calix 800G GigaCenter Embedded Web Interface (EWI) User's Guide.
T-Series Home Gateway for Global ETSI
The T-Series Home Gateway Units (HGUs) with the E7 platform allow for expansion for
global ETSI deployments. The T-Series HGUs are designed to work with both the BLM1500 and E7, providing you with a host of broadband deployment options.
T-Series Global ONT Introduction for global ETSI markets:

T071G (1 GE)
The T071G is a single Gigabit Ethernet port with integrated Layer 2 bridged or Layer 3
routed residential gateway functionality. The ONT is designed to support both residential
and business subscribers with multiple high-bandwidth applications such as high-speed
data, HDTV-based IPTV video, and routing/NAT services. Voice applications can be
supported using an external VoIP ATA or subtended gateway with VoIP capabilities.
Video support at Layer 2 is via multicast or unicast with integrated IGMP Snoop
functionality, with Layer 3 support of IGMP Snoop and Proxy.

T072G (4 GE + 2 POTS)
The T072G HGU ONT is a 4 GE, 2 POTS ONT with integrated Layer 2 bridged or
Layer 3 routed residential gateway functionality. The ONT is designed to support both
residential and business subscribers with multiple high-bandwidth applications such as
high-speed data, HDTV-based IPTV video, and routing and bridging features for WholeHome DVR. Voice support is via integrated FXS interfaces that support the SIP VoIP
protocol. Video support at Layer 2 is via multicast or unicast with integrated IGMP
Snoop functionality, with Layer 3 support of IGMP Snoop and Proxy.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
23
The T072G can be partially or fully provisioned as a Layer 2 bridged ONT. Each LAN
port can be individually configured and managed for Layer 2 bridged operation rather
than routed Layer 3 services. All GPON Home Gateway functions are configurable with
a RG configuration file downloadable from the E7 via OMCI.

T073G (4 GE + 2 POTS + USB + Wi-Fi)
The T073G HGU ONT is a 4 GE, 2 POTS ONT that includes 2.4 GHz Wi-Fi (IEEE
802.11 b/g/n) and USB port. The T073G with wireless interface supports the same
integrated Layer 2 bridged or Layer 3 routed residential gateway functionality as the
T072G ONT, with the added ability to support wireless services over the routed
interface. The ONT is designed to support both residential and business subscribers with
multiple high-bandwidth applications such as high-speed data, HDTV-based IPTV video,
and routing and bridging features for Whole-Home DVR. The wireless interface is
configured for 2x2 MIMO supporting data applications over the 2.4 GHz band. Voice
support is via integrated FXS interfaces that support the SIP VoIP protocol. Video
support to the LAN Gigabit Ethernet ports at Layer 2 is via multicast or unicast with
integrated IGMP Snoop functionality, with Layer 3 support of IGMP Snoop and Proxy
(multicast video is not supported over Wi-Fi)
The T073G can be partially or fully provisioned as a Layer 2 bridged ONT. Each LAN
port can be individually configured and managed for Layer 2 bridged operation rather
than for routed Layer 3 services. The wireless interface supports up to four SSIDs. All
GPON Home Gateway functions are configurable with a RG configuration file
downloadable from the E7 via OMCI.

T076G (4 GE + 2 POTS + RF)
The T076G HGU ONT is a 4 GE, 2 POTS, 1 RF ONT with integrated Layer 2 bridged
or Layer 3 routed residential gateway functionality. The ONT is operationally equivalent
to the T072G ONT with the additional of RF video overlay. The RF video supports both
analog and digital narrowcast video broadcast with forward path bandpass of 54 MHz to
870 MHz. The T076G ONT differs from the T072G ONT in that it includes power
inputs for both a 12 VDC power adaptor or option for battery backup using a UPS.

T077G (4 GE + 2 POTS + USB + Wi-Fi, RF)
The T077G HGU ONT is a 4 GE, 2 POTS, 1 RF ONT that includes 2.4 GHz Wi-Fi
(IEEE 802.11 b/g/n) and USB port. The ONT is operationally equivalent to the T073G
ONT with the additional of RF video overlay. The RF video supports both analog and
digital narrowcast video broadcast with forward path bandpass of 54 MHz to 870 MHz.
The T077G includes power inputs for both a 12 VDC power adaptor or option for
battery backup using an Uninterruptable Power Source (UPS). The ONT is equipped
with a removable fiber slack storage tray for managing excess fiber.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
24
GPON Interface Adaptor
The Calix GPON Interface Adaptor is a Gigabit Passive Optical Network (GPON) SFP
based ONT designed to be used with the Calix E7 platform. The GPON adaptor supports
residential VDSL2 services using the E3-12C and E3-48C platforms and business
applications using the E5-308 platform. The GPON Interface Adaptor is a fully functional
ONT that operate at 2.5 Gbps downstream and 1.2 Gbps upstream GPON speeds providing
a 1 Gbps Ethernet interface for respective host equipment. They are designed for use with
the Calix E7 fiber-to-the-premises (FTTP) system including E7-2 and E7-20 OLTs. See Calix
Application Note: GPON Interface Adaptor for more information.
Third-party equipment
The Calix E7 GPON solution may interface with the following third-party equipment:






Passive splitters which passively split the PON
Switches/routers for LAN/management access, Internet/ISP access, IPTV and Video
on Demand (VOD) services
Middleware and set top box for IPTV services
Central office voice switch with a GR-303 interface
EDFA/combiner which injects analog video into the PON
RF Return premises equipment connected to the ONTs
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
25
Supported GPON Services
All services other than RF video overlay are switched within the ONT and transported over
the PON as Ethernet services that are classified and placed within an operator-defined
service VLAN ID. ONT-based data services are managed in a similar fashion to the E7 GE
and 10GE Ethernet ports.
The Calix E7 system is capable of delivering the following applications and services:
Voice Services


Session Initiated Protocol (SIP) VoIP service
TDM Gateway (GR-303, TR-08) for VoIP
Data Services


1:N VLAN-per-Service
1:1 VLAN-per-Port
Video Services



IPTV / Switched Video Services
Multicast VLAN Registration (MVR)
CATV Radio Frequency (RF) video overlay
Overviews of services provisioning
See the following topics for the overviews of E7 service provisioning:
Overview: GPON L2 Data Services (on page 42)
Overview: GPON L2 IP Video Services (on page 44)
Overview: GPON L2 MVR Video Services (on page 46)
Overview: GPON Voice Services (P-Series only) (on page 59)
Overview: HGW Applications - External Mode (on page 48)
Overview: HGW Applications - Native Mode (P-Series only) (on page 54)
Overview: HGW Applications - TR-069 (on page 57)
Overview: SIP Gateway Service with Configuration File (on page 61)
Supported VLAN tagging and provisioning models
The E7 provides standards-based VLAN tagging, and Q-in-Q VLAN stacking support.
VLAN tagging was developed as a means to allow multiple networks to transparently
traverse the same physical network.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
26
VLAN-per-service provisioning model (1:N): When VLANs are provisioned to separate
traffic onto VLANs based on the type of service carried in the traffic. For example, IPTV
traffic is carried on a separate VLAN from data and voice traffic.
On ONT Ethernet ports, a single match list and service tag action specify the classification
and marking of packets from the subscriber port into the service VLAN.
VLAN-per-port provisioning model (1:1): When VLANs are provisioned as a unique
customer or port identifier, VLAN C-tags (customer tag) are utilized to create a VLAN per
customer / port association.
On ONT Ethernet ports, you can define the match list and tag action pair such that multiple
subscriber ports can reference it. This is accomplished by having a special value for the
output tag in the tag action, indicating that the value of the output tag is subscriber specific.
The customer-specific tag is contained in the Service object.
VLAN stacking or Q-in-Q provisioning model: The ability to add multiple VLAN tags
enables the following functionality:
Expands the addressable VLAN space from 4094 VLANs to over 16 million VLANs
Allows logical separation and trunking of VLANs through a network by using a VLAN tag to
group a larger range of VLAN tags together
The most common way to use VLAN stacking is by inserting two tags on the traffic. These
tags are typically referred to as the inner tag or C-tag and the outer tag or S-tag. As stated
previously, the C-tag, also known as the customer tag as it is used to uniquely identify a
customer, typically is used on a per port basis. The S-tag, also known as the service provider
tag as it is used to logically group C-tags together.
Transparent LAN services provision model: TLS can transparently trunk business traffic
across a network to other locations, typically a remote offices or secondary business location.
The traffic received from the business may be untagged, single-tagged, or double-tagged. The
E7 adds an outer tag to all frames to create a private switched LAN with two or more end
points.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Chapter 2
Home Gateway Overview
This section describes the Calix Home Gateway (HGW) components, concepts, and
application methods.
Topics Covered
This section covers the following topics:





HGW concepts
HGW services
HGW port assignments
RG management modes
HGW management interfaces
Cross-References
Overview: HGW Applications - External Mode (on page 48)
Overview: HGW Applications - Native Mode (on page 54)
Overview: HGW Applications - TR-069 (on page 57)
Overview: SIP Gateway Service with Configuration File (on page 61)
Calix 844G/854G GigaCenter Residential Services Applications Guide
Calix P-Series (836GE/700GE) Residential Services Applications Guide
T-Series ONT Operation and Maintenance Guide
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
28
How to Determine HGW ONTs
You can determine which ONT models support home gateway operation by issuing the show
ont-profile command from the E7 Command Line Interface.
A value of "1" in the "G" column of the CLI's ONT port types list, indicates that the model
represents support for "residential-gateway" operation.
You can also find this information via CMS or the Embedded Web Interface (EWI).
In the navigation tree, select ONTs, then view ALL of the displayed ONT profiles to get the
complete list of models that support the home gateway/RG function.
You can adjust the "Rows Per Page" count to view all of them at the same time.
Home Gateway Concepts
Calix Home Gateways (HGWs) logically partition an ONT into WAN and LAN IP domains,
enabling routing and local bridging of data traffic on the LAN side to concurrently support
both Layer 2 and Layer 3 services.
The logical components within an HGW are functionally similar to a standard GPON ONT
with a subtended 3rd party residential gateway (RG). That is, the ONT receives tagged traffic
from the downstream RG and sends it upstream single-tagged where the OLT may or may
not add a second tag.
The following terms are used in relation to HGWs:




LAN interface – The ports which are connected to subscriber devices. These ports are
generally unmanaged and support layer-2 switching between them.
WAN interface – The port which is connected to the access provider.
Internal interface – This is another name for the LAN interface when talking in the
context of NAT and IP address spaces. It represents an interface which is using a
private/locally scoped address.
External interface – This is another name for the WAN interface when talking in the
context of NAT. It represents an interface which is using a globally scoped address.
Note: The USB feature is not available in this release.
When an HGW is provisioned, it operates with two partitions:

Gateway partition

Local and wireless network

Home Gateway services

Management using TR-069 client
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
29

ONT partition

ONT Management

Subscriber Services (IPTV, voice, data, RF video)
HGWs can operate using a single WAN IP address with an integrated DHCP component for
dynamic IP address allocation to LAN devices. Set-top boxes, DVRs, computers, printers,
tablets and other Wi-Fi enabled appliances can access the WAN via the HGW. Having
Layer-2 bridging and Layer-3 routing provides support for Microsoft Mediaroom®, Minerva
IPTV, and whole-home DVR systems.
With HGWs that support Wi-Fi, implementing a wireless in-home network simplifies
networking and increases the number of supported devices by using the single WAN IP
address service model. Employing the Home Gateway’s embedded Point-to-Point Protocol
(PPP) and DHCP for dynamic IP address allocation allows the gateway to support multiple
Wi-Fi connected devices.
Management Options
HGW initial provisioning is done using a customer-defined RG configuration file, with the
option of on-going management via Embedded Web Interface (EWI) or the TR-069
protocol. Unlike the P-Series support of HGW, the T-Series ONTs always require the
download of an RG configuration file to set-up the routed WAN interfaces, as there is no
"Native" mode provisioning.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
30
The following options can be used to manage HGWs.
OMCI
HGWs support in-band and management and configuration of the interfaces and services
compliant to ITU-T G.984.4. The system EWI and CMS are used to provision, manage and
update the HGW services and image files.
TR-069
HGWs can be configured from an Auto Configuration Server (ACS) using the CPE WAN
Management Protocol (CWMP) described in BBF TR-069, including Consumer Connect.
HGWs comply with TR-098 and TR-104 data models. Residential Gateway (RG)
configuration files can be downloaded or uploaded from Consumer Connect or to a thirdparty ACS using TR-069.
Embedded Web Interface
HGW software includes an Embedded Web Interface (EWI) application that provides
access.
Related topics


For ONTs that support Home Gateway, see Supported GPON Equipment (on page 16) or
product release notes.
HGW ONT Management Interfaces (on page 37)
HGW Services
Calix Home Gateways (HGWs) can provide service delivery in a number of ways; for
example:



All subscriber services via a single VLAN on the RG interface.
Data services via one VLAN on the RG interface, video services via another VLAN on
the RG interface.
Data services via a VLAN on the RG interface, video services via a VLAN on the full
bridge (FB)#.
High Speed Internet
The first service VLAN (on the RG WAN interface) is required to be assigned to High Speed
Internet services. It has additional attributes which define the management mode, WAN
protocol and required configuration or credentials. The data service VLAN allows for
provisioning the following:


WAN Protocol as either DHCP, PPPoE, or Static IPoE
DHCP will boot automatically using the designated IP Host
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
31


PPPoE includes the user credentials Username and Password
Static IPoE includes the set-up parameters of assigned static IP address, subnet mask and
gateway
IPTV Video
HGWs support multicast and unicast IPTV services on either the routed/RG WAN interface
or L2 bridge ports provisioned as either Half-Bridge or Full-Bridge# mode. When the video
profile is assigned to the L2 bridge, a single IGMP Snoop function manages the multicast
flows across all Half-Bridge ports or across the Full-Bridge group. When the video profile is
assigned to the routed/RG WAN interface, it supports both IGMP Snoop and Proxy. All
modes support Multicast VLAN Registration (MVR) as part of the video profile.
HGWs receive only one copy of a multicast stream on the GPON uplink regardless of the
number of subscriber set-top boxes requesting the stream; the HGW replicates the multicast
streams on a per subscriber basis. HGWs support multicast traffic switching and routing
between Ethernet ports with up to 16 set-top boxes or media clients connected behind the
LAN ports with up to 40 service flows per ONT. HGWs manages mulicast joins and leaves,
with the support of fast leaves.
Note: IPTV requires QoS enforced by the Home Gateway model.
# Note: On the E7, T-Series ONTs do not support FB (Full-Bridge) mode. T-Series ONTs
are compatible with the E7, but not with the C7.
Voice and Fax
On HGWs, voice services are not resident on the gateway partition, but remain on the ONT
partition.
Voice services are supported as stated per HGW device datasheet and depending on the type
of OLT (C7, E7, etc.) and software version.
Note: Voice services are managed outside of the gateway partition with no connection to the
Home Gateway Profile or TR-069 provisioning.
Wireless LAN
HGWs that supports Wi-Fi can be used as Wi-Fi Access Points (APs) to create an in-home
Wireless LAN (WLAN).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
32
Home Gateway Port Assignments
This topic describes how ports are assigned to interfaces on Calix Home Gateways (HGWs).
An HGW Ethernet port can be a member of the RG (Residential Gateway) interface group,
FB (Full Bridge) interface group, or neither, allowing it to operate as a normal L2 classic port
(Half-Bridge mode).
Interface Group Assignments
Interface group
RG (Residential Gateway)
Description
The RG services are named as Gateway Services, where only four services are
supported and only one of them can have a multicast profile assignment.
Supported service-tag actions:
FB (Full Bridge) #

change-tag

add-and-change-tag
With Full-Bridge mode, traffic can pass between LAN ports within the same bridge.
With Full-Bridge mode, traffic can pass between LAN ports within the same bridge.
Support of Full-Bridge is assumed to be for video multicast services only to enable
Whole-Home DVR support, allowing communication between set-top boxes. A single
multicast VLAN can be associated to the Full-Bridge group.
The Full-Bridge interface only supports 1 service.
Supported service-tag actions:
<none> (Half Bridge)



change-tag

add-tag
Ports not associated with an RG or FB are in "Half-Bridge" mode and operate as L2
classic ports. This operation allows traffic to only pass between the WAN and LAN ports
and restricts traffic from passing between LAN ports within the same bridge.
When an 836 RSG or GigaCenter ONT is created, all ONT Ethernet ports are
assigned as members of the RG group. Ports can be removed from the RG group and
added to the FB group as needed.
When a P-Series or T-Series # ONT is created, the ONT Ethernet ports are not
members of any interface group, and can be added to an interface group as needed.
700GE ONTs reset whenever ports transition into or out of RG mode. For example,
when the first ONT Ethernet port is added to the RG group on a 700GE ONT, the
ONT resets. Similarly, when the last Ethernet port is removed from the RG group, the
ONT resets.
HGWs can support the following:



A single instance of RG/routed mode
A single instance of Full-Bridge mode # for IPTV services
Up to four instances of Half-Bridge mode for standard L2 bridged services
The use case of mixed High Speed Internet services with bandwidth metering and shaping on
the Routed WAN interface and L2 bridge ports is not supported, and Full-Bridge support is
only for video without bandwidth metering.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
33
Note: The 836 RSG always runs in RG mode. Even if all ONT Ethernet ports are removed
from the RG interface group, the Wi-Fi is still a member of the RG group, causing the ONT
to always remain in RG mode.
Note: If upon turn-up of an 836GE or GigaCenter, an IPTV client (STB) is attached to an
ONT Ethernet port that is a member of an RG interface group, it would obtain a lease from
the embedded DHCP server. Then, if the ONT Ethernet port is subsequently made a
member of an FB interface group, the STB retains the IP address.
Examples of port assignment configurations
Port Assignments
1 RG + 3 FB #
RG only
1 RG + 2 FB # + 1 HB
Description
(Typically deployed for RG HSI/Minerva IPTV services)

HSI is carried on a VLAN via the routed WAN interface

Video service is carried on a separate VLAN on the FB #

GE-2–GE-4 ports are associated with FB #

WiFi * and GE-1 port are associated with the routed WAN interface

IGMP proxy on the WAN interface is disabled

Both video and data services are carried on the same single VLAN via the routed WAN
interface

All GE ports and WiFi port * are associated with the routed WAN interface

IGMP-Proxy on the WAN interface is enabled
(Typically deployed for TLAN services)

HSI service is carried on a VLAN via the routed WAN interface

WiFi * and GE-1 port are associated with the routed WAN interface

IGMP Proxy on the WAN interface is disabled

Video service is carried on a separate VLAN on the FB #

GE-2/GE-3 ports are associated with the FB #

GE-4 port is associated with the HB with a 3rd VLAN
* For Wi-Fi enabled HGWs only.
# Note: On the E7, T-Series ONTs do not support FB (Full-Bridge) mode. T-Series ONTs
are compatible with the E7, but not with the C7.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
34
CLI examples of adding & removing ports from an interface
Interface group
CLI
RG
'G1'
FB
'F1'
How to add and remove ports
add ont-port 1/g1 to-res-gw
remove ont-port 1/g1 from-res-gw
add ont-port 1/g1 to-full-bridge
remove ont-port 1/g1 from-full-bridge
<none> Half-Bridge
'g1'
ONT template in CMS
Using CMS R12.1 or later, you can create an ONT template that defines all of the key
management aspects of a Home Gateway ONT as well as the logical assignments of physical
GE ports for the initial setup and whether the RG configuration supports Native Mode
versus External Mode. Once the template is created, you can apply it to the applicable ONT.
The template can also be shared between AE and GPON ONTs.
There is a system-default template that applies to ONTs implicitly until you specifically
change it on an ONT. Once a template is applied to an ONT, any further changes to that
template are not reflected on the ONT. Any new ONTs provisioned with the modified
template will use the new settings. You can always override the parameter values at the ONT
level. The ONT template is a CMS object, only. See the following topics for instructions on
using an ONT template in CMS:


Creating an ONT Template (on page 191)
Applying an ONT Template (on page 257)
RG Management Modes
The P-series Residential Gateway (RG) function is integrated into the RSG, so the ONT RG
interface can be managed in one of the following modes:

Native (P-series only) is the default behavior where the CMS/E7 directly provision up to
4 RG WAN interfaces. However, voice and legacy L2 services are still natively supported
for non-RG ports. In this mode, both the RG and ONT partitions are controlled by the
CMS/E7.

Native mode is the default for all P-series RG ONTs.

With the Native management mode, you can provision the following:

Create up to 4 RG WAN interfaces.

Specify the RG WAN interface protocol: IPoE DHCP, IPoE static, and PPPoE.
(WAN protocol is only configurable on the RG WAN interface associated with
the Ethernet service Data1. RG WAN interface for the Ethernet services Data2,
Data3, and Data4 are DHCP only.)

Enable IGMP on a single RG WAN interface (video service)

Enable MVR on a single RG WAN interface (video service)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
35

In the N:1 VLAN model, all RG WAN interfaces are on the same VLAN.

In the 1:1 VLAN model, each RG WAN interface is uniquely identified by a VLAN.
Typically, 1:1 VLANs are double-tagged, but, single-tagged VLANs are also
supported.
Note: T-Series ONTs do not support Native Mode as an option for the Management
Mode.

External uses an external RG configuration file that is downloaded to the ONT to fully
manage the WAN interfaces on the RG. In this mode, the CMS/E7 do not provision the
RG WAN interface. Except that the creation of an out-of-band (OOB) management
VLAN is controlled by the E7 OLT.

The RG partition is controlled by the configuration file.

The ONT partition is controlled by the E7 OLT.
Note: When management mode = External, you must set a config-file-instance value.
The T-series Home Gateway (HGW) ONTs only operate in the External mode, and
require an RG configuration file for Gateway (Layer 3) services.
Using an RG configuration file, a service provider is able to define up to four Routed
WAN interfaces supporting data, IPTV and auxiliary service VLANs as necessary. The
RG configuration can explicitly define these service VLANs along with service static
routes to bridge traffic on the LAN and wireless interfaces to the correct service VLAN.
When a configuration file is loaded on the ONT, there are three elements of the ONT
configuration that remain specific to each ONT:

Admin password

Primary SSID

Primary WPA/WPA2 key
Although a configuration file is applied to a Home Gateway system, the E7/CMS is still
used to create the ONT Ethernet service for each VLAN, where the service match list
used matches the RG WAN interface VLAN as specified in the configuration file.
Service tag actions for RG (Gateway) services
For RG specific services (as opposed to half-bridge [HB] or full-bridge[FB]), only
“Change Tag” and “Add and Change Tag” actions are supported. The concept of
provisioning this way was derived from the same topology that is observed today in
deployments that utilize external non-Calix RGs. This is especially used in scenarios
where a third-party RG is downstream of a regular GPON ONT. From a deployment
perspective, the HGW ONT then supports two logical components; a regular GPON
ONT and an RG. In this scenario, the ONT would receive tagged traffic from the
downstream RG and the ONT would either change the received tag and send it upstream
single-tagged or either change the received tag, send it upstream, and the OLT would
then add the second tag.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
36
T-series RG configuration file creation
The RG configuration file requires an intake form be submitted to Calix with the defined
configuration parameters. This results in the creation of an approved SIP configuration
file from Calix that is then transferred to a server local to the E7.
P-series RG configuration file creation
The RG configuration file must be created with the ONT embedded Web Interface
(EWI), saved, and then transferred to a server local to the E7. See Creating an RG
Configuration File (on page 194).
Use Cases for Management Modes
Native Mode
CMS, E7, and 836GE

Consumer Connect, CMS, E7, and 836GE
Service WAN VLANs are controlled by the OLT.

Default RG attributes are acceptable.

RG attribute manipulation prohibitively increases OPEX
due to manually adjusting the RG attributes or loading
the RG configuration files via the RG embedded web
interface.


RG attributes controlled through an RG configuration file
or RG profile via Consumer Connect.

Zero-touch turn-up.

Centralized visibility and control of RG features.
No centralized visibility or control of RG features.
External Mode
CMS, E7, and 836GE
Consumer Connect, CMS, E7, and 836GE

RG VLAN creation is controlled through a configuration file.

ONT partition is controlled by OLT.

Service-tag-actions and OLT transport VLANs.

Zero-touch turn-up.

RG configuration file distribution occurs over the GPON
OMCI.

RG attributes controlled through an RG configuration file
or RG profile via Consumer Connect.

No centralized visibility or control of RG features.

Centralized visibility and control of RG features.
ONT Template in CMS
Using CMS R12.1 or later, you can create an ONT template that defines all of the key
management aspects of a Home Gateway ONT as well as the logical assignments of physical
GE ports for the initial setup and whether the RG configuration supports Native Mode
versus External Mode. Once the template is created, you can apply it to the applicable ONT.
The template can also be shared between AE and GPON ONTs.
There is a system-default template that applies to ONTs implicitly until you specifically
change it on an ONT. Once a template is applied to an ONT, any further changes to that
template are not reflected on the ONT. Any new ONTs provisioned with the modified
template will use the new settings. You can always override the parameter values at the ONT
level. The ONT template is a CMS object, only. See the following topics for instructions on
using an ONT template in CMS:


Creating an ONT Template (on page 191)
Applying an ONT Template (on page 257)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
37
HGW Management Interfaces
Calix Home Gateways (HGWs) have a variety of provisioning, activation, and management
tools. Each tool offers unique features and access methods that together provide a
comprehensive set of management tools.
Note: See the Calix P-Series Home Gateway User's Guide and the Calix T-Series Operation and
Maintenance Guide (if applicable) for complete information on turning up and connecting to
HGW interfaces.
The following example graphic shows a configuration where P-Series ONTs are
automatically created on the GPON system using SmartActivate.
Management Options
The following methods can be used to manage HGWs.



RG Configuration File via OMCI
Home Gateway Embedded Web Interface (EWI), local or remote access
TR-069 and Consumer Connect Auto Configuration Server
RG Configuration File via OMCI
The HGW management model supports an automatic download of an RG configuration file.
This allows an operator to download and deploy common configuration settings across all
HGWs. The scope of HGW settings controlled by the RG configuration file depends on the
type of OLT (C7, E7, etc.).
Note: The RG configuration file download mechanism is via OMCI file transfer. Applying a
new RG configuration file will reset the RG configuration on the HGW. If a subscriber has
modified items such as SSIDs via the EWI, these changes will be lost when the new RG
configuration file is applied.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
38
Home Gateway Embedded Web Interface (EWI)
HGWs provide an easy-to-use Embedded Web Interface (EWI) that is accessed locally or
remotely using a web browser. The EWI provides access to the following functions:

Retrieving the basic ONT information, such as ONT model, CLEI number, product
serial number, and firmware version.

Configuring services and features on the ONT, such as VoIP, Wi-Fi, CWMP, security
and LAN network.

Managing the ONT, such as rebooting, and account management.
The Home Gateway interface supports two levels of access:

EWI via Local Access
The administer account provides the subscriber local access. For example, a service
technician on site with the HGW can logon to its EWI to provision and activate services.

Attach a PC to any of the RG LAN ports and allow the PC to obtain an IP address,
which will be in the 192.168.1.0/24 subnet, by default.

Launch a web browser and navigate to the following address and login:
http://192.168.1.1
username / password (836GE and GigaCenter): support / support
username / password (700GE and T-series): admin / admin
Note: Hidden service provider pages can be found at the default URL:
http://192.168.1.1/html/support/.

EWI via Remote Access
The remote management account allows the service provider to have remote access over
the WAN interface. For example, an administrator at the data center Telnets to the
HGW to enable Remote Management access to its EWI. It is important to note that the
Remote Management account interface access is disabled by default.
1. Enable the remote user interface for a specified time.
a. On the Navigation Tree, expand the ONT, and then click RG 1.
b. In the Set Remote Access Time box, enter the amount of time to enable remote
access (up to 1400 minutes/1 day), and then click Apply.
 For CLI: set ont-port <port-id> remote-access-time <minutes-value>
At this point the remote interface is accessible through the IP address of the RG
WAN interface.
2. Find the WAN interface IP address:

In the RG WAN Interface Status area, scroll to the right portion of the window
to view the IP address.

For CLI: show
ont-port <id> details
(not supported for T-Series)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
39
3. Launch a web browser and enter the WAN interface IP address, followed by the
remote access port:

P-Series example: http://10.10.200.157:8080
username / password (836GE): support / support
username / password (700GE): admin / admin

T-Series example: https:// 10.45.10.155:309
username / password: SuperAdmin / SuperAdmin
Note: The P-Series default login credentials are stored in the applied RG configuration
file, and can be modified through the EWI, Consumer-Connect (TR-069), or by loading
another RG configuration file with modifications. To modify these default values for a TSeries RG configuration file, contact Calix Technical Support for assistance. The T-Series
ONTs support RG remote access with releases E7 R2.3.20 and T-Series R4.1.38 and
above.
For complete information on connecting to HGWs, see:


P-Series Home Gateway User Guide
T-Series Operation and Maintenance Guide (if applicable)
TR-069 and Consumer Connect Auto Configuration Server
HGWs support the TR-069 standard protocol that provides an auto-configuration tool and
remote management of CPE devices and CPE Internet access devices such as modems,
routers, gateways, set-top boxes, and VoIP-phones.
Without modifying the applied RG configuration file, you can create a different management
profile that specifies specific TR-069 management objects with associated parameter values
and the ACS will update the appropriate ONT data attribute.
The TR-069 client can be configured to run in the following management modes:


In-band runs on an existing WAN interface. Typically, the path to the ACS server
utilizes an existing RG service, such as Gateway Service: 1 (HSI).
Out-of-band runs on its own WAN interface. An independent VLAN outside of the
service VLANs is provisioned on HGW ONTs to facilitate communication to the ACS
service.
Calix Consumer Connect is an Auto-Configuration Server (ACS) that uses TR-069 standard
protocol. All TR-069 compliant devices adhere to a well-defined data model that describes
common TR-98 management objects for the CPE, allowing remote configuration,
provisioning and device management.
1. CMS provisions the data service to the Routed WAN interface with Consumer
Connect ACS URL and credentials.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
40
2. CPE device is the connection initiator with the ACS and must be configured to make
contact with the ACS in the following ways:

CMS System Settings (ACS Settings)

CLI Home Gateway command settings (config acs setup)

Home Gateway Embedded Web Interface (EWI) settings
(administrative pages access only)
3. After an initial start, the HGW is discovered on the ACS using the bootstrap and
INFORM process. The ACS identifies the HGW by device type and instructs it to
upload a Service Defined RG configuration profile. The configuration is transferred
to the HGW using the HTTP protocol and re-initialized to begin services.
Once a connection between the HGW and the Consumer Connect ACS is
established, the CPE device is managed at two distinctly different levels:

Device level operations – a single HGW

Group level operations – a group of HGWs
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Chapter 3
Service Provisioning Overviews
This chapter shows overviews of provisioning sequences for various subscriber services. The
steps in the overviews are linked to supporting procedure topics.
Topics Covered
This chapter covers the following topics:



Overview: GPON L2 data services
Overview: GPON L2 video services
Overview: GPON L2 MVR video services
Note: T-series ONTs do not require any configuration files for layer-2 data services.





Overview: HGW Applications - External Mode
Overview: HGW Applications - Native mode (P-Series only)
Overview: HGW Applications - TR-069
Overview: GPON Voice services
Overview: SIP Gateway service
GPON Equipment Upgrades
Before configuring an ONT for a subscriber service, you must download, activate, and
commit the applicable system and ONT software, if not already done. For more information
about E7 system upgrades, refer to the following guides:


This Calix E7 Software Upgrade Guide describes how to perform software/firmware
upgrades as well as database backup and restore operations.
The Calix E7 GPON ONT Upgrade Guide describes how to perform upgrades for
compatible P-Series and T-Series GPON ONTs.
This document contains a subset of the information in the Calix E7 Software Upgrade
Guide.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
42
Overview: GPON L2 Data Services
This topic shows the sequence of procedures to perform when you are provisioning GPON
Layer-2 data services.
The E7 provides data interconnection between Internet service providers and subscribers via
the Calix GPON ONTs. Service profiles and service tag actions in the E7 and ONT help
provide tiered service offerings by specifying the classifying and marking of packets from the
subscriber port into the service VLAN.
The Calix E7 supports the following data service models over IP on Calix GPON ONTs.
This section describes the data service configuration process.

N:1/VLAN-per-service model: Defines broadcast domains that optimize traffic flow in
larger networks, providing many-to-one (N:1) subscriber-to-service connectivity. The
traffic frames for each type of service is assigned a unique VLAN ID (tag). An additional
tag can be added to limit the size of a group for improved reliability. A service carried on
an N:1 VLAN applies to multiple subscriber ports, allowing a single match list and tag
action to be used to denote the service.
Note: If using a N:1 VLAN model for services, Calix recommends enabling MAC
Forced Forwarding (MAC FF) and IP Source Verify (IPSV) when creating the VLAN,
where appropriate. The VLAN Per Service model is susceptible to MAC spoofing unless
MACFF and IPSV are enabled.

1:1/VLAN-per-port model: (Calix recommended model) Breaks large LANs into
smaller parts, providing one-to-one (1:1) subscriber-to-service connectivity. The traffic
frames from each subscriber port is assigned a unique VLAN ID (tag). The tag is applied
to a frame before the traffic is aggregated for transport. An additional tag can also be
added to group subscriber ports in logical categories.
A service carried on a 1:1 VLAN is the same for each subscriber, except the customer tag
is unique per subscriber. You can define the match list and tag action pair such that
multiple subscriber ports can reference it. This is accomplished by assigning an attribute
for the output tag in the tag action that indicates the value of the output tag is subscriber
specific. The customer specific tag is included in the service definition when provisioning
the service.
Note: T-series ONTs do not require any configuration files for layer-2 data services.
For guidance in filling in the provisioning forms necessary to configure data services, see:

Example Data Services Provisioning (on page 350)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
43
To configure L2 data services
Step 1. Configure the network uplinks for GPON services.
E7 Ethernet ports (on page 67)
Ethernet port interfaces (on page 73)
Service VLANs (on page 86)
Calix recommends using a 1:1/VLAN-per-port model, however when using N:1/VLAN-per-service model, enable MAC Forced
Forwarding (MAC FF) and IP Source Verify at the time of initial turnup.
VLAN memberships (on page 107)
Uplink interface (or ERPS domain, if the uplink resides on a different shelf) must be added to the VLAN membership.
Step 2. Create the necessary system profiles that support GPON applications.
Rules to classify traffic (on page 116)

Service match list (on page 127)

Service tag action (on page 131)

PON upstream CoS (on page 124)
(not supported for the P-series GX ONTs)
Profiles for data services (on page 166)

Bandwidth profile (on page 167)

Ethernet Security Profile (on page 188)
Step 3. Configure the PON.
GPON port (on page 232)
Create an ONT (on page 244)
Add PON US CoS Profiles (on page 256)
Configure the ONT Ethernet port (on page 257)
Specify security profile, and if necessary for HGW ONT, assign port to L2 interface (none)
Step 4. Configure the data service.
Creating an L2 Data Service (on page 271)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
44
Overview: GPON L2 IP Video Services
This topic shows the sequence of procedures to perform when you are provisioning GPON
Layer-2 IP video services.
Note: T-series ONTs do not require any configuration files for layer-2 data services.
For guidance in filling in the provisioning forms necessary to configure video services, see:


Example Video Services Provisioning (on page 358)
Example MVR Video Services Provisioning (on page 366)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
45
To configure L2 video services
Step 1. Configure the network uplinks for GPON services.
E7 Ethernet ports (on page 67)
Ethernet port interfaces (on page 73)
Service VLANs (on page 86)
For video service VLANs, enable IGMP snoop and if set to proxy, optionally create and reference an IGMP profile.
VLAN memberships (on page 107)
Uplink interface (or ERPS domain, if the uplink resides on a different shelf) must be added to the VLAN membership.
Step 2. Create the necessary system profiles that support GPON applications.
Rules to classify traffic (on page 116)

Service match list (on page 127)

Service tag action (on page 131)

PON upstream CoS (on page 124)
(not supported for the P-series GX ONTs)
Profiles for video services (on page 166)

Bandwidth profile (on page 167)

Multicast profile (on page 177)

Ethernet Security Profile (on page 188) (optional)
Step 3. Configure the PON.

GPON port (on page 232)

Create an ONT (on page 244)

Add PON US CoS Profiles (on page 256)

Configure the ONT Ethernet port for service (on page 257)
Specify security profile, and if necessary for HGW ONT, assign port to L2 interface
Step 4. Configure the video service.
Table view

Creating L2 Video Service with Form View (on page 289)
Form view

Creating L2 Video Service with Table View (on page 292)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
46
Overview: GPON L2 MVR Video Service
This topic shows the sequence of procedures to perform when you are provisioning GPON
Layer-2 IP video services, using the Multicast VLAN Registration (MVR) distribution of
multicast traffic.
Multicast VLAN Registration (MVR) is used at the ONT to merge the common multicast
VLAN content into the subscriber’s untagged service on the ONT User-Network Interface
(UNI). The E7 MVR implementation allows up to 4 independent multicast VLANs to be
merged into the subscriber’s unicast service.
Note: Calix recommends that an MVR VLAN and profile be used for all multicast IPTV
applications to move the multicast traffic out of the "video" VLAN, where the video VLAN
is assumed to have all of the middleware traffic, STB DHCP traffic, and so on. Typically, the
video VLAN will be more susceptible to accidental or malicious traffic, whereas, MVR pulls
the multicast traffic out, keeping the VLAN exclusively for IGMP signaling and multicast
streams.
Note: T-series ONTs do not require any configuration files for layer-2 data services.
For guidance in filling in the provisioning forms necessary to configure video services, see:


Example Video Services Provisioning (on page 358)
Example MVR Video Services Provisioning (on page 366)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
47
To configure L2 MVR video services
Step 1. Configure the network uplinks for GPON services.
E7 Ethernet ports (on page 67)
Ethernet port interfaces (on page 73)
Service VLANs (on page 86)

Create a video unicast VLAN with IGMP snoop = flood.

Create a video multicast VLAN with IGMP snoop = proxy and optionally create and reference an IGMP profile.
VLAN memberships (on page 107)
Uplink interface (or ERPS domain, if the uplink resides on a different shelf) must be added to the VLAN membership.
Step 2. Create the necessary system profiles that support GPON applications.
Rules to classify traffic (on page 116)

Service match list (on page 127)
Add tagged-rule, match video unicast VLAN, P-bit any.

Service tag action (on page 131)
Use match list unicast VLAN, change-tag action to unicast VLAN ID, use P-bit = 4.

PON upstream CoS (on page 124)
(not supported for the P-series GX ONTs)
Profiles for video services (on page 166)

Bandwidth profile (on page 167)

MVR profile (on page 178)
Add the video multicast VLAN to the MVR profile.

Multicast profile (on page 177)
Add the MVR profile to the multicast profile.

Ethernet Security Profile (on page 188) (optional)
Step 3. Configure the PON.
GPON port (on page 232)
Create an ONT (on page 244)
Add PON US CoS Profiles (on page 256)
Configure the ONT Ethernet port for service (on page 257)
Specify security profile, and if necessary for HGW ONT, assign port to L2 interface
Step 4. Configure the video service.
Table view

Create a video service on the ONT Ethernet port (on page 289)
Form view

Add a video service to an ONT Ethernet port (on page 292)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
48
Overview: HGW Applications - External Mode
The Home Gateway applications are provisioned in a similar sequence to other GPON
services, configuring the network uplinks, creating service-related profiles, and then
configuring subscriber services. However, you also need to define all of the key management
aspects of a Home Gateway ONT as well as the logical assignments of physical GE ports for
the initial setup.
This topic describes the sequence of procedures for configuring Home Gateway services in a
GPON system based on using the OMCI download of an RG configuration file for
configuring Layer-3 RG.

T-series ONTs use an RG configuration file that requires an intake form be submitted
to Calix with the defined configuration parameters. This results in the creation of an
approved RG configuration file from Calix that is then transferred to a server local to the
E7.
The T-series HGU ONTs always require an RG configuration file to set-up the routed
WAN interfaces.

P-series ONTs use an RG configuration file that has been created with the ONT
embedded Web Interface (EWI), saved, and then transferred to server local to the E7.
The P-series also has a default Native mode where the CMS/E7 directly provision up to
4 RG WAN interfaces.
Note: The CMS management model is required to designate a specific RG configuration file
instance to download on a per ONT basis. The service provider can administer eight
different RG configuration files on the E7.
Note: The ONT must be reset to factory default values before downloading new
configuration files. This can be accomplished by either pressing and holding the reset button
for 20 seconds or using the EWI.
T-Series ONTs will reset to factory default settings during the "retrieve ONT configuration
file" step if a prior non-default configuration file is present in the ONT. Perform the "apply
ONT configuration file" step as soon as possible after the retrieve step to minimize service
disruptions.
Provisioning partitions
When an ONT is configured for external mode, the E7 does not provision the RG WAN
interface on the ONT(with the exception of the out-of-band TR-069 management mode).
The sole responsibility for configuration of an ONT in external mode is completely
dependent on the RG configuration file.


The RG partition is controlled by the configuration file.
The ONT partition is controlled by the E7 OLT.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
49
When a configuration file is loaded on the ONT, there are three elements of the ONT
configuration that remain specific to each ONT:



Admin password
Primary SSID
Primary WPA/WPA2 key
Note: Although a configuration file is applied to a Home Gateway system, the E7/CMS is
still used to create the ONT Ethernet service for each VLAN, where the service match list
used matches the RG WAN interface VLAN as specified in the configuration file.
Using an RG configuration file, a service provider is able to define up to four Routed WAN
interfaces supporting data, IPTV and auxiliary service VLANs as necessary. The RG
configuration can explicitly define these service VLANs along with service static routes to
bridge traffic on the LAN and wireless interfaces to the correct service VLAN.
HGW port assignments
Home Gateway ONT Ethernet ports get assigned to an Residential Gateway (RG) 'G1' in
CLI, Full-Bridge (FB) 'F1' in CLI, or not a member of either, allowing it to operate as a
normal L2 classic port (Half-Bridge mode).
Residential Gateway (RG) Mode
The RG services are named as Gateway Services, where only four services are supported with
only one of them can have a multicast profile assignment. The ONT RG interface supports
up to 4 services.
Full-Bridge (FB) Mode
(P-series only) With Full-Bridge mode, traffic can pass between LAN ports within the same
bridge.
Support of Full-Bridge is assumed to be for video multicast services only to enable WholeHome DVR support, allowing communication between set-top boxes. A single multicast
VLAN can be associated to the Full-Bridge group. Applications that require Full-Bridge
support of IPTV enabled devices along with media-clients with a single IP Host supporting
data and unicast applications requires an auxiliary switch be installed behind the LAN port
and continued support of Half-Bridge. The ONT Full-Bridge interface only supports 1
service.
Half-Bridge (HB or Classic) Mode
In Half-Bridge mode, the port operates as a normal L2 classic port. This operation allows
traffic to only pass between the WAN and LAN ports and restricts traffic from passing
between LAN ports within the same bridge.
For example you can assign ports in the following configurations:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
50
Port Assignments
1 RG + 3 FB
RG only
ONT
700GE/836GE
700GE/836GE/T-Series
1 RG + 2 FB + 1 HB
700GE/836GE
Description
Typically deployed for RG HIS/Minerva IPTV services)

HSI is carried on a VLAN via the routed WAN interface

Video service is carried on a separate VLAN on the FB

GE-2–GE-4 ports are associated with FB

WiFi (836GE only) and GE-1 port are associated with
the routed WAN interface

IGMP proxy on the WAN interface is disabled

Both video and data services are carried on the same
single VLAN via the routed WAN interface

All GE ports and WiFi port (where applicable) are
associated with the routed WAN interface

IGMP-Proxy on the WAN interface is enabled
(Typically deployed for TLAN services)

HSI service is carried on a VLAN via the routed WAN
interface

WiFi (836GE only) and GE-1 port are associated with
the routed WAN interface

IGMP Proxy on the WAN interface is disabled

Video service is carried on a separate VLAN on the FB

GE-2/GE-3 ports are associated with the FB

GE-4 port is associated with the HB with a 3rd VLAN
Example of Home Gateway services provisioning
For guidance in filling in the provisioning forms necessary to configure HGW service is
external mode, see:

Example: HGW Service - P-Series External Mode (on page 380)
Configuration considerations





From a CMS/E7 perspective, none of the “Native RG Management” options are
available for ONTs in this mode.
The RG portion of the ONT is completely managed by the configuration file, including
the WAN interfaces and everything related. In particular, the configuration file configures
the RG with one or more VLANs on the GPON WAN.
The CMS/E7 is still used for creating ONT Ethernet services, such as creating and
applying service-tag actions, bandwidth profiles, and multicast profiles when adding the
service to the RG. The service-match list and service-tag must match the RG WAN
interface VLAN, as specified in the configuration file.
All services on the ONT RG interface must be deleted before you can put the ONT in
External mode.
The ONT must be reset to factory default values before downloading new configuration
files. This can be accomplished by either pressing and holding the reset button for 20
seconds or using the EWI. T-Series ONTs will reset to factory default settings during the
"retrieve ONT configuration file" step if a prior non-default configuration file is present
in the ONT. Perform the "apply ONT configuration file" step as soon as possible after
the retrieve step to minimize service disruptions.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
51

The E7 supports multiple instances for RG configuration files. Instances 17 through 24
are used exclusively for RG and can be specified either by the instance number alone or
by "rg-<1 through 8>"
rg-1
rg-2
rg-3
rg-4
rg-5
rg-6
rg-7
rg-8









Instance for RG (17)
Instance for RG (18)
Instance for RG (19)
Instance for RG (20)
Instance for RG (21)
Instance for RG (22)
Instance for RG (23)
Instance for RG (24)
An RG configuration file of a particular instance will be downloaded to ONTs with the
following conditions:

matching vendor, model and product code

configured in external mode

reference the particular RG configuration file instance
An RG configuration file defines 1-4 RG WAN interfaces, each with a unique VLAN.
When an RG configuration file is applied to an ONT, the ONT resets.
The configuration file management mode is supported on GPON only, not AE.
Both N:1 and 1:1 VLANs models are supported. Since the same configuration file will be
downloaded to each ONT, the OMCI is responsible for changing the VLAN on each
individual ONT.
In external configuration file management mode, multiple Ethernet services can be
created on the RG interface, each on a different VLAN.
When management mode = External, you must set a config-file-instance value. The Tseries Home Gateway (HGW) ONTs only operate in the External mode, and require an
RG configuration file for Gateway (Layer 3) services.
At most, one service is allowed to have an multicast-profile.
MVR video is supported.
Mediaroom network and service configuration
The following network and service models are representative of two typical Mediaroom
deployments with a Residential Gateway (RG).
Residential Gateway with
Untagged Traffic
Residential Gateway with
VLAN-tagged Traffic

The E7 sends all traffic to the RG and receives
all traffic from the RG as untagged traffic.

The E7 sends all traffic to the RG and receives all traffic
from the RG as VLAN-tagged traffic.

Toward the RG, the E7 merges the multicast
VLAN(s) traffic into the untagged unicast
subscriber traffic.

Toward the RG, the E7 merges the multicast VLAN(s)
traffic into the default unicast video VLAN.

When receiving traffic from the RG, the E7
snoops the untagged traffic for IGMP messages,
extracting those messages and sending them
upstream (as needed) within the multicast VLAN.

When receiving the video VLAN from the RG, the E7
snoops the traffic for IGMP messages, extracting those
messages and sending them upstream (as needed) within
the multicast VLAN.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
52
Residential Gateway with
Untagged Traffic

Upstream, all other traffic not part of the multicast
service is tagged with the subscriber’s Q-in-Q
tags or with the per-service single VLAN tag.
Residential Gateway with
VLAN-tagged Traffic

The E7 performs a change-tag tag action to map the RGcommon HSI and Video VLANs into provider managed
VLANs. The E7 can support Q-in-Q subscriber VLAN
models using an “add-outer, change-inner” tag action.
Residential Gateway with untagged traffic


Downstream untagged traffic includes VOD, ICC, and Control traffic flow downstream
within the E7 transport/access network with prioritization and congestion management
based on P-bits. Within the GPON subsystem, only the frames with P-bit=0 (HSI traffic)
match the provisioned service and are subject to the Bandwidth Profile.
Upstream untagged traffic includes the nominal Mediaroom control traffic that is part of
the HSI bandwidth meter. The upstream PIR rate in the subscriber’s bandwidth profile
can be increased by 128 Kbps to accommodate occasional bursts of Mediaoom control
traffic.
Residential Gateway with VLAN-tagged traffic
The ONT is configured with multiple unicast VLANs (for example, HSI and video) in
addition to the multicast VLAN. The multicast traffic is merged into the video VLAN using
MVR.
Procedure Assumptions
The following procedure assumes the following conditions:

The E7 unit and ONT have been upgraded to the latest software version. If necessary,
see:


Calix E7 Software Upgrade Guide
The RG configuration file is created and transferred to a server local to the E7. If
necessary, see:

Submitting a T-Series Configuration Parameter Definition Form

Creating a P-series RG Configuration File (on page 194)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
53
To configure HGW applications using an RG
configuration file via GPON OMCI
Step 1. Configure the network uplinks for GPON services.
E7 Ethernet ports (on page 67)
Ethernet port interfaces (on page 73)
Service VLANs (on page 86)
For video service VLANs, enable IGMP snoop and if set to proxy, create and reference an IGMP profile that specifies a Proxy
IP Address.
VLAN memberships (on page 107)
Uplink interface (or ERPS domain, if the uplink resides on a different shelf) must be added to the VLAN membership.
Step 2. Create the necessary system profiles that support GPON applications.
Rules to classify traffic (on page 116)

Service match list (on page 127)

Service tag action (on page 131)
(one for each type of service)

PON upstream CoS (on page 124)
(not supported for the P-series GX ONTs)
Profiles for video and data services (on page 166)

Bandwidth profile (on page 167)
(one for each type of service)

Multicast profile (on page 177) (for video services)
Note: Multicast maps are not supported for RG-based video services.

Ethernet Security Profile (on page 188) (optional)

Mapping Layer-3 Priority Values to P-Bits (on page 157) (optional)

ONT Template (on page 191)
Define all of the key management aspects of a Home Gateway ONT as well as the External management mode, and
logical assignments of physical GE ports for the initial setup.
Step 3. Configure the PON.
GPON port (on page 232)
Create an ONT (on page 244)
Apply ONT Template (on page 257)
Retrieve and Apply RG Configuration File (on page 237)
(with same file instance as specified in the ONT template)
Step 4. Configure the Gateway service.
Form view

Create data and video gateway service (on page 275)
Table view

Create a video gateway service (on page 295)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
54
Overview: HGW Applications - Native Mode (PSeries Only)
This topic shows the sequence of procedures for configuring Home Gateway Services on an
E7 with a Calix P-series or GigaCenter ONT in the default Native Mode, where the
CMS/E7 directly provision up to 4 RG WAN interfaces. This mode is limited to a single
VLAN (service) on the RG WAN interface. However, voice and legacy L2 services are still
natively supported for non-RG ports.
Note: T-Series ONTs do not support Native Mode as an option for the Management Mode.
For guidance in filling in the provisioning forms necessary to configure services, see:

Overview: HGW Service - P-Series Native Mode (on page 413)
Configuration guidelines



When an 836 RSG ONT is created on the E7, all ONT Ethernet ports are assigned as
members of the RG port. Ports can be removed from the RG group, and possibly added
to the FB interface group.
When a 700GE ONT is created on the E7, the ONT Ethernet ports are not a member of
the RG or FB interface group, and can be added to either the RG or FB interface group.
The 700GE resets whenever it transitions into or out of RG mode. For example, when
the first ONT Ethernet port is added to the RG group on a 700GE ONT, the ONT
resets. Similarly, when the last Ethernet port is removed from the RG group, the ONT
resets.
E7 native mode provisioning allows the E7 to directly provision up to 4 RG WAN
interfaces, without the need for an ACS or RG external configuration file. With the
native provisioning mode, you can do the following:

Create up to 4 RG WAN interfaces. However, a 5th RG WAN interface can be
created for the sole purpose of OOB management/TR69 access, if desired.

Specify the RG WAN interface protocol:

IPoE DHCP

IPoE static

PPPoE
Note: WAN protocol is only selectable on the RG WAN interface associated with
the Ethernet service Data1. The RG WAN interfaces for Ethernet service Data 2-4
are DHCP only.


Optionally enable IGMP on a single RG WAN interface (for example, video service).

Optionally enable MVR on a single RG WAN interface (for example, video service).
For RG specific services (not HB or FB), only “Change Tag” and “Add and Change
Tag” are supported.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
55


For RG specific services (not HB or FB), multicast maps are not supported for RG based
video services.
In Native management mode, only one Ethernet service can be created on the RG
interface.
Mediaroom network and service configuration
The following network and service models are representative of two typical Mediaroom
deployments with a Residential Gateway (RG).
Residential Gateway with
Untagged Traffic
Residential Gateway with
VLAN-tagged Traffic

The E7 sends all traffic to the RG and receives
all traffic from the RG as untagged traffic.

The E7 sends all traffic to the RG and receives all traffic
from the RG as VLAN-tagged traffic.

Toward the RG, the E7 merges the multicast
VLAN(s) traffic into the untagged unicast
subscriber traffic.

Toward the RG, the E7 merges the multicast VLAN(s)
traffic into the default unicast video VLAN.

When receiving traffic from the RG, the E7
snoops the untagged traffic for IGMP messages,
extracting those messages and sending them
upstream (as needed) within the multicast VLAN.

When receiving the video VLAN from the RG, the E7
snoops the traffic for IGMP messages, extracting those
messages and sending them upstream (as needed) within
the multicast VLAN.

Upstream, all other traffic not part of the multicast
service is tagged with the subscriber’s Q-in-Q
tags or with the per-service single VLAN tag.

The E7 performs a change-tag tag action to map the RGcommon HSI and Video VLANs into provider managed
VLANs. The E7 can support Q-in-Q subscriber VLAN
models using an “add-outer, change-inner” tag action.
Residential Gateway with untagged traffic


Downstream: VOD, ICC, and Control traffic flow downstream within the E7
transport/access network with prioritization and congestion management based on Pbits. Within the GPON subsystem, only the frames with P-bit=0 (HSI traffic) match the
provisioned service and are subject to the Bandwidth Profile.
Upstream: The nominal Mediaroom control traffic is part of the HSI bandwidth meter.
The upstream PIR rate in the subscriber’s bandwidth profile can be increased by 128
Kbps to accommodate occasional bursts of Mediaroom control traffic.
Residential Gateway with VLAN-tagged traffic
The ONT is configured with multiple unicast VLANs (for example, HSI and video) in
addition to the multicast VLAN. The multicast traffic is merged into the video VLAN using
MVR.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
56
To configure HGW applications with P-series in
native mode
Step 1. Configure the network uplinks for GPON services.
E7 Ethernet ports (on page 67)
Ethernet port interfaces (on page 73)
Service VLANs (on page 86)
For video service VLANs, enable IGMP snoop and if set to proxy, optionally create and reference an IGMP profile.
The E7 Management VLAN needs to have a VLAN ID that is unique and different from any RG service VLAN, including the RG
management profile VLAN used for TR-069.
VLAN memberships (on page 107)
Uplink interface (or ERPS domain, if the uplink resides on a different shelf) must be added to the VLAN membership.
Step 2. Create the necessary system profiles that support GPON applications.
Rules to classify traffic (on page 116)

Service match list (on page 127)

Service tag action (on page 131)
(one for each type of service)

PON upstream CoS (on page 124)
(not supported for the P-series GX ONTs)
Profiles for video and services (on page 166)

Bandwidth profile (on page 167)
(one for each type of service)

Multicast profile (on page 177) (for video services)

Ethernet Security Profile (on page 188)

Mapping Layer-3 Priority Values to P-Bits (on page 157)

ONT Template (on page 191)
(set management mode = native, and select WAN protocol)
Step 3. Configure the PON.
GPON port (on page 232)
Create an ONT (on page 244)
Apply ONT Template (on page 257)
Define all of the key management aspects of a Home Gateway ONT including the Native management mode, WAN protocol,
and logical assignments of physical GE ports for the initial setup.
Step 4. Configure the Gateway service.
Table view

Create a video gateway service (on page 289)
Form view

Create data and video gateway service (on page 275)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
57
Overview: HGW Applications - TR-069
This topic describes the sequence of procedures for using Consumer Connect in conjunction
with an E7 GPON deployment. The overview in this topic assumes that services are
provisioned on the 836GE or T-series, as described in Overview: HGW Applications - External
Mode (on page 48).
Note: This overview process applies to the 836GE and T-Series HGW models only.
Calix Consumer Connect is an Auto-Configuration Server (ACS) that uses TR-069 standard
protocol for remote management of CPE devices including the Calix Residential Services
Gateway. All TR-069 compliant devices adhere to a well-defined data model that describes
common TR-98 management objects for the CPE. Using the TR-069 protocol, Consumer
Connect provides remote configuration, provisioning and device management.
When the system is configured for TR-069 management, the RG TR-069 client
communicates with an Auto-Configuration Servers (ACS). For example, without modifying
the applied external configuration file, you can create an RG management profile that
specifies a TR-98 management object with associated parameter value that the ACS sends to
the ONT, either when the ONT comes online and checks in with the ACS, or on a
scheduled basis.
For guidance in filling in the provisioning forms necessary to configure services, see:

Example: HGW Service - TR-069 (on page 422)
Procedure Assumptions
The following procedure assumes the following conditions:

The E7 unit and ONT have been upgraded to the latest software version. If necessary,
see:



Calix E7 Software Upgrade Guide
A Consumer Connect (Calix hosted cloud-based SaaS) server is configured
You have defined a configuration profile from Consumer Connect (CC) with the desired
RG objects, parameters, and attributes (refer to the Consumer Connect Administrator User
Guide for instructions)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
58
To configure an HGW application using TR-069
Step 1. Configure the gateway services as described.
Overview: HGW Applications - External Mode (on page 48)
Step 2. Create an RG Management Profile to specify the location of the CC server.
RG management profile (on page 198)
Step 3. Configure the RG Interface to specify the RG management profile.
ONT Residential Gateway Interface (on page 262)
Step 4. Log in to Consumer Connect Administrator.
Login to the Consumer Connect (CC) Administrator, and then wait for the ONT to complete the check-in process. You can
observe that the WAN address used to reach out to the ACs server is the interface you specified. (Refer to the following for
instructions:

Compass Consumer Connect Administrator User's Guide

Calix Quick Tip QT-14-001: Home Gateway Setup via Consumer Connect
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
59
Overview: GPON Voice Services
This topic describes the sequence of procedures for configuring the E7 and P-series GPON
ONTs voice services. The P-series support these methods for providing GPON voice
services: SIP, TDM gateway, H.248 gateway, and MGCP gateway options.
This overview does not describe the SIP provisioning process, see:

Overview: SIP Gateway Service with Configuration File (on page 61)
For guidance in filling in the provisioning forms necessary to configure data services, see:

Example Voice Services Provisioning (on page 373)
Note: The T-series GPON ONTs only support SIP Gateway voice service.



A SIP agent/IAD function on Calix 700 ONTs converts voice signals on its POTS ports
into packetized format.
The SIP service option operates as a traditional VoIP offering, registering with a SIP
softswitch.
The TDM gateway option interoperates with a C7 or B6-640 (for MGCP) voice gateway,
which converts VoIP traffic back to TDM format for exchange on the PSTN.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
60
To configure GPON voice services for P-series
ONTs
Step 1. Configure the network uplinks for GPON services.
E7 Ethernet ports (on page 67)
Ethernet port interfaces (on page 73)
Service VLANs (on page 86)
The VLAN assignment must be different between the VoIP IP host and the subscriber port. Sharing VLANs between a
subscriber port and a VoIP IP host is not supported.
VLAN memberships (on page 107)
Uplink interface (or ERPS domain, if the uplink resides on a different shelf) must be added to the VLAN membership.
Step 2. Create the necessary system profiles that support GPON applications.
Rules to classify traffic (on page 116)

Service match list (on page 127)

Service tag action (on page 131)
Profiles for voice services (on page 201)

IP Host (on page 202)
(Reference a service tag action that indicates the voice service VLAN)

Create a TDM gateway profile (on page 215)

Create a TDM service group (on page 216)

Create an H.248 gateway profile (on page 217)

Create an MGCP gateway profile (on page 219)
The Calix Application Note: Using the ONT VoIP Configuration File describes how to use the Calix P-Series TFTP VoIP
configuration file to configure Voice over IP (VoIP) services on Calix 700 ONTs for Calix C7 and E7 GPON applications.
Step 3. Configure the PON.
GPON port (on page 232)
Create an ONT (on page 244)
Step 4. Configure the voice service.

Create a TDM gateway service (on page 317)

Create an H.248 voice service (on page 322)

Create an MGCP voice service (on page 326)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
61
Overview: SIP Gateway Service with
Configuration File
This topic shows the sequence of procedures for configuring SIP Gateway service in a
GPON system that is based on using the OMCI download of a SIP configuration file.

T-series ONTs use a SIP configuration file that requires an intake form be submitted to
Calix with the defined configuration parameters. This results in the creation of an
approved SIP configuration file from Calix that is then transferred to a server local to the
E7.
The T-series HGU ONTs always require a SIP configuration file to add a voice service.

P-series ONTs can use a SIP configuration file that has been created based on the Calix
VoIP template and sample file available with Calix P-Series VoIP Configuration File Template (version 1.20; for Calix 700 ONTs), and then transferred to server local to the E7.
Note: The P-series can also omit the SIP configuration file and base the service
provisioning exclusively on the E7 SIP Gateway Profile.
The Calix Application Note: Using the ONT VoIP Configuration File describes how to use the
following:



Calix T-Series XML VoIP configuration file (OMCI) to support the SIP Gateway per-line
VoIP provisioning method.
Calix P-Series FTP VoIP configuration file (OMCI) to support the SIP Gateway per-line
VoIP provisioning method.
Calix P-Series TFTP VoIP configuration file to configure Voice over IP (VoIP) services
on Calix 700 ONTs for Calix C7 and E7 GPON applications or Active Ethernet (AE)
operation (such as on E7 or B6 Ethernet OLTs).
The GigaCenter ONTs do not support the method of remote TFTP download of SIP
configuration. If you want to use a legacy SIP configuration file for voice provisioning on
GigaCenter ONTs, use the OMCI download of the SIP configuration file.
Note: The ONT must be reset to factory default values before downloading new
configuration files. This can be accomplished by either pressing and holding the reset button
for 20 seconds or using the EWI. T-Series ONTs will reset to factory default settings during
the "retrieve ONT configuration file" step if a prior non-default configuration file is present
in the ONT. Perform the "apply ONT configuration file" step as soon as possible after the
retrieve step to minimize service disruptions.
SIP Remote Services Support for P-Series ONTs
For E7s running R2.3 and higher, Calix recommends that you convert lines over from the
SIP Remote Profile to the SIP Gateway Profile, eliminating the need for the remote SIP
VoIP configuration file downloaded via TFTP. Instead, you can use a reduced configuration
file that resides on the E7, and does not overlap any of the configuration parameters that are
in the SIP Gateway Profile and SIP service objects.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
62
For compatibility to SIP services previously provisioned with software releases R2.2 and
lower, there is continued support for services using a remote SIP configuration file. For
example, if you have an existing remote SIP profile and you want it to be applied to a service,
the SIP gateway profile has a setting that can enable the remote SIP configuration file and
override the duplicate settings that are specified in the SIP gateway profile.
The E7 and P-series GPON ONTs support these methods for providing GPON voice
services: SIP gateway, TDM gateway, H.248 gateway, and MGCP gateway options.
For guidance in filling in the provisioning forms necessary to configure data services, see:

Example: SIP GW Voice Services Provisioning (on page 373)
Note: SIP Gateway is the only voice service supported on the T-series GPON ONTs.
IP Hosts For SIP Voice Services
Each voice service option requires an IP host definition object that specifies an IP host
address for VoIP. (The definition references a tag action that specifies the classifying and
marking of packets from the subscriber port into the service VLAN.) Additionally, the SIP
IP Host requires that the configuration-file instance is specified. This instance value must
match the value given when retrieving the SIP configuration file and applying it to the E7.
Instances 9 through 16 are used exclusively for VoIP files and can be specified either by
instance number alone or by "voip-<1 through 8>"
voip-1
voip-2
voip-3
voip-4
voip-5
voip-6
voip-7
voip-8
Instance for VoIP (9)
Instance for VoIP (10)
Instance for VoIP (11)
Instance for VoIP (12)
Instance for VoIP (13)
Instance for VoIP (14)
Instance for VoIP (15)
Instance for VoIP (16)
Procedure Assumptions
The following procedure assumes the following conditions:

The E7 unit and ONT have been upgraded to the latest software version. If necessary,
see:


Calix E7 Software Upgrade Guide
The SIP configuration file is created and transferred to a server local to the E7. If
necessary, see:

Completing Residential Gateway and SIP Configuration File Intake Forms

Calix Application Note: Using the ONT VoIP Configuration File
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
63
To configure SIP gateway service with OMCI
provisioning
Step 1. Configure the network uplinks for GPON services.
Ethernet ports (on page 67)
Ethernet port interfaces (on page 73)
Service VLANs (on page 86)
The VLAN assignment must be different between the VoIP IP host and the subscriber port. Sharing VLANs between a subscriber
port and a VoIP IP host is not supported. For T-series ONT peer-to-peer voice service, PON Hairpin or MAC-FF must be
enabled.
VLAN memberships (on page 107)
Uplink interface (or ERPS domain, if the uplink resides on a different shelf) must be added to the VLAN membership.
Step 2. Create the necessary system profiles that support GPON applications.
Rules to classify traffic (on page 116)

Service match list (on page 127)

Service tag action (on page 131)
HGW ONTs use tagged match lists with a change-tag service tag action.
Profiles for voice services (on page 201)

IP Host (on page 202)
Reference a service tag action that indicates the voice service VLAN and SIP configuration-file instance.

Create a dial plan (on page 206)

Create a SIP gateway profile (on page 208)
Step 3. Configure the PON.
GPON port (on page 232)
Create an ONT (on page 244)
Retrieve and apply the SIP configuration file (on page 237)
ONT voice port (on page 260)
Set the loss plan to manual and set tx and rx loss values
Step 4. Configure the voice service.
Form view

Create a SIP voice service (on page 310)
Table view

Create a SIP voice service (on page 313)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
64
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Chapter 4
Configuring GPON Applications
This chapter describes supporting procedures that show how to setup GPON applications,
including configuring the E7 system, creating profiles, configuring a PON, and then adding
subscriber services.

For overviews of subscriber services provisioning steps with links to supporting
procedure topics, see:
Service Provisioning Overviews (on page 41)

For guidance in filling in the provisioning forms necessary to configure services, see:
Service Provisioning Examples (on page 349)
Note: For information on initial system turn-up and modular chassis system configuration,
see the Calix E7 User Guide.
Topics Covered
This chapter covers the following topics:
Step 1. Configure network uplinks for GPON services
Step 2. Creating system profiles that support GPON applications
Step 3. Configure a PON
Step 4. Configure subscriber services
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
66
Step 1. Configure the Network Uplink(s) for
GPON Services
This section describes how to configure the network uplinks for provisioned GPON
services.

For overviews of subscriber services provisioning steps with links to supporting
procedure topics, see:
Service Provisioning Overviews (on page 41)

For instructions on configuring transport rings and aggregation links.
See "Configuring Transport and Aggregation Support" in the Calix E7 User Guide
Topics Covered
This section covers the following topics in bold that are part of the overall GPON services
configuration process:
Step 1. Configure network uplinks for GPON services

Configuring Ethernet port interfaces

Configuring E7 Ethernet ports

Creating service VLANs

Adding interfaces to VLAN memberships
Step 2. Create system profiles that support GPON applications
Step 3. Configure a PON
Step 4. Configure subscriber services
Overview: Configuring the Network Uplink(s)
This chapter describes how to configure the network uplink(s) for E7 GPON services.
If the network contains a number of E7 nodes, such as in a 10GE transport ring, the
network uplink(s) may reside in a different shelf from the GPON ports and may include
multiple uplinks per service. Network uplink(s) are typically located in a shelf closest to the
core or headend.
Calix recommends synchronizing the ARP timer in the upstream router with the age timer in
network device MAC tables. The ARP age timer value on the upstream router should be less
than or equal to the value set for the MAC age timer applied to the ONTs.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
67
Note: For information on initial system turn-up, modular chassis system configuration,
ERPS ring configuration, or configuring system-level objects, such as NTP servers and
SNMP traps, see the Calix E7 User Guide.
Configuration process
The network uplink configuration process follows:
1. Configure the 10GE or GE uplink port for service. (on page 67)

Set the Admin status for enable.
2. Configure the Ethernet interface on the uplink port. (on page 73)

Set the interface role to Trunk.

Enable RSTP for link protection or create LAG interfaces, as required.
3. Create the service VLAN(s). (on page 86)

Create one VLAN per subscriber for the 1:1 provisioning model.

Create one VLAN per service for the N:1 provisioning model.

For video service, enable IGMP Snooping.
4. Add the Ethernet uplink interface to the service VLAN memberships. (on page 107)
Configuring the Ethernet Uplink Port
The topic describes how to configure an E7 Ethernet port for an uplink.
E7 Ethernet ports and the associated Ethernet interfaces always exist and can only be
modified. LAG interfaces and their association with Ethernet ports can be created, deleted,
and modified. See Configuring an Ethernet or LAG Interface (on page 73).
The physical characteristics of the underlying ports include:



Speed
Duplex setting
Interface type
ETH-Port names:


g(port number) = Gigabit Ethernet Ports (GE)
x(port number) = 10Gigabit Ethernet Ports (10GE)
Configuration guidelines

An Ethernet port is always a member of exactly one interface, even when it is being used
in a standalone manner.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
68









An Ethernet port can be either assigned to the Ethernet interface associated with the
port, or assigned to an existing LAG interface.
The interface provisioning (for example, VLAN membership) applies to the port when
the interface is assigned to the port.
Keep the LACP role set to the default value of active, unless there is a very clear need.
Specifically, the topology where at least one side of the LAG is cross-card will not
operate when either side of the LAG is set to LACP role = passive.
When a port interface is added to an ERPS ring, the port attribute of Duplex defaults to
full and the Flow Control setting defaults to none. If the port interface is removed from
the ERPS domain, these attributes can again be modified.
Destination lookup failure (DLF) based rate limiting should never be used on aggregation
network elements as this naturally happens when the access network goes through a
topology change. The use of this feature at the access node is also not advised as the rate
limiter indiscriminately applies to all services including business services.
The E7-2 supports 2.5 Gbps pluggable module interfaces in the SFP ports of the 10GE4, GPON-4, VDSL2-48C, and VDSL2-48 cards.
The 2.5GE interfaces support equivalent functions and networking protocols as the GE
and 10GE interfaces.
Auto-negotiation is supported over twisted pair 1000BASE-T links and some fiber
1000BASE-X links. It is not supported over 2.5G or 10G links.
When connecting to devices that do not support auto-negotiation, provision the E7 port
manually for the speed, duplex, and flow control options that are compatible with the
options supported by the other side.
Forced Speed Settings Supported
Copper modules in SFP/CSFP ports
Direct-Attach cables in SFP/CSFP ports
Direct-Attach cables in SFP+ port
Copper modules in SFP+ ports
1G fiber modules in SFP or SFP+ ports
2.5G fiber modules in SFP ports
10G fiber modules in SFP+ ports

10M
100M
1G
X
X
X
X
X
X
X
2.5G
10G
X
X
X
The following rules apply for stand-alone E7 shelves and Modular Chassis Controller
(MCC) shelves:


SFP and SFP+ Network ports; support protection protocols; ERPS, LAG, RSTP:

Transport ports; ERPS or RSTP protection

Trunk/Edge ports; RSTP and/or LAG protection, towards the edge
switch/router or subtended device
SFP sockets:

1GE or 2.5GE data rate modes

At 2.5GE data rate mode, supported port roles are
Stacking/Edge/Trunk/Access

At 1G data rate mode; supported port roles are Edge/Trunk/Access
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
69



SFP+ sockets:

1GE or 10GE data rate modes

At 10G data rate mode; supported port roles are Stacking/Edge/Trunk/Access

At 1G data rate mode; supported port roles are Edge/Trunk/Access
Support for subscriber DSL drops; supported port roles are Access
The following rules apply for Modular Chassis Expansion (MCE) shelves:

SFP and SFP+ Access ports; no support for protection protocols



Aggregation; unprotected pt-to-pt links to subtended devices from SFP and
SFP+ sockets
SFP sockets

1GE or 2.5GE data rate modes

At 2.5GE data rate mode; supported port roles are Stacking/Access (unprotected
pt-to-pt)

At 1GE data rate mode; supported port roles are Access (unprotected pt-to-pt)
SFP+ sockets

1GE or 10GE data rate modes

At 10GE data rate mode; supported port roles are Stacking/Access (unprotected
pt-to-pt)

At 1GE data rate mode; supported port roles are Access (unprotected pt-to-pt)
Before starting
Before starting the configuration process, check that the following conditions are met:





The class map and class rules are configured.
The policy map and policies are configured.
The Ethernet or LAG interface is configured.
The Ethernet port grade-of-service (GoS) profile is created.
The class-of-service (CoS) profile is created.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
70
Parameters
You can provision the following parameters for E7 GE or 10GE Ethernet ports:
Parameter
Admin State
Description
Service state of port.
While troubleshooting a port that has Admin State = "enabled-noalarms," either use the CLI command "show alarm include
suppressed," or from the web browser interface temporarily set the
Admin State to "enabled," and then refresh the alarm panel
manually or wait for default refresh rate to see the suppressed
alarms.
Interface
Name of interface to select whether to leave the default connection
to the port's logical (associated) Ethernet interface, or assign the
port to a link aggregation group (LAG) interface.
Valid Options
enabled
disabled ‡
enabled-no-alarms
EthIntf
LagIntf
Note: Before you can assign a port to a LAG interface, you must
disable the port's default associated interface. When a port is
assigned to a LAG, the LAG interface provisioning (for example,
VLAN membership) applies to the port.
GOS Profile
Name of Grade-of-Service (GoS) profile to use that has been
previously defined. The GoS profile specifies the operation
thresholds for the Ethernet port.
Any established Ethernet GoS
profile
COS Config
Name of class-of-service (CoS) profile to use that has been
previously defined. The class-of-service profile specifies the
queuing of packets.
Any established Ethernet port
CoS profile
Broadcast Max Rate
Select whether to disable this parameter (off), or enter a value to
specify the maximum rate for broadcast traffic (packets/second).
This is an ingress rate limiter.
off, 0-16383999
Use "k" and "m" to multiply the
rate.
Unknown Mcast Max
Rate
Select whether to disable this parameter (off), or enter a value to
limit the rate for unknown multicast traffic (packets/seconds). Use
"k" and "m" to multiply rate.
off ‡
Enter Value = 0–16,383,999
DLF Max Rate
Select whether to disable this parameter (off), or enter a value for
the maximum ingress rate for unknown unicast or destination
lookup failure (DLF) traffic (packets/seconds). Use "k" and "m" to
multiply rate. DLF applies to unicast packets where the bridges
lookup the destination MAC address in their learning tables and
cannot find it (a lookup miss) thus floods the packet to the
broadcast domain until the packet hits a bridge that knows
(learned) the destination MAC address or the packet is received by
the destination device.
off ‡
Enter Value = 0–16,383,999
LACP Priority
Priority value to use for determining which port to activate in a
LAG. The lower value takes priority.
0-65535
32768 ‡
For example, in a cross-card protection LAG, set the ports on the
active card to a common LACP priority value, and then set the
LAG ports on the standby card to another common priority value.
The priority value on the active card ports must be lower than the
value set for the ports on the standby card.
LACP Timeout
The length of timeout for LACP.
Note: Avoid the use of LACP long timeouts, unless there is a very
specific need.
short ‡
long
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
71
Parameter
Duplex
Description
Valid Options

Half-duplex uses Carrier Sense Multiple Access (CSMA) to
detect collisions and recover from them.
half, full, auto‡ (auto-negotiate
duplex value with the link
partner)

Full-duplex transmits and receives at the same time. Note:
Use this setting for ERPS ring ports.

Auto:
Duplex mode for the port.
If the link is auto-negotiated, the duplex attribute is negotiated
with the link partner.
If the link speed is forced to a set value, full duplex is the
default.
Flow control
Applies back pressure to a transmitter that is outrunning the
receiver's capacity to process incoming data.

tx-pause sends pause packets to the partner link, when
needed.

rx-pause honors the partner link's pause packets and stops
transmitting, when asked.

tx-rx sends pause packets and honors the partner link's pause
packets.

none does not send pause packets and does not honor the
partner link's pause packets. Note: Use this setting for ERPS
ring ports.

Auto:
rx-tx, rx-pause, tx-pause, auto‡,
none
If the link is auto-negotiated, the pause attribute is negotiated
with the partner link.
If the link speed is forced to a set value, tx-rx is the default.
LLDP Mode
Link Layer Discovery Protocol (LLDP) mode for the port. LLDP
defines a set of information to be transmitted and received
periodically on an Ethernet interface to and from connected
devices. This information can be leveraged by the management
interfaces to build a “network” topology view and identify all
connected access nodes.
disabled, tx-only ‡
Note: LLDP is enabled by default for all GE Access interfaces
configured as Edge or Trunk.
Ethernet Speed
(Mb/s)
Data rate of port (bits/s).
Auto setting:

If the link supports auto-negotiation, the link partners autonegotiate the speed while advertising the duplex and flow
control parameters specified.

If the link does NOT support auto-negotiation, the setting is for
the fastest rate that the module can support.
auto‡, module-rate (native
speed of pluggable module),
10mbps, 100mbps, 1gbps,
2.5gbps, 10gbps
Module-rate is for SFP+ ports, which supports both 10GE and 1GE
modules. The bit rate of the installed module is forced as the port
speed. No auto-negotiation takes place with this setting. Module
rate is not supported for XFP ports.
Fixed speed setting forces the speed to the value specified. (Note:
See the configuration guidelines above for the forced speed setting
supported for various ports.)
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
72
To configure an E7 GE port for service
1. On the Navigation Tree, double-click an E7 line card, and then click a GE or 10GE port.

Alternatively, you can access an E7 Ethernet port using the following methods:

Click the triangle-arrow to the left of the service card in the Navigation tree, and then
click the specific Ethernet port from the tree.

On the Navigation Tree, click E7, and then click System > Ethernet Ports and click
a listed Ethernet port, or click in the row between the columns to edit the row. You
can select multiple ports to edit using the Control+click and Shift+click keys. Click
Apply when the parameter settings are complete.
2. Reference the table above to configure the parameters.
3. From the menu, click Apply.
For CLI:
set eth-port <port ID> [speed|duplex|flow-ctrl|interface|eth-gos|cos-queuecfg|bcast-max-rate|unk-mcast-max-rate|dlf-max-rate|lacp-priority|lacptimeout|admin-state]
Bulk Modifying Ethernet Ports
Modifying Ethernet ports in selected groups results in rapid configuration changes across a
node.
To create a range of Ethernet ports
1. On the Navigation Tree, select the node, and then click Ethernet Ports.
2. In the work area, select the Ethernet ports to modify using Shift+click or Ctrl+click.
To select a row from the table, click on the portion of the row in between the columns
that has no text, as indicated by the red rectangles below.
3. In the edit row at the top of the work area, select the parameter to modify, and select the
new value.
4. Click Enter to identify each row with a modified value as having a pending change,
indicated by an orange arrow.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
73
5. In the Toolbar, click Apply to commit the changes.
For CLI:
set eth-port <port ID> [speed|duplex|flow-ctrl|interface|eth-gos|cos-queuecfg|bcast-max-rate|unk-mcast-max-rate|dlf-max-rate|lacp-priority|lacptimeout|admin-state]
Configuring an E7 Ethernet or LAG Interface
This topic describes how to configure an E7 Ethernet interface and a Link Aggregation
Group (LAG) interface. E7 Ethernet interfaces are logical objects that represent the servicerelated attributes of an Ethernet port.
E7 Ethernet ports and the associated Ethernet interfaces always exist and can only be
modified. LAG interfaces and their association with E7 Ethernet ports can be created,
deleted, and modified.
Interface names


Eth interfaces (Non-LAG related interfaces) share the same name as the E7 Ethernet
Ports (card 1/Eth port g1, for example 1/g1)

g(port number) = GE(port number)

x(port number) = 10GE(port number)
LAG interfaces are named at the time of creation
Interface roles
Each GE and 10GE interface in the E7 has one of the following configuration-role types:
Trunk: A port connecting to other equipment belonging to the service provider or to
another service domain with consistent VLAN tagging levels. These ports may also be
referred to as Network ports or Provider ports in industry standards. These ports support
outer VLAN tag plus MAC switching.
Examples of trunk ports are 10G ERPS transport ports and GE uplinks. Trunk ports can be
configured for link aggregation, RSTP, or ERPS. To properly process ingress double tags, the
GE network interface (uplink) must be configured as a Trunk role.
Edge: A port facing customer equipment or facing reduced functionality devices, alternative
administrative domains, or managed CPE. Generally, this E7 Ethernet port interface is where
all classification is first performed on ingress traffic (if customer facing). The E7 Ethernet
interface is also expected to add, replace, or remove one or more VLAN tags on edge traffic.
RSTP and LAG networking protocols are supported.
Examples of an edge port would include GE ports to managed CPE, a GE/10GE port to
external equipment which may use different tagging levels, or GPON ports.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
74
Access: A port facing untrusted customer equipment or other devices serving subscribers.
Generally, this port interface is where individual subscriber services are defined and enforced
(bandwidth limits, security, multicast profiles). Networking protocols are not supported.
Examples of an access port would be point-to-point connections to subscribers or other
devices serving subscribers.
VLAN support
By default, every E7 Ethernet port with a trunk or edge interface on the unit is a member of
VLAN 1, the Native VLAN. The Native VLAN is available to pass any untagged traffic. You
can provision an E7 Ethernet port interface to use a different existing VLAN as the Native
VLAN.
To forward untagged traffic on E7 Ethernet ports with an access interface, an add-tag action
must be applied to untagged frames, assigning the traffic to a designated VLAN.
Tagged traffic that does not match any of the tagging criteria is dropped.
For modular chassis nodes, any VLAN created on the system is automatically mapped to the
Stacking Ports. The remaining port interfaces in the system must be a VLAN member for
traffic to pass on the VLAN through the interface.
Interface role configuration guidelines
Trunk
Edge
Access
E7-2 or E-Series
X
X
X
E7-2 MCC
X
X
X
E7-2 MCE
E7-20 SCP
X
X
X
E7-20 GE-24
X
ONT Ethernet Port
X
Tag Actions
X
Native VLAN
X
X
Networking Protocol
(RSTP, ERPS*, LAG)
X
X
X
*Edge ports only support RSTP and LAG networking protocols, NOT ERPS.
Link aggregation groups
The E7 uses IEEE 802.3ad/802.1AX Link Aggregation (LAG) to bond multiple GE or
10GE ports (not both) into a single link aggregation group with a single logical Ethernet
interface. The ports that comprise a LAG can be on the same line card or on two different
line cards in the same shelf.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
75
Link aggregation provides two principle values to the network operator:


Point to point link protection / redundancy between network elements
Bandwidth expansion of the logical interface beyond the capacity of a single link
Single-card LAGs
Two different single-card LAG configurations are shown below:


The active LAG configured for the E7 has all ports in the LAG active and the combined
bandwidth of the ports is available to carry the traffic on the logical link of the LAG.
When a failure occurs, the available bandwidth is reduced by the amount of bandwidth
carried over the failed port.
The active/standby LAG configured for the router has multiple ports active and one
port in standby, positioned to come online when an active port fails.
Example parameter settings:




RSTP Enabled = disabled
LAG cross-card = N (No) or disabled
LACP Min Ports = 1
LACP Max Ports = 2**
Note: **Ports added to the LAG that exceed the LACP Max Ports parameter are designated
as standby ports.
Cross-card LAGs
The cross-card protection LAGs shown below have half of the LAG ports on a card
designated as active, and the other half of the LAG ports on a standby card. Equipment and
facility protection are provided, but not an increase in bandwidth capacity across the active
and standby links. Each LAG has a failure threshold that defines how many active ports in
the group can fail before the group is taken out of service, and the system switches the LAG
operation to the ports on the standby card.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
76
Note: If the LACP Min Ports = the LACP Max Ports, the system switches the LAG
operation to the ports on the standby card when one active port fails. When using cross-card
LAG, the LAG on the switch connected to the E7 must have RSTP disabled.
Note: Keep the LACP role set to the default value of active, unless there is a very clear
need. Specifically, the topology where at least one side of the LAG is cross-card will not
operate when either side of the LAG is set to LACP role = passive.
Example parameter settings:




RSTP Enabled = disabled
LAG cross-card = Y (Yes) or enabled
Access router LAG:

LACP Min Ports = 1

LACP Max Ports = 2

Card 1 Ethernet ports LACP Priority = 128

Card 2 Ethernet ports LACP Priority = 100
E5-100 LAG:

LACP Min Ports = 1

LACP Max Ports = 1

Card 1 Ethernet port LACP Priority = 100

Card 2 Ethernet port LACP Priority = 128
LAG per card and RSTP
As a network configuration, RSTP can be enabled on two LAG interfaces to create a
protected connection to routers. As shown below, a separate LAG is configured on each
card and the LAG interfaces have an aggregated bandwidth capacity of 2Gbps, while RSTP
provides E7 cross-card equipment protection. All of the links in the LAG must terminate on
the same card for RSTP to be supported.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
77
Example parameter settings:



RSTP Enabled = enabled
LAG cross-card = N (No) or disabled
Access router LAG:

LACP Min Ports = 2

LACP Max Ports = 2
Facility and equipment protection using RSTP
Individual Ethernet port interfaces with either a Trunk or Edge role can participate in Rapid
Spanning Tree Protocol (RSTP).





Facility protection can be configured by using two ports on the same E7 card.
Equipment protection can be configured by using one port on two cards in the same E7
shelf. That is, one port on each E7 card.
For Modular Chassis systems, RSTP is only supported on MCC shelf interfaces.
For E7-20 systems, RSTP is only supported on SCP cards.
For cross-card LAG interfaces, RSTP is not supported on the E7, and the LAG end
connected to a switch must also have RSTP disabled. If RSTP is enabled on the
connected system, then that system will take 20-30 seconds to pass traffic again while
waiting for RSTP to timeout.
Note: Node protection can be configured by using two nodes (E7-2 or E5-400) on an ERPS
ring. See Configuring RSTP Settings for the RSTP parameters to apply to the nodes.
To view the E7 Ethernet port interfaces that are actively participating in RSTP, click E7 on
the Navigation Tree, and then click the RSTP > Interfaces tabs.
Configuration guidelines
Follow these guidelines when configuring an Ethernet port interface or LAG interface:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
78






An Ethernet interface always exists, cannot be deleted, can be modified, and is associated
with a specific companion Ethernet port (GE or 10GE).
A LAG interface can be created, deleted, and modified.
All VLAN associations must be removed from a LAG before the LAG can be deleted.
Before a port can be assigned to a LAG interface, the port's default associated interface
must be disabled. When a port is assigned to a LAG, the LAG interface provisioning (for
example, VLAN membership) applies to the port. See Configuring an Ethernet Port (on page
67) for details on how to add ports to the LAG interface.
A port is always a member of exactly one interface, even when it is being used in a
standalone manner.
You can configure only one of the following attributes on a given VLAN on a given
interface:









Trunk interfaces:

VLAN member

Native VLAN
Edge interfaces:

VLAN member

Tag-action

Native VLAN
Access interfaces:

VLAN member

Tag-action
Trunk and Edge interfaces are always associated with at least one VLAN, through the
native VLAN attribute (VLAN 1, by default). Access interfaces do not support a Native
VLAN, however, tag actions can be used to assign untagged traffic to a VLAN ID.
All network connections (ERPS, RSTP, LAG, DHCP servers, multicast routers, IGMPenabled video servers, network-facing routers) are made on Trunk or Edge interfaces,
only.
Interfaces can be associated with additional VLANs through memberships or tag-actions.
When a VLAN has DHCP snooping and Option 82 relay enabled, an Ethernet interface
can be directly added to the VLAN membership, but using a tag action to associate an
Ethernet interface to such a VLAN is not supported.
BPDU Guard and RSTP cannot be enabled on an interface, simultaneously.
The ports in a LAG must be either all GE or all 10GE.

For GE ports:

up to 8 GE ports per LAG

up to 6 LAGs per shelf
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
79






For 10GE ports:

up to 4 10GE ports per LAG

up to 2 LAGs per shelf
For Modular Chassis (MC) systems, LAG and RSTP interfaces are only supported on the
Modular Chassis Controller (MCC) shelf.
For E7-20 systems, LAG and RSTP interfaces are only supported on the SCP cards.
A LAG can include ports on the same line card, or on two different line cards within the
same shelf, known as cross-card protection.
For 1GE LAG groups, the connectors should be of the same type: SFP or SFP+, not
both.
For cross-card protection LAGs:

An equal number of links should be configured for the active card and the standby
card (1-4).

The ports on only one of the cards will be active while the ports on the other card are
standby.

Used between two systems connected by the LAG to determine which system should
be controlling the LAG. The lower value takes priority. Typically, the upstream side
of the LAG is configured for the LAG master (lower value).

When provisioning active/standby LAG, the port priority should NOT be
provisioned to 0.

For both ends of a cross-card LAG, the LAG ports on the active card must all have
the same LACP Priority value for the Ethernet port parameter, and the LAG ports
on the standby card must all have the same priority value. Yet, the priority value on
the active card ports must be lower than the value set for the ports on the standby
card, giving the priority to the active card ports.

The port priorities on each side of the LAG should be set to the same values.

Keep the interface LACP Role set to the default value of active, unless there is a very
clear need. Specifically, the topology where at least one side of the LAG is cross-card
will not operate when either side of the LAG is set to LACP role = passive.

Keep the Ethernet port parameter LACP Timeout set to the default value of short,
unless there is a very clear need. Specifically, the topology where at least one side of
the LAG is cross-card will not operate when either side of the LAG is set to LACP
Timeout = long.

RSTP must be disabled in order to configure a cross-card LAG.

Set the LACP Role parameter to Active for both ends of the LAG for a functional
topology.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
80

A failure threshold defines how many active ports in the group can fail before the
group is taken out of service, and the system switches the LAG operation to the
ports on the standby card. This threshold is indicated by the LACP Min Ports
parameters.







LACP Min Ports = LACP Max Ports (When one active port fails, the system
switches the LAG operation to the ports on the standby card.)
Set the following parameters as shown to achieve the best re-convergence time:

The VLAN IGMP Mode = proxy

The IGMP profile Router Learning Mode = static

The IGMP profile Router Solicit On Topology Change = N (disabled)

The LAG interface is designated as a static router port through the VLAN
membership.
For a single-card LAG, the ports added to the LAG that exceed the LACP Max Ports
parameter value are designated as standby ports and come online when a LAG active
port fails. (This is the equivalent of active/standby LAG on a single card.)
The Link Aggregation Control Protocol (LACP) assigns a LAG the same MAC address
of the associated Ethernet link with the highest port priority. When two or more ports
have the same priority, the MAC address of the port with the lowest port number is used.
Therefore, if ports 3, 5, and 7 are configured for a LAG, then the LAG MAC address is
the MAC address of port 3. The system MAC address identifies the system in the LACP
control messages, and the interface MAC address identifies the Link Aggregation Group.
Policy maps:

For Trunk interfaces, any policy map assignment is allowed.

For Edge and Access interfaces, if a policy map contains a two-tag classification, the
edge or access link must have a tag-action that adds the outer tag being matched by
the class rule.
For an RSTP network, Calix recommends setting the following parameters as shown:

The VLAN IGMP Mode = snoop-suppress or proxy

The IGMP profile Router Learning Mode = static-dynamic

The IGMP profile Router Solicit On Topology Change = Y (enabled)

The interface NOT be designated as a static router port through the VLAN
membership.
The Interface Quality Audit (IQA) function periodically checks the number of File Check
Sequence (FCS) errors received as a percentage of total frames received on an interface.
An interface that exceeds the provisioned thresholds can be set to generate an alarm,
switch traffic to an alternate path, or force the interface to an OOS state where operator
intervention is required to bring the interface to an operational state by manually
disabling the interface, and then re-enabling the interface.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
81
Before starting
Before starting the configuration process, check that the following conditions are met:

The policy map that you want to associate to the E7 Ethernet port interface is already
created.
Parameters
You can provision the following parameters for LAG or Ethernet interfaces:
Parameter
*
Name
Description
Name of LAG interface or associated Ethernet port (card/Ethernet port).
Valid Options
String 31 characters
(Note: This is a case-sensitive string.)
Role*
Role of E7 Ethernet port interface.

trunk and edge are supported on E7-2 standalone, E7 modular
chassis controller, and E7-20 SCP cards.

access is supported on E7-2 standalone, E7 modular chassis
controller, E7 modular chassis expansion cards, and E7-20
linecards.
See the rules and restrictions for each role in the above paragraphs.
trunk
edge
access
E7-2, E7 Modular Chassis
Controller, and E7-20 SCP
cards:

10G = trunk ‡

1G = edge ‡
E7-20 and E7 Modular
Chassis Expansion:

10G = access ‡

1G = access ‡
Default (LAG) = NA
Admin State
Service state of E7 port interface. Select whether the interface is in
service.
enabled ‡
disabled
Note: Before you can assign a port to a LAG interface, you must disable
the port's default associated interface. When a port is assigned to a
LAG, the LAG interface provisioning (for example, VLAN membership)
applies to the port.
Description
Descriptive name for the interface.
String 31 characters
RSTP
Whether the interface is running rapid spanning tree protocol (RSTP).
The E7 supports port-level RSTP. Therefore, ensure the far-end device
is configured similarly (port-level RSTP) and not using VLAN-level
RSTP.
enabled (‡ E7-2)
disabled (‡ E7-20)
tunneled
STP Priority

RSTP (enabled) is only supported for trunk and edge interfaces.

RSTP (tunneled) is supported for all interface roles and should only
be used when configuring TLAN service.

RSTP and BPDU Guard cannot be enabled on an interface,
simultaneously.

For Modular Chassis systems, RSTP is only supported on MCC
shelf interfaces.

For E7-20 systems, RSTP is only supported on SCP interfaces.

For cross-card LAG interfaces, RSTP is not supported and must be
disabled in order to configure a cross-card LAG.
Spanning tree protocol (STP) priority of this port interface.
Note: Leave the default value unless you are certain of a modified value
to assign as an STP priority for the interface.
0, 16, 32, 48, 64, 80, 96,
112, 128‡, 144, 160, 176,
192, 208, 224, 240
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
82
Parameter
STP Path Cost
Description
Spanning tree protocol (STP) path cost is the cost of transmitting a
frame on to a network through that port. It is assigned according to the
speed of the bridge. The slower the media, the higher the cost.
Valid Options
1-200000000
4‡
Note: Leave the default value unless you are certain of a modified value
to assign as the cost of service.
Policy Map
Name of policy map used on ingress traffic packets. The associated
map describes what actions to take when the ingress traffic packets
match the listed criteria.
name of map
Subscriber ID
Identification information of subscriber, such as phone number, or
account number.
String 0-63 characters
(LAG only) Individual traffic flows will only use a single link in the Link
Aggregation Group (LAG). The link used for each packet is based on a
hash algorithm.
src-mac
dest-mac
src-dest-mac ‡
1
LACP Hash
(Note: See "Link Aggregation Group" in the Calix E7 Engineering and
Planning Guide for topology considerations in the choice of distribution
algorithm.)
MTU (Bytes)
Maximum Transmission Unit size (bytes). E7 supports the ability to set
the MTU size on an interface to a maximum or 9000 bytes, not including
the Ethernet header, two VLAN tags for Q-in-Q, and the frame check
sequence (32-bit CRC).

MTU = 9000 bytes for E7 Ethernet interfaces

MTU = 2000 bytes for 700GE and 760GX GPON ONTs

MTU = 1600 bytes for 700GX GPON ONTs
1500-9600
2000 ‡
For example:
Ether Type

2000 bytes = MTU

2026 = Max Ethernet frame (with two VLAN tags without
Preamble/Delimiter)

2034 = Max Ethernet frame (with two VLAN tags including
Preamble/Delimiter)

2046 = Max Ethernet frame (with two VLANs, preamble/Delimiter,
and Interframe Gap)
The Ethertype indicates the protocol being transported in the Ethernet
frame.

0x8100 - IEEE 802.1Q-tagged

0x88a8 - IEEE 802.3ad provider bridging

0x9100 - Q-in-Q (double tagged)
0x8100 ‡
0x88a8
0x9100
The recommended value of 0x8100 should be used for all interfaces
(Ethernet and LAG).
Note: The VLAN tagged frames are identified as having a tag by
utilizing the Ethertype field.
Native VLAN
Native VLAN to use for untagged user traffic on this interface. VLANs
can be specified by name or by numeric VLAN ID. Supported for trunk
and edge interfaces, only.
numeric value
(range 1-4093)
1‡
To forward untagged traffic on E7 Ethernet ports with an access
interface, an add-tag action must be applied to untagged frames,
assigning the traffic to a designated VLAN.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
83
Parameter
Split Horizon
Forwarding
Description
Enable or disable split-horizon forwarding on this Edge interface of a
standalone E7-2 or modular chassis controller shelf. (The Split Horizon
Forwarding is not supported on the E7-20 system.)
Valid Options
disable
enable (‡ E7-2)
The default is “Enabled” or "Y" and should only be disabled when
setting up TLAN service between multiple edge or access ports on the
same E7. When Split-horizon forwarding is enabled on an edge port,
traffic from that port will only route to trunk links. The Split-horizon
forwarding flag has no effect on trunk links. Examples of an edge port
would include GE ports to managed CPE, a GE/10GE port to external
equipment which may use different tagging levels, or GPON ports. By
default, E7 edge ports have the split horizon feature enabled which
isolates port traffic from other edge ports within the same E7 line card.
BPDU MAC Mode
MAC for rapid spanning tree protocol (RSTP) bridge protocol data units
(BPDUs).

1d results in the E7 transmitting BPDUs with a DA of
01:80:C2:00:00:00. Use this selection when the E7 is connected to
an 802.1d compliant switch with redundant link.

1ad results in the E7 transmitting BPDUs with a DA of
01:80:C2:00:00:08. Use this selection when the E7 is connected to
an 802.1ad compliant switch with redundant link.
1d ‡
1ad
LACP Tunnel
LACP protocol packets are forwarded when set to enabled (Y) on an
Ethernet interface and should only be used when configuring TLAN
service.
disable ‡
enable
RSTP Auto Edge
Link
Enables or disables automatic RSTP detection and protocol negotiation
for other connected bridges on E7 Ethernet ports. Each RSTP edge link
transitions immediately to the RSTP forwarding port state, since there is
no possibility of it participating in a loop. If another connected bridge is
detected on a port with RSTP Edge Link enabled, the port immediately
transitions to point-to-point and negotiates the RSTP topology.
disable ‡
enable
Trusted
Whether the interface is a trusted source of DHCP option 82/LDRA
data.
selected (yes) ‡
unselected (no)
BPDU Guard

Ethernet interfaces used for LAG or ERPS links can only be set to
Trusted = Y.

Access interfaces can only be set to Trusted = N.
Enables or disables BPDU guard mode. When enabled, this prevents
topology loops by preventing the participation of an interface in a
spanning tree. When the interface receives a BPDU (STP, RSTP,
MSTP), it is put into a disabled state where an operator must manually
disable, and then re-enable the interface to put the interface back into
service.
BPDU Guard and RSTP cannot be enabled on an interface,
simultaneously.
disable (default for E7-2
standalone, MCC shelf, and
E7-20 SCP with RSTP
enabled on GE/10GE ports)
enable (default for all
Access interfaces, where
RSTP is not supported)
IGMP Immediate
Leave
Enables or disables IGMP immediate leave. When enabled, checks are
omitted that would see if there are other hosts interested in the multicast
group.
use-vlan-setting ‡
enabled
disabled
Subscriber ID
Identifying information of the subscriber.
string (0-63 characters)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
84
Parameter
Interface Quality
Audit Mode
Description
Mode to periodically check the number of File Check Sequence (FCS)
errors received as a percentage of total frames received on an interface.
An interface that exceeds the provisioned thresholds can be set to one
of the following modes:

no-audit - disables the Interface Quality Audit (IQA) mode

alarm-only - generates an alarm, but, does not take any action on
the interface

disable-interface – Disable the interface when the threshold is
exceeded

protocol-action – For ERPS and LAG, only disable the interface if
there is an alternate path that is up and available. For non-ERPS
and non-LAG interfaces, this is interpreted as “alarm only.”
Valid Options
no-audit, alarm-only ‡,
protocol-action, disableinterface
Polling Interval
Number of seconds between interface quality audits that compare
errored frames to total received frames.
1-60
1‡
Error Threshold
Number of errored frames per million total frames to consider a specific
interval as failed.
1-100000
1000 ‡
Polling Window
Number of interface quality audit intervals to consider for failure
determination.
10-60
60 ‡
Errored Interval
Count
Number of failed audit quality intervals within the polling window that will
indicate an interface failure for IQA to take an alarm or OOS action.
1-60
10 ‡
Interval Min Frames
Minimum number of frames that must be received per interval for a
specific interval to be considered valid.
1-2147483647
100 ‡
LACP Cross Card
(LAG only) Whether LAG cross-card protection is enabled, allowing
ports on two cards to be configured into a LAG where one card's ports
are active and the other card's ports are standby. This only applies to
cross-card protection LAGs.
disabled ‡
active-standby
LAG Cross Card
Revertive
(LAG only) Whether to have the LAG interface revert to the ports on the
active card after a failure is found and fixed. This is only used for crosscard protection LAGs.
N (unselected) ‡
Y (selected)
LACP Min Ports
(LAG only) Minimum number of ports required for LAG activation. When
the number of active ports falls below this value, the group is taken out
of service.
1-8
1‡
LACP Max Ports

When two LAGs are used with RSTP node protection, the system
switches LAG operation to the other LAG.

For cross-card protection LAGs, the system switches the LAG
operation to the ports on the standby card.
(LAG only) Maximum number of active ports participating in the LAG.

For single-card LAGs, the ports added to the LAG that exceed this
value are designated as standby ports and come online when an
active LAG port fails.

For a cross-card protection LAG, this value indicates the number of
ports on each card, assuming that there are an equal number of
active and standby ports in the LAG. You cannot add more that this
number of ports from any one card. The limit is 4.
1-8
8‡
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
85
Parameter
LACP System
Priority
LACP Role
Description
(LAG only) Used between two systems connected by the LAG to
determine which system should be controlling the LAG. The lower
value takes priority. Typically, the upstream side of the LAG is
configured for the LAG master (lower value).

When the LACP system-priority is changed, a 2-second downtime
will occur where no traffic passes through the LAG.

When provisioning active/standby LAG, the port priority should NOT
be provisioned to 0.

For both ends of a cross-card LAG, the LAG ports on the active card
must all have the same LACP Priority value for the Ethernet port
parameter, and the LAG ports on the standby card must all have the
same priority value. Yet, the priority value on the active card ports
must be lower than the value set for the ports on the standby card,
giving the priority to the active card ports.

The port priorities on each side of the LAG should be set to the
same values.
(LAG only) Role for this end of the LAG.

Active control mode actively initiates the LACP negotiations on a
link.

Passive mode does not initiate LACP negotiations, but will respond.
Valid Options
0-65535
32768 ‡
active ‡
passive
(Note: Avoid the use of LACP passive role, unless there is a very
specific need.)
* Required field
‡ Default
1
Only for LAG interfaces
To configure an E7 Ethernet port associated interface for service
1. On the Navigation Tree, click a GE or 10GE port where you want to configure an
associated interface.
2. In the Work Area, click Associated Interface > Provisioning.
3. Reference the table above to configure the parameters.
4. Click Apply.
For CLI:
set interface <interface name> [role|description|native-vlan|mtu|rstpactive|rstp-prio|rstp-path-cost|rstp-bpdu-mac|rstp-edge|bpduguard|immediate-leave|ingress-policy-map|split-horizon-fwd|lacp-role|lacphash-method|lacp-min-ports|lacp-max-ports|lacp-system-priority|lag-crosscard|lag-cross-card-revert|trusted|ethertype|admin-state]
To create or configure a LAG interface for service
1. On the Navigation Tree, click Interfaces.
2. Either create or modify a LAG interface:

To create a LAG interface, click Create.

To modify an existing LAG interface, in the table of Ethernet port interfaces, doubleclick the row that shows the interface you want to configure.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
86
3. Reference the table above to configure the parameters.
4. Click Create or Apply.
Note: Before you can assign a port to a LAG interface, you must disable the port's default
associated interface. When a port is assigned to a LAG, the LAG interface provisioning (for
example, VLAN membership) applies to the port. See Configuring an Ethernet Port (on page 67)
for details on how to add ports to the LAG interface.
For CLI:

create interface <interface name> (name is case sensitive) role
<trunk|edge>

disable interface <interface name> (name is case sensitive)

delete interface <interface name> (name is case sensitive)

set interface <interface name> (name is case sensitive)
Example:
create interface “MyLAG” role trunk description “LAG to 3750”
Creating the Service VLAN(s)
This topic shows you how to create a virtual LAN (VLAN) or transparent LAN (TLAN) to
segregate traffic for different services or subscribers on the same network and separate
device management control messages from traffic. See Provisioning VLAN Ranges (on page
104) if you want to create a set of VLANs with similar settings.
Native VLAN and untagged traffic
By default, every Ethernet port with an associated interface role of Trunk or Edge is a
member of VLAN 1, the Native VLAN. The Native VLAN is available to pass any untagged
traffic. You can provision an Ethernet port interface to use a different existing VLAN as the
Native VLAN.
Ethernet ports with an associated interface role of Access do not support a Native VLAN,
however, tag actions can be used to match untagged traffic to a VLAN ID.
Note: If you are configuring the E7 for in-band management, create a VLAN dedicated to
management traffic. Do not put management traffic on the Native VLAN (default is VLAN
1).
Note: For Ethernet services, VLAN tags provisioned on an Edge or Access link interface are
only passed.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
87
VLAN tagging and provisioning models
The E7 provides standards-based VLAN tagging, and Q-in-Q VLAN stacking support.
VLAN tagging was developed as a means to allow multiple networks to transparently
traverse the same physical network. When a service is provisioned at an xDSL or ONT
subscriber port, a match list and service-tag action specify the classification and marking of
packets from the subscriber port into the service VLAN.
VLAN-per-service provisioning model (N:1): When VLANs are provisioned to separate
traffic onto VLANs based on the type of service carried in the traffic. For example, IPTV
traffic is carried on a separate VLAN from data and voice traffic. A service carried on an N:1
VLAN applies to multiple subscriber ports, where a single match list and tag action can
indicate the service. To isolate subscriber traffic, you must enable MAC Forced Forwarding
(MACFF).
VLAN-per-port provisioning model (1:1): When VLANs are provisioned as a unique
customer or port identifier, VLAN C-tags (customer tag) are utilized to create a VLAN per
customer / port association. A service carried on a 1:1 VLAN is the same for each subscriber
except the customer tag is unique per subscriber, you can define the match list and tag action
pair such that multiple subscriber ports can reference it. This is accomplished by having a
special value for the output tag in the tag action, indicating that the value of the output tag is
subscriber specific. The customer-specific tag is contained in the Service object.
VLAN stacking or Q-in-Q provisioning model: The ability to add multiple VLAN tags
enables the following functionality:


Expands the addressable VLAN space from 4094 VLANs to over 16 million VLANs
Allows logical separation and trunking of VLANs through a network by using a VLAN
tag to group a larger range of VLAN tags together
The most common way to use VLAN stacking is by inserting two tags on the traffic. These
tags are typically referred to as the inner tag or C-tag and the outer tag or S-tag. As stated
previously, the C-tag, also known as the customer tag is used to uniquely identify a customer,
typically is used on a per port basis. The S-tag, also known as the service-provider tag is used
to logically group C-tags together.
Metro Ethernet Forum (MEF)/Transport LAN (TLAN) business service models:
MEF/TLAN service can transparently trunk business traffic across a network to other
locations, typically a remote office or secondary business location. The traffic received from
the business may be untagged, single-tagged, or double-tagged. The E7 adds an outer tag to
all frames to create a private switched LAN with two or more end points.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
88
VLAN Traffic flow in VDSL2 and GPON Cards
Since xDSL and GPON Ethernet ports have no interface association, unlike the Ethernet
ports, rather than adding a port interface to a VLAN membership to enable traffic flow, a
service-tag action must be created that specifies the VLAN. This service-tag action is then
referenced when the service is provisioned on the xDSL or ONT port. The VLAN must
already be created on the system for an xDSL or GPON port to pass traffic carried on a
VLAN.

To view the VLANs associated with specific port, click the port of interest on the
Navigation Tree, and then click the VLANS tab.

To view the VLANs associated with a port, click ONTS on the Navigation Tree, and
then click the VLANS tab.
To view the services associated with a specific VLAN, click VLANS on the Navigation
Tree, click the particular VLAN from the list that appears in the Work Area, and then
click the Service Associations tab.

VLAN with IGMP Snooping and multicast IP addresses
The E7 supports industry standard IETF RFC 4541 IGMP snooping of multicast video leave
and join requests sent between the set-top box and the video distribution network.
IGMP snooping enables the E7 to determine which ports should be a member of a multicast
group. It can provide a local response if the channel already exists on the system or it will
forward those requests upstream to a multicast router or another IGMP snooping Ethernet
switch. When multicast channels are received from the network, the E7 forwards the
channels to all ports that are currently members of the requested IGMP membership group.
The ability to perform snooping can be enabled on a per VLAN basis. If multicast traffic is
received on a VLAN where IGMP snooping is not enabled (flood), the traffic is handled as
broadcast traffic and sent to all ports on the VLAN.

Passive IGMP snooping (snoop-suppress), augmented with report suppression reduces
the number of general query and group specific reports sent to the multicast router
(querier).
Note: The suppress-snoop parameter does not apply to the E7-20, as it only supports
proxy for IGMP.

Active IGMP Snooping (IGMP Proxy), becomes capable of acting as a general querier
and thus takes an active role in maintaining the IGMP multicast network. When the
IGMP mode is set to proxy, an IGMP profile must be referenced from the VLAN. In
addition to general querier timing parameters, the following IGMP attributes per
multicast VLAN are supported:

Robustness parameter (number of times E7 sends out a general query)

Last member query interval

Immediate leave option

Static multicast router interface

Router learn mode
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
89
IGMP Proxy provides additional scalability to the IGMP network, reducing the IGMP
signaling load on the multicast router.
Additional multicast addressing considerations
In accordance with RFC 4541 (section 2.1.2), the E7 automatically passes multicast IP
addresses in the 224.0.0.x address range (defined as link-local) through the system on VLANs
with IGMP Snooping mode set to snoop-suppress or proxy (snooping enabled). For
example, the following 224.0.0.x multicast addresses are reserved for specific routing
protocols, and forwarded automatically on the E7 without a corresponding join request.
HSRP HELLO
DVMRP
OSPF ALL RTR
OSPF DES RTR
RIP
224.0.0.2
224.0.0.4
224.0.0.5
224.0.0.6
224.0.0.9
EIGRP
PIM
VRRP
HSRP
MLS ALL
SNOOPERS
224.0.0.10
224.0.0.13
224.0.0.18
224.0.0.102
224.0.0.106
If reserved 224.0.0.x multicast addresses are assigned to video channels in your lineup, the E7
will flood these channels to all ports on IGMP Snoop enabled VLANs, which could
potentially consume available bandwidth on subscriber links and result in tiling. Therefore,
Calix recommends NOT using 224.0.0.x (or any of the 32 multicast IP addresses that are not
unique at the L2/MAC address level) for video channel assignments. See Calix Quick Tip E7
QT-12-003 for more information.
For VLANs with IGMP Snooping set to flood (no snooping), the E7 passes all multicast
traffic transparently.
Service Security
The E7 supports the following service security features that are defined when the VLAN is
created. If using a N:1 VLAN model for services, Calix recommends enabling MAC Forced
Forwarding (MAC FF) and IP Source Verify (IPSV) when creating the VLAN, where
appropriate. The VLAN Per Service model is susceptible to MAC spoofing unless MACFF
and IPSV are enabled.


IP Source Verification ensures that only data from IP addresses learned by DHCP
snooping or static provisioning are allowed to ingress ONT Ethernet ports or xDSL
ports.
MAC Forced-Forwarding ensures that traffic from one subscriber interface cannot be
sent directly to another, reducing the chance that malicious traffic can be transmitted
between ports.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
90
Reserved VLANs
To ensure a wide range of access deployments, the E7 supports an extremely flexible VLAN
support model. For future development support, the E7 reserves four VLAN values. The E7
requires these VLANs always be identified. The default values for these VLANs are 1002,
1003, 1004, and 1005. It is possible to change these four values to be some other set of four
consecutive VLANs, if required using the basic system settings.
AE ONT Discovery
When a Calix AE ONT is attached to an E7 untrusted Ethernet port, the E7 system can send
the Discovery event as an SNMP notification (trap or inform message) to CMS regarding the
newly discovered AE ONT, as configured by the “snmp trap-dest” provisioning.
Note: CMS automatically adds its IP address as a trap destination when adding an E7 to
CMS.
The VLAN configured at the untrusted Ethernet port must have both the AE ONT
Discovery function and the DHCP Snooping function enabled for the E7 to initiate the
SNMP notification of an AE ONT discovery.

When you enable DHCP Snooping and AE ONT Discovery on a VLAN, the following
sequence occurs:
a. DHCP messages received by the E7 DHCP Snooping agent at “untrusted” Ethernet
interfaces are examined to identify messages that are originated by the Calix AE
ONT (DHCP Message with Option 60: Vendor class identifier value = “Calix
ONT”).
b. A lease is granted by the DHCP Server to the AE ONT, triggering the AE ONT
Discovery event where the ONT is dynamically linked with specific GE port it
reported on, and will show up on the navigation tree.
The event report includes the following fields:
♦ MAC address of the AE ONT
♦ VLAN
♦ Interface where the AE ONT is discovered
c. The lease is first added to the binding table maintained by the DHCP Agent.
Note: If the lease is already present in the DHCP lease table (assuming DHCP Snooping
is enabled) and AE ONT Discovery is enabled after a DHCP exchange, no event is
reported. Therefore, it is important that you enable both AE ONT Discovery and DHCP
Snooping when first configuring the VLAN attributes of the AE ONT management
VLAN.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
91
Note: The AE ONT discovery feature only supports Calix AE ONT release 2.0 or
higher with dynamically assigned IP addresses and with DHCP Option60 (Vendor class
identifier value = “Calix ONT”).

When you do NOT enable the AE ONT Discovery on a VLAN, yet you want
configured AE ONTs linked frequently, you will need a separate, more frequent
MAC/IP Host only scheduled inventory task run often (daily) to collect the MAC
information for linking.
VLAN Association to voice services
The IP Host object references a service tag action that indicates the voice service VLAN by
one of the following methods:

An IP host can directly specify an outer tag, when the referenced service tag action states
"Specified in Service" for the Outer Tag parameter.
This allows you to apply a different VLAN tag for the same service type (SIP, TDM
gateway, H.248 gateway, MGCP, or T1 PWE3) on each ONT.

An IP host can reference a service tag action that specifies the service VLAN ID for the
provisioned voice services.
This allows you to apply the same VLAN tagging for all ONTs that use the referenced
service tag action object.
Note: The VLAN assignment must be different between the VoIP IP host and the
subscriber port. Sharing VLANs between a subscriber port and a VoIP IP host is not
supported. Deploy VoIP service using the VLAN Per Service model; it is a captive
VLAN that is not open to subscribers.
Configuration guidelines

VLAN-Per-Service Model (N:1):

The VLAN Per Service model requires fewer VLANs than the VLAN Per Subscriber
model.

To isolate subscriber traffic, you must enable MAC Forced Forwarding (MACFF).
The VLAN Per Service model is susceptible to MAC spoofing unless MACFF and
IPSV are enabled.

This model provides the most bandwidth-efficient way of distributing multicast
content to all access nodes for video service.

Isolation of multicast traffic provides the flexibility to size a video VLAN without
having to address unnecessary multicast replication on the access network.

The P-bit value defined for a service VLAN must be consistent with the Class of
Service (CoS) type.

Deploy VoIP service using the VLAN-Per-Service model; it is a captive VLAN that
is not open to subscribers.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
92











Limit broadcast traffic and Address Resolution Protocol (ARP) requests by
configuring smaller subnets, each on a unique VLAN.

Do not create a large VLAN space with a large associated subnet space.

Set the broadcast domain size so that devices in the domain are not overwhelmed
with packets during peak traffic events (for example, following a power outage all
network devices may request IP addresses simultaneously).
VLAN-Per-Subscriber Model (1:1):

Each subscriber is assigned a unique VLAN, and VLANs belonging to the same
access node are grouped under a single VLAN.

Because MAC addresses are learned on a per VLAN basis, the VLAN Per Subscriber
model provides MAC address isolation, protecting the network from MAC collisions,
with the following exceptions:

A broadcast domain is limited to a single access node and the router, making it easier
to manage the broadcast load.
Even if no interface is currently using VLAN 1 as the Native VLAN, it is still off limits
for user provisioning, including use as the Management VLAN or ERPS control VLAN.
The E7 reserves four VLAN values for system operation. The default values for these
VLANs are 1002, 1003, 1004 and 1005. You can change these values to another set of
four consecutive VLANs, if required.
For an E7 Ethernet port interface to pass traffic carried on a VLAN, the interface must
be added to the VLAN membership, or specified as the target in a tag action.
You can configure only one of the following attributes on a given VLAN on a given E7
Ethernet port interface:

VLAN membership

Tag-action (edge and access interfaces only)

Native VLAN (edge and trunk interfaces only)
For an xDSL or GPON port to pass traffic carried on a VLAN, a service tag action must
be created specifying the VLAN.
For Home Gateway services, the first service VLAN is required to be assigned to High
Speed Internet services. It has additional attributes which define the management mode,
WAN protocol and required configuration or credentials.
The T-Series supports four independent WAN VLANs (High-Speed Internet, IPTV,
VoIP, TR-069). The RG config file "NAT enabled" attribute controls which of these
VLANs are routable from the LAN. By default, only the HSI WAN is routable.
Static/Default routes assigned to other WAN's require NAT to be enabled before you
can access them from the LAN.
The E7 Management VLAN needs to have a VLAN ID that is unique and different from
any service VLAN, including the RG management profile VLAN used for TR-069.
For GPON or xDSL VLANs that need to carry IPv6 traffic, enable the VLAN TLAN
parameter for transparent passthrough of IPv6 traffic.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
93












IPv4 and IPv6 are supported simultaneously, when the following provisioning criteria are
met:

The DHCP Snoop is enabled on the S-VLAN

Option 82/LDRA Enabled is selected on the shelf

The Ethernet uplink interface Trusted parameter is enabled
IGMP snooping is only enabled on the outer VLAN ID as multicast traffic is typically
transported throughout the network with a single VLAN ID tag.
All nodes in an ERPS ring must have the same IGMP Snooping provisioning on the
video VLAN for traffic to flow--either all with snooping (snoop-suppress, proxy) or all
without snooping (flood).
T-series and L2 IGMP-controlled multicast:

T-Series supports multiple VLANs, but only supports a single service provider and
requires channel independence across VLANs.

Different VLANs on different LAN ports share query domains and are treated as a
single video service by the ONT.

The ONT has a single proxy agent and does not consider the transport VLAN when
filtering channels. The only relevant information is the layer-3 IP address.
An operator may manually delete a lease entry from the table. However, if an IP Source
Verification is enabled on the VLAN, deleting the DHCP lease entry results in the
subscriber traffic being dropped until the subscriber’s IP host requests, and is granted, a
new IP address using DHCP.
When DHCP snooping is enabled on a subscriber VLAN, the E7 drops all DHCP server
communication originating from subscriber Ethernet interfaces. Calix recommends
DHCP snooping be enabled for all residential subscriber services, and that redundant
DHCP servers are included in the equipment configuration.
In the VDSL2 and GPON subsystems, DHCP leases cannot be learned without also
applying a limit to the number of learned leases on the port. Each Ethernet port has an
associated Port Security Profile that can limit DHCP leases in a range of 1-16. A security
profile used by an xDSL port must have a DHCP lease limit value of 10 or less.
When DHCP snooping is enabled, DHCP requests for VLANs do not appear in an E7
port mirror session.
The craft management ports cannot use IP addresses from the same subnet where
DHCP Snooping is enabled.
DHCP snooping is not supported on management VLANs.
DHCP Snoop must be enabled on the VLAN to support the AE Discovery Event
operation.
Simultaneous operation of DHCP Snooping and PPPoE are not supported. When a
PPPoE profile is selected, the DHCP features are disabled. See Configuring PPPoE
Operation for a Data Service (on page 283) for more information.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
94

For E7 VDSL2 and GPON, IP and MAC addresses may be dynamically learned using
either DHCP Snooping or manually provisioned with static IP/MAC addresses. Services
with static subnets (without MAC address specification) may also be provisioned for IP
Source Verification, but are bound to the port only by IP address. See Adding Static IP
Host Addresses and Subnets (on page 280).

DHCP and Static IP host: Binds IP and MAC address to a Port

Static IP Subnet: Checks individual host IP addresses to the subnet and binds the
subnet to a port
The E7 GPON systems have the following limits on the number of IP stations
(active DHCP leases, static IP hosts, and dynamically learned hosts within a static
subnet):
♦ The ONT supports up to 256 “IP stations” per ONT Ethernet port.
♦ The ONT supports up to 1024 total “IP stations” per ONT.
 The following capacities apply to Static IP Addresses/Subnets within the E7
VDSL2 subsystem.
♦ 1 Static IP subnet can be provisioned per xDSL Ethernet service.
♦ 4 Static IP hosts can be provisioned per xDSL Ethernet service.
♦ 8 Static IP hosts/subnets can be provisioned per xDSL port, across all
services.
♦ 256 Static addresses total per port (includes static addresses and sizes of static
subnets)
♦ 16 DHCP Leases per port (defined in the Ethernet Security Profile with a
default setting of 8).
Disabling MAC Learning causes traffic within the VLAN to be flooded to all egress
interfaces with membership in the VLAN, which can degrade throughput.
Disable MAC Learning for MEF point-to-point Ethernet Private Line (EPL) and
Ethernet Virtual Private Line (EVPL) services to allow service delivery without the E7
adding any subscriber MAC addresses to the E7 forwarding table.
Disabling MAC Learning should only be done with point-to-point services and is NOT
appropriate for a multi-point Ethernet-LAN (ELAN) service or other VLAN-per-service
applications.
MACFF can only be used in conjunction with DHCP Snoop.
MACFF can only be used in conjunction with DHCP Snoop, where you first enable
DHCP Snoop, wait a lease cycle, and then enable MACFF.
For T-series ONT peer-to-peer voice service, PON Hairpin or MAC-FF must be
enabled.
Enable MACFF to limit broadcast traffic on the VLAN domain when using the VLAN
Per Service model. It is not required for the VLAN per Port (single and double-tagged,
Q-in-Q) data model or PPPoE because this VLAN model by definition limits the
broadcast domain to a single access node and the router and makes it easier to manage
the broadcast load. However, MACFF should still be enabled on these VLANs.








Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
95









For E7 VDSL2 or GPON, MAC Forced Forwarding (MAC FF) can be used with the
following IP hosts:

IP hosts learned via DHCP Snooping

IP hosts statically provisioned (IP and MAC)

IP hosts statically provisioned (IP address only)

IP subnets statically provisioned (single IP address/MAC)
MAC Forced Forwarding supports a single source MAC address with multiple source IP
addresses, when the MAC address is not specified.
For E7 VDSL2 or GPON, MAC FF can be used with static IP subnets. See Adding Static
IP Host Addresses and Subnets (on page 280).
The E7 GPON system has the following limits for the PON Hairpin feature:

PON Hairpin capacity limitation of 2.4Gbps of traffic on a per GPON-4 card basis.
This is equivalent to 50% of the total upstream PON bandwidth capacity (using 4
PON interfaces). There is no limitation on the amount of traffic that can be switched
between GPON OLT ports on the same GPON-4 line card or between E7 cards.

The 2.4Gbps capacity is shared by GPON-4 OLT ports, thus 2 of the PON ports
can have 100% of their capacity hairpinned. If capacity is equally distributed each
PON port can have 600Mbps of hairpinned traffic.

If the 2.4Gpbs capacity is exceeded than the GPON-4 subsystem will go into
congestion and will drop packets.

The VLAN PON Hairpin function is not compatible with DHCP Snoop, IGMP
snoop, MAC Forced-Fwd, or IP Source Verify.
IGMP snooping is provisioned on a VLAN basis and is recommended for VLANs
carrying video services and should be avoided for VLANs in a Transparent LAN Service
(TLS).
The default behavior for data services is to filter all multicast traffic upstream from an
ONT Ethernet port or xDSL port, unless the TLAN parameter is enabled on the VLAN.
For VLANs that are carrying IPv6 multicast traffic, enabling (selecting) this feature
allows a passthrough of the IPv6 traffic.
Channels not joined by a subscriber on the ONT are dropped at the ONT. Channels not
joined by any ONT on the PON are dropped at the GPON OLT port.
The GPON card supports up to 32 IGMP-enabled multicast VLANs on the system,
which can all be on the PON.

For 1:1 provisioning model, the C-tag must be unique for each subscriber.

For N:1 provision model, the C-tag must be unique for each service.

For a double-tagged model, each of the inner tags must be unique.

For a single-tagged model, each of the tags must be unique.
A VLAN can only be deleted if it is NOT referenced by a tag action, a service tag action,
a provisioned service, or a voice service IP Host.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
96

E7 system supports the unrestricted use of C-Tag VLAN ID values in combination with
any S-Tag value, across any service end-point on an E7 system, regardless of PON port,
line card, or shelf.
With the following exceptions:

A C-Tag (or single-tagged S-Tag) may not be re-used on an individual ONT Ethernet
port (UNI).

An S-tag may not be re-used for a C-tag of another service on the same PON. For
example, when a VoIP service uses S-tag 200 for all subscribers, and a Data services
uses S-tag 100, the VoIP S-tag may not be re-used as a Data service C-TAG 200 (100,
200) on a given PON. The recommended practice is to ensure the S-Tag range is
outside of the subscriber C-Tag range.

An MVR VLAN may not match the outer tag specified by any service-tag action or
Ethernet service.

An MVR VLAN may not match the inner tag specified by any service-tag action or
Ethernet service.
Parameters
You can provision the following parameters for VLANs:
Parameter
Description
Valid Options
ID*
VLAN ID for the VLAN you are creating.
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
Name
Name of VLAN that is descriptive of the VLAN use. For example, VoIP
or Management.
String of 31 characters
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
97
Parameter
IGMP Mode
Description
IGMP mode for the VLAN. Calix recommends that VLANs used for
video services be set to suppress-snoop or proxy (enable snooping).

snoop-suppress (E7-2 or Modular Chassis systems only): Enables
IGMP snooping (with report suppression) on the VLAN to manage
the multicast group memberships of subscriber ports. The IGMP
capability ensures that only multicast channels which are joined by
a particular set-top box (STB) appear on the subscriber network. All
nodes in an ERPS ring must have the same IGMP Snooping
provisioning on the VLAN for video traffic to flow--either all enabled
or all disabled.
Valid Options
snoop-suppress
proxy
flood ‡
Within the IGMP protocol, the querier generates the following
messages:
--A General Query message is generated where all devices which
are joined to any group respond with a Report message.
--A Group Specific Query message is generated where the specific
group responds with a Report message.
The messages and reports can generate a lot of IGMP activity in a
large network. Report suppression allows intermediate devices,
between the querying router and the multicast consumer host, to
suppress duplicate Report messages within the response timer
window, in order to reduce the amount of IGMP traffic that must be
processed higher in the network. Disabling Report Suppression
allows more Report messages to be allowed up through the
network.

proxy: Causes the E7 to act as an IGMP v2 proxy for all STBs,
sending join/leave requests to the upstream IGMP router/content
provider as required. This provides a more robust IGMPv2
implementation, scaling to the maximum number of subscribers and
channels. When the IGMP mode is set to proxy, an IGMP profile
must be referenced from the VLAN on all E7s that have a video
VLAN with the IGMP Proxy setting. The E7-20 only supports proxy.

flood: Disables IGMP snooping and proxy. If multicast traffic is
received, IGMP traffic is forwarded through and multicast traffic is
forwarded to all member ports on the VLAN. The G.8032v2 ring
video only supports flooded IGMP mode.
Note: Recommended for VLANs not carrying multicast
traffic.
IGMP Profile
Name of the IGMP profile to associate with the VLAN. This profile only
applies if the IGMP mode is set to proxy. You can select the system
default profile or another existing IGMP profile.
system-default ‡
any existing profile
DHCP Snoop
Whether to enable DHCP snooping to track all DHCP activity on that
VLAN and create/update a table of DHCP leases granted. Calix
recommends DHCP snooping be enabled for all residential subscriber
services, and that redundant DHCP servers are included in the
equipment configuration.
cleared (disabled) ‡
selected (enabled)
Note:

When DHCP Snoop is enabled, MAC Learning is disabled by
default.

Maximum number of service VLANs with DHCP Snoop enabled, per
VDSL2 line card = 48.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
98
Parameter
MAC Forced-Fwd
Description
(VDSL2 and PON only) Whether to enable MAC Forced Forwarding
(MAC FF) which screens upstream packets at the ONT Ethernet port or
xDSL port and only allows through those packets with a destination
MAC address (DMAC) that matches the upstream access router.
Valid Options
cleared (disabled) ‡
selected (enabled)
MACFF can only be used in conjunction with DHCP Snoop, where you
first enable DHCP Snoop, wait a lease cycle, and then enable MACFF.
Calix recommends MAC Forced Forwarding be enabled for all
residential and business internet access services. MAC FF supports the
following:

IP hosts learned via DHCP Snooping

IP hosts statically provisioned (IP and MAC)

IP hosts statically provisioned (IP address only)

IP subnets statically provisioned (single IP address/MAC)
Note: Maximum number of service VLANs with MAC Fored-Forwarding
and/or IP-Source-Verify enabled, per VDSL2 line card = 48.
Note: For T-series ONT peer-to-peer voice service, PON Hairpin or
MAC-FF must be enabled.
IP Src Verify
(VDSL2 and PON only) Whether to bind the IP address and MAC
address to the physical ONT Ethernet port or xDSL port, preventing
subscribers from assigning an IP address to a device and passing traffic
on it. IP Source Verification for Static IP hosts requires MAC FF be
enabled. Calix recommends IP Source Verification be enabled for all
residential and business internet access services.
cleared (disabled) ‡
selected (enabled)
Note: Maximum number of service VLANs with MAC Fored-Forwarding
and/or IP-Source-Verify enabled, per VDSL2 line card = 48.
MAC Learning
Controls MAC address learning. This parameter control only applies to
standalone E7-2 systems.

E7-20 and E7-2 in Modular Chassis mode only support MAC
Learning enabled.

E7-2 system cannot be set to Modular-Chassis mode while any
VLAN has MAC Learning disabled.
cleared (disabled)
selected (enabled) ‡
Calix recommends leaving MAC Learning in the default enabled mode.
AE Discovery Event

Disabling MAC learning causes traffic within the VLAN to be flooded
to all egress interfaces with membership in the VLAN.

Disabling MAC Learning and DHCP Snooping, and enabling MAC
Forced-Fwd, causes all downstream packets to be flooded.

Enabling DHCP Snoop, sets MAC Learning to disabled by default.
Whether the E7 sends an event to CMS whenever a new Calix AE ONT
is discovered on an untrusted port. When enabled, an event is sent for
any new lease added to the binding table entries belonging to AE
ONTs. If the lease for the AE ONT already existed in the table at the
time of enabling the feature, an event will not be sent.
cleared (disabled) ‡
selected (enabled)
Note: DHCP Snoop must be enabled on the VLAN to support the AE
Discovery Event operation.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
99
Parameter
TLAN
Description
(VDSL2 and PON only) Whether to enable PON or xDSL transparent
LAN service which disables Ethernet Security Profiles, MAC Forced
Forwarding, DHCP Lease Limits, or Upstream Broadcast Limits that
were applied to the ONT Ethernet port or xDSL port with the associated
VLAN.
Valid Options
cleared (disabled) ‡
selected (enabled)
Note: For TLAN to be enabled all of the following must be/remain
disabled: DHCP Snoop, MAC Forced Forwarding, IP Source Verify, and
IGMP Mode must be/remain Flood (no snooping).
Note: The default behavior for data services is to filter multicast traffic
upstream from an ONT Ethernet port or xDSL port, unless the TLAN
parameter is enabled on the VLAN. For GPON or xDSL VLANs that
need to carry IPv6 traffic, enable the VLAN TLAN parameter for
transparent passthrough of IPv6 traffic.
PON Hairpin
(PON only) Whether to enable PON hairpin which allows traffic to flow
upstream from an ONT Ethernet port and back downstream on the
same PON to another ONT Ethernet port. Hairpin of services in the
PON requires additional resource allocation in the GPON subsystem
and should not be enabled unless hairpin service is required.
cleared (disabled) ‡
selected (enabled)
Note: For PON Hairpin to be enabled, all of the following must
be/remain disabled: DHCP Snoop, MAC Forced Forwarding, IP Source
Verify.
Note: Supported for TLAN and T1/E3 PWE3 services.
Note: For T-series ONT peer-to-peer voice service, PON Hairpin or
MAC-FF must be enabled.
PPPoE Profile
Assign a previously-created PPPoE profile. When a PPPoE profile is
selected, the DHCP features are disabled. See Creating a PPPoE
Profile (on page 186) for instructions.
any available PPPoE
profile
Note: For PPPoE to be enabled, all of the following must be/remain
disabled: DHCP Snoop, MAC Forced Forwarding, IP Source Verify.
*Required field
‡ Default
To create a VLAN
1. On the Navigation Tree, click VLANs.
2. In the Work Area, click Provisioning > Create to open the Create VLAN dialog box.
3. Reference the table above to configure the parameters.
4. Click Create.
For CLI:

create vlan <vlan ID> [name|mac-learning|mac-forced-forwarding|ipsource-verify|pon-hairpin|pon-tlan|igmp-mode|igmp-profile|dhcpsnooping|ae-ont-discovery|pppoe-profile]

delete vlan <vlan ID>

show vlan [vlan id|detail|igmp-counters|members|onts]

show vlan <vlan id> [detail|igmp-counters|mac|mcast|members|onts]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
100
Configuring DHCP Relay Option 82 and LDRA
This topic shows you how to configure the global DHCPv4 L2 Relay Agent (Option 82) and
Lightweight DHCPv6 Relay Agent (LDRA) features. Option 82 applies to all VLANs with
DHCP Snooping enabled, and LDRA applies to VLAN per Service data models with DHCP
Snooping enabled. These features are enabled simultaneously to add information to DHCP
requests that are relayed to a DHCP server to authenticate the source of the requests. See
RFC 3046, RFC 6221, and RFC 3315 for more information.
The E7 implementing LDRA performs a link-layer bridging (i.e., non-routing) function.
LDRA resides on the same IPv6 link as the client and a DHCPv6 Relay Agent or server, and
is functionally the equivalent of the Layer 2 DHCP Relay Agent for DHCPv4 operation.
Both IPv4 and IPv6 are supported for data services simultaneously on VLAN per Service
models in all Layer 2 topologies when the following conditions:



The "DHCP Snoop" is enabled on the S-VLAN
“Option 82/LDRA” is enabled on the E7 or E3/E5 unit or shelf
The Ethernet uplink interface is set for "Trusted=Y"
The two sub-options of Option 82 are defined in RFC 3046:

Agent Circuit-ID (intended for circuits terminated by the system hosting the Relay
agent)

Agent Remote-ID (intended to identify the remote host end of a circuit)
The two sub-options of LDRA are defined in RFC 3315:

Agent Interface-ID (equivalent to Option 82 Circuit-ID option in DHCPv4)

Agent Remote-ID (equivalent to Option 82 Remote-ID option in DHCPv4)
The LDRA sub-options are derived from the DHCP Option 82 Circuit-ID and RemoteID sub-options using the same format, and are not user-defined.
When DHCP Option 82/LDRA is enabled, Relay Agent identification information is
inserted into DHCP messages captured at the "Untrusted" interfaces and sent to the
DHCPv6 server by applying a system-defined access-identifier profile. The sent "Agent
Interface-ID" is equivalent to the DHCPv4 Circuit-ID information, and "Agent Remote-ID"
is equivalent to the DHCPv4 Remote-ID information.


The "eth-system-default" profile is applied to Ethernet and xDSL ports.
The "gpon-system-default" profile is applied to E7 GPON ONT Ethernet ports.
Ethernet interfaces are identified as either "Trusted" or "Untrusted."


Untrusted interfaces are snooped for client DHCP traffic.
Trusted interfaces are snooped for DHCP server traffic.
Note: All E7 GPON ONT Ethernet ports are implicitly Untrusted and the “Trusted”
attribute cannot be configured.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
101
When DHCP snooping is enabled on a VLAN, the E7 tracks all DHCP activity on that
VLAN within the system and maintains a table of DHCPv4 and DHCPv6 leases granted.
You can retrieve the table of granted leases via any of the management interfaces containing
the following attributes, which may be searched or filtered: VLAN ID, IP address, MAC
address, ONT port.
Neighbor Discovery Protocol (NDP) flood control is enabled automatically with LDRA
when DHCP Option 82 insertion is enabled. NDP flood control prunes NDP messages so
only IP hosts discover the access router. In order to enable visibility into the NDP flood
control processing, the E7 provides a number of counters such as all packets forwarded and
discarded on a per packet type basis, and access to the NDP cached entries. This information
can be accessed via CLI, EWI and CMS.
Upstream (client to server) DHCP packets captured on Untrusted interfaces, will have
the following Option 82 information inserted:
Note: LDRA sub-options are derived from the Option 82 Circuit-ID and Remote-ID suboptions using the same format.

Ethernet and xDSL ports:

Circuit-ID options:

Calix-format: <system-ID> eth <shelf>/<slot>/<port>:<Vlan-Id>[-<VlanId>]

TR-101-format: <system-ID> <iftype>
<shelf>/<slot>/<tr101port>:<cetag>[-<tag-Id>]
♦ The TR-101 iftype should be either “eth” or “atm” (must be all lower case).
♦ The TR-101 cetag should be one of 3 formats:
:vpi.vci for DSL lines/groups that are trained in ATM mode (tagged or
untagged)
:ce-vlan-id for tagged subscribers that are either PTM DSL lines/groups or
ONT
Null for untagged subscribers that are either PTM DSL lines/groups or ONT
Note: If the xDSL port is a member of a bonded link group, the port within the xDSL
bonded link group with the lowest port value will be selected to fill the <port> field in
the Circuit-ID string.

Remote-ID options:

Subscriber ID of the port on which the DHCP lease request is received. The first
64 characters of the Subscriber ID text field are inserted.

none (no content is inserted)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
102

E7 GPON ONT Ethernet ports:


Circuit ID options:

Calix-format: <system-ID> eth
<shelf>/<slot>/<port>/<OntID>/<Ontport>:<Vlan-Id>[-<Vlan-Id>]

TR-101-format: <system-ID> eth
<shelf>/<slot>/<port>/<OntID>/<Ontport>:<cetag>[-<tag-Id>]
Remote-ID options:

ONT FSAN serial number, which is the default, specified in the "gpon-systemdefault" profile.

Subscriber ID of the port on which the DHCP lease request is received. For
ONT VoIP hosts, the subscriber ID of the ONT is used. In both cases, the first
64 characters of the Subscriber ID text field are inserted.

none (no content is inserted)
Note: The default Calix format will have a defining letter for the port (x,g,v,etc) followed
by the port number. The TR101 format will have a defining letter for the port followed
by the port number, except for the VDSL ports which will be only the port number (no
leading letter 'v').
Downstream (server to client) DHCP packets will be captured and examined on Trusted
interfaces.


If a session match is found for an interface, the Option 82/LDRA string is removed if
Option 82/LDRA is enabled globally, and then the packet is delivered to the Ethernet,
xDSL, or ONT Ethernet port interface where the lease request originated.
If a session match is not found, the DHCP packet will be forwarded unchanged on either
the port for which the MAC is learned, or on all "Trusted" interfaces belonging to the
VLAN (in case of broadcast DHCP packets).
All packets received on Untrusted interfaces that already have DHCP Relay Agent
information will be dropped.
Configuration guidelines
The following additional constraints only affect VLANs with DHCP Snooping that are
provisioned on Ethernet and xDSL port interfaces and where the global DHCP relay Option
82/LDRA is enabled:



DHCP snooping and Option 82/LDRA are not supported on the Management VLAN.
Ethernet interfaces used for LAG or ERPS links cannot be set to “Untrusted.”
If a line card reboot or reset occurs, the DHCP lease database for all ports (xDSL,
GE/10GE, GPON) persists.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
103
The following guidelines apply to LDRA only:









LDRA cannot be enabled independently from Option 82.
LDRA is automatically enabled on any VLAN with DHCP Snoop enabled.
LDRA is supported for data services on VLAN per Service models only.
IPv6 residential gateways (RGs) are required for the VLAN per Service data model.
Access interfaces support IPv6 transparency only (no LDRA or NDP flood control) for
TLAN point-to-point, TLAN multi-point, and VLAN-per-port topologies.
E7-2 and E3-48C 10GE and E5-48 and E5-48C GE access interfaces support LDRA,
but are not expected to be subscriber-facing.
Edge interfaces do not support LDRA on received RELAY-FORWARD and RELAYREPLY messages.
Tag actions can be applied to untagged or single-tagged subscriber traffic processed by
LDRA, including:

GPON ONT / ETHERNET / VDSL subscriber untagged with tag action: Add Tag

GPON ONT / ETHERNET / VDSL subscriber single tagged with tag action:
Change Tag

GPON ONT / ETHERNET / VDSL subscriber single tagged with VLAN
membership

GPON ONT subscriber untagged with tag action: Add 2 Tags
Security features not supported for IPv6 traffic include: MAC FF, IP Source Verification,
and static IPv6 host entries.
To configure DHCP Option 82/LDRA insertion
1. On the Navigation Tree, select E7.
2. In the work area, click DHCP > Provisioning to open the DHCP Configuration form.
3. In the Option 82/LDRA Enabled checkbox, select the checkbox to enable this feature.
4. In the Option 82 Policy list, select whether to drop or overwrite packets with Option 82
on ingress packets.
5. In the toolbar, click Apply.
6. To specify the Remote-ID or Circuit-ID attributes on the global option 82 profile for E7
networks, use the procedure shown below.
For CLI:
set dhcp-cfg option-82 [enabled|disabled]
set dhcp-cfg option-82-policy [drop|overwrite]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
104
To configure the global access-identifier profiles
1. On the Navigation Tree, select E7.
2. In the work area, click Profiles > Access Identifier to view the table of default accessidentifier profiles.
3. Double-click the name of the profile that you want to configure:

eth-system-default is used for xDSL and GE ports.

gpon-system-default is used for GPON ONT ports.
4. In the Access Identifier Profile form, select the parameter from the attribute list:


Circuit ID list parameters:

calix-format

tr101-format
Remote ID list parameters:

ONT FSAN serial number is the default specified in the "gpon-system-default"
profile.

Subscriber ID of the port on which the DHCP lease request is received. For
ONT VoIP hosts, the subscriber ID of the ONT is used. In both cases, the first
16 characters of the Subscriber ID text field are inserted.

MAC Address (for DOCSIS provisioning) of the port so that the ONT MAC is
presented to the DHCP server to validate that the subscriber CPE is connected
to a valid ONT virtual Cable Modem (vCM). See the Calix Open Link Cable
vCMTS Command-Line Interface (CLI) Reference Guide and Calix Open Link Cable
vCMTS SNMP Management Guide for more information.

none
5. In the toolbar, click Apply.
For CLI:
set access-identifier-profile <eth-system-default|gpon-system-default>
remote-id [subscriber-id|fsan-serial-number|mac-addr|none]
set access-identifier-profile <eth-system-default|gpon-system-default>
circuit-id [calix-format|tr101-format]
Provisioning VLAN Ranges
Provisioning VLANs in ranges allows you to efficiently create, update, modify, and delete
VLANs. This feature also allows you to quickly create VLAN memberships to multiple
Ethernet port interfaces.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
105
To create a range of VLANs
1. On the Navigation Tree, select and expand the E7 node, and then click VLANS.
2. In the Toolbar, click the Range Operations icon
open the Create VLAN Range dialog box.
, and then select Range Create to
3. In the From and To boxes, enter the values of the first VLAN ID and last VLAN ID in
the range.
4. Select the Stop On Failure box to stop the range creation operation if a failure occurs.
For example, if VLANs within the specified range already exist.
5. Enter the parameters to apply to the VLANs in the range, and then click Create. The
Task Progress dialog appears to show the status of each operation.
6. Click ok.
For CLI:
create vlan <vlan ID>-<vlan ID> [name|mac-learning|igmp-mode|igmpprofile|dhcp-snooping|ae-ont-discovery]
To update a range of VLANs
1. On the Navigation Tree, select and expand the E7 node, and then click VLANS.
2. In the Toolbar, click the Range Operations icon
open the Update VLAN Range dialog box.
, and then select Range Update to
3. In the From and To boxes, enter the values of the first VLAN ID and last VLAN ID in
the range.
4. Enter only the parameter values that you want to update for the VLANs in the specified
range, and then click Update. The Task Progress dialog appears to show the status of
each operation.
5. Click ok.

Alternatively, to select an E7 VLAN to edit, click in the VLAN table row between
the columns where there is no text. You can select multiple VLANs to edit using the
Control+click and Shift+click keys. Make any modifications using the top edit row.
Click Apply from the toolbar when the modifications are complete.
For CLI:
set vlan <vlan ID>-<vlan ID> [name|mac-learning|igmp-mode|igmp-profile|dhcpsnooping|ae-ont-discovery]
To delete a range of VLANs
1. On the Navigation Tree, select and expand the E7 node, and then click VLANS.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
106
2. In the Toolbar, click the Range Operations icon
open the Delete VLAN Range dialog box.
, and then select Range Delete to
3. In the From and To boxes, enter the values of the first VLAN ID and last VLAN ID in
the range to delete.
4. Select the Stop On Failure box to stop the range deletion operation if a failure occurs.
For example, if VLANs within the specified range do not exist.
5. Select the Force Deletion box to ensure VLANs and associated VLAN memberships are
deleted.
6. Click Delete.
Note: A VLAN can not be deleted if it is referenced by a tag action, a service tag action, an
ONT Ethernet Service, or an ONT IP Host.

Alternatively, to select an E7 VLAN to delete, click in the VLAN table row between the
columns where there is no text. You can select multiple VLANs to delete using the
Control+click and Shift+click keys. Click Delete from toolbar to delete the selected
VLANs.
For CLI:
delete vlan <vlan ID>-<vlan ID>
To add interfaces or an ERPS domain to a range of VLAN memberships
1. On the Navigation Tree, select and expand the E7 node, and then click VLANS.
, and then select Range Action >
2. In the Toolbar, click the Range Operations icon
Add VLAN Members to open the Add VLAN Members dialog box.
3. In the From and To boxes, enter the values of the first VLAN ID and last VLAN ID in
the range.
4. In the Add Interfaces/ERPS column, select the interfaces to add to the specified range
of VLAN memberships.
Note: Use Shift+click or Ctrl+click to select multiple interfaces from the column.
5. Click the direction button
and then click ok.
to add the interfaces to the range of VLAN memberships,
6. The Task Progress dialog appears to show the status of each operation. Click ok.
For CLI:
add interface <interface name> to-vlan <vlan ID>-<vlan ID>
Related topic

Creating VLANs (on page 86)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
107
Adding the Uplink Interface(s) to VLAN Memberships
This topic shows you how associate E7 Ethernet port interfaces, LAG interfaces, multicast
router interfaces, and ERPS domains to a VLAN, thereby creating a VLAN membership. A
VLAN membership enables traffic on a specific VLAN to be forwarded to or accepted on an
E7 interface or ERPS domain. For any VLAN-tagged traffic to flow through an E7 Ethernet
interface, either the interface must be a member of the tagging VLAN, or the interface must
have a corresponding VLAN tag-action associated with it. When you create a tag-action, the
interface automatically becomes a member of the VLAN specified in the tag-action.
Configuration guidelines

You can configure only one of the following attributes on a given VLAN on a given
interface:



Trunk interfaces:

VLAN member

Native VLAN
Edge interfaces:

VLAN member

Tag-action

Native VLAN
Access interfaces:

VLAN member

Tag-action

When you create a tag-action, the interface automatically becomes a member of the
VLAN specified in the tag-action. See example below.

Trunk and edge interfaces are always associated with at least one VLAN, through the
native VLAN attribute (VLAN 1 by default).
An interface role cannot be modified when it is a member of a VLAN.
ERPS domains can only be associated with VLANs through membership.
When you add VLAN router interfaces, you are setting the static multicast router
location on specific ports, allowing the system to know which interface has the multicast
router. You can add many interfaces to the static location. For example, if the system is
connected to the multicast router via RSTP, you would want to add the static location to
both ports (for instance, 1/g1 and 2/g1). RSTP will block one port at a time. When the
port switches to the other port, there would still be connectivity to the multicast router.
When the IGMP profile has the Router Learning Mode configured for 'static-only',
IGMP Proxy will not allow a static multicast router ('mrouter') interface to be a multicast
destination. If the interface could become a multicast destination in the event of a
network topology change, the interface should not be configured as a mrouter interface.




Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
108


Even if no interface is currently using VLAN 1 as the Native VLAN, it is still off limits
for user provisioning, including use as the Management VLAN or ERPS control VLAN.
For modular chassis nodes, any VLAN created on the system is automatically mapped to
the Stacking Ports. The remaining port interfaces in the system must be a VLAN
member for traffic to pass on the VLAN through the interface.
Example application configuration for tag-action versus VLAN membership:
For incoming E7 traffic where the voice and video services are single-tagged and the per port
data VLANs are double-tagged:

VLAN-per-port for data traffic

Single voice service VLAN

Single video service VLAN
Configure the following:
1. Create a voice VLAN and a video VLAN and add the interface to each of the VLAN
memberships.
2. Create a no-match add-tag action to the interface for all remaining VLANs to add an
outer data service tag.
Before starting
Before starting the VLAN membership creation process, check that the following conditions
are met:


A VLAN must be created prior to adding VLAN member interfaces.
The Ethernet LAG interface or ERPS domain must exist to add it to a VLAN
membership.
To make an interface a VLAN member
1. On the Navigation Tree, click VLANs.
2. Click the Provisioning tab.
3. In the table of existing VLANs, double-click the row showing the VLAN which you
want to add members.
4. Click Action and then select the action to perform:

Add/Remove VLAN Members enables traffic on a specific VLAN to be
forwarded to or accepted on an E7 interface or ERPS domain.

Add/Remove VLAN Router Interfaces sets the static multicast router location on
specific ports, allowing the system to know which interface has the multicast router.
You can add many interfaces to the static location.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
109
5. In the dialog box, do the following:
a. In the Available Interfaces/ERPS scrolling list, click the interface or the ERPS
domain to add to the VLAN. You can select more than one item, using the
Ctrl+click or Shift+click key combinations.
b. Click the > button to add the selections to the Current Members or Current
Interfaces box.
Note: See the Configuration guidelines above.
Note: If the E7 system is set to Modular Chassis mode, the Ethernet port interfaces are
indicated with a shelf/card/port location. For example, EthIntf:1-2-G1.
6. Click Ok.
For CLI:
add interface <interface-id> to-vlan <vlan-id>
add erps-domain <domain-id> to-vlan <vlan-id>
add static-mcast-src interface <interface-id> to-vlan <vlan-id>
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
110
Step 2. Create GPON-Related Profiles
This section describes how to create various profiles that are necessary for provisioned
GPON services.

For overviews of subscriber services provisioning steps with links to supporting
procedure topics, see:
Service Provisioning Overviews (on page 41)
Topics Covered
This section covers the following topics in bold that are part of the overall GPON services
configuration process:
Step 1. Configure network uplinks for GPON services
Step 2. Create system profiles that support GPON applications

Creating an ONT profile

Creating Quality-of-Service (QoS) for GPON traffic management

Creating profiles for data and video services

Creating profiles for voice services

Creating profiles for T1/E1 services
Step 3. Configure a PON
Step 4. Configure subscriber services
Overview: GPON-Related Profiles
This section describes the various system profiles to use for GPON applications. Creating
profiles allows you define common provisioning attributes that can be reused many times
and applied to multiple service ports. See the following categories for the procedures to
create the profiles:






ONT profile (on page 115)
QoS profiles (on page 116)
Data and Video service profiles (on page 166)
Voice service profiles (on page 201)
T1/E1 service profiles (on page 221)
Global profiles in CMS (on page 226)
Note: For information about system profiles unrelated to GPON services, refer to the Calix
E7 User Guide.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
111
Profiles referenced in service provisioning


Profiles allow you to set up and maintain information that is common to multiple
subscribers. Repeating the similar task of subscriber service activation then consists of
referencing the existing profiles and sometimes providing subscriber-specific information
to complement the profiles.
When a profile is changed, all subscribers using that profile are affected.
Note: When a profile is changed, all objects referring to that object are affected. For
example, if the rate in a bandwidth profile is changed, all ONT Ethernet ports referencing
the profile are changed to the modified bandwidth rate. Profile objects may not be deleted
while they are being referenced.
ONT profile
By default, the system already has defined standard profiles (indexes 101 and above) for a
series of Calix ONTs. Up to 50 custom ONT profiles can be created. ONT profiles that
describe the configuration of ONTs are not shared globally and CMS synchronization is not
supported.
Quality of Service
The QoS-related profiles are used to classify and control traffic.
PON Class of service (CoS):
Supports four classes of service are carried on the PON, that apply to all services carried on
the PON.
There are defaults for each of the four classes, along with the intended service use. The
higher values for both the CoS value and the P-bit indicate a higher priority.
Note: Establish the PON CoS attributes before creating service provisioning on a PON.
Any change to the CoS global configuration will cause all PON ports to reset.
PON Upstream class of service:
A model that expands on the four default, system-defined instances of a PON Class of
Service by allowing an additional four user-defined priorities.
Service tag actions:
Each service provisioned at the subscriber port includes a reference to a match list and a tag
action that specifies the classifying and marking of packets from the subscriber port into the
service VLAN.
A service carried on an N:1 VLAN applies to multiple subscriber ports, so a single match list
and tag action can be used to describe the service.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
112
A service carried on a 1:1 VLAN is the same for each subscriber except the customer tag is
unique per subscriber. In this case, it would be ideal to define the match list and tag action
pair such that multiple subscriber ports can reference it. This is accomplished by having a
special value for the output in the tag action that indicates the value of the output tag is
subscriber specific. The customer-specific tag is contained in the service definition.
Ethernet Port class of service:
This profile is associated with an Ethernet port so traffic is sent at a particular rate by
controlling the queue of packets.
VLAN tag actions:
A tag-action allows you to add or change, or add and change VLAN tags on packets that are
received on a specified GE or 10GE edge or access link interface.
Policy map and policies:
Specifies what Quality of Service (QoS) actions to perform on ingress traffic packets when
the packets match selection criteria.
Layer-3 priority:
Maps Differentiated Services Code Point (DSCP) or IP Precedence priority bit values, used
for packet classification on DiffServ networks (defined in RFC 2474 and RFC 2475), to
IEEE 802.1p priority-bit values to classify traffic priority.
Data and Video
Bandwidth profiles:
Specifies the upstream and downstream rate limits for an individual service member.
Bandwidth from each service definition are accumulated into an aggregate class of service
rate that applies at the Ethernet port level. Even though the service member reference to a
bandwidth profile implies bandwidth control at the service level this is not the case;
bandwidth is controlled at the aggregate class of service for each port.
Each service definition maps to a particular class of service on the PON. Bandwidth limits
for all the services of a given CoS on a given port are aggregated and applied at the port level.
Multicast video profiles:
A video service is identified by the presence of a service definition, referencing a multicast
profile. The multicast profile defines the following attributes of a video service.


Maximum number of simultaneous streams on subscriber port.
The interval to expect queries from the upstream device, controlling how we age out
channels.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
113

A flag indicating whether we convert multicast traffic to unicast. (Only Calix GX ONTs
support this feature.)
Multiple video profiles will typically differ in the number of streams allowed. A small number
of video profiles will be created and applied to many subscriber ports. For example, bronze,
gold, and platinum video services.
A multicast profile references two previously defined profiles:

Multicast Address Map
Identifies the optional global allowable multicast IP ranges.

Multicast VLAN Registration (MVR) Profile
Identifies the optional MVR address ranges associated with specified multicast VLANs.
Security profiles:
Specifies security attributes of the ONT Ethernet port: DHCP lease limit, upstream
broadcast/multicast limit, L2CP filter.
Static IP host addresses and subnets:
Configures a static Ethernet service IP address or subnet, to associate with an ONT Ethernet
port service.
PPPoE profiles:
Referenced by the service VLAN that is configured for PPPoE operation.
IGMP profiles:
Defines a profile for VLAN association that sets configuration attributes of the Internet
Group Management Protocol (IGMP) snoop used to establish membership in a multicast
video services group.
ONT template:
Defines all of the key management aspects of a Home Gateway (HGW) ONT as well as the
logical assignments of physical GE ports for the initial setup.
RG Configuration File:
The Residential Gateway (RG) configuration file for the E7 to download which allows the
deployment of a common provisioning and service model across all 700GE ONTs or 836GR
RSG devices supporting Home Gateway.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
114
RG Management Profile:
An RG management profile specifies a TR-98 management object with an associated
parameter value that the Auto-Configuration Server (ACS) sends to the ONT, controlling the
behavior of the TR-069 client on RG-enabled ONTs without modifying the applied external
configuration file.
Voice over IP
IP host profiles:
The IP host profiles define attributes for static IP hosts, and is used for SIP, TDM gateway,
and PWE3 services. It defines how the ONT obtains an IP address for communication.
SIP Voice profiles:
Specifies the location of the SIP configuration file in a primary and a secondary location.
TDM Voice gateway profiles:
Specifies the port numbers for the UDP control plane traffic, and RTP voice traffic, as well
as the IP address of the C7 viper card.
H.248 Voice gateway profiles:
Specifies the H.248 gateway properties for the ONT's H.248 gateway services.
MGCP Voice gateway profiles:
Specifies the MGCP gateway properties for the ONT's H.248 gateway services.
T1/E1 service profiles
ONT PWE3 profiles:
This topic describes how to create an ONT PWE3 profile, or change the System-Default
profile that specifies the TDM protocol for the ONT's PWE3 services.
PWE3 profiles:
This topic describes how to create a PWE3 profile for T1 or E1 that specifies how a T1 port
interacts with the remote endpoint of the pseudo-wire.
IP host profiles:
The IP host profiles define attributes for static IP hosts, and is used for SIP, TDM gateway,
and PWE3 services. It defines how the ONT obtains an IP address for communication.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
115
Global profiles in CMS
Global profiles automate synchronizing profiles across multiple E7 nodes. They support
cross-network capabilities such as bulk provisioning. You create a profile once within CMS
and apply it across all targeted E7 nodes to ensure consistency across large deployments. See
Managing E7 Global Profiles in CMS (on page 226).
When you create a global profile, the profile is automatically downloaded to the networks in
the CMS management domain that enable global profile updates.
1. On the Navigation Tree, click CMS.
2. In the Work Area, click Profile > ONT, and then select the profile to create.
Grade of Service (GOS) profiles:
Specifies reporting thresholds for certain monitored attributes of an ONT Ethernet port, an
ONT T1 port, or an ONT PWE3 service. For example, any time a particular count exceeds a
specified threshold within a certain period (either 15 minutes or one day), a thresholdcrossing alert is generated. For information on creating the profile, see the Calix E7
Maintenance and Troubleshooting Guide.
Creating an ONT Profile
This topic shows you how to create an ONT profile. By default, the system already has
defined standard profiles (indexes 101 and above) for a series of Calix ONTs. Up to 50
custom ONT profiles can be created.
Note: To determine if a specific ONT model supports Home Gateway services, use the show
ont-profile CLI command, and then review the "G" (RG) and "F" (FB) Ports columns to
see if the result is "1" indicating support.
Note: ONT profiles that describe the configuration of ONTs are not shared globally and
CMS synchronization is not supported.
Note: The GPON ONT profile does not include an option for "Disable on battery." Set the
power option on each of the individual ONT ports.
Parameters
You can provision the following parameters for the ONT profile:
Parameter
Description
Valid Options
Name*
Profile name.
numeric: 1-50
Vendor*
Vendor ID for ONT profile.
text string (4)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
116
Parameter
Description
Valid Options
Model
Model for ONT.
text string (31)
Voice
Number of Voice (POTS) ports
0‡ - 8
Fast Eth.
Number of Fast Ethernet ports.
0‡ - 8
Gig. Eth.
Number of Gigabit Ethernet ports.
0‡ - 8
HPNA
Number of HPNA Ethernet ports.
0‡ - 8
T1
Number of T1 ports.
0‡ - 8
RF Video
Number of RF video ports.
0‡ - 8
Hot RF Video
Number of hot RF video ports.
0‡ - 8
Eth OAM Capable
Whether the ONT is capable of Ethernet OAM.
selected = yes‡
unselected = no
Convert Multicast
Capable
Whether the ONT is capable of converting multicast to unicast.
selected = yes
unselected = no‡
Residential Gateway
Number of Residential Gateway Virtual ports
0‡ - 8
Full Bridge
Number of Full Bridge Virtual ports.
0‡ - 8
Default to RG Mode
Whether the ONT should default to Residential Gateway Mode.
selected = yes
unselected = no‡
‡ Default
To create an ONT profile
1. On the CMS Navigation Tree, click ONTs.
2. In the Work Area, click Profiles > ONT Profile > Profiles.
3. In the menu, click Create.
a. In the Create ONT Profile dialog box, enter the information and port values for the
ONT.
b. Click Create.
4. Associate the ONT profile when provisioning an ONT.
For CLI:
create ont-profile <p-name> vendor-id <v-id>
show ont-profile
Creating QoS Profiles
The E7 supports the ability to classify ingress traffic based on the P-bit, DSCP value, or
VLAN values of the ingress traffic. Additionally, the ONT can classify traffic based on the
MAC OUI value or Ethertype. The E7 then marks the traffic with a new P-bit value.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
117
Using the newly marked P-bit values, the egress queues on the port then deliver the traffic to
the network using the strict priority queuing scheme (with minimum CoS bandwidth
guarantees if desired). Strict priority queuing means that all traffic (in the queues) with the
highest priority is delivered to the network first, then lower priority queue traffic is delivered.
This section describes how to create the following traffic-control objects for GPON traffic
management:
PON Class of Service (CoS): Defines a CoS profile to associate with an Ethernet port or
GPON port so traffic is sent at a particular rate by controlling the priority queuing of
packets.
PON Upstream Class of Service: The flexible GPON Quality of Service (QoS) model
expands on the 4 default, system-defined instances of a PON Class of Service (CoS 1-4) by
allowing an additional 4 user-defined priorities (user 1-4) of scheduled service per ONT
User-to-Network-Interface (UNI). These 4 user-defined CoS support multiple independent
instances of the same service class per ONT.
Match list and rules: Defines a set of criteria (matching rules) for classifying traffic on an
ONT Ethernet port. The match list defines how the ONT classifies subscriber traffic into a
service VLAN. It is applied to a service tag action that is then associated with an ONT
Ethernet port service.
Service tag actions: All services configured within an E7 GPON port and an ONT exist in
a VLAN-tagged service flow, requiring an associated service-tag action.
Layer-3 priority: Maps Differentiated Services Code Point (DSCP) values, used for packet
classification on DiffServ networks (defined in RFC 2474 and RFC 2475), to IEEE 802.1p
priority-bit values to classify traffic priority.
See Creating an Ethernet Bandwidth Profile (on page 188) for instructions on creating another
traffic-control object for services provisioned on ONT Ethernet ports.
Next steps:
After completing the creation of QoS profiles, see the following sections to continue creating
service-related profiles:




Data and Video service profiles (on page 166)
Voice service profiles (on page 201)
T1/E1 service profiles (on page 221)
Global profiles in CMS (on page 226)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
118
PON CoS
This topic covers the following subjects:




E7 GPON QoS Overview
OLT Service Scheduler
ONT Upstream Queue
Supported GPON QoS Applications
E7 GPON QoS Overview
To support prioritized upstream service flows, the E7 GPON solution supports up to eight
OLT Service Schedulers, also termed Transmission Containers (T-CONTs), types per ONT.
Four types (cos1-4) follow a system-default P-bit to CoS mapping model. For added
flexibility, four other types (user1-4), supported by compatible ONTs, are user-configurable
for any class of service. The combination of these eight T-CONTs supports multiple
instances of the same traffic class per ONT to be treated independently for rate-limiting and
shaping.

See Creating a PON Class of Service (on page 122) to change the default mapping
between GPON CoS to P-bits (cos-1 through cos-4).

See Creating a PON Upstream Class of Service (on page 124) to create and define PON
upstream CoS profiles (user-1 through user-4).
OLT Service Scheduler
The OLT Service Scheduler, or Transmission Container (T-CONT), is an ONT object that
represents a group of logical connections or service flows which appear as a single entity for
the purpose of upstream bandwidth assignment on the PON.


For release 2.1 or lower, each ONT can have up to 4 T-CONTs assigned (CoS 1-4)—one
per PON class of service.
For release 2.2 or higher, each ONT can have up to 8 T-CONTs assigned (CoS 1-4, user
1-4).
The ONT reports the status of the queues associated with the service scheduler to the OLT.
Based on the bandwidth demand, the OLT Dynamic Bandwidth Allocation (DBA) engine
allocates upstream transmit opportunities to the service scheduler, resulting in one or more
ONT upstream queues with the opportunity to send data up the PON.
Excess bandwidth, either unconfigured or not currently required by a subscriber, is allocated
to subscriber services based on the DBA priority.
When there is more than a single ONT queue associated with a single OLT service scheduler,
the ONT implements a scheduling mechanism between queues:


Strict Priority scheme between queues with different priority
Round Robin scheme between queues of the same priority
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
119
ONT Upstream Queue
The ONT Upstream Queue and Shaper, also termed a GPON Encapsulation Method
(GEM) port, is a virtual port used to differentiate among traffic classes (TCs). Each different
TC per ONT Ethernet port is assigned a different GEM Port that carries one or more traffic
flow associated with a specific TC. An ONT Ethernet port may have several upstream
queues associated with it that support different TCs. Each service scheduler consists of one
or more upstream queues. Each upstream queue carries one kind of service traffic that is a TCONT type.
Supported GPON QoS Applications
The E7 supports the following GPON CoS applications:





Multiple services, same traffic class (CoS), shared BW
Multiple services, same traffic class (CoS), independent BW
Multiple services, same traffic class (CoS), different P-Bits
Multiple services, same traffic class (CoS), independent BW, prioritized scheduling on the
PON
Single service with prioritization of flows within the service
Multiple services, same traffic class (CoS), shared BW
This model is intended for more than one service being configured on a VLAN, where any
service is with no explicit PON upstream CoS mapping, and is backwards compatible and
upgrade compatible. Services provisioned with software version earlier than R2.2 will operate
the same after upgrading to R2.2 or later.
This model assigns four T-CONT types, each representing an aggregated class of service for
an ONT (BE, AF1, AF2, EF). The four T-CONT types are pre-assigned a class of service
and the provisioned services are required to have bandwidth profiles that match the class of
service. Also, bandwidth assigned to the T-CONT type is always aggregated from the
multiple services mapped to it on the ONT.
Each ONT Ethernet port receives four upstream queues (or GEM ports) at service
instantiation where the outer P-bit of the tag action maps to one of the four GEM ports,
regardless of the VLAN. If two services are assigned to a single class of service, they will
share the GEM port. A second service on a different ONT Ethernet port will be assigned a
different GEM port, but will share the T-CONT type with service separation performed by
the ONT GEM port shaper. The mapping between the GEM port and the T-CONT type is
fixed for all services on the OLT and is defined by the E7 PON Class of Service
configuration attribute.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
120



Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
VLAN ID /
P-Bit
Data-1
AF1
cos-2
10 Mb/s
1/1 Mb/s
GEM 3
30 / 3
Data-2
BE
cos-1
50 Mb/s
0/5 Mb/s
GEM 1
32 / 0
Data-3
BE
cos-1
10 Mb/s
0/1 Mb/s
GEM 1
34 / 0
In Standard QoS Model T-CONT type (CoS-1):

Upstream BWP = Data-2 + Data-3 BWPs = 6 Mb/s

Downstream BWP = 60 Mb/s

Either service can use all of the bandwidth, if there is no contention for it.
Traffic marked with a P-bit value is forced into a pre-determined upstream traffic class
and bandwidth profile type.
The fixed PON CoS service model does not support the following:


P-bit preservation or DSCP-to-P-bit mapping
Ability to rate limit all P-bit flows within a single VLAN
Multiple services, same traffic class (CoS), independent BW
This model is intended for isolating the bandwidth for multiple services on an ONT
Ethernet port that share the same traffic class. The same service class per ONT port can
select different GEM ports and a different T-CONT type.


PON US profile is created and mapped to user-1 at the ONT
PON CoS of user-1 is selected when adding the Ethernet service
Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
VLAN ID /
P-Bit
Data-1
AF1
cos-2
10 Mb/s
1/1 Mb/s
GEM 3
30 / 3
Data-2
BE
cos-1
50 Mb/s
0/5 Mb/s
GEM 2
32 / 0
Data-3
BE
user-1
10 Mb/s
0/1 Mb/s
GEM 1
34 / 0
Multiple services, same traffic class (CoS), different P-Bits
This model is intended for isolating multiple services on an ONT Ethernet port that share
the same traffic class, where a service explicitly defines the outer VLAN, P-bit, and the PON
upstream traffic class. The service can have any bandwidth profile, or share a single
bandwidth profile with other services.
The specified P-Bit is not required to match one of the values defined for the CoS. The P-bit
0 (BE) service uses Software Egress Shaping Path when BE Rate < MAX Supported
throughput.


PON US profile is created and mapped to user-1 at the ONT
Service match list has tagged rule for VLAN 34, P-bit 3
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
121


Service tag action to use P-bit 3
PON CoS of user-1 is selected when adding Ethernet service
Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
VLAN ID /
P-Bit
Data-1
AF1
cos-2
10 Mb/s
1/1 Mb/s
GEM 3
30 / 3
Data-2
BE
cos-1
50 Mb/s
0/5 Mb/s
GEM 2
32 / 0
Data-3
BE
user-1
10 Mb/s
0/1 Mb/s
GEM 1
34 / 3
Multiple services, same traffic class (CoS), independent BW, prioritized scheduling on the
PON
This model is intended for more than one service of the same class where one service (AF2)
should have a higher priority than another (AF1), and they are configured as isolated services.
The same service class per ONT port can select different GEM ports, a different T-CONT
type, and priority of flow.




PON US profile is created with priority 3 and mapped to user-1 at the ONT
Service match list has tagged rule for VLAN 34, P-bit 4
Service tag action to use P-bit 4
PON CoS of user-1 is selected when adding Ethernet service
Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
PON Cos
Priority
VLAN ID /
P-Bit
Data-1
AF1
cos-2
1000 Mb/s
100/100 Mb/s
GEM 2
2
30 / 3
Data-3
AF2
user-1
1000 Mb/s
100/100 Mb/s
GEM 1
3
34 / 4
The recommended priority value of ‘3’ will ensure AF2 is scheduled before AF1.
Single service with prioritization of flows within the service
This model is intended for a service that requires QoS within a VLAN and explicitly defines
the PON upstream traffic class. This model allows a single service to be defined with P-bit
preservation, while maintaining quality of service within the VLAN. Typically, this model is
used within a TLAN or business service. There is a single rate for the entire VLAN service
that can have any type of bandwidth profile (best-effort, assured, expedited). Also, a userdefined PON upstream CoS should be assigned to ensure service separation.

Service tag action to preserve the P-bit value set in service provider supplied Residential
Gateways (RGs):

Copies the subscriber-side Q-Tag P-Bits to a single C-tag or S-Tag, or to the inner CTag of a double-tagged Service.

For the outer tag P-bit, you can specify the value of "copy."

For the inner tag, you can specify the value of "preserve."
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
122
Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
video-1
AF
cos-3
50 Mb/s
1/3 Mb/s
Traffic priority
queued prior to
mapping to a
GEM port -- for
example,
GEM 3.
Flow
Type
VLAN ID /
P-Bit
DHCP
30 / 0
VoD C&C
32 / 2
VoD
32 / 4
MC
32 / 5
Creating a PON Class of Service
Each E7 GPON provides a minimum of four classes of service for forwarding traffic. A
service may be provisioned so that traffic is placed in a class based on the P-bit value in the
VLAN tag. Since there are 8 possible P-bit values, there is not a one-to-one mapping
between P-bit values and the classes of service. The configuration for each class defines the
following:

P-bit values that will be included in the class

Forwarding type
Note: The upstream traffic on a service VLAN must have the same P-bit value as is set for
downstream traffic. The P-bit value must also be consistent with the class of service type, as
defined in the PON Class of Service (CoS) table.
The configurations apply to all PON ports in the system. Each ONT service can have
independent CoS queue management, as appropriate for the services on a particular GPON
port.
Note: Within an E7 network, ensure that the IPTV traffic has a high P-bit (priority) value
for points of congestion. Calix recommends using a minimum P-bit value of 4 for video
services. Typically, an upstream IP router sets the VLAN-ID and P-bit values at the
transition to the Ethernet access network (for example, at the point before where an E7
connects to an edge router).
If necessary, you can apply a Policy Map to the E7 Ethernet (ingress) port to mark (re-mark)
ingress traffic with a new P-bit value.
The default mapping between GPON CoS to P-bits is as shown:
GPON
CoS
Scheduling
Class Type
Default
P-bits
Service
CoS 4
Expedited Forwarding
5, 6, 7
Network control, voice, T1
CoS 3
Assured Forwarding 1
4
Video
CoS 2
Assured Forwarding 2
3
Application signaling, TLAN
CoS 1
Best Effort Forwarding
0, 1, 2
High-speed internet
Note: Any change made to the GPON CoS global configuration that invalidates existing
service provisioning will cause all GPON ports to be reset.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
123
Configuration guidelines









The P-bit value defined in the service-tag action must be consistent with the class of
service type as defined in the PON Class of Service (CoS) table.
PON CoS is a system-level configuration and applies to all PON ports in the E7 system.
As a higher number P-bit denotes higher priority, so does a higher PON CoS value.
All P-bits 0...7 must be represented in the mapping table.
A P-bit can only belong to a single PON class of service.
P-bits in lower classes of service must be lower than P-bits in higher classes of service.
A lower PON CoS must have lower or equal Scheduling Class Type when compared to a
higher CoS. The ordering of Scheduling Class Type values is Best Effort > Assured >
Expedited.
The P-bits can be mapped to fewer than all four CoS levels, however all CoS levels above
the unused CoS must also be unused.
Because the bandwidth limits for all ONT services (in the same class) of a single ONT
Ethernet port are aggregated into a single Class of Service (CoS) metered rate, only one
service per CoS per ONT port is allowed.
Parameters
Parameter
Description
Valid Options
cos1-type
Forwarding type for CoS 1. "Not used" indicates no forwarding (CoS is
unused).
expedited, assured, besteffort, not used
cos1-low-P-bit
Low bit value for CoS 1. "None" is the default behavior and indicates the
P-bit value is not set.
0-7
none ‡
cos1-high-P-bit
High P-bit value for CoS 1. "None" is the default behavior and indicates
the P-bit value is not set.
0-7
none ‡
cos2-type
Forwarding type for CoS 2. "Not used" indicates no forwarding (CoS is
unused).
expedited, assured, besteffort, not used
cos2-low-P-bit
Low bit value for CoS 2. "None" is the default behavior and indicates the
P-bit value is not set.
0-7
none ‡
cos2-high-P-bit
High P-bit value for CoS 2. "None" is the default behavior and indicates
the P-bit value is not set.
0-7
none ‡
cos3-type
Forwarding type for CoS 3. "Not used" indicates no forwarding (CoS is
unused).
expedited, assured, besteffort, not used
cos3-low-P-bit
Low bit value for CoS 3. "None" is the default behavior and indicates the
P-bit value is not set.
0-7
none ‡
cos3-high-P-bit
High P-bit value for CoS 3. "None" is the default behavior and indicates
the P-bit value is not set.
0-7
none ‡
cos4-type
Forwarding type for CoS 4. "Not used" indicates no forwarding (CoS is
unused).
expedited, assured, besteffort, not used
cos4-low-P-bit
Low bit value for CoS 4. "None" is the default behavior and indicates the
P-bit value is not set.
0-7
none ‡
cos4-high-P-bit
High P-bit value for CoS 4. "None" is the default behavior and indicates
the P-bit value is not set.
0-7
none ‡
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
124
See PON CoS (on page 117) for an overview of the system-defined and user-defined
priorities of scheduled services per ONT Ethernet port.
To create a PON class of service
1. On the Navigation Tree, click E7.
2. Click Profiles > COS > PON.
3. In the PON COS Configuration dialog box, do the following:
a. For each of the four Forwarding Type lists, select the class of service.
b. For the each of the Low P-bit lists, select the low P-bit value for each CoS.
c. For the each of the High P-bit lists, select the high P-bit value for each CoS.
d. Click Apply.
4. Associate the CoS to a service tag action so traffic is sent at a particular rate by
controlling the queuing of packets. See Creating Service Tag-Actions (on page 131).
For CLI:

set pon-cos-cfg <cos*-type|cos*-low-p-bit|cos*-high-p-bit>

show pon-cos-cfg
Creating a PON Upstream Class of Service Profile
PON upstream Class of Service (CoS) profiles allow you to expand on the 4 system-default
instances of CoS to 8 priorities of scheduled service per ONT. This model supports multiple
instances of the same traffic class per ONT to be treated independently for rate-limiting and
shaping.
For example, if there are two Best Effort (BE) services provisioned on Port 1, you could
assign one of the services to PON CoS user-1 so that each service would have a dedicated TCONT type in the upstream direction, rather than sharing a queue that is set to the aggregate
bandwidth of both services, allowing any one service to use all of the bandwidth if there is no
contention for it.

Service
Name
Traffic
Class
PON CoS
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
ONT Upstream
Queue
Data-1
BE
cos-1
50 Mb/s
0/5 Mb/s
queue 2
Data-2
BE
user-1
10 Mb/s
0/1 Mb/s
queue 1
The PON upstream CoS profile configuration and application process:
a. Create a PON US CoS profile with an identifying name for mapping.
b. Map the PON US CoS profile to an instance (user1-user4) at the ONT.
c. Select the PON CoS instance (user1-user4) that is mapped to a PON US CoS profile,
when adding an Ethernet service to the ONT port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
125
Configuration guidelines


There are still three classes of service (BE, AF, EF) for the user-defined PON upstream
CoS profiles. However, from the Dynamic Bandwidth Allocation (DBA) scheduling
perspective, a given GPON CoS can be prioritized so that there can be up to 4 AF
classes of service and up to 4 BE classes of service, where EF>AFx>BEx is the DBA
scheduling priority. Within a given service class, the services at the highest priority will be
allocated Excess bandwidth first and then the next highest priority.
If explicit CIR/PIR values are included for a PON upstream CoS profile, these values
take precedence over the Ethernet bandwidth profile associated with the service.
Additionally, the upstream CIR is only implemented at the upstream PON.
Examples:


If the user-defined PON CoS (user 1-4) CIR is 0, there will be no guaranteed
bandwidth, even if the service has set a CIR via the Ethernet bandwidth profile.

If the user-defined PON CoS (user 1-4) PIR is less than the Ethernet bandwidth
profile PIR, the service will only get the PON CoS PIR as the peak rate.
If the CIR and PIR are set on the user-defined PON CoS (user 1-4), the values should be
considered a cap for all services associated with that PON upstream CoS profile. If the
associated services are not managed to fit within these caps, you may see undesired or
unexpected behavior.
For example, the following operation exists with the particular settings on the PON
upstream CoS profile:

PIR/CIR = aggregate
There is a total of 100M for three services of 60M, 20M, and 20M.

PIR/CIR = 80M
There is a cap of the three services of 60M, 20M, and 20M, where the DBA
prioritization would dictate which service receives the appropriate throughput.

The following ONT-specific differences exist around a service, with respect to upstream
shaping:

GX-series ONTs:

Four classes of service (cos 1-4) where the total = 4 T-CONT types

PON upstream CoS profile (user 1-4) application is NOT supported

Can rate limit the upstream bandwidth per individual service instance so that
multiple instances of the same CoS share the upstream bandwidth according to
the bandwidth profile of each individual service. One instance of a CoS cannot
use all the bandwidth allocated to the PON CoS for that ONT by the Dynamic
Bandwidth Allocation (DBA) function. Maximum bandwidth allocated per ONT
CoS is the sum of the services bandwidth profiles defined with a matching CoS
on a single ONT.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
126


GE-series ONTs:

Four fixed classes of service (cos 1-4) plus four user-defined classes of service
(user 1-4) are supported for a total = 8 T-CONT types

Although using a pon-cos, other than fixed, enables upstream GEM port shapers
that rate limit per service, the implementation of a dedicated T-CONT type is
recommended for the most accurate upstream limiting.
T-series ONTs (with E7 R2.3+):

Four system-defined (fixed) classes of service (cos 1-4) plus three user-defined
classes of service (user 1-3) where the total = 7 T-CONT types

PON upstream CoS profile (user 1-3) application is supported where user-4 is
NOT supported
Parameters
You can provision the following parameters for the PON upstream class of service profile:
Parameter
Description
Valid Options
Name
Name of PON upstream class of service profile.
text string
Type
Traffic class forwarding type for CoS.
expedited, assured, besteffort, blank=not used
Typically, the following traffic classes, GPON CoS, and P-bit values are
associated:

Priority
Expedited Forwarding (EF), CoS 4, P-bits 5,6,7

Assured Forwarding 1 (AF1), CoS 3, P-bits 4

Assured Forwarding 2 (AF2), CoS 2, P-bits 3

Best Effort (BE), CoS 1, P-bits 0, 1, 2
Dynamic Bandwidth Allocation (DBA) priority where a given GPON CoS
can be prioritized so that there can be up to 4 AF classes of service and
up to 4 BE classes of service. Excess bandwidth, either unconfigured or
not currently required by a subscriber, is allocated to subscriber
services based on the DBA priority.

Where EF>AFx>BEx is the DBA scheduling priority.

Within a given service class, the services at the highest priority will
be allocated Excess bandwidth first and then the next highest
priority.
1 ‡, 2, 3, 4
CIR Bandwidth
Committed Information Rate (CIR) Bandwidth (Mb).
0-1200 Mb,
aggregated ‡
PIR Bandwidth
Peak Information Rate (PIR) Bandwidth (Mb).
0-1200 Mb,
aggregated ‡
‡ Default
See PON CoS (on page 117) for an overview of the system-defined and user-defined
priorities of scheduled services per ONT Ethernet port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
127
To create a PON upstream class of service profile
1. On the Navigation Tree, click E7.
2. Click Profiles > COS > PON Upstream.
3. Reference the table above to configure the parameters.
4. Click Create.
5. Map the PON upstream CoS profile to the ONT where it will be assigned to a service.
See Adding PON Upstream CoS Profiles to a GE ONT (on page 256).
6. Associate the PON upstream CoS to a service at the time of provisioning the service on
the GPON ONT.

See Configuring Data Services (on page 269).

See Configuring IP Video Services (on page 285).
For CLI:

create pon-us-cos-prof <name> [cos-type|prio|cir-bw|pir-bw]

set pon-us-cos-prof

show pon-us-cos-prof
Creating a Service Match List and Rules
The ONT performs the following two actions:


Classification – the service match lists are for matching and classifying traffic into
services.
Marking – the service tag actions are for marking the traffic with the appropriate VLAN
and P-bit required by the service.
This topic describes how to create a match list and then add an ordered collection of
matching rules to associate with a service tag action. The match list defines how the ONT
classifies subscriber traffic to determine the service in which it belongs. A match list can
contain both “tagged” and “untagged” match rules, up to 12 tagged rules and up to 16
untagged rules for each ONT Ethernet port.

Untagged match rules can match on the following:

A portion of the source MAC address as indicated by the Source MAC and Source
MAC Mask attributes of a video Set-Top box

The Ethernet type to distinguish video and High-Speed Internet (HSI) untagged
traffic

All untagged traffic by using the system default match list "all-untagged"

PVC VPI and VCI port numbers only apply to VDSL2 services
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
128

Tagged match rules can match on any combination of the following:

Outer tag

VLAN-ID

P-bit values

Tag Protocol Identifier (TPID) can also be specified at the E7 egress Ethernet port
interface, but defaults to 0x8100
Example of multiple match rule use for classifying traffic:
A service provider wants to use a single ONT Ethernet port to connect to a home network
with a combination of IPTV and data traffic. The IPTV traffic is identified by using the OUI
value of the video set top box.
This combination of rules can accomplish the example task:
1. An untagged traffic match rule would be applied with a specific MAC OUI match
criteria.
2. A second untagged match rule would be applied with a "match any" criteria.
Using a match list and service tag action, Calix ONTs support matching the traffic from all
set-top boxes (STB) of a particular manufacturer by indicating the STB OUI in the first half
of the specified Source MAC attribute followed by zeros, and then providing a mask for the
STB OUI by indicating ff:ff:ff:00:00:00 in the Source MAC Mask attribute.
Example entries that match all STB source MAC addresses of a particular manufacturer:


ADB set-top boxes: 00:03:91:00:00:00
Amino set-top boxes: 00:02:02:00:00:00
Note: If STBs from multiple vendors are being used, create additional untagged match rules,
entering the OUI for each STB vendor.
Alternatively, the ONTs support matching the traffic from a specific host by indicating the
MAC address in the Source MAC attribute, and then providing a mask for the address by
indicating ff:ff:ff:ff:ff:ff in the Source Mac Mask attribute.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
129
Configuration guidelines



If a residential gateway (RG) at the subscriber's premisis classifies traffic into VLANs,
then for each service type, create a match list with a tagged rule that matches the service
VLAN.
Because only video services are supported on the P-series FB interface, it is not necessary
to specify the OUI of the STB, and the all-untagged match list applies.
Ethertype is the only untagged traffic classifier supported by the T-Series ONTs.
Match list and rule parameters
You can provision the following parameters for match list and rules:
Parameter
Description
Valid Options
Name*
Name of service match list.
text string
S-VLAN (Outer Tag)
VLAN ID of the outer tag (tagged match rules only). VLANs can be
specified by name or by numeric VLAN ID, which ranges from 1-4094. In
addition, "untagged" indicates that only untagged traffic should be
matched and "ignore" indicates that the VLAN ID should not be
examined.
text string, 1-4094,
untagged, ignore ‡
Default = ignore
Outer Pbit
P-bit value of the outer tag (tagged match rules only). P-bit values are in
the range 0-7. Alternately "pbit-none" means the P-bit value is not
considered. If this parameter is not specified, "p-bit-none" is the default
behavior.
0-7, ignore
Default = p-bit-none
Source MAC
Source MAC address (untagged match rules only).
six hexadecimal digits in
the range 0-FF, optionally
separated by colons
Default = ignore
Source MAC Mask
Source MAC mask (untagged match rules only).
six hexadecimal digits in
the range 0-FF, optionally
separated by colons,
none ‡, oui

Ethertype
source MAC mask (x:x:x:x:x:x)

none (no MAC mask)

oui (mask OUI fields (FF:FF:FF:FF:FF:FF)
Ethernet type to match (untagged match rules only).

any = default

pppoe = 0x8863 or 0x8864 (for HSI)

arp = 0x0806 (for video)

ipv4 = 0x0800 (for video)

ipv6 = 0x86DD (for video)
any ‡, pppoe, arp, ipv4,
ipv6
*Required field
To create a service match list
1. Access the profile page:

From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E3-48C/E5-48/E7/ONT > Service >
Tagging > Match Lists.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
130

Locally on the E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > Tagging > Match Lists >
Profiles.
2. In the menu, click Create.
3. In the Name box of the Create Match List dialog box, enter the name of the service
match list that you are creating.
4. Click Create.
For CLI:

create svc-match-list <list name>

delete svc-match-list <list name>

show svc-match-list [list name]
To add a rule to a service match list
1. If you have not already done so, create a service match list. See "To create an Service
match list," above.
2. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile >E3-48C/E5-48/E7/ONT > Service >
Tagging > Match Lists.
Locally on the E7:

On the Navigation Tree, click the E7.

In the Work Area, click Profiles > Service > Tagging > Match Lists >
Profiles.
The table of the previously created match lists appears.
3. Double-click the row that shows the match list in which you want to add a rule.
4. In the menu, click Create and select the type of rule:

Tagged Match Rule

Untagged Match Rule
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
131
5. If you chose to create a tagged match rule, do the following:
a. In the Outer Tag list, select one of the following:

Enter value and then enter the VLAN ID of the outer tag that can be specified
by name or by numeric VLAN ID, which ranges from 1-4095.

untagged indicates that only untagged traffic should be matched.

ignore indicates that the VLAN ID should not be examined.
b. In the Outer P-bit list, select one of the following:

pbit value (range 0-7) that specifies the VLAN priority value to match.

pbit-none indicates the P-bit value is not considered. If this parameter is not
specified, "pbit-none" is the default behavior.
c. Click Create.
6. If you chose to create an untagged match rule, do the following:
a. In the Source MAC list, do one of the following:

Enter the source MAC address (six hexadecimal digits in the range 0-FF,
optionally separated by colons).

Leave the "ignore" to leave blank.
b. In the Source MAC list, do one of the following:

Select Enter Source MAC Mask, and then enter the source MAC mask (six
hexadecimal digits in the range 0-FF, optionally separated by colons).

Select oui to mask the OUI fields.

Select none to ignore.
c. In the Ethertype list, select the type of Ethernet frames that you want to match.
d. Click Create.
7. Associate the service match list with a service tag action to use on E7 ingress traffic
packets.
For CLI:

add tagged-rule to-svc-match-list

add untagged-rule to-svc-match-list

remove tagged-rule <r-index> from-svc-match-list

remove untagged-rule <r-index> from-svc-match-list
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
132
Creating Service-Tag Actions
The ONT performs the following two actions:


Classification – the service match lists are for matching and classifying traffic into
services.
Marking – the service tag actions are for marking the traffic with the appropriate VLAN
and P-bit required by the service.
This topic describes how to create service-tag actions that can be used for many subscriber
ports that require the same actions to be performed. All services configured within an E7
GPON port and an ONT exist in a VLAN-tagged service flow, requiring an associated
service-tag action.
Service-tag actions are applied to subscriber service provisioning as follows:


Video and data services provisioning on an ONT Ethernet port includes a reference to a
service-tag action.
Voice services provisioning on an ONT Voice port implicitly references a Voice Service
IP Host that includes a reference to a service-tag action.
The E7 and the ONT together can apply the following tag actions assigned to an ONT port
service.
Add a single tag
Adds a single outer tag to the matched traffic.




Add 2 tags
Adds an inner and outer tag to the matched traffic*.



Add and change tag
Can be applied to tagged and untagged traffic.
Supported for DSCP-to-P-bit translation.
Supported for Full Bridge (FB) interface services.
NOT supported for Residential Gateway (RG) interface
services.
Can be applied to untagged traffic, only.
Supported for DSCP-to-P-bit translation.
NOT supported for FB or RG interface services.
Adds an outer tag to the matched traffic and changes
the inner tag.




Can be applied to tagged traffic, only.
Supported for RG interface services.
NOT supported for FB interface services.
NOT supported for DSCP-to-P-bit translation.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
133
Change tag
Changes the outer tag on the matched traffic.



Can be applied to tagged traffic, only.
Supported for FB or RG interface services.
NOT supported for DSCP-to-P-bit translation.
*To properly process ingress double tags, the GE network interface (uplink) must be configured as a Trunk role.
Determining the service-tag action values
When a service is provisioned at an ONT Ethernet port, a match list and service-tag action
specify the classification and marking of packets from the subscriber port into the service
VLAN.
You have the following options for determining the added- or changed-tag values:

Specify the VLAN value explicitly.
This option is used for a VLAN-per-service provisioning model (N:1). A service carried
on an N:1 VLAN applies to multiple subscriber ports, where a single match list and tag
action can indicate the service.

Reference the VLAN value from the service provisioning on the ONT port.
This option is used for a VLAN-per-port provisioning model (1:1). A service carried on a
1:1 VLAN is the same for each subscriber except the customer tag is unique for each
single subscriber port, so you can define the match list and tag action pair such that
multiple subscriber ports can reference it. This is accomplished by indicating "Specified
in Service" for the Output Tag value in the tag action, and then the subscriber-specific
value for the output tag is defined when the service is provisioned on the port.
Note: The service provisioning process follows the creation of a service-tag action.
You also have the following options for determining the service-tag action P-bit value,
assigning it to a Class of Service (CoS):

Specify the P-bit value explicitly.
Enter the P-bit value to use for P-bit marking the outer tag.

Specify the CoS.
Enter the CoS ID to use for P-bit marking the outer tag to the lowest P-bit value
associated with this CoS. This value identifies the PON class of service.
GPON
CoS
Scheduling
Class Type
Default
P-bits
Service
CoS 4
Expedited Forwarding
5, 6, 7
CoS 3
Assured Forwarding
4
Video
CoS 2
Assured Forwarding
3
Application signaling, TLAN
CoS 1
Best Effort Forwarding
0, 1, 2
Network control, voice, T1
High-speed internet
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
134

Reference a Layer-3 Priority map.
Use a DSCP table to map untagged frames coming from the subscriber to a P-bit value.
From the ONT Ethernet port, you can select the system-default profile ("access") or
specify another custom profile. See Layer 3 Priority to P-Bit Mapping (on page 157). Also,
see Creating a Policy Map for L3 Priority Mapping (on page 154) for instructions on using a
class map to match the DSCP bits of untagged frames of ingress traffic on Trunk and
Edge Ethernet (GE/10GE) ports, and then using a policy map to assign a corresponding
P-bit (priority) value into the classified traffic.
Configuration rules:

Only one service per port can use the DSCP-Bit mapping function. However, a
second service of untagged traffic on the same port that matches a specific OUI
value is supported, where that OUI-matching service takes precedence for any
matching frames.

Layer-3 priority maps work with add-tag and add-2-tags tag actions.

If you select “Map a layer-3 Priority,” in the service tag action, then when creating the
service, you must select a PON CoS parameter of User1-4 or CoS1-4. Do not leave
the system-default parameter of “derived” as there is no single unique P-bit specified
from which to derive the intended CoS.

The T-Series ONTs do not mark the P-bit of broadcast and multicast frames based
on DSCP. T-Series ONTs handle all broadcast / multicast packets from the
subscriber as best-effort and mark them with the default P-bit of the service.
Provisioning sequence:
a. Create a DSCP-to-P-Bit map, if you do not want to use the system-default.
b. Assign the map to the ONT port (on page 257), or leave the system-default map
"access" assignment.
c. Create a service-tag action with an Outer P-Bit Source of Map a layer-3 Priority.
d. Create a service using the defined service-tag action.
The following table shows the 802.1p to DiffServ DSCP pre-defined, system-default
mapping table ("access").
Default
P-bits
DiffServ Code Point**
Service
0
CS6, CS7
(48-56)
Network control
0
EF
(46)
Voice, NSP, CES
5
CS5
(40)
Network Management
4
CS4 & AF41-43
(32-38)
Video
3
CS3 & AF31-33
(24-30)
Data3
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
135
Default
P-bits
DiffServ Code Point**
Service
2
CS2 & AF21-23
(16-22)
Data2
1
CS1 & AF11-13
(8-14)
Data1
0
0
Best Effort
**The E7 supports alphanumeric DSCP values that denote forwarding classes such as
AF21, AF31 in addition to numeric value assignment.

Preserve the existing P-bit value upstream.
Indicate that the E7 preserves the P-bit value set in service provider supplied Residential
Gateways (RGs).


Copies the subscriber-side Q-Tag P-Bits to a single C-tag or S-Tag, or to the
inner C-Tag of a double-tagged Service.

For the outer tag P-bit, you can specify the value of "copy".

For the inner tag, you can specify the value of "preserve".
Promote the existing P-bit value upstream.
Indicate that the E7 promotes the P-bit value set in service provider supplied Residential
Gateways (RGs).

The P-bit of the inner tag is promoted to the P-bit of the outer tag, allowing the
network QoS to handle the priority of the frame consistently.

For the inner tag P-bit, you can specify the value of "same-as-outer".
Note: The upstream traffic on a service VLAN must have the same P-bit value as is set for
downstream traffic. The P-bit value must also be consistent with the class of service type as
defined in the PON CoS table.
Note: For VDSL2 and GPON subscribers (if PON CoS = Fixed), downstream traffic with
P-Bit values not explicitly defined by the service(s) on the port will be passed through with
unmetered bandwidth.
VLAN Traffic flow in GPONs
Since E7 GPON Ethernet ports have no interface association, unlike the E7 Ethernet ports,
rather than adding a port interface to a VLAN membership to enable traffic flow, a servicetag action must be created that specifies the VLAN. This service-tag action is then referenced
when the service is provisioned on the ONT port. The VLAN must already be created on
the E7 for a GPON port to pass traffic carried on a VLAN.


To view the VLANs associated with specific GPON ports, click E7 > GPON-x >
GPON: on the Navigation Tree, and then click the VLANS tab.
To view the VLANs associated with an ONT, click ONTS on the Navigation Tree, and
then click the VLANS tab.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
136

To view the ONT services associated with a specific VLAN, click VLANS on the
Navigation Tree, click the particular VLAN from the list that appears in the Work Area,
and then click the Service Associations tab.
The ONT Ethernet ports support the same VLAN services as the E7 Ethernet ports,
including native IEEE 802.1Q VLAN tagging and IEEE 802.1ad VLAN stacking (Q-in-Q).
The following service models are supported.




VLAN per subscriber Ethernet port (1:1)
VLAN per Service (N:1)
Ethernet virtual circuits (VLAN trunks)
Transparent LAN Services
Within the E7 GPON OLT and ONT subsystem, MAC learning and switching occurs within
a single, outer VLAN ID, referred to as the VLAN C-tag. Packets on the PON always have a
C-tag, which consists of a provisioned VLAN ID and p-bit. The ONT is responsible for
classifying subscriber traffic and adding/modifying the C-tag.
Configuration guidelines:








The P-bit value specified in the service-tag action must be consistent with the class of
service type as defined in the PON Class of Service (CoS) table.
The ONT requires that SIP traffic be set to Expedited Forwarding. Therefore, the P-bits
set in the service tag action must map to the Expedited Forwarding CoS.
Each service-tag action references a service-match list (classify) and specifies a tag action
(mark and tag).
Each tag action is associated with a specific service.
The logical components within the RSG are functionally similar to a standard GPON
ONT with a subtended 3rd party residential gateway (RG): The ONT receives tagged
traffic from the downstream RG and sends it upstream single-tagged where the OLT
may or may not add a second tag.
Services provisioned on a Full Bridge interface only support:

add-tag

change-tag
Services provisioned on a Residential Gateway interface only support:

change-tag

add-and-change-tag
The following tag actions are supported for VLANs with IGMP enabled:

Add-tag

Change-tag
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
137










Services provisioned with a tag action Outer P-bit source of Map a layer-3 Priority
(DSCP translation to P-bit values) support the following:

add-tag

add-2-tags

Only one service per port can use the DSCP-Bit mapping function. However, a
second service of untagged traffic on the same port that matches a specific OUI
value is supported, where that OUI-matching service takes precedence for any
matching frames.

Each port is independent where it can use a different DSCP map.

GPON services only support DSCP to P-bit mapping, (while xDSL services support
DSCP or IP Precedence for a service, not both).

A PON CoS parameter of User1-4 or CoS1-4 must be used. Do not leave the
system-default parameter of “derived” as there is no single unique P-bit specified
from which to derive the intended CoS.

All of the traffic classified by the DSCP map and P-bit-marked according to the
DSCP map table is put into a single queue for upstream scheduling by the OLT.

In the event of congestion on the upstream bandwidth allocation, traffic in the queue
with the highest P-bit is transmitted first, thus preserving the DSCP set by the
downstream router.
Multiple services and service-tag actions can be applied to a single ONT Ethernet port.
The all-untagged match rule cannot be applied to multiple service-tag actions on the
same port. For example, one of the untagged match rules must point to a specific OUI.
The system applies the tag action that has the most specific match rule.
The same service-tag action can be used on multiple ONT Ethernet ports.
Each E7 shelf, or E7 Modular Chassis system has a capacity of 256 service tag actions.
For configurations that require large numbers of VLANs, Calix recommends selecting
the Specified in Service value for the "Outer Tag" parameter, and then specifying the
VLAN ID when provisioning the service.
The upstream and downstream values specified in the Ethernet Bandwidth Profile and Pbit values defined in the service-tag action must be consistent with the class of service
type as defined in the global CoS table.
For traffic to flow on the VLAN specified in a service-tag action, the VLAN and uplink
must already be created on the E7.
For a GPON port to pass traffic carried on a VLAN, a service-tag action must be created
specifying the VLAN and the VLAN must already be created on the E7.
If no matching criteria are assigned to a tag action, then the tag action is performed on all
packets entering the GPON port. That is, when a match list has a single untagged rule
with the outer tag set to "ignore" and the Outer P-bit set to "Pbit-none."
At least one tag must be specified in the match criteria because the system cannot change
the VLAN ID for untagged traffic.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
138















Traffic must have P-bits assigned in order to be scheduled (prioritized) on the GPON.
The "change-tag" action changes the VLAN ID in the outermost tag.
For double-tagged packets, the outer VLAN ID must match a provisioned VLAN. The
inner tag does not have to match a provisioned VLAN ID.
The E7 reserves four VLAN values for system operation. The default values for these
VLANs are 1002, 1003, 1004 and 1005. You can change these values to another set of
four consecutive VLANs, if required.
Although the "Native VLAN" (VLAN 1) does not apply for traffic arriving at the E7
GPON port, the default VLAN 1 is off limits for user provisioning.
IGMP snooping is provisioned on a VLAN basis.
IGMP snooping is only enabled on the outer VLAN ID as multicast traffic is typically
transported throughout the network with a single VLAN ID tag.
For double-tagged VLANs, the same inner tag cannot be used with different outer tags.
Any given (inner) tag received upstream on the PON can only push a single (outer) tag.
For example, if VLAN 100 is received on the PON, tag 200 can be pushed, and then tag
200 will be popped in the downstream.
Once a tag is used as a single-tagged VLAN, it cannot also be used in double-tagged
VLANs. For example, if VLAN 300 is single tagged:

It cannot be used as the inner tag of a double-tagged VLAN because the doubletagged VLAN would require VLAN 300 to push an outer tag.

It cannot not be used as the outer tag in a double-tagged VLAN because then it
would get popped in the downstream direction.
For video, the specified P-bit must match the CoS type of bandwidth profile.
The ONT does not support heterogeneous tagging in the MDU case for video service.
In double-tagged VLANs, if the inner tag is applied to multiple ONT subscriber ports, it
is an N:1 VLAN.
For single-tagged VLANs, if the outer tag is applied to multiple ONT subscriber ports, it
is an N:1 VLAN.
If a given VLAN, single- or double-tagged is applied to a single ONT subscriber port, it
is 1:1 VLAN.
VLAN Association to voice services:

The IP Host object references a service tag action that indicates the voice service
VLAN by one of the following methods:

An IP host can directly specify an outer tag, when the referenced service tag action
states "Specified in Service" for the Outer Tag parameter.

This allows you to apply a different VLAN tag for the same service type (SIP, TDM
gateway, H.248 gateway, MGCP, or T1 PWE3) on each ONT.

An IP host can reference a service tag action that specifies the service VLAN ID for
the provisioned voice services.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
139


This allows you to apply the same VLAN tagging for all ONTs that use the
referenced service tag action object.

The VLAN assignment must be different between the VoIP IP host and the
subscriber port. Sharing VLANs between a subscriber port and a VoIP IP host is not
supported.
For RG specific (Gateway) services (as opposed to half-bridge [HB] or full-bridge[FB]),
only “Change Tag” and “Add and Change Tag” actions are supported. The concept of
provisioning this way was derived from the same topology that is observed today in
deployments that utilize external non-Calix RGs. This is especially used in scenarios
where a third-party RG is downstream of a regular GPON ONT. From a deployment
perspective, the HGW ONT then supports two logical components; a regular GPON
ONT and an RG. In this scenario, the ONT would receive tagged traffic from the
downstream RG and the ONT would either change the received tag and send it upstream
single-tagged or either change the received tag, send it upstream, and the OLT would
then add the second tag.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
140
Example service-tag action configurations for data services
VLAN-per-service
Applies the specified service-tag action to the
matched traffic.
Matches all untagged traffic on the ONT Ethernet
port.

Adds VLAN ID 300

Marks with P-bit 0
The upstream traffic on a service VLAN must have
the same P-bit value as is set for downstream
traffic.
VLAN-per-subscriber
Applies the specified service-tag action to the
matched traffic.
Double tags all untagged traffic arriving on the ONT
port.

Outer tag is explicitly set to 300

Inner tagged is defined when adding the service
to a port

Upstream traffic is marked with P-bit 0
The upstream traffic on a service VLAN must have
the same P-bit value as is set for downstream
traffic.
Before starting
Before starting the service tag action creation process, check that the following conditions are
met:



All VLANs that were specified in the service tag action have already been created on the
E7.
The match list that you want to use in the tag action has already been created.
The PON Class of Service (CoS) is defined.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
141
Parameters
You can provision the following parameters for service tag actions:
Parameter
Description
Valid Options
Name*
Descriptive name of service tag action.
text string
Action*
Specifies the tag action to perform if the match criteria is met.
Add Tag, Add 2 Tags,
Change Tag, Add and
Change Tag
Match List*
Name and ID of the service match list to use for this tag action.
Any established service
match list
S-VLAN (Outer
Tag)
VLAN ID for the new outer tag. The specified VLAN must already be
provisioned in the system. Alternately, select use the tag value specified
in the ONT port service provisioning "use-svc" indicates that the VLAN ID
will be specified when you provision a service on the ONT port.
Specified in Service, Enter
Value (1-4093)
C-VLAN (Inner Tag)
Name of VLAN for the new inner tag. The specified VLAN must already
be provisioned in the system. Alternately, "use-svc" indicates that the
VLAN ID will be specified when you provision a service on the ONT port.
Specified in Service, Not
Used, Enter Value (1-4093)
Note: This parameter only applies if the selected action is "Add 2 Tags"
or "Add and Change Tag."
Outer P-Bit Source
Specifies where to derive the P-bit value for the outer tag. You can either
promote the P-bit from the subscriber tag, or set an explicit P-bit value in
the tags. The upstream traffic on a service VLAN must have the same Pbit value as is set for downstream traffic. The P-bit value must also be
consistent with the class of service type, as defined in the PON Class of
Service (CoS) table.
Specify P-bit ‡, Map a layer3 priority, From CoS
Note: If you select “Map a layer-3 Priority,” then, when creating the
service, you must select a PON CoS parameter of User1-4 or CoS1-4.
Do not leave the system-default parameter of “derived” as there is no
single unique P-bit specified from which to derive the intended CoS.
Outer P-Bit
Value to use for P-bit marking the outer tag when the Outer P-bit Source
is set to "Specify P-Bit."
0-7, copy
Copy indicates that the E7 copies the P-bit value set in service provider
supplied Residential Gateways (RGs). This option copies the subscriberside Q-Tag P-Bits to a single C-tag or S-Tag, or to the inner C-Tag of a
double-tagged Service.
Inner P-Bit Source
Specifies where to derive the P-bit value for the inner tag. You can either
preserve the P-bit from the subscriber tag, or set an explicit P-bit value in
the tags.
same-as-outer ‡, Specify PBit
Note: This parameter only applies for GPON when the selected action is
"Add 2 Tags" or "Add and Change Tag."
Inner P-Bit
Value to use for P-bit marking the inner tag when the Inner P-bit Source
is set to "Specify P-Bit."
0-7, preserve
Preserve indicates that the E7 preserves the P-bit value set in service
provider supplied Residential Gateways (RGs). This option copies the
subscriber-side Q-Tag P-Bits to a single C-tag or S-Tag, or to the inner
C-Tag of a double-tagged Service.
Note: This parameter only applies if the selected action is "Add 2 Tags"
or "Add and Change Tag."
CoS
CoS ID to use for P-bit marking the outer tag when the P-bit Source is set
to "Specify CoS." This value identifies the PON class of service.
1-4
Untagged P-Bit
When untagged upstream frames with the preserve or copy parameters
set for inner or outer P-bits, this "untagged P-bit" value sets the P-bit on
the untagged frame.
0-7
Note: This parameter only applies for GPON when the selected action is
"Add 2 Tags" or "Add and Change Tag."
*Required fields
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
142
To create a service tag action
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Service > Tagging > Tag
Actions.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > Tagging > Tag Actions >
Profiles.
2. In the menu, click Create.
3. Reference the table above to configure the parameters.
4. Click Create.
5. Associate the tag action to an ONT port when provisioning a service.
For CLI:


create svc-tag-action <name> type <add-2-tags|add-and-change> outer
<VLAN-ID> inner <VLAN-ID> svc-match-list <l-name> use-p-bit|derive-pbit
create svc-tag-action <name> type <add-tag|change-tag> outer
<VLAN_ID|use-svc-vlan> svc-match-list <l-name> use-p-bit|derive-pbit|untagged-p-bit

show svc-tag-action [name]

delete svc-tag-action <name>
Creating Ethernet Port Class of Service Profile
This topic describes how to create a Class of Service (CoS) profile to associate with an
Ethernet port so traffic is sent at a particular rate by controlling the queue of packets. At
egress, the E7 maps 8 priority CoS queues (0–7) to the P-bit values of the traffic, with the
highest priority queue matching P-bit 7 and the lowest priority queue matching P-bit 0. You
can configure each of the CoS queues with a maximum and minimum bandwidth rate.
On a per-port basis, the E7 also supports the ability to shape the aggregate traffic that
includes a maximum rate and a maximum burst size that determines the level to which traffic
is allowed to deviate from the configured rate shaper. The E7 auto-calculates the burst size if
a value is not specified.
Auto-calculated burst size = Number of bits that can be transmitted in 80ms at the configured rate limit
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
143
Example


Rate limit = 100 Mbps
Calculated burst size applied = 8,000 Kbits
Calix recommends the port burst size parameter reflect double the Round Trip Delay (RTD)
of the network, with 40 ms used as the default RTD. It is not possible to have a burst size
less than the MTU of the interface.
CoS application for Link Aggregation Groups (LAG)
Rate limiters and shapers on a LAG are applied as follows:


The maximum and minimum bandwidth rates per CoS are applied to the LAG interface
on ingress. The resulting rate limit is distributed over all links in the LAG.
The port shaping rate and burst size for traffic shaping are applied per-Ethernet port
independent of the other links in the LAG interface.
See "Traffic Management" and "Data Path" in the Calix E7 Engineering and Planning Guide.
Note: The upstream traffic on a service VLAN must have the same priority value as is set
for downstream traffic. The priority value must also be consistent with the class of service
type as defined in the Ethernet port CoS table.
Class of service parameters
You can provision the following parameters for class of service:
Parameter
Description
Valid Options
Name*
Name of COS queue.
text string
Queue 1 Rate
Shaping rate for queue 1, specified in Mbps. The allowed range is 1–
10000.
1–10000 Mbps
Queue 1 Min
Bandwidth
Minimum bandwidth for queue 1, specified in Mbps. The allowed range
is 1–10000.
1–10000 Mbps
Queue 2 Rate
Shaping rate for queue 2. Shaping rates are specified in Mbps.
1–10000 Mbps
Queue 2 Min
Bandwidth
Minimum bandwidth for queue 2, specified in Mbps. The allowed range
is 1–10000.
1–10000 Mbps
Queue 3 Rate
Shaping rate for queue 3, specified in Mbps. The allowed range is 1–
10000.
1–10000 Mbps
Queue 3 Min
Bandwidth
Minimum bandwidth for queue 3, specified in Mbps. The allowed range
is 1–10000.
1–10000 Mbps
Queue 4 Rate
Shaping rate for queue 4, specified in Mbps. The allowed range is 1–
10000.
1–10000 Mbps
Queue 4 Min
Bandwidth
Minimum bandwidth for queue 4, specified in Mbps. The allowed range
is 1–10000.
1–10000 Mbps
Queue 5 Rate
Shaping rate for queue 5, specified in Mbps. The allowed range is 1–
10000.
1–10000 Mbps
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
144
Parameter
Description
Valid Options
Queue 5 Min
Bandwidth
Minimum bandwidth for queue 5, specified in Mbps. The allowed range
is 1–10000.
1–10000 Mbps
Queue 6 Rate
Shaping rate for queue 6, specified in Mbps. The allowed range is 1–
10000.
1–10000 Mbps
Queue 6 Min
Bandwidth
Minimum bandwidth for queue 6, specified in Mbps. The allowed range
is 1–10000.
1–10000 Mbps
Queue 7 Rate
Shaping rate for queue 7, specified in Mbps. The allowed range is 1–
10000.
1–10000 Mbps
Queue 7 Min
Bandwidth
Minimum bandwidth for queue 7, specified in Mbps. The allowed range
is 1–10000.
1–10000 Mbps
Queue 8 Rate
Shaping rate for queue 8, specified in Mbps. The allowed range is 1–
10000.
1–10000 Mbps
Queue 8 Min
Bandwidth
Minimum bandwidth for queue 8, specified in Mbps. The allowed range
is 1–10000.
1–10000 Mbps
Port Shaping Rate
Aggregate shaping rate for the port, specified in Mbps. The allowed
range is 1–10000.
none (or keyword
"unshaped")
Alternately, select none to indicate that shaping should not be done.
Enter Value: 1–10000 Mbps
or select a value from the list
Aggregate burst size for port, specified in Kbits. The allowed range is 1
to 128000.
auto (or keyword "auto")
Port Burst Size
Alternately, select auto to automatically calculate the burst size.
Enter Value: 1–128000
Kbits or select a value from
the list
* Required field
To create a class of service
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7 CoS Profile.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > CoS > Ethernet > Create.
2. Reference the table above to configure the parameters.
3. Click Create.
4. Associate the class of service profile to an Ethernet port so traffic is sent at a particular
rate by controlling the queueing of packets.
5. See Configuring an Ethernet Port (on page 67).
For CLI:
create cos-queue-cfg <queue name> [queue-*-rate|queue-*-min-bw|portrate|port-burst-size]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
145
Creating VLAN Tag Actions on an Ethernet Interface
This topic describes how to create VLAN tag actions on an E7 edge or access link interface.
A tag-action allows you to add or change, or add and change VLAN tags on packets that are
received on a specified GE or 10GE interface. You can use a set of matching criteria to
select which packets to transform. Or, packets can be transformed unconditionally.
See the Calix E-Series Engineering and Planning Guide for an example of an E7 Ethernet
interface tag action and an interface QoS policy being applied to an Ethernet interface.
While tag actions are typically described as being applied to packets received (ingress traffic)
on an Ethernet port interface, the reverse of the tag action is applied to packets transmitted
(egress direction) from the interface. For example, if an Add-Tag action is applied to an
interface, that same tag is stripped from packets leaving the interface.
The following VLAN tag actions can be assigned to an edge or access link interface within
the networking domain:




Add Tag - The "add-tag" action adds an outer tag either on all packets on an interface,
or only on packets that match a specified VLAN ID or P-bit.
Add 2 Tags - The "add-2-tag" action adds an outer tag and an inner tag with the
specified VLAN IDs on packets of untagged traffic.
Change Tag - The "change-tag" action changes the outermost tag to the specified
VLAN ID on packets that match a specified VLAN ID.
Add and Change Tag - The "add-and-ch" action changes the tag and then adds an
outer tag on packets that either match a specified VLAN ID or are priority-tagged
frames.
Note: Tag-actions can only be applied to edge or access link interfaces. To create tag actions
for an ONT Ethernet or xDSL port subscriber service, you must use Service Tag Actions.
Configuration guidelines




Tag actions can only be assigned to edge or access link interfaces within the networking
domain and are defined with respect to ingress traffic.
When you create a tag-action, the interface automatically becomes a member of the
VLAN specified in the tag-action.
When you create an add-tag action, the P-bit of the incoming tag is automatically copied
into the P-bit of the added tag.
You can configure only one of the following attributes on a given VLAN on a given
interface:

VLAN membership

Tag-action (add, add-2-tags, change, or add-and-change)

Native VLAN
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
146









To forward untagged traffic, an access interface must have an add-tag action, add-andchange, or add-2-tags action applied to untagged frames, assigning the traffic to a VLAN.
An edge or access link interface can be associated with a particular VLAN either through
a VLAN membership or through a tag-action, but not through both.
Interfaces can be associated with additional VLANs through memberships or tag-actions.
An interface role cannot be modified when it is assigned a tag-action.
The E7 can perform the following tag actions on a VLAN that has IGMP enabled:

Add-tag action to untagged Ethernet frames

Change-tag action to change the VLAN ID at network administrative boundaries
If no matching criterion is assigned to a tag action, then the tag action is performed on all
packets entering the specified interface, except for the packet traffic on VLANs that have
an associated membership with the interface. When the match rule is set to ignore and pbit any that is the same as no matching criterion assigned. You can see this if you create a
tag action and leave those fields blank. It will be set to ignore.
For double-tagged packets, the outer VLAN ID must match a provisioned VLAN. The
inner tag does not have to match a provisioned VLAN ID.
A priority tagged frame has a new tag added or changed-to with the specified tag value.
Upon egress, the frame still carries the original priority bits onto the newly added or
change-to VLAN tag.
If an Ethernet interface has both a VLAN tag action and a policy map applied, the tag
action function is applied to the interface before the policy map function.
Example add-tag-action configurations
Create an action to add a tag (VLAN 400)
to all traffic on the associated interface.
Create an action to add a second tag
(VLAN 400) to all VLAN 401 traffic on the
associated interface.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
147
Create an action to add a tag (VLAN 400)
to all traffic based on the P-bit for the
associated interface.
Create an action to add a tag (VLAN 400)
to all traffic based on the P-bit and outer
tag on the associated interface.
Example application configuration for tag-action versus VLAN membership:
For incoming traffic where the voice and video services are single-tagged and the per-portdata VLANs are double-tagged:

VLAN-per-port for data traffic

Single voice service VLAN

Single video service VLAN
Configure the following:
1. Create a voice VLAN and a video VLAN and add the interface to each of the VLAN
memberships.
2. Create a no-match add-tag action to the interface for all remaining VLANs to add an
outer data service tag.
Before starting
Before starting the VLAN tag action process, check that the following conditions are met:


The VLANs must already exist in order to create tag actions.
The interface that is the target for the tag action must have the edge or access role
assigned.
Parameters
You can provision the following parameters for VLAN tag actions to an Ethernet interface:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
148
Parameter
Description
Valid Options
Matching Tag
Specifies the match criteria. If you select Enter Value, then you must also
specify the VLAN ID value to match. VLANs can be specified by name, or by
numeric VLAN ID.
(VLAN IDs 1002-1005 are reserved for E7 operation.)
ignore, any, untagged,
priority,
Enter Value (then enter a
VLAN ID 2-4094)
Matching pbit
P-bit value that specifies the VLAN priority value to match.
pbit-0 to pbit-7, pbit-any,
or leave blank
Action Performed*
Specifies whether to add, change, or add and change tags to incoming
packets.
add-tag
add-2-tags
ch-tag
add-and-ch
S-VLAN (Outer Tag)*
New VLAN ID.
(VLAN IDs 1002-1005 are reserved for E7 operation.)
2-4093
C-VLAN (Inner Tag)
New VLAN ID.
(VLAN IDs 1002-1005 are reserved for E7 operation.)
ignore, any, untagged,
Enter Value (then enter a
VLAN ID 2-4093)
Note: This parameter only applies if the Action Performed selection is "add2-tags" or add-and-change.
* Required field
To add VLAN tag actions to an E7 Ethernet interface
1. On the Navigation Tree, click Interfaces.
2. Double-click the specific interface where you want to add a tag action.
Note: The tag actions only apply to interfaces assigned as edge or access link.
3. Click the Tag Actions tab.
4. From the menu, click Create.
5. Reference the table above to configure the parameters.
6. Click Create.
For CLI:

To add a tag to all packets on an interface:
create tag-action add-tag <vlan ID> interface <interface name>

To add a tag only to the packets that match specific criteria on an interface, append one
of the following to the command above:
match-pbit <pbit value>
match-tag <vlan ID>
match-tag <vlan ID> match-pbit <pbit value>
Note: Using match-pbit criterion without using match-tag criterion will match only
802.1P packets (reserved VLAN 0).

To add an outer tag and an inner tag to untagged traffic on an interface:
create tag-action add-2-tags outer <vlan id> inner <vlan id> interface
<interface name> match-untagged
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
149

To change the outermost tag on packets that match a specific VLAN ID.
create tag-action change-tag <vlan ID> interface <interface name> match-tag
<match vlan ID>

To change the tag and add an outer tag on packets that match either a specific VLAN ID
or priority-tagged (P-bit) frames:
create tag-action add-and-change outer <vlan id> inner <vlan id> interface
<interface name> match-tag <vlan id>
create tag-action add-and-change outer <vlan id> inner <vlan id> interface
<interface name> match-prio-tag p-bit any
Creating a Class Map and Rules
Policy maps are lists of QoS-related actions to perform on packets that match certain criteria.
The matching criteria are specified by an associated classification map that lists rules to
identify packets, such as VoIP traffic.
This topic describes how to create a class map and class rules that specify certain selection
criteria, such as P-bit or VLAN values, to classify traffic from the network that is arriving at
the E7. If packets match the criteria listed in the class map, an associated policy map states
the Quality of Service (QoS) actions to perform on those identified packets. The class map
can specify whether packets must match any or all rules in order to be selected.
Class map rule for untagged traffic destined for the Native VLAN
The E7 Ethernet port Trunk and Edge interfaces are always associated with at least one
VLAN, through the native VLAN attribute (VLAN 1 by default). The native VLAN ID is
specified on the interface and is used for untagged user traffic on that interface.
Note: Interfaces with the Access role do not support a native VLAN. To forward untagged
traffic on E7 Ethernet ports with an Access interface, an add-tag action must be applied to
untagged frames, assigning the traffic to a designated VLAN.
To create a class rule for matching untagged traffic, do the following:
1. Specify the native VLAN ID when defining the Ethernet Interface attributes.
2. Set the following parameters when creating a class rule:

Match pbit = pbit-any

Match Outer = native VLAN ID

Match Inner = Any
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
150
For example, if you specify the native VLAN ID as 4 for the Ethernet interface, the class
rule for matching untagged traffic would appear as follows:
3. Apply the class rule to a class map, and then in turn, associate the class map to a policy
map that is associated to the Ethernet interface where you specified the Native VLAN
ID.
Configuration guidelines


If the "Match Type" is set to "all," a traffic packet matches the class map criteria if it
matches all of the rules in the map. In this case, you can add multiple rules to a class map
as long as the rules do not conflict. In practice, this limits you to adding one match-tag
rule, one match-2-tags rule, and one match-p-bit rule or match dscp rule.
If the "Match Type" is set to "any," you can add up to the limit of 100 class rules.
Class map and class rule parameters
Parameter
Description
Valid Options
Name*
Name of classification map.
Any existing class map
Map Type
Match type.
any, all ‡
Index*
Index of rule in map. This is a numeric index value that uniquely identifies
this object within the system. Index values start with 1.
1-100
Match pbit
P-bit value (range 0-7) that specifies the VLAN priority value to match.
Alternately, if "pbit-any" is used or the parameter is not specified, the Pbit value is not considered.
pbit-0 to pbit-7,
pbit-any ‡
Match Outer
Outer VLAN ID to match. VLANs can be specified by name or by numeric
VLAN ID (range 1-4093). Selecting "Any" or "Ignore" indicates a match
for both tagged and untagged traffic.
Ignore ‡
Enter Value
Match Inner
Inner VLAN ID to match. VLANs can be specified by name or by numeric
VLAN ID (range 1-4093).
Ignore ‡, any, untagged,
Enter Value
Match DSCP
DSCP value to match.
Not used ‡, Enter Value:
DSCP value 0-63, or: be
cs0, cs1, af11, af12, af13,
cs2, af21, af22, af23, cs3,
af31, af32, af33, cs4,
af41, af42, af43, cs5, ef,
cs6, cs7.
*Required field
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
151
To create a class map
1. On the Navigation Tree, click E7.
2. Click Policies > Class Map.
3. In the menu, click Create.
4. In the Create Class Map dialog box, do the following:
a. In the Name box, enter a descriptive name of the classification map that you are
creating.
b. In the Map Type list, select whether the packets must match any or all of the criteria
listed in the class map.
5. Click Create.
For CLI:

create class-map <c-map name>

create class-map <c-map name> match-type all

create class-map <c-map name> match-type any
To create a class rule
1. If you have not already done so, create a class map. See "To create a class map," above.
2. On the Navigation Tree, click E7.
3. Click Policies > Class Map.
The table of the previously created class maps appears.
4. Double-click the name of the class map in which you want to add a class rule.
5. Click Create.
6. Reference the table above to configure the parameters.
7. Click Create.
8. Associate the class map with a policy map that is associated to an E7 port interface to use
on ingress traffic packets. See Creating a Policy Map and Policies (on page 152).
For CLI:



add class-rule <rule index> to-map <c-map name> match-all
add class-rule <rule index> to-map <c-map name> match-pbit <P-bit
value>
add class-rule <rule index> to-map <c-map name> match-tag <outer vlan
ID> [match-pbit]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
152



add class-rule <rule index> to-map <c-map name> match-2-tags outer
<outer vlan ID> inner <inner vlan ID> [match-pbit]
add class-rule <rule index> to-map <c-map name> match-dscp <dscp
value>
add class-rule <rule index> to-map <c-map name> match-tag <outer vlan
ID> [match-dscp]
Creating a Policy Map and Policies
This topic describes how to create a policy map and policies that specify what Quality of
Service (QoS) actions to perform on ingress traffic packets when the packets match selection
criteria. The selection criteria are listed in a class map that is associated with the policy map.
In turn, the policy map is associated with an E7 Ethernet port interface.
See Creating a Policy Map for L3 Priority Mapping (on page 154) for instructions on using a class
map to match the layer-3 priority value of incoming frames of ingress traffic on Trunk and
Edge Ethernet (GE/10GE) ports, and then using a policy map to assign a corresponding Pbit (priority) value into the classified traffic.
See the Calix E-Series Engineering and Planning Guide for an example of an E7 Ethernet
interface tag action and an interface QoS policy being applied to an Ethernet interface.
The QoS actions that can be taken when packets match the selection criteria are as follows:



Out P-bit - marks the traffic by specifying a P-bit value to properly prioritize the traffic.
Upon egress, the frame is still priority tagged with the original P-bit value. The upstream
traffic on a service VLAN must have the same P-bit value as is set for downstream
traffic. The P-bit value defined in the policy map must be consistent with the class of
service type, as defined in the Ethernet port Class of Service (CoS) table.
Rate Limit - ensures ingress traffic does not exceed a specified bit rate.
Maximum Burst Size - ensures that the bursting nature of the traffic is reduced to the
specified value. Set the maximum burst size to a value greater than default when using
jumbo frames (for example 9000 kbyte) at higher rates. Typically, set the burst to the
amount of traffic sent in twice the round trip time. Also consider whether the traffic is
shaped before reaching the E7; the edge device that shapes traffic greatly reduces the
buffer requirements in the infrastructure device. Also see Creating Ethernet Port Class of
Service (on page 142) for information on maximum rate and burst size on a per-port basis.
Configuration Considerations

The E7 ports have a single-rate traffic shaping function, differing from the MEF scheme
and terms. For example, in MEF terms, Committed Burst Size (CBS) is a component of a
two-rate traffic shaping system. Where you have:

CIR (Committed Information Rate)

CBS (Committed Burst Size) for the CIR buffer

EIR (Excess Information Rate)

EBS (Excess Burst Size) for the EIR buffer
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
153
However, with the E7 single-rate configuration settings, you have:




Maximum Rate

Burst Size
Consider the provisioned Maximum Rate to be the equivalent of the provisioned
Committed Information Rate (CIR) rate in a two-rate system when the Excess
Information Rate (EIR) value = zero. That is, CIR + (EIR = 0) = PIR = Max.
The policies are processed in a specified sequence (lowest sequence number first), so
when a match occurs, no more policies are processed for that packet. This process is
important when you have overlapping match criteria. For example: If you create multiple
policy rules that specify an Out P-bit, only the policy rule with the lowest sequence
number ID is carried out.
Ethernet port interfaces have the following aspects:

For Trunk interfaces, any policy map assignment is allowed.

For Edge and Access interfaces, if a policy map contains a two-tag classification, the
edge or access link must have a tag-action that adds the outer tag being matched by
the class rule.
Before starting
Ensure the class map that you want to associate to the policy map is already created and
includes class rules.
Policy map and policy parameters
Parameter
Description
Valid Options
Name*
Name of policy map.
text string
Seq Num*
Numeric value that specifies the sequence for processing the policies in
the policy map. The lowest sequence number is processed first. If you
create multiple policy rules that specify an Out P-it, only the policy rule
with the lowest sequence number ID is carried out.
1-1500
Class Map*
Name of class map to associate to the policy action.
Any existing class map
Out pbit
P-bit value that specifies the VLAN priority value. The default setting of
pbit-none does not alter the existing pbit. The upstream traffic on a
service VLAN must have the same P-bit value as is set for downstream
traffic. The P-bit value must also be consistent with the class of service
type as defined in the Ethernet port CoS table.
pbit-0 to pbit-7,
pbit-none ‡
Default = pbit-none
Rate Limit
Whether to set an maximum allowable ingress rate limit. this is the
allowable processing rate in Mb/s at which packets entering an E7
Ethernet port interface are forwarded. If you select "Set a Rate Limit"
you must also enter a limit value.
none ‡
Set a Rate Limit
(64kb/s to 10000mb/s )
Max Burst Size
Maximum allowable burst size in kilobytes or use "m" suffix for
megabytes. You must set a non-zero value for the operation to
complete. Typically, set the burst to the amount of traffic sent in twice
the round trip time.
none ‡, Set a Burst Size (416000 kilobytes)
*Required fields
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
154
To create a policy map
1. On the Navigation Tree, click E7.
2. Click Policies > Policy Map.
3. In the menu, click Create.
4. In the Create Policy Map dialog box, enter a descriptive name for the policy map that you
are creating.
5. Click Create.
For CLI:
create policy-map <p-map name>
To create a policy
1. If you have not already done so, create a policy map. See "To create a policy map,"
above.
2. On the Navigation Tree, click E7.
3. Click Policies > Policy Map.
The table of the previously created policy maps appears.
4. Double-click the name of the policy map in which you want to add a policy.
5. In the menu, click Create.
6. Reference the table above to configure the parameters.
7. Click Create.
8. Associate the policy map with an E7 Ethernet port interface to use on ingress traffic
packets. See Configuring an Ethernet or LAG Interface (on page 73).
For CLI:
add policy <policy index> to-map <p-map name> class-map <c-map name> [setpbit|rate-limit|max-burst-size]
Creating a Policy Map for L3 Priority Mapping
For ingress traffic on Trunk and Edge Ethernet (GE/10GE) ports, you can use a class map
to match the layer-3 priority value of incoming frames, and then use a policy map to assign a
corresponding P-bit (priority) value into the classified traffic.
This topic shows example outlines of single, specific DSCP value and multiple values used to
define mapping onto P-bits. This assumes that the upstream routers or aggregation switch
are not P-bit aware and do not manage traffic based on P-bit marking. Instead, DSCP is used
for this purpose.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
155
For detailed instructions on how to create policy maps, see the following topics:


Creating a Class Map and Rules (on page 149)
Creating a Policy Map and Policies (on page 152)
Note: The upstream traffic on a service VLAN must have the same priority value as is set
for downstream traffic.
For further information on layer-3 priority mapping, see:

Mapping Layer-3 Priority Values to P-Bits (on page 157)
The following table shows the different classes of traffic as they correlate to AF ranges.
Classes 1 to 4 are referred to as Assured Forwarding PHB (Per Hop Behavior). AF is divided
into four independently forwarded AF classes and is defined in RFC 2597. Within each AF
class there are three different levels of drop precedence. In case of network congestion, a
packet with a higher drop precedence (drop probability) value would be discarded first.
RFC 2597 recommends the following DSCP codepoints for the four AF classes.
Drop
Probability
Class 1
Class 2
Class 3
Class 4
Low
AF11
(DSCP 10)
AF21
(DSCP 18)
AF31
(DSCP 26)
AF41
(DSCP 34)
Medium
AF12
(DSCP 12)
AF22
(DSCP 20)
AF32
(DSCP 28)
AF42
(DSCP 36)
High
AF13
(DSCP 13)
AF23
(DSCP 22)
AF33
(DSCP 30)
AF43
(DSCP 38)
The AFxy, format uses x as the class number and y as the drop precedence.
Expedited Forwarding (EF) is defined in RFC 2598 and falls under the DSCP Class 5 (CS5).
EF has the characteristics of low delay, low loss and low jitter. These characteristics are
suitable for voice, video and other realtime services. EF traffic is often given strict priority
queuing above all other traffic classes. The RFC recommended DSCP value for EF
corresponds to a DSCP value of 46.
Best Effort (BE) is indicated by a DiffServ value of 0.
Example 1: Single DSCP value mapping to CoS 5
1. Create class map (CoS 5).

Create class rule:

Match pbit pbit-any

Match Outer 100

Match Inner ignore

Match DSCP 40 (equates to CS5)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
156
2. Create policy map (CoS 5)

Create Policy: class map (CoS 5), Out pbit 5
3. Associate the policy map to the Ethernet port interface.
Example 2: Multiple DSCP value mapping
1. Create class maps and add rules.
a. Create class map (mix1)

create rule 1: match tag 101, match-dscp af11
b. Create class map (mix2)

create rule 1: match tag 102, match-dscp cs2
c. Create class map (mix3)

create rule 1: match-dscp af33
d. Create class map (mix4)

create rule 1: match tag 201, match-dscp cs4
e. Create class map (mix5)

create rule 1: match tag 202, match-dscp ef
f. Create class map (mix6)

create rule 1: match tag 203, match-dscp cs6
g. Create class map (mix7)

create rule 1: match tag 207, match-dscp 56
h. Create class map (op4)

create rule 1: match p-bit 4, match-dscp af33
2. Create policy maps and add policies.
a. Create policy map (mix)

create policy 1, class map (mix1), set P-bit 1

create policy 2, class map (mix2), set P-bit 2, rate-limit 15, max burst size 4

create policy 3, class map (mix3), set P-bit 3

create policy 4, class map (mix4), set P-bit 4

create policy 5, class map (mix5), set P-bit 5

create policy 6, class map (mix6), set P-bit 6

create policy 7, class map (mix7), set P-bit 7, rate-limit 10, max-burst size 4
b. Create policy map (0p4)

create policy 1, class map (0p4), set P-bit 3
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
157
3. Add policy maps to Ethernet interfaces.

1/x3 policy map (mix)

2/x3 policy map (mix)

2/g4 policy map (0p4)
Related topics


Creating a Class Map and Rules (on page 149)
Creating a Policy Map and Policies (on page 152)
Mapping Layer-3 Priority Values to P-Bits
The E7 supports mapping Differentiated Services Code Point (DSCP) values, used for
packet classification on DiffServ networks (defined in RFC 2474 and RFC 2475), to IEEE
802.1p priority-bit values to classify traffic priority.

Traffic coming from the subscriber going upstream to Access ports can reference
the use of layer 3 priority values from the service tag action associated with the service,
and then from the GPON Ethernet port, indicate whether to use the system-default
profile named "access" or a custom profile to map DSCP values to P-bit values.


Guidelines:

Supported with Add-Tag and Add-2-Tags tag actions.

If you select “Map a layer-3 Priority,” in the service tag action, then when
creating the service, you must select a PON CoS parameter of User1-4 or CoS14. Do not leave the system-default parameter of “derived” as there is no single
unique P-bit specified from which to derive the intended CoS.

Only one service per port can use the DSCP-Bit mapping function. However, a
second service of untagged traffic on the same port that matches a specific OUI
value is supported, where that OUI-matching service takes precedence for any
matching frames.

Each port is independent where it can use a different DSCP map.

The T-Series ONTs do not mark the P-bit of broadcast and multicast frames
based on DSCP. T-Series ONTs handle all broadcast / multicast packets from
the subscriber as best-effort and mark them with the default P-bit of the service.

All of the traffic classified by the DSCP map and P-bit-marked according to the
DSCP map table is put into a single queue for upstream scheduling by the OLT.

In the event of congestion on the upstream bandwidth allocation, traffic in the
queue with the highest P-bit is transmitted first, thus preserving the DSCP set by
the downstream router.
Use the following provisioning sequence:
c. Create DSCP to P-Bit map.
See Creating and Modifying a DSCP Map for Ingress Traffic (on page 159)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
158
d. Assign DSCP to P-Bit map to ONT Ethernet port.
See Configuring an ONT Ethernet Port (on page 257)
e. Create tag action with an Outer P-Bit source of “Map a layer-3 Priority.”
See Creating Service-Tag Actions (on page 131)
f. Create service using the defined tag action.
See Creating Data Services (on page 269)
See Creating IP Video Services (on page 285)
Note: The upstream traffic on a service VLAN must have the same priority value as is
set for the downstream traffic.

Traffic coming from the network going downstream to Ethernet Trunk and Edge
ports can use class map, class rules, and policy maps to match the ingress Layer-3 value
of incoming frames and assign a corresponding P-bit (priority) value.
Some service providers' networks include core routers or aggregation switches that are
not setup to use P-bits for traffic management downstream. Instead DSCP is used for
this purpose. In these cases all traffic received by the access node has a P-Bit value of 0,
and the access node needs to set the P-bit at the network interface, or traffic internal to
the access node will be discarded at random (service unaware).
See Creating a Policy Map for L3 Priority Mapping (on page 154).
DSCP traffic classes
The DSCP traffic classes are described in RFC 2474, RFC 2597, RFC 3246, the P-Bit
construct in IEEE 802.1p. The table below shows the mapping between Traffic Classes and
P-bits:
IP DSCP
Name
IP DSCP Abbreviation
CSx
Class Selector (where x is 0 through 7) as defined in RFC 2474
BE
Best Effort (also default)
AFxy
IEEE 802.1p
Mapped to P0 through P7 respectively. For
example: CS0 mapped to P0.
P0
"x" refers to Traffic Class, and "y" refers to Drop Precedence (RFC
2597).
Where x is 1,2,3,4 (higher is better), and y is 1, 2, 3 (lower is better)
AF1y
Assured Forwarding
P2
AF2y
Assured Forwarding
P3
AF3y
Assured Forwarding
P4
AF4y
Assured Forwarding
P5
Expedited Forwarding (RFC 3246)
P6
EF
The following table shows the various traffic types and the acronyms used for them:
User Priority
Acronym
Traffic Type
1
BK
Background
2
-
Spare
0 (Default)
BE
Best Effort
3
EE
Excellent Effort
4
CL
Controlled Load
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
159
User Priority
Acronym
Traffic Type
5
VI
Video, < 100 ms delay
5
VO
Voice, <10 ms delay
7
NC
Network Control
For more information, see the document Calix Engineering & Planning Guide: L2 Ethernet Access
Networks, available on the Calix Resource Center.
Creating and Modifying a DSCP Map for Ingress Traffic
This topic shows you how to create and modify an DSCP Map profile that is applied to a
GPON Ethernet port to enable and/or specify a mapping of the incoming frame DSCP
values to IEEE 802.1p priority bits.
To associate a DSCP Map with a service, do the following:
1. In the service tag action that is going to be applied to the data or video service, select
Map a Layer-3 priority from the P-Bit Source list.
2. On the ONT port where you are going to be provisioning the data or video service,
select the name of the DSCP profile to use from the DSCP/IP Precedence Profile
list.
Note: The upstream traffic on a service VLAN must have the same priority value as is set
for downstream traffic.
Note: If IP traffic on an Access Interface has a DSCP setting other than the values included
in the assigned DSCP map, the E7 system interprets this condition as a mismatch and uses a
"Default" P-bit value from the assigned DSCP Map profile. For example, if you were using
the system-default DSCP Map "Access" and the incoming frames had a DSCP value of 001
001, that value is not included in the assigned DSCP map, so the E7 would use the default Pbit value of 0. However, you can create a DSCP Map with a Default P-bit value of your
choice, and then assign the DSCP Map to the ONT port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
160
The system-default DSCP profile "Access," has values as follows:
DSCP
Value
Meaning
Decimal
Drop
Probability
802.1p
Priority-Bit
000 000
001 000
001 010
001 100
001 110
010 000
010 010
010 100
010 110
011 000
011 010
011 100
011 110
100 000
100 010
100 100
100 110
101 000
101 110
110 000
111 000
BE-CS0
CS1
AF11
AF12
AF13
CS2
AF21
AF22
AF23
CS3
AF31
AF32
AF33
CS4
AF41
AF42
AF43
CS5
EF
CS6
CS7
Default
0
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
46
48
56
n/a
0
1
1
1
1
2
2
2
2
3
3
3
3
4
4
4
4
5
5
0
0
0
Low
Medium
High
Low
Medium
High
Low
Medium
High
Low
Medium
High
Best Effort (BE)
Assured Forwarding (AF) gives assurance of delivery under prescribed conditions
Expedited Forwarding (EF) dedicated to low-loss, low-latency traffic
Default = P-bit assigned for a DSCP value that is not included in the DSCP Map
Note: Calix recommends NOT assigning P-bit value 7 to any DSCP value.
To create a DSCP map
1. In the Navigation Tree, click E7.
2. In the Work Area, click Profiles > DSCP > Create.
3. In the Create DSCP Map dialog, do the following:
a. In the Name box, enter a name that describes the use of this custom profile.
b. In each of the designated DSCP value lists, select the correlating P-bit value,
following site requirements and company policies and procedures to assign 802.1p
priority bit values to the values listed alongside each list box.
Note: Calix recommends to NOT assign any DSCP value to P-bit 7, as subscriber traffic
with P-bit 7 this potentially overrun your network control protocols.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
161
4. Click Create.
For CLI:
create dscp-map <name>
[default|cs0|af11|af12|af13|af21|af22|af23|cs3|af31|af41|ef|cs6|cs7]
To modify a DSCP map
1. In the Navigation Tree, click E7.
2. In the Work Area, click Profiles > DSCP.
3. Double-click the name of the DSCP map that you want to modify.
4. In each of the designated DSCP value lists, select the correlating P-bit value, following
site requirements and company policies and procedures to assign 802.1p priority bit
values to the values listed alongside each list box.
5. Click Apply to save the changes to the map.
For CLI:
set dscp-map <name>
[default|cs0|af11|af12|af13|af21|af22|af23|cs3|af31|af41|ef|cs6|cs7]
show dscp-map
show dscp-map <name>
Enabling Shaper Optimization
Follow the steps below to enable or disable the shaper optimizer. For downstream shaping to
actually take effect, more considerations are involved; traffic shaping and policing guidelines
follow.
To disable shaper optimization
1. In the Navigation Tree, click E7.
2. in the Work Area, click System > Provisioning.
3. In the System form, scroll to view the Enable ONT Downstream Shaping checkbox, and
then click the box to clear it, disabling the ONT shaper optimization function.
4. In the toolbar, click Apply.
Note: By default, the shaper optimization is set to enabled.
For CLI:
set system ont-dwnstrm-shaping [enabled|disabled]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
162
Traffic shaping and policing guidelines
For data services, the E7 provides shaping and policing functions on Calix P-Series
700GE/740GE/760GX ONTs and the 836GE RSG. When specific criteria are met for a
data service (described in "Applying policing and shaping," below), shaping is automatically
enabled for a single Class of Service on a single ONT Ethernet port for provisioned rates up
to 250 Mbps.
The following diagram summarizes the traffic shaping and policing behavior of P-Series
GPON ONT/RSGs.
Notes:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
163


When the ONT/RSG is shaping downstream traffic, the E7 GPON subsystem relaxes
(by 100 Mbps) the per-service policing normally applied to all services in the downstream
direction. This results in the E7 policing traffic grossly exceeding the maximum rate,
while the ONT/RSG shapes typical traffic bursts.
The E7 OLT schedules all traffic upstream to ensure efficient and prioritized use of
GPON bandwidth. Traffic is buffered in the ONT/RSG for periodic transmission,
resulting in shaped traffic for all upstream traffic.
Detailed information on shaping/policing support per configuration, shaping and policing
criteria, and speed-testing guidelines are provided below.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
164
Traffic management recommendations
Calix recommends the following guidelines to achieve consistent and accurate performance
for data services delivered from a Calix P-Series GPON ONT.



Internet access service below 250 Mbps – traffic shaping
L2 VPN / Transparent LAN (MEF E-LINE and E-LAN) services – traffic policing
Very high speed Internet access (> 250 Mbps) – traffic policing
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
165
Applying shaping and policing
Consistent with the above recommendations, by default, the E7 GPON system will apply
traffic shaping to a single internet access data service per ONT (select models listed below)
when the following conditions are met:





Shaping functionality enabled for E7 GPON

In the E7-level Work Area under System > Provisioning, the Enable ONT
Downstream Shaping checkbox is selected (default setting is selected/enabled)

This system-level provisioning enables (or disables) traffic shaping on all ONTs on
the E7 OLT.
Full-bridge mode is not configured
Bandwidth profile Peak Information Rate (PIR) < 250 Mbps
Data traffic is mapped to the lowest GPON CoS compared with all other services on the
ONT/RSG
VLAN settings

IGMP = flood (i.e. IGMP snooping disabled)

DHCP Snoop enabled

MAC FF enabled

IP Source Verify enabled

TLAN disabled
If all of the above criteria are met for a single* data service, then traffic shaping is applied.
Otherwise, traffic policing is used by the system to rate limit data traffic flows.
*Note: If a second data service on the ONT/RSG also meets the above criteria, the service
on the lowest numbered ONT Ethernet port is shaped.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
166
Traffic shaping on P-Series ONTs
700GE and 740GE ONTs, and 800GE RSGs support both traffic shaping and traffic
policing.
Downstream traffic
Downstream internet access traffic is shaped or policed based on the criteria above and the
ONT model.
Provisioned
Service BW
700GE/800GE
(L2 service)
700GE/800GE
(L2 full-bridge)
700GE/800GE
(L3 gateway)
740GE
(L2 service)
0–250 Mbps
Traffic shaped
Traffic policed
Traffic shaped
Traffic shaped
250–1000
Mbps
Traffic policed
Traffic policed
Traffic policed
Traffic policed
Shaping for data services above the capabilities of the GPON system should be provided by
a router/BNG upstream of the E7 OLT.
Upstream traffic
In a GPON FTTP system, upstream traffic is always shaped due to the mechanics of the
shared N:1 GPON transport layer. Upstream traffic is buffered in the ONT and scheduled
for transmission via the Status Reporting - Dynamic Bandwidth Algorithm (SR-DBA). By
default, each service on the PON is mapped to a different GPON CoS and rate limited to
individual limits.
Other ONTs
The 700GX and 760GX ONT families support a fixed traffic management capability.


760GX ONTs provide policing for all data services
700GX ONTs provide shaping for all services up to a 400 Mbps PIR
Creating Data and Video Service Profiles
This section describes how to create profiles and objects that will be associated with data and
video services provisioned on an ONT Ethernet port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
167
For Ethernet services, create the following profiles, as required:
Required
Layer 3
Optional

Match List and Rules (on page 127)

Service-tag Action (on page 131)

Bandwidth Profile (on page 167)*

Multicast Profile (on page 177)* (Video only)

ONT Template (on page 191)

RG Configuration File (on page 194)

RG Management Profile (for ACS) (on page 198)

Ethernet Security Profile (on page 188)

PPPoE Profile (on page 186) (Data only)

IGMP Profile (on page 183) Video only)
Note: *With GPON, the ONT is configured with a bandwidth profile to manage the STBs.
This profile may be as little as 1M. The bandwidth profile is not used for the multicast
streams. The Multicast profile limits the number of streams, which limits bandwidth based
on stream count.
Next steps:
After completing the creation of profiles for data and video services, see the following
sections to continue configuring data and video services:



Configuring a PON (on page 231)
Configuring Data Services (on page 269)
Configuring IP Video Services (on page 285)
Creating an Ethernet Bandwidth Profile for GPON Services
An Ethernet bandwidth profile specifies the upstream and downstream bandwidth rates to
apply to individual Ethernet services on ONT Ethernet ports. Typically, a single bandwidth
profile is applied to many subscriber ports.
Each direction of a traffic shaper can be configured to provide a specific rate for the shaper.
The following values are specified to designate the rate:



Committed Information Rate (CIR): The minimum guaranteed rate for upstream
traffic that the ONT provides for the particular Ethernet service. CIR defines the average
rate in bytes/s of packets up to which the network delivers and meets the performance
objectives defined by the CoS Service Attribute. CIR MUST be >= 0.
Committed Burst Size (CBS): CBS limits the maximum number of bytes available for a
burst of packets sent at the UNI speed to remain CIR-conformant.
Peak Information Rate (PIR): The PIR value is the maximum bandwidth rate for
upstream and downstream traffic that the ONT allows the service to use if bandwidth is
available. PIR defines the average rate in bytes/s of packets up to which the network may
deliver packets but without any performance objectives. PIR MUST be >= 0.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
168

Peak Burst Size (PBS): PBS limits the maximum number of bytes available for a burst
of packets sent at the UNI speed to remain PIR-conformant.
The PBS and the CBS and are measured in bytes and it is recommended that they be
configured to be equal to or greater than the size of the largest possible IP packet in the
stream.
Note: The CMS Global ONT Ethernet Bandwidth Profile includes parameters for
Committed Rate for Downstream and Committed Burst Size for Downstream, however,
those values are only applicable to AE ONT configurations, NOT E7 GPON.
The CIR and PIR values must be consistent with the following:

The Class of Service (CoS) type as defined in the GPON CoS global configuration table
or

The P-bit being used, whether it is specified in the service tag action, or when
provisioning the service if the service tag action referenced the "use in Service" option.
Dynamic Bandwidth Allocation (DBA) is a feature that dynamically changes upstream
GPON bandwidth assignments at the port level based on traffic class and demand.
If explicit CIR/PIR values are included for a PON upstream CoS profile, these values take
precedence over the Ethernet bandwidth profile associated to the service. Additionally, the
upstream CIR is only implemented at the upstream PON.
Examples:


If the user-defined PON CoS (user 1-4) CIR is 0, there will be no guaranteed bandwidth,
even if the service has set a CIR via the Ethernet bandwidth profile.
If the user-defined PON CoS (user 1-4) PIR is less than the Ethernet bandwidth profile
PIR, the service will only get the PON CoS PIR as the peak rate.
See GPON QoS (on page 117) and Creating a PON Upstream Class of Service Profile (on page
124).
Because PON networks carry voice, video, and data traffic with different Quality of Service
(QoS) requirements, including controlled latency and jitter (packet delay and packet delay
variation), and loss characteristics, as well as other specifications defined by Service Level
Agreements (SLAs). The total upstream GPON bandwidth (1.2 Gbps) is shared among the
subscribers and mapped to the following commonly-defined Per-Hop Behavior (PHB) traffic
classes:

Default PHB (Per hop behavior)—typically best-effort traffic
Any traffic that does not meet the requirements of any of the other defined classes is
placed in the default PHB. Typically, the default PHB has best-effort forwarding
characteristics.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
169

Expedited Forwarding (EF) PHB—dedicated to low-loss, low-latency traffic
The IETF defines Expedited Forwarding behavior in RFC 3246. The EF PHB has the
characteristics of low delay, low loss and low jitter. These characteristics are suitable for
voice, video and other real-time services. EF traffic is often given strict priority queuing
above all other traffic classes.

Assured Forwarding (AF) PHB—gives assurance of delivery under prescribed conditions
The IETF defines the Assured Forwarding behavior in RFC 2597 and RFC 3260.
Assured forwarding allows the operator to provide assurance of delivery as long as the
traffic does not exceed some subscribed rate. Traffic that exceeds the subscription rate
faces a higher probability of being dropped if congestion occurs.
The AF behavior group defines four separate AF classes. Within each class, packets are
given a drop precedence (high, medium or low). The combination of classes and drop
precedence yields twelve separate DSCP encodings from AF11 through AF43. Usually,
traffic policing is required to encode drop precedence. Typically, all traffic assigned to a
class is initially given a low drop precedence. As the traffic rate exceeds subscription
thresholds, the policer will increase the drop precedence of packets that exceed the
threshold.

Class Selector PHBs—maintains backward compatibility with the IP Precedence field
Traffic Class
Type
GPON
CoS
E7 P-bits
(default)
Service
Category
Expedited
Forwarding (EF)
4
5, 6, 7
Network
control,
voice, T1/E1
Example:
CIR = 384k
PIR = 0
P-bit = 5
Assured
Forwarding 1
(AF1)
3
4
Video
Example:
CIP = 512k
PIR = 1M
P-bit = 4
E7 BW Profile
DBA Priority For NonFixed Bandwidth
CIR>0, PIR=0
Fixed Bandwidth not subject
to
(PIR is provisioned for "0" to
represent that there is no
PIR independent of the CIR)
Committed Information Rate
(CIR): Guaranteed level of
bandwidth with low Delay
and Delay Variation.
CIR>0, PIR>=CIR
Committed Information Rate
(CIR) +
DBA scheduling
(bandwidth is pre-scheduled
and not re-allocated to other
services when not used)
Committed Bandwidth +
Excess Bandwidth
Priority 1
Peak Information Rate
(PIR).
(Highest Priority)
Both guaranteed and nonguaranteed bandwidth
levels. Moderate Delay and
Delay Variation.
Assured
Forwarding 2
(AF2)
2
3
Application
signaling,
TLAN
CIR>0, PIR>=CIR
Committed Information Rate
(CIR) +
Committed Bandwidth +
Excess Bandwidth
Peak Information Rate
(PIR).
Both guaranteed and nonguaranteed bandwidth
levels. Moderate Delay and
Delay Variation.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Priority 2
170
Traffic Class
Type
GPON
CoS
E7 P-bits
(default)
Service
Category
E7 BW Profile
DBA Priority For NonFixed Bandwidth
Best Effort (BE)
1
0, 1, 2
High-speed
internet
CIR=0, PIR>0
Best Effort Bandwidth
Example:
CIR = 0
PIR = 10M
P-bit = 0
Peak Information Rate
(PIR): No guaranteed
bandwidth levels. Higher
Levels of Delay and Delay
Variation.
Priority 3
(Lowest Priority)
Traffic in the Assured Forwarding classes is characteristically bursty, presenting the
opportunity for re-assignment of its bandwidth allocation between bursts to lower priority
services which indicate demand, such as those with Best Effort bandwidth. Additionally,
some Best Effort traffic may experience light network load conditions, freeing up bandwidth
for other high demand Best Effort subscribers. SR-DBA efficiently allocates available
bandwidth, and supports oversubscription—significantly improving network performance,
and allowing service providers to provide high bandwidth services to many subscribers.
Applying Ethernet bandwidth profiles
When creating services on ONT Ethernet ports, typically the service-tag action identifies an
explicit P-bit. The P-bit determines the PON CoS as per the above table. A given service
must use a bandwidth profile that is consistent with the services PON CoS. For example, if
the service uses P-bit 0, 1, or 2, it is by definition a best effort service and must use a
bandwidth profile where upstream CIR=0, and upstream PIR > 0.
How upstream bandwidth is allocated
The Optical Line Terminal (OLT) provides GPON network terminations. The E7 GPON
cards serve as the OLT, and are responsible for allocating upstream bandwidth to ONTs
either as fixed allocated bandwidth when DBA is disabled, or dynamically (for non-fixed
traffic classes) via the DBA algorithm when DBA is enabled.
A transmission container (T-CONT) is an ONT object that represents a group of logical
connections which appear as a single entity for the purpose of upstream bandwidth
assignment on the PON. Each ONT can have up to four service T-CONTs assigned—one
per PON class of service. On supported ONTs, four additional, user-defined TCONTs may
be assigned. The ONT reports the status of the queues associated with the T-CONTs to the
OLT. Based on demand and the constraints of the DBA algorithm, the OLT facilitates
sharing of the upstream bandwidth by allocating bandwidth grants to the T-CONTs. Excess
bandwidth, either unconfigured or not currently required by a subscriber, is allocated to
subscriber services based on the DBA priority order shown in the table above.
Ethernet Bandwidth Profile Examples:
Best Effort (BE) profile



Upstream CIR 0m
Upstream PIR 50m
Downstream PIR 100m
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
171
The Ethernet service MUST use P-bits 0, 1, or 2; or Cos 1 which is equivalent to 0-2. Best
Effort means, if there is BW available, then up to 50M can be sent for this example. Best
Effort is typically used for data services.
You might want to create three Ethernet Bandwidth profiles to support three tiers if Internet
data service.
Example: Assured Forwarding (AF) profile
AF1:



Upstream CIR 25m
Upstream PIR 100m
Downstream PIR 100m
AF2:



Upstream CIR 50m
Upstream PIR 200m
Downstream PIR 1g
For AF1, the Ethernet service MUST use P-bit 3 or CoS 2, which is equivalent to P-bit 3.
Since the AF definition is the same, it is the P-bit (3 or 4) that determines Assured
Forwarding 1 or Assured Forwarding 2. A “committed” rate of 25M or 50M is guaranteed (in
examples) and if there is extra bandwidth available, then up to 100M or 200M will be
allowed. This profile can also be used for data or, with a P-bit of 4, for video but the cost to
the end-user would increase, since there is a guarantee for part of the service.
You might want to create three Ethernet Bandwidth profiles to support three tiers if video
service.
Example: Expedited Forwarding (EF) profile


Upstream CIR 50m
Downstream PIR 1g
A “committed” rate of 50M is guaranteed. No bandwidth above 50M will be available, but it
will always have 50M assigned, even if no traffic is flowing. This profile is typically used for
voice service. This profile could also be used for video if the end-user agrees to the cost, as
this would be the most expensive.
See Creating a PON Class of Service (on page 122).
DBA configuration guidelines


The sum of guaranteed bandwidth (Committed Information Rate (CIR)), cannot exceed
the total upstream bandwidth of the GPON interface (1.2 Gbps).
DBA is enabled by default.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
172









DBA is set at the GPON port level.
DBA supports up to 64 ONTs per PON.
DBA-managed traffic includes the Assured Forwarding and Best Effort traffic class types
only.
All provisioned Expedited Forwarding bandwidth is fixed and statically pre-scheduled,
and is not available for reuse by the DBA algorithm.
Assured Forwarding services scheduled by DBA have a minimum bandwidth allocation
of 64 Kbps per service, and a maximum of 1G per service.
Best Effort services scheduled by DBA have a maximum bandwidth allocation of 1G per
service.
The DBA algorithm operates on the configured bandwidth profiles for each subscriber
and service, and the perceived demand from the ONTs.
Enable/disable DBA via the Command-line Interface (CLI).
DBA does not support configuration via the Calix Management System (CMS) or the
web interface.
Home Gateway services guidelines
When provisioning High Speed Internet services on the routed WAN interface of a 700GE
ONT or an 836GE RSG, CMS can set a Bandwidth Profile with metering and shaping
supporting up to 200 Mbps of data throughput. If a service profile requires bandwidth
exceeding the 200 Mbps limit, the management model supports an open bandwidth setting
of CIR=0 and PIR=0 that will not apply any bandwidth control at the ONT. In these
applications the High Speed Internet service can be metered and shaped at the OLT,
network router or BRAS. With an open bandwidth setting the effective data throughput over
the Routed WAN interface to a LAN port will approach 1Gbps line rate.
When supporting a combination of L2 bridged ports and routed WAN interfaces, the 700GE
High Speed Internet bandwidth profile with shaping can only be administered on one of
these interfaces. With the 836GE supporting wireless data this High Speed Internet profile is
assumed to always be on the Routed WAN interface. A bandwidth profile can be applied to
the L2 bridged ports but administered using a policer with no shaping. Because it is assumed
that L2 bridged ports are being used for IPTV multicast or private E-LAN or E-Line services
the ability to shape traffic is not necessary in these instances.
Ethernet bandwidth profile configuration guidelines


A given service must use a bandwidth profile that is consistent with the service PON
CoS. For example, if the service uses P-bit 0, 1, or 2, it is by definition a best effort
service and must use a bandwidth profile wherre upstream CIR = 0, and upstream PIR >
0.
The bandwidth limits for all ONT services (in the same class) of a single ONT Ethernet
port are aggregated into a single CoS metered rate, therefore only one service per CoS per
ONT port is allowed.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
173

The E7 ports have a single-rate traffic shaping function, differing from the MEF scheme
and terms. For example, in MEF terms, Committed Burst Size (CBS) is a component of a
two-rate traffic shaping system. Where you have:

CIR (Committed Information Rate)

CBS (Committed Burst Size) for the CIR buffer

EIR (Excess Information Rate)

EBS (Excess Burst Size) for the EIR buffer
However, with the E7 single-rate configuration settings, you have:

Maximum Rate

Burst Size
Consider the provisioned Maximum Rate to be the equivalent of the provisioned
Committed Information Rate (CIR) rate in a two-rate system when the Excess
Information Rate (EIR) value = zero. That is, CIR + (EIR = 0) = PIR = Max.



Bandwidth across the E7 GPON subsystem is managed by the E7 OLT. Bandwidth is
not affected by the number of ONTs on the PON, by the distance of the ONTs from
the OLT, or the split ratio / design.
Downstream, PON traffic management is much like the rest of the E7 core Ethernet
architecture – services can be guaranteed bandwidth, but can also take advantage of
excess bandwidth.

8 P-bit priority classes are transported through the E7 core Ethernet transport and
switching network.

Up to 2.5 Gbps P-bit priority-scheduled traffic is forwarded to the GPON MAC.

Up to 2.4 Gbps non-blocking traffic is sent down the PON to individual ONTs
based on MAC learning.

The E7 OLT enforces the Peak Information Rate for each service.

Downstream traffic is dynamic and all services can burst to the maximum PON rate
in the absence of higher priority traffic.
Upstream on the PON, traffic is scheduled based on a request/grant cycle initiated by
the ONT. Each provisioned service on the PON may have one of three components –
Expedited, Guaranteed and Non-guaranteed. Expedited service has the lowest jitter and
latency and is limited to roughly 50% of the PON upstream bandwidth capacity.

Expedited Forwarding (EF) class limit = 600 Mbps (composed solely of CIR traffic)

The Committed Information Rate (CIR) traffic limit = 1200 Mbps (includes the EF
component)

If the total PON Peak Information Rate (PIR) traffic is over 1200 Mbps, all nonguaranteed traffic shares proportionately the bandwidth not used by the CIR traffic.

Up to 1.2 Gbps capacity upstream
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
174






The OLT schedules all PON traffic based on service provisioning (not actual use).
Once scheduled, traffic allocation is reserved and is not dynamically reallocated to
other services if unused.

The ONT enforces upstream CIR and PIR rates for each service according the
provisioned service bandwidth profile

Upstream Best Effort and the Assured Forwarding non-guaranteed (PIR-CIR) traffic
have equal priority and are oversubscribed as a class. Once the PON has been
provisioned to its upstream capacity, additional non-guaranteed traffic Admitted to
the PON will reduce all non-guaranteed traffic proportionately.

T1 and VOIP services are required to use the Expedited Forwarding class.
The EF traffic could be zero, if the sum of AF CIR is equal to 1200. There would be no
capacity left for non-guaranteed traffic.
All CIR traffic is scheduled at 100% of the requested bandwidth profile, up to an
aggregate limit of 600 Mbps. Only Expedited Forwarding and Assured Forwarding class
types in the GPON CoS global configuration have a CIR component.
After CIR traffic is scheduled, the remaining PON bandwidth is shared proportionally
based on the difference of the CIR and PIR.
When the PON is not over-subscribed in the upstream direction, all services get 100% of
their PIR. When the PON is over-subscribed, no service gets 100% of the requested PIR.
If the aggregate PIR bandwidth exceeds the PON bandwidth capacity, the services are
scheduled a % less than their PIR based on the over-subscribed amount.
Example:
PON bandwidth = 1200 Mbps
3 ONTs with 1 service on each ONT
Rates are configured on the upstream portion of the services, relative to the
oversubscribed amount:
ONT
CIR
PIR
Over (PIR — CIR)
Percentage
#1
50
800
750
750 / 2100 = 35.7%
#2
100
800
700
700 / 2100 = 33.3%
#3
150
800
650
650 / 2100 = 30.9%
2100 — Total
1200 (available) — 300 (Sum of CIR as shown in table) = 900 (capacity available for nonguaranteed traffic)
With the following values known, the calculations can be used:

Capacity available for non-guaranteed traffic
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
175

Correct percentages to apply to each of the services relative to the capacity left over
for non-guaranteed traffic
ONT


Calculation
Expected Upstream Rate
#1
50 + (900 x 0.357)
371.3 Mbps
#2
100 + (900 x 0.333)
399.7 Mbps
#3
150 + (900 x 0.309)
428.1 Mbps
Traffic moving through the E7 and downstream onto the PON is prioritized and
scheduled according to the 8 Cos configuration in the Ethernet switch and then handed
to the GPON OLT at an aggregate rate of 2.5 Gbps. In the OLT GPON MAC, the peak
rate for the service is enforced (shaped) prior to sending the traffic down the PON to the
ONTs. Upstream and downstream, the P-bits are mapped into one of the 4 GPON CoS
global configuration.
For any GPON service through the E7, the downstream P-bit must be set on all frames
for a given ONT service (either upstream of the E7 or at ingress into the E7 using a
policy map) to match the P-bit that is provisioned by the user in the service when it is
added to the ONT.
The provisionable limits for each bandwidth rate are as follows:

The minimum metered rate is 64 Kbps.

The maximum metered rate is 1 Gbps.

Rates can be selected in 64 Kbps increments up to 2 Mbps.

Rates can be selected in 1 Mbps above 2 Mbps.

Setting the metered rate to 0 Kbps disables the meter.
Note: 700GX ONTs can rate limit traffic to a maximum rate of 400Mbps. Setting the
rate limit for values higher than 400Mbps will disable the rate limiter.
Parameters
You can provision the following parameters for Ethernet bandwidth profiles:
Parameter
Description
Valid Options
Name*
Descriptive name for the bandwidth profile.
Up to 31 characters
Committed Rate
for Upstream
Specifies the committed minimum rate the ONT allows traffic to flow
upstream. Where rates may be specified as follows:

In 64 kbps increments up to 2 Mbps
0-2048 Kbps,
0-1000 Mbps,
1 Gbps

In 1 Mbps increments between 2 Mbps to 1000 Mbps
kbps in 64k increments

0 kbps disables the meter
Use "m" suffix for Mb/s or "g" for Gb/s in whole number increments.
Note: 700GX ONTs can rate limit traffic to a maximum rate of 400
Mbps. Setting the rate limit for values higher than 400 Mbps will
disable the rate limiter.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
176
Parameter
Peak Rate for
Upstream
Description
Specifies the un-guaranteed maximum rate for upstream traffic.
Where rates may be specified as follows:
Valid Options

In 64 kbps increments up to 2 Mbps
0-2048 Kbps,
0-1000 Mbps,
1 Gbps

In 1 Mbps increments between 2 Mbps to 1000 Mbps
kbps in 64k increments

0 kbps disables the meter
Use "m" suffix for Mbps or "g" for Gbps in whole number increments.
Note: 700GX ONTs can rate limit traffic to a maximum rate of 400
Mbps. Setting the rate limit for values higher than 400 Mbps
disables the rate limiter.
Peak Rate for
Downstream
Specifies the un-guaranteed maximum rate for downstream
traffic.Where rates may be specified as follows:

In 64 kbps increments up to 2 Mbps
0-2048 Kbps,
0-1000 Mbps,
1 Gbps

In 1 Mbps increments between 2 Mbps to 1000 Mbps
kbps in 64k increments

0 kbps disables the meter
Use "m" suffix for Mbps or "g" for Gbps in whole number increments.
Note: 700GX ONTs can rate limit traffic to a maximum rate of 400
Mbps. Setting the rate limit for values higher than 400 Mbps
disables the rate limiter.
Downstream Peak
Burst Size
Upstream
Committed Burst
Size
Upstream Peak
Burst Size
Specifies the un-guaranteed maximum bandwidth for downstream
peak burst size.

Use "k" suffix for Kbytes (4 to 16000 kbytes)

Use "m" suffix for Mbytes (0 to 16 mbytes)

Use whole number increments
Specifies the minimum committed bandwidth for upstream peak
burst size.

Use "k" suffix for Kbytes (4 to 16000 kbytes)

Use "m" suffix for Mbytes (0 to 16 mbytes)

Use whole number increments
Specifies the un-guaranteed maximum bandwidth for upstream
peak burst size.

Use "k" suffix for Kbytes (4 to 16000 kbytes)

Use "m" suffix for Mbytes (0 to 16 mbytes)

Use whole number increments
4-16000 Kbytes
4-16000 Kbytes
4-16000 Kbytes
*Required field
To create a bandwidth profile
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Service > Ethernet
Bandwidth.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > Ethernet Bandwidth > Profiles.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
177
2. On the menu, click Create.
3. Reference the table above to configure the parameters.
4. Click Create.
5. Associate the bandwidth profile to a video or data service being created on an ONT
Ethernet port. See Configuring an ONT Port (on page 244).
For CLI:
create bw-profile <p-name> [upstream-cir|upstream-pir|downstreampir|upstream-cbs|upstream-pbs|downstream-pbs]
Creating a Multicast Profile
This topic describes how to create a multicast profile that enables provisioning of the IPTV
service limits that can be applied when adding an Ethernet service to an ONT port. A
multicast profile is defined by the parameters listed below and references two previously
defined profiles:

Multicast Address Map
Identifies the optional global allowable multicast IP ranges.
See Creating a Multicast Address Map and Ranges (on page 181).

Multicast VLAN Registration (MVR) Profile
Identifies the optional MVR address ranges associated with specified multicast VLANs.
See Creating a MVR profile and MVR VLAN Addresse (on page 178)s.
Parameters
You can provision the following parameters for multicast profiles:
Parameter
Description
Valid Options
Name*
Name of the multicast profile.
32 character string
Max Streams*
Maximum number of multicast streams allowed at the subscriber port.
1-128
This value should include the boot channels, the programming guide,
and any other channels that may be learned, in addition to the number
of STBs on the port.
Multicast Maps
Identifies the map of optional global multicast IP addresses that a
subscriber service can join when this multicast profile is used. The
multicast map is an optional parameter of the multicast profile. With no
multicast address map identified, multicast group destination addresses
are unconstrained.
Any established multicast
map
MVR Profile
Identifies the optional MVR profile to be used by this multicast profile.
Any established MVR profile
Note: An MVR profile cannot be paired with more than one multicast
map.
General Query
Interval
The value in seconds that matches the upstream router's general query
interval.
10-3600
240 ‡
In the absence of a channel join, the ONT keeps the channel active for
the query interval before cutting it off. The assumption is the router
sends a general query every interval which causes the set-top box to
join the channel which also keeps the channel alive.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
178
Parameter
Convert to Unicast
Description
Whether to convert multicast packets to unicast before sending them
out the subscriber Ethernet port.
Valid Options
selected=enabled
unselected=disabled
The Convert to Unicast parameter should ONLY be enabled if switches
are deployed on the subscriber side that cannot manage heavy
multicast traffic.

Note: Only the Calix GX ONTs support this feature.
* Required
‡ Default
To create a multicast profile
1. If you have not already done so, create an MVR Profile and Multicast Address Map, if
necessary.
2. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Service > Multicast >
Multicast.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > Multicast > Multicast > Profiles.
3. In the menu, click Create to open the Create Multicast Profile dialog box.
4. Reference the table above to configure the parameters.
5. Click Create.
6. Associate the multicast profile when creating video service on an ONT Ethernet port.
For CLI:

create mcast-profile <p-name> [name|max-strms|query-interval|convertmcast|mcast-map|mvr-profile]

delete mcast-profile <p-name>

set mcast-profile <p-name> [max-strms|query-interval|convert-mcast]

show mcast-profile [p-name]
Creating an MVR Profile and MVR VLAN Addresses
The Multicast VLAN Registration (MVR) feature isolates subscriber video traffic from the
network Multicast VLAN. This is accomplished by using an MVR profile that enables the
distribution of Multicast traffic on a dedicated Multicast VLAN across disparate access
networks, while allowing subscribers who are on different VLANs to join and leave the
multicast groups carried in the Multicast VLAN.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
179
This topic describes how to create an MVR profile and MVR VLAN address range that is
assigned to the MVR profile. The MVR profile is referenced by a multicast profile that is
applied when adding an Ethernet service to an ONT port. See Creating a Multicast Profile (on
page 177).
Typical applications include the following:



Distribution of multicast VLAN and merging multicast traffic into subscribers untagged
“single service” associated with a residential gateway
Distribution of multicast VLAN and converting to a common “Video VLAN” preconfigured on all STBs
Distribution of multiple multicast VLANs (for example, high definition IPTV, standard
definition IPTV, and digital audio) and merge into a single subscriber service
MVR works in conjunction with IGMP where subscribers join and leave multicast groups via
IGMP. However, both the IGMP messages and multicast content are mapped from the
subscriber’s service into the isolated network side multicast VLAN. The E7 GPON ONT
supports the ability to map the subscriber’s IGMP and multicast traffic into multiple network
multicast VLANs.
Note: Calix recommends that an MVR profile be used for all multicast IPTV applications to
move the multicast traffic out of the "video" VLAN, where the video VLAN is assumed to
have all of the middleware traffic, STB DHCP traffic, and so on. Typically, the video VLAN
will be more susceptible to accidental or malicious traffic, whereas, MVR pulls the multicast
traffic out, keeping the VLAN exclusively for IGMP signaling and multicast streams.
Configuration guidelines





For MVR configuration on an ONT Ethernet port, create a minimum of two VLANs:

One VLAN for Unicast traffic with no IGMP Snooping where it correlates to the
matched traffic rule and associated service-tag action when provisioning the service
on the ONT Ethernet port.

One VLAN for Multicast traffic with IGMP Snooping enabled where it correlates to
the MVR VLAN profile definition that is associated to the Multicast Profile used
when provisioning the service on the ONT Ethernet port.

Multicast addresses on an E7 PON must be unique across all IGMP-enabled VLANs
on the PON, including MVR VLANs in up to 4 MVR profiles. For example,
multicast address w.x.y.z cannot exist in both VLAN-A and VLAN-B on the same
PON, where IGMP snooping/proxy is enabled on VLAN-A and VLAN-B.
E7 GPON supports up to 4 MVR profiles.
Each MVR profile can contain up to 4 MVR VLANs.
Each MVR VLAN can have up to 4 multicast IP ranges.
One MVR VLAN per MVR profile can have no IP range specified so that all IGMP and
multicast traffic not matching any other MVR VLAN with defined IP address ranges will
be mapped to this VLAN with no assigned IP range.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
180






A VLAN can appear in only one MVR profile.
An MVR VLAN cannot also be used as an Ethernet service VLAN.
The address ranges must be distinct from each other, not overlapping.
The full range of Multicast addresses:

Start 224.0.0.1

Stop is 239.255.255.255
An MVR profile can be paired with only one multicast map.
Multicast video traffic (broadcast content) and unicast video traffic (STB DHCP activity,
VOD, etc.) must arrive at the E7 on separate VLANs.
Before starting
Before you start the procedure to create a MVR profile and include an MVR VLAN address
range, the VLAN must exist on the E7.
Parameters
You can provision the following parameters for an MVR profile and address ranges:
Parameter
Description
Valid Options
Name*
Name of the MVR profile.
32 character string
MVR VLAN ID*
Index value designating the VLAN to be assigned address
ranges.
any existing VLAN
Address Range#
Start*
First address in the MVR VLAN range.
IP address in "dotted quad" format:
"192.168.1.100".
Address Range#
End*
Last address in the MVR VLAN range.
IP address in "dotted quad" format:
"192.168.1.100".
*Required fields
To create an MVR profile and MVR VLAN addresses
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Service > Multicast >
MVR.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > Multicast > MVR > Profiles.
2. In the menu, click Create to open the Create MVR Profile dialog box.
3. In the Name box, enter a descriptive name for the profile, and then click Create.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
181
4. In the list of existing MVR profiles, double-click the profile name to select it.
5. In the menu, click Create to open the Create MVR VLAN dialog box.
6. Reference the table above to configure the parameters.
7. Click Create to add the MVR VLAN to the MVR profile.
8. Associate the MVR profile when creating a multicast profile.
For CLI:


create mvr-profile <p-name>
add vlan <vlan-id> to-mvr-profile <p-name> [mcast-range-1|mcast-range2|mcast-range-3|mcast-range-4]

delete mvr-profile <p-name>

remove vlan <vlan-id> from-mvr-profile <p-name>

set mvr-profile <p-name> name <new-name>


set mvr-profile <p-name> vlan <vlan-id> [mcast-range-1|mcast-range2|mcast-range-3|mcast-range-4]
show mvr-profile [p-name]
Creating a Multicast Address Map and Ranges
This topic describes how to create a multicast address map and IP address ranges that are
assigned to the map. The map is referenced by a multicast profile that is applied when adding
an Ethernet service to an ONT port. See Creating a Multicast Profile (on page 177).
Configuration guidelines




The multicast address map is an optional parameter of the multicast profile.
With no multicast address map identified, multicast group destination addresses are
unconstrained.
Each multicast address map can contain up to eight distinct multicast IP address ranges,
not overlapping.
The multicast address map is not supported for Residential Gateway (RG) based video
services. However, it is supported for Full Bridge (FB) based video services.
Parameters
You can provision the following parameters for multicast maps and ranges:
Parameter
Description
Valid Options
Name*
Name of the multicast map.
32 character string
ID*
Index value designating the multicast range in the
multicast map. You can leave the value, or select another
(1-8).
1-8
Start IP Address*
First address in the multicast range.
Any multicast address, lower than the end
IP address (224.0.0.0 - 239.255.255.255)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
182
Parameter
Description
End IP Address*
Last address in the multicast range.
Valid Options
Any multicast address, higher than the end
IP address (224.0.0.0 - 239.255.255.255)
*Required fields
To create a multicast address map and range
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E3-48C/E5-48/E7/ONT > Profile >
Service > Multicast > Multicast Maps.
Locally on the E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > Multicast > Multicast Maps >
Profiles.
2. In the menu, click Create to open the Create Multicast Maps dialog box.
3. In the Name box, enter a descriptive name for the map, and then click Create.
4. In the list of existing multicast maps, click the map name to select it.
5. In the menu, click Create to open the Create Multicast Address Range dialog box.
6. Reference the table above to configure the parameters.
7. Click Create to add the multicast address range to the multicast map.
8. Repeat Steps 5 through 7 to include another multicast range in the multicast map.
9. Associate the multicast map when creating a multicast profile.
For CLI:

create mcast-map <m-name>

add range to-mcast-map <m-name> mcast <m-range>

delete mcast-map <index>

remove range <index> from-mcast-map <m-name>

set mcast-map <old-name> name <new-name>

set mcast-map <m-name> range <index> mcast <m-range>

show mcast-map [m-name]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
183
Creating an IGMP Profile
This topic describes how to create a profile for VLAN association that sets configuration
attributes of the Internet Group Management Protocol (IGMP) snoop used to establish
membership in a multicast video services group. Multicast delivers IP packets to a select
group of hosts on the network. The IGMP enables the E7 to manage the flow of multicast
IP traffic, selectively forwarding and blocking flows to ports based on multicast group client
join and leave requests.
The E7 can passively snoop on the following IGMP packets transferred between IP
multicast routers, switches, and IP multicast hosts to learn the IP multicast group
membership and configure multicasting accordingly:



Query
Report
Leave (IGMP version 2)
The E7 forwards multicast traffic destined for multicast groups (discovered through IGMP
snooping) to ports that are members of that group. The E7 discards multicast traffic destined
for multicast groups that it does not recognize. IGMP snooping generates no additional
network traffic, allowing you to significantly reduce multicast traffic passing through your
device.
Note: If IGMP snoop is disabled, the IGMP traffic is forwarded through, and multicast
traffic is forwarded everywhere on the VLAN.
Configuration guidelines




The IGMP snooping is enabled on a per-VLAN basis.
All nodes in an ERPS ring must have the same IGMP Snooping provisioning on the
VLAN for video traffic to flow--either all enabled or all disabled.
For ERPS ring configurations:

For E7 in an ERPS ring with no directly attached routers, set the Router Learning
Mode to Static and have no statically defined router ports set. This ensures that only
the ring is “learned” or allowed to be the multicast router source so that subtended
RSTP rings that might incorrectly flood a general query around the RSTP rings
(typically during a topology change) are never learned as the querying router.

For E7 in an ERPS ring with a direct connection to the multicast router, configure
statically-defined router ports to identify the uplink. See Creating VLAN Members.
Multicast traffic will not be allowed to traverse ports blocked by the ring protection
protocol.
Note: Calix recommends that the subtending devices to be configured for IGMP proxy
to minimize the load on the multicast router and the E7 transport topology.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
184
Note: By default IGMP snooping is disabled on a VLAN. IGMP snooping should only
be enabled for VLANs that carry multicast content. Typically one, but sometimes a few
VLANs are utilized to distribute multicast content within the access network.










The video VLAN must be the same on the network side (IGMP router side) and access
side (IGMP host side).
The E7 can perform the following tag actions on a VLAN that has IGMP enabled:

Add-tag action to untagged Ethernet frames.

Change-tag action to change the VLAN ID at network administrative boundaries.
IGMP snooping is only enabled on the outer VLAN ID.
If a connected C7 is using IGMP proxy, then snooping must be enabled on the video
VLAN. Otherwise, snooping should be disabled (set to N).
With Router Learning Mode configured for ‘static-only’, IGMP Proxy will not allow a
static multicast router (‘mrouter’) interface to be a multicast destination. If the interface
could become a multicast destination in the event of a network topology change, the
interface should not be configured as a mrouter interface.
The network switch providing the video must have IGMP enabled.
For an RSTP network, Calix recommends setting the following parameters as shown:

The VLAN IGMP Mode = snoop-suppress or proxy

The IGMP profile Router Learning Mode = static-dynamic

The IGMP profile Router Solicit On Topology Change = Y (enabled)

The interface is NOT designated as a static router port through the VLAN
membership.
For Cross-Card LAG interfaces, set the following parameters as shown to achieve the
best re-convergence time:

The VLAN IGMP Mode = proxy

The Router Learning Mode = static

The Router Solicit On Topology Change = N (disabled)

The LAG interface is designated as a static router port through the VLAN
membership.
IGMP snooping occurs internally to the E7 and Calix ONT and is not a networking
protocol.
The following set of counters are supported on a per-VLAN basis:

V2 joins sent and received

Leave messages sent and received

Group-specific queries sent and received

Invalid IGMP messages received

Query solicits and general queries sent and received
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
185
IGMP profile parameters
You can provision the following parameters for an IGMP profile:
Parameter
Name*
Description
Valid Options
A descriptive name to identify the profile.
31-character text string
IP address to use when in proxy mode.
This address is used as the source address in IGMP messages sent
upstream. It should be a valid IPv4 address in the same subnet as
the upstream router. This address can be the same IP as the
Management VLAN for the node.
IP address in "dotted quad"
format. For example:
"192.168.1.100". Alternately,
"none" can be used to reset the
value to "0.0.0.0"
Immediate Leave
Whether a multicast stream is dropped as soon as a Leave is
received. May be overridden per interface.
Y (enable)
N (disable) ‡
Robustness
Number of IGMP group-specific queries sent per query interval
when proxy is configured.
1-10
1‡
Last Member Query
Count
Number of group-specific queries sent when a Leave is received.
1-8
2‡
Last Member Query
Interval
Time to wait in milliseconds for a response to a group-specific
query.
100-5000
1000 ‡
Method used for learning the location of upstream routers.
static-and-dynamic ‡
static-only
Proxy IP Address*
Router Learning
Mode
Router Solicit On
Topology Change
Query Response
Interval
Query Interval
Note: With Router Learning Mode configured for ‘static-only,’ IGMP
Proxy will not allow a static multicast router (‘mrouter’) interface to
be a multicast destination.
Whether to send a Query Solicitation when a topology change
occurs. When the topology changes in a network, such as when a
link is added or removed from an RSTP domain, a Query
Solicitation message is generated on all ports belonging to the
VLAN for which IGMP snooping is enabled. If the upstream
multicast Querier in the network supports Query Solicitation and has
the function enabled, it will respond by sending a General Query
out, causing devices to re-adjust to a new multicast source port
location, if necessary.
Y (enable) ‡
N (disable)
Time to wait for responses to general queries, in seconds.
1-20
10 ‡
Note: Setting the value lower than 10 could result in a high traffic
rate.
Time interval in seconds between general queries.
Note: Calix recommends setting (or leaving) the IGMP Query
Interval value for the video VLAN to 60 seconds (default).
10-1000
60 ‡
A 60-second query interval allows a good balance between
maintaining bandwidth efficiency (channel pruning) versus limiting
potential IGMP control message processing overflow by the CPU,
and it matches the typical default IGMP Query setting on most
routers.
Startup Query
Interval
Time interval between general queries during startup in seconds.
2-250
15 ‡
Startup Query Count
Time to wait for responses to general queries during startup.
1-10
2‡
Host Purge Time
Purge time in seconds for host ports.
130-3600
260 ‡
Router Port Purge
Time
Purge time in seconds for router ports.
60-600
260 ‡
*Required field
‡Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
186
To create an IGMP profile
1. On the Navigation Tree, click E7.
2. Click Profiles > IGMP > Create.
3. Reference the table above to configure the parameters.
4. Click Create.
5. Associate the IGMP profile to a specific VLAN, if the VLAN IGMP mode is set to
Proxy.
For CLI:
create igmp-profile <p-name> [name|immediate-leave|robustness-retries|lastmemb-query-intrvl|router-learning-mode|router-solicit-top-chg|queryinterval|query-resp-interval|startup-query-interval|startup-querycount|proxy-ip|host-port-purge-time|router_port-purge-time]
Creating a PPPoE Profile
This topic shows you how to create a PPPoE profile that is referenced by the HSI service
VLAN that is configured for PPPoE operation.
See Configuring PPPoE Operation for a Data Service (on page 283) for configuration guidelines
and instructions.
Configuration guidelines:





The E7 uplink toward the router or PPPoE Server must be on an interface set to the
mode of "Trunk."
At the aggregating Trunk interface northbound of the E7, the PPPoE traffic must adhere
to a specific VLAN membership on the Trunk interface.
The PPPoE profile is applied to a service VLAN where simultaneous operation of
DHCP Snooping and PPPoE are not supported. Both PPPoE and DHCP are
mechanisms for a subscriber host to acquire an IP address with which to communicate.
If a service is using PPP, then it is not using DHCP, and vice versa.
Setting a VLAN PPPoE profile to “none” passes through all PPPoE traffic,
transparently. If a PPPoE profile is used with PPPoE snoop, a list of all the active
sessions and statistics are available, and the PPPoE stack is enabled, which passes
through PPPoE traffic transparently as long as the Clients/BRAS are operating normally
(illegal packets will be dropped).
Each GPON subscriber can only have up to 1 Ethernet service with PPPoE enabled.
Parameters
You can provision the following parameters for PPPoE profiles:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
187
Parameter
Description
Valid Options
Name*
Descriptive name for the PPPoE profile.
text string
Mode
The mode to use for the operation:
auto ‡, relay, snoop

Auto – Automatically detects the mode between
native PPPoE clients and PPPoA clients, and
runs relay (PPPoE IA) for PPPoE clients, and
runs IWF for PPPoA clients.

Relay – (Works with PPPoE clients only.) Inserts
circuit-id and remote-id on the upstream
direction, and then removes the circuit-id and
remote-id on the downstream direction.

Snoop – (Works with PPPoE clients only.)
Snoops PPPoE packets without modifying the
packets (i.e. does not insert/remove circuit-id
and remote-id).
Stale Timeout(s)
Inactivity time-out for session teardown.
10-300
300 ‡
Discovery Timeout (s)
Discovery timeout (seconds).
1-30
3‡
Allowed BNG MAC 1
Allowed (trusted) Broadband Network Gateway
(BNG defined in TR-101) MAC address or OUI.
Alternately, the keyword "none" indicates that all
BNG MACs are allowed.
six hexadecimal digits in the range 0-FF,
optionally separated by colons
none ‡
Allowed BNG MAC 2
Allowed (trusted) Broadband Network Gateway
(BNG defined in TR-101) MAC address or OUI.
Alternately, the keyword "none" indicates that all
BNG MACs are allowed.
six hexadecimal digits in the range 0-FF,
optionally separated by colons
none ‡
Allowed BNG MAC 3
Allowed (trusted) Broadband Network Gateway
(BNG defined in TR-101) MAC address or OUI.
Alternately, the keyword "none" indicates that all
BNG MACs are allowed.
six hexadecimal digits in the range 0-FF,
optionally separated by colons
none ‡
Allowed BNG MAC 4
Allowed (trusted) Broadband Network Gateway
(BNG defined in TR-101) MAC address or OUI.
Alternately, the keyword "none" indicates that all
BNG MACs are allowed.
six hexadecimal digits in the range 0-FF,
optionally separated by colons
none ‡
* Required
‡ Default
To create a PPPoE profile
1. On the Navigation Tree, click E7/E5-48/E3-48C.
2. Click Profiles > PPPOE.
3. In the menu, click Create.
4. Reference the table above to configure the parameters.
5. Click Create.
For CLI:
create pppoe-profile <name> [mode|stale-timeout|disctimeout|allowed-bng-1|allowed-bng-2|allowed-bng-3|allowed-bng-4]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
188
Creating an Ethernet Security Profile
This topic shows you how to create an Ethernet security profile that is applied to ONT
Ethernet ports to enable and/or specify security attributes of the ONT Ethernet port.
Note: The E7 implementation of security profiles applies to non-TLAN services only. For
TLAN services, the L2CP Filter parameter must be set to all-tunnel.
Layer 2 Control Protocol (L2CP) handling
The E7 supports provisionable Layer 2 Control Protocol (L2CP) handling (tunnel, discard)
on GPON ONT Ethernet interfaces and VLANs on the interface. The control protocol
refers to a grouping of protocols, for example RSTP, LACP, Pause, GARP, and so forth.
The L2CP filtering is an MEF-driven requirement for business services that use BPDU
tunneling. The L2CP feature supports per subscriber port configuration options to pass or
discard the following L2CP protocols:



Bridge Block of protocol frames with destination MAC addresses 0x01:80:c2:00:00:00
through 0x01:80:c2:00:00:0f.
GARP Block of protocol frames with destination MAC addresses 0x01:80:c2:00:00:20
through 0x01:80:c2:00:00:2f.
All LANs Bridge Management Group protocol frames with destination MAC address
0x01:80:c2:00:00:10.
Parameters
You can provision the following parameters for Ethernet security profiles:
Parameter
Description
Valid Options
Name*
Name of the security profile.
up to 32 character string
Source MAC Limit
Number of unique MAC addresses allowed on a subscriber port.
0 ‡-255
Maximum age for source MAC addresses, in seconds.
60-86400
300 ‡
Source MAC Age
Note: The ARP age timer in the router must be set to a value less
than or equal to the value set for the MAC age timer.
DHCP Lease Limit
Specifies the maximum number of DHCP leases allowed on the ONT
Ethernet port (aggregate for all services). Only VLANs with DHCP
Snooping on the port are subject to the DHCP lease limit. In the
VDSL2 and GPON subsystems, DHCP leases cannot be learned
without also applying a limit to the number of learned leases on the
port. Each Ethernet port has an associated Port Security Profile that
can limit DHCP leases in a range of 1-16. The E7 does not support
infinite lease times on DHCP snooping.
1-16
8‡
Note: Does not apply to Residential Gateway (RG) interfaces.
Upstream
Broadcast/Multicast
Limit (Kb/sec)
Specifies the maximum rate of Layer 2 broadcast traffic per second
allowed on the ONT Ethernet port.
0 – 10240 Kbps (10 Mbps)
24 ‡
Note: Does not apply to Residential Gateway (RG) interfaces.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
189
Parameter
L2CP Filter
Description
Layer 2 Control Protocol filter sets whether to pass or discard the
L2CP protocol frames. Besides selecting from the system default
filters (all-discard or all-tunnel), you can create additional filters to
specify which L2CP ranges to discard or tunnel.
Valid Options
all-discard ‡
all-tunnel, or any previouslycreated filter
Note: For TLAN services, this parameter must be set to all-tunnel.
Does not apply to Residential Gateway (RG) interfaces.
DOS Attack Detection
Whether to enable or disable Denial Of Service (DOS) attack
detection against PPPoE control flows. DOS attack is implemented
for PPPoE discovery phase packets only, where it meters the arrival
of PPPoE control packets from a particular subscriber, and uses that
rate to detect an arrival rate being above a threshold for a time. When
the threshold is detected, the condition is considered "yellow". When
the threshold continues for a specified time, the condition is
considered "red" and a DOS attack condition exists. Counters are
kept for packets arriving in the "yellow" and "red" conditions.
selected = enabled ‡
unselected = disabled
Threshold rates:

Allow IPv6
Yellow - 10 pkts/second

Red - 10 pkts/second for 5 consecutive seconds

When the Red condition occurs, the interface is disabled for 300
seconds.
Whether to enable or disable IPv6 traffic. IPv6 traffic flows by default.
If the setting in this profile is changed to "Disabled", IPv6 unicast,
multicast and broadcast traffic ingressing the interface is blocked.
selected = enabled ‡
unselected = disabled
*Required field
‡ Default
To create a Ethernet security profile
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Security > Ethernet.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Security > Ethernet > Profiles.
2. In the menu, click Create to open the Create Security Profile dialog box.
3. Reference the table above to configure the parameters.
4. Click Create.
5. Apply the Ethernet Security Profile to an ONT Ethernet port.
For CLI



create eth-sec-profile <p-name>
create l2cp-filter <name> [range-1-action|range-2-action|range-3action]
delete eth-sec-profile
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
190

set eth-sec-profile <p-name>

set l2cp-filter <name> [range-1-action|range-2-action|range-3-action]

show eth-sec-profile [<p-name>]
Creating an L2CP Filter
This topic shows you how to create an Layer 2 Control Protocol (L2CP) filter that specifies
which L2CP ranges to discard or tunnel L2CP protocol frames. The E7 already has two
system default filters that either discard (all-discard) or pass (all-tunnel) all L2CP protocol
frames for all ranges.
The L2CP filter is referenced from the Ethernet security profile that is applied to ONT
Ethernet ports to enable and/or specify security attributes of the ONT Ethernet port.
Note: The E7 implementation of security profiles applies to non-TLAN services only.
Layer 2 Control Protocol (L2CP) handling
The E7 supports provisionable Layer 2 Control Protocol (L2CP) handling (tunnel, discard)
on GPON ONT Ethernet interfaces and VLANs on the interface. The control protocol
refers to a grouping of protocols, for example RSTP, LACP, Pause, GARP, and so forth.
The L2CP filtering is an MEF-driven requirement for business services that use BPDU
tunneling. The L2CP feature supports per subscriber port configuration options to pass or
discard the following L2CP protocols:



BPDU Range - indicates L2CP protocol frames with destination MAC addresses
0x01:80:c2:00:00:00 through 0x01:80:c2:00:00:0f.
GARP Range - indicates L2CP protocol frames with destination MAC addresses
0x01:80:c2:00:00:20 through 0x01:80:c2:00:00:2f.
All-LANs Range - (Bridge Management Group) indicates L2CP protocol frames with
the destination MAC address 0x01:80:c2:00:00:10.
Parameters
You can provision the following parameters for L2CP Filters:
Parameter
Description
Valid Options
Name*
Name of the L2CP filter.
up to 32 character string
BPDU
Specifies the action for layer-2 control protocol packets in the BPDU
range.
discard ‡
tunnel
GARP
Specifies the action for layer-2 control protocol packets in the GARP
range.
discard ‡
tunnel
ALL-LANS
Specifies the action for layer-2 control protocol packets in the ALLLANS range.
discard ‡
tunnel
*Required field
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
191
To create an L2CP filter
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E3-48C/E5-48/E7/ONT > Profile >
Security > L2CP.
Locally on the E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Security > L2CP > Filters.
2. In the menu, click Create to open the Create L2CP Filter dialog box.
3. Reference the table above to configure the parameters.
4. Click Create.
For CLI
create l2cp-filter <name> [range-1-action|range-2-action|range-3-action]
Creating an ONT Template
Using CMS R12.1 or later, you can create an ONT template that defines all of the key
management aspects of a Home Gateway (HGW) ONT as well as the logical assignments of
physical GE ports for the initial setup. Once the template is created, you can apply it to the
appropriate ONT. The template can also be shared between AE and GPON ONTs.
There is a system-default template that applies to ONTs implicitly until you specifically
change it on an ONT. Once a template is applied to an ONT, any further changes to that
template are not reflected on the ONT. Any new ONTs provisioned with the modified
template will use the new settings. You can always override the parameter values at the ONT
level. The ONT template is a CMS object, only.
If you did not use the ONT template for defining a HGW ONT, you would access the
parameters in various objects:
ONT Object
RG Interface
ONT Template Parameters

Management Mode

Management Profile

WAN Protocol (native mode, P-series only)

Configuration-File Instance (external mode)

RG DSCP/IP Prec
FB Interface (P-series only)

FB DSCP/IP Prec

Security Profile
ONT GE Port

Security Profile

GE/FE Port assignments to HGW Interfaces

In-Band Service
Gateway Service Form
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
192
Note: Both RG and FB interfaces support a DSCP/IP-precedence to P-bit mapping on a
per-VLAN basis. The LAN side clients are responsible for setting DSCP/IP-precedence.
Parameters
You can provision the following parameters for ONT templates:
Parameter
Description
Valid Options
ID
Index of the template
Name
Name of the multicast profile.
32 character string
Management Mode
Management Mode of RG port.
native ‡, external

Native mode (P-series only) allows all of the RG provisioning,
through adding services, to be done in CMS or E7 interfaces. Note:
T-Series ONTs do not support Native Mode as an option for the
Management Mode.

External mode allows the RG provisioning to be done through an
ACS or RG Configuration File. The services are still added through
CMS or E7 interfaces, and must map to the configuration done
externally.
1-20
Management Profile
Name of RG management profile for TR-069 that allows you to
configure common ACS-related parameters, and how the TR-069
management channel is setup (in-band or out-of-band).
Any previously-created
profile, or the system-default
profile
In-Band Service
When the the TR-069 client is configured to for Management mode =
In-band in the RG Management Profile, the client runs on an existing
RG WAN interface. Typically, the path to the ACS server utilizes an
existing RG service such as Gateway Service: 1 (for example, a HSI
service).
none ‡, Gateway Service: 14
WAN Protocol
(P-series) WAN Protocol for RG Interface in Native Management Mode.
WAN protocol is only configurable on the RG WAN interface associated
with the Ethernet service Data1. RG WAN interface for the Ethernet
services Data2, Data3, and Data4 are DHCP only.
dhcp ‡, static, pppoe
RG DSCP/IP Prec

static allows you to enter static-ip, static-ip-mask, static-ip-gateway.

pppoe allows you to enter pppoe-user, and pppoe password.
Name of DSCP or IP-precedence to P-bit map to use on ingress at the
Residential Gateway interface. There are system-default profiles named
"access" that you can use or you can create custom profiles and assign
them to the interface.
DscpMap: access ‡,
IpPrecMap: access, any
previously-created profile
Both RG and FB interfaces support a DSP/IP precedence to P-bit
mapping on per-VLAN basis.
FB DSCP/IP Prec
(P-series only) Name of DSCP or IP-precedence to P-bit map to use on
ingress at the Full Bridge interface. There are system-default profiles
named "access" that you can use or you can create custom profiles and
assign them to the interface.
DscpMap: access ‡,
IpPrecMap: access, any
previously-created profile
Both RG and FB interfaces support a DSP/IP precedence to P-bit
mapping on per-VLAN basis.
Security Profile
Name of Security Profile to apply to the interface that can limit DHCP
leases, limit the rate of Layer 2 broadcast traffic allowed on the
interface, and indicate whether to pass the L2CP protocol frames.
system-default ‡, or any
existing security profile
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
193
Parameter
GE 1-8
Description
Assign the GE port as a member of either the RG or FB (P-series only)
interface group, or not a member of either, allowing it to operate as a
normal L2 classic port (Half-Bridge mode).

Valid Options
none ‡, RG-1, FB-1
Residential Gateway (RG) Mode
The RG services are named as Gateway Services, where only four
services are supported with only one of them can have a multicast
profile assignment. The ONT RG interface supports up to 4 services.

Full-Bridge (FB) Mode (P-series only)
With Full-Bridge mode, traffic can pass between LAN ports within the
same bridge.
Support of Full-Bridge is assumed to be for video multicast services only
to enable Whole-Home DVR support, allowing communication between
set-top boxes. A single multicast VLAN can be associated to the FullBridge group. Applications that require Full-Bridge support of IPTV
enabled devices along with media-clients with a single IP Host
supporting data and unicast applications requires an auxiliary switch be
installed behind the LAN port and continued support of Half-Bridge. The
ONT Full-Bridge interface only supports 1 service.

Half-Bridge (HB or Classic) Mode
In Half-Bridge mode, the port operates as a normal L2 classic port. This
operation allows traffic to only pass between the WAN and LAN ports
and restricts traffic from passing between LAN ports within the same
bridge.
FE 1-2

When an 836 RSG ONT is created on the E7, all ONT Ethernet
ports are assigned as members of the RG port. Ports can be
removed from the RG group, and possibly added to the FB interface
group.

When a 700GE or T-series ONT is created on the E7, the ONT
Ethernet ports are not a member of a HGW interface group, and
can be added to an interface group. The 700GE resets whenever it
transitions into or out of RG mode. For example, when the first ONT
Ethernet port is added to the RG group on a 700GE ONT, the ONT
resets. Similarly, when the last Ethernet port is removed from the
RG group, the ONT resets.
Assign the Fast Ethernet port as a member of an HGW interface group,
or not, allowing it to operate as a normal L2 classic port (Half-Bridge
mode).
none ‡, RG-1, FB-1
* Required
‡ Default
To create an ONT template
1. Access the profile page:

From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Templates > ONT.
2. In the menu bar, click Create to open a New ONT Template dialog.
3. Reference the table above to configure the parameters.
4. Click Create.
5. Apply the template to the Home Gateway ONT, when configuring the PON. See
Applying an ONT Template (on page 257).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
194
Creating an RG Configuration File
This topic describes how to create an RG configuration file for the E7 to download which
allows the deployment of a common provisioning and service model across all 700GE
ONTs, 836GE, or GigaCenter devices supporting Home Gateway (HGW). The file
download mechanism is via OMCI file transfer. See Retrieving and Applying a Configuration File
(on page 237).
For most HGW ONT deployments that involve data-only services, or access modes that
require a single VLAN service, the default RG configuration file that is created when the
HGW ONT becomes operational is sufficient. However, when any customization is required
that is not supported by the default profile (associated with RG Management Mode: Native),
it is necessary to use a customized RG configuration file.
Note: You can use a single RG configuration file for both 836GE and 700GE ONTs
operating in RG mode. However, you should use the 836GE to create the default file.
Note: The ONT must be reset to factory default values before downloading new
configuration files. This can be accomplished by either pressing and holding the reset button
for 20 seconds or using the EWI. Applying a new RG configuration file will reset the RG
configuration on the HGW. If a subscriber has modified items such as SSIDs via the EWI,
these changes will be lost when the new RG configuration file is applied.
Configuration Files for T-Series ONTs



T-series ONTs use an RG configuration file that requires an intake form be submitted to
Calix with the defined configuration parameters, such as LAN IP addresses, subnets, wifi
power, and DHCP lease times. This results in the creation of an approved RG
configuration file from Calix that is then transferred to a server local to the E7.
The T-series HGU ONTs always require an RG configuration file to set-up the routed
WAN interfaces.
See Completing Residential Gateway and SIP Configuration File Intake Forms.
Example requirements
A customized RG configuration file would be utilized to set up the gateway partition for the
following example requirements:





Multiple VLANs associated with the routed WAN interface
Special DNS configuration in the RG
Setup of PPPoE or static IPoE connections
Enabling of IPTV and other services on separate VLANs
Setup of GigaCenter L2 bridged video
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
195
RG configuration file attributes
The following attributes can be set in the RG configuration file:







WAN interface, including connection type and VID
Static routes
DNS Host Mapping entries
PPPoE or static IPoE connections setup
Wi-Fi Radio set-up
DHCP defaults set-up (IP address start, DHCP reservation enable). All WAN interfaces
on the ONT use the same Option #60 identifier specified in the RG Config File .xml. If
an Option #60 field is required, download an RG config file with this specified, even if
the ONT is in layer-2 mode for LAN / data services.
The T-Series supports four independent WAN VLANs (High-Speed Internet, IPTV,
VoIP, TR-069). The RG configuration file "NAT enabled" attribute controls which of
these VLANs are routable from the LAN. By default, only the HSI WAN is routable.
Static/Default routes assigned to other WAN's require NAT to be enabled before you
can access them from the LAN.
Note: Locally saved configurations (using Configuration Save) are specific to that HGW
device. These configurations include all of the default values for that device such as
Administer Username and Password, SSID and WPA/WPA2 key. These device-specific
attributes may not be applicable to other units at other locations.
Before starting
Before you start the procedure below, the ONT must have the operational software loaded
on the ONT as the ONT only has a manufacturing image on it when you remove the ONT
from the box. In order to accomplish this task, do one of the following:

Attach the ONT to the PON so that the operational software is automatically loaded on
the ONT.
or

Obtain the ONT image from the Calix Software Center and upload the software image
directly to the ONT using Smart Activate.
Note: Loading software via the iOS SmartActivate application is not supported.
To create an RG configuration file
1. Attach a PC to any of the RG LAN ports and allow the PC to obtain an IP address,
which will be in the 192.168.1.0/24 subnet, by default.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
196
2. Launch a web browser and navigate to the following address and login:
http://192.168.1.1
username / password (836GE and GigaCenter): support / support
username / password (700GE and T-series): admin / admin
3. Provision the necessary service elements of the RG, such as service WAN VLANs and
service static routes.
Note: For Microsoft Mediaroom deployments, you can use Option-121 on a DHCP
server to provide default routes for Microsoft Mediaroom unicast traffic. See Classless
Static Routes (Option 121) (on page 196).
4. Navigate to the Utilities > Configuration Save.
5. In the Version box, enter a version string value (for example 1.0.0.0) for the
configuration file.
Note: Do not enter a version string here if deploying the configuration file via an ACS.
6. Click Backup to backup the file to the PC.
Note: DO NOT open and save the configuration file in Microsoft Notepad or any other
editors that may manipulate the configuration file. Some editors may manipulate the
configuration file that you created without you realizing it, resulting in a file validation
error when loading the configuration file.
Classless Static Routes (Option 121)
Classic Static Routes (as defined by RFC 3442), allows the assignment of multiple routes
between a DHCP server and various clients. Per RFC 3442, this Dynamic Host
Configuration Protocol (DHCP) option is passed from the DHCP Server to the DHCP
Client to configure a list of static routes in the networks routing table. The network
destinations in these routes are classless - each routing table entry includes its own subnet
mask.
The classless route is assigned a destination descriptor and a gateway IP address, derived
from a combination of the destination IP address and its subnet mask.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
197
Customers needing to deploy the classless static routes option within their network must
insert a global declaration and a subnet declaration for use by their DHCP server.
The following declarations must be included within the DHCP server configuration file when
implementing classless static routing.
Example # 1
# Global Declaration
option classless-static-routes code 121 = array of integer 8;
# Subnet Declaration
option classless-static-routes 16,10,20,10,32,102,1;
Reading this simple subnet declaration from left to right, the classless static route is defined
as follows:
Subnet Mask: 16 bit
Subnet: 10.20.0.0
Gateway Address: 10.32.102.1
Example # 2
# Global Declaration
option classless-static-routes code 121 = array of integer 8;
# Subnet Declaration
option classless-static-routes
32,10,208,53,36,192,168,69,1,24,10,20,15,10,32,102,1;
Again, reading from left to right, this combined host route and subnet route in the same
declaration is defined as follows:
Host Route
Subnet Mask: 32 bit
Host: 10.208.53.36
Gateway: 192.168.69.1
Subnet Route
Subnet Mask: 24 bit
Subnet: 10.20.15.0
Gateway Address: 10.32.102.1
Option 121 Deployment Guidelines
Keep the following in mind when deploying Option 121 within your network:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
198



If a DHCP option 121 route conflicts with a route configured via XML configuration file
or ACS, the XML configuration or ACS provisioned route takes precedence. A
conflicting route is defined as the address / mask portion matching an existing route. If
the address / mask differs, then the option 121 route can be installed and normal route
precedence rules apply (longest match). Calix recommends managing and administrating
the routes for the RG in a single place, selecting one of the following for ease of
management:

DHCP server via option 121 (recommended method)

RG configuration file

ACS configuration
If the option 121 route is modified or additional routes are added on the DHCP server,
the RG DHCP client will pick up any changes on the next DHCP renewal. If you wish to
force an update, reboot the RG.
DHCP option 121 routes are viewable via the RG GUI on the service static routes page.
Creating an RG Management Profile
This topic describes how to create an RG management profile that is used to control the
behavior of the TR-069 client on RG-enabled ONTs. For example, without modifying the
applied external configuration file, you can create an RG management profile that specifies a
TR-98 management object with an associated parameter value that the Auto-Configuration
Server (ACS) sends to the ONT, either when the ONT comes online and checks in with the
ACS, or on a scheduled basis.
Alternatively, you can use the E7 system-default RG management profile.
Home Gateway operation with E7 and the 700GE ONTs and 836GE RSG supports TR069. This allows you to deploy a common management and service model for both xDSL
and fiber-based systems. The protocol provides a safe auto-configuration tool as well as
controlling CPE management functions. TR-069 addresses the vast number of CPE Internet
access devices such as modems, routers, gateways, set-top boxes, and VoIP-phones. The
technical standard was developed for automatic configuration of these devices with Auto
Configuration Servers (ACS).
Note: Similar to the configuration file management mode, the RG management profile can
only manipulate the RG components.
Calix Consumer Connect is an ACS that uses TR-069 standard protocol for remote
management of CPE devices including the 700GE ONTs and 836GE Residential Services
Gateway. All TR-069 compliant devices adhere to a well-defined data model that describes
common TR-98 management objects for the CPE. Using the TR-069 protocol, Consumer
Connect provides remote configuration, provisioning and device management.
In TR-069 protocol the CPE device is the connection initiator with the ACS and must be
configured to make contact with the ACS. The 836GE RSG can be configured to initiate the
connection in three ways:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
199



CMS System Settings (ACS Settings)
CLI Home Gateway command settings (config acs setup)
Web browser Home Gateway interface settings (Support / TR-069)
Once a connection between the 700GE ONT or 836GE RSG and the Consumer Connect
ACS is established, the CPE device is managed at two distinctly different levels:


Device level operations – a single ONT or RSG
Group level operations – a group of ONTs and RSGs
The E7 system supports a TR-069 client on the RG, independent of RG management mode
(native or external). This topic shows you how to create an RG management profile that
specifies any TR-069 based ACS (Auto-Configuration Servers) interface (either the Calix
Consumer Connect network or other 3rd party ACS client) that will be used by ONTs/RSGs
operating in External Mode. The E7 provides a default RG management profile. You can
either modify the system-default profile or create a new profile. For example, specifying the
Auto-Configuration Servers (ACS) address, username, and password.
The TR-069 client can be configured to run in the following management modes:


In-band runs on an existing RG WAN interface. Typically, the path to the ACS server
utilizes an existing RG service such as Gateway Service: 1 (for example, a HSI service).
Out-of-band runs on its own RG WAN interface. An independent VLAN outside of the
service VLANs is provisioned on both the RG and ONT to facilitate communication to
the ACS service.
Note: When using RG Management profiles, whether in-band or out-of-band, it is assumed
that a DHCP server exists and is accessed via ACS. This assumes that your network is
provisioned with a DHCP server and ACS.
Public versus private IP addressing
Whether you use public or private IP addresses on the ONT RG interfaces, a routable path
must exist between the WAN IP address of the provisioned WAN interface on the ONT and
the Consumer Connect server.
Parameters
You can provision the following parameters for the RG management profile:
Parameter
Description
Valid Options
Name*
Name of RG management profile.
numeric: 1-50
ACS URL*
IP address of Auto-Configuration Server (ACS).
text string (4)
Username*
The username the ONT uses to login to the ACS.
text string (31)
Password*
The password the ONT uses to login to the ACS.
0‡ - 8
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
200
Parameter
Description
Management Mode*
Management mode of the Residential Gateway. The TR-069 client can
be configured to run in the following management modes:

In-band runs on an existing RG WAN interface. Typically, the path
to the ACS server utilizes an existing RG service such as Gateway
Service: 1 (for example, a HSI service).

Out-of-band runs on its own RG WAN interface. An independent
VLAN outside of the service VLANs is provisioned on both the RG
and ONT to facilitate communication to the ACS service.
Valid Options
in-band, out-of-band
Outer VLAN
(For out-of-band management mode, only.) TR-069 management VLAN
(outer tag if double tagged).
none ‡, from RG, enter
value
Inner VLAN
(For out-of-band management mode, only.) TR-069 management VLAN
(inner tag if double tagged).
none ‡, from RG, enter
value
P-Bit
(For out-of-band management mode, only.) TR-069 management VLAN
P-bit.
0‡-7
Bandwidth Profile
(For out-of-band management mode, only.) Name of bandwidth profile
to use.
Any existing bandwidth
profile
‡ Default
To create a new RG management profile
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Service > RG
Management.
Locally on E7:

On the Navigation Tree, click ONTs.

In the Work Area, click Profiles > RG Management > Profiles.
2. On the menu, click Create.
3. Reference the table above to configure the parameters.
4. Click Create.
5. Associate the RG management profile to the RG interface using one of the following
methods:
a. Directly associate the profile to an RG interface.
See Configuring an ONT Residential Gateway Interface (on page 262).
b. (CMS R12.1 or later only) Reference the profile in an ONT Template and apply the
template to an ONT when configuring the PON.
See Creating an ONT Template (on page 191).
See Applying an ONT Template (on page 257).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
201
For CLI:
create rg-mgmt-profile <name> acs-url <url> username <u-name>
password <pswd> [mgmt-mode|outer-vlan|inner-vlan|p-bit|bw-profile]
set rg-mgmt-profile <name> acs-url <url> username <u-name> password
<pswd> [mgmt-mode|outer-vlan|inner-vlan|p-bit|bw-profile]
Creating Voice Service Profiles
This section describes how to create profiles and objects that will be associated with voice
services provisioned on an ONT POTS port.
For each type of voice service:


Define the applicable IP host.
Create the voice service profile.
For SIP Gateway voice service using a SIP configuration file:


Place the SIP gateway configuration file on a server local to the E7 for an download
operation.

For P-series ONTs, see the Calix Application Note: Using the 700 ONT VoIP
Configuration File for a template and example file.

For T-series ONTs, contact Calix to submit an intake form to customer service with
defined configuration parameters. This allows the creation of an approved SIP
gateway configuration file from Calix to be applied to all ONTs
Optionally, you can create a dial plan. If a custom numbering plan is not applied to a
Voice port, the E7 applies the default numbering plan table (Access).
For SIP Remote voice service using a VoIP configuration file:

For P-series ONTs only, see the Calix Application Note: Using the 700 ONT VoIP
Configuration File for a file template and example.
Note: The 844G and 854G GigaCenters do not support remote TFTP download of the
legacy SIP configuration file (SIP RMT Method).
Next steps:
After completing the creation of profiles for voice services, see the following sections to
continue configuring voice services:



Configuring a PON (on page 231)
Configuring Voice Services (on page 307)
Configuring T1 Services (on page 336)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
202
Configuring IP Hosts for Voice Services
This topic describes how to configure an IP host that defines how an ONT obtains an IP
address for communication.
Each voice service option requires an IP host definition object that specifies an IP host
address for VoIP. (The definition references a tag action that specifies the classifying and
marking of packets from the subscriber port into the service VLAN.) Although an IP Host is
configured for each type of voice service on an ONT, it is not explicitly referenced when
creating a voice service because it applies to all voice services of the same type provisioned
on the ONT. However, you are given the option to modify the existing IP Host or replace it
with a new IP Host definition when adding a voice service with the Table view.
IP Host ports on the ONT are pseudo-devices which allow bridge port paths for IP Host
Termination at the ONT. These types of bridges are used to define data paths for SIP, TDM
Gateway, and T1 over Ethernet (PWE3). Each IP Host interface may be configured with a
unique IP address, mask, and gateway address. Optionally, the IP Host may obtain the IP
address configuration information via DHCP client protocol. Each IP Host has a dedicated
MAC address.
When an ONT has more than one voice port provisioned with the same type of service (for
example, SIP or TDM Gateway), all like services provisioned on that ONT are managed by a
single IP host.
Configure an IP host to define how an ONT obtains an IP address for communication. An
ONT may support the following IP hosts, if equipped with the necessary ports.

SIP IP host indicated by SIP in the ID. (Only voice service T-series supports.)

TDM Gateway IP host indicated by TDM in the ID.

H.248 Gateway IP host indicated by H.248 in the ID.

MGCP Gateway IP host indicated by MGCP in the ID.

T1 pseudowire (PWE3) services IP host indicated by PWE3 in the ID.
VLAN Association to voice services
The IP Host object references a service tag action that indicates the voice service VLAN by
one of the following methods:

An IP host can directly specify an outer tag, when the referenced service tag action states
"Specified in Service" for the Outer Tag parameter.
This allows you to apply a different VLAN tag for the same service type (SIP, TDM
gateway, H.248 gateway, or T1 PWE3) on each ONT.

An IP host can reference a service tag action that specifies the service VLAN ID for the
provisioned voice services.
This allows you to apply the same VLAN tagging for all ONTs that use the referenced
service tag action object.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
203
Note: The VLAN assignment must be different between the VoIP IP host and the
subscriber port. Sharing VLANs between a subscriber port and a VoIP IP host is not
supported.
Configuration guidelines







The ONT requires that voice traffic be set to an Expedited Forwarding Class of Service
(CoS 4). Therefore, the associated service tag action must either specify CoS 4 or a P-bit
value of 5, 6, or 7.
For TDM Gateway services, the E7 allows operators to use the C7 internal DHCP server
to provide IP addresses for ONT VoIP hosts, or use an external DHCP server option.
The E7 GPON only supports a single VoIP Interface Group for 700GE, 700GX and
760GX, although the GX ONTs support multiple VoIP IP Hosts.
The T-series ONTs only support a SIP gateway VoIP service that requires a SIP gateway
configuration file which is referenced in the SIP IP Host object.
T-Series does NOT support static provisioning of a DNS server for the SIP IP-Host.
Therefore, you must use DHCP to specify the DNS server to the ONT. Calix
recommends that redundant DHCP servers are included in the equipment configuration.
To provision the IP Host for a DHCP host protocol configuration, you must select dhcp
for the Host Protocol parameter. Any previously assigned Static IP, Static IP Mask, and
Static IP Gateway addresses are ignored, yet preserved.
To provision the IP Host for a Static protocol configuration, you must select static for
the Host Protocol parameter, and then enter the Static IP, Static IP Mask, and Static IP
Gateway addresses.
Note: When the IP Host protocol is changed from Static to Dynamic at the VDSL line
card level, the applied SIP Gateway Profile DNS entries must be populated with zero
entries (0.0.0.0).






The E7 SIP IP-Host does not support DHCP Option #60.
If the ip-host is set to no-ip (PWE3 only), no IP address is specified.
For voice and pseudo-wire services the static IP gateway and subnet mask attribute are
only required when static IP addresses are in use.
The gateway address and subtending IP addresses must belong to the same subnet, as
indicated by the mask.
To provision an IP host for H.248 or MGCP services using Fully Qualify Domain Name
(FQDN), follow these requirements:

The ‘Host Protocol’ parameter must be set to dhcp.

The ‘Host Name’ parameter must be configured with a fully qualified domain name.

The ‘Primary Gateway Controller’ and ‘Secondary Gateway Controller’ parameters in
the H.248 or MGCP Gateway Profile must be configured with a fully qualified
domain name.
The static IP address must not be the same as the gateway address.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
204





A single IP host (ID indicates TDM) manages all of the TDM Gateway services on the
ONT.
A single IP host (ID indicates H.248) manages all of the H.248 Gateway services
parameters on the ONT.
A single IP host (ID indicates PWE3) manages all of the PWE3 services on the ONT.
A single IP host (ID indicates MGCP) manages all of the MGCP Gateway services on
the ONT.
A single IP host (ID indicates SIP) manages all of the SIP services on the ONT.

The E7 supports 8 SIP configuration files for each combination of
vendor/model/product.

SIP configuration file instances 9 through 16 are used exclusively for VoIP
configuration files and can be specified either by instance number alone or by “voip<1 through 8>.”

The instance specified in the SIP IP Host must match the instance specified in the
Retrieve ONT Configuration File operation. See Retrieving and Applying a SIP GW
Configuration File (on page 237).
Before starting
Before starting the configuration process, check that the following conditions are met:


The service tag action that you want to reference in the IP host is already created.
The IP address for the ONT, subnet mask, and IP gateway are already determined, if the
host protocol is set to "Static."
Parameters
You can provision the following parameters for IP host profiles:
Parameter
Svc Tag Action
Description
Name of service tag action or "none" for no service tag action. IP host
traffic is always untagged.
Valid Options
index-name of tag action
Note: The referenced service tag action must specify P-bits that map
to the Expedited Forwarding CoS (CoS 4 or P-bit 5, 6, or 7), as the
ONT requires that SIP traffic be set to Expedited Forwarding.
For voice, typical deployments set to add a single tag upstream (and
strip downstream) and set the upstream TCI to be set to 6 (expedite
service)
Outer Tag
Indicates the customer-specific tag when the Output Outer Tag
attribute of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005 which
are reserved for E7
operation.)
Inner Tag
Indicates the customer-specific tag when the Output Inner Tag
attribute of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005 which
are reserved for E7
operation.)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
205
Parameter
Host Protocol
Description
Host protocol for the SIP client. If you select "static," you must also
enter a static IP address, mask, and gateway addresses.

If the ip-host is set to no-ip (PWE3 only), no IP address is
specified.

If you set the Host Protocol to dhcp, the previously-set Static-IP,
Static IP Mask, and Static IP Gateway addresses are ignored, yet
preserved.

If you set the Host Protocol to static, you must also enter the
Static-IP, Static IP Mask, and Static IP Gateway addresses.
Valid Options
static, dhcp, no ip (PWE3
only)
Note: If GW Profile uses FQDNs, then the ONT should also use an
FQDN. If the GW profile uses static IPs, then the ONT should also use
a static IP.
Static IP
(Static host protocol only) IP address statically assigned to the ONT if
the host protocol is static. This attribute is ignored, yet preserved, if the
host protocol is DHCP.
4-byte IP address
Static IP Mask
(Static host protocol only) IP network mask assigned to the ONT if the
host protocol is static. This attribute is ignored, yet preserved, if the
host protocol is DHCP.
4-byte IP address
Static IP Gateway
(Static host protocol only) Static IP gateway 4-byte address for the
ONT to use in routing its traffic to the SIP server, if the host protocol is
static. This attribute is ignored, yet preserved, if the host protocol is
DHCP.
4-byte IP address
Hostname
(MGCP and H.248 only) Host-name that will be transmitted in DHCP
Option 81. The ‘Host Name’ must be configured with a fully qualified
domain name.
text string
Config-file-instance
(SIP only) An instance that must be referenced when the SIP gateway
configuration file is retrieved. Instances 9 through 16 are used
exclusively for VoIP configuration files and can be specified either by
instance number alone or by “voip-<1 through 8>.”
None ‡, voip1-8, enter value

voip-1
- Instance for VoIP (9)

voip-2
- Instance for VoIP (10)

voip-3
- Instance for VoIP (11)

voip-4
- Instance for VoIP (12)

voip-5
- Instance for VoIP (13)

voip-6
- Instance for VoIP (14)

voip-7
- Instance for VoIP (15)

voip-8
- Instance for VoIP (16)
Note: The instance specified in the SIP IP Host must match the
instance specified in the Retrieve ONT Configuration File operation.
To create an IP host profile
1. On the Navigation Tree, click ONTS.
2. Click Provisioned ONTS > IP Hosts.
3. In the work area, double-click the IP host to configure.
4. Reference the table above to configure the parameters.
5. In the menu, click Apply.
For CLI:
set ont <ont ID> ip-host [sip|tdm-gw|pwe3|mgcp|h248]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
206
Creating a Dial Plan and Rules
This topic describes how to create and delete number plan tables for SIP gateway VoIP
service.
Number plans are used to identify specific types of phone numbers dialed by a subscriber,
and to process the number before transmission by deleting, replacing, or adding digits
according to the relevant rule. The rule can also automatically add the country code and
national destination (region) code, or deny the number pattern entirely.
If a custom numbering plan is not applied when you create a SIP gateway service, the default
numbering plan table (Access) is applied which contains a generic digit entry rule and a rule
for 911 calling. Up to twenty number plans may be created per E-series node or modular
chassis system.


On legacy systems, the dialplan is embedded in the SIP gateway object.
On current systems using the SIP Gateway with per-port provisioning method, a separate
SIP Dialplan profile can be created and attached to the SIP port service.
Digit collection timeout and calling
The default digit collection timeout (referred to as the inter digit timeout) is 10 seconds for
defined numbering plan tables. If at any point during the 10-second timeout sufficient digits
are collected, the call is made immediately.
Note: If you apply a custom numbering plan with no rule entries, a digit collection timeout
of three seconds is enforced, regardless of how many digits are collected.
System-default dial plan rules
Rule ID
Pattern
system-default-1
^911n
system-default-2
^411
system-default-3
^[2-9][0-9]{6}
system-default-4
^1[2-9][0-9]{9}
system-default-5
^011[0-9]*T
system-default-6
^S[0-9]{2}
Parameters
You can provision the following parameters for creating a dial plan and adding rules:
Parameter
Description
Valid Options
Name*
Descriptive name for the dial plan.
text string up to 31 characters
Digit Short Timer(s)
Value to use that resolves an overlapping dial plan, where
you can enter additional digits if needed, causing a much
faster timeout and sending the digit string / INVITE much
quicker.
1-16
4‡
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
207
Parameter
Description
Digit Long Timer(s)
Value = 16 to use as the first digit timer (where dial tone will
time out) as well as in conditions where no dial plan match
has been found so more digits are required. Once a partial
match is found the long timer is no longer used.
4-20
16 ‡
ID
Index of dial plan rule.
1-30
Pattern
Dial plan rule pattern.
^
|
[a-b]
{n}
*
T
S
c
r
d
,
n

^ Match from the start of the dial string

| Individual elements of the dial plan are separated by
the vertical bar (pipe key)

[a-b] Square brackets are used to define options or subranges of allowable digits

{n} Curly brackets are used to define the number of of
allowed digits in a string. Applies only to variable directly
preceding it.

* Wild card match - Matches on a variable number of
digits

T Variable digit timeout

S Star key on the handset - applies to Vertical Service
Codes

c Confirmation tone is played after star code is
executed

r Recall tone is played during call forwarding sequence

d Dialtone is played during a call forwarding sequence

, (Comma) Outside dialtone is played if preceded by a 9

n no local disconnect
Valid Options
Note: The Maximum Network Dial Plan Table size is 100
rows x 28 (2800 bytes).
A rule cannot exceed 28 bytes (or characters), because a
rule must fit in a single row. A rule is not allowed to overlap
rows.
* Required
‡ Default value
To create a dial plan
1. On the Navigation Tree, click E7.
2. Click Profiles > Service > Dial Plan.
3. In the menu, click Create.
4. In the Name box, enter the name for the dial plan table (up to 31 characters).
5. In the Digit Short Timer(s) box, enter a value to use that resolves an overlapping dial
plan, where you can enter additional digits if needed, causing a much faster timeout and
sending the digit string / INVITE much quicker.
6. In the Digit Long Timer(s) box, enter a value = 16 to use as the first digit timer (where
dial tone will time out) as well as in conditions where no dial plan match has been found
so more digits are required. Once a partial match is found the long timer is no longer
used.
7. Click Create.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
208
For CLI:
create dial-plan <name> [digit-short-timer|digit-long-timer]
delete dial-plan <name>
set dial-plan <p-name> [rule|name|digit-short-timer|digit-longtimer]
show dial-plan [<name>]
To create dial plan rule
1. On the Navigation Tree, click E7.
2. Click Profiles > Service > Dial Plan.
3. In the Work area, double-click the dial plan of which you want to add a rule.
4. In the menu, click Create > Dial Plan Rule.
5. In the Create Dial Plan Rule dialog box, do the following:
a. In the ID list, select the index value to use if different from the default rule of "1."
b. In the Pattern box, type the pattern string and rule string.
The pattern must start with ^ and end with |.
For allowed characters, refer to the above table.
6. Click Create.
For CLI:
add rule <p-index> to-dial-plan <p-name> pattern <token>
delete dial-plan <name>
set dial-plan <p-name> [rule|name|digit-short-timer|digit-longtimer]
show dial-plan [<name>]
Creating a SIP Gateway Profile
This topic describes how to create a SIP gateway profile that is assigned to a SIP gateway
service provisioned on a Voice port.
You can define a unique SIP Profile ONTs and E-series xDSL nodes, entering attributes for
both the Primary Proxy Server settings, Primary and Secondary DNS servers, as well as
Secondary Proxy Server settings if enabling SIP Server Redundancy using static host
provisioning.
Parameters
You can provision the following parameters for SIP gateway profiles:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
209
Parameter
Description
Valid Options
Name*
Name of the SIP profile.
Any established SIP service profile
Proxy Server
IP address or hostname of the SIP proxy server of the SIP
server or outbound proxy SIP server. If the primary path
or server is disrupted, the ONT or VDSL2 card will resolve
to a pre-provisioned secondary server without the need
for DNS.
IP address, hostname
Note: A DNS server is required if this parameter value is
a Fully-Qualified Domain Name (FQDN) of the SIP server.
Note: It should be noted that T-series ONTs requires the
proxy server and register server to be set to the same
value. When the proxy server is specified, OMCI will set
both the proxy server and register server. The P-series
ONTs will ignore attributes it does not understand.
Proxy Server Port
UDP port for proxy server.
0-65535
5060 ‡
Secondary Proxy
Server
IP address of the secondary SIP proxy server, or
outbound proxy SIP server. If the primary path or server is
disrupted, the SIP client remains connected, as long as
the secondary proxy functions correctly. When the
secondary proxy detects a failure or is disabled, the SIP
client will again try to switch back to the primary SIP
proxy.
IP address, hostname
Note: Not supported on the T-Series ONTs.
Secondary Proxy
Server Port
UDP port for secondary proxy server.
Note: Not supported on the T-Series ONTs.
0-65535
5060 ‡
Primary DNS Server*
IP address or hostname of the primary DNS server.
IP address
Secondary DNS
Server*
IP address or hostname of the secondary DNS server.
IP address
RTP Codec First
Order
The Realtime Transport Protocol (RTP) code to use.
u-law ‡, a-law, g723, g729

a-law algorithm is commonly used in Europe.

u-law (mu-law or µ-law) algorithm is commonly used
in the USA and Japan.

g723 (T-series only) G723 encoding

g729 (T-series only) G729 encoding
Packet Rate First
Order
(xDSL or T-series only) The expected RTP packet rate
sent by the ONT or E-series (packets/msec).
10ms ‡, 20ms, 30ms
Silence Suppression
First Order
Whether to enable Silence Suppression first-order priority
codec.
selected (enabled), unselected (disabled)
‡
RTP Codec Second
Order
The Realtime Transport Protocol (RTP) code to use.
none ‡, u-law, a-law, g723, g729

a-law algorithm is commonly used in Europe.

u-law (mu-law or µ-law) algorithm is commonly used
in the USA and Japan.

g723 (T-series only) G723 encoding

g729 (T-series only) G729 encoding
Packet Rate Second
Order
(xDSL or T-series only) The expected second-order RTP
packet rate sent by the ONT or E-series (packets/msec).
10ms ‡, 20ms, 30 ms
Silence Suppression
Second Order
Whether to enable Silence Suppression second-order
priority codec.
selected, unselected ‡
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
210
Parameter
RTP Codec Third
Order
Description
The Realtime Transport Protocol (RTP) code to use.

a-law algorithm is commonly used in Europe.

u-law (mu-law or µ-law) algorithm is commonly used
in the USA and Japan.

g723 (T-series only) G723 encoding

g729 (T-series only) G729 encoding
Valid Options
none ‡, u-law, a-law, g723, g729
Packet Rate Third
Order
(xDSL or T-series only) The expected third-order RTP
packet rate sent by the ONT or E-series (packets/msec).
10ms ‡, 20ms, 30ms
Silence Suppression
Third Order
Whether to enable Silence Suppression third-order priority
codec.
selected (enabled), unselected (disabled)
‡
T1 Timer (ms)
T1 and T2 are SIP timers. T1 is an estimate of the round
trip time, the client will start to retransmit an INVITE
transaction at T1 and then double the time for each
subsequent retransmission.
100-1500
500 ‡
T2 Timer (s)
T1 and T2 are SIP timers. T2 is the maximum retransmit
interval for non-INVITE requests and INVITE responses.
These will rarely change.
1-5
4‡
Registration
Period(s)
Duration of the SIP registration request.
60-86400
3600 ‡
Distinctive Ring
Prefix
Distinctive ring prefix is an identifier used in the Alert-Info
header field (up to 36 characters). The E7 acts as the
media gateway to support different ring cadences
generated from the softswitch in real time. Assigning
distinctive ring patterns to specific incoming numbers for a
specific VoIP port must be configured on the softswitch.
text string
Bellcore-dr ‡
Important: The case-sensitive name must match the
Distinctive Ringing text string used by the softswitch.
The softswitch sends an INVITE to the E7 with the header
Alter-Info field, for example:
AlertInfo = <xxx://xxx.xx.xx/xxx/Bellcore-dr1>
The string after last forward slash ( / ) is parsed as the
ring ID.
When a line is in ring state, the ring cadence is used
based on the Alert-Info header in INVITE message. The
cycle that is defined by the ring cadence index is repeated
until the line leaves the ring state.
Call Waiting Prefix
Call-waiting ring prefix.
text string
CallWaitingTone ‡
Out Of Band DTMF
Out-of-band Dual-Tone Multi-Frequency (DTMF) mode.
none ‡, rfc2833, info
Local Hook Flash

Select Info to relay DTMF tones as SIP INFO
messages.

Select rfc2833 to relay DTMF tones according to RFC
2833. (Only supported on GigaCenter ONTs.)

Select none to not relay DTMF tones.
Defines where hook-flash control resides.

When enabled (selected), the local User Agent will
consume the hook-flash and provide the service
locally.

When disabled (unselected), then the hook-flash is
passed to the Softswitch for processing.
selected (enabled) ‡,
unselected (disabled)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
211
Parameter
RTP DSCP
Description
The DiffServ Code Point (DSCP) value for traffic using
this SIP profile.
Valid Options

0-63 - DSCP for RTP packets

cs0 - DSCP CS0 (0)

cs1 - DSCP CS1 (8)

af11 - DSCP AF11 (10)

af12 - DSCP AF12 (12)

af13 - DSCP AF13 (14)

cs2 - DSCP CS2 (16)

af21 - DSCP AF21 (18)

af22 - DSCP AF22 (20)

af23 - DSCP AF23 (22)

cs3 - DSCP CS3 (24)

af31 - DSCP AF31 (26)

af32 - DSCP AF32 (28)

af33 - DSCP AF32 (30)

cs4 - DSCP CS4 (32)

af41 - DSCP AF41 (34)

af42 - DSCP AF41 (36)

af43 - DSCP AF43 (38)

cs5 - DSCP CS5 (40)

ef - DSCP EF (46) ‡

cs6 - DSCP CS6 (48)

cs7 - DSCP CS7 (56)
RTP Ethernet QoS
Ethernet QoS for RTP packets override.
0-7
6‡
Domain
Domain name. Alternatively, "none" can be used for no
domain name.
1-63 character text string, none ‡
If present, the domain is used to populate the SIP
destination addresses; the “to” and “request uri” fields. If
not present, the proxy server IP is used in these fields.
The domain field allows you to specify an internet type
domain address.
Example:

Domain: “empty”

Proxy-server: 10.0.20.10
Generated by software:

SIP to: sip:7663339@10.0.20.10

SIP request URI: sip:7663339@10.0.20.10:5060
Example:

Domain: mytelco.com

Proxy-server: 10.0.20.10
Generated by software:

SIP to: sip:7663339@mytelco.com

SIP request URI: sip:7663339@mytelco.com:5060
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
212
Parameter
Country Code
Description
E.164 Country code designator (Protocol Country Variant
profile). This attribute specifies the country code where
the service is being deployed. This code selects country
specific tone settings, line interfaces, line levels and line
frequencies. Currently supported values include the
following:

North America: 1 (GPON and xDSL)

Italy: 39 (xDSL only)

United Kingdom: 44 (GPON only)

Sweden: 46 (GPON only)

Poland: 48 (GPON only)

Brazil: 55 (GPON only)

Australia: 61 (GPON only)

ETSI: 9000 (GPON only)
Valid Options
1‡ -9999
Note: Country codes are not currently supported on Tseries ONTs or P-series 700GX ONTs.
Release Timer (s)
Specifies the amount of time it takes to terminate a call
after an on-hook is detected.
1-20
10‡
RTP Port
Identifies the starting RTP Port range for the SIP RTP
path.
49152‡ - 65535
Switch Type
Populates the Softswitch attribute of the SIP agent
configuration data ME with the value provided by the
Switch Type attribute of the SIP gateway profile.
zte, huaw, syla, eric, cs2k, bell

zte the dial plan # key is transmitted in the SIP INVITE
instead of escape-quote (%23)

huaw (Huawei) the dial plan # key is transmitted in
the SIP INVITE instead of escape-quote (%23)

syla the dial plan # key is escape-quote (%23) in the
SIP INVITE

eric (Ericsson) the dial plan # key is escape-quote
(%23) in the SIP INVITE

cs2k the dial plan # is escape-quote (%23) in the SIP
INVITE

bell the dial plan # key is escape-quote (%23) in the
SIP INVITE

None the dial plan # key is escape-quote (%23) in the
SIP INVITE
*Required fields
‡ Default
To create a SIP gateway profile
1. On the Navigation Tree, click E7.
2. Click Profiles > Service > SIP GW > Profiles.
3. In the menu, click Create.
4. Reference the table above to configure the parameters.
5. Click Create to save the profile.
Apply a SIP profile when you create a SIP voice service on a voice port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
213
For CLI:

create sip-gw-profile <p-name>
Creating a SIP Remote Profile
This topic describes how to create a SIP remote profile assigned to a SIP remote service
provisioned on a P-series ONT voice (POTS) port. The profile defines a network host from
which SIP configuration data can be retrieved by an ONT. For information on creating a
remote SIP configuration file, see the Calix Application Note: Using the 700 ONT VoIP
Configuration File.
Note: The T-series ONTs only support SIP gateway voice service, and do not support SIP
remote service.
SIP Remote Services Support for P-Series ONTs
For E7s running R2.3 and higher, Calix recommends that you convert lines over from the
SIP Remote Profile to the SIP Gateway Profile, eliminating the need for the remote SIP
VoIP configuration file downloaded via TFTP. Instead, you can use a reduced configuration
file that resides on the E7, and does not overlap any of the configuration parameters that are
in the SIP Gateway Profile and SIP service objects.
For compatibility to SIP services previously provisioned with software releases R2.2 and
lower, there is continued support for services using a remote SIP configuration file. For
example, if you have an existing remote SIP profile and you want it to be applied to a service,
the SIP gateway profile has a setting that can enable the remote SIP configuration file and
override the duplicate settings that are specified in the SIP gateway profile.
The E7 and P-series GPON ONTs support these methods for providing GPON voice
services: SIP gateway, TDM gateway, H.248 gateway, and MGCP gateway options.
Configuration guidelines




When a profile is changed, all subscribers using that profile are affected.
Profiles cannot be deleted while they are in use.
If the ONT receives and uses a configuration file to successfully boot up, the ONT
retains and uses that file to boot up later, when or if the TFTP server connection fails.
The same configuration file is used until the TFTP server is again reachable for a file
update.
Profiles can also be reloaded for a specific ONT POTS port from the Provisioned
ONTs > Ports > Provisioning table view, select the ONT POTS port, and then click
Action > Restart SIP Remote Configuration Service.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
214
Parameters
You can provision the following parameters for SIP remote configuration profiles:
Parameter
Description
Valid Options
Name*
Name of the SIP profile.
Any established SIP service
profile
Primary Config
Server*
IP address or hostname of the primary SIP configuration server. For the
E7 to properly resolve hostnames, a DNS server must be configured, at
least on the Management VLAN. Since SIP traffic would be on a
different VLAN, the DNS server that contains the IP to hostname
mapping for the SIP server must be reachable via the Management
VLAN.
IP address, hostname
Name of the SIP configuration file on the primary server.
80-character text string
Primary Config
Filename*
For instructions on creating a SIP configuration file, see the Calix
Application Note: Using the 700 ONT VoIP Configuration File.
Secondary Config
Server
IP address or hostname of the secondary SIP configuration server.
IP address, hostname
Secondary Config
Filename
Name of the SIP configuration file on the secondary server.
80-character text string
*Required fields
To create a SIP remote configuration profile
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Service > SIP RMT
Locally:

On the Navigation Tree, click E7.

Click Profiles > Service > SIP RMT > Profiles.
2. In the menu, click Create.
3. Reference the table above to configure the parameters.
4. Click Create to save the profile.
5. Apply a SIP remote configuration profile when you create a SIP voice service on an
ONT POTS port.
For CLI:


create sip-rmt-cfg-profile <p-name> primary-server <p-address>
primary-filename <p-file> [secondary-server <s-address>|secondaryfilename <s-file>]
restart sip-rmt-config-profile <p-name> services
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
215
Creating a TDM Gateway Profile
This topic describes how to create a TDM voice gateway profile that is assigned to a TDM
voice gateway service provisioned on a P-series ONT voice (POTS) port. The profile is
referenced when you provision the service on a POTS port.
Parameters
You can provision the following parameters for TDM Gateway voice profiles:
Parameter
Description
Valid Options
Name*
Name of the TDM gateway profile.
Any established TDM Gateway profile
Server IP Address*
The C7 SIPVCG IP address for call signaling.
IP address in dot notation
Packetization Rate*
Packetization rate in msec.
10ms ‡, 20ms
RTP DSCP*
DSCP value for RTP packets.

0-63 - DSCP for RTP packets

cs0 - DSCP CS0 (0)

cs1 - DSCP CS1 (8)

af11 - DSCP AF11 (10)

af12 - DSCP AF12 (12)

af13 - DSCP AF13 (14)

cs2 - DSCP CS2 (16)

af21 - DSCP AF21 (18)

af22 - DSCP AF22 (20)

af23 - DSCP AF23 (22)

cs3 - DSCP CS3 (24)

af31 - DSCP AF31 (26)

af32 - DSCP AF32 (28)

af33 - DSCP AF32 (30)

cs4 - DSCP CS4 (32)

af41 - DSCP AF41 (34)

af42 - DSCP AF41 (36)

af43 - DSCP AF43 (38)

cs5 - DSCP CS5 (40)

ef - DSCP EF (46) ‡

cs6 - DSCP CS6 (48)

cs7 - DSCP CS7 (56)
RTP Ethernet QoS*
Ethernet QoS for RTP packets.
0-7
6‡
*Required field
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
216
To create a TDM voice gateway profile
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E3-48C/E5-48/E7/ONT > Profile >
Service > TDM GW.
Locally on the E7:

On theNavigation Tree, click E7.

In the Work Area, click Profiles > Service > TDM GW > Profiles.
2. In the menu, click Create.
3. Reference the table above to configure the parameters.
4. Click Create to save the profile.
Apply a TDM gateway profile when you create a TDM voice service on an ONT POTS port.
For CLI:

create tdm-gw-profile <p-name> [server-ip]

delete tdm-gw-profile [p-name]

set tdm-gw-profile <p-name> [server-ip]

show tdm-gw-profile [p-name] [services]
Creating a TDM Gateway Service Group
For C7 TDM Gateway service, you must configure the SIP voice concentration group (SIP
VCG) on the C7 network and add a VoIP connection to the E7. For details, see the Calix C7
VoIP Services Guide. For details, see the Calix C7 VoIP Services Guide. If you use CMS to
provision a C7 TDM Gateway service, you can specify the CSIP VCG in a TDM Gateway
Service Group that is referenced when you activate the service.
This topic describes how to create a TDM Gateway Service Group that defines the C7
network and interface groups used for delivering the TDM Gateway service, allowing CMS
to automatically create and validate C7 gateway cross-connects.
Note: The E7 GPON only supports a single VoIP Interface Group for 700GE, 700GX and
760GX, although the GX ONTs support multiple VoIP IP Hosts.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
217
Parameters
You can provision the following parameters for TDM Gateway service groups:
Parameter
Description
Valid Options
ID*
Index of the TDM Gateway service group.
Any value between 1-1000, inclusively.
Description
Unique name that indicates the entire description of the
C7 network and Calix C7 gateway interface group used
for this TDM service group. This value is auto-filled once
the network name and interface groups are selected.
String text
If left blank, the system automatically
enters the combination of names for the
selected C7 network and interface groups.
C7 Network Name*
Name of the C7 network where the interface groups have
been created for C7 TDM gateway.
Any available configured C7 network
where the required interface groups exist.
GR303/GR8 IG*
GR-303/GR-8 Interface Group (IG) for CMS to use for
automatically creating the cross-connects.
Any available GR-303/GR-8 IG that is
established on the selected C7 Network.
SIPVCG IG*
SIP Voice Concentration Group Interface Group (IG) for
CMS to use for automatically creating the cross-connects.
Any available SIP VCG IG that is
established on the selected C7 Network.
OSMINE-Compliant Northbound Interface use only
Parameters applicable for E7 GPON and xDSL ports when the OSMINE-compliant Northbound Interface has been installed with
CMS. If you are defining end-to-end E7 TDM voice service provisioning, enter the applicable information in the fields.
Enabled
Whether the service group is enabled for use.
Y ‡ = enabled, N = disabled
*Required field
‡ Default
To create a CMS TDM gateway service group
1. On the Navigation Tree, click CMS.
2. Click System > TDM Service Group.
3. In the menu, click Create.
4. Reference the table above to configure the parameters.
5. Click Create to save the service group.
Apply a TDM gateway service group when you create a TDM voice service on an E7 system
via CMS.
Creating an H.248 Gateway Profile
This topic describes how to create a profile that specifies the H.248 gateway properties for
the P-series ONT's H.248 gateway services. The H.248 service is not supported by the Tseries ONTs.
Note: The ‘Primary Gateway Controller’ and ‘Secondary Gateway Controller’ parameters
must be configured with a fully qualified domain name, when the IP host for H.248 services
is provisioned using Fully Qualify Domain Name (FQDN).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
218
Parameters
You can provision the following parameters for H.248 gateway profiles:
Parameter
Description
Valid Options
Name*
Name of the H.248 gateway profile.
A 31-character text string
Base RTP Port
Base port number for RTP packets.
49152 ‡ to 65535
Primary Gateway
Controller
IP address or hostname of the primary H.248 gateway controller, that is,
the softswitch.
text string
Primary Switch Type
Type of voice soft switch.
cs-2000, cs-1500,
metaswitch, sonus,
genband-g2, genband-g9,
taqua, none ‡

h248-ansi-generic - softswitch type set to H.248 ANSI Generic

none - softswitch type not specified

cs-2000 - Nortel Communication Server 2000

cs-1500 - Nortel Communication Server 1500

metaswitch - Metaswitch softswitches

sonus - Sonus softswitches

genband-g2 - GENBAND G2 Compact Gateway

genband-g9 - GENBAND G9 Converged Gateway

taqua - Taqua softswitches
Secondary Gateway
Controller
IP address or hostname of the secondary H.248 gateway controller, that
is, the softswitch.
text string
Secondary Switch
Type
Type of voice soft switch.
cs-2000, cs-1500,
metaswitch, sonus,
genband-g2, genband-g9,
taqua, none ‡

h248-ansi-generic - softswitch type set to H.248 ANSI Generic

none - softswitch type not specified

cs-2000 - Nortel Communication Server 2000

cs-1500 - Nortel Communication Server 1500

metaswitch - Metaswitch softswitches

sonus - Sonus softswitches

genband-g2 - GENBAND G2 Compact Gateway

genband-g9 - GENBAND G9 Converged Gateway

taqua - Taqua softswitches
Termination Prefix
Prefix string to use for terminations.
TP ‡, text string
Ephemeral
Termination ID
ID to use for ephemeral terminations.
RTP ‡, text string
ESA Mode
Whether to enable the ESA mode.
selected = enabled
unselected = disabled ‡
RTP Codec
RTP code to use.
u-law ‡, a-law
Packet Rate
Packet rate (packets/msec).
10ms ‡, 20ms
*Required field
‡Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
219
To create an H.248 Gateway profile
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Service > H.248 GW.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > H.248 GW > Profiles.
2. In the menu, click Create.
3. Reference the table above to configure the parameters.
4. Click Create.
For CLI:
create h248-gw-profile <p-name> [rtp-base-port|pri-gw-controller|sec-gwcontroller|sec-switch-type|term-prefix|ephemeral-term-id|esa-mode|rtpmode|rtp-codec|packet-rate]
Creating an MGCP Gateway Profile
This topic describes how to create a profile that specifies the Media Gateway Control
Protocol (MGCP) properties for the P-series ONT's MGCP gateway services. The MGCP
Gateway Profile defines the base RTP port, the primary and secondary gateway controller
addresses, any termination prefix, and the ephemeral termination ID for the service. The
MGCP gateway service is not supported by the T-series ONTs.
Note: The ‘Primary Gateway Controller’ and ‘Secondary Gateway Controller’ parameters
must be configured with a fully qualified domain name, when the IP host for MGCP services
is provisioned using Fully Qualify Domain Name (FQDN).
Parameters
You can provision the following parameters for MGCP gateway profiles:
Parameter
Description
Valid Options
Name*
Descriptive name for the MGCP Gateway Profile.
A 31-character text string
Base RTP Port
Base port number for RTP packets.
0-65535
49152 ‡
Primary Gateway
Controller
IP address or hostname of the primary MGCP gateway controller, that
is, the softswitch.
dot delimited IP address
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
220
Parameter
Description
Valid Options
Secondary Gateway
Controller
IP address or hostname of the secondary MGCP gateway controller,
that is, the softswitch.
dot delimited IP address
Termination Prefix
Prefix string to use for terminations.
text string
TP ‡
Retry Timeout
Specifies the number of seconds to wait for a response to a request.
4-50
30 ‡
Restart Delay
Specifies the delay value sent in the Restart in Progress (RSIP) graceful
tear down method in seconds.
1-600
1‡
Flash Hook
Persistence
Enables a hook flash signal to be treated as a persistent event. A
persistent event is reported to the call agent even if the call agent has
not requested to be notified when it occurs.
enabled (selected), disabled
(unselected) ‡
On Hook Persistence
Enables an on hook signal to be treated as a persistent event.
enabled (selected), disabled
(unselected) ‡
Off Hook Persistence
Enables an off hook signal to be treated as a persistent event.
enabled (selected), disabled
(unselected) ‡
*Required field
‡Default
Note: From CMS, the MGCP global profile has parameters listed that apply to AE and
GPON applications. However, some of the parameters are common to both applications and
some parameters are mutually exclusive, as shown below.

Common global MGCP profile parameters for AE and GPON :


GPON-only parameters for global MGCP profile:


ID, Name, Base RTP Port, and Primary/Secondary Gateway Controller IP
Termination Prefix, Retry Timeout, Retry Delay, Flash Hook Persistence, On Hook
Persistence, Off Hook Persistence
AE-only parameters for global MGCP profile:

End Point Prefix
To create a Global MGCP Gateway Profile
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Service > MGCP GW.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > MGCP GW > Profiles.
2. In the menu, click Create to open the Create MGCP Profile dialog box.
3. Reference the table above to configure the parameters.
4. Click Create.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
221
For CLI:
create mgcp-profile <p-name> [pri-gw-controller|sec-gwcontroller|term-prefix|retry-timeout|restart-delay|flash-hookpersist|on-hook-persist|off-hook-persist]
Creating T1/E1 Service Profiles
This section describes how to create profiles and objects that will be associated with T1 or
E1 services provisioned on an ONT T1 port.
For each type of voice service:



Define the IP host for PWE3.
Create the T1 or E1 port PWE3 service profile.
Create an ONT PWE3 profile or change the System-Default profile.
Next steps:
After completing the creation of profiles for T1 or E1 services, see the following sections to
continue configuring T1/E1 services:


Configuring a PON (on page 231)
Configuring T1/E1 Services (on page 336)
Configuring an IP Host for PWE3
This topic describes how to configure an IP host that defines how an ONT obtains an IP
address for communication. Each ONT that provides T1 or E1 pseudowire (PWE3) services
has an IP host indicated by PWE3 in the ID.
Note: The IP Host object either directly specifies a VLAN association or calls a service tag
action that specifies the VLAN association for the provisioned port services.
Configuration guidelines







The PWE3 IP host only supports the static host protocol, which requires a static IP,
Static IP Mask, and Static IP Gateway addresses. PWE3 currently only supports a subnet
mask of 255.255.255.0.
For voice and pseudo-wire services the static IP gateway and subnet mask attribute are
only required when static IP addresses are in use.
The gateway address and subtending IP addresses must belong to the same subnet, as
indicated by the mask.
The static IP address must not be the same as the gateway address.
A single IP host (ID indicates PWE3) manages all of the T1 ports on the ONT.
A single IP address is used for PWE3 protocol, per ONT.
Voice traffic is carried on the expedited forwarding class of service 4.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
222

The ALU 7750 interop is supported by the E7 being able to provision each pseudowire
with a unique VLAN ID.

The svc-tag-action specifies adding an outer tag from the service.

The IP host specifies an outer tag from the service.

Each service then defines its own VLAN ID.
Before starting
Before starting the configuration process, check that the following conditions are met:


The service tag action that you want to associate to the IP host is already created.
The IP address for the ONT, subnet mask, and IP gateway are already determined, if the
host protocol is set to "Static."
Parameters
You can provision the following parameters for IP host profiles:
Parameter
Tag Action
Description
Name of a previously created "add tag" tag action in order to add a
VLAN tag to all pseudowire traffic. All pseudowires can be on the same
VLAN or each pseudowire can be provisioned with a unique VLAN ID.
Valid Options
index-name of tag action
For each pseudowire to have its own VLAN ID within the network, both
endpoints of the pseudowire will share the same VLAN ID. Use the
same service tag action that indicates "Specified in Service" for each
pseudowire circuit to allow the ONT to configure one-for-one T1/E1
circuit-to-VLAN mapping.
S-VLAN (Outer Tag)
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005 which
are reserved for E7
operation.)
C-VLAN (Inner Tag)
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005 which
are reserved for E7
operation.)
Host Protocol
Host protocol for the SIP client. "Static" is the only supported host
protocol for PWE3 IP Hosts, therefore, you must also enter a static IP
address, mask, and gateway addresses.
static
dhcp
Static IP
IP address statically assigned to the ONT if the host protocol is static.
This attribute is ignored, yet preserved, if the host protocol is DHCP.
4-byte IP address
Static IP Mask
IP network mask assigned to the ONT if the host protocol is static. This
attribute is ignored, yet preserved, if the host protocol is DHCP.
4-byte IP address
Static IP Gateway
Static IP gateway 4-byte address for the ONT to use in routing its traffic
to the SIP server, if the host protocol is static. This attribute is ignored,
yet preserved, if the host protocol is DHCP.
4-byte IP address
To create an IP host profile
1. On the Navigation Tree, click ONTS.
2. Click Provisioned ONTS > IP Hosts.
3. Select the CO endpoint ONT from the pull-down menu directly below the IP Hosts tab.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
223
4. In the work area, double-click the PWE3 IP host to configure.
5. Reference the table above to configure the parameters.
6. In the menu, click Apply.
7. Repeat steps 1 through 6 for the CPE endpoint ONT, changing the Static IP address as
necessary.
For CLI:
set ont <ont ID> ip-host pwe3 [svc-tag-action|outer-vlan|inner-vlan|hostconfig|static-ip|static-netmask|static-gw]
Creating an ONT PWE3 Profile
This topic describes how to create an ONT PWE3 profile, or change the System-Default
profile that specifies the TDM protocol for the ONT's PWE3 services. See the Calix T1
PseudoWire Applications document for details. The ONT PWE3 profile is specified when
creating the ONT provisioning record. This profile can be modified by changing the TDM
mode of the ONT. See Creating GPON ONTs (on page 244).
To create an ONT PWE3 profile
1. On the Navigation Tree, double-click ONTs.
2. Click Profiles > ONT PWE3 > Profiles, and then do one of the following:

To create an ONT PWE3 profile, click Create in the menu.

To change the System-Default profile, double-click system-default in the table view.
3. In the ONT PseudoWire (PWE3) Profile dialog box, do the following:
a. In the Name box, enter or change a descriptive name for the profile.
b. In the TDM Mode list, select whether the TDM protocol for the ONTs PWE3
services is T1 or E1.
c. Click Create or Apply.
Note: The ONT PWE3 profile is specified when creating the ONT provisioning record.
For CLI:
create ont-pwe3-profile <p-name> tdm-mode <e1|t1>
Creating a T1/E1 PWE3 Profile
This topic describes how to create a T1 or E1 port PWE3 profile that specifies how a port
interacts with the remote endpoint of the pseudo-wire. See the Calix T1 Pseudowire Application
for 766GX ONTs document for details.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
224
Global profiles in CMS
Global profiles automate synchronizing profiles across multiple E7 nodes. They support
cross-network capabilities such as bulk provisioning. You create a profile once within CMS
and apply it across all targeted E7 nodes to ensure consistency across large deployments.
When you create a global profile, the profile is automatically downloaded to the networks in
the CMS management domain that enable global profile updates.
1. On the Navigation Tree, click CMS.
2. In the Work Area, click Profile > ONT, and then select the profile to create.
Parameters
The default values are the recommended values. The Clock Timing parameter selection is
dependent on where the ONT is deployed:

Loop timing is recommended if the ONT is deployed in the CO.
A port has it' transmit timing derived from the receive timing.

Differential timing is recommended if the ONT is deployed in the field and a traceable
clock is available.
Uses a traceable clock to encode and decode RTP time stamps, allowing the RTP to
recover a more accurate clock.

Adaptive timing is recommended if the ONT is deployed in the field and a traceable
clock is NOT available.
Relies solely on information found in each RTP packet to recover the clock.
You can provision the following parameters for T1 PWE3 profiles:
Parameter
Description
Valid Options
Name*
Name of the T1 PWE3 profile.
A 31-character text string
Clock Timing
Clock timing mode.
adaptive‡, differential, Loop
(recovered from T1)

Loop timing should correspond with the CO endpoint clock timing
method, or see recommendations above. Loop method uses the
received T1 service clock where it is looped back to provide the
transmit T1 service clock.

Adaptive method uses the average arrival time of the packets to
derive the transmitter's clock. In most use cases, Calix recommends
using Adaptive/ Adaptive mode at the C7 T1 PWE and E7 GPON
ONT endpoints.

Differential method uses a residual timestamp at the sender, based
on the difference between the shared reference (traceable) time
and the T1 line. Differential timing requires the use of RTP header
timestamps.
Note: The B6 does not support differential clock timing.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
225
Parameter
Jitter Buffer
Description
Valid Options
Jitter buffer in microseconds compensates for variations in the arrival
rate of traffic at the sending end relative to the receiving end.
1000-512000
1500 ‡ (ONT PWE Profile)
To compensate for "jittery" networks, you may need to adjust the jitter
buffer depth to compensate for overruns and underrun conditions.
3000 ‡ (E7 T1/PWE Profile)
As a rule of thumb, the following formula can be used to calculate the
desired jitter buffer depth:
[(Payload Size/193)x1000 µs (microseconds) x 3
For example, a payload size of 224 bytes would yield a jitter buffer
depth value of 3482 µs (rounded up to 3500).
For Active Ethernet deployments, Calix recommends setting the Jitter
Buffer Depth to 3000 at a packet size of 192.
For GPON deployments, Calix recommends setting the Jitter Buffer
Depth to 3500 at a packet size of 224.
RTP Enable
Whether to enable RTP headers on packets. Select enable only if using
Differential Timing.
Y=enabled,
N=disabled ‡
Note: The E7 supports the ability to provision PWE3 to interoperate with
the B6-440 by adding the ability to provision the RTP Payload Type –
which defaults to a value of 96 but the B6 requires a value of 86. To
operate with the B6-440 the ONT needs to support RTP header type 86.
RTP Time Stamp
Mode
Packet Size
Clock source mode to use for RTP. Leave blank if not using RTP.
differential, absolute ‡
Note: The B6 does not support differential mode.
Packet size for SAToP service-type in bytes. The packet size value
must be the same for each endpoint.
80-1450
204 ‡
Note: The B6 has a fixed 96-byte payload size.
*Required field
To create an T1/E1 PWE3 profile
1. Access the profile page:


From CMS:

On the Navigation Tree, click CMS.

In the Work Area, click Profile > E7/ONT > Profile > Service > T1/E1
PWE3.
Locally on E7:

On the Navigation Tree, click E7.

In the Work Area, click Profiles > Service > T1/E1 PWE3 > Profiles.
2. In the menu, click Create.
3. Reference the table above to configure the parameters in a profile for the CO endpoint.
4. Click Create.
5. Repeat Steps 2, 3, and 4 changing the profile name to describe the CPE endpoint, and
then select adaptive for the Clock Timing.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
226
For CLI:




create t1-pwe3-profile <p-name> [clock-timing|jitter-buf-depth|rtpheaders|rtp-mode|sat-packet-size]
delete t1-pwe3-profile <p-name>
set t1-pwe3-profile <p-name> [clock-timing|jitter-buf-depth|rtpheaders|rtp-mode|sat-packet-size]
show t1-pwe3-profile [p-name]
Managing Global Profiles in CMS
Global profiles automate synchronizing profiles and templates across multiple E7 networks.
They support cross-network capabilities such as bulk provisioning across networks. You
create a profile once within CMS and apply it across all targeted E7 networks to ensure
consistency across large deployments.
How Global Profile Mapping Works
When you create a global profile, CMS automatically maps or links it with a local node
profile. Once linked, the local profiles are automatically synchronized or updated.
Global profiles are mapped or synchronized with local E-Series system nodes when you
perform any of the following tasks:



Create a global profile in CMS
Add a new node to CMS
Manually synchronize global profiles with nodes
For global profiles to be mapped to and synchronized with local node profiles, all of the
following conditions must be met:
1. The node must be connected to CMS.
2. The Enabled parameter for the global profile must be set to Yes. For the behavior when
this parameter is modified, see the explanations below.
3. The Global Profiles Enabled parameter for the node must be set to Yes. For the
behavior when this parameter is modified, see the explanations below.
Assuming that the above conditions are met, when you create a global profile, the system
checks the local profiles on each node and first compares all profile parameters except the
profile ID.
Note: The following global profiles are not mapped or synchronized to local profiles when
created: ONT, PPPoE, and IGMP.
The following table describes how the system maps global profiles created in CMS to local
node profiles.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
227
How a global profile maps to a local profile
When none of the
local profiles match
the global profile
The system creates a local profile with the @ symbol as the prefix in the Profile ID field.
When one or more
local profiles match
the global profile
The system maps the global profile to the matched local profile with the same profile ID, if
it exists. If it does not exist, the system maps to one of the matched local profiles.
If the global profile ID is already used by one of the local profiles, a new local profile is
created with "_1" appended to the profile ID.
To view how a global profile is mapped to individual node profiles, see Synchronizing Global
Profiles (on page 228).
Modifying the Enabled parameter for a global profile
1. If you create a global profile with the Enabled parameter set to No, the global profile
does not map to or synchronize with local profiles.
2. If you modify the Enabled parameter for an existing global profile from No to Yes, the
global profile maps to and synchronizes with enabled nodes. For any future nodes
created in CMS, the global profile is also mapped and synchronized.
3. If you modify the Enabled parameter for an existing global profile from Yes to No,
nodes already synchronized are not affected. For any future nodes created in CMS, the
global profile is not mapped or synchronized.
Modifying the Global Profiles Enabled parameter for a node
1. If you create a node with the Global Profiles Enabled parameter set to No, global
profiles do not map to or synchronize with the profiles on that node.
2. If you modify the Global Profiles Enabled parameter for an existing node from No to
Yes, the global profiles map and synchronize with the node.
3. If you modify the Global Profiles Enabled parameter for an existing node from Yes to
No, the existing profiles on the node are not affected. For any future global profiles
created or modified in CMS, the local profiles are not mapped or synchronized.
Creating Global Profiles in CMS
Global profiles automate synchronizing profiles across multiple E7 nodes. They support
cross-network capabilities such as bulk provisioning. You create a profile once within CMS
and apply it across all targeted E7 nodes to ensure consistency across large deployments.
When you create a global profile, the profile is automatically downloaded to the networks in
the CMS management domain that enable global profile updates.
1. On the Navigation Tree, click CMS.
2. In the Work Area, click Profile > E7/ONT, and then select the profile to create.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
228
Creating a Global Profile by Importing a Local Profile
You can create a global profile by importing a profile from a local E7 node.
Note: When you import a local E7 profile, the system adds the @ symbol to the front of the
global profile description.
Importing a local E7 profile requires Full CMS Administration privileges.
To create a global profile by importing a E7 local profile
1. On the Navigation Tree, select an E7 unit.
2. In the Work Area, click Profile or Template, and then click the type of profile or
template to import.
3. In the displayed list, double-click to select the profile or template to import.
4. Click Action > Import Local Profile, and then click OK to confirm the action.
5. To view the new global profile(s), on the Navigation Tree, click CMS > Profile >
E7/ONT, and then click the type of profile or Template.

Click the profile to select it, and then click Action > Details to view the
syncronization status for the profile in each of the connected networks.
Synchronizing Global Profiles
Global profiles are automatically synchronized with enabled nodes when you create a global
profile.
To view or change the Global Profiles Enabled node parameter, see Modifying the Enabled
Status of a Global Profile (on page 229).
Use the following procedure to manually synchronize global profiles. When performing a
manual synchronization, you select the global profile(s) and synchronize them to all enabled
nodes.
Synchronizing a global profile requires Full CMS Administration privileges.
Notes:
* Global ONT-related profiles can be shared between E7 GPON and AE ONTs.
* The following profiles are not shared globally and CMS synchronization is not supported:
ONT, PPPoE, IGMP, CoS, and Policies.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
229
To synchronize global profiles to all enabled nodes
1. On the Navigation Tree, click CMS.
2. In the Work Area, click Profile, and then click the node type and type of profile to
synchronize.
3. In the profile list, select the item(s) to synchronize.
4. Click Action > Synchronize.
5. In the Confirmation dialog box, click OK.
6. To view the status of the synchronization, click Action > Details. A detail screen opens
for each selected profile with details of the operation.
Modifying the Enabled Status of a Global Profile
Only the enabled status of an E7 global profile can be modified. You can toggle the status of
the Enabled field between Y (Yes) and N (No). Setting the field to Y synchronizes the
profiles with all nodes that enable global profiles.
To change the properties of a global profile, delete the old profile, create a new profile, and
then apply it.
Modifying a global profile requires Full CMS Administration privileges.
To modify the Enabled status of an E7 global profile
1. On the Navigation Tree, click CMS.
2. In the Work Area, click Profile, and then click the node type and type of profile to
modify.
3. Select the profile(s) to modify. When selecting multiple profiles, use Shift+click to select
a range of profiles, or Ctrl+click to select one profile at a time.
4. Use the horizontal scroll bar to locate the Enabled column. In the Edit row, modify the
field.
5. Click Apply. Click OK to save the new settings.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
230
Deleting Global Profiles
You can delete E7 global profiles from nodes that have profiles enabled but do not have that
profile applied. Deleting a profile does not remove provisioning from a node that has the
profile applied.
A successful deletion (where the profile is not used in any enabled nodes) removes the profile
from the CMS database. An unsuccessful deletion (where one or more nodes actively use the
profile) flags the profile as disabled, but CMS retains it in the database and on the nodes that
use it. If a global profile is used in a voice, data, or video subscriber template, it is not
deleted.
An optional force delete removes the profile from all connected nodes where it is not in
active use, and erases it from the database. A force delete does not delete the provisioning
from equipment that uses it.
Deleting a global profile requires Full CMS Administration privileges.
To delete an E7 global profile
1. On the Navigation Tree, click CMS.
2. In the Work Area, click Profile, the node type, and then the type of profile to delete.
3. Click Delete. A confirmation screen opens.
4. (Optional) Click the Force Delete check box.
5. Click OK to delete the profile.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
231
Step 3. Configure a PON
This section describes how to configure a PON at the headend (GPON port) and the
premises (ONT) side of the network. Certain configuration rules must be adhered to in order
to ensure reliable service throughout the network. Configuration rules and guidelines are
included in this guide as necessary.

For overviews of subscriber services provisioning steps with links to supporting
procedure topics, see:
Service Provisioning Overviews (on page 41)
Topics Covered
This section covers the following topics in bold that are part of the overall GPON services
configuration process:
Step 1. Configure network uplinks for GPON services
Step 2. Create system profiles that support GPON applications
Step 3. Configure a PON

Configure GPON port

Retrieve a Configuration File

Create an ONT

Adding PON Upstream CoS Profiles to an ONT

Applying an ONT Template

Configuring an ONT Ethernet Port

Configuring an ONT Voice Port

Configuring an ONT Residential Gateway Interface

Configuring an ONT Full Bridge Interface
Step 4. Configure subscriber services
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
232
Overview: Configuring a PON
This chapter describes how to configure a PON for GPON services.
Configuration process
The PON configuration process follows:
1. Configure the GPON port.

Set the Admin status for enable (on page 232)
2. Create the ONT.

Automatically for P-Series only (on page 250)

Manually for T-Series or P-Series (on page 244)
3. Apply profiles file(s).

Retrieve and apply ONT configuration file(s) (on page 237)

Map PON upstream Class of Service profiles to the ONT (on page 256)

Apply ONT template, if Home Gateway (on page 257)
4. Configure ONT ports and interfaces.

Ethernet port for data or video services (on page 257)

Voice port for VoIP services (on page 260)

RG interface for HGW, if not using the ONT template (on page 262)

FB interface for HGW, if not using the ONT template (on page 266)
Configuring an E7 GPON Port
This topic describes how to configure a GPON port on an E7 GPON line card.
VLAN Traffic flow in GPONs
E7 GPON ports have no interface association, unlike the E7 Ethernet ports. Therefore,
rather than adding a port interface to a VLAN membership to enable traffic flow, for a
GPON port to pass traffic carried on a VLAN, a service-tag action must be created
specifying the VLAN and the VLAN must already be created on the E7.


To view the VLANs associated with specific GPON ports, click the GPON card of
interest on the Navigation Tree, and then click the VLANS tab.
To view the VLANs associated with an ONT, click ONTS on the Navigation Tree, and
then click the VLANS tab.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
233

To view the ONT services associated with a specific VLAN, click VLANS on the
Navigation Tree, click the particular VLAN from the list that appears in the Work Area,
and then click the Service Associations tab.
Configuration guidelines








A GPON port is specified by card number and port number. For example, 1/1.
Each GPON-4 card provides four GPON ports that subtend up to 64 ONTs each, for a
card capacity of 256 ONTs.
Each GPON-8 card provides eight GPON ports that subtend up to 64 ONTs each, for a
card capacity of 512 ONTs.
The E7 GPON card supports up to 32 IGMP-enabled multicast VLANs on the system,
which can all be on the PON.
Dynamic Bandwidth Allocation (DBA) operation

DBA is set at the GPON port level, and is enabled by default

DBA supports up to 64 ONTs per PON.

DBA-managed traffic includes the Assured Forwarding and Best Effort traffic class
types only.

The DBA algorithm operates on the configured bandwidth profiles for each
subscriber and service, and the perceived demand from the ONTs.

All traffic in the DBA pool (Best Effort and Assured Forwarding classes) is reallocated to the pool of available bandwidth when the service is not using its
provisioned bandwidth.
GPON bandwidth guidelines

GPON has a total upstream bandwidth of 1.2 Gbps.

Any one service can be provisioned up to 1 Gbps.

Expedited Forwarding bandwidth is limited to 600 Mbps, and is not part of the DBA
pool of dynamically allocated bandwidth.

Committed Information Rate (CIR) traffic in the Assured Forwarding class is limited
to 1.2 Gbps.

Assured Forwarding services scheduled by DBA have a minimum bandwidth
allocation of 64 kbps per service, and a maximum of 1 Gbps per service.

Best Effort services scheduled by DBA have a maximum bandwidth allocation of 1
Gbps per service.
E7 GPON ports have no interface association, unlike the E7 Ethernet ports.
For traffic on a specific VLAN to be forwarded to and accepted on an E7 GPON port,
the particular VLAN must be provisioned on the E7 and a service tag action specifying
the VLAN must be included in the ONT service provisioning.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
234


In order to fully comply with the network design framework outlined by GPON C+
(ITU-T G.984.2 Amendment 2) a method for correcting errors over a single-path optical
transmission line is used called Forward Error Correction (FEC). The E7 GPON port
parameters of Upstream/Downstream FEC can be set to "auto" so the FEC is
automatically enabled when a C+ GPON Optical Interface Module (OIM) is inserted
into the GPON port socket for OLTs capable of supporting C+/FEC: E7-20 GPON8x, E7-2 GPON-8 and GPON-4r2.
Class C+ optical interface modules can also be used in non-FEC capable E7 OLTs (E7-2
GPON-4 and E7-20 GPON-4x) to provide an extension of the B+ or Reach Extended
B+ ODN reach, but FEC is required to comply with the full extent of C+ as defined in
ITU-T G.984.2 Amendment 2, combining both the added optical power of the C+
optics, and the error correction algorithm provided by FEC.
Parameters
You can provision the following parameters for GPON ports:
Parameter
Description
Valid Options
Admin Status
Administrative state of the GPON port.
disabled
enabled ‡
Split Horizon
Enabled
Enable or disable Split-Horizon forwarding on this GPON port. Traffic
is not allowed to flow between any two ports when Split Horizon is
enabled on the ports. Disabling Split Horizon allows traffic to flow
between any other port, and should only be disabled when setting up
TLAN service between multiple GPON ports on the same E7.
selected (enabled) ‡
unselected (disabled)
GoS
Index of Ethernet Grade of Service (GoS) profile to use.
Any previously-created
profile 1-10
Downstream
SDBER Rate
GPON port downstream Signal Degraded Error Rate (SDBER)
defined in 10-n. This value sets the threshold value above which the
bit error rate of the facility constitutes a degraded signal. When the bit
error rate exceeds the threshold specified in this parameter, the
system raises a signal degraded bit error rate (SDBER) alarm.
SDBER parameter values are:
2-9
5‡

6 (value of 10 to the negative 6)

7 (value of 10 to the negative 7)

8 (value of 10 to the negative 8)

9 (value of 10 to the negative 9)
Low Tx power
Alarm Threshold
(dBm)
Sets the threshold value below which the bit error rate of the facility
constitutes a degraded signal for an NE transmit optical power alarm.
-16.0 ‡ to 10.0
High Tx Power
Alarm Threshold
(dBm)
Sets the threshold value above which the bit error rate of the facility
constitutes a degraded signal for an NE transmit optical power alarm.
-16.0 to 10.0 ‡
Optical
Monitoring
Whether the GPON port allows optical monitoring.
selected (enabled) ‡
unselected (disabled)
Upstream FEC
Method for correcting upstream errors over a single-path optical
transmission line Forward Error Correction (FEC).
disabled ‡, enabled, auto
auto setting enables FEC automatically when a C+ GPON Optical
Interface Module (OIM) is inserted into the GPON port socket.
Downstream
FEC
Method for correcting downstream errors over a single-path optical
transmission line Forward Error Correction (FEC).
disabled ‡, enabled, auto
auto setting enables FEC automatically when a C+ GPON Optical
Interface Module (OIM) is inserted into the GPON port socket.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
235
Parameter
Description
Valid Options
AES
Whether the traffic on the GPON port is encrypted with Secure
Advanced Encryption Standard (AES).
selected (enabled) ‡
unselected (disabled)
Dynamic
Bandwidth
Allocation
Enable or disable dynamic bandwidth allocation on this GPON port.
selected (enabled) ‡
unselected (disabled)
Description
Descriptive name for the GPON port for easy identification.
text string with a 31character limit
‡ Default
To configure a GPON port for service
1. On the Navigation Tree, double-click an E7 GPON line card, and then click a GPON
port.

Alternatively, you can click the triangle-arrow to the left of the line card in the
Navigation tree, and then click the specific GPON port from the tree.
2. Reference the table above to configure the parameters.
3. From the menu, click Apply to save changes.
For CLI:

set gpon-port <port> ]

enable gpon-port <port>

show gpon-port <port>
Scheduling an RG Configuration Retrieve Task in CMS
This topic describes how to schedule file management tasks for the ONT Residential
Gateway (RG). This operation only applies to ONTs that support Home Gateway Services.
You can schedule a file retrieve or file remove task. The file retrieve task loads an RG
configuration file onto an E7. The file removal task removes an OMCI configuration file
from the E7.
Please refer to the Managing RG Configuration Files for more information about this
feature.
To schedule an RG Configuration file retrieve task
1. On the Navigation Tree, click CMS.
2. In the Work Area, click System > Scheduled Tasks > RG Config File
Management> File Retrieve.
3. In the toolbar, click Create.
The New RG Config File Retrieve Task dialog box opens.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
236
4. In the Schedule Options area, do the following:
a. Select Schedule for later and then click the calendar icon to open the Select Date
dialog box. Use the scroll buttons to view the next (or previous) month or year, click
the date to start the upgrade, and then click OK. In the hour (hr) and minute (min)
lists, select the time for the download to start.
b. To configure the task to recur on a daily or monthly basis, click Recurring, and then
select the task frequency by clicking the Daily or Monthly radio button. For daily
backups, click the check box next to each day of the week to schedule a backup, or
click All.
c. To specify a date and time to end a recurring backup, click Stop after and select the
date, hour, and minutes.
5. In the Config File Info area, do the following:
a. In the FTP Server box, type the IP address of the FTP server to use.
b. Enter a Username and Password for accessing the server.
c. In the File box, enter the name of the RG Configuration file that had previously been
uploaded to the FTP server.
d. (Recommended) Leave the FTP Server Validation check box selected to validate the
FTP IP address, user name, and password, as well as write permission to the FTP
folder.
e. In the Vendor box enter the code "CXNK" for P-Series ONTs.
f. In the Instance box, enter the RG configuration file instance number. The E7
supports eight instances for RG configuration files (index values 17 - 24).
g. In the Version box, enter the software version.
h. In the Model box, enter the ONT model number. This field is optional. You can use
"." characters as wildcard characters.

“7..GE.” – will match any 700GE.

"8..GE.” or “836GE.” will match the 836GE.

The ‘.’ at the end is required because ONTs report spaces in the model number.
i.
In the Product box, enter a code that indicates the ONT product family. For
example, all Calix ONTs that can support RG use a product code of "S8". This field
is optional.
j.
If the Apply Config File box is checked, and if an ONT is provisioned with this
particular instance has a higher software version number, the new configuration will
automatically be downloaded to the ONT.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
237
To schedule an RG Configuration file remove task
1. On the Navigation Tree, click CMS.
2. In the Work Area, click System > Scheduled Tasks > RG Config File
Management> File Remove.
3. In the toolbar, click Create.
The New RG Config File Remove Task dialog box opens.
4. In the Schedule Options area, do the following:
a. Select Schedule for later and then click the calendar icon to open the Select Date
dialog box. Use the scroll buttons to view the next (or previous) month or year, click
the date to start the upgrade, and then click OK. In the hour (hr) and minute (min)
lists, select the time for the download to start.
b. To configure the task to recur on a daily or monthly basis, click Recurring, and then
select the task frequency by clicking the Daily or Monthly radio button. For daily
backups, click the check box next to each day of the week to schedule a backup, or
click All.
c. To specify a date and time to end a recurring backup, click Stop after and select the
date, hour, and minutes.
5. In the Config File Info area, do the following:
a. In the Vendor box enter the code "CXNK" for P-Series ONTs.
b. In the Instance box, enter the RG configuration file instance number. The E7
supports eight instances for RG configuration files (index values 17 - 24).
c. In the Version box, enter the software version.
d. In the Model box, enter the ONT model number. This field is optional.
e. In the Product box, enter a code that indicates the ONT product family. This field is
optional.
f. If the Force Remove box is checked, CMS will make a best effort attempt to remove
this specific index file, even if there is a model mismatch.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
238
Retrieving and Applying a Configuration File
This topic describes how to retrieve, and apply ONT configuration files. This topic also
shows how to remove configuration files from the E7.

T-series
The SIP configuration file and RG configuration file is generated by Calix and must be
requested via an intake form that you submit to Calix with all configuration parameters
pre-defined. Calix then provides an approved configuration file that is then transferred to
a server local to the E7. See Completing Residential Gateway and SIP Configuration File Intake
Forms.
Note: Please allow two weeks for the generation and approval process.

P-series
The RG configuration file must be created with the ONT embedded Web Interface
(EWI), saved, and then transferred to a server local to the E7.
The SIP configuration file can be created based on the Calix VoIP template and sample
file available with Calix Application Note: Using the ONT VoIP Configuration File, and then
transferred to server local to the E7.
Note: The P-series can also omit the SIP configuration file and base the service
provisioning exclusively on the E7 SIP Gateway Profile.
Process
The operation is similar for retrieving and applying both VoIP and RG configuration
files. However they can be distinguished from each other by the instance number that is
specified.

VoIP files use instances 9 through 16 exclusively and can be specified either by
instance number alone or by "voip-<1 through 8>."
The SIP configuration-file instance is also specified in the E7 SIP IP Host applied to
the ONT SIP voice services.

RG files use instances 17 through 24 exclusively and can be specified either by the
instance number alone or by "rg-<1 through 8>."
The RG configuration-file instance is also specified in the ONT template applied to
the ONT or the ONT RG interface.
The following steps outline the process for retrieving and applying a configuration file:
1. Retrieve the configuration file from an external server that is reachable by the E7.

The “cancel” action can be invoked before the "apply" action is performed, either
while the “retrieve” action is still in progress, or after the “retrieve” action has
completed.
2. Apply the configuration file to the ONT, causing the ONT to reset and use the new
file.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
239
3. Delete the old ONT configuration file from the E7 OLT flash memory.
When you load a configuration file onto the E7, all ONTs in Configuration File Management
Mode will automatically receive this file.


You can also manually load the file on a single ONT by specifying both a product code
and model mask to identify a specific ONT when you want to test a new configuration
file, or if you want to update the configuration file used by each ONT incrementally. The
OLT will not download a new configuration file, unless the version number in the file is
different from what is in the file currently on the ONT.
You can also specify the product code and/or model mask to identify a group of ONTs,
including a mix of model types.
Note: The ONT must be reset to factory default values before downloading new
configuration files. This can be accomplished by either pressing and holding the reset button
for 20 seconds or using the EWI. Applying a new RG configuration file will reset the RG
configuration on the HGW. If a subscriber has modified items such as SSIDs via the EWI,
these changes will be lost when the new RG configuration file is applied.
The T-Series ONTs will reset to factory default settings during the "retrieve ONT
configuration file" step if a prior non-default configuration file is present in the ONT.
Perform the "apply ONT configuration file" step as soon as possible after the retrieve step to
minimize service disruptions. Once the subscriber RG setting are provisioned, major changes
to the L3 services are not allowed via XML Configuration files. (Changes are only allowed via
WAN GUI settings on an individual ONT basis or via ACS/TR-69.)
The following is typical of external RG configuration conditions:
Download file over the OMCI from the E7
Download file via ACS

Management Mode:
External

Management Mode:
External

Config-File Instance:
17 - 24

Config-File Instance:
none
Configuration File Management Actions
From the Actions menu, you can select from the following:
Action
Retrieve
Description
Retrieves the configuration file from a configured FTP server and places it in the E7 flash
memory. The E7 may distribute the configuration file but it will not be applied to the ONT.

FTP Server*

User*

Password*

File Path*

Vendor*

Instance*

Version*

Model

Product
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
240
Action
Cancel
Apply
Description
Cancels the retrieve operation and deletes the ONT configuration file from ONT and E7
memory. The “cancel” action can be invoked before the "apply" action is performed, either
while the “retrieve” action is still in progress, or after the “retrieve” action has completed.
After the “apply” action is performed on the configuration file, then you must use the
“remove” action to delete the configuration file from ONT and E7 memory.

Vendor*

Instance*

Model

Product
Applies the downloaded (retrieved) configuration file to the ONT. This results in an ONT
reset, and then the ONT applies the configuration from the file to its provisioning. When
this action is invoked, all the ONTs matching the vendor, model, and product will be reset.

Remove
Vendor*

Model

Product
Removes unused configuration files from the E7.

Vendor*

Instance*

Model

Product
*Required field
Note: From CMS, you can schedule the above tasks to be performed on multiple E7s that
span multiple regions or network groups. The Retrieve scheduled task has an option of
"Apply" (default is unselected), to push the retrieved configuration file to ONTs and trigger a
reset for the ONTs to start using the provisioning indicated in the file.
Parameters
You can provision the following parameters when managing configuration files:
Parameter
Description
FTP Server*
The IP address of your FTP server.
User*
Username required by your FTP server.
Password*
Password required by your FTP server.
File Path*
File path of the configuration file on your FTP server.
Vendor*
The ONT vendor. For example, Calix vendor string is CXNK.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
241
Parameter
Instance*
Description
The E7 supports 8 SIP configuration files and 8 RG configuration files for each
combination of vendor/model/product.
Instances 9 through 16 are used exclusively for VoIP configuration files and can be
specified either by instance number alone or by “voip-<1 through 8>”

voip-1

voip-2
- Instance for VOIP (10)

voip-3
- Instance for VOIP (11)

voip-4
- Instance for VOIP (12)

voip-5
- Instance for VOIP (13)

voip-6
- Instance for VOIP (14)

voip-7
- Instance for VOIP (15)

voip-8
- Instance for VOIP (16)
- Instance for VOIP (9)
Instances 17 through 24 are used exclusively for RG configuration file and can be
specified either by the instance number alone or by “rg-<1 through 8>”
Version*

rg-1
- Instance for RG (17)

rg-2
- Instance for RG (18)

rg-3
- Instance for RG (19)

rg-4
- Instance for RG (20)

rg-5
- Instance for RG (21)

rg-6
- Instance for RG (22)

rg-7
- Instance for RG (23)

rg-8
- Instance for RG (24)
The version number of the SIP configuration file or the RG configuration file <x.x.x.x>.
Typically, the version string is the first line in the configuration file.
Note: The OLT will not download a new configuration file, unless the version number in
the file is different from what is in the file currently on the ONT.
Model
Optional model mask to further specify the ONTs on which you want to apply the
configuration file. You can use "." characters as wildcard characters.

“7..GE.” – will match any 700GE.

"8..GE.” or “836GE.” will match the 836GE.

The ‘.’ at the end is required because ONTs reports spaces in the model number.
Note: The use of Model number is being deprecated on GigaCenter products. As such,
there is no model number search criteria for GigaCenter products. Perform look-up by
product code only (see below).
Product
The ONT product code is an optional mask to further specify the ONTs on which you want
to apply the configuration file. For example, all Calix GigaCenters that support RG use a
product code of "P0" (P-zero).

S8 - 711GE, 712GE, 716GE, 717GE, 721GE, 722GE, 725GE, 726GE, 727GE,
836GE

B8 – 741GE, 742GE, 743GE, 744GE

SF – 710, 710G, 710GX, 711, 711G, 711GX, 712, 712G, 712GX, 714, 714G, 714GX,
720, 720G, 720GX, 721, 721G, 721GX, 722, 722G, 722GX, 724, 724G, 724GX, 725,
725G, 725GX

MD – 760G, 760GX, 762G, 762GX, 763GX, 763GX-R, 766GX, 766GX-R, 766GX-R24, 767GX-R

P0 - 844G-1, 844G-2, 854G-1, 854G-2

T0 - T071G, T072G, T073G, T076G, T077G
*Required field
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
242
General Notes




On a typical system, the Vendor parameter provides sufficient granularity for applying
SIP configuration files. That is, the Model and Product code parameters are not
necessary to specify.
In cases where SIP configuration files must be different for certain ONT types within a
given vendor, the Product code parameter should be used, if possible. For example, Calix
GX and GE ONTs may support different capabilities within the SIP configuration file,
and the Product code parameter can distinguish between GX and GE.
The Model mask parameter can further qualify ONTs within a product code, or it can be
used when the product code does not provide sufficient granularity. For example, all 700
GX/GE ONTs could be distinguished from 800 GE ONTs by using the model mask
parameter.
Note: The ONT must be reset to factory default values before downloading new
configuration files. This can be accomplished by either pressing and holding the reset
button for 20 seconds or using the EWI.
T-Series ONTs will reset to factory default settings during the "retrieve ONT
configuration file" step if a prior non-default configuration file is present in the ONT.
Perform the "apply ONT configuration file" step as soon as possible after the retrieve
step to minimize service disruptions.
a. On the Navigation Tree, click ONTs.
b. In the Work Area, click Provisioned ONTs > Provisioning.
c. In the table of ONTs, double-click the row with the ONT that you want to reset.
d. In the menu, click Action > Reset ONT.

Select the Force checkbox if you want to force the ONT to reset.

Select the Reset RG checkbox if you also want the defaults restored for the RG
partition of an ONT (for example 836GE) along with the reboot of the ONT
partition.

Clear the Reset RG checkbox if you want all of the ONT services torn down in
the ONT partition (for example 836GE) and rebuilt quickly while LAN-based
services on the RG partition continue to work. The RG WAN access is affected
during this short process.
e. Click Reset ONT to indicate that you want to proceed with the action.
Note: See RG Setting Interdependencies for scenarios where an RG configuration file is
applied to an P-Series 700GE/836GE and GigaCenter ONT, and then settings are adjusted.
To manage configuration files
1. On the Navigation Tree, click ONTs.
2. In the Work Area, click Config File Management > Action.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
243
3. Select one of the actions, described in the table above:

Retrieve

Apply

Remove
4. Click the appropriate confirmation to invoke the action.
For CLI:
retrieve ont-config
apply ont-config
remove ont-config
cancel ont-config
reset ont
Related topic



Creating an RG Configuration File (on page 194)
Classless Static Routes (on page 196)
Example Home Gateway Service Provisioning (External Configuration File) (on page 380)
RG Setting Interdependencies
This topic describes various scenarios where an RG configuration file is applied to a P-Series
700GE/836GE or GigaCenter ONT, and then settings are adjusted.
Note: This topic does not apply to the T-Series ONTs.
Configuration scenarios

When an RG configuration file is applied to an ONT, and then a subscriber logs in to the
ONT and changes the SSID name and WPA password.
Result: The ONT retains those modified settings after a reboot.

When an RG configuration file is already applied to an ONT and then another RG
configuration file is retrieved to the E7 with the same RG file instance value that has
been applied to the ONT.
Result: The ONT and E7 do a version number check on the configuration file:


If the version of the retrieved file matches the version of the applied file, the RG uses
the configuration file stored in ONT flash.

If the version of the retrieved file does NOT match the version of the applied file,
the ONT downloads and applies the configuration file from the E7, eliminating any
subscriber-made changes to the settings.
When a backup file is created for an ONT that has an RG configuration file applied,
subsequent changes are made to the settings, and then a reset is performed on the RG,
forcing the ONT to download/apply the RG file from the E7.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
244
Result: To restore an existing RG configuration, re-install the backup RG configuration
file using the Utilities > Configuration Backup/Restore. Once the file has been
restored, the ONT reboots, implementing the parameters as defined by the restored file.
This restored configuration includes what was in the originally applied RG configuration
file as well as any subsequent changes made to the settings.
Note: Locally saved configurations (using Configuration Save) are specific to that HGW
device. These configurations include all of the default values for that device such as
Administer Username and Password, SSID and WPA/WPA2 key. These device-specific
attributes may not be applicable to other units at other locations.

When a new or changed (different instance value) RG configuration file is applied to an
ONT.
Result: The ONT resets and the admin password, primary SSID, and primary WPA keys
default to the values on the sticker located on the side of the ONT.
Creating GPON ONTs
ONTs are created on the network in one of two ways:


Manually where the ONT is pre-provisioned by entering the ONT serial number into the
Create ONT dialogue box.
Automatically where the ONT is discovered on the network after successfully completing
the Remote ONT Activation Process.
Manually Creating an ONT (Pre-Provisioning)
This topic describes how to configure an ONT using the pre-provisioning and activation
approach. Typically, the provisioning of an ONT is done in advance of installation and
discovery of the physical ONT.
ONT Pre-provisioning
Create an ONT provisioning record in the E7 database by specifying an ONT Logical ID (or
let the system assign the ID), the ONT profile, and then specifying either the ONT serial
number or the registration ID.


The ONT Global Logical Identifier assigned by either you or the system. All
provisioning related to the ONT (including ports, services, etc.) is indexed using this
global identifier as a base.
The ONT profile is named with the model number of the ONT (e.g."711GX") and
describes the numbers and types of ports associated with that ONT. When an ONT is
provisioned, the system automatically creates provisioning for the appropriate ONT
ports. If you need to create a custom profile for an ONT, see Creating an ONT Profile (on
page 115).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
245


The serial number is the value associated with the specific ONT equipment and that
will be reported by the ONT when it arrives and is discovered. The value is determined
by the manufacturer and is found on the ONT and its packing.
The registration ID is a user supplied value that is independent of the specific ONT
equipment. This value is entered through a RONTA mechanism which requires that the
provisioned record contain a registration ID and no serial number. See Assigning a
Registration ID using RONTA (on page 248). When the ONT arrives and is discovered, the
serial number will be detected and included in the provisioned record.
ONT Arrival and activation
When an ONT is connected to a PON, the E7 automatically discovers the ONT and detects
the serial number. The E7 system attempts to match the ONT to an existing “provisioned
but not linked” ONT record in the database. This match may be done by serial number or by
registration ID as described above.
When the match between a discovered ONT and a provisioning record occurs, the ONT is
automatically linked to the provisioning record.
If there is no match between a discovered ONT and a provisioning record, you can do either
of the following actions:


Edit an existing provisioning record to match the serial number of a discovered ONT.
Create a new provisioning record with a serial number that matches the discovered ONT.
Once a match is found, the system updates the provisioning record to indicate the ONT is
linked to provisioning information, and to note the physical location (Shelf, Slot, GPON
Port). If the match was made using the registration ID, the serial number reported by the
ONT is added to the provisioning record. All pre-provisioning associated with the ONT
(including ports and services) is sent to the ONT and the service is brought up as
provisioned.
ONT Provisioning record modification
You can select an ONT listed in the table view to modify the provisioning record attributes,
such as adding or changing the Registration ID or changing the profile, if the change is not
service affecting.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
246
ONT Removal
To remove an ONT that is present on the system, first unlink the ONT from the
provisioning record and then delete it from the system. You can either change the ONT
serial number on the provisioning record or directly issue an action to unlink the ONT. Once
an ONT is unlinked, it will range on any E7 PON that is discovered. If the E7 system that it
connects to has the ONT’s serial number in a pre-provisioned or pre-existing ONT record,
the ONT automatically links to the new system and services resume. Within a single E7
system, the single provisioning record in the database can be associated with any card in the
system. See "Replacing or Installing Equipment" in the Calix E7 Maintenance and
Troubleshooting Guide.
You can also replace an ONT by issuing an action or effectively remove a faulty ONT from a
system by placing it in quarantine. See "Adding an ONT to Quarantine" in the Calix E7
Maintenance and Troubleshooting Guide.
Power shedding option
The GPON ONT profile does not include an option for "Disable on battery." Set the power
option on each of the individual ONT ports.
Parameters
You can provision the following parameters for an ONT:
Parameter
Description
Valid Options
ID*
Identifies ONT by a global ID. For example, 10001. You must first select
the User Assigned ID option to manually assign the ONT ID value. The
default setting allows the system to assign the ID.
1-64000000
ONT Profile*
Select one of the default Calix ONT profiles, or select a custom profile
that was previously created. See Creating an ONT Profile (on page
115).
Any established ONT profile
Admin State
Administrative status of ONT. The 'enabled-no-alarms' state enables the
ONT but suppresses alarms.
disabled
enabled
enabled-no-alarms
Serial#
ONT serial number that is a numerical portion of the FSAN Serial
Number of the anticipated ONT.
1-8 Hex digits
Select one of the following methods to pre-provision an ONT:
Registration ID

Serial#

Registration ID
ONT registration ID that is the RONTA identifier. Enter a value that you
supply independent of the specific ONT equipment and is unique
among all provisioned ONT records in the system.
1-10 alpha-numeric
characters
Select one of the following methods to pre-provision an ONT:

Serial#

Registration ID
Subscriber ID
ONT subscriber ID that matches back-office ID.
1-63 text string characters
Description
Description that labels the ONT location.
1-48 text string characters
PWE3 Profile
Name of the PWE3 profile to use from the list of available profiles. See
Creating an ONT PWE3 Profile (on page 223).
system-default
Any established PWE3
profile
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
247
Parameter
Template
Description
(CMS object only) Select one of the created ONT templates that define
all of the key management aspects of a Home Gateway (HGW) ONT as
well as the logical assignments of physical GE ports for the initial setup.
The template can also be shared between AE and GPON ONTs.
Valid Options
Any established ONT
template
There is a system-default template that applies to ONTs implicitly until
you specifically change it on an ONT. Once a template is applied to an
ONT, any further changes to that template are not reflected on the ONT.
Any new ONTs provisioned with the modified template will use the new
settings. You can always override the parameter values at the ONT
level. See Creating an ONT Template (on page 191).
*Required fields
To pre-provision an ONT before arrival
1. On the Navigation Tree, double-click ONTS.
2. Click the Provisioned ONTS > Provisioning tabs.
3. From the menu, click Create.
4. Reference the table above to configure the parameters.
5. Click Save & New if you are creating the provisioning record, or click OK if you are
modifying an existing ONT provisioning record.
6. To delete an ONT provisioning record, do the following:
a. Click the Provisioned ONTS > Provisioning tabs.
b. In the provisioning record table, click the row of the record that you want to delete.
c. In the menu, click Delete and then click Delete at the dialog box prompt.
For CLI:


create ont <ont ID> [ip-host|profile|serial-number|reg-id|subscriberid|description|ont-pwe3-profile|admin-state]
set ont <ont ID> profile <p-name> [serial-number|reg-id|subscriberid|description|ont-pwe3-profile|pon-port|admin-state]

show ont [detail|unassigned|unassigned detail]

enable ont
To link an ONT to a provisioning record upon arrival
1. On the Navigation Tree, double-click ONTS.
2. Click the Discovered ONTS tab to view the ONTs that the system recognizes.
When a match between a discovered ONT and a provisioning record occurs, the ONT is
automatically linked to the provisioning record.
3. In the Search/Filter, click Not Linked to view the discovered ONTs that are not linked
to a matching provisioning record.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
248
4. Click the row of a discovered ONT, and then from the menu, click Action and select the
method to link the ONT to a provisioning record:

Link to New Provisioning allows you to create a new provisioning record with a
serial number that matches the discovered ONT.

Link to Existing Provisioning allows you to edit the serial number in an existing
provisioning record to match the serial number of the discovered ONT.
5. In the Link ONT dialog box, do the following:
a. In the ONT Profile box, do one of the following:

If you selected "Link to New Provisioning," either leave the System Assigned ID
check box selected to automatically assign an index to the new provisioning
record, or clear the check box and enter an ID.

If you selected "Link to Existing Provisioning," chose an index to one of the
existing provisioning records that you will edit to match the discovered ONT.
b. In the Serial# box, the ONT serial number discovered by the system appears.
6. Reference the table above to configure the parameters.
7. Click Link.
For CLI:



create ont <ont ID> [ip-host|profile|serial-number|reg-id|subscriberid|description|ont-pwe3-profile|admin-state]
set ont <ont ID> profile <p-name> [serial-number|reg-id|subscriberid|description|ont-pwe3-profile|gpon-port|admin-state]
show ont [discovered|discovered detail|discovered on-pon-port|detail]
Assigning a Registration ID using RONTA
The Calix Remote ONT Activation (RONTA) feature simplifies the installation and turn-up
of any Calix ONT of the specified equipment type. Commands are entered via butt set at the
customer premises, which allows configuration of an ONT in a variety of environments,
without assistance from the central office, or the need for special equipment.
The RONTA feature is used to reset the ONT to its factory defaults, locally provision
service, or assign a registration ID as part of the pre-provisioning process. The RONTA
feature is activated when the ONT is powered with the drop fiber disconnected. The ONT
leaves the RONTA mode as soon as an optical signal is detected, leaving the Registration ID
on the ONT disabled once a successful link has occurred.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
249
Remote ONT Registration Rules
Follow these rules when using the remote ONT (RONTA) registration feature:





RONTA can only be used on Calix ONTs.
The ONT must have a physical POTS port in order to connect the butt set. The butt set
must be connected to the first POTs port on the ONT.
The Registration ID must be unique for each ONT on the network.
The ONT must be powered off when connecting the butt set. Reapplying power initiates
the RONTA sequence.
The fiber pigtail (SC-UPC connector) must be disconnected from the ONT when using
RONTA. Reconnect the pigtail once RONTA is completed and confirmed.
Note: The Registration ID must be unique per PON.
To turn-up an ONT using RONTA
1. Disconnect power to the ONT.
2. Disconnect the network fiber (pigtail) from the ONT.
3. Connect an RJ-11 terminated butt set to the first (LINE ONE) voice port on the ONT.
Note: For butt set devices using alligator clips, back-out the Tip and Ring screws and
clip the butt set leads to the T and R posts (black to Tip, red to Ring).Verify that the
network fiber is disconnected from the ONT.
4. Reapply power to the ONT.

For 700G or 700GX ONTs, listen to the butt set and wait until you hear a click
sound (ranges from 10 to 45 seconds after power has been re-applied).

For 700GE ONTs, wait for the OFF HOOK LED on the ONT to start blinking
(approximately 50 seconds for 2 POTS ONTs, 60 seconds for 4 POTS ONTs).

For GigaCenter ONTs, wait approximately 150-180 seconds for the GigaCenter to
complete it's boot-up cycle. Voice Activate is ready to accept input when the
PHONE1 LED comes on steadily when going off-hook.
Note: If digits are entered prior to the ONT being ready (click sound or OFF HOOK
Blink), those digits are ignored.
5. Press "*", "*", "*" ,"0" (star, star, star, zero) keys on the butt-set key pad. The butt set
sounds DTMF tones as the keys are pressed.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
250
Note: The volume of the voice prompt is adjustable by pressing the asterisk (star) key. At
each successive depression of the key, the volume increases (four distinct volume levels
are available) while the voice prompt is repeated at the current volume level. Replaying of
the voice prompt alone is not supported in this release. In other words, to replay the
voice prompt (pressing the star key once), a corresponding change in volume will result.
You can toggle through the four volume levels as often as necessary to return to the
desired volume.
6. A voice prompt occurs: "Please enter [GPON or AE] Registration ID followed by
pound".
Note: If you do not hear a message after entering the code, you may need to hang up the
phone (butt set) and go off hook again (or perform a flash hook), and then re-enter the
code and wait for the next voice prompt..
7. Enter a Registration ID of your choosing (up to 10 alpha-numeric characters in length
that do not have to relate directly to the FSAN), followed by the # (pound) key.
Note: When using the RONTA technique for turn-up, make sure all Registration ID
numbers are unique.
8. The voice prompts: "You entered 'xxxx'. If correct, enter 1, otherwise enter 0".
9. If you pressed 1, the voice prompt responds: "Registration ID saved".
10. If you pressed 0, the system returns to step 6 above.
Once complete, the following operational behavior is expected:


The Registration ID is persisted in flash memory.
The Registration ID is erased only when the ONT is re-set to factory default via a butt
set.
With the Registration ID now embedded, pre-provisioning is allowed without knowing the
ONT serial number.
Note: Reattach the network fiber (pigtail) to the ONT before securing the ONT enclosure.
Automatically Creating an ONT - Smart Activate
Calix has developed a family of Remote P-series ONT creation tools known as Smart
Activate. Depending on the ONT being deployed, installers can activate ONTs in one of two
ways:


Web Activate is an enhanced version of the previously available Remote ONT Activation
(RONTA) feature
Voice Activate simplifies the installation and turn-up of any Calix ONT.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
251
Web Activate
This new web browser based ONT activation tool allows the field installer to use a laptop
(plugged into the first Ethernet port on the ONT) to activate the ONT. New features
available in this tool include a Static IP configuration option for ONT deployments as well as
ONT firmware upgrade and factory reset options. Web Activate is currently available for use
with the 740GE family of ONTs as well as the 716GE-I ONT.
The Calix ONT Web Activate feature is used to pre-register ONTs as they are deployed in
the field. The application and activation process is similar to the butt-set Voice Activate
feature. During the ONT power-up boot process, the ONT enables the first Ethernet port
and creates an IP host that accepts a static IP address of 192.168.100.100. The field
technician connects the first Ethernet port to a PC and configures the PC Ethernet port to
the static address 192.168.100.1 and the subnet mask 255. 255. 255. 0. The technician opens a
web browser using the address http://192.168.100.100 and is prompted for a username and
password. The technician then enters the factory default credentials ("admin", "fiber1ttx")
and is presented with the Smart Activate page.
Note: For 844G/854G GigaCenter and 836GE/700GE Home Gateway Applications, the
Ethernet port used for Smart Activate-Web connection must be a member of the RG-1
interface.
To initiate Smart Activate, enter the 10-character alpha-numeric Registration ID into the
empty field. No special characters are allowed.
Upon clicking Apply, the ONT resets in order to apply the RegID.
Note: The GPON ONT profile does not include an option for "Disable on battery." Set the
power option on each of the individual ONT ports.
Certain parameter entry fields are automatically shown or hidden depending on the selections
made by the user. For example, all static IP configuration entry fields are shown only if the
user has selected "Management IP Address Mode" or "Static".
Note: Web Activate is not supported on 700GX ONTs.
Voice Activate
The Calix Voice Activate feature simplifies the installation and turn-up of any Calix ONT.
Commands are entered via buttset at the customer premises, which allows configuration of
an ONT in a variety of environments, without assistance from the central office, or the need
for special equipment. The Voice Activate feature can be used to reset the ONT to its factory
defaults, locally provision service, or assign a registration ID as part of the pre-provisioning
process.
Note: The Registration ID must be unique per PON.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
252
The Voice Activate feature is activated when the ONT is powered with the drop fiber
disconnected. The ONT leaves Voice Activate mode as soon as an optical signal is detected,
leaving the Registration ID on the ONT disabled once a successful link has occurred. Voice
Activate is available for use with all Calix ONTs. See Assigning a Registration ID to an ONT (on
page 252).
The following GPON ONT Voice Activate commands are available:
GPON ONT Voice Activate Commands
Function
Command
Keystrokes
Master Reset for an ONT
***#
Assigning a Registration ID (GPON Mode)
***0
Assigning a Registration ID to an ONT
Butt set provisioning via the Voice Activate feature simplifies the installation and turn-up of
any Calix ONT of the specified equipment type. Commands are entered via butt set at the
customer premises, which allows configuration of an ONT in a variety of environments,
without assistance from the central office, or the need for special equipment.
After using the management interface to assign a Registration ID and pre-provision services
to the ONT, the Voice Activate feature is used to install and turn-up a Calix ONT at the
subscriber site. Using a butt set, the craftsperson enters the same Registration ID into the
ONT allowing the installation and the service activation to be under the complete control of
the installer at the subscriber site.
Note: The Registration ID must be unique per PON.
Keep in mind the following when working with Voice Activate:
ONT Registration Rules
Follow these rules when using the voice activation feature:





Voice activation can only be used on Calix ONTs
The ONT must have a physical POTS port in order to connect the butt set. The butt set
must be connected to the first POTs port on the ONT.
The Registration ID must be unique for each ONT on the network.
The ONT must be powered off when connecting the butt set. Reapplying power initiates
the voice activation sequence.
The fiber pigtail (SC-UPC connector) must be disconnected from the ONT when using
this feature. Reconnect the pigtail once voice activation is completed and confirmed.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
253
To turn-up an ONT using Voice Activate
Note: Ensure you listen to the entire voice prompt prior to pressing any keys on the butt set.
1. Disconnect power to the ONT.
2. Disconnect the network fiber (pigtail) from the ONT.
3. Connect an RJ-11 terminated butt set to the first voice port on the ONT.
Note: For butt set devices using alligator clips, back-out the Tip and Ring screws and
clip the butt set leads to the T and R posts (black to Tip, red to Ring).Verify that the
network fiber is disconnected from the ONT.
4. Reapply power to the ONT.

For 700G or 700GX ONTs, listen to the butt set and wait until you hear a click
sound (ranges from 10 to 45 seconds after power has been re-applied).

For 700GE ONTs, wait for the OFF HOOK LED on the ONT to start blinking
(approximately 50 seconds for 2 POTS ONTs, 60 seconds for 4 POTS ONTs).

For GigaCenter ONTs, wait approximately 150-180 seconds for the GigaCenter to
complete it's boot-up cycle. Voice Activate is ready to accept input when the
PHONE1 LED comes on steadily when going off-hook.
Note: If digits are entered prior to the ONT being ready (click sound or OFF HOOK
Blink), those digits are ignored.
5. Press "*", "*", "*" ,"0" (star, star, star, zero) keys on the butt set key pad. The butt set
sounds DTMF tones as the keys are pressed.

For GigaCenter ONTs, the PHONE1 LED blinks at a 50% duty cycle indicating
voice activate sequence has been initiated.
6. A voice prompt occurs: "Please enter [GPON or AE] Registration ID followed by
pound".
Note: If you do not hear a message after entering the code, you may need to hang up the
phone (butt set) and go off hook again (or perform a flash hook), and then re-enter the
code and wait for the next voice prompt.
Note: The volume of the voice prompt is adjustable by pressing the asterisk (star) key. At
each successive depression of the key, the volume increases (four distinct volume levels
are available) while the voice prompt is repeated at the current volume level. Replaying of
the voice prompt alone is not supported in this release. In other words, to replay the
voice prompt (pressing the star key once), a corresponding change in volume will result.
You can toggle through the four volume levels as often as necessary to return to the
desired volume.
7. Enter a Registration ID of your choosing (up to 10 alpha-numeric characters in length),
followed by the # (pound) key.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
254
Note: When using the voice activation technique for turn-up, make sure all Registration
ID numbers are unique.
8. The voice prompts: "You entered 'xxxx'. If correct, enter 1, otherwise enter 0".
9. If you pressed 1, the voice prompt responds: "Registration ID saved".
10. If you pressed 0, the system returns to step 6 above.
Once complete, the following operational behavior is expected:

The Registration ID is persisted in flash memory.

The Registration ID is erased only when the ONT is re-set to factory default via a
butt set.

The Registration ID is included in Option-61 searches during DHCP discover
requests.

If the DHCP server does not respond with a configuration file name, the ONT
requests its configuration file using the following name: "<registrationID>.cfg"
With the Registration ID now embedded, pre-provisioning is allowed without knowing the
ONT serial number.
Note: Reattach the network fiber (pigtail) to the ONT before securing the ONT enclosure.
If the volume of the recorded messages is not loud enough you can change the volume by
pressing the asterisk key on the phone. This will change the volume and replay the last
message at the new volume. You can do this until you get the desired volume. All further
messages will play with this volume.
When the maximum volume is reached the volume will be set back to the lowest volume.
You can continue pressing the asterisk to increase the volume. There are 4 volume levels.
Previously the asterisk just replayed the last message. You can not just replay the last
message. It will always change the volume. If you want to just replay the message you will
either have to accept the new volume or press the asterisk key several more times to get to
the desired volume.
Upgrading ONTs
Before configuring an ONT for a subscriber service, you must download, activate, and
commit the ONT software, if not already done. For more information about E7 system
upgrades, refer to the following guides:


This Calix E7 System Upgrade Guide describes how to perform software/firmware
upgrades as well as database backup and restore operations.
The Calix E7 GPON ONT Upgrade Guide describes how to perform upgrades for
compatible P-Series, T-Series, and GigaCenter GPON ONTs which does not rely on the
OLT to distribute the software image to the ONT. The independent ONT upgrade
allows you to upgrade the ONT without upgrading the OLT system software.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
255
This document contains a subset of the information in the Calix E7 System Upgrade Guide.
Since the E7 platform supports independent ONT upgrades, see the platform release notes
to determine which ONT software image supports the OLT software currently running in
the network.
Visibility to Software Images
CMS allows you to identify which ONT software images are running in the network. The
EWI and embedded and CLI support filtering the ONT releases per card via the “show ONT
release” command. The following example shows the release management page where
ONT images are identified in CMS.
ONT image status indications




Running indicates the OLT image is affiliated with the currently “running” E7 software.
Downloaded indicates the E7 OLT was instructed to download the ONT image to the
corresponding ONTs. For ONT images that are bundled with the E7 software, this
happens automatically. When performing an ONT-only upgrade, you must initiate this
action.
Activated indicates the E7 OLT was instructed to activate the ONT image that was
previously downloaded on the corresponding ONTs. When this is “Y”, then the
corresponding ONTs shown are running that version of the image.
Committed indicates the E7 OLT was instructed to commit the ONT image that was
previously activated on the corresponding ONTs. When this is “Y”, the corresponding
ONTs have this image as the default version.
Note: When an image is “Activated” but not “Committed”, then if the ONT reboots,
the ONT will initially fall back to its previous image. Committing the release for a single
ONT upgrade is not valid, as this is a temporary state.
Resetting an ONT to the Factory Default
The E7 GPON ONT buttset master reset procedure returns the ONT settings to the factory
default.
Another feature of Smart Activate is the ability for the technician or service provider to
restore the ONT to the factory state through the “Factory Reset” page.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
256
To reset the ONT to factory default
1. Disconnect power to the ONT.
2. Disconnect the network fiber (pigtail) from the ONT.
3. Connect an RJ-11 terminated buttset to the first (LINE ONE) voice port on the ONT.
Note: For buttset devices using alligator clips, back-out the Tip and Ring screws and clip
the buttset leads to the T and R posts (black to Tip, red to Ring).Verify that the network
fiber is disconnected from the ONT.
4. Reapply power to the ONT.
5. For 700G or 700GX ONTs, listen to the buttset and wait until you hear a click sound
(approximately 10 seconds for SFU ONTs or 15-20 seconds for MDU ONTs).
6. For 700GE ONTs, wait for the OFF HOOK LED on the ONT to start blinking
(approximately 50 seconds for 2 POTS ONTs, 60 seconds for 4 POTS ONTs).
Note: If digits are entered prior to the ONT being ready (click sound or OFF HOOK
Blink), those digits are ignored.
7. Press "*", "*", "*" and "#" (star, star, star, pound) keys on the buttset key pad. The
buttset sounds DTMF tones as the keys are pressed.
8. A voice prompts to acknowledge your selection of requesting an ONT master reset.
9. After the confirmation prompt, press '1' to confirm the reset. A voice prompt replies,
"ONT Master Reset is completed".
10. Press '0' to abort. A voice prompt replies, "ONT Master Reset is cancelled".
11. Continue entering new RONTA commands as required.
12. Re-connect the network fiber to the ONT and wait for the ONT to come on line.
To restore the ONT to the factory state through Smart Activate
1. From the Factory Reset” page, click the "Check here to confirm the factory reset"
checkbox to confirm the intent to reset the ONT.
2. click Reset to return the ONT to a factory default condition.
Adding PON Upstream CoS Profiles to an ONT
This topic describes how to select previously-created PON Upstream CoS profiles and map
them to a either a Calix GE or T-series ONT. From the E7 system Profile menu, you can
create a collection of E7 PON Upstream CoS profiles that can be added to individual ONTs
by mapping them to "user CoS" for then applying to an Ethernet service on the ONT.


See Creating a PON Upstream Class of Service Profile (on page 124).
See GPON QoS (on page 117).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
257
To add PON upstream CoS profiles to GE ONT
1. From the Navigation Tree, click ONTs.
2. In the Work Area, click Provisioned ONTs > PON Upstream CoS > Create.
3. In the Create ONT PON Upstream CoS dialog, do the following:
a. In the ID list, select the index value for mapping a PON upstream CoS profile. (For
example, selecting 1 will map the profile to user-1.)
b. In the PON Upstream CoS Profile list, select the profile that you want to map to the
index you selected in Step a.
c. Click Create.
4. When adding an Ethernet service to an ONT, you can select the PON CoS profile that is
mapped to user 1-4, among other choices.
For CLI:
add ont-pon-us-cos <user-id> to-ont <ont-id> pon-us-cos-profile <pname>
remove ont-pon-us-cos <user-id> from-ont <ont-id>
Applying an ONT Template
This topic shows you how to apply an ONT template that was previously created through
CMS R12.1 or later. By default, the system already has defined standard profiles (indexes 101
and above) for a series of Calix ONTs. Up to 50 custom ONT profiles can be created.
Note: ONT templates can be shared between AE and GPON ONTs.
To apply an ONT template
1. On the CMS Navigation Tree, click ONTs for the E7 node you want to configure.
2. In the Work Area, click the ONT ID for the ONT of which you want to configure.
3. In the menu, click Action > Apply Template to ONT.
4. In the Apply Template dialog, select the template to apply from the Template list.
5. Click Apply.
Configuring an ONT Ethernet Port
This topic describes how to configure an ONT Ethernet port for service.
Note: See Calix Home Gateway Services (on page 28) for an overview on the Home Gateway
(HG) modes and configuration.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
258
Note: If upon turnup of an 836GE or GigaCenter ONT, a CPE (STB) is attached to an
ONT Ethernet port that is a member of an RG interface group, it would obtain a lease from
the embedded DHCP server. Then, if the ONT Ethernet port is subsequently made a
member of an FB interface group, the CPE retains the IP address.
ONT Template in CMS
Using CMS R12.1 or later, you can create an ONT template that defines all of the key
management aspects of a Home Gateway ONT as well as the logical assignments of physical
GE ports for the initial setup. Once the template is created, you can apply it to the applicable
ONT.
Maximum Transmission Unit
The Maximum Transmission Unit (MTU) is a fixed value (read only) for an ONT Ethernet
port and depends on the configured ONT:


700GX ONT Ethernet interfaces support a fixed 1600 byte MTU
76xGX and 700GE ONT Ethernet interfaces support a fixed 2000 byte MTU
Parameters
You can provision the following parameters for an ONT Ethernet port:
Parameter
Admin State
Description
Administrative state of the port.
Note: For Ethernet ports that are members of an RG interface, the Admin State
parameter is irrelevant, as the RG is considered under the control of the
subscriber, not the service provider.
Valid Options
Enabled
Enabled-no-alarms ‡
Disabled
Subscriber ID
Subscriber ID information, such as name, address, or account number.
String up to 27 characters
(blank) ‡
Description
Optional description field for the port or service.
String up to 27 characters
(blank) ‡
DSCP/IP
Precedence Map
Name of DSCP or IP-precedence to P-bit map to use on ingress. There are
system-default profiles named "access" that you can use or you can create
custom profiles and assign them to the interface.
Any previously-created
map, or the system-default
map
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
259
Parameter
Interface
Description
Valid Options
(Home Gateway ONTs only) Whether the ONT Ethernet port is assigned to an
Residential Gateway (RG) 'G1' in CLI, Full-Bridge (FB) 'F1' in CLI, or not a
member of either, allowing it to operate as a normal L2 classic port (Half-Bridge
mode).
FB, RG, blank selects halfbridge
Residential Gateway (RG) Mode
The RG services are named as Gateway Services, where only four services are
supported with only one of them can have a multicast profile assignment. The
ONT RG interface supports up to 4 services.
Full-Bridge (FB) Mode
(P-series only) With Full-Bridge mode, traffic can pass between LAN ports
within the same bridge.
Support of Full-Bridge is assumed to be for video multicast services only to
enable Whole-Home DVR support, allowing communication between set-top
boxes. A single multicast VLAN can be associated to the Full-Bridge group.
Applications that require Full-Bridge support of IPTV enabled devices along
with media-clients with a single IP Host supporting data and unicast
applications requires an auxiliary switch be installed behind the LAN port and
continued support of Half-Bridge. The ONT Full-Bridge interface only supports 1
service.
Half-Bridge (HB or Classic) Mode
In Half-Bridge mode, the port operates as a normal L2 classic port. This
operation allows traffic to only pass between the WAN and LAN ports and
restricts traffic from passing between LAN ports within the same bridge.
When an 836 RSG or GigaCenter ONT is created on the E7, all ONT
Ethernet ports are assigned as members of the RG port. Ports can be removed
from the RG group, and possibly added to the FB interface group.
When a 700GE or T-series ONT is created on the E7, the ONT Ethernet
ports are not a member of a HGW interface group, and can be added to an
interface group. The 700GE resets whenever it transitions into or out of RG
mode. For example, when the first ONT Ethernet port is added to the RG group
on a 700GE ONT, the ONT resets. Similarly, when the last Ethernet port is
removed from the RG group, the ONT resets.
Note: For Ethernet ports that are members of an RG interface, the following
parameters are irrelevant, as the RG is considered under the control of the
subscriber, not the service provider: Admin State, Disable on Battery, Speed,
Duplex.
Speed
Data rate of the Ethernet port in Mb/s.
HPNA ports default to 100 Mb/s and cannot be changed.
FE ports default to auto but can be changed to 10 and 100 Mb/s. GE ports can
be changed to 1000.
auto ‡
10
100
1000
Note: For Ethernet ports that are members of an RG interface, the Speed
parameter is irrelevant, as the RG is considered under the control of the
subscriber, not the service provider.
Duplex
Duplex mode for an Ethernet port. HPNA ports default to half-duplex and
cannot be changed. FE ports default to duplex and cannot be changed.
Full ‡
Half
Note: For Ethernet ports that are members of an RG interface, the Duplex
parameter is irrelevant, as the RG is considered under the control of the
subscriber, not the service provider.
Link OAM Events
Whether to enable link Operation, Administration and Maintenance (OAM)
event monitoring.
unselected (disabled) ‡
selected (enabled)
GoS
Grade of Service (GOS) profile number to use on this port.
(select from list)
(blank) ‡
Disable on Battery
Port operational state when the ONT is operating on battery backup power
(during a power outage).
unselected (No) ‡
selected (Yes)
Note: For Ethernet ports that are members of an RG interface, the Disable on
Battery parameter is irrelevant, as the RG is considered under the control of the
subscriber, not the service provider.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
260
Parameter
Description
Valid Options
Security Profile
Name of Security Profile to use.
system-default ‡
Text string
Accept Link OAM
Loopback
Sets the ONT Ethernet port to either accept or reject a received request in the
form of an 802.3ah frame that is sent by a host, requesting that the receiving
host put its port into loopback.
unselected (No) ‡
selected (Yes)
DHCP Limit
Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable vCMTS)
to allow an override of the DHCP Lease Limit specified in a security profile
applied to a port. This allows the same security profile to be reused and also
allows the required DOCSIS provisioning where the lease limit is specified
individually on the port on which the new service will be added. See the Calix
Open Link Cable vCMTS Command-Line Interface (CLI) Reference Guide and
Calix Open Link Cable vCMTS SNMP Management Guide for more information.
None ‡
No Limit
Enter Value (0-255)
‡ Default
To configure an ONT Ethernet port for service
1. On the Navigation Tree, click ONTS.
2. In the Work Area, click Provisioned ONTS > Ports to display the ONT ports.
3. From the list of ONT ports, click an ONT Ethernet port.
Note: The appropriate number of ports specific to a given model of ONT are
automatically populated on the provisioning page.
4. Reference the table above to configure the parameters.
5. From the menu, click Apply to save changes.
For CLI:

enable ont-port <ont port ID> where port ID format is <ont-id/ont-port>
and where g=gig-eth, f=fast-eth, h=hpna-eth. Example: 10001/f2.

add ont-port <ont-port> to-res-gw

add ont-port <ont-port> to-full-bridge


set ont-port <port> eth-svc [bw-profile|svc-tag-action|outervlan|inner-vlan|mcast-profile|description|admin-state]
show ont-port [detail|fast-eth|gig-eth|hpna-eth]
Configuring an ONT Voice Port
This topic describes how to configure an ONT Voice (POTS) port for service.
Note: For International deployments, the Caller ID protocol, Caller ID Alert Signal, VMWI
alert Signal, and POTS Loss Plan Values are provisionable based on the host country. Refer
to the Calix Application Note: Using 700 ONT VoIP Configuration File for specific International
Dialing parameters.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
261
Parameters
You can provision the following parameters for an ONT Voice port:
Parameter
Description
Valid Options
Admin State
Administrative state of the ONT POTS port.
Enabled ‡
Enabled-no-alarms
Disabled
Subscriber ID
Subscriber ID information, such as phone number, or
account number.
String up to 27 characters
(blank) ‡
Description
Optional description field for the port, subscriber
address, name, or service.
String up to 27 characters
(blank) ‡
Impedance
Impedance in ohms.
For P-series: 600 ‡, 900
The T-series supports setting values via a
configuration file:
For T-series:600 ‡, 900, etsi
Signal Type
System Tx Loss Plan

600 C1=150 nF, R1=750 Ohm, R2=270 Ohm

900 C1=115 nF, R1=820 Ohm, R2=220 Ohm

etsi C1=230 nF, R1=1050 Ohm, R2=320 Ohm)
Signal type for the POTS line.
loop-start ‡, ground-start

Ground start is a signaling technique used to
produce dial tone by momentarily grounding one
side of a two-wire circuit. The ring side of a wire
pair is usually the side that is grounded. Ground
start signaling is often used for telephone lines
connected to a PBX as well as by many older pay
phones. Both SIP and C7 TDM gateway-based
VoIP services support ground start. Ground start
service is not supported for H.248 VoIP service.
T-series supports setting values
via a configuration file.

Loop start (i.e. POTS) is the alternative to ground
start.
System transmit (tx) loss plan for POTS (voice) line
provides attenuation settings, according to various
standards, to reduce the perception of noise and echo
on the line.

GR-909 loss plan (less attenuation of -2 dB –
higher signal level) is more compatible with GR303 type phone systems.

ANSI loss plan (more attenuation of -3 dB – lower
signal level) is more compatible with American
VoIP type phone systems.

ETSI-pstn loss plan (more attenuation of -4 dB lowest signal level) is more compatible with
European VoIP type phone systems.

Manual loss plan allows you to set the transmit
gain from the range -12.0 to 6.0 dB.
gr-909, ansi ‡, etsi-pstn, manual
Note: The TX and RX loss plan settings must match.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
262
Parameter
System Rx Loss
Plan
Description
Valid Options
System receive (rx) loss plan for POTS (voice) line
provides attenuation settings, according to various
standards, to reduce the perception of noise and echo
on the line.
gr-909, ansi ‡, etsi-pstn, manual

GR-909 loss plan (less attenuation of -4 dB –
higher signal level) is more compatible with GR303 type phone systems.

ANSI loss plan (more attenuation of -9 dB – lower
signal level) is more compatible with American
VoIP type phone systems.

ETSI-pstn loss plan (more attenuation of -11 dB lowest signal level) is more compatible with
European VoIP type phone systems.

Manual loss plan allows you to set the receive
gain from the range -12.0 to 6.0 dB.
Note: The TX and RX loss plan settings must match.
Transmit Gain
Transmit gain for a voice port.
Note: This attribute is in effect only when the System
Tx Loss Plan is set to manual.
Receive Gain
Receive gain for a voice port.
Note: This attribute is in effect only when the System
Rx Loss Plan is set to manual.
-12.0 to 6.0 dB
0‡
-12.0 to 6.0 dB
0‡
‡ Default
To configure an ONT Voice (POTS) port for service
1. On the Navigation Tree, click ONTS.
2. In the Work Area, click the Provisioned ONTS > Ports to display the ONT ports.
3. From the top of the Work Area, use the ONT drop-down list
select the ONT on which to add the service.
4. From the list of ONT ports, click a Voice port.
5. Reference the table above to configure the parameters.
6. From the menu, click Apply to save changes.
For CLI:

set ont-port <port>

show ont-port
Configuring an ONT Residential Gateway Interface
This topic describes how to configure an ONT Residential Gateway (RG) interface for
service. This operation only applies to ONTs that support Home Gateway Services.
Note: See the Calix P-Series Home Gateway User's Guide for information on saving and
retrieving an 836GE configuration file and TR-069 settings.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
to
263
ONT Template in CMS
Using CMS R12.1 or later, you can create an ONT template that defines all of the key
management aspects of a Home Gateway ONT as well as the logical assignments of physical
GE ports for the initial setup and whether the RG configuration supports Native Mode
versus External Mode. Once the template is created, you can apply it to the applicable ONT.
Configuration guidelines









Native mode is the default for all P-Series Home Gateway and GigaCenter ONTs. TSeries ONTs do not support Native mode as an option for the Management Mode.
For Ethernet ports that are members of an RG interface, the following parameters are
irrelevant, as the RG is considered under the control of the subscriber, not the service
provider: Admin State, Disable on Battery, Speed, Duplex.
With the Native management mode, you can provision the following:

Create up to 4 RG WAN interfaces.

Specify the RG WAN interface protocol: IPoE DHCP, IPoE static, and PPPoE.
(WAN protocol is only configurable on the RG WAN interface associated with the
Ethernet service Data1. RG WAN interface for the Ethernet services Data2, Data3,
and Data4 are DHCP only.)

Enable IGMP on a single RG WAN interface (video service)

Enable MVR on a single RG WAN interface (video service)
In the N:1 VLAN model, all RG WAN interfaces are on the same VLAN.
In the 1:1 VLAN model, each RG WAN interface is uniquely identified by a VLAN.
Typically, 1:1 VLANs are double-tagged, but, single-tagged VLANs are also supported.
When an 836 RSG, 844G, or 854G ONT is created on the E7, all ONT Ethernet ports
are assigned as members of the RG port. Ports can be removed from the RG group, and
possibly added to the FB interface group.
When a 700GE ONT is created on the E7, the ONT Ethernet ports are not a member of
the RG or FB interface group, and can be added to either the RG or FB interface group.
The 700GE resets whenever it transitions into or out of RG mode. For example, the
ONT resets when the first ONT Ethernet port is added to the RG group on a 700GE
ONT, or when the last Ethernet port is removed from the RG group. Also, when the
RG Interface on an 700GE is enabled or disabled, the ONT resets.
When a T-Series ONT is created on the E7, the ONT Ethernet ports are not a member
of the RG interface group, and can only be added to the RG interface group. The FB
interface group is not supported.
HGWs provide an Embedded Web Interface (EWI) that is accessed locally or remotely
using a web browser. The remote management account allows the service provider to
have remote access over the WAN interface. It is important to note that the Remote
Management account interface access is disabled by default. See HGW Management
Interfaces (on page 37) for instructions on accessing the HGW EWI.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
264
Note: See Example: Multicast IPTV over L2 Bridge Wi-Fi (on page 389) for information on
configuring an L2 Bridge object on GigaCenter ONTs.
Parameters
You can provision the following parameters for an ONT RG interface:
Parameter
Admin State
Description
Administrative state of the port.
When the RG Interface on an 700GE is enabled or disabled, the ONT resets.
Valid Options
Enabled
Enabled-no-alarms ‡
Disabled
Subscriber ID
Subscriber ID information, such as name, address, or account number
String up to 27 characters
(blank) ‡
Description
Optional description field for the port or service
String up to 27 characters
(blank) ‡
Management Mode
Management Mode of RG port.
native ‡, external

Native (P-series only) management is the default behavior allows the
CMS/E7 to directly provision the RG WAN interface. This mode is limited to
a single VLAN (service) on the RG WAN interface. However, voice and
legacy L2 services are still natively supported for non-RG ports. Note: TSeries ONTs do not support Native Mode as an option for the Management
Mode.

External management uses an RG configuration file that is downloaded to
the ONT to fully manage the RG function. In this mode, the CMS/E7 do not
provision the RG WAN interface.
Note: When management mode = External, you must set a config-fileinstance value.
Config File Instance
Identifier for the external RG configuration file to use.

For P-series, this option only appears if Management Mode = External.

For T-series, this is a required field, and "none" does not apply.
none ‡, rg1-8, enter value
Instances 17 through 24 are used exclusively for RG configuration file and can
be specified either by the instance number alone or by “rg-<1 through 8>”
WAN Protocol

rg-1
- Instance for RG (17)

rg-2
- Instance for RG (18)

rg-3
- Instance for RG (19)

rg-4
- Instance for RG (20)

rg-5
- Instance for RG (21)

rg-6
- Instance for RG (22)

rg-7
- Instance for RG (23)

rg-8
- Instance for RG (24)
(Only for P-series when Management Mode = Native)
WAN Protocol for RG Interface in Native Management Mode.

static allows you to enter static-ip, static-ip-mask, static-ip-gateway.

pppoe allows you to enter pppoe-username, and pppoe password. 31character text string
dhcp ‡, static, pppoe
Management
Profile
Name of RG management profile for TR-069 that allows you to configure
common ACS-related parameters, and how the TR-069 management channel
is setup (in-band or out-of-band).
Any previously-created
profile, or the systemdefault profile
TR-069 Eth Service
(Only for P-series when Management Mode = Native) Name or index of the
Ethernet service for inband TR-069 management. This is a text string.
Gateway Service:1-4
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
265
Parameter
Disable on Battery
Description
Port operational state when the ONT is operating on battery backup power
(during a power outage). This setting applies to all the Ethernet ports that are
members of the RG interface, as follows:

Disable the eth ports that are members of the RG

Disable wifi

Disable USB
Valid Options
unselected (No) ‡
selected (Yes)
DSCP/IP
Precedence Map
Name of DSCP or IP-precedence to P-bit map to use on ingress. There are
system-default profiles named "access" that you can use or you can create
custom profiles and assign them to the interface.
Any previously-created
map, or the system-default
map
Set Remote Access
Time (s)
The Home Gateway (HGW) Embedded Web Interface (EWI) on HGW ONTs
supports two levels of access: Administrator account, which provides the
subscriber local access, and Remote Management account, which allows the
service provider to have remote access over the WAN interface. For example,
an administrator at the data center Telnets to the HGW to enable Remote
Management access to its EWI. It is important to note that the Remote
Management account interface access is disabled by default. This parameter
sets the length of time you can remotely access the HGW EWI in minutes.
0-1440

See HGW Management Interfaces (on page 37) for instructions on
accessing the HGW EWI.

Note: The administrator account is not supported on the WAN side for PSeries ONTs.
‡ Default
To configure an ONT RG interface
1. On the Navigation Tree, click ONTS.
2. In the Work Area, click Provisioned ONTS > Ports to display the ONT ports.
3. At the top of the Work Area, use the drop-down ONT list to select the ONT of which
to configure.
4. From the list of ONT ports, click the RG interface.
5. Reference the table above to configure the parameters.
6. From the menu, click Apply to save changes.
For CLI:
set ont-port
To remotely access the Home Gateway (HGW) Embedded Web Interface
1. Enable the remote user interface for a specified time.
a. On the Navigation Tree, expand the ONT, and then click RG 1.
b. In the Set Remote Access Time box, enter the amount of time to enable remote
access (up to 1400 minutes/1 day), and then click Apply.
 For CLI: set ont-port <port-id> remote-access-time <minutes-value>
At this point the remote interface is accessible through the IP address of the RG
WAN interface.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
266
2. Find the WAN interface IP address:

In the RG WAN Interface Status area, scroll to the right portion of the window
to view the IP address.

For CLI: show
ont-port <id> details
(not supported for T-Series)
3. Launch a web browser and enter the WAN interface IP address, followed by the
remote access port:

P-Series example: http://10.10.200.157:8080
username / password (836GE): support / support
username / password (700GE): admin / admin

T-Series example: https:// 10.45.10.155:309
username / password: SuperAdmin / SuperAdmin
Note: The P-Series default login credentials are stored in the applied RG configuration
file, and can be modified through the EWI, Consumer-Connect (TR-069), or by loading
another RG configuration file with modifications. To modify these default values for a TSeries RG configuration file, contact Calix Technical Support for assistance. The T-Series
ONTs support RG remote access with releases E7 R2.3.20 and T-Series R4.1.38 and
above.
For complete information on connecting to HGWs, see:


P-Series Home Gateway User Guide
T-Series Operation and Maintenance Guide (if applicable)
Configuring an ONT Full Bridge Interface
This topic describes how to configure an ONT Full Bridge (FB) interface for service. This
operation only applies to ONTs that support Home Gateway Services, such as 836GE RSG,
and 700GE.
The Full Bridge interface is intended for Whole-Home DVR deployments that enables the
user to bridge multiple LAN side interfaces to a logical WAN interface. This allows video
ports on these LAN devices to communicate on the local area network without needing to
access the WAN.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
267
Configuration guidelines












The Full Bridge operation only supports N:1 VLAN model on the E7. This limits the
service-tag actions to the following:

add-tag when the subscriber ports are untagged

change-tag when the subscriber ports are tagged
When the video profile is assigned to the L2 bridge, a single IGMP Snoop function
manages the multicast flows across all Half-Bridge ports or across the Full Bridge group.
When the video profile is assigned to the Routed WAN interface using Home Gateway,
it supports both IGMP Snoop and Proxy.
The Home Gateway supports IPTV services for up to 16 set-top boxes or media clients
connected behind the LAN ports with up to 40 service flows per ONT.
The DHCP lease limit, that is specified in the Security Profile, applies to all of the ports
in the Full Bridge group.
The IGMP limit, that is specified in the multicast profile maximum streams, applies to all
of the ports in the Full Bridge group.
The Full Bridge service can be provisioned with MAC forced-forwarding, IPSV, and
DHCP snooping.
Full bridge interfaces are not supported on 760GX ONTs.
Bridging HPNA ports on 712GE/722GE ONTs is not currently supported.
Only 1 Full Bridge supported per ONT.
ONT Ethernet ports are added to the Full Bridge Interface (FB-1 in web browser
interface, F1 in CLI).
Add Video service to the Full Bridge port.
Note: See Example: Multicast IPTV over L2 Bridge Wi-Fi (on page 389) for information on
configuring an L2 Bridge object on GigaCenter ONTs.
Parameters
You can provision the following parameters for a full bridge interface:
Parameter
Description
Valid Options
Admin State
Administrative state of the port.
Enabled
Enabled-no-alarms ‡
Disabled
Subscriber ID
Subscriber ID information, such as name, address, or account number
String up to 27 characters
(blank) ‡
Description
Optional description field for the port or service
String up to 27 characters
(blank) ‡
Security Profile
Name of Security Profile to use.
Text string
system-default ‡
DSCP/IP
Precedence Map
Name of DSCP or IP-precedence to P-bit map to use on ingress. There are
system-default profiles named "access" that you can use or you can create
custom profiles and assign them to the interface.
Any previously-created
map, or the system-default
map
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
268
To configure an ONT full bridge interface
1. On the Navigation Tree, click ONTS.
2. In the Work Area, click Provisioned ONTS > Ports to display the ONT ports.
3. At the top of the Work Area, use the drop-down ONT list to select the ONT of which
to configure.
4. From the list of ONT ports, click the full bridge interface.
5. Reference the table above to configure the parameters.
6. From the menu, click Apply to save changes.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
269
Step 4. Configure Subscriber Services
This section describes how to configure various GPON services, using the previously-created
profiles and configured uplinks.

For overviews of subscriber services provisioning steps with links to supporting
procedure topics, see:
Service Provisioning Overviews (on page 41)
Topics Covered
This section covers the following topics in bold that are part of the overall GPON services
configuration process:
Step 1. Configure network uplinks for GPON services
Step 2. Creating system profiles that support GPON applications
Step 3. Configure a PON
Step 4. Configure subscriber services

Configuring Data Services

Configuring IP Video Services

Configuring Voice Services

Configuring RF Overlay Video Services

Configuring T1/E1 Services
Note: For information on configuring a set of Operation, Administration, and Maintenance
(OAM) funtions that monitor network operation, detect and localize network faults, and
provide a measure of network performance, see "Configuring Etherent OAM" in the Calix
E7 Maintenance and Troubleshooting Guide.
Configuring Data Services
This section describes how to create data services on E7 GPON ONTs.
Topics Covered
This section covers the following topics in bold that are the last step of the overall GPON
services configuration process. The procedures in this section assume that you have
completed the processes in steps 1, 2, 3.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
270
Step 1. Configure network uplinks for GPON services (on page 66)
Step 2. Create system profiles that support GPON applications (on page 110)
Step 3. Configure a PON (on page 231)
Step 4. Configure data subscriber services

Creating an L2 Data Service

Creating Gateway Data and Video Services

Adding Static IP Host Addresses and Subnets

Configuring PPPoE Operation for Data Service
Related Topics
For guidance in filling in the provisioning forms necessary to configure data services, see:

Example Data Services Provisioning (on page 373)
For overviews of provisioning sequences where the steps in the overviews are linked to
supporting procedure topics, see:

Service Provisioning Overviews (on page 41)
Overview: Adding a GPON Data Service
The E7 provides data interconnection between Internet service providers and subscribers via
the Calix GPON ONTs. Service profiles and service tag actions in the E7 and ONT help
provide tiered service offerings by specifying the classifying and marking of packets from the
subscriber port into the service VLAN.
The Calix E7 supports the following data service models over IP on Calix GPON ONTs.
This section describes the data service configuration process.

N:1/VLAN-per-service model: Defines broadcast domains that optimize traffic flow in
larger networks, providing many-to-one (N:1) subscriber-to-service connectivity. The
traffic frames for each type of service is assigned a unique VLAN ID (tag). An additional
tag can be added to limit the size of a group for improved reliability. A service carried on
an N:1 VLAN applies to multiple subscriber ports, allowing a single match list and tag
action to be used to denote the service.
Note: If using a N:1 VLAN model for services, Calix recommends enabling MAC
Forced Forwarding (MAC FF) and IP Source Verify (IPSV) when creating the VLAN,
where appropriate. The VLAN Per Service model is susceptible to MAC spoofing unless
MACFF and IPSV are enabled.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
271

1:1/VLAN-per-port model: (Calix recommended model) Breaks large LANs into
smaller parts, providing one-to-one (1:1) subscriber-to-service connectivity. The traffic
frames from each subscriber port is assigned a unique VLAN ID (tag). The tag is applied
to a frame before the traffic is aggregated for transport. An additional tag can also be
added to group subscriber ports in logical categories.
A service carried on a 1:1 VLAN is the same for each subscriber, except the customer tag
is unique per subscriber. You can define the match list and tag action pair such that
multiple subscriber ports can reference it. This is accomplished by assigning an attribute
for the output tag in the tag action that indicates the value of the output tag is subscriber
specific. The customer specific tag is included in the service definition when provisioning
the service.
For guidance in filling in the provisioning forms necessary to configure data services, see:



Example: Data Services Provisioning (on page 373)
Example: HGW Service - P-Series Native Mode (on page 413)
Example: HGW Service - P-Series External Mode (on page 380)
Creating a Subscriber Service

Form view shows an expandable structure that allows you to create multiple
instances of different service types, by scrolling to selected ports on the ONT.

Table view shows the services currently provisioned on the selected ONT, and
allows you to create a single service of the selected type.
Information you need
You must have the names of the following objects to configure an ONT data service:


Ethernet bandwidth profile (on page 167)
Service-tag action ID (on page 131)


Output Outer Tag or Inner Tag (if referenced as "Specified in Service" in the servicetag action)
PON CoS (on page 124) (optional)
Creating an L2 Data Service
This topic describes how to add an individual data service on a Layer-2 ONT GE port, using
a Table view to first survey the services currently provisioned on any ONT configured in the
E7 system.
The Calix E7 also supports a subscriber services activation Form where you can add any
possible service for any ONT configured in the E7 system.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
272

For an outline of the entire process of provisioning a data service, see:
Overview: GPON Data Services (on page 42)

For guidance in filling in the provisioning forms necessary to configure video services,
see:
Example Data Services Provisioning (on page 350)
Transparent LAN data services
A Transparent LAN (TLAN) service can be configured where a common outer tag is added
to all ports in the TLAN. The provisioning is similar to the VLAN-per-service data services
model, with the following details:



VLAN must have IGMP mode set to flood (no snooping).
Interfaces at each end of the TLAN:

Split-horizon forwarding is disabled.

Role is designated as an edge link.

RSTP Enabled is set to tunneled.

LACP Tunnel is set to Yes.
Add the data service to the ONT Ethernet port, specifying a service VLAN in the Out
Tag parameter that is unique to the Transparent LAN (TLAN).
Note: The default behavior for data services is to filter all multicast traffic upstream from
an ONT Ethernet port, unless the PON TLAN parameter is enabled on the VLAN.

Associate a service-tag action that includes the following:

A selection of Add Tag for the Tag Action parameter

A selection of Specified in Service for the Outer Tag parameter

A match list association where there are two match rule entries to match all traffic, if
desired:

Untagged rule with the selection of ignore for the Source MAC parameter and
none for the Source MAC Mask parameter to match all untagged frames

Tagged rule with the selection of ignore for the Outer Tag parameter and pbitnone for the Outer P-Bit parameter to match all tagged frames
Note: The upstream and downstream values specified in the Ethernet Bandwidth Profile and
P-bit values defined in the service-tag action must be consistent with the class of service type
as defined in the global CoS table. See Creating Traffic Management Profiles (on page 116) or
"Ethernet Traffic Management" in the Calix E7 Engineering and Planning Guide.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
273
Information you need
You must have the following information on hand to configure an ONT data service:



Ethernet bandwidth profile
Service tag action ID
PON CoS (optionally)
Parameters
You can provision the following data service parameters accessed from the Services page:
Parameter
Description
Valid Options
Subscriber Port
Subscriber Port*
System address of the ONT port where the subscriber services will be
provisioned.
Any ONT GE port
Note: For HGW ONTs, the GE port must NOT be a member of an L3
interface to allow the port to operate as a normal L2 classic port (HalfBridge mode).
Subscriber ID
Subscriber ID information, such as phone number, or account number.
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
String up to 27 characters
(blank) ‡
Description
Optional description field for the port, subscriber address, name, or
service. If you leave this box empty, the E7 copies the Description entry
from the ONT provisioning record to this field.
String up to 27 characters
(blank) ‡
Create Data Service
Service Name*
Name of service for the ONT port to use.
Data1 ... Data8
BW Profile*
Name of previously-created Ethernet bandwidth profile to apply to this
port.
Any established
bandwidth profile
PON CoS
Class of Service instance to apply to the service.
derived, user-1, user-2,
user-3, user-4, cos-1, cos2, cos-3, cos-4, fixed

derived option has incoming frames mapped to cos-1 to 4 (T-CONT
types) based on the P-Bit value indicated in the associated servicetag action.

cos 1-4 options represent standard T-CONT types with default PON
CoS forwarding types. Incoming frames are mapped to the T-CONT
type specified (cos-1 to 4).

user 1-4 options represent user-defined T-CONT types that can be
configured with any traffic class forwarding type. For compatible
ONTs, this allows multiple services with the same traffic class to be
carried by separate T-CONTs on the PON. Incoming frames are
mapped to the T-CONT type specified (user-1 to 4).

fixed represents the GPON QoS behavior and features prior to
R2.2, and is intended for backwards compatibility with those earlierprovisioned services.
See Selecting PON CoS (on page 279) for details on the PON CoS
options.
See GPON QoS (on page 117) for an overview of how the system
supports prioritized upstream service flows.
Upstream Peak Rate
Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
274
Parameter
Description
Upstream Committed
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Downstream Peak
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Service Tag Action*
Name of service tag action or "none" for no service tag action.
index-name of tag action
S-VLAN (Outer Tag)
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
Note: The default behavior for data services is to filter all multicast
traffic upstream from an ONT Ethernet port, unless the PON TLAN
parameter is enabled on the VLAN.
C-VLAN (Inner Tag)
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
Valid Options
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
*Required fields
‡ Default
To create a data service
1. On the Navigation Tree, click ONTS.
2. In the Work Area, click Provisioned ONTS > Services > Table.
3. From the top of the Work Area, use the ONT drop-down list to select the ONT on
which to add the service.
4. From the menu, click Create > Data Service to open the Create dialog box.
5. Reference the table above to configure the parameters.
6. Click Create to activate a data service on the subscriber port.
For CLI:



add eth-svc <service name> to-ont-port <ONT port> bw-profile <bw
profile name> svc-tag-action <tag-action name> [outer-vlan <vlan ID>
inner-vlan <vlan ID> mcast-profile <profile name> description
<service> pon-cos <us-cos> admin-state [enabled|disabled]
set ont-port <port> eth-svc [bw-profile|svc-tag-action|outervlan|inner-vlan|description|admin-state]
show ont-port
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
275
Related topics




Creating an Ethernet Bandwidth Profile (on page 167)
GPON QoS (on page 117)
Creating a Service Match List and Rules (on page 127)
Creating Service-Tag Actions (on page 131)
Creating Gateway Data and Video Service with Form View
This topic describes how to configure Gateway data and video services on an Residential
Gateway (RG) interface, using a subscriber services form where you can provision any
possible service for any ONT configured in the E7 system.
Optionally, you can add an individual gateway service, using a Table view to first survey the
services currently provisioned on any ONT configured in the E7 system.

For an outline of the entire process of provisioning video service, see:
Overview: HGW Applications - External Mode (on page 48)

For guidance in filling in the provisioning forms necessary to configure gateway services,
see:
HGW Service - External Mode Example (on page 380)
Note: The upstream and downstream values specified in the Ethernet Bandwidth Profile and
P-bit values defined in the service-tag action must be consistent with the class of service type
as defined in the global CoS table. See Creating Traffic Management Profiles (on page 116) or
"Ethernet Traffic Management" in the Calix E7 Engineering and Planning Guide.
Parameters
You can provision the following parameters for video service on an ONT Ethernet port:
Parameter
Subscriber ID
Description
Subscriber ID information, such as phone number, or account number.
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
Description
Optional description field for the port, subscriber address, name, or
service.
If you leave this box empty, the E7 copies the Description entry from the
ONT provisioning record to this field.
Valid Options
String up to 27
characters
(blank) ‡
String up to 27
characters
(blank) ‡
Management Profile
Name of RG management profile for TR-069 that allows you to
configure common ACS-related parameters, and how the TR-069
management channel is setup (in-band or out-of-band).
Any established RG
management profile
TR-069 Eth Service
(P-series only) When the the TR-069 client is configured to for
Management mode = In-band in the RG Management Profile, the client
runs on an existing RG WAN interface. Typically, the path to the ACS
server utilizes an existing RG service such as Gateway Service: 1 (for
example, a HSI service).
Gateway Service:1-4
Multicast Profile*
Name of Ethernet multicast profile to apply to this port.
Any established
multicast profile
BW Profile*
Name of Ethernet bandwidth profile to apply to this port.
Any established
bandwidth profile
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
276
Parameter
PON CoS
Description
Class of Service instance to apply to the service.

derived option has incoming frames mapped to cos-1 to 4 (T-CONT
types) based on the P-Bit value indicated in the associated servicetag action.

cos 1-4 options represent standard T-CONT types with default PON
CoS forwarding types. Incoming frames are mapped to the T-CONT
type specified (cos-1 to 4).

user 1-4 options represent user-defined T-CONT types that can be
configured with any traffic class forwarding type. For compatible
ONTs, this allows multiple services with the same traffic class to be
carried by separate T-CONTs on the PON. Incoming frames are
mapped to the T-CONT type specified (user-1 to 4). Note: If you
want to apply a user-defined PON Upstream CoS profile, it must
have been previously mapped to the ONT for it to be available for
selection in this step. If necessary, see Adding PON Upstream CoS
Profiles to an ONT (on page 256).

fixed represents the GPON QoS behavior and features prior to
R2.2, and is intended for backwards compatibility with those earlierprovisioned services.
Valid Options
derived, user-1, user-2,
user-3, user-4, cos-1,
cos-2, cos-3, cos-4, fixed
See Selecting PON CoS (on page 279) for details on the PON CoS
options.
See GPON QoS (on page 117) for an overview of how the system
supports prioritized upstream service flows.
Upstream Peak Rate
Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Upstream Committed
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Downstream Peak
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Tag Action*
Name of service tag action to apply to the service.
Any established tag
action
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
277
Parameter
Description
S-VLAN (Outer Tag)
If the associated service-tag action indicates "Specified in Service" for
the Outer Tag parameter, this VLAN ID number is used for the outer tag
on this port. Alternately, "none" indicates that no VLAN ID is specified
by this service.
Valid Options
none
Enter value (1-4093)
If the associated service-tag action indicates "Specified in Service" for
the Outer Tag parameter, select one of the following options to specify
an outer VLAN tag ID:
Select none to apply the tagging that is explicitly stated in the associate
service-tag action.
Select Enter Value if the associated service-tag action indicates
"Specified in Service" for the Outer Tag parameter. Enter the VLAN ID
number to use for the outer tag on this port.
C-VLAN (In Tag)
If the associated service-tag action indicates "Specified in Service" for
the Inner Tag parameter, this VLAN ID number is used for the inner tag
on this port. Alternately, "none" indicates that no VLAN ID is specified
by this service.
1-4093
none
If the associated service-tag action indicates "Specified in Service" for
the Inner Tag parameter, select one of the following options to specify
an inner VLAN tag ID, as required:
Select none to apply the tagging that is explicitly stated in the
associated service-tag action.
Select Enter Value if the associated service-tag action indicates
"Specified in Service" for the Inner Tag parameter. Enter the VLAN ID
number to use for the inner tag on this port.
*Required fields
Information you need
You must have the following information on hand to configure an ONT video service:




Ethernet bandwidth profile
Multicast profile
Service tag action ID
PON CoS (optionally)
Procedure Assumptions
The following procedure assumes the following conditions:

The E7 unit and ONT have been upgraded to the latest software version. If necessary,
see:


Calix E7 Software Upgrade Guide
The RG configuration file is created and transferred to a server local to the E7. If
necessary, see:

Submitting a T-Series Configuration Parameter Definition Form

Creating a P-series RG Configuration File
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
278

The ONT template is created and applied to the ONT to define all of the key
management aspects of a Home Gateway ONT as well as the logical assignments of
physical GE ports for the initial setup. If necessary, see:

Creating an ONT Template (on page 191)

Applying an ONT Template (on page 257)
To create data and video gateway services with Form view
1. On the Navigation Tree, double-click ONTS.
2. In the work area, click the Provisioned ONTS > Services > Form.
3. From the drop-down list
at the top of the page, select the index
assigned to the ONT on which to add the service.
4. From the list of ONT ports, click the orange triangle
which to add the service.
next to the RG-1 interface on
5. In the Gateway service form, enter the appropriate information for the gateway service 1
(data) and gateway service 2 (video) based on the above parameter descriptions.
Note: IGMP snooping is only enabled on the outer VLAN ID as multicast traffic is
typically transported throughout the network with a single VLAN ID tag. All nodes in an
ERPS ring must have the same IGMP Snooping provisioning on the video VLAN for
traffic to flow--either all with snooping (snoop-suppress, proxy) or all without snooping
(flood).
6. Click Apply to apply the service to the port.
For CLI:





add eth-svc <service name> to-ont-port <ONT port> bw-profile <ONT bw
profile name>
ont-tag-action <tag-action name> [outer-vlan <vlan ID> inner-vlan
<vlan ID>
ont-mcast-profile <profile name> description <service> admin-state
[enabled|disabled]
set ont-port <port> eth-svc [bw-profile|svc-tag-action|outervlan|inner-vlan|mcast-profile|description|admin-state]
show ont-port [detail|fast-eth|gig-eth|hpna-eth|pots|t1|video-hotrf|video-rf|port]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
279
Selecting an E7 PON CoS Option
To support prioritized upstream service flows, the E7 GPON solution supports up to eight
T-CONTs types per ONT. Four types (cos1-4) follow a system-default P-bit to CoS
mapping model. For added flexibility, four other types (user1-4), supported by compatible
ONTs, are user-configurable for any class of service. The combination of these eight TCONTs supports multiple instances of the same traffic class per ONT to be treated
independently for rate-limiting and shaping.
Note: The PON CoS options “derived” through “user-4” support the new GPON QoS
behavior and features available in R2.2+.
Note: T-Series ONTs are supported in E7 R2.3+.
PON Class of Service options for an Ethernet service
PON CoS
Forwarding
Type
Bandwidth
Description
derived
Derived from the priority
of the incoming frames
after tag actions have
been performed,
mapping to cos-1 to 4.
Aggregated for all
services with the
same PON CoS
With this option, incoming frames are mapped to cos-1 to 4 (TCONT types) based on the P-Bit value indicated in the
associated service-tag action.
Note: This option cannot be used with P-Bit preservation and
promotion.
ONT operational notes:
For P-Series GX ONTs: Multiple services with the same traffic
class are rate-limited and shaped independently by GEM port,
isolating the bandwidth for each service before sharing the same
T-CONT.
For P-Series GE and T-Series ONTs: Multiple services with the
same traffic class have unique GEM ports, but are not ratelimited independently before sharing the same T-CONT. To
achieve independent rate-limiting, the second service of the
same traffic class should use user-1 to x to carry the service on
a separate T-CONT.
cos-1
Fixed Best-Effort
cos-2
Fixed Assured
Forwarding
cos-3
Fixed Assured
Forwarding
cos-4
Fixed Expedited
Forwarding
Aggregated for all
services associated
with this system
defined CoS level
These options represent standard T-CONT types with default
PON CoS forwarding types. Incoming frames are mapped to the
T-CONT type specified (cos-1 to 4).
The provisioned services are required to have a bandwidth
profile that matches the class of service. Bandwidth is assigned
as aggregated from the multiple services and mapped to the
ONT.
ONT operational notes:
Same as above.
user-1
user-2
user-3
user-4
Any
Aggregated or
Settable. If
Aggregated, the
rate is derived from
all services
associated with the
system defined
CoS level.
These options represent user-defined T-CONT types that can be
configured with any traffic class forwarding type. For compatible
ONTs, this allows multiple services with the same traffic class to
be carried by separate T-CONTs on the PON. Incoming frames
are mapped to the T-CONT type specified (user-1 to 4).
ONT compatibility:

For GX ONTs: Not supported.

For GE ONTs: user-1 to 4 are supported.

For T-Series ONTs: user-1 to 3 are supported.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
280
PON CoS
Forwarding
Type
Bandwidth
fixed
Derived from the priority
of the incoming frames
after tag actions have
been performed,
mapping to cos-1 to 4.
Aggregated for all
services with the
same PON CoS
Description
This option represents the GPON QoS behavior and features
prior to R2.2, and is intended for backwards compatibility with
those earlier-provisioned services.
With this option, incoming frames are mapped to cos-1 to 4 (TCONT types) based on the P-Bit value indicated in the
associated service-tag action.
Per ONT Ethernet port, this setting provides four GEM ports for
services, one for each system CoS (1-4) value. Multiple services
that map to the same CoS share the same GEM port queue and
aggregate bandwidth, where any one service can use all of the
bandwidth if there is no contention for it.
Quick QoS application examples:

To support VoD over the top without rate limiting (where the VoD traffic P-Bit value is not explicitly defined by the service):
* Use "fixed."

To rate limit two BE services independently:
* On GX SFU/MDU ONTs, use "derived" or "cos-1" for both services. The two services will be
rate-limited independently by GEM port before sharing the same T-CONT.
* On GE ONTs, use "cos-1" (or "derived") for one service and "user-1" for the second service.
Each service must be mapped to a different T-CONT.
Adding Static IP Host Addresses and Subnets
This topic shows you how to configure a static Ethernet service IP address or subnet, to
associate with an ONT Ethernet port service.
Configuration guidelines









To identify a specific IP host for the purposes of securing the subscriber’s traffic, the IP
address must be provided, and optionally, the MAC address information.
To identify an IP subnet, a MAC address is not required. The smallest subnet that can be
provisioned in the system is 255.255.255.252, or /30.
A given data service on an ONT represents exactly one subnet. To support a multihomed router off an ONT port, multiple data services must be provisioned to represent
multiple subnets.
The gateway address and subtending IP addresses must belong to the same subnet as
indicated by the mask.
The static IP address must not be the same as the gateway address.
Duplicate static IP addresses are not allowed in the system.
Adding static IP hosts or subnets to Residential Gateway (RG) services is not supported.
However, adding static IP hosts or subnets to Full Bridge (FB) services is supported.
If the VLAN has a static IP-address, then IP Source Verify may not be enabled unless
MAC Forced Forwarding is also enabled.
If a provisioned static IP address conflicts with a DHCP learned IP address, the system
will accept the static IP address and reject/delete the learned IP address.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
281


The following capacities apply to Static IP Addresses/Subnets within the E7 GPON
subsystem.

Only 1 static IP subnet can be provisioned per ONT Ethernet service.

Up to 16 static IP entries per ONT Ethernet port, on a single service or across
multiple services.

The ONT supports up to 256 "IP stations" per ONT Ethernet port. The number of
IP stations includes active DHCP leases, static IP hosts, and dynamically learned
hosts within a static subnet.

The ONT supports up to 1024 total "IP stations" per ONT. The number of stations
includes active DHCP leases, static IP hosts, and dynamically learned hosts within a
static subnet.
There are two use cases for a static subnet:

1) A customer's premises router is present, with a network-facing IP interface. The
remote static subnet is subtended from the customer router. In this scenario, only the
router interface IP address is visible to MACFF, and it is not necessary to provision
an Access Router (AR) for the subnet (the router will be an ARP Proxy for the
subnet, and all ARPs from the router will be proxied by MACFF.)

2) A customer network is bridged from the subscriber interface. In this scenario, the
access node performs MACFF for any hosts within the subnet. Also, an AR address
must be provisioned for the subnet.
As a result, the AR address is an optional parameter for the first use case, and a
mandatory parameter for the second use case.

IP and MAC addresses may be dynamically learned using either DHCP Snooping or
manually provisioned with static IP/MAC addresses. Services with static subnets
(without MAC address specification) may also be provisioned for IP Source Verification,
but are bound to the port only by IP address.

DHCP and Static IP host: Binds IP and MAC address to an ONT Ethernet Port

Static IP Subnet: Checks individual host IP addresses to the subnet and binds subnet
to ONT port

The E7 GPON system has the following limits on the number of IP stations
(active DHCP leases, static IP hosts, and dynamically learned hosts within a static
subnet):
♦ The ONT supports up to 256 “IP stations” per ONT Ethernet port.
♦ The ONT supports up to 1024 total “IP stations” per ONT.
Before starting
Before starting this procedure, you will need to provision a service on the ONT port where
you want to configure the static IP host address or subnet.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
282
Parameters
You can provision the following parameters for a static IP host address and subnet:
Parameter
Description
Valid Options
Service*
Name of the service to associate with an IP address.
Any established service name
Type*
Select whether to add a static IP host address or a subnet.
ip-addr, subnet
Static IP Host Address
IP Address*
Subscriber host IP address.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
MAC Address
Subscriber host MAC address associated with the IP
address.
Six hexadecimal digits in the range 0FF, optionally separated by colons.
Alternately, "none" can be used to
indicate no MAC address specified.
Gateway*
IP address of the default gateway for subtending static IP
address objects.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
Net Mask*
Net mask for the IP address.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
Static Subnet
Subnet Address*
Subscriber IP address subnet.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
Gateway*
IP address of the default gateway for subtending static IP
address objects.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
Subnet Mask*
Subnet mask for subtending static IP address objects.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
*Required fields
To add a static IP host address
1. On the Navigation Tree, click ONTS.
2. Click Provisioned ONTS > Ports > Static IP/Subnet.
3. In the menu, click the context drop-down list
to select the
ONT port where the service is provisioned of which you want to add a static IP host or
subnet.
4. Click Create to open the Create Ethernet Service IP/Subnet dialog box.
5. Reference the table above to configure the parameters.
6. Click Create.
For CLI:

add static-ip-entry to-ont-port <p-id> eth-svc <s-name> type host ip
<h-ip> netmask <n-ip> default-gw <gw-ip> [mac <m-address>]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
283


add static-ip-entry to-ont-port <p-id> eth-svc <s-name> type subnet ip
<sub-ip> netmask <n-ip> default-gw <gw-ip> [mac <m-address>]
show ont-port <port-id> eth-svc <s-name> static-ip-entry <index>
Configuring PPPoE Operation for a Data Service
The E7 GPON ONT Ethernet ports support Point-to-Point Over Ethernet, and PPPoE
intermediate agent functionality.
The service can use either single tagged or double tagged (Q-in-Q) frames, to and from the
uplink ports, depending on the customer configuration.
When a single VLAN tag is required, a PVID value is assigned to what is considered the
Service Provider Tag (S-Tag). When the service model requires Double Tagged traffic (Q-inQ), an optional inner or Customer Tag (C-Tag) can be provisioned for traffic received for the
customer or CPE initiated PPP session. Prioritization bit values can be assigned for both
VLAN tags.
When PPPoX intermediate agent function is enabled in the VLAN, the E7 automatically
detects all PPPoE Active Discovery packets, including
PADI/PADO/PADR/PADS/PADT, and builds a correspondence table between user
provisioned S-Tag / C-Tag PVIDs, and PPP Session ID, for the given ONT port.
The PPPoE intermediate agent functionality allows for a PPPoE session access method
where the access node inserts a Access Loop Identification (ALID) tag to the PPPoE frames
to be sent upstream toward the Broadband Network Gateway (BNG), and then tracks the
PPPoE sessions. The inserted PPPoE tag contains the identification of the access loop on
which the PADI or PADR packet was received in the access node where the intermediate
agent resides. The E7 complies to TR-101 R-124 requirements for the Agent Circuit ID
inserted by the Access Node PPPoE Intermediate Agent (IA) Vendor specific Tag by
applying a system-defined access-identifier profile.
This topic shows you how to configure PPPoE operation on an ONT port that has a
provisioned data service.
See Creating a PPPoE Profile (on page 186) for instructions, if necessary.
Configuration guidelines:



The E7 uplink toward the router or PPPoE Server must be on an interface set to the
mode of "Trunk."
At the aggregating Trunk interface northbound of the E7, the PPPoE traffic must adhere
to a specific VLAN membership on the Trunk interface.
The PPPoE must be configured so that tag actions are on the Access ports, facing the
subscriber modem.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
284








A modem with a common preprogrammed VLAN can be changed at the GPON ONT
Ethernet port interface to either a common service VLAN, or to a 1:1 VLAN associated
with that customer.
For PPPoE to be enabled, all of the following must be/remain disabled: DHCP Snoop,
MAC Forced Forwarding, IP Source Verify.
Sessions may be manually terminated.
Only one PPPoE session is supported per ONT port. If a second new session is initiated,
the original session tears down and the new session is allowed.
The PPPoE profile is applied to a service VLAN where simultaneous operation of
DHCP Snooping and PPPoE are not supported. When a PPPoE profile is selected for a
data service VLAN, the DHCP features are disabled.
If a PPPoE profile is used with PPPoE snoop, a list of all the active sessions and
statistics are available, and the PPPoE stack is enabled, which passes through PPPoE
traffic transparently as long as the Clients/BRAS are operating normally (illegal packets
will be dropped).
When a PPPoE snoop is NOT applied to a VLAN in the E7, PPP traffic is forwarded as
part of the traffic stream, but, the Intermediate Agent and security aspects of the feature
are not enabled in this mode.
Each GPON subscriber can only have up to 1 Ethernet service with PPPoE enabled.
To configure an ONT port for PPPoE operation
1. Create a service VLAN and do the following:

Set the VLAN to reference the PPPoE profile.

Ensure that the DHCP Snoop is disabled (unselected).

Add the VLAN Member to the E7 uplink interface configured in Step 1.
2. Create a match list and service tag action to match the data traffic at the subscriber port
and mark it with the service VLAN ID.
3. Create a data service on the subscriber port, associating the service tag action created in
Step 2.
To view the PPPoE sessions
1. On the Navigation Tree, click the ONT Ethernet port of interest.
2. In the Workarea, click PPPoE > Sessions.
For CLI:
show
show
show
show
pppoe
pppoe
pppoe
pppoe
sessions
sessions
sessions
sessions
[detail]
id <ses-id> [detail]
mac <m-add> [detail|id]
ont-port <ont-id/ont-port>
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
285
To delete a PPPoE session
1. On the Navigation Tree, click the ONT Ethernet port of interest.
2. In the Workarea, click PPPoE > Sessions.
3. Click on the table row that indicates a PPPoE session to select it.
4. In the toolbar, click Delete.
For CLI:
delete pppoe sessions ont-port <ont-id/ont-port>
Configuring IP Video Services
This section describes how to create IP video services on E7 GPON ONTs.
Topics Covered
This section covers the following topics in bold that are the last step of the overall GPON
services configuration process. The procedures in this section assume that you have
completed the processes in steps 1, 2, 3.
Step 1. Configure network uplinks for GPON services (on page 66)
Step 2. Create system profiles that support GPON applications (on page 110)
Step 3. Configure a PON (on page 231)
Step 4. Configure video subscriber services

Creating L2 Video Service with Form View

Creating L2 Video Service with Table View

Creating a Gateway Video Service

Creating a Gateway Data and Video Service

Adding Static IP Host Addresses and Subnets
Related Topics
For guidance in filling in the provisioning forms necessary to configure video services, see:



Example Video Services Provisioning (on page 358)
Example MVR Video Services Provisioning (on page 366)
Example Multicast IPTV over L2 Bridge Wi-Fi on GigaCenter ONTs (on page 389)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
286
For overviews of provisioning sequences where the steps in the overviews are linked to
supporting procedure topics, see:

Service Provisioning Overviews (on page 41)
Overview: Adding a GPON Video Service
The E7 supports both broadcast IPTV and Video on Demand (VOD) video services.
Beyond basic broadcast IPTV distribution, the E7 also supports carrier deployments of
Microsoft Mediaroom® and other next generation video / middleware platforms. These next
generation IPTV solutions include broadcast video (Live Video), VOD, media sharing /
home DVR, picture-in-picture, and gaming.
The E7 supports broadcast IPTV service using IGMPv2 Snooping (RFC 4541), in both
“Snooping with Report Suppression” and “Proxy” modes.
Note: On-Demand Video streams are unicast traffic similar to any other data service being
delivered by the E7. The Video On Demand (VOD) streams are merged with multicast
IPTV at the ONT Ethernet interface or the residential gateway/set top box.
The following points describe the flow of IPTV video through the E7 GPON and Ethernet
network:



Within the E7, traffic is only replicated to the GPON line cards, not the many ONTs
associated with the system.
The GPON service access card only replicates multicast traffic to the OLT ports on the
card.
If multiple users on the same ONT are watching the same stream, the ONT provides the
channel replication function.
Configuration guidelines







The GPON card supports up to 32 IGMP-enabled multicast VLANs across the system,
which can all be on a PON.
The video VLAN must be the same on the network side (IGMP router side) and access
side (IGMP host side).
The ONT does not support heterogeneous tagging in the MDU case for video service.
All nodes in an ERPS ring must have the same IGMP Snooping provisioning on the
video VLAN for traffic to flow--either all with snooping (snoop-suppress, proxy) or all
without snooping (flood).
The E7 supports up to 800 IGMP multicast groups, enabling up to 800 independent
broadcast video and music channels.
In the multicast profile, the Max Streams value should include the boot channels, the
programming guide, and any other channels that may be learned, in addition to the
number of STBs on the port.
The upstream router MUST be an IGMP querier.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
287












The Query Interval parameter in the Ethernet multicast profile must match the upstream
router configuration.
The E7 passes the following multicast IP addresses through the system on a VLAN that
has IGMP Snooping enabled. (For VLANs with IGMP Snooping disabled, the E7 passes
all multicast traffic transparently.)
HSRP HELLO
224.0.0.2
DVMRP
224.0.0.4
OSPF ALL RTR
224.0.0.5
OSPF DES RTR
224.0.0.6
RIP
224.0.0.9
EIGRP
224.0.0.10
PIM
224.0.0.13
VRRP
224.0.0.18
HSRP
224.0.0.102
MLS ALL SNOOPERS
224.0.0.106
The E7 can perform the following tag actions on a VLAN that has IGMP enabled:

Add-tag action to untagged Ethernet frames.

Change-tag action to change the VLAN ID at network administrative boundaries.
IGMP snooping is only enabled on the outer VLAN ID.
If a connected C7 is using IGMP proxy, then snooping must be enabled on the video
VLAN. Otherwise, snooping should be disabled (set to N).
With Router Learning Mode configured for ‘static-only’, IGMP Proxy will not allow a
static multicast router (‘mrouter’) interface to be a multicast destination. If the interface
could become a multicast destination in the event of a network topology change, the
interface should not be configured as a mrouter interface.
The network switch providing the video must have IGMP enabled.
IGMP control messages are forwarded both directions around an ERPS ring, enabling
the population of the multicast forwarding tables for all connected E7 platforms on the
ring. In the event of a ring switch, video will be able to quickly flow in either direction
without waiting for the IGMP protocol to resolve the video paths.
IGMP and Multicast traffic are not allowed to traverse ports blocked by the ring
protection protocol.
The E7 monitors all interfaces associated with the IGMP multicast VLAN for the
presence of an IGMP General Query message to automatically detect the multicast
router.
The E7 drops joins and leaves received on router (uplink) side ports. Ports connected to
a router are assumed to be facing the network and should not receive joins and leaves.
IGMP is enabled for all ports designated as ring ports.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
288



IGMP snooping occurs internally to the E7 and Calix ONT and is not a networking
protocol.
A 700GE ONT or 836GE RSG supports multicast and unicast IPTV services on either
the Routed WAN interface or L2 bridge ports provisioned as either Half-Bridge or FullBridge mode.

When the multicast profile is assigned to the L2 bridge, a single IGMP Snoop
function manages the multicast flows across all Half-Bridge ports, or across the FullBridge group.

When the multicast profile is assigned to the Routed WAN interface using Home
Gateway, it supports both IGMP Snoop and Proxy.

All modes support Multicast VLAN Replication (MVR) as part of the multicast
profile.
Multicast VLAN Registration (MVR) is used at the ONT to merge the common
multicast VLAN content into the subscriber’s untagged service on the ONT UserNetwork Interface (UNI). The E7 MVR implementation allows up to 4 independent
multicast VLANs to be merged into the subscriber’s unicast service. These multicast
VLANs can be used to segregate various content (e.g. HD, SD, Audio, local channels) or
facilitate additional video provider content that a service provide may seek to distribute
to end users.
The E7 currently supports RFC 4541 IGMPv2 and RFC 3376 IGMPv3. Most IPTV set top
boxes support IGMPv2.
For guidance in filling in the provisioning forms necessary to configure video services, see:




Example: Video Services Provisioning (on page 358)
Example: MVR Video Services (on page 366)
Example: HGW Service - P-Series Native Mode (on page 413)
Example: HGW Service - P-Series External Mode (on page 380)
Creating a Subscriber Service

Form view shows an expandable structure that allows you to create multiple
instances of different service types, by scrolling to selected ports on the ONT.

Table view shows the services currently provisioned on the selected ONT, and
allows you to create a single service of the selected type.
Information you need
You must have the following information on hand to configure ONT data service:


Ethernet bandwidth profile (on page 167)
Ethernet multicast profile (on page 177)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
289

Service-tag action ID (on page 131)


Output Outer Tag or Inner Tag (if referenced as "Specified in Service" in the servicetag action)
PON CoS (on page 124) (optional)
Creating L2 Video Service with Form View
This topic describes how to configure Layer-2 IP video services on an ONT Ethernet port,
or an ONT Full Bridge (FB) interface, using an ONT services form where you can provision
any possible service for the any ONT configured in the E7 system.
Optionally, you can add an individual video service, using a Table view to first survey the
services currently provisioned on any ONT configured in the E7 system.

For an outline of the entire process of provisioning video service, see:
Overview: GPON IP Video Services (on page 44)

For guidance in filling in the provisioning forms necessary to configure video services,
see:
Example Video Services Provisioning (on page 358) and Example MVR Video Services
Provisioning (on page 366)
Note: The upstream and downstream values specified in the Ethernet Bandwidth Profile and
P-bit values defined in the service-tag action must be consistent with the class of service type
as defined in the global CoS table. See Creating Traffic Management Profiles (on page 116) or
"Ethernet Traffic Management" in the Calix E7 Engineering and Planning Guide.
Information you need
You must have the following information on hand to configure an ONT video service:




Ethernet bandwidth profile
Multicast profile
Service tag action ID
PON CoS (optionally)
Parameters
You can provision the following parameters for video service on an ONT Ethernet port:
Parameter
Description
Valid Options
Subscriber ID
Subscriber ID information, such as phone number, or account number.
String up to 27
characters
(blank) ‡
Description
Optional description field for the port, subscriber address, name, or
service.
String up to 27
characters
(blank) ‡
Multicast Profile*
Name of Ethernet multicast profile to apply to this port.
Any established
multicast profile
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
290
Parameter
Description
Valid Options
BW Profile*
Name of Ethernet bandwidth profile to apply to this port.
Any established
bandwidth profile
PON CoS
Class of Service instance to apply to the service.
derived, user-1, user-2,
user-3, user-4, cos-1,
cos-2, cos-3, cos-4, fixed

derived option has incoming frames mapped to cos-1 to 4 (T-CONT
types) based on the P-Bit value indicated in the associated servicetag action.

cos 1-4 options represent standard T-CONT types with default PON
CoS forwarding types. Incoming frames are mapped to the T-CONT
type specified (cos-1 to 4).

user 1-4 options represent user-defined T-CONT types that can be
configured with any traffic class forwarding type. For compatible
ONTs, this allows multiple services with the same traffic class to be
carried by separate T-CONTs on the PON. Incoming frames are
mapped to the T-CONT type specified (user-1 to 4). Note: If you
want to apply a user-defined PON Upstream CoS profile, it must
have been previously mapped to the ONT for it to be available for
selection in this step. If necessary, see Adding PON Upstream CoS
Profiles to an ONT (on page 256).

fixed represents the GPON QoS behavior and features prior to
R2.2, and is intended for backwards compatibility with those earlierprovisioned services.
See Selecting PON CoS (on page 279) for details on the PON CoS
options.
See GPON QoS (on page 117) for an overview of how the system
supports prioritized upstream service flows.
Upstream Peak Rate
Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Upstream Committed
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Downstream Peak
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Tag Action*
Name of service tag action to apply to the service.
Any established tag
action
Note: IGMP snooping is only enabled on the outer VLAN ID as
multicast traffic is typically transported throughout the network with a
single VLAN ID tag. All nodes in an ERPS ring must have the same
IGMP Snooping provisioning on the video VLAN for traffic to flow--either
all with snooping (snoop-suppress, proxy) or all without snooping
(flood).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
291
Parameter
Out Tag
Description
If the associated service-tag action indicates "Specified in Service" for
the Outer Tag parameter, select one of the following options to specify
an outer VLAN tag ID:
In Tag

Select none to apply the tagging that is explicitly stated in the
associate service-tag action.

Select Enter Value if the associated service-tag action indicates
"Specified in Service" for the Outer Tag parameter. Enter the VLAN
ID number to use for the outer tag on this port.
If the associated service-tag action indicates "Specified in Service" for
the Inner Tag parameter, select one of the following options to specify
an inner VLAN tag ID, as required:

Select none to apply the tagging that is explicitly stated in the
associated service-tag action.

Select Enter Value if the associated service-tag action indicates
"Specified in Service" for the Inner Tag parameter. Enter the VLAN
ID number to use for the inner tag on this port.
Valid Options
none
Enter value (1-4093)
1-4093
none
*Required fields
Procedure Assumptions
The following procedure assumes that if you intend to add a service to a Full Bridge (FB)
interface, you have already assigned the applicable GE port to the interface. If necessary, see
the following topics for instructions:


Configuring an ONT Ethernet Port (on page 257)
Configuring an ONT Full Bridge Interface (on page 266)
To create a video service with Form view
1. On the Navigation Tree, double-click ONTS.
2. In the work area, click the Provisioned ONTS > Services > Form.
3. From the drop-down list
at the top of the page, select the index
assigned to the ONT on which to add the service.
4. From the list of ONT ports, click the orange triangle next to the ONT Ethernet port,
or the ONT FB interface on which to add the service.
5. Reference the table above to configure the parameters.
6. Click Apply to apply the service to the port.
For CLI:



add eth-svc <service name> to-ont-port <ONT port> bw-profile <ONT bw
profile name>
ont-tag-action <tag-action name> [outer-vlan <vlan ID> inner-vlan
<vlan ID>
ont-mcast-profile <profile name> description <service> admin-state
[enabled|disabled]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
292


set ont-port <port> eth-svc [bw-profile|svc-tag-action|outervlan|inner-vlan|mcast-profile|description|admin-state]
show ont-port [detail|fast-eth|gig-eth|hpna-eth|pots|t1|video-hotrf|video-rf|port]
Related topics





Creating an Ethernet Bandwidth Profile (on page 167)
Creating a Service Match List and Rules (on page 127)
Creating Service-Tag Actions (on page 131)
GPON QoS (on page 117)
Calix Home Gateway Services (on page 28)
Creating L2 Video Service with Table View
This topic describes how to configure Layer-2 IP video services on an ONT Ethernet port,
or an ONT Full Bridge (FB) interface, using a Table view to first survey the services
currently provisioned on any ONT configured in the E7 system.
Optionally, you can use a subscriber services activation form where you can provision any
possible service for any ONT configured in the E7 system.

For an outline of the entire process of provisioning video service, see:
Overview: GPON IP Video Services (on page 44)

For guidance in filling in the provisioning forms necessary to configure video services,
see:
Example Video Services Provisioning (on page 358) and Example MVR Video Services
Provisioning (on page 366)
Information you need
You must have the following information on hand to configure an ONT video service:




Ethernet bandwidth profile
Multicast profile
Service tag action ID
PON CoS (optionally)
Parameters
You can provision the following video service parameters accessed from the Table view:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
293
Parameter
Description
Valid Options
Subscriber Port
Subscriber Port*
System address of the ONT Ethernet port or ONT FB interface where
the subscriber services will be provisioned.
Any ONT POTS port
Note: For HGW ONTs, the GE port must first be assigned to a layer-2
interface, if not already done. That is, either assigned as a member to
Full-Bridge (FB), or NOT assigned as a member of any interface,
allowing the port to operate as a normal L2 classic port (Half-Bridge
mode).
Subscriber ID
Subscriber ID information, such as phone number, or account number.
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
Description
Optional description field for the port, subscriber address, name, or
service.
String up to 27 characters
(blank) ‡
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Description entry from the
ONT provisioning record to this field.
Create Video Service
Service Name*
Ethernet service name to apply to the ONT port (Video1 to Video4).
Video1 ... Video4
BW Profile*
Name of previously-created Ethernet bandwidth profile to apply to this
port.
Any established
bandwidth profile
PON CoS
Class of Service instance to apply to the service.
derived, user-1, user-2,
user-3, user-4, cos-1, cos2, cos-3, cos-4, fixed

derived option has incoming frames mapped to cos-1 to 4 (T-CONT
types) based on the P-Bit value indicated in the associated servicetag action.

cos 1-4 options represent standard T-CONT types with default PON
CoS forwarding types. Incoming frames are mapped to the T-CONT
type specified (cos-1 to 4).

user 1-4 options represent user-defined T-CONT types that can be
configured with any traffic class forwarding type. For compatible
ONTs, this allows multiple services with the same traffic class to be
carried by separate T-CONTs on the PON. Incoming frames are
mapped to the T-CONT type specified (user-1 to 4). Note: If you
want to apply a user-defined PON Upstream CoS profile, it must
have been previously mapped to the ONT for it to be available for
selection in this step. If necessary, see Adding PON Upstream CoS
Profiles to an ONT (on page 256).

fixed represents the GPON QoS behavior and features prior to
R2.2, and is intended for backwards compatibility with those earlierprovisioned services.
See Selecting PON CoS (on page 279) for details on the PON CoS
options.
See GPON QoS (on page 117) for an overview of how the system
supports prioritized upstream service flows.
Multicast Profile*
Name of the previously-created multicast profile to apply to the service.
Any established multicast
profile
Upstream Peak Rate
Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
294
Parameter
Description
Upstream Committed
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Downstream Peak
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Service Tag Action*
Name of the service tag action or "none" for no service tag action.
index-name of tag action
S-VLAN (Outer Tag)
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
Note: IGMP snooping is only enabled on the outer VLAN ID as
multicast traffic is typically transported throughout the network with a
single VLAN ID tag. All nodes in an ERPS ring must have the same
IGMP Snooping provisioning on the video VLAN for traffic to flow--either
all with snooping (snoop-suppress, proxy) or all without snooping
(flood).
C-VLAN (Inner Tag)
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
Valid Options
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
*Required fields
‡ Default
Procedure Assumptions
The following procedure assumes that if you intend to add a service to a Full Bridge (FB)
interface, you have already assigned the applicable GE port to the interface. If necessary, see
the following topics for instructions:


Configuring an ONT Ethernet Port (on page 257)
Configuring an ONT Full Bridge Interface (on page 266)
To create a video service
1. On the Navigation Tree, click ONTS.
2. In the work area, click Provisioned ONTS > Services > Table.
3. From the drop-down list
at the top of the page, select the index
assigned to the ONT on which to add the service.
4. From the menu, click Create > Video Service to open the Create dialog box.
5. Reference the table above to configure the parameters.
6. Click Create to activate a video service on the subscriber port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
295
For CLI:





add eth-svc <service name> to-ont-port <ONT port> bw-profile <ONT bw
profile name>
ont-tag-action <tag-action name> [outer-vlan <vlan ID> inner-vlan
<vlan ID>
ont-mcast-profile <profile name> description <service> admin-state
[enabled|disabled]]
set ont-port <port> eth-svc [bw-profile|svc-tag-action|outervlan|inner-vlan|mcast-profile|description|admin-state]
show ont-port [detail|fast-eth|gig-eth|hpna-eth|pots|t1|video-hotrf|video-rf|port]
Related topics

Creating an Ethernet Bandwidth Profile (on page 167)




Creating a Service Match List and Rules (on page 127)
Creating Service-Tag Actions (on page 131)
GPON QoS (on page 117)
Calix Home Gateway Services (on page 28)
Creating a Gateway Video Service with Table View
This topic describes how to configure and individual Gateway video service on an Residential
Gateway (RG) interface, using a Table view to first survey the services currently provisioned
on any ONT configured in the E7 system.
Optionally, you can add a gateway video service using a subscriber services form where you
can provision any possible service for any ONT configured in the E7 system.

For an outline of the entire process of provisioning video service, see:
Overview: HGW Applications - External Mode (on page 48)

For guidance in filling in the provisioning forms necessary to configure gateway services,
see:
HGW Service - External Mode Example (on page 380)
Mediaroom network and service configuration
The following network and service models are representative of two typical Mediaroom
deployments with a Residential Gateway (RG).
Residential Gateway with
Untagged Traffic
Residential Gateway with
VLAN-tagged Traffic

The E7 sends all traffic to the RG and receives
all traffic from the RG as untagged traffic.

The E7 sends all traffic to the RG and receives all traffic
from the RG as VLAN-tagged traffic.

Toward the RG, the E7 merges the multicast
VLAN(s) traffic into the untagged unicast
subscriber traffic.

Toward the RG, the E7 merges the multicast VLAN(s)
traffic into the default unicast video VLAN.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
296
Residential Gateway with
Untagged Traffic
Residential Gateway with
VLAN-tagged Traffic

When receiving traffic from the RG, the E7
snoops the untagged traffic for IGMP messages,
extracting those messages and sending them
upstream (as needed) within the multicast VLAN.

When receiving the video VLAN from the RG, the E7
snoops the traffic for IGMP messages, extracting those
messages and sending them upstream (as needed) within
the multicast VLAN.

Upstream, all other traffic not part of the multicast
service is tagged with the subscriber’s Q-in-Q
tags or with the per-service single VLAN tag.

The E7 performs a change-tag tag action to map the RGcommon HSI and Video VLANs into provider managed
VLANs. The E7 can support Q-in-Q subscriber VLAN
models using an “add-outer, change-inner” tag action.
Residential Gateway with untagged traffic


Downstream: VOD, ICC, and Control traffic flow downstream within the E7
transport/access network with prioritization and congestion management based on Pbits. Within the GPON subsystem, only the frames with P-bit=0 (HSI traffic) match the
provisioned service and are subject to the Bandwidth Profile.
Upstream: The nominal Mediaroom control traffic is part of the HSI bandwidth meter.
The upstream PIR rate in the subscriber’s bandwidth profile can be increased by 128
Kbps to accommodate occasional bursts of Mediaroom control traffic.
Residential Gateway with VLAN-tagged traffic
The ONT is configured with multiple unicast VLANs (for example, HSI and video) in
addition to the multicast VLAN. The multicast traffic is merged into the video VLAN using
MVR.
Parameters
You can provision the following video service parameters accessed from Table view:
Parameter
Description
Valid Options
Subscriber Port
Subscriber Port*
System address of the ONT port where the subscriber services will be
provisioned.
Any ONT POTS port
Note: For HGW ONTs, the GE port must first be assigned to a layer-2
interface, if not already done. That is, either assigned as a member to
Full-Bridge (FB), or NOT assigned as a member of any interface,
allowing the port to operate as a normal L2 classic port (Half-Bridge
mode).
Subscriber ID
Subscriber ID information, such as phone number, or account number.
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
Description
Optional description field for the port, subscriber address, name, or
service.
String up to 27 characters
(blank) ‡
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Description entry from the
ONT provisioning record to this field.
Create Video Service
Service Name*
Name of gateway service for the ONT port to use.
Gateway1 ... Gateway4
BW Profile*
Name of previously-created Ethernet bandwidth profile to apply to this
port.
Any established
bandwidth profile
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
297
Parameter
PON CoS
Description
Class of Service instance to apply to the service.

derived option has incoming frames mapped to cos-1 to 4 (T-CONT
types) based on the P-Bit value indicated in the associated servicetag action.

cos 1-4 options represent standard T-CONT types with default PON
CoS forwarding types. Incoming frames are mapped to the T-CONT
type specified (cos-1 to 4).

user 1-4 options represent user-defined T-CONT types that can be
configured with any traffic class forwarding type. For compatible
ONTs, this allows multiple services with the same traffic class to be
carried by separate T-CONTs on the PON. Incoming frames are
mapped to the T-CONT type specified (user-1 to 4). Note: If you
want to apply a user-defined PON Upstream CoS profile, it must
have been previously mapped to the ONT for it to be available for
selection in this step. If necessary, see Adding PON Upstream CoS
Profiles to an ONT (on page 256).

fixed represents the GPON QoS behavior and features prior to
R2.2, and is intended for backwards compatibility with those earlierprovisioned services.
Valid Options
derived, user-1, user-2,
user-3, user-4, cos-1, cos2, cos-3, cos-4, fixed
See Selecting PON CoS (on page 279) for details on the PON CoS
options.
See GPON QoS (on page 117) for an overview of how the system
supports prioritized upstream service flows.
Multicast Profile*
Name of the previously-created multicast profile to apply to the service.
Any established multicast
profile
Upstream Peak Rate
Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Upstream Committed
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Downstream Peak
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Service Tag Action*
Name of the service tag action or "none" for no service tag action.
index-name of tag action
S-VLAN (Outer Tag)
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
Note: IGMP snooping is only enabled on the outer VLAN ID as
multicast traffic is typically transported throughout the network with a
single VLAN ID tag. All nodes in an ERPS ring must have the same
IGMP Snooping provisioning on the video VLAN for traffic to flow--either
all with snooping (snoop-suppress, proxy) or all without snooping
(flood).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
298
Parameter
Description
Valid Options
C-VLAN (Inner Tag)
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
*Required fields
‡ Default
Information you need
You must have the following information on hand to configure an ONT video service:




Ethernet bandwidth profile
Multicast profile
Service tag action ID
PON CoS (optionally)
Procedure Assumptions
The following procedure assumes the following conditions:

The E7 unit and ONT have been upgraded to the latest software version. If necessary,
see:



Calix E7 Software Upgrade Guide
The RG configuration file is created and transferred to a server local to the E7. If
necessary, see:

Submitting a T-Series Configuration Parameter Definition Form

Creating a P-series RG Configuration File
The ONT template is created and applied to the ONT to define all of the key
management aspects of a Home Gateway ONT as well as the logical assignments of
physical GE ports for the initial setup. If necessary, see:

Creating an ONT Template (on page 191)

Applying an ONT Template (on page 257)
To create a gateway video service
1. On the Navigation Tree, click ONTS.
2. In the work area, click Provisioned ONTS > Services > Table.
3. From the drop-down list
at the top of the page, select the index
assigned to the ONT on which to add the service.
4. From the menu, click Create > Gateway Service to open the Create dialog box.
5. Reference the table above to configure the parameters.
6. Click Create to activate a video service on the subscriber port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
299
For CLI:





add eth-svc <service name> to-ont-port <ONT port> bw-profile <ONT bw
profile name>
ont-tag-action <tag-action name> [outer-vlan <vlan ID> inner-vlan
<vlan ID>
ont-mcast-profile <profile name> description <service> admin-state
[enabled|disabled]]
set ont-port <port> eth-svc [bw-profile|svc-tag-action|outervlan|inner-vlan|mcast-profile|description|admin-state]
show ont-port [detail|fast-eth|gig-eth|hpna-eth|pots|t1|video-hotrf|video-rf|port]
Related topics

Creating an Ethernet Bandwidth Profile (on page 167)




Creating a Service Match List and Rules (on page 127)
Creating Service-Tag Actions (on page 131)
GPON QoS (on page 117)
Calix Home Gateway Services (on page 28)
Creating Gateway Data and Video Service with Form View
This topic describes how to configure Gateway data and video services on an Residential
Gateway (RG) interface, using a subscriber services form where you can provision any
possible service for any ONT configured in the E7 system.
Optionally, you can add an individual gateway service, using a Table view to first survey the
services currently provisioned on any ONT configured in the E7 system.

For an outline of the entire process of provisioning video service, see:
Overview: HGW Applications - External Mode (on page 48)

For guidance in filling in the provisioning forms necessary to configure gateway services,
see:
HGW Service - External Mode Example (on page 380)
Note: The upstream and downstream values specified in the Ethernet Bandwidth Profile and
P-bit values defined in the service-tag action must be consistent with the class of service type
as defined in the global CoS table. See Creating Traffic Management Profiles (on page 116) or
"Ethernet Traffic Management" in the Calix E7 Engineering and Planning Guide.
Parameters
You can provision the following parameters for video service on an ONT Ethernet port:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
300
Parameter
Subscriber ID
Description
Subscriber ID information, such as phone number, or account number.
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
Description
Optional description field for the port, subscriber address, name, or
service.
If you leave this box empty, the E7 copies the Description entry from the
ONT provisioning record to this field.
Valid Options
String up to 27
characters
(blank) ‡
String up to 27
characters
(blank) ‡
Management Profile
Name of RG management profile for TR-069 that allows you to
configure common ACS-related parameters, and how the TR-069
management channel is setup (in-band or out-of-band).
Any established RG
management profile
TR-069 Eth Service
(P-series only) When the the TR-069 client is configured to for
Management mode = In-band in the RG Management Profile, the client
runs on an existing RG WAN interface. Typically, the path to the ACS
server utilizes an existing RG service such as Gateway Service: 1 (for
example, a HSI service).
Gateway Service:1-4
Multicast Profile*
Name of Ethernet multicast profile to apply to this port.
Any established
multicast profile
BW Profile*
Name of Ethernet bandwidth profile to apply to this port.
Any established
bandwidth profile
PON CoS
Class of Service instance to apply to the service.
derived, user-1, user-2,
user-3, user-4, cos-1,
cos-2, cos-3, cos-4, fixed

derived option has incoming frames mapped to cos-1 to 4 (T-CONT
types) based on the P-Bit value indicated in the associated servicetag action.

cos 1-4 options represent standard T-CONT types with default PON
CoS forwarding types. Incoming frames are mapped to the T-CONT
type specified (cos-1 to 4).

user 1-4 options represent user-defined T-CONT types that can be
configured with any traffic class forwarding type. For compatible
ONTs, this allows multiple services with the same traffic class to be
carried by separate T-CONTs on the PON. Incoming frames are
mapped to the T-CONT type specified (user-1 to 4). Note: If you
want to apply a user-defined PON Upstream CoS profile, it must
have been previously mapped to the ONT for it to be available for
selection in this step. If necessary, see Adding PON Upstream CoS
Profiles to an ONT (on page 256).

fixed represents the GPON QoS behavior and features prior to
R2.2, and is intended for backwards compatibility with those earlierprovisioned services.
See Selecting PON CoS (on page 279) for details on the PON CoS
options.
See GPON QoS (on page 117) for an overview of how the system
supports prioritized upstream service flows.
Upstream Peak Rate
Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Upstream Committed
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
301
Parameter
Description
Valid Options
Downstream Peak
Rate Override
For DOCSIS provisioning (with the Calix Compass: Open Link Cable
vCMTS) to allow an override of the Ethernet bandwidth profile applied to
a service. This allows a pre-defined profile to be reused and also allows
the required DOCSIS provisioning where the upstream/downstream
bandwidth parameters are specified individually each time a new
service is configured on a port. See the Calix Open Link Cable vCMTS
Command-Line Interface (CLI) Reference Guide and Calix Open Link
Cable vCMTS SNMP Management Guide for more information.
none
Enter Value
Tag Action*
Name of service tag action to apply to the service.
Any established tag
action
S-VLAN (Outer Tag)
If the associated service-tag action indicates "Specified in Service" for
the Outer Tag parameter, this VLAN ID number is used for the outer tag
on this port. Alternately, "none" indicates that no VLAN ID is specified
by this service.
none
Enter value (1-4093)
If the associated service-tag action indicates "Specified in Service" for
the Outer Tag parameter, select one of the following options to specify
an outer VLAN tag ID:
Select none to apply the tagging that is explicitly stated in the associate
service-tag action.
Select Enter Value if the associated service-tag action indicates
"Specified in Service" for the Outer Tag parameter. Enter the VLAN ID
number to use for the outer tag on this port.
C-VLAN (In Tag)
If the associated service-tag action indicates "Specified in Service" for
the Inner Tag parameter, this VLAN ID number is used for the inner tag
on this port. Alternately, "none" indicates that no VLAN ID is specified
by this service.
1-4093
none
If the associated service-tag action indicates "Specified in Service" for
the Inner Tag parameter, select one of the following options to specify
an inner VLAN tag ID, as required:
Select none to apply the tagging that is explicitly stated in the
associated service-tag action.
Select Enter Value if the associated service-tag action indicates
"Specified in Service" for the Inner Tag parameter. Enter the VLAN ID
number to use for the inner tag on this port.
*Required fields
Information you need
You must have the following information on hand to configure an ONT video service:




Ethernet bandwidth profile
Multicast profile
Service tag action ID
PON CoS (optionally)
Procedure Assumptions
The following procedure assumes the following conditions:

The E7 unit and ONT have been upgraded to the latest software version. If necessary,
see:

Calix E7 Software Upgrade Guide
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
302


The RG configuration file is created and transferred to a server local to the E7. If
necessary, see:

Submitting a T-Series Configuration Parameter Definition Form

Creating a P-series RG Configuration File
The ONT template is created and applied to the ONT to define all of the key
management aspects of a Home Gateway ONT as well as the logical assignments of
physical GE ports for the initial setup. If necessary, see:

Creating an ONT Template (on page 191)

Applying an ONT Template (on page 257)
To create data and video gateway services with Form view
1. On the Navigation Tree, double-click ONTS.
2. In the work area, click the Provisioned ONTS > Services > Form.
3. From the drop-down list
at the top of the page, select the index
assigned to the ONT on which to add the service.
4. From the list of ONT ports, click the orange triangle
which to add the service.
next to the RG-1 interface on
5. In the Gateway service form, enter the appropriate information for the gateway service 1
(data) and gateway service 2 (video) based on the above parameter descriptions.
Note: IGMP snooping is only enabled on the outer VLAN ID as multicast traffic is
typically transported throughout the network with a single VLAN ID tag. All nodes in an
ERPS ring must have the same IGMP Snooping provisioning on the video VLAN for
traffic to flow--either all with snooping (snoop-suppress, proxy) or all without snooping
(flood).
6. Click Apply to apply the service to the port.
For CLI:





add eth-svc <service name> to-ont-port <ONT port> bw-profile <ONT bw
profile name>
ont-tag-action <tag-action name> [outer-vlan <vlan ID> inner-vlan
<vlan ID>
ont-mcast-profile <profile name> description <service> admin-state
[enabled|disabled]
set ont-port <port> eth-svc [bw-profile|svc-tag-action|outervlan|inner-vlan|mcast-profile|description|admin-state]
show ont-port [detail|fast-eth|gig-eth|hpna-eth|pots|t1|video-hotrf|video-rf|port]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
303
Selecting an E7 PON CoS Option
To support prioritized upstream service flows, the E7 GPON solution supports up to eight
T-CONTs types per ONT. Four types (cos1-4) follow a system-default P-bit to CoS
mapping model. For added flexibility, four other types (user1-4), supported by compatible
ONTs, are user-configurable for any class of service. The combination of these eight TCONTs supports multiple instances of the same traffic class per ONT to be treated
independently for rate-limiting and shaping.
Note: The PON CoS options “derived” through “user-4” support the new GPON QoS
behavior and features available in R2.2+.
Note: T-Series ONTs are supported in E7 R2.3+.
PON Class of Service options for an Ethernet service
PON CoS
Forwarding
Type
Bandwidth
Description
derived
Derived from the priority
of the incoming frames
after tag actions have
been performed,
mapping to cos-1 to 4.
Aggregated for all
services with the
same PON CoS
With this option, incoming frames are mapped to cos-1 to 4 (TCONT types) based on the P-Bit value indicated in the
associated service-tag action.
Note: This option cannot be used with P-Bit preservation and
promotion.
ONT operational notes:
For P-Series GX ONTs: Multiple services with the same traffic
class are rate-limited and shaped independently by GEM port,
isolating the bandwidth for each service before sharing the same
T-CONT.
For P-Series GE and T-Series ONTs: Multiple services with the
same traffic class have unique GEM ports, but are not ratelimited independently before sharing the same T-CONT. To
achieve independent rate-limiting, the second service of the
same traffic class should use user-1 to x to carry the service on
a separate T-CONT.
cos-1
Fixed Best-Effort
cos-2
Fixed Assured
Forwarding
cos-3
Fixed Assured
Forwarding
cos-4
Fixed Expedited
Forwarding
Aggregated for all
services associated
with this system
defined CoS level
These options represent standard T-CONT types with default
PON CoS forwarding types. Incoming frames are mapped to the
T-CONT type specified (cos-1 to 4).
The provisioned services are required to have a bandwidth
profile that matches the class of service. Bandwidth is assigned
as aggregated from the multiple services and mapped to the
ONT.
ONT operational notes:
Same as above.
user-1
user-2
user-3
user-4
Any
Aggregated or
Settable. If
Aggregated, the
rate is derived from
all services
associated with the
system defined
CoS level.
These options represent user-defined T-CONT types that can be
configured with any traffic class forwarding type. For compatible
ONTs, this allows multiple services with the same traffic class to
be carried by separate T-CONTs on the PON. Incoming frames
are mapped to the T-CONT type specified (user-1 to 4).
ONT compatibility:

For GX ONTs: Not supported.

For GE ONTs: user-1 to 4 are supported.

For T-Series ONTs: user-1 to 3 are supported.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
304
PON CoS
Forwarding
Type
Bandwidth
fixed
Derived from the priority
of the incoming frames
after tag actions have
been performed,
mapping to cos-1 to 4.
Aggregated for all
services with the
same PON CoS
Description
This option represents the GPON QoS behavior and features
prior to R2.2, and is intended for backwards compatibility with
those earlier-provisioned services.
With this option, incoming frames are mapped to cos-1 to 4 (TCONT types) based on the P-Bit value indicated in the
associated service-tag action.
Per ONT Ethernet port, this setting provides four GEM ports for
services, one for each system CoS (1-4) value. Multiple services
that map to the same CoS share the same GEM port queue and
aggregate bandwidth, where any one service can use all of the
bandwidth if there is no contention for it.
Quick QoS application examples:

To support VoD over the top without rate limiting (where the VoD traffic P-Bit value is not explicitly defined by the service):
* Use "fixed."

To rate limit two BE services independently:
* On GX SFU/MDU ONTs, use "derived" or "cos-1" for both services. The two services will be
rate-limited independently by GEM port before sharing the same T-CONT.
* On GE ONTs, use "cos-1" (or "derived") for one service and "user-1" for the second service.
Each service must be mapped to a different T-CONT.
Adding Static IP Host Addresses and Subnets
This topic shows you how to configure a static Ethernet service IP address or subnet, to
associate with an ONT Ethernet port service.
Configuration guidelines









To identify a specific IP host for the purposes of securing the subscriber’s traffic, the IP
address must be provided, and optionally, the MAC address information.
To identify an IP subnet, a MAC address is not required. The smallest subnet that can be
provisioned in the system is 255.255.255.252, or /30.
A given data service on an ONT represents exactly one subnet. To support a multihomed router off an ONT port, multiple data services must be provisioned to represent
multiple subnets.
The gateway address and subtending IP addresses must belong to the same subnet as
indicated by the mask.
The static IP address must not be the same as the gateway address.
Duplicate static IP addresses are not allowed in the system.
Adding static IP hosts or subnets to Residential Gateway (RG) services is not supported.
However, adding static IP hosts or subnets to Full Bridge (FB) services is supported.
If the VLAN has a static IP-address, then IP Source Verify may not be enabled unless
MAC Forced Forwarding is also enabled.
If a provisioned static IP address conflicts with a DHCP learned IP address, the system
will accept the static IP address and reject/delete the learned IP address.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
305


The following capacities apply to Static IP Addresses/Subnets within the E7 GPON
subsystem.

Only 1 static IP subnet can be provisioned per ONT Ethernet service.

Up to 16 static IP entries per ONT Ethernet port, on a single service or across
multiple services.

The ONT supports up to 256 "IP stations" per ONT Ethernet port. The number of
IP stations includes active DHCP leases, static IP hosts, and dynamically learned
hosts within a static subnet.

The ONT supports up to 1024 total "IP stations" per ONT. The number of stations
includes active DHCP leases, static IP hosts, and dynamically learned hosts within a
static subnet.
There are two use cases for a static subnet:

1) A customer's premises router is present, with a network-facing IP interface. The
remote static subnet is subtended from the customer router. In this scenario, only the
router interface IP address is visible to MACFF, and it is not necessary to provision
an Access Router (AR) for the subnet (the router will be an ARP Proxy for the
subnet, and all ARPs from the router will be proxied by MACFF.)

2) A customer network is bridged from the subscriber interface. In this scenario, the
access node performs MACFF for any hosts within the subnet. Also, an AR address
must be provisioned for the subnet.
As a result, the AR address is an optional parameter for the first use case, and a
mandatory parameter for the second use case.

IP and MAC addresses may be dynamically learned using either DHCP Snooping or
manually provisioned with static IP/MAC addresses. Services with static subnets
(without MAC address specification) may also be provisioned for IP Source Verification,
but are bound to the port only by IP address.

DHCP and Static IP host: Binds IP and MAC address to an ONT Ethernet Port

Static IP Subnet: Checks individual host IP addresses to the subnet and binds subnet
to ONT port

The E7 GPON system has the following limits on the number of IP stations
(active DHCP leases, static IP hosts, and dynamically learned hosts within a static
subnet):
♦ The ONT supports up to 256 “IP stations” per ONT Ethernet port.
♦ The ONT supports up to 1024 total “IP stations” per ONT.
Before starting
Before starting this procedure, you will need to provision a service on the ONT port where
you want to configure the static IP host address or subnet.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
306
Parameters
You can provision the following parameters for a static IP host address and subnet:
Parameter
Description
Valid Options
Service*
Name of the service to associate with an IP address.
Any established service name
Type*
Select whether to add a static IP host address or a subnet.
ip-addr, subnet
Static IP Host Address
IP Address*
Subscriber host IP address.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
MAC Address
Subscriber host MAC address associated with the IP
address.
Six hexadecimal digits in the range 0FF, optionally separated by colons.
Alternately, "none" can be used to
indicate no MAC address specified.
Gateway*
IP address of the default gateway for subtending static IP
address objects.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
Net Mask*
Net mask for the IP address.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
Static Subnet
Subnet Address*
Subscriber IP address subnet.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
Gateway*
IP address of the default gateway for subtending static IP
address objects.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
Subnet Mask*
Subnet mask for subtending static IP address objects.
IP address in dotted quad" format:
"192.168.1.100". Alternately, "none" can
be used to reset the value to "0.0.0.0"
*Required fields
To add a static IP host address
1. On the Navigation Tree, click ONTS.
2. Click Provisioned ONTS > Ports > Static IP/Subnet.
3. In the menu, click the context drop-down list
to select the
ONT port where the service is provisioned of which you want to add a static IP host or
subnet.
4. Click Create to open the Create Ethernet Service IP/Subnet dialog box.
5. Reference the table above to configure the parameters.
6. Click Create.
For CLI:

add static-ip-entry to-ont-port <p-id> eth-svc <s-name> type host ip
<h-ip> netmask <n-ip> default-gw <gw-ip> [mac <m-address>]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
307


add static-ip-entry to-ont-port <p-id> eth-svc <s-name> type subnet ip
<sub-ip> netmask <n-ip> default-gw <gw-ip> [mac <m-address>]
show ont-port <port-id> eth-svc <s-name> static-ip-entry <index>
Configuring Voice Services
This section describes how to create voice services on E7 GPON ONTs.
Note: The T-series GPON ONTs only support SIP Gateway voice service.
IP Hosts For Voice Services
Each voice service option requires an IP host definition object that specifies an IP host
address for VoIP. (The definition references a tag action that specifies the classifying and
marking of packets from the subscriber port into the service VLAN.) Although an IP Host is
configured for each type of voice service on an ONT, it is not explicitly referenced when
creating a voice service because it applies to all voice services of the same type provisioned
on the ONT. However, you are given the option to modify the existing IP Host or replace it
with a new IP Host definition when using the Table view approach.
Topics Covered
This section covers the following topics in bold that are the last step of the overall GPON
services configuration process. The procedures in this section assume that you have
completed the processes in steps 1, 2, 3.
Step 1. Configure network uplinks for GPON services (on page 66)
Step 2. Create system profiles that support GPON applications (on page 110)
Step 3. Configure a PON (on page 231)
Step 4. Configure voice subscriber services

An overview of the E7 GPON voice services configuration process

Example provisioning of voice services

Configuring TDM gateway voice services from the Ports tag

Configuring TDM gateway voice service from the Services tag

Configuring SIP voice services from the Ports tab

Configuring SIP voice service from the Services tab

Configuring H.248 gateway voice services from the Ports tab

Configuring H.248 gateway voice service from the Services tab

Configuring MGCP voice service from the Ports tab

Configuring MGCP voice service from the Services tab
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
308
Related Topics
For guidance in filling in the provisioning forms necessary to configure voice services, see:

Example Voice Services Provisioning (on page 373)
For overviews of provisioning sequences where the steps in the overviews are linked to
supporting procedure topics, see:

Service Provisioning Overviews (on page 41)
Process Overview: Configuring SIP Voice Service on an ONT
The Calix E7 supports a SIP voice services option for GPON ONTs, where a native
IAD/SIP agent on the ONT converts ONT voice traffic to VoIP format for exchange via
SIP protocol. There are the following architectures for VoIP services management:

T-series ONTs use a SIP configuration file that requires an intake form be submitted to
Calix with the defined configuration parameters. This results in the creation of an
approved SIP configuration file from Calix that is then transferred to a server local to the
E7.
The T-series HGU ONTs always require a SIP configuration file to add a voice service.

P-series ONTs can use a SIP configuration file that has been created based on the Calix
VoIP template and sample file available with Calix P-Series VoIP Configuration File Template (version 1.20; for Calix 700 ONTs), and then transferred to server local to the E7.
Note: The P-series can also omit the SIP configuration file and base the service
provisioning exclusively on the E7 SIP Gateway Profile.
The Calix Application Note: Using the ONT VoIP Configuration File describes how to use the
following:



Calix T-Series XML VoIP configuration file (OMCI) to support the SIP Gateway per-line
VoIP provisioning method.
Calix P-Series FTP VoIP configuration file (OMCI) to support the SIP Gateway per-line
VoIP provisioning method.
Calix P-Series TFTP VoIP configuration file to configure Voice over IP (VoIP) services
on Calix 700 ONTs for Calix C7 and E7 GPON applications or Active Ethernet (AE)
operation (such as on E7 or B6 Ethernet OLTs).
The GigaCenter ONTs do not support the method of remote TFTP download of SIP
configuration. If you want to use a legacy SIP configuration file for voice provisioning on
GigaCenter ONTs, use the OMCI download of the SIP configuration file.
Note: The ONT must be reset to factory default values before downloading new
configuration files. This can be accomplished by either pressing and holding the reset button
for 20 seconds or using the EWI. T-Series ONTs will reset to factory default settings during
the "retrieve ONT configuration file" step if a prior non-default configuration file is present
in the ONT. Perform the "apply ONT configuration file" step as soon as possible after the
retrieve step to minimize service disruptions.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
309
SIP Remote Services Support for P-Series ONTs
For E7s running R2.3 and higher, Calix recommends that you convert lines over from the
SIP Remote Profile to the SIP Gateway Profile, eliminating the need for the remote SIP
VoIP configuration file downloaded via TFTP. Instead, you can use a reduced configuration
file that resides on the E7, and does not overlap any of the configuration parameters that are
in the SIP Gateway Profile and SIP service objects.
For compatibility to SIP services previously provisioned with software releases R2.2 and
lower, there is continued support for services using a remote SIP configuration file. For
example, if you have an existing remote SIP profile and you want it to be applied to a service,
the SIP gateway profile has a setting that can enable the remote SIP configuration file and
override the duplicate settings that are specified in the SIP gateway profile.
For guidance in filling in the provisioning forms necessary to configure voice services, see:

Example Voice Services Provisioning (on page 373)
Note: SIP Gateway is the only voice service supported on the T-series GPON ONTs.
IP Hosts For SIP Voice Services
Each voice service option requires an IP host definition object that specifies an IP host
address for VoIP. (The definition references a tag action that specifies the classifying and
marking of packets from the subscriber port into the service VLAN.) Additionally, the SIP
IP Host requires that the configuration-file instance is specified. This instance value must
match the value given when retrieving the SIP configuration file and applying it to the E7.
When an ONT enables more than one SIP voice port, all like services on the ONT are
assigned to the same SIP IP Host.
Instances 9 through 16 are used exclusively for VoIP files and can be specified either by
instance number alone or by "voip-<1 through 8>"
voip-1
voip-2
voip-3
voip-4
voip-5
voip-6
voip-7
voip-8
Instance for VoIP (9)
Instance for VoIP (10)
Instance for VoIP (11)
Instance for VoIP (12)
Instance for VoIP (13)
Instance for VoIP (14)
Instance for VoIP (15)
Instance for VoIP (16)
Procedure Assumptions
The following procedure assumes the following conditions:

The E7 unit and ONT have been upgraded to the latest software version. If necessary,
see:

Calix E7 Software Upgrade Guide
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
310

The SIP configuration file is created and transferred to a server local to the E7. If
necessary, see:

Calix Technical Assistance Center (TAC) regarding a T-Series Configuration
Parameter Definition Form

Calix Application Note: Using the 700 ONT VoIP Configuration File
Creating a Subscriber Service

Form view shows an expandable structure that allows you to create multiple
instances of different service types, by scrolling to selected ports on the ONT.

Table view shows the services currently provisioned on the selected ONT, and
allows you to create a single service of the selected type.
For information on creating a SIP configuration file, see the Calix Application Note: Using the
700 ONT VoIP Configuration File.
Note: Voice traffic is carried on expedited Class of Service 4. Since the SIP IP host is a
trusted entity on the ONT, it is assumed that a 1:N VLAN model will be used for voice
services.
Unsupported Switches
Calix provides a standard SIP test plan for service providers to test VoIP interoperability
with unsupported switches. If using a switch for which interoperability support by Calix is
not officially declared, Calix strongly recommends executing the test plan against the switch
prior to turning up VoIP users. Contact your Calix sales engineer for additional information.
Refer to the Calix Customer Test Plan: SIP Interoperability
https://portal.calix.com/portal/calixdocs/tools/SIP_Interop/SIP_Interop_Test_Plan.pdf for full
details and instructions.
Information you need
You must have the following information on hand to configure ONT SIP voice service:




SIP server and call feature information with which to populate a SIP configuration file
IP address of the TFTP server hosting the SIP configuration file
(Optional) IP addresses for ONT SIP lines (only if using a static IP addressing scheme)
SIP profile to use on the ONT Voice port.
Creating a SIP Voice Service from the Form View
This topic describes how to use the Form view to configure a SIP voice service.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
311
Note: When a profile is changed, all subscribers using that profile are affected. Profiles
cannot be deleted while they are in use. Profiles can also be reloaded for a specific ONT
Voice port from the Provisioned ONTs > Ports > Provisioning table view, select the
ONT Voice port, and then click Action > Restart SIP Service.
Information you need
You must have the following information on hand to configure ONT SIP voice service:


SIP profile to use for the service.
SIP server and call feature information
Parameters
You can provision the following parameters for a SIP service on an ONT port:
Parameter
Description
Valid Options
Subscriber ID
Subscriber ID information, such as phone number, or account
number.
String up to 27 characters
(blank) ‡
Description
Optional description field for the port, subscriber address, name,
or service.
String up to 27 characters
(blank) ‡
Type of voice service to add to the port.
SIP ‡, TDM, H.248,
MGCP
Service Type
Note: T-series ONTs only support SIP voice service.
SIP Profile*
User Name*
Name of SIP profile to apply to this port.

Use a SIP Gateway profile (SipGwProf:) for services that will
either use local provisioning, or a SIP configuration file that
is retrieved via OMCI and then applied to the ONT.

Use a Remote SIP profile (SIPProf:) for services that will
access a SIP configuration file that is located on a remote
FTP server.
User name for registration with the SIP server (it forms the
UserId field, left of the @ in the SIP URL).
Any established SIP
profile
text string
The “@” character is supported in the username for VDSL and
T-Series ONT SIP services.
Note: Calix P-Series ONTs do not support a username with an
@ sign.
Password*
The SIP registration password that matches the user name.
24-character text string,
with the exception of ! ' "
Universal Resource
Indicator*
This is the Universal Resource Indicator (URI) of the port.
text string up to 32
characters
If a local URI is "aaa@bbb", "aaa" is the telephone number
configured, and "bbb" is the domain name of the SIP server
configured.
Note: The "@bbb" portion of the URI is defined in the SIP
configuration file that is referenced in the SIP Profile.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
312
Parameter
Description
Enable SIP Config
File (Overrides Local
Provisioning)
For compatibility to SIP services previously provisioned with
software releases R2.2 and lower, there is continued support for
services using an existing TFTP configuration file for
management of the voice port. If you select the "Enable SIP
config file" checkbox, the service provisioning parameters in one
of the following SIP Configuration Files are used, rather than the
parameters that were configured locally.

E7 accesses a SIP configuration file that is located on a
remote FTP server.

E7 retrieves and then applies a SIP configuration file to an
ONT(s).
Valid Options
selected (use
configuration file),
unselected (use local
provisioning)‡
The TFTP file works in combination with the voice port
attributes. The following voice port attributes provisioned on the
E7 can be overridden by the attributes in the TFTP configuration
file:
Enable Caller ID

Selectable dial plan profile

Call Waiting Enable

Caller ID Enable

Three way calling Enable

T.38 Fax Relay

Message Waiting Indicator Enable

Direct Connect (Hot Line) and Direct Connect Timer (Warm
Line).
Enables or disables Caller ID feature.
Calling Number is provisionable via OMCI, Calling Name is
provisionable via xml.
Three-Way Calling
Msg Waiting
Indicator
select to enable,
clear to disable
Enables or disables Three-way Calling feature.
select to enable,
clear to disable
Whether to enable the audio and visual message indicator.
select to enable,
clear to disable
Note: T-series does not support OMCI provisioning of of this
feature. The indicator is always enabled.
Enable Direct
Connect
Whether to enable support for a Directory Number used for
Direct Connect (Hot Line) Services and Direct Connect Timer
(Warm Line).
select to enable,
clear to disable
Direct Connect
If Direct Contact support is enabled, enter a hot line number to
immediately dial after an off-hook event (for example, taxi/hotel
phones hanging on the walls of airports).
Number string between 015 numbers.
Direct-Connect
Timer
If Direct Contact support is enabled, optionally specify the delay
in seconds that the dial tone will be played before the Direct
Contact number command is dialed. This feature is known as
warm line support and may be used to redirect a call to a prerecorded message, a front desk operator, or an emergency
contact.
0‡ to 35

0 = Hotline services

non-zero values = Warmline services
Note: T-series does not support Warmline.
Dial Plan*
Number plan table for SIP VoIP service.
any available plans
Call Waiting
Enables or disables Call waiting feature.
select to enable,
clear to disable
T.38 Fax Relay
Enables or disables the T.38 fax relay feature. While E7 GPON
does support T.38 fax services, T.38 is controlled in the SIP
configuration file.
select to enable,
clear to disable
*Required fields
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
313
To create a SIP voice service
1. On the Navigation Tree, double-click ONTS.
2. In the work area, click the Provisioned ONTS > Services > Form.
3. From the drop-down list
at the top of the page, select the index
assigned to the ONT on which to add the service.
4. From the list of ONT ports, click the orange triangle
which to add the service.
next to the Voice-# port on
5. Reference the table above to configure the parameters.
6. Click Create to apply the service to the port.
For CLI:


add sip-svc to-ont-port <POTS port> sip-rmt-cfg-profile <sipr-profile>
user <user name> password <pswd> uri <URI ID> [sip-rmt-cfgoverride|call-waiting|caller-id|three-way-calling|t38-fax-relay|dialplan|admin-state]
set ont-port <port> sip-svc [sip-profile|user|password|uri|callwaiting|caller-id|t38-fax-relay|admin-state]

show ont-port <port-id> [detail|sip-svc]

restart ont-port <p-id> sip-svc

restart sip-profile <p-name> services
Configuring SIP Voice Services from the Table View
The Calix E7 supports a subscriber services activation page where you can provision any
possible service for any ONT configured in the E7 system.
This topic describes how to configure SIP voice services on GPON ONTs, using the E7
subscriber services page. The SIP voice services solution for GPON ONTs employs a native
IAD/SIP agent on the ONT that converts ONT voice traffic to VoIP format for exchange
via SIP protocol.
For information on creating a SIP configuration file, see the Calix Application Note: Using the
700 ONT VoIP Configuration File.
Note: When a profile is changed, all subscribers using that profile are affected. Profiles
cannot be deleted while they are in use. Profiles can also be reloaded for a specific ONT
Voice port from the Provisioned ONTs > Ports > Provisioning table view, select the ONT
Voice port, and then click Action > Restart SIP Service.
Note: Voice traffic is carried on expedited Class of Service 4. Since the SIP IP host is a
trusted entity on the ONT, it is assumed that a 1:N VLAN model will be used for voice
services.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
314
Information you need
You must have the following information on hand to configure ONT SIP voice service:




SIP server and call feature information with which to populate a SIP configuration file
IP address of the TFTP server hosting the SIP configuration file (only if not using local
provisioning)
(Optional) IP addresses for ONT SIP lines (only if using a static IP addressing scheme)
SIP profile to use on the ONT voice (POTS) port.
Parameters
You can provision the following SIP voice service parameters accessed from the Services
page:
Parameter
Description
Valid Options
Subscriber Port
Subscriber Port*
System address of the ONT port where the subscriber services will be
provisioned.
Any ONT Voice port
Subscriber ID
Subscriber ID information, such as phone number, or account number.
String up to 27 characters
(blank) ‡
Description
Optional description field for the port, subscriber address, name, or
service.
String up to 27 characters
(blank) ‡
Create SIP Service
SIP Profile*
Name of the SIP profile to use.
Any established SIP
profile
User Name*
User name for registration with the SIP server (it forms the UserId field,
left of the @ in the SIP URL).
text string
The “@” character is supported in the username for VDSL and T-Series
ONT SIP services.
Note: Calix P-Series ONTs do not support a username with an @ sign.
Dial Plan
Number plan table for SIP VoIP service.
Any established dial plan
Note: Although the dial plans are named upon creation, the selection of
the dial plan to use in the SIP profile is indicated by an index. To identify
the index of a dial plan, double-click the plan name in the Profiles >
Service > Dial Plan table.
Universal Resource
Indicator*
Password*
This is the Universal Resource Indicator (URI) of the port.
If a local URI is "aaa@bbb", "aaa" is the telephone number configured,
and "bbb" is the domain name of the SIP server configured. Note: The
"@bbb" portion of the URI is defined in the SIP configuration file that is
referenced in the SIP Profile.
The SIP registration password that matches the user name.
text string up to 32
characters
24-character text string,
with the exception of ! ' "
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
315
Parameter
Description
Enable SIP Config
File (Overrides local
provisioning)
For compatibility to SIP services previously provisioned with software
releases R2.2 and lower, there is continued support for services using
an existing TFTP configuration file for management of the voice port. If
you select the "Enable SIP config file" checkbox, the service
provisioning parameters in one of the following SIP Configuration Files
are used, rather than the parameters that were configured locally.

E7 accesses a SIP configuration file that is located on a remote FTP
server.

E7 retrieves and then applies a SIP configuration file to an ONT(s).
Valid Options
selected (use
configuration file),
unselected (use local
configuration)‡
The TFTP file works in combination with the voice port attributes. The
following voice port attributes provisioned on the E7 can be overridden
by the attributes in the TFTP configuration file:

Selectable dial plan profile

Call Waiting Enable

Caller ID Enable

Three way calling Enable

T.38 Fax Relay

Message Waiting Indicator Enable

Direct Connect (Hot Line) and Direct Connect Timer (Warm Line).
Enable Caller ID
Enables or disables Caller ID feature.
select to enable,
clear to disable
Three-way calling
Enables or disables Three-way Calling feature.
select to enable,
clear to disable
Msg Waiting
Indicator
Whether to enable the audio and visual message indicator.
select to enable,
clear to disable
Note: T-series does not support OMCI provisioning of of this feature.
The indicator is always enabled.
Enable Direct
Connect
Whether to enable support for Direct Connect (Hot Line) and Direct
Connect Timer (Warm Line)
select to enable,
clear to disable
Direct Connect
If Direct Contact support is enabled, enter a hot line number to
immediately dial after an off hook event (for example, taxi/hotel phones
hanging on the walls of airports).
Number string between 015 numbers.
Direct Connect Timer
If Direct Contact support is enabled, optionally configure the delay in
seconds before the Direct Contact number command is dialed. This
feature is known as warm line support and may be used to redirect a
call to a pre-recorded message, a front desk operator, or an emergency
contact.
0‡-35
Call Waiting
Enables or disables Call Waiting feature: Accept the new call and put
the current call on hold.
select to enable,
clear to disable
T.38 Fax Relay
Enables or disables the T.38 fax relay feature. While E7 GPON does
support T.38 fax services, T.38 is controlled in the SIP configuration file.
select to enable,
clear to disable
Host Protocol
Host protocol for the SIP client. If you select "static," you must also
enter a static IP address, mask, and gateway addresses.
static
dhcp
Static IP
IP address statically assigned to the ONT if the host protocol is static.
This attribute is ignored, yet preserved, if the host protocol is DHCP.
4-byte IP address
Static IP Mask
IP network mask assigned to the ONT if the host protocol is static. This
attribute is ignored, yet preserved, if the host protocol is DHCP.
4-byte IP address
Static IP Gateway
Static IP gateway 4-byte address for the ONT to use in routing its traffic
to the SIP server, if the host protocol is static. This attribute is ignored,
yet preserved, if the host protocol is DHCP.
4-byte IP address
Service Tag Action
Name of service tag action or "none" for no service tag action. IP host
traffic is always untagged.
index-name of tag action
Update IP Host
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
316
Parameter
Description
Valid Options
Outer Tag
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
Inner Tag
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
Config-file Instance
Instances 9 through 16 are used exclusively for VoIP configuration files
and can be specified either by instance number alone or by “voip-<1
through 8>.”
None ‡, voip1-8, enter
value

voip-1
- Instance for VoIP (9)

voip-2
- Instance for VoIP (10)

voip-3
- Instance for VoIP (11)

voip-4
- Instance for VoIP (12)

voip-5
- Instance for VoIP (13)

voip-6
- Instance for VoIP (14)

voip-7
- Instance for VoIP (15)

voip-8
- Instance for VoIP (16)
Note: The instance specified in the SIP IP Host must match the
instance specified in the Retrieve ONT Configuration File operation.
*Required fields
‡ Default
To create a SIP voice service
1. On the Navigation Tree, click ONTS.
2. In the Work Area, click Provisioned ONTS > Services > Form.
3. From the drop-down list
at the top of the page, select the index
assigned to the ONT on which to add the service.
4. From the menu, click Create > SIP Service to open the Create dialog box.
5. Reference the table above to configure the parameters.
6. Click Create to apply the service to the port.
For CLI:
add sip-svc to-ont-port <POTS port> sip-profile <s-profile> user <user name>
password <pswd> uri <URI ID> [sip-rmt-cfg-override|call-waiting|callerid|three-way-calling|t38-fax-relay|admin-state]
set ont-port <port> sip-svc [sip-profile|user|password|uri|admin-state]
show ont-port <port-id> [detail|sip-svc]
restart ont-port <p-id> sip-svc
restart sip-profile <p-name> services

If the ip-host is set to dhcp, the static-ip, static-netmask, and static-gw addresses are
ignored, yet preserved.

If the ip-host is set to static, you must also enter the static-ip, static-netmask, and
static-gw addresses.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
317
Process Overview: Configuring TDM Gateway Voice Service on an ONT
The Calix E7 supports a TDM voice services option using a Calix C7 voice gateway to the
PSTN. The TDM gateway solution employs VoIP between the Calix P-Series ONTs and the
C7 voice gateway, which converts voice traffic back to TDM format for exchange on the
PSTN. This topic describes how to configure TDM gateway voice service on P-Series
GPON ONTs.
Note: For TDM gateway services, you can use the C7 gateway's internal DHCP server to
provide IP addresses for the E7 ONT VoIP hosts (recommended), or use an external DHCP
server option (requires Option 43 parameters included in the DHCP Offer). Also, the E7
GPON only supports a single VoIP Interface Group for P-Series ONTs (700GE/GX,
although the GX ONTs support multiple VoIP IP Hosts).
See Overview: GPON Voice Services (on page 59) for the sequence of procedures for configuring
the E7 and P-series GPON ONTs voice services.
TDM Gateway Service Group
For C7 TDM Gateway service, you must configure the SIP voice concentration group (SIP
VCG) on the C7 network and add a VoIP connection to the E7. For details, see the Calix C7
VoIP Services Guide. If you use CMS to provision a C7 TDM Gateway service, you can specify
the CSIP VCG in a TDM Gateway Service Group that is referenced when you activate the
service.
You can create a TDM Gateway Service Group that defines the C7 network and interface
groups used for delivering the TDM Gateway service, allowing CMS to automatically create
and validate C7 gateway cross-connects. See TDM Gateway Service Group (on page 216) for
instructions.
Profiles referenced in service provisioning

If you use CMS to provision a TDM Gateway service and then make changes to the E7
provisioning, bypassing CMS, a message displays indicating that the provisioning in CMS
and E7 is not in a synchronized state. To remedy the situation, click ONTs from the
CMS Navigation Tree, select the affected ONT, click the affected voice port, click
Action > Override TDM Service, and then select the set of parameters that you want
to apply to the TDM Gateway service on the ONT port.

Select With CMS Settings to apply the current settings in CMS to the TDM
Gateway service on the voice port.

Select With Network Settings to replace the CMS settings for the TDM Gateway
service on the voice port with the settings from the E7.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
318

For C7 TDM Gateway service, you must configure the SIP voice concentration group
(SIP VCG) on the C7 network and add a VoIP connection to the E7. For details, see the
Calix C7 VoIP Services Guide. If you use CMS to provision C7 TDM Gateway service, you
specify the CSIP VCG in the TDM Gateway Service Group that is referenced in the
Services screen when you activate service.
TDM Gateway Service Report in CMS
CMS allows you to run a database search for provisioned TDM Gateway services on a multiplatform basis, and then generate a report on the results.
Do one of the following, depending on whether you have CMS Desktop or CMS Web open:


(CMS Desktop) On the Tools menu, click Search > Multi-Platform > TDM Service,
and then click Submit.
(CMS Web) Open CMS Web. In the Module list on the left, click Configuration >
Multi-Platform > TDM Service.
Creating a Subscriber Service


Form view shows an expandable structure that allows you to create multiple instances of
different service types, by scrolling to selected ports on the ONT.
Table view shows the services currently provisioned on the selected ONT, and allows
you to create a single service of the selected type.
Information you need
You must have the following information on hand to configure ONT TDM Gateway voice
service:



TDM Gateway profile to use on the ONT Voice port
Service Group to define the C7 network and interface groups used for delivering the
TDM Gateway service (available through CMS only)
Call Reference Value (CRV) identifiers to use for the subscriber voice line, as provisioned
on the Calix C7 gateway interface group (case sensitive). For example, N1-1-IG1-224.
Creating a TDM Gateway Voice Service from the Form View
This topic describes how to use the Ports tab to configure a TDM Gateway voice service by
appying the following previously-created profiles:


TDM gateway profile
TDM gateway service group (optional)
Use the same screen to disable Voice ports.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
319
Information you need
You must have the following information on hand to configure ONT TDM Gateway voice
service:



TDM Gateway profile to use on the ONT Voice port
Call Reference Value (CRV) identifiers to use for the subscriber voice line
Service Group to define the C7 network and interface groups used for delivering the
TDM Gateway service (available through CMS only)
Parameters
You can provision the following parameters for TDM Gateway voice service on an ONT
Voice (POTS) port:
Parameter
Description
Valid Options
TDM Gateway
Profile*
Name of the TDM Gateway profile to use for the service.
Any established TDM
Gateway profile
Service Group
(via CMS only)
(Optional) Defines the C7 network and interface groups used for delivering
theTDM Gateway service, allowing CMS to automatically create and
validate C7 gateway cross-connects.
Any global TDM Service
Group established from
CMS
Note: If you do not reference a service group, you must configure the SIP
voice concentration group (SIP VCG) on the C7 network and add a VoIP
connection to the E7. For details, see the Calix C7 VoIP Services Guide.
Call Reference
Value*
Call Reference Value (CRV) identifies the subscriber line in the (GR-303
or TR-8) switch interface group. Enter the CRV number for this subscriber
line, as provisioned on the Calix C7 gateway interface group (case
sensitive). For example, N1-1-IG1-224. This CRV ID must be provisioned
on the CRVs used to build translation tables on the Class 5 switch that
map remote connections to internal circuits at the switch.
Any available CRV
number on the IG at the
C7 gateway - Note:
Format is case sensitive.
CRV MUST be in upper
case.
Administrative
Status
Administrative state of the service.
enabled ‡
disabled
enabled-no-alarms
*Required fields
‡ Default
To create a TDM gateway voice service
1. On the Navigation Tree, click ONTS.
2. In the list of linked ONTs, click the ONT to configure, and then click the Ports tab to
view its ports.
3. From the list of ONT ports, double-click the ONT Voice port on which to add services.
4. From the menu, click Create > TDM Gateway Service.
5. Reference the table above to configure the parameters.
6. Click Create to apply the service to the port.
7. To verify the service operation, click the Provisioning tab for the voice port. If service is
operational, you will see a Service Status of registered.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
320
For CLI:
add tdm-gw-svc to-ont-port <ont port> tdm-gw-profile <profile name> crv <crvstring> [admin-state <state>]
Example:

add tdm-gw-svc to-ont-port 1/p1 tdm-gw-profile VOICE crv N1-1-IG1-224
admin-state enabled

set ont-port <port> tdm-gw-svc [tdm-gw-profile|crv|admin-state]

show ont-port <port-id> [detail|tdm-gw-svc]
Creating TDM Gateway Voice Service from the Table View
This topic describes how to use the Services tab to configure a TDM Gateway voice service
from applying previously-created profiles:


TDM gateway profile
TDM gateway service group
Use the same screen to disable Voice ports.
Information you need
You must have the following information on hand to configure ONT TDM Gateway voice
service:



TDM Gateway profile to use on the ONT Voice port
Call Reference Value (CRV) identifiers to use for the subscriber voice line
Service Group to define the C7 network and interface groups used for delivering the
TDM Gateway service (available through CMS only)
Parameters
You can provision the following TDM Gateway voice service parameters accessed from the
Services page:
Parameter
Description
Valid Options
Subscriber Port
Subscriber Port*
Subscriber ID
System address of the ONT port where the subscriber services will be
provisioned.
Any ONT Voice port
Subscriber ID information, such as phone number, or account number.
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
Description
Optional description field for the port, subscriber address, name, or
service.
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Description entry from the
ONT provisioning record to this field.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
321
Parameter
Description
Valid Options
Create TDM Gateway Service
TDM Gateway
Profile*
Service Group (via
CMS only)
Name of the TDM Gateway profile to use.

If the assigned Service Group has a referenced TDM Gateway
Profile, you can override that selection, using this field.

If the assigned Service Group does NOT have a referenced TDM
Gateway Profile, you must select a profile from this field.
(Optional) Name of the TDM Service Group used to define the Calix C7
gateway interface group.
Any established TDM
Gateway profile
Any established TDM
Service Group
Note: If you do not reference a service group, you must configure the
SIP voice concentration group (SIP VCG) on the C7 network and add a
VoIP connection to the E7. For details, see the Calix C7 VoIP Services
Guide.
Call Reference
Value*
Call Reference Value (CRV) identifies the subscriber line, as
provisioned on the Calix C7 gateway interface group (case sensitive).
For example, N1-1-IG1-224. This CRV ID must be provisioned on the
CRVs used to build translation tables on the Class 5 switch that map
remote connections to internal circuits at the switch.
Any available CRV
number on the IG at the
C7 gateway - Note: The
CRV MUST be in upper
case.
Update TDM Gateway IP Host
Host Protocol
Host protocol for the SIP client. If you select "static," you must also
enter a static IP address, mask, and gateway addresses.
static
dhcp
If you set the Host Protocol to dhcp, any values set for the Static-IP,
Static IP Mask, and Static IP Gateway addresses are ignored, yet
preserved.
Static IP
IP address statically assigned to the ONT if the host protocol is static.
This attribute is ignored, yet preserved, if the host protocol is
subsequently switched to DHCP.
4-byte IP address
Note: The static IP address must not be the same as the gateway
address.
Static IP Mask
IP network mask assigned to the ONT if the host protocol is static. This
attribute is ignored, yet preserved, if the host protocol is subsequently
switched to DHCP.
4-byte IP address
Static IP Gateway
Static IP gateway 4-byte address for the ONT to use in routing its traffic
to the SIP server, if the host protocol is static. This attribute is ignored,
yet preserved, if the host protocol is subsequently switched to DHCP.
4-byte IP address
Note: The gateway address and subtending IP addresses must belong
to the same subnet, as indicated by the mask.
Svc Tag Action
Name of service tag action or "none" for no service tag action. IP host
traffic is always untagged.
index-name of tag action
S-VLAN (Outer Tag)
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
C-VLAN (Inner Tag)
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
*Required fields
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
322
To create a TDM gateway service
1. On the Navigation Tree, click ONTS.
2. In the work area, click Provisioned ONTS > Services.
3. From the menu, click Create > TDM Gateway Service to open the Create dialog box.
4. Reference the table above to configure the parameters.
5. Click Create to activate a TDM Gateway voice service on the subscriber port.
For CLI:
add tdm-gw-svc to-ont-port <ont port> tdm-gw-profile <profile name> crv <crvstring> [admin-state <state>]
Example:

add tdm-gw-svc to-ont-port 1/p1 tdm-gw-profile VOICE crv N1-1-IG1-224
admin-state enabled

set ont-port <port> tdm-gw-svc [tdm-gw-profile|crv|admin-state]

show ont-port <port-id> [detail|tdm-gw-svc]
Process Overview: Configuring H.248 Voice Service on an ONT
This section describes how to configure H.248 Gateway voice services on P-series GPON
ONTs. The T-series ONTs do not support the H.248 voice service.
Note: Voice traffic is carried on expedited Class of Service 4. Since the H.248 Gateway IP
host is a trusted entity on the ONT, it is assumed that a 1:N VLAN model will be used for
voice services.
See Overview: GPON Voice Services (on page 59) for the sequence of procedures for configuring
the E7 and P-series GPON ONTs voice services.
Creating a Subscriber Service


Form view shows an expandable structure that allows you to create multiple instances of
different service types, by scrolling to selected ports on the ONT.
Table view shows the services currently provisioned on the selected ONT, and allows
you to create a single service of the selected type.
Information you need
You must have the following information on hand to configure ONT H.248 Gateway voice
service:


(Optional) IP addresses for ONT lines (only if using a static IP addressing scheme)
H.248 Gateway profile to use on the ONT Voice port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
323
Creating an H.248 Voice Service from the Form View
This topic describes how to configure an H.248 voice service from the Ports tab.
Information you need
You must have the following information on hand to configure ONT H.248 Gateway voice
service:


(Optional) IP addresses for ONT lines (only if using a static IP addressing scheme)
H.248 gateway profile to use on the ONT Voice port
Media gateway considerations
There is a default inactivity timeout of 25 seconds in the Media Gateway (MG) to determine
when the MG to Media Gateway Controller (MGC) association is down. Under normal
operation, there is a keep alive heartbeat/polling interval that is initiated by the MGC to the
MG. If the interval value is longer than 25 seconds, the E7 reports an alarm condition.
Therefore, the MGC (H.248 switch) must have a polling interval less than 25 seconds to
avoid the E7 alarm condition described.
Parameters
You can provision the following parameters for an H.248 Gateway service on an ONT port:
Parameter
Description
Valid Options
Gateway Profile*
The name of the H.248 gateway profile to use for the service.
any existing H.248
profile
Termination ID*
The ID to use for ephemeral terminations.
text string, 0-48
characters
Administrative Status
Administrative state of the service.
enabled
disabled
enabled-no-alarms
*Required fields
To create an H.248 gateway voice service
1. On the Navigation Tree, double-click ONTS.
2. In the list of linked ONTs, double-click the ONT to configure, and then click the Ports
tab to view its ports.
3. From the list of ONT ports, double-click the ONT Voice port on which to add services.
4. From the menu, click Create > H.248 Gateway Service.
5. Reference the table above to configure the parameters.
6. Click Create to apply the service to the port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
324
For CLI:



add h248-gw-svc to-ont-port <port> h248-gw-profile <p-name>
termination-id <string> [admin-state]
set ont-port <port> h248-gw-svc [h248-gw-profile|termination-id|adminstate] [subscriber-id|description|speed|duplex|eth-sec-profile|onteth-gos|ont-t1-gos|line-code|line-length|line-length-metric|loopbackmode|in-band-loopback|impedance|disable-on-batt|signal-type|adminstate]
show ont-port <port-id> [detail|h248-gw-svc]
Configuring H.248 Voice Service from the Table View
The Calix E7 supports a subscriber services activation page where you can provision any
possible service for any ONT configured in the E7 system.
This topic describes how to configure H.248 Gateway voice services on GPON ONTs, using
the E7 subscriber services page.
Note: Voice traffic is carried on expedited Class of Service 4. Since the H.248 gateway IP
host is a trusted entity on the ONT, it is assumed that a 1:N VLAN model will be used for
voice services.
Information you need
You must have the following information on hand to configure ONT H.248 Gateway voice
service:


(Optional) IP addresses for ONT lines (only if using a static IP addressing scheme)
H.248 gateway profile to use on the ONT Voice port
Media gateway considerations
There is a default inactivity timeout of 25 seconds in the Media Gateway (MG) to determine
when the MG to Media Gateway Controller (MGC) association is down. Under normal
operation, there is a keep alive heartbeat/polling interval that is initiated by the MGC to the
MG. If the interval value is longer than 25 seconds, the E7 reports an alarm condition.
Therefore, the MGC (H.248 switch) must have a polling interval less than 25 seconds to
avoid the E7 alarm condition described.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
325
Parameters
You can provision the following H.248 gateway voice service parameters accessed from the
Services page:
Parameter
Description
Valid Options
Subscriber Port
Subscriber Port*
System address of the ONT port where the subscriber services will be
provisioned.
Any ONT Voice port
Subscriber ID
Subscriber ID information, such as phone number, or account number.
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
Description
Optional description field for the port, subscriber address, name, or
service.
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Description entry from the
ONT provisioning record to this field.
Create H.248 Gateway Service
H.248 Gateway
Profile*
Name of the H.248 Gateway profile to use for the service.
Any established H.248
gateway profile
Termination ID*
H.248 termination ID.
text string
Host Protocol
Host protocol for the H.248 gateway client. If you select "static," you
must also enter a static IP address, mask, and gateway addresses.
static
dhcp
Static IP
IP address statically assigned to the ONT if the host protocol is static.
This attribute is ignored, yet preserved, if the host protocol is
subsequently switched to DHCP.
4-byte IP address
Update H.248 Gateway IP Host
Note: The static IP address must not be the same as the gateway
address.
Static IP Mask
IP network mask assigned to the ONT if the host protocol is static. This
attribute is ignored, yet preserved, if the host protocol is subsequently
switched to DHCP.
4-byte IP address
Static IP Gateway
Static IP gateway 4-byte address for the ONT to use in routing its traffic
to the SIP server, if the host protocol is static. This attribute is ignored,
yet preserved, if the host protocol is subsequently switched to DHCP.
4-byte IP address
Note: The gateway address and subtending IP addresses must belong
to the same subnet, as indicated by the mask.
Service Tag Action
Name of service tag action or "none" for no service tag action. IP host
traffic is always untagged.
index-name of tag action
S-VLAN (Outer Tag)
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
C-VLAN (Inner Tag)
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
*Required fields
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
326
To create an H.248 Gateway voice service
1. On the Navigation Tree, click ONTS.
2. In the work area, click Provisioned ONTS > Services.
3. From the menu, click Create > H.248 Gateway Service to open the Create dialog box.
4. Reference the table above to configure the parameters.
5. Click Create to activate an H.248 Gateway voice service on the subscriber port.
For CLI:



add h248-gw-svc to-ont-port <port> h248-gw-profile <p-name>
termination-id <string> [admin-state]
set ont-port <port> h248-gw-svc [h248-gw-profile|termination-id|adminstate] [subscriber-id|description|speed|duplex|eth-sec-profile|onteth-gos|ont-t1-gos|line-code|line-length|line-length-metric|loopbackmode|in-band-loopback|impedance|disable-on-batt|signal-type|adminstate]
show ont-port <port-id> [detail|h248-gw-svc]
Process Overview: Configuring MGCP Voice Service on an ONT
This section describes how to configure MGCP Gateway voice services on GPON ONTs.
The TDM gateway option interoperates with B6-640 for MGCP VoIP to TDM switch
interface translation (GR-303 and TR-08).
E7 supports VoIP interoperability for the following:


MGCP voice interface with MetaSwitch
MGCP voice interface with GENBAND C15
Note: Voice traffic is carried on expedited Class of Service 4. Since the MGCP Gateway IP
host is a trusted entity on the ONT, it is assumed that a 1:N VLAN model will be used for
voice services.
See Overview: GPON Voice Services (on page 59) for the sequence of procedures for configuring
the E7 and P-series GPON ONTs voice services.
Note: Voice traffic is carried on expedited Class of Service 4. Since the MGCP Gateway IP
host is a trusted entity on the ONT, it is assumed that a 1:N VLAN model will be used for
voice services.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
327
Creating a Subscriber Service


Form view shows an expandable structure that allows you to create multiple instances of
different service types, by scrolling to selected ports on the ONT.
Table view shows the services currently provisioned on the selected ONT, and allows
you to create a single service of the selected type.
Information you need
You must have the following information on hand to configure ONT MGCP Gateway voice
service:


(Optional) IP addresses for ONT lines (only if using a static IP addressing scheme)
MGCP Gateway profile to use on the ONT Voice port.
Creating an MGCP Voice Service from the Form View
This topic describes how to configure an MGCP voice service on an ONT Voice (POTS)
port.
Profiles referenced in service provisioning
When provisioning subscriber services on an ONT port, you set up information that is
common to multiple subscribers and maintained in profiles. Repeating the similar task of
subscriber service activation then consists of referencing the existing profiles and sometimes
providing subscriber-specific information to complement the profiles.
Note: When a profile is changed, all subscribers using that profile are affected. Profiles
cannot be deleted while they are in use.
Information you need
You must have the following information on hand to configure ONT MGCP Gateway voice
service:


(Optional) IP addresses for ONT lines (only if using a static IP addressing scheme)
MGCP gateway profile to use on the ONT Voice port
Parameters
You can provision the following parameters for an MGCP Gateway service on an ONT port:
Parameter
Description
Valid Options
Gateway Profile*
The name of the MGCP gateway profile to use for the service.
any existing MGCP
profile
Termination ID
The ID to use for ephemeral terminations. This value is
populated, based on the subscriber port selected for adding the
service. For example, when voice port 7 is selected, the
Termination ID = 7.
text string
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
328
Parameter
Description
Valid Options
Administrative Status
Administrative state of the service.
enabled
disabled
enabled-no-alarms
GR 303
For GR303 Option, only used for B6 TDM Gateway support.
Enables use of the MGCP and RFC 2833 voice control protocol
compatible with the B6-640 Trunking Gateway (TGW) in GR-303
mode.
enabled (selected),
disabled (unselected)
*Required fields
To create an MGCP gateway voice service
1. On the Navigation Tree, double-click ONTS.
2. In the list of linked ONTs, double-click the ONT to configure, and then click the Ports
tab to view its ports.
3. From the list of ONT ports, double-click the ONT Voice port on which to add services.
4. From the menu, click Create > MGCP Service.
5. Reference the table above to configure the parameters.
6. Click Create to apply the service to the port.
For CLI:

add mgcp-svc to-ont-port <POTS port> mgcp-profile <mgcp-profile> [gr303|admin-state]

set ont-port <port> mgcp-svc [mgcp-profile|gr-303|admin-state]

show ont-port <port-id> [detail|mgcp-svc]
Configuring MGCP Voice Service from the Table View
The Calix E7 supports a subscriber services activation page where you can provision any
possible service for any ONT configured in the E7 system.
This topic describes how to configure MGCP Gateway voice services on GPON ONTs,
using the E7 subscriber services page. Optionally, you can configure an MGCP Gateway
voice service from the Ports tab.
The TDM gateway option interoperates with B6-640 for MGCP VoIP to TDM switch
interface translation (GR-303 and TR-08).
E7 supports VoIP interoperability for the following:


MGCP voice interface with MetaSwitch
MGCP voice interface with GENBAND C15
Note: Voice traffic is carried on expedited Class of Service 4. Since the MGCP gateway IP
host is a trusted entity on the ONT, it is assumed that a 1:N VLAN model will be used for
voice services.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
329
Information you need
You must have the following information on hand to configure ONT MGCP Gateway voice
service:


(Optional) IP addresses for ONT lines (only if using a static IP addressing scheme)
MGCP gateway profile to use on the ONT Voice port
Parameters for MGCP gateway voice service at Services page
Parameter
Description
Valid Options
Subscriber Port
Subscriber Port*
Subscriber ID
System address of the ONT port where the subscriber services will be
provisioned.
Any ONT Voice port
Subscriber ID information, such as phone number, or account number.
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
Description
Optional description field for the port, subscriber address, name, or
service.
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Description entry from
the ONT provisioning record to this field.
Create MGCP Gateway Service
MGCP Gateway
Profile*
Name of the MGCP Gateway profile to use.
Any established MGCP
gateway profile
Termination ID*
MGCP termination ID. This value is populated, based on the subscriber
port selected for adding the service. For example, when voice port 7 is
selected, the Termination ID = 7.
text string
Host Protocol
Host protocol for the MGCP gateway client. If you select "static," you
must also enter a static IP address, mask, and gateway addresses.
static
dhcp
Static IP
IP address statically assigned to the ONT if the host protocol is static.
This attribute is ignored, yet preserved, if the host protocol is DHCP.
4-byte IP address
Update MGCP Gateway IP Host
Note: The static IP address must not be the same as the gateway
address.
Static IP Mask
IP network mask assigned to the ONT if the host protocol is static. This
attribute is ignored, yet preserved, if the host protocol is DHCP.
4-byte IP address
Static IP Gateway
Static IP gateway 4-byte address for the ONT to use in routing its traffic
to the SIP server, if the host protocol is static. This attribute is ignored,
yet preserved, if the host protocol is DHCP.
4-byte IP address
Note: The gateway address and subtending IP addresses must belong
to the same subnet, as indicated by the mask.
Service Tag Action
Name of service tag action or "none" for no service tag action. IP host
traffic is always untagged.
index-name of tag action
S-VLAN (Outer Tag)
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
C-VLAN (Inner Tag)
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
*Required fields
‡ Default
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
330
To create an MGCP Gateway voice service
1. On the Navigation Tree, click ONTS.
2. In the work area, click Provisioned ONTS > Services.
3. From the menu, click Create > MGCP Gateway Service to open the Create dialog box.
4. Reference the table above to configure the parameters.
5. Click Create to activate an MGCP Gateway voice service on the subscriber port.
For CLI:



add mgcp-svc to-ont-port <POTS port> mgcp-profile <mgcp-profile> [gr303|admin-state]
set ont-port <port> mgcp-svc [mgcp-profile|termination-id|admin-state]
[subscriber-id|description|speed|duplex|eth-sec-profile|ont-ethgos|ont-t1-gos|line-code|line-length|line-length-metric|loopbackmode|in-band-loopback|impedance|disable-on-batt|signal-type|adminstate]
show ont-port <port-id> [detail|mgcp-svc]
Configuring RF Overlay Video Services
This section describes how to create RF overlay video services on E7 GPON ONTs.
Topics Covered
This section covers the following topics in bold that are the last step of the overall GPON
services configuration process. The procedures in this section assume that you have
completed the processes in steps 1, 2, 3.
Step 1. Configure network uplinks for GPON services (on page 66)
Step 2. Create system profiles that support GPON applications (on page 110)
Step 3. Configure a PON (on page 231)
Step 4. Configure RF overlay video subscriber services

About RF overlay video services

About RF overlay video services with RF return path

Configuring RF overlay video services on an ONT RF port
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
331
Process Overview: Configuring GPON RF Overlay Video Services
The E7 system and GPON cards allow third-party overlay components to add RF video
functionality to the PON. The RF signals do not traverse the E7 line card, and therefore do
not consume system resources. For more information, see Calix GPON RF Overlay Deployment
Guidelines.
Before starting
Before starting the configuration process, check that the following conditions are met:


The E7 and ONTs are installed and wired, and ONTs are turned up on a GPON port.
An EDFA amplifier has been set up to insert the analog video overlay signal onto the
PON.
Configuration process
The GPON RF overlay video services configuration process is as follows:
1. Verify that the analog video overlay signal is present on the PON.
2. Configure the AVO Profile.
3. Configure the ONT RF video port for service.
4. If applicable, configure the ONT RF return port for service (for ONTs equipped with
integrated RF return path only).
RF Video Overlay Delivery
The Calix E7 system and GPON card supports Radio Frequency (RF) overlay for Cable TV
(CATV) services over the 47 to 870 MHz band. The RF video overlay path requires the
following equipment:



RF Transmitter: This device is typically located in the central office. At the headend,
video signals are modulated (analog) or encoded (digital) into RF signals. These signals
are combined and sent to a transmitter and optically modulated onto a 1550 nm
wavelength optical signal.
EDFA Amplifier: This device accepts the optical signal from the transmitter and
amplifies the signal so it can be split to support multiple PONs, increase the PON reach,
and deliver adequate signal to noise ratio at the consumer TV set.
Combiner: This device combines the 1550 nm overlay video optical signals with the
GPON 1490 nm forward path and 1310 nm reverse path, using CWDM passive optics
and transported over a single strand of fiber into a PON.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
332

ONT: Each ONT has an optical triplexer that performs electrical-to-optical conversion
(and vice versa) for the three bandwidth ranges supported by the GPON standards. The
three frequency ranges are used for downstream IP data (including IPTV signals),
upstream IP data, and RF video overlay (optional). The RF video signals are demodulated
and exit the ONT via a standard coaxial cable fitting (RG-58). The ONT operates as the
network interface device (NID) connecting the service provider network with the inhome wiring.
The following diagram shows the typical configuration of an overlay video network:
Note: Decreasing the number of splits increases the reach up to 40 km.
Refer to CAB-13-034 HPNA 3.1 Home Networking Guide for IPTV, RF Video, Whole-home
DVR, and Internet Access Applications for details.
RF Video Overlay with RF Return Path
The E7 can be used with Calix 700 ONTs featuring integrated RF Return supporting a 5 to
42 MHz return path frequency band. This RF Return solution enables bi-directional
communications between a set-top box, consumer electronics device, or cable modem.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
333
The design of the system uses a similar topology and identical set-top box hardware for
interactive services as current cable operators’ HFC technology and practices. The product
allows a single ONT for transport of both the forward and reverse RF paths, incorporates
power management per FSAN power shedding standards, and can be operated without the
GPON data link as a PON RF node for video and interactive set-top box services.
The Calix RF Return solution uses the 1610 nm wavelength as the return path from the
ONT to the headend. The ONT generates the optical signal and multiplexes the wavelength
with the PON signals. At the headend the 1610 nm wavelength is separated using the 4wavelength CWDM module. The 1610 nm signal is terminated on a standard high-gain HFC
reverse path optical receiver which demodulates it into an electrical RF signal, amplifies and
sets the signal level. At this stage the signal may be combined with other return path signals
depending on the aggregate number of set-top boxes to be supported. These combined
signals are fed into the RF return path demodulators located within the headend and
converted back into return path messages.
Refer to CAB-07-025, RF Return System Features and Planning Guidelines, for additional detail
regarding RF video overlay and RF return network characteristics and planning.
Configuration guidelines
For purposes of configuring the RF Return system, it is assumed that the following
conditions exist:



The planned RF Return network has previously deployed Analog Video Services using
the traditional 3-wavelength model.
That the SA Prisma II chassis has been previously installed and is functioning.
That an appropriately sized EDFA module has been installed and is functioning in the
chassis.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
334



That the following new equipment has been installed and is functional:

Headend 4-wavelength CWDM Module

SA Return Optical Receiver Module
That the 725 ONT has been installed and has been discovered on the network and that
the STB is receiving forward path OOB video signals from the headend.
That Local Craft Interface (LCI) software from Scientific Atlanta has been installed on
the network and can communicate with the Prisma II chassis. The software can be
downloaded from this site:
www.scientificatlanta.com/products/customers/iframe_EM_PrismaIILCI.htm


That the Out of Band (OOB) transmitter and Reverse Path Demodulator are
communicating with one or more set top boxes which are currently not on the ONT
network.
To facilitate the connectivity for the subtending STBs off of the return device, all security
must be disabled on the VLAN (no ip-source-verify). A Match List/Rule should be in
place with the src-mac of the return device and OUI as the src-mac-mask. See Creating a
Service Match List and Rules (on page 127). If ip-source-verify is enabled, the subtending
STBs will not work because their IP addresses are never learned by the system.
Note: For more comprehensive information on the Scientific-Atlanta RF Return solution,
refer to the Calix 725 ONT RF Return Configuration Guide.
Enabling RF Overlay Video Service
This topic describes how to create an RF video overlay service on an ONT.
Parameters
You can provision the following parameters on an ONT RF video overlay port or RF return
port:
Parameter
Description
Valid Options
Admin State
Administrative state of the port.
Enabled
Enabled-no-alarms
Disabled ‡
Subscriber ID
Subscriber ID information, such as name, address, or account
number.
String up to 27 characters
(blank) ‡
Description
Optional description field for the port or service .
String up to 27 characters
blank) ‡
Disable on
Battery
Port operational state when the ONT is operating on battery
backup power (during a power outage)
N (unselected) ‡
Y (selected)
RFoG Only

Y (yes) disables the port when the ONT operates on battery
during a power outage

N (no) maintains port operation
Enforces RFoG compliance for only Calix 725GE ONTs on an
E7-system basis.

Calix - Signal strength +20dBmV +/- 2 dB at 550MHz)

RFoG - complies with the SCTE RFoG requirements
RFoG only (selected)
Calix (unselected) ‡
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
335
Parameter
Description
Valid Options
Automatic Gain
Control
Sets automatic gain control on a per-system basis.
selected (enabled) ‡
unselected (disabled)
OMI Level
Optical modulation index level (%).
3.0 to 4.0
3.5 ‡
Low Signal
Threshold
A Per-System provisionable low signal threshold “Low Optical
Signal” alarm, based on the OSSI. This is the value for the low
signal threshold which when exceeded triggers an alarm.
–6 to –13 dBm
–6 dBm‡
RF Return State
Status of RF return path.
disabled ‡, enabled, force-uson, allow-long-bursts

enabled - enables RF return path

disabled - disables RF return path

force-us-on - forces upstream testing

allow-long-bursts- allows bursts over 1-second
‡ Default
To enable RF video overlay service from the ONT port
1. On the Navigation Tree, double-click ONTS.
2. In the list of linked ONTs, double-click the ONT to configure, and then click the Ports
tab to view its ports.
3. From the list of ONT ports, double-click the ONT RF video port on which to add
service.
4. Reference the table above to configure the parameters.
5. On the menu, click Apply to save changes.
Note: Some ONTs are equipped with a 'Hot' RF video port that provides a higher frequency
signal output for applications where a stronger signal is required, such as applications that use
an external signal splitter.
If the ONT is equipped with an integrated RF return port, enable the port for service as
described below.
To create an RF video overlay service from the services tab
1. On the Navigation Tree, double-click ONTS.
2. In the list of linked ONTs, double-click the ONT to configure, and then click the
Services tab.
3. Click Create > RF Service.
4. Reference the table above to configure the parameters.
5. Click Create.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
336
To configure profile and enable an RF return port for service
1. On the Navigation Tree, double-click ONTS.
2. In the Work Area, click Profiles > AVO Config.
3. Reference the table above to configure the parameters.
4. In the menu, click Apply.
5. Click provisioned Provisioned ONTs > Ports.
6. From the list of ONT ports, double-click the ONT RF return port to configure.
7. Reference the table above to configure the parameters.
8. On the menu, click Apply to save changes.
For CLI:

set avo-cfg <name> name <new-name>

show avo-cfg


set ont <ont ID> rf-avo rf-return-path [enabled|disabled|force-uson|allow-long|bursts] [pon-port|admin-state]
set ont-port <port> [eth-svc|pwe3-svc|sip-svc|tdm-gw-svc|subscriberid|description|speed|duplex|gos-profile|line-code|line-length|linelength-metric|loopback-mode|in-band-loopback|disable-on-batt|adminstate]
Configuring T1/E1 Services
This section describes how to create T1 or E1 data services on E7 GPON ONTs. You can
also provision services through CMS, using the Creating T1 Service from the Services Tab (on page
345) procedures.
Topics Covered
This section covers the following topics in bold that are the last step of the overall GPON
services configuration process. The procedures in this section assume that you have
completed the processes in steps 1, 2, 3.
Step 1. Configure network uplinks for GPON services (on page 66)
Step 2. Create system profiles that support GPON applications (on page 110)
Step 3. Configure a PON (on page 231)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
337
Step 4. Configure T1/E1 PWE3 subscriber services

Configuring an ONT T1 port for service

Configuring timing for GE ports of a GPON Card

Creating T1/E1 data services on an ONT T1 port

Configuring a PWE3 Service from the Services tab
Process Overview: Configuring GPON T1/E1 Services
The E7 supports T1 and E1 services over GPON and point-to-point Ethernet using
pseudowire emulation edge-to-edge (PWE3) technology which provides a standards-based
approach to T1 or E1 service delivery over a packet switched network.
The E7 supports T1 or E1 services on Calix ONTs equipped with T1 pseudowire ports (for
example, the 766GX ONT), where traditional T1 or E1 services are converted to packet
flows at the ONT and carried back to the E7, where they are delivered to a remote
pseudowire device that translates the packet stream back to the original T1 or E1 format.
Also see Calix T1 Pseudowire Applications.
About De-multiplexing PWE3 services
The available transport modes for E7 PWE3 services are UDP-IP and MEF.
All UDP demultiplexing options conform to Mode 3 added for clarification RFC 5086
(CESoPSN) and Mode 1 added for clarification RFC 5087 (TDMoIP). MEF options
conform to the ECIDs (Emulated Circuit IDs).




Either the local (source) UDP port or remote (destination) UDP port may be used to
multiplex and de-multiplex individual PWs between nodes, resulting in the UDP port
acting as the PW Label.
PWE endpoints MUST agree upon use of either the source UDP or destination UDP
port as the PW Label.
The configured source or destination port (one or the other, but not both) together with
both the source and destination IP addresses uniquely identify the PW.
All UDP de-multiplexing options conform to RFC 5086 (CESoPSN) and RFC 5087
(TDMoIP).
Note: Calix recommends using the RFC 5086 method for de-multiplexing. This method
requires that the remote (destination) UDP port always be specified, avoiding port 2142.
CESoPSN Mode (RFC 5086):


The destination UDP port is used to multiplex and de-multiplex individual PWEs
between nodes, resulting in the destination UDP port acting as the PW Label.
The configured destination port, together with both the source and destination IP
addresses, uniquely identifies the PW for the receiver.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
338
TDMoIP Mode (RFC 5087):



When the source UDP port is used as the PW label, the destination UDP port number
MUST be set to the IANA assigned value of 2142.
Calix recommends NOT using UDP-based PWs, where port-translating middle boxes are
present between PW endpoints.
When using the destination UDP port 2142, the source UDP port must be set to the
same value.
Configuration guidelines for operation with B6-440




E7 supports the ability to provision PWE3 to interoperate with the B6-440 line card and
T1 equipped ONTs by adding the ability to provision the RTP Payload Type – which
defaults to a value of 96 but the B6 requires a value of 86.
By default, the 766GX ONT requires header type 96. To operate with the B6-440, the
ONT needs to support RTP header type 86.
Set RTP to Enabled, and RTP Payload Type to 86 in the T1/E1 PWE3 profile.
Keep in mind the following B6’s functionality when configuring the PWE endpoints:

The B6 has a fixed Payload Size of 96 bytes.

Src UDP is fixed, Dst UDP is configurable.

It supports Adaptive and Loop timing modes but not Differential.

The Calix B6 only supports CESoPSN de-multiplexing mode, as detailed in RFC
5086.
Before starting
Before starting the services configuration process, check that the following conditions are
met:
1. The network uplinks for GPON services are configured.

E7 Ethernet ports (on page 67)

Ethernet port interfaces (on page 73)

Service VLANs (on page 86)
Within a Layer-2 network, T1/E1 services from an ONT are typically placed in a
single VLAN for transport between the remote pseudowire devices and the IP
gateway. Multiple remote locations may be split into separate VLANS for ease of
network planning and operation.

VLAN memberships (on page 107)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
339
2. The necessary E7 system profiles that support GPON applications are created.

ONT profile (on page 115)

Quality-of-Service (QoS) for GPON traffic management (on page 116)

Service match list (on page 127)
Accept the Default Match Criteria list: 1 - (all-untagged)

Service tag action (on page 131)
Transport of T1/E1 services over a packet network requires a CoS priority and
sufficient bandwidth allocation within the packet network to reduce latency and
packet loss. T1/E1 service VLANS should be given a high IEEE 802.1p priority “pbit” value (for example, 5).
You must create an "add tag" tag action in order to add a VLAN tag to all
pseudowire traffic. Each pseudowire must have its own VLAN ID within the
network. Both endpoints of the pseudowire will share the same VLAN ID. Create a
separate tag action for each pseudowire.
The service tag is associated with the PWE3 IP host – one IP host, one tag action.
If you want to use a different VLAN for each PWE3 service, set the tag action to be
“specified in service”. Then, when you provision the actual PWE3 service, enter the
VLAN ID for that PWE3 service in the service provisioning.

Profiles for T1/E1 services (on page 221)
All ports on an ONT must be either T1 or E1, which is indicated via the ONT PWE3
Profile (on page 223) when the ONT is created and cannot be changed on an existing
ONT.
Assign IP addresses for the CO endpoint ONT and the CPE endpoint by defining
the IP Host for PWE3 (on page 221) for each ONT at the PWE3 circuit endpoints.
Endpoint IP addresses must be located within the same subnet.
3. The PON is configured.

GPON port (on page 232)

ONT provisioning (on page 244)
Step 4. T1/E1 PWE3 services configuration process
Assuming that the conditions stated above are met, the T1/E1 PWE3 services configuration
process follows:
1. Provision T1 ports on the ONTs (on page 340)
2. Add pseudowire service to the T1 ports (on page 343)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
340
Information you need
You must have the following information on hand to configure ONT T1/E1 PWE3 service:




Tag Action name
T1/E1 PWE3 profile name
UDP port number
Destination IP
Configuring an ONT T1 Port
This topic describes how to configure pseudowire services on an ONT T1 port. See the Calix
T1 Pseudowire Applications for MDU ONTs document for details.
When using the in-band loopback feature on properly equipped ONTs, consider the
following:





ONTs must be connected to the E7 via a GPON-4 card.
In-band loopback detection can be enabled/disabled on a per port basis.
In-band loopbacks can be enabled or disabled via CLI, web interface, or CMS.
During loopback, the ONT transmits an Alarm Indication Signal (AIS) towards the CPE
or subscriber interface and provides a notification of the active loopback to the E7 (via
CLI, web interface, or CMS).
When the Inband Loop Back parameter is set to N (no), the only ways to invoke a
loopback are to loop up manually via provisioning or installing an external "smartjack" at
the ONT.
Parameters
You can provision the following parameters for PWE3 services on an ONT T1 port:
Parameter
Description
Valid Options
Admin State
Administrative state of the port.
Enabled
Enabled-no-alarms
Disabled ‡
Subscriber ID
Subscriber ID information, such as name, address, or account
number.
String up to 27 characters
(blank) ‡
Description
Optional description field for the port or service .
String up to 27 characters
(blank) ‡
Line Code
T1 line code
b8zso ‡
ami
Note: T1 port parameters must be verified to ensure compatibility
with PWE3 settings, including Line Coding.
Line Length
T1 line length in feet.
up to-110, 111-220‡,
221-330, 331-440, 441-550,
551-660
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
341
Parameter
Loop Back
Description
T1 loopback mode:

Facility loopback sends data received from the transport
network back to the same transport network.

Equipment loopback is looping the downstream signal
(toward the T1/E1 port) back upstream (away from the T1/E1
port).
Valid Options
none‡, facility, eqpt
GOS Profile
Index of previously created GOS profile to use.
Any available ONT T1 GOS
profile
Inband Loop
Back
Enables/disables DS1 in-band loopback code detection on this
port to verify the circuit is provisioned correctly by inserting a
specific repeating bit pattern (Facility Type 2 or FAC2) into the T1
bit stream and putting the port into loopback. In-band loopbacks
allow the service provider to test DS1 circuits independently of
the access network by isolating the transport side of the circuit.
Y (yes)
N (no) ‡
Impedance
Impedance value for T1/E1.
75-unbalanced
100 ‡
120-balanced
‡ Default
To configure an ONT T1 port for service
1. From the Navigation Tree, click ONTs.
2. From the Work Area menu, select Provisioned ONTs > Ports > Provisioning.
3. Select an ONT from the pull-down menu.
4. Scroll down to the ONT T1 port header for the CO endpoint ONT.
5. Double-click a T1 port and perform the following from the ONT T1 port screen:
a. Set the Admin Status to enabled.
Note: Selecting an Admin Status of "enabled - no alarms" temporarily suppresses alarms
during the provisioning process.
b. Enter a Subscriber ID and Description for the ONT port.
c. Verify the T1 port Framing parameter is set to Unframed.
d. Verify the T1 port Line Coding parameter is set to B8ZS.
e. For the remaining fields, accept the default values.
6. From the menu, click Apply.
7. Repeat steps 1 through 6 above for the CPE endpoint ONT.
8. You are now ready to add the pseudowire service to the ONT T1 ports.
For CLI:
set ont-port <port> [eth-svc|h248-gw-svc|pwe3-svc|sip-svc|tdm-gwsvc|subscriber-id|description|speed|duplex|eth-sec-profile|ont-eth-gos|ontt1-gos|line-code|line-length|line-length-metric|loopback-mode|in-bandloopback|impedance|disable-on-batt|signal-type|admin-state]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
342
Configuring Timing for GE Ports of a GPON Card
The BITS clock input is NOT required for most GPON applications, including most T1/E1
applications. A traceable network clock synchronization for E7 GPON is only required in
rare situations where differential clock recovery is being used for T1/E1 pseudowire
applications.
For TDM T1/E1 Pseudowire (PWE) services delivered across a packet network that require
a service clock recovery algorithm to recreate the original service clock at the far end pack-toTDM transition. Two mechanisms are available for T1/E1 clock recovery:


Adaptive Clock Recovery (ACR)
Differential Clock Recovery (DCR)
ACR is used in most networks and is sufficient to recover the T1/E1 service clock for most
applications. When a network is susceptible to high packet delay variation (PDV), and a
traceable clock is available at both PWE3 end point devices, the T1/E1 circuit can be
configured to use DCR and will be highly immune to network-induced PDV. Most T1/E1
deployments do not require DCR. A BITS Stratum 1 clock reference is required for T1
services if DCR is used.
Refer to the Calix T1 Pseudowire Applications Guide, for additional information on T1/E1
service delivery, clock recovery options, and network timing requirements.
The E7-2 and E7-20 platforms support E1 timing input to the BITS pins on the rear of each
shelf. The system can be configured for a accept T1 input (1.544 Mbps) or E1 input (2.048
Mbps). To facilitate conversion from a BNC connector commonly used for E1 services to a
4 wire interface used for T1 services, Calix offers an optional RJ-45 to BNC connector cable.
To configure timing for GE ports of a GPON card
1. On the Navigation Tree, click E7.

For E7-2 or modular chassis systems, click Shelf#.
2. In the Work Area, click Timing to open the System Timing parameter form view.
3. In the Admin State list, select whether to enable the system timing.
4. In the Source Type list, select the timing source attribute.
5. In the Bits Output Type list, select the type of BITS timing output.
6. In the Source Protection list, select the type of timing source protection.
7. In the Timing Source: BITS-A box, select whether to enable the BITS-A as a timing
source.
8. In the Timing Source: BITS-B box, select whether to enable the BITS-B as a timing
source.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
343
For CLI:
(For E7 Modular Chassis) set shelf <shelf-id> timing [source|src-type|bitsoutput-type|src-protection|admin-state]
(For E7-2 and E7-20) set timing [source|src-type|bits-output-type|srcprotection|admin-state]
Creating a T1/E1 Service on an ONT T1 Port
This topic describes how to configure pseudowire services on an ONT T1 port. See the Calix
T1 Pseudowire Applications Guide for details.
The E7 and Calix 760GX ONTs provide T1/E1 services over GPON and point-to-point
Ethernet networks using pseudowire emulation technology. T1/E1 PWE3 (Pseudo-wire)
service provisioning specifies the Transport Mode, determining how the local and remote
ends of the circuit are defined.

With UDP for the pseudowire multiplexing layer, the Calix 760GX ONT uses StructureAgnostic Time Division Multilexing (TDM) over Packet (SAToP), RFC 4553, for
encapsulation and transport of T1/E1 services over the IP/Ethernet packet switched
network. The Remote UDP port must be specified (avoiding 2142), yet the UDP port of
the local and remote PWE3 circuits can be set independently, in support for UDP demultiplexing, as defined in RFC 5086.
Note: Calix recommends using the RFC 5086 method for de-multiplexing. This method
requires that the remote (destination) UDP port always be specified, avoiding port 2142.
See Overview: Configuring GPON T1/E1 Services (on page 337) for more information demultiplexing PWE3 services.

With MEF (layer-2 transport) for Ethernet-only encapsulation, the T1/E1 circuit uses a
structure defined by the Metro Ethernet Forum (MEF). The local and remote ends of the
circuit are given ECID values. The remote end of the T1/E1 pseudowire can be
addressed using either a MAC address or an IP address. Calix recommends using an IP
address to allow the two end points to learn each other's MAC addresses dynamically
based on ARP exchanges. In this manner, a failed ONT can be replaced, given the same
IP address for the T1/E1 service, and the service will restore automatically.
Profiles referenced in service provisioning
When provisioning subscriber services on an ONT port, you set up information that is
common to multiple subscribers and maintained in profiles. Repeating the similar task of
subscriber service activation then consists of referencing the existing profiles and sometimes
providing subscriber-specific information to complement the profiles.
Note: When a profile is changed, all subscribers using that profile are affected. For example,
if the rate in a bandwidth profile is changed, all ONT Ethernet ports referencing the profile
are changed to the modified bandwidth rate. Profile objects may not be deleted while they are
being referenced.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
344
Information you need
You must have the following information on hand to configure a T1/E1 service:



T1/E1 PWE3 profile to use on the ONT T1 port.
UDP port Number to use for the T1/E1 PWE3 service.
Destination IP address to use for the remote end of the pseudowire.
Parameters
You can provision the following parameters for PWE3 services on an ONT T1 port:
Parameter
PWE3 Profile*
Transport Mode
Description
Valid Options
Name of PWE3 profile to use.
Any available PWE3 profile
Choose Layer-3 (IP) or Layer-2 (MEF) transport mode.
udp-ip
mef

UDP/IP is transported with Ethernet, UDP, and IP headers. MEF
is transported with Ethernet headers. The de-multiplexing
(transport) method must be consistent across all PWE3 services
provisioned on an ONT. Mixing de-multiplexing modes on the
same ONT is NOT supported.
Note: Calix recommends using the RFC 5086 (udp-ip) method for
de-multiplexing. This method requires that the remote (destination)
UDP port always be specified, avoiding port 2142.

MEF (layer-2 transport) is for Ethernet-only encapsulation of the
T1 circuit using a structure defined by the Metro Ethernet Forum
(MEF). The local and remote ends of the circuit are given ECID
values. The remote end of the T1 pseudowire can be addressed
using either a MAC address or an IP address. Calix
recommends using an IP address to allow the two end points to
learn each other's MAC addresses dynamically based on ARP
exchanges.
GOS
Grade of Service (GOS) profile number to use on this port.
Any available PWE3 GOS
profile
Admin State
Admin state of ONT service.
enabled
disabled
Remote IP*
The IP address of the remote end of the pseudowire to where the
ONT transmits PWE3 packets. The combination of the IP address
and UDP port number uniquely identifies the pseudowire, being
associated with the physical T1 port and directs the pseudowire
payload to the proper T1 (TDM) port. The E7 will ARP for the
remote end MAC.
"dotted quad" format
(ex: 192.168.1.100)
Alternately, "none" can be
used to reset the value to
"0.0.0.0."
Note: Either the remote MAC or the remote IP address is required
when in MEF transport mode.
For MEF Transport Mode
Local ECID
Emulated circuit ID (ECID) must unique for a given MAC address
(endpoint). This is a numeric value.
Unspecified
Enter value
1-1048575
Remote ECID
Remote emulated circuit ID. ECID may be different on each end of
the PWE3.
Unspecified
Enter value
1-1048575
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
345
Parameter
Remote MAC
Description
Valid Options
Available for MEF transport mode only: MAC address of the remote
end of the pseudowire. This is a MAC address.
six hexadecimal digits in the
range 0-FF, optionally
separated by colons.
Note: Either the remote MAC or the remote IP address is required
when in MEF transport mode.
For UDP-IP Transport Mode
Local UDP Port*
UDP port number to use for receiving PWE3 packets, which may be
the same on both ends of pseudowire. The combination of the IP
address and UDP port number uniquely identifies the pseudowire,
being associated with the physical T1 port and directs the
pseudowire payload to the proper T1 (TDM) port.
Unspecified
Enter value
1024-65535
Remote UDP Port
UDP port number where PWE3 packets are transmitted. This is a
TCP or UDP port number. For the recommended de-multiplexing
method of RFC 5086, the Remote UDP port must be specified
(avoiding the value 2142), yet the UDP port of the local and remote
PWE3 circuits can be set independently.
Unspecified
Enter value
1024-65535
*Required fields
To create a T1/E1 service on an ONT T1 port
1. On the Navigation Tree, click ONTS.
2. In the list of linked ONTs, double-click the ONT to configure the CO endpoint, and
then click the Ports tab to view its ports.
3. From the list of ONT ports, double-click the ONT T1 port on which to add service.
4. From the menu, click Create.
5. Reference the table above to configure the parameters.
6. Click Create.
7. Repeat steps 1 through 5 above for the CPE endpoint ONT, changing the PWE3 profile
to match the timing method, and the Destination IP Host address as appropriate.
For CLI:



add pwe3-svc to-ont-port <ONT T1 port > t1-pwe3-profile <profile name>
upd-port <UDP port> remote-ip <IP address> [gos-profile <index> adminstate <state>]
set ont-port <port> pwe3-svc [t1-pwe3-profile|udp-port|remote-ip|gosprofile|admin-state]
show ont-port [detail|fast-eth|gig-eth|hpna-eth|pots|t1|video-hotrf|video-rf|port]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
346
Configuring a PWE3 Service from the Service Tab
The Calix E7 supports a subscriber services activation page where you can provision any
possible service for any ONT configured in the E7 system.
This topic shows you how to provision a T1 PWE3 service for a GPON ONT. See the Calix
T1 Pseudowire Applications for details.
Optionally, you can configure a T1 PWE3 service from the Ports tab to access detailed
provisioning at a port level and its services.
The E7 and Calix 760GX ONTs provide T1/E1 services over GPON and point-to-point
Ethernet networks using pseudowire emulation technology. T1/E1 PWE3 (Pseudo-wire)
service provisioning specifies the Transport Mode, determining how the local and remote
ends of the circuit are defined.

With UDP for the pseudowire multiplexing layer, the Calix 760GX ONT uses StructureAgnostic Time Division Multilexing (TDM) over Packet (SAToP), RFC 4553, for
encapsulation and transport of T1/E1 services over the IP/Ethernet packet switched
network. The Remote UDP port must be specified (avoiding 2142), yet the UDP port of
the local and remote PWE3 circuits can be set independently, in support for UDP demultiplexing, as defined in RFC 5086.
Note: Calix recommends using the RFC 5086 method for de-multiplexing. This method
requires that the remote (destination) UDP port always be specified, avoiding port 2142.
See Overview: Configuring GPON T1/E1 Services (on page 337) for more information demultiplexing PWE3 services.

With MEF (layer-2 transport) for Ethernet-only encapsulation, the T1/E1 circuit uses a
structure defined by the Metro Ethernet Forum (MEF). The local and remote ends of the
circuit are given ECID values. The remote end of the T1/E1 pseudowire can be
addressed using either a MAC address or an IP address. Calix recommends using an IP
address to allow the two end points to learn each other's MAC addresses dynamically
based on ARP exchanges. In this manner, a failed ONT can be replaced, given the same
IP address for the T1/E1 service, and the service will restore automatically.
Information you need
You must have the following information on hand to configure ONT TDM Gateway voice
service:



T1/E1 PWE3 profile to use on the ONT T1 port.
UDP port Number to use for the T1/E1 PWE3 service.
Destination IP address to use for the remote end of the pseudowire.
Parameters
You can provision the following parameters for T1/E1 PWE3 services accessed from the
Services page:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
347
Parameter
Description
Valid Options
Subscriber Port
Subscriber Port*
System address of the ONT port where the subscriber services will be
provisioned.
Any ONT POTS port
Subscriber ID
Subscriber ID information, such as phone number, or account number.
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Subscriber ID entry from
the ONT provisioning record to this field.
Description
Optional description field for the port, subscriber address, name, or
service.
String up to 27 characters
(blank) ‡
If you leave this box empty, the E7 copies the Description entry from
the ONT provisioning record to this field.
Create PWE3 Service
PWE3 Profile*
Name of the T1/E1 PWE3 profile to use for the service.
Any established PWE3
profile
Transport Mode
Choose Layer-3 (IP) or Layer-2 (MEF) transport mode.
udp-ip
mef

UDP/IP is transported with Ethernet, UDP, and IP headers. MEF is
transported with Ethernet headers. The de-multiplexing (transport)
method must be consistent across all PWE3 services provisioned
on an ONT. Mixing de-multiplexing modes on the same ONT is
NOT supported.
Note: Calix recommends using the RFC 5086 (udp-ip) method for demultiplexing. This method requires that the remote (destination) UDP
port always be specified, avoiding port 2142.

MEF (layer-2 transport) is for Ethernet-only encapsulation of the T1
circuit using a structure defined by the Metro Ethernet Forum
(MEF). The local and remote ends of the circuit are given ECID
values. The remote end of the T1 pseudowire can be addressed
using either a MAC address or an IP address. Calix recommends
using an IP address to allow the two end points to learn each
other's MAC addresses dynamically based on ARP exchanges.
Local UDP Port*
(UDP-IP mode only)
Local UDP port number to use, which must be the same on both ends of
pseudowire. The combination of the IP address and UDP port number
uniquely identifies the pseudowire, being associated with the physical
T1 port and directs the pseudowire payload to the proper T1 (TDM) port.
1024-65534
Remote UDP Port
(UDP-IP mode only)
UDP port at the remote end of the pseudo-wire. This is a TCP or UDP
port number.
Unspecified
Enter value
1024-65534
Local ECID
(MEF mode only)
Emulated circuit ID.
1-1048575
Remote ECID
(MEF mode only)
Remote emulated circuit ID.
1-1048575
Remote MAC
(MEF mode only)
Available for MEF transport mode only: MAC address of the remote end
of the pseudowire. This is a MAC address.
six hexadecimal digits in
the range 0-FF, optionally
separated by colons.
Note: Either the remote MAC or the remote IP address is required when
in MEF transport mode.
Remote IP*
The IP address of the remote end of the pseudowire. The combination
of the IP address and UDP port number uniquely identifies the
pseudowire, being associated with the physical T1 port and directs the
pseudowire payload to the proper T1 (TDM) port.
"dotted quad" format
(ex: 192.168.1.100)
Alternately, "none" can be
used to reset the value to
"0.0.0.0."
Host Protocol
Host protocol for the SIP client. "Static" is the only supported host
protocol for PWE3 IP Hosts, therefore, you must also enter a static IP
address, mask, and gateway addresses.
static
dhcp
Static IP
(static protocol only)
IP address statically assigned to the ONT if the host protocol is static.
This attribute is ignored, yet preserved, if the host protocol is DHCP.
4-byte IP address
Update IP Host
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
348
Parameter
Description
Valid Options
Static IP Mask
(static protocol only)
IP network mask assigned to the ONT if the host protocol is static. This
attribute is ignored, yet preserved, if the host protocol is DHCP.
4-byte IP address
Static IP Gateway
(static protocol only)
Static IP gateway 4-byte address for the ONT to use in routing its traffic
to the SIP server, if the host protocol is static. This attribute is ignored,
yet preserved, if the host protocol is DHCP.
4-byte IP address
Svc Tag Action
Name of the previously created "add tag" tag action in order to add a
VLAN tag to all pseudowire traffic. Each pseudowire must have its own
VLAN ID within the network. Both endpoints of the pseudowire will
share the same VLAN ID. Use a separate tag action for each
pseudowire circuit.
index-name of tag action
S-VLAN (Outer Tag)
Indicates the customer-specific tag when the Output Outer Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
C-VLAN (Inner Tag)
Indicates the customer-specific tag when the Output Inner Tag attribute
of the referenced tag action states "Specified in Service."
2-4093
(Except for 1002-1005
which are reserved for E7
operation.)
*Required fields
‡ Default
To create a T1/E1 service on an ONT T1 port
1. On the Navigation Tree, click ONTS.
2. In the work area, click Provisioned ONTS > Services.
3. From the menu ONT drop-down list, select the ONT for the CO endpoint that you wish
to provision.
4. From the menu, click Create > PWE3 Service to open the Create dialog box.
5. Reference the table above to configure the parameters.
6. Click Create to activate a T1 PWE3 service on the subscriber port.
7. Repeat steps 3 through 6 above for the CPE endpoint ONT, changing the PWE3 profile
to match the timing method, and the Destination IP Host address as appropriate.
For CLI:





add pwe3-svc to-ont-port <ONT T1 port> t1-pwe3-profile <profile name>
transport-type upd local-port <l-port> remote-ip <address> [remoteport|ont-pwe3-svc-gos|outer-vlan|inner-vlan|admin-state]
add pwe3-svc to-ont-port <ONT T1 port> t1-pwe3-profile <profile name>
transport-type mef ecid <circuit-id> remote-ecid <r-circuit-id>
remote-ip <address> [ont-pwe3-svc-gos|admin-state]
add pwe3-svc to-ont-port <ONT T1 port> t1-pwe3-profile <profile name>
transport-type mef ecid <circuit-id> remote-ecid <r-circuit-id>
remote-mac <mac> [ont-pwe3-svc-gos|admin-state]
set ont-port <port> pwe3-svc [t1-pwe3-profile|udp-port|remote-ip|gosprofile|admin-state]
show ont-port [detail|fast-eth|gig-eth|hpna-eth|pots|t1|video-hotrf|video-rf|port]
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Chapter 5
Service Provisioning Examples
This chapter describes various provisioning examples for the Calix E7 GPON solution.
Topics Covered
This chapter covers the following topics:










Data services overall process
Video services overall process
MVR video services overall process
Voice services overall process
Home Gateway service external mode
Home Gateway IPTV service over L2 bridge Wi-Fi
Home Gateway IPTV service over RG Wi-Fi
Home Gateway service native mode
Home Gateway TR-069
QoS service models
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
350
Example: Data Services
This topic shows an example process for provisioning data services on the GPON ONT
Ethernet port.
See Overview: GPON L2 Data Services (on page 42) for the sequence of linked procedures for
configuring the E7 and GPON ONTs data services.
Step 1: Configure network uplinks




Configure Ethernet Interfaces
Configure Ethernet Ports
Create Service VLANs
Make Interfaces VLAN Members
See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
See "Configuring Transport and Aggregation Support" in the Calix E7
User Guide for instructions on configuring transport rings and
aggregation links.
Step 2: Create system profiles
Create Rules to Classify Traffic:
a) Create a Match List
Typically only untagged traffic is present on the ONT Ethernet
port, so you can use the system default match list "alluntagged," defined as shown, to match all untagged traffic.
If a residential gateway (RG) is installed in a subscribers
premises, the RG classifies traffic into VLANs. Then for each
service type, create a match list that contains a tagged rule,
matching the service VLAN.

E7 > Profiles > Service > Tagging > Match Lists >
Profiles > Create
See Creating a Service Match List and Rules (on page 127).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
351
b) Create a Service Tag Action
Applies the specified service-tag action to the matched traffic.
VLAN-per-service:

Single tags all untagged traffic on the ONT Ethernet port.

or

Adds a tag to all traffic arriving on the ONT port with a tag
value of 12.
Specify the added VLAN tag in the Service Tag Action (Outer
Tag = 300) so you can apply the same VLAN tagging for all
data service provisioning that uses the tag action object.
When you indicate Specify P-Bit for the Outer P-Bit Source,
enter the P-bit value that marks the traffic for the best effort
forwarding class.
Note: Upstream GPON traffic on a service VLAN must have
the same P-bit value as is set for downstream.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
352
VLAN-per-subscriber:

Double tags all untagged traffic arriving on the ONT port.

or

Double tags all traffic arriving on the ONT port with a tag
value of 12.
Specify the added VLAN outer tag in the Service Tag Action
(Outer Tag= 300) and indicate the VLAN inner tag is specified
when adding the service to a port (Inner Tag = Specified in
Service). This allows you to apply the same outer tag for the
type of traffic and also apply a unique inner tag for each
subscriber.
When you indicate Specify P-Bit for the Outer P-Bit Source,
enter the P-bit value that marks the traffic for the best effort
forwarding class.
Note: Upstream GPON traffic on a service VLAN must have
the same P-bit value as is set for downstream traffic.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
See Creating Service-Tag Actions (on page 131).
Creating a PON Upstream Class of
Service Profile.
PON upstream Class of Service (CoS) profiles allow you to
expand on the 4 system-default instances of CoS to 8
priorities of scheduled service per ONT.

1.) Create a PON US CoS profile.

2.)Map the PON US CoS profile to an instance (user1-4)
at the ONT.

3.) Select the PON CoS instance when adding a service
to an ONT port.

E7 > Profiles > CoS > PON Upstream > Create
See Creating a PON Upstream Class of Service Profile (on
page 124).
(not supported for the P-series GX ONTs)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
353
Configure the Ethernet Bandwidth
Profile.
An Ethernet bandwidth profile specifies the upstream and
downstream bandwidth rates to apply to individual Ethernet
services on ONT Ethernet ports. Typically, a single bandwidth
profile is applied to many subscriber ports.

Committed Rate for Upstream: 0k

Peak Rate for Upstream: 50M

Peak Rate for Downstream: 100M

E7 > Profiles > Service > Ethernet Bandwidth > Create
See Creating an Ethernet Bandwidth Profile (on page 167).
Create an Ethernet Security Profile.
An Ethernet security profile is applied to ONT Ethernet ports
to enable and/or specify security attributes of the ONT
Ethernet port, including Layer 2 Control Protocol (L2CP)
handling on GPON ONT Ethernet interfaces and VLANs on
the interface.
The E7 has a default Ethernet Security profile that you can
apply to ONT Ethernet ports or you can create a new profile
with modified attributes.

DHCP Lease Limit: 10

Upstream Broadcast/Multicast Limit: 24

L2CP Filter: user-defined

Flood Destination Lookup Fail: selected

DOC Attack Detection: selected

E7 > Profiles > Security > Ethernet > Profiles > Create
The E7 has two system default L2CP filters that either discard
(all-discard) or pass (all-tunnel) all L2CP protocol frames for
all ranges. You can also create filters that specify which L2CP
ranges to discard or tunnel L2CP protocol frames.
The E7 implementation of security profiles applies to nonTLAN services only.

E7 > Profiles > Security > L2CP > Filters > Create
See Creating an Ethernet Security Profile (on page 188).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
354
Step 3: Configure a PON
Enable the GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.

Admin State: enabled

Split Horizon: selected

Dynamic Bandwidth Allocation (DBA): selected

Shelf# > Card# (GPON) > GPON #

Click Apply from the menu.
See Configuring an E7 GPON Port (on page 232).
Create an ONT.
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT. ONTs are
created as follows:
Manually where the ONT is pre-provisioned by entering the
ONT serial number into the Create ONT dialogue box.
Automatically where the ONT is discovered on the network
after successfully completing the Remote ONT Activation
Process.
Selecting System Assigned ID allows the automatic
assignment for the ONT ID.

Provisioned ONTs > Provisioning > Create
See Creating GPON ONTs (on page 244).
Add PON US CoS Profile to ONT.
Select a previously-created PON Upstream CoS profile and
map it to a either a Calix GE or T-series ONT.

ID: 1 (user-1)

Profile: BE (previously created)

ONTs > Provisioned ONTs > ONT ID# > PON Upstream
CoS > Create
See Adding PON Upstream CoS Profiles to an ONT (on page
256).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
355
Configure an ONT Ethernet Port.
Configure an ONT Ethernet port for service.

Enable the port and enter subscriber information.

Assign port to L2 interface (none), if necessary for HGW
ONT.

Specify the security profile.

To run OAM tests, the Link OAM Events and Accept Link
OAM Loopback must be set to Y (Yes).

Click Apply on the menu.

ONTs > Provisioned ONTs > Ports > GE
See Configuring an ONT Ethernet Port (on page 257).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
356
Step 4: Configure subscriber services
Add the Data Service to an Ethernet Port.
VLAN-per-service:
References a Service Tag Action that added a single tag and specified the Outer Tag. This allows you to apply the same VLAN tag for
all subscribers of data service (N:1).

ONTs > Provisioned ONTS > Services > Table.

From the top of the Work Area, use the ONT drop-down list
service.

Create > Data Service.
to select the ONT on which to add the
See Creating an L2 Data Service (on page 271).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
357
VLAN-per-subscriber:
References a Service Tag Action that added two tags, specified the Outer Tag, and indicated the VLAN inner tag is specified when the
service is added to a port.
Specify a unique VLAN inner tag to apply a different VLAN tag for each subscriber (1:1).

ONTs > Provisioned ONTS > Services > Table.

From the top of the Work Area, use the ONT drop-down list
service.

Create > Data Service.
to select the ONT on which to add the
See Creating an L2 Data Service (on page 271).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
358
Example: Video Services
This topic shows an example process for provisioning video services on the E7 GPON and
ONT Ethernet port.
See Overview: GPON L2 IP video Services (on page 44) for the sequence of linked procedures
for configuring the E7 and GPON ONTs video services.
Step 1: Configure network uplinks



Configure Ethernet Interfaces
Configure Ethernet Ports
Create Service VLANs

If the VLAN IGMP Mode is set to proxy, an IGMP profile
must be referenced from the VLAN. Use the system-default
IGMP profile, or create a new IGMP profile for the VLAN to
reference that sets configuration attributes of the IGMP
snoop used to establish membership in a multicast video
services group.

Note: All nodes in an ERPS ring must have the same IGMP
Snooping provisioning on the video VLAN for traffic to flow-either all with snooping (snoop-suppress, proxy) or all
without snooping (flood).

See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
See "Configuring Transport and Aggregation Support" in the Calix
E7 User Guide for instructions on configuring transport rings and
aggregation links.
Make Interfaces VLAN Members
Step 2: Create system profiles
Create Rules to Classify Traffic:
a) Create a Match List
Create a list with rules that match the traffic from set-top boxes
(STB). This allows both video and internet services on the same
port. To match the traffic from all STBs of a particular
manufacturer, indicate the STB OUI in the first half of the Source
MAC and enter zeros for the last half of the source MAC.
Example entries that match all STB source MAC addresses of a
particular manufacturer:
ADB set-top boxes: 00:03:91:00:00:00
Amino set-top boxes: 00:02:02:00:00:00
Alternatively, the ONTs support matching the traffic from a
specific host by indicating the MAC address in the Source MAC
attribute, and then providing a mask for the address by
indicating ff:ff:ff:ff:ff:ff in the Source Mac Mask attribute.
Source MAC mask (untagged match rules only).

source MAC mask (x:x:x:x:x:x)

none (no MAC mask)

oui (mask OUI fields (FF:FF:FF:FF:FF:FF)
Ethernet type to match (untagged match rules only).

any = default

pppoe = 0x8863 or 0x8864 (for HSI)

arp = 0x0806 (for video)

ipv4 = 0x0800 (for video)

ipv6 = 0x86DD (for video)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
359
If a residential gateway (RG) is installed in the subscriber's
premises, the RG classifies traffic into VLANs. Then for each
service type, create a match list that contains a tagged rule,
matching the service VLAN.

E7 > Profiles > Service > Tagging > Match Lists >
Profiles > Create
See Creating a Service Match List and Rules (on page 127).
b) Create a Service Tag Action
Applies the specified service-tag action to the matched traffic.
VLAN-per-service:

Single tags all untagged traffic on the ONT Ethernet port that
matches all STB OUIs of a particular manufacturer.

or

Adds a tag to all traffic arriving on the ONT port with a tag
value of 24.
Specify the added VLAN tag in the Service Tag Action (Outer
Tag = 250) so you can apply the same VLAN tagging for all data
service provisioning that uses the tag action object.
When you indicate Specify P-Bit for the P-Bit Source, enter the
P-bit value that marks the traffic for the assured forwarding
class. See the PON CoS step above.
Note: Upstream GPON traffic on a service VLAN must have the
same P-bit value as is set for downstream traffic.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
360
VLAN-per-subscriber:

Double tags all untagged traffic arriving on the ONT port that
matches all STB OUIs of a particular manufacturer.

or

Double tags all traffic arriving on the ONT port with a tag
value of 24.
Specify the added VLAN outer tag in the Service Tag Action
(Outer Tag= 250) and indicate the VLAN inner tag is specified
when adding the service to a port (Inner Tag = Specified in
Service). This allows you to apply the same outer tag for the
type of traffic and also apply a unique inner tag for each
subscriber.
When you indicate Specify P-Bit for the P-Bit Source, enter the
P-bit value that marks the traffic for the assured forwarding
class. See the PON CoS step above.
Note: Upstream GPON traffic on a service VLAN must have the
same P-bit value as is set for downstream traffic.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
See Creating Service-Tag Actions (on page 131).
Configure the Ethernet Bandwidth Profile.
An Ethernet bandwidth profile specifies the upstream and
downstream bandwidth rates to apply to individual Ethernet
services on ONT Ethernet ports. Typically, a single bandwidth
profile is applied to many subscriber ports.

Committed Rate for Upstream: 25M

Peak Rate for Upstream: 100M

Peak Rate for Downstream: 100M

E7 > Profiles > Service > Ethernet Bandwidth > Create
See Creating an Ethernet Bandwidth Profile (on page 167).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
361
Creating Multicast Ranges.
A multicast map can optionally reference a multicast range that
defines a single range of multicast addresses that provides a
filter against unwanted IGMP traffic. The IGMP traffic that falls
outside of the multicast ranges is discarded at the ONT. You can
define a maximum of eight multicast ranges to create a set of
incontiguous address ranges.
The multicast ranges apply to the E7 system globally and are
automatically assigned to any ONT that has a video service
provisioned.

E7 > Profiles > Service > Multicast Maps > Create
See Creating Multicast Ranges (on page 181).
Configure the Ethernet Multicast Profile.
An Ethernet multicast profile enables provisioning of the IPTV
service limits that can be applied to subscriber services.
Enter a Query Interval value that matches the query interval of
the upstream router that is acting as the IGMP querier.
The Convert to Unicast parameter should ONLY be enabled if
switches are deployed on the subscriber side that cannot
manage heavy multicast traffic. (Only Calix GX ONTs support
this feature.)

E7 > Profiles > Service > Multicast > Multicast > Profiles
> Create
See Creating an Ethernet Multicast Profile (on page 177).
Create an Ethernet Security Profile.
An Ethernet security profile is applied to ONT Ethernet ports to
enable and/or specify security attributes of the ONT Ethernet
port, including Layer 2 Control Protocol (L2CP) handling on
GPON ONT Ethernet interfaces and VLANs on the interface.
The E7 has a default Ethernet Security profile that you can apply
to ONT Ethernet ports or you can create a new profile with
modified attributes.

DHCP Lease Limit: 10

Upstream Broadcast/Multicast Limit: 24

L2CP Filter: user-defined

Flood Destination Lookup Fail: selected

DOC Attack Detection: selected

E7 > Profiles > Security > Ethernet > Profiles > Create
The E7 has two system default L2CP filters that either discard
(all-discard) or pass (all-tunnel) all L2CP protocol frames for all
ranges. You can also create filters that specify which L2CP
ranges to discard or tunnel L2CP protocol frames.
The E7 implementation of security profiles applies to non-TLAN
services only.

E7 > Profiles > Security > L2CP > Filters > Create
See Creating an Ethernet Security Profile (on page 188).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
362
Step 3: Configure a PON
Enable the GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.

Admin State: enabled

Split Horizon: selected

Dynamic Bandwidth Allocation (DBA): selected

Shelf# > Card# (GPON) > GPON #

Click Apply from the menu.
See Configuring an E7 GPON Port (on page 232).
Create an ONT.
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT. ONTs are
created as follows:
Manually where the ONT is pre-provisioned by entering the ONT
serial number into the Create ONT dialogue box.
Automatically where the ONT is discovered on the network after
successfully completing the Remote ONT Activation Process.
Selecting System Assigned ID allows the automatic
assignment for the ONT ID.

Provisioned ONTs > Provisioning > Create
See Creating GPON ONTs (on page 244).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
363
Configure an ONT Ethernet Port.
Configure an ONT Ethernet port for service.

Enable the port and enter subscriber information.

Assign port to L2 interface (none), if necessary for HGW
ONT.

Specify the security profile.

To run OAM tests, the Link OAM Events and Accept Link
OAM Loopback must be set to Y (Yes).

Click Apply on the menu.

ONTs > Provisioned ONTs > Ports > GE
See Configuring an ONT Ethernet Port (on page 257).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
364
Step 4: Configure subscriber services
Add the Video Service to an Ethernet Port.
VLAN-per-service:
References a Service Tag Action that added a single tag and specified the Outer Tag. This allows you to apply the same VLAN tag for
all subscribers of data service. See Creating Video Service on an ONT Ethernet Port.

ONTs > Provisioned ONTS > Services > Table.

From the top of the Work Area, use the ONT drop-down list
service.

Create > Video Service.
to select the ONT on which to add the
See Creating an L2 Video Service (on page 292).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
365
VLAN-per-subscriber:
References a Service Tag Action that added two tags, specified the Outer Tag, and indicated the VLAN inner tag is specified when the
service is added to a port.
Specify a unique VLAN inner tag to apply a different VLAN tag for each subscriber (1:1).

ONTs > Provisioned ONTS > Services > Table.

From the top of the Work Area, use the ONT drop-down list
service.

Create > Video Service.
to select the ONT on which to add the
See Creating an L2 Video Service (on page 292).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
366
Example: MVR Video Services
This topic shows an example process for provisioning video services on the E7 GPON
ONT Ethernet port using the Multicast VLAN Registration (MVR) feature to isolate
subscriber video traffic from the network multicast VLAN. This is accomplished by using an
MVR profile that enables the distribution of multicast traffic on a dedicated multicast VLAN
across disparate access networks, while allowing subscribers who are on different VLANs to
join and leave the multicast groups carried in the Multicast VLAN.
MVR works in conjunction with IGMP where subscribers join and leave multicast groups via
IGMP. However, both the IGMP messages and multicast content are mapped from the
subscriber’s service into the isolated network side multicast VLAN. The E7 GPON ONT
supports the ability to map the subscriber’s IGMP and multicast traffic into multiple network
multicast VLANs.
Note: Calix recommends that an MVR profile be used for all multicast IPTV applications to
move the multicast traffic out of the "video" VLAN, where the video VLAN is assumed to
have all of the middleware traffic, STB DHCP traffic, VOD, and so on. Typically, the video
VLAN will be more susceptible to accidental or malicious traffic, whereas, MVR pulls the
multicast traffic out, keeping the VLAN exclusively for IGMP signaling and multicast
streams.
See Overview: GPON L2 MVR Video Services (on page 46) for the sequence of linked
procedures for configuring the E7 and GPON ONTs MVR video services.
Example configuration:
Unicast VLAN:




Middleware traffic, STB DHCP traffic, high-speed internet
VLAN ID IGMP Snooping - flood (no snooping)
Service-Tag Action - matches untagged traffic in Unicast VLAN, action is add-2-tags
(2001 for inner tag, 200 for outer tag)
Multicast VLAN:




IGMP signaling and multicast streams
VLAN ID - 100 single tag
IGMP Snooping - snoop-suppress or proxy (enable snooping)
MVR Profile VLAN ID = Multicast VLAN ID
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
367
Step 1: Configure network uplinks



Configure Ethernet Interfaces
Configure Ethernet Ports
Create Service VLANs

If the VLAN IGMP Mode is set to proxy, an IGMP profile
must be referenced from the VLAN. Use the system-default
IGMP profile, or create a new IGMP profile for the VLAN to
reference that sets configuration attributes of the IGMP
snoop used to establish membership in a multicast video
services group.

For an MVR configuration, create a minimum of two VLANS:
---One VLAN for Unicast
---One VLAN for Multicast
See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
See "Configuring Transport and Aggregation Support" in the Calix
E7 User Guide for instructions on configuring transport rings and
aggregation links.
For example:
Video (Unicast) VLAN:

Middleware traffic, STB DHCP traffic, high-speed internet

VLAN ID - 2001 for inner tag, 200 for outer tag

IGMP Snooping - flood (no snooping)
MVR (Multicast) VLAN:

IGMP signaling and multicast streams

VLAN ID - 101 single tag

IGMP Snooping - snoop-supress or proxy (E7-20 only
supports proxy, which requires a Proxy IP Address indicated
in the referenced IGMP Profile)

VLANs > Create
See Create the Service VLANs (on page 86).

Make Interfaces VLAN Members
Add uplink interface (LAG) to the service VLANs.

VLANs > Click Interface# > Action > Add/Remove VLAN
Members.

See Adding the Uplink Interface(s) to VLAN Memberships
(on page 107).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
368
Step 2: Create system profiles
Create Rules to Classify Traffic:
a) Create a Match List
The match rule only applies to the Unicast traffic, NOT the
Multicast VLAN. The Multicast VLAN will follow the same match
rule as setup for the Unicast stream when it is applied to the the
ONT Ethernet port.
Options:

To match all untagged traffic, use the system default match
list provided in the E7, as will be used in this example.

If a residential gateway (RG) is installed in the subscriber's
premesis, the RG classifies traffic into VLANs. Then for
each service type, create a match list that contains a tagged
rule. For MVR video, match the video Unicast VLAN.

To allow both video and internet services on the same port,
create a list with rules that match the traffic from set-top
boxes (STB). To match the traffic from all STBs of a
particular manufacturer, indicate the STB OUI in the first half
of the Source MAC and enter zeros for the last half of the
source MAC. See Creating a Service Match List and Rules
(on page 127).

E7 > Profiles > Service > Tagging > Match Lists >
Profiles > Create
See Creating a Service Match List and Rules (on page 127).
Example entries that match all STB source MAC addresses of a
particular manufacturer:
ADB set-top boxes: 00:03:91:00:00:00
Amino set-top boxes: 00:02:02:00:00:00
b) Create a Service Tag Action
Apply a specified service-tag action to the matched traffic. See
Creating Service-Tag Actions (on page 131).
For this example:

The system-default match list that matches all untagged
traffic is used.

Two tags are added to the Unicast stream where the outer
tag is assigned 200 and the inner tag will be specified when
the service is provisioned on the ONT Ethernet port.

The indication of Specify P-Bit is used for the P-Bit Source,
and the P-bit value of 4 marks the traffic for the assured
forwarding class.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
369
Configure the Ethernet Bandwidth Profile.
An Ethernet bandwidth profile specifies the upstream and
downstream bandwidth rates to apply to individual Ethernet
services on ONT Ethernet ports. Typically, a single bandwidth
profile is applied to many subscriber ports.
The bandwidth limits for all ONT services (in the same class) of
a single ONT Ethernet port are aggregated into a single CoS
metered rate. See Creating an Ethernet Bandwidth Profile (on
page 167).
Create an MVR Profile and MVR VLAN
Addresses.
For this example, the created MVR profile designates the
Multicast VLAN (101) as an MVR VLAN and no IP range is
specified, allowing all IGMP and Multicast traffic.

E7 > Profiles > Service > Multicast > MVR > Profiles >
Create

Double click the MVR profile > Create
See Creating an MVR Profile and MVR VLAN Addresses (on
page 178).
Configure the Ethernet Multicast Profile.
An Ethernet multicast profile enables provisioning of the IPTV
service limits that can be applied to subscriber services.

Select the MVR profile where the MVR VLAN ID is that of
the multicast VLAN.

Enter a Query Interval value that matches the query interval
of the upstream router that is acting as the IGMP querier.

The Convert to Unicast parameter should ONLY be enabled
if switches are deployed on the subscriber side that cannot
manage heavy multicast traffic. (Only Calix GX ONTs
support this feature.)

E7 > Profiles > Service > Multicast > Multicast > Profiles
> Create
See Creating an Ethernet Multicast Profile (on page 177).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
370
Create an Ethernet Security Profile.
An Ethernet security profile is applied to ONT Ethernet ports to
enable and/or specify security attributes of the ONT Ethernet
port, including Layer 2 Control Protocol (L2CP) handling on
GPON ONT Ethernet interfaces and VLANs on the interface.
The E7 has a default Ethernet Security profile that you can apply
to ONT Ethernet ports or you can create a new profile with
modified attributes.

DHCP Lease Limit: 10

Upstream Broadcast/Multicast Limit: 24

L2CP Filter: user-defined

Flood Destination Lookup Fail: selected

DOC Attack Detection: selected

E7 > Profiles > Security > Ethernet > Profiles > Create
The E7 has two system default L2CP filters that either discard
(all-discard) or pass (all-tunnel) all L2CP protocol frames for all
ranges. You can also create filters that specify which L2CP
ranges to discard or tunnel L2CP protocol frames.
The E7 implementation of security profiles applies to non-TLAN
services only.

E7 > Profiles > Security > L2CP > Filters > Create
See Creating an Ethernet Security Profile (on page 188).
Step 3: Configure a PON
Enable the GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.

Admin State: enabled

Split Horizon: selected

Dynamic Bandwidth Allocation (DBA): selected

Shelf# > Card# (GPON) > GPON #

Click Apply from the menu.
See Configuring an E7 GPON Port (on page 232).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
371
Create an ONT.
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT. ONTs are
created as follows:
Manually where the ONT is pre-provisioned by entering the ONT
serial number into the Create ONT dialogue box.
Automatically where the ONT is discovered on the network after
successfully completing the Remote ONT Activation Process.
Selecting System Assigned ID allows the automatic
assignment for the ONT ID.

Provisioned ONTs > Provisioning > Create
See Creating GPON ONTs (on page 244).
Configure an ONT Ethernet Port.
Configure an ONT Ethernet port for service.

Enable the port and enter subscriber information.

Assign port to L2 interface (none), if necessary for HGW
ONT.

Specify the security profile.

To run OAM tests, the Link OAM Events and Accept Link
OAM Loopback must be set to Y (Yes).

Click Apply on the menu.

ONTs > Provisioned ONTs > Ports > GE
See Configuring an ONT Ethernet Port (on page 257).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
372
Step 4: Configure subscriber services
Add the Video Service to an ONT Ethernet Port.
This example video service assigns a multicast profile that references an MVR profile for the Multicast VLAN.
This service also references a Service Tag Action that added two tags, specifying the Outer Tag, and indicating the VLAN inner tag is
specified when the service is added to a port. You can specify a unique VLAN inner tag to apply a different VLAN tag for each
subscriber.

ONTs > Provisioned ONTS > Services > Table.

From the top of the Work Area, use the ONT drop-down list
service.

Create > Video Service.
to select the ONT on which to add the
See Overview: GPON L2 MVR Video Service (on page 46).
Verify Service Functionality

Click the E7 node in the navigation tree. In the work area click DHCP > Leases. Check whether any subscriber devices have
acquired an IP address in the service VLAN.

Click the E7 node in the navigation tree. In the work area click Multicast > Groups.

In the list of all video streams currently being monitored on the entire E7, check whether any subscriber devices have acquired an
IP address in the service VLAN.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
373
Example: SIP GW Voice Services
This topic shows an example process for provisioning SIP Gateway voice services on the E7
GPON system that is based on using the OMCI download of a SIP configuration file.

T-series ONTs use a SIP configuration file that is obtained by submitting an intake form
to Calix with the defined configuration parameters. This results in the creation of an
approved SIP configuration file from Calix that you then transfer to a server local to the
E7.
The T-series HGU ONTs always require a SIP configuration file to add a voice service,
and the SIP Gateway is the only voice service supported on the T-series GPON ONTs.

P-series ONTs can use a SIP configuration file that you create, based on the Calix VoIP
template and sample file available with Calix Application Note: Using the 700 ONT VoIP
Configuration File, and then you transfer the file to a server local to the E7.
The P-series can also omit the SIP configuration file and base the service provisioning
exclusively on the SIP Gateway Profile.
See Overview: SIP Gateway Service with Configuration File (on page 61) for the sequence of linked
procedures for configuring the E7 GPON ONT SIP gateway voice services.
Procedure Assumptions
The following procedure assumes the following conditions:

The E7 unit and ONT have been upgraded to the latest software version. If necessary,
see:


Calix E7 Software Upgrade Guide
The SIP configuration file is created and transferred to a server local to the E7. If
necessary, see:

Submitting a T-Series Configuration Parameter Definition Form

Calix Application Note: Using the 700 ONT VoIP Configuration File
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
374
Step 1: Configure network uplinks



Configure Ethernet Interfaces
Configure Ethernet Ports
Create Service VLANs
See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
Create VLAN 3, DHCP Snoop = enabled
The VLAN assignment must be different between the VoIP IP
host and the subscriber port. Sharing VLANs between a
subscriber port and a VoIP IP host is not supported. For T-series
ONT peer-to-peer voice service, PON Hairpin or MAC-FF must
be enabled.

VLANs > Create

See Create the Service VLANs (on page 86).

Make Interfaces VLAN Members
Add uplink interface (LAG) to the SIP VLAN.

VLANs > Click Interface# > Action > Add/Remove VLAN
Members.

See Adding the Uplink Interface(s) to VLAN Memberships
(on page 107).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
375
Step 2: Create system profiles
Create Rules to Classify Traffic:
a) Create a Match List
Create a match list with an untagged rule that matches any of
the possible criteria.
Note: HGW ONTs use tagged match lists with a change-tag
service tag action.

E7 > Profiles > Service > Tagging > Match Lists >
Profiles > Create
See Creating a Service Match List and Rules (on page 127).
b) Create a Service Tag Action
Applies the specified service-tag action to the matched traffic.
VLAN tag is specified in the Service Tag Action (for this
example, Outer Tag = 3) so you can apply the same VLAN
tagging for all ONTs that use the tag action object.
Use the system default match list "MatchAny" since typically
untagged voice traffic will be present on a Voice port.
When you indicate Specify P-Bit for the P-Bit Source, enter the
P-Bit value (5, 6, or 7) that matches the Expedited Forwarding
scheduling class type.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
See Creating Service-Tag Actions (on page 131).
Configure the IP Host for the ONT SIP
Voice Services.
Each voice service option requires an IP host definition object
that indicates an IP host address for VoIP, and references a tag
action that specifies the classifying and marking of packets from
the subscriber port into the service VLAN.
When the selected Host Protocol is dhcp, the IP addresses are
dynamically assigned. Even if the Static IP address, mask, and
gateway are specified, they are ignored when the selected Host
Protocol is dhcp.
Additionally, the SIP IP Host requires that the configuration-file
instance is indicated. Note: This specified instance must match
the instance indicated when retrieving the SIP configuration file
and applying it to the E7.

ONTs > Provisioned ONTs > IP Hosts > double-click
OntIPHost: SIP
See Configuring the IP Hosts for Voice Services (on page 202).
Instances 9 through 16 are used exclusively for VoIP files and
can be specified either by instance number alone or by "voip-<1
through 8>"

voip-1

Instance for VoIP (9)

voip-2

Instance for VoIP (10)

voip-3

Instance for VoIP (11)

voip-4

Instance for VoIP (12)

voip-5

Instance for VoIP (13)

voip-6

Instance for VoIP (14)

voip-7

Instance for VoIP (15)

voip-8

Instance for VoIP (16)

Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
376
Create a Dial Plan.
If a custom numbering plan is not applied when you create a SIP
gateway service, the default numbering plan table (Access) is
applied which contains a generic digit entry rule and a rule for
911 calling.

ONTs > Provisioned ONTs > ONT ID# > PON Upstream
CoS > Create
See Creating a Dial Plan and Rules (on page 206).
Create a SIP Gateway Profile.
Create a SIP gateway profile that is assigned to a SIP gateway
service provisioned on a Voice port. Setting up information that
is common to multiple subscribers is easily maintained in the
service profile.
When a profile is changed, all subscribers using that profile are
affected.

E7 > Profiles > Service > SIP GW > Create
See Creating a SIP Gateway Profile (on page 208).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
377
Step 3: Configure a PON
Enable the GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.

Admin State: enabled

Split Horizon: selected

Dynamic Bandwidth Allocation (DBA): selected

Shelf# > Card# (GPON) > GPON #

Click Apply from the menu.
See Configuring an E7 GPON Port (on page 232).
Create an ONT.
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT. ONTs are
created as follows:
Manually where the ONT is pre-provisioned by entering the ONT
serial number into the Create ONT dialogue box.
Automatically where the ONT is discovered on the network after
successfully completing the Remote ONT Activation Process.
Selecting System Assigned ID allows the automatic
assignment for the ONT ID.

ONTs > Provisioned ONTs > Provisioning > Create
See Creating GPON ONTs (on page 244).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
378
Retrieve and Apply the SIP Configuration
File.

1) Retrieve the SIP configuration file from an external server
that is local to the E7.

2) Apply the configuration file to the ONT, causing the ONT
to reset and use the new file.
Note: The configuration-file instance specified when retrieving
the SIP configuration file must match the instance indicated in
the E7 SIP IP Host.
Instances 9 through 16 are used exclusively for VoIP files and
can be specified either by instance number alone or by "voip-<1
through 8>"

voip-1

Instance for VoIP (9)

voip-2

Instance for VoIP (10)

voip-3

Instance for VoIP (11)

voip-4

Instance for VoIP (12)

voip-5

Instance for VoIP (13)

voip-6

Instance for VoIP (14)

voip-7

Instance for VoIP (15)

voip-8

Instance for VoIP (16)
Note: The ONT must be reset to factory default values before
downloading new configuration files.


ONTs > Config File Management > Action

Retrieve

Apply
See Retrieving and Applying a Configuration File (on page 237).
Configure an ONT Voice Port.
Configure an ONT voice (POTS) port for service.
For International deployments, the Caller ID protocol, Caller ID
Alert Signal, VMWI alert Signal, and POTS Loss Plan Values
are provisionable based on the host country. Refer to the Calix
Application Note: Using 700 ONT VoIP Configuration File for
specific International Dialing parameters.

ONTs > Provisioned ONTs > Ports

From the top of the Work Area, use the ONT drop-down list
to select the ONT on which to
add the service.

Voice-#

Click Apply on the menu.
See Configuring an ONT Voice Port (on page 260).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
379
Step 4: Configure subscriber services
Add SIP Service to the Voice (POTS) Port.
For the Universal Resource Indicator (URI) of the port, if a local URI is "aaa@bbb," "aaa" is the telephone number configured, and
"bbb" is the domain name of the SIP server configured.
Note: The "@bbb" portion of the URI is defined in the SIP configuration file that is referenced in the SIP Profile.

ONTs > Provisioned ONTS > Services > Table.

From the top of the Work Area, use the ONT drop-down list
service.

Create > SIP Service.
to select the ONT on which to add the
See Creating a SIP Voice Service (on page 313).
Verify the Service Operation
Click the Provisioning tab for the voice port. If service is operational, you will see a Service Status of registered.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
380
Example: HGW Service - External Mode
This topic shows an example process for provisioning Home Gateway Services on an E7
GPON ONT in external mode, where an RG configuration file is downloaded to the ONT
to fully manage the RG function. In this mode, the CMS/E7 do not provision the RG WAN
interface.
For most 836GE RSG deployments that involve data-only services, or access modes that
require a single VLAN service, the default RG profile that is created when the RSG becomes
operational is sufficient. However, when any customization is required that is not supported
by the default profile (associated with RG Management Mode: Native), it is necessary to use
an RG Configuration File.
1. Create an RG configuration file to deploy a common provisioning and service model
across all 700GE ONTs or 836GE RSG devices supporting Home Gateway. See Creating
an RG Configuration File (on page 194).
2. Download an existing configuration file onto the E7.

All ONTs in configuration file management mode will automatically receive this file.

Or, manually load the file on a particular ONT.
The file download mechanism is via OMCI file transfer. See Managing RG Configuration
Files.
See Overview: HGW Applications - External Mode (on page 48) for the sequence of linked
procedures for configuring the E7 and GPON ONTs home gateway services in external
mode.
Configuration considerations




From a CMS/E7 perspective, none of the “Native RG Management” options are
available for ONTs in this mode.
The RG portion of the ONT is completely managed by the configuration file, including
the WAN interfaces and everything related. In particular, the configuration file configures
the RG with one or more VLANs on the GPON WAN.
The CMS/E7 is still used for creating ONT Ethernet services, such as creating and
applying service-tag actions, bandwidth profiles, and multicast profiles when adding the
service to the RG. The service-match list and service-tag must match the RG WAN
interface VLAN, as specified in the configuration file.
All services on the ONT RG interface must be deleted before you can put the ONT in
External mode.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
381









The ONT must be reset to factory default values before downloading new configuration
files. This can be accomplished by either pressing and holding the reset button for 20
seconds or using the EWI. T-Series ONTs will reset to factory default settings during the
"retrieve ONT configuration file" step if a prior non-default configuration file is present
in the ONT. Perform the "apply ONT configuration file" step as soon as possible after
the retrieve step to minimize service disruptions.
An RG configuration file of a particular instance will be downloaded to ONTs with the
following conditions:

matching vendor, model and product code

configured in external mode

reference the particular RG configuration file instance
An RG configuration file defines 1-4 RG WAN interfaces, each with a unique VLAN.
When an RG configuration file is applied to an ONT, the ONT resets.
The configuration file management mode is supported on GPON only, not AE.
Both N:1 and 1:1 VLANs models are supported. Since the same configuration file will be
downloaded to each ONT, the OMCI is responsible for changing the VLAN on each
individual ONT.
In external configuration file managment mode, multiple Ethernet services can be created
on the RG interface, each on a different VLAN.
At most, one service is allowed to have an multicast-profile.
MVR video is supported.
Example deployment of services using the E7 configuration file:

RG management mode:
external

RG services:
GE-1 for High-Speed Internet (HSI) data service (Data1)
GE-2, GE-3, GE-4 for video service (MVR)
SIP
See Example Voice Services Provisioning from Port View (on page 373).

For RG specific services (not HB or FB), only “Change Tag” and “Add and Change
Tag” are supported.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
382
Step 1: Configure network uplinks


Configure Ethernet Interfaces
Configure Ethernet Ports
See procedures in Configuring the Network Uplink(s) for
GPON Service (on page 66).

Create Service VLANs
For example:

Data VLANs 10, 2, DHCP-snoop = enabled

Video (unicast) VLAN 104,
DHCP-snoop = enabled
IGMP-mode = flood

MVR (multicast) VLAN 101,
DHCP-snoop = enabled
IGMP-mode = snoop-suppress or proxy Note: (E7-20
only supports proxy IGMP mode, which requires a Proxy
IP Address indicated in the referenced IGMP Profile)

VLANs > Create
See Create the Service VLANs (on page 86).

Make Interfaces VLAN Members
Add uplink interface (LAG) to the service VLANs.

VLANs > Click Interface# > Action > Add/Remove
VLAN Members.

See Adding the Uplink Interface(s) to VLAN Memberships
(on page 107).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
383
Step 2: Create system profiles
Create Rules to Classify (Data) Traffic:
a) Create a Match List
For P-series ONTs, the default RG configuration file used by
the ONT specifies VLAN ID 10 for the HSI services.
Therefore, for HSI services, we also match on VLAN ID 10.
E7 > Profiles > Service > Tagging > Match Lists > Profiles
> Create
b) Create a Service Tag Action
We match on VLAN ID 10 and perform a change-tag action to
VLAN ID 2.
E7 > Profiles > Service > Tagging > Tag Actions > Profiles
> Create

See Creating a Service Match List and Rules (on page
127).

See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
384
Create Rules to Classify (Video) Traffic:
a) Create a Match List
The match list and tag actions are defined for a downstream
RG that is sending single-tagged traffic with a VLAN ID of
104.
E7 > Profiles > Service > Tagging > Match Lists > Profiles
> Create
b) Create a Service Tag Action
We match on 104, and perform a change-tag action to 104 as
it is sent upstream from the ONT. The service provider could
provision 104 in the default configuration file, and as long as
the match list included a tagged match rule for 104, they
could change the VLAN ID to whatever they desire.
E7 > Profiles > Service > Tagging > Tag Actions > Profiles
> Create

See Creating a Service Match List and Rules (on page
127).

See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
385
Configure the Ethernet Bandwidth
Profile.
Create Ethernet bandwidth profiles to specify the upstream
and downstream bandwidth rates to apply to the HSI and
video services.
For this example:
Peak
Committed US
US
DS
Data
10M
10M
0k
Video
1024k
8M
512k
E7 > Profiles > Service > Ethernet Bandwidth > Profiles >
Create

See Creating an Ethernet Bandwidth Profile (on page
167).
Create an MVR Profile and MVR VLAN Addresses, and then
Enable It.
For this example, the created MVR profile designates the
Multicast VLAN (101) as an MVR VLAN and no IP range is
specified, allowing all IGMP and Multicast traffic.
E7 > Profiles > Service > Multicast > MVR > Profiles >
Create

See Creating an MVR Profile and MVR VLAN Addresses
(on page 178).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
386
Configure the Ethernet Multicast Profile.
An Ethernet multicast profile enables provisioning of the IPTV
service limits that can be applied to subscriber services.
Select the MVR profile to be used by this profile.
Enter a Query Interval value that matches the query interval
of the upstream router that is acting as the IGMP querier.
The Convert to Unicast parameter should ONLY be enabled if
switches are deployed on the subscriber side that cannot
manage heavy multicast traffic. (Only Calix GX ONTs support
this feature.)
E7 > Profiles > Service > Multicast > Profiles > Create

See Creating an Ethernet Multicast Profile (on page 177)
Create an ONT Template.
Using CMS R12.1, you can provision an ONT template that
defines all of the key management aspects of the ONT as well
as the logical assignments of physical GE ports.

Management mode: external

WAN protocol: DHCP

DSCP/IP Precedence: access

Security profile: system-default

RG: GE 1

FB: GE 2, GE 3, GE 4

CMS > Profile > E7/ONT > Templates > ONT > Create

See Creating an ONT Template (on page 191).
Step 3: Configure a PON
Enable the GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.

In the Navigation tree, click the triangle-arrow
( ) to the left of the GPON line card, and then click the
specific GPON port from the tree.

See Configuring an E7 GPON Port (on page 232).
Ensure the WAN fiber is attached to the ONT.
Ensure the ONT is discovered.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
387
Create an ONT.
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT. ONTs are
created as follows:
Manually where the ONT is pre-provisioned by entering the
ONT serial number into the Create ONT dialogue box.
Automatically where the ONT is discovered on the network
after successfully completing the Remote ONT Activation
Process.
Selecting System Assigned ID allows the automatic
assignment for the ONT ID.

ONTs > Provisioned ONTs > Provisioning > Create
See Creating GPON ONTs (on page 244).
Apply the ONT Template.
Apply an ONT template that was previously created through
CMS R12.1 or later.

ONTs > Provisioned ONTs > Provisioning > Action >
Apply Template to ONT.

In the Apply Template dialog, select the template to apply
from the Template list.
See Applying an ONT Template (on page 257).
Retrieve and Apply the RG
Configuration File.

1) Retrieve the SIP configuration file from an external
server that is local to the E7.

2) Apply the configuration file to the ONT, causing the
ONT to reset and use the new file.
Note: The configuration-file instance specified when retrieving
the RG configuration file must match the instance indicated in
the ONT template.
Instances 17 through 24 are used exclusively for RG
configuration files and can be specified either by instance
number alone or by "rg-<1 through 8>"

rg-1

Instance for RG (17)

rg-2

Instance for RG (18)

rg-3

Instance for RG (19)

rg-4

Instance for RG (20)

rg-5

Instance for RG (21)

rg-6

Instance for RG (22)

rg-7

Instance for RG (23)

rg-8

Instance for RG (24)
Note: The ONT must be reset to factory default values before
downloading new configuration files.


ONTs > Config File Management > Action

Retrieve

Apply
See Retrieving and Applying a Configuration File (on page
237).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
388
Step 4: Configure subscriber services
Add the Data Service to the RG Interface and Video Service to the FB Interface.
From one ONT Services page, add all Home Gateway Services, entering the subscriber information once and using the Copy to All
Ports function to simplify provisioning.

ONTS > Provisioned ONTs > Ports > Provisioning

From the top of the Work Area, use the ONT drop-down list
service.

RG-1 > Create > Gateway Service

See Creating Gateway Data and Video Services with Form View (on page 275), and Creating a Gateway Video Service with Table
View (on page 295).

ONTS > Provisioned ONTs > Ports > Provisioning

From the top of the Work Area, use the ONT drop-down list
service.

FB-1 > Create > Video Service
to select the ONT on which to add the
to select the ONT on which to add the
See Example: SIP GW Voice Services (on page 373) for instructions on provisioning a SIP gateway voice service.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
389
Example: Multicast IPTV over L2 Bridge Wi-Fi
This topic shows an example process for provisioning residential services on an E7 GPON
844G/854G GigaCenter that supports dual-band concurrent Wi-Fi, allowing continued
usage of the 2.4 GHz band for data and legacy consumer devices while supporting IPTV at
5.0 GHz provisioned as a bridged service.
GigaCenters 5.0 GHz radio has a Wi-Fi QoS feature that is assigned to a particular SSID.
The pre-defined IPTV SSID sets the priority of video traffic over best-effort data services
that are assigned to other SSIDs in the 5.0 GHz band.
For most GigaCenter deployments that involve data-only services, or access modes that
require a single VLAN service, the default RG configuration file on the GigaCenter is
sufficient. However, when deploying L2 bridged services, the RG configuration file requires
customization as follows:
1. Create an RG configuration file to deploy a common provisioning and service model
across all GigaCenter devices supporting Home Gateway. See Creating an RG Configuration
File (on page 194).
2. Using an FTP client, transfer the file to an FTP server.
3. Download the configuration file from the FTP server onto the E7.

All ONTs in external management mode will automatically receive this file.

Or, manually load the file on a particular ONT.
The file download mechanism is via OMCI file transfer. See Retrieving and Applying a
Configuration File (on page 237).
See Overview: HGW Applications - External Mode (on page 48) for the sequence of linked
procedures for configuring the E7 and GPON ONTs home gateway services in external
mode.
Configuration considerations




The RG portion of the ONT is completely managed by the configuration file, including
the RG service WAN VLANs and everything related.
The CMS/E7 is still used for creating ONT Ethernet services, such as creating and
applying service-tag actions, bandwidth profiles, and multicast profiles when adding the
service to the RG. The service-match list and service-tag must match the RG service
WAN VLAN, as specified in the configuration file.
All services on the ONT RG interface must be deleted before you can put the ONT in
External mode.
For RG specific services, only “Change Tag” and “Add and Change Tag” are supported.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
390







An RG configuration file of a particular instance will be downloaded to ONTs with the
following conditions:

matching vendor, model and product code

configured in external mode

reference the particular RG configuration file instance
In external management mode, an RG configuration file defines 1-4 RG WAN interfaces,
where multiple Ethernet services can be created on the RG interface, each with a unique
VLAN.
When an RG configuration file is applied to an ONT, the ONT resets.
Both N:1 and 1:1 VLANs models are supported. Since the same configuration file will be
downloaded to each ONT, the OMCI is responsible for changing the VLAN on each
individual ONT.
GigaCenters 5.0 GHz radio has a Wi-Fi QoS feature that is assigned to a pre-defined
IPTV SSID. The pre-defined IPTV SSID sets the priority of video traffic over best-effort
data services that are assigned to other 5.0 GHz SSIDs.
At most, one service is allowed to have a multicast-profile.
MVR video is supported for Full-Bridge, L2 Bridge, and RG interfaces.
Example deployment of services using the RG configuration file:

RG management mode:
external

HSI services over RG
RG-1 for High-Speed Internet (HSI) data service (Gateway Service:1)

IPTV services over L2 bridge
Associate interface Ethernet port 2 to Layer 2 Bridge for L2 bridged video service (MVR)
(Gateway Service:2)



Set-top box communication is contained within L2 bridge
Must use 5GHz_IPTV_SSIDxxxxxx for prioritization of IPTV streams, where the last
six digits are the FSAN.
DVR must be wired to the GigaCenter.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
391
Step 1: Configure network uplinks
Create Service VLANs.
For example:

Data VLAN 10
DHCP-snoop = enabled
MACFF = enabled
IP Source Verify = enabled

Video (unicast) VLAN 106,
DHCP-snoop = enabled
MACFF = enabled
IP Source Verify = enabled
IGMP-mode = flood

MVR (multicast) VLAN 101
IGMP-mode = proxy Note: (E7-20 only supports proxy
IGMP mode, which requires a Proxy IP Address indicated
in the referenced IGMP Profile)

VLANs > Create
See Create the Service VLANs (on page 86).
Configure Ethernet Interfaces

Create LAG

Role = trunk
Configure Ethernet Ports.

Interface = LAG

Admin State = enabled
See procedures in Configuring the Network Uplink(s) for
GPON Service (on page 66).
Make Interfaces VLAN Members.
Add uplink interface (LAG) to the service VLANs.

VLANs > Click Interface# > Action > Add/Remove
VLAN Members.
See Adding the Uplink Interface(s) to VLAN Memberships (on
page 107).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
392
Step 2: Create system profiles
Create Rules to Classify (Data) Traffic:
a) Create a Match List
For P-series ONTs, the default RG configuration file used by
the ONT specifies VLAN ID 10 for the HSI services.
Therefore, for HSI services, we also match on VLAN ID 10.
E7 > Profiles > Service > Tagging > Match Lists > Profiles
> Create
b) Create a Service Tag Action
We match on VLAN ID 10, perform a change-tag action to
VLAN ID 10, and set P-bit 0.
E7 > Profiles > Service > Tagging > Tag Actions > Profiles
> Create

See Creating a Service Match List and Rules (on page
127).

See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
393
Create Rules to Classify (Video) Traffic:
a) Create a Match List
The match list and tag actions are defined for a downstream
RG that is sending single-tagged traffic with a VLAN ID of
106.
E7 > Profiles > Service > Tagging > Match Lists > Profiles
> Create
b) Create a Service Tag Action
We match on 106, perform a change-tag action to 106, and
set P-bit 4 as it is sent upstream from the ONT. The service
provider could provision 106 in the default configuration file,
and as long as the match list included a tagged match rule for
106, they could change the VLAN ID to whatever they desire.
E7 > Profiles > Service > Tagging > Tag Actions > Profiles
> Create

See Creating a Service Match List and Rules (on page
127).

See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
394
Configure the Ethernet Bandwidth
Profile.
Create Ethernet bandwidth profiles to specify the upstream
and downstream bandwidth rates to apply to the HSI and
video services.
For this example:
Peak
Committed US
US
DS
Data
100m
100m
0k
Video
100m
100m
64k
E7 > Profiles > Service > Ethernet Bandwidth > Profiles >
Create

See Creating an Ethernet Bandwidth Profile (on page
167).
Create an MVR Profile and MVR VLAN
Addresses, and then Enable It.
For this example, the created MVR profile designates the
Multicast VLAN (101) as an MVR VLAN and no IP range is
specified, allowing all IGMP and Multicast traffic.
E7 > Profiles > Service > Multicast > MVR > Profiles >
Create

See Creating an MVR Profile and MVR VLAN Addresses
(on page 178).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
395
Configure the Ethernet Multicast Profile.
An Ethernet multicast profile enables provisioning of the IPTV
service limits that can be applied to subscriber services.
Select the MVR profile to be used by this profile.
Enter a Query Interval value that matches the query interval
of the upstream router that is acting as the IGMP querier.
The Convert to Unicast parameter should ONLY be enabled if
switches are deployed on the subscriber side that cannot
manage heavy multicast traffic. (Only Calix GX ONTs support
this feature.)
E7 > Profiles > Service > Multicast > Profiles > Create

See Creating an Ethernet Multicast Profile (on page 177)
Create an ONT Template.
Using CMS R12.1 or higher, you can provision an ONT
template that defines all of the key management aspects of
the ONT as well as the logical assignments of physical GE
ports.

Management mode: external

Config File Instance: 20

Security profile: system-default

RG: GE 1, GE 2, GE 3, GE 4
CMS > Profile > E3-48C/E5-48/E7/ONT > Templates > ONT
> Create

See Creating an ONT Template (on page 191).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
396
Create an RG Configuration File.
When deploying IPTV over L2 bridged wireless, the RG configuration file requires customization to define the SSIDs and create the L2
bridge. Ensure the GigaCenter is not connected to a PON, has an operational image loaded (like 11.0.1.x), and that the defaults are in
place. You can do this by going to Utilities > Restore Defaults, and then wait for it to reboot.
Setup the SSID.

SSID (network name): 5GHz_IPTV_SSIDxxxxxx (IPTV SSID has the last six digits of the FSAN)

SSID state: enabled

Broadcast SSID: disabled

Allow guest network clients to communicate with each other: selected

Allow SSID to be used in a bridged WAN service: selected

See Creating an RG Configuration File (on page 194).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
397
Define the HSI service VLAN.

IGMP: disabled

NAT: enabled

Connection type: DHCP

Tag Action: tagging

VLAN ID: 10

Priority: 0
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
398
Define the Video service VLAN.
Define your L2 Bridge service VLAN and pick the ports you want in the L2 bridge. Calix recommends at least one LAN port for the
DVR.

IGMP: enabled

Connection type: Layer 2 Bridged

Tag Action: tagging

VLAN ID: 106

Priority: 4

Associate interface to Layer 2 Bridge: Ctrl+click one or more Ethernet port(s) and the 5GHz_IPTV_SSID
Save the Configuration File.
Utilities > Configuration Save
Using an FTP client, transfer the file to an FTP server that is reachable by the E7.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
399
Step 3: Configure a PON
Enable the GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.

In the Navigation tree, click the triangle-arrow
( ) to the left of the GPON line card, and then click the
specific GPON port from the tree.

See Configuring an E7 GPON Port (on page 232).
Ensure the WAN fiber is attached to the ONT.
Ensure the ONT is discovered.
Retrieve and Apply the RG
Configuration File.
1) Retrieve the RG configuration file from an external server
that is local to the E7.
Note: The configuration-file instance specified when retrieving
the RG configuration file must match the instance indicated in
the ONT template.
Instances 17 through 24 are used exclusively for RG
configuration files and can be specified either by instance
number alone or by "rg-<1 through 8>"

rg-1

Instance for RG (17)

rg-2

Instance for RG (18)

rg-3

Instance for RG (19)

rg-4

Instance for RG (20)

rg-5

Instance for RG (21)

rg-6

Instance for RG (22)

rg-7

Instance for RG (23)

rg-8

Instance for RG (24)
Here
Note: The ONT must be reset to factory default values before
downloading new configuration files.


2) Apply the configuration file to the ONT, causing the
ONT to reset and use the new file.


ONTs > Config File Management > Action

Retrieve

Apply
See Retrieving and Applying a Configuration File (on page
237).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
400
Create an ONT.
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT. ONTs are
created as follows:
Manually where the ONT is pre-provisioned by entering the
ONT serial number into the Create ONT dialog box.
Automatically where the ONT is discovered on the network
after successfully completing the Remote ONT Activation
Process.
Selecting System Assigned ID allows the automatic
assignment for the ONT ID.

ONTs > Provisioned ONTs > Provisioning > Create
See Creating GPON ONTs (on page 244).
Step 4: Configure subscriber services
Add the Data Service and Video Service.
From one ONT Services page, you could add all Home Gateway Services.

ONTS > Provisioned ONTs > Ports > Provisioning

From the top of the Work Area, use the ONT drop-down list
service.

RG-1 > Create > Gateway Service

See Creating Gateway Data and Video Services with Form View (on page 275), and Creating a Gateway Video Service with Table
View (on page 295).

ONTS > Provisioned ONTs > Ports > Provisioning

From the top of the Work Area, use the ONT drop-down list
service.

RG-1 > Create > Gateway Service
to select the ONT on which to add the
to select the ONT on which to add the
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
401
Example: Multicast IPTV over RG Wi-Fi
This topic shows an example process for provisioning residential services on an E7 GPON
844G/854G GigaCenter that supports dual-band concurrent Wi-Fi, allowing continued
usage of the 2.4 GHz band for data and legacy consumer devices while supporting IPTV at
5.0 GHz provisioned as a bridged service.
GigaCenters 5.0 GHz radio has a Wi-Fi QoS feature that can be assigned to different SSIDs.
The pre-defined IPTV SSID sets the priority of video traffic over best-effort data services
that are assigned to other SSIDs.
For most GigaCenter deployments that involve data-only services, or access modes that
require a single VLAN service, the default RG configuration file that is created when the
GigaCenter becomes operational is sufficient. However, when deploying L2 bridged services,
the RG configuration file requires customization as follows:
1. Create an RG configuration file to deploy a common provisioning and service model
across all GigaCenter devices supporting Home Gateway. See Creating an RG Configuration
File (on page 194).
2. Using an FTP client, transfer the file to an FTP server.
3. Download the configuration file from the FTP server onto the E7.

All ONTs in configuration file management mode will automatically receive this file.

Or, manually load the file on a particular ONT.
The file download mechanism is via OMCI file transfer. See Retrieving and Applying a
Configuration File (on page 237).
See Overview: HGW Applications - External Mode (on page 48) for the sequence of linked
procedures for configuring the E7 and GPON ONTs home gateway services in external
mode.
Configuration considerations




The RG portion of the ONT is completely managed by the configuration file, including
the RG service WAN VLANs and everything related.
The CMS/E7 is still used for creating ONT Ethernet services, such as creating and
applying service-tag actions, bandwidth profiles, and multicast profiles when adding the
service to the RG. The service-match list and service-tag must match the RG service
WAN VLAN, as specified in the configuration file.
All services on the ONT RG interface must be deleted before you can put the ONT in
External mode.
For RG specific services, only “Change Tag” and “Add and Change Tag” are supported.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
402







An RG configuration file of a particular instance will be downloaded to ONTs with the
following conditions:

matching vendor, model and product code

configured in external mode

reference the particular RG configuration file instance
In external management mode, an RG configuration file defines 1-4 RG WAN interfaces,
where multiple Ethernet services can be created on the RG interface, each with a unique
VLAN.
When an RG configuration file is applied to an ONT, the ONT resets.
Both N:1 and 1:1 VLANs models are supported. Since the same configuration file will be
downloaded to each ONT, the OMCI is responsible for changing the VLAN on each
individual ONT.
GigaCenters 5.0 GHz radio has a Wi-Fi QoS feature that is assigned to a pre-defined
IPTV SSID. The pre-defined IPTV SSID sets the priority of video traffic over best-effort
data services that are assigned to other 5.0 GHz SSIDs.
At most, one service is allowed to have a multicast-profile.
MVR video is supported for Full-Bridge, L2 Bridge, and RG interfaces.
Example deployment of services using the RG configuration file:

RG management mode:
native

All HSI and IPTV services over RG
GE-1 for High-Speed Internet (HSI) data service (Gateway Service:1)
GE-4 for video service (MVR) (Gateway Service:2)


Must use 5GHz_IPTV_SSIDxxxxxx for prioritization of IPTV streams, where the last
six digits are the FSAN.
DVR must be wired.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
403
Step 1: Configure network uplinks
Create Service VLANs
For example:

Data VLANs 10,
DHCP-snoop = enabled

Video (unicast) VLAN 106,
DHCP-snoop = enabled
IGMP-mode = flood

MVR (multicast) VLAN 101,
DHCP-snoop = enabled
IGMP-mode = snoop-suppress or proxy Note: (E7-20
only supports proxy IGMP mode, which requires a Proxy
IP Address indicated in the referenced IGMP Profile)

VLANs > Create
See Create the Service VLANs (on page 86).
Configure Ethernet Interfaces

Create LAG

Role = trunk
Configure Ethernet Ports

Interface = LAG

Admin State = enabled
See procedures in Configuring the Network Uplink(s) for
GPON Service (on page 66).
Make Interfaces VLAN Members
Add uplink interface (LAG) to the service VLANs.

VLANs > Click Interface# > Action > Add/Remove
VLAN Members.
See Adding the Uplink Interface(s) to VLAN Memberships (on
page 107).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
404
Step 2: Create system profiles
Create Rules to Classify (Data) Traffic:
a) Create a Match List
For P-series ONTs, the default RG configuration file used by
the ONT specifies VLAN ID 10 for the HSI services.
Therefore, for HSI services, we also match on VLAN ID 10.
E7 > Profiles > Service > Tagging > Match Lists > Profiles
> Create
b) Create a Service Tag Action
We match on VLAN ID 10, perform a change-tag action to
VLAN ID 10, and set P-bit 0.
E7 > Profiles > Service > Tagging > Tag Actions > Profiles
> Create

See Creating a Service Match List and Rules (on page
127).

See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
405
Create Rules to Classify (Video) Traffic:
a) Create a Match List
The match list and tag actions are defined for a downstream
RG that is sending single-tagged traffic with a VLAN ID of
106.
E7 > Profiles > Service > Tagging > Match Lists > Profiles
> Create
b) Create a Service Tag Action
We match on 106, perform a change-tag action to 106, and
set P-bit 0 as it is sent upstream from the ONT. The service
provider could provision 106 in the default configuration file,
and as long as the match list included a tagged match rule for
106, they could change the VLAN ID to whatever they desire.
E7 > Profiles > Service > Tagging > Tag Actions > Profiles
> Create

See Creating a Service Match List and Rules (on page
127).

See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
406
Configure the Ethernet Bandwidth
Profile.
Create Ethernet bandwidth profiles to specify the upstream
and downstream bandwidth rates to apply to the HSI and
video services.
For this example:
Peak
Committed US
US
DS
Data
100m
100m
0k
Video
100m
100m
64k
E7 > Profiles > Service > Ethernet Bandwidth > Profiles >
Create

See Creating an Ethernet Bandwidth Profile (on page
167).
Create an MVR Profile and MVR VLAN
Addresses, and then Enable It.
For this example, the created MVR profile designates the
Multicast VLAN (101) as an MVR VLAN and no IP range is
specified, allowing all IGMP and Multicast traffic.
E7 > Profiles > Service > Multicast > MVR > Profiles >
Create

See Creating an MVR Profile and MVR VLAN Addresses
(on page 178).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
407
Configure the Ethernet Multicast Profile.
An Ethernet multicast profile enables provisioning of the IPTV
service limits that can be applied to subscriber services.
Select the MVR profile to be used by this profile.
Enter a Query Interval value that matches the query interval
of the upstream router that is acting as the IGMP querier.
The Convert to Unicast parameter should ONLY be enabled if
switches are deployed on the subscriber side that cannot
manage heavy multicast traffic. (Only Calix GX ONTs support
this feature.)
E7 > Profiles > Service > Multicast > Profiles > Create

See Creating an Ethernet Multicast Profile (on page 177)
Create an ONT Template.
Using CMS R12.1 or higher, you can provision an ONT
template that defines all of the key management aspects of
the ONT as well as the logical assignments of physical GE
ports.

Management mode: external

Config File Instance: 20

Security profile: system-default

RG: GE 1, GE 2, GE 3, GE 4
CMS > Profile > E3-48C/E5-48/E7/ONT > Templates > ONT
> Create

See Creating an ONT Template (on page 191).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
408
Create an RG Configuration File.
When deploying IPTV, the RG configuration file requires customization to define the 5GHz_IPTV_SSID for prioritization of IPTV
streams.
Setup the SSID.

SSID (network name): 5GHz_IPTV_SSIDxxxxxx

SSID state: enabled

Broadcast SSID: disabled

Allow guest network clients to communicate with each other: selected

Allow SSID to be used in a bridged WAN service: unselected

See Creating an RG Configuration File (on page 194).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
409
Define the HSI service VLAN.

IGMP: disabled

NAT: enabled

Connection type: DHCP

Tag Action: tagging

VLAN ID: 10

Priority: 0
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
410
Define the Video service VLAN.

IGMP: enabled

Connection type: DHCP (IPoE)

Tag Action: tagging

VLAN ID: 106

Priority: 4
Save the Configuration File.
Utilities > Configuration Save
Using an FTP client, transfer the file to an FTP server.
Step 3: Configure a PON
Enable the GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.

In the Navigation tree, click the triangle-arrow
( ) to the left of the GPON line card, and then click the
specific GPON port from the tree.

See Configuring an E7 GPON Port (on page 232).
Ensure the WAN fiber is attached to the ONT.
Ensure the ONT is discovered.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
411
Retrieve and Apply the RG
Configuration File.
1) Retrieve the RG configuration file from an external server
that is local to the E7.
Note: The configuration-file instance specified when retrieving
the RG configuration file must match the instance indicated in
the ONT template.
Instances 17 through 24 are used exclusively for RG
configuration files and can be specified either by instance
number alone or by "rg-<1 through 8>"

rg-1

Instance for RG (17)

rg-2

Instance for RG (18)

rg-3

Instance for RG (19)

rg-4

Instance for RG (20)

rg-5

Instance for RG (21)

rg-6

Instance for RG (22)

rg-7

Instance for RG (23)

rg-8

Instance for RG (24)
Note: The ONT must be reset to factory default values before
downloading new configuration files.


2) Apply the configuration file to the ONT, causing the
ONT to reset and use the new file.


ONTs > Config File Management > Action

Retrieve

Apply
See Retrieving and Applying a Configuration File (on page
237).
Create an ONT.
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT. ONTs are
created as follows:
Manually where the ONT is pre-provisioned by entering the
ONT serial number into the Create ONT dialog box.
Automatically where the ONT is discovered on the network
after successfully completing the Remote ONT Activation
Process.
Selecting System Assigned ID allows the automatic
assignment for the ONT ID.

ONTs > Provisioned ONTs > Provisioning > Create
See Creating GPON ONTs (on page 244).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
412
Step 4: Configure subscriber services
Add the Data Service and Video Service.
From one ONT Services page, you could add all Home Gateway Services, entering the subscriber information once and using the
Copy to All Ports function to simplify provisioning.

ONTS > Provisioned ONTs > Ports > Provisioning

From the top of the Work Area, use the ONT drop-down list
service.

RG-1 > Create > Gateway Service

See Creating Gateway Data and Video Services with Form View (on page 275), and Creating a Gateway Video Service with Table
View (on page 295).

ONTS > Provisioned ONTs > Ports > Provisioning

From the top of the Work Area, use the ONT drop-down list
service.

RG-1 > Create > Gateway Service
to select the ONT on which to add the
to select the ONT on which to add the
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
413
Example: HGW Service - P-Series Native Mode
This topic shows an example process for provisioning Home Gateway Services on an E7
GPON P-Series ONT in native mode, which is the default behavior of P-series ONTs,
where the CMS/E7 directly provision up to 4 RG WAN interfaces. This mode is limited to a
single VLAN (service) on the RG WAN interface. However, voice and legacy L2 services are
still natively supported for non-RG ports.
See Overview: HGW Applications - Native Mode (on page 54) for the sequence of linked
procedures for configuring the E7 and GPON ONTs home gateway services in native mode.
An ONT Ethernet port can be a member of either the RG (Residential Gateway) or FB (Full
Bridge) interface group, or not a member of either, allowing it to operate as a normal L2
classic port (Half-Bridge mode).

Residential Gateway (RG) Mode
The RG services are named as Gateway Services, where only four services are supported
with only one of them can have a multicast profile assignment. The ONT RG interface
supports up to 4 services.

Full-Bridge (FB) Mode
With Full-Bridge mode, traffic can pass between LAN ports within the same bridge.
Support of Full-Bridge is assumed to be for video multicast services only to enable
Whole-Home DVR support, allowing communication between set-top boxes. A single
multicast VLAN can be associated to the Full-Bridge group. Applications that require
Full-Bridge support of IPTV enabled devices along with media-clients with a single IP
Host supporting data and unicast applications requires an auxiliary switch be installed
behind the LAN port and continued support of Half-Bridge. The ONT Full-Bridge
interface only supports 1 service.

Half-Bridge (HB or Classic) Mode
In Half-Bridge mode, the port operates as a normal L2 classic port. This operation allows
traffic to only pass between the WAN and LAN ports and restricts traffic from passing
between LAN ports within the same bridge.
Configuration guidelines


When an 836 RSG ONT is created on the E7, all ONT Ethernet ports are assigned as
members of the RG port. Ports can be removed from the RG group, and possibly added
to the FB interface group.
When a 700GE ONT is created on the E7, the ONT Ethernet ports are not a member of
the RG or FB interface group, and can be added to either the RG or FB interface group.
The 700GE resets whenever it transitions into or out of RG mode. For example, when
the first ONT Ethernet port is added to the RG group on a 700GE ONT, the ONT
resets. Similarly, when the last Ethernet port is removed from the RG group, the ONT
resets.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
414


The 836 RSG always runs in RG mode. Even if all ONT Ethernet ports are removed
from the RG interface group, the wifi is still a member of the RG group, causing the
ONT to always remain in RG mode.
E7 native mode provisioning allows the E7 to directly provision up to 4 RG WAN
interfaces, without the need for an ACS or RG external configuration file. With the
native provisioning mode, you can do the following:

Create up to 4 RG WAN interfaces. However, a 5th RG WAN interface can be
created for the sole purpose of OOB management/TR69 access, if desired.

Specify the RG WAN interface protocol:

IPoE DHCP

IPoE static

PPPoE
Note: WAN protocol is only selectable on the RG WAN interface associated with
the Ethernet service Data1. The RG WAN interfaces for Ethernet service Data 2-4
are DHCP only.




Optionally enable IGMP on a single RG WAN interface (for example, video service).

Optionally enable MVR on a single RG WAN interface (for example, video service).
For RG specific services (not HB or FB), only “Change Tag” and “Add and Change
Tag” are supported.
For RG specific services (not HB or FB), multicast maps are not supported for RG based
video services.
In Native management mode, only one Ethernet service can be created on the RG
interface.
Example deployment of 836GE ONT services using the Native mode:

RG management mode:
native

RG interface:
GE-1 for High-Speed Internet (HSI) data service

FB interface:
GE-2, GE-3, GE-4 for video service (MVR)

Voice ports:
SIP
See Example Voice Services Provisioning from Port View (on page 373).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
415
Step 1: Configure network uplinks


Configure Ethernet Interfaces
Configure Ethernet Ports
See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
See procedures in Configuring the Network Uplink(s) for
GPON Service (on page 66).

Create Service VLANs
For example:

Data VLANs 10, 2, DHCP-snoop = enabled

Video (unicast) VLAN 104,
DHCP-snoop = enabled
IGMP-mode = flood

MVR (multicast) VLAN 101,
DHCP-snoop = enabled
IGMP-mode = snoop-suppress or proxy Note: (E7-20
only supports proxy IGMP mode, which requires a Proxy
IP Address indicated in the referenced IGMP Profile)

VLANs > Create
See Create the Service VLANs (on page 86).

Make Interfaces VLAN Members
Add uplink interface (LAG) to the service VLANs.

VLANs > Click Interface# > Action > Add/Remove
VLAN Members.

See Adding the Uplink Interface(s) to VLAN Memberships
(on page 107).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
416
Step 2: Create system profiles
Create Rules to Classify (Data) Traffic:
a) Create a Match List
For P-series ONTs, the default RG configuration file used by
the ONT specifies VLAN ID 10 for the HSI services.
Therefore, for HSI services, we also match on VLAN ID 10.
E7 > Profiles > Service > Tagging > Match Lists > Profiles
> Create
b) Create a Service Tag Action
We match on VLAN ID 10 and perform a change-tag action to
VLAN ID 2.
E7 > Profiles > Service > Tagging > Tag Actions > Profiles
> Create

See Creating a Service Match List and Rules (on page
127).

See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
417
Create Rules to Classify (Video) Traffic:
a) Create a Match List
The match list and tag actions are defined for a downstream
RG that is sending single-tagged traffic with a VLAN ID of
104.
E7 > Profiles > Service > Tagging > Match Lists > Profiles
> Create
b) Create a Service Tag Action
We match on 104, and perform a change-tag action to 104 as
it is sent upstream from the ONT. The service provider could
provision 104 in the default configuration file, and as long as
the match list included a tagged match rule for 104, they
could change the VLAN ID to whatever they desire.
E7 > Profiles > Service > Tagging > Tag Actions > Profiles
> Create

See Creating a Service Match List and Rules (on page
127).

See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
418
Configure the Ethernet Bandwidth
Profile.
Create Ethernet bandwidth profiles to specify the upstream
and downstream bandwidth rates to apply to the HSI and
video services.
For this example:
Peak
Committed US
US
DS
Data
10M
10M
0k
Video
1024k
8M
512k
E7 > Profiles > Service > Ethernet Bandwidth > Profiles >
Create

See Creating an Ethernet Bandwidth Profile (on page
167).
Create an MVR Profile and MVR VLAN Addresses, and then
Enable It.
For this example, the created MVR profile designates the
Multicast VLAN (101) as an MVR VLAN and no IP range is
specified, allowing all IGMP and Multicast traffic.
E7 > Profiles > Service > Multicast > MVR > Profiles >
Create

See Creating an MVR Profile and MVR VLAN Addresses
(on page 178).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
419
Configure the Ethernet Multicast Profile.
An Ethernet multicast profile enables provisioning of the IPTV
service limits that can be applied to subscriber services.
Select the MVR profile to be used by this profile.
Enter a Query Interval value that matches the query interval
of the upstream router that is acting as the IGMP querier.
The Convert to Unicast parameter should ONLY be enabled if
switches are deployed on the subscriber side that cannot
manage heavy multicast traffic. (Only Calix GX ONTs support
this feature.)
E7 > Profiles > Service > Multicast > Profiles > Create

See Creating an Ethernet Multicast Profile (on page 177)
Create an ONT Template.
Using CMS R12.1, you can provision an ONT template that
defines all of the key management aspects of the ONT as well
as the logical assignments of physical GE ports.

Management mode: Native

WAN protocol: DHCP

DSCP/IP Precedence: access

Security profile: system-default

RG: GE 1

FB: GE 2, GE 3, GE 4

CMS > Profile > E7/ONT > Templates > ONT > Create

See Creating an ONT Template (on page 191).
Step 3: Configure a PON
Enable the E7 GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.

In the Navigation tree, click the triangle-arrow to the left of
the GPON line card, and then click the specific GPON
port from the tree.

See Configuring an E7 GPON Port (on page 232).
Ensure the WAN fiber is attached to the ONT.
Ensure the ONT is discovered.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
420
Create an ONT.
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT. ONTs are
created as follows:
Manually where the ONT is pre-provisioned by entering the
ONT serial number into the Create ONT dialog box.
Automatically where the ONT is discovered on the network
after successfully completing the Remote ONT Activation
Process.
Selecting System Assigned ID allows the automatic
assignment for the ONT ID.

ONTs > Provisioned ONTs > Provisioning > Create
See Creating GPON ONTs (on page 244).
Apply the ONT Template.
Apply an ONT template that was previously created through
CMS R12.1 or later.

ONTs > Provisioned ONTs > Provisioning > Action >
Apply Template to ONT.

In the Apply Template dialog, select the template to apply
from the Template list.
See Applying an ONT Template (on page 257).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
421
Step 4: Configure subscriber services
Add the Data Service to the RG Interface and Video Service to the FB Interface.
From one ONT Services page, add all Home Gateway Services, entering the subscriber information once and using the Copy to All
Ports function to simplify provisioning.

ONTS > Provisioned ONTs > Services > Form (select the ONT ID from the drop-down list)

See Configuring Data Services (on page 269), and Configuring IP Video Services (on page 285).
See Example: SIP GW Voice Services (on page 373) for instructions on provisioning a SIP gateway voice service.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
422
Example: HGW Service - TR-069
This topic shows an example process for using Consumer Connect in conjunction with an
E7 GPON deployment. The example procedure in this topic assumes that the services
provisioned on the 836GE or T-series during the Example Home Gateway Service - External
Configuration File (on page 380) are in place.
Note: This example process applies applies to Calix ONTs that support TR-69 CPE
management, including the P-Series 836GE (E7 R2.2 and higher) and T-Series T07xG (E7
R2.3 and higher) models.
The TR-069 protocol allows operators to deploy a common management and service model
for both xDSL and fiber-based deployments. The protocol provides a safe autoconfiguration tool as well as controlling CPE management functions. TR-069 addresses the
vast number of CPE Internet access devices such as modems, routers, gateways, set-top
boxes, and VoIP-phones. The technical standard was developed for automatic configuration
of these devices with Auto Configuration Servers (ACS).
Calix Consumer Connect is an Auto-Configuration Server (ACS) that uses TR-069 standard
protocol for remote management of CPE devices including the Calix Residential Services
Gateway. All TR-069 compliant devices adhere to a well-defined data model that describes
common TR-98 management objects for the CPE. Using the TR-069 protocol, Consumer
Connect provides remote configuration, provisioning and device management.
When the system is configured for TR-069 management, the RG TR-069 client
communicates with an Auto-Configuration Servers (ACS). For example, without modifying
the applied external configuration file, you can create an RG management profile that
specifies a TR-98 management object with associated parameter value that the ACS sends to
the ONT, either when the ONT comes online and checks in with the ACS, or on a
scheduled basis.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
423
Note: For additional information on set-up and maintenance of the Consumer Connect
interface, refer to the documentation provided with Consumer Connect software. Also see,
Compass QT-14-001 Calix ONT Home Gateway Setup via Consumer Connect and ONT QT-13-005
Managing Calix 836GE RSGs with Consumer Connect.
The TR-069 client can be configured to run in the following management modes:


in-band runs on an existing RG WAN interface. Typically, the path to the ACS server
utilizes an existing RG service such as Gateway Service: 1 (for example, a HSI service).
out-of-band runs on its own RG WAN interface. An independent VLAN outside of the
service VLANs is provisioned on both the RG and ONT to facilitate communication to
the ACS service.
Note: Whether the service provider is using public or private IPs on their ONT RG
interfaces, a routable path must exist between the WAN IP of the provisioned WAN
interface on the ONT and the Consumer Connect server.
See Overview: HGW Applications - TR-069 (on page 57) for the sequence of linked procedures
for configuring the E7 and GPON ONTs home gateway services with TR-069.
Configuration considerations












The ONT management mode (native or external) is irrelevant to the functionality of the
TR-069 client configured on the RG.
The system-default RG management profile provides in-band TR-069 management by
default.
Both in-band and out-of-band can be used as a means to provide a unicast path from the
TR-069 client to the ACS server.
The TR-069 management VLAN configuration is sent to the ONT via OMCI and causes
a WAN service to be created within the RG.
The ONTs RG interface object controls which RG service the TR-069 client will be
bound. That is, if you add an Ethernet service for in-band TR-069 to the ONT RG
interface, the TR-069 client will automatically be bound to this VLAN.
To enable out-of-band TR-069 you need to modify the RG management profile to
include VLAN, P-Bit, and bandwidth profile information.
The TR-069 management VLAN only supports the DHCP WAN protocol, so there are
no configuration options to change this setting.
Multiple Ethernet services can be created on the RG interface, each on a different
VLAN.
At most, one service is allowed to have a multicast profile.
The multicast profile is not allowed on the TR-069 management VLAN.
MVR video service is supported.
The TR-069 Management VLAN attribute must be set and the VLAN must match one
of the ONT Ethernet service VLANs.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
424
An out-of-band RG WAN interface can be the fifth RG WAN interface in the situation
where four RG WAN interfaces are in use.
A routable path must exist between the WAN IP of the provisioned WAN interface on
the ONT and the Consumer Connect server, whether the service provider is using public
or private IPs on the RG interfaces.
When a new CPE device checks-in with Consumer Connect, or any ACS, the TR-98
internet gateway device data model is provided by the CPE to the ACs server. This data
model provides all of the necessary definable and provisionable attributes by the ACS
server.
Associate the RG management profile to the RG interface using one of the following
methods:





Directly associate the profile to an RG interface.

(CMS R12.1 or later only) Reference the profile in an ONT Template and apply the
template to an ONT when configuring the PON.
Example deployment of services using the E7 configuration file:
RG management mode:

external
RG services:

GE-1 for High-Speed Internet (HSI) data service (Data1)
GE-2, GE-3, GE-4 for video service (MVR)
SIP
See Example Voice Services Provisioning from Port View (on page 373).
In-Band Management Mode
Configure triple-play services.
The following example procedure assumes that the triple-play
services are provisioned on the 836GE.
See procedure in the Example Home Gateway Service - External
Configuration File (on page 380) for GPON Services.
Create an RG Management Profile.
ONTs > Profiles > RG Management > Profiles > Create

See Creating an RG Management profile (on page 198).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
425
Associate the RG Management Profile.
The default configuration file used by the ONT used VLAN ID
10 for the HSI services. Therefore, for HSI services, we also
match on VLAN ID 10.
ONTs > Provisioned ONTs > Ports > (select the ONT ID
from the drop-down list)

See Configuring an ONT Residential Gateway Interface
(on page 262).

Also see Creating an ONT Template (on page 191).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
426
Log in to Consumer Connect Administrator.

Log in to the Consumer Connect (CC) Administrator, and then click CPE > Search to search for your ONT.

When you find your ONT, click on the tablet icon.

As shown below, the CPE (836GE) is in the process of checking in with the Auto-Configuration Servers (ACS) server. This process
typically takes less than 5 minutes.

Once the process is complete, the Connection Request URL, username, and password are all filled out. The CC server has
determined the CPE is using a data model of an Internet Gateway Device, and it is a member of the 836GE CPE group.

Note: When the 836GE is in GPON mode, the Connection Request username and password are set to be admin/admin.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
427
Log in to Consumer Connect Customer Service Representative Interface.

Log in to the Consumer Connect Customer Service Representatives (CSR) interface, click Devices, and then validate the
presence of your ONT.

Go to the subscriber page and assign the device to you. Ensure the serial number, manufacturer, and subscriber profile is correctly
chosen.

This completes the normal day-to-day process for a service provider.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
428
Out-of-Band Management Mode
Configure triple-play services.
The following example procedure assumes that the triple-play
services are provisioned on the 836GE.
See procedure in the Example Home Gateway Service - External
Configuration File (on page 380) for GPON Services.
Configure the Ethernet Bandwidth
Profile.
An Ethernet bandwidth profile specifies the upstream and
downstream bandwidth rates to apply to the HSI and video
services.
E7 > Profiles > Service > Ethernet Bandwidth > Profiles >
Create

See Creating an Ethernet Bandwidth Profile (on page
167).
Create an RG Management Profile.
ONTs > Profiles > RG Management > Profiles > Create

See Creating an RG Management profile (on page 198).
Configure the RG Interface.
Configure an ONT Residential Gateway (RG) interface for
service with the external management mode to allow the RF
service provisioning by an external RF configuration file or
ACS.
ONTS > Provisioned ONTs > Ports > Provisioning >
(select the ONT ID from the drop-down list) > RG-1
After the changes are made, click Apply.

See Configuring an ONT Residential Gateway Interface
(on page 262).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
429
Configure an ONT Template.
Alternatively, using CMS R12.1, you can provision an ONT
template that defines all of the key management aspects of
the ONT as well as the logical assignments of physical GE
ports.

Management mode: native

WAN protocol: DHCP

Security profile: system-default

RG: GE 1

FB: GE 2, GE 3, GE 4

CMS > Profile > E7/ONT > Templates > ONT

See Creating an ONT Template (on page 191).

See Applying an ONT Template (on page 257).
Log in to Consumer Connect Administrator.
Login to the Consumer Connect (CC) Administrator, and then wait for the ONT to complete the check-in process. You can observe
that the WAN address used to reach out to the ACs server is the interface you specified.
Download the Configuration File.
Retrieve and apply a previously created RG configuration file
to fully manage the RG functions.
Note: CMS 12.1 allows you can create a task to retrieve the
RF configuration file.
ONTS > Config file Management > Action (Retrieve|Apply)
For the Model, you can use "." characters as wildcard
characters.

“7..GE.” – will match any 700GE.

"8..GE.” or “836GE.” will match the 836GE.

The ‘.’ at the end is required because ONTs reports
spaces in the model number.
For the ONT Product, enter a code that indicates the ONT
product family. For example, all Calix ONTs that can support
RG use a product code of "S8".

See Creating an RF Configuration File (on page 194).

See Managing RG Configuration Files.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
430
Add the Subscriber Services to the ONT.
From one ONT Services page, add all Home Gateway Services, entering the subscriber information once and using the Copy to All
Ports function to simplify provisioning.
ONTS > Provisioned ONTs > Ports > Provisioning > (select the ONT ID from the drop-down list) > (double-click the ONT RG
Interface RG-1) > Create > Gateway Service.

See Configuring Data Services on an ONT Port, and Creating MVR Video Service on an ONT Ethernet Port.
ONTS > Provisioned ONTs > Services > Table > (select the ONT ID from the drop-down list) > Create > SIP Service
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
431
QoS Service Model Examples
The E7 supports the following GPON service models.





Multiple services, same traffic class (CoS), shared BW
Multiple services, same traffic class (CoS), independent BW
Multiple services, same traffic class (CoS), different P-Bits
Multiple services, same traffic class (CoS), independent BW, prioritized scheduling on the
PON
Single service with prioritization of flows within the service
Multiple services, same traffic class (CoS), shared BW Service
Model
This model is intended for more than one service being configured on a VLAN, where any
service is with no explicit PON upstream CoS mapping, and is backwards compatible and
upgrade compatible. Services provisioned with software version earlier than R2.2 will operate
the same after upgrading to R2.2 or later.
This model assigns four T-CONT types, each representing an aggregated class of service for
an ONT (BE, AF1, AF2, EF). The four T-CONT types are pre-assigned a class of service
and the provisioned services are required to have bandwidth profiles that match the class of
service. Also, bandwidth assigned to the T-CONT type is always aggregated from the
multiple services mapped to it on the ONT.
Each ONT Ethernet port receives four upstream queues (or GEM ports) at service
instantiation where the outer P-bit of the tag action maps to one of the four GEM ports,
regardless of the VLAN. If two services are assigned to a single class of service, they will
share the GEM port. A second service on a different ONT Ethernet port will be assigned a
different GEM port, but will share the T-CONT type with service separation performed by
the ONT GEM port shaper. The mapping between the GEM port and the T-CONT type is
fixed for all services on the OLT and is defined by the E7 PON Class of Service
configuration attribute.

Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
VLAN ID /
P-Bit
Data-1
AF1
cos-2
10 Mb/s
1/1 Mb/s
GEM 3
30 / 3
Data-2
BE
cos-1
50 Mb/s
0/5 Mb/s
GEM 1
32 / 0
Data-3
BE
cos-1
10 Mb/s
0/1 Mb/s
GEM 1
34 / 0
In Standard QoS Model T-CONT type (CoS-1):

Upstream BWP = Data-2 + Data-3 BWPs = 6 Mb/s

Downstream BWP = 60 Mb/s

Either service can use all of the bandwidth, if there is no contention for it.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
432
Traffic marked with a P-bit value is forced into a pre-determined upstream traffic class
and bandwidth profile type.
The fixed PON CoS service model does not support the following:



P-bit preservation or DSCP-to-P-bit mapping

Ability to rate limit all P-bit flows within a single VLAN
This topic shows the overall process for provisioning legacy differentiated service model on
the E7 GPON and ONT Ethernet port.
This model assigns four TCONTs, each representing an aggregated class of service for an
ONT (BE, AF1, AF2, EF). The four TCONTs are pre-assigned a class of service and
services are required to have bandwidth profiles that match the class of service. Also,
bandwidth assigned to the TCONTs is always aggregated from the multiple services mapped
to it on the ONT.
Each ONT Ethernet port receives four GEM ports at service instantiation where the outer
P-bit of the tag action maps to one of the four GEM ports, regardless of the VLAN. If two
services are assigned to a single class of service, they will share the GEM port. A second
service on a different ONT Ethernet port will be assigned a different GEM port, but will
share the TCONT with service separation performed by the ONT upstream GEM shaper.
The mapping between the GEM port and the TCONT is fixed for all services on the OLT
and is defined by the E7 PON Class of Service configuration attribute. See Creating a PON
Class of Service (on page 122) to change the default mapping between GPON CoS to P-bits
(cos-1 through cos-4).
Configuration considerations
Any service provisioned with a software version earlier than R2.2 will operate the same
after upgrading to R2.2 or later.
Traffic marked with a P-bit value is forced into a pre-determined upstream traffic class
and bandwidth profile type.
The fixed PON CoS service model does not support the following:




P-bit preservation or DSCP-to-P-bit mapping

Being able to rate limit all P-bit flows within a single VLAN
Note: See GPON QoS (on page 117).
Step 1: Configure network uplinks




Configure Ethernet Interfaces
Configure Ethernet Ports
Create Service VLANs
Make Interfaces VLAN Members
See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
433
Step 2: Create system profiles
Create an Ethernet Bandwidth Profile:

Create a bandwidth profile for best effort (DATA-BE).

E7 > Profiles > Service > Ethernet Bandwidth >
Profiles > Create
See Creating an Ethernet Bandwidth Profile (on page
167).
Create and apply a PON Upstream CoS
Profile to a GE ONT:

Create a PON upstream CoS profile for best effort with
explicit upstream shaping (BE_100).

E7 > Profiles > CoS > PON Upstream > Create
See Creating a PON Upstream Class of Service Profile
(on page 124).

Map the PON upstream CoS profile to user-1 for a GE
ONT. (ID 1)

ONTs > Provisioned ONTs > PON Upstream CoS >
Create
See Adding PON Upstream CoS Profiles to a GE ONT
(on page 256).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
434
Create Rules to Classify Traffic:
a) Create a Match List
Typically only untagged traffic is present on the ONT Ethernet
port, so you can use the system default match list "alluntagged," defined as shown, to match all untagged traffic.
If a residential gateway (RG) is installed in a subscribers
house, the RG classifies traffic into VLANs. Then for each
service type, create a match list that contains a tagged rule,
matching the service VLAN. See Creating a Service Match
List and Rules (on page 127).

Create a match list (ETYPE_IP)
add untagged rule match ethertype ipv4
add untagged rule match ethertype arp

E7 > Profiles > Service > Tagging > Match Lists >
Profiles > Create
b) Create a 2nd Match List

Create a match list (ETYPE_PPPOE)
add untagged rule match ethertype pppoe
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
435
c) Create a Service Tag Action
Applies the specified service-tag action to the matched traffic.
See Creating Service-Tag Actions (on page 131).
Specify the added VLAN tag in the Service Tag Action (Outer
Tag = 20) so you can apply the same VLAN tagging for all
data service provisioning that uses the tag action object.
When you indicate Specify P-Bit for the P-Bit Source, enter
the P-bit value that marks the traffic for the best effort
forwarding class.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
d) Create a 2nd Service Tag Action
Applies the specified service-tag action to the matched traffic.
Specify the added VLAN tag in the Service Tag Action (Outer
Tag = 21) so you can apply the same VLAN tagging for all
data service provisioning that uses the tag action object.
When you indicate Specify P-Bit for the P-Bit Source, enter
the P-bit value that marks the traffic for the best effort
forwarding class.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
Step 3: Configure a PON
Enable the E7 GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.
See Configuring an E7 GPON Port (on page 232).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
436
Configure an ONT.
See procedures in Configuring an ONT (on page 244).
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT.
Step 4: Configure subscriber services
Add the Data Service to an Ethernet Port.
Create two data services that map to the same VLAN (101) on 1/g1, where the flexible assignments of upstream rate shaping is
configured. See Creating Data Service on an ONT Ethernet Port.
Multiple services, same traffic class (CoS), independent BW
Service Model
This model is intended for isolating the bandwidth for multiple services on an ONT
Ethernet port that share the same traffic class. The same service class per ONT port can
select different GEM ports and a different T-CONT type.


PON US profile is created and mapped to user-1 at the ONT
PON CoS of user-1 is selected when adding the Ethernet service
Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
VLAN ID /
P-Bit
Data-1
AF1
cos-2
10 Mb/s
1/1 Mb/s
GEM 3
30 / 3
Data-2
BE
cos-1
50 Mb/s
0/5 Mb/s
GEM 2
32 / 0
Data-3
BE
user-1
10 Mb/s
0/1 Mb/s
GEM 1
34 / 0
This topic shows the overall process for provisioning enhanced multi-CoS differentiated
services on the E7 GPON and ONT Ethernet port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
437
This model is intended for more than one service being configured on the same VLAN. The
PON upstream CoS can optionally be provisioned, otherwise, the behavior defaults to the
legacy model if not provisioned, where it is backwards compatible and upgrade compatible.
Any service provisioned with software version earlier than R2.2 will operate the same after
upgrading to R2.2 or later.
Configuration considerations
More than one service is configured on a VLAN.
Any service provisioned with a software version earlier than R2.2 will operate the same
after upgrading to R2.2 or later.
The fixed CoS service model does not support the following:




P-bit preservation or DSCP-to-P-bit mapping

Being able to rate limit all P-bit flows within a single VLAN
See GPON QoS (on page 117).
Step 1: Configure network uplinks




Configure Ethernet Interfaces
Configure Ethernet Ports
Create Service VLANs
Make Interfaces VLAN Members
See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
Step 2: Create system profiles
Create an Ethernet Bandwidth Profile:

Create a bandwidth profile for best effort (DATA-BE).

E7 > Profiles > Service > Ethernet Bandwidth >
Profiles > Create
See Creating an Ethernet Bandwidth Profile (on page
167).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
438
Create and apply a PON Upstream CoS
Profile to a GE ONT:

Create a PON upstream CoS profile for best effort with
explicit upstream shaping (BE_100).

E7 > Profiles > CoS > PON Upstream > Create
See Creating a PON Upstream Class of Service Profile
(on page 124).

Map the PON upstream CoS profile to user-1 for a GE
ONT. (ID 1)

ONTs > Provisioned ONTs > PON Upstream CoS >
Create
See Adding PON Upstream CoS Profiles to a GE ONT
(on page 256).
Create Rules to Classify Traffic:
a) Create a Match List
Typically only untagged traffic is present on the ONT Ethernet
port, so you can use the system default match list "alluntagged," defined as shown, to match all untagged traffic.
If a residential gateway (RG) is installed in a subscribers
house, the RG classifies traffic into VLANs. Then for each
service type, create a match list that contains a tagged rule,
matching the service VLAN. See Creating a Service Match
List and Rules (on page 127).

Create a match list (ETYPE_IP)
add untagged rule match ethertype ipv4
add untagged rule match ethertype arp

E7 > Profiles > Service > Tagging > Match Lists >
Profiles > Create
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
439
b) Create a 2nd Match List

Create a match list (ETYPE_PPPOE)
add untagged rule match ethertype pppoe
c) Create a Service Tag Action
Applies the specified service-tag action to the matched traffic.
See Creating Service-Tag Actions (on page 131).
Specify the added VLAN tag in the Service Tag Action (Outer
Tag = 20) so you can apply the same VLAN tagging for all
data service provisioning that uses the tag action object.
When you indicate Specify P-Bit for the P-Bit Source, enter
the P-bit value that marks the traffic for the best effort
forwarding class.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
d) Create a 2nd Service Tag Action
Applies the specified service-tag action to the matched traffic.
Specify the added VLAN tag in the Service Tag Action (Outer
Tag = 21) so you can apply the same VLAN tagging for all
data service provisioning that uses the tag action object.
When you indicate Specify P-Bit for the P-Bit Source, enter
the P-bit value that marks the traffic for the best effort
forwarding class.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
440
Step 3: Configure a PON
Enable the E7 GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.
See Configuring an E7 GPON Port (on page 232).
Configure an ONT.
See procedures in Configuring an ONT (on page 244).
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT.
Step 4: Configure subscriber services
Add the Data Service to an Ethernet Port.
Create two data services that map to the same VLAN (101) on 1/g1, where the flexible assignments of upstream rate shaping is
configured. See Creating Data Service on an ONT Ethernet Port.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
441
Multiple services, same traffic class (CoS), different P-Bits Service
Model
This model is intended for isolating multiple services on an ONT Ethernet port that share
the same traffic class, where a service explicitly defines the outer VLAN, P-bit, and the PON
upstream traffic class. The service can have any bandwidth profile, or share a single
bandwidth profile with other services.
The specified P-Bit is not required to match one of the values defined for the CoS. The P-bit
0 (BE) service uses Software Egress Shaping Path when BE Rate < MAX Supported
throughput.




PON US profile is created and mapped to user-1 at the ONT
Service match list has tagged rule for VLAN 34, P-bit 3
Service tag action to use P-bit 3
PON CoS of user-1 is selected when adding Ethernet service
Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
VLAN ID /
P-Bit
Data-1
AF1
cos-2
10 Mb/s
1/1 Mb/s
GEM 3
30 / 3
Data-2
BE
cos-1
50 Mb/s
0/5 Mb/s
GEM 2
32 / 0
Data-3
BE
user-1
10 Mb/s
0/1 Mb/s
GEM 1
34 / 3
This topic shows the overall process for provisioning single-rate single-CoS model services
on the E7 GPON and ONT Ethernet port.
This single-rate single-CoS model is intended for a service that explicitly defines:



Outer VLAN
P-bit
PON upstream traffic class
This model is intended for isolating multiple services on an ONT Ethernet port that share
the same traffic class. By using a single GEM port since there is only a single traffic class, the
service is isolated from other services on the ONT Ethernet port, allowing the service to
have any bandwidth profile, or share a single bandwidth profile with other services.
See GPON QoS (on page 117).
Configuration considerations




Single service per VLAN.
Isolates multiple services on a User-to-Network Interface (UNI) even when they share
the same traffic class.
Single VLAN rate limit.
Up to 28 independent services per ONU, all of which are isolated with rate limiters.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
442
Step 1: Configure network uplinks




Configure Ethernet Interfaces
Configure Ethernet Ports
Create Service VLANs
Make Interfaces VLAN Members
See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
Step 2: Create system profiles
Create an Ethernet Bandwidth Profile:

Create a bandwidth profile for best effort (DATA-BE).

E7 > Profiles > Service > Ethernet Bandwidth >
Profiles > Create
See Creating an Ethernet Bandwidth Profile (on page
167).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
443
Create and apply a PON Upstream CoS
Profile to a GE ONT:
a) Create a PON Upstream CoS Profile

Create a PON upstream CoS profile for best effort with
explicit upstream shaping (BE_100).

E7 > Profiles > CoS > PON Upstream > Create
See Creating a PON Upstream Class of Service Profile
(on page 124).
b) Create another PON Upstream CoS Profile

Create a PON upstream CoS profile for best effort with
aggregated upstream bandwidth (BE_100).
c) Map a PON Upstream CoS Profile to user-1 (ID 1)

ONTs > Provisioned ONTs > PON Upstream CoS >
Create
See Adding PON Upstream CoS Profiles to a GE ONT
(on page 256).
d) Map a PON Upstream CoS Profile to user-2 (ID 2)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
444
Create Rules to Classify Traffic:
a) Create a Match List
Typically only untagged traffic is present on the ONT Ethernet
port, so you can use the system default match list "alluntagged," defined as shown, to match all untagged traffic.
c) Create a Service Tag Action

Applies the specified service-tag action to the matched
traffic. See Creating Service-Tag Actions (on page 131).

Single tags all untagged traffic on the ONT Ethernet port.
Specify the added VLAN tag in the Service provisioning.

When you indicate Specify P-Bit for the P-Bit Source,
enter the P-bit value that marks the traffic for the best
effort forwarding class.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
Step 3: Configure a PON
Enable the E7 GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.
See Configuring an E7 GPON Port (on page 232).
Configure an ONT.
See procedures in Configuring an ONT (on page 244).
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
445
Step 4: Configure subscriber services
Add the Data Service to an Ethernet Port.
Create two data services that map to the same VLAN (101) on 1/g1, where the flexible assignments of upstream rate shaping is
configured. See Creating Data Service on an ONT Ethernet Port.
Multiple services, same traffic class (CoS), independent BW,
prioritized scheduling on the PON Service Model
This model is intended for more than one service of the same class where one service (AF2)
should have a higher priority than another (AF1), and they are configured as isolated services.
The same service class per ONT port can select different GEM ports, a different T-CONT
type, and priority of flow.




PON US profile is created with priority 3 and mapped to user-1 at the ONT
Service match list has tagged rule for VLAN 34, P-bit 4
Service tag action to use P-bit 4
PON CoS of user-1 is selected when adding Ethernet service
Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
PON Cos
Priority
VLAN ID /
P-Bit
Data-1
Data-3
AF1
cos-2
1000 Mb/s
100/100 Mb/s
GEM 2
2
30 / 3
AF2
user-1
1000 Mb/s
100/100 Mb/s
GEM 1
3
34 / 4
The recommended priority value of ‘3’ will ensure AF2 is scheduled before AF1.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
446
This topic shows the overall process for provisioning single-rate multi-CoS model service on
the E7 GPON and ONT Ethernet port.
This single-rate multi-CoS model is intended for a service that requires:
QoS within a VLAN
P-bit preservation, or DSCP assignment for a VLAN
Explicitly defined PON upstream traffic class to insure service separation



Typically, this model is used within a TLAN or business service. The VLAN service can have
any type (best-effort, assured, expedited) of bandwidth profile.
Typically, this model is used within a TLAN or business service. There is a single rate for the
entire VLAN where it can have any type (best-effort, assured, expedited) of bandwidth
profile assigned, and should be assigned a user-defined PON upstream CoS to ensure service
separation.
See GPON QoS (on page 117).
Step 1: Configure network uplinks




Configure Ethernet Interfaces
Configure Ethernet Ports
Create Service VLANs
Make Interfaces VLAN Members
See procedures in Configuring the Network Uplink(s) for GPON
Service (on page 66).
Step 2: Create system profiles
Create an Ethernet Bandwidth Profile:

Create a bandwidth profile for best effort (DATA-BE).

E7 > Profiles > Service > Ethernet Bandwidth >
Profiles > Create
See Creating an Ethernet Bandwidth Profile (on page
167).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
447
Create and apply a PON Upstream CoS
Profile to a GE ONT:
a) Create a PON US CoS Profile

Create a PON upstream CoS profile for best effort with
explicit upstream shaping (BE_100).

E7 > Profiles > CoS > PON Upstream > Create
See Creating a PON Upstream Class of Service Profile
(on page 124).
b) Map the Profile to the ONT

Map the PON upstream CoS profile to user-1 for a GE
ONT. (ID 1)

ONTs > Provisioned ONTs > PON Upstream CoS >
Create
See Adding PON Upstream CoS Profiles to a GE ONT
(on page 256).
Create Rules to Classify Traffic:
a) Create a Match List

Create a match list (VLAN_10px)

Add a tagged rule to match VLAN ID = 10

E7 > Profiles > Service > Tagging > Match Lists >
Profiles > Create
See Creating a Service Match List and Rules (on page
127).
b) Create a Service Tag Action
Applies the specified service-tag action to the matched traffic.

Single tags all untagged traffic on the ONT Ethernet port.

Specify the added VLAN tag in the Service provisioning.

Indicate Specify a layer-3 priority to use a DSCP table
or an IP Precedence table to map to a P-bit value.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
See Creating Service-Tag Actions (on page 131).
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
448
c) Create a 2nd Service Tag Action

Changes the VLAN tag for traffic that matches the match
list criteria (VLAN = 10).

Specify the change VLAN tag value in the Service
provisioning.

Indicate Specify P-Bit for the P-Bit Source, and then
select copy to preserve the outer tag P-bit value that was
set in a service provider-supplied RG.

E7 > Profiles > Service > Tagging > Tag Actions >
Profiles > Create
Step 3: Configure a PON
Enable the E7 GPON Port.
Split Horizon should ONLY be disabled when setting up TLAN
service between multiple GPON ports on the same E7 card.
See Configuring an E7 GPON Port (on page 232).
Configure an ONT.
See procedures in Configuring an ONT (on page 244).
Typically, the provisioning of an ONT is done in advance of
installation and discovery of the physical ONT.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
449
Step 4: Configure subscriber services
Add the Data Service to an Ethernet Port.
Create a single service per VLAN with a P-bit model that requires QoS. Each service will get four GEM ports and can map to flexible
assignments of upstream rate shaping. See Creating Data Service on an ONT Ethernet Port.
Single service with prioritization of flows within the service
This model is intended for a service that requires QoS within a VLAN and explicitly defines
the PON upstream traffic class. This model allows a single service to be defined with P-bit
preservation, while maintaining quality of service within the VLAN. Typically, this model is
used within a TLAN or business service. There is a single rate for the entire VLAN service
that can have any type of bandwidth profile (best-effort, assured, expedited). Also, a userdefined PON upstream CoS should be assigned to ensure service separation.

Service tag action to preserve the P-bit value set in service provider supplied RGs:

Copies the subscriber-side Q-Tag P-Bits to a single C-tag or S-Tag, or to the inner CTag of a double-tagged Service.

For the outer tag P-bit, you can specify the value of "copy."

For the inner tag, you can specify the value of "preserve."
Service
Name
Traffic
Class
T-CONT Type
(PON CoS)
Downstream
Bandwidth
(PIR)
Upstream
Bandwidth
(CIR/PIR)
GEM Port
video-1
AF
cos-3
50 Mb/s
1/3 Mb/s
Traffic priority
queued prior to
mapping to a
GEM port -- for
example,
GEM 3.
Flow
Type
VLAN ID /
P-Bit
DHCP
30 / 0
VoD C&C
32 / 2
VoD
32 / 4
MC
32 / 5
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
450
Quick Start E7 GPON RSG Use Cases
E7 GPON RSG Smart Activate Turn-up
This section provides quick procedures to turn up a GPON 836GE RSG using the Smart
Activate application and launch Smart Activate following turn-up.
Note: The following procedures do not apply to AE ONTs/RSGs.
Turning Up a GPON RSG Using Smart Activate
Calix GPON 836GE RSGs ship with a manufacturing (bootstrap) image only. The
manufacturing image provides the following functionality:


Smart Activate application
Auto-detection of WAN transport
When a GPON RSG is turned up, it ranges, performs a firmware check and then downloads
the operational image. The operational image contains the Home Gateway elements of the
RSG firmware.
Follow the procedures below to turn up an GPON RSG with Smart Activate via an Ethernet
cable or WiFi Accesss Point.
To turn up a 836GE out of the box using a PC and Ethernet cable
Note: This procedure assumes that the ONT/RSG fiber and power cables are disconnected.
1. Configure your PC for a static IP address. See Configuring Your Local PC for Web
Activate for details.
2. Connect an Ethernet cable between the PC RJ-45 connector and RSG LAN port 1.
3. Power on the 836GE RSG.
4. From your PC browser enter IP address 192.168.100.100.
5. At the Windows Security screen enter the following credentials:

User Name = admin

Password = fiber1ttx
6. From the Smart Activate window, enter the Registration ID (alpha-numeric) and then
click Submit.
7. Attach a WAN facing fiber to the RSG.
The RSG ranges, performs a firmware check, downloads the operational image, and resets.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
451
To turn up a GPON 836GE out of the box using a mini WiFi Access Point (dongle)
and iOS application
This procedure assumes the following conditions:





User supplied mobile device: iPhone, iPad,or iTouch with iOS 5.0 +
Smart Activate has been downloaded to the mobile device
(https://itunes.apple.com/us/app/smart-activate/id634979663?mt=8)
The WiFi dongle is powered on and configured with WPA, display SSID
The mobile device is paired up with the WiFi dongle
The RSG fiber and power cables are disconnected
Turn up an RSG using a WiFi dongle as follows:
1. Power on the 836GE RSG.
2. After the RSG boots up, connect an Ethernet CAT 5 cable between RSG LAN port 1
and the WiFi dongle WAN port.
3. Launch Smart Activate from your mobile device.
4. From the Smart Activate application, enter the Registration ID (alpha-numeric) and then
touch the Activate arrow.
5. Attach a WAN facing fiber to the RSG.
The RSG ranges, performs a firmware check, downloads the operational image, and then
resets.
Launching Smart Activate for a GPON RSG
Follow the procedures below to launch the Smart Activate application via an Ethernet cable
or WiFi Access Point after turning up a GPON 836GE RSG.
To launch Smart Activate using a PC and Ethernet cable
Note: Verify that there is only one network adapter on the PC.
1. Disconnect the fiber from the 836GE RSG.
2. Power cycle the RSG.
3. After the RSG boots up, connect an Ethernet CAT 5 cable between the PC RJ-45
connector and any RSG LAN port that is a member of a Residential Gateway (RG)
interface.
The PC receives an IP address via DHCP from the RG.
4. To log in to the RSG Embedded Web Interface (EWI), open your browser and enter the
IP address and user/password specified on the RSG label.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
452
5. From the RSG EWI, enter http://192.168.1.1/smartActivate.html.
You are redirected to http://192.168.100.100:2080.
6. Enter the following default credentials:

User Name = admin

Password = fiber1ttx
The Smart Activate screen displays.
To launch Smart Activate using a mini WiFi Access Point (dongle) and iOS
application
Note: Firmware upgrades are not supported with this application.
This procedure assumes the following conditions:




User supplied mobile device: iPhone, iPad,or iTouch with iOS 5.0 +
Smart Activate has been downloaded to the mobile device
(https://itunes.apple.com/us/app/smart-activate/id634979663?mt=8)
The WiFi dongle is powered on and configured with WPA, display SSID
The mobile device is paired up with the WiFi dongle
Launch the Smart Activate application using a WiFi dongle as follows:
1. Disconnect the fiber from the 836GE RSG.
2. Power cycle the RSG.
3. After the RSG boots up, connect an Ethernet CAT 5 cable between RSG LAN port 1
and the WiFi dongle WAN port.
4. Launch Smart Activate from your mobile device.
The Smart Activate screen displays.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
453
Home Gateway GPON RSG Services Turn-up
About Service Tag Actions for RG-based Services
The 836GE RSG operates with two logical partitions: a standard GPON ONT and a
Residential Gateway (or Home Gateway).
The logical components within the RSG are functionally similar to a standard GPON ONT
with a subtended 3rd party residential gateway (RG): The ONT receives tagged traffic from
the downstream RG and sends it upstream single-tagged where the OLT may or may not add
a second tag.
For RG-based services (not HB or FB), only Change Tag and Add and Change Tag VLAN
service tags are supported.
Note: Service tag actions for RSGs configured in Native and External mode are defined in
the same manner.
Single VLAN tag example (IEEE 802.1Q)
In the example below, the service tag action matches on outer or service provider tag (S-Tag)
10 and changes the tag to S-Tag 2000 as it is sent upstream from the RSG. This is
representative of the RG sending Ethernet frames upstream with an S-Tag of 10, and the
ONT matching on S-Tag 10 and then changing the S-Tag to 2000.
SE_Training_1>show svc-match-list "@GPON_RG_HSI"
service match-list "@GPON_RG_HSI":
Untagged Rules:
Rule Source MAC
---- -------------------------------------------<no rules>
Tagged Rules:
Rule Outer Tag
---- -------------------------1
VLAN 10
SE_Training_1>show svc-tag-action "@GPON_RG_HSI"
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
454
Name
Action
------------------------------- ---------------------------------------------@GPON_RG_HSI
change-tag
match: service match-list
"@GPON_RG_HSI"
outer: 2000, p-bit: 0
Double VLAN tag example (IEEE 802.1ad)
In the example below, the service tag action matches on S-Tag 10, changes the tag to an
inner or customer tag (C-Tag) to uniquely identify the subscriber, and adds an S-Tag of 2100.
This is representative of the RG sending Ethernet frames upstream with an S-Tag of 10, and
the ONT matching on S-Tag 10, changing the tag to a unique C-Tag, and then sending the
frame upstream where the OLT adds an S-Tag.
SE_Training_1>show svc-match-list "@GPON_RG_HSI"
service match-list "@GPON_RG_HSI":
Untagged Rules:
Rule Source MAC
---- -------------------------------------------<no rules>
Tagged Rules:
Rule Outer Tag
---- -------------------------1
VLAN 10
SE_Training_1>show svc-tag-action "@GPON_RG_HSI_DT"
Name
Action
------------------------------- ---------------------------------------------@GPON_RG_HSI_DT
add-and-change
match: service match-list
"@GPON_RG_HSI"
outer: 2100, p-bit: 0
inner: from service, p-bit: same-asouter
Configuring a GPON RSG in Native Mode Using Default RG
Values
The procedures in this topic provide examples for configuring an 836GE RSG in Native
Mode for the following services using default RG values:


RG High Speed Internet (HSI) data, Full Bridge (FB) video (MVR), and SIP voice
RG HSI data and RG MVR video
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
455
These procedures assume the following conditions:



CMS is running at R12.1 or higher
E7 is running at R2.2 or higher
Network uplinks are configured for GPON services
Note: The following examples use specific profile names, however you may substitute names
as needed.
To configure a GPON RSG in Native Mode for RG HSI, FB video, and SIP voice using default RG
values
1. To create an ONT Template defining key management aspects of the RSG and logical
assignments of the physical GE ports, select CMS > Profile > E7/ONT > Templates
> ONT > Create and then enter the following parameters:

ID = value between 1-20

Name = RG_3FB

Management Mode = native

WAN Protocol = DHCP

GE 1 = RG 1

GE 2-GE 4 = FB 1

(For all other settings, accept defaults)
Note: Both RG and FB interfaces support a DSCP/IP-precedence to P-bit mapping on
a per-VLAN basis. The LAN side clients are responsible for setting DSCP/IPprecedence.
See Creating an ONT Template (on page 191) for details.
2. Build a match list for HSI services as follows:
a. Select CMS > Profile > E7/ONT > Service > Tagging > Match Lists > Create
and then enter the following parameters:

Name = @GPON_RG_HSI

(For all other settings, accept defaults)
b. In the Match List table select the match list created in step 2a, select Create >
Tagged Match Rule, and then enter the following parameters:

S-VLAN (Outer Tag) = 10

(For all other settings, accept defaults)
See Creating a Service Match List and Rules (on page 127) for details.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
456
3. To create a service tag action for HSI services, select CMS > Profile > E7/ONT >
Service > Tagging > Tag Action > Create and then enter the following parameters:
To learn how service tag actions work with the RG, see About Service Tag Actions for RGbased Services (on page 453).

Name = @GPON_RG_HSI

Action = Change Tag

Match List = @GPON_RG_HSI (created in step 2a)

S-VLAN (Outer Tag) = 2000

Outer P-Bit = 0

For AE ONT = N

(For all other settings, accept defaults)
This service tag action matches on S-Tag 10 and changes the tag to 2000 as it is sent
upstream from the RSG.
See Creating Service-Tag Actions (on page 131) for details.
4. Build a multicast map for Full Bridge (FB) video services as follows:
Note: Multicast maps are not supported for RG-based video services.
a. Select CMS > Profile > E7/ONT > Service > Multicast > Multicast Maps >
Create > Multicast Maps and then enter the following parameters:

Name = @Video

(For all other settings, accept defaults)
b. In the list of multicast maps select @Video, click Create > Multicast Address Range
and then enter the following parameters:

Start IP Address: 224.0.0.1

End IP Address: 239.255.255.255
The multicast map limits ingress IGMP reports with a specific Destination MAC
Address that a STB can send.
See Creating a Multicast Address Map and Ranges (on page 181) for details.
5. Build an MVR profile for video services as follows:
a. Select CMS > Profile > E7/ONT > Service > Multicast > MVR > Create and
then enter the following parameters:

Name = @Video

Sync to E7 = Y

Local VLAN = N
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
457
b. In the list of MVR profiles select @Video, click Create > MVR VLAN and then
enter the following parameters:

Address Range1 Start = 224.0.0.0

Address Range1 End = 239.255.255.255
See Creating an MVR Profile and MVR VLAN Addresses (on page 178) for details.
6. To create a multicast profile for video services, select CMS > Profile > E7/ONT >
Service > Multicast > Multicast > Create and then enter the following parameters:

Name = @Video

Max Streams = 16

Multicast Maps = @Video

MVR Profile = @Video

(For all other settings, accept defaults)
See Creating a Multicast Profile for details.
7. To create a service tag action for FB video services, select CMS > Profile > E7/ONT
> Service > Tagging > Tag Action > Create and then enter the following parameters:

Name = @FB_Video

Match List = 1 (all-untagged)

S-VLAN (Outer Tag) = 104

Outer P-Bit = 4

(For all other settings, accept defaults)
Note: Because only video services are supported on the FB interface, it is not necessary
to specify the OUI of the STB, and the all-untagged match list applies.
See Creating Service-Tag Actions (on page 131) for details.
8. To create Ethernet bandwidth profiles for RG HSI and FB video services, select CMS >
Profile > E7/ONT > Service > Ethernet Bandwidth > Create and then enter the
following parameters:
RG HSI:

Name = @GPON_RG_HSI_10x10

Peak Rate for Upstream = 10m

Peak Rate for Downstream = 10m

Committed Rate for Downstream = 10m

For AE ONT = N

(For all other settings, accept defaults)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
458
FB video:

Name = @GPON_Video

Committed Rate for Upstream = 25m

Peak Rate for Upstream = 100m

Peak Rate for Downstream = 100m

Committed Rate for Downstream = 100m

For AE ONT = N

(For all other settings, accept defaults)
See Creating an Ethernet Bandwidth Profile for GPON Services (on page 167) for details.
9. Verify that the WAN facing fiber is attached to the 836GE RSG.
10. To verify that the RSG has been discovered in the E7, navigate to the E7, double-click
ONTS, and then click Discovered ONTs.
11. To provision the RSG, select the 836GE RSG in the Discovered ONTs table, click
Action > Link to New Provisioning, and then enter the following parameters:

ONT Profile = 836GE

Template = RG_3FB (or the name of the ONT template that you created in step 1)

(For all other settings, accept defaults)
12. To provision Home Gateway services for HSI, click Provisioned ONTs > Services >
Create > Gateway Service and then select the following parameters:

Subscriber Port = RG-1

Service Name = Gateway Service: 1

BW Profile = @GPON_RG_HSI_10x10

Svc Tag Action = @GPON_RG_HSI

(For all other settings, accept defaults)
13. To provision FB video services, click Provisioned ONTs > Services > Create >
Video Service and then select the following parameters:

Subscriber Port = FB-1

Service Name = Video: 1

BW Profile = @GPON_Video

Multicast Profile = @Video

Svc Tag Action = @FB_Video

(For all other settings, accept defaults)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
459
14. To provision SIP voice service, click Provisioned ONTs > Services > Create > SIP
Service and then enter the following parameters:
Note: This step assumes that you have created a SIP profile and service tag action for
SIP voice service. See Creating a SIP Remote Configuration Profile (on page 213) and Creating
Service-Tag Actions (on page 131) for instructions.

Subscriber Port = Voice-1

SIP Profile = an existing SIP profile

User Name = user name for registration with SIP server (for example, a phone
number)

URI = type the Universal Resource Indicator

Password = registration password

Service Tag Action = an existing service tag action

(For all other settings, accept defaults)
To configure a GPON RSG in Native Mode for RG HSI and RG MVR using default RG values
1. To create an ONT Template defining key management aspects of the RSG and logical
assignments of the physical GE ports, select CMS > Profile > E7/ONT > Templates
> ONT > Create and then enter the following parameters:

ID = value between 1-20

Name = RG_HSI_MVR

Management Mode = native

WAN Protocol = DHCP

GE 1-GE 4 = RG 1

(For all other settings, accept defaults)
Note: Both RG and FB interfaces support a DSCP/IP-precedence to P-bit mapping on
a per-VLAN basis. The LAN side clients are responsible for setting DSCP/IPprecedence.
2. Build a match list for HSI services as follows:
a. Select CMS > Profile > E7/ONT > Service > Tagging > Match Lists > Create
and then enter the following parameters:

Name = @GPON_RG_HSI

(For all other settings, accept defaults)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
460
b. In the Match List table select the match list created in step 2a, select Create >
Tagged Match Rule, and then enter the following parameters:

S-VLAN (Outer Tag) = 10

(For all other settings, accept defaults)
See Creating a Service Match List and Rules (on page 127) for details.
3. To create a service tag action for HSI services, select CMS > Profile > E7/ONT >
Service > Tagging > Tag Action > Create and then enter the following parameters:
To learn how service tag actions work with the RG, see About Service Tag Actions for RGbased Services (on page 453).

Name = @GPON_RG_HSI

Action = Change Tag

Match List = @GPON_RG_HSI (created in step 2a)

S-VLAN (Outer Tag) = 2000

Outer P-Bit = 0

For AE ONT = N

(For all other settings, accept defaults)
This service tag action matches on S-Tag 10 and changes the tag to 2000 as it is sent
upstream from the RSG.
See Creating Service-Tag Actions (on page 131) for details.
4. Build a match list for RG MVR video services as follows:
a. Select CMS > Profile > E7/ONT > Service > Tagging > Match Lists > Create
and then enter the following parameters:

Name = @GPON_RG_Video

(For all other settings, accept defaults)
b. In the Match List table select the match list created in step 2a, select Create >
Tagged Match Rule, and then enter the following parameters:

S-VLAN (Outer Tag) = 104

(For all other settings, accept defaults)
See Creating a Service Match List and Rules (on page 127) for details.
5. To create a service tag action for RG MVR video services, select CMS > Profile >
E7/ONT > Service > Tagging > Tag Action > Create and then enter the following
parameters:

Name = GPON_RG_Video

Action = Change Tag

Match List = @GPON_RG_Video (created in step 4a)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
461

S-VLAN (Outer Tag) = 104

Outer P-Bit Source = Specify P-Bit

Outer P-Bit = 4

For AE ONT = N

(For all other settings, accept defaults)
This service tag action matches on S-Tag 104 and performs a change-tag action to 104 as
it is sent upstream from the RSG.
See Creating Service-Tag Actions (on page 131) for details.
6. Build an MVR profile for video services as follows:
a. Select CMS > Profile > E7/ONT > Service > Multicast > MVR > Create and
then enter the following parameters:

Name = @Video

Sync to E7 = Y

Local VLAN = N
b. In the list of MVR profiles select @Video, click Create > MVR VLAN and then
enter the following parameters:

Address Range1 Start = 224.0.0.0

Address Range1 End = 239.255.255.255
See Creating an MVR Profile and MVR VLAN Addresses (on page 178) for details.
7. To create a multicast profile for video services, select CMS > Profile > E7/ONT >
Service > Multicast > Multicast > Create and then enter the following parameters:

Name = @Video

Max Streams = 16

Multicast Maps = @Video

MVR Profile = @Video

(For all other settings, accept defaults)
See Creating a Multicast Profile [GPON] (on page 177) for details.
8. To create Ethernet bandwidth profiles for RG HSI and MVR video services, select CMS
> Profile > E7/ONT > Service > Ethernet Bandwidth > Create and then enter the
following parameters:
RG HSI:

Name = @GPON_RG_HSI_10x10

Peak Rate for Upstream = 10m

Peak Rate for Downstream = 10m
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
462

Committed Rate for Downstream = 10m

For AE ONT = N

(For all other settings, accept defaults)
RG MVR:

Name = @GPON_Video

Committed Rate for Upstream = 25m

Peak Rate for Upstream = 100m

Peak Rate for Downstream = 100m

Committed Rate for Downstream = 100m

For AE ONT = N

(For all other settings, accept defaults)
See Creating an Ethernet Bandwidth Profile for GPON Services (on page 167) for details.
9. Verify that the WAN facing fiber is attached to the 836GE RSG.
10. To verify that the RSG has been discovered in the E7, navigate to the E7, double-click
ONTS, and then click Discovered ONTs.
11. To provision the RSG, select the 836GE RSG in the Discovered ONTs table, click
Action > Link to New Provisioning, and then enter the following parameters:

ONT Profile = 836GE

Template = RG_HSI_MVR (or the name of the ONT template that you created in
step 1)

(For all other settings, accept defaults)
12. To provision Home Gateway services for HSI, click Provisioned ONTs > Services >
Create > Gateway Service and then select the following parameters:

Subscriber Port = RG-1

Service Name = Gateway Service: 1

BW Profile = @GPON_RG_HSI_10x10

Svc Tag Action = @GPON_RG_HSI

(For all other settings, accept defaults)
13. To provision RG MMR video services, click Provisioned ONTs > Services > Create
> Gateway Service and then select the following parameters:

Subscriber Port = RG-1

Service Name = Gateway Service: 1

BW Profile = @GPON_Video

Multicast Profile = @Video
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
463

Svc Tag Action = @GPON_RG_Video

(For all other settings, accept defaults)
Configuring a GPON RSG in Native Mode Using RG Values
Defined via Consumer Connect
The following procedure provides an example for configuring an 836GE RSG in Native
Mode for RG HSI data, Full Bridge video (MVR), and SIP voice services using RG values
defined in Consumer Connect.
This procedure assumes the following conditions:






CMS is running at R12.1 or higher
E7 is running at R2.2 or higher
Network uplinks are configured for GPON services
Service VLANs are configured for HSI and video
A Consumer Connect (Calix hosted cloud-based SaaS) server is configured
You have defined a configuration profile from Consumer Connect with the desired RG
objects, parameters, and attributes (refer to the Consumer Connect Administrator User Guide
for instructions)
Note: The following examples uses specific profile names, however you may substitute
names as needed.
To configure a GPON RSG in Native Mode using RG values defined via Consumer
Connect (in-band)
1. To configure the RSG to access the path to the Consumer Connect server, do the
following:
a. Select CMS > Profile > E7/ONT > RG Management and add the Consumer
Connect URL, user name, and password to the system-default RG management
profile. For example:

ACS URL = http://connect01.local:8080
Note: Consumer Connect is a type of Auto Configuration Server (ACS).

User Name = tr069

Password = tr069

(For all other settings, accept defaults)
See Creating an RG Management Profile (on page 198) for details.
2. To create an ONT Template defining key management aspects of the RSG and logical
assignments of the physical GE ports, select CMS > Profile > E7/ONT > Templates
> ONT > Create and then enter the following parameters:
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
464

ID = value between 1-20

Name = RG_3FB

Management Mode = native

Management Profile = 1(system-default)

WAN Protocol = DHCP

GE 1 = RG 1

GE 2-GE 4 = FB 1

(For all other settings, accept defaults)
Note: Both RG and FB interfaces support a DSCP/IP-precedence to P-bit mapping on
a per-VLAN basis. The LAN side clients are responsible for setting DSCP/IPprecedence.
See Creating an ONT Template (on page 191) for details.
3. Build a match list and service tag action for HSI services as follows:
To learn how service tag actions work with the RG, see About Service Tag Actions for RGbased Services (on page 453).
a. Select CMS > Profile > E7/ONT > Service > Tagging > Match Lists > Create
and then enter the following parameters:

Name = @GPON_RG_HSI

(For all other settings, accept defaults)
b. In the Match List table select the match list created in step 2a, select Create >
Tagged Match Rule, and then enter the following parameters:

S-VLAN (Outer Tag) = 10

(For all other settings, accept defaults)
See Creating a Service Match List and Rules (on page 127) for details.
4. To create a service tag action for HSI services, select CMS > Profile > E7/ONT >
Service > Tagging > Tag Action > Create and then enter the following parameters:

Name = @GPON_RG_HSI

Action = Change Tag

Match List = @GPON_RG_HSI (created in step 2a)

S-VLAN (Outer Tag) = 2000

Outer P-Bit = 0

For AE ONT = N

(For all other settings, accept defaults)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
465
This service tag action matches on S-Tag 10 and changes the tag to 2000 as it is sent
upstream from the ONT or RSG.
See Creating Service-Tag Actions (on page 131) for details.
5. Build a multicast map for Full Bridge (FB) video services as follows:
Note: Multicast maps are not supported for RG-based video services.
a. Select CMS > Profile > E7/ONT > Service > Multicast > Multicast Maps >
Create > Multicast Maps and then enter the following parameters:

Name = @Video

(For all other settings, accept defaults)
b. In the list of multicast maps select @Video, click Create > Multicast Address Range
and then enter the following parameters:

Start IP Address: 224.0.0.1

End IP Address: 239.255.255.255
The multicast map limits ingress IGMP reports with a specific Destination MAC
Address that a STB can send.
See Creating a Multicast Address Map and Ranges (on page 181) for details.
6. Build an MVR profile for video services as follows:
a. Select CMS > Profile > E7/ONT > Service > Multicast > MVR > Create and
then enter the following parameters:

Name = @Video

Sync to E7 = Y

Local VLAN = N
b. In the list of MVR profiles select @Video, click Create > MVR VLAN and then
enter the following parameters:

Address Range1 Start = 224.0.0.0

Address Range1 End = 239.255.255.255
See Creating an MVR Profile and MVR VLAN Addresses (on page 178) for details.
7. To create a multicast profile for video services, select CMS > Profile > E7/ONT >
Service > Multicast > Multicast > Create and then enter the following parameters:

Name = @Video

Max Streams = 16

Multicast Maps = @Video

MVR Profile = @Video

(For all other settings, accept defaults)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
466
See Creating a Multicast Profile for details.
8. To create a service tag action for FB video services, select CMS > Profile > E7/ONT
> Service > Tagging > Tag Action > Create and then enter the following parameters:

Name = @FB_Video

Match List = 1 (all-untagged)

S-VLAN (Outer Tag) = 104

Outer P-Bit = 4

(For all other settings, accept defaults)
Note: Because only video services are supported on the FB interface, it is not necessary
to specify the OUI of the STB, and the all-untagged match list applies.
See Creating Service-Tag Actions (on page 131) for details.
9. To create a Ethernet bandwidth profiles for RG HSI and FB video services, select CMS
> Profile > E7/ONT > Service > Ethernet Bandwidth > Create and then enter the
following parameters:

Name = @GPON_RG_HSI_10x10

Peak Rate for Upstream = 10m

Peak Rate for Downstream = 10m

Committed Rate for Downstream = 10m

For AE ONT = N

(For all other settings, accept defaults)
See Creating an Ethernet Bandwidth Profile for GPON Services (on page 167) for details.
10. Verify that the WAN facing fiber is attached to the 836GE RSG.
11. To verify that the RSG has been discovered in the E7, navigate to the E7, double-click
ONTS, and then click Discovered ONTs.
12. To provision the RSG, select the 836GE RSG in the Discovered ONTs table, click
Action > Link to New Provisioning, and then enter the following parameters:

ONT Profile = 836GE

Template = RG_3FB (or the name of the ONT template that you created in step 1)

(For all other settings, accept defaults)
13. To provision Home Gateway services for HSI, click Provisioned ONTs > Services >
Create > Gateway Service and then select the following parameters:

Subscriber Port = RG-1

Service Name = Gateway Service: 1

BW Profile = @GPON_RG_HSI_10x10
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
467

Svc Tag Action = @GPON_RG_HSI

(For all other settings, accept defaults)
Gateway service is established, and the RSG downloads the configuration profile from
the Consumer Connect server.
14. To provision FB video services, click Provisioned ONTs > Services > Create >
Video Service and then select the following parameters:

Subscriber Port = FB-1

Service Name = Video: 1

BW Profile = @GPON_Video

Multicast Profile = @Video

Svc Tag Action = @FB_Video

(For all other settings, accept defaults)
15. To provision SIP voice service , click Provisioned ONTs > Services > Create > SIP
Service and then enter the following parameters:
Note: This step assumes that you have created a SIP profile and service tag action for
SIP voice service. See Creating a SIP Remote Configuration Profile (on page 213) and Creating
Service-Tag Actions (on page 131) for instructions.

Subscriber Port = Voice-1

SIP Profile = an existing SIP profile

User Name = user name for registration with SIP server (for example, a phone
number)

URI = the Universal Resource Indicator

Password = registration password

Service Tag Action = an existing service tag action

(For all other settings, accept defaults)
Configuring an E7 GPON RSG in External Mode (GPON OMCI
Download)
The following procedure provides a day one example for configuring an 836GE RSG in
External Mode for RG HSI (IPoE), RG video (MVR), and SIP voice services using a custom
RG configuration file created via the RG EWI.
To configure an E7 GPON RSG in External Mode using a custom RG configuration file
Note: The following example uses specific profile names, however you may substitute names
as needed.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
468
This procedure assumes the following conditions:






CMS is running at R12.1 or higher
E7 is running at R2.2 or higher
You have uploaded the custom RG configuration file to an FTP server, and the E7 can
reach the IP address of the FTP server
The RSG has been discovered in the E7
The RSG is configured for External Mode
You do not have any other RSGs or RG-enabled ONTs configured for External Mode
deployed in the network
Note: For instructions on creating an RG configuration file, refer to Creating a Custom RG
Configuration File Via the EWI for External Mode Deployments (on page 473).
Configure an RSG in External Mode using baseline RG values as follows:
1. To create an ONT Template defining key management aspects of the RSG and logical
assignments of the physical GE ports, select CMS > Profile > E7/ONT > Templates
> ONT > Create and then enter the following parameters:

ID = value between 1-20

Name = RG_TriplePlay

Management Mode = external

Config File Instance = 17

GE 1-GE 4 = RG 1

(For all other settings, accept defaults)
Note: RG interfaces support a DSCP/IP-precedence to P-bit mapping on a per-VLAN
basis. The LAN side clients are responsible for setting DSCP/IP-precedence.
See Creating an ONT Template (on page 191) for details.
2. Build a match list for HSI services as follows:
a. Select CMS > Profile > E7/ONT > Service > Tagging > Match Lists > Create
and then enter the following parameters:

Name = @GPON_RG_HSI

(For all other settings, accept defaults)
b. In the Match List table select the match list created in step 2a, select Create >
Tagged Match Rule, and then enter the following parameters:

S-VLAN (Outer Tag) = 10

(For all other settings, accept defaults)
See Creating a Service Match List and Rules (on page 127) for details.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
469
3. To create a service tag action for HSI services, select CMS > Profile > E7/ONT >
Service > Tagging > Tag Action > Create and then enter the following parameters:
To learn how service tag actions work with the RG, see About Service Tag Actions for RGbased Services (on page 453).

Name = @GPON_RG_HSI

Action = Change Tag

Match List = @GPON_RG_HSI (created in step 2a)

S-VLAN (Outer Tag) = 2000

Outer P-Bit = 0

For AE ONT = N

(For all other settings, accept defaults)
This service tag action matches on S-Tag 10 and changes the tag to 2000 as it is sent
upstream from the RSG.
See Creating Service-Tag Actions (on page 131) for details.
4. Build a match list for RG MVR video services as follows:
a. Select CMS > Profile > E7/ONT > Service > Tagging > Match Lists > Create
and then enter the following parameters:

Name = @GPON_RG_Video

(For all other settings, accept defaults)
b. In the Match List table select the match list created in step 2a, select Create >
Tagged Match Rule, and then enter the following parameters:

S-VLAN (Outer Tag) = 104

(For all other settings, accept defaults)
See Creating a Service Match List and Rules (on page 127) for details.
5. To create a service tag action for RG MVR video services, select CMS > Profile >
E7/ONT > Service > Tagging > Tag Action > Create and then enter the following
parameters:

Name = GPON_RG_Video

Action = Change Tag

Match List = @GPON_RG_Video (created in step 4a)

S-VLAN (Outer Tag) = 104

Outer P-Bit Source = Specify P-Bit

Outer P-Bit = 4

For AE ONT = N
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
470

(For all other settings, accept defaults)
This service tag action matches on S-Tag 104 and performs a change-tag action to 104 as
it is sent upstream from the RSG.
See Creating Service-Tag Actions (on page 131) for details.
6. Build an MVR profile for video services as follows:
a. Select CMS > Profile > E7/ONT > Service > Multicast > MVR > Create and
then enter the following parameters:

Name = @Video

Sync to E7 = Y

Local VLAN = N
b. In the list of MVR profiles select @Video, click Create > MVR VLAN and then
enter the following parameters:

Address Range1 Start = 224.0.0.0

Address Range1 End = 239.255.255.255
See Creating an MVR Profile and MVR VLAN Addresses (on page 178) for details.
7. To create a multicast profile for video services, select CMS > Profile > E7/ONT >
Service > Multicast > Multicast > Create and then enter the following parameters:

Name = @Video

Max Streams = 16

MVR Profile = @Video

(For all other settings, accept defaults)
See Creating a Multicast Profile [GPON] (on page 177) for details.
8. To create Ethernet bandwidth profiles for RG HSI and MVR video services, select CMS
> Profile > E7/ONT > Service > Ethernet Bandwidth > Create and then enter the
following parameters:
RG HSI:

Name = @GPON_RG_HSI_10x10

Peak Rate for Upstream = 10m

Peak Rate for Downstream = 10m

Committed Rate for Downstream = 10m

For AE ONT = N

(For all other settings, accept defaults)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
471
RG MVR:

Name = @GPON_Video

Committed Rate for Upstream = 25m

Peak Rate for Upstream = 100m

Peak Rate for Downstream = 100m

Committed Rate for Downstream = 100m

For AE ONT = N

(For all other settings, accept defaults)
See Creating an Ethernet Bandwidth Profile for GPON Services (on page 167) for details.
9. On the Navigation Tree, click ONTs.
10. To transfer the file from the FTP server to the E7, click Config File Management >
Action > Retrieve and then enter the following parameters:

(enter relevant parameters for your FTP server)

File Path: File path of the RG configuration file on your FTP server

Vendor: CXNK

Instance: 17

Version: 1.0.0.0

Product: S8

Model: 8..GE.
Note: See Managing RG Configuration Files for a detailed description of the product
code and model mask fields.
11. To apply the downloaded RG configuration file to all RSGs deployed in the network,
click Action > Apply, and then enter the following parameters:

Vendor: CXNK

Model: 8..GE.

Product: S8
See Managing RG Configuration Files for details.
The RSG reboots. The primary SSID, primary WPA/WPA2 key, and admin password
for the RSGs are retained, and the RG attributes and features specified in the
configuration file are applied.
12. Verify that the WAN facing fiber is attached to the 836GE RSG.
13. To verify that the RSG has been discovered in the E7, navigate to the E7, double-click
ONTS, and then click Discovered ONTs.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
472
14. To provision the RSG, select the 836GE RSG in the Discovered ONTs table, click
Action > Link to New Provisioning, and then enter the following parameters:

ONT Profile = 836GE

Template = RG_TriplePlay (or the name of the ONT template that you created in
step 1)

(For all other settings, accept defaults)
15. To provision RG HSI services, click Provisioned ONTs > Services > Create >
Gateway Service and then select the following parameters:

Subscriber Port = RG-1

Service Name = Gateway Service: 1

BW Profile = @GPON_RG_HSI_10x10

Svc Tag Action = @GPON_RG_HSI

(For all other settings, accept defaults)
16. To provision RG MMR video services, click Provisioned ONTs > Services > Create
> Gateway Service and then select the following parameters:

Subscriber Port = RG-1

Service Name = Gateway Service: 1

BW Profile = @GPON_Video

Multicast Profile = @Video

Svc Tag Action = @GPON_RG_Video

(For all other settings, accept defaults)
17. To provision SIP voice service, click Provisioned ONTs > Services > Create > SIP
Service and then enter the following parameters:
Note: This step assumes that you have created a SIP profile and service tag action for
SIP voice service. See Creating a SIP Remote Configuration Profile (on page 213) and Creating
Service-Tag Actions (on page 131) for instructions.

Subscriber Port = Voice-1

SIP Profile = an existing SIP profile

User Name = user name for registration with SIP server (for example, a phone
number)

URI = type the Universal Resource Indicator

Password = registration password

Service Tag Action = an existing service tag action

(For all other settings, accept defaults)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
473
Creating a Custom RG Configuration File Via the EWI for External
Mode Deployments
The following procedure provides an example for creating a custom RG configuration file
via the RSG or RG-enabled ONT Embedded Web Interface (EWI), and then transferring
the file to an FTP server for future download to the E7 in GPON environments. This
procedure does not require access to Consumer Connect, or any type of Auto Configuration
Server (ACS).
A custom RG configuration file may be applied to RSGs/ONTs configured for External
Mode to support deployments involving advanced service models that cannot be supported
in Native Mode. Such deployments require a custom RG configuration file in order to
configure RG-specific parameters including DNS Host Mapping, LAN IP Address, and
DHCP server settings. The RG configuration file allows customization specific to your
service model, and replaces the default RG configuration.
To create a custom RG configuration file via the RG EWI
Note: After creating a custom RG configuration file, use the EWI to make subsequent
changes. Manual changes to the XML file created by the RSG are not recommended.
This procedure assumes the following conditions:



An FTP server is installed on your network and an FTP client is installed on your PC to
transfer the RG configuration file
The RSG/RG-enabled ONT has booted up and the operational image has been loaded
on the RSG
The RSG/RG-enabled ONT is configured for External Mode
1. Connect an Ethernet CAT 5 cable between the PC RJ-45 connector and any RSG/ONT
LAN port that is a member of the EWI.
The PC receives IP address 192.168.1.0/24 by default from the RG.
2. To access the RSG/ONT, launch your browser, enter IP address http://192.168.1.1,
and then log in using the following default credentials:

User Name: support

Password: support
Note: Do not use the admin user account for this procedure.
3. Configure the service VLANs as follows:
Note: The following example uses specific VLAN labels and IDs, however you may
substitute as needed.
a. Navigate to the hidden service provider page at http://192.168.1.1/html/support.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
474
b. From the Support menu, click Service WAN VLANs.
c. In the Wide Area Network (WAN) Settings page, click New.
d. To configure the default HSI VLAN, enter the following parameters in the Add
Service VLAN window:

Service VLAN Label: ipoe_rgv10

NAT: Enabled

Tag Action: Tagged

VLAN ID: 10

(for all other settings, accept defaults)
e. Click Apply.
f. In the Wide Area Network (WAN) Settings page, click New.
g. To configure the default video VLAN, enter the following parameters in the Add
Service VLAN window:

Service VLAN Label: ipoe_rgv104

IGMP: Enabled

NAT: Enabled

Connection Type: DHCP (IPoE)

Tag Action: Tagged

VLAN ID: 104

Priority: 4
h. Click Apply.
After configuring the HSI and video VLANs, the WAN settings display as follows:
4. Based on any other deployment requirements, navigate to the appropriate page and apply
the desired settings.
See the Calix 800GE Residential Gateway EWI User's Guide for further information on the
functionality of each EWI page.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
475
5. Back up the RG configuration file to the PC as follows:
a. From the main menu bar, click Utilities.
b. From the Utilities menu, click Configuration Save.
c. Verify that Action: Backup is selected.
d. In the Version box, enter version string value 1.0.0.0 for the configuration file (or
assign the next incremental value).
e. Click Backup.
6. Using the FTP client on your PC, transfer the RG configuration file to an FTP server on
the network for download to the E7.
Note: The E7 management interface must be able to reach the FTP server.
Managing a Custom RG Configuration File from CMS
This topic provides example procedures for managing a custom RG configuration file for an
836GE RSG from the CMS in a GPON environment, as follows:
Note: To create an RG configuration file, refer to Creating a Custom RG Configuration File Via
the EWI (on page 473).



Applying a custom RG configuration file to a single RSG: Use this procedure when
all RSGs are using the same configuration file, and you want to test a new configuration
file, or if you want to update the configuration file used by each RG incrementally.
Applying a custom RG configuration file to all RSGs: Use this procedure when all
RSGs are using the same configuration file, you have tested a new configuration file on a
single RSG, and you want to apply the configuration file to all RSGs.
Restoring a baseline custom RG configuration file for a single RSG: Use this
procedure when you are deploying an RSG in a GPON environment that was previously
configured for AE services, or you need to recover from a suspected customer-induced
condition on the RSG.
These procedures assume the following conditions:





CMS is running at R12.1 or higher
E7 is running at R2.2 or higher
You have uploaded the custom RG configuration file to an FTP server, and the E7 can
reach the IP address of the FTP server
The RSG(s) has been discovered in the E7
The RSG(s) is configured for External Mode
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
476
To apply a custom RG configuration file for a single RSG
This procedure assumes that all RSGs in the network are currently provisioned for
configuration file instance 17.
1. On the Navigation Tree, click ONTs.
2. To transfer the file from the FTP server to the E7, click Config File Management >
Action > Retrieve and then enter the following parameters:

(enter relevant parameters for your FTP server)

File Path: File path of the RG configuration file on your FTP server

Vendor: CXNK

Instance: 18

Version: 1.0.0.0

Product: S8

Model: 8..GE. (The ‘.’ at the end is required because RSGs/ONTs reports spaces in
the model number.)
Note: You can enter both a product code and model mask to identify a specific
RSG/ONT model as shown in this example, or you can enter the product code and/or
model mask to identify a group of RSGs/ONTs, including a mix of model types. See
Managing RG Configuration Files for a detailed description.
3. To configure the E7 to download and apply the retrieved RG configuration file to
836GE RSGs deployed in the network, click Action > Apply, and then enter the
following parameters:

Vendor: CXNK

Model: 8..GE.

Product: S8
Note: At this point, because all RSGs are provisioned for configuration file instance 17,
the E7 OLT will not send provisioning updates to the RSGs and subsequently, none of
the RSGs will download the new configuration file.
4. To apply configuration file instance 18 to a single RSG, do the following:
a. Select Provisioned ONTs > Services > Table, and click the RG interface ID.
b. Click the Config File Instance drop-down arrow and select 18.
The RSG resets. The primary SSID, primary WPA/WPA2 key, and admin password for
the RSG are retained, and the RG attributes and features specified in the new
configuration file are applied.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
477
To apply a custom RG configuration file for all RSGs
This procedure assumes that all RSGs in the network are provisioned for configuration file
instance 17.
1. On the Navigation Tree, click ONTs.
2. To transfer the file from the FTP server to the E7, click Config File Management >
Action > Retrieve and then enter the following parameters:

(enter relevant parameters for your FTP server)

File Path: File path of the RG configuration file on your FTP server

Vendor: CXNK

Instance: 17

Version: 1.0.0.1 (assuming that version 1.0.0.0 is running on the system, and you are
retrieving version 1.0.0.1)

Product: S8

Model: 8..GE.
Note: You can enter both a product code and model mask to identify a specific
RSG/ONT model as shown in this example, or you can enter the product code and/or
model mask to identify a group of RSGs/ONTs, including a mix of model types. See
Managing RG Configuration Files for a detailed description.
3. To apply the downloaded RG configuration file to all RSGs deployed in the network,
click Action > Apply, and then enter the following parameters:

Vendor: CXNK

Model: 8..GE.

Product: S8
See Managing RG Configuration Files for details.
The RSGs reboot. The primary SSID, primary WPA/WPA2 key, and admin password
for the RSGs are retained, and the RG attributes and features specified in the new
configuration file are applied.
To restore a baseline custom RG configuration file for a single RSG
This procedure assumes that you have downloaded the custom RG configuration file to the
E7 and applied that particular instance to the RSG.
1. On the Navigation Tree, click ONTs.
2. In the table view, select the RSG, and then select Action > Reset ONT.
3. In the Reset ONT window, check the Reset RG box and then click Reset ONT.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
478
The RSG deletes the existing RG configuration file, resets, downloads the custom RG
configuration file over OMCI from the E7, and resets again. The primary SSID, primary
WPA/WPA2 key and admin password are restored to default parameters, and the RG
attributes and features specified in the configuration file are applied.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Appendix A
Reference Information
This appendix provides general reference information about the Calix E7 Ethernet service
access platform.
Topics Covered
This appendix covers the following topics:






System capacities
HPNA services deployment
ONT power shedding
LED behavior
Line card additional status descriptions
SIP configuration file and settings
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
480
System Support Capacities
The Calix E7 system support capacities follow.
Description
Capacity
General System
User accounts, locally defined (not in the RADIUS)
100
Simultaneous Netconf sessions for web browser interface
15
The Netconf interface has a 30 minute timeout, which cannot
be turned off. The web browser interface has an inactivity
timer of approximately 30 minutes.
Simultaneous CLI sessions
5
There is an ENABLE/DISABLE flag in the CLI for session
timeout, but the only ENABLE timeout duration supported is 30
minutes.
There might temporarily be an extra Netconf (16) and an extra
CLI session (6), for just the duration of the login process. If the
extra session is accepted, then a previous, oldest session is
dropped under the assumption that this session is most likely
to be idle.
SNMP Trap destinations (defined by IP address)
5
RADIUS
4 authentication RADIUS servers and 4 accounting RADIUS
servers are supported
All of the authentication RADIUS servers are assumed to have
the same authentication information, that is, server replication.
The system communicates with the “best” server, and then
only sends to the next server if it does not get a response.
Where “best” is determined by the success rate of getting
responses to recent requests.
MAC address Table (E7 line cards share a common table)
32,000
Switching Capacity
Wire speed full duplex forwarding across all ports. Dedicated,
non-blocking switch port to all VDSL2, GPON, GE, and 10GE
interfaces.
Default "Native" VLAN for untagged traffic (GE and 10GE
ports) on Trunk and Edge interfaces.
1 - This VLAN is utilized to switch all untagged traffic through
the system. This VLAN cannot be deleted, but can be
changed. Not supported on GE-24x GE, ONT Ethernet ports,
or E7 Access interfaces.
Bandwidth Policing (rate limiting)

1 Mbps up to line rate for GE and 10GE ports

64 kbps to 2 Mbps in 64kbps increments; 1 Mbps
increments from 2 Mbps up to 400 Mbps for GPON ONT
Ethernet ports
Egress Priority Queues per 1GE or 10GE port (not ONT
Ethernet ports)

8 per port (GE and 10GE) ports based on P-bit value with
P-bit = 7 highest priority
Queue Scheduling Algorithm
Strict priority across 8 queues, with maximum and minimum
guaranteed bandwidth per class. Tail drop is used when
dropping packets from queue.
Broadcast Video channels using IGMP snooping
800 (maximum IGMP group size)
Ethernet port mirrors
1
VLANs
Maximum number
4090 (VLANs 1002, 1003, 1004, and 1005 are reserved for
system use but can be changed to another range, VLAN 1 is
untagged)
Default Internal VLAN (GE and 10GE ports only)
1 - This VLAN is utilized to switch all untagged traffic through
the system. This VLAN cannot be deleted, but can be
changed. Not supported on ONT Ethernet ports.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
481
Description
Capacity
Tag Actions per card (ONT service tag actions are not included
in this limit)
768
VLANs that may be set to DHCP Snoop or Proxy (E7-2 only)

256 per system

48 per VDSL2 line card
VLANs that may have PPPoE profile assigned (E7-2 only)
24
VLANs that may have MAC-Forced-Forwarding and/or IP-SrcVerify enabled (per VDSL2 Card only)
8
10Gig SFP+/XFP modules and GPON Optical Interface
Modules (OIMs)
Must be keyed
Ethernet services
Services allowed on an xDSL port
6
Services allowed on an ONT Ethernet port

Services on a VDSL card that may resolve to a VLAN marked
as TLAN (this includes the same TLAN on multiple services)
8 on an ONT Ethernet port

4 on an ONT RG interface

1 on an ONT FB interface
24
Ethernet Frame Size
MTU Maximum Transmission Unit size (bytes)
The E7 supports the ability to set the MTU Maximum
Transmission Unit size (bytes) on a GE and 10GE port
interface to a maximum of 9600 bytes, not including Ethernet
header and Two VLAN tags for Q-in-Q. GPON ONTs and
xDSL ports have a fixed MTU value.

MTU = 9600 bytes (E7 Ethernet interfaces)

MTU = 9600 bytes (E7 Backplane links)

MTU = 2000 bytes (700GE and 760GX GPON ONTs)

MTU = 1600 bytes (700GX GPON ONTs)

MTU = 1500 bytes (E7 xDSL ports)
The MTU is defined as the maximum size payload of the
Ethernet frame, not the Ethernet frame size. In an IP network,
this is the largest IP packet that can be transmitted on the
Ethernet network without IP packet fragmentation. The
Ethernet frame size varies depending on the number of VLAN
tags applied to the payload, plus allowances for
Preamble/Delimiter and interframe gap.

+ 8 bytes (Preamble/Delimiter)

+ 14 bytes (header not including VLAN tags)

+ 4 bytes (inner VLAN tag)

+ 4 bytes (outer VLAN tag)

+ 4 bytes (trailer)

+ 12 bytes (interframe gap)
For example:

2000 bytes = MTU

2026 = Max Ethernet frame (with two VLAN tags without
Preamble/Delimiter)

2034 = Max Ethernet frame (with two VLAN tags including
Preamble/Delimiter)

2046 = Max Ethernet frame (with two VLANs,
preamble/Delimiter, and Interframe Gap)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
482
Description
Capacity
Maximum throughput: Protocol efficiency for Ethernet
Protocol efficiency = Payload size ÷ Frame size
Maximum efficiency is achieved with the largest allowed
payload size.
For example:

1500 bytes (Maximum payload size)

+ 8 bytes (preamble)

+ 14 bytes (header)

+ 4 bytes (trailer)

+ 12 bytes (interframe gap)

= 1538

1500 (payload size) ÷ 1538 (frame size) = 97.53%
Maximum throughput: Efficiency for optional 802.1Q tagged
Ethernet packets, include 4 bytes in the frame size
1500 (payload size) ÷ 1542 (frame size) = 97.28%
Maximum throughput: Protocol overhead for Ethernet as a
percentage
Protocol overhead = 1 — Protocol efficiency
Maximum throughput: IP payload throughput
Payload Throughput = Efficiency * Net bit rate
Where the physical layer net bit rate (the wire bit rate)
depends on the Ethernet physical layer standard, and may be
10 Mbit/s, 100 Mbit/s, 1 Gbit/s or 10 Gbit/s. Maximum
throughput for 100BASE-TX Ethernet is consequently 97.53
Mbit/s without 802.1Q, and 97.28 Mbit/s with 802.1Q.
ERPS Ring
ERPS rings per E7-2 system
6
ERPS rings per E7-20 system
2
ERPS rings per VDSL card
2
ERPS domain per E7 interface
1
“units” per ERPS ring
32
This number counts each E7-20 SCP card located in the ring
as 1 unit, and each E7-2 card located in the ring as 1 unit,
whether in a dual- or single-card E7 shelf. This number does
not include devices or E7s subtended from the ring.
Interconnected rings for a “chain of ERPS rings”
3
Unit count per E7-2
1
Unit count per E7-20 SCP card
1 (up to 2 units per E7-20 shelf)
Unit count per E7-2 line card
1 (up to 2 units per E7-2 shelf)
Link Aggregation Groups
Link Aggregation Groups per shelf using GE ports
16
Active ports per Link Aggregation Group using GE ports
8
Ports per Link Aggregation Group using GE ports
8
Link Aggregation Groups per shelf using 10GE ports
2
Ports per Link Aggregation Group using 10GE ports
4
Traffic Rate Limiters
Per E7 card
1500
Independent policy rules
1500
Per card with RSTP protection
1500
Profiles and Templates per E7
Policy Maps
256
Policies per Policy Map
1500
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
483
Description
Capacity
Policy Map Match entries for a VDSL card
24
Policy Map Match entries for all other card types
1536
Class Maps
1500
Class Rules per Class Map
100
Subscriber bandwidth profiles (GPON and VDSL together)
300
Multicast profiles
32
MVR profiles
5
Match lists (GPON and VDSL together)
255
Service tag actions
256
DSL port templates
264
SIP Remote Configuration Profiles (GPON)
32
SIP Gateway Profiles
1 per VDSL2 line card, 32 per system
TDM Gateway profiles
32
Dial plans
20
Maximum Network Dial Plan Table size is 100 rows x 28 (2800
bytes).
A rule cannot exceed 28 bytes (or characters), because a rule
must fit in a single row. A rule is not allowed to overlap rows.
Ds1PWE3 profiles
8
DSCP maps
10
IP Precedence maps
10
H.248 Gateway profiles
32
MGCP Gateway profiles
32
ONT PWE3 profiles
4
ONT profiles
200
PPPoE profiles
50
VLAN IGMP profiles
20
Security profiles
16
Security profiles used by VDSL interfaces (including bondedLinks) must have DHCP lease limt = 10 or less
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
484
GPON Capacities
Description
MTU Packet Size (GPON services, total frame size)
PON Bandwidth
GPONs per OLT card
Capacity

2000 Bytes 700 ONTs

2000 Bytes 760 ONTs

2.488 Gbps downstream

1.244 Gbps upstream
4 per:

E7-2 GPON-4/r2 line card

E7-20 GPON-4x line card
8 per:
ONT capacity

E7-2 GPON-8 line card

E7-20 GPON-8x line card

64 ONTs per PON

256 ONTs per card:
E7-2 GPON-4
E7-2 GPON-4 r2
E7-20 GPON-4x

512 ONTs per card:
E7-2 GPON-8
E7-20 GPON-8x

1024 ONTs per E7-2 1U shelf

5120 ONTs per E7-20 shelf

32 ONTs per PON for extended reach modules
Note: Each PON has a non-blocking 2.5 Gbps
symmetric connection to the E7 switch core.
Ethernet services allowed on an ONT port or interface
Standard Reach Optical Interface Module (OIM)
Extended Reach OIM
GPON with one-way video overlay - three wavelengths
per PON
GPON with two-way video overlay - four wavelengths
per PON
Optical Distribution Network

8 on an ONT Ethernet port

4 on an ONT RG interface

1 on an ONT FB interface

Up to 64 passive optical splits per PON

Up to 20 km reach with 32 way split

Up to 11 km reach with 64 way split

Up to 20 km reach with 1:32 passive optical splits
per PON (28 dB link budget)

Up to 40 km reach with 1:8 way split

GPON digital downstream: 1490 nm

GPON digital upstream 1310 nm

Video overlay downstream: 1550 nm

GPON digital downstream: 1490 nm

GPON digital upstream 1310 nm

Video overlay downstream: 1550 nm

Return path upstream: 1610 nm
Single-fiber Class C+ (32 dB link margin)
Class C+ and FEC with the following line cards:

E7-20 GPON-8x

E7-2 GPON-8

E7-2 GPON-4 r2
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
485
Description
“Old” OIMs used in C7
Capacity
Too wide and cannot be placed in adjacent ports
Note: New, narrow OIMs are available for the E7, have
new part number. OIMs must be purchased from Calix
Packet based ONT services supported
Video

RF Video

IPTV with IGMP snooping
Voice

ONT SIP for voice (32 SIP profiles supported)

Calix TDM Gateway (C-SIP) for voice

H.248 Gateway

T1

T1 PseudoWire on 766GX ONT
Data
Home Gateway support for multicast traffic switching
and routing

High Speed Internet

Transparent Lan Service (TLS)

Up to 16 set-top boxes or media clients connected
behind the LAN ports

Up to 40 service flows per ONT
Passing traffic between ONTs on same PON
Not unless PON_TLAN is enabled on the VLAN
T1 PseudoWires per PON
128
SIP Remote Configuration Profiles supported
32
SIP Gateway Profiles supported
32
Tagged Rules per ONT Ethernet port
12
Untagged Rules per ONT Ethernet port
16
Ethernet Bandwidth Profiles
300
DHCP Snoop-Enabled VLANs per GPON card
256
ONT Bandwidth shaping and limiting

Minimum metered rate of 64kbps

Maximum metered rate of 1000Mbps

Below 2 Mbps, increments in steps of 64kbps

Above 2Mbps, increments in steps of 1Mbps

4 egress priority queues per PON where P-bit
values are mapped into 4 GPON Classes of Service
(CoS) queues (Tail drop is used when dropping
packets from queue)

Queue scheduling algorithm of strict priority with
maximum and minimum guaranteed bandwidth per
class

Maximum of 4 distinct multicast VLANs per ONT

1024 downstream policers per PON

Each CoS used on each ONT port uses a policer

The limit of Expedited Forwarding traffic = 614 Mbps
per PON upstream

Both Expedited Forwarding (EF) and Assured
Forwarding (AF) traffic classes have a CIR
component to the bandwidth. The CIR can be
provisioned up to the 1.2G limit upstream, but only
~600M can be in the EF class.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
486
Description
Number of Egress Priority Queues (GPON)
Capacity

4096 GEM ports per PON

1024 T-CONTs per PON
8 T-CONTs per T-Series and P-Series GE ONT, 4 (+1
for OMCI) T-CONTs per P-Series GX ONT

8 T-CONTs per ONT

32 GEM ports per ONT
P-bit values are mapped into eight CoS queues. P- and
T-Series GE ONTs.
Queue Scheduling Algorithm
Strict priority and WFQ with maximum and minimum
guaranteed bandwidth per class. Tail drop is used when
dropping packets from queue.
Static IP Addresses/Subnets within the E7 GPON
subsystem

Only 1 static IP subnet can be provisioned per ONT
Ethernet service.

Up to 16 static IP hosts can be provisioned per ONT
Ethernet port, on a single service or across multiple
services.

The ONT supports up to 256 “IP stations” per ONT
Ethernet port. The number of IP stations includes
active DHCP leases, static IP hosts, and
dynamically learned hosts within a static subnet.

The ONT supports up to 1024 total “IP stations” per
ONT. The number of stations includes active DHCP
leases, static IP hosts, and dynamically learned
hosts within a static subnet.
Service Hairpin capacity on a PON
2.4 Gbps of traffic on a per GPON-4 card basis
(equivalent to 50% of the total upstream PON bandwidth
capacity)
MEPs per ONT
4
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
487
Using the Cut-Through Telnet or Web Interface
With the CMS Desktop cut-through feature, you can start a Telnet or web session to do the
following:

Work in the web interface or command line interface (CLI) mode to perform
provisioning commands.

Provision a higher (later) version of software through the CMS server, even though
such nodes have not been tested on, and may not work with, the current CMS
software server version.
CMS supports a maximum of 15 Web Interface cut-through sessions and 5 Telnet CLI
sessions for each node.
Cut-through sessions require Min (Minimum) CMS Administration privileges and Full
Provisioning privileges for the node on which you want to establish a connection.
To open to a Telnet session
1. On the Navigation Tree, click a Region or Network Group.
2. In the Work Area, click Network Details > and the model name of the device.
3. In the Display Name column, right-click the node of which you want to connect.
4. From the pop-up menu, select one of the following:

Cut-Through Web to open a CMS Cut-Through Web window.

Cut-Through Telnet to open a CMS Telnet Cut-Through CLI window.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
488
HPNA Services Deployment
Calix Model 712GE and 722GE ONTs are used in conjunction with HPNA-enabled devices
to deliver IPTV and HSI over standard residential coaxial cable or a coaxial to twisted pair
adapter.
Note: Twisted pair wiring is not compatible with HPNA deployments if using analog video
services as well.
HPNA devices may include set-top boxes, stand-alone HPNA bridges, and Residential
Gateways. HPNA services are provisioned identically to Ethernet services.
Calix ONTs with HPNA incorporate a coaxial F-connector port that connects directly to the
home network's coaxial cable. These ONTs support both HPNA networking and traditional,
one-way RF video.
Before deploying an HPNA network, the service provide must plan and characterize the
signal attenuation cause by the in=home coaxial plant. Many options exist for deploying
HPNA in a network including:



Point-to-point configuration: a single HPNA device (ONT) connected directly to an
HPNA device such as a set-top box or HPNA bridge.
Point-to-multipoint with no RF video: a single HPNA device (ONT) connected to a
splitter with multiple HPNA device outputs.
Point-to-multipoint with RF video: a single HPNA device (ONT) connected to a
diplexer and splitter with multiple HPNA device outputs as well as RF video signals over
the same coax.
Refer to CAB-13-034 HPNA 3.1 Home Networking Guide for IPTV, RF Video, Whole-home
DVR, and Internet Access Applications for details.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
489
ONT Power Shedding
All Calix ONTs are managed via an ONT Management Control Interface (OMCI). An
important element of OMCI is determining what services remain active and which services
can be disabled when an ONT loses its primary power source. Known as power shedding,
the E7 system allows you to conserve battery backup capacity when a loss of power is
detected by provisioning the Disable on BATT field for the port. Power shedding is
controlled at the ONT port level and can be set to determine whether services (ports) remain
on or are disabled when an ONT goes on battery back-up power. The table below
summarizes how power shedding is implemented in the E7 system.
Port Type
Default Behavior
Available Override
POTS
POTS circuits remain active when on
battery (Disable on BATT is set to NO).
No override. POTS services remain on when on
battery.
FE/GE or HPNA
Disabled after 5 minutes. Allows mission
critical applications to be shut down
gracefully (Disable on BATT is set to YES).
Disable on BATT can be set to NO - Ethernet Port
services remain active indefinitely (or until battery
capacity is depleted).
RF
Disabled Immediately. Typically, RF video
not a mission critical application (Disable on
BATT set to YES).
Disable on BATT can be set to NO - RF Video
services remain active indefinitely (or until battery
capacity is depleted).
T1
T1 circuits remain active when on battery
(Disable on BATT set to NO).
No override. T1 services remain on when on
battery.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
490
E7 LED Behavior
Line card LEDs




Service (SRVC) indicates at least 1 port has been provisioned on this slot
Control (CTRL) green LED indicates active controller, amber LED indicates standby
controller
Fault (FAIL) red LED indicates the card is in fault
Cards have additional LED states at boot time (see table below)
Port LEDs







Green LED (Ethernet) that stays on indicates a link with no activity, flashes during
activity.
Green LED (GPON port) that stays on indicates at least 1 ONT is ranged, blinks when
the first ONT is ranging.
Green LED (DSL port) that stays on indicates at least one DSL subscriber port is
synched up and operating correctly (the system is up, operational, and ready to or able to
pass traffic).
Green LED (POTS port) that stays on indicates, indicates at least one POTS subscriber
port is operating correctly (the system is up, operational, and is off-hook).
Red LED (10GE) indicates a module is inserted into a port that is redirected to the
backplane.
Inserting a supported module into a port causes the LED to blink green 3 times,
indicating module recognition.
If no blinking occurs on module insertion, the module is not supported/recognized; An
alarm is present in this situation.
Line card LED boot sequence
CTRL LED
SRVC LED
FAIL LED
State Description
Active Card Boot Sequence
Green
Yellow
Red
Power on
off
Off
Red
NB Execution
1 short green
Off
Red
UB Execution
2 short green
Off
Red
Booting Kernel
3 short green
Off
Red
Application Loading
2 short, 1 long green
Off
Off
Application Initializing
1 short, 1 long green
Off
Off
Database Loading
Green 1 Short Off
Off
Off
Database Activation
Green
Off
Off
Application Startup complete, no
services defined
Green
Green
Off
Application startup complete,
services defined
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
491
CTRL LED
SRVC LED
FAIL LED
State Description
Standby Card Boot Sequence
Green
Yellow
Red
Power On
Off
Off
Red
NB Execution
1 Short Yellow
Off
Red
UB Execution
2 Short Yellow
Off
Red
Booting Kernel
3 Short Yellow
Off
Red
Application Loading
2 Short 1 Long Yellow
Off
Off
Application Initializing
1 Short 1 Long Yellow
Off
Off
Database Loading
Yellow 1 Short Off
Off
Off
Database Activiation
Yellow
Off
Off
Application Startup complete, no
services defined
Yellow
Green
Off
Application startup Complete,
services defined
Other States
Off
Off
All Short Red
Equipment Mismatch
Yellow blinking
Red blinking
E7-20 card inserted in E7-2
Yellow rapid
blinking
Red rapid blinking
E7-20 SCP card is partially inserted
in chassis. Push the card fully into the
chassis where the card reboots.
All Short Yellow
Off
Flash Write in Progress (database or
program update)
Off
2 Short Red
Green
Pattern & color
Reflects Service
and Flash Write
Red
Equipment Failure for Active Card
yellow
Pattern & color
Reflects Service
and Flash Write
Red
Equipment Failure for Standby Card
1 Short Green
Off
Off
No Database in Flash on Active Card
1 Short Yellow
Off
Off
No Database in Flash on Standby
Card
Off
Off
2 Short 1 Long Red
Green blinking
Yellow rapid blinking
Pattern & Color Reflects
Card Status
Off
Application Initiated Shutdown
Waiting for card to cool down before
loading application
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
492
E7 Line Card Additional Status Descriptions
The table below shows the possible states for an E7 line card Additional Status.
Line Card Additional Status
Description
default-prov
Indicates that the object's parameters have never been changed
from default values.
child-prov
Indicates that the object has subtending records provisioned. these
may be ports or interfaces that have been updated by the user.
present
Indicates that the object is present.
system-disabled
Indicates an object has a service affecting alarm reported against it,
or any of its parents.
For example:

An ONT parent is the system object.

A Card parent is the shelf, and then the system.
user-disabled
Indicates an object is disabled by the user (Admin status =
disabled).
degraded
Indicates an object (ONT or a Card) has a non-service affecting
alarm reported against it.
active
Indicates that the card is the system controller which manages
alarms, configuration, and performance monitoring. A "*" is shown
next to the card label in the web interface and in the CLI show
card command results.
standby
Indicates the card is in standby status.
Note: If the card has the default-prov state and does not have the child-prov state, this
indicates that the card hierarchy is completely default and will be deleted from the database
upon card departure.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
493
Resetting an ONT
This topic shows you how to reset a specified ONT. There are the following levels of reset
for an ONT:


ONT reset causes it to restart, re-range, and be discovered

Force option reboots the specified ONT

Reset RG option (selected) reboots the specified ONT and restores the defaults
for the RG partition of the ONT (for example 836GE)
ONT reset to the factory default returns the ONT settings to the factory default.
Note: A Calix GE ONT in RG mode will not reset when the light is absent.
To reset an ONT
1. On the Navigation Tree, click ONTs.
2. In the Workarea, click Provisioned ONTs > Provisioning.
3. In the table of ONTs, double-click the row with the ONT that you want to reset.
4. In the menu, click Action > Reset ONT.

Select the Force checkbox if you want to force the ONT to reset.

Select the Reset RG checkbox if you also want the defaults restored for the RG
partition of an ONT (for example 836GE) along with the reboot of the ONT
partition.
5. Click Reset ONT to indicate that you want to proceed with the action.
For CLI:
reset ont <ONT ID> [forced]
reset ont <serial number>
reset ont <ONT ID> rg-restore-defaults
To reset the ONT to factory default
1. Disconnect power to the ONT.
2. Disconnect the network fiber (pigtail) from the ONT.
3. Connect an RJ-11 terminated buttset to the first (LINE ONE) voice port on the ONT.
Note: For buttset devices using alligator clips, back-out the Tip and Ring screws and clip
the buttset leads to the T and R posts (black to Tip, red to Ring).Verify that the network
fiber is disconnected from the ONT.
4. Reapply power to the ONT.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
494
5. For 700G or 700GX ONTs, listen to the buttset and wait until you hear a click sound
(approximately 10 seconds for SFU ONTs or 15-20 seconds for MDU ONTs).
6. For 700GE ONTs, wait for the OFF HOOK LED on the ONT to start blinking
(approximately 50 seconds for 2 POTS ONTs, 60 seconds for 4 POTS ONTs).
Note: If digits are entered prior to the ONT being ready (click sound or OFF HOOK
Blink), those digits are ignored.
7. Press "*", "*", "*" and "#" (star, star, star, pound) keys on the buttset key pad. The
buttset sounds DTMF tones as the keys are pressed.
8. A voice prompts to acknowledge your selection of requesting an ONT master reset.
9. After the confirmation prompt, press '1' to confirm the reset. A voice prompt replies,
"ONT Master Reset is completed".
10. Press '0' to abort. A voice prompt replies, "ONT Master Reset is cancelled".
11. Continue entering new RONTA commands as required.
12. Re-connect the network fiber to the ONT and wait for the ONT to come on line.
For CLI:
reset ont <ONT ID>
reset ont <ONT ID> rg-restore-defaults (only applies to RG mode)
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
495
Restarting a SIP Remote Configuration Profile
This topic shows you how to restart a SIP remote configuration profile that is assigned to an
xDSL port service, causing a restart for system components using the SIP remote
configuration profile.
To restart a SIP remote configuration profile
1. On the E7 Navigation Tree, click Shelf# > Card# > xDSL#.
2. In the Workarea, click Port > Provisioning > Basic.
3. In the toolbar, click Action > Reset to Default, and then Yes to return the xDSL port
to default settings.
4. Click Apply.
For CLI:
restart dsl-port <port>


For stand-alone E7-2, DSL ports are specified by card, port type, and port number. For
example: 2/v4.
For modular chassis E7-2, DSL ports are specified by shelf, card, port type, and port number.
For example: 1/2/v4.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
496
CPE Vendor-Defined Fault Codes for TR-069
TR-069 from the DSL forum indicates that fault codes in the range of 9800-9899 are
considered CPE-based vendor-defined fault codes.
Code Name
Code
Number
Code Description
CMSRET_SUCCESS_REBOOT_REQUIRED
9800
Config successful, but requires reboot to take effect.
CMSRET_SUCCESS_UNRECOGNIZED_DATA_IGN
ORED
9801
Success, but some unrecognized data was ignored.
CMSRET_SUCCESS_OBJECT_UNCHANGED
9802
Success, furthermore object has not changed, returned by STL
handler functions.
CMSRET_FAIL_REBOOT_REQUIRED
9803
Config failed, and now system is in a bad state requiring reboot.
CMSRET_NO_MORE_INSTANCES
9804
getnext operation cannot find any more instances to return.
CMSRET_MDM_TREE_ERROR
9805
Error during MDM tree traversal.
CMSRET_WOULD_DEADLOCK
9806
Caller is requesting a lock while holding the same lock or a
different one.
CMSRET_LOCK_REQUIRED
9807
MDM lock is required for this operation.
CMSRET_OP_INTR
9808
Operation was interrupted, most likely by a Linux signal.
CMSRET_TIMED_OUT
9809
Operation timed out.
CMSRET_DISCONNECTED
9810
Communications link is disconnected.
CMSRET_MSG_BOUNCED
9811
Msg was sent to a process not running, and the
bounceIfNotRunning flag was set on the header.
CMSRET_OP_ABORTED_BY_USER
9812
Operation was aborted/discontinued by the user.
CMSRET_RECURSION_ERROR
9817
Too many levels of recursion.
CMSRET_OPEN_FILE_ERROR
9818
Open file error.
CMSRET_EAGAIN_ERROR
9820
Socket write EAGAIN error.
CMSRET_SOCKET_ERROR
9821
Socket error.
CMSRET_KEY_GENERATION_ERROR
9830
Certificate key generation error.
CMSRET_INVALID_CERT_REQ
9831
Requested certificate does not match with issued certificate.
CMSRET_INVALID_CERT_SUBJECT
9832
Certificate has invalid subject information.
CMSRET_OBJECT_NOT_FOUND
9840
Failed to find object.
CMSRET_INVALID_FILENAME
9850
Filename was not given for download.
CMSRET_INVALID_IMAGE
9851
Bad image was given for download.
CMSRET_INVALID_CONFIG_FILE
9852
Invalid config file was detected.
CMSRET_CONFIG_PSI
9853
Old PSI/3.x config file was detected.
CMSRET_IMAGE_FLASH_FAILED
9854
Could not write the image to flash.
CMSRET_RESOURCE_NOT_CONFIGURED
9855
Requested resource is not configured/found.
Proprietary Information: Not for use or disclosure except by written agreement with Calix.
© Calix. All Rights Reserved.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising