IP6510 v8 M

IP6510 Multiple WAN
Router/Bridge
USER'S MANUAL
LOOP TELECOMMUNICATION INTERNATIONAL, INC.

8F, NO. 8, HSIN ANN RD.
SCIENCE-BASED INDUSTRIAL PARK
HSINCHU, TAIWAN
Tel: +886-3-578-7696
Fax: +886-3-578-7695
 2014 Loop Telecommunication International, Inc. All rights reserved.
Version 8 May 15, 2014
ii
TABLE OF CONTENTS
1 PRODUCT DESCRIPTION ...................................................................................................................... 1
1.1 DESCRIPTION ..................................................................................................................................... 1
1.2 APPLICATIONS ........................................................................................................................................... 2
1.3 SPECIFICATIONS ........................................................................................................................................ 3
2 INSTALLATION ........................................................................................................................................ 6
2.1 SITE SELECTION ................................................................................................................................. 6
2.2 MECHANICAL INSTALLATION ................................................................................................................ 6
2.2.1 Power ........................................................................................................................................... 7
2.2.2 E1/ T1/Ethernet Card Description ................................................................................................ 7
2.2.2.1 Jumper Settings ....................................................................................................................... 8
2.2.2.2 E1/T1 pin assignment .............................................................................................................. 9
2.3 FRONT PANEL CONSOLE PORT AND LEDS ........................................................................................ 10
2.3.1 Console Port .............................................................................................................................. 10
2.4 LED OPERATION .............................................................................................................................. 10
2.5 ETHERNET CONNECTION................................................................................................................... 11
3 OPERATION ........................................................................................................................................... 12
3.1 POWER ON ...................................................................................................................................... 12
3.2 USING A VT-100 TERMINAL .............................................................................................................. 12
3.2.1 VT-100 Monitor Serial Port Setup .............................................................................................. 12
3.3 LOGIN, SET TIME AND DATE AND LOGOUT ......................................................................................... 13
3.3.1 Overview .................................................................................................................................... 13
3.3.2 Login .......................................................................................................................................... 13
3.3.3 Password ................................................................................................................................... 14
3.3.4 Show System Date/Time and Change It .................................................................................... 14
3.3.5 Logout ........................................................................................................................................ 14
3.4 Interface Naming Rule ............................................................................................................... 14
3.5 Assigning Timeslots To A WAN Port ......................................................................................... 15
3.6 CONFIGURATION............................................................................................................................... 15
3.7 REMOTE MANAGEMENT .................................................................................................................... 15
3.7.1 SNMP ......................................................................................................................................... 15
3.7.2 SSH ............................................................................................................................................ 16
3.8 VERIFYING LOOP-IP6510 OPERATIONS ............................................................................................. 16
3.8.1 Independent Test ....................................................................................................................... 16
3.8.2 Substitution ................................................................................................................................ 17
3.8.3 Using the Bert Test Set .............................................................................................................. 17
4 REMOTE BRIDGE SETUP OVERVIEW ................................................................................................ 18
4.1 OVERVIEW ....................................................................................................................................... 18
4.2 STEP BY STEP SETUP INSTRUCTIONS ................................................................................................ 19
5 PPP/MLPPP............................................................................................................................................ 20
5.1 OVERVIEW ....................................................................................................................................... 20
6 VLAN....................................................................................................................................................... 22
6.1 OVERVIEW ....................................................................................................................................... 22
6.2 EXAMPLE SETUP .............................................................................................................................. 22
6.2.1 Application #1 (Fig. 6-1) Step by Step Setup Instructions .......................................................... 22
6.2.2 Application #2 (Fig. 6-2) Step by Step Setup Instructions .......................................................... 24
6.3 VLAN AND PORT TABLES ................................................................................................................. 26
6.3.1 VLAN Table ................................................................................................................................ 26
6.3.2 VLAN Port Table ........................................................................................................................ 27
7 VLAN STACKING (Q-IN-Q) SETUP....................................................................................................... 27
7.1 OVERVIEW ....................................................................................................................................... 27
iii
7.2 VLAN STACKING .............................................................................................................................. 28
7.3 DEFINITIONS..................................................................................................................................... 29
7.4 SETUP EXAMPLE .............................................................................................................................. 29
8 FRAME RELAY SETUP ......................................................................................................................... 31
8.1 OVERVIEW ....................................................................................................................................... 31
9 NAT / NAPT ............................................................................................................................................ 33
9.1 OVERVIEW ....................................................................................................................................... 33
9.2 EXAMPLE AND SETUP INSTRUCTIONS ................................................................................................. 33
9.3 PORT FORWARDING EXAMPLE AND INSTRUCTIONS ............................................................................. 35
10 STP/RSTP SETUP ................................................................................................................................. 36
10.1 OVERVIEW ....................................................................................................................................... 36
11 QOS (QUALITY OF SERVICE) .............................................................................................................. 41
11.1 OVERVIEW ....................................................................................................................................... 41
11.2 POLICY SYNTAX................................................................................................................................ 41
10.2.1 Policy add .............................................................................................................................. 41
10.2.2 Policy delete........................................................................................................................... 42
10.2.3 Policy display ......................................................................................................................... 42
12 OSPF SETUP ......................................................................................................................................... 45
12.1 OVERVIEW ....................................................................................................................................... 45
13 DHCP SETUP ......................................................................................................................................... 47
13.1 DHCP SERVER OVERVIEW ............................................................................................................... 47
13.2 DHCP SERVER SETUP ..................................................................................................................... 48
13.3 DHCP RELAY OVERVIEW ................................................................................................................. 49
13.4 DHCP RELAY SETUP....................................................................................................................... 49
14 FIRMWARE/CONFIG UPLOAD AND DOWNLOAD WITH TFTP ......................................................... 50
14.1 OVERVIEW ....................................................................................................................................... 50
14.2 SETTING UP A TFTP SERVER ........................................................................................................... 50
14.3.1 Configuration Upload ............................................................................................................. 51
14.3.2 Configuration Download ........................................................................................................ 51
14.3.3 Firmware Download ............................................................................................................... 51
15 OPERATION COMMANDS .................................................................................................................... 52
15.1 PING COMMAND ............................................................................................................................... 52
15.2 TRACEROUTE COMMAND .................................................................................................................. 52
15.3 BRIDGE COMMAND ........................................................................................................................... 52
15.4 DHCP COMMANDS ........................................................................................................................... 56
15.5 INTERFACE COMMANDS .................................................................................................................... 61
15.6 LOGIN COMMANDS............................................................................................................................ 68
15.7 POLICY COMMANDS .......................................................................................................................... 68
15.8 ROUTE COMMANDS .......................................................................................................................... 70
15.9 SHOW COMMANDS ........................................................................................................................... 71
15.10 SYSTEM COMMANDS......................................................................................................................... 76
15.11 MLPPP COMMANDS ......................................................................................................................... 79
16 GLOSSARY ............................................................................................................................................ 80
iv
LIST OF FIGURES
Figure 1- 1 Multiple WAN--------------------------------------------------------------------------------------- 2

Figure 1- 2 MLPPP Bundle ------------------------------------------------------------------------------------- 2
Figure 1- 3 Ethernet as a backup link ----------------------------------------------------------------------- 2
Figure 2-1 Front Panel ------------------------------------------------------------------------------------------ 6

Figure 2- 2 IP6510 Slot A and Slot B Location ------------------------------------------------------------ 7
Figure 2- 3 E1/T1 Card Panel View -------------------------------------------------------------------------- 7
Figure 2- 4 RJ 45 Electrical Ethernet Card Panel View ------------------------------------------------- 7
Figure 2- 5 SFP Optical Electrical Card Panel View ----------------------------------------------------- 8
Figure 2- 6 IP6510 Jumper Setting for T1 Card ----------------------------------------------------------- 8
Figure 2- 7 IP6510 Jumper Setting for E1 Card ----------------------------------------------------------- 8
Figure 2- 8 Loop-IP6510 Front Panel ----------------------------------------------------------------------- 10
Figure 3- 1 VT-100 Monitor Connection ------------------------------------------------------------------- 12

Figure 3- 2 IP6510 Slot A and Slot B ----------------------------------------------------------------------- 15
Figure 4- 1 Remote bridge mode Setup ------------------------------------------------------------------- 18
Figure 5- 1 MLPPP Application ------------------------------------------------------------------------------ 20
Figure 6- 1 VLAN Application #1----------------------------------------------------------------------------- 22

Figure 6- 2 VLAN Application #2----------------------------------------------------------------------------- 24
Figure 7- 1 Transparently Conveying VLAN-enabled Customer Traffic ---------------------------- 28

Figure 7- 2 802.1Q Encapsulation--------------------------------------------------------------------------- 28
Figure 7- 3 802.1ad (QinQ) encapsulation ---------------------------------------------------------------- 28
Figure 7- 4 SVLAN Setup Diagram ------------------------------------------------------------------------- 29
LIST OF TABLES
Table 2- 1 Power Connector ----------------------------------------------------------------------------------- 7
Table 2- 2 Jumper Setting for E1/T1 Card ----------------------------------------------------------------- 8
Table 2- 3 E1/T1 pin definition -------------------------------------------------------------------------------- 9
Table 2- 4 Ethernet Ports Pin Definition -------------------------------------------------------------------- 9
Table 2- 5 Console Port Pin Assignment ------------------------------------------------------------------ 10
Table 2- 6 Front Panel LED Indication --------------------------------------------------------------------- 10
Table 2- 7 Ethernet Plug-in Card LED Indication -------------------------------------------------------- 11
Table 2- 8 T1/E1 Plug-in Card LED Indication ----------------------------------------------------------- 11
Table 2- 9 RJ45 10/100M Ethernet Connector Pin Assignment ------------------------------------- 11
Table 3- 1 Console Port Default Setting ------------------------------------------------------------------- 13
Table 6- 1 VLAN Table ----------------------------------------------------------------------------------------- 26

Table 6- 2 VLAN Port ------------------------------------------------------------------------------------------- 27
v
D Bitte führen Sie das Gerät am Ende seinerLewbensdauer den zue Verfügung
stehended Rückgabeund Sammelsystemen zu.
GB At the end of the product's useful life, please dispose of it at appropriate collection
points provided in your country
F Une fois le produit en fin devie, veuillez le déposer dans un point de recyclage
approprié.
ES Para preservar el medio ambiente, al final dela vida útil de su producto, depositelo
en los laguares destinado aello de acuerdo con la legislación vigente.
P No final de vida útil do producto, por favor coloque no ponto de recolha apropriado.
I Onde tutelare l'ambiente, non buttate l'apparecchio trai i normali rifiuti al termine
della sua vita utile, ma portatelo presso i punti do taccolta specifici per questi rifiuti
previsti dalla normativa vigente.
NL Wij raden u aan het apparant aan het einde van zijn nuttige levensduur, niet bij hey
gewone huisafval te deponeren, maar op de dearvoor bestemde adressen.
DK Når produktet er udtjent, bor det børtskaffes via de sæ rlige indsamlingssteder i

landet.
N Ved slutten av produktets levetid bør det avhendes på en kommunal miljøstasjon

eller leveres til en elektroforhandler.
S Lämna vänligen in produkten på lämplig återvinningsstation när den är förbrukad.
FIN Hävitä tuote käytöiän päättyessä viemällä se asianmukaiseen keräyspisteeseen.
PL Gdy produkt nie nadaje sie juz do dalszego uzytku, nalezy zostawic go w jednym ze
specjalnych punktów zajmujacych sie zbiórka zuzytych producktów w wybranych
miejscach na terenie kraju.
CZ Po skončení jeho životnosti odložte prosím výrobek na přislušném sbĕrném místé

zřízeném dle předpisů ve vaší zemi.
SK Po skončení jeho životnosti odovzdajte prosím zariadenie na príslušnom zbernom

mieste podía platných miestnych predpisov a noriem.
SLO Ko se izdelku izteče življenska doba, ga odnesite na ustrezno zbirno mesto oziroma
ga odvrzite v skladu z veljavnimi predpisi.
GR Στο Тέλος тης λειτουργικής Ζωής του προϊόντος παρακαλώ

Πετξτε το στα ειōικά σημεία που Παρέχονται οτη χωρα σας.
PRC 當產品使用壽命結束,請在你的國家所提供的適當地點做好回收處理
1 Product Description IP6510 Multiple WAN Router /Bridge
1 Product Description
1.1 Description
The Loop-IP6510 Router/Bridge provides remote bridge connectivity from 4 Ethernet ports to 2 fixed WAN
ports and also to 2 optional WAN slots. Whereas the 2 fixed WAN ports are always Ethernet, choices are
available for the 2 optional WAN slots. Each of the 2 optional slots can accept one of 4 choices of plug-in
cards, which are (a) a card with dual T1 port, (b) a card with dual E1 port, (c) a card with one 10/100 BaseT
fast Ethernet port and (d) a card with one SFP (mini-GBIC) housing for 100M-FX fast Ethernet port.
Using the optional dual E1/T1 card option, up to 4 E1/T1 lines can be used for WAN connectivity, either
separately, or in a single bundle.
All Ethernet, WAN and LAN ports have speed auto-sensing, half/full duplex auto-negotiation, and auto
MDI/MDI-X crossover features. In addition all serial (E1/T1) WAN interfaces support PPP, MLPPP, Frame
Relay, Cisco compatible HDLC and HDLC protocols.
The Loop-IP6510 Router/Bridge supports DB9S console port, which allows users to execute in-service
diagnostics and fault isolation from a local terminal. It also allows user to remote manage via Telnet, SSH
and SNMP through Ethernet or WAN ports. Multicolor LED indicators and ACO (Alarm Cut-Off) button are
provided on the front panel.
Loop Telecom Page 1

1.2 Applications
E1/T1
LAN LAN
Network
IP6510 IP6510
Figure 1- 1 Multiple WAN
E1/T1
IP6510 IP6510
Figure 1- 2 MLPPP Bundle
Backup
Network
DSL DSL
Ethernet Ethernet
E1/T1
Network
IP6510 IP6510
Figure 1- 3 Ethernet as a backup link
Loop Telecom Page 2

1.3 Specifications
Ethernet WAN Interface
Two built-in 10/100BaseT Ethernet ports (WAN1 and WAN2)
Speed auto-sensing
Half/full duplex auto-negotiation
Auto MDI/MDI-X crossover
WAN Plug-in Module

E1 card: 2 ports per card, up to 4 ports per system
T1 card: 2 ports per card, up to 4 ports per system
Electrical RJ45 Ethernet card: 1 port per card, up to 2 ports per system
Optical SFP Ethernet card: 1 port per card, up to 2 ports per system
Layer-two E1/T1 WAN protocols: PPP, MLPPP, HDLC, Frame Relay, Cisco compatible HDLC
E1 Line Interface
Line Rate 2.048M bps  50 ppm
Line Code HDB3
Output Signal ITU G.703
Connector RJ48C
Loopbacks Line Loopback, Payload Loopback
Test Pattern 20-bit QRSS, 3-in-24, 1-in-8, 2-in-8, 1:1
T1 Line Interface
Line Rate 1.544 Mbps  50 bps
Line Code AMI or B8ZS
Output Signal DS1
Connector RJ48C
Loopbacks Line Loopback, Payload Loopback
Test Pattern 20-bit QRSS, 3-in-24, 1-in-8, 2-in-8, 1:1
LAN Interface
4 10/100BaseT interfaces
Speed auto-sensing
Half/full duplex auto-negotiation
Auto MDI/MDI-X crossover
Management
SNMP v1, v2c
Telnet
SSH
Bridge
STP, RSTP
802.1q supported
Cisco ISL packet transparent
VLAN packet transparent
User configurable aging time
Up to 16K MAC table
Padding/un-padding Ethernet FCS
Support IEEE 802.1ad Q-in-Q
Router
Routing protocol: RIP-I, RIP-II, OSPF
Static route
Loop Telecom Page 3

Address Translation
NAT/NAPT
Static address table for NAT
Port forwarding table for NAPT (Virtual Service)
Supports port range from 1 to 65535
DHCP
DHCP server support for LAN users (RFC2131, RFC2132)
BOOTP compatible
DHCP relay
Access Control & Firewall (RT)

Packet filtering based on
 Inbound/outbound direction
 Source/destination IP address
 Protocol types (ICMP, TCP, UDP)
 Port number range
Up to 4 control lists
QoS
QoS based on rate limit
Classification based on
 Outbound direction
 Source/destination IP addresses
 DSCP
 Protocol types
 Port number range
Administration & Diagnostics

Ping
Traceroute
Loopback
Telnet
SSH
Electrical
Power Source (AC) 100 to 240 Vac, 0.8A
Power Source (DC) -36 to -72 Vdc, 1.2A
Power Consumption < 20 W
Physical and Environment

Dimensions 334.5 x 44 x 228 mm (W x H x D)
Mounting Stand-alone, wall mount
Temperature Range 0C to 55C
Humidity 0% - 95% RH (non-condensing)
Standards Compliance
IEEE 802.1d bridge, 802.1w RSTP, 802.1q VLAN, 802.1ad Q-in-Q
IETF RIP1 (RFC1058), RIP2 (RFC1389)
ITU G.703, G.704, G.823
Compliance
EMC/EMI FCC15 Class A, EN55022, EN55024
Safety UL60950, IEC60950-1 (CB)
Network FCC68, CS-03
Loop Telecom Page 4

Note: Non-Loop SFP modules are not guaranteed to work with our equipments. It is strongly recommended to buy
Loop-logo SFP modules.
Loop Telecom Page 5

2 Installation IP6510 Multiple WAN Router /Bridge
2 Installation
2.1 Site Selection
The following list shows site selection guidelines. Follow this list to select a proper installation site.
1. Location of the Loop-IP6510 unit should be part of the central office equipment layout design.
Consideration should be given to entrance cable routing.
2. The installation site should provide proper room for adequate ventilation and cable routing. Reserve at
least 0.5 m at the rear of the unit for human access, cables, and air flow.
3. The site should provide a stable environment. The operating area should be clean and free from
extremes of temperature, humidity, shock, and vibration.
4. Relative humidity should stay between 0 and 95%.
2.2 Mechanical Installation

The Loop-IP6510 is a desk-top stackable unit. The front panel is shown below in Figure 2-1.
Figure 2-1 Front Panel
CAUTION:
 Never install communications wiring during a lightning storm.
 Never install communication jacks in wet locations unless the jack is specifically
designed for wet locations.
 Never touch un-insulated communication wires or terminals unless the line has
been disconnected at the network interface.
 Use caution when installing or modifying communication lines.
Loop Telecom Page 6

2.2.1 Power
The power connection on your unit will be AC 100-240Vac (0.8A) and DC -36 to -72Vdc (1.2A). AC and DC
power are supported simultaneously on the IP6510.
Before attaching any power supply, check the label on the Loop-IP6510 unit to ensure that you connect the
unit to the correct power source. The unit’s power switch should be in the OFF position while you connect the
power source.
Table 2- 1 Power Connector

Signal Description
-V -DC 24 or 48 Volts
+V +DC Return
Chassis Ground
2.2.2 E1/ T1/Ethernet Card Description

The IP6510 can carry up to two dual E1/T1 plug-in cards or Single Ethernet cards in Slot A and Slot B.
Note: Plug-in cards are not hot-pluggable. Please turn off the device before removing or inserting a
plug-in card.
Slot A Slot B
Figure 2- 2 IP6510 Slot A and Slot B Location
Figure 2- 3 E1/T1 Card Panel View
Figure 2- 4 RJ 45 Electrical Ethernet Card Panel View
Loop Telecom Page 7

Figure 2- 5 SFP Optical Electrical Card Panel View
2.2.2.1 Jumper Settings
Table 2- 2 Jumper Setting for E1/T1 Card

E1 (120 ohm) T1(100 ohm)
J1 1,2 -
JP1 - 2,3
JP10 - 2,3
Figure 2- 6 IP6510 Jumper Setting for T1 Card
J1
Main Board
JP1 JP10
Figure 2- 7 IP6510 Jumper Setting for E1 Card
Loop Telecom Page 8

J1
Main Board
JP1 JP10
NOTE: CLI commands for T1 such as interface intf t1 code are only available at the command line if the
card is in T1 mode. The same for E1 commands.
2.2.2.2 E1/T1 pin assignment
Table 2- 3 E1/T1 pin definition

Pin Number Signal Signal Direction
1 Ring In
2 Tip In
3 Unassigned
4 Ring Out
5 Tip Out
6 Unassigned
7 Shield Ground
8 Shield Ground
Table 2- 4 Ethernet Ports Pin Definition

Pin Number Signal Description
1 Transmit Data + Output
2 Transmit Data - Output
3 Receive Data + Input
6 Receive Data - Input
7 Chassis Ground
8 Chassis Ground
Loop Telecom Page 9

2.3 Front Panel Console Port and LEDS

The front panel is shown in the figure below. The LEDs on the front panel indicate unit status.
Cold plug-in Cold plug- in

Slot A Slot B
Ground
Screw
USB Port*
AC
Power ACO WAN Console
DC LAN 1- 4
Power WAN1-2 Backup* Port
LEDs
* Future option
Figure 2- 8 Loop-IP6510 Front Panel
2.3.1 Console Port

To use the RS232 interface to configure the unit, use a straight cable to connect a VT100 terminal to the DB9
jack (Console Port) on the front panel of the Loop-IP6510. Console Port pin assignments are listed in table 2-
5 below.
Table 2- 5 Console Port Pin Assignment

Pin Number Signal Source
1 Data Carrier Detect To DTE
2 Receive Data To DTE
3 Transmit Data From DTE
4 Unassigned
5 Signal Ground
6 Data Set Ready To DTE
7 Unassigned
8 Clear to send To DTE
9 Unassigned
2.4 LED Operation

The front panel of the IP6510 has two LEDs for each LAN port. They are for: Ethernet Link/Active, and
Ethernet speed. LED Indications are listed in Table 2-6, Table 2-7, Table 2-8 below.
Table 2- 6 Front Panel LED Indication

LED Color Indication
Off Power Off
Red N/A
ACT
Green System is operating
Amber Power on self test
Loop Telecom Page 10

Off No alarm
Red At least one alarm is active
ALM
Green N/A
Amber N/A
Off No plug-in card detected
A Green Layer two protocol is active in both slots
Red At least one alarm state is alert
Off No plug-in card detected
B Green Layer two protocol is active in both slots
Red At least one alarm state is alert
Note: Under normal status, the LED indication order for ACT and ALM will be Green to Amber. When the
LED is flashing, keep pressing the ACO button will set the machine to default.
Table 2- 7 Ethernet Plug-in Card LED Indication

Off Link is down
LINK/ACT Green Link is up
Flashing Green Link is receiving or transmitting packets
10M/100M Off The interface is operating in 10BaseT mode
Green The interface is operation in 100BaseT mode
Table 2- 8 T1/E1 Plug-in Card LED Indication

Green Link frame is in sync.
Flashing Green A test is in progress
LINE Red Loss of signal or loss of frame
Amber Receive yellow alarm from line
Flashing Amber Receive AIS from line
Green The interface is operating in T1 mode
MODE
Off The interface is operating in E1 mode
2.5 Ethernet Connection

RJ45 10/100M Ethernet connection pin assignments are listed in Table 2-9 below.
Table 2- 9 RJ45 10/100M Ethernet Connector Pin Assignment

Pin Number Signal
1 Transmit Data +
2 Transmit Data -
3 Receive Data +
4 No Connection
5 No Connection
6 Receive Data -
7 No Connection
8 No Connection
Note: The Ethernet interface supports Auto MDI/MDI-X and will work with either a parallel or a
crossover cable.

3 Operation IP6510 Multiple WAN Router /Bridge
3 Operation
This chapter describes the Loop-IP6510 router configuration options and operational functions. Refer to
subsequent chapters for detailed instructions regarding specific applications.
3.1 Power On
After following the installation instructions in Chapter 2, power up the unit. It will go through a self-test
procedure.
3.2 Using a VT-100 Terminal

In order to properly set up the Loop-IP6510 you will need a VT-100 Monitor. A VT-100 Monitor is a PC
running emulator software. Use a DB9 cable to connect the front Console Port of the IP6510 to either COM
Port 1or COM Port 2 of the PC you are using as a VT-100 monitor. It does not matter which COM Port you
connect it to.
Note: Many newer PCs use USB Ports. If your computer has a USB port rather than COM ports you will
need to purchase a commercially available PC USB to DB9 conversion cable. These cables come
with software which, when loaded in a PC, will allow you to send keyboard commands through the
PC’s USB Port to the DB9 Console Port of the Loop-IP6510.
IP6510
DB9 to PC's Com Port

(Newer laptop PCs will require a
DB9 to USB cable.)
VT-100 Monitor
Figure 3- 1 VT-100 Monitor Connection
3.2.1 VT-100 Monitor Serial Port Setup
Open your VT-100 emulator program. Left-click your mouse on Setup. A drop-down menu will appear. Left
click your mouse on Serial port Setup.

A Serial port setup screen will appear as shown below.
Set COM Port to the COM Port you are connected to on your VT-100 monitor. Then select your other
settings from Table 3-1 below.
Table 3- 1 Console Port Default Setting
Item Options Default
Baud 38400, 19200, 9600, 2400, 1200 9600
Data Bit 8, 7 bit per byte 8
Stop Bit 2, 1 bit 1
Parity Bit NONE, EVEN, ODD NONE
After selecting your settings left-click your mouse on OK. The setup screen will disappear.
To save your setup, left-click Save setup with your mouse, as shown in the screen below.
You can save the setup in any directory you choose. For the sake of convenience we saved our setup in the
Loopterm file on our desktop.
3.3 Login, Set Time and Date and Logout

3.3.1 Overview
The IP6510 CLI provides for two levels of users: operator and admin. The operator is allowed to inspect
current system configuration and operation status only. The admin is allowed to change system settings. The
IP6510 disables password checking for operator and admin by default.
3.3.2 Login

The user uses login admin to login as an admin user. A command example is shown below. This example
assumes that the password check for admin is disabled, so when the system prompts for a password just
press ENTER (ie. ignore the password). The command logout logs the user off of the system.
>login admin
Password:
Welcome!!
Press '?' to get help!
admin>
3.3.3 Password
The user uses the command system account password to change the password. The system prompts for
the old password. Type in the old password and press ENTER. The system prompts for the new password.
Enter the new password and press ENTER to reconfirm the new password. Press ENTER and the password
is changed.
>login admin
Password:
Welcome!!
admin>system account password

Old password: xxxx
New password: xxxx
Confirm new password: xxxx
Command succeeded
3.3.4 Show System Date/Time and Change It

Type in the command show system time and press Enter to bring up a date/time display. To change the
setting, type in the command system time followed by the correct date and 24 hr. time as shown in the
sample screen below. Press Enter.
admin>show system time
09/20/2007 17:53:16
Command succeeded
admin>system time 09/10/2007 10:10:00

Command succeeded
Note: The system time and date will be automatically saved since the setting.
3.3.5 Logout
Type in the command logout and press ENTER.
admin>logout
Bye bye!
3.4 Interface Naming Rule

There are two E1/T1 plug-in cards for IP6510. Slot A and Slot B have two interfaces respectively. The
interfaces are named as wan-a-1 and wan-a-2; wan-b-1 and wan-b-2.

Figure 3- 2 IP6510 Slot A and Slot B

3.5 Assigning Timeslots To A WAN Port
An E1 or T1 WAN port is ineffective until at least one timeslot is assigned to it. The command interface wan-
x-x timeslot assigns and deletes timeslots to/from the WAN port.
For example: “interface wan-a-x timeslot add/set/delete”

add: add some more timeslots to interface and keep timeslots already assigned for the interface.
set: clear all timeslots assigned for the interface and assign the newly specified timeslots to the interface.
delete: delete timeslots from interface.
Note: T1 can distribute timeslots numbering from 1 to 24.

E1 can distribute timeslots numbering from 1 to 31.
3.6 Configuration
All commands take effect immediately except for: system configuration load and system firmware load.
Those commands take effect after the unit is powered down and then powered up again.
3.7 Remote Management

3.7.1 SNMP
IP6510 SNMP agent supports up to 5 trap addresses. Whenever an alarm occurs, the IP6510 sends a trap
message to all of the trap addresses. Use the command system snmp trap add to add a trap address into
the address list. The following example shows how to configure the SNMP.
192.168.1.254/24
LAN1
PC
IP6510
LAN
Example for PC:

IP 192.168.1.1
Mask: 255.255.255.0
Gateway: 192.168.1.254
Example for IP6510:

interface lan1 ip 192.168.1.254/24

system snmp trap add v1 192.168.1.1 public
system configuration save
3.7.2 SSH
SSH provides authentication and a secure remote management channel which is more secure than
traditional Telnet. Before activating the SSH service, the user should generate RSA and DSA key pairs to do
authentication for the future connection. Following example shows how to activate the SSH service on
IP6510. Once the SSH service is activated, the user can use a SSH client (ex. A free PUTTY) to connect to
the IP6510. Once the user is connected to IP6510 by using SSH, the user can get the same CLI command
interface as connected to console port.
LAN/WAN
100.1.1.1
100.1.1.2 IP6510
Example for IP6510:

system ssh host generate rsa
system ssh host generate dsa
system ssh setup enable
system configuration save
3.8 Verifying Loop-IP6510 Operations

The purpose of this section is not to help the user determine where a possible fault in the network may lie.
For this, the user needs to know the exact geometry of the network. Then standard network trouble shooting
procedures should be followed, which involve sectionalizing the network and performing loopback tests on
pieces of the network.
The purpose here is to help the user determine whether the Loop-IP6510 equipment is at fault after tests
have pointed a suspicious finger at this equipment. The procedures outlined here depends on test equipment
and other equipment the user may have on hand.
The organization of these procedures start from the simple to the complex. The procedure ends when a
definitive conclusion is made that the Loop-IP6510 equipment is at fault. To verify that the Loop-IP6510
equipment is not at fault, specialized equipment such as a BERT (bit error rate test) set is needed.
3.8.1 Independent Test

Remove all line and connections to the Loop-IP6510. Remove power. After a few seconds, re-apply power.
Observe the power-up self-test sequence. If this fails, then Loop-IP6510 has failed. See if the LEDs show any
abnormal displays. If yes, use the LED indications to guide the user to test other parts of the network, such
as the E1/T1 line.
Especially during initial installation, excessive errors may be due to (a) incorrect configuration of either Loop-
IP6510 or of the equipment at the other end of the line, or (b) due to faulty line installation, which results in

excessive noise, cross talk, or impedance mismatch. Especially in electrically noisy environments, such as
central offices, use of shielded cables are mandatory.
3.8.2 Substitution
If a spare Loop-IP6510 plug-in is available, then replace the working one with the spare. The user must
carefully configure the spare exactly as the working one. If the substitution clears the problem, then the
original working one is suspect. Note that this is not definitive as other reasons may cause the same
symptom. A good practice is to reconfigure the original one and swap once more.
If both units behave the same, then the problem is probably elsewhere.
3.8.3 Using the Bert Test Set

If a BERT (bit error rate test) set and another Loop-IP6510 are available, such as the Fireberd 6000, then a
comprehensive suite of test are available to examine the health of the Loop-IP6510. If another Loop-IP6510
is not available, use of the loopback plugs would provide some of the tests otherwise possible.
With a BERT, each of the ports of the Loop-IP6510 can be tested individually. The user must configure the
BERT in the exact way the Loop-IP6510 is configured. This is easily done by comparing each of the options
one by one. After checking that the configuration matches, if any one of the ports fails, then Loop-IP6510 has
failed.

4 Remote Bridge Setup Overview IP6510 Multiple WAN Router /Bridge
4 Remote Bridge Setup Overview

4.1 Overview
Figure 4-1 below illustrates the IP6510 being used in bridge mode. There are two IP6150 in this application.
Their setup procedures are identical. The IP addresses and gateway addresses used in the diagram
correspond to the sample step by step configuration instructions in section 4.2.
(PPP, MLPPP, HDLC, or CHDLC)
wan-a-1
SNMP
Local Network 1
LAN 1
TDM IP Network
Network Loop-IP 6510 # 1
Management IP:140.132.254.254
Mask: 255. 255.0.0
(PPP, MLPPP, HDLC, or CHDLC)
wan-a-1
Local Network 2
LAN 1
Loop- IP 6510 # 2
Management IP:140.132.254.253
Gateway
Figure 4- 1 Remote bridge mode Setup

4 Remote Bridge Setup Overview IP6510 Multiple WAN Router /Bridge
4.2 Step by Step Setup Instructions

The first step is to create a bridge group for the IP6510. Type in the command bridge create followed by the
given name and a MAC address. Then press the Enter key.
The second parameter, MAC address, is an optional parameter. If MAC address is not given, the IP6510 will
generate the MAC address randomly. It may conflict with the MAC address of other devices. The following
command can be set up once every time for IP6510.
>login admin
Password:
Welcome!!
admin>bridge create br1

WARNING: A MAC address has been randomly generated for bridge group! It might
conflict with other device!!
Command succeeded
The IP6510 WAN ports carry Ethernet frame checksum by default. To save WAN port’s bandwidth, we
disable the carry of the FCS by command bridge br1 fcs disable.
admin>bridge br1 fcs disable

Command succeeded
To setup management on bridge mode, the user have to enable bridge management feature and assign an
IP address for the management port.
admin>bridge br1 management enable

Command succeeded
admin>bridge br1 ip 140.132.254.254/16

Command succeeded

5 PPP/MLPPP IP6510 Multiple WAN Router /Bridge
5 PPP/MLPPP
5.1 Overview
Multilink PPP can connect multiple links between two systems as needed to provide extra bandwidth.
Remotely accessing resources through PPP Multilink allows for the increase in overall throughput by
combining the bandwidth of two or more physical communication links.
Example: Bundle the four T1 interfaces (wan-a-1 to wan-b-2) in a virtual interface (m1) and make the virtual
interface become bridge mode. When the data packets transmit from LAN to bundle interface, MLPPP will
fragment the packets and transmit the fragments to wan-a-1 to wan-b-2. The remote device receives the
fragments and assembles them into a complete packet.
Figure 5- 1 MLPPP Application

IP6510 supports multiple WAN interfaces. Before configuring each WAN interface, it is necessary to setup
the timeslot map in advance. Use the interface wan-x-x timeslot add to assign timeslots to T1 interfaces.
The following example assigns 24 timeslots to all T1 interfaces.
admin>interface wan-a-1 timeslot add 1-24

Command succeeded
admin>interface wan-a-2 timeslot add 1-24

Command succeeded
admin>interface wan-b-1 timeslot add 1-24

Command succeeded
admin>interface wan-b-2 timeslot add 1-24

Command succeeded
NOTE: For making an MLPP bundle with E1 interfaces, use the command interface wan-x-x timeslot add
1-31 to add all of the available timeslots to the E1 interfaces. All of the other commands below are the same.
Set the interface to use PPP for layer-two encapsulation.

5 PPP/MLPPP IP6510 Multiple WAN Router /Bridge
admin>interface wan-a-1 encapsulation ppp

Command succeeded
admin>interface wan-a-2 encapsulation ppp

Command succeeded
admin>interface wan-b-1 encapsulation ppp

Command succeeded
admin>interface wan-b-2 encapsulation ppp

Command succeeded
Create a virtual bundle m1 by command multilink create.
admin>multilink create m1
Command succeeded
Join all of the E1 or T1 ports to be members of the bundle m1.

NOTE: The configuration on these interfaces will be cleared to default.
admin>multilink virtual m1 add wan-a-1 wan-a-2 wan-b-1 wan-b-2

The configurations of bundled interface(s) have been cleared!
Command succeeded
Create a bridge group. The following command show an example that creates a bridge without a specifying
a MAC address. In the case, the IP6510 randomly generates a MAC address for the group.

WARNING: A MAC address has been randomly generated for bridge group! It might conflict
with other device!!
Command succeeded
Add lan1 and m1 into bridge.
admin>bridge br1 add lan1 m1

Command succeeded

6 VLAN IP6510 Multiple WAN Router /Bridge
6 VLAN
6.1 Overview
VLAN is used to subdivide a LAN into smaller entities known as VLAN1, VLAN2, VLAN3, VLAN 4094. A
device in a particular VLAN can monitor traffic in that VLAN only, and cannot monitor packets in any other
VLANs. This provides an important level of security and also assists the user to do certain kinds of QoS.
In Figure 6-1, below, VLAN1 and VLAN2 both feed into the VLAN-aware Ethernet Switch. The switch assigns
a Port VID to each port. VLAN1 is assigned VID:3 and VLAN2 is assigned VID:5. Transmissions from
VLAN1(VID:3) and VLAN2(VID:5) are put into tagged packets by the switch and then passed on to the
Ethernet Port of the IP6510.
The IP6510 reads the tag on the packets and uses this VLAN ID to make packet forwarding decisions. In the
diagram below, the packets are to be sent via two T1 interfaces to the Network. Each of these channels can
carry VLAN traffic(eg. VID:3, wan-a-1). The IP6510 forwards packets of a VLAN to a proper interface
according to the tags on the packets.
Figure 6- 1 VLAN Application #1
6.2 Example Setup
6.2.1 Application #1 (Fig. 6-1) Step by Step Setup Instructions
1. Bridge mode and Timeslot Setting
given name and a MAC address.
The second parameter, MAC adress, is an optional parameter. If MAC address is not given, the IP6510 will
generate the MAC address randomly. It may conflict with the MAC address of other devices.

WARNING: A MAC address has been randomly generated for bridge group! It might conflict with
other device!!
Command succeeded

For WAN interface setup, there are wan-a-1and wan-a-2 for setting.
The IP6510 supports multiple WAN interfaces. Before configuring each WAN interface, it needs to setup the
timeslot map in advance.
Type in the command interface wan-a-1 timeslot set to assign timeslots to interface wan-a-1. The
following example assigns 24 timeslots to interface wan-a-1 from timeslot 1 to timeslot 24.
admin>interface wan-a-1 timeslot set 1-24

Command succeeded
NOTE: For E1, the proper command would be wan-a-1 timeslot set 1-31 to assign all available E1
timeslots to this WAN port.
Type in the command interface wan-a-2 timeslot set to assign timeslots to interface wan-a-2 timeslot.
Here, we don’t explicitly specify any encapsulation method for T1 interfaces. This causes the interfaces to
run default encapsulation method, HDLC.
admin>interface wan-a-2 timeslot set 1-24

Command succeeded
Type in the admin command bridge br1 add lan1 wan-a-1 wan-a-2.
admin>bridge br1 add lan1 wan-a-1 wan-a-2

Command succeeded
2. VLAN Setup
The VLAN has to be enabled on the bridge. Type in the command bridge br1 vlan followed by enable.
admin>bridge br1 vlan setup enable

Command succeeded
You must create a VID for each VLAN. To create VID:3 type in the command bridge br1 vlan create and
press Enter. To create VID:5 type in the command bridge br1 vlan create 5.
admin>bridge br1 vlan create 3

Command succeeded

Command succeeded
You must setup the WAN Port to allow it to process VLAN1 (VID:3) or VLAN2 (VID:5).For tagged member
of VID:3 VLAN1. Type in the command bridge br1 vlan add 3 tag wan-a-1. Press Enter. For tagged
member for VID:5 VLAN2. Type in the command bridge br1 vlan add 5 tag wan-a-2.
admin>bridge br1 vlan add 3 tag wan-a-1

Command succeeded

Command succeeded
3. Ethernet Port Setup
You must setup the Ethernet Port to allow it to process VLAN1 (VID:3) and VLAN2 (VID:5). To set LAN1
Ethernet to be a tagged member for VID:3 VLAN1, type in the command bridge br1 vlan add 3 tag lan1.

Press Enter. To set LAN1 Ethernet to be a tagged member for VID:5 VLAN2, type in the command Bridge
br1 vlan add 5 tag lan1. Press Enter.
admin>bridge br1 vlan add 3 tag lan1

Command succeeded

Command succeeded
The setup for Application #1 (Figure 6-1) is now complete.
6.2.2 Application #2 (Fig. 6-2) Step by Step Setup Instructions
Figure 6-2, below, is much like Figure 6-1, except that it contains both tagged and untagged packets on the
Ethernet side. The IP6510 assigns a default VLAN ID to untagged packets (ie.VLAN3 packets in the
diagram). The default VID is always the Port VID of the Ethernet Port.
Figure 6- 2 VLAN Application #2
Connect a cable between the COM port of your PC and the Console port of the IP6510. Then follow the
instructions below.
1. Bridge mode and Timeslot Setting
given name and a MAC address. Then press the Enter key.
The second parameter, MAC address, is an optional parameter. If the MAC address is not given, the IP6510 will
generate the MAC address randomly. It may conflict with the MAC address of other devices.

WARNING: A MAC address has been randomly generated for bridge group! It might conflict with other
device!!
Command succeeded
For WAN interface setup, there are wan-a-1and wan-a-2 for setting.The IP6510 supports multiple WAN
interfaces. Before configuring each WAN interface, it needs to setup the timeslot map in advance.
Type in the command interface wan-a-1 timeslot set to assign timeslots to interface wan-a-1. The following
example assigns 24 timeslots to interface wan-a-1 from timeslot 1 to timeslot 24.

A admin>interface wan-a-1 timeslot set 1-24

Command succeeded
NOTE: For E1, the proper command would be wan-a-1 timeslot set 1-31 to assign all available E1
timeslots to this WAN port.
Type in the command interface wan-a-2 timeslot set to assign timeslots to interface wan-a-2 timeslot.
Here, we don’t explicitly specify any encapsulation method for T1 interfaces. This causes the interfaces to
run default encapsulation method, HDLC.
A admin>interface wan-a-2 timeslot set 1-24

Command succeeded
Type in the admin command bridge br1 add lan1 wan-a-1 wan-a-2 wan-b-1.
A admin> bridge br1 add lan1 wan-a-1 wan-a-2 wan-b-1
Command succeeded
2. VLAN Setup
You must set the VLAN mode. Type in the command bridge br1 vlan followed by the parameter you require.
In our sample screen we chose to use enable as our parameter.
admin>bridge br1 vlan setup enable

Command succeeded
You must create a VID for each port. To create VID:3 type in the command bridge br1 vlan create 3 and
press Enter. To create VID:5 type in the command set vlan create 5. To create VID:7 type in the command
bridge br1 vlan create 7.

Command succeeded

Command succeeded

Command succeeded
For tagged member of VID:3 VLAN1, type in the command bridge br1 vlan add 3 tag wan-a-1. Press Enter.
For tagged member of VID:5 VLAN2, type in the command bridge br1 vlan add 5 tag wan-a-2. For tagged
member of VID:7 VLAN2, type in the command bridge br1 vlan add 7 tag wan-b-1.

Command succeeded

Command succeeded
admin>bridge br1 vlan add 7 tag wan-b-1

Command succeeded
3. Ethernet Port Setup
You must setup the Ethernet Port to allow it to process VLAN1 (VID:3), VLAN2 (VID:5) and VLAN3 (VID:7)
To set LAN1 Ethernet to be a tagged member for VID:3 VLAN1, type in the command bridge br1 vlan add
3 tag lan1. Press Enter. To set LAN1 Ethernet to be a tagged member for VID:5 VLAN2, type in the command

bridge br1 vlan add 5 tag lan1. Press Enter. To set LAN1 Ethernet to be an untagged member for VID:7
VLAN3, type in the command bridge br1 vlan add 7 untag lan1. Press Enter. Finally, to set LAN1’s PVID to
be VID:7, type in the command interface lan1 vlan pvid 7.

Command succeeded

Command succeeded
admin>bridge br1 vlan add 7 untag lan1

Command succeeded
admin>interface lan1 vlan pvid 7

Command succeeded
The setup of Application #2 (Figure 6-2) is now complete.
6.3 VLAN and Port Tables
6.3.1 VLAN Table
The “show bridge br1 vlan table” command can be used to access the VLAN Table. The VLAN table displays
the tagged/untagged member for each VLAN ID. There can be as many as 4094 VLAN IDs. The VID1 appears in
the table is automatically generated. The others must be created.
Table 6- 1 VLAN Table

admin>show bridge br1 vlan table
====================================================================
VID: 1
Tag Member:
Untag Member:
BrgMng_0, lan1, wan-a-1, wan-a-2, wan-b-1
====================================================================
VID: 3
Tag Member:
lan1, wan-a-1
Untag Member:
====================================================================
VID: 5
Tag Member:
lan1, wan-a-2
Untag Member:
====================================================================
VID: 7
Tag Member:
wan-b-1
Untag Member:
lan1

7 VLAN Stacking (Q-in-Q) Setup IP6510 Multiple WAN Router /Bridge
Command succeeded
6.3.2 VLAN Port Table
The “show bridge br1 vlan port” command can be used to display a port’s parameters in the VLAN
environment.
Table 6- 2 VLAN Port

admin>show bridge br1 vlan port
Port PVID Frame-type Ingress-filter
=====================================================================
lan1 7 all disabled
wan-a-1 1 all disabled
wan-a-2 1 all disabled
wan-b-1 1 all disabled
Command succeeded
7 VLAN Stacking (Q-in-Q) Setup
7.1 Overview
Double-tag Q-in-Q allows a service provider to convey customer traffic transparently. Figure 7-1, below,
shows the basic application of the IP6510 Q-in-Q feature. The IP6510 receives Ethernet frames (tagged or

untagged) from a customer’s LAN, then encapsulates the frames with an additional outer tag and sends them
out through a WAN link.
Customer Customer Customer Customer

Network VLAN Switch VLAN Switch Network
C- Tag + S- Tag C- Tag + S-Tag C-Tag

C- Tag VLAN 1
VLAN 1 Provider
IP6510 Network IP6510
VLAN 2 VLAN 2
. Customer VLAN Traffic .
.. ..
. Provider VLAN Tunnel
.
Figure 7- 1 Transparently Conveying VLAN-enabled Customer Traffic
7.2 VLAN Stacking

C-TAGs are standard format VLAN tags. 802.1ad S-TAGs are similar, but use different TPID and have Drop
Eligible Indicator instead of CFI.
C-TAG
LEN/
TPID TCI DATA FCS
DA(6B) SA(6B) ETYPE
(2B) (2B) (0~1500B) (4B)
(2B)
C
8100 PCP F C-VID
I
Figure 7- 2 802.1Q Encapsulation
S-TAG C-TAG
LEN/
TPID TCI TPID TCI DATA FCS
DA(6B) SA(6B) ETYPE
(2B) (2B) (2B) (2B) (0~1500B) (4B)
(2B)
D
8100 PCP E S-VID
I
Figure 7- 3 802.1ad (QinQ) encapsulation
*PCP: The Priority Code Point (PCP) is a 3-bit length field which is used to convey priority and drop
eligibility parameters.
*DEI: the Drop Eligible Indicator bit.
*S_VID: The S_VLAN Identifier (VID) is a 12-bit length field uniquely identifying the VLAN to which the
frame belongs. Its value can be between 1 and 4,094.

7.3 Definitions
Priority Code Point (PCP) is user configurable and sets the default value of the priority field of a newly
inserted S-TAG.
Drop Eligible Indicator (DEI) is user configurable. The default value is 0.
TPID of S-TAG is user configurable. The default value is 8100.
Per-port Parameter S-VLAN Port Type defines how a port processes an egress packet. Following table
defines actions of all possible egress processes.
Table 7- 1 Egress Process

Port Type Action
Provider When the port transmits a packet that has no S-TAG, the IP6510 inserts
an S-TAG with the receive port’s S-PVID. The Tag process enables a
provider network port to insert an outer tag (S-TAG) for user packets.
Customer The port always removes the S-TAG when a packet is forwarded through
the port. The process enables a customer network port to remove the
outer tag before it forwards a packet to the customer’s network.
Note: Default WANs are provider ports. Provider ports allow only packets with S-Tag to pass through.
Default LANs are customer ports. Customer ports do not allow packets with S-TAG to pass An SVLAN
group can include members of the customer port group only or the provider port group only. The
SVLAN group cannot include members of both port groups. If the packets from customer to provider
ports want to pass through, IP6510 must set up the customer ports' PVID same as provider ports'
SVID.
7.4 Setup Example

In Figure 7-4, below, The switch assigns a Port VID to each port. WAN1 is assigned VID:3. Transmissions
from LAN1 are put into tagged packets by the switch and then passed on to WAN1.
The IP6510 reads the tag on the packets and uses this VLAN id to make packet forwarding decisions. In the
diagram below, the IP6510 forwards packets of a VLAN to a proper logical chanel according to the tags on
the packets.
C- TAG Data LAN 1 S- TAG C- TAG Data

WAN 1
Loop
Data Customer pvid3 Provider svid3 S- TAG Data
Figure 7- 4 SVLAN Setup Diagram
Table 7- 2 SVLAN Parameter Value Table

Parameter(IP6510) Value
SVLAN-ENABLE True
VLAN-ENABLE False
SVLAN TPID 8100
LAN1 port type customer
WAN1 port type provider
LAN1 SVLAN PVID 3

SVLAN Group 1 (SVID=3) With members WAN1
Setup Commands
admin> create bridge br1
WARNING: A MAC address has been randomly generated for bridge group! It might
conflict with other device!!
Command succeeded
admin>bridge br1 add lan1 wan1

Command succeeded
admin>bridge br1 svlan setup enable

Command succeeded
admin>bridge br1 svlan create 3

Command succeeded
admin> bridge br1 svlan add 3 wan1

Command succeeded
admin> interface lan1 svlan pvid 3

Command succeeded

8 Frame Relay Setup IP6510 Multiple WAN Router /Bridge
8 Frame Relay Setup
8.1 Overview
Each IP6510 WAN port can support multiple Frame Relay PVCs, up to 16 per port. The maximum number of
PVCs in IP6510 is 64. Figure 8-1 below illustrates a Frame Relay setup. The dashed lines in the diagram
represent Frame Relay PVCs.
Note: The IP6510 only supports user site protocol and cannot communicate directly with each other. They
must be connected to a Frame Relay network that includes devices that run FR network protocol.
Frame
Relay User
Network
IP6510
Figure 8- 1 Frame Relay Application

8 Frame Relay Setup IP6510 Multiple WAN Router /Bridge

Set the WAN port to run Frame Relay.
adm in>interface wan -a-1 encapsulation fram e_relay

Com m and succeeded
Set Frame Relay polling protocol as Q.933 Annex A and its parameters n391, n392, n393, and t391. Please
note that these parameters must match the parameters on the network side.
adm in>interface wan -a-1 fram e_relay q933 n391 10 n392 4 n393 5 t391 20
Com m and succeeded
Then create a PVC and set its bandwidth parameters.
adm in>interface wan -a-1 pvc add pvc1 17 512 512 64 120
Com m and succeeded
Note: In the above screen the first 512 is the value for the CIR (Committed Information Rate) of PVC1. The
total sum of the CIR values for all PVCs must not exceed the total physical bandwidth of the WAN
port. Physical bandwidth can be calculated by using the formula.
Physical bandwidth= n (where n represents number of timeslots assigned to wan-a-1) x 64k.
If you are not sure how many timeslots you used in your WAN port mapping, you can check by using
the command show interface wan-a-1 config.
Assign an IP address for the PVC.
adm in>interface wan -a-1 pvc1 ip 100.2.254.254/16

Com m and succeeded
A PVC can also run a dynamic routing protocol. In following example, RIP II is enabled
adm in>interface wan -a-1 pvc1 route rip setup enable

Com m and succeeded
adm in>interface wan-a-1 pvc1 route rip version 2

Com m and succeeded
This setup procedure is now complete.

9 NAT / NAPT IP6510 Multiple WAN Router /Bridge
9 NAT / NAPT
9.1 Overview
NAT stands for Network Address Translation, NAPT means Network Address and Port Translation. These
two very similar techniques can change the IP address, checksum, and other headers in the packet while
leaving the data unchanged. It can be applied in a one-to-one or one-to-many setting. The one to one method
can be used to translate between two different systems of addresses.
The one to many NAPT application, the most commonly used technique, hides several devices who do not
have a globally unique IP address behind a single IP address that is globally unique. All traffic from the local
network arrives here and the router then distributes the packets using previously stored translation data. An
analogy can be an office telephone network with a single telephone number but with an extension necessary
to contact any one person. Another example can be a large family with a single home address but many kids,
all of whom receive letters in the mail.
Because NAT/NAPT hides many devices behind one IP address, it does not allow for ideal “end to end”
communication. However, this technique can greatly expand the available address space, and was thus a
major way to prevent IP address exhaustion before the introduction of IPv6.
9.2 Example and Setup Instructions
E1 (PPP or HDLC)
WAN 1 LAN 1
100.2.254.254/24 Private IP: 192.168.2.1/24
Local Network
IP Network
IP6510
Figure 6-1 IP Routing with Network Address Translation Example
NAT Address Example
admin> interface wan1 nat setup enable

1
→ Enable the NAPT feature on the WAN1 interface.
admin> interface wan1 ip 100.2.254.254/24
2
→ Set the WAN1 IP address
admin> interface lan1 ip 192.168.2.1/24
3
→ Set the LAN1 IP address
admin> interface wan1 nat address add 1 100.2.254.250 100.2.254.253
4
→ Set the public NAT IP address range for WAN1 port

NAT Static Example
admin> interface wan1 nat static add 100.2.254.250 192.168.2.2

1 → Add a static NAT forwarding list from the public IP address 100.2.254.250 to the private IP
address 192.168.2.2.
admin> interface wan1 nat static add 100.2.254.251 192.168.2.3
2 → Add a static NAT forwarding list from the public IP address 100.2.254.251 to the private IP
address 192.168.2.3.
NAPT Static Example
admin> interface wan1 napt setup enable

1
→ Enable the NAPT feature on the WAN1 interface.
2
3
admin> interface wan1 napt static add forward1 5 192.168.2.2
4
→ Add a static NAPT rule for the IP address with the TCP protocol over port 5.
admin> interface wan1 napt static add forward2 100 222 192.168.2.3
5
→ Add a static NAPT rule for the IP address with the TCP protocol over ports 100 to 222.

9.3 Port Forwarding Example and Instructions
ISP Public Remote PC

Public IP: 202.162.213.147/24/24
Gateway: 192.168.1.1
Public IP: 202.162.213.148/29

Gateway: 202.162.213.146
WAN1
IP6510
Port Forwarding
202.162.213.146:20 → 192.168.1.109:20
LAN1 202.162.213.146:21 → 192.168.1.109:21
IP Address: 202.162.213.146:80 → 192.168.1.109:80
192.168.1.1/24
202.162.213.146:443 → 192.168.1.109:443
202.162.213.146:8080 → 192.168.1.109:8080
FTP Server
Private IP: 192.168.1.109/24 Client
Gateway: 192.168.1.1 Private IP: 192.168.1.204/24
Gateway: 192.168.1.1
Figure 6-1 IP Routing with Network Address Translation Example

1
2
admin> interface wan1 napt setup enable
3
→ Turn on NAPT for the WAN1 port
admin> interface wan1 napt static add forward1 20 21 192.168.1.109
4
→ Add static NAPT forwarding for ports 20 and 21
5
→ Add static NAPT forwarding for port 80
6
7
NOTE Ports are uniquely allocated, so that when 202.162.213.146:20 is translated to 192.168.1.109:20,
another server cannot allocate port 21 anymore.

10 STP/RSTP Setup IP6510 Multiple WAN Router /Bridge
10 STP/RSTP Setup
10.1 Overview
The Spanning Tree Algorithm can be used to detect and disable network loops and to provide backup links
between bridges. This allows the device to interact with other STP/RSTP-compliant switches or bridges in a
network to ensure that only one route exists between any two stations on the network and to provide backup
links which automatically take over when a primary link goes down.
In Figure 9-1, below, the forwarding port in IP6510 #4 is blocked so that there can only be one path between
PC#1 and PC #2.
IP6510 #1 IP6510 #2
PC # 1 PC # 2
LAN 1 WAN 1 LAN 1
LAN1 WAN 1 LAN1
Blocked
IP6510 #3 IP6510 #4
Traffic Path
Figure 9- 1 Normal RSTP Link

In Figure 9-2, below, the WAN link between IP6510 #1 and IP6510 #2 has broken. The system immediately
removes the forwarding port block in IP6510 #4 so that there is still a path between PC #1 and PC #2.
WAN 1
PC #1 PC # 2
Link
LAN 1
Broken LAN1
PC1 to PC2
link is
recovered
LAN 1 WAN 1 LAN1

Port Block is
removed
Traffic Path
Figure 9- 2 Restored RSTP Link
In Figure 9-3, WAN 2 is blocked by RSTP. Only WAN1 can carry on the data transfer from PC#1 to PC#2.
WAN 1
LAN 1
PC # 1 WAN 2 LAN 2 PC # 2
Port Blocked
by RSTP
Traffic Path
Figure 9- 3 RSTP data transfer application #1

In Figure 9-4, when WAN1 is broken, the working path will switch immediately from WAN1 to WAN2 within 6
seconds.
WAN 1
Link
Broken
WAN 1
PC #1 LAN 1 WAN 2 LAN 2 PC #2

Port Block is PC1 to PC 2
removed link is
Traffic Path recovered
Figure 9- 4 RSTP data transfer application #2
The spanning tree algorithms supported by this device include:
STP – Spanning Tree Protocol (IEEE 802.1d)

RSTP – Rapid Spanning Tree Protocol (IEEE 802.1w)
Spanning tree algorithm uses a distributed algorithm to select a bridging device that serves as the root of the
spanning tree network. It selects a root port on each bridging device (except for the root device) which incurs
the lowest path cost when forwarding a packet from that device to the root device. Then it selects a
designated bridging device from each LAN, which incurs the lowest path cost when forwarding a packet from
that LAN to the root device. All ports connected to designated bridging devices are assigned as designated
ports. After determining the lowest cost spanning tree, it enables all root ports and designated ports, and
disables all other ports. Network packets are therefore only forwarded between root ports and designated
ports, eliminating any possible network loops.
Once a stable network topology has been established, all bridges listen for Hello BPDUs (Bridge Protocol
Data Units) transmitted from the Root Bridge. If a bridge does not get a Hello BPDU after a predefined
interval (Maximum Age), the bridge assumes that the link to the Root Bridge is down. This bridge will then
initiate negotiations with other bridges to reconfigure the network topology. RSTP is designed as a general
replacement for the slower, legacy STP. RSTP achieves much faster reconfiguration (i.e., around one tenth
of the time required by STP) when a node or port fails.

For optimal performance of the bridges it is recommended to use the default operational values for
performance parameters. These have been specified in order to avoid the need to set values prior to
operation. They have been chosen with a view to maximizing the ease with which Bridged LAN components
interoperate.
Table 9- 1 Transit and transmission delays
Parameter Recommended value Absolute maximum

Maximum bridge transit delay 1.0 4.0
Maximum BPDU transmission delay 1.0 4.0
Maximum Message Age increment overestimate 1.0 4.0
All times are in seconds.
Table 9- 2 (Rapid) Spanning Tree algorithm timer values
Recommended or Range
Parameter Fixed value
default value
Bridge Hello Time 2.0 — 1.0-10.0
Bridge Max Age 20.0 — 6.0-40.0
Bridge Forward Delay 15.0 — 4.0-30.0
Transmission Limit 3 — —
All times are in seconds.
Table 9- 3 Bridge and port priority parameter values
Parameter Recommended or default value Range

Bridge Priority 32768 0-61440 in steps of 4096
Port Priority 128 0-240 in steps of 16
To enable STP/RSTP service, a bridge group must be setup properly in advance.
admin>bridge br1 spantree setup enable

1
→ Enable Spanning Tree Protocol
admin> show bridge br1 config
NOTE → Type in this command to show the current bridge setup. If there is no interface in bridge mode,
please follow the steps described in Section 4.2 to switch the required interface to bridge mode.
admin> bridge br1 spantree priority 32768
2
→ Set the bridge priority value
admin> interface lan1 spantree priority 127
3
→ Set the LAN port priority
admin> interface wan1 spantree priority 127
4
→ Set the WAN port priority
admin> bridge br1 spantree age 25
5
→ Set the spantree Bridge Max Age (in seconds)
admin> bridge br1 spantree delay 20
6
→ Set the spantree Bridge Forward Delay (in seconds)
7 admin> bridge br1 spantree hello 4

→ Set the spantree Hello Time (in seconds)

admin>interface lan1 spantree cost 100
8
→ Set the LAN port cost value
admin>interface wan1 spantree cost 100
9
→ Set the WAN port cost value
admin>interface lan1 spantree link-type p-to-p
10
→ Set the LAN spantree link type
admin>interface wan1 spantree link-type p-to-p
11
→ Set the WAN spantree link type
admin>interface lan1 spantree edge-port enable
12
→ Set the LAN edge port to enable
admin>interface wan1 spantree edge-port enable
13
→ Set the WAN edge port to enable
The setup procedure is now complete. If you want to see what your setup looks like, type in the command
show bridge br1 spantree and press Enter. A sample display is shown below.
admin>show bridge br1 spantree
Spanning Tree protocol is enabled

protocol version: rstp
Bridge Information:
Bridge ID Hello Time Max Age Forward Delay Root Cost
========================================================================
Root 32768-008EA208A8D3 4 sec 25 sec 20 sec 0
This 32768-008EA208A8D3 4 sec 25 sec 20 sec 0
Port Information:
State Priority Cost Edge-port Link-type Root Port
========================================================================
lan1 Disabled 127 100 enabled p-to-p No
wan1 Disabled 127 100 enabled p-to-p No
Command succeeded

11 QoS (Quality of Service) IP6510 Multiple WAN Router /Bridge
11 QoS (Quality of Service)
11.1 Overview
In packet networks, one important requirement for link sharing is to share bandwidth on a link between
multiple agencies, where each agency wants to receive a guaranteed share of the link bandwidth during
congestion. But bandwidth that is not being used by one agency should be available to other agencies
sharing the link.
Quality of Service (QoS) is the idea that transmission rates, error rates can be measured, improved, and to
some extent guaranteed in advance. QoS enables you to provide better service to certain flows and helps
user to control the use of the outbound traffic on a given link. IP6510 QoS is policy based where the traffic
type defines each policy.
In the Loop-IP6510, we have classified the outgoing traffic (i.e. policy) by packet’s IP address, network
protocol, TCP/UDP port number, and/or DSCP value. User can configure the committed bandwidth for a
particular class of traffic by mentioning the minimum and maximum bandwidth. Users should make sure that
total configured bandwidth of all such policies do not exceed the link’s physical bandwidth.
Note: QoS is supported for WAN interfaces only.
11.2 Policy Syntax
10.2.1 Policy add

Interface inft policy qos rate_limit append selector action parameter
Instructs to put the newly created policy entry at the tail of the policy list.
selector If outgoing packets match criteria, the selector sets some matching
conditions. If the packet going through the interface matches the conditions,
then the rate_limit will be applied according to the parameters specified by
action-parameter. Format of the selector is as following:
src_ip [prefix] dest_ip [prefix] protocol [src_port] [dst_port] [dscp]
src_ip & [prefix] The source network address that is affected by the
policy. The parameter will be matched with source
address field of IP packets. The user can specify ‘any’ if
he/she is not interested in a specific IP address
dst_ip & [prefix] The interested destination network address. The
parameter will be matched with destination address field
of IP packets.
protocol Interested protocol type carried by an IP packet. The
field can be a decimal value or a protocol name, like
TCP or UDP.
src_port If protocol is TCP or UDP, user can mention the specific
source port number carried by an IP packet. User can
specify a range of source port or ‘any’ if he/she is not
interested for a particular source port number.
dst_port Interested destination port number for an IP packet if
protocol is TCP or UDP. User can mention destination
port number in minimum-maximum format for a range
of port number or ‘any’ if he/she is not interested for a
particular destination port number. Both

source/destination port number is a decimal value (1 to

65535)
dscp Diffrentiated Services Code Point (DSCP) is an integer
value encoded in the DS field of an IP header. The
DSCP is an example of traffic marking because its
value corresponds with a prefred QoS as the packet
traverses the network. The DSCP value corresponds to
a specific QoS. The six most significant bits of the
DiffServ field is called as the DSCP, which is basically
the six most significant bits of TOS byte in IP header.
So DSCP value range is 0-63.
action_parameter action_parameter controls the outgoing traffic flow rate for IP packet
matched the policy criteria specified by selector.
rate Committed access rate in minimum-maximum format.
The minimum rate is guaranteed the minimum rate of
the selected policy. When the maximum_rate is
mentioned in the action-parameter, the parameter is
specified the maximum rate of the selected policy. If
maximum_rate is not mentioned, it is used that
maximum rate is same as minimum rate.
type Unit of rate in kbps or mbps, specify the unit of
bandwidth in bits per sec.
10.2.2 Policy delete

Interface intf policy qos rate_limit delete [policy_num]
Instruct the policy to be deleted. Each policy is indexed by the policy number in the policy list, user
should mention the policy number which one to be removed.
10.2.3 Policy display

show interface intf policy qos
This CLI is used to display all policies user ever entered for WAN interface, shows all policy in the
policy list sequentially according to the policy number.


10 % Telnet
192.168.1.0/24 20% WWW

20% FTP
A(60 %)
50% other
wan-a-1 LAN 1
15% Telnet
192.168.2.0/24 30% WWW

IP6510
30% FTP
B(40%)
25% other
Local
wan-a-2 LAN 1 network
IP6510
Figure 10- 1 QoS Application
Two subnetworks, A and B are accessed through the wan-a-1 interface as depicted in the figure i.e. all
traffics of these networks are passed through wan-a-1 interface. Again each of A and B have different types
of traffic, say Telnet, WWW, FTP or so on.
Suppose Telnet of subnet A has a high traffic rate and consumes most of the bandwidth of wan-a-1. Other
services will be blocked, as wan-a-1 doesn’t have enough bandwidth compared to LAN1 and eventually some
traffic from LAN1 will be dropped. To solve this problem, policy rate limiting is installed on wan-a-1 to control
bandwidth distribution.
Suppose subnet A will have 60% of the available wan-a-1 bandwidth guaranteed; subnetwork B the rest
(40%). Within each subnetwork the guaranteed flows for each type of service are as as indicated in the
figure. Assume wan-a-1 has 1Mbps bandwidth, so telnet in subnet A will have 60 Kbps (10% of 60% of
1Mbps) guaranteed bandwidth, while FTP will have 120 Kbps. Corresponding commands for these Telnet
and FTP for subnet A are as follows:
admin>interface wan-a-1 policy qos rate_limit append 192.168.1.0/24 any tcp 23 any 60-60 kbps
Command succeeded
admin>interface wan-a-1 policy qos rate_limit append 192.168.1.0/24 any tcp 21 any 120 kbps
Command succeeded
For other 2 class of traffic in subnet A, type in the following commands:
admin>interface wan-a-1 policy qos rate_limit append 192.168.1.0/24 any any 80 any 120-120 kbps
Command succeeded
admin>interface wan-a-1 policy qos rate_limit append 192.168.1.0/24 any any 80 any 300 kbps
Command succeeded

The following are the commands to setup traffic distribution control for subnet B
admin>interface wan-a-1 policy qos rate_limit append 192.168.2.0/24 any TCP 23 any 60 kbps
Command succeeded
admin>interface wan-a-1 policy qos rate_limit append 192.168.2.0/24 any TCP 21 any 120-120 kbps
Command succeeded
admin>interface wan-a-1 policy qos rate_limit append 192.168.1.0/24 any 80 120 kbps
Command succeeded
admin>interface wan-a-1 policy qos rate_limit append 192.168.1.0/24 any 100 100
Command succeeded

12 OSPF Setup IP6510 Multiple WAN Router /Bridge
12 OSPF Setup
12.1 Overview
Figure 11-1 below illustrates the IP6510 being used in router mode..
Peer Router
IP 100.2.254.253
WAN 1 LAN 1
IP Network IP: 100.2.254.254 IP: 192.168.1.1 Local Network
MASK: 255.255.0.0 MASK: 255.255.255.0 with IP Address
IP: 160.2.254.253
Gateway: 255.255.0.0
IP6510
Network Address:
IP Router 100.3.0.0
255.255.0.0
Figure 11- 1 Router Setup (OSPF)
Open Shortest Path First Protocol (OSPFv2)

OSPF is an interior gateway protocol used for routing between routers belonging to a single Autonomous
System. OSPF uses link-state technology in which routers send each other information about the direct
connections and links which they have to other routers. Each OSPF router maintains an identical database
describing the Autonomous System's topology. From this database, a routing table is calculated by
constructing a shortest- path tree. OSPF recalculates routes quickly in the face of topological changes,
utilizing a minimum of routing protocol traffic. OSPF provides support for equal-cost multi-path. An area
routing capability is provided, enabling an additional level of routing protection and a reduction in routing
protocol traffic. In addition, all OSPF routing protocol exchanges are authenticated.
OSPF has been designed expressly for the TCP/IP internet environment, including explicit support for CIDR
and the tagging of externally-derived routing information. OSPF also provides for the authentication of routing
updates, and utilizes IP multicast when sending/receiving the updates.
OSPF routes IP packets based solely on the destination IP address found in the IP packet header. IP packets
are routed "as is" - they are not encapsulated in any further protocol headers as they transit the Autonomous
System.
OSPF allows sets of networks to be grouped together. Such a grouping is called an area. The topology of an
area is hidden from the rest of the Autonomous System. This information hiding enables a significant
reduction in routing traffic. Also, routing within the area is determined only by the area's own topology, lending
the area protection from bad routing data.
OSPF enables the flexible configuration of IP subnets. Each route distributed by OSPF has a destination and
mask. Two different subnets of the same IP network number may have different sizes (i.e., different masks).
This is commonly referred to as variable length subnetting. A packet is routed to the best (i.e., longest or
most specific) match.

12 OSPF Setup IP6510 Multiple WAN Router /Bridge
Set IP addresses for LAN1 and WAN1.
admin>interface lan1 ip 192.168.1.1/24

Command succeeded
admin>interface wan1 timeslot add 1-32

Command succeeded
admin>interface wan1 ip 100.2.254.254/16

Command succeeded
Type in the admin command route ospf area add 1 to create an area with ID 1.
admin>route ospf area add 1

Command succeeded
Set up the WAN1 interface. Type in the admin command interface wan1 route ospf setup enable 1 to
add WAN1 into area 1. Then press the Enter key.
admin>interface wan1 route ospf setup enable 1

Command succeeded
Save the configuration. Type in the command system configuration save. Then press the Enter key.
admin>system configuration save

Command succeeded
The setup procedure is now complete.

13 DHCP Setup IP6510 Multiple WAN Router /Bridge
13 DHCP Setup
13.1 DHCP Server overview
DHCP (Dynamic Host Configuration Protocol) can be used to automatically assign IP addresses, to deliver
TCP/IP stack configuration parameters (ie. subnet mask and default router), and to provide other
configuration information. Figure 12-1 below illustrates the IP6510 set up in a DHCP server application. All
hosts (shown on the right side of the network diagram) can get IP addresses from the IP6510 when its DHCP
Server is enabled.
IP6510
IP Network WAN 1 LAN 1 Host (DHCPClient)
Network Address: 192.168.1.0

Subnet Mask: 255.255.255.0
Host (DHCPClient)
..........
Figure 12- 1 DHCP Application

13.2 DHCP Server Setup
Use the command dhcp server subnet add to create a subnet which contains all necessary information
needed by DHCP clients. In the following example screen the subnet loop1 had been created.
admin>dhcp server subnet add loop1

Command succeeded
Once a subnet is created, we set network address. When the DHCP server allocate an IP address for a
client, the server will also send the client proper network address. The network address is 192.168.1.0/24.
admin>dhcp server subnet loop1 network 192.168.1.0/24

Command succeeded
An IP address range from 192.168.1.5 to 192.168.1.20 is for the subnet by type in command dhcp server
subnet loop1 ip_range.
admin>dhcp server subnet loop1 ip_rang 192.168.1.5 192.168.1.20

Command succeeded
The command dhcp server subnet domain_name works set works for domain name.
admin>dhcp server subnet loop1 domain_name works

Command succeeded
A DNS server 192.168.1.2 is set by command dhcp server subnet loop1 dns_server add.
admin>dhcp server subnet loop1 dns_server add 192.168.1.2

Command succeeded
To use command dhcp server interface add to add all LAN interfaces which offer DHCP service. As
following example, only the LAN1 is enabled for the service.
admin>dhcp server interface add lan1

Command succeeded
The command dhcp server enables the DHCP service.
[A]admin>dhcp server setup enable

...started, check status
Command succeeded
When the DHCP server is running, the hosts on network connected to LAN1 can use the DHCP to obtain IP
addresses.

13.3 DHCP Relay Overview
Deploying DHCP in a single subnet network is straightforward. DHCP messages are IP broadcast messages,
and all computers on the subnet can listen to and respond to these broadcasts. A single DHCP server is all
that is required.
It is complicated when there is more than one subnet on your network. This is because the DHCP broadcast
messages do not (by default) cross the router interfaces. The DHCP relay agent allows you to place DHCP
clients and DHCP servers on different subnets of your network or even to put them on different networks.
IP6510
WAN 1 LAN1
IP Network Host (DHCP Client)
DHCP Server DHCP Relay Server

10.3.2.10
Host (DHCP Client)
..........
Figure 12- 2 DHCP Relay Setup
13.4 DHCP Relay Setup
The following example illustrates how to enable a DHCP relay service with the IP6510.
admin>dhcp relay interface add lan1

Command succeeded
admin>dhcp relay server 10.3.2.10

Command succeeded
admin>dhcp server setup enable

...started, check status
Command succeeded

14 Firmware/Config Upload and Download With TFTP IP6510 Multiple
WAN Router /Bridge
14 Firmware/Config Upload and Download With TFTP
14.1 Overview
Firmware/Download and Configuration Upload/Download functions can be performed with the TFTP server on the
LAN side or with the TFTP server on an outside network.
14.2 Setting Up a TFTP Server

Figure 13-1, below illustrates a setup example for the Loop-IP6510 firmware configuration upload and download.
The TFTP Server is on the LAN side. The IP addresses and gateway addresses used in the diagram correspond
to the step by step configuration instructions found in Section 13.3 below.
Figure 13- 1 Setting Up the TFTP Server
NOTE: In this application the Loop-IP6510 and the TFTP Server are in the same subnet. Connect a cable
between the COM port of your PC and the Console port of the IP6510. The TFTP Server is connected
to the LAN1 Port of the Loop-IP6510.

14 Firmware/Config Upload and Download With TFTP IP6510 Multiple
WAN Router /Bridge

Before doing configuration firmware data transfer, a bridge group should be created with management IP
10.0.7.100. Follow chapter 5 to do this.
To upload configuration proceed to section 13.3.1 Configuration Upload.

To download configuration proceed to section 13.3.2 Configuration Download.
To download firmware proceed to section 13.3.3 Firmware Download.
14.3.1 Configuration Upload
Type in the admin command system configuration copy startup_cfg tftp://, followed by the IP address of the
TFTP Server, followed by /IP6510_config. Then press Enter. Your screen will tell you if the command
succeeded.
admin>system configuration copy startup tftp://10.0.7.1/IP6510_config

command succeeded
In your TFTP server, you will see the configuration file, IP6510_config.
14.3.2 Configuration Download
Type in the admin command system configuration copy tftp://, followed by the IP address of the TFTP Server,
followed by the name of the configuration file on the TFTP server, followed by startup.
Press Enter. Your screen will tell you if the command succeeded. You must now reset the system to let the
downloaded configuration take effect. To do so, type in the admin command system reboot and then press
Enter. Resetting can also be done by powering down the unit and then powering it up again.
admin>system configuration copy tftp://10.0.7.1/IP6510_config startup

command succeeded
adm in>system reboot
14.3.3 Firmware Download

Type in the admin command system firmware load tftp://, followed by the IP address of the TFTP Server,
followed by the firmware filename on the TFTP server. Then press Enter. Your screen will appear as shown
below. You must now reset the system to let the downloaded firmware take effect. To do so, type in the admin
command system reboot and then press Enter. Resetting can also be done by powering down the unit and then
powering it up again.
admin>system firmware load tftp://10.0.7.1/ip6510_v1.1.1.rom

1551424 bytes received.
Download succeeded! Please reboot the system first!
Command succeeded
admin>system reboot

15 Operation Commands IP6510 Multiple WAN Router /Bridge
15 Operation Commands
This chapter describes the IP6510 configuration options and operational functions. Each command requires
a certain user privilege.
15.1 Ping Command

Command: ping
Privilege: operator
Syntax: ping address [-l packet_size] [-w timeout]
Explanation: Issue ICMP echo request to a host, once the command is issued, it periodically send ICMP
echo requests to the host. The user presses ESC to quit from the command.
Parameters: address The destination address of the ICMP packets.
[packet_size] How many bytes to be carried by the ICMP packets. (1 to 1500)
[timeout] Timeout in milliseconds to wait for each reply (1 to 5000)
15.2 Traceroute Command

Command: traceroute
Privilege: operator
Syntax: traceroute address [-l max_hops] [-w timeout]
Explanation: Issue trace route requests
Parameters: address The destination address of the ICMP packets.
[timeout] Timeout in milliseconds to wait for each reply (1 to 5000)
[max_hops] Maximum number of hops to search for target (1 to 50)
15.3 Bridge Command

Command: bridge create
Privilege: admin
Syntax: bridge create name [mac]
Explanation: This command will create a bridge group with a management virtual interface, which using
the mac address specified. If the mac address is not specified, a random address will be
generated for the bridge group. This generated address might conflict with other device.
Note: This device only supports one bridge group.
Parameters: name The bridge group name to be created
[mac] mac address for this bridge group. If no mac address is specified, a random
address will be generated for the bridge group.
Command: bridge destroy

Privilege: admin
Syntax: bridge destroy name
Explanation: Destroy the specified bridge group. All the interface belongs to this bridge group will be
removed from this bridge group first.
Parameters: name The bridge brg_name group name will be destroyed.
In the following commands, please replace “brg_name” with the real bridge group name in your system.
Command: bridge brg_name add

Privilege: admin
Syntax: bridge brg_name add [interface]
Explanation: Add interface(s) into the specified bridge group; that interface(s) will be in bridge mode and
its router feature will be invalid.
Parameters: [interface] name of the interface to be added.
If no interface is specified, all the interfaces will be add to the bridge group.

Command: bridge brg_name age

Privilege: admin
Syntax: bridge brg_name age time
Explanation: Set maximum age of auto-learned MAC addresses.
Parameters: time The maximum age. (in seconds)
Command: bridge brg_name delete

Privilege: admin
Syntax: bridge brg_name delete [interface]
Explanation: Remove an interface from a bridge group.
Parameters: [interface] name of the interface to be deleted. If no interface is specified, all the interfaces
will be deleted from the bridge group.
Command: bridge brg_name fcs

Privilege: admin
Syntax: bridge brg_name fcs setting
Explanation: Enable/disable the original Ethernet frame checksum.
Parameters: setting enable/disable
Command: bridge brg_name ip

Privilege: admin
Syntax: bridge brg_name ip address
Explanation: Set IP address on the virtual management interface for this bridge group. After setting the ip
address, this bridge group is remote manageable.
Parameters: address The management IP. (xxx.xxx.xxx.xxx/xx)
Command: bridge brg_name management

Privilege: admin
Syntax: bridge brg_name management enable/diable
Explanation: Enable/disable bridge management feature.
Parameters: enable/diable enable/disable
Command: bridge brg_name spantree age

Privilege: admin
Syntax: bridge brg_name spantree age value
Explanation: Sets the maximum age of received protocol information before it is discarded. That is, when
this router is the root bridge, if a non-root bridge has not received a hello message within
the time period set by maximum age, the non-root bridge assumes that a network failure
has occurred and the bridges can begin reconfiguring the network.
Parameters: value the maximum age (in seconds) of received protocol information before it is
discarded. The possible values range from 6 to 40.seconds. The default value
is 20 seconds
Note: The default value of 20 seconds is recommended in the STP/RSTP. If you change
this value, the following relationships must be observed: 2 x (Bridge_Forward_Delay – 1.0
seconds) >= Bridge_Max_Age Bridge_Max_Age >= 2 x (Bridge_Hello_Time + 1.0
seconds)
Command: bridge brg_name spantree delay

Privilege: admin
Syntax: bridge brg_name spantree delay value
Explanation: Set a bridge’s spanning tree delay value
Parameters: value the time in seconds that bridge use for forward delay. The possible value range
from 4 to 30 seconds. The default value is 15 seconds
Note: The default value of 15 seconds is recommended in the STP/RSTP. If you
change this value, the following relationship must be observed:
2 x (Bridge_Forward_Delay – 1.0 seconds) >= Bridge_Max_Age

Command: bridge brg_name spantree hello

Privilege: admin
Syntax: bridge brg_name spantree hello value
Explanation: This command sets how often (in seconds) the root bridge sends out BPDU hello
messages. At any instant in STP/RSTP, one bridge is the root bridge. The root bridge
generates a hello message periodically. All other network bridges wait for hello messages.
If a bridge does not get a hello message in the expected time, it presumes network
malfunctions and notifies other bridges that the network transmission paths must be
reconfigured. When this device is the root bridge, all other bridges use this device's hello
time value.
Parameters: value the time interval for the root bridge sends out BPDU hello messages. The
possible value is 1 to 10. The default value is 2 seconds
Note: A hello time value that is too low results in many BPDU hello messages being sent
over the network, possibly creating excessive traffic on the network. A value that is too
high slows the response to network topology changes. The default value of 2 seconds
is recommended in 802.1d/802.1w. If you change this value, the following relationship
must be obeyed:
Bridge_Max_Age >= 2 x (Bridge_Hello_Time + 1.0 seconds)
Command: bridge brg_name spantree priority

Privilege: admin
Syntax: bridge brg_name spantree priority value
Explanation: Set a bridge’s spanning tree priority value.
Sets the priority for specified bridge group. The lower the bridge’s priority, the more likely to
be selected as the root bridge
Parameters: value the value can be set from 0 to 65535. The value 0 is the highest priority. Default
value is 32768.
Command: bridge brg_name spantree setup

Privilege: admin
Syntax: bridge brg_name spantree setup setting
Explanation: Enable/disable spanning tree feature
Command: bridge brg-name svlan

Privilege: admin
Syntax: bridge brg-name svlan setup
Explanation: Enable/disable VLAN Feature. After enabling the VLAN feature, the default VLAN(vid:1) will
be created automatically, and all ports will become untagged members of VLAN 1. If
disables the VLAN feature, the bridge group will become VLAN-unware.
Parameters: Enable/disable enable/disable
Command: bridge brg_name svlan add

Privilege: admin
Syntax: bridge brg_name svlan add vid interface [sub_interface]
Explanation: Add one port to be a member of one SVLAN.
Parameters: vid SVLAN ID. Range from 1-4094
interface Interface Name. (lan1 to lan4/wan1 to wan2/wan-a-1 to wan-b-2)
Command: bridge brg_name svlan create

Privilege: bridge brg_name svlan create admin
Syntax: vid
Explanation: Create a SVLAN.

Command: bridge brg_name svlan dei

Privilege: admin
Syntax: bridge brg_name svlan dei action
Explanation: set the svlan tag drop eligible indicator bit
Parameters: action enabled/disabled
Command: bridge brg-name svlan delete

Privilege: admin
Syntax: bridge brg-name svlan delete vid interface [sub-interface]
Explanation: Remove a port from one SVLAN.
interface Interface Name. (lan1 to lan4/wan1 to wan2/wan-a-1 to wan-b-2)
Command: bridge brg_name svlan destroy

Privilege: admin
Syntax: bridge brg_name svlan destroy vid
Explanation: Deactivate a SVLAN.
Command: bridge brg-name svlan mgmt

Privilege: admin
Syntax: bridge brg-name svlan mgmt vid
Explanation: set management SVLAN ID for the bridge
Command: bridge brg-name svlan pcp

Privilege: admin
Syntax: bridge brg-name svlan pcp value
Explanation: set the svlan tag priority code point
Parameters: value 0-7
Command: bridge brg-name svlan regencrc

Privilege: admin
Syntax: bridge brg-name svlan regencrc action
Explanation: Enable/disable regenerating CRC on WAN interface for SVLAN frames.
Command: bridge brg-name svlan tpid

Privilege: admin
Syntax: bridge brg-name svlan tpid value
Explanation: Set the svlan tag etype
Parameters: value 2 bytes, default value 8100
Command: bridge brg_name vlan

Privilege: admin
Syntax: bridge brg_name vlan setup
Explanation: Enable/disable VLAN Feature. After enabling the VLAN feature, the default VLAN (vid:1) will
be created automatically, and all ports will become untagged members of VLAN 1. If
disables the VLAN feature, the bridge group will become VLAN-unware.
Parameters: Enable/disable enable/disable

Command: bridge brg_name vlan add

Privilege: admin
Syntax: bridge brg_name vlan add vid tag/untag intf
Explanation: Add one port to be a tagged or untagged member of one created VLAN in a bridge group.
Parameters: vid bridge brg_name VLAN ID. Range from 1-4094
tag/untag Tagged port or untagged port
intf Interface Name. (lan1 to lan4/wan1 to wan2/wan-a-1 to wan-b-2)
Command: bridge brg_name vlan create

Privilege: admin
Syntax: bridge brg_name vlan create vid
Explanation: Except VLAN 1(default VLAN), each VLAN needs to be created before use.
This command will create a VLAN in a bridge group.
Command: bridge brg_name vlan delete

Privilege: admin
Syntax: bridge brg_name vlan delete vid tag/untag intf
Explanation: Delete a tagged or an untagged port from a created VLAN in a bridge group.
tag/untag Tagged port or untagged port
intf Interface Name (lan1 to lan4/wan1 to wan2/wan-a-1 to wan-b-2)
Command: bridge brg_name vlan destroy

Privilege: admin
Syntax: bridge brg_name vlan destroy vid
Explanation: If a created VLAN will not be used, use this command to destroy it. Default VLAN (vid:1)
cannot be destroyed.
Parameters: vid VLAN ID. Range from 1-4094
Command: bridge brg_name vlan mgmt

Privilege: admin
Syntax: bridge brg_name vlan mgmt vid
Explanation: For each bridge group, it will have an interface for management. This interface should
belong to one created VLAN. It means only hosts in this VLAN could communicate with the
interface. By default, this interface will belong to VLAN 1.
Command: bridge brg_name vlan regencrc

Privilege: admin
Syntax: bridge brg_name regencrc setting
Explanation: Enable/disable regenerating CRC on WAN interface for bridge brg_name frames.
Parameters: setting enable/disable (Default: disabled)
Note: Enable this feature will reduce the performance for bridge forwarding.
15.4 DHCP Commands
Command: dhcp relay interface add

Privilege: admin
Syntax: Dhcp relay interface add interface
Explanation: Add interface(s)/bridge mgmt(s) which the DHCP relay should listen to so that any request
from a DHCP client on that interface(s) will be forwarded to the server. If no interface
names are specified, it will identify all network interfaces/bridge mgmt interfaces and
exclude those interfaces which have no IP address
Parameters: interface lan1 to lan4/bridge_group_name

Command: dhcp relay interface delete

Privilege: admin
Syntax: Dhcp relay interface delete interface
Explanation: Exclude the interface(s)/bridge mgmt(s) from theDHCP relay so that any request from a
DHCP client on that interface(s) will not be forwarded to server
Command: dhcp relay server

Privilege: admin
Syntax: Dhcp relay server address
Explanation: Set DHCP server IP address to which DHCP and BOOTP requests should be relayed
Parameters: address IP address (xxx.xxx.xxx.xxx)
Command: dhcp relay setup

Privilege: admin
Syntax: Dhcp relay setup setting
Explanation: Enable/Disable DHCP relay features on the device. Note that DHCP server and relay
cannot be enabled simultaneously. Once the relay feature is enabled, any configuration
change for the relay will not take affect until the user disables and enables it again
Parameters: Setting enable/disable
Command: dhcp server host add

Privilege: admin
Syntax: Dhcp server host add name
Explanation: Hosts which require special configuration options can be added by this command. If no
address is specified in the following command, the address will be allocated dynamically (if
possible), but the host-specific information will still come from the host declaration
Parameters: Name unique name of host (<16 bytes)
Command: dhcp server host delete

Privilege: admin
Syntax: Dhcp server host delete name
Explanation: Delete the DHCP host so that all configurations for the host will be lost
Parameters: Name host name in configuration
Command: dhcp server host host_name bootfile

Privilege: admin
Syntax: Dhcp server host host_name bootfile filename
Explanation: Specifies the name of the file that is used as a boot image which is to be loaded by a client
from the next-server
Parameters: filename bootstrap file name (< 64 bytes) or NULL to remove setting
Command: dhcp server host host_name client_id

Privilege: admin
Syntax: Dhcp server host host_name client_id id
Explanation: Sets the DHCP host client identifier. This client id is matched to the actual DHCP or BOOTP
client’s identifier supplied by the client, or, if the host declaration or the client does not
provide a dhcp-client-identifier, by matching the hardware parameter in the host declaration
to the network hardware address supplied by the client.
Parameters: id client identifier (may be htype/chaddr) or NULL to remove s
etting
Command: dhcp server host host_name fixed_addr

Privilege: admin
Syntax: Dhcp server host host_name fixed_addr address
Explanation: Sets the DHCP host ip address. The fixed-address command is used to assign one fixed IP
addresses to a client
Parameters: address IP address (xxx.xxx.xxx.xxx) or NULL to remove setting

Command: dhcp server host host_name hardware

Privilege: admin
Syntax: Dhcp server host host_name hardware type address
Explanation: Sets the host hardware type/address. Specifies the MAC address of the client's hardware
and the physical hardware interface type in order for a BOOTP client to be recognized
Parameters: type ETHERNET/TOKEN-RING/FDDI or NULL to remove setting
address h/w address specific to h/w type
Command: dhcp server host host_name lease

Privilege: admin
Syntax: Dhcp server host host_name lease time
Explanation: Sets the DHCP host default duration of the lease; i.e., the duration of the lease for an IP
address that is assigned from a DHCP Server to a DHCP client
Parameters: time default lease time in secs or NULL to remove setting
Command: dhcp server host host_name next_server

Privilege: admin
Syntax: Dhcp server host host_name next_server address
Explanation: Specifies the IP address of the next server in the boot process, which is typically a Trivial
File Transfer Protocol (TFTP) server
Command: dhcp server host host_name option

Privilege: admin
Syntax: Dhcp server host host_name option code value
Explanation: Sets the DHCP host option by code (max 8 options). Apart from the above settings for a
host, if the user needs to mention some special configurations, he/she can use this
command, but the user needs to take care that the option code and corresponding value
are in proper format
Parameters: code option code from RFC 2132 (1 to 255)
value option value (< 64 bytes) or NULL to remove setting
Command: dhcp server interface add

Privilege: admin
Syntax: Dhcp server interface add interface
Explanation: Add interface(s)/bridge mgmt(s) to the DHCP server. The name of the network interface(s)/
bridge mgmt(s) on which the DHCP server should listen for client’s request may be
specified by this command line. If no interface names are specified it will identify all network
interfaces/bridge mgmt interfaces and exclude those interfaces which have no IP address.
Command: dhcp server interface delete

Privilege: admin
Syntax: Dhcp server interface delete interface
Explanation: Exclude the interface(s)/bridge mgmt(s) from DHCP server so that any request from a
DHCP client on that interface(s) will be ignored by the server
Command: dhcp server setup

Privilege: admin
Syntax: Dhcp server setup setting
Explanation: Enables/Disables the DHCP server feature on the device. Note that the DHCP server and
relay cannot be enabled simultaneously. Once the server is enabled, any configuration
change for the server will not take effect until the user disables and enables it again
Parameters: Setting enable/disable
Command: dhcp server subnet add

Privilege: admin
Syntax: Dhcp server subnet add name
Explanation: Add the DHCP subnetto the server, so that when a request is received from a DHCP client,
the server can assign an IP address and other necessary parameters to the client. Note that
user must add a subnet for each configured interface on which he/she WANts to run DHCP
server
Parameters: Name unique name of subnet (<16 bytes)
Command: dhcp server subnet delete

Privilege: admin
Syntax: Dhcp server subnet delete name
Explanation: Deletes the DHCP subnet so that all configurations for the subnet will be lost
Parameters: Name subnet name in configuration
Command: dhcp server subnet subnet_name bootfile

Privilege: admin
Syntax: Dhcp server subnet subnet_name bootfile filename
Explanation: Specifies the name of the file that is used as a boot image which is to be loaded by a client
from next-server
Parameters: filename bootstrap file name (< 64 bytes) or NULL to remove setting
Command: dhcp server subnet subnet_name bootp

Privilege: admin
Syntax: Dhcp server subnet subnet_name bootp support
Explanation: Enables/disables the BOOTP support for the subnet. If enabled, any request from a BOOTP
client will be accepted by the DHCP server, otherwise it will be silently discarded.
Parameters: support enable/disable
Command: dhcp server subnet subnet_name dns_server add

Privilege: admin
Syntax: Dhcp server subnet subnet_name dns_server add address
Explanation: Configures the Domain Name System (DNS) IP servers available to the client. User can
add 4 DNS servers by this command. If the DNS server is not configured, the client cannot
correlate host names to IP addresses
Parameters: address IP address (max 4 address)
Command: dhcp server subnet subnet_name dns_server delete

Privilege: admin
Syntax: Dhcp server subnet subnet_name dns_server delete address
Explanation: Deletes the DNS servers already configured
Parameters: address ip address or “all” to delete all setting
Command: dhcp server subnet subnet_name domain_name

Privilege: admin
Syntax: Dhcp server subnet subnet_name domain_name name
Explanation: Specifies the client's domain name string
Parameters: name domain name system (<32 bytes) or NULL to remove setting
Command: dhcp server subnet subnet_name ip_range

Privilege: admin
Syntax: Dhcp server subnet subnet_name ip_range start_addr end_addr
Explanation: Specifies the pool of IP addresses in the subnet that can be assigned to DHCP clients. The
address pool must be in the same network segment or subnet
Parameters: start_addr start IP address or NULL to remove setting
end_addr end ip address
Command: dhcp server subnet subnet_name lease

Privilege: admin
Syntax: Dhcp server subnet subnet_name lease time
Explanation: Set DHCP subnet default duration of lease

Sets the default duration of a lease for an IP address that is assigned from a DHCP Server
to a client
Parameters: time default lease time in secs to remove setting
Command: dhcp server subnet subnet_name nbns add

Privilege: admin
Syntax: Dhcp server subnet subnet_name nbns add address
Explanation: Specifies the IP address of the NetBIOS WINS name server. This is used to configure
NetBIOS Windows Internet Naming Service (WINS) name servers for Microsoft DHCP
clients.
Command: dhcp server subnet subnet_name nbns delete

Privilege: admin
Syntax: Dhcp server subnet subnet_name nbns delete address
Explanation: Deletes the NetBIOS WINS name server already configured
Parameters: address ip address or “all” to delete all setting
Command: dhcp server subnet subnet_name netb_type

Privilege: admin
Syntax: Dhcp server subnet subnet_name netb_type type
Explanation: Specifies the NetBIOS node type for Microsoft DHCP clients. Valid types are:
 B-node Broadcast
 P-node Peer-to-peer
 M-node Mixed
 H-node Hybrid
Parameters: type B-node, P-node, M-node or H-node or NULL
Command: dhcp server subnet subnet_name network

Privilege: admin
Syntax: Dhcp server subnet subnet_name network address
Explanation: Configures the network number and prefix for a DHCP address pool. The network-
number/prefix uniquely identifies the subnet so that DHCP server first identifies the subnet
from a client request it receives, and assigns a IP address from that subnet address pool
Parameters: address subnet IP address (xxx.xxx.xxx.xxx/xx) or NULL to remove setting
Command: dhcp server subnet subnet_name next_server

Privilege: admin
Syntax: Dhcp server subnet subnet_name next_server address
Explanation: Specifies the IP address of the next server in the boot process, which is typically a Trivial
File Transfer Protocol (TFTP) server
Command: dhcp server subnet subnet_name option

Privilege: admin
Syntax: Dhcp server subnet subnet_name option code value
Explanation: Sets DHCP options by code (max 8 options). Apart from the above settings for a host, if the
user needs to mention some special configurations, he/she can use this command, but the
user needs to take care the option code and corresponding value are in the proper formats.
Parameters: code option code from RFC 2132 (1 to 255)
value option value (<64 bytes) or NULL to remove setting
Command: dhcp server subnet subnet_name router add

Privilege: admin
Syntax: Dhcp server subnet subnet_name router add address
Explanation: Specifies the IP address of the default router in the subnet

Command: dhcp server subnet subnet_name router delete

Privilege: admin
Syntax: Dhcp server subnet subnet_name router delete address
Explanation: Deletes the router for the subnet already configured
Parameters: address IP deleteress (max 4 deleteress)
15.5 Interface Commands

The interface commands are always associated with an interface name (ex. Interface lan1). To simply the
syntax description, following commands use intf as the interface name.
Command: interface intf chdlc

Privilege: admin
Syntax: interface intf chdlc interval timeout
Explanation: Set Cisco HDLC Parameters
Parameters: interval Keep-alive interval (1-3600, default is 10 secs)
timeout Interface restart timeout (seconds, should be multiple of interval)
Command: interface intf encapsulation

Privilege: Admin
Syntax: interface intf encapsulation protocol
Explanation: Set layer2 encapsulation protocol
Parameters: protocol Layer 2 encapsulation
Command: interface intf e1 alarm

Privilege: admin
Syntax: interface intf e1 alarm type setting [severity] [value]
Explanation: Set T1 alarm type, Severity, threshold
Parameters: type alarm type (clock_loss/rai/ais/los/lof/bpv/es/uas/css/all)
setting disable/enable
[severity] Critical, major, minor, warning, informative cleared
[value] The value for the specific alarm’s threshold
Command: interface intf e1 bert

Privilege: admin
Syntax: interface intf e1 bert type
Explanation: Perform Bit Error Rate Tests (BERT)
Parameters: type full/data/idle/none (none to deactivate the diagnostic)
Command: interface intf e1 code

Privilege: admin
Syntax: interface intf e1 code type
Explanation: Define the line code
Parameters: type AMI/HDB3
Command: interface intf e1 crc

Privilege: admin
Syntax: interface intf e1 crc setting
Explanation: Enable or disable E1 CRC check
Command: interface intf e1 frame

Privilege: Admin
Syntax: interface intf e1 framing mode
Explanation: Define the framing characteristics
Parameters: mode FAS/none
Command: interface intf e1 idle_code

Privilege: admin
Syntax: interface intf e1 idle_code code
Explanation: Define the unused channel idle code
Parameters: code Idle code (0 to 255)
Command: interface intf e1 loopback activate

Privilege: admin
Syntax: interface intf e1 loopback activate type
Explanation: Activate loopback function
Parameters: type Loopback type (line/payload)
Command: interface intf e1 loopback deactivate

Privilege: admin
Syntax: interface intf e1 loopback deactivate
Explanation: Deactivate loopback function
Command: interface intf e1 loopback timer

Privilege: admin
Syntax: interface intf e1 loopback timer timing
Explanation: Set loopback function timer. When the loopback timer is enabled, the system deactivates a
loopback after the specified period. (The system sets loopback timer to 60 seconds by
default.)
Parameters: timing Loopback timing in seconds (0 to 86400)
0: disable the loopback timer
Command: interface intf e1 mf

Privilege: admin
Syntax: interface intf e1 pattern mf setting
Explanation: Enable or disable TS16 multi-framing
Parameters: setting enable / disable
Command: interface intf e1 pattern

Privilege: admin
Syntax: interface intf e1 pattern ch type
Explanation: Send test pattern
Parameters: ch full / data / idle / none
type The pattern type (3-in-24/1-in-8/2-in-8/1:1/none)
Command: interface intf e1 performance clear

Privilege: admin
Syntax: interface intf e1 performance clear
Explanation: Clear performance reports and alarm error count
Command: interface intf e1 primary_clock

Privilege: admin
Syntax: interface intf e1 primary_clock source
Explanation: Set primary clock source
Parameters: source internal/port1/port2
Command: interface intf e1 rai

Privilege: admin
Syntax: interface intf e1 rai setting
Explanation: Enable or disable E1 RAI (Remote Alarm Indication) setting
Command: interface intf e1 secondary_clock

Privilege: admin
Syntax: interface intf e1 secondary_clock source

Explanation: Set secondary clock source

Parameters: source internal/port1/port2
Command: interface intf mtu

Privilege: admin
Syntax: interface intf mtu
Explanation: Set the maximum transmission unit for a packet
Parameters: size 54~1532 bytes
Command: interface intf nway auto

Privilege: admin
Syntax: interface intf nway auto
Explanation: Enable auto negotiation to set up link speed/duplex.
Parameters: none
Command: interface intf nway force

Privilege: admin
Syntax: interface intf nway force speed duplex
Explanation: Force mode to set up link speed and duplex.
Parameters: speed 10/100
duplex full/half
Command: interface intf route ospf auth-key message-digest-key

Privilege: admin
Syntax: interface intf route ospf auth-key message-digest-key
Explanation: Set OSPF MD5 authentication key. Assign a password to be used by neighboring OSPF
routers on a network segment that is using OSPF’s MD5 password authentication.
Parameters:
Command: interface intf route ospf auth-key text-key

Privilege: admin
Syntax: interface intf route ospf auth-key text-key
Explanation: Set OSPF text format authentication key. Assign a password to be used by neighboring
OSPF routers on a network segment that is using OSPF’s simple password authentication.
Parameters:
Command: interface intf route ospf cost

Privilege: admin
Syntax: interface intf route ospf cost value
Parameters: value Valid values are 1 to 65535
Command: interface intf route ospf dead

Privilege: admin
Syntax: interface intf route ospf dead value
Explanation: Set the number of seconds that a device’s hello packets must not have been seen before its
neighbors declare the OSPF router down. This value must be the same for all routers
attached to a common network. The default value is 40 seconds.
Parameters: value the number of seconds to wait before sending another packet (Valid values
are 1 to 65535)
Command: interface intf route ospf hello

Privilege: admin
Syntax: interface intf route ospf hello value
Explanation: Set the number of seconds between hello packets sent on an OSPF interface. This value
must be the same for all routers attached to a common network. The default value is 10
seconds.
Parameters: value the number of seconds to wait before sending another packet ( Valid values
are 1 to 65535)

Command: interface intf route ospf prior

Privilege: admin
Syntax: interface intf route ospf prior value
Explanation: Set priority to help determine the OSPF designated router for a network. By setting a higher
value, the router will be more eligible to become the Designated Router. By setting the value
to 0, the router will no longer be eligible to be the Designated Router. The default value is 1.
Parameters: value ( Valid values are 0 to 255)
Command: interface intf route ospf retransmit

Privilege: admin
Syntax: interface intf route ospf retransmit value
Explanation: Specify the number of seconds between link state advertisement retransmissions for
adjacent OSPF routers linked to this interface. This value is used when re-transmitting
Database Description and Link State Request packets. The default value is 5 seconds.
are 1 to 65535)
Command: interface intf route ospf transmit

Privilege: admin
Syntax: interface intf route ospf transmit value
Explanation: Set the estimated number of seconds it takes to transmit a link state update packet on an
OSPF interface. The LSAs’ age should be incremented by this value when transmitting. The
default value is 1 second.
are 1 to 65535)
Command: interface intf route ospf setup

Privilege: admin
Syntax: interface intf route ospf setup setup [area_id]
Explanation: Enable/Disable OSPF for a specified interface
Parameters: setup enable/disable
[area_id] 0 to 4294967295
Command: interface intf spantree cost

Privilege: admin
Syntax: interface intf spantree cost value
Explanation: Set port cost for spanning tree
Parameters: value cost value. Assign lower number to faster media (1-65535)
Command: interface intf spantree edge_port

Privilege: admin
Syntax: interface intf spantree edge_port setting
Explanation: Enable/disable edge-port feature. This indicates that this port/interface is known to be on
the edge of a bridged LAN.
Command: interface intf spantree link_type

Privilege: admin
Syntax: interface intf spantree link_type type
Explanation: Set link type to the following three ways.
- auto: The switch will auto detect the link type. (This is the default value)
- p-to-p: The link is a point-to-point link to another device.
- shared: The link is a shared segment and can contain more than one device.
Parameters: type type of link (auto/p-to-p/shared)
Command: interface intf spantree priority

Privilege: admin
Syntax: interface intf spantree priority value
Explanation: Sets a spanning tree priority for a port, which will be used to break the tie when two (or
more) ports connected to the same bridge towards the root bridge tie for position as the root
port. The port with the lowest port priority will forward (be root port) and the other port(s) will
block (be alternate port).
Parameters: value port priority (0-255). Default value is 128.
Command: interface intf svlan ingress-filter

Privilege: admin
Syntax: interface intf svlan ingress-filter action
Explanation: enable/disable ingress filtering for one port.
Command: interface intf svlan port-type

Privilege: admin
Syntax: interface intf svlan port-type type
Explanation: set the acceptable frame type of one port
Parameters: type provider/customer
Command: interface intf svlan pvid

Privilege: admin
Syntax: interface intf svlan pvid vid
Explanation: set Interface PVID
Command: interface intf t1 address

Privilege: admin
Syntax: interface intf t1 address type
Explanation: Set T1 address type
Parameters: type CSU/TE (for T1 only)
Command: interface intf t1 alarm

Privilege: admin
Syntax: interface intf t1 alarm type setting [severity] [threshold]
Explanation: Set T1 alarm type, Severity, threshold
Parameters: type alarm type (clock_loss/yel/los/lof/bpv/es/uas/css/ais/all)
setting disable/enable
[severity] Alarm Severity (critical, major, minor, warning, informative cleared)
[threshold] 5 to 900 for BPV, for all others its 1 to 9.
Command: interface intf t1 bert

Privilege: admin
Syntax: interface intf t1 bert ch
Explanation: Perform Bit Error Rate Tests (BERT)
Parameters: ch full/data/idle/none (none to deactivate the diagnostic)
Command: interface intf t1 code

Privilege: admin
Syntax: interface intf t1 code type
Parameters: type AMI/B8ZS
Command: interface intf t1 frame

Privilege: admin
Syntax: interface intf t1 frame type
Explanation: Define the framing characteristics
Parameters: type D4/ESF/ESF&T1.403
Command: interface intf t1 idle_code

Privilege: admin

Syntax: interface intf t1 idle_code code

Explanation: Define the unused channel idle code
Parameters: code Idle code (0 to 255)
Command: interface intf t1 linecode

Privilege: admin
Syntax: interface intf t1 linecode type
Parameters: type for T1: AMI/B8ZS
Command: interface intf t1 lbo

Privilege: admin
Syntax: interface intf t1 lbo type
Explanation: Set T1 line LBO
Parameters: type 0dB/-7.5dB/-15dB
Command: interface intf t1 loopback

Privilege: admin
Syntax: interface intf t1 loopback deactivate
Command: interface intf t1 loopback deactivate

Privilege: admin
Syntax: interface intf t1 loopback deactivate
Command: interface intf t1 loopback inband

Privilege: admin
Syntax: interface intf t1 loopback inband setup
Explanation: Enable/disable inband loopback code detector
Parameters: setup Enable / Disable
Command: interface intf t1 loopback local activate

Privilege: admin
Syntax: interface intf t1 loopback local activate type
Explanation: Activate local loopback function
Parameters: type line / payload
Command: interface intf t1 loopback remote activate

Privilege: admin
Syntax: interface intf t1 loopback remote activate type
Explanation: Activate remote loopback function
Parameters: type in-band/at&t-payload/ansi-payload/ansi-line)
Command: interface intf t1 loopback timer

Privilege: admin
Syntax: interface intf t1 loopback timer timing
Explanation: Set loopback function timer. When the loopback timer is enabled, the system deactivates a
loopback after the specified period. (The system sets loopback timer to 60 seconds by
default.)
Parameters: timing Loopback timing in seconds (0 to 86400)
0: disable the loopback timer
Command: interface intf t1 pattern

Privilege: admin
Syntax: interface intf t1 pattern ch type
Explanation: Send test pattern
Parameters: ch full / data / idle / none

type The pattern type (3-in-24/1-in-8/2-in-8/1:1: none)
Command: interface intf t1 performance clear

Privilege: admin
Syntax: interface intf t1 performance clear
Explanation: Clear performance reports and alarm error count
Command: interface intf t1 primary_clock

Privilege: admin
Syntax: interface intf t1 clock source
Explanation: Set primary clock source
Parameters: source Clock source (internal/port1/port2)
Command: interface intf t1 secondary_clock

Privilege: admin
Syntax: interface intf t1 secondary_clock source
Explanation: Set secondary clock source
Parameters: source Clock source (internal/port1/port2)
Command: interface intf t1 yel

Privilege: admin
Syntax: interface intf t1 yel setup
Explanation: Enable or disable T1 YEL
Parameters: setting enable / disable
Command: interface intf tci

Privilege: admin
Syntax: interface intf tci value
Explanation: Set default tci to KS8995m
Parameters: Value 1 to 65535
Command: interface intf timeslot add

Privilege: admin
Syntax: interface intf timeslot add range
Explanation: Add more timeslots to a WAN port and keep time slots that are already assigned for the
WAN port.
Parameters: range a time slot range can be single time slot number (1 to 24), or a range of
time slots that specified in format “start-end”. For example, “1-10”
represents time slot range from time slot 1 to time slot 10.
Command: interface intf timeslot delete

Privilege: admin
Syntax: interface intf timeslot delete range
Explanation: Delete more timeslots to original setting
Parameters: range a time slot range can be single time slot number (1 to 24), or a range of time
slots that specified in format “start-end”. For example, “1-10” represents
time slot range from time slot 1 to time slot 10.
Command: interface intf timeslot set

Privilege: admin
Syntax: interface intf timeslot set timeslot
Explanation: Remove all time slots assigned to a WAN port then re-assign time slots specified by time
slot to the port.
Parameters: timeslot_range timeslot range. 0 to clear
Command: interface intf vlan frame-type

Privilege: admin
Syntax: interface intf vlan frame-type type
Explanation: Set the acceptable frame type of a given interface. Two options could be chose: all means
this interface could accept tagged, untagged or pure-priority packets; tag-only means this
interface could only accept tagged packets.
Parameters: type all/tag-only
Command: interface intf vlan ingress-filter

Privilege: admin
Syntax: interface intf vlan ingress-filter setting
Explanation: Enable/disable ingress filtering of a given interface. If enables ingress filtering on the
interface, it will check whether the incoming packet belongs to the VLAN which the interface
belongs to. If not, discards the packet.
Parameters: setting enabled/disabled
Command: interface intf vlan pvid

Privilege: admin
Syntax: interface intf vlan pvid vid
Explanation: Set Interface’s PVID. This PVID will be used in port-based VLAN.
Parameters: vid VLAN ID(range from 1 to 4094)
Command: interface wan-a-1 als setup

Privilege: admin
Syntax: interface wan-a-1 als setup [setting]
Explanation: Set interface’s auto laser shutdown
Parameters: setting enable/disable (default: disable)
Command: interface wan-a-1 tci

Privilege: admin
Syntax: interface wan-a-1 tci [value]
Explanation: Set default tci to ks8995m
Parameters: value 1~65535 (default: 4096)
15.6 Login Commands

Command: login
Privilege: None
Syntax: Login user
Explanation: Login as a specific system user
Parameters: user operator | admin
15.7 Policy Commands

Command: policy acl create
Privilege: admin
Syntax: policy acl create name
Explanation: Creates an access control list with a given name. This list is combined with several rules
and those rules will be checked accordingly.
A maximum of 64 lists can be created.
Parameters: name list_name (<6 bytes)
Command: policy acl destroy

Privilege: admin
Syntax: policy acl destroy name
Explanation: Destroys the specified access control list. Those rules in the list will disappear.
Parameters: name list_name in configuration
Command: policy acl list1 append

Privilege: admin
Syntax: policy acl list1 append action selector
Explanation: Appends an entry on the specified list. If a packet matches the selector described in the
rule, action will be taken.
A maximum of 32 entries can be added to a list.
Parameters: action { permit | deny }
selector "[src_ip/prefix] [dst_ip/prefix] [protocol] [service]"
Command: policy acl list1 delete

Privilege: admin
Syntax: policy acl list1 delete start_index [end_index]
Explanation: Deletes entry(s) by indicating the index number.
The rule in the back will follow the procedure to move forward step by step.
Parameters: start_index The starting index number. 0 to delete all rules in the list.
[end_index] The end index number
Command: policy mac create

Privilege: admin
Syntax: policy mac create name
Explanation: Creates an access control list for mac address. This list is used only for interfaces in bridge
mode.
Maximum 6 lists can be created.
Parameters: name list_name (<6 bytes)
Command: policy mac destroy

Privilege: admin
Syntax: policy mac destroy name
Explanation: Destroys an access control list for mac address
Parameters: name list_name in configuration
Command: policy mac mac_list append
Privilege: admin
Syntax: policy mac mac_list append selector
Explanation: Adds a MAC address to be blocked to a specified list
Maximum 32 entries can be added for a list.
Parameters: selector "XX : XX : XX : XX : XX : XX"
Command: policy mac mac_list delete

Privilege: admin
Syntax: policy mac mac_list delete selector
Explanation: Deletes a MAC address from a specified list
Parameters: selector "XX : XX : XX : XX : XX : XX"
Command: policy qos rate_limit append

Privilege: admin
Syntax: policy qos rate_limit append src_ip dest_ip protocol [src_port] [dst_port] [dscp]
Explanation: Append a traffic control policy
Parameters: src_ip any | source IP address/prefix
dest_ip any | destination IP address/prefix
protocol tcp | udp | icmp | any | 0 to 255
[src_port] any | min[-max] only for TCP/UDP
[dest_port] any | min[-max] only for TCP/UDP
[dscp] Optional Diffserv code point value(s) in decimal, starts with keyword dscp
i.e. dscp val1 val2-val3 val4...space to separate DSCP values, but no space for
action_parameter rate type rate Committed access rate in min[- max] format type of
bandwidth for rate in bits per sec
[action_parameter] action_parameter controls the outgoing traffic flow rate for IP
packet matched the policy criteria specified by selector.
[rate] Committed access rate in minimum-maximum format. The minimum rate is
guaranteed the minimum rate of the selected policy. When the maximum_rate is
mentioned in the action-parameter, the parameter is specified the maximum rate

of the selected policy. If maximum_rate is not mentioned, it is used that maximum
rate is same as minimum rate.
[type] Unit of rate in kbps or mbps, specify the unit of bandwidth in bits per sec.
Command: policy qos rate_limit delete

Privilege: admin
Syntax: policy qos rate_limit delete policy num
Explanation: Delete a traffic control policy
Parameters: policy_num – policy index, starts from 1
Command: Interface intf policy qos rate_limit insert

Privilege: admin
Syntax: Interface intf policy qos rate_limit insert policy num src_ip del_ip protocol [scr_port]
[del_port] [dscp]
Explanation: Insert a traffic control policy
Parameters: policy_num Policy index before which new policy will be inserted selector
src_ip dest_ip protocol [src_port] [dst_port] [dscp]
src_ip any | source IP address/prefix
dest_ip any | destination IP address/prefix
protocol tcp | udp | icmp | any | 0 to 255
[src_port] any | min[-max] only for TCP/UDP
[dest_port] any | min[-max] only for TCP/UDP
[dscp] Optional Diffserv code point value(s) in decimal, starts with keyword 'dscp' i.e.
dscp val1 val2-val3 val4...space to separate DSCP values action_parameter rate type rate
Committed access rate in min[-max] format type kbps | mbps type of bandwidth for rate in
bits per sec
[action_parameter] action_parameter controls the outgoing traffic flow rate for IP
packet matched the policy criteria specified by selector.
[rate] Committed access rate in minimum-maximum format. The minimum rate is
guaranteed the minimum rate of the selected policy. When the maximum_rate is
mentioned in the action-parameter, the parameter is specified the maximum rate
of the selected policy. If maximum_rate is not mentioned, it is used that maximum
rate is same as minimum rate.
[type] Unit of rate in kbps or mbps, specify the unit of bandwidth in bits per sec.
15.8 Route Commands

Command: route ospf area add
Privilege: admin
Syntax: route ospf area add area_id
Explanation: Add an OSPF area
Parameters: area_id
Command: route ospf area authentication

Privilege: admin
Syntax: route ospf area authentication area_id type
Explanation: Enable authentication for an OSPF area
Parameters: area_id 0 to 4294967295
type null | password |md5
Command: route ospf area cost

Privilege: admin
Syntax: route ospf area cost area_id cost
Explanation: Assign a specific cost to the default summary route used.
cost 0 to 16777215
Command: route ospf area delete

Privilege: admin
Syntax: route ospf area delete area_id
Explanation: Delete an OSPF area
Command: route ospf area type

Privilege: admin
Syntax: route ospf area type area_id type
Explanation: Specify an address range for which a single route will be advertised.
type normal | stub | stub-no-summary
Command: route ospf redistribute

Privilege: admin
Syntax: route ospf redistribute type
Explanation: Redistribute routing information from a specified place into RIP/OSPF tables
Parameters: Type static | rip |default | none
Command: route ospf router-id

Privilege: admin
Syntax: route ospf router-id id
Explanation: Set the OSPF router id
Parameters: id IP address that identifies this OSPF router
Command: route static add

Privilege: admin
Syntax: route static add network gateway intf
Explanation: Add a static route
Parameters: network Destination network (xxx.xxx.xxx.xxx/xx)
gateway Routing gateway
intf Output interface (lan1 to lan4/wan1 to wan2/wan-a-1 to wan-b-2)
Command: route static delete

Privilege: admin
Syntax: route static delete network
Explanation: Delete a static route
Parameters: network Destination network (xxx.xxx.xxx.xxx/xx)
15.9 Show Commands

Command: show bridge
Privilege: admin
Syntax: show bridge
Explanation: Show bridge configuration
Parameters: none
Command: show bridge brg_name config

Privilege: admin
Syntax: show bridge brg_name config
Explanation: Show bridge group configuration
Parameters: none
Command: show bridge brg_name spantree

Privilege: admin
Syntax: show bridge brg_name spantree
Explanation: Show RSTP status of brg_name
Parameters: none
Command: show bridge brg_name vlan port

Privilege: admin
Syntax: show bridge brg_name vlan port
Explanation: Show each port's VLAN information
Parameters: none
Command: show bridge brg_name vlan state

Privilege: admin
Syntax: show bridge brg_name vlan state
Explanation: Show bridge state
Parameters: None
Command: show bridge brg_name vlan table

Privilege: admin
Syntax: show bridge brg_name vlan table
Explanation: Show VLAN table
Parameters: None
Command: show bridge brg_name svlan port

Privilege: admin
Syntax: show bridge brg_name svlan port
Explanation: show each port's svlan information that contain PVID, port_type, ingress_filter
Parameters:
Command: show bridge brg_name svlan state

Privilege: admin
Syntax: show bridge brg_name svlan state
Explanation: show svlan state
Parameters:
Command: show bridge brg_name svlan table

Privilege: admin
Syntax: show bridge brg_name svlan table
Explanation: show svlan table that contain relationship of VID
Parameters:
Command: show interface intf chdlc

Privilege: admin
Syntax: show interface intf chdlc
Explanation: Show Cisco HDlC parameters
Parameters: None
Command: show interface intf config

Privilege: admin
Syntax: show interface intf config
Explanation: Show interface configuration.
Interface options include lan1, lan2, lan3, lan 4, wan1, wan2, wan-a-1, wan-a-2, wan-b-1,
wan-b-2.
Parameters: None
Command: show interface intf e1 alarm

Privilege: admin
Syntax: show interface intf e1 alarm
Explanation: Shows alarm status
Command: show interface intf e1 configuration

Privilege: admin
Syntax: show interface intf e1 configuration
Explanation: Shows E1 line information and configuration
Command: show interface intf e1 diagnostics

Privilege: admin
Syntax: show interface intf e1diagnostics
Explanation: Shows E1 diagnostic status and BERT results
Command: show interface intf e1 performance

Privilege: admin
Syntax: show interface intf e1 performance
Explanation: Show E1 performance statistics
Command: show interface intf e1 status

Privilege: admin
Syntax: show interface intf e1 status
Explanation: Show E1 status
Command: show interface intf ospf config

Privilege: admin
Syntax: show interface intf route ospf config
Explanation: Show the network interface related OSPF configurations
Parameters:
Command: show interface intf ospf status

Privilege: admin
Syntax: show interface intf route ospf status
Explanation: Show the network interface related OSPF status
Parameters:
Command: show interface intf speed

Privilege: admin
Syntax: show interface intf speed
Explanation: Show LAN speed/duplex setting
Parameters: None
Command: show interface intf statistics

Privilege: admin
Syntax: show interface intf statistics [interval]
Explanation: Show LAN traffic statistics
Parameters: [interval] Timing interval in secs to refresh display (1 to 60)
If the parameter is absent, the command only shows statistics once.
Command: show interface intf t1 configuration

Privilege: admin
Syntax: show interface intf t1 configuration
Explanation: Displays the line configuration

Parameters:
Command: show interface intf t1 diagnostics

Privilege: admin
Syntax: show interface intf t1diagnostics
Explanation: Displays the diagnostic status and BERT result
Parameters:
Command: show interface intf t1 line alarm

Privilege: admin
Syntax: show interface intf t1 line alarm
Explanation: Displays the line alarm count
Parameters:
Command: show interface intf t1 performance

Privilege: admin
Syntax: show interface intf t1 performance type, interval [register]
Explanation: Show the performance statistics
Parameters: Type Line / user/ remote
interval 1hr/24hr
[register] es / uas / bes / ses / css / locf, only for 24hr interval
Command: Show interface intf t1 status

Privilege: admin
Syntax: Show interface intf t1 status
Explanation: Show the line current status and line availability
Parameters:
Command: show interface wan-a-1 als

Privilege: operator
Syntax: show interface wan-a-1 als
Explanation: Show the state of auto laser shutdown
Parameters:
Command: Show interface wan-a-1 diagnosis

Privilege: operator
Syntax: show interface wan-a-1 diagnosis
Explanation: Show diagnostic information
Parameters:
Command: show multilink config

Privilege: admin
Syntax: show multilink config [virtual_name]
Explanation: Show the virtual interface multilink configurations.
Parameters: [virtual_name] virtual interface name. If this parameter is absent, the command
displays all virtual interfaces.
Command: show route entry

Privilege: admin
Syntax: show route entry
Explanation: Show routing entries
Parameters: [all] Show all routing entries including dynamic entries
Command: show route ospf border-router

Privilege: admin
Syntax: show route ospf border-routers
Explanation: Show the border and boundary router current status
Parameters:

Command: show route ospf config

Privilege: admin
Syntax: show route ospf config [area_id] [intf_name]
Explanation: Show the OSPF configuration
Parameters:
Command: show route ospf database

Privilege: admin
Syntax: show route ospf database
Explanation: Show the OSPF database summary
Parameters:
Command: show route ospf neighbor

Privilege: admin
Syntax: show route ospf neighbor
Explanation: Show the OSPF neighbor list
Parameters:
Command: show route ospf route

Privilege: admin
Syntax: show route ospf route
Explanation: Show the OSPF routing entries
Parameters:
Command: show route ospf router-info

Privilege: admin
Syntax: show route ospf router-info
Explanation: Show the OSPF router current status
Parameters:
Command: show system alarm history

Privilege: operator
Syntax: show alarm history
Explanation: Show alarm history
Parameters:
Command: show system alarm status

Privilege: operator
Syntax: show current alarm status
Explanation: Show current alarm status
Parameters:
Command: show system fwinfo

Privilege: admin
Syntax: show system fwinfo
Explanation: Show card firmware information
Parameters: none
Command: show system hwinfo

Privilege: admin
Syntax: show system hwinfo
Explanation: Show card hardware information
Parameters: none
Command: show system ip

Privilege: admin
Syntax: show system ip

Explanation: Show SNMP management IP

Parameters: none
Command: show system ssh status

Privilege: operator
Syntax: show system ssh status
Explanation: Show SSH status
Parameters:
Command: show system ssh public-key

Privilege: operator
Syntax: show system ssh public-key type
Explanation: show SSH public-key
After SSH host keys are generated, the user is able to display public keys for passing the
keys to clients.
Parameters: type Specifies what type of key to display. (rsa/dsa)
15.10 System Commands

Command: system account password
Privilege: admin
Syntax: system account password user checking hash-value
Explanation: Change user password or disable password checking
Parameters: user Account name (operator/admin)
checking Specifies if password checking is required when an user is logging in.
(enable/disable)
hash-value If password checking is enabled, the command will prompt the user to input
a new password for the account after the user presses ENTER. The system
uses the password string to generate a hashed value then stores it in the
configuration database. When a hashed password value is applied by the
parameter, the system directly stores the hashed value and uses it to verify
password typed by users. The parameter is mainly for batch configuration,
like startup configuration, so users do not use it usually.
Command: system alarm aco

Privilege: admin
Syntax: system alarm aco
Explanation: Alarm cut off
Parameters:
Command: system alarm clear

Privilege: admin
Syntax: system alarm clear
Explanation: Clear alarm history
Parameters:
Command: system alarm setup

Privilege: admin
Syntax: system alarm setup type setup [severity] [threshold]
Explanation: Change alarm attributes
Parameters: type LAN1-link-down LAN1 link down alarm
LAN2-link-down LAN2 link down alarm


wan-a-1-layer2-link-down slot A port1 layer2 link down alarm
wan-a-2-layer2-link-down slot A port2 layer2 link down alarm
wan-b-1-layer2-link-down slot B port1 layer2 link down alarm
wan-b-2-layer2-link-down slot B port2 layer2 link down alarm
wan-a-clock-loss slot A port1 clock loss alarm
wan-a-1-rai-yel slot A port1 RAI/YELLOW alarm
wan-a-1-ais slot A port1 AIS alarm
wan-a-1-los slot A port1 LOS alarm
wan-a-1-lof slot A port1 LOF alarm
wan-a-1-bpv slot A port1 BPV alarm
wan-a-1-es slot A port1 ES alarm
wan-a-1-uas slot A port1 UAS alarm
wan-a-1-css slot A port1 CSS alarm
wan-a-2-rai-yel slot A port2 RAI/YELLOW alarm
wan-a-2-ais slot A port2 AIS alarm
wan-a-2-los slot A port2 LOS alarm
wan-a-2-lof slot A port2 LOF alarm
wan-a-2-bpv slot A port2 LOF alarm
wan-a-2-es slot A port2 ES alarm
wan-a-2-uas slot A port2 UAS alarm
wan-a-2-css slot A port2 CSS alarm
wan-b-clock-loss slot B port1 clock loss alarm
wan-b-1-rai-yel slot B port1 RAI/YELLOW alarm
wan-b-1-ais slot B port1 AIS alarm
wan-b-1-los slot B port1 LOS alarm
wan-b1-lof slot B port1 LOF alarm
wan-b-1-bpv slot B port1 BPV alarm
wan-b-1-es slot B port1 ES alarm
wan-b-1-uas slot B port1 UAS alarm
wan-b-1-css slot B port1 CSS alarm
wan-b-2-rai-yel slot B port2 RAI/YELLOW alarm
wan-b-2-ais slot B port2 AIS alarm
wan-b-2-los slot B port2 LOS alarm
wan-b-2-lof slot B port2 LOF alarm
wan-b-2-bpv slot B port2 LOF alarm
wan-b-2-es slot B port2 ES alarm
wan-b-2-uas slot B port2 UAS alarm
wan-b-2-css slot B port2 CSS alarm
setup Enable/Disable the alarm
severity Critical, major, minor, warning, informative, cleared
threshold Only for T1 alarm types, 5 to 900 for BPV, for all others its 1 to 9.
Command: system configuration copy

Privilege: admin
Syntax: system configuration upload src_file dst_file
Explanation: Upload/download system configuration to the address specified
Parameters: src_file working_cfg or URL of the source of configuration file
dst_file startup or URL of the copied
Command: system configuration reset

Privilege: admin
Syntax: system configuration reset
Explanation: Reset configuration to factory default values
Parameters:

Command: system configuration save

Privilege: admin
Syntax: system configuration save
Explanation: Save working configuration as startup configuration. Usually, the Router-A immediately
makes configuration change effective and store the change in volatile RAM. The command
stores the newest working configuration into nonvolatile memory to make them effective
after system reboot.
Parameters:
Command: system firmware load

Privilege: admin
Syntax: system firmware load url
Explanation: Upgrade system firmware from a TFTP server
Parameters: url URL of the firmware image. (tftp://server_ip/file_name)
server_ip: IP address of the TFTP sever
file_name: file name of the new firmware image
Command: system ip
Privilege: admin
Syntax: system ip
Explanation: Setup the SNMP management IP
Parameters: IP address
Subnet Mask: automatically set to a fixed value, 255, 255, 255, 255
Command: system log clear

Privilege: admin
Syntax: system log clear
Explanation: clear system log
Parameters:
Command: system ssh setup

Privilege: admin
Syntax: system ssh setup setting
Explanation: Enable/Disable SSH service
The system needs RSA and DSA keys before it can enable the SSH service. The user is
able to set or generate such public keys by commands system ssh host_key set and
system ssh host_key generate.
Parameters: setup Enable / Disable
Command: system ssh host_key generate

Privilege: admin
Syntax: system ssh host_key generate type
Explanation: Generate a SSH host key
Before SSH service can be enabled, the user must generate a RSA key and a DSA key for
host authentication. Usually, the user can use the command to newly generate the keys.
Parameters: type Specifies what kind of key to be generated.
rsa: Setting a RSA key
dsa: Setting a DSA key
Command: system ssh host_key set

Privilege: admin
Syntax: system ssh host_key set type
Explanation: Set a SSH host key
Users can use the command to a host key if he/she already generated one.
Parameters: type Key type of the key to be set
rsa: setting a RSA key
dsa: Setting a DSA key

Command: system term

Privilege: admin
Syntax: system term baud data parity stop
Explanation: Change console port setting
Parameters: baud Baud rate. (2400/4800/9600/19200/38400)
data Number of data bits. (7/8)
parity Parity check. (odd/even/none)
stop Number of stop bits. (1/2)
Command: system time

Privilege: admin
Syntax: system time MM/DD/YYYY hh:mm:ss
Explanation: Set current system date/time
Parameters: MM Month (1 to 12).
DD Day (1 to 31).
YYYY Four-digit year.
hh Hour (0 to 23).
mm Minute (0 to 59).
ss Second (0 to 59).
Command: system reboot

Privilege: admin
Syntax: system reboot
Explanation: Reboot the system
Parameters: None
15.11 MLPPP commands
Command: multilink create

Privilege: admin
Syntax: multilink create virtual_name
Explanation: Create the virtual interface name to the multilink bundle
Parameters: virtual_name virtual interface name (<16 bytes)
Command: multilink destroy

Privilege: admin
Syntax: multilink destory virtual_name
Explanation: Destory the virtual interface name from the multilink bundle.
Parameters: virtual_name virtual interface name
Command: multilink virtual_interface virtual_name add

Privilege: admin
Syntax: multilink virtual_interface virtual_name add interface […]
Explanation: Add interfaces to the multilink bundle.
Parameters: interface wan-a-1 to wan-b-2
Command: multilink virtual_interface virtual_name delete

Privilege: Admin
Syntax: multilink virtual_interface virtual_name delete interface […]
Explanation: Delete interfaces from the multilink bundle.
Parameters: interface wan-a-1 to wan-b-2
Command: multilink virtual_interface virtual_name interval

Privilege: admin
Syntax: multilink virtual_interface virtual_name interval value

16 Glossary IP6510 Multiple WAN Router /Bridge
Explanation: Set the retry interval of keeping alive.

Parameters: value value between 5 to 100, default is 5.
Command: multilink virtual_interface virtual_name ip

Privilege: admin
Syntax: multilink virtual_interface virtual_name ip address
Explanation: Setting the virtual interface ip address.
Parameters: address IP address (xxx.xxx.xxx.xxx/xx)
Command: multilink virtual_interface virtual_name times

Privilege: admin
Syntax: multilink virtual_interface virtual_name times value
Explanation: Set the retry times of keeping alive
Parameters: value value between 6 to 100, default is 6
Command: multilink virtual_interface virtual_name mtu

Privilege: admin
Syntax: multilink virtual_interface virtual_name mtu
Explanation: Set the maximum transmission unit for a packet
Parameters: size 54~1532 bytes
16 Glossary
ACL Access Control List

CIR Committed Information Rate
CLI Command Line Interface
DCE Data Circuit-terminating Equip-connects
DLCI Data Link Connection Identifier
DNS Domain name server
DS1 Digital Signal, Level One E1 or T1
E1 European Digital signal, Level One
FR Frame Relay
FTP File Transfer Protocol
HDLC High Level Data Link Control
HTTP Hyper Text Transmission Protocol
ICMP Internet Control Message Protocol
IP Internet Protocol
LAN Local Area Network
LED Light Emitting Diode
MAC Media Access Control
MLPPP Multilink Point-to-Point Protocol
NAT Network Address Translation
NAPT Network Address Port Translation
OSPF Open Shortest Path First Protocol
PING Packets Internet Groper
PPP Point-to-Point Protocol
PVCs Private Virtual Circuit
RAI Remote Alarm Indiction
RAM Random Access Memory
RIP Router Information Protocol
RSTP Rapid Spanning Tree Protocol
STP Spanning Tree Protocol
TDM Time Division Multiplexing
TFTP Trivial FTP
URL Universal Record Location
VID VLAN ID

16 Glossary IP6510 Multiple WAN Router /Bridge
VLAN Virtual LAN

WAN Wide Area Network
WINS Windows Internet Naming Service

IP6510 v8 M

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IP6510 v8 M

Uploaded by

Copyright:

Available Formats

IP6510 Multiple WAN

LOOP TELECOMMUNICATION INTERNATIONAL, INC.

Figure 1- 1 Multiple WAN--------------------------------------------------------------------------------------- 2

Figure 2-1 Front Panel ------------------------------------------------------------------------------------------ 6

Figure 3- 1 VT-100 Monitor Connection ------------------------------------------------------------------- 12

Figure 4- 1 Remote bridge mode Setup ------------------------------------------------------------------- 18

Figure 5- 1 MLPPP Application ------------------------------------------------------------------------------ 20

Figure 6- 1 VLAN Application #1----------------------------------------------------------------------------- 22

Figure 7- 1 Transparently Conveying VLAN-enabled Customer Traffic ---------------------------- 28

Table 3- 1 Console Port Default Setting ------------------------------------------------------------------- 13

Table 6- 1 VLAN Table ----------------------------------------------------------------------------------------- 26

DK Når produktet er udtjent, bor det børtskaffes via de sæ rlige indsamlingssteder i

N Ved slutten av produktets levetid bør det avhendes på en kommunal miljøstasjon

S Lämna vänligen in produkten på lämplig återvinningsstation när den är förbrukad.

FIN Hävitä tuote käytöiän päättyessä viemällä se asianmukaiseen keräyspisteeseen.

CZ Po skončení jeho životnosti odložte prosím výrobek na přislušném sbĕrném místé

SK Po skončení jeho životnosti odovzdajte prosím zariadenie na príslušnom zbernom

GR Στο Тέλος тης λειτουργικής Ζωής του προϊόντος παρακαλώ

Loop Telecom Page 1

Figure 1- 1 Multiple WAN

Figure 1- 2 MLPPP Bundle

Figure 1- 3 Ethernet as a backup link

Loop Telecom Page 2

WAN Plug-in Module

Loop Telecom Page 3

Access Control & Firewall (RT)

Administration & Diagnostics

Physical and Environment

Loop Telecom Page 4

Loop Telecom Page 5

2.2 Mechanical Installation

Figure 2-1 Front Panel

Loop Telecom Page 6

Table 2- 1 Power Connector

2.2.2 E1/ T1/Ethernet Card Description

Figure 2- 2 IP6510 Slot A and Slot B Location

Figure 2- 3 E1/T1 Card Panel View

Figure 2- 4 RJ 45 Electrical Ethernet Card Panel View

Loop Telecom Page 7

Figure 2- 5 SFP Optical Electrical Card Panel View

2.2.2.1 Jumper Settings

Table 2- 2 Jumper Setting for E1/T1 Card

Figure 2- 6 IP6510 Jumper Setting for T1 Card

Figure 2- 7 IP6510 Jumper Setting for E1 Card

Loop Telecom Page 8

2.2.2.2 E1/T1 pin assignment

Table 2- 3 E1/T1 pin definition

Table 2- 4 Ethernet Ports Pin Definition

Loop Telecom Page 9

2.3 Front Panel Console Port and LEDS

Cold plug-in Cold plug- in

Figure 2- 8 Loop-IP6510 Front Panel

2.3.1 Console Port

Table 2- 5 Console Port Pin Assignment

2.4 LED Operation

Table 2- 6 Front Panel LED Indication

Loop Telecom Page 10

Table 2- 7 Ethernet Plug-in Card LED Indication

Table 2- 8 T1/E1 Plug-in Card LED Indication

2.5 Ethernet Connection

Table 2- 9 RJ45 10/100M Ethernet Connector Pin Assignment

Loop Telecom Page 11