NN47263-302 04.01 Commissioning

Commissioning
Avaya Secure Router 2330/4134
10.3
NN47263-302, 04.01
October 2010
2010 Avaya Inc.
All Rights Reserved.

Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of
such changes.
Documentation disclaimer
Avaya shall not be responsible for any modifications, additions, or
deletions to the original published version of this documentation unless
such modifications, additions, or deletions were performed by Avaya.
End User agree to indemnify and hold harmless Avaya, Avaya's agents,
servants and employees against all claims, lawsuits, demands and
judgments arising out of, or in connection with, subsequent
modifications, additions or deletions to this documentation, to the
extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web
sites referenced within this site or documentation(s) provided by Avaya.
Avaya is not responsible for the accuracy of any information, statement
or content provided on these sites and does not necessarily endorse
the products, services, or information described or offered within them.
Avaya does not guarantee that these links will work all the time and has
no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. In addition,
Avayas standard warranty language, as well as information regarding
support for this product, while under warranty, is available to Avaya
customers and other parties through the Avaya Support Web site:
http://www.avaya.com/support. Please note that if you acquired the
product from an authorized Avaya reseller outside of the United States
and Canada, the warranty is provided to you by said Avaya reseller and
not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN
AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE
RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE
ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE.
BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABLY AS YOU AND END USER),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (AVAYA).
protected by copyright and other intellectual property laws including the

sui generis rights relating to the protection of databases. You may not
modify, copy, reproduce, republish, upload, post, transmit or distribute
in any way any content, in whole or in part, including any code and
software. Unauthorized reproduction, transmission, dissemination,
storage, and or use without the express written consent of Avaya can
be a criminal, as well as a civil, offense under the applicable law.
Third-party components
Certain software programs or portions thereof included in the Product
may contain software distributed under third party agreements (Third
Party Components), which may contain terms that expand or limit
rights to use certain portions of the Product (Third Party Terms).
Information regarding distributed Linux OS source code (for those
Products that have distributed the Linux OS source code), and
identifying the copyright holders of the Third Party Components and the
Third Party Terms that apply to them is available on the Avaya Support
Web site: http://www.avaya.com/support/Copyright/.
Trademarks
The trademarks, logos and service marks (Marks) displayed in this
site, the documentation(s) and product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third
parties. Users are not permitted to use such Marks without prior written
consent from Avaya or such third party which may own the Mark.
Nothing contained in this site, the documentation(s) and product(s)
should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All other trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support
Web site: http://www.avaya.com/support
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems
or to ask questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support
telephone numbers, see the Avaya Web site: http://www.avaya.com/
support
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation(s) and Product(s) provided
by Avaya. All content on this site, the documentation(s) and the
product(s) provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is
Commissioning
October 2010
Contents
Chapter 1: New in this release.................................................................................................5
Features............................................................................................................................................................5
Other changes...................................................................................................................................................5
FAT 32 File System Support for SR 4134 and SR 2330...........................................................................5
Multiple SNTP Server support..................................................................................................................5
Source IP enhancements.........................................................................................................................6
Chapter 2: Introduction.............................................................................................................7
Prerequisites.....................................................................................................................................................7
Navigation.........................................................................................................................................................7
Chapter 3: Avaya Secure Router 2330/4134 commissioning................................................9

Prerequisites.....................................................................................................................................................9
Secure Router 2330/4134 commissioning procedures.....................................................................................9
Secure Router 2330/4134 commissioning navigation.....................................................................................12
Chapter 4: Commissioning the Avaya Secure Router 2330/4134.......................................15

Gathering required information.......................................................................................................................15
Connecting a terminal for local access...........................................................................................................17
Powering up the Secure Router 2330/4134....................................................................................................18
Logging in to the Secure Router 2330/4134...................................................................................................21
Defining boot parameters................................................................................................................................22
Viewing boot parameters and software image information.....................................................................24
Enabling the management LAN port...............................................................................................................24
Disabling the USB port on the Secure Router 4134........................................................................................26
Configuring SSH.............................................................................................................................................27
Enabling FTP, TFTP, and Telnet......................................................................................................................27
Configuring FTP users....................................................................................................................................28
Verifying the Telnet connection.......................................................................................................................29
Viewing Telnet server settings.........................................................................................................................29
Clearing a Telnet session................................................................................................................................30
Configuring the Telnet banner.........................................................................................................................30
Configuring the Telnet timeout........................................................................................................................31
Configuring the host name..............................................................................................................................32
Configuring the static default route.................................................................................................................32
Verifying the next-hop connection...................................................................................................................33
Configuring the date........................................................................................................................................33
Configuring the time........................................................................................................................................34
Configuring multiple SNTP servers.................................................................................................................35
Configuring the SNTP client............................................................................................................................36
Displaying the SNTP configuration.................................................................................................................37
Configuring the SNTP source address............................................................................................................37
Configuring daylight saving time.....................................................................................................................37
Example of configuring daylight saving time...................................................................................................39
Changing the admin user password................................................................................................................40
Changing the administrator account name.....................................................................................................41
Adding users...................................................................................................................................................41
Removing users..............................................................................................................................................42
Pinging a device..............................................................................................................................................43
Commissioning
October 2010
Saving a configuration.....................................................................................................................................43
Deleting a configuration file.............................................................................................................................44
Rebooting or resetting the Secure Router 2330/4134.....................................................................................44
Powering down the Secure Router 2330/4134...............................................................................................45
Viewing the Secure Router 2330/4134 configuration......................................................................................46
Viewing chassis status....................................................................................................................................46
Viewing interface module configuration...........................................................................................................47
Checking the system for alarms......................................................................................................................47
Checking the system status............................................................................................................................48
Configuring reverse Telnet on the Secure Router 4134..................................................................................48
Copying an external compact flash or a USB drive file...................................................................................50
Downloading a network file to a compact flash or a USB drive.......................................................................50
Formatting the external compact flash file system..........................................................................................51
Formatting the USB drive file system..............................................................................................................52
Listing files on a compact flash drive or USB drive.........................................................................................52
Listing image version files from a compact flash drive or USB drive..............................................................53
Removing a file from a compact flash drive or USB drive...............................................................................53
Renaming a file on a compact flash drive or USB drive..................................................................................54
Uploading files from a compact flash drive or USB drive................................................................................54
Uploading the event log from the Secure Router 2330/4134..........................................................................55
Commissioning
October 2010
Chapter 1: New in this release

The following sections detail what is new in Avaya Secure Router 2330/4134 Commissioning
(NN47263-302) for Release 10.3.
Features
There is no new feature content added to Avaya Secure Router 2330/4134 Commissioning
(NN47263-302) for Release 10.3.
Other changes
The following sections include commissioning specific feature information that was previously
documented in the Secure Router 2330/4134, 10.2 and 10.2.1 release notes, and has been
moved to Avaya Secure Router 2330/4134 Configuration Commissioning (NN47263-302)
for Release 10.3:
FAT 32 File System Support for SR 4134 and SR 2330

Beginning with Release 10.2, Secure Router 2330/4134 supports the FAT 32 file system for
the compact flash and USB drives. For more information, see Formatting the external compact
flash file system on page 51.
Multiple SNTP Server support

Beginning with Release 10.2, Secure Router 2330/4134 supports Multiple Simple Network
Time Protocol (SNTP) Servers. For more information see, Configuring multiple SNTP
servers on page 35.
Commissioning
October 2010
New in this release
Source IP enhancements
Beginning with Release 10.2, Secure Router 2330/4134 supports adding source address
information to existing services. For more information about Source IP enhancements, see
Avaya Secure Router 2330/4134 Configuration IPv4 and Routing (NN47263-502).
For information about adding source address information to SNTP, see Configuring the SNTP
source address on page 37.
Commissioning
October 2010
Chapter 2: Introduction
This document provides information about the recommended method to commission the Avaya Secure
Router 2330/4134. For a complete list of Command Line Interface (CLI) commands that you use to monitor
and configure the Secure Router 2330/4134, see Avaya Secure Router 2330/4134 Command Line
Reference (NN47263-507).
Prerequisites
Hardware installation is complete.
You must have a console cable to connect to the console port of the router.
You must have an Ethernet cable to connect to the management port of the router.
Important:
The Secure Router 2330 does not support a dedicated management LAN port. You
can use one of the front panel Ethernet ports as a management LAN port.
Be familiar with using the CLI and interpreting partial configuration procedures. See Avaya
Secure Router 2330/4134 Using the Command Line Interface (NN47263-506).
Navigation
Avaya Secure Router 2330/4134 commissioning on page 9
Commissioning the Avaya Secure Router 2330/4134 on page 15
Commissioning
October 2010
Introduction
Commissioning
October 2010
Chapter 3: Avaya Secure Router 2330/4134

commissioning
You commission the Avaya Secure Router 2330/4134 to prepare the unit for software feature
configuration. Commissioning includes tasks such as establishing communication with the system,
defining boot parameters, configuring usernames and passwords, and establishing remote access.
Prerequisites
Ensure the Secure Router 2330/4134 is securely installed in an equipment rack.
Secure Router 2330/4134 commissioning procedures

This task flow shows you the sequence of procedures you perform to commission the Secure
Router 2330/4134. To link to any procedure, go to Secure Router 2330/4134 commissioning
navigation on page 12.
Commissioning
October 2010
Avaya Secure Router 2330/4134 commissioning
Figure 1: Secure Router 2330/4134 commissioning procedures
10
Commissioning
October 2010
Secure Router 2330/4134 commissioning procedures
Figure 2: Secure Router 2330/4134 commissioning procedures (continued)
Commissioning
October 2010
11
Secure Router 2330/4134 commissioning navigation

Gathering required information on page 15
Connecting a terminal for local access on page 17
Powering up the Secure Router 2330/4134 on page 18
Logging in to the Secure Router 2330/4134 on page 21
Defining boot parameters on page 22
Enabling the management LAN port on page 24
Disabling the USB port on the Secure Router 4134 on page 26
Configuring SSH on page 27
Enabling FTP, TFTP, and Telnet on page 27
Verifying the Telnet connection on page 29
Viewing Telnet server settings on page 29
Clearing a Telnet session on page 30
Configuring the Telnet banner on page 30
Configuring the Telnet timeout on page 31
Configuring the host name on page 32
Configuring the static default route on page 32
Verifying the next-hop connection on page 33
Configuring the date on page 33
Configuring the time on page 34
Configuring the SNTP client on page 36
Displaying the SNTP configuration on page 37
Configuring daylight saving time on page 37
Changing the admin user password on page 40
Changing the administrator account name on page 41
Adding users on page 41
Removing users on page 42
Configuring FTP users on page 28
Pinging a device on page 43
12
Commissioning
October 2010
Secure Router 2330/4134 commissioning navigation
Saving a configuration on page 43

Deleting a configuration file on page 44
Rebooting or resetting the Secure Router 2330/4134 on page 44
Powering down the Secure Router 2330/4134 on page 45
Viewing the Secure Router 2330/4134 configuration on page 46
Viewing chassis status on page 46
Viewing interface module configuration on page 47
Checking the system for alarms on page 47
Checking the system status on page 48
Configuring reverse Telnet on the Secure Router 4134 on page 48
Copying an external compact flash or a USB drive file on page 50
Downloading a network file to a compact flash or a USB drive on page 50
Formatting the external compact flash file system on page 51
Formatting the USB drive file system on page 52
Listing files on a compact flash drive or USB drive on page 52
Listing image version files from a compact flash drive or USB drive on page 53
Removing a file from a compact flash drive or USB drive on page 53
Renaming a file on a compact flash drive or USB drive on page 54
Uploading files from a compact flash drive or USB drive on page 54
Uploading the event log from the Secure Router 2330/4134 on page 55
Commissioning
October 2010
13
14
Commissioning
October 2010
Chapter 4: Commissioning the Avaya

Secure Router 2330/4134
This section includes the recommended method to commission the Avaya Secure Router 2330/4134,
while ensuring that you limit unauthorized access to the router.
Commissioning is the first step following hardware installation. The commissioning task includes the initial
procedures required to bring the router online, and to configure appropriate access for remote users.
Gathering required information

Before you begin, gather all the information you require to complete the commissioning steps.
Procedure steps
Record all the required information for commissioning your Secure Router 2330/4134
in the following table.
Procedure job aid

Table 1: Gathering required information
Required information
Sample entries
New password for admin

user
kevx
Host name
fremont
Record information here
Management IP address and 10.11.12.13 255.255.255.0

mask
Next hop IP address for static 11.12.13.14/24
route to hosts and servers
IP address of hosts and
servers that access the
Secure Router 2330/4134
a.b.c.d/32
The following figure is an example of a commissioning scenario showing the basic

configuration requirements including host name, management interface, and terminals.
Commissioning
October 2010
15
Commissioning the Avaya Secure Router 2330/4134
Figure 3: Commissioning scenario
The following figure shows the same commissioning example scenario but with the Secure
Router 2330.
Figure 4: Secure Router 2330 Commissioning scenario
16
Commissioning
October 2010
Connecting a terminal for local access
Connecting a terminal for local access

Connect a local terminal to the console port of the Secure Router 2330/4134. This local
connection provides communication with the system during commissioning.
Important:
When powering up for the first time, Avaya recommends that you use a direct console
connection to the Secure Router 2330/4134. After you have completed the initial
configuration, you can use a remote connection for router management.
Prerequisites
You have a PC running HyperTerminal or similar terminal emulation program with the
following communication protocol settings:
- 9600 bps
- 8 data bits
- 1 stop bit
- No flow control
- No parity
Ensure you have the supplied console cable (shipped with the chassis).
Ensure you have the supplied female DB-9 to RJ-45 adapter if you require it for connection
to your terminal or PC.
Ensure you have the Secure Router 2330/4134 securely installed in the equipment rack.
Procedure steps
1. Insert the male RJ-45 connector in the console port of the Secure Router
2330/4134.
2. Connect the female DB-9 to RJ-45 adapter to the opposite end of the console cable,
if necessary.
3. Insert the RJ-45 or female DB-9 connector (dependent on your equipment) in a
terminal or PC.
Procedure job aid

The following figure shows how to connect a terminal to the Secure Router 4134 for local
access.
Commissioning
October 2010
17
Figure 5: Connect a local terminal to the Secure Router 4134
The following figure shows how to connect a terminal to the Secure Router 2330 for local
access.
Figure 6: Connect a local terminal to the Secure Router 2330
Powering up the Secure Router 2330/4134

Power up the Secure Router 2330/4134 to initiate the power-on diagnostics test. The Secure
Router 2330/4134 indicates the resulting pass or fail with status LEDs, and by logging results in
the event log.
Average time for the Secure Router to boot up: 5 minutes.
18
Commissioning
October 2010
Powering up the Secure Router 2330/4134
Prerequisites
The Secure Router 2330/4134 is securely mounted and grounded. For information about
installing the Secure Router 4134 chassis, see Avaya Secure Router 4134 Installation
Chassis (NN47263-300). For information about installing the Secure Router 2330
chassis, see Avaya Secure Router 2330 Installation Chassis (NN47263-304). For
information about installing the power supplies, interface modules, and other hardware
components, see Avaya Secure Router 2330/4134 Installation Hardware Components
(NN47263-301).
A local terminal is connected to the Secure Router console port (the console port is located
on the rear panel of the Secure Router 4134 and the front panel of the Secure Router
2330).
Ensure you have powered up the terminal or PC.
Voltage:
Risk of electric shock
Ensure the Secure Router 2330/4134 is properly grounded. For information about grounding
the Secure Router 4134, see Avaya Secure Router 4134 Installation Chassis
(NN47263-300). For information about grounding the Secure Router 2330, see Avaya
Secure Router 2330 Installation Chassis (NN47263-304).
Important:
When powering up for the first time, Avaya recommends that you use a direct console
connection to the Secure Router 2330/4134. After you have completed the initial
configuration, you can use a remote connection for router management.
Procedure steps (AC power)

1. Connect power cables for AC power supplies.
On the Secure Router 2330, no power switch exists, and so the router begins to
power up as soon as the power cable is connected.
2. On the Secure Router 4134, turn on one power switch at a time (if you installed two
AC power supplies). Power switches are on the rear panel of the Secure Router
4134. The fans start immediately, and the LEDs cycle.
Commissioning
October 2010
19
3. Verify that diagnostic testing is underway by observing the startup messages on

your local terminal.
4. Once the router completes the self-diagnostics tests, verify that the System LED
and, on the Secure Router 4134, the power LEDs that correspond to the power
supplies installed on your router (PS0 and PS1) are green.
5. Verify that the fan LED on the rear panel of the Secure Router 2330/4134 is green,
and air is flowing through the unit.
Procedure steps (DC power on Secure Router 4134)

1. Connect power cables for DC power supplies.
2. Turn on the DC power source. The fans start immediately, and the LEDs cycle.
3. Verify that diagnostic testing is underway by observing the startup messages on
your local terminal.
4. Once the router completes the self-diagnostics tests, verify that the System LED
and the power LEDs that correspond to the power supplies installed on your router
(PS0 and PS1) are green.
5. Verify that the fan LED on the rear panel of the Secure Router 4134 is green, and
air is flowing through the unit.
For troubleshooting information, see Avaya Secure Router 2330/4134 Troubleshooting
(NN47263-700).
When the Secure Router 2330/4134 begins powering up, the boot sequence displays
messages on the terminal or PC that you connected to the console port. A prompt displays at
the beginning of the boot sequence indicating that you can stop the auto-boot sequence by
pressing any key. The Secure Router 2330/4134 waits for 5 seconds for input from you before
beginning the boot sequence. If you press a key and stop the auto-boot sequence, the Secure
20
Commissioning
October 2010
Logging in to the Secure Router 2330/4134
Router 2330/4134 displays the bootrom command menu. The following figure shows the
prompt to stop the auto-boot sequence and enter the bootrom command area.
Figure 7: Accessing the bootrom command menu
If you accidentally enter the bootrom command menu, you can exit that command menu and
restart the normal boot sequence by pressing @ on your keyboard.
For detailed information on using the bootrom command menu, see Avaya Secure Router
2330/4134 Troubleshooting (NN47263-700).
Logging in to the Secure Router 2330/4134

The first time you log on to the Secure Router 2330/4134 CLI, you perform initial configuration
such as the following:
Configure the IP address for the management port.
Configure the next-hop (gateway IP address).
Enable remote access.
Use the procedure in this section to log on to the Secure Router 2330/4134 for the first time.
Prerequisites
You have securely mounted the Secure Router 2330/4134 in an equipment rack.
You have connected a local terminal to the console port of the Secure Router 2330/4134.
You have powered up the Secure Router 2330/4134.
The boot sequence is complete.
Commissioning
October 2010
21
Procedure steps
To log on to the Secure Router 2330/4134 CLI for the first time, enter the default user
name and password: login: admin password: setup
Defining boot parameters

You can configure boot parameters for the Secure Router 2330/4134, if necessary. You
configure boot parameters only if you are having issues to boot the router. For example, you
can change the device from which the router boots (that is, the device that has the software
image) if you want to try to boot the device from a software image on an FTP server in the
network.
The boot parameters are relevant to the boot process only. Any network addressing that you
configure for boot parameters is independent of the normal IP addresses that the router uses in
runtime. The addresses you configure in the boot parameters can be the same as or different
from the IP addresses you configure for normal operation. After the Secure Router 2330/4134
boots, the router no longer uses the information in the boot parameters, but rather the router
uses what you have configured in the system.cfg file.
The Secure Router 2330/4134 provides two bootrom images for redundancy:
normal bootromthe default boot image saved in the normal boot area, and used as your
working bootrom image
golden bootromthe backup boot image saved in the golden boot area, and used if the
normal bootrom image is corrupted
For more information about troubleshooting the Secure Router 2330/4134, see Avaya Secure
Router 2330/4134 Troubleshooting (NN47263-700).
Procedure steps
1. To access configuration mode, enter:
configure terminal
2. To define the boot parameters, enter:
boot_params
Example of defining boot parameters

1. Access configuration mode:
configure terminal
2. Define boot parameters:
boot_params
The router returns the following:
WARNING : Configuration changes not yet saved!
22
Commissioning
October 2010
Defining boot parameters
3. When prompted, enter the name of the device from which you prefer the router
boots:
Boot dev [ftp,cf0,cf1,usb0]: cf0
4. Enter the boot file name (the router provides this information if you have previously
configured it):
Boot file name: SR4134.Z
5. Enter the name of the server you use to download the software image (the router
provides this information if you have previously configured it):
Server name: sunserver
6. Enter the server IP address (the router provides this information if you have
previously configured it):
Server IP address: 10.10.11.12
7. Enter the router IP address (the router provides this information if you have
My IP address: 10.10.13.14
8. Enter the subnet mask (the router provides this information if you have previously
configured it):
My subnet mask: 255.255.255.0
9. Enter the gateway IP address (the router provides this information if you have
Gateway IP address: 10.10.15.16
10. Enter your user name and password:
User name: kevx
Password: kevx
11. Enter 0 to disable or 1 to enable the checksum feature:
Checksum enable [0:Disable,1:Enable]: 1
12. Enter 0 to disable or 1 to enable the display of the image header contents:
Show header enable [0:Disable,1:Enable]: 1
13. Enter the number (0, 1, or 2) that corresponds to the type of bootrom image update
that you prefer, or enter 3 if you prefer to not update the bootrom image:
Save bootrom image [0:AutoUpdate,1:NormalBTupd,
2:GoldenBTupd,3:NoUpd]: 0
If you select 0, 1, or 2, the router returns the following:
Commissioning
October 2010
23
BOOT PARAMETERS HAVE BEEN SAVED.

14. Reboot the Secure Router 2330/4134 to activate changes, or continue with your
configuration:
DO YOU WANT TO REBOOT: (Y/N) ? y
Viewing boot parameters and software image information

Use the procedures in this section to view the boot parameters configuration and to display
information for the normal and golden bootrom images.
Procedure steps
1. To view the boot parameters configuration, enter:
show boot_params
2. 2. To view the current software version information, enter:
show version
Enabling the management LAN port

Enable a management Local Area Network (LAN) port on the Secure Router 4134 for network
management access. To enable the management port, you assign it an IP address.
The Secure Router 2330 does not support a dedicated management LAN port. You can use
one of the front panel Ethernet ports as a management LAN port.
Important:
The Secure Router 4134 management Ethernet interface (FE 0/0) on the rear panel does
not support jumbo frames. Therefore, the management port Maximum Transmission Unit
(MTU) can be configured with a value in the range of 64 to 1500 bytes.
Important:
The Secure Router 4134 management Ethernet interface (FE 0/0) does not support routing
or multicast.
Important:
The Secure Router 4134 management Ethernet interface (FE 0/0) is disabled after boot if
a voice card is installed in the chassis. You can use one of the front panel Ethernet ports
as a management LAN port.
The following figure shows the location of the management port on the rear panel of the Secure
Router 4134.
24
Commissioning
October 2010
Enabling the management LAN port
Figure 8: Management port on the rear panel of the Secure Router 4134
Prerequisites
You must be connected to the Secure Router 2330/4134 through the console port. See
Connecting a terminal for local access on page 17 for information about connecting a
terminal to the console port.
You must log in as a user with sufficient permissions to configure the Secure Router
2330/4134.
You must have the IP address and netmask that you want to assign to the management
port.
The following procedure uses Ethernet port 0/0 (on the rear of the Secure Router 4134) for the
management port. You can also use port 0/1 or port 0/2 on the front panel of the Secure Router
4134 for management purposes. Ethernet port 0/0 is a 10/100 Base-T port. Ethernet ports 0/1
and 0/2 are 10/100/1000 Base-T ports.
On the Secure Router 2330, you can use one of the front panel Ethernet ports as a
management port.
Procedure steps
Commissioning
October 2010
25
configure terminal
2. To identify the management port for configuration, enter:
interface ethernet 0/0
3. To configure the management port IP address, enter:
ip address <ipaddr> <netmask>
4. To configure the speed and mode of the port, enter:
speed <10|100|1000|auto> mode <full_duplex|half_duplex>
Table 2: Variable definitions
Variable
Value
<10 | 100 | 1000 | auto>
The speed of the interface. Enter auto for autonegotiation. Note that Ethernet port 0/0 is a 10/100
Base-T port.
<full_duplex | half_duplex>
The port mode. The default value is half_duplex.
<ipaddr>
The IP address that you assign to the management

port. For example, 10.11.12.13.
<netmask>
The network mask that you assign to the management

port IP address. For example, 255.255.255.0.
Disabling the USB port on the Secure Router 4134

To provide additional security on the router, you can optionally disable the rear-panel USB port.
The Secure Router 2330 does not support a USB port.
Important:
The system configuration must be stored to retain this setting over system reboots.
Procedure steps
configure terminal
2. To disable the USB port, enter:
no usb enable
3. To display the status of the USB port, enter:
show usb_userstat
4. To re-enable the USB port, as required, enter:
26
Commissioning
October 2010
Configuring SSH
usb enable
Configuring SSH
You can enable an SSH connection for remote access. To generate a key and enable SSH,
use the procedures in this section.
Procedure steps
configure terminal
2. To access the SSH key generation subtree, enter:
ssh_keygen
3. To generate the DSA key, enter:
generate dsa
4. To generate the RSA key, enter:
generate rsa
5. To exit the SSH key generation subtree, enter:
exit
6. To enable the SSH connection, enter:
ssh_server enable
7. To save the configuration, enter:
save local
Enabling FTP, TFTP, and Telnet

The default configuration for the Secure Router 2330/4134 includes FTP, TFTP, and Telnet
servers disabled. You can enable any and all of these servers to allow this type of access to
the Secure Router 2330/4134.
Prerequisites
You must assign an IP address to the Secure Router 2330/4134.
Procedure steps
Commissioning
October 2010
27
configure terminal
2. To enable the FTP service, enter:
ftp_server
3. To enable the TFTP service, enter:
tftp_server
4. To enable the Telnet service, enter:
telnet_server
Configuring FTP users

Procedure steps
configure terminal
2. To configure an FTP user, enter a user name:
ftp_user <username>
The default ftp user name is admin.
3. At the prompt, enter a password for the FTP user:
Please enter new password:
<password>
The default ftp user password is admin.

4. At the prompt, re-enter the password:
Please re-enter password:
<password>
If you entered the password correctly, the Secure Router returns a message
indicating a successful configuration:
password is set
5. To verify the current ftp server configuration, enter:
show ftp
Job aid: sample output

The following figure shows sample output for the show ftp command.
28
Commissioning
October 2010
Verifying the Telnet connection
Verifying the Telnet connection

Verify the Telnet connection to ensure that users can successfully access the Secure Router
2330/4134 using remote access.
Prerequisites
The IP address of the management interface on the Secure Router 2330/4134 must be
configured.
You must have the IP address of the management interface on the router.
You must have a terminal or workstation connected to the Ethernet LAN.
Procedure steps
1. To start a Telnet session from your workstation, enter:
telnet <ipaddr>
2. To log in, enter:
login:
admin
password:
setup
Viewing Telnet server settings

View the Telnet server settings for information about the status of the Telnet server (enabled
or disabled) and the Telnet session timeout value.
Procedure steps
To view information about the Telnet server settings, enter:
Commissioning
October 2010
29
show telnet
Clearing a Telnet session

You can disconnect a specific Telnet session, if necessary, or you can disconnect all Telnet
sessions simultaneously.
Procedure steps
1. To view the list of users currently connected using a Telnet session to find the Telnet
session sequence numbers, enter: show users The following figure shows an
example of the Telnet session sequence numbers for users remotely connected to
the router.
2. To clear a specific Telnet session, enter: clear telnet_session <value>

Variable
<value>
Value
The Telnet session sequence number. Enter
a value from 1 to 16.
To quickly disconnect all Telnet sessions, use the command: clear telnet_sessions
Configuring the Telnet banner

You can customize the banner that appears when users access the router using Telnet
services. When configuring the Telnet banner, use \n to begin a new line.
With Release 10.2 and later, you no longer need to use quotes ("") as a delimiter for the banner
text.
30
Commissioning
October 2010
Configuring the Telnet timeout
Procedure steps
configure terminal
2. To configure the Telnet banner, enter:
telnet_banner banner <string> [banner1] [banner2]
Variable
Value
[banner1]
An optional parameter that you use to extend

the banner text. If you require the banner text
be more than 255 characters in length, use
banner1 <string> to continue the
banner text.
[banner2]
An optional parameter that you use to extend

the banner text.
<string>
The banner text that you want to appear in

Telnet sessions. The banner text can be up
to 255 characters in length. Use \n to begin
a new line within the banner.
Configuring the Telnet timeout

You can configure the timeout value for Telnet sessions. A Telnet session disconnects if it
remains inactive for the configured session duration.
Procedure steps
configure terminal
2. To configure the Telnet timeout value, enter:
telnet_timeout <value>
Variable
<value>
Commissioning
Value
Enter the time in seconds (from 0 to 3600)
after which inactive Telnet sessions
automatically disconnect. The default value
is 900 seconds. If you enter a value of 0
October 2010
31
Variable
Value
seconds, inactive Telnet sessions do not
automatically disconnect.
Configuring the host name

Configure a host name for the Secure Router 2330/4134 to uniquely identify it. Once assigned,
the host name becomes the CLI prompt name.
Important:
Changing the host name later (that is, post commissioning), and committing this change,
drops all Telnet and SSH connections. All active console sessions also end.
Procedure steps
configure terminal
2. To configure the host name for the Secure Router 2330/4134, enter:
hostname <WORD>
Variable
<WORD>
Value
The name you want to assign to the Secure
Router 2330/4134.
Configuring the static default route

Configure a static route to specify a preferred route to a destination. You can identify the
gateway, or next-hop, for a static route by specifying one of the following:
IP address of a directly connected interface
name of a local interface such as ethernet0/0
Procedure steps
configure terminal
2. To configure the gateway route, enter:
32
Commissioning
October 2010
Verifying the next-hop connection
ip route <netaddr/mask> <gateway>

Variable
Value
<netaddr/mask>
The IP address and the subnet mask of the

destination network. For example,
11.12.13.14/24. Entering the subnet mask is
optional.
<gateway>
The IP address or interface name of the

gateway. For example, 10.11.12.16.
Verifying the next-hop connection

Use the procedure in this section to verify that the connection from the management interface
successfully connects to the next-hop device.
Prerequisites
You must have the IP address of the next-hop device.
Procedure steps
To ping the next-hop device, enter:
ping <ipaddr>
Configuring the date

To configure the date, you enter the month, day, and year.
Procedure steps
configure terminal
2. To configure the date, enter:
date <month> <day> <year>
Commissioning
October 2010
33

Variable
Value
<day>
The current day in relation to the month.

Enter a value from 1 to 31.
<month>
The current month. Enter a value from 1 to

12.
<year>
The current year. Enter a value from 2000 to

2100.
Configuring the time

To set the current time for the Secure Router 2330/4134, you specify the time in relation to
Coordinated Universal Time (UTC):
time zone offset ahead (+) or behind (-) UTC
number of hours ahead or behind UTC
number of minutes ahead or behind UTC
Procedure steps
configure terminal
2. To configure your local time, enter:
utc <+|-> <hour offset> <minute offset>
Variable
34
Value
<+|->
The time zone offset. Enter + to indicate that

your time zone is ahead of UTC. Enter - to
indicate that your time zone is behind UTC.
For example, if you are in New York, you
enter utc -.
<hour offset>
The number of hours that your local time is

offset from UTC. Enter a value from 0 to 23.
For example, if you are in New York, you
enter utc - 4.
<minute offset>
The number of minutes that your local time

is offset from UTC. Enter a value from 0 to
Commissioning
October 2010
Configuring multiple SNTP servers
Variable
Value
59. For example, if you are in New York, you
enter utc - 4 0.
Configuring multiple SNTP servers

The Secure Router 2330/4134 supports the Multiple Simple Network Time Protocol (SNTP)
Server feature. SNTP is a simple form of the Network Time Protocol (NTP), which is an internet
protocol used for synchronization of computer clocks.
The Multiple SNTP Server feature provides support for up to 10 SNTP servers. Multiple servers
provide redundant backup for synchronizing time on the Secure Router. During configuration,
servers can be specified by hostname or IP address, and a timeout value must be set for the
query. The Multiple SNTP Server features operates by having the SNTP service query
configured SNTP servers on a round-robin basis. If an SNTP server is queried and fails to
respond, the router sends a request to the next configured SNTP server. The SNTP server
support is not active until the service is enabled. While the service is enabled the configuration
cannot be changed.
The show sntp command has been modified to display the current state of SNTP, the server it
is contacting to receive the current time, as well as all configured servers. When specifying a
server by domain name, DNS entries need to be configured before SNTP functions properly.
Use the following procedure to configure multiple SNTP servers.
Procedure steps
1. To configure multiple SNTP servers, enter Configuration Mode.
configure terminal
2. Because DNS entries must be configured for SNTP to function properly, configure
primary and secondary DNS servers.
ip pname_server <address> ip name_server <address>
3. To configure an SNTP server, enter the sntp sub-tree.
sntp
4. Configure the source address of the SNTP client.
source-address <address>
5. Configure the number of retries for each SNTP server.
retries <count>
6. Configure an NTP server.
server <server> [timeout]
Commissioning
October 2010
35
7. To add up to 10 SNTP servers, repeat step 6.

8. Enable the SNTP client.
enable
Variable
Value
<address>
Specifies an IP address.
<count>
Specifies the number of retries the NTP server performs, in

the range 15. Default is 3.
<server>
Specifies the NTP server to use for updates.
<timeout>
Specifies the maximum response time, in the range 10

7200. Default is 1024.
Configuring the SNTP client

The Simple Network Time Protocol (SNTP) synchronizes the internal clocks of various network
devices across large, diverse networks to universal standard time. Use the procedure in this
section to enable the SNTP client on the Secure Router 2330/4134.
Procedure steps
configure terminal
2. To set the location of the SNTP server, enter:
sntp server {ipaddr|hostname}
3. To set the timeout value for the response from the server, enter:
sntp timeout <value>
Variable
36
Value
{ipaddr | hostname}
The IP address or host name of the

broadcast server. The default value is any
broadcast server.
<value>
The timeout value in seconds. The default

timeout value is 1024 seconds.
Commissioning
October 2010
Displaying the SNTP configuration
Displaying the SNTP configuration

Use this procedure to display the SNTP configuration.
Procedure steps
To display the SNTP configuration, enter:
show sntp
Configuring the SNTP source address

Use the following procedure to configure the SNTP server source address for all services.
Procedure Steps
1. To configure source addresses for a service, enter Configuration Mode.
configuration terminal
2. Enter the sntp subtree
sntp
3. Configure the source address.
source-address <[ip-address]|[interface-name]>
Variable
Value
[ip-address]
Specifies the source address by IP address.
[interface-name]
Specifies the source address by interface name.
Configuring daylight saving time

The daylight saving time (DST) feature allows you to configure a time offset for daylight saving.
Use the procedure in this section to configure DST on the Secure Router 2330/4134.
Procedure steps
Commissioning
October 2010
37
configure terminal
2. To configure the DST offset, enter:
dst set <device location> <start hour> <start minute> <start
week of month> <start day of week> <start month> <end hour>
<end minute> <end week of month> <end day of week> <end month>
<dst duration hrs> <dst duration minutes>
3. To enable DST, enter:
dst enable
4. To disable DST, enter:
no dst enable
5. To display the DST configuration and status, enter:
show dst
Variable
38
Value
<device location>
Specifies the location of the device.
<start hour>
Specifies the start hour (00 - 23), in other

words, the hour at which the DST offset time
begins.
<start minute>
Specifies the start minute (00 - 59)
<start week of month>
Specifies the start week of <start month> (1

- 4)
<start day of week>
Specifies the start day of week (0 - sunday,

6 - saturday)
<start month>
Specifies the start month of year (1 - 12)
<end hour>
Specifies the end hour (00 - 23), in other

words, the hour at which the DST offset time
ends.
<end minute>
Specifies the end minute (00 - 59)
<end week of month>
Specifies the end week of <end month> (1 4)
<end day of week>
Specifies the end day of week (0 - sunday,

6 - saturday)
<end month>
Specifies the end month of year (1 - 12)
<dst duration hrs>
Specifies the number of offset hours to add

to the time at the start of DST (and remove
at the end of DST).
Commissioning
October 2010
Example of configuring daylight saving time
Variable
Value
Specifies the number of offset minutes to add
to the time at the start of DST (and remove
at the end of DST).
<dst duration minutes>
Example of configuring daylight saving time

Consider the following DST scenario:
DST start: 2nd Sunday of April at 2:00 AM
DST end: 2nd Sunday of October at 2:00 AM
Offset time amount: 1:00 hours
To achieve this configuration, consider the following:
Parameter
DST start: 2nd

Sunday of April at
2:00 AM
DST end: 2nd Sunday

of October at 2:00 AM
Offset time
amount: 1:00
hours
start hour
start minute
start week of month
start day of week
start month
end hour
end minute
end week of month
end day of week
end month
10
dst duration hrs
dst duration minutes
To configure DST for this example, use the following procedure.
Procedure steps
1. To enter configuration mode, enter:
configure terminal
2. To configure the DST for this example, enter:
Commissioning
October 2010
39
dst set LOCATION 2 0 2 0 4 2 0 2 0 10 1 0

3. To enable DST, enter:
dst enable
This configuration provides the following outcome:
For year 2009: DST start: SUN APR 12 02:00:00 2009 DST end: SUN OCT 11 02:00:00 2009
For year 2010: DST start: SUN APR 11 02:00:00 2010 DST end: SUN OCT 10 02:00:00 2010
Changing the admin user password

The system administrator login consists of two components: the account name and the
password. The initial login name is always "admin". You can change this after logging in for
the first time. The default administrative password is "setup". Avaya recommends you change
the default password as soon as possible to ensure only authorized personnel can access the
Secure Router 2330/4134.
Procedure steps
1. To access password configuration mode, enter:
password
The Secure Router 2330/4134 prompts you for the current user name.
2. Enter the default user name, which is the current user name:
admin
The Secure Router 2330/4134 prompts you for the old password.
3. Enter the default password, which is the current password:
setup
The Secure Router 2330/4134 prompts you for the new password.
4. Enter your new password. The Secure Router 2330/4134 prompts you to verify the
new password.
5. Re-enter your new password. A message appears that confirms that the password
is changed.
40
Commissioning
October 2010
Changing the administrator account name
Changing the administrator account name

Use the procedure in this section to change the administrator login name (Level 1 access) to
a user-specified name. The default login name for the Secure Router 2330/4134 is "admin".
The administrator login name can be from 3 to 39 characters in length.
Procedure steps
configure terminal
2. To change the login name, enter:
admin_name <WORD>
The Secure Router 2330/4134 displays a message that confirms the login name is
successfully changed.
Adding users
You can identify users (that is, login names) who can access the Secure Router 2330/4134,
and assign each user an access privilege (levels 24). Only the system administrator (level 1
access) can add, modify, or remove this information from the system.
Procedure steps
configure terminal
2. Enter the user name and access level:
user <username> level <value>
The Secure Router 2330/4134 prompts you to enter a password for this user.
3. Enter a password (from 0 to 10 characters) for the new user. The Secure Router
2330/4134 prompts you to re-enter the password.
4. Re-enter the password for the new user. The Secure Router 2330/4134 confirms
that the password is set and confirms the name of the new user is added.
Commissioning
October 2010
41

Variable
Value
<username>
The user name you want to add to the Secure

Router 2330/4134. The user name can
contain up to 39 characters.
<value>
The access level assigned to the user.

Values are 24. The lower the access level
value, the higher the access privileges. For
example, a user with an access level of 2 has
more privileges than a user with an access
level 3 or 4.
Procedure job aid

The CLI supports four levels of privilege for users. The following table defines each level.
Table 15: CLI user access levels
Privilege level
Privilege name
Definition
1 (highest)
PRIVILEGE_ADMIN
Admin level can access any

command and configure any
feature in the router,
including user configuration
and administration.
PRIVILEGE_CONFIGURE
Configure level can configure

any feature. Cannot add or
delete users.
PRIVILEGE_TEST
Test level can only run

diagnostic tests. Cannot
access configuration
commands.
4 (lowest)
PRIVILEGE_NORMAL
Normal level can only enter

show or display
commands.
Removing users
The system administrator can remove configured user names from the Secure Router
2330/4134.
Important:
To reset a user password, you must delete and then recreate the user account.
42
Commissioning
October 2010
Pinging a device
Procedure steps
configure terminal
2. To remove a user, enter:
no user <username>
Pinging a device
Ping a device to verify the connection between the Secure Router 2330/4134 and that network
device. If the network device sends a ping reply, a message indicates that the specified IP
address is alive and can communicate with the router. If the router does not receive a reply,
the message indicates that the address is not responding.
Prerequisites
You must physically connect the Secure Router 2330/4134 to the network.
You must physically connect the specific network device to the network.
Procedure steps
Ping the network device:
ping <ipaddr>
Saving a configuration
Issue the save command to save the running configuration to a file. You can save the
configuration to the local file system, or to a file on the network.
Procedure steps
1. To save the configuration to the local file system, enter:
save local [file <filename>]
2. To save the configuration to a network file, enter:
save network <ipaddr> <path>
Variable
[file <filename>]
Commissioning
Value
The name of the file to which the
configuration is saved. This is an optional
October 2010
43
Variable
Value
parameter. The configuration is saved to the
system default file (system.cfg) if you do not
specify a filename.
<ipaddr>
The IP address of the device on which you

store the network configuration file.
<path>
The full path of the remote configuration file.
Deleting a configuration file

Delete the .cfg file to remove a configuration file from the flash. Use this command with caution
as it can delete all current configurations from the router. If you do not specify a filename, the
command deletes the system.cfg file by default.
Procedure steps
1. To delete the current configuration file, enter:
clear cfg_file [<filename>]
A prompt appears asking you to confirm the operation.
2. Enter y to delete, or n to cancel the operation.
Variable
[<filename>]
Value
The name of the file to delete. This is an
optional parameter. if You do not specify a
filename, the router deletes the system
default file (system.cfg).
Rebooting or resetting the Secure Router 2330/4134

Reset and reboot the Secure Router 2330/4134 properly to avoid file system corruption.
Resetting the router returns it to a factory-default configuration. Rebooting the router shuts
down and restarts the system. The procedure in this section shows you how to reset the
configuration on the Secure Router 2330/4134, reboot the router to restore the factorydefault settings, and save the factory-default settings to the configuration file.
44
Commissioning
October 2010
Powering down the Secure Router 2330/4134
Important:
If you have the Mediation Server Module installed on the SR4134, there is a 2-minute delay
after you issue the reboot command while the router waits for the module to shut down.
The chassis reboots automatically when the Mediation Server Module completes shutdown.
Procedure steps
configure terminal
2. To reset the Secure Router 2330/4134, enter:
system reset-to-factory {system|users}
3. To exit configuration mode, enter:
exit
4. To reboot the Secure Router 2330/4134, enter:
reboot
Issue the reboot command from the CLI root.
5. When the Secure Router 2330/4134 completes the reboot, save the factorydefault settings to the system.cfg file by entering:
save local
Variable
{system | users}
Value
Enter system to remove all information
stored in memory, which includes user
information, event logs, crash logs,
command logs, and boot parameters.
Enter users to remove all users and
information related to users.
Powering down the Secure Router 2330/4134

Use the procedure in this section if you must power down the Secure Router 2330/4134. For
example, Avaya strongly recommends that you power down the router to install an interface
module in a slot in which that module has not previously been installed. You must also power
down the Secure Router 4134 before opening the service access panel on the rear of the
router, or when removing the cover from the Secure Router 2330.
Commissioning
October 2010
45
Prerequisites
Ensure you have backed up your system configuration. Use the save local command to
save your configuration.
Procedure steps
1. To shut down the system, enter:
reboot
If you have the Mediation Server Module installed on the SR4134, there is a 2minute delay after you issue the reboot command while the router waits for the
module to shut down. The chassis reboots automatically when the Mediation Server
Module completes shutdown.
2. When the system restarts (you will see memory tests begin on your console), power
down the Secure Router 4134 by putting the power switch (or power switches if you
have more than one power supply installed) in the "off" position. To power down the
Secure Router 2330, disconnect the power cord.
Viewing the Secure Router 2330/4134 configuration

View the Secure Router 2330/4134 configuration to understand the current state of the system
software.
For more information about using commands, see Avaya Secure Router 2330/4134 Using
the Command Line Interface (NN47263-506). For a complete list of CLI commands, see Avaya
Secure Router 2330/4134 Command Line Reference (NN47263-507).
Procedure steps
1. To view the current configuration, enter:
show configuration running
You can also enter show running-config to view the current configuration.
2. To view the configuration that is stored in Flash, enter:
show configuration stored
You can also enter show startup-config to view the stored configuration.
Viewing chassis status

Use the procedure in this section to view summary information about the Secure Router
2330/4134 chassis, including its operational status. After you install interface modules, you
46
Commissioning
October 2010
Viewing interface module configuration
can use the show chassis command to verify that the Secure Router 2330/4134 recognizes
the modules.
Procedure steps
To view summary information about the Secure Router 2330/4134, enter:
show chassis
Viewing interface module configuration

Use the procedure in this section to quickly check the state and configuration of installed
interface modules.
Procedure steps
1. To view the configuration of interface modules installed in your Secure Router
2330/4134, enter:
show module configuration all
2. To view the configuration of individual interface modules, enter:
show module configuration [t1|e1|ct3| serial|hssi|t3] <slot/
port>
Checking the system for alarms

The Secure Router 2330/4134 reports alarms when it detects irregular conditions in incoming
signals to the interface modules. Use the show module alarms command to quickly check
for any irregularities.
Procedure steps
1. To view the current alarms for any T1 WAN link on the Secure Router 2330/4134,
enter:
show module alarms t1 <slot/port>
2. To view the current alarms for any E1 port on the Secure Router 2330/4134, enter:
show module alarms e1 <slot/port>
3. To view the current alarms for any CT3 port on the Secure Router 4134, enter:
show module alarms ct3 <slot/port>
4. To view the current alarms for any serial port on the Secure Router 2330/4134,
enter:
Commissioning
October 2010
47
show module alarms serial <slot/port>

5. To view the current alarms for any HSSI port on the Secure Router 4134, enter:
show module alarms hssi <slot/port>
6. To view the current alarms for any T3 port on the Secure Router 4134, enter:
show module alarms t3 <slot/port>
Checking the system status

You can view the operating status and current configuration of each WAN, Ethernet, or serial
interface using the show module configuration command. Refer to Avaya Secure Router
2330/4134 Command Line Reference (NN47263-507) for a complete list of CLI commands
for the Secure Router 2330/4134.
Procedure steps
View the operating status of all installed interface modules:
show module configuration all
Configuring reverse Telnet on the Secure Router 4134

Reverse Telnet gives you the ability to Telnet to a device, and then use a console connection
to connect to another device from there. For example, you can Telnet to a router, and then
connect into a switch, modem, or any other device that has a console port. There are many
devices that do not have remote access built into them, and the only access option for these
devices is a console session. With reverse Telnet, you can remotely manage these type of
devices through the Secure Router 4134.
The Secure Router 2330 does not have an AUX port and therefore cannot support reverse
Telnet.
1. Connect a straight-through cable from the console port of the console-only device
to the AUX port on the Secure Router 4134.
2. In the CLI, to enter configuration mode, enter:
configure termainal
3. To specify reverse Telnet configuration, enter:
reverse_telnet
The following steps allow you to configure the AUX port of the Secure Router 4134
with the proper settings for the console connection to the remote device.
48
Commissioning
October 2010
Configuring reverse Telnet on the Secure Router 4134
4. To configure the baud rate, enter:

set_baud_rate <baud_rate>
5. To configure the data bits, enter:
set_data_bits <data_bits>
6. To configure the flow control, enter:
set_flow_control <flow-control>
7. To configure the parity, enter:
set_parity <parity>
8. To configure the stop bits, enter:
set_stop_bits <stop_bits>
9. To configure the revers telnet port, enter:
telnet_port <telnet_port>
10. To configure the timeout, enter:
telnet_timeout <telnet_timeout>
11. To enable reverse Telnet, enter:
[no] enable
Variable
Value
<baud_rate>
Sets the speed of the AUX port. Range is 50 115200 (default 9600).
<data_bits>
Configures the data bits on the AUX port.
<flow-control>
Configures flow control on the AUX port.

Range: 0-none, 1-software, 2-hardware
(default: 0).
<parity>
Sets parity of the AUX port. Range: 0-none,

1-odd, 2-even (default: no parity).
<stop_bits>
Configures the number of stop bits on the

AUX port. Range: 1 - 2 (default 1).
<telnet_port>
Specifies the Telnet port which reverse

Telnet listens on to establish the remote
console though the AUX port. Range :2000 65535 (default 2001).
<telnet_timeout>
Specifies the timeout for the reverse telnet

session in seconds. Range: 0 ( disable
timeout) - 7200 (default 600).
Commissioning
October 2010
49
Variable
[no] enable
Value
Activates the reverse Telnet functionality on
the router. The no option deactivates reverse
Telnet.
Copying an external compact flash or a USB drive file

Use this procedure to copy a file to or from an external compact flash drive or a USB drive.
Procedure steps
1. Insert a compact flash drive or USB drive into the router.
2. To copy a file, enter:
file copy <source_file> <dest_file>
Variable
Value
<source_file>
Specifies the source file name.
<dest_file>
Specifies the destination file name.
Downloading a network file to a compact flash or a USB

drive
Use this procedure to download a file from the network to an internal or external compact flash
drive or a USB drive.
Procedure steps
2. To copy a file, enter:
file download <host_ipaddr | host_ipv6addr> <source_file>
<dest_file> [interface <interface>] [id <user_id>] [passwd
<user_passwd>] [mode {image | file}] [source-address
<src_ipaddr>]
50
Commissioning
October 2010
Formatting the external compact flash file system

Variable
Value
<dest_file>
Specifies the name of the destination file.
<host_ipaddr |
host_ipv6addr>
Specifies the host IPv4 or IPv6 address.
[id <user_id>]
Specifies the user ID.
[interface <interface>]
Specifies the outgoing interface. For example,

ethernet0/2.
[mode {image | file}]
Specifies the file download mode. Options are image or file.

The default is file.
If you are downloading a Secure Router image, be sure to
set the mode to image.
[passwd <user_passwd>]
Specifies the user password.
[source-address
<src_ipaddr>]
Specifies the source IP address.
<source_file>
Specifies the source file name in the format <dirpath/

filename>.
Formatting the external compact flash file system

Use this procedure to format the USB drive for the FAT 16 or FAT 32 file system.
Procedure steps
1. Insert a compact flash drive into the router.
2. To format the compact flash drive, enter:
format </cf0 | /cf1> <16> | <32>
The following message is displayed:
WARNING :Do not remove the Compact Flash during this process
Do not reboot this device during this process
COMPACT FLASH FORMAT: Are you sure ? (y/n) :
3. To approve the formatting, enter:
y
Erasing Compact Flash Blocks. Please wait till
completedCompact flash formatting completed
Commissioning
October 2010
51

Variable
Value
<16>
Specifies the FAT 16 file system.
<32>
Formatting the USB drive file system

Use this procedure to format the USB drive for the FAT 16 or FAT 32 file system.
Procedure steps
1. Insert a USB drive into the router.
2. To format the USB drive, enter:
format /usb0 <16> | <32>
WARNING :Do not remove the Compact Flash during this process
Do not reboot this device during this process
COMPACT FLASH FORMAT: Are you sure ? (y/n) :
3. To approve the formatting, enter:
y
Variable
Value
<16>
<32>
Listing files on a compact flash drive or USB drive

Use this procedure to list the files stored on a compact flash drive or USB drive.
Procedure steps
2. To list stored files, enter:
52
Commissioning
October 2010
Listing image version files from a compact flash drive or USB drive
file ls [file_system </cfo | /cf1 | /usb0>]

Variable
[file_system </cfo | /cf1 | /usb0>]
Value
Specifies a specific file system from which to
list stored files.
Listing image version files from a compact flash drive or

USB drive
Use this procedure to list versions of the image files from a compact flash drive or USB drive.
Procedure steps
file version [file_name </cfo | /cf1 | /usb0>]
Variable
[file_name </cfo | /cf1 | /usb0>]
Value
Specifies a specific device from which to list
the image version files.
Removing a file from a compact flash drive or USB drive

Use this procedure to remove a file stored on a compact flash drive or USB drive.
Procedure steps
file rm <path_filename>
Variable
<path_filename>
Commissioning
Value
Specifies the path and name of the file to
remove.
October 2010
53
Renaming a file on a compact flash drive or USB drive

Use the following procedure to rename a file stored on a compact flash drive or USB drive.
Procedure Steps
file rename <current_filname> <new_filename>
Variable
Value
<current_filname>
Specifies the file to be renamed.
[interface-name]
Specifies the new name for the file.
Uploading files from a compact flash drive or USB drive

Use this procedure to upload files to the Secure Router from a compact flash drive or USB drive.
Procedure steps
file upload <src_filename> <host_ipaddr | host_ipv6addr>
<dest_filname>
Variable
54
Value
<dest_filname>
Specifies the destination file name,

expressed in the directory path/filename
format.
<host_ipaddr | host_ipv6addr>
Specifies the host IPv4 or IPv6 address.
<src_filename>
Specifies the source filename, expressed in

the device/filename format.
Commissioning
October 2010
Uploading the event log from the Secure Router 2330/4134
Uploading the event log from the Secure Router 2330/4134

Use this procedure to upload the event log from the Secure Router to the network.
Procedure steps
file upload_event_log <host_ipaddr | host_ipv6addr>
<remote_filename> <src_ipaddr>
Variable
Value
<host_ipaddr | host_ipv6addr>
Specifies the IPv4 or IPv6 address the file is

to be uploaded to.
<remote_filename>
Specifies the name of remote filename to

apply to the event log.
<src_ipaddr>
Specifies the source IP address.
Commissioning
October 2010
55
56
Commissioning
October 2010

NN47263-302 04.01 Commissioning

Uploaded by

Document Information

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

NN47263-302 04.01 Commissioning

Uploaded by

Copyright:

Available Formats

Commissioning

Avaya Secure Router 2330/4134

2010 Avaya Inc.

All Rights Reserved.

protected by copyright and other intellectual property laws including the

Chapter 3: Avaya Secure Router 2330/4134 commissioning................................................9

Chapter 4: Commissioning the Avaya Secure Router 2330/4134.......................................15

Chapter 1: New in this release

FAT 32 File System Support for SR 4134 and SR 2330

Multiple SNTP Server support

New in this release

Chapter 3: Avaya Secure Router 2330/4134

Secure Router 2330/4134 commissioning procedures

Avaya Secure Router 2330/4134 commissioning

Figure 1: Secure Router 2330/4134 commissioning procedures

Secure Router 2330/4134 commissioning procedures

Figure 2: Secure Router 2330/4134 commissioning procedures (continued)

Avaya Secure Router 2330/4134 commissioning

Secure Router 2330/4134 commissioning navigation

Secure Router 2330/4134 commissioning navigation

Saving a configuration on page 43

Avaya Secure Router 2330/4134 commissioning

Chapter 4: Commissioning the Avaya

Gathering required information

Procedure job aid

New password for admin

Record information here

Management IP address and 10.11.12.13 255.255.255.0

The following figure is an example of a commissioning scenario showing the basic

Commissioning the Avaya Secure Router 2330/4134

Figure 3: Commissioning scenario

Figure 4: Secure Router 2330 Commissioning scenario

Connecting a terminal for local access

Connecting a terminal for local access

Procedure job aid

Commissioning the Avaya Secure Router 2330/4134

Figure 5: Connect a local terminal to the Secure Router 4134

Figure 6: Connect a local terminal to the Secure Router 2330

Powering up the Secure Router 2330/4134

Powering up the Secure Router 2330/4134

Procedure steps (AC power)

Commissioning the Avaya Secure Router 2330/4134

3. Verify that diagnostic testing is underway by observing the startup messages on

Procedure steps (DC power on Secure Router 4134)

Logging in to the Secure Router 2330/4134

Figure 7: Accessing the bootrom command menu

Logging in to the Secure Router 2330/4134

Commissioning the Avaya Secure Router 2330/4134

Defining boot parameters

Example of defining boot parameters

Defining boot parameters

Commissioning the Avaya Secure Router 2330/4134

BOOT PARAMETERS HAVE BEEN SAVED.

Viewing boot parameters and software image information

Enabling the management LAN port

Enabling the management LAN port

Commissioning the Avaya Secure Router 2330/4134

<10 | 100 | 1000 | auto>

The port mode. The default value is half_duplex.

The IP address that you assign to the management

The network mask that you assign to the management

Disabling the USB port on the Secure Router 4134

Enabling FTP, TFTP, and Telnet