65K110FTTP 29a PDF

Total Access 5000 Series
FTTP
Fiber to the Premises
P/N: 65K110FTTP
Basic Configuration Guide
January 2020
65K110FTTP-29A
To the Holder of this Document
To the Holder of this Document

This document is intended for the use of ADTRAN customers only for the purposes of the
agreement under which the document is submitted, and no part of it may be used, reproduced,
modified or transmitted in any form or means without the prior written permission of ADTRAN.
The contents of this document are current as of the date of publication and are subject to
change without notice.
Trademark Information
“ADTRAN” and the ADTRAN logo are registered trademarks of ADTRAN, Inc. Brand names
and product names included in this document are trademarks, registered trademarks, or trade
names of their respective holders.
Disclaimer of Liability
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is”, and any
liability arising in connection with such hardware or software products shall be governed by
ADTRAN’s standard terms and conditions of sale unless otherwise set forth in a separately
negotiated written agreement with ADTRAN that specifically applies to such hardware or
software products.
To the fullest extent allowed by applicable law, in no event shall ADTRAN be liable for errors in
this document for any damages, including but not limited to special, indirect, incidental or
consequential, or any losses, such as but not limited to loss of profit, revenue, business inter-
ruption, business opportunity or data, that may arise from the use of this document or the infor-
mation in it.
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of
danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
Safety and Regulatory information is provided in this document and/or a separate Safety and
Regulatory document that is part of the product-applicable document set.
Copyright © 2020 ADTRAN, Inc.

All Rights Reserved.
2 65K110FTTP-29A
Revision A
Revision History
Revision History
Rev A January 2020 Initial release.
65K110FTTP-29A 3
Revision A
Revision History
4 65K110FTTP-29A
Revision A
Table of Contents
Table of Contents
Overview................................................................................................................................ 21
Scope of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
In this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Hazard and Advisory Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Related Online Documentation and Resources..................................................................... 24
Fiber to the Premises Overview . . . . . . . . . . . . . . . . . . . . . . . .27

1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.3 GPON Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1.3.1 Customer VLAN (C-VLAN) Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.3.2 N:1 Service VLAN (S-VLAN) Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.3.3 Hybrid N+1:1 Combined VLAN Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1.4 Fiber to the Premises with Active Ethernet Overview . . . . . . . . . . . . . . . . . . . . 33

1.4.1 Customer 1:1 VLAN (C-VLAN) Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.4.2 N:1 Service VLANs Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.5 Voice Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

1.5.1 GR-303 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.5.2 MGCP Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.5.2.1 Call Agent and Endpoint Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.5.2.2 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.5.3 SIP Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.5.3.1 Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.5.3.2 Terminating Multimedia Communications (Five SIP Facets) . . . . . . . . . . . . . . . 40
1.5.3.3 SIP Pre-Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.6 Command Line Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

1.6.1 Command Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
1.6.2 CLI Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.6.3 CLI Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1.6.4 CLI Input Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
1.6.5 CLI Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1.7 User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
GPON Provisioning using CLI. . . . . . . . . . . . . . . . . . . . . . . . . .49

2.1 Scope of this Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
65K110FTTP-29A 5
Revision A
Table of Contents
2.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.3.1 OLT/PON Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.3.1.1 Enable the OLT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.3.1.2 Provision the PON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.3.1.3 Enter the Registration-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.3.1.3.1 Registration-ID Entry for Total Access 3xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.3.1.3.2 Registration-ID Entry for Total Access 421x /Total Access 421xw . . . . . . . . . . 55
2.3.1.3.3 Total Access 421x/Total Access 421xw LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.3.1.3.4 Registration-ID Entry for Total Access 3xx Residential Gateway . . . . . . . . . . . 57
2.3.1.3.5 Registration-ID Entry for Total Access 324RG and 334RG . . . . . . . . . . . . . . . . 58
2.3.1.3.6 Registration-ID Entry for Total Access 324 3rd Generation and Total
Access 374. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.3.1.3.7 Registration-ID Entry for Total Access 4xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.3.1.4 Discover the ONT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.3.2 Service Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.3.2.1 Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.3.2.1.1 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.3.2.1.2 MGCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.3.2.1.3 GR-303. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.3.2.1.4 Select Your Voice Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.3.2.1.5 SIP OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.3.2.1.6 SIP Non-OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.3.2.1.7 MGCP OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.3.2.1.8 MGCP Non-OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.3.2.1.9 GR-303 Voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.3.2.2 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.3.2.3 Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.3.2.4 RF-Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.3.2.5 Transport Layer Security (TLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.3.2.5.1 Select Your TLS Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.3.2.5.2 TLS Single Tag Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.3.2.5.3 TLS Double Tag Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.3.3 Create an EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.3.4 Set the Voice Service Mode on the ONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.3.5 Provision the Port on the ONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.3.5.1 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.3.5.2 FXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.3.5.3 RF-Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
2.3.5.4 Virtual Gigabit Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.3.5.5 VDSL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2.3.5.6 Provision the EFM Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
2.3.6 Create an IP Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
2.3.7 Create an EVC-Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.3.8 Provision the SIP Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2.3.8.1 Configure additional SIP Trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2.3.9 Provision the MGCP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6 65K110FTTP-29A
Revision A
Table of Contents
2.3.10 Provision Non-OMCI MGCP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

2.3.11 Provision the SIP Dialing Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2.3.11.1 Dial Plan Pattern Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2.3.11.2 SPRE Pattern Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
2.3.11.3 External Line Code Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
2.3.11.4 Dial Plan Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
2.3.12 Provision Class of Service (CoS) (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . 104
2.3.13 Provision for Global Voice (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
2.3.14 Provision the Voice User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
2.3.15 Provision the Media Profile (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
2.3.16 Provision the CODEC Profile (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
2.3.17 Provision the Call Feature Profile (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . 109
2.3.18 Provision the OMCI SIP Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
2.3.19 Provision OMCI MGCP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
2.3.20 Provision GR-303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Provisioning using the Web GUI. . . . . . . . . . . . . . . . . . . . . . . 115

3.1 Scope of this Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

3.3.1 OLT/PON Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.3.1.1 Enable the OLT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.3.1.2 Provision the PON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.3.1.3 Enter the Registration-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
3.3.1.3.1 Registration-ID Entry for Total Access 3xx . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
3.3.1.3.2 Registration-ID Entry for Total Access 421x /Total Access 421xw . . . . . . . . . 122
Total Access 421x/Total Access 421xw LEDs . . . . . . . . . . . . . . . . . . . . . . . . . 123
3.3.1.3.3 Registration-ID Entry for Total Access 3xx Residential Gateway . . . . . . . . . . 124
Set Registration ID Activation using a Telco Butt Set . . . . . . . . . . . . . . . . . . . 124
3.3.1.3.4 Registration-ID Entry for Total Access 324RG and 334RG . . . . . . . . . . . . . . . 126
Access 374. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
3.3.1.3.6 Registration-ID Entry for Total Access 4xx . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
3.3.1.4 Discover the ONT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
3.3.2 Service Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.3.2.1 Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.3.2.1.1 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.3.2.1.2 MGCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.3.2.1.3 GR-303. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.3.2.1.4 Select Your Voice Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.3.2.1.5 SIP OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.3.2.1.6 SIP Non-OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.3.2.1.7 MGCP OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
3.3.2.1.8 MGCP Non-OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
65K110FTTP-29A 7
Revision A
Table of Contents
3.3.2.1.9 GR-303 Voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

3.3.2.2 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
3.3.2.3 Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.3.2.4 RF-Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
3.3.2.5 TLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
3.3.2.5.1 Select Your TLS Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
3.3.2.5.2 TLS Single Tag Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
3.3.2.5.3 TLS Double Tag Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
3.3.3 Create an EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
3.3.4 Set the Voice Service Mode on the ONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.3.5 Provision the Port on the ONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
3.3.5.1 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
3.3.5.2 FXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
3.3.5.3 RF-Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
3.3.5.4 Virtual Gigabit Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
3.3.6 Create an IP Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
3.3.7 Create an EVC-Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
3.3.8 Provision the SIP Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
3.3.9 Provision the MGCP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
3.3.10 Provision Non-OMCI MGCP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
3.3.11 Provision the SIP Dialing Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
3.3.11.1 Dial Plan Pattern Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
3.3.11.2 SPRE Pattern Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
3.3.12 Provision the Common Profiles (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
3.3.12.1 Provision the Call Features Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
3.3.12.2 Provision the Media Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
3.3.12.3 Provision the Codec Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
3.3.18 Provision GR-303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Provisioning Active Ethernet using CLI . . . . . . . . . . . . . . . . .179

4.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
4.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
4.4 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

8 65K110FTTP-29A
Revision A
Table of Contents
4.4.1.2 Discover the ONT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

4.4.1.3 ONT Inband Management Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
4.4.2.1 Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
4.4.2.1.1 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
4.4.2.1.2 MGCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
4.4.2.1.3 GR-303. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
4.4.2.1.5 SIP OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
4.4.2.1.7 MGCP OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
4.4.2.1.9 GR-303 Voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
4.4.2.2 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
4.4.2.3 Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
4.4.2.4 TLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
4.4.3 Create an EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
4.4.5.1 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
4.4.5.2 FXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
4.4.6 Create an IP Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
4.4.7 Create an EVC-Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
4.4.15 Provision the Media Profile (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
4.4.16 Provision the CODEC Profile (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
4.4.17 Provision the Call Feature Profile (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . 229
4.4.20 Provision GR-303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Provisioning Active Ethernet using the Web. . . . . . . . . . . . .235

5.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
65K110FTTP-29A 9
Revision A
Table of Contents
5.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

5.3.1.2 Discover the ONT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
5.3.1.3 ONT Inband Management Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
5.3.2.1 Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
5.3.2.1.1 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
5.3.2.1.2 MGCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
5.3.2.1.3 GR-303. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
5.3.2.1.5 SIP OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
5.3.2.1.7 MGCP OMCI Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
5.3.2.1.9 GR-303 Voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
5.3.2.2 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
5.3.2.3 Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
5.3.3 Create an EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
5.3.5.1 Ethernet Port Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
5.3.5.2 FXS Port Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
5.3.6 Create an IP Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
5.3.7 Create an EVC-Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
5.3.12 Provision the Common Profiles (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
5.3.12.1 Provision the Call Features Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
5.3.12.2 Provision the Media Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
5.3.12.3 Provision the Codec Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
5.3.18 Provision GR-303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
10 65K110FTTP-29A
Revision A
Table of Contents
GPON Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285

6.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
6.3 VLAN/TLS/IPTV Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

6.3.1 1:1 Customer VLAN (C-VLAN) Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
6.3.1.1 Example 1:1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
6.3.2 N:1 Service VLAN (S-VLAN) Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
6.3.2.1 N:1 Service VLAN Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
6.3.2.2 N:1 Service VLAN Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
6.3.3 Hybrid N+1:1 Combined VLAN Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
6.3.3.1 Hybrid N+1:1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
6.3.3.2 Hybrid N+1:1 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
6.4 TLS Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

6.4.1 TLS Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
6.4.2 TLS Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
6.4.3 IPTV Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Active Ethernet Configurations. . . . . . . . . . . . . . . . . . . . . . . . 309

7.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
7.3 1:1 Customer VLAN (C-VLAN) Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

7.3.1 Example 1:1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
7.4 N:1 Service VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

7.4.1 N:1 Service VLAN Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
7.4.2 N:1 Service VLAN Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
7.5 Hybrid N+1:1 Combined VLAN Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

7.5.1 Hybrid N+1:1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
7.5.2 Hybrid N+1:1 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
7.6 TLS Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

7.6.1 TLS Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
7.6.2 TLS Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

8.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
8.3 Shapers, GPON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
65K110FTTP-29A 11
Revision A
Table of Contents
8.3.1 Downstream Shaping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

8.3.2 Upstream Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
8.4 Provisioning using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

8.4.1 Downstream Shaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
8.4.2 Downstream Shaper for Multiple Customers . . . . . . . . . . . . . . . . . . . . . . . . . . 334
8.4.2.1 P-Bit to Queue Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
8.4.2.2 EVC Map to QoS Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
8.4.2.3 Queue Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
8.4.3 Upstream Shaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
8.4.3.1 Upstream Shaping Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
8.4.3.2 Downstream GPON QoS for User Fairness. . . . . . . . . . . . . . . . . . . . . . . . . . . 337
8.4.3.2.1 Total Minimum Rate Threshold Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . 339
8.4.3.2.2 Per Service Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
8.4.3.2.3 Single Subscriber Per ONT Model Example . . . . . . . . . . . . . . . . . . . . . . . . . . 341
8.4.3.2.4 Example Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Scenario 1 - Congested PON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Scenario 2 - Congested PON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Scenario 3 - Uncongested PON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Scenario 4 - Uncongested PON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
8.4.4 Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
8.4.4.1 Downstream Shaper Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
8.4.4.2 Downstream Shaper Provisioning for Multiple Customers . . . . . . . . . . . . . . . . 349
8.4.4.2.1 P-Bit to Queue Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
8.4.4.2.2 EVC Map to QoS Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
8.4.4.2.3 Queue Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
8.5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

8.5.1 Step 1: Create Unique Queues for Each Port . . . . . . . . . . . . . . . . . . . . . . . . . 351
8.5.2 Step 2: Attach the Downstream Queue Profiles and Upstream Channels
to Each Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
8.5.3 Step 3: Attach the Downstream Shapers to the Specified Queues from
the Map Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
8.5.4 Step 4: Attach the Upstream Shapers to the Specified Channels . . . . . . . . . . 352
8.5.5 Attach/Detach Interface to the Shaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
8.6 Shapers, AE (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

8.6.1 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
8.6.1.1 CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
8.6.1.1.1 Downstream Shaper Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
8.6.1.1.2 Upstream Shaper Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
8.6.2 Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
8.6.2.1 Downstream Shaper Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
8.6.2.2 Upstream Shaper Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
8.7 Policers, AE (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

8.7.1 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
8.7.1.1 CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
12 65K110FTTP-29A
Revision A
Table of Contents
8.7.2 Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
SFP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361

9.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
9.3 Information Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

9.3.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
3rd Party ONT Provisioning for Active Ethernet . . . . . . . . . .363

10.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
10.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

10.3.1 Example Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Home Phoneline Networking Alliance . . . . . . . . . . . . . . . . . . 367

11.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
11.3 Introduction to HPNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
11.4 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
IEEE 802.1X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

12.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
12.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

12.3.1 Port-Based Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
12.3.2 RADIUS Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
12.3.2.1 RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
12.4 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

12.4.1 Step 1: Provision a Subtended Host for RADIUS Client . . . . . . . . . . . . . . . . . 375
12.4.2 Step 2: Provision a RADIUS Server and Group. . . . . . . . . . . . . . . . . . . . . . . . 377
12.4.3 Step 3: Provision the ONT Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
12.4.4 Step 4: Provision the RADIUS Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
12.4.5 Step 5: Enable System-Wide 802.1X Authentication . . . . . . . . . . . . . . . . . . . . 382
12.5 Show Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

12.5.1 Status Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
65K110FTTP-29A 13
Revision A
Table of Contents
12.5.1.1 GPON Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

12.5.1.2 GPON Port Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
12.5.1.3 ONT Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
12.5.1.4 ONT Port Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
12.5.1.5 ONT Gigabit Port 802.1X Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
12.5.1.6 Radius Relay Agent Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
12.5.2 Performance-Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
12.5.2.1 Current ONT 802.1X Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
12.5.2.2 Previous ONT 802.1X Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
12.5.2.3 Current ONT Radius Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
12.5.2.4 Previous ONT Radius Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
12.5.2.5 Current Relay Agent Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
12.5.2.6 Previous Relay Agent Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
12.6 Provisioning Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

12.6.1 Example 1 - One RADIUS Server in the Network with RADIUS Relay . . . . . . 387
12.6.2 Example 2 - Two RADIUS Servers in the Network without RADIUS Relay
Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Activation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .391

13.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
13.3 Manual Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

13.3.1 Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
13.3.2 Con. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
13.4 Auto-Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

13.4.1 Pros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
13.4.2 Cons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
13.5 Auto-Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

13.5.1 Pros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
13.5.2 Cons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
13.6 Registration-ID Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

13.6.1 Pros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
13.6.2 Cons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
ONT Capability Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . 399

14.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
14.3 Adding a New ONT Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
14 65K110FTTP-29A
Revision A
Table of Contents
14.4 Removing an ONT Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
14.5 Adding a Vendor Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
14.6 Removing a Vendor Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
14.7 Restoring a Fixed Part Number Entry to Default Value . . . . . . . . . . . . . . . . . . 405
14.8 Restoring Vendor Entry to Default Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
14.9 ONT Capability Provisioning Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Warranty and Contact Information . . . . . . . . . . . . . . . . . . . . 409
65K110FTTP-29A 15
Revision A
List of Figures
List of Figures
Figure 1-1. Total Access 5000 GPON General Application Diagram . . . . . . . . . . . . . . 29

Figure 1-2. 1:1 Customer VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 1-3. N:1 Service VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 1-4. Hybrid N+1:1 Combined VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 1-5. Total Access 5000 Active Ethernet General Application Diagram . . . . . . . 33
Figure 1-6. Customer 1:1 VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 1-7. N:1 Service VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 1-8. Hybrid N+1:1 Combined VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 1-9. MGCP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 1-10. ONT MGCP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 1-11. Total Access 5000 Logon Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 1-12. User Statistics Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 2-1. 401 Web GUI Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 3-1. OLT Card Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 3-2. PON Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 3-3. 401 Web GUI Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 3-4. ONT Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 3-5. Create EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 3-6. Edit EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 3-7. Edit EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 3-8. Voice Service Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 3-9. ONT Port Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 3-11. FXS Port Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 3-12. RF-Video Port Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 3-13. IP-Host Create Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 3-14. IP-Host Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 3-15. EVC-Map Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 3-16. EVC-Map Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 3-17. EVC-Map Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 3-18. EVC-Map IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 3-19. SIP Trunk Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Figure 3-20. Dial Plan Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 3-21. SIP User Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 3-22. SIP User Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 5-1. OLT Card Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 5-2. GE Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Figure 5-3. ONT Inband Management Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Figure 5-4. Create EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Figure 5-5. Edit EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Figure 5-6. Edit EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Figure 5-7. Voice Service Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
16 65K110FTTP-29A
Revision A
List of Figures
Figure 5-9. ONT Ethernet Port Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Figure 5-10. FXS Port Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Figure 5-11. IP-Host Create Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Figure 5-12. IP-Host Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Figure 5-13. EVC-Map Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Figure 5-14. EVC-Map Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Figure 5-15. EVC-Map Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 5-16. EVC-Map IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 5-17. SIP Trunk Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Figure 5-18. Dial Plan Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Figure 5-19. SIP User Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Figure 5-20. SIP User Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Figure 6-1. 1:1 Customer VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Figure 6-2. N:1 Service VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Figure 6-3. Hybrid N+1:1 Combined VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 297
Figure 7-1. 1:1 Customer VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Figure 7-2. N:1 Service VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Figure 7-3. Hybrid N+1:1 Combined VLAN Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 320
Figure 8-1. GPON Downstream Shaping Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Figure 8-2. Per PON Bandwidth Thresholds Example . . . . . . . . . . . . . . . . . . . . . . . . 338
Figure 8-3. Downstream QoS for Single Subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 8-4. Example Provisioning of Weights and Minimum Rates . . . . . . . . . . . . . . 344
Figure 12-1. Port Authentication Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Figure 14-1. Adding a New ONT Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Figure 14-2. Removing an ONT Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Figure 14-3. Adding a Vendor Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Figure 14-4. Removing Vendor Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Figure 14-5. Entry Before being Restored to Default Value . . . . . . . . . . . . . . . . . . . . . 405
Figure 14-6. Restored Entry to Default Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Figure 14-7. Restoring Vendor Entry to Default Value . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 14-8. Restored Entry to Default Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
65K110FTTP-29A 17
Revision A
List of Tables
List of Tables
Table 1. List of Topics in the Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Table 2. Related Online Documents and Resources . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 1-1. Section 1 Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 1-2. Five Facets of SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 1-3. Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 1-4. CLI Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 1-5. Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Table 1-6. Input Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 2-1. Section 1 Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 2-2. Activation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 2-3. Range Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 2-4. Inband Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 2-5. Registration-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 2-6. ONT Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 2-7. Registration-ID Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 2-8. Registration-ID Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 2-9. Front Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 2-10. Discover the ONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Table 2-11. Voice Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Table 2-12. EVC and TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 2-13. Voice Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 2-14. Non-Default Metro Ethernet Network Interface . . . . . . . . . . . . . . . . . . . . . . 69
Table 2-15. MAC-Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 2-16. Subscriber Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Table 2-17. Discover the ONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 2-18. Port Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 2-19. VDSL Deployment Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 2-20. IP Host Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Table 2-21. Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Table 2-22. Subscriber Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 2-23. Authentication Mode Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 2-24. DHCPv6 Access Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 2-25. Supported Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 2-26. Additional EVC-Map Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 2-27. Dial Plan Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Table 2-28. SPRE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Table 2-29. External Line Code Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Table 2-30. Media Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 2-31. CODEC Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 2-32. Call Feature Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Table 2-33. SIP Voice User Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Table 3-1. Section 3 Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Table 3-2. Range Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
18 65K110FTTP-29A
Revision A
List of Tables
Table 3-3. Registration-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Table 3-4. ONT Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 3-5. Registration-ID Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 3-6. Registration-ID Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Table 3-7. Front Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 3-8. ONT Discovery Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Table 3-9. Voice Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Table 3-10. EVC and TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Table 3-12. MAC-Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Table 3-13. Port Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Table 3-14. Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Table 3-15. Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Table 3-16. Common Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 4-2. Inband Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Table 4-4. Non-Default Metro Ethernet Network Interface . . . . . . . . . . . . . . . . . . . . . 193
Table 4-5. MAC-Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Table 4-6. Subscriber Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Table 4-7. Discover the ONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Table 4-8. Port Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Table 4-9. IP Host Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Table 4-11. Subscriber Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Table 4-12. Authentication Mode Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Table 4-13. DHCPv6 Access Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Table 4-14. Supported Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Table 4-15. Additional EVC-Map Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Table 4-16. Dial Plan Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Table 4-17. SPRE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Table 4-18. External Line Code Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Table 4-22. SIP Voice User Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Table 5-4. Port Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Table 5-6. Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Table 5-7. Common Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
65K110FTTP-29A 19
Revision A
List of Tables

Table 8-2. Congested PON Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Table 8-3. Congested PON Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Table 8-4. Uncongested PON Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Table 8-5. Uncongested PON Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Table 10-1. Section 10 Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Table 12-2. RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Table 12-4. Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Table 12-5. Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
20 65K110FTTP-29A
Revision A
Introduction, Overview
Overview
This guide provides installation instructions for provisioning Fiber to the Premises (FTTP). This
guide provides both CLI and GUI instructions.
Scope of this Guide

The Total Access 5000 Series FTTP Basic Configuration Guide is designed for planning a
network or provisioning service. This guide provides application and technology overviews,
example configurations, and provisioning steps to help you get service up and running. Use
this guide as a base for tailoring your system to your specific requirements.
The provisioning instructions and examples in this guide represent general use cases; they do
not address all provisioning scenarios and operator-specific use cases.
In this Guide
This guide contains the topics listed in Table 1.
Table 1. List of Topics in the Guide
Section Topic Scope
1 “Fiber to the Premises Overview” This section provides an over-

view of provisioning FTTP to a
customer’s premises.
2 “GPON Provisioning using CLI” This section provides provisioning
for GPON using CLI.
3 “Provisioning using the Web GUI” This section provides provisioning

for GPON using the Web GUI.
4 “Provisioning Active Ethernet using CLI” This section provides the minimum
amount of steps required to provi-
sion a GPON module for the FTTP
application using Active Ethernet
and CLI.
5 “Provisioning Active Ethernet using the Web” This section provides the minimum
amount of steps required to provi-
sion a GPON module for the FTTP
application using Active Ethernet
using the Web GUI.
6 “GPON Configurations” This section provides examples of

common Total Access 5000 GPON
configurations.
7 “Active Ethernet Configurations” This section provides examples of

common Total Access 5000 Active
Ethernet configurations.
8 “Traffic Management” This section covers Traffic Manage-

ment (shapers and policers) provi-
sioning that can be applied to your
network.
65K110FTTP-29A 21
Revision A
Table 1. List of Topics in the Guide (Continued)
Section Topic Scope
9 “SFP Information” This section provides the command

to display the CLEI code information
of an installed SFP in the selected
GPON OLT.
10 “3rd Party ONT Provisioning for Active Ether- This section provides the minimum
net” steps required for third party ONT
provisioning for an Active Ethernet
(AE) deployment. It also provides an
example deployment
11 “Home Phoneline Networking Alliance” This section provides a brief over-

view of Home Phoneline Networking
Alliance (HPNA), and how to provi-
sion for HPNA
12 “IEEE 802.1X” This section provides an overview of

the IEEE 802.1X feature, provision-
ing options, useful show commands,
and example provisioning for this
feature.
13 “Activation Mode” This section provides four different

methods for activating your GPON
ONT. Each method contains a list of
pros and cons associated with that
registration method.
14 “ONT Capability Provisioning” This section provides a method to

configure the OLT for the expected
functionality of an ONT. The main
purpose of this feature is to ease
integration of new ONTs into the sys-
tem.
15 “Warranty and Contact Information” This section provides Warranty and

contact information.
“Acronyms” This section provides a list of acro-

nyms used throughout this guide,
22 65K110FTTP-29A
Revision A
Hazard and Advisory Symbols

The following Hazard symbols are used throughout this guide:
f WARNING!
Warning: Service affecting. Possible risk of system failure.
f CAUTION!
Caution: Indicates that a failure to take or avoid a specific action could result in a loss of data.
w NOTICE!
Notice: Provides information that is essential to the completion of a task.
g NOTE
Note: Information that emphasizes or supplements important points of the main text.
65K110FTTP-29A 23
Revision A
Introduction, Related Online Documentation and Resources
Related Online Documentation and Resources

Refer to Table 2 for additional information on Total Access 5000 FTTP applications.
Documentation for ADTRAN Carrier Networks products is available for viewing and download
directly from the ADTRAN Support Community website.
Go to: https://supportforums.adtran.com/welcome
Registration is required.
Table 2. Related Online Documents and Resources
Title Part Number Description
Total Access 5000 Series System Deployment Guides
Total Access 5000 Series Com- 65K97CMN-29 Provides the minimum configuration steps
mon Modules Basic Configura- needed to provision the Common Mod-
tion Guide ules for all Total Access 5000 Series plat-
forms. Use this guide to perform initial
provisioning of System Controller Mod-
ules (SCMs), Switch Modules (SMs), and
Management and Switch Modules
(MSMs).
Total Access 5000 Series System Guides
Total Access 5000/5006 Chassis 65KCHASSIS-5 Provides a comprehensive description of

Installation Guide and installation instructions for Total
Access 5000/5006 Chassis and associ-
ated components. Use this information to
install a new Chassis, to make SMIO3
alarm, clock, and test bus connections,
and to install modules in the Chassis.
Total Access 5004 Chassis 65K4CHASSIS-5 Provides a comprehensive description of

Installation Guide and installation instructions for Total
Access 5004 Chassis and associated
components. Use this information to
install a new Total Access 5004 Chassis
and to install Common modules in the
Chassis.
Total Access 5000/5006 Engi- 65K100ENG-7 Provides engineering specifications for

neering Guide the Total Access 5000/5006 Chassis and
components, including Line, Access, and
Fan Modules. Use this information during
network planning, when ordering new or
replacement components, and for an
overall understanding of the Total Access
5000/5006 product line.
24 65K110FTTP-29A
Revision A
Table 2. Related Online Documents and Resources (Continued)
Total Access 5004 Engineering 65K499ENG-7 Provides engineering specifications for

Guide the Total Access 5004 Chassis and com-
ponents, including Line, Access, and Fan
Modules. Use this information during net-
work planning, when ordering new or
replacement components, and for an
overall understanding of the Total Access
5004 product line.
Total Access 5000 Series CLI 65K103CLI-35 Provides Command Line

Dictionary Interface (CLI) commands for the
ADTRAN Total Access 5000 Series prod-
ucts. This guide gives detailed descrip-
tions of the commands, descriptions of
the syntax, and usage examples for each
supported product. Use this guide in con-
junction with the applicable system
deployment guide when using CLI to
deploy your application.
Total Acc4ess 5000 IO Modules N/A Provides information pertaining to the

and compatibility Matrix Total Access 5000 Series I/O modules
and rear/front blank panels. Use the com-
parison matrix in this guide to match the
correct I/O Module to the available Total
Access 5000 Series Access and Line
Modules.To access the matrix, go to http//
www.adtran.com
ADTRAN Pluggable Optics N/A Provides an online tool that enables

Compatibility Matrix selective filtering to identify the ADTRAN
approved optical modules that are appli-
cable for a specific application. To access
the matrix, go to: http//www.adtran.com/
sfp
Total Access 5000 Series Load N/A Provides maximum current draw and heat
Calculation Guidelines dissipation specifications for all Total
Access 5000 Series Chassis and modules
and Optical Network Edge (ONE) mod-
ules. Use this information to determine
the number of modules that can be safely
installed in the Chassis to ensure that the
Chassis is not overloaded. To o access
the matrix, go to: http//www.adtran.com
Total Access 5000 Switch Mod- 65KSMAPP-49 Provides information on provisioning the
ule Application Guide Total Access 5000 Switch Module for Link
Aggregation, Y-Cable Redundancy or
RADIUS.
Total Access 5000 GPON User 65K110GPON-31 Describes and defines the ADTRAN user
Interface Guide interface for the GPON Optical Line Ter-
mination. Use this guide as a reference
when provisioning with the Web.
65K110FTTP-29A 25
Revision A
Table 2. Related Online Documents and Resources (Continued)
Total Access 5000 Active Ether- 65K83AE-31 Describes and defines the ADTRAN user
net User Interface Guide interface for the Active Ethernet Access
Module. Use this guide in conjunction with
the applicable system deployment guide
when using Web to deploy your applica-
tion.
26 65K110FTTP-29A
Revision A
Fiber to the Premises Overview - Scope
1 Fiber to the Premises Overview
1.1 Scope
This section provides an overview of provisioning FTTP to a customer’s premises.
1.2 In this Section

This section contains the topics listed in Table 1-1.
Table 1-1. Section 1 Topics
Sub-Section Topic See Page …
1.3 GPON Overview 28
1.4 Fiber to the Premises with Active Ethernet Overview 33
1.5 Voice Overview 37
1.6 Command Line Interface Overview 42
1.7 User Interface 47
65K110FTTP-29A 27
Revision A
Fiber to the Premises Overview - GPON Overview
1.3 GPON Overview

Gigabit Passive Optical Network (GPON) technology provides a consistent and common
approach to advancing the public communications network using:
■ Traditional telephone services [Plain Old Telephone Service (POTS)]
■ High speed data services
■ Video services (CATV overlay or video over IP).
The GPON network consists of an Optical Line Terminal (OLT) located at the central office and
the Optical Network Terminal (ONT) located at the customer’s premises. Between them lies
the Optical Distribution Network (ODN) comprised of fibers and passive splitters or couplers. A
splitter is a device that divides an optical signal into two or more signals, each carrying a
selected frequency range. It can also reassemble signals from multiple signal sources into one
signal.
The GPON technology is based on Passive Optical Network (PON) technology. Traditionally,
telecommunication networks use devices that require power to transmit data from one point to
another including processors, memory chips, repeaters, and relays. With passive optical
networks, components that need power to transmit data between the central office and the
customer premises are replaced by passive components that guide traffic based on splitting
optical wavelengths to end points along the way. These passive components, such as splitters
and coupler devices, work by passing or restricting light and do not require power to transmit
data.
In a PON, a single piece of fiber can be run from the serving exchange out to a subdivision or
office park. Then, individual fiber strands can be run to each building. Also, serving equipment
can be split from the main fiber using passive splitters or couplers. This allows one piece of
fiber cable from the exchange to the customer to be shared by many customers, thereby
dramatically lowering the overall costs of deployment for Fiber To The Premises (FTTP) appli-
cations.
GPON offers the following features:
■ Consistent Operations, Administration, and Maintenance (OAM)
■ Traffic management and flow-through provisioning
■ Resiliency through dynamic circuit removal and restoration
■ Electrical and Optical Ethernet connections to the customer
Figure 1-1 on page 29 is an example of a GPON application.
28 65K110FTTP-29A
Revision A
Phone
Internet
Central Office Total Access 300
Internet ONT
Splitter
IPTV N x GigE GPON

Head End IP Core
HDTV
Set-Top Box
Voice
Total Access 5000 Total Access 300
Switch ONT
Phone
Internet
Figure 1-1. Total Access 5000 GPON General Application Diagram
65K110FTTP-29A 29
Revision A
1.3.1 Customer VLAN (C-VLAN) Model

Figure 1-2 displays a Total Access 5000 with a 1:1 Customer VLAN(C-VLAN) model. The C-
VLAN model creates a VLAN for each subscriber. All services (Data, Video, etc.) provided to
the customer are carried on the same VLAN. The number of VLANs required is equal to the
number of subscribers serviced.
An advantage of the C-VLAN model is security. Each subscriber is isolated from other
subscribers on separate VLANs. Another advantage is the similarity to older ATM based
configurations. The main disadvantage of the C-VLAN model is the lack of multicast repli-
cation. A separate copy of each multicast stream must be sent to the Total Access 5000 for
each user requesting it. These copies inefficiently use uplink bandwidth, thus limiting the size
of the subscriber base for each Total Access 5000.
Figure 1-2 illustrates a 1:1 Customer VLAN model inside a Total Access 5000. When provi-
sioning a C-VLAN each VLAN requires an EVC and an EVC Map to connect the EVC to the
correct UNI port.
MEN EVC
EVC Customer
Port Map
ONT 1
GPON
Network
Splitter
UNI
Unicast Ethernet
Cust. VLAN OLT UNI
Video
Port
/Data
Cust. VLAN
Unicast ONT 2
Video
/Data Network
UNI
Total Access 5000 Ethernet

UNI
Figure 1-2. 1:1 Customer VLAN Diagram
30 65K110FTTP-29A
Revision A
1.3.2 N:1 Service VLAN (S-VLAN) Model

Figure 1-3 displays a Total Access 5000 with a N:1 Service VLAN model. The N:1 Service
VLAN model creates one VLAN for each provided service (Data, Video, etc.). This service
VLAN is shared by multiple (N) subscribers.
The N:1 Service VLAN model allows for the replication of multicast traffic to multiple users.
This replication makes more efficient use of uplink bandwidth. The N:1 Service VLAN model
may also have advantages when adding video to an existing network, as the addition of a
video VLAN will not disrupt the existing data VLAN. A disadvantage of this model is that the
Total Access 5000 must provide additional security as the subscribers are not on isolated
VLANs.
Figure 1-3 illustrates a N:1 Service VLAN model inside a Total Access 5000. When provi-
sioning a S-VLAN each VLAN requires an EVC and an EVC Map to connect the EVC to the
required UNI port. Therefore each UNI port will have one EVC Map for each service passing
through it.
MEN EVC
EVC Customer
Port Map
ONT 1
GPON
Network
Splitter
UNI
Unicast/ Ethernet
Video VLAN UNI
Multicast
OLT
Video Port
Data VLAN
Unicast ONT 2
Data
Network
UNI

UNI
Figure 1-3. N:1 Service VLAN Diagram
65K110FTTP-29A 31
Revision A
1.3.3 Hybrid N+1:1 Combined VLAN Model

The following configuration examples provision a Total Access 5000 with a Hybrid N+1:1
VLAN (Combined VLAN) model. The Combined VLAN model creates a VLAN for each
subscriber that handles data and unicast video traffic. A separate shared VLAN is created for
multicast video and IGMP traffic, this allows for multicast replication. The number of VLANs
required is equal to the number of subscribers serviced plus one, (N+1:1).
This model provides all of the advantages of the C-VLAN, (i.e. security, simplified operations,
etc.) while removing its biggest disadvantage, no multicast replication.
Figure 1-4 illustrates a Hybrid N+1:1 VLAN model inside a Total Access 5000. When provi-
sioning a Combined VLAN each VLAN requires an EVC and an EVC Map to connect the EVC
to the each required UNI port. Therefore each UNI port will have one EVC Map for Unicast and
Data and another for Multicast.
MEN EVC
EVC Customer
Port Map
ONT 1
GPON
Network
Splitter
UNI
Ethernet
Data Cust. VLAN
UNI
OLT
Unicast Video
Port
Multicast Video
Multicast Video
Cust. VLAN
ONT 2
Data Network
UNI
Unicast Video
Ethernet
Total Access 5000 UNI
Figure 1-4. Hybrid N+1:1 Combined VLAN Diagram
32 65K110FTTP-29A
Revision A
Fiber to the Premises Overview - Fiber to the Premises with Active Ethernet Overview
1.4 Fiber to the Premises with Active Ethernet Overview

The increasing popularity of bandwidth intensive applications has driven the demand for fiber
access. Two of the most popular standards-based deployment options for fiber media from the
central office (CO) to the customer premises are Passive Optical Networks (PONs) and Active
Ethernet networks. Since the Active Ethernet deployment method uses standard Ethernet
frames, no transition protocol is required. This technology provides a consistent and common
approach to providing triple play services using the public communications network for:
■ Traditional telephone services [Plain Old Telephone Service (POTS)]
■ High speed data services
■ Video services
The optical network consists of an Optical Line Terminal (OLT) located at the central office and
Optical Network Terminals (ONTs) located at the customer premises. To allow for the trans-
mission of downstream and upstream traffic on one single fiber, different wavelengths are
used for each direction. Downstream traffic uses 1490 nm, while upstream traffic is carried on
1310 nm. The ONT employs a bi-directional SFP that is a complement to the bi-directional
SFP used in the OLT.
Supported distances for bi-directional SFPs range from 10 km up to 80 km.
Figure 1-5 displays an Active Ethernet general application diagram.
Phone
Internet
Central Office Total Access 300
Internet ONT
IPTV N x GigE Active

Head End IP Core Ethernet
HDTV
Set-Top Box
Voice
Total Access 5000 Total Access 300
Switch ONT
Phone
Internet
Figure 1-5. Total Access 5000 Active Ethernet General Application Diagram
65K110FTTP-29A 33
Revision A
1.4.1 Customer 1:1 VLAN (C-VLAN) Model

The following configuration examples provision a Total Access 5000 with a Customer 1:1
VLAN(C-VLAN) model. The C-VLAN model creates a VLAN for each subscriber. All services
(Data, Video, etc.) provided to the customer are carried on the same VLAN. The number of
VLANs required is equal to the number of subscribers serviced.
correct UNI port.
MEN EVC
EVC Customer
Port Map
ONT 1
OLT
Port
Data
Cust. VLAN
Multicast Video
Unicast Video
Data Cust. VLAN

Multicast Video
ONT 2
Unicast Video Network
OLT
UNI
Port

UNI
Figure 1-6. Customer 1:1 VLAN Diagram
34 65K110FTTP-29A
Revision A
1.4.2 N:1 Service VLANs Model

The following configuration examples provision a Total Access 5000 with a N:1 Service VLAN
model. The N:1 Service VLAN model creates one VLAN for each provided service (Data,
Video, etc.). This service VLAN is shared by multiple (N) subscribers.
GigaBit Multi-Service Edge Switch must provide additional security as the subscribers are not
on isolated VLANs.
each required UNI port. Therefore each UNI port will have one EVC Map for each service
passing through it.
MEN EVC
EVC Customer
Port Map
ONT 1
Network
OLT UNI
Port
Ethernet
Multicast Video VLAN UNI
Video
Data VLAN
Unicast ONT 2
Video OLT
Port Network
/Data
UNI

UNI
65K110FTTP-29A 35
Revision A
1.4.3 Hybrid N+1:1 Combined VLAN Model

This model provides all of the advantages of the C-VLAN, (i.e. security, simplified operations,
MEN EVC
EVC Customer
Port Map
ONT 1
Network
OLT
UNI
Port
Data Cust. VLAN
Unicast Video
Ethernet
UNI
Data Cust. VLAN

Unicast Video
Video VLAN
Multicast Video
ONT 2
OLT
Port Network
UNI
Total Access 5000

Ethernet
UNI
36 65K110FTTP-29A
Revision A
Fiber to the Premises Overview - Voice Overview
1.5 Voice Overview

The Total Access 5000 Series allows you to choose from several different delivery options
from traditional Generic Requirement 303 (GR-303) to VoIP options such as Session Initiation
Protocol (SIP) or Media Gateway Control Protocol (MGCP).
1.5.1 GR-303 Description

GR-303 is a Telcordia standard interface to a Class 5 telephone switch to a digital loop carrier
(DLC). This is the primary interface to the telco switch from the outside world. In order to
connect directly to the PTSN, IP phones and IP telephony gateways must adhere to GR-303.
1.5.2 MGCP Description

Media Gateway Control Protocol (MGCP) is an IP telephony signaling protocol from the
Internet Engineering Taskforce (IETF). MGCP requires the use of softswitches for call control
and resembles the telephony model of the circuit-switched PTSN more than SIP. The softs-
witch is aware of the entire call throughout its duration and enables operator intervention like
the PTSN.
MGCP works between a call agent or ONT MGCP Endpoint controller, usually a software
switch, and a ONT MGCP Endpoint with internal endpoints. The call agents create and
manage media sessions with endpoints of physical or virtual data sources through the ONT
MGCP Endpoint. The ONT MGCP Endpoint is the network device that converts voice signals
carried by telephone lines into data packets carried over the Internet or other packet networks.
In this network structure, the FTTP ONT product functions as an ONT MGCP Endpoint.
ONT MGCP Endpoints communicate with analog endpoints (telephones and fax through
foreign exchange station (FXS) interfaces) in a manner configured by the call agent. MGCP is
the protocol used for communication between the call agent and the ONT MGCP Endpoint. In
network structures that include multiple call agents and ONT MGCP Endpoints, call agents
communicate with other call agents using SIP and ONT MGCP Endpoints communicate with
other ONT MGCP Endpoints using Realtime Transport Protocol (RTP) or Realtime Control
Protocol (RTCP). See Figure 1-9 for an illustration of how MGCP functions in the network.
Media Gateway Media Gateway
VoIP
Network
Phone/Fax RTP Phone/Fax
MGCP MGCP
SIP
Call Agent Call Agent
Figure 1-9. MGCP Network
65K110FTTP-29A 37
Revision A
1.5.2.1 Call Agent and Endpoint Communication

ONT MGCP Endpoints use MGCP to communicate with call agents, which use SIP to commu-
nicate with other call agents. ONT MGCP Endpoints communicate with other ONT MGCP
Endpoints via RTP over the VoIP network, thus creating a VoIP call from analog sources.
Signals from the ONT MGCP Endpoint are transmitted to the call agent directly from a
specified FXS port. Each port is named in order to synchronize the signals. Every MGCP
command includes a transaction ID, acknowledgment, and a response. See Figure 1-10 for a
description of how ONT MGCP Endpoints communicate with call agents (via MGCP).
Media Gateway Call Agent Media Gateway
Create Connection
Response Session
description 1 (local)
Create Connection Session
description 1 (remote)
Response Session
description 2 (local)
Modify Connection Session

description 2 (remote)
Media Transfer
Figure 1-10. ONT MGCP Endpoints
1.5.2.2 Standards
There are two MGCP standards. The latest version, MGCP 1.0bis, is derived from RFC 3435.
The older version, MGCP 0.1/NCS 1.0, is based on a PacketCableTM derivative. Different call
agents can use different MGCP standards, so it is important to configure gateways and call
agents to use the same standards.
38 65K110FTTP-29A
Revision A
1.5.3 SIP Description

SIP is an IP telephony signaling protocol that is widely used to start and terminate voice calls
over the Internet. Supporting two-way and multi-party calls, SIP can be used for any real-time
media transmission over an IP network, including video calling and conferencing.
SIP, the IETF protocol for VoIP (Voice over Internet Protocol), is defined in RFC 3261. SIP
makes use of network entities called SIP proxies (external to the Total Access 5000 system) to
help route requests to the user's current location, authenticate and authorize users for
services, implement provider call-routing policies, and provide features to users. SIP
messages carry session descriptions that allow participants to agree on a set of compatible
media types.
SIP voice user provisioning is done in two parts. All profiles (media, codec-list, call-feature,
sip-trunk and dialing) are centrally provisioned and can be shared across multiple voice users.
SIP users are provisioned on the access modules and centrally provisioned profiles are
connected to these users on need basis.
Most of the profiles or various attributes in a profile are optional and have default value
associated with them. There are only few attributes that are mandatory to bring up sip voice
user. Sip-trunk is considered as a mandatory profile and proxy & registrar primary ip address
attributes must be configured and attached to a voice user. Similarly connection to fxs port,
sip-identity, auth name and sip-trunk are mandatory parameters for SIP voice user to be ready
for activation.
The SIP voice user is expected to go running once it has all mandatory and non-conflicting
parameters. There is a time lag (~10 sec) between change in configuration in the centrally
provisioned profiles and the ONT getting the updated configuration.
1.5.3.1 Benefits
Service provider customers deploy VoIP technologies in general to reduce capital and opera-
tional expenses. Key aspects of benefits include the following:
■ Reduced equipment, maintenance and support costs by capping or replacing legacy
Class 5 and Class 4 switch networks.
■ Reduced transport costs for long-distance and international traffic through use of
compressed voice on packet data networks.
■ Elimination of TDM networks for the local Public Telephone Service Network (PTSN) and
convergence on all-packet networks for access and edge infrastructure.
■ Reduction of operations personnel breadth and level of expertise by reducing or
eliminating TDM switching specialties.
■ Enhanced feature flexibility and expedited feature availability through deployment of SIP
call-routing and media-server feature creation.
The SIP gateway functionality can take the place of an integrated GR-303 interface but with
slightly lower cost points. However, the network host for the SIP gateway will now be a softs-
witch instead of a class 5 switch as typically used for GR-303.
65K110FTTP-29A 39
Revision A
1.5.3.2 Terminating Multimedia Communications (Five SIP Facets)

For establishing and terminating mutlimedia communications, SIP supports the five facets
listed in Table 1-2.
Table 1-2. Five Facets of SIP
Facet Description
User location The user location determines the end system used for communica-
tion.
User availability The user availability determines the willingness of the called party to
engage in communication.
User capability The user capability determines the form of media and media param-
eters used for communication.
Session setup The session setup establishes the session parameters for the caller
and calling party.
Session management The session management manages the transfer and termination of
services, modifies the session parameters, and invokes services.
1.5.3.3 SIP Pre-Installation Requirements

Ensure the following items are complete before deploying SIP:
■ Select, install, and configure one or more SIP proxies on the data network.
A softswitch is a high-performance network server or cluster capable of supporting

thousands (or even hundreds of thousands) of customer calls and provides SIP proxy
functionality. Most dedicate a part of their internal network to voice traffic, either physically
(via dedicated network resources) or logically (using virtual LANs) in order to provide the
low-latency, low-loss transport environment that IP voice requires.
■ Configure existing (or new, or expanded) data network routers and switches to transport
VoIP traffic throughout their network, from the access network, across edge networks to
their server core, and via transport networks to peer IP networks or other PSTN edge
gateways.
■ Select and install PSTN gateways to convert packet-voice to/from TDM-voice to enable
interworking between legacy segments of their network and new VoIP segments.
Often a customer will have already deployed VoIP for long-distance transport, and will
have replaced their Class 4 network (tandem switches) with softswitch technology before
transitioning their access network. The result is an expanding VoIP core with various
gateways around the edge connecting to the traditional PSTN. Eventually the VoIP
domain grows large enough to overtake the PSTN and the perspective effectively
reverses.
■ Select and install additional VoIP equipment such as media gateways (for voice mail,
announcements, conferencing, IVR services, etc.) and session border controllers (to
provide security with peer VoIP networks, cellular networks, etc.).
40 65K110FTTP-29A
Revision A
■ Integrate the above components with existing or new OSSs, and define the set of voice
services that can be supported.
In general, the service creation environment and the integration environment are more
flexible than for the traditional PSTN, but the integration effort can still be significant. For
many customers the transition to IP-based service delivery is sufficient reason to replace
some existing service provisioning systems, though many maintain existing systems for
network transport and circuit maintenance.
Once the basic VoIP infrastructure is in place, the customer must install and configure the
access network hardware to provide a VoIP interface for the customers.
65K110FTTP-29A 41
Revision A
Fiber to the Premises Overview - Command Line Interface Overview
1.6 Command Line Interface Overview

This section details the following information:
■ Command Modes
■ CLI Shortcuts
■ CLI Error Messages
■ CLI Input Descriptions
1.6.1 Command Modes

The NetVanta CLI has the following three command modes:
■ Basic
■ Application
■ Enable
Each mode supports a specific set of commands. For example, all interface configuration
commands are accessible only through the Enable mode.
Table 1-3 shows a brief description of each command mode.
Table 1-3. Command Modes
Mode Access by... Prompt Use this mode to...
Basic Beginning a session > ■ Display system information

■ Show status or statistics
Enable Entering Enable mode while in # ■ Manage running configurations

the Basic mode as follows: ■ Enter configuration modes
>enable ■ View security settings
Application Performing a common func- # ■ Copy system provisioning

tion with a reduced set of com- ■ Execute standard test
mands procedures
42 65K110FTTP-29A
Revision A
1.6.2 CLI Shortcuts

Use the CLI shortcuts to help configure the product. Table 1-4 provides a list of CLI shortcuts.
Table 1-4. CLI Shortcuts
Shortcut Description
Up arrow or CTRL + P Use the up arrow to re-display a previously entered command. The up
arrow can cycle through all commands entered starting with the most
recent command.
TAB After entering a partial, but unique, command, press the TAB to complete
the command. The command displays on the command prompt and waits
for input.
? Use the ? for any of the following:

■ Display a list of all subcommands in the current mode.
■ Display a list of available commands beginning with certain letter(s).
■ Obtain syntax help for a specific command by entering the command,
a space, and then a question mark (?). The CLI displays the range of
values and a brief description of the next parameter expected for that
particular command.
CTRL + A Use CTRL + A to jump to the beginning of the displayed command line.
CTRL + E Use CTRL + E to jump to the end of the displayed command line.
CTRL + U Use CTRL + U to clear the current displayed command line.
Auto finish Enter enough letters to identify a command as unique. For example,
entering int eth 1 at the Global Configuration prompt provides access
to the configuration parameters for the specified Ethernet interface.
65K110FTTP-29A 43
Revision A
1.6.3 CLI Error Messages

Table 1-5 lists and defines some of the more common error messages given in the CLI.
Table 1-5. Error Messages
Message Helpful Hints
%Ambiguous command This message occurs when multiple commands can be derived
from the input. Try using the “?” command to determine the error.
Refer to Section 1.6.2, “CLI Shortcuts” on page 43 for more infor-
mation.
%Unrecognized command This message occurs when a single command is entered that
fails to match any supported commands. Try using the “?” com-
mand to determine the error. Refer to Section 1.6.2, “CLI Short-
cuts” on page 43 for more information.
%Invalid or incomplete command This message occurs when the command is not properly fin-
ished. Try using the “?” command to determine the error. Refer to
Section 1.6.2, “CLI Shortcuts” on page 43 for more information.
%Invalid input detected at “^” The error in command entry is located where the caret (^) mark
marker appears. Enter a question mark at the prompt. The system dis-
plays a list of applicable commands or gives syntax information
for the entry.
44 65K110FTTP-29A
Revision A
1.6.4 CLI Input Descriptions

Table 1-6 lists and defines the inputs used throughout the CLI.
Table 1-6. Input Descriptions
Input Syntax Input Example Description
<x-y> -2-4000 Use this input to enter a range by entering the x and y
variables. The x and y variables are numeric and can
be negative.
<x-n> 1-n Use this input to enter an infinite range by entering the
x variable. The x variable is numeric and can be nega-
tive.
<x> 0 Use this input to enter a single number.
<x,y-z,a> -1,4-10,20-22 Use this input to enter a comma delimited numeric list
without spaces. This input can include ranges.
<HH:MM:SS> 12:30:01 Use this input to enter the time in hour-minute-second

format.
<HH:MM> 12:30 Use this input to enter the time in hour-minute format.
MONTH MAR Use this input to enter the month. Use the full month
name or the 3-letter abbreviation. This input is not
case sensitive.
HHH 010 Use this input to enter a numeric hex. The number of
“H”s designates the number of hex digits allowed.
WORD MAP_1 Use this input to enter a string without spaces. This
input is case sensitive.
LINE MAP 2 Use this input to enter a string allowing spaces. This
input is case sensitive.
LIST 1,3-7,9,10 Use this input to enter a comma delimited numeric list
without spaces. This input can include ranges.
<character> A Use this input to enter any single alpha character.
A.B.C.D Use this input to enter an IP address.
xx:xx:xx:xx:xx:xx Use this input to enter a MAC address.
<shelf/slot/port> 1/1/1 Use this input to enter the shelf, slot, and port.
<shelf/slot/port:channel> 1/1/1:1 Use this input to enter the shelf, slot, port and channel.
<shelf/slot/WORD> 1/1/MAP Use this input to enter the shelf, slot, and WORD.
<shelf/slot> 1/S Use this input to enter the shelf and slot.
<shelf/WORD> 1/DEFAULT Use this input to enter the shelf and WORD.
<shelf> 1 Use this input to enter the shelf number. Only shelf 1 is
supported.
65K110FTTP-29A 45
Revision A
Table 1-6. Input Descriptions (Continued)
Input Syntax Input Example Description
<slot/port> 1/1 Use this input to enter the slot and port.
<slot> 1 Use this input to enter the slot. Valid inputs are 0 - 22
for module slots, A for SM A, B for SM B, S for the
SCU, and F for the fan module.
<port> 1 Use this input to enter the port number.
46 65K110FTTP-29A
Revision A
Fiber to the Premises Overview - User Interface
1.6.5 CLI Login

Access the management and provisioning features for the NetVanta products by CLI using a
standard DB-9 serial cable to connect to the console port located on the unit. Also, access the
CLI through Telnet.
To establish CLI communication with the product, perform the following steps:
1. Connect to the craft interface using a VT100 terminal or PC with VT100 emulation soft-
ware configured with the following parameters:
■ Any of the following baud rates: 9600, 19200, 38400, 57600, or 115200
■ 8 data bits
■ No parity
■ 1 stop bit
■ No flow control
2. Once connected, press ENTER several times to access the CLI.
1.7 User Interface

The NetVanta User Interface requires a web browser. Complete the following steps to log in to
the system.
To access the Web GUI, complete the following steps:
1. Enter the NetVanta IP Address in the Address Bar of the web browser, and then press
ENTER.
The NetVanta Logon screen appears, as illustrated in Figure 1-11.
Figure 1-11. Total Access 5000 Logon Screen
65K110FTTP-29A 47
Revision A
Fiber to the Premises Overview - User Interface
g NOTE
Because this document supports both the Total Access 5000 and 5006 systems, the
screen headings may display Total Access 5000 or Total Access 5006 depending on the
system in use.
2. In the Username: field, enter the username.

3. In the Password: field, enter the password.
g NOTE
The default username and password for the system are ADMIN and PASSWORD. The
username and password fields are case sensitive.
4. Click Login or press ENTER.

If the username and password are valid, the User Statistics dialog box appears as
illustrated in Figure 1-12.
Figure 1-12. User Statistics Dialog Box
5. Click OK to continue.
6. The NetVanta User Interface appears starting with the System Status Screen.
48 65K110FTTP-29A
Revision A
GPON Provisioning using CLI - Scope of this Section
2 GPON Provisioning using CLI
2.1 Scope of this Section

This section provides the minimum amount of steps required to provision a GPON module for
the FTTP application using CLI.
gThe NOTE
provisioning instructions and examples in this guide represent general use cases; they do
2.2 In this Section

2.3 Provisioning 50
65K110FTTP-29A 49
Revision A
GPON Provisioning using CLI - Provisioning
2.3 Provisioning
Provisioning is a two-step process.
First, the OLT/PON needs to be provisioned. Then the Service State for each needs to be
assigned. Complete the following when deploying an FTTP application using the CLI.
■ “OLT/PON Provisioning” below
■ “Service Provisioning” on page 62
2.3.1 OLT/PON Provisioning

Before you can being provisioning services, it is first necessary to enable the OLT and PON
along with discovering the ONT you will be provisioning for services.
2.3.1.1 Enable the OLT Module

For services to flow properly, it is necessary to ensure the OLT module is set to In Service. To
enable the OLT module, complete the following steps:
1. Access the Global Configuration Command Set.
ChassisID#configure terminal
2. Enable the GPON OLT module.
ChassisID(config)#no slot shutdown <shelf/slot>
2.3.1.2 Provision the PON

For services to flow properly, it is necessary to ensure the selected PON is set to In Service. It
is at this stage that you will also need to choose the Activation Method of the ONT. To enable
the PON, complete the following steps:
gThisNOTE
is a general set of instructions to provision the PON. Optional settings are available. For
additional information on these optional settings refer to the applicable documents listed in
“Hazard and Advisory Symbols” on page 23.
1. Access the GPON interface.

ChassisID(config)#interface gpon <shelf/slot/port>
2. Set the activation mode.
Refer to Table 2-2 on page 51 for a list of the Activation Modes.
gNotate
NOTE
the Activation Mode for each provisioned PON. This information will be used later when
discovering the ONT.
The default mode is Auto-Discovery. For more details about the available modes, refer to
Table 2-2 on page 51.
gRegistration
NOTE
ID, for the ADTRAN 424RG, is performed by Serial Number Activation. This
occurs when the ONT is “Discovered” by the OLT. If AOE Auto Upgrade is active, a new ONT
installation will be detected and a fast blinking FIBER LED will indicate a new software
download has commenced. This may take 5 - 10 minutes to complete.
50 65K110FTTP-29A
Revision A
Table 2-2. Activation Mode
Activation Mode Command
Auto Activate ChassisID(config-gpon x/x/x)#activation-mode auto-activate
Auto Discover ChassisID(config-gpon x/x/x)#activation-mode auto-discover
Manual ChassisID(config-gpon x/x/x)#activation-mode manual
Registration ChassisID(config-gpon x/x/x)#activation-mode registration [lock-

serial-number|unlock-serial-number]
gFor the
NOTE
differences on Lock Serial Number and Unlock Serial Number, refer to Section 13,
“Activation Mode” on page 391.
3. Select a range indication for the PON.

■ Standard is the default range.
■ For Total Access 5000 System Release 7.1 and above, the GPON 4X SFP OLT
(P/N 1187502F1) supports up to 64 ONTs per PON. The GPON 2.5G 2-Port Access
Module (P/N 1187500E1) and GPON 2.5G 2X SFP Access Module (P/N 1187501G1)
support up to 32 ONTs per PON. For the GPON 4X SFP OLT, the range is reduced by
approximately 10km, when the 64 ONT split is used. The GPON OLT 8X SFP
(P/N 1187503F1) supports up to 64 ONTs per PON.
■ Maximum range is not supported for the GPON OLT 8X SFP (P/N 1187503F1).
ChassisID(config-gpon x/x/x)#range [extended|maximum|standard]
Refer to Table 2-3 for range descriptions.
Table 2-3. Range Description
Range Description
extended Extended range is 34/37.5km.
maximum Maximum range is 60km.
standard Standard range is 20km.
4. Set the S-tag for the subtended host.
gThisNOTE
step requires an EVC to be configured that matches the provisioned S-tag. ADTRAN
recommends the EVC be configured for MAC-Switched mode, instead of Tag-Switched mode.
ChassisID(config-gpon x/x/x)#subtended-host <ont-id> s-tag <2-4094>

5. Set the S-tag priority for the subtended host.
ChassisID(config-gpon x/x/x)#subtended-host <ont-id> s-tag-priority
<0-7>
6. Select the method of inband management.
Refer to Table 2-4 on page 52 for the inband management options.
65K110FTTP-29A 51
Revision A
Table 2-4. Inband Management
Inband Command Description
Static ChassisID(config-gpon x/x/x)#subtended-host Set the static IP address and

IP <ont-id> ip address a.b.c.d a.b.c.d subnet mask for the ONT’s
inband management.
If selected, continue to step 7.
DHCP ChassisID(config-gpon x/x/x)#subtended-host Allocate the IP address for the

IP <ont-id> ip address dhcp ONT’s inband management
dynamically using DHCP.
If selected, continue to step 8.
7. If using a static IP address, set the default gateway for the subtended-host.
ChassisID(config-gpon x/x/x)#subtended-host <ont-id> ip default-gateway
A.B.C.D
8. Enable or disable Forward Error Correction (FEC) for downstream traffic toward the
customer ONT.
FEC helps eliminate packet loss by providing redundancy in the signal. If downstream
FEC is enabled, the ONT that supports FEC decoding capability should apply FEC
decoding and error-correction to the downstream data flow. The ONT that does not
support FEC decoding skips the parity bytes and does not apply FEC decoding and error-
correction to the downstream data flow. To disable, use the no form of this command.
ChassisID(config-gpon x/x/x)#downstream fec enable
■ FEC decoding does not attempt to correct any transmission errors.
■ The activation and deactivation of FEC operates regardless of port status. The
behavior during switch-over is undefined and is likely to cause a momentary loss of
data.
9. Enable or disable FEC for upstream traffic toward the OLT. To disable, use the no form of
this command.
ChassisID(config-gpon x/x/x)#upstream fec enable
■ The ONT may or may not support the capability to apply FEC encoding to the
upstream data.
■ Enabling upstream FEC adds more overhead on the PON channel due to the
addition of parity bytes and reduces the total combined fixed and assured rates per
PON by rough 6%.
10. Enable the interface.
ChassisID(config-gpon x/x/x)#no shutdown
11. If using DHCP address, view the DHCP address for a GPON subtended-host.
ChassisID(config-gpon x/x/x)#do show interfaces gpon <shelf/slot/pon>
subtended-host
What’s Next
■ For Registration-ID activation, continue to Section 2.3.1.3, “Enter the Registration-
ID” on page 53.
■ For all other activation modes, continue to Section 2.3.1.4, “Discover the ONT” on
page 61.
52 65K110FTTP-29A
Revision A
2.3.1.3 Enter the Registration-ID
! Do not
CAUTION!
duplicate the same Registration-ID to two different ONTs to be activated on the OLT.
As an example, ONT A has S/N S1 and Registration-ID R1 and is UP; another ONT B, has S/
N S2 and Registration-ID R2. ONT B becomes faulty and needs replacement. When the
technician removes ONT B and adds a new ONT in place of B with a Registration-ID R1, ONT
B would not come UP and cause a duplicate Registration-ID error at the OLT. If the technician
did not resolve the duplicate Registration-ID and leave the ONT connected, ONT A would still
be UP and running. After an OLT reboot, there is a chance that the ONT replaced at B would
get the service of ONT A.
The registration-ID steps vary depending on your ONT. Use Table 2-5 to navigate to your next
step.
Table 2-5. Registration-ID
Registration-ID Procedure See Page
Section 2.3.1.3.1, “Registration-ID Entry for Total Access 3xx” 53
Registration-ID Entry for Total Access 421x /Total Access 421xw 55
Registration-ID Entry for Total Access 3xx Residential Gateway 57
Registration-ID Entry for Total Access 324RG and 334RG 58
Registration-ID Entry for Total Access 324 3rd Generation and Total Access 374 59
Registration-ID Entry for Total Access 4xx 60
2.3.1.3.1 Registration-ID Entry for Total Access 3xx

To enter a Registration-ID to the ONT, complete the following steps:
1. Power down the ONT (if powered on).
2. If necessary, disconnect the subscriber POTS wiring.
3. Connect DTMF phone to one of the POTS jacks.
4. Power on the ONT and wait until the unit is ready to accept the Registration-ID. ONT
status indications are provided in Table 2-6.
Table 2-6. ONT Status
Status LED Status
Unit is booting up Flashing green, then solid yellow
Unit has booted Off for the initial LED status
Unit is ready to accept the Registration-ID Flashing red and green quickly
5. Within 10 seconds, lift up phone receiver and listen. A dial tone should be heard.
gIf theNOTE
Registration-ID is not entered within 300 seconds, hang up and return to step 1.
65K110FTTP-29A 53
Revision A
6. Enter: *001234*XXXXXXXXXX*XXXXXXXXXX* (where XXXXXXXXXX is the

Registration-ID for this site).
7. Wait for verification that the ONT understood and accepted the Registration-ID as
indicated by the ONT LEDs listed in Table 2-7.
Table 2-7. Registration-ID Acceptance
Status Description
Success If verification succeeds, the following attributes

apply:
■ LED: Flashing green
■ Tone: Stutter dialtone
■ Caller-ID: **Accepted** and echoing the
Registration-ID
Failure If verification fails, the following attributes apply:

■ LED: Flashing red
■ Tone: Fast busy
■ Caller-ID: If the pattern is entered incorrectly,
**Invalid** appears. If the first ID does not match
the second, **Re-enter** appears
If a failure occurs, hang up and return to step 5.
8. Hang up phone.
9. Wait for validation of the Registration-ID as indicated by the ONT LEDs listed in
Table 2-8.
Table 2-8. Registration-ID Status
Status LED Description
Discovery (validation pending) Flashing yellow
Success Solid green
Failure Solid red
Dark Fiber Off
10. If success, registration is complete. Disconnect phone & connect house wiring.
11. If error, return to Step 1.
What’s Next
Continue to Section 2.3.1.4, “Discover the ONT” on page 61.
54 65K110FTTP-29A
Revision A
2.3.1.3.2 Registration-ID Entry for Total Access 421x /Total Access 421xw
To enter a Registration-ID to the SFU ONT (Total Access 421x or Total Access 421xw),
complete the following steps:
1. Power down ONT (if powered on), and disconnect the fiber.
2. If necessary, disconnect house POTS wiring.
4. Power on the ONT and wait for the ONT to come up within 2 minutes.
5. Perform a 10 second reset on the ONT by pushing the reset button.
6. Wait for the OMCI LED to start flashing.
7. Wait for the OMCI LED to stop flashing, and the SYS LED will come on solid.
8. Once the SYS LED is on solid, wait 40-45 seconds for the POTS LED to start flashing.
9. Take the butt set off-hook. For activating the prompt tone for Registration-ID, dial ‘*0’. A
continuous prompt tone of 450 Hz should be heard.
gIf theNOTE
Registration-ID is not entered within 300 seconds, hang up and return to step 1.
10. After the prompt tone, dial the Registration-ID value.

a. Dial the 10 digit number with # at the end to indicate the end of the input string.
Digits in the range of 0 to 9 are accepted.
b. Enter the identical Registration-ID again and press # (as seen in the previous step).
11. If time out tone is played, re-enter the Registration-ID by placing the phone on-hook.
Again take the phone off-hook and repeat step 7.
12. If Error-tone is played, the input Registration-ID is not accepted. Re-enter the
Registration-ID by placing the phone on-hook. Again take the phone off-hook and repeat
step 9.
13. If OK tone is played, continuously with small intervals of approximately 2 to 4 seconds,
the Registration-ID is accepted. Place the phone on-hook, connect fiber and reboot the
ONT.
14. If the Registration-ID entered on the ONT matches the Registration-ID provisioned on the
OLT, the ONT will successfully be registered with the OLT. The NTWK on the ONT will be
ON at the end of the process. Refer to Table 2-9 on page 56 for a list of LEDs.
If the Registration-ID entered on the ONT does not match the Registration-ID provisioned
on the OLT, the SYS LED will keep blinking during the ONT boot-up to indicate the ONT is
trying to register itself but cannot complete the process successfully. Refer to Table 2-9
on page 56 for a list of LEDs.
65K110FTTP-29A 55
Revision A
2.3.1.3.3 Total Access 421x/Total Access 421xw LEDs

The ONT provides front panel LEDs to display status information. The ONT LEDs and status
descriptions are shown in Table 2-9.
Table 2-9. Front Panel LEDs
Label Status Description
POWER  Off No power

 Green Power is On
BATT  Off No battery power

 Green Battery installed and charged
 Green Flashing Battery charging, or operating in depleted condition
SYS  Off Power on, fully functional and ranged and/or

synchronized
 Green Hardware is 100% operational
 Green Flashing PON is in ranging and synchronizing mode
 Red System failed to boot
DATA  Off No data on Ethernet port

 Green Data being processed on Ethernet port
NTWK  Off No data being passed

 Green Link between Network and ONT established
OMCI  Off Dark Fiber

 Green Ranged, Synchronized, and Up on the PON
 Green Flashing Communicating with OLT and Ranging
POTS  Off Telephone is on hook

1/2
 Green At lease one port is Off Hook
 Green Flashing At least one port off-hook for one-hour or more
LINK/  Off Ethernet port not active

CARRIER
 Green Connection between ONT and CPE router established
 Green Flashing Traffic on Ethernet port
10/100  Off Ethernet rate up to 10Mbps

 Green Ethernet rate up to 100mbps
 Green Flashing Ethernet rate up to 1000Mbps
What’s Next
56 65K110FTTP-29A
Revision A
2.3.1.3.4 Registration-ID Entry for Total Access 3xx Residential Gateway

To set the Registration ID using a DTMF Keypad on a standard telco Butt Set, complete the
following steps:
1. Verify the PON fiber-feed is disconnected from the ONT.
2. Press the RESET button on a previously powered-up ONT, or perform an initial power-up
on a new ONT.
3. Wait approximately one minute for the start-up to complete, (PWR LED is ON and solid;
LOS LED is ON and solid).
4. Attach the Butt Set to the POTS Port 1 and go off-hook.

5. Observe that the reorder tone (fast busy) is generated.
gThe NOTE
Reorder tone is continuously played after going off-hook until the valid Registration ID
password is dialed. See Step 6.
6. On the keypad, dial the registration ID password: *123#.

7. Observe that the special information tone is generated.
gThisNOTE
is a fast “Hi-Mid--Low” tone that repeats.
8. On the keypad, press * to initiate the Registration ID input sequence.

9. Observe that the special information tone stops.
10. Dial the remainder of the Registration ID sequence: 10 digit plus #.
gIf theNOTE
Registration ID entered is not valid, the Special Information tone will be re-played. An
incorrect Registration ID can be changed by re-entering the Registration ID password (*123#)
and then re-entering a correct Registration ID sequence.
11. Wait 2 seconds. A confirmation tone is generated by the Butt Test Set. This indicates a
valid Registration ID was entered.
12. Hang-up the Butt Set.
13. Push the RESET button, or power-cycle the ONT.
14. Connect the fiber between the PON and ONT.
15. The ONT should begin Ranging with the new Registration ID. The PON LED will blink
during Ranging. The PON LED will become solid after 20-30 seconds. This indicates the
ONT has activated.
16. Once the ONT has Ranged on the PON, the Butt Set Registration ID process is disabled.
gIf AOENOTE
Auto Upgrade is active, a new ONT installation will be detected and a fast blinking PON
LED will indicate a new software download has commenced. This may take 5 - 10 minutes to
complete.
What’s Next
65K110FTTP-29A 57
Revision A
2.3.1.3.5 Registration-ID Entry for Total Access 324RG and 334RG

following steps:
2. If necessary, disconnect house POTS wiring.
3. Connect DTMF phone to the first POTS port.
4. Power on the ONT and wait for the ONT to come up. ONT comes up in 25 seconds.
5. Perform 10 sec reset on the ONT by pushing the reset button.
6. Wait 40-45 seconds for the POTS LED to start flashing.
7. Able to get prompt tone even after 300 seconds by dialing '*0'.
8. Take the butt set off-hook. For activating the prompt tone for the Registration-ID, dial '*0'.
A continuous prompt tone of 450 Hz should be heard.
b. Enter the identical Registration-ID again and press # (as performed in the previous
step).
Again take the phone off-hook and repeat step7.
Registration-ID by placing the phone on-hook. Again take the phone off-hook and
repeating step 8.
12. If OK tone is played, continuously with small intervals (approximately 2 to 4 seconds),
then Registration-ID is accepted. Place the phone on-hook, connect fiber and reboot the
ONT.
OLT, the ONT will successfully be registered with the OLT.
What’s Next
58 65K110FTTP-29A
Revision A
Access 374
1. Verify the ONT is DISCONNECTED from the PON and reset or power-up the unit.
2. Wait approximately 1 minute for start-up to complete. The LEDs will provide the following
indications:
■ Total Access 374
♦ PWR LED illuminated, solid
♦ FAIL LED illuminated, solid
■ Total Access 324 3rd Generation
♦ LOS LED illuminated, solid
3. Attach the Butt Set or DTMF phone to POTS port #1 and go off-hook.
4. Verify that reorder tone (fast busy) is present.
5. Dial the registration ID entry code - *123#.
6. A special information tone will be played to indicate the ONT is ready to accept the
registration ID.
7. Enter an asterisk (*), wait for the tone to stop, then enter the 10 digit registration ID, then
press on the pound key (#).
8. You should now hear three tones, indicating its OK to hang up the phone/butt set.
9. Reset the ONT, and connect to the PON. Once ONT activation is successful, the MGT,
NET, and PWR LEDs should all illuminate green.
Guidelines
Use the following guidelines when provisioning Registration-ID:
■ Fast busy is continuously played until the asterisk (*) key is pressed.
■ If the registration ID is not valid, the special information tone will be played.
■ After entering *123#, the registration ID sequence can be entered (*10-digits#) and
changed by re-entering a new registration ID sequence as many times as necessary. The
confirmation tone is played each time a valid registration ID sequence is entered.
■ Once the ONT is ranged, the registration ID process is disables.
What’s Next
65K110FTTP-29A 59
Revision A
gThisNOTE
procedure is not applicable to the following Total Access 4xx products:
Total Access 421x/421xw and the Total Access 400.
1. Plug in both power and fiber to the ONT and allow the ONT to “range.” This process will
take several seconds. The LEDs will indicate that the process is complete.
2. Connect an RJ-45 Ethernet cable from a laptop PC to the Ethernet LAN interface on the
401 ONT. See Figure 2-1 for the location of the LAN interface.
3. Open a web browser on the laptop.
4. Enter the IP address 192.168.1.1 in the address window. A popup window appears that
requests user name and password.
5. Enter the use name and password, as follows:
■ User name: admin
■ Password: admin
The web GUI screen appears in your web browser (see Figure 2-1).
Figure 2-1. 401 Web GUI Display
6. Navigate to Management>SLID Configuration (see the menu tree in Figure 2-1).

7. Enter the Reg ID in the box labeled “Input New SLID.” Press <SAVE>.
8. Reboot the ONT using the option in the web GUI.
This applies the configuration.
What’s Next
60 65K110FTTP-29A
Revision A
2.3.1.4 Discover the ONT

To discover the ONT, complete the following steps:
1. Access the remote device.
ChassisID(config)#remote-device ont <ont-id>@<shelf/slot/port>
2. Discover the ONT.
Refer to Table 2-10 for the selected activation method.
Table 2-10. Discover the ONT
Manual or ChassisID(config-ont ont-id@x/x/x)#serial-number line

Auto-Discovery Substitute LINE with the ONT serial number. Example ADTN12345678.
Auto-Activate N/A
Registration-ID ChassisID(config-ont ont-id@x/x/x)registration-id <number 10>

Lock-SN or The Registration-ID requires a 10 digit number to match the Registration-ID
Registration-ID programmed into the ONT by the installer. If using the NG-PON2 4x10/10GigE
Unlock-SN OLT (P/N 1187514F1), the Registration-ID can be more than 10 digits and may
contain alphanumeric characters.
3. Enable the ONT interface.

ChassisID(config-ont ont-id@x/x/x)#no shutdown
4. Return to the Global Configuration Command Set.
ChassisID(config-ont ont-id@x/x/x)#exit
65K110FTTP-29A 61
Revision A
2.3.2 Service Provisioning

The Total Access 5000 FTTP application supports triple-play provisioning via Web GUI. To
begin provisioning services, choose one of the following paths:
■ Section 2.3.2.1, “Voice” below
■ Section 2.3.2.2, “Data” on page 66
■ Section 2.3.2.3, “Video” on page 66
■ Section 2.3.2.4, “RF-Video” on page 66
■ Section 2.3.2.5, “Transport Layer Security (TLS)” on page 66
2.3.2.1 Voice
The Total Access 5000 FTTP application supports Session Initiation Protocol (SIP), Media
Gateway Control Protocol (MGCP), and GR-303 voice.
2.3.2.1.1 SIP
SIP works in concert with voice and video by enabling and agreeing on characterizations of a
session for sharing data. SIP is an application-layer control protocol that can establish, modify,
and terminate multimedia sessions.
SIP provides two options. The first is provided in the Voice menu found under the Services
option. For purposes of this document, this option is referred to as Non-OMCI. The second
option is provided in the Voice FTTx menu found under the Services option. For purposes of
this document, this option is referred to as OMCI.
gIf yourNOTE
deployment uses a Remote Gateway ONT, OMCI (Voice FTTx) is the only supported
option.
2.3.2.1.2 MGCP
MGCP is a protocol that works hand-in-hand with H.323 and SIP in VoIP services. MGCP
works between a call agent or media gateway controller, usually a software switch, and a
media gateway with internal endpoints. The media gateway is the network device that
converts voice signals carried by telephone lines into data packets carried over the Internet or
other packet networks.
MGCP provides two options. The first is provided in the Voice menu found under the Services
gIf yourNOTE
deployment uses a Remote Gateway ONT, OMCI (Voice FTTx) is the only supported
option.
2.3.2.1.3 GR-303
GR-303 is the basic protocol used for POTS service.
62 65K110FTTP-29A
Revision A
gA Total
NOTE
Access 5000 Voice Gateway Module is required when provisioning GR-303.
2.3.2.1.4 Select Your Voice Option

Use Table 2-11 to determine your voice option and navigate to your next step. If you’re unsure
of your voice option, refer to “Voice” on page 62.
Table 2-11. Voice Options
Option See Page
SIP OMCI Voice 63
SIP Non-OMCI Voice 64
MGCP OMCI Voice 64
MGCP Non-OMCI Voice 65
GR-303 Voice 65
2.3.2.1.5 SIP OMCI Voice

To provision for SIP OMCI voice, complete the following steps:
gThisNOTE
is a general set of instructions to turn up SIP OMCI voice. Optional settings are available.
For additional information on these optional settings refer to the applicable documents listed in
“Hazard and Advisory Symbols” on page 23
1. Section 2.3.3, “Create an EVC” on page 68

2. Section 2.3.4, “Set the Voice Service Mode on the ONT” on page 73
3. Section 2.3.5, “Provision the Port on the ONT” on page 74
4. Section 2.3.6, “Create an IP Host” on page 82
5. Section 2.3.7, “Create an EVC-Map” on page 83
6. Section 2.3.8, “Provision the SIP Trunk” on page 93
7. Section 2.3.11, “Provision the SIP Dialing Profile” on page 98
8. Section 2.3.18, “Provision the OMCI SIP Users” on page 111
65K110FTTP-29A 63
Revision A
2.3.2.1.6 SIP Non-OMCI Voice

gThisNOTE
is a general set of instructions to turn up SIP Non-OMCI voice. Optional settings are
available. For additional information on these optional settings refer to the applicable
documents listed in “Hazard and Advisory Symbols” on page 23.

8. Section 2.3.12, “Provision Class of Service (CoS) (Optional)” on page 104
9. Section 2.3.13, “Provision for Global Voice (Optional)” on page 105
10. Section 2.3.14, “Provision the Voice User” on page 106
2.3.2.1.7 MGCP OMCI Voice

gThisNOTE
is a general set of instructions to turn up MGCP OMCI voice. Optional settings are

6. Section 2.3.9, “Provision the MGCP Profile” on page 95
7. Section 2.3.19, “Provision OMCI MGCP Endpoints” on page 113
64 65K110FTTP-29A
Revision A
2.3.2.1.8 MGCP Non-OMCI Voice

gThisNOTE
is a general set of instructions to turn up MGCP Non-OMCI voice. Optional settings are

7. Section 2.3.10, “Provision Non-OMCI MGCP Endpoints” on page 96
2.3.2.1.9 GR-303 Voice

To provision for GR-303 voice, complete the following steps:
gThisNOTE
is a general set of instructions to turn up GR-303 voice. Optional settings are available.
3. Section 2.3.20, “Provision GR-303” on page 114
65K110FTTP-29A 65
Revision A
2.3.2.2 Data
To provision for data, complete the following steps:
gThisNOTE
is a general set of instructions to turn up data. Optional settings are available. For

2.3.2.3 Video
To provision for video, complete the following:
gThisNOTE
is a general set of instructions to turn up video. Optional settings are available. For

2.3.2.4 RF-Video
To provision for RF-Video, complete the following:
gThisNOTE
is a general set of instructions to turn up RF-video. Optional settings are available. For
additional information refer to the applicable documents listed in “Hazard and Advisory
Symbols” on page 23.
2.3.2.5 Transport Layer Security (TLS)

Transport Layer Security (TLS) enables the user to tag-switch through the system. The user
can send traffic without MAC Security or MAC Limits. Proxy ARP will be disabled as well, so
the devices will respond with their own ARP. Using TLS removes the ability to use IGMP repli-
cation on this particular port. Since the flow will be tag switched up to the network, the VLANs
must be configured in a way that an outer VLAN appears only on a single access module
within the entire system. The inner tag (if running double tags) cannot be duplicated within the
access module. If the VLAN becomes MAC-switched, TLS no longer functions.
66 65K110FTTP-29A
Revision A
Refer to Table 2-12 for an available list of TLS options.
Table 2-12. EVC and TLS
Mac-Switched No Mac-Switched
Double-Tag Not Supported Double tagged TLS, N end points, S-

tag must be unique within the entire
Total Access 5000 Network. C-tag
must be unique per port
Single-Tag Not Supported E-Line (TLS), Max of 2 endpoints,

including men-port
2.3.2.5.1 Select Your TLS Option

Use Table 2-13 to determine your TLS option and navigate to your next step.
Option See Page
TLS Single Tag Configuration 67
TLS Double Tag Configuration 67
2.3.2.5.2 TLS Single Tag Configuration

To provision TLS Single Tag, complete the following:
gThisNOTE
is a general set of instructions to turn up TLS. Optional settings are available. For

2.3.2.5.3 TLS Double Tag Configuration

To provision TLS Double Tag, complete the following:
gThisNOTE
is a general set of instructions to turn up TLS. Optional settings are available. For

65K110FTTP-29A 67
Revision A
2.3.3 Create an EVC

The EVC (Ethernet Virtual Connection) is a centrally managed object defining the properties of
a particular S-Tag within a Total Access 5000. The EVC object enables the provisioning of
ELINE, E-TREE, and E-LAN applications. EVCs are available for use by all access modules
within a shelf.
In a system using an S-VLAN model, each user requires a unique S-VLAN to be tag switched
throughout the system. ONTs 1-64 on slot 1 must have different VLANs than users 1-64 on
Slot 2.
support up to 32 ONTs per PON.
■ VLANs cannot be duplicated across other nodes.
gThe NOTE
EVC for SIP/MGCP traffic will be a dedicated EVC because voice traffic requires different
Quality of Service (QoS) handling than other data traffic.
■ Changing the default IGMP EVC means also changing the default IP IGMP EVC
statement for each access module.
■ When deleting the default IGMP EVC (IGMP_EVC), ensure that all IGMP-enabled maps
associated with the IGMP EVC are disabled as well.
■ EVC names are case sensitive.
■ A default IGMP EVC (IGMP_EVC) is included in the factory default settings, it can be
modified and used or deleted.

2. Access the EVC Interface Configuration Command Set.
ChassisID(config)#evc WORD
3. Set the S-tag for the EVC.
ChassisID(config-evc name)#s-tag <1-4094>
4. Apply this EVC to the default ethernet interface as a MEN port.
ChassisID(config-evc name)#connect men-port default-ethernet
The default interface is set in the Switch Module provisioning.
The commands listed in Table 2-14 on page 69 can be used to provision the EVC to use
a non-default Metro Ethernet Network Interface.
68 65K110FTTP-29A
Revision A
Table 2-14. Non-Default Metro Ethernet Network Interface
Interface Command
EFM group ChassisID(config-evc name)#connect men-port efm-group

[<shelf/slot/group>|WORD]
Ten Gigabit- ChassisID(config-evc name)#connect men-port ten-gigabit-
Ethernet ethernet <shelf/slot/group>
Gigabit-Ethernet ChassisID(config-evc name)#connect men-port gigabit-
ethernet <shelf/slot/group>
LAG group ChassisID(config-evc name)#connect men-port lag-group
<shelf/slot/group>
5. Depending on your selected service, enable or disable MAC-Switching.

The commands listed in Table 2-15 can be used to enable or disable MAC-Switching.
Table 2-15. MAC-Switching
Service Command Definition
Voice/Video/Data ChassisID(config-evc name)#mac-switched Enabled
Single/Double Tag TLS ChassisID(config-evc name)#no mac- Disabled

switched
6. If provisioning Single Tag TLS, continue to step 12. If provisioning for Double Tag TLS,
continue to step 7. For all other services, continue to step 9.
7. Enable double-tag-switching.
ChassisID(config-evc name)#double-tag-switched
8. If provisioning Double Tag TLS, continue to step 12. For all other services, continue to
step 9.
9. Configure the unit to strip the CE-VLAN tag as it is mapped to the EVC in the customer-
to-network direction.
ChassisID(config-evc name)#no preserve-ce-vlan
10. If provisioning for voice or data, skip to step 12. If provisioning for video, set a priority
value for the IGMP packets.
ChassisID(config-evc name)#subscriber igmp priority <0-7>
11. Set the IGMP version.
V2 is IGMPv2 (RFC 2236). V3 Lite is Lightweight IGMPv3 (RFC 5790).
ChassisID(config-evc name)#ip igmp version [v2|v3 lite]
12. Enable the EVC.
ChassisID(config-evc name)#no shutdown
ChassisID(config-evc name)#exit
65K110FTTP-29A 69
Revision A
If currently provisioning for video, continue to step 11. If currently provisioning for voice or
data, skip to What’s Next.
14. Set the IGMP mode for the GigE SM/access module.
Refer to Table 2-16 for a list of available subscriber modes.
Table 2-16. Subscriber Modes
Mode Steps
Proxy IGMP proxy can be broken down into three functions:

■ Report suppression - Intercepts, absorbs, and summarizes IGMP reports
coming from IGMP hosts. IGMP reports are relayed upstream only when
necessary, i.e. when the first user joins a multicast group, and once only per
multicast group in response to an IGMP query.
■ Last leave - Intercepts absorbs, and summarizes IGMP leaves coming from
IGMP hosts. IGMP leaves are relayed upstream only when necessary, i.e. when
the last user leaves a multicast group.
■ Query suppression - Intercepts and processes IGMP queries, in such a way that
IGMP specific queries are never sent to client ports, and IGMP general queries
are relayed only to those clients’ ports receiving at least one multicast group.
The OLT offers a unique but necessary capability in this respect. TR-156 requires
that all IGMP queries be sent over the multicast GEM port. However, the common
IGMP processing code of the Total Access 5000 access modules operates per
number of ports (or ONTs). The OLT break this TR-156 requirement by only
forwarding each proxy agent’s query to the intended ONT thereby avoiding an
IGMP query storm from causing set top box problems.
Snooping IGMP snooping is the process of listening to IGMP network traffic. Snooping allows
a network switch to listen in on the IGMP conversation between hosts and routers.
The switch maintains a map of which links need which multicast streams. These
streams can be filtered from the links that do not need them. Snooping allows a
switch to only forward multicast traffic to the links that have solicited them.
Snooping is not a recommended mode for IGMP.
Transparent IGMP transparent passes IGMP messages transparently.
ChassisID(config)#ip igmp evc WORD <shelf/slot> mode

[proxy|snooping|transparent]
gPortsNOTE
can be enabled with either snooping or proxy, with additional maps blocking IGMP.
15. Set the IGMP mode for each access module that will carry IGMP traffic.
gIf IGMP
NOTE
processing is enabled, all IGMP-enabled maps in the GPON OLT Access Module
must have the same setting.

gThe NOTE
IGMP EVC for the OLT Slot will not be running until the EVC-Map is created.
70 65K110FTTP-29A
Revision A
16. Repeat step 14 - 15 for each access module that will carry IGMP traffic.
17. If the IGMP mode is set to proxy, complete the following steps:
a. Set the proxy host IP address.
gThe NOTE
default proxy host IP address is 0.0.0.0.
ChassisID(config)#ip igmp evc WORD <shelf/slot> proxy host ip

address A.B.C.D
b. Set the proxy last-member-query interval.
The last-member-query interval controls the time-out (in milliseconds) used to
detect whether any group receivers remain on an interface after a receiver leaves a
group. If a receiver sends a leave-group message, the router sends a group-specific
query on that interface. After twice the time specified by this command plus as much
as one second longer, if no receiver responds, the router removes that interface
from the group and stops sending that group’s multicast packets to the interface.
gThe NOTE
default proxy last-member query interval is 1000.
ChassisID(config)#ip igmp evc WORD <shelf/slot> proxy last-member-

query interval <100-65535>
c. Set the proxy last-member-query count.
The last-member-query count controls the number of times the last-member-query
interval is used.
gThe NOTE
default proxy last-member query count is 2.

query count <1-255>
18. Provision Multicast Content Admission Control (CAC).
The Multicast CAC feature provides the following at a PON-level:
■ A provisionable threshold for a multicast bandwidth threshold crossing alarm (TCA).
If the multicast bandwidth is above this threshold the alarm is set. Once set, the alarm
is cleared when the multicast bandwidth stays below the threshold for at least 5
minutes.
■ A provisionable flag to control whether Multicast CAC is enabled or not. If enabled,
IGMP joins for new multicast groups are disallowed when the multicast bandwidth is
above the threshold.
a. Enable or disable Multicast Content Admission Control (CAC) flag.

ChassisID(config)#multicast-cac enable
gUseNOTE
the no form of this command to disable Multicast CAC.
b. Set the multicast bandwidth threshold for the TCA.

ChassisID(config)#thresholds multicast-bandwidth <0-n>
65K110FTTP-29A 71
Revision A
gUseNOTE
the no form of this command to disable TCA.
The upper limit is technology dependent. If you enter a value that exceeds the upper
limit, an error message will indicate the valid rate.
c. Verify the Mutlicast CAC status.
ChassisID(config)#do show interfaces gpon <shelf/slot/pon>
gpon 1/16/1 is UP and Running
Number of Configured ONTs : <number>
Number of Discovering ONTs : <number>
Number of Unrecognized ONTs : <number>
Number of Operational ONTs : <number>
Number of Available HW Resour : <number>
Longest Fiber Distance : <value>
Shortest Fiber Distance : <value>
Oversubscription Allowed : [true|false]
Multicast CAC Status : [accepting|rejecting|disabled]
Downstream Upstream
Max Provisionable BW kbps : value value
Configured PIR BW kbps : value value
Configured Fixed BW kbps : value value
Configured Assured BW kbps : value value
Available PIR BW kbps : value value
Available CIR BW kbps : value value
Current PIR BW kbps : value value
Current CIR BW kbps : value value
gThe NOTE
Number of Available Hardware Resources field displays the remaining number of
resources available on the PON.
What’s Next
■ For SIP or MGCP provisioning, continue to Section 2.3.4, “Set the Voice Service Mode on
the ONT” on page 73.
■ For video, data, or TLS provisioning, continue to Section 2.3.5, “Provision the Port on the
ONT” on page 74.
72 65K110FTTP-29A
Revision A
2.3.4 Set the Voice Service Mode on the ONT

To set the voice service mode, complete the following steps:
2. Set the voice service mode for the ONT.
SIP ChassisID(config)#voice protocol ont-id@<shelf/slot/port> sip
MGCP ChassisID(config)#voice protocol ont-id@<shelf/slot/port> mgcp
GR-303 ChassisID(config)#voice protocol ont-id@<shelf/slot/port> fxs-

signaling
3. If provisioning OMCI SIP or OMCI MGCP, set the VoIP Config Method.
Remote Gateways require the use of OMCI.
a. Access the remote device.
b. Set the method.
ChassisID(config-remote-device ont x@x/x/x)#voip-config method
[file-retrieval|local-on|omci]
What’s Next
For OMCI SIP, Non-OMCI SIP, OMCI MGCP, Non-OMCI MGCP, or GR-303 provisioning,
continue to Section 2.3.5, “Provision the Port on the ONT” on page 74.
65K110FTTP-29A 73
Revision A
2.3.5 Provision the Port on the ONT
gIf provisioning
NOTE
data and video on the same port, the ONT port only needs to be enabled once.
Select the Port Type. Use Table 2-18 to determine your port type and navigate to your next
step.
Table 2-18. Port Type
Service ONT Type See Page
Data/Video/TLS Non-Remote Gateway Ethernet Below
Remote Gateway Virtual Gigabit Interface 77
GPON MDU VDSL Interface 78
Voice All ONTs FXS 75
RF-Video All ONTs RF-Video 76
2.3.5.1 Ethernet
After selecting Ethernet as the ONT port type, complete the following steps:
1. Access the Ethernet interface of the ONT.
gThe NOTE
eth-port is the Ethernet port number on the ONT, port is the PON port on the OLT to which
the ONT is connected.
ChassisID(config)#interface gigabit-ethernet <ont-id/0/eth-
port>@<shelf/slot/port>
2. Set the number of mac addresses allowed.
■ 16 MAC addresses per ONT are allowed and must be shared by all Ethernet ports on the
ONT.
■ A value of 0 will actually allow up to 128 MAC addresses to be attributed to the ONT.
However, the number of MAC addresses the OLT can support is limited so using more
than 16 will severely limit the number of MAC addresses available to other ONTs. No more
than 16 static addresses can be configured regardless of the number of MAC addresses
allowed by this setting.
■ If the mac address limit is disabled, it opens unlimited mac addresses on the UNI and the
limit is per the hardware resources available.
ChassisID(config-giga-eth x/x/x@x/x/x)#mac limit <1-n>
3. Enable the Ethernet interface of the ONT.
ChassisID(config-giga-eth x/x/x@x/x/x)#no shutdown
ChassisID(config-giga-eth x/x/x@x/x/x)#exit
What’s Next
For video, data, or TLS provisioning, continue to Section 2.3.7, “Create an EVC-Map” on
page 83.
74 65K110FTTP-29A
Revision A
2.3.5.2 FXS
After selecting FXS as the ONT port type, complete the following steps:
1. Access the FXS Interface Configuration Command Set.
ChassisID(config)#interface fxs <ont-id/0/fxs-port>@<shelf/slot/port>
2. Adjust the Tx Gain for the FXS port between -12dB and 6dB.
ChassisID(config-fxs x/x/x@x/x/x)#tx-gain <N.N>
3. Adjust the Rx Gain for the FXS port between -12dB and 6dB.
ChassisID(config-fxs x/x/x@x/x/x)#no shutdown
5. Return to the Global Configuration prompt.
ChassisID(config-fxs x/x/x@x/x/x)#exit
What’s Next
■ For SIP or MGCP provisioning, continue to Section 2.3.6, “Create an IP Host” on page 82.
■ For GR-303 provisioning, continue to Section 2.3.20, “Provision GR-303” on page 114.
65K110FTTP-29A 75
Revision A
2.3.5.3 RF-Video
After selecting RF-Video as the ONT port type, complete the following steps:
1. Access the video port.
ChassisID(config)#interface rf-video <ont-id/0/1>@<shelf/slot/port>
2. Enable the video port.
ChassisID(config-rf-video x/x/x@x/x/x.gpon)#no shutdown
3. Enable video return (SWRD).
ChassisID(config-rf-video x/x/x@x/x/x.gpon)#video-return
ChassisID(config-rf-video x/x/x@x/x/x.gpon)#exit
What’s Next
For RF-Video, this completes provisioning. Services should be up and running. To provision
another service, continue to Section 2.3.2, “Service Provisioning” on page 62.
76 65K110FTTP-29A
Revision A
2.3.5.4 Virtual Gigabit Interface

To provision a virtual gigabit interface, complete the following steps:
1. Access the Virtual Gigabit Ethernet Interface Configuration Command Set.
ChassisID(config)#interface virtual-gigabit-ethernet <ont-id/0/
ChassisID(config-virtualGigabitEthernet x/x/x@x/x/x)#no shutdown
ChassisID(config-virtualGigabitEthernet x/x/x@x/x/x)#exit
What’s Next
page 83.
65K110FTTP-29A 77
Revision A
2.3.5.5 VDSL Interface

To provision the VDSL interface, complete the following:
2. Access the VDSL Interface Configuration Command Set.
ChassisID(config)#interface vdsl <ont-id/0/vdsl-port>@<shelf/slot/
port>.gpon
3. Enter a text description of the interface.
ChassisID(config-vdsl x/x/x@x/x/x)#description LINE
4. Enable the VDSL link up/down alarm.
ChassisID(config-vdsl x/x/x@x/x/x)#alarm enable link-down
5. Set the service mode.
The DSL service mode must be set for each port.
ChassisID(config-vdsl x/x/x@x/x/x)#service-mode vdsl2
6. Configure the minimum and maximum downstream payload rates from the VTU-C to the
VTU-R.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path payload-rate downstream
0 minimum <32-150000> maximum <32-150000>
7. Configure the minimum and maximum upstream payload rates from the VTU-R to the
VTU-C.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path payload-rate upstream 0
minimum <32-96000> maximum <32-96000>
8. Configure the downstream minimum, target, and maximum noise margins the VTU-R
receiver shall tolerate.
ChassisID(config-vdsl x/x/x@x/x/x)#dmt-options snr-margin downstream
margins minimum <0.0-31.0> target <0.0-31.0> maximum <0.0-31.0>
9. Configure the upstream minimum, target, and maximum noise margins the VTU-R
receiver shall tolerate.
ChassisID(config-vdsl x/x/x@x/x/x)#dmt-options snr-margin upstream
margins minimum <0.0-31.0> target <0.0-31.0> maximum <0.0-31.0>
10. Enable all required hamband notches to reduce hamband interference.
ChassisId(config-vdsl x/x/x@x/x/x)#dmt-options hamband-notch
[1.8|3.5|7.0|10.1|14.0|18.06|21.00|24.89|28.00]
11. Provision the downstream latency path delay.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path delay downstream 0 <1-
63>
12. Provision the upstream latency path delay.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path delay upstream 0 <1-63>
13. Provision the upstream latency path initialization policy to maximize data rate.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path init-policy upstream 0
data-rate
78 65K110FTTP-29A
Revision A
14. Provision the downstream latency path initialization policy to maximize data rate.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path init-policy downstream
0 data-rate
15. Provision the upstream latency path minimum Impulse Noise Protection (INP) to
maximize data rate.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path inp upstream 0 <0-16>
16. Provision the downstream latency path minimum Impulse Noise Protection (INP) to
maximize data rate.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path inp downstream 0 <0-16>
17. Provision the upstream latency path type to interleave.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path type upstream 0
interleave
18. Provision the downstream latency path type to interleave.
ChassisId(config-vdsl x/x/x@x/x/x)#latency-path type downstream 0
interleave
19. Provision the upstream power backoff to custom.
ChassisId(config-vdsl x/x/x@x/x/x)#power-back-off upstream mode custom
20. Provision downstream rate adaption to begin at startup.
ChassisId(config-vdsl x/x/x@x/x/x)#rate-adaption downstream startup
21. Provision upstream rate adaption to begin at startup.
ChassisId(config-vdsl x/x/x@x/x/x)#rate-adaption upstream startup
22. Using Table 2-19 and the CLI help prompts, type a variation of the following command:
ChassisID(config-vdsl x/x/x)#deployment region 1 scenario 2 other-
service 1 application-standard 1 band-plan 1 band-profile 7 psd-u0 1
psd-mask 1
Refer to the following for the VDSL deployment syntax:
Table 2-19. VDSL Deployment Syntax
Syntax Description
Deployment Region Selects what group spectral masks to be used. North America is the only
supported region.
Enter 1 to select North America.
Scenario Determines the usage of lower band frequencies. Exchange is the only
supported option.
Enter 2 to select Exchange.
Other-service Selects the other-service sharing the spectrum with VDSL. Typically, the
choice will be POTS. The options are as follows:
■ 1 - POTS
■ 4 - ADSL
65K110FTTP-29A 79
Revision A
Table 2-19. VDSL Deployment Syntax (Continued)
Syntax Description
Application-standard For VDSL1 (G.993.1) in North America, select ANSI; for VDSL1 in Europe,
select ETSI; for VDSL2 (G.993.2), select ITU. The options are as follows:
■ 1 - ANSI
■ 2 - ETSI
■ 4 - ITU
Band-plan Represents the highest supported band edges for each band carrier
group. The option is as follows:
■ 1 - A–998
Band-profile Selects the characteristics such as PSD and transmit power. This option
defaults to 8A. The options are as follows:
■ 1 - 8A - Typical Application: Exchange (CO)
■ 2 - 8B - Typical Application: Exchange (CO)
■ 3 - 8C - Typical Application: Cabinet (RT)
■ 4 - 8D - Typical Application: Exchange (CO) or Cabinet (RT)
■ 5 - 12A - Typical Application: Exchange (CO) or Cabinet (RT)
■ 6 - 12B - Typical Application: Exchange (CO) or Cabinet (RT)
■ 7 - 17A - Typical Application: Cabinet (RT) or MDU
PSD-u0 Determines whether the use of the U0 band is enabled; yes is the
recommended default. This is located immediately above POTS/IDSN.
The options are as follows:
■ 1 - Enable
■ 2 - Disable
PSD-mask The PSD mask is applied to the U0; EU 32 is the only supported option.
Enter 1 to select EU 32.
gThisNOTE
is not a complete list of options. Some options can dynamically appear and disappear
depending on previous selections within the command.

ChassisID(config-vdsl x/x/x@x/x/x)#no shutdown
24. Return to the Enable prompt.
ChassisID(config-vdsl x/x/x@x/x/x)#exit
What’s Next
For video or data provisioning, continue to Section 2.3.5.6, “Provision the EFM Port” on
page 81.
80 65K110FTTP-29A
Revision A
2.3.5.6 Provision the EFM Port

To provision the EFM port, complete the following:
1. Access the EFM Group Interface Configuration Command Set.
ChassisID(config)#interface efm-port <ont-id/0/vdsl-port>@<shelf/slot/
port>.gpon
2. Configure the maximum limit of learned MAC addresses for the EFM port interface.
ChassisID(config-efm-port x/x/x@x/x/x)#mac limit <1-n>
3. Enable the EFM interface.
ChassisID(config-efm-port x/x/x@x/x/x)#no shutdown
ChassisID(config-efm-port x/x/x@x/x/x)#exit
ChassisID(config-atm x/x/x@x/x/x)#end
6. Verify the EFM port is In Service.
ChassisID#show interfaces efm-port <ont-id/0/vdsl-port>@<shelf/slot/
port>.gpon
efm-port 1/0/1@1/6/1 is IS and active
Receive Transmit
Packets : 0 0
Octets : 0 0
Overflow pkt : na 0
Overflow oct : na 0
What’s Next
page 83.
65K110FTTP-29A 81
Revision A
2.3.6 Create an IP Host

Each gateway requires a unique IP address and an EVC-Map to associate the IP address with
a particular transport EVC. The EVC, the IP subnet, and any related IP server configurations
are typically shared among multiple gateway instances, but can vary.
1. Access the IP Host Configuration Command Set.
Substitute WORD with an alphanumeric string used to identify the IP Host. If an IP Host
with this identifier does not already exist, a new one is created.
gOnlyNOTE
two interface ip-host entities can be created per ONT. Attempts to create more than two
will be rejected.
ChassisID(config)#interface ip-host WORD ont-id@<shelf/slot/port>

2. Select the method of IP host management.
Refer to Table 2-20 for a list of IP host options.
Table 2-20. IP Host Management
IP Host Command Description
Static ChassisID(config-ip-host name ont-id@x/x/x)#ip Set the static IP

IP address a.b.c.d a.b.c.d address and subnet
mask for the IP host
interface.
Continue to step 3.
DHCP ChassisID(config-ip-host name ont-id@x/x/x)#ip Allocate the IP

address dhcp address for this IP
host interface
dynamically using
DHCP.
Continue to step 4.
3. If a static IP address is used, assign the IP address of the default gateway.

ChassisID(config-ip-host name ont-id@x/x/x)#default-gateway A.B.C.D
gThe NOTE
IP address should be unique in the network.
4. Connect the IP host interface to a SIP or MGCP voice service.

ChassisID(config-ip-host name ont-id@x/x/x)#connect service [sip|mgcp]
5. Enable the IP host.
ChassisID(config-ip-host name ont-id@x/x/x)#no shutdown
ChassisID(config-ip-host name ont-id@x/x/x)#exit
What’s Next
For SIP or MGCP provisioning, continue to Section 2.3.7, “Create an EVC-Map” on page 83.
82 65K110FTTP-29A
Revision A
2.3.7 Create an EVC-Map

The EVC-Map establishes a connection between the ONT Ethernet Port and the EVC defined,
as well as holds C-tag information, if needed. The EVC-Map specifies the criteria required for
a particular packet to be classified into the EVC as well as translation parameters for the VLAN
ID and P-Bits. The EVC-Map also provides parameters to select how MAC addresses are
authenticated and learned.
gEVC-Map
NOTE
names are case sensitive.
1. Configure the name of the Map that connects to the EVC and the shelf and slot that
corresponds to the GPON client.
ChassisID(config)#evc-map WORD <shelf/slot>
2. Set the priority for the traffic. It is recommended that SIP traffic be given a high priority
throughout the network. A value of 5 is normally assigned.
ChassisID(config-evc-map name x/x)#men-pri <0-7>
3. Connect the EVC-Map to the UNI port. Use Table 2-21 to determine the type and the
command to complete.
gThe NOTE
eth-port is the Ethernet port # on the ONT, pon-port is the GPON port on the OLT to which
Table 2-21. Interface Type
Service ONT Type Command
Data/Video/ Non-Remote Gigabit-Ethernet ChassisID(config-evc-map name x/x)#

TLS Gateway connect uni gigabit-ethernet
<ont-id/0/eth-port>@<shelf/slot/pon-
port>.gpon
Remote Virtual ChassisID(config-evc-map name x/x)#

Gateway Gigabit-Ethernet connect uni virtutal gigabit-ethernet
port>.gpon
GPON MDU EFM ChassisID(config-evc-map name x/x)#

connect uni efm-port <ont-id/0/vdsl-
Voice All ONTs IP Host ChassisID(config-evc-map name x/x)#

connect ip-host word <ont-id/0/eth-
port>@<shelf/slot/pon-port>
4. Connect the EVC-Map to the EVC.

ChassisID(config-evc-map name x/x)#connect evc WORD
5. If provisioning for voice or data, skip to step 16. If provisioning for video or TLS, set the
subscriber IGMP mode.
■ Forking is only supported on the Total Access 5000 GPON OLT 8X SFP Access Module
(P/N 1187503F1).
65K110FTTP-29A 83
Revision A
■ If provisioning for TLS, the IGMP mode must be set to transparent.

ChassisID(config-evc-map name x/x)#subscriber igmp mode
[block|processing-enabled|transparent|forking]
6. If provisioning for TLS, skip to step 10. If provisioning for video, continue to step 7.
7. Enable smart immediate leave.
This function is associated with IGMP snooping or routing whereby the switch or router
stops sending immediately the multicast stream when receiving an IGMP leave for the
last member on this requesting interface, i.e. without sending one or more group specific
queries and waiting for its timeout.
ChassisID(config-evc-map name x/x)#subscriber igmp immediate-leave
8. Set the IGMP proxy router IP address if the host connected to the ONT cares about the
IP address for IGMP query messages.
The default IGMP proxy router IP address is 0.0.0.0.
ChassisID(config-evc-map name x/x)#subscriber igmp proxy router ip
address A.B.C.D
9. If provisioning for video, skip to step 16.
wStepsNOTICE!
10 - 15 are only for provisioning TLS. If you are provisioning for voice, video, or data,
continue to step 16.
10. Set the DHCP mode to transparent.

ChassisID(config-evc-map name x/x)#subscriber access dhcp mode
transparent
11. Set the PPPoE mode to transparent.
ChassisID(config-evc-map name x/x)#subscriber access pppoe mode
transparent
12. Set the ARP mode to transparent.
ChassisID(config-evc-map name x/x)#subscriber arp mode transparent
13. If provisioning for Single TLS, skip to 27. If provisioning for Double Tag TLS, continue to
step 14.
14. Set the C-tag.
ChassisID(config-evc-map name x/x)#men-c-tag <2-4094>
15. If provisioning for Double Tag TLS, continue to step 27.
16. Set the subscriber modes.
Refer to Table 2-22 on page 85 for a list of available subscriber modes.
gPPPoE
NOTE
does not support video services.
84 65K110FTTP-29A
Revision A
Mode Steps
DHCPv4 Complete the following steps:

1. Apply DHCP for subscriber authentication for the EVC-Map.
authenticate
2. Discard PPPoE discovery traffic for the EVC-Map.
block
DHCPv6 Complete the following:

ChassisID(config-evc-map name x/x)#subscriber access dhcp6 mode
authenticate
For a list of DHCPv6 options refer to Table 2-24 on page 87.
block
PPPoE Complete the following steps:

1. Discard DHCP traffic for the EVC-Map.
block
2. Apply PPPoE for subscriber authentication for the EVC-Map.
authenticate
■ The default setting for the DHCPv6 access mode mirrors the DHCPv4 setting, therefore
DHCPv6 is enabled by default for all DHCPv4 circuits. To disable DHCPv6 on all existing
circuits of an access module enter the following command:
ChassisId(config)#force subscriber dhcpv6 disable <shelf/slot>
■ Changing the access mode does not change the relay agent settings. Refer to “” on
page 87 for relay agent provisioning steps.
Refer to Table 2-23 on page 86 for a description of the authentication modes.
65K110FTTP-29A 85
Revision A
Table 2-23. Authentication Mode Description
Authentication Mode Description
DHCP Processing Dynamic Host Configuration Protocol (DHCP) is an auto-configuration

protocol used to configure network devices in IP networks. A DHCPv4
customer uses the protocol to acquire configuration information such as IP
addresses, and default routers from the DHCP server being used by the
network. This server maintains all the available IP addresses and configu-
ration information for those addresses in the network.
DHCP supports the following options:
Authenticate - Indicates that the source and contents of the data will be
authorized by DHCP. This can prevent unauthorized access to the
network. ADTRAN recommends this option.
Block - Indicates that all unauthorized Internet Protocol V4 traffic from
unauthorized DHCP users will be blocked. All DHCP messages are
blocked from entering the network via this interface mapping.
Transparent - Ignores DHCPv4 processing.
Snoop - Indicates that any DHCPv4 will be allowed without performing
authentication.
PPPoE Processing Point to Point Protocol over Ethernet (PPPoE) processing is a network
protocol for encapsu-lating Point to Point Protocol (PPP) frames inside
Ethernet frames. PPPoE is used mainly with Digital Subscriber Lines
(DSL) modems over Ethernet. It is also used in Metro Ethernet networks.
Because Ethernet networks employ a packet-based data protocol, there is
a lack of security to protect against IP and MAC address conflicts. PPPoE
establishes a point-to-point connection over the network and then
transports data packets between these specific points or interfaces.
PPPoE supports the following options:
Authenticate - Indicates the MAC address of the subscriber will be
authenticated before data is accepted.
Block - Indicates that the subscriber will not be authenticated using
PPPoE.
Transparent - Indicates that no type of authentication will be used and that
all PPPoE traffic will be allowed.
Refer to Table 2-24 on page 87 for a list of available access modes.
86 65K110FTTP-29A
Revision A
Table 2-24. DHCPv6 Access Modes
Access Mode Command Description
Authenticate ChassisID(config-evc-map name x/x)# Use DHCPv6 for authentication,

subscriber access dhcpv6 mode allow link local IPv6 packets.
authenticate
Same as ChassisId(config-evc-map name x/x)# Mirrors the DHCPv4 authentication

DHCPv4 subscriber access dhcpv6 mode same- Mode.
as-dhcpv4 This is the Default mode.
If DHCPv4 is set to authenticate,
link local IPv6 is allowed and
DHCPv6 is used for authentication.
If DHCPv4 is set to block, link local
IPv6 will also be blocked along with
DHCPv6.
Transparent ChassisId(config-evc-map name x/x)# Ignore DHCPv6 packets. Ignore

subscriber access dhcpv6 mode link local IPv6 packets.
transparent
Block ChassisId(config-evc-map name x/x)# Discard DHCPv6 packets. Blocks

subscriber access dhcpv6 mode block link local IPv6 packets.
Snoop ChassisId(config-evc-map name x/x)# Process DHCP without performing

subscriber access dhcpv6 mode snoop authentication.
17. Configure the Relay Agent.

The Total Access 5000 products provide the option to enable a Relay Agent, on an EVC
Map, that inserts access loop identification information, in the form of Circuit/Interface ID,
Remote ID, and loop characteristic information (as defined in Broadband Forum TR-101),
into both DHCPv4 and DHCPv6 packets before forwarding the packets to the DHCP
server. This information is used by the DHCP server for authentication purposes.
DHCPv4 utilizes Option-82 to insert the Circuit ID, Remote ID, and loop characteristics.
DHCPv6 utilizes Option-17 to insert a vendor-specific tag containing the loop
characteristics, Option-18 to insert the Interface ID (equivalent of DHCPv4 Circuit ID) and
Option-37 to insert the Remote ID. The Interface or Circuit ID identifies the access loop
logical port on the Total Access 5000 or OSP on which the DHCP message was received.
The Remote ID uniquely identifies the user on the access loop on the Total Access 5000
on which the DHCP discovery message was received.
gBeginning
NOTE
with Total Access 5000 System Release 8.7, the DHCP remote ID is the name of
the EVC Map.
The format of the Circuit/Interface ID and Remote ID is a string of variables usually

separated by characters (# . / ,etc.) and is limited to 63 total characters. Each variable
begins and ends with a dollar sign ($).
For example, for a circuit in shelf 1, slot 5, port 27, with a VLAN ID of 201. The command
on the following page would output the Circuit ID below.
Command:
ChassisID(config-evc-map name x/x)#subscriber access dhcp option-82
circuit-id $shelf$/$slot$/$port$/$vid$
65K110FTTP-29A 87
Revision A
Circuit ID:
1/5/27/201
■ There is only one "remote-id format" storage per EVC Map used for DHCP, DHCPv6 and
PPPoE intermediate agent. Changing one of these affects all of the other Remote-id
formats on the EVC Map. Enabling remote-id insert on DHCP, DHCPv6 or PPPoE
intermediate agent on an EVC map will enable remote-id insert for all services on the EVC
Map. DHCP and PPPoE circuit-id and DHCPv6 interface-id format are also shared.
■ Enabling loop-characteristic insertion on DHCPv4, DHCPv6, or PPPoE will enable it for all
three protocols on that EVC Map.
Table 2-25 lists the variables supported by the NetVanta products and the information
inserted into the Circuit/Remote ID for each variable.
Table 2-25. Supported Variables
Variable Output Description
$accessnodeid$ TID/Chassis-ID if sync enabled; otherwise TID value 1

For Example: TA5000_56
$chassis-id$ TID/Chassis-ID if sync enabled; otherwise chassis-id value 1, 2

For Example: shelf_56
$cn$ Access node number
$node$ Access node number
$shelf$ Shelf number in the access node
$slot$ Slot number in the shelf
$sn$ Slot number in the shelf
$port$ Port number is the PON number
$ont$ ONT number
$ontslot$ ONT Slot number
$ontport$ Port on ONT
$vid$ VLAN ID on the subscriber interface.
$q-vid$ VLAN ID on the subscriber interface.
$pbits$ Ethernet priority bits on the network port interface
$map$ EVC map name connected to the user sending the DHCP packets 3
For Example: data26map
$serialnum$ Returns Activated ONT serial number to CIRCUIT-ID and REMOTE-

ID fields
1. If TID - System Name Sync is enabled the chassis-id is overwritten with the TID, therefore $accessnodeid$ and
$chassis-id$ display equivalent values. If TID - System Name Sync is disabled $accessnodeid$ displays the
TID and $chassis-id$ displays the chassis-id.
2. $chassis-id$ is only supported by Total Access 5000 System Release 7.2 forward.
3. $map$ can only be used in the Remote ID.
88 65K110FTTP-29A
Revision A
18. Configure Circuit ID.

a. Enable DHCPv4 Relay Agent. Enabling the Relay Agent inserts the Option-82
Circuit ID.
b. Configure the format of the Circuit ID. Replace WORD in the following command
with the Circuit ID. The format of the Circuit ID is a string of variables usually
separated by characters (# . / ,etc.). Refer to Table 2-25 on page 88 for a list of
supported variables.
circuit-id WORD
19. Configure the Remote ID.
a. Enable Option 82 Remote ID insertion.
remote-id
b. Configure the format of the Remote ID. The format of the Remote ID is a string of
variables usually separated by characters (# . / ,etc.). Refer to Table 2-25 on
page 88 for a list of supported variables.
remote-id format WORD
20. Configure DHCPv6 Relay Agent Insertion.
Configure the DHCPv6 relay agent to insert a custom Circuit ID, a Remote ID and loop
characteristics into DHCPv6 packets.
gDHCPv6
NOTE
mode must be set to Authenticate, Snoop, or Same-as-DHCPv4.
21. Configure Interface ID.

Interface ID.
ChassisID(config-evc-map name x/x)#subscriber access dhcpv6 relay-
agent mode enable
or
agent mode same-as-dhcpv4
gSetting
NOTE
the same-as-dhcpv4 option will mirror the provisioned mode of DHCPv4 option-82
relay agent as the effective mode for the DHCPv6 relay-agent.
b. Configure the format of the Interface ID. Replace WORD in the following command
with the Interface ID. The format of the Interface ID is a string of variables usually
agent interface-id format WORD
65K110FTTP-29A 89
Revision A

agent remote-id insert
agent remote-id format WORD
23. Configure PPPoE Intermediate Agent Insertion.
Configure the PPPoE relay agent to insert a custom Circuit ID, a Remote ID and loop
characteristics into PPPoE packets.
gPPPoE
NOTE
mode must be set to Authenticate.

a. Enable Intermediate Agent, enabling the Intermediate Agent inserts the Circuit ID.
ChassisID(config-evc-map WORD x/x)#subscriber access pppoe
intermediate-agent
b. Configure the format of the Circuit ID. Refer to Table 2-25 on page 88 for a list of
ChassisID(config-evc-map name x/x)#subscriber access pppoe
intermediate-agent circuit-id WORD
25. Enable Intermediate Agent Remote ID insertion.
ChassisID(config-evc-map name x/x)#subscriber access dhcp pppoe
intermediate-agent remote-id
26. Apply any additional EVC-Map configurations.
gThe NOTE
following configurations listed in Table 2-26 on page 91 are optional and not required to
pass single-tagged traffic.
90 65K110FTTP-29A
Revision A
Table 2-26. Additional EVC-Map Configurations
Option Command Description
Static IP ChassisID(config-evc-map name x/x)#subscriber Configures a Static IP on an

access static-ip <subscriber ip> <subscriber EVC; the Gateway MAC can
mac> <gateway ip> <gateway mac> be left off and it resolves
through ARP or if the MAC is
entered as
00:00:00:00:00:00, the MAC
resolves through ARP.
S-Tag ChassisID(config-evc-map name x/x)#men-pri Configures the priority level

Priority <0-7> of the criteria for the
associated map in the EVC
to which the map is
connected. When maps are
configured for explicit CoS,
the P-bit value of the EVC
tag for associated frames
can always be set to that
CoS value.
S-Tag ChassisID(config-evc-map name x/x)#men-pri Configures the S-tag P-bits

P-Bits inherit to the ingress P-bits.
C-Tag ChassisID(config-evc-map name x/x)#men-c-tag- Configures the C-tag P-bits

P-Bits pri inherit to the ingress P-bits.
Double ChassisID(config-evc-map name x/x)#men-c-tag Configures the inner VLAN

Tag <1-4094> tag for this circuit and
creates a QinQ-tagged flow
towards the network side.
C-Tag ChassisID(config-evc-map name x/x)#men-c-tag- Configures the priority level

Priority pri [<0-7>|inherit] of the MEN C-Tag for the
associated map. When
maps are configured for
explicit CoS, the P-bit value
of the MEN C-Tag for
associated frames can
always be set to that CoS
value.
Matching ChassisID(config-evc-map name x/x)#match Matches the CE-VLAN-ID

CE-VLAN ce-vlan-id <0-4094> coming off of the loop.
Matching ChassisID(config-evc-map name x/x)#match Configures the ingress

CE-VLAN ce-vlan-pri <0-7> matching criteria to include
Priority the priority level within the
CE VLAN identifier or the
map. Use the no form of this
command to remove the
matching criteria from the
map.
65K110FTTP-29A 91
Revision A
Table 2-26. Additional EVC-Map Configurations (Continued)
Matching ChassisID(config-evc-map name x/x)#match Configures the ingress

Multicast [broadcast|l2cp|multicast|unicast|untagged] matching criteria to include
multicast traffic.
Network ChassisID(config-evc-map name x/x)#network- Configures the P-Bit priority

Ingress ingress-filter men-pri <0-7>|list (or priorities if more than one
Filter P-Bit was provisioned using
the LIST command) for
traffic entering the network.
MAC OUI ChassisID(config-evc-map name x/x)#match Allows multiple services to

source mac-address be assigned to the same
[xx:xx:xx:xx:xx:xx|xx:xx:xx:xx:xx:xx UNI and be separated by the
xx:xx:xx:xx:xx:xx] Organizationally Unique
Identifier (OUI) portion of the
MAC address.
wMACNOTICE!
OUI is only supported for video. If applying MAC OUI to other services, such as data, it
can stop that service from functioning properly.
27. Enable the EVC-Map.

ChassisID(config-evc-map name x/x)#no shutdown
What’s Next
■ For OMCI SIP and Non-OMCI SIP provisioning, continue to Section 2.3.8, “Provision the
SIP Trunk” on page 93.
■ For OMCI MGCP and Non-OMCI MGCP provisioning, continue to Section 2.3.9,
“Provision the MGCP Profile” on page 95.
■ For non-remote gateway ONT video or data provisioning, this completes provisioning.
Services should be up and running. To provision another service, continue to Section
2.3.2, “Service Provisioning” on page 62.
■ For TLS, this completes provisioning. Services should be up and running. To provision
■ For Shaper provisioning, continue to Section 8, “Traffic Management” on page 331.
92 65K110FTTP-29A
Revision A
2.3.8 Provision the SIP Trunk

The SIP trunk is the logical path to the SIP proxy. The attributes configured on the trunk should
be compatible with the corresponding parameters on the SIP proxy. If the system defaults
match the capabilities and configured options of the SIP proxy, a small amount of trunk provi-
sioning is required.
All voice trunks are shared across the node, so provisioning of a trunk at the GigE Switch
Module makes it available to all gateways.
1. Access the SIP Trunk Configuration Command Set.
Use the voice sip-trunk <Txx> command to activate the SIP Trunk Configuration
Command Set. <Txx>, in which 'x' represents a number 0-9, is used to identify this trunk.
If a trunk with this identifier does not already exist, a new one is created. There is a limit
of 5 trunks that can be created.
ChassisID(config)#voice sip-trunk <Txx>
2. Set the IP address or fully qualified domain name (FQDN) of the primary SIP server to
which the trunk will send call-related messages.
ChassisID(config-sip-trunk name)#sip proxy primary [A.B.C.D|WORD]
3. Set the primary SIP registrar full qualified domain name (FQDN) or IP address that is
based on the domain naming system (DNS) suffix.
ChassisID(config-sip-trunk name)#sip registrar primary A.B.C.D udp <0-
65535>
4. Configure the domain name.
ChassisID(config-sip-trunk name)#domain WORD
If the domain name is configured in the IP host and also in the SIP trunk, then the domain
name configured via IP host shall override the domain name configured via trunk for that
particular user. For example, if the domain name in the IP host is configured as
provider1.telco1.com and the domain name configured in the SIP trunk is configured as
provider2.telco2.com, then the domain name for this IP host shall be
provider1.telco1.com.
If the domain name is configured in the SIP trunk profile using FQDNs and the domain
name is not defined in the IP host then the domain name for all users shall be the domain
name configured in the SIP trunk.
5. If the system defaults match the capabilities and configured options of the SIP proxy, no
further provisioning is required.
65K110FTTP-29A 93
Revision A
2.3.8.1 Configure additional SIP Trunks

Before provisioning an additional SIP Trunk, the following restrictions should be observed.
■ Up to five SIP Trunks can be provisioned per OLT
■ Only one SIP Trunk is allowed per ONT or Subscriber
To provision an additional SIP Trunk, complete the following steps:
ChassisID(config)#
2. Create a second SIP Trunk.
ChassisID(config)#voice sip-trunk name
Where “name” is the designation for the second SIP Trunk, (i.e., T02).
3. Set the SIP User interface.
ChassisID(config-sip-trunk 02)#voice user sip 1/0/1@1/19/1
Where the SIP User’s interface is 1/0/1@1/19/1.
4. Assign the second SIP Trunk to this user.
ChassisID(config-voice-user-sip 1/0/1@1/19/1)#sip-trunk T02
What’s Next
For Non-OMCI and OMCI SIP provisioning, continue to Section 2.3.11, “Provision the SIP
Dialing Profile” on page 98.
94 65K110FTTP-29A
Revision A
2.3.9 Provision the MGCP Profile

To create the MGCP profile, complete the following:
1. Create the MGCP profile.
ChassisID(config)#voice profile mgcp WORD
2. Specify the primary MGCP call agent host name.
It is important to identify the call agent to the ONT MGCP Endpoint. Both primary and
secondary call agents can be established, but at minimum a primary call agent is
required. If a connection with the primary call agent fails, call agents will be tried in the
order they are entered in the configuration.
TA5K (config-mgcpname)#call-agent primary <IP address>
What’s Next
■ For Non-OMCI MGCP provisioning, continue to Section 2.3.10, “Provision Non-OMCI
MGCP Endpoints” on page 96.
■ For OMCI MGCP provisioning, continue to Section 2.3.19, “Provision OMCI MGCP
Endpoints” on page 113.
65K110FTTP-29A 95
Revision A
2.3.10 Provision Non-OMCI MGCP Endpoints

MGCP endpoints are dedicated FXS ports configured to use MGCP to communicate with a
call agent.
1. Create an endpoint and enter the endpoint configuration.
The <index> parameter is a numerical value ranging from 1 to 255 that is used to identify
the endpoint in the default naming structure.
Using the no form of this command destroys the specified endpoint, and if necessary,
disconnects it from the specified interface.
TA300(config)#voice mgcp-endpoint <index>
2. Create a textual description of the endpoint.
Using the no form of this command removes the endpoint’s description.
TA300(config-mgcp-x)#description WORD
3. If required, connect the endpoint to a physical FXS port, rather than a virtual one, on the
FTTP ONT product.
gThisNOTE
command fails if the specified FXS port is already in use on another MGCP endpoint or a
configured voice user.
Using the no form of this command disconnects the endpoint from the physical FXS port
and connects it to a virtual port.
TA300(config-mgcp-<endpoint>)#connect fxs <slot/port>
4. If required, give the endpoint a specific name to be referenced by the call agent.
By default, when endpoints are created and given an index number, they are named in
the following format: aaln/x, where x is the index number.
TA300(config-mgcp-<endpoint>)#name WORD
5. If required, block caller ID information on an endpoint.
gThisNOTE
does not affect caller ID delivered in the RTP stream to the FXS port.
The command blocks caller ID delivery to the connected FXS port, if the caller ID
information is presented in the MGCP signaling messages.
Using the no form of this command allows caller ID information to appear as if it is
included in the MGCP message.
TA300(config-mgcp-<endpoint>)#block-caller-id
6. Specify how long (in milliseconds) the endpoint’s battery is removed during a forward
disconnect situation.
In a forward disconnect, the call agent sends a network disconnect (osi), and the
specified forward disconnect time matches the battery behavior.
TA300(config-mgcp-<endpoint>)#fwd-disconnect delay
[250|500|750|900|1000|2000|follow-switch]
The battery behavior can also be set to follow the Class 5 switch. This depends upon the
endpoint’s RFC 2833 signaling setting. If the RFC 2833 signaling is enabled, then using
96 65K110FTTP-29A
Revision A
the follow-switch parameter means that the Class 5 switch determines the length of time
the battery is removed.
TA300(config-mgcp-<endpoint>)#fwd-disconnect delay follow-switch
What’s Next
For Non-OMCI MGCP, this completes provisioning. Services should be up and running. To
provision another service, continue to Section 2.3.2, “Service Provisioning” on page 62.
65K110FTTP-29A 97
Revision A
2.3.11 Provision the SIP Dialing Profile

The Dialing Profile is assigned to voice users, and is used to notify the access modules when
to stop collecting digits being dialed and begin connecting a phone call. The dial profile
creates and stores number-complete templates.
A number-complete template consists of a pattern of digits used by telephone companies
when making calls. A typical template would be 555-XXX-XXX. These templates can be
expanded to include Dial Plans, External Line Codes and Special Prefix Patterns.
The access module collects digits and looks for a match against the Dial Plans, External Line
Codes and Special Prefix (SPRE) Patterns. When the digits dialed match a number-complete
template, the dial-string is immediately sent to the server for routing.
For example, a normal phone number consists of the following template: 555-XXX-XXXX
(where “X” is a wild card denoting any digit from 1 to 9). The first three digits are the Area
Code Designation, the next three digits are the Phone Exchange Designation, and the last four
digits are the Local Number Designation.
When a user initiates a phone call, the access module compares the dialed digits to the
number-complete template. If the dialed digits are a match (in this case, three 5s followed by
seven other digits) the access module immediately sends the complete dial-string to the
server. The server then routes and connects the call.
If the user dials a pattern of digits that does not match any number-complete template, the
pattern will still be forwarded to the server after the Inter-digit Timeout has expired. Proper
definition of the dial plan is recommended for optimum customer experience. At the very least,
emergency numbers should be configured to avoid delays in these calls.
The different types of number-complete templates can be chained together to form longer dial-
strings with the use of chaining characters (“&”). For example, if a dialing profile contains an
External Line Code "9&", a Special Prefix "*70&" and a Dial Plan "555-XXX-XXXX" and the
user dials *70,9,555-123-4567, all the digits will be gathered into a single dial-string and sent
to the server when the last digit is entered. An External Line Code will only be matched once
during a dialing sequence.
2.3.11.1 Dial Plan Pattern Restrictions

Dial Plan patterns are entered using the dial-plan <type> <PATTERN> [emergency-
number] [external-line-code <prohibited|required>] command. The following types
are supported: 900-number, always-permitted, internal, international, local, national, operator-
assisted, specify-carrier, toll-free, user1, user2 and user3. Multiple patterns of the same type
are allowed. The pattern must be in the form of a phone number or dialing pattern containing
wildcards. Available wildcards are: N=2-9, M=1-8, X=0-9, and [abc]=Any digit contained in the
bracketed list. When creating a Dial Plan Pattern, the following rules must be observed:
■ Templates must have at least one number or wild card
■ The “(' ')” and “-” characters are allowed, but not inside brackets “[ ]”
■ A “,”is allowed within bracket “[ ]”, but not elsewhere
■ Wild cards (MNX) are not allowed inside brackets “[ ]”
■ Order of numbers is not enforced within brackets “[ ]”
■ The “$” character is allowed, but MUST be the last character in the pattern or standalone
■ If “*” and “#” are entered, they must be the first character in the pattern. They cannot be
standalone.
The following are examples of possible Dial Plan patterns:
98 65K110FTTP-29A
Revision A
■ For a residential customer:

♦ dial-plan 900-number 1-900-NXX-XXXX
♦ dial-plan always-permitted 911 emergency-number
♦ dial-plan international 011$
♦ dial-plan local 256-NXX-XXXX
♦ dial-plan local NXX-XXXX
♦ dial-plan national 1-NXX-NXX-XXXX
♦ dial-plan specify-carrier 10-10-XXX$
♦ dial-plan toll-free 1-800-NXX-XXXX
♦ dial-plan user1 [23456]11
■ For a business customer (using an external line code):
♦ dial-plan 900-number 1-900-NXX-XXXX external-line-code required
♦ dial-plan internal MXXX external-line-code prohibited
♦ dial-plan international 011$ external-line-code required
♦ dial-plan local 256-NXX-XXXX external-line-code required
♦ dial-plan local NXX-XXXX external-line-code required
♦ dial-plan national 1-NXX-NXX-XXXX external-line-code required
♦ dial-plan specify-carrier 10-10-XXX$ external-line-code required
♦ dial-plan toll-free 1-800-NXX-XXXX external-line-code required
♦ dial-plan user1 [23456]11 external-line-code required
2.3.11.2 SPRE Pattern Restrictions

SPRE patterns are entered using the spre <PATTERN> [tone <dial|stutter-dial>]
command. SPRE Pattern creates special code numbers required to access voice services. A
SPRE Pattern must be in the form of a special prefix (spre) code or dialing pattern containing
wild cards. Available wild cards are: N=2-9, M=1-8, X=0-9 [abc] = any digit contained within
the bracket list. The pattern can end with a chaining character (“&” or “$”) which allows for the
collection of more digits before the dial string is sent to the server. Ending the pattern with “&”
causes the server to continue to look for another number-complete template (dial plan,
external line-code or special prefix pattern) following the SPRE code. Ending it with “$” causes
the access module to stop attempting to match additional inputs. However, digits will continue
to be collected until after the Inter-Digit time out occurs.The following rules must be observed:
■ The Template must begin with an “*” or “#”. An “*” and “#” are not allowed elsewhere in the
Template
■ The Template must have at least one number
■ The characters “(“”) and “-” are allowed, but not inside “[ ]”
■ Do not use “,” or “” inside “[ ]”
65K110FTTP-29A 99
Revision A
■ Wild cards (MNX) are not allowed inside “[ ]”

■ The characters “&” and “$” are allowed but must be the last character and cannot be a
standalone
The following are examples of possible SPRE Patterns:
■ spre *3XX
■ spre *6[37]&
■ spre *72& tone stutter-dial
■ spre *82&
■ spre *9[02]& tone stutter-dial
■ spre *7[45]$
■ spre *[56789]X
2.3.11.3 External Line Code Restrictions

External Line Codes are entered using the external-line-code <PATTERN> [tone
<dial|stutter-dial>] command. An External Line Code must be in the form of a dialing
pattern without wild cards. For example, if a user must first dial “8” to obtain an outside line,
the entry would be “8&” where the ampersand tells the server that the “8” designates an
outside number and to expect more digits in the number-complete template. The pattern can
end with a chaining character (“&” or “$”), which allows for collection of more digits before the
dial string is sent to the server. Ending the pattern with a “&” causes the server to continue to
look for another number-complete template (dial plan or special prefix pattern) following the
external line code. An external line code will only be matched once. Ending the pattern with a
“$” causes the access module to stop attempting to match additional inputs. However, digits
will continue to be collected until after the Inter Digit time out occurs. The following rules must
be observed:
■ Template must have at least one number.
■ Wild cards are not allowed.
■ If “*” and “#” are entered, they must be the first character. They cannot be standalone.
■ The characters “&” or “$” are allowed but must be the last character and cannot be
standalone.
The following is an example of a possible External Line Code:
■ external-line-code 8& tone dial
100 65K110FTTP-29A
Revision A
2.3.11.4 Dial Plan Provisioning

To provision the dial plan, complete the following:
2. Create or modify a dialing profile.
ChassisID#voice profile dialing WORD
3. Provision the dial-plan options.
ChassisID(config-dialing-profile WORD)#dial-plan <type> <pattern>
[emergency-number] [external-line-code <required|prohibited>]
■ To support ten-digit and seven-digit local dialing simultaneously, either the ten-digit dial
plan must contain the area code (256-XXX-XXXX, for example) or the seven-digit dial plan
should not be specified. If the seven-digit dial plan is not specified, the user will have to
wait for the inter-digit timeout to expire before the call will be connected.
■ When the external-line-code option is not specified, an external line code is considered
optional. This indicates that this number-complete template will be matched regardless of
whether or not an External Line Code is present. For example, assume that in order to get
to a phone connection outside of a business, the user first must dial “8”. If a Dial Plan
pattern of “991” is defined with the External Line Code set to “Optional”, a user could get
an Emergency Operator (911) either by dialing “8911” or “911”.
4. Set the star codes for this number (call forwarding, automatic recall, etc).
ChassisID(config-dialing-profile WORD)#voice spre *XX
Refer to Table 2-27 for a list of dial plan options.
Refer to Table 2-28 on page 102 for a list of SPRE options.
Table 2-27. Dial Plan Options
Syntax Description
type The following options are available:

■ always-permitted – Always Permitted
■ internal – Internal Calls
■ national – National Calls
■ toll-free – Toll Free Calls
■ 900-number – 900 Number Calls
■ international – International Calls
■ operator-assisted – Operator Assisted Calls
■ specify-carrier – Carrier Specified
■ user1 – Match User 1
emergency-number Emergency Number designates whether this Dial Plan is designated as an

Emergency Service. When Enabled, this number is designated as an
Emergency Service number. For example, “911” is typically reserved as an
Emergency Number. Emergency Numbers can be assigned special behaviors
not normally found in other calls. For more information, refer to the voice
emergency-number onhook [inhibit|allow] command in the Section
2.3.17, “Provision the Call Feature Profile (Optional)” on page 109.
65K110FTTP-29A 101
Revision A
Table 2-27. Dial Plan Options (Continued)
Syntax Description
external-line-code External Line Code describes the behavior of this Dial Plan when an External
Line Code is present. The External Line Code should be used when a
customer subscribes to the “Hosted PBX”, “Centrex” or “Business Group”
feature on the server. The External Line Code option identifies whether a Dial
Plan Pattern is expected to follow the dialing of an External Line code, which
allows for the identification of what would otherwise be contradictory dial
plans. The following options are available:
■ Prohibited – indicates that this number-complete template will not be
matched if an External Line Code has been previously dialed. For example,
a user inside a company is trying to connect with another employee inside
the same company by dialing an internal four-digit extension number using
the pattern “MXXX”; if the user first dials an “8” and then the employee’s
extension, the pattern will not be matched allowing more digits to be dialed.
If the Prohibited option had not been set, the dial string would have been
sent to the server as soon as the four digits were entered. This would have
been an invalid number and would also prevent longer, external numbers
from being dialed.The Prohibited options instructs the server to complete
the number dialed only if an external line code is not dialed. This would be
of particular importance if some of the employee extensions could be
confused with outside numbers (i.e., extension 4111, or 9112).
■ Required – indicates that this number-complete template will only be
if a Dial Plan pattern of “555-XXX-XXXX” is defined as a local number, it will
only be matched (and immediately sent in the dial string to the server) if the
user first dials the external line code (i.e., “8” for these examples).
Table 2-28. SPRE Options
Syntax Description
tone Specifying a Tone causes the access module to generate a call progress tone
after the number-complete template is matched, and before further digits are
entered. A tone can only be specified if the SPRE pattern ends with a chaining
character. For example, a “&” or a “$” character. The following options are
possible:
■ Dial – Dial indicates a constant dial tone is heard.
■ Stutter – Stutter indicates an intermittent dial tone is heard.
5. If this profile is for customers that support the "Hosted-PBX", "Centrex" or "Business
Group" feature, specify an external line code.
ChassisID(config-dialing-profile WORD)#external-line-code <pattern>
[tone <dial|stutter-dial>]
Refer to Table 2-29 for a list of External Line Code options.
102 65K110FTTP-29A
Revision A
Table 2-29. External Line Code Options
Syntax Description
character. For example, an “&” or a “$” character. The following options are
possible:
■ Dial – indicates a constant dial tone is heard.
■ Stutter – indicates an intermittent dial tone is heard.
What’s Next
■ For Non-OMCI SIP provisioning, continue to Section 2.3.12, “Provision Class of Service
(CoS) (Optional)” on page 104.
■ For OMCI SIP provisioning, continue to Section 2.3.15, “Provision the Media Profile
(Optional)” on page 107.
65K110FTTP-29A 103
Revision A
2.3.12 Provision Class of Service (CoS) (Optional)

CoS is an optional provisioning choice that defines the permissions available to a system user
for making voice calls. Voice CoS permissions include the type of calls and actions a user can
perform.
The default CoS, called DEFAULT_COS, grants permission to place all types of calls is
automatically assigned to all voice users.
Creating further CoS entries is only necessary if restrictions are to placed on types of calls the
voice user can make.
To create or edit a CoS, complete the following:
1. Access the Voice CoS Command prompt.
Use the voice class-of-service WORD command to activate the Voice CoS Command
Set. Substitute WORD with an alphanumeric string used to identify this CoS. If a CoS
TA300(config)#voice class-of-service WORD
2. If required, apply any necessary calling restrictions.
All types are enabled by default, so only “no” commands need be entered into a new CoS
entity (to deny permission to that call type). Almost all dial plan types are accepted: 900-
number, internal, international, local, national, operator-assisted, specify-carrier, toll-free,
user1, user2 and user3. Dial plan type always-permitted cannot be denied. In addition,
the [no] call-privilege all command can be used to turn on (or off) all permissions at once.
TA300(config-cos name)#[no] call-privilege <type>
TA300(config-cos name)#exit
4. Access the Voice User Command prompt.
Substitute NUMBER:20 with a number less than 20 digits long used to identify this user.
Generally, the user's phone number is entered here, but it is not necessary. If a User with
this identifier does not already exist, a new one is created.
TA300(config)#voice user <number>
5. Connect the voice user to the new class of service.
Substitute WORD with the alphanumeric string used to identify the voice class-of-service
entity created in step 1.
TA300(config-user name)#cos <name>
TA300(config-user name)#exit
Repeat steps 4 - 6 for all voice users to whom the calling restrictions apply.
What’s Next
Continue to Section 2.3.13, “Provision for Global Voice (Optional)” on page 105.
104 65K110FTTP-29A
Revision A
2.3.13 Provision for Global Voice (Optional)

Global provisioning options are available to set the ONT to perform certain operations, like
three-way conferencing, locally.
It is not necessary to change any of these settings if the SIP server is capable of performing
them.
To provision the global voice options, complete the following:
1. Set the flashhook mode.
This command determines if flashhook events will be interpreted locally or will be
forwarded to the far end.
TA300(config)#voice flashhook mode [interpreted|transparent]
2. If the flashhook mode is set to interpreted, set the voice conference mode.
This command determines if voice conferencing bridging will be handled within the unit or
from a far-end conferencing server.
TA300(config)#voice conference mode [local|network]
3. If the voice conference mode is set to local, specify the actions performed if the
conference originator issues a flashhook once the conference has been established.
The following options are available:
■ The drop option specifies that the last party added to the 3-way conference will be
dropped and the call will continue between the two remaining parties.
■ The ignore option specifies that the flashhook will be ignored. The 3-way conference
will continue without interruption.
■ The split option specifies that the 3-way conference will be split into two calls, one
between the originator and the first party and one between the originator and second
party. When additional flashhooks are issued after the split, they will toggle the origi-
nator between the two calls.
TA300(config)#voice conference local originator flashhook
[drop|ignore|split]
4. Configure a global starting User Datagram Protocol (UDP) port for Realtime Transport
Protocol (RDP).
Each Access Module in the shelf will use the same starting UDP port. The default port is
10000.
TA300(config)#ip rtp udp <1026-60000>
What’s Next
Continue to Section 2.3.14, “Provision the Voice User” on page 106.
65K110FTTP-29A 105
Revision A
2.3.14 Provision the Voice User

The user provisioning process is repeated for each individual customer and is typically as
automated as possible. Except for the SIP identity which is unique in the system or network.
Each user must be associated with a particular FXS port and registered to a specific SIP trunk.
To provision a user to a particular FXS port and registered to a specific SIP trunk, complete the
following:
TA300(config)#voice user <NUMBER>
2. Specify the physical port on the selected access module which the user is associated.
TA300(config-user name)#connect fxs 2/<port>
3. Set the SIP identity.
The WORD parameter should match the SIP Identity in the SIP call-router. Also a
common practice to use the customer's phone number here. It is not necessary, however,
and the SIP Identity can be any string that does not contain the following characters:
`@^[]{}\|:<>?" and <space>. The <Txx> parameter identifies the trunk that this user
should use to contact the SIP server.
The auth-name and password parameters are optional.
TA300(config-user name)#sip-identity <station> <Txx> register auth-name
<username> password <password>
What’s Next
For Non-OMCI SIP, this completes provisioning. Services should be up and running. To
106 65K110FTTP-29A
Revision A
2.3.15 Provision the Media Profile (Optional)

The media profile is created in the Total Access 5000 to provision the Realtime Transport
Protocol (RTP) parameters on the access module/remote device.
1. Access the Media Profile Command Set.
TA5K(config)#voice profile media WORD
2. Provision the media profile options.
Refer to Table 2-30 for a list of media profile options.
Table 2-30. Media Profile Options
Command Description
TA5K(config-media-profile Use this command to configure the RTP frame packetization

name)#rtp frame-packetization time in milliseconds.
[10|20|30]
TA5K(config-media-profile Use this command to set the allowable limits of latency on

name)#rtp packet-delay nominal the network. This sets the nominal delay time value in
<0-240> increments of 10 milliseconds.

name)#rtp packet-delay maximum the network. This sets the maximum delay time value in
TA5K(config-media-profile Use this command to configure the method by which RTP

name)#rtp dtmf-relay enable dial tone multi-frequency (DTMF) events are relayed.
TA5K(config-media-profile Use this command to configure the maximum RTP quality of

name)#rtp qos dscp <0-63> service (QoS) parameters for differentiated services code
point (DSCP).
TA5K(config-media-profile Use this command to configure the starting RTP UDP port
name)#rtp local-port [<1026- used to source RTP from the ONT.
60000>|range]
TA5K(config-media-profile Use this command to switch to passthrough mode on fax or

name)#fax mode modem- modem tone detection. This command allows modem and
passthrough fax calls to maintain a connection without altering the signals
with the voice improvement settings.
TA5K(config-media-profile Use this command to improve voice quality for packetized-

name)#echo cancellation enable based voice calls.
TA5K(config-media-profile Use this command to configure the minimum and maximum

name)#flashhook threshold time the switch hook must be held to be interpreted as a
[<40-1550>|range] flash.
TA5K(config-media-profile Use this command to enable voice activity detection. When

name)#voice-activity-detection enabled, RTP packets will not be sent during periods of
enable silence.
What’s Next
Continue to Section 2.3.16, “Provision the CODEC Profile (Optional)” on page 108.
65K110FTTP-29A 107
Revision A
2.3.16 Provision the CODEC Profile (Optional)

CODECs are used to convert an analog voice signal to digitally encoded version. Codecs vary
in the sound quality, the bandwidth required, the computational requirements, etc.
1. Access the CODEC Profile Command Set.
TA5K(config)#voice profile codec-list WORD
2. Provision the CODEC profile options.
Refer to Table 2-31 for a list of CODEC options.
Table 2-31. CODEC Profile Options
Command Description
TA5K(config-codec-list-profile Use this command to specify the order of preference for

name)#preference coder-decoders used by the CODEC list.
<1-3> codec [g711alaw|g711ulaw
|g722|g729]
What’s Next
Continue to Section 2.3.17, “Provision the Call Feature Profile (Optional)” on page 109.
108 65K110FTTP-29A
Revision A
2.3.17 Provision the Call Feature Profile (Optional)

Call feature options are available to set the access module/remote device to perform certain
operations, like three-way conferencing, locally. It is not necessary to change any of these
settings if the SIP server is capable of performing them.
1. Access the Call Feature Command Set.
TA5K(config)#voice profile call-feature WORD
2. Provision the call feature profile options.
Refer to Table 2-32 for a list of call feature options.
Table 2-32. Call Feature Profile Options
Command Description
TA5K(config-call-feature Use this command to determine if voice conferencing bridging

name)#feature-mode network will be handled within the unit or from a far-end conferencing
server.
TA5K(config-call-feature Use this command if the voice conference mode is set to

name)#conference local local, specify the actions performed if the conference
originator flashhook originator issues a flashhook once the conference has been
[drop|ignore|split] established.
The drop option specifies that the last party added to the 3-
way conference will be dropped and the call will continue
between the two remaining parties.
The ignore option specifies that the flashhook will be ignored.
The 3-way conference will continue without interruption.
The split option specifies that the 3-way conference will be
split into two calls, one between the originator and the first
party and one between the originator and second party. When
additional flashhooks are issued after the split, they will toggle
the originator between the two calls.
TA5K(config-call-feature Use this command to specify the maximum time a call is

name)#timeouts alerting <0- allowed to remain in the alerting state. The shorter of this
60> timeout or the configured maximum number of rings will
determine how long a call is allowed to ring.
TA5K(config-call-feature Use this command to specify the maximum time allowed

name)#timeouts interdigit between dialed digits.
<1-16>
TA5K(config-call-feature Use this command to enable transfer on hangup. When

name)#transfer-on-hangup transferring a call, hanging up initiates the transfer to the
enable destination party.
TA5K(config-call-feature Use this command to enable call waiting on the subscriber

name)#call-waiting enable port.
TA5K(config-call-feature Use this command to allow inbound caller ID to this endpoint.

name)#caller-id-inbound
enable
TA5K(config-call-feature Use this command to allow outband caller ID from this

name)#caller-id-outband endpoint.
enable
65K110FTTP-29A 109
Revision A
Table 2-32. Call Feature Profile Options (Continued)
Command Description
TA5K(config-call-feature Use this command to allow the initiation of three-way

name)#conference conference calls. This feature allows multiple parties to
[enable|local] communicate at the same time on the same line.
TA5K(config-call-feature Use this command to determine if an Emergency call will be

name)#emergency-number onhook dropped or remain open when the call originator goes on-
[inhibit|allow] hook.
■ If set to allow, the call will be dropped if the call
originator hangs up. This is the default mode.
■ If set to inhibit, the call will remain open until the
Emergency Operator terminates the call. While the
call is held-up, the local phone will ring and the
Emergency Operator will hear a ringback tone.
TA5K(config-call-feature Use this command to set the maximum duration, in minutes,
name)#emergency-number an inhibited call may remain open by an Emergency Operator.
ringing-timeout <1-60>
What’s Next
Continue to Section 2.3.18, “Provision the OMCI SIP Users” on page 111.
110 65K110FTTP-29A
Revision A
2.3.18 Provision the OMCI SIP Users

All profiles (media, CODEC, call-feature, etc.) can be shared across multiple voice users. To
create a SIP user, complete the following steps:
1. Access the SIP Voice User Command Set.
TA5K(config)#voice user sip <ont-id/0/[1-16]>@<shelf/slot/port>
2. Assign a description for the voice user.
TA5K(config-voice-user-sip x/x/x@x/x/x)#description WORD
3. Connect the voice user to one or more profiles.
Refer to Table 2-33 for a list of connection options.
Table 2-33. SIP Voice User Options
Profile Command
CODEC TA5K(config-voice-user-sip x/x/x@x/x/x)#connect profile codec-

list word
Dialing TA5K(config-voice-user-sip x/x/x@x/x/x)#connect profile dialing

word
Call Feature TA5K(config-voice-user-sip x/x/x@x/x/x)#connect profile call-

feature word
Media TA5K(config-voice-user-sip x/x/x@x/x/x)#connect profile media

word
4. Connect the SIP voice user to the FXS port.

TA5K(config-voice-user-sip x/x/x@x/x/x)#connect fxs <ont-id/0/
fxs_Port>@<shelf/slot/port>
5. Assign an identity (phone number) for the SIP voice user.
TA5K(config-voice-user-sip x/x/x@x/x/x)#identity <value>
6. Specify the SIP trunk through which to register the server. The trunk is specified in the
format Txx.
TA5K(config-voice-user-sip x/x/x@x/x/x)#sip-trunk Txx
7. Set the user name that will be required as authentication for registration to the SIP server.
TA5K(config-voice-user-sip x/x/x@x/x/x)#auth-name <value>
8. Set the password that will be required as authentication for registration to the SIP server.
TA5K(config-voice-user-sip x/x/x@x/x/x)#password <value>
9. Enable the SIP voice user.
TA5K(config-voice-user-sip x/x/x@x/x/x)#no shutdown
10. Verify the parameters of the SIP user.
If mandatory parameters are missing, there is conflicting configuration, or the ONT
returns an error while provisioning, last error string displays the appropriate cause of
error and puts the voice user in operationally down state. For example if no FXS port is
connected to a SIP voice user, it operationally goes down and displays informative
message in last error.
65K110FTTP-29A 111
Revision A
TA5K(config-voice-user-sip x/x/x@x/x/x)#do show voice user sip <RD_ID/

0/[1-16]@<shelf/slot/port>
voice user sip 1/0/1@1/16/1 is IS and DOWN
Description :
Subscriber Identity : 3012001635
Fxs Connection : 1/0/10@1/16/1
Registration State : Init
Codec in Use : na
Session : Idle
Last error : Voice user not connected to valid FXS port
11. Check the status of all SIP voice users running on a card.
TA5K(config-voice-user-sip x/x/x@x/x/x)#do show table voice user sip
<shelf/slot/port>
Subscriber End-point Admin Oper Registration
Identity Index State State State Session
---------- ----------- ------ ------ -------- --------
3012001635 1/0/1@1/16/1 IS DOWN na na
What’s Next
■ For OMCI SIP, this completes provisioning. Services should be up and running. To
■ To provision for Shapers, continue to Section 8, “Traffic Management” on page 331.
112 65K110FTTP-29A
Revision A
2.3.19 Provision OMCI MGCP Endpoints

To create the MGCP endpoints, complete the following:
1. Access the Voice User Command Set.
ChassisID(config)#voice user mgcp <ont-id/0/[1-16]>@<shelf/slot/port>
2. Specify the physical port on the selected Access Module to which the user is associated.
ChassisID(config-voice user-mgcp x/x/x@x/x/x)#connect fxs <ont-id/0/
fxs-port>@<shelf/slot/port>
3. Connect the MGCP voice user to the MGCP profile.
ChassisID(config-voice user-mgcp x/x/x@x/x/x)#connect profile mgcp WORD
4. Enable the VOIP user.
ChassisID(config-voice user-sip x/x/x@x/x/x)#no shutdown
ChassisID(config-voice user-sip x/x/x@x/x/x)#exit
What’s Next
For OMCI MGCP, this completes provisioning. Services should be up and running. To
65K110FTTP-29A 113
Revision A
2.3.20 Provision GR-303

To provision for GR-303, complete the following steps:
gGR-303
NOTE
is a function of the DS1 Voice Gateway Access Module.

2. Access the GR-303 Interface Configuration Command Set.
ChassisID(config)#interface gr303-group <shelf/slot/group>
3. Assign a name to the interface group.
ChassisID(config-gr303-group x/x/x)#description LINE
4. Set the switch-type.
ChassisID(config-gr303-group x/x/x)#switch-type [gte-gtd5|lucent-
5ess|metaswitch|nortel-dms|siemens-ewsd]
5. Assign the required physical ports being used as the primary, secondary, and any other
GR-303 links.
a. Set the physical port being used as the primary GR-303 link.
ChassisID(config-gr303-group x/x/x)#connect interface t1 <shelf/
slot/port> primary
b. Set the physical port being used as the secondary GR-303 link.
slot/port> secondary
c. Set the physical port being used as the normal GR-303 link.
slot/port> normal <3-28>
d. Repeat step c to assign the next GR-303 link.
gThe NOTE
ordering is important. The port of the voice switch and port of the DS1 Voice Gateway
assigned to the same GR-303 link must be physically connected.
6. Connect the Call Reference Value (CRV) to the FXS interface.

ChassisID(config-gr303-group x/x/x)#connect interface crv <1-2048>
interface fxs <1/0/fxs port>@<shelf/slot/port>.gigabit-ethernet
ChassisID(config-gr303-group x/x/x)#exit
What’s Next
For GR-303 voice, this completes provisioning. Services should be up and running. To
114 65K110FTTP-29A
Revision A
Provisioning using the Web GUI - Scope of this Section
3 Provisioning using the Web GUI

This section provides provisioning for GPON using the Web GUI.
g NOTE
3.2 In this Section

3.3 Provisioning 116
65K110FTTP-29A 115
Revision A
Provisioning using the Web GUI - Provisioning
3.3 Provisioning
To provision FTTP, complete the following using the Web GUI:
■ “OLT/PON Provisioning” below
■ “Service Provisioning” on page 130

Before you can begin provisioning services, it is first necessary to enable the OLT and PON
along with discovering the ONT you will be provisioning for triple-play.

1. Navigate to the OLT Card Provisioning menu.
Modules > GPON OLT > Provisioning > Card
Figure 3-1. OLT Card Service Provisioning
2. Set the card service state to IS.

3. Click Apply.
116 65K110FTTP-29A
Revision A
3.3.1.2 Provision the PON

g NOTE
This is a general set of instructions to provision the PON. Optional settings are available. For
“Hazard and Advisory Symbols” on page Intro-23.
1. Navigate to the OLT PON Provisioning menu.

Modules > GPON OLT > Provisioning > PON
Figure 3-2. PON Provisioning
2. Set the PON Service State to IS on the selected PON number.

3. Set the Activation Mode.
g NOTE
Notate the Activation Mode for each provisioned PON. This information will be used later when
discovering the ONT. The default mode is Auto-Discovery. For more details about the available
modes, refer to Section 13, “Activation Mode” on page 391.
■ Registration ID, for the ADTRAN 424RG, is performed by Serial Number Activation. This
occurs when the ONT is “Discovered” by the OLT.
If AOE Auto Upgrade is active, a new ONT installation will be detected and a fast blinking
FIBER LED will indicate a new software download has commenced. This may take 5 - 10
minutes to complete. For the differences on Lock Serial Number and Unlock Serial
Number, refer to Section 13, “Activation Mode” on page 391.
■ Select a range indication for the PON.
65K110FTTP-29A 117
Revision A
g NOTE
■ Standard is the default range.
support up to 32 ONTs per PON. For the GPON 4X SFP OLT, the range is reduced by
approximately 10km, when the 64 ONT split is used. The GPON OLT 8X SFP
(P/N 1187503F1) supports up to 64 ONTs per PON.
■ Maximum range is not supported for the GPON OLT 8X SFP (P/N 1187503F1).
4. Refer to Table 3-2 for range descriptions.
Table 3-2. Range Description
Range Description
extended Extended range is 34/37.5km.
maximum Maximum range is 60km.
standard Standard range is 20km.
5. Enable or disable FEC for downstream traffic toward the customer ONT.
FEC helps eliminate packet loss by providing redundancy in the signal. If downstream
FEC is enabled, the ONT that supports FEC decoding capability should apply FEC
decoding and error-correction to the downstream data flow. The ONT that does not
support FEC decoding skips the parity bytes and does not apply FEC decoding and error-
correction to the downstream data flow.
FEC decoding does not attempt to correct any transmission errors.
The activation and deactivation of FEC operates regardless of port status. The behavior
during switch-over is undefined and is likely to cause a momentary loss of data.
6. Click Apply.
What’s Next
■ For Registration-ID activation, continue to Section 3.3.1.3, “Enter the Registration-ID” on
page 119.
■ For all other activation modes, continue to Section 3.3.1.4, “Discover the ONT” on
page 129.
118 65K110FTTP-29A
Revision A
3.3.1.3 Enter the Registration-ID

The registration-ID steps vary depending on your ONT. Use Table 3-3 to navigate to your next
step.
Table 3-3. Registration-ID
Registration-ID Procedure See Page
Section 3.3.1.3.2, “Registration-ID Entry for Total Access 421x /Total Access 122
421xw”
Section 3.3.1.3.3, “Registration-ID Entry for Total Access 3xx Residential 124
Gateway”
Section 3.3.1.3.4, “Registration-ID Entry for Total Access 324RG and 334RG” 126
Section 3.3.1.3.5, “Registration-ID Entry for Total Access 324 3rd Generation 127
and Total Access 374”
65K110FTTP-29A 119
Revision A

To enter a Registration-ID for the ONT, complete the following steps:
1. Power down the ONT (if powered on).
2. If necessary, disconnect the subscriber POTS wiring.
4. Power on the ONT and wait until the unit is ready to accept the Registration-ID. ONT
status indications are provided in Table 3-4.
Table 3-4. ONT Status
Status LED Status
Unit is booting up Flashing green, then solid yellow
Unit has booted Off for the initial LED status
Unit is ready to accept the Registration-ID Flashing red and green quickly
5. Within 10 seconds, pick up the phone receiver. A dial tone should be heard.
g NOTE
If the Registration-ID is not entered within 300 seconds, hang up the receiver and return to
step 1.
6. Enter: *001234*XXXXXXXXXX*XXXXXXXXXX* (where XXXXXXXXXX is the Registration-ID for

this site).
7. Wait for verification that the ONT understood and accepted the Registration-ID as
indicated by the ONT LEDs listed in Table 3-5.
Table 3-5. Registration-ID Acceptance
Status Description
Success If verification succeeds, the following attributes

apply:
■ LED: Flashing green
■ Tone: Stutter dialtone
■ Caller-ID: **Accepted** and echoing the
Registration-ID
Failure If verification fails, the following attributes apply:

■ LED: Flashing red
■ Tone: Fast busy
■ Caller-ID: If the pattern is entered incorrectly,
**Invalid** appears. If the first ID does not match
the second, **Re-enter** appears
If a failure occurs, hang up and return to step 5.
8. Hang up phone.
120 65K110FTTP-29A
Revision A
9. Wait for validation of the Registration-ID as indicated by the ONT LEDs listed in
Table 3-6.
Table 3-6. Registration-ID Status
Status LED Description
Discovery (validation pending) Flashing yellow
Success Solid green
Failure Solid red
Dark Fiber Off
10. If success, registration is complete. Disconnect phone & connect house wiring.
What’s Next
65K110FTTP-29A 121
Revision A
3.3.1.3.2 Registration-ID Entry for Total Access 421x /Total Access 421xw
To enter a Registration-ID to the SFU ONT (Total Access 421x or Total Access 421xw),
2. If necessary, disconnect residence POTS wiring.
4. Power on the ONT and wait for the ONT to come up within 2 minutes.
5. Perform a 10 second reset on the ONT by pushing the reset button.
6. Wait for the OMCI LED to start flashing.
7. Wait for the OMCI LED to stop flashing, and the SYS LED will come on solid.
8. Once the SYS LED is on solid, wait 40-45 seconds for the POTS LED to start flashing.
9. Take the butt set off-hook. For activating the prompt tone for Registration-ID, dial ‘*0’. A
continuous prompt tone of 450 Hz should be heard.
g NOTE
If the Registration-ID is not entered within 300 seconds, hang up and return to step 1.

b. Enter the identical Registration-ID again and press # (as seen in the previous step).
Again take the phone off-hook and repeat step 7.
Registration-ID by placing the phone on-hook. Again take the phone off-hook and repeat
step 9.
13. If OK tone is played, continuously with small intervals of approximately 2 to 4 seconds,
the Registration-ID is accepted. Place the phone on-hook, connect fiber and reboot the
ONT.
OLT, the ONT will successfully be registered with the OLT. The Network LED on the ONT
will be ON at the end of the process. Refer to Table 3-7 on page 3-123 for a list of LEDs.
If the Registration-ID entered on the ONT does not match the Registration-ID provisioned
on the OLT, the SYS LED will keep blinking during the ONT boot-up to indicate the ONT
is trying to register itself but cannot complete the process successfully. Refer to Table 3-7
on page 3-123 for a list of LEDs.
122 65K110FTTP-29A
Revision A
Total Access 421x/Total Access 421xw LEDs

The ONT provides front panel LEDs to display status information. The ONT LEDs and status
descriptions are shown in Table 3-7.
Table 3-7. Front Panel LEDs
Label Status Description
POWER  Off No power

 Green Power is On
BATT  Off No battery power

 Green Battery installed and charged
 Green Flashing Battery charging, or operating in depleted condition
SYS  Off Power on, fully functional and ranged and/or

synchronized
 Green Hardware is 100% operational
 Green Flashing PON is in ranging and synchronizing mode
 Red System failed to boot
DATA  Off No data on Ethernet port

 Green Data being processed on Ethernet port
NTWK  Off No data being passed

 Green Link between Network and ONT established
OMCI  Off Dark Fiber

 Green Ranged, Synchronized, and Up on the PON
 Green Flashing Communicating with OLT and Ranging
POTS  Off Telephone is on hook

1/2 Green At lease one port is Off Hook

 Green Flashing At least one port off-hook for one-hour or more
LINK/  Off Ethernet port not active

CARRIER Green Connection between ONT and CPE router established

 Green Flashing Traffic on Ethernet port
10/100  Off Ethernet rate up to 10Mbps

 Green Ethernet rate up to 100mbps
 Green Flashing Ethernet rate up to 1000Mbps
What’s Next
65K110FTTP-29A 123
Revision A
3.3.1.3.3 Registration-ID Entry for Total Access 3xx Residential Gateway

There are two methods where the OLT will register the ONT:
■ Automatic Serial Number Activation. This is performed by the OLT when the ONT is
“Discovered”.
■ Registration ID using Telco Butt Set Activation (see below).
Set Registration ID Activation using a Telco Butt Set

following steps:
1. Verify the PON fiber-feed is disconnected from the ONT.
2. Press the RESET button on a previously powered-up ONT, or perform an initial power-up
on a new ONT.
3. Wait approximately one minute for the start-up to complete, (PWR LED is ON and solid;
LOS LED is ON and solid).
4. Attach the Butt Set to the POTS Port 1 and go off-hook.
5. Observe that the reorder tone (fast busy) is generated.
g NOTE
The Reorder tone is continuously played after going off-hook until the valid Registration ID
password is dialed. See Step 6.
6. On the keypad, dial the registration ID password: *123#.

7. Observe that the special information tone is generated.
g NOTE
This is a fast “Hi-Mid--Low” tone that repeats.
8. On the keypad, press * to initiate the Registration ID input sequence.

9. Observe that the special information tone stops.
10. Dial the remainder of the Registration ID sequence: 10 digit plus #.
g NOTE
If the Registration ID entered is not valid, the Special Information tone will be re-played. An
incorrect Registration ID can be changed by re-entering the Registration ID password (*123#)
and then re-entering a correct Registration ID sequence.
11. Wait 2 seconds. A confirmation tone is generated by the Butt Test Set. This indicates a
valid Registration ID was entered.
12. Hang-up the Butt Set.
13. Push the RESET button, or power-cycle the ONT.
14. Connect the fiber between the PON and ONT.
15. The ONT should begin Ranging with the new Registration ID. The PON LED will blink
during Ranging. The PON LED will become solid after 20-30 seconds. This indicates the
ONT has activated.
16. Once the ONT has Ranged on the PON, the Butt Set Registration ID process is disabled.
124 65K110FTTP-29A
Revision A
g NOTE
If AOE Auto Upgrade is active, a new ONT installation will be detected and a fast blinking PON
LED will indicate a new software download has commenced. This may take 5 - 10 minutes to
complete.
What’s Next
65K110FTTP-29A 125
Revision A
3.3.1.3.4 Registration-ID Entry for Total Access 324RG and 334RG

following steps:
2. If necessary, disconnect residence POTS wiring.
3. Connect DTMF phone to the first POTS port.
4. Power on the ONT and wait for the ONT to come up. ONT comes up in 25 seconds.
5. Perform 10 sec reset on the ONT by pushing the reset button.
6. Wait 40-45 seconds for the POTS LED to start flashing.
7. Able to get prompt tone even after 300 seconds by dialing '*0'.
8. Take the butt set off-hook. For activating the prompt tone for the Registration-ID, dial '*0'.
A continuous prompt tone of 450 Hz should be heard.
b. Enter the identical Registration-ID again and press # (as performed in the previous
step).
Again take the phone off-hook and repeat step7.
Registration-ID by placing the phone on-hook. Again take the phone off-hook and
repeating step 8.
12. If OK tone is played, continuously with small intervals (approximately 2 to 4 seconds),
then Registration-ID is accepted. Place the phone on-hook, connect fiber and reboot the
ONT.
OLT, the ONT will successfully be registered with the OLT.
What’s Next
126 65K110FTTP-29A
Revision A
Access 374
1. Verify the ONT is DISCONNECTED from the PON and reset or power-up the unit.
2. Wait approximately 1 minute for start-up to complete. The LEDs will provide the following
indications:
■ Total Access 374
♦ FAIL LED illuminated, solid
■ Total Access 324 3rd Generation
♦ LOS LED illuminated, solid
3. Attach the Butt Set or DTMF phone to POTS port #1 and go off-hook.
4. Verify that reorder tone (fast busy) is present.
5. Dial the registration ID entry code - *123#.
6. A special information tone will be played to indicate the ONT is ready to accept the
registration ID.
7. Enter an asterisk (*), wait for the tone to stop, then enter the 10 digit registration ID, then
press on the pound key (#).
8. You should now hear three tones, indicating its ok to hang up the phone/butt set.
9. Reset the ONT, and connect to the PON. Once ONT activation is successful, the MGT,
NET, and PWR LEDs should all illuminate green.
Guidelines
Use the following guidelines when provisioning Registration-ID:
■ Fast busy is continuously played until the asterisk (*) key is pressed.
■ If the registration ID is not valid, the special information tone will be played.
■ After entering *123#, the registration ID sequence can be entered (*10-digits#) and
changed by re-entering a new registration ID sequence as many times as necessary. The
confirmation tone is played each time a valid registration ID sequence is entered.
■ Once the ONT is ranged, the registration ID process is disables.
What’s Next
65K110FTTP-29A 127
Revision A
g NOTE
This procedure is not applicable to the following Total Access 4xx products:
Total Access 421x/421xw and the Total Access 400.
1. Plug in both power and fiber to the ONT and allow the ONT to “range.” This process will
take several seconds. The LEDs will indicate that the process is complete.
2. Connect an RJ-45 Ethernet cable from a laptop PC to the Ethernet LAN interface on the
401 ONT. See Figure 3-3 for the location of the LAN interface.
3. Open a web browser on the laptop.
4. Enter the IP address 192.168.1.1 in the address window. A popup window appears that
requests user name and password.
5. Enter the use name and password, as follows:
■ User name: admin
■ Password: admin
The web GUI screen appears in your web browser (see Figure 3-3).
Figure 3-3. 401 Web GUI Display
6. Navigate to Management>SLID Configuration (see the menu tree in Figure 3-3).

7. Enter the Reg ID in the box labeled “Input New SLID.” Press <SAVE>.
8. Reboot the ONT using the option in the web GUI.
This applies the configuration.
What’s Next
128 65K110FTTP-29A
Revision A

1. Navigate to the ONT Provisioning menu.
Modules > GPON OLT > Provisioning > ONT
Figure 3-4. ONT Provisioning
2. Discover the ONT. Follow the steps in Table 3-8 for your previously chosen activation
mode.
g NOTE
If you are uncertain of your selected Activation Mode, refer to the PON Provisioning menu:
Modules > GPON OLT > Provisioning > PON.
Table 3-8. ONT Discovery Method
Registration-ID
Lock-SN/
Manual Auto-Discovery Auto-Activate
Registration-ID
Unlock-SN
1. In the Create ONT 1. In the Create ONT 1. In the Create ONT 1. In the Create ONT
section, select an section, select an section, select an section, select an
unused number unused number unused number unused number
for your ONT. for your ONT. for your ONT. for your ONT.
2. In the Provisioned 2. Select your serial 2. The ONT’s serial 2. In the Registration
Serial Number, number from the number should ID, enter the
enter the ONT’s list of Unused automatically ONT’s registration
serial number. Serial Numbers. appear. If not, ID.
3. Set the Admin 3. Click Create. click Refresh. 3. Set the Admin
State to IS. 4. Set the Admin 3. Set the Admin State to IS.
4. Click Apply. State to IS. State to IS. 4. Click Apply.
5. Click Apply. 4. Click Apply.
65K110FTTP-29A 129
Revision A

■ 3.3.2.1 below
■ Section 3.3.2.4, “RF-Video” on page 138
3.3.2.1 Voice
3.3.2.1.1 SIP
and terminate multimed sessions.
g NOTE
If your deployment uses a Remote Gateway ONT, OMCI (Voice FTTx) is the only supported
option.
3.3.2.1.2 MGCP
g NOTE
option.
3.3.2.1.3 GR-303
g NOTE
A Total Access 5000 Voice Gateway Module is required when provisioning GR-303.
130 65K110FTTP-29A
Revision A

of your voice option, refer to Section 3.3.2.1, “Voice” on page 130.
Option See Page
Section 3.3.2.1.5, “SIP OMCI Voice” Below
Section 3.3.2.1.6, “SIP Non-OMCI Voice” 132
Section 3.3.2.1.7, “MGCP OMCI Voice” 133
Section 3.3.2.1.8, “MGCP Non-OMCI Voice” 134
Section 3.3.2.1.9, “GR-303 Voice” 135

To provision for voice, complete the following steps:
g NOTE
This is a general set of instructions to turn up SIP OMCI voice. Optional settings are available.

65K110FTTP-29A 131
Revision A

g NOTE
This is a general set of instructions to turn up SIP Non-OMCI voice. Optional settings are
documents listed in “Hazard and Advisory Symbols” on page Intro-23.

132 65K110FTTP-29A
Revision A

g NOTE
This is a general set of instructions to turn up MGCP OMCI voice. Optional settings are

65K110FTTP-29A 133
Revision A

g NOTE
This is a general set of instructions to turn up MGCP Non-OMCI voice. Optional settings are

134 65K110FTTP-29A
Revision A
3.3.2.1.9 GR-303 Voice

g NOTE
This is a general set of instructions to turn up GR-303 voice. Optional settings are available.
65K110FTTP-29A 135
Revision A
3.3.2.2 Data
g NOTE
This is a general set of instructions to turn up data. Optional settings are available. For

136 65K110FTTP-29A
Revision A
3.3.2.3 Video
g NOTE
This is a general set of instructions to turn up video. Optional settings are available. For

65K110FTTP-29A 137
Revision A
3.3.2.4 RF-Video
To provision for RF-Video, complete the following:
g NOTE
This is a general set of instructions to turn up RF-video. Optional settings are available. For
1. Section 3.3.5, “Provision the Port on the ONT” on page 146.
138 65K110FTTP-29A
Revision A
3.3.2.5 TLS
TLS enables the user to tag-switch through the system. The user can send traffic without MAC
Security or MAC Limits. Proxy ARP will be disabled as well, so the devices will respond with
their own ARP. Using TLS removes the ability to use IGMP replication on this particular port.
Since the flow will be tag switched up to the network, the VLANs must be configured in a way
that an outer VLAN appears only on a single access module within the entire system. The
inner tag (if running double tags) cannot be duplicated within the access module. If the VLAN
becomes MAC-switched, TLS no longer functions.
Refer to Table 3-10 for an available list of TLS options.
Table 3-10. EVC and TLS
Mac-Switched No Mac-Switched
Double-Tag Not Supported Double tagged TLS, N end points, S-

tag must be unique within the entire
Total Access 5000 Network. C-tag
must be unique per port.
Single-Tag Not Supported E-Line (TLS), Max of 2 endpoints,

including men-port
65K110FTTP-29A 139
Revision A
3.3.2.5.1 Select Your TLS Option

Use Table 3-9 to determine your TLS option and navigate to your next step.
Option See Page
TLS Single Tag Configuration Below
TLS Double Tag Configuration 141
3.3.2.5.2 TLS Single Tag Configuration

g NOTE
This is a general set of instructions to turn up TLS. Optional settings are available. For

140 65K110FTTP-29A
Revision A
3.3.2.5.3 TLS Double Tag Configuration

To provision TLS Double Tag, complete the following:
g NOTE
This is a general set of instructions to turn up TLS. Optional settings are available. For

65K110FTTP-29A 141
Revision A
3.3.3 Create an EVC

within a shelf.
g NOTE
The EVC for SIP/MGCP traffic will be a dedicated EVC because voice traffic requires different
To create an EVC, complete the following steps:

1. Navigate to the Create EVC section of the EVC page.
Services > EVCs > EVC > Create EVC
Figure 3-5. Create EVC
2. Enter a unique EVC name into the Name field.
g NOTE
EVC names are case sensitive.
3. Click the Create button to access the Edit EVC options. The Edit EVC screen will open
(see Figure 3-6 on page 143).
142 65K110FTTP-29A
Revision A
Figure 3-6. Edit EVC
4. Set the Admin State to Enabled.

5. Enter the S-Tag for the EVC.
Service Definition
Voice/Video/Data Enabled
Single/Double Tag TLS Disabled
7. If provisioning Single Tag TLS, continue to step 16. If provisioning for Double Tag TLS,
continue to step 8. For all other services, continue to step 10.
8. Enable double-tag-switching.
ChassisID(config-evc name)#double-tag-switched
9. If provisioning Double Tag TLS, continue to step 16. For all other services, continue to
step 10.
10. Disable the Preserve CE-VLAN ID setting on the EVC.
11. If provisioning for video, set the Subscriber IGMP Priority.
If provisioning for voice or data, skip to step 9.
12. Select the Interface Type for the MEN Port(s).
g NOTE
For Video Services, default-ethernet must be one of your MEN Ports.
13. Select A for the MEN port slot.
65K110FTTP-29A 143
Revision A
14. Enter the Port/Group numbers of the MEN Port(s). MEN Port is the upstream network
connection for the EVC.
15. Click Add.
16. Click Apply to enable the EVC.
17. The EVC should be added to the bottom of the EVC list. Verify the Status is Running, It
may take up to 10 seconds for the Status to change to Running.
18. If currently provisioning for voice or data, skip to What’s Next. If currently provisioning for
video, complete the following:
a. Select the IGMP tab.
b. An IGMP EVC connection is required for the switch module (Slot A) and each
access module. Select the required EVC name in the IGMP EVC Name drop down.
c. Select the required slot.
d. Click the Create button.
19. The IGMP EVC should be added to the bottom of the IGMP EVC list. Verify the Status is
Running, It may take up to 10 seconds for the Status to change to Running.
g NOTE
The IGMP EVC for the OLT Slot will not be running until the EVC-Map is created.
What’s Next
■ For SIP or MGCP provisioning, continue to “Set the Voice Service Mode on the ONT” on
page 3-145.
■ For video or data provisioning, continue to Section 3.3.5, “Provision the Port on the ONT”
on page 146.
■ For TLS provisioning, continue to Section 3.3.7, “Create an EVC-Map” on page 153.
144 65K110FTTP-29A
Revision A

Figure 3-8. Voice Service Mode
2. Click Level and Management IP (Subtended Host) check boxes.
g NOTE
You may have to scroll to the right to view all available options.
3. Set the POTS Service Mode.

For more details about the available modes, refer to the Total Access 5000 GPON User
Interface Guide (P/N 65K110GPON-31).
4. Set the VoIP Config Method.
Remote Gateways require the use of OMCI. For more details about the available
methods, refer to the Total Access 5000 GPON User Interface Guide
(P/N 65K110GPON-31).
5. Select static or DHCP from the IP Allocation field.
6. If using DHCP, skip to step 10.
7. If using a static IP address for ONT management, enter the IP Address.
8. If using a static IP address for ONT management, enter the Subnet Mask.
9. If using a static IP address for ONT management, enter the Gateway IP Address.
10. Click Apply.
g NOTE
To view the DHCP address, navigate to the ONT Status Screen (Modules > GPON OLT >
Status > ONT > ONT Status) and check the Subtended Host check box. Scroll to the right to
view the IP address.
What’s Next
For SIP, MGCP, GR-303 provisioning, continue to Section 3.3.5, “Provision the Port on the
ONT” on page 146.
65K110FTTP-29A 145
Revision A
g NOTE
If provisioning data and video on the same port, the ONT port only needs to be enabled once.
1. Navigate to the ONT Port Provisioning menu.

Modules > GPON OLT > Provisioning > ONT > ONT Port
Figure 3-9. ONT Port Provisioning
2. Select your PON.

3. Select your ONT.
4. Select the Port Type. Use Table 3-13 to determine your port type and navigate to your
next step.
Data/Video Non-Remote Gateway Ethernet 147
Voice All ONTs FXS 148
RF-Video All ONTs RF-Video 149
146 65K110FTTP-29A
Revision A
3.3.5.1 Ethernet
1. Set the number of MAC addresses allowed.
g NOTE
ONT.
2. Set the Service State to IS to enable the Ethernet interface of the ONT.
3. Click Apply.
What’s Next
For video or data provisioning, continue to Section 3.3.7, “Create an EVC-Map” on page 153.
65K110FTTP-29A 147
Revision A
3.3.5.2 FXS
Figure 3-11. FXS Port Provisioning
1. Adjust the Tx Gain for the FXS port between -12.0dB and +6.0dB.
2. Adjust the Rx Gain for the FXS port between -12dB and +6.0dB.
3. Set the Service State to IS to enable the FXS interface of the ONT.
4. Click Apply.
What’s Next
■ For SIP or MGCP provisioning, continue to Section 3.3.6, “Create an IP Host” on
page 151.
148 65K110FTTP-29A
Revision A
3.3.5.3 RF-Video
After selecting RF-Video as the ONT port type, complete the following
steps:
Figure 3-12. RF-Video Port Provisioning
1. Enable the video return.

2. Set the Service State to IS to enable the RF-Video interface of the ONT.
3. Click Apply.
What’s Next
For RF-Video, this completes provisioning. Services should be up and running. To provision
.
65K110FTTP-29A 149
Revision A

1. Open a new telnet window and log on to the Total Access 5000 shelf using the same user
credentials used for the Web GUI.
2. Access the Enable prompt.
ChassisID>enable
ChassisID#
6. You may now close out the telnet window.
What’s Next
page 151.
■ For video or data provisioning, continue to Section 3.3.7, “Create an EVC-Map” on
page 153.
150 65K110FTTP-29A
Revision A

1. Navigate to the IP Host Provisioning menu.
Modules > GPON OLT > Provisioning > IP Host
Figure 3-13. IP-Host Create Menu
2. Enter the IP-Host Name.

3. Click Create, the Edit/Create screen is displayed.
Figure 3-14. IP-Host Provisioning
4. Select the PON number.

5. Select the ONT.
6. In the IP-Host Name field, enter a unique name for the IP-Host.
65K110FTTP-29A 151
Revision A
g NOTE
Only two interface IP-host entities can be created per ONT. Attempts to create more than two
will be rejected.
7. Select the IP Allocation method. If set to DHCP, skip to step 9.

8. If the allocation method is set to Static, complete the following:
a. Enter the IP Address.
b. Enter the Subnet Mask.
c. Enter the Gateway.
9. If DNS is not required, skip to step 10. If DNS is required, complete the following:
a. Select Enabled.
b. Enter the default domain name of the DNS.
c. Enter the preferred DNS.
Only 2 addresses can be entered at a time. The first address becomes the preferred
DNS and the subsequent address becomes the second priority.
The DNS must be configured using IP host to resolve FQDN configured in the SIP
trunk and MGCP.
10. Click Apply in the Edit/Create section.
11. Select the Connection Type in the Create IP Host Connection section.
12. Click Create.
13. Verify your IP Host listed state is Active and that there are no errors that appear in the
Last Error column.
What’s Next
152 65K110FTTP-29A
Revision A

To create an EVC-Map, complete the following steps:
1. Access the Interface Map.
Modules > GPON OLT > Provisioning > Interface Map
Figure 3-15. EVC-Map Create
2. Enter the new EVC-Map name into the Map Name field and click the Create button.
g NOTE
An example name would be DATAMap. If there are spaces in the name, you must use quotes
around the name to use show commands.
65K110FTTP-29A 153
Revision A
Figure 3-16. EVC-Map Edit
3. Set the Service State to Active.
154 65K110FTTP-29A
Revision A
4. Select the Interface Type. Use Table 3-14 to determine the type and the steps to
complete.
Service ONT Type Steps
Data/Video Non-Remote Gigabit-Ethernet Complete the following steps:

Gateway 1. Select the OLT Port.
Remote Virtual Gigabit-Ethernet 2. Select the ONT.
Gateway 3. Select the ONT Port.
4. Select the Upstream Channel.
Voice All ONTs IP Host Select the IP Host created for this
service.
5. Select the EVC created for your selected service.

■ Forking is only supported on the Total Access 5000 GPON OLT 8X SFP Access Module
(P/N 1187503F1).
■ If provisioning for TLS, the IGMP mode must be set to transparent.
last member on this requesting interface, i.e. without sending one or more group specific
queries and waiting for its timeout.
The default IGMP proxy router IP address is 0.0.0.0.
w NOTICE!
Steps 11 - 16 are only for provisioning TLS. If you are provisioning for voice, video, or data,

14. If provisioning for Single TLS, skip to 21. If provisioning for Double Tag TLS, continue to
step 15.
15. Set the C-tag.
16. If provisioning for Double Tag TLS, continue to step 21.
17. If provisioning voice, skip to step 21. If you are provisioning for voice or data, configure
the Authentication Method. Use Table 3-15 on page 3-156 to determine the
authentication and steps required.
65K110FTTP-29A 155
Revision A
g NOTE
PPPoE does not support video services.
Table 3-15. Authentication Method
Authentication Steps
DHCPv4 only Complete the following steps:

1. Set DHCP Processing to Authenticate.
2. Set DHCPv6 Processing to Block.
3. Set PPPoE to Block.
DHCPv6 only Complete the following:

1. Set DHCP Processing to Block.
2. Set DHCPv6 Processing to Authenticate.
DHCPv4 and DHCPv6 Complete the following:

2. Set DHCPv6 Processing to Same As DHCPv4.
PPPoE Complete the following:

3. Set PPPoE to Authenticate.
18. Configure the Relay Agent. If you are unsure about supported options, contact your
network administrator. For more information on Relay Agent, refer to the Total Access
5000 GPON User Interface Guide (P/N 65K110GPON-31).
a. Enter the Circuit ID Format.
b. Enable or disable Remote ID.
c. Enter the Remote ID Format.
d. Enable or disable DHCP Option 82 Insertion.
e. Enable or disable DHCPv6 Relay Agent.
f. Enable or disable PPPoE Intermediate Agent.
19. If provisioning a data or video service on a Remote Gateway ONT, complete the following
steps:
a. Click Advanced.
156 65K110FTTP-29A
Revision A
Figure 3-17. EVC-Map Advanced
b. Select the CE-VLAN. The CE-VLAN can be typed in or selected from a drop-down
list.
20. If provisioning for video, complete the following steps. If provisioning for data, skip to step
21.
a. Click IGMP.
Figure 3-18. EVC-Map IGMP
b. Set the subscriber IGMP mode.

c. Enable Immediate Leave.
d. Set the IGMP proxy router IP address.
21. Click Apply.
22. The EVC-Map should be added to the bottom of the EVC-Map list. Verify the Status is
23. If provisioning video, return to the IGMP EVC list to verify the IGMP EVC for the OLT slot
is now Running.
65K110FTTP-29A 157
Revision A
What’s Next
■ For remote gateway, refer to the ADTRAN 400 Series Residential Gateway ONT Basic
Configuration Guide.
■ For TLS, this completes provisioning. Services should be up and running. To provision
158 65K110FTTP-29A
Revision A

All voice trunks are shared across the node, so provisioning of a trunk at the GigE SM makes
it available to all gateways.
1. Navigate to the Trunk menu.
OMCISIP – Services > Voice FTTx > SIP > Trunk
Non-OMCI SIP – Services > Voice > SIP > Trunk
Figure 3-19. SIP Trunk Create
65K110FTTP-29A 159
Revision A
2. Click Add.
3. Enter the Trunk’s 2 digital identifier following T.
4. Click OK.
5. Enter the SIP Primary Proxy IP address.
6. Enter the Primary Registrar IP address.
7. If using a secondary server, enter the SIP Secondary Proxy address.
8. If using a secondary server, enter the Secondary Registrar IP address.
further provisioning is required. For more details about the available provisioning options,
refer to the Total Access 5000 Switch Module User Interface Guide (P/N 65K110SM-31).
10. Click Apply.
What’s Next
160 65K110FTTP-29A
Revision A

1. Access the Profiles menu.
OMCI MGCP – Services > Voice FTTx > MGCP > Profiles
Non-OMCI MGCP – Services > Voice > SIP > Profiles
2. Enter the Profile Name.
g NOTE
Only one MGCP Profile is supported.
3. Click Create, the Provision MGCP Profile screen is displayed.

4. Specify the primary MGCP call agent IP address.
5. Click Apply.
What’s Next
65K110FTTP-29A 161
Revision A

call agent.
1. Navigate to the Endpoints menu.
Services > Voice > MGCP > Endpoints
2. Enter the slot number of the GPON OLT.
3. Enter a unique MGCP Endpoint Index.
4. Click Create.
5. Enter the MGCP Profile to be used by this voice user.
6. Enter the FXS port with which this MGCP endpoint is associated.
7. Click Apply.
What’s Next
162 65K110FTTP-29A
Revision A


■ Templates must have at least one number or wild card
■ The “(' ')” and “-” characters are allowed, but not inside brackets “[ ]”
■ A “,”is allowed within bracket “[ ]”, but not elsewhere
■ Wild cards (MNX) are not allowed inside brackets “[ ]
■ Order of numbers is not enforced within brackets “[ ]”
■ The “$” character is allowed, but MUST be the last character in the pattern or standalone
standalone
65K110FTTP-29A 163
Revision A


Template
■ The Template must have at least one number
■ The characters “(“”) and “-” are allowed, but not inside “[ ]”
164 65K110FTTP-29A
Revision A
■ Do not use “,” or “” inside “[ ]”

■ Wild cards (MNX) are not allowed inside “[ ]”
standalone
■ spre *3XX
■ spre *6[37]&
■ spre *82&
■ spre *7[45]$
■ spre *[56789]X

be observed:
■ Template must have at least one number (0-9)
■ Wild cards are not allowed
■ If “*” and “#” are entered, they must be the first character. They cannot be standalone
standalone
65K110FTTP-29A 165
Revision A

1. Navigate to the Dialing Profile menu.
OMCI SIP – Services > Voice FTTx > SIP > Dialing Profiles
Non-OMCI SIP – Services > Voice > SIP > Dialing Profiles
Figure 3-20. Dial Plan Provisioning
2. If you are creating a new dialing profile, enter a new profile name. The name cannot
contain the “/” character.
3. Click Add.
4. Select the dial plan type for the new dial plan.
5. Enter the Dial Plan Pattern. For Example 256-NXX-XXXX.
6. Click Apply in the Create Dial Plan section.
What’s Next
■ For OMCI SIP provisioning, continue to Section 3.3.12, “Provision the Common Profiles
166 65K110FTTP-29A
Revision A
3.3.12 Provision the Common Profiles (Optional)

Both OMCI SIP and OMCI MGCP support the use of common profiles. This feature enables
the creation of specific profiles that can be assigned to multiple users.
g NOTE
If you are unsure about these options, contact your network administrator. For more details
about the available provisioning options, refer to the Total Access 5000 Switch Module User
Interface Guide (P/N 65K110SM-31). Creating Common Profiles is optional for your network. If
these profiles are not required, continue to Section 3.3.16, “Provision the OMCI SIP Users” on
page 174.
Refer to Table 3-16 for a list of the supported profiles.
Table 3-16. Common Profiles

Profile Support See Page
Call Feature SIP 167
Media SIP/MGCP 169
Codec SIP/MGCP 170
3.3.12.1 Provision the Call Features Profile

1. Navigate to the Call Features menu.
Services > Voice FTTx > Common Profiles > Call Features
Option Description
Emergency Number Ringing Sets the maximum duration, in minutes, an inhibited call may remain
Timeout open by an Emergency Operator.
Emergency Number Onhook Determines if an Emergency call will be dropped or remain open
allow when the call originator goes on-hook.
■ If set to allow, the call will be dropped if the call originator hangs up.
This is the default mode.
■ If set to inhibit, the call will remain open until the Emergency
Operator terminates the call. While the call is held-up, the local
phone will ring and the Emergency Operator will hear a ringback
tone.
Call Waiting Enables call waiting on the subscriber port.
Caller ID Inbound Allows inbound caller ID to this endpoint.
Caller ID Outbound Allows outband caller ID from this endpoint.
65K110FTTP-29A 167
Revision A
Option Description
Transfer On Hangup Enables transfer on hangup. When transferring a call, hanging up

initiates the transfer to the destination party.
Timeout Alerting Specifies the maximum time a call is allowed to remain in the alerting
state. The shorter of this timeout or the configured maximum number
of rings will determine how long a call is allowed to ring.
Timeout Interdigit Specifies the maximum time allowed between dialed digits.
Conference Allows the initiation of three-way conference calls. This feature allows
multiple parties to communicate at the same time on the same line.
Conference Local Originator If the voice conference mode is set to local, specify the actions
Flashhook performed if the conference originator issues a flashhook once the
conference has been established.
■ The drop option specifies that the last party added to the 3-way
conference will be dropped and the call will continue between the
two remaining parties.
■ The ignore option specifies that the flashhook will be ignored. The
3-way conference will continue without interruption.
■ The split option specifies that the 3-way conference will be split into
two calls, one between the originator and the first party and one
between the originator and second party. When additional
flashhooks are issued after the split, they will toggle the originator
between the two calls.
Feature Mode Determines if voice conferencing bridging will be handled within the
unit or from a far-end conferencing server.
What’s Next
Continue to Section 3.3.12.2, “Provision the Media Profile” on page 169.
168 65K110FTTP-29A
Revision A
3.3.12.2 Provision the Media Profile

1. Navigate to the Media menu.
Services > Voice FTTx > Common Profiles > Media
Option Description
RTP Frame Packetization Configures the RTP frame packetization time in milliseconds.
Packet Delay Nominal Sets the allowable limits of latency on the network. This sets the
nominal delay time value in increments of 10 milliseconds.
RTP Packet Delay Maximum Sets the allowable limits of latency on the network. This sets the
maximum delay time value in increments of 10 milliseconds.
RTP DTMF Relay Configures the method by which RTP dial tone multi-frequency
(DTMF) events are relayed.
RTP QoS DSCP Configures the maximum RTP quality of service (QoS) parameters for
differentiated services code point (DSCP).
RTP Local Port Min Configures the starting RTP UDP port used to source RTP from the
ONT.
RTP Local Port Max Configures the starting RTP UDP port used to source RTP from the
ONT.
Fax Mode Switches to passthrough mode on fax or modem tone detection. This
command allows modem and fax calls to maintain a connection
without altering the signals with the voice improvement settings.
Echo Cancellation Improves voice qua;lity for packetized-based voice calls.
Flash Hook Min Configures the minimum time the switch hook must be held to be
interpreted as a flash.
Flash Hook Max Configures the maximum time the switch hook must be held to be
Silence Suppression Enables voice activity detection. When enabled, RTP packets will not
be sent during periods of silence.
What’s Next
Continue to Section 3.3.12.3, “Provision the Codec Profile” on page 170.
65K110FTTP-29A 169
Revision A
3.3.12.3 Provision the Codec Profile

1. Navigate to the CODEC menu.
Services > Voice FTTx > Common Profiles > Codec
Option Description
Preference Specifies the order of preference for coder-decoders used by the

CODEC list.
Codec Specifies the CODEC.
What’s Next
■ For OMCI SIP continue to Section 3.3.16, “Provision the OMCI SIP Users” on page 174.
■ For OMCI MGCP continue to Section 3.3.17, “Provision OMCI MGCP Endpoints” on
page 176.
170 65K110FTTP-29A
Revision A

perform.
1. Access the Class of Service menu.
Services > Voice > SIP > Class of Service
2. In the Class of Rules, enter a unique rule name.
3. Click Create.
4. By default all the Class of Service options are automatically provisioned with the
exception of Disable Call Waiting. Use the check box to either allow or disallow the
selected service.
For more details about the available provisioning options, refer to the Total Access 5000
Switch Module User Interface Guide (P/N 65K110SM-31).
5. Click Apply.
What’s Next
65K110FTTP-29A 171
Revision A

them.
1. Access the Global Voice menu.
Services > Voice > SIP > Options
2. Provision the options. If you are unsure about supported options, contact your network
administrator.
Switch Module User Interface Guide.
What’s Next
172 65K110FTTP-29A
Revision A

following:
1. Access the Voice User menu.
Services > Voice > SIP > Voice Users
2. Enter the user number for this voice user. This is typically the phone number associated
with this user.
3. Select the dialing profile to be used by this user. If you did not create a dialing profile, a
default profile (DEFAULT_DP) is provided.
4. Select the class of service to be used by this user. If you did not create a CoS, a default
rule (DEFAULT_COS) is provided.
5. Enter the SIP identity.
The parameters should match the SIP identity in the SIP call-router. A common practice
is to also user the customer’s phone number here. It is not necessary, however, and the
SIP identity can be any string that does not contain the following characters:
`@^[]{}\|:<>?" and <space>.
6. Enter the trunk number created previously.
7. Enter the authentication name. This is typically the phone number associated with this
user.
8. Enter the authentication password for this user.
9. Enter the index of the FXS slot/port to be associated with this user. Example: 1/2.
10. Click Apply.
What’s Next
65K110FTTP-29A 173
Revision A

1. Navigate to the Users menu.
Services > Voice FTTx > SIP > Users
Figure 3-21. SIP User Create
2. Enter the slot number.

3. Enter the GPON/AE port.
4. Enter the ONT.
5. Enter a unique identifier number.
6. Click Create. Figure 3-22 on page 175 is displayed.
174 65K110FTTP-29A
Revision A
Figure 3-22. SIP User Edit
7. Enter a description for this voice user. This is typically the phone number associated with
this user.
9. It is a common practice to also use the customer's phone number here. It is not
necessary, however, and the SIP Identity can be any string that does not contain the
following characters: `@^[]{}\|:<>?" and <space>.
11. Enter the username. This is typically the phone number associated with this user.
12. Enter the password for this user.
13. Enter the Dialling Plan Profile to be used for this voice user. ADTRAN provides a default
dialing plan profile called DEFAULT_DP.
14. Enter the Codec List Profile to be used for this voice user.
15. Enter the Media Profile to be used for this voice user.
16. Enter the Call Feature Profile to be used for this voice user.
17. Enter the FXS port connected to this voice user.
19. Click Apply.
What’s Next
For OMCI SIP, this completes provisioning. Services should be up and running. To provision
65K110FTTP-29A 175
Revision A

Services > Voice FTTx > MGCP > Endpoints
3. Enter the GPON/AE port.
4. Enter the ONT.
6. Click Create. The Provision MGCP Endpoint menu appears.
12. Click Apply.
What’s Next
176 65K110FTTP-29A
Revision A

1. Access the DS1 Voice Gateway.
DS1 VG > Provisioning > Card
2. Set the service state to In Service.
3. Set the Call Control Mode to GR-303.
4. Set the required DS1 ports to In Service.
DS1 VG > Provisioning > DS1
DS1 VG > Provisioning > GR-303 > Other Provisioning
6. Set the switch type.
7. Assign the physical ports, from step 4, being used as the primary, secondary, and normal.
DS1 VG > Provisioning > GR-303 > Switch DS1s
8. Set the number of CRVs.
DS1 VG > Provisioning > GR-303 > Subscribers
9. Set the Start CRV.
10. Set the Node.
11. Set the Slot.
12. Set the Provisioning Mode to either GPON or Active Ethernet.
13. Set the start port.
14. Click Apply.
What’s Next
65K110FTTP-29A 177
Revision A
178 65K110FTTP-29A
Revision A
Provisioning Active Ethernet using CLI - Scope of this Section
4 Provisioning Active Ethernet using CLI

the FTTP application using Active Ethernet and CLI.
g NOTE
4.2 In this Section

Sub-Section Topic See Page
65K110FTTP-29A 179
Revision A
Provisioning Active Ethernet using CLI - Provisioning
4.3 Provisioning
4.4 In this Section

To provision the OLT/PON, complete the following:
■ Section 4.4.1, “OLT/PON Provisioning” below
■ Section 4.4.2, “Service Provisioning” on page 183


2. Enable the GPON OLT module.
ChassisID(config)#no slot shutdown <shelf/slot
What’s Next
180 65K110FTTP-29A
Revision A
Provisioning Active Ethernet using CLI - In this Section

1. Access the remote device.
2. Enable the ONT interface.
ChassisID(config-ont ont-id@x/x/x)#no shutdown
ChassisID(config-ont ont-id@x/x/x)#exit
What’s Next
Continue to Section 4.4.1.3, “ONT Inband Management Provisioning” on page 182.
65K110FTTP-29A 181
Revision A
4.4.1.3 ONT Inband Management Provisioning

To provision inband management for an ONT connected to a port on the OLT, complete the
following steps:
1. Access the Global Configuration prompt.
2. Access the Gigabit-Ethernet Interface Configuration prompt.
ChassisID(config)#interface gigabit-ethernet <shelf/slot/port>
3. Set the S-tag for the subtended host.
ChassisID(config-giga-eth x/x/x)#subtended-host s-tag <2-4094>
ChassisID(config-giga-eth x/x/x)#subtended-host s-tag-priority <0-7>
5. Select the method of inband management.
Refer to Table 4-2 for the inband management options.
Static ChassisID(config-giga-eth x/x/x)#subtended-host ip Set the static IP

IP address A.B.C.D A.B.C.D address and subnet
mask for the ONT’s
inband management.
If selected, continue
to step 6.
DHCP ChassisID(config-giga-eth x/x/x)#subtended-host ip Allocate the IP

address dhcp address for the
ONT’s inband
dynamically using
DHCP.
to step 7.
6. If using a static IP address, set the default gateway for the subtended-host.
ChassisID(config-giga-eth x/x/x)#subtended-host ip default-gateway
A.B.C.D
ChassisID(config-giga-eth x/x/x)#no shutdown
8. If using a DHCP IP address, view the DHCP address for a AE subtended-host.
ChassisID(config-giga-eth x/x/x)#do show interfaces gigabit-ethernet
<shelf/slot/pon> subtended-host
182 65K110FTTP-29A
Revision A

The Total Access 5000 FTTP application supports triple-play provisioning via CLI. To begin
provisioning services, choose one of the following paths:
■ Section 4.4.2.1, “Voice” below
4.4.2.1 Voice
4.4.2.1.1 SIP
g NOTE
option.
4.4.2.1.2 MGCP
g NOTE
option.
4.4.2.1.3 GR-303
g NOTE
65K110FTTP-29A 183
Revision A

Option See Page
Section 4.4.2.1.5, “SIP OMCI Voice” 185
Section 4.4.2.1.9, “GR-303 Voice” 189
184 65K110FTTP-29A
Revision A

g NOTE
This is a general set of instructions to turn up SIP OMCI voice.

65K110FTTP-29A 185
Revision A

g NOTE
This is a general set of instructions to turn up SIP Non-OMCI voice.

186 65K110FTTP-29A
Revision A

g NOTE
This is a general set of instructions to turn up MGCP OMCI voice.

65K110FTTP-29A 187
Revision A

g NOTE
This is a general set of instructions to turn up MGCP Non-OMCI voice.

188 65K110FTTP-29A
Revision A
4.4.2.1.9 GR-303 Voice

g NOTE
This is a general set of instructions to turn up GR-303 voice.
65K110FTTP-29A 189
Revision A
4.4.2.2 Data
g NOTE
This is a general set of instructions to turn up data.

190 65K110FTTP-29A
Revision A
4.4.2.3 Video
g NOTE
This is a general set of instructions to turn up video.

65K110FTTP-29A 191
Revision A
4.4.2.4 TLS
inner tag (if running double tags) cannot be duplicated within the access module. If the VLAN
becomes MAC-switched, TLS no longer functions.
g NOTE
This is a general set of instructions to turn up TLS.

192 65K110FTTP-29A
Revision A
4.4.3 Create an EVC

within a shelf.
In a system using an S-VLAN model, each user requires a unique S-VLAN to be tag switched
throughout the system. ONTs 1-64 on slot 1 must have different VLANs than users 1-64 on
Slot 2.
g NOTE
support up to 32 ONTs per PON.
■ VLANs cannot be duplicated across other nodes.
■ The EVC for SIP/MGCP traffic will be a dedicated EVC because voice traffic requires
different Quality of Service (QoS) handling than other data traffic.
■ Changing the default IGMP EVC means also changing the default IP IGMP EVC
statement for each access module.
■ When deleting the default IGMP EVC (IGMP_EVC), ensure that all IGMP-enabled maps
associated with the IGMP EVC are disabled as well.
■ EVC names are case sensitive.
■ A default IGMP EVC (IGMP_EVC) is included in the factory default settings, it can be
modified and used or deleted.

2. Access the EVC Interface Configuration Command Set.
3. Set the S-tag for the EVC.
4. Apply this EVC to the default ethernet interface as a MEN port.
The commands listed in Table 4-4 can be used to provision the EVC to use a non-default
Metro Ethernet Network Interface.
Table 4-4. Non-Default Metro Ethernet Network Interface
Interface Command
EFM group ChassisID(config-evc name)#connect men-port efm-group [<shelf/

slot/group>|WORD]
Gigabit-Ethernet ChassisID(config-evc name)#connect men-port gigabit-ethernet

<shelf/slot/group>
65K110FTTP-29A 193
Revision A
Table 4-4. Non-Default Metro Ethernet Network Interface (Continued)
Interface Command
LAG group ChassisID(config-evc name)#connect men-port lag-group

<shelf/slot/group>

The commands listed in Table 4-5 can be used to enable or disable MAC-Switching.
Service Command Definition
Voice/Video/Data ChassisID(config-evc name)#mac-switched Enabled
Single Tag TLS ChassisID(config-evc name)#no mac-switched Disabled
6. If provisioning Single Tag TLS, continue to step 10. For all other services, continue to
step 7.
7. Configure the unit to strip the CE-VLAN tag as it is mapped to the EVC in the customer-
to-network direction.
ChassisID(config-evc name)#no preserve-ce-vlan
8. If provisioning for voice or data, skip to step 10. If provisioning for video, set a priority
value for the IGMP packets.
ChassisID(config-evc name)#subscriber igmp priority <0-7>
9. Set the IGMP version.
V2 is IGMPv2 (RFC 2236). V3 Lite is Lightweight IGMPv3 (RFC 5790).
ChassisID(config-evc name)#ip igmp version [v2|v3 lite]
10. Enable the EVC.
If currently provisioning for video, continue to step 12. If currently provisioning for voice or
data, skip to What’s Next.
12. Set the IGMP mode for the GigE SM/access module.
Refer to Table 4-6 on page 195 for a list of available subscriber modes.
194 65K110FTTP-29A
Revision A
Mode Steps
Proxy IGMP proxy can be broken down into three functions:

■ Report suppression - Intercepts, absorbs, and summarizes IGMP reports
coming from IGMP hosts. IGMP reports are relayed upstream only when
necessary, i.e. when the first user joins a multicast group, and once only per
multicast group in response to an IGMP query.
■ Last leave - Intercepts absorbs, and summarizes IGMP leaves coming from
IGMP hosts. IGMP leaves are relayed upstream only when necessary, i.e. when
the last user leaves a multicast group.
■ Query suppression - Intercepts and processes IGMP queries, in such a way that
IGMP specific queries are never sent to client ports, and IGMP general queries
are relayed only to those clients’ ports receiving at least one multicast group.
The OLT offers a unique but necessary capability in this respect. TR-156 requires
that all IGMP queries be sent over the multicast GEM port. However, the common
IGMP processing code of the Total Access 5000 access modules operates per
number of ports (or ONTs). The OLT break this TR-156 requirement by only
forwarding each proxy agent’s query to the intended ONT thereby avoiding an
IGMP query storm from causing set top box problems.
Snooping IGMP snooping is the process of listening to IGMP network traffic. Snooping allows
a network switch to listen in on the IGMP conversation between hosts and routers.
The switch maintains a map of which links need which multicast streams. These
streams can be filtered from the links that do not need them. Snooping allows a
switch to only forward multicast traffic to the links that have solicited them.
Snooping is not a recommended mode for IGMP.
Transparent IGMP transparent passes IGMP messages transparently.

g NOTE
Ports can be enabled with either snooping or proxy, with additional maps blocking IGMP.
13. Set the IGMP mode for each access module that will carry IGMP traffic.
g NOTE
If IGMP processing is enabled, all IGMP-enabled maps in the GPON OLT Access Module
must have the same setting.

g NOTE
14. Repeat step 12 - 13 for each access module that will carry IGMP traffic.
15. If the IGMP mode is set to proxy, complete the following steps:
a. Set the proxy host IP address.
65K110FTTP-29A 195
Revision A
g NOTE
The default proxy host IP address is 0.0.0.0.
ChassisID(config)#ip igmp evc WORD <shelf/slot> proxy host ip

address A.B.C.D
b. Set the proxy last-member-query interval.
The last-member-query interval controls the time-out (in milliseconds) used to
detect whether any group receivers remain on an interface after a receiver leaves a
group. If a receiver sends a leave-group message, the router sends a group-specific
query on that interface. After twice the time specified by this command plus as much
as one second longer, if no receiver responds, the router removes that interface
from the group and stops sending that group’s multicast packets to the interface.
g NOTE
The default proxy last-member query interval is 1000.

query interval <100-65535>
c. Set the proxy last-member-query count.
The last-member-query count controls the number of times the last-member-query
interval is used.
g NOTE
The default proxy last-member query count is 2.

query count <1-255>
16. Provision Multicast Content Admission Control (CAC).
The Multicast CAC feature provides the following at a PON-level:
■ A provisionable threshold for a multicast bandwidth threshold crossing alarm
(TCA). If the multicast bandwidth is above this threshold the alarm is set. Once
set, the alarm is cleared when the multicast bandwidth stays below the
threshold for at least 5 minutes.
■ A provisionable flag to control whether Multicast CAC is enabled or not. If
enabled, IGMP joins for new multicast groups are disallowed when the multicast
bandwidth is above the threshold.
a. Enable or disable Multicast Content Admission Control (CAC) flag.
ChassisID(config)#multicast-cac enable
g NOTE
Use the no form of this command to disable Multicast CAC.
b. Set the multicast bandwidth threshold for the TCA.

ChassisID(config)#thresholds multicast-bandwidth <0-n>
g NOTE
Use the no form of this command to disable TCA.
196 65K110FTTP-29A
Revision A
The upper limit is technology dependent. If you enter a value that exceeds the upper
limit, an error message will indicate the valid rate.
c. Verify the Mutlicast CAC status.
ChassisID(config)#do show interfaces gpon <shelf/slot/pon>
gpon 1/16/1 is UP and Running
Number of Configured ONTs : <number>
Number of Discovering ONTs : <number>
Number of Unrecognized ONTs : <number>
Number of Operational ONTs : <number>
Number of Available HW Resour : <number>
Longest Fiber Distance : <value>
Shortest Fiber Distance : <value>
Oversubscription Allowed : [true|false]
Multicast CAC Status : [accepting|rejecting|disabled]
Downstream Upstream
Max Provisionable BW kbps : value value
Configured PIR BW kbps : value value
Configured Fixed BW kbps : value value
Configured Assured BW kbps : value value
Available PIR BW kbps : value value
Available CIR BW kbps : value value
Current PIR BW kbps : value value
Current CIR BW kbps : value value
g NOTE
The Number of Available Hardware Resources field displays the remaining number of
resources available on the PON.
What’s Next
■ For video, data, or TLS provisioning, continue to Section 4.4.5, “Provision the Port on the
ONT” on page 199.
65K110FTTP-29A 197
Revision A

To set the voice service mode, complete the following steps:
2. Set the voice service mode for the ONT.

SIP ChassisID(config)#voice protocol ONT-ID@<shelf/slot/
port>.gigabit-ethernet sip
MGCP ChassisID(config)#voice protocol ONT-ID@<shelf/slot/
port>.gigabit-ethernet mgcp
GR-303 ChassisID(config)#voice protocol ONT-ID@<shelf/slot/
port>.gigabit-ethernet fxs-signaling
3. If provisioning OMCI SIP or OMCI MGCP, set the VoIP Config Method.
Remote Gateways require the use of OMCI.
a. Access the remote device.
b. Set the method.
ChassisID(config-remote-device ont x@x/x/x)#voip-config method
[file-retrieval|local-on|omci]
What’s Next
For OMCI SIP, Non-OMCI SIP, OMCI MGCP, Non-OMCI MGCP, or GR-303 provisioning,
continue to Section 4.4.5, “Provision the Port on the ONT” on page 199.
198 65K110FTTP-29A
Revision A
g NOTE
Select the Port Type. Use Table 4-8 to determine your port type and navigate to your next
step.
Service Type See Page
Data/Video Ethernet 199
Voice FXS 200
4.4.5.1 Ethernet
1. Access the Ethernet interface of the ONT.
g NOTE
The eth-port is the Ethernet port number on the ONT, port is the PON port on the OLT to which
ChassisID(config)#interface gigabit-ethernet <ont-id/0/eth-

port>@<shelf/slot/port>.gigabit-ethernet
2. Set the number of mac addresses allowed.
ONT.
ChassisID(config-giga-eth x/x/x@x/x/x)#mac limit <0-16>
ChassisID(config-giga-eth x/x/x@x/x/x)#exit
What’s Next
65K110FTTP-29A 199
Revision A
4.4.5.2 FXS
1. Access the FXS Interface Configuration Command Set.
ChassisID(config)#interface fxs <ont-id/0/fxs-port>@<shelf/slot/
port>.gigabit-ethernet
2. Adjust the Tx Gain for the FXS port between -12dB and 6dB.
3. Adjust the Rx Gain for the FXS port between -12dB and 6dB.
ChassisID(config-fxs x/x/x@x/x/x)#no shutdown
ChassisID(config-fxs x/x/x@x/x/x)#exit
What’s Next
page 202.
200 65K110FTTP-29A
Revision A

ChassisID(config-virtualGigabitEthernet x/x/x@x/x/x)#exit
What’s Next
65K110FTTP-29A 201
Revision A

Each gateway requires a unique IP address and an EVC-Map to associate the IP address with
a particular transport EVC. The EVC, the IP subnet, and any related IP server configurations
are typically shared among multiple gateway instances, but can vary. To create an IP Host,
1. Access the IP Host Configuration Command Set.
Substitute WORD with an alphanumeric string used to identify the IP Host. If an IP Host
g NOTE
Only two interface ip-host entities can be created per ONT. Attempts to create more than two
will be rejected.
ChassisID(config)#interface ip-host WORD ont-id@<shelf/slot/port>

2. Select the method of IP host management.
Refer to Table 4-9 for a list of IP host options.
Table 4-9. IP Host Management
IP Host Command Description
Static ChassisID(config-ip-host name ont-id@x/x/x)#ip Set the static IP

IP address A.B.C.D A.B.C.D address and subnet
mask for the IP host
interface.
Continue to step 3.
DHCP ChassisID(config-ip-host name ont-id@x/x/x)#ip Allocate the IP

address dhcp address for this IP
host interface
dynamically using
DHCP.
Continue to step 4.
3. If a static IP address is used, assign the IP address of the default gateway.

ChassisID(config-ip-host name ont-id@x/x/x)#default-gateway A.B.C.D
g NOTE
The IP address should be unique in the network.
4. Connect the IP host interface to a SIP or MGCP voice service.
ChassisID(config-ip-host name ont-id@x/x/x)#connect service [sip|mgcp]
5. Enable the IP host.
ChassisID(config-ip-host name ont-id@x/x/x)#no shutdown
ChassisID(config-ip-host name ont-id@x/x/x)#exit
What’s Next
202 65K110FTTP-29A
Revision A

The EVC-Map establishes a connection between the ONT Ethernet Port and the EVC defined,
as well as holds C-tag information, if needed. The EVC-Map specifies the criteria required for
a particular packet to be classified into the EVC as well as translation parameters for the VLAN
ID and P-Bits. The EVC-Map also provides parameters to select how MAC addresses are
authenticated and learned.
g NOTE
EVC-Map names are case sensitive.

1. Configure the name of the Map that connects to the EVC and the shelf and slot that
corresponds to the GPON client.
2. Set the priority for the traffic. It is recommended that SIP traffic be given a high priority
throughout the network. A value of 5 is normally assigned.
ChassisID(config-evc-map name x/x)#men-pri <0-7>
3. Connect the EVC-Map to the UNI port. Use Table 4-10 to determine the type and the
command to complete.
g NOTE
The eth-port is the Ethernet port # on the ONT, pon-port is the GPON port on the OLT to which
Service ONT Type Command
Data/Video/ Non-Remote Gigabit-Ethernet ChassisID(config-evc-map name x/x)#

TLS Gateway connect uni gigabit-ethernet
port>.gpon
Voice All ONTs IP Host ChassisID(config-evc-map name x/x)#

connect ip-host WORD <ont-id/0/eth-
port>@<shelf/slot/pon-port>
4. Connect the EVC-Map to the EVC.

ChassisID(config-evc-map name x/x)#connect evc WORD
g NOTE
If provisioning for TLS, the IGMP mode must be set to transparent.
ChassisID(config-evc-map name x/x)#subscriber igmp mode

[block|processing-enabled|transparent|forking]
65K110FTTP-29A 203
Revision A
last member on this requesting interface, for example, without sending one or more
group specific queries and waiting for its timeout.
ChassisID(config-evc-map name x/x)#subscriber igmp immediate-leave
The default IGMP proxy router IP address is 0.0.0.0
ChassisID(config-evc-map name x/x)#subscriber igmp proxy router ip
address A.B.C.D
w NOTICE!
Steps 10 - 14 are only for provisioning TLS. If you are provisioning for voice, video, or data,

transparent
transparent
ChassisID(config-evc-map name x/x)#subscriber arp mode transparent
13. If provisioning for Single TLS, skip to 25.
14. Set the subscriber modes.
Refer to Table 4-11 for a list of available subscriber modes.
g NOTE
Mode Steps
DHCPv4 Complete the following steps:

authenticate
block
204 65K110FTTP-29A
Revision A
Table 4-11. Subscriber Modes (Continued)
Mode Steps
DHCPv6 Complete the following:

ChassisID(config-evc-map name x/x)#subscriber access dhcp6 mode
authenticate
For a list of DHCPv6 options refer to Table 4-13.
block
PPPoE Complete the following steps:

1. Discard DHCP traffic for the EVC-Map.
block
2. Apply PPPoE for subscriber authentication for the EVC-Map.
authenticate
■ The default setting for the DHCPv6 access mode mirrors the DHCPv4 setting, therefore
DHCPv6 is enabled by default for all DHCPv4 circuits. To disable DHCPv6 on all existing
circuits of an access module enter the following command.
ChassisId(config)#force subscriber dhcpv6 disable <shelf/slot>
■ Changing the access mode does not change the relay agent settings. Refer to Section 15.,
“Configure the Relay Agent.” on page 206 for relay agent provisioning steps.
Refer to Table 4-12 for a description of the authentication modes.
Table 4-12. Authentication Mode Description
DHCP Processing Dynamic Host Configuration Protocol (DHCP) is an auto-configuration

protocol used to configure network devices in IP networks. A DHCPv4
customer uses the protocol to acquire configuration information such as IP
addresses, and default routers from the DHCP server being used by the
network. This server maintains all the available IP addresses and configu-
ration information for those addresses in the network.
DHCP supports the following options:
■ Authenticate - Indicates that the source and contents of the data will be
authorized by DHCP. This can prevent unauthorized access to the
network. ADTRAN recommends this option.
■ Block - Indicates that all unauthorized Internet Protocol V4 traffic from
unauthorized DHCP users will be blocked. All DHCP messages are
blocked from entering the network via this interface mapping.
■ Transparent - Ignores DHCPv4 processing.
■ Snoop - Indicates that any DHCPv4 will be allowed without performing
authentication.
65K110FTTP-29A 205
Revision A
Table 4-12. Authentication Mode Description (Continued)
PPPoE Processing Point to Point Protocol over Ethernet (PPPoE) processing is a network
protocol for encapsu-lating Point to Point Protocol (PPP) frames inside
Ethernet frames. PPPoE is used mainly with Digital Subscriber Lines
(DSL) modems over Ethernet. It is also used in Metro Ethernet networks.
Because Ethernet networks employ a packet-based data protocol, there is
a lack of security to protect against IP and MAC address conflicts. PPPoE
establishes a point-to-point connection over the network and then
transports data packets between these specific points or interfaces.
PPPoE supports the following options:
■ Authenticate - Indicates the MAC address of the subscriber will be
authenticated before data is accepted.
■ Block - Indicates that the subscriber will not be authenticated using
PPPoE.
■ Transparent - Indicates that no type of authentication will be used and
that all PPPoE traffic will be allowed.
Refer to Table 4-13 for a list of available access modes.
Table 4-13. DHCPv6 Access Modes
Access Mode Command Description
Authenticate ChassisID(config-evc-map name x/x)# Use DHCPv6 for authentication,

subscriber access dhcpv6 mode allow link local IPv6 packets.
authenticate
Same as ChassisId(config-evc-map name x/x)# Mirrors the DHCPv4 authentication

DHCPv4 subscriber access dhcpv6 mode same- Mode.
as-dhcpv4 This is the Default mode.
■ If DHCPv4 is set to
authenticate, link local IPv6 is
allowed and DHCPv6 is used for
authentication.
■ If DHCPv4 is set to block, link
local IPv6 will also be blocked
along with DHCPv6.
Transparent ChassisId(config-evc-map name x/x)# Ignore DHCPv6 packets. Ignore

subscriber access dhcpv6 mode link local IPv6 packets.
transparent
Block ChassisId(config-evc-map name x/x)# Discard DHCPv6 packets. Blocks

subscriber access dhcpv6 mode block link local IPv6 packets.
Snoop ChassisId(config-evc-map name x/x)# Process DHCP without performing

subscriber access dhcpv6 mode snoop authentication.
15. Configure the Relay Agent.

The Total Access 5000 products provide the option to enable a Relay Agent, on an EVC
Map, that inserts access loop identification information, in the form of Circuit/Interface ID,
Remote ID, and loop characteristic information (as defined in Broadband Forum TR-101),
206 65K110FTTP-29A
Revision A
into both DHCPv4 and DHCPv6 packets before forwarding the packets to the DHCP
server. This information is used by the DHCP server for authentication purposes.
DHCPv4 utilizes Option-82 to insert the Circuit ID, Remote ID, and loop characteristics.
DHCPv6 utilizes Option-17 to insert a vendor-specific tag containing the loop
characteristics, Option-18 to insert the Interface ID (equivalent of DHCPv4 Circuit ID) and
Option-37 to insert the Remote ID. The Interface or Circuit ID identifies the access loop
logical port on the Total Access 5000 or OSP on which the DHCP message was received.
The Remote ID uniquely identifies the user on the access loop on the Total Access 5000
on which the DHCP discovery message was received.
g NOTE
Beginning with Total Access 5000 System Release 8.7, the DHCP remote ID is the name of
the EVC Map.
The format of the Circuit/Interface ID and Remote ID is a string of variables usually

separated by characters (# . / ,etc.) and is limited to 63 total characters. Each variable
begins and ends with a dollar sign ($).
For example, for a circuit in shelf 1, slot 5, port 27, with a VLAN ID of 201. The command
below would output the Circuit ID below.
Command:
circuit-id $shelf$/$slot$/$port$/$vid$
Circuit ID:
1/5/27/201
■ There is only one "remote-id format" storage per EVC Map used for DHCP, DHCPv6
and PPPoE intermediate agent. Changing one of these affects all of the other
Remote-id formats on the EVC Map. Enabling remote-id insert on DHCP, DHCPv6
or PPPoE intermediate agent on an EVC map will enable remote-id insert for all
services on the EVC Map. DHCP and PPPoE circuit-id and DHCPv6 interface-id
format are also shared.
■ Enabling loop-characteristic insertion on DHCPv4, DHCPv6, or PPPoE will enable it
for all three protocols on that EVC Map.
Table 4-14 lists the variables supported by the NetVanta products and the information
inserted into the Circuit/Remote ID for each variable.
Table 4-14. Supported Variables
$accessnodeid$ TID/Chassis-ID if sync enabled; otherwise TID value 1

For Example: TA5000_56
$chassis-id$ TID/Chassis-ID if sync enabled; otherwise chassis-id value 1, 2

For Example: shelf_56
$cn$ Access node number
$node$ Access node number
$shelf$ Shelf number in the access node
$slot$ Slot number in the shelf
65K110FTTP-29A 207
Revision A
Table 4-14. Supported Variables (Continued)
$sn$ Slot number in the shelf
$port$ Port number is the PON number
$ont$ ONT number
$ontslot$ ONT Slot number
$ontport$ Port on ONT
$vid$ VLAN ID on the subscriber interface.
$q-vid$ VLAN ID on the subscriber interface.
$pbits$ Ethernet priority bits on the network port interface
$map$ EVC map name connected to the user sending the DHCP packets 3
For Example: data26map
$serialnum$ Returns Activated ONT serial number to CIRCUIT-ID and REMOTE-

ID fields
1. If TID - System Name Sync is enabled the chassis-id is overwritten with the TID, therefore $accessnodeid$ and
$chassis-id$ display equivalent values. If TID - System Name Sync is disabled $accessnodeid$ displays the TID
and $chassis-id$ displays the chassis-id.
2. $chassis-id$ is only supported by Total Access 5000 System Release 7.2 forward.
3. $map$ can only be used in the Remote ID.
208 65K110FTTP-29A
Revision A

Circuit ID.
b. Configure the format of the Circuit ID. Replace WORD in the following command
with the Circuit ID. The format of the Circuit ID is a string of variables usually
circuit-id WORD
remote-id
remote-id format WORD
18. Configure DHCPv6 Relay Agent Insertion.
Configure the DHCPv6 relay agent to insert a custom Circuit ID, a Remote ID and loop
characteristics into DHCPv6 packets.
g NOTE
DHCPv6 mode must be set to Authenticate, Snoop, or Same-as-DHCPv4.
19. Configure Interface ID.

Interface ID.
agent mode enable
or
agent mode same-as-dhcpv4
g NOTE
Setting the same-as-dhcpv4 option will mirror the provisioned mode of DHCPv4 option-82
relay agent as the effective mode for the DHCPv6 relay-agent.
b. Configure the format of the Interface ID. Replace WORD in the following command
with the Interface ID. The format of the Interface ID is a string of variables usually
agent interface-id format WORD
65K110FTTP-29A 209
Revision A

agent remote-id insert
agent remote-id format WORD
21. Configure PPPoE Intermediate Agent Insertion.
Configure the PPPoE relay agent to insert a custom Circuit ID, a Remote ID and loop
characteristics into PPPoE packets.
g NOTE
PPPoE mode must be set to Authenticate.

a. Enable Intermediate Agent, enabling the Intermediate Agent inserts the Circuit ID.
ChassisID(config-evc-map WORD x/x)#subscriber access pppoe
intermediate-agent
b. Configure the format of the Circuit ID. Refer to Table 4-14 on page 207 for a list of
ChassisID(config-evc-map name x/x)#subscriber access pppoe
intermediate-agent circuit-id WORD
23. Enable Intermediate Agent Remote ID insertion.
ChassisID(config-evc-map name x/x)#subscriber access dhcp pppoe
intermediate-agent remote-id
24. Apply any additional EVC-Map configurations.
g NOTE
The following configurations listed in Table 4-15 are optional and not required to pass single-
tagged traffic.
Table 4-15. Additional EVC-Map Configurations
Static IP ChassisID(config-evc-map name x/x)#subscriber Configures a Static IP

access static-ip <Subscriber IP> <Subscriber MAC> on an EVC; the
<Gateway IP> <Gateway MAC> Gateway MAC can be
left off and it resolves
through ARP or if the
MAC is entered as
00:00:00:00:00:00,
the MAC resolves
through ARP.
210 65K110FTTP-29A
Revision A
S-Tag ChassisID(config-evc-map name x/x)#men-pri <0-7> Configures the priority

Priority level of the criteria for
the associated map in
the EVC to which the
map is connected.
When maps are
configured for explicit
CoS, the P-bit value of
the EVC tag for
associated frames
can always be set to
that CoS value.
S-Tag ChassisID(config-evc-map name x/x)#men-pri Configures the S-tag

P-Bits inherit P-bits to the ingress
P-bits.
C-Tag ChassisID(config-evc-map name x/x)#men-c-tag-pri Configures the C-tag

P-Bits inherit P-bits to the ingress
P-bits.
Double ChassisID(config-evc-map name x/x)#men-c-tag Configures the inner

Tag <1-4094> VLAN tag for this
circuit and creates a
QinQ-tagged flow
towards the network
side.
C-Tag ChassisID(config-evc-map name x/x)#men-c-tag-pri Configures the priority

Priority [<0-7>|inherit] level of the MEN C-
Tag for the associated
map. When maps are
configured for explicit
CoS, the P-bit value of
the MEN C-Tag for
associated frames
can always be set to
that CoS value.
Matching ChassisID(config-evc-map name x/x)#match Matches the CE-

CE-VLAN ce-vlan-id <0-4094> VLAN-ID coming off of
the loop.
Matching ChassisID(config-evc-map name x/x)#match Configures the

CE-VLAN ce-vlan-pri <0-7> ingress matching
Priority criteria to include the
priority level within the
CE VLAN identifier or
the map. Use the no
form of this command
to remove the
matching criteria from
the map.
65K110FTTP-29A 211
Revision A
Matching ChassisID(config-evc-map name x/x)#match Configures the

Multicast [broadcast|l2cp|multicast|unicast|untagged] ingress matching
criteria to include
multicast traffic.
Network ChassisID(config-evc-map name x/x)#network- Configures the P-Bit

Ingress ingress-filter men-pri <0-7>|LIST priority (or priorities if
Filter more than one P-Bit
was provisioned using
the LIST command)
for traffic entering the
network.
MAC OUI ChassisID(config-evc-map name x/x)#match source Allows multiple

mac-address [xx:xx:xx:xx:xx:xx|xx:xx:xx:xx:xx:xx services to be
xx:xx:xx:xx:xx:xx] assigned to the same
UNI and be separated
by the
Organizationally
Unique Identifier
(OUI) portion of the
MAC address.
w NOTICE!
MAC OUI is only supported for video. If applying MAC OUI to other services, such as data, it
can stop that service from functioning properly.
25. Enable the EVC-Map.

ChassisID(config-evc-map name x/x)#no shutdown
What’s Next
212 65K110FTTP-29A
Revision A

Use the voice sip-trunk <Txx> command to activate the SIP Trunk Configuration
Command Set. <Txx>, in which 'x' represents a number 0-9, is used to identify this trunk.
If a trunk with this identifier does not already exist, a new one is created.
ChassisID(config)#voice sip-trunk <Txx>
2. Set the IP address or fully qualified domain name (FQDN) of the primary SIP server to
which the trunk will send call-related messages.
ChassisID(config-sip-trunk name)#sip proxy primary [A.B.C.D|WORD]
3. Set the primary SIP registrar full qualified domain name (FQDN) or IP address that is
based on the domain naming system (DNS) suffix.
ChassisID(config-sip-trunk name)#sip registrar primary A.B.C.D udp <0-
65535>
4. Configure the domain name.
ChassisID(config-sip-trunk name)#domain WORD
If the domain name is configured in the IP host and also in the SIP trunk, then the domain
name configured via IP host shall override the domain name configured via trunk for that
particular user. For example, if the domain name in the IP host is configured as
provider1.telco1.com and the domain name configured in the SIP trunk is configured as
provider2.telco2.com, then the domain name for this IP host shall be
provider1.telco1.com.
If the domain name is configured in the SIP trunk profile using FQDNs and the domain
name is not defined in the IP host then the domain name for all users shall be the domain
name configured in the SIP trunk.
further provisioning is required.
What’s Next
65K110FTTP-29A 213
Revision A

1. Create the MGCP profile.
ChassisID(config)#voice profile mgcp WORD
2. Specify the primary MGCP call agent host name.
TA5K(config-mgcpname)#call-agent primary <IP address>
What’s Next
214 65K110FTTP-29A
Revision A

call agent.
1. Create an endpoint and enter the endpoint configuration.
The <index> parameter is a numerical value ranging from 1 to 255 that is used to identify
the endpoint in the default naming structure.
Using the no form of this command destroys the specified endpoint, and if necessary,
disconnects it from the specified interface.
TA300(config)#voice mgcp-endpoint <index>
2. Create a textual description of the endpoint.
Using the no form of this command removes the endpoint’s description.
TA300(config-mgcp-x)#description WORD
3. If required, connect the endpoint to a physical FXS port, rather than a virtual one, on the
FTTP ONT product.
g NOTE
This command fails if the specified FXS port is already in use on another MGCP endpoint or a
configured voice user.
Using the no form of this command disconnects the endpoint from the physical FXS port
and connects it to a virtual port.
TA300(config-mgcp-<endpoint>)#connect fxs <slot/port>
4. If required, give the endpoint a specific name to be referenced by the call agent.
By default, when endpoints are created and given an index number, they are named in
the following format: aaln/x, where x is the index number.
TA300(config-mgcp-<endpoint>)#name WORD
5. If required, block caller ID information on an endpoint.
g NOTE
This does not affect caller ID delivered in the RTP stream to the FXS port.
The command blocks caller ID delivery to the connected FXS port, if the caller ID
information is presented in the MGCP signaling messages.
Using the no form of this command allows caller ID information to appear as if it is
included in the MGCP message.
TA300(config-mgcp-<endpoint>)#block-caller-id
6. Specify how long (in milliseconds) the endpoint’s battery is removed during a forward
disconnect situation.
In a forward disconnect, the call agent sends a network disconnect (osi), and the
specified forward disconnect time matches the battery behavior.
TA300(config-mgcp-<endpoint>)#fwd-disconnect delay
[250|500|750|900|1000|2000|follow-switch]
The battery behavior can also be set to follow the Class 5 switch. This depends upon the
endpoint’s RFC 2833 signaling setting. If the RFC 2833 signaling is enabled, then using
65K110FTTP-29A 215
Revision A
the follow-switch parameter means that the Class 5 switch determines the length of time
the battery is removed.
TA300(config-mgcp-<endpoint>)#fwd-disconnect delay follow-switch
What’s Next
216 65K110FTTP-29A
Revision A


■ Templates must have at least one number or wild card.
■ The “(' ')” and “-” characters are allowed, but not inside brackets “[ ]”.
■ A “,”is allowed within bracket “[ ]”, but not elsewhere.
■ Wild cards (MNX) are not allowed inside brackets “[ ]”.
■ Order of numbers is not enforced within brackets “[ ]”.
■ The “$” character is allowed, but MUST be the last character in the pattern or standalone.
standalone.
65K110FTTP-29A 217
Revision A

218 65K110FTTP-29A
Revision A

Template.
■ The Template must have at least one number.
■ The characters “(“”) and “-” are allowed, but not inside “[ ]”.
■ Do not use “,” or “” inside “[ ]”.
■ Wild cards (MNX) are not allowed inside “[ ]”.
standalone.
■ spre *3XX
■ spre *6[37]&
■ spre *82&
■ spre *7[45]$
■ spre *[56789]X
65K110FTTP-29A 219
Revision A

be observed:
■ Template must have at least one number (0-9).
standalone.

2. Create or modify a dialing profile.
ChassisID#voice profile dialing WORD
3. Provision the dial-plan options.
ChassisID(config-dialing-profile WORD)#dial-plan <type> <pattern>
[emergency-number] [external-line-code <required|prohibited>]
Refer to Table 4-16 on page 221 for a list of dial plan options.
220 65K110FTTP-29A
Revision A
Table 4-16. Dial Plan Options
Syntax Description
type The following options are available:

■ always-permitted – Always Permitted
■ internal – Internal Calls
■ national – National Calls
■ toll-free – Toll Free Calls
■ 900-number – 900 Number Calls
■ international – International Calls
■ operator-assisted – Operator Assisted Calls
■ specify-carrier – Carrier Specified
emergency-number Emergency Number designates whether this Dial Plan is designated as an

Emergency Service. When Enabled, this number is designated as an
Emergency Service number. For example, “911” is typically reserved as an
Emergency Number. Emergency Numbers can be assigned special behaviors
not normally found in other calls. For more information, refer to the voice
emergency-number onhook [inhibit|allow] command in the
Section 4.4.17, “Provision the Call Feature Profile (Optional)” on page 229.
external-line-code External Line Code describes the behavior of this Dial Plan when an External
Line Code is present. The External Line Code should be used when a
customer subscribes to the “Hosted PBX”, “Centrex” or “Business Group”
feature on the server. The External Line Code option identifies whether a Dial
Plan Pattern is expected to follow the dialing of an External Line code, which
allows for the identification of what would otherwise be contradictory dial
plans. The following options are available:
■ Prohibited – indicates that this number-complete template will not be
a user inside a company is trying to connect with another employee inside
the same company by dialing an internal four-digit extension number using
the pattern “MXXX”; if the user first dials an “8” and then the employee’s
extension, the pattern will not be matched allowing more digits to be dialed.
If the Prohibited option had not been set, the dial string would have been
sent to the server as soon as the four digits were entered. This would have
been an invalid number and would also prevent longer, external numbers
from being dialed.The Prohibited options instructs the server to complete
the number dialed only if an external line code is not dialed. This would be
of particular importance if some of the employee extensions could be
confused with outside numbers (i.e., extension 4111, or 9112).
■ Required – indicates that this number-complete template will only be
if a Dial Plan pattern of “555-XXX-XXXX” is defined as a local number, it will
only be matched (and immediately sent in the dial string to the server) if the
user first dials the external line code (i.e., “8” for these examples).
g NOTE
■ To support ten-digit and seven-digit local dialing simultaneously, either the ten-digit dial
plan must contain the area code (256-XXX-XXXX, for example) or the seven-digit dial plan
65K110FTTP-29A 221
Revision A
should not be specified. If the seven-digit dial plan is not specified, the user will have to
wait for the inter-digit timeout to expire before the call will be connected.
■ When the external-line-code option is not specified, an external line code is considered
optional. This indicates that this number-complete template will be matched regardless of
whether or not an External Line Code is present. For example, assume that in order to get
to a phone connection outside of a business, the user first must dial “8”. If a Dial Plan
pattern of “991” is defined with the External Line Code set to “Optional”, a user could get
an Emergency Operator (911) either by dialing “8911” or “911”.
4. Set the star codes for this number (call forwarding, automatic recall, etc).
ChassisID(config-dialing-profile WORD)#voice spre *XX
Refer to Table 4-17 for a list of SPRE options.
Table 4-17. SPRE Options
Syntax Description
character. For example, a “&” or a “$” character. The following options are
possible:
5. If this profile is for customers that support the "Hosted-PBX", "Centrex" or "Business
Group" feature, specify an external line code.
ChassisID(config-dialing-profile WORD)#external-line-code <pattern>
[tone <dial|stutter-dial>]
Refer to Table 4-18 for a list of External Line Code options.
Table 4-18. External Line Code Options
Syntax Description
character. For example, an “&” or a “$” character. The following options are
possible:
What’s Next
■ For OMCI SIP provisioning, continue to Section 4.4.15, “Provision the Media Profile
222 65K110FTTP-29A
Revision A

perform.
1. Access the Voice CoS Command prompt.
Use the voice class-of-service WORD command to activate the Voice CoS Command
Set. Substitute WORD with an alphanumeric string used to identify this CoS. If a CoS
TA300(config)#voice class-of-service WORD
2. If required, apply any necessary calling restrictions.
All types are enabled by default, so only “no” commands need be entered into a new CoS
entity (to deny permission to that call type). Almost all dial plan types are accepted: 900-
number, internal, international, local, national, operator-assisted, specify-carrier, toll-free,
user1, user2 and user3. Dial plan type always-permitted cannot be denied. In addition,
the [no] call-privilege all command can be used to turn on (or off) all permissions at once.
TA300(config-cos name)#[no] call-privilege <type>
TA300(config-cos name)#exit
TA300(config)#voice user <number>
5. Connect the voice user to the new class of service.
Substitute WORD with the alphanumeric string used to identify the voice class-of-service
entity created in step 1.
TA300(config-user name)#cos <name>
Repeat steps 4 - 6 for all voice users to whom the calling restrictions apply.
What’s Next
65K110FTTP-29A 223
Revision A

them.
1. Set the flashhook mode.
This command determines if flashhook events will be interpreted locally or will be
forwarded to the far end.
TA300(config)#voice flashhook mode [interpreted|transparent]
2. If the flashhook mode is set to interpreted, set the voice conference mode.
This command determines if voice conferencing bridging will be handled within the unit or
from a far-end conferencing server.
TA300(config)#voice conference mode [local|network]
3. If the voice conference mode is set to local, specify the actions performed if the
conference originator issues a flashhook once the conference has been established.
■ The drop option specifies that the last party added to the 3-way conference will be
dropped and the call will continue between the two remaining parties.
■ The ignore option specifies that the flashhook will be ignored. The 3-way conference
will continue without interruption.
■ The split option specifies that the 3-way conference will be split into two calls, one
between the originator and the first party and one between the originator and second
party. When additional flashhooks are issued after the split, they will toggle the
originator between the two calls.
TA300(config)#voice conference local originator flashhook
[drop|ignore|split]
4. Configure a global starting User Datagram Protocol (UDP) port for Realtime Transport
Protocol (RDP).
Each Access Module in the shelf will use the same starting UDP port. The default port is
10000.
TA300(config)#ip rtp udp <1026-60000>
What’s Next
224 65K110FTTP-29A
Revision A

following:
TA300(config)#voice user <NUMBER>
2. Specify the physical port on the selected access module which the user is associated.
TA300(config-user name)#connect fxs 2/<port>
3. Set the SIP identity.
The WORD parameter should match the SIP Identity in the SIP call-router. Also a
common practice to use the customer's phone number here. It is not necessary, however,
and the SIP Identity can be any string that does not contain the following characters:
`@^[]{}\|:<>?" and <space>. The <Txx> parameter identifies the trunk that this user
should use to contact the SIP server.
The auth-name and password parameters are optional.
TA300(config-user name)#sip-identity <station> <Txx> register auth-name
<username> password <password>
What’s Next
65K110FTTP-29A 225
Revision A
4.4.15 Provision the Media Profile (Optional)

1. Access the Media Profile Command Set.
TA5K(config)#voice profile media WORD
Command Description
TA5K(config-media-profile Use this command to configure the RTP frame packetization

name)#rtp frame-packetization time in milliseconds.
[10|20|30]

name)#rtp packet-delay nominal the network. This sets the nominal delay time value in

name)#rtp packet-delay maximum the network. This sets the maximum delay time value in
TA5K(config-media-profile Use this command to configure the method by which RTP

name)#rtp dtmf-relay enable dial tone multi-frequency (DTMF) events are relayed.
TA5K(config-media-profile Use this command to configure the maximum RTP quality of

name)#rtp qos dscp <0-63> service (QoS) parameters for differentiated services code
point (DSCP).
TA5K(config-media-profile Use this command to configure the starting RTP UDP port
name)#rtp local-port [<1026- used to source RTP from the ONT.
60000>|RANGE]
TA5K(config-media-profile Use this command to switch to passthrough mode on fax or

name)#fax mode modem- modem tone detection. This command allows modem and
passthrough fax calls to maintain a connection without altering the signals
with the voice improvement settings.
226 65K110FTTP-29A
Revision A
Table 4-19. Media Profile Options (Continued)
Command Description
TA5K(config-media-profile Use this command to improve voice quality for packetized-

name)#echo cancellation enable based voice calls.
TA5K(config-media-profile Use this command to configure the minimum and maximum

name)#flashhook threshold time the switch hook must be held to be interpreted as a
[<40-1550>|RANGE] flash.
TA5K(config-media-profile Use this command to enable voice activity detection. When

name)#voice-activity-detection enabled, RTP packets will not be sent during periods of
enable silence.
What’s Next
Continue to Section 4.4.16, “Provision the CODEC Profile (Optional)” on page 228.
65K110FTTP-29A 227
Revision A
4.4.16 Provision the CODEC Profile (Optional)

1. Access the CODEC Profile Command Set.
TA5K(config)#voice profile codec-list WORD
Command Description
TA5K(config-codec-list-profile Use this command to specify the order of preference for

name)#preference coder-decoders used by the CODEC list.
<1-3> codec [g711alaw|g711ulaw
|g722|g729]
What’s Next
Continue to Section 4.4.17, “Provision the Call Feature Profile (Optional)” on page 229.
228 65K110FTTP-29A
Revision A
4.4.17 Provision the Call Feature Profile (Optional)

1. Access the Call Feature Command Set.
TA5K(config)#voice profile call-feature WORD
Command Description
TA5K(config-call-feature Use this command to determine if voice conferencing

name)#feature-mode network bridging will be handled within the unit or from a far-end
conferencing server.
TA5K(config-call-feature Use this command if the voice conference mode is set to

name)#conference local local, specify the actions performed if the conference
originator flashhook originator issues a flashhook once the conference has been
[drop|ignore|split] established.
■ The drop option specifies that the last party added to the
3-way conference will be dropped and the call will continue
between the two remaining parties.
■ The ignore option specifies that the flashhook will be
ignored. The 3-way conference will continue without
interruption.
■ The split option specifies that the 3-way conference will be
split into two calls, one between the originator and the first
party and one between the originator and second party.
When additional flashhooks are issued after the split, they
will toggle the originator between the two calls.
TA5K(config-call-feature Use this command to specify the maximum time a call is

name)#timeouts alerting <0-60> allowed to remain in the alerting state. The shorter of this
timeout or the configured maximum number of rings will
determine how long a call is allowed to ring.
TA5K(config-call-feature Use this command to specify the maximum time allowed

name)#timeouts interdigit between dialed digits.
<1-16>
TA5K(config-call-feature Use this command to enable transfer on hangup. When

name)#transfer-on-hangup transferring a call, hanging up initiates the transfer to the
enable destination party.
TA5K(config-call-feature Use this command to enable call waiting on the subscriber

name)#call-waiting enable port.

name)#caller-id-inbound enable

name)#caller-id-outband enable endpoint.
65K110FTTP-29A 229
Revision A
Command Description

name)#caller-id-inbound enable

name)#caller-id-outband enable endpoint.
TA5K(config-call-feature Use this command to allow the initiation of three-way

name)#conference conference calls. This feature allows multiple parties to
[enable|local] communicate at the same time on the same line.
TA5K(config-call-feature Use this command to determine if an Emergency call will be

name)#emergency-number onhook dropped or remain open when the call originator goes on-
[inhibit|allow] hook.
■ If set to allow, the call will be dropped if the call originator
hangs up. This is the default mode.
■ If set to inhibit, the call will remain open until the
Emergency Operator terminates the call. While the call is
held-up, the local phone will ring and the Emergency
Operator will hear a ringback tone.
TA5K(config-call-feature Use this command to set the maximum duration, in minutes,

name)#emergency-number an inhibited call may remain open by an Emergency
ringing-timeout <1-60> Operator.
What’s Next
Continue to Section 4.4.18, “Provision the OMCI SIP Users” on page 231.
230 65K110FTTP-29A
Revision A

1. Access the SIP Voice User Command Set.
TA5K(config)#voice user sip <ont-id/0/[1-16]>@<shelf/slot/port>
2. Assign a description for the voice user.
TA5K(config-voice-user-sip x/x/x@x/x/x)#description WORD
3. Connect the voice user to one or more profiles.
Refer to Table 4-22 for a list of connection options.
Table 4-22. SIP Voice User Options
Profile Command
CODEC TA5K(config-voice-user-sip x/x/x@x/x/x)#connect profile codec-

list WORD
Dialing TA5K(config-voice-user-sip x/x/x@x/x/x)#connect profile dialing

WORD
Call Feature TA5K(config-voice-user-sip x/x/x@x/x/x)#connect profile call-

feature WORD
Media TA5K(config-voice-user-sip x/x/x@x/x/x)#connect profile media

WORD
4. Connect the SIP voice user to the FXS port.

TA5K(config-voice-user-sip x/x/x@x/x/x)#connect fxs <ont-id/0/
fxs_Port>@<shelf/slot/port>
5. Assign an identity (phone number) for the SIP voice user.
TA5K(config-voice-user-sip x/x/x@x/x/x)#identity <value>
6. Specify the SIP trunk through which to register the server. The trunk is specified in the
format Txx.
TA5K(config-voice-user-sip x/x/x@x/x/x)#sip-trunk Txx
7. Set the user name that will be required as authentication for registration to the SIP server.
TA5K(config-voice-user-sip x/x/x@x/x/x)#auth-name <value>
8. Set the password that will be required as authentication for registration to the SIP server.
TA5K(config-voice-user-sip x/x/x@x/x/x)#password <value>
9. Enable the SIP voice user.
TA5K(config-voice-user-sip x/x/x@x/x/x)#no shutdown
10. Verify the parameters of the SIP user.
If mandatory parameters are missing, there is conflicting configuration, or the ONT
returns an error while provisioning, last error string displays the appropriate cause of
error and puts the voice user in operationally down state. For example if no FXS port is
connected to a SIP voice user, it operationally goes down and displays informative
message in last error.
65K110FTTP-29A 231
Revision A
TA5K(config-voice-user-sip x/x/x@x/x/x)#do show voice user sip <RD_ID/

0/[1-16]@<shelf/slot/port>
voice user sip 1/0/1@1/16/1 is IS and DOWN
Description :
Subscriber Identity : 3012001635
Fxs Connection : 1/0/10@1/16/1
Registration State : Init
Codec in Use : na
Session : Idle
Last error : Voice user not connected to valid FXS port
11. Check the status of all SIP voice users running on a card.
TA5K(config-voice-user-sip x/x/x@x/x/x)#do show table voice user sip
<shelf/slot/port>
Subscriber End-point Admin Oper Registration
Identity Index State State State Session
---------- ----------- ------ ------ -------- --------
3012001635 1/0/1@1/16/1 IS DOWN na na
What’s Next
■ For OMCI SIP, this completes provisioning. Services should be up and running. To
■ To provision for shapers, continue to Section 8.3, “Shapers, GPON” on page 332.
232 65K110FTTP-29A
Revision A

To create the MGCP endpoints, complete the following:
1. Access the Voice User Command Set.
ChassisID(config)#voice user mgcp <ont-id/0/[1-16]>@<shelf/slot/port>
2. Specify the physical port on the selected Access Module to which the user is associated.
ChassisID(config-voice user-mgcp x/x/x@x/x/x)#connect fxs <ont-id/0/
fxs-port>@<shelf/slot/port>
3. Connect the MGCP voice user to the MGCP profile.
ChassisID(config-voice user-mgcp x/x/x@x/x/x)#connect profile mgcp WORD
4. Enable the VOIP user.
ChassisID(config-voice user-sip x/x/x@x/x/x)#no shutdown
ChassisID(config-voice user-sip x/x/x@x/x/x)#exit
What’s Next
65K110FTTP-29A 233
Revision A

g NOTE
GR-303 is a function of the DS1 Voice Gateway Access Module.

2. Access the GR-303 Interface Configuration Command Set.
ChassisID(config)#interface gr303-group <shelf/slot/group>
ChassisID(config-gr303-group x/x/x)#description LINE
4. Set the switch-type.
ChassisID(config-gr303-group x/x/x)#switch-type [gte-gtd5|lucent-
5ess|metaswitch|nortel-dms|siemens-ewsd]
5. Assign the required physical ports being used as the primary, secondary, and any other
GR-303 links.
a. Set the physical port being used as the primary GR-303 link.
slot/port> primary
b. Set the physical port being used as the secondary GR-303 link.
slot/port> secondary
c. Set the physical port being used as the normal GR-303 link.
slot/port> normal <3-28>
d. Repeat step c to assign the next GR-303 link.
g NOTE
The ordering is important. The port of the voice switch and port of the DS1 Voice Gateway
assigned to the same GR-303 link must be physically connected.
6. Connect the Call Reference Value (CRV) to the FXS interface.

ChassisID(config-gr303-group x/x/x)#connect interface crv <1-2048>
interface fxs <1/0/fxs port>@<shelf/slot/port>.gigabit-ethernet
ChassisID(config-gr303-group x/x/x)#exit
What’s Next
234 65K110FTTP-29A
Revision A
Provisioning Active Ethernet using the Web - Scope of this Section
5 Provisioning Active Ethernet using the Web

the FTTP application.
g NOTE
5.2 In this Section

65K110FTTP-29A 235
Revision A
Provisioning Active Ethernet using the Web - Provisioning
5.3 Provisioning
Provisioning is done in two steps. Complete the following steps when deploying an FTTP
application using the Web GUI.
■ Section 5.3.1, “OLT/PON Provisioning” below
■ Section 5.3.2, “Service Provisioning” on page 239


1. Navigate to the OLT Card Provisioning menu.
Modules > GPON OLT > Provisioning > Card
Figure 5-1. OLT Card Service Provisioning
2. Set the card service state to IS.

3. Click Apply.

g NOTE
This is a general set of instructions to provision the PON.
1. Navigate to the Active Ethernet GE Provisioning menu.

Modules > GPON OLT > Provisioning > GE
236 65K110FTTP-29A
Revision A
Figure 5-2. GE Provisioning
2. Set the port Service State to IS on the selected port number.

3. Click Apply.
What’s Next
Continue to Section 5.3.1.3, “ONT Inband Management Provisioning” on page 238.
65K110FTTP-29A 237
Revision A
5.3.1.3 ONT Inband Management Provisioning

To provision inband management for an ONT connected to a port on the OLT, complete the
following steps:
Figure 5-3. ONT Inband Management Provisioning
2. Click Subtended Host check box.

3. Set the S-tag (VLAN ID) for the subtended host.
5. Select the method of inband management (static or DHCP) from the IP Allocation drop
down.
Inband Steps Description
Static 1. Enter the IP Address for the ONT. Set the static IP
IP 2. Enter the Subnet Mask for the ONT. address, subnet
mask, and gateway
3. Enter the default Gateway IP Address for the ONT.
IP address for the
ONT’s inband
management.
DHCP When selected, you cannot enter an IP Address, Subnet Mask, or Allocate the IP
Gateway IP as these items are not applicable. address for the
ONT’s inband
management
dynamically using
DHCP.
g NOTE
To view the DHCP address, navigate to the ONT Status Screen (Modules > GPON OLT >
Status > ONT > ONT) and check the Subtended Host check box. Scroll to the right to see the
IP address.
238 65K110FTTP-29A
Revision A

■ Section 5.3.2.1, “Voice” Below
5.3.2.1 Voice
5.3.2.1.1 SIP
g NOTE
option.
5.3.2.1.2 MGCP
g NOTE
option.
5.3.2.1.3 GR-303
g NOTE
65K110FTTP-29A 239
Revision A

Option See Page
Section 5.3.2.1.5, “SIP OMCI Voice” 241
Section 5.3.2.1.9, “GR-303 Voice” 245
240 65K110FTTP-29A
Revision A

g NOTE
This is a general set of instructions to turn up SIP OMCI voice.

65K110FTTP-29A 241
Revision A

g NOTE
This is a general set of instructions to turn up SIP Non-OMCI voice.

242 65K110FTTP-29A
Revision A

g NOTE
This is a general set of instructions to turn up MGCP OMCI voice.

65K110FTTP-29A 243
Revision A

g NOTE
This is a general set of instructions to turn up MGCP Non-OMCI voice.

244 65K110FTTP-29A
Revision A
5.3.2.1.9 GR-303 Voice

g NOTE
This is a general set of instructions to turn up GR-303 voice.
65K110FTTP-29A 245
Revision A
5.3.2.2 Data
g NOTE
This is a general set of instructions to turn up data.

246 65K110FTTP-29A
Revision A
5.3.2.3 Video
g NOTE
This is a general set of instructions to turn up video.

65K110FTTP-29A 247
Revision A
5.3.3 Create an EVC

within a shelf.
g NOTE
The EVC for SIP/MGCP traffic will be a dedicated EVC because voice traffic requires different
To create an EVC, complete the following steps:

1. Navigate to the Create EVC section of the EVC page.
Services > EVCs > EVC > Create EVC
Figure 5-4. Create EVC
2. Enter a unique EVC name into the Name field.
g NOTE
3. Click the Create button to access the Edit EVC options. The Edit EVC screen (Figure 5-5
on page 249) will open.
248 65K110FTTP-29A
Revision A
4. Set the Admin State to Enabled.

5. Enter the S-Tag for the EVC.
6. Enable Mac Switching on the EVC.
7. Disable the Preserve CE-VLAN ID setting on the EVC.
8. If provisioning for video, set the Subscriber IGMP Priority.
If provisioning for voice or data, skip to step 9.
9. Select the Interface Type for the MEN Port(s).
g NOTE
For Video Services, default-ethernet must be one of your MEN Ports.
10. Select A for the MEN port slot.

11. Enter the Port/Group numbers of the MEN Port(s). MEN Port is the upstream network
connection for the EVC.
12. Click Add.
13. Click Apply to enable the EVC.
14. The EVC should be added to the bottom of the EVC list. Verify the Status is Running, It
may take up to 10 seconds for the Status to change to Running.
65K110FTTP-29A 249
Revision A
15. If currently provisioning for voice or data, skip to What’s Next. If currently provisioning for
video, complete the following:
a. Select the IGMP tab.
b. An IGMP EVC connection is required for the switch module (Slot A) and each
access module. Select the required EVC name in the IGMP EVC Name drop down.
c. Select the required slot.
d. Click the Create button.
16. The IGMP EVC should be added to the bottom of the IGMP EVC list. Verify the Status is
g NOTE
What’s Next
■ For video or data provisioning, continue to Section 5.3.5, “Provision the Port on the ONT”
on page 252.
250 65K110FTTP-29A
Revision A

Modules > GPON OLT> Provisioning > ONT
Figure 5-7. Voice Service Mode
2. Click Level and Management IP (Subtended Host) check boxes.
g NOTE
You may have to scroll to the right to view all available options.
3. Set the POTS Service Mode.

For more details about the available modes, refer to the Total Access 5000 GPON User
Interface Guide.
4. Set the VoIP Config Method.
Remote Gateways require the use of OMCI. For more details about the available
methods, refer to the Total Access 5000 GPON User Interface Guide (P/N 65K90GPON-
31).
5. If using a static IP address for ONT management, enter the IP Address.
6. If using a static IP address for ONT management, enter the Subnet Mask.
7. If using a static IP address for ONT management, enter the Gateway IP Address.
8. Click Apply.
What’s Next
For SIP, MGCP, GR-303 provisioning, continue to Section 5.3.5, “Provision the Port on the
ONT” on page 252.
65K110FTTP-29A 251
Revision A
g NOTE
1. Navigate to the ONT Port Provisioning menu.

Modules > GPON OLT > Provisioning > ONT > ONT Port
2. Select your PON.

3. Select your ONT.
4. Select the Port Type. Use Table 5-4 to determine your port type and navigate to your next
step.
Data/Video Non-Remote Gateway Ethernet Port 253

Provisioning
Voice All ONTs FXS Port Provisioning 254
252 65K110FTTP-29A
Revision A
5.3.5.1 Ethernet Port Provisioning

1. Set the number of MAC addresses allowed.
Figure 5-9. ONT Ethernet Port Provisioning
ONT.
2. Set the Service State to IS to enable the Ethernet interface of the ONT.
3. Click Apply.
What’s Next
65K110FTTP-29A 253
Revision A
5.3.5.2 FXS Port Provisioning

Figure 5-10. FXS Port Provisioning
1. Adjust the Tx Gain for the FXS port between -12.0dB and +6.0dB.
2. Adjust the Rx Gain for the FXS port between -12dB and +6.0dB.
3. Set the Service State to IS to enable the FXS interface of the ONT.
4. Click Apply.
What’s Next
page 256.
254 65K110FTTP-29A
Revision A

1. Open a new telnet window and log on to the Total Access 5000 shelf using the same user
credentials used for the Web GUI.
2. Access the Enable prompt.
ChassisID>enable
ChassisID#
6. You may now close out the telnet window.
What’s Next
page 256.
■ For video or data provisioning, continue to Section 5.3.7, “Create an EVC-Map” on
page 258.
65K110FTTP-29A 255
Revision A

1. Navigate to the IP Host Provisioning menu.
Modules > GPON OLT> Provisioning > IP Host
Figure 5-11. IP-Host Create Menu
2. Enter the IP-Host Name.

3. Click Create, the Edit/Create screen is displayed.
Figure 5-12. IP-Host Provisioning
4. Select the PON number.

5. Select the ONT.
6. In the IP-Host Name field, enter a unique name for the IP-Host.
256 65K110FTTP-29A
Revision A
g NOTE
Only two interface IP-host entities can be created per ONT. Attempts to create more than two
will be rejected.
7. Select the IP Allocation method. If set to DHCP, skip to step 9.

8. If the allocation method is set to Static, complete the following:
a. Enter the IP Address.
b. Enter the Subnet Mask.
c. Enter the Gateway.
9. If DNS is not required, skip to step 10. If DNS is required, complete the following:
a. Select Enabled.
b. Enter the default domain name of the DNS.
c. Enter the preferred DNS.
Only 2 addresses can be entered at a time. The first address becomes the preferred
DNS and the subsequent address becomes the second priority.
The DNS must be configured using IP host to resolve FQDN configured in the SIP
trunk and MGCP.
10. Click Apply in the Edit/Create section.
11. Select the Connection Type in the Create IP Host Connection section.
12. Click Create.
13. Verify your IP Host listed state is Active and that there are no errors that appear in the
Last Error column.
What’s Next
65K110FTTP-29A 257
Revision A

1. Access the Interface Map.
Modules > GPON OLT > Provisioning > Interface Map
Figure 5-13. EVC-Map Create
2. Enter the new EVC-Map name into the Map Name field and click the Create button. See
Figure 5-14 on page 259.
g NOTE
An example name would be DATAMap. If there are spaces in the name, you must use quotes
around the name to use show commands.
258 65K110FTTP-29A
Revision A
Figure 5-14. EVC-Map Edit

4. Select the Interface Type. Use Table 5-5 on page 260 to determine the type and the steps
to complete.
65K110FTTP-29A 259
Revision A
Service ONT Type Steps
Data/Video Non-Remote Gigabit-Ethernet Complete the following steps:

Gateway 1. Select the OLT Port.
Remote Virtual Gigabit-Ethernet 2. Select the ONT.
Gateway 3. Select the ONT Port.
4. Select the Upstream Channel.
Voice All ONTs IP Host Select the IP Host created for this
service.
5. Select the EVC created for your selected service.

6. If provisioning voice, skip to step 10. If you are provisioning for voice or data, configure
the Authentication Method. Use Table 5-6 to determine the authentication and steps
required.
g NOTE
Table 5-6. Authentication Method
Authentication Steps
DHCPv4 only Complete the following steps:

DHCPv6 only Complete the following:

2. Set DHCPv6 Processing to Authenticate.
DHCPv4 and DHCPv6 Complete the following:

2. Set DHCPv6 Processing to Same As DHCPv4.
PPPoE Complete the following:

3. Set PPPoE to Authenticate.
7. Configure the Relay Agent. If you are unsure about supported options, contact your
network administrator. For more information on Relay Agent, refer to the Total Access
5000 GPON User Interface Guide (P/N 65K90GPON-31)
a. Enter the Circuit ID Format.
b. Enable or disable Remote ID.
c. Enter the Remote ID Format.
260 65K110FTTP-29A
Revision A
d. Enable or disable DHCP Option 82 Insertion.

e. Enable or disable DHCPv6 Relay Agent.
f. Enable or disable PPPoE Intermediate Agent.
8. If provisioning a data or video service on a Remote Gateway ONT, complete the following
steps:
a. Click Advanced.
Figure 5-15. EVC-Map Advanced
b. Select the CE-VLAN. The CE-VLAN can be typed in or selected from a drop-down
list.
9. If provisioning for video, complete the following steps. If provisioning for data, skip to step
10.
a. Click IGMP.
Figure 5-16. EVC-Map IGMP
b. Set the subscriber IGMP mode.

c. Enable Immediate Leave.
d. Set the IGMP proxy router IP address.
10. Click Apply.
65K110FTTP-29A 261
Revision A
11. The EVC-Map should be added to the bottom of the EVC-Map list. Verify the Status is
12. If provisioning video, return to the IGMP EVC list to verify the IGMP EVC for the OLT slot
is now Running.
What’s Next
■ For remote gateway ONT video or data provisioning, continue to Section 5.3.2, “Service
Provisioning” on page 239.
262 65K110FTTP-29A
Revision A

1. Navigate to the Trunk menu (see Figure 5-17 on page 263).
OMCISIP – Services > Voice FTTx > SIP > Trunk
Non-OMCI SIP – Services > Voice > SIP > Trunk
Figure 5-17. SIP Trunk Create
65K110FTTP-29A 263
Revision A
2. Click Add.
3. Enter the Trunk’s 2 digital identifier following T.
4. Click OK.
5. Enter the SIP Primary Proxy IP address.
6. Enter the Primary Registrar IP address.
7. If using a secondary server, enter the SIP Secondary Proxy address.
8. If using a secondary server, enter the Secondary Registrar IP address.
further provisioning is required. For more details about the available provisioning options,
refer to the Total Access 5000 Switch Module User Interface Guide (P/N 65K90SM-31).
10. Click Apply.
What’s Next
For Non-OMCI and OMCI SIP provisioning, continue toSection 5.3.11, “Provision the SIP
264 65K110FTTP-29A
Revision A

1. Access the Profiles menu.
OMCI MGCP – Services > Voice FTTx > MGCP > Profiles
Non-OMCI MGCP – Services > Voice > SIP > Profiles
2. Enter the Profile Name.
g NOTE
Only one MGCP Profile is supported.
3. Click Create, the Provision MGCP Profile screen is displayed.

4. Specify the primary MGCP call agent IP address.
5. Click Apply.
What’s Next
65K110FTTP-29A 265
Revision A

call agent.
Services > Voice > MGCP > Endpoints
2. Enter the slot number of the GPON OLT.
3. Enter a unique MGCP Endpoint Index.
4. Click Create.
6. Enter the FXS port with which this MGCP endpoint is associated.
7. Click Apply.
What’s Next
266 65K110FTTP-29A
Revision A


■ Templates must have at least one number or wild card.
■ The “(' ')” and “-” characters are allowed, but not inside brackets “[ ]”.
■ A “,”is allowed within bracket “[ ]”, but not elsewhere.
■ Wild cards (MNX) are not allowed inside brackets “[ ]”.
■ Order of numbers is not enforced within brackets “[ ]”.
■ The “$” character is allowed, but MUST be the last character in the pattern or standalone.
standalone.
65K110FTTP-29A 267
Revision A

268 65K110FTTP-29A
Revision A

Template.
■ The Template must have at least one number.
■ The characters “(“”) and “-” are allowed, but not inside “[ ]”.
■ Do not use “,” or “” inside “[ ]”.
■ Wild cards (MNX) are not allowed inside “[ ]”.
standalone.
■ spre *3XX
■ spre *6[37]&
■ spre *82&
■ spre *7[45]$
■ spre *[56789]X
65K110FTTP-29A 269
Revision A

be observed:
■ Template must have at least one number (0-9).
standalone.
270 65K110FTTP-29A
Revision A

1. Navigate to the Dialing Profile menu.
OMCI SIP – Services > Voice FTTx > SIP > Dialing Profiles
Non-OMCI SIP – Services > Voice > SIP > Dialing Profiles
Figure 5-18. Dial Plan Provisioning
2. If you are creating a new dialing profile, enter a new profile name. The name cannot
contain the “/” character.
3. Click Add.
4. Select the dial plan type for the new dial plan.
5. Enter the Dial Plan Pattern. For Example 256-NXX-XXXX.
6. Click Apply in the Create Dial Plan section.
What’s Next
■ For OMCI SIP provisioning, continue to Section 5.3.12, “Provision the Common Profiles
65K110FTTP-29A 271
Revision A
5.3.12 Provision the Common Profiles (Optional)

Both OMCI SIP and OMCI MGCP support the use of common profiles. This feature enables
the creation of specific profiles that can be assigned to multiple users.
g NOTE
If you are unsure about these options, contact your network administrator. For more details
about the available provisioning options, refer to the Total Access 5000 Switch Module User
Interface Guide (P/N 65K90SM-31). Creating Common Profiles is optional for your network. If
these profiles are not required, continue to Section 5.3.16, “Provision the OMCI SIP Users” on
page 280.
Refer to Table 5-7 for a list of the supported profiles.
Table 5-7. Common Profiles

Profile Support See Page
Call Feature SIP 272
Media SIP/MGCP 274
Codec SIP/MGCP 276
5.3.12.1 Provision the Call Features Profile

1. Navigate to the Call Features menu.
Services > Voice FTTx > Common Profiles > Call Features
Option Description
Emergency Number Ringing Sets the maximum duration, in minutes, an inhibited call may remain
Timeout open by an Emergency Operator.
Emergency Number Onhook Determines if an Emergency call will be dropped or remain open
allow when the call originator goes on-hook.
■ If set to allow, the call will be dropped if the call originator hangs up.
This is the default mode.
■ If set to inhibit, the call will remain open until the Emergency
Operator terminates the call. While the call is held-up, the local
phone will ring and the Emergency Operator will hear a ringback
tone.
Call Waiting Enables call waiting on the subscriber port.
Caller ID Inbound Allows inbound caller ID to this endpoint.
Caller ID Outbound Allows outband caller ID from this endpoint.
272 65K110FTTP-29A
Revision A
Option Description
Transfer On Hangup Enables transfer on hangup. When transferring a call, hanging up

initiates the transfer to the destination party.
Timeout Alerting Specifies the maximum time a call is allowed to remain in the alerting
state. The shorter of this timeout or the configured maximum number
of rings will determine how long a call is allowed to ring.
Timeout Interdigit Specifies the maximum time allowed between dialed digits.
Conference Allows the initiation of three-way conference calls. This feature allows
multiple parties to communicate at the same time on the same line.
Conference Local Originator If the voice conference mode is set to local, specify the actions
Flashhook performed if the conference originator issues a flashhook once the
conference has been established.
■ The drop option specifies that the last party added to the 3-way
conference will be dropped and the call will continue between the
two remaining parties.
■ The ignore option specifies that the flashhook will be ignored. The
3-way conference will continue without interruption.
■ The split option specifies that the 3-way conference will be split into
two calls, one between the originator and the first party and one
between the originator and second party. When additional
flashhooks are issued after the split, they will toggle the originator
between the two calls.
Feature Mode Determines if voice conferencing bridging will be handled within the
unit or from a far-end conferencing server.
What’s Next
Continue to Section 5.3.12.2, “Provision the Media Profile” on page 274.
65K110FTTP-29A 273
Revision A
5.3.12.2 Provision the Media Profile

1. Navigate to the Media menu.
Services > Voice FTTx > Common Profiles > Media
Option Description
RTP Frame Packetization Configures the RTP frame packetization time in milliseconds.
Packet Delay Nominal Sets the allowable limits of latency on the network. This sets the
nominal delay time value in increments of 10 milliseconds.
RTP Packet Delay Maximum Sets the allowable limits of latency on the network. This sets the
maximum delay time value in increments of 10 milliseconds.
RTP DTMF Relay Configures the method by which RTP dial tone multi-frequency
(DTMF) events are relayed.
RTP QoS DSCP Configures the maximum RTP quality of service (QoS) parameters for
differentiated services code point (DSCP).
RTP Local Port Min Configures the starting RTP UDP port used to source RTP from the
ONT.
RTP Local Port Max Configures the starting RTP UDP port used to source RTP from the
ONT.
Fax Mode Switches to passthrough mode on fax or modem tone detection. This
command allows modem and fax calls to maintain a connection
without altering the signals with the voice improvement settings.
274 65K110FTTP-29A
Revision A
Table 5-9. Media Profile Options (Continued)
Option Description
Echo Cancellation Improves voice quality for packetized-based voice calls.
Flash Hook Min Configures the minimum time the switch hook must be held to be
Flash Hook Max Configures the maximum time the switch hook must be held to be
Silence Suppression Enables voice activity detection. When enabled, RTP packets will not
be sent during periods of silence.
What’s Next
Continue to Section 5.3.12.3, “Provision the Codec Profile” on page 276.
65K110FTTP-29A 275
Revision A
5.3.12.3 Provision the Codec Profile

1. Navigate to the CODEC menu.
Services > Voice FTTx > Common Profiles > Codec
Option Description
Preference Specifies the order of preference for coder-decoders used by the

CODEC list.
Codec Specifies the CODEC.
What’s Next
■ For OMCI SIP continue to Section 5.3.16, “Provision the OMCI SIP Users” on page 280.
■ For OMCI MGCP continue to Section 5.3.17, “Provision OMCI MGCP Endpoints” on
page 282.
276 65K110FTTP-29A
Revision A

perform.
1. Access the Class of Service menu.
Services > Voice > SIP > Class of Service
2. In the Class of Rules, enter a unique rule name.
3. Click Create.
4. By default all the Class of Service options are automatically provisioned with the
exception of Disable Call Waiting. Use the check box to either allow or disallow the
selected service.
5. Click Apply.
What’s Next
65K110FTTP-29A 277
Revision A

them.
1. Access the Global Voice menu.
Services > Voice > SIP > Options
2. Provision the options. If you are unsure about supported options, contact your network
administrator.
What’s Next
278 65K110FTTP-29A
Revision A

following:
1. Access the Voice User menu.
Services > Voice > SIP > Voice Users
2. Enter the user number for this voice user. This is typically the phone number associated
with this user.
3. Select the dialing profile to be used by this user. If you did not create a dialing profile, a
default profile (DEFAULT_DP) is provided.
4. Select the class of service to be used by this user. If you did not create a CoS, a default
rule (DEFAULT_COS) is provided.
The parameters should match the SIP identity in the SIP call-router. A common practice
is to also user the customer’s phone number here. It is not necessary, however, and the
SIP identity can be any string that does not contain the following characters:
`@^[]{}\|:<>?" and <space>.
7. Enter the authentication name. This is typically the phone number associated with this
user.
8. Enter the authentication password for this user.
9. Enter the index of the FXS slot/port to be associated with this user. Example: 1/2.
10. Click Apply.
What’s Next
65K110FTTP-29A 279
Revision A

1. Navigate to the Users menu.
Services > Voice FTTx > SIP > Users
Figure 5-19. SIP User Create

3. Enter the GPON/GPON OLT port.
4. Enter the ONT.
6. Click Create. The provision SIP User menu appears (seeFigure 5-20 on page 281).
280 65K110FTTP-29A
Revision A
Figure 5-20. SIP User Edit
7. Enter a description for this voice user. This is typically the phone number associated with
this user.
9. It is a common practice to also use the customer's phone number here. It is not
necessary, however, and the SIP Identity can be any string that does not contain the
following characters: `@^[]{}\|:<>?" and <space>.
11. Enter the username. This is typically the phone number associated with this user.
12. Enter the password for this user.
13. Enter the Dialling Plan Profile to be used for this voice user. ADTRAN provides a default
dialing plan profile called DEFAULT_DP.
14. Enter the Codec List Profile to be used for this voice user.
19. Click Apply.
What’s Next
For OMCI SIP, this completes provisioning. Services should be up and running. To provision
65K110FTTP-29A 281
Revision A

Services > Voice FTTx > MGCP > Endpoints
3. Enter the GPON/GPON OLT port.
4. Enter the ONT.
6. Click Create. The Provision MGCP Endpoint menu appears.
12. Click Apply.
What’s Next
282 65K110FTTP-29A
Revision A

1. Access the DS1 Voice Gateway.
DS1 VG > Provisioning > Card
2. Set the service state to In Service.
3. Set the Call Control Mode to GR-303.
4. Set the required DS1 ports to In Service.
DS1 VG > Provisioning > DS1
DS1 VG > Provisioning > GR-303 > Other Provisioning
6. Set the switch type.
7. Assign the physical ports, from step 4, being used as the primary, secondary, and normal.
DS1 VG > Provisioning > GR-303 > Switch DS1s
8. Set the number of CRVs.
DS1 VG > Provisioning > GR-303 > Subscribers
9. Set the Start CRV.
10. Set the Node.
11. Set the Slot.
12. Set the Provisioning Mode to either GPON or Active Ethernet.
13. Set the start port.
14. Click Apply.
What’s Next
65K110FTTP-29A 283
Revision A
284 65K110FTTP-29A
Revision A
GPON Configurations - Scope of this Section
6 GPON Configurations

This section provides examples of common Total Access 5000 GPON configurations.
g NOTE
6.2 In this Section

6.3 TLS Configuration Examples 304
65K110FTTP-29A 285
Revision A
GPON Configurations - VLAN/TLS/IPTV Examples
6.3 VLAN/TLS/IPTV Examples

This section includes provisioning examples for the following:
■ Section 6.3.1, “1:1 Customer VLAN (C-VLAN) Examples” on page 287
■ Section 6.3.2, “N:1 Service VLAN (S-VLAN) Examples” on page 290
■ Section 6.3.3, “Hybrid N+1:1 Combined VLAN Examples” on page 297
■ Section 6.4.1, “TLS Example 1” on page 304
■ Section 6.4.2, “TLS Example 2” on page 305
■ Section 6.4.3, “IPTV Configuration Examples” on page 307
286 65K110FTTP-29A
Revision A
6.3.1 1:1 Customer VLAN (C-VLAN) Examples

The following configuration examples provision a Total Access 5000 with a 1:1 Customer
correct UNI port.
MEN EVC
EVC Customer
Port Map
ONT 1
GPON
Network
Splitter
UNI
Unicast Ethernet
Cust. VLAN OLT UNI
Video
Port
/Data
Cust. VLAN
Unicast ONT 2
Video
/Data Network
UNI

UNI
The following examples configure a Total Access 5000 with a 1:1 Customer VLAN model and
the following attributes:
GPON application with a DHCP Subscriber Authentication with Option 82 Subscriber Protocol
65K110FTTP-29A 287
Revision A
6.3.1.1 Example 1:1 Example

Example 2, VDSL2, Redundant GE Uplink, 1:1 VLAN, DHC P w/Option 82
1. Create an EVC for each customer

ChassisID(config)#evc CUST1_EVC
ChassisID(config-evc CUST1EVC)#s-tag 100
ChassisID(config-evc CUST1EVC)#double-tag-switched
ChassisID(config-evc CUST1EVC)#connect men-port default-ethernet
ChassisID(config-evc CUST1EVC)#no preserve-ce-vlan
ChassisID(config-evc CUST1EVC)#no shutdown
ChassisID(config-evc CUST1EVC)#exit
ChassisID(config)#exit
ChassisID(config-evc CUST2EVC)#s-tag 200
ChassisID(config-evc CUST2EVC)#double-tag-switched
ChassisID(config-evc CUST2EVC)#connect men-port default-ethernet
ChassisID(config-evc CUST2EVC)#no preserve-ce-vlan
ChassisID(config-evc CUST2EVC)#no shutdown
ChassisID(config-evc CUST2EVC)#exit
2. Create an EVC Map per customer (ONT).
The example shows the provisioning of 2 ONTs.
PON 1, ONT ID 1, ONT port 1
ChassisID(config)#evc-map MAP_CUST1 1/5
ChassisID(config-evc-map MAP_CUST1 1/5)#connect uni gigabit-ethernet 1/
0/1@1/5/1
ChassisID(config-evc-map MAP_CUST1 1/5)#connect evc CUST1_EVC
ChassisID(config-evc-map MAP_CUST1 1/5)#men-pri 0
ChassisID(config-evc-map MAP_CUST1 1/5)#subscriber access dhcp mode
block
ChassisID(config-evc-map MAP_CUST1 1/5)#subscriber igmp mode block
ChassisID(config-evc-map MAP_CUST1 1/5)#subscriber access pppoe mode
block
ChassisID(config-evc-map MAP_CUST1 1/5)#subscriber access static-ip
1.2.3.3 00:01:02:03:04:05 1.2.3.254 00:01:02:00:00:00
ChassisID(config-evc-map MAP_CUST1 1/5)#subscriber arp mode proxy
ChassisID(config-evc-map MAP_CUST1 1/5)#no shutdown
ChassisID(config-evc-map MAP_CUST1 1/5)#exit
0/1@1/5/2
block
block
288 65K110FTTP-29A
Revision A

1.2.3.4 00:01:02:03:04:06 1.2.3.254 00:01:02:00:00:00
65K110FTTP-29A 289
Revision A
6.3.2 N:1 Service VLAN (S-VLAN) Examples

Total Access 5000 must provide additional security as the subscribers are not on isolated
VLANs.
passing through it.
MEN EVC
EVC Customer
Port Map
ONT 1
GPON
Network
Splitter
UNI
Unicast/ Ethernet
Video VLAN UNI
Multicast
OLT
Video Port
Data VLAN
Unicast ONT 2
Data
Network
UNI

UNI
290 65K110FTTP-29A
Revision A
6.3.2.1 N:1 Service VLAN Example 1

This example displays data and video on the same port.
Example 1, VDSL2, Redundant GE Uplink, N:1 VLAN, PPPoE w/ Intermediate Agent
1. Create an EVC for each service.

ChassisID(config)#evc DATA_EVC
ChassisID(config-evc DATA_EVC)#s-tag 101
ChassisID(config-evc DATA_EVC)#connect men-port default-ethernet
ChassisID(config-evc DATA_EVC)#mac-switched
ChassisID(config-evc DATA_EVC)#no preserve-ce-vlan
ChassisID(config-evc DATA_EVC)#no shutdown
ChassisID(config-evc DATA_EVC)#exit
ChassisID(config)#evc VIDEO_EVC
ChassisID(config-evc VIDEO_EVC)#s-tag 1001
ChassisID(config-evc VIDEO_EVC)#connect men-port default-ethernet
ChassisID(config-evc VIDEO_EVC)#no preserve-ce-vlan
ChassisID(config-evc VIDEO_EVC)#subscriber igmp priority 3
ChassisID(config-evc VIDEO_EVC)#no shutdown
ChassisID(config-evc VIDEO_EVC)#exit
2. Set up per-EVC, per-slot IGMP settings on both GPON and switch modules. The IGMP
proxy mode used in this example.
ChassisID(config)#ip igmp evc VIDEO_EVC 1/5 mode proxy
ChassisID(config)#ip igmp evc VIDEO_EVC 1/5 proxy host ip address
10.20.200.1
ChassisID(config)#ip igmp evc VIDEO_EVC 1/5 proxy last-member-query
count 2
interval 1000
ChassisID(config)#ip igmp evc VIDEO_EVC 1/A mode proxy
ChassisID(config)#ip igmp evc VIDEO_EVC 1/A proxy host ip address
10.20.200.1
ChassisID(config)#ip igmp evc VIDEO_EVC 1/A proxy last-member-query
count 2
interval 1000
3. Create an EVC Map per customer (ONT) for each service. Use the set-top box MAC
address to distinguish its traffic.
a. Create the video EVC Maps.
PON 1, ONT ID 1, ONT port 1, match set-top box
ChassisID(config)#evc-map VIDEO_MAP_CUST1 1/5
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#connect uni gigabit-
ethernet 1/0/1@1/5/1
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#connect evc VIDEO_EVC
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#men-pri 3
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#match source mac-
adress 00:02:02:00:00:00 ff:ff:ff:00:00:00
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#match untagged
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#subscriber igmp mode
processing-enabled
65K110FTTP-29A 291
Revision A
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#subscriber igmp

immediate-leave
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#subscriber igmp proxy
router ip address 10.20.200.2
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#subscriber access
dhcp mode authenticate
pppoe mode block
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#subscriber arp mode
proxy
dhcp option-82
dhcp option-82 remote-id
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#description
REMID_VIDEO_CUST1
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#no shutdown
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#exit
PON 1, ONT ID 2, ONT port 1, match set-top box
address 00:02:02:00:00:00 ff:ff:ff:00:00:00
ChassisID(config-evc-map VIDEO_MAP_CUST2 1/5)#match untagged mac-
address 00:02:02:00:00:00 ff:ff:ff:00:00:00
processing-enabled
immediate-leave
pppoe mode block
proxy
dhcp option-82
REMID_VIDEO_CUST2
292 65K110FTTP-29A
Revision A
b. Create the data EVC Maps.

PON 1, ONT ID 1, ONT port 1, match all other
ChassisID(config)#evc-map DATA_MAP_CUST1 1/5
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#connect uni gigabit-
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#connect evc DATA_EVC
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#men-pri 0
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#subscriber access dhcp
mode authenticate
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#subscriber igmp mode
block
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#subscriber access
pppoe mode block
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#subscriber arp mode
proxy
option-82
option-82 remote-id
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#description
REMID_DATA_CUST1
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#no shutdown
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#exit
mode authenticate
block
pppoe mode block
proxy
option-82
option-82 remote-id
REMID_DATA_CUST2
65K110FTTP-29A 293
Revision A
6.3.2.2 N:1 Service VLAN Example 2

This example displays data and video on different ONT ports.
snooping mode used in this example.
ChassisID(config)#ip igmp evc VIDEO_EVC 1/5 mode snooping
count 2
interval 1000
ChassisID(config)#ip igmp evc VIDEO_EVC 1/A mode snooping
count 2
interval 1000
3. Create an EVC Map per customer (ONT) for each service.
These examples show DHCP authentication for video and PPPoE authentication for
data.
processing-enabled
immediate-leave
pppoe mode block
294 65K110FTTP-29A
Revision A

proxy
dhcp option-82
REMID_VIDEO_CUST1
processing-enabled
immediate-leave
pppoe mode block
proxy
dhcp option-82
REMID_VIDEO_CUST2
These examples show the addition of a customer-specific C-tag toward the network.
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#men-c-tag 101
mode block
block
pppoe mode authenticate
proxy
65K110FTTP-29A 295
Revision A

pppoe intermediate-agent
pppoe intermediate-agent remote-id
REMID_DATA_CUST1
mode block
block
proxy
REMID_DATA_CUST2
296 65K110FTTP-29A
Revision A
6.3.3 Hybrid N+1:1 Combined VLAN Examples

This model provides all of the advantages of the C-VLAN, ( i.e. security, simplified operations,
MEN EVC
EVC Customer
Port Map
ONT 1
GPON
Network
Splitter
UNI
Ethernet
Data Cust. VLAN
UNI
OLT
Unicast Video
Port
Multicast Video
Multicast Video
Cust. VLAN
ONT 2
Data Network
UNI
Unicast Video
Ethernet
Total Access 5000 UNI
The following examples configure a Total Access 5000 with a Hybrid N+1:1 VLAN model and
the following attributes: GPON application with a redundant GE uplink and DHCP Subscriber
Authentication
65K110FTTP-29A 297
Revision A
6.3.3.1 Hybrid N+1:1 Example 1

This example shows a 1:1 customer VLAN with multicat replication (Hybrid/Split VLAN).
Example 3, VDSL2, Redundant GE Uplink, Hybrid VLAN, DHCP
1. Create an EVC for each customer and a single EVC for video.
ChassisID(config-evc CUST1_EVC)#s-tag 100
ChassisID(config-evc CUST1_EVC)#mac-switched
ChassisID(config-evc CUST1_EVC)#connect men-port default-ethernet
ChassisID(config-evc CUST1_EVC)#no preserve-ce-vlan
ChassisID(config-evc CUST1_EVC)#no shutdown
ChassisID(config-evc CUST1_EVC)#exit
10.20.200.1
count 2
interval 1000
10.20.200.1
count 2
interval 1000
298 65K110FTTP-29A
Revision A

These examples show DHCP authentication.
PON 1, ONT ID 1, ONT port 1, match multicast traffic
ChassisID(config-evc-map VIDEO_MAP_CUST1 1/5)#match multicast
processing-enabled
mode block
immediate-leave
PON 1, ONT ID 2, ONT port 1, match multicast traffic
processing-enabled
mode block
immediate-leave
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#connect evc CUST1_EVC
mode authenticate
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#subscriber igmp mode block
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#subscriber access pppoe
mode block
ChassisID(config-evc-map DATA_MAP_CUST1 1/5)#subscriber arp mode proxy
option-82
option-82 remote-id
65K110FTTP-29A 299
Revision A

REMID_DATA_CUST1
mode authenticate
mode block
option-82
option-82 remote-id
REMID_DATA_CUST2
300 65K110FTTP-29A
Revision A
6.3.3.2 Hybrid N+1:1 Example 2

This example shows N:1 service VLANs for data and Hybrid/Split VLAN for video.
Example 3, VDSL2, Redundant GE Uplink, Hybrid VLAN, DHCP
1. Create an EVC each for data and video.

10.20.200.1
count 2
interval 1000
10.20.200.1
count 2
interval 1000
3. Create an EVC Map per customer (ONT) for set-top box multicast traffic. Use match
multicast to distinguish this traffic.
PON 1, ONT ID 1, ONT port 1, match multicast
processing-enabled
mode block
immediate-leave
65K110FTTP-29A 301
Revision A

PON 2, ONT ID 1, ONT port 1, match multicast
processing-enabled
mode block
immediate-leave
4. Create an EVC Map per customer (ONT) for non-multicast traffic.
mode authenticate
mode block
option-82
option-82 remote-id
REMID_DATA_CUST1
mode authenticate
302 65K110FTTP-29A
Revision A

mode block

option-82
option-82 remote-id
REMID_DATA_CUST2
65K110FTTP-29A 303
Revision A
GPON Configurations - TLS Configuration Examples
6.4 TLS Configuration Examples

inner tag (if running double tags) cannot be duplicated within the card. If the VLAN becomes
MAC-switched, TLS no longer functions.
6.4.1 TLS Example 1

This example displays a single tagged TLS service.
1. Create an EVC for each TLS service.
ChassisID(config-evc CUST1_EVC)#no mac-switched
ChassisID(config-evc CUST1_EVC)#no-preserve-ce-vlan
2. Create an EVC Map per customer (ONT)
0/1@1/5/1
transparent
ChassisID(config-evc-map MAP_CUST1 1/5)#subscriber igmp mode
transparent
transparent
ChassisID(config-evc-map MAP_CUST1 1/5)#subscriber arp mode transparent
0/1@1/5/2
304 65K110FTTP-29A
Revision A

transparent
transparent
transparent
6.4.2 TLS Example 2

This example displays a double-tagged TLS service (MEN C-tag added and stripped by Total
Access 5000 system).
ChassisID(config-evc CUST1_EVC)#double-tag-switched
0/1@1/5/1
transparent
transparent
transparent
ChassisID(config-evc-map MAP_CUST1 1/5)#men-c-tag 101
65K110FTTP-29A 305
Revision A

0/1@1/5/2
transparent
transparent
transparent
306 65K110FTTP-29A
Revision A
6.4.3 IPTV Configuration Examples

1. Creating the EVC
ChassisID(config)#evc IGMP_EVC
ChassisID(config-evc IGMP_EVC)#s-tag 108
ChassisID(config-evc IGMP_EVC)#mac-switched
ChassisID(config-evc IGMP_EVC)#connect men-port default-ethernet
ChassisID(config-evc IGMP_EVC)#no preserve-ce-vlan
ChassisID(config-evc IGMP_EVC)#no shutdown
ChassisID(config-evc IGMP_EVC)#exit
2. Configuring the OLT for IGMP
ChassisID(config)#ip igmp evc IGMP_EVC 1/21 mode proxy
ChassisID(config)#ip igmp evc IGMP_EVC 1/21 proxy last-member-query
interval 2000
ChassisID(config)#ip igmp evc IGMP_EVC 1/21 proxy last-member-query
count 2
3. Enabling the UNI Ports
ChassisID(config)#interface gigabit-ethernet 5/0/1@1/21/3
ChassisID(config-giga-eth 5/0/1@1/21/3)#no shutdown
ChassisID(config-giga-eth 5/0/1@1/21/3)#exit
ChassisID(config-giga-eth 5/0/2@1/21/3)#exit
Single UNI Port Configured with CE-VLAN-ID Matching Criteria
ChassisID(config)#evc-map VIDEO-1 1/21
ChassisID(config-evc-map VIDEO-1 1/21)#connect uni gigabit-ethernet 5/
0/1@1/21/3
ChassisID(config-evc-map VIDEO-1 1/21)#connect evc IGMP_EVC
ChassisID(config-evc-map VIDEO-1 1/21)#subscriber igmp mode processing-
enabled
ChassisID(config-evc-map VIDEO-1 1/21)#subscriber igmp immediate-leave
ChassisID(config-evc-map VIDEO-1 1/21)#subscriber igmp proxy router ip
address 10.13.107.254
ChassisID(config-evc-map VIDEO-1 1/21)#match ce-vlan-id 201
ChassisID(config-evc-map VIDEO-1 1/21)#no shutdown
ChassisID(config-evc-map VIDEO-1 1/21)#exit
g NOTE
Multiple UNI Ports (Same ONT) Configured with No Matching Criteria
UNI 1 EVC Map

0/1@1/21/3
enabled
address 10.13.107.254
65K110FTTP-29A 307
Revision A

UNI 2 EVC Map
0/2@1/21/3
enabled
address 10.13.107.254
308 65K110FTTP-29A
Revision A
Active Ethernet Configurations - Scope of this Section
7 Active Ethernet Configurations

This section provides examples of common Total Access 5000 Active Ethernet configurations.
g NOTE
7.2 In this Section

This section contains the topics listed inTable 7-1.
7.3 1:1 Customer VLAN (C-VLAN) Examples 310
7.4 N:1 Service VLANs 313
7.5 Hybrid N+1:1 Combined VLAN Examples 320
7.6 TLS Examples 327
6Multi-Sect-29x 309
Revision A
Active Ethernet Configurations - 1:1 Customer VLAN (C-VLAN) Examples
7.3 1:1 Customer VLAN (C-VLAN) Examples

The following configuration examples provision a Total Access 5000 with a 1:1 Customer
correct UNI port.
MEN EVC
EVC Customer
Port Map
ONT 1
OLT
Port
Data
Cust. VLAN
Multicast Video
Unicast Video
Data Cust. VLAN

Multicast Video
ONT 2
Unicast Video Network
OLT
UNI
Port

UNI
310 6Multi-Sect-29x
Revision A
7.3.1 Example 1:1 Example

Example 2, VDSL2, Redundant GE Uplink, 1:1 VLAN, DHC P w/Option 82
1. Create an EVC for each customer

2. Create an EVC Map per customer (ONT).
The example shows the provisioning of 2 ONTs.
OLT Port 1, ONT port 1
0/1@1/5/1.gigabit-ethernet
block
block
1.2.3.3 00:01:02:03:04:05 1.2.3.254 00:01:02:00:00:00
block
block
6Multi-Sect-29x 311
Revision A

1.2.3.4 00:01:02:03:04:06 1.2.3.254 00:01:02:00:00:00
312 6Multi-Sect-29x
Revision A
Active Ethernet Configurations - N:1 Service VLANs
7.4 N:1 Service VLANs

Product Name must provide additional security as the subscribers are not on isolated VLANs.
passing through it.
MEN EVC
EVC Customer
Port Map
ONT 1
Network
OLT UNI
Port
Ethernet
Multicast Video VLAN UNI
Video
Data VLAN
Unicast ONT 2
Video OLT
Port Network
/Data
UNI

UNI
6Multi-Sect-29x 313
Revision A
7.4.1 N:1 Service VLAN Example 1

The following example displays data and video on same ONT port.
2. Set up per-EVC, per-slot IGMP settings on both Active E and switch modules (proxy
mode used in this example).
10.20.200.1
count 2
interval 1000
10.20.200.1
count 2
interval 1000
3. Create an EVC Map per customer (ONT) for each service. Use the set-top box MAC
address to distinguish its traffic.
OLT port 1, ONT port 1, match set-top box
ethernet 1/0/1@1/5/1.gigabit-ethernet
address 00:02:02:00:00:00 ff:ff:ff:00:00:00
processing-enabled
immediate-leave
314 6Multi-Sect-29x
Revision A

pppoe mode block
proxy
dhcp option-82
REMID_VIDEO_CUST1
OLT port 2, ONT port 1, match set-top box
address 00:02:02:00:00:00 ff:ff:ff:00:00:00
processing-enabled
immediate-leave
pppoe mode block
proxy
dhcp option-82
REMID_VIDEO_CUST2
6Multi-Sect-29x 315
Revision A

OLT port 1, ONT port 1, match all other
mode authenticate
block
pppoe mode block
proxy
option-82
option-82 remote-id
REMID_DATA_CUST1
mode authenticate
block
pppoe mode block
proxy
option-82
option-82 remote-id
REMID_DATA_CUST2
316 6Multi-Sect-29x
Revision A
7.4.2 N:1 Service VLAN Example 2

This example displays data and video on different ONT ports.
2. Set up per-EVC, per-slot IGMP settings on both Active E and switch modules (snooping
mode used in this example).
ChassisID(config)#ip igmp evc VIDEO_EVC 1/5 mode snooping
count 2
interval 1000
ChassisID(config)#ip igmp evc VIDEO_EVC 1/A mode snooping
count 2
interval 1000
These examples show DHCP authentication for video and PPPoE authentication for
data.
OLT port 1, ONT port 2
processing-enabled
immediate-leave
pppoe mode block
6Multi-Sect-29x 317
Revision A

proxy
dhcp option-82
REMID_VIDEO_CUST1
processing-enabled
immediate-leave
pppoe mode block
proxy
dhcp option-82
REMID_VIDEO_CUST2
These examples show the addition of a customer-specific C-tag toward the network.
mode block
block
proxy
318 6Multi-Sect-29x
Revision A

REMID_DATA_CUST1
mode block
block
proxy
REMID_DATA_CUST2
6Multi-Sect-29x 319
Revision A
Active Ethernet Configurations - Hybrid N+1:1 Combined VLAN Examples
7.5 Hybrid N+1:1 Combined VLAN Examples

This model provides all of the advantages of the C-VLAN, ( i.e. security, simplified operations,
MEN EVC
EVC Customer
Port Map
ONT 1
Network
OLT
UNI
Port
Data Cust. VLAN
Unicast Video
Ethernet
UNI
Data Cust. VLAN

Unicast Video
Video VLAN
Multicast Video
ONT 2
OLT
Port Network
UNI
Total Access 5000

Ethernet
UNI
320 6Multi-Sect-29x
Revision A
7.5.1 Hybrid N+1:1 Example 1

This example displays customer VLANs with multicast replication (Hybrid/Split VLAN).
1. Create an EVC for each customer and a single EVC for video.
2. Set up per-EVC, per-slot IGMP settings on both AE and GigE SMs (proxy mode used in
this example).
10.20.200.1
count 2
interval 1000
10.20.200.1
count 2
interval 1000
These examples show DHCP authentication.
OLT port 1, ONT port 1, match multicast traffic
6Multi-Sect-29x 321
Revision A

processing-enabled
dhcp mode block
immediate-leave
OLT port 2, ONT port 1, match multicast traffic
processing-enabled
dhcp mode block
immediate-leave
mode authenticate
block
pppoe mode block
proxy
option-82
option-82 remote-i
REMID_DATA_CUST1
322 6Multi-Sect-29x
Revision A

mode authenticate
block
pppoe mode block
proxy
option-82
option-82 remote-id
REMID_DATA_CUST2
6Multi-Sect-29x 323
Revision A
7.5.2 Hybrid N+1:1 Example 2

This example shows N:1 service VLANs for data and hybrid/split VLAN for video.
1. Create an EVC each for data and video.
2. Set up per-EVC, per-slot IGMP settings on both AE and GigE SMs (proxy mode used in
this example).
10.20.200.1
count 2
interval 1000
10.20.200.1
count 2
interval 1000
3. Create an EVC Map per customer (ONT) for set-top box multicast traffic. Use match
multicast distinguish this traffic
OLT port 1, ONT port 1, match multicast
processing-enabled
dhcp mode block
immediate-leave
324 6Multi-Sect-29x
Revision A

OLT port 2, ONT port 1, match multicast
processing-enabled
dhcp mode block
immediate-leave
4. Create an EVC Map per customer (ONT) for non-multicast traffic.
mode authenticate
block
pppoe mode block
proxy
option-82
option-82 remote-id
REMID_DATA_CUST1
6Multi-Sect-29x 325
Revision A
mode authenticate
block
pppoe mode block
proxy
option-82
option-82 remote-id
REMID_DATA_CUST2
326 6Multi-Sect-29x
Revision A
Active Ethernet Configurations - TLS Examples
7.6 TLS Examples

inner tag (if running double tags) cannot be duplicated within the card. If the VLAN becomes
MAC-switched, TLS no longer functions.
7.6.1 TLS Example 1

This example displays a single tagged TLS service.
transparent
transparent
transparent
6Multi-Sect-29x 327
Revision A

transparent
transparent
transparent
7.6.2 TLS Example 2

This example displays a double-tagged TLS service (MEN C-tag added and stripped by Total
Access 5000 system).
transparent
transparent
transparent
328 6Multi-Sect-29x
Revision A

transparent
transparent
transparent
6Multi-Sect-29x 329
Revision A
330 6Multi-Sect-29x
Revision A
Traffic Management - Scope of this Section
8 Traffic Management

This section covers Traffic Management (shapers and policers) provisioning that can be
applied to your network.
8.2 In this Section

8.3 Shapers, GPON 332
8.4 Provisioning using CLI 334
8.5 Shapers, AE (Example) 353
8.7 Policers, AE (Example) 357
6Multi-Sect-29x 331
Revision A
Traffic Management - Shapers, GPON
8.3 Shapers, GPON

Shaping is a mechanism used at egress to smooth out bursts of traffic. Unlike a policer, which
discards large bursts of traffic, shapers work on queues. The bursts in traffic can appear
smoothed because of the queue function. The shaper acts more like a rate limiter. The port
shaper uses a token bucket (much like a policer); however, when large bursts are received,
the packets are delayed rather than discarded immediately. When a packet arrives at the
shaper, if there are sufficient tokens available, the packet is transmitted without delay. If there
are insufficient tokens in the bucket, the packet is delayed until there are enough tokens in the
bucket to allow transmission.
The benefit of a shaper is that it will not drop frames with a small burst of traffic, but it does
potentially add latency (delay).
The GPON FTTP application supports downstream and upstream shapers. In downstream,
the shapers are per queue (in turn based P-Bits) and per ONT. In upstream, the shapers are
per ONT or per ONT Channel (TCONT).
8.3.1 Downstream Shaping
g NOTE
For Total Access 5000 System Release 7.1 and above, oversubscription is supported for
downstream. All provisioned ONTs connected to a PON can have more than 2.5 Gig rate
provisioned.
The purpose of downstream shaping (see Figure 8-1 on page 8-333) is to provide the ability to
provision different rates for the same services for customers being serviced from the same
ONT or user network interface (UNI).
This can be done using a combination of quality of service (QoS) map profiles and
downstream shapers. The QoS map profiles allow the user to map any given p-bit(s) to any
class of service (CoS) queue. This allows the user to place different services which have the
same p-bit priority, into different queues. This contrasts with what was done before where all
traffic went through the System CoS Map which would simply map p-bit X to queue Y. The
benefit of this is that now you may provision separate downstream shapers with different rates
on the outputs of the CoS queues. This gives you the ability to service multiple customers
from the same ONT but still provide them with separate rates of service.
Weighted Fair Queue (WFQ) provides similar behavior to the shapers in that the inputs to the
WFQ are weights and queue groupings. These weights can be changed to allow one service
to have a higher priority than the other services in the same WFQ.
g NOTE
The WFQ does not act unless there is enough downstream congestion. It is not necessary to
provision the WFQ to obtain the required functionality.
332 6Multi-Sect-29x
Revision A
Traffic Management - Shapers, GPON
Figure 8-1. GPON Downstream Shaping Hierarchy
8.3.2 Upstream Shaping

In previous releases, provisioning more data bandwidth than existed on the PON was not
allowed. This was nominally 1.2 Gbps upstream and 2.4 Gbps downstream. Upstream
shaping now allows oversubscription of bandwidth but adds the option of guaranteed and/or
not guaranteed bandwidth.
In the upstream direction, there are three bandwidth values that are provisioned in a shaper
when the shaper is attached to a GPON channel (upstream from ONT). The shaper rate is the
maximum rate the service receives or the PIR (Peak Information Rate). There are two options
to assign a guaranteed upstream rate:
■ Fixed Bandwidth
■ Assured Bandwidth
The Committed Information Rate (CIR) must be less than or equal to PIR for a service. If CIR
equals the PIR, then all service bandwidth is guaranteed. If CIR is less than PIR, the
bandwidth between CIR and PIR is not guaranteed. This bandwidth is labeled “best effort”
(PIR - CIR = best effort).The total CIR of all service endpoints on the PON cannot exceed the
upstream PON bandwidth.
Fixed bandwidth is used for services requiring low/fixed latency. The service is granted the
same upstream bandwidth in every upstream allocation period. Even if no traffic is sent, fixed
bandwidth is allocated transmit time and thus this bandwidth is not available for best-effort
use.
Assured bandwidth is also guaranteed, but the bandwidth is averaged over multiple allocation
periods. A service may get no bandwidth in one allocation cycle and more in another. Unlike
fixed bandwidth, unused assured bandwidth is available for best-effort use by other traffic
flows/subscribers.
Typically, the service is configured with either fixed or assured bandwidth but not both. CLI
allows both to be configured. If configured with both, the fixed plus assured bandwidth must be
less than the PIR and both fixed and assured count toward the total PON CIR bandwidth.
6Multi-Sect-29x 333
Revision A
Traffic Management - Provisioning using CLI
8.4 Provisioning using CLI

8.4.1 Downstream Shaper
To provision the downstream shaper, complete the following steps:
g NOTE
Provisioning downstream shapers is not required for normal operation.

2. Access the Shaper Configuration Command Set.
ChassisID(config)#shaper WORD <shelf/slot>
3. Configure the shaped traffic that egresses at a rate up to the value specified.
ChassisID(config-shaper name x/x)#rate <m-n>
4. Attach the shaper to the selected GPON ONT port and configure a list of queues on the
interface to shape.
ChassisID(config-shaper name x/x)#per remote-device <ont-id>@<shelf/
slot/port>.gpon queue [LIST|<0-7>]
5. Enable the shaper.
ChassisID(config-shaper name x/x)#no shutdown
ChassisID(config-shaper name x/x)#exit
8.4.2 Downstream Shaper for Multiple Customers

To provision the downstream shaper for multiple customers, complete the following steps:
g NOTE
Provisioning the shaper is not required for normal operation.
8.4.2.1 P-Bit to Queue Mapping

2. Create a QoS map profile.
ChassisID(config)#qos map-profile WORD
3. Map the p-bit to the selected queue.
ChassisID(config qos-map profile name)#p-bit X queue Y
8.4.2.2 EVC Map to QoS Map

2. Access the EVC Map Configuration Command Set.
334 6Multi-Sect-29x
Revision A
3. Connect the EVC-Map to a QoS map profile.

ChassisID(config-evc-map name x/x)#connect qos downstream map-profile
WORD
g NOTE
The EVC Map still needs to be connected to an EVC and an UNI to function properly.
8.4.2.3 Queue Scheduling

2. Enter the configuration mode for the selected CoS queue.
ChassisID(config)#queue remote-device <ont-id>@<shelf/slot/port>.gpon
[LIST|<0-7>]
3. Group the CoS queue (X) and the CoS queue under it (X-1) in the same WFQ.
ChassisID(config-queue x@x/x/x)#cos group lower-adjacent
4. Set the weight that this queue (X) will have for the WFQ.
ChassisID(config-queue x@x/x/x)#weight Y
g NOTE
To ungroup queue X from the WFQ, set its CoS back to X using the following command:
ChassisID(config-queue x@x/x/x)#cos X
8.4.3 Upstream Shaper

To provision the upstream shaper, complete the following steps:
ChassisID(config)#shaper WORD <ont-id>@<shelf/slot/port>
3. Configure the shaper traffic that egresses at a rate up to the value specified.
4. Provision the assured bandwidth.
ChassisID(config-shaper name x/x)#gpon channel assured-bandwidth
<0,64-1244160>
5. Provision the fixed bandwidth.
ChassisID(config-shaper name x/x)#gpon channel fixed-bandwidth
<0,64-1244160>
6. Attach the shaper to the required upstream channel.
g NOTE
ADTRAN supports four upstream shapers per ONT, but these must be connected to different
channels. The interface maps are not restricted to one map to one shaper, but it could be
multiple interface maps to one shaper. The Total Access 5000 GPON 2.5G 2-Port Access
Module (P/N 1187500E1) does not support multiple upstream shaper channels.
6Multi-Sect-29x 335
Revision A
ChassisID(config-shaper name x/x)#per interface gpon <ont-id/0/

port>@<shelf/slot/port> channel <1-4>
8.4.3.1 Upstream Shaping Example
g NOTE
■ The interface is the GPON interface, not the ethernet interface. For multiple upstream
shapers on the same ONT, the interface will be the same, but the channel will be different.
■ The channel makes a distinction between the two upstream shapers.
■ The connect gpon upstream channel <1-4> command is added to the EVC Map. It
connects the upstream shaper to the EVC Map.
shaper "11_downstream" 1/13

per remote-device 11@1/13/1.gpon queue 0
rate 200000
gpon channel assured-bandwidth 0
gpon channel fixed-bandwidth 0
no shutdown
shaper "11_upstream_ch1" 11@1/13/1.gpon
per interface gpon 11/0/1@1/13/1.gpon channel 1
rate 1024
no shutdown
shaper "11_upstream_ch2" 11@1/13/1.gpon
per interface gpon 11/0/1@1/13/1.gpon channel 2
rate 1024
no shutdown
evc-map "11_p1_data" 1/13
connect evc "AUTOGEN_101_0"
connect uni gigabit-ethernet 11/0/1@1/13/1.gpon
connect gpon upstream channel 1
subscriber access static-ip 192.168.1.241 00:00:00:00:00:00 192.168.1.254
00:00:00:00:00:00
men-pri 4
men-c-tag-pri 0
subscriber access dhcpv6 relay-agent mode disable
no shutdown
evc-map "11_p2_data" 1/13
connect evc "AUTOGEN_101_0"
subscriber access static-ip 192.168.1.242 00:00:00:00:00:00 192.168.1.254
00:00:00:00:00:00
336 6Multi-Sect-29x
Revision A
men-pri 0
men-c-tag-pri 0
subscriber access dhcpv6 relay-agent mode disable
no shutdown
8.4.3.2 Downstream GPON QoS for User Fairness

Figure 8-2 provides an example of an alternative QoS model. This model provides per service
rate guarantees for each SFU ONT on the PON.
Two rates Min-Rate and PIR are specified for the queue associated with the high-speed
internet access (HSIA) traffic class for each ONT.
g NOTE
The rates are actually specified in a shaper associated with a queue.
The design allows the ability to also provision an optional PIR for the queue associated with
the Video on Demand (VoD) traffic class.
The PIR is the peak rate possible for a given queue provided there is enough bandwidth left on
the PON. The Min-Rate is a minimum rate provided under the condition there is enough
bandwidth left on the PON after servicing the higher priority traffic classes.
The aggregate Min-Rate for HSIA cannot be oversubscribed on a PON. Min-Rate is used to
derive corresponding internal PON level weight used by the PON level scheduler for HSIA
traffic. The PON weight will be selected such that the HSIA traffic is provided Min-Rate
bandwidth when the PON is congested and there is enough bandwidth after accounting for
higher priority traffic classes.
6Multi-Sect-29x 337
Revision A
Figure 8-2. Per PON Bandwidth Thresholds Example
A PON level threshold - Total Minimum Rate Threshold must be provisioned. This is the sum
of all Min-rates provisioned on the PON. This threshold must be provisioned at the Total
Access 5000 node commissioning time (or new OLT installation time) prior to provisioning any
subscriber services. By default, the threshold is set to full GPON bandwidth (2488 Mbps). The
operator is expected to set it to a value less than or equal to 2488 Mbps - Multicast bandwidth
threshold.
338 6Multi-Sect-29x
Revision A
8.4.3.2.1 Total Minimum Rate Threshold Provisioning

To provision the total minimum rate threshold, complete the following:
g NOTE
GPON QoS is only supported on the GPON OLT 8X SFP Access Module
(P/N 1187503F1) and the 8-Port OLT 2nd Generation (P/N 1187503F2). It is not supported on
any other GPON Access Modules.

2. Provision the shaper on the selected OLT module.
3. Set the total minimum rate threshold on the PON.
ChassisID(config-gpon x/x/x)#thresholds total-min-rate <0-n>
8.4.3.2.2 Per Service Model

The Single Subscriber Per ONT model provides per subscriber rate guarantees for each ONT
on the PON. The min-rate (assured rate) and PIR (maximum rate) can be set for the
aggregate output of these queues for each ONT. The sum of all the min-rates on the PON
cannot exceed the total min-rate threshold value provisioned on the GPON interface. This
ensures that min-rate cannot be oversubscribed on a PON, although the PIR can still be
oversubscribed on the PON. During congestion, bandwidth will be allocated to the ONT based
on the subscribed min-rate.
The shaper is associated with an input queue on a particular ONT’s traffic management block.
To specify the Minimum Rate to a downstream shaper, complete the following:
3. Configure the shaper traffic that egresses at a rate up to the value specified in kbps.
4. Set the new minimum rate parameter in kbps.
ChassisID(config-shaper name x/x)#min-rate <0-n>
The OLT ensures the total minimum rate configured on the downstream shapers on a
PON cannot exceed the total minimum rate threshold.
Provisioning will be rejected if the total minimum rates on the downstream shapers
exceed the total minimum rate threshold on the GPON interface.
interface to shape.
ChassisID(config-shaper name x/x)#per remote-device <ont-id>@<shelf/
slot/port>.gpon queue [LIST|<0-7>]
6Multi-Sect-29x 339
Revision A

7. Verify the configuration of the Total Minimum Threshold on the GPON interface and the
sum of the shaper Minimum Rates.
ChassisID(config-shaper name x/x)#do show interface gpon <shelf/slot/
port>
g NOTE
The show interface gpon <shelf/slot/port> command also shows how much Minimum Rate
bandwidth is still available.
gpon 1/2/1 is IS and up

Number of Configured ONTs : 7
Number of Discovering ONTs : 1
Number of Unrecognized ONTs : 0
Number of Operational ONTs : 6
Number of Available HW Resour : 959
g NOTE
The Number of Available Hardware Resources field displays the remaining number of
hardware resources available on the PON.
Longest Fiber Distance : ont-12, 230m

Shortest Fiber Distance : ont-2, 162m
Oversubscription Allowed : true
Multicast CAC Status : admitting
DS Total-min-rate thresh kbps : 540000
g NOTE
DS Total-min-rate thresh kbps shows what is configured for 'thresholds total-min-rate'
Downstream Upstream
Max Provisionable BW kbps : 2488320 1244160
Configured PIR BW kbps : 11000000 0
Configured Fixed BW kbps : na 0
Configured Assured BW kbps : na 0
Configured min-rate BW kbps : 380000 na
g NOTE
Configured min-rate BW shows the sum of the configured 'min-rate' commands on the
shapers
Available PIR BW kbps : 2488320 1244160

Available CIR BW kbps : na 1153872
Available min-rate BW kbps : 160000 na
g NOTE
Available min-rate BW shows 'thresholds total-min-rate' minus sum of configured 'min-rate'
commands on shapers
Current PIR BW kbps : 10999989 7488

Current CIR BW kbps : na 13008
340 6Multi-Sect-29x
Revision A
8.4.3.2.3 Single Subscriber Per ONT Model Example

Figure 8-3 displays downstream QoS for the single subscriber per ONT model.
ONT1 Q3 W
Pbit = 7,6
WFQ
(Network control, Prio=3
cVoIP) W
ONT32 Q3
ONT1 Q2 W
Pbit = 5
(IGMP,Multicast
WFQ
video) ONT32 Q2 W Prio=2
MC W
PON
SP
ONT1 Q1 W
WFQ
Pbit = 4,3,2 Prio=1
(VoD, ICC, etc.)
W
ONT32 Q1
ONT1 Q0 S W1
Pbit = 1,0
WFQ
PIR1 Prio=0
(HSIA)
S W32
ONT32 Q0
PIR32
Wi is derived from
min-rated(i)
PIRx for ONT x PON Scheduler
min-rate(x) and PIRx are provisionable
Figure 8-3. Downstream QoS for Single Subscriber
The WFQ is applied per priority group so downstream traffic for all ONTs on the PON are in the
WFQ for each priority queue.
The following example configuration is for the single subscriber per ONT model. Downstream
traffic with a P-bit of 0 is placed in queue 0. Downstream traffic with a P-bit of 1 is placed in
queue 1. For this example, only queue 0 and queue 1 are shaped so the min-rate and PIR will
only apply to those queues.
evc-map "s2-01-data" 1/2
connect evc "DATA_1201"
men-pri 0
men-c-tag-pri 0
no shutdown
men-pri 0
men-c-tag-pri 0
no shutdown
men-pri 0
men-c-tag-pri 0
no shutdown
6Multi-Sect-29x 341
Revision A

men-pri 0
men-c-tag-pri 0
no shutdown
men-pri 0
men-c-tag-pri 0
no shutdown
men-pri 0
men-c-tag-pri 0
no shutdown
qos cos-map 0 0 1
qos cos-map 1 2 3
qos cos-map 2 4 5
qos cos-map 3 6 7
queue remote-device 1@1/2/1 0
cos 0
weight 100
cos 0
weight 100
cos 0
weight 100
cos 0
weight 100
cos 0
weight 100
cos 0
weight 100
interface gpon 1/2/1
thresholds total-min-rate 600000
no shutdown
rate 1000000
min-rate 150000
no shutdown
342 6Multi-Sect-29x
Revision A

rate 1000000
min-rate 150000
no shutdown
rate 1000000
min-rate 100000
no shutdown
rate 1000000
min-rate 100000
no shutdown
rate 1000000
min-rate 50000
no shutdown
rate 1000000
min-rate 50000
no shutdown
6Multi-Sect-29x 343
Revision A
8.4.3.2.4 Example Scenario

Figure 8-4 displays 3 ONTs using UvClass 12, 13, and 16G subscriber profiles. The Minimum
Rates provisioned for these ONTs are 35M, 45M, and 55M, respectively. The PIRs provisioned
for those ONTs are 49.5M, 82.5M, and 300M, respectively. The operator provisions the
weights 90 for Q1 and 10 for Q0.
ONT1
Pbit = 2,0 Q0 Wt1
S
UvClass 12 (HSIA)
Min-rate = 35M PIR = 49.5M
Min-rate = 35M
ONT2
Pbit = 2,0 Q0 Wt2
PON WFQ
S PON SP
UvClass 13 (HSIA) Scheduler
Min-rate = 45M PIR = 82.5M
Min-rate = 45M
ONT32 Wt32
Pbit = 2,0 Q0 S
UvClass 16G (HSIA)
Min-rate = 55M PIR = 300M
Min-rate = 55M
Figure 8-4. Example Provisioning of Weights and Minimum Rates
Assuming the PIR rates are not reached, bandwidth is allocated on the PON based on the
weights Wti. In terms of rate guarantees, examine both congested and uncongested
examples.
344 6Multi-Sect-29x
Revision A
Scenario 1 - Congested PON

Since the Minium Rate derived weights are applied at the PON level, Minimum Rate is
guaranteed for each ONT when ALL ONTs have traffic to send provided the higher priority
traffic classes (Q3, Q2, and Q1 traffic) is negligible. If all the ONTs are sending data at rates
more than their respective Minimum Rates, every ONT will get bandwidth equal to the provi-
sioned Minimum Rate.
Table 8-2 considers a fully populated PON with 32 active ONTS, even if not listed explicitly.
Table 8-2. Congested PON Example 1
Description Rate
ONT1 HSIA Bandwidth 35M
ONT3-32 HSIA Bandwidth -
Scenario 2 - Congested PON

If the actual available bandwidth for HSIA is less than the sum of Minium Rates of the active
ONTs, the bandwidth is distributed among the ONTs in proportion to their Minimum Rates. In
this case, each ONT will get less than its Min-Rate for its HSIA traffic. This is due to the higher
priority traffic classes taking up more than their budgeted bandwidth.
Table 8-3. Congested PON Example 2
Description Rate
Total Line Rate 2488M
Total MC Bandwidth Threshold 1000M
Total MC Bandwidth (Actual) 1000M
Non-MC High Priority Traffic Class Bandwidth (Budgeted) 300M
Total Minimum Rate Threshold 1188M
Actual Available Bandwidth for HSIA 88M
6Multi-Sect-29x 345
Revision A
Table 8-3. Congested PON Example 2 (Continued)
Description Rate
ONT1 HSIA Bandwidth - (Minimum Rate = 35M, PIR = 300M) = Lower {Wt1/?Wti of actual
available HSIA bandwidth, PIR1}
= Lower {~22M, 300M}
= ~22M
ONT2 HSIA bandwidth = Lower { Wt2/?Wti of actual

(Min-rate = 45M, PIR = 1000M) available HSIA bandwidth, PIR2}
= Lower {~29M, 1000M}
= ~29M

= Lower {~36M, 1000M}
= ~37M
346 6Multi-Sect-29x
Revision A
Scenario 3 - Uncongested PON

If the actual available bandwidth for HSIA is more than the sum of Min-Rates (and even if it is
less than the Total-Min-Rate threshold), the bandwidth is distributed among the ONTs in
proportion to their Min-Rates. In this case, each ONT will get more than its Min-Rate for its
HSIA traffic.
Table 8-4. Uncongested PON Example 1
Description Rate
Non-MC High Priority Traffic Class Bandwidth (Actual) 600M
ONT1 HSIA Bandwidth = Lower {Wt1/?Wti of actual

(Minimum Rate = 35M, PIR = 300M) available HSIA bandwidth, PIR1}
= Lower {~226M, 300M}
= ~226M

= Lower {~291M, 1000M}
= ~291M

= Lower {~371M, 1000M}
= ~371M
6Multi-Sect-29x 347
Revision A
Scenario 4 - Uncongested PON

If the actual available bandwidth for HSIA is more than the Total-Min-Rate threshold, the
bandwidth is distributed among the ONTs in proportion to their Min-Rates. In this case, each
ONT will get more than its Min-Rate for its HSIA traffic and some may even reach their peak
rates.
Table 8-5. Uncongested PON Example 2
Description Rate
Non-MC High Priority Traffic Class Bandwidth (Actual) 0M
ONT1 HSIA Bandwidth = Lower {Wt1/?Wti of non-MC

(Minimum Rate = 35M, PIR = 300M) bandwidth, PIR1}
= Lower {~387M, 300M}
= ~300M
ONT2 HSIA bandwidth = Lower { Wt2/?Wti of non-MC

(Min-rate = 45M, PIR = 1000M) bandwidth, PIR2}
= Lower {~522M, 1000M}
= ~522M
ONT32 HSIA bandwidth = Lower { Wt32/?Wti of non-MC

(Min-rate = 55M, PIR = 1000M) bandwidth, PIR32}
= Lower {~666M, 1000M}
= ~666M
348 6Multi-Sect-29x
Revision A
8.4.4 Web
g NOTE
Total Access 5000 Release 8.5 does not support configuring downstream QoS using the User
Interface.
8.4.4.1 Downstream Shaper Provisioning

To provision the downstream shaper, complete the following steps:
g NOTE
1. Access the Shaper.

GPON OLT > Provisioning > Shaper
g NOTE
To create or retrieve a shaper, enter the shaper name and select Go.
2. Select Downstream for the Shaper Direction.

interface to shape.
5. Select Apply to enable the shaper.
8.4.4.2 Downstream Shaper Provisioning for Multiple Customers

To provision the downstream shaper for multiple customers, complete the following steps:
g NOTE
8.4.4.2.1 P-Bit to Queue Mapping

1. Access the QoS Map Profile.
(active) Switch Module > Provisioning > Network Tab
2. Enter a QoS map profile name and select Create.
3. Enter a description.
4. Map the p-bit to the selected queue.
5. Select Go.
6Multi-Sect-29x 349
Revision A
8.4.4.2.2 EVC Map to QoS Map

1. Access the Interface Map
GPON OLT > Provisioning > Interface Map
2. Connect the EVC Map to a QoS map profile.
GPON OLT > Provisioning > Interface Map > Traffic Classification > QoS Map-
Profile > QoS Profile Name
g NOTE
The EVC Map still needs to be connected to an EVC and an UNI to function properly.
8.4.4.2.3 Queue Scheduling

1. Access the Queue.
GPON OLT > Provisioning > Queue
2. Select Explicit for the method of the selected CoS queue.
3. Group the CoS queue (X) and the CoS queue under it (X-1) in the same WFQ by
assigning the same Weight Percent.
g NOTE
To ungroup queue X from the WFQ, set its CoS back to X using the following command:
ChassisID(config-queue x@x/x/x)#cos X
350 6Multi-Sect-29x
Revision A
Traffic Management - Example
8.5 Example
The following provides a sample configuration for provisioning shapers.
8.5.1 Step 1: Create Unique Queues for Each Port

qos map-profile INET-PORT1
p-bit 0 queue 0
p-bit 1-3 queue 4
p-bit 4-5 queue 5
p-bit 6 queue 6
p-bit 7 queue 7
qos map-profile INET-PORT2
p-bit 0 queue 1
p-bit 1-3 queue 4
p-bit 4-5 queue 5
p-bit 6 queue 6
p-bit 7 queue 7
8.5.2 Step 2: Attach the Downstream Queue Profiles and Upstream

Channels to Each Port
evc-map INET-PON1-1-ONT1-PORT1
connect evc INET
connect uni gigabit-ethernet 1/0/1@1/1/1
connect qos downstream map-profile INET-PORT1
men-pri 0
no shutdown
evc-map INET-PON1-1-ONT1-PORT2
connect evc INET
connect uni gigabit-ethernet 1/0/2@1/1/1
connect qos downstream map-profile INET-PORT2
men-pri 0
no shutdown
8.5.3 Step 3: Attach the Downstream Shapers to the Specified

Queues from the Map Profiles
shaper DOWN-INET-PON1-1-ONT1-PORT1 1/1
per remote-device gpon 1@1/1/1 queue 0
rate 10000
no shutdown
shaper DOWN-INET-PON1-1-ONT1-PORT2 1/1
per remote-device gpon 1@1/1/1 queue 1
rate 20000
no shutdown
6Multi-Sect-29x 351
Revision A
Traffic Management - Example
8.5.4 Step 4: Attach the Upstream Shapers to the Specified Channels

shaper UP-INET-PON1-1-ONT1-PORT1 1@1/1/1
per interface gpon 1/0/1@1/1/1 channel 1
rate 10000
no shutdown
shaper UP-INET-PON1-1-ONT1-PORT2 1@1/1/1
per interface gpon 1/0/1@1/1/1 channel 2
rate 20000
no shutdown
8.5.5 Attach/Detach Interface to the Shaper

(shaper)#shaper "372E_21_DATA_DOWN" 1/4
(shaper)#do show run shaper "372E_21_DATA_DOWN" 1/4
shaper "372E_21_DATA_DOWN" 1/4
per interface gigabit-ethernet 1/4/1 queue 0
rate 1000000
no shutdown
(shaper)#no per interface

rate 1000000
no shutdown
(shaper)#per remote-dev 1@1/4/1 queue 0

per remote-device 1@1/4/1.gigabit-ethernet queue 0
rate 1000000
no shutdown
(shaper)#no per remote-device 1@1/4/1.gigabit-ethernet queue 0

(shaper)# per interface gigabit-ethernet 1/4/1 queue 0
per interface gigabit-ethernet 1/4/1 queue 0
rate 1000000
no shutdown
352 6Multi-Sect-29x
Revision A
Traffic Management - Shapers, AE (Example)
8.6 Shapers, AE (Example)

Shaping is a mechanism used at egress to smooth out bursts of traffic. Unlike a policer, which
discards large bursts of traffic, shapers work on queues. The bursts in traffic can appear
smoothed because of the queue function. The shaper acts more like a rate limiter. The port
shaper uses a token bucket (much like a policer); however, when large bursts are received,
the packets are delayed rather than discarded immediately. When a packet arrives at the
shaper, if there are sufficient tokens available, the packet is transmitted without delay. If there
are insufficient tokens in the bucket, the packet is delayed until there are enough tokens in the
bucket to allow transmission.
The benefit of a shaper is that it will not drop frames with a small burst of traffic, but it does
potentially add latency (delay).
8.6.1 Provisioning
The Active Ethernet FTTP application supports downstream and upstream shapers. In
downstream, the shapers are per priority queue per port. In upstream, the shapers are per
ONT.
8.6.1.1 CLI
8.6.1.1.1 Downstream Shaper Provisioning

Shapers are applied per physical port. To provision the shaper parameters, complete the
following steps:
g NOTE
Provisioning the downstream shaper is not required for normal operation.
1. Access the Shaper Configuration prompt.

ChassisID(config-shaper name x/x)#rate <0-n>
3. Attach the shaped traffic to the gigabit-ethernet interface.
g NOTE
The shaper can be attached to a single queue on a port (e.g. queue 5) or to all the queues on
a port (e.g. queue 0-7). The shaper can NOT be attached to a subset of queues on a port (e.g.
queue 0-4). Two different shapers can be attached to two different queues on the same port.
ChassisID(config-shaper name x/x)#per interface gigabit-ethernet

<shelf/slot/port> queue [LIST|<0-7>]
6Multi-Sect-29x 353
Revision A
8.6.1.1.2 Upstream Shaper Provisioning

Upstream Shapers are applied per ONT. To provision the upstream shaper parameters,
g NOTE
Provisioning the upstream shaper is not required for normal operation.
1. Access the Shaper Configuration prompt.

ChassisID(config)#shaper WORD <1@shelf/slot/port>
ChassisID(config-shaper name x/x)#rate <0-n>
3. Attach the shaped traffic to the ONT.
The gigabit-ethernet index must be the same as the index in step 1.
g NOTE
The shaper will be attached on ALL queues for the ONT. There is no per-queue shaping
options for upstream shaping. Only one upstream shaper per ONT is allowed.
ChassisID(config-shaper name x/x)#per interface gigabit-ethernet

<1@shelf/slot/port>
354 6Multi-Sect-29x
Revision A
8.6.2 Web
8.6.2.1 Downstream Shaper Provisioning

Shapers are applied per physical port. To provision the shaper parameters, complete the
following steps:
g NOTE
Provisioning the downstream shaper is not required for normal operation.

AE 24-Port > Provisioning > Shaper
g NOTE
2. Assign a unique name to the shaper.

3. Select the Go button.
4. Select Downstream for the Shaper Direction.
6. Attach the shaped traffic to the gigabit-ethernet interface.
g NOTE
The shaper can be attached to a single queue on a port (e.g. queue 5) or to all the queues on
a port (e.g. queue 0-7). The shaper can NOT be attached to a subset of queues on a port (e.g.
queue 0-4). Two different shapers can be attached to two different queues on the same port.
8.6.2.2 Upstream Shaper Provisioning

Upstream Shapers are applied per ONT. To provision the upstream shaper parameters,
g NOTE
Provisioning the upstream shaper is not required for normal operation.

AE 24-Port > Provisioning > Shaper
g NOTE
2. Assign a unique name to the shaper.

4. Select Upstream for the Shaper Direction.
6. Attach the shaped traffic to the ONT.
6Multi-Sect-29x 355
Revision A
g NOTE
The shaper will be attached on ALL queues for the ONT. There is no per-queue shaping
options for upstream shaping. Only one upstream shaper per ONT is allowed.
356 6Multi-Sect-29x
Revision A
Traffic Management - Policers, AE (Example)
8.7 Policers, AE (Example)

Policing is a rate-based admission control function that uses a leaky/token bucket algorithm.
The purpose of a policer is to keep non-conforming traffic from entering the network and
degrading other customers and/or services.
8.7.1 Provisioning
8.7.1.1 CLI
The policer can be used to limit bandwidth in specified traffic flows. To provision for policing,
g NOTE
The policer is not required for normal operation.
1. Access the Policer Configuration prompt.

ChassisID(config)#policer WORD <shelf/slot>
2. Configure the committed information rate (CIR) in kbps.
The CIR is the rate up to which service frames are delivered according to the service
performance objectives.
ChassisID(config-policer name x/x)#cir <0-n>
3. Configure the committed burst size (CBS).
The CBS is the maximum available bytes for a burst of ingress traffic sent at the port
speed while still conforming to the CIR.
ChassisID(config-policer name x/x)#cbs <0-n>
4. Configure the excess information rate (EIR) in kbps.
ChassisID(config-policer name x/x)#eir [<0-n>|max-bandwidth]
5. Configure the excess burst size (EBS).
The EBS is the maximum available bytes for a burst of ingress traffic sent at the port
speed while still conforming to the EIR.
ChassisID(config-policer name x/x)#ebs <0-n>
6. Set the EVC ingress. The EVC ingress represents upstream to the customer.
ChassisID(config-policer name x/x)#per custom evc-map WORD ingress
7. Enable the Policer.
ChassisID(config-policer name x/x)#no shutdown
ChassisID(config-policer name x/x)#exit
6Multi-Sect-29x 357
Revision A
8.7.2 Web
The policer can be used to limit bandwidth in specified traffic flows. To provision for policing,
g NOTE
The policer is not required for normal operation.
1. Access the Policer.

AE 24-Port > Provisioning > Policer
g NOTE
To create or retrieve a policer, enter the shaper name and select Go.
2. Assign a unique name to the policer.

4. At the Per Custom evc-map, assign an EVC Map to this policer.
5. Configure the committed information rate (CIR) in kbps.
The CIR is the rate up to which service frames are delivered according to the service
performance objectives.
6. Configure the committed burst size (CBS).
The CBS is the maximum available bytes for a burst of ingress traffic sent at the port
speed while still conforming to the CIR.
7. Configure the excess information rate (EIR) in kbps.
8. Configure the excess burst size (EBS).
The EBS is the maximum available bytes for a burst of ingress traffic sent at the port
speed while still conforming to the EIR.
9. Set the EVC ingress. The EVC ingress represents upstream to the customer.
10. Select Apply to enable the Policer.
358 6Multi-Sect-29x
Revision A
6Multi-Sect-29x 359
Revision A
360 6Multi-Sect-29x
Revision A
SFP Information - Scope of this Section
9 SFP Information

This section provides the command to display the CLEI code information of an installed SFP in
the selected GPON OLT.
9.2 In this Section

9.3 Information Command 362
6Multi-Sect-29x 361
Revision A
SFP Information - Information Command
9.3 Information Command

To display the CLEI code information, use the following command:
ChassisID#show interfaces gpon <shelf/slot/port> pluggable
9.3.1 Example
The following example displays the CLEI code information of the SFP installed in port 1 of the
OLT installed in slot 5 of the Total Access 5000.
ChassisID#show interfaces gpon 1/5/1 pluggable
gpon pluggable port 1/5/1 is Up
Pluggable Type : SFP
Pluggable Connector Type : Fiber SC
Capabilities : Pluggable/VOLTAGE Readable
Port Status : Present/Valid/ADTRAN Supported/Tx Enabled
Vendor Name : ADTRAN
Vendor Part Number : 1442530G1
Vendor Serial Number : X11-04-001034
ADTRAN CLEI : BVL3AHFDAA
Tx Power : 30 tenths of dBm
Tx Bias : 18 milliAmps
Temperature : 37 Celsius
Voltage : 3
Alarms :
362 6Multi-Sect-29x
Revision A
3rd Party ONT Provisioning for Active Ethernet - Scope of this Section
10 3rd Party ONT Provisioning for Active Ethernet

This section provides the minimum steps required for third party ONT provisioning for an
Active Ethernet (AE) deployment. It also provides an example deployment.
10.2 In this Section

10.3 “Provisioning” 364
65K110FTTP-29A 363
Revision A
3rd Party ONT Provisioning for Active Ethernet - Provisioning
10.3 Provisioning
It is assumed that the ONT will be provisioned independently of the OLT. The new provisioning
of the EVC Map is available through the Total Access 5000 CLI and not through AOE or the
user interface. Also, for these applications the following limitations are still to be addressed:
■ Match untagged, match multicast, and match unicast operation for EVC Maps
■ Inheriting the vlan priority bits in the CE-VLAN to use as the vlan priority bits in the S-tag
■ S-tag priority bits for a flow can only be set with the men-pri command
■ The operation of the mac limit command has not been fully verified
■ EVC Map must be connected to an EVC with preserve-ce-vlan disabled
■ A feature that allows a user to move any Ethernet Device that has been successfully
authenticated using DHCP between different ports of an ADTRAN AE or GPON ONT. This
move would be done without requiring the manual intervention in the OLT/ONT by the
installer. It should be noted that ONT ports must be provisioned for their specific service
(either multicast and/or unicast). For example, if an Ethernet device is moved from a
multicast port to a unicast only port, it cannot be expected to function. It is assumed that
the installer is moving between ports with similar provisioning. The only function required
by the user will be a resetting of the Ethernet Device. If the single ONT is used in a multi-
dwelling unit application, then this feature removes the protection against mac-spoofing.
The AE deployment supports connecting to third party ONTs that are managed from a
separate server. To provision a third party ONT for AE deployment, complete the following
steps:
1. Attach the third party ONT to a front panel port on the Active Ethernet 24-Port Access
Module.
3. Access the Gigabit-Ethernet Interface Configuration Command Set.
ChassisID(config)#interface gigabit-ethernet <shelf/slot/port>
4. Provision the port speed to match the installed SFP.
ChassisID(config-giga-eth x/x/x)#speed [100|1000]
5. Enable the port.
ChassisID(config-giga-eth x/x/x)#no shutdown
6. Provision the EVCs (voice, data, and video) for the ONT.
7. Provision the EVC Maps similar to what is done for an ADTRAN ONT, but connect the
UNI interface to the OLT front panel port attached to the third party ONT.
ChassisID(config-evc-map name x/x)#connect uni gigabit-ethernet <shelf/
slot/port>
8. If multiple EVC Maps share the same UNI, set the EVC Map to match the CE-VLAN.
ChassisID(config-evc-map name x/x)#match ce-vlan-id <0-4094>
364 65K110FTTP-29A
Revision A
10.3.1 Example Provisioning

In this example the following VLANs are used for the various services in the network:
■ DATA = 90
■ VIDEO = 115
■ VOICE = 116
■ Management = 200
It is assumed that the ONT will be configured to expect these services on the same VLANs,
except for management. In this example, it is assumed that the ONT sends/receives
management traffic untagged. The expected configuration of the ONT determines the 'match
ce-vlan-id *' commands. In this case, since management is not tagged that evc-map will not
have a match criteria.
1. Provision the gigabit-ethernet ports attached to the 3rd party ONT.
ChassisID(config)#interface gigabit-ethernet 1/3/1
ChassisID(config-giga-eth 1/1/1)#speed 1000
ChassisID(config-giga-eth 1/1/1)#no shutdown
ChassisID(config-giga-eth 1/1/1)#exit
ChassisID(config)#evc data-evc
ChassisID(config-evc data_evc)#s-tag 90
ChassisID(config-evc data_evc)#connect men-port default-ethernet
ChassisID(config-evc data_evc)#mac-switched
ChassisID(config-evc data_evc)#no preserve-ce-vlan
ChassisID(config-evc data_evc)#no shutdown
ChassisID(config-evc data_evc)#exit
ChassisID(config)#evc video_evc
ChassisID(config-evc video_evc)#s-tag 115
ChassisID(config-evc video_evc)#connect men-port default-ethernet
ChassisID(config-evc video_evc)#mac-switched
ChassisID(config-evc video_evc)#no preserve-ce-vlan
ChassisID(config-evc video_evc)#no shutdown
ChassisID(config-evc video_evc)#exit
ChassisID(config)#evc voice_evc
ChassisID(config-evc voice_evc)#s-tag 116
ChassisID(config-evc voice_evc)#connect men-port default-ethernet
ChassisID(config-evc voice_evc)#mac-switched
ChassisID(config-evc voice_evc)#no preserve-ce-vlan
ChassisID(config-evc voice_evc)#no shutdown
ChassisID(config-evc voice_evc)#exit
ChassisID(config)#evc mgmt_evc
ChassisID(config-evc mgmt_evc)#s-tag 200
ChassisID(config-evc mgmt_evc)#connect men-port default-ethernet
ChassisID(config-evc mgmt_evc)#mac-switched
ChassisID(config-evc mgmt_evc)#no preserve-ce-vlan
ChassisID(config-evc mgmt_evc)#no shutdown
ChassisID(config-evc mgmt_evc)#exit
3. Set up per-EVC, per-slot IGMP Settings on both the Active Ethernet 24-Port Access
Module and GigE SM (proxy mode used in this example).
65K110FTTP-29A 365
Revision A
ChassisID(config)#ip igmp evc video_evc 1/3 proxy host ip address

10.20.200.1
ChassisID(config)#ip igmp evc video_evc 1/3 mode proxy
ChassisID(config)#ip igmp evc video_evc 1/A proxy host ip address
10.20.200.1
ChassisID(config)#ip igmp evc video_evc 1/A mode proxy
a. Create the video EVC Map.
ChassisID(config)#evc-map video_map_cust1 1/3
ChassisID(config-evc-map video_map_cust1 1/3)#connect evc video_evc
ChassisID(config-evc-map video_map_cust1 1/3)#connect uni gigabit-
ethernet 1/3/1
ChassisID(config-evc-map video_map_cust1 1/3)#match ce-vlan-id 115
ChassisID(config-evc-map video_map_cust1 1/3)#men-pri 5
ChassisID(config-evc-map video_map_cust1 1/3)#men-c-tag-pri 0
ChassisID(config-evc-map video_map_cust1 1/3)#subscriber igmp mode
processing-enabled
ChassisID(config-evc-map video_map_cust1 1/3)#subscriber igmp
immediate-leave
ChassisID(config-evc-map video_map_cust1 1/3)#subscriber igmp proxy
ChassisID(config-evc-map video_map_cust1 1/3)#no shutdown
ChassisID(config-evc-map video_map_cust1 1/3)#exit
b. Create the data EVC Map.
ChassisID(config)#evc-map data_map_cust1 1/3
ChassisID(config-evc-map data_map_cust1 1/3)#connect evc data_evc
ChassisID(config-evc-map data_map_cust1 1/3)#connect uni gigabit-
ethernet 1/3/1
ChassisID(config-evc-map data_map_cust1 1/3)#match ce-vlan-id 90
ChassisID(config-evc-map data_map_cust1 1/3)#men-pri 0
ChassisID(config-evc-map data_map_cust1 1/3)#men-c-tag-pri 0
ChassisID(config-evc-map data_map_cust1 1/3)#no shutdown
ChassisID(config-evc-map data_map_cust1 1/3)#exit
c. Create the voice EVC Map.
ChassisID(config)#evc-map voice_map_cust1 1/3
ChassisID(config-evc-map voice_map_cust1 1/3)#connect evc voice_evc
ChassisID(config-evc-map voice_map_cust1 1/3)#connect uni gigabit-
ethernet 1/3/1
ChassisID(config-evc-map voice_map_cust1 1/3)#match ce-vlan-id 116
ChassisID(config-evc-map voice_map_cust1 1/3)#men-pri 7
ChassisID(config-evc-map voice_map_cust1 1/3)#men-c-tag-pri 0
ChassisID(config-evc-map voice_map_cust1 1/3)#no shutdown
ChassisID(config-evc-map voice_map_cust1 1/3)#exit
d. Create the management EVC Map.
ChassisID(config)#evc-map mgmt_map_cust1 1/3
ChassisID(config-evc-map mgmt_map_cust1 1/3)#connect evc mgmt_evc
ChassisID(config-evc-map mgmt_map_cust1 1/3)#connect uni gigabit-
ethernet 1/3/1
ChassisID(config-evc-map mgmt_map_cust1 1/3)#men-pri 3
ChassisID(config-evc-map mgmt_map_cust1 1/3)#men-c-tag-pri 0
ChassisID(config-evc-map mgmt_map_cust1 1/3)#no shutdown
ChassisID(config-evc-map mgmt_map_cust1 1/3)#exit
366 65K110FTTP-29A
Revision A
Home Phoneline Networking Alliance - Scope of this Section
11 Home Phoneline Networking Alliance

This section provides a brief overview of Home Phoneline Networking Alliance (HPNA), and
how to provision for HPNA.

11.3 “Introduction to HPNA” 368
6Multi-Sect-29x 367
Revision A
Home Phoneline Networking Alliance - Introduction to HPNA
11.3 Introduction to HPNA

HPNA is an alliance of leading technology companies that promote the adoption of a high
performance existing-wire home networking standard for applications such as triple-play
service. HPNA features guaranteed QOS, remote management and diagnostics. It operates
up to 320 Mbps over both coaxial and phone wires.
HPNA utilizes coaxial media and mixed phone/coaxial media for the following:
■ Networking over coaxial cable typically used in media servers and Set Top Box (STB)
home networking applications
■ MUX access over coaxial cables
■ Networking over mixed phone wires and coaxial cables for use in FTTP PONs for home
networking and multimedia applications
11.4 Provisioning
Data services for HPNA are configured on the OLT.
g NOTE
No provisioning is required when setting up HPNA on the ONT. Firmware must be downloaded
to the GG3211 during boot-up in order for HPNA to be functional. However, the ONT currently
does not support any dynamically configurable options for HPNA.
To provision for HPNA on the OLT, complete the following:

1. Access the Ethernet interface of the OLT.
ChassisID(config)#interface gigabit-ethernet 1/0/3@<shelf/slot/port>
2. Enable the HPNA interface of the OLT.
4. Verify the provisioning.
ChassisID#show interface gigabit-ethernet 1/0/3@<shelf/slot/port>
giga-eth 18/0/3@1/1/1 is IS and up
Auto Detect Configuration : Auto-Auto
Maximum MAC Allowed : 8
Loopback Configuration : No Loopback
Max Frame Size : 2000
Pause Time : 0
PPPoE Filter : Allow
Power Control : Disabled
Configuration Status : 1000 Full
Configuration : Parent Dependent
Data Communicaton Protocol: DCE
Input Stats Output Stats
Running Totals:
Packets 44744494 45001695
Bytes 1407644792 1552135366
Unicasts 44744494 45001693
Broadcasts 0 2
368 6Multi-Sect-29x
Revision A
Home Phoneline Networking Alliance - Provisioning
Multicasts 0 0
Errors 0 0
Discards 0 0
Runts 0
Giants 0
Frame Errors 0
CRC Errors 0
g NOTE
For a list of additional HPNA status commands, refer to the Total Access 5000 Series CLI
Dictionary.
6Multi-Sect-29x 369
Revision A
Home Phoneline Networking Alliance - Provisioning
370 6Multi-Sect-29x
Revision A
IEEE 802.1X - Scope of this Section
12 IEEE 802.1X

This section provides an overview of the IEEE 802.1X feature, provisioning options, useful
show commands, and example provisioning for this feature.
g NOTE

12.3 “Introduction” 372
12.5 “Show Commands” 383
12.6 “Provisioning Examples” 387
65K110FTTP-29A 371
Revision A
IEEE 802.1X - Introduction
12.3 Introduction
Port authentication is used by a network operator to securely verify the intended equipment is
installed. The device being validated is called the Supplicant, and is commonly a gateway
device installed at the customer site. An access device (such as a DSLAM, OLT, or even an
ONT) employs an IEEE 802.1X Authenticator Port Access Entity (PAE) to communicate with
the Supplicant using Extensible Authentication Protocol (EAP) messages. The Authenticator
PAE on the access device also communicates with a network operator's authentication server
(typically a RADIUS server) to perform the authentication.
Figure 12-1. Port Authentication Overview
At a high level, the Authenticator PAE on the access device serves as a form of communi-
cation bridge for the EAP message exchange between the Supplicant and the Server. The
PAE is also responsible for enforcing the authentication status (authorized or unauthorized) to
allow or block the customer traffic entering the network.
The information exchanged between the Supplicant and the Server depends on the type of
authentication requested by the Server.
12.3.1 Port-Based Authentication

Typically, the Supplicant provides a single Ethernet Medium Access Controller (MAC) that
faces the Wide Area Network (WAN). This MAC communicates with the access device via a
physical or logical Ethernet connection, such as an EFM-Port, an EFM-Group, or a native
Ethernet connection. It is also common for this Supplicant WAN-facing MAC to be a routing
interface, which implies that all outbound traffic from this MAC has a single fixed source MAC
address.
The IEEE 802.1X standard is designed to manage Authenticators on a per interface basis.
The ADTRAN implementation of IEEE 802.1X is consistent with authentication on the basis of
physical or logical interface.
The Authenticator PAE on the access device instantiates one Authenticator entity on each of
its subscriber-facing Ethernet MAC interfaces (which can be an EFM-Port, EFM-Group, or
native Ethernet connection). The Authenticator PAE supports managed objects and maintains
authentication state machines on each of these Authenticators. Since there is assumed to be
one MAC address per Supplicant port, the access device learns this MAC address from the
incoming Extensible Authentication Protocol Over Local Area Network (EAPoL) packets and
uses it as a key parameter in the validation and enforcement of the authentication state.
The access device can support multiple services over each Ethernet interface. These services
are realized using VLANs to separate the traffic and EVC-Maps as the provisioning model. All
372 65K110FTTP-29A
Revision A
of the services for a given subscriber interface are assumed to be terminated by a single
Supplicant MAC, and also a single Supplicant MAC address. The Authentication status
(authorized or unauthorized) for the port is enforced equally for all services on that port. If the
port is IEEE 802.1X authorized, then all customer traffic is allowed on the MAC address
learned from the Supplicant. If the port is IEEE 802.1X unauthorized, then no customer traffic
is allowed on that MAC address.
12.3.2 RADIUS Relay Agent

In order to avoid providing public addresses for the RADIUS clients in the network, a RADIUS
relay agent can be placed between the RADIUS clients and the RADIUS authentication server.
The RADIUS clients communicate with the Authentication server through the RADIUS relay
agent.
Each RADIUS client operates the same whether talking directly to the authentication server or
to the relay agent. This allows for deployment with or without the relay agent without any
changes to the RADIUS client software. The RADIUS client is configured with the IP address
and shared secret of the authentication server. The RADIUS relay agent acts as a NAT
gateway between the RADIUS client and the authentication server. Optionally, it can also
enforce common values for RADIUS message attributes like NAS-Identifier and NAS-IP-
Address for all RADIUS messages being sent to the Authentication server.
12.3.2.1 RADIUS Attributes

RADIUS messages can include combinations of the attributes listed in Table 12-2.
Table 12-2. RADIUS Attributes
Attribute Meaning Example RADIUS Messages
Message- RADIUS message Per RADIUS RFC Access-Request

Authenticator(80) authenticator Access-Challenge
Access-Accept
Access-Reject
State(24) RADIUS message Per RADIUS RFC Access-Request

state (for challenges)
Access-Challenge
User-Name(1) Supplicant Per supplicant Access-Request

EAP-Identity Access-Challenge
Access-Accept
Access-Reject
NAS-IP-Address(4) RADIUS client IP 10.100.42.95 Access-Request

address (binary)
Calling-Station-Id(31) Supplicant MAC 00-A0-C8-A7-AC-CE Access-Request

address (ASCII)
NAS-Identifier(32) ASCII TID of the PAE TA5000-Huntsville Access-Request

host system
EAP-Message(79) EAP message to/from N/A Access-Request

the Supplicant (for challenges)
Access-Challenge
Access-Accept
Access-Reject
65K110FTTP-29A 373
Revision A
Table 12-2. RADIUS Attributes (Continued)
Attribute Meaning Example RADIUS Messages
NAS-Port-Id(87) ASCII identifier of the eth 1/17/1 Access-Request

PAE Access-Request
port hosting the
Supplicant
Vendor-Specific(26) Vendor-specific Access-Request

attribute with sub-
attributes:
■ Vendor ID (binary) ■ Adtran (664)
■ 101: ASCII Vendor ■ ADTRAN
name
■ 102: ASCII slot part ■ 1187121L1
number
Session-Timeout(27) Session timeout N/A Access-Accept

(binary). Sets the PAE Access-Challenge
reauth or supplicant-
side timeout
Termination-Action(29) Termination action N/A Access-Accept

(binary). The presence Access-Challenge
of this attribute is used
by the PAE to interpret
its response to the
Session-Timeout
374 65K110FTTP-29A
Revision A
IEEE 802.1X - Provisioning
12.4 Provisioning
To provision for IEE 802.1X authentication, complete the following.
12.4.1 Step 1: Provision a Subtended Host for RADIUS Client

Provision the subtended host that will be used by the RADIUS client. It is necessary to create
an EVC that connects the subtended host to a VLAN and a physical interface that faces the
RADIUS server.
1. Create an EVC.
a. Access the Global Configuration Command Set.
b. Access the EVC Interface Configuration Command Set.
Substitute WORD for an alphanumeric string used to identify the EVC. If the EVC
with this identifier does not exist, a new one is created.
c. Set the S-tag for the EVC.
d. Apply this EVC to the default ethernet interface as a MEN port.
e. Enable the EVC.
2. Provision the subtended host.
a. Access the GPON Interface Configuration Command Set.
b. Set the S-tag for the subtended host.
ChassisID(config-gpon x/x/x)#subtended-host <ont-id> s-tag <2-4094>
c. Set the S-tag priority for the subtended host.
ChassisID(config-gpon x/x/x)#subtended-host <ont-id> s-tag-priority
<0-7>
d. Select the method of inband management.
65K110FTTP-29A 375
Revision A
Static ChassisID(config-gpon x/x/x)#subtended-host Set the static IP

IP <ont-id> ip address a.b.c.d a.b.c.d address and subnet
mask for the ONT’s
inband management.
to step e.
DHCP ChassisID(config-gpon x/x/x)#subtended-host Allocate the IP

IP <ont-id> ip address dhcp address for the
ONT’s inband
management
dynamically using
DHCP.
to step f.
e. If using a static IP address, set the default gateway for the subtended-host.
ChassisID(config-gpon x/x/x)#subtended-host <ont-id> ip default-
gateway A.B.C.D
f. Set the activation mode.
ChassisID(config-gpon x/x/x)#activation-mode auto-activate
g. Enable the OLT interface.
ChassisID(config-gpon x/x/x)#no shutdown
h. If using a DHCP IP address, view the DHCP address for a AE subtended-host.
ChassisID(config-giga-eth x/x/x)#do show interfaces gigabit-
ethernet <shelf/slot/pon> subtended-host
i. Return to the Global Configuration Command Set.
ChassisID(config-gpon x/x/x)#exit
376 65K110FTTP-29A
Revision A
12.4.2 Step 2: Provision a RADIUS Server and Group

To provision a RADIUS server(s) and group, complete the following:
1. Access the RADIUS Server Command Set.
ChassisID(config)#port-auth server radius WORD
2. Set the IP address of the RADIUS server.
ChassisID(config-server-radius radserver)#ip-address A.B.C.D
3. Set the shared secret.
ChassisID(config-server-radius radserver)#key WORD
ChassisID(config-server-radius radserver)#exit
5. Access the RADIUS Group Command Set.
ChassisID(config)#port-auth group radius WORD
6. Add the RADIUS server to the RADIUS group.
ChassisID(config-group-radius radgroup)#add server WORD sequence-number
<1-4>
7. Set the NAS-Port-ID format.
This provides an interface description format that identifies the physical interface used for
authenticating subscribers.
g NOTE
For the FTTP application, the NAS Port ID string should end in “$ontslot$.$ontport$. For
example, a suitable NAS Port ID format string would be "PON_1/1/$slot$/
$port$:$ont$.$ontslot$.$ontport$".
ChassisID(config-group-radius radgroup)#nas-port-id WORD

ChassisID(config-group-radius radgroup)#exit
65K110FTTP-29A 377
Revision A
12.4.3 Step 3: Provision the ONT Port

To provision the ONT port, complete the following:
1. Access the interface of the ONT.
ChassisID(config)#interface [gigabit-ethernet|efm-port] <ont-id/0/
■ The eth-port is the Ethernet port number on the ONT; port is the PON port on the OLT to
which the ONT is connected.
■ If using an 1108VP GPON MDU, use efm-port as the selected interface. For all other
ONTs, use gigabit-ethernet.
ChassisID(config-interface x/x/x@x/x/x.gpon)#no shutdown
3. Connect the ONT to the selected IP host and RADIUS server group.
ChassisID(config-interface x/x/x@x/x/x.gpon)#port-auth connect
subtended-host WORD radius group WORD
4. Use Table 12-4 for any additional provisioning options.
Table 12-4. Additional Options
Command Description Default
ChassisID(config-interface x/x/x@x/ If the port mode is set to auto, force-authorized

x/x.gpon)#port-auth port-control the Supplicant via RADIUS is
[auto|force-authorized|force- authenticated before traffic
unauthorized] passes through the network. If
the port mode is set to force-
authorized or force-
unauthorized, the authorization
is fixed.
ChassisID(config-interface x/x/x@x/ This sets the allotted time 60

x/x.gpon)#port-auth timeout quiet- before the 802.1X PAE restarts
period <1-65535> after a failed 802.1X
authorization attempt.
ChassisID(config-interface x/x/x@x/ This sets the allotted time for 30

x/x.gpon)#port-auth timeout server the Access Module to contact
<1-4294967295> the RADIUS server(s).

ChassisID(config-interface x/x/x@x/x/x.gpon)#exit
378 65K110FTTP-29A
Revision A
12.4.4 Step 4: Provision the RADIUS Relay Agent

1. Create a private IP Host.
b. Access the IP Host Configuration Command Set.
Substitute WORD for an alphanumeric string used to identify the IP Host. If an IP
Host with this identifier does not already exist, a new one is created.
ChassisID(config)#interface ip-host WORD <shelf/slot>
g NOTE
IP Host names are case sensitive.
c. Set the static IP address and subnet mask for the IP Host interface.
ChassisID(config-ip-host name x/x)#ip address A.B.C.D A.B.C.D
g NOTE
Configure the private IP Host’s IP address as the default gateway address for all subtended
hosts using the relay.
d. Disable the default gateway.

ChassisID(config-ip-host name x/x)#no default-gateway
g NOTE
The IP address should be unique among other IP Hosts in the system.
e. Enable the IP Host.

ChassisID(config-ip-host name x/x)#no shutdown
2. Create a public IP Host.
b. Access the IP Host Configuration Command Set.
Substitute WORD for an alphanumeric string used to identify the IP Host. If an IP
Host with this identifier does not already exist, a new one is created.
ChassisID(config)#interface ip-host WORD <shelf/slot>
g NOTE
IP Host names are case sensitive.
c. Set the static IP address and subnet mask for the IP host interface.
ChassisID(config-ip-host name x/x)#ip address A.B.C.D A.B.C.D
d. Assign the IP address of the default gateway.
ChassisID(config-ip-host name x/x)#default-gateway A.B.C.D
g NOTE
The IP address should be unique among other IP Hosts in the system.
65K110FTTP-29A 379
Revision A
e. Enable the IP Host.

ChassisID(config-ip-host name x/x)#no shutdown
3. Create an EVC for the private IP Host.
b. Access the EVC Interface Configuration Command Set.
Substitute WORD for an alphanumeric string used to identify the EVC. If the EVC
with this identifier does not exist, a new one is created.
g NOTE
c. Set the S-tag for the EVC.

d. Apply this EVC to the private IP Host.
ChassisID(config-evc name)#connect ip-host WORD <shelf/slot>
e. Enable the EVC.
f. Return to the Global Configuration Command Set.
4. Provision the System Management EVC for the public IP Host.
a. Access the System Management EVC Interface Configuration Command Set.
ChassisID(config)#system-management-evc
b. Set the system management VLAN to the required ID.
ChassisID(config-sys-mgmt-evc)#s-tag <1-4094>
c. Apply this EVC to the default ethernet interface as a MEN port.
ChassisID(config-sys-mgmt-evc)#connect men-port default-ethernet
d. Apply this EVC to the public IP Host.
ChassisID(config-sys-mgmt-evc)#connect ip-host WORD <shelf/slot>
5. Configure the RADIUS Relay Agent.
g NOTE
The RADIUS relay can use UDP source ports 1025-65535 to communicate with the authenti-
cation server.
a. Access the RADIUS Relay Command Set.

ChassisID(config)#port-auth radius-relay WORD <shelf/slot>
b. Connect the public IP Host to the RADIUS relay.
ChassisID(config-relay name x/x)#connect public ip-host WORD
<shelf/slot>
380 65K110FTTP-29A
Revision A
c. Use Table 12-5 for any additional provisioning options.
Table 12-5. Additional Options
Command Description
ChassisID(config-relay name x/x)#radius- Configures the RADIUS relay to ensure

attribute nas-identifier word that the NAS-Identifier attribute value
matches the configured string. If the
string includes the token
“$accessnodeid$”, then the system TID
will be inserted in its place.

attribute nas-ip-address public-ip that the NAS-IP-Address attribute value
matches the public IP Host’s IP
address.

attribute user-name calling-station-id that the User-Name attribute value is
the MAC address contained in the
Calling-Station-ID attribute.
ChassisID(config-relay name x/x)#radius- Configures the Vendor-Specific

attribute vendor-specific id <number> sub-type attribute.
<number> sub-value word
ChassisID(config-relay name x/x)#radius- Configures the RADIUS Relay to

attribute calling-station-id mac-delimiter regulate the Calling-Station-Id attribute
[colons|hyphens] value. If the value appears to represent
a MAC address, ensure the delimiter is
the selected type (colons or hyphens),
updating the value if necessary.
ChassisID(config-relay name x/x)#radius- Configure the RADIUS Relay to filter

attribute allow <attribute name> messages to only allow the specified
RADIUS attributes. There should be
one "radius-attribute allow <attribute
name>" command for each attribute
type that should be allowed through the
Relay.
ChassisID(config-relay name x/x)#radius- Configures the RADIUS Relay to filter

attribute allow attribute-id * messages as the above command.
However, this command provides the
flexibility to select any attribute by
attribute ID.
ChassisID(config-relay name x/x)#radius- Configures the RADIUS Relay to not

attribute allow all filter attributes from RADIUS messages.
d. Enable the interface.

ChassisID(config-relay name x/x)#no shutdown
e. Return to the Global Configuration Command Set.
ChassisID(config-relay name x/x)#exit
65K110FTTP-29A 381
Revision A
12.4.5 Step 5: Enable System-Wide 802.1X Authentication

Use the following command to enable IEEE 802.1X for the entire system:
g NOTE
The per-port settings take effect only if the system-level port-auth setting is enabled.
ChassisID(config)#port-auth
382 65K110FTTP-29A
Revision A
IEEE 802.1X - Show Commands
12.5 Show Commands

Use the following commands for viewing status and provisioning information.
12.5.1 Status Commands
12.5.1.1 GPON Port Status

ChassisID#show interface gpon <shelf/slot/port>
gpon 1/19/2 is IS and up
Number of Configured ONTs : 1
Number of Discovering ONTs : 0
Number of Unrecognized ONTs : 0
Number of Operational ONTs : 1
Number of Available HW Resour : 959
Longest Fiber Distance : ont-1, 159m
Shortest Fiber Distance : ont-1, 159m
Oversubscription Allowed : true
Downstream Upstream
Max Provisionable BW kbps : 2488320 1244160
Configured PIR BW kbps : 0 0
Configured Fixed BW kbps : na 0
Configured Assured BW kbps : na 0
Configured min-rate BW kbps : 0 na
Available PIR BW kbps : 2488320 1244160
Available CIR BW kbps : na 1194848
Available min-rate BW kbps : 2488000 na
Current PIR BW kbps : 0 0
Current CIR BW kbps : na 0
12.5.1.2 GPON Port Provisioning

ChassisID#show run interface gpon <shelf/slot/port>
interface gpon 1/19/2
activation-mode auto-activate
subtended-host 1 ip address 192.168.10.121 255.255.255.0
subtended-host 1 ip default-gateway 192.168.10.1
subtended-host 1 s-tag 410
no shutdown
12.5.1.3 ONT Port Status

ChassisID#show remote-device <ont ID>@<shelf/slot/port>
remote-device ont 1@1/19/2.gpon
ont 1@1/19/2 is IS and up
Uptime : 0 days, 01 hours, 15 minutes, 54 seconds
Description :
Activated Serial Number : CIGG60871237
Ont Software Version : H00.01.0004.K1
Ont Boot Software Version : na
Ont Upgrade Status : Not Started
Ont Part Number : 00102-00002-21
65K110FTTP-29A 383
Revision A
Ont RSSI dBm : -17.4

Ont Upstream BIP : 0
Ont Downstream BIP : 0
Ont RDI : 0
Ont RX Ploam CRC Error : 0
Ont US Good DBRu : 0
Ont US Bad DBRu : 0
Ont Equalization Delay bit : 265555
Ont Fiber Distance m : 159
Ont ACS Server Profile :
Ont ACS Username :
Ont last error : VoIP provisioning: VoIP IP host not
supported
12.5.1.4 ONT Port Provisioning

ChassisID#show run interface gigabit-ethernet <ont ID>@<shelf/slot/port>
interface gigabit-ethernet 1/0/1@1/19/2.gpon
mac limit 8
no shutdown
port-auth timeout quiet-period 60
port-auth timeout server 30
12.5.1.5 ONT Gigabit Port 802.1X Status

ChassisID#show port-auth interface gigabit-ethernet <RD ID/0/RD
interface gigabit-ethernet 1/0/1@1/19/2 is IS and up
EAPoL Protocol Version : 0
PAE Capabilities : authenticator only
Authenticator State : initialize
Backend Auth State : initialize
Port Auth Status : unauthorized
Control Direction : both
Port Control : force authorized
Re-authentication : disabled
Last Config Error : none
12.5.1.6 Radius Relay Agent Status

ChassisID#show port-auth radius-relay WORD <shelf/slot>
port-auth radius-relay basicRelay 1/A is IS and up
Valid Client Requests : 0
Valid Server Challenges : 0
Valid Server Accepts : 0
Valid Server Rejects : 0
Invalid Message Authenticator : 0
Invalid Client Packet Format : 0
Invalid Server Packet Format : 0
Unknown Client Code : 0
Unknown Server Code : 0
Client Dropped : 0
Client Missing Attribute : 0
Unknown Server : 0
Last Error : Running
384 65K110FTTP-29A
Revision A
12.5.2 Performance-Monitoring Commands
12.5.2.1 Current ONT 802.1X Statistics

ChassisID#show port-auth statistics interface gigabit-ethernet
<RD ID/0/RD port>@<shelf/slot/port> performance-statistics 15-minute
gigabit-ethernet 1/0/1@1/19/2 15-Min PM (Current)
Receive Transmit
EAPoL Total Frames : 0 0
EAP Request ID Frames : na 0
EAP Request Frames : na 0
EAP Response ID Frames : 0 na
EAP Response Frames : 0 na
EAP Length Error Frames : 0 na
EAPoL Start Frames : 0 na
EAPoL Logoff Frames : 0 na
EAPoL Invalid Frames : 0 na
12.5.2.2 Previous ONT 802.1X Statistics

ChassisID#show port-auth statistics interface gigabit-ethernet <RD ID/0/RD
port>@<shelf/slot/port> performance-statistics 15-minute 1
gigabit-ethernet 1/0/1@1/19/2 15-Min PM (1) 09/10 17:15
Receive Transmit
EAPoL Total Frames : 0 0
EAP Request ID Frames : na 0
EAP Request Frames : na 0
EAP Response ID Frames : 0 na
EAP Response Frames : 0 na
EAP Length Error Frames : 0 na
EAPoL Start Frames : 0 na
EAPoL Logoff Frames : 0 na
EAPoL Invalid Frames : 0 na
12.5.2.3 Current ONT Radius Statistics

ChassisID#show port-auth server subtended-host <RD ID>@<shelf/slot/port>
performance-stat 15-minute
1@1/19/2 15-Min PM (Current)
Receive Transmit
Access Request Packets : na 0
Access Rerequest Packets : na 0
Access Challenge Packets : 0 na
Access Accept Packets : 0 na
Access Reject Packets : 0 na
Invalid Packets : 0 na
Bad Authenticators : 0 na
Client Timeouts : 0 na
Unknown Types : 0 na
Packets Dropped : 0 na
65K110FTTP-29A 385
Revision A
12.5.2.4 Previous ONT Radius Statistics

ChassisID#show port-auth server subtended-host <RD ID>@<shelf/slot/port>
performance-stat 15-minute 1
1@1/19/2 15-Min PM (1) 09/10 17:30
Receive Transmit
Access Request Packets : na 0
Access Rerequest Packets : na 0
Access Challenge Packets : 0 na
Access Accept Packets : 0 na
Access Reject Packets : 0 na
Invalid Packets : 0 na
Bad Authenticators : 0 na
Client Timeouts : 0 na
Unknown Types : 0 na
Packets Dropped : 0 na
12.5.2.5 Current Relay Agent Statistics

ChassisID#show port-auth radius-relay WORD <shelf/slot> performance-stat
15-minute
port-auth radius-relay 1/A basicRelay is IS and up
Current Interval (11:15)
Client Dropped : 0
Unknown Server : 0
12.5.2.6 Previous Relay Agent Statistics

ChassisID#show port-auth radius-relay WORD <shelf/slot> performance-stat
15-minute 1
port-auth radius-relay 1/A basicRelay is IS and up
Current Interval (11:00)
Client Dropped : 0
Unknown Server : 0
386 65K110FTTP-29A
Revision A
IEEE 802.1X - Provisioning Examples
12.6 Provisioning Examples

12.6.1 Example 1 - One RADIUS Server in the Network with RADIUS
Relay
In this example the following is assumed:
■ One RADIUS server
■ Relay Agent
■ RADIUS client active on slot 1/17 with an IP address of 10.100.42.95
♦ RADIUS traffic on VLAN 4092 on the gigabit-ethernet interface 1/2/8
■ Subscriber on Gig-port 1/0/1@1/17/1
1. Enable port authentication for the system.
2. Define the RADIUS server and server group.
ChassisID(config)#port-auth server radius radiusServer
ChassisID(config-server-radius radiusServer)#ip-address 10.47.84.20
ChassisID(config-server-radius radiusServer)#key secret
ChassisID(config)#port-auth group radius radiusGroup
ChassisID(config-group-radius radgroup radiusGroup)#add server
radiusServer sequence-number 1
ChassisID(config-group-radius radgroup radiusGroup)#nas-port-id PON_1/
1/$slot$/$port$:$ont$.$ontslot$.$ontport$
3. Provision the subtended host that will be used by the RADIUS client. It is necessary to
create an EVC that connects the subtended host to a VLAN and a physical interface that
faces the RADIUS server.
ChassisID(config)#evc evc-4092
ChassisID(config-evc evc-4092)#s-tag 4092
ChassisID(config-evc evc-4092)#connect men-port gigabit-ethernet 1/2/8
ChassisID(config-evc evc-4092)#connect ip-host PRIVATE 1/A
ChassisID(config-evc evc-4092)#mac-switched
ChassisID(config-evc evc-4092)#no shutdown
ChassisID(config)#interface gpon 1/17/1
ChassisID(config-gpon 1/17/1)#subtended-host 1 s-tag 4092
ChassisID(config-gpon 1/17/1)#subtended-host 1 s-tag priority 1
ChassisID(config-gpon 1/17/1)#subtended-host 1 ip address 10.100.42.95
255.255.255.0
ChassisID(config-gpon 1/17/1)#subtended-host 1 ip default-gateway
10.100.42.254
ChassisID(config-gpon 1/17/1)#no shutdown
4. Provision the System Management EVC for the public IP Host.
ChassisID(config)#system-management-evc
ChassisID(config-sys-mgmt-evc)#s-tag 2094
ChassisID(config-sys-mgmt-evc)#connect men-port default-ethernet
ChassisID(config-sys-mgmt-evc)#connect ip-host PUBLIC 1/A
65K110FTTP-29A 387
Revision A
5. Provision a private IP Host.

ChassisID(config)#interface ip-host PRVIATE 1/A
ChassisID(config-ip-host PRIVATE 1/A)#ip address 10.100.42.254
255.255.255.0
ChassisID(config-ip-host PRIVATE 1/A)#no default-gateway
ChassisID(config-ip-host PRIVATE 1/A)#no shutdown
6. Create a Public IP Host.
ChassisID(config)#interface ip-host PUBLIC 1/A
ChassisID(config-ip-host PUBLIC 1/A)#ip address 10.47.84.200
255.255.255.0
ChassisID(config-ip-host PUBLIC 1/A)#default-gateway 10.47.84.254
ChassisID(config-ip-host PUBLIC 1/A)#no shutdown
7. Configure the RADIUS Relay Agent.
ChassisID(config)#port-auth radius-relay basicRelay 1/A
ChassisID(config-relay basicRelay 1/A)#connect public ip-host PUBLIC 1/
A
ChassisID(config-relay basicRelay 1/A)#radius-attribute nas-identifier
EXAMPLE
ChassisID(config-relay basicRelay 1/A)#radius-attribute nas-ip-address
public-ip
ChassisID(config-relay basicRelay 1/A)#radius-attribute user-name
calling-station-id
ChassisID(config-relay basicRelay 1/A)#radius-attribute vendor-specific
id 193 sub-type 101 sub-value EXAMPLE
ChassisID(config-relay basicRelay 1/A)#no shutdown
8. Enable the ONT interfaces for the subscriber ports. Configure port authentication
parameters on the gigabit-ethernet port including the associated RADIUS server group.
ChassisID(config-giga-eth 1/0/1@1/17/1.gpon)#no shutdown
ChassisID(config-giga-eth 1/0/1@1/17/1)#port-auth port-control auto
ChassisID(config-giga-eth 1/0/1@1/17/1)#port-auth timeout quiet-period
20
ChassisID(config-giga-eth 1/0/1@1/17/1)#port-auth timeout server 30
ChassisID(config-giga-eth 1/0/1@1/17/1)#port-auth connect subtended-
host radius group radiusGroup
388 65K110FTTP-29A
Revision A
12.6.2 Example 2 - Two RADIUS Servers in the Network without

RADIUS Relay Agent
■ Two RADIUS servers (A, B) in the network
♦ System groups both servers into the same server group
♦ Server A is queried first, with fallback to server B
■ RADIUS client active on slot 1/17 with IP address 10.100.42.95
♦ RADIUS traffic on VLAN 4092 on gigabit-ethernet interface 1/2/8
■ Subscriber on Gig-port 1/0/1@1/17/1
1. Enable port authentication for the system.
2. Define the RADIUS servers and server group.
ChassisID(config)#port-auth server radius radiusServerA
ChassisID(config)#port-auth server radius radiusServerB
ChassisID(config)#port-auth group radius radiusGroup
ChassisID(config-group-radius radiusGroup)#add server radiusServer
sequence-number 1
ChassisID(config-group-radius radiusGroup)#add server radiusServer
sequence-number 1
ChassisID(config-group-radius radiusGroup)#nas-port-id nas-port-id
PON_1/1/$slot$/$port$:$ont$.$ontslot$.$ontport$
3. Provision the subtended host that will be used by the RADIUS client. It is necessary to
create an EVC that connects the subtended host to a VLAN and a physical interface that
faces the RADIUS server.
ChassisID(config)#evc evc-4092
ChassisID(config-evc evc-4092)#s-tag 4092
ChassisID(config-evc evc-4092)#connect men-port gigabit-ethernet 1/2/8
ChassisID(config-evc evc-4092)#mac-switched
ChassisID(config-evc evc-4092)#no shutdown
ChassisID(config)#interface gpon 1/17/1
ChassisID(config-gpon 1/17/1)#subtended-host 1 s-tag 4092
ChassisID(config-gpon 1/17/1)#subtended-host 1 s-tag priority 1
ChassisID(config-gpon 1/17/1)#subtended-host 1 ip address 10.100.42.95
255.255.255.0
ChassisID(config-gpon 1/17/1)#subtended-host 1 ip default-gateway
10.100.42.254
ChassisID(config-gpon 1/17/1)#no shutdown
4. Enable the ONT interfaces for the subscriber ports. Configure port authentication
parameters on the gigabit-ethernet port including the associated RADIUS server group.
65K110FTTP-29A 389
Revision A
ChassisID(config-giga-eth 1/0/1@1/17/1.gpon)#port-auth port-control

auto
ChassisID(config-giga-eth 1/0/1@1/17/1.gpon)#port-auth timeout quiet-
period 20
ChassisID(config-giga-eth 1/0/1@1/17/1.gpon)#port-auth timeout server
30
ChassisID(config-giga-eth 1/0/1@1/17/1.gpon)#port-auth connect ip-host
radiusIpHost radius group radiusGroup
ChassisID(config-giga-eth 1/0/1@1/17/2.gpon)#port-auth port-control
auto
ChassisID(config-giga-eth 1/0/1@1/17/2.gpon)#ort-auth timeout quiet-
period 20
ChassisID(config-giga-eth 1/0/1@1/17/2.gpon)#port-auth timeout server
30
ChassisID(config-giga-eth 1/0/1@1/17/2.gpon)#port-auth connect ip-host
radiusIpHost radius group radiusGroup
390 65K110FTTP-29A
Revision A
Activation Mode - Scope of this Section
13 Activation Mode

This section provides four different methods for activating your GPON ONT. Each method
contains a list of pros and cons associated with that registration method.

13.3 “Manual Activation” 392
13.4 “Auto-Discovery” 393
13.5 “Auto-Activation” 394
13.6 “Registration-ID Activation” 395
65K110FTTP-29A 391
Revision A
Activation Mode - Manual Activation
13.3 Manual Activation

g NOTE
Registration ID, for the ADTRAN 424RG, is performed by Serial Number Activation. This
occurs when the ONT is “Discovered” by the OLT.
If AOE Auto Upgrade is active, a new ONT installation will be detected and a fast blinking
FIBER LED will indicate a new software download has commenced. This may take 5 - 10
minutes to complete.
13.3.1 Pro
Manual activation provides the most control to service operators.
13.3.2 Con
Only ONTs specifically entered into the OLT are allowed to be active on the PON.
What’s Next
■ For CLI Manual Activation, continue to Section 2.3.1, “OLT/PON Provisioning” on
page 50.
■ For Web Manual Activation, continue to Section 2.3.1, “OLT/PON Provisioning” on
page 50.
392 65K110FTTP-29A
Revision A
Activation Mode - Auto-Discovery
13.4 Auto-Discovery
Auto-Discovery mode adds the ability to discover a new ONT when connected but does
not activate the new ONT until the required provisioning is entered into the OLT. The
discovery operation is performed every 20 seconds. The feature allows selecting the
appropriate ONT SN from a list of “discovered” ONT SNs when provisioning the SN infor-
mation into the OLT. The first three steps in “Manual Activation” are still needed but the
SN can be selected from the list rather than typed in by hand.
13.4.1 Pros
■ Provides a very secure method as the serial number (S/N) of the unit must match the
S/N configured in the Total Access 5000 OLT.
■ Provides the most efficient manner to provision the S/N and the desired ONT-ID
number between 1 - 32/64 depending on your OLT.
13.4.2 Cons
■ Prior to beginning the installation process, the S/N of the ONT must be known by the
group that provisions the Total Access 5000 and by the installation group. The unit
with the same S/N must be selected by the person installing the ONT and must be
installed at the precise location that was pre-provisioned at the Total Access 5000.
■ Process can be very difficult to coordinate S/N of the ONTs between the two groups.
What’s Next
■ For CLI Auto-Discovery, continue to Section 3.3.1, “OLT/PON Provisioning” on
page 116.
■ For Web Auto-Discovery, continue to Section 3.3.1, “OLT/PON Provisioning” on
page 116.
65K110FTTP-29A 393
Revision A
Activation Mode - Auto-Activation
13.5 Auto-Activation
Auto-Activation mode is the most open (insecure) version of the activation modes. This
mode periodically (every 20 seconds) scans the GPON interface for any newly added
ONT and automatically assigns an ONT-ID, learns the SN, and activates the ONT.
Caution is advised when using this mode. If an ONT needs to be replaced then the
replacement ONT will automatically be discovered and activated using a new ONT-ID.
The replaced ONT's services will not be moved to the new ONT because there is no way
for the OLT to know that the new ONT is a replacement device instead of a new device.
The proper way to replace an ONT in this mode is to edit, in the OLT, the SN of the ONT to
be replaced to match the new ONT SN value. Then the replacement ONT can be attached
and all services will be associated to the new ONT.
13.5.1 Pros
■ Provides the easiest method to use in the field because the unit is automatically
discovered by the OLT and is automatically assigned an ONT-ID between 1 and 32/
64.
13.5.2 Cons
■ Provides the most insecure method.
■ Assigns ONT-ID automatically, therefore the management and provisioning of
services is more difficult.
■ Creates a difficulty to provision services to the correct ONT-ID if several ONTs have
been placed in the field prior to provisioning the OLT. If all ONTs on the same PON
have the same service profile it becomes easier to provision, but the location of the
ONT must match the provisioning OLT for billing and management purposes.
■ Creates an ONT replacement problem. The replaced services will not be moved to the
new ONT because there is no way for the OLT to know that the new ONT is a
replacement device as opposed to a new device. The proper method to replace an
ONT in this mode is to edit, in the OLT, the S/N of the ONT to be replaced to match
the new ONT S/N value. Then the replacement ONT can be attached and all services
will be associated to the new ONT.
What’s Next
■ For CLI Auto-Activation, continue to Section 3.3.1, “OLT/PON Provisioning” on
page 116.
■ For Web Auto-Activation, continue to Section 3.3.1, “OLT/PON Provisioning” on
page 116.
394 65K110FTTP-29A
Revision A
Activation Mode - Registration-ID Activation
13.6 Registration-ID Activation

Registration-ID Activation provides two methods for use:
■ Lock Serial Number
■ Unlock Serial Number
g NOTE
If the Registration-ID is programmed into the ONT, it is ignored unless the PON is set to
the Registration-ID method.
Registration-ID activation offers a secure way to add only ONTs that are expected to be
installed without requiring the installer to know the SN of the ONT being installed. SNs are
programmed into ONTs at the factory and cannot be changed. Using the manual or auto-
discovery activation modes would normally mean that a specific ONT device must be
installed at a specific location before the OLT will activate it. Registration-ID activation
allows a unique 10-digit number to be programmed into the ONT by the installation
technician during installation. The matching Registration-ID is provisioned into the OLT
instead of the SN along with the ONT-ID value. Once the ONT is discovered the ONT will
be activated using the Registration-ID without regard to the SN value programmed by the
factory for the first activation. Future activations of the ONT will match the Registration-ID
and the SN. The ONT SN will be displayed in the learned SN and the provisioned SN
column.
g NOTE
The Serial Number and Registration-ID are matched only in loc
There is another advantage Registration-ID activation mode offers over the previous
methods. ONT replacement is significantly simplified using this method. In lock mode, if
the S/N is provisioned at the OLT, the S/N must be either removed or changed in a
replacement scenario. In unlock mode, as long as either Registration-ID or S/N matches
the ONT connected to the PON, the ONT would come UP.
The only action that needs to be performed on the ONT is that the replacement ONT must
be provisioned with the same Registration-ID that is programmed into the OLT for that
associated ONT. ONT Replacement should follow these steps to ensure successful
replacement:
g NOTE
The following steps apply to both modes. In the lock mode, if there is a S/N (learned or
provisioned) that needs to be removed or matched with the ONT being replaced.
1. Disconnect the ONT to be replaced from the fiber.

2. Provision the correct Registration-ID into the replacement ONT (see “Enter the
Registration-ID” on page 53).
3. Connect the replacement ONT to the fiber.
g NOTE
A replacement ONT will not be activated as long as another ONT is activated that contains
the same Registration-ID. This prevents removing services from a customer should a
duplicate Registration-ID be accidentally entered into a new ONT being installed on the
fiber. Only an ONT in the “Discovering” state will be replaced when a Registration-ID is
matched to a new ONT.
65K110FTTP-29A 395
Revision A
When there is only a S/N programmed for the ONT and no Registration-ID provisioned at
the OLT, if preferable, you can change to any one of the Registration-ID modes. In both
cases, the ONTs would come up.
If Registration-IDs are provisioned only at the OLT, then unlock mode would bring UP the
ONTs (as S/N match) whereas lock mode would not as it requires both S/N and Regis-
tration-ID (which are not programmed in ONT in this case) and so lock mode would not be
able to activate the ONTs.
If S/N and Registration-ID are provisioned at the OLT, unlock mode matches the S/N or
Registration-ID, whereas lock mode matches the S/N and Registration-ID.
The unlock serial number option of the Registration-ID mode allows customers to deploy
Registration-ID provisioned ONTs, on top of brownfield networks that previously only used
serial number registration (instead of registration ID). This is done by changing the mode
of the PON to "Registration ID" mode with suboption unlock-serial-number. In this mode, if
the OLT has a provisioned SN that matches the ONT's SN, then the ONT will register with
the matching ONT ID in the OLT. The registration ID will not be asked from the ONT in this
case. Thus provisioned serial number is prioritized over registration ID. If there is no provi-
sioned serial number then the provisioned Registration ID will be requested from the ONT
and matched upon. If this also fails then the OLT alarms that an unknown Serial
Numbered ONT has been connected.
This mode will help customers when they have many ONTs installed and running in the
field that were registered via serial number. Now the customer wants to move their
network to a registration ID mode without isolating/blocking the previous installed base of
ONTs. In the updated "unlock-serial-number" mode, the user's ONTs would automatically
register on the PON since they have provisioned Serial Numbers in the OLT
Another scenario is when a user either has ONTs that do not support Registration-ID
mode or they want to continue deploying existing ONTs (without Registration IDs) and new
ONT's (with Registration-ID), but keep them in the same network. This new mode (regis-
tration ID unlock) gives the user the ultimate flexibility in deploying a network. Even if a
user would like to continue installing via serial number up to some date in the future, they
can still convert the PON to this mode and seamlessly transition from "serial" number
deployments to "registration-ID" deployments, without further NOC intervention.
g NOTE
If the activation mode is lock-serial number, then future activations of the ONT will match
both the Registration-ID and the SN. If the activation mode is unlock-serial number, then
future activations of the ONT will match either the SN or the Registration-ID and the SN
take higher precedence over Registration-ID.
13.6.1 Pros
■ Provides the most secure method of registration.
■ Provides the easiest method to administrate. The installer does not need to know the
S/N of the unit being installed.
■ Provides for easier ONT replacement. If the activation registration lock-serial-number
method is used, the installer only needs to know the registration ID. Only one change
needs to be made to achieve complete service migration to the replacement ONT.
♦ The management team must delete the ONT S/N from the OLT provisioning.
Applicable to lock mode only. In unlock mode, either S/N or Registration-ID need
to match to bring up the ONT.
396 65K110FTTP-29A
Revision A
♦ When replacing the ONT in the field, re-entering the same Registration ID used
by the previous ONT is all that needs to be done.
13.6.2 Cons
■ Provides a potential insecure activation method when using the activation registration
unlock-serial-number command.
f CAUTION!
Do not duplicate the same Registration-ID to two different ONTs to be activated on the
OLT.
As an example, ONT A has S/N S1 and Registration-ID R1 and is UP another ONT B has
S/N S2 and Registration-ID R2.
ONT B becomes faulty and needs replacement. When the technician removes ONT B and
adds a new ONT in place of B with a Registration-ID R1, ONT B would not come UP and
cause a duplicate Registration-ID error at the OLT. If the technician did not resolve the
duplicate Registration-ID and leave the ONT connected, ONT A would still be UP and
running. After an OLT reboot, there is a chance that the ONT replaced at B would get the
service of ONT A.
■ Can potentially create an ONT replacement problem. The new or replacement ONT
can remove the service of another ONT already operating in the field.
■ Allows the service of another ONT to accidentally be taken by the newly installed ONT
if the Registration-ID is duplicated by the technician during installation of the new,
replacement ONT.
What’s Next
■ For CLI Registration-ID activation, continue to Section 2.3.1.2, “Provision the PON” on
page 50.
■ For Web Registration-ID activation, continue to Section 2.3.1.2, “Provision the PON”
on page 50.
65K110FTTP-29A 397
Revision A
398 65K110FTTP-29A
Revision A
ONT Capability Provisioning - Scope of this Section
14 ONT Capability Provisioning
The ONT Capability Provisioning feature provides a method to configure the OLT for the
expected functionality of an ONT. The main purpose of this feature is to ease integration of
new ONTs into the system.
There are two tables associated with this new feature. The first table (refer to Figure 14-1 on
page 401) is used for referencing an ONT by its part number. The second table (refer to Figure
14-3 on page 403) is used for referencing an ONT by its four-character vendor name. Each
table has fixed entries that cannot be removed, although they can be modified for test
purposes. These tables govern the behavior of all ONTs on all PONs on a shelf. Any change
to a table entry for a specific ONT part number or vendor name, will affect every ONT
with that part number or vendor name connected to any PON on the Total Access 5000
shelf. Because of this, it is not recommended that an existing fixed ONT capability be changed
except in a lab environment. These fixed entries are marked by a “*” in column 1 under the Def
(Default) heading. If one of these fixed entries is inadvertently modified from those values set
by ADTRAN when the product was shipped, it will be noted by a second “*” in column 3. A “no”
command can be used on a fixed entry to return it to its default values. Refer to Section 14.7,
“Restoring a Fixed Part Number Entry to Default Value” on page 405 for this procedure.
When a new ONT (one not already in either table) is going to be introduced into the system,
ADTRAN recommends adding a single ONT of the new type to the system, and getting its
capability settings correct before adding remaining ONTs of this type into the system. This will
ensure the table settings take effect for all ONTs of this type.
For a list of terms associated with Capability Provisioning, refer to Section 14.9, “ONT
Capability Provisioning Terms” on page 408.
f CAUTION!
This feature should be used with extreme care. It creates shelf-wide provisioning that could be
service-affecting if used incorrectly. Changes to these provisioning items are not guaranteed
to take place until the next ONT activation.
65K110FTTP-29A 399
Revision A
ONT Capability Provisioning - In this Section

14.3 Adding a New ONT Part Number 401
14.4 Removing an ONT Part Number 402
14.5 Adding a Vendor Name 403
14.6 Removing a Vendor Name 404
14.7 Restoring a Fixed Part Number Entry to Default Value 405
14.8 Restoring Vendor Entry to Default Value 406
14.9 ONT Capability Provisioning Terms 408
400 65K110FTTP-29A
Revision A
ONT Capability Provisioning - Adding a New ONT Part Number
14.3 Adding a New ONT Part Number

In the following example, part number 123xxxx is being added to the part number table.
g NOTE
Each table (part number table and vendor name table) can have new entries added to
them to help facilitate the setup of new ONTs. These new entries can be removed from the
table if not needed. These entries will not have “*” in any column under the Def heading.
To add a new ONT part number to a PON, complete the following.

TA5000#configure terminal
TA5000(config)#ont-capability part-number 123xxxx
ONT Capability Part number "123xxxx" created
TA5000(config-ont-cap-part-num 123xxxx)ont-type
adtran300 -Adtran 2nd Generation 300 series
adtran400 -Adtran 4th Generation 400 series
adtran600 -Adtran XGSPON 600 series
adtranmdu -Adtran MDU 8P-8VDSL2
generic -Set ONT Type to generic
g NOTE
Set any non-ADTRAN ONT to “generic”.
ONT Capability Part number "123xxxx" created

TA5000(config-ont-cap-part-num 123xxxx)#do show ont-capability
The following table is displayed:
123xxxx
Figure 14-1. Adding a New ONT Part Number
65K110FTTP-29A 401
Revision A
ONT Capability Provisioning - Removing an ONT Part Number
14.4 Removing an ONT Part Number

In the following example, part number 123XXXX is being removed.
g NOTE
The “no” command can be used on a new entry to remove it from the table.
To remove an ONT part number, complete the following:

TA5000(config)#no ont-capability part-number 123xxxx
TA5000(config)#do show ont-capability
Figure 14-2. Removing an ONT Part Number
402 65K110FTTP-29A
Revision A
ONT Capability Provisioning - Adding a Vendor Name
14.5 Adding a Vendor Name

In the following example, vendor name ABCD is being added.
To add a new vendor name, complete the following:
TA5000 (config)#ont-capability vendor-name ABCD
ONT Capability Vendor "ABCD" created
TA000(config-ont-cap-vendor ABCD)#do show ont-capability
ABCD
Figure 14-3. Adding a Vendor Name
65K110FTTP-29A 403
Revision A
ONT Capability Provisioning - Removing a Vendor Name
14.6 Removing a Vendor Name

In the following example, vendor name ABCD is being removed.
To remove a vendor name, complete the following:
TA5000 (config)#no ont-capability vendor-name ABCD
Figure 14-4. Removing Vendor Name
404 65K110FTTP-29A
Revision A
ONT Capability Provisioning - Restoring a Fixed Part Number Entry to Default Value
14.7 Restoring a Fixed Part Number Entry to Default Value

In the following example, part number 1179870F2 is being restored to its default value.
Note that the value for part number 1179870F2 under the Rll Cnt heading is “F”. The default
value should be “T”. The variation is denoted by “*”. Note the change in Figure 14-6.
To restore a fixed entry to it’s default value, complete the following:
TA5000(config)#no ont-capability part-number 1179870F2
* F
Figure 14-5. Entry Before being Restored to Default Value
Figure 14-6. Restored Entry to Default Value
65K110FTTP-29A 405
Revision A
ONT Capability Provisioning - Restoring Vendor Entry to Default Value
14.8 Restoring Vendor Entry to Default Value

In the following example, vendor IPHO is being restored to its default value.
To restore an entry to its default value, complete the following:
Note the variation is denoted by “*”.
* 6
Figure 14-7. Restoring Vendor Entry to Default Value
As the table indicates, the IPHO entry has been modified.

Restoring the vendor IPHO to its default values is on the next page.
To restore a fixed entry to it’s default value, complete the following:
TA5000(config)#no ont-capability vendor-name IPHO
Note that the IPHO entry has returned to its Default Value.
406 65K110FTTP-29A
Revision A
ONT Capability Provisioning - Restoring Vendor Entry to Default Value
IPHO
IPHO
IPH O 32
Figure 14-8. Restored Entry to Default Value
65K110FTTP-29A 407
Revision A
ONT Capability Provisioning - ONT Capability Provisioning Terms
14.9 ONT Capability Provisioning Terms

The following terms are used when implementing Capability Provisioning.
■ dbru-status - Dynamic bandwidth reports upstream status support (default value =
false). This defines whether the ONT supports explicit status reporting of its buffer
status for dynamic bandwidth allocation as defined in ITU-T G.998.
■ extended-64bit-pm - Ethernet frame extended PM 64 bit support (default value =
false). This defines whether the ONT supports ethernet frame extended PM 64 bit as
defined in ITU-T G.998.
■ extended-pm - Ethernet Frame Extended PM support (default value = false). This
defines whether the ONT supports ethernet frame extended PM as defined in ITU-T
G.998.
■ mgmt-me-id - IP host management ME id (default value = 515). This defines the
instance ID of the managed entity used for IP host management at the ONT.
■ nsr-grant-size - Non-status reporting grant size in bytes/frame (default value = 32).
This defines the number of bytes per frame granted for idle slot detection on non-
status reporting ONTs on the PON. This number includes 5 bytes for the GEM header.
This is a per PON implementation, so the grant size used by the PON will be that of
the ONT with the highest required nsr-grant-size.
■ ont-type - Ont type/generation (default value = generic). This item indicates the type
or generation of the ONT. There are types listed for ADTRAN ONTs, as well as a
generic selection for non-ADTRAN ONTs.
■ product-name - ONT product name (default value = “”). This is the name (45
characters maximum) that will be displayed when the show ont-capability, the
show remote-devices <remote-index>, and show running-config ont-
capability commands are selected. If the product name is longer than 21
characters, it will be truncated in the table displayed by the show ont-capability
command, but it should display in its entirety in the show remote-devices <remote-
index> and the show running-config ont-capability commands.
■ rolling-counter - Rolling counter PM support (default value = false). This item defines
whether the ONT supports continuous accumulation PM as defined in ITU-T G.998.
■ rtp - Real-time transport protocol PM support (default value = false). This item defines
whether the ONT supports RTP PM history data as defined in ITU-T G.998.
■ t1-prov - T1 provisioning over OMCI support (default value = false). This item defines
whether the ONT supports T1 provisioning over OMCI as defined in ITU-T G.998.
408 65K110FTTP-29A
Revision A
Warranty and Contact Information
15 Warranty and Contact Information
15.1 Warranty
Warranty information can be found at:
www.adtran.com/warranty.
15.2 Contact Information

For all customer support inquiries, please contact ADTRAN Customer Care:
Contact Support Contact Information
Customer Care From within the U.S. 1.888.4ADTRAN (1.888.423.8726)

From outside the U.S. + 1.256.963.8716
Technical Support:
■ Web: www.adtran.com/support
Training:
■ Email: training@adtran.com
www.adtran.com/training
■ Web:
www.adtranuniversity.com
Sales Pricing and Availability 1.800.827.0807
65K110FTTP-29A 409
Revision A
Warranty and Contact Information
410 65K110FTTP-29A
Revision A
Acronyms
ADTRAN Advanced Transmissions

ARP Address Resolution Protocol
CLEI Common Language Equipment Identification
CLI Command Line Interface
CRC Cyclic Redundancy Checks
C-VLAN Customer VLAN
DBRu Dynamic Bandwidth Report upstream
DCE Data Communications Equipment
DHCP Dynamic Host Configuration Protocol
DLC Digital Loop Carrier
DSCP Differentiated Services Code Point
DSL Digital Subscriber Line
DSLAM Digital Subscriber Line Access Multiplexer
EVC Ethernet Virtual Connection
FTTP Fiber to the Premises
FXS Foreign Exchange Service
GEM GPON Encapsulated Method
GFP Generic Framing Procedure
GPON Gigabit Passive Optical Network
GR-303 Generic Requirement 303
IETF Internet Engineering Taskforce
IP Internet Protocol
LED Light Emitting Diode
MDU Multi-unit Dwellings Unit
MGCP Media Gateway Control Protocol
NAS Network Access Server
ODN Optical Distribution Network
OLT Optical Line Terminal
ONT Optical Network Terminal
PIR Peak Information Rate
PON Passive Optical Network
POTS Plain Old Telephone Service
PPP Point to Point Protocol
PPPoE Point to Point Protocol over Ethernet
PSTN Public Switched Telephone Network
RSSI Received Signal Strength Indicator
65K110FTTP--29A 411
Revision A
RTP Real-Time Transport Protocol
RTCP Realtime Control Protocol
SFP Small Form-factor Pluggable
SIP Session Initiation Protocol
S-Tag Service Tag
TDM Time-division Multiplexing
TLS Transport Layer Security
UNI User to Network Interface
VLAN Virtual Local Area Network
VoIP Voice over Internet Protocol
412 65K110FTTP--29A
Revision A

65K110FTTP 29a PDF

Uploaded by

Copyright:

Available Formats

65K110FTTP 29a PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

65K110FTTP 29a PDF

Uploaded by

Copyright:

Available Formats

Total Access 5000 Series

Basic Configuration Guide

To the Holder of this Document

f Important Notice on Product Safety

Copyright © 2020 ADTRAN, Inc.

Rev A January 2020 Initial release.

Fiber to the Premises Overview . . . . . . . . . . . . . . . . . . . . . . . .27

1.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1.3 GPON Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1.4 Fiber to the Premises with Active Ethernet Overview . . . . . . . . . . . . . . . . . . . . 33

1.5 Voice Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

1.6 Command Line Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

1.7 User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

GPON Provisioning using CLI. . . . . . . . . . . . . . . . . . . . . . . . . .49

2.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

2.3.10 Provision Non-OMCI MGCP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Provisioning using the Web GUI. . . . . . . . . . . . . . . . . . . . . . . 115

3.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

3.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

3.3.2.1.9 GR-303 Voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Provisioning Active Ethernet using CLI . . . . . . . . . . . . . . . . .179

4.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

4.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

4.4 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

4.4.1.2 Discover the ONT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Provisioning Active Ethernet using the Web. . . . . . . . . . . . .235

5.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

5.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

GPON Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285

6.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

6.3 VLAN/TLS/IPTV Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

6.4 TLS Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Active Ethernet Configurations. . . . . . . . . . . . . . . . . . . . . . . . 309

7.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

7.3 1:1 Customer VLAN (C-VLAN) Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

7.4 N:1 Service VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

7.5 Hybrid N+1:1 Combined VLAN Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

7.6 TLS Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

8.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

8.3 Shapers, GPON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

8.3.1 Downstream Shaping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

8.4 Provisioning using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

8.5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

8.6 Shapers, AE (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

8.7 Policers, AE (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

8.7.2 Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

SFP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361

9.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

9.3 Information Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

3rd Party ONT Provisioning for Active Ethernet . . . . . . . . . .363

10.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

10.3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Home Phoneline Networking Alliance . . . . . . . . . . . . . . . . . . 367

11.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

11.3 Introduction to HPNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

11.4 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

IEEE 802.1X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

12.2 In this Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371