Utstarcom en GEPON BBS1000plus CLI Operation R2.32.1.28
Utstarcom en GEPON BBS1000plus CLI Operation R2.32.1.28
Utstarcom en GEPON BBS1000plus CLI Operation R2.32.1.28
BBS 1000+
Release 2.32.1.28
CLI Operation Guide
5 BASIC CONFIGURATION
Configuring Basic System Information ..................................................................................... 93
Configuring Layer 2 Ports ........................................................................................................ 95
Introduction to BBS 1000+ GE ports........................................................................................ 95
GE Port Features................................................................................................................ 95
Administrative Status .................................................................................................... 95
Link Status of GE Port................................................................................................... 96
PVID.............................................................................................................................. 96
Traffic Storm Control ..................................................................................................... 96
Auto Negotiation............................................................................................................ 97
Flow Control .................................................................................................................. 97
Ingress filter................................................................................................................... 98
Rate Limit ...................................................................................................................... 98
User-isolation ................................................................................................................ 98
GE ports Configuration Tasks............................................................................................. 99
Configuring Layer 2 Link Aggregation ................................................................................... 100
Link Aggregation Interface Restrictions............................................................................ 100
Link Aggregation Layer 2 Configuration Tasks ................................................................. 101
Link Aggregation Group Management Procedure ............................................................ 101
Example of Creating an L2 Link Aggregation Group ........................................................ 102
Application Description................................................................................................ 102
Example Topology....................................................................................................... 103
6 VLAN MANAGEMENT
VLAN Introduction.................................................................................................................. 169
Layer 2 Port-Based VLANs .............................................................................................. 169
GE port VLAN ............................................................................................................. 169
Restrictions for Layer 2 VLAN Management............................................................... 169
VLAN ID Processing in Unique-tag/Stack-tag Mode......................................................... 170
ONU Forwarding Rules For L2 Data Packets in Unique-tag Mode ............................. 170
ONU Forwarding Rules For L2 Data Packets in Stack-tag Mode................................ 171
BBS 1000+ Ingress Port Forwarding Rules for L2 Data Packets................................ 171
ONU VLAN Management ................................................................................................. 172
ONU Default VLAN ..................................................................................................... 172
Especially VLAN ID Assignment in Unique-tag Running Mode .................................. 172
Especially ONU VLAN ID Reconfiguring in Stack-tag Mode and QinQ Running Mode173
VLAN Layer 2 Configuration Tasks ........................................................................................ 174
VLAN Layer 2 Management Procedure ................................................................................. 174
VLAN Creation Example ........................................................................................................ 175
Application Description ..................................................................................................... 175
Example Topology ............................................................................................................ 175
Configuration Requirements ....................................................................................... 175
Configuration Tasks .......................................................................................................... 175
Create a VLAN. ........................................................................................................... 175
Add Members to the VLAN ......................................................................................... 176
Configure the Interface PVID ...................................................................................... 176
Deleting the Example Configuration on BBS 1000+......................................................... 176
Reconfigure the port's PVID ....................................................................................... 176
Delete Members from the VLAN ................................................................................. 177
Delete a VLAN ............................................................................................................ 178
9 CONFIGURING SYSLOG
Understanding the Concepts.................................................................................................. 275
System Log Message Format........................................................................................... 275
Sending Syslog Messages to the Console or Flash Memory ........................................... 276
Logging Host Server and Facilities................................................................................... 277
System Log Configuration Commands............................................................................. 278
Syslog Configuration Procedure....................................................................................... 278
Syslog Configuration Example............................................................................................... 278
Application Description................................................................................................ 278
Example Topology....................................................................................................... 279
Configuration Tasks .......................................................................................................... 279
Configure an SVI on BBS 1000+ ................................................................................ 279
Verify the out-band gateway ....................................................................................... 280
Configure Syslog on BBS 1000+ ................................................................................ 280
Configure the Cisco switch ......................................................................................... 281
Configure the Syslog Server ...................................................................................... 281
Set the Syslog Server IP Address............................................................................... 283
Removing All Syslog Configurations on BBS 1000+ ........................................................ 285
Remove the syslog configuration ................................................................................ 285
Remove the SVI ......................................................................................................... 285
Removing VLAN 500................................................................................................... 286
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
16
10 CONFIGURING RSTP
Introduction RSTP ................................................................................................................. 287
RSTP Configuration Commands............................................................................................ 287
RSTP Configuration Procedure ............................................................................................. 288
RSTP Configuration Example ................................................................................................ 288
Application Description..................................................................................................... 288
Example Topology ............................................................................................................ 289
Configuration Requirement ......................................................................................... 289
Configuration Tasks.......................................................................................................... 289
Configure the ONU's MAC and PON's lport binding ................................................... 289
Configure VLAN 10 on BBS 1000+............................................................................. 290
Enable Spanning Tree on the VLAN 10 ...................................................................... 290
Show Spanning Tree Configuration ............................................................................ 290
Create VLAN 10 on Cisco 3750 ................................................................................. 291
Enable Spanning Tree on the VLAN 10 ...................................................................... 292
Verify the Spanning Tree ............................................................................................ 292
Two links Case ...................................................................................................... 293
One Link Case....................................................................................................... 293
Rescover to Two Links Case. ................................................................................ 294
13 CONFIGURING MULTICAST
Multicast Address................................................................................................................... 321
Configuring IGMP Snooping .................................................................................................. 321
IGMP Snooping Work Mode ............................................................................................. 321
IGMP Snooping Configuring Tasks................................................................................... 322
IGMP Snooping Configuration Example ................................................................................ 322
Application Description................................................................................................ 322
Example Topology....................................................................................................... 323
Configuration Requirements ....................................................................................... 323
Configuration Tasks .......................................................................................................... 324
Create Service VLAN 10 ............................................................................................. 324
Enable IGMP Snooping on VLAN .............................................................................. 325
Perform IGMP Snooping Service ................................................................................ 325
Check IGMP group information on BBS 1000+ .......................................................... 327
Configuring IGMP Proxy ........................................................................................................ 328
IGMP Proxy Configuring Tasks......................................................................................... 329
Configuring IGMP Proxy Procedure ................................................................................ 330
IGMP Proxy Configuring Example ......................................................................................... 330
Application Description................................................................................................ 330
Example Topology....................................................................................................... 330
Configuration Tasks .......................................................................................................... 331
Configure a Routed Interface ...................................................................................... 331
Configure ONUs' Lport Binding ................................................................................... 332
Start up PON Port OLT1/1........................................................................................... 332
Configure Super SVI ................................................................................................... 332
Configure IGMP Proxy ................................................................................................ 333
Perform IGMP Proxy Service ...................................................................................... 335
Check IGMP group information on BBS 1000+ .......................................................... 337
14 CONFIGURING ACL
ACL Work Mode..................................................................................................................... 339
ACL Configuration Tasks ....................................................................................................... 339
ACL Configuration Procedures ............................................................................................ 342
ACL Profile Configuration ...................................................................................................... 343
15 CONFIGURING QOS
BBS 1000+ QoS Overview..................................................................................................... 377
Classification ............................................................................................................... 379
Queuing and Scheduling............................................................................................. 379
QoS Configuring Commands............................................................................................ 381
QoS Configuring Procedure ............................................................................................. 381
ACL and QoS ................................................................................................................... 381
BBS 1000+ QoS Configuration Example ............................................................................... 382
Application Description ..................................................................................................... 382
Topology Example ............................................................................................................ 382
Configuration Tasks .......................................................................................................... 383
Configure QoS on GE3/2 ............................................................................................ 383
Configure QoS on GE1/1 ............................................................................................ 383
Configure ratelimit on GE1/1....................................................................................... 384
Result Analyze ............................................................................................................ 384
16 SYSTEM ADMINISTRATION
User Account Management ................................................................................................... 385
User Management Operations ......................................................................................... 386
Examples of User Management ....................................................................................... 386
Change password for Administrator............................................................................ 386
Add a Super user ........................................................................................................ 387
Delete a user............................................................................................................... 388
File Management ................................................................................................................... 388
System Start Up Method................................................................................................... 388
System File Introduction ................................................................................................... 389
File Configuration Tasks ................................................................................................... 390
Firmware Upgrade Procedure................................................................................................ 391
Firmware Upgrade Normally In-band Management ............................................................... 393
LIST OF TABLES
Table 1 Notice Icon Descriptions......................................................................................... 27
Table 2 Text Convention Descriptions................................................................................. 28
Table 3 CLI Command Modes............................................................................................. 38
Table 4 CLI Syntax Convention Description........................................................................ 40
Table 5 Shortcuts for obtaining help within CLI".................................................................. 40
Table 6 Hotkeys................................................................................................................... 42
Table 7 BBS 1000+ internal and external ports................................................................... 44
Table 8 VLAN ID Handling Mechanism for the four Running Modes .................................. 46
Table 9 Commands to configure running mode .................................................................. 49
Table 10 ASIC System Information Configuration Commands ............................................. 94
Table 11 Typical GE port configuration commands............................................................... 99
Table 12 Typical Layer 2 LAG configuration commands..................................................... 101
Table 13 Interface Range configuration commands ........................................................... 124
Table 14 Typical MAC Address Table configuration commands ......................................... 142
Table 15 Typical ARP configuration commands ................................................................ 149
Table 16 Typical IP Route configuration commands ......................................................... 156
Table 17 Typical port mirroring commands ....................................................................... 163
Table 18 VLAN Assignment in ONU Registration for the Four Running Modes.................. 172
Table 19 VLAN ID Assignment............................................................................................ 172
Table 20 Typical layer 2 VLANconfiguration commands..................................................... 174
Table 21 PON system parameters ..................................................................................... 179
Table 22 Authentication Configuring Commands ................................................................ 181
Table 23 VLAN ID Assignment (Based on a VLAN ID Base of 101) ................................... 182
Table 24 OLT Configuration Commands............................................................................. 191
Table 25 .............................................................................................................................. 197
Table 26 OLT DBA Configuration Parameters ................................................................... 198
Table 27 OLT DBA Configuration Commands .................................................................... 198
Table 28 ONU DBA_SLA Configuring Commangs.............................................................. 201
Table 29 DBA Parameters Configuration ............................................................................ 202
Table 30 ONU Policy Configuring Commands .................................................................... 210
Table 31 Downstream Bandwidth Paramenters ................................................................. 211
Table 32 ONU p2p stream Policy Parameters ................................................................... 214
Table 33 ONU1's DBA-SLA Parameters ............................................................................. 215
Table 34 Case1 of p2p Policy.............................................................................................. 218
Table 35 Case2 of p2p Policy.............................................................................................. 218
Table 36 Case3 of p2p Policy.............................................................................................. 219
Table 37 type and hw-rev value configuration .................................................................. 229
Table 38 ONU100's hardware type ..................................................................................... 231
Table 39 ONU Configuring Commands............................................................................... 234
Table 40 MAC Address Configuration Commands.............................................................. 237
Table 41 Re-authentication Parameter Configuring Commands ......................................... 246
Table 42 Remote Authentication Configuring Commands .................................................. 249
Table 43 Remote Accounting Configuring Commands ....................................................... 273
Table 44 Non-RFC 3164 Syslog Format Description ......................................................... 276
Table 45 Syslog Severity Level Description ........................................................................ 276
Table 46 Syslog Facility Codes ......................................................................................... 277
Table 47 Syslog Configuration Commands ......................................................................... 278
Table 48 RSTP Configuring Commands ............................................................................. 287
Table 49 DHCP Configuring Commands............................................................................. 297
Table 50 DHCP Relay Configuring Commands .................................................................. 311
Table 51 IGMP Snooping Configuring Commands ............................................................. 322
Table 52 IGMP Proxy Configuring Commands ................................................................... 329
LIST OF FIGURES
Figure 1 Serial RJ-45/DB9 RS-232 cable connection ......................................................... 31
Figure 2 HyperTerminal COM port selection ...................................................................... 32
Figure 3 DEBUG Port Communication Parameters ............................................................ 33
Figure 4 Ethernet cable Management port connection ....................................................... 34
Figure 5 BBS 1000+ system interface modules ................................................................. 43
Figure 6 BBS 1000+ back view(DC) .................................................................................. 44
Figure 7 BBS1000+ PON running mode ............................................................................. 44
Figure 8 BBS 1000+ PON Part .......................................................................................... 46
Figure 9 BBS 1000+ Start Up Procedures .......................................................................... 50
Figure 10 Out-Band Management Port ................................................................................. 52
Figure 11 BBS 1000+ L2 switch configuration topology example ........................................ 53
Figure 12 PC1 IP Address Configuration .............................................................................. 59
Figure 13 Configuring BBS 1000+ as a L3 switch ................................................................ 61
Figure 14 PC1 IP Address Configuration .............................................................................. 72
Figure 15 QinQ Application Example Topology .................................................................... 76
Figure 16 FE Port for Out Band Management(DC) .............................................................. 79
Figure 17 In-Band Configuration Topology ........................................................................... 81
Figure 18 PC Gateway Configuration ................................................................................... 86
Figure 19 SNMP Configuring Topology ................................................................................ 87
Figure 20 Netman 4000 OMC-D TopoUI Client window ....................................................... 90
Figure 21 Create NE window ................................................................................................ 91
Figure 22 Traffic Storm Control ........................................................................................... 96
Figure 23 User-isolation example ......................................................................................... 99
Figure 24 Link Aggregation Configuration Topology .......................................................... 103
Figure 25 Using DMAC as Loading-sharing Rule ............................................................... 114
Figure 26 One link case, Rtag is dmac ............................................................................... 117
Figure 27 Two links case , Rtag is dmac ............................................................................ 118
Figure 28 Three links case, Rtag is dmac .......................................................................... 118
Figure 29 Break L1, Two links case, Rtag is dmac ............................................................. 119
Figure 30 Using DIP XOR SIP as Loading-share Rule ....................................................... 120
Figure 31 One link case, Rtag is DIP XOR SIP .................................................................. 122
Figure 32 Two links case, Rtag is DIP XOR SIP ................................................................ 123
Figure 33 Three links case, Rtag is DIP XOR SIP .............................................................. 124
Figure 34 Secondary IP address Application on the Uplink Interface ................................. 127
Figure 35 Secondary IP address Application on a Super SVI ............................................ 127
Figure 36 SVI application uplink backup configuration .................................................... 130
Figure 37 Super SVI example ............................................................................................. 132
Figure 38 L3 Link Aggregation port based on an SVI port .................................................. 135
Figure 39 L3 LAG interface based on a Routed interface .................................................. 138
Figure 40 Static MAC Address Configuration Topology ..................................................... 143
Figure 41 ARP Configuration Topology .............................................................................. 150
Figure 42 Metric Example ................................................................................................... 155
Figure 43 IP Route Topology .............................................................................................. 157
Figure 44 Port Mirror Topology ........................................................................................... 164
Figure 45 VLAN Management ............................................................................................ 170
Figure 46 VLAN Creation Topology .................................................................................... 175
Figure 47 Local ONU Authentication .................................................................................. 183
Figure 48 Discovery Handshak Message Exchange .......................................................... 195
Figure 49 GATE/REPORT Process .................................................................................... 195
Figure 50 OLT&ONU DBA Configuration ........................................................................... 202
Figure 51 p2p Access Mode Topology Example ................................................................ 207
Figure 52 P2P-stream & Upstream Forwarding .................................................................. 209
This document describes how to operate the GEPON (Gigabit Ethernet Passive
Optical Network) BBS 1000+ system with a basic configuration and lists the CLI
(Command Line Interface) command set. For GEPON System Structure, refer to
GEPON System Overview manual.
The parameters used in the given example are particular to the equipment being
configured in the example. Users need supply the necessary respective value
when configuring their own system.
The software except the BBS 1000+ firmware used in the given example is
provided by the third party and used here for function configuration demo only.
This guide is intended for technical engineers and system administrators who
are responsible for operating and maintaining the GEPON BBS 1000+ system.
Release notes are issued with some products. Visit our websites at
http://support.utstar.com.cn (China Service Center) and
http://support.utstar.com. (other Service Centers) If the information in the
release notes differs from the information in this guide, follow the instructions in
the release notes.
Conventions This guide may contain notices, figures, screen captures, and certain text
conventions..
Figures and Screen This guide provides figures and screen captures as examples. These examples
Captures contain sample data. This data may vary from the actual data on an installed
system.
Convention Description
Text represented as a screen This typeface represents text that appears on a terminal
display screen, for example login:.
Text represented as user This typeface represents commands entered by the
entry. user, for example, cd
$HOME.
Text represented as menu, This typeface represents all menu, sub-menu, tab, and field
sub-menu, tab, and field names within procedures, for example:
names
On the File menu, click New.
Text represented by <variable> This typeface represents a required variable, for example:
<filename>
Related For more infornation on GEPON BBS 1000+ Release 2.32.01.028, refer to the
Documentation following documents.
GEPON BBS 1000+ Installation Guide
GEPON BBS 1000+ Release 2.32.01.028 CLI Reference Guide
GEPON BBS 1000+ Release 2.32.01.028 SNMP Reference Guide
GEPON BBS 1000+ Release 2.32.01.028 Alarm Message Guide
GEPON OLT BBS 1000+ Doc. Code L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
Contacting Customer Service 29
Contacting Customer For information about customer service, including support, training, code
Service releases and updates, contracts, and documentation, visit our websites at
http://support.utstar.com.cn (China Service Center) and
http://support.utstar.com (other Service Centers).
Obtaining Technical UTStarcom maintains a strong global presence, operating Technical Response
Assistance and Service Centers, in the US, Japan, India, China, Ireland, Mexico and Brazil.
These centers are available for technical telephone support to entitled
customers during normal business hours. After hours support is available to
customers who purchase a premium Service Agreement.
Support Website The UTStarcom Support website provides a variety of tools to assist customers
in resolving technical issues on UTStarcom products. The UTStarcom Support
website is available 24 hours per day. Customer registration is required. Certain
premium features require a valid Service Agreement.
Warranty Support UTStarcom provides its customers warranty support per the terms of the
UTStarcom Warranty Statement for their equipment. Customers who require
warranty support should contact the UTStarcom Service Center that serves their
territory.
This manual introduces the GEPON BBS 1000+ system's CLI network
management features.
In the initial BBS 1000+ setup stage, two methods are provided for logging in to
the system using CLI-based management:
Terminal Emulation using the DEBUG port (RJ-45 connector)
Telnet using the Management port (RJ-45 connector)
Using Terminal When using terminal emulation to access the BBS 1000+ system, the PC's
Emulation to login to serial RS-232 COM port is connected to the BBS 1000+'s DEBUG port. Follow
BBS 1000+ the steps below to connect a PC to the BBS 1000+ system:
1 Use a RJ-45/DB9 RS-232 serial cable. Connect the DB-9 connector to a vacant
serial RS-232 COM port on the PC, and the RJ-45 connector to the BBS
1000+'s DEBUG port, as shown in the figure below:
Figure 1 Serial RJ-45/DB9 RS-232 cable connection
4 From the Connect using drop-down list, select the COM port corresponding
with the cable connection made in Step 1.
5 Click <Configure> to display the COMx Properties dialog box.
Data Bits: 8
Parity: None
Stop Bits: 1
Username:
Password:
The default system administrator username and password are: admin and
admin.
8 Enter the username and password.
After logging onto the BBS 1000+ successfully, the following command prompt
is displayed.
BBS1000+>
Using telnet to login to When using Telnet to access the BBS 1000+ system, the PC network card's
BBS 1000+ (RJ-45) connector is connected to the BBS 1000+'s Management port (RJ-45).
Follow the steps below to connect a PC to the BBS 1000+ system:
1 Use an Ethernet cable with RJ-45 connectors on both ends to connect the BBS
1000+ Management port with the PC's network card.
Figure 4 Ethernet cable Management port connection
4 After establishing the connection with BBS1000+, the system will prompt you to
enter the username and password.
Username:
Password:
For BBS 1000+, the default administrator user name and password are both
"admin". The user name and password for guests (with read-only access) are
both "guest".
If the user enters an incorrect Username and Password six times in a row,
the telnet connection will be terminated.
5 Enter the username and password.
Upon successful login, the following system prompt is displayed.
telnet@BBS1000+>
This prompt indicates that the user is at the first command mode interface; the
EXEC level.
Depending on the particular user account privileges, different CLI command
mode can be accessed.
For more information on user account privilege, refer to section "CLI
Command Mode".
Login Session The BBS 1000+ system supports up to four concurrent Telnet sessions when a
console session is also active, or five when a console session is inactive.
The idle session timeout is set to 30 minutes by default. When a session has
been idle for 30 minutes, the user will automatically be logged out.
At the Privileged EXEC command mode the system prompt changes to the
following:
telnet@BBS1000+#
3 Type the following command to set the idle session timeout to one hour.
telnet@BBS1000+(config-mgmt)# system timeout 3600
After entering the save command, the configuration information is saved in the
BBS 1000+'s Flash memory. It normally takes several seconds before the
configuration is saved. On successful saving the telnet will display the following
message to indicate that the timeout configuration was successful.
telnet@BBS1000+(config-mgmt)#
Logout the BBS 1000+ There are two different CLI logouts types: Manual Logout and Timeout.
Manual Logout
At any command mode, type the logout command to terminate the current
CLI connection.
For example, if the current command mode is Configure Management, the
user enter the logout command to exit BBS 1000+ system.
Use the following command to logout of the system.
telnet@BBS1000+(config-mgmt)# logout
Time-out
A time-out occurs when the user account has been idle for the configured
Idle Timeout period.
For example, if the current command mode is Configure Management,
when the idle time reaches the configured timeout value, the session is
terminated by the system automatically. In this situation the following system
message is displayed:
telnet@BBS1000+(config-mgmt)# Log out by the system
CLI Command Mode The BBS 1000+ CLI utilizes a layered command architecture referred to as
command modes. Each of these command modes provide a subset of CLI
commands. The CLI commands available depends on which command mode is
currently activated.
When the users first logs in they are at the basic user mode, called the EXEC
command mode. In order to access higher level command modes, a password
must be entered. The command modes including their access methods and
related command privileges are described below.
EXEC This command mode allows users to view basic system information and verify
connectivity, but configuration changes are not allowed.
Access Method: At initial user login the user is at the EXEC command mode.
Privileged EXEC Besides allowing user access to all of the EXEC command mode commands,
configuration commands that do not require saving, are also permitted. At the
Privileged EXEC command mode, access to the system configuration file is
prohibited.
Access Method: From the EXEC prompt "BBS1000+>", enter the command
enable. If the configuration "enable password" is set, the user will be
prompted to enter the Privileged EXEC password.
Configure Management From this command mode general management functions can be performed,
such as creating user accounts, password modification, IP address
configuration, file system functions, updating the Boot ROM image, log
management configuration, system re-boot and Access Control List (ACL)
management.
Access Method: From the Privileged EXEC prompt "BBS1000+#", enter the
configure management command.
Configure Terminal This command mode allows users to make device configuration changes.
These changes can be saved to the BBS 1000+'s flash memory and will be
activated on the next system boot-up. The root level Configure Terminal
command mode, Global Configuration command mode, contains sub-levels
for individual ports, VLANs, and other configuration areas.
Global Configuration
Access Method: From the Privileged EXEC prompt "BBS1000+#", enter the
config terminal command.
In the system prompt shown above, "2/1" represents OLT module 2 port 1, these
numbers may be different depending on which module/port is accessed.
ONU Configuration
ONU Configuration: ONU Configuration is a sub-mode of the OLT
Configuration command mode. It is used for configuring of ONU logical port
parameters.
In the system prompt shown above, "2/4/31" represents OLT module 2, port 4
and ONU logical port 31 , these numbers may be different depending on which
module/port is accessed.
CLI
Command Access From/
Mode Parent Mode Access Command Prompt Functions
EXEC Telnet or NA (system login) BBS1000+> Allows the user to view
Terminal basic system information
Emulation and verify connectivity,
e.g. ping
Privileged EXEC enable BBS1000+# All EXEC mode
EXEC Command (optional: password) commands and
Mode configuration commands
that do not require saving,
are also permitted.
Debug EXEC debug BBS1000+(debug)# Use debug commands for
Command troubleshooting specific
Mode problems or during
troubleshooting sessions
with UTStarcom technical
support staff
Management Privileged configure management BBS1000+(config-mgmt)# Configuration of
Configuration EXEC BBS1000+ global
Command parameters
Mode
Terminal Privileged configure terminal BBS1000+(config-t)# Configuration of PON
Configuration EXEC global parameters
(Global) Command
Mode
OLT Interface Terminal interface epon-olt module/port BBS1000+(config-t-if-olt-1/1) Configuration of OLT
Configuration Configuration # parameters
(Global)
["1/1" represents the OLT
module and port numbers;
actual values may differ]
n
ONU OLT Interface onu Lport ID BBS1000+(config-if-onu-1/1/ Configuration of ONU
Configuration 1)# parameters
Configuration
["1/1/1" represents the OLT
module, OLT port & logical
ONU port numbers; actual
values may differ]
CLI
Command Access From/
Mode Parent Mode Access Command Prompt Functions
Gigabit Terminal interface giga-ethernet module/port BBS1000+(config-t-if-ge-1/1) Configuration of
Interface Configuration # Gigabit-Ethernet
(Global) parameters
Configuration ["1/1" represents the BBS
module and GE port
numbers; actual values may
differ]
Link Terminal interface link-aggregation LinkID BBS1000+(config-t-if-lg-1)# Configuration of Link
Aggregation Configuration Aggregation parameters
Interface (Global) ["1" represents the LAG ID]
Configuration
Interface Terminal interface range RangeID BBS1000+(config-t-if-range-g Configuration of range
Range Configuration e2/1-3)# parameters
(Global)
Configuration ["ge2/1-3" represents GE
module 2 ports 1-3]
Loopback Terminal interface loopback LoopID BBS1000+(config-t-if-lpb-1)# Configuration of Loopback
Interface ["1" represents the loopback Interface parameters
Configuration ID]
Configuration
VLAN Terminal interface vlan vlanID BBS1000+(config-t-vlan-333) Configuration of VLAN
Interface Configuration # parameters
(Global)
Configuration ["333" represents the VLAN
ID]
DHCP Terminal ip dhcp pool name BBS1000+(config-t-DHCP)# Configuration of DHCP
Configuration parameters
Configuration (Global)
ONU Upgrade Terminal onu-upgrade BBS1000+(config-t-onu-ugp) Configuration of ONU
Configuration Configuration # upgrading parameters
(Global)
CLI Access Level Each CLI command has an access level of 0, 1, 2, or 10. The CLI access levels
are described below:
Access Level:
1 Port-level user: The user has port level configuration read/write access, but
is not permitted to modify the system configuration.
2 Power user: The user can control the entire system excluding the
configuration of other login accounts.
10 Administrator: The user can control the entire system, including the
configuration of other login accounts.
CLI Syntax A CLI command includes the command itself and other mandatory and/or
Conventions optional keywords and parameters. This document uses the following CLI
syntax conventions:
Table 4 CLI Syntax Convention Description
Type Face
or Symbol Description
Boldface Characters in bold typeface represent a command or key word.
Italics Italics represent a variable or placeholder for a user supplied
parameter. In situations where italics are not appropriate, the
variable is enclosed in angle brackets (< >).
Plain text Plain text represents the screen display or system prompt.
<placeholder> Text enclosed in angle brackets (< >) indicate a variable or
placeholder supplied by the user when italics cannot be used.
[optional] Square brackets ([ ]) indicate optional keywords or parameters. For
optional multiple choice keywords, individual keywords are
separated by a vertical bar "|"
{x | y | z} Braces ({ }) indicate a required keyword choice. Individual keywords
are separated by a vertical bar "|"
Syntax Example 1:
BBS1000+(config-t)# mac-address-table static mac-address vlan vlanid
interface <interfaceType> <interfaceID>
Syntax Example 2:
BBS1000+(config-mgmt)# snmp-server community-string {ro|rw}
{enable|disable}
In example 1, "BBS1000+(config-t)#" is the system prompt;
"static-mac-address" is the CLI command; "mac-addr, vlanid and portnum" are
required user supplied values; "vlan and port" are required keywords; "cos
value" is an optional keyword and user supplied value.
CLI Command Help The BBS 1000+ CLI provides various help and shortcut keys. The table below
lists the main shortcuts and methods for obtaining help within CLI.
Method Function
Type "?" in any CLI command mode All available commands in the present
command mode are displayed.
Partial command entry + "?" All commands beginning with the text
entered are displayed. (Do not enter a space
before the question mark.)
Example 1:
Command: BBS1000+> ?
Example 2:
Command: BBS1000+(config-t)#po?
pon-sys
BBS1000+(config-t)#pon-sys
Example 3:
Hotkey
Table 6 Hotkeys
Hotkey Function
Ctrl-Z The command entered before pressing the hotkey will be
issued and the command mode will return to EXEC
command mode. If no command is entered, present
command mode state returns to the EXEC command
mode.
Ctrl-B, left arrow Move the cursor left without deleting characters
Ctrl-F, right arrow Move the cursor right until reaching the end of the line
Ctrl-E Move the cursor to the end of the line
Esc-B Move the cursor back one word
Esc-F Move the cursor forward one word
Backspace Move the cursor left deleting the previous character
Ctrl-D Delete the character at the present cursor position
Ctrl-U Delete text up to the cursor
Ctrl-K Delete text after the cursor
Ctrl-A Move the cursor to the beginning of the line
Esc-D Delete remainder of word
Ctrl-W Delete word up to the cursor
Ctrl-P Get prior command history
Ctrl-N Get next command history
Up arrow Review command history one at a time
Down arrow View next command until reaching the current command
Ctrl-T Transpose current and previous character
BBS 1000+ has 1 Gigabit Switch Module (GSM) and one or two Line Terminal
Modules (LTM). There are 12 Gigabit Ethernet switch ports on the GSM module.
Four of these GE ports (GE3/1-GE3/4) provide BBS 1000+'s four uplink ports.
The other 8 GE ports (GE1/1-GE1/4 and GE2/1-GE2/4) are the internal
downlink ports connected to two LTM modules. Modules LTM1 and LTM2
provide the BBS 1000+ system with eight external downlink ports. The four ports
of the LTM1 module on the right are named OLT1/1 to OLT1/4. The ports of the
LTM2 module on the left are named OLT2/1 to OLT2/4.
There are four uplink ports and eight downlink ports on the BBS 1000+ back.
BBS 1000+ PON BBS 1000+ supports PON running mode which includes system running mode,
Running Mode PON port mode and ONU running mode, refer to the figure below.
Figure 7 BBS1000+ PON running mode
Unique-tag mode
All successfully registered ONUs are automatically assigned to different
VLANs. After passing OLT, downstream data is marked untagged.
Mixed-tag Mode
This system running mode includes two PON port modes which are
Transparent mode and Stck-tag mode.
PON port Mode
Transparent mode
All successfully registered ONUs are automatically assigned to a default
VLAN(VLAN ID=0). OLT will not do any tag manipulation and ONU is not
associated to any specific tag.
Stack-tag mode
All successfully registered ONUs are assigned a default VLAN(VLAN ID=1).
After passing OLT port, tag will be added to upstream untagged packets,
VLAN tag is removed from downstream tagged packets with tag equal to
'stacked tag
QinQ tag handling mode
All successfully registered ONUs are assigned a default VLAN(VLAN
ID=1). In addition to customer's VLAN tag, a service provider's VLAN tag
is added to a packet sent upstream and removed from a packet sent
downstream. This is also called double tag mode.
QinQ mode could only be configured when the system is in mixed-tag
mode and the PON port is in stack-tag mode. Under the same OLT PON
port, different ONU could be configured as QinQ mode or non-QinQ
mode.
"stack-tag" mode and "transparent" mode would be based on PON port, and
"QinQ" mode would be based on ONU.
In Unique-tag system running mode, vlan-mode per PON port and QinQ per
ONU configurations could not be configured. PON running mode for port and
ONU are all fixed.
Tag Handling in Different The VLAN handling mechanism for downstream/upstream data through BBS
Running Mode 1000+ system's PON part are different for different running mode. For the
composition of BBS 1000+ PON part, please refer to Figure 8
For detailed information about the PON part, please refer to Table 8.
Figure 8 BBS 1000+ PON Part
Unique tag handling mode Match native tag Not match native tag
Unicast/ Upstream Tagged Keep tag Discard
Multicast/
Untagged Add native tag
Broardcast
Downstream Tagged Remove tag Discard
Untagged Discard
Transparent tag handling mode Match native tag Not match native tag
Unicast/ Upstream Tagged Keep tag Keep tag
Multicast/
Untagged Keep untagged
Broardcast
Downstream Tagged Keep tag Keep tag
Untagged Keep untagged
Stack tag handling mode Match native tag Not match native tag
Unicast/ Upstream Tagged Keep tag Keep tag
Multicast/
Untagged Add native tag
Broardcast
Downstream Tagged Remove tag Keep tag
Untagged Keep untagged
QinQ tag handling mode Match native tag Not match native tag
unicast/multicast/bo Upstream Tagged Add native tag Add native tag
ardcast
Untagged Add native tag
Downstream Tagged Remove tag Remove tag
untagged Keep untag
Updating the Running The default running mode of the BBS 1000+ system is Transparent mode under
Mode Mixed-tag mode. The user can modify the system running mode at the
Configure Management level and can modify the vlan mode at the PON port
as well as can configure ONU mode per ONU.
After modifying BBS 1000+'s running mode, you must save the configuration
and reboot the system, as shown in the example below.
For Example:
Password:
telnet@BBS1000+> enable
describion :[ePON]
sysName :BBS1000+
Location :1275 Harbor Bay Parkway, Alameda, CA 94502,
Tel:1(510)864-8800
Contact :John Smith
Device Id :abcdefghijklmnopqrstuvwxyzabcd
Up Time :[1 days 16h:58m:52s]
CLI Timeout :900 seconds
Inband TTL :128
Outband TTL :128
Management from ONU:disabled
System mode : mixed-tag
BPDU Flood : disable
CPU manufacturer: freescale
CPU type : MPC8250
Memory size : 128M-Byte
Flash size : 16M-Byte
Switch buffer : 1M-Byte
telnet@BBS1000+#
telnet@BBS1000+(config-mgmt)# save
telnet@BBS1000+(config-mgmt)# reboot
rebooting...
telnet@BBS1000+(config-mgmt)# save
telnet@BBS1000+(config-mgmt)# reboot
rebooting...
telnet@BBS1000+(config-t-if-olt-1/1)# vlan-mode
telnet@BBS1000+(config-t-if-olt-1/1)#
6 Set the system's working mode as default and reboot the BBS 1000+ system.
telnet@BBS1000+# configure management
telnet@BBS1000+(config-mgmt)# reboot
rebooting...
Running mode
Configuring related
Commands
Table 9 Commands to configure running mode
Setting up BBS 1000+ Before configuring BBS 1000+ as a L2 switch, the following concepts should be
as a L2 switch noted:
1 ONU Lport (Logical Port) Assignment
2 ONU Registration Process
3 In-Band and Out-Band Management
4 ICMP/ARP
ONU Lport (Logical Port) Each of the BBS1000+'s downlink ports, referred to hereafter as PON ports, can
Assignment connect with up to 64 ONUs. Since these 64 ONUs are connected to the same
physical PON port, the individual ONUs are assigned to one of the PON port's
64 logical ports (lports). For assigning ONU and PON port connections, the
BBS1000+ system uses a binding table. The table sets a mapping relationship
between ONU MAC addresses and individual lports. The binding table is user
defined, enabling the lports to be assigned statically.
ONU Registration By default, Logical Port (lport) to MAC address binding is enabled.
Process
When an ONU is connected to the BBS1000+ and powered on, it goes through
the following registration process:
1 The OLT assigns the ONU a Logical Link ID (LLID).
2 The pre-configured lport number is obtained from the binding table.
3 This lport number is assigned to the ONU.
4 The VLAN ID and other attributes are assigned to the ONU.
For a list of other attributes assigned in step 4 above, refer to Return List on the
Radius Server on page 248.
In-Band and Out-Band Through In-Band management an administrator has remote management
Management access to the BBS 1000+ system. In-Band management can be performed via
the BBS 1000+'s Uplink ports (GE3/1-4) or via ONUs which connect to BBS
1000+'s Downlink ports(GE1-2/1-4).
From BBS 1000+ the remote device can be pinged to validate the connection
and routing.
BBS 1000+ supports pinging out from the In-Band interface only.
Perform the tasks below to configure BBS 1000+ as a L2 switch for untagged
downstream and untagged upstream traffic.
In the following example the PCs connected to the ONU and BBS 1000+ receive
their IP addresses statically.
Example Topology
Figure 11 BBS 1000+ L2 switch configuration topology example
In this example, the BBS 1000+ default lport binding function is enabled.
ONU1's MAC address is bound to GE1/1's lport 1
To enable communication between the PC and the BBS 1000+'s Uplink port
(GE3/1), the uplink port must be a member of the ONU's VLAN. In the example
above, BBS 1000+'s GE3/1 uplink port must be a member of VLAN 101 to
enable communications with PC1.
To ensure that the BBS 1000+'s L2 switch is functioning properly, the connection
between the PC2 and the PC1 must be checked. It can be tested by pinging
from the PC1 to the PC2 or vice versa.
Configuration Requirements
The following example can work in three modes, but only step 6 is given for
different three modes, other steps assume that BBS1000+ is running in
Stack-tag mode.
Configuration Tasks The general tasks involved in configuring the BBS 1000+ L2 switch are given
below. After this task overview, detailed steps are described for each task, using
the topology example in Figure 11.
1 Reconfigure the Management port IP address
2 Login to BBS 1000+ via the management port
3 Configure the ONU's MAC and PON's lport binding
4 Activate the OLT port and the lport binding
5 Verify the OLT and ONUs configuration
6 Configure the servie VLAN for GE3/1and GE1/1
Configure the service VLAN for GE3/1 in Unique-tag Mode
Configure the service VLAN for GE3/1& GE1/1 in Stack-tag Mode
Configure the service VLAN for GE3/1 & GE1/1 in Transparent Mode
7 Perform a connection test
telnet@BBS1000+(config-mgmt)#
telnet@BBS1000+(config-mgmt)#
4 Enter the following command to remotely connect to the BBS 1000+ system.
c:\> telnet 192.168.103.227
After the connection is established with BBS 1000+, the following prompt will be
displayed on the screen:
Username:
Pasword:
Password:*****
telnet@BBS1000+>
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)#
3 Since ONU1 is assigned lport 1, enter the OLT lport 1 configuration command
mode.
In the following command "onu 1" is the same as OLT 1/1's lport 1. To assign
the ONU lport 5, the command would be "onu 5".
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)#
4 Now from inside lport 1's configuration command mode, bind ONU1's MAC
address with this lport (lport 1).
Part Number L2 CO00 2321 06 15 00 GEPON OLT OLT BBS 1000+
June 2007 CLI Operation Guide
56 Chapter 3: Starting up BBS 1000+ System
The ONU's MAC address can be found on a label on the ONU's bottom
cover.
telnet@BBS1000+(config-if-onu-1/1/1)# dba-sla mac
00:07:ba:34:bd:e7
telnet@BBS1000+(config-if-onu-1/1/1)#
5 Return to the CONFIG Terminal command mode by entering the exit command
twice.
telnet@BBS1000+(config-if-onu-1/1/1)# exit
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
When the communication between ONU and OLT is normal, the CLI
command show interface epon-olt 1/1 mac-address-table can be used to
obtain the ONU's MAC address.
Activate the OLT port and the lport binding
1 Enter the following command to enter port OLT1/1's configuration command
mode.
telnet@BBS1000+(config-t)# interface epon-olt 1/1
telnet@BBS1000+(config-t-if-olt-1/1)#
2 The OLT port is in the shutdown state by default, enter the following command
to activate the OLT port..
telnet@BBS1000+(config-t-if-olt-1/1)# no shutdown
telnet@BBS1000+(config-t-if-olt-1/1)#
Upon the OLT port activation, the connected ONU will be registered
automatically and the lport is bound to the ONU's MAC address.
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-101)#
VLAN 101:
Name :PON 1
port(s) or group(s) :ge1/1,ge3/1
Tagged port(s) or group(s) :ge1/1
Untagged port(s) or group(s) :ge3/1
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-101)#
VLAN 101:
Name :PON 1
port(s) or group(s) :ge1/1,ge3/1
Tagged port(s) or group(s) :
Untagged port(s) or group(s) :ge1/1,ge3/1
4 Return to the CONFIG Terminal command mode.
telnet@BBS1000+(config-t-vlan-101)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# exit
Configure the service VLAN for GE3/1 & GE1/1 in Transparent Mode
1 Create VLAN 101.
telnet@BBS1000+(config-t)# vlan 101
telnet@BBS1000+(config-t-vlan-101)#
telnet@BBS1000+(config-t-vlan-101)#
VLAN 20:
Name :PON 1
port(s) or group(s) :ge1/1,ge3/1
Tagged port(s) or group(s) :
Untagged port(s) or group(s) :ge3/1, ge1/1
telnet@BBS1000+(config-t)#
PON Authentication The BBS 1000+ system can be configured using either of the following two
Method authentication methods:
Local authentication -- enabled by default
Remote authentication through the RADIUS (Remote Authentication Dial-In
User Service) server (IEEE 802.1x).
Example Topology
Figure 13 Configuring BBS 1000+ as a L3 switch
In the topology above, ports OLT1/1 and OLT1/2 are connected to two PCs via
ONUs. The uplink is connected to the L3 Switch's g1/0/5 port via BBS 1000+'s
GE3/1 uplink port.
In this example BBS 1000+ uses lport binding, to bind ONU1's MAC address
with OLT1/1's lport 1 and ONU2's MAC address is bound to OLT1/2's lport 1.
When BBS 1000+ operates as a L3 Switch, the uplink port (GE3/1) is configured
as a Routed Interface, and the downlink ports OLT1/1 and OLT1/2 are
configured as one Super VLAN.
To ensure that the BBS 1000+'s L3 switch function is working normally, the L3
connection between the PC and the Cisco 3750 switch must be tested. In order
to test the connection, an IP address must be configured for the Cisco 3750
switch's g1/0/5 port. Then from PC1, ping the BBS 1000+'s Super SVI. Then
from the BBS 1000+ GE3/1 port, ping the Cisco 3750 switch's g1/0/5 port.
Finally from PC1 ping the Cisco 3750 g1/0/5 port.
Configuration Requirements
The Cisco switch is configured as in the example network topology and is
accessible from BBS 1000+.
Configuration Tasks The general tasks involved in configuring BBS 1000+ as an L3 switch are given
below. After this task overview, detailed steps are described for each task, using
the topology example in Figure 13.
1 Reconfigure the Management port's IP address.
2 Login to BBS 1000+ via the Management port.
3 Configure the ONU's lport and PON's MAC binding.
4 Activate the OLT port and enable lport binding.
5 Verify the OLT and ONUs configuration
6 Configure the Router Interface for GE3/1.
7 Configure the Super SVI:
Configure the Super SVI in Unique-tag Mode
Configure the Super SVI in Transparent Mode
Configure the Super SVI in Stack-tag Mode
8 Create a Router Interface on the Cisco switch.
9 Add a static route on BBS 1000+
10 Configure the IP address for the PCs
11 ARP Configuration on BBS 1000+.
12
The default login username/password combination is: admin/admin for the
system administrator and guest/guest for a read only user.
telnet@BBS1000+(config-mgmt)#
telnet@BBS1000+(config-mgmt)#
1 Enter the following command to remotely connect to the BBS 1000+ system.
c:\> telnet 192.168.103.227
After the connection is established with BBS 1000+, the following prompt will be
displayed on the screen.
Username:
Pasword:
Password:*****
telnet@BBS1000+>
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)#
3 Since ONU1 is assigned lport 1, enter the OLT lport 1 configuration command
mode.
In the following command "onu 1" is the same as OLT 1/1's lport 1. To assign
the ONU lport 5, the command would be "onu 5".
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)#
4 Now from inside lport 1's configuration command mode, bind ONU1's MAC
address with this lport (lport 1).
Part Number L2 CO00 2321 06 15 00 GEPON OLT OLT BBS 1000+
June 2007 CLI Operation Guide
64 Chapter 3: Starting up BBS 1000+ System
The ONU's MAC address can be found on a label on the ONU's bottom
cover.
telnet@BBS1000+(config-if-onu-1/1/1)# dba-sla mac
00:07:ba:34:af:36
telnet@BBS1000+(config-if-onu-1/1/1)#
5 Return to the CONFIG Terminal command mode by entering the exit command
twice.
telnet@BBS1000+(config-if-onu-1/1/1)# exit
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/2)# onu 1
telnet@BBS1000+(config-if-onu-1/2/1)#
7 Return to the CONFIG Terminal mode by entering the exit command twice.
telnet@BBS1000+(config-if-onu-1/2/1)# exit
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)#
2 The OLT port is in the shutdown state by default, enter the following command
to activate the OLT port.
telnet@BBS1000+(config-t-if-olt-1/1)# no shutdown
telnet@BBS1000+(config-t-if-olt-1/1)#
After the OLT port is activated, the connected ONU will be registered
automatically and the lport will be bound to the ONU's MAC address.
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/2)#
5 Activate OLT1/2 port. (The connected ONU is registered at the same time).
telnet@BBS1000+(config-t-if-olt-1/2)# no shutdown
telnet@BBS1000+(config-t-if-olt-1/2)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
-------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=1, LLID[0]=1
Name = ONU-1
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU vlan id = 1
ONU mac address = 00:07:ba:34:bd:b1
User ID = onu_2
RTT TQ = 4
Framed IP Address = 0.0.0.0
Framed Netmask = 0.0.0.0
Laser_on_time = 4
Laser_off_time = 4
Mpcp Timeout = 4000
Multicast filtering = enable
P2p-access policing = disable
P2p-access port_number = 63
P2p-access port bitmap[1-32][33-64]:[0xffffffff][0xffffffff]
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.18
Bootloader version = 02.01.10
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-ge-3/1)#
telnet@BBS1000+(config-t-if-ge-3/1)#
telnet@BBS1000+(config-t-if-ge-3/1)#
telnet@BBS1000+(config-t-if-ge-3/1)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-1000)# exit
telnet@BBS1000+(config-t)#
In this example, ge1/1-2 should be tagged member of VLAN 1000, ge1/1 and
ge1/2 are pre-configured as tagged member of VLAN 101 and VLAN 165
respectively.
4 Add SVI member interfaces (VLAN 101 and 165) to the Super SVI.
telnet@BBS1000+(config-t-if-vlan-1000)# member 101,165
telnet@BBS1000+(config-t-if-vlan-1000)# no shutdown
telnet@BBS1000+(config-t-if-vlan-1000)# exit
telnet@BBS1000+(config-t)#
Member: 101,165
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-101)# exit
telnet@BBS1000+(config-t)#
2 Create VLAN 165 and assign GE1/2 as untagged member of the VLAN.
telnet@BBS1000+(config-t)# vlan 165
telnet@BBS1000+(config-t-vlan-165)# exit
telnet@BBS1000+(config-t)#
3 Create a VLAN and assign GE ports (GE1/1 and GE1/2) as tagged members of
the VLAN.
telnet@BBS1000+(config-t)# vlan 1000
telnet@BBS1000+(config-t-vlan-1000)# exit
telnet@BBS1000+(config-t)#
6 Add SVI member interfaces (VLAN 101 and 165) to the Super SVI.
telnet@BBS1000+(config-t-if-vlan-1000)# member 101,165
telnet@BBS1000+(config-t-if-vlan-1000)# no shutdown
telnet@BBS1000+(config-t-if-vlan-1000)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-101)# exit
GEPON OLT OLT BBS 1000+ Part Number L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
Configuring BBS 1000+ as an L3 switch 69
telnet@BBS1000+(config-t)#
2 Create VLAN 165 and assign GE1/2 as untagged member of the VLAN.
telnet@BBS1000+(config-t)# vlan 165
telnet@BBS1000+(config-t-vlan-165)# exit
telnet@BBS1000+(config-t)#
3 Create a VLAN and assign GE ports (GE1/1 and GE1/2) as tagged members of
the VLAN.
telnet@BBS1000+(config-t)# vlan 1000
telnet@BBS1000+(config-t-vlan-1000)# exit
telnet@BBS1000+(config-t)#
6 Add SVI member interfaces (VLAN 101 and 165) to the Super SVI.
telnet@BBS1000+(config-t-if-vlan-1000)# member 101,165
telnet@BBS1000+(config-t-if-vlan-1000)# no shutdown
telnet@BBS1000+(config-t-if-vlan-1000)# exit
telnet@BBS1000+(config-t)#
Member: 101,165
telnet@BBS1000+(config-t)#
8 Configure ONU-VLAN of the ONU1 connected to the OLT1/1 and the ONU2
connected to the OLT1/2.
telnet@BBS1000+(config-t)# interface epon-olt 1/1
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t-if-olt-1/2)#exit
telnet@BBS1000+(config-t)#
3750>
3750>enable
Password:******
3750(config)#
3750(config-if)#
3750(config-if)#
4 Configure the Cisco switch g1/0/5 port's IP address and start up this port.
3750(config-if)#ip address 40.0.0.1 255.255.255.0
3750(config-if)# no shutdown
3750(config-if)#
3750(config)#exit
3750#
Building configuration...
[OK]
3750#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
------------------+-----------------+--------+----------+----
40.0.0.1 00:13:1a:d1:03:48 dynamic ge3/1 319
50.0.0.100 00:0d:56:f6:3b:8c dynamic Vlan101 329
60.0.0.100 00:0d:56:fb:e1:f3 dynamic Vlan165 359
3 From BBS 1000+, use the ping command to test the connection between BBS
1000+'s Router Interface and Cisco 3750.
telnet@BBS1000+(config-t)# ping 40.0.0.1
!!!!!
telnet@BBS1000+(config-t)#
4 In the following example, PC1 is used to ping test the connection between PC1
and the Cisco 3750 switch, but first a new routing item must be added to the
Cisco switch's routing table.
3750(config)#ip route 50.0.0.0 255.255.255.0 40.0.0.10
BBS 1000+ Working in This section describes when BBS 1000+ works as an L2 switch and how to
QinQ Mode configure that BBS 1000+ works in QinQ mode as required in application.
Application Description The packets from the customer connected to the BBS 1000+ are tagged. BBS
1000+ creates a channel for transmiting the packets from the customer, adding
its ISP service VLAN to the packets. And the double tagged packets are
processed by the upstream network side of BBS 1000+.
Example Topology
Figure 15 QinQ Application Example Topology
OLT1/1 of BBS 1000+ is connected to the customer access side through ONU1,
and the uplink GE3/1 is connected to the network side. VLAN 20 is the service
VLAN of the customer and VLAN 10 is the ISP service VLAN on BBS 1000+.
Configuration Requirements
Suppose ONU1 is registered successfully.
The equipment on the upstream network side can process the double-tagged
data.
Configuration Tasks
telnet@BBS1000+(config-t-if-olt-1/1)#
telnet@BBS1000+(config-t-vlan-10)#exit
VLAN 10:
Name :
port(s) or group(s) :ge1/1,ge3/1
Tagged port(s) or group(s) :ge1/1,ge3/1
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-if-olt-1/1)# onu-vlan 1 10
telnet@BBS1000+(config-t-if-olt-1/1)#
Result Analysis:
The packets with service VLAN tag(20) are sent from the downstream
customer access side. When passing through BBS 1000+, they are added
with ISP service VLAN tag (10). On the upstream network side, the packets
with double tags are received.
The packets with double tags are sent from the upstream network side.
When passing through BBS 1000+, ISP service VLAN tag (10) is removed.
On the downstream ISP access side, the packets with customer service
VLAN tag (20) are received.
In-band and Out-band In-Band management provides the administrator remote management access to
Introduction BBS 1000+ through an ISP network. Management traffic must be separate from
other service traffic. This can be achieved via VLAN implementation, by
configuring a management VLAN that is separate from other service VLANs.
BBS 1000+ can use any of the uplink ports (GE 3/1-4) for remote in-band
management. The port used is then assigned to a particular VLAN, according to
prior network planning.
BBS 1000+ can be managed from downlink ports via ONU. This feature can be
configured under Management Configuration mode. It is disabled by default.
description :[ePON]
sysName :BBS1000+
Location :1275 Harbor Bay Parkway, Alameda, CA 94502,
Tel:1(510)864-8800
Contact :John Smith
Device Id :abcdefghijklmnopqrstuvwxyzabcd
Up Time :[2 days 23h:26m:43s]
CLI Timeout :900 seconds
Inband TTL :128
Outband TTL :128
Management from ONU:disabled
System mode : mixed-tag
BPDU Flood : disable
CPU manufacturer: freescale
CPU type : MPC8250
Memory size : 128M-Byte
Flash size : 16M-Byte
Switch buffer : 1M-Byte
telnet@BBS1000+#
In-Band Configuration In the following example, the In-Band management port is configured as an SVI.
example-- SVI
Example Topology
Figure 17 In-Band Configuration Topology
Configuration Requirements
The management PC must be able to connect with the Cisco L3 switch.
Configuration Tasks The general tasks involved in configuring the In-Band management port using
SVI are given below. After this overview, detailed steps are described for each
task, using the topology example in Figure 17.
1 Configure the BBS 1000+ GE3/1 uplink port as SVI
2 Configure SVI on the Cisco switch.
3 Add a static IP route on BBS 1000+
4 Configure the gateway for the PC
5 Login to BBS 1000+ via telnet.
telnet@BBS1000+#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-400)#
telnet@BBS1000+(config-t-vlan-400)#exit
telnet@BBS1000+(config-t)#
VLAN 400:
Name :
port(s) or group(s) :ge3/1
Tagged port(s) or group(s) :ge3/1
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-vlan-400)#
telnet@BBS1000+(config-t-if-vlan-400)# exit
telnet@BBS1000+(config-t)#
ip mask : 255.255.255.0
host ip address : 192.168.103.15
next hop : 0.0.0.0
ftp user name : gepon
ftp user password : 123456
boot file name : 2.31.0.10.stz
boot device : flash
The next hop line specifies out-band management default gateway, which is
0.0.0.0.
If the next hop field is any other value except 0.0.0.0, there are two methods to
reconfigure the out-band gateway.
Enter Vxworks mode
Using [no] ip route command
BBS1000+(debug)# bcm
BCM.0> reboot
...
DS1921 init successful ( Bus Clock 66 MHz),RTC is OK
I2C clock rate 400 KHz
BBS1000+A BOOTROM version: 01.03.01.000
Press any key to stop auto-boot...
1
[VxWorks Boot]: c
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : flash0
processor number : 0
host name : host
file name : BBS1000plus.stz
inet on ethernet (e) : 192.168.103.251:ffffff00
inet on backplane (b): 255.255.255.0
host inet (h) : 192.168.103.5
gateway inet (g) : 192.168.103.254 .
user (u) : epon
ftp password (pw) (blank = use rsh): epon
flags (f) : 0x0
target name (tn) : aaa.st
startup script (s) :
other (o) : motfcc
telnet@BBS1000+(config-mgmt)#
3750>
3750>enable
Password:******
3750#configure terminal
3750(config)#
3750(config-if)#
3750(config-if)#no shutdown
3750(config-if)#
telnet@BBS1000+(config-t)#
3 From the login prompt, enter the user name and password.
Username: Admin
Password: *****
Initial SNMP The GEPON NMS communicates with NEs via the Simple Network
Configuration Management Protocol (SNMP) for supporting various management functions.
Each managed NE is configured with an SNMP Agent, which supports SNMP
Version 2c (SNMPv2c).Each NE SNMP agent maintains a persistent
Management Information Base (MIB), a database containing node level
inventory, fault and performance management information. The NE SNMP
Agent also controls the flow of management information between the
management server and the node.
Application Description
In this example Netman 4000 is the SNMP server used to manage BBS 1000+.
Using in-band management and the management VLAN is 400.
Example topology
Figure 19 SNMP Configuring Topology
Configuration Requirements
Netman 4000 OMC-D has been installed on the SNMP Server.
The L3 Switch Cisco 3750 interfaces connected to SNMP server and BBS
1000+ have been configured.
Configuration Tasks The general tasks involved in configuring SNMP on the BBS 1000+ system are
given below. After this task overview, detailed steps are described for each task,
using the topology example in Figure 19.
1 Configure the BBS 1000+ GE3/1 uplink port as an SVI
2 Add BBS 1000+ Node on Netman 4000 OMC-D.
The default system administrator's account and password are: admin and
admin.
telnet@BBS1000+#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-400)#
telnet@BBS1000+(config-t-vlan-400)#exit
telnet@BBS1000+(config-t)#
VLAN 400:
Name :
port(s) or group(s) :ge3/1
Tagged port(s) or group(s) :ge3/1
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-vlan-400)#
telnet@BBS1000+(config-t-if-vlan-400)# exit
telnet@BBS1000+(config-t)#
8 Perform a connection test from the BBS 1000+ to the SNMP Server.
telnet@BBS1000+(config-t)# ping 192.168.103.100
telnet@BBS1000+#
telnet@BBS1000+(config-mgmt)#
telnet@BBS1000+(config-mgmt)#
telnet@BBS1000+(config-mgmt)#snmp-server community
"myprivate" rw
telnet@BBS1000+(config-mgmt)#
User can configure trap receiver on SNMP Server, too. Details please refer to
Netman 4000 OMC-D Operation Guide.
5 Verify the SNMP configuration on BBS 1000+
telnet@BBS1000+(config-mgmt)# show snmp-server
sysName : BBS1000+
Location: 1275 Harbor Bay Parkway, Alameda, CA 94502,
Tel:1(510)864-8800
Contact : John Smith
upTime :[0 days 00h:05m:39s]
SNMP is Enabled.
SNMP read-only access community string: mypublic
SNMP read-write access community string: myprivate
SNMP Trap host ip : 192.168.103.100
SNMP Trap commuinity: mypublic
SNMP Trap status : enable
SNMP Trap port : 162
3 Right click the right blank area and select "create NE" on the shortcut menu.
4 Input IP address as 10.0.0.10. This is the IP address for the interface of the BBS
1000+'s uplink GE port GE3/1.
5 Select BBS 1000+ from NE Type drop list.
6 Input getcommunity as "mypublic" and writeCommunity as "myprivate".
7 Click <Add>.
8 From Netman 4000 OMC-D TopoUI Client, click "Release Edit Lock" icon.
UTStarcom's GEPON BBS 1000+ switches are configured at the factory with
default parameters that permit basic operation of the system.
Configuring Basic This section describes how to configure the following basic system parameters:
System Information
Contact information
System location
System name
System description
System device ID
System clock
System hostname
All configuration commands listed in below table must be performed from the
Configure Management command mode.
Table 10 ASIC System Information Configuration Commands
If the string includes spaces, enclose it between single or double quote marks.
All strings, except system clock, can contain any combination of alphanumeric
and punctuation characters.
Configuration Examples
description :[ePON]
sysName :BBS1000+
Location :1275 Harbor Bay Parkway, Alameda, CA 94502,
Tel:1(510)864-8800
Contact :John Smith
Device Id :UTS-0000-0000-0000
Up Time :[0 days 02h:40m:51s]
.. screen output truncated...
2 Change the BBS 1000+ system's description to "GEPON BBS 1000+ system".
BBS1000+(config)# configure management
telnet@BBS1000+-1(config-mgmt)#
success
telnet@BBS1000+-1(config-mgmt)#
Configuring Layer 2 BBS 1000+ Gigabit-Ethernet ports, Link Aggregation ports, PON ports or a
Ports range of interfaces can be configured as Layer 2 ports.
GE ports are switch ports associated with a physical GSM port
Link Aggregation ports are composed of GE ports
PON ports are OLT ports associated with a physical LTM port
Interface ranges are composed of GE ports or Link Aggregation ports
Layer 2 GE/LAG ports are used for managing the physical port and
associated layer 2 protocols and do not handle routing or bridging.
Introduction to BBS
1000+ GE ports
Depending on whether the link is an uplink or downlink, change of the link status
using the following rules:
For BBS 1000+ uplink GE port, when it has physical link, its link status is Up.
For BBS 1000+ downlink GE port, if OLT port's administrative status is Enable,
the downlink GE port's link status is Up.
PVID
PVIDPort based VLAN IDis used to label GE ports' VLAN association. If a
downstream untagged packet is received by a BBS 1000+ OLT's uplink port
(GE3/1-4), the packet will be assigned the port's PVID.
The maximum packet rate on BBS 1000+ is 262143pps. As shown in Figure 22,
the Broadcast storm control threshold is 10%. When the broadcast traffic rate
reaches 10% of the maximum port rate (262143pps) or 26214pps, the system
will drop the additional broadcast packets. Once the rate drops below the
configured threshold value, the packets will again be forwarded.
When the threshold is set to 0 for a particular data type, all of that type of traffic
will be dropped.
On BBS 1000+ STP packets are treated the same as Multicast packets,
therefore when the Multicast Storm Control parameter is zero(0), all STP
packets will also be dropped.
The following warning message is display each time the Storm control
configuration is changed.
Issue the CLI show configuration running command to display the traffic
storm control configuration.
Auto Negotiation
The uplink GE ports on BBS 1000+ have the Auto Negotiation function. When
auto negotiation is enabled on the ports at both ends, the working mode (half or
full duplex) and rate (10Mbps, 100Mbps or 1000Mbps) is automatically set to the
highest level provided on both ports.
In order for auto negotiation to function properly, the far-end equipment should
also have this function. Auto negotiation is enabled by default.
The default uplink GE port working mode and rate is full-duplex at 1000Mbps.
The GE port can only operate at 1000Mbps when operating in full-duplex. When
the rate is set to 100Mbps or 10Mbps, after enabling auto negotiation function,
the two ports will only need to decide the working mode between half-duplex
and full-duplex.
Flow Control
BBS 1000+ provides flow control in both the receive and transmit directions. In
order for flow control to function properly, the far-end equipment should also
have this function. Flow control is enabled by default.
Assuming that flow control is activated on the GE port, when traffic congestion
occurs, the port will send a message to the far-end port informing it to stop
sending messages temporarily. After receiving the message, the far-end port will
stop sending packets to BBS 1000+ temporarily to avoid packet loss.
Ingress filter
If a downstream tagged packet is received by a BBS 1000+ uplink port
(GE3/1-4), it will be forwarded according to the port's configuration, as described
below:
If the uplink port's (GE3/1-4) Ingress filter function is enabled, only those
packets belonging to the uplink port's VLANs will be forwarded. Other
packets will be discarded.
If the uplink ports' (GE3/1-4) Ingress Filter function is not enabled, all packets
with VLAN IDs listed in the BBS 1000+ VLAN table will be forwarded,
regardless of whether the port is a member of the VLAN or not. Other
packets will be discarded.
Rate Limit
BBS 1000+ provides rate limiting on both upstream and downstream traffic of
the GE ports. The configurable rate range is 1-1000Mbps.
If the GE port's rate limit is set to 100Mbps and the ingress traffic rate exceeds
this limit, the excess incoming packets will be discarded. If the forwarding
method is First-In-First-Out (FIFO), then when the rate reaches 120Mbps, the
excess 20 Mbps will be discarded.
User-isolation
When user isolation is activated, users in the same VLAN of BBS 1000+
different downlink ports are separated from each other. Users under one
downlink port are always separated, even if user isolation is activated. The
default User-isolation value is Enabled. When any two of these users want to
communicate, they must communicate through the L3 level.
When the VLAN ID is not enough for all equipments connected in the BBS
1000+ downlink ports, or for whatever reason setting the same VLAN ID for
multiple equipments, and the users in these VLAN cannot visit each other, in
those cases, users need to activate user isolation function in the downlink ports.
In the above figure, ONU1 and ONU3 belong to VLAN100. If the PCs connected
to ONUs cannot visit each other, in this case, user needs to activate
user-isolation function in ports GE1/1 and GE1/4.
Also, in the above figure, ONU1 and ONU3 belong to VLAN100, If the PCs
connected to ONU1 and ONU3 can visit each other, in this case, user needs to
shut down user-isolation function in port GE1/1 port and GE1/4 port.
PCs connected to ONU1 and ONU2 can't visit each other for they are connected
to the same OLT1/1 port even if ONU2 belongs to VLAN100. If the
communication is needed between the above PCs, the above two ONU's
p2p-access work mode must be enable. For the details, refer to ONU p2p
Configuring on page 207.
GE ports Configuration
Tasks
Configuring Layer 2 BBS 1000+ has 12 GE ports which operate as layer 2 interfaces. These GE
Link Aggregation ports can be managed either individually. The four uplink ports can be also
managed as a Link Aggregation Group (LAG). LAGs group are a collection of
physical ports together as if they are a single port. By trunking several links of
equal speed together to form a port bundle, we can provide higher bandwidth
and redundancy between switches or servers.
Link Aggregation Before making physical connections between devices, the trunk should be
Interface Restrictions configured on the devices at both ends. When using a port trunk, note that:
Trunk ports must all be 1000 Mbps
Ports at both ends must be configured as trunk ports
Ports at both ends of a trunk must be configured identically, including speed,
duplex mode, and VLAN assignments
Trunk port members cannot be configured as mirror source or target ports
All the ports in a trunk must be treated as a whole when added or removed
from a VLAN
All the ports in the trunk group must be in the same spanning tree state
Ports in a trunk can only belong to the same VLANs as those assigned to the
trunk.
Enable the trunk prior to connecting any cables to avoid creating a loop
Disconnect all trunk port cables or disable the trunk ports before removing a
port trunk to avoid creating a loop
Link Aggregation Group The normal procedure for creating a Link Aggregation group is described below:
Management Procedure
1 Create an empty group by specifying the group ID (value from 1 to 32) and the
load-sharing algorithm. Once the link aggregation group is created, its default
PVID is 1.
2 Add Link Aggregation Group members. Be sure that all the members only
belong to the default VLAN.
3 Add the Link Aggregation Group to VLAN(s) as a normal Layer 2 interface.
Afterwards all the trunk ports become members of the VLAN(s)
4 If the LAG members are untagged, configure the Link Aggregation Group's
PVID when needed.
5 The Link Aggregation Group name can be assigned if required.
If the ports to be assigned to the trunk are already trunk VLAN members, the
following method is recommended for creating a Link Aggregation Group:
1 Create an empty group by specifying the group ID (value from 1 to 32) and the
load-sharing algorithm.
2 Add the LAG to VLAN(s) as a normal layer 2 interface
3 Add members to the Link Aggregation Group.
If the members are untagged, configure Link Aggregation Group PVID when
needed.
After the execution of this command the system will perform the following
actions:
Delete this Link Aggregation from all VLANs.
The ports will continue to be members of the previous trunk VLANs.
Delete this Link Aggregation in the BBS 1000+ system.
Example Topology
Figure 24 Link Aggregation Configuration Topology
Configuration Requirements
Base ID VLAN of BBS 1000+ is set to the default (101).
ONU1 is bound to lport 1 of OLT1/1, ONU2 is bound to lport 2 of OLT1/1 and
ONU3 is bound to lport 1 of OLT1/4. All ONUs can register with BBS 1000+
successfully.
The Channel-group has been pre-configured on the L3 Switch (Cisco 3750).
The link between the Cisco switch and the server is working normally.
Configuration Tasks The general tasks involved in creating a L2 Link Aggregation are given below.
After this task overview, detailed steps are described for each task, using the
topology example in Figure 24.
2 Specify the load-balance algorithm for use on LAG 2. In this example, the
Source IP algorithm is used.
The six load-balancing algorithms are: Source MAC; Destination MAC;,
Source and Destination MAC; Source IP; Destination IP; Source and
Destination IP
BBS1000+(config-t-if-lg-2)# load-balance src-ip
BBS 1000+(config-t)#
VLAN 101:
Name :PON 1
port(s) or group(s) :ge1/1,lg2*[]
Tagged port(s) or group(s) :ge1/1,lg2*[]
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-vlan-101)# exit
VLAN 101:
Name :PON 1
port(s) or group(s) :ge1/1,ge3/3-4,lg2*[]
Tagged port(s) or group(s) :ge1/1,ge3/3-4,lg2*[]
Untagged port(s) or group(s) :
VLAN 102:
Name :PON 2
port(s) or group(s) :ge1/1,lg2*[]
Tagged port(s) or group(s) :ge1/1,lg2*[]
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-vlan-102)# exit
VLAN 102:
Name :PON 2
port(s) or group(s) :ge1/1,ge3/3-4,lg2*[]
Tagged port(s) or group(s) :ge1/1,ge3/3-4,lg2*[]
Untagged port(s) or group(s) :
Independent VLAN learning deals with the layer 2 interface only. So, displaying
the MAC address table only shows the MACs learnt for specific LAGs, not the
port member of the trunk group.
All static MAC addresses and ACL rules associated with interface ge3/3-4
are cleared by this command.
2 Display VLAN 101 information.
telnet@BBS1000+(config-t-if-lg-2)# show vlan 101
VLAN 101:
Name :PON 1
port(s) or group(s) :ge1/1,lg2*[ge3/3-4]
Tagged port(s) or group(s) :ge1/1,lg2*[ge3/3-4]
Untagged port(s) or group(s) :
VLAN 293:
Name :PON 97
port(s) or group(s) :ge1/4,lg2*[ge3/3-4]
Tagged port(s) or group(s) :ge1/4
Untagged port(s) or group(s) :lg2*[ge3/3-4]
Removing the LAG on In order to avoid loops, Disconnect the physical LAG connections before
BBS 1000+ removing the LAG:
BBS1000+(config-t-if-lg-2)#
VLAN 101:
Name :PON 1
port(s) or group(s) :ge1/1,ge3/3-4,lg2*[]
Tagged port(s) or group(s) :ge1/1,ge3/3-4,lg2*[]
Untagged port(s) or group(s) :
VLAN 293:
Name :PON 97
port(s) or group(s) :ge1/4,ge3/3-4,lg2*[]
Tagged port(s) or group(s) :ge1/4
Untagged port(s) or group(s) : ge3/3-4,lg2*[]
GE: 3/3
Switchport: Enabled
Name: GE-11
MTU: 1500bytes
Speed: 1000Mbps
AdminStatus: Enable
Auto Negotiation: Enabled
Ingress vlan filter: Disabled
BBS1000+(config-t-if-lg-2)# exit
BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-lg-2)#exit
telnet@BBS1000+(config-t)#
VLAN 101:
Name :PON 1
port(s) or group(s) :ge1/1,ge3/3-4
Tagged port(s) or group(s) :ge1/1,ge3/3-4
Untagged port(s) or group(s) :
VLAN 293:
Name :PON 97
port(s) or group(s) :ge1/4
Tagged port(s) or group(s) :ge1/4
Untagged port(s) or group(s) :
--------+--------------+-----------------------+-------------
Practical Configuration In actual practice, the following LAG creation steps are usually followed:
Tips
1 Create VLAN(s)
2 Create a LAG
3 Add this LAG to the VLAN(s) created in the step 1.
4 Add member ports to the LAG.
The basic steps for performing these procedures are described below:
Create VLAN 101 and 102 and assign member ports to the VLANs
telnet@BBS1000+(config-t)# vlan 101
telnet@BBS1000+(config-t-vlan-101)# exit
telnet@BBS1000+(config-t-vlan-102)# exit
Create LAG 2
telnet@BBS1000+(config-t)# interface link-aggregation 2
VLAN 101:
Name :
port(s) or group(s) :ge3/3,ge3/4,lg1*[]
Tagged port(s) or group(s) :ge3/3,ge3/4,lg1*[]
Untagged port(s) or group(s) :
NOTE: All the static MAC address and ACL rules associated with
interface ge3/3-4 have been cleared.
VLAN 102:
Name :PON 2
port(s) or group(s)
:ge1/1,lg1*[ge3/1-2],lg2*[ge3/3-4]
Tagged port(s) or group(s)
:ge1/1,lg1*[ge3/1-2],lg2*[ge3/3-4]
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-if-lg-2)#
User can configure the link aggregation group Rtag while the group is first
created and empty only.
When referring to individual links within a LAG, the following notation is used.
The first active link inside the link aggregation group uses index 0; the
second uses index 1.
if the link of index M in an LAG is down or removed, the original index M+1
becomes index M link and the original M+2 becomes index M+1 link...
Example Topology
Figure 25 Using DMAC as Loading-sharing Rule
In the following example, GE3/1-4 belongs to VLAN 1 and VLAN 200; they are
tagged in VLAN 200 and untagged in VLAN 1 and are configured as member of
lg1. Lg1 uses DMAC as its load-sharing rule. The third party switch also has the
same configuration on its trunk group and also uses DMAC as the load-sharing
criteria. Traffic between Host1 and Host2 are tagged using VID=200. Here is the
BBS 1000+ configuration.
Configure Requirements
Base_VLAN_ID of BBS 1000+ is reconfigured from 101 to 200.
ONU is bound to lport 1 of OLT1/1 and can register to BBS 1000+
successfully.
Channel-group has been configured on L2 switch.
The link between L3 Switch and Host2 can work normally.
Configuration Steps
1 Logon to BBS 1000+.
Username:admin
Password:******
BBS1000+> enable
BBS1000+#
VLAN 200:
Name : LAG-Tst
port(s) or group(s) :ge1/1,ge3/1-4
Tagged port(s) or group(s) :ge1/1,ge3/1-4
Untagged port(s) or group(s) :
BBS1000+(config-t-vlan-200)# exit
BBS1000+(config-t)#
BBS1000+(config-t-if-lg-1)#
BBS1000+(config-t-if-lg-1)# exit
BBS1000+(config-t)#
BBS1000+(config-t-vlan-200)# exit
BBS1000+(config-t)#
BBS1000+(config-t-if-lg-1)#
BBS1000+(config-t-if-lg-1)#
Result Analyze
1 One link case
BBS 1000+ learns that MAC=00:00:00:00:02/VLAN200 needs to go to LAG1
through independent VLAN learning. It has 4 members in the LAG1 but only one
link up, traffic from Host1 to Host2 goes through L0 and returns from Host2 to
Host1 through L0 too.
Example Topology
Figure 30 Using DIP XOR SIP as Loading-share Rule
Configure Requirements
Base_VLAN_ID of BBS 1000+ is reconfigured from 101 to 200.
ONU is bound to lport 1 of OLT1/1 and can register to BBS 1000+
successfully.
Channel-group has been configured on L2 switch.
The link between L2 Switch and Host2 can work normally.
Configure Steps
1 Logon to BBS 1000+.
Username:admin
Password:******
GEPON OLT OLT BBS 1000+ Part Number L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
Configuring Layer 2 Link Aggregation 121
BBS1000+> enable
BBS1000+#
VLAN 200:
Name : LAG-Tst
port(s) or group(s) :ge1/1,ge3/1-4
Tagged port(s) or group(s) :ge1/1,ge3/1-4
Untagged port(s) or group(s) :
BBS1000+(config-t-vlan-200)# exit
BBS1000+(config-t)#
BBS1000+(config-t-if-lg-1)#
BBS1000+(config-t-if-lg-1)# exit
BBS1000+(config-t)#
BBS1000+(config-t-vlan-200)# exit
BBS1000+(config-t)#
BBS1000+(config-t-if-lg-1)#
BBS1000+(config-t-if-lg-1)#
Result Analyze
1 One link case, traffic all go through L0.
Figure 31 One link case, Rtag is DIP XOR SIP
There is only one link between BBS 1000+ and the third party switch. So the
traffic between host1 and host2 will go through L0 in the LAG1.
GEPON OLT OLT BBS 1000+ Part Number L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
Configuring Layer 2 Link Aggregation 123
Configuring Interface The Interface Range command allows specification of a range of interfaces to
Range which subsequent commands are applied. After issuing the Interface Range
command, the system prompt will change indicating access to the Interface
Range Configuration command mode. While in this mode, CLI commands will
be applied to all of the ports within the range.
The following parameters can be configured from the Interface Range command
mode:
Set the PVID for all ports in the range
Shutdown or enable (no shutdown) all ports in the range
There are two Interface Range types, GE port and Link Aggregation. As the
name implies, the GE Interface Range can only contain GE ports, whereas the
Link Aggregation type can only contain LAGs.
Interface Range
Configuration
Commands
Table 13 Interface Range configuration commands
Interface Range The following example assumes that GE3/1 and GE3/2 are already untagged
Configuration Example members of VLAN 100. This example will assign PVID 100 to a range of GE
ports (GE3/1-2).
BBS1000+(config-t-if-range-ge3/1-2)#
BBS1000+(config-t-if-range-ge3/1-2)#
GE: 3/1
Name: GE-9
MTU: 1500bytes
Speed: 1000Mbps
AdminStatus: Enable
Link Status: Down
PVID: 100
Configuring Layer 3 This section describes configuration of layer 3 interfaces on the GEPON BBS
Interface Parameters 1000+ switch. There are four types of layer 3 interfaces:
Routed Interface
Switch Virtual Interface
Super SVI
Layer 3 Link Aggregation Interface
Status Introduction There are two types of status conditions on BBS 1000+ L3 interfaces, the
Interface status and the Line Protocol status. Interface status indicates whether
the interface hardware is currently active or is disabled by the administrator. The
Line Protocol status indicates whether the software processes that handle the
line protocol consider the interface unusable or the interface has been disabled
by an administrator.
By default the interface status is down. When the interface is active, the
displayed interface status will be "up"
By default the line protocol status is down. It can be changed the shutdown
and no shutdown commands
An L3 interface only functions properly when both the interface status and line
protocol status are up.
The first line of the display above indicates that the GE3/1 interface has a
physical link which is active and the line protocol is up.
Configuring Secondary An L3 interface can have one primary IP address and up to 32 secondary IP
IP address addresses. Packets generated by the BBS 1000+ software always use the
primary IP address. Therefore, all routers and access servers should reside in
the same subnet as the primary IP address.
Hosts can determine subnet masks using the Internet Control Message Protocol
(ICMP) mask request message. Routers respond to this request with an ICMP
mask reply message.
Secondary addresses are treated like primary addresses, except the system
does not generate a datagram using a secondary IP address as their source
address, other than routing updates with secondary source addresses. IP
broadcasts and Address Resolution Protocol (ARP) requests are handled
properly, as are interface routes in the IP routing table.
Example: The uplink port GE3/1 primary IP address is 10.0.0.1/25, it's subnet
allows up to 126 hosts per logical subnet. But on one physical subnet there
are 200 hosts connected to BBS 1000+ via two L2 Switches. Using
secondary IP address 20.0.0.1/25 on GE3/1 allows the other hosts to have
two logical subnets using one physical subnet.
The application requires the downstream network to be divided into multiple
subnets.
Figure 35 Secondary IP address Application on a Super SVI
Configuring Routed A routed port is a physical port that performs like a port on a router. It does not
Port Interface need to be connected to a router. Routed ports are not associated with a
particular VLAN, as is an untagged port. A routed port behaves like a regular
router interface.
To configure a routed port it must be set to layer 3 mode by using the "no
switchport" command. Next an IP address is assigned to the interface and the
port is enabled using the "no shutdown" command.
On the BBS 1000+ system, only uplink ports (GE3/1-4) can be configured as
routed ports.
Example of Configuring
a Routed Interface
The procedures to create and remove a Routed Interface are described below.
BBS1000+(config-t-if-ge-3/2)# no shutdown
GE: 3/2
Switchport: Enabled
Name: GE-10
MTU: 1500bytes
Speed: 1000Mbps
AdminStatus: Enable
Auto Negotiation: Enabled
Ingress vlan filter: Disabled
Flow Control receive: Enabled
Flow Control transmit: Enabled
Maximum receive frame: 1532
Link Status: Up
PVID: 1
Configuring Switch When packets communicate in L2, they can only be forwarded within the same
Virtual Interface (SVI) VLAN. In order for packets to be routed between different VLANs, L3
communication is required. BBS 1000+ uses SVI (Switched Virtual Interface) to
enable the BBS 1000+'s routing of packets between different VLANs.
By configuring a Switch Virtual Interface (SVI) one or more BBS 1000+ GE ports
can be configured in one VLAN. These GE ports become a virtual single
interface and can be assigned a single IP address to enable routing.
SVIs can be created by issuing the interface vlan command from the
configuration terminal command mode.
In the topology above, BBS 1000+ connects to the Internet via two ISPs. The
link between Uplink port GE3/1 and ISP1 is 1000M and always in working mode.
The link between Uplink port GE3/4 and ISP2 is 100M and is in backup mode.
When the 1000M link is down, the 100M link will take over. In this situation,
GE3/1 and GE3/4 must be configured as an SVI. The two GE ports are both
members of VLAN 500 and configured as a single L3 IP address.
Routed Interface (RI) are limited in that they can only be configured with one
interface, whereas with SVI multiple interfaces can be configured to extend the
GE port's interface range. For example in the topology above, uplink port GE3/1
is presently configured in SVI 1, but this port can be later added to another SVI if
needed.
Example of Configuring The network topology shown in Figure 36 above is used in this configuration
SVI example. A SVI is configured for BBS 1000+'s GE3/1 and GE3/4 ports, so that
L3 communication can be established between BBS 1000+ and an ISP.
Create a SVI
1 Create a VLAN and assign Gigabit-Ethernet port members to the VLAN.
telnet@BBS1000+(config-t)# vlan 500
telnet@BBS1000+(config-t-vlan-500)# exit
2 Create an SVI based on VLAN 500 and then display VLAN 500 information.
telnet@BBS1000+(config-t)# interface vlan 500
VLAN 500:
Name :
port(s) or group(s) :ge3/2,ge3/4
Tagged port(s) or group(s) :ge3/2,ge3/4
Untagged port(s) or group(s) :
Optionally, use the CLI command below to show all L3 interfaces. With this
command you can verify whether the SVI exists.
telnet@BBS1000+(config-t)# show ip interface brief
Configuring a Super In order for packets to be routed between different VLANs, L3 communication is
SVI required. BBS 1000+ uses Super SVI to enable routing of ONU packets
between different sub-VLANs. Sub-VLANs separate virtual broadcast domains
under Super SVI and share the same gateway. Therefore, Super SVI is an
aggregation technique for conserving IP address resources.
Super SVI is an L3 interface. First configure an SVI for one or more BBS 1000+
downlink GE ports. Then define the VLAN as a Super SVI. Last add ONU
VLANs as Super VLAN members.
Figure 37 Super SVI example
In the topology above, Super VLAN 600 has two sub-VLAN, one is VLAN 101
and the other is VLAN 133. The Super SVI's IP address (50.0.0.10/24) becomes
the gateway IP address of each of the CPE PCs. Downlink port GE1/1 and
ONU1 are members of VLAN 101. Downlink port GE1/2 and ONU2 are
members of VLAN 133. These two sub-VLANs separate virtual broadcast
domains under Super VLAN 600.
On the BBS 1000+ system, Super SVI can only be configured on the downlink
GE ports (GE1/1-4 and GE2/1-4).
GEPON OLT OLT BBS 1000+ Part Number L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
Configuring a Super SVI 133
Configuring a Super SVI The network topology shown in Figure 37 above is used in this configuration
Example example. A Super SVI interface is configured for BBS 1000+ GE1/1 and GE1/2,
so that L3 communication can be established between BBS 1000+ and the two
PCs.
Procedures to create and delete a Super SVI Interface are described below.
VLAN 600:
Name :
port(s) or group(s) :ge1/1-2
Tagged port(s) or group(s) :ge1/1-2
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-vlan-600)# exit
Creating Layer 3 Link Layer 3 link aggregation ports can be created based on an SVI port or routed
Aggregation port. This section describes both configurations.
Interfaces
The steps for creating an L3 Link Aggregation port based on a SVI port are
listed below.
1 Create a Layer 2 VLAN.
2 Configure a SVI type interface.
3 Assign an IP address to this interface.
4 Based on this SVI, configure a LAG routed interface.
The steps for creating an L3 Link Aggregation port based on a GE routed port
are listed below.
1 Configure a Gigabit-Ethernet routed port.
2 Based on this Gigabit-Ethernet routed port configure a LAG routed interface.
Example Topology
Figure 38 L3 Link Aggregation port based on an SVI port
As shown in Figure 38, BBS 1000+ uplink ports GE3/1 and GE3/4 form Link
Aggregation Group 1, and its IP address is 60.0.0.10/24. The Cisco switch ports
g1/0/5 and g1/0/6 form Channel-group 1, and its IP address is 60.0.0.1/24.
Configuration Tasks The general tasks involved in configuring Link Aggregation Groups for SVIs are
given below. After this task overview, detailed steps are described for each task,
using the topology example in Figure 38.
1 Configure Link Aggregation Group 1
2 Configure a SVI Interface
3 Create an Ethernet SVI VLAN 600 on the Cisco switch
4 Connection Testing
telnet@BBS1000+(config-t-vlan-600)# exit
telnet@BBS1000+(config-t)#
NOTE: All the static MAC address and ACL rules associated with
interface ge3/1,ge3/4 have been cleared.
telnet@BBS1000+(config-t-if-vlan-1000)# exit
3750(config-if)#channel-group 1 mode on
3750(config-if)#channel-group 1 mode on
3750(config-if)# no shutdown
4 Configure port-channel 1.
3750(config)#interface port-channel 1
Connection Testing
Run the ping command from BBS 1000+.
Removing all
configurations in this
example from BBS
1000+
telnet@BBS1000+(config-t-vlan-600)# exit
telnet@BBS1000+(config-t)#
Example Topology
Figure 39 L3 LAG interface based on a Routed interface
As shown in Figure 39, BBS 1000+ uplink ports GE3/1 and GE3/4 form Link
Aggregation Group 2, and its IP address is 70.0.0.10/24. The upstream Cisco
switch ports, g1/0/5 and g1/0/6, form channel-group 1, and its IP address is
70.0.0.1/24.
Configuration Tasks The general tasks involved in configuring Link Aggregation Groups (LAG) for
Routed Interfaces are given below. After this task overview, detailed steps are
described for each task, using the topology example in Figure 39.
1 Create and Configure Link Aggregation Group 2
2 Create two Routed Interfaces
3 Assign Link Aggregation Group 2 members
4 Create Routed Interfaces on the Cisco switch
5 Test the connection from BBS 1000+
2 Configure the LAG as an L3 link aggregation interface and assign its IP address.
telnet@BBS1000+(config-t-if-lg-2)# no switchport
telnet@BBS1000+(config-t-if-lg-2)# exit
telnet@BBS1000+(config-t-if-ge-3/1)# no switchport
telnet@BBS1000+(config-t-if-ge-3/1)# exit
telnet@BBS1000+(config-t-if-ge-3/4)# no switchport
telnet@BBS1000+(config-t-if-ge-3/4)# exit
telnet@BBS1000+(config-t)# exit
3750(config-if)#no switch
3750(config-if)# no switch
3750(config-if)# no shutdown
Deleting all
configurations from this
example on BBS 1000+
GE: 3/1
Switchport: Enabled
Name: GE-9
MTU: 1500bytes
Speed: 1000Mbps
AdminStatus: Disable
Auto Negotiation: Enabled
Ingress vlan filter: Disabled
Flow Control receive: Enabled
Flow Control transmit: Enabled
Maximum receive frame: 1532
Link Status: Down
PVID: 1
Configuring MAC BBS 1000+ maintains a MAC Address Table for packet forwarding. Each table
Address Table entry includes a MAC address, a VLAN ID and a port number. The L2 table entry
can be either populated by the BBS switch hardware or manually created.
The dynamic entry created by the system is aged out in a configurable MAC age
time, which by default is 300 seconds. Manually created entries remain in the
table until manually deleted.
In the following situation, MAC table entries should be manually specified for the
device. When a designated subscriber device with a particular MAC address is
only allowed access a specific BBS 1000+ port in a VLAN ID.
Example Topology
Figure 40 Static MAC Address Configuration Topology
Configuration Requirements
ONU1 is bound to lport 1 of OLT1/1 and can be registered on BBS 1000+.
ONU2 is bound to lport 1 of OLT1/4 and can be registered on BBS 1000+
BBS 1000+ system is running in Mix-tag mode and OLT1/1 as well as
OLT1/4 are running in Stack-tag mode.
The IP addresses of PC1 and PC2 have been configured.
Configuration Tasks The general tasks involved in configuring Static MAC Address Configuration are
given below. After this task overview, detailed steps are described for each task,
using the topology example in Figure 40.
1 'Verify BBS 1000+'s System Running Mode and PON port mode
2 Configure Service VLAN 50
3 Configure a Static MAC Address Entry
4 Verify the Configuration
Verify BBS 1000+'s System Running Mode and PON port mode
telnet@BBS1000+(config-t)# show system
describion :[ePON]
sysName :BBS1000+
Location :1275 Harbor Bay Parkway, Alameda, CA 94502,
Tel:1(510)864-8800
Contact :John Smith
Device Id :abcdefghijklmnopqrstuvwxyzabcd
Part Number L2 CO00 2321 06 15 00 GEPON OLT OLT BBS 1000+
June 2007 CLI Operation Guide
144 Chapter 5: Basic Configuration
VLAN 50:
Name :
port(s) or group(s) :ge1/1,ge1/4,ge3/1
Tagged port(s) or group(s) :
Untagged port(s) or group(s) :ge1/1,ge1/4,ge3/1
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu-vlan 1 50
-------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=5, LLID[0]=5
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU vlan id = 50
ONU mac address = 00:07:ba:34:bd:b1
User ID = onu_2
RTT TQ = 2
Framed IP Address = 0.0.0.0
Framed Netmask = 0.0.0.0
Laser_on_time = 4
Laser_off_time = 4
Mpcp Timeout = 4000
Multicast filtering = enable
P2p-access policing = disable
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.18
Bootloader version = 02.01.10
telnet@BBS1000+(config-t-if-olt-1/4)# onu-vlan 1 50
-------------------------------------------------------------
OLT = 1/4, Logical port = 1, ONU id=1, LLID[0]=1
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU vlan id = 50
ONU mac address = 00:07:ba:34:bd:d7
User ID = onu_12
RTT TQ = 0
Framed IP Address = 0.0.0.0
Framed Netmask = 0.0.0.0
Laser_on_time = 4
Part Number L2 CO00 2321 06 15 00 GEPON OLT OLT BBS 1000+
June 2007 CLI Operation Guide
146 Chapter 5: Basic Configuration
Laser_off_time = 4
Mpcp Timeout = 4000
Multicast filtering = enable
P2p-access policing = disable
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.20
Bootloader version = 02.01.10
telnet@BBS1000+(config-t-if-olt-1/4)#
Result Analyze
After configuring a static MAC table entry for PC1, PC1 only can access BBS
1000+ system via OLT1/1 in the VLAN 50.
telnet@BBS1000+(config-t-if-ge-3/1)# pvid 1
telnet@BBS1000+(config-t-if-ge-3/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-50)# no member
ge3/1,ge1/1,ge1/4
telnet@BBS1000+(config-t-vlan-50)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu-vlan 1 1
-------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=5, LLID[0]=5
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU vlan id = 1
ONU mac address = 00:07:ba:34:bd:b1
User ID = onu_2
RTT TQ = 2
Framed IP Address = 0.0.0.0
Framed Netmask = 0.0.0.0
Laser_on_time = 4
Laser_off_time = 4
Mpcp Timeout = 4000
Multicast filtering = enable
P2p-access policing = disable
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.18
Bootloader version = 02.01.10
BBS 1000+ uses an ARP table to maintain the mapping of IP addresses to MAC
addresses. The fields of the ARP table are IP address, MAC address and
Interface Number, etc. An ARP table entry can be either dynamic or static. The
dynamic entry is automatically generated by the system, and the static entry is
specified manually. BBS 1000+ uplink ports support both dynamic and static
methods of generating ARP entries, but the downlink ports only support the
static method.
BBS 1000+ uses a host-route table to maintain the mapping between host IP
addresses and Interfaces. Host-route table entries can be created statically or
dynamically.
The ARP command is used to manage ARP tables and the host-route
command is used to manage host-route tables.
BBS 1000+ complies with the following ARP protocols listed below:
Address Resolution Protocol (ARP) specified by RFC 826.
Manual ARP binding and proxy ARP specified in RFC 1027 to facilitate
routing among clients.
ARP Configuring
Commands
Example Topology
Figure 41 ARP Configuration Topology
Configuration Requirements
ONU1 is bound to lport 1 of OLT1/1 and can register on BBS 1000+. ONU2 is
bound to lport 2 of OLT1/1 and can register on BBS 1000+.
The BBS 1000+ is running in Mix-tag and OLT port 1/1 running in stack-tag
mode.
Vlan 101 has been already configured for ONU1 with GE1/1 as a tagged
member and vlan 102 has also been already configured for ONU2 with
GE1/1 as a tagged member(ONU1' vlan id is 101 and ONU2's vlan id is 102).
IP addresses of PC1 and PC2 have been configured.
VLAN 100:
Name :
port(s) or group(s) :ge1/1
Tagged port(s) or group(s) :ge1/1
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-vlan-100)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-vlan-100)#
2 Add an ARP entry for PC1 by issuing the following CLI command, where:
10.0.0.99 is the IP address of PC1
00:0b:db:0a:3f:78 is the MAC address of PC1
VLAN 100 is the Super VLAN on BBS 1000+
Sub-vlan 101 is a member of the Super VLAN (ONU's VLAN ID)
GE1/1 is the GE port that PC1 connects to via ONU1.
------------------+-----------------+--------+----------+----
10.0.0.99 00:0b:db:0a:3f:78 static Vlan101 -NA-
telnet@BBS1000+(config-t)#
4 After adding the ARP entry, PING the Super SVI's IP address from PC1.
c:\> ping 10.0.0.10
2 Add a host-route entry for PC2 by issuing the following CLI command, where:
10.0.0.100 is the IP address of PC2
VLAN 100 is the Super VLAN on the BBS 1000+
Sub-vlan 102 is a member of the Super VLAN (ONU's VLAN ID)
Since we added an ARP entry for PC1 in the pervious step, the system will
automatically generate a correlated static host-route entry.
Static(A) in the above display information means that this entry is statically
added via ARP command. Static(H) means this entry is statically added via
Host-route command.
4 After adding the Host-route entry, PING the Super SVI's IP address from PC2 to
verify the connection.
c:\> ping 10.0.0.10
------------------+-----------------+--------+----------+----
10.0.0.99 00:0b:db:0a:3f:78 static Vlan101 -NA-
10.0.0.100 00:0f:1f:a0:56:62 dynamic Vlan102 337
Since we previously added a host-route entry for PC2, the system automatically
generated a correlated dynamic ARP entry.
2 Delete the static ARP entry.
telnet@BBS1000+(config-t)# no arp 10.0.0.99
------------------+-----------------+--------+----------+----
10.0.0.100 00:0f:1f:a0:56:62 dynamic Vlan102 337
The dynamic ARP entry can be deleted manually otherwise it will be aged out
automatically. The ARP entry aging time is the same as the MAC address aging
time. This aging time is configurable; the default value is 300 seconds.
3 Delete the dynamic ARP entry.
telnet@BBS1000+(config-t)# arp-flush interface vlan 100
telnet@BBS1000+ (config-t)#
If the Super SVI is deleted first, the ARP and host-route tables will be
cleared by system automatically.
A default route can be configured for use when a matching routing table entry
does not exist. If a default route is not specified and the packet does not have a
matching route table entry, the packet will be discarded. In this situation an
ICMP packet is returned to the original host to report the error.
Metric
When there are two route entries between the equipment, use the metric
parameter to set the default route. The possible values are 1-255, with the
lowest number having the highest priority.
Figure 42 Metric Example
In the figure above, there are two routes between BBS 1000+ and subnet
4.4.4.0/24. The routing entries are specified as shown below:
IP Route Configuring
Commands
Table 16 Typical IP Route configuration commands
Example Topology
Figure 43 IP Route Topology
There are two links between BBS 1000+ and the Cisco switch. Link1 is from
BBS 1000+ uplink port GE3/2 to Cisco switch port g1/0/7; Link2 is from uplink
port GE3/3 to g1/0/8. The Cisco switch connects to the server via g1/0/6.
telnet@BBS1000+(config-t-if-ge-3/2)# no switchport
telnet@BBS1000+(config-t-if-ge-3/2)# no shutdown
telnet@BBS1000+(config-t-if-ge-3/2)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-ge-3/3)# no switchport
telnet@BBS1000+(config-t-if-ge-3/3)# no shutdown
telnet@BBS1000+(config-t-if-ge-3/3)# exit
telnet@BBS1000+(config-t)#
Password:******
3750#configure terminal
Enter the following configuration commands, one per line. End by pressing
CTRL+Z.
3750(config-if)#no switchport
3750(config-if)#no shutdown
3750(config-if)#exit
3750(config)#exit
3750#
3750(config-if)#no switchport
3750(config-if)#no shutdown
3750(config-if)#exit
3750(config)#
3750(config-if)#no switchport
3750(config-if)#no shutdown
3750(config-if)#exit
3750(config)#
Server Configuration
1 On the Cisco switch add an ARP table entry for the server.
Use the following CLI command to add the ARP entry, where:
4.4.4.10 is the server IP address.
00:0f:1f:a0:56:62 is the server MAC address.
telnet@BBS1000+(config-t-if-ge-3/2)# shutdown
The successful Ping result indicates that BBS 1000+ used the static IP route to
forward packets.
Verify the default IP Route configuration
Disable Link2, and then run a ping command from BBS 1000+ to the server IP
address.
telnet@BBS1000+(config-t-if-ge-3/3)# shutdown
The successful Ping result indicates that BBS 1000+ used the default IP route to
forward packets.
telnet@BBS1000+(config-t-if-ge-3/2)# no switchport
telnet@BBS1000+(config-t-if-ge-3/2)# exit
telnet@BBS1000+(config-t-if-ge-3/3)# no switchport
telnet@BBS1000+(config-t-if-ge-3/3)# exit
Configuring Port You can monitor traffic on GEPON BBS 1000+ ports by configuring another port
Mirror to "mirror" the traffic on the ports to be monitored. By attaching a protocol
analyzer to the mirror port, you can observe the traffic on the monitored ports.
Restrictions on
Monitoring Sessions
Port Mirror Configuring The following steps describe how to set up a monitor session:
Procedures
1 Configure the monitor session source.
2 Configure the monitor session destination.
3 Verify the monitor session.
4 Activate the monitor session.
5 If required another monitor session can be set up. This session is stored in the
buffer for future activation.
6 Verify the monitor session.
Example Topology
Figure 44 Port Mirror Topology
Configuration Requirements
1 ONU is bound to lport 5 on OLT1/1 and can successfully register on BBS 1000+.
2 The VLAN BASE ID is 101 (the default).
3 PC1 and PC2's IP addresses are already configured.
In this example, assum GE1/1 has already been a tagged member of vlan
105
2 Display the VLAN information.
telnet@BBS1000+(config-t-vlan-105)# show vlan 105
VLAN 105:
Name :PON 5
port(s) or group(s) :ge1/1,ge3/1
Tagged port(s) or group(s) :ge1/1
Untagged port(s) or group(s) :ge3/1
GEPON OLT OLT BBS 1000+ Part Number L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
Configuring Port Mirror 165
GE: 3/1
Switchport: Enabled
Name: GE-9
MTU: 1500bytes
Speed: 1000Mbps
AdminStatus: Enable
Auto Negotiation: Enabled
Ingress vlan filter: Disabled
Flow Control receive: Enabled
Flow Control transmit: Enabled
Maximum receive frame: 1532
Link Status: Up
PVID: 105
telnet@BBS1000+(config-t)#
Session 1
-----------
Source receive interfaces :
Source transmit interfaces :
Destination interfaces :
buffered Session 1
---------------------
Source receive interfaces :ge3/1
Source transmit interfaces :ge3/1
Destination interfaces :
Session 1
-----------
Source receive interfaces :
Source transmit interfaces :
Destination interfaces :
buffered Session 1
---------------------
Source receive interfaces :ge3/1
Source transmit interfaces :ge3/1
Destination interfaces :ge3/3
Session 1
-----------
Source receive interfaces :ge3/1
Source transmit interfaces :ge3/1
Destination interfaces :ge3/3
buffered Session 1
---------------------
Source receive interfaces :
Source transmit interfaces :
Destination interfaces :
telnet@BBS1000+(config-t)#
From PC2:
c:\> ping 10.0.0.10
Check the protocol analyzer connected to the mirror port to verify the source
port condition.
Session 1
-----------
Source receive interfaces :
GEPON OLT OLT BBS 1000+ Part Number L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
Configuring Port Mirror 167
Session 1
-----------
Source receive interfaces :
Source transmit interfaces :
Destination interfaces :
buffered Session 1
---------------------
Source receive interfaces :
Source transmit interfaces :
Destination interfaces :
BBS1000+(config-t)#
VLAN Introduction GEPON BBS 1000+ supports up to 4094 VLAN IDs (1 to 4094)
For example in VLAN Management, the GE1/1 port PVID is 10, therefore when
removing GE1/1 from VLAN 10, the GE1/1 port PVID will be changed to 1 (the
default VLAN ID).
Figure 45 VLAN Management
4 VLAN 1 is the default VLAN for each L2 port, (GE1/1-4, GE2/1-4, GE3/1-4) and
cannot be removed or configured.
Any L2 port can be an untagged member of many different VLANs. But this
configuration can cause packet forwarding problems, therefore it is not
recommended.
VLAN ID Processing in VLAN IDs are processed by both the BBS 1000+ and ONU. Internal BBS 1000+
Unique-tag/Stack-tag packets are always tagged. Any incoming untagged packets are tagged first at
Mode the ingress port before they are processed by BBS 1000+.
If the VLAN IDs match, the ONU strips the VLAN ID from the packet and
forwards it downstream.
If the VLAN IDs do not match, the ONU discards the tagged packet
downstream.
When a downstream untagged packet from the OLT is received by the ONU,
the ONU discard the packet downstream.
If an egress port is a tagged member of a VLAN, the packet exits this port
with its original VLAN tag.
If an egress port is a untagged member of a VLAN, the packet exits this port
with its VLAN tag stripped.
After the lport is assigned, each ONU is assigned to a unique VLAN. A unique
VLAN ID is assigned based on the VLAN ID base, which by default is 101.
There are either 4 or 8 OLT ports on the BBS 1000+ depending on the
configuration. Each OLT port is connection to each downlink GE port. Each
downlink GE port can support up to 64 ONUs, thus there are 64 default VLANs
for each downlink GE port. The first downlink GE port can assign VLAN IDs
between 101 and 164, the ONU get its VLAN ID based on the formula below:
Where:
Valid VLAN IDs are 1 to 4094 with the exception of 1006 to 1261 (inclusive)
which are reserved. The valid values for the configurable VLAN_ID_base can be
between 2 and 494 and between 1262 and 3583
The following example is to modify the ONU VLAN ID under stack-tag running
mode.
telnet@BBS1000+(config-t-if-olt-1/1)# onu-vlan 1 10
telnet@BBS1000+(config-t-if-olt-1/1)# exit
-------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=1, LLID[0]=1
Name = ONU-1
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU vlan id = 10
ONU mac address = 00:07:ba:34:bd:e7
User ID = onu_1
RTT TQ = 0
Framed IP Address = 0.0.0.0
Framed Netmask = 0.0.0.0
Laser_on_time = 4
Laser_off_time = 4
Mpcp Timeout = 4000
Multicast filtering = enable
P2p-access policing = disable
P2p-access port_number = 63
P2p-access port bitmap[1-32][33-64]:[0xffffffff][0xffffffff]
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.20
Bootloader version = 02.01.10
telnet@BBS1000+(config-t-if-olt-1/1)#
Part Number L2 CO00 2321 06 15 00 GEPON OLT OLT BBS 1000+
June 2007 CLI Operation Guide
174 Chapter 6: VLAN Management
When user enters onu-vlan CLI command in the Unique-tag running mode, an
error message will be displayed on the screen.
VLAN Layer 2
Configuration Tasks
VLAN Layer 2 The typical steps for creating a VLAN are listed below:
Management
Procedure
1 Create an empty VLAN by specifying the VLAN ID (value from 1 to 4094 with the
exception of 1006 to 1261 (inclusive) which are reserved), and optionally assign
it a VLAN name.
VLAN Creation
Example
Application Description The PC is connected BBS 1000+ uplink port GE3/1 and the Switch is connected
to BBS 1000+ uplink port GE3/2. Both GE3/1 and GE3/2 are assigned to VLAN
100, which is a data VLAN.
Configuration Requirements
BBS 1000+ is running in stack-tag mode .
BBS1000+(config-t)#
BBS1000+(config-t-vlan-100)#
Part Number L2 CO00 2321 06 15 00 GEPON OLT OLT BBS 1000+
June 2007 CLI Operation Guide
176 Chapter 6: VLAN Management
VLAN 100:
Name :vlan-100
port(s) or group(s) :ge1/1,ge3/1
Tagged port(s) or group(s) :ge1/1
Untagged port(s) or group(s) :ge3/1
BBS1000+(config-t-vlan-100)#
GE: 3/1
Switchport: Enabled
Name: GE-9
MTU: 1500bytes
Speed: 1000Mbps
AdminStatus: Enable
Auto Negotiation: Enabled
Ingress vlan filter: Disabled
Flow Control receive: Enabled
Flow Control transmit: Enabled
Maximum receive frame: 1532
Link Status: Down
PVID: 100
VLAN 100:
Name :vlan-100
port(s) or group(s) :ge1/1,ge3/1
Tagged port(s) or group(s) :ge1/1
Untagged port(s) or group(s) :ge3/1
BBS1000+(config-t-vlan-100)#
GE: 3/1
Switchport: Enabled
Name: GE-9
MTU: 1500bytes
Speed: 1000Mbps
AdminStatus: Enable
Auto Negotiation: Enabled
Ingress vlan filter: Disabled
Flow Control receive: Enabled
Flow Control transmit: Enabled
Maximum receive frame: 1532
Link Status: Down
PVID: 100
telnet@BBS1000+(config-t-if-ge-3/1)# pvid 1
telnet@BBS1000+(config-t-if-ge-3/1)# exit
telnet@BBS1000+(config-t)#
BBS1000+(config-t-vlan-100)#
VLAN 100:
Name :vlan-100
port(s) or group(s) :
Tagged port(s) or group(s) :
BBS1000+(config-t-vlan-100)#
Delete a VLAN
After you remove member ports from the VLAN, then the VLAN can be deleted.
Any VLAN without current members can be deleted, with the exception of VLAN
1which is the default VLAN for all ports.
BBS1000+(config-t)#
4 Display all VLAN information to confirm that the VLAN was removed.
BBS1000+(config-t)# show vlan
PON System
Configuration
PON System Parameters The PON system configurations include the following parameters:
To check the PON system configuration, use the following CLI command:(In
Unique-tag running mode)
User Authentication There are two types of BBS 1000+ users: CLI and ONU. Each of them can be
Method authenticated locally or remotely.
Authentication
Configuring Commands
Configuring ONU's Before configuring BBS 1000+ ONU's local authentication, the following
Local Authentication concepts should be noted:
1 ONU Lport (Logical Port) Assignment
2 ONU Registration Process
3 VLAN ID Assignment in Unique-tag running mode
ONU Lport (Logical Port) Each of the BBS 1000+'s downlink ports, referred to hereafter as PON ports,
Assignment can connect with up to 64 ONUs. Since these 64 ONUs are connected to the
same physical PON port, the individual ONUs are assigned to one of the PON
port's 64 logical ports (lports). For assigning ONU and PON port connections,
the BBS 1000+ system uses a binding table. The table sets a mapping
relationship between ONU MAC addresses and individual lports. The binding
table is user defined, enabling the lports to be assigned statically.
ONU Registration By default, Logical Port (lport) to MAC address binding is enabled.
Process
When an ONU is connected to the BBS 1000+ and powered on, it goes through
the following registration process:
1 The OLT assigns the ONU a Logical Link ID (LLID).
2 The pre-configured lport number is obtained from the binding table.
3 This lport number is assigned to the ONU.
4 The VLAN ID and other attributes are assigned to the ONU.
For a list of other attributes assigned in step 4 above, refer to Return List on the
Radius Server on page 248.
VLAN ID Assignment in Each downlink GE port (GE1/1-4, GE2/1-4) is assigned 64 tagged VLANs.
Unique-tag running When an ONU is registered, it is also assigned as a member of one of these 64
mode VLANs. The VLANs assigned to each downlink GE port are listed in Table 23.
Table 23 VLAN ID Assignment (Based on a VLAN ID Base of 101)
After the lport is assigned, each ONU is assigned to a unique VLAN. A unique
VLAN ID is assigned based on the VLAN ID base, which by default is 101.
There are either 4 or 8 OLT ports on the BBS 1000+ depending on the
configuration. Each OLT port is connected to a separate downlink GE port. Each
downlink GE port can support up to 64 ONUs, thus there are 64 default VLANs
for each downlink GE port. The first downlink GE port can assign VLAN IDs
between 101 and 164, the ONU get its VLAN ID based on the following formula:
Where:
The VLAN ID base is configurable (default is 101). Possible Value: 2-494 and
1262-3583
Valid VLAN IDs are 1 to 4094 with the exception of 1006 to 1261 (inclusive)
which are reserved. The valid values for the VLAN ID base can be between 2
and 494 and between 1262 and 3583.
VLAN ID Assignment in Either all downlink GE ports (GE1/1-4, GE2/1-4) or all uplink GE ports(GE3/1-4)
Stack-tag running mode are the untagged members of default vlan 1.
Example Topology
Figure 47 Local ONU Authentication
As shown in Figure 47, BBS 1000+'s downstream OLT1/1 port connects with
ONU1 and ONU2 through a splitter. In this example, BBS 1000+'s local
authentication's lport binding function is enabled and the VLAN ID Base is set to
10.
Configuration Tasks The general tasks involved in configuring local ONU authenticatin are given
below. After this task overview, detailed steps are described for each task, using
the topology example in Figure 47.
1 Configure PON System Parameters
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
184 Chapter 7: Configuring GEPON Features
success
ONU's lport number can be derived from the planned VLAN ID. In this example,
ONU1 is in VLAN 10 therefore its logical port will be lport1 of GE1/1, and ONU2
planned VLAN ID is 15, so its logical port will be lport6 of GE1/1.
1 Enter the Configuration Terminal command mode.
telnet@BBS1000+>enable
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)#
3 Since ONU1 is assigned lport 1, enter the OLT lport 1 configuration command
mode.
In the following command "onu 1" is the same as OLT 1/1's lport 1. To assign the
ONU lport 5, the command would be "onu 5".
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)#
4 Now from inside lport 1's configuration command mode, bind ONU1's MAC
address with this lport (lport 1).
The ONU's MAC address can be found on a label on the ONU's bottom cover.
telnet@BBS1000+(config-if-onu-1/1/1)#
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu 6
telnet@BBS1000+(config-if-onu-1/1/6)#
7 Return to the Configuration Terminal mode by entering the exit command twice.
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
186 Chapter 7: Configuring GEPON Features
telnet@BBS1000+(config-if-onu-1/1/6)# exit
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)#
2 The OLT port is in the shutdown state by default, enter the following command
to activate the OLT port..
telnet@BBS1000+(config-t-if-olt-1/1)# no shutdown
telnet@BBS1000+(config-t-if-olt-1/1)#
Upon the OLT port activation, the connected ONU will be registered
automatically and the lport is bound to the ONU's MAC address.
3 Return to the Configuration Terminal command mode.
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
-------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=1, LLID[0]=1
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU mac address = 00:07:ba:34:af:36
User ID =
RTT TQ = 2
Laser_on_time = 4
Laser_off_time = 4
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.19.00
Bootloader version = 02.01.10.00
-------------------------------------------------------------
OLT = 1/1, Logical port = 6, ONU id=2, LLID[0]=2
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU mac address = 00:07:ba:35:a2:e0
User ID =
RTT TQ = 4
Laser_on_time = 4
Laser_off_time = 4
Hardware type = ONU100
Hardware version = 0
success
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)# exit
telnet@BBS1000+(config-t-if-olt-1/1)# onu 6
OLT Management
The shutdown command deactivates the port and sets the port's Administrative
Status to Disabled. The no shutdown command activates the port and sets the
port's Administrative Status to Enabled.
Transceiver Type
There are five type of transceivers:FIBERXON, INFINEON, SFP, ZENO, ZONU.
Currently only FIBERXON is supported.
Use CLI command "show interface epon-olt brief" to check the transceiver type.
Reseting OLT Under certain situations, abnormal behavior may occur on the OLT ports as
listed below:
1 Packet loss at OLT ports
2 The ONU MAC addresses in the PON system's MAC Address Table are not
consistent with the actual ONU MAC addresses.
When these conditions occur, the user needs to reset the OLT port. The GEPON
system currently provides two methods for resetting the OLT port:
Automatically using the Monitoring Method
Manual Reset Method
Monitoring Method
At the DEBUG configuration level, two CLI commands provide automatic
abnormality monitoring: olt-pause-frames-monitoring and
olt-mismatch-monitoring. When this type of abnormality occurs, the system
will reset the corresponding OLT port.
By default olt-pause-frames-monitoring is Enabled. When the number of
PON port pause-frames received, reaches a threshold during a certain
period, the system will reset this PON port.
By default olt-mismatch-monitoring is Enabled. When the PON system's
MAC address table is not consistent with the actual ONU MAC addresses,
the system will reset the port.
Example:
Disable the both of these monitoring methods from the DEBUG command
mode.
1 Enter Debug command mode.
BBS1000+# debug
telnet@BBS1000+(debug)#
The CLI command ltm-reset can be used to reset the LTM module as shown in
the example below.
1 Check the BBS 1000+'s 8051 chip status to verify that the LTM module is
installed properly in the BBS 1000+ system.
telnet@BBS1000+(config-t)# show 8051
1 Check the BBS 1000+'s 8051chip status to verify that the LTM module is
installed properly in the BBS 1000+ system.
telnet@BBS1000+(config-t)# show 8051
telnet@BBS1000+(config-t-if-olt-1/1)#
OAM rate limit After enabling OAM rate limit, those OAM communication rate will be limited by
BBS 1000+ system. By default, the oam rate limit is disabled.
telnet@BBS1000+(config-t-if-olt-1/2)#
BBS1000+(config-t-if-olt-2/1)#
BBS1000+(config-if-olt-2/1)#
Disable OLT
BBS1000+(config)# interface epon-olt 2/1
BBS1000+(config-if-olt-2/1)# shutdown
BBS1000+(config-if-olt-2/1)#
----------------------------------------------------------------------
-------------------------------------------------------
OLT = 1/1
Report Frames:
Tx OK .......................... = 48441045
Rx OK .......................... = 48392890
Gate Frames:
Tx OK .......................... = 48524517
Rx OK .......................... = 49121469
Sys Frames:
Tx OK .......................... = 6217278
Rx OK .......................... = 62092
Rx Err ......................... = 0
Sys Octets:
Tx OK .......................... = 472514116
Rx OK .......................... = 4470644
Rx PHY Err ......................... = 0
PON Octets:
Tx OK .......................... = 3496184656
Rx OK .......................... = 3938486824
PON Frames:
Total Tx Dropped ............... = 0
Total Rx Dropped ............... = 68
Rx FCS Error ................... = 0
Rx Multicast ................... = 54659342
Tx Multicast ................... = 48477372
Rx Broadcast ................... = 0
Tx Broadcast ................... = 0
-------------------------------------------------------
OLT = 1/2
Report Frames:
Tx OK .......................... = 0
Rx OK .......................... = 0
Gate Frames:
Tx OK .......................... = 0
Rx OK .......................... = 0
Sys Frames:
Tx OK .......................... = 0
Rx OK .......................... = 0
Rx Err ......................... = 0
Sys Octets:
Tx OK .......................... = 0
Rx OK .......................... = 0
Rx PHY Err ......................... = 0
PON Octets:
Tx OK .......................... = 0
Rx OK .......................... = 0
PON Frames:
Total Tx Dropped ............... = 0
Total Rx Dropped ............... = 0
Rx FCS Error ................... = 0
Rx Multicast ................... = 0
Tx Multicast ................... = 0
Rx Broadcast ................... = 0
Tx Broadcast ................... = 0
-------------------------------------------------------
.. screen output truncated...
OLT&ONU DBA
Configuration
MPCP Introduction BBS 1000 uses the Multi-Point Control Protocol (MPCP), as defined in IEEE
802.3ah, to perform ONU Auto-Discovery, Registration, Bandwidth Allocation,
Round Trip Time (RTT) calculation, and OAM functions. MPCP messages are
passed back and forth between the OLT and ONUs to implement these
operations. The main MPCP messages are described below.
GATE message: The OLT sends Gate messages to the ONUs to assign
transmission time slots for both ONU discovery and normal data transmission.
The ONUs then use these assigned time slots for transmitting data packets.
REPORT message: The ONUs sends Report messages to inform the OLT of
ONU status, such as bandwidth requirements and traffic congestion conditions.
The Report messages help the OLT make intelligent bandwidth allocation
decisions.
1 Once the ONU discovery process is completed, the OLT assigns the ONU a
specific transmission timeslot via a GATE message.
2 Before the ONU's timeslot arrives, the ONU buffers data waiting to be
transmitted
3 During the ONU's timeslot, the ONU transmits a REPORT message and Data
to be forwarded
4 After receiving REPORT messages and Data from all the ONUs in the queue,
the process starts over with the OLT sending out a GATE message
MPCP Timeout There are two MPCP Timeout parameters, one for the OLT and the other for the
ONU. Both Timeout parameters are described below:
For example, during the ONU automatic discovery and registration process, the
OLT waits for a specified timeout period after sending a GATE message for the
ONU to respond with a REGISTER_REQ message.
The OLT MPCP Timeout range is 200-5000ms. The default value is 1000ms.
The CLI command for displaying the MPCP Timeout value is shown below.
For example, during the ONU automatic discovery and registration process, the
ONU waits for a specified timeout period after sending a REGISTER_REQ
message for the OLT to respond with a REGISTER message.
The ONU MPCP Timeout range is 200-5000ms. The default value is 4000ms.
The CLI MPCP Timeout configuration commands are listed below.
Dynamic Bandwidth Dynamic Bandwidth Allocation (DBA) is essential for an efficient GEPON
Allocation Introduction network. This is the only mechanism that allows for performance of
over-subscription on the PON, and is a key requirement for provisioning in
business and residential deployments.
To discover new ONU, OLT sends discovery gate periodically to the ONUs.
Within this window ONU can send register request to OLT and wait to get grant.
The frequency of how often the discovery gate should be sent can be configured
for each OLT port at the start of DBA algorithm. User can also configure the size
of the discovery gate and the grant cycle.
After modifying discovery size, discovery frequency, and grant cycle; user
should shutdown the OLT port and no shutdown the OLT port in order to take
these changes effect.
Configuring OLT DBA When allocating upstream dynamic bandwidth, BBS 1000+ supports two DBA
algorithms: Internal and Plato. The main differences between these two
algorithms are listed below:
1 The minimum bandwidth precision for Plato is 64kbit, which is less than
algorithm Internal's 1Mbit minimum bandwidth precision. Here precision means
the minimum bandwidth unit that can be assigned to end customers.
2 When Plato algorithm is used by one port of OLT, if no data is transmitted from
one connected ONU, this ONU's assigned committed bandwidth will be
reassigned to other ONUs. For algorithm Internal, it will always reserve the
committed bandwidtch to each ONU.
NoteA higher value will result in better Bandwidth utilization but will also
increase the time from power up that will take for an ONU to be registered.
Cycle Size During data transmission process, the cycle's size used to transmit data by 16384..131072TQ
all ONUs connected to that OLT.
Default Value: 65536
Changing DBA
algorithm From Plato to
Internal on OLT1/1
telnet@BBS1000+(config-t-if-olt-1/1)# no shutdown
Configuring ONU ONU SLA is to configure ONU's service level agreements for dynamic
DBA-SLA bandwidth algorithm.
class
Class parameters are only used in algorithm Plato.
Class is divided into 8 levels. Numbers 0-7 are used to label them from lower
to higher priority.
The ONU with the highest priority will first get the maximum bandwidth.
Lport binding
Please refer to Configuring ONU's Local Authentication ONU's Local
Authentication on page 181
MAC-limit
Please refer to PON System MAC Address Table on page 236.
BBS1000+(config-if-onu-2/4/1)# show in epon-olt 2/4 onu 1 dba-sla
ONU DBA-SLA
Configuration
Commands
Table 28 ONU DBA_SLA Configuring Commangs
Example Topology
Figure 50 OLT&ONU DBA Configuration
As shown in Figure 50, Through ONU1 and ONU2 respectively, Internet Cafe
and Phone Bar connect BBS 1000+ downlink port OLT2/4. According to actual
requirement, configure the DBA parameters shown in Table 29:
Table 29 DBA Parameters Configuration
Configuration Tasks The general tasks involved in configuring OLT&ONU DBA are given below.
After this task overview, detailed steps are described for each task, using the
topology example in Figure 50.
1 Configure OLT DBA
2 Configure ONU2 DBA-SLA
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-t-if-olt-1/1)# onu 2
telnet@BBS1000+(config-if-onu-1/1/2)# shutdown
telnet@BBS1000+(config-if-onu-1/1/2)# no shutdown
Result Analyze
Through the above configuration, when there is upstream data transmission for
the Caf bar and Phone bar, the data will follow the rules:
The maximum upstream bandwidth for the Internet Caf bar connected to
ONU1 is 50M and the guaranteed upstream bandwidth is 10M. The data
from Internet Caf bar has a relatively low priority. The priority is 0.
The maximum upstream bandwidth for the Phone bar connected to ONU2 is
1.5M and the guaranteed upstream bandwidth is 1M. The data from Phone
bar has the highest priority. The priority is 7.
When data traffic happens at BBS 1000+'s port OLT1/1, the data from Phone
Bar will pass through first.
telnet@BBS1000+(config-if-onu-1/1/2)# shutdown
telnet@BBS1000+(config-if-onu-1/1/2)# no shutdown
(Kbps) (Kbps)
----------------------------------------------------------------------------
ONU Policy
Configuration
ONU Policy Introduction To realize the dynamic bandwidth assignment (DBA) between ONUs, the same
PON port of BBS 1000+ system supports two policies:
Downstream Policy
Downstream policy is to control the downstream's bandwidth assignment
from BBS 1000+ OLT port to ONUs.
p2p-Stream Policy
p2p-Stream policy is to control the bandwidth assignment between
ONUs.When ONU is in p2p-access mode, this ONU can communicate with
other ONUs.
p2p-streamDBA is closely related to ONU's DBA-SLA configuration. For detailed
information please refer to Result Analyze of Configuration Tasksation Tasks on
page 215
ONU Downstream User can configure ONU's downstream bandwidth. Downstream bandwidth
Configuring includes the following parameters:
The priority of downstream forwarding
They are high-priority-frames and short-frames. The defaults for both of them
are Enable.
Maximum-bandwidth
The maximum bandwidth is allowed for downstream.
Maximum-bandwidthhas two units to choose: Kbps and Mbps.
The configurable range is 0..1000Mbps and 0..1000000kbps.
The default for 10000000Kbps.
Max-burst-size
When traffic jam happens, the system will control the flow through Toke. The
bucket's buffer size is max-burst-size. That is , when there is traffic jam,
system will guarantee that max-burst-size data will not get lost.
The value range for max-burst-size is 0-8192Kbytes. The default
max-burst-size is 256Kbytes.
To activate the downstream bandwidth parameters' configurations, ONU
downstream bandwidth policing must be enabled. The default value for
this policy is disable.
Use CLI command downstream bandwidth policing to activate ONU's
downstream bandwidth configuration.
User can use similar command as the following to check ONU's downstrem
bandwidth parameters' configuration.
telnet@BBS1000+(config-if-onu-1/1/1)# show interface epon-olt 1/1 onu
downstream-bandwidth
For the ONU under p2p-access mode, user can control the data communication
between them with p2p-stream policy.
P2P-stream Policy
By default, ONU's p2p mode is disabled. Through CLI command p2p-access
policing [onulist] to activate ONU's p2p mode.
Under p2p-access mode, user can configure the following ONU p2p-stream
bandwidth parametres:
Maximum-bandwidth
The maximum bandwidth can be allowed between two
ONUs.Maximum-bandwidth has two units to choose: Kbps and Mbps. For
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
208 Chapter 7: Configuring GEPON Features
different OLT types, there are two different value range to configure
maximum-bandwidth parameter.
For M4 OLT, the configurable range is 0..500Mbps and 0..500000kbps.
The default is 100000Kbps.
For M3 OLT, the configurable range is 0..1000Mbps and 0..1000000Kbps.
The default is 1000Kbps.
Using CLI command show inter epon-olt brief to distingush the OLT type.
Max-burst-size
When traffic jam happens, the system will control the flow through Toke. The
bucket's buffer size is max-burst-size. That is, when there is traffic jam,
system will guarantee that max-burst-size data will not get lost.
The value range for max-burst-size is 0-8192Kbytes. The default
max-burst-size is 256Kbytes.
To activate the p2p-stream bandwidth parameters' configurations, ONU
p2p-stream bandwidth policing must be enabled. The default value for this
policy is disable.
Use CLI command p2p-stream bandwidth policing to activate ONU's
p2p-stream bandwidth configuration.
User can use similar command as the following to check ONU's p2p bandwit
parameters' configuration.
telnet@BBS1000+(config-if-onu-1/1/1)# show interface epon-olt 1/1 onu p2p-bandwidth
ONU Policy
Configuration
Commands
Example Topology
Figure 53 ONU Downstream Policy Configuration
The Internet Cafe is connected to BBS 1000+ downlink port OLT1/1 via ONU1
and the Phone barisconnected to BBS 1000+ downlink port OLT1/1 via ONU2.
According to specific requirement, the Downstream Bandwidthparameters
shown in Table 31 can be configured:
Configuration Tasks The general tasks involved in configuring ONU downstream bandwidth policy
are given below. After this task overview, detailed steps are described for each
task, using the topology example in Figure 53.
1 Configure ONU1's downstream bandwidth
2 Configure ONU2's downstream bandwidth
Password:******
telnet@BBS1000+> enable
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)#
OLT LPort
maximum maximum policing-enable high-priority-frames short-frames
bandwidth burst-size 0-DISABLE 0-DISABLE 0-DISABLE
(Kbps) (Kbytes) 1-ENABLE 1-ENABLE 1-ENABLE
------------------------------------------------------------------------------------
1/1 1 100000 256 1 1 1
telnet@BBS1000+(config-t-if-olt-1/1)# onu 2
telnet@BBS1000+(config-if-onu-1/1/2)# downstream
maximum-bandwidth 1512 kbps
OLT LPort
maximum maximum policing-enable high-priority-frames short-frames
bandwidth burst-size 0-DISABLE 0-DISABLE 0-DISABLE
(Kbps) (Kbytes) 1-ENABLE 1-ENABLE 1-ENABLE
------------------------------------------------------------------------------------
1/1 2 1512 256 0 1 1
telnet@BBS1000+(config-if-onu-1/1/2)#
Result Analyze
Through the above configuration, when there is downstream data to the Internet
Caf and the Phone Bar, the following bandwidth assignment policies will
apply:igured. c requirement, the nd the Phone bar
The maximum downstream bandwidth for the Internet Caf is 100M.
The maximum downstream bandwidth for the Phone Bar is 1.5M.
When downstream data traffic jam happens, the data with higher priority and
shorter frame will pass through first.
OLT LPort
maximum maximum policing-enable high-priority-frames short-frames
bandwidth burst-size 0-DISABLE 0-DISABLE 0-DISABLE
(Kbps) (Kbytes) 1-ENABLE 1-ENABLE 1-ENABLE
------------------------------------------------------------------------------------
1/1 2 1000000 256 0 1 1
Example Topology
Figure 54 P2P Stream Policy Configuration
Configuration Tasks The general tasks involved in configuring ONU p2pstream bandwidth policy are
given below. After this task overview, detailed steps are described for each task,
using the topology example in Figure 54.
1 Configure ONU1's work mode as p2p-access
2 Configure ONU2's p2p-stream bandwidth
3 Configure ONU3's p2p-stream bandwidth
4 Display ONU1's DBA-SLA Configuration
5 Configure ONU1's DBA-SLA
Password:******
telnet@BBS1000+> enable
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)#
-------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=5, LLID[0]=5
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU vlan id = 101
ONU mac address = 00:07:ba:34:bd:b1
User ID = onu_2
RTT TQ = 0
Framed IP Address = 0.0.0.0
Framed Netmask = 0.0.0.0
Laser_on_time = 4
Laser_off_time = 4
Mpcp Timeout = 4000
Multicast filtering = enable
P2p-access policing = enable
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.20.00
Bootloader version = 02.01.10.00
telnet@BBS1000+(config-t-if-olt-1/1)# onu 2
telnet@BBS1000+(config-if-onu-1/1/2)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu 3
telnet@BBS1000+(config-if-onu-1/1/3)#
OLT LPort
maximum maximum policing-enable high-priority-frames short-frames
bandwidth burst-size 0-DISABLE 0-DISABLE 0-DISABLE
(Kbps) (Kbytes) 1-ENABLE 1-ENABLE 1-ENABLE
------------------------------------------------------------------------------------
1/1 3 2000 256 1 1 1
telnet@BBS1000+(config-if-onu-1/1/3)#
telnet@BBS1000+(config-if-onu-1/1/1)# reset
Result Analyze On the topology map, ONU1 is in p2p-access Mode. The data is transmitted
from ONU1 to uplink port GE3/2, ONU2 and ONU3. According to the total data
transmitting rate and the DBA-SLA Max. Bandwidth configuration, there are four
cases:
1 The total transmitting data from ONU1 is 15M. And ONU1's DBA-SLA Max
bandwidth is 20M.The total transmitting data from ONU1 is less than ONU1's
upstream bandwidth valueDBA-SLA bandwidth.
2 The total transmitting data from ONU1 to ONU2 and ONU3 is 5M, And ONU1's
p2p-stream Max. bandwidth is 8M. The total transmitting data from ONU1 to
other ONUs is less than ONU1's p2p-stream bandwidth valueMax. Bandwidth.
Therefore, under this case, all data will be transmitted normally
Case2: Transmitting Data Total > DBA-SLA Max. Bandwidth
Rev. Data
Reciever Tran. Data Rate Rate Rate Anay.
GE3/2 10M 8.3M 20M*(10/24)=8.3M
ONU2 8M 4.6M 20M*(14/24)=11.7M 8M*(8/14)=4.6M
ONU3 6M 3.4M 11.7M>8M 8M*(6/14)=3.4M
Total 24M 16.3M
1 The total transmitting data from ONU1 is 24M. And ONU1's DBA-SLA Max
bandwidth is 20M. The total transmitting data from ONU1 exceeds ONU1's
upstream bandwidth valueDBA-SLA bandwidth.
Therefore, according to the percentage of upstream data and the data between
ONUs, one can calculate:
ONU Upstream data: 20M*(10/24)=8.3M
Data between ONUs: 20M*(14/24)=11.7M
2 From the above step1, The total permitted transmitting data from ONU1 to
ONU2 and ONU3 is 11.7M. And ONU1's p2p-stream Max. bandwidth is 8M. The
total transmitting data from ONU1 to other ONUs exceeds ONU1's p2p-stream
bandwidth valueMax. Bandwidth.
Hence one can calculate the actual data from ONU1 to ONU2 and ONU3:
ONU2's received data: 8M*(8/14)=4.6M
ONU3's received data:8M*(6/14)=3.4M
Under this case, the transmitted data jam happens and only part of the data will
be transmitted according to ONU1's DBA-SLA and ONU1 p2p-stream
bandwidthconfiguration.
Since the actural total transmitted data is less than the DBA-SLA Max
bandwidth16.3M<20M, even though data traffic jam happens, part of the
bandwidth is wasted.
This is mainly because the actural data traffic between ONUs exceeds permitted
p2p-stream Max. bandwidth. When this case lasts for a long time, one needs to
modify the p2p-stream Max. bandwidth parameter.
Case3: Transmitting Data Total > DBA-SLA Max. Bandwidth
Rec. Data
Reciever Tran. Data Rate Rate Rate Anay.
GE3/2 30M 17.14M 20M*(30/35)=17.14M
ONU2 3M 1.72M 20M*(5/35)=2.86M 2.86M*(3/5)=1.72M
ONU3 2M 1.14M 2.86M<8M 2.86M*(2/5)=1.14M
Total 35M 20M
1 The total transmitting data from ONU1 is 35M. And ONU1's DBA-SLA Max
bandwidth is 20M. The total transmitting data from ONU1 exceeds ONU1's
upstream bandwidth valueDBA-SLA bandwidth.
Therefore, according to the percentage of upstream data and the data between
ONUs, one can calculate:
ONU Upstream Data: 20M*(30/35)=17.14M
Data between ONUs: 20M*(5/35)=2.86M
2 From the above step 1, the total transmitted data from ONU1 to ONU2 and
ONU3 is 2.86M. And ONU1's p2p-stream Max. bandwidth is 8M. The total
transmitted data from ONU1 to other ONUs is less than ONU1's p2p-stream
bandwidth valueMax. Bandwidth.
From above one can calculate the actural data from ONU1 to ONU2 and ONU3
is:
ONU2's received data: 2.86M*(3/5)=1.72M
ONU3's received data: 2.86M*(2/5)=1.14M
Under this case, data traffic jam happens and the data will be partially
transmitted according to ONU1's DBA-SLA and ONU1 p2p-stream bandwidth
configuration. Since the actural total transmitted data reaches the DBA-SLA
Max bandwidth, no bandwidth is wasted.
Deleting All the Here only take ONU1 as an example.
Configurations
Restore ONU1's p2p-stream bandwidth Configuration
1 Restore ONU1's p2p-stream maximum bandwidth.
telnet@BBS1000+(config-if-onu-1/1/1)# no p2p-stream
maximum-bandwidth
-------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=2, LLID[0]=2
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU vlan id = 101
ONU mac address = 00:07:ba:35:a2:ec
User ID =
RTT TQ = 6
Framed IP Address = 0.0.0.0
Framed Netmask = 0.0.0.0
Laser_on_time = 4
Laser_off_time = 4
Mpcp Timeout = 4000
Multicast filtering = enable
P2p-access policing = disable
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.10.00
Bootloader version = 02.01.10.00
ONU Management In this section, we will cover the following three kinds of ONU managements.
ONU Basic Management
ONU OAM Management
ONU Remote Management
ONU Basic Management ONU is usually located on the user side. For convenient management, BBS
1000+ provides CLI commands to manage ONU.
Enable/Disable ONU
shutdown means to prohibit using ONU. Activate ONU using command no
shutdown.
The default status of ONU is no shutdown. User can use the following
command to check ONU's status.
Reset ONU
BBS 1000+ provides CLI commands to reset one specific ONU.
For Example:
When user want to start up ONU with Lport 1 of OLT1/1, enter following CLI
command
telnet@BBS1000+(config-if-onu-1/1/1)# reset
Switch-cli
BBS 1000+ provides CLI commands toconfigure ONU's login mode.
This only applies to ONUs that supports CLI commands, for example,
ONU200A.
telnet@BBS1000+(config-if-onu-1/1/1)# switch-cli
ONU200A>
Step 2: Configure the encyrpion key used in actived link during the
communication.
Syntax: encryption key {default| update < ASCII String String up to 16 char>}
OAM link-test
OAM link test is used to test OAM link quality between the OLT and the ONU.
OLT sends specified number of frames at pre-defined frame size to the ONU.
Syntax:Configure terminal
interface epon-olt <module/port>
2 Configure ONU OAM link test
Syntax:oam link-test <frame-size> <total-num-of-frames>
Possible Values:
frame-size: 64~1514
num-of-frames: 0~100; 0: stop testing
Default value:
frame-size: 1000
Access Level: 2
Help description: To test onu physical link by specify frame.
3 After link test succeed, PON side will return the following testing result
parameters:
Example:
There are three states for the ONU.When ONU's is under OAM link test mode, it
can't perform PON loop-back test.
Figure 55 ONU's status
Example Topology
Figure 56 PON Loopback Configuring Topology
In the above topology, BBS 1000+'s uplink port GE3/3 is connected to Smartbits
port A and downlink port OLT2/2 is connected to Smartbits port B through
ONU1. Service VLAN 10 is configured on the BBS 1000+ and activate PON
loopback test on VLAN 10. Data packets are sent from Smartbits port B to port A
through BBS 1000+ and the user needs to observe the counters of the BBS
1000+ system. From the counter results, the user can know if the data link
between OLT2/2 and ONU1 is normal or not.
Configure Steps
1 Create the test VLAN 10, add ge2/3,ge3/3 as tagged members of this VLAN.
telnet@BBS1000+# show vlan 10
VLAN 10:
Name :
port(s) or group(s) :
telnet@BBS1000+(config-t)# vlan 10
telnet@BBS1000+(config-t-vlan-10)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-2/2)# shutdown
telnet@BBS1000+(config-t-if-olt-2/2)# no shutdown
telnet@BBS1000+(config-t-if-olt-2/2)# exit
-------------------------------------------------------------
1 2/2 1 4 4 00:07:ba:34:74:4c Dynamic
2 2/2 2 12 12 00:07:ba:34:07:90 Dynamic
3 2/2 3 20 20 00:e0:8e:ab:27:63 Dynamic
telnet@BBS1000+(config-t-if-olt-2/2)# onu 3
6 From the SmartBits port A send broadcast traffic to port B. The counter of
broadcast frames sent is 16,624,751.
7 Show the counters on the tested ONU.
telnet@BBS1000+# show interface epon-olt 2/2 onu 3 statistics
-------------------------------------------------------
OLT = 2/2, > Report Frames:
Tx OK .......................... = 97957
Rx OK .......................... = 94361
Gate Frames:
Tx OK .......................... = 155924
Rx OK .......................... = 97959
Sys Frames:
Tx OK .......................... = 0
Rx OK .......................... = 0
Rx Err ......................... = 0
Sys Octets:
Rx OK .......................... = 0
Rx PHY Err ......................... = 0
PON Octets:
Tx OK .......................... = 614963605904
Rx OK .......................... = 2211886068816
PON Frames:
Total Tx Dropped ............... = 0
Tx OK .......................... = 16722838
Rx OK .......................... = 16722815
Rx Err ......................... = 0
Rx Oversized ................... = 0
Rx OAM ......................... = 0
Tx OAM ......................... = 0
Rx FCS Error ................... = 0
Rx Multicast ................... = 97956
Tx Multicast ................... = 16722833
Rx Broadcast ................... = 16624751
Tx Broadcast ................... = 0
Registration Request Frames:
Tx OK .......................... = 0
Registration Frames:
Rx OK .......................... = 0
Registration Acknowledge Frames:
Tx OK .......................... = 0
Frames Tx:
Q0 ............................. = 0
Q1 ............................. = 0
Q2 ............................. = 16624751
Q3 ............................. = 0
Q4 ............................. = 0
Q5 ............................. = 0
Q6 ............................. = 0
Q7 ............................. = 0
Frames Dropped:
Q0 ............................. = 0
Q1 ............................. = 0
Q2 ............................. = 0
Q3 ............................. = 0
Q4 ............................. = 0
Q5 ............................. = 0
Q6 ............................. = 0
Q7 ............................. = 0
Radius Statistics:
Messages Sent .............................. = 0
Accounting Msgs Sent ................... = 0
Authentication Msgs Sent ............... = 0
Messages Received .......................... = 0
Accounting Msgs Received ............... = 0
Authentication Msgs Received ........... = 0
Accepted Msgs Received ............. = 0
Rejected Msgs Received ............. = 0
Challenged Msgs Received............ = 0
Accepted Msgs with Wrong Attributes ........ = 0
The Rx Broadcast value above is same as the packts from SmartBits port A.
-------------------------------------------------------
OLT = 2/2
Report Frames:
Tx OK .......................... = 1831385
Rx OK .......................... = 1827276
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
228 Chapter 7: Configuring GEPON Features
Gate Frames:
Tx OK .......................... = 1832226
Rx OK .......................... = 1855896
Sys Frames:
Tx OK .......................... = 0
Rx OK .......................... = 16624751
Rx Err ......................... = 0
Sys Octets:
Tx OK .......................... = 0
Rx OK .......................... = 2260966136
Rx PHY Err ......................... = 0
PON Octets:
Tx OK .......................... = 2326605452
Rx OK .......................... = 2326488476
PON Frames:
Total Tx Dropped ............... = 0
Total Rx Dropped ............... = 0
Rx FCS Error ................... = 0
Rx Multicast ................... = 1829506
Tx Multicast ................... = 1833365
Rx Broadcast ................... = 16624751
Tx Broadcast ................... = 16624751
The Rx and Tx values above is same as the packts from SmartBits port A.
Result Analyze:
From the statistics, the data link between OLT2/2 and ONU 3 is normal.
ONU Remote In this section, we will cover the following four kinds of ONU remote
Management managements.
Remotely upgrade ONU
Remotely change MAC address
Enable/disable ONU UNI port Auto-negotiation
Global enable/disable ONU UNI link status alarm filter on Management
Configure mode
The firmware upgrade methods can be divided into two ways according the
upgrade start time: manual and schedule. The manual way will upgrade the
ONU firmware immediately, while the schedule way will upgrade the ONU
firmware according to the to-be-set start time and the to-be-set duration time.
The four ONU100s are connected to BBS 1000+ 's port OLT1/1 through splitter.
Suppose that those ONUs are registered to BBS 1000+ through logical port
binding.
1 Enter ONU upgrade configuration command mode.
GEPON OLT BBS 1000+ Doc. Code L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
ONU Management 231
BBS1000+(config-t)# onu-upgrade
BBS1000+(config-t-onu-ugp)#
Hardware type: 2
Update method: manual
Firmware version: 2.1.20
Image name: 2.1.20.bin
-------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=1, LLID[0]=1
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state = authorized
ONU mac address = 00:07:ba:34:bd:b1
User ID = onu_2
RTT TQ = 2
Laser_on_time = 4
Laser_off_time = 4
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.18
Bootloader version = 02.01.10
--------------------------------------------------------------
OLT = 1/1, Logical port = 2, ONU id=3, LLID[0]=3
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state = authorized
ONU mac address = 00:07:ba:34:bd:b8
User ID = onu_6
RTT TQ = 2
Laser_on_time = 4
Laser_off_time = 4
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.18
Bootloader version = 02.01.10
--------------------------------------------------------------
OLT = 1/1, Logical port = 4, ONU id=4, LLID[0]=4
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state = authorized
ONU mac address = 00:07:ba:34:00:59
User ID = onu_1_1_1
RTT TQ = 2
Laser_on_time = 4
Laser_off_time = 4
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.18
Bootloader version = 02.01.08
--------------------------------------------------------------
OLT = 1/1, Logical port = 3, ONU id=5, LLID[0]=5
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state = authorized
ONU mac address = 00:07:ba:34:bd:d6
User ID = onu_4
RTT TQ = 2
Laser_on_time = 4
Laser_off_time = 4
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.18
Bootloader version = 02.01.10
BBS1000+(config-t-if-onu-2/4/2)# remote-mgmt
xx:xx:xx:xx:xx:xx
User can use the following command to shut down the status alarm filter:
After disabling the alarm filter function, user can check UNI port's link status
change at the Trap Server or syslog server if configured with debugging
Severity.
ONU Configuration
Commands
Table 39 ONU Configuring Commands
BBS1000+(config-if-onu-2/1/2)#
BBS1000+(config-if-onu-2/1/2)# shutdown
BBS1000+(config-if-onu-2/1/2)#
-------------------------------------------------------------
OLT = 2/4, Logical port = 1, ONU id=1, LLID[0]=1
-------------------------------------------------------
OLT = 1/1, > Report Frames:
Tx OK .......................... = 2567097
Rx OK .......................... = 2567080
Gate Frames:
Tx OK .......................... = 2580781
Rx OK .......................... = 2602965
Sys Frames:
Tx OK .......................... = 15
Rx OK .......................... = 840960
Rx Err ......................... = 0
Sys Octets:
Rx OK .......................... = 15500566743
Rx PHY Err ......................... = 0
PON Octets:
Tx OK .......................... = 72607127296
Rx OK .......................... = 57228170194375
PON Frames:
Total Tx Dropped ............... = 0
Tx OK .......................... = 3375974
Rx OK .......................... = 8878590
Rx Err ......................... = 0
Rx Oversized ................... = 0
Rx OAM ......................... = 1
Tx OAM ......................... = 1
Rx FCS Error ................... = 0
Rx Multicast ................... = 8878685
PON System MAC Through PON MAC Address Table, user can check ONU and its connected
Address Table servers' L2 transmission information.
The PON part of BBS 1000+ system also supports MAC Address Table. This
MAC Address Table is composed by the following parts:
All connected ONU's MAC addresses, ONU's LAN IDs, OLT port number
and their Lport numbers, LLID;
All ONU-connected equipments (PCs, for example) MAC addresses (if any),
ONU's VLAN IDs, OLT port numbers and their Lports numbers, ,LLID.
MAC Address
Configuration
Commands
Topology Example
Figure 58 Configuring PON MAC Address Table
As shown in Figure 58, set ONU's MAC limit as 2. We will describe the MAC
limit mechanism in the following cases:
CASE1: Connect PC1, PC2 and PC3 sequentially to ONU, BBS 1000+ system
will only connect the first two PCs (PC1 and PC2.
CASE2: Through MAC address aging, reset PON's MAC address table. Then,
for example, BBS 1000+ disconnects PC2, BBS 1000+ system will learn PC1
and PC3's MAC addresses.
System Requirement
ONU can be register successfully to the BBS 1000+.
-------------------------------------------------------------------------------
1/1 1 101 10000 100000 30 0 00:07:ba:35:a2:ec
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
Here we can know that the MAC address of PC1 and PC2 are learned by BBS
1000+ PON system.
*** WARNING: Please note that after the timer change, you must
reboot
the box, or reset the OLT's for the system to function
properly.
Are you sure you want to go ahead (y/n) ? y
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
240 Chapter 7: Configuring GEPON Features
telnet@BBS1000+(config-t-if-olt-1/1)# no shutdown
Understanding The IEEE 802.1x standard defines a client-server based access control and
Remote authentication protocol that prevents unauthorized connection from publicly
Authentication accessible ports without proper authentication. Devices wishing to access
through RADIUS services behind a port under 802.1 x controls must authenticate themselves,
before any data packets originating from the devices are allowed to pass
through. In the cases of authentication failure, the device will be prevented from
accessing the port and therefore will not be able to use the services behind the
port.
The specific roles of the three network components are described below:
ONU system (Example: ONU 200A) The client that requests access to
LAN and OLT services. It also responds to query from the OLT in order to
establish services. IEEE802.1x-compliant client software must run on the
ONU host CPU.
BBS system (Example: BBS 1000+) The Optical Line Terminal (OLT)
board controls the physical access to the network based on the
authentication status of the ONU. It acts as a proxy between the client and
the authentication server, requesting identity information from the ONU,
verifying the information with RADIUS server and replaying it back to the
ONU. This authenticator software runs inside the OLT firmware. The BBS
system includes the RADIUS client on the OLT host CPU, which is
responsible for encapsulating and encapsulating the EAP frames and
interacting with the authentication server.
Authentication Server (RADIUS Server) performs ONU authentication.
The authentication server uses the authentication credentials supplied by the
ONU and notifies the BBS system whether or not the ONU is authorized to
access services. The Authentication server connects to the BBS 1000+ via
UDP connection.
802.1 x /RADIUS The below figure illustrates the 802.1x EAP authentication process model
Process comprised of a PC client, BBS 1000+ and Radius Server. In this model, the
Radius server should support EAP authentication, and the client should support
MD5-chanllenge authentication.
Figure 59 802.1x/RADIUS Authentication Process
RADIUS Authentication RADIUS server includes authentication server and accounting server.
Server and Accounting
Server BBS 1000+ system supports 4 types of RADIUS servers:
ONU authentication
ONU accounting
CLI user authentication
CLI user accounting
For each type of RADIUS server, BBS 1000+ support up to 2 RADIUS servers,
one is primary server and another secondary server as redundancy.
connect to another RADIUS server first, if that failed, the switch-over failed
and the current RADIUS server will still be used.
After 15 minutes (configurable) on secondary server, BBS 1000+ will try to
switch back to primary server.
Special Requirement for There are some special requirements for CLI user authentication:
CLI User Authentication
If retry expires on secondary server, BBS 1000+ refers to local database and
if it finds account, CLI user can login. This guarantees CLI user can login
even without a RADIUS server.
If there is not account on the Radius server and BBS 1000+ receives "reject"
message, BBS 1000+ disconnects telnet session immediately.
After 3 times (configurable) CLI RADIUS authentication failure, the BBS
1000+ system will automatically switch to use local-DB for CLI user
authentication. This is designed to prevent the user been locked out. Be
noticed, this automatically change would affect user saved configuration,
which means the BBS 1000+ will use pre-saved user-authentication-method
to authenticate CLI user after system reboot.
user-auth-method {radius-serversystem-database}
For Example:
Configuring 802.1 x RADIUS authentication configuration includes the ONU authentication and CLI
/RADIUS user authentication. BBS 1000+ supports RADIUS server authentication
Authentication redundancy, i.e., you can configure to have the primary and secondary RADIUS
server.
Shared Keys
After user set primary RADIUS server shared-keys, the corresponding
secondary RADIUS server will set automatically, vice versa.
Realm
RADIUS server realm is supported only in ONU authentication. It append to the
end of ONU username.
Auto switch
If auto-switch is enabled, the secondary RADIUS server will be used when the
primary RADIUS server does not work, however, the system will continue to
retry to switch back to the primary RADIUS server after certain period. The retry
period and total number of retry times are configurable.
Timeout
User can configure the message timeout value when retry to access the primary
RADIUS server.
NAS
A Network Access Server (NAS) is responsible for passing user information to
designated RADIUS server, and then acting on the returned response. This
function is performed on BBS 1000+ OLT.
Return List on the In order to finish ONU and CLI users' remote authentication, the administrator
Radius Server needs to configure RADIUS server.
MaxJitter
Priority
Device-Id
Module-Id
Port-No
Logical-Port-No
Port-Limit
Remote Authentication Typical configuration commands of the Remote Authentication are as following:
Configuration
Commands
Example Topology
Figure 61 RADIUS Server Authentication Topology
In the topology above, the RADIUS Server is directly connected to the BBS
1000+ Management port.
When the RADIUS Server is connected to the BBS 1000+'s uplink port (In-Band
mode), the uplink port's IP address must be configured.
Configuration Tasks The general tasks involved in configuring RADIUS are given below. After this
task overview, detailed steps are described, using the topology example in
Figure 61.
1 Install the RADUIS Server software on the PC
2 Configure RADUIS
3 Configure BBS 1000+
4 Verify ONU1's RADIUS authentication
After copying the above directory, the RADIUS server must be restarted.
Configure RADUIS
1 From the Window's Start button, select [Programs/Steel-Belted
RADIUS/Steel-Belted RADIUS Administrator]. The RADIUS server starts up and
the following window is displayed, as shown in Figure 63.
Figure 63 RADIUS Administrator Main Window
2 From the Radius server selection options, select the default setting, Local.
Then click <Connect> to connect with the server. The connection process and
results are displayed in the status box, as shown in Figure 64.
If the RADIUS Server is to be connected remotely, select the Remote option
instead, and then enter the Remote Server's IP address.
3 From the option list on the left side of the configuration window, select RAS
Clients. Afterwards the window will display a new set of controls, as shown in
Figure 65.
4 From the Client name dropdown list select ANY, and then from the
Make/model dropdown list select UTStarcom.
5 Click <Edit authentication shared secret...>. The Enter shared secret dialog
box is displayed, as shown in Figure 66.
Figure 66 Edit Authentication password
7 From the option list on the left side of the configuration window, select Users.
Afterwards the window will display a new set of controls, as shown in Figure 68.
Figure 68 RADIUS Users Selection
8 Click <Add> to display the Add New User dialog box, as shown in Figure 69.
GEPON OLT BBS 1000+ Doc. Code L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
ONU Remote Authentication Example 255
9 In the Enter user name text box, enter the ONU's ID. (The ONU-ID can be
found on a label on the bottom of the ONU device or via CLI command. In this
example we have used "ONU1".)
10 Click <OK>.
Here the User is an ONU device, so Domain and SecureID does not need to be
configured..
11 After a new user is added the <Set password> button will be enabled. Click
<Set password>. The Enter User Password dialog box is displayed, as shown
in Figure 70.
Figure 70 Enter User Password
14 Select the Return list attributes tab page, and then click <Ins>. The Add New
Attribute dialog box is displayed, as shown in Figure 72.
Figure 72 Add New Attribute
15 From this dialog box new RADIUS attributes can be added using the three step
procedure described below. Add all of the attributes listed in Figure 73 need to
be added.
a Select an attribute from the Available attributes list.
b In the Enter a number text box, enter the attribute value.
c Click <Add>.
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
4 Set the RADIUS server's IP address and the shared key on BBS 1000+.
This shared key must match the one configured in Configure RADUIS on page
251. (In this example "mypassword" is used.)
Warning: reboot system to take effect for radius server shared key
modification.
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
GEPON OLT BBS 1000+ Doc. Code L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
ONU Remote Authentication Example 259
telnet@BBS1000+(config-t-if-olt-1/1)#
2 The OLT port is in the shutdown state by default, enter the following command
to activate the OLT port.
telnet@BBS1000+(config-t-if-olt-1/1)# no shutdown
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
------------------------------------------------------------
OLT = 1/1, Logical port = 1, ONU id=1, LLID[0]=1
Internal state = Running, admin state = Enabled
Registered state = Registered, authentication state =
authorized
ONU vlan id = 101
ONU mac address = 00:07:ba:34:af:36
User ID = 1010104390472910
RTT TQ = 2
Framed IP Address = 0.0.0.0
Framed Netmask = 0.0.0.0
Laser_on_time = 4
Laser_off_time = 4
Multicast filtering = enable
Hardware type = ONU100
Hardware version = 0
Firmware version = 02.01.11.00
Bootloader version = 02.01.10.00
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#exit
telnet@BBS1000+#
Example Topology
Figure 76 RADIUS Server Authentication Topology
In the topology above, the RADIUS Server is directly connected to the BBS
1000+ Management port.
When the RADIUS Server is connected to the BBS 1000+'s uplink port (In-Band
mode), the uplink port's IP address must be configured.
Configuration Requirement
The RADUIS Server software have been installed on the PCs
2 From the Radius server selection options, select the default setting, Local.
Then click <Connect> to connect with the server. The connection process and
results are displayed in the status box, as shown in Figure 64.
If the RADIUS Server is to be connected remotely, select the Remote option
instead, and then enter the Remote Server's IP address.
3 From the option list on the left side of the configuration window, select RAS
Clients. Afterwards the window will display a new set of controls, as shown in
Figure 65.
Figure 79 RADIUS RAS Clients Selection
4 From the Client name dropdown list select ANY, and then from the
Make/model dropdown list select UTStarcom.
5 Click <Edit authentication shared secret...>. Then Enter shared secret dialog
box is displayed, as shown in Figure 66.
Figure 80 Edit Authentication password
7 From the option list on the left side of the configuration window, select Users.
Afterwards the window will display a new set of controls, as shown in Figure 68.
8 Click <Add> to display the Add New User dialog box, as shown in Figure 69.
Figure 83 Add New User
9 In the Enter user name text box, enter the CLI account. (In this example we use
mytestuser.)
10 Click <OK>.
11 After a new user is added the <Set password> button will be enabled. Click
<Set password>. The Enter User Password dialog box is displayed, as shown
in Figure 70.
14 Select the Return list attributes tab page, and then click <Ins>. The Add New
Attribute dialog box is displayed, as shown in Figure 72.
Figure 86 Add New Attribute
16 Click <Add> to add this attribute and click<Close>. The Steel-Belted Radius
Configuration dialog box is displayed and the newly added attributes are listed
in the Return list attributes tab page, as shown in Figure 74.
Figure 88 Steel-Belted Radius Configuration (II)
2 Set the primary RADIUS server's IP address and the shared key on BBS 1000+.
This shared key must match the one configured in Configure RADUIS on page
251. (In this example "mypassword" is used.)
telnet@BBS1000+#
telnet@BBS1000+(config-mgmt)#
Username:mytestuser
Password:******
telnet@BBS1000+>
Result Analyze
CLI user logs into BBS 1000+ system through primary RADIUS server
authentication.
Case2: Connect primary and secondary RADIUS server both, and primary
server doesn't work normally.
Username:mytestuser
Password:******
telnet@BBS1000+>
Result Analyze
Since primary RADIUS server can not work normally, by the switch between
primary and secondary servers, CLI user logs in BBS 1000+ system through
secondary RADIUS server authentication.
Case3: Connect primary and secondary RADIUS server both, but primary
server and secondary don't work normally.
1 Add a user
telnet@BBS1000+(config-mgmt)# user add mytestuser gepon 10
Password:******
telnet@BBS1000+>
user-auth-method system-database
Result Analyze
Since both primary and secondary RADIUS servers cannot work normally, BBS
will automatically switch to local authentication. CLI user logs in BBS 1000+
system through local authentication.
At the same time, by checking system's running configuration, one knows that
the system's authentication is set to local. Only after rebooting the system, can
one change BBS 1000+'s CLI user authentication.
Delete User-mytestuser
1 Delete user mytestuser.
BBS1000+(config-mgmt)# user delete mytestuser
User Access
----------------------+---------
admin 10
Configuration 802.1 x RADIUS server accounting is implemented in BBS 1000+ to track CLI users and
/RADIUS Accounting ONU use of system for security enhancement. Same as in the RADIUS server
authentication, BBS 1000+ supports RADIUS server accounting redundancy.
Each time ONU unregistered from the BBS100, a RADIUS accounting STOP
message will be sent to the RADIUS accounting server.
Each time a CLI user login into BBS 1000+ using RADIUS authentication, a
RADIUS accounting START message will be sent to the RADIUS accounting
server.
Each time a CLI user log out from the BBS 1000+ (could be user logout, session
timeout, closing telnet session...), a RADIUS accounting STOP message will be
sent to the RADIUS accounting server.
Configuring ONU accounting RADIUS server
Configuring CLI user accounting RADIUS server
Remote Accounting Typical configuration task of the Remote Accounting are as following:
Configuration
Commands
Table 43 Remote Accounting Configuring Commands
Remote Accounting To configure ONU accounting and CLI accounting, please follow the following
Configuration tasks.
Procedure
Enabling RADIUS server authentication
Configure ONU accouting
Configuring ONU Primary/Secondary accounting RADIUS server
Configuring RADIUS server realm (supported in onu authentication)
For complete information about the syslog message format, structure, severity
level and detailed system message, refer to the GEPON BBS 1000+ System
Message Manual.
Syslog messages can be sent to the console, remote syslog server and/or BBS
1000+ Flash memory.
Console: By default, syslog messages with a severity level higher than 3
(errors) will be displayed on the console screen.
Syslog Server: Up to five syslog servers, each with its own IP address and
UDP port number can be configured. Each server can be configured to
record different facility and severity level messages as required.
Flash: For troubleshooting purposes, critical messages can be sent to the
BBS 1000+ Flash memory. Due to Flash memory size limitation, only the first
128 bytes of the message will be logged.
Understanding the
Concepts
System Log Message BBS 1000+ provides two system log message formats, RFC 3164 format, and
Format Non-RFC 3164 format.
RFC 3164
RFC 3164 is defined for UNIX hosts. Based on RFC 3164, the full format of a
syslog message has three parts:
The first part is the PRI
The second part is the HEADER
The third part is the MSG
Non-RFC 3164
The Non-RFC 3164 syslog message format is more suitable for switch/router
devices. This type of message is easier to read and the values could be
defined in message as decimal, chars and hex.
The structure of a Non-RFC 3164 formatted syslog message is shown below:
mm/dd/yy:hh/mm/ss:facility-severity-MNEMONIC:description
Example:
syslog:SAT JUL 17 16:18:18 2004:LOG-7-USER:user [admin] has logged
into the system
Sending Syslog Specific Syslog messages can be displayed on the Console or recorded in the
Messages to the BBS 1000+ Flash memory. The messages sent to the Console or Flash
Console or Flash memory can be limited according to the message's severity level By default,
Memory severity level 3 (errors) Syslog messages and higher are sent to both the
Console and Flash memory.
Either the numeric form of the Severity Level or its equivalent Keyword can be
used in the command. Severity Levels along with their related Keywords are
displayed in Table 45.
Table 45 Syslog Severity Level Description
Logging Host Server Up to five syslog servers can be connected to the BBS 1000+ system. Each
and Facilities server can be configured to log messages related to one or more facility types.
The minimum severity level of syslog messages to be sent to each server is also
configurable.
Both the IP address and UDP port of the Syslog server is configurable. The
UDP port range is 1 to 65535.
When the Syslog server port is not specified, the default port (514) will be used.
Code Facility
auth Authorization system
dhcp Dynamic Host Configuration Protocol
eth Ethernet interface
pon Passive Optical Network
snmp Simple Network Management Protocol
sys System
syslog System log message
user User process
When specifying the severity level of Syslog messages to be sent to the Syslog
server, only the severity level keyword can be used. This is different than for
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
278 Chapter 9: Configuring Syslog
Syslog messages sent to the Console or Flash memory, which can be specified
by either the severity level number or keyword.
System Log Common system log configuration commands are shown in Table 47:
Configuration
Commands
Table 47 Syslog Configuration Commands
Syslog Configuration The general steps for configuring Syslog are listed below:
Procedure
1 Enter the CLI Configure Management command mode.
2 Set the Syslog message format.
3 Configure Syslog for one or more of the following devices:
Console
BBS 1000+ Flash memory
Syslog Server
Example Topology
Figure 89 Syslog Configuration Topology
BBS 1000+ connects with the Cisco 3750 switch via BBS 1000+ uplink port
GE3/1. The Cisco switch connects with the Syslog Server via the switch's g1/0/6
interface. In this example, Cisco 3750 is operating as an L2 switch.
telnet@BBS1000+(config-t-vlan-500)# exit
VLAN 500:
Name :
port(s) or group(s) :ge3/1
Tagged port(s) or group(s) :ge3/1
Untagged port(s) or group(s) :
2 If the next hop field is any other value except 0.0.0.0, refer to Verify Out-band
default gateway on page 82 to remove the out-band gateway.
BBS1000+(config-mgmt)#
BBS1000+(config-mgmt)#
3750(config-vlan)#exit
3750(config)#
3750(config-if)#
3 Click the Syslog Server tab on the left side of the window. The Syslog Server
window is displayed, as shown in Figure 91.
Figure 91 Syslog Server Window
4 Click the <Configure Syslog Server> icon, and then select the Syslog
Configuration tab, as shown in Figure 92.
5 From the Syslog Configuration tab page, set the following parameters:
Directory for syslog: D:\gepon
Who can log to this: Anyone
Log message to: One file:Syslog.log
2 Verify the L3 connection between the Syslog server and BBS 1000+.
c:\> ping 20.0.0.1
3 Logout of BBS 1000+ and then re-login, entering the Privileged EXEC command
mode.
telnet@BBS1000+# logout <ENTER>
Username:admin
Password:******
telnet@BBS1000+> enable
telnet@BBS1000+#
4 From the Syslog Server, verify that the previous user login operation is recorded
in the syslog. Refer to the screen capture below:
GEPON OLT BBS 1000+ Doc. Code L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
Syslog Configuration Example 285
BBS1000+(config-mgmt)#
telnet@BBS1000+(config-t-vlan-500)# exit
telnet@BBS1000+(config-t)#
Introduction RSTP The BBS 1000+ RSTP can operate either in RSTP or STP-compatible mode. In
a network, if some devices run STP and some devices run RSTP, The devices
run RSTP should be configured to operate in STP-compatible mode.
By default, the BPDU flood is disable.That is, BPDU packects will be forwarded
directorly to CPU. When enable BPDU flood, BPDU packests will flood to all
ports in VLAN.
RSTP Configuration
Procedure
1 Enable Rapid Spanning Tree for one VLAN under Configure Terminal command
mode.
2 Configure RSTP parameters for this VLAN under Configure Terminal command
mode if need.
Forward delay time
Hello time
Max Age Time
Bridge priority
RSTP Configuration
Example
Application Description In this example, the BBS 1000+ functions as an L2 Switch. The data VLAN is
VALN 10. It is connected to the Cisco 3750 via two links. Spanning-Tree protocol
is activated on both the BBS 1000+ and the Cisico 3750 to maintain a loop-free
topology.
Configuration Requirement
BBS 1000+ PON port OLT 1/1 is running in stack-tag mode.
PCs IP addresses have been configured as the above figure.
Configuration Tasks Configure the ONU's MAC and PON's lport binding
telnet@BBS1000+(config-t)# interface epon-olt 1/1
telnet@BBS1000+(config-t-if-olt-1/1)# no shutdown
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)# exit
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
When the communication between ONU and OLT is normal, the CLI
command show interface epon-olt 1/1 mac-address-table can be used to
obtain the ONU's MAC address.
VLAN 10:
Name :
port(s) or group(s) :ge1/1, ge3/2,ge3/4
Tagged port(s) or group(s) :ge1/1, ge3/2,ge3/4
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-vlan-10)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu-vlan 1 10
telnet@BBS1000+(config-t-if-olt-1/1)#exit
telnet@BBS1000+(config-t)#
Vlan 10
Spanning Tree enabled protocol RSTP
Root ID Priority 32778
Address 0011.93c9.0f80
Port ge3/2
Hello Time 2 sec Max Age 20 sec Forwad Delay 15 sec
3750#conf term
3750(config)#vlan 10
3750(config-vlan)#exit
3750(config)#
3750(config-if)#switchport
3750(config-if)#exit
3750(config)#exit
3750(config-if)#switchport
3750(config-if)#exit
3750(config)#
3750(config-if)#switchport
3750(config-if)#exit
3750(config)#
VLAN0010
Spanning tree enabled protocol ieee
Root ID Priority 32778
Address 0011.93c9.0f80
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Vlan 10
Spanning Tree enabled protocol RSTP
Root ID Priority 32778
Address 0011.93c9.0f80
Port ge3/2
Hello Time 2 sec Max Age 20 sec Forwad Delay 15 sec
VLAN0010
Spanning tree enabled protocol ieee
Root ID Priority 32778
Address 0011.93c9.0f80
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
From the display information above, Link1 between GE3/2 and G1/0/7 is
working and Link2 between GE3/4 and G1/0/8 is backup one.
1 Disconnect Link1 between GE3/2 and G1/0/7 through disabling GE3/2 port on
BBS1000+.
telnet@BBS1000+(config-t)# interface giga-ethernet 3/2
telnet@BBS1000+(config-t-if-ge-3/2)# shutdown
GE: 3/2
Switchport: Enabled
Name: GE-10
MTU: 1500bytes
Speed: 0Mbps
AdminStatus: Disable
Auto Negotiation: Enabled
Ingress vlan filter: Enabled
Flow Control receive: Enabled
Flow Control transmit: Enabled
Storm-control multicast: disable
Storm-control broadcast: disable
Storm-control unicast: 5
Maximum receive frame: 1532
Link Status: Down
Transceiver Type: None
PVID: 1
Vlan 10
Spanning Tree enabled protocol RSTP
Root ID Priority 32778
Address 0011.93c9.0f80
Port ge3/3
Hello Time 2 sec Max Age 20 sec Forwad Delay 15 sec
Bridge ID Priority 61450
Address 0000.1121.160c
Hello Time 2 sec Max Age 20 sec Forwad Delay 15 sec
Interface Role State Cost Priority Type PortFast
---------- ---------- ---------- ---------- ---------- --------- ----------
ge1/1 DESIGNATED FORWARDING 20000 128 P2P FALSE
ge3/2 DISABLED DISABLED 20000000 128 P2P FALSE
ge3/4 ROOT FORWARDING 20000 128 P2P FALSE
From the display information above, Link2 between GE3/4 and G1/0/8 is
working.
1 Reconnect Link1 between GE3/2 and G1/0/7 through enabling GE3/2 port on
the BBS1000+.
telnet@BBS1000+(config-t)# interface giga-ethernet 3/2
telnet@BBS1000+(config-t-if-ge-3/2)# no shutdown
GE: 3/2
Switchport: Enabled
Name: GE-10
MTU: 1500bytes
Speed: 1000Mbps
AdminStatus: Enable
Auto Negotiation: Enabled
Ingress vlan filter: Enabled
Flow Control receive: Enabled
Vlan 10
Spanning Tree enabled protocol RSTP
Root ID Priority 32778
Address 0011.93c9.0f80
Port ge3/2
Hello Time 2 sec Max Age 20 sec Forwad Delay 15 sec
From the display information above, Link1 between GE3/2 and G1/0/7 is
working and Link2 between GE3/4 and G1/0/8 is backup one.
DHCP Configuration To configure the BBS 1000+ DHCP server feature, you will perform the following
Tasks tasks:
Table 49 DHCP Configuring Commands
Create manual binding when rfd2131 policy used host <ip address> hardware-address <MAC address>
Create manual binding when sbb policy used host <ip address> vlan-id <vlan-id>
Configure merit-dump merit-dump <str>
Configure root-path root-path <str>
Configure NTP servers ntp-server < address1> [<address2>] [<address3>]
Configure Syslog servers syslog-server < address1> [<address2>] [<address3>]
Related Show Commands
Example Topology
Figure 96 DHCP Configuration Example
The following example creates a routed interface on uplink port GE3/2 and
creates two VLANs, 4093 and 4094. It adds Gigabit Ethernet ports GE1/1,
GE1/2, GE1/3 and GE1/4 to these two VLANs. It thus creates two L3 super SVI
interface 10.10.0.0 and 10.10.1.0 and adds member VLANs to these 2 super
VLANs. After basic BBS1000+ configuration, it enables the DHCP service and
creates DHCP address pool UT-1 and UT-2 .
Configuration Requirements
1 BBS 1000+ PON ports (OLT1/1 and OLT1/4) are assumed to run in stack-tag
mode, and these two ports are active.
2 The configuration of call server related to VoIP has been finished.
3 The configuration related to call server on ONU404 has been finished.
Configuration Tasks The general tasks involved in configuring the BBS 1000+ as DHCP Server are
given below. After this task overview, detailed steps are described for each task,
using the topology example in Figure 96.
1 Verify BBS 1000+'s Running Mode
2 Create a Routed Interface
3 L2 Configuration--Create ONU's Service VLANs
4 L2 Configuration--Create Two Super VLANs
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
300 Chapter 11: Configuring DHCP Server
Login: admin
Password:*****
telnet@BBS1000+> enable
telnet@BBS1000+#
PON Configuration
Configure ONU's authentication method as local and enable local lport binding
function.
If local sla authentication is disabled in the above display information, enter the
following CLI command to enable it:
If local logical port strict binding is disabled in the above display information,
enter the following CLI command to enable it:
2 Bind ONU 1's MAC address with BBS 1000+ port OLT1/1's lport 1.
telnet@BBS1000+(config-t)# interface epon-olt 1/1
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)# exit
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
3 Bind ONU 1's MAC address with BBS 1000+ port OLT1/4's lport 1.
telnet@BBS1000+(config-t)# interface epon-olt 1/4
telnet@BBS1000+(config-t-if-olt-1/4)# onu 1
telnet@BBS1000+(config-if-onu-1/4/1)#exit
telnet@BBS1000+(config-t-if-olt-1/4)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-ge-3/2)# no switchport
telnet@BBS1000+(config-t-if-ge-3/2)# exit
telnet@BBS1000+(config-t)#
VLAN 50:
Name :
port(s) or group(s) :ge1/1,ge1/4
Tagged port(s) or group(s) :
Untagged port(s) or group(s) :ge1/1,ge1/4
telnet@BBS1000+(config-t-vlan-50)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu-vlan 1 50
telnet@BBS1000+(config-t-if-olt-1/1)#
telnet@BBS1000+(config-t-if-olt-1/4)# onu-vlan 1 50
telnet@BBS1000+(config-t-if-olt-1/4)#
VLAN 100:
Name :
port(s) or group(s) :ge1/1
Tagged port(s) or group(s) :ge1/1
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-vlan-100)#exit
telnet@BBS1000+(config-t)#
VLAN 200:
Name :
port(s) or group(s) :ge1/4
Tagged port(s) or group(s) :ge1/4
Untagged port(s) or group(s) :
telnet@BBS1000+(config-t-vlan-100)# exit
telnet@BBS1000+(config-t)#
2 Assign BBS 1000+ downlink GE ports GE1/1 and GE1/4 as tagged members of
VLAN 4093.
telnet@BBS1000+(config-t-vlan-4093)# member ge1/1,ge1/4
tagged
telnet@BBS1000+(config-t-valn-4093)# exit
telnet@BBS1000+(config-t)#
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
304 Chapter 11: Configuring DHCP Server
4 Assign BBS 1000+ downlink GE ports GE1/1 and GE1/4 as untagged members
of VLAN 4094.
telnet@BBS1000+(config-t-vlan-4094)# member ge1/1,ge1/4
untagged
telnet@BBS1000+(config-t-valn-4094)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-vlan-4093)#
telnet@BBS1000+(config-t-if-vlan-4093)#
3 Add SVI member interfaces(VLAN 100 and 200) to the Super SVI.
telnet@BBS1000+(config-t-if-vlan-4093)# member-vlan 100,200
telnet@BBS1000+(config-t-if-vlan-4093)#
telnet@BBS1000+(config-t-if-vlan-4093)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-vlan-4094)# super-svi
telnet@BBS1000+(config-t-if-vlan-4094)# member-vlan 50
telnet@BBS1000+(config-t-if-vlan-4094)# no shutdown
telnet@BBS1000+(config-t-if-vlan-4094)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-dhcp)# exit
telnet@BBS1000+(config-t-dhcp)# exit
telnet@BBS1000+(config-t-dhcp)# lease 1 12 30
telnet@BBS1000+(config-t-dhcp)#
5 The DHCP configuration is finished, exit from Configure DHCP command mode.
telnet@BBS1000+(config-t-dhcp)# exit
BBS1000+(config-t)#
2 Configure ONU404-1's downlink port and uplink port LAN4's VLAN ID as 100,
as shown in the figure below.
telnet@BBS1000+(config-t)#
From PC1:
C:\ >ipconfig/renew
IP Address. . . . . . . . . . . . : 10.10.1.2
DHCP Relay To configure BBS 1000+ as a DHCP Relay, the following tasks can be
Configuration Tasks performed as below:
Table 50 DHCP Relay Configuring Commands
Example Topology
Figure 100 DHCP Relay Configuration
In the above figure, two DHCP Servers are connected to BBS 1000+'s uplink
port GE3/1 via the Cisco switch.
Configuration Requirements
1 BBS 1000+ PON ports (OLT1/1 and OLT1/2) are assumed to run in stack-tag
mode, and the two ports are active.
2 ONU1 and ONU2 are bound with the corresponding PON's lport.
3 Configure ONU1 and GE1/1 as the members of VLAN101 also configure
ONU2 and GE1/2 as the members of VLAN 165
Configuration Tasks The tasks involved in configuring DHCP Relay are described below, using the
topology example in Figure 100.
1 Install the DHCP Server software on both DHCP serversr
2 Configure a Routed Interface on BBS 1000+
3 Create a Super SVI on BBS 1000+
4 Start the DHCP Relay service on BBS 1000+
5 Verify the DHCP Relay configuration
GEPON OLT BBS 1000+ Doc. Code L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
DHCP Relay configuration Example 313
2 From the left windowpane, expand the This Computer branch and Right click
Scopes, seclect New Scope from the shutcut menu. Create a new Scope is
shown in the following figure.
3 Click <OK>, return to Properties lable interface in the BBS 1000+ Scope.
GEPON OLT BBS 1000+ Doc. Code L2 CO00 2321 06 15 00
CLI Operation Guide June 2007
DHCP Relay configuration Example 315
4 From BBS 1000+ Scope's Properties window, select options label , and right
click the blank space, choose New... on the pop-up menu, Select Option window
displays as below:
Figure 105 Select Option Window
5 Select Gateways from the list, to display the Gateways dialog box, as shown
below.
6 Enter 50.0.0.10 in the Address to add textbox, and then click <Add>. The item
will be added to the list on the right. Click <OK> when finished. The Options is
displayed as shown below:
Figure 107 Configuring Address
telnet@BBS1000+(config-t-if-ge-3/1)#
telnet@BBS1000+(config-t-if-ge-3/1)# no switchport
telnet@BBS1000+(config-t-if-ge-3/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-1000)# exit
telnet@BBS1000+(config-t)#
6 Configure the DHCP relay's target addresses, i.e., the two DHCP servers.
telnet@BBS1000+(config-t-if-vlan-1000)# dhcp relay-to
60.0.0.1
telnet@BBS1000+(config-t-if-vlan-1000)#exit
telnet@BBS1000+(config-t)#
8 Verify that the Super SVI was configured properly by viewing its configuration
information.
telnet@BBS1000+(config-t)# show interface super-vlan
Member: 101,165
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
C:\> ipconfig/renew
Multicast Address Multicast IP addresses are Class D IP addresses, which include a range of IP
addresses from 224.0.0.0 to 239.255.255.255.
Some Multicast IP addresses, for example those listed below, are reserved for
special use.
224.0.0.1 All multicast-capable hosts
224.0.0.2 All multicast-capable routers
224.0.0.4 All DVMRP routes
224.0.0.5 All OSPF routers
224.0.0.13 All PIM routes
Configuring IGMP BBS 1000+ can use IGMP snooping to suppress the flooding of multicast traffic
Snooping by dynamically configuring ports so that multicast traffic is only forwarded to
ports associated with IP multicast devices.
As the name implies, IGMP snooping requires the LAN switch to snoop on the
IGMP transmissions between the host and the router, and keep track of
multicast groups and member ports.
IGMP Snooping Work On the BBS 1000+ system IGMP snooping can be enabled at either the Global
Mode or VLAN level. By default Global IGMP snooping is disabled and IGMP
snooping on individual VLAN is also disabled.
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
322 Chapter 13: Configuring Multicast
When IGMP snooping is enabled at the Global level, then IGMP snooping is
enabled on all VLANs and individual VLAN cannot be disabled. When Global
IGMP snooping is disabled, IGMP snooping on all VLANs is disabled by
default , but can be enabled on individual VLAN.
IGMP Snooping To configure the BBS 1000+ IGMP Snooping feature, you will perform the
Configuring Tasks following tasks:
Example Topology
Figure 109 IGMP Snooping Configuration
In the above figure, BBS 1000+ is connected to multicast source PC4 via uplink
port GE3/1. Downlink port OLT1/1 connects to ONU1-3 through a splitter. Port
GE3/1, GE1/1 and ONU1-3 belong to VLAN10. PC1 to PC3 each connect to
their corresponding ONU (ONU1-3). PC1-3 are all group members and expect
multicast traffic from BBS 1000+.
Configuration Requirements
1 BBS 1000+ PON ports OLT1/1 are assumed to run in stack-tag mode, and the
port is active.
2 ONU1, ONU2 and ONU3 are bound with the corresponding PON's lport.
Configuration Tasks The following IGMP snooping configuration tasks are described using the
topology example in Figure 109.
1 Create Service VLAN 10
2 Perform IGMP Snooping Service
3 Check IGMP group information on BBS 1000+
Login: admin
Password:*****
telnet@BBS1000+>enable
telnet@BBS1000+#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-10)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# no shutdown
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t-if-ge-3/1)# no shutdown
telnet@BBS1000+(config-t-if-ge-3/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
Port: The UDP port of the multicast stream which member expect to
receive
NIC: The IP address of PC2.
12 From the WSend window, right lick on the newly created group and select [
Start].
Figure 113 Initiate Multicast Group
14 The number of packets received by WListen (Figure 114) and sent by WSend
(Figure 113) are the same, this confirms that IGMP snooping is working on BBS
1000+.
Check IGMP group information on BBS 1000+
telnet@BBS1000+(config-t)# show ip igmp snooping vlan 10
IGMP Snooping on vlan 10 has 1 entries
IGMP Snooping on Vlan 10 is enabled.
Multicast Age Time : 180 seconds
Router Age Time : 180 seconds
Source Only Multicast Age Time: 300 seconds
Last Member Age Time : 1 seconds
The IP multicast group is:
-------------------------------------------------------------
225.1.1.1 10 dynamic ge1/1
To enable IGMP proxy on BBS 1000+, IGMP proxy should be configured on the
appropriate BBS 1000+ uplink L3 interface. The corresponding interface on the
upstream router should be running IGMP. All BBS 1000+ downlink interfaces
associated with a multicast group should be configured to run IGMP.
Figure 115 IGMP Proxy Configuration
When BBS 1000+ functions as a IGMP proxy, it performs the following tasks on
behalf of the host:
1 When queried, sends IGMP Reports to the specified group.
2 If a host wants to join a new group, it sends unsolicited Report message to the
new group.
3 When the last member of the particular wants to leave, it will send an unsolicited
Leave message to BBS 1000+.
IGMP Proxy Configuring To configure the BBS 1000+ IGMP Proxy feature, you will perform the following
Tasks tasks:
In order for multicast traffic to travel from source to destination nodes, ensure
that a PING message can pass between them.
On the upstream CISCO router, ensure that "IP multicast-routing" and "IGMP
version 2" for the associated interfaces are both activated.
IGMP Proxy configuration is described below using the topology in Figure 116
as an example.
Example Topology
Figure 116 IGMP Proxy Configuration
In Figure 116, BBS 1000+ connects to multicast source PC3 via uplink port
GE3/1. Downlink port OLT1/1 connects to ONU1-2 through a splitter. Port GE1/1
and ONU1-2 belong to the Super SVI, which has an IP address of 192.168.1.1.
PC1 and PC2 connect to ONU1 and ONU2, respectively. PC1 and PC2 are
members. They receive multicast traffic from BBS 1000+ using IGMP Proxy
Configuration Tasks The procedures for configuring IGMP Proxy are described below, using the
topology example in Figure 116.
1 Configure a Routed Interface
2 Start up PON Port OLT1/1
3 Configure Super SVI
4 Configure IGMP Proxy
5 Multicast is enabled on interfaceAdd host route
6 Perform IGMP Proxy Service
7 Check IGMP group information on BBS 1000+
Login: admin
Password:*****
telnet@BBS1000+>enable
telnet@BBS1000+#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-ge-3/1)# no switchport
telnet@BBS1000+(config-t-if-ge-3/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)#
telnet@BBS1000+(config-t-if-olt-1/1)# onu 1
telnet@BBS1000+(config-if-onu-1/1/1)# exit
telnet@BBS1000+(config-t-if-olt-1/1)#
telnet@BBS1000+(config-if-onu-1/1/2)# exit
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-olt-1/1)#
telnet@BBS1000+(config-t-if-olt-1/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-4094)# exit
telnet@BBS1000+(config-t-if-vlan-4094)# ip address
192.168.1.1 255.255.255.0
telnet@BBS1000+(config-t-if-vlan-4094)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-ge-3/1)# ip igmp-proxy
telnet@BBS1000+(config-t-if-ge-3/1)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-vlan-4094)# exit
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)#
12 From the WSend window, as shown in Figure 120, right-click on the newly
created entry and select [Start].
Figure 120 Initiate Multicast Packets
14 The number of packets received by WListen (Figure 121) and sent by WSend
(Figure 120) are the same, this confirms IGMP Proxy is working on BBS 1000+.
Check IGMP group information on BBS 1000+
1 Issue the following command to display all members of all IGMP groups.
telnet@BBS1000+(config-t)# show ip igmp groups
--------------------------------------------------
1/1 1 01:00:5e:01:01:01
telnet@BBS1000+(config-t)#
ACL Work Mode Currently two default actions are supported by the access control list: deny and
permit. These are the actions performed when traffic does not match any of the
specified ACL rules.
ACL Configuration There are two methods for defining and applying the ACL: Using ACL profile
Tasks and ACL CLI. When using ACL profile, we should import the ACL profile via
FTP.
ACL Configuration
Procedures
In the Forwarding mode, the ACL default action can be defined on the L2
ports.
4 Display ACL rules applied to all interfaces.
5 Disable the ACL profile on individual BBS 1000+ logical ports as required.
ACL Profile The BBS 1000+ database can store up to 32 ACL profiles and maintains only
Configuration one ACL running configuration per port.
An ACL profile is comprised of ACL field lists. Field lists are comprised of fields
and rules. A rule is the action to be performed when the incoming packet
matches the value of a specified field. An example ACL profile is shown below.
Each ACL profile must start with Profile start followed by a user defined Profile
Name. A profile description must end with profile end. Between the Profile
start and profile end lines, Field Lists and their related Rules are defined.
Field Lists and their related Rules are described below using the example field
list shown in Figure 123.
Up to 10 Field can be defined in an Field List, but each Field List must begin
with the field keyword followed by a user defined field list number, name and a
colon ":" character. Three fields are mandatory: (EtherII | 802.3, tag | untag
and IP | ARP). These fields define the Ethernet frame and packet type.
Besides these mandatory fields, other optional fields are defined.
When an incoming packet matches the type defined in the Field List, it is
compared with the defined Rules of the related Field List. If the conditions are
met then the Action is performed, either permit or deny as defined by the Rule.
In the following example, it is assumed that the ACL profile is applied to the
GE3/4 port.
If all the comparison conditions are "True", then the GE3/4 port will execute the
action defined in rule1 (in this example: the port will permit this packet to be
forwarded).
Specifying ACL Profiles ACL profiles must observe the following restrictions:
1 One profile can be applied to one or more logical ports; each logical port can be
configured with only one ACL profile. A new ACL profile will overwrite the old
ACL profile.
2 A maximum of 32 profiles can be stored in the database.
3 An ACL Field List can contain up to 10 different Field.
4 An ACL Field List must contain at least one ACL rule.
5 One profile can contain up to 80 rules (more than one rule can be defined for
each Field List).
6 The sequential order of the Field List in the ACL profile determines the field list
priority
7 Each Field List name and number must be unique within the ACL profile.
8 Each Rule name and number must be unique within an individual Field List.
9 Each text file can contain only one profile
10 A name defined for a Profile, Field List or Rule can be a maximum of 32
characters
Specifying ACL Fields An ACL profile can consist of up to 10 Field Lists. ACL fields define the incoming
packet condition to be monitored. When the incoming packet matches this
monitored condition the related rule(s) decide what action is to be taken.
Obviously a defined field condition without a matching rule would be pointless,
therefore each Field List must have at least one defined rule.
Example Field Lists for IP packets and ARP packets are described below.
Syntax explanation
All range-masks are represented in HEX format prefixed with "0x".
MAC address represented in the xx:xx:xx:xx:xx:xx format, where "xx" is in
HEX format.
Mandatory fields
The following mandatory fields are self contained and do not take an associated
rule.
field-number: User defined Field List number
field-name: User defined Field List name
EtherII | 802.3:Ethernet Frame Type
tag | untag: The Packet type, Tagged or Untagged
IP | ARP: Packet type
Optional fields
All optional fields specified in the field list require an associated rule.
Protocol: Keyword only, no parameters
Priority range-mask: If the Priority field is included in the field list, then it
must be preceded by the tag field
DSCP range-mask: If the DSCP field is specified, then the IP field must be
included in the field list.
SrcPort range-mask | DstPort range-mask : SrcPort and DstPort fields are
only valid for TCP and UDP packets
vlan range-mask
sip range-mask
dip range-mask
smac range-mask
dmac range-mask
Field List Example using The following Field List explanations for IP type packets are based on the Field
IP Packets List example below.
DSCP Field
In this DSCP example a non-default range is used, "DSCP 0x38". This
indicates that the DSCP range-mask is 0x38.
Using the number of zeros in "111000" (three), the DSCP range is calculated as
23 or 8. This means that any incoming packet's DSCP value, within a range of
eight starting from the value specified in the associated Field List Rule, will
match the rule.
The range of possible Rule List values is the same as for the Field List. For
DSCP this is 0x0-0x3F. The valid Rule List values start at 0x00 and go up to
0x3F, in increments equal to the Range Mask defined in the related Field List, in
this example 0x38, which equals eight. So, valid DSCP Rule List values with a
Range Mask of 0x38 are 0, 8, 16, ... 48, 56.
In the following example packets with DSCP values from 0x30 (48) to 0x37 (55),
will be forwarded.
According to the DSCP range-mask defined in the Field List (0x38), valid DSCP
Rule values are listed in Table 58.
When the ACL profile is imported, the system will validate the rules. Only valid
rules will be accepted.
Sip Field
In this example the SIP range mask is "sip 0xFFFFFFC0" which is equal to
binary 1111,1111,1111,1111,1111,1111,1100,0000. Using the number of zeros in
this binary number (six), the SIP range is calculated as 26 or 64. This means
that the packet's source IP address must be within a range of 64, starting from
the SIP address specified in the associated Field List Rule, to satisfy the rule.
The range of possible Rule List values is the same as for the Field List
(0x0-0xFFFFFFFF) with the exception of "0x0", which is not a valid SIP rule
value. The valid SIP rule values must be a multiple of the range value specified
in the associated Field List.
In the following example packets with a SIP address between 5.1.1.0 and
5.1.1.63 inclusive, will be forwarded.
When the ACL profile is imported, the system will validate the rules. Only valid
rules will be accepted.
According to the SIP range-mask defined in the Field List (0xFFFFFFC0), valid
SIP rule values are listed in Table 59.
Table 59 Valid SIP Rule values based on a SIP mask
The rules for specifying DIP fields and rules are the same as those for SIP fields
and rules.
Field List Example using The following Field List will be used as an example to describe Fields related to
ARP Packets ARP type packets.
In this example, some fields such as priority, sip, dip are the same as in the
section above and will not be described again. Other fields such as VLAN,
smac, dmac will be described below.
VLAN Field
"VLAN 0xFF0" in the example indicates a VLAN range-mask of 0xFF0.
This means that any packets with a VLAN ID within a range of 16 starting from
the value specified in the associated Field List Rule, will satisfy the rule.
The range of possible VLAN Rule List values is the same as for the related Field
List (0x000-0xFFF), with the exception of 0x000. The range of valid VLAN Rule
values is from 0x001 to 0xFFF, in increments equal to the Range Mask defined
in the related VLAN Field, in this example 0xFF0, which equals 16. So, valid
VLAN Rule values with a Range Mask of 0xFF0 are 0, 16, 32, ... 4064, 4080.
In the following example, packets with a VLAN ID between 4064 and 4095
inclusive, will be forwarded.
According to the VLAN range-mask defined in the Field List (0xFF0), valid VLAN
Rule values are listed inTable 60.
When the ACL profile is imported, the system will validate the rules. Only valid
rules will be accepted.
Binary
Valid VLAN ID Rule Values Equivalent Range of Matching VLAN Values
DEC Hex Bin Dec
0 0x0 0000,0000,0000 0~15
16 0x10 0000,0001,0000 16~31
... ... ...
4064 0xFE0 1111,1110,0000 4064~4079
4080 0xFF0 1111,1111,0000 4080~4095
SMAC Field
In this example, the SMAC Field range mask is "FF:FF:FF:FF:FF:FF". Since
there are no zeros in the binary format of this value, the SMAC range is equal to
20 or 1. This means that only the SMAC defined in the associated Rule will be
matched.
The range of possible SMAC Rule values is the same as for the SMAC Field (00
- FF:FF:FF:FF:FF:FF), with the exception of 00. Valid SMAC Rule values must
be a multiple of the range specified in the SMAC Field range-mask. In this
example the SMAC range is equal to one(1), so any value up to
FF:FF:FF:FF:FF:FF is valid.
DMAC Field
In this example, the DMAC Field range mask is " FF:FF:FF:FF:FF:00". The
binary form of this value has eight zeros, so the DMAC range is equal to 28 or
256. This means that any packet's DMAC value, within a range of 256 from the
value specified in the associated Field List Rule, will satisfy the rule.
According to the DMAC range-mask defined in the Field List, valid DMAC Rule
values are listed in Table 61.
When the ACL profile is imported, the system will validate the rules. Only valid
rules will be accepted.
Specifying ACL Rules An ACL profile can contain up to 80 rules. Rules defined for a Field List must be
related to the Fields defined in the Field List.
The valid rule values in the table above, must be equal to a multiple of the range
defined in the related Field's range-mask. (Example: For a DSCP with a range
of 8, valid rule values can be 0, 8, 16, 24 ...)
Syntax explanation
All rules must begin with the rule keyword
The user defined rule-number and rule-name are both mandatory and must
be unique within an individual Field List.
The etherII, 802.3, tag, untag, ip and arp fields do not require a rule, but
all other fields must have a related rule.
Protocol rules take effect only if the Protocol keyword is specified in the
related field list.
All parameter values configured in the rule list can use either Decimal or HEX
numbers
The following rules all require an associated parameter
SIP IP-address
DIP IP-address
SrcPort port-value
DstPort port-value
VLAN vlan-value
Priority prio-value
SMAC sourceMAC
DMAC destinationMAC
The previous rules requiring associated parameters, are all dependant on the
related Field's range mask. Using sip IP address for example: If a range
mask of "0xFFFFFFFF" was specified, then only one IP address will match,
i.e., the IP address specified in the rule. Otherwise, a range of IP addresses
will match the rule depending on the range-mask defined.
The SrcPort and DstPort rules are only valid for TCP or UDP protocols.
When the rule's action is defined as remark_dscp, remark_prio, or
rate_limit, then the DCSP, Priority or Bandwidth value can be reset to a new
value, using the corresponding new_dscp <0-63> | new_priority <0-7> |
bandwidth <1-1000> [burst-size <4|8|16|32|64|128|256|512>]
The new bandwidth defined above is in Mbps and Priority refers to the CoS
value.
By applying the previous ACL field list, packets matching all of the following
conditions will be dropped (deny):
The packets are EtherII type
They are tagged packets
The VLAN tag contained in the packet is 4
The COS value of the packet is 3
The packets are ARP type
Packets matching all of the following conditions will have their DSCP value reset
to 52:
The packet is EtherII type
They are tagged packets
The VLAN tag contained in the packet is 5
The packet is an IP type
The packet protocol type is TCP
The source IP address is in the 172.16.4.0/24 network segment
The destination IP address is in the 200.10.7.0/24 network segment
These ports can be used by a virus or hacker to attack the system. When a
non-fragmented packet has a frame flag value of "0" it is assumed to be a virus,
and the packet is dropped.
To disable the ACL default action use the No form of the command, i.e., no
acl-default-action pre-configuration.
Example:
To disable IPMC filtering use the "No" form of the command, i.e., no ip
multicast filter.
Example:
1 Enable IPMC filtering on the GE3/1 interface of the BBS 1000+ system.
telnet@BBS1000+(config-t-if-ge-3/1)# ip multicast filter
IPMC Filtering is always used on downlink GE ports to block packets from ONUs
with specific formats.
ACL Profile Configuring This section describes how to create an ACL profile. The main steps involved,
Example are shown below:
1 Determine the application's specific ACL profile requirements.
2 Define the ACL Rules (to implement the previous requirements).
3 Create the ACL Profile.
In this example an ACL needs to be created that will perform the following
functions:
Only allow telnet connections with BBS 1000+ from IP address
192.168.103.37
Allow in-band management of BBS 1000+ via uplink port GE3/1
GE3/1 is configured as an SVI with an IP address of 40.0.0.10 and the
management VLAN ID is 400, so only allow packets tagged with a VLAN
ID of 400
Only allow packets with a destination port number of 23 (telnet)
If the packets match the following conditions, then they will be permitted.
Packets are EtherII type
Packets are IP type.
Protocol type of the packets is TCP
VLAN ID of the packets is 400.
Source IP address of the packets is 192.168.103.37/24.
Telnet packet destination port is 23.
profile end
After the ACL profile is defined, it should be uploaded to the BBS 1000+ system
and applied on the CPU interface from the Configure Management command
mode.
In the current version, management ACL only supports src/des IP, src/des port,
and protocol type.
Example Topology
Figure 125 ACL Topology Example
In this example an ACL will be defined to deny a specific Cisco switch interface
(IP address 5.1.1.2/24 on port g1/0/25) access to BBS 1000+'s GE3/1 port.
Configuration Tasks The tasks involved in configuring an ACL are given below, using the topology
Using ACL Profile example in Figure 125.
3750>
3750>enable
Password:******
3750#configure terminal
3750(config-if)#no switchport
3750(config-if)# no shutdown
3750(config-if)#exit
3750(config)#exit
3750#
Building configuration...
[OK]
3750#
1 Login to the BBS 1000+ and enter the Configure Terminal command mode.
c:\> telnet 192.168.103.227
Login: admin
Password:*****
telnet@BBS1000+>
telnet@BBS1000+>configure terminal
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-ge-3/1)#
telnet@BBS1000+(config-t-if-ge-3/1)# no switchport
telnet@BBS1000+(config-t-if-ge-3/1)# no shutdown
4 Display the configuration information for the BBS 1000+ GE3/1 port.
telnet@BBS1000+(config-t-if-ge-3/1)# show interface
giga-ethernet 3/1
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config)#
telnet@BBS1000+(config-mgmt)#
..
In this example "gepon" and "geponbbs" are the FTP server user name and
password respectively.
-------------------------------------------------
1024 JUL-27-2020 00:35:40 <DIR> onuImage
3546308 JUL-27-2020 05:01:32 BBS1000plus.stz
28 JAN-01-1980 00:00:02 sysInfo
325 JUL-27-2020 00:46:28 access.txt
telnet@BBS1000+#
2 Import the ACL file (access.txt) to Profile 1 from the Configure Terminal
command mode.
In the following example, it is assumed that a previous "Profile 1" does not exist
in the BBS 1000+ database.
telnet@BBS1000+(config-t)#
...Done!
telnet@BBS1000+(config-mgmt)#
telnet@BBS1000+(config-mgmt)#
3 Verify that ACL profile (1) was successfully applied to the port.
BBS1000+(config-t-if-ge-1/2)# show acl-applied-interface
.....
After disabling the ACL profile, the profile is not applied on the BBS 1000's CPU
interface..
3750#ping 5.1.1.1
!!!!!
telnet@BBS1000+(config-mgmt)#exit
telnet@BBS1000+(config-t)# clear-database-acl 1
Configuration Tasks The tasks involved in configuring an ACL are given below, using the topology
Using ACL CLI example in Figure 125.
The tasks 1,2,5,6,7 are the same as the configuration tasks described in the
above section, so only the task 3,4,8 are listed below.
...Done!
...Done!
telnet@BBS1000+(config-ext-nacl)#
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t)# exit
telnet@BBS1000+(config-mgmt)#
After apply the ACL file to the CPU interface, the ACL rule is saved in the
database as ACL profile.
telnet@BBS1000+(config-mgmt)#exit
Example Topology
Figure 126 Configure ACL for Forwarding packets
In Figure 126, BBS 1000+ connects to port g1/0/25 of Cisco 3750 via uplink port
GE3/1. A FTP server is connected to the BBS 1000+'s out-band Management
port. Downlink port GE1/1 is a member of Super VLAN 500. The VLAN of
ONU1 is a member-VLAN of Super VLAN 500. Super SVI 500's IP address is
4.1.1.1/24. PC1 connects to BBS 1000+ through ONU1.
Define an ACL profile on BBS 1000+ to deny PC1's visit to Cisco 3750.
Configuration Tasks The tasks involved in configuring ACL for forwarding packets are described
Using ACL Profile below, using the topology example in Figure 126.
3750>
3750>enable
Password:******
3750#configure terminal
3750(config-if)#no switchport
3750(config-if)#no shutdown
3750(config-if)#exit
3750(config)#exit
3750#
Building configuration...
[OK]
3750#
1 Login to the BBS 1000+ and enter the Configure Terminal command mode.
c:\> telnet 192.168.103.227
Login: admin
Password:*****
telnet@BBS1000+>
telnet@BBS1000+>configure terminal
Doc. Code L2 CO00 2321 06 15 00 GEPON OLT BBS 1000+
June 2007 CLI Operation Guide
370 Chapter 14: Configuring ACL
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-if-ge-3/1)#
telnet@BBS1000+(config-t-if-ge-3/1)# no switchport
telnet@BBS1000+(config-t-if-ge-3/1)# no shutdown
4 Display the configuration information for the BBS 1000+ GE3/1 port.
telnet@BBS1000+(config-t-if-ge-3/1)# show interface
giga-ethernet 3/1
telnet@BBS1000+(config-t)#
telnet@BBS1000+(config-t-vlan-500)# exit
telnet@BBS1000+(config-t-if-vlan-500)# no shutdown
Member: 101
telnet@BBS1000+(config)#
telnet@BBS1000+(config-mgmt)#
2 Download the ACL profile named "access.txt" to the BBS 1000+'s flash:/
directory. (In this example "gepon" and "geponbbs" are the FTP user name and
password respectively.
telnet@BBS1000+(config-mgmt)# ftp 192.168.103.100 get gepon
geponbbs flash:/access.txt access.txt
..
3 Verify that the ACL profile downloaded successfully to the BBS 1000+'s flash:/
directory.
telnet@BBS1000+(config-mgmt)# file-system list flash:
-------------------------------------------------
telnet@BBS1000+#
2 From the Configure Terminal command mode, import the file "access.txt" to the
BBS 1000+ ACL Profile.
In the following example, it is assumed that a previous "Profile 2" does not
already exist in the BBS 1000+ database.
telnet@BBS1000+(config-t)#
...Done!
profile end
telnet@BBS1000+(config-t-if-ge-1/1)# apply-acl-profile 2
2 Verify that the ACL profile (2) was successfully applied to the port.
BBS1000+(config-t-if-ge-1/1)# show acl-applied-interface
-----------------------------------------------------------
ge1/1 2 1 1
C:\>ping 5.1.1.2
-----------------------------------------------------------
telnet@BBS1000+(config-t-if-ge-1/1)#
C:\>ping 5.1.1.2
telnet@BBS1000+(config-t-if-ge-1/1)#exit
telnet@BBS1000+(config-t)# clear-database-acl 2
Configuration Tasks The tasks involved in configuring ACL for forwarding packets are described
Using ACL CLI below, using the topology example in Figure 126.
The tasks 1,2,3,4,7,8,9 are the same as the configuration tasks described in the
above section, so only the tasks 5,6,10 are listed below.
telnet@BBS1000+(config-ext-nacl)#
...Done!
telnet@BBS1000+(config-ext-nacl)#
telnet@BBS1000+(config-ext-nacl)#
telnet@BBS1000+(config-t-if-ge-1/1)# apply-access-list
BBS_Uplink
telnet@BBS1000+(config-t-if-ge-1/1)#
2 Verify that the ACL list was successfully applied to the port.
telnet@BBS1000+(config-t-if-ge-1/1)# show
acl-applied-interface
telnet@BBS1000+(config-t-if-ge-1/1)# exit
BBS 1000+ QoS This chapter describes how to configure Quality of Service (QoS) in BBS 1000+
Overview to select specific network traffic, prioritize it according to its relative importance.
Implementing QoS in BBS 1000+ to avoid bottlenecks congestion makes
network performance more predictable and bandwidth utilization more effective.
In a typical BBS 1000+ network as depicted in Traffic Bottlenecks, there are two
bottlenecks for the upstream traffic. One is at the 2 Gigabit uplink interface,
because if fully populated there are 8 Gigabit traffic go to uplink. The other is on
each OLT port. Because each OLT interface can connect up to 32 ONUs, on
average each ONU's traffic should be limited to 31.25Mbps. For downstream
traffic, the bottleneck is at the OLT interface, for a specific ONU, the traffic
should be limited to the bandwidth allocated to it, the default max bandwidth for
specific ONU is 100M.
To implement QoS, the switch must be able to distinguish different packets. This
is so called classification. The classification can be carried in Layer 2 frame or
Layer 3 IP packet header.
The Layer 2 frame that carries QoS classifications are 802.1Q frames with
802.1p class of service (CoS) priority bits defined.
Figure 128 802.1 Q Frame
TPID (Tag Protocol ID) has a defined value of 0x8100, which indicates the
tag header is presented in the frame. TCI (Tag Control Information) follows
the TPID field, which includes 3 bits of user priority field. The 3 bits can give 8
levels of CoS (Class of Services) with 0 as the lowest priority and 7 as the
highest.
Layer 3 IP packet header can carry either an IP precedence value or a
Differentiated Services Code Point (DSCP) value.
Figure 129 original ToS Field and DSCP Field
For Policing and Marking are not related with QoS Configruation in the BBS
1000+, here ignores these two QoS actions intrudction.
Classification
During classification, BBS 1000+ performs lookup and assigns QoS label to the
packet. The options are:
1 Trust the DSCP value in the incoming packet (configure the port to trust DSCP),
and assign the same DSCP value to the packet.
Modify the DSCP to another value by using the configurable
DSCP-to-DSCP-mutation map.
2 Trust the IP precedence value in the incoming packet (configure the port to trust
IP precedence), and generate a DSCP value for the packet by using the
configurable IP-precedence-to-DSCP map.
IP Precedence 0 1 2 3 4 5 6 7
DSCP 0 8 16 24 32 40 48 56
3 Perform the classification based on ACL (Access List), which examines various
fields in the IP header. If no ACL is configured, the packet is assigned 0 as the
DSCP and CoS values, which means best-effort traffic.
Queue 0 to 2 are running in WRR mode. Strict Priority queue is always being
served first. Each queue can be configured to run in Strict priority mode by set
the queue weight to 0. And each queue can be configured to run in WRR mode
by set the weight from 1 to 0xF to the queue.
In BBS 1000+ default DSCP to CoS map is disabled, i.e. all DSCP packets has
the CoS priority of 0. When QoS is enabled, the default DSCP to CoS map is:
d1 : d2 0 1 2 3 4 5 6 7 8 9
---------------------------------------
0 : 0 0 0 0 0 0 0 0 1 1
1 : 1 1 1 1 1 1 2 2 2 2
2 : 2 2 2 2 3 3 3 3 3 3
3 : 3 3 4 4 4 4 4 4 4 4
4 : 5 5 5 5 5 5 5 5 6 6
5 : 6 6 6 6 6 6 7 7 7 7
6 : 7 7 7 7
We use DSCP to CoS map to generate a CoS value, which is used to select one
of the four egress queues. The mapping can also be modified.
Table 66 BBS 1000+ Default CoS Priority to Queue Map
0 1 2 3 4 5 6 7
CoS Priority
CoS Queue 0 0 1 1 2 2 3 3
CoS Queue 0 1 2 3
Weight 4 8 12 0
QoS Configuring Configure under GE interface, Link Aggregation interface and interface range.
Commands
Table 68 QoS Configuring Commands
QoS Configuring
Procedure
profile end
There may be some conflicts between ACL remark configuration and mls
qos maps. ACL remark rules have higher priority than mls qos maps table.
So if there are the conflicts, the system will use ACL remark rules instead of
Application Description The following example only to demonstrate QoS working mechanism.In theGE
port send large amount data to the GEPON system. And in the downlink ports
set rate limit to control the output rate (to ONU). This will make BBS 1000+
system's downlink become a bottleneck. Then one can observe ONU site's data
flow receving condition and therefore analyze whether QoS works.
In the BBS 1000+ system's GE port GE3/2 send 32 data flows. The total rate is
1000Mbps. Every 8 data flows (250Mbps) are set to priority 0-7 an d sent to
ONUs. In the downlink port GE1/1 set output's rate-limit as 200Mbps, The total 8
data flows have a rate of 250M. This will form bottleneck at port GE1/1's output
direction.
Giga-ethernet 3/2
Trust admin state: ip-precedence
Trust mode: ip-precedence
trust enabled flag: enabled
Qos is using self configuration!
Qos Enabled flag: enabled
Qos DSCP Map: enabled
Qos Map trust mode: ip-precedence
.. screen output truncated...
Giga-ethernet 1/1
Result Analyze
The GE port sends 1000Mbps data to GEPON system, the ONU receiving result
is
1 The receiving data rate for each ONU is 50Mbps.
2 The priorities of those 50Mbps are 6 and 7.
Since BBS 1000+ system bandwidth bottleneck, the system will activate QoS to
make sure that higher priority data will be forwarded. And lower priorities data
migh get discarded.
User Account Local CLI user accounts can be created, modified, maintained and deleted by
Management the system administrator. A user account consists of a user name, password
and an access (privilege) level. The four BBS 1000+ access levels are listed
below.
0------Read-Only
1------Port-Config (port)
2------Super User (write) (all operations excluding user account
management)
10----System Administrator (all operations including user account
management)
The access level controls which CLI interfaces and related commands are
available to the user.
The default system administrator's account and password are: admin and
admin.
Each CLI command is also assigned an access level. A user must have an
equal or higher access level to perform the related command. The command
levels are listed below:
0------Read-Only level command (These commands only display information
and cannot be used to modify the system)
1------Port-Config level command (These commands can be used to add,
modify and delete port level configurations)
2------Super User level command (These commands can be used to perform
all operations with the exception of account management)
10----System Administrator (These commands can be used to modify the
entire system including login and account management)
User Management The following user configuration tasks are described below:
Operations
Table 69 User Management Commands
After entering this command and pressing Enter, the system will prompt "Enter
new password" and "Confirm new password" enter the new password, and then
press Enter.
telnet@BBS1000+(config-mgmt)#
success
Password: ******
telnet@BBS1000+>
telnet@BBS1000+(config-mgmt)#
success
User Access
----------------------+---------
Myoperator 2
admin 10
Username:Myoperator
Password:******
telnet@BBS1000+>
Delete a user
Only administrator can delete user account on the BBS 1000+.Here we assume
to delete the user Myoperator.
1 Enter Management Configure command mode.
telnet@BBS1000+> enable
telnet@BBS1000+(config-mgmt)#
2 Delete a user.
telnet@BBS1000+(config-mgmt)# user delete Myoperator
User Access
----------------------+---------
admin 10
File Management This section describes how to manage configuration files and software image
files. Configuration parameters of the device are saved in the configuration file.
Software image file is indispensable for switch running, and cannot be modified
in the system normal running process except version upgrade.
System Start Up Method When the BBS 1000+ system starts up it can get the image file using one of the
following two methods:
BBS 1000+ Flash Memory: Start up the system via the image file
(BBS1000plus.stz) in the BBS 1000+ Flash memory.
FTP Server: Start up the system via an image file (BBS1000plus.st) on the
FTP Server.
During the system boot up process, if the system cannot get the image file or for
any reason the boot up process is interrupted, the [VxWorks Boot]: prompt will
be displayed.
[VxWorks Boot]: p
During system failure, connection to the BBS 1000+ system must be made via
the Console port .
System File Introduction Under a normal BBS 1000+ system, user can check the system file directory via
command file-system list. The system's root directory is flash: and nvm:
Firmware Upgrade The following procedures describe the process when a system firmware
Procedure upgrade or re-installation is required.
The firmware package which is normally copied to the local management PC.
Table 72 describes the files and folder in the firmware upgrade package.
Table 72 Firmware Upgrade Files and Destination Folders
Destination Directory on
File Name Description the BBS1000+
bootrom_uncmp.bin BBS1000+ Bootrom file flash:
onu.bin ONU Bootrom file flash:/onuImage
BBS1000plus.stz BBS1000+ image file flash:
BBS1000plus.st BBS1000+ image file ftp server:
BBS1000plus_Release_Notes.doc upgrade guide
Normally the management PC functions as an FTP server and the firmware files
are located on the PC, as shown Figure 132:
Figure 132 Firmware update files on the management PC
For security concern, user might first to do backup for system configuration file
epon.db which is located in directory nvm:/cfgdata.
Example Topology
Figure 134 Example Firmware Upgrade Topology
Pre-Upgrade Requirements
1 The BBS 1000+ system can boot up normally. (If not refer to VxWorks
Configuration After System Failure on page 398.
2 The management PC can telnet the BBS 1000+ system via In-band.
Configuration Tasks The following tasks should be performed to configure the system as shown in
the topology in Figure 134.
1 Configure FTP Server
2 Configure BBS 1000+
3 Click the FTP Server button the left side of of the 3CDaemon window.
4 Click the Configure FTP Server icon, to open the 3CDaemon Configuration
window, as shown in Figure 136.
5 Select the FTP Profile tab page and then set the following parameters to create
a new profile:
Profile Name: gepon
User's password: geponbbs
User Directory: Directory where the firmware image files are saved. For
example, d:\Gepon
When using different FTP server software, refer to the related software
manuals.
Configure BBS 1000+
1 Log in to BBS 1000+ as a user with administration privileges, then enter the
following commands to access the CONFIG Management command mode.
BBS1000+>enable
BBS1000+#
BBS1000+(config-mgmt)#
Check the BOOTROM version number, if the BOOTROM version is the same
as the new image file as listed in the Release_Note.doc file, then skip step 3.
Otherwise, upgrade the BOOTROM File first. (In this example the previous
version is 01.00.00.000 but the upgrade version is 01.03.01.000).
3 Upgrade the BOOTROM file by downloading it from the FTP server to the BBS
1000+ Flash memory, using the bootrom-update command.
4 (In the following command the first parameter is the FTP host IP address,
"gepon" is the user's name, "geponbbs" is the user's password and
"bootrom_uncmp_BBS1000plus.bin" is the filename of the new BOOTROM file.)
BBS1000+(config-mgmt)# bootrom-update 192.168.103.37 gepon
geponbbs bootrom_uncmp_BBS1000plus.bin
.................................
Before upgrading the image file, is recommended to back up the previous image
file. This can be performed using one of the following methods:
Save it in the Flash memory: Due to the limited capacity of BBS 1000+ Flash
memory, this is not recommended.
Save it on the FTP Server.
Follow the step below to save the previous image file to the FTP Server.
1 Upload the previous image files to the FTP server using the ftp command.
2 (In the following command the first parameter is the FTP host IP address, "put"
indicates a FTP upload action, "gepon" is the user's name, "geponbbs" is the
user's password, "BBS1000plus.stz" is the local Bootrom path and filename on
BBS 1000+, and "BBS1000plus_1.0.1.stz" is the remote filename on the FTP
server.)
BBS1000+(config-mgmt)# ftp 192.168.103.37 put gepon geponbbs
flash:/BBS1000plus.stz BBS1000plus_1.0.1.stz
3 Download the new image file from the FTP server to the BBS 1000+ Flash
memory using the ftp command.
4 (In the following command the first parameter is the FTP host IP address, "get"
indicates a FTP download action, "gepon" is the user's name, "geponbbs" is the
user's password, "BBS1000plus.stz" is the local Bootrom path and filename on
BBS 1000+, and "BBS1000plus.stz" is the remote filename on the FTP server.)
BBS1000+(config-mgmt)# ftp 192.168.103.37 get gepon geponbbs
flash:/BBS1000plus.stz BBS1000plus.stz
5 Verify that the newly downloaded image file can be found in the BBS 1000+
flash: directory.
telnet@BBS1000+(config-mgmt)# file-system list flash:
Run the following command if the boot file name is diffrent from the new image
file in the BBS1000+ Flash memory.
BBS1000+(config-mgmt)# boot system flash BBS1000plus_New.stz
8 Verify the upgraded version information, particularily the first line, as shown
below.
BBS1000+# show version
During the upgrade process, if a problem is encountered and the system will
not boot up, refer to the following section: VxWorks Configuration After
System Failure
VxWorks When the system image file will not load or the system boot up process is
Configuration After interrupted, the system will enter the [VxWorks Boot]: prompt.
System Failure
This section describe how to configure BBS 1000+ under the Vxwoks command
mode, therefore BBS 1000+ can boot up normally. For upgrading the BBS
1000+, please refer to the above section "Firmware Upgrade Normally In-band".
1 During system failure or when the boot up process is interrupted, BBS 1000+
enters the [VxWorks Boot]: mode as displayed below:
[VxWorks Boot]:
3 In the next example the "p" command is issued to display the current system's
start up parameters:
[VxWorks Boot]: p
Application Description After a system failure, the following example procedure can be performed to
re-establish a connection with the FTP server and upgrade the BBS 1000+
firmware and image file.
When the system has failed or the boot up process has been interrupted, the
Console port is the only port that can be accessed on the BBS 1000+. In the
following example an Out-band connection will be established with the BBS
1000+. Then the system boot parameters will be configured and BBS 1000+ will
be restarted. The system will now boot up from the FTP server connected to the
Out-band Management port, as shown in Figure 138.
Configuration Tasks The tasks below must be performed to establish a connection with the FTP
server, as shown in Figure 138.
1 Set up FTP Server
2 Configure the BBS 1000+ system boot parameters
[VxWorks Boot] :
1 To change the system boot parameters, type "c" and then press Enter, as
shown below.
[VxWorks Boot] :c
2 The boot device parameter is displayed. Enter "motfcc" which is the FTP
server's device ID and press Enter, as shown below.
boot device: flash motfcc
3 For the next two parameters no modification is required, so press Enter two
times to skip these parameters.
processor number: 0 < press Enter>
4 The file name parameter is displayed. Enter the name of the Image file on the
FTP server (BBS1000plus.st) and then press Enter.
file name: BBS1000plus.st
5 The inet on ethernet parameter is displayed. Enter the IP address of the BBS
1000+ out-band Management port, and then press Enter.
inet on ethernet (e): 192.168.103.199
6 The host inet parameter is displayed. Enter the IP address of the FTP server,
and then press Enter.
host inet (h): 192.168.103.37
8 The user parameter is displayed. Enter the user name, and then press Enter.
user (u): gepon
9 The ftp password parameter is displayed. Enter the password, and then
press Enter.
To remove a password, enter the VxWorks Boot command "." (a period) to
clear the field, and then press Enter.
10 ftp password (pw): geponbbs
11 The last four parameters do not need to be configured, so press Enter four times
to skip these.
flags (f): 0x0 < press Enter>
12 When all the parameters are configured, the following prompt will display.
Press @ and then Enter, to resume the start up process.
[VxWorks Boot]: @
13 The system should now continue to boot up normally. Enter the user name and
password to enter the CLI EXEC command mode, as shown below.
telnet@BBS1000+>
telnet@BBS1000+#
telnet@BBS1000+(config-mgmt)#
15 From the config-mgmt prompt enter the show boot attributes command to
display the boot parameters, as shown below.
BBS1000+(config-mgmt)# show boot attributes
16 The system has now successfully booted from the FTP server. The BBS 1000+
system firmware can now be upgraded. Refer to Firmware Upgrade Normally
In-band Management on page 393.
CO Central Office
HOL Head-Of-Line
IP Internet Protocol
LG Link Aggregation
Headquartered in the United States with sales, support, and manufacturing facilities worldwide, UTStarcom designs, manufactures, sells, and installs an
integrated suite of wireless and wireline access network and switching systems. UTStarcoms complete suite of network equipment gives telecommunication
service providers the means to cost-effectively provide efficient and scalable voice, data, and Internet services around the globe.
Copyright 2006-2007 UTStarcom, the UTStarcom logo, !-Volution, AIRSTAR, AN-2000, AN-FTTB, CommWorks, the CommWorks logo, iAN, iCell, Internode,
Intranode, iPATH, ISP, MovingMedia, mSwitch, Next Generation Network Technology. Now, NGDLC, PAS, PAS Wireless, Seamless World, Softexchange,
Sonata, Sonata Access Tandem, Sonata HLR, Sonata IP, Sonata MSC, Sonata WLL, Telos, Total Control, Unitech, WACOS, WICOPS, WLL, and Xtreme IP are
registered trademarks or trademarks of UTStarcom, Inc. and its subsidiaries.