Documente Academic
Documente Profesional
Documente Cultură
Installation and
Configuration Guide
Release 5.5
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT
NOTICE, ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED
WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION
OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION
PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO
LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR OCCAM REPRESENTATIVE FOR A COPY.
MANDATORY REGULATIONS AND SAFETY WARNINGS ARE PROVIDED IN APPENDIX A. IT IS THE RESPONSIBILITY OF THE USER
TO READ THIS APPENDIX PRIOR TO INSTALLATION OF THIS PRODUCT.
The following third-party software may be included with your product and will be subject to the software license agreement:
Network Time Protocol (NTP). Copyright © 1992, David L. Mills. The University of Delaware makes no representations about
the suitability of this software for any purpose.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE
PROVIDED “AS IS” WITH ALL FAULTS. OCCAM NETWORKS AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES,
EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL OCCAM NETWORKS OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR
INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF
THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF OCCAM NETWORKS OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
Occam Networks, Inc. products are not designed or authorized for use as a component in any life support, life safety, or
other comparable application. Our products should not be used in any application where the failure or faulty performances
of the product might result in a risk of personal injury or death. Buyer assumes all risk of loss, damage or injury alleged to
arise from the failure or faulty performance of a faulty performance of an Occam Networks product in any unauthorized
application. Buyer agrees to indemnify and hold harmless Occam Networks Inc., and its officers, directors, employees, agents,
representatives, and sales partners, from any and all claims, costs, damages, losses, and expenses (including reasonable
attorney fees) which arise from or are alleged to have been caused by any claim for personal injury or death connected with
Buyer’s use of an Occam Networks product in any unauthorized application, including claims which allege that Occam
Networks has been negligent in connection with the design or manufacture of the product.
ON 2230,BLC 6001, BLC 6012, BLC 6150-01, BLC 6151-01, BLC 6152-01, BLC 6212-02, BLC 6214, BLC 6244, BLC 6246, BLC
6252, BLC 6252-02, 6252-03, BLC 6312, BLC 6314, BLC 6440-01, BLC 6450, BLC 6640-01, and BLC 6660 are registered
trademarks of Occam Networks, Inc. in the U.S. and certain other countries. All other trademarks mentioned in this document
are the property of their respective owners.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page iii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page iv of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
Table of Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Document Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxi
Who Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxi
Approvals and Rating Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxi
Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxi
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page v of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page vi of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Rear Panel of BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Connectors for Subscriber Interfaces and T1 Ports . . . . . . . . . . . . . . . . . . . . . 79
Ethernet Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Alarm/Auxiliary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Shelf Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Cabinet Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Network Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Preventing Electrostatic Discharge (ESD) Damage . . . . . . . . . . . . . . . . . . . . . . 83
Unpacking the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Rack Mounting the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Inserting Blades Into the BLC 6012i Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Attaching an ADSL Bridge Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
ADSL Bridge Clip Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Attaching the ADSL Bridge Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Connecting the Subscriber and T1 Interface Cable . . . . . . . . . . . . . . . . . . . . . . . . 98
T1 Pinout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Subscriber Pinout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Connecting the 10/100/1000 Base-TX Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . 104
Connecting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Inserting the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Inserting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuring the Shelf ID Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Using the show version Command To Verify the Slot/Shelf ID . . . . . . . . . . . 108
BLC 6012i Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page vii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page viii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page ix of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page x of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
VPT 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Interface A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Interface C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
VPT 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Interface B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Interface L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
VPS 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Interfaces D and E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
VPS 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Interfaces F and G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Interface (Multilink Group) M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
VPS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Interfaces H and I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Interface (Multilink Group) T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
VPS 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Interfaces J and K. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
VPS 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Interface (Multilink Group) N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Interface O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
VPS 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Interfaces P and Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
VPS 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Interface R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Interface (Multilink Group) S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xi of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
XG Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298
Configuring Multicast Rate Limiting on an Ingress Ethernet Interface . . . .299
Configuring Unknown Unicast Rate Limiting on Ingress Ethernet and
XG Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299
Verifying Your Rate Limiting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xiii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xiv of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xv of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xvi of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Configuring a T1 Interface for Cross-Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Configuring Cross-Connect Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Default Cross-Connect Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Configuring a Cross-Connect Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Commands to Configure Cross-Connect Profiles . . . . . . . . . . . . . . . . . . . . . . 554
Attaching a Profile to a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Displaying Voice Port and Profile Information. . . . . . . . . . . . . . . . . . . . . . . . . . . 560
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xvii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
Channel 31 Configuring TR-08 for TDM Voice on the BLC 6246 and
BLC 6150-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .647
Port Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .647
POTS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .648
TR-08 for TDM Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .649
Channel Associated Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .649
Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .651
Configuring a T1 Interface for TR-08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .652
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xviii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xix of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xx of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxi of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxiii of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Table of Contents
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxiv of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Preface
Document Objectives
0 Preface
In This Chapter:
Document Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Who Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Approvals and Rating Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvi
Document Objectives
This guide describes how to install and configure Release 5.5 of the BLC 6000
System.
Customer Support
Business hours:
5 a.m. to 5 p.m. PST Monday through Friday
+1-805-692-2911 or 1-888-525-2435
support@occamnetworks.com.
For urgent matters after regular business hours and on weekends, please call
+1-805-692-2911 AND send an e-mail to “support@occamnetworks.com”. A
support engineer will return your call.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxv of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Preface
Conventions
Conventions
The following conventions are used in this manual:
Conventions Description
courier new This typeface is used for information that
appears on the screen.
courier new bold This typeface is used for information that
you must enter.
rotis bold This typeface is used for commands and
command variables that are entered
literally.
{variable} A command variable enclosed in braces
indicates that the variable is mandatory.
[variable] A command variable enclosed in square
brackets indicates that the variable is
optional.
{variable1 | variable2 | Command variables contained in braces
variable3} and separated by a vertical bar represent
a group of items where it is mandatory
that at least one must be selected.
[variable1 | variable2 | Command variables contained in square
variable3] brackets and separated by a vertical bar
represent a group of items where one
may optionally be chosen.
Note: Text This note symbol alerts you to
supplementary information.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxvi of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
Overview
Chapter 1
0 BLC 6000 System Overview
In This Chapter:
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
BLC 6000 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
System 6000 BLCs and Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
BLC 6000 Optical Transceivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Overview
The BLC 6000 system includes plug-in blades, high capacity and stackable chassis,
cabinets and an Element Management System. It supports standard lifeline POTS
telephones, DSL modems and GigE ONUs.
The BLC 6000 connects POTS and VoIP to a traditional Class 5 via TR-08 or GR-303.
In addition, it can support IP IADs, terminal adapters or IP phones as well as connect
POTS into next-generation IP softswitches.
The BLC 6000 incorporates a distributed architecture that enables system blades to
operate in a 12-slot high capacity chassis or in stackable 1RU chassis.
Note: When a blade is combined with a BLC 6001 chassis, the assembly is denoted
by the letters “BLC” prefix. For example, a 6246 blade is referred to as a
BLC 6246 when inserted into a BLC 6001 chassis.
The following tables show an overview of the BLC 6000 system blades and chassis.
The blades and chassis are also described in more detail later in this chapter.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 1 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
Overview
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 2 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
BLC 6000 Chassis
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 3 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
BLC 6000 Chassis
PN: 710033-R
BLC 6012 High Twelve blade capacity.
Capacity CO Chassis Vertical chassis with replaceable fan assembly
wired for POTS appli-
and air filter.
cations using 6151
blades Fiber protection cover.
Requires 12 Rack Units in 23-inch rack, 11 ½
PN: 710053-P inches deep
Includes POTS backplane wiring and Fiber
Management Front cover.
The fan tray has a filter because this chassis is
intended for use in Central Office space or
vaults.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 4 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
BLC 6000 Chassis
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 5 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
System 6000 BLCs and Blades
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 6 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
System 6000 BLCs and Blades
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 7 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
System 6000 BLCs and Blades
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 8 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
BLC 6000 Optical Transceivers
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 9 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
BLC 6000 Optical Transceivers
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 10 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
BLC 6000 Optical Transceivers
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 11 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 1: BLC 6000 System Overview
BLC 6000 Optical Transceivers
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 12 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Introduction
Chapter 2
Installing a BLC 6001 Chassis
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
BLC 6001 Chassis Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Rack Mounting the BLC 6001 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Preventing Electrostatic Discharge (ESD) Damage . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Inserting a Blade Into the BLC 6001 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Connecting the Subscriber and T1 Interface Cable. . . . . . . . . . . . . . . . . . . . . . . . . . 26
Connecting an ADSL Bridge Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Connecting the Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Connecting the 10 GigE Copper Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Connecting the 10/100/1000 Base-TX Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring the Slot/Shelf ID Selector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
BLC 6001 Chassis Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Introduction
This chapter describes how to connect the BLC 6001 chassis. Be sure to read the
safety warnings located in Appendix A, Safety Warnings on page 825.
The BLC 6001 Stackable Chassis holds a single 6000 series blade which can then be
deployed as a standalone, self-contained unit. The blades plug into the front,
allowing fast and easy field replacement without disconnecting the back wiring.
Port capacity is determined by the blade used; it is usually 24 or 48 ports, however
the chassis itself is designed to accommodate up to 96 lines.
The units are stackable with any combination of blades to allow low and medium
density deployments to meet exact site configuration needs. The BLC 6001 chassis
(including the replaceable fan assembly) is one Rack Unit high. It requires a 1.75
inch space in a 19- or 23-inch rack, 11 ½ inches deep.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 13 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
BLC 6001 Chassis Rear Panel
GROUND
SHELF SELECT
ALARM/AUX
Ethernet Interfaces
There are six RJ45 connectors for 10/100/1000-TX Ethernet Interfaces.
Power
There are -48 VDC Power A and B inputs on a terminal strip.
Grounding Lug
The grounding lug attaches a ground cable in the range of 8 to 10 AWG.
Shelf/Slot ID Selector
The Shelf/Slot ID selector is on four rotary switches on rear panel.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 14 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Preparing for Installation
Caution: Static voltages as low as 30 volts can damage circuitry. Make sure to
! observe all standard anti-static procedures when handling electronic equipment
and components.
2 Remove the “Open Me First” envelope. This envelope should contain the
following items:
CD ROM containing PDFs of Occam Networks Installation Guides and
Warranty card
shipping list
release notes
5 Examine the chassis and cables for signs of damage or other mishandling.
6 Check the packing list to verify receipt of all components. Contact Occam
Networks immediately to report any discrepancies.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 15 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Site Preparation
Site Preparation
Proper installation is necessary to prevent injury to yourself and damage to the
BLC. Evaluate your site using the following guidelines prior to installation.
Cabinet Preparation
Make sure that the location is accessible and that you are able to complete the
installation. The BLC requires a vertical mounting space of one EIA rack unit (1.75
inches). It is 12 inches deep, and requires approximately 3 inches of additional
depth to allow sufficient bend radius for cables.
Airflow Requirements
It is important to consider the following information when you plan an acceptable
cabinet rack configuration:
An enclosed cabinet must have adequate ventilation. Ensure that it is not overly
congested because each unit generates heat. Enclosed cabinets should have
adequate thermal management to provide an environment of -40C to +65C
(-40F to +149F).
When mounting the BLC in an open rack, ensure that the rack frame does not
block the right intake or the left exhaust ports.
In an enclosed rack with a ventilation fan in the top, excessive heat generated by
equipment near the bottom of the rack can be drawn upward and into the intake
ports of the equipment above it in the rack. Ensure that you provide adequate
ventilation for equipment at the bottom of the rack
Baffles can help to isolate exhaust air from intake air, which also helps to draw
cooling air through the chassis. The best placement of the baffles depends on the
airflow patterns in the rack, which can be found by experimenting with different
arrangements.
Power
Make sure that you have access to the power system and that the system supports
the power requirements for the BLC:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 16 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Site Preparation
Cables
Make sure that each cable is adequate for installation at your site:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 17 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Rack Mounting the BLC 6001 Chassis
Eight pan-pilot screws, slot 12-24 x.625. These are used to attach the rack
mount bracket to user-supplied rack
Three cable ties 5.5 L x.13 W. These ties are not used when installing the BLC.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 18 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Preventing Electrostatic Discharge (ESD) Damage
Figure 2-4: 23 Inch Rack Mount Adapter Attached to BLC Mounting Brackets
12-24 X .625
PAN-PILOT
SCREWS
23 INCH RACK
MOUNT
ADAPTOR
3 Align the holes in the brackets with the mounting holes in the equipment rack.
4 Insert two 12-24 x.625 pan-pilot screws through the holes in the brackets and
into the threaded holes in the mounting post and tighten them snugly.
Always wear an ESD-preventive wrist strap when handling the BLC chassis and
blades, ensuring that the strap makes ample contact with your skin. Clip the
wrist strap on to the grounding lug.
Note: Periodically check to make sure that the resistance value of the antistatic
wrist strap is between 1 and 10 megohms.
Remember that the wrist strap only protects the BLC from ESD voltages present
on the body. ESD voltages can also be present on clothing and can cause ESD
damage to the BLC.
Ground yourself by touching the metal part of the chassis if you do not have a
wrist strap available.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 19 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Inserting a Blade Into the BLC 6001 Chassis
2 Press the compact flash (CF) card down slightly along the outside edge of the
card to ensure there is a proper connection. The CF card may be on the top or
bottom of the blade, despending upon the model number.
3 Carefully align the blade with the grooves in the BLC 6001 chassis.
4 As you slide the blade into the chassis make sure the levers are in the open posi-
tion. When levers are open the interior edges that face the blade are in the up
position and the exterior edges of the blade are in the down position.
5 Carefully push the blade in the appropriate slot toward the rear of chassis. Make
sure blade is loose as it is being slid in and is not crooked.
Caution: Never force the blade into position. If in doubt of the blade’s correct
! alignment, remove, inspect and reinsert the blade.
6 When the blade is pushed back as far as possible in the chassis, close the levers
on each side. The blade usually will stop at the edge of the connectors inside the
chassis. Close the levers to enable the blade to proceed onto connectors, making
sure that the levers catch the side of the chassis. At this point the blade will still
not be tightly seated in the chassis.
Caution: The levers cannot usually get blade seated all the way in. If closing the
! levers causes them to jam do not force them to close. The levers may still be in
an slightly “open” position when they have gone in as far as they can.
The levers on a blade are primarily designed to eject a blade after it has been
inserted. Their role on insertion is to get blade close enough to the chassis so that
the jacking screws can be inserted and tightened down. Attempting to fully seat
the blades by pressing hard on levers can and does break them off.
7 Tighten the jack screws on top and bottom of blade completely insert the blade
in the chassis. Tighten each screw equally top and bottom evenly.
Caution: It is mandatory to use the jack screws to lock the blade in the chassis
! to prevent vibration from shaking the blade loose. Screwing the blade tightly in
the chassis also maintains grounding and EMI seals to meet the FCC approvals.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 20 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Ground Wire
The grounding lug is on the rear panel of the BLC 6001 chassis, as shown in Figure
2-5.
2 Connect a suitable ground wire (8 AWG minimum) to the ground lug. For best
grounding, use the smallest gauge AWG wire (thickest wire) possible. Connect
the ground cable using an appropriate double hole lug.
4 According to local practice, connect other end of ground cable to closest equip-
ment rack common ground bus structure with a screw, washer and lock washer
to ensure a reliable ground connection.
5 Dress the ground cable run with cable ties or clamps, and verify tight connection
on screws, nuts and connectors.
6 Verify the ground by placing the black test lead (-) of a voltmeter to the frame
ground and confirm 0 (zero) OHMs from the chassis ground to the equipment
rack ground bus.
Warning: Do not allow the test probes of the voltmeter to touch each other
while they are touching the power terminals.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 21 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Power
1 For single power feed locate the 48VDC RETURN A power studs. For dual power
feed locate the 48VDC RETURN A and 48VDC RETURN B power studs.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 22 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Power
3 Connect suitable power cable (18 AWG recommended) to the power 48VDC
RETURN A studs using an appropriate double hole lug.
5 Connect other end of 48VDC RETURN A power cable to closest LIVE Return
power feed within the rack enclosure. If installing single power feed only skip to
step 10.
6 For dual-power-feed locate the 48VDC RETURN B (Return for B) power studs.
7 Connect a separate suitable power cable (18 AWG recommended) to the power
48VDC RETURN B studs using an appropriate double hole lug.
9 Connect other end of 48VDC RETURN B power cable to closest redundant LIVE
48VDC Return power feed within the rack enclosure, separate from feed to
48VDC RETURN A.
10 Dress 48VDC RETURN A (and 48VDC RETURN B) cable run with cable ties or
clamps, verify tight connection on screws, nuts and connectors.
11 Use a voltmeter to confirm correct voltage level and polarity for –48VDC across
power stud set A (and –48VDC across power stud set B for dual-power- feed).
Place the black test lead (-) of the voltmeter to the Return A or B (using either
one will test both). Place the red test lead (+) on the A-side connection and
verify that it is between -42 VDC and -57 VDC. Place the red test lead on the B-
side connection and verify that it is between -42 VDC and -57 VDC.
Warning: Do not allow the test probes of the voltmeter to touch each other
while they are touching the power terminals.
Warning: Make sure that the polarity of the DC connections is correct. If the
voltmeter displays a positive polarity, wires have been crossed. Reversed polarity
causes damage to the BLC and the DC power supply and creates a dangerous
shock hazard. If the power is reverse connected at this point, re-do this detailed
procedure correctly starting at step 1.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 23 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Alarm/Auxiliary Cable
1 2 3 4 5 6 7 8
2 Hold the connector with the eight small shiny flat-head screws facing you and
have the set of eight individual plastic plugs facing to the right. Held this way,
the Molex connector pins are numbered 1 (top) through 8 (bottom):
Alarm/Auxiliary Pinout
Connection No.
1 Alarm Out Normally Open
2 Alarm Out Common
3 Alarm Out Normally Closed
4 Unused
5 Alarm In
6 Auxiliary Console TX
7 Auxiliary Console GND
8 Auxiliary Console RX
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 24 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Alarm/Auxiliary Cable
3 Turn those small captive screws gently counterclockwise until each internal
“slider”, visible on the left side, bottoms lightly in the wire slot.
4 Connect the small gauge wires from the alarm distribution panel (in or near the
equipment rack) for each alarm function required.
5 For each wire from the alarm distribution panel, locate the matching Molex
connector wire slot, and insert the small gauge wire with 1/4 inch stripped into
the open internal slider slot. Gently tighten the flat-head screw in the clockwise
direction, thus moving the internal slider up (toward the screw head) to securely
pinch and capture the wire.
6 Continue steps 2-5 until all required alarm wires are connected.
7 Insert the Molex connector in the BLC chassis. It will only fit in one direction.
8 Dress alarm wire runs with cable ties or clamps. Verify tight connection on
screws, nuts and connectors.
Note: The alarm-out will always register an active alarm state if the alarm-in is not
attached to an alarm system. To prevent this, use the environment alarm in
command to disable the alarm. Information about this command may be found in
section Environment Alarm In and Out Commands in Chapter 36, Alarms and Sensors
on page 692.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 25 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Subscriber and T1 Interface Cable
J4 J3
J2 J1
Blade J1 J2 J3 J4
Model
6150-01 X T1 (1-4) POTS POTS service
service for for lines 25-48
lines 1-24
6151-01 X X POTS POTS service
service for for lines 25-48
lines 1-24
6212-02 ADSL2+ ADSL2+ X X
service for service for
lines 1-24 lines 25-48
6214 Combined Combined External External POTS
POTS / POTS / POTS signals signals on lines
ADSL2+ ADSL2+ on lines 1- 25-48
signals on signals on 24
lines 1-24 lines 25-48
6246 Combined Four X X
POTS / powered T1
ADSL2+ ports
signals on
lines 1-24
6252-03 X X Combined Combined
POTS / POTS / ADSL2+
ADSL2+ signals on lines
signals on 25-48
lines 1-24
6440-01 X T1 (1-8) X X
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 26 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Subscriber and T1 Interface Cable
Blade J1 J2 J3 J4
Model
6640-01 X T1 (1-8) X X
6660-01/ X T1 (1-8) X X
6660-02/
6660-03
Instructions
1 Attach the champ connector snugly to the rear of the chassis.
Warning: Each shielded connector on the rear of the BLC 6001 and BLC 6012
chassis is grounded to the chassis via the jack/hex connector screws. Do NOT
remove the jack/hex connector screws.
Caution: The champ connector must SECURELY seat on the “J” connector or
bridge clip before the screw becomes tight in the standoff. If the screw becomes
! tight in the standoff before the champ connector is securely seated you may
need to insert one or more washers. Please contact Occam Networks if washers
are required
SCREW
A
1/16 inch {
B
3 Use the supplied tie wrap (from the rack mount kit) to attach other side of the
champ connector as shown in Figure 2-11. Make sure to secure the wire wrap
snugly.
Note: Make sure that the tie wrap remains snug and does not stretch out if the
cables are moved.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 27 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Subscriber and T1 Interface Cable
Figure 2-11: Champ Connector on BLC 6640-01 Chassis with Cable Attached
25
1 1
25
26
50 50
26
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 28 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Subscriber and T1 Interface Cable
T1 Pinout Definitions
Table 2-4: T1 Interface Pinout Definition
This pinout definition conforms to industry standard RJ-48X pinout
RX = Receive from the network (into the BLC)
TX = Transmit to the network (out of the BLC)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 29 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Subscriber and T1 Interface Cable
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 30 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting an ADSL Bridge Clip
The BLC 6212 can share lines with the BLC 6150 or 6151 when located in adjacent
chassis slots in a BLC 6012 Chassis or when two BLC 6001 Chassis are mounted
adjacent to each other through the use of an ADSL bridge clip.
Use of an ADSL bridge clip eliminates the need for external splitters when operating
with a BLC 6150 or 6151. However, if these BLCs are used with other POTS lines, an
external splitter is still required.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 31 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting an ADSL Bridge Clip
2- Standoffs, 0.25L,
.06" THICK
SHORT STANDOFFS
W ASHERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 32 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting an ADSL Bridge Clip
2 Remove the plastic covers from the side of the bridge clip that has two connec-
tors as shown in Figure 2-17. This side of the bridge clip is attached to the BLC.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 33 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting an ADSL Bridge Clip
3 Use as many washers as required and four short screws from the kit to securely
fasten each corner of the DSL Bridge to the “J” connector as shown in
Figure 2-17.
Caution: The DSL Bridge must SECURELY seat on the “J” connector before the
screw becomes tight in the standoff. If the screw becomes tight in the standoff
! before the DSL Bridge is securely seated you may need to use more than one
washer. The DSL Bridge Kit supplies washers in two thicknesses. If more washers
are required please contact Occam Networks.
4 Attach the J Connectors to the ADSL Bridge Clip as shown in Figure 2-13. Use
the directions in the section <Blue><Italic>Connecting the Subscriber and T1
Interface Cable on page 26, attaching the subscriber and T1 interface table to
the ADSL bridge clip instead of directly to the J connectors.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 34 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the Fiber Optic Cables
2 Gently insert the module into a SFP slot on the chassis front panel. Push it into
a slot until you feel the spring catch.
Caution: To prevent contamination do not remove the dust plug from the
! Optical Laser Module until you are ready to connect the fiber cable.
3 Insert the end of the fiber cable into the module and confirm that both the SFP
module and fiber optic cable are properly seated in the port.
4 Route the fiber cable through the cable guide at the top of the BLC 6012 chassis.
Caution: To avoid damage to your fiber-optic cables do not bend the cables to
! a radius smaller than 1.5 inches (38 mm). Bending the cable farther than its
minimum bend radius may result in increased attenuation or broken fibers.
Note: Keep the SFP transceivers and fiber optic cables clean and dust-free to
prevent damage and maintain high signal accuracy.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 35 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the 10 GigE Copper Interfaces
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 36 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Connecting the 10/100/1000 Base-TX Ethernet
4 6 1 2
3 5
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 37 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Configuring the Slot/Shelf ID Selector
Note: Due to a management issue with OccamView, the CLI and the EMS, Occam
Networks recommends that you do not set the slot ID to 13,14 or 15 on a BLC 6001
chassis.
Note: The BLC must be rebooted for the shelf and slot ID to take effect.
The shelf and slot ID may be confirmed by running the show version command.
Please see page 41 for an example of this command and where to find the slot/shelf
ID in the output.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 38 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Configuring the Slot/Shelf ID Selector
Each BLC in your network must be configured with a unique slot/shelf ID value.
Note: In order to support the Ethernet cut-through feature on their copper ports.
Occam Networks recommends that you do not configure more than four BLCs in
each stack.
The first option is to number each BLC 6001 chassis in the stack with a unique shelf
ID/slot ID value combination.
For example, a BLC chassis could be numbered as slot ID A, with a chassis ID of 126.
The dials would be set as follows:
Dial 1 = A
Dial 2 = 6
Dial 3 = 2
Dial 4 = 1
F 01 F 01
BC D E
BC D E
23
23
45
45
DIAL 4 DIAL 3
67 67
89A 89A
F 01 F 01
BC D E
BC D E
23
23
DIAL 2 DIAL 1
45
45
67 67
89A 89A
The second option is to number each BLC 6001 chassis in the stack with a common
shelf ID value to identify the “stack”. The individual units should use different slot
ID values. Typically the value of “slot 1” is assigned to the top chassis in this stack.
For example, the top BLC 6001 chassis in the stack could be numbered as slot #1,
with a chassis ID of 001. The dials would be set as follows:
Dial 1 = 1
Dial 2 = 1
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 39 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Configuring the Slot/Shelf ID Selector
Dial 3 = 0
Dial 4 = 0
BC D E F 01 F 01
BC D E
23
23
45
45
DIAL 4 DIAL 3
67 67
89A 89A
F 01 F 01
BC D E
BC D E
23
23
45
45
DIAL 2 DIAL 1
67 67
89A 89A
Continuing with this numbering system, the top BLC 6001 chassis in another stack
could be numbered as slot #1, with a chassis ID of 002. The dials would be set as
follows:
Dial 1 = 1
Dial 2 = 2
Dial 3 = 0
Dial 4 = 0
F 01 F 01
BC D E
BC D E
23
23
45
45
DIAL 4 DIAL 3
67 67
89A 89A
F 01 F 01
BC D E
BC D E
23
23
45
45
DIAL 2 DIAL 1
67 67
89A 89A
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 40 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
Configuring the Slot/Shelf ID Selector
1 Using a very small flat-head screwdriver, rotate the bottom right round switch
(dial 1) to the hexadecimal digit assigned for the slot ID value. Feel the positive
dent for each digit rotation.
2 Rotate the top left round switch (dial 4) to the first hexadecimal digit assigned
for the shelf ID value.
3 Rotate the top right round switch (position 3) to the second hexadecimal digit
assigned for the shelf ID value.
4 Rotate the bottom left round switch (position 2) to the third hexadecimal digit
assigned for the shelf ID value.
Processor: 440GP Rev. C at 396 MHz, revision 4.129 (pvr 4012 0481)
VCO: 792 MHz, PLB: 132 MHz, OPB: 66 MHz, EPB: 66 MHz, Sysclk: 33 MHz
Hostname occam, uptime is 4 days, 21:03, load average 0.00, 0.00, 0.00
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 41 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 2: Installing a BLC 6001 Chassis
BLC 6001 Chassis Specifications
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 42 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Introduction
Chapter 3
0 Installing a BLC 6012 Chassis
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Rear Panel of BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Rack Mounting the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Inserting a Blade Into the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Connecting the Subscriber and T1 Interface Cable. . . . . . . . . . . . . . . . . . . . . . . . . . 64
Connecting the 10/100/1000 Base-TX Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Connecting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Configuring the Shelf ID Selector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
BLC 6012 Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Introduction
The BLC 6012 chassis holds up to twelve 6000 series blades. The BLC 6012i chassis
requires a 23-inch rack, and is 11 ½ inches deep. It is twelve Rack Units (RUs) high
including a replaceable fan tray and fiber management shelf. The chassis also has
an optional air filter.
Blade interconnect is through a connection plane that also distributes power and
alarm connections to all of the slots. The chassis is numbered with twelve “slots”,
numbered from left to right. Slot 1 is the default fan control blade and thus will
normally always be equipped.
The BLC 6012 chassis comes prewired from the factory with one of four wiring
arrangements that are supported by the load network command.
These wiring arrangements are described in detail in Appendix B, BLC 6012 Chassis
Wiring Arrangements on page 833.
6012-F: This configuration is used by the BLC 6312 and BLC 6314.
6012-G: This configuration has four free copper ports on the BLCs in
slots 1 and 12.
6012-P: This configuration has one free copper port on the BLCs in
slots 1 and 12.
6012-R: The Ring wiring configuration is the common wiring arrangement for
the BLC 6012 chassis when used in Remote Terminal applications.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 43 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Introduction
The BLC 6012-H wiring arrangement is also available. This wiring arrange-
ment is not supported by the load network command.
Blades are shipped separately. Please read Appendix A, Safety Warnings on page 825
before installing blades in the BLC 6012 chassis.
Note: For information about installing a chassis cable guard on a BLC 6012 chassis
please see Appendix D, Installing a Cable Guard on a BLC 6012 Chassis on page 859.
The BLC 6012 Chassis is shipped with a fan assembly inserted. The fan assembly
filter should be replaced when it appears to be too full of debris to allow air to pass.
Replacement filters are available from Occam Networks.
For information about replacing a fan tray filter on a BLC 6012 chassis please see
Appendix E, Replacing a Fan Filter on a BLC 6012 Chassis on page 863.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 44 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Rear Panel of BLC 6012 Chassis
SUBSCRIBER
AND T1
"CHAMP"
CONNECTORS
ALARM/
AUXILIARY
PORTS
ETHERNET
PORTS
SHELF
SELECTORS
Ethernet Interfaces
There are six RJ45 connectors for 10/100/1000-TX Ethernet Interfaces per slot
(72 total).
Alarm/Auxiliary
Each slot has an alarm output, alarm input and auxiliary console port on an 8-pin
Molex connector.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 45 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Rear Panel of BLC 6012 Chassis
four 50-pin Champ connectors per slot (48 total). These connectors are not used on
the BLC.
Shelf Select
Shelf system ID s are implemented on 3 rotary switches on bottom right of the rear
panel of the BLC 6012 chassis. The slot ID is hard set by the slot position in the
chassis.
The Shelf ID and Slot ID should be set with network uniqueness. In other words,
each "shelf" and each "slot" in the network should be uniquely numbered. Each BLC
6012 chassis must be assigned a unique shelf ID, since the Slot ID range is 0 to 15
and the slots are hardwired as Slot 1 through 12. Therefore, two BLC 6012 chassis
that are set to the same Shelf ID would result in duplicate Shelf/Slot ID values when
the same slot is equipped in each. Slot #1 is the default fan control blade and is
normally always equipped as well as Slot #12 which is wired for the continuity of
the EPS Ring.
Power
The power connection is on the bottom middle of the rear panel of the BLC 6012
chassis. There are A and B inputs and returns on dual lug connectors. This chassis
should use 8 AWG wire at a minimum for the power connections. It is common for
a fully loaded 12 slot chassis to be fused by a 50 Amp breaker.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 46 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Site Preparation
Site Preparation
Proper installation is necessary to prevent injury to yourself and damage to the
BLC 6012 chassis. Evaluate your site using the following guidelines prior to
installation.
Cabinet Preparation
Make sure that the location is accessible and that you are able to complete the
installation. The BLC 6012 chassis requires a vertical mounting space of twelve EIA
rack units in a 23-inch rack. The chassis is 11.5 inches deep, and requires
approximately 3 inches of additional depth to allow sufficient bend radius for
cables.
Airflow Requirements
It is important to consider the following information when you plan an acceptable
cabinet rack configuration:
An enclosed cabinet must have adequate ventilation. Ensure that it is not overly
congested because each unit generates heat. Enclosed cabinets should have
adequate thermal management to provide an environment of -40C to +65C
(-40F to +149F).
When mounting the BLC 6012 in an open rack, ensure that the rack frame does
not block the bottom intake or the top exhaust ports.
In an enclosed rack with a ventilation fan in the top, excessive heat generated
by equipment near the bottom of the rack can be drawn upward and into the
intake ports of the equipment above it in the rack. Ensure that you provide
adequate ventilation for equipment at the bottom of the rack
Baffles can help to isolate exhaust air from intake air, which also helps to draw
cooling air through the chassis. The best placement of the baffles depends on
the airflow patterns in the rack, which can be found by experimenting with
different arrangements.
Power
Make sure that you have access to the power system and that the system supports
the power requirements for the BLC 6012:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 47 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Site Preparation
Network Facilities
You may either use Ethernet or T1 as your network connection.
Ethernet Connection
An Ethernet facility must be available for transport of data from the BLC to the
central office (CO). From a remote terminal (RT) this typically will be a single mode
fiber connection, using the appropriate small form factor pluggable (SFP) laser
module.
T1 Connection
If using T1 as the network connection, one or more T1 facilities must be available
for transport of traffic from the BLC 6235 to the CO. The BLC provides a CSU
interface and supports either a short haul or a long haul interface.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 48 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Preparing for Installation
Caution: If the BLC is touched or handled improperly ESD damage to the BLC can
! occur. Static voltages as low as 30 volts can damage circuitry. Make sure to observe
all standard anti-static procedures when handling electronic equipment and
components.
Always wear an ESD-preventive wrist strap when handling the BLC chassis and
blades, ensuring that the strap makes ample contact with your skin. A noninsu-
lated grounding banana jack is located on the upper right of the BLC 6012
chassis.
Note: Periodically check to make sure that the resistance value of the antistatic
wrist strap is between 1 and 10 megohms.
Remember that the wrist strap only protects the BLC from ESD voltages present
on the body. ESD voltages can also be present on clothing and can cause ESD
damage to the BLC.
Ground yourself by touching the metal part of the chassis if you do not have a wrist
strap available.
2 Remove the “Open Me First” envelope. This envelope should contain the
following items:
CD ROM containing PDFs of Occam Networks Installation Guides and
Warranty card
shipping list
release notes
5 Examine the chassis and cables for signs of damage or other mishandling.
6 Check the packing list to verify receipt of all components. Contact Occam
Networks immediately to report any discrepancies.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 49 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Rack Mounting the BLC 6012 Chassis
Cables
Make sure that each cable is adequate for installation at your site:
2 Align the holes in the brackets with the mounting holes in the equipment rack.
3 Insert the mounting screws through the holes in the brackets and into the
threaded holes in the mounting post and tighten them snugly.
Note: The racking of the 6012 chassis may require a second technician to hold the
chassis while it is being secured with rack screws.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 50 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Ground Wire
2 Unscrew the clear protection plate to reveal the ground lug and the power
terminals, as shown in Figure 3-26. A white arrow in the picture points to the
ground lug.
4 Connect a suitable ground wire (8 AWG minimum) to the ground lug. For best
grounding, use the smallest gauge AWG wire (thickest wire) possible. Connect
the ground cable using an appropriate double hole lug.
6 According to local practice, connect other end of ground cable to closest equip-
ment rack common ground bus structure with a screw, washer and lock washer
to ensure a reliable ground connection.
7 Verify the ground by placing the black test lead (-) of a voltmeter to the frame
ground. Place the red test lead on the Return A or B ground and confirm 0 (zero)
OHMs from BLC 6012 chassis ground to the equipment rack ground bus.
Warning: Do not allow the test probes of the voltmeter to touch each other
while they are touching the power terminals.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 51 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Power
Note: The alarm-out will always register an active alarm state if only one power
source is used. To prevent this, use the environment alarm voltage input
commands to disable the alarm. Information about this command may be found on
in the section Configuring Power Alarms in Chapter 36, Alarms and Sensors on page
696.
The BLC 6012 chassis is diode-protected against reversed power connections, so no
current will flow into the chassis from the power studs if the power is reverse
connected.
The power connection is on the bottom middle of the rear panel of the BLC 6012
chassis by the grounding lug. There are A and B inputs and returns on dual lug
connectors. This chassis should use 8 AWG wire at a minimum for the power
connections. These should be protected by fuse or a circuit breaker rated at 50
Amps capable of supporting 55 V DC. The nominal power requirement is –48VDC,
but the BLC 6000 Series is specified to run within the range –40VDC to –56.7VDC.
1 For single power feed locate the 48VDC RETURN A power studs. For dual power
feed locate the 48VDC RETURN A and 48VDC RETURN B power studs.
3 Connect a suitable wire power cable (8 AWG minimum) to the power 48VDC
RETURN A studs using an appropriate double hole lug.
5 Connect other end of 48VDC RETURN A power cable to closest LIVE Return
power feed within the rack enclosure. If installing single power feed only skip to
step 10.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 52 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Power
6 For dual-power-feed locate the 48VDC RETURN B (Return for B) power studs.
7 Connect a separate suitable power cable (8 AWG minimum) to the power 48VDC
RETURN B studs using an appropriate double hole lug.
9 Connect other end of 48VDC RETURN B power cable to closest redundant LIVE
48VDC Return power feed within the rack enclosure, separate from feed to
48VDC RETURN A.
10 Dress 48VDC RETURN A (and 48VDC RETURN B) cable run with cable ties or
clamps, verify tight connection on screws, nuts and connectors.
11 Use a voltmeter to confirm correct voltage level and polarity for –48VDC across
power stud set A (and –48VDC across power stud set B for dual-power- feed).
Place the black test lead (-) of the voltmeter to the Return A or B (using either
one will test both). Place the red test lead (+) on the A-side connection and
verify that it is between -42 VDC and -57 VDC. Place the red test lead on the B-
side connection and verify that it is between -42 VDC and -57 VDC.
Warning: Do not allow the test probes of the voltmeter to touch each other
while they are touching the power terminals.
Warning: Make sure that the polarity of the DC connections is correct. If the
voltmeter displays a positive polarity, wires have been crossed. Reversed polarity
causes damage to the BLC and the DC power supply and creates a dangerous
shock hazard. If the power is reverse connected at this point, re-do this detailed
procedure correctly starting at step 1.
12 Replace plastic protection plate and four screws at the lower rear of the BLC
6012 chassis.
Note: At this point, with no blade inserted, the BLC 6012 chassis has LIVE power
feed. However the fans will not turn and there are no LEDs to confirm power status
until the BLC blade is installed (described on page 54).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 53 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Inserting a Blade Into the BLC 6012 Chassis
Caution: You MUST insert blades in slots 1 and 12 of the BLC 6012 chassis, even if
! you are putting less than twelve blades in the chassis.
2 Press the compact flash (CF) card down slightly along the outside edge of the
card to ensure there is a proper connection. The CF card may be on the top or
bottom of the blade, despending upon the model number.
3 Carefully align the blade with the grooves in the BLC 6012 chassis, as shown in
Figure 3-27.
4 As you slide the blade into the chassis make sure the levers are in the open posi-
tion. When levers are open the interior edges that face the blade are in the up
position and the exterior edges of the blade are in the down position, as shown
in Figures 3-28 and 3-29.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 54 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Inserting a Blade Into the BLC 6012 Chassis
5 Carefully push the blade in the appropriate slot toward the rear of chassis as
shown in Figure 3-30. Make sure blade is loose as it is being slid in and is not
crooked.
Caution: Never force the blade into position. If in doubt of the blade’s correct
! alignment, remove, inspect and reinsert the blade.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 55 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Inserting a Blade Into the BLC 6012 Chassis
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 56 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Inserting a Blade Into the BLC 6012 Chassis
6 When the blade is pushed back as far as possible in the chassis, close the levers
on each side. The blade usually will stop at the edge of the connectors inside the
chassis. Close the levers to enable the blade to proceed onto connectors, making
sure that the levers catch the side of the BLC 6012 chassis. At this point the
blade will still not be tightly seated in the chassis.
Caution: The levers cannot usually get blade seated all the way in. If closing the
! levers causes them to jam do not force them to close. The levers may still be in
an slightly “open” position when they have gone in as far as they can, as shown
in Figure 3-31.
The levers on a blade are primarily designed to eject a blade after it has been
inserted. Their role on insertion is to get blade close enough to the chassis so that
the jacking screws can be inserted and tightened down. Attempting to fully seat
the blades by pressing hard on levers can and does break them off.
7 Tighten the jack screws on top and bottom of blade completely insert the blade
in the chassis. Tighten each screw equally top and bottom evenly to seat the
module completely in the rack.
Caution: It is mandatory to use the jack screws to lock the blade in the chassis
! to prevent vibration from shaking the blade loose. Screwing the blade tightly in
the chassis also maintains grounding and EMI seals to meet the FCC approvals.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 57 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Inserting a Blade Into the BLC 6012 Chassis
8 Repeat these steps to insert other blades in the BLC 6012 chassis.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 58 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Alarm/Auxiliary Cable
Please see Figure 3-25 on page 45 for a larger diagram showing the location of the
alarm/auxiliary connectors on the rear of a BLC 6012 chassis.
Alarm/auxiliary wires must be connected for each populated blade slot, using the
8-pin Molex connector supplied with each BLC blade. Alarm status for each BLC
blade is independent of all other BLC blades. Each BLC blade/slot combination
requires it’s own alarm connection to alarm distribution panels.
1 Hold the connector facing the 8 small shiny flat-head screws, and have the set
of 8 individual plastic plugs facing to the right.
2 Held this way, the Molex connector pins are numbered 1 (top) through 8
(bottom):
Alarm/Auxiliary Pinout
Connection No.
1 Alarm Out Normally Open
2 Alarm Out Common
3 Alarm Out Normally Closed
4 Unused
5 Alarm In
6 Auxiliary Console TX
7 Auxiliary Console GND
8 Auxiliary Console RX
3 Turn those small captive screws gently counterclockwise until each internal
“slider”, visible on the left side, bottoms lightly in the wire slot.
4 Locate the small gauge wires from the alarm distribution panel (in or near the
Equipment Rack) for each alarm function required.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 59 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Alarm/Auxiliary Cable
5 For each wire from the alarm distribution panel, locate the matching Molex
connector wire slot, and insert the small gauge wire with 1/4 inch stripped into
the open internal slider slot. Gently tighten the flat-head screw in the clockwise
direction, thus moving the internal slider up (toward the screw head) to securely
pinch and capture the wire.
6 Continue steps 2-5 until all required alarm wires are connected.
7 Insert the Molex connector in the appropriate BLC blade/slot alarm socket on
the BLC 6012 chassis rear panel (it will only fit in one direction).
8 Dress alarm wire runs with cable ties or clamps. Verify tight connection on
screws, nuts and connectors.
Note: The alarm-out will always register an active alarm state if the alarm-in is not
attached to an alarm system. To prevent this, use the environment alarm in
command to disable the alarm. Information about this command may be found in
section Environment Alarm In and Out Commands in Chapter 36, Alarms and Sensors
on page 692.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 60 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Attaching an ADSL Bridge Clip
2- Standoffs, 0.25L,
.06" THICK
SHORT STANDOFFS
W ASHERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 61 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Attaching an ADSL Bridge Clip
2 Remove the plastic dust covers from the backplane of the chassis and from the
side of the ADSL bridge clip that has two connectors. Align the two plugs on the
ADSL bridge clip to the desired J connector receptacles.
3 Use as many washers as required and four short screws from the kit to securely
fasten each corner of the ADSL bridge clip to the “J” connectors as shown in
Figure 3-36.
Caution: The ADSL bridge clip must SECURELY seat on the “J” connectors
before the screw becomes tight in the standoff. If the screw becomes tight in
! the standoff before the DSL bridge clip is securely seated you may need to use
more than one washer. The DSL bridge clip kit supplies washers in two
thicknesses. If more washers are required please contact Occam Networks.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 62 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Attaching an ADSL Bridge Clip
Figure 3-36: Attaching ADSL Bridge Clip With Washers and Screws
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 63 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Subscriber and T1 Interface Cable
Blade J1 J2 J3 J4
Model
6150-01 X T1 (1-4) POTS POTS service
service for for lines 25-48
lines 1-24
6151-01 X X POTS POTS service
service for for lines 25-48
lines 1-24
6212-02 ADSL2+ ADSL2+ X X
service for service for
lines 1-24 lines 25-48
6214 Combined Combined External External POTS
POTS / POTS / POTS signals signals on lines
ADSL2+ ADSL2+ on lines 1- 25-48
signals on signals on 24
lines 1-24 lines 25-48
6246 Combined Four X X
POTS / powered T1
ADSL2+ ports
signals on
lines 1-24
6252-03 X X Combined Combined
POTS / POTS / ADSL2+
ADSL2+ signals on lines
signals on 25-48
lines 1-24
6440-01 X T1 (1-8) X X
6640-01 X T1 (1-8) X X
6660-01/ X T1 (1-8) X X
6660-02/
6660-03
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 64 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Subscriber and T1 Interface Cable
J3 J1
J4 J2
1 Connect the plug end of the cable to the desired J connector receptacle on the
rear of the BLC 6012 chassis.
If you have attached an ADSL bridge clip to your chassis, connect the plug end
of the cable to the bridge clip.
2 Screw the champ connector to the BLC at the bottom of the J connector or to
the bridge clip.
Note: The supplied screws may be too long to use with your champ connector.
To verify if they are the correct length, extend the screw fully. The screw is too
long if it is flush with or goes past the connector’s body as shown in Figure 3-
39 (point B). Use a screw that is about 1/16 inch (1.5 mm) from the bottom of
the connector’s body as shown in Figure 3-39 (point A) when fully extended.
Warning: Each shielded connector on the rear of the BLC 6001 and BLC 6012
chassis is grounded to the chassis via the jack/hex connector screws. Do NOT
remove the jack/hex connector screws.
Caution: The champ connector must SECURELY seat on the “J” connector or
bridge clip before the screw becomes tight in the standoff. If the screw becomes
! tight in the standoff before the champ connector is securely seated you may
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 65 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Subscriber and T1 Interface Cable
need to insert one or more washers. Please contact Occam Networks if washers
are required
SCREW
A B
{
1/16 inch
3 Use the supplied tie wrap to attach other side of the champ connector to the J
connector or bridge clip as shown in Figures 3-40 and 3-41. Make sure to secure
the wire wrap snugly.
Note: Make sure that the tie wrap remains snug and does not stretch out if the
cables are moved.
4 Confirm that both ends of the champ connector are securely fastened to the J
connector or bridge clip and that the connector is firmly seated.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 66 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Subscriber and T1 Interface Cable
Figure 3-41: BLC 6012 Chassis with Champ Connector Attached to ADSL Bridge
Clip
21 5 215
52 60 25 06
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 67 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Subscriber and T1 Interface Cable
T1 Pinout Definitions
Table 3-4: T1 Interface Pinout Definition
This pinout definition conforms to industry standard RJ-48X pinout
RX = Receive from the network (into the BLC)
TX = Transmit to the network (out of the BLC)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 68 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Subscriber and T1 Interface Cable
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 69 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Subscriber and T1 Interface Cable
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 70 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the 10/100/1000 Base-TX Ethernet
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 71 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Fiber Optic Cable
Caution: You can install a SFP module in an port while the BLC is powered on and
running. However, you should enter the command shutdown, replace the module,
! and then enter the command no shutdown. Link errors may result otherwise.
2 Gently insert the module into a SFP slot on the chassis front panel. Push it into
a slot until you feel the spring catch.
Caution: To prevent contamination do not remove the dust plug from the Optical
! Laser Module until you are ready to connect the fiber cable.
3 Insert the end of the fiber cable into the module and confirm that both the SFP
module and fiber optic cable are properly seated in the port.
4 Route the fiber cable through the cable guide at the top of the BLC 6012 chassis.
! Caution: To avoid damage to your fiber-optic cables do not bend the cables to a
radius smaller than 1.5 inches (38 mm). Bending the cable farther than its minimum
bend radius may result in increased attenuation or broken fibers.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 72 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Connecting the Fiber Optic Cable
Note: Keep the SFP transceivers and fiber optic cables clean and dust-free to
prevent damage and maintain high signal accuracy.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 73 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Configuring the Shelf ID Selector
Note: The blade must be rebooted for the shelf and slot ID to take effect.
For the additional single-hexadecimal-digit Slot ID, each slot within a BLC 6012
chassis is hardwired to a value of 1-12 matching the slot number, so no manual
setting is required. The shelf and slot ID may be confirmed by running the show
version command. Please see page 75 for an example of this command and where
to find the slot/shelf ID in the output.
The Shelf ID Selector is on the bottom right of the rear panel of the BLC 6012
chassis.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 74 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
Configuring the Shelf ID Selector
F 01 F 01 F 01
BC D E
23
BC D E
BC D E
23
23
DIAL 1 DIAL 2 DIAL 3
45
45
45
67 A 67 A 67
89 89 89A
1 Using a very small flat-head screwdriver, rotate the left- most round switch
(position 1) to the first hexadecimal digit assigned. Feel the positive dent for
each digit rotation.
2 Rotate the middle round switch (position 2) to the second hexadecimal digit
assigned.
3 Rotate the right-most round switch (position 3) to the third hexadecimal digit
assigned.
4 Visually confirm the 3 round switches together match the hexadecimal Shelf ID
number assigned.
Processor: 440GP Rev. C at 396 MHz, revision 4.129 (pvr 4012 0481)
VCO: 792 MHz, PLB: 132 MHz, OPB: 66 MHz, EPB: 66 MHz, Sysclk: 33 MHz
Hostname occam, uptime is 4 days, 21:03, load average 0.00, 0.00, 0.00
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 75 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 3: Installing a BLC 6012 Chassis
BLC 6012 Specifications
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 76 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Introduction
Chapter 4
0 Installing a BLC 6012i Chassis
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Rear Panel of BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Rack Mounting the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Inserting Blades Into the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Connecting the Subscriber and T1 Interface Cable. . . . . . . . . . . . . . . . . . . . . . . . . . 98
Connecting the 10/100/1000 Base-TX Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Connecting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuring the Shelf ID Selector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
BLC 6012i Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Introduction
Release 5.5 introduces a BLC 6012 chassis with integrated wiring. This new chassis
is called the the BLC 6012i chassis. The BLC 6012i chassis has the connections
between the slots built into the backplane replacing the need for external Ethernet
jumpers to provide the communication between slots. It is designed to support all
active BLCs running OccamOS 5.5. Configuration of this chassis is described in
Chapter 4, BLC 6012I Chassis Configuration on page 77.
Note: For information about installing a chassis cable guard on a BLC 6012 chassis
please see Appendix D, Installing a Cable Guard on a BLC 6012 Chassis on page 859.
The BLC 6012 Chassis is shipped with a fan assembly inserted. The fan assembly
filter should be replaced when it appears to be too full of debris to allow air to pass.
Replacement filters are available from Occam Networks.
For information about replacing a fan tray filter on a BLC 6012 chassis please see
Appendix E, Replacing a Fan Filter on a BLC 6012 Chassis on page 863.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 77 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Introduction
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 78 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Rear Panel of BLC 6012i Chassis
SUBSCRIBER
AND T1
"CHAMP"
CONNECTORS
ALARM/
AUXILIARY
PORTS
ETHERNET
PORTS
SHELF
SELECTORS
GROUND WIRE
POWER CONNECTORS CONNECTOR
Ethernet Interfaces
There are two RJ45 connectors for 10/100/1000-TX Ethernet Interfaces per slot
(12 total).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 79 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Rear Panel of BLC 6012i Chassis
Alarm/Auxiliary
Each slot has an alarm output, alarm input and auxiliary console port on an 8-pin
Molex connector.
Shelf Select
Shelf system ID s are implemented on 3 rotary switches on bottom right of the rear
panel of the BLC 6012 chassis. The slot ID is hard set by the slot position in the
chassis.
The Shelf ID and Slot ID should be set with network uniqueness. In other words,
each "shelf" and each "slot" in the network should be uniquely numbered. Each BLC
6012 chassis must be assigned a unique shelf ID, since the Slot ID range is 0 to 15
and the slots are hardwired as Slot 1 through 12. Therefore, two BLC 6012 chassis
that are set to the same Shelf ID would result in duplicate Shelf/Slot ID values when
the same slot is equipped in each. Slot #1 is the default fan control blade and is
normally always equipped as well as Slot #12 which is wired for the continuity of
the EPS Ring.
Power
The power connection is on the bottom middle of the rear panel of the BLC 6012i
chassis. There are A and B inputs and returns on dual lug connectors. This chassis
should use 8 AWG wire at a minimum for the power connections. It is common for
a fully loaded 12 slot chassis to be fused by a 50 Amp breaker.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 80 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Site Preparation
Site Preparation
Proper installation is necessary to prevent injury to yourself and damage to the
BLC 6012 chassis. Evaluate your site using the following guidelines prior to
installation.
Cabinet Preparation
Make sure that the location is accessible and that you are able to complete the
installation. The BLC 6012 chassis requires a vertical mounting space of twelve EIA
rack units in a 23-inch rack. The chassis is 11.5 inches deep, and requires
approximately 3 inches of additional depth to allow sufficient bend radius for
cables.
Airflow Requirements
It is important to consider the following information when you plan an acceptable
cabinet rack configuration:
An enclosed cabinet must have adequate ventilation. Ensure that it is not overly
congested because each unit generates heat. Enclosed cabinets should have
adequate thermal management to provide an environment of -40C to +65C
(-40F to +149F).
When mounting the BLC 6012 in an open rack, ensure that the rack frame does
not block the bottom intake or the top exhaust ports.
In an enclosed rack with a ventilation fan in the top, excessive heat generated
by equipment near the bottom of the rack can be drawn upward and into the
intake ports of the equipment above it in the rack. Ensure that you provide
adequate ventilation for equipment at the bottom of the rack
Baffles can help to isolate exhaust air from intake air, which also helps to draw
cooling air through the chassis. The best placement of the baffles depends on
the airflow patterns in the rack, which can be found by experimenting with
different arrangements.
Power
Make sure that you have access to the power system and that the system supports
the power requirements for the BLC 6012:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 81 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Site Preparation
Network Facilities
You may either use Ethernet or T1 as your network connection.
Ethernet Connection
An Ethernet facility must be available for transport of data from the BLC to the
central office (CO). From a remote terminal (RT) this typically will be a single mode
fiber connection, using the appropriate small form factor pluggable (SFP) laser
module.
T1 Connection
If using T1 as the network connection, one or more T1 facilities must be available
for transport of traffic from the BLC 6235 to the CO. The BLC provides a CSU
interface and supports either a short haul or a long haul interface.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 82 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Preparing for Installation
Caution: If the BLC is touched or handled improperly ESD damage to the BLC can
! occur. Static voltages as low as 30 volts can damage circuitry. Make sure to observe
all standard anti-static procedures when handling electronic equipment and
components.
Always wear an ESD-preventive wrist strap when handling the BLC chassis and
blades, ensuring that the strap makes ample contact with your skin. A noninsu-
lated grounding banana jack is located on the upper right of the BLC 6012i
chassis.
Note: Periodically check to make sure that the resistance value of the antistatic
wrist strap is between 1 and 10 megohms.
Remember that the wrist strap only protects the BLC from ESD voltages present
on the body. ESD voltages can also be present on clothing and can cause ESD
damage to the BLC.
Ground yourself by touching the metal part of the chassis if you do not have a wrist
strap available.
2 Remove the “Open Me First” envelope. This envelope should contain the
following items:
CD ROM containing PDFs of Occam Networks Installation Guides and
Warranty card
shipping list
release notes
5 Examine the chassis and cables for signs of damage or other mishandling.
6 Check the packing list to verify receipt of all components. Contact Occam
Networks immediately to report any discrepancies.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 83 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Rack Mounting the BLC 6012i Chassis
Cables
Make sure that each cable is adequate for installation at your site:
2 Align the holes in the brackets with the mounting holes in the equipment rack.
3 Insert the mounting screws through the holes in the brackets and into the
threaded holes in the mounting post and tighten them snugly.
Note: The racking of the 6012iI chassis may require a second technician to hold
the chassis while it is being secured with rack screws.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 84 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Ground Wire
2 Unscrew the clear protection plate to reveal the ground lug and the power
terminals, as shown in Figure 4-2. A white arrow in the picture points to the
ground lug.
4 Connect a suitable ground wire (8 AWG minimum) to the ground lug. For best
grounding, use the smallest gauge AWG wire (thickest wire) possible. Connect
the ground cable using an appropriate double hole lug.
6 According to local practice, connect other end of ground cable to closest equip-
ment rack common ground bus structure with a screw, washer and lock washer
to ensure a reliable ground connection.
7 Verify the ground by placing the black test lead (-) of a voltmeter to the frame
ground. Place the red test lead on the Return A or B ground and confirm 0 (zero)
OHMs from BLC 6012i chassis ground to the equipment rack ground bus.
Warning: Do not allow the test probes of the voltmeter to touch each other
while they are touching the power terminals.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 85 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Power
Note: The alarm-out will always register an active alarm state if only one power
source is used. To prevent this, use the environment alarm voltage input
commands to disable the alarm. Information about this command may be found on
in the section Configuring Power Alarms in Chapter 36, Alarms and Sensors on page
696.
The BLC 6012i chassis is diode-protected against reversed power connections, so no
current will flow into the chassis from the power studs if the power is reverse
connected.
The power connection is on the bottom middle of the rear panel of the BLC 6012i
chassis by the grounding lug. There are A and B inputs and returns on dual lug
connectors. This chassis should use 8 AWG wire at a minimum for the power
connections. These should be protected by fuse or a circuit breaker rated at 50
Amps capable of supporting 55 V DC. The nominal power requirement is –48VDC,
but the BLC 6000 Series is specified to run within the range –40VDC to –56.7VDC.
1 For single power feed locate the 48VDC RETURN A power studs. For dual power
feed locate the 48VDC RETURN A and 48VDC RETURN B power studs.
3 Connect a suitable wire power cable (8 AWG minimum) to the power 48VDC
RETURN A studs using an appropriate double hole lug.
5 Connect other end of 48VDC RETURN A power cable to closest LIVE Return
power feed within the rack enclosure. If installing single power feed only skip to
step 10.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 86 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Power
6 For dual-power-feed locate the 48VDC RETURN B (Return for B) power studs.
7 Connect a separate suitable power cable (8 AWG minimum) to the power 48VDC
RETURN B studs using an appropriate double hole lug.
9 Connect other end of 48VDC RETURN B power cable to closest redundant LIVE
48VDC Return power feed within the rack enclosure, separate from feed to
48VDC RETURN A.
10 Dress 48VDC RETURN A (and 48VDC RETURN B) cable run with cable ties or
clamps, verify tight connection on screws, nuts and connectors.
11 Use a voltmeter to confirm correct voltage level and polarity for –48VDC across
power stud set A (and –48VDC across power stud set B for dual-power- feed).
Place the black test lead (-) of the voltmeter to the Return A or B (using either
one will test both). Place the red test lead (+) on the A-side connection and
verify that it is between -42 VDC and -57 VDC. Place the red test lead on the B-
side connection and verify that it is between -42 VDC and -57 VDC.
Warning: Do not allow the test probes of the voltmeter to touch each other
while they are touching the power terminals.
Warning: Make sure that the polarity of the DC connections is correct. If the
voltmeter displays a positive polarity, wires have been crossed. Reversed polarity
causes damage to the BLC and the DC power supply and creates a dangerous
shock hazard. If the power is reverse connected at this point, re-do this detailed
procedure correctly starting at step 1.
12 Replace plastic protection plate and four screws at the lower rear of the BLC
6012i chassis.
Note: At this point, with no blade inserted, the BLC 6012i chassis has LIVE power
feed. However the fans will not turn and there are no LEDs to confirm power status
until the BLC blade is installed (described on page 88).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 87 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Inserting Blades Into the BLC 6012i Chassis
Caution: You MUST insert blades into the bookend slots 1 and 12 of the BLC 6012
! chassis, even if you are putting less than twelve blades in the chassis. Blades
inserted into the bookend positions must be at least GigE BLCs (BLC 6312, BLC 6314
or BLC 6450).
Note: All blades inserted into the BLC 6012i chassis must operate with OccamOS
5.5 code.
2 Press the compact flash (CF) card down slightly along the outside edge of the
card to ensure there is a proper connection. The CF card may be on the top or
bottom of the blade, despending upon the model number.
3 Insert the blade into bookend slot 1. Carefully align the blade with the grooves
in the BLC 6012i chassis, as shown in Figure 4-3.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 88 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Inserting Blades Into the BLC 6012i Chassis
4 As you slide the blade into the chassis make sure the levers are in the open posi-
tion. When levers are open the interior edges that face the blade are in the up
position and the exterior edges of the blade are in the down position, as shown
below in Figures 4-4 and 4-5.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 89 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Inserting Blades Into the BLC 6012i Chassis
5 Carefully push the blade in the appropriate slot toward the rear of chassis as
shown in Figure 4-6. Make sure blade is loose as it is being slid in and is not
crooked.
Caution: Never force the blade into position. If in doubt of the blade’s correct
! alignment, remove, inspect and reinsert the blade.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 90 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Inserting Blades Into the BLC 6012i Chassis
6 When the blade is pushed back as far as possible in the chassis, close the levers
on each side. The blade usually will stop at the edge of the connectors inside the
chassis. Close the levers to enable the blade to proceed onto connectors, making
sure that the levers catch the side of the BLC 6012 chassis. At this point the
blade will still not be tightly seated in the chassis.
Caution: The levers cannot usually get blade seated all the way in. If closing the
! levers causes them to jam do not force them to close. The levers may still be in
an slightly “open” position when they have gone in as far as they can, as shown
in Figure 4-7.
The levers on a blade are primarily designed to eject a blade after it has been
inserted. Their role on insertion is to get blade close enough to the chassis so that
the jacking screws can be inserted and tightened down. Attempting to fully seat
the blades by pressing hard on levers can and does break them off.
7 Tighten the jack screws on top and bottom of blade completely insert the blade
in the chassis. Tighten each screw equally top and bottom evenly to seat the
module completely in the rack.
Caution: It is mandatory to use the jack screws to lock the blade in the chassis
! to prevent vibration from shaking the blade loose. Screwing the blade tightly in
the chassis also maintains grounding and EMI seals to meet the FCC approvals.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 91 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Inserting Blades Into the BLC 6012i Chassis
9 Insert the blade into bookend slot 12 in the same manner as the blade in
bookend slot 1. Verify that the blade is powered.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 92 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Alarm/Auxiliary Cable
Please see Figure 4-1 on page 79 for a larger diagram showing the location of the
alarm/auxiliary connectors on the rear of a BLC 6012i chassis.
Alarm/auxiliary wires must be connected for each populated blade slot, using the
8-pin Molex connector supplied with each BLC blade. Alarm status for each BLC
blade is independent of all other BLC blades. Each BLC blade/slot combination
requires it’s own alarm connection to alarm distribution panels.
1 Hold the connector facing the 8 small shiny flat-head screws, and have the set
of 8 individual plastic plugs facing to the right.
2 Held this way, the Molex connector pins are numbered 1 (top) through 8
(bottom):
Alarm/Auxiliary Pinout
Connection No.
1 Alarm Out Normally Open
2 Alarm Out Common
3 Alarm Out Normally Closed
4 Unused
5 Alarm In
6 Auxiliary Console TX
7 Auxiliary Console GND
8 Auxiliary Console RX
3 Turn those small captive screws gently counterclockwise until each internal
“slider”, visible on the left side, bottoms lightly in the wire slot.
4 Locate the small gauge wires from the alarm distribution panel (in or near the
Equipment Rack) for each alarm function required.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 93 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Alarm/Auxiliary Cable
5 For each wire from the alarm distribution panel, locate the matching Molex
connector wire slot, and insert the small gauge wire with 1/4 inch stripped into
the open internal slider slot. Gently tighten the flat-head screw in the clockwise
direction, thus moving the internal slider up (toward the screw head) to securely
pinch and capture the wire.
6 Continue steps 2-5 until all required alarm wires are connected.
7 Insert the Molex connector in the appropriate BLC blade/slot alarm socket on
the BLC 6012i chassis rear panel (it will only fit in one direction).
8 Dress alarm wire runs with cable ties or clamps. Verify tight connection on
screws, nuts and connectors.
Note: The alarm-out will always register an active alarm state if the alarm-in is not
attached to an alarm system. To prevent this, use the environment alarm in
command to disable the alarm. Information about this command may be found in
section Environment Alarm In and Out Commands in Chapter 36, Alarms and Sensors
on page 692.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 94 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Attaching an ADSL Bridge Clip
2- Standoffs, 0.25L,
.06" THICK
SHORT STANDOFFS
W ASHERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 95 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Attaching an ADSL Bridge Clip
2 Remove the plastic dust covers from the backplane of the chassis and from the
side of the ADSL bridge clip that has two connectors. Align the two plugs on the
ADSL bridge clip to the desired J connector receptacles.
3 Use as many washers as required and four short screws from the kit to securely
fasten each corner of the ADSL bridge clip to the “J” connectors as shown in
Figure 4-12.
Caution: The ADSL bridge clip must SECURELY seat on the “J” connectors
before the screw becomes tight in the standoff. If the screw becomes tight in
! the standoff before the DSL bridge clip is securely seated you may need to use
more than one washer. The DSL bridge clip kit supplies washers in two
thicknesses. If more washers are required please contact Occam Networks.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 96 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Attaching an ADSL Bridge Clip
Figure 4-12: Attaching ADSL Bridge Clip With Washers and Screws
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 97 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Subscriber and T1 Interface Cable
Blade J1 J2 J3 J4
Model
6150-01 X T1 (1-4) POTS POTS service
service for for lines 25-48
lines 1-24
6151-01 X X POTS POTS service
service for for lines 25-48
lines 1-24
6212-02 ADSL2+ ADSL2+ X X
service for service for
lines 1-24 lines 25-48
6214 Combined Combined External External POTS
POTS / POTS / POTS signals signals on lines
ADSL2+ ADSL2+ on lines 1- 25-48
signals on signals on 24
lines 1-24 lines 25-48
6246 Combined Four X X
POTS / powered T1
ADSL2+ ports
signals on
lines 1-24
6252-03 X X Combined Combined
POTS / POTS / ADSL2+
ADSL2+ signals on lines
signals on 25-48
lines 1-24
6440-01 X T1 (1-8) X X
6640-01 X T1 (1-8) X X
6660-01/ X T1 (1-8) X X
6660-02/
6660-03
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 98 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Subscriber and T1 Interface Cable
J3 J1
J4 J2
1 Connect the plug end of the cable to the desired J connector receptacle on the
rear of the BLC 6012i chassis.
If you have attached an ADSL bridge clip to your chassis, connect the plug end
of the cable to the bridge clip.
2 Screw the champ connector to the BLC at the bottom of the J connector or to
the bridge clip.
Note: The supplied screws may be too long to use with your champ connector.
To verify if they are the correct length, extend the screw fully. The screw is too
long if it is flush with or goes past the connector’s body as shown in Figure 4-
15 (point B). Use a screw that is about 1/16 inch (1.5 mm) from the bottom of
the connector’s body as shown in Figure 4-15 (point A) when fully extended.
Warning: Each shielded connector on the rear of the BLC 6001 and BLC 6012i
chassis is grounded to the chassis via the jack/hex connector screws. Do NOT
remove the jack/hex connector screws.
Caution: The champ connector must SECURELY seat on the “J” connector or
bridge clip before the screw becomes tight in the standoff. If the screw becomes
! tight in the standoff before the champ connector is securely seated you may
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 99 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Subscriber and T1 Interface Cable
need to insert one or more washers. Please contact Occam Networks if washers
are required
SCREW
A B
{
1/16 inch
3 Use the supplied tie wrap to attach other side of the champ connector to the J
connector or bridge clip as shown in Figures 4-16 and 4-17. Make sure to secure
the wire wrap snugly.
Note: Make sure that the tie wrap remains snug and does not stretch out if the
cables are moved.
4 Confirm that both ends of the champ connector are securely fastened to the J
connector or bridge clip and that the connector is firmly seated.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 100 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Subscriber and T1 Interface Cable
Figure 4-17: BLC 6012i Chassis with Champ Connector Attached to ADSL Bridge
Clip
21 5 215
52 60 25 06
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 101 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Subscriber and T1 Interface Cable
T1 Pinout Definitions
Table 4-4: T1 Interface Pinout Definition
RX = Receive from the network (into the BLC)
TX = Transmit to the network (out of the BLC)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 102 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Subscriber and T1 Interface Cable
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 103 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the 10/100/1000 Base-TX Ethernet
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 104 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Fiber Optic Cable
Caution: You can install a SFP module in an port while the BLC is powered on and
running. However, you should enter the command shutdown, replace the module,
! and then enter the command no shutdown. Link errors may result otherwise.
2 Gently insert the module into a SFP slot on the chassis front panel. Push it into
a slot until you feel the spring catch.
Caution: To prevent contamination do not remove the dust plug from the Optical
! Laser Module until you are ready to connect the fiber cable.
3 Insert the end of the fiber cable into the module and confirm that both the SFP
module and fiber optic cable are properly seated in the port.
4 Route the fiber cable through the cable guide at the top of the BLC 6012i
chassis.
! Caution: To avoid damage to your fiber-optic cables do not bend the cables to a
radius smaller than 1.5 inches (38 mm). Bending the cable farther than its minimum
bend radius may result in increased attenuation or broken fibers.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 105 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Connecting the Fiber Optic Cable
Note: Keep the SFP transceivers and fiber optic cables clean and dust-free to
prevent damage and maintain high signal accuracy.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 106 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Configuring the Shelf ID Selector
Note: The blade must be rebooted for the shelf and slot ID to take effect.
For the additional single-hexadecimal-digit Slot ID, each slot within a BLC 6012i
chassis is hardwired to a value of 1-12 matching the slot number, so no manual
setting is required. The shelf and slot ID may be confirmed by running the show
version command. Please see page 108 for an example of this command and where
to find the slot/shelf ID in the output.
The Shelf ID Selector is on the bottom right of the rear panel of the BLC 6012i
chassis.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 107 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
Configuring the Shelf ID Selector
F 01 F 01 F 01
BC D E
23
BC D E
BC D E
23
23
DIAL 1 DIAL 2 DIAL 3
45
45
45
67 A 67 A 67
89 89 89A
1 Using a very small flat-head screwdriver, rotate the left- most round switch
(position 1) to the first hexadecimal digit assigned. Feel the positive dent for
each digit rotation.
2 Rotate the middle round switch (position 2) to the second hexadecimal digit
assigned.
3 Rotate the right-most round switch (position 3) to the third hexadecimal digit
assigned.
4 Visually confirm the 3 round switches together match the hexadecimal Shelf ID
number assigned.
Processor: 440GP Rev. C at 396 MHz, revision 4.129 (pvr 4012 0481)
VCO: 792 MHz, PLB: 132 MHz, OPB: 66 MHz, EPB: 66 MHz, Sysclk: 33 MHz
Hostname occam, uptime is 4 days, 21:03, load average 0.00, 0.00, 0.00
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 108 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
BLC 6012i Specifications
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 109 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 4: Installing a BLC 6012i Chassis
BLC 6012i Specifications
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 110 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
Introduction
Chapter 5
0 BLC 6012i Chassis Configuration
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
BLC 6012 Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Chassis Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
BLC 6012i Chassis Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
BLC 6012 Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Frontpanel Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Installing Blades Into the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Introduction
Release 5.5 introduces a BLC 6012 chassis with integrated wiring. This new chassis
is called the BLC 6012i chassis. All blades installed in the BLC 6012i chassis must be
running OccamOS 5.5.
The BLC 6012i chassis has the connections between the slots built into the
backplane replacing the need for external Ethernet jumpers to provide the
communication between slots. It is designed to support all active BLC blades.
There are no load network commands required for this chassis. Each blade can read
the chassis backplane, so each blade knows that it's in a BLC 6012i chassis. Since
the wiring is fixed, each blade will automatically configure its internal Ethernet
ports based on the chassis type and slot occupied.
A "frontpanel" mode has been added for 10G connections. This command supports
the construction of XG interconnect on the 6012i and XG subtending to interior
slot fiber blades. Frontpanel mode is enabled with the command “frontpanel” as
described in the section Frontpanel Mode on page 117.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 111 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
Chassis Wiring
Chassis Wiring
The BLC 6012i chassis has twenty Ethernet ports accessible on the rear of the
chassis, ports 5 and 6 on interior slots 2 through 11.
Each Ethernet port in the Bookend position is used for intra-blade connectivity.
Port 6 is used to connect the bookends when frontpanel mode is not used for the
interconnect. The BLC 6012i chassis’ interior blades (Slots 2 – 11) are connected
through five subtended rings that are configured as follows:
1 1
2 6 6 2
3 3
4 4
5 5
SLOT SLOT
2 3
1 2 1 2
SLOT SLOT RING 5
4 5
1 2 1 2
SLOT SLOT
6 7 RING 4
1 2 1 2
SLOT SLOT
8 9
RING 3
1 2 1 2
SLOT SLOT
10 11
RING 2
1 2 1 2
RING 1
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 112 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
BLC 6012i Chassis Terminology
“internal (intrnl)”: These ports are associated with the BLC 6012i chassis slot to
slot connections. No external access to a port is possible and the configuration
is fixed.
The CLI only allows internal ports on the BLC to be in “shutdown” or “no shut-
down” mode. These modes are used for diagnostic purposes. The EWI Edit
function is disabled on these internal ports so no changes can be implemented
on these ports through the EWI.
The following ports are internally wired:
Ports 1-6 on blades in bookend slots 1 and 12
Ports 1 and 2 on slots 2-11.
“fiber”: These ports are actively connected to the SFP ports on the front
none: Interior ports 3 and 4 on slots 2-11 that have not been assigned for filter
resources or tagged conversion.
Table 5-1: Effect of BLC 6012i Backplane On Ethernet Ports 1-6 For All Blades
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 113 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
BLC 6012 Chassis Configuration
Note: The ring profiles attached to ports 1-5 only allow VLANs 2-122 to pass. You
may modify this configuration if your network needs require you to do so.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 114 of 880
10/09/08
10/09/08
785553 Rev. 2.0
Fiber Blades
To configure XG fiber blades (6312, 6314 and 6450) for ring operation the frontpanel command must be enabled, as described
in the section Frontpanel Mode on page 117.
Page 115 of 880
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
BLC 6012 Chassis Configuration
Interior Slots
On the interior slots (Slots 2 – 11), ports 1 and 2 are used for the connections
between slots and are labeled as “Internal Mode” by default.
Ports 3 and 4 on interior blades other than the BLC 6312 are reserved and are
labeled “Mode None” unless they are used for internal resources (looped ports or
additional filters). Ports 3 and 4 on the BLC 6312 installed in interior slots have
Ports 3 and 4 set to “Fiber Mode” when installed in the internal slots of a 6012i
chassis.
The 6312 supports dual medium (copper/fiber). All non-connected port types will
default the medium to fiber with dual medium functionality disabled and act as an
external port.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 116 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
Frontpanel Mode
Frontpanel Mode
Frontpanel mode allows fiber blades in the bookend slots (slots 1 and 12) of the BLC
6012i chassis to connect using the XG1 and XG2 ports. It is configured from EPS
configuration mode with the “frontpanel” command as follows:
occam(config)#eps
occam(config-eps)#frontpanel
Occam Networks sells a 10 Gig wiring kit (part number 535122) called the H Wiring
Kit. This wiring kit is described in the section H Wiring Configuration in Appendix B,
BLC 6012 Chassis Wiring Arrangements on page 834.
Table 5-4: Frontpanel Command Results on 6314 and 6450 blades in 6012i chassis
Interior Slots
Fiber blades in the interior slots of the 6012i chassis support subtended rings, as
shown in Figure 5-1. If issued, the frontpanel command must be entered on both
blades on a subtended ring to prevent disabling EPS resiliance.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 117 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
Frontpanel Mode
Table 5-5: Frontpanel Command Results on the 6312 blade in 6012i chassis
Interior Slots
If issued, the frontpanel command must be entered on both blades on a subtended
ring to prevent disabling EPS resiliance.
If the “frontpanel” command is enabled on a 6312 fiber blade on an interior slot,
ports 1 and 2 of that blade will be set to fiber medium mode and will be
unconfigured.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 118 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
Installing Blades Into the BLC 6012i Chassis
2 Insert the blade into bookend slot 1. Verify that the blade is powered.
The blade will be set to VPS mode by default. The blade will automatically
configure the internal backplane ports accordingly. On slot 1, Ethernet ports 1-
5 will be configured for PG1 1. The highest SFP port on the 1Gig bookend blades
will be EPS enabled for “ring all” and “igmp passthrough” for subtending addi-
tional fiber rings.
If you configure the bookend blade as a VPT any configurations will be set to the
defaults again.
3 Insert the blade into bookend slot 12. Verify that the blade is powered.
The blade will be set to VPS mode by default. The blade will automatically
configure the internal backplane ports accordingly. On slot 12, Ethernet ports 1-
5 will be configured for PG1 2. The highest SFP port on the 1Gig bookend blades
will be EPS enabled for “ring all” and “igmp passthrough” for subtending addi-
tional fiber rings.
If you configure the bookend blade as a VPT any configurations will be set to the
defaults again.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 119 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 5: BLC 6012i Chassis Configuration
Installing Blades Into the BLC 6012i Chassis
than a 6012i chassis it will be reconfigured. If the blade was in a BLC 6012i chassis
but is moved to a different slot, it will also be reconfigured, meaning any Ring
modes (Ring all setting, PG 1 or PG 2 setting, port interconnect configuration) will
be cleared and set to “none”.
Ports configured as Tagged, Untagged or Subscriber ports will not be changed. The
full configuration will be preserved only if the blade is installed in the same slot in
a BLC 6012i chassis.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 120 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Introduction
Chapter 6
Command-Line Interface (CLI)
0
Basics
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Basic Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Interface Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Profile Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Service Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Channel Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
QoS Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Finding Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Issuing Privileged Mode Commands From Other Configuration Modes . . . . . . . . 131
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Undoing a Command or Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Saving Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Erasing Configuration Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Introduction
This chapter describes what you need to know about the command-line interface
(CLI) used to configure a BLC. The CLI allows a user to interact with BLC systems.
Occam operating commands can be entered via a Secure Shell (SSH) or a Telnet
session or a local console connection. Refer to the publication Occam Command
Reference Manual for a complete description of the user interface commands.
Note: Individual BLCs use specific commands and commands modes. All commands
are not available on all BLCs.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 121 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Basic Command Modes
Global From this mode, From Privileged Mode, enter To exit to Privileged
Configura- you can enter a the configure terminal Mode, enter the exit or
tion variety of inter- command. After you enter end command.
face and profile Global Configuration Mode Use various commands
configuration the prompt will change to to enter Interface and
modes and make the host name “Occam” Profile modes.
changes to the followed by a the word
running “config” in parenthesis and
configuration. a pound sign (#). You
cannot enter Global Config-
uration Mode from User
Mode:
occam# configure terminal
occam(config)#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 122 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Basic Command Modes
Figure 6-1: Basic Command Modes
User Mode
Occam>
enable
disable
Privileged Mode
Occam#
configure
terminal
exit
Various
command
Global Configuration Mode options
Occam(config)#
exit
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 123 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Interface Configuration Modes
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 124 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Interface Configuration Modes
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 125 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Profile Configuration Modes
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 126 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Profile Configuration Modes
DS0 Voice ross- From DS0 Voice From Global Configuration Mode To exit to
Connect Profile Cross-Connect enter the command subscriber- Global Config-
Configuration Profile Configu- profile cross-connect voice uration Mode,
ration Mode you {profileName}. After you enterTDS0 enter the exit
can configure a Voice Cross-Connect Profile command.
DS0 Cross- Configuration Mode, the prompt
Connect profile will change to the host name
to attach to a “Occam” followed by the words
channel in an “config-profile” in parenthesis, the
interface group. profile name, and a pound sign (#):
Occam(config-profile)
<profileName>#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 127 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Profile Configuration Modes
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 128 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Service Configuration Modes
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 129 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Channel Configuration Mode
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 130 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Finding Command Options
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 131 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Getting Help
Getting Help
Help may be requested at any point in a command by entering a question mark (?):
Enter the first few characters (enough to uniquely identify the command)
followed by a question mark (with no space) to complete a command:
Occam> sh?
show
Note: A carriage return sign <cr> indicates that the command may be entered
as it is, without any of the other options.
Enter a question mark in place of a keyword or argument on the command line
to list a command’s keywords or arguments:
occam> show interfaces ethernet?
<1-22> Ethernet interface number
drop-counters Display drop counters for ethernet interface
errors Display ethernet interface errors
fiber Fiber Interface
max Summarize Ethernet Maximum Rates
rates Summarize Ethernet Rates
service Display services attached
summary Summary
<cr>
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 132 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Erasing Configuration Changes
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 133 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 6: Command-Line Interface (CLI) Basics
Erasing Configuration Changes
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 134 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Selecting a Connection Method
Chapter 7
Initial Configuration Steps
In This Chapter:
Selecting a Connection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Connecting the Console (Craft Interface) Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Remote Connection Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Configuring a Prewired BLC 6012 Chassis With the “load network” Command . 141
Assigning a Static IP Address to the BLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Configuring System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Configuring Network Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Configuring NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Caution: If you are using the load network command to automatically configure
! EPS on a prewired BLC 6012 chassis, as described in section Configuring a Prewired
BLC 6012 Chassis With the “load network” Command on page 141, that command
must be the first configuration command issued on the BLC. You must enter it
before you manually assign a static IP address to the BLC. Using any configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 135 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Connecting the Console (Craft Interface) Cable
commands (such as ip address) before you enter the load network command
will interfere with the proper setup of your EPS configuration.
PIN 1
PIN 1
DB-9* RJ-45**
2 (RX) 3 (TX)
3 (TX) 6 (RX)
5 (Gnd) 5 (Gnd)
*Pins 1, 4, 6, 7, 8 and 9 are not used
**Pins 1, 2, 4, 7 and 8 are not used
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 136 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Connecting the Console (Craft Interface) Cable
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 137 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Connecting the Console (Craft Interface) Cable
5 After the messages stop scrolling, press the <Enter> key to see a password
prompt. The factory default password is “occam”. The section Configuring
Network Security on page 150 describes how to change this password.If you are
automatically configuring EPS on a prewired BLC 6012 chassis you should enter
the load network command before you change the password.
Password:
6 After the password is entered, the prompt for CLI User mode appears:
Occam>
Note: If you have never configured an Occam BLC, make sure to read Chapter
6, Command-Line Interface (CLI) Basics on page 121. That chapter contains
important information about the Occam CLI and how to use it to configure your
BLC.
7 If you are configuring a blade in a prewired BLC 6012 chassis please turn to
Configuring a Prewired BLC 6012 Chassis With the “load network” Command on
page 141 to continue your configuration.
If you want to assign a static IP address to your BLC please turn to Remote
Connection Methods on page 139 for information about how to do so.
To continue to configure your BLC via the console cable please turn to Config-
uring System Parameters on page 148.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 138 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Remote Connection Methods
!
clear text, and is thus subject to snooping. In contrast, the SSH protocol
encrypts all data which provides very secure access.
Secure Shell
Access to the BLC via a SSH connection permits one to issue all standard CLI
commands, just as though connected to the console interface of the BLC.
Your computer must run a SSH client to connect to the BLC. Various commercial
and shareware SSH clients are available, such as SecureCRT (available at
http://www.vandyke.com/), puTTY.
Note: You may force an SSH disconnect by typing the SSH escape sequence, "~",
immediately followed by hitting the enter key (<CR>). This command will exit a SSH
session, whether it is locked up (because the other end has disappeared) or actively
connected.
After you have installed the SSH client, use the following steps to connect to the
BLC via a SSH connection:
1 Type “ssh cli@ippaddress” at the SSH prompt, where the IP address is the one
configured for the BLC. For example:
Unix$ssh cli@123.123.123.123
2 The prompt for the CLI login password will appear. The default password is
“occam”:
Password: occam
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 139 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Remote Connection Methods
Telnet Connection
If your facility does not have support for a SSH connection, you may use a Telnet
connection to connect to the BLC. Occam Networks strongly recommends against
using Telnet, as it does not provide adequate security.
The BLC may also initiate FTP transactions.
2 The prompt for the CLI login password will appear. The default password is
“occam”:
Password: occam
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 140 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring a Prewired BLC 6012 Chassis With the “load network” Command
!
command issued on the BLC. Using other configuration commands (such as ip
address) will interfere with the proper setup of your EPS configuration.
Commands that do not configure the BLC (such as any of the “show” commands”)
may be used however.
The prewired BLC 6012 chassis come with configurations loaded on the flash
memory. These configure the Ethernet interfaces for chassis cabling and
applications.
6012-F: This configuration is used when the chassis bookends are 6312 or 6314
-blades.
2 Enter Privileged Mode. The default password for Privileged Mode is “razor”:
Occam> enable
Password: razor
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 141 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring a Prewired BLC 6012 Chassis With the “load network” Command
9 If you want to assign a static IP address to your BLC please turn to Manually
Assigning a Static IP Address to the BLC on page 135 for information about how
to do so.
If you want to remotely access the BLC please turn to Remote Connection
Methods on page 139 for information about how to do so.
If you want to continue to configure your BLC via the console cable please turn
to Connecting the Console (Craft Interface) Cable on page 136.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 142 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring a Prewired BLC 6012 Chassis With the “load network” Command
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 143 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring a Prewired BLC 6012 Chassis With the “load network” Command
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 144 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring a Prewired BLC 6012 Chassis With the “load network” Command
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 145 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Assigning a Static IP Address to the BLC
Note: If you change the IP address of a BLC it will disrupt its behavior and that of
other BLCs attached to it in a network.
1 Enter Privileged Mode. The default password for Privileged Mode is “razor”:
occam> enable
Password: razor
occam#
3 Enter BVI Configuration Mode and create a BVI, specify specifying interface 1
(one):
occam(config)# interface bvi 1
Note: POTS and CES enabled BLCs support multihoming. These BLCs feature a
default management BVI and also support the ability to create a dynamic
second BVI. This second BVI supports transport of VoIP bearer traffic (RTP, RTCP),
SIP signaling and MGCP signaling on a VoIP VLAN
Please see Chapter 8, Configuring Multihoming on page 153 for information
about how to configure multihoming on the following BLC’s:
BLC 6150-01
BLC 6151-01
BLC 6252-02, BLC 6252-03
BLC 6440-01
BLC 6660-01, BLC 6660-02, BLC 6660-03
1.
The BLC automatically obtains an IP address for itself via DHCP. Chapter 22, IP Security Manage-
ment (IPSM) on page 451 describes how to configure the command dhcp mode. This command
specifies how a device that is attached to a BLC obtains it’s own IP address via DHCP.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 146 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Assigning a Static IP Address to the BLC
7 Assign a static IP default route to the bridge group to direct all traffic not
destined for your network to a default router:
occam(config)# ip default-route ip-address
11 You may now continue to connect to the BLC CLI via a console connection or
you may remotely access it through either a SSH or a Telnet session. Please turn
to Configuring System Parameters on page 148 to continue your configuration.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 147 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring System Parameters
2 Enable syslog with the logging command. Syslog allows you to log and analyze
system events and errors to a local log file or to a remote loghost. The logging
command allows you to specify a facility, a log priority level and (optionally) a
remote loghost.
Messages logged locally are written to the file /var/log/messages.
! Caution: Given the limited storage capacity of the BLC compact flash, logging
to the local log file at a severity above critical (crit[ital]) is strongly discouraged.
Facility
The facility specifies the subsystem that produced the message (e.g., all messages
from the linux kernel are logged with the facility "kern"). The factory default
facility is "all available facilities" (denoted by "*" in the CLI).
The facilities supported (in ascending order) are as follows:
syslog
security
kern
ftp
daemon
authpriv
auth.
Level
The “level” indicates the severity of the message. An asterisk (*) is a wildcard
meaning “all levels”. When a level is specified, log messages of that level and all
higher levels are sent to the logging host. The default log level is "warning level"
("warn" in the CLI).
The log priority levels (in ascending order) are as follows:
debug
info
notice
warn
error
crit
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 148 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring System Parameters
alert
emerg(ital. all).
Multiple logging entries are permitted and each may specify facility, log severity
level, and loghost. For more information on Syslog please refer to Chapter 38,
System Logging (Syslog) on page 751.
occam(config)# logging [facility.level] syslog-host
3 Occam Networks recommends that you disable Telnet access to the BLC if you
are able to use an SSH connection to the BLC:
occam(config)# no telnet
4 (Optional) Change the name of the BLC from “occam” to a name you choose:
occam(config)# hostname name
You may delete a hostname with the command no hostname.
Note: When a hostname is given, the BLC also automatically adds an IP
hostname with the IP address of the BVI.
The first word is a key, anything after is the value attached to that key. In the
above example, 'nextReboot' is the key. You can have several info messages and
you can remove any of them by using the command no info {key}. There is no
limit on the text length, but you cannot use any of the following characters:
TAB, <enter>, '?', '!'.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 149 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring Network Security
2 Change the Unix password to enter the system root from the factory default.
When prompted, enter and verify the new password. The password must be at
least six characters long. A maximum of three verification attempts may be
made.If you choose the “clear” option, enter the password in a clear text form.
That password will be encrypted. If you choose the “encrypted” option, enter the
password in an already encrypted form:
occam(config)# unix password root {clear | encrypted} password}
3 Set your own password to enter User Mode. The factory default password is
“occam”. Use the command no login password to remove the need for a pass-
word and allow User Mode to be entered by a simple carriage return:
occam(config)# login password password
4 Use the enable password command to set your own password to enter Privi-
leged Mode. The factory default password is “razor”. Use the command no
enable password to remove the need for a password and allow Privileged Mode
to be entered by a simple carriage return.
Type a “7” if you use a password that is already encrypted so it will not be
encrypted again. You will not normally need to enter an encrypted password, as
passwords are encrypted within the configuration and are displayed as such if
you display your configuration with a command such as show running-
configuration:
occam(config)# enable password [7]password
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 150 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring NTP
Configuring NTP
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
occam(config)#
2 Configure an NTP date-server. Enter the command and a fully qualified domain
name or the IP address of the server running NTP:
occam(config)# ntp date-server ip-address
4 Enter the show ntp command to verify the configured servers and that the NTP
date server has synchronized with a NTP server.
In the following example no NTP server has been configured:
occam# show ntp
No date-server hosts configured
occam#
In the following example a NTP server has been configured but is not
reachable OR not enough time (five minutes) has elapsed for a status file to
be shown:
occam# show ntp
Status: Not synchronized
Servers: 10.0.0.57
occam#
In the following example a NTP server has been configured and there is a
valid status file:
occam# show ntp
Status: Synchronized to (10.0.0.57)
Servers: 10.0.0.57
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 151 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 7: Initial Configuration Steps
Configuring NTP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 152 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Introduction
Chapter 8
Configuring Multihoming
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Configuring a BVI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Configuring a Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Configuring Protocols To Run On a Specific BVI. . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Checking the BVI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Introduction
OccamOS supports multihoming on the following POTS and CES enabled BLCs:
BLC 6150-01
BLC 6151-01
BLC 6440-01
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 153 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Introduction
MGMT
ROUTER
BLC
EPS RING
VOICE
SERVICES/
INTERNET
Routing
Two routing tables are supported with two forwarding data bases. When voice
applications are bound to BVI 1 or BVI 2, application source traffic will be directed
to the routing table defined for that IP interface to determine what the forwarding
policies are for that particular traffic.
The BLC automatically creates a second policy routing table when BVI 2 is
configured and binds BVI 2 to that routing table. The BLC also creates a forwarding
policy that causes packets that are sourced by applications with BVI 2’s IP address
to be routed to that second policy routing table.
The commands ip route table main and ip route table policy configure the routing
tables for BVI1 and BVI 2, respectively. These commands, entered from Global
Configuration mode, allow you to enter a sub-menu mode for each route table and
allow you to configure both static routes and default routes that point to the
gateway on BVI’s network. In addition, the routing table for BVI 1 may configured
by using the commands ip route and ip default-route from Global Configuration
mode.
Routing table configuration is described in the section Configuring a Routing Table
on page 158. You may view the route table configuration by using the command
show ip route [policy, main] which is described in the section Using the “show ip
route” Command on page 162.
Binding a voice application to a specific BVI causes that application to be bound to
a specific interface IP address. The application creates an IP header with that source
IP address when it initiates the forwarding process. When traffic encounters the
system filter that is configured by default on the IP interface, the interface
recognizes the source IP address and tags the packet with a particular mark. Later
in the forwarding process the routing policy manager will see the tag and look up
its particular destination within the correct routing table context.
You may view which protocols are bound to each IP interface by using the
command show interfaces bvi binding which is described in the section Using the
“show interfaces bvi binding” Command on page 162.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 154 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Introduction
Ingress Traffic
System filters are automatically installed on BVI 2 that only accept ICMP packets
and any protocol bound to the BVI. All other packets are dropped.
Egress Traffic
The only traffic that may be sent out of BVI 2 are ICMP packets and traffic for the
application that is bound to that IP interface. Any application traffic not bound to
the IP interface will not be sent out of it and will be routed in the context of the
main routing table.
DHCP
In addition to statically configuring each BVI you may also configure them to
acquire their IP addresses from a DHCP server. This is described in the section
Configuring a BVI on page 157. If configured to do so, each BVI will send a request
to their DHCP servers, get back interface specific IP addresses and any other
configured parameters (i.e. the default route).
ACLs
In addition to the system defined ACLs that are automatically created, user defined
ACLs can be configured on each BVI to restrict the set of host devices that have
access to the BLC.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 155 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Introduction
Create a BVI on the BLC, configuring it with a unique IP address. Configure the
BVI to be on a unique EPS VLAN. Enable the BVI with the command no shut-
down. This is described in the section Configuring a BVI on page 157.
Bind one or more voice applications (SIP, MGP, RTP) to the BVI. This is described
in the section Configuring Protocols To Run On a Specific BVI on page 160
Commands to view your configuration are described in the section Checking the BVI
Configuration on page 161
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 156 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Configuring a BVI
Configuring a BVI
1 Enter Global Configuration Mode:
Occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
3 Put each BVI on a separate VLAN, selecting a VLAN number between 2 and 122:
Occam(config-if-bvi#)# eps access untagged vlan {2-122}
Note: If you do not enter the default gateway address with the ip address
command, as shown here, you must enter it by using the ip default-route
command as shown below in the following section, Configuring a Routing Table.
You may use the command show interfaces bvi to view the configuration of one
or both BVIs. This command is described in the section Using the “show interfaces
bvi” Command on page 161.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 157 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Configuring a Routing Table
Note: The routing table for BVI 1 (route table main) must be configured with
routes that cover all the route destinations that the voice applications that are
bound to BVI 2 are trying to reach. The easiest way to do this is to configure a
default route for BVI 1.
2 Assign a static IP default route to the bridge group to direct all traffic not
destined for your network to a default router:
occam(config)# ip default-route ip-address
3 (Optional) Configure a static route, specifying the IP route prefix for the desti-
nation, the prefix mask for the destination and the forwarding gateway’s IP
address:
occam(config)# ip route {prefix} {mask} {gateway}
3 (Optional) Configure a static route, specifying the IP route prefix for the desti-
nation, the prefix mask for the destination and the forwarding gateway’s IP
address:
Occam(config-rtable-main)# ip route {prefix} {mask} {gateway}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 158 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Configuring a Routing Table
3 (Optional) Configure a static route, specifying the IP route prefix for the desti-
nation, the prefix mask for the destination and the forwarding gateway’s IP
address:
Occam(config-rtable-policy)# ip route {prefix} {mask} {gateway}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 159 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Configuring Protocols To Run On a Specific BVI
MGCP
MGCP configuration is described in Chapter 23, Managed Multicast Via IGMP Proxy
on page 479.
Configure MGCP to run on BVI 1 or BVI 2 by entering the following command from
Global Configuration Mode
Occam(config)# mgcp interface bvi {1, 2}
The no form of the command configures MGCP to run on BVI 1, the factory default:
Occam(config)# no mgcp interface
RTP
Configure RTP to run on BVI 1 or BVI 2 by entering the following command from
Global Configuration Mode:
Occam(config)# rtp interface bvi {1, 2}
The no form of the command configures RTP to run on BVI 1, the factory default:
Occam(config)# no rtp interface bvi
Note: When the command rtp interface bvi is issued, both voice RTP traffic and
CES traffic will be moved. If you configure RTP on BVI 2 in a CES configuration, you
will need to also configure your CES links to run on BVI 2.
SIP
SIP configuration is described in Chapter 20, Configuring SIP on page 379.
Configure SIP to run on BVI 1 or BVI 2 by entering the following command from
Global Configuration Mode
Occam(config)# sip interface bvi {1, 2}
The no form of the command configures SIP to run on BVI 1, the factory default:
Occam(config)# no sip interface
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 160 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Checking the BVI Configuration
show interfaces bvi, to view the configuration of both BVIs (see below)
show interfaces bvi binding, to view which interfaces protocols are bound to
each IP interface (page 162)
show ip route, to view the configurations of the main and policy route tables
(page 162)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 161 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Checking the BVI Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 162 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Checking the BVI Configuration
[SIZE] = Optional) Specifies the datagram size. The range is from 40 to 18024
bytes in each ping. The default is 64 bytes.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 163 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 8: Configuring Multihoming
Checking the BVI Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 164 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Ethernet Interface Overview
Chapter 9
Ethernet Interface Configuration
In This Chapter:
Ethernet Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Speed, Duplex and Media Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Configuring 10/100/1000 Base-TX Ethernet (UTP) Interfaces . . . . . . . . . . . . . . . . 171
Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces . . . . . . . . 173
Configuring 10 GigE Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Checking Connectivity and Verifying Configuration . . . . . . . . . . . . . . . . . . . . . . . 176
Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces on page 173
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 165 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Ethernet Interface Overview
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 166 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Ethernet Interface Overview
Defaults:
Ports 1 and 2 default to be 10/100/1000 BaseT Ethernet Ports on RJ 45
connectors 1 and 2.
Ports 3 through 6 default to be Fiber/SFP ports
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 167 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Ethernet Interface Overview
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 168 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Speed, Duplex and Media Settings
The factory default configuration for the duplex and speed commands is “auto
negotiation”.
To configure speed and duplex modes for the Ethernet interfaces, use the following
commands in Ethernet Interface Configuration Mode:
speed {10 | 100 | 1000 | auto}
duplex {full | half | auto}
Media Command
The media command is used to force a link when connected to non-Occam
equipment and there is a requirement that the speed AND duplex settings not be
configured to auto (using the commands speed auto and duplex auto).
Warning: The media command should only be used when it is absolutely required
! and only when connecting to non-Occam equipment. Leave all speed, duplex and
media commands to their default settings when connecting to Occam equipment.
The media xover and media straight commands only apply to copper ports when
the speed is set to 10 or 100 Mbps (speed 10 or speed 100) and duplex full or half
(duplex full or duplex half). The speed may not be set at 1000 Mbps (speed 1000)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 169 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Speed, Duplex and Media Settings
when the media xover and media straight commands are used.
If you are connecting a BLC Ethernet interface to an ISP that requires you to force
the link, Occam Networks recommends that you request that the ISP be set to auto
negotiate while advertising only 100Mbps.
Once the link is up, check both Ethernet devices to make sure they are in full duplex
mode. If not, change the media setting to crossover (xover) and recheck the link.
Once the link is up and in full duplex mode, you must save the configuration
settings on the BLC. If the configurations are not saved, the link may not come up
or may be prone to errors once you reboot.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 170 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Configuring 10/100/1000 Base-TX Ethernet (UTP) Interfaces
Table 9-3: Default Configuration for the 10/100/1000 Base-TX Ethernet Interface
Configuration Steps
Use the following instructions to configure the 10/100/1000 Base-TX Ethernet
interfaces. Please refer to the Occam Networks publication Command Reference
Guide for more information on the commands used in these configuration steps:
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
occam(config)#
The first word is a key, anything after is the value attached to that key. In the
above example, 'subscriber' is the key. You can have several info messages and
you can remove any of them by using the command no info {key}'. There is no
limit on the text length, but you cannot use any of the following characters:
TAB, <enter>, '?', '!'.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 171 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Configuring 10/100/1000 Base-TX Ethernet (UTP) Interfaces
10 Save your configuration. Refer to the section Checking Connectivity and Verifying
Configuration on page 176 for information on how to confirm your Ethernet
configuration:
occam# copy running-config startup-config
Building configuration....
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 172 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces
Table 9-4: Default Ethernet Configuration for 1000 Base-LX Ethernet Interfaces
Configuration Steps
Use the following instructions to configure the 1000 Base-LX Optical interfaces.
Please refer to the Occam Networks publication Command Reference Guide for
more information on the commands used in these configuration steps:
For example:
occam(config-if-eth)# info subscriber 123_Main
The first word is a key, anything after is the value attached to that key. In the
above example, 'subscriber' is the key. You can have several info messages and
you can remove any of them by using the command no info {key}. There is no
limit on the text length, but you cannot use any of the following characters:
TAB, <enter>, '?', '!'.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 173 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces
7 To configure the other 1000 Base-LX Ethernet interface repeat steps 2 through
7.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 174 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Configuring 10 GigE Interfaces
4 For example:
occam(config-if-xg)# info subscriber 123_Main
The first word is a key, anything after is the value attached to that key. In the
above example, 'subscriber' is the key. You can have several info messages and
you can remove any of them by using the command no info {key}. There is no
limit on the text length, but you cannot use any of the following characters:
TAB, <enter>, '?', '!'.
9 Save your configuration. Refer to the section Checking Connectivity and Verifying
Configuration on page 176 for information on how to confirm your Ethernet
configuration:
occam# copy running-config startup-config
Building configuration....
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 175 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Checking Connectivity and Verifying Configuration
2 Trace the route of packets from the BLC to a remote host located out the inter-
face you want to test:
occam# traceroute ip_address
3 If the host is unresponsive via the ping command or telnet, check the IP address
configured on the BLC by using the show interfaces bvi command. Also verify
that the subnet mask for the interface is set correctly and that it matches the
subnet mask assigned on the LAN:
occam# show interfaces bvi 1
BVI1/1 is up, line protocol is up
Hardware is Bvi
Internet address is 192.168.99.199/255.255.255.0
MTU 1500 bytes, BW 100000 Kbit
EPS Settings:
eps access untagged vlan 2
Last input 0, output 0
894 packets input, 57752 bytes
0 input errors
601 packets output, 79703 bytes
0 output errors
4 If you are trying to ping to an IP address in another IP subnet, ensure that the
BLCs default gateway parameter is set correctly.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 176 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Checking Connectivity and Verifying Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 177 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 9: Ethernet Interface Configuration
Checking Connectivity and Verifying Configuration
rates. If you specify an interface number you will receive information about a
specific Ethernet interface. If you do not enter an interface number this
command output will display this information about all Ethernet interfaces. Use
the command clear ethernet rates to reset Ethernet rate counters.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 178 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Introduction
Chapter 10
Ethernet Protection Switching (EPS)
Overview
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
EPS Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
EPS Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Ethernet Interfaces on VPSs and VPTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
MAC Address Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
QoS Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Subtended Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
EPS Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Ethernet Loop Detection (ELD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Adding a VPS To an Active Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Adding a VPS To an Active Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Introduction
Ethernet Protection Switching (EPS) is a new Ethernet-based technology that
delivers the redundancy and fast failover attributes of existing Synchronous Optical
Network (SONET) networks without the 16-node limitation of SONET networks.
This chapter provides an overview of EPS.
Please read the following chapters for more information about configuring EPS:
Chapter 11, Configuring an EPS Aggregation Ring Network on page 199 provides
information about configuring an EPS aggregation network.
Chapter 12, Configuring Subtended EPS Access-Rings with Ethernet Links on page
243 provides information about how to configure subtended EPS access rings.
Chapter 13, Configuring EPS Over MLPPP Links on page 253 provides information
about how to configure EPS over MLPPP links.
Chapter 15, Rate Limiting on Ethernet and XG Interfaces on page 297 provides
information about how to configure rate limiting on an Ethernet or XG interface
for ingress and egress traffic in Mbps.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 179 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Overview
EPS Overview
EPS uses industry standard 802.1Q Virtual LANS (VLANS) to enable the construction
of ringed Ethernet topologies. EPS makes it possible to safely construct Ethernet
loop topologies by segmenting a ring into two groups of VLANS which are called
Path Groups (PGs). These PGs are labeled Path Group 1 (PG1) and Path Group 2
(PG2).
VPTs
The VLAN path groups each terminate at the head end of the EPS ring on a pair of
BLC systems set up as VPTs (VLAN path terminators). Each VPT is designated as part
of one of the path groups. Any BLC that features Gigabit Ethernet may be
configured as a VPT.
Each ring must contain two VPTs. All other BLCs on the ring have VPS functionality.
If your network is large enough to require more than one EPS ring, each ring should
be connected by a router that maintains separation between the multiple EPS rings.
A bridge loop is prevented by each of the VPTs only communicating on their
designated path group. The VPTs are connected together by an interconnect. The
interconnect enables the VPTs to pass traffic destined for the other path group
across to the other VPT. The non-interconnect ports are available for ring
construction or for untagged or tagged VLAN access ports.
VPSs
VPSs typically listen on both path groups and actively communicate on one path
group. The VPS uses two Ethernet interfaces to access and continue the ring.
The VPS provides full functionality for customer services. Configuration of path
groups is based on how much load is on the rings. If there are four VPSs, typically
two would be configured to prefer PG1 and two would prefer PG2.
What Is a Heartbeat?
The heartbeat is a multicast packet that contains information such as the path
group, the source MAC address and the ring ID. The heartbeat generation interval
may not be configured.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 180 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Overview
Alarms
Alarms are generated when an EPS device fails to detect heartbeats or its active
path group and fails over to the standby path group. A restoration clears the failure
alarm and the VPS automatically reverts back to its preferred Path Group.
Please see section EPS Alarms on page 196 for more information about EPS alarms.
Figure 10-1 shows a diagram of a simple EPS network.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 181 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Overview
VIDEO
HEADEND
V V
P P
T T
CLASS 5
1 2 SWITCH VOICE
ISP ROUTER
PG2
BLC 6012
PG1 PG2
PG1 PG2
VPS VPS
BLC 6012
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 182 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Overview
VLAN IDs
The IEEE 802.1q standard creates VLANs by adding a “tag” to an Ethernet packet.
This tag is attached at the origin switch and directs other switches to send the
packet only to members of the same VLAN. It is typically removed by the last BLC
prior to transmitting to the destination host. BLCs on access rings support VLAN
TAG numbers from 2-122. The BLC 6450, used on aggregation rings, supports VLAN
TAG numbers from 2-1000.
1-4094
8 1 0 0 0-7 0
(BLC supports 2-122)
VLAN Numbering
Each Path Group may contain multiple VLANs.
VLAN Number 1: VLAN 1 is reserved for EPS control purposes. This VLAN is invis-
ible and provides the “heartbeat” (this concept is further explained in the section
Ethernet Interfaces on VPSs and VPTson page 187)
VLAN Number 2 – Management and Voice (as well as the single VLAN default):
EPS VLAN 2 is pre-configured as the default for all ports. This default setting
means you can install a BLC and have all interfaces reachable with minimal
configuration in a basic network design.
VLANs 5, 7-122 - Multiple ISP VLANs: If you have several separate ISPs sharing
the same set of BLCs, you can add more EPS VLAN numbers (5, 7-122), one for
each ISP’s set of subscriber ports. Each ESP VLAN number set of ports will be
isolated from every other set of ports, and automatically from the internal
“management” ports (such as BVI 1) which remain configured in EPS VLAN 2.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 183 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Overview
Note: The information above pertains to traffic within the BLC EPS domain. As
traffic leaves a BLC and goes out toward an ONT, video multicast traffic that was
previously on VLAN 3 exits with video unicast and broadcast traffic on VLAN 6.
Please see Chapter 14, Ethernet Subscriber Interfaces on page 281 for more
information.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 184 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Keys
EPS Keys
An EPS Key connects two switch ports together. It allows the BLC’s internal switch
to remap frame VLAN IDs that pass between the two ports (e.g. PG1 and PG2) at a
VPTs or to another tagged value upon exit of the BLC network.
Note: Once ports have been reserved as EPS Key ports, they cannot be used for
anything else. Also, after a port is reserved as an EPS Key port, any configuration
that was previously on it will be lost.
On most BLCs an internal EPS Key must be reserved prior to configuring a BLC as a
VPT and at each location a tagged port is used. Each tagged interface must have an
EPS key available at boot time. If two tagged interfaces on the same blade then two
EPS keys are required, etc.
Look below in Table 10-1 to see if your BLC requires an internal EPS key.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 185 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Keys
OR
After the internal EPS Key has been configured, continue with your configuration.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 186 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Ethernet Interfaces on VPSs and VPTs
Note: Subscriber traffic that joins the EPS ring only on VPTs and is not present
anywhere else on the ring will be treated as unknown multicast traffic on the
upstream router ports.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 187 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Ethernet Interfaces on VPSs and VPTs
A A
V V
P P
T T
B C
1 2
PG1 PG2
BLC 6012
D D D
D D D
V V V V
P P P P
S S D S S
D
1 2 5 6
PG1 PG2
D D
D D
V V
P P
S S
3 4
BLC 6012
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 188 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Ethernet Interfaces on VPSs and VPTs
Caution: On the BLC 6150-01, BLC 6212-02, BLC 6252-02, BLC 6252-03,
! BLC 6440-01, and BLC 6640-01 the command eps key reserve must be executed
prior to configuring a port as tagged.
Untagged Interfaces
When an untagged packet enters an interface, the BLC will tag it with an ID number
configured with the command “eps access untagged vlan {VLAN-ID-number}”.
VPS and VPT interfaces that will transmit to networks nodes that expect untagged
Ethernet frames should be configured with this command. These are typically
subscriber ports and primary ISP “feeder” networks connected at the COT.
Please turn to the section Configuring a VPS or VPT Ethernet Interface for Untagged
Traffic, in Chapter 11, Configuring an EPS Aggregation Ring Network on page 225.
Tagged Interfaces
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 189 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Ethernet Interfaces on VPSs and VPTs
BLC 6150-01
BLC 6212-02
BLC 6312
BLC 6314
BLC 6440-01
BLC 6640-01
TLS configuration is described in Chapter 11, Configuring an EPS Aggregation Ring
Network. Please refer to the section Configuring TLS on page 230.
Subscriber Interfaces
The command eps access subscriber configures an interface to be an Ethernet
subscriber interface. This means that the fiber link connects to an ONT prepared for
one or more VLANs providing the option of multiple independent services to the
customer premesis. VLAN isolation and relative prioritization are maintained across
the fiber link.
Subcriber interfaces use access profiles s that can be assigned to a service on the
subscriber port. Fiber access profiles support:
DHCP Relay
IGMP Proxy
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 190 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Ethernet Interfaces on VPSs and VPTs
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 191 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Rate Limiting
Rate Limiting
System 6000, with the exception of the BLC 6151-01, supports rate limiting on
Ethernet network interfaces. Rate limiting may be configured on an interface by
interface basis for ingress and egress traffic in Mbps (Megabits per second).
Additional rate limiting may be performed on multicast, broadcast and unknown
unicast traffic on an interface by interface basis for ingress traffic in PPS (packets
per second) allowed. This rate limiting helps to prevent multicast, broadcast and
unknown unicast storms which create excessive traffic and degrade network
performance.
Information about how to configure rate limiting on an Ethernet interface is
described in Chapter 15, Rate Limiting on Ethernet and XG Interfaces on page 297.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 192 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
MAC Address Forwarding
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 193 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
QoS Mapping
QoS Mapping
EPS maps QOS traffic classes to 802.1 p tags on MAC frames on egress. On ingress
802.1 p tags are mapped to traffic classes. 802.1 establishes eight levels of priority
similar to IP Precedence. Network adapters and switches route traffic based on the
priority level (high or low). Table 10-2 shows these levels of priority. The asterisk (*)
shows the egress maps.
Subtended Rings
You may configure your EPS network with one or more subtended agggregation
and access rings.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 194 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Subtended Rings
Information about how to configure a subtended ring with MLPPP links is described
in the section Chapter 13, Configuring EPS Over MLPPP Links in the section
Configuring a Subtended EPS Ring with MLPPP on page 259.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 195 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Alarms
EPS Alarms
EPS has three possible alarms: an EPS Failover Alarm, an Opposite Path Group Alarm
and an EPS "Dead In The Water" (DITW) Alarm. These alarms are described below.
ClearedTimestamp: when the alarm was cleared (valid for cleared alarms only)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 196 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
EPS Alarms
ClearedTimestamp: when the alarm was cleared (valid for cleared alarms only)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 197 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 10: Ethernet Protection Switching (EPS) Overview
Ethernet Loop Detection (ELD)
unplug Ethernet interfaces from VPSs on the ring (if they are interfaces that are
presently configured to participate in the ring)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 198 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Introduction
Chapter 11
Configuring an EPS Aggregation
Ring Network
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Configuring an Access-Ring Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Configuring a Ring Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Configuring BLCs On an Aggregation Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Configuring an Interconnect on a VPT on an Aggregation Ring . . . . . . . . . . . . . . 210
Configuring a VPT Ethernet Interface as a Path Group Participant . . . . . . . . . . . 212
Configuring a VPS Interface on an Aggregation Ring . . . . . . . . . . . . . . . . . . . . . . 214
Configuring a VPS Interface on a Subtended Aggregation Ring. . . . . . . . . . . . . . 216
Configuring an Access-Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Configuring a VPS or VPT Ethernet Interface for Untagged Traffic . . . . . . . . . . . 225
Configuring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic . . . . . . . . 226
Configuring TLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Configuring a BLC to Run EPS with Non-EPS Devices . . . . . . . . . . . . . . . . . . . . . . 235
Ethernet Loop Detection (ELD) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Displaying Information About Your EPS Configuration . . . . . . . . . . . . . . . . . . . . . 239
Introduction
EPS Configuration
This chapter describes how to configure an EPS Aggregation Ring network.
Please read the following chapters for more information about configuring EPS:
Chapter 10, Ethernet Protection Switching (EPS) Overview on page 179 provides an
overview of EPS.
Chapter 12, Configuring Subtended EPS Access-Rings with Ethernet Links on page
243 provides information about how to configure subtended EPS access rings.
Chapter 13, Configuring EPS Over MLPPP Links on page 253 provides information
about how to configure EPS over MLPPP links.
Chapter 15, Rate Limiting on Ethernet and XG Interfaces on page 297 provides
information about how to configure rate limiting on an Ethernet or XG interface
for ingress and egress traffic in Mbps.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 199 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Introduction
about how to configure Ethernet fiber interfaces can serve as subscriber facing
interfaces.
Note: Enabling/disabling aggregation mode will reset all external ports to the
default EPS configuration.
Figure 11-1: EPS Aggregation Ring Network Overview
INTERNET MIDDLEWARE/
ROUTER DHCP SERVER
IP VIDEO
HEAD-END VoD
SERVER
AGGREGATION
RING
BLC 1
BLC 6
VPS 1 and VPS 2 have access-ring profile “west-salem” associated with them.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 200 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Introduction
VPS 3 and VPS 4 have access-ring profile “east-side” associated with them. This
profile translates the VLANs on Access-Ring 2 as follows:
Figure 11-2 shows an aggregation ring subtended off of the main EPS aggregation
ring.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 201 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Introduction
INTERNET MIDDLEWARE/
ROUTER DHCP SERVER
IP VIDEO
HEAD-END VoD
SERVER
6450 VPS 7
6450 VPS 8
6450 VPS 9
BLC 9
ACCESS
BLC 4 ACCESS RING 3
RING 2 (EAST-MIDWAY)
(WEST-MIDWAY)
BLC 7
BLC 6
BLC 5 BLC 8
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 202 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Introduction
The BLCs on all three access-rings use VLAN 2 for voice, VLAN 3 for video and VLAN
4 for data.
Access-Ring 1 (“west-salem”)
VPS 5 and VPS 6 on access-ring 1 ‘have an access-ring profile named “west-salem”
associated with them. This profile translates the VLANs on Access-Ring 1 as follows:
Access-Ring 2 (“west-midway”)
VPS 7 and VPS 8 on access-ring 2 have access-ring profile “west-midway”
associated with them. This profile translates the VLANs on Access-Ring 2 as follows:
Access-Ring 3 (“east-midway”)
VPS 9 and VPS 10 on access-ring 3 have access-ring profile “west-midway
associated with them. This profile translates the VLANs on Access-Ring 1 as follows:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 203 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Introduction
Access-Ring 4 (“east-salem”)
VPS 11 and VPS 12 on access-ring 4 have access-ring profile “east-midway”
associated with them. This profile translates the VLANs on Access-Ring 2 as follows:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 204 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Access-Ring Profile
3 For example, if a access-ring profile “west-salem” was being created for VPS 1
and 2 in Figure 11-1, or VPS 5 and 6 in Figure 11-2, the commands should be as
follows:
occam(config)# access-ring-profile west-salem
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 205 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Access-Ring Profile
For example:
occam# do show access-ring-profile west-salem
access-ring-profile west-salem:
aggregation vlan access vlan
2 2
3 3
401 4
601 6
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 206 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a Ring Profile
2 Enter Ring Profile Configuration Mode and create a Ring Profile with a specific
name:
occam(config)# ring-profile {profile-name}
3 For example, if Ring Profile “west” was being created for VPS 1 and 2 in Figure
11-2, the command should be as follows:
occam(config)# ring-profile west
4 Enter the numbers of the VLANs that are allowed to pass through this BLC.
occam(config-ring-profile)# allow {VLAN-number}
Repeat this command as many times as necessary, once for each VLAN.
For example, if Ring Profile “west” was being created for VPS 1 and 2 in Figure
11-2, all of the VLANs that pass though VLANs 6 - 8 should be included:
occam(config-ring-profile)# allow 2
occam(config-ring-profile)# allow 3
occam(config-ring-profile)# allow 401
occam(config-ring-profile)# allow 402
occam(config-ring-profile)# allow 601
occam(config-ring-profile)# allow 602
6 For example, to view Ring Profile “west”, enter the following command:
occam(config-ring-profile)# do show ring-profile west
ring-profile west:
eps vlan
2
3
401
402
601
602
occam(config-ring-profile)#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 207 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring BLCs On an Aggregation Ring
6450 VPT 1
6450 VPT 2
6450 VPS 3
6450 VPS 4
3 Select VPT as the EPS mode for the BLC and configure the PGs:
VPT 1:
occam(config-eps)# mode vpt pg1
VPT 2:
occam(config-eps)# mode vpt pg2
5 By default, the redundant video feature is enabled, meaning that the VPTs are
configured for more than one video source. If there is only a single source of
video coming into the VPT, enter the no redundant video command:
occam(config-eps)# no redundantvideo
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 208 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring BLCs On an Aggregation Ring
Note: Configuration changes do not take effect until after exiting EPS
Configuration Mode.
Note: Configuration changes do not take effect until after exiting EPS
Configuration Mode.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 209 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Interconnect on a VPT on an Aggregation Ring
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 210 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Interconnect on a VPT on an Aggregation Ring
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 211 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPT Ethernet Interface as a Path Group Participant
INTERFACE B
INTERFACE A
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 212 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPT Ethernet Interface as a Path Group Participant
6 Repeat steps 2 through 5 for other interfaces on this VPT that you wish to
configure as path group participants.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 213 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS Interface on an Aggregation Ring
MAIN
AGGREGATION
RING
) 6450 VPS1
PASSTHROGH
0 VPS 5 INTERFACE
6450 VPS 2
VPS 6
SUBTENDED
AGGREGATION
RING A
(WEST)
0 VPS 7
6450 VPS 8
3 Specify the EPS path(s) the interface should participate with as “ring all”. This is
the option that is used for normal conditions and configures the interface to
listen to both path groups, participating on the preferred path group:
occam(config-if-eth)# eps ring all
OR
occam(config-if-xg)# eps ring all
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 214 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS Interface on an Aggregation Ring
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 215 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS Interface on a Subtended Aggregation Ring
MAIN
AGGREGATION
BLC 1 RING
ACCESS
BLC 2
RING 1
(WEST-SALEM) 6450 VPS1 SUBTENED
AGGREGATION
RING
6450 VPS 5 INTERFACE
6450 VPS 7
6450 VPS 8
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 216 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS Interface on a Subtended Aggregation Ring
In the example shown in Figure 11-7, the interface off of VPS1 should be config-
ured for PG1. If the Ring Profile “west” is attached to the interface, the
command should be as follows:
occam(config-if-xg)# eps ring pg1 west
In the example shown in Figure 11-7, the interface off of VPS2 should be
configured for PG2. If the Ring Profile “west” is attached to that interface, the
command should be as follows:
occam(config-if-xg)# eps ring pg2 west
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 217 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS Interface on a Subtended Aggregation Ring
6450 VPS 5
B
6450 VPS 2
C
6450 VPS 6
D
SUBTENDED
AGGREGATION
RING A (WEST)
E H
6450 VPS 7 6450 VPS 8
F G
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 218 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS Interface on a Subtended Aggregation Ring
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 219 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Access-Ring
Configuring an Access-Ring
Configuring a VPS On an Access-Ring
Note: VPS 5 and VPS6 in the figure below are configured as VPSs but function as
VPTs for Access Ring1. Therefore, when the show eps map command is issued on
the BLCs in Access Ring 1, VPS 5 and VPS 6 will show up as VPTs.
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
occam(config)#
For example, in Figure 11-9 below, BLC 1 and BLC 2 should be configured with
the command:
occam(config-eps)# ring path preference pg1
MAIN
AGGREGATION
BLC 1 RING
PG 1
ACCESS
BLC 2
RING 1
(WEST-SALEM) 6450 VPS1
6450 VPS 7
6450 VPS 8
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 220 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Access-Ring
Note: If the show eps map command is entered on BLCs , VPSs 5 and 6 will be
identified as VPTs because they function as VPTs for Access Ring 1.
Figure 11-10: VPS Access-Ring Interfaces Off an Aggregation Ring
MAIN
AGGREGATION
BLC 1 RING
ACCESS-RING
INTERFACE
ACCESS
BLC 2
RING 1
(WEST-SALEM) 6450 VPS1
6450 VPS 7
6450 VPS 8
In the example shown in Figure 11-7, the interface off of VPS5 should be config-
ured for PG1. If the Access-Ring Profile “west-salem” is attached to the
interface, the command should be as follows:
occam(config-if-xg)# eps ring pg1 west-salem
In the example shown in Figure 11-7, the interface off of VPS6 should be config-
ured for PG2. If the Ring Profile “west-salem” is attached to that interface, the
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 221 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Access-Ring
Note: The load network command must be the first command entered on the BLC.
Note: The load network command may not be used on aggregation BLCs to
configure EPS aggregation rings.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 222 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Access-Ring
MAIN
A
AGGREGATION
BLC 1 RING
B
C
ACCESS
BLC 2
RING 1
D 6450 VPS1
(WEST-SALEM)
6450 VPS 5
E
BLC 3 6450 VPS 2
F
6450 VPS 6
SUBTENDED
AGGREGATION
RING A (WEST)
3 Configure the Ethernet interface ring option as “all”, listening to both path
groups and participating on the preferred path group:
occam(config-if-eth)# eps ring all
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 223 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring an Access-Ring
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 224 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS or VPT Ethernet Interface for Untagged Traffic
3 Configure the interface to receive and forward traffic with 802.1q VLAN tags:
occam(config-if-eth)# eps access untagged {VLAN-ID-number}
OR
occam(config-if-xg)# eps access untagged {VLAN-ID-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 225 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic
Limit of 768 tag entries (access profiles, tagged ports, access-ring profile and
ring profiles) combined in all of the profiles in the EPS domain
Per BLC:
You must assign resource ports (EPS Keys) to each tagged profile on each blade.
Note: Make sure that you do not configure more VLAN tags than the BLC and EPS
domain can support.
3 [Optional] Define the VLAN for untagged packets entering a tagged interface
with the command untagged vlan. Map the internal EPS VLAN ID (aggregation
ring: 2-100; access ring: 2-122) to an untagged user VLAN ID (a number
between 1-4094):
occam(config-tagged-profile)# untagged vlan {2-122} {1-4094}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 226 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic
4 [Do one or more times.] Define the VLAN for tagged packets entering a tagged
interface with the command tagged vlan. Map the internal EPS VLAN ID to
tagged user VLAN ID:
occam(config-tagged-profile)# tagged vlan {2-122} {1-4094}
Repeat this command for each VLAN mapping you wish to create. In any case
where a value has already been defined, the new value will override the old.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 227 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic
2 Configure the interface to receive and forward traffic with 802.1q VLAN tags:
occam(config-if-eth)# eps access tagged {profile}
OR
occam(config-if-xg)# eps access tagged {profile}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 228 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic
Example Configuration
In this example a BLC 6440 is configured to map EPS domain VLANs 2-6 to user
domain VLANs 202-206 on an 802.1q trunk. Furthermore, it maps all ingress
untagged traffic onto EPS domain VLAN 10 and sends any egress traffic from EPS
domain VLAN 10 out untagged.
The tagged profile is named “vlan-map” and applied to interface 7.
tagged-profile vlan-map
untagged vlan 10 1
tagged vlan 2 202
tagged vlan 3 203
tagged vlan 4 204
tagged vlan 5 205
tagged vlan 6 206
interface Ethernet 7
eps access tagged vlan-map
no shutdown
exit
tagged-profile site1:
eps vlan user vlan
2 202
3 203
4 204
5 205
6 206
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 229 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring TLS
Configuring TLS
EPS supports TLS, also known as “Double Q Tagging, “VLAN stacking” and “Q-in-Q”.
TLS provides the ability to transparently transport LAN services through the Occam
BLC Network from one Ethernet port to any other Ethernet port ONLY on the
following BLCs:
BLC 6150-01
BLC 6212-02
BLC 6244
BLC 6246
BLC 6312
BLC 6314
BLC 6450
BLC 6440-01
BLC 6640-01
2 Use the default-prio {0-6} command to configure the default priority of the
TOS/DSCP bits for the Ethernet interface.
3 Use the priority tagged command to derive the priority from the incoming tag.
For example, if the incoming tag has a priority tag of 7, the tag is transparently
mapped to 6 on the EPS tag. The original tag is not modified.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 230 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring TLS
Configuring TLS
TLS is configured with the command eps access doubleqtag vlan {2-122} from
Ethernet Interface Configuration mode. When this command is issued on a VLAN,
an outer 802.1Q tag is added to the customer's 802.1Q tag. This tag is gets stripped
before the frame is sent out. The forwarding decision is thus made based on the
outer 802.1Q tag, rather than the inner 802.1Q tag. This outer 802.1Q tag
essentially serves as a transport VLAN and the customer VLAN tags are preserved as
the inner 802.1Q tag VLAN tag.
1 Enter Ethernet Interface or 10 GigE Interface Configuration mode and specify
an interface number:
occam(config)# interface ethernet {Ethernet-interface-number}
OR
occam(config)# interface xg {XG-interface-number}
Note: Since all management traffic for the BLC network runs on VLAN 2, Occam
Networks recommends that it not be used for TLS.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 231 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring TLS
Traffic Ethernet Port Type Ethernet Port Type Traffic Stream Out
Stream In Inbound Outbound
Tagged VLAN Double Tagged Port Double Tagged Port Tagged VLAN 50
50 VLAN 50 VLAN 50
Tagged VLAN Double Tagged Port Double Tagged Port Tagged VLAN 99
99 VLAN 50 VLAN 50
Tagged VLAN Double Tagged Port Untagged port VLAN Tagged VLAN 99
99 VLAN 50 50
Untagged Double Tagged Port Double Tagged Port Untagged
VLAN 50 VLAN 50
Untagged Double Tagged Port Untagged port VLAN Untagged
VLAN 50 50
Untagged Untagged port VLAN Double Tagged Port Untagged
50 VLAN 50
Tagged VLAN Untagged port VLAN Double Tagged Port No traffic
99 50 VLAN 50
Tagged VLAN Double Tagged Port Tagged No traffic
99 VLAN 50
Untagged Untagged port VLAN Untagged port VLAN Untagged
50 50
Untagged Double Tagged Port Tagged No traffic
VLAN 50
Tagged VLAN Double Tagged Port Tagged VLAN transla- No traffic
99 VLAN 50 tion 50 to 99
Untagged Double Tagged Port Tagged VLAN transla- No traffic
VLAN 50 tion 50 to 99
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 232 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring TLS
2 Enter TLS Profile Configuration Mode and create a TLS Profile with a specific
name:
occam(config-tls-profile)# tls-profile {profile-name}
3 Define the default VLAN ID for the VLAN to which the TLS Profile is attached. All
traffic with no source IP address will be mapped to this VLAN:
occam(config-tls-profile)# eps vlan {VLAN-ID-number}
5 Assign a rate-limiting policy map to the TLS profile as an output policy, rate-
limiting all unicast traffic coming to the subscriber from the BLC. Specify the
policy map by name:
occam(config-tls-profile)# service-policy output {policy-map-
name}
6 Assign a rate-limiting policy map to the TLS profile as an input policy, rate-
limiting all unicast traffic coming to the BLC from the subscriber. Specify the
policy map by name:
occam(config-tls-profile)# service-policy input {policy-map-
name}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 233 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring TLS
9 occam(config-if-eth)# exit
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 234 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Configuring a BLC to Run EPS with Non-EPS Devices
4 Specify the preferred EPS path group (pg), choosing pg1 or pg 2. The default
path group is pg1:
occam(config)# eps ring path preference {pg1, pg2}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 235 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Ethernet Loop Detection (ELD) Configuration
ELD Operation
Whenever ELD detects a loop condition and blocks an interface from entering the
forwarding state it generates a local BLC alarm and associated RMI events for EMS.
In addition a message is sent to the console and to syslog. Clearing of the loop
condition or changing the configuration of the interface in such a way to remove
the loop condition clears the local BLC alarm and sends a clearing RMI event to the
EMS.
When an interface’s administrative state is “up”, the CLI will disable and enable the
interface when a VLAN configuration is changed. The interface will be disabled
BEFORE the VLAN change and enabled AFTER the VLAN change.
If a VLAN is misconfigured, the CLI toggle will force an ELD test of that interface.
If a VLAN is reconfigured to clear a loop, the CLI toggle will clear the alarms on
both (ELD) BLCs.
If a cable is plugged into the wrong interface causing a loop, unplugging the
cable will clear the alarm on both BLCs.
Loop Detection
When a loop is detected, the port is disabled and an alarm is generated. The port
will not automatically be re-enabled when the loop is cleared; the user must enter
the command no shutdown on the port to enable it and to clear the alarm.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 236 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Ethernet Loop Detection (ELD) Configuration
or
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 237 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Ethernet Loop Detection (ELD) Configuration
Use the command show eps to verify if ELD is enabled or disabled. (Sample output
of this command may be found in the Occam Networks publication Command
Reference Guide or Appendix A, Configuring EPS, in the manual BLC 6000 System
Overview.
The last line of output will read:
EPS loop detection is enabled
or
EPS loop detection is disabled
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 238 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Displaying Information About Your EPS Configuration
mode VPT
vpt path group 1
global mask 0x400
timer interval(ms) 4
heartbeat path group 1
ring ID 0
interval(ms) 4
speed(Mbps) 1000
sequence 43083
timestamp 0x000148076
origin MAC 00:02:86:00:92:C9
tx packets 3319884
tx bytes 345267936
occam#exit
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 239 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Displaying Information About Your EPS Configuration
The following example shows sample output from this command for a VPS on an
aggregation ring:
occam# show eps
Device Mode: VPS
eps ring path preference: PG1
Information about the show eps fields when the BLC is configured to be a VPS:
Field Description
mode Shows if the BLC is a VPT or a VPS. Should say VPS.
path group Path Group 1 or Path Group 2. The PG1 or PG2 column
headers are used to display Path Group information.
current path group Current Path Group of the VPS BLC. Should be 1 or 2.
default path group Path Group specified by the command
eps ring path preference.
heartbeat state UP or DOWN state determined by the presence or absence
of a Path Group heartbeat.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 240 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Displaying Information About Your EPS Configuration
Field Description
EPS state EPS states that include fault hysteresis and reversion
information:
UNKNOWN - A heartbeat has not been received on this
Path Group
DOWN - A heartbeat has been detected but not recently.
UP_FAULT_STATE - The heartbeat has been present for
less than 1 minute.
UP_REVERSION_STATE- The heartbeat has been present
for more than 1 minute but less than two minutes. This
is the pre-reversion state.
UP_ACTIVE - The heartbeat is up and stable. This Path
Group is ready to sustain active traffic.
global mask An internal EPS mask that defines the Path Group
boundaries.
The EPS mask for aggregation rings is 0x400
The EPS mask for access-rings is 0x80.
time since last Amount of time in milliseconds since the reception of the
heartbeat (ms) last heartbeat on this Path Group.
generation interval (ms) Interval in milliseconds between heartbeats as indicated
inside the heartbeat.
path speed
XGigEthernet
sequence number Sequence number received in the last heartbeat for this PG.
sequence misses How many out of sequence heartbeat packets were
received (missed heartbeats)
origin mac MAC address of the VPT sending the heartbeat on this Path
Group.
origin MC DEST Multicast Address on the heartbeat on this Path Group.
source dev Source device (interface) that the heartbeat for this Path
Group was received on.
rx last interval Number of heartbeats received on this Path Group during
the last polling interval (20 ms).
rx packets Total number of heartbeats received on this Path Group
rx bytes Total number of heartbeat bytes received on this Path
Group.
fault counter Total number of faults that have occurred on this Path
Group. Faults are only counted on the current Path Group.
For example, a PG2 BLC does not care about PG1 heartbeat
failures.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 241 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 11: Configuring an EPS Aggregation Ring Network
Displaying Information About Your EPS Configuration
Field Description
fault subscribers Number of subscribers affected by the last fault (e.g.,
downstream subscriber’s PCs). During a fail-over a broad-
cast is sent out on the new Path Group on behalf of the
subscribers. This educates all switches of the new path on
the ring to the subscribers.
fault access
fault actual (ms) EPS measures the time it takes for a fail-over sequence to
complete. The time is measured from the reception of the
last heartbeat to the completion of fail-over operations. It
is typically 30 or 40 ms.
fault complete actual (ms)
poll interval (ms) Interval at which the BLC polls for heartbeats on a Path
Group. This should be 8 ms for aggregation rings and 20 ms
for access-rings.
reversion hysteresis (sec) Amount of time after the fault hysteresis state has cleared
the alarm that the VPS will take to revert back to its
preferred Path Group.
Use the show eps map ip {ip-node-address} command to access another BLC by
IP address and displays the EPS type for each port on the remote blade. Enter the
command and an IP address of a remote BLC.
The following shows sample output for the show eps map ip command:
occam# show eps map ip 192.168.21.111
Port Media Type State | Intfc-id Ip Type Mode Chassis Product Mac address age
2 copper ---- invalid | fff/15/12 192.168.21.105 PG1 VPS 1 BLC_6640 00:02:86:00:05:27 2 days,5:23
3 copper PG2 valid | 4c8/7/4 192.168.21.136 ALL VPS 12 BLC_6640 00:02:86:00:06:91 25 sec
5 copper PG2 valid | fff/15/2 192.168.21.20 PG1 VPT 1 BLC_6640_01 00:02:86:00:2a:4b 20 sec
6 copper INTC valid | fff/15/6 192.168.21.20 INTC VPT 1 BLC_6640_01 00:02:86:00:2a:4b 20 sec
8 fiber PG2 unknown |
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 242 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Introduction
Chapter 12
Configuring Subtended EPS
Access-Rings with Ethernet Links
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Configuring a Subtended Access Ring With an Ethernet Link. . . . . . . . . . . . . . . . 244
Introduction
This chapter describes how to configure subtended EPS Access-Rings.
Please read the following chapters for more information about configuring EPS:
Chapter 10, Ethernet Protection Switching (EPS) Overview on page 179 provides an
overview of EPS.
Chapter 11, Configuring an EPS Aggregation Ring Network on page 199 provides
information about configuring an EPS aggregation network.
Chapter 13, Configuring EPS Over MLPPP Links on page 253 provides information
about how to configure EPS over MLPPP links.
Chapter 15, Rate Limiting on Ethernet and XG Interfaces on page 297 provides
information about how to configure rate limiting on an Ethernet or XG interface
for ingress and egress traffic in Mbps.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 243 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
Aggregation Ring 1
VPS 1 VPS 2
A F
PG 1 PG 2
"Heartbeat" "Heartbeat"
E
VPS 3 Access Ring VPS 5
Path
D K Group 2
"Heartbeat"
PG 2
"Heartbeat"
PG 1
"Heartbeat"
PG 1
"Heartbeat" K
B C VPS 7
VPS 4 Subtended
J
Access Ring
G
Path
Group 1 H I
"Heartbeat"
VPS 6
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 244 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
The PG1 heartbeat travels around the Access Ring and enters VPS 4 on Interface
B. This PG1 heartbeat exits out two interfaces on VPS 4: interface C and interface
G.
The PG 1 heartbeat that exits out of interface C continues around the Access
Ring and exits to the aggregation ring on VPS 2 on interface F.
The PG 1 heartbeat that exits out of interface G continues around the
Subtended Access Ring and exits to the Access Ring on VPS 5, interface K.
PG2 2 acts in a similar manner in the opposite direction. This allows both the Access
Ring and the Subtended Access Ring to have heartbeats.
Interfaces that are set to “ring pg1” or “ring pg2” will only pass traffic on the
designated path group. All traffic on the other path group is dropped, preventing
redundant heartbeats.
VPS’s on the rings that are configured to participate on both path groups pass on
heartbeats from path group 1 and path group 2.
Note: Because VPS 1 and VPS 2 are configured as VPSs but function as VPTs for
Access Ring 1, if the show eps map command is entered on these BLCs they will be
identified as VPTs.
Global and interface configuration steps for Access Ring 2 are outlined in the
following section.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 245 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 246 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
2 Configure this Ethernet interface to participate with PG 1. Note that you must
configure the interface to participate with the PG coming out of the head-end
VPS it is closest to (in this case VPS 1):
occam(config-if-eth)# eps ring pg1
or
occam(config-if-xg)# eps ring pg1
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 247 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 248 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
2 Configure the interface to participate with PG 2. Again, note that you must
configure the interface to participate with the PG coming out of the head-end
VPS it is closest to (in this case VPS 2):
occam(config-if-eth)# eps ring pg2
or
occam(config-if-xg)# eps ring pg2
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 249 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
4 Select the ring path preference as PG 1, as this VPS is closer to VPS 4 (PG1) than
VPS 5 (PG2):
occam(config-eps)# ring path preference pg 1
4 Select the ring path preference as PG 2, as this VPS is closer to VPS 5 (PG 2) than
VPS 4 (PG1):
occam(config-eps)# ring path preference pg 2
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 250 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
Configuration Steps For Ethernet Interfaces “H” and “I” on VPS 6 and Interfaces
“J” and “K” on VPS 7
Interfaces H, I, J and K in Figure 12-1 have the same configuration steps.
1 Enter Ethernet or XG Configuration mode and specify an Ethernet interface to
configure:
occam(config)# interface ethernet {interface-number}
or
occam(config-if-xg)# interface xg{interface-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 251 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links
Configuring a Subtended Access Ring With an Ethernet Link
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 252 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Introduction
Chapter 13
Configuring EPS Over MLPPP Links
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Configuring VLAN Untagged Traffic Over MLPPP . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Configuring a Subtended EPS Ring with MLPPP. . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Introduction
T1 ports not assigned to CES or DS0 cross connects may be configured for MLPPP
on the following BLCs:
EPS Configuration
This chapter provides information about configuring EPS over MLPPP links.
Please read the following chapters for more information about configuring EPS:
Chapter 10, Ethernet Protection Switching (EPS) Overview on page 179 provides an
overview of EPS.
Chapter 11, Configuring an EPS Aggregation Ring Network on page 199 provides
information about configuring an EPS aggregation network.
Chapter 12, Configuring Subtended EPS Access-Rings with Ethernet Links on page
243 provides information about how to configure subtended EPS access rings.
Chapter 15, Rate Limiting on Ethernet and XG Interfaces on page 297 provides
information about how to configure rate limiting on an Ethernet or XG interface
for ingress and egress traffic in Mbps.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 253 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Introduction
In applications involving video distribution, BLC blades that serve as "book ends"
in slots 1 and 12 provide critical IGMP packet handling. If any blade in a chassis
is supporting video on an interior slot or video is supported on any subtended
ring from the chassis, MLPPP should be restricted to two (2) member links with
header compression enabled or four (4) member links with header compression
disabled.
The BLC 6440 and 6660 provide for up to eight (8) MLPPP member links. With
header compression enabled, the first sixty-four (64) voice calls will have their
RTP headers compressed. The remaining calls will be transported uncompressed.
Exceeding the capacity of an MLPPP bundle with additional voice calls will cause
voice quality impairments.
The maximum number of voice calls supported over an MLPPP bundle with
header compression disabled is 80.
The maximum number of voice calls supported over an MLPPP bundle with
header compression enabled is 64.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 254 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Introduction
One of the PPP (T1) links (NOT the master T1 link) is manually stopped.
Note: When a T1 fails in an MLPPP bundle, the entire MLPPP bundle itself does not
need to restart. However, it takes a few seconds (less than three seconds) before
the failure is recognized and EPS packets continue to flow. This may be on the
active EPS path which can result in an EPS Path fall-over even though the MLPPP
bundle does not restart.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 255 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Introduction
Figures 13-1 and 13-2 show legal and illegal EPS rings configured with a T1/MLPPP
link:
VPT 1 VPT 2
Path Path
Group 1 Group 2
"Heartbeat" "Heartbeat"
VPS VPS
MLPPP
VPS VPS
VPT 1 VPT 2
Path Path
Group 1 Group 2
"Heartbeat" "Heartbeat"
VPS VPS
MLPPP
VPS VPS
Figure 13-2 is an illegal EPS ring because VPS 1 has two MLPPP groups between it
and VPT2. In addition, VPS 4 has the same problem in the other direction.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 256 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring VLAN Untagged Traffic Over MLPPP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 257 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring VLAN Untagged Traffic Over MLPPP
16 Repeat steps 12 through 16 for any other T1 interfaces you wish to add to the
multilink group.
19 Confirm your multilink configuration. Sample output from these commands are
in the Command Reference Guide:
occam# show interfaces multilink [multilink-id-number]
occam# show interfaces multilink summary
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 258 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 259 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
Interfaces A and B:
"ring interconnect"
"igmp passthrough"
VPT 1: VPT 2:
"mode vpt pg1" "mode vpt pg2"
A B
Interface C: Interface L:
"eps ring pg1" VPT 1 VPT 2 "eps ring pg1"
"igmp host" "igmp host"
C L
PG 1 PG 2
Interfaces
F I Interfaces
D, E, F, and G: H, I, J and K:
VPS 2 VPS 3 " eps ring all"
" eps ring all"
"igmp passthrough" G H "igmp passthrough"
M T
MLPPP
MLPPP
Interfaces
O, P, Q and R:
N " eps ring all"
"igmp passthrough"
S
VPS 5 Et t
VPS 7
VPS 5 and 6: he ne R VPS 7:
O rn
et h er
"mode vps" Et "mode vps"
"ring path "ring path
preference pg1" P VPS 6 Q preference pg2"
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 260 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
Figure 13-4: Clocking on a Subtended EPS Ring with Two MLPPP Links
VPT 1
NSP Transmitter:
"network-clock-select primary serial 2"
"nsp mode tx 5"
NSP
CLOCK
VPT 1 VPT 2
SOURCE
VPS 1 VPS 4
RING 1
MLPPP
RING 2
Interface N Interface S
(Multilink VPS 5 (Multilink
Group). NSP Transmitter: Group).
Each T1 "network-clock-select Each T1
interface in primary serial 1" interface in
multilink "nsp mode tx7" multilink
group: group:
"service- VPS 5 Et VPS 7 "service-
he et
module t1 rn rn module t1
et the
clock source E clock source
line" line"
VPS 6
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 261 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 262 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
VPT 1
In Figures 13-3 and 13-4 VPT 1 is an NSP transmitter:
1 Enter EPS Configuration Mode:
occam(config)# eps
2 Select VPT as the EPS mode for the BLC and configure it for PG 1. VPS is the
factory default mode:
occam(config-eps)# mode vpt pg1
8 (Optional) Set the NSP application’s DSCP value for packets that it generates.
The parameters are between 0 and 63. This command has no effect on packets
that the NSP application receives from peer applications and takes effect imme-
diately. It is described more fully in Chapter 41, Differentiated Services (Diffserv)
on page 733:
occam(config)# ip diffserv dscp protocol NSP {0-63}
Interface A
1 Enter Ethernet Configuration mode and specify an Ethernet interface number.
For example:
occam(config)# interface ethernet {interface-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 263 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
Interface C
In Figure 13-3 the heartbeat from VPT 1 exits out of interface C, ending at VPT 2.
This enables Ring 1 to have a heartbeat on path group 1.
1 Enter Ethernet Configuration mode and specify an Ethernet interface number.
For example:
occam(config)# interface ethernet {interface-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 264 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
VPT 2
1 Enter EPS Configuration Mode:
occam(config)# eps
2 Select VPT as the EPS mode for the BLC and configure it for PG 2. VPS is the
factory default mode:
occam(config-eps)# mode vpt pg1
Interface B
1 Enter Ethernet Configuration mode and specify an Ethernet interface number.
For example:
occam(config)# interface ethernet {interface-number}
Interface L
The heartbeat from VPT 2 exits out of interface L, ending at VPT 1, enabling Ring 1
to have a heartbeat on path group 2:
1 Enter Ethernet Configuration mode and specify an Ethernet interface number.
For example:
occam(config)# interface ethernet {interface-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 265 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
VPS 1
1 Enter EPS Configuration Mode:
occam(config)# eps
Interfaces D and E
In Figure 22-3 the configuration steps for interfaces D and E are the same:
Interface D exits VPS 1 and connects VPS 1 to VPT 1 on Ring 1.
1 Interface E exits VPS 1 and connects VPS 1 to VPS 2 on Ring 1.
1 Enter Ethernet Configuration mode and specify an Ethernet interface to
configure as interface D or E:
occam(config)# interface ethernet {ethernet-interface}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 266 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
VPS 2
1 Enter EPS Configuration Mode:
occam(config)# eps
Interfaces F and G
In Figure 22-3 the configuration steps for interfaces F and G are the same:
Interface F exits VPS 2 and connects VPS 2 to VPS 1 on Ring 1.
Interface G exits VPS 2 and connects VPS 2 to VPS 3 on Ring 1.
1 Enter Ethernet Configuration mode and specify an Ethernet interface to
configure as interface F or G:
occam(config)# interface ethernet {ethernet-interface}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 267 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 268 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
16 Repeat steps 13 through 16 for any other T1 interfaces you wish to add to the
multilink group.
VPS 3
1 Enter EPS Configuration Mode:
occam(config)# eps
Interfaces H and I
In Figure 22-3 the configuration steps for interfaces H and I are the same:
Interface H exits VPS 2 and connects VPS 2 to VPS 1 on Ring 1.
Interface I exits VPS 2 and connects VPS 2 to VPS 3 on Ring 1.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 269 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 270 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 271 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
16 Repeat steps 13 through 16 for any other T1 interfaces you wish to add to the
multilink group.
VPS 4
1 Enter EPS Configuration Mode:
occam(config)# eps
Interfaces J and K
In Figure 22-3 the configuration steps for interfaces J and K are the same:
Interface J exits VPS 4 and connects VPS 4 to VPS 3 on Ring 1.
Interface K exits VPS 4 and connects VPS 4 to VPT 1 on Ring 1.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 272 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
VPS 5
1 Enter EPS Configuration Mode:
occam(config)# eps
7 (Optional) Set the NSP application’s DSCP value for packets that it generates.
The parameters are between 0 and 63. This command has no effect on packets
that the NSP application receives from peer applications and takes effect imme-
diately. It is described more fully in Chapter 41, Differentiated Services (Diffserv)
on page 733:
occam(config)# ip diffserv dscp protocol NSP {0-63}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 273 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
6 Specify the clock source for the T1 interface as the line (loop-timed) clock.
Remember, subtended MLPPP BLCs clock via their T1 line and not via NSP:
occam(config-if-ser)# service-module t1 clock source line
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 274 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
17 Repeat steps 11 through 16 for any other T1 interfaces you wish to add to the
multilink group.
18 Select a T1 interface port number as the source for clocking for VPS 5. For
example, as shown in Figure 22-4:
occam(config)# network-clock-select primary serial 1
Interface O
1 Enter Ethernet Configuration mode and specify an Ethernet interface number.
For example:
occam(config)# interface ethernet {interface-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 275 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
VPS 6
7 Enter EPS Configuration Mode:
occam(config)# eps
Interfaces P and Q
In Figure 22-3 the configuration steps for interfaces D and E are the same:
Interface P exits VPS 6 and connects VPS 6 to VPS 5 on Ring 2.
Interface Q exits VPS 6 and connects VPS 6 to VPS 7 on Ring 2.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 276 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
VPS 7
1 Enter EPS Configuration Mode:
occam(config)# eps
Interface R
1 Enter Ethernet Configuration mode and specify an Ethernet interface to
configure as interface P or Q:
occam(config)# interface ethernet {ethernet-interface}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 277 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
6 Specify the clock source for the T1 interface as the line (loop-timed) clock.
Remember, subtended MLPPP BLCs clock via their T1 line and not via NSP:
occam(config-if-ser)# service-module t1 clock source line
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 278 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
17 Repeat steps 17 through 20 for any other T1 interfaces you wish to add to the
multilink group.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 279 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 13: Configuring EPS Over MLPPP Links
Configuring a Subtended EPS Ring with MLPPP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 280 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Introduction
Chapter 14
Ethernet Subscriber Interfaces
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
VLAN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Defining a Unicast Rate Limiting Policy Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Configuring an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Configuring an Ethernet Subscriber Interface and an Ethernet Service. . . . . . . . 292
Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Introduction
This chapter describes how to configure Ethernet fiber interfaces on the BLC 6312
and BLC 6314 Optical Line Termination (OLT) blades as subscriber facing interfaces
that connect to Occam Networks line of Optical Network Terminals (ONTs) at
customer premises. Please refer to Occam Networks’ ONT Installation and
Configuration Guides for information about configuring ONTs.
EPS Configuration
Please read the following chapters for more information about configuring EPS in
a BLC network:
Chapter 10, Ethernet Protection Switching (EPS) Overview on page 179 provides an
overview of EPS.
Chapter 11, Configuring an EPS Aggregation Ring Network on page 199 provides
information about configuring an EPS aggregation network.
Chapter 12, Configuring Subtended EPS Access-Rings with Ethernet Links on page
243 provides information about how to configure subtended EPS access rings.
Chapter 13, Configuring EPS Over MLPPP Links on page 253 provides information
about how to configure EPS over MLPPP links.
Chapter 15, Rate Limiting on Ethernet and XG Interfaces on page 297 provides
information about how to configure rate limiting on an Ethernet or XG interface
for ingress and egress traffic in Mbps.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 281 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Chapter Overview
Chapter Overview
Ethernet subscriber ports are configured by creating access profiles and attaching
them to Ethernet services. Up to five Ethernet services may be configured on a
subscriber interface. There are no default Ethernet services.
In detail, the steps to configure an Ethernet subscriber port are as follows:
(Optional) First, configure a policy map to rate limit unicast traffic on a VLAN to
a specified rate in Kbps. Policy map configuration is described on page 286.
Second, configure an access profile for the Ethernet service. Ethernet access
profile configuration is described on page 288. Configure the following within
an access profile
Define the EPS (network) VLAN.
Apply the policy map to the access profile as input and output service policies,
rate limiting unicast traffic coming to and from the subscriber
IGMP parameters
IPSM parameters, including DHCP and ARP mode options, broadcast traffic
policing (blacklisting) and the number of MAC addresses that are allowed.
Enable or disable MAC address learning on the interface to which the profile
is attached.
Specify the maximum number of dynamic MAC addresses that are allowed to
pass through a VLAN on an Ethernet subscriber interface.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 282 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Chapter Overview
(Optional)
Specify subscriber Configure an
Define MAC/IP
(ONT) VLAN specified Ethernet service
association
Up to five Ethernet
services may be attached
to each Ethernet subscriber
port
Ethernet interface
configured as a
subscriber interface
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 283 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
VLAN Mapping
VLAN Mapping
Within the BLC EPS domain VLAN ID’s should be set as follows:
As traffic leaves the BLC and goes out an Ethernet interface toward the ONT the
BLC muxes any multicast traffic on VLAN 3 over to VLAN 6.
As multicast traffic enters the BLC from the ONT it is moved from VLAN 6 to VLAN 3.
Traffic leaving the ONT and going toward the subscriber is untagged.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 284 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
VLAN Mapping
PSTN
COT
Internet
Video
Central Office Headend
VPS on PG2
VOICE-VLAN 2
VPT on PG1
MULTICAST TRAFFIC-VLAN 3
BLC 6312
DATA-VLAN 4 BLC 6312 VPS on PG1
VPS on PG1
VIDEO UNICAST AND
BROADCAST TRAFFIC (AKA STB
CONNECTIONS)-VLAN 6
VLAN IDs LEAVING BLC
NETWORK:
VOICE-VLAN 2
DATA-VLAN 4
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 285 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Defining a Unicast Rate Limiting Policy Map
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 286 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Defining a Unicast Rate Limiting Policy Map
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 287 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Configuring an Access Profile
2 Enter Access Profile Configuration Mode. Create a profile by using the name of
a profile you want to create, or an existing profile you want to modify. Use the
no access-profile command to delete a profile:
occam(config)# access-profile profile-name
3 Define the default VLAN ID for the VLAN to which the access profile is attached.
All traffic with no source IP address will be mapped to this VLAN:
occam(config-access-profile)# eps vlan {2-122}
Note: The command eps vlan defines the EPS VLAN. Use the command match
vlan from Ethernet Service Configuration mode to specify the user ONT VLAN to
which an Ethernet service is attached.
4 (Optional) Configure the port the profile is attached to as a IGMP host to enable
forwarding of IGMP managed multicast traffic to downstream subscriber inter-
faces. This feature is disabled by default. If the IP address is not specified, the
BVI IP address will be used. Use the command no igmp to disable traffic
forwarding:
occam(config-access-profile)# igmp host {IP address}
5 (Optional) Limit the number of groups on the port to which the profile is
attached. The factory default is 255:
occam(config-access-profile)# igmp group-limit {1-255}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 288 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Configuring an Access Profile
6 Configure DHCP mode for snooping, Layer 2 relay or Layer 3 relay. When Layer
2 or Layer 3 relay is configured, the Option 82 parameter may be configured as
well. Please turn to the section DHCP Configuration in Chapter 22, IP Security
Management (IPSM) on page 451 for information about these DHCP configura-
tion options:
occam(config-access-profile)# dhcp mode
{l2Relay|l3Relay|snoop|none}
7 Configure the ARP mode to proxy or none. Please turn to the section ARP Proxy
in Chapter 22, IP Security Management (IPSM) on page 464 for information
about these configuration options:
occam(config-access-profile)# arp mode {proxy|none}
8 Enter the command arp reply gateway if you are configuring ARP proxy in
conjunction with peer to peer traffic blocking. Please turn to the section Peer to
Peer Traffic Blocking in Chapter 22, IP Security Management (IPSM) on page 440
for information about this command:
occam(config-access-profile)# arp reply gateway
9 Configure the maximal acceptable packet rate limit for a protocol from a device
that is associated with the access profile. Please turn to the section Blacklisting
in Chapter 22, IP Security Management (IPSM) on page 469 for information
about this command:
occam(config-access-profile)# blacklist rate
limit{arp|dhcp|igmp} {PPS} {1-30} {1-10} {shutdown|alarm}
10 (Optional) Change the ARP cache timeout from the default value of 15 minutes.
The parameters are from between one and 480 minutes:
occam(config-access-profile)# arp cache timeout {minutes}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 289 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Configuring an Access Profile
13 Assign a rate-limiting policy map to the access profile as an output policy, rate-
limiting all unicast traffic coming to the subscriber from the BLC. Specify the
policy map by name (as described in the section, Defining a Unicast Rate Limiting
Policy Map on page 286):
occam(config-access-profile)# service-policy output {policy-map-
name}
14 Assign a rate-limiting policy map to the access profile as an input policy, rate-
limiting all unicast traffic coming to the BLC from the subscriber. Specify the
policy map by name (as described in the section, Defining a Unicast Rate Limiting
Policy Map on page 286):
occam(config-access-profile)# service-policy input {policy-map-
name}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 290 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Configuring an Access Profile
Note: If the destination profile already exists, its parameters will be overwritten by
the source profile. If you modify the source profile after issuing the access-copy-
profile command, the changes you make do not propagate to the destination
profile.
Note: You can modify the default profile, but you cannot delete it. You cannot
delete a profile that is currently associated with a port.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 291 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Configuring an Ethernet Subscriber Interface and an Ethernet Service
Use the command no match vlan {1-4094} to remove this VLAN association
from an Ethernet Service.
7 (Optional) If you have previously configured an Ethernet service and you wish
to change the static associations you may do so with one of the following
commands:
Remove all static associations:
occam(config-if-eth-service-<1-5>)# delete static associations
8 Optionally, set maximum number of IGMP groups allowed, overriding the IGMP
group limit set in the attached access profile. This command and the other over-
ride access-profile commands may be useful if an access profile is attached to
a large number of ports and a change needs to be made to a small number of
them:
occam(config-if-eth-service-<1-5>)# override access-profile igmp
group-limit {1-255}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 292 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Configuring an Ethernet Subscriber Interface and an Ethernet Service
Configuring the ARP Reply Gateway Setting When Using the ON 2351 Enclosure
Occam Network’s ON 2351enclosure can accommodate four Single Family
Residential ONT electronics. Release 3.0 of the ON 2342 and ON 2343 ONT software
can accommodate up to four Single Family Residential ONTs operating on a single
fiber port from the BLC 6312, BLC 6314 or BLC 6450. The communication is
cascaded from the first ONT to the other three using the second WAN SFP port on
the ONT and either a copper SFP-to-SFP cable assembly or SFP lasers connected via
fiber.
In order to support this cascading of SFR ONT electronics, the ARP messages must
be forwarded from the most remote ONT through the intermediate ONT units to
obtain address translation. The CLI command mdu enable similar functionality as
ARP reply gateway on a port-wide basis. ARP mode proxy and DHCP must to be
enabled per service for this to function correctly. From a user point of view all ARP
requests (even ARPs pertaining to MACs that exist on the same subscriber Ethernet
interface) will all be responded to with the Gateway MAC for security and traffic
control reasons.
Use the CLI command mdu to override the ARP reply gateway configuration set in
Access Profile Configuration Mode, as shown in step 8 in the section Configure IPSM
Parameters on page 289.
BLCs configured for normal ARP-reply-gateway mode without the mdu command
enabled on a service level will drop requests for MACs on the same interface.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 293 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Configuring an Ethernet Subscriber Interface and an Ethernet Service
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 294 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Sample Configuration
Sample Configuration
This is a sample Ethernet subscriber interface configuration that follows the
network example shown in Figure 14-2.
1.Network VLAN
2.ONT VLAN
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 295 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 14: Ethernet Subscriber Interfaces
Sample Configuration
occam(config-if-eth-service-3)# no shutdown
occam(config-if-eth-service-3)# exit
occam(config-if-eth)# no shutdown
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 296 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 15: Rate Limiting on Ethernet and XG Interfaces
Introduction
Chapter 15
Rate Limiting on Ethernet and XG
0
Interfaces
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Configuring Rate Limiting on Egress Ethernet and XG Interfaces. . . . . . . . . . . . . 298
Configuring Rate Limiting on Ingress Ethernet Interfaces. . . . . . . . . . . . . . . . . . . 298
Verifying Your Rate Limiting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Introduction
Rate limiting may be configured on an Ethernet or XG interface by interface basis
for ingress and egress traffic in Mbps (Megabits per second). Additional rate
limiting may be performed on multicast, broadcast and unknown unicast traffic on
an interface by interface basis for ingress traffic in PPS (packets per second)
allowed. This rate limiting helps to prevent multicast, broadcast and unknown
unicast storms which create excessive traffic and degrade network performance.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 297 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 15: Rate Limiting on Ethernet and XG Interfaces
Configuring Rate Limiting on Egress Ethernet and XG Interfaces
subscriber interface, the rate limits are removed. Information about how to
configure rate limiting on a VLAN is described in Chapter 14, Ethernet Subscriber
Interfaces on page 281.
Note: You cannot enter the egress rate limit command from XG Interface
Configuration mode.
The following example configures egress rate limiting on Ethernet interface 3. The
rate limit is set to 150 Mbps:
occam(config)# interface ethernet 3
occam(config-if-eth)# egress rate limit 150
Note: You cannot enter the ingress rate limit command from XG Interface
Configuration mode.
The following example configures ingress rate limiting on Ethernet interface 2. The
rate limit is set to 245 Mbps:
occam(config)# interface ethernet 2
occam(config-if-eth)# ingress rate limit 245
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 298 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 15: Rate Limiting on Ethernet and XG Interfaces
Configuring Rate Limiting on Ingress Ethernet Interfaces
The following example rate limits broadcast frames on Ethernet interface 4. The
rate limit is set to 3500 pps.
occam(config)# interface ethernet 4
occam(config-if-eth)# ingress broadcast rate limit 3500
The following example rate limits broadcast frames on XG interface 1. The rate limit
is set to 4600 pps.
occam(config)# interface xg 1
occam(config-if-xg)# ingress broadcast rate limit 4600
Caution: Do not use this command in a video (Triple Play) network, as it may cause
! some television channels to be dropped
Use the command ingress multicast rate limit {pps} from Ethernet Configuration
mode to rate limit multicast frames on an ingress Ethernet interface. The limit is
specified in packets per second (pps). The accepted range is 0 through 200,000,000
pps. The default is 0 pps, indicating no rate limiting.
Note: You cannot enter the ingress multicast rate limit command from XG
Interface Configuration mode.
The following example rate limits multicast frames on Ethernet interface 8. The rate
limit is set to 3800 pps.
occam(config)# interface ethernet 8
occam(config-if-eth)# ingress multicast rate limit 3800
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 299 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 15: Rate Limiting on Ethernet and XG Interfaces
Verifying Your Rate Limiting Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 300 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 15: Rate Limiting on Ethernet and XG Interfaces
Verifying Your Rate Limiting Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 301 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 15: Rate Limiting on Ethernet and XG Interfaces
Verifying Your Rate Limiting Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 302 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Introduction
Chapter 16
Configuring Link Aggregation
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Configuring a LAG Out Of a VPT That Will Connect To A Head End Router. . . . . 306
Configuring a LAG As an Interconnect Between Two BLC 6001 Chassis . . . . . . . 309
Assigning Ethernet Interfaces To a LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Sample Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Viewing Your LAG Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Introduction
Overview
Occam Network’s Release 5.5 supports Link Aggregation as defined in IEEE Std.
802.3, Clause 43.
Occam’s implementation of Link Aggregation allows two to eight 1 Gig links to be
combined into a single virtual interface, a Link Aggregation Group (LAG). This LAG
may be configured to connect to head-end routers, providing load sharing,
increased bandwidth and link protection. It may also be configured as an
interconnect between two VPT blades loaded in BLC 6001 Chassis.
Figure 16-1 shows an example of LAGs in a BLC network. LAGs 1 and 2 are
connected to a head-end router and LAG 3 is configured as an interconnect. LAG 4
is configured out of a VPS to another router.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 303 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Introduction
HEAD END
ROUTER
LAG 1 LAG 2
"igmp router" "igmp router"
VPT on PG 1 VPT on PG 2
LAG 2
"igmp passthrough"
LAG 4
"igmp host"
VPS on PG 2
ROUTER
LAGs recover if a group member goes down. They support the addition and removal
of link members with only a minor transient traffic interruption.
Link up and down alarms for LAG members are processed as normal alarms. A link
down alarm for a LAG will occur when no remaining members are up. When a
member of a LAG returns to an operational state, a link up alarm will be sent and
the link down alarm will be cleared.
Supported Chassis
BLC 6001 Chassis: No restrictions on any fiber/copper port being configured as
a LAG member.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 304 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Introduction
Supported BLCs
LAG is only supported on the following BLCs:
BLC 6450
BLC 6314
BLC 6312
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 305 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Configuring a LAG Out Of a VPT That Will Connect To A Head End Router
2 Enter LAG Configuration mode and specify a LAG number. Up to four LAGs may
be created:
occam(config)# interface lag {LAG-number}
3 Configure EPS settings on the LAG by enabling one of the following commands:
a Configure the LAG to add an outer tag to a specified VLAN via TLS.
Please see the section Configuring TLS on page 231 in Chapter 11, Configuring
an EPS Aggregation Ring Network for information about how to configure a
tagged profile:
occam(config-if-lag)# eps access doubleqtag vlan {VLAN-number}
OR
b Configure the LAG to map EPS domain VLANS onto a customer switch VLAN
domain. A tagged profile must be created that defines the mapping between
EPS domain VLANs and customer switch VLANs, including only those VLANs
which are required by the customer. Please see the section Configuring a
Tagged Profile on page 226 in Chapter 11, Configuring an EPS Aggregation
Ring Network for information about how to configure a tagged profile:
occam(config-if-lag)# eps access tagged {profile-name}
OR
c Configure the LAG to receive and forward traffic with 802.1q VLAN tags.
LAGs that will transmit to networks nodes that expect untagged Ethernet
frames should be configured with the command “eps access untagged vlan
{VLAN-ID-number}”. A tag with the VLAN ID number is added for any frame
received on that interface, and only packets with that VLAN ID will be trans-
mitted out that interface after the tag field is removed.
Please see the section Configuring a VPS or VPT Ethernet Interface for
Untagged Traffic on page 225 in Chapter 11, Configuring an EPS Aggregation
Ring Network for more information:
occam(config-if-lag)# eps access untagged vlan {VLAN-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 306 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Configuring a LAG Out Of a VPT That Will Connect To A Head End Router
OR
b If the LAG is passing traffic up to routers that are doing the IGMP routing
you may configure the LAG group as an IGMP passthrough group. The
optional IP address parameter is the source IP address for IGMP packets:
occam(config-if-lag)# igmp passthrough {IP-address}
3 Set the maximum allowed number of multicast groups on the LAG, specifying a
number between 1 and 255. The factory default is 255. Use the command no
igmp group-limit to return the command to the default setting:
occam(config-if-lag)# igmp group-limit {1-255}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 307 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Configuring a LAG Out Of a VPT That Will Connect To A Head End Router
The first word is a key, anything after is the value attached to that key. In the
above example, 'router' is the key. You can have several info messages and you
can remove any of them by using the command no info {key}. There is no limit
on the text length, but you cannot use any of the following characters: TAB,
<enter>, '?', '!'.
10 Please turn to the section Assigning Ethernet Interfaces To a LAG on page 314 to
complete your LAG configuration.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 308 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Configuring a LAG As an Interconnect Between Two BLC 6001 Chassis
2 Enter LAG Configuration mode and specify a LAG number. Up to four LAGs may
be created, including the interconnect LAG:
occam(config)# interface lag {LAG-number}
5 Set the maximum allowed number of multicast groups on the LAG, specifying a
number between 1 and 255. The factory default is 255. Use the command no
igmp group-limit to return the command to the default setting:
occam(config-if-lag)# igmp group-limit {1-255}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 309 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Configuring a LAG As an Interconnect Between Two BLC 6001 Chassis
The first word is a key, anything after is the value attached to that key.You can
have several info messages and you can remove any of them by using the
command no info {key}. There is no limit on the text length, but you cannot use
any of the following characters: TAB, <enter>, '?', '!'.
11 Please turn to the section Assigning Ethernet Interfaces To a LAG on page 314 to
complete your LAG configuration.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 310 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Configuring a LAG Out Of a VPS
2 Enter LAG Configuration mode and specify a LAG number. Up to four LAGs may
be created:
occam(config)# interface lag {LAG-number}
3 Configure EPS settings on the LAG by enabling one of the following commands:
a Configure the LAG to add an outer tag to a specified VLAN via TLS.
Please see the section Configuring TLS on page 231 in Chapter 11, Configuring
an EPS Aggregation Ring Network for information about how to configure a
tagged profile:
occam(config-if-lag)# eps access doubleqtag vlan {VLAN-number}
OR
b Configure the LAG to map EPS domain VLANS onto a customer switch VLAN
domain. A tagged profile must be created that defines the mapping between
EPS domain VLANs and customer switch VLANs, including only those VLANs
which are required by the customer. Please see the section Configuring a
Tagged Profile on page 226 in Chapter 11, Configuring an EPS Aggregation
Ring Network for information about how to configure a tagged profile:
occam(config-if-lag)# eps access tagged {profile-name}
OR
c Configure the LAG to receive and forward traffic with 802.1q VLAN tags.
LAGs that will transmit to networks nodes that expect untagged Ethernet
frames should be configured with the command “eps access untagged vlan
{VLAN-ID-number}”. A tag with the VLAN ID number is added for any frame
received on that interface, and only packets with that VLAN ID will be trans-
mitted out that interface after the tag field is removed.
Please see the section Configuring a VPS or VPT Ethernet Interface for
Untagged Traffic on page 225 in Chapter 11, Configuring an EPS Aggregation
Ring Network for more information:
occam(config-if-lag)# eps access untagged vlan {VLAN-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 311 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Configuring a LAG Out Of a VPS
5 Set the maximum allowed number of multicast groups on the LAG, specifying a
number between 1 and 255. The factory default is 255. Use the command no
igmp group-limit to return the command to the default setting:
occam(config-if-lag)# igmp group-limit {1-255}
The first word is a key, anything after is the value attached to that key. . You can
have several info messages and you can remove any of them by using the
command no info {key}. There is no limit on the text length, but you cannot use
any of the following characters: TAB, <enter>, '?', '!'.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 312 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Configuring a LAG Out Of a VPS
12 Please turn to the section Assigning Ethernet Interfaces To a LAG on page 314 to
complete your LAG configuration.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 313 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Assigning Ethernet Interfaces To a LAG
3 Select a LAG number to which you wish to add the Ethernet or XG interfaces.
Up to four LAGs may be configured on a BLC:
occam(config-if-eth)# lag-interface {LAG-number}
OR
occam(config-if-xg)# lag-interface {LAG-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 314 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Sample Configurations
Sample Configurations
Sample Configuration Of a LAG To a Head End Router
This is an example of a simple configuration of a LAG to a head end router. The
occam(config)# interface lag 1
occam(config-if-lag)# eps access tagged router
occam(config-if-lag)# igmp router
occam(config-if-lag)# no shutdown
occam(config-if-lag)# exit
occam(config)# interface xg 1
occam(config-if-xg)# lag-interface 2
occam(config-if-xg)# no shutdown
occam(config-if-xg)# exit
occam(config)# interface xg 2
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 315 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Sample Configurations
occam(config-if-xg)# lag-interface 2
occam(config-if-xg)# no shutdown
occam(config-if-xg)# exit
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 316 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Viewing Your LAG Configuration Settings
show bridge interface lag {1-4}: sample output for this command is shown on
page 317.
show interfaces lag [lag-number]: sample output for this command is shown on
page 318.
Information about LAGs may also be viewed by entering other commands. Some of
these commands are:
show eps
For example:
occam#show bridge interfaces lag 1
Hardware switch MAC Table:
Address Port Static VLAN Path Group Source
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 317 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Viewing Your LAG Configuration Settings
Field Description
LAG # members Shows the configured LAGs and the interfaces
that belong to each LAG
Admin state The administrative state of the LAG and of each
of the interfaces in the LAG.
EPS This column displays different information
Oper state about both the LAG and the interfaces.
EPS: Displays the EPS configuration of the LAG.
The options are tagged, untagged, interconnect
(INTC), dblq 101 (double Q tagged, or TLS).
Oper state: Displays the operational state of the
interface. The options are up or down.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 318 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Viewing Your LAG Configuration Settings
Field Description
IGMP Fwd state This column displays different information
about both the LAG and the interfaces.
IGMP: Displays if the LAG has been configured
as an IGMP router (RTR) or passthrough (PASS)
interface.
Fwd state: Displays if the interface is
forwarding traffic. The options are FWD
(forwarding) or BLK (blocked).
LDBAL Speed This column displays different information
about both the LAG and the interfaces.
LDBAL: Displays the load balancing configura-
tion of the LAG.
Speed: Displays the speed of traffic on the
interface.
Rx pkts The number of packets received on the LAG and
of each of the interfaces in the LAG.
Tx pkts The number of packets transmitted on the LAG
and of each of the interfaces in the LAG.
Rx errs The number of packets received on the LAG and
of each of the interfaces in the LAG displaying
various internal frame or delivery errors.
Tx errs The number of packets transmitted on the LAG
and of each of the interfaces in the LAG
displaying various internal frame or delivery
errors.
Rx % The percent of the number of packets received
on this LAG that are are received on this
interface.
Tx % The percent of the number of packets trans-
mitted on this LAG that are transmitted on this
interface.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 319 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 16: Configuring Link Aggregation
Viewing Your LAG Configuration Settings
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 320 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 17: Configuring Span Powered T1 Lines
Chapter 17
Configuring Span Powered T1 Lines
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
T1 Span Power Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Other T1 Line Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Viewing Your Powered T1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Extra care must be taken when testing any span powered T1 in cabinets
equipped with DSX cross connect with bantam test jacks. Make sure to
turn the power off before plugging any test set into T1 lines.
Occam Networks recommends that you ONLY test span powered T1 line
with 5-pin protectors with test points that can be used to measure
between the Transmit and Receive pairs. Occam Networks strongly recom-
mends that you do NOT use protectors with test points.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 321 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 17: Configuring Span Powered T1 Lines
Introduction
Introduction
The BLC 6246 provides DC power onto T1 lines, which in turn provides power to line
repeaters that extend the line length. The BLC 6246 is also able to loop power
received on the T1 span. Interfaces for span powered T1 lines are disabled by factory
default.
Typically the CO provides power and attempts to maintain a 60 milliamps on the
span powered T1 at all times. Up to 130 Volts may be sent down the T1 line to do
this; the longer the span, the higher voltage on the line.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 322 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 17: Configuring Span Powered T1 Lines
T1 Span Power Commands
Power Commands
Use the following commands to enable or disable a 60mA current source on the
span powered T1 line so as to provide power to line repeaters that will extend the
line length:
SPAN
POWERED
CO R R R
T1 LINE
BLC "A" BLC "B"
RESIDENCE
RT RT
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 323 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 17: Configuring Span Powered T1 Lines
Other T1 Line Configuration Commands
Cause this T1 to receive or not receive clocking from external equipment via
the line:
occam(config-if-serial)# service-module t1 clock source line
occam(config-if-serial)# no service-module t1 clock source
line
Data Coding Enable inverted data coding, changing all 1 bits into 0 bits and all 0 bits into
1 bits:
occam(config-if-serial)# service-module t1 data-coding
inverted
Enable normal data coding, returning data coding to normal. This is the
factory default:
occam(config-if-serial)# service-module t1 data-coding normal
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 324 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 17: Configuring Span Powered T1 Lines
Other T1 Line Configuration Commands
FDL Standard Configure the T1 to use or not use ANSI T1.403 as the FDL standard:
occam(config-if-serial)# service-module t1 fdl ansi
occam(config-if-serial)# no service-module t1 fdl ansi
Configure the T1 to use or not use AT&T TR54016 as the FDL standard:
occam(config-if-serial)# service-module t1 fdl att
occam(config-if-serial)# no service-module t1 fdl att
Configure the T1 to use or not use both ANSI T1.403 and AT&T TR54016 as
the FDL standard:
occam(config-if-serial)# service-module t1 fdl both
occam(config-if-serial)# no service-module t1 fdl both
Configure the T1 to use or not use SLC96 Remote Terminal as the FDL
standard:
occam(config-if-serial)# service-module t1 fdl slc96rt
occam(config-if-serial)# no service-module t1 fdl slc96rt
Framing The service provider determines if SLC-96, Extended Super Frame (ESF), D4
Super Frame (SF) or Unframed format is required for your circuit.
You may also use the “no” form of the command to specify the factory
default:
Occam(config-if-serial)# no service-module t1 lbo
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 325 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 17: Configuring Span Powered T1 Lines
Other T1 Line Configuration Commands
Line Coding Specify the line code. Your T1 service provider determines if your circuit
Format requires alternate mark inversion (AMI) or binary 8 zero substitution (B8ZS)
be configured as the line code. The factory default is B8ZS line code.
Enable or disable “payload” as the local loopback format. When this option
is selected data crosses into the framer in the QFALC chip. It gets reframed
and resynced before it is sent out of the BLC again:
occam(config-if-serial)# service-module t1 local-loopback
payload
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 326 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 17: Configuring Span Powered T1 Lines
Other T1 Line Configuration Commands
Remote/Yellow Remote alarms are transmitted by the BLC when it detects an alarm condi-
alarm tion. A remote alarm is also called RAI (Remote Alarm Indicator) or "yellow"
alarm. An RAI can be received and transmitted if enabled. It is transmitted
when a LOS (loss of signal - also called a "red" alarm). is locally detected. If
received, it indicates the remote end is in red alarm (hence the name
remote-alarm).
A remote alarm condition is transmitted by setting the bit 2 of each time
slot to zero when D4 Super Frame is configured (see the service-module t1
framing command). This is why remote alarms are disabled by default. With
Extended Super Frame configured, the remote alarm condition is signalled
out of band in the facilities data link.
Enables or disables the T1 to use “payload v54” as the remote loopback code
used to transmit or accept CSU loopback requests:
occam(config-if-serial)# service-module t1 remote-loopback
payload v54
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 327 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 17: Configuring Span Powered T1 Lines
Viewing Your Powered T1 Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 328 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Introduction
Chapter 18
Configuring DSL Interfaces
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
ADSL2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
DSL Interface Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Configuring a DSL Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Configuring an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Enabling and Configuring a DSL Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Configuring a DSL Bonding Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Enabling and Configuring Service(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Introduction
This chapter how to configure DSL interfaces on the following BLCs:
ADSL2 Features
Bonding
ADSL2 bonding allows one ATM stream to be split over two ADSL2 lines. Bonding
configuration is described on page 356.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 329 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
ADSL2 Features
In Annex L mode the lower spectrum ADSL signals are enhanced to allow the
modems to maintain synchronization out to greater distances. Depending on the
gauge of the copper plant, those distances can be several thousands feet beyond
the nominal maximum for ADSL. Annex L is enabled on the BLC with Auto and
G.992_3 line protocols. Please see page 334 for information about using the
command dmt operating-mode to configure these line protocols.
Annex M
Annex M is a standard ADSL2 feature that provides for increased upstream rates.
Rates in the range of 2.2M to 3M upstream are achievable depending on the
capabilities of the modem. ADSL Annex M doubles the upstream rate by using of
some of the lower end DS channels (also referred to as tones or bins). Typical Annex
A capable devices use bins 6 - 32 for US traffic and Annex M devices use bins 6-63.
This mode is not negotiated between the two endpoints, so both the DSL interface
on the BLC and the modem need to be configured for Annex M mode. Annex M is
available in conjunction with other ADSL2 features such as bonding and Annex L.
By using this feature you can create symmetric services that are comparable to (or
an improvement) G.SHDSL and dedicated T1 circuits by applying profiles that force
the upstream and downstream rates to the same rate.
Annex M is enabled via the dmt operating-mode command through the DSL
profile. This command is discussed on page 334.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 330 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
ADSL2 Features
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 331 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
DSL Interface Configuration Overview
Configure and enable a DSL bonding group (page 356) or a DSL interface (page
358).
Configure and enable a service and attach the service to a DSL interface or
bonding group page 361).
You may configure the following parameters within a service:
Apply an access profile to the service.
Match the user (ONT) VLAN to the EPS VLAN
Optionally configure a a static MAC/IP address association
Optionally, override the following settings in the attached access profile:
• Configure the maximum number of MAC addresses allowed
• Configure the maximum number of IGMP groups allowed
• Enable or disable MAC learning
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 332 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
DSL Interface Configuration Overview
(Optional)
Specify subscriber Configure a
Define MAC/IP
(ONT) VLAN specified service
association
Configure a DSL
DSL interface profile
or bonding group (Optional if keeping
default settings)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 333 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
The recommended DSL profile for non-video services is shown on page 347.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 334 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Status : disabled
DownShift Interval : 30 sec
UpShift Interval : 30 sec
DSL Line Retransmission Error Recovery :
Status : disabled
Minimum RS Overhead : 1
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 335 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
2 Enter DSL Profile Configuration Mode. Create a profile by using the name of a
profile you want to create, or an existing profile you want to modify. Use the no
dsl-profile command to delete a profile:
Occam(config)# dsl-profile {dsl-profile-name}
3 Use the commands described below in Tables 18-2 through 18-7 to make any
changes you desire to the factory default DSL profile configuration.
5 From Global Configuration Mode, enter DSL Interface Configuration Mode and
specify the interface to which you want to attach the profile:
Occam(config)# interface dsl {dsl-interface-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 336 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
10 Please turn to the section Configuring an Access Profile on page 350 for infor-
mation about how to configure and enable one or more services.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 337 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Note: In this release, if the DSL Line Retransmission Error Recovery feature is
activated then Seamless Rate Adaptation (SRA) is disabled.
Table 18-1: Commands to Configure the DSL Line Retransmission Error Recovery
Feature
Command Description
dmt retransmission Enables the DSL Line Retransmission Error
no dmt retransmission Recovery feature.
The "no" form of this command disables
this feature. This is the factory default
setting.
dmt retransmission reed-solomon{Kbps} Configures the minimum Reed-Solomon
no dmt retransmission reed-solomon correction overhead setting for the DSL
Line Retransmission Error Recovery
feature. The parameters are between 0-
127.
The "no" form of the command disables
this command.
When this command is set to 0, this will
disable Reed-Solomon. Occam Networks
recommends using at least a value of 1.
This parameter has a comparable impact
on the attainable bitrate as the impulse-
noise-protection parameter does when
the Retransmission featureis disabled but
with a better granularity.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 338 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Note: The bitrate values in the following commands must be a number that is a
multiple of 32. If a value is entered that is not a multiple of 32 it will be rounded
to the next higher multiple of 32.
Command Description
dmt bitrate minimum downstream {Kbps} Sets the minimum downstream bitrate in
no dmt bitrate minimum downstream Kbps (kilobits per second). The parame-
ters are between 32 and 12000 Kbps and
the factory default is 32 Kbps.
dmt bitrate minimum upstream {Kbps} Sets the minimum upstream bitrate to a
no dmt bitrate minimum upstream value in Kbps. The parameters are
between 0 and 12000 Kbps and the
factory default value is 32 Kbps.
dmt bitrate maximum downstream disable Disables S=1/2 and sets the maximum
{Kbps} downstream bitrate to a value in Kbps.
no dmt bitrate maximum downstream disable The parameters are between 40 and 8128
Kbps.
This command does not have a default
value. The command no dmt bitrate
maximum downstream disable sets the
maximum downstream bitrate to 32000
Kbps.
dmt bitrate maximum downstream enable {Kbps} Enables S=1/2 and sets the maximum
no dmt bitrate maximum downstream enable downstream bitrate to a value in Kbps.
The parameters are between 40 and
32000 Kbps and the default value is
23000 Kbps.
dmt bitrate maximum upstream {Kbps} Sets the minimum upstream bitrate to a
no dmt bitrate maximum upstream enable value in Kbps. The parameters are
between 40 and 16000 Kbps and the
default value is 2048 Kbps.
Caution: The dmt bitrate commands described in this table cause the interface to
! retrain when the parameter is changed. Setting a parameter to its current value
does not cause a retrain. If an interface is training when this parameter is changed,
the interface retrains to the new parameter.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 339 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Command Description
dmt impulse-noise-protection downstream Sets the minimum number of DMT
{0-17} frames/symbols (INP/S parameter) per
no dmt impulse-noise-protection downstream codeword for downstream or upstream
impulse noise protection.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 340 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
dmt maximum-delay downstream {0-20} Sets the maximum allowed delay down-
no dmt maximum-delay downstream stream and upstream to a value
between 0 and 20 ms.
The factory defaults for upstream and
dmt maximum-delay upstream {0-20} downstream are 20 ms.
no dmt maximum-delay upstream When the DSL Line Retransmission Error
Recovery feature is enabled, a minimum
value of 4 MUST be set for the command
dmt maximum-delay downstream.
dmt operating-mode {G.992_1, G.992_3, Sets the operational mode
G.992_3_M, G.992_5, G.992_5_M, ANSI_T1. G.992_1: G.992.1
AUTO}
G.992_3: G.992.3
no dmt operating-mode
G.992_3_M: G.992.3_AnnexM
G.992_5: G.992.5
G.992_5_M: G.992.5_AnnexM
ANSI_T1.413: T1.413
AUTO: Automatic selection. This is the
factory default.
Annex L is enabled on the BLC with Auto
and G.992_3 line protocols.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 341 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Command Description
dmt bitswap downstream Enables or disables downstream
no dmt bitswap downstream bitswapping. This feature is enabled
by default.
dmt bitswap upstream Enables or disables upstream
no dmt bitswap upstream bitswapping. This feature is enabled
by default.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 342 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Command Description
dmt snr-margin target downstream {0 - 31} Sets the SNR (Signal to Noise) target down-
no dmt snr-margin target downstream stream and upstream margins to a value
between 0 and 31 dB.
The target margins define the SNR margins
dmt snr-margin target upstream {0 - 31} that must be available when the handshake
no dmt snr-margin target upstream process is determining the capability of
each subcarrier.
The the factory default is 6 dB.
dmt snr-margin maximum downstream {0 - These commands define the amount of
31} margin above target that must be present
no dmt snr-margin maximum downstream before power cutback kicks in.
They set the SNR (Signal to Noise)
maximum downstream and upstream
dmt snr-margin maximum upstream {0 - 31} margins to values between 0 and 31 dB
no dmt snr-margin maximum upstream (decibels).
The maximum margins implemented in the
BLC represent specific SNR margins, above
which power cutback kicks in. For example,
setting the maximum margin to 12dB (dmt
snr-margin maximum downstream 12)
will initiate power cutback if the line has
<target-snr-margin>+12dB or better SNR
margin.
In the BLC, a configuration of
“maximum margin = 12dB”
means initiate power cutback if the oper-
ating margin is greater than or equal to
12dB.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 343 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Command Description
dmt snr-margin down-shift downstream {0 - Sets the downshift downstream SNR
31} margin to a value between 0 and 31 dB.
no dmt snr-margin down-shift downstream The command no dmt snr-margin down-
shift downstream resets the margin to 4
dB, the factory default.
dmt snr-margin up-shift downstream {0 - 31} Sets the upshift downstream SNR margin
no dmt snr-margin up-shift downstream to a value between 0 and 31 dB.
The command no dmt snr-margin up-
shift downstream resets the margin to 8
dB, the factory default.
dmt snr-margin down-shift upstream {0 - 31} Sets the downshift upstream SNR margin
no dmt snr-margin down-shift upstream to a value between 0 and 31 dB. The
command no dmt snr-margin up-shift
downstream resets the margin to 4 dB, the
factory default.
dmt snr-margin up-shift upstream {0 - 31} Sets the upshift upstream SNR margin to a
no dmt snr-margin up-shift upstream value between 0 and 31 dB.
The command no dmt snr-margin up-
shift upstream resets the margin to 8 dB,
the factory default.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 344 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Command Description
dmt snr-margin downstream {0 - 31} {0 - 31} Sets the downstream SNR minimum and
no dmt snr-margin downstream maximum values between 0 and 31 dB. The
first parameter sets the minimum down-
stream SNR and the second parameter sets
the maximum downstream SNR.
The command no dmt snr-margin down-
stream resets the downstream SNR
minimum and maximum values to the
factory default values.
The factory default downstream minimum
value is 2.0 dB.
The factory default downstream maximum
value is 9.0 dB.
dmt snr-margin upstream {0 - 31} {0 - 31} Sets the upstream SNR minimum and
no dmt snr-margin upstream maximum values between 0 and 31 dB. The
first parameter sets the minimum upstream
SNR and the second parameter sets the
maximum upstream SNR.
The command no dmt snr-margin
upstream resets the upstream SNR
minimum and maximum values to the
factory default values.
The factory default upstream minimum
value is 2.0 dB.
The factory default upstream maximum
value is 9.0 dB.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 345 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Command Description
dmt encoding trellis Enables trellis coding. Trellis coding is enabled by
no dmt encoding trellis default.
The command no dmt encoding trellis disables trellis
coding.
dmt reed-solomon Enables Reed Solomon coding. Reed Solomon coding is
enabled by default.
Command Description
dmt sra Enables SRA.
dmt sra minimum-downshift-interval {0-16383} Sets the minimum downshift and
no dmt sra minimum-downshift-interval upshift Rate Adaptation (RA) interval
to a value between 0 and 16383
seconds.
dmt sra minimum-upshift-interval {0-16383} The factory default setting for
no dmt sra minimum-upshift-interval minimum downshift and upshift RA is
30 seconds.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 346 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 347 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Detaching a Profile
To detach a profile from an interface follow these steps:
1 From the Global Configuration Mode, go to DSL Interface Configuration Mode
and specify the interface from which you want to detach the profile:
Occam(config)# interface dsl {dsl-interface-number}
Deleting a Profile
Delete a profile by using the no dsl-profile command and its profile-name from
Global Configuration Mode:
Occam(config)# no dsl-profile {profile-name}
Note: You can modify the default profile, but you cannot delete it. You cannot
delete a profile that is currently associated with an interface.
Copying a Profile
To copy a source profile to a new profile enter the dsl-copy-profile command from
the Global Configuration Mode. If the destination profile indicated in this
command does not exist, dsl-copy-profile creates it. The command then copies all
non-default configurations defined for the source profile to the destination profile:
Occam(config)# dsl-copy-profile source-profile dest-profile
Warning: If the parameters for an existing destination profile change due to this
command, the interfaces attached to it will retrain.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 348 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Profile
Note: If the destination profile already exists, its parameters will be overwritten by
the source profile. Finally, if you modify the source profile after issuing the dsl-
copy-profile command, the changes you make do not propagate to the destination
profile.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 349 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring an Access Profile
3 The default QoS setting assigns fixed priorities to give management the highest
priority, to separate multicast and unicast video and to leave Internet traffic
with the lowest priority or service level. The priority command may be used to
configure the priority of traffic on a DSL service to be set as level 1 through 4
or as a default setting. Traffic on a service that is configured with a higher
priority will completely clear before traffic on a service with a lower priority
queue will pass.
Note: Multicast priority is globally configured on a BLC because multicast
resources are shared across all ports. Multicast priority is configured with the
command subscriber multicast priority {1 | 2 | 3 |4 | default} from Global
Configuration Mode.
occam(config-pmap)# priority {1-4}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 350 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring an Access Profile
show policy-map binding: use this command to display policy maps and which
Ethernet port and service they are applied to.
2 Enter Access Profile Configuration Mode. Create a profile by using the name of
a profile you want to create, or an existing profile you want to modify. Use the
no access-profile command to delete a profile:
Occam(config)# access-profile {access-profile-name}
3 Define the default VLAN ID for the service to which the access profile is
attached. All traffic with no source IP address will be mapped to this VLAN. The
default is VLAN 2:
Occam(config-access-profile)# eps access untagged vlan {2-122}
4 Assign a rate-limiting policy map to the access profile as an output policy, rate-
limiting all unicast traffic coming to the subscriber from the BLC. Specify the
policy map by name (as described in the section, Defining a Unicast Rate Limiting
Policy Map on page 350):
occam(config-access-profile)# service-policy output {policy-map-
name}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 351 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring an Access Profile
5 Assign a rate-limiting policy map to the access profile as an input policy, rate-
limiting all unicast traffic coming to the BLC from the subscriber. Specify the
policy map by name (as described above in the section, Defining a Unicast Rate
Limiting Policy Map on page 350):
occam(config-access-profile)# service-policy input {policy-map-
name}
6 (Optional) Configure the port the profile is attached to as a IGMP host to enable
forwarding of IGMP managed multicast traffic to downstream subscriber inter-
faces. This feature is disabled by default. If the IP address is not specified, the
BVI IP address will be used. Use the command no igmp to disable traffic
forwarding:
occam(config-access-profile)# igmp host {IP address}
7 (Optional) Limit the number of groups on the port to which the profile is
attached. The factory default is 255:
occam(config-access-profile)# igmp group-limit {1-255}
8 Configure DHCP mode for snooping, Layer 2 relay or Layer 3 relay. When Layer
2 or Layer 3 relay is configured, the Option 82 parameter may be configured as
well. Please turn to the section DHCP Configuration in Chapter 22, IP Security
Management (IPSM) on page 451 for information about these DHCP configura-
tion options:
occam(config-access-profile)# dhcp mode
{l2Relay|l3Relay|snoop|none}
9 Configure the ARP mode to proxy or none. Please turn to the section ARP Proxy
in Chapter 22, IP Security Management (IPSM) on page 464 for information
about these configuration options:
occam(config-access-profile)# arp mode {proxy|none}
10 Enter the command arp reply gateway if you are configuring ARP proxy in
conjunction with peer to peer traffic blocking. Please turn to the section Peer to
Peer Traffic Blocking in Chapter 22, IP Security Management (IPSM) on page 440
for information about this command:
occam(config-access-profile)# arp reply gateway
11 Configure the maximal acceptable packet rate limit for a protocol from a device
that is associated with the access profile. Please turn to the section Blacklisting
in Chapter 22, IP Security Management (IPSM) on page 469 for information
about this command:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 352 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring an Access Profile
12 (Optional) Change the ARP cache timeout from the default value of 15 minutes.
The parameters are from between one and 480 minutes:
occam(config-access-profile)# arp cache timeout {minutes}
15 If required, enable or disable the PPPoA to PPPoE IWF. Select “iwf” to enable the
feature or “none” to disable it. PPPoA to PPPoE IWF is disabled by factory
default:
occam(config-access-profile)# pppoe mode {iwf|none}
16 If requred, configure the PPPoE stale session detection parameters. The BLC will
monitor traffic over the provided interval. If traffic is detected flowing in one
direction only for (retry_count x interval), the session will be considered as stale
and the BLC will terminate it properly. This feature is disabled by default.
{interval}: determine the interval in seconds used to sample traffic in both
direction. The parameters are from 2-10 seconds and the default value is 5
seconds.
{retry-count}: the number of interval failures required to confirm a stale
session. The parameters are from 2-5 intervals and the default value is 3
intervals.
occam(config-access-profile)# pppoe stale-detection enabled
{interval} {retry-count}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 353 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring an Access Profile
17 If requred, configure the PPPoE Discovery Timeout parameters. The BLC will send
Discovery packets towards the BRAS device and wait for 'interval' seconds
before resending the packet if no answers from BRAS were received. If a PPPoE
packet was re-transmitted for 'retry_count' times, the PPPoE Discovery status
will go back to IDLE. If a packet needs retransmission, the new interval will be
the square value of the old interval:
{interval}: the initial in seconds used to detect un-responded Discovery
packets. The parameters are between 1 and 10 seconds.
{retry-count}: the number of Discovery packet retransmits allowed. The
parameters are between 1 and 30.
occam(config-access-profile)# pppoe discovery timeout {interval}
{retry-count}
20 Continue on to the section Configuring a DSL Bonding Group on page 356 if you
wish to configure a DSL bonding group.
Continue on to the section Enabling and Configuring a DSL Interface on page 358
if you wish to configure a DSL bonding group.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 354 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring an Access Profile
Note: If the destination profile already exists, its parameters will be overwritten by
the source profile. If you modify the source profile after issuing the access-copy-
profile command, the changes you make do not propagate to the destination
profile.
Note: You can modify the default profile, but you cannot delete it. You cannot
delete a profile that is currently associated with a port.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 355 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Bonding Group
2 Enter DSL Bonding Configuration mode and specify the bonding group ID:
Occam(config)# dsl bonding-group group-id {1-6}
Use the no form of the command to return the maximum downstream bitrate
to the default value of:
occam(config-dsl-bonding-#)# no bitrate maximum downstream
Use the no form of the command to return the maximum upstream bitrate to
the default value:
occam(config-dsl-bonding-#)# no bitrate maximum upstream
5 Assign up to two consecutive DSL ports from the same port range to the
bonding group in a comma separated list.
Note: Do not enter a space after a comma when using this command:
occam(config-dsl-bonding-#)# assign-ports {1,2,3...48}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 356 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Configuring a DSL Bonding Group
Use the no form of the command to remove ports from the DSL bonding group:
occam(config-dsl-bonding-#)# no assign-ports {1, 2}
7 Configure a service to attach to the bonding group. Please turn to the section
Enabling and Configuring Service(s) on page 361 for information about how to
configure a service, attach the access profile to the service and then and attach
the service to the bonding group.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 357 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Enabling and Configuring a DSL Interface
2 Enter DSL Interface Configuration Mode and specify the DSL interface to which
you want to attach a service:
Occam(config)# interface dsl {dsl-interface-number}
There are 15 pre-defined filter masks available for the mask psd downstream
command. Each setting either reduces or completely eliminates some of the
available bins across the downstream spectrum for a particular DSL line. Each
filter mask acts on a different part of the spectrum, with the exception of filter
mask of 0, which turns filter masking off.
PSD masks are used to reduce the interference that a DSL line has on other DSL
lines within a shared binder group. This command is especially useful if you are
sharing a binder group with a competitor. Interference is an issue when some of
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 358 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Enabling and Configuring a DSL Interface
the lines in a binder group are at one loop length (e.g., originating from a
Remote Terminal), and other lines are at another length (e.g., originating from a
Central Office).
6 Please turn to page 361 for information about how to configure a service and
attach it to a DSL interface.
Disabling an Interface
1 From the Global Configuration Mode, enter Interface Configuration Mode and
specify the interface you want to disable:
Occam(config)# interface dsl {dsl-interface-number}
show dsl profile [profile-name]: use this command to display information about
a profile. If you omit the profile-name argument, this command displays profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 359 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Enabling and Configuring a DSL Interface
show dsl status [dsl-interface-number]: use this command to display the oper-
ational status of the interface (up/down), the actual line rates as well the
operational mode to which it is trained.
show dsl tones {dsl-interface-number}: use this command to display bits per
bin for each of the 256 ADSL tone frequencies for a specific DSL interface.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 360 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Enabling and Configuring Service(s)
2 Assign an access profile by name to the service (please see page 350 for infor-
mation about how to configure an access profile):
Occam(config-if-dsl-service-<1-x>)# access profile name
3 Set Permanent Virtual Circuit (PVC) parameters that match the ADSL modem:
Set the Virtual Path Identifier (VPI), choosing between zero and 15.
Set the Virtual Channel Identifier (VCI), choosing between 32 and 511.
Note: VCI numbers from 0 to 31 are reserved:
Occam(config-if-dsl-service-<1-x>)# pvc vpi/vci
5 (Optional) If you have previously configured this DSL service and you wish to
change the static associations that your have previously configured on it, you
may do so with one of the following commands:
Remove all static associations:
occam(config-if-dsl-service-<1-4>)# delete static associations
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 361 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Enabling and Configuring Service(s)
6 Optionally, delete a stale or an inactive DHCP client. Enter a MAC address in the
format AA:BB:CC:DD:EE:FF:
occam(config-if-dsl-service-<1-4>)# delete dhcp client {mac-
address}
7 Optionally, set maximum number of IGMP groups allowed, overriding the IGMP
group limit set in the attached access profile. This command and the other over-
ride access-profile commands may be useful if an access profile is attached to
a large number of ports and a change needs to be made to a small number of
them:
occam(config-if-dsl-service-<1-4>)# override access-profile igmp
group-limit {1-255}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 362 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Enabling and Configuring Service(s)
show dsl service: use this command from Privileged mode to display informa-
tion about services on all DSL interfaces.
show dsl service {0-15/32-511}: use this command from Privileged mode to
display information about a PVC. Enter the VPI and the VCI.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 363 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 18: Configuring DSL Interfaces
Enabling and Configuring Service(s)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 364 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Introduction
Chapter 19
PPPoA to PPPoE Interworking
Function
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
PPPoA to PPPoE IWF Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
PPPoA to PPPoE IWF Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Introduction
The PPPoA to PPPoE Interworking Function (IWF) is a function to support migration
of ATM based DSLAM services onto the IP based DSLAM ports of an Occam BLC
network. The purpose is to allow a DSL BLC to support existing ATM based PPPoA
modems to their supporting Broadband Remote Access Server (BRAS). This function
is designed around the DSL Forum TR-101, Migration to Ethernet-Based DSL
Aggregation document.
Overview
PPPoE
PPPoE enables the transport of PPP frames over Ethernet by encapsulating PPP
frames inside Ethernet frames. PPPoE consists of two protocols; the PPP protocol
and the “oE” protocol that is added on top of the PPP protocol. In order to establish
a PPP link, an oE session needs to be established. This is the responsibility of the oE
Protocol. This is referenced in RFC-2516
The oE protocol is divided into two parts; the Discovery protocol which establishes
the session and the Session protocol which carries the PPP frames in an Ethernet
Encapsulation. In order to send PPP frames across the Session Protocol, the
Discovery negotiation must be completed and successful.
Discovery Protocol
During the oE Discovery protocol, PAD (PPPoE Active Discovery Initiation) packets
are sent with the Ethernet format. The Protocol ID (ethertype field) is 0x8863.
A PAD packet has the following format:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 365 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Overview
Discovery (PADI)0x09
Offer (PADO)0x07
Request (PADR)0x19
Session (PADS)0x65
Terminate (PADT)0xa7
For the PADI, PADO, PADR packets, the session ID field MUST be 0x0. PADI is the
only broadcast packet for PPPoE. A PADT packet MUST contain the session ID its
requesting to terminate
The PPPoE Discovery state machine is:
Client Server
Send PADI
Send PADO
Send PADR
Send PADS
Communication
opened
Once the communication is opened, the only way to terminate the oE session is for
one side to send a PADT packet containing the session ID received in the PADS
packet. If the server does not like the client’s request, a PADS will be returned with
session ID=0x0 and an error flag that indicates the reason for the refusal.
Session Protocol
During the oE Session protocol, PAS (PPPoE Active Discovery Session-confirmation)
packets are sent with an Ethernet format. The Protocol ID (ethertype field) is
0x8864. It contains the PPP protocol information.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 366 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Overview
A PAS packet MUST have the code field set to 0x0 and the session ID field be the
same as returned in the PADS packet. A session is terminated by using a PADT
packet with proper session ID value.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 367 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Overview
PPPoA
DSL modems that are configured to support PPPoA will send PPP frame packets
over the DSL ATM link. Once the BLC receives these packets, it checks to see if there
is a PPPoE session established. If there is not a session yet established, the BLC first
confirms that the packets are PPP LCP packets. If they are, the BLC establishes an
oE connection with a BRAS and forwardings the PPP information to the BRAS in a
0x8864 encapsulated packet.
The BLC is only directly involved in the oE portion of the PPPoE protocol. The PPP
section still is negotiated between the PPP client (ADSL modem) and the server
(BRAS).
As specified in TR-101, an IWF tag is be added to the PAD packets going to the BRAS
informing it that an IWF agent is in between the client and itself. Also, if supported
by the BRAS, the IWF agent and the BRAS can negotiate MTU settings. If not
supported, MTU setting of 1492 must be used.
PPPoA to PPPoE IWF can only be supported in access profiles configured for the
same VLAN. This feature only works on a single VLAN per BLC.The management
interface will check for other access profiles already configured with this option
and compare their VLAN configuration. If the VLAN don't match, an error will be
returned informing the user of the problem.
Stale session detection is disabled by default, allowing the BLC to monitor traffic in
both directions for a port in session state. If traffic flows only in one direction, the
session is considered staled and terminated. To make sure the BLC is not stuck in a
PAD state, it will try to retransmit unanswered PAD packet up to a certain amount
of times with a back-off algorithm.
Installing this ACL is expected to drop all traffic coming from the subscriber.
Because of these security issues (user can't install ACL), and since ACL configuration
is VLAN based, the recommendation it not to design a network where PPPoE and
PPPoA IWF users co-exists on the same subscriber VLAN. If a PPPoA IWF and a
PPPoE subscriber have to co-exist on the same subscriber VLAN, Occam Networks’
recommendation is to not use any ACL.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 368 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
PPPoA to PPPoE IWF Configuration
2 Enter Access Profile Configuration Mode. Create a profile by using the name of
a profile you want to create, or an existing profile you want to modify. Use the
no access-profile command to delete a profile:
occam(config)# access-profile {access-profile-name}
3 If required, enable or disable the PPPoA to PPPoE IWF. Select “iwf” to enable the
feature or “none” to disable it. PPPoA to PPPoE IWF is disabled by factory
default:
occam(config-access-profile)# pppoe mode {iwf|none}
4 If required, configure the PPPoE stale session detection parameters. The BLC will
monitor traffic over the provided interval. If traffic is detected flowing in one
direction only for (retry_count x interval), the session will be considered as stale
and the BLC will terminate it properly. This feature is disabled by default.
{interval}: determine the interval in seconds used to sample traffic in both
direction. The parameters are from 2-10 seconds and the default value is 5
seconds.
{retry-count}: the number of interval failures required to confirm a stale
session. The parameters are from 2-5 intervals and the default value is 3
intervals.
occam(config-access-profile)# pppoe stale-detection enabled
{interval} {retry-count}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 369 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
PPPoA to PPPoE IWF Configuration
5 If required, configure the PPPoE Discovery Timeout parameters. The BLC will
send Discovery packets towards the BRAS device and wait for 'interval' seconds
before resending the packet if no answers from BRAS were received. If a PPPoE
packet was re-transmitted for 'retry_count' times, the PPPoE Discovery status
will go back to IDLE. If a packet needs retransmission, the new interval will be
the square value of the old interval:
{interval}: the number ofseconds used to detect un-responded Discovery
packets. The parameters are between 1 and 10 seconds.
{retry-count}: the number of Discovery packet retransmits allowed. The
parameters are between 1 and 30.
occam(config-access-profile)# pppoe discovery timeout {interval}
{retry-count}
Disable this feature with the following command:
occam(config-access-profile)# no pppoe discovery timeout
Clearing Statistics
You may enter the following command from Privileged or User Modes.
Depending if the optional 'port' parameter is provided, this command will reset all
subscriber PPPoA statistics or just for the provided port.
occam# clear pppoa statistics [port-number]
occam> clear pppoa statistics [port-number]
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 370 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Show Commands
Show Commands
You may enter the following commands from Privileged or User Modes.
Displaying Access Profile Configuration Information
If a DSL profile isn't specified, information about all DSL profiles on this BLC will be
shown.
occam# show access-profile [DSL-profile]
For example:
occam# show access-profile PPPoE
Output Service Policy: N/A
EPS: vlan 6
Mac Limit: 1
Mac Learning: enabled
DHCP Mode: none
DHCP Servers:
DHCP Hot Swap: disabled
Circuit-Id: ${SYSNAME} atm ${SLOT}/${DEVNAME}:${PVC}
Blacklist config:
Protocol: ARP
Packet Rate: 5 pps
Alarming Interval: 5 secs
Clearing Interval: 3 units of Alarming interval
Action: shutdown
Protocol: DHCP
Packet Rate: 5 pps
Alarming Interval: 5 secs
Clearing Interval: 3 units of Alarming interval
Action: shutdown
Protocol: IGMP
Packet Rate: 30 pps
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 371 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Show Commands
For example:
occam# show subscriber pppoe summary
PPPoE Sessions
Port | State | Session ID | AC MAC Address | Count | Uptime
-----|-----------|------------|-------------------|-------|----------
01/2 | SESSION | 1734 | 00:10:67:00:ac:2c | 1 | 0d22h11m
02/2 | SESSION | 1723 | 00:10:67:00:ac:2c | 1 | 0d22h11m
03/2 | SESSION | 1728 | 00:10:67:00:ac:2c | 1 | 0d22h11m
PPPoE Info:
MAC Address: 00:02:86:00:00:b1
AC MAC Address: 00:10:67:00:ac:2c
Service-Name: occamnetworks.com
AC-Name: CS_PPP_SERVER
Host-Uniq: 28
Field Description
Port/Service Shows the DSL port/service where a service has been
established.
State The current PPPoE state. (Idle, Initial, Offer, Request,
Session).
Session ID The session ID assigned by the BRAS.
MAC Address The virtual MAC address of the session's client.
Count How many time the PPPoE session restarted.
Session Uptime How long the current session has been up.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 372 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Show Commands
For example:
occam# show subscriber pppoe session id 1734
PPPoE Sessions
Port | State | Session ID | AC MAC Address | Count | Uptime
-----|-----------|------------|-------------------|-------|----------
01/2 | SESSION | 1734 | 00:10:67:00:ac:2c | 1 | 0d22h14m
Displaying Summarized PPPoE Session Statistics for All PPPoA IWF Configured Ports
This command displays the PPPoE session statistics for all PPPoA IWF configured
ports in a summarized format.
occam# show subscriber pppoe statistics summary
For example:
occam# show subscriber pppoe session statistics summary
PPPoE IWF Session Statistics Summary
PPPoE IWF Session TX/RX packet summary:
Rx packets 151490587
Dropped Rx packets 0
Tx packets 21144015
Dropped Tx packets 0
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 373 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Show Commands
Displaying the PPPoE session Statistics For the Provided PPPoA IWF Configured Port
This command displays the PPPoE session statistics for the provided PPPoA IWF
configured port.
occam# show subscriber pppoe session statistics {port}
For example:
occam# show subscriber pppoe session statistics 1
PPPoE IWF Session Statistics for port/service: 1/2
PPPoE IWF Session TX/RX packet summary:
Rx packets 7255955
Dropped Rx packets 0
Tx packets 1114236
Dropped Tx packets 0
Tx PADI packets 70
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 374 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Show Commands
Tx PADO packets 0
Tx PADR packets 52
Tx PADS packets 0
Tx PADT packets 0
Total Tx PAD packets 122
For example:
occam# show subscriber pppoe discovery statistics 1
PPPoE Statistics for port/service: 1/2
PPPoE IWF Session TX/RX packet summary:
Rx packets 7
Dropped Rx packets 5
Tx packets 7
Dropped Tx packets 0
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 375 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Show Commands
Rx PADO packets 1
Rx PADR packets 0
Rx PADS packets 1
Rx PADT packets 0
Total Rx PAD packets 2
Tx PADI packets 5
Tx PADO packets 0
Tx PADR packets 2
Tx PADS packets 0
Tx PADT packets 0
Total Tx PAD packets 7
Displaying Different Statistics About Received PPPoA Frames For All PPPoA IWF Configured Ports
This command displays different statistics about received PPPoA frames for all
PPPoA IWF configured ports.
occam# show subscriber pppoa statistics summary
For example:
occam# show subscriber pppoa statistics summary
PPPoA Statistics Summary
PPPoA TX/RX frames summary:
Rx frames 21171791
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 376 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Show Commands
Dropped Rx frames 10
Tx frames 151689267
Dropped Tx frames 0
Displaying Different Statistics About Received PPPoA Frames For All PPPoA IWF Configured Ports
This command displays different statistics about received PPPoA frames for the
provided port configured for PPPoA IWF.
occam# show subscriber pppoa statistics {DSL port}
For example:
occam# show subscriber pppoa statistics 1
PPPoA Statistics for port/service: 1/2
PPPoA TX/RX frames summary:
Rx frames 1115743
Dropped Rx frames 1
Tx frames 7265769
Dropped Tx frames 0
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 377 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 19: PPPoA to PPPoE Interworking Function
Show Commands
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 378 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Introduction
Chapter 20
Configuring SIP
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
SIP Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Configuring Global SIP Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Configuring a Voice Port SIP Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Configuring a SIP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Configuring a Voice Port For SIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Viewing Your SIP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Digit Map Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
CLASS Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Introduction
Occam Network’s Session Initiated Protocol (SIP) feature, as described in RFC 3261,
allows softswitches to use SIP to control the VoIP POTS ports of the BLC 6000 by
configuring the BLC to operate as a RFC 3261 compliant SIP user agent.
In this model, POTS ports register with a SIP proxy server to perform call processing.
The SIP signaling may be configured to transport over UDI or TCP or for SIPS URI
encapsulation over TLS.
The BLC supports transport of the SIP traffic in a separate VLAN, requiring the
multi-homing feature be configured on the BLC. Multi-homing is described in
Chapter 8, Configuring Multihoming on page 153.
SIP requires the endpoint to provide all local control for dial tone, digit collection
and ring control. SIP is only used for establishing and maintaining connections with
remotes.
BLC 6150-01
BLC 6151-01
BLC 6152-02
BLC 6244
BLC 6246
BLC 6252-03
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 379 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Introduction
Chapter Overview
The first section SIP Basics on page 382 provides an overview of how the BLC
feature functions.
SIP configuration, described more fully below, is described in the sections
Configuring Global SIP Configurations on page 388, Configuring a Voice Port SIP
Profile on page 389, Configuring a SIP Profile on page 397 and Configuring a Voice
Port For SIP on page 404.
The section Viewing Your SIP Configuration on page 409 describes how to view your
SIP configuration.
The section Digit Map Configuration on page 419 describes how to configure a digit
map.
The section CLASS Feature Overview on page 421 contains a table that shows if a
Custom Local Area Signaling Services (CLASS) feature is provided as a BLC POTS
feature, as a soft switch feature, or a feature provided by both. If the CLASS feature
is provided by both the BLC and a softswitch, the feature must be configured on
both devices to be enabled.
Global SIP
Param eters
on BLC
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 380 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Introduction
Voice ports can share voice port profiles and SIP profiles. In Figure 20-2 shows a
BLC with the following sample configuration:
The BLC configured with Global SIP parameters that apply to each of its voice
ports that is configured for SIP.
Voice port 1 uses voice port profile “A” and SIP profile “A”
Voice port 2 uses voice port profile “A” and SIP profile “B”
Voice port 3 uses voice port profile “A” and SIP profile “C”
Voice port 4 uses voice port profile “B” and SIP profile “C”
S IP P R O F IL E V O IC E P O R T S IP P R O F IL E S IP P R O F IL E V O IC E P O R T
"A " P R O F IL E " A " "B " "C " P R O F IL E "B "
V O IC E V O IC E V O IC E V O IC E
PORT 1 PORT 2 PORT 3 PORT 3
B L C W IT H G L O B A L S IP P A R A M E T E R S C O N F IG U R E D
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 381 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
SIP Basics
SIP Basics
User Agents and Servers
A SIP based network includes user agents and servers.
SIP Servers
There are four different types of SIP servers: proxy, redirect, registrar and location
server. These servers may or may not be located on the same physical devices.
Proxy Servers
The BLC’s SIP UA sends registrations, invitations to sessions, and other requests to
a softswitch configured as a proxy server. Proxy servers act like a server, routing
these SIP requests to other UASs, and like a client, routing SIP responses to their
UACs.
Proxy servers also can authenticate and authorize users for services, implement
provider call-routing policies, and provide features to users. They may also interpret
and rewrite specific parts of a request message before forwarding it.
A proxy server is involved only in setting up and tearing down a communication
session. After the user agents have established a session, communications occur
directly between the parties.
Redirect Servers
Redirect servers help UACs locate UASs by providing information about their
location (a SIP URI). If a UAS can’t be found at the first URI used, the redirect server
will either provide information about the UAS’s current URI or the address of a
server with more information.
After the UAC gets this new URI from the redirect server it will send its request
again directly to that address.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 382 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
SIP Basics
Registrar Servers
Registrar servers authenticate UAs and then received information about their
current location (their current URI). This allows redirect servers to help UAs find
them.
Location Servers
Registrar servers send the URIs that they receive from UAs to Location Servers.
These Location Servers keep this information in a database that binds an address
with a particular network domain.
This server works in conjunction with the registration service and allows a proxy
server to input a URI and receive a set of URIs that tells it where to send a particular
request.
SIP Messages
SIP messages are defined for two formats: requests, sent from a client to a server,
and responses, sent from a server to a client. The request message defines the
client’s requested operation, and the response provides information regarding the
status of that request.
Request Messages
There are six types of request messages. Each request contains a field which is called
a method, which describes its purpose.
INVITE
AN INVITE request asks the UA to participate in a session. The body of the INVITE
request includes a description of the session. When a SIP UAC sends an INVITE
request to a UAS the INIVITE will include the phone number of the remote.
ACK
An ACK request acknowledges that the UA has received a final request to an INVITE
request.
OPTIONS
An OPTIONS request queries for information from a server about its capabilities,
including which session description protocols and methods it supports.
BYE
A BYE request is sent by a UAC or UAS to terminate a session.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 383 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
SIP Basics
CANCEL
A CANCEL request cancels a pending request.
REGISTER
A REGISTER request informs a registrar server about UA’s current location.
Occam Network’s SIP feature also supports SUBSCRIBE and NOTIFY messages. The
BLC will send a SUBSCRIBE message to the proxy if the port is configured for MWI.
The BLC will receive NOTIFY from the proxy and set the local ports MWI according
to the content in the NOTIFY message.
Response Messages
When a server receives a request message it issues one or more response messages.
These response messages contain status codes that indicate the current condition
of this request. The status code values are divided into six classes. The first digit of
the status code defines the class of response. The status codes are HTTP/1.1 response
codes and are described in detail in RFC 3261.
1xx
Informational (e.g. 100 Trying, 180 Ringing, 183 Session Progress)
Informational responses, also known as provisional responses, indicate that request
has been received and the server is continuing to process the request.
2xx
Successful (e.g. 200 OK, 202 Accepted) 2xx codes indicate that the request was
successful.
3xx
Redirection (e.g. 300 Multiple Choices, 301 Moved Permanently, 302 Moved
Temporarily) If the User Agent Server (UAS) decides to redirect the call, a 3xx
response is sent.
4xx
Client Error (e.g. 401 Unauthorized, 403 Forbidden, 403 Forbidden)
4xx responses contain bad syntax or cannot be fulfilled at this server.
5xx
Server Error (e.g. 500 Server Internal Error, 501 Not Implemented, 502 Bad
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 384 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
SIP Basics
6xx
Global Failure (e.g. 600 Busy Everywhere, 603 Decline, 604 Does Not Exist
Anywhere) The request cannot be fulfilled at any server
SIP Addressing
Each POTS port has a unique Uniform Resource Identifier (URI). This URI is used by
the SIP network to identify which requests and responses are from that port.
The URI is in the format:
“display string” <protocol:username@proxy-server>
The “display string” parameter is the portion of the port's URI that is displayed.
In the example below the display sting is "123_Maple_St".
The protocol options are “sip” and “sips” (TLS for security).
The username parameter is a unique username for the device. It may be the tele-
phone number but does not have to be. In either case, the username must be
matched to the telephone number in the softswitch. In the example below the
username is 2019999001.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 385 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
SIP Basics
Analog Analog
Telephone Telephone
BLC A SIP Proxy BLC B
Server
(1) CUSTOMER
DIALS NUMBER
(2) INVITE
(3) INVITE
(8) ACK
(9) ACK
(11) CUSTOMER
PUTS PHONE
ONHOOK
(12) BYE
(13) BYE
(14) OK
(15) OK
1 The customer using BLC A dials a phone number on their analog phone.
2 BLC A uses a dial plan to collect the digits dialed for the phone number and puts
the phone number digits in the URI that is sent in an INVITE request to the soft-
switch configured as a proxy server.
4 BLC B tells the softswitch that it is ringing the number by sending the 180 code.
6 BLC B tells the softswitch that has accepted the phone call by sending the 200
code.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 386 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
SIP Basics
8 BLC A sends the softswitch an ACK request acknowledging that it has accepted
the phone call.
10 The phone call messaging takes place directly between BLC A and BLC B.
14 BLC A tells the softswitch that it has received the BYE request by sending the
200 code.
15 The softswitch sends the 200 code acknowledging the BYE request on to BLC B.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 387 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring Global SIP Configurations
2 Enable SIP:
occam(config)# sip
3 By default SIP runs on BVI 1. Optionally, configure SIP to run on BVI 2. Please
see Chapter 8, Configuring Multihoming on page 153 for more information
about how to configure multihoming:
occam(config)# sip interface bvi 2
4 Set the SIP transport type (how SIP is transported), choosing between TLS, TCP
or UDP. The factory default is UDP:
occam(config)# sip transport {TLS|TCP|UDP}
5 Set the port number for the selected SIP transport method. If the transport type
is TCP or UDP the default port number is 5060. If the transport type is TLS the
default port number is 5061:
occam(config)# sip port {1025-65535}
6 Set the SIP application’s DSCP value for packets that it generates. The parame-
ters are between 0 and 63. This command has no effect on packets that the SIP
application receives from peer applications and takes effect immediately. It is
described more fully in Chapter 33, Differentiated Services (Diffserv) on page 677:
occam(config)# ip diffserv dscp protocol SIP {0-63}
7 Continue on to the following section Configuring a Voice Port SIP Profile on page
389 to configure a SIP profile.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 388 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port SIP Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 389 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port SIP Profile
and then attach the new profile to the desired voice port(s). This is described in the
section Copying a Voice Port Profile on page 396. The section Deleting a Voice Port
Profile on page 396 describes how to delete a voice port SIP profile.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 390 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port SIP Profile
2 Enter Voice Port Profile Configuration Mode with the voice-profile pots voip
command. Create a profile by using the name of a profile you wish to create or
an existing profile you wish to modify. Each voice port profile must have a
unique name:
occam(config)# voice-profile pots voip {profileName}
For example, if a Voice Profile named “sip” was being configured the command
would be:
Occam(config)# voice-profile pots voip sip
4 Continue to configure the voice port profile by using the some or all commands
shown below in Table 20-1. If you do not wish to change one or more of the
default parameters you do not need to enter those commands.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 391 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port SIP Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 392 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port SIP Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 393 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port SIP Profile
Codec-list: occam(config-profile)profile-name#
Preferred coder-decoders (codecs) used during codec-list (g711ulaw, g726-32K-pt2,
call compression. The order entered determines g726-32k}
the priority order of the codecs.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 394 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port SIP Profile
Codec-Options: occam(config-profile)profile-name#
Configures the jitter delay and packetization codec-options {g711ulaw, g726-32K-pt2,
options for codecs. g726-32k}
Jitter Delay: occam(config-voice-codec)#
Specifies jitter buffer delay in 5 msec jitter-delay {10,..110}
increments.
First use the “codec-options” command to enter
Voice Profile Codec configuration mode. From
this configuration mode you may enter the
“jitter-delay” command.
Packetization: occam(config-voice-codec)#
Selects the packetization period value in milli- packetization {15 | 10 | 20 |40}
seconds.
First use the “codec-options” command to enter
Voice Profile Codec configuration mode. From
this configuration mode you may enter the
“packetization” command.
Modem Codec Bypass: occam(config-profile)profile-name#
Configures the modem-codec-bypass as: modem-codec-bypass {enabled, disabled}
6 Repeat steps 2 through 5 for each SIP profile you wish to configure.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 395 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port SIP Profile
If a voice port profile with the name of the new profile already exists, its param-
eters will be overwritten by those of the new profile. In addition, if you modify
the original profile after issuing the voice-copy-profile command, the changes
you make do not propagate to the new voice port profile you created. Finally, if
the parameters for an existing profile with the same name as the new voice
profile change due to this command, the interfaces attached to this profile will
retrain.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 396 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a SIP Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 397 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a SIP Profile
Note: When parameters are changed in a SIP Profile, the associated voice channels
must re-register with the Registrar to declare the capabilities of the channel under
the new profile. This will cause a short disruption of service to the voice port. Occam
Networks recommends that changes to the SIP profile be done during light voice
call periods.
1 Enter Global Configuration mode:
occam#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
2 Enter SIP Profile Configuration Mode with the command sip-profile. Create a
profile by using the name of a profile you wish to create or an existing profile
you wish to modify. Each SIP profile must have a unique name:
occam(config)# sip-profile {sip-profile-name}
For example, if a SIP Profile named “sip_new” was being configured the
command would be:
Occam(config)# sip-profile sip_new
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 398 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a SIP Profile
Feature Command
Proxy Server: occam(config-sip-profile)#
Enter the FQDN (i.e. metaswitch.testlab.com) proxy {FQDN or IP address}: [1025-65535]
or IP address of a primary proxy server. You
may also optionally enter the port number occam(config-sip-profile)#
of the primary proxy server. The range or proxy secondary: {FQDN or IP address} [1025-
port numbers is between 1025-65535. 65535]
You may also enter the FQDN or IP address of
a secondary proxy server. The secondary
proxy server will be used if the primary proxy
server is unavailable.Again, you may also
optionally enter the port number of the
secondary proxy server. The range or port
numbers is between 1025-65535.
No primary or secondary proxy servers are
configured by factory default.
Proxy servers are described in the section
SIP Servers on page 382.
4 Configure the optional SIP Profile Parameters, referring to Table 20-3 for infor-
mation about the profile’s default values. If you do not wish to change one or
more of the optional default parameters of the SIP profile you do not need to
enter these commands.
Feature Command
SIP Domain: occam(config-sip-profile)#
Enter the FQDN or IP address for the domain sip-domain {FQDN or IP address}
part of the Uniform Resource Identifiers
(URI).
If this information is absent, this field
defaults to the proxy. No domain is config-
ured by factory default.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 399 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a SIP Profile
Registrar: occam(config-sip-profile)#
A registrar is a User Agent Server (UAS) that registrar {FQDN or IP address} [1025-65535]
accepts registration requests.
Enter the FQDN or IP address of a primary occam(config-sip-profile)#
registrar. You may also optionally enter the registrar secondary {FQDN or IP address}
UDP port number of the primary registrar. [1025-65535]
The range or port numbers is between 1025-
65535.
You may also enter the FQDN or IP address of
a secondary registrar. The secondary regis-
trar will be used if the primary registrar is
unavailable. Again, you may also optionally
enter the UDP port number of the secondary
registrar. The range or port numbers is
between 1025-65535.
If this information is absent, the registrar
defaults to the proxy. No primary or
secondary registrars are configured by
factory default.
Registrar servers are described in the section
SIP Servers on page 382.
Registration Timeout (Regtime): occam(config-sip-profile)#
Configures the registration timeout in regtime {1-86400}
seconds. The parameters are between one
and 86400.
The factory default is 3600 seconds.
Call Waiting: occam(config-sip-profile)#
Enables or disables the call waiting feature call-waiting {enable, disable}
on the port to which the profile is attached.
This feature is disabled by factory default.
Call waiting may be temporarily cancelled by
dialing (*70) before making the phone call.
When the phone is returned to the on hook
position call waiting is automatically
restored. During the call, incoming callers go
directly to Voice Mail. If voice mail is not
available, incoming callers hear a busy
signal.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 400 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a SIP Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 401 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a SIP Profile
occam(config)# exit
occam# copy running-config startup-config
Building configuration....
7 Go on to the following section Configuring a Voice Port For SIP on page 404.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 402 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a SIP Profile
If a voice port profile with the name of the new SIP profile already exists, its
parameters will be overwritten by those of the new SIP profile. In addition, if you
modify the original SIP profile after issuing the sip-copy-profile command, the
changes you make do not propagate to the new SIP profile you created. Finally,
if the parameters for an existing SIP profile with the same name as the new SIP
profile change due to this command, the interfaces attached to this SIP profile
will retrain.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 403 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port For SIP
2 Enter Voice Port Configuration Mode and specify a voice port number to
configure:
occam(config)# voice-port {voice-port-number}
3 Attach the voice port profile you created in the previous section, Configuring a
Voice Port SIP Profile to the voice port, specifying the voice port profile by name:
occam(config-voice)# attach-profile {voice-port-profile-name}
6 Configure the voice port by using the commands in the following table:
Feature Command
Attach SIP Profile: occam(config-voice-sip)#
Attach the SIP profile to the voice port, attach-profile {SIP-profile-name}
specifying the SIP profile by name.
Authentication Username: occam(config-voice-sip)#
Enter the authentication username, to be authusername {string}
used for authentication.
Authentication Password: occam(config-voice-sip)#
Enter the authentication password. password {string}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 404 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port For SIP
7 Optionally, override any of the settings in the SIP profile attached to this voice
port by using the commands in the following table. These commands do not
change the SIP profile:
Feature Command
Proxy Server Override: occam(config-voice-sip)#
Overrides the proxy server configuration override sip-profile proxy {FQDN or IP address}
in the SIP profile attached to this voice [1025-65535]
port and configures new proxy server for
the voice port. occam(config-voice-sip)#
override sip-profile proxy secondary{FQDN or
IP address} [1025-65535]
Registrar Override: occam(config-voice-sip))# override sip-profile
Overrides the primary and secondary registrar {FQDN or IP address} [1025-65535]
registrar configurations in the SIP profile
attached to this voice port and configures occam(config-voice-sip)# override sip-profile
new primary and secondary registrars for registrar secondary {FQDN or IP address}
the voice port. [1025-65535]
Registration Timeout Override: occam(config-voice-sip)# override sip-profile
Overrides the registration timeout regtime {1-86400}
(regtime) configuration in the SIP profile
attached to this voice port and configures
a new timeout for the voice port.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 405 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port For SIP
9 The voice port is shutdown by default. To enable the port enter the command
no shutdown:
occam(config-voice-sip)# no shutdown
11 Repeat steps 2 through 8 for each voice port to which you wish to attach a SIP
profile.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 406 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port For SIP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 407 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Configuring a Voice Port For SIP
Attaching a New SIP Profile to a Voice Port Previously Configured For SIP
1 Enter Global Configuration mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
2 Enter Voice Port Configuration Mode and specify a voice port number to
configure:
occam(config)# voice-port {voice-port-number}
4 Disable SIP:
occam(config-voice)# no sip
5 Reenable SIP:
occam(config-voice)# sip
6 Attach the new SIP profile to the voice port, specifying the SIP profile by name:
occam(config-voice-sip)# attach-profile {SIP-profile-name}
7 Make any other configuration changes to the voice port with the commands
described in Tables 20-4 and 20-5.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 408 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
show sip: this command displays Global SIP settings on the BLC. It is described
on page 409.
show sip endpoints: this command displays information about the SIP
endpoints. It is described on page 414.
show sip profiles: this command displays information about the SIP profiles. It
is described on page 416.
show sip users: this command displays information about the SIP users. It is
described on page 418.
Field Description
SIP User Agent Status of the user agent (user application). The options are up
or down.
SIP Interface BVI interface used (BVI1 or BVI2) and its IP address.
SIP Transport SIP transport type. The options are TLS, TCP or UDP.
SIP Port TLS, TCP or UDP port number.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 409 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
Field Description
name Name is the name of the user (username) that will be
authenticating
display Portion of the port's URI that is displayed.
authname Authentication username, to be used for authentication.
password Authentication password.
proxy FQDN or IP address of the proxy server.
regtime Registration timeout in seconds. The parameters are between
one and 86400. The factory default is 3600 seconds.
digit map Digit map, displaying a list of valid telephone numbers. Digit
map configuration is described on page 419.
callwaiting Shows if the call waiting feature is enabled on this voice port.
3waycalling Shows if the three way calling feature is enabled on this voice
port.
callerid Shows if the caller ID feature is enabled on this voice port.
mwi Shows if the message waiting indicator feature is enabled on
this voice port.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 410 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
Field Description
codec-list Shows the codecs used on this voice port. In the above
example the codecs are g726-32k-pt2 and g711ulaw.
codec-options This describes the names of the codec(s) used on this voice
port and the codec’s RTP packet type, packetization and jitter
delay values.
In the above example the codec options are shown as:
codec-options g726-32k-pt2 2 20 40
codec-options g711ulaw 0 10 20
Running parameters
URI: "123_Maple_St" <sip:2019999001@192.168.19.11>
Authentication: 2019999001:sip101
Primary:
proxy: 192.168.19.11
registrar: 192.168.19.11
Secondary:
proxy: 192.168.50.175
registrar: 192.168.50.175
digit map: P|x.T
CLASS features:
Codecs: Name PType Packet Jitter Delay
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 411 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
g726-32k-pt2 2 20 40
g711ulaw 0 10 20
Field Description
Last Dialed This is the last number dialed on the port.
Connections RTP address of the remote
Registration This section of output describes the registration parameters
to the primary proxy server.
Primary Status This is a numeric status code. The response codes are HTTP/1.1
response codes. You will see “200 OK” if the request has been
successful.
The status codes are HTTP/1.1 response codes and are
described in detail in RFC 3261. They are discussed earlier in
the section Response Messages on page 384.
Timer This field displays how long the registration is good for.
Expires This field displays when the registration will be renewed.
URI The Uniform Resource Indicator (URI) of the POTS port. This
URI is used by the SIP network to identify which requests and
responses are from that port.
The URI is in the format:
URI: “display string” <protocol:username@proxy-server>
The “display string” parameter is the portion of the port's URI
that is displayed. In the example below the display sting is
"123_Maple_St".
The protocol options are “sip” and “sips” (TLS for security).
The username parameter is the uername used for authentica-
tion. In the example below the username is 2019999001.
The proxy-server parameter is the proxy server’s FQDN or IP
address. In the example below the proxy server’s IP address is
192.168.19.11.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 412 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
Field Description
Secondary This field displays the secondary proxy and registrar. These
may also be a FQDN or an IP address.
Digit Map This displays the digit map, displaying a list of valid telephone
numbers. Digit map configuration is described on page 419.
CLASS Features Locally programmed call features.
These call features may need to be programmed on the
switch. Please refer to the section CLASS Feature Overview on
page
Codecs This describes the codec name (name), RTP packet type
(ptype), packetization (packet) and jitter delay (delay).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 413 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
Field Description
Port Voice port number
Adm Administrative state of the port
UP: the voice port is up (no shutdown)
down: the voice port is down (shutdown)
Oper Operational state of the port
UP: the voice port is up and fully configured for SIP
down: the voice port is down. SIP is in shutdown mode or not
fully configured.
Mode This will either show SIP or ESA (Emergency Stand Alone).
Please see Chapter 13, Emergency Stand Alone (ESA) System
and BLC 6660-01/-02/-03 Overview on page 125 in the publi-
cation System 6000 Overview for information about ESA.
Registrar Shows which registrar is currently registered. The options are:
Primary: The primary registrar is registered.
Secondary: The secondary registrar.
Down: Neither the primary or secondary registrar is
registered.
Hook Shows the hook state. The options are “On” or “Off”.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 414 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
Field Description
State Port state. The options are:
BUSY - Phone is off-hook and the user is hearing a busy
signal.
ROH - The receiver has been off hook a long time and the
BLC is generating a receiver offhook tone.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 415 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
Field Description
SIP profile SIP Profile name
Proxy Primary proxy server configured in this SIP profile.
Secondary Secondary proxy server configured in this SIP profile.
Proxy
Domain SIP Domain configured in this SIP profile.
This is the hostname or IP address for the domain part of the
Uniform Resource Identifiers (URI). If this information is
absent, this field defaults to the proxy. No domain is config-
ured by factory default.
Registrar Primary registrar configured in this SIP profile.
Secondary Secondary registrar configured in this SIP profile.
Registrar
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 416 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
Field Description
Registration This setting means that after the BLC registers the switch will
Timeout assume that it should disconnect after whatever period of
time has been configured if the BLC hasn’t reregistered.
The default registration timeout is one hour. The registration
timeout setting is dependent on the softswitch. If the soft-
switch wants to use another amount of time, the
softswitches timeout setting will be used.
The BLC will automatically reregister before the registration
expires.
Call Waiting Status of the call waiting feature (enabled or disabled) in this
SIP profile.
Three Way Status of the three way calling feature (enabled or disabled)
Calling in this SIP profile.
Caller ID Status of the caller ID feature (enabled or disabled) in this SIP
profile.
MWI Status of the message waiting indicator feature (enabled or
disabled) in this SIP profile.
Digit Map Digit map for this SIP profile.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 417 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Viewing Your SIP Configuration
Field Description
Port Voice port number
Display Portion of the port's URI that is displayed.
Username SIP username configured for this port.
Domain SIP Domain configured in this SIP profile.
This is the hostname or IP address for the domain part of the
Uniform Resource Identifiers (URI). If this information is
absent, this field defaults to the proxy. No domain is config-
ured by factory default.
Call Features Call features enabled on this port.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 418 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Digit Map Configuration
Symbol Result
0123456789 Identifies a specific digit
x Wildcard entries that represents any number
X between 0 and 9.
[digit digit] Two digits
[digit-digit] Two digits separated by hyphen ("-") match any
digit between and including the two.
[digit-digitdigit-digit] Two sets of digits separated by hyphen ("-") specify
two ranges of digits. Note that the digit ranges are
NOT separated by a comma. For example, the digit
map entry “[1-36-8]” signifies that digits 1, 2, 3, 6,
7 and 8 are accepted.
T Indicates that an specified time out period should
take place before automatic dialing starts
* Indicates the star key on the telephone.
. A period matches an arbitrary number, including
zero, of occurrences of the preceding entry.
A space between entries means “or”. For example,
the entry “4 5 6” means the digits “4” or “5” or “6”.
Note: Do not use the pound symbol (#) in a dial plan. Entering this key will
immediately terminate dialing and send the dialed digits to the softswitch.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 419 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
Digit Map Configuration
Table 20-13 below describes the digit maps shown in the above example:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 420 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
CLASS Feature Overview
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 421 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 20: Configuring SIP
CLASS Feature Overview
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 422 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Introduction
Chapter 21
Access Control Lists (ACLs)
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Ethernet ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
IP Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Displaying ACL and Access Group Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Security Filter Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Introduction
Security filters allow various layer 2 and layer 3 filters to be configured and
installed on a VLAN. Ingress filters can also be used in conjunction with security
filters to filter specific traffic from subscriber ports associated with the configured
VLAN. Ingress filtering is described in Chapter 23, IP Security Management (IPSM) on
page 439.
Individual security filters specific to a VLAN are listed in an Access Control List
(ACL). An ACL defines a VLAN access policy. Subscriber VLANs on a BLC are filtered
on interfaces through the use of configurable ACLs. This allows the administrator
to configure a new ACL set of security policies and then replace the existing, in use,
policy without opening up a potential security hole.
ACLs address several security issues related to a subscriber intentionally or
unintentionally sending unwanted or risky traffic onto the provider network. ACLs
are used to block the following types of traffic:
Windows related traffic, for example network and device discovery (NetBIOS or
NBT - NetBIOS over TCP/IP).
Address spoofing, for example sending packets into the network with a source
IP address that has not been assigned.
Ethernet ACL
An Ethernet ACL filter allows matching EtherTypes to pass and drops all others. It is
applied to a subscriber VLAN that has global significance. The global impact applies
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 423 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Introduction
only to inbound subscriber traffic on that VLAN. It does not effect outbound traffic
from Ethernet interfaces or Ethernet ring or access ports. Ethernet ACL
configuration is described on page 425.
IP ACL
An IP ACL filters components of the layer 3 IP protocol header as well as the layer
4 TCP/UDP protocol header. It is attached to a VLAN. IP ACL configuration is
described on page 427.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 424 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Ethernet ACLs
Ethernet ACLs
You can define multiple EtherTypes for a given ACL but you can only apply a single
ACL to a VLAN by using the subscriber ethernet access-group command.
ACLs cannot be altered when active (i.e. when attached to a VLAN). For information
about how to detach an Ethernet ACL from a VLAN please see section Detaching an
Ethernet ACL From a VLAN on page 426.
Note: This filter is optional, since an ARP filter is always added by default when an
IP EtherType filter is created.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 425 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Ethernet ACLs
For example:
occam(config)# access-list ethernet eth-acl-1 permit 0x5afaf
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 426 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
IP Access Control Lists
Note: The order in which you enter the filters is important as packets are tested
against the filter data base in the order in which they are defined. The first rule that
a packet matches will be the one that is obeyed. Care should be given to the filter
sequence entered.
Configuring an IP ACL
From Global Configuration Mode, enter the access-list ip command.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 427 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
IP Access Control Lists
VLAN: 3
Ethernet access group: none
IP access group: 5
Action Type Owner State Hits Vlan Etype Source IP Proto sPort dPort
Fwd Static MGMT Active 0 45 0x800 0.0.0.0/32 17 68 Any
Drop Static MGMT Active 0 45 0x800 Any 6 Any 137
Drop Static MGMT Active 0 45 0x800 Any 6 Any 138
Drop Static MGMT Active 0 45 0x800 Any 6 Any 139
Drop Static MGMT Active 0 45 0x800 Any 6 Any 445
Fwd Static MGMT Active 0 45 0x800 192.168.12.0/24 Any Any Any
Fwd Static SYSTEM Active - 45 0x806
Drop Static SYSTEM Active 458 45 Any
The order in which the filters are added is the order of precedence. In other words
the filter that matches first takes precedence over later matches. The following
example will permit all traffic even from all devices including those in subnet 10/8:
occam(config)# access-list ip 1 permit 0.0.0.0/0
occam(config)# access-list ip 1 deny 10.0.0.0/8
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 428 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
IP Access Control Lists
Note: The BVI only accepts ACLs that specify source IP subnet/host and protocol.
The ACL must not specify any TCP/IP interface numbers.
! everything. Make sure not to exclude yourself from access if you are telneted into
the BLC.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 429 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
IP Access Control Lists
2 Remove the access-list from a specific VLAN with the no subscriber ip access-
group command. Specify an access-list by name and an EPS VLAN number
between 2-122:
occam(config)# no subscriber ip access-group {acl-name} in {2-
122}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 430 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Displaying ACL and Access Group Information
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 431 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Displaying ACL and Access Group Information
If DHCP snooping is enabled, the packets are trapped (i.e., copied to the subscriber
management application) prior to the filtering process. Therefore, filters do not
have any effect on the DHCP traffic when DHCP relay or snooping is enabled. For
example, if the following filter is added, it would look like anything that was not
on the 192.168.12.0 network (or an ARP) would be dropped, including DHCP
discoveries. Since DHCP relay or snooping is enabled, the packets never make it to
the filter, therefore are not dropped and the client PC would get its IP address
which may later be filtered by the filter policy:
occam# show subscriber access-group
VLAN: 4
Ethernet access group: none
IP access group: ip-acl-5
Action Type Owner State Hits Vlan Etype Source IP Proto sPort dPort
Drop Static SYSTEM Active 183 45 Any
Fwd Static SYSTEM Active - 45 0x806
Fwd Static MGMT Active 163 45 0x800 192.168.12.0/24 Any Any Any
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 432 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Displaying ACL and Access Group Information
increment concurrently, (i.e., any full match filter will have its hit counter
incriminated). For example, an ACL matching 0/0 and 10/8 will have both hit
counters increment, since 0/0 subsumes 10/8. Precedence order determines which
filter action is taken (permit/deny).
You may configure an ACL to have hit counters on the static filters with the
following command from Global Configuration mode:
occam(config)# subscriber ip access-group {ip access-list} in
{VLAN ID} count
Dynamic ingress filters may not be configured to have hit counters.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 433 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Security Filter Configuration Examples
9 Allow all IP traffic from subnet 10.0.0.0/8 (assuming subscriber subnet is that
subnet):
occam(config)# access-list ip ip ip-acl-2 permit 10.0.0.0/8
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 434 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Security Filter Configuration Examples
Video VLAN
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
occam(config)#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 435 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Security Filter Configuration Examples
9 Allow all IP traffic from subnet 10.3.0.0/16 (assuming STB subnet is that subnet):
occam(config)# access-list ip ip-acl-3 permit 10.3.0.0/16
Data VLAN
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
occam(config)#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 436 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Security Filter Configuration Examples
9 Allow all IP traffic from subnet 10.4.0.0/16 (assuming data subnet is that
subnet):
occam(config)# access-list ip ip-acl-4 permit 10.4.0.0/16
Modem VLAN
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
occam(config)#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 437 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 21: Access Control Lists (ACLs)
Security Filter Configuration Examples
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 438 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
IPSM Feature Overview
Chapter 22
IP Security Management (IPSM)
In This Chapter:
IPSM Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
DHCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
ARP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Blacklisting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Ingress Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Problem Solution
DHCP Server from subscriber IP ACLs
DoS Attacks Blacklisting Agent
Network Neighborhood, through the ARP Proxy
whole neighborhood IP ACLs
MAC Spoofing DHCP Relay
IP Spoofing DHCP Relay and ARP Proxy
Worms, Viruses, Hackers DHCP Relay and ARP Proxy and IP
ACLs and Peer to Peer Traffic
Blocking
Note: Please refer to Chapter 21, Access Control Lists (ACLs) on page 423 for
information about how to configure IP and Ethernet ACLs
Associations
This chapter begins with a description of the associations database on page 442.
This database is dynamically built by DHCP and by static associations and is
primarily used by the ARP Proxy and ingress filtering features. This section also
describes how to display subscriber side network associations on page 442 and
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 439 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
IPSM Feature Overview
DHCP
DHCP snooping, Layer 2 Relay, and Layer 3 Relay configuration are described on
page 451. This can be used in conjunction with ARP proxy and ingress filters to
protect the network.
ARP Proxy
ARP Proxy configuration is described on page 464. ARP Proxy configured in
conjunction with either DHCP or static associations serves two purposes.
The first benefit of enabling ARP proxy is to reduce the amount of ARP traffic in
the network. The BLC caches network ARP responses to subscriber side devices.
When the BLC receives an ARP request from a subscriber device, it checks the ARP
cache.
When the BLC finds the ARP request in the cache it will proxy the response to the
device and not forward the ARP request into the network. When the BLC does not
find the ARP request in the cache, the ARP request will be forwarded into the
network.
When the BLC receives the ARP response, it will populate the ARP cache. The
response is not relayed to the subscriber. The subscriber device has to re-ARP for
the network device. When it does, the BLC will send back a proxy reply, as the
network device is now in the BLC's ARP cache. This serves to reduce the amount of
ARP traffic in the network.
The second benefit of enabling ARP proxy is that when the BLC receives an ARP
packet from a subscriber, and the IP or MAC address does not match the IP or MAC
address in the associations table on that port, the ARP packet will be dropped. Note
that when a subscriber changes its IP address and adds a static ARP entry for a
network side device, the BLC will still forward traffic for this device since it will not
ARP. To prevent this enable ingress filtering.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 440 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
IPSM Feature Overview
Blacklisting Agent
Configuration of the blacklisting agent is described on page 469. This feature
protects the BLC against DoS attacks that utilize certain network control packets.
Ingress Filters
Ingress filter configuration is described on page 473. Ingress filters are applied to
individual VLANs and are global to all Ethernet services on that VLAN. They are used
to filter out all traffic that does not match the associations database.
Ingress filters require that either some sort of DHCP or static associations be
configured on a Ethernet service. Since ingress filters are applied on a VLAN all
devices on that VLAN must have received an IP address via DHCP or have a static IP
address association. Ingress filters can be used with or without ARP proxy and/or
peer to peer traffic blocking. Ingress filters are installed using the associations
database the BLC has built. All traffic from the subscriber is compared to this filter.
When the traffic does not match the installed filter, it is dropped.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 441 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
Associations
The associations database contains information about devices in the network. This
database functions like an ARP cache and is built dynamically by DHCP or by static
associations. It is used primarily by the ARP Proxy and ingress filtering features.
When peer to peer traffic blocking is not enabled but ARP proxy is enabled, and a
subscriber side device ARPs for a network device within its subnet (when a network
device is beyond a subscribers side device’s subnet, the network device will ARP for
its gateway) the ARP agent will populate the network side associations table. There
are both subscriber side and network side associations.
Interface: Ethernet4
VLAN MAC Address IP Address Gateway Type Owner State
3 00:09:09:09:09:02 9.9.9.2/32 9.9.9.100 Static MGMT Active
The State field displays whether or not the MAC address has been pushed
down to the filter level inside the Ethernet subsystem. If you have
configured a static configuration with a wildcard MAC address (all zeros),
this field will show "not installed". If the device obtained a lease via DHCP
and the state field shows something other than "active" for a valid MAC
address (for example "not installed"), there is an error in your configuration.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 442 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
Age in seconds
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 443 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
Static Associations
A static association is an administratively created association. Various forms of
static associations can be created to support statically addressed residential or
business subscribers. You may create a host static association or a subnet static
association. These are described below.
A static association forces compliance to a static IP address or a static MAC address
or a wild card on the MAC address.
Static associations are configured in Service configuration mode with the associate
command.
Ethernet
occam(config-if-eth-service-<1-5>)# associate {mac-address} [ip-
address] [ip-mask] [default gateway]
DSL
occam(config-if-dsl-service-<1-4>)# associate {mac-address} [ip-
address] [ip-mask] [default gateway]
Note: The service must be shutdown before any changes will be made to the
associations table.
The MAC address may be valid or wild (all zeros). The gateway address may be
optional, depending if you are configuring a host or subnet static association. This
is described in detail below in the sections Host Static Associations on page 445 and
Subnet Static Associations on page 445. When peer to peer traffic blocking is
enabled a gateway address must be specified.
When a static association is configured one of the filter entries that is allocated in
the service with the command mac limit {1-64} is consumed.
The command mac limit {1-64} allows you to configure the maximum number of
MAC addresses, choosing a number between one and sixty-four. This command is
entered from Service Configuration Mode. This feature provides a way to limit the
number of usable devices a customer may have in their home. Each VLAN may have
up to sixty-four MAC addresses, including dynamic and static.
The default MAC limit for access profiles on a DSL platform is one. The default MAC
limit for access profiles on fiber platform is four.
In this example, up to four MAC addresses may be used on an VLAN:
occam(config-access-profile)# mac limit 4
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 444 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
the address of the gateway on the network is optional. When a gateway is spec-
ified in a static association a network association for the gateway (ARP-GW)
automatically created. This must be configured when the peer to peer traffic
blocking feature is enabled.
For example:
occam(config-if-eth-service-<1-5>)# associate 00:02:02:00:15:d5
192.168.35.235 255.255.255.255
the subnet mask is something other than "/32". Subnet masks "/24" or "/28" may
be used, for example.
the address of the gateway on the network must be specified when peer to peer
traffic is blocked. When a gateway is specified in a static association, a network
association for the gateway (ARP-GW) is automatically created. This is required
when the peer to peer traffic blocking feature is enabled.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 445 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
When you configure a subnet static association with the associate {mac-address}
[ip-address] [ip-mask] [default gateway] command:
the MAC address cannot be an explicit MAC address and must be a wildcard. For
example:
Note: Make sure that you have correctly configured the mac limit command to
provide enough filter entries, since the BLC will learn a MAC address for every
device in the extended subnet.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 446 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
INTERNET
Gateway address:10.1.1.1
VPT VPT
VPS
EPS RING VPS
VPS
BLC 6312
VPS
ROUTER B
10.1.1.3 10.1.1.5
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 447 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 448 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
INTERNET
Gateway address:10.1.1.1
VPT VPT
a. Occam(config-if-eth-service-<1-5>)#
associate 00:00:00:00:00:00 10.1.1.0
ONT 255.255.255.0 10.100.1.1
OR
b. Occam(config-if-eth-service-<1-5>)#
ROUTER B
associate 10:30:da:37:4b:1a 10.1.1.0
255.255.255.0 10.100.1.1
10.1.1.3 10.1.1.5
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 449 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Associations
Managing Associations
Removing static associations for all or a single Ethernet service may be done with
one of the following commands:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 450 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
DHCP Configuration
Occam Networks supports DHCP Snooping, Layer 2 Relay and Layer 3 Relay. Layer
2 Relay is the preferred DHCP mode when the server supports this option and is also
configured for Layer 2 Relay.
A PC or other device can request an IP address automatically from a DHCP server
by sending a broadcast DCHPDISCOVER packet. A BLC in between the PC and DHCP
server can use its DHCP agent to find out information about the MAC, IP address,
and default gateway. This information is stored in a local DHCP lease database and
is used for subsequent management decisions.
In conjunction with disabling MAC learning, DHCP snooping, Layer 2 Relay, and
Layer 3 Relay can help in preventing DoS attacks by limiting the IP traffic to a
specific MAC and VLAN. DHCP Server responses are trapped before being sent to
the subscriber device. All broadcasted DHCP packets on the network side are
trapped by each BLC. The BLC processes the packet when it is for a local subscriber
device. When the packet is not for a local subscriber device, it is dropped. Traffic
from a subscriber will NOT be filtered during the DHCP process unless the proper
ACLs are configured. Please refer to Chapter 21, Access Control Lists (ACLs) on page
423 for information about how to configure ACLs.
Note: DHCP snooping and Layer 2 Relay are attributes of the service VLAN, even
though the options are configured inside Access Profile Configuration Mode. Thus,
when two Ethernet services on the same VLAN have clients that use DHCP and one
has an access profile, snooping and/or Layer 2 Relay enabled and the other doesn't,
the first port will get an IP address and the second one will be dropped, as the BLC
will drop all DHCP packets. This caveat does not apply to DHCP Layer 3 Relay, which
is a per port configuration.
DHCP Leases
When a client acquires a lease from a server the BLC “snoops” the packets to learn
how long the lease is valid. This information is put into a lease database on the BLC
and is checked every five minutes. The MAC filter entry is active until the address is
purged when the lease expires.
Note: When a lease expires it may take up to five minutes for the DHCP agent to
recognize that the lease has expired and purge the address from the system.
Client leases are persisted to a flat text file on a compact flash. The directory name
is /cf/config/dhcp. The filename is appended with the slot number (i.e. leasedb-9) in
case blades are moved to different slots in the chassis. When the BLC is moved to a
new slot, no leases are restored when the system reboots. A new lease file is created
with the new slot number. The old lease database is destroyed.
Client leases are persisted to the compact flash once an hour so that when there is
a restart/reboot, the service is not interrupted when the BLC powers back up again.
Client leases are also persisted to the compact flash during the shutdown process.
On power up, leases are restored from a slot specific lease database file.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 451 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
DHCP Snooping
DHCP snooping is passive. The BLC snoops the packet to learn information about
the DHCP lease and forwards it out on the VLAN configured on the Ethernet service.
The BLC does not inject any information (such as the Circuit ID or Remote ID) into
the DHCP packet. DHCP snooping populates the associations table with the MAC,
IP and gateway addresses.
2 Enter Access Profile Configuration Mode. Create a profile by using the name for
a profile you want to create, or an existing profile you want to modify. Use the
no access-profile command to delete a profile:
occam(config)# access-profile profile-name
Layer 2 Relay
Layer 2 Relay will relay the modified DHCP packet into the network on the
subscriber’s VLAN. DHCP requests are sent into the network with unmodified Layer
2 headers, which may be broadcast or unicast. DHCP server responses are trapped
before being propagated to the subscriber device. All broadcasted DHCP responses
on the network side are trapped by each BLC. The BLC processes the response when
it is for a local subscriber device. When the packet is not for a local subscriber
device, it is dropped.
Snooping and Layer 2 Relay are attributes of the VLAN. You cannot have one access
profile with snooping and/or Layer 2 Relay enabled and another access profile with
snooping and/or Layer 2 Relay disabled on the same EPS VLAN on the same BLC.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 452 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
Layer 3 Relay
The BLC will insert the Option 82 parameters into the DHCP packet and then
forward them as unicast packets into the network on the BVI VLAN. When Layer 3
relay is enabled and the DHCP server is on a different subnet, you must enter the
server's IP address using the command dhcp server {server_ip}. This IP address must
be accessible through the BLC BVI interface IP address (i.e. you must be able to ping
the DHCP server's IP address from the BLC command line) because BLC must
maintain L3 connectivity with the server at all times. The BLC’s IP address resides on
the BVI interface which is configured on VLAN 2.
DHCP broadcast packets are trapped by the BLC and turned into unicast traffic all
the way to the server, reducing unuseful broadcast traffic on the subscriber’s
network. Having your server on a different network inaccessible from your
subscribers will prevent them from attempting DOS type of attack against the
server. DHCP Layer 3 Relay resets the giaddr field in the BOOTP header back to
0.0.0.0 when relaying packets back to the subscriber device at the same time it
strips the Option 82 parameters.
You can configure up to three redundant servers.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 453 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
2 Enter Access Profile Configuration Mode. Create a profile by using the name for
a profile you want to create, or an existing profile you want to modify. Use the
no access-profile command to delete a profile:
occam(config)# access-profile profile-name
3 Configure DHCP Layer 2 or Layer 3 Relay on a specific VLAN. The factory default
mode is “none”:
occam(config-access-profile)# dhcp mode l2relay
or
occam(config-access-profile)# dhcp mode l3relay
4 (Optional) A DHCP Relay Circuit ID string that identifies the port and Ethernet
service is inserted inside Option 82 by default. This string may be customized
with text or keywords to add additional information.
occam(config-access-profile)# dhcp circuit-id {text string}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 454 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
5 (Optional) Instruct the DHCP agent to insert a DHCP Relay Remote ID string as
a sub-option(3) inside Option 82
occam(config-access-profile)# dhcp remote-id {string}
6 When you have configured Layer 3 relay you must specify by IP address a server
that will receive copies of the DHCP/BOOTP relayed messages. You may
configure up to three servers by entering the command dhcp server repeatedly
occam(config-access-profile)# dhcp server {ip-address}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 455 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
To delete a server enter the command no dhcp server. For example, to delete the
server with the IP address 132.178.11.12, enter the command:
occam(config-access-profile)# no dhcp server 132.178.11.12
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 456 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
show dhcp clients: use this command to display information about DHCP
clients. Sample output is shown on page 459.
show dhcp clients summary: use this command to display information about
DHCP clients in a summarized format. Sample output is shown on page 459.
show dhcp clients information: use this command to display information DHCP
client information for a selected MAC address. Sample output is shown on page
459.
show dhcp clients statistics: use this command to display DHCP client statistics
for the selected MAC address. Sample output is shown on page 460.
show dhcp clients interface ethernet: use this command to display DHCP
client information for a selected Ethernet interface. Sample output is shown on
page 460.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 457 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 458 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
Interface: Ethernet3
VLAN Client IP Address State Persisted Lease Expiry
3 00:02:02:00:05:a6 192.168.35.129 Ack Update Thu Jan 1 16:12:07 2004
3 00:02:02:00:07:a0 192.168.35.130 Ack Update Thu Jan 1 16:12:03 2004
Use the show dhcp clients summary command to display DHCP client information
for all the interfaces in a summarized format. For example:
occam# show dhcp clients summary
Port VLAN # Clients
Ethernet21 4 0
Ethernet21 3 0
Ethernet21 2 1
Ethernet13 4 0
Ethernet13 3 2
Ethernet13 2 1
Ethernet3 4 0
Ethernet3 3 2
Ethernet3 2 1
Ethernet4 4 0
Ethernet4 3 1
Ethernet4 2 1
<output truncated>
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 459 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
Use the show dhcp clients statistics {VLAN number} {mac-address} to display
DHCP clients statistics for the selected MAC address. Enter the MAC address in the
format AA:BB:CC:DD:EE:FF.
The following example shows DHCP clients statistics for MAC address
00:02:86:30:05:f3:
occam# show dhcp clients statistics 5 00:30:da:33:7a:c7
Client: 00:30:da:33:7a:c7
Rx Discovers = 1
Rx Offers = 0
Rx Requests = 193
Rx Acks = 0
Rx Naks = 0
Rx Declines = 0
Rx Releases = 0
Rx Informs = 0
Tx Discovers = 0
Tx Offers = 1
Tx Requests = 0
Tx Acks = 193
Tx Naks = 0
Tx Declines = 0
Tx Releases = 0
Tx Informs = 0
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 460 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
<output truncated>
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 461 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
Note: This command displays information about the BLC’s DHCP leases and not the
client’s leases.
The following example shows sample output from the show dhcp lease command:
occam# show dhcp lease
Device bvi1:
IP: 192.168.4.167
Netmask: 255.255.255.0
Broadcast: 192.168.4.255
Network: 192.168.4.0
Next server 192.168.4.101
Gateway: 192.168.4.254
Nameservers: 192.168.2.1
Renewal time: Sun Jan 4 01:30:12 1970
Expiration time: Sun Jan 4 03:00:12 1970
Field Description
Device The interface to which this information pertains.
IP The IP address that was provided by the DHCP server.
(When the IP address displays “0.0.0.0” that signifys
that no DHCP server has responded to the DHCP
discovery requests)
Netmask The network mask that the DHCP server has provided.
This may be “0.0.0.0” when no DHCP server has been
contacted.
Broadcast The broadcast IP address to be used on this interface.
Network The subnetwork to which this interface belongs. This is
not actually returned by the DHCP server, but is calcu-
lated from the returned IP address and netmask
attributes.
Next Server The DHCP server IP address from which these configu-
ration parameters were obtained.
Gateway The default router that the DHCP server wants this
device to use when no more specific routing is avail-
able. This will cause a default route to be inserted into
the routing table.
Nameservers The DNS nameserver that the DHCP server wants this
device to use.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 462 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
DHCP Configuration
Field Description
Renewal Time The time at which this device will begin the lease
renewal process. Lease renewal involves the re-negoti-
ation of the IP addresses that it was assigned initially.
This device will attempt to renew its lease on this
address.
Expiration Time The time at which the lease for the assigned IP address
will expire when the lease is not renewed.
VLAN: 5
Server SIADDR
00:03:47:71:9a:f2 192.168.37.10
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 463 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
ARP Proxy
ARP Proxy
Note: In this section the term client refers to the receiver of the IP address.
ARP
Address Resolution Protocol (ARP) is a network protocol, which maps a network
layer protocol address to a data link layer hardware address. For example, ARP is
used to resolve IP address to the corresponding Ethernet address. A host in an
Ethernet network can communicate with another host, only when it knows the
Ethernet address (MAC address) of that host
ARP maintains the mapping between IP address and MAC address in a table in
memory called ARP cache.
ARP Proxy
Occam Networks supports ARP proxy for subscriber side devices. The ARP Proxy
feature adds a significant level of security to the network by intercepting and
validating all ARP packets coming from and going to a subscriber device. When a
subscriber sends an ARP request, the BLC tries to proxy a response out of a local
cache. When there is not enough information in the cache to do so, the BLC relays
the request into the network. When the BLC receives an ARP reply from the network
side, it populates the local ARP cache.
ARP Proxy prevents a subscriber device from masquerading as a default router by
replying to a broadcast ARP for the gateway from another subscriber device or by
generating a gratuitous ARP.
ARP proxy uses a subscriber associations database to identify local devices. This
database is populated either statically by the network administrator or dynamically
via DHCP, so some form of DHCP or static associations must be configured for this
feature to be used.
You may configure ARP proxy by itself or ARP proxy in conjunction with peer to
peer traffic blocking.
When only ARP proxy is enabled, the BLC will learn and cache network side devices
that subscribers ARP for. Once a network device is in the cache, the BLC will proxy
responses for these learned devices (to Ethernet subscribers) until the ARP cache
times out. The ARP cache time-out is a configurable option.
When DHCP is enabled or the static association has a gateway configured the BLC
will not allow the gateway to time out. When the gateway is about to time out and
there are current associations, the BLC will spoof an ARP request by using the
subscribers information, so that it can repopulate the ARP cache with the gateway
information. When there are no current associations (all subscribers are gone) the
gateway will time out.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 464 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
ARP Proxy
Note: When peer to peer traffic blocking is enabled, the DHCP server must provide
a default gateway. When you configure a static association you must also configure
a default gateway.
When peer to peer traffic blocking is enabled, peer to peer traffic is not allowed and
is forced upstream to the default gateway. The ARP agent will not respond whenthe
target device is on the same port as the requestor. When the subscriber does not
ARP (for example, when it has a static association) the BLC will not be able to force
the traffic up to the default gateway. Also, when ARP is enabled and the subscriber
uses DHCP to obtain an IP address or the BLC has a static association with a valid
MAC and IP, any ARP request that does not have a matching MAC/IP address to the
BLC's associations will be dropped.
When peer to peer traffic blocking is enabled, most upstream broadcast traffic is
blocked. DHCP and ARP traffic is transmitted. When peer to peer traffic blocking is
not enabled, upstream broadcast traffic may be disabled by configuring an
Ethernet filter in an ACL. This configuration is described in the section Ethernet ACLs
in Chapter 21, Access Control Lists (ACLs) on page 425.
Note: Many gateways may not want to forward packets received from an interface
when the target is on the same subnet as the sender and will send back a ICMP
Redirect message. This message informs the sending device that there is a more
efficient route to the destination. ICMP Redirect should be disabled on the gateway
when the peer to peer traffic blocking feature is enabled in the network.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 465 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
ARP Proxy
Ethernet:
occam(config)# subscriber broadcast flooding enable {VLAN ID}
occam(config)# subscriber broadcast flooding disable {VLAN ID}
For example, the following command disables broadcast flooding on VLAN 22:
occam(config)# subscriber access broadcast flooding disable 22
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 466 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
ARP Proxy
2 Enter Access Profile Configuration Mode. Create a profile by using the name for
a profile you want to create, or an existing profile you want to modify. Use the
no access-profile command to delete a profile:
occam(config)# access-profile profile-name
4 (Optional) Change the ARP cache timeout from the default value of 15 minutes.
The parameters are between one and 480 minutes:
occam(config-access-profile)# arp cache timeout {minutes}
5 Enter the command arp reply gateway when you are configuring ARP proxy in
conjunction with peer to peer traffic blocking. The command no arp reply
gateway, which is the factory default, causes the ARP agent to return the MAC
address of the target device that may or may not be the default gateway:
occam(config-access-profile)# arp reply gateway
OR
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 467 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
ARP Proxy
d Enter the command associate. The following table details what parameters
are mandator and which are optional:
mac-address Mandatory
ip-address Mandatory
IP-mask When this field is not specified it will
default to the host mask.
Mandatory when the peer to peer
traffic blocking feature is enabled.
default gateway IP-address Mandatory when the peer to peer
traffic blocking feature is enabled.
e You must always enter a MAC and IP address. When you configure ARP proxy
in conjunction with peer to peer traffic blocking you must enter the IP
address of the gateway:
occam(config-if-eth)# associate {mac-address} {ip-address}{IP-
mask} {default gateway IP-address}
7 If you enabled peer to peer traffic blocking in step 5 you may disable down-
stream broadcast traffic. Specify the VLAN for which you are configuring ARP
proxy:
occam(config)# subscriber broadcast flooding disable {1-122}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 468 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Blacklisting
Blacklisting
Occam Networks’ blacklisting agent protects the BLC against Denial of Service
(DoS) attacks that utilize certain network control packets. The blacklisting agent
monitors all interfaces on a BLC and shuts down ports that exceed a certain rate of
specific packet types over a specified period of time. The packet types are ARP,
DHCP and IGMP protocols. Blacklisting may only be enabled when these protocols
have been enabled. For example when IGMP is enabled and DHCP is not, blacklisting
will only be configured for IGMP.
You may configure both the maximum allowed rate and the interval during which
packets must exceed that rate to force action for each of these three protocols.
When a port is found to surpass the maximum rate you may configure that one of
the following actions will occur:
The Ethernet service will be shutdown and an alarm will be triggered. The port
will not be disabled and other Ethernet services on the port will not be affected.
For both options (alarm or Ethernet service shutdown) the offender will be
periodically re-evaluated. When the rate is found to be acceptable, a clearing alarm
will be triggered and when it was shut down, the Ethernet service will be enabled
again. When the port is still surpassing the configured traffic parameters, it will stay
in alarm mode or remain shutdown and in alarm mode, depending which option has
been configured. The port will keep being retested until it is eventually kept in
alarm mode or remain shutdown and kept in alarm mode.
You may configure these alarm and clearing events to be sent to OccamView.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 469 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Blacklisting
Configuring Blacklisting
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
occam(config)#
2 Enter Access Profile Configuration Mode. Create a profile by using the name of
a profile you want to create, or an existing profile you want to modify. Use the
no access-profile command to delete a profile:
occam(config)# access-profile profile-name
3 Configure the maximal acceptable packet rate limit for a protocol from a device
that is associated with an access profile:
occam(config-access-profile)# blacklist rate
limit{arp|dhcp|igmp} {PPS} {1-30} {1-10} {shutdown|alarm}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 470 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Blacklisting
Examples
The following command rate limits ARP requests to only one ARP request per
second on average. These ARP requests are monitored for 10 seconds. When
more than ten ARP requests are passed during these ten seconds, the Ethernet
service will be shutdown and an alarm will be issued. ARP requests must be
passed lower than the average rate of one ARP request per second for a period
of 20 seconds (10 * 2) before the Ethernet service is enabled again:
occam(config-access-profile)# blacklist rate limit arp 1 10 2
shutdown
The following command rate limits DHCP to only 4 packets per second on
average. The packets are monitored for 20 seconds. When more than 80 DHCP
packets are passed during those 20 seconds an alarm will be issued. Packets must
be passed lower than the average rate of 4 packets per second for a period of 40
seconds (20 * 2) before the Ethernet service is out of alarm mode:
occam(config-access-profile)# blacklist rate limit dhcp 4 20 2
alarm
The following command rate limits IGMP to only 10 packets per second on
average. The packets are monitored for 15 seconds. When more than 150
packets are passed during those 15 seconds, the Ethernet service will be shut-
down and an alarm will be issued. Packets must be passed lower than the
average rate of 10 packets per second for a period of 30 seconds (15 * 2) before
the Ethernet service is enabled again:
occam(config-access-profile)# blacklist rate limit igmp 10 15 2
shutdown
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 471 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Blacklisting
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 472 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Ingress Filters
Ingress Filters
Ingress Filters
Ingress filters are attached to VLANs and are applied to all Ethernet services on that
VLAN. Ingress filters are installed based on either DHCP activity or by configuring
static associations. Ingress filters will drop all traffic that does not match the
MAC/IP association.
When ARP proxy and peer to peer traffic blocking are enabled, the BLC will proxy
a response to the subscriber with the gateway MAC address and all traffic will be
sent through the gateway. Peer to peer traffic will be disabled.
When DHCP is enabled the BLC is able to filter based on MAC and IP addresses.
When these addresses don't match the information stored in an associations
database, the packet is discarded. These filters are installed automatically after each
device requests an IP address via DHCP.
Static associations of IP and MAC address for filtering may be configured through
the CLI. When used in conjunction with ARP Proxy and peer to peer traffic blocking,
the combined features become very effective at disabling layer two peer to peer
traffic.
Network filtering with wildcard MAC address for filtering may also be configured
through the CLI. This feature is applicable in a business service scenario where a
router is attached to the device.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 473 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Ingress Filters
Ingress filters are applied when the ACL is applied to a VLAN using the Global
Configuration mode command:
occam(config)# subscriber ip access-group {ACL} in {VLAN ID}
All devices in the associations database that are on the VLAN to which the ACL is
applied have their ingress traffic filtered. When an device is added or removed from
the associations database an ingress filter will be added or removed as well.
A device may be added to the association database via DHCP activity or by the
creation of a static association. When the device is configured with a subnet static
association you must configure a matching subnet when you enter the access-list
ip permit associations command. This command permits host addresses (i.e. /32) by
default.
For example, if you configure a static association with the command:
occam(config-if-eth-service-1)# associate 00:00:00:00:00:00
192.168.30.0 255.255.255.0 192.168.30.1
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 474 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Ingress Filters
match the filter, but the BLC will also respond to subscriber ARPs with the
gateway’s MAC address. and prevent peer to peer traffic.
Configuring an ACL With Ingress Filters
From Global Configuration Mode, enter the access-list ip command.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 475 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Ingress Filters
<output truncated>
Example One
This IP access list only permits associations. When applied to the VLAN, it will install
ingress filters for the addressed host for both DHCP and static associations. There is
no security filtering (i.e., NetBIOS)
occam(config)# access-list ip ip-acl-1 permit associations
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 476 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Ingress Filters
Example Two
In this example IP access list “ip-acl-10” permits DHCP client requests, drops DHCP
server responses, NetBIOS and CIFS traffic originating from the subscriber and
contains an ingress filter for host associations (DHCP or static):
occam(config)# access-list ip ip-acl-10 permit 0.0.0.0/32 udp 68
occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 udp 67
occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 tcp any 139
occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 138
occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 137
occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 445
occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 tcp any 445
occam(config)# access-list ip ip-acl-10 permit associations
Example Three
This example is similar to example #2, but it permits associations for a class C
subnet (/24) instead of for hosts. This type of filter would be typically used when
providing Ethernet service to a business. A static association with a class C subnet
would be configured on the Ethernet service:
occam(config)# access-list ip ip-acl-5 permit 0.0.0.0/32 udp 68
occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 udp 67
occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 tcp any 139
occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 138
occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 137
occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 445
occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 tcp any 445
occam(config)# access-list ip ip-acl-5 permit associations/24
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 477 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 22: IP Security Management (IPSM)
Ingress Filters
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 478 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Introduction
Chapter 23
Managed Multicast Via IGMP Proxy
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Interface Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Optional IP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Sample IGMP Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Configuring Managed Multicast Traffic Parameters on Ethernet Interfaces . . . . 485
Configuring Multicast Parameters on Ethernet Subscriber Interfaces . . . . . . . . . 486
Displaying Information About Your IGMP Configuration . . . . . . . . . . . . . . . . . . . 491
Introduction
The BLC supports managed multicast (IGMP v2 RFC 2236) via an IGMP (Internet
Group Management Protocol) proxy daemon. Occam networks uses IGMP proxy for
video traffic.
Router Interface
IGMP router interfaces are router facing ports. A router interface acts as a
subscriber to another IGMP device. It sends, joins or responds to queries.
Use the following CLI command from Ethernet Interface Configuration mode to
configure an interface as an IGMP router facing interface:
occam(config-if-eth)# igmp router [ip-address]
IGMP router interfaces are typically configured with the following EPS commands:
occam(config-if-eth)# eps access tagged
OR
occam(config-if-eth)# eps access untagged
Please see Chapter 9, Ethernet Interface Configuration on page 165 and Chapter 11,
Configuring an EPS Aggregation Ring Network on page 199 for information about
configuring EPS commands.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 479 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Interface Configuration Options
Passthrough Interface
Any multicast traffic received on a passthrough interface will be forwarded out all
other passthrough interfaces. All IGMP traffic received on a passthrough interface
will be forwarded out all other passthrough interfaces and all router interfaces.
Use the following CLI command from Ethernet Interface Configuration mode to
configure an interface as an IGMP passthrough interface:
occam(config-if-eth)# igmp passthrough [ip-address]
IGMP passthrough interfaces are typically configured with the EPS command:
occam(config-if-eth)# eps ring all
Host Interface
IGMP host interfaces are host facing ports and performs the host function defined
in RFC 2236. It prunes multicast traffic so that the only multicast groups forwarded
down that interface are those that have been specifically requested by one or more
hosts downstream.
Use the following CLI command from Ethernet Interface Configuration mode and
Access Profile Configuration modes to configure an interface as an IGMP host:
occam(config-if-eth)# igmp host [ip-address]
occam(config-access-profile)# igmp host [ip-address]
IGMP Version
IGMP v2 is the protocol currently supported and will continue to be the supported
protocol toward the customer's premise. However, a newer IGMP v3 has been
defined that provides more information. The BLC network will continue to operate
when the customer uses IGMP v2 but if the head end servers are using IGMP v3 the
BLC network can be provisioned to respond with a format of (*, G) addressing where
we will respond to any (*) source addressing and not to specific source addresses
when the double addressing is used.
Use the following CLI command from Ethernet Interface Configuration mode and
Access Profile Configuration modes to configure the IGMP version:
occam(config-if-eth)# igmp version {v2 | v3}
occam(config-access-profile)# igmp version {v2 | v3}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 480 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Optional IP Address Configuration
Default IP Address
The default value is no address specified. When this is the case the BVI's IP address
is used. To reset the address to default enter one of the following commands:
igmp host
igmp router
igmp passthrough
Recommended IP Address
The recommended value for the IP address is "0.0.0.0" when IGMP is configured in
an access profile. On Ethernet interfaces the IP address may remain unspecified (the
default is the BLC’s BVI IP address).
The exception to this recommendation may be when configuring an IGMP "router"
Ethernet interface when the upstream third party router expects IGMP reports to
originate from the video IP subnet configured on the router. If the IP address is
configured on ring Ethernet "passthrough" ports it SHOULD be configured to be the
same address on all passthrough ports on the BLC. If configured differently a BLC
will appear to be different IP devices at each VTP's/bookends.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 481 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Optional IP Address Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 482 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Sample IGMP Configurations
VIDEO C C
A
SOURCE BLC 6314 BLC 6314
B B
C C
BLC 6312
BLC 6312
C C
C
C
BLC 6312
BLC 6312
C
C
C BLC 6312 C
D D D
LEGEND
"A": ETHERNET INTERFACE CONFIGURED WITH THE COMMAND
occam(config-if-eth)# igmp router
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 483 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Sample IGMP Configurations
VIDEO C C
A
SOURCE BLC 6314 BLC 6314
B B
C C
BLC 6312
BLC 6312
C C
C C
BLC 6312 BLC 6312
C C
B B
C C
BLC 6312
D D D
LEGEND
"A": ETHERNET INTERFACE CONFIGURED WITH THE COMMAND
occam(config-if-eth)# igmp router
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 484 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Configuring Managed Multicast Traffic Parameters on Ethernet Interfaces
Passthrough Interface:
occam(config-if-eth)# igmp passthrough [ip-address]
4 Set the maximum allowed number of groups per interface, specifying a number
between 1 and 255. The factory default is 255:
occam(config-if-eth)# igmp group-limit {1-255}
Note: The multicast limit for the Aggregation BLC 6450 is 1000 streams,
providing more capacity in the Aggregation Ring for services to multiple Access
rings.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 485 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Configuring Multicast Parameters on Ethernet Subscriber Interfaces
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 486 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Configuring Multicast Parameters on Ethernet Subscriber Interfaces
2 Enter Access Profile Configuration Mode. Create a profile by using the name of
a profile you want to create, or an existing profile you want to modify. Use the
no access-profile command to delete a profile:
occam(config)# access-profile profile-name
3 Configure the VLAN ID. All traffic with no source IP address will be mapped to
this VLAN:
occam(config-access-profile)# eps vlan {3-122}
5 (Optional) Limit the number of groups on the port to which the profile is
attached. The factory default is 255.
occam(config-access-profile)# igmp group-limit {1-255}
Note: The multicast limit for the Aggregation BLC 6450 is 1000 streams,
providing more capacity in the Aggregation Ring for services to multiple Access
rings.
Note: You may later use the command override access-profile igmp group-
limit {1-255} from Ethernet Service Configuration mode to override the
number set in the access profile to which the service is attached. This command
is useful if an access profile is attached to a large number of ports and a change
needs to be made to a small number of them.
6 Assign a rate-limiting policy map to the access profile as an output policy, rate-
limiting all unicast traffic coming to the subscriber from the BLC. Specify the
policy map by name (as described in Chapter 14, Ethernet Subscriber Interfaces
in the section Defining a Unicast Rate Limiting Policy Map on page 286):
occam(config-access-profile)# service-policy output {policy-map-
name}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 487 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Configuring Multicast Parameters on Ethernet Subscriber Interfaces
7 Assign a rate-limiting policy map to the access profile as an input policy, rate-
limiting all unicast traffic coming from the subscriber to the BLC. Specify the
policy map by name:
occam(config-access-profile)# service-policy input {policy-map-
name}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 488 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Configuring Multicast Parameters on Ethernet Subscriber Interfaces
Use the command no match vlan {1-4094} to remove this VLAN association
from an Ethernet Service.
5 Optionally, remove static associations for all or a single VLAN with one of the
following commands:
Remove all static associations:
occam(config-if-eth-service-1)# delete static associations
Remove a single static association:
occam(config-if-eth-service-1)# no associate mac-address
6 Optionally, set maximum number of IGMP groups allowed, overriding the IGMP
group limit set in the attached access profile. This command and the other over-
ride access-profile commands may be useful if an access profile is attached to
a large number of ports and a change needs to be made to a small number of
them:
occam(config-if-eth-service-<1-5>)# override access-profile igmp
group-limit {1-255}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 489 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Configuring Multicast Parameters on Ethernet Subscriber Interfaces
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 490 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Displaying Information About Your IGMP Configuration
show multicast port summary: This command shows multicast information about
all the interfaces that are configured for multicast. The following example shows
sample output:
occam# show multicast port summary
Total streams open: 4
Port Mode Address Stream-limit Version Status
Ethernet5/1 PASSTHRU 192.168.21.101 unlimited IGMPV* Listener
Ethernet5/4 ROUTER 192.168.21.101 unlimited IGMPV2 Listener
Ethernet5/21 HOST 192.168.21.101 255 IGMPV2 Querier
Ethernet5/13 HOST 192.168.21.101 255 IGMPV2 Querier
Ethernet5/5 HOST 192.168.21.101 255 IGMPV2 Querier
Ethernet5/6 HOST 192.168.21.101 255 IGMPV2 Querier
Ethernet5/3 HOST 192.168.21.101 255 IGMPV2 Querier
Ethernet5/2 HOST 192.168.21.101 255 IGMPV2 Querier
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 491 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Displaying Information About Your IGMP Configuration
show multicast port ethernet: This command shows multicast information about
an Ethernet interface configured for multicast. The following example shows
sample output:
occam>show multicast port ethernet 1
Total streams open: 0
Port Mode Stream-limit Version Status
Ethernet5/1 PASSTHRU unlimited IGMPV* Listener
Rx pkts: 1244
Rx Reports: 1244
Rx Leaves: 0
Rx General Queries: 468
Rx Group Queries: 4
Rx unknown msg types: 0
Rx CRC Errors: 0
Filtered Src IP's: 0
Filtered Group's: 0
Tx pkts: 1254
Tx Reports: 1252
Tx Leaves: 2
Tx General Queries: 0
Tx Group Queries: 0
Suppressed Reports: 1
Group Query Timeouts: 0
occam>
show multicast port: This command shows multicast information about all
interfaces configured for multicast. The following example shows sample output:
occam>show multicast port
Total streams open: 4
Port Mode Stream-limit Version Status
Ethernet5/1 PASSTHRU unlimited IGMPV* Listener
Ethernet5/4 ROUTER unlimited IGMPV2 Listener
Ethernet5/21 HOST 255 IGMPV2 Querier
Group: 225.10.10.10
Member(s): 192.168.21.203
Ethernet5/13 HOST 255 IGMPV2 Querier
Ethernet5/5 HOST 255 IGMPV2 Querier
Ethernet5/6 HOST 255 IGMPV2 Querier
Ethernet5/3 HOST 255 IGMPV2 Querier
Group: 224.0.18.103
Member(s): 192.168.21.135
192.168.21.136
Group: 224.0.18.104
Member(s): 192.168.21.135
192.168.21.136
Group: 225.10.10.10
Member(s): 192.168.21.136
192.168.21.135
Group: 239.255.255.250
Member(s): 192.168.21.136
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 492 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Displaying Information About Your IGMP Configuration
192.168.21.135
Ethernet5/2 HOST 255 IGMPV2 Querier
occam>
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 493 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 23: Managed Multicast Via IGMP Proxy
Displaying Information About Your IGMP Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 494 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Introduction
Chapter 24
Configuring Circuit Emulation
Switching (CES)
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Choosing a T1 Line Framing Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Configuring Synchronous CES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Configuring Asynchronous CES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Terminating a CES Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Viewing Your CES Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Introduction
The BLC 6150-01, BLC 6246, BLC 6440-01, BLC 6640-01 and
BLC 6660-01/-02/-03 support Synchronous and Asynchronous CES. CES provides
methods of seamlessly transporting T1s across an Ethernet/IP network. CES
connections may be connected between any two T1 interfaces of supported BLC
platforms. The BLC 6440-01, BLC 6640-01 and BLC 6660-01/-02/-03 support up to
eight CES connections. The BLC 6150 and BLC 6150-01 support up to four CES
connections.
Synchronous CES
Synchronous CES is used to transport T1s with timing that is synchronous to the
BLC system timing. Therefore, Synchronous CES requires that all T1s of a BLC belong
to a common timing domain. BLC network clocks may synchronize using NSP or an
external BITS clock.
Asynchronous CES
Asynchronous CES embeds the T1 clocking information in the data stream to all for
the transport of T1s with timing that is asynchronous to the BLC network clock. As
a result, the BLC may be used to transport T1s that belong to separate timing
domains.
CES Applications
The intended application of CES is to provide transparent DS1 service between two
points within a BLC network.
Example applications include the following:
A PRI trunk between a CLASS 5 switch and a PBX.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 495 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Introduction
Bandwidth Requirement
CES sends a packet every 1/2 msec that contains:
100 bytes of payload
12 bytes RTP
8 bytes UDP
20 bytes IP
21 bytes Ethernet.
The total is 161 bytes, or 1288 bits. This is a rate of 2.576 Mbps
Configuration Restrictions
CES can only be configured on BLCs with T1s and gigabit Ethernet interfaces.
CES and MLPPP can not operate on the same BLC blade.
Due to the synchronous, low latency nature of the T1 interface, CES imposes
strict requirements for network jitter and latency. As a result, CES connections
may traverse a maximum of 80 gigabit switch nodes.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 496 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Choosing a T1 Line Framing Format
When transporting voice trunks (or any T1s using Robbed Bit Signaling (RBS)),
CES framing must never be set to unframed.
Unchannelized T1s (sometimes called "data" T1s) most commonly use ESF
framing.
In rare cases, CES is used to transport a data T1 which uses a proprietary framing
format. In this situation you must configure the T1 as UNFRAMED. As noted in
the configuration restrictions above, T1s in unframed mode may not be config-
ured as the primary or secondary clock source of the BLC with the network-
clock-select command.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 497 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Choosing a T1 Line Framing Format
Figure 24-1: PRI (Primary Rate Interface) between a Class 5 switch and a PBX
Framing in this example should be configured as ESF, and the linecoding should be
configured as B8ZS.
IP GigE - EPS
IP GigE - EPS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 498 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 499 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
ANOTHER T1 INTERFACE IS
CONFIGURED AS THE SECONDARY
SOURCE FOR CLOCKING
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 500 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
There are several ways to configure NSP clocking in a Synchronous CES network. All
CES endpoints may be configured to share a single active NSP clock source
throughout the ring and to be on the same NSP domain. All remote devices see the
same clock. Figure 24-5 shows an example of this option.
NSP TX NSP RX
DOMAIN 1 DOMAIN 1
T1 #1 INFO
CLOCKING INFO CLOCKING INFO
FROM SWITCH FROM BLC TO
TO BLC T1 T1 #1 CHANNEL BANK
T1
#2
IN
FO
CLOCKING INFO
FROM BLC TO
T1 #2 CHANNEL BANK
CHANNEL BANK
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 501 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
BLCs on the same EPS ring may belong to separate timing domains. In the example
below, the first timing domain (NSP group 1) is used to provide clock from the Class
5 switch to the channel bank. The second timing domain (NSP group 2) is used to
transport clock from router #1 to router #2.
VPT 1 VPT 2
NSP TX NSP RX
DOMAIN 1 DOMAIN 1
T1 #1 INFO
CLOCKING INFO CLOCKING INFO
FROM SWITCH FROM BLC TO
TO BLC T1 #1 T1 #1 CHANNEL BANK
T1 #2 INFO
T1 #2 T1 #2
ROUTER #1 ROUTER #2
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 502 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 503 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
CLOCKING INFO
ON T1 LINES
DMS 100 CONFIGURED AS
CLASS 5 "PRIMARY" AND
SWITCHES "SECONDARY"
CHANNEL BANKS
1 1
2 IP GigE - EPS 2
3 3 4
5 4
6 5
7 67
8 (CLOCKING INFO) 8
T1 INTERFACES BLC "A" BLC "B" T1 INTERFACES
IP ADDRESS: IP ADDRESS:
10.10.10.1 10.10.10.2
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 504 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
Configuration Steps
Use the steps below to configure BLC “A” and BLC “B” (as shown in Figure 24-4) in a Synchronous
CES network. Steps that are used by both BLC “A” and BLC “B” are shown in the middle of the table,
under both columns. Steps that are specifically used by one or the other BLC are shown under the
right or left column.
BLC A BLC B
1. Enter Global Configuration Mode:
Occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
2. (Optional) Configure CES to run on BVI 1 or BVI 2. Please see Chapter 8, Configuring Multi-
homing on page 153 for more information about how to configure multihoming:
occam(config)# ces interface bvi {1,2}
3. (Optional) Configure RTP to run on BVI 1 or BVI 2:
occam(config)# rtp interface bvi {1,2}
Note: If you run RTP on BVI 2 you will need to also configure your CES
links to run on BVI 2.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 505 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
BLC A BLC B
6. Specify the IP address or hostname of BLC 6. Specify the IP address or hostname of
“B” and the T1 interface on BLC “B”. Sepa- BLC “A” and the T1 interface on BLC “A”.
rate the IP address or hostname and the T1 Separate the IP address or hostname and
interface number with a space: the T1 interface number with a space:
Occam(config-if-serial)# ces Occam(config-if-serial)# ces
connect-to {BLC “B” IP-address or connect-to {BLC “A” IP-address or
hostname} {T1 interface number on hostname} {T1 interface number on
BLC “B”} BLC “A”}
For example, to connect to T1 line “2” on For example, to connect to T1 line “1” on
BLC “B” in Figure 24-7 enter the command: BLC “A” in Figure 24-7 enter the
Occam(config-if-serial)# ces command:
connect-to 10.10.10.2 2 Occam(config-if-serial)# ces
connect-to 10.10.10.1 1
The ces connect-to command cannot be
entered if the T1 interface is already The ces connect-to command cannot be
enabled. entered if the T1 interface is already
enabled.
7. Configure this T1 to receive clocking from 7. Configure this T1 as a source of clocking
the external equipment. This T1 must either for the external equipment. The T1 will
be used for the BLC's Network clock, or be be synchronous to the Network clock
externally synchronized to the T1 the BLC is option for the BLC:
using for Network clock: Occam(config-if-serial)#
Occam(config-if-serial)# service- service-module t1 clock source
module t1 clock source line internal
8. Configure the framing format. Please refer to the section Choosing a T1 Line Framing
Format on page 497 to help you decide which framing format to specify for your
configuration:
Occam(config-if-serial)# service-module t1 framing {esf | sf | unframed}
9. Enter the linecode type, specifying alternate mark inversion (AMI) or binary 8 zero substi-
tution (B8ZS). This command is optional if you select “b8zs”, the factory default. The
linecode on the T1 interface on BLC “A” and BLC “B” must match:
Occam(config-if-serial)# service-module t1 linecode {ami | b8zs}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 506 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
BLC A BLC B
10. (Optional) Specify the Line Build Out (LBO) format. The options are:
CSU_0_L CSU 0 dB (low sens)
CSU_0 CSU 0 dB
CSU_0_H CSU 0 dB (high sens)
CSU_7_L CSU -7.5 dB (low sens)
CSU_7 CSU -7.5 dB
CSU_7_H CSU -7.5 dB (high sens)
CSU_15_L CSU -15 dB (low sens)
CSU_15 CSU -15 dB
CSU_15_H CSU -15 dB (high sens)
CSU_22_L CSU -22 dB (low sens)
CSU_22 CSU -22 dB
CSU_22_H CSU -22 dB (high sens)
The first word is a key, anything after is the value attached to that key. In the above
example, 'CES-mode' is the key. You can have several info messages and you can remove
any of them by using the command no info {key}'. There is no limit on the text length,
but you cannot use any of the following characters: TAB, <enter>, '?', '!'.
12. Enable the T1 port:
Occam(config-if-serial)# no shutdown
13. Exit Serial Interface Configuration Mode and return to Global Configuration Mode:
Occam(config-if-serial)# exit
14. Repeat steps 2 through 12 for each T1 interface you wish to configure for CES.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 507 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Synchronous CES
BLC A BLC B
15. Set the CES application’s DSCP value for packets that it generates. The parameters are
between 0 and 63. This command has no effect on packets that the CES application
receives from peer applications and takes effect immediately. It is described more fully in
Chapter 33, Differentiated Services (Diffserv) on page 677:
occam(config)# ip diffserv dscp protocol CES {0-63}
16. Exit Global Configuration Mode and save your configuration:
Occam(config)# exit
Occam# copy running-config startup-config
Building configuration....
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 508 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Asynchronous CES
Note: It is vial that the integrity of the clock be maintained from the source to the
receiver. If it is not, data will be lost.
Figure 24-8: Asynchronous CES Network
VPT 1 VPT 2
T1 #1 and #2 INFO
CLOCKING INFO THROUGH EPS RING CLOCKING INFO
FROM SWITCH FROM BLC TO
TO BLC T1#2 T1 #2 CHANNEL BANK
ROUTER #1 ROUTER #2
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 509 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Asynchronous CES
T1#1 T1#1
IP GigE - EPS
IP ADDRESS: IP ADDRESS:
123.45.67.8 123.45.67.9
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 510 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Asynchronous CES
Configuration Steps
Use the steps below to configure BLC “C” and BLC “D” (as shown in Figure 24-9) in
an Asychronous CES network. Steps that are used by both BLC “C” and BLC “D” are
shown in the middle of the table, under both columns. Steps that are specifically
used by one or the other BLC are shown under the right or left column.
BLC A BLC B
1. Enter Global Configuration Mode:
Occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
2. (Optional) Configure CES to run on BVI 1 or BVI 2. Please see Chapter 8, Configuring Multi-
homing on page 153 for more information about how to configure multihoming:
occam(config)# ces interface bvi {1,2}
3. (Optional) Configure RTP to run on BVI 1 or BVI 2:
occam(config)# rtp interface bvi {1,2}
Note: If you run RTP on BVI 2 you will need to also configure your CES links
to run on BVI 2.
4. Enter Serial Interface Configuration Mode, 4. Enter Serial Interface Configuration Mode,
specifying a T1 interface port number. specifying a T1 interface port number.
CES will be performed between the T1 CES will be performed between the T1
interface configured on this BLC and the T1 interface configured on this BLC and the
interface configured on BLC “D” in Step 2 in T1 interface configured on BLC “C” in Step
the column to the right: 2 in the column to the left:
Occam(config)# interface serial Occam(config)# interface serial
{T1-interface-number} {T1-interface-number}
For example, to connect T1 interface “1” on For example, to connect T1 interface “2”
BLC “C” to T1 interface 2 on BLC “D”, enter on BLC “D” to T1 interface 1 on BLC “C”,
the command: enter the command:
Occam(config)# interface serial 1 Occam(config)# interface serial 2
To connect T1 interface “4” on BLC “C” to T1 To connect T1 interface “5” on BLC “D” to
interface 5 on BLC “D”, enter the command: T1 interface 4 on BLC “C”, enter the
Occam(config)# interface serial 4 command:
Occam(config)# interface serial 5
5. Enable CES mode on the T1 interface:
Occam(config-if-serial)# mode ces
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 511 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Asynchronous CES
BLC A BLC B
5. Specify the IP address or hostname of BLC 5. Specify the IP address or hostname of BLC
“D” and the T1 interface on BLC “D”. Sepa- “C” and the T1 interface on BLC “C”. Sepa-
rate the IP address or hostname and the T1 rate the IP address or hostname and the T1
interface number with a space: interface number with a space:
Occam(config-if-serial)# ces Occam(config-if-serial)# ces
connect-to {BLC “D” IP-address or connect-to {BLC “A” IP-address or
hostname} {T1 interface number on hostname} {T1 interface number on
BLC “D”} BLC “C”}
For example, to connect to T1 line “2” on For example, to connect to T1 line “1” on
BLC “D” in Figure 24-7, enter the command: BLC “C” in Figure 24-7, enter the
Occam(config-if-serial)# ces
connect-to 10.10.10.4 command:
Occam(config-if-serial)# ces
connect-to 10.10.10.3 1
To connect to T1 line “5” on BLC “D” in
Figure 24-7, enter the command: To connect to T1 line “4” on BLC “C” in Figure
Occam(config-if-serial)# 24-7, enter the command:
ces connect-to 10.10.10.4 5
Occam(config-if-serial)#
ces connect-to 10.10.10.3 4
6a. Typically this T1 should be set to “async- 6. Configure this T1 to be the source of clock
line” in order to receive clocking from the for the external equipment. The T1 will be
external equipment. The T1 local clock will generating this clock from the timing
be used for the local T1 transmitter and recovered from the remote T1:
transmitted across the network to the Occam(config-if-serial)# service-
remote: module t1 clock source async-
internal
Occam(config-if-serial)# service-
module t1 clock source async-line
7. Configure the framing format. Please refer to the section Choosing a T1 Line Framing Format
on page 497 to help you decide which framing format to specify for your configuration:
Occam(config-if-serial)# service-module t1 framing {esf | sf | unframed}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 512 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Asynchronous CES
BLC A BLC B
8. Specify the Line Build Out (LBO) format. The options are:
CSU_0_L CSU 0 dB (low sens)
CSU_0 CSU 0 dB
CSU_0_H CSU 0 dB (high sens)
CSU_7_L CSU -7.5 dB (low sens)
CSU_7 CSU -7.5 dB
CSU_7_H CSU -7.5 dB (high sens)
CSU_15_L CSU -15 dB (low sens)
CSU_15 CSU -15 dB
CSU_15_H CSU -15 dB (high sens)
CSU_22_L CSU -22 dB (low sens)
CSU_22 CSU -22 dB
CSU_22_H CSU -22 dB (high sens)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 513 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Configuring Asynchronous CES
BLC A BLC B
13. Set the CES application’s DSCP value for packets that it generates. The parameters are
between 0 and 63. This command has no effect on packets that the CES application receives
from peer applications and takes effect immediately. It is described more fully in Chapter
33, Differentiated Services (Diffserv) on page 677:
occam(config)# ip diffserv dscp protocol CES {0-63}
14. Exit Global Configuration Mode and save your configuration:
Occam(config)# exit
Occam# copy running-config startup-config
Building configuration....
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 514 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Terminating a CES Connection
Note: If a PG (Path Group) switchover occurs in an EPS ring and the CES traffic is
switched to a different PG, there will be a brief increase in the errors seen in the
CES Summary command.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 515 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Viewing Your CES Configuration
1 0 0 0 0 2 0 1 0
2 0 0 0 0 0 0 0 0
3 0 0 0 0 0 0 0 0
4 0 0 0 0 2 0 1 0
5 0 0 0 0 2 0 1 0
BLC_B#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 516 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Viewing Your CES Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 517 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Viewing Your CES Configuration
1 164580908 164580909
2 164619000 164580493
3 164581389 164581389
BLC-D#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 518 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Viewing Your CES Configuration
Field Description
state IDLE - Startup state that will not be seen unless
the DSP core is dead.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 519 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 24: Configuring Circuit Emulation Switching (CES)
Viewing Your CES Configuration
Field Description
too_far The number of packets with a sequence number
that is too far to use.
underflow The number of times the jitter buffer has
underflowed.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 520 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Introduction
Chapter 25
Configuring MGCP/VoIP
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Configuring a Voice Profile For Delivering POTS Over VoIP . . . . . . . . . . . . . . . . . . 523
Configuring a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Configuring MGCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Blocking New Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Displaying Voice Port, Profile and MGCP/VoIP Configuration Information . . . . . 541
Introduction
This chapter describes how to configure MGCP/VoIP services on the following BLCs:
BLC 6150-01
BLC 6151-01
BLC 6246
BLC 6252-03
The BLCs deliver standard telephony Lifeline POTS services, acting as line access
gateways by converting the analog voice traffic to VoIP with MGCP signaling for
transport through a BLC 6000 system. At the Central Office, the voice traffic can
be handed directly to a Next Gen/softswitch platform, or a BLC 6000 COT that
provides standard GR-303 or TR-08/connections to a Class 5 switch.
Note: POTS and CES enabled BLCs support multihoming. These BLCs feature a
default management BVI and also support the ability to create a dynamic second
BVI. This second BVI allows you to separate RTP, SIP or MGCP traffic onto a new
VLAN. Voice related protocols may be bound to either BVI. Please see Chapter 8,
Configuring Multihoming on page 153 for information about how to configure
multihoming.
How to configure a voice profile for delivery POTS over VoIP (page 523)
How to enable a voice port and attach a profile to the port (page 531).
This section also describes how to configure unbalanced ringing on the voice
port. (page 532).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 521 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Introduction
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 522 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Profile For Delivering POTS Over VoIP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 523 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Profile For Delivering POTS Over VoIP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 524 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Profile For Delivering POTS Over VoIP
2 Enter Voice Port Profile Configuration Mode with the voice-profile pots voip
command. Create a profile by using the name of a profile you wish to create or
an existing profile you wish to modify. Each voice port profile must have a
unique name:
occam(config)# voice-profile pots voip <profileName}
For example, if a Voice Profile named “mgcp_new” was being configured the
command would be:
Occam(config)# voice-profile pots voip mgcp_new
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 525 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Profile For Delivering POTS Over VoIP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 526 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Profile For Delivering POTS Over VoIP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 527 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Profile For Delivering POTS Over VoIP
Codec-list: occam(config-profile)profile-name#
Preferred coder-decoders (codecs) used codec-list (g711ulaw, g726-32K-pt2, g726-
during call compression. The order entered 32k}
determines the priority order of the codecs.
Codec-Options: occam(config-profile)profile-name#
Configures the jitter delay and packetiza- codec-options {g711ulaw, g726-32K-pt2,
tion options for codecs. g726-32k}
Jitter Delay: occam(config-voice-codec)#
Specifies jitter buffer delay in 5 msec jitter-delay {10,..110}
increments.
First use the “codec-options” command to
enter Voice Profile Codec configuration
mode. From this configuration mode you
may enter the “jitter-delay” command.
Packetization: occam(config-voice-codec)#
Selects the packetization period value in packetization {15 | 10 | 20 |40}
milli-seconds.
First use the “codec-options” command to
enter Voice Profile Codec configuration
mode. From this configuration mode you
may enter the “packetization” command.
Modem Codec Bypass: occam(config-profile)profile-name# modem-
Configures the modem-codec-bypass as: codec-bypass {enabled, disabled}
disabled - No codec bypass
enabled - Modem codec bypass functions
are configured to follow the settings of the
echo-tone-disabler command.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 529 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Profile For Delivering POTS Over VoIP
Building configuration....
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 530 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Port
2 Enter Voice Configuration Mode and specify the voice interface number
(between 1 and 48) you want to configure:
Occam(config)# voice-port {1-48}
3 Confirm that the voice port mode is set as MGCP, the system default:
occam(config-voice)# mode mgcp
5 (Optional) Attach descriptive text to the voice interface profile (for example
“Associated with 123 Main Street”):
Occam(config-voice)# description descriptive-text
6 Voice interfaces are shutdown by default. To enable the interface enter the no
shutdown command:
Occam(config-voice)# no shutdown
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 531 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Port
2 Enter Voice Configuration Mode and specify the voice interface number
(between 1 and 48) on which you want to configure unbalanced ringing:
Occam(config)# voice-port {1-48}
2 Enter Voice Configuration Mode and specify the voice interface number
(between 1 and 48) on which you want to configure unbalanced ringing:
Occam(config)# voice-port {1-48}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 532 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring a Voice Port
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 533 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring MGCP
Configuring MGCP
Note: When MGCP is referred to in the configuration steps below, Network-based
Call Signaling (NCS) is understood to also apply, except where otherwise noted.
2 Specify the IP address or domain name of a BLC 6640-01 as a primary call agent.
The default interface is 2727. As the BLC 6640-01 can only use interface 2727
you should not change the interface number from this default value.
Note: When using hostnames, the hostname IP mapping must be either be
resolvable through DNS or should be set locally using the command ip host.
Occam(config)# mgcp call-agent {ip address| hostname} [port]
3 Optionally you may specify the IP address or domain name of another BLC 6640-
01 as a secondary call agent. As with the first call agent, you should not change
the interface number from the default value.
Occam(config)# mgcp call-agent secondary {ip address| hostname}
[port]
6 (Optional) Set the MGCP application’s DSCP value for packets that it generates.
The parameters are between 0 and 63. This command has no effect on packets
that the MGCP application receives from peer applications and takes effect
immediately. It is described more fully in Chapter 33, Differentiated Services
(Diffserv) on page 677:
occam(config)# ip diffserv dscp protocol MGCP {0-63}
7 (Optional) Set the RTP application’s DSCP value for packets that it generates. The
parameters are between 0 and 63. This command has no effect on packets that
the RTP application receives from peer applications and takes effect immedi-
ately. It is described more fully in Chapter 33, Differentiated Services (Diffserv) on
page 677:
occam(config)# ip diffserv dscp protocol RTP {0-63}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 534 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring MGCP
occam(config)# exit
occam# copy running-config startup-config
Building configuration....
9 Enter the ping command with the BLC 6640-01’s IP address. MGCP can’t be
started until the BLC 6640-01 can be reached on the network:
Occam# ping {ip address| hostname}
11 Use any of the commands described in Table 25-2 to change the default MGCP
settings. If you do not wish to change any settings proceed to step 7.
Default:3000 milliseconds
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 535 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring MGCP
Default: Disabled
Default: Disabled
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 536 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring MGCP
Default: Disabled
Note: This option is needed if the CA is also using
a Media Server to mix audio streams. Vocal Data,
Broadsoft and Sonus, New Jersey are among the
CA’s that require the BLC to be configured with
this command.
Default: Enabled
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 537 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring MGCP
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 538 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Configuring MGCP
mgcp profile ncs Specify the operating profile for the Media
no mgcp profile Gateway as Network-based Call Signaling (NCS).
The “no” version of this command returns the
profile to the default value of MGCP
Default: Disabled (MGCP is default)
12 Initiate MGCP. Do not change the local UDP interface parameter from it’s
default value of 2427:
Occam(config)# mgcp
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 539 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Blocking New Calls
Note: This command will only work if the VoIP endpoints are not nailed up.
Therefore, this command will have no effect between a BLC 6150-01, BLC 6151-01,
or BLC 6252-03 and a BLC 6640-01 configured for TR-08 interoperability. This
command will block new calls between a BLC 6150-01, BLC 6151-01, BLC 6152-01,
or BLC 6252-03 and a BLC 6640-01 configured for GR-303 interoperability.
occam(config)# mgcp block-newcalls
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 540 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Displaying Voice Port, Profile and MGCP/VoIP Configuration Information
show voice dsp: displays the current status of all digital signal processor (DSP)
voice channels.
show voice power [port-number]: use this command to measure in real time the
transmit and receive signal power on one or all voice ports. If an interface
number is not specified, the power of all interfaces is displayed. Power measure-
ment is displayed in dBm0 (equal to a digital milliwat) and is taken after
adjustment by output-gain and input-gain parameters.
Transmit power (TX) is defined as power going into the network. The transmit
power meter continues to measure even when the port is onhook.
Receive power (RX) is defined as power going out of the network.
show voice profile [voice profile-name]: use this command to display informa-
tion about a specified voice profile. If a voice profile is not specified by name,
information about all voice profiles is displayed.
show mgcp connection: use this command to display the active MGCP
controlled connections and which port on the BLC 6640 is the endpoint for each
call.
show mgcp endpoint: use this command to display the active MGCP controlled
endpoints and verify which voice ports have been bound to MGCP.
show mgcp statistics: use this command to display MGCP statistics for received
and transmitted messages.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 541 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 25: Configuring MGCP/VoIP
Displaying Voice Port, Profile and MGCP/VoIP Configuration Information
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 542 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Introduction
Chapter 26
Configuring Cross-Connect Modes
on the BLC 6150-01 and the
BLC 6246
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Configuring a T1 Interface for Cross-Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Configuring Cross-Connect Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Configuring Cross-Connect Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Attaching a Profile to a Voice Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Displaying Voice Port and Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Introduction
The cross- connect modes available for configuration on the BLC 6150-01 and BLC
6246 are:
Cross-Connect Voice Clear Channel Mode: This mode is used for such applica-
tions as Primary Rate Interface (PRI), and Signaling System 7 (SS7) in a setting
where a DS0 has no interference due to signaling. Signaling must take place on
a separate channel.
Cross-Connect Voice Single Party Mode: This mode is used to configure a cross
connection between a GR-303 POTS Call Reference Value (CRV) and a TR-08
channel bank single party card. Configuration of the BLC 6150 and BLC 6150-
011 for SIngle Party Voice Cross-Connect is described in this chapter.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 543 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring a T1 Interface for Cross-Connect
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 544 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring a T1 Interface for Cross-Connect
7 (Optional) Specify Binary 8 Zero Substitution (b8zs) or AMI (ami) as the line code
format. The factory default is B8ZS:
occam(config-if-serial)# service-module t1 linecode {b8zs |ami}
10 (Optional) Enable the BLC 6150-01 to generate and detect remote (yellow)
alarms:
occam(config-if-serial)# service-module t1 remote-alarm-enable
The first word is a key, anything after is the value attached to that key. In the
above example, 'cross-connect-mode' is the key. You can have several info
messages and you can remove any of them by using the command no info
{key}'. There is no limit on the text length, but you cannot use any of the
following characters: TAB, <enter>, '?', '!'.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 545 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 546 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 547 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 548 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 549 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 550 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 551 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 552 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
Note: The configuration for any single DS0 must match between the BLC 6150-
01/6246 and the BLC 6640-01. However not all DS0s on a T1 will necessarily be
assigned to the same profile.
1 Enter Global Configuration mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 553 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
3 Configure the Cross Connect Profile Parameters, referring to Tables 26-1 for
information about the profile’s default values.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 554 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
transparent2833:Utilize transparent
RFC2833 RTP mode. This is the factory
default setting for the DS0 Cross-
Connect Voice and the Cross-Connect
Voice CAS profiles.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 555 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 556 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
Jitter Delay - Specifies jitter buffer delay in After you select a codec to configure by
5 msec increments. entering the command codec-option you may
configure the jitter delay value. When you have
finished configuring the codec’s parameters
enter the exit command.
occam(config-profile)profile-name#
codec-option {codec-name}
occam(config-voice-codec)# jitter-
delay {10,..110}
occam(config-voice-codec)# exit
occam(config-profile)profile-name#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 557 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Configuring Cross-Connect Profiles
occam(config-profile)profile-name#
codec-option {codec-name}
occam(config-voice-codec)#
packetization {15 | 10 | 20 |40}
occam(config-voice-codec)# exit
occam(config-profile)profile-name#
Modem Codec Bypass: occam(config-profile)profile-name#
modem-codec-bypass {enabled, disabled}
Configures the modem-codec-bypass as:
disabled - No codec bypass
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 558 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Attaching a Profile to a Voice Port
2 Enter Voice Port Configuration Mode and specify a voice port number between
49 and 144 to configure:
occam(config)# voice-port {49-144}
4 The port is shutdown by default. To enable the port enter the command no
shutdown:
occam(config-voice)# no shutdown
5 (Optional) Attach descriptive text to the voice port profile (for example “Asso-
ciated with 123 Main Street”):
occam(config-voice)# description description-text
For example:
Occam(config-voice)# info attached-profile bronze
The first word is a key, anything after is the value attached to that key. In the
above example, 'attached-profile' is the key. You can have several info messages
and you can remove any of them by using the command no info {key}'. There
is no limit on the text length, but you cannot use any of the following charac-
ters: TAB, <enter>, '?', '!'.
8 Repeat steps 2 through 6 for each port to which you wish to attach a cross-
connect profile.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 559 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246
Displaying Voice Port and Profile Information
show voice power {port-number}: use this command to measure in real time the
transmit and receive signal power on one or all voice ports. If an interface
number is not specified, the power of all interfaces are displayed. Power
measurement is displayed in dBm0 (equal to a digital milliwat) and is taken after
adjustment by output-gain and input-gain parameters.
Transmit power (TX) is defined as power going into the network. The transmit
power meter continues to measure even when the port is onhook.
Receive power (RX) is defined as power going out of the network.
show voice list-of-profiles: use this command to display the names of existing
voice profiles
show voice profile [voice profile-name]: use this command to display informa-
tion about a specified voice profile. If a voice profile is not specified by name,
information about all voice profiles is displayed.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 560 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Introduction
Chapter 27
Configuring DS0 Cross Connect
0
Introduction
This chapter describes how to configure data, voice and clear channel DS0 cross
connect on the BLC 6640-01. Please refer to Chapter 26, Configuring Cross-Connect
Modes on the BLC 6150-01 and the BLC 6246 on page 543 for information about
configuring cross- connect modes on the BLC 6150-01. The BLC 6440-01 do not
support DS0 Cross-Connect functionality.
DS0 cross connect enables DS0s on a T1 to be transported across IP. From an MGCP
perspective, the BLC 6640-01 treat DS0 cross connect endpoints as if they are
additional endpoints. For example, “phone/25@BLC 6640” can be mapped to any
interface group and channel.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 561 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Introduction
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 562 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a T1 Interface for Cross Connect
Note: The serial interface configuration on the system must match the serial
interface configuration on the application it is connected to. Both configurations
must have matching parameters (i.e., framing, facility data link (fdl) standards, line
coding).
1 Enter Global Configuration mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
3 If you are configuring Data or Voice Cross Connect modes, enable channelized
mode:
Occam(config-if-serial)# mode channelized
If you are configuring Clear Channel Voice Cross Connect mode, disable
channelized mode:
Occam(config-if-serial)# mode channelized
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 563 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a T1 Interface for Cross Connect
The first word is a key, anything after is the value attached to that key. In the
above example, 'cross-connect-mode' is the key. You can have several info
messages and you can remove any of them by using the command no info
{key}'. There is no limit on the text length, but you cannot use any of the
following characters: TAB, <enter>, '?', '!'.
7 (Optional) Specify “line” (loop-timed) as the clock source for the T1 interface.
This command determines which end of the line will provide the clocking signal.
“Line” is the factory default. Unless the factory default has been changed, this
command is optional:
Occam(config-if-serial)# service-module t1 clock source line
8 Specify Binary 8 Zero Substitution (b8zs) or AMI (ami) as the line code format.
This command is optional if you select b8zs, the factory default:
Occam(config-if-serial)# service-module t1 linecode {b8zs |ami}
11 (Optional) Enable the system to generate and detect remote (yellow) alarms:
Occam(config-if-serial)# service-module t1 remote-alarm-enable
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 564 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring Network Clocking
6 (Optional) Set the NSP application’s DSCP value for packets that it generates.
The parameters are between 0 and 63. This command has no effect on packets
that the NSP application receives from peer applications and takes effect imme-
diately. It is described more fully in Chapter 33, Differentiated Services (Diffserv)
on page 677:
occam(config)# ip diffserv dscp protocol NSP {0-63}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 565 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 566 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 567 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
Codecs: g711ulaw
MGCP Type: OccamCompliant
Modem Codec Bypass: enable
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 568 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
For example, if a DS0 data cross connect profile named ds0_data_new was being
configured the command would be:
Occam(config)# subscriber-profile cross-connect data ds0_data_new
3 Configure the subscriber profile with the commands described in Table 27-1 on
page 570.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 569 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 570 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 571 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 572 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 573 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring a Cross-Connect Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 574 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring an Interface Group
Note: The commands show alarms active and show alarms log display IG alarms.
Please refer to Chapter 36, Alarms and Sensors on page 691 for information about
these commands and the IG alarms that are displayed.
OR
Use the channels command to configure a range of channels. Separate
channel numbers by a space:
Occam(config-interface-group-cross-connect-channel)# channels {1-24}
{1-24}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 575 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring an Interface Group
For example, if you are configuring channels 1 through 5, the command is:
Occam(config-interface-group-cross-connect-channel)# channels 1 5
For example, if you are configuring a single endpoint with the endpoint
named “phone/1@gw.occamnetworks.com”, the command is:
Occam(config-interface-group-cross-connect-channel)# endpoint
phone/1@gw.occamnetworks.com
OR
Use the endpoint-start command to configure a range of endpoints 27-48
(use this command if the channels command was used in step 3 above). The
endpoint-start command specifies the starting endpoint. Each successive
channel gets the same endpoint, but the endpoint number is incriminated
by 1:
Occam(config-interface-group-cross-connect-channel)#
endpoint-start {name/#@host}
For example, if the channels 1 - 5 are configured with the starting endpoint
named “phone/1@gw.occamnetworks.com”, the command is:
Occam(config-interface-group-cross-connect-channel)# endpoint
phone/1@gw.occamnetworks.com
8 Attach a subscriber profile to the channel or channels (the profile was created
earlier in sectionConfiguring a Cross-Connect Subscriber Profile):
Occam(interface-group-channel)# attach-profile subscriber-
profile-name
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 576 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Configuring an Interface Group
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 577 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01
Viewing Your Configuration
show subscriber-profiles: use this command to view the names of the existing
subscriber-profiles.
show shelf: use this command to display the status of the system in shelf
topology.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 578 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Chapter 28
Configuring the BLC 6640-01 for
GR-303 Interoperability in a Shelf
Configuration
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Shelf Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Self Deployment Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Configuring the Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Configuring T1 Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Configuring Network Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
GR-303 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Configuring an IG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Configuring Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Configuring GR-303 Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Initiating a Switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Configuring Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Removing Cards from the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Viewing Your CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
Introduction
The 6640 and 6640-01 blades and BLC 6640 and BLC 6640-01 assemblies provide
GR-303 Class 5 switch interfaces for the BLC 6000 Broadband Loop Carrier system.
All voice traffic in a BLC 6000 system is carried as VoIP with MGCP signaling. The
6640-01 blades and BLC 6640-01 assemblies convert the POTS traffic to T1 circuits
with GR-303 signaling for connection to a Class 5 switch. Each 6640-01 blade and
BLC 6640-01 assembly has eight T1 ports.
Multiple 6640-01 blades or BLC 6640-01 assemblies can operate in a single
Interface Group (IG). A GR-303 IG allows for oversubscription of up to 2048
subscribers using up to 28 T1s. Each IG goes to one Integrated Digital Terminal (IDT),
but different groups can go to different IDTs. All T1s on an BLC that go to the same
IDT must be in the same IG. A BLC may be configured to have multiple IGs.
Caution: If you have a single blade that functions as a standalone GR303 TGW and
! you wish to add one or more blades to it and create a shelf, Occam Networks
strongly recommends that the IG(s) be removed from the standalone blade and re-
built after the shelf has been created. Simply disabling the IG, adding blades, and
reenabling the IG may cause communication with the switch to fail.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 579 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 580 of 880
10/09/08
10/09/08
785553 Rev. 2.0
REMOTE TERMINAL
BLC MGCP AND RTP FOR VOICE
IP FOR DATA
KEY
PSTN = Public Switched Telephone Network
IP
NETWORK Primary SC = Primary Shelf Controller
Proprietary Information - Occam Networks Inc.
1- 48 SUBSCRIBER
LINES PER BLC Secondary SC = Secondary Shelf Controller
REMOTE TERMINAL
BLC
CENTRAL OFFICE
6640
6640
6640
6640
6640
6640
6640
6640
PSTN
CLI Commands
TR-08 OR
Page 581 of 880
GR-303
BLC 6012 (UP TO 4/8 DS1S
PER BLC)
Class 5 Switch
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Optimize redundancy
GR-303 Limitations
There must be a minimum of 2 T1s and a maximum of 28 T1s per interface group.
Occam Networks recommends at least 2 T1s (primary and secondary), with
each T1 on a separate 6640-01 blades. T1 separation allows the interface
group to be redundant, since the primary and secondary interface group
applications are executed on the same blade as the primary and secondary
T1s.
The number of simultaneous calls possible is the same as the number of DS0s
available. This can be calculated as follows:
# Available DS0s = (# T1s)*(24 DS0s/T1) - 4 DS0s for TMC/EOC
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 582 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Note: For shelves with four or more 6640-01 blades the SC function can be
configured on any two 6640-01 blades in the Shelf.
Redundant Configurations
In redundant configurations, the primary and secondary T1s for the interface group
are on separate 6640-01 blades. The blade with the primary T1 runs the primary IG
applications, and the blade with the secondary T1 runs the secondary IG
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 583 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
applications. The IG applications are in a hot standby configuration. This means that
the IG applications are mirroring data between the active and standby applications,
and the standby applications can take over as soon as they detect failure of the
active applications.
Redundant configurations allow voice services to continue even if one of the 6640-
01 blades is down (for maintenance, etc.)
Silo Configurations
A silo configuration concentrates the T1s for a GR-303 interface group on only a
few 6640-01 blades. With a silo configuration if a 6640-01 blade is down (for
maintenance, etc.), the number of IGs impacted is reduced; however, that IG loses
a greater number of T1s.
Striping Configurations
A striping configuration spreads T1s for a GR-303 IG across many 6640-01 blades
If a 6640-01 blades is down, the number of IGs impacted is increased; however,
each IG loses a smaller number of T1s.
Note: Care must be taken when making the physical connections between the
6640 blades and the GR-303 switch. There are no provisions in GR-303 to verify
that the T1s are physically mapped correctly. Debugging of mis-mapped T1s is a
time-consuming process, fraught with intermittent errors.
Endpoint Configurations
The 6640-01 provides the ability to link VoIP endpoints (through MGCP and RTP) to
a TDM switch (through GR-303).
Endpoints (in the VoIP terminology) are mapped to GR-303 channels within an IG.
For example, phone/z@mgw-abc is mapped to IG X, channel Y.
Usually endpoints from the same media gateway are mapped to the same IG.
However this is not a requirement.
For example:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 584 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Shelf Components
Shelf Controllers
Every shelf has two 6640-01 blades that are configured as Shelf Controllers (SC).
These blades manage the shelf and thus carry an additional CPU load.
The recommendation is to first utilize non-SC blades for primary or secondary T1s.
oManagement functions of the Shelf Controllers can affect the performance of IGs
with the primary or secondary T1 on that blade.
Network Configurations
Deployments of Occam equipment typically utilize Ethernet protection switching
(EPS), with one or more EPS rings.
GR-303 shelf deployments lend themselves to ring operations. In general, the GR-
303 shelf chassis is its own EPS ring, with two blades configured as virtual path
terminators (VPTs), and the remaining blades configured as virtual path selectors
(VPSs).
If possible, the recommendation is that the VPT blades not be run on the same
blades that have shelf controller or interface group application functionality.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 585 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
If running video/IGMP on the same EPS ring, do not run the SC function on the
VPT blades.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 586 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Note: The commands show alarms active and show alarms log display shelf and
card alarms. Please refer to Chapter 36, Alarms and Sensors on page 698 for
information about these commands and the shelf card alarms that are displayed.
Note: It is very important to configure the Slot/Shelf ID selector to a unique value for
each BLC in your network. This information is required by management stations to
identify a specific BLC blade in a specific chassis.
Each chassis is a "shelf" since the slots are hardwired as Slot 1 through 12.
Therefore, two BLC 6012 chassis that are set to the same Shelf ID would result in
duplicate Shelf/Slot ID values when the same slot is equipped in each.
If the BLC 6640-01s in a shelf configuration are in the 1RU chassis, all the BLCs
must have the same shelf ID set (using the first three thumb wheels). Each must
then have a unique slot ID (using the last thumb wheel).
The Shelf ID numbering is hexadecimal. Please see Appendix Appendix C, Decimal to
Hexadecimal Conversion Table on page 857 for a table that converts decimal
numbering to hexadecimal numbering.
Please refer to the sections Configuring the Slot/Shelf ID Selector in Chapter 2,
Installing a BLC 6001 Chassis on page 38 and Configuring the Shelf ID Selector in
Chapter 3, Installing a BLC 6012 Chassis on page 74 for more information about how
to configure a shelf ID.
2 Enter Privileged Mode with the enable command and the password (The default
password for Privileged Mode is “razor”):
Occam> enable
Password:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 587 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
7 Create an alias for the IP address. Enter the hostname (the alias of the host) and
the host’s IP address):
Occam(config)# ip host hostname ip-address
Assign a static IP default route to the bridge group to direct all traffic not
destined for your network to a default router:
Occam(config)# ip default-route ip-address
Repeat these steps for each BLC 6640-01that you want to configure as a card in
the shelf.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 588 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Note: You may reverse the primary and standby shelf controllers by entering the
switchover command from Privileged Mode. Please see Shelf Control Switchover on
page 613 information about how to use this command.
1 Connect to the 6640-01 that you want to configure as a primary shelf controller
via an SSH, Telnet or console connection and enter the password to access User
Mode (The default password for User Mode is “occam”)
Password:
Occam>
2 Enter Privileged Mode with the enable command and the password (The default
password for Privileged Mode is “razor”):
Occam> enable
Password:
5 Set the BLC 6640-01 to shelf mode, specifying the cluster IP address or host-
name of the shelf.
Note: SCs utilize a cluster IP address for management functions. Only the
active SC will receive traffic directed to the cluster IP address.
The cluster IP address is a distinct IP address from the IPs on each blade. For
example, if you have a chassis with twelve blades, you will need thirteen IP
addresses from the same subnet (one for each blade, plus a separate cluster IP
address):
Occam(config-shelf)# mode shelf {cluster ip-address or hostname}
6 Add a BLC 6640-01 as a card to this shelf, specifying the IP address or hostname
of the card. Repeat this command for each card you wish to add to the shelf:
Note: Please see section Removing Cards from the Shelf on page 613 for
information about removing cards from a shelf.
Occam(config-shelf)# insert card {ip-address}
For example:
Occam(config-shelf)# insert card 10.0.0.102
Occam(config-shelf)# insert card 10.0.0.103
Occam(config-shelf)# insert card 10.0.0.104
Occam(config-shelf)# insert card 10.0.0.105
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 589 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 590 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
2 Enter Privileged Mode with the enable command and the password (The default
password for Privileged Mode is “razor”):
Occam> enable
Password:
5 Set the 6640-01 to shelf mode, specifying the same cluster IP address or host-
name of the shelf that you used to configure the primary shelf controller:
Occam(config-shelf)# mode shelf {cluster ip-address or hostname}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 591 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Configuring T1 Lines
Caution: Any unused (unconnected) T1 lines should be disabled with the
! shutdown command to prevent cross-talk (cross-talk is unwanted or undesirable
signals caused by the electric or magnetic fields of one signal affecting another
adjacent signal).
Note: The following commands are entered on the 6640-01 acting as the primary
shelf controller.
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
occam(config)#
5 (Optional) Specify “line” (loop-timed) as the clock source for the T1 interface.
This command determines which end of the line will provide the clocking signal.
“Line” is the factory default. Unless the factory default has been changed, this
command is optional:
Occam(config-if-serial)# service-module t1 clock source line
6 (Optional) Enter the framing type, specifying Extended Super Frame (esf), the
factory default. Unless the factory default has been changed, this command is
optional:
Occam(config-if-serial)# service-module t1 framing esf
7 Remove ANSI T1.403, AT&T TR54016 functionality on the facility data link (FDL)
mode:
Occam(config-if-serial)# no service-module t1 fdl
For example:
Occam(config-if-serial)# info mode GR303
The first word is a key, anything after is the value attached to that key. In the
above example, 'mode' is the key. You can have several info messages and you
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 592 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
can remove any of them by using the command no info {key}'. There is no limit
on the text length, but you cannot use any of the following characters: TAB,
<enter>, '?', '!'.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 593 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Note: Use a unique “tx” number for each BLC 6640-01 or 6640-01 blade in the
shelf. For example, only one BLC 6640-01 or 6640-01 blade may be configured
with the command nsp mode tx 1.
6 (Optional) Set the NSP application’s DSCP value for packets that it generates.
The parameters are between 0 and 63. This command has no effect on packets
that the NSP application receives from peer applications and takes effect imme-
diately. It is described more fully in Chapter 33, Differentiated Services (Diffserv)
on page 677:
occam(config)# ip diffserv dscp protocol NSP {0-63}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 594 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 595 of 880
10/09/08
Table 28-1: Default Subscriber Profile Attributes
10/09/08
785553 Rev. 2.0
CLI Commands
GPON Command Reference Guide
Profile Feature Default Value Command
Input Gain Value- 0 dB occam(config-profile)profile-name# input-gain {-12dB..12dB}
Specify the input gain value in decibels.
Output-Gain 0 occam(config-profile)profile-name# output-gain {-12, -11,
Set the output gain, local adjustment in ...11,12}
decibels.
Forward Disconnect 900 occam(config-profile)profile-name# forward-disconnect {msec}
Proprietary Information - Occam Networks Inc.
CLI Commands
Page 597 of 880
10/09/08
785553 Rev. 2.0
CLI Commands
GPON Command Reference Guide
RTP Signaling Type NUERA2833 occam(config-profile)profile-name# rtp-sig-type
Enable the Real-time Transport Protocol (RTP) (nuera2833,cablelabs2833}
Signaling Mode. Choose between:
nuera2833- Utilize Nuera RFC2833 RTP
mode
RTP mode
When you are creating a subscriber profile for
use with the ON2342 you must use the
“cablelabs2833” option.
Echo Cancel Enabled occam(config-profile)profile-name# echo-cancel enable
Enable echo cancellation
EchoTail Length 48 occam(config-profile)profile-name# echo-tail-length {24, 32, 48,
Set the echo tail length in milliseconds milliseconds 64, 80, 96, 112, 128}
CLI Commands
Page 599 of 880
10/09/08
785553 Rev. 2.0
CLI Commands
GPON Command Reference Guide
MGCP Type Occam occam(config-profile)profile-name# mgcp-type
Select the corresponding MGCP type for compliant {occamcompliant|wave7optics|innomedia|telcosystems|genericiad}
remote endpoint.
The options are to utilize:
Occam-compliant MGCP type mode
(default)
Wave7Optics MGCP type mode
Proprietary Information - Occam Networks Inc.
For example, if a subscriber profile with the name “gr303new” is being config-
ured, the command is
Occam(config)# subscriber-profile tdm gr303 gr303new
3 Use the commands listed in Table 28-1 to configure the subscriber profile.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 601 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Configuring an IG
To configure redundant GR-303, the primary and secondary T1s (DS1s) must be on
different blades. If both primary and secondary T1s are on the same blade, then
GR303 redundancy is not possible. In addition, when multiple GR-303 IGs are
configured in the shelf, the pairing of primary and secondary must be matched or
distinct.
Primary T1: The T1 that is designated the first T1 in an IG and carries the primary
Timeslot Management Channel (TMC) and Embedded Operation Channel (EOC)
DS0s.
Secondary T1: the T1 in an IG that is designated to carry the secondary TMC and
EOC DS0s.
Active T1: a T1 that is carrying voice traffic to the endpoints (or subscriber ports)
in an IG, including Primary and Secondary T1s.
The commands show alarms active and show alarms log display IG alarms. Please
refer to Chapter 36, Alarms and Sensors on page 691 for information about these
commands and the IG alarms that are displayed.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 602 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
IG 1 has the primary T1 line on 2/1 and the secondary T1 line on 3/1
IG 2 has the primary T1 line on 4/3 and the secondary T1 line on 5/3.
IG 3 has the primary T1 line on 6/5 and the secondary T1 line on 7/5
IG 4 has the primary T1 line on 8/7 and the secondary T1 line on 9/7
(STANDBY SC)
(PRIMARY SC)
6640
6640
6640
6640
6640
6640
6640
6640
6640
6640
6640
6640
IG 1
A B
IG 2
A B
IG 3
A B
IG 4
A B
1 2 3 4 5 6 7 8 9 10 11 12
KEY
A = Primary T1 for a GR-303 IG
= Interface Group
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 603 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
IG 1 has the primary T1 line on 2/1 and the secondary T1 line on 3/1
IG 2 has the primary T1 line on 4/3 and the secondary T1 line on 12/3.
IG 3 has the primary T1 line on 2/5 and the secondary T1 line on 3/5
IG 4 has the primary T1 line on 4/7 and the secondary T1 line on 12/7
(STANDBY SC)
(PRIMARY SC)
EMPTY
EMPTY
EMTPY
EMTPY
EMPTY
EMTPY
EMPTY
6640
6640
6640
6640
6640
IG 1
A B
IG 2
A B
IG 3
A B
IG 4
A B
1 2 3 4 5 6 7 8 9 10 11 12
KEY
A = Primary T1 for a GR-303 IG
= Interface Group
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 604 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Steps to Configure an IG
Note: The following commands are entered on the shelf controller 6640-01.
1 Enter Global Configuration Mode:
Occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
4 Add a T1 line to the IG. The first T1 line assigned to the IG is the “primary” T1
line. The primary T1 line carries the EOC and TMC. It is required that the first T1
interface be assigned as the primary T1 line.
Specify:
the logical T1 number for the IG {1-28}
the slot for the card with the T1 {1-12}
the serial interface on that card {1-8}
Occam(interface-group-gr303)ig-number# assign serial {1-28}
{1-12} {1-8}
For example:
Occam(interface-group-gr303)ig-1# assign serial 1 1/1
5 Add a secondary T1 line to the IG with the assign serial secondary command.
This optional command may be used when you have more than one T1 trunk
interface assigned to the GR-303 IG. Any of the remaining T1 lines may be
assigned as the secondary T1 line. However the secondary T1 line cannot be on
the same card as the primary T1 line:
Occam(interface-group-gr303)ig-number# assign serial {1-28}
{1-12} {1-8} secondary
For example:
Occam(interface-group-gr303)ig-1# assign serial 2 1/1 secondary
6 Use the command assign serial to add other T1 lines to the IG, incrementing
each number:
Occam(interface-group-gr303)ig-number# assign serial {1-28} {1-8}
For example:
Occam(interface-group-gr303)ig-1# assign serial 3 3/2
Occam(interface-group-gr303)ig-1# assign serial 4 4/2
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 605 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
7 Specify the type of IDT for the GR-303 IG. The different switch types determine
what set of managed objects are created by the EOC Agent. The factory default
is the Nortel DMS switch (dms):
Occam(interface-group-gr303)ig-number# switch-type {dms | dms10 |
5ess | ewsd | gtd5}
8 (Optional) Use the command initiate pps-eoc to trigger a EOC path protection
switch (PPS).
The option “primary-active” will attempt to make the primary-EOC active.
This will be successful after negotiation with the far end {IDT}.
The option “primary-standby” will attempt to make the primary-EOC standby.
(In other words, primary-EOC will be standby and secondary-EOC will be
active.) This will be successful after negotiation with the IDT.
The option “primary-active-forced” will force the primary EOC to become
active. There will be no negotiation with the IDT.
The option “primary-standby-forced” will force the secondary-EOC to
become active. There will be no negotiation with the IDT.
This information will be relayed to the EOC application, and the path protection
switch will be attempted in the background (asynchronously). As a result, the
requested state here may not be the actual state of the link. Use the command
show interface-group [ig-number] to verify the results of this operation.
Note: The command initiate pps-eoc takes effect when the IG is started (with
the command no shutdown):
Occam(interface-group-gr303)ig-number# initiate pps-eoc
{primary-active |primary-standby |primary-active-forced
|primary-standby-forced}
10 Use the command initiate pps-tmc to trigger a TMC path protection switch.
The option “primary-active” will attempt to make the primary-TMC active.
This will be successful after negotiation with the far end {IDT}.
The option “primary-standby” will attempt to make the primary-TMC
standby. (In other words, primary-tmc will be standby and secondary-tmc will
be active.) This will be successful after negotiation with the far end {IDT}.
The option “primary-active-forced” will force the primary-TMC to become
active. There will be no negotiation with the IDT.
The option “primary-standby-forced” will force the secondary-TMC to
become active. There will be no negotiation with the IDT.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 606 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
This information will be relayed to the EOC application, and the path protection
switch will be attempted in the background (asynchronously). As a result, the
requested state here may not be the actual state of the link. You may use the
command show interface-group [ig-number] to verify the results of this
operation
Note: The command initiate pps-tmc takes effect when the IG is started (with
the command no shutdown):
Occam(interface-group-gr303)ig-number# initiate pps-tmc
{primary-active |primary-standby |primary-active-forced
|primary-standby-forced}
Note: The command no inhibit pps-tmc will disable this feature and allow the
PPS to occur normally.
13 (Optional) Raise and clear memory corrupted alarms to the LDS with the
initiate-memory-corrupted-alarm command. This feature can be used to
inform the LDS that the BLC’s memory has been corrupted to force the LDS to
reprovision the RDT:
Occam(interface-group-gr303)ig-number# initiate memory-
corrupted-alarm
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 607 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Occam(interface-group-gr303)ig-number# no shutdown
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 608 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Configuring Channels
Note: The following commands are entered on the shelf controller.
Note: New GR-303 channels with no endpoint configuration are not saved. In
other words, channels in a GR-303 Interface Group with all default parameters will
not be saved. When channels are configured in a GR-303 Interface Group for future
use, assign a non-default profile, e.g. future channels, or an end point name that
identifies that these are reserved or for future use.
1 Enter Global Configuration Mode:
Occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
OR
Use the channels command to configure a range of channels. Separate
channel numbers by a space:
Occam(interface-group-gr303)ig-number# channels {1-2048}
{1-2048}
For example, if you are configuring five channels, starting with channel 1,
the command is:
Occam(interface-group-gr303)ig-number# channels 1 5
5 Configure MGCP endpoint mapping for the channel or range of channels and
specify a MGCP endpoint name (for example,
“phone/1@gw.occamnetworks.com”):
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 609 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Use the endpoint command to configure a endpoint (use this command if the
channel command was used in step 3 above):
Occam(interface-group-gr303-channels)ig-1/ch-number# endpoint
{name/#@host}
For example, if you are configuring a single endpoint with the endpoint
named “phone/1@gw.occamnetworks.com”, the command is:
Occam(interface-group-gr303-channels)ig-1/ch-1# endpoint
phone/1@gw.occamnetworks.com
OR
Use the endpoint-start command to configure a range of endpoints (use this
command if the channels command was used in step 3 above). The
endpoint-start command specifies the starting endpoint. Each successive
channel gets the same endpoint, but the endpoint number is incriminated
by 1:
Occam(interface-group-gr303-channels)ig-1/chs-number-number#
endpoint-start {name/#@host}
For example, if the channels 1 - 5 are configured with the starting endpoint
named “phone/1@gw.occamnetworks.com”, the command is:
Occam(interface-group-gr303-channels)ig-1/chs-1-5# endpoint-
start phone/1@gw.occamnetworks.com
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 610 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 611 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Note: Timing commands are optional, as the factory defaults work well for most
environments.
1 Set the maximum number of retransmissions for a frame at Layer 2 (LAPD). The
default value is 3:
Occam(interface-group)# timer n200 {1-10}
2 Set the maximum length of time in milliseconds that LAPD will wait for ACK of
a transmitted frame. The default value is 150 milliseconds:
Occam(interface-group)# timer t200 {100 | 150 | 200 | 250 | 300 |
350}
3 Set the maximum time in milliseconds a data link is allowed to remain idle
before verifying the path between the RDT and IDT. The default is 30
milliseconds:
Occam(interface-group)# timer t203 {100 | 150 | 200 | 250 | 300 |
350}
4 Set the value of the TMC timer and define the maximum length of time in milli-
seconds the RDT will wait for a reply to a SETUP message. The default value is
700 ms. [R12-449]:
Occam(interface-group)# timer t303 {700 | 1200 | 1700 | 2200 |
2700 | 3200 | 3700 | 4200 | 4700}
5 Set the maximum length in seconds that the RDT will wait for a rely to a
RELEASE message. The default is 4 seconds. [R12-453]:
Occam(interface-group)# timer t308 {2-5}
6 Set the maximum length in time the RDT will wait for a reply to a SETUP
message following the initial expiration of timer T303. The parameters are
between 700 and 14700, and the default is 14700 ms (14.7 seconds). [R12-460]:
Occam(interface-group)# timer t396 {700 | 1700 | 2700 | 3700 |
4700 | 5700 | 6700 | 7700 | 8700 | 9700 | 10700 | 11700 | 12700 |
13700 | 14700}
7 Set the maximum length in time the RDT will wait for the IDT to ACK an INFOR-
MATION message that indicated that a customer who had been generating a
permanent signal has turned to on-hook. The default is 120s. [R12-455]:
Occam(interface-group)# timer t397 {60 | 120 | 180}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 612 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
Initiating a Switchover
The shelf controller and IG may be “switched over” for maintenance operations.
IG Switchover
IGs may be switched from the active mode to standby mode by entering the initiate
application-switchover command from GR-303 Interface Group Mode on the BLC
that is the active shelf controller:
Occam(interface-group-gr303)ig-number# initiate application-
switchover {primary-active| primary-standby}
The option “primary-active” will attempt to make the primary IG active. This will
be successful after negotiation with the far end {IDT}.
Note: Do not use this command if you have already configured the shelf. This
command will disable the shelf.
3 Set system to shelf mode, specifying the cluster IP address or hostname of the
shelf:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 613 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
4 Remove a card from the shelf, specifying the IP address or slot number of the
card. Repeat this command for each card you wish to remove from the shelf:
Occam(config-shelf)# remove card {ip-address}
For example, to remove the card in slot 3 of the shelf, enter the command:
Occam(config-shelf)# remove card 3
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 614 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
show subscriber-profiles: use this command to view the names of the existing
subscriber-profiles
show shelf: use this command to display the status of the system in shelf
topology
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 615 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf
Configuration
To exit this display hold down the CTRL and letter C keys at the same time.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 616 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Introduction
Chapter 29
0 Automated Shelf Upgrader
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Shelf Status Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Shelf Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Introduction
This chapter describes the Automated Shelf Upgrader (ASU) feature.
The ASU performs the following steps:
Checks the status of the shelf to confirm that the current shelf configuration
can support the ASU.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 617 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Status Check
All blades in the shelf are configured with the same OS release.
All the above conditions must be met before you can upgrade a shelf with the ASU
feature.
The reload shelf check command can be executed independently of the actual
upgrade procedure allowing you to analyze the shelf during normal business hours
and actually upgrade the self at a later time. In addition, when you enter the reload
shelf command the shelf status will automatically be checked again immediately
prior to proceeding and the shelf reload will be dependent on its successful
completion.
You may be prompted to enter the copy running-config startup-config command
to save your current configuration before upgrading your shelf, as shown below:
IG status:
IG Apps Redundant Link Redundant
1 yes(secondary) yes
Shelf software:
Slot 8 Version 5.3 1174298401 Prompt to enter command
Slot 12 Version 5.3 1174298401 copy running-config startup-config.
Slot 1 Version 5.3 1174298401
Slot 2 Version 5.3 1174298401
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 618 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Status Check
IG status:
IG Apps Redundant Link Redundant
1 yes(secondary) yes
Shelf software:
Slot 8 Version 5.3 1174298401
Slot 12 Version 5.3 1174298401
Slot 1 Version 5.3 1174298401
Slot 2 Version 5.3 1174298401
Auto upgrade can commence, since the auto
upgrade pre-check state shows no problems and
Auto upgrade pre-check state: there are no IG's with links non-redundant links.
IG's with links not redundant :
Occam1#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 619 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Software Upgrade
Software Upgrade
Upgrading the Blades
Enter the following command from the active SC to start an upgrade of all the
blades in the shelf:
Occam# upgrade shelf all {ftp-url}
The ftp URL must be in the following format:
ftp://[username[:password]@]hostaddr[/[/]directory]/filename
ftp://occamnetworks:shady1@192.148.11.1//usr/blc_software/5.5/R2
Note: Occam Networks recommends that you only use the upgrade shelf software
command under the guidance of customer support. This command upgrades the
software but not the firmware.
Occam# upgrade shelf software {ftp-url}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 620 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Software Upgrade
Firmware installed
Upgrade complete: Use the 'reload shelf' command to have upgrade take effect
and to reboot cards in an orderly manner.
Occam1#
You may monitor the status of the upgrade by repeatedly entering the
show shelf upgrade command.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 621 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Reload
Shelf Reload
Using the reload shelf Command
Next, enter the reload shelf command. As with the upgrade shelf all command,
this must be entered on the active SC, which will also get reloaded as part of this
operation. During the reload process the standby SC becomes the active SC and
runs this process to completion. This reload process is described in more detail
Chapter 37, Upgrading Shelf Software to Release 5.3R2 in the BLC 6000 System
Installation and Configuration Guide, Release 5.4R4 (PN 785535).
The reload process will not commence if:
The standby SC does not support this reload feature (this blade has not yet been
upgraded to 5.3R2)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 622 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Reload
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 623 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Reload
IG status:
IG Apps Redundant Link Redundant
1 yes(secondary) yes
Shelf software:
Slot 8 Version 5.3 1174298401
Slot 12 Version 5.3 1174298401
Slot 1 Version 5.3 1174298401
Slot 2 Version 5.3 1174298401
Occam#show shelf
System (shelf 0, slot 8, ip 192.168.25.128) - mode is Shelf [Active]
Cluster IP: 192.168.25.132
Peer Controller: 192.168.25.131
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 624 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Reload
The following examples show how you can use the show shelf reload and
show shelf commands to monitor the steps that have been taken so far in the
reload process and what steps are currently being taken:
IG status:
IG Apps Redundant Link Redundant
1 yes(secondary) yes
Before any BLCs are
Shelf software: reloaded, the status of
Slot 8 Version 5.3 1174298401 shelf is checked. This is
Slot 12 Version 5.3 1174298401
Slot 1 Version 5.3 1174298401
reported by "Occam1", the
Slot 2 Version 5.3 1174298401 previously active BLC.
IG status:
The status of shelf
IG Apps Redundant Link Redundant is reported by
1 yes(secondary) yes "Occam2", the
newly active BLC.
Shelf software:
Slot 8 Version V5.3R2
Slot 12 Version V5.3R2
Slot 1 Version V5.3R2
Slot 2 Version V5.3R2
This is a normal
Auto upgrade pre-check state: message because
IG's with links not redundant : once the blades
All blades in the shelf do not have same software version begin the upgrade
they do not all
have the same
Rebooted slot 8 software version.
Slot 8 has been rebooted
Slot 8 back up. and is back up.
To upgrade slot 1 IG's: 1
Rebooted slot 1
Slot 1 has been
rebooted but is not
back up yet.
Occam2#show shelf
System (shelf 0, slot 2, ip 192.168.25.131) - mode is Shelf [Active]
Cluster IP: 192.168.25.132
Peer Controller: 192.168.25.128
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 625 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Reload
The following examples show how the show shelf reload and show shelf command
outputs look when the reload process has completed:
IG status:
IG Apps Redundant Link Redundant
1 yes(secondary) yes
Shelf software:
Slot 12 Version 5.3 1174298401
Slot 14 Version 5.3 1174298401
Slot 1 Version 5.3 1174298401
Slot 2 Version 5.3 1174298401
Rebooted slot 2
Slot 2 back up.
IG status:
IG Apps Redundant Link Redundant
1 yes(secondary) yes
Shelf software:
Slot 8 Version 5.3 V5_3T8
Slot 12 Version 5.3 V5_3T8
Slot 1 Version 5.3 V5_3T8
Slot 2 Version V5.3T8
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 626 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Reload
Occam2#show shelf
System (shelf 0, slot 2, ip 192.168.25.131) - mode is Shelf [Active]
Cluster IP: 192.168.25.132
Peer Controller: 192.168.25.128
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 627 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 29: Automated Shelf Upgrader
Shelf Reload
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 628 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Introduction
Chapter 30
Configuring the BLC 6640-01 for
TR-08 Mode 1 Interpretability
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Configuring Network Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
Configuring T1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
TR-08 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Configuring an Interface Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Viewing Your CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Introduction
The BLC 6640-01 provides a cost effective Central Office Terminal (COT), translating
between MGCP-signalled VOIP and TR-08 signalled Time division Multiplexing
(TDM) voice. This function is not supported on the BLC 6440-01.
CENTRAL
ADSL/POTS POTS OFFICE NEXT GEN
AND 2ND TERMINAL SWITCH
POTS LINE
ADSL/POTS
TR-08 Mode 1
The BLC 6640-01 supports one TR-08 interface group consisting of one to four T1
lines. Only TR-08 Mode I is supported. This mode is used in unconcentrated
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 629 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Configuring Network Clocking
situations where each MGCP endpoint has a dedicated DS0. A MGCP endpoint can
be mapped to any DS0.
Port Mapping
The T1s of the four TR-08 spans are designated A, B, C, D as follows:
T1 port 2 = B link
T1 port 3 = C link
T1 port 4 = D link
The A-link must be the first T1 assigned to a TR-08 interface-group.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 630 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Configuring Network Clocking
Note: Use a unique “tx” number for each BLC 6640-01 or 6640-01 blade in the
shelf. For example, only one BLC 6640-01 or 6640-01 blade may be configured
with the command nsp mode tx 1.
6 (Optional) Set the NSP application’s DSCP value for packets that it generates.
The parameters are between 0 and 63. This command has no effect on packets
that the NSP application receives from peer applications and takes effect imme-
diately. It is described more fully in Chapter 33, Differentiated Services (Diffserv)
on page 677:
occam(config)# ip diffserv dscp protocol NSP {0-63}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 631 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Configuring T1 Interfaces
Configuring T1 Interfaces
Caution: Any unused (unconnected) T1 lines should be disabled with the
! shutdown command to prevent cross-talk (cross-talk is unwanted or undesirable
signals caused by the electric or magnetic fields of one signal affecting another
adjacent signal).
Note: A primary T1 line (TR-08 A-link) must be configured for every IG that has
been enabled.
Note: When using the BLC 6640-01 as a Trunking Gateway only one IG can be
configured. Serial interface 1 must be provisioned as the A-link.
5 Specify SLC96 Remote Terminal (slc96) as the facility data link (fdl) standard for
a T1 data link:
Occam(config-if-serial)# service-module t1 fdl slc96rt
6 (Optional) Specify “line” (loop-timed) as the clock source for the T1 interface.
This command determines which end of the line will provide the clocking signal.
“Line” is the factory default. Unless the factory default has been changed, this
command is optional:
Occam(config-if-serial)# service-module t1 clock source line
7 Specify the alarm mode for interpreting FDL alarms on the T1 line.
The option {note} specifies Network Office Terminating Equipment (NOTE)
alarm mode
The option {wp1} specifies Office Repeater Bay (ORB) WP1 alarm mode
The option {wp1b} specifies Office Repeater Bay (ORB) WP1B alarm mode
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 632 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Configuring T1 Interfaces
8 Specify Binary 8 Zero Substitution (b8zs) or AMI (ami) as the line code format.
This command is optional if you select b8zs, the factory default:
Occam(config-if-serial)# service-module t1 linecode {b8zs |ami}
11 (Optional) Enable the BLC 6640-01 to generate and detect remote (yellow)
alarms:
Occam(config-if-serial)# service-module t1 remote-alarm-enable
For example:
Occam(config-if-serial)# info mode TR08
The first word is a key, anything after is the value attached to that key. In the
above example, 'mode' is the key. You can have several info messages and you
can remove any of them by using the command no info {key}. There is no limit
on the text length, but you cannot use any of the following characters: TAB,
<enter>, '?', '!'.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 633 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Configuring T1 Interfaces
7 Enter any of the commands detailed in steps 6 through 16 from the previous
section (Configuring the Primary (A) T1 Interface on page 632) that apply to your
configuration.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 634 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
TR-08 Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 635 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
TR-08 Subscriber Profile
Note: Occa
m Networks recommends
that the packetization
period only be set to 5 ms.
on ports that are used for
modem/fax support:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 636 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
TR-08 Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 637 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
TR-08 Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 638 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
TR-08 Subscriber Profile
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 639 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
TR-08 Subscriber Profile
enable-Codec bypass
follows echo tone
disabler
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 640 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
TR-08 Subscriber Profile
For example, if a TR-08 Subscriber Profile named TR08-new was being config-
ured the command would be:
Occam(config)# subscriber-profile tdm tr08 tr08-new
3 Configure the TR-08 profile using the commands detailed in Table 30-1.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 641 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Configuring an Interface Group
2 Enter Interface Group Configuration Mode and select a TR-08 Interface Group
number between one to ten to configure:
Occam(config)# interface-group {1-10}
For example, if T1 line 1 is added to the interface group the command is:
Occam(interface-group-tr08)ig-number# assign serial 1 1
5 Repeat step 3 for each T1 you wish to add to the interface group:
OR
Use the channels command to configure a range of channels. Separate
channel numbers by a space:
Occam(interface-group-tr08)ig-number# channels {1-96} {1-96}
For example, if you are configuring channels 1 through 5, the command is:
Occam(interface-group-tr08)ig-number# channels 1 5
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 642 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Configuring an Interface Group
7 Configure MGCP endpoint mapping for the channel or range of channels and
specify a MGCP endpoint name:
Use the endpoint command to configure a endpoint (use this command if the
channel command was used in step 3 above):
Occam(config-interface-group-channel)/ch-number# endpoint
{name/#@host}
For example, if you are configuring a single endpoint with the endpoint
named “phone/1@gw.occamnetworks.com”, the command is:
Occam(config-interface-group-channel)/ch-1# endpoint
phone/1@gw.occamnetworks.com
OR
Use the endpoint-start command to configure a range of endpoints (use this
command if the channels command was used in step 3 above). The
endpoint-start command specifies the starting endpoint. Each successive
channel gets the same endpoint, but the endpoint number is incriminated by
1:
Occam(config-interface-group-channel)/chs-number-number#
endpoint-start {name/#@host}
For example, if the channels 1 - 5 are configured with the starting endpoint
named “phone/1@gw.occamnetworks.com”, the command is:
Occam(config-interface-group-channel)/chs-1-5# endpoint-start
phone/1@gw.occamnetworks.com
8 Attach a subscriber profile to the channel (the profile was created earlier in
sectionTR-08 Subscriber Profile):
Occam(interface-group-channel)# attach-profile subscriber-
profile-name
(For example, if you had created a subscriber profile called “tr08-new” earlier,
the command would be:
Occam(config-interface-group-channel)/chs-number-number# attach-
profile tr08-new
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 643 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Configuring an Interface Group
11 Repeat steps 5 through 9 for each channel you wish to configure, up to 96 chan-
nels, with each channel assigned to a unique endpoint.
13 (Optional) Enable alarm spoofing if you do not wish FDL alarms be generated to
the switch:
Occam(interface-group-tr08)ig-number## alarm-spoof
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 644 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Viewing Your Configuration
show subscriber-profiles: use this command to view the names of the existing
subscriber-profiles.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 645 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability
Viewing Your CPU Usage
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 646 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Introduction
Chapter 31
Configuring TR-08 for TDM Voice on
the BLC 6246 and BLC 6150-01
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Configuring a T1 Interface for TR-08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Configuring POTS Channel Bank Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Configuring a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Displaying Voice Port and Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Introduction
The BLC 6246 and BLC 6150-01 support POTS voice functionality. The voice can be
delivered to the central office using either TDM or packet voice technology. When
the BLC is configured to use TDM one of its T1 interfaces is used as a TR-08
interface, connected to a local DLC, or connected to TR-08 ports on the Class 5
switch in the Central Office.
Port Numbering
BLC 6246
Endpoints 1 - 24 may be configured as POTS voice ports or as DS0 cross connect
ports.
BLC 6250-01
Endpoints 1 - 48 may be configured as POTS voice ports or as DS0 cross connect
ports. Endpoints 49 - 144 may only used as DS0 cross connect endpoints (on the
BLC 6150-01).
If any one of the ports in the lower 1 - 48 range are configured for DS0 cross
connect, all other ports in that range must also be configured for DS0 cross
connect.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 647 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Introduction
How to enable a voice port and attach a profile to the port (page 662).
This section also describes how to configure unbalanced ringing on the voice
port. (page 663).
How to display information about voice ports and profiles (page 665)
POTS Features
The following POTS features are supported when the BLC 6246 and BLC 6150-01
are configured to use TDM:
Caller ID: No user interface is needed for Caller ID. Only the FSK transmission
standard specified by [GR-303] is supported.
Call Waiting: No user interface is needed for call waiting on the BLC 6246 and
BLC 6150-01. This feature is enabled/disabled at the call agent.
Call Waiting Caller Identity Delivery: No user interface is needed for call waiting
calling identity delivery on the BLC.The end user interface for this function is the
display on the customer premises. Phone customers need to subscribe the caller
ID and call waiting caller ID services from their telephone service provider to
receive caller information.
Visual Message Waiting Indicator: No user interface is needed for visual message
waiting indicator on the BLC. The end user interface for this function is the
visual indicator on the CPE. Phone customers need to subscribe to voice
mail/message service from their ISP to activate this feature.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 648 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Introduction
Call Control Signaling: Offhook, onhook, etc. for each POTS line.
Management/Alarm Signaling: Configuration and alarms for the LDS and DLC.
TR-08 features include SLC96 framing, Facility Data Link (FDL) and Forward
Disconnect support.
Foreign Exchange Station (FXS), for foreign exchange office channel bank
emulation
SLC 96-remote terminal-single party (slc96rt-sp), for TR-08 single party channel
bank emulation. SLC96 is a digital loop carrier system manufactured by AT&T
that interfaces with a Local Digital Switch using the TR-08 protocol.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 649 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Introduction
Table 31-1: RT Channel Number to Timeslot Mapping for D1D and D4 Modes
RT Timeslot Number
Channel
Number
D1D D4
0 0 0
1 2 1
2 4 2
3 6 3
4 8 4
5 10 5
6 12 6
7 14 7
8 16 8
9 18 9
10 20 10
11 22 11
12 1 12
13 3 13
14 5 14
15 7 15
16 9 16
17 11 17
18 13 18
19 15 19
20 17 20
21 19 21
22 21 22
23 23 23
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 650 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Introduction
Port Mapping
The T1s of the four TR-08 spans are designated A, B, C, D as follows:
T1 port 2 = B link
T1 port 3 = C link
T1 port 4 = D link
The A-link must be the first T1 assigned to a TR-08 interface-group. Up to two A-
links may be assigned (one to each interface-group).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 651 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring a T1 Interface for TR-08
4 Specify the alarm mode for interpreting FDL alarms on the T1 line to WP1B:
Occam(config-if-serial)# service-module t1 alarm-mode wp1b
5 (Optional) Enter the line code format, specifying Alternate Mark Inversion (AMI)
as the line code:
Occam(config-if-serial)# service-module t1 linecode ami
6 Specify the facility data link (fdl) mode for a SLC96 Remote Terminal (slc96rt):
Occam(config-if-serial)# service-module t1 fdl slc96rt
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 652 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring a T1 Interface for TR-08
8 Set the channel mapping mode, specifying D1D or D4. The default channel
mapping mode is D1D. The BLC will use the channel mapping mode and the
desired RT channel number to calculate the appropriate timeslot:
Occam(config-if-serial)# service-module t1 channel-mapping {d1d
|d4}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 653 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring POTS Channel Bank Profiles
Default Voice Port Profile on the BLC 6246 and BLC 6150-01
All ports have attached profiles. If you do not assign a profile to a port, the system,
by default, assigns the profile named "default" to that port. This profile can be
changed but not deleted.
A profile named “default” is on the BLC 6246 for ports 1-24 and on the
BLC 6150-01 for ports 1-48. This profile is for POTS-VoIP, a voice profile that
delivers POTS over VoIP. Once you enter POTS Channel Bank Profile Configuration
Mode, a POTS Channel Bank default profile is attached to
ports 1-48.
The POTS Channel Bank default profile can be changed but cannot be deleted from
the BLC. The profile must be attached to a voice port for the change to take effect.
The POTS Channel Bank default profile is shown below.
Profile type: pots-tr08
Input Gain: 0 dB
Output Gain: 0 dB
Forward Disconnect: 900 milliseconds
Fax Delay: 0 milliseconds
Fax CNG Detect: disable
Fax CNG Timer: 0 seconds
Signaling Type: slc96rt-sp
Rtp Signaling Type: none
Echo cancel: enable
Echo tail length: 32 milliseconds
Echo Tone Disabler: G.165
Connection mode: pots-t1:1/1
Idle Channel Suppression: enable
Receive Level: -3.0 dB
Transmit Level: -3.0 dB
Codecs:
g711ulaw
Codec Options:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 654 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring POTS Channel Bank Profiles
g711ulaw:
Jitter Delay: 20ms
Packetization: 10ms
g726-32k-pt2:
Jitter Delay: 40ms
Packetization: 20ms
g726-32k:
Jitter Delay: 40ms
Packetization: 20ms
Modem Codec Bypass: enable
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 655 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring POTS Channel Bank Profiles
2 Enter POTS Channel Bank Profile Configuration Mode with the voice-profile
pots channel-bank command. Create a profile by using the name of a profile
you wish to create or an existing profile you wish to modify. Each voice port
profile must have a unique name:
occam(config)# voice-profile pots channel-bank {profileName}
For example, if a POTS Channel Bank Profile named “tr08_new” was being
configured the command would be:
Occam(config)# voice-profile pots channel-bank tr08_new
Note: At this point in your configuration (after steps 1 and 2), the profile you
have created has the default POTS Channel Bank default profile attributes that
were described on page 654. If you wish to attach this profile to voice ports
without making any changes to it, please turn to step 11 to complete your
profile configuration. If you wish to make changes to the POTS Channel Bank
default profile, please continue on to step 3 in this section.
Note: Use the command no voice-profile pots channel-bank to delete a
profile by name.
3 Set the POTS port to T1 control. The T1 interface must be the same one that was
configured earlier in the sectionConfiguring a T1 Interface for TR-08:
Occam(config-profile)<profileName># connect pots-t1 {1-4}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 656 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring POTS Channel Bank Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 657 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring POTS Channel Bank Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 658 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring POTS Channel Bank Profiles
Codec-list: occam(config-profile)profile-name#
codec-list (g711ulaw, g726-32K-pt2,
Preferred coder-decoders (codecs) used g726-32k}
during call compression. The order
entered determines the priority order of
the codecs.
Codec-Options: occam(config-profile)profile-name#
codec-options {g711ulaw, g726-32K-pt2,
Configures the jitter delay and packetiza- g726-32k}
tion options for codecs.
Jitter Delay: occam(config-voice-codec)#
jitter-delay {10,..110}
Specifies jitter buffer delay in 5 msec
increments.
First use the “codec-options” command to
enter Voice Profile Codec configuration
mode. From this configuration mode you
may enter the “jitter-delay” command.
Packetization: occam(config-voice-codec)#
packetization {15 | 10 | 20 |40}
Selects the packetization period value in
milli-seconds.
First use the “codec-options” command to
enter Voice Profile Codec configuration
mode. From this configuration mode you
may enter the “packetization” command.
Modem Codec Bypass: occam(config-profile)profile-name#
modem-codec-bypass {enabled, disabled}
Configures the modem-codec-bypass as:
disabled - No codec bypass
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 660 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring POTS Channel Bank Profiles
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 661 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring a Voice Port
2 Enter Voice Configuration Mode and specify the voice port number you want to
configure:
Occam(config)# voice-port voice-port-number
For example, if you are attaching a profile named tr08_new to the voice port,
the command would be:
Occam(config-voice)# attach profile tr08_new
4 The port is shutdown by default. To enable the port enter the no shutdown
command:
Occam(config-voice)# no shutdown
5 (Optional) Attach descriptive text to the voice port profile (for example “Asso-
ciated with 123 Main Street”):
Occam(config-voice)# description description-text
For example:
Occam(config-voice)# info attached-profile bronze
The first word is a key, anything after is the value attached to that key. In the
above example, 'attached-profile' is the key. You can have several info messages
and you can remove any of them by using the command no info {key}. There is
no limit on the text length, but you cannot use any of the following characters:
TAB, <enter>, '?', '!'.
8 Repeat steps 2 through 6 for each port to which you wish to attach a profile.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 662 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring a Voice Port
2 Enter Voice Configuration Mode and specify the voice interface number
(between 1 and 48) on which you want to configure unbalanced ringing:
Occam(config)# voice-port {1-48}
2 Enter Voice Configuration Mode and specify the voice interface number
(between 1 and 48) on which you want to configure unbalanced ringing:
Occam(config)# voice-port {1-48}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 663 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Configuring a Voice Port
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 664 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Displaying Voice Port and Profile Information
show voice dsp: displays the current status of all digital signal processor (DSP)
voice channels.
show voice power {port-number}: use this command to measure in real time
the transmit and receive signal power on one or all voice ports. If an interface
number is not specified, the power of all interfaces are displayed. Power
measurement is displayed in dBm0 (equal to a digital milliwat) and is taken after
adjustment by output-gain and input-gain parameters.
Transmit power (TX) is defined as power going into the network. The transmit
power meter continues to measure even when the port is onhook.
show voice list-of-profiles: use this command to display the names of existing
voice profiles.
show voice profile [voice profile-name]: use this command to display informa-
tion about a specified voice profile. If a voice profile is not specified by name,
information about all voice profiles is displayed.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 665 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01
Displaying Voice Port and Profile Information
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 666 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
Chapter 32
Configuring Foreign Exchange
Station (FXS)/ Channel Associated
Signaling (CAS) Mode on the
BLC 6640-01
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
Configuring T1 Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
Configuring Network Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Subscriber Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Configuring an Interface Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Introduction
The BLC 6640-01 support Foreign Exchange System / Channel Associated Signaling
FXS/CAS signaling. This enables the BLC 6640-01 to connect to a switch which is
using FXS/CAS signing with either D4 Super Frame (SF) or Extended Super Frame
(ESF) framing. This function is not supported on the BLC 6440-01.
An FXS interface is a piece of transmission equipment that emulates the line side
interface of a switching system and can be directly connected to a standard
telephone. It supplies ring, supervisory voltage, and dial tone.
Configuring T1 Lines
Caution: Any unused (unconnected) T1 lines should be disabled with the
! shutdown command to prevent cross-talk (cross-talk is unwanted or undesirable
signals caused by the electric or magnetic fields of one signal affecting another
adjacent signal).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 667 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
4 Specify “line” (loop-timed) as the clock source for the T1 interface. This
command determines which end of the line will provide the clocking signal. This
command is optional if you select “line”, the factory default:
Occam(config-if-serial)# service-module t1 clock source line
5 Specify Extended Super Frame (ESF) as the framing type (factory default):
Occam(config-if-serial)# service-module t1 framing esf
6 Enter the linecode type, specifying alternate mark inversion (AMI) or binary 8
zero substitution (B8ZS). This command is optional if you select “b8zs”, the
factory default:
Occam(config-if-serial)# service-module t1 linecode {ami | b8zs}
For example:
Occam(config-if-serial)# info mode FXS-CAS
The first word is a key, anything after is the value attached to that key. In the
above example, 'mode' is the key. You can have several info messages and you
can remove any of them by using the command no info {key}. There is no limit
on the text length, but you cannot use any of the following characters: TAB,
<enter>, '?', '!'.
11 Repeat steps 2 through 10 for each T1 interface you wish to configure on the
BLC 6640-01.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 668 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
6 (Optional) Set the NSP application’s DSCP value for packets that it generates.
The parameters are between 0 and 63. This command has no effect on packets
that the NSP application receives from peer applications and takes effect imme-
diately. It is described more fully in Chapter 33, Differentiated Services (Diffserv)
on page 677:
occam(config)# ip diffserv dscp protocol NSP {0-63}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 669 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
Subscriber Profiles
To configure a channel in an interface group you must attach a subscriber profile
to it. A profile includes parameters such as the signalling type, and RTP signaling
mode. When a parameter in a profile is changed, the value of that parameter on all
channels attached to that profile is also changed.
If an existing profile is modified, that change takes effect on every channel linked
to that profile. To change a single channel you must copy the profile, change the
desired parameters, and then assign the new profile to the desired channel. There
can be one profile for many channels, but one channel cannot have more than one
profile.
You may create a virtually unlimited number of subscriber profiles. Subscriber
profiles are maintained in memory so that the profiles can be assigned when
needed.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 670 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
For example, if a subscriber profile with the name “fxsnew” is being configured,
the command is:
Occam(config)# subscriber-profile tdm tr08 fxsnew
3 Enable the Nuera RFC2833 Real-time Transport Protocol (RTP) Signaling Mode.
This is the factory default:
Occam(config-profile)<profileName># rtp-sig-type nuera2833
7 (Optional) Set the output gain, local adjustment in decibels. The default is 0:
Occam(config-profile)<profileName># output-gain {-12,
-11,...11,12}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 671 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
9 (Optional) Set the echo tail length in milliseconds. The default is 64 milliseconds:
Occam(config-profile)<profileName># echo-tail-length {24, 32, 48,
64, 80, 96, 112, 128}
10 (Optional) Set the amount of time in milliseconds before there will be an alert
sent out after the removal of the battery signal. The default is 900 milliseconds:
Occam(config-profile)<profileName># forward-disconnect {msec}
11 (Optional) Set the jitter buffer delay length in milliseconds (msec). The default
is 20 msec. The parameters are between 10 and 110 in five msec increments:
Occam(config-profile)<profileName># jitter-delay {msec}
12 (Optional) Set the fax jitter buffer delay length in msec. The default is 0 msec
(disabled). The parameters are between 0 and 210 in five msec increments:
Occam(config-profile)<profileName># fax-delay {msec}
14 (Optional) Select the corresponding MGCP type for remote endpoint. The
options are to utilize:
Occam-compliant MGCP type mode (default)
Wave7Optics MGCP type mode
Innomedia MGCP type mode
Telco Systems MGCP type mode
Generic IAD MGCP type mode
Occam(config-profile)<profileName># mgcp-type
{occamcompliant|wave7optics|innomedia|telcosystems|genericiad}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 672 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
For example, if T1 line 1 is added to the interface group the command is:
Occam(config-interface-group-cross-connect)# assign serial 1 1
Note: You must add T1 interfaces in order (for example T1 2 may not be added
before T1 1).
5 Repeat step 3 for each T1 you wish to add to the interface group:
OR
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 673 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
7 Configure MGCP endpoint mapping for the channel or range of channels and
specify a MGCP endpoint name:
Use the endpoint command to configure a endpoint (use this command if the
channel command was used in step 3 above):
Occam(config-interface-group-cross-connect-channel)# endpoint
{name/#@host}
For example, if you are configuring a single endpoint with the endpoint
named “phone/1@gw.occamnetworks.com”, the command is:
Occam(config-interface-group-cross-connect-channel)# endpoint
phone/1@gw.occamnetworks.com
OR
Use the endpoint-start command to configure a range of endpoints (use this
command if the channels command was used in step 3 above). The
endpoint-start command specifies the starting endpoint. Each successive
channel gets the same endpoint, but the endpoint number is incriminated by
1:
Occam(config-interface-group-cross-connect-channel)#
endpoint-start {name/#@host}
For example, if the channels 1 - 5 are configured with the starting endpoint
named “phone/1@gw.occamnetworks.com”, the command is:
Occam(config-interface-group-cross-connect-channel)# endpoint
phone/1@gw.occamnetworks.com
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 674 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
8 Attach a subscriber profile to the channel or channels (the profile was created
earlier in section Configuring a Subscriber Profileon page 671):
Occam(config-interface-group-cross-connect-channel)# attach-
profile subscriber-profile-name
(For example, if you had created a subscriber profile called “fxsnew” earlier, the
command would be:
Occam(config-interface-group-cross-connect-channel)# attach-
profile fxsnew
11 Repeat steps 5 through 9 for each channel you wish to configure, up to 192
channels, with each channel assigned to a unique endpoint.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 675 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling
(CAS) Mode on the BLC 6640-01
show subscriber-profiles: use this command to view the names of the existing
subscriber-profiles.
show shelf: use this command to display the status of the system in shelf
topology.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 676 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 33: Differentiated Services (Diffserv)
Introduction
Chapter 33
Differentiated Services (Diffserv)
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Flow Classifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Queue/Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Configuring IP Diffserv DSCP Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Configuring IP Diffserv DSCP Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Introduction
The BLC supports the Differentiated Services (Diffserv) model proposed by the
Diffserv Working Group. Under the IETF DiffServ model, traffic is divided into
multiple classes defined by a network identifier, based on the traffic requirements.
The BLC classifies IP packets using IP Differentiated Services Code Points (DSCP).
Within an IP cloud, a Differentiated Services (DS) capable core router forwards and
routes IP packets and will treat an IP packet based on the DS code point and the
management policies at each hop.
Flow Classifications
Untagged Classification
When a BLC receives untagged packets, untagged flow classification is performed
on the DS Field of the IP header. The value of the DSCP of the DS field is mapped
to a priority between 1 and 8 where 1 is the highest priority. There is a default
mapping of DSCP to priority (as shown in the section Displaying the DSCP to Priority
Mapping Table on page 681). The default mapping can be viewed and changed via
CLI commands. Please see sections Configuring IP Diffserv DSCP Mapping on page
681 for information about these commands.
Packets that enter the system that are received untagged are tagged regardless of
whether the packet exits the system 802.1q tagged or untagged. The 802.1p user
priority is derived directly from the DSCP to priority mapping. The 802.1p user
priority is a 3-bit value representing priorities 0-7 where priority 7 is the highest
priority.
Packets that originate within the system are similarly assigned a priority based on
the applications requesting DSCP. If the application does not request a DSCP then
the local IP stack assigns the default value 18 (which represents AF21). The default
is also configurable via the CLI, using the command ip diffserv dscp default.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 677 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 33: Differentiated Services (Diffserv)
Markers
Packets that exit the kernel 802.1q tagged derive the 802.1p user priority from the
DSCP mapped priority.
Markers
Transit traffic is not DSCP remarked as it enters the system on the BLC. The BLC has
applications which request IP to apply a specific DSCP to the DS field to packets
that the application generates. For example, the IGMP, RTP and MGCP applications
on the BLC request IP to mark their packets accordingly. All other locally generated
traffic is default marked by IP (i.e., SNMP, SSH etc.).
Queue/Schedulers
The BLC supports eight packet priorities derived either from the DSCP or the 802.1p
user priority. Each of the eight priorities is mapped to a queue on the egress port.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 678 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 33: Differentiated Services (Diffserv)
Configuring IP Diffserv DSCP Protocol
Command Description
ip diffserv dscp protocol CES {0-63} Sets the CES application’s
DSCP value to a number
between 0 and 63
ip diffserv dscp protocol IGMP {0-63} Sets the IGMP application’s
DSCP value to a number
between 0 and 63
ip diffserv dscp protocol MGCP {0-63} Sets the MGCP application’s
DSCP value to a number
between 0 and 63
ip diffserv dscp protocol NSP {0-63} Sets the NSP application’s
DSCP value to a number
between 0 and 63
ip diffserv dscp protocol RTP {0-63} Sets the RTP application’s
DSCP value to a number
between 0 and 63
ip diffserv dscp protocol SIP {0-63} Sets the SIP application’s
DSCP value to a number
between 0 and 63
ip diffserv dscp protocol defaultS {0-63} Sets the default DSCP value
for all other applications to a
number between 0 and 63
Example
In this example the MGCP protocol application is configured to use the DSCP value
of 32 for packets that it generates:
occam# configure terminal
occam(config)# ip diffserv dscp protocol mgcp 32
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 679 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 33: Differentiated Services (Diffserv)
Configuring IP Diffserv DSCP Protocol
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 680 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 33: Differentiated Services (Diffserv)
Configuring IP Diffserv DSCP Mapping
Parameter Description
dscp value Value from 0 through 63
priority value Priority value between 1 (highest) and 8
Example
In this example the DSCP value "32" is mapped to priority "1" within the system.
This causes packets marked with this DSCP to be queued in the highest priority
queue under congestion conditions. It also causes untagged packets entering the
system to be 802.1p tagged with priority 7 (the highest user priority) if the packet
exists the system 802.1q tagged:
occam# configure terminal
occam(config)# ip diffserv dscp map 32 priority 1
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 681 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 33: Differentiated Services (Diffserv)
Configuring IP Diffserv DSCP Mapping
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 682 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 34: Power Save Mode
Introduction
Chapter 34
Power Save Mode
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Enabling and Disabling Power Save Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Configuring Power Save Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Viewing Power Save Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Introduction
The BLC 6212-02, BLC 6244, BLC 6246, and BLC 6252-03 feature a “power save”
mode. This mode, which is disabled by default, allows a BLC to reduce power
consumption in a Remote Terminal (RT) when an AC power outage is detected.
In a typical Remote Terminal (RT), BLCs are powered by a bank of batteries that is
continuously charged by an AC power supply. In the event of an AC power outage,
the batteries must be able to power the RT for at least eight hours. The “power save”
mode enables the BLC, in combinations with other systems in the RT, to lower its
power consumption in order to support an RT's eight hours uptime requirement.
When the BLC is in power save mode the DSL modems shut down when the input
voltage drops to -46.77V (typical battery powered input voltage).
To disable power save mode use the command no power save from Global
Configuration Mode:
Occam# no power save
.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 683 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 34: Power Save Mode
Configuring Power Save Mode
For example, to activate power save mode when the input power drops below -49
volts, use the command:
Occam(config)# power save ac off threshold -49
The no power save ac off threshold command sets this threshold to -48V, the
default AC Off voltage
Occam(config)# no power save ac off threshold
For example, to configure power save mode to commence five minutes after loss of
AC power, use the command:
Occam(config)# power save ac off timer 5
The no power save ac off ac timer command sets this threshold to the factory
default value of 15 minutes:
Occam(config)# no power save ac off timer
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 684 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 34: Power Save Mode
Configuring Power Save Mode
For example, to activate power save mode when the temperature drops below -50
volts, use the command:
Occam(config)# power save ac on threshold -50
The no power save ac on threshold command sets this threshold to -52V, the
default AC On voltage
Occam(config)# no power save ac on threshold
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 685 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 34: Power Save Mode
Viewing Power Save Settings
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 686 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 35: Blade to Blade Communication (SSH From CLI)
Introduction
Chapter 35
Blade to Blade Communication (SSH
From CLI)
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Configuring Blade to Blade Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Deleting a Specified Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Viewing Public Keys Associated With a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Introduction
The BLC supports the Secure Shell (SSH) from the CLI. This allows ease of
communication between blades. CLI commands may be performed on a remote
blade as easily as the blade to which you are physically attached.
Your computer must run a SSH client to connect to the BLC. Various commercial
and shareware SSH clients are available, such as SecureCRT (available at
http://www.vandyke.com/), puTTY.
Please refer to the section Remote Connection Methods in Chapter 7, Initial
Configuration Steps on page 139 for information about accessing a blade with a
SSH connection.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 687 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 35: Blade to Blade Communication (SSH From CLI)
Configuring Blade to Blade Communication
To connect to a specified host using SSH Version 2, enter the following command
from Privileged Mode:
ssh {host} [username]
For the parameter “host”, put the IP address or hostname of the blade to which
you want to connect.
Examples
1 If you want to connect to a BLC with the IP address 123.456.7.89, with a user-
name “steve”, use the command:
occam# ssh 123.456.7.89 steve
If this is the first time you are connecting to this BLC, you will see the following
output. Type “yes” when prompted to complete the connection:
The authenticity of host '123.456.7.89 (123.456.7.89)' can't be
established.
RSA key fingerprint is
13:11:38:e7:9f:0d:c6:e2:01:71:3c:8f:e4:b9:38:a6.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘123.456.7.89’ (RSA) to the list of
known hosts.
steve@123.456.7.89's password:
2 If you want to connect to a BLC with the IP address 987.654.3.21 and do not
want to specify a username, use the command:
occam# ssh 987.654.3.21
If this is not the first time you are connecting to this BLC, you will see the
following output:
cli@987.654.3.21's password:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 688 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 35: Blade to Blade Communication (SSH From CLI)
Deleting a Specified Host
Example
To delete the IP address 123.456.7.89 from the known hosts file, use the command:
occam# clear ssh host 123.456.7.89
Example
To display the public key associated with hostname “ces6”, use the command:
occam# show ssh key ces6
ces6,192.168.12.46 ssh-dssAAAAB3NzaC1kc3MAAABBAKBIZw9gDayvwNB
fcMS/bRQZQX89wEaczHRU4sm2MI0nuoOYJ17QafKVx/SV+58JBzSDfh8LPa1QRb7uu
LKI5l0AAAAVAI/6MxQBzZ3IA+85YtPp0MJ53VYrAAAAQA2ianasaAVTgyAinLnq8tw
mSD001aMj4a4YLNVj4oxX7mPzEm883qN5XzLm0xudBhQbj1vO0Bf8SnXos9A7fuIAA
ABAczk1badR+N8abitWFmU01leaAtTQJWHSCzgzsjEq1pCyxxCQobEBhxjnBR8NAEy
GfYuNgFPqt2INBcJ7d1p0MA==
ces1#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 689 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 35: Blade to Blade Communication (SSH From CLI)
Viewing Public Keys Associated With a Host
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 690 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Introduction
Chapter 36
Alarms and Sensors
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Environment Alarm In and Out Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Configuring Power Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Displaying Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
Clearing Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Displaying Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Alarms Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Index of Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Introduction
There are various ways to monitor the BLC through the use of alarms and sensors.
Visible and/or audible alarms can be attached to the BLC. The audible/visible
alarm indicator is connected by a cable. The indicator is activated when the
system enters the alarmed state or when a new alarm is raised. It is deactivated
if all pending alarms are cleared. This alarm indicator can be turned off with the
command clear alarm indicator. Please see the section Environment Alarm In and
Out Commands on page 692 for information on this feature.
The A and B power connectors on the BLC chassis may be enabled or disabled.
Please see the section Configuring Power Alarms on page 696 for information on
this feature.
Please see the section Displaying Alarms on page 698 for information about what
alarms are generated on the BLC.
Active alarms can be viewed with CLI commands. An alarm log is kept for inspec-
tion by network management applications. Please see the section Displaying
Alarms on page 698 for information on these features.
System sensors on the BLC can also be viewed with CLI commands. Please see the
section Displaying Sensors on page 700 for information on this feature.
Please see page 703 for a list of alarms, sorted by feature that are supported by the
BLC. Alarms differ, according to BLC model. Please see page 732 for an alphabetical
list of these alarms.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 691 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Environment Alarm In and Out Commands
Alarm In Function
Alarm in allows you to attach an external device to the BLC and trigger an alarm to
the BLC based on a voltage differential. For example, if a BLC is in an RT and you
wants to know if the door to the RT is opened, you can set a trigger on the door to
cause a voltage change when the door is opened. This would cause an alarm in on
the BLC. When the door is shut, the alarm is no longer present.
You can define whether the alarm in is ignored, normal or inverted (default is
ignored) as well as send an SNMP trap with a defined text string.
On the BLC 6000 platform there is one alarm in. When a return for this alarm is
connected a high voltage power circuit is completed. When this return is
interrupted, this circuit is broken. Because of this, the alarm-out will always register
an active alarm state by factory default if the AlarmIn alarm is not attached to an
alarm system.
You can use the environment alarm in command from Global Configuration Mode
to configure the alarm in to:
Ignore alarm in completely (This is the factory default setting, which allows you
to be able to hook up various types of equipment to the alarm in.):
occam(config)# environment alarm in ignore
Be in alarm when there is a voltage potential applied that completes the circuit:
occam(config)# environment alarm in invert
You can also use the environment alarm in description command to write
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 692 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Environment Alarm In and Out Commands
Note: The LED will remain on even after if the alarm is cleared. This must be cleared
manually either by the alarm cutoff switch on the front of the BLC or by the
command clear alarm indicator. Also, if the alarm is still active and either the alarm
cutoff switch is used or the clear alarm indicator command is executed, the relay
will go back to its default state, but the LED will not clear.
Please see the sections describing the front panel in BLC product overview chapters
at the front of the manual for information about the location of the alarm LED and
the alarm cutoff switch.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 693 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Environment Alarm In and Out Commands
The BLC’s alarm condition goes away (for example, if a “link down” occurs, the
“link up” acknowledges it and the indicator returns to normal)
The user can acknowledge the alarm in the alarm window and the indicator
returns to normal.
Note: The Primary and Secondary BLCs must run the same version of code (both
must run 5.5R1 code, for example).
Figure 36-1: EMS Network Configuration with Primary and Secondary BLCs
SECONDARY BLC
EM S
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 694 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Environment Alarm In and Out Commands
All BLCs are configured by default so that all alarms, including those sent by EMS,
will activate the alarm indicator. This default setting may be changed on the
Primary and Secondary BLCs with the environment alarm out mode command.
The command options are:
environment alarm out mode none The alarm indicator is never turned
on
environment alarm out mode local The alarm indicator is only turned
on for locally generated alarms.
environment alarm out mode remote The alarms indicator is turned on
only for alarms generated by the
OccamView network management
system. Local alarms will not acti-
vate the indicator.
environment alarm out mode all All alarms will activate the alarm
indicator (factory default).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 695 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Configuring Power Alarms
The alarm-out may register an active alarm state if only one power source is used.
The command environment alarm voltage input allows this alarm to be disabled
or enabled. By default, both A and B power alarms are enabled.
The command options are:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 696 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Configuring Power Alarms
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 697 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Displaying Alarms
Displaying Alarms
The show alarms active and show alarms log commands in User and Privileged
Modes display the status of alarms. The show alarms summary shows alarms in a
summarized format.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 698 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Clearing Alarms
Clearing Alarms
Clearing the Alarm Indicator
Use the clear alarm indicator command to clear the external alarm indicator:
occam# clear alarm indicator
The commands show alarms active and show alarms log display a unique alarm
index number in the first line of output.
For example:
occam# show alarms active
Index Severity SA Created Description
1 Major - 1970/01/01 12:00:40 AlarmIn: AlarmInOn
Use this alarm index number to select active alarms to clear. If no alarm index
number is selected, all active alarms are cleared.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 699 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Displaying Sensors
Displaying Sensors
The show environment commands in Privileged Mode display the status of the
system sensors.
The show environment all command displays all of the system sensors. The
following example shows sample output from this command:
occam# show environment all
Fans: Fan10 4800 RPM
Fan9 4920 RPM
Fan8 4860 RPM
Fan7 4860 RPM
Fan6 4740 RPM
Fan5 4920 RPM
Fan4 4980 RPM
Fan3 4740 RPM
Fan2 4740 RPM
Fan1 4740 RPM
Voltages: #A Vin -48V -54.84 Volts
#B Vin -48V -2.37 Volts
SSTL2REF +1.25V 1.25 Volts
SSTL2VTT +1.25V 1.25 Volts
FPGA +1.8V 1.80 Volts
DDR SDRAM +2.5V 2.49 Volts
DSP +1.6V 1.59 Volts
440GP +1.8V 1.80 Volts
LM87 +3.3V Mezz1 3.28 Volts
VBAT1 -50V Mezz1 -45.76 Volts
VBAT2 -35V Mezz1 -33.45 Volts
VH +80V Mezz1 77.80 Volts
Temperatures: Internal temperature 27 C
External temperature 22 C
Internal temperature Mezz1 25 C
#1 External temperature Mezz1 46 C
#2 External temperature Mezz1 41 C
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 700 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Displaying Sensors
The show environment fans command displays the system fan sensors. The
following example shows sample output from this command.
Note: This command will only display information if the blade is in the 1 RU
BLC 6001 chassis or in a bookend position (slot 1 or 12) of the 12 RU BLC 6012
chassis:
The show environment alarms command displays the system sensors alarm
state:
occam# show environment alarms
Fans: Fan1 OK
Fan2 OK
Fan3 OK
Fan1 Mezz1 OK
Fan2 Mezz1 OK
Fan3 Mezz1 OK
Voltages: #A Vin -48V OK
#B Vin -48V MAJOR
SSTL2REF +1.25V OK
SSTL2VTT +1.25V OK
FPGA +1.8V OK
DDR SDRAM +2.5V OK
DSP +1.6V OK
440GP +1.8V OK
LM87 +3.3V Mezz1 OK
VBAT1 -50V Mezz1 OK
VBAT2 -35V Mezz1 OK
VH +80V Mezz1 OK
Temperatures: Internal temperature OK
External temperature OK
Internal temperature Mezz1 OK
#1 External temperature Mezz1 OK
#2 External temperature Mezz1 OK
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 701 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Displaying Sensors
The show environment voltages command displays the system voltage sensors.
The following example shows sample output from this command:
occam# show environment voltages
Voltages: +5V 4.84 Volts
LM87 +3.3V 3.31 Volts
440GP +1.8V 1.79 Volts
+1.2V 1.20 Volts
+1.25V 1.24 Volts
+2.5V 2.50 Volts
SSTL2VTT +1.25V 1.24 Volts
SSTL2REF +1.25V 1.23 Volts
FPGA +1.8V 1.80 Volts
#B Vin -48V -47.97 Volts
#A Vin -48V -47.97 Volts
occam#
The show environment table command displays the system high and low limits
for each sensor. The following example shows sample output from this
command:
occam# show environment table
Low High
Voltages: +5V 4.50 5.50 Volts
LM87 +3.3V 2.97 3.63 Volts
440GP +1.8V 1.62 1.98 Volts
+1.2V 1.08 1.32 Volts
+1.25V 1.13 1.38 Volts
+2.5V 2.25 2.75 Volts
SSTL2VTT +1.25V 1.15 1.35 Volts
SSTL2REF +1.25V 1.15 1.35 Volts
FPGA +1.8V 1.62 1.98 Volts
#B Vin -48V -57.60 -38.40 Volts
#A Vin -48V -57.60 -38.40 Volts
Temperatures: External temperature -40 118 C
Internal temperature -40 75 C
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 702 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Alarms Catalog
This section describes the BLC generated alarms sorted by feature. Alarms differ,
according to BLC model.
Fan Speed
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 703 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Temperature Exceptions
External Alarm
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 704 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 705 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
T1 Alarms
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 706 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Alarm Name T1 OK
Description This alarm is generated when the outstanding alarm condition of this
T1 port is cleared. This alarm is used to acknowledge all negative
alarms on this T1 port# received earlier. This alarm also clears all previ-
ously received T1 OK alarms from the device.
Service affecting? No
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 707 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 708 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Trunk Alarms
This section covers both TR08 and GR.303 alarms.
TR-08 Alarms
A brief note on the TR08 alarms:
Minor - non service-affecting (the RT door is open, etc.) Something is not right, but
everything is still functioning normally.
Major - some (but not all) of the subscribers have service affecting faults. In this
case, the shelf itself is working, but something has gone wrong with some of the
subscribers. There is only 1 major alarm.
Shelf - the trunk has lost "operational integrity". This means that the trunk has been
cut, the shelf circuit has exploded, or some other really bad thing. There is a shelf
alarm for each shelf (a, b, c, d).
Power/Misc. alarm - These alarms are used to indicate some type of environmental
off-normal condition.
If a shelf alarm is applied, then a major alarm will automatically be applied. The
trunk manager will apply a major alarm if any shelf alarm is to be applied. However,
a major alarm can be applied with no shelf alarm being applied (e.g., p->q does not
mean that q->p, from a logic perspective) if some subscribers have lost service but
not all of them (and the trunks are operating properly). Also, shelf alarms are fairly
serious matters.
A BLC can generate TR-08 alarms or report events seen on the data link with
another TR-08 entity such as a specials shelf. The events are broken into sub-
categories: incoming and outgoing. Incoming events are reported by 'this
equipment', whenever it receives an alarm on the FDL from some 3rd party
equipment (with which we have a TR-08 connection). Outgoing events are ones
generated by the TR-08 software on 'this equipment'.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 709 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 710 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 711 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
GR-303 Alarms
There are two critical alarms for TMC and EOC failure and two minor alarms
indicating a protection not available condition on TMC and EOC links respectively.
A number of alarms have been defined to report conditions with protection
switching. You may initiate a protection switch using either:
A Manual Switchover or
A Forced Switchover
In the case of a forced switchover, an immediate switch back is inhibited and the
switchover must occur even if the IG 'thinks" that the protected paths are
unavailable.
There are two autonomous switch alarms for TMC and EOC which indicate that the
equipment took the action itself without user interaction.
Alarms are defined here to indicate the following conditions for EOC and TMC links:
Forced switch to protect
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 712 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 713 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 714 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 715 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 716 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 717 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Alarm Name IG Up
Description Interface group has been started (user-commanded) or restarted (e.g.,
due to cards coming back up after a reboot).
Service Affecting? No
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 718 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 719 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
EPS Alarms
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 720 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 721 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Shelf Alarms
Card Alarms
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 722 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Configuration Change
The configuration change event is triggered whenever copy running to startup is
executed.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 723 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
GNK Alarms
These alarms report a GNDK bit detected (GNDK = Ground Key). This condition
indicates the presence of unbalanced current between Tip and Ring of greater than
10mA due to external disturbance. Shorting to ground, foreign voltage and
damaged POTS line chipset are possible causes. When detected, the port is
shutdown. i.e. battery is removed. The port is periodically re-enabled to check if the
condition is cleared.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 724 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 725 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 726 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Fan Alarms
These are the fan alarms which are sent out by the BLC when the fan tray is
inserted/removed.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 727 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 728 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
Alarm Name Client Queue HWM (high water mark) Threshold Reached
Description The high water mark threshold has been reached and the client queue
is dangerously close to dropping packets.
Service affecting? No
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 729 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 730 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Alarms Catalog
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 731 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Index of Alarms
Index of Alarms
30- the sensor that senses this condition . . . . . . . . . . . . . . . . . . . . . . . . 730
AC POWER_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
AC POWER_ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
CardDown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
CardInserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
CardRemoved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
CardUp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
Client Queue HWM (high water mark) Threshold Reached . . . . . . . . . . 760
Client Queue HWM Threshold Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
Client Queue Packets Are Not Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . 760
Client Queue Packets Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
ConfigurationChange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
DSL ModemInShowtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
DSL ModemOutShowtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
dslModemPowerChange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
EndpointChanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
EOC Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
EOC Auto Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
EOC Auto Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
EOC Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
EOC Forced Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
EOC Forced Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
EOC Inhibit Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
EOC Inhibit Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
EOC Manual Protection Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
EOC Manual Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
EOC Protection Not Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
EOC Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
EPS Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
EPS Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
EPS Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
EPS Loop Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
EPS Revert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
Fan Tray Inserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
Fan Tray Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
FanSpeedChange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Filter mask HWM Threshold cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Filter mask HWM Threshold reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Filter mask resources available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Filter mask resources exhausted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Filter Rule HWM Threshold Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
Filter Rule HWM Threshold Reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
Filter Rule Resources Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 732 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Index of Alarms
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 733 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 36: Alarms and Sensors
Index of Alarms
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 734 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Introduction
Chapter 37
Simple Network Management
Protocol (SNMP)
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Default SNMP Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Enabling SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Displaying SNMP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
SNMP Support For Activation of Subscriber Services. . . . . . . . . . . . . . . . . . . . . . . 747
Introduction
The BLC features a Simple Network Management Protocol (SNMP) agent, allowing
it to respond to SNMP requests from managers and send SNMPv2 traps to SNMP
managers.
There are four SNMP operations: get, getnext, set and trap. A trap is when an SNMP
agent sends an unsolicited message to one or more configured SNMP managers.
The SNMP traps generated by the BLC provide information about the interfaces and
the sensors in the BLC crossing configured thresholds. The traps supported for this
release include both standard and enterprise traps. The BLC supports SNMP V1 and
V2C.
MIB files are available on your documentation CD. Alternatively, you may request
a copy of the MIB from your Occam Networks’ customer service representative and
they will post the files to your FTP account on the Occam Networks’ support FTP
server.
SNMP support for activation of subscriber services is is described in the section
"SNMP Support For Activation of Subscriber Services" section on page 747.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 735 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Enabling SNMP
Enabling SNMP
Follow these steps to enable SNMP on the BLC:
1 Enter Global Configuration Mode:
occam# configure terminal
Enter configuration commands, one per line.
End with CNTL/Z.
occam(config)#
All SNMP devices that are assigned to the same community as members have
the same access rights, specifying a level of access.
read-only (ro), which enables only queries and get requests to be performed.
The default community string for read-only access is “public”.
read-write (rw), which enables configuration changes to be performed. The
default community string for read-write access is “private”
The host list is a list of hostnames or host IP addresses, in the form “A.B.C.D;
A1.B1.C1.D1; A2.B2.C2.D2”. Universal access from any host is defined by
“0:0:0:0”:
Examples of this command are shown below:
The following example creates a read-only community called “mycom” that
can be accessed from the host “10.1.2.3”:
occam(config)# snmp-server community mycom ro 10.1.2.3
3 Enter or modify the name of an SNMP contact person. The factory default
contact is “support@occamnetworks.com”:
occam(config)# snmp-server contact name
4 Enter or modify the physical location of the SNMP system. The factory default
is “Occam Networks, Santa Barbara, California”:
occam(config)# snmp-server location location
5 Enter or modify the name assigned to the SNMP system. The factory default
is BLC:
occam(config)# snmp-server name name
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 736 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Enabling SNMP
6 Use the various snmp-server enable traps commands to enable SNMP traps.
These commands are accepted quietly.
Table 37-2 below describes the snmp-server enable traps commands. The “no”
forms of these commands causes these traps to be disabled. For example, the
command no smnp-server enable traps standard all causes all standard SNMP
traps to be disabled.
Use the no form of these commands to stop traps from being sent.
Command Event
snmp-server enable traps envmon all Any of the environmental traps have
been triggered.
snmp-server enable traps envmon external-alarm The BLC’s alarm-in has been triggered
or cleared.
snmp-server enable traps envmon fan-speed Sensors have detected a change in the
fan speed.
snmp-server enable traps envmon temperature Sensors have detected a change in the
temperature within the BLC that is
beyond acceptable limits. The
command show environment table
shows the acceptable range of temper-
ature and voltage for each BLC.
snmp-server enable traps envmon voltage The power supply has detected a
change in the supplied voltage.
Command Event
snmp-server enable traps eps all Any of the EPS traps have been
enabled.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 737 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Enabling SNMP
Command Event
snmp-server enable traps kernel all Any of the kernel traps have been
triggered.
snmp-server enable traps kernel An AC power outage is detected or
acPowerNotification power has been restored.
snmp-server enable traps kernel The BLC’s fan tray has been removed or
fanTrayNotification inserted.
snmp-server enable traps kernel gnkNotification A GNK alarm has been detected on this
port and port has been shutdown or
the GNK alarm has been cleared on this
port and port has been re-enabled.
snmp-server enable traps kernel The BLC has shutdown due to over
overTempNotification temperature or the BLC re-enabled as
over temperature condition has
cleared.
Command Event
snmp-server enable traps leps all An Ethernet loop has been detected or
the loop condition has cleared.
snmp-server enable traps leps An Ethernet loop has been detected or
epsLoopNotification the loop condition has cleared.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 738 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Enabling SNMP
Command Event
snmp-server enable traps standard all Causes all standard traps to be enabled.
snmp-server enable traps standard cold-start The BLC is re-initializing.
snmp-server enable traps standard link-down A physical port driver has detected that
a previously active link has gone down.
snmp-server enable traps standard link-up A physical port driver has detected that
a previously inactive link has come
online.
Command Event
snmp-server enable traps subservices all Causes all subservices traps to be
enabled.
snmp-server enable traps subservices The client queue has exceeded
clientQueuePacketDropNotification threshold and packets are being
dropped or the condition has cleared
and packets are no longer being
dropped.
snmp-server enable traps subservices The client queue’s HWM threshold has
clientQueueThresholdNotification been reached and is dangerously close
to dropping packets or the client queue
is now below the HWM threshold.
snmp-server enable traps subservices Alerts to when the filter mask resources
ingressFilterMaskResourcesNotification have been exhausted and when there
are filter mask resources available
again.
snmp-server enable traps subservices Alerts to when the number of filter
ingressFilterMaskThresholdNotification masks has hit the HWM threshold and
when the filter mask HWM threshold
alarm has cleared.
snmp-server enable traps subservices Alerts to when the filter rule resources
ingressFilterRuleResourcesNotification have been exhausted and when there
are filter rule resources available again.
snmp-server enable traps subservices Alerts to when the number of filter
ingressFilterRuleThresholdNotification rules has hit the HWM threshold and
when the filter rule HWM threshold
alarm has cleared.
snmp-server enable traps subservices A subscriber port has been blacklisted
subscriberPortBlackListingNotification or is no longer being blacklisted.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 739 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Enabling SNMP
7 After you have chosen which traps you wish to enable, specify a host to be a
trap receiver with one of the following snmp-server host commands:
Command Description
snmp-server host all {ipaddr/hostname} Allows all SNMP traps to be sent to a
{community} {interface} specified host.
snmp-server host envmon {ipaddr/hostname} Allows all environmental monitor
{community} {interface} SNMP traps to be sent to a specified
host.
snmp-server host eps {ipaddr/hostname} Allows all SNMP EPS traps to be sent to
{community} {interface} a specified host.
snmp-server host kernel {ipaddr/hostname} Allows all SNMP kernel traps to be sent
{community} {interface} to a specified host.
snmp-server host leps {ipaddr/hostname} Allows all SNMP Ethernet loop traps to
{community} {interface} be sent to a specified host.
snmp-server host standard {ipaddr/hostname} Allows all SNMP standard traps to be
{community} {interface} sent to a specified host.
snmp-server host subservices {ipaddr/hostname} Allows all SNMP subservice traps to be
{community} {interface} sent to a specified host.
The variables for each snmp-server host command are described as follows:
Variable Event
ipaddr/hostname The hostname or IP address of the trap
recipient
community The community string to use when
sending this trap
interface The UDP interface upon which the
host is listening for traps. By default,
this is interface 162.
The “no” form of the snmp-server host commands causes these traps to be
disabled. For example, the command no smnp-server host standard all causes
all SNMP standard traps to no longer be sent to the previously specified host.
In the following example, all SNMP traps are sent to the IP address 1.1.1.1, the
community is named “managers”, and specified UDP interface is 192:
occam(config)# snmp-server host all 1.1.1.1 managers 192
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 740 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Enabling SNMP
10 Enter the show snmp command to confirm your SNMP configuration. The
following example shows sample output from this command:
occam# show snmp
Admin State: ON
sysContact: support@occamnetworks.com
sysName: BLC-6252
sysLocation: Occam Networks, Santa Barbara, California
sysDescription: BLC-6252
0 SNMP packets input
0 Bad SNMP version errors
0 Unknown community name
0 Illegal operation for community name supplied
0 Encoding errors
0 Number of requested variables
0 Number of altered variables
0 Get-request PDUs
0 Get-next PDUs
0 Set-request PDUs
0 Too big errors (Maximum packet size 1500)
0 Requested PDUs that do not exist
0 Bad values
0 Read onlys
0 General errors
0 Get-request responses
0 Traps received
0 SNMP packets output
0 Too big errors (Maximum packet size 1500)
0 No such name errors
0 Bad values errors
0 General errors
0 Response PDUs
0 Trap PDUs
0 Get-requests sent
0 Get-next requests sent
0 Set-requests sent
SNMP traps:
fan-speed: disabled
link-down: disabled
link-up: disabled
cold-start: disabled
voltage: disabled
temperature: disabled
SNMP Communities:
public
Access: ro
Managers: 0:0:0:0
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 741 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Enabling SNMP
private
Access: rw
Managers: 0:0:0:0
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 742 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Displaying SNMP Information
The show snmp contact command displays the SNMP contact information:
occam> show snmp contact
SysContact: support@occamnetworks.co
The show snmp hostname command displays the host that receives SNMP traps:
occam> show snmp hostname
sysName: snmp-server
The show snmp location command displays the SNMP location information:
occam> show snmp location
sysLocation: Occam Networks, Santa Barbara, California
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 743 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Displaying SNMP Information
The show snmp command displays all of the above information together:
occam> show snmp
Admin State: ON
sysContact: support@occamnetworks.com
sysName: BLC-6252
sysLocation: Occam Networks, Santa Barbara, California
sysDescription: BLC-6252
0 SNMP packets input
0 Bad SNMP version errors
0 Unknown community name
0 Illegal operation for community name supplied
0 Encoding errors
0 Number of requested variables
0 Number of altered variables
0 Get-request PDUs
0 Get-next PDUs
0 Set-request PDUs
0 Too big errors (Maximum packet size 1500)
0 Requested PDUs that do not exist
0 Bad values
0 Read onlys
0 General errors
0 Get-request responses
0 Traps received
0 SNMP packets output
0 Too big errors (Maximum packet size 1500)
0 No such name errors
0 Bad values errors
0 General errors
0 Response PDUs
0 Trap PDUs
0 Get-requests sent
0 Get-next requests sent
0 Set-requests sent
SNMP traps:
external-alarm: disabled
fan-speed: disabled
temperature: disabled
voltage: disabled
cold-start: disabled
link-down: disabled
link-up: disabled
SNMP Communities:
public
Access: ro
Hosts: 0:0:0:0
private
Access: rw
Hosts: 0:0:0:0
occam>
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 744 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Displaying SNMP Information
The show snmp community command displays any defined SNMP communities:
occam# show snmp community
SNMP Communities:
public
Access: ro
Managers: 0:0:0:0
private
Access: rw
Managers: 0:0:0:0
mycom
Access: ro
Managers: 10.0.0.177
mycom2
Access: rw
Managers: peckory
The show snmp trap command displays all SNMP traps, as well as defined trap
receivers. Traps are messages that alert the SNMP manager to a condition on the
network.
The main types of events that would cause traps to be sent out are related to:
interfaces (operation state entering/leaving the down state)
sensors (crossing of thresholds by the readings from the various sensors).
The show environment table command, discussed in Chapter 36, Alarms
and Sensors on page 700 displays the system high and low limits for each
sensor.
occam# show snmp trap
SNMP traps:
external-alarm: enabled
fan-speed: enabled
temperature: enabled
voltage: enabled
cold-start: enabled
link-down: enabled
link-up: enabled
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 745 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
Displaying SNMP Information
In Privileged Mode the show snmp command will also show community and trap
information, as shown in the following example:
occam# show snmp
Admin State: ON
sysContact: support@occamnetworks.com
sysName: BLC-6252
sysLocation: Occam Networks, Santa Barbara, California
sysDescription: BLC-6252
0 SNMP packets input
0 Bad SNMP version errors
0 Unknown community name
0 Illegal operation for community name supplied
0 Encoding errors
0 Number of requested variables
0 Number of altered variables
0 Get-request PDUs
0 Get-next PDUs
0 Set-request PDUs
0 Too big errors (Maximum packet size 1500)
0 Requested PDUs that do not exist
0 Bad values
0 Read onlys
0 General errors
0 Get-request responses
0 Traps received
0 SNMP packets output
0 Too big errors (Maximum packet size 1500)
0 No such name errors
0 Bad values errors
0 General errors
0 Response PDUs
0 Trap PDUs
0 Get-requests sent
0 Get-next requests sent
0 Set-requests sent
SNMP traps:
fan-speed: disabled
link-down: disabled
link-up: disabled
cold-start: disabled
voltage: disabled
temperature: disabled
SNMP Communities:
public
Access: ro
Managers: 0:0:0:0
private
Access: rw
Managers: 0:0:0:0
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 746 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
SNMP Support For Activation of Subscriber Services
The features supporting a DSL port are described below on page 747.
The features supporting an Ethernet subscriber port are described on page 748.
DSL Ports
For a DSL ports, the OCCAM-SERVICE-ACTIVATION-MIB will allow selecting a DSL
port and supports the following operations:
Read all existing info fields associated with the DSL port
Read/Set the Access Profile assigned to a DSL Service assigned to a DSL port
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 747 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
SNMP Support For Activation of Subscriber Services
Read all existing info fields associated with Ethernet Subscriber port
Media Gateway
For a Media Gateway, the OCCAM-SERVICE-ACTIVATION-MIB will allow selecting a
voice port and supports the following operations:
Read/Set the voice port description (note: this may go away if description is
dropped)
Read all existing info fields associated with the voice port
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 748 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
SNMP Support For Activation of Subscriber Services
Read/Set the SIP params (User Name, Display Name, Auth User Name, Password)
Trunking Gateway
For a Trunking Gateway, the OCCAM-SERVICE-ACTIVATION-MIB will allow selecting
a channel on an IG and supports the following operations:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 749 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 37: Simple Network Management Protocol (SNMP)
SNMP Support For Activation of Subscriber Services
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 750 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 38: System Logging (Syslog)
Introduction
Chapter 38
0 System Logging (Syslog)
In this Chapter
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
Enabling Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Disabling Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Displaying Syslog Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Introduction
System logging (syslog) allows you to save messages in a log file or send messages
to a specified syslog server host’s IP address or hostname. These messages are useful
to help you log and analyze configuration events and system error messages (i.e.,
interface status and security alerts).
BLC logs are maintained internally in memory and are limited to 1MB. If the BLC
reboots the logs are lost. The log file is circular; if the size of the log reaches 1MB
then subsequent entries start at the beginning of the file, writing over the oldest
entries. To maintain logs across BLC reboots and larger then 1MB, Occam
recommends using an external syslog server.
BLC syslog software allows you to choose the types of information captured by
specifying a “facility”, which describes the part of the system that generated the
message and a “level”, which indicates the severity of the message.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 751 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 38: System Logging (Syslog)
Enabling Syslog
Enabling Syslog
Enable syslog with the logging command in Global Configuration mode. Syslog
allows you to log and analyze system events and errors to a local log file or to a
remote loghost to be analyzed. Messages logged locally are written to the file
/var/log/messages. Multiple logging entries are permitted and each may specify
facility, log severity level, and loghost.
The command allows you to specify a “facility” and a “level”, separated by a period.
The facility.level parameter is optional; if skipped, “*.warn” is used:
occam(config)# logging [facility.level] syslog-host
Facilities
A facility describes the part of the system that generated the message. An asterisk
(*) is a wildcard meaning “all facilities”, which is the factory default. The facilities
available and their descriptions are shown in Table 38-1:
Facilities Description
auth Security/Authorization messages
authpriv Security/Authorization messages
(private)
daemon System daemon
ftp FTP daemon
kern Kernel messages
syslog Messages generated internally by syslog
user User process messages
Levels
A level indicates the severity of the message. An asterisk (*) is a wildcard meaning
“all levels”. When a level is specified, log messages of that level and all higher levels
are sent to the logging host. The factory default level is “warn”. The levels available
and their descriptions are shown in Table 38-2:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 752 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 38: System Logging (Syslog)
Enabling Syslog
The following command specifies that the Syslog server host “syslog-
host.occamnetworks.com” receive messages that are generated by the authori-
zation system facility at the informational level and above:
occam(config)# logging auth.info syslog-host.occamnetworks.com
The following command specifies that the syslog server host “syslog-
host.occamnetworks” receive all messages generated by the Kernel:
occam(config)# logging kern.* syslog-host.occamnetworks.com
The following command uses the factory defaults to specify that the syslog
server host “elm.occamnetworks.com” receive messages that are created by all
facilities at the warning level and above:
occam(config)# logging elm.occamnetworks.com
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 753 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 38: System Logging (Syslog)
Disabling Syslog
Disabling Syslog
The no logging [facility.level] syslog-host command in Global Configuration mode
deletes a syslog server with the specified facility level and host. The facility level is
optional; if skipped, all levels to the host are removed.
occam(config)# no logging [facility.level] syslog-host
The following examples show various logging commands that disable logging:
The following command disables all logging to the syslog server host “syslog-
host.occamnetworks.com”:
occam(config)# no logging syslog-host.occamnetworks.com
The following command disables logging only from the kernel to the Syslog
server host “syslog-host.occamnetworks.com”:
occam(config)# no logging kern.* syslog-host.occamnetworks.com
2 The command debug mgcp can be used to monitor message flow overall. To
send the debug information syslog, the facility level must be “daemon” or
higher:
occam# debug mgcp {all | errors | events | flag | packets | parser}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 754 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Startup Configuration
Chapter 39
Viewing Your Hardware and
Software Configuration
In This Chapter:
Viewing the Startup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
Viewing the Running Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Viewing Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
Viewing the Software and Hardware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Viewing the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Checking the Network Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
After configuring the BLC, you can use various commands to view the system
hardware and software configuration.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 755 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Running Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 756 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Running Configuration
Use the show running-config diff command from Privileged Mode to display
the differences between the system running configuration and the startup
configuration. This command allows the administrator to view the differences
between the two configurations and determine if the running configuration
should be saved.
In this example, script version 5.5R1 is the current configuration and script
version 5.5 “171,174d170” is the startup configuration. In version 5.5R1 the
source of the primary network clocking has been changed from system, the
factory default, to the NCO_NTP reference:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 757 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Running Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 758 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing Interfaces
Viewing Interfaces
Viewing Information About All Interfaces
Enter the show interfaces command from User or Privileged Mode without
specifying an interface to display information about all of the system’s interfaces.
The following example shows sample output:
occam# show interfaces
Ethernet4/1 is up, line protocol is up
Hardware is GigabitEthernet, address is 0002.8600.078c
MTU 1600 bytes, BW 1000000 Kbit
full, 1000
Media gigabitEthernet
EPS Settings:
path participant, path configuration is ALL
Queueing strategy: Strict Priority
Output Queue (Priority Queue (1=Hi): size):
PQ 1: 0 PQ 2: 0 PQ 3: 0 PQ 4: 0
PQ 5: 0 PQ 6: 0 PQ 7: 0 PQ 8: 0
Total queue drops: 0
Multicast:
Port configured as passthrough port.
dot3AlignmentErrors: 0
dot3FCSErrors: 0
dot3SingleCollisionFrames: 0
dot3MultipleCollisionFrames: 0
dot3DeferredTransmissions: 0
dot3LateCollisions: 0
dot3ExcessiveCollisions: 0
dot3FramesTooLong: 0
rmonRxDropEvents: 0
rmonRxOctets: 2552317119
rmonRxPkts: 414716700
rmonRxBroadcastPkts: 36967
rmonRxMulticastPkts: 25301189
rmonRxCRCAlignErrors: 0
rmonRxUndersizePkts: 0
rmonRxOversizePkts: 0
<Text excluded>
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 759 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing Interfaces
Command Description
show interfaces bvi [number] Displays BVI information configura-
tion, status, and statistics
show interfaces ethernet [number] Displays information about one or all
Ethernet interfaces
show interfaces ethernet fiber Displays information about one or all
[number] Ethernet fiber interfaces
show interfaces xg [number] Displays information about one or all
XG interfaces
show interfaces xg fiber [number] Displays information about one or all
XG fiber interfaces
Command Description
show interfaces ethernet summary Displays information about all the
Ethernet interfaces in a summarized
format
show interfaces xg summary Displays information about all the xg
interfaces in a summarized format
show interfaces summary Displays information about all the
interfaces in a summarized format
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 760 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Software and Hardware Version
Processor: 440GP Rev. C at 396 MHz, revision 4.129 (pvr 4012 0481)
VCO: 792 MHz, PLB: 132 MHz, OPB: 66 MHz, EPB: 66 MHz, Sysclk: 33 MHz
Processor: 440GP Rev. C at 396 MHz, revision 4.129 (pvr 4012 0481)
VCO: 792 MHz, PLB: 132 MHz, OPB: 66 MHz, EPB: 66 MHz, Sysclk: 33 MHz
Hostname ces1, uptime is 6 days, 3:30, load average 0.78, 0.31, 0.20
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 761 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Software and Hardware Version
Base board:
bytes_used: 448/496
rev_cpu: 440GP Rev. C revNum: 4.129 (pvr 4012 0481)
mac_address: 00:02:86:00:0b:56
company_name: OCCM
board_name: 4
board_assembly: 900032-01
board_type: 1
board_serial_number: 08361720
board_revision: C1
manufacture_date: 8/14/2003
top_level_assembly: xx6150
model_num: 6150
rev_fpga0: 000.020
rev_fpga1: 000.007
rev_pld: 1.0
chassis: 12RU
shelf_id: ccc1
build_id: V5_3T6
product: wartortle
platform: wartortle
cfCapacity: 64225280
patch_rc_conf: yes
rev_qfalc_0: 0x02
Mezz0:
bytes_used: 269/496
company_name: OCCM
board_name: 11
board_assembly: 900037-01
board_type: 1
board_serial_number: 08361964
board_revision: C1
manufacture_date: 8/23/2003
rev_bcm5703_mac: 0x1002
rev_bcm5703_driver: 0x1002
rev_bcm5691_switch: BCM5691_A1
rev_bcm5691_driver: 5.3.1
bcm_switch_type: 5691
Mezz1:
bytes_used: 144/496
company_name: OCCM
board_name: 14
board_assembly: 900045-01
board_type: 1
board_serial_number: 03461953
board_revision: D0
manufacture_date: 3/16/2004
Fan:
bytes_used: 145/496
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 762 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Software and Hardware Version
company_name: OCCM
board_name: 29
board_assembly: 900054-01
board_type: 1
board_serial_number: 99900020
board_revision: B2
manufacture_date: 10/18/2004
Backplane:
bytes_used: 185/496
board_assembly: 900050-01
board_name: 24
board_revision: B1
board_serial_number: 12372019
board_type: 1
company_name: OCCM
manufacture_date: 12/9/2003
top_level_assembly: 695102
model_num: 6012
Boot info:
bytes_used: 1491/65520
reset_reason_5: reason Unknown(0x0) : Date unknown
reset_reason_6: reason Unknown(0x0) : Date Thu Sep 21 20:20:37 UTC 2006
reset_reason_7: reason Unknown(0x0) : Date Tue Sep 26 18:23:58 UTC 2006
reset_reason_8: reason Unknown(0x0) : Date Wed Sep 27 17:20:36 UTC 2006
reset_reason_9: reason Unknown(0x0) : Date Wed Oct 4 16:04:21 UTC 2006
reset_reason_10: reason Unknown(0x0) : Date Thu Oct 5 21:02:35 UTC 2006
reset_reason_11: reason Unknown(0x0) : Date Tue Oct 10 17:38:39 UTC 2006
reset_reason_12: reason Unknown(0x0) : Date Thu Oct 12 17:26:06 UTC 2006
reset_reason_13: reason Unknown(0x0) : Date Thu Oct 12 18:23:05 UTC 2006
reset_reason_14: reason Unknown(0x0) : Date Wed Nov 29 19:35:29 UTC 2006
reset_reason_16: reason Unknown(0x0) : Date Tue Dec 5 10:18:06 PST 2006
reset_reason_17: reason Unknown(0x0) : Date Wed Dec 6 09:15:52 PST 2006
reset_reason_18: reason Unknown(0x0) : Date Thu Dec 7 09:28:29 PST 2006
reset_reason_19: reason Unknown(0x0) : Date Fri Dec 8 13:48:28 PST 2006
mac_address: 00:02:86:00:0b:56
freq_vco: 2f34f600
freq_cpu: 179a7b00
freq_plb: 07de2900
freq_opb: 03ef1480
freq_epb: 03ef1480
freq_sysclk: 01f78a40
occamBoardType: 00000000
occamBoardSubType: 00000000
rev_booter: Ver:V5_3T6 built Fri Dec 8 15:15:10 PST 2006 by occamos
on bfg3.est.occamnetworks.com
boot_count: 0x000014
reset_last_reason: Unknown
reset_reason_reg: 0x0
reset_reason_20: reason Unknown(0x0) : Date Fri Dec 8 16:24:55 PST 2006
rtcPwrUptimeLast: 790861
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 763 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Software and Hardware Version
Occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 764 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Viewing the Chassis
----------------------------------------------------------------------
| 6012 Chassis |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| 6 | 6 | 6 | 6 | 6 | 6 | | | 6 | | | |
| 1 | 1 | 1 | 1 | 1 | 4 | | | 2 | | | |
| 5 | 5 | 5 | 5 | 5 | 4 | | | 1 | | | |
| 0 | 0 | 0 | 0 | 1 | 0 | | | 2 | | | |
| | | - | | - | - | | | | | | |
| | | 0 | | 0 | 0 | | | | | | |
| | | 1 | | 1 | 1 | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| U/u | U/u | U/u | U/u | U/u | U/u | | | U/u | | | |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 765 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Checking the Network Connection
Pinging IP Hosts
Verify specific IP hosts are reachable by entering the ping command as follows:
ping {IP address or host name} [BVI-number] [COUNT] [SIZE]
[SIZE] = Optional) Specifies the datagram size. The range is from 40 to 18024
bytes in each ping. The default is 64 bytes.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 766 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Checking the Network Connection
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 767 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 39: Viewing Your Hardware and Software Configuration
Checking the Network Connection
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 768 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Introduction
Chapter 40
Updating Your System
Configuration
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
BLC System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
Upgrading and Verifying a New Software Release . . . . . . . . . . . . . . . . . . . . . . . . . 771
Displaying a List of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
Using the “boot enable” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
Installing a New Kernel or Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Checking the Validity of a Software Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
Deleting a Software Release File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Displaying the Status of Installed Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
Introduction
The BLC is upgradable via FTP of a new image from a remote FTP server. The FTP
server must be reachable via IP from the BLC and the ISO image must be within the
FTP server’s directory space.
The BLC software resides on compact flash, which contains two kernel images. One
software load/kernel combination is the primary image and the other is the
secondary image.
The BLC monitor will automatically boot the primary image unless instructed to do
otherwise. The software release that is booted becomes the current image; the
other is termed the alternate image. The selection of the primary system will be
under CLI control.
Note: You must use an FTP server that supports the size command with Occam
Networks FTP client. Examples of these servers are:
Windows 2000 (with the Microsoft Internet Information Server pkg)
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 769 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
BLC System Components
Boot PROM
The Boot Information EEPROM is shared with the BLC monitor, which uses the
information in the PROM to determine the location and relative boot priority of
each of the system images stored in compact flash. The BLC monitor may also use
the PROM to store a state variable (the "Boot Count") that allows it to fall back
automatically to the secondary or tertiary system image if it is unable to boot the
primary system image.
Boot Flash
Boot Flash is a block-erasable flash memory device that is divided into nine logical
partitions, each of which begins at a known fixed address in processor memory. One
of these partitions contain the bootable Linux kernel image; the fourth partition
contains the executable code for the BLC monitor.
Compact flash partitions 1 and 2 contain Linux kernels that boot directly into the
BLC software. Each of these bootable images depends on a uniquely-named Occam
OS Image File that is stored on the Compact Flash device.
Partition 3 contains a stand-alone Linux kernel, called the Emergency Kernel, that
does not depend on Compact Flash. This kernel includes a RAM Disk image that
contains a minimal set of Linux utility programs that may be used to format
Compact Flash and manually download and install a BLC software release on the
unit.
Partition 7 contains the executable code for the BLC monitor itself.
Image Files
A BLC software release is delivered as a single, large (20 MB) tarred and zipped
image file. The image file includes the BLC application software and data files, as
well as installable images for the Linux kernel and the BLC monitor. The image file
is self-contained. There are no partial releases.
Each image file has a name of the form OCCAMOS.xxxxxxxx, where xxxxxxxx is the
unique "build identifier" of that version of the system. Released versions of the
software have alphanumeric identifiers, such as V4_0_Product Name
A software release is installed by copying its image file to compact flash, extracting
the Linux kernel from the image file, writing the kernel to compact flash partition
1 or 2, and rebooting the BLC using the newly installed kernel.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 770 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Upgrading and Verifying a New Software Release
3 Load the new code onto the BLC with the command upgrade all {ftp-url}.
4 When the command line reappears, execute the command show boot status
(You should see a listing of two main partitions. One partition has the old code
and one has the new code. Make sure that one does indeed have the new code
version):
occam# show boot status
5 Reboot the system. If the optional parameter seconds is defined the system will
postpone the reload for the defined number of seconds.
Some software components (such as the Interface-Group manager) have the
capability to veto a reload operation if they are currently performing some crit-
ical operations (such as starting an Interface Group). The reload command
would then be rejected. If you wants to override this veto mechanism you may
use the reload force command.
The system confirms that that an upgrade had not been started between the
time the reload was queued and the time the reboot should take place. If this
occurs and the reload command has been issued the system will not reload. If
the reload force command command has been issued, the system will reload no
matter what.
Note: If you reload while logged into the BLC via Telnet or SSH, your session is
terminated. It takes approximately one minute for the BLC to be ready to accept
new remote commands.
occam# reload [1-43200]
6 When the command line reappears, execute the command show version to
make sure that the new code has been loaded onto the system:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 771 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Upgrading and Verifying a New Software Release
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 772 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Using the upgrade software Command
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 773 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Using the “boot enable” Command
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 774 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Installing a New Kernel or Firmware
This command may be used to copy the primary kernel into the secondary partition.
Please see the separate publication, Command Reference Guide, for an example of
how to use this command to do so.
Note: This command may be extended to install from a source other than an image
file-URL.
An example of this command is:
occam# boot install firmware flash:OCCAMOS.OCCAMOS.V4_1R1_6640
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 775 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Checking the Validity of a Software Image
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 776 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Deleting a Software Release File
Note: The delete command may be extended to delete other files on the compact
flash file system, or on other file systems.
An example of this command is:
occam# delete flash:OCCAMOS.xxxxxxxxx
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 777 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Displaying the Status of Installed Software
Partition 1
Header type : ppcboot
Image size : 2093118
Image checksum : 0xd367b1c5
Image type : kernel
Compression type : none
Load address : 0x500000
Entry address : 0x500000
Build identifier : 1005746735
Partition 1 is primary
Kernel build id is 1076495402, image file is OCCAMOS.1076495402
This is the current system image
Partition 2 is secondary
Kernel build id is 1076322603, image file is OCCAMOS.1076322603
Partition 3 is not enabled
It is not a bootable image
FPGA partition
Image is invalid
Tertiary partition is invalid
The current user file system is /cf/OCCAMOS.1076495402
Its type is 'ext2'
Its build id is 1076495402
Filesystem images:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 778 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Displaying the Status of Installed Software
OCCAMOS.1076322603 (secondary)
OCCAMOS.1076495402 (current,primary)
occam#
occam#
occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 779 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 40: Updating Your System Configuration
Displaying the Status of Installed Software
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 780 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 41: Configuring Network Traffic Intercept (NTI)
Introduction
Chapter 41
Configuring Network Traffic
Intercept (NTI)
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
NTI Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
NTI Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
Configuring a NTI Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
Enabling NTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
Viewing the NTI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Introduction
This chapter describes the Occam Networks’ Network Traffic Intercept (NTI) feature
that supports the data intercept requirements of CALEA as described in J-STD-025A
Section 4.6.3 (Packet Data). A Law Enforcement Agency (LEA) may use the NTI
feature to instantly monitor traffic at any point in the outside or inside plant
network.
Any Occam BLC that has Layer 2 connectivity to a target subscriber’s device(s)
can provide NTI capabilities without affecting performance, network/element
configuration or traffic flow.
Any traffic type can be monitored – HTTP, DHCP, VoIP, ARP, etc. – without
service interruption and without alerting end users to monitoring activity.
MAC Address
NTI uses a target device’s Layer 2 MAC address to identify the target data stream.
This target device may be such devices as an ONT, a PC, a set-top box, soft phone,
etc.
Using the MAC address of an ONT will allow you to capture the traffic bound for
inbound terminating on the ONT. This includes:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 781 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 41: Configuring Network Traffic Intercept (NTI)
Introduction
show bridge: The show bridge command may be used to display all of the
currently learned MAC addresses on that BLC, in conjunction with the DSL and
Ethernet interfaces they were learned on.
show associations: If the target subscriber’s devices are behind an ONT you may
enter the show associations command to view the MAC addresses of devices on
specific VLANs that have either static or dynamic associations.
internal mode: When the host BLC is configured with the command mode
internal from NTI configuration mode the tcpdump tool decodes the inter-
cepted traffic. The tcpdump tool allows you to intercept and display TCP/IP and
other packets on that interface. tcpdump output may be seen by entering the
command show nti tcpdump on this BLC, as described in the section Viewing the
NTI Configuration on page 787.
local mode: When the host BLC is configured with the command mode local
from NTI configuration mode intercepted traffic is forwarded out the
subscriber’s host BLC’s craft port. This traffic may be viewed by connecting a
network sniffing capable device to the craft port such as etherreal, tcpdump,
etc.
remote mode: When the BLC is configured with the command mode remote
{ip-address} from NTI configuration mode, intercepted traffic is UDP tunneled
on port 9999 to an OSSAN. If an OSSAN is used to intercept the subscriber traffic
it may be stored for future analysis. LEAs would typically use remote mode to
monitor targeted subscriber traffic.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 782 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 41: Configuring Network Traffic Intercept (NTI)
Introduction
TARGET
SUBSCRIBER'S CONSOLE ATTACHED TO OSSAN
DEVICE CRAFT PORT ON HOST BLC
EPS RING
BLCS IN CO
TARGET
SUBSCRIBER'S
HOST BLC IN RT CENTRAL OFFICE
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 783 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 41: Configuring Network Traffic Intercept (NTI)
NTI Configuration Overview
2 Enter NTI Profile Configuration Mode. Create a profile by using the name of a
profile you want to create, or an existing profile you want to modify. Use the no
nti-profile command to delete a profile:
Occam(config)# nti-profile {nti-profile-name}
3 Create a profile by using the name of a profile you want to create, or an existing
profile you want to modify. Use the no nti-profile command to delete a profile:
Occam(config)# nti-profile {nti-profile-name}
4 Enter the ingress interface on the host BLC for the target subscriber’s device. The
service parameter identifies the type of traffic that you wish to monitor (for
example, ARP traffic). If you simply wish to monitor the user traffic you may
omit the service parameter:
occam(config-nti-prf)# interface dsl {dsl-interface-number}
[service-number]
occam(config-nti-prf)# interface ethernet {ethernet-interface-
number} [service-number]
5 Enter the MAC address of the target subscriber’s device. Use the command no
mac to remove the specified MAC address:
occam(config-nti-prf)# mac {AA:BB:CC:DD:EE:FF}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 784 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 41: Configuring Network Traffic Intercept (NTI)
Enabling NTI
Enabling NTI
1 Enter Global Configuration Mode:
Occam# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Occam(config)#
local mode
In local mode intercepted traffic is forwarded out the craft device:
Occam(config-nti)# mode local
remote mode
In remote mode intercepted traffic is UDP tunneled on port 9999 to an
OSSAN. This is the mode would typically be used by law enforcement.The IP
address of the OSSAN must also be entered:
Occam(config-nti)# mode remote {IP address}
For example:
Occam(config-nti)# mode remote 192.168.21.132
5 Enable NTI:
Occam(config-nti)# no shutdown
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 785 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 41: Configuring Network Traffic Intercept (NTI)
Viewing the NTI Configuration
The NTI mode is set to “internal”. Other NTI mode options are local and remote.
This is configured with the command mode internal entered from NTI Config-
uration mode, as described in the section Enabling NTI on page 785.
The NTI profile is named “dis”. A NTI profile is configured with the command
nti-profile {profile-name} entered from Global Configuration mode, as
described in the section Configuring a NTI Profile on page 784.
The NTI state is “active”. If NTI was not in progress the state would be “inactive”.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 786 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 41: Configuring Network Traffic Intercept (NTI)
Viewing the NTI Configuration
There have been 201435 catured packets sent to and from the monitored device.
The monitored device has the MAC address “00:02:86:00:06:87”. The MAC
address is entered in the NTI profile with the command mac, as described in the
section Configuring a NTI Profile on page 784.
The last four lines show the rate calculations (rx pps), including the rate limit,
and by how much this rate may have been exceeded.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 787 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 41: Configuring Network Traffic Intercept (NTI)
Viewing the NTI Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 788 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Introduction
Chapter 42
ADSL2+ Line Testing- SELT, DELT
and MLT
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
SELT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
DELT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
Examples of SELT and DELT Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Introduction
Occam Networks provides the ability to test ADSL2+ lines with Dual Ended Loop
Testing (DELT) and Single Ended Loop Testing (SELT).
DELT and SELT are supported on the following BLCs:
BLC 6212
BLC 6214
BLC 6244
BLC 6246
BLC 6252-03
DELT and SELT can be used to estimate and ascertain particular characteristics of
the subscriber line. DELT and SELT can be used to determine loop length, the
location of bridge taps, the length of bridge taps and the gauge of loop segments.
DELT and SELT can also help determine where shorts are occurring in the line and
the location of load coils, providing information about line noise and other
interference characteristics.
DELT and SELT testing capability is built into each port on an Occam BLC ADSL2/2+
blade. The Occam BLC ADSL2/2+ blade hardware provides raw data measurements
that can be processed and interpreted. Interpretation of the results requires
analysis software. Occam Networks provides an interpretation software package
called “Dr. DSL” from our partner Aware, Inc. Please contact your Occam Networks
sales representative for information about the purchase of the “Dr. DSL” package.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 789 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
SELT
SELT
SELT does not require any external test equipment in either the CO or at the remote
end of the loop, and is thus very useful to prequalify a loop and determine if it is
capable of supporting ADSL2+ service before installation.
Use the command test dsl selt {dsl-interface-number}[period <1..6>] from
Privileged mode to launch a SELT test on the specified port's copper loop. Optionally
enter a parameter for the number of twenty second periods to measure. The factory
default is 2 (i.e. forty seconds). The minimum duration is 1 (twenty seconds).
You must shut down the DSL port before starting SELT. In addition a CPE may not
be connected to the other end of the line. If a CPE is present when SELT is run the
results will be distorted.
You may not run SELT and DELT at the same time. If you start DELT while SELT is
running, SELT is stopped and DELT starts. The DSL port is disabled (shutdown) after
the test. You may stop SELT by entering the command shutdown from DSL
Interface Configuration mode.
Results of the SELT test may be viewed by entering the command show dsl selt {dsl-
interface-number} but test results should be interpreted through the Aware
software application for clarity. Sample test results are shown on page 795.
Figures 42-1 through 42-2 show an example of a SELT loop test.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 790 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
SELT
BLC IN RT
RESIDENCE
(NO ADSL2+ MODEM )
BLC IN RT
RESIDENCE
(NO ADSL2+ MODEM )
AWARE SOFTWARE
APPLICATION
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 791 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
DELT
DELT
DELT requires equipment that supports the DELT feature at both ends of the copper
loop and thus may not be used if an ADSL 2+ modem has not yet been installed at
a customer’s home. The results from DELT are more useful than those from SELT, as
they provide better loop diagnostics and more detailed information.
DELT may be started on any DSL line, even if it is in a bonding group, in any
administrative state (enabled or disabled), or operational state (idle, handshake,
showtime), or even when SELT is running. As stated above, if you start DELT while
SELT is running, SELT is stopped and DELT starts.
The port is restored after the test to the prior administrative state regardless of the
success or failure of the test. You may stop DELT by entering the command
shutdown from DSL Interface Configuration mode.
Note: Verify that the modem supports DELT functionality. If the command test dsl
delt is run against a modem without support, you will get a Loop Diag Status of
"FAILED Wrong_Profile" in the test result.
DELT requires a DMT operating mode of G992.3 or higher. SELT has no requirement
on the operating mode.
Use the command test dsl delt {dsl-interface-number} from Privileged mode to
launch a DELT test on the specified port's copper loop.
Results of the DELT test may be viewed by entering the command show dsl delt
{dsl-interface-number} but test results should be interpreted through the Aware
software application for clarity. Sample test results are shown on page 795.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 792 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
DELT
BLC IN RT
RESIDENCE
(with ADSL2+ MODEM )
BLC IN RT
RESIDENCE
(with ADSL2+ MODEM )
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 793 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
DELT
BLC IN RT RESIDENCE
(with ADSL2+ MODEM )
AWARE APPLICATION
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 794 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
AGC 3.0 dB
FrontEndDelay (sample at 2.2 MHz) 51.5 ms
FrontEndGain 169.5 dB
-----------------------------------------------------------
Uncalibrated Echo Response (Offset: Real Imaginary)
0: 0 0
1: -132830091 72900670
2: -3407358 162400744
3: 136126566 104716551
4: 178273873 -46684193
5: 79662104 -185062427
6: -109043177 -196196940
7: -251751520 -34821443
8: -200898371 209933198
9: 67588817 324455655
10: 344878485 134835756
11: 320406805 -234996475
12: -23401455 -404499328
13: -336756682 -206394471
14: -348985782 134981202
15: -112395165 331495173
16: 159504581 285095069
17: 295984585 76942599
18: 248615167 -144960919
19: 75237435 -261776248
20: -116882323 -231354825
21: -231324557 -89114766
22: -223078711 83287203
23: -109455443 201819799
24: 46810079 217078992
25: 170787493 131245955
26: 209211029 -8933123
27: 151185229 -136930697
28: 28870416 -196924831
29: -100011604 -166801413
30: -178858368 -64918009
31: -176210567 60656569
32: -97373142 154564196
33: 20140172 178070451
34: 124384291 124400667
35: 171646763 19770050
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 795 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 796 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 797 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 798 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 799 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
-----------------------------------------------------------
Variance
0: -32768 3330 2800 2950 3070 3790 4230 4900
8: 5420 5990 6400 6720 6820 6930 6850 6770
16: 6590 6450 6320 6120 5960 5850 5710 5550
24: 5390 5340 5210 5110 4900 4900 4770 4710
32: 4590 4570 4430 4430 4310 4310 4200 4170
40: 4030 4030 3930 3920 3810 3840 3720 3740
48: 3650 3700 3580 3560 3440 3500 3420 3440
56: 3390 3400 3310 3340 3240 3280 3230 3280
64: 3200 3240 3220 3240 3260 3210 3200 3210
72: 3150 3120 3150 3210 3180 3260 3200 3230
80: 3170 3280 3270 3250 3270 3330 3320 3330
88: 3320 3420 3380 3430 3450 3530 3460 3580
96: 3560 3600 3630 3650 3670 3710 3740 3770
104: 3780 3880 3870 3890 3960 3970 3970 4070
112: 4040 4120 4110 4150 4210 4260 4300 4340
120: 4380 4420 4400 4490 4510 4550 4550 4600
128: 4640 4680 4670 4740 4750 4740 4770 4850
136: 4880 4900 4930 5000 4970 5030 5050 5080
144: 5130 5090 5180 5210 5220 5260 5300 5300
152: 5340 5350 5350 5400 5470 5470 5460 5520
160: 5540 5540 5610 5600 5680 5670 5710 5760
168: 5720 5760 5800 5790 5830 5910 5880 5900
176: 5910 5930 5980 5920 5980 6010 6020 6090
184: 6030 6120 6100 6130 6190 6170 6170 6180
192: 6200 6220 6280 6240 6320 6310 6320 6350
200: 6300 6330 6370 6340 6390 6400 6440 6380
208: 6410 6420 6440 6480 6510 6510 6500 6520
216: 6510 6520 6590 6570 6550 6560 6600 6570
224: 6560 6600 6560 6610 6600 6610 6610 6640
232: 6630 6660 6690 6620 6680 6640 6680 6690
240: 6650 6710 6680 6640 6700 6680 6720 6720
248: 6730 6710 6680 6740 6750 6690 6690 6710
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 800 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 801 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
410 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 :
420 : -50 : -60 : -60 : -60 : -60 : -60 : -60 : -60 : -60 : -60 :
430 : -60 : -60 : -60 : -60 : -60 : -60 : -60 : -60 : -60 : -70 :
440 : -70 : -70 : -70 : -70 : -70 : -70 : -70 : -70 : -70 : -70 :
450 : -70 : -80 : -80 : -80 : -80 : -80 : -80 : -80 : -80 : -80 :
460 : -80 : -90 : -90 : -90 : -90 : -90 : -90 : -90 : -90 : -90 :
470 : -100 : -100 : -100 : -100 : -100 : -100 : -100 : -100 : -110 : -110 :
480 : -110 : -110 : -110 : -110 : -110 : -110 : -120 : -120 : -120 : -120 :
490 : -120 : -120 : -120 : -120 : -120 : -130 : -130 : -130 : -130 : -130 :
500 : -130 : -130 : -130 : -130 : -130 : -130 : -130 : -130 : -130 : -130 :
510 : -130 : -130 :
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 802 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
400 : -20415 : -934 : 20228 : 3259 : -19728 : -5517 : 18972 : 7673 : -17960 : -9692 :
410 : 16736 : 11549 : -15280 : -13244 : 13642 : 14682 : -11874 : -15922 : 9943 : 16920 :
420 : -7902 : -17658 : 5781 : 18126 : -3625 : -18355 : 1497 : 18339 : 651 : -18027 :
430 : -2696 : 17490 : 4668 : -16746 : -6525 : 15737 : 8179 : -14542 : -9737 : 13213 :
440 : 11088 : -11699 : -12268 : 10102 : 13200 : -8420 : -13899 : 6709 : 14408 : -4913 :
450 : -14663 : 3160 : 14688 : -1405 : -14535 : -283 : 14167 : 1873 : -13645 : -3370 :
460 : 12910 : 4741 : -12080 : -5972 : 11082 : 7072 : -9998 : -7988 : 8821 : 8760 :
470 : -7590 : -9362 : 6347 : 9832 : -5075 : -10106 : 3812 : 10236 : -2575 : -10223 :
480 : 1389 : 10093 : -257 : -9829 : -839 : 9441 : 1838 : -8989 : -2757 : 8468 :
490 : 3602 : -7870 : -4350 : 7209 : 5014 : -6512 : -5574 : 5787 : 6089 : -5053 :
500 : -6503 : 4273 : 6859 : -3520 : -7139 : 2734 : 7317 : -1971 : -7473 : 1186 :
510 : 7593 : -403 :
scaled by (31712)/(2^30) - imaginary part:
0 : 1 : -225 : -162 : -162 : 98 : 98 : -98 : -98 : 66 : -66 :
10 : 66 : 66 : -66 : -66 : 98 : -34 : 69 : -66 : -133 : 0 :
20 : 171 : 28 : -219 : -117 : 346 : 343 : -527 : -756 : 480 : 1551 :
30 : -3 : -2394 : -1294 : 2982 : 3520 : -2410 : -6290 : -139 : 8239 : 4521 :
40 : -7924 : -9355 : 4929 : 13031 : 34 : -14554 : -5797 : 13728 : 11285 : -10875 :
50 : -15776 : 6471 : 18803 : -1071 : -20218 : -4763 : 19948 : 10548 : -18049 : -15830 :
60 : 14698 : 20314 : -10179 : -23675 : 4754 : 25758 : 1227 : -26352 : -7412 : 25465 :
70 : 13419 : -23179 : -18968 : 19582 : 23716 : -14907 : -27424 : 9390 : 29930 : -3345 :
80 : -31132 : -2947 : 30963 : 9193 : -29504 : -15063 : 26852 : 20355 : -23141 : -24893 :
90 : 18622 : 28419 : -13435 : -30957 : 7854 : 32410 : -2121 : -32767 : -3606 : 32134 :
100 : 9104 : -30496 : -14230 : 28057 : 18844 : -24829 : -22810 : 21032 : 26085 : -16755 :
110 : -28626 : 12173 : 30378 : -7364 : -31364 : 2540 : 31568 : 2276 : -31059 : -6894 :
120 : 29835 : 11279 : -27981 : -15280 : 25599 : 18895 : -22689 : -22047 : 19407 : 24657 :
130 : -15807 : -26740 : 11950 : 28235 : -7953 : -29164 : 3876 : 29520 : 174 : -29358 :
140 : -4146 : 28610 : 8007 : -27325 : -11651 : 25653 : 15019 : -23506 : -18037 : 21023 :
150 : 20711 : -18183 : -22994 : 15105 : 24848 : -11794 : -26232 : 8344 : 27166 : -4773 :
160 : -27701 : 1195 : 27694 : 2334 : -27271 : -5803 : 26429 : 9158 : -25144 : -12252 :
170 : 23503 : 15181 : -21471 : -17833 : 19159 : 20161 : -16558 : -22155 : 13763 : 23773 :
180 : -10729 : -25049 : 7590 : 25901 : -4385 : -26295 : 1090 : 26340 : 2136 : -26003 :
190 : -5329 : 25255 : 8414 : -24139 : -11336 : 22724 : 14052 : -20911 : -16574 : 18816 :
200 : 18803 : -16488 : -20768 : 13934 : 22400 : -11161 : -23719 : 8287 : 24622 : -5301 :
210 : -25223 : 2229 : 25421 : 845 : -25249 : -3882 : 24705 : 6837 : -23840 : -9657 :
220 : 22632 : 12363 : -21105 : -14853 : 19293 : 17133 : -17181 : -19146 : 14904 : 20883 :
230 : -12370 : -22317 : 9686 : 23430 : -6887 : -24177 : 3981 : 24638 : -1043 : -24715 :
240 : -1866 : 24435 : 4770 : -23815 : -7593 : 22886 : 10261 : -21630 : -12825 : 20091 :
250 : 15190 : -18227 : -17334 : 16189 : 19191 : -13874 : -20771 : 11400 : 22104 : -8773 :
260 : -23093 : 6054 : 23761 : -3240 : -24101 : 400 : 24117 : 2429 : -23789 : -5243 :
270 : 23144 : 7943 : -22123 : -10509 : 20870 : 12955 : -19302 : -15194 : 17502 : 17216 :
280 : -15454 : -18997 : 13203 : 20504 : -10754 : -21745 : 8204 : 22648 : -5530 : -23220 :
290 : 2804 : 23513 : -60 : -23459 : -2677 : 23121 : 5386 : -22425 : -8004 : 21446 :
300 : 10481 : -20148 : -12821 : 18641 : 14936 : -16844 : -16860 : 14831 : 18561 : -12634 :
310 : -19973 : 10265 : 21128 : -7778 : -21977 : 5205 : 22540 : -2553 : -22762 : -69 :
320 : 22714 : 2712 : -22320 : -5288 : 21662 : 7810 : -20701 : -10195 : 19439 : 12456 :
330 : -17989 : -14491 : 16237 : 16364 : -14306 : -17951 : 12214 : 19318 : -9896 : -20441 :
340 : 7520 : 21258 : -5018 : -21792 : 2496 : 22024 : 60 : -21970 : -2610 : 21649 :
350 : 5113 : -20969 : -7536 : 20046 : 9819 : -18863 : -11979 : 17420 : 13992 : -15776 :
360 : -15820 : 13918 : 17375 : -11896 : -18704 : 9686 : 19782 : -7399 : -20581 : 4954 :
370 : 21121 : -2521 : -21344 : 41 : 21299 : 2413 : -20978 : -4817 : 20368 : 7180 :
380 : -19474 : -9374 : 18323 : 11502 : -16943 : -13410 : 15369 : 15146 : -13553 : -16656 :
390 : 11597 : 17963 : -9505 : -18981 : 7272 : 19719 : -4970 : -20205 : 2601 : 20406 :
400 : -241 : -20352 : -2114 : 19986 : 4401 : -19375 : -6627 : 18517 : 8694 : -17394 :
410 : -10637 : 16046 : 12379 : -14472 : -13985 : 12786 : 15327 : -10891 : -16456 : 8894 :
420 : 17327 : -6821 : -17941 : 4719 : 18304 : -2556 : -18396 : 410 : 18199 : 1650 :
430 : -17776 : -3688 : 17102 : 5609 : -16249 : -7368 : 15181 : 9015 : -13915 : -10459 :
440 : 12475 : 11686 : -10939 : -12736 : 9288 : 13559 : -7552 : -14163 : 5797 : 14561 :
450 : -4022 : -14723 : 2280 : 14653 : -562 : -14395 : -1071 : 13944 : 2636 : -13298 :
460 : -4057 : 12513 : 5383 : -11575 : -6560 : 10538 : 7549 : -9425 : -8420 : 8214 :
470 : 9098 : -6983 : -9616 : 5711 : 9998 : -4439 : -10179 : 3183 : 10233 : -1974 :
480 : -10172 : 795 : 9956 : 314 : -9635 : -1345 : 9272 : 2305 : -8741 : -3189 :
490 : 8194 : 3971 : -7549 : -4696 : 6878 : 5323 : -6166 : -5844 : 5421 : 6312 :
500 : -4671 : -6684 : 3901 : 6999 : -3138 : -7244 : 2350 : 7409 : -1570 : -7520 :
510 : 795 : 7584 :
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 803 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
0 : -1030 : -1420 : -1420 : -1410 : -1410 : -1400 : -1410 : -1410 : -1420 : -1400 :
10 : -1390 : -1330 : -1410 : -1410 : -1420 : -1410 : -1410 : -1400 : -1400 : -1400 :
20 : -1400 : -1390 : -1380 : -1390 : -1380 : -1370 : -1350 : -1340 : -1330 : -1320 :
30 : -1310 : -1300 : -1290 : -1280 : -1270 : -1250 : -1250 : -1250 : -1240 : -1240 :
40 : -1240 : -1240 : -1220 : -1220 : -1210 : -1220 : -1210 : -1210 : -1210 : -1200 :
50 : -1210 : -1200 : -1200 : -1200 : -1200 : -1200 : -1200 : -1200 : -1200 : -1190 :
60 : -1190 : -1190 : -1190 : -1190 : -1180 : -1190 : -1190 : -1190 : -1190 : -1180 :
70 : -1190 : -1180 : -1190 : -1190 : -1190 : -1190 : -1180 : -1180 : -1190 : -1180 :
80 : -1170 : -1190 : -1180 : -1170 : -1180 : -1180 : -1180 : -1180 : -1180 : -1180 :
90 : -1170 : -1170 : -1170 : -1170 : -1180 : -1170 : -1180 : -1170 : -1170 : -1180 :
100 : -1170 : -1170 : -1180 : -1170 : -1160 : -1170 : -1170 : -1170 : -1170 : -1180 :
110 : -1180 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 :
120 : -1180 : -1170 : -1160 : -1170 : -1180 : -1170 : -1160 : -1170 : -1180 : -1160 :
130 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1160 :
140 : -1170 : -1170 : -1170 : -1160 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 :
150 : -1170 : -1160 : -1170 : -1170 : -1160 : -1160 : -1160 : -1170 : -1160 : -1160 :
160 : -1160 : -1170 : -1170 : -1170 : -1160 : -1160 : -1170 : -1170 : -1170 : -1170 :
170 : -1160 : -1160 : -1170 : -1170 : -1160 : -1170 : -1160 : -1170 : -1160 : -1150 :
180 : -1160 : -1160 : -1160 : -1170 : -1160 : -1170 : -1160 : -1170 : -1170 : -1160 :
190 : -1160 : -1160 : -1160 : -1160 : -1160 : -1170 : -1160 : -1170 : -1160 : -1160 :
200 : -1170 : -1170 : -1160 : -1140 : -1170 : -1160 : -1160 : -1160 : -1160 : -1160 :
210 : -1160 : -1170 : -1160 : -1160 : -1160 : -1160 : -1170 : -1160 : -1160 : -1170 :
220 : -1160 : -1160 : -1160 : -1160 : -1160 : -1160 : -1160 : -1130 : -1160 : -1160 :
230 : -1160 : -1160 : -1160 : -1160 : -1160 : -1160 : -1160 : -1160 : -1160 : -1160 :
240 : -1160 : -1160 : -1160 : -1170 : -1170 : -1160 : -1160 : -1160 : -1160 : -1160 :
250 : -1160 : -1120 : -1160 : -1160 : -1170 : -1160 : -1160 : -1160 : -1160 : -1160 :
260 : -1150 : -1150 : -1160 : -1160 : -1150 : -1160 : -1160 : -1160 : -1150 : -1160 :
270 : -1150 : -1160 : -1160 : -1160 : -1160 : -1120 : -1170 : -1160 : -1160 : -1150 :
280 : -1160 : -1150 : -1160 : -1160 : -1160 : -1170 : -1160 : -1160 : -1160 : -1160 :
290 : -1160 : -1160 : -1160 : -1150 : -1160 : -1150 : -1160 : -1160 : -1160 : -1110 :
300 : -1150 : -1160 : -1150 : -1160 : -1160 : -1160 : -1160 : -1150 : -1160 : -1160 :
310 : -1160 : -1150 : -1160 : -1150 : -1160 : -1150 : -1150 : -1150 : -1160 : -1150 :
320 : -1150 : -1160 : -1160 : -1110 : -1150 : -1150 : -1150 : -1150 : -1150 : -1160 :
330 : -1160 : -1160 : -1150 : -1150 : -1160 : -1160 : -1160 : -1160 : -1150 : -1150 :
340 : -1150 : -1160 : -1150 : -1150 : -1160 : -1150 : -1150 : -1120 : -1150 : -1150 :
350 : -1160 : -1160 : -1160 : -1140 : -1160 : -1150 : -1150 : -1140 : -1150 : -1150 :
360 : -1150 : -1150 : -1160 : -1160 : -1150 : -1150 : -1150 : -1150 : -1160 : -1160 :
370 : -1160 : -1130 : -1160 : -1160 : -1150 : -1150 : -1150 : -1150 : -1150 : -1150 :
380 : -1150 : -1150 : -1160 : -1150 : -1150 : -1160 : -1150 : -1150 : -1150 : -1160 :
390 : -1150 : -1150 : -1150 : -1150 : -1150 : -1130 : -1150 : -1150 : -1150 : -1150 :
400 : -1150 : -1160 : -1150 : -1150 : -1150 : -1150 : -1150 : -1150 : -1150 : -1150 :
410 : -1150 : -1140 : -1150 : -1150 : -1150 : -1150 : -1150 : -1160 : -1160 : -1130 :
420 : -1160 : -1150 : -1150 : -1160 : -1160 : -1160 : -1150 : -1150 : -1160 : -1160 :
430 : -1150 : -1150 : -1150 : -1150 : -1150 : -1160 : -1160 : -1160 : -1150 : -1160 :
440 : -1160 : -1150 : -1150 : -1130 : -1160 : -1160 : -1160 : -1160 : -1150 : -1170 :
450 : -1160 : -1160 : -1160 : -1160 : -1160 : -1160 : -1170 : -1170 : -1170 : -1170 :
460 : -1170 : -1160 : -1170 : -1160 : -1170 : -1170 : -1170 : -1140 : -1180 : -1170 :
470 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1170 : -1180 : -1170 : -1180 :
480 : -1170 : -1170 : -1170 : -1180 : -1170 : -1180 : -1180 : -1180 : -1180 : -1190 :
490 : -1180 : -1170 : -1190 : -1180 : -1180 : -1180 : -1190 : -1180 : -1180 : -1180 :
500 : -1180 : -1180 : -1180 : -1190 : -1180 : -1190 : -1180 : -1180 : -1190 : -1180 :
510 : -1180 : -1190 :
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 804 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
130 : 55 : 55 : 54 : 55 : 55 : 55 : 55 : 55 : 55 : 55 :
140 : 54 : 54 : 54 : 54 : 55 : 54 : 54 : 54 : 54 : 54 :
150 : 54 : 54 : 54 : 54 : 54 : 54 : 54 : 54 : 54 : 54 :
160 : 54 : 54 : 54 : 54 : 54 : 54 : 53 : 53 : 53 : 53 :
170 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 :
180 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 :
190 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 53 :
200 : 53 : 53 : 53 : 53 : 53 : 53 : 53 : 52 : 52 : 52 :
210 : 52 : 52 : 52 : 52 : 52 : 52 : 52 : 52 : 52 : 52 :
220 : 52 : 52 : 52 : 52 : 52 : 52 : 52 : 52 : 52 : 52 :
230 : 52 : 52 : 52 : 51 : 51 : 51 : 51 : 51 : 51 : 51 :
240 : 51 : 51 : 51 : 51 : 51 : 51 : 51 : 51 : 51 : 51 :
250 : 51 : 51 : 51 : 51 : 51 : 51 : 51 : 51 : 51 : 51 :
260 : 51 : 51 : 51 : 51 : 50 : 50 : 50 : 50 : 50 : 50 :
270 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 :
280 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 :
290 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 : 50 :
300 : 50 : 50 : 50 : 49 : 49 : 50 : 49 : 50 : 50 : 49 :
310 : 49 : 49 : 49 : 49 : 49 : 49 : 49 : 49 : 49 : 49 :
320 : 49 : 49 : 49 : 49 : 49 : 49 : 49 : 49 : 49 : 49 :
330 : 49 : 49 : 49 : 49 : 49 : 49 : 49 : 49 : 48 : 48 :
340 : 49 : 48 : 48 : 48 : 49 : 49 : 49 : 48 : 48 : 48 :
350 : 48 : 48 : 49 : 48 : 48 : 48 : 48 : 48 : 48 : 48 :
360 : 48 : 48 : 48 : 48 : 48 : 48 : 48 : 47 : 47 : 48 :
370 : 48 : 48 : 48 : 48 : 48 : 47 : 47 : 47 : 48 : 48 :
380 : 48 : 48 : 48 : 48 : 47 : 47 : 47 : 48 : 47 : 48 :
390 : 47 : 47 : 47 : 47 : 47 : 47 : 47 : 47 : 47 : 47 :
400 : 47 : 47 : 46 : 47 : 47 : 47 : 47 : 47 : 47 : 47 :
410 : 47 : 46 : 47 : 47 : 47 : 47 : 47 : 47 : 46 : 47 :
420 : 46 : 47 : 46 : 46 : 46 : 46 : 46 : 46 : 46 : 46 :
430 : 46 : 46 : 46 : 46 : 46 : 46 : 46 : 46 : 46 : 46 :
440 : 46 : 46 : 46 : 46 : 46 : 46 : 46 : 46 : 46 : 46 :
450 : 46 : 46 : 45 : 45 : 46 : 45 : 45 : 46 : 46 : 46 :
460 : 46 : 46 : 45 : 45 : 46 : 46 : 46 : 46 : 45 : 46 :
470 : 46 : 45 : 46 : 45 : 45 : 46 : 46 : 45 : 46 : 45 :
480 : 45 : 45 : 46 : 46 : 46 : 45 : 45 : 45 : 45 : 45 :
490 : 45 : 44 : 45 : 45 : 45 : 44 : 44 : 41 : 41 : 39 :
500 : 40 : 38 : 37 : 37 : 36 : 32 : 30 : 29 : 27 : 20 :
510 : 16 : 0 :
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 805 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT
Examples of SELT and DELT Reports
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 806 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
Introduction
Chapter 43
POTS Line Testing- MLT, Ringer and
Tone Detection Tests
In This Chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
MLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Off-Hook Tone Generator Diagnostic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Ring Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Tone Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Introduction
Occam Networks provides the ability to test POTS lines with a Metallic Loop Test
(MLT) an Off-Hook (Howler tone) tone generator, a ringing test, and a tone
detection mode. These diagnostic functions are described in this chapter.
To help diagnose voice, POTS, and line problems the following procedures are
recommended in the order listed below.
1 First run MLT with the line connected - this can be done remotely and can help
isolate any obvious line or POTS problems without needing to go to customer
site. MLT is described on page 808.
2 Second, run the off hook (Howler) tone generator diagnostic. This will test the
BLC’s Digital Signal Processor (DSP) and the POTS line. The off hook tone
generator diagnostic is described on page 821.
3 Third, disconnect the line and run MLT again. This will isolate problems with the
POTS circuitry.
4 Fourth, run the ring test. This will test the DSP, POTS circuit, POTS line, and
phone. The ringer test is described on page 822.
5 Finally, run the tone detection test. This will indicate if tones are going to the
DSP without distortion. The ringer test is described on page 823.
While a voice port is placed into test mode no calls can go to or from that port.
The state/status of the port can be displayed using the show voice port {port-
number} command.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 807 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
MLT
MLT allows remote diagnosis of POTS lines by having the POTS SLIC (Subscriber Line
Interface Circuit) obtain electrical measurements through the tip and ring leads.
These measurements include voltage, current, resistance and capacitance. Further
analysis of the basic measurements is also implemented based on the GR-909
requirements. These tests are hazardous potential, foreign EMF, resistive fault,
receiver offhook and ringer test. Fuse test is also provided along with loop detection
and loop length estimation.
BLC 6151-01
BLC 6152
BLC 6244
BLC 6246
BLC 6252-03
SNMP Support
The BLC features SNMP support for Metallic Loop Testing for BLC POTS interfaces.
The MIB files are available on your documentation CD. Alternatively, you may
request a copy of the MIB from your Occam Networks’ customer service
representative and they will post the files to your FTP account on the Occam
Networks’ support FTP server.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 808 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
If the interface is offhook, only Alarm, Hook State and Transversal Current are
reported. The following example shows sample output for this command when the
interface is in offhook state:
occam# show voice tip-ring-status 1
Voice Port 1:
Alarm: None
Hook State: Offhook (must be onhook to get complete status)
Transversal Current: 27.0 mA
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 809 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
Note: MLT is performed through controlling the SLIC (Subscriber Line Interface
Circuit) chipset in the BLC. Multiple values being grossly out of expected range
(especially Vdd and GNDK alarm) may be indicative of a damaged SLIC, in which
case the results cannot be trusted. No results being returned may also be indicative
of internal hardware issues.
Table 43-1: “show voice tip-ring-status” Command Field Descriptions
Field Description
Alarm A GNDK (Ground Key) alarm indicates the presence of
a significant unbalanced current between Tip and Ring
due to external disturbance. Shorting to ground,
foreign voltage and damaged SLIC are possible causes.
When detected, the port is shut down (i.e., the battery
is removed). Then periodically the port is re-enabled to
check if the condition is cleared.
An OTEMP alarm is caused by the BLC's hardware chip
experiencing thermal overload.
Hook State Onhook - Line is onhook
Offhook - Line is offhook
Transversal Current Transversal current is defined to be:
(Tip current + Ring current) / 2.
Normal value during onhook is:
0 mA +/- 2 mA (due to accuracy limitation)
Normal value during offhook is:
26 mA +/- 2 mA (loop current)
Longitudinal Current Longitudinal current is defined to be
(Tip current - Ring current) / 2.
Normal value during onhook and offhook is:
0 mA +/- 2 mA.
A non-zero value indicates current leakage to the
ground.
This parameter is not available in offhook state.
Tip Voltage This is the tip DC voltage relative to ground. When the
interface is enabled the typical onhook voltage is:
-7 V +/-2 V.
This parameter is not available in offhook state.
Ring Voltage This parameter is the ring DC voltage relative to
ground. When the interface is enabled the typical
onhook voltage is:
-44 V +/-2 V.
This parameter is not available in offhook state.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 810 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
Field Description
Tip-Ring Voltage This parameter is the tip DC voltage relative to ring.
When the interface is enabled the typical onhook
voltage is: +36 V +/- 2V
This parameter is not available in offhook state.
Vdd This parameter is the internal voltage with a typical
value of: 26 V +/- 2 V.
This parameter is intrusive during offhook but will be
available during onhook.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 811 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
DC Currents:
Itransversal: -0.2 mA
Ilongitudinal: 0.4 mA
Itip: 0.2 mA
Iring: -0.6 mA
Capacitance:
CEQtr: 1014 nF
CEQtg: 30 nF
CEQrg: 34 nF
Resistance:
Rtr: >1000 kOhm
Rtg: >1000 kOhm
Rrg: >1000 kOhm
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 812 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
Fuse Test:
Tip Fuse: Passed
Ring Fuse: Passed
Errors:
None
Re-enabling voice port....
If alarm is detected the full Metallic Loop Test is not performed. Only high
impedance mode voltages will be available. This test limitation is due to the
interface being in protected mode. Below is a sample output of this condition:
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 813 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
DC Currents:
Itransversal: n/a
Ilongitudinal: n/a
Itip: n/a
Iring: n/a
Capacitance:
CEQtr: n/a
CEQtg: n/a
CEQrg: n/a
Resistance:
Rtr: n/a
Rtg: n/a
Rrg: n/a
Fuse Test:
Tip Fuse: Aborted
Ring Fuse: Aborted
Errors:
Alarm detected
Re-enabling voice port....
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 814 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
Field Description
Alarm A GNDK (Ground Key) alarm indicates the presence of a
significant unbalanced current between Tip and Ring due to
external disturbance. Shorting to ground, foreign voltage and
damaged SLIC are possible causes. When detected, the port is
shutdown. i.e. battery is removed. Then periodically the port
is re-enabled to check if the condition is cleared.
An OTEMP alarm is caused by the BLC's hardware chip expe-
riencing thermal overload.
Hook State Onhook - Line is onhook
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 815 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
Field Description
DC Currents Currents are measured in active mode.
Transversal current is defined to be (Tip current + Ring
current) / 2. Normal value during onhook is:
0 mA +/- 2 mA (due to accuracy limitation).
Normal value during offhook is:
26 mA +/- 2 mA (loop current).
Longitudinal current is defined to be:
(Tip current - Ring current) / 2.
Normal value during onhook and offhook is:
0 mA +/- 2 mA.
A non-zero value indicates current leakage to the ground.
Both tip and ring current are derived from transversal and
longitudinal currents.
Capacitance Capacitance measurements are based on a three terminal
circuit but with some limitations. In the presence of capaci-
tance network, as shown in Figure 43-1, the individual
capacitance is not resolved. The equivalent capacitances
CEQtr, CEQtg and CEQrg are reported. They represent the
following:
CEQtr = Ctr + Ctg/4 + Crg/4[2 terminal perspective]
Ctg Crg
Gnd
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 816 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
Field Description
Resistance DC resistance measurements are based on a three terminal
circuit model as shown in Figure 43-2. Rtr, Rtg and Rrg are
provided. Resistance measurements are not available if the
fuse test fails or an alarm is present.
Figure 43-2: DC Resistance
Tip Rtr Ring
Rtg Rrg
Gnd
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 817 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
DC Currents:
Itransversal: -0.2 mA
Ilongitudinal: 0.4 mA
Itip: 0.2 mA
Iring: -0.6 mA
Capacitance:
CEQtr: 1014 nF
CEQtg: 30 nF
CEQrg: 34 nF
Resistance:
Rtr: >1000 kOhm
Rtg: >1000 kOhm
Rrg: >1000 kOhm
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 818 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
Fuse Test:
Tip Fuse: Passed
Ring Fuse: Passed
Errors:
None
Detecting a Loop
The command test voice loop-detect {port-number} [detection threshold] reports
loop detection. Loop detection is based on tip-ring capacitance measurement. You
may specify the detection threshold. If not supplied, a loop detection threshold of
10 nF is be used. This test is not available if the fuse test fails or an alarm is present.
This test is intrusive and is available in shutdown state only.
Sample output is shown below. In this example port number one is tested and the
threshold parameter is 12 nF.
occam# test voice loop_detect 1 12
Detection threshold: 12 nF
Loop capacitance: 226 nF
Loop detected: yes
Errors:
None
For DSL platforms, when the DSL ports are bridged to the POTS lines, the DSL
circuitry has capacitance that contribute to the measurement. Typically the
additional capacitance is around 27 nF. Therefore it is necessary to add 27 nF to the
desired threshold.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 819 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
MLT
Errors:
None
For DSL platforms, when the DSL ports are bridged to the POTS lines, the DSL
circuitry has capacitance that contribute to the measurement. Typically the
additional capacitance is around 27 nF. The reported loop length assumes the
presence of the DSL circuitry and compensates for it. The uncompensated
measurement is also reported.
occam# test voice loop-length 1 79
This voice port is not shutdown. Continuing will temporarily shutdown
the voice port and will interrupt subscriber service. Do you wish to
continue? [y/N] y
Shutting down voice port....
Running test...
Capacitance factor: 79 nF/mile
Loop capacitance: 32 nF
Loop length: 2170 ft
Uncompensated loop capacitance:60 nF (no DSL circuit correction)
Uncompensated loop length: 4014 ft (no DSL circuit correction)
Errors:
None
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 820 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
Off-Hook Tone Generator Diagnostic
To send an off-hook tone to a specified POTS port, enter the following command
from Privileged mode:
Occam# test voice tone {pots-port-number}
To stop sending the off-hook tone to the POTS port, enter the following command
from Privileged mode:
Occam# no test voice tone {pots-port-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 821 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
Ring Test
Ring Test
The ring test allows you to test the operation of the phone as well as the DSP and
SLIC. When the ring test is initiated, the DSP sends a ring signal to the phone. The
phone should ring and if picked up a busy tone will be played. The ring test will test
the pathway from the DSP to the SLIC to the phone as well as the operation of the
phone.
RING SIGNAL
TO SLIC/
HOST DSP
NETWORK POTS PHYSICAL
POTS LINE
PHONE AT
BLC WITH HD POTS PORTS CUSTOMER
PREMISES
To enable the ring test on a specified POTS port, enter the following command from
Privileged mode. When the command is entered the phone should immediately
start ringing. When the phone is picked up the ring is turned off and a busy tone is
generated. The busy tone or ringing (if phone was not picked up) will continue until
the test is disabled:
Occam# test voice ring {pots-port-number}
To disable the ring test on a specified POTS port, enter the following command
from Privileged mode:
Occam# no test voice ring {pots-port-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 822 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
Tone Detection
Tone Detection
The tone detection diagnostic helps diagnose DSP/SLIC issues. When the tone
detection diagnostic is started it enables the DSP DTMF detector. A
customer/technician can then pick up the phone and enter digits, sending DTMF
tones to the DSP. The DSP will stay in tone detection mode until the test is disabled.
When the command show voice digits command is entered the DSP displays the
last eleven detected digits.
The tone levels can also be displayed by entering the show voice power command
at the same time the DTMF tones are sent to the DSP.
This type of diagnostic helps test the pathway from the phone to the SLIC to the
DSP. This diagnostic may also be useful in diagnosing problems with dialing and
DTMF detection as well.
B. DTMF TONES
SENT FROM
PHONE TO DSP
TO SLIC/
HOST DSP
NETWORK POTS PHYSICAL
POTS LINE
PHONE AT
BLC WITH HD POTS PORTS
CUSTOMER
PREMISES
A. DSP DTMF
DETECTOR ENABLED
To enable the tone detection diagnostic on a specified POTS port, enter the
following command from Privileged mode. When the tone detection diagnostic is
enabled the DSP will generate a dial tone until the first digit is entered. Any number
of digits can be entered. The last eleven digits can be displayed using the show
voice digits {pots-port-number} command:
Occam# test voice tone-detect {pots-port-number}
To disable the tone detection diagnostic on a specified POTS port, enter the
following command from Privileged mode:
Occam# no test voice tone-detect {pots-port-number}
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 823 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests
Tone Detection
Once the show voice digits command displays the digits detected, the DSP will
clear its digit buffer and reset the buffer for the next detected digits.
An example of output from this command is shown below, showing output for
POTS port 5:
Occam# show voice digits 5
Detected digits
digit 1 = 5
digit 2 = 2
digit 3 = 6
digit 4 = 5
digit 5 = 6
digit 6 = 4
digit 7 = 6
digit 8 = *
digit 9 = #
digit 10 = n/a
digit 11 = n/a
Use the show voice power [voice-port-number] command to display the tone levels
for all or a specified voice port. This command must be issued at the same time the
DTMF tones are sent from the phone to the DSP. An example of output from this
command is shown below, showing output for POTS port 5:
Occam# show voice power 5
Voice Port: 5
Transmit Power: -70.7 dBm0
Receive Power: <-71 dBm0
Occam#
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 824 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix A: Safety Warnings
Introduction
Appendix A
Safety Warnings
In this Appendix:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
Restricted Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
Protective Earthing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
Safety Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Equipment Interconnection Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
Preventing Electrostatic Discharge Damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
FCC Part 15 Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
FCC Part 68 Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
IC CS-03 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
Laser Transmitter Operation and Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . 831
Introduction
The following section outlines the mandatory regulatory compliance information
and safety warnings governing the installation and operation of the BLC.
Adherence to these instructions is necessary to ensure that regulatory compliance
requirements are met.
Before connecting this equipment, users should read and understand all
instructions. Follow all instructions and warnings marked on the product.
Restricted Access
The BLC contains potentially hazardous voltages and is intended for installation in
a Restricted Access Location.
A Restricted Access Location is a location where access can only be gained by USERS
or by SERVICE PERSONNEL who have been instructed about any precautions that
must be taken and the reason for the restrictions applied to the location. Access is
gained through the use of an Access Code, Special Tool or Lock and Key, or other
means of security, and is controlled by the authority responsible for the location.
The BLC contains no user-serviceable parts. Only trained and qualified personnel
should be allowed to service this equipment.
Protective Earthing
Protection of the Telecommunications Network during a Lightning event or
Overvoltage event from power line crosses relies on the protective earthing of the
BLC. The protective earthing terminal located on the rear of the chassis MUST be
permanently connected to a reliable ground.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 825 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix A: Safety Warnings
Safety Considerations
Safety Considerations
This section contains safety warnings that you should be aware of before installing
the BLC platform.
Safety Warnings
Failure to adhere to the safety warnings outlined in this publication may cause
bodily injury. A warning symbol precedes each warning statement.
Warning: To avoid electric shock, do not connect safety extra-low voltage (SELV)
circuits to telephone-network voltage (TNV) circuits. LAN interfaces contain SELV
circuits, and WAN interfaces contain TNV circuits. Both LAN and WAN interfaces
may use RJ-45 connectors. Use caution when connecting cables.
Warning: Use caution when working near WAN interfaces. Hazardous network
voltages may be present in WAN interfaces regardless of whether power to the
BLC is OFF or ON. When detaching cables, always attempt to detach the end away
from the BLC first.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 826 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix A: Safety Warnings
Equipment Interconnection Points
Caution: For both equipment protection and user safety, periodically check the
! resistance value of the antistatic strap. The measurement should range from 1 to
10 Megaohm (Mohm).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 827 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix A: Safety Warnings
FCC Part 15 Statement
The following information is for FCC compliance of Class B devices: The equipment
described in this manual generates and may radiate radio-frequency energy. If it is
not installed in accordance with Occam's installation instructions, it may cause
interference with radio and television reception. This equipment has been tested
and found to comply with the limits for a Class B digital device in accordance with
the specifications in part 15 of the FCC rules. These specifications are designed to
provide reasonable protection against such interference in a residential installation.
However, there is no guarantee that interference will not occur in a particular
installation.
Modifying the equipment without Occam’s written authorization may result in the
equipment no longer complying with FCC requirements for Class A or Class B digital
devices. In that event, your right to use the equipment may be limited by FCC
regulations, and you may be required to correct any interference to radio or
television communication at your own expense.
You can determine whether your equipment is causing interference by turning it
off. If the interference stops, it was probably caused by the Occam equipment or
one of its peripheral devices. If the equipment causes interference to radio or
television reception, try to correct the interference by using one or more of the
following measures:
Move the equipment to one side or the other of the television or radio.
Plug the equipment into an outlet that is on a different circuit from the televi-
sion or radio. (That is, make certain the equipment and the television or radio
are on circuits controlled by different circuit breakers or fuses.)
Modifications to this product not authorized by Occam Networks, Inc. could void
the FCC approval and negate your authority to operate the product.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 828 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix A: Safety Warnings
FCC Part 68 Compliance
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 829 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix A: Safety Warnings
IC CS-03 Warnings
IC CS-03 Warnings
The following information applies to models used in Canada:
Caution: Users should not attempt to make connections themselves, but should
! contact the appropriate electric inspection authority, or electrician, as appropriate.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 830 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix A: Safety Warnings
Laser Transmitter Operation and Safety Precautions
Transmitter Operation
The laser modules are used as an optical source in data transmission applications,
and operate at a selected bit rate with a digital signal format. These modules should
be operated in accordance to the operating conditions outlined in their pertinent
data sheets to comply with the Class 1 laser safety requirements. The compliance is
applicable with or without the optical connector (fiber) attached to the modules.
Operating the laser transmitter module outside of its absolute maximum ratings
may cause the device to fail and may be a safety hazard.
The laser transmitter does not incorporate any external adjustment features.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 831 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix A: Safety Warnings
Laser Transmitter Operation and Safety Precautions
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 832 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
Introduction
Appendix B
BLC 6012 Chassis Wiring
Arrangements
In this Appendix:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
H Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
FTTX Wiring Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Gateway Chassis Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
POTS Wiring Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Ring Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
Introduction
The BLC 6012 chassis comes prewired from the factory with three wiring
arrangements: G, R, P and F. These wiring configurations are described in this
section.
The BLC 6012-F, BLC 6012-G, BLC 6012-R, and BLC 6012-P wiring arrangements are
supported by the load network command. This command is described in Chapter 7,
Initial Configuration Steps in the section Configuring a Prewired BLC 6012 Chassis
With the “load network” Command on page 141.
The BLC 6012-H wiring arrangement is not supported by the load network
command.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 833 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
H Wiring Configuration
H Wiring Configuration
The H wiring configuration is used in a BLC 6012 chassis populated with two
BLC 6314s or BLC 6045s in the bookend positions and BLC 6312s or BLC 6314s in
the middle slots.
The H wiring kit’s part number is 535122. It consists of the following shielded
cables:
One of the 51-inch cables connects the blade in Slot 1/ XG1 to the blade in Slot
12/ XG2.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 834 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
H Wiring Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 835 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
H Wiring Configuration
One of the 51-inch cables connects the blade in Slot 1/ XG1 to the blade in
Slot 12/ XG2.
The 6-inch cables connect blades in adjacent slots, as described in the previous
section H Wiring Configuration In Full BLC 6012 Chassis on page 834.
The second 51-inch cable connects the blade in Slot N/ XG1 to the blade in Slot
N/ XG2.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 836 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
FTTX Wiring Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 837 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
FTTX Wiring Configuration
Figure B-4 shows how the shielded cable is fastened to the top of the BLC 612 with
a cable tie in such a way that it is not in the way of other cables that will be inserted
in the front of the chassis.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 838 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
FTTX Wiring Configuration
The arrangement shown in Figure B-5 can also be used with other BLCs (except the
BLC 6151) in the bookend positions. However, in this case the bookend blades do
not have 10 Gig copper ports. In this case, the Shielded CAT 5e cable is used to
connect between Port 6 of Slots 1 and 12. This arrangement uses five subtended
rings of two BLCs. This arrangement with the F-wiring with non-631x BLCs will
consume all ports in the bookends until the chassis is upgraded with BLC 6312s or
BLC 6314s.
6
5
ETHERNET
4
PORT
NUMBERS 3
2
1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
6
5 5
ETHERNET
4
PORT
NUMBERS 3 2
2 2
1 1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 839 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
FTTX Wiring Configuration
6
5
ETHERNET
4 4
PORT
NUMBERS 3
2 2 2 2
1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
Subtended Ring 3
The third subtended Ring in the chassis consists of Slots 6 and 7. These are
connected to Slot 1 using Port 3 PG1 to Slot 6 Port 2. These are connected to Slot
12 using Port 3 PG2 to Slot 7 Port 1. The connection is between Slot 6 Port 1 to Slot
7 Port 2. This is shown in Figure B-8. The first and second subtended rings are also
shown in this figure with cables the cables drawn in light grey.
6
5
ETHERNET
4
PORT 3
3
NUMBERS 3
2 2 2
1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 840 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
FTTX Wiring Configuration
6
5
ETHERNET 4
4
PORT
NUMBERS 3
2 2 2 2
1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
Subtended Ring 5
The fifth subtended Ring in the chassis consists of Slots 10 and 11. These are
connected to Slot 1 using Port 1 PG1 to Slot 10 Port 2. These are connected to Slot
12 using Port 5 PG2 to Slot 11 Port 1. The connection is between Slot 10 Port 1 to
Slot 11 Port 2. This is shown in Figure B-10. The first, second, third and forth
subtended rings are also shown in this figure with cables the cables drawn in light
grey.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 841 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
FTTX Wiring Configuration
6
5 5
ETHERNET
4
PORT
NUMBERS 3
2 2 2
1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 842 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
FTTX Wiring Configuration
Figure B-11 shows the rear of BLC 6012 Chassis with the complete FTTx wiring
arrangement.
Figure B-11: Rear of BLC 6012 Chassis With Complete FTTx Wiring Arrangement
“load network” Commands for the BLC 6312 and BLC 6314
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 843 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
FTTX Wiring Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 844 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
Gateway Chassis Wiring Configuration
The BLC in Slot #1 (chassis master) and in Slot #12 (chassis slave) supports Virtual
Path Termination (VPT) or Virtual Path Switching (VPS) functionality. This includes
a 1GbE EPS copper Ethernet directly between Slot 1, Port 5 and Slot 12, Port 6. The
remainder of the chassis (up to ten slots) are populated with BLCs that provide
additional Voice Gateway capacity. The communication for the Voice Gateway
traffic is supported on a daisy chain through ports 5 and 6, forming a subtended
1GbE ring for this service.
The BLC 6312 can be used in the Gateway wiring arrangement but has to share the
same subtended ring within the chassis as any Trunking Gateway (BLC 6640), Packet
Transport (BLC 6440) or HD POTS (BLC 6150).
6
5
ETHERNET
4
PORT
NUMBERS 3
2
1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
The 24 inch red wire that connects Slot 1/ Port 6 to Slot 12/ Port 5 is part of the
Gigabit Backbone Ethernet network.
The 6 inch orange wire that connect Ports 5 and 6 on Slots 1 through 12 forms
a GbE "buss" connecting each slot through the chassis.
This arrangement leaves ports 1 through 4 on slots 1 and 12 as unrestricted
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 845 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
Gateway Chassis Wiring Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 846 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
POTS Wiring Arrangement
In the POTS wiring arrangement the bookend slots (1 and 12) are equipped with a
BLC 6150-01, or BLC 6212-02 to serve the VPS functionality. This wiring creates
four subtended rings at 100BaseTX (or 1000BaseTX) with either two or three BLCs
in each ring. No more than three BLC 6151s should be connected together in a
subtended ring to control the cumulative jitter that develops in the main processor
when servicing the two 100BaseTX Ethernet ports. Also, a BLC 6151 should not
share a subtended ring with any other type of BLC, especially a BLC 6235 which also
operates at 100BaseTX but which also supports large data blocks generated on its
ADSL ports which would create unacceptable jitter into the BLC 6151 POTS ports.
Therefore, each of the four subtended rings must contain only BLC 6151s or only
BLCs that support the 1000BaseTX Ethernet ports such as on BLC 6150s,
BLC 6212s, BLC 6252s, BLC 6312s or BLC 644s.
This POTS wiring arrangement can be used to serve 576 POTS ports by populating
Slots 1 and 12 with BLC 6150s or BLC 6312s and Slots 2 through 11 with BLC 6151s.
The 24 inch red wire that connects Slot 1 / Port 6 to Slot 12 / Port 6 in
Figure B-13 provides a 1x1GbE EPS connection path.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 847 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
POTS Wiring Arrangement
6
5
ETHERNET
4
PORT
NUMBERS 3
2
1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
Port 5 of Slot 1 and 12 are reserved to allow copper connection between multiple
chassis located at the same place.
Four subtended rings are formed between Slot 1 and Slot 12, as shown in
Figures B-14 through B-17.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 848 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
POTS Wiring Arrangement
6
5
ETHERNET 4
4
PORT
NUMBERS 3
2 2 2 2
1 1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 849 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
POTS Wiring Arrangement
6
5
ETHERNET
4
PORT
3
NUMBERS 3 2
2 2
1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 850 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
POTS Wiring Arrangement
6
5
ETHERNET
4
PORT
NUMBERS 3
3
2 2 2 2
1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 851 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
POTS Wiring Arrangement
Port 4 of Slot 1 and Slot 12 are free for connection to other chassis at that same
location.
Since all the ports are used on the bookend blades, the Valere Ethernet Controller
is connected to Slot 2 / Port 3 to provide the connectivity of the alarms.
6
5
ETHERNET
4 4
PORT
NUMBERS 3
2 2 2 2
1 1 1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 852 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
POTS Wiring Arrangement
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 853 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
Ring Wiring Configuration
The Ring wiring configuration is the common wiring arrangement for the BLC 6012
chassis when used in Remote Terminal applications.
The BLC in Slot #1 (chassis master) and in Slot #12 (chassis slave), supports a
1x1GbE EPS ring completed with copper Ethernet wire directly between Slot 1/Port
5 and Slot 12/Port 6.
Interior slots 2 through 11 are populated with a mixture of either BLC 6150-01s to
support voice, BLC 6212-02s or BLC 6252-03s to support voice, video and data
(DSL) services or BLC 6246s to support voice and data (DSL) services.
Communication for the interior BLCs is supported on a daisy chain through ports 5
and 6, forming a subtended ring at 1000BaseTX for voice, video and data (DSL)
services. Communication for the 6246 BLCs is supported on a daisy chain through
ports 1 and 2, forming a sub-tended ring at 100BaseTX for voice and data service.
Where the BLC 6150-01, BLC 6212-02, or BLC 6252-03 intercept the daisy chain
through ports 1 and 2, these ports are set into a special Bypass Mode to
transparently transport the 100BaseTX service through the BLC.
Note: There are special card edge connectors in Slots 2 through 11 that bridge the
connection of this path when the slot is vacant. The BLC 6246 provides a
connection between Ports 5 and 6 on the BLC itself that serves the same function
as the special card edge connector, since these ports are not used in this BLC.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 854 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
Ring Wiring Configuration
6 6 6 6 6 6 6 6 6 6 6 6
5 5 5 5 5 5 5 5 5 5 5 5
ETHERNET 4 4 4 4 4 4 4 4 4 4 4 4
PORT
3 3 3 3 3 3 3 3 3 3 3 3
NUMBERS
2 2 2 2 2 2 2 2 2 2 2 2
1 1 1 1 1 1 1 1 1 1 1 1
12 11 10 9 8 7 6 5 4 3 2 1
CHASSIS SLOT NUMBERS
The 24 inch red wire that connects Slot 1/ Port 6 to Slot 12/ Port 5 is part of the
Gigabit Backbone Ethernet network.
The connection through Ports 5 and 6 forms a GbE "buss" connecting each slot
through the chassis with the connection through Ports 1 and 2 forms a 100
Mbps Ethernet "buss" connecting each slot through the chassis.
Slot 1 / Port 2 is used to support the Enhanced Valere Ethernet Controller for
intelligent alarm generation in Occam Networks cabinets.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 855 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix B: BLC 6012 Chassis Wiring Arrangements
Ring Wiring Configuration
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 856 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix C: Decimal to Hexadecimal Conversion Table
Decimal to Hexadecimal Conversion Table
Appendix C
Decimal to Hexadecimal Conversion
Table
In this Appendix:
Decimal to Hexadecimal Conversion Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Decimal Hexadecimal
Number Number
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 A
11 B
12 C
13 D
14 E
15 F
245 F5
246 F6
247 F7
248 F8
249 F9
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 857 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix C: Decimal to Hexadecimal Conversion Table
Decimal to Hexadecimal Conversion Table
Decimal Hexadecimal
Number Number
250 FA
251 FB
252 FC
253 FD
254 FE
255 FF
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 858 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix D: Installing a Cable Guard on a BLC 6012 Chassis
Installing a Cable Guard
Appendix D
Installing a Cable Guard on a
0
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 859 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix D: Installing a Cable Guard on a BLC 6012 Chassis
Installing a Cable Guard
The BLC 6012 chassis has four pegs (one on each corner) that correspond to holes
on the cable guard. Figure D-2 shows a peg in the upper right corner of a BLC 6012
chassis.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 860 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix D: Installing a Cable Guard on a BLC 6012 Chassis
Installing a Cable Guard
Place the cable guard over the BLC 6012 so that the chassis peg line up with the
holes on the guard. Push the cable guard down on the chassis pegs until each peg
is secure in a chassis hole (Figure D-4). Make sure that the arced side of the cable
guard is facing up so the fan vents do not get covered (Figure D-5).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 861 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix D: Installing a Cable Guard on a BLC 6012 Chassis
Installing a Cable Guard
Figure D-5: Cable Guard on 6012 Chassis With Fan Filter Exposed
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 862 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 6.0
Appendix E: Replacing a Fan Filter on a BLC 6012 Chassis
Appendix E
Replacing a Fan Filter on a
BLC 6012 Chassis
This section explains how replace the fan filter on a BLC 6012 chassis. The filter is
disposable and should be replaced when it appears to be too full of debris to allow
air to pass. The filter is used only on CO installations. Service life depends on
environment but in a normal CO environment it is recommended to inspect at 6
month intervals and replace if necessary.
The BLC 6012 CO System is designed to operate without alarms or interruption of
service with the fan tray removed up to 90 seconds. The fan tray is fully hot
swappable without impact to service.
1 Using a Phillips Head screwdriver, unscrew the screws on either side of the fan
tray. Figure E -1: shows the location of the screws.
Figure E -1: Locations of Screws on Fan Tray
Part Number 785597 Rev. 1.0Proprietary Information - Occam Networks Inc. Page 863 of 434
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 6.0
Appendix E: Replacing a Fan Filter on a BLC 6012 Chassis
2 Wait for the fans to stop spinning. Pull the fan tray out of the chassis, as shown
in Figure E -2:
Figure E -2: Fan Tray Pulled Out of BLC 6012 Chassis
3 Place the fan tray upside down and pull off the fan filter, as shown in
Figure E -3:
Figure E -3: Pulling Off the Fan Tray Filter
Part Number 785597 Rev. 1.0Proprietary Information - Occam Networks Inc. Page 864 of 434
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 6.0
Appendix E: Replacing a Fan Filter on a BLC 6012 Chassis
4 Place the new fan filter in the tray. Put the front short edge of the fan filter in
first and then gently press the longer edge down until it snaps into place.
Figure E -4: Putting in New Fan Tray Filter
5 Replace the fan tray in the chassis and tighten the screws on each side.
Part Number 785597 Rev. 1.0Proprietary Information - Occam Networks Inc. Page 865 of 434
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 6.0
Appendix E: Replacing a Fan Filter on a BLC 6012 Chassis
Part Number 785597 Rev. 1.0Proprietary Information - Occam Networks Inc. Page 866 of 434
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 6.0
Appendix F: Shelf Hardware Upgrade Instructions
Pre-upgrade Checklist
Appendix F
Shelf Hardware Upgrade
0
Instructions
In this Appendix:
Pre-upgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
When using 6640-01s or 6440-01s as VPTs, both VPTs must be –01s. This section
describes how to upgrade a 6640 or 6440 to a 6640-01 or 6440-01 with minimum
disruption to your network. This procedure should take approximately 20 minutes
to complete.
Pre-upgrade Checklist
Use a console cable during this procedure.
The 6640-01 or 6440-01 replacement blades must have the same configuration
as the 6640 or 6440 they are replacing pre-loaded to start the procedure below.
Either copy both configuration files named /config/startup-config and
/config/startup-config-shelf, or contact Customer Service for assistance with
the preconfiguration of 6640-01s and 6440-01 blades.
This procedure assumes you will upgrade slots 1 and 12, configured for VPT,
Shelf Controller, and TGW Applications (TMC/EOC signaling). If any other slot is
upgraded, there is no need to configure the interconnect on the blades in slots
1 and 12 for VLAN 2, as described in steps 1 and 5. In addition, step 13 is
unnecessary.
Part Number 785597 Rev. 1.0Proprietary Information - Occam Networks Inc. Page 867 of 434
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 6.0
Appendix F: Shelf Hardware Upgrade Instructions
Upgrade Procedure
Upgrade Procedure
If the two Shelf Controllers (SC) are not configured also as TGW (TMC/EOC
applications configured on slot 1 and 12), skip steps 1, 5, and 9.
1 Pre-configure the –01 blades for both Slot 1 and Slot 12 (see pre-upgrade
checklist above).
2 The EPS Interconnect Ethernet port must be changed on the Slot 12 blade to
VLAN 2 by using the command eps access untagged vlan 2 from Ethernet Inter-
face Configuration mode.
3 Use the command show shelf from Privileged mode to find out which blade is
the active SC. Slot 1 should be the active SC. If it is not, use the command
switchover from Privileged mode to make it the active SC.
5 Configure the EPS Interconnect Ethernet port on the existing blade in Slot 1 for
VLAN 2 with the command eps access untagged vlan 2 from Ethernet Interface
Configuration mode.
7 Wait for the new BLC 6640-01 or BLC 6440-01 in Slot 12 to complete bootup.
Use the command show shelf from Privileged mode to confirm that the new
blade in Slot 12 is fully up and configured.
8 Use the command switchover on the existing blade in Slot 1 to cause the new
blade in Slot 12 to become the active SC.
9 Use the commands show shelf and show interface-group from Privileged mode
to confirm that the blade in slot 12 has become the active SC and the shelf
configuration is stable.
10 Check all IGs to verify that the IG is redundant and that all DS1s in the IG have
a valid IP address with the command show interface-group.
11 Switch the active applications on the IGs to the newly active SC in slot 12 with
the command initiate application-switchover primary-standby from GR-303
Interface Group Configuration mode, so that when the existing blade Slot 1 is
pulled (step 9) the TGW does not need to do an application switch (since it has
already been done here). For example:
slot_12 (config-interface-group-gr303)ig-1# initiate
application-switchover primary-standby
The following IGs will be affected by this operation: 1 5. Do you
want to continue? [y/N] y
slot_12 (config-interface-group-gr303)ig-1#
Part Number 785597 Rev. 1.0Proprietary Information - Occam Networks Inc. Page 868 of 434
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 6.0
Appendix F: Shelf Hardware Upgrade Instructions
Upgrade Procedure
13 Configure the EPS Interconnect Ethernet port on the new 6640-01 or 6440-01
blades in slot 12 as an “interconnect” with the command eps ring interconnect.
from Ethernet Interface Configuration mode.
14 Insert the new BLC 6640-01 or BLC 6440-01 in Slot 1. Wait until the bootup
sequence in completed.
15 Confirm the shelf is fully restored and functional with the command show shelf
from Privileged mode.
16 Confirm all IGs are restored and functional with the command show interface-
group as appropriate.
17 Confirm EPS ring is restored and functional with the command show eps from
Privileged mode. As noted above you may have to move some Ethernet fiber
ports to the new –01 blade available locations.
Part Number 785597 Rev. 1.0Proprietary Information - Occam Networks Inc. Page 869 of 434
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 6.0
Appendix F: Shelf Hardware Upgrade Instructions
Upgrade Procedure
Part Number 785597 Rev. 1.0Proprietary Information - Occam Networks Inc. Page 870 of 434
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
Open SSL Code
Appendix G
Software License Information
In this Appendix:
Open SSL Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
SSLEAY Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
Open SSH Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
Carnegie Mellon License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
GNU General Public License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
In addition to the Occam proprietary software program, which has its own distinct
license, Occam may also have provided the following additional separate and
distinct programs which each has its own licensing and copyright terms as follows:
1 Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimer.
2 Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
4 The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to
endorse or promote products derived from this software without prior written
permission. For written permission, please contact openssl-core@openssl.org.
5 Products derived from this software may not be called “OpenSSL” nor may
“OpenSSL” appear in their names without prior written permission of the
OpenSSL Project.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 871 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
SSLEAY Code
SSLEAY Code
Copyright (C) 1995-1998 Eric Young (eay@crypsoft.com) All rights reserved.
1 Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimer.
2 Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
4 If you include any Windows specific code (or a derivative thereof) from the apps
directory (application code) you must include an acknowledgment: "This
product includes software written by Tim Hudson (tjh@cryptsoft.com)."
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of
this code cannot be changed, i.e., this code cannot simply be copied and put under
another distribution license (including the GNU General Public License).
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 872 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
Open SSH Code
1 Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimer.
2 Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS'' AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD PROJECT OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 873 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
Carnegie Mellon License
permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR
THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL,
INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 874 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
GNU General Public License
Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite
330, Boston, MA 02111-1307 USA. Everyone is permitted to copy and distribute
verbatim copies of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and
change it. By contrast, the GNU General Public License is intended to guarantee
your freedom to share and change free software--to make sure the software is free
for all its users. This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to using
it. (Some other Free Software Foundation software is covered by the GNU Library
General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our
General Public Licenses are designed to make sure that you have the freedom to
distribute copies of free software (and charge for this service if you wish), that you
receive source code or can get it if you want it, that you can change the software
or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you
these rights or to ask you to surrender the rights. These restrictions translate to
certain responsibilities for you if you distribute copies of the software, or if you
modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee,
you must give the recipients all the rights that you have. You must make sure that
they, too, receive or can get the source code. And you must show them these terms
so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you
this license which gives you legal permission to copy, distribute and/or modify the
software.
Also, for each author's protection and ours, we want to make certain that everyone
understands that there is no warranty for this free software. If the software is
modified by someone else and passed on, we want its recipients to know that what
they have is not the original, so that any problems introduced by others will not
reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to
avoid the danger that redistributors of a free program will individually obtain
patent licenses, in effect making the program proprietary. To prevent this, we have
made it clear that any patent must be licensed for everyone's free use or not
licensed at all.The precise terms and conditions for copying, distribution and
modification follow.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 875 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
GNU General Public License
2 You may copy and distribute verbatim copies of the Program's source code as
you receive it, in any medium, provided that you conspicuously and appropri-
ately publish on each copy an appropriate copyright notice and disclaimer of
warranty; keep intact all the notices that refer to this License and to the absence
of any warranty; and give any other recipients of the Program a copy of this
License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may
at your option offer warranty protection in exchange for a fee.
3 You may modify your copy or copies of the Program or any portion of it, thus
forming a work based on the Program, and copy and distribute such modifica-
tions or work under the terms of Section 1 above, provided that you also meet
all of these conditions:
a You must cause the modified files to carry prominent notices stating that
you changed the files and the date of any change.
b You must cause any work that you distribute or publish, that in whole or in
part contains or is derived from the Program or any part thereof, to be
licensed as a whole at no charge to all third parties under the terms of this
License.
c If the modified program normally reads commands interactively when run,
you must cause it, when started running for such interactive use in the most
ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying that
you provide a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this License.
(Exception: if the Program itself is interactive but does not normally print
such an announcement, your work based on the Program is not required to
print an announcement.)
These requirements apply to the modified work as a whole. If identifiable
sections of that work are not derived from the Program, and can be reason-
ably considered independent and separate works in themselves, then this
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 876 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
GNU General Public License
License, and its terms, do not apply to those sections when you distribute
them as separate works. But when you distribute the same sections as part
of a whole which is a work based on the Program, the
distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to
each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your
rights to work written entirely by you; rather, the intent is to exercise the
right to control the distribution of derivative or collective works based on
the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under the
scope of this License.
4 You may copy and distribute the Program (or a work based on it, under
Section 2) in object code or executable form under the terms of Sections 1 and
2 above provided that you also do one of the following:
a Accompany it with the complete corresponding machine-readable source
code, which must be distributed under the terms of Sections 1 and 2 above
on a medium customarily used for software interchange; or,
b Accompany it with a written offer, valid for at least three years, to give any
third party, for a charge no more than your cost of physically performing
source distribution, a complete machine-readable copy of the corresponding
source code, to be distributed under the terms of Sections 1 and 2 above on
a medium customarily used for software interchange; or,
c Accompany it with the information you received as to the offer to distribute
corresponding source code. (This alternative is allowed only for noncommer-
cial distribution and only if you received the program in object code or
executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making
modifications to it. For an executable work, complete source code means all the
source code for all modules it contains, plus any associated interface definition
files, plus the scripts used to control compilation and installation of the execut-
able. However, as a special exception, the source code distributed need not
include anything that is normally distributed (in either source or binary form)
with the major components (compiler, kernel, and so on) of the operating system
on which the executable runs, unless that component itself accompanies the
executable.
If distribution of executable or object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the source code
from the same place counts as distribution of the source code, even though third
parties are not compelled to copy the source along with the object code.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 877 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
GNU General Public License
4 You may not copy, modify, sublicense, or distribute the Program except as
expressly provided under this License. Any attempt otherwise to copy, modify,
sublicense or distribute the Program is void, and will automatically terminate
your rights under this License. However, parties who have received copies, or
rights, from you under this License will not have their licenses terminated so
long as such parties remain in full compliance.
5 You are not required to accept this License, since you have not signed it.
However, nothing else grants you permission to modify or distribute the
Program or its derivative works. These actions are prohibited by law if you do
not accept this License. Therefore, by modifying or distributing the Program (or
any work based on the Program), you indicate your acceptance of this License
to do so, and all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6 Each time you redistribute the Program (or any work based on the Program), the
recipient automatically receives a license from the original licensor to copy,
distribute or modify the Program subject to these terms and conditions. You
may not impose any further restrictions on the recipients' exercise of the rights
granted herein. You are not responsible for enforcing compliance by third
parties to this License.
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 878 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
GNU General Public License
9 The Free Software Foundation may publish revised and/or new versions of the
General Public License from time to time. Such new versions will be similar in
spirit to the present version, but may differ in detail to address new problems or
concerns. Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any later
version", you have the option of following the terms and conditions either of
that version or of any later version published by the Free Software Foundation.
If the Program does not specify a version number of this License, you may
choose any version ever published by the Free Software Foundation.
10 If you wish to incorporate parts of the Program into other free programs whose
distribution conditions are different, write to the author to ask for permission.
For software which is copyrighted by the Free Software Foundation, write to the
Free Software Foundation; we sometimes make exceptions for this. Our decision
will be guided by the two goals of preserving the free status of all derivatives of
our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 879 of 880
10/09/08
BLC 6000 System Configuration and Installation Guide- Release 5.5
Appendix G: Software License Information
GNU General Public License
785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 880 of 880
10/09/08