Occam_OS 5_5_Install_and_Config_guide[1]

0

0

0

0

0

0

0

0

0BLC 6000 System Installation and Configuration GuideRelease 5.5

Occam Networks, Inc. main +1.805.692.29006868 Cortona Drive fax +1.805.692.2999 Part No. 785553Santa Barbara, CA 93117 www.occamnetworks.com Rev. 2.0

BLC 6000 System Configuration and Installation 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.

BLC 6000 Installation and Configuration GuideCopyright © 2008 Occam Networks, Inc. All rights reserved. Printed in USA.

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page iii of 88010/09/08


785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page iv of 88010/09/08


Table of Contents

Table of Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiDocument Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxiWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxiApprovals and Rating Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxiCustomer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxiConventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii

Channel 1 BLC 6000 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1BLC 6000 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3System 6000 BLCs and Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6BLC 6000 Optical Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Channel 2 Installing a BLC 6001 Chassis . . . . . . . . . . . . . . . . . . . . . . . 13Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13BLC 6001 Chassis Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Ethernet Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Grounding Lug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Shelf/Slot ID Selector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Alarm/Auxiliary Console Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Connectors for Subscriber Interfaces and T1 Ports . . . . . . . . . . . . . . . . . . . . . 14

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Unpacking the BLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Cabinet Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Ethernet Network Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Rack Mounting the BLC 6001 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Rack Mount Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Rack Mounting Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Preventing Electrostatic Discharge (ESD) Damage. . . . . . . . . . . . . . . . . . . . . . . . . 19Inserting a Blade Into the BLC 6001 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Connecting the Subscriber and T1 Interface Cable . . . . . . . . . . . . . . . . . . . . . . . . 26

Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27T1 Pinout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Subscriber Pinout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Connecting an ADSL Bridge Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31ADSL Bridge Clip Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page v of 88010/09/08


Table of Contents

Attaching the ADSL Bridge Clip Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Connecting the Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Inserting the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Inserting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Connecting the 10 GigE Copper Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Connecting the 10/100/1000 Base-TX Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . 37Configuring the Slot/Shelf ID Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Using the “show version” Command To Verify the Slot/Shelf ID. . . . . . . . . . . 41BLC 6001 Chassis Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Channel 3 Installing a BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . 43Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Rear Panel of BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Ethernet Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Alarm/Auxiliary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Connectors for Subscriber Interfaces and T1 Ports. . . . . . . . . . . . . . . . . . . . . . 45Shelf Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Cabinet Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Network Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Preventing Electrostatic Discharge (ESD) Damage . . . . . . . . . . . . . . . . . . . . . . 49Unpacking the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Rack Mounting the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Connecting the Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Inserting a Blade Into the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Attaching an ADSL Bridge Clip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

ADSL Bridge Clip Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Attaching the ADSL Bridge Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Connecting the Subscriber and T1 Interface Cable . . . . . . . . . . . . . . . . . . . . . . . . 64T1 Pinout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Subscriber Pinout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Connecting the 10/100/1000 Base-TX Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . 71Connecting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Inserting the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Inserting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring the Shelf ID Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Using the show version Command To Verify the Slot/Shelf ID . . . . . . . . . . . . 75

BLC 6012 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Channel 4 Installing a BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . 77

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page vi of 88010/09/08


Table of Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Rear Panel of BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Connectors for Subscriber Interfaces and T1 Ports . . . . . . . . . . . . . . . . . . . . . 79Ethernet Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Alarm/Auxiliary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Shelf Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Cabinet Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Network Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Preventing Electrostatic Discharge (ESD) Damage . . . . . . . . . . . . . . . . . . . . . . 83Unpacking the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Rack Mounting the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Inserting Blades Into the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Attaching an ADSL Bridge Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

ADSL Bridge Clip Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Attaching the ADSL Bridge Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Connecting the Subscriber and T1 Interface Cable . . . . . . . . . . . . . . . . . . . . . . . . 98T1 Pinout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Subscriber Pinout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Connecting the 10/100/1000 Base-TX Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . 104Connecting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Inserting the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Inserting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Configuring the Shelf ID Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Using the show version Command To Verify the Slot/Shelf ID . . . . . . . . . . . 108

BLC 6012i Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Channel 5 BLC 6012i Chassis Configuration . . . . . . . . . . . . . . . . . . . 111Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Chassis Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112BLC 6012i Chassis Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113BLC 6012 Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Bookend Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Interior Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Frontpanel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Frontpanel Mode On the 6314 and 6450 Fiber Blades. . . . . . . . . . . . . . . . . . 117Frontpanel Mode On the 6312 Fiber Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Installing Blades Into the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Factory Default Blade Configuration In a BLC 6012i Chassis . . . . . . . . . . . . 119Blades Relocated Into a BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page vii of 88010/09/08


Table of Contents

Channel 6 Command-Line Interface (CLI) Basics . . . . . . . . . . . . . . . . 121Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121Basic Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122Interface Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Profile Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Service Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Channel Configuration Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130QoS Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130Finding Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Issuing Privileged Mode Commands From Other Configuration Modes . . . . . .131Getting Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Undoing a Command or Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Saving Configuration Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Erasing Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133

Channel 7 Initial Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . 135Selecting a Connection Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Using a DHCP Server to Assign an IP Address to the BLC . . . . . . . . . . . . . . .135Manually Assigning a Static IP Address to the BLC . . . . . . . . . . . . . . . . . . . .135

Connecting the Console (Craft Interface) Cable . . . . . . . . . . . . . . . . . . . . . . . . .136Console Cable Rating and Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Inserting the Console Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

Remote Connection Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139Secure Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139Telnet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

Configuring a Prewired BLC 6012 Chassis With the “load network” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

“load network” Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143Assigning a Static IP Address to the BLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146Configuring System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148Configuring Network Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150Configuring NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Channel 8 Configuring Multihoming. . . . . . . . . . . . . . . . . . . . . . . . . . 153Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154Multihoming Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Configuring a BVI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157Configuring a Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

Configuring a Routing Table For BVI 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Configuring a Routing Table For BVI 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Configuring Protocols To Run On a Specific BVI . . . . . . . . . . . . . . . . . . . . . . . . .160MGCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160RTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Checking the BVI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page viii of 88010/09/08


Table of Contents

Channel 9 Ethernet Interface Configuration . . . . . . . . . . . . . . . . . . . 165Ethernet Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Speed, Duplex and Media Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Speed and Duplex Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Media Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Using Speed, Duplex and Media Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Configuring 10/100/1000 Base-TX Ethernet (UTP) Interfaces . . . . . . . . . . . . . . 171Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces . . . . . . . 173Configuring 10 GigE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Checking Connectivity and Verifying Configuration . . . . . . . . . . . . . . . . . . . . . . 176

Checking Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Verifying Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Channel 10 Ethernet Protection Switching (EPS) Overview . . . . . . . . . 179Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179EPS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

VPSs and VPTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Failure Detection Using “Heartbeats”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180VLAN IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183VLAN Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

EPS Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Ethernet Interfaces on VPSs and VPTs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

VPT Interfaces on EPS Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187VPS Interfaces on EPS Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188EPS Tagged and Untagged Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Rate Limiting VLANs on the BLC 6312 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

MAC Address Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Limiting MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

QoS Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Subtended Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194EPS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

EPS Failover Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Opposite Path Group Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196EPS DITW Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Ethernet Loop Detection (ELD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Adding a VPS To an Active Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Channel 11 Configuring an EPS Aggregation Ring Network . . . . . . . . 199Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

EPS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199EPS Aggregation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Configuring an Access-Ring Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Configuring a Ring Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Configuring BLCs On an Aggregation Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Configuring a BLC as a VPT on an Aggregation Ring . . . . . . . . . . . . . . . . . . . 208Configuring a BLC as a VPS on an Aggregation Ring. . . . . . . . . . . . . . . . . . . 209

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page ix of 88010/09/08


Table of Contents

Configuring an Interconnect on a VPT on an Aggregation Ring . . . . . . . . . . . .210Configuring a VPT Ethernet Interface as a Path Group Participant . . . . . . . . . .212Configuring a VPS Interface on an Aggregation Ring. . . . . . . . . . . . . . . . . . . . .214

Configuring a Passthrough Interface on an Aggregation Ring VPS . . . . . . .214Configuring a VPS Interface on a Subtended Aggregation Ring . . . . . . . . . . . .216

Configuring a VPS Interface For a Subtended Aggregation Ring . . . . . . . . .216Configuring a Passthrough Interface For a Subtended Aggregation Ring. .218

Configuring an Access-Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Configuring a VPS On an Access-Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Configuring a VPS Interface For an Access Ring. . . . . . . . . . . . . . . . . . . . . . .221Using the “load network” Command on Access-Rings. . . . . . . . . . . . . . . . . .222Configuring a Passthrough Interface For an Access-Ring . . . . . . . . . . . . . . .223

Configuring a VPS or VPT Ethernet Interface for Untagged Traffic . . . . . . . . . .225Configuring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic . . . . . . .226

Configuring a Tagged Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226Attaching a Tagged Profile to an Ethernet Interface . . . . . . . . . . . . . . . . . . .228Example Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229Viewing Your Tagged Profile Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .229

Configuring TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230Priority Bit Settings On Q-in-Q tagged traffic . . . . . . . . . . . . . . . . . . . . . . . .230Configuring TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231Double Tagged Ports and Behaviors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232Policy Map Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Configuring a TLS Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Configuring an Ethernet Interface For TLS . . . . . . . . . . . . . . . . . . . . . . . . . . .234

Configuring a BLC to Run EPS with Non-EPS Devices. . . . . . . . . . . . . . . . . . . . .235Ethernet Loop Detection (ELD) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .236

ELD Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236stp access Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237Enabling and Disabling ELD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

Displaying Information About Your EPS Configuration . . . . . . . . . . . . . . . . . . .239

Channel 12 Configuring Subtended EPS Access-Rings with Ethernet Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243Configuring a Subtended Access Ring With an Ethernet Link . . . . . . . . . . . . . .244

VPS and Ethernet Interface Configuration Steps For VPS 4 . . . . . . . . . . . . .246VPS and Ethernet Interface Configuration Steps For VPS 5 . . . . . . . . . . . . .248VPS and Ethernet Interface Configuration Steps For VPS 6 and 7 . . . . . . . .250

Channel 13 Configuring EPS Over MLPPP Links . . . . . . . . . . . . . . . . . . 253Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253

EPS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253MLPPP Engineering Guidlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254MLPPP Stability Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

Configuring VLAN Untagged Traffic Over MLPPP . . . . . . . . . . . . . . . . . . . . . . . .257Configuring a Subtended EPS Ring with MLPPP . . . . . . . . . . . . . . . . . . . . . . . . .259

Configuration Steps Figure 13-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page x of 88010/09/08


Table of Contents

VPT 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Interface A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Interface C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264VPT 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Interface B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Interface L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265VPS 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Interfaces D and E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266VPS 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Interfaces F and G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Interface (Multilink Group) M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268VPS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Interfaces H and I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Interface (Multilink Group) T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271VPS 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Interfaces J and K. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272VPS 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Interface (Multilink Group) N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Interface O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275VPS 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Interfaces P and Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276VPS 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Interface R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Interface (Multilink Group) S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Channel 14 Ethernet Subscriber Interfaces. . . . . . . . . . . . . . . . . . . . . . 281Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

EPS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282VLAN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Defining a Unicast Rate Limiting Policy Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Policy Map Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Configuring an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Configuring an Ethernet Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Copying an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Deleting an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Displaying Access Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Configuring an Ethernet Subscriber Interface and an Ethernet Service . . . . . . 292Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Voice VLAN 2 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Data VLAN 4 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Video VLAN 6 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Channel 15 Rate Limiting on Ethernet and XG Interfaces . . . . . . . . . . 297Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Rate Limiting Unicast Traffic on VLANS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Configuring Rate Limiting on Egress Ethernet and XG Interfaces . . . . . . . . . . . 298Configuring Rate Limiting on Ingress Ethernet Interfaces . . . . . . . . . . . . . . . . . 298

Configuring Broadcast Rate Limiting on Ingress Ethernet and

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xi of 88010/09/08


Table of Contents

XG Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298Configuring Multicast Rate Limiting on an Ingress Ethernet Interface . . . .299Configuring Unknown Unicast Rate Limiting on Ingress Ethernet and XG Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299

Verifying Your Rate Limiting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300

Channel 16 Configuring Link Aggregation . . . . . . . . . . . . . . . . . . . . . . 303Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303Supported Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304Supported Chassis Wiring Arrangements. . . . . . . . . . . . . . . . . . . . . . . . . . . . .305Supported BLCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305

Configuring a LAG Out Of a VPT That Will Connect To A Head End Router . . .306Clearing the Configuration of a LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308

Configuring a LAG As an Interconnect Between Two BLC 6001 Chassis . . . . . .309Configuring a LAG Out Of a VPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311Assigning Ethernet Interfaces To a LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315

Sample Configuration Of a LAG To a Head End Router . . . . . . . . . . . . . . . . .315Sample Configuration Of a LAG Interconnect Between BLC 6001 Chassis .315

Viewing Your LAG Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317“show bridge interface lag” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317“show interfaces lag” Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318“show running-config lag” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319

Channel 17 Configuring Span Powered T1 Lines . . . . . . . . . . . . . . . . . 321Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322T1 Span Power Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323

Power Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323Power Loop Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323

Other T1 Line Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324Viewing Your Powered T1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328

Channel 18 Configuring DSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 329Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329ADSL2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329

Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329Annex L (Extended Reach) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329Annex M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330DSL Line Retransmission Error Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330SRA (Seamless Rate Adaptation). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330SELT and DELT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331

DSL Interface Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332Configuring a DSL Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334

Default DSL Profile For ADSL2+ BLCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334Creating and Attaching a Profile to an Interface . . . . . . . . . . . . . . . . . . . . . .336Commands to Configure the DSL Line Retransmission Error Recovery Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xii of 88010/09/08


Table of Contents

Commands to Configure Upstream and Downstream Maximum and Minimum Bitrates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Commands to Configure Traffic Related Values . . . . . . . . . . . . . . . . . . . . . . . 340Commands to Enable/Disable Bitswapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Commands to Set DSL Profile SNR Margin Values . . . . . . . . . . . . . . . . . . . . . 343Commands to Set DSL Profile Test Related Values . . . . . . . . . . . . . . . . . . . . . 346Commands to Set SRA Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Recommended DSL Profile Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347Detaching a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348Deleting a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348Copying a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348Viewing Information About DSL Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Configuring an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Defining a Unicast Rate Limiting Policy Map . . . . . . . . . . . . . . . . . . . . . . . . . 350Configuring an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Detaching an Access Profile From a Service . . . . . . . . . . . . . . . . . . . . . . . . . . 354Displaying Access Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Copying an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Deleting an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Configuring a DSL Bonding Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356DSL Bonding Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Configuring DSL Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Viewing the Bonding Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Enabling and Configuring a DSL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358Configure a DSL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358Disabling an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359Viewing Information About DSL Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Enabling and Configuring Service(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Displaying Service Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . 363

Channel 19 PPPoA to PPPoE Interworking Function. . . . . . . . . . . . . . . 365Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

PPPoE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365PPPoA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368PPPoA to PPPoE IWF and Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . 368

PPPoA to PPPoE IWF Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Clearing a PPPoE Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370Clearing Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Channel 20 Configuring SIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

BLCs That Support SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Chapter Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380SIP Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

SIP Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382User Agents and Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382SIP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xiii of 88010/09/08


Table of Contents

SIP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385SIP Message Flow Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .386

Configuring Global SIP Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388Configuring a Voice Port SIP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389

Default Voice Port Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389Voice Port Sip Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389Voice Port SIP Profile Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . .391Copying a Voice Port Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .396Deleting a Voice Port Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .396

Configuring a SIP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .397Default SIP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .397SIP Profile Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398Copying a SIP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403Deleting a SIP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403

Configuring a Voice Port For SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404Detaching a Voice Port Profile From a Voice Port . . . . . . . . . . . . . . . . . . . . .407Attaching a New SIP Profile to a Voice Port Previously Configured For SIP408

Viewing Your SIP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .409Viewing Global SIP Settings On the BLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . .409Viewing SIP Configuration Settings On Voice Ports . . . . . . . . . . . . . . . . . . . .410Viewing Information About Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .414Viewing Information About SIP Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . .416Viewing Information About SIP Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .418

Digit Map Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .419Default SIP Digit Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .419Sample Digit Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .420

CLASS Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .421

Channel 21 Access Control Lists (ACLs). . . . . . . . . . . . . . . . . . . . . . . . . 423Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .423

Ethernet and IP ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .423Ethernet ACLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425

Configuring an Ethernet ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425Removing an Entry From an Ethernet ACL . . . . . . . . . . . . . . . . . . . . . . . . . . .426Attaching an Ethernet ACL To a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426Detaching an Ethernet ACL From a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . .426

IP Access Control Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427Configuring an IP ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427Deleting an Entry from an IP ACL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .428IP ACL Configuration Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .428Replacing an IP ACL on a BVI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429Removing an IP ACL on a BVI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429Attaching an IP ACL to a VLAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429Removing an IP Access-List From a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . .430

Displaying ACL and Access Group Information . . . . . . . . . . . . . . . . . . . . . . . . . .431Displaying Ethernet ACL Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .431Displaying IP ACL Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .431Using the “show subscriber access-group” Command . . . . . . . . . . . . . . . . . .432

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xiv of 88010/09/08


Table of Contents

Security Filter Configuration Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434Scenario 1 - Single PVC with DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434Scenario 2 - Single PVC with PPPoE Access . . . . . . . . . . . . . . . . . . . . . . . . . . 435Scenario 3 - Multiple PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

Channel 22 IP Security Management (IPSM) . . . . . . . . . . . . . . . . . . . . 439IPSM Feature Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440ARP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Peer to Peer Traffic Blocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Broadcast Traffic Policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441Blacklisting Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441Ingress Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442Subscriber Side Association Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442Network Side Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443Static Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444Managing Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

DHCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451DHCP Leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451DHCP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452DHCP Layer 2 and Layer 3 Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452Displaying DHCP Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . 457

ARP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464ARP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464ARP Proxy in Conjunction with Peer to Peer Traffic Blocking . . . . . . . . . . . 465Broadcast Traffic Policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Blacklisting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469Ingress Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

Ingress Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473Ingress Filter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474Displaying Your Ingress Filter Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 476Ingress Filter Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

Channel 23 Managed Multicast Via IGMP Proxy . . . . . . . . . . . . . . . . . 479Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479Interface Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

Router Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479Passthrough Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480Host Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480IGMP Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480Disabling Traffic Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

Optional IP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481Default IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481Applying or Changing an IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481Recommended IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xv of 88010/09/08


Table of Contents

Sample IGMP Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .483Configuring Managed Multicast Traffic Parameters on Ethernet Interfaces . .485Configuring Multicast Parameters on Ethernet Subscriber Interfaces . . . . . . .486

Configuring an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .487Configuring an Ethernet Port as a Subscriber Interface . . . . . . . . . . . . . . . .488Configuring an Ethernet Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .488

Displaying Information About Your IGMP Configuration . . . . . . . . . . . . . . . . . .491Show Multicast Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .491

Channel 24 Configuring Circuit Emulation Switching (CES) . . . . . . . . 495Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .495

CES Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .495Bandwidth Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .496Configuration Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .496

Choosing a T1 Line Framing Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .497Sample CES Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .498

Configuring Synchronous CES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .499Network Clocking in a Synchronous CES Network . . . . . . . . . . . . . . . . . . . . .499Configuring NSP on a Synchronous CES Network . . . . . . . . . . . . . . . . . . . . .503Configuring T1 Interfaces in a Synchronous CES Network . . . . . . . . . . . . . .504

Configuring Asynchronous CES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .509Network Clocking in an Asynchronous CES Network . . . . . . . . . . . . . . . . . . .509Configuring T1 Interfaces in an Asynchronous CES Network . . . . . . . . . . . .510

Terminating a CES Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .515Viewing Your CES Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .515

Sample Output for Synchronous CES Configurations . . . . . . . . . . . . . . . . . .515Sample Output for Asynchronous CES Configurations . . . . . . . . . . . . . . . . .517Explanation of Output For “show ces” Command. . . . . . . . . . . . . . . . . . . . . .519

Channel 25 Configuring MGCP/VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . 521Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .521

Configuration Steps Described In This Chapter. . . . . . . . . . . . . . . . . . . . . . . .521Configuring a Voice Profile For Delivering POTS Over VoIP . . . . . . . . . . . . . . . .523

Default Voice Port Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .523Voice Port Profile Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525

Configuring a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .531Configuring Unbalanced Ringing on a Voice Port . . . . . . . . . . . . . . . . . . . . .532Configuring Maximum Balanced Ringing On a Voice Port . . . . . . . . . . . . . .532

Configuring MGCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .534Blocking New Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .540Displaying Voice Port, Profile and MGCP/VoIP Configuration Information . . .541

Viewing Information About Voice Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .541Viewing Information About Voice Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . .541Viewing Information About MGCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .541

Channel 26 Configuring Cross-Connect Modes on the BLC 6150-01

and the BLC 6246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xvi of 88010/09/08


Table of Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543Configuring a T1 Interface for Cross-Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . 544Configuring Cross-Connect Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

Default Cross-Connect Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546Configuring a Cross-Connect Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553Commands to Configure Cross-Connect Profiles . . . . . . . . . . . . . . . . . . . . . . 554

Attaching a Profile to a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559Displaying Voice Port and Profile Information. . . . . . . . . . . . . . . . . . . . . . . . . . . 560

Channel 27 Configuring DS0 Cross Connect Modes on the BLC 6640-01. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561

DS0 Data Cross-Connect Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561Voice Cross-Connect Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561Clear Channel Voice Cross-Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562

Configuring a T1 Interface for Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . 563Configuring Network Clocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565Configuring a Cross-Connect Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . 566

Default Values For Cross-Connect Subscriber Profiles . . . . . . . . . . . . . . . . . . 566Configuring a Cross-Connect Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . 569

Configuring an Interface Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575Viewing Your Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578

Channel 28 Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 579Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579Shelf Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580Self Deployment Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582

Shelf Configuration Network Design Principals . . . . . . . . . . . . . . . . . . . . . . . 582GR-303 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582Supported GR-303 Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 583Redundant vs. Non-Redundant GR-303 IGs . . . . . . . . . . . . . . . . . . . . . . . . . . 583Silo vs. Striping Configurations For GR-303 IGs . . . . . . . . . . . . . . . . . . . . . . . 584Endpoint Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584Subscriber Profiles for Endpoints / Channels . . . . . . . . . . . . . . . . . . . . . . . . . 585Shelf Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585Interactions With Other Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586Maintenance / Upgrade Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586

Configuring the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587Setting the Shelf and Slot IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587Configuring 6640-01s as Cards in the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . 587Configuring a 6640-01 as a Primary Shelf Controller . . . . . . . . . . . . . . . . . . 589Configuring a 6640-01 as a Standby Shelf Controller. . . . . . . . . . . . . . . . . . 591

Configuring T1 Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592Configuring Network Clocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594GR-303 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xvii of 88010/09/08


Table of Contents

Default GR-303 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .595Configuring a GR-303 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . .601

Configuring an IG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .602Steps to Configure an IG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .605

Configuring Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .609Configuring GR-303 Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .612Initiating a Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .613

Shelf Control Switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .613IG Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .613

Configuring Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .613Removing Cards from the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .613Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615Viewing Your CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .616

hannel 29 Automated Shelf Upgrader. . . . . . . . . . . . . . . . . . . . . . . . . 617Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .617Shelf Status Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .618Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .620

Upgrading the Blades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .620Shelf Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .622

Using the reload shelf Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .622Monitoring the Shelf Reload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .623

Channel 30 Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .629

TR-08 Mode 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .629Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .630

Configuring Network Clocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .630Configuring T1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .632

Configuring the Primary (A) T1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .632Configuring the Remaining T1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .634

TR-08 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .635Creating a TR-08 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .641

Configuring an Interface Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .642Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .645Viewing Your CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .645

Channel 31 Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .647

Port Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .647POTS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .648TR-08 for TDM Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .649Channel Associated Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .649Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .651

Configuring a T1 Interface for TR-08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .652

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xviii of 88010/09/08


Table of Contents

Configuring POTS Channel Bank Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654Default Voice Port Profile on the BLC 6246 and BLC 6150-01 . . . . . . . . . . . 654Pots Channel Bank Profile Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . 656

Configuring a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662Configuring Unbalanced Ringing on a Voice Port . . . . . . . . . . . . . . . . . . . . . 663Configuring Maximum Balanced Ringing on a Voice Port . . . . . . . . . . . . . . 663

Displaying Voice Port and Profile Information. . . . . . . . . . . . . . . . . . . . . . . . . . . 665

Channel 32 Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling (CAS) Mode on the BLC 6640-01. . 667Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667Configuring T1 Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667Configuring Network Clocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669Subscriber Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670

Configuring a Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671Configuring an Interface Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673Viewing Your Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676

Channel 33 Differentiated Services (Diffserv). . . . . . . . . . . . . . . . . . . . 677Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677Flow Classifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677

Untagged Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677802.1Q Tagged Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678

Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678Queue/Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678Configuring IP Diffserv DSCP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679Displaying the Protocol Application DSCP Table . . . . . . . . . . . . . . . . . . . . . . 680

Configuring IP Diffserv DSCP Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681Displaying the DSCP to Priority Mapping Table . . . . . . . . . . . . . . . . . . . . . . . 681

Channel 34 Power Save Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683Enabling and Disabling Power Save Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683Configuring Power Save Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684

Configuring the Bottom Threshold Input Voltage . . . . . . . . . . . . . . . . . . . . . 684Configuring the Power Save Timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684Configuring the Input Voltage When AC Power Is Considered Restored . . . 685

Viewing Power Save Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686

Channel 35 Blade to Blade Communication (SSH From CLI) . . . . . . . . 687Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687Configuring Blade to Blade Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688Deleting a Specified Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689Viewing Public Keys Associated With a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xix of 88010/09/08


Table of Contents

Channel 36 Alarms and Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .691Environment Alarm In and Out Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .692

Alarm In Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .692Alarm Out Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .693Alarm Closure Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .694

Configuring Power Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .696Displaying Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .698

Viewing Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .698Viewing All Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .698Viewing Alarms in a Summarized Format . . . . . . . . . . . . . . . . . . . . . . . . . . . .699

Clearing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .699Clearing the Alarm Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .699Clearing Active Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .699

Displaying Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .700Alarms Catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .703

System Environmental Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .703Physical Port Related Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .705Trunk Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .709EPS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .720Shelf Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .722GNK Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .724Over Temperature Shutdown Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .725Power Management Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .726Fan Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .727Native IP Management Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .728

Index of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .732

Channel 37 Simple Network Management Protocol (SNMP) . . . . . . . . 735Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .735Default SNMP Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .735Enabling SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .736Displaying SNMP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .743

User Mode Show SNMP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .743Privileged Mode Show SNMP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . .745

SNMP Support For Activation of Subscriber Services . . . . . . . . . . . . . . . . . . . . .747DSL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .747Ethernet Subscriber Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .748Media Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .748Trunking Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .749

Channel 38 System Logging (Syslog). . . . . . . . . . . . . . . . . . . . . . . . . . . 751Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .751Enabling Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .752

Facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .752Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .752Example Syslog Logging Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .753

Disabling Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .754

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xx of 88010/09/08


Table of Contents

Displaying Syslog Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754

Channel 39 Viewing Your Hardware and Software Configuration. . . . 755Viewing the Startup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755Viewing the Running Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

Displaying Information About Interfaces In the Running Configuration . . 756Displaying Information About the Running Configuration File . . . . . . . . . . 757

Viewing Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759Viewing Information About All Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . 759Viewing Information About Specific Interfaces . . . . . . . . . . . . . . . . . . . . . . . 760Viewing Summarized Information About Interfaces . . . . . . . . . . . . . . . . . . . 760

Viewing the Software and Hardware Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . 761Displaying the System Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761Viewing Information About the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . 761

Viewing the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765Checking the Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

Displaying Domain Name Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766Pinging IP Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

Channel 40 Updating Your System Configuration . . . . . . . . . . . . . . . . 769Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769BLC System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770

Boot PROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770Boot Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770

Upgrading and Verifying a New Software Release . . . . . . . . . . . . . . . . . . . . . . . 771Using the upgrade software Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773Displaying a List of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773Using the “boot enable” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774Installing a New Kernel or Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

Installing a New Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775Installing a New Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

Checking the Validity of a Software Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776Verifying the Integrity of a Downloaded System Image . . . . . . . . . . . . . . . . 776Verifying the Integrity of a Bootflash Partition . . . . . . . . . . . . . . . . . . . . . . . 776

Deleting a Software Release File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777Displaying the Status of Installed Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778

Displaying Information about a Bootflash Partition . . . . . . . . . . . . . . . . . . . 778Displaying Information about the Current Status of the Bootable Images .778Displaying the Contents of the Boot EEPROM . . . . . . . . . . . . . . . . . . . . . . . . 779Displaying the Contents Of the Manufacturing EEPROM . . . . . . . . . . . . . . . 779

Channel 41 Configuring Network Traffic Intercept (NTI) . . . . . . . . . . . 781Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781

MAC Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781Targeted Subscriber Traffic Monitoring Locations . . . . . . . . . . . . . . . . . . . . . 782

NTI Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784Configuring a NTI Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxi of 88010/09/08


Table of Contents

Enabling NTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .785Viewing the NTI Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .786

“show nti profile [profile-name]” Command. . . . . . . . . . . . . . . . . . . . . . . . . .786“show nti config” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .786“show nti status” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .787“show nti tcpdump” Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .787

Channel 42 ADSL2+ Line Testing- SELT, DELT and MLT . . . . . . . . . . . . 789Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .789SELT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .790DELT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .792Examples of SELT and DELT Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .795

Example SELT Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .795Example DELT Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .801

Channel 43 POTS Line Testing- MLT, Ringer and Tone Detection Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .807MLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .808

BLCs That Feature MLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .808SNMP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .808Showing the Tip-Ring Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .809Performing a Metallic Loop Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .812Viewing the Results of the MLT Test in a Log File . . . . . . . . . . . . . . . . . . . . . .818Detecting a Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .819Testing the Loop Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .820

Off-Hook Tone Generator Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .821Ring Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .822Tone Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .823

Appendix A Safety Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .825Restricted Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .825Protective Earthing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .825Safety Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .826

Safety Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .826Equipment Interconnection Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .827Preventing Electrostatic Discharge Damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . .827FCC Part 15 Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .828FCC Part 68 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .829IC CS-03 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .830

Ringer Equivalence Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .830Equipment Attachment Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .830

Laser Transmitter Operation and Safety Precautions. . . . . . . . . . . . . . . . . . . . . .831Precautions for Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .831Transmitter Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .831

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxii of 88010/09/08


Table of Contents

Appendix B BLC 6012 Chassis Wiring Arrangements. . . . . . . . . . . . . . 833Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833

Shielded Cat 6 Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833H Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834

H Wiring Configuration In Full BLC 6012 Chassis. . . . . . . . . . . . . . . . . . . . . . 834H Wiring Configuration In Partially Full BLC 6012 Chassis . . . . . . . . . . . . . . 836

FTTX Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837Backbone Transport Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837First Subtended Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839Second Subtended Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840Subtended Ring 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840Forth Subtended Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841Subtended Ring 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841

Gateway Chassis Wiring Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845POTS Wiring Arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847

6012-P First Subtended Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8496012-P Second Subtended Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8496012-P Third Subtended Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8516012-P Fourth Subtended Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852

Ring Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854

Appendix C Decimal to Hexadecimal Conversion Table . . . . . . . . . . . . 857Decimal to Hexadecimal Conversion Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857

Appendix D Installing a Cable Guard on a BLC 6012 Chassis859Installing a Cable Guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859

Appendix E Replacing a Fan Filter on a BLC 6012 Chassis . . . . . . . . . 863

Appendix F Shelf Hardware Upgrade Instructions . . . . . . . . . . . . . . . . 867Pre-upgrade Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868

Appendix G Software License Information . . . . . . . . . . . . . . . . . . . . . . 871Open SSL Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871SSLEAY Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872Open SSH Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873Carnegie Mellon License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873GNU General Public License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875

Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxiii of 88010/09/08


Table of Contents

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxiv of 88010/09/08

BLC 6000 System Configuration and Installation Guide- Release 5.5 Preface

Document Objectives

0Preface

In This Chapter:Document Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvWho Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvApprovals and Rating Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvCustomer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvConventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvi

Document ObjectivesThis guide describes how to install and configure Release 5.5 of the BLC 6000 System.

Who Should Read This GuideThis guide is intended to be used by the following network experts:

Component installers who have experience installing communications equip-ment and cables.

Network administrators who have experience with communications networks, protocols, and equipment.

Approvals and Rating LabelThe approvals and rating label is located on the bottom of the BLC or blade. This label also provides the model and serial numbers.

Customer SupportBusiness hours:

5 a.m. to 5 p.m. PST Monday through Friday

+1-805-692-2911 or 1-888-525-2435

[email protected].

For urgent matters after regular business hours and on weekends, please call +1-805-692-2911 AND send an e-mail to “[email protected]”. A support engineer will return your call.

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxv of 88010/09/08

BLC 6000 System Configuration and Installation Guide- Release 5.5 PrefaceConventions

ConventionsThe following conventions are used in this manual:

Conventions Descriptioncourier 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 | variable3}

Command variables contained in braces and separated by a vertical bar represent a group of items where it is mandatory that at least one must be selected.

[variable1 | variable2 | variable3]

Command variables contained in square 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 tosupplementary information.

Caution: Text This caution symbol alerts you to a situa-tion that could result in equipment damage or loss of data.

Warning: Text This warning symbol alerts you that failure to take or avoid a specific action might result in physical harm to you or to the hardware.Be sure to read the safety warnings located in Appendix A, Safety Warnings on page 825.

!

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page xxvi of 88010/09/08

BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 1: BLC 6000 System Overview

Overview

Chapter 10BLC 6000 System Overview

In This Chapter:Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1BLC 6000 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3System 6000 BLCs and Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6BLC 6000 Optical Transceivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

OverviewThe 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.

Table 1-1: BLC 6000 Blade Overview

Blade Model POTS ADSL2Plus Ports

T1 Ports Optical GigE Ports

10GigE Ports

6150 48 4 4

6151 48

6152 48 4

6252 48 48 4

6212 48 4

6244 24 24 2

6246 24 24 4 (powered) 2

6312 22 2 copper

6314 16 2 copper,

2 optical

6440 8 4

785553 Rev. 2.0 Proprietary Information - Occam Networks Inc. Page 1 of 88010/09/08

BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 1: BLC 6000 System OverviewOverview

Table 1-2: BLC 6000 Chassis Overview

6640 8 (GR-303) or

4 (TR-08)

4

6660 8 4

Chassis Model Slots Chassis Name

6012 12 12 RU chassis

6001 1 1 RU chassis

Blade Model POTS ADSL2Plus Ports

T1 Ports Optical GigE Ports

10GigE Ports



BLC 6000 Chassis

BLC 6000 ChassisThere are two chassis in the BLC 6000 product line, the one rack unit (RU) BLC 6001 stackable chassis and the 12 RU BLC 6012 high capacity chassis. The BLC 6012 comes in different versions, as described below in Table 1-3:

Table 1-3: BLC 6000 Chassis

Chassis Name/Part Number

Description

BLC 6001 Stackable Chassis

Part Number:710032

Single blade capacity.

Horizontal chassis with replaceable fan assembly.

Requires One 1 ¾ inch space in 19- or 23-inch rack, 11 ½ inches deep.

BLC 6012/710033

Twelve blade capacity.

Vertical chassis with replaceable fan assembly and optional air filter.

Bare unwired chassis intended as a spare system and not for general deployment.

Requires 12 Rack Units in 23-inch rack, 11 ½ inches deep.

BLC 6012 High Capacity RT Chassis wired Gateway for any blade other than 6235 or 6151

PN: 710033-G


Vertical chassis with replaceable fan assembly and air filter.

Fiber protection cover.

Requires 12 Rack Units in 23-inch rack, 11 ½ inches deep

Includes Gateway backplane wiring.

The fan tray does not have a filter because this chassis is intended for use in enclosed cabinets.

BLC 6012 High Capacity RT Chassis wired for POTS appli-cations using 6151 blades

PN: 710033-P





Includes POTS backplane wiring.



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 1: BLC 6000 System OverviewBLC 6000 Chassis

BLC 6012 High Capacity RT Chassis wired for Voice and Data applications using:

a. 6235 and other 6000 bladesOR

b. no more than five 6151 blades and other 6000 blades

PN: 710033-R





Includes Ring backplane wiring.


BLC 6012 High Capacity CO Chassis wired for POTS appli-cations using 6151 blades

PN: 710053-P





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.



BLC 6000 Chassis

BLC 6012 High Capacity CO Chassis wired Gateway for any blade other than 6235 or 6151

PN: 710053-G





Includes Gateway backplane wiring and Fiber Management Front cover.


BLC 6012 High Capacity CO Chassis wired for POTS appli-cations using 6151 bladesPN: 710053-R





Includes Ring backplane wiring and Fiber Management Front cover.



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 1: BLC 6000 System OverviewSystem 6000 BLCs and Blades

System 6000 BLCs and BladesEach BLC and blade is a complete unit with it own processing capacity and a high performance, fully capable Ethernet switch. A blade may be deployed as a standalone in a BLC 6001 chassis or in combinations in a BLC 6012 chassis. BLCs and blades include transport ports along with the subscriber or switch interface ports.

The System 6000 BLCs and blades are described below in Table 1-4:

Table 1-4: BLC 6000 Blades

Blade Number and Name

Description

BLC 6150-01 and 6150-01 POTS Blade

48 Lifeline POTS ports

10 GbE ports

6x10/100/1000 BaseTX RJ45 ports

4x1GbE SFP ports

POTS to VoIP, MGCP signaling

8 T1 ports



2 100 M Ethernet ports




10 GbE ports


4x1GbE SFP ports

BLC 6212-02 and 6212-02 ADSL2Plus Blade

48 ADSL2Plus ports

10 GbE ports

6x10/100/1000TX RJ45 ports

4x1GbE SFP ports

BLC 6214 and 6214 ADSL2Plus with Gigabit Ethernet, Internal Splitter Blade

48 ADSL2Plus ports

10 GbE ports

6x10/100/1000TX RJ45 ports

4x1GbE SFP ports

BLC 6244

ADSL2Plus and POTS with Gigabit Ethernet

24 ADSL2Plus and Lifeline POTS combination ports

8 GbE ports

6x10/100/1000BaseTX RJ45 ports

2x1GbE SFP ports



System 6000 BLCs and Blades

BLC 6246

ADSL2Plus and POTS with Gigabit Ethernet and Powered T1


8 GbE ports


2x1GbE SFP ports

4 Powered T1 ports

BLC 6252-03 and 6252-03 ADSL2Plus and POTS Blade


10 GbE ports


4x1GbE SFP ports

BLC 6312 and 6312 Optical Line Termination (OLT) Blade

18 SFP Fiber ports

4 combination 10/100/1000 BaseT or SFP ports

2 10 Gigabit Intelligent Blade Interconnect Archi-tecture (IBIA) ports

BLC 6314 and 6314 10 GigE Optical Packet Transport and OLT Blade

18 SFP Fiber ports



BLC 6440-01 and 6440-01 Optical Packet Transport Blade

10 GbE ports


4x1GbE SFP ports

8 T1 ports

BLC 6450 and 6450 10GbE Aggregation Blade

18 SFP Fiber ports



BLC 6640 and 6640 Subscriber Trunk Gateway Blade

8 T1 ports that support up to one TR-08 Group or one GR-303 Group

10 GbE ports


4x1GbE SFP ports

2 ports either 1GbE SFP or 10/100/1000BaseTX

BLC 6640-01 and 6640-01 Subscriber Trunk Gateway Blade

8 T1 ports that support up to one TR-08 Group or one GR-303 Group

10 GbE ports


4x1GbE SFP ports


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 1: BLC 6000 System OverviewSystem 6000 BLCs and Blades

BLC 6660-01 and 6660-01 Emer-gency Stand Alone (ESA) Blade

Supports 600 ESA subscribers

10 GbE ports


4x1GbE SFP ports

8 T1 ports

BLC 6660-02 and 6660-02 ESA Blade


10 GbE ports


4x1GbE SFP ports

8 T1 ports

BLC 6660-03 and 6660-03 ESA Blade


10 GbE ports


4x1GbE SFP ports

8 T1 ports



BLC 6000 Optical Transceivers

BLC 6000 Optical TransceiversPart Number Description

105004 1Gb/100Mb EO-XCVR 1310nm SMF SFP LC 15dB Ethernet Optical Transceiver Single Mode Fiber

Small Form-factor Pluggable

LC Connector

-40oC to +80oC

Output Power -5.0 to 0 dBm

Minimum Input Power -20.0 dBm

Maximum Input Power -3.0 dBm

Power Budget 15.0 dB



LC Connector

40oC to +80oC

Output Power -4.0 to +1.0 dBm



Power Budget 17.0dB



LC Connector

-40oC to +80oC






BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 1: BLC 6000 System OverviewBLC 6000 Optical Transceivers

105013 1 Gb Ethernet Optical Transceiver, 1310nm, Single Mode Fiber,

Small Form-factor Pluggable,

LC Connector,

-40oC to +80oC,

Output Power -11.0 to -3.0 dBm,

Minimum Input Power -20.0 dBm,


Power Budget 9.0 dB

105019 1Gb/100Mb EO-XCVR, 850nm Multi-Mode, SFP LCMb Ethernet Optical Transceiver Multi Mode Fiber


LC Connector

-5oC to +70oC

Used only for in-building, local connections

105145 1Gb/100Mb EO-XCVR 1550nm SMF SFP LC 22dB1 Gb / 100 Mb Ethernet Optical Transceiver Single Mode Fiber


LC Connector

-25oC to +85oC





105146 1Gb/100Mb EO-XCVR 1550nm Single-Mode SFP LC 24dB Ethernet Optical Transceiver

Single Mode Fiber


LC Connector

-5oC to +70 oC

Output Power 0.0 to +5.0 dBm






BLC 6000 Optical Transceivers

105160 1 GbE Single Fiber XCVR 1310nm Xmt/1490nm Rcv SMF SFP LC 11dB 1 Gb Ethernet Optical Transceiver

Single Fiber

1310nm transmit and 1490nm receive

Single Mode Fiber


LC Connector

-40oC to +80oC

Output Power -9.0 to -3.0 dBm




10 Km range

105161 1 GbE Single Fiber XCVR 1490nm Xmt/1310nm Rcv SMF SFP LC 11dB 1 Gb Ethernet Optical Transceiver

Single Fiber

1490nm transmit and 1310nm receive

Single Mode Fiber


LC Connector

-40oC to +80oC

Output Power -9.0 to -3.0 dBm


Maximum Input Power -3.0 dBm,


10 Km range


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 1: BLC 6000 System OverviewBLC 6000 Optical Transceivers


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 2: Installing a BLC 6001 Chassis

Introduction

Chapter 2Installing a BLC 6001 Chassis

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13BLC 6001 Chassis Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Rack Mounting the BLC 6001 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Preventing Electrostatic Discharge (ESD) Damage . . . . . . . . . . . . . . . . . . . . . . . . . . 19Inserting a Blade Into the BLC 6001 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Connecting the Subscriber and T1 Interface Cable. . . . . . . . . . . . . . . . . . . . . . . . . . 26Connecting an ADSL Bridge Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Connecting the Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Connecting the 10 GigE Copper Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Connecting the 10/100/1000 Base-TX Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Configuring the Slot/Shelf ID Selector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38BLC 6001 Chassis Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

IntroductionThis 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.

Figure 2-1: BLC 6001 Chassis With 6314 Blade Inserted


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisBLC 6001 Chassis Rear Panel

BLC 6001 Chassis Rear PanelFigure 2-2: BLC 6001 Chassis Rear Panel

Ethernet InterfacesThere are six RJ45 connectors for 10/100/1000-TX Ethernet Interfaces.

PowerThere are -48 VDC Power A and B inputs on a terminal strip.

Grounding LugThe grounding lug attaches a ground cable in the range of 8 to 10 AWG.

Shelf/Slot ID SelectorThe Shelf/Slot ID selector is on four rotary switches on rear panel.

Alarm/Auxiliary Console PortThere is an alarm output, alarm input and auxiliary console port on an 8-pin Molex connector.

Connectors for Subscriber Interfaces and T1 PortsThere are four 50-pin Champ connectors per slot (48 total). These connectors are not used on the BLC

RJ45 CONNECTORS FORETHERNET INTERFACES

POWER

GROUND

SHELF SELECT

ALARM/AUX

50-PIN CHAMP CONNECTORSFOR SUBSCRIBER INTERFACES

AND T1 INTERFACES



Preparing for Installation

Preparing for InstallationUnpacking the BLC

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.

1 Inspect all packing containers. If any damage or other signs of mishandling is evident, immediately inform both the carrier and Occam Networks before proceeding.

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

3 Remove the Rack Mount Kit.

4 Carefully remove the chassis from the container.

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.

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisSite Preparation

Site PreparationProper installation is necessary to prevent injury to yourself and damage to the BLC. Evaluate your site using the following guidelines prior to installation.

Cabinet PreparationMake 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.

PowerMake sure that you have access to the power system and that the system supports the power requirements for the BLC:

Input Voltage Range: -36 to -75 VDC (-48VDC Nominal) typical

Power consumption rating: 3A Max, 150 watts typical

Ethernet Network FacilityAn 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 dual single mode optical connection, using the appropriate small form factor pluggable (SFP) laser module.



Site Preparation

CablesMake sure that each cable is adequate for installation at your site:

Table 2-1: Cable Descriptions

Cable Connector Part Number

Craft Interface (Console) Cable

RJ-45 to DB-9 Included

Alarm Cable 8-Pin Molex connector

Included

Ethernet Cable 10/100 /1000 Base-TX Interfaces: Cat 6e

User Supplied

1 GbE Ethernet Interfaces:

LC Connector

User Supplied

Power Cable

Red, 18 AWG, PVC Insul., -48VDC

User supplied

or

PN 695228(Power Wiring Kit with 15 foot A/B power (Black) and return (Red) 18 AWG and a 15 foot 8 AWG Ground (Yellow) wires with appropriate termi-nals for attaching to BLC 6001 Chassis)

Power Cable

Black, 18 AWG, PVC Insul., -48Return

Ground Cable

8 AWG


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisRack Mounting the BLC 6001 Chassis

Rack Mounting the BLC 6001 ChassisThe BLC 6001 chassis comes with two sets of mounting brackets attached to the chassis and a rack mount kit (P/N 535107). The brackets come attached to the center of the BLC, but may also be attached to the front or the rear of the chassis.

Rack Mount KitThe contents of the rack mount kit are:

Two 23 inch rack mount adapters

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.

Figure 2-3: Rack Mount Kit



Preventing Electrostatic Discharge (ESD) Damage

Rack Mounting Instructions

1 (Optional) If installing the BLC 6001 chassis in a 23 inch rack, use four 12-24 x.625 pan-pilot screws (two each side) to attach the 23 inch rack mount adapters to the mounting brackets.

Figure 2-4: 23 Inch Rack Mount Adapter Attached to BLC Mounting Brackets

2 Position the chassis in the equipment rack.

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.

Preventing Electrostatic Discharge (ESD) DamageIf the BLC is touched or handled improperly ESD damage to the BLC can occur.

To prevent ESD damage to the BLC, observe the following guidelines:

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.

23 INCH RACKMOUNT

ADAPTOR

12-24 X .625PAN-PILOTSCREWS


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisInserting a Blade Into the BLC 6001 Chassis

Inserting a Blade Into the BLC 6001 Chassis1 Remove the blade from its static-protective packaging.

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.

!

!

!



Connecting the Ground Wire

Connecting the Ground WireWarning: Severe, possibly lethal, voltages can be encountered. Read and follow Appendix A “Safety Warnings and Notices” before proceeding.

The grounding lug is on the rear panel of the BLC 6001 chassis, as shown in Figure 2-5.

Figure 2-5: Grounding Lug on Rear of BLC

1 Assure power is disconnected from the chassis.

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.

3 Replace ground stud nut and tighten.

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisConnecting the Power

Connecting the PowerThese steps describe how to connect the –48V DC power cables to the BLC 6001 chassis and to check for proper supply voltage. The BLC 6001 chassis supports either single or dual redundant power feeds. Both installation options are described below.

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 in the section Configuring Power Alarms in Chapter 36, Alarms and Sensors on page 696.

Note: The BLC 6001 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 left half of the rear panel of the chassis to the right of the Ethernet connectors. There are A and B inputs and returns on dual lug connectors. This chassis should use 18 AWG wire for the power connections. These should be protected by fuse with a circuit breaker rated at 6 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.

The power connection is on the middle of the rear panel of the chassis, as shown in Figure 2-6.

Figure 2-6: BLC 6001 Chassis Power Connection

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.

2 Loosen nuts on the power studs you will use.



Connecting the Power

3 Connect suitable power cable (18 AWG recommended) to the power 48VDC RETURN A studs using an appropriate double hole lug.

4 Replace 48VDC RETURN A stud nuts and tighten.

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.

8 Replace 48VDC RETURN B stud nuts and tighten.

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: 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisConnecting the Alarm/Auxiliary Cable

Connecting the Alarm/Auxiliary CableThe Alarm/Auxiliary Connector attaches to the rear of the BLC. Figure 2-7 shows a connector attached to the rear panel:

Figure 2-7: Alarm/Auxiliary Connector at Rear of BLC

The connectors are identified in Figure 2-8:

Figure 2-8: Alarm/Auxiliary Console Port

1 Locate the supplied 8-pin Molex connector.

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):

Table 2-2: Alarm/Auxiliary Connector Pinout Definition

Alarm/Auxiliary Connection No.

Pinout

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

1 2 3 4 5 6 7 8



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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisConnecting the Subscriber and T1 Interface Cable

Connecting the Subscriber and T1 Interface CableThe subscriber and T1 interfaces are both on four 50-pin female Telco “Champ” connectors which are located on the right side of the rear panel of the BLC 6001 chassis. These connectors conform to industry standard RJ-21X pinout configuration.

Figure 2-9: Champ Connector IDs on Rear of BLC 6001 Chassis

The function/pin-out of these connectors is dependent on the blade installed in the chassis, as shown below in Table 2-3.

Table 2-3: J Connectors on BLC 6000 Blades

Blade Model

J1 J2 J3 J4

6150-01 X T1 (1-4) POTS service for lines 1-24

POTS service for lines 25-48

6151-01 X X POTS service for lines 1-24


6212-02 ADSL2+ service for lines 1-24

ADSL2+ service for lines 25-48

X X

6214 Combined POTS / ADSL2+ signals on lines 1-24

Combined POTS / ADSL2+ signals on lines 25-48

External POTS signals on lines 1-24



Four powered T1 ports

X X

6252-03 X X Combined POTS / ADSL2+ signals on lines 1-24


6440-01 X T1 (1-8) X X

J4 J3

J2 J1



Connecting the Subscriber and T1 Interface Cable

Instructions

1 Attach the champ connector snugly to the rear of the chassis.

2 Screw the champ connector to the BLC.

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 2-10 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 2-10 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 need to insert one or more washers. Please contact Occam Networks if washers are required

Figure 2-10: Champ Connector Screw Length

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.

6640-01 X T1 (1-8) X X

6660-01/ 6660-02/ 6660-03

X T1 (1-8) X X

Blade Model

J1 J2 J3 J4

!

A

B{1/16 inch

SCREW



Figure 2-11: Champ Connector on BLC 6640-01 Chassis with Cable Attached

Figure 2-12: Champ Connector Pin Locations (Chassis Connector)

1 255026

2550

126




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)

Table 2-5: Powered T1 Interface Pinout Definition

Warning: Only trained and qualified personnel should be allowed to work on and handle powered T1 lines.

T1 Port Name Pin Pair (Ring-Tip)

Typical Pinning Colors (Ring-Tip)

1 RX1 1 - 26 Blue - White

TX1 2 - 27 Orange - White

2 RX2 3 - 28 Green - White

TX2 4 - 29 Brown - White

3 RX3 5 - 30 Slate - White

TX3 6 - 31 Blue - Red

4 RX4 7 - 32 Orange - Red

TX4 8 - 33 Green - Red

5 RX5 9 - 34 Brown - Red

TX5 10 - 35 Slate - Red

6 RX6 11 - 36 Blue - Black

TX6 12 - 37 Orange - Black

7 RX7 13 - 38 Green - Black

TX7 14 - 39 Brown - Black

8 RX8 15 - 40 Slate - Black

TX8 16 - 41 Blue - Yellow






TXT2 12 - 37 Orange - Black







Subscriber Pinout Definitions

Table 2-6: Subscriber Interface Pinout Definition

POTS/ADSL Interface

Pin Pair (Ring-Tip) Typical Pinning Colors (Ring-Tip)

1 1 - 26 Blue - White

2 2 - 27 Orange - White

3 3 - 28 Green - White

4 4 - 29 Brown - White

5 5 - 30 Slate - White

6 6 - 31 Blue - Red

7 7 - 32 Orange - Red

8 8 - 33 Green - Red

9 9 - 34 Brown - Red

10 10 - 35 Slate - Red

11 11 - 36 Blue - Black

12 12 - 37 Orange - Black

13 13 - 38 Green - Black

14 14 - 39 Brown - Black

15 15 - 40 Slate - Black

16 16 - 41 Blue - Yellow

17 17 - 42 Orange - Yellow

18 18 - 43 Green - Yellow

19 19 - 44 Brown - Yellow

20 20 - 45 Slate - Yellow

21 21 - 46 Blue - Violet

22 22 - 47 Orange - Violet

23 23 - 48 Green - Violet

24 24 - 49 Brown - Violet

25 (unused) 25 - 50 (unused) Slate - Violet (unused)



Connecting an ADSL Bridge Clip

Connecting an ADSL Bridge ClipThe ADSL bridge clip is attached to the J Connectors which are located on the right side of the rear panel of the BLC 6001 chassis. The subscriber and T1 interface cable is then attached to the bridge clip, as shown in Figure 2-13.

Figure 2-13: Cable Attached to 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisConnecting an ADSL Bridge Clip

ADSL Bridge Clip KitThe ADSL Bridge Clip kit (PN 695254) contains the following items:

1- ADSL Bridge Clip

2- Standoffs, 0.25L,

4- Pan head screws, 4-40x.625

4- Flat #4 washers,.032 thick


1- Nylon cable tie, 5.50L x.13W

Figure 2-14: ADSL Bridge Clip Kit

LONG STANDOFF

ADSL BRIDGE CLIP

SHORT STANDOFFS

PAN HEAD SCREWS

.032" THICKWASHERS

.06" THICKWASHERS



Connecting an ADSL Bridge Clip

Attaching the ADSL Bridge Clip Kit

1 Remove and discard the tie wrap retainers and screws on the “J” connectors. Install the short standoffs in their place.

Figure 2-15: Tie Wrap Retainers

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.

Figure 2-16: Side of ADSL Bridge Clip to Attach to BLC


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisConnecting 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.

Figure 2-17: Attaching DSL Bridge With Washers and Screws

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.

!

ONE OR MORE WASHERS (AS REQUIRED)AND ONE PAN HEAD SCREW WITH

CAPTIVE STAR WASHER IN EACH CORNER OF BRIDGE CLIP



Connecting the Fiber Optic Cables

Connecting the Fiber Optic CablesThe Optical Gigabit Ethernet connections are on the front panel. They are used with small form factor pluggable (SFP) bi-directional laser modules using LC connectors, shown in Figure 2-18.

You can install a SFP module in an port while the BLC is powered on and running. Remember to wear an ESD-preventive wrist strap when doing so as described in the section <Blue><Italic>Preventing Electrostatic Discharge (ESD) Damage. on page 19.

Figure 2-18: Optical Laser Module

Inserting the Module

1 Remove the Optical Laser Module from its protective packaging.

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.

Inserting the Fiber Optic Cable

1 Remove the dust plug from the Optical Laser Module and save it for future use.

2 Remove any protective caps from the fiber optic 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.

!

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisConnecting the 10 GigE Copper Interfaces

Connecting the 10 GigE Copper InterfacesThere are two RJ-45 connectors on the front of the BLC 6314 chassis that support 10 GbE.

Table 2-7 shows the RJ-45 pinout definition for 10 GigE copper interfaces.

Table 2-7: Ethernet Interface RJ-45 Pinout Definition

Pin 10/100T Signal 1000T Signal

1 Tx+ Tx A+

2 Tx- Tx A-

3 Rx+ Rx B+

4 Unused Tx C+

5 Unused Tx C-

6 Rx - Rx B-

7 Unused Rx D+

8 Unused Rx D-



Connecting the 10/100/1000 Base-TX Ethernet

Connecting the 10/100/1000 Base-TX EthernetThere are six RJ45 connectors for 100 Base-TX Ethernet Interfaces on the rear of the chassis. The connector numbers are identified in Figure 2-19.

Figure 2-19: 10/100/1000 Base-TX Ethernet Network Interfaces ID Numbers

Table 2-7 on page 36 shows the RJ-45 pinout definition.

4 6 1 2

53


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisConfiguring the Slot/Shelf ID Selector

Configuring the Slot/Shelf ID SelectorThis section describes how to configure the slot/shelf ID selector on the rear of a BLC 6001 chassis. It is very important to configure this selector to a unique value for each BLC in your network. This information can be read across the network by management stations to identify a specific BLC in a specific BLC 6001 chassis.

The shelf/slot ID selector is implemented on four rotary switches that are located on the middle of the rear panel of the chassis, as shown in Figure 2-20. Use a very small flat-head screwdriver to rotate the switches.

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.

Figure 2-20: Shelf/Slot Selector at Rear of Chassis

The switch numbers are identified in Figure 2-21.

Figure 2-21: Slot/Shelf ID Selector

The slot ID value is configured with dial #1. It is a single-hexadecimal-digit value range from 0-F.

The shelf ID is configured with dials #2-4. It is a three-hexadecimal-digit value range from 000-FFF, allowing you to configure up to 4096 different shelf ID values.

Dial 4 = Shelf ID value 1



Please see Appendix C, Decimal to Hexadecimal Conversion Table on page 857 for a table that converts decimal numbering to hexadecimal numbering.

4 3

2 1



Configuring the Slot/Shelf ID Selector

Each BLC in your network must be configured with a unique slot/shelf ID value.

Configuring Slot/Shelf ID Numbers On a Stack of BLC 6001 Chassis

For a “stack” of co- located BLC 6001 chassis there are two number assignment options.

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

Figure 2-22: Shelf ID Slot A, Shelf 126

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

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8C

D

3

1 2

7B 6AE F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

DIAL 1

DIAL 4 DIAL 3

DIAL 2


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisConfiguring the Slot/Shelf ID Selector

Dial 3 = 0

Dial 4 = 0

Figure 2-23: Shelf ID Slot 1, Shelf 001

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

Figure 2-24: Shelf ID Slot 1, Shelf 002

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

DIAL 1

DIAL 4 DIAL 3

DIAL 2

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8C

D

3

1 2

7B 6AE F

5

9

DIAL 1

DIAL 4 DIAL 3

DIAL 2



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.

5 Visually confirm the 4 round switches match the hexadecimal slot/shelf ID number assigned.

Using the “show version” Command To Verify the Slot/Shelf ID

This blade is in the slot with the ID number "A"which is in the shelf with ID number "126"

occam#show versionOccamOS System V5.5R1 for BLC 6312 [shelf:126, slot:A]Kernel build id V5_5R1, made Fri Feb 17 10:16:43 PST 2008Booter build id 1142849160, made Mon Feb 20 02:29:31 PST 2008

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

Board assembly number is 900118-02, revision number is B2, type is 1Serial number is 10512612, MAC address is 00:02:86:00:4a:93Manufactured by OCCM on 10/21/2007

PLD revision 0.1FPGA revision FPGA_0: 002.000

Hostname occam, uptime is 4 days, 21:03, load average 0.00, 0.00, 0.00occam#


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 2: Installing a BLC 6001 ChassisBLC 6001 Chassis Specifications

BLC 6001 Chassis SpecificationsSlots: One slot, holds a single BLC 6000 system blade

Size: One RU, 1.75 in. (4.45cm) high x 17.0 in. (43.2 cm) wide x 11.75 in (29.9 cm) deep

Rack mounting: Brackets: EIA 23 in. (58.42 cm), EIA 19 in. (48.26 cm)

Weight: 5.5 lbs. (2.5 kg) (including fan module, no blades)

Power connection: -48VDC (-40VDC to -56.7VDC) input, A and B feeds

Alarm connection: Power A and B inputs on Terminal Strip



Introduction

Chapter 30Installing a BLC 6012 Chassis

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Rear Panel of BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Rack Mounting the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Inserting a Blade Into the BLC 6012 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Connecting the Subscriber and T1 Interface Cable. . . . . . . . . . . . . . . . . . . . . . . . . . 64Connecting the 10/100/1000 Base-TX Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Connecting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Configuring the Shelf ID Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74BLC 6012 Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

IntroductionThe 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisIntroduction

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.

BLC 6012i ChassisRelease 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 BLC Blades. Configuration of this chassis is described in Chapter 4, BLC 6012I Chassis Configuration on page 77.



Rear Panel of BLC 6012 Chassis

Rear Panel of BLC 6012 ChassisInterfaces are laid out in a vertical column associated with each slot in the chassis. Figure 3-25 points out the connectors on the rear panel of the BLC 6012 chassis.

Figure 3-25: Rear Panel of BLC 6012 Chassis Rear Panel

Ethernet InterfacesThere are six RJ45 connectors for 10/100/1000-TX Ethernet Interfaces per slot (72 total).

Alarm/AuxiliaryEach slot has an alarm output, alarm input and auxiliary console port on an 8-pin Molex connector.

Connectors for Subscriber Interfaces and T1 PortsThere are four 50-pin Champ connectors per slot (48 total). The function/pin-out of these connectors is dependent on the Blade installed in the chassis. There are

SUBSCRIBERAND T1

"CHAMP"CONNECTORS

ALARM/AUXILIARY

PORTS

ETHERNETPORTS

SHELFSELECTORS

POWERCONNECTORS

GROUND WIRECONNECTOR


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisRear Panel of BLC 6012 Chassis

four 50-pin Champ connectors per slot (48 total). These connectors are not used on the BLC.

Shelf SelectShelf 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.

PowerThe 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.



Site Preparation

Site PreparationProper 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 PreparationMake 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.




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.



PowerMake sure that you have access to the power system and that the system supports the power requirements for the BLC 6012:

Input Voltage Range: -39 to -56 VDC (-48VDC Nominal) typical.

Power consumption rating: 50A watts typical.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisSite Preparation

Network FacilitiesYou 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.




Preparing for InstallationPreventing Electrostatic Discharge (ESD) Damage

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.




Unpacking the BLC 6012 Chassis




shipping list

release notes





!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisRack Mounting the BLC 6012 Chassis



Rack Mounting the BLC 6012 Chassis1 Position the BLC 6012 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.






User Supplied


LC Connector

Power Cable


User supplied

or

PN 695216(Power Wiring Kit with 15 foot A/B dual power (Black) and return (Red) 8 AWG and a 15 foot 8 AWG Ground (Yellow) wires with appropriate dual terminal lugs for attaching to BLC 6012 Chassis)

Power Cable


Ground Cable8 AWG




Connecting the Ground WireThese steps describe how to connect the ground wire to the BLC 6012 chassis and to check for proper ground connection.

Warning: Severe, possibly lethal, voltages can be encountered. Read and follow Appendix A “Safety Warnings and Notices” before proceeding.

The BLC 6012 chassis has a dual terminal lug grounding point above the dual power terminals to attach a ground cable. The grounding lug and dual power terminals come from the factory covered by a clear protection plate.


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.

Figure 3-26: BLC 6012 Ground

3 Remove ground stud nuts.


5 Replace ground stud nuts and tighten.


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.



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisConnecting the Power

Connecting the PowerThese steps describe how to connect the –48V DC power cables to the BLC 6012 chassis and to check for proper supply voltage. The BLC 6012 chassis supports either single or dual redundant power feeds. Both installation options are described below.

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.

Figure 3 -1: BLC 6012 Power Connection



3 Connect a suitable wire power cable (8 AWG minimum) to the power 48VDC RETURN A studs using an appropriate double hole lug.







7 Connect a separate suitable power cable (8 AWG minimum) to the power 48VDC RETURN B studs using an appropriate double hole lug.








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).


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisInserting a Blade Into the BLC 6012 Chassis

Inserting a Blade Into the BLC 6012 Chassis

Warning: When performing the following procedures, wear a grounding wrist strap to avoid ESD damage to the BLC. Ensure that the wrist strap makes good skin contact. The BLC 6012 has an noninsulated banana jack located in the upper right corner of the 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.

1 Remove the blade from its static-protective packaging.


3 Carefully align the blade with the grooves in the BLC 6012 chassis, as shown in Figure 3-27.

Figure 3-27: Inserting Blade in BLC 6012 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 in Figures 3-28 and 3-29.

!




Figure 3-28: Top Lever on Blade in Open Position

Figure 3-29: Bottom Lever on Blade in Open Position

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.!



Figure 3-30: Blade Being Inserted in 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.


Figure 3-31: Levers in Slightly Open Position

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.


!

!



Figure 3-32: Tightening Blade Jack Screws

8 Repeat these steps to insert other blades in the BLC 6012 chassis.




Connecting the Alarm/Auxiliary CableThis section describes how to connect the alarm/auxiliary wires to the rear of the BLC 6012 chassis.

Figure 3-33: Alarm/Auxiliary Connector at Rear of BLC 6012 Chassis

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):



4 Locate the small gauge wires from the alarm distribution panel (in or near the Equipment Rack) for each alarm function required.


Pinout


2 Alarm Out Common


4 Unused

5 Alarm In





BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisConnecting the Alarm/Auxiliary Cable



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).





Attaching an ADSL Bridge Clip

Attaching an ADSL Bridge ClipThe BLC 6212-02 can share lines with the BLC 6150-01 or BLC 6151-01 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-01 or BLC 6151-01. However, if these blades are used with other POTS lines, an external splitter is still required.

ADSL Bridge Clip KitThe ADSL bridge clip kit (PN 695254) contains the following items:

1- ADSL Bridge Clip







LONG STANDOFF

ADSL BRIDGE CLIP

SHORT STANDOFFS

PAN HEAD SCREWS

.032" THICKWASHERS

.06" THICKWASHERS


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisAttaching an ADSL Bridge Clip

Attaching the ADSL Bridge Clip

1 Remove and discard the tie wrap retainers and screws on the “J” connectors. Install the short standoffs (1/4 hex x 1/4 long #4-40) provided in the ADSL bridge clip kit in their place.


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.

!




4 Continue on to the next section for information about how to attach a subscriber/T1 cable to the ADSL bridge clip.

Figure 3-36: Attaching ADSL Bridge Clip With Washers and Screws

Figure 3-37: ADSL Bridge Clip Attached To BLC 6012 Chassis




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisConnecting the Subscriber and T1 Interface Cable

Connecting the Subscriber and T1 Interface CableThe subscriber and T1 interfaces are both on 50-pin female Telco “Champ” connectors which are located on the rear panel of the BLC 6012 chassis. These connectors conform to industry standard RJ-21X pinout configuration. The function/pin-out of these connectors is dependent on the blade installed in the chassis.


Blade Model

J1 J2 J3 J4







X X







X X



6440-01 X T1 (1-8) X X

6640-01 X T1 (1-8) X X

6660-01/ 6660-02/ 6660-03

X T1 (1-8) X X




Figure 3-38: Champ Connectors on BLC 6012 Chassis

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

J4 J2

J1J3

!



need to insert one or more washers. Please contact Occam Networks if washers are required


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.


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.

A B

{

1/16 inch

SCREW




Figure 3-40: BLC 6012 Chassis with Champ Connector Attached

Figure 3-41: BLC 6012 Chassis with Champ Connector Attached to ADSL Bridge Clip

Figure 3-42: Champ Connector Pin Locations

1 2 55 02 6

2 55 0

12 6





This pinout definition conforms to industry standard RJ-48X pinout



Table 3-5: BLC 6246 Powered T1 Interface Pinout Definition





































POTS/ADSL Interface







6 6 - 31 Blue - Red




10 10 - 35 Slate - Red

11 11 - 36 Blue - Black

















Connecting the 10/100/1000 Base-TX Ethernet

Connecting the 10/100/1000 Base-TX EthernetThere are six RJ45 connectors for 100 Base-TX Ethernet interfaces per slot on the rear panel.

The function/pin-out of these connectors is dependent on the blade installed in the chassis. The BLC 6012 supports functionality on ports on interfaces 1 through 6.

These numbers are identified in Figure 3-43

Figure 3-43: 0/100/1000 Base-TX Ethernet Network Interface Numbers

Table 3-7 shows the RJ-45 pinout definition.


Pin 10/100 Base-TX 1000 BaseTX

1 Tx+ Tx A+

2 Tx- Tx A-

3 Rx+ RxB+

4 Unused RxC+

5 Unused RxC-

6 Rx - RxB-

7 Unused RxD+

8 Unused RxD-


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisConnecting the Fiber Optic Cable

Connecting the Fiber Optic CableThe Optical Gigabit Ethernet connections are on the front panel. They are used with small form factor pluggable (SFP) bi-directional laser modules using LC connectors, shown in Figure 3-44.

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.

Remember to wear an ESD-preventive wrist strap when doing so as described in the section <Blue><Italic>Connecting the Ground Wire. on page 51.










4 Route the fiber cable through the cable guide at the top of the BLC 6012 chassis.


!

!

!



Connecting the Fiber Optic Cable



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisConfiguring the Shelf ID Selector

Configuring the Shelf ID SelectorThis section describes how to configure the Shelf ID selector on the rear of a BLC 6012 chassis. It is very important to configure this selector to a unique value for each BLC in your network. This information can be read across the network by management stations to identify a specific BLC blade in a BLC 6012 shelf. It is recommended the combination of Shelf ID be unique across the network. Each BLC 6012 chassis is considered a “shelf” with a unique three-hexadecimal-digit value. Please see Appendix C, Decimal to Hexadecimal Conversion Table on page 857 for a table that converts decimal numbering to hexadecimal numbering.

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.

Figure 3-45: Shelf ID Selector on BLC 6012 Chassis




Figure 3-46 shows an example of how to set shelf ID “C84”:



Configuring the Shelf ID Selector

Figure 3-46: Shelf ID Example

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.

Using the show version Command To Verify the Slot/Shelf ID

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

DIAL 1 DIAL 2 DIAL 3








BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 3: Installing a BLC 6012 ChassisBLC 6012 Specifications

BLC 6012 SpecificationsSlots: Twelve slots, holds up to twelve BLC 6000 system blades

Size: Twelve RU, 21 in. (53.36 cm) high x 21.25 in. (53.99 cm) wide x 11.75 in (29.9 cm) deep

Rack mounting: EIA 23 in. (58.42 cm)

Weight: 35.5 lbs. (16.14 kg) including fan shelf, no blades

Power connection: -48VDC (-40VDC to–56.7VDC) input, A and B feeds

Alarm connection: One input and one output per slot, wire terminal connector


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i Chassis

Introduction

Chapter 40Installing a BLC 6012i Chassis

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Rear Panel of BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Rack Mounting the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Connecting the Ground Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Inserting Blades Into the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Connecting the Alarm/Auxiliary Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Connecting the Subscriber and T1 Interface Cable. . . . . . . . . . . . . . . . . . . . . . . . . . 98Connecting the 10/100/1000 Base-TX Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Connecting the Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Configuring the Shelf ID Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107BLC 6012i Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

IntroductionRelease 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisIntroduction

Figure 4-1: BLC 6012I Chassis Front



Rear Panel of BLC 6012i Chassis

Rear Panel of BLC 6012i ChassisInterfaces are laid out in a vertical column associated with each slot in the chassis. Figure 4-1 points out the connectors on the rear panel of the BLC 6012i chassis.

Figure 4-1: Rear Panel of BLC 6012 Chassis Rear Panel

Connectors for Subscriber Interfaces and T1 PortsThere are four 50-pin Champ connectors per slot (48 total). The function/pin-out of these connectors is dependent on the Blade installed in the chassis. There are four 50-pin Champ connectors per slot (48 total). These connectors are not used on the BLC.

Ethernet InterfacesThere are two RJ45 connectors for 10/100/1000-TX Ethernet Interfaces per slot (12 total).

SUBSCRIBERAND T1

"CHAMP"CONNECTORS

ALARM/AUXILIARY

PORTS

ETHERNETPORTS

SHELFSELECTORS

POWER CONNECTORS

GROUND WIRECONNECTOR


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisRear Panel of BLC 6012i Chassis

Alarm/AuxiliaryEach slot has an alarm output, alarm input and auxiliary console port on an 8-pin Molex connector.

Shelf SelectShelf 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.

PowerThe 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.



Site Preparation

Site PreparationProper 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 PreparationMake 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.




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.



PowerMake sure that you have access to the power system and that the system supports the power requirements for the BLC 6012:

Input Voltage Range: -39 to -56 VDC (-48VDC Nominal) typical.

Power consumption rating: 50A watts typical.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisSite Preparation

Network FacilitiesYou 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.




Preparing for InstallationPreventing Electrostatic Discharge (ESD) Damage

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.




Unpacking the BLC 6012 Chassis




shipping list

release notes





!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisRack Mounting the BLC 6012i Chassis



Rack Mounting the BLC 6012i Chassis1 Position the BLC 6012i 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.






User Supplied


LC Connector

Power Cable


User supplied

or

PN 695216(Power Wiring Kit with 15 foot A/B dual power (Black) and return (Red) 8 AWG and a 15 foot 8 AWG Ground (Yellow) wires with appropriate dual terminal lugs for attaching to BLC 6012i Chassis)

Power Cable


Ground Cable8 AWG




Connecting the Ground WireThese steps describe how to connect the ground wire to the BLC 6012i chassis and to check for proper ground connection.

Warning: Severe, possibly lethal, voltages can be encountered. Read and follow Appendix A “Safety Warnings and Notices” before proceeding.

The BLC 6012i chassis has a dual terminal lug grounding point above the dual power terminals to attach a ground cable. The grounding lug and dual power terminals come from the factory covered by a clear protection plate.


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.

Figure 4-2: BLC 6012i Ground

3 Remove ground stud nuts.


5 Replace ground stud nuts and tighten.


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.



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisConnecting the Power

Connecting the PowerThese steps describe how to connect the –48V DC power cables to the BLC 6012i chassis and to check for proper supply voltage. The BLC 6012i chassis supports either single or dual redundant power feeds. Both installation options are described below.

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.

Figure 4 -2: BLC 6012i Power Connection



3 Connect a suitable wire power cable (8 AWG minimum) to the power 48VDC RETURN A studs using an appropriate double hole lug.







7 Connect a separate suitable power cable (8 AWG minimum) to the power 48VDC RETURN B studs using an appropriate double hole lug.








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).


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisInserting Blades Into the BLC 6012i Chassis

Inserting Blades Into the BLC 6012i Chassis

Warning: When performing the following procedures, wear a grounding wrist strap to avoid ESD damage to the BLC. Ensure that the wrist strap makes good skin contact. The BLC 6012i has an noninsulated banana jack located in the upper right corner of the 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.

1 Remove the blade from its static-protective packaging.


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.

Figure 4-3: Inserting Blade in BLC 6012 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.

Figure 4-4: Top Lever on Blade in Open Position

Figure 4-5: Bottom Lever on Blade in Open Position



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.

Figure 4-6: Blade Being Inserted in 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.


Figure 4-7: Levers in Slightly Open Position

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.


!

!



Figure 4-8: Tightening Blade Jack Screws

8 Verify that the blade in slot 1 is powered.

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.

10 Insert the remaining interior blades.




Connecting the Alarm/Auxiliary CableThis section describes how to connect the alarm/auxiliary wires to the rear of the BLC 6012i chassis.

Figure 4-9: Alarm/Auxiliary Connector at Rear of BLC 6012i Chassis

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):



4 Locate the small gauge wires from the alarm distribution panel (in or near the Equipment Rack) for each alarm function required.


Pinout


2 Alarm Out Common


4 Unused

5 Alarm In





BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisConnecting the Alarm/Auxiliary Cable



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).






Attaching an ADSL Bridge ClipThe BLC 6212-02 can share lines with the BLC 6150-01 or BLC 6151-01 when located in adjacent chassis slots in a BLC 6012i 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-01 or BLC 6151-01. However, if these blades are used with other POTS lines, an external splitter is still required.

ADSL Bridge Clip KitThe ADSL bridge clip kit (PN 695254) contains the following items:

1- ADSL Bridge Clip







LONG STANDOFF

ADSL BRIDGE CLIP

SHORT STANDOFFS

PAN HEAD SCREWS

.032" THICKWASHERS

.06" THICKWASHERS


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisAttaching an ADSL Bridge Clip

Attaching the ADSL Bridge Clip

1 Remove and discard the tie wrap retainers and screws on the “J” connectors. Install the short standoffs (1/4 hex x 1/4 long #4-40) provided in the ADSL bridge clip kit in their place.


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.

!




4 Continue on to the next section for information about how to attach a subscriber/T1 cable to the ADSL bridge clip.

Figure 4-12: Attaching ADSL Bridge Clip With Washers and Screws

Figure 4-13: ADSL Bridge Clip Attached To BLC 6012i Chassis




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisConnecting the Subscriber and T1 Interface Cable

Connecting the Subscriber and T1 Interface CableThe subscriber and T1 interfaces are both on 50-pin female Telco “Champ” connectors which are located on the rear panel of the BLC 6012i chassis. These connectors conform to industry standard RJ-21X pinout configuration. The function/pin-out of these connectors is dependent on the blade installed in the chassis.


Blade Model

J1 J2 J3 J4







X X







X X



6440-01 X T1 (1-8) X X

6640-01 X T1 (1-8) X X

6660-01/ 6660-02/ 6660-03

X T1 (1-8) X X




Figure 4-14: Champ Connectors on BLC 6012i Chassis

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

J4 J2

J1J3

!



need to insert one or more washers. Please contact Occam Networks if washers are required


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.


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.

A B

{

1/16 inch

SCREW




Figure 4-16: BLC 6012i Chassis with Champ Connector Attached

Figure 4-17: BLC 6012i Chassis with Champ Connector Attached to ADSL Bridge Clip

Figure 4-18: Champ Connector Pin Locations

1 2 55 02 6

2 55 0

12 6







Table 4-5: BLC 6246 Powered T1 Interface Pinout Definition



































POTS/ADSL Interface







6 6 - 31 Blue - Red




10 10 - 35 Slate - Red

11 11 - 36 Blue - Black
















BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisConnecting the 10/100/1000 Base-TX Ethernet

Connecting the 10/100/1000 Base-TX EthernetThere are two RJ45 connectors for 100 Base-TX Ethernet interfaces per slot on the rear panel. The function/pin-out of these connectors is dependent on the blade installed in the chassis.

The Ethernet interface numbers are identified in Figure 4-19

Figure 4-19: 10/100/1000 Base-TX Ethernet Network Interface Numbers

Table 4-7 shows the RJ-45 pinout definition.


Pin 10/100 Base-TX 1000 BaseTX

1 Tx+ Tx A+

2 Tx- Tx A-

3 Rx+ RxB+

4 Unused RxC+

5 Unused RxC-

6 Rx - RxB-

7 Unused RxD+

8 Unused RxD-

6

5



Connecting the Fiber Optic Cable

Connecting the Fiber Optic CableThe Optical Gigabit Ethernet connections are on the front panel. They are used with small form factor pluggable (SFP) bi-directional laser modules using LC connectors, shown in Figure 4-20.

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.

Remember to wear an ESD-preventive wrist strap when doing so as described in the section <Blue><Italic>Connecting the Ground Wire. on page 85.










4 Route the fiber cable through the cable guide at the top of the BLC 6012i chassis.


!

!

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisConnecting the Fiber Optic Cable




Configuring the Shelf ID Selector

Configuring the Shelf ID SelectorThis section describes how to configure the Shelf ID selector on the rear of a BLC 6012i chassis. It is very important to configure this selector to a unique value for each BLC in your network. This information can be read across the network by management stations to identify a specific BLC blade in a BLC 6012i shelf. It is recommended the combination of Shelf ID be unique across the network. Each BLC 6012i chassis is considered a “shelf” with a unique three-hexadecimal-digit value. Please see Appendix C, Decimal to Hexadecimal Conversion Table on page 857 for a table that converts decimal numbering to hexadecimal numbering.

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.

Figure 4-21: Shelf ID Selector on BLC 6012i Chassis




Figure 4-22 shows an example of how to set shelf ID “C84”:


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisConfiguring the Shelf ID Selector

Figure 4-22: Shelf ID Example

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.

Using the show version Command To Verify the Slot/Shelf ID

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

0

4

8

CD

3

1 2

7B 6A

E F

5

9

DIAL 1 DIAL 2 DIAL 3









BLC 6012i Specifications

BLC 6012i SpecificationsSlots: Twelve slots, holds up to twelve BLC 6000 system blades

Size: Twelve RU, 21 in. (53.36 cm) high x 21.25 in. (53.99 cm) wide x 11.75 in (29.9 cm) deep

Rack mounting: EIA 23 in. (58.42 cm)

Weight: 35.5 lbs. (16.14 kg) including fan shelf, no blades

Power connection: -48VDC (-40VDC to–56.7VDC) input, A and B feeds

Alarm connection: One input and one output per slot, wire terminal connector


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 4: Installing a BLC 6012i ChassisBLC 6012i Specifications


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 5: BLC 6012i Chassis Configuration

Introduction

Chapter 50BLC 6012i Chassis Configuration

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111BLC 6012 Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Chassis Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112BLC 6012i Chassis Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113BLC 6012 Chassis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Frontpanel Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Installing Blades Into the BLC 6012i Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

IntroductionRelease 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 5: BLC 6012i Chassis ConfigurationChassis Wiring

Chassis WiringThe 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:

Figure 5-1: BLC 6012i Chassis Wiring

Ring Bookend Port Interior Ports Bookend Port

Ring 1 Slot 1, Ethernet port 1

Slot 10, Ethernet ports 1, 2


Slot 12, Ethernet port 1

















12345

6

SLOT1

1 2 1 2

1 2 1 2

1 2 1 2

1 2 1 2

1 2 1 2

6

12345SLOT

2SLOT

3

SLOT4

SLOT5

SLOT6

SLOT7

SLOT8

SLOT9

SLOT10

SLOT11

SLOT12

RING 1

RING 2

RING 3

RING 4

RING 5



BLC 6012i Chassis Terminology

BLC 6012i Chassis TerminologyThe BLC 6012i chassis uses the following terms for ports that reside on the backplane. These terms may be viewed by viewing the “medium” field when CLI “show” commands are entered.

“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.

“copper”: These ports are connected to the 10/100/1000BT connectors on the back of a chassis. Ports 5 and 6 on slots 2-11 are copper ports.

“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

Port Slot 1 Slots 2-11 Slot 12

1 Internal Internal Internal

2 Internal Internal Internal

3 Internal Not connected internally or externally

(Fiber on 6312)

Internal

4 Internal Not connected internally or externally

(Fiber on 6312)

Internal

5 Internal External Copper ports

(Dual portsa on 6312)

a.Fiber or Copper

Internal

6 Internal External Copper ports


Internal


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 5: BLC 6012i Chassis ConfigurationBLC 6012 Chassis Configuration

BLC 6012 Chassis ConfigurationBookend Slots

Connection from a bookend VPT in the BLC 6012i chassis to a router can be accomplished through a optical connection(s) using either Multi-Mode or Single Mode lasers. A Link Aggregation Group (LAG) can be used from each BLC in the bookend slots if they are fiber blades (BLC 6312, BLC 6314 or BLC 6450).

Use a copper SFP (PN 105180) in one of the laser ports (e.g. Port 7), to provide copper connection(s) to a router from a VPT blade for multicast traffic. This copper SFP consumes a single SFP socket; however due to the "head" size of the Ethernet jack any stacked SFP port cannot be used.

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.


BL

C 6000 S

ystem C

onfiguration and Installation Guide- R

elease 5.5Chapter 5: B

LC 6012i C

hassis Configuration

BLC 6012 Chassis Configuration

785553 Rev. 2.0

Proprietary Information - O

ccam N

etworks Inc.

Page 115 of 880

10/09/08

d must be enabled, as described

Medium Admin State

Internal No Shutdown






numpofi

a.N- 62- 66

? No Shutdown

Table 5-2: BLC 6012-I VPT/VPS Slots 1 and 12

Fiber Blades

To configure XG fiber blades (6312, 6314 and 6450) for ring operation the frontpanel commanin the section Frontpanel Mode on page 117.

Port EPS IGMP Ring Profile

Slot 1 Slot 12 Name Passed VLANs

1 PG1 PG2 Host slots10-11 2-122

2 PG1 PG2 Host slots8_9 2-122




6 Ring All (Except if VPT,

then Interconnect)

Ring All (Except if VPT,

then Interconnect)

Passthrough N/A 2-122

Highest bered fiber

rt on non-ber bladea

on-fiber blades are 6150, 6015, 6214,6244, 6246 6440:44 or 6246: Highest numbered port is port 810, 6015, 6214, 6440: Highest numbered port is port 10

Ring All Ring All ? N/A 2-122

BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 5: BLC 6012i Chassis ConfigurationBLC 6012 Chassis Configuration

Interior SlotsOn 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.

Table 5-3: BLC 6012-I VPT/VPS Slots 2 through 11

Port EMS IGMP Medium Admin State

1 Ring All Passthrough Internal NoShutdown

2 Ring All Passthrough Internal NoShutdown

3 None None Mode None(Fiber Mode on BLC 6312)

N/A

4 None None Mode None(Fiber Mode on BLC 6312)

N/A

5 None None Copper


a.Fiber or Copper

Shutdown

6 None None Copper


Shutdown



Frontpanel Mode

Frontpanel ModeFrontpanel 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.

Frontpanel Mode On the 6314 and 6450 Fiber Blades

Bookend Slots

Table 5-4 shows the results of issuing the “frontpanel” command on the 6314 and 6450 fiber blades in the bookend positions of the BLC 6012i chassis.

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.

Frontpanel Mode On the 6312 Fiber Blade

Bookend Slots

Table 5-5 shows the results of issuing the “frontpanel” command on the 6312 fiber blade in the bookend positions of the BLC 6012i chassis.

Port Slot 1 Slot 12

XG1 VPS mode (default): Configured as “ring all”

VPT mode : Configured as “interconnect”

VPS mode (default): Configured as “ring all”


XG2 Ring PG1 Ring PG2

XG4 If the blade is in VPS mode, the XG4 Port will be set to Ring All and “no shut-down”. These settings support configuration of an EPS Ring by installing the XFP laser and appropriate fiber.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 5: BLC 6012i Chassis ConfigurationFrontpanel 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.

Port Slot 1 Slot 12

XG1 VPS mode (default): Configured as “ring all”


VPS mode (default): Configured as “ring all”


XG2 Ring PG1 Ring PG2

6 The medium configuration changes from internal to fiber and port is uncon-figured (shutdown). It is assumed that both bookend blades will be fiber blades and will be connected using the XG1 Ports configured as as Ring All (VPS) or Interconnect (VPT). XG2 10 Gig copper ports provide a 10 Gig subtended ring between the bookend blades in the front wiring mode.

Port Slot 2 -11

1 Fiber

2 Fiber

3 Fiber

4 Fiber

5 Fiber or copper

6 Fiber or copper



Installing Blades Into the BLC 6012i Chassis

Installing Blades Into the BLC 6012i ChassisNote: All blades inserted into the BLC 6012i chassis must operate with OccamOS 5.5 code. Blades inserted into the bookend positions must be at least GigE BLCs.

The installation procedure for this chassis is as follows:

1 Connect power to 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.

4 Insert the remaining interior blades.

Factory Default Blade Configuration In a BLC 6012i ChassisWhen a factory default blade is inserted in a BLC 6012i chassis it will be configured with the correct Ring port parameters. After it has been saved the start-up configuration file will indicate that the blade initiated in a BLC 6012i chassis.

Blades Relocated Into a BLC 6012i ChassisIf a blade that has a previous start-up configuration is relocated into a BLC 6012i chassis, the start-up configuration will be modified to match the blade to its new position. As part of this process, all Ring configurations will be cleared and then ports designated as "internal" (associated with the BLC 6012i chassis slot to slot connections) will be configured to match the BLC 6012i chassis functionality.

The term “internal” is described in the section BLC 6012i Chassis Terminology on page 113.

A blade is considered to be moved if it is placed into a position different than the same slot in a 6012i chassis. Specifically, if a blade was previously in a chassis other


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 5: BLC 6012i Chassis ConfigurationInstalling 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 6: Command-Line Interface (CLI) Basics

Introduction

Chapter 60Command-Line Interface (CLI) Basics

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Basic Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Interface Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Profile Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Service Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Channel Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130QoS Configuration Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Finding Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Issuing Privileged Mode Commands From Other Configuration Modes . . . . . . . . 131Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Undoing a Command or Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Saving Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Erasing Configuration Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

IntroductionThis 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 6: Command-Line Interface (CLI) BasicsBasic Command Modes

Basic Command ModesThe command-line interface has different modes. Each command mode permits you to configure different components on the system.

The command-line interface consists of the following three main modes:

Mode Description Access Method Exit Method

User The User Mode features commands which allow you to change terminal settings, perform basic tests and list system information.

Log in, using the default password “occam”.

After you log in the prompt will change to the host name followed by an angle bracket (>):User Access Verification

Password: occamoccam>

Enter the logout or exit command.

Privileged This mode contains the commands avail-able in User Mode. It also features commands which allow you to configure oper-ating parameters.

Enter the Privileged Mode from User Mode, using the default password word “razor”.

After you enter Privileged Mode the prompt will change to the host name followed by a pound sign (#):occam> enablePassword: razoroccam#

To exit to User Mode, use the disable or logout command.

To enter GlobalConfiguration mode,

use the configureterminal command.

Global Configura-tion

From this mode, you can enter a variety of inter-face and profile configuration modes and make changes to the running configuration.

From Privileged Mode, enter the configure terminal command. After you enter Global Configuration Mode the prompt will change to the host name “Occam” followed by a the word “config” in parenthesis and a pound sign (#). You cannot enter Global Config-uration Mode from User Mode:occam# configure terminaloccam(config)#

To exit to Privileged Mode, enter the exit or end command.Use various commands to enter Interface and Profile modes.



Basic Command Modes

Figure 6-1: Basic Command Modes

Global Configuration ModeOccam(config)#

enabledisable

configureterminal

exit

Login via secureshell or console

exit

exit

Privileged ModeOccam#

User ModeOccam>

Variouscommandoptions


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 6: Command-Line Interface (CLI) BasicsInterface Configuration Modes

Interface Configuration ModesThere are various interface configuration modes available from Global Configuration Mode:


Bridge Virtual Interface (BVI)

From BVI Configuration Mode, you can create a bridge-group virtual interface for management and voice networking.

From Global Configuration Mode, enter the interface bvi command. After you enter BVI Configuration Mode the prompt will change to the host name “Occam” followed by the words “config-if-bvi” in parenthesis and a pound sign (#):occam(config)# interface bvi {BVI-number}occam(config-if-bvi)#

To exit to Global Configura-tion Mode, enter the exit command.

DSL Interface Configuration

From DSL Inter-face Configuration Mode you can configure the DSL interfaces

From Global Configuration Mode, enter the interface dsl command. After you enter BVI Configuration Mode the prompt will change to the host name “Occam” followed by a the words “config-if-dsl” in parenthesis and a pound sign (#):Occam(config)# interface dsl 1Occam(config-if-dsl)#


Ethernet Configuration

From Ethernet Configuration Mode, you can enable Ethernet interfaces to be configured

From Global Configuration Mode, enter the interface ethernet command. After you enter Ethernet Configuration Mode the prompt will change to the host name “Occam” followed by a the words “config-if-eth” in parenthesis and a pound sign (#):Occam(config)# interfaceethernet {n}Occam(config-if-eth)#


Interface Group ConfigurationNote: This command is only available on the BLC 6640/6640-01

From Interface Group Configu-ration Mode, you can configure a Interface Group

From Global Configuration Mode, enter the interface group command. After you enter Interface Group Configura-tion Mode the prompt will change to the host name “Occam” followed by a the words “interface-group” in parenthesis and a pound sign (#):Occam(config)# interface-group{n}Occam(interface-group)#




Interface Configuration Modes

Serial Interface Configuration

From Serial Interface Configuration Mode, you can configure the eight T1 interfaces.

From Global Configuration Mode, enter the interface serial command. After you enter Serial Interface Mode the prompt will change to the host name “Occam” followed by a the words “config-if-serial” in parenthesis and a pound sign (#):Occam(config)# interface serial{1-8}Occam(config-if-serial)#


XG Configuration

From XG Configuration Mode, you can enable XG inter-faces to be configured

From Global Configuration Mode, enter the interface xg command. After you enter XG Configuration Mode the prompt will change to the host name “Occam” followed by a the words “config-if-xg” in parenthesis and a pound sign (#):Occam(config)# interfacexg {n}Occam(config-if-xg)#




BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 6: Command-Line Interface (CLI) BasicsProfile Configuration Modes

Profile Configuration ModesProfile configuration modes are available from Global Configuration Mode.


Access Profile Configuration

Access Profile Configuration Mode allows you to configure an access profile. An access profile is a collection of subscriber management attributes. It can be attached to or removed from services on Ethernet subscriber inter-faces. Changes to the attributes of an access profile are prop-agated to the interfaces to which the service is attached.

To enter Access Profile Configura-tion Mode, enter the access-profile command from Global Configura-tion Mode, specifying an access profile-name. After you enter Access Profile Configuration Mode the prompt will change to the host name followed by a the words “config-access-profile” in paren-thesis and a pound sign (#):occam(config)# access-profileprofile-nameoccam(config-access-profile)#

To exit to Global Config-uration Mode, enter the exit command.

DSL Profile Configuration

DSL Profile Configuration Mode allows you to configure a DSL profile. A DSL profile allows you to configure band-width allocation for multiple interfaces at the same time.

To enter DSL Profile Configuration Mode, enter the dsl-profile command from Global Configura-tion Mode, specifying a dsl profile-name. After you enter DSL profile Configuration Mode the prompt will change to the host name followed by a the words “config-dsl-profile” in parenthesis and a pound sign (#):Occam(config)# dsl-profileprofile-nameOccam(config-dsl-profile)#




Profile Configuration Modes

DS0 Data Cross-Connect Profile ConfigurationThis command is only available on the BLC 6640-01.

From DS0 Data Cross-Connect Profile Configu-ration Mode you can configure a DS0 Cross-Connect profile to attach to a channel in an interface group.

From Global Configuration Mode enter the command subscriber-profile cross-connect data {profileName}. After you enter DS0 Data Cross-Connect Profile Config-uration Mode, the prompt will change to the host name “Occam” followed by the words “config-profile” in parenthesis, the profile name, and a pound sign (#):Occam(config-profile)<profileName>#


DS0 Voice ross-Connect Profile Configuration

From DS0 Voice Cross-Connect Profile Configu-ration Mode you can configure a DS0 Cross-Connect profile to attach to a channel in an interface group.

From Global Configuration Mode enter the command subscriber-profile cross-connect voice {profileName}. After you enterTDS0 Voice Cross-Connect Profile Configuration Mode, the prompt will change to the host name “Occam” followed by the words “config-profile” in parenthesis, the profile name, and a pound sign (#):Occam(config-profile)<profileName>#


GR-303 Profile Configuration

From GR-303 Profile Configu-ration Mode you can configure a GR-303 profile to attach to a channel in an interface group.

From Global Configuration Mode enter the command subscriber-profile tdm gr303 {profileName}. After you enter GR-303 Profile Configuration Mode, the prompt will change to the host name “Occam” followed by the words “config-profile” in parenthesis, the profile name, and a pound sign (#):Occam(config-profile)<profileName>#




BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 6: Command-Line Interface (CLI) BasicsProfile Configuration Modes

Tagged Profile Configuration

Tagged Profile Configuration Mode allows you to configure a tagged profile. A tagged profile maps EPS domain VLANS (2-122) onto a customer switch VLAN domain (1-4094).

To enter Tagged Profile Configura-tion Mode, enter the tagged-profile command from Global Configuration Mode, specifying a tagged profile-name. After you enter Tagged Profile Configuration Mode the prompt will change to the host name followed by a the words “config-tagged-profile” in parenthesis and a pound sign (#):Occam(config# tagged-profile nameOccam(config-tagged-profile)#


TR-08 Profile Configuration

From TR-08 Profile Configu-ration Mode you can configure a TR-08 profile to attach to a channel in an interface group.

From Global Configuration Mode enter the command subscriber-profile tdm tr08 {profileName}. After you enter TR-08 Profile Configuration Mode, the prompt will change to the host name “Occam” followed by the words “config-profile” in parenthesis, the profile name, and a pound sign (#):Occam(config-profile)<profileName>#





Service Configuration Modes

Service Configuration ModesDSL Service Configuration Mode is available from DSL Interface Configuration Mode. Ethernet Service Configuration Mode is available from Ethernet Interface Configuration Mode:


DSL ServiceConfiguration

The DSLService Configuration Mode allows you to configure an DSL Service on an DSL interface. A DSL Service can have an access profile attached to it.

To enter DSL Service Configura-tion Mode, first configure an DSL interface to become a subscriber interface by entering the command eps access subscriber. Next, enter the service command from DSL Interface Configuration Mode, specifying a service number from 1-4. After you enter DSL Service Configuration Mode the prompt will change to the host name followed by a the words “config-if-dsl-service-{1-4}” in parenthesis and a pound sign (#). For example:Occam(config-if-dsl)# service 2Occam(config-if-dsl-service-2)#

To exit to DSL Interface Configuration Mode, enter the exit command.

Ethernet ServiceConfiguration

The Ethernet Service Configu-ration Mode allows you to configure an Ethernet Service on an Ethernet interface. An Ethernet Service can have an access profile attached to it.

To enter Ethernet Service Config-uration Mode, first configure an Ethernet interface to become a subscriber interface by entering the command eps access subscriber. Next, enter the service command from Ethernet Interface Configuration Mode, specifying a service number from 1-5. After you enter Ethernet Service Configuration Mode the prompt will change to the host name followed by a the words “config-if-eth-service-{1-5}” in parenthesis and a pound sign (#). For example:Occam(config-if-eth)# service 2Occam(config-if-eth-service-2)#

To exit to Ethernet Interface Configuration Mode, enter the exit command.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 6: Command-Line Interface (CLI) BasicsChannel Configuration Mode

Channel Configuration ModeThe following mode is available from Interface Group Configuration Mode

Note: This command is only available on the BLC 6640-01.

QoS Configuration ModesThere are three QoS configuration modes available:


Interface Group Channel ConfigurationNote: This command is only available on the BLC 6640-01.

From Interface Group Channel Configura-tion Mode, you can configure a Interface Group Channel

From Interface Group Configura-tion Mode, enter the channel command and pick a channel number between 1-2048 for GR303 IGs, 1-96 for TR08 IGs, 1-192 for cross-connect IGs to configure. After you enter Channel Configuration Mode the prompt will change to the host name “Occam” followed by a the words “interface-group-channel” in parenthesis and a pound sign (#):Occam(interface-group)# channel numberOccam(interface-group-channel)#

To exit to Inter-face Group Configu-ration Mode, enter the exit command.


Policy Map Configuration Mode

Use the Policy Map Configuration Mode to configure or modify a QoS Service Policy Map.

From Global Configuration Mode, enter the policy-map command. After you enter Policy Map Configuration Mode the prompt will change to the host name “Occam” followed by a the words “config-pmap” in parenthesis and a pound sign (#):occam(config)# policy-map nameoccam(config-pmap)#




Finding Command Options

Finding Command OptionsEach command consists of one or more command words, followed by zero or more arguments. Entering a question mark at the system prompt to list all commands available for a particular command mode. The following example shows a sample display of the output from a question mark entered at the Global Configuration Mode prompt:

occam(config)# access-copy-profile Copy an existing Access profile to another profile access-list Add an access list entry access-profile Configure a Access Profile arp Set a static ARP entry clock Configure time-of-day clock do Execute EXEC-level commands enable Set the privileged exec mode password end Exit from configure mode environment Configure the environment monitoring eps Enable and configure Ethernet Protection Switching ethernet Configure Ethernet parameters exit Exit from configure mode hostname Set system's network name http Set HTTP server configuration info Set the user information interface Configure interfaces ip Global IP configuration subcommands load preset base configurations logging Adding syslog destination hosts login Set the user exec mode password no Negate a command or set its defaults ntp Network Time Protocol policy-map Configure a QoS Policy prompt Set the system prompt snmp-server Modify SNMP Parameters subscriber Set global subscriber parameter tagged-profile Configure a tagged VLAN Profile telnet Enable Telnet Mode terminal Set terminal attributes for all sessions unix Set password

Issuing Privileged Mode Commands From Other Configuration Modes

You may issue Privileged Mode from other configuration modes by entering the word “do” in front of the command. For example, you may enter the command show interface ethernet summary from Ethernet Interface Configuration mode by entering the command:

occam(config-if-eth)# do show interface ethernet summaryEthernet Summary Port|EPS |IGMP |Admin|Oper |Fwd |Speed |Rx |Tx |Rx |Tx # |state |state|state|state|state| |pkts |pkts |errs|errs ----|-------- |-----|-----|-----|-----|------|----------|----------|----|---- 1 |ring PG2 |HOST |up |up |FWD |1000 |2236709 |2205698 |0 |0 2 |ring ALL |PASS |up |down |BLK |1000 |0 |25 |0 |0 3 |ring ALL |PASS |up |down |BLK |1000 |0 |25 |0 |0 4 |tagged |HOST |up |down |BLK |1000 |0 |25 |0 |0 5 |vlan 2 |NONE |down |down |BLK |1000 |0 |0 |0 |0 6 |vlan 100 |NONE |up |down |BLK |1000 |0 |0 |0 |0 7 |SUB |HOST |up |up |FWD |1000 |1177 |904915 |0 |0 8 |SUB |NONE |down |down |BLK |1000 |0 |0 |0 |0 9 |SUB |NONE |down |down |BLK |1000 |0 |0 |0 |0 10 |SUB |NONE |down |down |BLK |1000 |0 |0 |0 |0 11 |SUB |NONE |down |down |BLK |1000 |0 |0 |0 |0 12 |SUB |NONE |down |down |BLK |1000 |0 |0 |0 |0<output truncated>


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 6: Command-Line Interface (CLI) BasicsGetting Help

Getting HelpHelp 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

Enter an abbreviated command followed by a space and a question mark (show interfaces?) to obtain a list of commands that begin with a particular character string:occam# show int bvi Bridge-Group Virtual Interface ethernet Ethernet Interface summary Interface status summary xg XG Interface<cr>

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>

Undoing a Command or FeatureIf you want to undo a command you entered or disable a feature, enter the keyword no before most commands; for example, no snmp-server.

Saving Configuration FeaturesMake sure to enter the copy running-config startup-config command to save your configuration changes so the changes are not lost if there is a system reload or power outage. For example:occam# copy running-config startup-configBuilding configuration...

It might take a bit of time to save the configuration to NVRAM.



Erasing Configuration Changes

Erasing Configuration ChangesUse the erase startup-config command from Global Configuration Mode to return the BLC to the factory default configuration. This command clears the contents of the startup configuration file and resets the system.occam(config)# erase startup-config

Warning: Use caution when using this command. It is recommended that you copy the existing configuration to a remote server before erasing the startup configuration file.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 6: Command-Line Interface (CLI) BasicsErasing Configuration Changes


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 7: Initial Configuration Steps

Selecting a Connection Method

Chapter 7Initial Configuration Steps

In This Chapter:Selecting a Connection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Connecting the Console (Craft Interface) Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Remote Connection Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Configuring a Prewired BLC 6012 Chassis With the “load network” Command .141Assigning a Static IP Address to the BLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Configuring System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Configuring Network Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Configuring NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Selecting a Connection MethodYou may connect to the BLC via a console, Secure Shell (SSH) or a Telnet connection. You may have a mximum of 10 total sessions open to a BLC.

Using a DHCP Server to Assign an IP Address to the BLCIf your network uses a DHCP server you do not need to use a console cable to make your initial connection to the BLC. Instead, you may initially connect to the BLC via a SSH or Telnet connection. You will need to know what IP address your DHCP server has assigned to the BLC. Dynamic Host Configuration Protocol (DHCP) is enabled on the BLC by factory default.

Please turn to Remote Connection Methods on page 139 for information about connecting to the BLC via a SSH or Telnet connection.

Manually Assigning a Static IP Address to the BLCIf you wish to manually assign a static IP Address to the BLC, you must initially connect to the BLC via a console connection. After you have configured the BLC with an IP address you may remotely issue CLI commands by establishing a Secure Shell or a Telnet connection from a remote console or workstation.

Please turn to Connecting the Console (Craft Interface) Cable on page 136 for information about connecting to the BLC via a console connection.

Please turn to Assigning a Static IP Address to the BLC on page 146 for information about manually assigning an IP address to the BLC.

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

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsConnecting 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.

Connecting the Console (Craft Interface) CableThe craft interface end of the console cable is a female DB-9 connector which plugs directly into the serial interface of a laptop or desktop computer. Connect the supplied console cable by inserting the RJ-45 modular jack into the interface on the front left corner of the BLC.

Each BLC blade has a console connector that is used to configure just that one BLC blade. For the typical BLC 6012 chassis installation (with multiple BLC blades) you will have to move the direct console cable connector from blade to blade to configure each. This technique is normal during initial configuration (and for some BLC blade failure modes) where there is no usable network connection yet. Typically, after initial configuration BLC blades will be connected together through the network. Remote configuration using Telnet or Secure Shell will make it easier to move from blade to blade.

Console Cable Rating and PinoutThe console cable is Category 5, 24 AWG.

Figure 7-1: DB-9 Female Pin Locations

Figure 7-2: RJ-45 Female Pin Locations

Table 7-1: Pinout definition for the Console Cable

*Pins 1, 4, 6, 7, 8 and 9 are not used

**Pins 1, 2, 4, 7 and 8 are not used

DB-9* RJ-45**

2 (RX) 3 (TX)

3 (TX) 6 (RX)

5 (Gnd) 5 (Gnd)

PIN 1

PIN 1



Connecting the Console (Craft Interface) Cable

Inserting the Console Cable

1 Connect the DB-9 end of the serial cable to the 9-pin serial interface on the PC (typically the COM1 port). Connect the RJ-45 end to the console interface on the front of the BLC blade.

2 Use a terminal application such as Hyperterminal for Windows or Minicom for Linux and Unix to view the console output. The serial settings are shown below in Table 7-2.

Table 7-2: Serial Settings

3 Power ON the BLC

4 As the BLC powers on, it automatically begins a Power On Self-Test (POST) to ensure that the hardware functions properly. After POST is completed, the configuration scripts are accessible by logging in from the console or via ssh or telnet.

Messages appear on your console screen which look similar to the following:

PPCBoot 1.2.0 (Nov 11 2003 - 08:56:35)IBM PowerPC 440 Rev. CBoard: wartortle VCO: 792 MHz CPU: 396 MHz PLB: 132 MHz OPB: 66 MHz EPB: 66 MHz Watchdog enabledLoading FPGA Device 0...

<TEXT EXCLUDED>

The end of the POST script looks similar to the following:Welcome to OCCAMentering runlevel 3INIT: no more processes left in this runlevel................................................CLI Available for login, press <return>

baud rate 9600

data bits 8

parity none

stop bits 1

flow control none

terminal mode autodectectVT-100 is also supported


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsConnecting 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.



Remote Connection Methods

Remote Connection MethodsThe BLC CLI can be remotely accessed through either a SSH or a Telnet session after it has been assigned an IP address. The BLC will attempt to automatically obtain an IP address from a DHCP server. If the BLC is not able to obtain an IP via DHCP you may assign an IP address statically. Please turn to Assigning a Static IP Address to the BLC, on page 146 for information about how do so.

SSH and Telnet are both enabled by default.

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 [email protected]

2 The prompt for the CLI login password will appear. The default password is “occam”:Password: occam

Caution: Occam Networks strongly recommends against using Telnet, as it does not provide secure access. Information such as passwords is sent in clear text, and is thus subject to snooping. In contrast, the SSH protocol encrypts all data which provides very secure access.

Telnet access is enabled by default on the BLC, based on feedback from customers who preferred convenience over security. For adequate security please disable telnet, using the steps detailed below in the section Telnet Connection.

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsRemote Connection Methods

Telnet ConnectionIf 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.

Enabling a Telnet Connection

Use the following steps to connect to the BLC via a telnet connection:

1 Type the command telnet and the IP address at the prompt, where the IP address is the one configured for the BLC. For example:Unix$telnet 123.123.123.123

2 The prompt for the CLI login password will appear. The default password is “occam”:Password: occam



Configuring a Prewired BLC 6012 Chassis With the “load network” Command


Caution: If used, the load network command must be the FIRST configuration 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.

6012G: This configuration is primarily used in a central office. It provides four free copper ports on the BLCs in slots 1 and 12.

6012-P: This configuration is primarily used in a remote terminal. It provides one free copper port on the BLCs in slots 1 and 12.

These prewired chassis automatically configure EPS when the command load network is used. All other BLC networking connections and parameters must be configured. These wiring arrangements are discussed in section Appendix B, BLC 6012 Chassis Wiring Arrangements on page 833.

Type the words “load network” followed by a question mark (?) to display the options that are available for the BLC. The commands are filtered to display the options that are available for the chassis wiring type (6012G, 6012R or 6012P) and blade location in the chassis. The following section, “load network” Commands, on page 143, describes the various load network commands.

1 Connect to the BLC’s CLI from:

a console, as described in the section Connecting the Console (Craft Interface) Cable on page 136,

or via a SSH or a Telnet session as described in the section Remote Connection Methods on page 139.

2 Enter Privileged Mode. The default password for Privileged Mode is “razor”:Occam> enablePassword: razoroccam#

3 Enter Global Configuration Mode:occam# configure terminal

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsConfiguring a Prewired BLC 6012 Chassis With the “load network” Command

4 Enter the command load network, followed by a question-mark to view the configuration templates available for the blade. The commands are filtered to display the options that are available for the chassis wiring type (6012G, 6012R or 6012P) and blade location in the chassis. The following section, “load network” Commands, on page 143 describes these commands and their functions:occam(config)# load network?

5 Choose an appropriate load network command from the list:occam(config)# load network config_file_name

6 Exit Global Configuration Mode:occam(config)# exit

7 Save your configuration by entering the command copy running-config startup-config. This command copies the running configuration to the startup-configuration on the BLC’s flash memory. Occam Networks recommends that you save your configuration frequently to prevent previous configuration steps from being lost if you make a mistake during your system configuration:Occam# copy running-config startup-configBuilding configuration....

8 Use the command show eps to verify configuration and cabling:occam# show eps

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.




“load network” Commands

Commands for FTTx Wiring ConfigurationThe FTTx Wiring configuration is described in Appendix B, BLC 6012 Chassis Wiring Arrangements on page 837.

Configuringa VPT

Configures the BLC in slot 1 to be a VPT on PG1 in a FTTx wiring configuration.

load network 6012F-vpt-slot1

Configures the BLC in slot 12 to be a VPT on PG2 in a FTTx wiring configuration.


Configuringa VPS

Configures the BLC in slot 1 as a VPS in a FTTx wiring configuration.

load network 6012F-vps-slot1

Configures the BLC in slot 12 as a VPS in a FTTx wiring configuration.



BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsConfiguring a Prewired BLC 6012 Chassis With the “load network” Command

Commands for Gateway ConfigurationThe Gateway Wiring configuration is described in Appendix B, BLC 6012 Chassis Wiring Arrangements on page 845.

Configuringa VPT

Configures the BLC in slot 1 to be a VPT on PG1 in a Gateway wiring configuration.

load network 6012G-vpt-slot1



Configuringa VPS

Configures the BLC in slot 1 as a VPS in a Gateway wiring configuration.

load network 6012G-vps-slot1



Configuringan Interior Slot

Configures a BLC in an interior slot (2-11) as a VPS in a Gateway wiring configuration.

load network 6012G-vps

Commands for POTS ConfigurationThe POTS Wiring configuration is described in Appendix B, BLC 6012 Chassis Wiring Arrangements on page 847.

Configuringa VPT

Configures the BLC in slot 1 to be a VPT on PG1 in a POTS wiring configuration.

load network 6012P-vpt-slot1



Configuringa VPS

Configures the BLC in slot 1 as a VPS in a POTS wiring configuration.

load network 6012P-vps-slot1




Configures a BLC in an interior slot (2-11) as a VPS in a POTS wiring configuration.

load network 6012P-vps




Commands for Ring ConfigurationThe Ring Wiring configuration is described in Appendix B, BLC 6012 Chassis Wiring Arrangements on page 854.

Configuringa VPT

Configures the BLC in slot 1 to be a VPT on PG1 in a Ring wiring configuration.

load network 6012R-vpt-slot1



Configuringa VPS

Configures the BLC 2 in slot 1 as a VPS in a Ring wiring configuration.

load network 6012R-vps-slot1

Configures the BLC in slot 12 as a VPS in a Ring wiring configuration.



Configures a BLC in an interior slot (2-11) as a VPS in a Ring wiring configuration.

load network 6012R-vps


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsAssigning a Static IP Address to the BLC

Assigning a Static IP Address to the BLCYou must assign an IP address to the BLC either dynamically, via DHCP, or statically. The BLC automatically will dynamically obtain an IP address via DHCP if you have a DHCP server1. This section describes how to statically assign an 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> enablePassword: razoroccam#

2 Enter Global Configuration Mode:occam# configure terminalEnter configuration commands, one per line. End with CNTL/Z.occam(config)#

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 VLANPlease 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

4 Stop DHCP from attempting to add an IP address:occam(config-if-bvi)# no ip address dhcp

5 Assign an IP address and subnet mask to the bridge group:occam(config-if-bvi)# ip address ip-address subnet-mask

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 commandspecifies how a device that is attached to a BLC obtains it’s own IP address via DHCP.



Assigning a Static IP Address to the BLC

6 Exit out of Bvi Interface Configuration Mode:

occam(config-if-bvi)# exit

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

8 Enable the BVI:occam(config-if-bvi)# no shutdown

9 Exit BVI Configuration Mode:occam(config-if-bvi)# exit

10 Exit Global Configuration Mode and save your configuration:occam(config)# exit

occam# copy running-config startup-configBuilding configuration....

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsConfiguring System Parameters

Configuring System Parameters1 Enter Global Configuration Mode:

occam# configure terminalEnter configuration commands, one per line. End with CNTL/Z.occam(config)#

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

!



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.

Caution: Deleting or changing a hostname that is used by endpoints in Interface Group(s) will interrupt communication between the MG and the TGW and cause the endpoints to become unreachable.

5 (Optional) Associate IP addresses with identifier names, causing the names to become more conveniently entered “aliases” for the addresses:occam(config)# ip host name ip-address

6 (Optional) Attach informational text to the BLC:occam(config)# info key informative-text

For example:

occam(config)# info nextReboot wednesday at 5:00

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>, '?', '!'.



!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsConfiguring Network Security

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



Caution: Occam Networks strongly recommends changing factory default passwords immediately to ensure secure access to your network.!



Configuring NTP

Configuring NTP1 Enter Global Configuration Mode:


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 configuredoccam#

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 ntpStatus: Not synchronizedServers: 10.0.0.57occam#

In the following example a NTP server has been configured and there is a valid status file:occam# show ntpStatus: Synchronized to (10.0.0.57)Servers: 10.0.0.57occam#

5 Save your configuration:occam# copy running-config startup-configBuilding configuration....


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 7: Initial Configuration StepsConfiguring NTP


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 8: Configuring Multihoming

Introduction

Chapter 8Configuring Multihoming

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Configuring a BVI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Configuring a Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Configuring Protocols To Run On a Specific BVI . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Checking the BVI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

IntroductionOccamOS supports multihoming on the following POTS and CES enabled BLCs:

BLC 6150-01

BLC 6151-01

BLC 6252-02, BLC 6252-03

BLC 6440-01

BLC 6660-01, BLC 6660-02, BLC 6660-03

A multihomed device has multiple IP interfaces on different networks. Occam’s multihoming feature uses two IP interfaces. These interfaces are each on a different logical network, defined by unique VLAN ID numbers within the BVI configuration.

POTS and CES enabled BLCs feature a default management BVI and also support the ability to create a dynamic second BVI. You may configure the IP address, subnet mask, and subnet route on either BVI. BVI 1 is the default BVI for all BLC traffic. It is created by the BLC’s system on startup and unlike BVI 2, cannot be deleted. There is only one routing table by default.

Both BVIs support transport of VoIP bearer traffic (RTP, RTCP), SIP signaling and MGCP signaling on unique VoIP VLANs. Management traffic must always run on BVI 1. SIP, MGCP and RTP can either be on BVI 1 with management traffic or be configured to run on BVI 2, on a separate VLAN from management traffic.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 8: Configuring MultihomingIntroduction

Figure 8-1: Multihoming Network Example

RoutingTwo 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.

EPS RING

VOICESERVICES/INTERNET

MGMT

BLC

ROUTER



Introduction

Ingress and Egress Traffic

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.

Ping and Traceroute Commands

A new ping command has been created that will allow you to verify specific IP hosts are reachable. The syntax of this command is:

ping {IP address or host name} [BVI-number]

If you do not specify an interface the ping command will default to BVI 1. If you wish the ICMP packet to exit from BVI 2 you must specify that IP interface in the command. This will cause the BLC to use the source address of BVI 2 and route the ping packets to a destination through the gateways that are configured in the routing table that is associated with BVI 2. Please see the section Using the “ping” Command on page 163 for an example of how to use the ping command.

In addition the traceroute command may be used to trace the route of a packet out of BVI 1 or BVI 2.

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 8: Configuring MultihomingIntroduction

Multihoming Configuration OverviewThis is an overview of the configuration steps required to enable multihoming on a BLC:

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.

Configure a route to a default gateway(s) on the BLC’s network that provide paths to other subnets. You must configure this route either as described in the section Configuring a BVI on page 157 or as described in the section Configuring a Routing Table on page 158

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



Configuring a BVI

Configuring a BVI1 Enter Global Configuration Mode:

Occam# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Occam(config)#

2 Enter BVI Configuration Mode and specify BVI 1 or BVI 2:Occam(config)# interface bvi {1,2}

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}

4 Configure a unique IP address for each BVI

Either enable your DHCP server to give the BVI an address:Occam(config-if-bvi#)# ip address dhcp

OR

Statically enter an IP address and IP subnet mask. Optionally enter a default gateway (router) address:Occam(config-if-bvi#)# ip address {IP-address} {IP subnet mask} [default-gateway-address]

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.

5 Enable the BVI:Occam(config-if-bvi#)# no shutdown

6 Exit BVI Configuration Mode:Occam(config-if-bvi2)# exit

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 8: Configuring MultihomingConfiguring a Routing Table

Configuring a Routing TableThis section describes how to configure a routing table that provides a path to a default gateway that in turn provides a path to other subnets. Configuration for both BVI 1 and BVI 2 are described. You can only install routes if the gateway is reachable.

Configuring a Routing Table For BVI 1You may configure a routing table for BVI 1 by entering commands from Global Configuration mode or from IP Route Table Main Configuration Mode. Both methods are described below.

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.

Entering Commands From Global Configuration Mode


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}

Entering Commands From Global Configuration Mode

1 Enter IP Route Table Main Configuration Mode.Occam(config)# ip route table main

2 Configure a default route, entering the forwarding router's IP address:Occam(config-rtable-main)# 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-rtable-main)# ip route {prefix} {mask} {gateway}



Configuring a Routing Table

4 Exit IP Route Table Main Configuration Mode:Occam(config-rtable-main)# exit

Configuring a Routing Table For BVI 2

1 Enter IP Route Table Policy Configuration Mode:Occam(config)# ip route table policy

2 Configure a default route, entering the forwarding router's IP address:Occam(config-rtable-policy)# 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-rtable-policy)# ip route {prefix} {mask} {gateway}

4 Exit IP Route Table Policy Configuration Mode:Occam(config-rtable-policy)# exit


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 8: Configuring MultihomingConfiguring Protocols To Run On a Specific BVI

Configuring Protocols To Run On a Specific BVIBy default the protocols RTP, MGCP and SIP are bound to BVI 1.

MGCPMGCP 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 ModeOccam(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

RTPConfigure 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.

SIPSIP 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 ModeOccam(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



Checking the BVI Configuration

Checking the BVI ConfigurationYou may check your BVI configuration by using the following commands:

show interfaces bvi, to view the configuration of both BVIs (see below)

show running-config interfaces bvi, to view the running configuration of a BVI (page 162)

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)

ping, to verify specific IP hosts are reachable (page 163)

traceroute, to trace the route to a destination address or hostname out of a BVI 1 or BVI 2 (page 164)

Using the “show interfaces bvi” Command

Use the command show interfaces bvi to view the configuration of both BVIs. Enter a BVI number to view the configuration of one BVI:occam1# show interfaces bvi BVI1/1 is up, line protocol is up Hardware is Bvi Internet address is 192.168.12.41/255.255.255.0 MTU 1500 bytes, BW 100000 KbitEPS Settings: eps access untagged vlan 2 stp access is disabled Last input 0, output 0 1884477 packets input, 142243099 bytes 0 input errors 43613 packets output, 8307298 bytes 0 output errors

BVI1/2 is up, line protocol is up Hardware is Bvi Internet address is 192.168.14.221/255.255.255.0 MTU 1500 bytes, BW 100000 KbitEPS Settings: eps access untagged vlan 14 stp access is disabled Last input 0, output 0 101491 packets input, 5688756 bytes 0 input errors 2670204493 packets output, 3157633538 bytes 0 output errors


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 8: Configuring MultihomingChecking the BVI Configuration

Using the “show running-config interfaces bvi” Command

Use the command show running-config interfaces bvi to view the running configuration of a BVI:occam# show running-config interfaces bvi 2!interface bvi 2 ip address 192.168.14.221 255.255.255.0 eps access untagged vlan 14 no shutdownexit!! Configure RTP Interface!rtp interface bvi 2occam#

Using the “show interfaces bvi binding” Command

The show interfaces bvi binding command shows you which protocols are bound to each IP interface:occam# show interfaces bvi bindingBvi bindings:Bvi 1 bound applications: mgcpBvi 2 bound applications: rtp,sip

Using the “show ip route” Command

The show ip route [policy, main] command shows you the configurations of the main or policy route table. If you do not specify a route table information will be shown for both:

occam# show ip route policy Destination Gateway Proto Dev Table default 192.168.22.1 static bvi2 policy

occam# show ip route Destination Gateway Proto Dev Table default 192.168.22.1 static bvi2 policy 192.168.48.0/24 192.168.21.4 static bvi1 main 192.168.49.0/24 192.168.21.4 static bvi1 main 192.168.41.0/24 192.168.21.4 static bvi1 main default 192.168.21.1 static bvi1 main



Checking the BVI Configuration

Using the “ping” Command

Verify specific IP hosts are reachable by entering the ping command as follows:

ping {IP address or host name} [BVI-number] [COUNT] [SIZE]

The syntax of the command is as follows:

{ip-address or hostname} = Ping destination IP address or host name

[BVI-number] = (Optional) BVI interface number 1 or 2 (default 1)

[COUNT] = Optional) Number of ping packets to send. The range is from 1 to 2147483647. The default is 5.

[SIZE] = Optional) Specifies the datagram size. The range is from 40 to 18024 bytes in each ping. The default is 64 bytes.

The following example:

checks the IP address “192.168.12.41”

sends the request out BVI 2

configures that eight ping packets be sent

specifies that the datagram size is 70 bytes

occam# ping 192.168.12.41 2 8 70PING 192.168.12.41 (192.168.12.41) from 192.168.22.32 bvi2: 70(98) bytes of data.78 bytes from 192.168.12.41: icmp_seq=1 ttl=254 time=2.39 ms78 bytes from 192.168.12.41: icmp_seq=2 ttl=254 time=2.35 ms78 bytes from 192.168.12.41: icmp_seq=3 ttl=254 time=1.74 ms78 bytes from 192.168.12.41: icmp_seq=4 ttl=254 time=2.23 ms78 bytes from 192.168.12.41: icmp_seq=5 ttl=254 time=1.86 ms78 bytes from 192.168.12.41: icmp_seq=6 ttl=254 time=2.35 ms78 bytes from 192.168.12.41: icmp_seq=7 ttl=254 time=1.44 ms78 bytes from 192.168.12.41: icmp_seq=8 ttl=254 time=2.11 ms

--- 192.168.12.41 ping statistics ---8 packets transmitted, 8 received, 0% packet loss, time 7071msrtt min/avg/max/mdev = 1.446/2.064/2.398/0.325 msoccam#


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 8: Configuring MultihomingChecking the BVI Configuration

Using the “traceroute” Command

Traces the route to a destination address or hostname by using the traceroute command as follows:

traceroute {ip-address or hostname} [1-2] [2-20] [yes|no] [1-65535] [0-255]


{ip-address or hostname} = IP address or host name of trace target


[2-20] = (Optional) Seconds to wait for response to probe (default 5)

[1-255] = (Optional) Maximum time to live (TTL) (default 30). This option specifies how many more hops a packet can travel before being discarded or returned.

[yes|no] = (Optional) Address to name lookup

[1-65535] = (Optional) UDP port number (default 33434)

[0-255] = (Optional) TOS field value (default 0)

occam# traceroute 192.168.10.1 2 4 32 yes 33435 1 traceroute to 192.168.10.1 (192.168.10.1) from 192.168.22.32, 32 hops max, 40 byte packets 1 192.168.22.1 (192.168.22.1) 1.714 ms 1.01 ms 1.091 ms 2 gopher (192.168.10.1) 1.762 ms 6.672 ms 1.014 msoccam#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 9: Ethernet Interface Configuration

Ethernet Interface Overview

Chapter 9Ethernet Interface Configuration

In This Chapter:Ethernet Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Speed, Duplex and Media Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Configuring 10/100/1000 Base-TX Ethernet (UTP) Interfaces . . . . . . . . . . . . . . . . 171Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces . . . . . . . . 173Configuring 10 GigE Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Checking Connectivity and Verifying Configuration . . . . . . . . . . . . . . . . . . . . . . . 176

Ethernet Interface OverviewTables 9-1 and 9-2 below describe Ethernet interfaces on Occam’s BLC Family.

The section Speed, Duplex and Media Settings on page 169 describes how to adjust the speed , duplex and media settings on Ethernet interfaces.

The following sections describe how to enable Ethernet interfaces, configure applicable duplex and speed settings and enter informative text about the interface:

Configuring 10/100/1000 Base-TX Ethernet (UTP) Interfaces on page 171

Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces on page 173

Configuring 10 GigE Interfaces on page 175

Table 9-1: Overview of Ethernet Interfaces on BLC Family

BLC Model Number Description of Ethernet Interfaces

BLC 6150-01 BLC Group “A”

BLC 6151-01 BLC Group “B”


BLC 6244 BLC Group “E”

BLC 6246 BLC Group “E”

BLC 6252-02BLC 6252-03

BLC Group “A”

BLC 6312 BLC Group “C”

BLC 6314 BLC Group “D”


BLC 6450 BLC Group “D”


BLC 6660-01/-02/-03 BLC Group “A”


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 9: Ethernet Interface ConfigurationEthernet Interface Overview

Table 9-2: BLC Ethernet Interface Groups Defined

BLC Group “A”The BLC 6150-01, BLC 6212-02, BLC 6252-02, BLC 6252-03, BLC 6440-01, BLC 6640-01, and BLC 6660-01/-02/-03 each have ten Ethernet interfaces: Ethernet interfaces 1 through 6 are 10/100/1000 Base-TX copper interfaces

Ethernet interfaces 7 through 10 are 1000 Base-LX Gigabit Ethernet fiber interfaces. The fiber interfaces are receptacles for small form-factor plug-gable (SFP) optical transceivers.

BLC Group “B”The BLC 6151-01 has two physical 10/100/1000 Base-TX copper interfaces, Ethernet interfaces 1 and 2.



Ethernet Interface Overview

BLC Group “C”The BLC 6312 has: 2 ports of dedicated 10 GigE interfaces.

Interfaces XG 1 and XG 2 are 10Gig copper RJ-45 Ethernet connectors on the front of the chassis. Use the command interface xg {1-2} to enter into 10Gig Interface Configuration Mode. This command is entered from Global Configuration Mode.

22 ports of dedicated GigE Fiber (SFP)

Interfaces 1 through 22 on the front of the chassis are 1000 Base-LX Gigabit Ethernet fiber interfaces. The fiber interfaces are receptacles for small form-factor pluggable (SFP) optical transceivers.

6 ports of 10/100/1000 BaseT Ethernet

Interfaces 1 through 6 on the on RJ45 connectors on the rear of the chassis are 10/100/1000 Base-TX copper interfaces. These interfaces may be used if GigE Fiber (SFP) Ethernet interfaces 1 through 6 are not used on the front of the chassis. The availability of a port is determined by the presence or absence of an SFP fiber module.

Use the command ethernet medium {1-6} {copper l fiber} to configure Ethernet ports 1-6 to be copper or fiber ports. This command is entered from Global Configuration Mode.For example the following command configures port 1 as a fiber port:occam(config)# ethernet medium 1 fiber

The following command configures port 4 as a copper port:occam(config)# ethernet medium 4 copper

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

Individual Fiber/SFP interfaces can be transferred to individual 10/100/1000 BaseT ports. For example, Fiber/SFP interface 1 can be switched to Ethernet 1 on RJ-45 #1, Fiber/SFP 2 can be switched to Ethernet 2 on RJ-45 #2, etc.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 9: Ethernet Interface ConfigurationEthernet Interface Overview

BLC Group “D”The BLC 6314 and 6450 have: Four ports of dedicated 10 GigE interfaces.

Interfaces XG1 and XG2 are 10Gig copper RJ-45 Ethernet connectors on the front of the chassis.

Interfaces XG3 and XG4 are 10GigE XFP connectors on the front of the chassis that support dual fiber XFP lasers. Use the command interface xg {1-4} to enter into 10Gig E Interface Configuration Mode. This command is entered from Global Configuration Mode.

Sixteen ports of dedicated GigE Fiber (SFP)

Interfaces 7 through 22 on the front of the chassis support small form factor pluggable (SFP) laser modules for GigE Fiber.

Six ports of 10/100/1000 BaseT Ethernet

10/100/1000 BaseT Ethernet RJ45 connectors 1 through 6 on the rear of the chassis.

BLC Group “E”The BLC 6244 and BLC 6246 each have eight ports of Gigabit Ethernet: Two connectors 1000BaseLX Gigabit Ethernet fiber (Interfaces 7 and 8) are

on the front of the chassis and support small form factor pluggable (SFP) laser modules for GigE Fiber.

Four external 1000/100/10TX Ethernet ports (Interfaces 1, 2 and 5, 6) are on the rear of chassis)

Two internal 1000/100/10TX Ethernet ports (Interfaces 3, 4) act as a built-in “EPS Key” for VLAN translation.



Speed, Duplex and Media Settings

Speed, Duplex and Media Settings

Speed and Duplex OptionsThe 10/100/1000 Base-TX interfaces have speed and duplex options which are configurable from the CLI. The 1000 Base-LX interfaces only have duplex options.

When attaching a 1000 Base-LX fiber cable to a LX-to-UTP converter, care must be taken not to mix duplex configurations on each side of the converter. Setting one side to full-duplex and the other to half-duplex can result in packet loss and severe performance degradation across the converter. Setting one side to auto and forcing the other side to full or half-duplex results in a non-deterministic state that may not work.

If an Ethernet interface is configured for full-duplex and the UTP on the converter is in half-duplex mode, CRC errors will appear on the BLC interface. The show interfaces ethernet command can be used to view statistics that contain the receive CRC error counter.

If the Ethernet interface is configured for half-duplex and the UTP on the converter is in full-duplex mode, transmit collisions will occur on the BLC Ethernet interface. The appearance of transmit collisions can occur if both the LX and UTP converters are in half-duplex mode, but collisions will occur much more often in a mixed mode configuration.

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 CommandThe 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)

Caution: Occam Networks strongly recommends leaving all Ethernet interfaces speed, duplex and media settings at the default setting of “auto”. Manual configuration is almost never necessary.

!

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 9: Ethernet Interface ConfigurationSpeed, 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.

Using Speed, Duplex and Media CommandsOn instances in which the auto negotiate function fails it is necessary to force all three parameters to match on the link.

For example, on the BLC, you may set the parameters on Ethernet interface 3 as follows:occam(config)# interface ethernet 3occam(config-if-eth)# duplex fulloccam(config-if-eth)# speed 100

occam(config-if-eth)# media straight

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.



Configuring 10/100/1000 Base-TX Ethernet (UTP) Interfaces

Configuring 10/100/1000 Base-TX Ethernet (UTP) Interfaces

Factory Default Values

Table 9-3 shows the factory default Ethernet configuration for the 10/100/1000 Base-TX Ethernet unshielded twisted-pair (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:


2 Enter Ethernet Configuration Mode, specifying an Ethernet interface number:occam(config)# interface ethernet {interface-number}

3 (Optional) Configure the operating speed of the 10/100/1000 Base-TX Ethernet interface. The operating speed is auto negotiated (auto) by default:occam(config-if-eth)# speed {10 | 100 | 1000 | auto}

4 (Optional) Configure the duplex mode of the 10/100/1000 Base-TX Ethernet interface. The duplex mode is auto negotiated (auto) by default:occam(config-if-eth)# duplex {full | half | auto}

5 (Optional) Attach informational text to the Ethernet interface:occam(config-if-eth)# info key informative-text

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>, '?', '!'.

Feature Default Value Command to Modify Default Value

Duplex Mode

Auto negotiated

occam(config-if-eth)# duplex (full | half | auto}

Speed Mode Auto negotiated

occam(config-if-eth)# speed (10 | 100 | 1000 |auto}


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 9: Ethernet Interface ConfigurationConfiguring 10/100/1000 Base-TX Ethernet (UTP) Interfaces

6 Enable the interface, which is shutdown by default:occam(config-if-eth)# no shutdown

7 Exit Ethernet Interface Configuration Mode and return to Global Configuration mode:occam(config-if-eth)# exit

8 To configure the other 10/100/1000 Base-TX Ethernet interface repeat steps 2 through 7.


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-configBuilding configuration....



Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces

Configuring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces

Factory Default Values

Table 9-4 shows the factory default Ethernet configuration for the 1000 Base-LX Ethernet 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:

Caution: When replacing a fiber module on an active (powered up) BLC you should enter the command shutdown, replace the module, and then enter the command no shutdown. Link errors may result otherwise.


2 Enter Ethernet Interface Configuration Mode, specifying an Ethernet interface number:occam(config)# interface ethernet {interface-number}

3 (Optional) Attach informational text to the Ethernet interface:occam(config-if-eth)# info {key informative-text}

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>, '?', '!'.

Feature Default Value Command to Modify Default Value

Duplex Mode: Full occam(config-if-eth)# duplex (full | half | auto}

Speed Mode: 1000 N/A

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 9: Ethernet Interface ConfigurationConfiguring 1000 Base-LX Gigabit Ethernet Optical (Fiber) Interfaces

4 (Optional) Configure the duplex mode of the 10/100/1000 Base-TX Ethernet interface. The duplex mode is auto negotiated (auto) by default:occam(config-if-eth)# duplex {full | half | auto}

5 Enable the interface, which is shutdown by default:occam(config-if-eth)# no shutdown

6 Exit Ethernet Interface Configuration Mode and return to Global Configuration mode:occam(config-if-eth)# exit

7 To configure the other 1000 Base-LX Ethernet interface repeat steps 2 through 7.





Configuring 10 GigE Interfaces

Configuring 10 GigE Interfaces Use the following instructions to configure the 10 GigE Interfaces. Please refer to the Occam Networks publication Command Reference Guide for more information on the commands used in these configuration steps:


2 Enter 10 GigE Interface Configuration Mode, specifying a 10 GigE (XG) Interface by number:occam(config)# interface xg {XG-interface-number}

3 (Optional) Attach informational text to the Ethernet interface:occam(config-if-xg)# info key informative-text

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>, '?', '!'.

5 Enable the interface, which is shutdown by default:occam(config-if-xg)# no shutdown

6 Exit 10 GigE Interface Configuration Mode and return to Global Configuration mode:occam(config-if-xg)# exit

7 To configure the other GigE interface(s) repeat steps 2 through 5, specifying another GigE interface number.


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-configBuilding configuration....


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 9: Ethernet Interface ConfigurationChecking Connectivity and Verifying Configuration

Checking Connectivity and Verifying ConfigurationChecking Connectivity

Use the ping and traceroute commands from Privileged Mode to test connectivity on Ethernet interfaces.

1 Ping a remote host that is located out the interface you want to test:occam# ping ip_address

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 1BVI1/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 KbitEPS 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.



Checking Connectivity and Verifying Configuration

Verifying Your ConfigurationThe following commands may be used to view your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide.

show interfaces ethernet [Ethernet-interface-number] show interfaces xg [XG-interface-number]

Use this command from User and Privileged modes to verify that the speed and duplex modes of the interfaces are configured correctly. If you specify an inter-face number you will receive information about a specific Ethernet interface. If you do not enter an interface number this command output will display infor-mation on all interfaces.

show interfaces ethernet drop-counters [Ethernet-interface-number] show interfaces xg drop-counters [XG-interface-number]

Use this command from User and Privileged modes to display drop counters for the interfaces. If you specify an interface number you will receive the drop counters about a specific Ethernet interface. If you do not enter an interface number this command output will display the drop counters from all interfaces.

show interfaces ethernet errors [Ethernet-interface-number]show interfaces xg drop-counters [XG-interface-number]

Use this command from User and Privileged modes to display error information for the interfaces. If you specify an interface number you will receive the error information about a specific Ethernet interface. If you do not enter an interface number this command output will display the errors from all interfaces.

show interfaces ethernet [Ethernet-interface-number] fiber show interfaces xg [XG-interface-number] fiber

Use this command from User and Privileged modes to view information about the interfaces.

show interfaces ethernet summaryshow interfaces xg summary

Use this command from User and Privileged modes to view statistics for all inter-faces in a summarized format.

show interfaces ethernet rates [Ethernet-interface-number]show interfaces xg rates [XG-interface-number]

Use this command from User and Privileged modes to view transmit and receive


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 9: Ethernet Interface ConfigurationChecking 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.

show interfaces ethernet max rates [Ethernet-interface-number]show interfaces xg max rates [Ethernet-interface-number]

Use this command from User and Privileged modes to view maximum transmit and receive rates. If you specify an interface number you will receive informa-tion about a specific Ethernet interface. If you do not enter an interface number this command output will display information on all Ethernet interfaces. Use the command clear ethernet rates to reset Ethernet maximum rate counters.

show running-config interfaces xg {XG-interface-number}show running-config interfaces ethernet {Ethernet-interface-number}

Use this command from Privileged mode to display information about an inter-face in the running configuration.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 10: Ethernet Protection Switching (EPS) Overview

Introduction

Chapter 10Ethernet Protection Switching (EPS) Overview

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179EPS Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180EPS Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Ethernet Interfaces on VPSs and VPTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192MAC Address Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193QoS Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Subtended Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194EPS Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Ethernet Loop Detection (ELD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Adding a VPS To an Active Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Adding a VPS To an Active Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

IntroductionEthernet 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 9, Ethernet Interface Configuration on page 165 provides information about how to configure speed and duplex settings on Ethernet interfaces.

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.

Chapter 14, Ethernet Subscriber Interfaces on page 281 provides information about how to configure Ethernet fiber interfaces can serve as subscriber facing interfaces.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 10: Ethernet Protection Switching (EPS) OverviewEPS Overview

EPS OverviewEPS 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).

VPSs and VPTsAn EPS network has BLC systems operating as VLAN Path Selectors (VPSs) and VPTs.

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.

Failure Detection Using “Heartbeats”Failover and redundancy capabilities are provided by the ability of the VPSs on the EPS ring to change path groups and communicate with the other VPT. Each VPT sends a “heartbeat” every 10ms on the VLAN path group that it is configured for (Path Group 1 or Path Group 2). These heartbeats travel around the ring and terminate at the other VPT. Each Path Group can only have one VPT.

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.



EPS Overview

How Heartbeats are Received and Passed on By VPSs

The VPSs on the EPS ring use the arrival of the heartbeats from the VPTs to determine if the path is intact. The VPSs will monitor the heartbeats from both VPTs, but only send traffic to the VPT that is associated with their path group preference (set in the CLI).

If the VPS does not receive the heartbeat from the VPT on its preferred path group it will change path groups and communicate with the other VPT. This enables the EPS ring to tolerate the loss of a link, forwarding VPS or VPT. After a failure a path group is monitored and is reverted to after a period of 120 seconds. This is called the hysteresis period. The hysteresis period may not be configured.

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.



Figure 10-1: Simple EPS Loop Topology Network Diagram

PG2

VIDEOHEADEND

CLASS 5SWITCH VOICE

VPS VPS

BLC 6012

ISP ROUTER

VPS VPS

BLC 6012

BLC 6012

VPT

1

PG1

PG2

VPS VPS

BLC 6012

PG1

PG2

VPT

2



EPS Overview

VLAN IDsThe 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.

Figure 10-2: IEEE 802.1q Standard Tag On an Ethernet Packet

VLAN NumberingEach 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.

VLAN 3 – Video Multicast: Occam Networks recommends that VLAN 3 be config-ured for video multicast traffic.

VLAN 4 – Data: VLAN 4 is recommended for data management

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.

VLAN 6 - Video Unicast and Broadcast: Occam Networks recommends that VLAN 6 be configured for video unicast and broadcast traffic.

Dest Address Source Address Tag Type Data FCS

8 1 0 0 0-7 0 1-4094(BLC supports 2-122)

“802.1q” format Priority VLAN ID



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.



EPS Keys

EPS KeysAn 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.

Table 10-1: BLCs EPS Key Table

Internal EPS Key

An internal EPS key requires no additional hardware. Use the command eps key reserve to configure an internal EPS Key.

Enter the commandoccam(config)# eps key reserve 3-4

to reserve ports 3 and 4 as an internal EPS key.

BLC Model Number Description of Ethernet Interfaces

BLC 6150-01 Requires an internal EPS Key

BLC 6151-01 EPS Key never used


BLC 6214 Requires an internal EPS Key

BLC 6244 Requires an internal EPS Key for a second tagged port (not needed for first tagged port on BLC)

BLC 6246 Requires an internal EPS Key for a second tagged port (not needed for first tagged port on BLC)

BLC 6252-02, BLC 6252-03

Requires an internal EPS Key

BLC 6312 No EPS Key required

BLC 6314 No EPS Key required



BLC 6660-01/-02/-03 Requires an internal EPS Key


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 10: Ethernet Protection Switching (EPS) OverviewEPS Keys

OR

Enter the command (except on the BLC 6244 or BLC 6246)occam(config)# eps key reserve 7-8

to reserve ports 7 and 8 as an internal EPS key.

After the internal EPS Key has been configured, continue with your configuration.



Ethernet Interfaces on VPSs and VPTs

Ethernet Interfaces on VPSs and VPTsVPT Interfaces on EPS Rings

A VPT is constructed using two BLCs interconnected by one Ethernet port. One VPT is configured as Path Group 1 (PG1). The other is configured as PG2. Interfaces on the VPTs either connect to each other or to the path group.

VPT Interconnect Interfaces

Use the Ethernet Interface Configuration command “eps ring interconnect” on VPT aggregation or access ring interconnect interfaces. In Figure 10-3 these are the interfaces identified as “A”.

These interfaces will be typically configured as IGMP proxy passthrough interfaces. All multicast traffic received on a passthrough interface will be forwarded out all other passthrough interfaces and all router interfaces. Please refer to Chapter 23, Managed Multicast Via IGMP Proxy on page 479 for more information about this command

VPT Ring Interfaces

Use the Ethernet Interface Configuration command “eps ring pg1” or “eps ring pg2” on VPT aggregation or access ring interfaces. In Figure 10-3 interface “B” carries the “heartbeat” packet on Path Group 1 out from VPT 1 toward VPS 2 and configured with the commnd “eps ring pg1”. Interface “C” carries the “heartbeat” packet on Path Group 1 out from VPT 2 toward VPS 6 and configured with the commnd “eps ring pg2”.

These interfaces will be typically configured as IGMP proxy host interfaces, pruning 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.

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 10: Ethernet Protection Switching (EPS) OverviewEthernet Interfaces on VPSs and VPTs

VPS Interfaces on EPS RingsUse the Ethernet Interface Configuration command “eps ring all” on VPS aggregation or access ring interfaces. All packets with any VLAN ID are transmitted on ports configured with this command. In Figure 10-3 these are the interfaces identified as “D”.

These interfaces will also be typically configured as IGMP proxy passthrough interfaces.

Figure 10-3: EPS VPT, VPS Ring Commands

PG2

BLC 6012 BLC 6012

BLC 6012

VPS

1

VPT

1

PG1

BLC 6012

PG1

PG2

VPT

2

A A

B C

D D D

D

D D D D

D

D D DVPS

2

VPS

3

VPS

4

VPS

5

VPS

6




EPS Tagged and Untagged InterfacesThe 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.

Ports can be configured as tagged or untagged interfaces. Any interface can be configured as an untagged interface, but tagged interfaces are limited to the Ethernet ports. Tagged and untagged interfaces do not necessarily need to be attached to the VPSs; they may be attached to a VPT on this ring or to another ring on the EPS network.

Use EPS Access commands from Ethernet Interface and 10 GigE Interface Configuration modes and MLPPP Interface Configuration mode to configure 802.1q VLAN ID for tagged and untagged and interfaces and the 802.1q-in-q VLAN ID tag for Transparent LAN Services (TLS).

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

Tagged Interfaces and Tagged Profiles

The command eps access tagged {tagged-profile} configures a 802.1q VLAN ID for tagged interfaces that are not part of a ring.

Tagged Ethernet interfaces use Tagged Profiles to either limit the number of VLANs on a tagged interface or to define the mapping between EPS domain VLANs and customer switch VLANs, including only those VLANs which are required by the customer. Once a tagged profile has been defined it may be applied to one or more interfaces. If the interface in which the tagged packet entered does have a tagged profile that specifies the packet's VLAN ID tag, the BLC will drop the packet.

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 10: Ethernet Protection Switching (EPS) OverviewEthernet Interfaces on VPSs and VPTs

Double Q Tagged Interfaces (TLS)

The command eps access doubleqtag vlan {VLAN-ID-number} configures a 802.1q-in-q VLAN ID for Transparent LAN Services (TLS). TLS is also known as “Double Q Tagging, “VLAN stacking” and “Q-in-Q”. It enables service providers to use a single VLAN to support customers who have multiple VLANs by preserving VLAN IDs and keeping traffic in different customer VLANs segregated. Each TLS customer on an EPS domain consumes a single EPS VLAN.

TLS transparently transports 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 6252-02, BLC 6252-03

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:

Ingress/egress rate limiting per VLAN and per port

MAC limits per VLAN

Static MACs per VLAN

DHCP Relay

IGMP Proxy

Access Control Lists (ACLs) (Layer 2/Layer 3 including static IP provisioning)

An option to prevent Layer 2 Peer-to-Peer connections directly between subscriber ports.




Configuration of EPS subscriber interfaces is described in Chapter 14, Ethernet Subscriber Interfaces on page 281.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 10: Ethernet Protection Switching (EPS) OverviewRate Limiting

Rate LimitingSystem 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.

Rate Limiting VLANs on the BLC 6312The BLC 6312 provides the ability to rate limit VLANs as well as Ethernet interfaces. VLANs may be rate limited in increments of 64 Kbps.

There is no system check to ensure that the sum of VLAN rates do not exceed the port rate. If the provider wants to oversubscribe the port rate, that should be allowed, in which case the sum of VLAN rates would be higher than the port rate.

Information about how to configure rate limiting on a VLAN is described in Chapter 14, Ethernet Subscriber Interfaces on page 281.



MAC Address Forwarding

MAC Address ForwardingDuring the MAC address forwarding process, the VPTs translate between path groups. The VPTs discard traffic received on EPS path interfaces not associated with their group.

However on the interconnect interface, the VPT untags the traffic destined for the other path group, sends it across the interconnect link and retags it with the new PG.

When the MAC forwarding process is complete, the MAC forwarding table of each VPS contains two entries for every known MAC address, one for each path group. The internal MAC table contains three fields: the MAC address, the VLAN linked to that address, and the port number to reach that address. The VPTs have similar MAC tables.

After a period of 3-7 minutes, the entries not associated with current path group of the VPS time out, as they are not refreshed with traffic. This is because the VPS will only forward traffic to entries on its path group. If a new client joins the ring, the broadcast is sent out again in all directions and one of the two entries eventually ages out.

A VPS network switches path groups if a heartbeat is not received for their preferred path group. When the switchover occurs, the VPS immediately generates a “gratuitous ARP” reply on the functioning path group. This allows the other ring members know that it is now reachable on the new path group and serves to minimize the impact on voice traffic (since most voice traffic is originated on the local VPS). After its own MAC is broadcast, the VPS searches the MAC forwarding table for MAC addresses associated with subscriber connections and broadcasts them on the new path group.

Limiting MAC AddressesThe number of MAC addresses that can be learned or programmed statically on a given Ethernet interface is limited to a user-configured number. MAC address limits are on a per VLAN basis. The sum of limits in multiple services associated with that interface defines the interface's MAC limit. Each VLAN may have up to sixty-four MAC addresses, including dynamic and static. The factory default is four MAC addresses.

Information about how use the mac limit command to limit the number of MAC address on a VLAN is described in Chapter 22, IP Security Management (IPSM) in the section Associations on page 442 and in Chapter 14, Ethernet Subscriber Interfaces on page 281.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 10: Ethernet Protection Switching (EPS) OverviewQoS Mapping

QoS MappingEPS 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.

Table 10-2: QoS Priority Queues

Since the VPT uses untagged ports to perform VLAN translations that allow peer-to-peer connectivity across the ring, DSCP TOS bits are used to re-map the priorities in the translation. To maintain network wide consistency, DSCP configuration should be homogeneous.

Subtended RingsYou may configure your EPS network with one or more subtended agggregation and access rings.

Subtended Aggregation Ring Configuration

Information about how to configure a subtended aggregation ring off of an aggregation is described in the section Configuring a VPS Interface on a Subtended Aggregation Ring, in Chapter 11, Configuring an EPS Aggregation Ring Network on page 216.

Subtended Access Ring Configuration

Information about how to use Ethernet links to configure a subtended access ring off of an aggregation ring is described in the section Configuring a VPS Interface on a Subtended Aggregation Ring, in Chapter 11, Configuring an EPS Aggregation Ring Network on page 216.

Information about how to use Ethernet links to configure a subtended access ring off of an access ring is described in Chapter 12, Configuring Subtended EPS Access-Rings with Ethernet Links on page 243.

TRAFFIC CLASS 802.1P Gal48370 Priority Queue

TC_NETWORK_CONTROL 7* HIGH

TC_INTERACTIVE 6 HIGH

TC_INTERACTIVE 5* HIGH

TC_BETTER_EFFORT 4 HIGH

TC_BETTER_EFFORT 3* LOW

TC_BEST_EFFORT 2 LOW

TC_BEST_EFFORT 1 LOW

TC_BEST_EFFORT 0* LOW



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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 10: Ethernet Protection Switching (EPS) OverviewEPS Alarms

EPS AlarmsEPS 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.

EPS Failover AlarmAn alarm will be generated when an EPS device fails over from its preferred path group. Upon reversion, the alarm will be cleared. The attributes for this alarm are as follows:

Severity code: Major

Severity category: Non Service Affecting (NSA)

State: Active, Inactive (cleared)

Timestamp: when the alarm was created

ClearedTimestamp: when the alarm was cleared (valid for cleared alarms only)

Description: EPS failover occurred, operating on path-group X (where X is the opposite of the path-group preference).

Opposite Path Group AlarmThe command alarm opposite-path-group enables an alarm that will indicate when the alternate Path Group (PG) to the preferred PG has failed, providing information in the event that network resilience is jeopardized. This command is entered from EPS Configuration Mode. Use the no form of the command to disable the alarm

In this example EPS Configuration Mode is entered and the opposite path group alarm is enabled. PG 1 is the preferred PG and PG 2 fails:occam(config)# epsoccam(config-eps)# alarm opposite-path-group

occam(config-eps)#Jan 9, 2008 6:49:38 PM

com.occamnetworks.mgmt.impl.eps.EpsCardMonitor

SEVERE: EPS clear - Path group: 2 Ring: 0

EPS DITW AlarmAn alarm will be generated when an EPS device fails to detect heartbeats on any path group. This is the "Dead In The Water" (DITW) alarm. If an EPS device is DITW, it will immediately join the first path group it detects a heartbeat on. By default, it is always checking for heartbeats on both path groups. The DITW alarm will be cleared when a heartbeat is detected on either path group allowing EPS operations to continue.



EPS Alarms

Severity code: Critical

Severity category: Service Affecting (SA)


Timestamp: when the alarm was created


Description: EPS failure, no heartbeats detected on any path group.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 10: Ethernet Protection Switching (EPS) OverviewEthernet Loop Detection (ELD)

Ethernet Loop Detection (ELD)ELD reduces the occurrence of network outages caused by accidentally configuring or cabling Ethernet interfaces in such a way that cause network loops. ELD will block an interface from entering the forwarding state if it senses that a loop has been created. When an interface is administratively enabled or after certain configuration changes the interface is transitioned to a disabled state and then re-enabled in order to activate the loop detection.

ELD operates on the following types of Ethernet interface configurations:

EPS Ring interfaces (All, PG1, PG2)

EPS Access Untagged interfaces with the default of untagged VLAN 2

Note: The BLC 6151-01 does not support ELD.

Information about how to configure a ELD is described in Chapter 11, Configuring an EPS Aggregation Ring Network in the section Ethernet Loop Detection (ELD) Configuration on page 236.

Adding a VPS To an Active RingTo add a VPS to an active ring, simply:

power up and configure the BLC to be a VPS.

unplug Ethernet interfaces from VPSs on the ring (if they are interfaces that are presently configured to participate in the ring)

connect these Ethernet ports to the new VPS

The path group that is affected will be brought down only for the period of time between unplugging and reconnecting the interfaces. During this time EPS traffic will fail to the alternate path group.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring Network

Introduction

Chapter 11Configuring an EPS Aggregation Ring Network

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Configuring an Access-Ring Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Configuring a Ring Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Configuring BLCs On an Aggregation Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Configuring an Interconnect on a VPT on an Aggregation Ring . . . . . . . . . . . . . . 210Configuring a VPT Ethernet Interface as a Path Group Participant . . . . . . . . . . . 212Configuring a VPS Interface on an Aggregation Ring . . . . . . . . . . . . . . . . . . . . . . 214Configuring a VPS Interface on a Subtended Aggregation Ring. . . . . . . . . . . . . . 216Configuring an Access-Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Configuring a VPS or VPT Ethernet Interface for Untagged Traffic . . . . . . . . . . . 225Configuring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic . . . . . . . . 226Configuring TLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Configuring a BLC to Run EPS with Non-EPS Devices . . . . . . . . . . . . . . . . . . . . . . 235Ethernet Loop Detection (ELD) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Displaying Information About Your EPS Configuration . . . . . . . . . . . . . . . . . . . . . 239

IntroductionEPS Configuration

This chapter describes how to configure an EPS Aggregation Ring network.



Chapter 10, Ethernet Protection Switching (EPS) Overview on page 179 provides an overview of EPS.




Chapter 14, Ethernet Subscriber Interfaces on page 281 provides information


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkIntroduction

about how to configure Ethernet fiber interfaces can serve as subscriber facing interfaces.

EPS Aggregation ServicesEPS Aggregation Services are based on a form of ring-to-ring bridging. Figure 11-1 shows an example of a simple EPS aggregation ring network. This diagram shows one EPS aggregation ring and two EPS access rings.

Note: Enabling/disabling aggregation mode will reset all external ports to the default EPS configuration.

Figure 11-1: EPS Aggregation Ring Network Overview

The BLCs on both access-ring 1 (west-salem) and access-ring 2 (east-salem) use VLAN 2 for voice, VLAN 3 for video and VLAN 4 for data.

VPS 1 and VPS 2 have access-ring profile “west-salem” associated with them.

6450 VPS 3

BLC 6

BLC 5

6450 VPS1

6450 VPS 2BLC 2

BLC 1

AGGREGATIONRING

ACCESSRING 1

(WEST-SALEM)

BLC 3

ACCESSRING 2

(EAST-SALEM)

ROUTER

BLC 4

IP VIDEOHEAD-END VoD

SERVER

INTERNET MIDDLEWARE/DHCP SERVER

6450 VPT 1 6450 VPT 2

6450 VPS 4



Introduction

This profile translates the VLANs on Access-Ring 1 as follows:

Note: Typically the management VLAN 2 will not be mapped to another aggregation VLAN. VLAN 3 is dedicated to managed multicast traffic and cannot be translated. Occam Networks recommends that STBs be placed on VLAN 6. The STBs will obtain their address via DHCP on VLAN 6 but when they issue an IGMP request the multicast traffic will automatically be placed on VLAN 3.

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.

Access Ring VLAN # Aggregation-Ring VLAN #

2 2

3 3

4 401

6 601


2 2

3 3

4 402

6 602



Figure 11-2: EPS Aggregation Ring with Subtended Aggregation Ring

6450 VPS 1

MAINAGGREGATION

RING

ACCESSRING 2

(WEST-MIDWAY)

ACCESSRING 3

(EAST-MIDWAY)

ROUTER

IP VIDEOHEAD-END VoD

SERVER

INTERNET MIDDLEWARE/DHCP SERVER

6450 VPT 1 6450 VPT 2

SUBTENDEDAGGREGATION

RING A(WEST)


RING B(EAST)

ACCESSRING 4

(EAST-SALEM)

ACCESSRING 1

(Access-RingProfile

"WEST-SALEM")

BLC 2BLC 1

BLC 3

BLC 4

BLC 5

BLC 6BLC 7

BLC 8

BLC 9

BLC 10

BLC 11

BLC 12

6450 VPS 2 6450 VPS 3

6450 VPS 4

6450 VPS 5

6450 VPS 6

6450 VPS 76450 VPS 8

6450 VPS 9

6450 VPS 10

6450 VPS 11

6450 VPS 12



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:


2 2

3 3

4 401

6 601


2 2

3 3

4 402

6 602


2 2

3 3

4 403

6 603



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:

Subtended Aggregation-Ring A (“west”)

VPS 1 and VPS 2 on subtended aggregation ring A have ring profile “west” associated with them. This ring profile only allows the following VLANs to pass though them:

Subtended Aggregation-Ring B (“east”)

VPS 3 and VPS 4 on subtended aggregation ring B have ring profile “east” associated with them. This ring profile only allows the following VLANs to pass though them:


2 2

3 3

4 404

6 604

VLANs # Allowed Access-Ring Association

2 Management and Multicast VLANs for Access-Ring 1 (“west-salem”)

and Access-Ring 2 (“west-midway”)

3

401 Access-Ring 1 (“west-salem”)

601

402 Access-Ring 2 (“west-midway”)

602

VLANs # Allowed Access-Ring Association

2 Management and Multicast VLANs for Access-Ring 3 (“east-salem”)

and Access-Ring 2 (“east-midway”)

3

403 Access-Ring 14 (“east-salem”)

603

404 Access-Ring 2 (“east-midway”)

604



Configuring an Access-Ring Profile

Configuring an Access-Ring ProfileSubtended access rings support a subset of aggregation VLANs through access-ring profile configuration. Access-ring profiles segregate VLANs on access-rings, hiding traffic and MAC addresses and allowing only the traffic required for the operation of that ring will be seen on that ring.


2 Enter Access-Ring Profile Configuration Mode and create an Access-Ring Profile with a specific name:occam(config)# access-ring-profile {profile-name}

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

4 Enter two VLAN numbers.

the first VLAN number is the VLAN ID on the aggregation ring.

the second VLAN number is the VLAN ID on the access-ring.

Repeat this command as many times as necessary, once for each VLAN conversion.occam(config-access-ring-profile)# vlan {VLAN-number} {VLAN-number}

For example, for access-ring profile “west-salem” the commands should be as follows:occam(config-access-ring-profile)# vlan 2 2occam(config-access-ring-profile)# vlan 3 3occam(config-access-ring-profile)# vlan 401 4occam(config-access-ring-profile)# vlan 601 6

5 View your Access-Ring Profile Configuration to confirm your configuration:occam(config-access-ring-profile)# do show access-ring-profile {profile-name}


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring 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 4601 6 occam#

6 Exit Access-Ring Profile Configuration Mode:occam(config-access-ring-profile)# exit



Configuring a Ring Profile

Configuring a Ring Profile1 Enter Global Configuration Mode:


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 2occam(config-ring-profile)# allow 3occam(config-ring-profile)# allow 401occam(config-ring-profile)# allow 402occam(config-ring-profile)# allow 601occam(config-ring-profile)# allow 602

5 View your Ring Profile Configuration to confirm your configuration:

occam(config-ring-profile)# do show ring-profile {profile-name}

6 For example, to view Ring Profile “west”, enter the following command:occam(config-ring-profile)# do show ring-profile westring-profile west:eps vlan23401402601602occam(config-ring-profile)#

7 Exit Ring Profile Configuration Mode:occam(config-ring-profile)# exit


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring BLCs On an Aggregation Ring

Configuring BLCs On an Aggregation RingThis section describes how to configure a VPT and a VPS on an aggregation ring.

Figure 11-3: Aggregation Ring

Configuring a BLC as a VPT on an Aggregation Ring


2 Enter EPS Configuration Mode:occam(config)# eps

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

4 Enable aggregation mode on the VPT:occam(config-eps)# aggregation

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

6450 VPT 1

6450 VPT 2

6450 VPS 1

6450 VPS 2

6450 VPS 3

6450 VPS 4

6450 VPS 5

6450 VPS 6



Configuring BLCs On an Aggregation Ring

Note: This command must be entered on BOTH VPTs .

Note: Configuration changes do not take effect until after exiting EPS Configuration Mode.

6 Exit EPS Configuration Mode:occam(config-eps)# exit

Configuring a BLC as a VPS on an Aggregation Ring



3 Configure the EPS mode as VPS:occam(config-eps)# mode vps

4 Select the ring path preference for the aggregation VPS.

5 Occam Networks recommends that BLCs in aggregation mode be configured in pairs.

For example, the VPSs in Figure 11-3 might be configured as follows:

VPSs 1 and 2 on PG 1

VPSs 3, 4, 5 and 6 on PG 2

OR

VPSs 1, 2, 3 and 4 on PG 1

VPSs 3 5 and 6 on PG 2

You should try to configure the VPSs so that the traffic on the subtended access-rings is balanced. occam(config-eps)# ring path preference {pg1|pg2}

6 Enable aggregation mode on the VPS:occam(config-eps)# aggregation

Note: Configuration changes do not take effect until after exiting EPS Configuration Mode.



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring an Interconnect on a VPT on an Aggregation Ring

Configuring an Interconnect on a VPT on an Aggregation Ring

This section describes how to configure an interface to be an interconnect on an aggregation ring. For example, in Figure 11-4 below, interfaces A and B are configured as interconnects.

Figure 11-4: Aggregation Ring VPT Interconnects


2 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}

3 Configure the interface to be an interconnecting interface between VPTs:occam(config-if-eth)# eps ring interconnect

OR occam(config-if-xg)# eps ring interconnect

4 Configure the Ethernet interface as an IGMP passthrough:occam(config-if-eth)# igmp passthrough

If configuring a 10 GigE interface:occam(config-if-xg)# igmp passthrough

5 Enable the interface:occam(config-if-eth)# no shutdown

OR occam(config-if-xg)# no shutdown

6 Exit Ethernet Interface or 10 GigE Interface Configuration mode:occam(config-if-eth)# exit

OR occam(config-if-xg)# exit



Configuring an Interconnect on a VPT on an Aggregation Ring


occam# copy running-config startup-config


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring a VPT Ethernet Interface as a Path Group Participant

Configuring a VPT Ethernet Interface as a Path Group Participant

This section describes how to configure an interface to be a path group participant on an aggregation ring. For example, in Figure 11-5 below, interfaces A and B are configured as path group participants.

Figure 11-5: Aggregation Ring VPT Path Group Participants




3 Configure the interface to participate with PG 1 or PG 2. For example, in Figure 11-5, interface A would be configured for PG 1 and interface B would be config-ured for PG 2.

Note: Ring profiles are optional but not the norm on these interfaces:occam(config-if-eth)# eps ring pg1 [ring-profile]ORoccam(config-if-eth)# eps ring pg2 [ring-profile]

ORoccam(config-if-xg)# eps ring pg1 [ring-profile]

ORoccam(config-if-xg)# eps ring pg2 [ring-profile]



INTERFACE B

INTERFACE A



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.




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring a VPS Interface on an Aggregation Ring

Configuring a VPS Interface on an Aggregation RingConfiguring a Passthrough Interface on an Aggregation Ring VPS

This section describes how to configure a VPS interface on an aggregation ring as a passthrough interface.

Figure 11-6: Aggregation Ring VPS Passthrough Interfaces




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

4 Configure the interface as “passthrough” for IGMP. occam(config-if-eth)# igmp passthrough

OR

6450 VPS1

6450 VPS 2

MAINAGGREGATION

RING


RING A(WEST)

0 VPS 5

VPS 6

0 VPS 76450 VPS 8

)PASSTHROGH

INTERFACE



Configuring a VPS Interface on an Aggregation Ring

occam(config-if-xg)# igmp passthrough








BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring a VPS Interface on a Subtended Aggregation Ring

Configuring a VPS Interface on a Subtended Aggregation RingConfiguring a VPS Interface For a Subtended Aggregation Ring

This section describes how to configure a VPS interface to support a subtended aggregation ring off of an aggregation ring.

Figure 11-7: Aggregation Ring VPS Subtended Aggregation Ring Interfaces


2 Enter Ethernet Configuration mode and specify an Ethernet interface:occam(config)# interface ethernet {Ethernet-interface-number}


3 Configure the Ethernet interface to participate with PG 1 or 2 and attach a specified Ring Profile that will only allow configured VLANs on the subtended aggregation ring:occam(config-if-eth)# eps ring {pg1|pg2} {ring-profile-name}

If configuring a 10 GigE interface:occam(config-if-xg)# eps ring {pg1|pg2} {ring-profile-name}

6450 VPS1

6450 VPS 2

BLC 2

BLC 1

MAINAGGREGATION

RING

BLC 3


RING A(WEST)

6450 VPS 5

6450 VPS 6

6450 VPS 76450 VPS 8

ACCESSRING 1

(WEST-SALEM)SUBTENED

AGGREGATIONRING

INTERFACE



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

4 Configure the Ethernet interface as an IGMP host:occam(config-if-eth)# igmp host

If configuring a 10 GigE interface:occam(config-if-xg)# igmp host


If configuring a 10 GigE interface:occam(config-if-xg)# no shutdown

6 Exit Ethernet Configuration Mode:occam(config-if-eth)# exit

If you configured a 10 GigE interface, exit 10 GigE Interface Configuration mode:occam(config-if-xg)# exit




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring a VPS Interface on a Subtended Aggregation Ring

Configuring a Passthrough Interface For a Subtended Aggregation RingThis section describes how to configure a VPS passthrough interface on a subtended aggregation ring off of an aggregation ring. In the example shown in Figure 11-8, these are interfaces A through H

Figure 11-8: Aggregation Ring VPS Subtended Aggregation Ring Passthrough Interfaces




3 Configure the Ethernet interface ring option as “all”:occam(config-if-eth)# eps ring all

If configuring a 10 GigE interface:occam(config-if-xg)# eps ring all

4 Configure the Ethernet interface as an IGMP passthrough interface:occam(config-if-eth)# igmp passthrough



6450 VPS1

6450 VPS 2

SUBTENDEDAGGREGATIONRING A (WEST)

6450 VPS 5

6450 VPS 6

6450 VPS 7 6450 VPS 8

ACCESSRING 1

WEST-SALEM) A

B

C

D

E

F G

H



Configuring a VPS Interface on a Subtended Aggregation Ring







BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring an Access-Ring

Configuring an Access-RingConfiguring 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.




4 Select the ring path preference for the VPS:occam(config-eps)# ring path preference {pg1|pg2}

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

BLC 3 and BLC 4 should be configured with the command:occam(config-eps)# ring path preference pg2


Figure 11-9: Access Ring VPS Configuration

6450 VPS1

6450 VPS 2

BLC 2

BLC 1

MAINAGGREGATION

RING

BLC 3


RING A(WEST)

6450 VPS 5

6450 VPS 6

6450 VPS 76450 VPS 8

ACCESSRING 1

(WEST-SALEM)

BLC 4

PG 2

PG 1



Configuring an Access-Ring

Configuring a VPS Interface For an Access RingThis section describes how to configure a VPS interface to support an Access Ring off of a main or subtended aggregation 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


2 Enter Ethernet Configuration mode and specify an Ethernet interface:occam(config)# interface ethernet {Ethernet-interface-number}OR occam(config)# interface xg {XG-interface-number}

3 Configure the Ethernet interface to participate with PG 1 or 2 and attach a specified Access-Ring Profile:occam(config-if-eth)# eps ring {pg1|pg2} {access-ring-profile-name}

If configuring a 10 GigE interface:occam(config-if-xg)# eps ring {pg1|pg2} {access-ring-profile-name}

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

6450 VPS1

6450 VPS 2

BLC 2

BLC 1

MAINAGGREGATION

RING

BLC 3


RING A(WEST)

6450 VPS 5

6450 VPS 6

6450 VPS 76450 VPS 8

ACCESSRING 1

(WEST-SALEM)

ACCESS-RINGINTERFACE

ACCESS-RINGINTERFACE

BLC 4



command should be as follows:occam(config-if-xg)# eps ring pg2 west-salem


If configuring a 10 GigE interface:occam(config-if-xg)# igmp host





7 Exit Global Configuration Mode and save your configuration:occam(config)# exitoccam# copy running-config startup-configBuilding configuration....

Using the “load network” Command on Access-Rings.Prewired BLC 6012 chassis come with configurations loaded on the flash memory. These configure the Ethernet interfaces for chassis cabling and applications (VPS or VPT). The lode network command may be used on BLC 6012 chassis on Access-Rings.

Please read Chapter 7, Initial Configuration Steps on page 135 for information about how to connect with the BLC and configure your system parameters. This chapter also describes how to use the load network command to automatically configure EPS on prewired BLC 6012 chassis. When the load network command is used all other BLC networking connections and parameters must be configured.

These wiring arrangements are discussed in section Appendix B, BLC 6012 Chassis Wiring Arrangements on page 833.

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.



Configuring an Access-Ring

Configuring a Passthrough Interface For an Access-RingThis section describes how to configure a passthrough interface on an Access-Ring off of a subtended or main aggregation ring. In the example shown in Figure 11-11, these are interfaces A through F

Figure 11-11: Aggregation Ring VPS Access-Ring Passthrough Interfaces




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

If configuring a 10 GigE interface:occam(config-if-xg)# eps ring all

4 Configure the Ethernet interface as an IGMP passthrough interface:occam(config-if-eth)# igmp passthrough


6450 VPS1

6450 VPS 2

BLC 2

BLC 1

MAINAGGREGATION

RING

BLC 3

SUBTENDEDAGGREGATIONRING A (WEST)

6450 VPS 5

6450 VPS 6

6450 VPS 7 6450 VPS 8

ACCESSRING 1

(WEST-SALEM)

A

B

C

D

E

F










Configuring a VPS or VPT Ethernet Interface for Untagged Traffic

Configuring a VPS or VPT Ethernet Interface for Untagged Traffic

VPS and VPT interfaces that will transmit to networks nodes that expect untagged Ethernet frames should be configured with the command “eps access untagged vlan {VLAN-ID-number}”. This is the normal choice for subscriber ports and primary ISP “feeder” networks connected at the COT.

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 transmitted out that interface after the tag field is removed.




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}







BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic

Configuring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic

This section describes how to configure an EPS access tagged interface that maps EPS domain VLANS onto a customer switch VLAN domain. A tagged profile defines the mapping between EPS domain VLANs and customer switch VLANs, including only those VLANs which are required by the customer. Once a tagged profile has been defined it may be applied to one or more interfaces.

Per EPS domain:

Limit of 32 tagged profiles per EPS domain

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:

No more than 2 tagged profiles per copper blade

No more than 12 tagged profiles per fiber blade

Tag entry limit:

BLC 6450: No more than 120 tag entries in any given profile

Any other BLC: No more than 768 tag entries in any given profile

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.

Configuring a Tagged Profile


2 Enter Tagged Profile Configuration Mode and create a tagged-profile with a specific name:occam(config)# tagged-profile {name}

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}




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.

5 Exit Tagged Profile Configuration Mode. Changes made to a tagged profile do not take effect until after the profile has been exited:occam(config-tagged-profile)# exit


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring a VPS or VPT Ethernet Interface for VLAN Tagged Traffic

Attaching a Tagged Profile to an Ethernet Interface



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}









Example ConfigurationIn 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-mapuntagged vlan 10 1 tagged vlan 2 202 tagged vlan 3 203 tagged vlan 4 204 tagged vlan 5 205 tagged vlan 6 206interface Ethernet 7 eps access tagged vlan-mapno shutdownexit

Viewing Your Tagged Profile ConfigurationUse the command show tagged profile to display information about all tagged profiles. Use the command show tagged profile {profile-name} to display information about a specific tagged profile.

The following example shows sample output from this command:occam# show tagged-profile

tagged-profile site1:eps vlan user vlan2 2023 2034 2045 2056 206occam#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkConfiguring TLS

Configuring TLSEPS 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 6252-02, BLC 6252-03

BLC 6312

BLC 6314

BLC 6450

BLC 6440-01

BLC 6640-01

BLC 6660-01, BLC 6660-02, BLC 6660-03

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.

This feature enables service providers to use a single VLAN to support customers who have multiple VLANs by preserving VLAN IDs and keeping traffic in different customer VLANs segregated. Each TLS customer on an EPS domain consumes a single EPS VLAN.

Priority Bit Settings On Q-in-Q tagged trafficThere are three ways you may configure priority bit settings on Q-in-Q traffic:

1 Allow all incoming traffic be DSCP mapped. This is the factory default setting.

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.



Configuring TLS

Configuring TLSTLS 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.



2 Configure the interface to add an outer tag to a specified VLAN:occam(config-if-eth)# eps access doubleqtag vlan {2-122}

OR occam(config-if-xg)# eps access doubleqtag vlan {2-122}

Note: Since all management traffic for the BLC network runs on VLAN 2, Occam Networks recommends that it not be used for TLS.







Double Tagged Ports and BehaviorsThe table below shows example combinations of sending a tagged and untagged stream of traffic at a Double Q tagged Ethernet port and an untagged VLAN port.

Traffic Stream In

Ethernet Port Type Inbound

Ethernet Port Type Outbound

Traffic Stream Out

Tagged VLAN 50

Double Tagged Port VLAN 50


Tagged VLAN 50

Tagged VLAN 99



Tagged VLAN 99

Tagged VLAN 99


Untagged port VLAN 50

Tagged VLAN 99

Untagged Double Tagged Port VLAN 50


Untagged



Untagged

Untagged Untagged port VLAN 50


Untagged

Tagged VLAN 99



No traffic

Tagged VLAN 99


Tagged No traffic

Untagged Untagged port VLAN 50


Untagged


Tagged No traffic

Tagged VLAN 99


Tagged VLAN transla-tion 50 to 99

No traffic


Tagged VLAN transla-tion 50 to 99

No traffic



Configuring TLS

Policy Map Configuration

1 Enter Policy Map Configuration Mode and create a rate-limiting policy map:occam(config)# policy-map {policy-map name}

2 Configure the policy map to rate-limit unicast traffic on a VLAN to a specified rate in Mbps with three decimal point precision:occam(config-pmap)# rate-limit {0.1-32}

3 Exit Policy Map Configuration Mode:occam(config-pmap)# exit



Configuring a TLS Profile


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}

4 Configure the maximum number of MAC addresses that are allowed on a specific service on an Ethernet subscriber interface:occam(config-tls-profile)# mac limit{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}

7 Exit TLS Profile Configuration Mode:occam(config-tls-profile)# exit





Configuring an Ethernet Interface For TLS

1 Enter Ethernet Interface Configuration mode specifying an interface by number:occam(config)# interface ethernet {interface-number}

2 Configure the Ethernet interface to become a subscriber interface:occam(config-if-eth)# eps access subscriber

3 Enter Ethernet Service Configuration mode specifying a service by number. The parameters are from one through five:occam(config-if-eth)# service {1-5}

4 Attach a TLS-Profile to the service:occam(config-if-eth-service-<1-5>)# tls-profile profile-name

5 Configure the service to match any VLAN.occam(config-if-eth-service-<1-5>)# match vlan any

6 Enable the service:occam(config-if-eth-service-<1-5>)# no shutdown

7 Exit Service Configuration mode:occam(config-if-eth-service-<1-5>)# exit

8 Exit Ethernet Interface Configuration mode:

9 occam(config-if-eth)# exit





Configuring a BLC to Run EPS with Non-EPS Devices

Configuring a BLC to Run EPS with Non-EPS DevicesYou may configure a BLC to interact with non-EPS devices (i.e., VLAN switch). The BLC will not appear to be running EPS to these devices and will act as a simple layer 2 device.




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}

5 Enter Ethernet Configuration mode and specify an Ethernet interface number to configure to be a path participant:occam(config)# interface ethernet {interface-number}

6 Configure the interface to be a network access point for subscriber voice/voice control/management traffic:occam(config-if-eth)# eps access untagged vlan 2


8 Exit Ethernet Configuration mode:occam(config-if-eth)# exit


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkEthernet Loop Detection (ELD) Configuration

Ethernet Loop Detection (ELD) ConfigurationELD reduces the occurrence of network outages caused by accidentally configuring or cabling Ethernet interfaces in such a way that cause network loops. ELD will block an interface from entering the forwarding state if it senses that a loop has been created. When an interface is administratively enabled or after certain configuration changes the interface is transitioned to a disabled state and then re-enabled in order to activate the loop detection.

ELD operates on the following types of Ethernet interface configurations:

EPS Ring interfaces (All, PG1, PG2)

EPS Access Untagged interfaces with the default of untagged VLAN 2

Note: The BLC 6151-01 does not support ELD.

ELD OperationWhenever 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.

Plugging in a cable will force an ELD test.

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.



Ethernet Loop Detection (ELD) Configuration

stp access CommandLoop detection is not conducted on Spanning Tree Protocol (STP) access interfaces. Testing of these interfaces would cause ELD to report non-existent STP loops.

The command stp access tells the BLC’s ELD software not to test an STP interface and drop ELD test packets on that interface. This prevents false loop detection in power up scenarios where multiple attached STP interfaces can be in a forwarding state. By factory default, STP interfaces are not tested (the command is enabled by default).

Enabling STP Access Interfaces

The following example disables ELD on Ethernet interface 3:occam(config)# interface ethernet 3occam(config-if-eth)# stp access

If configuring a 10 GigE interface, enter 10 GigE Interface Configuration mode:occam(config)# interface xg 3occam(config-if-xg)# stp access

Disabling STP Access Interfaces

The command no stp access enables ELD on Ethernet interface 3:occam(config)# interface ethernet 3occam(config-if-eth)# no stp access

If configuring a 10 GigE interface, enter 10 GigE Interface Configuration mode:occam(config)# interface xg 3occam(config-if-xg)# no stp access

Verifying STP Access Status

Use the command show interfaces ethernet to verify if STP access is enabled or disabled. (Please see the Occam Networks publication Command Reference Guide for sample output of this command.)

Under the heading “EPS Settings”, the output will read:stp access is enabled

or

stp access is disabled


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkEthernet Loop Detection (ELD) Configuration

Enabling and Disabling ELDELD may be enabled and disabled with the command (no) loop detection from EPS Configuration mode. ELD is enabled by factory default.

The following example disables ELD:occam(config)# epsoccam(config-eps)# no loop detection

The following example enables ELD:occam(config)# epsoccam(config-eps)# loop detection

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



Displaying Information About Your EPS Configuration


Use the show eps command to display your EPS configuration and statistics.

The following example shows sample output from this command for a VPT on an aggregation ring:occam##show eps Device Mode: VPT on PG1

mode VPTvpt path group 1global mask 0x400timer interval(ms) 4heartbeat path group 1ring ID 0interval(ms) 4speed(Mbps) 1000sequence 43083timestamp 0x000148076origin MAC 00:02:86:00:92:C9tx packets 3319884tx bytes 345267936

Subtended/main ring statusName PG Hb-Rx Total-Hb-Rx Faults Seq-Num Seq-Misses State XG 15/2 1 65 3297315 0 42266 0 up

occam#exit


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkDisplaying Information About Your EPS Configuration

The following example shows sample output from this command for a VPS on an aggregation ring:

occam# show epsDevice Mode: VPS eps ring path preference: PG1

path group PG1 PG2current path group 1 0default path group 1 0heartbeat state UP UPeps state UP_ACTIVE UP_ACTIVEglobal mask 0x400 0x400time since last heartbeat(ms) 1 3generation interval(ms) 4 4path speed XGigEthernet XGigEthernetsequence number 51365 50551sequence misses 0 0origin MAC 00:02:86:00:92:C9 00:02:86:00:92:FBorigin MC DEST 01:02:86:00:00:01 01:02:86:00:00:02source dev XG 15/1 XG 15/2rx last interval 2 2rx packets 2060720 2060416rx bytes 185464800 185437440fault counter 0 0fault subscribers 0 0fault access 0 0fault actual(ms) 0 0fault complete actual(ms) 0 0poll interval(ms) 8 8reversion hysteresis(sec) 60 60

Subtended/main ring statusName PG Hb-Rx Total-Hb-Rx Faults Seq-Num Seq-Misses StateEthernet 15/4 1 13 824218 0 43529 0 up Ethernet 15/5 1 13 825135 0 43529 0 up XG 15/4 1 13 824759 0 43529 0 up occam#

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 commandeps ring path preference.

heartbeat state UP or DOWN state determined by the presence or absence of a Path Group heartbeat.




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 heartbeat (ms)

Amount of time in milliseconds since the reception of the 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.

Field Description


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 11: Configuring an EPS Aggregation Ring NetworkDisplaying Information About Your EPS Configuration

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

EPS map for node: 192.168.21.111

Port Media Type State | Intfc-id Ip Type Mode Chassis Product Mac address age2 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 sec5 copper PG2 valid | fff/15/2 192.168.21.20 PG1 VPT 1 BLC_6640_01 00:02:86:00:2a:4b 20 sec6 copper INTC valid | fff/15/6 192.168.21.20 INTC VPT 1 BLC_6640_01 00:02:86:00:2a:4b 20 sec8 fiber PG2 unknown | occam#

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.

Field Description


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet Links

Introduction

Chapter 12Configuring Subtended EPS Access-Rings with Ethernet Links

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Configuring a Subtended Access Ring With an Ethernet Link . . . . . . . . . . . . . . . . 244

IntroductionThis chapter describes how to configure subtended EPS Access-Rings.







Chapter 14, Ethernet Subscriber Interfaces on page 281 provides information about how to configure Ethernet fiber interfaces can serve as subscriber facing interfaces.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 12: Configuring Subtended EPS Access-Rings with Ethernet LinksConfiguring a Subtended Access Ring With an Ethernet Link

Configuring a Subtended Access Ring With an Ethernet Link

You may configure your EPS aggregating network with one or more subtended rings. Subrings may be configured with Ethernet links. The BLC 6150-01 and BLC 6660-01/-02/-03 platforms support subrings configured with MLPPP links. Please refer to the section Configuring a Subtended EPS Ring with MLPPP in Chapter 13, Configuring EPS Over MLPPP Links on page 259.

An example of an EPS aggregation network configured with a subtended Ethernet ring is shown in Figure 12-1. This is only an example and your own network configuration may be different.

Figure 12-1: EPS Aggregation Network With Subtended Ring

VPS 5Access Ring

SubtendedAccess Ring

PG 1"Heartbeat"

PathGroup 1

"Heartbeat"

Path

Group 2"Heartbeat"

VPS 7

VPS 6

VPS 4

VPS 3

VPS 1 VPS 2

Aggregation Ring 1

A

B

PG 1"Heartbeat"

C

D

E

F

G

PG 1"Heartbeat"

PG 2"Heartbeat"

PG 2"Heartbeat"

H I

J

K

K




The PG1 heartbeat from the aggregation ring travels as follows:

It enters VPS 1 from the aggregation ring on interface I.

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.



VPS and Ethernet Interface Configuration Steps For VPS 4

Configuration Steps for VPS 4




4 Select the ring path preference as PG 1:occam(config-eps)# ring path preference pg 1


Configuring Ethernet Interfaces “B” and “C” on VPS 4

Interfaces B and C in Figure 12-1 have the same configuration steps.

1 Enter Ethernet or XG Configuration mode and specify an interface to configure: occam(config)# interface ethernet {interface-number}or occam(config)# interface xg {interface-number}

2 Configure the Ethernet interface to participate with both path groups:occam(config-if-eth)# eps ring alloroccam(config-if-xg)# eps ring all

3 Configure the Ethernet interface as IGMP passthrough:occam(config-if-eth)# igmp passthroughoroccam(config-if-xg)# igmp passthrough

4 Enable the interface:occam(config-if-eth)# no shutdownoroccam(config-if-xg)# no shutdown

5 Exit Ethernet or XG Configuration Mode:occam(config-if-eth)# exitoroccam(config-if-xg)# exit




Configuring Ethernet Interface “G” on VPS 4

1 Enter Ethernet Configuration mode and specify an Ethernet interface to configure as interface “G”. In this example interface 3 is selected:occam(config)# interface ethernet 3oroccam(config)# interface xg 3

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 pg1oroccam(config-if-xg)# eps ring pg1

3 Configure the Ethernet interface as an IGMP host:occam(config-if-eth)# igmp hostoroccam(config-if-xg)# igmp host







VPS and Ethernet Interface Configuration Steps For VPS 5





4 Select the ring path preference as PG 2: occam(config-eps)# ring path preference pg 2


Ethernet Interfaces “D” and “E” on VPS 5

Interfaces D and E in Figure 12-1 have the same configuration steps.

1 Enter Ethernet or XG Configuration mode and specify an Ethernet interface to configure as interface D or interface E. occam(config)# interface ethernet {interface-number}oroccam(config-if-xg)# interface xg{interface-number}

2 Configure the interface to participate with both path groups:occam(config-if-eth)# eps ring alloroccam(config-if-xg)# eps ring all

3 Configure the interface as IGMP passthrough:occam(config-if-eth)# igmp passthroughoroccam(config-if-xg)# igmp passthrough






Ethernet Interface “K” on VPS 5

1 Enter Ethernet or XG Configuration mode and specify an interface to configure as interface F:occam(config)# interface ethernet {interface-number}oroccam(config)# interface xg 3

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 pg2oroccam(config-if-xg)# eps ring pg2

3 Configure the interface as an IGMP host:occam(config-if-eth)# igmp hostoroccam(config-if-xg)# igmp host







VPS and Ethernet Interface Configuration Steps For VPS 6 and 7





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





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}oroccam(config-if-xg)# interface xg{interface-number}

2 Configure the interface to participate with both path groups:occam(config-if-eth)# eps ring alloroccam(config-if-xg)# eps ring all

3 Configure the interface as IGMP passthrough:occam(config-if-eth)# igmp passthroughoroccam(config-if-xg)# igmp passthrough






BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 13: Configuring EPS Over MLPPP Links

Introduction

Chapter 13Configuring EPS Over MLPPP Links

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Configuring VLAN Untagged Traffic Over MLPPP . . . . . . . . . . . . . . . . . . . . . . . . . . 257Configuring a Subtended EPS Ring with MLPPP. . . . . . . . . . . . . . . . . . . . . . . . . . . 259

IntroductionT1 ports not assigned to CES or DS0 cross connects may be configured for MLPPP on the following BLCs:

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).

EPS ConfigurationThis chapter provides information about configuring EPS over MLPPP links.







Model Number of MLPPP Bundles Available

BLC 6150-01 1-4

BLC 6246 1-4

BLC 6660-01/-02/-03 1-8

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 13: Configuring EPS Over MLPPP LinksIntroduction

MLPPP Engineering GuidlinesMLPPP links require substantial CPU processing power for header compression and packet forwarding. The following recommendations should be followed to ensure consistent performance of the BLC network when deploying MLPPP links.

VPT blades provide a specialized network function by sending control packets with critical timing requirements. For VPT blades, MLPPP should be restricted to two (2) member links with header compression enabled or four (4) member links with header compression disabled. If the VPT blade is also distributing video multicast traffic into the access network, avoid running MLPPP links on the VPT blades.

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.

Occam Networks has verified the network performance up to 48 voice channels maximum in conjunction with a mix of DSL data traffic. Performance test whereby the MLPPP links are saturated with thousands of small packets that exceed the MLPPP link capacity may cause some voice call connection failures.

Packet forwarding over MLPPP bundles is handled by software bridging.

The maximum forwarding rate is approximately 6000 pps when no voice channels are connected.

With 24 voice channels connected, a maximum of 4500 pps of data packet forwarding is supported.

With 48 voice channels connected, a maximum of 3000 pps of data packet forwarding is supported.

MLPPP cannot operate on a blade that is supporting a T1 CES service.



Introduction

MLPPP Stability EnhancementsMLPPP links require substantial CPU processing power for header compression and packet forwarding. Release 5.3R2 changed the MLPPP Trunking to establish a closer relationship between the individual T1 members of the group with the first path being designated as a Master connection and the others as secondary. This aids in the management of the MLPPP connection so that individual T1 lines can be added or taken out of service without taking the whole connection down.

Beginning with release 5.3R2, the entire multilink bundle will go down only if the Master T1 is manually disabled. The bundle will stay enabled though any of the following link states:

One of the PPP (T1) links (NOT the master T1 link) is manually stopped.

A new PPP link to the ML group is introduced.

A PPP link (NOT the T1 master link) is removed from an ML group.

An LCP terminate-request is received by the PPP link.

An LCP configure-request is received by the PPP link.

Three echo-requests go unanswered (keep alive functionality).

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 13: Configuring EPS Over MLPPP LinksIntroduction

Figures 13-1 and 13-2 show legal and illegal EPS rings configured with a T1/MLPPP link:

Figure 13-1: Legal EPS Ring

Figure 13-1 is a legal EPS ring.

Figure 13-2: Ilegal EPS Ring

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.

PathGroup 2

"Heartbeat"

PathGroup 1

"Heartbeat"

VPT 1 VPT 2

VPSVPS

VPSVPS

MLPPP

PathGroup 2

"Heartbeat"

PathGroup 1

"Heartbeat"

VPT 1 VPT 2

VPSVPS

VPSVPS

MLPPP



Configuring VLAN Untagged Traffic Over MLPPP

Configuring VLAN Untagged Traffic Over MLPPPCaution: 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).

1 Enter Multilink Interface Configuration Mode and create a multilink bundle:occam(config)# interface multilink {1-100}

2 Configure the bundle:occam(config-if-mlink)# eps access untagged vlan {2-122}

3 Enable the multilink group:occam(config-if-mlink)# no shutdown

4 Exit Multilink Interface Configuration Mode and return to Global Configuration Mode:occam(config-if-mlink)# exit

5 Enter Serial Interface Configuration Mode, specifying a T1 interface port number:occam(config)# interface serial {T1-interface-number}

6 Specify the clock source for the T1 interface:occam(config-if-ser)# service-module t1 clock source line

7 Enable PPP mode:occam(config-if-ser)# mode ppp

8 Assign the T1 port to the multilink group you created in step 1:occam(config-if-ser)# multilink-group {1-100}

9 Enable the T1 port:occam(config-if-ser)# no shutdown

10 Exit Serial Interface Configuration Mode and return to Global Configuration Mode:occam(config-if-ser)# exit

11 Enter Serial Interface Configuration Mode, specifying another T1 interface port number:occam(config)# interface serial {T1-interface-number}


!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 13: Configuring EPS Over MLPPP LinksConfiguring VLAN Untagged Traffic Over MLPPP

13 Assign the T1 port to the multilink group you created in Step 2:occam(config-if-ser)# multilink-group {multilink-id-number}



16 Repeat steps 12 through 16 for any other T1 interfaces you wish to add to the multilink group.

17 Select the source for clocking:occam(config)# network-clock-select primary serial {T1-interface-number}



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



Configuring a Subtended EPS Ring with MLPPP

Configuring a Subtended EPS Ring with MLPPPThe BLC 6150-01, BLC 6246, BLC 6640-01, and BLC 6660-01/-02/-03 platforms support subrings configured with Ethernet MLPPP links. MLPPP on the subtended ring should be set to PG1 or PG2 on both sides. Figures 22-3 and 22-4 show an example of a subtended EPS ring with two MLPPP links.

MLPPP T1 links should be clocked from the NSP or NTP at the upstream node. A new timing domain, if required, must be established at the remote end of MLPPP links using one (or more as alternates) of the T1 links from the MLPPP bundle.

In the example configuration shown in Figure 22-4, Ring 1 is configured as a for NSP timing on broadcast group domain number 5. VPT 1 is a NSP transmitter and VPS 2 and 3 are NSP receivers. The T1 links between VPS 2 to VPS 5 receive their clocking from this timing domain. T1 interface 2 on VPS 5 is configured as the primary source for clocking and T1 interface 3 is configured as the secondary source for clocking.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 13: Configuring EPS Over MLPPP LinksConfiguring a Subtended EPS Ring with MLPPP

Figure 13-3: Subtended EPS Ring with Two MLPPP Links

VPT 1 VPT 2

VPS 4VPS 1

VPS 3 VPS 2

VPS 5 VPS 7Ethernet

InterfacesD, E, F, and G:" eps ring all"

"igmp passthrough"

RING 2

InterfacesO, P, Q and R:" eps ring all"

"igmp passthrough"

MLP

PP

RING 1

MLP

PP

VPT 1:"mode vpt pg1"

VPS 6Eth

ernet

Both Sides ofMultilink Goup

Interfaces M and N:"eps ring pg1"

Interface C:"eps ring pg1""igmp host"

Interfaces A and B:"ring interconnect""igmp passthrough"

A B

C

D

E

F

M G H

N

O

P Q

R

Both Sides ofMultilink Goup

Interfaces S and T:"eps ring pg2"

S

T

InterfacesH, I, J and K:" eps ring all"

"igmp passthrough"

I

J

K

L

VPT 2:"mode vpt pg2"

Interface L:"eps ring pg1""igmp host"

PG 1 PG 2

VPS 1and 2:"mode vps""ring path

preference pg1"

VPS 5 and 6:"mode vps""ring path

preference pg1"

VPS 7:"mode vps""ring path

preference pg2"

VPS 3 and 4:"mode vps""ring path

preference pg2"




Figure 13-4: Clocking on a Subtended EPS Ring with Two MLPPP Links

VPT 1 VPT 2

VPS 4VPS 1

VPS 3 VPS 2

VPS 5 VPS 7Ethernet

RING 2

MLP

PP

RING 1

MLP

PP

VPS 5 and 6 areNSP Receivers:

"network-clock-select primary nsp"

"nsp mode rx7"

VPS 5NSP Transmitter:

"network-clock-selectprimary serial 1""nsp mode tx7"

VPS 1, 2, 3 and 4 areNSP Receivers:

"network-clock-selectprimary nsp"

"nsp mode rx5"

VPT 1NSP Transmitter:

"network-clock-select primary serial 2""nsp mode tx 5"

VPS 6Eth

ernet

Interface M(MultilinkGroup).Each T1interface

in multilinkgroup:

"service-module t1

clock sourceinternal"

Interface N(MultilinkGroup).Each T1

interface inmultilinkgroup:

"service-module t1

clock sourceline"

Interface S(MultilinkGroup).Each T1

interface inmultilinkgroup:

"service-module t1

clock sourceline"

Interface T(MultilinkGroup).Each T1interface

in multilinkgroup:

"service-module t1

clock sourceinternal"

NSPCLOCK

SOURCE



Configuration Steps Figure 13-3VPT 1 - Please turn to page 263 for configuration steps.

Interface A - Please turn to page 263 for configuration steps.

Interface C - Please turn to page 264 for configuration steps.

VPT 2 - Please turn to page 265 for configuration steps.

Interface B - Please turn to page 265 for configuration steps.

Interface L - Please turn to page 265 for configuration steps.

VPS 1 - Please turn to page 266 for configuration steps.

Interfaces D and E - Please turn to page 266 for configuration steps.


Interfaces F and G - Please turn to page 267 for configuration steps.

Interface (Multilink Group) M - Please turn to page 268 for configuration steps.


Interfaces H and I - Please turn to page 269 for configuration steps.

Interface (Multilink Group) T - Please turn to page 271 for configuration steps.


Interfaces J and K - Please turn to page 272 for configuration steps.


Interface (Multilink Group) N - Please turn to page 274 for configuration steps.

Interface O - Please turn to page 275 for configuration steps.


Interfaces P and Q - Please turn to page 276 for configuration steps.


Interface R - Please turn to page 277 for configuration steps.

Interface (Multilink Group) S - Please turn to page 277 for configuration steps.




VPT 1In Figures 13-3 and 13-4 VPT 1 is an NSP transmitter:


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


4 Specify a T1 interface as the primary source for clocking:Occam(config)# network-clock-select primary serial {interface-number}

5 Specify a T1 interface as the secondary source for clocking:Occam(config)# network-clock-select secondary serial {interface-number}

6 Configure VPT 1 as a NSP transmitter on a broadcast domain group number between one and thirty-two. In Figure 22-4 the VPT is transmitting on broadcast group domain number 5:occam(config)# nsp mode tx 5

7 (Optional) Configure the NSP Time-To-Live (TTL) command, specifying a number of routed (not switched) hops. The default value is 64 hops:Occam(config)# nsp tx ttl {1-225}

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}

2 Configure the interface to be an interconnecting interface between VPTs:occam(config)# eps ring interconnect

3 Enable the interface:Occam(config-if-eth)# no shutdown



4 Exit Ethernet Interface Configuration Mode:Occam(config-if-eth)# exit

Interface CIn 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.


2 Configure the Ethernet interface to participate with path group 1:occam(config-if-eth)# eps ring pg1








VPT 2


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


4 Configure VPT 2 as an NSP receiver on a broadcast domain group number between one and thirty-two. In Figure 13-4 the broadcast domain group number is five:occam(config)# nsp mode rx 5

Interface B


2 Configure the interface to be an interconnecting interface between VPTs:occam(config)# eps ring interconnect

3 Enable the interface:Occam(config-if-eth)# no shutdown

4 Exit Ethernet Interface Configuration Mode:Occam(config-if-eth)# exit

Interface LThe heartbeat from VPT 2 exits out of interface L, ending at VPT 1, enabling Ring 1 to have a heartbeat on path group 2:


2 Configure the Ethernet interface to participate with path group 2:occam(config-if-eth)# eps ring pg2






6 Exit Global Configuration Mode and save your configuration:occam(config)# exitoccam# copy running-config startup-config

VPS 1


2 Select VPS as the EPS mode for the BLC:occam(config-eps)# mode vps

3 Specify PG 1 as the preferred EPS path group:occam(config-eps)# ring path preference pg1


5 Configure VPS 1 as a NSP receiver on broadcast group domain number 5:occam(config)# nsp mode rx 5

Interfaces D and EIn 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}

2 Configure the Ethernet interface to participate with both path groups:occam(config-if-eth)# eps ring all

3 Configure the Ethernet interface as IGMP passthrough:occam(config-if-eth)# igmp passthrough







VPS 2






Interfaces F and GIn 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}







Interface (Multilink Group) MIn Figure 22-3, multilink group M connects VPS 2 to VPS 5. The heartbeat from VPT 1 enters through this interface, ending at VPS 3. This enables Ring 2 to have a heartbeat on path group 1:


2 Configure the bundle:occam(config-if-mlink)# eps ring pg1




For example, enter the command:occam(config)# interface serial 1

6 Specify the clock source for the T1 interface:occam(config-if-ser)# service-module t1 clock source internal















17 Select the source for clocking:occam(config)# network-clock-select primary serial nsp


VPS 3






Interfaces H and IIn 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.



1 Enter Ethernet Configuration mode and specify an Ethernet interface to configure as an interface:occam(config)# interface ethernet {ethernet-interface}








Interface (Multilink Group) TIn Figure 22-3, multilink group T connects VPS 7 to VPS 3. The heartbeat from VPT 2 enters through this interface, ending at VPS 2. This enables Ring 2 to have a heartbeat on path group 2:







6 Specify the clock source for the T1 interface:occam(config-if-ser)# service-module t1 clock source internal














17 Select the source for clocking:occam(config)# network-clock-select primary serial nsp


VPS 4






Interfaces J and KIn 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.










VPS 5





5 Configure VPS 5 as a NSP transmitter on broadcast group domain number 7:occam(config)# nsp mode tx 7





8 Specify a T1 interface as the primary source for clocking:Occam(config)# network-clock-select primary serial {interface-number}

9 Specify a T1 interface as the secondary source for clocking:Occam(config)# network-clock-select secondary serial {interface-number}

Interface (Multilink Group) NIn Figures 22-3 and 22-4 multilink group N connects VPS 5 to Ring 2. VPS 5 is an NSP transmitter:

1 Enter Multilink Interface Configuration Mode and create a multilink bundle, picking a number between 1 and 2147483647. For example:occam(config)# interface multilink 2




5 Enter Serial Interface Configuration Mode, specifying a T1 interface port number between one and four. For example:occam(config)# interface serial 1

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


8 Assign the T1 port to the multilink group you created in step 4:occam(config-if-ser)# multilink-group 2



11 Enter Serial Interface Configuration Mode, specifying another T1 interface port number. For example:occam(config)# interface serial 2





13 Assign the T1 port to the multilink group:occam(config-if-ser)# multilink-group 2





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









VPS 6






Interfaces P and QIn 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.

1 Enter Ethernet Configuration mode and specify an Ethernet interface to configure as interface P or Q:occam(config)# interface ethernet {ethernet-interface}









VPS 7






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}






Interface (Multilink Group) SIn Figure 22-3, multilink group S connects VPS 7 to Ring 2:








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





11 Enter Serial Interface Configuration Mode, specifying another T1 interface port number between one and four:occam(config)# interface serial {T1-interface-number}


13 Assign the T1 port to the multilink group:occam(config-if-ser)# multilink-group {1-100}








18 Select the source for clocking:occam(config)# network-clock-select primary serial {T1-interface-number}





BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 14: Ethernet Subscriber Interfaces

Introduction

Chapter 14Ethernet Subscriber Interfaces

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282VLAN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Defining a Unicast Rate Limiting Policy Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Configuring an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Configuring an Ethernet Subscriber Interface and an Ethernet Service. . . . . . . . 292Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

IntroductionThis 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 ConfigurationPlease read the following chapters for more information about configuring EPS in a BLC network:








BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 14: Ethernet Subscriber InterfacesChapter Overview

Chapter OverviewEthernet 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.

Third, configure the Ethernet interface to become a subscriber interface. Optionally, add information in the info about the subscriber, for example) in the

Fourth, configure services on the subscriber interface. Up to five Ethernet services may be configured on each Ethernet subscriber interface. Ethernet service configuration is described on page 292.

Configure the following within an Ethernet 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

Set the maximum number of MAC addresses allowed, overriding the MAC limit set in the attached access profile.

Set the maximum number of IGMP groups allowed, overriding the number of IGMP groups set in the attached access profile.



Chapter Overview

Figure 14-1: Ethernet Subscriber Interface Configuration Steps

Configure anEthernet service

Create anaccess profile

Specify subscriber(ONT) VLAN specified

Attach the policy mapas a service policy to

rate limit unicasttraffic coming to BLC(service-policy input)

Specify network(EPS) VLAN ID

(Optional)Define MAC/IP

association

Ethernet interfaceconfigured as a

subscriber interface

Create a policy mapto rate limit unicast

traffic

Configure IGMP andIPSM parameters

Only one access profilemay be attached to a

service

Up to five Ethernetservices may be attached

to each Ethernet subscriberport

Match is made here betweenthe network VLAN and the

subscriber VLAN


rate limit unicast trafficcoming from BLC

(service-policy output)


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 14: Ethernet Subscriber InterfacesVLAN Mapping

VLAN MappingWithin 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.

The VLAN ID’s on the ONT should be set as follows:

Traffic leaving the ONT and going toward the subscriber is untagged.

VLAN DESCRIPTION VLAN ID

Multicast Traffic VLAN 3

Data VLAN 4

Video unicast traffic (STB connections) VLAN 6

VLAN DESCRIPTION VLAN ID

Data VLAN 4

Video multicast, unicast and broadcast traffic VLAN 6



VLAN Mapping

Figure 14-2: VLAN Mapping Diagram

VPS on PG2

VPT on PG1

VPT on PG2

VPS on PG2

BLC 6312VPS on PG1BLC 6312

VPS on PG1

ONT

VIDEO

VIDEO

VIDEO

DATAVOICE

Central Office

PSTN

VideoHeadend

InternetCOT

EPS VLAN IDs THROUGH BLCNETWORK:

VOICE-VLAN 2

MULTICAST TRAFFIC-VLAN 3

DATA-VLAN 4

VIDEO UNICAST ANDBROADCAST TRAFFIC (AKA STB

CONNECTIONS)-VLAN 6

VLAN IDs LEAVING BLCNETWORK:

VOICE-VLAN 2

DATA-VLAN 4

VIDEO MULTICAST, UNICAST andBROADCAST TRAFFIC - VLAN 6SERVICE 1:

MATCHES EPS VOICE VLAN 2 TOCUSTOMER VOICE VLAN 2

SERVICE 2:MATCHES EPS DATA VLAN 4 TO

CUSTOMER DATA VLAN 4

SERVICE 3:MATCHES EPS VIDEO VLAN 6 TO

CUSTOMER VIDEO VLAN 6


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 14: Ethernet Subscriber InterfacesDefining a Unicast Rate Limiting Policy Map

Defining a Unicast Rate Limiting Policy MapThe BLC 6312 and BLC 6314 provide the ability to use access profiles to rate limit unicast traffic on VLANs on Ethernet subscriber ports. An Ethernet subscriber port has been configured as such with the command eps access subscriber. This is described in the section Configuring an Ethernet Subscriber Interface and an Ethernet Service on page 292.

Network Ethernet Port Rate Limiting

The BLC 6312 and BLC 6314 also provide the ability to configure ingress and egress port-based rate limits on network Ethernet ports. An Ethernet network port has been configured as such with one of the following commands:

eps access doubleqtag vlan

eps access tagged

eps access untagged vlan

In this release Ethernet subscriber ports may not rate limit on a per port basis. If an Ethernet network port has an ingress/egress rate limit on it and becomes a subscriber port, the rate limits are removed from the port.

Rate limiting on an Ethernet network port is described in Chapter 15, Rate Limiting on Ethernet and XG Interfaces on page 297.

Policy Map Configuration


2 Configure the policy map to rate-limit unicast traffic on a VLAN to a specified rate in Mbps with three decimal point precision:occam(config-pmap)# rate-limit {0.1-32}

3 If required to allow support for derived voice (Analog terminal adapter) on an Ethernet port of a DSL modem, set the QoS priorities on a service, overriding the defaults. The priorities may be set as 1-4, with 1=HIGHEST and 4=LOWEST or DEFAULT:occam(config-pmap)# priority {1 | 2 | 3 | 4 | default}






Defining a Unicast Rate Limiting Policy Map

Displaying Service Policy Information

The following commands may be used to view information about service policies. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide. All of the following commands may be viewed from User Configuration Mode,

show policy-map [name]: use this command to display policy map configuration.

show policy-map binding: use this command to display policy maps and which Ethernet port and service they are applied to.

show policy-map interface: use this command to display which access profiles policy maps are bound to.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 14: Ethernet Subscriber InterfacesConfiguring an Access Profile

Configuring an Access ProfileAn access profile is a collection of subscriber management attributes. An access profile can be attached to or removed from one or more Ethernet services on Ethernet subscriber ports. Changes to the attributes of an access profile are propagated to the Ethernet service(s) the access profile is attached to. You can create an access profile, and attach it to a set of Ethernet service(s), thus making changes in one place instead of configuring individual Ethernet service(s).

There is no default access profile. When a new access profile is created, it will have default values for all of the parameters except the EPS VLAN. An access profile has to be explicitly attached to each created Ethernet service, as described on page 292.

Configuring an Ethernet 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.

Configure IGMP Parameters

Please refer to Chapter 23, Managed Multicast Via IGMP Proxy on page 479, for more information about configuring IGMP parameters.

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}



Configuring an Access Profile

Configure IPSM Parameters

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

Note: If you are configuring ON 2342s or ON 2343s in the ON 2351 MDU chassis, please refer to Configuring the ARP Reply Gateway Setting When Using the ON 2351 Enclosure on page 293 for information about how to use the mdu command to enable similar functionality as ARP reply gateway on a port-wide basis..

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}

11 Configure the maximum number of MAC addresses that are allowed on a specific service on an Ethernet subscriber interface. The parameters are between one and sixty-four.

This feature provides a way to limit the number of usable devices a customer may have in their home and is typically used when video multicasting is config-ured for a network.

Each VLAN may have up to sixty-four MAC addresses, including dynamic and static. The factory default is four MAC addresses:occam(config-access-profile)# mac limit{1-64}


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 14: Ethernet Subscriber InterfacesConfiguring an Access Profile

12 Enable or disable MAC learning. This feature is enabled by factory default:occam(config-access-profile)# mac-learning {enable|disable}

Configure Service Policy Parameters

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}

15 Exit Access Profile Configuration Mode:occam(config-access-profile)# exit






Copying an Access ProfileTo copy a source profile to a new profile enter the access-copy-profile command from the Global Configuration Mode. If the destination profile indicated in this command does not exist, access-copy-profile creates it. The command then copies all non-default configurations defined for the source profile to the destination profile:occam(config)# access-copy-profile source-profile dest-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.

Deleting an Access ProfileDelete a profile by using the no access-profile command and its profile-name from Global Configuration Mode:occam(config)# no access-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 a port.

Displaying Access Profile InformationUse the show access profile profile-name command from Privileged and User modes to display interface information for a specific profile. If you omit the profile-name argument, this command displays profile information for all existing access profiles.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 14: Ethernet Subscriber InterfacesConfiguring an Ethernet Subscriber Interface and an Ethernet Service

Configuring an Ethernet Subscriber Interface and an Ethernet Service

1 Enter Ethernet Interface Configuration mode specifying an interface by number. The parameters are from one through twenty-two:occam(config)# interface ethernet {1-22}

2 Configure the Ethernet interface to become a subscriber interface:occam(config-if-eth)# eps access subscriber


4 Attach an access profile to the service:occam(config-if-eth-service-<1-5>)# access-profile profile-name

5 Specify a VLAN to which the Ethernet service interface is attached. Incoming traffic must match this VLAN ID in order for this service to be applied to the traffic.

Note: The command match vlan specifies the user ONT VLAN to which an Ethernet service is attached. Use the command eps vlan from Access Profile Configuration mode to define the network VLAN:occam(config-if-eth-service-<1-5>)# match vlan {1-4094}

Use the command no match vlan {1-4094} to remove this VLAN association from an Ethernet Service.

6 Optionally, configure a static MAC/IP address association:occam(config-if-eth-service-<1-5>)# associate {mac-address} [ip-address] [ip-mask] [default gateway]

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

Remove a single static association: occam(config-if-eth-service-<1-5>)# no associate mac-address

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}



Configuring an Ethernet Subscriber Interface and an Ethernet Service

9 Optionally, set maximum number of MAC addresses allowed, overriding the MAC limit set in the attached access profile:occam(config-if-eth-service-<1-5>)# override access-profile mac limit {1-64}

10 Optionally, enable or disable MAC learning, overriding the setting in the attached access profile:occam(config-if-eth-service-<1-5>)# override access-profile mac-learning {enable | disable}



13 Exit Ethernet Interface Configuration mode:occam(config-if-eth)# exit



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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 14: Ethernet Subscriber InterfacesConfiguring an Ethernet Subscriber Interface and an Ethernet Service

The mdu command is entered from on an Ethernet subscriber interface, as shown below:occam(config)# interface ethernet {1-22}occam(config-if-eth)#eps access subscriberoccam(config-if-eth)#mdu

To disable this command, enter the following:occam(config-if-eth)#no mdu



Sample Configuration

Sample ConfigurationThis is a sample Ethernet subscriber interface configuration that follows the network example shown in Figure 14-2.

Voice VLAN 2 Commandsoccam(config)# access-profile voiceoccam(config-access-profile)# mac limit 2

occam(config-access-profile)# eps vlan 21

occam(config-access-profile)# exitoccam(config)# interface ethernet 5occam(config-if-eth)# eps access subscriberoccam(config-if-eth)# service 1

occam(config-if-eth-service-1)# match vlan 22

occam(config-if-eth-service-1)# access-profile voiceoccam(config-if-eth-service-1)# no shutdownoccam(config-if-eth-service-1)# exitoccam(config-if-eth)# no shutdown

Data VLAN 4 Commandsoccam(config)# access-profile dataoccam(config-access-profile)# mac limit 2occam(config-access-profile)# eps vlan 4occam(config-access-profile)# exitoccam(config)# interface ethernet 5occam(config-if-eth)# eps access subscriberoccam(config-if-eth)# service 2occam(config-if-eth-service-2)# match vlan 4occam(config-if-eth-service-2)# access-profile dataoccam(config-if-eth-service-2)# no shutdownoccam(config-if-eth-service-2)# exitoccam(config-if-eth)# no shutdown

Video VLAN 6 Commandsoccam(config)# access-profile videooccam(config-access-profile)# igmp hostoccam(config-access-profile)# mac limit 2occam(config-access-profile)# eps vlan 6occam(config-access-profile)# exitoccam(config)# interface ethernet 5occam(config-if-eth)# eps access subscriberoccam(config-if-eth)# service 3occam(config-if-eth-service-3)# match vlan 6occam(config-if-eth-service-3)# access-profile video

1.Network VLAN2.ONT VLAN


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 14: Ethernet Subscriber InterfacesSample Configuration

occam(config-if-eth-service-3)# no shutdownoccam(config-if-eth-service-3)# exitoccam(config-if-eth)# no shutdown


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 15: Rate Limiting on Ethernet and XG Interfaces

Introduction

Chapter 150Rate Limiting on Ethernet and XG Interfaces

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Configuring Rate Limiting on Egress Ethernet and XG Interfaces. . . . . . . . . . . . . 298Configuring Rate Limiting on Ingress Ethernet Interfaces. . . . . . . . . . . . . . . . . . . 298Verifying Your Rate Limiting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

IntroductionRate 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.

Rate Limiting Unicast Traffic on VLANSThe BLC 6312 and 6314 support access profiles that rate limit unicast traffic on VLANs. This feature is only available on Ethernet subscriber interfaces. If an Ethernet interface has ingress/egress rate limit on it and becomes an Ethernet

Rate Limiting Feature Ethernet XG

Rate Limiting on Egress Interfaces(described on page 298)

yes no

Rate limiting Ingress Interfaces(described on page 298)

yes no

Rate limiting broadcast traffic on ingress interfaces(described on page 298)

yes yes

Rate limiting multicast traffic on ingress interfaces(described on page 299)

yes no

Rate limiting unknown-unicast traffic on ingress interfaces(described on page 299)

yes yes


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 15: Rate Limiting on Ethernet and XG InterfacesConfiguring 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.

Configuring Rate Limiting on Egress Ethernet and XG Interfaces

Use the command egress rate limit {mbits} from Ethernet Configuration mode to configure rate limiting on an egress Ethernet interface. The rate limit is specified in Mbps. The accepted range for both is 0 through 1024. The factory default is 0, indicating no rate limiting.

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 3occam(config-if-eth)# egress rate limit 150

Configuring Rate Limiting on Ingress Ethernet Interfaces

Use the command ingress rate limit {mbits} from Ethernet mode to configure rate limiting on ingress Ethernet interfaces. The rate limit is specified in Mbps. The accepted range for both is 0 through 1000. The factory default is 0, indicating no rate limiting.

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 2occam(config-if-eth)# ingress rate limit 245

Configuring Broadcast Rate Limiting on Ingress Ethernet and XG InterfacesBroadcast frames are flooded to all interfaces that are members of the same VLAN. Use the command ingress broadcast rate limit {pps} from Ethernet and XG Configuration modes to rate limit broadcast frames on an ingress Ethernet interface. The limit is specified in packets per second (pps). The accepted range is 0 through 2,000,000 pps. If the rate limit is set to 0, no rate limiting will be done. The factory default is 0 pps.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 15: Rate Limiting on Ethernet and XG InterfacesConfiguring 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 4occam(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 1occam(config-if-xg)# ingress broadcast rate limit 4600

Configuring Multicast Rate Limiting on an Ingress Ethernet InterfaceMulticast frames are flooded to all interfaces that are members of the multicast destination.

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 8occam(config-if-eth)# ingress multicast rate limit 3800

Configuring Unknown Unicast Rate Limiting on Ingress Ethernet and XG Interfaces

Unicast frames that do not have a matching destination MAC in the forwarding database are known as unknown-unicast frames and they are flooded to all interfaces that are members of the same VLAN.

Use the command ingress unknown-unicast rate limit {pps} from Ethernet and XG Configuration modes to rate limit unknown-unicast frames on an ingress Ethernet interface. The limit is specified in packets per second (pps). The accepted range is 0 through 260,000 pps. The default is 100 pps. If the rate limit is set to 0, no rate limiting will be done.

The following example rate limits unknown-unicast frames on Ethernet interface 9.

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 15: Rate Limiting on Ethernet and XG InterfacesVerifying Your Rate Limiting Configuration

The rate limit is set to 4300 pps.occam(config)# interface ethernet 9occam(config-if-eth)# ingress unknown-unicast rate limit 4300

The following example rate limits unknown-unicast frames on XG interface 1 The rate limit is set to 4000 pps.occam(config)# interface xg 2occam(config-if-xg)# ingress unknown-unicast rate limit 4400

Verifying Your Rate Limiting ConfigurationThe following commands may be used to view your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide.

show interfaces ethernet [Ethernet-interface-number]

show interfaces xg [XG-interface-number]

Use these commands from User and Privileged modes to verify that the speed and duplex modes of the interface are configured correctly. Specify an interface number to receive information about a specific interface or use the commands by themselves to show information on all interfaces.

show interfaces ethernet fiber [Ethernet-interface-number]

show interfaces xg fiber [XG-interface-number]

Use these commands from User and Privileged modes to view information about the fiber Ethernet and XG interfaces. Specify an interface number to receive information about a specific interface or use the commands by themselves to show information on all interfaces.

show interfaces ethernet summary

show interfaces xg summary

Use these commands from User and Privileged modes to view statistics for all Ethernet and XG interfaces in a summarized format.

show interfaces ethernet rates [Ethernet-interface-number]

show interfaces xg rates [XG-interface-number]

Use these commands from User and Privileged modes to view transmit and receive rates. Specify an interface number to receive information about a specific Ethernet interface or use the commands by themselves to show infor-mation on all interfaces. Use the commands clear ethernet rates and clear xg rates to reset Ethernet and XG rate counters.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 15: Rate Limiting on Ethernet and XG Interfaces

Verifying Your Rate Limiting Configuration

show interfaces ethernet max rates [Ethernet-interface-number]

show interfaces xg max rates [XG-interface-number]

Use this command from User and Privileged modes to view maximum transmit and receive rates. Specify an interface number to receive information about a specific interface or use the commands by themselves to show information on all interfaces. Use the commands clear ethernet rates and clear xg rates to reset Ethernet and XG rate counters.

show running-config interfaces ethernet {Ethernet-interface-number}

show running-config interfaces xg {XG-interface-number}

Use these commands from Privileged mode to display information about an Ethernet or XG interface in the running configuration.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 15: Rate Limiting on Ethernet and XG InterfacesVerifying Your Rate Limiting Configuration


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link Aggregation

Introduction

Chapter 16Configuring Link Aggregation

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Configuring a LAG Out Of a VPT That Will Connect To A Head End Router. . . . . 306Configuring a LAG As an Interconnect Between Two BLC 6001 Chassis . . . . . . . 309Assigning Ethernet Interfaces To a LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Sample Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Viewing Your LAG Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

IntroductionOverview

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationIntroduction

Figure 16-1: Example of LAGs In A BLC Network

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.

BLC 6012 Chassis: No restrictions on any fiber/copper port being configured as a LAG member.

BLC 6012i Chassis: Restrictions on Ethernet ports 1-6.

VPT on PG 1 VPT on PG 2

HEAD ENDROUTER

ROUTER

VPS on PG 2

LAG 4"igmp host"

LAG 2"igmp router"

LAG 1"igmp router"

LAG 2"igmp passthrough"



Introduction

Supported Chassis Wiring ArrangementsThe only chassis arrangement that will support LAG on 10/100/1000BaseT ports on bookend Blades is a BLC 6012G chassis. The 6012P chassis has only a single 10/100/1000BaseT port unassigned and the BLC 6012F and 6012i consume all bookend copper ports.

Supported BLCsLAG is only supported on the following BLCs:

BLC 6450

BLC 6314

BLC 6312


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationConfiguring a LAG Out Of a VPT That Will Connect To A Head End Router

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}



Configuring a LAG Out Of a VPT That Will Connect To A Head End Router

4 Configure IGMP settings on the LAG group:

a If there is video traffic on the EPS ring, configure the LAG group as an IGMP router group. The optional IP address parameter is the source IP address for IGMP packets:occam(config-if-lag)# igmp router {IP-address}

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}

4 Configure the IGMP protocol 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 command no igmp version to return the setting to the default, IGMP v2.:occam(config-if-lag)# igmp version {v2 | v3}

5 Configure the load balancing between the LAG links.

The “default” load balancing option on the LAG is based on the source (src) + destination (dst) MAC addresses. Occam Networks recommends that you use the default setting.

The “src-mac” option configures the source MAC address as the basis for load balancing between the links.

The “dst-mac” option configures the destination MAC address as the basis for load balancing:

occam(config-if-lag)# load-balance {src-mac | dst-mac | default}


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationConfiguring a LAG Out Of a VPT That Will Connect To A Head End Router

6 Enable the LAG:occam(config-if-lag)# no shutdown

7 (Optional) Attach informational text to the LAG:occam(config-if-lag)# info {key} {informative-text}

For example:

occam(config-if-lag)# info router router_34

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>, '?', '!'.

8 Exit LAG Configuration mode:occam(config-if-lag)# exit

9 Repeat the above steps to configure other LAGs.

10 Please turn to the section Assigning Ethernet Interfaces To a LAG on page 314 to complete your LAG configuration.

Clearing the Configuration of a LAG

1 Specify the LAG number that has the configuration you wish to clear:occam(config)# interface lag {LAG-number}

2 Clear the LAG’s configuration:occam(config-if-lag)# no config




Configuring a LAG As an Interconnect Between Two BLC 6001 Chassis

Configuring a LAG As an Interconnect Between Two BLC 6001 Chassis

The BLC’s software will verify that the VPTs are located in BLC 6001 chassis’ before allowing configuration of two Ethernet ports to act as a single resilient interconnect Link.


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}

3 Configure the LAG as an interconnect between the VPT to another VPT in another BLC 6001 chassis:occam(config)# eps ring interconnect

4 Configure the LAG as an IGMP passthrough group, enabling any multicast traffic received to be forwarded out all other passthrough interfaces. The optional IP address parameter is the source IP address for IGMP packets:occam(config-if-lag)# igmp passthrough [IP-address]


6 Configure the IGMP protocol 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 command no igmp version to return the setting to the default, IGMP v2:occam(config-if-lag)# igmp version {v2 | v3}


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationConfiguring 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>, '?', '!'.





Configuring a LAG Out Of a VPS

Configuring a LAG Out Of a VPS1 Enter Global Configuration Mode:


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}

4 Configure the LAG as an IGMP host:occam(config-if-lag)# igmp host


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationConfiguring a LAG Out Of a VPS


6 Configure the IGMP protocol 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 command no igmp version to return the setting to the default, IGMP v2.:occam(config-if-lag)# igmp version {v2 | v3}








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 Repeat the above steps to configure other LAGs.



Configuring a LAG Out Of a VPS



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationAssigning Ethernet Interfaces To a LAG

Assigning Ethernet Interfaces To a LAGYou must configure a LAG before you assign Ethernet interfaces to the LAG. LAG configuration is described in the sections Configuring a LAG Out Of a VPT That Will Connect To A Head End Router on page 306 and Configuring a LAG As an Interconnect Between Two BLC 6001 Chassis on page 309.


2 Enter Ethernet Interface or 10 GigE Interface Configuration mode and specify an interface number to configure as part of a LAG. Up to eight interfaces may be added to a LAG.

Note: You may mix copper and fiber ports on the same LAG, but all LAG members must all have the same speed.

Note: If you need to change the medium or set the speed of an Ethernet interface, you must do so before adding it to a LAG.occam(config)# interface ethernet {Ethernet-interface-number}


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}





6 Repeat the above steps as many times as necessary.



Sample Configurations

Sample ConfigurationsSample 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 1occam(config-if-lag)# eps access tagged routeroccam(config-if-lag)# igmp routeroccam(config-if-lag)# no shutdownoccam(config-if-lag)# exit

occam(config)# interface ethernet 1occam(config-if-eth)# lag-interface 1occam(config-if-eth)# no shutdownoccam(config-if-eth)# exit




Sample Configuration Of a LAG Interconnect Between BLC 6001 ChassisThis is an example of a simple configuration of a LAG interconnect between BLC 6001 chassis:occam(config)# interface lag 2occam(config-if-lag)# eps ring interconnectoccam(config-if-lag)# igmp passthroughoccam(config-if-lag)# no shutdownoccam(config-if-lag)# exit

occam(config)# interface xg 1occam(config-if-xg)# lag-interface 2occam(config-if-xg)# no shutdownoccam(config-if-xg)# exit

occam(config)# interface xg 2


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationSample Configurations

occam(config-if-xg)# lag-interface 2occam(config-if-xg)# no shutdownoccam(config-if-xg)# exit



Viewing Your LAG Configuration Settings

Viewing Your LAG Configuration SettingsYou may use the following commands to view your LAG configuration:

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.

show running-config lag {lag-number}: sample output for this command is shown on page 319.

Information about LAGs may also be viewed by entering other commands. Some of these commands are:

show eps

show eps map

show interfaces ethernet summary

show interfaces xg summary

show multicast port

“show bridge interface lag” CommandThe show bridge interface lag {1-4} command displays bridge information about a specific LAG. Other show bridge commands may also be used to display information about LAGs.Sample output of the show bridge interface lag 1 command is shown below:

For example:

occam#show bridge interfaces lag 1Hardware switch MAC Table: Address Port Static VLAN Path Group Source

00:00:0c:07:ac:00 lag 1 No 2 PG1 ACCESS 00:02:86:00:00:71 lag 1 No 2 PG1 ACCESS 00:02:86:00:09:73 lag 1 No 2 PG1 ACCESS 00:02:86:00:0b:56 lag 1 No 2 PG1 ACCESS 00:02:86:00:0b:82 lag 1 No 2 PG1 ACCESS 00:02:86:00:0b:98 lag 1 No 2 PG1 ACCESS 00:02:86:00:0b:9d lag 1 No 2 PG1 ACCESS 00:02:86:00:0b:a9 lag 1 No 2 PG1 ACCESS 00:02:86:00:0b:b4 lag 1 No 2 PG1 ACCESS 00:02:86:00:0b:ca lag 1 No 2 PG1 ACCESS <output truncated>


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationViewing Your LAG Configuration Settings

“show interfaces lag” CommandThe show interfaces lag command displays output for all or a specified LAG.

Sample output for this command is shown below:

Table 16-1: show interfaces lag Command Field Descriptions

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.

EPSOper state

This column displays different information 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.

occam#show interfaces lag LAG # |Admn|EPS |IGMP|LDBAL| | | | | | | |Oper |Fwd |Speed|Rx |Tx |Rx |Tx |Rx |Tx members |stat|stat |stat| |pkts |pkts |err|err|% |% ------------|----|---------|----|-----|----------|----------|---|---|---|--- lag 1 |up |tagged |RTR |DEF |51268583 |5972634 |0 |0 | | ------------|----|---------|----|-----|----------|----------|---|---|---|--- ethernet 3 |up |up |FWD |1000 |313012 |30626 |0 |0 |0 |0 ethernet 4 |up |up |FWD |1000 |171061 |5909180 |0 |0 |0 |98 ethernet 5 |up |up |FWD |1000 |50784510 |32828 |0 |0 |99 |0 ------------|----|---------|----|-----|----------|----------|---|---|---|--- lag 2 |up |INTC |PASS|DEF |56342798 |107571079 |0 |0 | | ------------|----|---------|----|-----|----------|----------|---|---|---|--- xg 1 |up |up |FWD |10000|32358385 |56526035 |0 |0 |57 |52 xg 2 |up |up |FWD |10000|23984413 |51045044 |0 |0 |42 |47 ------------|----|---------|----|-----|----------|----------|---|---|---|--- lag 3 |up |dblQ 101 |PASS|DEF |57636241 |6361192 |0 |0 | | ------------|----|---------|----|-----|----------|----------|---|---|---|--- ethernet 16|up |up |FWD |1000 |3075358 |25012 |0 |0 |5 |0 ethernet 17|up |up |FWD |1000 |24403339 |6091833 |0 |0 |42 |95 ethernet 20|up |up |FWD |1000 |3244730 |220211 |0 |0 |5 |3 ethernet 22|up |up |FWD |1000 |26912814 |19025 |0 |0 |46 |0 ------------|----|---------|----|-----|----------|----------|---|---|---|--- lag 4 |up |dblQ 101 |PASS|DEF |6087059 |51331760 |0 |0 | | ------------|----|---------|----|-----|----------|----------|---|---|---|--- ethernet 1 |up |up |FWD |1000 |5957628 |25203588 |0 |0 |97 |49 ethernet 2 |up |up |FWD |1000 |129431 |26128172 |0 |0 |2 |50occam#



Viewing Your LAG Configuration Settings

“show running-config lag” CommandThe show running-config lag {1-4} command displays information about a specified LAG in the running configuration. Sample output is shown below:occam#show running-config interfaces lag 1interface lag 1 eps access tagged uplink igmp router no shutdownexitoccam#

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.

Field Description


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 16: Configuring Link AggregationViewing Your LAG Configuration Settings


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 17: Configuring Span Powered T1 Lines

Chapter 17Configuring Span Powered T1 Lines

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322T1 Span Power Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Other T1 Line Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Viewing Your Powered T1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328


Warning: Span powered T1 lines should only be installed by trained and qualified personnel. Standard procedure for span powered T1 lines should apply. Power across span powered T1 lines can reach 130 volts DC from pair to pair.

Any exposed terminal should be insulated and marked with appropriate precautions. Typically this protection panel or insulation is red.

The voltage measurement of the span powering should be measured between the TRANSMIT pair and the RECEIVE pair of the T1 circuit. The power is applied between the center-taps of the transformers on the Transmit and Receive pairs. Therefore, the voltage across the T/R of the Transmit pair or T/R of the Receive pair will be quite low and measured in millivolts. However, power across span powered T1 lines can reach 130 volts DC from pair to pair.

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.

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 17: Configuring Span Powered T1 LinesIntroduction

IntroductionThe 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.

Table 17-1: Span Powered T1 Interface Pinout Definition



Port Description Pin Pair (Ring-Tip)












T1 Span Power Commands

T1 Span Power CommandsUse the service-module t1 power commands from Serial Interface configuration mode to configure span powered T1 lines.

Power CommandsUse 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:

occam(config-if-serial)# service-module t1 power enableoccam(config-if-serial)# service-module t1 power noneoccam(config-if-serial)# no service-module t1 power

Power Loop CommandsUse the following commands to enable or disable a power loop on the T1 line. Use the power loop command at the last BLC before the customer premises:

occam(config-if-serial)# service-module t1 power loopoccam(config-if-serial)# no service-module t1 power loop

Figure 17-1: Span Powered T1 Line Network Design

BLC "B"RESIDENCE

= T1 Repeater (maximum of 5 may be used between BLCs)

BLC "A" configures span powered T1 line with command:Occam(config-if-serial)# service-module t1 power enable

BLC "B" configures span powered T1 line with command:Occam(config-if-serial)# service-module t1 power loop

RRR

R

BLC "A"

SPANPOWERED

T1 LINE

RT RT

CO


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 17: Configuring Span Powered T1 LinesOther T1 Line Configuration Commands

Other T1 Line Configuration CommandsThis section describes other commands (besides the ones used described in the previous section) that may be used to configure span powered T1 lines.



2 Enter Serial Interface Configuration Mode, specifying a slot and a T1 interface port number:occam(config)# interface serial <slot>/<port 1-x>

3 Optionally, configure the T1 with the following commands:

Feature Command and Command Function

AIS/Blue alarm Enable a AIS/Blue alarm:occam(config-if-serial)# service-module t1 ais-alarm-enable

FDL alarms Enable FDL alarms:occam(config-if-serial)# service-module t1 alarm-mode

Clock Enable or disable the adapter internal clock:occam(config-if-serial)# service-module t1 clock source internaloccam(config-if-serial)# no service-module t1 clock source internal

Cause this T1 to receive or not receive clocking from external equipment via the line:occam(config-if-serial)# service-module t1 clock source lineoccam(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

!



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 ansioccam(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 attoccam(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 bothoccam(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 slc96rtoccam(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.

Configure the T1 to use or not use ESF as the framing format. occam(config-if-serial)# service-module t1 framing esfoccam(config-if-serial)# no service-module t1 framing esf

Enable or disable the T1 to use SF as the framing format. occam(config-if-serial)# service-module t1 framing sfoccam(config-if-serial)# no service-module t1 framing sf

Enable or disable the T1 to use SLC-96 as the framing format:occam(config-if-serial)# service-module t1 framing slc96occam(config-if-serial)# no service-module t1 framing slc96

Enable or disable the T1 to use an unframed format. occam(config-if-serial)# service-module t1 framing unframedoccam(config-if-serial)# no service-module t1 framing unframed

Line Build Out (LBO) Format

Occam Networks recommends that no Line Build Out (LBO) format be spec-ified when span power is enabled. This is the factory default and means that packets are transmitted without decreasing outgoing signal strength.Occam(config-if-serial)# service-module t1 lbo none

You may also use the “no” form of the command to specify the factory default:Occam(config-if-serial)# no service-module t1 lbo


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 17: Configuring Span Powered T1 LinesOther T1 Line Configuration Commands

Line Coding Format

Specify the line code. Your T1 service provider determines if your circuit 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 AMI as the linecode format:occam(config-if-serial)# service-module t1 linecode amioccam(config-if-serial)# no service-module t1 linecode ami

Enable or disable B8ZS as the linecode format. occam(config-if-serial)# service-module t1 linecode b8zsoccam(config-if-serial)# no service-module t1 linecode b8zs

Local Loopback Enable or disable “full” as the local loopback format. This option is akin to a “line loopback”. The data does not go through the framer inside the QFALC chip:occam(config-if-serial)# service-module t1 local-loopback fulloccam(config-if-serial)# no service-module t1 local-loopback full

Enable or disable “internal” as the local loopback format. This option is primarily used to diagnose CES problems and for development. Data goes through the BLC internal system and doesn't go through the framer:occam(config-if-serial)# service-module t1 local-loopback internal

occam(config-if-serial)# no service-module t1 local-loopback internal

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

occam(config-if-serial)# no service-module t1 local-loopback payload

T1 power and power loop

Enable or disable a 60mA current source on the T1 line so as to provide power to line repeaters that will extend the line length:occam(config-if-serial)# service-module t1 power enableoccam(config-if-serial)# service-module t1 power noneoccam(config-if-serial)# no service-module t1 power

Enable and disable a power loop on the T1 line:occam(config-if-serial)# service-module t1 power loopoccam(config-if-serial)# no service-module t1 power loop



Other T1 Line Configuration Commands

4 Enable the T1 port:Occam(config-if-serial)# no shutdown

5 Exit Serial Interface Configuration Mode and return to Global Configuration Mode:Occam(config-if-serial)# exit

6 Repeat steps 2 through 5 for each T1 interface to be used.

7 Exit Global Configuration Mode and save your configuration:Occam(config)# exitOccam# copy running-config startup-config

Remote/Yellow alarm

Remote alarms are transmitted by the BLC when it detects an alarm condi-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 generation and detection of remote (yellow) alarms:occam(config-if-serial)# service-module t1 remote-alarm-enable

occam(config-if-serial)# no service-module t1 remote-alarm-enable

Remote Loopback

T1 Loopback allows either end to loop the lines on a T1 so that either the local side or the remote side of the T1 can perform T1 line testing, e.g., to determine the quality of the T1. Loopback testing allows service providers to troubleshoot T1 lines without sending someone out into the field. A loop-back code can be sent on the line and then read back at the central office to see if there are any errors or problems.

Enables or disables the T1 to use “full” as the remote loopback code used to transmit or accept CSU loopback requests:occam(config-if-serial)# service-module t1 remote-loopback full

occam(config-if-serial)# no service-module t1 remote-loopback full

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

occam(config-if-serial)# no service-module t1 remote-loopback payload v54


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 17: Configuring Span Powered T1 LinesViewing Your Powered T1 Configuration

Viewing Your Powered T1 ConfigurationT1 power status and current detection can be monitored by entering the command show service-module t1 serial, as shown in the example below:

Shows the T1 power is enabled. Otheroptions are:T1 power is disabledT1 power is looped

Occam#show service-module t1 serial 1

Service-module serial 1: Module type is T1 Serial 1 is up, operational state is up Receiver alarm status is noalarm. Framing is ESF, Line Code is B8ZS, Current clock source is LINE, Line build out is CSU_0, T1 power is enabled, T1 power is detected. Facilities Data Link support is NONE, Alarm Mode is WP1B, Channelization is enabled, Mode is channelized No CES connection enabled. DS0s in clear channel mode are: 12 24 Local Loopback is set to noloop. Remote Alarm is set to DISABLE, Remote Loopback is set to sendnocode. AIS Alarm is set to DISABLE Net bandwidth is 1536 Kbits/sec. Data coding is set to normal. Last clearing of alarm counters never loss of signal : 0, loss of frame : 0, AIS alarm : 0, Remote alarm : 0,

Shows the T1 power is detected. Otheroptions are:T1 power is not detected


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 18: Configuring DSL Interfaces

Introduction

Chapter 18Configuring DSL Interfaces

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329ADSL2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329DSL Interface Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Configuring a DSL Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Configuring an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Enabling and Configuring a DSL Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358Configuring a DSL Bonding Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Enabling and Configuring Service(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

IntroductionThis chapter how to configure DSL interfaces on the following BLCs:

BLC 6212-02: 48 ADSL2+ ports

BLC 6214: 48 ADSL2+ports

BLC 6244: 24 ADSL2+ ports



BLC 6252-03: 48 ADSL2+ ports

ADSL2 FeaturesBonding

ADSL2 bonding allows one ATM stream to be split over two ADSL2 lines. Bonding configuration is described on page 356.

Annex L (Extended Reach)Annex L is a standard ADSL2 feature that provides for extended reach beyond the nominal 18,000 ft. limit of ADSL with 26 gauge wire. Most ADSL2 modems support Annex L and will automatically transition from the default North American mode (Annex A) to Annex L. This transition occurs on copper plant longer than 15,000 ft.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesADSL2 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 MAnnex 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.

DSL Line Retransmission Error RecoveryRelease 5.5 introduces support for DSL Line Retransmission Error Recovery. This impulse noise protection technology reduces BER or packet-loss on ADSL2+ or VDSL2 lines to extend service by allowing either higher bandwidth or longer reach with lower delay.

In this release, if DSL Line Retransmission Error Recovery is activated, Seamless Rate Adaptation (SRA) is disabled.

This feature is configured through the DSL profile. Configuration steps are described on page 338.

SRA (Seamless Rate Adaptation)SRA software allows modems to make seamless data transfer rate changes to avoid dropping a connection. Modems are affected by cross talk from adjacent lines, as well as by other interference such as temperature changes and radio signals. Any interference on the connection can cause a modem to retrain on another connection and drop the existing connection. SRA makes dynamic data transfer rate changes to accommodate temporary noise conditions on the line thus preventing dropped connections. SRA configuration commands are shown on page 346.



ADSL2 Features

SELT and DELTOccam Networks provides the ability to test ADSL2+ lines with Dual Ended Line Testing (DELT) and Single Ended Line Testing (SELT). 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.

SELT and DELT are described in Chapter 42, ADSL2+ Line Testing- SELT, DELT and MLT on page 789.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesDSL Interface Configuration Overview

DSL Interface Configuration OverviewDSL interfaces are configured by creating access profiles and attaching them to services. Up to four services may be configured on a DSL interface. There are no default services.

In detail, the steps to configure a DSL interface are as follows:

Optionally configure and enable a DSL profile (page 334)

A DSL profile is a named list of DSL line specific parameters. This step is optional if you wish to keep the default settings.

Optionally configure a policy map to rate limit unicast traffic on a VLAN to a specified rate in Kbps (page 350)

Configure and enable an access profile (page 350).

You may configure the following parameters 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.

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



DSL Interface Configuration Overview

Figure 18-1: DSL Bonding Group or Interface Configuration Steps

Configure aservice

Create anaccess profile

Specify subscriber(ONT) VLAN specified


rate limit unicasttraffic coming to BLC(service-policy input)

Specify network(EPS) VLAN ID

(Optional)Define MAC/IP

association

DSL interfaceor bonding group

Create a policy mapto rate limit unicast

traffic

Configure IGMP andIPSM parameters

Only one access profilemay be attached to a

service

Up to four DSL servicesmay be attached to each

DSL subscriber port

Match is made here betweenthe network VLAN and the

subscriber VLAN


rate limit unicast trafficcoming from BLC

(service-policy output)

Configure a DSLprofile

(Optional if keepingdefault settings)


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesConfiguring a DSL Profile

Configuring a DSL ProfileYou can configure DSL line specific parameters by attaching a profile to it. A profile is a named list of configuration parameters with a value assigned to each parameter. All interfaces have attached profiles. If you do not assign a profile to an interface, the system, by default, assigns the profile named "default" to that interface.

Most of the attributes of a DSL profile are related to either the traffic, physical layer, or test characteristic of the line. DSL Profiles contain all the information required for configuring the Layer 1 DSL connection.

When a parameter in a profile is changed, the value of that parameter on all interfaces attached to that profile is also changed.

If an existing profile is modified, that change takes effect on every DSL interface linked to that profile. To change a single interface or a subset of interfaces, copy the profile, change the desired parameters, and then assign the new profile to the desired interfaces. There can be one profile for many interfaces, but one interface cannot have more than one profile.

Recommended DSL profile Settings

The recommended DSL profile for IP video is shown on page 347.

The recommended DSL profile for non-video services is shown on page 347.

Default DSL Profile For ADSL2+ BLCsThe DSL profile below is for the following BLCs:

occam# show dsl profile defaultdsl profile default : DMT profile parameters : Transmission System : AUTO BitRates : Maximum downstream : 32000 kbps upstream : 2048 kbps Minimum downstream : 32 kbps upstream : 32 kbps Snr Margin : Target : downstream : 6.0 dB upstream : 6.0 dB Maximum : downstream : 9.0 dB upstream : 9.0 dB Minimum : downstream : 2.0 dB upstream : 2.0 dB Downshift : downstream : 4.0 dB upstream : 4.0 dB upshift : downstream : 7.0 dB upstream : 7.0 dB Maximum Delay : downstream : 20 ms upstream : 20 ms Impulse Noise Protection : downstream : 1 upstream : 1 Trellis Coding : enabled Reed Solomon : enabled S=1/2 : enabled Bit Swapping : downstream : enabled upstream : enabled SRA :

BLC 6212-02 BLC 6246

BLC 6214 BLC 6252-03

BLC 6244



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



Creating and Attaching a Profile to an Interface

1 Enter Global Configuration Mode:Occam# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Occam(config)#

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.

4 Exit from DSL Profile Configuration Mode:Occam(config-dsl-profile)# exit

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}

6 Attach the profile to the interface by its name:Occam(config-if-dsl)# dsl profile {dsl-profile-name}

7 Exit from DSL Configuration mode:Occam(config-if-dsl)# exit

8 Exit from Global Configuration mode:Occam(config)# exit

9 Save your configuration:Occam# copy running-config startup-configBuilding configuration....

Commands Page Number

Commands to configure the DSL Line Retransmission Error Recovery feature

Page 338

Commands to configure upstream and downstream maximum and minimum bitrates.

Page 339

Commands to configure traffic related values. Page 340

Commands to enable and disable bitswapping. Page 342

Commands to configure SNR margins. Page 343

Commands to configure test related value. Page 346

Commands to configure SRA values. Page 346




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.



Commands to Configure the DSL Line Retransmission Error Recovery Feature

Release 5.5 introduces support for DSL Line Retransmission Error Recovery. In this release, if the DSL Line Retransmission Error Recovery is activated, Seamless Rate Adaptation (SRA) is disabled.

Table 18-1 shows how to configure this feature.

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 retransmissionno dmt retransmission

Enables the DSL Line Retransmission Error Recovery feature. The "no" form of this command disables this feature. This is the factory default setting.

dmt retransmission reed-solomon{Kbps} no dmt retransmission reed-solomon

Configures the minimum 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.




Commands to Configure Upstream and Downstream Maximum and Minimum Bitrates

Tables 18-2 shows traffic related values for the default DSL profile and the commands to change the default values. On certain commands, different BLC models have different parameters. These differences will be noted. If not noted, the parameters shown apply to all BLC models.

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.

Table 18-2: Commands to Configure Upstream and Downstream Maximum and Minimum Bitrates

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.

Command Description

dmt bitrate minimum downstream {Kbps} no dmt bitrate minimum downstream

Sets the minimum downstream bitrate in 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} no dmt bitrate minimum upstream

Sets the minimum upstream bitrate to a value in Kbps. The parameters are between 0 and 12000 Kbps and the factory default value is 32 Kbps.

dmt bitrate maximum downstream disable {Kbps}no dmt bitrate maximum downstream disable

Disables S=1/2 and sets the maximum downstream bitrate to a value in Kbps. 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} no dmt bitrate maximum downstream enable

Enables S=1/2 and sets the maximum 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} no dmt bitrate maximum upstream enable

Sets the minimum upstream bitrate to a value in Kbps. The parameters are between 40 and 16000 Kbps and the default value is 2048 Kbps.

!



Commands to Configure Traffic Related Values

Table 18-3: Commands to Configure Traffic Related Values and Configuration

Command Description

dmt impulse-noise-protection downstream {0-17}no dmt impulse-noise-protection downstream

dmt impulse-noise-protection upstream {0-17}no dmt impulse-noise-protection upstream

Sets the minimum number of DMT frames/symbols (INP/S parameter) per codeword for downstream or upstream impulse noise protection.

Note: A minimum value of 1 MUST be set for the command minimum impulse-noise-protection downstream when the the DSL Line Retransmission Error Recovery feature is enabled.The factory default for upstream and downstream settings is 1 (S=1/2).

0: no protection (for fast path configuration)1: noise protection (INP/S=1/2)2: noise protection (INP/S=1)3: noise protection (INP/S=2)4: noise protection (INP/S=3)5: more noise protection (S=4)*6: more noise protection (S=5)*7: noise protection (INP/S=6)8: noise protection (INP/S=7)9: noise protection (INP/S=8)10: noise protection (INP/S=9)11: noise protection (INP/S=10)12: noise protection (INP/S=11)13: noise protection (INP/S=12)14: noise protection (INP/S=13)15: noise protection (INP/S=14)16: noise protection (INP/S=15)17 noise protection (INP/S=16)




dmt maximum-delay downstream {0-20}no dmt maximum-delay downstream

dmt maximum-delay upstream {0-20}no dmt maximum-delay upstream

Sets the maximum allowed delay down-stream and upstream to a value between 0 and 20 ms. The factory defaults for upstream and downstream are 20 ms.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, G.992_3_M, G.992_5, G.992_5_M, ANSI_T1. AUTO}no dmt operating-mode

Sets the operational modeG.992_1: G.992.1G.992_3: G.992.3G.992_3_M: G.992.3_AnnexMG.992_5: G.992.5G.992_5_M: G.992.5_AnnexMANSI_T1.413: T1.413AUTO: Automatic selection. This is the factory default.Annex L is enabled on the BLC with Auto and G.992_3 line protocols.

Note: Occam Network recommends that you configure the operating mode as G.992_5 when you use multiple bonding groups on the same BLC.



Commands to Enable/Disable BitswappingBitswapping reallocates the bits in DSL bins, so as to maintain an acceptable signal to noise margin for each bin. You must use a modem with bit swapping capabilities in order to implement this feature.

Table 18-4: Commands to Enable/Disable Bitswapping

Command Description

dmt bitswap downstreamno dmt bitswap downstream

Enables or disables downstream bitswapping. This feature is enabled by default.

dmt bitswap upstreamno dmt bitswap upstream

Enables or disables upstream bitswapping. This feature is enabled by default.




Commands to Set DSL Profile SNR Margin ValuesTo maintain service in a dynamic environment, some margin must be maintained above the minimum signal to noise ratio (SNR) required. This is known as the SNR margin.

Table 18-5: Commands to Configure DSL Profile SNR Margin Values

Command Description

dmt snr-margin target downstream {0 - 31}no dmt snr-margin target downstream

dmt snr-margin target upstream {0 - 31}no dmt snr-margin target upstream

Sets the SNR (Signal to Noise) target down-stream and upstream margins to a value between 0 and 31 dB. The target margins define the SNR margins that must be available when the handshake process is determining the capability of each subcarrier.The the factory default is 6 dB.

dmt snr-margin maximum downstream {0 - 31}no dmt snr-margin maximum downstream

dmt snr-margin maximum upstream {0 - 31}no dmt snr-margin maximum upstream

These commands define the amount of margin above target that must be present before power cutback kicks in.They set the SNR (Signal to Noise) maximum downstream and upstream margins to values between 0 and 31 dB (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.

The factory default for upstream and downstream settings is 9 dB.

dmt snr-margin minimum downstream {0 - 31}/no dmt snr-margin minimum downstream

dmt snr-margin minimum upstream {0 - 31}/no dmt snr-margin minimum upstream

Sets the SNR (Signal to Noise) minimum downstream and upstream margins to values between 0 and 31 dB (decibels). The factory default for upstream and downstream settings is 2 dB.



dmt snr-margin down-shift downstream {0 - 31}no dmt snr-margin down-shift downstream

Sets the downshift downstream SNR margin to a value between 0 and 31 dB. 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}no dmt snr-margin up-shift downstream

Sets the upshift downstream SNR margin 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}no dmt snr-margin down-shift upstream

Sets the downshift upstream SNR margin 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}no dmt snr-margin up-shift upstream

Sets the upshift upstream SNR margin to a value between 0 and 31 dB. The command no dmt snr-margin up-shift upstream resets the margin to 8 dB, the factory default.

Command Description




dmt snr-margin downstream {0 - 31} {0 - 31}no dmt snr-margin downstream

Sets the downstream SNR minimum and 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}no dmt snr-margin upstream

Sets the upstream SNR minimum and 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.

Command Description



Commands to Set DSL Profile Test Related Values

Table 18-6: DSL Profile Default Test Related Values and Configuration Commands

Commands to Set SRA ValuesSRA allows the line rate to dynamically adapt to the current line condition without retraining the line by automatically maximizing the available bandwidth on the line. On the BLC, SRA is disabled by default and the normal rate adaptation is turned on.

Table 18-7: Commands to Configure DSL Profile SRA Values

Command Description

dmt encoding trellisno dmt encoding trellis

Enables trellis coding. Trellis coding is enabled by 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}no dmt sra minimum-downshift-interval

dmt sra minimum-upshift-interval {0-16383}no dmt sra minimum-upshift-interval

Sets the minimum downshift and upshift Rate Adaptation (RA) interval to a value between 0 and 16383 seconds. The factory default setting for minimum downshift and upshift RA is 30 seconds.




Recommended DSL Profile Settings

Recommended DSL Profile for IP Videodsl-profile VIDEOdmt operating-mode G.992.5dmt encoding trellisdmt reed-solomondmt bitswap downstreamdmt bitswap upstreamdmt sradmt sra minimum-downshift-interval 30dmt sra minimum-upshift-interval 30dmt bitrate maximum downstream disable <total DS bitrate required for service>dmt bitrate maximum upstream <total US bitrate required for service>dmt bitrate minimum downstream <Minimum DS bitrate required for video>dmt bitrate minimum upstream <Minimum US bitrate required for video>dmt impulse-noise-protection downstream 3dmt maximum-delay downstream 20dmt snr-margin maximum downstream 31dmt snr-margin up-shift downstream 8.5dmt snr-margin target downstream 8dmt snr-margin down-shift downstream 6dmt snr-margin minimum downstream 2dmt impulse-noise-protection upstream 0dmt maximum-delay upstream 0dmt snr-margin maximum upstream 31dmt snr-margin up-shift upstream 20.5dmt snr-margin target upstream 20dmt snr-margin down-shift upstream 18dmt snr-margin minimum upstream 2

Recommended DSL Profile for Non-Video Servicesdsl-profile HSIAdmt operating-mode G.992.5dmt encoding trellisdmt reed-solomondmt bitswap downstreamdmt bitswap upstreamdmt sradmt sra minimum-downshift-interval 30dmt sra minimum-upshift-interval 30dmt bitrate maximum downstream disable <total DS bitrate required for service>dmt bitrate maximum upstream <total US bitrate required for service>dmt bitrate minimum downstream 32dmt bitrate minimum upstream 32dmt impulse-noise-protection downstream 0dmt maximum-delay downstream 0dmt snr-margin maximum downstream 20dmt snr-margin up-shift downstream 7



dmt snr-margin target downstream 6dmt snr-margin down-shift downstream 4dmt snr-margin minimum downstream 2dmt impulse-noise-protection upstream 0dmt maximum-delay upstream 0dmt snr-margin maximum upstream 20dmt snr-margin up-shift upstream 7dmt snr-margin target upstream 6dmt snr-margin down-shift upstream 4dmt snr-margin minimum upstream 2

Detaching a ProfileTo 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}

2 Detach the profile from the interface.

Note: By default, the profile “default” is attached to all interfaces:Occam(config-if-dsl)# no dsl profile

Deleting a ProfileDelete 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 ProfileTo 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.




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.

Viewing Information About DSL Profilesshow dsl profile [profile-name]: use this command from User and Privileged modes to display information about a profile. If you omit the profile-name argument, this command displays profile information for all existing DSL profiles.

Output from this command is shown on page 334.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesConfiguring an Access Profile

Configuring an Access ProfileAn access profile is a collection of subscriber management attributes. It can be attached to or removed from services on DSL ports or bonding groups. Changes to the attributes of an access profile are propagated to the service(s) the access profile is attached to. You can create an access profile, and attach it to a set of services, thus making changes in one place instead of configuring individual services.

When a system boots up, a default access profile is created with the name “default”. All access profiles can be created/deleted/duplicated, except for this default profile. An access profile cannot be deleted if it is attached to a service.

This section describes how to:

configure a unicast rate limiting policy map (page 350)

configure an access profile (page 351)

copy an access profile (page 355)

delete an access profile (page 355)

The section Enabling and Configuring a DSL Interface on page 358 describes how to attach an access profile to a service. The section Detaching an Access Profile From a Service on page 354 describes how to detach an access profile from a service.

Defining a Unicast Rate Limiting Policy Map


2 Configure the policy map to rate-limit unicast traffic on a VLAN to a specified rate in Mbps with 3 decimal point precision:occam(config-pmap)# rate-limit {0.1-32}

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}







Displaying Policy Map Information

The following commands may be used to view information about policies maps. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide. All of the following commands may be viewed from User Configuration Mode,

show policy-map [name]: use this command to display policy map configuration.

show policy-map binding: use this command to display policy maps and which Ethernet port and service they are applied to.

show policy-map interface: use this command to display which to access profiles policy maps are bound.



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}

Configure Service Policy Parameters

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}



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}


Please refer to Chapter 23, Managed Multicast Via IGMP Proxy on page 479, for more information about configuring IGMP parameters.

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}

Configure IPSM Parameters

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:


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:




occam(config-access-profile)# blacklist rate limit{arp|dhcp|igmp} {PPS} {1-30} {1-10} {shutdown|alarm}

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}

13 Configure the maximum number of MAC addresses that are allowed on a specific service on an subscriber interface. The parameters are between one and sixty-four.

This feature provides a way to limit the number of usable devices a customer may have in their home and is typically used when video multicasting is configured for a network.

Each VLAN may have up to sixty-four MAC addresses, including dynamic and static. The factory default is four MAC addresses:occam(config-access-profile)# mac limit{1-64}

14 Enable or disable MAC learning. This feature is enabled by factory default:occam(config-access-profile)# mac-learning {enable|disable}

PPPoA to PPPoE Interworking Function (IWF)

Please turn to Chapter 19, PPPoA to PPPoE Interworking Function on page 365 for more information about the PPPoA to PPPoE IWF.

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}

To disable PPPoE stale session detection, enter the following command:occam(config-access-profile)# pppoe stale-detection disabled



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}

To disable this feature, enter the following command:occam(config-access-profile)# no pppoe discovery timeout

Complete Your Configuration




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.

Detaching an Access Profile From a ServiceAn access profiles is attached to a service. To detach an access profile from a service follow these steps:

1 From Global Configuration Mode, enter DSL Interface or DSL Bonding Configu-ration mode and specify the DSL port the service is attached to:Occam(config)# interface dsl {dsl-interface-number}OROccam(config)# dsl bonding-group group-id {1-x}

2 Enter DSL Service Configuration Mode:Occam(config-if-dsl)# service {1-4}

OROccam(config-dsl-bonding-group)# service {1-4}




3 Delete an access profile from the service:Occam(config-if-dsl-service-<1-4>)# no access profile

4 Exit DSL Service Configuration Mode: Occam(config-if-dsl-service-<1-4>)# exit

Displaying Access Profile Information Use the show access profile profile-name command from Privileged and User modes to display interface information for a specific profile. If you omit the profile-name argument, this command displays profile information for all existing access profiles.

Copying an Access ProfileTo copy a source profile to a new profile enter the access-copy-profile command from the Global Configuration Mode. If the destination profile indicated in this command does not exist, access-copy-profile creates it. The command then copies all non-default configurations defined for the source profile to the destination profile:Occam(config)# access-copy-profile {source-profile dest-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.

Deleting an Access ProfileDelete a profile by using the no access-profile command and its profile-name from Global Configuration Mode:Occam(config)# no access-profile {access-profile-name}

Note: You can modify the default profile, but you cannot delete it. You cannot delete a profile that is currently associated with a port.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesConfiguring a DSL Bonding Group

Configuring a DSL Bonding GroupADSL2 bonding allows one ATM stream to be split over multiple ADSL lines. Traffic may be spread across up to two ADSL lines, with aggregation performed on the receiving side.

DSL Bonding RestrictionsBonded ports must be consecutive DSL ports and confined to the following port ranges (port ranges are up to port number 24 on the BLC 6244 and BLC 6246):

For example, DSL ports 11 and 12 may be placed in the same bonding group. DSL ports 10 and 12 may not be placed in same group.

Configuring DSL Bonding


2 Enter DSL Bonding Configuration mode and specify the bonding group ID:Occam(config)# dsl bonding-group group-id {1-6}

3 Set the maximum downstream bitrate in kbps:occam(config-dsl-bonding-#)# bitrate maximum downstream {40-64000}

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

4 Set the maximum upstream bitrate in kbps:occam(config-dsl-bonding-#)# bitrate maximum upstream {40-6000}

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}

1-6 13-18 25-30 37-42

7-12 19-24 31-36 43-48



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}

6 Configure an access profile to configure subscriber management attributes for the bonding group. This access profile will be attached to a service which will in turn be attached to the bonding group. Please turn back to the section Config-uring an Access Profile on page 350 for information about how to configure an access profile.

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.

8 Enable the bonding group:occam(config-dsl-bonding-#)# no shutdown

Viewing the Bonding GroupThe following commands may be used to view information about your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide. Unless noted, all commands may be entered from User and Privileged modes.

show dsl bonding-group config [group-number]: use this command to display information about group rate, assigned ports (indicating which port is the master port), training state.

show dsl bonding-group status [group-number]: use this command to display information about a bonding-group.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesEnabling and Configuring a DSL Interface

Enabling and Configuring a DSL Interface Caution: Any time a DSL port is enabled but has no modem at the other end of it, the corresponding line is unterminated. Unterminated lines act as antenna receivers and amplifiers, picking up noise floating around them and potentially amplifying that noise. A DSL port that does not have a DSL modems attached to it should be disabled with the shutdown command.

Configure 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}

3 (Optional) Assign a name to the interface:

Note: An interface name may contain up to 64 printable characters. Letters, numbers and most special characters (such as underscores, hyphens, and ampersands) are allowed. Quotes and spaces are not allowed:Occam(config-if-dsl)# dsl subscriber {name}

4 (Optional) Attach informational text to the DSL interface:Occam(config-if-dsl)# info {key informative-text}

For example:Occam(config-if-dsl)# 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>, '?', '!'.

5 (Optional) Set the downstream power spectral density (psd) mask:Occam(config-if-dsl)# mask psd downstream {0-15}

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

!



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}

2 Disable the specified interface:Occam(config-if-dsl)# shutdown

Viewing Information About DSL InterfacesThe following commands may be used to view information about your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide. Each of these commands can be used without any specific configuration of the DSL interface. Unless noted, all commands may be entered from User and Privileged modes.

show dsl interface atm {dsl-interface-number}: use this command to show the ATM configuration and performance. This command displays interface and performance information for a specific interface.

show dsl performance [dsl-interface-number]: use this command to display ATM and line performance statistics. This command displays interface informa-tion for a specific interface, or all interfaces if no interface is specified.

show dsl performance history [interval-15|interval-24] [dsl-interface-number]: use this command to the history of the performance of a specific DSL interface or all DSL interfaces. You may optionally display 96 intervals of 15 minutes period statistics and 30 intervals of 24 hours period statistics.

show dsl performance summary [port|c15|c24|p15|p24] [dsl-interface-number]: use this command to display the DSL performance statistics in a summary fashion. This command displays summarized statistics for the current 15 minute, the current 24 hour, the previous 15 minute or the previous 24 hour period. If no parameters are provided at this level, the statistics summary for all ports and the current 15 minute period will be displayed. This command displays information for a specific interface, or all interfaces if none is specified.

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


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesEnabling and Configuring a DSL Interface

information for all existing DSL profiles.

show dsl rateinfo {dsl-interface-number} {dsl-interface-number}: use this command to display rate information for a single DSL interface or a range of DSL interfaces. Enter the command followed by a single DSL interface number or two DSL interface numbers, separated by a space. For example, to display rate information for interfaces one through ten, enter the following command:Occam# show dsl rateinfo 1 10

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 summary [dsl-interface-number]: Use this command to display one line of summarized information for a specific interface, or all interfaces if no interface is specified. This command has the same output as the command show interfaces dsl summary [dsl-interface-number].

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.

show interfaces dsl [dsl-interface-number]: use this command to display inter-face information for a specific interface, or all interfaces if no interface is specified.

show running-config interfaces dsl{dsl-interface-number}: use this command from Privileged mode to display information about a DSL interface in the running configuration.



Enabling and Configuring Service(s)

Enabling and Configuring Service(s) Up to four services may be added to each DSL interface or bonding group. These may be used for such functions as modem management, video and data. A DSL interface or bonding group can not support more than one service if the services are associated with more than one VLAN.

Multiple VLANs are associated with a service by a service policy which is linked to an access profile. The access profile is then associated with a service. The sections Configuring an Access Profile on page 350 and Configuring an Access Profile on page 350 describe how to configure a service policy and how to configure an access profile.

Please turn to page 363 to see a list of commands that may be used to view information about your service configuration.

1 Enter DSL Service Configuration Mode and select a service number between one and four to configure:Occam(config-if-dsl)# service {1-4}

OROccam(config-dsl-bonding-group)# service {1-4}

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

4 Optionally, configure a static MAC/IP address association:occam(config-if-dsl-service-<1-4>)# associate {mac-address} [ip-address] [ip-mask] [default gateway]

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

Remove a single static association: occam(config-if-dsl-service-<1-4>)# no associate mac-address


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesEnabling 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}

Override Access Profile Settings For This Port

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}

8 Optionally, set maximum number of MAC addresses allowed, overriding the MAC limit set in the attached access profile:occam(config-if-dsl-service-<1-4>)# override access-profile mac limit {1-64}

9 Optionally, enable or disable MAC learning, overriding the setting in the attached access profile:occam(config-if-dsl-service-<1-4>)# override access-profile mac-learning {enable | disable}

10 Enable the service: Occam(config-if-dsl-service-<1-4>)# no shutdown

11 Exit DSL Service Configuration Mode: Occam(config-if-dsl-service-<1-4>)# exit

12 (Optional) Repeat steps 4 through 13 to configure up to three additional services.

13 Exit DSL Interface or DSL Bonding Configuration mode: Occam(config-if-dsl)# exit

OROccam(config-dsl-bonding-group)# exit





Enabling and Configuring Service(s)

Displaying Service Configuration Information The following commands may be used to view your configurations. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide. Each of these commands can be used without any specific configuration of the DSL interface.

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.

show dsl service interface atm {dsl-interface-number}: use this command from Privileged mode to display information about a service on a specific DSL interface.

show policy-map binding {policy-map-name}: command to view to which services a policy map is associated. If no policy map is named, information will be returned for all policy maps.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 18: Configuring DSL InterfacesEnabling and Configuring Service(s)


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 19: PPPoA to PPPoE Interworking Function

Introduction

Chapter 19PPPoA to PPPoE Interworking Function

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365PPPoA to PPPoE IWF Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369PPPoA to PPPoE IWF Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

IntroductionThe 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.

OverviewPPPoE

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:


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 19: PPPoA to PPPoE Interworking FunctionOverview

Figure 19-1: PAD Packet

The code field defines what type of PAD packet it is:

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:

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.

DESTINATION

ff:ff:ff:ff:ff:ff

SOURCEETHERTYPE

00:00:0a:bb:cc:dd 0x8863version type code session id

1 1 0x09 0x0length

xpayload

xxxx

PAYLOAD

csum

CHECKSUM

Send PADI

Send PADR

Send PADO

Send PADS

Client Server

Communicationopened



Overview

A PAS packet has the following format:

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.

PPP-Protocol ID payload00:00:1a:2b:3c:4d 00:00:0a:bb:cc:dd 0x8864 1 1 0x00 0x7748 x 0xc021 xxxxxx csum

Ether TypeSourceDestinationlength

Payloadpayload

Checksumversion type code session id


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 19: PPPoA to PPPoE Interworking FunctionOverview

PPPoADSL 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.

PPPoA to PPPoE IWF and Access Control ListsSince no PPPoE packets will be transmitted on the subscriber link, the following traditional PPPoE ACL will not work:access-list ethernet X permit 0x8863access-list ethernet X permit 0x8864subscriber access-group ethernet X in Y

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.



PPPoA to PPPoE IWF Configuration

PPPoA to PPPoE IWF ConfigurationCaution: You may only configure one service with a PPPOAOE access profile on a DSL port. Configuring another service with a PPPOAOE access profile will cause PPPOAOE to fail.

To configure PPPoA to PPPoE Interworking Function (IWF), set the access-profile PPPoE mode to IWF, as shown in the following steps. Please turn to the section Configuring an Access Profile in Chapter 18, Configuring DSL Interfaces on page 350 for more information about how to configure 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 {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}

To disable PPPoE stale session detection, enter the following command:occam(config-access-profile)# pppoe stale-detection disabled

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 19: PPPoA to PPPoE Interworking FunctionPPPoA 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 a PPPoE SessionForces the specified session to terminate (i.e. a PADT packet will be sent to the BRAS indicating the session 'session_id' is no longer active). If a session ID isn't specified, all sessions on this BLC will be terminated. An acknowledgement message will be presented to the user to confirm the action in this case. You may enter the clear pppoe session command from Privileged or User Modes.occam# clear pppoe session [session-id]occam> clear pppoe session [session-id]

Clearing StatisticsYou 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]



Show Commands

Show CommandsYou 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

Igmp Port Type: NONE Igmp Source Address: N/A Igmp Max Streams: 255

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}

Arp Mode: none Arp Cache Timeout: 15 minutes Arp Reply Gateway: disabled

PPPoE Mode: iwf PPPoE Stale-detection: State enabled Interval 6 Retry-Count 4 PPPoE Discovery Retransmit: Interval 2 Retry-Count 3

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


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 19: PPPoA to PPPoE Interworking FunctionShow Commands

Alarming Interval: 5 secs Clearing Interval: 3 units of Alarming interval Action: shutdown

Displaying the Current PPPoE Session

This command displays the current PPPoE session established between the BRAS device and the BLC client. If a DSL port isn't specified, information for all DSL ports will be shown.occam# show subscriber pppoe summary [DSL-port]

For example:occam# show subscriber pppoe summaryPPPoE SessionsPort | State | Session ID | AC MAC Address | Count | Uptime-----|-----------|------------|-------------------|-------|----------01/2 | SESSION | 1734 | 00:10:67:00:ac:2c | 1 | 0d22h11m02/2 | SESSION | 1723 | 00:10:67:00:ac:2c | 1 | 0d22h11m03/2 | SESSION | 1728 | 00:10:67:00:ac:2c | 1 | 0d22h11m

occam# show subscriber pppoe summary 1PPPoE Sessions Port/Service: 1/2 Session Count: 1 Session ID: 1734 State: SESSION Session Uptime: 0d22h12m

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

Table 19-1: show alarms active Field Descriptions

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.



Show Commands

Displaying PPPoE session Info Based On the Provided Session ID

This command displays PPPoE session information based on the provided session ID. The provided session ID is a number between 1 and 65535.occam# show subscriber pppoe summary {session ID}

For example:occam# show subscriber pppoe session id 1734PPPoE SessionsPort | 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 summaryPPPoE 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

PPPoE IWF Session process failure summary: Service Down Error 0 Invalid Session ID Error 0 Network Device Error 0 Packet Length Error 0 Packet Transmission Error 0 AC MAC Mismatch Error 0 Subscriber MAC Mismatch Error 0 Stale PPPoA Session Error 0 Stale PPPoE Session Error 0 Memory Allocation Failure 0



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 1PPPoE 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

PPPoE IWF Session process failure summary: Service Down Error 0 Invalid Session ID Error 0 Network Device Error 0 Packet Length Error 0 Packet Transmission Error 0 AC MAC Mismatch Error 0 Subscriber MAC Mismatch Error 0 Stale PPPoA Session Error 0 Stale PPPoE Session Error 0 Memory Allocation Failure 0

Displaying PPPoE Discovery Statistics for All DSL Ports

The show subscriber pppoe discovery statistics summary command displays PPPoE Discovery statistics for all combined ports.

For example:occam# show subscriber pppoe discovery statistics summaryPPPoE Statistics Summary PPPoE IWF Session TX/RX packet summary: Rx packets 122 Dropped Rx packets 70 Tx packets 122 Dropped Tx packets 0

PPPoE Discovery (PAD) packet summary: Rx PADI packets 0 Rx PADO packets 28 Rx PADR packets 0 Rx PADS packets 24 Rx PADT packets 0 Total Rx PAD packets 52

Tx PADI packets 70



Show Commands

Tx PADO packets 0 Tx PADR packets 52 Tx PADS packets 0 Tx PADT packets 0 Total Tx PAD packets 122

Drop PADI packets 6 Drop PADO packets 42 Drop PADR packets 4 Drop PADS packets 28 Drop PADT packets 0 Total Drop PAD packets 80

PPPoE Discovery process failure summary: Rx PAD in Invalid State 70 Invalid Version/Type Error 0 Packet Length Error 0 Tag Length Error 0 AC MAC Mismatch Error 0 Subscriber MAC Mismatch Error 0 Invalid Session ID Error 0 Service-Name-Error 0 AC-System-Error 0 Generic-Error 0 Packet Transmission Error 0 Service Down Error 0 Invalide Service-Name Tag 0 Network Device Error 0 Subscriber Device Error 0 Max PAD Retransmit Error 10 Memory Allocation Failure 0 Total PAD Process Failure 80

Displaying PPPoE Discovery Statistics For a Specified DSL Port

This command displays PPPoE Discovery statistics for the provided port only.occam# show subscriber pppoe discovery statistics {port}

For example:occam# show subscriber pppoe discovery statistics 1PPPoE 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

PPPoE Discovery (PAD) packet summary: Rx PADI packets 0



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

Drop PADI packets 1 Drop PADO packets 4 Drop PADR packets 0 Drop PADS packets 1 Drop PADT packets 0 Total Drop PAD packets 6

PPPoE Discovery process failure summary: Rx PAD in Invalid State 5 Invalid Version/Type Error 0 Packet Length Error 0 Tag Length Error 0 AC MAC Mismatch Error 0 Subscriber MAC Mismatch Error 0 Service-Name-Error 0 AC-System-Error 0 Generic-Error 0 Packet Transmission Error 0 Service Down Error 0 Invalide Service-Name Tag 0 Network Device Error 0 Subscriber Device Error 0 Max PAD Retransmit Error 1 Memory Allocation Failure 0 Total PAD Process Failure 6

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 summaryPPPoA Statistics Summary PPPoA TX/RX frames summary: Rx frames 21171791



Show Commands

Dropped Rx frames 10 Tx frames 151689267 Dropped Tx frames 0

PPPoA Atm Encapsulation summary: Rx aal5snap frames 4 Rx vcmux frames 30 Rx unknown frames 0

PPPoA process failure summary: Link error 0 Rx queue full 0 Frame length error 0 No Session Established 10 Memory Allocation Failure 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 1PPPoA 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

PPPoA Atm Encapsulation summary: Rx aal5snap frames 0 Rx vcmux frames 2 Rx unknown frames 0

PPPoA process failure summary: Link error 0 Rx queue full 0 Frame length error 0 No Session Established 1 Memory Allocation Failure 0




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIP

Introduction

Chapter 20Configuring SIP

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379SIP Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382Configuring Global SIP Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Configuring a Voice Port SIP Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Configuring a SIP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397Configuring a Voice Port For SIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404Viewing Your SIP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409Digit Map Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419CLASS Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

IntroductionOccam 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.

BLCs That Support SIPThis chapter describes how to configure SIP on the following BLCs:

BLC 6150-01

BLC 6151-01

BLC 6152-02

BLC 6244

BLC 6246

BLC 6252-03


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPIntroduction

Chapter OverviewThe 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.

SIP Configuration OverviewThe BLC has Global SIP configuration parameters that are described in the section Configuring Global SIP Configurations on page 388. These parameters are common to all voice ports on that BLC that are configured to use SIP.

A voice port profile must be configured and attached to each voice port. Voice port profiles describe parameters common to groups of ports such as signaling, codecs and input and output gain. Configuration is described in the section Configuring a Voice Port SIP Profile on page 389.

In addition to a voice port profile, each voice port configured for SIP must also have a SIP profile attached to it. A SIP profile includes SIP parameters common to groups of ports such as proxies and call features. The section Configuring a SIP Profile on page 397 describes how to configure a SIP profile.

Finally, the section Configuring a Voice Port For SIP on page 404 describes how to enable a voice port and attach both a voice port and a SIP profile to the port.

Figure 20-1: SIP Configuration

Voice PortConfigured

for SIP

Voice PortProfile

Parameters

Global SIPParameters

on BLC

SIP ProfileParameters



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”

Figure 20-2: SIP Configuration Example

VO IC EPO RT 1

B LC W ITH G LO BAL S IP PAR AM E TER S CO NFIG URE D

VO IC EPO R T 2

VO IC EPO RT 3

V O IC EP O R T 3

S IP PRO FILE"B "

S IP P R O FILE"C "

VO IC E PO R TP R O FILE "B "

S IP P R O FILE"A"

VO IC E PO R TPRO FILE "A"


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPSIP Basics

SIP BasicsUser Agents and Servers

A SIP based network includes user agents and servers.

SIP User Agents

A user agent contains a user agent client (UAC) which generates requests, and a user agent server (UAS) which responds to requests. The Occam BLC SIP feature configures the BLC to operate as a RFC 3261 compliant SIP user agent. Individual POTS ports are configured as SIP endpoints with unique SIP identities. These SIP endpoints register with soft switches which may act as a SIP proxy server or as a Back-To-Back User Agent (B2BUA) whereby SIP signaling is terminated on the softswitch.

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.



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 MessagesSIP 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.



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



SIP Basics

Gateway) The server failed to fulfill an apparently valid request.

6xx

Global Failure (e.g. 600 Busy Everywhere, 603 Decline, 604 Does Not Exist Anywhere) The request cannot be fulfilled at any server

SIP AddressingEach 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.

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.

SIP URI example:

"123_Maple_St" <sip:[email protected]>



SIP Message Flow ExampleFigure 20-3 shows an example of how messages might flow in a BLC SIP network.

Note: After a softswitch is configured as a Back-to-Back User Agent (B2BUA). A B2BUA is in the call-signalling-path all the times, tracking each call from beginning to end. Thus, this diagram shows only the RTP media stream directly passing between BLC A to BLC B

Figure 20-3: SIP Message Flow Example

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.

3 The softswitch sends the INVITE request to BLC B.

4 BLC B tells the softswitch that it is ringing the number by sending the 180 code.

5 The softswitch passes this information on to BLC A.

6 BLC B tells the softswitch that has accepted the phone call by sending the 200 code.

(2) INVITE

SIP ProxyServer

BLC A BLC B

AnalogTelephone

(3) INVITE

(6) 200 OK

(7) 200 OK

(10) RTP MEDIA STREAM

(4) 180 RINGING

(5) 180 RINGING

(1) CUSTOMERDIALS NUMBER

(11) CUSTOMERPUTS PHONE

ONHOOK

AnalogTelephone

(8) ACK

(9) ACK

(13) BYE

(12) BYE

(14) OK

(15) OK



SIP Basics

7 The softswitch passes the 200 code on to BLC A.

8 BLC A sends the softswitch an ACK request acknowledging that it has accepted the phone call.

9 The softswitch passes on the ACK request to BLC B.

10 The phone call messaging takes place directly between BLC A and BLC B.

11 The customer using BLC B hangs up the phone.

12 BLC B sends the softswitch a BYE request, terminating the session.

13 The softswitch passes the BYE request on to 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPConfiguring Global SIP Configurations

Configuring Global SIP ConfigurationsConfigure SIP parameters for all the voice ports that are enabled to use SIP.

1 Enter Global Configuration mode:occam#configure terminalEnter configuration commands, one per line. End with CNTL/Z.Occam(config)#

2 Enable SIP:occam(config)# sip

Use the no form of the command to disable SIP:occam(config)# no 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.



Configuring a Voice Port SIP Profile

Configuring a Voice Port SIP ProfileDefault Voice Port Profile

All voice ports have attached profiles. If you do not assign a profile to an voice port, the system, by default, assigns the profile named "default" to that voice port. This profile can be changed but not deleted. If you wish to only change a few attributes of the default profile Occam Networks recommends that you copy the attributes of the default voice port profile to another profile by using the voice-copy-profile command, as described in the section Copying a Voice Port Profile on page 396.

The initial values for the default voice port profile are shown below:profile: default Profile type: pots-voip 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: pots Rtp Signaling Type: nuera2833 Echo cancel: enable Echo tail length: 32 milliseconds Echo Tone Disabler: G.165 Connection mode: pots Idle Channel Suppression: enable Receive Level: -3.0 dB Transmit Level: -3.0 dB Codecs: g711ulaw Codec Options: g711ulaw: Jitter Delay: 20ms Packetization: 10msModem Codec Bypass: enable

Voice Port Sip ProfileAt a minimum you must change the RTP signaling type from the default value of “nuera2833” to “none” (rtp-sig-type none).

You may configure virtually an unlimited number of voice port SIP profiles. Voice port SIP profiles are maintained in memory so that the profiles can be assigned to voice ports when needed.

The same profile can be attached to multiple voice ports, but one voice port cannot have more than one profile attached to it. If an existing profile is modified, that change takes effect on every voice port attached to that profile. To change a select number of voice ports Occam Networks recommends that you copy the profile parameters of an existing profile to a new profile, change the desired parameters,


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPConfiguring 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.




Voice Port SIP Profile Configuration Steps


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}

The prompt changes to:Occam(config-profile)<profileName>#

For example, if a Voice Profile named “sip” was being configured the command would be:Occam(config)# voice-profile pots voip sip

and the prompt would change to:Occam(config-profile)sip#

Use the command no voice-profile {profileName} to delete a profile by name.

3 Configure the Real-time Transport Protocol (RTP) Signaling Mode is configured as “none”:Occam(config-profile)<profileName># rtp-sig-type none

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.

Table 20-1: Voice Port Profile Configuration Commands

Feature Command to Change Default Value

Input Gain Value:

Sets the decibel amount of input gain to insert at the receiver side of the interface. The param-eters are -12 dB to +12dB in one dB increments. The default is 0 dB.

occam(config-profile)profile-name# input-gain {-12dB..12dB}

Output Gain Value:

Sets the decibel amount of output gain (atten-uation) to insert at the transmit side of the interface. The parameters are -12 dB to +12dB in one dB increments. The default is 0 dB.

occam(config-profile)voice-profile-name# output-gain {-12,-11,..,11,12}



Forward Disconnect:Specifies in milliseconds the amount of time the battery is removed to alert the remote end disconnect. At the end of a call, when the far end hangs up, the forward disconnect signal is applied to the line to inform the local user that the remote has disconnected. The default value is 900 milliseconds

occam(config-profile)profile-name# forward-disconnect {600..1200}

Fax Delay:

Specifies fax jitter buffer delay in five msec increments

occam(config-profile)profile-name# fax-delay {0...210}

Fax CNG Detector:

Enables or disables the fax CNG (CalliNG) tones detector. This feature is disabled by factory default.

occam(config-profile)profile-name# fax-cng-detect {enable, disable}

Fax CNG Timer:

Specifies the number of seconds the CNG detector is enabled at the start of a call.The factory default is 0 seconds.

occam(config-profile)profile-name# fax-cng-timer {0-120}

Signaling Type:This feature is set as POTS by factory default and is not configurable.

occam(config-profile)profile-name# sig-type pots

Echo Cancel:Set the voice echo cancel setting to enabled, disabled, or let MGCP decide. This feature is enabled by factory default.

occam(config-profile)profile-name# echo-cancel {mgcp, enable, disable}

Echo Tail Length:Set the echo path delay in milliseconds (msec). This is the amount of delay in time over which echo is controlled. The default value is 32 msec

occam(config-profile)profile-name# echo-tail-length {24, 32, 48, 64, 80, 96, 112, 128}

Echo Tone Disabler:Configures the voice port with one of the following parameters:

disable - Ignore 2100 Hz tone

G.164 - Bypass echo cancellation on 2100 Hz tone detection

G.165 - Bypass echo cancellation on 2100 Hz tone with phase reversal. This is the factory default.

occam(config-profile)profile-name# echo-tone-disabler (disable, G.164,G.165}

Connection Mode:

The connection mode is POTS- MGCP by factory default and is not configurable.

N/A




Idle Channel Suppression:

This feature is enabled by factory default and is not configurable.

N/A

Receive level:

Set the receive level on a voice-port in decibels. The default value is -3.0 dB.

occam(config-profile)profile-name# receive-level {-15, -14.9, -14.8,..,+9.8, +9.9,+10}

Transmit Level:

Sets the transmit level on a voice-port in deci-bels. The default value is -3.0 dB

occam(config-profile)profile-name#

transmit-level {-15, -14.9, -14.8,..,+9.8, +9.9,+10}



Codec-list: Preferred coder-decoders (codecs) used during call compression. The order entered determines the priority order of the codecs.

The codec options are:g711ulaw: ulaw PCM. This is the factory default codec and may be used with both the Metaswitch and Coppercom softswitch.The default values for this codec are:Jitter Delay: 20msPacketization: 10ms

g726-32K-pt2: ADPCM 32k payload type 2. This codec may be used with the Metaswitch softswitch.The default values for this codec are:Jitter Delay: 40msPacketization: 20ms

g726-32k: ADPCM 32k dynamic payload type. This codec is described in RFC 3551. This algo-rithm compresses voice from 64 kbps to 32 kbps. It supports dynamic packet types and may be used with the Coppercom softswitch.The default values for this codec are:Jitter Delay: 40msPacketization: 20ms

Note: In this release you may only configure the g721 OR g726-32k codec on a profile because the g721 codec supports fixed packet type 2 and the g726-32k codec supports dynamic packet types. You may not configure both. The g711ulaw will always be on the codec list, even if it is not entered.Upon detection of a fax CED or CNG tone the algorithm will automatically switch from g.726/g.721 to g.711.Three way calling is not supported with the g721 and g726 codecs unless the softswitch does the mixing.

occam(config-profile)profile-name#codec-list (g711ulaw, g726-32K-pt2, g726-32k}




5 Exit to Global Configuration Mode:Occam(config-profile)<profileName># exit

6 Repeat steps 2 through 5 for each SIP profile you wish to configure.

Codec-Options:

Configures the jitter delay and packetization options for codecs.

occam(config-profile)profile-name#codec-options {g711ulaw, g726-32K-pt2, g726-32k}

Jitter Delay:

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.

occam(config-voice-codec)#jitter-delay {10,..110}

Packetization: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.

occam(config-voice-codec)#packetization {15 | 10 | 20 |40}

Modem Codec Bypass:Configures the modem-codec-bypass as:

disabled - No codec bypass

enabled - Modem codec bypass functions are configured to follow the settings of the echo-tone-disabler command.

If the echo-tone-disabler command is config-ured with the parameter:

disable: the modem codec bypass feature is also configured to ignore a 2100 Hz answer tone when it is detected.

G.164: the modem codec bypass feature is also configured to bypass echo cancellation on 2100 Hz tone detection. This option does not look for phase reversal on the tone.

G.165: the modem codec bypass feature is also configured to bypass echo cancellation on 2100 Hz tone only when phase reversal is detected on it.

occam(config-profile)profile-name# modem-codec-bypass {enabled, disabled}





8 Continue on to the section Configuring a SIP Profile on page 397.

Copying a Voice Port ProfileFollow these steps to copy the parameters of a source voice port profile to a new voice port profile:


2 Copy the voice port profile as follows:

Enter the command voice-copy-profile

Enter the name of the source voice port profile

Enter the name of the new voice port profile you wish to create

occam(config)# voice-copy-profile old-profile-name new-profile-name

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.

Deleting a Voice Port Profile


2 Delete the voice port profile, specifying it by name:occam(config)# no voice-profile profile-name



Configuring a SIP Profile

Configuring a SIP ProfileIn addition to a voice port profile you must also create a SIP profile to attach to one or more voice ports. At a minimum you must configure a proxy server on the profile.

You may configure virtually an unlimited number of SIP profiles. SIP profiles are maintained in memory and can be assigned to voice ports when needed.

As with the voice port profiles, the same SIP profile can be attached to multiple voice ports, but one voice port cannot have more than one SIP profile attached to it. If an existing SIP profile is modified, that change takes effect on every voice port attached to that profile. To change a profile attached select number of voice ports Occam Networks recommends that you copy the profile parameters of an existing SIP profile to a new SIP profile, change the desired parameters, and then attach the new SIP profile to the desired voice port(s). This is described in the section Copying a SIP Profile on page 403.

The section Deleting a SIP Profile on page 403 describes how to delete a SIP profile.

Default SIP ProfileIf you do not assign a SIP profile to a voice port, the system, by default, assigns the SIP profile named "default" to that voice port. This profile can be changed but not deleted. It is recommended that you rename the default SIP profile if you change it.

The values for the default SIP profile are shown below:Proxy: NoneSecondary Proxy: NoneDomain: NoneRegistrar: NoneSecondary Registrar: NoneRegistration Timeout: 3600Call Waiting: disableThree Way Calling: disableCaller ID: disableMWI: disableDigit Map: x.T


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPConfiguring a SIP Profile

SIP Profile Configuration Steps

Note: If you are attaching a new SIP profile to a voice port configured for SIP, you must disable SIP functionality on the voice port before attaching the new SIP profile. After you attach the new SIP profile you may reenable SIP functionality the voice port. Please see the section Attaching a New SIP Profile to a Voice Port Previously Configured For SIP on page 408 for information about how to do this.

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 terminalEnter 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

Use the command no sip-profile {sip-profile-name} to delete a profile by name.

3 Configure the name or IP address of a proxy server, as shown below in Table 20-2.




Table 20-2: Mandatory SIP Profile Configuration Command

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.

Table 20-3: Optional SIP Profile Configuration Commands

Feature Command

Proxy Server:Enter the FQDN (i.e. metaswitch.testlab.com) or IP address of a primary proxy server. You may also optionally enter the port number of the primary proxy server. The range or port numbers is between 1025-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.

occam(config-sip-profile)#proxy {FQDN or IP address}: [1025-65535]

occam(config-sip-profile)#proxy secondary: {FQDN or IP address} [1025-65535]

Feature Command

SIP Domain:

Enter the FQDN 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.

occam(config-sip-profile)#sip-domain {FQDN or IP address}



Registrar:A registrar is a User Agent Server (UAS) that accepts registration requests. Enter the FQDN or IP address of a primary registrar. You may also optionally enter the UDP port number of the primary registrar. 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.

occam(config-sip-profile)#registrar {FQDN or IP address} [1025-65535]

occam(config-sip-profile)#registrar secondary {FQDN or IP address} [1025-65535]

Registration Timeout (Regtime):Configures the registration timeout in seconds. The parameters are between one and 86400.The factory default is 3600 seconds.

occam(config-sip-profile)#regtime {1-86400}

Call Waiting: Enables or disables the call waiting feature 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.

Note: You have to have a digit map that will match *70. The default digit, [0-9*].T map will match *70. Alternatively, you could use: *xx | x.TThe section Digit Map Configuration on page 419 contains more dial map information.

occam(config-sip-profile)#call-waiting {enable, disable}




5 Exit SIP Profile Configuration Mode:occam(config-sip-profile)# exit

6 Exit Global Configuration Mode and save your configuration:

Caller ID: Enables or disables the caller ID feature on the port to which the profile is attached.This feature is disabled by factory default.

occam(config-sip-profile)#caller-id {enable, disable}

Message Waiting Indication (mwi): Enables or disables the message waiting indication feature (stutter dial tone) on the port to which the profile is attached.The message waiting indication is disabled by factory default.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.

occam(config-sip-profile)#mwi {enable, disable}

Three-Way-Calling:

Enables or disables the three way calling feature on the port to which the profile is attached.The three way calling feature is disabled by factory default.

Note: Three way calling is not supported with the g726 codecs unless the softswitch does the mixing.

occam(config-sip-profile)#three-way-calling {enable, disable}}

Digit Map: A digit map is a list of valid telephone numbers. It outlines the length and format of a valid telephone number. The format is based on MGCP (RFC 2705). A digit map consists of a series of space separated entries, each of which includes a sequence of digits and symbols. For example, "0T 00 011 1805xxx [2-79]xxx 8[1-9]xx 411 911" is a valid digit map.The section Digit Map Configuration on page 419 defines the digits and symbols used in a digit map.

occam(config-sip-profile)#digit-map {digit_map_entry1 digit_map_entry2 digit_map_entry3...}



occam(config)# exit


7 Go on to the following section Configuring a Voice Port For SIP on page 404.




Copying a SIP ProfileFollow these steps to copy the parameters of a source SIP profile to a new SIP profile:


2 Copy the SIP profile as follows:

Enter the command sip-copy-profile

Enter the name of the source SIP profile

Enter the name of the new SIP profile you wish to create

occam(config)# sip-copy-profile old-profile-name new-profile-name

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.

Deleting a SIP Profile


2 Delete the SIP profile:occam(config)# no sip-profile SIP-profile-name


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPConfiguring a Voice Port For SIP

Configuring a Voice Port For SIP1 Enter Global Configuration mode:

occam# configure terminalEnter 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}

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}

4 Configures the voice port for SIP mode:occam(config-voice)# mode sip

5 Enter Voice Port SIP Configuration Mode:occam(config-voice)# sip

6 Configure the voice port by using the commands in the following table:

Table 20-4: Voice Port Configuration Commands

Feature Command

Attach SIP Profile:Attach the SIP profile to the voice port, specifying the SIP profile by name.

occam(config-voice-sip)#attach-profile {SIP-profile-name}

Authentication Username:Enter the authentication username, to be used for authentication.

occam(config-voice-sip)#authusername {string}

Authentication Password:Enter the authentication password.

occam(config-voice-sip)#password {string}



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:

Table 20-5: SIP Port Profile Override Configuration Commands

Display Name:

Configures the portion of the port's URI that is displayed. For example, the displayname may be the user’s location, such as “123_Maple_St”. This parameter is optional.

occam(config-voice-sip)#displayname {string}

URI Username:

Configures the username of the port's URI. This parameter is optional. The username may or may not be the tele-phone number assigned to the POTS line. Or it may be the customer’s name, resi-dence, or any other combination of letters or numbers. Whatever string is used to define the username must be matched by the softswitch to the telephone numbers assigned to the POTS line.

occam(config-voice-sip)#username {string}

Feature Command

Proxy Server Override:

Overrides the proxy server configuration in the SIP profile attached to this voice port and configures new proxy server for the voice port.

occam(config-voice-sip)#override sip-profile proxy {FQDN or IP address} [1025-65535]

occam(config-voice-sip)#override sip-profile proxy secondary{FQDN or IP address} [1025-65535]

Registrar Override:Overrides the primary and secondary registrar configurations in the SIP profile attached to this voice port and configures new primary and secondary registrars for the voice port.

occam(config-voice-sip))# override sip-profile registrar {FQDN or IP address} [1025-65535]

occam(config-voice-sip)# override sip-profile registrar secondary {FQDN or IP address} [1025-65535]

Registration Timeout Override:

Overrides the registration timeout (regtime) configuration in the SIP profile attached to this voice port and configures a new timeout for the voice port.

occam(config-voice-sip)# override sip-profile regtime {1-86400}



8 Exit Voice Port SIP Configuration Mode:occam(config-voice-sip)# exit

9 The voice port is shutdown by default. To enable the port enter the command no shutdown:occam(config-voice-sip)# no shutdown

10 Exit to Global Configuration Mode:occam(config-voice)# exit

11 Repeat steps 2 through 8 for each voice port to which you wish to attach a SIP profile.

SIP Domain Override:Overrides the SIP domain configuration in the SIP profile attached to this voice port and configures a new SIP domain for the voice port.

occam(config-voice-sip)# override sip-profile sip-domain {FQDN or IP address}

Digit Map Override:

Overrides the digit map configuration in the SIP profile attached to this voice port and reconfigures the digit map for the voice port.

occam(config-voice-sip)#override sip-profile digit-map {digit_map_entry1 digit_map_entry2 digit_map_entry3...}

Caller ID Override:

Overrides the caller ID feature configura-tion in the SIP profile attached to this voice port and reconfigures the caller ID feature for the voice port.

occam(config-voice-sip)#override sip-profile caller-id {enable, disable}

Call-Waiting Override:

Overrides the call waiting feature config-uration in the SIP profile attached to this voice port and reconfigures the call waiting feature for the voice port.

occam(config-voice-sip)#override sip-profile call-waiting {enable, disable}

Message Waiting Indicator Override:

Overrides the Message Waiting Indicator (MWI) configuration in the SIP profile attached to this voice port and reconfig-ures the message waiting indication for the voice port.

occam(config-voice-sip)#override sip-profile mwi {enable, disable}

Three Way Calling Override:

Overrides the three-way-calling configu-ration in the SIP profile attached to this voice port and reconfigures the three-way-calling feature for the voice port.

occam(config-voice-sip)# override sip-profile three-way-calling {enable, disable}}



Configuring a Voice Port For SIP



13 Continue on to the following section Viewing Your SIP Configuration on page 409 to confirm your SIP configuration.

Detaching a Voice Port Profile From a Voice Port

1 From the Global Configuration Mode enter Voice Port Configuration Mode and specify the voice port from which you want to detach the profile:Occam(config)# voice-port {voice-port-number}

2 Enter Voice Port SIP Configuration Mode:occam(config-voice)# mode sip

3 Detach the voice port profile from the voice port:occam(config-voice-sip)# no attach-profile {voice-port-name}



Attaching a New SIP Profile to a Voice Port Previously Configured For SIP

1 Enter Global Configuration mode:occam# configure terminalEnter 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}

3 Enter Voice Port SIP Configuration Mode:occam(config-voice)# mode sip

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.

8 Exit Voice Port SIP Configuration Mode:occam(config-voice-sip)# exit

9 Enable the port enter:occam(config-voice-sip)# no shutdown

10 Exit to Global Configuration Mode:occam(config-voice)# exit




Viewing Your SIP Configuration

Viewing Your SIP ConfigurationThe following commands are described below:

show sip: this command displays Global SIP settings on the BLC. It is described on page 409.

show sip config {voice-port-number}: this command displays summarized information about the SIP configuration on a specified voice port. It is described on page 410.

show sip port [voice-port-number]: this command displays detailed information about the SIP configuration on one or all voice ports. It is described on page 411.

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.

Viewing Global SIP Settings On the BLCUse the command show sip to display Global SIP settings on the BLC. Sample output is shown below:occam# show sipSIP User Agent: UPSIP Interface: bvi2 (192.168.14.221)SIP Transport: udpSIP Port: 5060

Table 20-6: “show sip” Command Field Descriptions

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPViewing Your SIP Configuration

Viewing SIP Configuration Settings On Voice Ports

Viewing Summarized Information About SIP Configuration Settings On a Voice Port

Use the command show sip config {voice-port-number} to display summarized information about the SIP configuration on a specified voice port. Sample output for SIP configuration on voice port one is shown below:occam# show sip config 1Port 1 config name 2019999801 display 123_Maple_Street authname 2019999001:sip101 password sip101 domain 192.168.19.11 proxy 192.168.19.11 backupproxy 192.168.50.175 regtime 3600 digit map x.T callwaiting No 3waycalling No callerid No mwi No codec-list g726-32k-pt2 g711ulaw codec-options g726-32k-pt2 2 20 40 codec-options g711ulaw 0 10 20

Table 20-7: “show sip config” Command Field Descriptions

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.




Viewing Detailed Information About SIP Configuration Settings On a Voice Port

Use the command show sip port [voice-port-number] to display detailed information about the SIP configuration on a specified voice port. If you do not enter a voice port number information will be returned for all voice ports. Sample output for SIP configuration on voice port one is shown below:occam# show sip port 1Port 1 status Admin: UP Oper: UP Mode: SIP ON-HOOK State: ACTIVE Last Dialed: 9999002 Connections: 192.168.22.44:13058

Registration: Primary Status: 200 OK Timer: 3600 secs Expires: Thu Oct 19 13:38:36 2006

Running parameters URI: "123_Maple_St" <sip:[email protected]> 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

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 40codec-options g711ulaw 0 10 20

The codec g726-32k-pt2 has the following parameters:RTP packet type = 2The packetization = 20 msecThe jitter delay value = 40 msec

The codec g711ulaw has the following parameters:RTP packet type = 0The packetization = 10 msecThe jitter delay value = 20 msec

Field Description



g726-32k-pt2 2 20 40 g711ulaw 0 10 20

Table 20-8: “show sip port” Command Field Descriptions

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.

SIP URI example:"123_Maple_St" <sip:[email protected]>

Authentication This is in the format authentication username:authentication password.For example: 2019999001:sip101The authentication username is “2019999001” and the authentication password is 'sip101”

Primary This field displays the primary proxy and registrar. These may be a FQDN or an IP address.




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).

Field Description



Viewing Information About EndpointsUse the command show sip endpoints to information about the SIP endpoints. Sample output for this command is shown below:

occam# show sip endpoints Port Admn Oper Mode Registrar Hook State Last Dialed Connections 1 UP UP SIP Primary Off CALLUP 192.168.22.44:13058 2 UP UP SIP Primary Off CALLUP 192.168.22.44:13062 3 UP UP SIP Primary Off CALLUP 192.168.22.44:13066<output truncated>

Table 20-9: “show sip endpoints” Command Field Descriptions

Field Description

Port Voice port number

Adm Administrative state of the portUP: the voice port is up (no shutdown)down: the voice port is down (shutdown)

Oper Operational state of the portUP: the voice port is up and fully configured for SIPdown: 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”.




State Port state. The options are:

BUSY - Phone is off-hook and the user is hearing a busy signal.

CALLING - Dialing has completed and the BLC is waiting for the proxy to respond.

CALLUP - The voice path is established.

DIALING - The phone is off-hook and the user can hear a dialtone and may dial a phone number.

IDLE - The port is on hook and ready for calls.

RINGBACK - The remote is ringing, and ringback is generated.

RINGING - An incoming call has been accepted and the BLC is ringing the port.

ROH - The receiver has been off hook a long time and the BLC is generating a receiver offhook tone.

STANDBY - The port is either waiting for ESA or waiting for REGISTRATION. The port is not ready for calls.

TRANSFER - The BLC has initiated a transfer and is waiting for it to complete.

WAIT_ENABLE - Waiting for the port to be enabled. This state is passed through every time the local port hangs up.

WAIT_LOCAL - The remote has hung up. Waiting for the local port to hangup.

Last Dialed Last number dialed out.

Connections RTP address of the remote

Field Description



Viewing Information About SIP ProfilesUse the command show sip-profiles to information about the SIP profiles. Sample output for this command is shown below:

occam# show sip-profilesSIP profile: sip_profile_101 Proxy: 192.168.19.11 Secondary Proxy: 192.168.19.15 Domain: 192.168.19.17 Registrar: 192.168.19.21 Secondary Registrar: 192.168.19.31 Registration Timeout: 3600 Call Waiting: enable Three Way Calling: enable Caller ID: enable MWI: enable Digit Map: x.TSIP profile: sip_profile_102 Proxy: 192.168.50.175 Secondary Proxy: 192.168.19.11 Domain: 192.168.19.11 Registrar: 192.168.50.165 Secondary Registrar: 192.168.50.166 Registration Timeout: 3600 Call Waiting: enable Three Way Calling: enable Caller ID: enable MWI: enable Digit Map: x.T

Table 20-10: “show sip-profiles” Command Field Descriptions

Field Description

SIP profile SIP Profile name

Proxy Primary proxy server configured in this SIP profile.

Secondary Proxy

Secondary proxy server configured in this SIP profile.

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 Registrar

Secondary registrar configured in this SIP profile.




Registration Timeout

This setting means that after the BLC registers the switch will 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 Calling

Status of the three way calling feature (enabled or disabled) 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.

Field Description



Viewing Information About SIP UsersUse the command show sip users to information about the SIP username configured for this port. This command is useful in identifying specific ports if two of them have been configured with the same username.

Sample output for this command is shown below:

occam# show sip usersPort Display Username Domain Call Features 1 phone 1 4153653101 10.0.0.233 2 phone 2 4153653102 10.0.0.233 3 phone 3 4153653103 10.0.0.233 4 phone 4 4153653104 10.0.0.233 5 phone 5 3014243105 10.3.10.2 CID CW 3W MWI 6 phone 6 3014243106 10.3.10.2 CID CW 3W MWI 7 phone 7 3014243107 10.3.10.2 CID CW 3W MWI 8 phone 8 3014243108 10.3.10.2 CID CW 3W MWI 9 phone 9 3016853109 10.0.0.233 10 phone 10 3016853110 10.0.0.233 11 phone 11 3016853111 10.0.0.233 12 phone 12 3016853112 10.0.0.233

Table 20-11: “show sip users” Command Field Descriptions

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.



Digit Map Configuration

Digit Map ConfigurationA digit map is a list of the valid telephone numbers that outlines the length and format of a valid telephone number. The format is based on MGCP (RFC 2705).

It consists of a series of space separated entries, each of which includes a sequence of digits and symbols. Table 20-12 below defines the digits and symbols used in a digit map.

Table 20-12: Valid Digits and Symbols Used in a Digit Map

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.

Default SIP Digit MapThe default SIP digit map is “x.T”. This digit map means that the customer may dial any number of any digits and after a pause of four seconds the BLC will send the dialed digits to the softswitch.

Symbol Result

0 1 2 3 4 5 6 7 8 9 Identifies a specific digit

x Wildcard entries that represents any number between 0 and 9.X

[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”.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPDigit Map Configuration

Sample Digit MapThis is an example of a digit map:occam(config-sip-profile)# digit-map 0T 00 011 549xxxx 670xxxx [2-47-9]xxxxxx 411 911

Table 20-13 below describes the digit maps shown in the above example:

Table 20-13: Digits Map Example Description

Digit Map Description0T Connect the call four seconds after the digit 0 is

dialed.00 Match the digits 00011 Match the digits 011549xxxx Match any series of seven digits that start with

549670xxxx Match any series of seven digits that start with

670[2-47-9]xxxxxx Match any series of seven digits that start with

numbers 2, 3 and 4 or 7, 8 and 9.411 Match the digits 411911 Match the digits 911



CLASS Feature Overview

CLASS Feature OverviewTable 20-14 details if a CLASS feature is configured on a softswitch or by both the softswitch and the BLC. If the CLASS feature is provided by both the BLC and a softswitch, the feature must be configured on both devices to be enabled.

Table 20-14: Class Feature Implementation

CLASS Feature Implementation

Anonymous Call Blocking Softswitch

Automatic Callback Softswitch

Automatic Recall Softswitch

Basic Business Group Softswitch

Call Forwarding Busy Softswitch

Call Forwarding No Answer Softswitch

Call Forwarding Selective Softswitch

Caller Identification Both

Caller Identification on Call Waiting Both

Caller Identity Delivery/Suppression Softswitch

Calling Number Delivery Softswitch

Call Waiting Operation Both

Cancel Call Waiting Softswitch

Customer Originated Trace Softswitch

Denied Origination Softswitch

Denied Termination Softswitch

Directed Call Pickup Softswitch

Family Time (FT) Softswitch

Group Make Busy Softswitch

Line Hunt Group CFBL Softswitch

Line Hunt Group CFDA Softswitch

Line Hunt Group CFV Softswitch

Line Hunt Group VMBL Softswitch

Multi-Frequency Voice Mail System Softswitch

Multiple PIC Softswitch

Nuisance Call Softswitch

Night Service Softswitch

Public Feature Code Softswitch

Remote Access to Call Forwarding Softswitch

Selective Call Acceptance Softswitch


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 20: Configuring SIPCLASS Feature Overview

Selective Call Forwarding Softswitch

Selective Call Rejection Softswitch

Selective Distinctive Ringing/Call Waiting

Both

Simultaneous Ringing Softswitch

SIP Call Forwarding Both

SIP Call Hold Both

SIP Call Transfer Both

SMDI Voice Mail Softswitch

Three-Way-Calling Both

Toll Restriction Softswitch

Toll Restriction with PIN Override Softswitch

CLASS Feature Implementation


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 21: Access Control Lists (ACLs)

Introduction

Chapter 21Access Control Lists (ACLs)

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Ethernet ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425IP Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427Displaying ACL and Access Group Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431Security Filter Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

IntroductionSecurity 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).

Non-windows related traffic that serves no useful purpose in the network.

DHCP Server on CPE side responding to subscriber DHCP clients requests

Address spoofing, for example sending packets into the network with a source IP address that has not been assigned.

Ethernet and IP ACLsYou may configure Ethernet and IP ACLs.

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


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.



Ethernet ACLs

Ethernet ACLsYou 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.

Configuring an Ethernet ACLFrom Global Configuration Mode, enter the access-list ethernet command.

This command may be used to add a filter for an ARP EtherType, an IP EtherType, and a specific EtherType. This command can be executed multiple times to match multiple EtherTypes. The ACL name is an alphanumeric name and may also include a dash (-) and and underscore (_).

Filter for an ARP EtherType

Add an ARP EtherType filter to the ACL:occam(config)# access-list ethernet {acl-name} permit arp

Note: This filter is optional, since an ARP filter is always added by default when an IP EtherType filter is created.

Filter for an IP EtherType

Add an IP EtherType filter to the ACL:occam(config)# access-list ethernet {acl-name} permit ip

Filter for a PPPoE Discovery EtherType

Add an PPPoE Discovery Stage filter to the ACL:occam(config)# access-list ethernet {acl-name} permit pppoe-discovery

Filter for a PPPoE Session EtherType

Add an PPPoE Session Stage filter to the ACL:occam(config)# access-list ethernet {acl-name} permit pppoe-session

Filter for a Broadcast EtherType

Add an Broadcast filter to the ACL:occam(config)# access-list ethernet {acl-name} permit broadcast


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 21: Access Control Lists (ACLs)Ethernet ACLs

Filter for a Specific EtherType

Add a filter for a specific EtherType to the access-list. Specify an access-list by name and enter the EtherType in hex (for example 0x5afaf):occam(config)# access-list ethernet {acl-name} permit {0X0600-0Xfff}

For example:occam(config)# access-list ethernet eth-acl-1 permit 0x5afaf

Removing an Entry From an Ethernet ACLTo delete an entry from an Ethernet ACL, you must use the command no access-list from Global Configuration Mode, with the same address information you used to add the entry. For example:

Add:occam(config)# access-list ethernet eth-acl-1 permit 0x8863

Delete:occam(config)# no access-list ethernet eth-acl-2 permit 0x8863

Attaching an Ethernet ACL To a VLANAttach the ACL to a specific VLAN with the subscriber ethernet access-group command. Specify an ACL by name and an EPS VLAN number between 2-122:occam(config)# subscriber ethernet access-group {acl-name} in {2-122}

Detaching an Ethernet ACL From a VLANRemove the ACL from a specific VLAN with the no access-group command. Specify an ACL by name and an EPS VLAN number between 2-122:occam(config)# no subscriber ethernet access-group {acl-name} in {2-122}



IP Access Control Lists

IP Access Control ListsThe ip access command configures an ACL entry that allows the administrator to specify components of the layer 3 IP protocol header as well as the layer 4 TCP/UDP protocol header. At least one of the protocol fields must be specified but many can be omitted. The commands ip access-group or subscriber ip access-group are then used to attach the ACL to a BVI interface or a VLAN.

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 ACLFrom Global Configuration Mode, enter the access-list ip command.

Note: An ACL is always terminated by an implicit deny statement for everything.

occam(config)# access-list ip {acl-name} {deny, permit} {filter[/source-mask]}[icmp|udp|tcp][<1-65535>|ANY] [<1-65535>|ANY]

{acl-name} Specifies the IP ACL name. The ACL name is an alpha-numeric name and may also include a dash (-) and and underscore (_).

{deny} Specify packets to reject

permit Specify packets to accept

{filter[/source-mask]}

Filter based on the Source IP subnet in an A.B.C.D format.Optionally, add a source mask. The source mask is required if you are specifying a subnet mask. It is optional if the Source IP address (srcIP) is a host address.ORFilter based on the associations database Optionally, add a source mask.

[icmp|udp|tcp] (Optional) Specifies the layer 4 protocol carried by the IP datagram: ICMP, UDP or TCP

[1-65535>|ANY] (Optional) Source port. If not specified, the source port is assumed to be “match any”.

[<1-65535>|ANY] (Optional) Destination port. If not specified, the destination port is assumed to be “match any”.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 21: Access Control Lists (ACLs)IP Access Control Lists

Deleting an Entry from an IP ACL To delete an entry from an IP ACL, you must use the command no access-list from Global Configuration Mode, with the same address information you used to add the entry. For example:

Add:occam(config)# access-list ip 2 permit 0.0.0.0/0 udp 68

Delete:occam(config)# no access-list ip 2 permit 0.0.0.0/0 udp 68

IP ACL Configuration GuidelinesWhen an IP ACL is applied to a VLAN, two implicit filters are automatically added. One drops all traffic and the other permits all ARP traffic. These filters do not need to be entered explicitly. They may be viewed with the command show subscriber access-group as “SYSTEM” filters under the column “Owner”. An example of this is shown below:

occam# show subscriber access-group

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/0occam(config)# access-list ip 1 deny 10.0.0.0/8

Changing the order to:occam(config)# access-list ip 1 deny 10.0.0.0/8occam(config)# access-list ip 1 permit 0.0.0.0/0

filters out any device in 10/8 and allows everything else.

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




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



IP Access Control Lists

Attaching an IP ACL on a BVI Interface

1 Enter BVI Interface Configuration Mode:occam(config-if-bvi)# interface bvi {1,2}

2 Assign an IP ACL to the interface:occam(config-if-bvi)# ip access-group {acl-name} in

Caution: The ACL is always terminated by an implicit deny statement for everything. Make sure not to exclude yourself from access if you are telneted into any BLC.

Note: The BVI only accepts ACLs that specify source IP subnet/host and protocol. The ACL must not specify any TCP/IP interface numbers.

Replacing an IP ACL on a BVI InterfaceTo replace an IP ACL on an interface with another one, use the ip access-group in command in BVI Interface Configuration Mode. Use the new IP ACL number that you wish to use to replace the previous IP ACL:occam(config-if-bvi)# ip access-group {acl-name} in

Removing an IP ACL on a BVI InterfaceTo remove a IP ACL from an interface, use the no ip access-group in command in BVI Interface Configuration Mode.

Note: It is recommend that you use the ip access-group in command to replace one IP ACL with another one. Removing a IP ACL leaves a potential security hole until another is added:occam(config-if-bvi)# no ip access-group

Attaching an IP ACL to a VLAN

Caution: The ACL is always terminated by an implicit deny statement for everything. Make sure not to exclude yourself from access if you are telneted into the BLC.


2 Attach the access-list to a specific VLAN with the subscriber ip access-group command. Specify an access-list by name and an EPS VLAN number between 2-122. Optionally, enable hit counters for IP ACLs. This does not include ingress filter hit counters:

!

!


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 21: Access Control Lists (ACLs)IP Access Control Lists

occam(config)# subscriber ip access-group {acl-name} in {2-122} [count]


Removing an IP Access-List From a VLAN


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}




Displaying ACL and Access Group Information

Displaying ACL and Access Group InformationUse the show access-list command to display information for a specific ACL, or all ACLs if one is not specified. Use the show subscriber global-config to display global access control.

Displaying Ethernet ACL DefinitionsUse the show access-list ethernet command to display information about Ethernet ACLs. The following example shows sample output from this command:occam# show access-list ethernet access-list ethernet eth-acl-1 permit arpaccess-list ethernet eth-acl-1 permit ipaccess-list ethernet eth-acl-11 permit 0x8863access-list ethernet eth-acl-11 permit 0x8864

Displaying IP ACL DefinitionsUse the show access-list ip command to display information about IP ACLs. The following example shows sample output from this command:

occam# show access-list ipaccess-list ip ip-acl-1 permit associationsip access-list ip-acl-1 (not active)

access-list ip ip-acl-5 permit 0.0.0.0/32 udp 68access-list ip ip-acl-5 deny 0.0.0.0/0 udp 67access-list ip ip-acl-5 deny 0.0.0.0/0 tcp any 139access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 138access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 137access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 445access-list ip ip-acl-5 deny 0.0.0.0/0 tcp any 445access-list ip ip-acl-5 permit associations/24ip access-list ip-acl-5 (not active)

access-list ip ip-acl-7 permit 0.0.0.0/32 udp 68access-list ip ip-acl-7 deny 0.0.0.0/0 udp 67access-list ip ip-acl-7 deny 0.0.0.0/0 tcp any 139access-list ip ip-acl-7 deny 0.0.0.0/0 udp any 138access-list ip ip-acl-7 deny 0.0.0.0/0 udp any 137access-list ip ip-acl-7 deny 0.0.0.0/0 udp any 445access-list ip ip-acl-7 deny 0.0.0.0/0 tcp any 445access-list ip ip-acl-7 permit 192.168.17.0/24ip access-list ip-acl-7 (not active)

access-list ip ip-acl-10 permit 0.0.0.0/32 udp 68access-list ip ip-acl-10 deny 0.0.0.0/0 udp 67access-list ip ip-acl-10 deny 0.0.0.0/0 tcp any 139access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 138access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 137access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 445


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 21: Access Control Lists (ACLs)Displaying ACL and Access Group Information

access-list ip ip-acl-10deny 0.0.0.0/0 tcp any 445access-list ip ip-acl-10 permit associationsip access-list ip-acl-10 (not active)

Using the “show subscriber access-group” CommandUse the show subscriber access-group [eps-vlan-number] to display global access control. Enter an EPS VLAN number between 2 and 122. If this number is omitted, information for all EPS VLANs will be displayed

The following example shows sample output from this command:occam# show subscriber access-group

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

If snooping is not enabled, DHCP packets would be dropped by this filter.

Security filters have associated counters. Ingress filters and the implicit ARP filter installed by the system do not have these counters. Multiple counters may

VLAN: 4


IP access group: ip-acl-5










VLAN: 4









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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 21: Access Control Lists (ACLs)Security Filter Configuration Examples

Security Filter Configuration ExamplesThe following section describes some of the common scenarios found in provider networks. Note that the configuration steps outlined in the examples relate to subscriber security features only and are not intended to be complete configurations for the rest of the system (such as Ethernet services, access profiles, rate limiting, physical line parameters, etc.).

Scenario 1 - Single PVC with DHCPIn this scenario, each subscriber interface uses a single PVC. Subscriber PCs are configured via DHCP. PPPoE frames are dropped via the implicit "drop-all-ethertypes" filter. NETBIOS packets are dropped explicitly through filters outlined below. All subscriber traffic is on VLAN 2.


2 Drop DHCP server responses:occam(config)# access-list ip ip-acl-2 deny 0.0.0.0/0 udp 67

3 Permit DHCP discovery frames:occam(config)# access-list ip ip ip-acl-2 permit 0.0.0.0/0 udp any 67

4 Drop NETBIOS Name Service UDP frames:occam(config)# access-list ip ip ip-acl-2 deny 0.0.0.0/0 udp any 137

5 Drop NETBIOS Datagram UDP frames:occam(config)# access-list ip ip ip-acl-2 deny 0.0.0.0/0 udp any 138

6 Drop CIFS (Common Internet File System) TCP frames:occam(config)# access-list ip ip ip-acl-2 deny 0.0.0.0/0 tcp any 139

7 Drop CIFS (Common Internet File System) TCP frames:occam(config)# access-list ip ip ip-acl-2 deny 0.0.0.0/0 tcp any 445

8 Drop CIFS (Common Internet File System) UDP frames:occam(config)# access-list ip ip ip-acl-2 deny 0.0.0.0/0 udp any 445

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

10 Apply IP ACL ip-acl-2 to VLAN 2:


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 21: Access Control Lists (ACLs)Security Filter Configuration Examples

occam(config)# subscriber ip access-group ip ip-acl-2 in 2



Scenario 2 - Single PVC with PPPoE AccessIn this scenario, each subscriber interface uses a single PVC. Network access is given via PPPoE. All subscriber traffic is on VLAN 2.


2 Permit PPPoE discovery frames:occam(config)# access-list ethernet eth-ip-2 permit 0x8863

3 Permit PPPoE Session frames:occam(config)# access-list ethernet eth-ip-2 permit 0x8864

4 Apply Ethernet ACL ip-acl-2 to VLAN 2:occam(config)# subscriber ethernet access-group eth-ip-2 in 2



Scenario 3 - Multiple PVCsIn this scenario, each subscriber interface uses three PVCs, one for Video (VLAN 3), one for Data (VLAN 4) and one for subscriber modem management (VLAN 5). DHCP discovery frames are allowed but DHCP server responses from subscribers are dropped. NBT packets are also dropped. Since there is an external interface on the subscriber modem for the STBs, there is a possibility that the subscriber could plug in a PC into the STB interface. Applying filters on VLAN 3 (Video VLAN) eliminates risky traffic entering that VLAN. Same filters are not needed on VLAN 5 (Modem VLAN) since that VLAN is internal to the modem on the subscriber end and there is no external interface for that VLAN.

Video VLAN





3 Permit DHCP discovery frames:occam(config)# access-list ip ip-acl-3 permit 0.0.0.0/0 udp any 67

4 Drop NBT Name Service UDP frames:occam(config)# access-list ip ip-acl-3 deny 0.0.0.0/0 udp any 137

5 Drop NBT Datagram UDP frames:occam(config)# access-list ip ip-acl-3 deny 0.0.0.0/0 udp any 138

6 Drop CIFS (Common Internet File System) TCP frames:occam(config)# access-list ip ip-acl-3 deny 0.0.0.0/0 tcp any 139


8 Drop CIFS (Common Internet File System) UDP frames:occam(config)# access-list ip ip-acl-3 deny 0.0.0.0/0 udp any 445

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

10 Apply IP ACL ip-acl-3 to video VLAN 3:occam(config)# subscriber ip access-group ip-acl-3 in 3



Data VLAN




4 Drop NBT Name Service UDP frames:occam(config)# access-list ip ip-acl-4 deny 0.0.0.0/0 udp any 137

5 Drop NBT Datagram UDP frames:


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 21: Access Control Lists (ACLs)Security Filter Configuration Examples

occam(config)# access-list ip ip-acl-4 deny 0.0.0.0/0 udp any 138



8 Drop CIFS (Common Internet File System) UDP frames:occam(config)# access-list ip ip-acl-4 deny 0.0.0.0/0 udp any 445

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

10 Apply IP ACL ip-acl-4 to data VLAN 4:occam(config)# subscriber ip access-group ip-acl-4 in 4



Modem VLAN



3 Allow all IP traffic from subnet10.5.0.0/16 (assuming subscriber modem subnet is that subnet):occam(config)# access-list ip ip-acl-5 permit 10.5.0.0/16

4 Apply IP ACL ip-acl-5 to modem VLAN 5:occam(config)# subscriber ip access-group ip-acl-5 in 5






BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 22: IP Security Management (IPSM)

IPSM Feature Overview

Chapter 22IP Security Management (IPSM)

In This Chapter:IPSM Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442DHCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451ARP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464Blacklisting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469Ingress Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

IPSM Feature OverviewThere are four general categories of IPSM features: DHCP, ARP Proxy, Blacklisting and ingress filtering of ports and VLANs. By using combinations of these features as well as IP ACLs, you can control subscribers on a per port/service basis as well as blacklist ports when malicious traffic events occur. By enabling these features, you may more effectively protect your BLC as well as your networks from harm.

The following table shows some of these malicious traffic events and which IPSM features) should be enabled to protect against them.

Note: Please refer to Chapter 21, Access Control Lists (ACLs) on page 423 for information about how to configure IP and Ethernet ACLs

AssociationsThis 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

Problem Solution

DHCP Server from subscriber IP ACLs

DoS Attacks Blacklisting Agent

Network Neighborhood, through the whole neighborhood

ARP ProxyIP 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


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 22: IP Security Management (IPSM)IPSM Feature Overview

network side associations on page 443. Static association configuration is also described on page 444

DHCPDHCP 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 ProxyARP 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.

Peer to Peer Traffic BlockingThe peer to peer traffic blocking feature must be used in conjunction with ARP proxy. When peer to peer traffic blocking is enabled the BLC responds to all ARP requests with an ARP reply which informs the requesting device to send its packets to the requested IP address to the gateway. This gateway information is learned by the BLC either through the DHCP request or the static association that is configured on the Ethernet service. When using static associations a gateway must be configured.



IPSM Feature Overview

Broadcast Traffic PolicingWhen both DHCP and ARP management are enabled in an Access Profile broadcast traffic received on the service VLAN may be discarded. This feature is not enabled by default. Subscriber broadcast traffic to the network is filtered by configuring an Ethernet ACL for the Service VLAN. Network broadcast traffic to the subscriber is filtered by a configuration parameter for the Service VLAN.

Blacklisting AgentConfiguration of the blacklisting agent is described on page 469. This feature protects the BLC against DoS attacks that utilize certain network control packets.

Ingress FiltersIngress 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 22: IP Security Management (IPSM)Associations

AssociationsThe 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.

Subscriber Side Association DatabaseThe association database may have one or more entries per subscriber interface displaying the VLAN, MAC and IP addresses and the default gateway associated with a particular port. These are created either by DHCP, when DHCP is enabled, or when a static association is configured on a service.

The subscriber side associations database may be displayed by entering the commands show association interface ethernet {ethernet-port-number} and show association interface dsl {dsl-port-number} from Privileged and User modes.

IP addresses of subscriber's device.The mask "/32" shows that this is

a host association.

IP addresses of gateway that isused by the subscriber's device

to access networks that arenot on its local subnet.

This association was createdstatically and is

administratively managed

The State field displays whether or not the MAC address has been pusheddown 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 DHCPand the state field shows something other than "active" for a valid MAC

address (for example "not installed"), there is an error in your configuration.

VLAN that thesubscriber's device is on.

In this example bothdevices are on VLAN 3.

This association wascreated dynamically

by DHCP

Occam#show association interface ethernet 4Interface: Ethernet4VLAN MAC Address IP Address Gateway Type Owner State3 00:02:02:00:05:a6 192.168.35.246/32 192.168.35.4 Dynamic DHCP Active3 00:02:02:00:07:a0 192.168.35.245/32 192.168.35.4 Dynamic DHCP Active

Interface: Ethernet4VLAN MAC Address IP Address Gateway Type Owner State3 00:09:09:09:09:02 9.9.9.2/32 9.9.9.100 Static MGMT Active

MAC address of thesubscriber's device



Associations

Network Side AssociationsAssociations on the network side display the VLAN, MAC and IP addresses for other devices in the network. When a gateway is specified in a subscriber side association database it is automatically populated in the network side association database.

When ARP Proxy is enabled in access profile configuration mode the BLC ARP agent will learn and add network associations based on configuration. When the ARP feature “reply gateway” is not enabled, and a subscriber side device ARPs for a network device within its subnet (when a network device is beyond the subscriber side’s subnet, the subscriber device will ARP for its gateway) the ARP agent will populate the network side associations table when it receives a ARP reply. When ARP proxy is disabled the network side ARP cache will not be populated.

Displaying a Network Side Associations Database

The network side associations database may be displayed by entering the command show association network from Privileged and User modes. Sample output from this command and notes to help interpret the fields is shown below:

Occam#show association networkInterface: NetworkVLAN MAC Address IP Address Owner Age4 00:01:30:f4:49:e0 192.168.17.4 ARP-GW 5114 00:01:30:86:0f:00 192.168.17.1 ARP 5115 00:01:30:f4:49:e0 192.168.36.4 ARP-GW 5713 00:01:30:f4:49:e0 192.168.35.4 ARP-GW 5713 00:03:47:71:a2:b7 9.9.9.100 ARP-GW 571

IP address of the device onthe network side

VLANs on thenetwork interface

MAC address of the device onthe network side (i.e., the

gateway)There are two types of owners of

network associations:ARP and ARP-GW. The ARP-GWis a gateway that is used by a

subscriber association.

Age in seconds



Static AssociationsA 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.

Ethernetoccam(config-if-eth-service-<1-5>)# associate {mac-address} [ip-address] [ip-mask] [default gateway]

DSLoccam(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



Associations

Host Static Associations

When you configure a host static association with the associate {mac-address} [ip-address] [ip-mask] [default gateway] command:

the MAC address is required but may be a wildcard.

Note: A wildcard MAC address is all zeros: 00:00:00:00:00:00 and matches any MAC address.

the IP addresses is required.

the subnet mask will default to “/32” when not configured.

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

Subnet Static Associations

A subnet association is typically configured in a business application. Extended and remote subnet associations are supported, depending on the addressing architecture.

When you configure a subnet static association with the associate {mac-address} [ip-address] [ip-mask] [default gateway] command:

the MAC is required but may be a wildcard.


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.

Extended Subnet Configuration

In an extended subnet network configuration everything except the gateway device is reachable through the service. The gateway device is within the subnet but it is on the network side. There may be router device on the subscriber side.

Multiple subnets can reside on the same transport VLAN when the upstream router has the ability to support multiple subnets on the same line.



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:

occam(config-if-eth-service-<1-5>)# associate 00:00:00:00:00:00 10.1.1.0 255.255.255.0 10.1.1.1


the subnet mask

the address of the gateway

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.



Associations

Figure 22-1 shows an example of an extended subnet network configuration.

Figure 22-1: Extended Subnet Static Association

EPS RING VPS

VPS

BLC 6312VPS

VPT VPT

INTERNET

VPS

ROUTER A

ONT

ROUTER B

IP Address:10.1.1.2

One static MAC may be configured on the PVC:Occam(config-if-eth-service-<1-5>)#associate 00:00:00:00:00:00 10.1.1.0255.255.255.0 10.1.1.1

Gateway address:10.1.1.1

10.1.1.6

10.1.1.3

10.1.1.4

10.1.1.5

Gateway address for all PCs is on the network siderouter (router A): 10.1.1.1



Remote Subnet Associations

In this configuration the entire subnet is behind a subscriber side router. The router’s gateway is outside of the subscriber subnet on the network side. This configuration is used when that administrator of a network gives an entire network behind a router on the business side. All the devices on the subnet are on the other side of the Ethernet port, behind the router and the router's interface on the network side is on a different subnet.

Both the subnet and host associations are required. The MAC address of both associations may or may not be wild. The source MAC address will always be the router's MAC address, since the router is always going to be routing packets through it.

The MAC addresses can be wild. However, specifying the MAC address provides increased security when ingress filters are configured. Figure 22-2 shows an example of an remote subnet network configuration.



Associations

Figure 22-2: Remote Subnet Static Association

EPS RING VPS

VPS

BLC 6312VPS

VPT VPT

INTERNET

VPS

ROUTER A

ONT

ROUTER B

IP Address:10.1.1.2

Two static associations may be configured on thesame PVC:

1. Static association for router's interface on thenetwork side:Occam(config-if-eth-service-<1-5>)#associate 00:30:da:37:4b:1a 10.100.1.32255.255.255.255 10.100.1.1

2. This may be configured either of these ways:

a. Occam(config-if-eth-service-<1-5>)# associate 00:00:00:00:00:00 10.1.1.0255.255.255.0 10.100.1.1

OR

b. Occam(config-if-eth-service-<1-5>)# associate 10:30:da:37:4b:1a 10.1.1.0255.255.255.0 10.100.1.1

Gateway address:10.1.1.1

10.1.1.6

10.1.1.3

10.1.1.4

10.1.1.5



Managing AssociationsRemoving static associations for all or a single Ethernet service may be done 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} {ip-address}



DHCP Configuration

DHCP ConfigurationOccam 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: NTP should be configured when DHCP is enabled on the BLC.

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 LeasesWhen 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 22: IP Security Management (IPSM)DHCP Configuration

DHCP SnoopingDHCP 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.

Configuring DHCP Snooping


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 snooping on a specific VLAN:occam(config-access-profile)# dhcp mode snoop

DHCP Layer 2 and Layer 3 RelayDHPC Layer 2 and Layer 3 Relay trap DHCP packets from subscriber devices. Both features support improved security by appending information that can be used by the DHCP server to control IP address assignment within the BLC network. This feature is based on RFC 3046 DHCP Relay Agent Information using Option 82 with the Agent Circuit ID sub-option. Information may be added to the remote ID or Circuit ID. These fields can be used to allow one DHCP server to specifically assign IP addresses for different purposes. In other words, the DHCP server may be configured to hand out different IP subnets for different requests coming from different VLAN's, Ethernet service's, or BLC's. The Option 82 parameters are removed before the packet is sent to the subscriber device.

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.



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.



Configuring DHCP Layer 2 and Layer 3 Relay



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 oroccam(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}

The “no” form of the command (no dhcp circuit-id) causes the DHCP agent to insert the default Circuit ID sub-option:

DSL profile circuit id default: ${SYSNAME} atm ${SLOT}/${DEVNAME}:${PVC}

Ethernet access profile circuit id default:

text-string This is a text phrase that may be up to 63 characters including keywords. Text may be added before, between and after keywords.

To use a keyword enter the dollar sign symbol and then one or more of the following keywords in brackets:SYSNAME, SYSIP,SLOT, DEVNAME, VLAN, PVC

For example, the following command configures the circuit ID string to contain the system name and the slot number:dhcp circuit-id ${SYSNAME} ${SLOT}

There are no spaces between the brackets and the keywords enclosed in the brackets. For example, {SYSNAME} is valid but { SYSNAME } is not.For more information about the keywords please refer to the Command Reference Guide.



DHCP Configuration

${SYSNAME} eth ${SLOT}/${DEVNAME}:${VLAN}

Note: When using the keyword VLAN, the EPS VLAN defined in the access profile is inserted as an option 82 parameter by the BLC's relay agent. When the DHCP packet is forwarded out of the local network, the VLAN ID in the DHCP packet header may change depending on the configuration of the Ethernet egress port but the VLAN ID inserted as an option 82 parameter will NOT be changed with it. This should be taken into account when considering whether to use the VLAN keyword or hard-code the VLAN ID into the option string. For example: L2 relay is configured. A packet has VLAN 4 inserted as the option 82 parameter. The packet is also relayed into the network with VLAN 4 in the DHCP packet header. The egress Ethernet interface to the DHCP servers has a tagged profile that changes the external VLAN ID in the packet header from VLAN 4 to VLAN 1024. When the DHCP packet traverses the tagged interface, the VLAN in the DHCP packet header will be modified from VLAN 4 to VLAN 1024, while the option 82 VLAN ID will remain VLAN 4.

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}

The “no” form of the command (no dhcp remote-id) causes the DHCP agent to not insert the Relay Remote ID sub-option. There is no default option inserted for the remote ID.

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 repeatedlyoccam(config-access-profile)# dhcp server {ip-address}

For example, to configure servers with the IP addresses 132.178.11.10,

text-string This is a text phrase that may be up to 63 characters, including keywords. Text may be added before, between and after keywords.To use a keyword enter the dollar sign symbol and then one or more of the following keywords in brackets:SYSNAME, SYSIP,SLOT, DEVNAME, VLAN, SERVICEFor example, the following command configures the remote ID string to contain the system name and the slot number:dhcp remote-id ${SYSNAME} ${SLOT}

Note: There are no spaces between the brackets and the keywords enclosed in the brackets. For example, {SYSNAME} is valid but { SYSNAME } is not.



132.178.11.11 and 132.178.11.12, enter the commands:occam(config-access-profile)## dhcp server 132.178.11.10occam(config-access-profile)# dhcp server 132.178.11.11occam(config-access-profile)# dhcp server 132.178.11.12

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



DHCP Configuration

Displaying DHCP Configuration Information

DHCP Summary Command

show dhcp summary: use this command to display DHCP information in a summarized format. Sample output is shown on page 458.

DHCP Clients Commands

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.

DHCP Interface Statistics Command

show dhcp interfaces statistics interface ethernet: use this command to display information about DHCP statistics information for the selected Ethernet interface. Sample output is shown on page 461.

DHCP Lease Command

show dhcp lease: use this command to display DHCP IP address leased from a server. Sample output is shown on page 462.

DHCP Servers Command

show dhcp servers interface ethernet: use this command to display DHCP severs information for a selected Ethernet interface. Sample output is shown on page 463.



Displaying Summarized DHCP Information

Use the command show dhcp summary to display information about the BLC’s DHCP agent in a summarized format. The following is sample output of the show dhcp summary command:

occam# show dhcp summaryDHCP Snoop Statistics: DHCP snooped devices = 48 Rx unknown clients = 0

DHCP Relay Configuration: Relay mode = Discard Add agent options = No Drop agent mismatches = No Max hop count = 4

DHCP Relay Statistics: DHCP relayed devices = 51 IP Header Identifier = 11714 No IP Address = 0 Max hop exceeds = 0 Giaddr errors = 0 Size exceeds = 0 Format errors = 0 Receive errors = 0 Network client discards = 0 Rx Server unknowns = 0

occam#



DHCP Configuration

DHCP Clients Commands

Use the show dhcp clients command to display information about DHCP clients. The following is sample output from the show dhcp clients command:

occam# show dhcp clientsInterface: Ethernet21VLAN Client IP Address State Persisted Lease Expiry3 00:02:02:00:16:09 192.168.35.126 Unknown Current Tue Feb 21 11:49:33 20063 00:02:02:00:15:e9 192.168.35.125 Ack Update Thu Jan 1 16:11:34 2004

Interface: Ethernet3VLAN Client IP Address State Persisted Lease Expiry3 00:02:02:00:05:a6 192.168.35.129 Ack Update Thu Jan 1 16:12:07 20043 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>

Use the show dhcp clients information {VLAN number} {mac-address} command to display DHCP clients information for a selected MAC address. Enter the MAC address in the format AA:BB:CC:DD:EE:FF. The following is sample output from the command:occam# show dhcp clients information 3 00:02:02:00:15:f4Client: 00:02:02:00:15:f4

Birth date: Thu Jan 1 16:02:10 2004Lease acquired on: Fri Sep 30 15:47:34 2005Lease duration: 3600 secondsLease expires on Fri Sep 30 16:47:34 2005

BOOTP information follows:

L2 MAC Address: 00:02:02:00:15:f4Client Hardware Address: 00:02:02:00:15:f4Client Requested IP Address: 192.168.35.242



Server Assigned IP Address: 192.168.35.242BOOTP Server: 192.168.48.3BOOTP Gateway: 0.0.0.0

DHCP options follow:

Magic Cookie: 0x63 0x82 0x53 0x63option: Server Id(54) - 192.168.48.3option: Network Mask(1) - 255.255.255.0option: Default Gateways(3) - 192.168.35.4 option: DNS Servers(6) - 192.168.10.1 option: Domain(15) - occamnetworks.comoption: 82 11 0x01 0x09 0x44 0x53option: ++++++ 0x4c 0x34 0x2f 0x70option: ++++++ 0x76 0x63 0x32occam#

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:c7Client: 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

Use the show dhcp clients interface ethernet {port-number} command to displays DHCP clients information for a selected Ethernet interface. For example:

occam# show dhcp clients interface ethernet 3Interface: Ethernet3VLAN Client IP Address State Persisted Lease Expiry3 00:02:02:00:05:a6 192.168.35.129 Ack Update Thu Jan 1 16:12:07 20043 00:02:02:00:07:a0 192.168.35.130 Ack Update Thu Jan 1 16:12:03 2004



DHCP Configuration

DHCP Interface Statistics Command

Use the show dhcp interfaces statistics interface ethernet {interface-number} command to display DHCP statistics for the selected interface. The following example shows DHCP statistics for Ethernet interface 13:occam# show dhcp interface statistics ethernet 3Subscriber Interface: Ethernet3VLAN 4 Rx Unicast pkts = 0 Rx Broadcast pkts = 0 Rx Broadcast filtered pkts = 0 Rx Errors = 0 Rx Discards = 0 Rx UDP port errors = 0 Rx UDP bad length field errors = 0 Rx BOOTP errors = 0 Rx DHCP errors = 0 Tx Unicast pkts = 0 Tx Broadcast pkts = 0 Tx errors = 0 VLAN MAC violations = 0 FDB add failures = 0 MAC address changes = 0 IP address changes = 0VLAN 3 Rx Unicast pkts = 5 Rx Broadcast pkts = 0 Rx Broadcast filtered pkts = 0 Rx Errors = 0 Rx Discards = 0 Rx UDP port errors = 0 Rx UDP bad length field errors = 0 Rx BOOTP errors = 0 Rx DHCP errors = 0 Tx Unicast pkts = 4 Tx Broadcast pkts = 0 Tx errors = 0 VLAN MAC violations = 0 FDB add failures = 0 MAC address changes = 0 IP address changes = 0occam#

<output truncated>



DHCP Lease Command

Use the command show dhcp lease to display DHCP addresses leased from a server.

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 leaseDevice bvi1: IP: 192.168.4.167Netmask: 255.255.255.0Broadcast: 192.168.4.255Network: 192.168.4.0Next server 192.168.4.101Gateway: 192.168.4.254Nameservers: 192.168.2.1Renewal time: Sun Jan 4 01:30:12 1970Expiration time: Sun Jan 4 03:00:12 1970

Table 22-1: show dhcp lease Field Descriptions

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.



DHCP Configuration

DHCP Servers Command

Use the command show dhcp servers interface ethernet {interface-number} to display DHCP sever information for a selected Ethernet interface. The following is output of the show dhcp servers interface ethernet command:occam# show dhcp servers interface ethernet 1

VLAN: 5Server SIADDR 00:03:47:71:9a:f2 192.168.37.10

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.

Field Description


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 22: IP Security Management (IPSM)ARP Proxy

ARP ProxyNote: In this section the term client refers to the receiver of the IP address.

ARPAddress 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 ProxyOccam 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.



ARP Proxy

ARP Proxy in Conjunction with Peer to Peer Traffic BlockingPeer to peer traffic blocking is enabled with the arp reply gateway command. When this feature is enabled the ARP agent will always reply with the default gateway MAC address whenever a device generates an ARP request. The default gateway for a subscriber device is determined from either the DHCP servers’ response to the requesting client or via static configuration.

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.



Broadcast Traffic PolicingWhen both DHCP and ARP management are enabled in an Access Profile broadcast traffic received on the service VLAN may be discarded. This feature is not enabled by default. Subscriber broadcast traffic to the network is filtered by configuring an Ethernet ACL for the Service VLAN. Network broadcast traffic to the subscriber is filtered by a configuration parameter for the Service VLAN.

Broadcast flooding on Ethernet ports is enabled by default. The following Global Configuration mode commands enable and disable broadcast flooding on a particular VLAN. Specify a VLAN number between 2 and 122.

DSL:occam(config)# subscriber access broadcast flooding enable {VLAN ID}occam(config)# subscriber access broadcast flooding disable {VLAN ID}

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

Use the command show subscriber global-config to display on which VLANs broadcast flooding has been disabled. Sample output for this command is shown below:occam# show subscriber global-configsubscriber access broadcast flooding:vlan 22: disabled



ARP Proxy

Configuring ARP Proxy



3 Configure the ARP mode to proxy or none:


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

6 To populate the subscriber association database, DHCP or a static association must be configured:

Configure a DHCP Mode

a Enable DHCP snooping mode, DHCP Layer 2 relay mode or DHCP Layer 3 relay mode:occam(config-access-profile)# dhcp mode snoopORoccam(config-access-profile)# dhcp mode l2relayORoccam(config-access-profile)# dhcp mode l3relay

b Exit Access Profile Configuration Mode:occam(config-access-profile)# exit

OR

Configure a static association between MAC addresses and IP addresses:

a Exit access-profile configuration mode:occam(config-access-profile)# exit

b Enter Ethernet Interface Configuration mode specifying an interface by



number. The parameters are from one through twenty-two:occam(config)# interface ethernet {1-22}

c Enter Ethernet Service Configuration mode specifying a service by number. The parameters are from one through five:occam(config-if-eth)# service {1-5}

d Enter the command associate. The following table details what parameters are mandator and which are optional:

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}

f Exit Ethernet Service Configuration mode:occam(config-if-eth)# exit

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}

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.



Blacklisting

BlacklistingOccam 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:

An alarm will be triggered

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 22: IP Security Management (IPSM)Blacklisting

Configuring Blacklisting



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}

The command options are:

arp Specifies to rate limit the ARP protocol

dhcp Specifies to rate limit the DHCP protocol

igmp Specifies to rate limit the IGMP protocol

PPS Number of packets per second allowed on averageFor ARP and DHCP the parameters are between 1-300For IGMP the parameters are between 10-300

1-30 Interval in seconds over which to monitor average packet rates.

1-100 The clearing interval is the period of time that has an acceptable packet limit after an unacceptable number of packets has passed through the port.

The number entered determines how many times to multiply the number of “monitoring” seconds (previous row).

For example, if you choose to monitor control packet rates for ten seconds and enter the number “two”, there will have to be acceptable packet limits for twenty seconds before the port would be determined “clear” after an error condition.



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

Clearing a Blacklisted Ethernet Service

The Privileged mode command clear blacklist subscriber {port-number} {Ethernet service-number} forces the clearing of a blacklisted Ethernet service, even when it has not passed the “clearing interval”. occam# clear blacklist {port-number} {Ethernet service-number}

This command will clear the Ethernet service but the Ethernet service will continue to be checked. When the traffic level is beyond configured rates the Ethernet service will be blacklisted again.

shutdown Configures the Ethernet services associated with the access profile to be shutdown and an alarm to be issued when the acceptable number of packets per second is exceeded.

alarm Configures that an alarm be issued when the acceptable number of packets per second is exceeded.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 22: IP Security Management (IPSM)Blacklisting

Viewing Blacklisted Ethernet Services

The mode commands show blacklist current and show blacklist history display the current and last fifty blacklisted ports/Ethernet services. These commands must be issued from Privileged Command mode.

The following is sample output from the command show blacklist current:

The “Device” column contains the offending device’s MAC address.

occam# show blacklist currentPort Device Port State Trigger Entered Retried Retries18-1 00:04:32:00:01:34 Disabled ARP 06:27:03 Feb 9, 2005 08:27:03 Feb 9, 2005 1221-1 00:04:32:00:11:FE Alarm DHCP 07:27:03 Feb 9, 2005 08:28:03 Feb 9, 2005 1022-1 00:04:32:00:34:12 Testing ARP 08:02:03 Feb 9, 2005 08:28:03 Feb 9, 2005 6



Ingress Filters

Ingress FiltersIngress 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.

Access Control ListsIngress filters are enabled through the configuration of Access Control Lists. An Access Control List (ACL) defines a list of individual filters specific to a VLAN. These filters define the VLAN access policy. Subscriber VLANs on a BLC are filtered on interfaces through the use of configurable Access Control Lists (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 configuration is described in Chapter 21, Access Control Lists (ACLs) on page 423.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 22: IP Security Management (IPSM)Ingress Filters

Ingress Filter ConfigurationIngress filtering requires the use of the associations database.

The following Global Configuration mode command creates an ACL:occam(config)# access-list ip {acl-name} permit associations[/subnet]

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

you must use the following command to enable ingress filtering:occam(config)# access-list ip {acl-name} permit associations/24

If you configure a static association with the command:occam(config-if-eth-service-1)# associate 00:00:00:00:00:00 192.168.0.0 255.255.0.0 192.168.45.1

you must use the following command to enable ingress filtering:occam(config)# access-list ip {acl-name} permit associations/16

Ingress Filtering with DHCP Enabled

An ingress filter is applied to the VLAN of the Ethernet service when the device obtains a lease via DHCP. This filter will remain in place for as long as the lease is valid. The ingress filter inspects all packets and compares the MAC and the assigned IP addresses of the device to the information in the associations database. When these addresses don't match, the packets are discarded. The device may send packets to any destination layer 2 device within its service VLAN, as long as its source MAC and IP satisfy the filter criteria.

Ingress Filtering with Peer to Peer Traffic Blocking Enabled

When ingress filtering is used in conjunction with the peer to peer traffic blocking feature, not only will the ingress filter drop any MAC/IP associations that don’t



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.

Note: An ACL is always terminated by an implicit deny statement for everything.

occam(config)# access-list ip {acl-name} {deny, permit} {WORD[/n]}{icmp|udp|tcp}{<1-65535>|ANY} {<1-65535>|ANY}

acl-name Specifies the IP ACL name. The ACL name is an alphanumeric name and may also include a dash (-) and and underscore (_).

deny Specify packets to reject

permit Specify packets to accept

{filter[/source-mask]} Filter based on the Source IP subnet in an A.B.C.D format. Optionally, add a source mask. The source mask is required when you are specifying a subnet mask. It is optional when the Source IP address (srcIP) is a host address.ORFilter based on the associations database Option-ally, add a source mask.

[icmp|udp|tcp] (Optional) Specifies the layer 4 protocol carried by the IP datagram: ICMP, UDP or TCP

[<1-65535>|ANY] (Optional) source portWhen not specified, the source port is assumed to be “match any”. This parameter is only used for UDP and TCP.

[<1-65535>|ANY] (Optional) destination portWhen not specified, the destination port is assumed to be “match any”. This parameter is only used for UDP and TCP.



Displaying Your Ingress Filter ConfigurationUse the show ingress_filters command to display the ingress filters that have been installed:

occam# show ingress_filtersInterface: Ethernet21Vlan Owner State Hits Dst MAC Source IP 3 INGRESS Active - Any 192.168.35.126/32 3 INGRESS Active - Any 192.168.35.125/32

<output truncated>

Ingress Filter Configuration ExamplesIngress filters can be used by themselves or in conjunction with other security ACLs. When ingress filters are used with ARP proxy and peer to peer traffic blocking, the gateway router may be configured to block specific types of traffic such as NetBIOS and CIFS, thus limiting the number of filter and mask resources used on the BLC.

When you are not using ARP proxy and peer to peer traffic blocking and would like to block traffic such as NetBIOS and DHCP server responses from the client side, you may configure access lists that block this traffic as well as have ingress filters configured.

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

IP access list ip-acl-1 is applied to VLAN 4 using the following command:occam(config)# subscriber ip access-group ip-acl-1 in 4

Use the following command to view the filter:

occam# show subscriber access-group 4




Fwd Static INGRESS Active 0 4 0x800 0.0.0.0/32 Any Any Any


Fwd Static SYSTEM Active 0 4 0x806




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 68occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 udp 67occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 tcp any 139occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 138occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 137occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 udp any 445occam(config)# access-list ip ip-acl-10 deny 0.0.0.0/0 tcp any 445occam(config)# access-list ip ip-acl-10 permit associations

IP access list ip-acl-10 is applied to VLAN 3 using the following command:occam(config)# subscriber ip access-group ip-acl-10 in 3

Use the following command to view the filter:

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 68occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 udp 67occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 tcp any 139occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 138occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 137occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 udp any 445occam(config)# access-list ip ip-acl-5 deny 0.0.0.0/0 tcp any 445occam(config)# access-list ip ip-acl-5 permit associations/24

occam# show access-group ip 3





Drop Static MGMT Active 0 3 0x800 Any 17 67 Any





Fwd Static INGRESS Active 0 3 0x800 0.0.0.0/32 Any Any Any


Fwd Static SYSTEM Active 0 3 0x806

Fwd Static SYSTEM Active 0 3 Any




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 23: Managed Multicast Via IGMP Proxy

Introduction

Chapter 23Managed Multicast Via IGMP Proxy

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479Interface Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479Optional IP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481Sample IGMP Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483Configuring Managed Multicast Traffic Parameters on Ethernet Interfaces . . . . 485Configuring Multicast Parameters on Ethernet Subscriber Interfaces . . . . . . . . . 486Displaying Information About Your IGMP Configuration . . . . . . . . . . . . . . . . . . . 491

IntroductionThe 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.

Interface Configuration OptionsAn interface may be configured as an IGMP router, passthrough or host facing interface. An Ethernet interface that is used for subscriber traffic may only configured as an IGMP host.

Router InterfaceIGMP 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

ORoccam(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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 23: Managed Multicast Via IGMP ProxyInterface Configuration Options

Passthrough InterfaceAny 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 InterfaceIGMP 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.

From RFC 2236:

“(Host facing interfaces) use IGMP to learn which groups have members on each of their attached physical networks. A (host facing interface) keeps a list of multicast group memberships for each attached network, and a timer for each membership....(Host facing interfaces) periodically send a General Query on each attached network for which this (host facing interface) is the Querier, to solicit membership information.”

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 VersionIGMP 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}



Optional IP Address Configuration

Disabling Traffic ForwardingUse the command no igmp to disable traffic forwarding.

Optional IP Address ConfigurationThe following commands take an optional IP address:

igmp host [ip-address]

igmp router [ip-address]

igmp passthrough [ip-address]

This optional IP address will be used by the IGMP daemon whenever sourcing packets from the interface that the command has been applied to either directly or indirectly (i.e.: via the access profile).

Default IP AddressThe 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

Applying or Changing an IP AddressTo apply an address enter the command igmp host 0.0.0.0.

To change the address re-enter the command with another IP address (for example, igmp host 1.2.3.4.)

Recommended IP AddressThe 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 23: Managed Multicast Via IGMP ProxyOptional IP Address Configuration

If the IP address is configured on ring Ethernet hosts ports it MUST be configured to be different from the other VPT/bookend. If the address is configured to be the same each VTP/bookend will remain in the Queries state resulting in increased bandwidth demands and CPU overhead which could possibly affect performance.

In all cases when specifying a specific IP address, the address should be unique to the subnet to which the address is a member.



Sample IGMP Configurations

Sample IGMP ConfigurationsFigure 23-1: Sample Managed Multicast EPS Ring Configuration

VIDEOSOURCE

A

LEGEND"A": ETHERNET INTERFACE CONFIGURED WITH THE COMMAND

occam(config-if-eth)# igmp router

"B": ETHERNET INTERFACE CONFIGURED WITH THE COMMANDoccam(config-if-eth)# igmp host

"C": ETHERNET INTERFACE CONFIGURED WITH THE COMMANDoccam(config-if-eth)# igmp passthrough

"D": ACCESS PROFILE CONFIGURED WITH THE COMMANDoccam(config-access-profile)# igmp host

BLC 6314 BLC 6314C C

BLC 6312C

CBLC 6312

C

C

BLC 6312

SET TOPBOX

ONT

D

SET TOPBOX

D D

ONT ONT

SET TOPBOX

BLC 6312

C

CBLC 6312

C

C

C C

B B


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 23: Managed Multicast Via IGMP ProxySample IGMP Configurations

Figure 23-2: Managed Multicast Network Configuration with Subtended Ring

VIDEOSOURCE

A

LEGEND"A": ETHERNET INTERFACE CONFIGURED WITH THE COMMAND

occam(config-if-eth)# igmp router

"B": ETHERNET INTERFACE CONFIGURED WITH THE COMMANDoccam(config-if-eth)# igmp host

"C": ETHERNET INTERFACE CONFIGURED WITH THE COMMANDoccam(config-if-eth)# igmp passthrough

"D": ACCESS PROFILE CONFIGURED WITH THE COMMANDoccam(config-access-profile)# igmp host

BLC 6314 BLC 6314C C

BLC 6312C

CBLC 6312

C

C

BLC 6312

BLC 6312BLC 6312

SET TOPBOX

ONT

C

C C

C

CC

B B

D

SET TOPBOX

D D

ONT ONT

SET TOPBOX

B B



Configuring Managed Multicast Traffic Parameters on Ethernet Interfaces

Configuring Managed Multicast Traffic Parameters on Ethernet Interfaces


2 Enter Ethernet Interface Mode:occam(config)# interface ethernet {1-22}

3 Configure the Ethernet interface as a host facing IGMP interface, as a network facing IGMP interface or as a multicast passthrough interface:

Host Facing IGMP Interface:occam(config-if-eth)# igmp host [ip-address]

Network Facing IGMP Interface:occam(config-if-eth)# igmp router[ip-address]

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.

5 Exit Ethernet Interface Mode:occam(config-if-eth)# exit




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 23: Managed Multicast Via IGMP ProxyConfiguring Multicast Parameters on Ethernet Subscriber Interfaces

Configuring Multicast Parameters on Ethernet Subscriber Interfaces

Multicast parameters on Ethernet subscriber interfaces are configured though access profiles. To configure these parameters you must:

First, configure an access profile. This is described on page 487.

Configure the access profile with the command igmp host

Optionally change the limit of the number of groups on the port to which the profile is attached from the default value of 255 with the command igmp group-limit

Define the network VLAN with the command eps vlan.

Optionally assign rate-limiting policy maps to the access profile.

Optionally, configure the following IPSM features: DHCP, ARP Proxy, Black-listing and ingress filtering of ports and VLANs. Configuration of these features is described in Chapter 22, IP Security Management (IPSM) on page 439.

Second, configure an Ethernet port as a subscriber interface with the command eps access subscriber. This is described on page 488.

Third, configure an Ethernet service on the Ethernet subscriber interface.

Select a number for the Ethernet service with the command service.

Attach the access profile to the service with the command access-profile.

Optionally change the limit of the number of groups on the port to which the profile is attached from the default value of 255 with the command igmp group-limit. This is described on page 488.

Use the command match vlan to specify the VLAN to which the service is attached. This is the user (ONT) VLAN.




Configuring an Access ProfilePlease see the Chapter 14, Ethernet Subscriber Interfaces on page 281 for further information about configuring an access profile. This chapter will describe only the IGMP configuration options available from Access Profile Configuration Mode



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}


4 Configure the port the profile is attached to as a IGMP host to enable forwarding of multicast traffic to downstream subscriber interfaces. This feature is disabled by default:occam(config-access-profile)# igmp host

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.

Rate Limit Unicast Traffic by Assigning Service Policy Parameters

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}



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}




Configuring an Ethernet Port as a Subscriber Interface


2 Enter Ethernet Interface Configuration mode specifying an interface by number. The parameters are from one through twenty-two:

occam(config)# interface ethernet {1-22}

3 Configure the Ethernet interface to become a subscriber interface:

occam(config-if-eth)# eps access subscriber

4 Exit Ethernet Interface Configuration mode:

occam(config-if-eth)# exit

Configuring an Ethernet ServiceThere are no default Ethernet services. If no Ethernet service is configured on an Ethernet interface after it has been configured as a subscriber interface, the interface cannot be enabled. Conversely, if the last Ethernet service is deleted, the interface will be disabled.

There may be one or more "service" configurations on tagged subscriber interfaces.


2 Attach an access profile to the service:occam(config-if-eth-service-<1-5>)#access-profile profile-name




3 Specify a VLAN to which the Ethernet service interface is attached. Incoming traffic must match this VLAN ID in order for this service to be applied to the traffic.

Note: The command match vlan specifies the user ONT VLAN to which an Ethernet service is attached. Use the command eps vlan from Access Profile Configuration mode to define the network VLAN:occam(config-if-eth-service-<1-5>)# match vlan {1-4094}

Use the command no match vlan {1-4094} to remove this VLAN association from an Ethernet Service.

4 Optionally, configure a static MAC/IP address association:occam(config-if-eth-service-<1-5>)# associate {mac-address} [ip-address] [ip-mask] [default gateway]

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}

Note: BLC 6450: occam(config-if-eth-service-<1-5>)# override access-profile igmp group-limit {1-1000}

7 Optionally, set maximum number of MAC addresses allowed, overriding the MAC limit set in the attached access profile:occam(config-if-eth-service-<1-5>)# override access-profile mac limit {1-64}

8 Optionally, enable or disable MAC learning, overriding the setting in the attached access profile:occam(config-if-eth-service-<1-5>)# override access-profile mac-learning {enable | disable}





11 Enable the Ethernet Interface:occam(config-if-eth)# no shutdown

12 Exit Ethernet Interface Configuration mode:occam(config-if-eth)# exit




Displaying Information About Your IGMP Configuration


Use the show igmp command to display information about your IGMP configuration. The following example shows sample output for this command:occam# show igmpIGMP Version = 2Robustness Variable = 2 Query Interval = 150 (1/10 sec)Query Response Interval = 15 (1/10 sec)Group Membership Interval = 315 (1/10 sec)Other Querier Present Interval = 307 (1/10 sec)Startup Query Interval = 10 (1/10 sec)Startup Query Count = 5 Last Member Query Interval = 2 (1/10 sec)Last Member Query Count = 2 Unsolicited Report Interval = 20 (1/10 sec)Version1 Router Present Timeout = 600 (1/10 sec)Version1 Hosts Present Timeout = 315 (1/10 sec)occam#

Show Multicast Interface CommandsUse the show multicast command to display what multicast streams are open. The following example shows sample output for this command:occam# show multicastTotal streams open: 4224.0.18.103 users: 1224.0.18.104 users: 1225.10.10.10 users: 2239.255.255.250 users: 1occam#

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 summaryTotal streams open: 4Port 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#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 23: Managed Multicast Via IGMP ProxyDisplaying 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 1Total streams open: 0Port Mode Stream-limit Version Status Ethernet5/1 PASSTHRU unlimited IGMPV* Listener

Rx pkts: 1244Rx Reports: 1244Rx Leaves: 0Rx General Queries: 468Rx Group Queries: 4Rx unknown msg types: 0Rx CRC Errors: 0Filtered Src IP's: 0Filtered Group's: 0Tx pkts: 1254Tx Reports: 1252Tx Leaves: 2Tx General Queries: 0Tx Group Queries: 0Suppressed Reports: 1Group 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: 4Port 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.203Ethernet5/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




192.168.21.135Ethernet5/2 HOST 255 IGMPV2 Querier occam>


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 23: Managed Multicast Via IGMP ProxyDisplaying Information About Your IGMP Configuration


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 24: Configuring Circuit Emulation Switching (CES)

Introduction

Chapter 24Configuring Circuit Emulation Switching (CES)

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495Choosing a T1 Line Framing Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497Configuring Synchronous CES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499Configuring Asynchronous CES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509Terminating a CES Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515Viewing Your CES Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

IntroductionThe 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 ApplicationsThe 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 24: Configuring Circuit Emulation Switching (CES)Introduction

A tie line between two PBXs in a campus environment.

Transport of data to an ISP over an unchannelized T1

Bandwidth RequirementCES 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.

Because of processing requirements, CES is not permitted on blades configured as shelf controllers in a shelf configuration or on blades with a primary or secondary GR-303 DS1.

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.

T1s configured as unframed may not be used as the primary or secondary network clock source for the BLC.


!



Choosing a T1 Line Framing Format

Choosing a T1 Line Framing FormatThe command service-module t1 framing command from Serial Interface Configuration Mode is used to specify a framing format for T1 lines. The use of this command is shown the sections Configuring T1 Interfaces in a Synchronous CES Network(page 504) and Configuring T1 Interfaces in an Asynchronous CES Network(page 510).

The framing type is dependent on the type of T1 line you are transporting with CES.


Some basic guidelines for configuring CES framing:

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.

service-module t1 framing esf This command specifies Extended Super Frame (ESF) as the T1 frame type.

service-module t1 framing sf This command specifies Super Frame as the T1 frame type.

service-module t1 framing unframed

This command specifies UNFRAMED as the T1 frame type.This format is rarely used, and is never used for T1s carrying voice traffic.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 24: Configuring Circuit Emulation Switching (CES)Choosing a T1 Line Framing Format

Sample CES ApplicationsThe following examples show three typical CES applications.

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.

Figure 24-2: Transport of Channelized T1 between a Class 5 switch and a Legacy POTS Channel Bank

Framing/linecoding should be either SF/AMI or ESF/B8ZS, as required in the channel bank.

Figure 24-3: Transport of Unchannelized T1 Line Carrying Data to an ISP

Framing and coding in this example should be set to ESF/B8ZS. If the T1 line uses a non-standard (proprietary) framing type, it must be configured as UNFRAMED on the BLC. If unframed mode is required, and one BLC is providing clock to the other with NSP, the BLC configured as “nsp mode tx” must derive its clock from a different T1, since unframed T1 lines cannot be the BLC's clock source.

IP GigE - EPS

CLASS 5 SWITCH BLC "A" BLC "B" PBX

IP GigE - EPS

CLASS 5 SWITCHPOTS CHANNEL BANK

BLC "A" BLC "B"

IP GigE - EPS

BLC "A" BLC "B"ROUTER ROUTER



Configuring Synchronous CES

Configuring Synchronous CESThis section contains the following instructions:

Network Clocking in a Synchronous CES Network on page 499

Configuring NSP on a Synchronous CES Network on page 503

Configuring T1 Interfaces in a Synchronous CES Network on page 504

Network Clocking in a Synchronous CES NetworkWhen a BLC is configured for Synchronous CES, the timing of each T1 is synchronous to the BLC network clock. There is a single timing domain per blade.

Figure 24-4 demonstrates how NSP clocking is configured for BLCs in a Synchronous CES network.

BLC “A” is configured to transmit clocking information on a specific NSP broadcast group, a number between one and nine. BLC “B” is configured to receive clocking information on the same broadcast group.

A T1 (serial) interface on BLC “A” is configured as a primary source for clocking and another is optionally set as a secondary source. BLC “A” transmits the clocking information to all BLCs in the network. BLC “B” is configured to listen to this clocking information. BLCs on the network that are not configured to listen to this clocking information will ignore it. The T1s on BLC “B” pass the clocking information onto the external equipment.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 24: Configuring Circuit Emulation Switching (CES)Configuring Synchronous CES

Figure 24-4: Synchronous CES Network Configuration

BLC "A"

CONFIGURED FOR NSPTRANSMIT MODE

CLOCK SOURCE FOR T1 INTERFACE ISCONFIGURED AS "LINE"

ONE T1 INTERFACE IS CONFIGURED ASTHE PRIMARY SOURCE FOR CLOCKING(SENDS CLOCKING INFO TO BLC "B" IN

NETWORK)

ANOTHER T1 INTERFACE ISCONFIGURED AS THE SECONDARY

SOURCE FOR CLOCKING

IP GigE - EPS

T1s T1s(CLOCKING INFO)BLC "B"

CONFIGURED FOR NSPRECEIVE MODE

CLOCK SOURCE FOR T1 INTERFACE ISCONFIGURED AS "INTERNAL"

CONFIGURED TO LISTEN TO "BLC A" ASA CLOCK SOURCE

(CLOCKINGINFO)

EXTERNALEQUIPMENT -

RECEIVECLOCK("LOOPTIMED")

EXTERNALEQUIPMENT -

SOURCECLOCK

("LOCALTIMED")

(CLOCKINGINFO)




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.

Figure 24-5: Synchronous CES Network Configuration Option 1

VPT 2

NSP TXDOMAIN 1

VPT 1

T1 #1 INFO

T1 #2 INFO

CLASS 5 SWITCH CHANNEL BANK

T1 #1

CLOCKING INFOFROM BLC TO

CHANNEL BANK

CLOCKING INFOFROM SWITCH

TO BLC T1

CHANNEL BANK

T1 #2


CHANNEL BANK

NSP RXDOMAIN 1

NSP RXDOMAIN 1



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.

Figure 24-6: Synchronous CES Network With Two Timing Domains

VPT 2

NSP TXDOMAIN 1

VPT 1

T1 #1 INFO

T1 #2 INFO

CLASS 5 SWITCH CHANNEL BANK

T1 #1


CHANNEL BANK


TO BLC T1 #1

T1 #2T1 #2

NSP TXDOMAIN 2

NSP RXDOMAIN 1

NSP RXDOMAIN 2

ROUTER #1 ROUTER #2




Configuring NSP on a Synchronous CES NetworkThis section describes how to configure NSP on a Synchronous CES network. Please refer to Figure 24-4 for an illustration of BLC “A” and BLC “B” in a Synchronous CES network configuration.

BLC A BLC B1. Enter Global Configuration Mode:


2. Configure a T1 interface as the primary source for clocking:Occam(config)# network-clock-select primary serial {interface number}

Configure another T1 interface on BLC “A” as the secondary source for clocking:Occam(config)# network-clock-select secondary serial {interface number}

2. Configure this BLC to use BLC “A” as the primary source for clocking:Occam(config)# network-clock-select primary nsp

3. Configure this BLC as a NSP transmitter. Specify a broadcast group domain number between one and thirty-two:Occam(config)# nsp mode tx {1-32}

For example, to configure this BLC to transmit NSP information on broadcast group 2, enter the command:Occam(config)# nsp mode tx 2

(Optional) Configure the NSP Time-To-Live (TTL) command, specifying a number of routed (not switched) hops. The default value is 64 hops:Occam(config)# nsp tx ttl {1-225}

(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 immediately. It is described more fully in Chapter 33, Differentiated Services (Diff-serv) on page 677:occam(config)# ip diffserv dscp protocol NSP {0-63}

3. Configure this BLC as a NSP receiver. Specify the same broadcast group domain number (between 1-32) that was config-ured on BLC ‘A”. Optionally, specify a secondary broadcast group number (in case of failure on the primary broadcast group):Occam(config)# nsp mode rx {same broadcast group number as configured for BLC “A”} {1-32}

For example, to configure this BLC to receive primary NSP information on broadcast group 2 and secondary NSP information on broadcast group 4, enter the command:Occam(config)# nsp mode rx 2 4

4. Exit Global Configuration Mode and save your configuration:Occam(config)# exitOccam# copy running-config startup-configBuilding configuration....



Configuring T1 Interfaces in a Synchronous CES Network


This section describes how to configure T1 interfaces on a Synchronous CES network. 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.

Figure 24-7 shows the an example of a CES network configuration with two BLCs. BLC “A” has the IP address 10.10.10.1 and BLC “B” has the IP address 10.10.10.2.

Figure 24-7: T1 Interfaces in CES Network Configuration

!

BLC "A"IP ADDRESS:10.10.10.1

IP GigE - EPS

(CLOCKING INFO)

DMS 100CLASS 5

SWITCHES CHANNEL BANKS

T1 INTERFACES8

76

5 43

21

31

T1 INTERFACES

42

5 687

BLC "B"IP ADDRESS:10.10.10.2

CLOCKING INFOON T1 LINES

CONFIGURED AS"PRIMARY" AND"SECONDARY"




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 B1. Enter Global Configuration Mode:Occam# configure terminalEnter 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, specifying a T1 interface port number. CES will be performed between the T1 interface configured on this BLC and the T1 interface configured on BLC “B” in Step 2 in the column to the right:Occam(config)# interface serial {T1-interface-number}

For example, to connect T1 interface “1” on BLC “A” to T1 interface 2 on BLC “B”, enter the command:Occam(config)# interface serial 1

4. Enter Serial Interface Configuration Mode, specifying a T1 interface port number.CES will be performed between the T1 interface configured on this BLC and the T1 interface configured on BLC “A” in Step 2 in the column to the left:Occam(config)# interface serial {T1-interface-number}

For example, to connect T1 interface “1” on BLC “A” to T1 interface 2 on BLC “B”, enter the command:Occam(config)# interface serial 2

5. Enable CES mode on the T1 interface:Occam(config-if-serial)# mode ces



6. Specify the IP address or hostname of BLC “B” and the T1 interface on BLC “B”. Sepa-rate the IP address or hostname and the T1 interface number with a space:Occam(config-if-serial)# ces connect-to {BLC “B” IP-address or hostname} {T1 interface number on BLC “B”}

For example, to connect to T1 line “2” on BLC “B” in Figure 24-7 enter the command:Occam(config-if-serial)# ces connect-to 10.10.10.2 2

The ces connect-to command cannot be entered if the T1 interface is already enabled.

6. Specify the IP address or hostname of BLC “A” and the T1 interface on BLC “A”. Separate the IP address or hostname and the T1 interface number with a space:Occam(config-if-serial)# ces connect-to {BLC “A” IP-address or hostname} {T1 interface number on BLC “A”}

For example, to connect to T1 line “1” on BLC “A” in Figure 24-7 enter the command: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 enabled.

7. Configure this T1 to receive clocking from the external equipment. This T1 must either be used for the BLC's Network clock, or be externally synchronized to the T1 the BLC is using for Network clock:Occam(config-if-serial)# service-module t1 clock source line

7. Configure this T1 as a source of clocking for the external equipment. The T1 will be synchronous to the Network clock option for the BLC:Occam(config-if-serial)# service-module t1 clock source 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}

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 dBCSU_0_H CSU 0 dB (high sens)CSU_7_L CSU -7.5 dB (low sens)CSU_7 CSU -7.5 dBCSU_7_H CSU -7.5 dB (high sens)CSU_15_L CSU -15 dB (low sens)CSU_15 CSU -15 dBCSU_15_H CSU -15 dB (high sens)CSU_22_L CSU -22 dB (low sens)CSU_22 CSU -22 dBCSU_22_H CSU -22 dB (high sens)

DSX1_133 DSX1 133 ftDSX1_266 DSX1 266 ft

DSX1_400 DSX1 400 ftDSX1_533 DSX1 533 ftDSX1_655 DSX1 655 ft

none CSU 0 dB (deprecated, use CSU_0)-7.5db CSU -7.5 dB (deprecated, use CSU_7)-15db CSU -15 dB (deprecated, use CSU_15)

Occam(config-if-serial)# service-module t1 lbo {LBO-format}

11. (Optional) Attach informational text to the Serial interface:Occam(config-if-serial)# info key informative-text

For example:Occam(config-if-serial)# info CES-mode A

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.

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}


BLC A BLC B



Configuring Asynchronous CES

Configuring Asynchronous CESThis section contains the following instructions:

Network Clocking in an Asynchronous CES Network on page 509

Configuring T1 Interfaces in an Asynchronous CES Network on page 510

Network Clocking in an Asynchronous CES NetworkAsynchronous CES does not rely on a system clock. In fact, the purpose of Asynchronous CES is to run a T1 line independent from the system’s clocks and other T1 lines. Also, Asynchronous CES does not use NSP to transport the clock across the network. The clock for each T1 is transported individually with the data.

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 2VPT 1

T1 #1 and #2 INFOTHROUGH EPS RING

T1 #1 CLOCKING INFOFROM BLC TO

CHANNEL BANK


TO BLC T1#2 T1 #2


CHANNEL BANK


TO BLC

T1#1

ROUTER #1 ROUTER #2


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 24: Configuring Circuit Emulation Switching (CES)Configuring Asynchronous CES

Configuring T1 Interfaces in an Asynchronous CES NetworkThis section describes how to configure T1 interfaces on an Asynchronous CES network. Figure 24-9 shows the an example of a CES network configuration with two BLCs. BLC “C” has the IP address 10.10.10.3 and BLC “D” has the IP address 10.10.10.4.


Figure 24-9: T1 Interfaces in an Asynchronous CES Network Configuration

!

BLC "C"

IP ADDRESS:123.45.67.8

IP GigE - EPS

T1#1

BLC "D"

IP ADDRESS:123.45.67.9

(CLOCKING INFO)

DMS 100CLASS 5 SWITCHES

CHANNEL BANKS

T1#2

T1#1

T1#2




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 B1. Enter Global Configuration Mode:


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, specifying a T1 interface port number. CES will be performed between the T1 interface configured on this BLC and the T1 interface configured on BLC “D” in Step 2 in the column to the right:Occam(config)# interface serial {T1-interface-number}

For example, to connect T1 interface “1” on BLC “C” to T1 interface 2 on BLC “D”, enter the command:Occam(config)# interface serial 1

To connect T1 interface “4” on BLC “C” to T1 interface 5 on BLC “D”, enter the command:Occam(config)# interface serial 4

4. Enter Serial Interface Configuration Mode, specifying a T1 interface port number.CES will be performed between the T1 interface configured on this BLC and the T1 interface configured on BLC “C” in Step 2 in the column to the left:Occam(config)# interface serial {T1-interface-number}

For example, to connect T1 interface “2” on BLC “D” to T1 interface 1 on BLC “C”, enter the command:Occam(config)# interface serial 2

To connect T1 interface “5” on BLC “D” to T1 interface 4 on BLC “C”, enter the command:Occam(config)# interface serial 5

5. Enable CES mode on the T1 interface:Occam(config-if-serial)# mode ces



5. Specify the IP address or hostname of BLC “D” and the T1 interface on BLC “D”. Sepa-rate the IP address or hostname and the T1 interface number with a space:Occam(config-if-serial)# ces connect-to {BLC “D” IP-address or hostname} {T1 interface number on BLC “D”}

Note: The ces connect-to command cannot be entered if the T1 interface is already enabled.

For example, to connect to T1 line “2” on BLC “D” in Figure 24-7, enter the command:Occam(config-if-serial)# ces connect-to 10.10.10.4

To connect to T1 line “5” on BLC “D” in Figure 24-7, enter the command:Occam(config-if-serial)# ces connect-to 10.10.10.4 5

5. Specify the IP address or hostname of BLC “C” and the T1 interface on BLC “C”. Sepa-rate the IP address or hostname and the T1 interface number with a space:Occam(config-if-serial)# ces connect-to {BLC “A” IP-address or hostname} {T1 interface number on BLC “C”}

Note: The ces connect-to command cannot be entered if the T1 interface is already enabled.

For example, to connect to T1 line “1” on BLC “C” in Figure 24-7, enter the command:Occam(config-if-serial)# ces connect-to 10.10.10.3 1

To connect to T1 line “4” on BLC “C” in Figure 24-7, enter the command:Occam(config-if-serial)# ces connect-to 10.10.10.3 4

6a. Typically this T1 should be set to “async-line” in order to receive clocking from the external equipment. The T1 local clock will be used for the local T1 transmitter and transmitted across the network to the remote:

Occam(config-if-serial)# service-module t1 clock source async-line

6b. When the clocking source is not deter-mined, the T1 on both BLCs (A and B) should be configured with the command service-module t1 clock source async-internal.

6. Configure this T1 to be the source of clock for the external equipment. The T1 will be generating this clock from the timing recovered from the remote T1:Occam(config-if-serial)# service-module t1 clock source async-internal

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}

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 dBCSU_0_H CSU 0 dB (high sens)CSU_7_L CSU -7.5 dB (low sens)CSU_7 CSU -7.5 dBCSU_7_H CSU -7.5 dB (high sens)CSU_15_L CSU -15 dB (low sens)CSU_15 CSU -15 dBCSU_15_H CSU -15 dB (high sens)CSU_22_L CSU -22 dB (low sens)CSU_22 CSU -22 dBCSU_22_H CSU -22 dB (high sens)

DSX1_133 DSX1 133 ftDSX1_266 DSX1 266 ftDSX1_400 DSX1 400 ftDSX1_533 DSX1 533 ftDSX1_655 DSX1 655 ft

none CSU 0 dB (deprecated, use CSU_0)-7.5db CSU -7.5 dB (deprecated, use CSU_7)-15db CSU -15 dB (deprecated, use CSU_15)

Occam(config-if-serial)# service-module t1 lbo {LBO-format}

9. (Optional) Attach informational text to the Serial interface:Occam(config-if-serial)# info key informative-text

For example:Occam(config-if-serial)# info CES-mode A

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>, '?', '!'.

10. Enable the T1 portOccam(config-if-serial)# no shutdown

11. Exit Serial Interface Configuration Mode and return to Global Configuration Mode:Occam(config-if-serial)# exit

12. Repeat steps 2 through 11 for each T1 interface you wish to configure for 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}


BLC A BLC B



Terminating a CES Connection

Terminating a CES ConnectionUse the command no ces connect-to in Serial Interface Mode to break a CES connection on a T1 line. For example, to break a CES connection on T1 interface 1, enter the commands:Occam# interface serial 1Occam(config-if-serial)# shutdown Occam(config-if-serial)# no ces connect-to

Viewing Your CES ConfigurationThe command show ces summary shows the CES connections on a BLC. Please see page 519 for an explanation of the command output.

The command clear ces clears the error counts and payload packet counts.

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.

Sample Output for Synchronous CES ConfigurationsThe following examples show sample command outputs for “BLC A” and “BLC B” configured for Sycnronous CES (as shown in Figure 24-7). The command fields are explained in Table 24-3 on page 519.

Table 24-1: T1 Line CES Connections

Sample Output for “BLC A”:

BLC A BLC BT1 #1 T1 #2T1 #2 T1 #1T1 #3 T1 #5T1 #4 T1 #3T1 #5 T1 #4

BLC_A# show ces summary

CES Connection States:

port ds0s mode state jitter Remote: port ds0 IP

1 1 -24 SYNC CES CONNECTED CLEAR 2 1 10.10.10.2






port bad lost old overflow rtp same too_far underflow


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 24: Configuring Circuit Emulation Switching (CES)Viewing Your CES Configuration

CES Payload Packetsport Rx Tx1 1001246891 10012457972 1001242816 10012435473 1001243047 10012437724 1001253126 1001243707BLC_A#

Sample Output for “BLC B”:

CES Payload Packetsport Rx Tx1 998424284 9983982002 998422112 9983922993 998422216 9983923734 998422313 998402512

BLC_B#

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# show ces summary


port ds0s mode state jitter Remote: port ds0 IP

1 1-24 SYNC CES CONNECTED CLEAR 2 1 10.10.10.1






port bad lost old overflow rtp same too_far underflow

1 0 0 0 0 0 0 0 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 0 0 0 0



Viewing Your CES Configuration

Sample Output for Asynchronous CES ConfigurationsThe following examples show sample command outputs for “BLC C” and “BLC D” configured for Asycnronous CES (as shown in Figure 24-9). In this sample output the T1 lines are connected as shown in the following table:

Table 24-2: T1 Line CES Connections

Sample Output for “BLC C”:

CES Payload PacketsPort Tx Rx1 164580908 1645809092 164619000 1645804933 164581389 164581389BLC-C#

Sample Output for “BLC D”:

CES Payload PacketsPort Tx Rx

BLC C BLC DT1 #1 T1 #2T1 #2 T1 #1T1 #3 T1 #3

BLC-C# show ces summaryCES Connection States:port ds0s mode state jitter Remote: port ds0 IP1 1-24 ASYNC CES CONNECTED CLEAR 2 1 10.10.10.42 1-24 ASYNC CES CONNECTED CLEAR 1 1 10.10.10.43 1-24 ASYNC CES CONNECTED CLEAR 3 1 10.10.10.4

CES Connection States:port bad lost old overflow rtp same too_far underflow1 0 0 0 0 0 0 0 02 0 0 0 0 0 0 0 03 0 0 0 0 0 0 0 0

BLC-D# show ces summaryCES Connection States:port ds0s mode state jitter Remote: port ds0 IP1 1-24 ASYNC CES CONNECTED CLEAR 2 1 10.10.10.32 1-24 ASYNC CES CONNECTED CLEAR 1 1 10.10.10.33 1-24 ASYNC CES CONNECTED CLEAR 3 1 10.10.10.3

CES Connection States:port bad lost old overflow rtp same too_far underflow1 0 0 0 0 0 0 0 02 0 0 0 0 0 0 0 03 0 0 0 0 0 0 0 0



1 164580908 1645809092 164619000 1645804933 164581389 164581389BLC-D#



Viewing Your CES Configuration

Explanation of Output For “show ces” Command

Table 24-3: “show ces summary” Field Descriptions

Field Description

state IDLE - Startup state that will not be seen unless the DSP core is dead.

CALLING- Heard from the remote exchanging parameters.

CONNECTED- Link is up.

INTERRUPTED- The remote end has stopped responding.

INCOMPATIBLE- The remote end has incompat-ible configurations.

jitter CLEAR - No current jitter problems.

ERRORS- Packet errors have been detected.

OVERFLOWING- Jitter buffer has recently overflowed.

UNDERFLOWING- Jitter buffer has recently underflowed.

bad Number of packets with a bad header.

lost Number of lost packets.

old A packet with a very old sequence number was received.

overflow The number of times the jitter buffer overflowed.

rtp The number of missing RTP sequences. (i.e. # dropped packets.)

same The number of packets with the same RTP sequence. (i.e. # duplicate packets).



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.

Field Description


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 25: Configuring MGCP/VoIP

Introduction

Chapter 25Configuring MGCP/VoIP

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521Configuring a Voice Profile For Delivering POTS Over VoIP . . . . . . . . . . . . . . . . . . 523Configuring a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531Configuring MGCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534Blocking New Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540Displaying Voice Port, Profile and MGCP/VoIP Configuration Information . . . . . 541

IntroductionThis 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.

Configuration Steps Described In This ChapterThis chapter contains configuration steps that show:

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).


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 25: Configuring MGCP/VoIPIntroduction

How to configure MGCP signaling on the BLC (page 534)

How to display configuration information about the following parameters (page 541):

voice interface

voice interface profile

MGCP/VoIP configuration information



Configuring a Voice Profile For Delivering POTS Over VoIP


Before you configure a voice interface you should first create a voice-profile to attach to it. A voice-profile includes parameters such as the codec, input gain, and RTP signaling mode.

If an existing profile is modified, that change takes effect on every voice interface linked to that profile. To change a single interface or a subset of interfaces, copy the profile, change the desired parameters, and then assign the new profile to the desired interfaces. The same profile can be attached to multiple interfaces, but one interface cannot have more than one profile attached to it.

You may configure virtually an unlimited number of voice interface profiles Voice profiles are maintained in memory so that the profiles can be assigned to voice interfaces when needed.

Default Voice Port ProfileAll interfaces have attached profiles. If you do not assign a profile to an interface, the system, by default, assigns the profile named "default" to that interface. The profile named “default” is for POTS-VoIP, a voice profile that delivers POTS over VoIP. This profile can be changed but not deleted. It is recommended that you rename the default profile if you change it. The initial values for this profile are shown below:profile: default Profile type: pots-voip 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: pots Rtp Signaling Type: nuera2833 Echo cancel: enable Echo tail length: 32 milliseconds Echo Tone Disabler: G.165 Connection mode: pots Idle Channel Suppression: enable Receive Level: -3.0 dB Transmit Level: -3.0 dB Codecs: g711ulaw Codec Options: g711ulaw: Jitter Delay: 20ms Packetization: 10ms g726-32k-pt2: Jitter Delay: 40ms Packetization: 20ms g726-32k:


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 25: Configuring MGCP/VoIPConfiguring a Voice Profile For Delivering POTS Over VoIP

Jitter Delay: 40ms Packetization: 20msModem Codec Bypass: enable




Voice Port Profile Configuration Steps

Note: This section is optional. You may wish to use the default voice profile (as shown on page 523). You may also modify the default profile, but it is recommended that you create a new 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}

the prompt changes to:Occam(config-profile)<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

and the prompt would change to:Occam(config-profile)mgcp_new#

Use the command no voice-profile <profileName> to delete a profile by name.

3 Configure a profile by using the commands shown below in Table 25-1.

Table 25-1: Voice Port Profile Configuration Commands


Input Gain Value:Set the decimal amount of input gain. The parameters are -12 dB to +12dB in one dB increments. The default is 0 dB.


Output Gain Value:Sets the local adjustment, in decibels.Set the decimal amount of output gain (attenuation). The parameters are -12 dB to +12dB in one dB increments. The default is 0 dB.




Forward Disconnect:Specifies in milliseconds the amount of time the battery is removed to alert the remote end disconnect. At the end of a call, when the far end hangs up, the forward discon-nect signal is applied to the line to inform the local user that the remote has discon-nected. The default value is 900 milliseconds


Fax Delay - Specifies fax jitter buffer delay in five msec increments


Fax CNG Detector - Enables or disables the fax CNG (CalliNG) tones detector. This feature is disabled by factory default.


Fax CNG Timer - Specifies the number of seconds the CNG detector is enabled at the start of a call.The factory default is 0 seconds.

occam(config-profile)profile-name# fax-cng-detect {0-120}

Signaling Type(not configurable)

occam(config-profile)profile-name# sig-type pots

RTP Signaling Type:Select Real-time Transport Protocol (RTP) Signaling Mode as Nuera 2833 or “none”. The default is Nuera 2833.

occam(config-profile)profile-name# rtp-sig-type {nuera2833, none}





Echo Tone Disabler.Configures the voice port with one of the following parameters: disable - Ignore 2100 Hz tone


G.165 - Bypass echo cancellation on 2100 Hz tone with phase reversal. This is the factory default.





Connection Mode:The connection mode is POTS- MGCP by factory default and is not configurable.

N/A

Idle Channel Suppression: This feature is enabled by factory default and is not configurable.

N/A

Receive level:Set the receive level on a voice-port in deci-bels. The default value is -3.0 dB.


Transmit Level:Sets the transmit level on a voice-port in decibels. The default value is -3.0 dB

occam(config-profile)profile-name# transmit-level {-15 db to +10 db.}



Codec-list:

Preferred coder-decoders (codecs) used during call compression. The order entered determines the priority order of the codecs.



g726-32k: ADPCM 32k dynamic payload type. This codec is described in RFC 3551. This algorithm compresses voice from 64 kbps to 32 kbps. It supports dynamic packet types and may be used with the Coppercom softswitch.The default values for this codec are:Jitter Delay: 40msPacketization: 20ms

Note: NOTE: In this release you may only configure the g721 OR g726-32k codec on a profile because the g721 codec supports fixed packet type 2 and the g726-32k codec supports dynamic packet types. You may not configure both. The g711ulaw will always be on the codec list, even if it is not entered.Upon detection of a fax CED or CNG tone the algorithm will automatically switch from g.726/g.721 to g.711.Three way calling is not supported with the g721 and g726 codecs unless the softswitch does the mixing.






5 Repeat steps 2 through 13 for each profile you wish to configure



Codec-Options:

Configures the jitter delay and packetiza-tion options for codecs.


Jitter Delay:



Packetization:

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:Configures the modem-codec-bypass as:disabled - No codec bypassenabled - Modem codec bypass functions are configured to follow the settings of the echo-tone-disabler command.

If the echo-tone-disabler command is configured with the parameter:disable: the modem codec bypass feature is also configured to ignore a 2100 Hz answer tone when it is detected.G.164: the modem codec bypass feature is also configured to bypass echo cancellation on 2100 Hz tone detection. This option does not look for phase reversal on the tone. G.165: the modem codec bypass feature is also configured to bypass echo cancellation on 2100 Hz tone only when phase reversal is detected on it.




Building configuration....

7 Continue on to the section Configuring a Voice Port.



Configuring a Voice Port

Configuring a Voice PortThis section describes how to enable a voice port and attach a voice port profile to it.


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

4 Select a profile by name to attach to the voice interface:Occam(config-voice)# attach-profile profile-name

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

7 Exit to Global Configuration Mode:Occam(config-voice)# exit

8 Repeat steps 2 through 6 for each interface numbered 1 through 48 to which you wish to attach a profile.



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 25: Configuring MGCP/VoIPConfiguring a Voice Port

Configuring Unbalanced Ringing on a Voice Port

Unbalanced Ringing provides a ringing signal compatible with most applications where the POTS subscriber line traverses a remote DLC. Unbalanced Ringing is disabled by default.


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}

3 Enable unbalanced ringing on the voice port:Occam(config-voice)# unbalanced-ring

Use the no form of the command to disable this feature:Occam(config-voice)# no unbalanced-ring



Configuring Maximum Balanced Ringing On a Voice PortNormal balanced ring is approximately 80V rms Tip to Ring. Maximum balanced ring is approximately 108V rms Tip to Ring. To achieve this the driver is pushed into saturation, thus creating a square wave. Normal ringing is a sine wave.

Square wave ringing does not meet the TR-57 specification. Therefore the max-balanced-ring command should not be used unless the normal balanced ring is not sufficient for the application (e.g. DLC or long loop). This feature is disabled by default.



3 Enable unbalanced ringing on the voice port:Occam(config-voice)# max-balanced-ring




Use the no form of the command to disable this feature:Occam(config-voice)# no max-balanced-ring


5 Save your configuration:Occam# copy running-config startup-config


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 25: Configuring MGCP/VoIPConfiguring MGCP

Configuring MGCPNote: When MGCP is referred to in the configuration steps below, Network-based Call Signaling (NCS) is understood to also apply, except where otherwise noted.

Note: This configuration uses a BLC 6640-01 as a call agent.

1 From Global Configuration Mode:Occam# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Occam(config)#

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]

4 (Optional) Configure MGCP to run on BVI 1 or BVI 2. Please see Chapter 8, Configuring Multihoming on page 153 for more information about how to configure multihoming:occam(config)# mgcp interface bvi {1,2}

5 (Optional) Configure RTP to run on BVI 1 or BVI 2:occam(config)# rtp interface bvi {1,2}

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}

8 Exit Global Configuration Mode and save your configuration:



Configuring MGCP

occam(config)# exit


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}

10 Return to Global Configuration Mode:Occam# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Occam(config)#

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.

Table 25-2: MGCP Configuration Commands

Command Function and Command Setting for Occam Only or Softswitch Environment

mgcp endpoint-prefix name Selects the endpoint prefix name. The “no” version of this command returns it to the default value.

Default: The default endpoint prefix name is “phone”

Occam Only Environment: No need to change default setting.Softswitch Environment (managed by softswitch): Set this command according to your networking preference.

mgcp max-waiting-delay {0-600000}no mgcp max-waiting-delay

Configures the maximum waiting delay in milli-seconds. This value will be used in an Restart in Progress (RSIP) message as restart instructions for the call agent. The “no” version of this command returns it to the default value.

Default:3000 milliseconds

Occam Only Environment: Set this command according to your networking preference.Softswitch Environment: Set this command according to your networking preference.



mgcp option explicit-detectionno mgcp option explicit-detection

Enables or disables the explicit detection feature. This feature checks on endpoint hook-status request(s) coming from the call-agent to the current endpoint hook-status. If they are the same, the glare is detected and the request from the call-agent is returned with an error. This configuration is made optional to enable interop-erability with third-party call-agents who do not have this feature implemented.This command is not required with the BLC or other call agents that do not require detection of explicit hookstates.

Default: Disabled

Occam Only Environment: This command should remain disabled.Softswitch Environment: This command should be enabled.

mgcp option occam-single-contextno mgcp option occam-single-context

Allows or disallows only one RTP session to be set up by the call-agent on an endpoint when the connection between a BLC 6150-01, BLC 6151-01 or BLC 6252-03 is managed by a BLC 6640.

Default: Disabled

Occam Only Environment (managed by BLC 6640): This command should be enabled.Softswitch Environment: This command should remain disabled.



Configuring MGCP

mgcp option passthruno mgcp option passthru

Passes through flashhook events to call agent without acting on them, The “no” version of this command disables this feature.

Default: DisabledNote: 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.

Occam Only Environment: This command should remain disabled.Softswitch Environment: This command should be enabled.

mgcp option securityno mgcp option security

Enable or disable security within the Media Gateway. If security is enabled, the Media Gateway will only communicate with call agents that are configured.

Default: Enabled

Note: If multiple call agents try to control the BLC simultaneously, calls may fail on all interfaces. MGCP security is ENABLED by default. Disable it at your own risk. (not recommended to change for Occam only or Softswitch environments)

mgcp packetization-period {10 | 20} no mgcp packetization-period

This command configures the default packetiza-tion period of the VoIP (RTP) packets in milli-seconds, if the Softswitch (TGW or 3rd party CA) do not explicitly request this via MGCP protocol call-control messages. The purpose of this command is to provide user configuration of this value in environments where the softswitch will not request this info in the call-control messages and the default of 10ms is not suitable for their applications.

Default: 10 ms. for Occam only and softswitch environments.



mgcp persistent-event flashhookno mgcp persistent-event flashhook

Enables a flashhook to be treated as a persistent event. A persistent events is reported to the call agent even if the call agent has not requested to be notified when it occurs.

Default: Disabled (Enabled if the MGCP profile is set to NCS by the mgcp profile command)

Occam Only Environment: This command should be disabled Softswitch Environment: This command should be enabled.

mgcp persistent-event offhookno mgcp persistent-event offhook

Enables offhook to be treated as a persistent event.


Occam Only Environment: This command should be disabledSoftswitch Environment: This command should be enabled.

mgcp persistent-event onhookno mgcp persistent-event onhook

Enables onhook to be treated as a persistent event.


Occam Only Environment: This command should be disabledSoftswitch Environment: This command should be enabled

mgcp profile mgcp [ip] Specify the operating profile for the Media Gateway as MGCP (factory default). You may chose the option “ip” to set up the Media Gateway to use the Media Gateway IP address as the domain name in the endpoint naming instead of its FQDN.Default: MGCP and using FQDN.

Occam Only Environment: MGCP, using FQDN.Softswitch Environment: Dependent upon Soft-switch configuration, but the recommended setting is NCS using IP address.



Configuring MGCP

12 Initiate MGCP. Do not change the local UDP interface parameter from it’s default value of 2427:

Occam(config)# mgcp



mgcp profile ncsno mgcp profile

Specify the operating profile for the Media Gateway as Network-based Call Signaling (NCS). The “no” version of this command returns the profile to the default value of MGCPDefault: Disabled (MGCP is default)

Occam Only Environment: Not neededSoftswitch Environment: Dependent upon Soft-switch configuration, but the recommended setting is NCS using IP address

mgcp restart-delay {1-600}no mgcp restart-delay

Specifies the delay value sent in the Restart in Progress (RSIP) graceful tear down method in seconds. The delay value for RSIP graceful tear down is sent after the no mgcp command is entered. The “no” version of this command returns it to the default value.

Default: 1 second (not recommended to change for Occam only or Softswitch environments)

mgcp retry-timeout {4-50}no mgcp retry-timeout

Specifies the timeout waiting for retry responses to a request. The “no” version of this command returns it to the default value.

Default: 30 seconds (not recommended to change for Occam only or Softswitch environments).


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 25: Configuring MGCP/VoIPBlocking New Calls

Blocking New CallsUse the mgcp block-newcalls command from Global Configuration Mode to remove an endpoint from service gracefully. This means that new calls are blocked while existing calls are maintained until they are completed. This command is disabled by default.

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



Displaying Voice Port, Profile and MGCP/VoIP Configuration Information

Displaying Voice Port, Profile and MGCP/VoIP Configuration Information

The following commands may be used to view your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide.

Viewing Information About Voice Ports

show voice: displays DSP status and voice port configuration.

show voice dsp: displays the current status of all digital signal processor (DSP) voice channels.

show voice port {port-number}: use this command to display configuration information about a specific voice port.

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.

Viewing Information About Voice Profiles

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.

Viewing Information About MGCP

show mgcp: use this command to display MGCP configuration information.

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 25: Configuring MGCP/VoIPDisplaying Voice Port, Profile and MGCP/VoIP Configuration Information


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246

Introduction

Chapter 26Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543Configuring a T1 Interface for Cross-Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544Configuring Cross-Connect Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546Configuring Cross-Connect Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546Attaching a Profile to a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559Displaying Voice Port and Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560

IntroductionThe cross- connect modes available for configuration on the BLC 6150-01 and BLC 6246 are:

Cross-Connect Data Mode: This mode is used by DS0s carrying Dataphone Digital Service (DDS) traffic, D-channel in CCS circuit (e.g. PRI between a PBX and SW/DAC) and TMC, EOC channels when carrying a GR303 link as DS1 - IP - DS1 through a cross connect IG.

Cross-Connect Voice Channel Associated Signaling (CAS) Mode: This mode is used by DS0s carrying voice traffic on CAS circuits (all 24 DS0s). It is used for such applications as TR-08, Foreign Exchange Station (FXS), Foreign Exchange Office (FXO), and Ear and Mouth (E&M).

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.

Cross-Connect Voice Coin Mode: This mode is used to configure a cross-connection between a GR-303 coin Call Reference Value (CRV) and a TR-08 channel bank coin card.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246Configuring a T1 Interface for Cross-Connect

Configuring a T1 Interface for Cross-ConnectNote: The serial interface configuration on the BLC 6150-01 and BLC 6246 must match the serial interface configuration on the application to which it is connected. Both configurations must have matching parameters (i.e., facility, facility data link (fdl) standards, linecoding).



2 Enter Serial Interface Configuration Mode, specifying the T1 interface:occam(config)# interface serial {1-4}

3 Enable channelized mode:occam(config-if-serial)# mode channelized

4 Select a facility data link (fdl) standard for a T1 data link:

Enter “ansi” to select ANSI T1.403.

Enter “att” to select AT&T TR54016

Enter “both” to select both ANSI T1.403 and AT&T TR54016

Enter “slc96rt” to select SLC96 Remote Terminal

Enter the command no service module t1 fdl disables the fdl optionoccam(config-if-serial)# service-module t1 fdl {ansi | att | both | slc96rt}

5 Specify the framing format.

Enter “esf” to select Extended Super Frame (factory default)

Enter “sf” to select Super Frame

Enter “slc96” to select SLC-96 formatoccam(config-if-serial)# service-module t1 framing {esf | sf |slc96}

6 Enable the T1 port:occam(config-if-serial)# no shutdown

!



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}

8 (Optional) Enable 16 or 32 bit Cyclic Redundancy Checks (CRC) for error checking. This command is optional if you select 16-bit CRC, the factory default:occam(config-if-serial)# crc {16 |32}

9 (Optional) Configure the line build-out. There is no default:occam(config-if-serial)# service-module t1 lbo {-15 db | -7.5 db | none}

10 (Optional) Enable the BLC 6150-01 to generate and detect remote (yellow) alarms:occam(config-if-serial)# service-module t1 remote-alarm-enable

11 (Optional) Configure the T1 to enter loopback mode when it receives a loopback code on the line. The default is full and payload loopbacks with standard-loopup codes:occam(config-if-serial)# service-module t1 remote-loopback {full| payload}

12 (Optional) Attach informational text to the Serial interface:Occam(config-if-serial)# info key informative-text

For example:Occam(config-if-serial)# info cross-connect-mode single-party-voice-cross-connect-mode

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>, '?', '!'.

13 Enable the T1 port:occam(config-if-serial)# no shutdown

14 Exit Serial Interface Configuration Mode and return to Global Configuration Mode:occam(config-if-serial)# exit

15 Exit Serial Interface Configuration Mode and return to Global Configuration Mode:occam(config-if-serial)# exit




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246Configuring Cross-Connect Profiles

Configuring Cross-Connect ProfilesTo configure an voice port you must attach a Cross-Connect profile to it. A profile includes parameters such as the codec, signalling type, and RTP signaling mode.

When a profile is modified, the change affects every voice port linked to that profile. To change a single voice you must copy the profile, change the desired parameters, and then assign the new profile to the desired voice. There can be one profile for many voice ports, but one voice port cannot have more than one profile.

You may create as many profiles as needed. Profiles are maintained in memory and can be modified and reassigned.

Default Cross-Connect ProfilesWhen you enter a Cross-Connect Profile Configuration Mode you have access to a profile for that mode. This section shows the initial values for profiles in the various cross-connect profile configuration modes.

The Cross-Connect Data Default Profile is shown on page 547

The Cross-Connect Voice Profile is shown on page 548

The Cross-Connect Voice CAS Profile is shown on page 549

The Cross-Connect Voice Non-CAS Profile is shown on page 550

The DS0 Cross-Connect Voice Single-Party Profile is shown on page 551

The DS0 Cross-Connect Voice Coin Profile is shown on page 552



Configuring Cross-Connect Profiles

Cross-Connect Data Default Profile

The initial values for the profile in Cross-Connect Data Profile Configuration Mode are shown below:Profile type: cross-connect-data 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: clear-channel Rtp Signaling Type: none Echo cancel: disable Echo tail length: 32 milliseconds Echo Tone Disabler: G.165 Connection mode: t1-rtp Idle Channel Suppression: disable Codecs: g711bypass Codec Options: g711ulaw: Jitter Delay: 20ms Packetization: 10ms g726-32k-pt2: Jitter Delay: 40ms Packetization: 20ms g726-32k: Jitter Delay: 40ms Packetization: 20ms g726-32k: Jitter Delay: 40ms Packetization: 20ms Modem Codec Bypass: enable



Cross-Connect Voice Profile

The initial values for the profile in Cross-Connect Voice Profile Configuration Mode are shown below:Profile type: cross-connect-voice 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: transparent Rtp Signaling Type: transparent2833 Echo cancel: enable Echo tail length: 32 milliseconds Echo Tone Disabler: G.165 Connection mode: t1-rtp Idle Channel Suppression: disable Codecs: g711ulaw Codec Options: 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




Cross-Connect Voice CAS Profile

The initial values for the profile in Cross-Connect Voice CAS Profile Configuration Mode are shown below:Profile type: cross-connect-voice-cas 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: transparent Rtp Signaling Type: transparent2833 Echo cancel: enable Echo tail length: 32 milliseconds Echo Tone Disabler: G.165 Connection mode: t1-rtp Idle Channel Suppression: disable Codecs: g711ulaw Codec Options: 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



Cross-Connect Voice Non-CAS Profile

The initial values for the profile in Cross-Connect Voice Non-CAS Profile Configuration Mode are shown below:Profile type: cross-connect-voice-non-cas 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: clear-channel Rtp Signaling Type: none Echo cancel: enable Echo tail length: 32 milliseconds Echo Tone Disabler: G.165 Connection mode: t1-rtp Idle Channel Suppression: disable Codecs: g711ulaw Codec Options: 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




DS0 Cross-Connect Voice Single-Party Profile

The initial values for the profile in DS0 Cross-Connect Voice Single-Party Configuration Mode are shown below:Profile type: cross-connect-voice-single-party 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: slc96co-sp Rtp Signaling Type: nuera2833 Echo cancel: enable Echo tail length: 32 milliseconds Echo Tone Disabler: G.165 Connection mode: t1-rtp Idle Channel Suppression: disable Codecs: g711ulaw Codec Options: 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



DS0 Cross-Connect Voice Coin Profile

The initial values for the profile in DS0 Cross-Connect Voice Coin Profile Configuration Mode are shown below:Profile type: cross-connect-voice-coin 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: slc96co-coin Rtp Signaling Type: nuera2833 Echo cancel: enable Echo tail length: 32 milliseconds Echo Tone Disabler: G.165 Connection mode: t1-rtp Idle Channel Suppression: disable Codecs: g711ulaw Codec Options: 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




Configuring a Cross-Connect ProfileUse the following configuration steps to configure a cross-connect profile.

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.


2 Enter a cross-connect profile configuration mode and configure a cross-connect profile. The prompt will change to occam(configprofile)< profileName>#.

The cross-connect profile mode options are:

Cross-Connect Data Mode:occam(config)# voice-profile cross-connect data {profile-name}

Cross-Connect Voice Mode:occam(config)# voice-profile cross-connect voice {profile-name}

Cross-Connect Voice Channel Associated Signaling (CAS) Mode:occam(config)# voice-profile cross-connect voice cas {profile-name}

Cross-Connect Voice Non-CAS Mode:occam(config)# voice-profile cross-connect voice non-cas {profile-name}

Cross-Connect Voice Single-Party Mode:occam(config)# voice-profile cross-connect voice single-party {profile-name}

Cross-Connect Voice Coin Mode:occam(config)# voice-profile cross-connect coin {profile-name}

For example, if a cross-connect data profile named “ds0_data_new” was being configured the command would be:occam(config)# voice-profile cross-connect data ds0_data_new

and the prompt would change to:occam(config-profile)ds0_data_new#



3 Configure the Cross Connect Profile Parameters, referring to Tables 26-1 for information about the profile’s default values.

4 Exit Cross-Connect Profile Configuration Mode:occam(config-profile)<profileName># exit



6 Go on to the following section Attaching a Profile to a Voice Port on page 559.

Commands to Configure Cross-Connect Profiles

Table 26-1: Cross-Connect Profile Configuration Commands


Input Gain:Sets the decibel amount of input gain to insert at the receiver side of the interface. The default for all cross-connect profiles is 0 decimals.


Output Gain Value: Sets the decibel amount of output gain (attenuation) to insert at the transmit side of the interface. The default for all cross-connect profiles is 0 decimals.


Forward Disconnect:Sets the time in milliseconds to alert the remote end disconnect after a battery is removed. The default for all cross-connect profiles is 900 milliseconds.


Fax Delay: Specifies fax jitter buffer delay in five msec increments. The default for all cross-connect profiles is 0 milliseconds.


Fax CNG Detector: Enables or disables the fax CNG (CalliNG) tones detector. The fax CNG (CalliNG) tones detector is disabled by default on all cross-connect profiles.





Fax CNG Timer - Specifies the number of seconds the CNG detector is enabled at the start of a call. The default for all cross-connect profiles is 0 seconds.


Signaling Type:Selects the signaling mode. The options are:

clear-channel: Utilize clear-channel mode. This the factory default setting for the Data Cross-Connect Data and Cross-Connect Voice Non-CAS Profiles.

transparent: Utilize transparent signaling mode. This is the factory default setting for the Cross-Connect Voice and the Cross-Connect Voice CAS profiles.

slc96co-sp: Utilize SLC-96 central office single party signaling mode. This is the factory default setting for the DS0 Cross-Connect Voice Single-Party Profile.

slc96co-coin: Utilize SLC-96 central office coin signaling mode. This is the factory default setting for the DS0 Cross-Connect Voice Coin Profile.

Cross-Connect Data Profile: occam(config-profile)profile-name# sig-type clear-channel

(Not configurable)

Cross-Connect Voice Profile,Cross-Connect Voice CAS Profile,Cross-Connect Voice Non-CAS Profile,Cross-Connect Voice Single-Party Profile,Cross-Connect Voice Coin Profile: occam(config-profile)profile-name# sig-type {clear-channel, slc96co-coin, slc96co-sp, transparent}

RTP Signaling Type:Selects the Real-time Transport Protocol (RTP) Signaling Mode

none: Utilize no RTP signaling. This the factory default setting for the Data Cross-Connect and Cross-Connect Voice Non-CAS Profiles.

nuera2833: Utilize Nuera RFC2833 RTP mode. This is the factory default setting for the Cross-Connect Voice Single-Party and the Cross-Connect Voice Coin 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.

Cross-Connect Data Profile: occam(config-profile)profile-name# rtp-sig-type none

(Not configurable)

Cross-Connect Voice Profile,Cross-Connect Voice CAS Profile,Cross-Connect Voice Non-CAS Profile,Cross-Connect Voice Single-Party Profile,Cross-Connect Voice Coin Profile: occam(config-profile)profile-name# rtp-sig-type {none, nuera2833, transparent2833}



Echo Cancel: Cancels voice echo during a call.

mgcp - MGCP decides if voice echo is to be enabled or not (on the BLC).

enable- enable ECAN locally, ignore MGCP setting. This is the setting for the Cross-Connect Voice profiles.

disable - disable ECAN locally, ignore MGCP setting. This is the setting for the Cross-Connect Data profile.

occam(config-profile)profile-name# echo-cancel {mgcp,enable, disable}

Echo Tail Length:Sets the echo tail-length in milliseconds. Echo tail length (or echo path delay) is the amount of delay in time over which echo is controlled. The default for all cross-connect profiles is 32 milliseconds.


Echo Tone DisablerThe echo-tone-disabler command may be configured to disable the echo canceller feature when a 2100 Hz tone is detected. The tone is used in both fax and modem protocols and it may or may not have phase reversal. Phase reversal is used to disable echo cancellation.

disable - Ignore 2100 Hz tone


G.165 - Bypass echo cancellation on 2100 Hz tone with phase reversal. This is the factory default for all cross-connect profiles.


Connection Mode (not configurable) N/A

Idle Channel Suppression (not configurable) N/A

Codec: Set the list of preferred codecs used, space separated in order or priority:g711ulaw: ulaw PCMg726-32k-pt2: ADPCM 32k payload type 2g726-32k-ADPCM 32k RFC 3551

occam(config-profile)profile-name# codec-list {g711ulaw, g726-32k-pt2, g726-32k}




Jitter Delay - Specifies jitter buffer delay in 5 msec increments.

After you select a codec to configure by 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




Packetization - select the packetization period value in milli-seconds.

After you select a codec to configure by entering the command codec-option you may configure the jitter delay value.

occam(config-profile)profile-name# codec-option {codec-name}


occam(config-voice-codec)# exit




enabled - Configures the profile to follow the settings of the echo-tone-disabler command. By factory default all cross-connect profiles have the modem codec--bypass setting enabled.

If the echo-tone-disabler command is configured with the parameter:


G.164: the modem codec bypass feature is also configured to bypass echo cancel-lation on 2100 Hz tone detection. This option does not look for phase reversal on the tone.

G.165: the modem codec bypass feature is also configured to bypass echo cancel-lation on 2100 Hz tone only when phase reversal is detected on it.




Attaching a Profile to a Voice Port

Attaching a Profile to a Voice Port1 Enter Global Configuration mode:

occam# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Occam(config)#

2 Enter Voice Port Configuration Mode and specify a voice port number between 49 and 144 to configure:occam(config)# voice-port {49-144}

3 Select a profile by name to attach to the voice port:occam(config-voice)# attach-profile profile-name

For example, if you had created a subscriber profile called “ds0_data_new” earlier, the command would be:occam(config-voice)# attach-profile ds0_data_new

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

6 (Optional) Attach informational text to the voice port:Occam(config-voice)# info key informative-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>, '?', '!'.

7 Exit to Global Configuration Mode:occam(config-profile)# exit

8 Repeat steps 2 through 6 for each port to which you wish to attach a cross-connect profile.




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 26: Configuring Cross-Connect Modes on the BLC 6150-01 and the BLC 6246Displaying Voice Port and Profile Information

Displaying Voice Port and Profile Information The following commands may be used to view your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide.

show voice port {port-number}: use this command to display configuration about a specific voice port

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.



show voice list-of-profiles: use this command to display the names of existing voice profiles



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01

Introduction

Chapter 270Configuring DS0 Cross Connect Modes on the BLC 6640-01

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561Configuring a T1 Interface for Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563Configuring Network Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565Configuring a Cross-Connect Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 566Configuring an Interface Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578

IntroductionThis 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.


DS0 Data Cross-Connect ModeThis mode is used by DS0s carrying special circuit traffic.

Note: The configuration for any single DS0 must match on another BLC and the BLC 6640-01. However, DS0s on a T1 will not necessarily be assigned to the same profile.

Voice Cross-Connect ModeThis mode is used by DS0s carrying voice traffic on CAS circuits (all 24 DS0s). It is used for such applications as TR-08, Foreign Exchange Station (FXS), Foreign Exchange Office (FXO), and Ear and Mouth (E&M).

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01Introduction

Clear Channel Voice Cross-ConnectThis mode is used to configure clear channel voice cross connect on the BLC 6640 and BLC 6640-01. This configuration configures a voice channel on a Common Channel Signaling (CCS) circuit. Clear channel voice cross connect mode is used by DS0s carrying voice traffic on 23 B-channels of CCS circuits and is used for such applications 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.



Configuring a T1 Interface for Cross Connect

Configuring a T1 Interface for Cross ConnectCaution: 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 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).


2 Enter Serial Interface Configuration Mode, specifying the T1 interface:Occam(config)# interface serial {1-8}

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

4 Select a facility data link (fdl) standard for a T1 data link:

ansi selects ANSI T1.403.

att selects AT&T TR54016

both selects both ANSI T1.403 and AT&T TR54016

slc96rt selects SLC96 Remote Terminal

the command no service module t1 fdl disables the fdl optionOccam(config-if-serial)# service-module t1 fdl {ansi | att | both | slc96rt}

5 Specify the framing format.

esf selects Extended Super Frame (factory default)

sf selects Super Frame

slc96 selects SLC-96 formatOccam(config-if-serial)# service-module t1 framing {esf | sf | slc96}


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01Configuring a T1 Interface for Cross Connect


For example:Occam(config-if-serial)# info cross-connect-mode data

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}

9 (Optional) Enable 16 or 32 bit Cyclic Redundancy Checks (CRC) for error-checking. This command is optional if you select 16-bit CRC, the factory default:

Occam(config-if-serial)# crc {16 |32}

10 (Optional) Configure the line build-out. There is no default:Occam(config-if-serial)# service-module t1 lbo {-15 db | -7.5 db | none}

11 (Optional) Enable the system to generate and detect remote (yellow) alarms: Occam(config-if-serial)# service-module t1 remote-alarm-enable

12 (Optional) Configure the T1 to enter loopback mode when it receives a loopback code on the line. The default is full and payload loopbacks with standard-loopup codes:Occam(config-if-serial)# service-module t1 remote-loopback {full | payload}







Configuring Network Clocking

Configuring Network ClockingNetwork Synchronization Protocol (NSP) is used to keep clocking synchronized between BLCs. NSP provides for several clock sources (called transmitters) that broadcast NSP information. BLCs that want to sync to a broadcast are called receivers, and can listen to a primary and a secondary transmission stream.

In a typical network configuration, one or more BLC 6440-01 or BLC 6640-01s are configured as NSP transmitters and BLCs are configured as NSP receivers.


2 Specify a T1 interface as the primary source for clocking:Occam(config)# network-clock-select primary serial {1-8}

3 Specify a T1 interface as the secondary source for clocking:Occam(config)# network-clock-select secondary serial {1-8}

4 Configure the BLC 6440-01 or BLC 6640-01 as a NSP transmitter, specifying a unique broadcast number between one and thirty-two:Occam(config)# nsp mode tx {1-32}






BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01Configuring a Cross-Connect Subscriber Profile

Configuring a Cross-Connect Subscriber ProfileWhen you enter a Cross-Connect Profile Configuration Mode you have access to a profile for that mode. This section shows the initial values for profiles in the various cross-connect profile configuration modes.

The Cross-Connect Data Default Profile is shown on page 566

The Cross-Connect Voice Default Profile is shown on page 566

The Cross-Connect Voice Channel Associated Signaling (CAS) Default Profile is shown on page 567

The Cross-Connect Voice Non-CAS Default Profile is shown on page 567

Default Values For Cross-Connect Subscriber Profiles

Cross-Connect Data Default Profile

Profile type: cross-connect-data Input Gain: 0 dB Output Gain: 0 dB Forward Disconnect: 900 milliseconds Packetization Period: 10 milliseconds Jitter Delay: 20 milliseconds Fax Delay: 0 milliseconds Fax CNG Detect: disable Fax CNG Timer: 0 seconds Signaling Type: clear-channel Rtp Signaling Type: none Echo cancel: disable Echo tail length: 48 milliseconds Echo Tone Disabler: G.165 Idle Channel Suppression: disable Rtcp Missed Event: enable Codecs: g711bypass MGCP Type: OccamCompliant Modem Codec Bypass: enable

Cross-Connect Voice Default ProfileProfile type: cross-connect-voice Input Gain: 0 dB Output Gain: 0 dB Forward Disconnect: 900 milliseconds Packetization Period: 10 milliseconds Jitter Delay: 20 milliseconds Fax Delay: 0 milliseconds Fax CNG Detect: disable



Configuring a Cross-Connect Subscriber Profile

Fax CNG Timer: 0 seconds Signaling Type: transparent Rtp Signaling Type: transparent2833 Echo cancel: enable Echo tail length: 48 milliseconds Echo Tone Disabler: G.165 Idle Channel Suppression: disable Rtcp Missed Event: enable Codecs: g711ulaw MGCP Type: OccamCompliant Modem Codec Bypass: enable

Cross-Connect Voice Channel Associated Signaling (CAS) Default ProfileProfile type: cross-connect-voice-cas Input Gain: 0 dB Output Gain: 0 dB Forward Disconnect: 900 milliseconds Packetization Period: 10 milliseconds Jitter Delay: 20 milliseconds Fax Delay: 0 milliseconds Fax CNG Detect: disable Fax CNG Timer: 0 seconds Signaling Type: transparent Rtp Signaling Type: transparent2833 Echo cancel: enable Echo tail length: 48 milliseconds Echo Tone Disabler: G.165 Idle Channel Suppression: disable Rtcp Missed Event: enable Codecs: g711ulaw MGCP Type: OccamCompliant Modem Codec Bypass: enable

Cross-Connect Voice Non-CAS Default ProfileProfile type: cross-connect-voice-non-cas Input Gain: 0 dB Output Gain: 0 dB Forward Disconnect: 900 milliseconds Packetization Period: 10 milliseconds Jitter Delay: 20 milliseconds Fax Delay: 0 milliseconds Fax CNG Detect: disable Fax CNG Timer: 0 seconds Signaling Type: clear-channel Rtp Signaling Type: none Echo cancel: enable Echo tail length: 48 milliseconds Echo Tone Disabler: G.165 Idle Channel Suppression: disable Rtcp Missed Event: enable



Codecs: g711ulaw MGCP Type: OccamCompliant Modem Codec Bypass: enable






2 Enter a Cross-Connect Subscriber Profile Configuration Mode and configure a cross-connect profile. The prompt will change to occam(config-profile)<profileName>#.

The cross-connect profile mode options are:

Cross-Connect Data Mode:occam(config)# subscriber-profile cross-connect data {profile-name}

Cross-Connect Voice CAS Mode:occam(config)# subscriber-profile cross-connect voice cas {profile-name}

Cross-Connect Voice Non-CAS Mode:occam(config)# subscriber-profile cross-connect voice non-cas {profile-name}

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

and the prompt would change to:Occam(config-profile)<ds0_data_new>#

3 Configure the subscriber profile with the commands described in Table 27-1 on page 570.

4 Exit Cross-Connect Subscriber Profile Configuration Mode:Occam(config-profile)<profileName># exit



6 Please to section Configuring an Interface Group on page 575 to continue your configuration.



Table 27-1: Subscriber Profile Configuration Commands


Input Gain Value- Specify the input gain value in decibels (dB). The default for all subscriber cross-connect profiles is 0 dB.

occam(config-profile)profile-name#input-gain {-12dB..12dB}

output-gain - Set the output gain, local adjustment in decibels. The default for all subscriber cross-connect profiles is 0 dB.

occam(config-profile)profile-name# output-gain {-12, -11,...11,12}

forward disconnect - Set the amount of time in milliseconds (msec) before there will be an alert sent out after the removal of the battery signal. The default for all subscriber cross-connect profiles is 900 msec.

occam(config-profile)profile-name# forward-disconnect {0,600..120}

packetization period - Set the packetization period in millisec-onds (msec). The default for all subscriber cross-connect profiles is 10 msec.

Note: Occam Networks recommends that the packetization period only be set to 5 msec. on ports that are used for modem/fax support.

occam(config-profile)profile-name# packetization-period {5 | 10 | 20}

jitter delay - Set the jitter buffer delay length in milli-seconds (msec).The parameters are between 10 and 110 in five msec increments. The default for all subscriber cross-connect profiles is 20 msec.

occam(config-profile)profile-name# jitter-delay {10..110}

fax delay - Set the fax jitter buffer delay length in msec. The parameters are between 0 and 210 in five msec increments.The default for all subscriber cross-connect profiles is 0 (disabled).

occam(config-profile)profile-name# fax-delay {0..210}




fax cng detect- Most faxes send audible beep tones called CNG (CalliNG) tones. A CNG tone is a beep that repeats every three seconds. A fax generates a CNG tone after it has dialed a destination fax’s number and is waiting for it to answer.Many of the latest fax machines (Super G3) generate 2100hz tone with phase reversal just as modems do. The fax CNG detector provides a way to distinguish between these fax machines and modems. The command fax-cng-detect may be used to enable or disable the fax CNG detector on the BLC. The fax CNG detector is disabled by default on all subscriber cross-connect profiles.


fax cng timer - Configures how long the fax CNG detector is enabled at the start of a call. The command specifies the amount of time the CNG detector is on in one second increments.The default for all subscriber cross-connect profiles is 0.

occam(config-profile)profile-name# fax-cng-timer {0, 1....120}

Signaling Type - Selects the signaling mode. The options are:

clear-channel: Utilize clear-channel mode. This the factory default setting for the Cross-Connect Data and Cross-Connect Voice Non-CAS Profiles.

transparent: Utilize transparent signaling mode. This is the factory default setting for the Cross-Connect Voice and the Cross-Connect Voice CAS profiles.

Cross-Connect Data Profile: occam(config-profile)profile-name# sig-type clear-channel

(Not configurable)

Cross-Connect Voice Profile,Cross-Connect Voice CAS Profile,Cross-Connect Voice Non-CAS Profile: occam(config-profile)profile-name# sig-type {clear-channel, transparent}



RTP Signaling Type - Selects the Real-time Transport Protocol (RTP) Signaling Mode

none: Utilize no RTP signaling. This the factory default setting for the Cross-Connect Data and Cross-Connect Voice Non-CAS Profiles.

transparent2833:Utilize transparent RFC2833 RTP mode. This is the factory default setting for the Cross-Connect Voice and the Cross-Connect Voice CAS profiles.

nuera2833: Utilize Nuera RFC2833 RTP mode.

Cross-Connect Data Profile: occam(config-profile)profile-name# rtp-sig-type none

(Not configurable)

Cross-Connect Voice Profile,Cross-Connect Voice CAS Profile,Cross-Connect Voice Non-CAS Profile: occam(config-profile)profile-name# rtp-sig-type {none, nuera2833, transparent2833}

echo-cancel - Cancels voice echo during a call.

disable - disable ECAN locally, ignore MGCP setting. This is the setting for the Cross-Connect Data profile.

enable- enable ECAN locally, ignore MGCP setting. This is the setting for the Cross-Connect Voice, Cross-Connect Voice CAS and Cross-Connect Voice Non-CAS profiles.

occam(config-profile)profile-name# echo-cancel {enable, disable}

echo tail length - Sets the echo tail-length in milliseconds. Echo tail length (or echo path delay) is the amount of delay in time over which echo is controlled. The default for all cross-connect profiles is 48 milliseconds.





echo tone disabler-The echo-tone-disabler command may be configured to disable the echo canceller feature when a 2100 Hz tone is detected. The tone is used in both fax and modem protocols and it may or may not have phase reversal. Phase reversal is used to disable echo cancellation.

disable- Ignore 2100 Hz tone


G.165 - Bypass echo cancellation on 2100 Hz tone with phase reversal. This is the factory default for all cross-connect profiles.

occam(config-profile)profile-name# echo-tone {disable, G.164, G.165}

Idle Channel Suppression(Not configurable)

N/A

rtcp-missed-event - Enable the BLC 6640-01 to accept Real Time Transport Control Protocol (RTCP) missed event messages. The mgcp-option rtcp-missed-event command is usually enabled, but doesn't have to be. This command may need to be disabled if the BLC is configured to send voice on a channel. If the DSP on the BLC misses 4 consecutive RTCP messages, it sends an event to the Trunking Gateway (TGW). If the mgcp-option rtcp-missed-event command is enabled, when the TGW receives that event, it will treat it as if the endpoint is unreachable, and will do the required steps to tear down the call (e.g., to prevent a call from being charged long distance when the connection has died). Some Integrated Access Devices (IADs) don't send out the RTCP as often as they should when mapping a channel.The mgcp-option rtcp-missed-event command is enabled by default on all subscriber cross-connect profiles.

occam(config-profile)profile-name# mgcp-option rtcp-missed-event {enable, disable}



Codec: preferred coder-decoder (codec) used during call compression (not configurable):g711bypass: This is the factory default value for the Cross-Connect Data profile.g711ulaw: ulaw PCM

This is the factory default value for the Cross-Connect Voice, Cross-Connect Voice CAS, Cross-Connect Voice Non-CAS profiles.

N/A

mgcp-type - Select the corresponding MGCP type for remote endpoint as Occam-compliant(Not configurable)

N/A

modem codec bypass - Configures the modem-codec-bypass as:


enabled - Configures the profile to follow the settings of the echo-tone-disabler command. By factory default all cross-connect profiles have the modem codec--bypass setting enabled.





occam(config-profile)profile-name# modem-codec-bypass {enable, disable}



Configuring an Interface Group

Configuring an Interface GroupChannels that have DS0 cross connect endpoint must have a DS0 voice cross connect subscriber profile assigned. For example, if “phone/25@BLC 6440” is assigned to interface group 1, channel 25, then that channel must also have a DS0 voice cross connect channel assigned.

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.


2 Enter Interface Group Configuration Mode and select an interface group number between one and two to configure:Occam(config)# interface-group {1-2}

3 Configure the interface group mode as cross-connect

Note: The prompt is (config-interface-group-tr08) because TR-08 is the factory default interface-group mode. This will change to (config-interface-group-cross-connect) in the next step. Select D1D or D4 channel to timeslot mapping mode. The factory default is D4 channel to timeslot mapping mode:

Occam((config-interface-group-tr08)# mode cross-connect {d1d | d4}

4 Assign a T1 interface to the interface group.

{1-4} specifies the logical T1 number

{1-8} specifies the physical T1 interface number.Occam(config-interface-group-cross-connect)# assign serial {1-4} {1-8}

5 Enter RT Channel Configuration Mode and select a single channel or a range of channel numbers between 1 to 24 to configure.

Use the channel command to configure a channel number:Occam(config-interface-group-cross-connect-channel)# channel {1-24}

For example, if you are configuring channel 1 the command is:Occam(config-interface-group-cross-connect-channel)# channel 1

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}


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01Configuring 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

6 Configure MGCP endpoint mapping for the channel or range of channels between 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/[email protected]”, the command is:Occam(config-interface-group-cross-connect-channel)# endpoint phone/[email protected]

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/[email protected]”, the command is:Occam(config-interface-group-cross-connect-channel)# endpoint phone/[email protected]

The results would be

channel 1 mapped to phone/[email protected]





7 (Optional) Attach a description to the channel or channels (for example "Asso-ciated with 480-555-1001 on the LDS)":Occam(config-interface-group-cross-connect-channel)# description descriptive-text

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




(For example, if you had created a subscriber profile called “ds0_data_new” earlier, the command would be:Occam(config-interface-group-cross-connect-channel)# attach-profile ds0_data_new

9 Exit RT Channel Configuration Mode:Occam(config-interface-group-cross-connect-channel)# exit

10 Enable the Interface Group:Occam(config-interface-group-cross-connect)# no shutdown

11 Exit Interface Group Configuration Mode:Occam(config-interface-group-cross-connect)# exit




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 27: Configuring DS0 Cross Connect Modes on the BLC 6640-01Viewing Your Configuration

Viewing Your ConfigurationThe following commands may be used to view your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide.

show interface-group [IG number] [first channel number] [last channel number]: use this command from User Configuration Mode to view information about an IG configuration. You may this command to verify that the mode is correct, that the T1 lines in the IG are configured correctly, and that the chan-nels are correctly configured. This command may be configured to display information about all IGs configured on the BLC, a specific IG or a specific range of channels on a specified IG.

show interface-group endpoint {MGCP endpoint-name}: use this command to view to which IG/CRV an endpoint is mapped. An example of an MGCP endpoint-name is “phone/[email protected]”.

show interface-group statistics {ig-number}: use this command from to view statistical information about an interface group.

show interface-group summary: use this command to view information about IG configurations. The output is sorted by serial interface numbers.

show subscriber-profile {profile-name}: use this command to verify that a configured profile has the correct settings.

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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf

Configuration

Chapter 28Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf Configuration

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579Shelf Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580Self Deployment Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582Configuring the Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587Configuring T1 Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592Configuring Network Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594GR-303 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595Configuring an IG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602Configuring Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609Configuring GR-303 Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612Initiating a Switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613Configuring Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613Removing Cards from the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615Viewing Your CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616

IntroductionThe 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.

Caution: Any unused (unconnected) T1 lines should be disabled with the

!

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 28: Configuring the BLC 6640-01 for GR-303 Interoperability in a Shelf Configuration

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).

Shelf Configuration OverviewTwo or more 6640-01 blades or BLC 6640-01 assemblies may be combined into a single shelf unit. This shelf can be managed and configured as a single entity. This allows up to 28 DS1s to be configured in a single GR-303 IG. GR-303 IGs can be configured to utilize T1s from all BLCs in the shelf

In the shelf architecture, two 6640-01 blades or BLC 6640-01 assemblies act as an active and standby shelf controller configuration. The shelf controller is responsible for providing a single point of contact for managing up to twelve 6640-01 blades within the shelf. If the active shelf controller fails, the standby shelf controller takes over the shelf management functionality.

A cluster IP address is shared between the active and standby shelf controllers. Only the active shelf controller receives traffic directed to the cluster IP.

The active/standby shelf controller configuration allows management applications such as the OccamView Element Management System (EMS) to manage the shelf. This configuration also enables the shelf to maintain integrity during conditions where one of the shelf controllers is down or unreachable.

The shelf management application may reside on a 6640-01 blade that is also acting as an active (or standby) GR303 gateway carrying voice traffic.


GPO

N C

omm

and Reference G

uideCLI C

omm

ands

785553 Rev. 2.0

Proprietary Inform

ation - Occam

Netw

orks Inc.P

age 581 of 88010/09/08

PSTN

etwork

r

troller

ch

Figure 28-1: Sample Shelf Configuration

BLC

REMOTE TERMINAL

BLC

REMOTE TERMINAL

1- 48 SUBSCRIBERLINES PER BLC

TR-08 ORGR-303

(UP TO 4/8 DS1SPER BLC)

IPNETWORK

CENTRAL OFFICE

MGCP AND RTP FOR VOICEIP FOR DATA

6640 (STAN

DBY SC)

6640 (PRIMA

RY SC)

6640

6640

6640

6640

6640

6640

6640

6640

6640

6640

KEY

PSTN = Public Switched Telephone N

Primary SC = Primary Shelf Controlle

Secondary SC = Secondary Shelf Con

BLC 6012

Class 5 Swit


Self Deployment GuidelinesShelf Configuration Network Design Principals

GR-303 shelf deployments must balance several network design principles. These principals must consider the limitations of GR-303 as well as other network concerns. The limitations of GR-303 are described below.

Network Design Principles to consider are:

Minimize number of blades used

Maximize density in terms of number of T1s and endpoints

Maximize performance, both during "normal" operations and during network events

Optimize redundancy

Considerations of interactions with other network services, such as data and video services

Balancing the GR-303 limitations, Occam-specific GR-303 considerations, and shelf considerations involves experience and best judgment. These guidelines should be considered as guidelines only: each network deployment is unique, depending upon the number of nodes in the network and the services offered.

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

For example, if there are 6 T1s, then:

# Available DS0s = (6)*(24) - 4 = 140

Maximum of 2048 endpoints per interface group

Variable concentration ratios (number of endpoints / number of available DS0s)

GR-303 does not define fixed concentration ratios, but instead allows any



Configuration

combination of endpoints and T1s. Continuing the example from above of 6 T1s, with 1400 endpoints the concentration ratio is 1400 / 140 = 10.

Higher concentration ratios allow fewer switch resources to be consumed, but increase the likelihood that an end user will not get dial tone on the first offhook. Higher concentrations are typically used for residential customers.

Lower concentration ratios consume more switch resources, but have a lower likelihood that an end user will not get dial tone on the first offhook. Lower concentrations are typically used for business customers, and for applications where lines are continuously in use (such as data services or dial up lines).

Supported GR-303 Network ConfigurationsIn light of the GR-303 limitations, Occam Networks supports the following configurations in the current release of GR-303 code:

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 vs. Non-Redundant GR-303 IGs

Non-Redundant Configurations

In a non-redundant configurations, the primary and secondary T1s for the IG are on the same 6640-01 blade.

Non-redundant configurations lose voice services whenever the 6640 blade with the primary and secondary T1s is down (for maintenance, etc.)

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

Number of BLC 6640s

Max Number of IGs Max

Maximum Number of Endpoints

Maximum Number of Simultaneous

Calls

2 2 4,096 380

4 4 8,000 764

6 5 10,000 1148

8 7 14,000 1532

10 9 15,000 1916

12 10 16,000 2300



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 vs. Striping Configurations For GR-303 IGsThe T1s for a GR-303 IG can be spread across one or more 6640-01 blades in a solo or striping configuration. Occam Networks recommendation is to utilize striping configuration when possible.

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 ConfigurationsThe 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:

phone/1@mgw-abc could be mapped to IG 1, channel 101

phone/2@mgw-abc could be mapped to IG 2, channel 299

This flexibility allows endpoints to be mapped to IGs with different concentration ratios, different switches, etc.



Configuration

Subscriber Profiles for Endpoints / ChannelsThe 6640-01 provides several default subscriber profiles, and allows the creation of new subscriber profiles. Subscriber profiles contain configuration for signaling, echo cancellation, etc. that maximize the performance for endpoints.

Subscriber profiles are set for each channel within in an IG. For example:subscriber profile "customer_profile_Z" is mapped to IG X, channel Y

Subscriber profiles allow endpoints from different vendors of media gateway, as well as different end user settings, to be mapped to IGs.

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.

Blades With IG Applications

Every redundant GR-303 IG has a primary and secondary T1 on separate 6640-01 blades. The blade with the primary T1 runs the primary interface group applications, and the blade with the secondary T1 runs the secondary interface group applications.

These blades have an additional CPU load to perform IG operations, both with the switch and with the media gateway endpoints.

There can be no more than two primary or secondary T1s for IGs per blade.

If there are two primary or secondary T1s for IGs on a blade, both IGs must both be either a primary or a secondary. In other words, a GR-303 shelf deployment cannot have a primary of one IG on the same blade as the secondary of another IG.

Network ConfigurationsDeployments 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.



Interactions With Other Services

CES T1s cannot be on the same blade as primary or secondary T1s for IGs.

If running video/IGMP on the same EPS ring, do not run the SC function on the VPT blades.

Non-GR-303 interface groups (TR-08 and cross-connect interface groups) cannot be configured on the same blades that have the primary or secondary T1 for a GR-303 IG. The recommendation is that TR-08 and cross-connect interface groups not be configured on the same blades that have shelf controller functionality.

ON 2342 ONT configuration: The Occam GR-303 shelf defaults to nuera2833 RTP signaling, but currently only cablelabs2833 is supported by the ON2342. Endpoints in the GR-303 shelf should be configured via IP address rather than by hostname as with the BLC.

Maintenance / Upgrade WindowsShelf reloads/upgrades should be performed during off-peak or low load periods.



Configuration

Configuring the ShelfThis section describes how to configure a shelf. These steps include configuring 6640-01 blades as cards in the shelf, and configuring a 6640-01 blade as a primary or standby shelf controller.

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.

Setting the Shelf and Slot IDsEach "shelf" and each "slot" in the network should be uniquely numbered.

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.

Configuring 6640-01s as Cards in the Shelf

1 Connect to the 6640-01 that you want to configure as a card 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> enablePassword:

3 Enter Global Configuration Mode:Occam# configure terminal



Enter configuration commands, one per line. End with CNTL/Z.Occam(config)#

4 Enter Shelf Configuration Mode:Occam(config)# shelf

5 Set the 6640-01 system to card mode:Occam(config-shelf)# mode card

6 Exit Shelf Configuration Mode:Occam(config-shelf)# exit

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

8 Dynamic Host Configuration Protocol (DHCP) is enabled by factory default. If your network uses a DHCP server to assign addresses, go on to step 12. If you are not using a DHCP server, follow these steps to assign static IP addresses to the BLC 6640-01:

Enter Bvi Interface Configuration Mode to create a bridge-group virtual interface (BVI), specifying interface 1 (one):occam(config)# interface bvi 1

Stop DHCP from attempting to add an IP address:occam(config-if-bvi)# no ip address

Assign an IP address and subnet mask to the bridge group:occam(config-if-bvi)# ip address ip-address subnet-mask

Exit out of Bvi Interface Configuration Mode:occam(config-if-bvi)# exit

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

Enter Bvi Interface Configuration Mode again:Occam(config)# interface bvi 1

9 Enable the bridge group:Occam(config-if-bvi)# no shutdown

10 Exit Bvi Configuration Mode:occam(config-if-bvi)# exit

Repeat these steps for each BLC 6640-01that you want to configure as a card in the shelf.



Configuration

Configuring a 6640-01 as a Primary Shelf Controller You must configure one 6640-01 as a primary shelf controller and another as a standby shelf controller in a shelf configuration. The first 6640-01 configured with the mode shelf command is the primary shelf controller.

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>




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.102Occam(config-shelf)# insert card 10.0.0.103Occam(config-shelf)# insert card 10.0.0.104Occam(config-shelf)# insert card 10.0.0.105






Configuration

Configuring a 6640-01 as a Standby Shelf Controller

1 Connect to the 6640-01 that you want to configure as a standby 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>




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}




Configuring T1 LinesCaution: 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.


2 Enter Serial Interface Configuration Mode, specifying a slot and a T1 interface port number between one and eight:occam(config)# interface serial {slot}/{port 1-8}

3 Remove the ip address:Occam(config-if-serial)# no ip address

4 Enable channelized mode:Occam(config-if-serial)# mode channelized


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

!



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>, '?', '!'.



11 Repeat steps 2 through 10 for each T1 interface to be used on the BLC 6640-01.



Note: Executing the command copy running-config startup-config on the active shelf controller causes this activity to be performed on all blades within the shelf.



Configuring Network ClockingNote: Network clocking must be done on each blade (cards and shelf controllers) in the shelf configuration.

Network Synchronization Protocol (NSP) is used to keep clocking synchronized between BLCs. NSP provides for several clock sources (called transmitters) that broadcast NSP information. BLCs that want to sync to a broadcast are called receivers, and can listen to a primary and a secondary transmission stream.

In a typical network configuration, one or more BLC 6640-01 or 6640-01 blades are configured as NSP transmitters and all other BLCs in the network are configured as NSP receivers.




4 Configure the BLC 6640-01s or 6640-01 blade as a NSP transmitter, specifying a broadcast number between one and thirty-two. One or more BLC 6640-01s or 6640-01 blades in the shelf can be NSP transmitters. Typically the two bookend BLCs (slot 1 and slot 12) are each NSP transmitters.:Occam(config)# nsp mode tx {1-32}

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.







Configuration

GR-303 Subscriber ProfileTo configure a channel in an IG you must attach a GR-303 subscriber profile to it. A profile includes parameters such as the signaling mode and 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.

Default GR-303 Subscriber ProfileThere are two default subscriber profiles created on the BLC 6640-01 and 6640-01 blade. One, called "default" is pre-set for TR08 mode. The other, called "default-gr303" is pre-set for GR-303 mode. The "default-gr303" profile is initially attached to all channels in a GR-303 IG, unless another profile is specifically attached to the channels.

When configuring a BLC 6640-01 or 6640-01 blade for GR303 interoperability, you must either create a new subscriber-profile, or modify the "default-gr303" subscriber profile.

The initial values for this profile are shown below. Commands to change these defaults are shown in Table 28-1.occam(config)#show subscriber-profile defaultprofile: default Profile type: tdm-tr08 Input Gain: 0 dB Output Gain: 0 dB Forward Disconnect: 900 milliseconds Packetization Period: 10 milliseconds Jitter Delay: 20 milliseconds Fax Delay: 0 milliseconds Fax CNG Detect: disable Fax CNG Timer: 0 seconds Signaling Type: slc96rt-sp Rtp Signaling Type: nuera2833 Echo cancel: enable Echo tail length: 48 milliseconds Echo Tone Disabler: G.165 Idle Channel Supression: enable Rtcp Missed Event: enable Codecs: g711ulaw MGCP Type: OccamCompliant MGCP Profile: MGCP Modem Codec Bypass: enable


785553 Rev. 2.0

Proprietary Inform

ation - Occam

Netw

orks Inc.P

age 596 of 88010/09/08

GPO

N C

omm

and Reference G

uideCLI C

omm

ands

name# input-gain {-12dB..12dB}

name# output-gain {-12, -11,

name# forward-disconnect {msec}

name# packetization-period {msec}

name# jitter-delay {msec}

name# fax-delay {msec}

Table 28-1: Default Subscriber Profile Attributes

Profile Feature Default Value Command

Input Gain Value- Specify the input gain value in decibels.

0 dB occam(config-profile)profile-

Output-GainSet the output gain, local adjustment in decibels.

0 occam(config-profile)profile-...11,12}

Forward Disconnect Set the amount of time in milliseconds before there will be an alert sent out after the removal of the battery signal.

900 milliseconds

occam(config-profile)profile-

Packetization PeriodSet the packetization period in milliseconds.

Note: Occam Networks recommends that the packetization period only be set to 5 ms. on ports that are used for modem/fax support.

10 milliseconds.


Jitter DelaySet the jitter buffer delay length in millisec-onds (msec).The parameters are between 10 and 110 in five msec increments

20 ms occam(config-profile)profile-

Fax DelaySet the fax jitter buffer delay length in msec. The parameters are between 0 and 210 in five msec increments

0 msec (disabled)


GPO

N C

omm

and Reference G

uideCLI C

omm

ands

785553 Rev. 2.0

Proprietary Inform

ation - Occam

Netw

orks Inc.P

age 597 of 88010/09/08 Fax C

Most (CalliNrepeaCNG tnumbManygeneras moa waymachThe coenablBLC.

ax-cng-detect {enable,

Fax CConfienablThe coCNG d

ax-cng-timer {0, 1....120}

SignaSpeci

ig-type gr303-rt

Profil

NG Detectfaxes send audible beep tones called CNG G) tones. A CNG tone is a beep that

ts every three seconds. A fax generates a one after it has dialed a destination fax’s er and is waiting for it to answer. of the latest fax machines (Super G3) ate 2100hz tone with phase reversal just dems do. The fax CNG detector provides to distinguish between these fax ines and modems. mmand fax-cng-detect may be used to

e or disable the fax CNG detector on the

disabled occam(config-profile)profile-name# fdisable}

NG Timergures how long the fax CNG detector is ed at the start of a call. mmand specifies the amount of time the etector is on in one second increments

0, No timer, fax CNG detector on at all times

occam(config-profile)profile-name# f

ling Typefy GR-303 as the signalling mode

GR-303RT occam(config-profile)profile-name# s

e Feature Default Value Command

785553 Rev. 2.0

Proprietary Inform

ation - Occam

Netw

orks Inc.P

age 598 of 88010/09/08

GPO

N C

omm

and Reference G

uideCLI C

omm

ands

name# rtp-sig-type

name# echo-cancel enable

name# echo-tail-length {24, 32, 48,

name# echo-tone {disabler, G.164,

RTP Signaling Type Enable the Real-time Transport Protocol (RTP) Signaling Mode. Choose between:

nuera2833- Utilize Nuera RFC2833 RTP mode

cablelabs2833- Utilize Cable Labs RFC2833 RTP mode

When you are creating a subscriber profile for use with the ON2342 you must use the “cablelabs2833” option.

NUERA2833 occam(config-profile)profile-(nuera2833,cablelabs2833}

Echo CancelEnable echo cancellation

Enabled occam(config-profile)profile-

EchoTail LengthSet the echo tail length in milliseconds

48 milliseconds

occam(config-profile)profile-64, 80, 96, 112, 128}

Echo Tone DisablerThe echo-tone-disabler command may be configured to disable the echo canceller feature when a 2100 Hz tone is detected. The tone is used in both fax and modem protocols and it may or may not have phase reversal. Phase reversal is used to disable echo cancellation.

disable- Ignore 2100 Hz tone


G.165 - Bypass echo cancellation on 2100 Hz tone with phase reversal

G.165 occam(config-profile)profile-G.165}


GPO

N C

omm

and Reference G

uideCLI C

omm

ands

785553 Rev. 2.0

Proprietary Inform

ation - Occam

Netw

orks Inc.P

age 599 of 88010/09/08 Idle C

(Not c

RTCP EnablTransmessaThe mcommto be.if thechannconseto theIf thecommthat eunreatear dbeingtion h(IADs)shoul

gcp-option rtcp-missed-

Codec(Not c

Profil

hannel Suppressiononfigurable)

Enabled N/A

Missed Evente the BLC 6640-01 to accept Real Time port Control Protocol (RTCP) missed event ges. gcp-option rtcp-missed-event and is usually enabled, but doesn't have This command may need to be disabled BLC is configured to send voice on a el. If the DSP on the BLC misses 4 cutive RTCP messages, it sends an event Trunking Gateway (TGW). mgcp-option rtcp-missed-event and is enabled, when the TGW receives vent, it will treat it as if the endpoint is chable, and will do the required steps to own the call (e.g., to prevent a call from charged long distance when the connec-as died). Some Integrated Access Devices don't send out the RTCP as often as they d when mapping a channel.

Enabled occam(config-profile)profile-name# mevent {enable, disable}

onfigurable)g711ulaw N/A

e Feature Default Value Command

785553 Rev. 2.0

Proprietary Inform

ation - Occam

Netw

orks Inc.P

age 600 of 88010/09/08

GPO

N C

omm

and Reference G

uideCLI C

omm

ands

name# mgcp-type nnomedia|telcosystems|genericiad}

name# mgcp-profile {mgcp|ncs}

name# modem-codec-bypass {enable,

MGCP TypeSelect 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 compliant

occam(config-profile)profile-{occamcompliant|wave7optics|i

MGCP ProfileSelect the corresponding MGCP profile remote endpoint.

Note: When upgrading from OccamOS 5.4 to OccamOS 5.5 NCS settings will be lost and all subscriber profiles will be configured in in MGCP mode. You must manually enter the "mgcp-profile ncs" command in all applicable subscriber profiles.

MGCP occam(config-profile)profile-

Modem Codec BypassSet the modem codec bypass values

disable=No codec bypass

enable-Codec bypass follows echo tone disabler

enabled occam(config-profile)profile-disable}



Configuration

Configuring a GR-303 Subscriber ProfileTo configure a GR-303 subscriber profile use the following configuration steps:

Note: The following commands are entered on the shelf controller.


2 Configure a GR-303 subscriber profile:Occam(config)# subscriber-profile tdm gr303 {profile-name}

For example, if a subscriber profile with the name “gr303new” is being config-ured, the command isOccam(config)# subscriber-profile tdm gr303 gr303new

and the prompt would change to:Occam(config-profile)gr303-new#

3 Use the commands listed in Table 28-1 to configure the subscriber profile.

4 Exit GR-303 Subscriber Profile Configuration Mode and return to Global Configuration Mode:Occam(config-profile)<profileName># exit



6 Please turn to Configuring an IG on page 602 to continue your configuration.



Configuring an IGTo 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.

Note: A GR-303 IG allows for oversubscription of up to 2048 subscribers using up to 28 T1s.

Note: The following terms are used in this chapter:

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.



Configuration

An example of an acceptable configuration is shown in Figure 28-2. This example shows a shelf with twelve 6640-01 blades.

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.



Figure 28-2: GR-303 Shelf Configuration Example

6640(STA

ND

BY SC)

12

6640

1

6640(PRIM

ARY SC)

2 3 4 5 6 7 8 9 10 11

KEY

= Primary T1 for a GR-303 IG

= Secondary T1 for a GR-303 IG

= "Traffic Only " T1 for a GR-303 IG

= Interface Group

A

B

A B

A B

A B

A B

IG 1

IG 2

IG 3

IG 4

6640

6640

6640

6640

6640

6640

6640

6640

6640



Another example of an acceptable configuration is shown in Figure 28-3. This example shows a shelf with only five 6640-01 blades.


IG 2 has the primary T1 line on 4/3 and the secondary T1 line on 12/3.



Figure 28-3: GR-303 Shelf Configuration Example 2

An example of an unacceptable configuration is IG 1 with the primary T1 line on 2/1 and the secondary T1 line on 3/1 and IG 2 with the primary T1 line on 3/1 and the secondary T1 line on 4/1.

6640(STAN

DBY SC)

12

EMPTY

1

6640(PRIM

ARY SC)

2 3 4 5 6 7 8 9 10 11

KEY

= Primary T1 for a GR-303 IG

= Secondary T1 for a GR-303 IG

= "Traffic Only " T1 for a GR-303 IG

= Interface Group

A

B

A B

A B

A B

A B

IG 1

IG 2

IG 3

IG 4

EMTPY

EMPTY

EMTPY

EMTPY

EMPTY

EMPTY

6640

6640

6640



Configuration

Steps to Configure an IG

Note: The following commands are entered on the shelf controller 6640-01.


2 Configure an IG, choosing a number between one and ten:Occam(config)# interface-group {1-10}

3 Enable GR-303 mode:Occam(interface-group)# mode gr303

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/2Occam(interface-group-gr303)ig-1# assign serial 4 4/2



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}

9 (Optional) Inhibit a EOC PPS on the selected channel

Note: The command no inhibit pps-eoc will disable this feature and allow the PPS to occur normally.Occam(interface-group-gr303)ig-number# inhibit pps-eoc {primary | secondary}

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.



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}

11 Set the maximum number of information frames that may be outstanding at LAPD. The default is 7:Occam(interface-group-gr303)ig-number# maxiframes {1-7}

12 (Optional) Inhibit a TMC path protection switch on the selected channel:Occam(interface-group-gr303)ig-number# inhibit pps-tmc {primary | secondary}

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

14 (Optional) Enable the periodic-audit command to cause the IG to periodically audit all its endpoints by sending out an MGCP AuditEndpoint message. The IG does this to proactively ensure that the endpoints are reachable and are working properly. This feature is enabled by default. The IG needs to be restarted for this change to take effect:Occam(interface-group-gr303)ig-number# periodic-audit {enable | disable}

15 (Optional) Use the option duplex-tmc-failure-restart enable command to enable the IG to restart if a duplex TMC failure condition is encountered. Use the option duplex-tmc-failure-restart disable command to cause the IG to NOT restart if a duplex TMC failure condition occurs. This feature is enabled by default:Occam(interface-group-gr303)ig-number# option duplex-tmc-failure-restart {enable | disable}

16 (Optional) Configure timing. Timing commands are optional, as the factory defaults work well for most environments. The GR-303 timing commands are described in section Configuring GR-303 Timing on page 612.

17 Enable the IG:



Occam(interface-group-gr303)ig-number# no shutdown

18 Exit IG Configuration Mode:Occam(interface-group-gr303)ig-number# exit





Configuration

Configuring ChannelsNote: 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.


2 Enter IG Configuration Mode:Occam(interface-group-gr303)ig-number# interface-group {1-10}

3 Enter IG Channel Configuration Mode and select a single channel or a range of channel numbers to configure.

Use the channel command to configure a single channel:Occam(interface-group-gr303)ig-number# channel {1-2048}

For example, if you are configuring channel 1 the command is:Occam(interface-group-gr303)ig-number# channel 1

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

4 Select a profile by name to attach to the channel or range of channels:Occam(interface-group-gr303-channels)ig-1/chs-number-number# attach-profile profile-name

5 Configure MGCP endpoint mapping for the channel or range of channels and specify a MGCP endpoint name (for example, “phone/[email protected]”):



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/[email protected]”, the command is:Occam(interface-group-gr303-channels)ig-1/ch-1# endpoint phone/[email protected]

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/[email protected]”, the command is:Occam(interface-group-gr303-channels)ig-1/chs-1-5# endpoint-start phone/[email protected]







6 (Optional) Enter a description for a channel:Occam(interface-group-gr303-channels)ig-1/ch-number# description {word that describes the channel}

7 Exit Channel Configuration Mode and return to IG Configuration Mode:Occam(interface-group-gr303-channels)ig-1/chs-number-number# exit

8 Repeat steps 3 through 9 to configure other channels or ranges of channels.

9 Exit IG Configuration Mode:Occam(interface-group-gr303)ig-number# exit



Configuration





Configuring GR-303 Timing

Note: The following commands are entered on the shelf controller.

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}



Configuration

Initiating a SwitchoverThe shelf controller and IG may be “switched over” for maintenance operations.

Shelf Control SwitchoverShelf controls may be switched from the active shelf controller to the standby shelf controller by entering the command switchover from Privileged Mode on the BLC that is the active shelf controller:Occam# switchover

IG SwitchoverIGs 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}.

The option “primary-standby” will attempt to make the primary IG standby. In other words, the primary IG will be standby and the secondary IG will be active. This will be successful after negotiation with the IDT.

Configuring Standalone ModeYou may use the mode standalone command from Privileged Mode to set the system to standalone mode:Occam(config-shelf)# mode standalone {ip-address}

Note: Do not use this command if you have already configured the shelf. This command will disable the shelf.

Removing Cards from the Shelf1 Enter Global Configuration Mode:


2 Enter shelf configuration mode:Occam(config)# shelf

3 Set system to shelf mode, specifying the cluster IP address or hostname of the shelf:



Occam(config)# mode shelf {ip-address}

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



Configuration



You may also use this command to view GR-303 timing information. A properly operating GR303 IG should show at least:

“TGW interface-group Admin State: Active”,

“TGW Oper State: ACTIVE”,

“Primary TMC: Call processing: Up, PPS: Up”,

The status of the first T1 (“TGW configured T1s are”) should read “GR303_PRIMARY” under the “Role” field and “AVAILABLE” under the “State” field.

show interface-group endpoint {MGCP endpoint-name}: use this command to view to which IG/CRV an endpoint is mapped. An example of an MGCP endpoint-name is “phone/[email protected]”

show interface-group statistics {ig-number}: use this command from to view statistical information about an IG

show interface-group summary: use this command to view information about IG configurations. The output is sorted by serial interface numbers

show subscriber-profile {profile-name}: use this command to verify that a configured profile has the correct settings.

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



Viewing Your CPU UsageThe command debug cpu may be used from Privileged mode to display CPU utilization for a specified interval in seconds. The parameters are from 0 to 100 seconds.

The following example displays CPU usage for every two seconds:Occam# debug cpu 2CPU states: 27.6% user, 16.7% system, 0.0% nice, 55.7% idleCPU states: 0.0% user, 8.0% system, 0.0% nice, 92.0% idleCPU states: 0.0% user, 9.0% system, 0.0% nice, 91.0% idleCPU states: 0.0% user, 3.0% system, 0.0% nice, 97.0% idleCPU states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idleCPU states: 0.0% user, 6.5% system, 0.0% nice, 93.5% idle

To exit this display hold down the CTRL and letter C keys at the same time.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 29: Automated Shelf Upgrader

Introduction

Chapter 290Automated Shelf Upgrader

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617Shelf Status Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620Shelf Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

IntroductionThis 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.

Upgrades the software on all of the blades in the shelf.

Reloads all of the blades in the shelf.

Each of the above steps have CLI configuration and status commands as applicable which can only be executed from an active Shelf Controller. A failure anywhere in the upgrade or reload commands will halt the procedure. You may view the status of each step with the relevant show command. If the upgrade or reload procedures do fail, manual intervention is required to proceed. Please call Occam Networks for for assistance.

This feature was released in the OccamOS software release 5.3R2. Once all of the blades in a shelf have been upgraded to release 5.3R2 or beyond, any subsequent shelf upgrades can be done using these commands. Please refer to Chapter 37, Upgrading Shelf Software to Release 5.3R2 in the BLC 6000 System Installation and Configuration Guide, Release 5.4R4 (PN 785535) for information about how to upgrade blades to release 5.3R2.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 29: Automated Shelf UpgraderShelf Status Check

Shelf Status CheckUse the reload shelf check command from Privileged mode to verify that the status of the shelf will support the shelf reload commands.

Entering this command will confirm the following:

All blades in the shelf are configured with the same OS release.

All of the blades in the Shelf can support an automated upgrade

The IG applications are redundant.

The EOC and TMC links are active and redundant.

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:

Occam1#reload shelf checkBuilding configuration... Done (10:11)Running configuration has been changedUse 'copy running-config startup-config' to save modified configuration

IG status:IG Apps Redundant Link Redundant1 yes(secondary) yes

Shelf software:Slot 8 Version 5.3 1174298401Slot 12 Version 5.3 1174298401Slot 1 Version 5.3 1174298401Slot 2 Version 5.3 1174298401

Auto upgrade pre-check state:IG's with links not redundant :

Occam1#

Occam1#copy running-config startup-configBuilding configuration... Done (10:12)Occam1#

Prompt to enter command copy running-config startup-config.

copy running-config startup-configcommand entered.

reload shelf check command entered.on active SC.



Shelf Status Check

Occam1#reload shelf checkBuilding configuration... Done (10:11)




Occam1#

Auto upgrade can commence, since the autoupgrade pre-check state shows no problems andthere are no IG's with links non-redundant links.

reload shelf check command enteredagain on active SC.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 29: Automated Shelf UpgraderSoftware Upgrade

Software UpgradeUpgrading 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

The following example shows a ftp URL:

The login name for the ftp server is “occamnetworks”

The password for the ftp server is “shady1”

The IP address is “192148.11.1”

The directory path is //usr/blc_software.

The file name is 5.5/R1

ftp://occamnetworks:[email protected]//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}

username Login for ftp server.

password Password to ftp server

hostaddr IP address or hostname for the ftp serverNote: if you are using the hostname (i.e.: flipper.occamnetworks.com), you must add it to the host file of the BLC before you may use it in this command.

directory (Optional) If required, enter the directory path to the file.

filename Name of the image on the ftp server.



Software Upgrade

The following example shows sample output from this command:

You may monitor the status of the upgrade by repeatedly entering the show shelf upgrade command.

Occam1#upgrade shelf all ftp://occamnetworks:[email protected]//usr/blc_software/5.3/R2Upgrading all cards in the shelf....Using FTP to locate remote file...Preparing local system for download..###########################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################[OK]Image file renamed to OCCAMOS.V5_3T8Removing OCCAMOS.1173952801 to make roomWriting new kernel to partition 2Kernel installedVerifying partition...Partition verifiedEnabling new kernel...Kernel enabledExtracting firmware package...Installing firmware package...found firmware infoHardware Revision [D]About to check firmware, and install if necessaryFPGA_0 is current!FPGA_1 is current!

Erasing 128 Kibyte @ 0 -- 0 % complete.Erasing 128 Kibyte @ 20000 -- 25 % complete.Erasing 128 Kibyte @ 40000 -- 50 % complete.Erasing 128 Kibyte @ 60000 -- 75 % complete.Erased 512 Kibyte @ 0 -- 100% complete. Booter update successful.------------------------------------------About to re-check firmware(no installation)FPGA_0 is current!FPGA_1 is current!Booter is current!Firmware update complete

Firmware installed

Shelf upgrade status:Start time:Thu Aug 17 10:07:09 GMT+00:00 2006starting upgrade on slot 8starting upgrade on slot 12starting upgrade on slot 1starting upgrade on slot 2Upgrade success on slot 8Upgrade success on slot 12Upgrade success on slot 1Upgrade success on slot 2End time:Thu Aug 17 10:11:18 GMT+00:00 2006

Upgrade complete: Use the 'reload shelf' command to have upgrade take effectand to reboot cards in an orderly manner.Occam1#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 29: Automated Shelf UpgraderShelf Reload

Shelf ReloadUsing 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 shelf is not redundant

The standby SC does not support this reload feature (this blade has not yet been upgraded to 5.3R2)

All IG’s are not redundant

The following shows sample output from this command:

Occam1#reload shelfBuilding configuration... Done (10:13)No configuration changesThis command will reload all blades in this shelf in an orderly manner.Proceed with reload? [y/N] y

Enter "y" when prompted toproceed with reload.

reload shelf command entered onactive SC.



Shelf Reload

Monitoring the Shelf ReloadAs the shelf upgrade is happening, you can check the status of the upgrade with the show shelf and show shelf reload commands. These commands allow you to view how many blades have been upgraded, how many are left to be upgraded, what IG applications are currently being switched over, etc.

Because the active SC is reloaded as part of this procedure, if you are connected to that BLC via a telnet or SSH connection you will need to log in to the BLC that was previously the standby SC to view output from the show shelf and show shelf reload commands.



The following examples show initial output from these commands:

Occam#show shelf reload

Start time:Thu Aug 17 10:13:16 GMT+00:00 2006




Occam#show shelfSystem (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

Slot Address Mode Type SW version Status---- ------- ---- ---- ---------- ------1 192.168.25.130 Card BLC_6640 V5.3R3 up up2 192.168.25.131 Shelf BLC_6640 V5.3R3 up (In progress)8 192.168.25.128 Shelf BLC_6640 V5.3R3 up (local card)12 192.168.25.129 Card BLC_6640 V5.3R3 up

Pending actions for Interface Group Manager: Current action: Card 2 up Queued actions:

Occam#

Occam#Connection closed by foreign host.[jdoe@gopher jdoe]$

show shelf command entered.

show shelf reload command entered.

Upgrade of BLC in slot 2 currently in progress.

Active SC is upgraded, connection is lost.



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:

Occam2#show shelf reload

Upgrade status from previously active SC:





Rebooted slot 2Slot 2 back up.

Proceed with upgrade on new active SC


Shelf software:Slot 8 Version V5.3R2Slot 12 Version V5.3R2Slot 1 Version V5.3R2Slot 2 Version V5.3R2

Auto upgrade pre-check state:IG's with links not redundant :All blades in the shelf do not have same software version

Rebooted slot 8Slot 8 back up.To upgrade slot 1 IG's: 1Rebooted slot 1

Occam2#show shelfSystem (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

Slot Address Mode Type SW version Status---- ------- ---- ---- ---------- ------1 192.168.25.130 Card BLC_6640 5.3 1174298401 down (not reachable)2 192.168.25.131 Shelf BLC_6640 V5.3T8 up (local card)8 192 168 25 128 Shelf BLC 6640 V5 3T8 up

show shelf reload command entered on "Occam2",the BLC that was previously the standby SC and has

now become the active SC.

Slot 8 has been rebootedand is back up.

Slot 1 has beenrebooted but is not

back up yet.

Slot 2 has beenrebooted and is

back up.

Before any BLCs arereloaded, the status ofshelf is checked. This is

reported by "Occam1", thepreviously active BLC.

The status of shelfis reported by"Occam2", the

newly active BLC.

This is a normalmessage becauseonce the blades

begin the upgradethey do not allhave the same

software version.



The following examples show how the show shelf reload and show shelf command outputs look when the reload process has completed:

Occam2#show shelf reload

Upgrade status from previously active SC:





Rebooted slot 2Slot 2 back up.

Proceed with upgrade on new active SC


Shelf software:Slot 8 Version 5.3 V5_3T8Slot 12 Version 5.3 V5_3T8Slot 1 Version 5.3 V5_3T8Slot 2 Version V5.3T8

Auto upgrade pre-check state:IG's with links not redundant :All blades in the shelf do not have same software version

Rebooted slot 8Slot 8 back up.To upgrade slot 1 IG's: 1Rebooted slot 1Slot 1 back up.IG status on slot 1: IG's Redundant 1

Doing an app switchover on IG 1IG status on slot 1: IG's Redundant 1

To reboot new standby slot 12

Rebooted slot 12Occam2#

Slot 12 has beenrebooted.

Slot 1 is nowback up.

IG applications havebeen switched oversuccessfuly and are

redundant.



Shelf Reload

No current or queued actionsare listed.

Occam2#show shelfSystem (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

Slot Address Mode Type SW version Status---- ------- ---- ---- ---------- ------1 192.168.25.130 Card BLC_6640 V5.3T8 up2 192.168.25.131 Shelf BLC_6640 V5.3T8 up (local card)8 192.168.25.128 Shelf BLC_6640 V5.3T8 up12 192.168.25.129 Card BLC_6640 V5.3T8 upPending actions for Interface Group Manager: Current action: Queued actions: All BLCs have been reloaded

are are back up.




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability

Introduction

Chapter 30Configuring the BLC 6640-01 for TR-08 Mode 1 Interpretability

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629Configuring Network Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630Configuring T1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632TR-08 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635Configuring an Interface Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645Viewing Your CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

IntroductionThe 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.

Figure 30-1: Scenario for TR-08

TR-08 Mode 1The 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

RTRT

PSTNPSTN

TR-08(UP TO 4 DS1S

PER BLC)

CENTRALOFFICE

CLASS 5SWITCH

TRUNKVoIPMGCP

POTS

ADSL/POTS

NEXT GENSWITCH

REMOTETERMINAL

CENTRALOFFICE

TERMINAL

POTS

POTS

ADSL/POTSAND 2NDPOTS LINE


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 InterpretabilityConfiguring Network Clocking

situations where each MGCP endpoint has a dedicated DS0. A MGCP endpoint can be mapped to any DS0.


Port MappingThe T1s of the four TR-08 spans are designated A, B, C, D as follows:

T1 port 1 = A (primary) link

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.

Configuring Network ClockingNote: Network clocking must be done on each blade (cards and shelf controllers) in the shelf configuration.

Network Synchronization Protocol (NSP) is used to keep clocking synchronized between BLCs. NSP provides for several clock sources (called transmitters) that broadcast NSP information. BLCs that want to sync to a broadcast are called receivers, and can listen to a primary and a secondary transmission stream.

In a typical network configuration, one or more BLC 6640-01 or 6640-01 blades are configured as NSP transmitters and other BLCs in the network are configured as NSP receivers.

1 Enter Global Configuration mode:slot_1# configure terminalEnter configuration commands, one per line. End with CNTL/Z.



!



Configuring Network Clocking

4 Configure the BLC 6640-01s or 6640-01 blade as a NSP transmitter, specifying a broadcast number between one and thirty-two. One or more BLC 6640-01s or 6640-01 blades in the shelf can be NSP transmitters. Typically the two bookend BLCs (slot 1 and slot 12) are each NSP transmitters.:Occam(config)# nsp mode tx {1-32}

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.



7 Exit Global Configuration Mode and save your configuration:Occam(config)# exitOccam# copy running-config startup-configBuilding configuration....


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 InterpretabilityConfiguring T1 Interfaces

Configuring T1 InterfacesCaution: 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.

Configuring the Primary (A) T1 Interface


2 Enter Serial Interface Configuration Mode, specifying T1 interface port number one:Occam(config)# interface serial 1

3 Enable channelized mode: Occam(config-if-serial)# mode channelized

4 Specify SLC96 as the framing format: Occam(config-if-serial)# service-module t1 framing slc96

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


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

!



Configuring T1 Interfaces

Occam(config-if-serial)# service-module t1 alarm-mode {note |wp1 |wp1b}

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}

9 (Optional) Enable 16 or 32 bit Cyclic Redundancy Checks (CRC) for error-checking. This command is optional if you select 16-bit CRC, the factory default: Occam(config-if-serial)# crc {16 |32}

10 (Optional) Configure the line build-out. There is no default:Occam(config-if-serial)# service-module t1 lbo {-15 db | -7.5 db | none}

11 (Optional) Enable the BLC 6640-01 to generate and detect remote (yellow) alarms: Occam(config-if-serial)# service-module t1 remote-alarm-enable

12 (Optional) Configure the T1 to enter loopback mode when it receives a loopback code on the line.:Occam(config-if-serial)# service-module t1 remote-loopback {full | payload}

13 (Optional) Set the interface maximum transmission packet size or Maximum Transmission Unit (MTU) in bytes. The range is between 64 and 18000.

Note: Most installations do not need to change the default MTU value of 1524 bytes.Occam(config-if-serial)# mtu bytes


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>, '?', '!'.




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 InterpretabilityConfiguring T1 Interfaces

Configuring the Remaining T1 Interfaces


2 Enter Serial Interface Configuration Mode, specifying T1 interface port number two:Occam(config)# interface serial 2

3 Enable channelized mode: Occam(config-if-serial)# mode channelized

4 Specify that there is not a facility data link (fdl) standard:Occam(config-if-serial)# no service-module t1 fdl

5 Specify Super Frame as the framing format: Occam(config-if-serial)# service-module t1 framing sf

6 Specify the clock source as internal: Occam(config-if-serial)# service-module t1 clock source internal

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.



10 Repeat steps 2 through 8 from this section to configure T1 interfaces 3 and 4.

11 Exit Global Configuration Mode and save your configuration:Occam(config)# exitOccam# copy running-config startup-configBuilding configuration....



TR-08 Subscriber Profile

TR-08 Subscriber ProfileTo configure an interface group channel, you must first create one or more TR-08 subscriber profiles. These profiles are then attached to the appropriate channels.

There are virtually unlimited subscriber-voice-profiles allowed for the BLC 6640-01. Each subscriber-voice-profile must be named with a unique name.

Default Subscriber Profiles

There are two default subscriber profiles created on the BLC 6640-01. One, called "default" is pre-set for TR08 mode. The other, called "default-gr303" is pre-set for GR-303 mode. These profiles cannot be deleted but can be edited. If this is done, and the configuration is saved, the profiles will have the new values after a reload.

The initial values for this profile are shown below. Commands to change these defaults are shown in Table 30-1.Profile type: tdm-tr08Input Gain: 0 dBOutput Gain: 0 dBForward Disconnect: 900 millisecondsPacketization Period: 10 millisecondsJitter Delay: 20 millisecondsFax Delay: 0 millisecondsFax CNG Detect: disableFax CNG Timer: 0 secondsSignaling Type: slc96rt-spRtp Signaling Type: nuera2833Echo cancel: enableEcho tail length: 48 millisecondsEcho Tone Disabler: G.165Idle Channel Suppression: enableRtcp Missed Event: enableCodecs: g711ulaw MGCP Type: OccamCompliantModem Codec Bypass: enable


Feature Default Value

Command to Change Default Value

Input Gain Value- Specify the input gain value in decibels.

0 dB occam(config-profile)profile-name#input-gain {-12dB..12dB}

output-gain - Set the output gain, local adjustment in decibels.

0 occam(config-profile)profile-name# output-gain {-12, -11, ...11,12}


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 InterpretabilityTR-08 Subscriber Profile

forward disconnect - Set the amount of time in milliseconds before there will be an alert sent out after the removal of the battery signal.

900 milliseconds

occam(config-profile)profile-name# forward-disconnect {msec}

packetization period - Set the packetization period in milliseconds.

Note: Occam Networks recommends that the packetization period only be set to 5 ms. on ports that are used for modem/fax support:

10 milliseconds.

occam(config-profile)profile-name# packetization-period {msec}

jitter delay - Set the jitter buffer delay length in milliseconds (msec).The parameters are between 10 and 110 in five msec increments

20 ms occam(config-profile)profile-name# jitter-delay {msec}

fax delay - Set the fax jitter buffer delay length in msec. The parameters are between 0 and 210 in five msec increments

0 msec (disabled)

occam(config-profile)profile-name# fax-delay {msec}




fax cng detect- Most faxes send audible beep tones called CNG (CalliNG) tones. A CNG tone is a beep that repeats every three seconds. A fax gener-ates a CNG tone after it has dialed a destination fax’s number and is waiting for it to answer.Many of the latest fax machines (Super G3) generate 2100hz tone with phase reversal just as modems do. The fax CNG detector provides a way to distinguish between these fax machines and modems. The command fax-cng-detect may be used to enable or disable the fax CNG detector on the BLC.

Disabled occam(config-profile)profile-name# fax-cng-detect {enable, disable}

fax cng timer - Configures how long the fax CNG detector is enabled at the start of a call. The command specifies the amount of time the CNG detector is on in one second increments

0, No timer, fax CNG detector on at all times

occam(config-profile)profile-name# fax-cng-timer {0, 1....120}

Signaling Type - Specify slc96rt-sp as the signalling mode

slc96rt-sp occam(config-profile)profile-name# sig-type slc96rt-sp

RTP Signaling Type - Enable the Real-time Trans-port Protocol (RTP) Signaling Mode. Choose between:

nuera2833- Utilize Nuera RFC2833 RTP mode

cablelabs2833- Utilize Cable Labs RFC2833 RTP mode

NUERA2833 occam(config-profile)profile-name# rtp-sig-type (nuera2833,cablelabs2833}

echo-cancel - Enable echo cancellation

enabled occam(config-profile)profile-name# echo-cancel enable



echo tail length - Set the echo tail length in milliseconds

48 milliseconds


echo tone disabler-The echo-tone-disabler command may be config-ured to disable the echo canceller feature when a 2100 Hz tone is detected. The tone is used in both fax and modem protocols and it may or may not have phase reversal. Phase reversal is used to disable echo cancellation.

disable: Ignore 2100 Hz tone

G.164: Bypass echo cancellation on 2100 Hz tone detection

G.165: Bypass echo cancellation on 2100 Hz tone with phase reversal

G.165 occam(config-profile)profile-name# echo-tone {disabler, G.164, G.165}

Idle Channel Suppression(Not configurable)

Enabled N/A




rtcp-missed-event - Enable the BLC 6640-01 to accept Real Time Transport Control Protocol (RTCP) missed event messages. The mgcp-option rtcp-missed-event command is usually enabled, but doesn't have to be. This command may need to be disabled if the BLC is configured to send voice on a channel. If the DSP on the BLC misses 4 consecutive RTCP messages, it sends an event to the Trunking Gateway (TGW). If the mgcp-option rtcp-missed-event command is enabled, when the TGW receives that event, it will treat it as if the endpoint is unreachable, and will do the required steps to tear down the call (e.g., to prevent a call from being charged long distance when the connection has died). Some Integrated Access Devices (IADs) don't send out the RTCP as often as they should when mapping a channel.

Enabled occam(config-profile)profile-name# mgcp-option rtcp-missed-event {enable, disable}

Codec (Not configurable) g711ulaw N/A



mgcp-type - Select the corresponding MGCP type for remote endpoint. The options are to utilize:

Occam-compliant MGCP type mode (default)




Generic IAD MGCP type mode

Occam compliant

occam(config-profile)profile-name#mgcp-type {occamcompliant|wave7optics|innomedia|telcosystems|genericiad}

modem codec bypass - Set the modem codec bypass values

disable=No codec bypass

enable-Codec bypass follows echo tone disabler

Enabled occam(config-profile)profile-name# modem-codec-bypass {enable, disable}




Creating a TR-08 Subscriber Profile


2 Enter TR-08 Subscriber Profile Configuration Mode and configure a TR-08 subscriber profile. The prompt will change to occam(config-profile)<profileName>#:Occam(config)# subscriber-profile tdm tr08 {profile-name}

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

and the prompt would change to:Occam(config-profile)tr08-new#

3 Configure the TR-08 profile using the commands detailed in Table 30-1.

4 Exit TR-08 Subscriber Profile Configuration ModeOccam(config-profile)<profileName># exit




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 InterpretabilityConfiguring an Interface Group

Configuring an Interface GroupNote: The commands show alarms active and show alarms log display IG alarms. Please refer to Chapter 36, Alarms and Sensors on page 698 for information about these commands and the IG alarms that are displayed.


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}

3 Select the interface group mode to TR-08 mode 1 (unconcentrated) operation. Select between D1D (d1d) or D4 (d4) channel to timeslot mapping mode:Occam(interface-group)# mode tr08mode1 {d1d | d4}



{1-8} specifies the physical T1 interface number.Occam(interface-group-tr08)ig-number# assign serial {1-4} {1-8} {secondary}

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:


Use the channel command to configure a channel number:

Occam(interface-group-tr08)ig-number# channel {1-96}

For example, if you are configuring channel 1 the command is:Occam(interface-group-tr08)ig-number# channel 1

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




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/[email protected]”, the command is:Occam(config-interface-group-channel)/ch-1# endpoint phone/[email protected]

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/[email protected]”, the command is:Occam(config-interface-group-channel)/chs-1-5# endpoint-start phone/[email protected]







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


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 InterpretabilityConfiguring an Interface Group

9 (Optional) Attach a description to the channel (for example "Associated with 480-555-1001 on the LDS)":Occam(config-interface-group-channel)/chs-number-number# description text

10 Exit RT Channel Configuration Mode:Occam(config-interface-group-channel)/chs-number-number# exit

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.

12 Enable the Interface Group:Occam(interface-group-tr08)ig-number# no shutdown

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

14 (Optional) Enable the periodic-audit command to cause the IG to periodically audit all its endpoints by sending out an MGCP AuditEndpoint message. The IG does this to proactively ensure that the endpoints are reachable and are working properly. This feature is enabled by default.Occam(interface-group-tr08)ig-number# periodic-audit {enable | disable}

15 Exit Interface Group Configuration Mode:Occam(interface-group-tr08)ig-number# exit





Viewing Your Configuration

Viewing Your ConfigurationThe following commands may be used from User and Privileged Configuration modes to view your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide.

show interface-group [IG number] [first channel number] [last channel number]: use this command to view information about an IG configuration. You may this command to verify that the mode is correct, that the T1 lines in the IG are configured correctly, and that the channels are correctly configured. This command may be configured to display information about all IGs configured on the BLC, a specific IG or a specific range of channels on a specified IG.

show interface-group endpoint {MGCP endpoint-name}: use this command to view to which IG/CRV an endpoint is mapped. An example of an MGCP endpoint-name is “phone/[email protected]”.

show interface-group statistics {ig-number}: use this command from to view statistical information about an interface group.

show interface-group summary: use this command to view information about IG configurations. The output is sorted by serial interface numbers.

show subscriber-profile {profile-name}: use this command to verify that a configured profile has the correct settings


Viewing Your CPU UsageThe command debug cpu may be used from Privileged mode to display CPU utilization for a specified number of seconds. The parameters are from 0 to 100 seconds.

The following example displays CPU usage for two seconds:Occam# debug cpu 2CPU states: 27.6% user, 16.7% system, 0.0% nice, 55.7% idleCPU states: 0.0% user, 8.0% system, 0.0% nice, 92.0% idleCPU states: 0.0% user, 9.0% system, 0.0% nice, 91.0% idleCPU states: 0.0% user, 3.0% system, 0.0% nice, 97.0% idleCPU states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idleCPU states: 0.0% user, 6.5% system, 0.0% nice, 93.5% idleCPU states: 0.0% user, 2.0% system, 0.0% nice, 98.0% idle


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 30: Configuring the BLC 6640-01 for TR-08 Mode 1 InterpretabilityViewing Your CPU Usage


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01

Introduction

Chapter 31Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647Configuring a T1 Interface for TR-08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652Configuring POTS Channel Bank Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654Configuring a Voice Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662Displaying Voice Port and Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

IntroductionThe 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.

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.

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.

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01Introduction

This chapter contains configuration steps that show:

How to configure a T1 interface for TR08 (page 652)

How to configure a POTS channel bank profile (page 654)

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 FeaturesThe following POTS features are supported when the BLC 6246 and BLC 6150-01 are configured to use TDM:

Distinctive Ringing: No user interface is needed for distinctive ringing on the BLC. This feature is enabled/disabled at the call agent or at the switch. The BLC 6246 and BLC 6150-01 support up to four distinctive rings.

Caller ID: No user interface is needed for Caller ID. Only the FSK transmission standard specified by [GR-303] is supported.

Three-Way Calling: No user interface is needed for three-way calling on the BLC 6246 and BLC 6150-01. This feature is enabled/disabled at the call agent. Three-Way Calling (TWC) is a non-Centrex custom-calling feature that allows one to add a third party to an existing telephone conversation without operator assistance. The party initiating TWC by a flash may hold one party with privacy exclusion while dialing and talking with another party and can later include the held party in TWC. The added party may be dropped from the connection by a flash from the initiating party.

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.



Introduction

TR-08 for TDM VoiceSupport for TR-08 Mode 1 signaling enables the BLC 6246 and BLC 6150-01 to interoperate with a wide variety of existing Local Digital Switches (LDS).

TR-08 carries three types of information:

Voice Traffic: Digitized voice traffic and other audio information (dialtone, ringback tone, DTMF tone, etc.) for each POTS line.

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.

Channel Associated SignalingThe BLC 6246 and BLC 6150-01 support TR-08 signaling over a single T1 interface, acting as a channel bank by directly mapping all POTS interfaces through one T1 line to the Central Office. A channel bank changes analog voice and data signals into a digital format. A T1 circuit is made up of 24 channels.

When configured as a channel bank, the BLC 6246 and BLC 6150-01 use Channel Associated Signaling (CAS). CAS signaling is also known as Robbed Bit Signaling (RBS), because it steals bits from the channel data and uses them to represent the supervision status of the channel.

FXS and SLC 96 Channel Associated Signaling

The BLC 6246 and BLC 6150-01 Voice Channel Bank Mode supports 2 types of CAS:

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.

D4 and D1D Channel Numbering

The BLC 6246 and BLC 6150-01 map channels to specific timeslots based on the remote terminal (RT) channel mapping modes and inversely maps timeslots to channels. Each T1(DS1) line in the BLC’s TR-08 interface supports both D4 and D1D channel numbering. (D1D is a retrofit of D1 channel banks with D2 capability.)

The channel mapping mode is set through configuration of the T1 interface with the command service-module t1 channel-mapping{d1d | d4} command in Serial Interface Configuration Mode.

Table 31-1 illustrates the RT channel number to timeslot mapping for both D1D and D4 modes.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01Introduction

Table 31-1: RT Channel Number to Timeslot Mapping for D1D and D4 Modes

RT Channel Number

Timeslot 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



Introduction

Port MappingThe T1s of the four TR-08 spans are designated A, B, C, D as follows:

T1 port 1 = A (primary) link

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).


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01Configuring a T1 Interface for TR-08

Configuring a T1 Interface for TR-08Use the following steps to enable TR-08 on the BLC 6246 and BLC 6150-01. Table 31-2 shows the factory default configurations for T1 lines that specifically affect TR-08 functionality. You may also need to enter other configuration commands, depending on your network configuration.

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.

Table 31-2: Default T1 Configuration

1 Enter Privileged Mode:Occam> enablePassword: razorOccam#


3 Enter Serial Interface Configuration Mode, specifying any T1 interface number between one and four. Only one of the T1 interfaces is used for TR-08:Occam(config)# interface serial {1-4}

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


Command used to Modify Default Value

T1 facility data link(fdl) mode

AT&T TR54016 (att)

Occam(config-if-serial)# service-module t1 fdl {ansi | att | both | slc96-rt}

T1 framing type

Extended Super Frame (esf)

Occam(config-if-serial)# service-module t1 framing {esf | sf | slc96}

Robbed-bit signaling

Not enabled Occam(config-if-serial)# mode channelized

Channel mapping

D1D Occam(config-if-serial)# service-module t1 channel-mapping {d1d |d4}

!



Configuring a T1 Interface for TR-08

7 Enter the framing type, or subscriber loop carrier, 96 lines (slc96): Occam(config-if-serial)# service-module t1 framing slc96

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}


For example:Occam(config-if-serial)# info cross-connect-mode TR08

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>, '?', '!'.

10 Enable the serial interface:Occam(config-if-serial)# no shutdown

11 Exit Serial Interface Mode: Occam(config-if-serial)# exit




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01Configuring POTS Channel Bank Profiles

Configuring POTS Channel Bank ProfilesBefore you configure a voice port you must first create a POTS channel bank profile to attach to it. A POTS channel bank profile includes parameters (connection mode, signaling-type, etc.) and the serial interface (T1) to which the voice ports will be assigned. When a parameter in a profile is changed, the value of that parameter on all ports attached to that profile is also changed.

If an existing profile is modified, that change takes effect on every voice port linked to that profile. To change a single port or a subset of ports, copy the profile, change the desired parameters, and then assign the new profile to the desired ports. There can be one profile for many ports, but one port cannot have more than one profile.

A virtually unlimited number of profiles are allowed for the BLC 6246 and BLC 6150-01. Profiles are maintained in memory so that the profiles can be assigned to voice-ports when needed.

Default Voice Port Profile on the BLC 6246 and BLC 6150-01All 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:



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



Pots Channel Bank Profile Configuration Steps


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

and the prompt would change to:Occam(config-profile)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}

4 Configure a profile by using the commands shown below:


Input Gain Value:Set the decimal amount of input gain. The parameters are -12 dB to +12dB in one dB increments. The default is 0 dB.


Output Gain Value:Sets the local adjustment, in decibels.Set the decimal amount of output gain (attenuation). The parameters are -12 dB to +12dB in one dB increments. The default is 0 dB.

occam(config-profile)voice-profile-name# output {-12,-11,..,11,12}




Forward Disconnect:Specifies in milliseconds the amount of time the battery is removed to alert the remote end disconnect. At the end of a call, when the far end hangs up, the forward disconnect signal is applied to the line to inform the local user that the remote has disconnected. The default value is 900 milliseconds


Fax Delay:Specifies fax jitter buffer delay in five msec increments


Fax CNG Detector:Enables or disables the fax CNG (CalliNG) tones detector.This feature is disabled by factory default.

occam(config-profile)profile-name#fax-cng-detect {enable, disable}

Fax CNG Timer:Specifies the number of seconds the CNG detector is enabled at the start of a call. The factory default is 0 seconds.


Signaling Type:Selects the signaling type, choosing between foreign exchange station (fxs) and SLC-96 remote terminal single party (slc96rt-sp) mode.The factory default is slc96rt-sp.

occam(config-profile)profile-name# sig-type {fxs, slc96rt-sp}

RTP Signaling Type:Select Real-time Transport Protocol (RTP) Signaling Mode as “none”. This command has no other options in t

occam(config-profile)profile-name# rtp-sig-type none







Echo Tone Disabler.Configures the voice port with one of the following parameters:disable - Ignore 2100 Hz toneG.164 - Bypass echo cancellation on 2100 Hz tone detectionG.165 - Bypass echo cancellation on 2100 Hz tone with phase reversal. This is the factory default.


Connection Mode:Set the POTS port to T1 control. The T1 interface that you select must be the same one that was configured earlier in the sectionConfiguring a T1 Interface for TR-08. The factory default is interface 1 in slot 1 of the shelf.

Occam(config-profile) profileName # connect pots-t1 {1-4}

Idle Channel Suppression: This feature is enabled by factory default and is not configurable.

N/A

Receive level:Set the receive level on a voice-port in decibels. The default value is -3.0 dB.


Transmit Level:Sets the transmit level on a voice-port in decibels. The default value is -3.0 dB

occam(config-profile)profile-name# transmit-level {-15, -14.9,-14.8,..,+9.8, +9.9,+10}




Codec-list: Preferred coder-decoders (codecs) used during call compression. The order entered determines the priority order of the codecs.



g726-32k: ADPCM 32k dynamic payload type. This codec is described in RFC 3551. This algorithm compresses voice from 64 kbps to 32 kbps. It supports dynamic packet types and may be used with the Coppercom softswitch.The default values for this codec are:Jitter Delay: 40msPacketization: 20ms

NOTE: In this release you may only configure the g721 OR g726-32k codec on a profile because the g721 codec supports fixed packet type 2 and the g726-32k codec supports dynamic packet types. You may not configure both. The g711ulaw will always be on the codec list, even if it is not entered.Upon detection of a fax CED or CNG tone the algorithm will automatically switch from g.726/g.721 to g.711.Three way calling is not supported with the g721 and g726 codecs unless the soft-switch does the mixing.




Codec-Options:

Configures the jitter delay and packetiza-tion options for codecs.


Jitter Delay:



Packetization: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.




enabled - Modem codec bypass func-tions are configured to follow the settings of the echo-tone-disabler command.










6 Repeat steps 2 through 10 for each profile you wish to configure



8 Continue on to the sectionConfiguring a Voice Port.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01Configuring a Voice Port

Configuring a Voice Port 1 Enter Global Configuration Mode:


2 Enter Voice Configuration Mode and specify the voice port number you want to configure:Occam(config)# voice-port voice-port-number

3 Select a profile by name to attach to the voice port:

Occam(config-voice)# attach profile profile-name

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

6 (Optional) Attach informational text to the voice port:Occam(config-voice)# info key informative-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>, '?', '!'.

7 Exit to Global Configuration Mode:Occam(config-profile)# exit

8 Repeat steps 2 through 6 for each port to which you wish to attach a profile.






Configuring Unbalanced Ringing on a Voice Port

Unbalanced Ringing provides a ringing signal compatible with most applications where the POTS subscriber line traverses a remote DLC. Unbalanced Ringing is disabled by default.



3 Enable unbalanced ringing on the voice port:Occam(config-voice)# unbalanced-ring

Use the no form of the command to disable this feature:Occam(config-voice)# no unbalanced-ring



Configuring Maximum Balanced Ringing on a Voice PortNormal balanced ring is approximately 80V rms Tip to Ring. Maximum balanced ring is approximately 108V rms Tip to Ring. To achieve this the driver is pushed into saturation, thus creating a square wave. Normal ringing is a sine wave.

Square wave ringing does not meet the TR-57 specification. Therefore the max-balanced-ring command should not be used unless the normal balanced ring is not sufficient for the application (e.g. DLC or long loop). This feature is disabled by default.



3 Enable unbalanced ringing on the voice port:Occam(config-voice)# max-balanced-ring


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01Configuring a Voice Port

Use the no form of the command to disable this feature:Occam(config-voice)# no max-balanced-ring


5 Save your configuration:Occam# copy running-config startup-config



Displaying Voice Port and Profile Information

Displaying Voice Port and Profile Information The following commands may be used to view your configuration. Sample output from the commands described below may be found in the Occam Networks publication Command Reference Guide.

show voice: displays DSP status and voice port configuration.

show voice dsp: displays the current status of all digital signal processor (DSP) voice channels.

show voice port {port-number}: use this command to display configuration information about a specific voice port.

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.



show voice list-of-profiles: use this command to display the names of existing voice profiles.



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 31: Configuring TR-08 for TDM Voice on the BLC 6246 and BLC 6150-01Displaying Voice Port and Profile Information


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling

(CAS) Mode on the BLC 6640-01

Chapter 32Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling (CAS) Mode on the BLC 6640-01

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667Configuring T1 Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667Configuring Network Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669Subscriber Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670Configuring an Interface Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673Viewing Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676

IntroductionThe 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 LinesCaution: 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).


2 Enter Serial Interface Configuration Mode, specifying a T1 interface port number between one and eight:Occam(config)# interface serial {1-8}

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 32: Configuring Foreign Exchange Station (FXS)/ Channel Associated Signaling (CAS) Mode on the BLC 6640-01

3 Remove ANSI T1.403, AT&T TR54016 functionality (enabled by factory default) on the facility data link (FDL) mode: Occam(config-if-serial)# no service-module t1 fdl

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}

7 Enable channelized mode:Occam(config-if-serial)# mode channelized


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.






Configuring Network ClockingNetwork Synchronization Protocol (NSP) is used to keep clocking synchronized between BLCs. NSP provides for several clock sources (called transmitters) that broadcast NSP information. BLCs that want to sync to a broadcast are called receivers, and can listen to a primary and a secondary transmission stream.

In a typical network configuration, one or more BLC 6640-01s are configured as NSP transmitters and BLCs are configured as NSP receivers.




4 Configure the BLC 6640-01 as a NPS transmitter, specifying a broadcast number between one and thirty-two:Occam(config)# nsp mode tx {1-32}







Subscriber ProfilesTo 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.

Default Subscriber Profiles

There are two default subscriber profiles created on the BLC 6640-01s. One, called "default" is pre-set for TR08 mode. The other, called "default-gr303" is pre-set for GR-303 mode. When configuring a BLC 6640-01 for FXS interoperability, you must either create a new subscriber-profile, or modify the "default" subscriber profile.



Profile Name default

Signaling Mode FXS

RTP Signaling Type NUERA2833

Signaling Type slc96rt-sp

Preferred coder-decoders (codec) used during call compression

g711ulaw

input-gain 0

output-gain 0

echo-cancel disabled

echo tail length 64

forward disconnect 900

jitter delay 35

fax jitter buffer delay length 0

packetization period 10

mgcp-type Occam compliant

mgcp-option rtcp-missed-event enabled




Configuring a Subscriber ProfileTo configure a FXS subscriber profile use the following configuration steps:


2 Configure a subscriber profile by choosing a new name or using the “default” profile and modifying it:Occam(config)# subscriber-profile tdm tr08 {profile-name}

The prompt will change to:Occam(config-profile)<profileName>#

For example, if a subscriber profile with the name “fxsnew” is being configured, the command is:Occam(config)# subscriber-profile tdm tr08 fxsnew

The prompt will change to:Occam(config-profile) <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

4 Specify FXS as the signalling mode:

Occam(config-profile) <profileName># sig-type fxs

5 Enable the BLC 6640-01 to accept RTCP missed event messages.

Note: The mgcp-option rtcp-missed-event command is usually enabled, but doesn't have to be. This feature may need to be disabled if the BLC 6640-01 is configured to send voice on a channel. If the DSP on the BLC 6640-01 misses four consecutive RTCP messages, it sends an event to TGW. If the mgcp-option rtcp-missed-event command is enabled, when TGW receives that event, it will treat it as if the endpoint is unreachable, and will do the required steps to tear down the call (e.g., to prevent a call from being charged long distance when the connection has died). Some IADs don't send out the RTCP as often as they should when mapping a channel:Occam(config-profile)<profileName># mgcp-option rtcp-missed-event {enable, disable}

6 (Optional) Specify the input gain value in decibels. The default is 0:

Occam(config-profile)<profileName># input-gain {-12, -11,...11,12}

7 (Optional) Set the output gain, local adjustment in decibels. The default is 0:

Occam(config-profile)<profileName># output-gain {-12,-11,...11,12}



8 (Optional) Enable echo cancellation (factory default):Occam(config-profile)<profileName># echo-cancel enable

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}

13 (Optional) Set the packetization period in milliseconds. The default is 10 milliseconds:Occam(config-profile)<profileName># packetization-period {10|20}

14 (Optional) Select the corresponding MGCP type for remote endpoint. The options are to utilize:

Occam-compliant MGCP type mode (default)




Generic IAD MGCP type modeOccam(config-profile)<profileName># mgcp-type {occamcompliant|wave7optics|innomedia|telcosystems|genericiad}

15 Exit GR-303 Subscriber Profile Configuration Mode and return to Global Configuration Mode:Occam(config-profile)<profileName># exit






Configuring an Interface GroupNote: The commands show alarms active and show alarms log display IG alarms. Please refer to Chapter 36, Alarms and Sensors on page 698 for information about these commands and the IG alarms that are displayed.


2 Configure an interface group, choosing a number between one and two.Occam(config)# interface-group {1-2}

3 Configure the interface group mode as cross-connect

Note: The prompt is (config-interface-group-tr08) because TR-08 is the factory default interface-group mode. This will change to (config-interface-group-cross-connect) in the next step. Select D1D or D4 channel to timeslot mapping mode. The factory default is D4 channel to timeslot mapping mode:Occam((config-interface-group-tr08)# mode cross-connect {d1d | d4}



{1-8} specifies the physical T1 interface number.Occam(config-interface-group-cross-connect)# assign serial {1-8} {1-8} {ip-address}

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:


Use the channel command to configure a channel number:Occam(config-interface-group-cross-connect-channel)# channel {1-192}

For example, if you are configuring channel 1 the command is:Occam(config-interface-group-cross-connect-channel)# channel 1

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-192} {1-192}

For example, if you are configuring channels 1 through 5, the command is:Occam(config-interface-group-cross-connect-channel)# channels 1 5

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/[email protected]”, the command is:Occam(config-interface-group-cross-connect-channel)# endpoint phone/[email protected]

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/[email protected]”, the command is:Occam(config-interface-group-cross-connect-channel)# endpoint phone/[email protected]










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

9 (Optional) Attach a description to the channel or channels (for example "Asso-ciated with 480-555-1001 on the LDS)":Occam(config-interface-group-cross-connect-channel)# description text

10 Exit RT Channel Configuration Mode:Occam(config-interface-group-cross-connect-channel)# exit

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.

12 Enable the Interface Group:Occam(config-interface-group-cross-connect)# no shutdown

13 Exit Interface Group Configuration Mode:Occam(config-interface-group)# exit







show interface-group endpoint {MGCP endpoint-name}: use this command to view to which IG/CRV an endpoint is mapped. An example of an MGCP endpoint-name is “phone/[email protected]”

show interface-group statistics {ig-number}: use this command from to view statistical information about an interface group

show interface-group summary: use this command to view information about IG configurations. The output is sorted by serial interface numbers

show subscriber-profile {profile-name}: use this command to verify that a configured profile has the correct settings


show shelf: use this command to display the status of the system in shelf topology.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 33: Differentiated Services (Diffserv)

Introduction

Chapter 33Differentiated Services (Diffserv)

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677Flow Classifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678Queue/Schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678Configuring IP Diffserv DSCP Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679Configuring 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 ClassificationsUntagged 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 33: Differentiated Services (Diffserv)Markers

Packets that exit the kernel 802.1q tagged derive the 802.1p user priority from the DSCP mapped priority.

802.1Q Tagged Classification Packets that are received 802.1q tagged are always classified based on the value of the 802.1p user priority. It is expected that the user priority has been correctly determined based on the packet payload (i.e., either from the packets DSCP or other packet information) at the entry point to the tagged network.

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/SchedulersThe 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.

DSCP PRIORITY

802.1p PRIORITY

QUEUE

1 7 1

2 6 2

3 5 3

4 4 4

5 3 5

6 2 6

7 1 7

8 0 8



Configuring IP Diffserv DSCP Protocol

Configuring IP Diffserv DSCP ProtocolUse the ip diffserv dscp protocol commands from Global Configuration mode to configure a local protocol application’s DSCP value for packets that it generates. The command has no effect on packets that the protocol application receives from peer applications and takes effect immediately.

ExampleIn this example the MGCP protocol application is configured to use the DSCP value of 32 for packets that it generates:occam# configure terminaloccam(config)# ip diffserv dscp protocol mgcp 32

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


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 33: Differentiated Services (Diffserv)Configuring IP Diffserv DSCP Protocol

Displaying the Protocol Application DSCP TableUse the show ip diffserv dscp protocol command from Enable Mode to display the local protocol applications DSCP value for packets that the protocol generates.

This example shows sample output from this command: occam# show ip diffserv dscp protocolProtocol DSCPMGCP 46RTP 46IGMP 56Default 18



Configuring IP Diffserv DSCP Mapping

Configuring IP Diffserv DSCP MappingUse the Global Configuration Mode command ip diffserv dscp map to configure the associated priority of a DSCP value when encountered in the IP protocol header of a packet. This priority is then used within the system to determine relative queuing priority as well as the 802.1p user priority if the packet should exit the system 802.1q tagged. This command takes effect immediately.occam (config)# ip diffserv dscp map {dscp value} {priority value}

ExampleIn 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 terminaloccam(config)# ip diffserv dscp map 32 priority 1

Displaying the DSCP to Priority Mapping TableUse the show ip diffserv dscp map command from Enable or Privileged Mode to display the DSCP to priority mapping table.

This example shows sample output from this command: occam# show ip diffserv dscp mapDSCP Prio DSCP Prio DSCP Prio DSCP Prio 0 8 1 8 2 8 3 8 4 3 5 8 6 8 7 8 8 7 9 8 10 7 11 8 12 7 13 8 14 7 15 8 16 7 17 8 18 6 19 8 20 6 21 8 22 6 23 8 24 7 25 8 26 5 27 8 28 5 29 8 30 5 31 8 32 7 33 8 34 4 35 8 36 4 37 8 38 4 39 8 40 7 41 8 42 8 43 8 44 8 45 8 46 2 47 8 48 7 49 8 50 8 51 8 52 8 53 8 54 8 55 8 56 1 57 8 58 8 59 8 60 8 61 8 62 8 63 8

Parameter Description

dscp value Value from 0 through 63

priority value Priority value between 1 (highest) and 8


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 33: Differentiated Services (Diffserv)Configuring IP Diffserv DSCP Mapping


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 34: Power Save Mode

Introduction

Chapter 34Power Save Mode

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683Enabling and Disabling Power Save Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683Configuring Power Save Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684Viewing Power Save Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686

IntroductionThe 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).

Enabling and Disabling Power Save ModeThe power save mode is disabled by default on the BLC.

To enable power save mode use the command power save from Global Configuration Mode:Occam(config)# power save

To disable power save mode use the command no power save from Global Configuration Mode:Occam# no power save

.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 34: Power Save ModeConfiguring Power Save Mode

Configuring Power Save ModeDuring a power outage the DSL modems are turned off to preserve battery life. The BLC detects that AC power has cut out and batteries are powering the system by monitoring the voltage of the input power line. When AC is powering the system, the voltage is approximately -54V. If AC power is cut off and batteries begin to charge the RT, the voltage drops to approximately -46.77V. When the BLC is in power save mode, this input voltage power drop causes the DSL modems to be turned off. When input voltage is restored to -50.7V the DSL modems are turned back on. The input threshold and “restoration” voltages are configurable by using the power save ac off threshold and the power save ac on threshold commands.

Configuring the Bottom Threshold Input VoltageUse the power save off threshold command from Global Configuration Mode to configure a new input voltage that the BLC will use to consider AC power interrupted on the RT. Select a voltage between the range of -38 to -55V.Occam(config)# power save ac off threshold {-38 to -55}

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 voltageOccam(config)# no power save ac off threshold

Configuring the Power Save TimerUse the power save ac off ac timer command from Global Configuration Mode to configure a time delay between the loss of AC power and the commencement of power save mode. Select a period in time between zero and 180 minutes. The factory default is 15 minutes:Occam(config)# power save ac off timer {0 to 180}

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


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 34: Power Save ModeConfiguring Power Save Mode

Configuring the Input Voltage When AC Power Is Considered RestoredUse the power save ac on threshold command from Privileged Mode to configure a new threshold voltage that the BLC will use to consider AC power restored to the RT. Select an new “restoration” voltage between the range of -38 to -55V.

Note: The AC On threshold must be less than AC Off threshold.Occam(config)# power save ac on threshold {-38 to -55}

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 voltageOccam(config)# no power save ac on threshold


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 34: Power Save ModeViewing Power Save Settings

Viewing Power Save SettingsUse the show power save command from User or Privileged Mode to view the power save settings and the current power states of the system. This example shows sample output from the command:Occam# show power save

Power Save Configuration:

Ac is On - Normal battery charging input - will drop to 'Ac is Off' state when Vin is below -45.0 V (use 'power save ac off threshold' to adjust this level) - Data Modem is turned ON

Ac is Off - Standby battery input - will restore to 'Ac is On' state when Vin is above -45.0 V (use 'power save ac on threshold' to adjust this level) - Data Modem is turned OFF

Current Power States:

Ac is On - Normal battery charging input PowerSave Disabled Vin 0.0 Temperature 0.0

Data modems are ON Fan Mode is Slow 0 outage(s) since bootOccam#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 35: Blade to Blade Communication (SSH From CLI)

Introduction

Chapter 35Blade to Blade Communication (SSH From CLI)

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687Configuring Blade to Blade Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688Deleting a Specified Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689Viewing Public Keys Associated With a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

IntroductionThe 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.

Public Key Authentication

SSH provides secure encrypted communications between two untrusted hosts over an insecure network. This is accomplished through the use of public key authentication.

Public Key Authentication is based on Public Key encryption. SSH software features two encryption keys: a public key and a private key. Messages that are encrypted with the private key can only be decrypted by the public key, and vice-versa. The private key is kept on the local device (in this case, the local BLC) and the public key is put in a list of authorized hosts on the remote device (BLC). When you attempt to log into the remote BLC, it returns a brief message, encrypted with your public key. If the local BLC can decrypt the message and send back proof to the remote BLC that it has done so, the remote BLC knows that the local BLC has the private key and permits communication between them.

SSH clients such as SecureCRT and puTTY include key generators that generate pairs of public and private keys.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 35: Blade to Blade Communication (SSH From CLI)Configuring Blade to Blade Communication

Configuring Blade to Blade CommunicationWhen a SSH connection from one peer (blade) to another is attempted, the address of the public key of the connected is checked in a "known hosts" file that resides on the connectors system. If the host is not known, the user is prompted with a "yes/no" to accept the connectee's key. Once accepted, the key is stored in the known hosts file, that typically resides in the file $HOME/.ssh/known_hosts.

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.

The parameter “username” is optional. If a username is not provided, the user-name “cli” will be used.

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)? yesWarning: Permanently added ‘123.456.7.89’ (RSA) to the list of known [email protected]'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:[email protected]'s password:


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 35: Blade to Blade Communication (SSH From CLI)

Deleting a Specified Host

Deleting a Specified HostIf a BLC is replaced in the field, it will render a new public key for a known host and the authentication challenge of the formerly known host will fail. The previous BLC’s public key must be removed from the list of known hosts and a new SSH connection must be initiated with the ssh command.

To delete a specified host from a list of known hosts, enter the following command from Privileged Mode:

clear ssh key {host}

For the parameter “host”, put the IP address or hostname of the blade to which you want to connect.

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

Viewing Public Keys Associated With a HostTo display the public key associated with a host, enter the following command from Privileged Mode:

show ssh key [host]

For the optional parameter “host”, specify the IP address or hostname of the blade you want to view. If no host is specified, all host entries will be displayed.

Example

To display the public key associated with hostname “ces6”, use the command:occam# show ssh key ces6ces6,192.168.12.46 ssh-dssAAAAB3NzaC1kc3MAAABBAKBIZw9gDayvwNBfcMS/bRQZQX89wEaczHRU4sm2MI0nuoOYJ17QafKVx/SV+58JBzSDfh8LPa1QRb7uuLKI5l0AAAAVAI/6MxQBzZ3IA+85YtPp0MJ53VYrAAAAQA2ianasaAVTgyAinLnq8twmSD001aMj4a4YLNVj4oxX7mPzEm883qN5XzLm0xudBhQbj1vO0Bf8SnXos9A7fuIAAABAczk1badR+N8abitWFmU01leaAtTQJWHSCzgzsjEq1pCyxxCQobEBhxjnBR8NAEyGfYuNgFPqt2INBcJ7d1p0MA==ces1#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 35: Blade to Blade Communication (SSH From CLI)Viewing Public Keys Associated With a Host


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and Sensors

Introduction

Chapter 36Alarms and Sensors

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691Environment Alarm In and Out Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692Configuring Power Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696Displaying Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698Clearing Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699Displaying Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700Alarms Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703Index of Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732

IntroductionThere 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsEnvironment Alarm In and Out Commands

Environment Alarm In and Out CommandsThere are two alarm functions on the BLC family of products: alarm in and alarm out. These alarm functions are controlled by the commands environment alarm in and environment alarm out, as described below.

Alarm In FunctionAlarm 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 no voltage potential applied and the circuit is incomplete:occam(config)# environment alarm in normal

Be in alarm when there is a voltage potential applied that completes the circuit:occam(config)# environment alarm in invert

Table 36-1: Environment Alarm Status

You can also use the environment alarm in description command to write

Alarm In CLI Command Alarm (CLI status) Circuit

environment alarm in ignore N/A N/A

environment alarm in normal Active Incomplete

environment alarm in normal Inactive Complete

environment alarm in invert Inactive Incomplete

environment alarm in invert Active Complete



Environment Alarm In and Out Commands

descriptive text for this alarm:occam(config)# environment alarm in description

Alarm Out FunctionAlarm out is generated by a major alarm on the BLC. Any major alarm on the BLC will cause an alarm out (for example T1 failure, EPS ring failure, voltage failure, etc. as well as an alarm in). The alarm out can be used, for example, to sound a horn or set off a light.

There are two different alarm out relays that you can choose from: normally open (NO) and normally closed (NC). NO is normally open when not in alarm. The NC is normally closed when not in alarm. The NO and NC are connected. So if NO closes, NC opens and vice versa. You can use either alarm out relay, depending on what you are hooking your alarm out to. There is also an alarm LED that is set when an alarm is generated.

Tables 21-2 and 21-3 describe what happens to the relay and LED for both NO and NC.

Table 36-2: NO Alarm Relay Status

Table 36-3: NC Alarm Relay Status

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.

Alarm Normally Open (NO) LED

Active Closed On

Cleared Open Off

Alarm Normally Closed (NC) LED

Active Open On

Cleared Closed Off


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsEnvironment Alarm In and Out Commands

Alarm Closure Feature

Note: Please refer to the publication OccamView User Guide for more information about OccamView and how to configure alarm filters

OccamView supports the mapping of alarm notifications received at BLCs in RTs to a BLC in the CO. These alarm notifications can be configured to cause an audible or visual alarm, such as a ringing bell or a flashing warning light, depending on the configuration of the CO BLC. Two BLCs (primary and secondary) may be configured to be notified of remote BLC alarms. When the alarm event that caused the Alarm Out Indicator to be turned on returns to normal conditions, the Alarm Out Indicator can be returned to "normal" by acknowledging the Alarm condition.

This acknowledgement can take place in one of two ways:

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

REMOTE TERMINAL

REMOTE TERMINAL

EMS

CENTRAL OFFICE

PRIMARY BLC

SECONDARY BLC

REMOTE TERMINAL



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.


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).


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsConfiguring Power Alarms

Configuring Power AlarmsThe power connection on the rear panel of the BLC 6001 and the BLC 6012 chassis have A and B inputs and returns as shown in Figures 36-2 and 36-3.

Figure 36-2: BLC 6252 Power Connection

Figure 36-3: BLC 6012 Chassis Power Connection

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.


environment alarm voltage input a ignore The alarm indicator for A power is disabled.

environment alarm voltage input a normal The alarm indicator for A power is enabled.



Configuring Power Alarms

environment alarm voltage input bignore

The alarm indicator for B power is disabled.

environment alarm voltage input b normal The alarm indicator for B power is enabled.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsDisplaying Alarms

Displaying AlarmsThe 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.

Viewing Active AlarmsThe show alarms active {latest | earliest} command shows the active alarms. You may optionally choose to display the latest or earliest alarm first. The factory default is to display the latest alarm first.

Each alarm is characterized by the following attributes:

Index Identifier: a unique number assigned to this alarm

Severity code: Critical, Major, Minor

Severity category: Service Affecting (SA), Non Service Affecting(NSA)


Created Timestamp: when the alarm was created


Description: a text describing the alarm, containing the origin of the alarm and what the alarm is about.

The following example shows sample output for this command:occam# show alarms activeIndex Severity SA Created Description 1 Major - 1970/01/01 00:01:22 Voltage Sensor [#B Vin -48V]:HighLimitExceeded

Viewing All AlarmsAn Alarm Log is kept for inspection by network management applications and Network Management Personnel. The show alarms log {latest | earliest} command displays all alarms, both active and cleared. A maximum of 100 cleared alarms is kept in the log. You may choose to display the latest or earliest alarm first. The factory default is to display the latest alarm first.

The characteristics of the alarms listed in the output from the show alarms log command are the same as for the show alarms active command, described above.

The following example shows sample output for this command:occam# show alarms logIndex Severity SA Created Cleared Description 1 Major - 1970/01/01 00:01:22 Voltage Sensor [#B Vin -48V]:HighLimitExceeded



Clearing Alarms

Viewing Alarms in a Summarized FormatThe command show alarms summary gives a short summary of the configura-tion of the alarm modes and a count of active alarms:occam# show alarms summaryAlarm in mode: ignoreAlarm out mode: allVoltage input A mode: ignoreVoltage input B mode: normal

Active alarms: 0 critical, 0 major, 0 minoroccam#

Clearing AlarmsClearing the Alarm Indicator

Use the clear alarm indicator command to clear the external alarm indicator:occam# clear alarm indicator

Clearing Active AlarmsUse the clear active alarm command to clear the active alarms:occam# clear active alarm {alarm index number}

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 activeIndex Severity SA Created Description1 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsDisplaying Sensors

Displaying SensorsThe 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 allFans: 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 RPMVoltages: #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 VoltsTemperatures: Internal temperature 27 C External temperature 22 C Internal temperature Mezz1 25 C #1 External temperature Mezz1 46 C #2 External temperature Mezz1 41 Coccam#

The show environment temperatures command displays the system tempera-ture sensors. The following example shows sample output from this command:occam# show environment temperatures Temperatures: Internal temperature 28 C External temperature 22 C Internal temperature Mezz1 24 C #1 External temperature Mezz1 52 C #2 External temperature Mezz1 44 C



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:

occam# show environment fans 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

The show environment alarms command displays the system sensors alarm state:occam# show environment alarmsFans: Fan1 OK Fan2 OK Fan3 OK Fan1 Mezz1 OK Fan2 Mezz1 OK Fan3 Mezz1 OKVoltages: #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 OKTemperatures: Internal temperature OK External temperature OK Internal temperature Mezz1 OK #1 External temperature Mezz1 OK #2 External temperature Mezz1 OKoccam#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsDisplaying Sensors

The show environment voltages command displays the system voltage sensors. The following example shows sample output from this command:occam# show environment voltagesVoltages: +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 Voltsoccam#

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 tableLow 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 VoltsTemperatures: External temperature -40 118 C Internal temperature -40 75 Coccam#



Alarms Catalog

Alarms CatalogThis section describes the BLC generated alarms sorted by feature. Alarms differ, according to BLC model.

System Environmental Alarms

Power Supply Voltage Changes

Fan Speed

Alarm Name PowerSupplyVoltageChange

Description The power supply has detected a change in the supplied voltage. This can be either a voltage too high or voltage too low condition. The high and low thresholds are determined in hardware and are not software configurable.

HI: Voltage exceeded high-thresholdLO: Voltage lower than low-thresholdOK: Voltage has returned to normal operational range

Service affecting? No

Alarm Name FanSpeedChange

Description Sensors have detected a change in the fan speed. This is an autono-mous condition and not a standing alarm; hence there is no clear or OK event indicating that the fans have returned to normal speed. When the systems are running hot the fan speed is increased, when the temp returns to a pre-set level the fans return to normal speed. Fan speed change to fast is not a high severity condition. It just indi-cates that the ambient temperature detected by the unit has increased. The temperature sensor raises a high threshold alarm if there is a truly major heat related problem.

FAST: Fan speed highSLOW: Fan speed low



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsAlarms Catalog

Temperature Exceptions

DSL Modem Power Change

External Alarm

Alarm Name temperatureLimitsExceeded

Description Sensors have detected a change in the temperature within the BLC.

HI: Sensors have detected that the temperature within the BLC is above acceptable limits. The fans or external heat exchanger or cooling system may be failing or have already failedLO: Sensors have detected that the temperature within the BLC is below acceptable limits.OK: Sensors have detected that the temperature within the BLC has returned to acceptable limits.


Alarm Name dslModemPowerChange

Description .A power change has occurred affecting the operation of the DSL modems.

ON: The power input has returned to a predefined threshold. This event is emitted to indicate that the DSL modems have been powered on.OFF: The DSL modems have been powered down to conserve power, due to a switch to battery power (as detected by the input voltage monitor).

Service affecting? Yes

Alarm Name 30- the sensor that senses this condition

Description .An condition has been detected by the sensor reading external alarm contacts. The description for this alarm is configurable from the CLI using the following command:occam(config)# environment alarm in description {description}Please see the section Alarm In Function on page 692 for an explana-tion how to use this command.

ON - external alarm raisedOFF- external alarm condition clear




Alarms Catalog

Physical Port Related Alarms

General Port/Link Alarms

Alarm Name Link Down

Description A physical port driver has detected that a previously active link has gone down.


Alarm Name Link Up

Description A physical port driver has detected that a previously inactive link has come online. This condition clears all previous Link Down conditions




T1 Alarms

Alarm Name T1 LOS

Description Loss of Signal (LOS) on the T1 port. No signal can be detected coming into the interface.If this T1 port is part of a multilink bundle and it is the 'last' active port in the bundle, when this condition occurs, the equipment services by the multilink bundle are no longer available. This is reported as a crit-ical.If this port is configured to have primary EOC or TMC, or secondary EOC or TMC links for a GR-303 interface group, no addi-tional alarms are generated since GR.303 has a full suite of alarms for indicating changes to the protection switching configurations.If this interface is part of an interface group and carries ordinary voice traffic, then a failure will result in a change to the over-subscription ratio for the associated interface group. This over-subscription change is reported as a minor alarm.


Alarm Name T1 LOF

Description Loss of Frame. The facility has been unable to frame on the incoming signal for x consecutive seconds.If this T1 port is part of a multilink bundle and it is the 'last' active port in the bundle, when this condition occurs, the equipment services by the multilink bundle are no longer available. This is reported as a critical. If this port is configured to have primary EOC or TMC, or secondary EOC or TMC links for a GR-303 interface group, no addi-tional alarms are generated since GR.303 has a full suite of alarms for indicating changes to the protection switching configurations.If this interface is part of an interface group and carries ordinary voice traffic, then a failure will result in a change to the over-subscription ratio for the associated interface group. This over-subscription change is reported as a minor alarm.




Alarms Catalog

Alarm Name T1 AIS

Description Alarm Indication Signal (AIS) has been detected on this T1 port. If a node detects an upstream T1 failure, it transmits this alarm signal downstream to prevent further LOS alarms at downstream locations. (it is possible that the AIS can be provisioned to be either all ones or all zeros)


Alarm Name T1 Loopback

Description Loopback condition on the T1 port. The loopback condition means that this facility is in a loopback state (for testing purposes).The BLC responds to in-band line loop-up/down code and if the framing is ESF and the FDL is set to ATT, it will respond to a payload request command.At this time only a single event string is logged, regardless of the loopback type.


Alarm Name T1 RAI

Description Remote Alarm Indication (RAI) on the T1 port.Yellow alarmIf a node detects that the T1 signal it is receiving is not correct, it raises the YEL alarm, then it transmits a YEL back upstream to the sending equipment and an AIS downstream.


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.




DSL Modem Alarms

This section contains definitions for the two DSL modem alarms that are supported by the BLC. These alarms communicate the modem's operational state as it transitions in and out of the showtime state. There is a DSL Power Change event defined at the system level on page 704. These two events here are DSL port related.

Alarm Name DSL ModemOutShowtime

Description The DSL modem is out of Sync (showtime).The DSL LED on the BLC is red.


Alarm Name DSL ModemInShowtime

Description The DSL modem is in Sync (showtime).The DSL LED on the BLC is green.




Alarms Catalog

Trunk AlarmsThis 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'.

TR-08 Misc. Alarms

Alarm Name TR-08 Incoming Power/Miscellaneous Cleared

Description AC power is unavailable at the location or due to some environmental condition as reported by 3rd party equipment.

ON: The alarm condition has occurred.OFF: The alarm condition has cleared.




TR-08 Shelf Alarms

TR-08 Major Alarms

Alarm Name TR-08 Incoming Shelf

Description An incoming shelf alarm received on the FDL. This reports a loss of shelf's operational integrity (This generally means the shelf is bad, there is a LOS, LOF, etc.).



Alarm Name TR-08 Outgoing Shelf

Description This reports a loss of shelf's operational integrity (This generally means the shelf is bad, there is a LOS, LOF, etc.)



Alarm Name TR08 Incoming Major

Description A service-affecting fault has occurred, as reported to us on the FDL by some 3rd party network element (e.g. specials shelf); subscribers have lost service.



Alarm Name TR08 Outgoing Major

Description A service-affecting fault has occurred; some subscribers have lost service.





Alarms Catalog

TR-08 Minor Alarms

Alarm Name TR08 Incoming Minor

Description A non-service affecting fault, has been received on the FDL from some 3rd party network element, such as an open RT door, has occurred.



Alarm Name TR08 Outgoing Minor

Description A non-service affecting fault such as an open RT door has occurred.





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

Forced switch back to primary

Inhibit switch back to primary

Inhibit switch to protect

Autonomous Switch back to primary

Autonomous Switch to protect

Manual switch back to primary

Manual switch to protect

Each IG alarm contains an IG ID. This IG ID is displayed in the alarm description.

EOC and TMC Protection Not Available Alarms

Alarm Name EOC Protection Not Available

Description EOC protection is not available for the IG. This may happen in a situ-ation where a protection switch occurred from primary to secondary and the primary link is still down, indicating that a switch back cannot occur and hence there is no protection for this link.




Alarms Catalog

EOC and TMC Failure Alarms

EOC and TMC Forced Switch Alarms

Alarm Name EOC Failure

Description Both primary and secondary EOCs have been lost.


Alarm Name TMC Protection Not Available

Description TMC protection is not available for this IG. This may happen if a protection switch occurred from primary to secondary and the secondary link is still down, indicating that a switch back cannot occur. As a result, there is no protection for this link.


Alarm Name TMC Failure

Description Both primary and secondary TMCs have been lost.


Alarm Name EOC Forced Switch Back

Description The EOC link has been forced to switch to primary.


Alarm Name TMC Forced Switch Back

Description The TMC link has been forced to switch to primary.




EOC and TMC Inhibit Switch Alarms

Alarm Name EOC Forced Switch to Protect

Description EOC has been forced to switch to the protection link.


Alarm Name TMC Forced Switch to Protect

Description TMC has been forced to switch to the protection link.


Alarm Name EOC Inhibit Switch Back

Description A switch to primary has been inhibited on the EOC.


Alarm Name TMC Inhibit Switch Back

Description A switch to primary has been inhibited on the TMC.


Alarm Name EOC Inhibit Switch to Protect

Description A switch to protection has been inhibited on the EOC.


Alarm Name TMC Inhibit Switch to Protect

Description A switch to protection has been inhibited on the TMC.




Alarms Catalog

EOC and TMC Autonomous Switch Alarms

There are two autonomous switch events for TMC and EOC. These indicate that the equipment took the action itself without user interaction. The manual switch events are transient events.

Alarm Name EOC Auto Switch Back

Description An autonomous EOC switch to primary has occurred.


Alarm Name TMC Auto Switch Back

Description An autonomous TMC switch to primary has occurred.


Alarm Name EOC Auto Switch to Protect

Description An autonomous EOC protection switch (or switch to primary) has occurred.


Alarm Name TMC Auto Switch to Protect

Description An autonomous TMC protection switch (or switch to protect) has occurred.




EOC and TMC Manual Switch Alarms

The manual switch alarm are transient events.

Alarm Name EOC Manual Switch Back

Description An manual EOC switch back.


Alarm Name TMC Manual Switch Back

Description An manual TMC switch back has occurred.


Alarm Name EOC Manual Protection Switch

Description A manual EOC protection switch has occurred.


Alarm Name TMC Manual Protection Switch

Description An manual TMC protection switch has occurred.




Alarms Catalog

General GR-303 Events

This section contains definitions for a collection of generic GR.303 alarms used to convey information about the state of the primary and secondary EOC and TMC links as well as general information about the Interface Group.

Alarm Name EOC Active

Description The indicated EOC is Active for this IG.


Alarm Name EOC Standby

Description The indicated EOC is in Standby for this IG.


Alarm Name TMC Active

Description The indicated TMC is Active for this IG.


Alarm Name TMC Standby

Description The indicated TMC is in Standby for this IG


Alarm Name EndpointChanges

Description Endpoint(s) has changed state (reachable or unreachable).




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

Alarm Name IG Down

Description Interface group has been stopped (user-commanded) or cannot run (e.g., due to cards being down).

Service Affecting? Yes

Alarm Name IG Redundant

Description Interface group applications are redundant.


Alarm Name IG No Redundant

Description Interface group applications are not redundant.


Alarm Name LAPD Up

Description The LAPD link is up on EOC/TMC channel.




Alarms Catalog

Alarm Name LAPD Down

Description The LAPD link is down on EOC/TMC channel.


Alarm Name LAPD Redundant

Description The LAPD link is redundant on the EOC/TMC channel.


Alarm Name LAPD Dual Failure

Description Dual LAPD failure on EOC/TMC channel.




EPS Alarms

Alarm Name hbUp

Description An EPS heartbeat has been detected on a path which was previously down.


Alarm Name hbDown

Description An EPS heartbeat has not been received on a path for a specific amount of time.


Alarm Name EPS Failover

Description An EPS failover has occurred. This is expected, after receiving a heart-beat down event, in a correctly configured EPS network.


Alarm Name EPS Revert

Description The EPS configuration has reverted to the preferred path group. The previous heartbeat down condition has been cleared and the ring has reverted to its original state.


Alarm Name EPS Clear

Description An EPS failover has been cleared.




Alarms Catalog

Alarm Name EPS Loop Detected

Description An EPS loop was detected on the interface.


Alarm Name EPS Cleared

Description An EPS loop has been cleared on the interface.




Shelf Alarms

Card Alarms

Alarm Name CardInserted

Description A card has been inserted into a stack. This event occurs whether the card was inserted manually via the shelf mode command "insert card {IP address} {slot}" or automatically when the card rebooted and was detected by the shelf controller.


Alarm Name CardRemoved

Description A card has been removed from a stack. This event occurs when a card has been manually removed from the stack. Manual removal is the only way a card can be removed at this time. Use the CLI command, from shelf mode: remove card


Alarm Name CardUp

Description A card in a shelf has come on-line. This indicates that all the card's functions are up and operational including the management layer.


Alarm Name CardDown

Description A card has gone down, for hardware or software failure reasons. The shelf controller can no longer detect the presence of the card. All the ports on the card are no longer available.




Alarms Catalog

Configuration Change

The configuration change event is triggered whenever copy running to startup is executed.

Alarm Name ConfigurationChange

Description This event is generated whenever the copy running-config startup-config command (or similar operation to commit the configuration) is used.




GNK AlarmsThese 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.

Alarm Name KERNEL_GNK_New

Description A GNK alarm has been detected on this port and port has been shutdown.


Alarm Name KERNEL_GNK_Clear

Description GNK alarm has been cleared on this port and port has been re-enabled.




Alarms Catalog

Over Temperature Shutdown AlarmThis alarm is sent by the BLC when sensors detect that the temperature is over the normal limit and the BLC shuts down.

Alarm Name KERNEL_OverTemp_New

Description BLC shutdown due to over temperature.


Alarm Name KERNEL_OverTemp_Clear

Description BLC re-enabled as over temperature condition has cleared.




Power Management AlarmThis alarm is sent by the BLC when a AC power outage is detected.

Alarm Name AC POWER_ON

Description AC Power Failure. The DSL modems will be shutdown in a delayed fashion based on the timer settings configured.


Alarm Name AC POWER_OFF

Description AC Power has been restored.




Alarms Catalog

Fan AlarmsThese are the fan alarms which are sent out by the BLC when the fan tray is inserted/removed.

Alarm Name Fan Tray Removed

Description The fan tray has been removed.


Alarm Name Fan Tray Inserted

Description The fan tray has been inserted.




Native IP Management Alarms

Blacklisting Alarms

The BLC must be protected from Denial of Service attacks that take advantage of certain control packet types (currently consist of IGMP, DHCP and ARP) that the BLC is using for subscriber management. The vulnerability exists when a device generates large volumes of control packet types either intentionally or due to a virus which and can cause a denial of service for other subscribers on the BLC. Blacklisting will be used to monitor and trigger an action when a device or port is considered to be in violation of a service policy. If the control packet rate exceeds the metered rate over the sample period the port/PVC that the device is associated with will be blacklisted and the action will be to shutdown (and alarm) or to just trigger an alarm for the offending port/PVC. Once a port/PVC has been blacklisted it will be periodically re-enabled (if the action was to shut it down) to test if the offending device that triggered the blacklist has changed its behavior. The period that the port is retested will be subject to an exponential backoff algorithm to a maximum test period of ten minutes. If, after re-enabling the port/PVC the triggering device is found to be well behaved then a clearing condition will be triggered.

Alarm Name Port out-of-profile

Description Subscriber port is blacklisted.


Alarm Name Port in-profile

Description Subscriber port is cleared from blacklisting.




Alarms Catalog

Client Queue Threshold Alarms

The SSM module in the BLC maintains trap packet queues for each registered user land client. These queues are used to queue trapped (or copied) packets that have been sent to the CPU by the switch in the BLC. These queues have a hard coded upper limit at which point additional trapped packets are silently discarded (but counted). Each client queue is given a high and low watermark threshold. When the high watermark threshold is exceeded an alarm is triggered to notify management that the client queue is dangerously close to dropping packets. If the queue threshold drops below the low watermark an alarm is also be triggered. If the client queue continues to grow to the point that packets are being dropped then an alarm is triggered indicating the number of dropped packets since the system initialized. The high watermark is configured as four fifths of the queue capacity. The low watermark is configured to three fifths of the queue capacity.

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.


Alarm Name Client Queue HWM Threshold Clear

Description The client queue is now below the HWM Threshold.


Alarm Name Client Queue Packets Dropped

Description The client queue has exceeded threshold and packets are being dropped.


Alarm Name Client Queue Packets Are Not Dropped

Description The client queue are no longer being dropped.




Ingress Filter Alarms

Ingress filter alarms are associated with subscriber services. When you configure access lists and apply them to the subscriber ports, filter rule and mask resources are consumed from the system ports. Alarms are generated when the number of used rules and masks reach a preset high water mark and also when they are exhausted. Corresponding clearing events are generated when the filter usage drops below the high water mark and resource exhaustion limits.

The command resource-port causes the Ethernet port to be reserved for Ethernet chaining and adds its resources are added to the resource pool used for subscriber filtering.This command prevents the port from being used for external Ethernet connectivity. All other previous configuration on the port is disregarded. The commands shutdown and no shutdown have no affect on this port once it becomes a resource port.

The command no resource-port removes the port from the subscriber filter resource pool. If it is currently in use by active Ingress Filters the command will fail until all Ingress Filters have been removed. This may require that the DSL subsystem be shutdown.

When no resource port is configured, there are 128 rules and 16 masks available for these filters. If a resource port is configured, then there are 32 masks and 256 rules available. If a high water mark event is generated Occam Networks recommends that you configure an Ethernet port as a resource port if you have not previously done so. This would increase the filter resources that could trigger a clearing event. There are separate sets of events for filter masks and filter rules.

Alarm Name Filter mask HWM Threshold reached

Description Filter mask usage has hit the high water mark threshold.


Alarm Name Filter mask HWM Threshold cleared

Description Filter mask HWM Threshold cleared.


Alarm Name Filter mask resources exhausted

Description The filter mask resources have been exhausted.




Alarms Catalog

Alarm Name Filter mask resources available

Description Filter mask usage is below the maximum available limit.


Alarm Name Filter Rule HWM Threshold Reached

Description Filter rule usage has hit the high water mark threshold for subscriber services.


Alarm Name Filter Rule HWM Threshold Cleared

Description Filter rule HWM Threshold cleared.


Alarm Name Filter Rule Resources Exhausted

Description Filter rule resources have been exhausted.


Alarm Name Filter Rule Resources Available

Description Filter rule usage is below the maximum available limit.



BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsIndex of Alarms

Index of Alarms30- the sensor that senses this condition . . . . . . . . . . . . . . . . . . . . . . . . 730AC POWER_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757AC POWER_ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757CardDown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753CardInserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753CardRemoved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753CardUp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753Client Queue HWM (high water mark) Threshold Reached . . . . . . . . . . 760Client Queue HWM Threshold Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760Client Queue Packets Are Not Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . 760Client Queue Packets Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760ConfigurationChange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754DSL ModemInShowtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735DSL ModemOutShowtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735dslModemPowerChange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730EndpointChanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748EOC Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748EOC Auto Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746EOC Auto Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746EOC Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743EOC Forced Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744EOC Forced Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744EOC Inhibit Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745EOC Inhibit Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745EOC Manual Protection Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747EOC Manual Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747EOC Protection Not Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742EOC Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748EPS Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751EPS Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752EPS Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751EPS Loop Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752EPS Revert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751Fan Tray Inserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758Fan Tray Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758FanSpeedChange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729Filter mask HWM Threshold cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761Filter mask HWM Threshold reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761Filter mask resources available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761Filter mask resources exhausted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761Filter Rule HWM Threshold Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762Filter Rule HWM Threshold Reached . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762Filter Rule Resources Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762



Index of Alarms

Filter Rule Resources Exhausted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762hbDown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751hbUp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751IG Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749IG No Redundant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749IG Redundant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749IG Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749KERNEL_GNK_Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755KERNEL_GNK_New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755KERNEL_OverTemp_Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756KERNEL_OverTemp_New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756LAPD Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750LAPD Dual Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750LAPD Redundant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750LAPD Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749Link Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731Link Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731Port in-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759Port out-of-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759PowerSupplyVoltageChange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729T1 AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733T1 LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732T1 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733T1 LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732T1 OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734T1 RAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733temperatureLimitsExceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730TMC Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748TMC Auto Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746TMC Auto Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746TMC Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743TMC Forced Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744TMC Forced Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744TMC Inhibit Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745TMC Inhibit Switch to Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745TMC Manual Protection Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747TMC Manual Switch Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747TMC Protection Not Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742TMC Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748TR08 Incoming Major . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739TR08 Incoming Minor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740TR-08 Incoming Power/Miscellaneous Cleared . . . . . . . . . . . . . . . . . . . . 737TR-08 Incoming Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738TR08 Outgoing Major . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739TR08 Outgoing Minor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 36: Alarms and SensorsIndex of Alarms

TR-08 Outgoing Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738TR-08 Outgoing Power/Miscellaneous Cleared . . . . . . . . . . . . . . . . . . . . 737


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 37: Simple Network Management Protocol (SNMP)

Introduction

Chapter 37Simple Network Management Protocol (SNMP)

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735Default SNMP Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735Enabling SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736Displaying SNMP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743SNMP Support For Activation of Subscriber Services. . . . . . . . . . . . . . . . . . . . . . . 747

IntroductionThe 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.

Default SNMP ValuesTable 37-1 shows the factory default configuration for SNMP specific parameters:

Table 37-1: Default SNMP Configuration

SNMP contact name [email protected]

SNMP contact location Occam Networks, Santa Barbara, California

SNMP administrative state

OFF

SNMP name BLC model name (i.e., BLC 6252-03)


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 37: Simple Network Management Protocol (SNMP)Enabling SNMP

Enabling SNMPFollow these steps to enable SNMP on the BLC:

1 Enter Global Configuration Mode:occam# configure terminalEnter configuration commands, one per line.End with CNTL/Z.occam(config)#

2 Use the snmp-server community command from Global Configuration Mode to specify a community name to determine SNMP access. A community name is a name associated with the BLC and a set of SNMP managers that are allowed to manage it with the specified privilege level.

The syntax of the snmp-server community command is as follows:occam(config)# snmp-server community name [ro | rw] {host list}

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

The following example creates a read-write community called “mycom2” that can be accessed from any host:occam(config)# snmp-server community mycom2 rw 0:0:0:0

3 Enter or modify the name of an SNMP contact person. The factory default contact is “[email protected]”: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



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.

“Standard” traps are link-up, link-down, and cold-start. “Environmental” traps are fan-speed, voltage, and temperature.

In the following example, all traps are enabled:occam(config)# snmp-server enable traps all

Use the no form of these commands to stop traps from being sent.

Note: The “nspPeerDeadNotification” trap is not enabled with snmp-server enable traps all command in order to avoid a trap flood from all blades in the network if the NPS peer goes down. This trap must be enabled explicitly.

Table 37-2: Commands to Enable Environmental SNMP Traps

Table 37-3: Commands to Enable EPS Traps

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.



Table 37-4: Commands to Enable Kernel Traps

Table 37-5: Commands to Enable Ethernet Loop Traps

snmp-server enable traps eps epsPathGroupHeartbeatNotification

An EPS heartbeat has not been received on a path for a specific amount of time or an EPS heartbeat has been detected on a path which was previously down.

snmp-server enable traps eps epsRingFailoverNotification

An EPS failover has occurred. This is expected, after receiving a heartbeat down event, in a correctly configured EPS network.

snmp-server enable traps eps epsRingRevertNotification

The EPS configuration has reverted to the preferred path group. The previous heartbeat down condition has been cleared and the ring has reverted to its original state.

Command Event

snmp-server enable traps kernel all Any of the kernel traps have been triggered.

snmp-server enable traps kernel acPowerNotification

An AC power outage is detected or power has been restored.

snmp-server enable traps kernel fanTrayNotification

The BLC’s fan tray has been removed or 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 overTempNotification

The BLC has shutdown due to over 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 epsLoopNotification

An Ethernet loop has been detected or the loop condition has cleared.



Enabling SNMP

Table 37-6: Commands to Enable Standard Traps

Table 37-7: Commands to Enable Subservices Traps

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 clientQueuePacketDropNotification

The client queue has exceeded threshold and packets are being dropped or the condition has cleared and packets are no longer being dropped.

snmp-server enable traps subservices clientQueueThresholdNotification

The client queue’s HWM threshold has been reached and is dangerously close to dropping packets or the client queue is now below the HWM threshold.

snmp-server enable traps subservices ingressFilterMaskResourcesNotification

Alerts to when the filter mask resources have been exhausted and when there are filter mask resources available again.

snmp-server enable traps subservices ingressFilterMaskThresholdNotification

Alerts to when the number of filter masks has hit the HWM threshold and when the filter mask HWM threshold alarm has cleared.

snmp-server enable traps subservices ingressFilterRuleResourcesNotification

Alerts to when the filter rule resources have been exhausted and when there are filter rule resources available again.

snmp-server enable traps subservices ingressFilterRuleThresholdNotification

Alerts to when the number of filter rules has hit the HWM threshold and when the filter rule HWM threshold alarm has cleared.

snmp-server enable traps subservices subscriberPortBlackListingNotification

A subscriber port has been blacklisted or is no longer being blacklisted.



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:

The variables for each snmp-server host command are described as follows:

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

8 Start the SNMP agent to complete your BLC system configuration:occam(config)# snmp-server

Command Description

snmp-server host all {ipaddr/hostname} {community} {interface}

Allows all SNMP traps to be sent to a specified host.

snmp-server host envmon {ipaddr/hostname} {community} {interface}

Allows all environmental monitor SNMP traps to be sent to a specified host.

snmp-server host eps {ipaddr/hostname} {community} {interface}

Allows all SNMP EPS traps to be sent to a specified host.

snmp-server host kernel {ipaddr/hostname} {community} {interface}

Allows all SNMP kernel traps to be sent to a specified host.

snmp-server host leps {ipaddr/hostname} {community} {interface}

Allows all SNMP Ethernet loop traps to be sent to a specified host.

snmp-server host standard {ipaddr/hostname} {community} {interface}

Allows all SNMP standard traps to be sent to a specified host.

snmp-server host subservices {ipaddr/hostname} {community} {interface}

Allows all SNMP subservice traps to be sent to a specified host.

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.



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: ONsysContact: [email protected]: BLC-6252sysLocation: Occam Networks, Santa Barbara, CaliforniasysDescription: BLC-62520 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 received0 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 sentSNMP traps: fan-speed: disabled link-down: disabled link-up: disabled cold-start: disabled voltage: disabled temperature: disabledSNMP Communities: public Access: ro Managers: 0:0:0:0



private Access: rw Managers: 0:0:0:0



Displaying SNMP Information

Displaying SNMP InformationUser Mode Show SNMP Commands

The following commands show sample output from the show snmp commands available from the CLI User Mode:

The show snmp contact command displays the SNMP contact information:occam> show snmp contactSysContact: [email protected]

The show snmp hostname command displays the host that receives SNMP traps:occam> show snmp hostnamesysName: snmp-server

The show snmp location command displays the SNMP location information:occam> show snmp locationsysLocation: Occam Networks, Santa Barbara, California

The show snmp description command displays the SNMP description information:occam> show snmp descriptionsysDescription: BLC-6252

The show snmp statistics command displays SNMP statistics:occam> show snmp statistics0 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 received0 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


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 37: Simple Network Management Protocol (SNMP)Displaying SNMP Information

The show snmp command displays all of the above information together:occam> show snmpAdmin State: ONsysContact: [email protected]: BLC-6252sysLocation: Occam Networks, Santa Barbara, CaliforniasysDescription: BLC-62520 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 received0 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 sentSNMP traps: external-alarm: disabled fan-speed: disabled temperature: disabled voltage: disabled cold-start: disabled link-down: disabled link-up: disabledSNMP Communities: public Access: ro Hosts: 0:0:0:0 private Access: rw Hosts: 0:0:0:0occam>



Displaying SNMP Information

Privileged Mode Show SNMP CommandsThe following commands show sample output from the show snmp commands available from the CLI Privileged Mode. All of the show snmp commands that are available from User Mode are available from Privileged Mode:

The show snmp community command displays any defined SNMP communities:occam# show snmp communitySNMP 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 trapSNMP traps: external-alarm: enabled fan-speed: enabled temperature: enabled voltage: enabled cold-start: enabled link-down: enabled link-up: enabledoccam#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 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 snmpAdmin State: ONsysContact: [email protected]: BLC-6252sysLocation: Occam Networks, Santa Barbara, CaliforniasysDescription: BLC-62520 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 received0 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 sentSNMP traps: fan-speed: disabled link-down: disabled link-up: disabled cold-start: disabled voltage: disabled temperature: disabledSNMP Communities: public Access: ro Managers: 0:0:0:0 private Access: rw Managers: 0:0:0:0occam#



SNMP Support For Activation of Subscriber Services

SNMP Support For Activation of Subscriber ServicesSNMP supports activation of subscriber services with the OCCAM-SERVICE-ACTIVATION-MIB. MIBs are automatically loaded onto all customer FTP accounts.

The features supporting a DSL port are described below on page 747.

The features supporting an Ethernet subscriber port are described on page 748.

The features supporting a Media Gateway are described on page 748.

The features supporting a Trunking Gateway are described on page 749.

The Occam OCCAM-SERVICE_ACTIVATION-MIB supports persistence. The MIB can be used to trigger copying the running configuration to the startup configuration.

DSL PortsFor a DSL ports, the OCCAM-SERVICE-ACTIVATION-MIB will allow selecting a DSL port and supports the following operations:

Enable/Disable the DSL port

Read the admin status of the DSL port

Read all existing info fields associated with the DSL port

Remove info fields from the DSL port

Set info fields (up to three) on the DSL port

Read which Services (1 to 4) are currently assigned to a DSL port

Assign (SET) a DSL Service (1 to 4) to a DSL port

Enable/Disable a DSL Service assigned to a DSL port

Read the admin status of a DSL Service assigned to a DSL port

Read/Set the VPI/CPI assigned to a DSL Service assigned to a DSL port

Read available Access Profile names

Read/Set the Access Profile assigned to a DSL Service assigned to a DSL port

Read available DSL Profiles

Read/Set the DSL Profile assigned to a DSL port

Read/Set Access Profile overrides on Services: igmp-group-limit, mac-limit, and mac learning


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 37: Simple Network Management Protocol (SNMP)SNMP Support For Activation of Subscriber Services

Ethernet Subscriber PortsFor an Ethernet Subscriber ports, the OCCAM-SERVICE-ACTIVATION-MIB will allow selecting a Ethernet Subscriber port and supports the following operations:

Enable/Disable the Ethernet Subscriber port

Read the admin status of the Ethernet Subscriber port

Read all existing info fields associated with Ethernet Subscriber port

Remove info fields from the Ethernet Subscriber port

Set info fields (up to three) on the Ethernet Subscriber port

Read which Services (1 to 5) are currently assigned to an Ethernet Subscriber port

Assign (SET) an Ethernet Service (1 to 5) to an Ethernet Subscriber port

Enable/Disable an Ethernet Service assigned to an Ethernet Subscriber port

Read the admin status of an Ethernet Service assigned to an Ethernet Subscriber port

Read/Set the Subscriber VLAN assigned to an Ethernet Service assigned to an Ethernet Subscriber port

Read/Set the Access Profile assigned to an Ethernet Service assigned to an Ethernet Subscriber port

Media GatewayFor a Media Gateway, the OCCAM-SERVICE-ACTIVATION-MIB will allow selecting a voice port and supports the following operations:

Enable/Disable the voice port

Read the voice port admin status

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

Remove info fields from the voice port

Set info fields (up to three) on the voice port

Read/Set the voice port voice profile



SNMP Support For Activation of Subscriber Services

Read available voice profile names

Read/Enable/Disable the voice port unbalanced ring status

Read/Set the voice port protocol choice (MGCP/SIP)

Read/Set the voice port SIP profile

Read available SIP profile names

Read/Set the SIP Domain Name SIP Profile override

Read/Set the SIP params (User Name, Display Name, Auth User Name, Password)

Trunking GatewayFor a Trunking Gateway, the OCCAM-SERVICE-ACTIVATION-MIB will allow selecting a channel on an IG and supports the following operations:

Enable/Disable the channel

Read the channel admin status

Read/Set the channel description

Read/Set the channel endpoint name

Read/Set the channel subscriber profile

Read available subscriber profile names


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 37: Simple Network Management Protocol (SNMP)SNMP Support For Activation of Subscriber Services


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 38: System Logging (Syslog)

Introduction

Chapter 380System Logging (Syslog)

In this ChapterIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751Enabling Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752Disabling Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754Displaying Syslog Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754

IntroductionSystem 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 38: System Logging (Syslog)Enabling Syslog

Enabling SyslogEnable 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

FacilitiesA 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:

Table 38-1: Syslog facilities

LevelsA 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:

Table 38-2: Syslog levels

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 (in priority order) Description

emerg BLC unusable

alert Immediate action required

crit Critical conditions

err Error conditions

warn Warning conditions


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 38: System Logging (Syslog)

Enabling Syslog

Example Syslog Logging CommandsThe following examples show various logging commands that enable logging:

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 the Syslog server host “syslog-host.occamnet-works.com” receive messages generated by all facilities at the debugging level and above:occam(config)# logging *.debug 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

notice Significant but normal condition

info Informational messages

debug Debugging messages


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 38: System Logging (Syslog)Disabling Syslog

Disabling SyslogThe 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

Displaying Syslog Information1 The show logging command in User and Privileged Mode displays the status of

currently configured logging:occam# show loggingFacilities.Level Host*.warn 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}

Caution: It is recommended that debug commands only be used when troubleshooting specific problems under the direction of an Occam Networks technical support representative. When you are finished using a debug command remember to disable it with the no form of the command.

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 39: Viewing Your Hardware and Software Configuration

Viewing the Startup Configuration

Chapter 39Viewing Your Hardware and Software Configuration

In This Chapter:Viewing the Startup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755Viewing the Running Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756Viewing Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759Viewing the Software and Hardware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761Viewing the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765Checking the Network Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

After configuring the BLC, you can use various commands to view the system hardware and software configuration.

Viewing the Startup ConfigurationUse the show startup-config command from Privileged Mode to display the configuration the BLC will use the next time it reboots. The following example shows sample output for this command:occam# show startup-config!Script Version 5.5!Model BLC 6450!! Configure System!terminal width 120hostname vpt1!! Configure Clock!clock timezone PSTclock summer-time!! Configure EPS!eps mode vpt pg1 aggregationexit!! Configure Tagged Profile(s)!tagged-profile video untagged vlan 9


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 39: Viewing Your Hardware and Software ConfigurationViewing the Running Configuration

tagged vlan 100 10 tagged vlan 110 11 tagged vlan 120 12 tagged vlan 130 13 tagged vlan 140 14 tagged vlan 150 15 tagged vlan 160 16 tagged vlan 170 17 tagged vlan 180 18 tagged vlan 190 19<Text excluded>

Viewing the Running ConfigurationUse the show running-config commands from Privileged Mode to display information about the configuration file currently running on the BLC.

Displaying Information About Interfaces In the Running ConfigurationUse the show running-config interfaces commands from Privileged Mode to display interface information about the configuration file currently running on the BLC.

The show running-config interfaces bvi command displays information about the BVI interface. The following example shows sample output from this command:occam# show running-config interfaces bvi 1interface Bvi 1 ip address 176.129.48.197 255.255.255.0 eps vlan 2 no shutdownexit!

The show running-config interfaces ethernet {1-12} command displays infor-mation about an Ethernet interface. The following example shows sample output from this command:occam# show running-config interfaces ethernet 1!interface Ethernet 1 duplex auto speed auto ingress unknown-unicast rate limit 100 ingress multicast rate limit 0 ingress broadcast rate limit 1000 eps ring all igmp passthrough 192.22.33.1 no shutdownexit!



Viewing the Running Configuration

Displaying Information About the Running Configuration File

Use the show running-config command from Privileged Mode to display the configuration file currently running on the BLC. The following example shows sample output from this command:occam# show running-configvpt2#show running-config Building configuration... Done (09:01)!Script Version 5.5!Model BLC 6450!! Configure System!terminal width 120hostname vpt2!! Configure Clock!clock timezone PSTclock summer-time!! Configure Access List!access-list ip 1 permit associations!! Configure EPS!eps

<Text excluded>

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:

occam# show running-config diffBuilding configuration... Done (09:40)1c1< !Script Version 5.5R1---> !Script Version 5.5171,174d170< !


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 39: Viewing Your Hardware and Software ConfigurationViewing the Running Configuration

< ! Configure Network Clock< ! < network-clock-select primary nco_ntpoccam#



Viewing Interfaces

Viewing InterfacesViewing 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 interfacesEthernet4/1 is up, line protocol is up Hardware is GigabitEthernet, address is 0002.8600.078c MTU 1600 bytes, BW 1000000 Kbit full, 1000 Media gigabitEthernetEPS Settings: path participant, path configuration is ALLQueueing strategy: Strict PriorityOutput 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: 0Multicast:Port configured as passthrough port.

Dot3, RMON and Misc Statistics: txPkts: 108309514txBytes: 38012343txDiscards: 0txErrors: 0txUnicastPkts: 87862345txNonUnicastPkts: 20447169

dot3AlignmentErrors: 0dot3FCSErrors: 0dot3SingleCollisionFrames: 0dot3MultipleCollisionFrames: 0dot3DeferredTransmissions: 0dot3LateCollisions: 0dot3ExcessiveCollisions: 0dot3FramesTooLong: 0

rmonRxDropEvents: 0rmonRxOctets: 2552317119rmonRxPkts: 414716700rmonRxBroadcastPkts: 36967rmonRxMulticastPkts: 25301189rmonRxCRCAlignErrors: 0rmonRxUndersizePkts: 0rmonRxOversizePkts: 0<Text excluded>


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 39: Viewing Your Hardware and Software ConfigurationViewing Interfaces

Viewing Information About Specific InterfacesEnter the show interfaces command from User or Privileged Mode with specific interfaces to display information about individual interfaces. Table 39-1 shows the show interfaces commands and their descriptions.

Table 39-1: Show Interfaces Commands

Viewing Summarized Information About InterfacesEnter the show interfaces summary commands from User Mode to display interface information in a summarized format. Table 39-2 shows the show interfaces summary commands and their descriptions.

Table 39-2: Show Interfaces Commands

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 [number]

Displays information about one or all 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



Viewing the Software and Hardware Version

Viewing the Software and Hardware VersionUse the show version and show hardware commands from User and Privileged Modes to display the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images.

Displaying the System VersionThe following example shows sample output from the show version command:occam# show versionOccamOS System 5.5 for BLC 6450 [shelf:fff, slot:15]Kernel build id 1182412802, made Thu Jun 21 01:16:41 PDT 2007Booter build id 1182412802, made Thu Jun 21 01:12:43 PDT 2007


Board assembly number is 900151-01, revision number is A0, type is 1Serial number is 11613049, MAC address is 00:02:86:00:92:fbManufactured by OCCM on 11/29/2006


Hostname vpt2, uptime is 26 min, load average 0.22, 0.16, 0.16occam#

Viewing Information About the HardwareThe following shows sample output from the show hardware command:

Occam# show hardwareOccamOS System V5.3R2 for BLC 6150 [shelf:ccc, slot:1]Kernel build id V5_3R2, made Fri Dec 8 15:18:02 PST 2006Booter build id V5_3R2, made Fri Dec 8 15:15:10 PST 2006


Board assembly number is 900032-01, revision number is C1, type is 1Top-level assembly is xx6150Serial number is 08361720, MAC address is 00:02:86:00:0b:56Manufactured by OCCM on 8/14/2003

PLD revision 1.0FPGA revision FPGA_0: 000.020, FPGA_1: 000.007

Hostname ces1, uptime is 6 days, 3:30, load average 0.78, 0.31, 0.20


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 39: Viewing Your Hardware and Software ConfigurationViewing 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



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


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 39: Viewing Your Hardware and Software ConfigurationViewing the Software and Hardware Version

rtcDate: Thu Dec 14 19:56:21 PST 2006 rtcPwrUptimeTotal: 1321866 Occam#



Viewing the Chassis

Viewing the ChassisUse the show chassis command from User and Privileged Modes to display the system chassis.

The following example shows output of the show chassis command:occam# show 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 | | | | +-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+

PG1/PG2 - U: Up/Active D: Down VP1: VPT1 VP2: VPT2 u: Up

Slot IP SW Version Hostname ---- -- ---------- -------- 1 192.168.12.41 V5_3R2 ces1 2 192.168.12.21 V5_3R2 ces2 3 192.168.12.102 V5_3R2 vps12 4 192.168.12.91 V5_3R2 vps1 5 192.168.12.45 V5_3R2 six151-01 6 192.168.12.46 V5_3R2 ces6 9 192.168.12.149 V5_3R2 cm6212


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 39: Viewing Your Hardware and Software ConfigurationChecking the Network Connection

Checking the Network ConnectionDisplaying Domain Name Information

Use the show hosts command display domain name information: occam# show hostsDefault domain is not setHost AddressOccam 192.168.21.132localhost 127.0.0.1warty 192.168.21.111occam#

Pinging IP HostsVerify specific IP hosts are reachable by entering the ping command as follows:

ping {IP address or host name} [BVI-number] [COUNT] [SIZE]


{ip-address or hostname} = Ping destination IP address or host name


[COUNT] = Optional) Number of ping packets to send. The range is from 1 to 2147483647. The default is 5.

[SIZE] = Optional) Specifies the datagram size. The range is from 40 to 18024 bytes in each ping. The default is 64 bytes.

The following example:

checks the IP address “192.168.12.41”

sends the request out BVI 2

configures that eight ping packets be sent

specifies that the datagram size is 70 bytes

occam# ping 192.168.12.41 2 8 70PING 192.168.12.41 (192.168.12.41) from 192.168.22.32 bvi2: 70(98) bytes of data.78 bytes from 192.168.12.41: icmp_seq=1 ttl=254 time=2.39 ms78 bytes from 192.168.12.41: icmp_seq=2 ttl=254 time=2.35 ms78 bytes from 192.168.12.41: icmp_seq=3 ttl=254 time=1.74 ms78 bytes from 192.168.12.41: icmp_seq=4 ttl=254 time=2.23 ms78 bytes from 192.168.12.41: icmp_seq=5 ttl=254 time=1.86 ms78 bytes from 192.168.12.41: icmp_seq=6 ttl=254 time=2.35 ms



Checking the Network Connection

78 bytes from 192.168.12.41: icmp_seq=7 ttl=254 time=1.44 ms78 bytes from 192.168.12.41: icmp_seq=8 ttl=254 time=2.11 ms

--- 192.168.12.41 ping statistics ---8 packets transmitted, 8 received, 0% packet loss, time 7071msrtt min/avg/max/mdev = 1.446/2.064/2.398/0.325 msoccam#


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 39: Viewing Your Hardware and Software ConfigurationChecking the Network Connection


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 40: Updating Your System Configuration

Introduction

Chapter 40Updating Your System Configuration

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769BLC System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770Upgrading and Verifying a New Software Release . . . . . . . . . . . . . . . . . . . . . . . . . 771Displaying a List of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773Using the “boot enable” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774Installing a New Kernel or Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775Checking the Validity of a Software Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776Deleting a Software Release File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777Displaying the Status of Installed Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778

IntroductionThe 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)

WS_FTP Server version 2.0.3 by Ipswitch.

Linux versions Redhat 6.1, 7.0 -> 7.2


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 40: Updating Your System ConfigurationBLC System Components

BLC System ComponentsThe BLC Software Upgrade function works with the BLC system Boot PROM, Boot Flash and Occam OS Image Files, which are used to store and distribute BLC software releases.

Boot PROMThe 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 FlashBoot 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 FilesA 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 40: Updating Your System ConfigurationUpgrading and Verifying a New Software Release

Upgrading and Verifying a New Software ReleaseUse the following configuration steps to upgrade a BLC with new software and to verify that the new software has been loaded.

1 Access the system via SSH or a Telnet connection. Use the appropriate passwords to access the User and Privileged CLI command modes.

2 Save the current configuration to the disk:occam# copy running-config startup-config

3 Load the new code onto the BLC with the command upgrade all {ftp-url}.

The ftp url must be in the format:ftp://[username[:password]@]hostaddr[/[/]directory]/filename [zmon]

Note: It may take up to five minutes to transfer the new code and install it:occam# upgrade all {ftp-url}

An example of this command is:occam# upgrade all ftp://occamnetworks.com/pub/OCCAMOS.V5_4R1

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:


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 40: Updating Your System ConfigurationUpgrading and Verifying a New Software Release

occam# show boot status



Using the upgrade software Command

Using the upgrade software CommandThe upgrade software command has the same function as the upgrade all command, except that is does not update the FPGAs and ROM monitor.

Displaying a List of FilesUse the dir {ftp-url} command in Privileged Mode to display a list of files on a specified file system before changing its contents.

Before you copy a new configuration file to Flash memory you can use the dir command to verify that the file system does not already contain a configuration file with the same name. You can also use this command to verify a Flash configuration filename for use in another command before you copy a Flash configuration file to another location.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 40: Updating Your System ConfigurationUsing the “boot enable” Command

Using the “boot enable” CommandUse the boot enable {image-url} command in Privileged Mode to make a system image the active system, where {image-url} is the file-URL of the image file that is to be made active. The flash: file system will be assumed if no file system prefix is specified.The boot enable command identifies the bootflash partition in which the kernel for this image is installed. It then updates the boot EEPROM, indicating that the specified kernel should be the active kernel the next time the BLC is rebooted. The command will issue an error message if the kernel for the selected image has not been installed. This command terminates normally if the specified kernel is already enabled.

An example of this command is:occam# boot enable flash:OCCAMOS.xxxxxxx



Installing a New Kernel or Firmware

Installing a New Kernel or FirmwareUse the boot install command to install a new kernel or firmware.

Installing a New KernelUse the boot install kernel {image-url} command to install a kernel for an image that has already been downloaded, where {image-url} is the file-URL of the image file that contains the software release whose kernel is to be installed.

The boot install kernel command extracts the Linux kernel from the image file and copies it to compact flash, preserving the active kernel. This command is responsible for ensuring that the image file is valid, and that the Linux kernel is written to compact flash correctly.

The syntax flash: file system will be assumed if no file system prefix is specified.

An example of this command is:occam# boot install kernel flash: OCCAMOS.V4_0R1_6252

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.

Installing a New Firmware

Note: The upgrade all command is usually used instead of the boot install firmware command to install a new firmware package.

The command boot install firmware {image-url} updates the FPGA’s and ROM monitor (PPCBOOT), where {image-url} is the file-URL of the image file that contains the software release from which the FPGA code and ROM monitor is to be installed.

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


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 40: Updating Your System ConfigurationChecking the Validity of a Software Image

Checking the Validity of a Software ImageUse the boot verify commands to check the validity of a software image.

Verifying the Integrity of a Downloaded System ImageUse the boot verify command in Privileged Mode to verify the integrity of a downloaded system image, where {image-url} is the file-URL of the image file that contains the software release to be verified.

The flash: file system will be assumed if no file system prefix is specified.

An example of this command is:occam# boot verify verify:OCCAMOS.xxxxxxxx

Verifying the Integrity of a Bootflash PartitionUse the boot verify partition command in Privileged Mode to verify the integrity of a bootflash partition. Specify a partition number from 1 though 3 to select the partition that contains the image you wish to verify.

The boot verify partition command extracts the image size and checksum from the boot image header, computes a new checksum on the body of the image, and compares the two checksums. If the computed checksum and the stored checksum do not match an error message is issued.

An example of this command is:occam# boot verify partition 3Verifying partition...Partition verifiedoccam#



Deleting a Software Release File

Deleting a Software Release FileUse the delete command in Privileged Mode to delete a software release, where {image-url} is the file-URL of the image file for the software release to be deleted.

The delete command recognizes that the file being deleted is a system image. An error message will be issued if the user attempts to delete the current system image.

If the image file being deleted is associated with the system that is currently enabled, and if this is not the current system, then the delete command will delete the image and implicitly enable the current system.

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


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 40: Updating Your System ConfigurationDisplaying the Status of Installed Software

Displaying the Status of Installed SoftwareUse the show boot commands to display the status of installed software.

Displaying Information about a Bootflash PartitionUse the show boot partition {number} command in Privileged Mode to display information about a bootflash partition.

An example of this command is:occam# show boot partition 1

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

Displaying Information about the Current Status of the Bootable ImagesUse the show boot status command in Privileged Mode to display information about the current status of the bootable images.

This command will take into account the image files stored on the flash file system, the kernels installed in compact flash, the contents of the boot EEPROM, and the current system image.

An example of this command is:occam# show boot status

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.1076322603Partition 3 is not enabled It is not a bootable image

FPGA partition Image is invalidTertiary partition is invalidThe current user file system is /cf/OCCAMOS.1076495402 Its type is 'ext2' Its build id is 1076495402

Filesystem images:



Displaying the Status of Installed Software

OCCAMOS.1076322603 (secondary) OCCAMOS.1076495402 (current,primary)occam#

Displaying the Contents of the Boot EEPROMUse the show prom boot command in Privileged Mode to display information about the contents of the boot EEPROM.

An example of this command is:occam# show prom bootBoot Address 1 : 1Boot Address 2 : 2Boot Address 3 : fe200000Boot Count : 0

occam#

Displaying the Contents Of the Manufacturing EEPROMUse the show prom manufacturing command in Privileged Mode to display information about the contents of the manufacturing EEPROM.

An example of this command is:occam# show prom manufacturingBoard Assembly : 900032-01Board Name : 27Board Revision : B6Board Serial : 08366010Board Type : 1Company Name : OCCMMAC Address : 00:03:86:03:07:8fManufacture Date : 09/02/2003VCXO Data : null

occam#


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 40: Updating Your System ConfigurationDisplaying the Status of Installed Software


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 41: Configuring Network Traffic Intercept (NTI)

Introduction

Chapter 41Configuring Network Traffic Intercept (NTI)

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781NTI Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784NTI Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784Configuring a NTI Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784Enabling NTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785Viewing the NTI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786

IntroductionThis 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 AddressNTI 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:

voice to the ONT’s POTS connection.

management traffic to the ONT

SIP, MGCP and NSP traffic

If you do not know the MAC addresses of a target subscribers devices the following commands may help you obtain them on the host BLC:


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 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.

Targeted Subscriber Traffic Monitoring LocationsWhen NTI is enabled on a BLC, traffic is replicated from the subscriber’s host BLC to a mirror port on the same BLC. Traffic may be monitored on an Occam Secure Support Access Node (OSSAN). An OSSAN is an Occam-developed support tool with pre-loaded software utilized in most Occam field deployments.

The host BLC may be configured in internal, local or remote modes to determine where the intercepted traffic is monitored.

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.



Introduction

Figure 41-1: Subscriber Traffic Monitoring Points Via NTI

CENTRAL OFFICE

EPS RING

TARGETSUBSCRIBER'SHOST BLC IN RT

OSSAN

BLCS IN CO

TARGETSUBSCRIBER'S

DEVICE

NTI "LOCAL MODE"TRAFFIC MONITORING

POINT

CONSOLE ATTACHED TOCRAFT PORT ON HOST BLC

NTI "INTERNAL MODE"TRAFFIC MONITORING

POINT

NTI "REMOTE MODE"TRAFFIC MONITORING

POINT


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 41: Configuring Network Traffic Intercept (NTI)NTI Configuration Overview

NTI Configuration OverviewTo enable NTI you must first enter NTI Profile Configuration mode and create a NTI profile, giving it a unique name. This NTI profile specifies the target MAC, and the interface on the BLC on which the device to be monitored resides. Next you must enter NTI Configuration mode to configure the desired NTI mode (internal, local or remote), attach the desired NTI profile, and enable NTI.

Configuring a NTI Profile1 Enter Global Configuration Mode:


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}

6 Exit NTI Profile Configuration Mode:occam(config-nti-prf)# exit




Enabling NTI

Enabling NTI 1 Enter Global Configuration Mode:


2 Enter NTI Configuration Mode:Occam(config)# nti

3 Configure the NTI mode, selecting from the following:

internal mode

In internal mode tcpdump -i decodes the intercepted traffic. This tcpdump may be seen by entering the command show nti tcpdump, as described in the section Viewing the NTI Configuration on page 787:

Occam(config-nti)# mode internal

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

4 Attach a NTI profile, specifying the profile by nameOccam(config-nti)# nti-profile {NTI profile name}

5 Enable NTI:Occam(config-nti)# no shutdown

6 Exit NTI Configuration Mode:Occam(config-nti)# exit


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 41: Configuring Network Traffic Intercept (NTI)Viewing the NTI Configuration

Viewing the NTI Configuration

“show nti profile [profile-name]” CommandUse this command to display NTI profile information. If no profile name is entered this command will display information for all NTI profiles. NTI profile configuration is described in the section Configuring a NTI Profile on page 784. In this example we see the following:

The NTI profile is named “dis”.

The ingress interface on which the device to be monitored resides is DSL 1.

The Mac address of the device to be monitored is “00:02:86:00:06:87”.

occam# show nti-profileNti profile: dis Interface: Dsl 1 MAC Address : 00:02:86:00:06:87

“show nti config” CommandUse this command to display NTI configuration information. In this example we see the following:

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”.

occam# show nti configNTI Configuration Mode: internal Profile: dis State: active



Viewing the NTI Configuration

“show nti status” CommandUse this command to display NTI status information. In this example we see the following:

The time NTI was started.

The current time.

The NTI mode is “internal”.

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.

occam# show nti statusstart time: Tue Feb 6 20:24:25 UTC 2007current time: Tue Feb 6 20:26:37 UTC 2007Mode INTERNALPackets 201435mac 00:02:86:00:06:87rx pps limit 500rx pps 0rx pps max 6rx pps limit exceeded 0

“show nti tcpdump” CommandUse this command to view the tcpdump of NTI interfaces. The command show nti tcpdump will only show output when NTI mode is configured as internal by entering the command mode internal entered from NTI Configuration mode:

occam# show nti tcpdump20:25:23.800120 10.1.17.11 > 10.1.17.27: icmp: echo request (DF) [tos 0x48]20:25:23.821180 10.1.17.27 > 10.1.17.11: icmp: echo reply [tos 0x48]20:25:24.813163 10.1.17.11 > 10.1.17.27: icmp: echo request (DF) [tos 0x48]20:25:24.836213 10.1.17.27 > 10.1.17.11: icmp: echo reply [tos 0x48]20:25:25.819153 10.1.17.11 > 10.1.17.27: icmp: echo request (DF) [tos 0x48]20:25:25.841222 10.1.17.27 > 10.1.17.11: icmp: echo reply [tos 0x48]20:25:26.830191 10.1.17.11 > 10.1.17.27: icmp: echo request (DF) [tos 0x48]20:25:26.851267 10.1.17.27 > 10.1.17.11: icmp: echo reply [tos 0x48]20:25:27.839195 10.1.17.11 > 10.1.17.27: icmp: echo request (DF) [tos 0x48]20:25:27.861274 10.1.17.27 > 10.1.17.11: icmp: echo reply [tos 0x48]


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 41: Configuring Network Traffic Intercept (NTI)Viewing the NTI Configuration


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLT

Introduction

Chapter 42ADSL2+ Line Testing- SELT, DELT and MLT

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789SELT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790DELT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792Examples of SELT and DELT Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795

IntroductionOccam 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLTSELT

SELTSELT 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.



SELT

Figure 42-1: SELT Test

Figure 42-2: SELT Test Results

BLC IN RTRESIDENCE

(NO ADSL2+ MODEM )

A. BLC in RT runs SELT loop test on DSL interface 1 forsixty seconds:Occam# test dsl selt 1 period 3

BLC IN RTRESIDENCE

(NO ADSL2+ MODEM )

B. SELT loop test results are interpreted by Awaresoftware application.

AWARE SOFTWAREAPPLICATION


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLTDELT

DELTDELT 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.

Figures 42-3 through 42-5 show an example of a DELT loop test.



DELT

Figure 42-3: DELT Test - From BLC To ADSL2+ Modem

Figure 42-4: DELT Test - From ADSL2+ Modem To BLC

BLC IN RT

A. BLC in RT runs DELT loop test on DSL interface 2 foreighty seconds:Occam# test dsl delt 2 period 4

RESIDENCE(with ADSL2+ MODEM )

BLC IN RT

B. ADSL2+ modem responds to BLC DELT test.

RESIDENCE(with ADSL2+ MODEM )


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLTDELT

Figure 42-5: DELT Test Results

C. DELT loop test results are interpreted by Awaresoftware application.

BLC IN RT RESIDENCE(with ADSL2+ MODEM )

AWARE APPLICATION



Examples of SELT and DELT Reports

Examples of SELT and DELT ReportsA sample of a SELT report is shown below. An example of DELT report is shown on page 801.

Example SELT Reportoccam# show dsl selt 15

AGC 3.0 dBFrontEndDelay (sample at 2.2 MHz) 51.5 msFrontEndGain 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


BLC 6000 System Configuration and Installation Guide- Release 5.5 Chapter 42: ADSL2+ Line Testing- SELT, DELT and MLTExamples of SELT and DELT Reports

36: 144357321 -89374457 37: 57077374 -156840383 38: -51147222 -155951925 39: -134209369 -89730262 40: -158409603 11736020 41: -115845401 104940941 42: -26600989 151529099 43: 70762409 133893951 44: 135788265 61560546 45: 142843229 -33813554 46: 91011384 -112282891 47: 3519940 -142274912 48: -82670908 -113166204 49: -132445463 -38795028 50: -126744155 49059128 51: -69714891 114251413 52: 13830030 131079489 53: 89194146 94308418 54: 126172671 20541808 55: 111082519 -59242667 56: 51686893 -112695410 57: -26687521 -119150384 58: -91930235 -77518517 59: -118274698 -6047108 60: -96397997 65661556 61: -36590325 108890314 62: 36028264 107251418 63: 92046989 62811899 64: 109633092 -5346859 65: 82977106 -69317271 66: 24069747 -103750376 67: -42650925 -95863128 68: -90421183 -50093465 69: -100851286 14219579 70: -70935887 70990786 71: -13757632 97934989 72: 47207070 85273151 73: 87707929 39194177 74: 92323822 -21078374 75: 60278373 -71293733 76: 5302161 -91900241 77: -50233544 -75610112 78: -84386792 -29902424 79: -84285963 26358168 80: -50923814 70690337 81: 1631135 85947381 82: 52149328 66908605 83: 80785742 21996621 84: 76849797 -30420597 85: 42742995 -69511161 86: -7330501 -80244357 87: -53269543 -59120269




88: -77111045 -15254754 89: -70037749 33546887 90: -35586603 67979467 91: 12040090 74862471 92: 53816912 52157949 93: 73471299 9478629 94: 63809643 -35948584 95: 29297056 -66223624 96: -15948933 -69810635 97: -53929593 -45902681 98: -69901921 -4498435 99: -58086554 37770977100: -23729538 64303260101: 19199555 65036030102: 53686539 40238770103: 66384533 183324104: 52781754 -39099895105: 18768496 -62230121106: -21889127 -60478455107: -53115187 -35062208108: -62878615 3560671109: -47806113 39981572110: -14322352 59980753111: 24064298 56072636112: 52219881 30291255113: 59340181 -6794326114: 43088221 -40434181115: 10326912 -57531387116: -25764342 -51757227117: -50993873 -25869064118: -55731558 9562690119: -38582325 40467493120: -6741513 54866177121: 27007803 47506128122: 49431256 21761301123: 52036483 -11880354124: 34264487 -40089719125: 3552196 -51982250126: -27806689 -43308779127: -47550362 -17960782128: -48261422 13761732129: -30150204 39316123130: -750829 48900351131: 28176307 39187493132: 45372885 14466648133: 44449310 -15227444134: 26248756 -38194360135: -1670780 -45671663136: -28167620 -35175829137: -42966835 -11297574138: -40643944 16304560139: -22589889 36774100



140: 3724316 42360441141: 27816825 31333647142: 40399643 8454743143: 36922319 -17024602144: 19214613 -35129504145: -5420669 -39051459146: -27199991 -27705495147: -37755852 -5956467148: -33344451 17441533149: -16141062 33339541150: 6793355 35827983151: 26375298 24339074152: 35123798 3782090153: 29984280 -17606154154: 13388087 -31501154155: -7883764 -32752917156: -25432130 -21278741157: -32587887 -1909423158: -26892129 17595771159: -10950449 29681106160: 8736726 29895630161: 24449827 18525607162: 30200746 323370163: 24082255 -17458659164: 8823037 -27941217165: -9413185 -27293226166: -23461846 -16093014167: -28013947 1021873168: -21579477 17250763169: -6967264 26334526170: 9932123 24954144171: 22523256 13939124172: 26037225 -2172351173: 19362880 -17010558174: 5364001 -24862333175: -10351015 -22869842176: -21647893 -12061288177: -24263825 3152820178: -17404836 16761282179: -3962504 23532846180: 10690417 21012368181: 20840822 10400894182: 22665276 -3995047183: 15648779 -16492616184: 2733809 -22306848185: -10947289 -19332132186: -20071517 -8917829187: -21186785 4719944188: -14067420 16209366189: -1642712 21150651190: 11132538 17779331191: 19300692 7582374




192: 19797187 -5325888193: 12601517 -15873623194: 680236 -20020576195: -11221413 -16307370196: -18501530 -6356184197: -18434599 5820187198: -11216787 15453177199: 170128 18855246200: 11207771 14872226201: 17621942 5221566202: 17054051 -6194795203: 9898077 -14925167204: -906474 -17634001205: -11056985 -13452953206: -16646776 -4178936207: -15636506 6427946208: -8617691 14257029209: 1513009 16338591210: 10759762 12043280211: 15555401 3231391212: 14191519 -6530970213: 7404916 -13450302214: -2004226 -14951465215: -10313251 -10646010216: -14343279 -2389745217: -12719223 6476381218: -6259602 12514528219: 2350253 13509623220: 9720540 9280578221: 13060091 1665007222: 11249499 -6277861223: 5209137 -11483786224: -2565107 -12062777225: -9017009 -7997882226: -11736771 -1062328227: -9842542 5966444228: -4275276 10391142229: 2655357 10647733230: 8247306 6830311231: 10431510 599788232: 8546750 -5564939233: 3506261 -9311992234: -2623052 -9345328235: -7464145 -5829558236: -9234223 -278926237: -7427254 5115928238: -2896787 8313586239: 2517733 8216134240: 6722006 5029388241: 8208919 82022242: 6532484 -4686191243: 2459734 -7473802



244: -2373085 -7331936245: -6112816 -4444547246: -7427903 7846247: -5894291 4306988248: -2196571 6849735249: 2215560 6732317250: 5680348 4095235251: 6923008 -30848252: 5537585 -4060280253: 2091032 -6498833254: -2110349 -6446889255: -5479360 -3972044

-----------------------------------------------------------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 3770104: 3780 3880 3870 3890 3960 3970 3970 4070112: 4040 4120 4110 4150 4210 4260 4300 4340120: 4380 4420 4400 4490 4510 4550 4550 4600128: 4640 4680 4670 4740 4750 4740 4770 4850136: 4880 4900 4930 5000 4970 5030 5050 5080144: 5130 5090 5180 5210 5220 5260 5300 5300152: 5340 5350 5350 5400 5470 5470 5460 5520160: 5540 5540 5610 5600 5680 5670 5710 5760168: 5720 5760 5800 5790 5830 5910 5880 5900176: 5910 5930 5980 5920 5980 6010 6020 6090184: 6030 6120 6100 6130 6190 6170 6170 6180192: 6200 6220 6280 6240 6320 6310 6320 6350200: 6300 6330 6370 6340 6390 6400 6440 6380208: 6410 6420 6440 6480 6510 6510 6500 6520216: 6510 6520 6590 6570 6550 6560 6600 6570224: 6560 6600 6560 6610 6600 6610 6610 6640232: 6630 6660 6690 6620 6680 6640 6680 6690240: 6650 6710 6680 6640 6700 6680 6720 6720248: 6730 6710 6680 6740 6750 6690 6690 6710




Example DELT Test ResultsA sample of a DELT test report is shown below.

occam# show dsl delt 2

Loop Diag status : CompletedCPE Vendor ID : BDCMSelected protocol : G.992.5-Annex_A

Loop Diagnostics Results:==========================US(NE) attainable bit rate (bps) : 1228000US(NE) loop attenuation (x10 dB) : 10US(NE) signal attenuation (x10 dB) : 0US(NE) snr margin (x10 dB) : 60US(NE) actual Tx Power FE (x10 dBm) : 112DS(FE) attainable bit rate (bps) : 21556000DS(FE) loop attenuation (x10 dB) : 30DS(FE) signal attenuation (x10 dB) : 30DS(FE) snr margin (x10 dB) : 90DS(FE) actual Tx Power FE (x10 dBm) : 20

Loop Diagnostics HLOG Near End (x10 dB):===================================== 0 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : -105 : -6 : 16 : 10 : 18 : 24 : 31 : 35 : 35 : 32 : 28 : 23 : 16 : 7 : 20 : -1 : -10 : -20 : -29 : -38 : -47 : -56 : -65 : -73 : -81 : 30 : -89 : -97 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : 40 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : 50 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : -963 : 60 : -963 : -963 : -963 : -963 :

Loop Diagnostics HLOG Far End (x10 dB):===================================== 0 : -810 : -410 : -440 : -440 : -480 : -480 : -480 : -480 : -520 : -520 : 10 : -520 : -520 : -520 : -520 : -480 : -570 : -540 : -550 : -490 : -490 : 20 : -460 : -490 : -440 : -410 : -390 : -360 : -340 : -320 : -300 : -270 : 30 : -250 : -230 : -210 : -200 : -180 : -160 : -150 : -140 : -120 : -110 : 40 : -110 : -100 : -90 : -90 : -80 : -80 : -70 : -70 : -70 : -60 : 50 : -60 : -60 : -50 : -50 : -50 : -50 : -40 : -40 : -40 : -40 : 60 : -40 : -40 : -30 : -30 : -30 : -30 : -30 : -30 : -20 : -20 : 70 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -10 : -10 : -10 : 80 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : 90 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : 100 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : 110 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : 120 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : -10 : 130 : -10 : -10 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : 140 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : 150 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : 160 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : 170 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -20 : -30 : 180 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 190 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 200 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 210 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 220 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 230 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 240 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 250 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 260 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : -30 : 270 : -30 : -30 : -30 : -30 : -30 : -40 : -40 : -40 : -40 : -40 : 280 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 290 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 300 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 310 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 320 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 330 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 340 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 350 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 360 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : -40 : 370 : -40 : -40 : -40 : -40 : -40 : -50 : -50 : -50 : -50 : -50 : 380 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : 390 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : 400 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 : -50 :



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 :

Loop Diagnostics HLIN Near End:=====================================scaled by (46120)/(2^30) - real part: 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 6741 : 12161 : -580 : 10 : -26362 : -19447 : 20516 : 30495 : -11489 : -32767 : 5034 : 30112 : -2838 : -25109 : 20 : 3580 : 20116 : -5612 : -15177 : 7687 : 10511 : -8916 : -6109 : 9163 : 2158 : 30 : -8337 : 998 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : 40 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : 50 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : 60 : -32768 : -32768 : -32768 : -32768 :scaled by (46120)/(2^30) - imaginary part: 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 1521 : 17942 : 28011 : 10 : 11453 : -23943 : -26008 : 16293 : 32741 : -7696 : -31896 : 3497 : 27783 : -3105 : 20 : -22610 : 4711 : 17670 : -6792 : -12816 : 8448 : 8260 : -9207 : -4041 : 8853 : 30 : 475 : -7599 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : 40 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : 50 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : -32768 : 60 : -32768 : -32768 : -32768 : -32768 :

Loop Diagnostics HLIN Far End:=====================================scaled by (31712)/(2^30) - real part: 0 : 0 : 225 : 162 : 162 : 98 : -98 : -98 : 98 : 66 : 66 : 10 : 66 : -66 : -66 : -66 : 98 : -34 : 0 : 3 : 0 : 120 : 20 : 0 : -130 : -28 : 302 : 219 : -464 : -489 : 508 : 1078 : -279 : 30 : -2019 : -550 : 2757 : 2289 : -2909 : -4903 : 1392 : 7460 : 2171 : -8427 : 40 : -6989 : 6735 : 11429 : -2607 : -14084 : -2897 : 14427 : 8621 : -12519 : -13680 : 50 : 8830 : 17493 : -3857 : -19751 : -1793 : 20282 : 7673 : -19197 : -13260 : 16555 : 60 : 18196 : -12573 : -22187 : 7571 : 24864 : -1825 : -26216 : -4289 : 26079 : 10443 : 70 : -24492 : -16284 : 21531 : 21471 : -17388 : -25720 : 12249 : 28833 : -6436 : -30680 : 80 : 254 : 31199 : 6108 : -30372 : -12192 : 28299 : 17782 : -25106 : -22734 : 20975 : 90 : 26794 : -16075 : -29819 : 10707 : 31844 : -5005 : -32732 : -731 : 32563 : 6407 : 100 : -31428 : -11740 : 29399 : 16622 : -26521 : -20905 : 22988 : 24524 : -18949 : -27446 : 110 : 14513 : 29618 : -9784 : -30973 : 4983 : 31555 : -111 : -31399 : -4614 : 30509 : 120 : 9113 : -28947 : -13333 : 26842 : 17178 : -24193 : -20533 : 21105 : 23420 : -17642 : 130 : -25761 : 13899 : 27526 : -9982 : -28769 : 5937 : 29424 : -1828 : -29507 : -2175 : 140 : 29040 : 6108 : -28054 : -9835 : 26553 : 13352 : -24661 : -16555 : 22291 : 19414 : 150 : -19649 : -21897 : 16647 : 23983 : -13451 : -25602 : 10064 : 26788 : -6547 : -27497 : 160 : 2992 : 27767 : 575 : -27545 : -4114 : 26874 : 7514 : -25840 : -10745 : 24374 : 170 : 13772 : -22540 : -16555 : 20358 : 19057 : -17903 : -21194 : 15171 : 22972 : -12249 : 180 : -24428 : 9161 : 25519 : -5987 : -26168 : 2706 : 26397 : 511 : -26254 : -3730 : 190 : 25681 : 6881 : -24766 : -9886 : 23471 : 12732 : -21843 : -15372 : 19926 : 17754 : 200 : -17677 : -19833 : 15248 : 21605 : -12580 : -23067 : 9721 : 24212 : -6795 : -24947 : 210 : 3771 : 25341 : -686 : -25370 : -2365 : 25036 : 5396 : -24333 : -8264 : 23287 : 220 : 11044 : -21910 : -13632 : 20234 : 16043 : -18246 : -18180 : 16062 : 20062 : -13632 : 230 : -21617 : 11034 : 22915 : -8287 : -23869 : 5434 : 24428 : -2524 : -24702 : -413 : 240 : 24622 : 3345 : -24155 : -6178 : 23417 : 8970 : -22288 : -11568 : 20895 : 14030 : 250 : -19172 : -16275 : 17232 : 18269 : -15070 : -20018 : 12681 : 21481 : -10102 : -22638 : 260 : 7415 : 23455 : -4623 : -23993 : 1828 : 24174 : 1030 : -23958 : -3812 : 23490 : 270 : 6576 : -22667 : -9237 : 21531 : 11762 : -20123 : -14112 : 18463 : 16249 : -16497 : 280 : -18151 : 14341 : 19779 : -11995 : -21134 : 9476 : 22215 : -6862 : -22982 : 4191 : 290 : 23424 : -1424 : -23541 : -1332 : 23322 : 4054 : -22813 : -6684 : 21964 : 9222 : 300 : -20835 : -11664 : 19429 : 13915 : -17754 : -15947 : 15855 : 17744 : -13759 : -19293 : 310 : 11470 : 20606 : -9050 : -21605 : 6522 : 22288 : -3911 : -22702 : 1240 : 22781 : 320 : 1396 : -22549 : -4048 : 22047 : 6589 : -21204 : -9031 : 20123 : 11317 : -18752 : 330 : -13486 : 17130 : 15435 : -15289 : -17194 : 13232 : 18682 : -11082 : -19945 : 8713 : 340 : 20895 : -6299 : -21573 : 3755 : 21939 : -1214 : -22034 : -1332 : 21830 : 3879 : 350 : -21325 : -6340 : 20555 : 8719 : -19519 : -10952 : 18167 : 12999 : -16644 : -14911 : 360 : 14853 : 16577 : -12923 : -18053 : 10773 : 19258 : -8532 : -20228 : 6175 : 20886 : 370 : -3733 : -21283 : 1284 : 21360 : 1163 : -21182 : -3615 : 20692 : 6026 : -19932 : 380 : -8293 : 18940 : 10500 : -17690 : -12484 : 16183 : 14319 : -14497 : -15944 : 12592 : 390 : 17315 : -10554 : -18479 : 8398 : 19375 : -6108 : -20005 : 3765 : 20377 : -1408 :




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 :

Loop Diagnostics QLN Near End (x10 dBm/Hz):===================================== 0 : -1505 : -1175 : -1180 : -1190 : -1170 : -1195 : -1180 : -1170 : -1170 : -1125 : 10 : -1150 : -1135 : -1145 : -1130 : -1125 : -1120 : -1150 : -1135 : -1045 : -1120 : 20 : -1140 : -1125 : -1115 : -1095 : -1155 : -1140 : -1155 : -1140 : -1140 : -1155 : 30 : -1180 : -1185 : -1190 : -1185 : -1185 : -1185 : -1185 : -1185 : -1170 : -1190 : 40 : -1200 : -1180 : -1190 : -1180 : -1180 : -1180 : -1190 : -1180 : -1175 : -1180 : 50 : -1175 : -1195 : -1180 : -1190 : -1190 : -1180 : -1180 : -1195 : -1190 : -1200 : 60 : -1180 : -1185 : -1205 : -1175 :

Loop Diagnostics QLN Far End (x10 dBm/Hz):=====================================



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 :

Loop Diagnostics SNR Near End (dB):===================================== 0 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 28 : 34 : 40 : 10 : 42 : 45 : 47 : 48 : 50 : 51 : 51 : 51 : 52 : 52 : 20 : 53 : 53 : 53 : 53 : 53 : 52 : 51 : 49 : 47 : 44 : 30 : 39 : 34 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 40 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 50 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 95 : 60 : 95 : 95 : 95 : 95 :

Loop Diagnostics SNR Far End (dB):===================================== 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 10 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 20 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 0 : 30 : 0 : 0 : 0 : 23 : 25 : 27 : 28 : 30 : 31 : 33 : 40 : 34 : 35 : 37 : 38 : 39 : 40 : 41 : 42 : 42 : 43 : 50 : 44 : 45 : 46 : 46 : 47 : 48 : 48 : 49 : 49 : 50 : 60 : 50 : 51 : 51 : 51 : 52 : 52 : 53 : 53 : 53 : 53 : 70 : 53 : 53 : 54 : 54 : 54 : 54 : 54 : 54 : 55 : 55 : 80 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 90 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 100 : 55 : 55 : 55 : 55 : 55 : 55 : 55 : 54 : 54 : 54 : 110 : 54 : 54 : 54 : 54 : 54 : 54 : 54 : 54 : 54 : 54 : 120 : 54 : 54 : 55 : 54 : 54 : 54 : 54 : 54 : 55 : 54 :




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 :




BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection Tests

Introduction

Chapter 43POTS Line Testing- MLT, Ringer and Tone Detection Tests

In This Chapter:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807MLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808Off-Hook Tone Generator Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821Ring Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822Tone Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823

IntroductionOccam 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection TestsMLT

MLTMLT 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.

BLCs That Feature MLTThe following BLC 6000 blades support MLT:

BLC BLC 6150-01

BLC 6151-01

BLC 6152

BLC 6244

BLC 6246

BLC 6252-03

SNMP SupportThe 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.



MLT

Showing the Tip-Ring StatusThe show voice tip-ring-status [port-number] command to obtain tip-ring status. This command retrieves parameters that can be retrieved non-intrusively. If a port number is not specified the status of all ports will be shown.occam# show voice tip-ring-status 1Voice Port 1: Alarm: None Hook State: Onhook Transversal Current: 0.1 mA Longitudinal Current: 0.7 mA Tip Voltage: -7.7 V Ring Voltage: -42.5 V Tip-Ring Voltage: 36.6 V Vdd: 26.4 V

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 1Voice Port 1: Alarm: None Hook State: Offhook (must be onhook to get complete status) Transversal Current: 27.0 mA

If alarm is detected, only alarm information is reported. The following example shows sample output of a GNDK detection.occam# show voice tip-ring-status 1Voice Port 1:Alarm: GNDK fault Hook State: n/a Transversal Current: n/a Longitudinal Current: n/a Tip Voltage: n/a Ring Voltage: n/a Tip-Ring Voltage: n/a Vdd: n/a



Table 43-1 describes how to interpret this command.

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 onhookOffhook - 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.



MLT

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 +/- 2VThis 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.

Field Description



Performing a Metallic Loop TestUse the test voice mlt {port-number} command to perform a Metallic Loop Test (MLT), specifying an interface number. This command performs a suite of tests that help determine the integrity of a POTS line.

The port number must be specified. As this command is intrusive, the port will need to be disabled (shutdown) first. The following example performs a MLT on interface 1 and shows sample output. Table 43-2 describes how to interpret this command:Occam# test voice mlt 1This voice port is not shutdown. Continuing will temporarily shutdown the voice port and will interrupt subscriber service. Do you wish to continue? [y/N] yShutting down voice port....Running test...

Time: Wed Apr 26 13:13:39 2006Alarm: NoneHook State: OnhookVdd: 26.4 V

Active Mode Voltages: VDCtr: 36.9 Vdc VDCtg: -8.4 Vdc VDCrg: -45.3 Vdc VACtr: 0.0 Vrms VACtg: 0.0 Vrms VACrg: 0.9 Vrms

High Impedance Mode Voltages: VDCtr: 0.6 Vdc VDCtg: -1.2 Vdc VDCrg: -1.8 Vdc VACtr: 0.1 Vrms VACtg: 0.0 Vrms VACrg: 0.0 Vrms

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



MLT

Hazardous Potential Test: Result: Passed

GR-909 Foreign EMF Test: Result: Passed

Fuse Test: Tip Fuse: Passed Ring Fuse: Passed

GR-909 Resistive Fault Test: Result: Passed

GR-909 Receiver Offhook Test: Result: Passed Resistance 1: high (not offhook) Resistance 2: high (not offhook) Difference: n/a

GR-909 Ringer Test: Result: Passed REN: 1.1

Errors: NoneRe-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:

occam# test voice mlt 1This voice port is not shutdown. Continuing will temporarily shutdown the voice port and will interrupt subscriber service. Do you wish to continue? [y/N] yShutting down voice port....Running test...Time: Fri Jun 9 12:19:04 2006Alarm: GNDK faultHook State: n/aVdd: n/a

Active Mode Voltages: VDCtr: n/a VDCtg: n/a VDCrg: n/a VACtr: n/a VACtg: n/a VACrg: n/a




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

GR-909 Hazardous Potential Test: Result: Passed


Fuse Test: Tip Fuse: Aborted Ring Fuse: Aborted

GR-909 Resistive Fault Test: Result: Aborted

GR-909 Receiver Offhook Test: Result: Aborted Resistance 1: n/a Resistance 2: n/a Difference: n/a

GR-909 Ringer Test: Result: Aborted REN: n/a

Errors: Alarm detectedRe-enabling voice port....



MLT

Table 43-2 describes how to interpret this command:

Table 43-2: “test voice mlt” 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 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

Offhook - Line is offhook

Vdd Internal voltage with typical value of 26 V +/- 2 V.

Active Mode Voltages

In active mode, the SLIC drives the tip/ring in a normal "no shutdown" state. Thus, tip/ring DC voltage measurements should reflect normal battery voltage, while the AC voltage measurements should be 0 volt. Active mode measurements are not available when alarm is detected. VDCtr: Tip to Ring DC voltageVDCtg: Tip to Ground DC voltageVDCrg: Ring to Ground DC voltageVACtr: Tip to Ring AC voltageVACtg: Tip to Ground AC voltageVACrg: Ring to Ground AC voltage

High Impedance Mode Voltages

In high impedance mode, the voltage measurements repre-sent the foreign voltage. In normal condition, all DC and AC voltage measurements should be 0 volt. If a huge capacitance is present on the line, a small DC voltage reading may be observed. A telephone ring capacitor is one possible source.VDCtr: Tip to Ring DC foreign voltageVDCtg: Tip to Ground DC foreign voltageVDCrg: Ring to Ground DC foreign voltageVACtr: Tip to Ring AC foreign voltageVACtg: Tip to Ground AC foreign voltageVACrg: Ring to Ground AC foreign voltage



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]

CEQtg = Ctg + (Ctr*Crg)/(Ctr+Crg)[tip to gnd with ring in high impedance]

CEQrg = Crg + (Ctr*Ctg)/Ctr+Ctg) [ring to gnd with tip in high impedance]

Note that in the absence of Ctr, CEQtg = Ctg and CEQrg = Crg. Capacitance measurements are not available if the fuse test fails or an alarm is present.

Figure 43-1: Capacitance Network

Field Description

Ctr

CrgCtg

TipRing

Gnd



MLT

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

GR-909 Hazardous Potential Test

This test detects the presence of hazardous foreign voltage between T-G (tip to ground), R-G (ring to ground) or T-R (tip to ring). Hazardous foreign voltage is defined to be voltage greater than 50 volts RMS or 135 volts DC. This test reports passed/failed. Refer to the high impedance mode voltage section for the foreign voltage measurements.

GR-909 Foreign EMF Test

This test fails if the T-G or R-G ac voltage is greater than 10 volts or the T-G or R-G dc voltage is greater than 6 volts. Refer to the high impedance mode voltage section for the foreign voltage measurements.

Fuse Test The tip and ring leads are protected by fuses. This test deter-mines if any of the fuses are blown. This test returns pass/fail for tip and ring. This test is not performed if alarm is present.

GR-909 Resistive Fault Test

This test fails if the T-R, T-G or R- G resistance is less than 150 KOhm. This test is not performed if hazardous potential test, FEMF test or fuse test fails. This test returns passed/failed. Refer to resistance section for the measured values.

GR-909 Receiver Offhook Test

This test fails if a non-linearity in the T-R DC resistance is greater than 15%. Non-linearity is defined as the difference in resistance measured at two different current levels. This test is not performed if fuse test fails or alarm is present. This test returns the DC resistances at two different operating points and the percent difference between the two DC resistances.

GR-909 Ringer Test

This test fails when the equivalent ringer count across tip and ring is less than 0.175 REN or greater than 5 REN. This test will not run if fuse test fails or alarm is present. This test reports passed/fail and the REN number.

Field Description

Rtr

Rrg Rtg

TipRing

Gnd



Viewing the Results of the MLT Test in a Log FileThe results of the MLT test (test voice mlt) are saved to a log file so it can be viewed at a later time. Use the show voice mlt-history [port-number] command to view this file. If the interface number is not specified, history of all interfaces will be displayed. The following example shows sample output from this command:

occam# show voice mlt-history 1Voice Port 1:

Time: Wed Apr 26 13:13:39 2006Alarm: NoneHook State: OnhookVdd: 26.4 V

Active Mode Voltages: VDCtr: 36.9 Vdc VDCtg: -8.4 Vdc VDCrg: -45.3 Vdc VACtr: 0.0 Vrms VACtg: 0.0 Vrms VACrg: 0.9 Vrms


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

GR-909 Hazardous Potential Test: Result: Passed




MLT

Fuse Test: Tip Fuse: Passed Ring Fuse: Passed

GR-909 Resistive Fault Test: Result: Passed

GR-909 Receiver Offhook Test: Result: Passed Resistance 1: high (not offhook) Resistance 2: high (not offhook) Difference: n/a

GR-909 Ringer Test: Result: Passed REN: 1.1

Errors: None

Detecting a LoopThe 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.



Testing the Loop LengthLoop length estimate is based on tip-ring capacitance measurement. You may specify the loop length multiplier. If not supplied, loop length multiplier of 83 nF/ mile will be used. This test will not be available if fuse test fails or alarm is present. This test is intrusive and will be available in shutdown state only.

The command test voice loop-length {voice-port-number} [capacitance factor] returns the loop length estimate. The optional [capacitance factor] parameter is nF/mile and the parameters are from 10 to 200. If unspecified, the factory default value of 83 is used.

Sample output is shown below. In this example port number one is tested and the capacitance factor is 79 nF/mile:occam# test voice loop-length 1 79This voice port is not shutdown. Continuing will temporarily shutdown the voice port and will interrupt subscriber service. Do you wish to continue? [y/N] yShutting down voice port....Running test... Capacitance factor: 79 nF/mile Loop capacitance: 32 nF Loop length: 2170 ft

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 79This voice port is not shutdown. Continuing will temporarily shutdown the voice port and will interrupt subscriber service. Do you wish to continue? [y/N] yShutting 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



Off-Hook Tone Generator Diagnostic

Off-Hook Tone Generator DiagnosticThe off-hook tone generator diagnostic allows you to test the path going from the DSP through the Subscriber Line Interface Circuit (SLIC) and to the phone. You can enable an off-hook tone, and then pick up the phone and listen for the tone. If no tone is heard there is most likely a problem with the DSP or SLIC. If the tone is heard then the problem is most likely a network issue (no communication between the call-agent and the endpoint). The off-hook tone will continue until the test is disabled.

Figure 43-3: 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}

TO

NETWORK

OFF HOOK TONE

PHONE ATCUSTOMERPREMISES

SLIC/POTS

DSPHOSTPHYSICALPOTS LINE

BLC WITH HD POTS PORTS


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection TestsRing Test

Ring TestThe 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.

Figure 43-4: Ring Test

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}

TO

NETWORK

RING SIGNAL


SLIC/POTS





Tone Detection

Tone DetectionThe 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.

Figure 43-5: Tone Detection

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}

TO

NETWORK


SLIC/POTS



C. COMMAND "show voicedigits" SHOWS DTMF TONES

A. DSP DTMFDETECTOR ENABLED

B. DTMF TONESSENT FROM

PHONE TO DSP


BLC 6000 System Configuration and Installation Guide- Release 5.5Chapter 43: POTS Line Testing- MLT, Ringer and Tone Detection TestsTone 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 5Detected digitsdigit 1 = 5digit 2 = 2digit 3 = 6digit 4 = 5digit 5 = 6digit 6 = 4digit 7 = 6digit 8 = *digit 9 = #digit 10 = n/adigit 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 5Voice Port: 5Transmit Power: -70.7 dBm0Receive Power: <-71 dBm0Occam#


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix A: Safety Warnings

Introduction

Appendix ASafety Warnings

In this Appendix:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825Restricted Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825Protective Earthing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825Safety Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826Equipment Interconnection Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827Preventing Electrostatic Discharge Damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827FCC Part 15 Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828FCC Part 68 Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829IC CS-03 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830Laser Transmitter Operation and Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . 831

IntroductionThe 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 AccessThe 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 EarthingProtection 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix A: Safety WarningsSafety Considerations

Safety Considerations This section contains safety warnings that you should be aware of before installing the BLC platform.

Safety WarningsFailure to adhere to the safety warnings outlined in this publication may cause bodily injury. A warning symbol precedes each warning statement.

Safety with Electricity

Warning: Before working on equipment that is connected to power lines, remove jewelry, including necklaces, rings, and watches. Metal objects heat up when connected to power and ground and can cause serious burns or become welded to the terminals.

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.

Warning: Do not work on the system or connect or disconnect cables during periods of lightning activity.

Warning: Do not work alone if potentially hazardous conditions exist.

Warning: Never assume that electricity is disconnected from a circuit. Always check.



Equipment Interconnection Points

Equipment Interconnection PointsInterconnection points for the BLC system are defined as (SELV) for Ethernet and Console interfaces and (TNV) for ADSL interfaces.

Connect SELV circuits on this equipment only to other circuits that comply with the requirements of SELV circuits as defined in CSA C22.2 No. 950, UL 1950, EN 60950, AS/NZS 3260 or IEC 950.

Connect TNV circuits on this equipment only to other circuits that comply with the requirements of TNV circuits as defined in CSA C22.2 No. 950, UL 1950, EN 60950, AS/NZS 3260 or IEC 950.

Preventing Electrostatic Discharge DamageMany BLC components are sensitive to damage from electrostatic discharge (ESD). ESD occurs when electronic printed circuit cards are handled improperly and can result in intermittent or complete failures.

Caution: Always follow ESD prevention procedures when handling the BLC.

Ensure that the BLC chassis electrically connected to earth ground.

To safely channel unwanted ESD voltages to ground, wear an ESD-preventive wrist strap and ensure that it makes good skin contact. Connect the clip to an unpainted surface at the rear of the chassis frame or if the rear of the chassis frame is not accessible, then remove the front bezel and attach the ESD strap to either of the ball studs used to secure the bezel in place. To properly guard against ESD damage and shocks, the cord and wrist strap must operate effectively.

If no wrist strap is available, ground yourself by touching an unpainted metal part of the chassis.

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).

!

!


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix A: Safety WarningsFCC Part 15 Statement

FCC Part 15 StatementThe following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

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:

Turn the television or radio antenna until the interference stops.

Move the equipment to one side or the other of the television or radio.

Move the equipment farther away from 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.



FCC Part 68 Compliance

FCC Part 68 ComplianceThis equipment complies with Part 68 of the FCC rules. On the Approvals Label located on the bottom of the BLC is a label that contains, among other information, the FCC registration number. If requested, you must provide this information to the telephone company.

An FCC-compliant cord and modular plug is provided with this equipment. This equipment is designed for connection to the telephone network or premises wiring using a compatible modular jack that is Part 68 compliant. See the installation instructions for details.

This equipment cannot be used on telephone company-provided coin service. Connection to party line service is subject to state tariffs.

If this equipment causes harm to the telephone network, the telephone company will notify you in advance that it may be necessary to temporarily discontinue service. If advance notice is not practical, the telephone company will notify you as soon as possible. Also, you will be advised of your right to file a complaint with the FCC.

The telephone company may make changes in its facilities, equipment, operations, or procedures that could affect the operation of this equipment. If this happens, the telephone company will provide advance notice for you to make the necessary modifications to maintain uninterrupted service.

This device does not include any upgradable parts.

This equipment uses Universal Service Order Code (USOC) jacks.


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix A: Safety WarningsIC CS-03 Warnings

IC CS-03 WarningsThe following information applies to models used in Canada:

Ringer Equivalence NumberThe Ringer Equivalence Number (REN) assigned to each terminal device provides an indication of the maximum number of terminals allowed to be connected to a telephone interface. The termination on an interface may consist of any combination of devices, and is subject only to the requirement that the sum of the Ringer Equivalence Numbers of all the devices does not exceed 5.

Equipment Attachment LimitationsThe Industry Canada label located on the bottom of the BLC identifies certified equipment. This certification means that the equipment meets certain telecommunications network protective, safety and operational, requirements as detailed in the appropriate Terminal Equipment Technical Requirement Documents. The Department does not guarantee the equipment will operate to the user's satisfaction.

Users should ensure that it is permissible to be connected to the facilities of the local telecommunications company before installing this equipment. The equipment must also be installed using an acceptable method of connection. The customer should be aware that compliance with the above conditions may not prevent degradation of service in some situations.

Repairs to certified equipment should be coordinated by a representative designated by the supplier. Any repairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommunications company cause to request the user to disconnect the equipment.

Users should ensure for their own protection that the electrical ground connections of the power utility, telephone lines, and internal metallic water pipe system, if present, are connected together. This precaution may be particularly important in rural areas.

Caution: Users should not attempt to make connections themselves, but should contact the appropriate electric inspection authority, or electrician, as appropriate. !



Laser Transmitter Operation and Safety Precautions

Laser Transmitter Operation and Safety Precautions Precautions for Safety

Warning: The laser radiation emitted from the edge of the receptacle or the end of the optical fiber is invisible and is hazardous to human eyes. Avoid looking into the receptacle or optical fiber end when the device is being operated.

Transmitter OperationThe 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.

In viewing the laser beam, we strongly recommend the use of an infrared-to-visible converter such as a fluorescent screen or a TV camera.

Operating the laser transmitter module outside of its absolute maximum ratings may cause the device to fail and may be a safety hazard.

Do not open the housing of the device.

Do not strongly pull or bend the optical fiber.

The laser transmitter does not incorporate any external adjustment features.

An “Identification and Certification Label”, identifying the laser radiation classi-fication, is attached to the individual laser module.

MANUFACTURED IN THE USA

This product complies with 21 CFR 1040.10 and 1040.11

Meets Class I laser safety requirements.


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix A: Safety WarningsLaser Transmitter Operation and Safety Precautions


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix B: BLC 6012 Chassis Wiring Arrangements

Introduction

Appendix BBLC 6012 Chassis Wiring Arrangements

In this Appendix:Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833H Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834FTTX Wiring Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837Gateway Chassis Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845POTS Wiring Arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847Ring Wiring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854

IntroductionThe 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.

Shielded Cat 6 CablesSome BLCs require a shielded CAT 6 cable to comply with the FCC Part 15 emissions standards. This cable is terminated by shielded RJ-45 connectors on both ends and the cable shield material is tied to both connectors. Figure B-1 shows the shielding on the RJ-45 connector.

Figure B-1: Shielded RJ-45 Connector


BLC 6000 System Configuration and Installation Guide- Release 5.5 Appendix B: BLC 6012 Chassis Wiring ArrangementsH Wiring Configuration

H Wiring ConfigurationThe 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:

H Wiring Configuration In Full BLC 6012 ChassisA fully populated BLC 6012 chassis should be configured as follows:

One of the 51-inch cables connects the blade in Slot 1/ XG1 to the blade in Slot 12/ XG2.

The eleven 6-inch cables connect Slots 1 through 12 as follows:

The blade in Slot 1/XG2 connects to the blade in Slot 2/XG1






The blade in Slot 7/XG2 connects to the blade in Slot8/XG1



Cable Description Quantity Occam Part Number

51-inch Cat-6 Cables - Straight Shielded RJ-45 to RJ-45, White.One cable is used to connect bookend to bookend blades in the BLC 6012 chassis. the other cable may be used to bridge gaps in a partially filled BLC 6012 chassis.

2 725203-0004

6-inch Cat-6 Cables - Straight Shielded RJ-45 to RJ-45, White.These are used to connect adjacent blades in the BLC 6012 chassis.

11 725203-0005



H Wiring Configuration



Figure B-1: BLC 6012-H Wiring Arrangement in Full Chassis


BLC 6000 System Configuration and Installation Guide- Release 5.5 Appendix B: BLC 6012 Chassis Wiring ArrangementsH Wiring Configuration

H Wiring Configuration In Partially Full BLC 6012 ChassisA partially populated BLC 6012 chassis should be configured as follows:

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.

Figure B-2: BLC 6012-H Wiring Arrangement in Partially Full Chassis



FTTX Wiring Configuration

FTTX Wiring ConfigurationThe 785440 FTTX Cabling Kit consists of the following parts:

The connection from the front of the chassis requires a five foot Ethernet cable. The preferred wiring of the chassis for the 10 GigE transport is to connect each of the internal blades with 1 Gig protected for single failure. The F-Wiring is designed to implement these requirements. It also supports POTS wiring as well.

Backbone Transport WiringThe backbone EPS ring is implemented using BLC 6314s or BLC 6312s by connecting XG1 port on the front of the blade from Slot 1 to Slot 12. Thus whether the EPS ring is 10 Gig Fiber or 1 Gig Fiber, the connection between the bookends is implemented using the first 10 Gig copper port.


T568B Cat 5e Cord –Straight Shielded 5 ft. Red RJ-45 to RJ-45

1 725143-004

T568B Cat 5e Cord –Straight 18 in. Green RJ-45 to RJ-45

4 725116

T568B Cat 5e Cord –Straight 12 in. Blue RJ-45 to RJ-45

6 725101

T568B Cat 5e Cord –Straight 6 in. Orange RJ-45 to RJ-45

5 725100


BLC 6000 System Configuration and Installation Guide- Release 5.5 Appendix B: BLC 6012 Chassis Wiring ArrangementsFTTX Wiring Configuration

Figure B-3: BLC 6012-F F-Wired Chassis Backbone 631x Blades

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.

Figure B-4: Shielded Cable Tied To Top of BLC 6012 Chassis




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.

Figure B-5: BLC 6012-F F-Wired Chassis Backbone Other Blades

First Subtended RingThe first subtended Ring in the chassis consists of Slots 2 and 3. These are connected to Slot 1 using Port 5 PG1 to Slot 2 Port 2. These are connected to Slot 12 using Port 1 PG2 to Slot 3 Port 1. The connection between Slot 2 is from Port 1 to Slot 3 to Port 2. This is shown in Figure B-6.

Figure B-6: BLC 6012-F F-Wired Chassis - Subtended Ring 1

12 11 10 9 8 7 5 4 3 2 16

CHASSIS SLOT NUMBERS

654321

ETHERNETPORT

NUMBERS

1

12 11 10 9 8 7 5 4 3 2 16

1 12

5


654321

ETHERNETPORT

NUMBERS

1

2



Second Subtended RingThe second subtended Ring in the chassis consists of Slots 4 and 5. These are connected to Slot 1 using Port 4 PG1 to Slot 4 Port 2. These are connected to Slot 12 using Port 2 PG2 to Slot 5 Port 1. The connection is between Slot 4 Port 1 to Slot 5 Port 2. These connections are highlighted in Figure B-7. The first subtended ring is also shown in this figure with cables the cables drawn in light grey.

Figure B-7: : BLC 6012-F F-Wired Chassis - Subtended Ring 2

Subtended Ring 3The 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.


12 11 10 9 8 7 5 4 3 2 16

2

4


654321

ETHERNETPORT

NUMBERS 22

1 1

12 11 10 9 8 7 5 4 3 2 16

3 3


654321

ETHERNETPORT

NUMBERS 212

1




Forth Subtended RingThe forth subtended Ring in the chassis consists of Slots 8 and 9. These are connected to Slot 1 using Port 2 PG1 to Slot 8 Port 2. These are connected to Slot 12 using Port 4 PG2 to Slot 9 Port 1. The connection is between Slot 8 Port 1 to Slot 9 Port 2. This is shown in Figure B-9. The first, second and third subtended rings are also shown in this figure with cables the cables drawn in light grey.


Subtended Ring 5The 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.

12 11 10 9 8 7 5 4 3 2 16

4

2


654321

ETHERNETPORT

NUMBERS22

1 1




12 11 10 9 8 7 5 4 3 2 16

5

1


654321

ETHERNETPORT

NUMBERS2

12




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

Commands for FTTx Wiring Configuration

Configuringa VPT

Configures the BLC in slot 1 to be a VPT on PG1 in a FTTx wiring configuration


Configures the BLC in slot 12 to be a VPT on PG2 in a FTTx wiring configuration




Configuringa VPS

Configures the BLC in slot 1 as a VPS in a FTTx wiring configuration


Configures the BLC in slot 12 as a VPS in a FTTx wiring configuration




Gateway Chassis Wiring Configuration

Gateway Chassis Wiring ConfigurationOccam Part Number 535101 is a Cabling kit that when installed on a base BLC 6012 Chassis will result in a BLC 6012-G Gateway Configuration used primarily at a Central Office Terminal.

The 535101 Gateway Cabling Kit consists of the following parts:

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).

Figure B-12: BLC 6012-G Gateway Wiring Arrangement

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


T568B Cat 5e Cord –Straight 2 ft. Red, RJ-45 to RJ-45

1 725102

T568B Cat 5e Cord –Straight 6 in. Orange, RJ-45 to RJ-45

11 725100

12 11 10 9 8 7 5 4 3 2 16


654321

ETHERNETPORT

NUMBERS

1


BLC 6000 System Configuration and Installation Guide- Release 5.5 Appendix B: BLC 6012 Chassis Wiring ArrangementsGateway Chassis Wiring Configuration

Ethernet ports for connection to other communications systems such as an ISP Router, Video Head-end systems or management networks.

Commands for Gateway Configuration

Configuringa VPT





Configuringa VPS






Configures a BLC in an interior slot (2-11) as a VPS in a Gateway wiring configuration.

load network 6012G-vps



POTS Wiring Arrangement

POTS Wiring ArrangementOccam Part Number 535108 is a Cabling kit that when installed on a base BLC 6012 Chassis will result in a BLC 6012-P POTS Configuration used primarily as a Remote Terminal.

The 535108 POTS Cabling Kit consists of the following parts:

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.


T568B Cat 5e Cord –Straight 2 ft. Red RJ-45 to RJ-45

1 725102

T568B Cat 5e Cord –Straight 18 in. Green RJ-45 to RJ-45

4 725116

T568B Cat 5e Cord –Straight 12 in. Blue RJ-45 to RJ-45

4 725101


6 725100


BLC 6000 System Configuration and Installation Guide- Release 5.5 Appendix B: BLC 6012 Chassis Wiring ArrangementsPOTS Wiring Arrangement

Figure B-13: BLC 6012-P 1x1GbE EPS Connection Path

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.

12 11 10 9 8 7 5 4 3 2 16


654321

ETHERNETPORT

NUMBERS

1




6012-P First Subtended Ring The first subtended ring in the 6012-P wiring arrangement, as shown in Figure B-14 is formed by connecting the following slots and ports to connect three slots between the bookends:

Slot 1/ Port 4 to Slot 2/ Port 2

Slot 2 /Port 1 to Slot 3/ Port 2



Figure B-14: BLC 6012-P First Subtended Ring

6012-P Second Subtended RingThe second subtended ring, as shown in Figure B-15, is formed by connecting the following slots and ports:

Slot 1 / Port 3 to Slot 5/ Port 2

Slot 5 / Port 1 to Slot 6 / Port 2


12 11 10 9 8 7 5 4 3 2 16


654321

ETHERNETPORT

NUMBERS

11

22

4

21



Figure B-15: BLC 6012-P Second Subtended Ring

12 11 10 9 8 7 5 4 3 2 16


654321

ETHERNETPORT

NUMBERS

11

2 23




6012-P Third Subtended RingThe third subtended ring, as shown in Figure B-16, is formed by connecting the following slots and ports to connect two slots between the bookends:




Figure B-16: BLC 6012-P Third Subtended Ring

12 11 10 9 8 7 5 4 3 2 16


654321

ETHERNETPORT

NUMBERS

122

3

1

2



6012-P Fourth Subtended RingThe fourth subtended ring, as shown in Figure B-17, is formed by connecting the following slots and ports to connect the final three slots between the bookends:





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.

Figure B-17: BLC 6012-P Fourth Subtended Ring

Commands for POTS Configuration(The POTS Wiring configuration is described in Appendix B, BLC 6012 Chassis Wiring Arrangements on page 847)

Configuringa VPT





12 11 10 9 8 7 5 4 3 2 16


654321

ETHERNETPORT

NUMBERS

1 1

2

4

1

2 21




Configuringa VPS






Configures a BLC in an interior slot (2-11) as a VPS in a POTS wiring configuration.

load network 6012P-vps


BLC 6000 System Configuration and Installation Guide- Release 5.5 Appendix B: BLC 6012 Chassis Wiring ArrangementsRing Wiring Configuration

Ring Wiring ConfigurationOccam Part Number 535100 is a Cabling kit that when installed on a base BLC 6012 Chassis will result in a BLC 6012-R Ring Configuration used primarily as a Remote Terminal. The 535100 Ring Cabling Kit consists of the following parts:

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.


T568B Cat 5e Cord –Straight 2 ft. Red RJ-45 to RJ-45

1 725102


22 725100



Ring Wiring Configuration

Figure B-18: BLC 6012-R Ring Wiring Arrangement

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.

The unrestricted Ports 3 and 4 on Slots 1 and 12 are available to connect a subtended link to other chassis co-located or for connecting to other Ethernet services at this site. Port 3 and 4 can be used in Slots 2 through 11 for other Ethernet services if required.

Commands for Ring Configuration

Configuringa VPT





Configuringa VPS






Configures a BLC in an interior slot (2-11) as a VPS in a Ring wiring configuration.

load network 6012R-vps

12 11 10 9 8 7 5 4 3 2 16


ETHERNETPORT

NUMBERS

1

556

234

1

5

34

1

5

34

1

5

34

1

5

34

1

5

34

1

5

34

1

5

34

1

5

34

1

5

34

1

5

34

1

5

34

22222222 2 2 2

6666666 6 6 6 6


BLC 6000 System Configuration and Installation Guide- Release 5.5 Appendix B: BLC 6012 Chassis Wiring ArrangementsRing Wiring Configuration


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix C: Decimal to Hexadecimal Conversion Table

Decimal to Hexadecimal Conversion Table

Appendix CDecimal to Hexadecimal Conversion Table

In this Appendix:Decimal to Hexadecimal Conversion Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857

Decimal to Hexadecimal Conversion TableThe BLC 6001 and the BLC 6012 chassis use hexadecimal numbering for the shelf selector. Hexadecimal numbering is based on sixteen digits. The following table shows how to convert decimal numbers to hexadecimal numbers.

Decimal Number

Hexadecimal 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


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix C: Decimal to Hexadecimal Conversion TableDecimal to Hexadecimal Conversion Table

250 FA

251 FB

252 FC

253 FD

254 FE

255 FF

Decimal Number

Hexadecimal Number


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix D: Installing a Cable Guard on a BLC 6012 Chassis

Installing a Cable Guard

Appendix D0Installing a Cable Guard on a BLC 6012 Chassis

In this Appendix:Installing a Cable Guard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859

Installing a Cable GuardA cable guard may be attached to BLC 6012 chassis designated for use in a Central Office.

Figure D-1: Cable Guard


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix D: Installing a Cable Guard on a BLC 6012 ChassisInstalling 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.

Figure D-2: Peg for Cable Guard on 6012 Chassis

Figure D-3 shows the corresponding hole on the cable guard.

Figure D-3: Hole for Peg on Cable Guard


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix 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).

Figure D-4: Cable Guard on 6012 Chassis


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix D: Installing a Cable Guard on a BLC 6012 ChassisInstalling a Cable Guard

Figure D-5: Cable Guard on 6012 Chassis With Fan Filter Exposed


BLC 6000 System Configuration and Installation Guide- Release 6.0Appendix E: Replacing a Fan Filter on a BLC 6012 Chassis

Appendix EReplacing 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 43410/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


BLC 6000 System Configuration and Installation Guide- Release 6.0Appendix 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.


BLC 6000 System Configuration and Installation Guide- Release 6.0 Appendix E: Replacing a Fan Filter on a BLC 6012 Chassis


BLC 6000 System Configuration and Installation Guide- Release 6.0Appendix F: Shelf Hardware Upgrade Instructions

Pre-upgrade Checklist

Appendix F0Shelf Hardware Upgrade Instructions

In this Appendix:Pre-upgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867Upgrade 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.

Depending on your network configuration, Ethernet ports may need to be moved on the shelf during the upgrade procedure. Customer Service can also provide assistance with this procedure.

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.


BLC 6000 System Configuration and Installation Guide- Release 6.0 Appendix F: Shelf Hardware Upgrade InstructionsUpgrade Procedure

Upgrade ProcedureIf 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.

4 Remove the existing blade in slot 12.

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.

6 Insert the new BLC 6640-01 or BLC 6440-01 in Slot 12.

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-standbyThe following IGs will be affected by this operation: 1 5. Do you want to continue? [y/N] yslot_12 (config-interface-group-gr303)ig-1#


BLC 6000 System Configuration and Installation Guide- Release 6.0Appendix F: Shelf Hardware Upgrade Instructions

Upgrade Procedure

12 Remove the existing blade from Slot 1.

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.

18 The upgrade procedure is now complete.


BLC 6000 System Configuration and Installation Guide- Release 6.0 Appendix F: Shelf Hardware Upgrade InstructionsUpgrade Procedure


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix G: Software License Information

Open SSL Code

Appendix GSoftware License Information

In this Appendix:Open SSL Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871SSLEAY Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872Open SSH Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873Carnegie Mellon License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873GNU 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:

Open SSL CodeCopyright (c) 1998-2000 The Open SSL Project. 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.

3 All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software devel-oped by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).”

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 [email protected].

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.

6 Redistributions in any form whatsoever must retain the following acknowledg-ment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://wwww.opensssl.org/).”

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix G: Software License InformationSSLEAY Code

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS 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.

SSLEAY CodeCopyright (C) 1995-1998 Eric Young ([email protected]) All rights reserved.



3 All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes cryptographic software written by Eric Young ([email protected])." The word 'cryptographic' can be left out if the routines from the library being used are not cryptograph-ically related.

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 ([email protected])."

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).



Open SSH Code

Open SSH Code Copyright © 1995 Tatu Ylonen ([email protected]) Espoo, Finland. All rights reserved.

As to crc32.c only, Copyright © 1986 Gary S. Brown. You may use this program or code or tables extracted from it as desired without restriction.

As to deattack.c only, Copyright © 1998 CORE SDI, S.A. Buenos Aires, Argentina. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that this copyright notice is retained. THIS SOFTWARE IS PROVIDED 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES ARE DISCLAIMED. IN NO EVENT SHALL CORE SDI S.A. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES RRESULTING FROM THE USE OR MISUSE OF THIS SOFTWARE.

Copyright (c) 1988, 1993 Markus Friedl, Theo de Raadt, Niels Provos, Dug Song,Aaron Campbell.



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.

Carnegie Mellon License Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative work

Copyright 1996, 1998, 1999, 2000 The Regents of the University of California.

All rights reserved.

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both copyright notice and this permission notice appear in the supporting documetation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix G: Software License InformationCarnegie 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.



GNU General Public License


GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

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.

PreambleThe 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.


BLC 6000 System Configuration and Installation Guide- Release 5.5Appendix G: Software License InformationGNU General Public License

GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

1 This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or trans-lated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

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




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.



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.

7 If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any partic-ular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.This section is intended to make thoroughly clear what is believed to be a conse-quence of the rest of this License.




8 If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this 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

11 BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTIC-ULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.



END OF TERMS AND CONDITIONS

Copyright (C) 2001-2002 Occam Networks, Inc. All Rights Reserved.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You have received a copy of the GNU General Public License (in Appendix F) along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

You can contact Occam Networks at:

[email protected] +1-805-692-29116868 Cortona DriveSanta Barbara, CA 93117785553 Rev. 2.0BLC 6000 System Configuration and Installation Guide- Release 5.588010/09/08


Occam_OS 5_5_Install_and_Config_guide[1]

Documents

blades6 blc

system overview1overview1

occam networks product

harmless occam networks

occam representative

system installation

installation guide release

system configuration