Paradyne BitStorm 2400 User manual

BitStorm

™

2400

User’s Guide

Document No. 2400-A2-GB20-10

December 2002

A

December 2002 2400-A2-GB20-10

Printed in U.S.A.

Notice

This publication is protected by federal copyright law. No part of this publication may be copied or distributed,

transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or

by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express

written permission of Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773.

Paradyne Corporation makes no representation or warranties with respect to the contents hereof and specifically

disclaims any implied warranties of merchantability or fitness for a particular purpose. Further, Paradyne Corporation

reserves the right to revise this publication and to make changes from time to time in the contents hereof without

obligation of Paradyne Corporation to notify any person of such revision or changes.

Changes and enhancements to the product and to the information herein will be documented and issued as a new

release to this manual.

Warranty, Sales, Service, and Training Information

Contact your local sales representative, service representative, or distributor directly for any help needed. For additional

information concerning warranty, sales, service, repair, installation, documentation, training, distributor locations, or

Paradyne worldwide office locations, use one of the following methods:

!

Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty at

www.paradyne.com/warranty.)

!

Telephone: Call our automated system to receive current information by fax or to speak with a company

representative.

— Within the U.S.A., call 1-800-870-2221

— Outside the U.S.A., call 1-727-530-2340

Document Feedback

We welcome your comments and suggestions about this document. Please mail them to Technical Publications,

Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773, or send e-mail to userdoc@paradyne.com. Include the

number and title of this document in your correspondence. Please include your name and phone number if you are

willing to provide additional clarification.

Trademarks

ACCULINK, COMSPHERE, FrameSaver, Hotwire, MVL, NextEDGE, OpenLane, and Performance Wizard are

registered trademarks of Paradyne Corporation. BitStorm, EtherLoop, GrandVIEW, ReachDSL, StormTracker,

Spectrum Manager, StormPort, and TruePut are trademarks of Paradyne Corporation. All other products and services

mentioned herein are the trademarks, service marks, registered trademarks, or registered service marks of their

respective owners.

2400-A2-GB20-10 December 2002

i

Contents

About This Guide

!

Document Purpose and Intended Audience . . . . . . . . . . . . . . . . . . . . v

!

Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

!

Product-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

!

Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

1 BitStorm 2400 Overview

!

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

!

Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

!

EtherLoop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

!

Data Rate Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Token Bucket. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

!

Spectrum Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

!

Traffic Aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

!

Layer 2 CoS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

!

Priority Queuing Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Switching Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Downstream Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Upstream Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

!

VLAN Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Secure VLAN Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

!

Multicast Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

!

Multicast Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Multicast Group Membership Management. . . . . . . . . . . . . . . . . . 1-10

Multicast Traffic Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

!

Multicast IP Address and MAC Address Mapping . . . . . . . . . . . . . . . . 1-10

!

IGMP Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Join Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Membership Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Membership Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Leave Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Contents

ii

December 2002 2400-A2-GB20-10

!

IGMP Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

IGMP V1 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

IGMP V2 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

IGMP V1 and V2 Co-existence . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Summary of IGMP V2 Message Formats . . . . . . . . . . . . . . . . . . . 1-13

!

Multicast Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

IGMP Report Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

IGMP Leave Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Group-to-Interface Table Processing. . . . . . . . . . . . . . . . . . . . . . . 1-15

!

MAC Layer Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

2 Terminology and Conventions

!

System Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3 Using the Asynchronous Terminal Interface

!

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

!

Navigating Menu Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

!

Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

!

Main Menu Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

!

Switch Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

!

Port Statistics Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

!

Configuration File Upload/Download Screen . . . . . . . . . . . . . . . . . . . . 3-7

!

Image File Download Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

!

Serial Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

!

Change Password Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

!

Configure EtherLoop Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

4 Using the Web Interface

!

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

!

Web Interface Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

!

Configuring the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Contents

2400-A2-GB20-10 December 2002

iii

!

Management Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Switch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Port Configuration/Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Serial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Password Modification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

!

Notification (Traps). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

SNMP Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

SNMP Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

!

Spanning Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

Spanning Tree Bridge Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-18

Spanning Tree Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

!

VLANs/Multicast Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Current VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Static VLAN Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

VLAN/GVRP (GARP VLAN Registration Protocol) Port

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

Current Multicast Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Static Multicast Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

GARP/GMRP Port Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

A Monitoring and Troubleshooting

!

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

BSNMP Traps

!

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

C MIB Support

!

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

!

SNMP Addressing Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

!

MIB-II (RFC 1213) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

!

SNMPv2-MIB (RFC 1907) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

sysDescr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

sysObjectID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

SNMP Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4

Contents

iv

December 2002 2400-A2-GB20-10

!

Bridge-MIB (RFC 1483) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5

dot1dBase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5

dot1dBaseNumPorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5

dot1dTp Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6

!

RMON-MIB (RFC 1757). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6

!

P-Bridge-MIB (RFC 2674) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7

!

Q-Bridge-MIB (RFC 2674) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7

!

EtherLike-MIB (RFC 2665). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8

dot3StatsTable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8

!

TMS-Common-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9

!

OEM-BCM-5600-MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9

!

IF-MIB (RFC 2233). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

!

SNMP-Framework-MIB (RFC 2571) . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

!

SNMP-MPD-MIB (RFC 2572) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

!

SNMP-Target-MIB (RFC 2573) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11

!

SNMP-Notification-MIB (RFC 2573) . . . . . . . . . . . . . . . . . . . . . . . . . . C-11

!

SNMP-User-Based-SM-MIB (RFC 2574). . . . . . . . . . . . . . . . . . . . . . . C-11

!

SNMP-View-Based-ACM-MIB (RFC 2575) . . . . . . . . . . . . . . . . . . . . . C-11

Index

2400-A2-GB20-10 December 2002

v

About This Guide

Document Purpose and Intended Audience

This guide contains information necessary for the use of the asynchronous

terminal interface and web interface, in addition to SNMP and MIB information, for

the BitStorm 2400 IP DSLAM, Model 2461.

This release of the User’s Guide adds clarifications to certain procedures.

The successful user of this manual has experience with the installation and

configuration of EtherLoop and DSL network devices, especially those used in

Multi-Tenant Unit (MTU)/Multi-Dwelling (MDU) applications.

Document Summary

Section Description

Chapter 1, BitStorm 2400

Overview

Provides an introduction to the capabilities and

features of the BitStorm 2400.

Chapter 2, Terminology and

Conventions

Defines terms used in this manual and in the product’s

user interfaces.

Chapter 3, Using the

Asynchronous Terminal

Interface

Explains how to use the asynchronous terminal

interface.

Chapter 4, Using the Web

Interface

Explains how to use the web interface.

Appendix A,

Monitoring and

Troubleshooting

Describes how to monitor the system and diagnose

problems.

Appendix B,

SNMP Traps

Describes the SNMP Traps supported.

Appendix C,

MIB Support

Describes the MIBs and objects supported.

Index

Lists key terms, concepts, and sections in alphabetical

order.

About This Guide

vi

December 2002 2400-A2-GB20-10

A master glossary of terms and acronyms used in Paradyne documents is

available online at www.paradyne.com. Select

Support

→

Technical Manuals

→

Technical Glossary

.

Product-Related Documents

Complete documentation for this product is available online at

www.paradyne.com. Select

Support

→

Technical Manuals

.

To order a paper copy of a Paradyne document:

!

Within the U.S.A., call 1-800-PARADYNE (1-800-727-2396)

!

Outside the U.S.A., call 1-727-530-8623

Reference Documents

Document Number Document Title

2400-A2-GN20

BitStorm 2400 Installation Guide

Describes how to install and configure the BitStorm 2400.

This guide is shipped with the unit.

1020-A2-GN70

StormPort DSL Modem Installation Sheet

Describes how to install the StormPort DSL Modem,

Models 620 and 1020. These instructions are included

with the modem.

EMS-A2-GB20

StormTracker EMS 2.3 User’s Guide

Explains how to use the StormTracker EMS and describes

the options available. This guide is available online.

Document Number Document Title

IEEE 802.3z 1000BaseX

RFC 2571 Arch SNMP

RFC 826 ARP

RFC 2597 Assured Forwarding PHB

RFC 1493 Bridge MIB

RFC 2475 DiffServ

RFC 2474 DiffServ Field

– EtherLoop MIB

IEEE 802.3 Ethernet

RFC 1643 Ethernet MIB

About This Guide

2400-A2-GB20-10 December 2002 vii

RFC 2068 HTTP

RFC 2236 IGMP v2

RFC 1122 Internet Hosts

RFC 791 IP

IEEE 802.3ad Link Aggregation

RFC 2668 MAUs

RFC 2572 Messages SNMP

RFC 1212 MIB

RFC 1213 MIB II

RFC 2233 MIB SMI v2

RFC 2674 MO for Bridges 802.1D/q

RFC 2665 MOs Ethernet-like

IEEE 802/1D/p Priority Queuing

RFC 1757 RMON (groups 1,2,3,9)

RFC 1889 RTP

– Small Form-factor Pluggable (SFP) Transceiver MultiSource

Agreement (MSA)

RFC 2573 SNMP Apps

RFC 1157 SNMP v1

RFC 1907 SNMP v2

RFC 2574 SNMP v3

RFC 1902 SNMPv2 structure

RFC 1906 SNMPv2 transport mappings

RFC 793 TCP

RFC 1155 TCP/IP

RFC 854 Telnet

RFC 783 TFTP

RFC 768 UDP

RFC 2575 VACM SNMP

IEEE 802.1Q VLAN Tagging

Document Number Document Title

About This Guide

viii

December 2002 2400-A2-GB20-10

2400-A2-GB20-10 December 2002

1-1

1

BitStorm 2400 Overview

Overview

The BitStorm™ 2400 is an IP DSLAM contained in a 1RU rack-mountable

enclosure. It provides 24 channels of dedicated EtherLoop™ transport. Each

channel provides up to 10 Mbps of dedicated bandwidth depending on loop length.

The BitStorm 2400 IP DSLAM interfaces with a router or switch on the WAN side,

and StormPort™ CPE modems on the LAN side. Features available within the

BitStorm 2400 are accessible via SNMP software, such as StormTracker™ EMS.

The BitStorm 2400 IP DSLAM combines the following in one device:

!

Layer 2+ switching

!

Element management

!

Provisioning

!

Integrated Gigabit Ethernet switch links

!

EtherLoop DSL

Figure 1-1. BitStorm 2400 IP DSLAM

02-17144

1. BitStorm 2400 Overview

1-2

December 2002 2400-A2-GB20-10

Features

Based on EtherLoop technology, the BitStorm 2400 IP DSLAM has the following

features:

!

Compact size (height = 1RU)

!

Shelf-mountable (up to eight units high) and rack-mountable

!

Low price per port

!

Up to 24 ports 10 Mbps EtherLoop

— Data Rate Limiting (downstream 64 kbps increments provided by CPE)

— Standby mode (CPE initiates training to prevent line noise)

!

Spectrum Management

!

Traffic Aggregation

!

Traffic Management

!

QoS Support

!

Dual Gigabit Ethernet fiber and copper ports for WAN uplinks or stacking

!

Robust Layer 2+ Ethernet switching capability

!

Line speed switching

!

Multicast controls and IGMP snooping

!

CoS and QoS

— 802.1D/p Priority Queuing

— 802.1D Transparent Bridging/Spanning Tree

— 802.1Q VLAN Tagging (256 VLANs)

— Secure VLAN mode

!

Full integrated management

— MIB-II, Ether-Like, RMON (4 Groups), BRIDGE, P-BRIDGE, Q-BRIDGE,

and Enterprise MIBs (SNMP v1/v2/v3)

— Fully supported by StormTracker EMS 2.3/2.4

— Web browser interface

— Terminal interface via the CRAFT port or Telnet

1. BitStorm 2400 Overview

2400-A2-GB20-10 December 2002 1-3

EtherLoop

EtherLoop, like Ethernet, is a “burst-mode” technology – it transmits only when

there is information to send. In contrast, conventional copper access technologies

maintain constant signal, regardless of whether or not there is information to send.

Because EtherLoop is not always transmitting, it has the opportunity to “listen” to

the loop. Each EtherLoop-based modem has built-in Spectrum Manager™. This

innovative feature measures the spectral environment of the loop, analyzes the

results, and identifies potential interference. Because EtherLoop is agile in

frequency, the modem can adjust its frequency away from the interference source.

Based on this unique patented capability, EtherLoop can be deployed without

restriction in accordance with ANSI T1.417 Spectrum Management standard.

Data Rate Limiting

Data Rate Limiting allows service providers to offer various levels of service to

subscribers. Each discreet level of service translates into an

upstream/downstream maximum data rate (MDR) and maximum burst (MB)

values. Service levels can be offered in units of 64 kbps steps of upstream or

downstream bandwidth.

Maximum upstream/downstream burst limits shall be provisioned as the maximum

number of bytes that may be transmitted in a burst of traffic before the rate limiting

will take effect. Maximum burst size should typically be some multiple of the

respective MDR value. Example: A user who has a downstream MDR of 512 kbps

could be allowed a maximum burst size of 192 kbps (MB = 3 * MDR/second). The

aggregate upstream and downstream MDRs should not exceed the actual

bandwidth available on the EtherLoop circuit. SNMP traps may be set to monitor

EtherLoop line rates that fall below specified rate limit.

Token Bucket

Data Rate Limiting is set up using SNMP software, such as StormTracker EMS. It

is implemented by a Token Bucket mechanism on the transmit scheduler. The

Token Bucket will be a counter representing the number of “in policy” bytes of data

that may be transmitted. Tokens will be added to the bucket at the rate of MDR/8

per second.

The Token Bucket will have a maximum value (size) equal to the MB parameter.

Tokens will be added to the bucket until the point that the MB value has been

reached. Once the bucket is “full” the refresh tokens will overflow and not

accumulate in the bucket.

Frames will be admitted to the transmit queue only if there are enough tokens

available in the bucket based on the byte length of the frame to be transmitted.

Tokens will be removed from the bucket as frames are passed to the output queue.

“Out of Policy” frames (frames for which there are insufficient tokens available)

arriving at the transmit process will be dropped.

1. BitStorm 2400 Overview

1-4

December 2002 2400-A2-GB20-10

Spectrum Manager

Spectrum Manager operates within the StormTracker EMS software and makes

EtherLoop spectrally compatible with asymmetrical services such as ADSL and

G.Lite, detecting and protecting against interference within the same binder. In

addition, EtherLoop in its native state is spectrally compatible with symmetrical

digital services such as T1, HDSL, HDSL2, or SDSL.

Although Spectrum Manager capabilities may seem like rate-limiting features, they

are simply spectral management functions. The primary benefit of spectral

management is that the lower upstream frequency (imposed by protect modes)

causes little or no interference with downstream frequency or other services in a

binder, thus reducing crosstalk.

Table 1-1, Spectrum Manager Modes, shows the various modes in which

Spectrum Manager operates.

Traffic Aggregation

The integrated Layer 2+ BitStorm 2400 IP DSLAM aggregates the traffic to and

from the gigabit Ethernet interfaces. It operates as a multi-port Layer 2+ Ethernet

bridge per the IEEE 802.1D/802.1Q specifications. The BitStorm 2400 IP DSLAM

and EtherLoop lines support the forwarding of IEEE 802.1Q tagged VLANs and

selective IP multicast forwarding (via IGMP Snooping).

Table 1-1. Spectrum Manager Modes

Mode Description

Native EtherLoop operates without the analysis of other service activity in the

individual loops.

Monitor Spectrum Manager analyzes other services in the loop that may limit

EtherLoop performance.

Forced EtherLoop provides optimum spectrally compatible performance with

asymmetric services in the individual loop that may temporarily affect

EtherLoop’s upstream capability. In this mode, EtherLoop is forced to

“mimic” asymmetric DSL.

Auto-Protect EtherLoop operates in an Asymmetric Mode if asymmetric interferers

are present. EtherLoop returns to normal upstream operations once

the interference is gone.

Video-Protect EtherLoop operates in a forced Asymmetric Mode with guaranteed

high downstream bandwidth for the delivery of streaming video

applications.

1. BitStorm 2400 Overview

2400-A2-GB20-10 December 2002 1-5

Layer 2 CoS Support

Traffic management allows for the proactive management of bandwidth allocation.

By provisioning bandwidth management policies, classifying traffic, and applying

traffic shaping, users receive smooth and predictable service.

The integrated Layer 2+ has the ability to recognize flows based on Layer 2 packet

information including:

!

IEEE 802.1p priority information in tagged frames

!

Source MAC Address

!

Destination MAC Address

!

IEEE 802.1Q VLAN identifiers

Additional traffic management features and IP QoS functions will be added in

future releases.

Priority Queuing Support

The BitStorm 2400 and StormPort CPE modems are enabled to recognize and

respond to IEEE 802.1D priority classifications. This standard is also known as the

IEEE 802.1p, which is a subsection of the IEEE 802.1D standard. The 802.1p

priority bits information is carried in a 3-bit field in the IEEE 802.1Q tag.

The CO and CPE modems inspect and classify packets based on the IEEE 802.1p

priority field value. IEEE 802.1p defines 8 levels of priority (0-lowest to 7-highest).

The CO and CPE modems map these priority levels to one of two output queues

(high and low). The Ethernet Ports map these priorities to one of four output

queues (lowest, low, high, highest). This mapping complies with the recommended

mapping in the IEEE 802.1D-1998 standard. The mapping is configurable and may

be set to meet specific implementation standards.

Once traffic has been allocated to the output queues of the CO and CPE modems,

they will be serviced according to strict priority (picked from high until empty). Note

that this process is observed for packets in the downstream direction from the CO

and the upstream direction for the CPE (EtherLoop is a point-to-point connection

that preserves packet order so priority output queuing processes do not have to be

re-run on the receiving device).

Switching Fabric

The Ethernet Switching fabric in the BitStorm 2400 recognizes and responds to

IEEE 802.1D priority classifications. This standard is also known as the IEEE

802.1p which is a subsection of the 802.1D standard. The 802.1p is carried in a

3-bit field in the IEEE 802.1Q tag. The BitStorm 2400 classifies frames based on

the presence and code points (values) of priority information in the IEEE 802.1Q

tag.

1. BitStorm 2400 Overview

1-6

December 2002 2400-A2-GB20-10

Downstream Traffic

In downstream traffic, frames with IEEE 802.1D priority code points of 4 to 7 are

directed to the high priority queue. Frames without IEEE 802.1Q tags and tagged

frames with priority codepoints of 0 to 3 are directed to the low priority queue.

The output frame schedulers on the BitStorm 2400 picks frames from the high

priority queue ahead of any frames on the low priority queue. The low priority

queue may overflow due to lack of servicing by giving preference to the high

priority queue. This may result in frame loss in the event of a high volume of high

priority frames. The loss of frames will be reported to the management platform.

Upstream Traffic

In upstream traffic, the EtherLoop StormPort CPE modems define high and low

priority output queues. Frames with IEEE 802.1D priority codepoints of 4 to 7

should be directed to the high priority queue. Frames without IEEE 802.1Q tags

and tagged frames with priority codepoints of 0 to 3 should be directed to the low

priority queue.

The output frame scheduler on the StormPort CPE picks frames from the high

priority queue ahead of any frames on the low priority queue. The low priority

queue may overflow due to lack of servicing by giving preference to the high

priority queue. This may result in frame loss in the event of a high volume of high

priority frames. The loss of frames is reported to the management platform.

Additionally, there is a setting in the VLAN/GVRP Port Configuration screen of the

web interface that allows you to set priority for untagged frames. The default is 0,

but can be changed if necessary.

VLAN Support

VLAN was introduced to control traffic flows on a physical network. A VLAN

defines a group of systems connected into a logical broadcast domain. This

reduces overall LAN traffic and improves security. A VLAN can be created to serve

any purpose. The BitStorm 2400 system will implement VLAN mechanisms that

support the IEEE 802.1Q specification.

Virtual LANs (VLANs) have been widely accepted and implemented in Ethernet

networks as a means to control everything from broadcast storms to security

issues to quality of service parameters and many other creative uses.

In its simplest form, VLAN support is a way to partition a switch or multiport router

such that it creates two or more broadcast domains. Generally users and devices

within a broadcast domain or VLAN may communicate freely with each other.

Communication across VLANs is enabled and controlled via a router or layer 3

switch.

Historically, VLAN capabilities were developed by individual switch and router

manufacturers and served the needs of only a specific class of devices from that

manufacturer. In recent years, the IEEE has standardized VLAN implementations

to enable a more consistent approach to VLAN mechanisms and to enable

interoperability among various components and equipment from different

manufacturers.

1. BitStorm 2400 Overview

2400-A2-GB20-10 December 2002 1-7

The VLAN standard IEEE 802.1Q deals with the creation and management of

VLANs on many types of devices. One of the main features of this standard is the

adoption of a new Ethernet frame format that includes a ‘tag’ to carry VLAN and

packet prioritization information. This tag adds 4 bytes to the standard Ethernet

frame. The tag itself is optional, i.e., it may or may not be present on any given

frame. A major implication of the new frame format is that the maximum valid

Ethernet frame size has been increased from 1518 bytes to 1522 bytes. The

increase in the maximum valid frame size is an issue of possible concern for older

(non-VLAN-aware) devices which may have had limits on the acceptable frame

sizes.

Figure 1-2. Standard Ethernet Frame Format and Extended Format with IEEE

802.1Q Tagging

VLAN support involves:

!

VLAN Membership Management

!

Forwarding

VLAN membership can be based on the following:

!

EtherLoop Subscriber Interfaces

!

Ethernet or GigE Ports on the BitStorm 2400

!

Explicit tagging of traffic by end devices

VLAN support requires the implementation of the following operations:

!

VLAN Creation

!

VLAN Frame Forwarding

!

Ingress and Egress filtering & forwarding rules

!

Tagging and un-tagging frames as required

VLAN support is explicitly implemented at both the BitStorm 2400 and the

EtherLoop StormPort modems. Each component operates as a VLAN enabled

multiport bridge.

Dest MAC@ Source MAC@ L/Type Data FCS

Dest MAC@ Source MAC@ L/Type Data FCSVLAN Tag

TPID 0x'8100' TCI

Priority VIDC

02-17292

1. BitStorm 2400 Overview

1-8

December 2002 2400-A2-GB20-10

Secure VLAN Mode

The BitStorm 2400 also extends a secure VLAN mode in the web interface for

port-to-port security. In this mode, Etherloop ports can only communicate talk with

the WAN side of the network.

When a VLAN is in secure mode, packets received on member ports are

redirected to the uplink port (25) and not switched to other members. Conversely,

when a VLAN is not in secure mode, the member ports share packets as in a

normal VLAN.

VLAN secure status can be toggled with an SNMP browser (or the web interface)

by setting the private->enterprises->wrs->tms->idb->garpMib->garpMIBObjects->

gDot1qVlanStaticSecureTable->gDot1qVlanStaticSecureEntry->gDot1qVlanStatic

SecureRowStatus object to active(1) (or the integer 1) or notInService(2) (or the

integer 2). However, you must create and delete static VLANs through the

standard VLAN mibs. This can be set up through the VLAN setting instructions

documented in the

StormTracker EMS 2.3 User’s Guide

.

Multicast Overview

Multicast support is provided by the BitStorm 2400 to deal efficiently with IP

multicast packets received from sources from the GigE link or from a locally

connected source. The primary application of IP multicast traffic is to deliver

content to one or more users with a single IP stream.

IP multicasts are used for many popular applications including:

!

Stock Ticker and news feeds (Pointcast)

!

Video and Audio streaming (broadcast like services over the IP network – Real

Media)

!

Some ‘Near’ Video on Demand servers (e.g., movies that start every

15 minutes)

!

Voice over IP (VoIP) conference calling features

!

Multipoint conference applications (Net Meeting, PictureTel)

True video on demand and point-to-point VoIP applications will typically use

unicast mechanisms (not multicast) for traffic delivery. These applications require a

server to communicate directly with a unique subscriber and send packets as

needed to each subscriber. Hybrid systems also exist where content is distributed

on a schedule via IP multicast and then play out on demand under local control.

As with any class of applications, there are many ways in which the services may

be provided. The features as described in this document for implementation in the

BitStorm 2400 will provide support for IP multicast application using IGMP V1

and/or IGMP V2 protocols. Some applications will combine IP streaming with

VLAN and CoS/QoS techniques to deliver unique services.

Care must be taken in designing large-scale implementations to properly

characterize the nature and behavior of the application, network and end stations.

1. BitStorm 2400 Overview

2400-A2-GB20-10 December 2002 1-9

Protocols

Extensive protocols and support exist for the distribution of multicast traffic across

the Internet and private GigE links. These protocols include Multicast Open

Shortest Path First (MOSPF), Distance Vector Multicast Routing Protocol

(DVMRP), and Protocol Independent Multicast (PIM, PIM SM, PIM DM).

It is assumed that one these routing protocols will be used to deliver the IP

multicast streams to the BitStorm 2400 IP DSLAM for delivery to subscribers. The

BitStorm 2400 will not directly participate in the routing protocols. In most

circumstances, the BitStorm 2400 will communicate with a router or Layer 3 switch

that performs these routing functions.

IP multicast packets are forwarded to the last router hop and are then delivered on

the router interface as specially formatted layer two broadcasts. Multicast support

is required in the BitStorm 2400 system to efficiently handle the forwarding of

multicast packets at Layer 2.

In the absence of multicast support, all multicast packets delivered to the

BitStorm 2400 IP DSLAM would be flooded to all ports (EtherLoop and Ethernet)

on the system. The result of this flooding is that all users would receive the traffic

for all of the multicasts that any user of the BitStorm 2400 had requested. This

would quickly overwhelm the bandwidth and resources of the system and end

stations.

Multicast support in the BitStorm 2400 system is based on the IETF Internet

Group Management Protocol (IGMP) standards Version 1 and Version 2.

Multiple versions of IGMP exist:

!

IGMP v1 – RFC 1112

!

IGMP v2 – RFC 2236

!

IGMP v3 – Draft

See

IGMP Protocols

on page 1-11 for more information on IGMP operations.

Multicast Support

Support for efficient IP multicasting is critical for streaming applications such as

digital video delivery. Simply replicating packets and sending them serially to users

will not scale. Multicast routing capability is currently available in most routers.

Multicast support for the BitStorm 2400 system will ensure that IP multicasts are

efficiently forwarded at Layer 2 to subscribers and blocked from non-subscribers.

The BitStorm 2400 system operates as an IP Multicast-aware Layer 2 Switch

(Layer 2+).

IP Multicast support involves:

!

Multicast Group Membership Management

!

Multicast Traffic Forwarding (Layer 2)

1. BitStorm 2400 Overview

1-10

December 2002 2400-A2-GB20-10

Multicast Group Membership Management

Multicast group membership management operations include:

!

Joining a Multicast Group

!

Multicast Group Membership Query

!

Multicast Group Membership Report

!

Leaving a Multicast Group

!

Summarizing IGMP reports to minimize duplicate information being forwarded

to the router interface

!

Generating proxy Queries Messages in the event there is no local multicast

enabled router

Multicast Traffic Routing

To properly and efficiently implement multicast traffic routing in the access

network, the following situations are handled:

!

First Member Joining the Multicast Group

!

Multicast packet forwarding and replication at Layer 2 elements

!

Detecting the presence of IGMP Version 1 or IGMP Version 2 hosts on

subscriber segments.

!

Determining when the last active member leaves a multicast group

Multicast IP Address and MAC Address Mapping

IP Multicast addresses are 32-bits long with the four high order bits set to “1110,”

which leaves 28 bits for multicast groups. When IP Multicast traffic is routed across

a Layer 2 network, the lower 23 bits of the 28-bit Multicast Group Address are

mapped into the lower 24 bits of the corresponding MAC multicast address and the

most significant bit is set to 0. The higher 24 bits of the MAC multicast address are

fixed to 01.00.5E.

Because only 23 bits of the 28 bits of the IP multicast address are mapped into the

MAC multicast address, this leaves 32 IP multicast addresses mapped into a

single MAC multicast address. The CO and the BitStorm 2400 both need to

inspect the IP header in the multicast frame to determine the actual IP multicast

group for forwarding traffic on the right port.

Page is loading ...

Paradyne BitStorm 2400 User manual

Paradyne BitStorm 2400 User manual

Related papers

Other documents