NETWORK EQUIPMENT TECHNOLOGIES, INC. (hereinafter referred to as "N.E.T."), PROVIDES THIS
DOCUMENT AS IS, WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE.
No part of this publication may be stored in a retrieval system, transmitted or reproduced in any way, including photocopy, photograph, magnetic, or other record, without the prior written permission of N.E.T. Unpublished-rights
reserved under the copyright laws of the United States.
Trademarks
The N.E.T. logo, PanaVue, PrimeSwitch, Promina, SCREAM, Service Creation Manager, and SHOUTIP are
registered trademarks, and CellXpress, FrameXpress, Frame Relay Exchange, IPNX, LAN/WAN Exchange, Network
Equipment Technologies, N.E.T., the net.com logo, net.com, netMS, PortExtender, PrimeVoice, SCREAMvue, and
SHOUT are trademarks of Network Equipment Technologies, Inc.
SunOS and Solaris software copyright is held by Sun Microsystems, Inc. Sun Microsystems is a registered trademark
and Sun, SunOS, OpenWindows, Solaris, and Ultra are trademarks of Sun Microsystems, Inc. UNIX is a registered
trademark of The Open Group.
All other trademarks and registered trademarks are the sole property of their respective owners.
This document constitutes the sole Specifications referred to in N.E.T.'s Product Warranty for the products or services
described herein. N.E.T.’s Product Warranty is subject to all the conditions, restrictions, and limitations contained
herein and in the applicable contract. N.E.T. has made reasonable efforts to verify that the information in this document is accurate, but N.E.T. reserves the right to correct typographical errors or technical inaccuracies. N.E.T.
assumes no responsibility for any use of the information contained in this document or for any infringement of patents or other rights of third parties that may result from the use of this document. Networking products cannot be
tested in all possible uses, configurations or implementations, and interoperability with other products cannot be
guaranteed. The customer is solely responsible for verifying the suitability of N.E.T.'s products for use in its network.
Local market variations may apply. This document is subject to change by N.E.T. without notice as additional information is incorporated by N.E.T. or as changes are made by N.E.T. to hardware or software.
U.S. Government Rights, Government Users
The software accompanying this documentation is furnished under a license and may only be used in accordance with
the terms of such license. This documentation is "commercial computer software documentation" as that term is used
in 48 CFR 12.212. Unless otherwise agreed, use, duplication, or disclosure of this documentation and any related
software by U.S. Government civilian agencies is subject to restrictions as set forth in 48 CFR 52.227-14 (ALT III)
and 48 CFR 52.227-19, and use, duplication, or disclosure by the U.S. Department of Defense is subject to restrictions as set forth in 48 CFR 227.7202-1(a) and 48 CFR 227.7202-3(a) or, if applicable, 48 CFR 252.2277013(c)(1)(ii) (OCT 1988).
Released
July 2006
Network Equipment Technologies, Inc.
6900 Paseo Padre Parkway
Fremont, CA 94555 U.S.A.
http://www.net.com
iiLAN/WAN Exchange Installation and Configuration Guide Release 3.04
SSH Sessions from a UNIX Server ........................................................................................ A-8
Restricting Transport Protocol Access ......................................................................................... A-9
Index ..................................................................................................................................................1
viLAN/WAN Exchange Release 3.04Installation and Configuration
This document provides information about the LAN/WAN Exchange
(LWX) application for use with the PX3 card. This document is for use in
the installation and management of the LWX application with the
Promina Series of Multiservice Access Platforms.
This document assumes that you have a working knowledge of data
communications, LAN and WAN routing principles, trunking and
transmission concepts, Cisco IOS commands, features, and concepts, and
PX3 card operation. You should also be aware of the hazards associated
with electronic equipment and electricity, a detailed discussion of which
is beyond the scope of this document.
Screen displays are provided as examples of output. Because the
displayed information is dependent on each node’s configuration, the
examples shown in this document may not correspond exactly to the
information displayed by another node. Differences in software releases
can also account for differences in displayed information.
Document Organization
The document contains the following sections:
SectionTitleDescription
Chapter 1IntroductionProvides an overview of the product.
Chapter 2Installing and
Chapter 3Verifying the
Chapter 4Upgrading the LWX
Chapter 5Problem ChecklistsProvides checklists for addressing
Chapter 6Alarms and EventsDescribes the events generated by the
Chapter 7SNMP OverviewDescribes the SNMP agents used in the
Configuring LWX
Configuration and
Connections
Application
Provides LWX installation and
configuration procedures.
Describes how to verify the configuration
and existing connections.
Describes how to upgrade the LWX
application.
installation problems.
LWX application.
LWX application.
Chapter 8Agent ConfigurationDescribes how to install and configure the
SNMP agents used in the LWX
application.
Installation and Configuration GuideLAN/WAN Exchange Release 3.04xvii
We encourage comments on the content of this document. Please address
any comments to:
Manager, Information Development
N.E.T.
6900 Paseo Padre Parkway
Fremont, California 94555
infodev@net.com
N.E.T. may use or distribute, without incurring any obligation, and in any
way it believes appropriate, any information supplied.
Technical Assistance Information
If there is a problem installing or using N.E.T. products, contact your
technical support organization. For those customers who have access to
the N.E.T. Technical Assistance Center (TAC), the toll-free number for
the United States is:
1-800-800-4638
For N.E.T.’s TAC support, customers outside the United States, except in
the UK and Europe, may use the following number:
703-724-7999
For N.E.T.’s TAC support, UK and European customers can use the
following number:
(44) 1293-600703
TAC personnel are available by telephone 24 hours a day, 7 days a week.
Warranty and contract customers receive first consideration in the
scheduling of technical resources.
Before contacting TAC for help, review and verify the provisions
contained in your warranty or contract. Depending on those provisions,
there may be a charge for service.
When authorized, TAC engineers can diagnose most network problems
remotely, using dial-up connections. When a service technician is
required, TAC will dispatch the nearest N.E.T. or third-party service
engineer.
xxLAN/WAN Exchange Release 3.04Installation and Configuration Guide
The LAN/WAN Exchange (LWX) application is a general purpose
router/bridge application integrated into the Promina Series platform,
providing internetwork connectivity between LANs over WANs that
contain Promina Series nodes. The LWX application is used in
conjunction with a PX3 front card and an Ethernet or Token Ring
interface rear card, and provides:
•concurrent multi-protocol routing and fallback MAC layer bridging
•up to eight logical serial connections to other LWXs or external
routers
Supported PX3
and Interface
Cards
Memory
Requirements
LWX Release 3.04 supports four- and eight-port PX3 cards1 with
Ethernet and Token Ring interface cards (T1/Ethernet and E1/Ethernet
are not supported). LWX Release 3.04 requires PX3 cards of a certain
revision level, as shown in Table 1-1.
Table 1-1Supported PX3 Revision Levels
Assembly No.Revision Level
#027074-405 (4-port)
#027075-407 (8-port)
#029756-405 (4-port)
#029757-407 (8-port)
Rev. B or higher
Rev. A or higher
LWX Release 3.04 also requires Release 1.2.2.9 or higher of the PX3
Bootstrap software.
The minimum memory requirements for LWX Release 3.04 are shown in
Table 1-2:
Table 1-2Minimum Memory Requirements
FlashSystem DRAMPacket DRAM
16 MB16 MB16 MB
Base and Global
Versions
The LWX application is available in two versions, base and global. The
base version supports a basic set of functions:
•Interfaces: Ethernet and serial ports
•Protocols: IP, IPX, SNMP, and transparent bridging
1.Support for 16-port PX3 cards may be included in a future release.
•WAN services: HDLC, frame relay, X.25, PPP, and SMDS
•Compatible with the Cisco IP/IPX products
•Supports flash memory, NVRAM DOS filesystem
•Supports upgrades using PCMCIA cards (Release 3.02.03 or later)
The global version supports all the base functions, and these additional
functions:
•Interfaces: Token Ring
•Protocols: Decnet IV, Decnet V, Appletalk, XNS, Vines, OSI, and
Apollo
•IP routing: ES-IS and IS-IS
•IBM support: RSRB, local ack, address priority, NETBIOS name
cache, STUN, SDLLC, and DLSw+ (does not support APPN)
•WAN services: SDLC
The LWX application is based on the Cisco Internetwork Operating
System (IOS), Release 11.2.14. To configure LWX, you need to use
Cisco IOS commands. For information about Cisco IOS Release 11.2
commands, see the Cisco IOS Software Configuration document set.
The LWX application is designed to satisfy LAN/WAN interoperability
and connectivity requirements of multi-protocol, multimedia, and
multivendor networks.
Support for
Multi-Protocol
Networks
The LWX application supports various routing protocols: AppleTalk,
DECnet, Novell, CLNS static, and IP. Bridging support includes:
Transparent, Remote Source Route, Fast Sequenced Transport, LLC2,
SNA, and NETBIOS1.
Supported MediaIn addition to Ethernet and Token Ring interfaces, the LWX application
supports internal synchronous serial speeds up to 4096 Kbps on a
Promina 800 node (2048 Kbps on a Promina 400 or 200 node).
Dynamic Network
Routing
The LWX application supports various dynamic routing protocols, such
as IGRP, OSPF, RIP, BGP, GDP, SPLIT Horizon, IRDP, and IS-IS, to
ensure reliable packet routing. LAN traffic can be routed by the logical
network, through a protocol such as IGRP and EIGRP. Traffic can also be
routed by the Promina network itself.
Dynamic
Bandwidth Setting
Dynamic Routing
Tables
Bandwidth is dynamically adjusted to respond to network changes,
ensuring that reliable bandwidth is available for network traffic.
LAN traffic is automatically routed either through the logical LAN
network or through the Promina network.
LWX software is stored in flash memory on the PX3 card. In the event of
a failure, software is automatically loaded from the flash memory. The
Promina can also distribute software upgrades (for example, using FTP
across an interface card) and provide out-of-band diagnostics to the LWX
application.
1.There are limitations on NETBIOS support over Token Ring.
Access MethodsYou connect to the LWX application in one of three ways:
•Remotely using telnet
•Through the Promina node using the Connect to PX Card feature.
•Through a terminal connected to the UART connector on the PX3
card
Network SecurityYou can secure the LWX application and your data from unauthorized
use by:
•Limiting access to the privileged command set and to console and
terminal lines by using operator account passwords.
•Restricting transmissions to specified addresses (such as ports, hosts,
and gateways) using access lists.
•Providing controls according to the service used (such as mail, file
transfers, and remote login).
•Using DDN security options for IP packets.
•Using Secure Shell (SSH v1) sessions for securing file management
traffic flowing into and out of the LWX network. For this release, the
SSH package is imported from Cisco IOS Release 12.3.10. This
implementation utilizes DES encryption (56-bit) with
password-based authentication.
•Disabling or restricting standard session access or standard file
transfer access.
Network
Management
You can manage the LWX application using a network management
system that supports the Simple Network Management Protocol (SNMP),
such as HP OpenView.
Backup and
Restore
LWX Release 3.04 and higher provides a mechanism to backup and
restore the configuration files for managed nodes from a network
management workstation.
SNMP v3 SupportLWX Release 3.03 and higher now supports SNMP v3. However, the
implementation of SNMP v3 on the LWX application will still have the
same limitations as Cisco IOS Release 12.1.
Note: This manual, Installation and Configuration Guide, is the key resource for
LWX operations and initial installation tasks. The Cisco IOS Release 11.2
Software Configuration documentation set provides essential information to
install and configure the LWX application.
Figure 1-1 shows where to go for information on installing and
configuring the LWX application. For the three tasks shown, an arrow
points to support documentation for each task. The gray (bottom row)
arrows indicate cross references from one document to another.
LWX Release 3.04 supports most of the features and functions in Cisco
IOS Release 11.2, which are described in the accompanying Cisco
document set Cisco IOS Release 11.2 Software Configuration. Features
and functions described in Cisco documentation but not supported by
LWX fall into three categories:
•Features and functions no longer supported by Cisco: Unsupported
Software Functions on page 1-7.
•Differences in platform function: Platform Functionality Differences
on page 1-7.
•Differences in platform configuration: Platform Configuration
Differences on page 1-8.
Unsupported
Software
Functions
Platform
Functionality
Differences
LWX Release 3.04 does not support PUP routing, Chaos routing, and
Hello inter-router protocols; Cisco stopped supporting these protocols in
Release 9.1.9. LWX also does not support HTTP EZ setup and SLARP
autoconfiguration.
LWX Release 3.04 (PX3 platform) provides some additional functions
not supported by Cisco routers, and does not support some Cisco features.
These differences must be kept in mind when referring to the Cisco IOS Release 11.2 Software Configuration document set. The major
differences include:
•Virtual Card Connect. LWX Release 3.04 allows an operator to
connect to the PX3 card through the Promina network using virtual
card connection; this is an additional function not supported by Cisco.
•Remote Access and Control. LWX Release 3.04 allows remote
access to the router, and control of system functions, including remote
restart.
•LAN interfaces. LWX Release 3.04 (PX3 platform) supports only
the following interface cards:
Ethernet (LAN)
Token Ring
Certain Cisco routers support multiple LAN interfaces. References in
the Cisco documentation to multiple LAN ports, such as switching
between these ports, do not apply to LWX. This includes, for
example, SRB autonomous switching: all LWX switching is RSRB.
•Serial interfaces. The serial interfaces to the LWX are Promina calls.
The LWX is unaware of physical serial interfaces. Therefore,
functions that need to control modems, such as dial backup, are
generally not available.
•Flash memory. The LWX code is stored on the PX3 card’s flash
memory. Loading procedures for the LWX are documented in
Upgrading the LWX Application on page 4-1. For additional
information regarding flash memory, see the PX Platform Guide.
•Other interfaces. The LWX (PX platform) has no auxiliary port,
FDDI, HSSI, ISDN, or Ultra interface. All references to these
interfaces in the Cisco documentation are not applicable to LWX. For
example, SLIP connections require the auxiliary port in Cisco routers
and so are not available on the LWX.
Platform
Configuration
Differences
Because of the hardware differences, procedures for configuring LWX
differ from configuring Cisco IOS:
•Loopback Tests. A loopback test detects and distinguishes
equipment malfunctions between the line and the modem or
CSU/DSU problems. This function is not supported by LWX,
because it is unaware of the physical serial interface. Physical
interfaces are controlled by the Promina OI. Loopback tests are
supported on data cards.
•SRB Autonomous Switching. Autonomous switching in
source-route bridging refers to local SRB between Token Ring
interfaces in the same router. The LWX does not support multi-LAN
port interfaces.
•TFTP Server. The LWX network server can be configured as a
limited TFTP server from which other PX3 cards running LWX can
boot their software. As a TFTP server host, the LWX network server
responds to TFTP request messages. This procedure is documented in
Configuring the Application as a TFTP Server on page 2-5.
•Fast switching. Cisco documentation refers to fast switching over the
CSC-C2CTR interface. This interface is not supported on the PX3
platform. For similar reasons, fast switching for the following
protocols is not supported:
–SRB fast switching over Token Ring
–RSRB (SRB over a tunnel) fast switching over Token Ring
–SMDS fast switching for IP on selected interfaces (HSSI)
•Dial Backup Service. The dial backup service provides protection
against WAN downtime by using a backup serial line that is
configured through a circuit-switched connection. In the LWX
environment, the Promina is responsible for re-routing calls due to
circuit interruption. All dial functions are therefore not supported,
including DDR (Dial on Demand Routing), DDR Hunt Group, and
CHAP for DDR.
•SLIP. A method of sending Internet packets over standard RS-232
asynchronous serial lines, SLIP is only supported on the Cisco
auxiliary interface, which does not exist on the PX3 platform.
•Half-Duplex Mode (STUN). The LWX is not aware of the physical
RS-232 interface, so it does not support half-duplex mode, (a 2-wire
mode in which RTS/CTS signals are toggled).
Before starting to configure LWX, there are several preliminary steps that
must be completed. These include:
•Installing the PX3 cards into a Promina network.
•Installing ports for the PX3 cards into the Promina network database.
•Deciding on the design of your router network.
Consult the PX Platform Guide for information on installing PX3 cards;
and refer to the Promina Series Documentation Set for information on
configuring the Promina network.
Setting the Clock
The LWX application uses the clock from the local Promina node.
If the system is synchronized by a valid outside timing mechanism, such
as an NTP or VINES clock source, or if you have a Cisco 7000 with
calendar capability, you do not need to set the system clock.
2 - 2 LAN/WAN Exchange Release 3.04 Installation and Configuration
Page 31
Installing and Configuring LWXConfiguring Features Using the Setup Command
By using the setup command facility, you specify which protocols and
interfaces are installed. The facility steps you through the configuration
of each interface until all have been configured. For more information on
configuring interfaces, refer to the Cisco document set Cisco IOS Release
11.2 Software Configuration.
If you are configuring a new LWX application (that is, you have ordered
a new PX3 card with the LWX application on it), you must use the Cisco
IOS setup command facility to enter basic configuration information. If
you have upgraded the LWX application on an existing card, the
configuration database used for previous releases of LWX remains on the
card. You may need to update the configuration database to take
advantage of new features.
If the LWX database is not yet configured, the prompt displayed is of the
format LWX _d Xn Yc Z#, where X is the domain number, Y is the node
number, and Z is the card number. If the LWX application is already
configured, the prompt will display the hostname set during
configuration.
If the LWX database is not yet configured, the application does not
launch the configuration dialog. It displays a default configuration in
which all interfaces are in a shutdown state, with no IP addresses
assigned. To configure the LWX application, start the configuration
dialog by typing the following commands:
LWX_d0n1c2> enable
LWX_d0n1c2# setup
Before you begin to use the setup command facility, be sure that you
know what:
•Interfaces the card has
•Protocols the card is routing
•Whether the card is to perform bridging
•Network addresses for the protocols being configured
•Password strategy for your environment
You must run through the entire configuration dialog even if you only
want to change a few items. To accept default settings for items that you
do not want to change, press Return.
The configuration dialog begins with text as shown in Example 2-1.
Continue answering questions until all interfaces have been configured
and you have saved the configuration.
Example 2-1Setup Command Facility Example
LWX_d0n1c1#setup
--- System Configuration Dialog ---
At any point you may enter a question mark ’?’ for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets ’[]’.
Continue with configuration dialog? [yes/no]: yes
First, would you like to see the current interface summary? [yes]:
Note: If a complete configuration of the LWX is not possible using the Cisco
IOS setup command facility, request at least one protocol from the global
parameters. At the end of the setup sequence, answer Yes to the question “Use
this configuration?” Not accepting the configuration can corrupt the configuration
database. The configuration can be changed later through the setup command
or the configure command.
When the setup routine is complete, restart the LWX using the reload
command.
2 - 4 LAN/WAN Exchange Release 3.04 Installation and Configuration
Page 33
Installing and Configuring LWXConfiguring the Application as a TFTP Server
LWX Release 3.04 allows you to configure the LWX as a Trivial File
Transfer Protocol (TFTP) server.
Example 2-2 provides an example of the command syntax necessary to
begin and complete a typical configuration. Enter configuration
commands, one per line. Press Control- Z to implement and exit the
configuration process. Note that only one configuration command
(conf t) is entered in this example.
For specific information on the TFTP configuration process, refer to the
accompanying Cisco document set Router Products Configuration and
Reference.
Example 2-2Establishing a TFTP Server Configuration
n1c24# conf t
n1c24(config)# tftp-server flash lwxg54.03
n1c24(config)# end
n1c24# wr
A working copy of the LWX configuration is loaded into DRAM, while
the application is stored in non-volatile memory (NVRAM) or kept as a
file on a remote host. The show config command displays the NVRAM
version of the configuration, while the show running (previously write term) command displays the working configuration. (All commands
used in this section are Cisco IOS commands.)
Note: Several Cisco IOS commands, including show running, copy
running-config, and copy startup-config tftp, have multiple forms. LWX
supports both the old and new forms; the new form is used in this document.
Storing the
Configuration in
NVRAM
Storing the
Configuration on a
Remote Host
Example 2-3Writing the Configuration File to a Host
LWX_d0n157c41# copy startup-config tftp
Remote host [134.56.186.115]?
Name of configuration file to write [n4c5-config]?
Write file n4c5-config on host 134.56.186.115? [confirm] y
Writing n4c5-config ...
[OK]
Use the enabled command copy running-config to store the
configuration in NVRAM.
1. Use the enabled command copy startup-config tftp to store the
configuration as a file on a remote host. The operating system
requests the destination host’s address and a file name, as shown in
Example 2-3.
2. To load the configuration from the network, use the enabled
command configure and then enter network as shown in Example
2-4.
Example 2-4Loading the Configuration from the Network
Configuring from terminal, memory, or network [terminal]? network
2 - 6 LAN/WAN Exchange Release 3.04 Installation and Configuration
Page 35
Installing and Configuring LWXBacking Up the LWX Configuration
3. Next, the operating system asks whether to use a host or network
configuration file, and prompts you for the address of the host and a
configuration filename as shown in Example 2-5.
Example 2-5Entering the Host/Network Configuration File Information
Host or network configuration file [host]?
IP address of remote host [255.255.255.255]? 134.56.186.115
Name of configuration file [n4c5-config]?
Configure using n4c5-config from 134.56.186.115? [confirm]yes
Booting n4c5-config from 134.56.186.115: !! [OK - 874/160000 bytes]
Backup and
Restore of
Archived
Configuration
Files
Example 2-6NVRAM Unpack Command
LWX_d1961n1c33#nvram unpack pack.dba
LWX_d1961n1c33#nvram_unpack: Unpacking archive file: pack.dba
UnpackArchiveFile: Opening archive file pack.dba
COMPLETE file pack.dba with 2386 bytes
UnpackArchiveFile: Reading arcFH to archive file for 274 bytes
UnpackArchiveFile: Got total files 3
File config.lwx is 1393 bytes
File platform.dbs is 403 bytes
File confreg.lwx is 100 bytes
Unpacking file config.lwx, 1393 bytes
Unpacking file platform.dbs, 403 bytes
Unpacking file confreg.lwx, 100 bytes
To bring this restored configuration on line issue a 'reload'
command!
LWX Release 3.04 and higher provides an NVRAM Unpack CLI
command which allows the user to manually unpack an archived
configuration file which has been downloaded to an LWX node.
When the user issues the command and specifies the filename of the
archived configuration, the archived configuration is unpacked and will
be ready for restoration to active operation upon a restart of the LWX card
as shown in Example 2-6.
This chapter describes how to verify the LWX configuration, physical
connections, and logical connections. This section discusses the
following topics:
The show config command displays the LWX database configuration
that is stored in NVRAM (stored using the copy running-config
command). Using the show running command displays the working
configuration stored in flash memory.
Changes made to the working configuration but not copied to the
NVRAM appear when show running is entered, but not show config. In
Example 3-1, typing show config at the prompt would not display the
lines shown in bold if source bridging were configured but not written to
NVRAM.
Using 999 out of 31456 bytes
!
hostname n157c5
!
!
!
!
!
interface CBus 0
no ip address
!
interface TokenRing 0
ip address 134.56.186.121 255.255.255.248
no keepalive
source-bridge 4 6 200
source-bridge spanning
multiring all
!
interface Serial 0
ip address 134.56.194.106 255.255.255.248
!
.
.
interface Serial 7
ip address 134.56.186.114 255.255.255.248
shutdown
!
!
router rip
network 134.56.0.0
!
ip route 134.56.0.0 255.255.0.0 134.56.186.112
!
!
ip name-server 255.255.255.255
!
!
line cbt 0
login
line vty 0 4
login
line con 0
exec-timeout 0 0
stopbits 1.5
line cbt 0
stopbits 1.5
line vty 0
line vty 1
line vty 2
line vty 3
line vty 4
!
end
This section describes how to verify physical and logical connections
from OSI layer one to layer three.
Verifying Token
Ring Connections
Example 3-2Verifying Token Ring Connections
LWX_d0n157c41#show interface t 0
TokenRing 0 is up, line protocol is up
Hardware is Token Ring 16M, address is 0080.b210.017f (bia 0080.b210.017f)
Internet address is 134.56.186.124, subnet mask is 255.255.255.248
MTU 4472 bytes, BW 16000 Kbit, DLY 630 usec, rely 255/255, load 1/255
Encapsulation SNAP, loopback not set, keepalive not set
ARP type: SNAP, ARP Timeout 4:00:00
Ring speed: 16 Mbps
Multiring node, Source Route Bridge capable
Group Address: 0x00000000, Functional Address: 0x00000100
Last Ring Status 2d21 <Only station> (0x40)
Last input 0:00:01, output 0:00:01, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 1 drops
Five minute input rate 0 bits/sec, 0 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
102987 packets input, 14310193 bytes, 0 no buffer
Received 102954 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1322 packets output, 115191 bytes, 0 underruns
0 output errors, 4 interface resets, 0 restarts
12 transitions
To check the Token Ring connection, type show interface t 0 at the
prompt. In Example 3-2, the lines in bold show the general status and the
packets being input and output.
LWX_d0n157c41#show int e 0
Ethernet 0 is up, line protocol is up
Hardware is Lance, address is 0080.b210.00c2 (bia 0000.0000.0000)
Internet address is 134.56.186.5, subnet mask is 255.255.255.248
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 4:00:00
Last input 0:00:00, output 0:00:25, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 32/75, 0 drops
Five minute input rate 0 bits/sec, 1 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
650672 packets input, 71404625 bytes, 0 no buffer
Received 650435 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
4387 packets output, 400260 bytes, 0 underruns
0 output errors, 115 collisions, 0 interface resets, 0 restarts
To check Ethernet connections, type show int e 0 at the prompt.
In Example 3-3, the lines in bold show the general status and the packets
being input and output. For example:
Verifying
Connections with
Ping
Example 3-4Verifying Connections with Ping
LWX_d0n157c41#ping 134.56.186.121
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 134.56.186.121, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 4/4/4 ms
LWX_d0n157c41#ping 134.56.186.121
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 134.56.186.121, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Ping examines the connections between the LWX and another LWX or
external router up through OSI layer three. It sends an echo-request
packet to the target address. If the target has a matching address, it returns
an echo-response packet. Failures can occur because a route could not be
established within the timeout period, or because an ARP was required
for a MAC address (shown in Example 3-4).
ping <address>
where <address> is an IP address on the LWX or external router. For
example:
To check that routing is working, telnet to a remote LWX or external
router. The telnet protocol allows any customer to log onto remote hosts.
telnet makes the other hosts appear as if they are all using the same
technique to display information. An example command syntax is shown
below.
telnet <address>
where <address> is an IP address on the LWX or external router. A
sample screen session is shown in Example 3-5.
This chapter describes methods for upgrading the LWX application. The
application is upgraded by transferring the image to the flash memory and
selecting it as the boot image. Upgrading the Bootstrap program is also
covered.
This chapter contains the following sections:
•Preparing the Card for a New Application Image on page 4-2
•Downloading an Image from a PCMCIA Card on page 4-4
•Upgrading Cards on a Network Using TFTP on page 4-6
•Upgrading the Application Using the PX3 Bootstrap Program on
Before transferring the LWX application image to the flash memory of
the PX3 card, you must determine the size of the image and prepare the
flash by allocating sufficient RAM for the image.
Use the flash dir command to determine the amount of RAM required.
This command displays the size of the image in bytes, which can be
converted to megabytes by dividing by 1,000,000.
For example, an image that is 4063372 bytes is 4.06 megabytes (MB).
The amount of RAM required is the next highest integer, 5 MB.
To prepare the PX3 card for a new application image
1. Allocate sufficient RAM for the image by running ramloadmode.
Example 4-1Allocating RAM Using ramloadmode
LWX_d0n157c41#ramloadmode 5
Reload for the new ram load mode to take effect.
LWX_d0n157c41#reload
Proceed with reload? [confirm]
%SYS-5-RELOAD: Reload requested
Reloading .....
Caution: Be sure to allocate sufficient RAM for the new image. If you do not
allocate enough RAM, the downloading process will leave your card in the PX3
booter.
2. Check the flash directory to determine if there is sufficient room for
the image, by entering flash dir.
4. Run the show version command to verify that the application is in
read-write mode.
Example 4-4Running the show version command
LWX_d0n157c41#show version
LWX Software (PX3) Version g3.03.01(54.03), RELEASE SOFTWARE
Copyright 1997 by Network Equipment Technologies, Inc. Fremont, CA 94555
All Rights Reserved
Compiled Thu Apr 1 18:37:40 PST 1999 by lwxrel
After preparing the card, you can upgrade the application image.
PX3 cards on a network can be upgraded by downloading the LWX
application image from a PCMCIA card to the flash memory of a PX3
card on the network, then transferring the new image to other cards on the
network using TFTP.
PCMCIA cards are not supported in LWX releases prior to 3.02.03. You
must upgrade from earlier LWX releases by using the PX3 boot menus
(see Upgrading the Application Using the PX3 Bootstrap Program on
page 4-8).
To download a new application image from a PCMCIA card
1. To download the image, you must be running in ramloadmode.
2. Mount the PCMCIA card by entering pcmcia mount.
Example 4-5Mounting a PCMCIA Card
LWX_d0n157c41#pcmcia mount
Flash device size = 8388608 at 04000000
/flash/1 installed
3. Check the PCMCIA directory for the image filename by entering
pcmcia dir.
Example 4-6Checking the PCMCIA Directory
LWX_d0n157c41#pcmcia dir
LWXG54 .03 7091984 @ 3
PCMCIA space occupied = 7602176 bytes, free = 786432 bytes
4. Copy the image to the flash by entering the pcmcia copy command.
Example 4-7Copying an Image to Flash Memory
LWX_d0n157c41#pcmcia copy to flash LWXG54.03 lwxb.1
eeeeeee
LWX_d0n157c41#flash dir
LWXG54 .03 7091984 @ 3
LWXB .1 828964 @ 31
If you receive an error message stating that “the image may not be
contiguous”, delete all images on the flash and reload if necessary.
Once you have downloaded the new application image onto a PX3 card,
you can transfer the new image to cards on a network using TFTP. To do
so, you must first configure the new version to a TFTP server.
To upgrade PX3 cards on a network using TFTP
1. Configure the new version of the LWX application as a TFTP server.
Example 4-9Configuring LWX as a TFTP Server
LWX_d0n157c41#conf t
Enter configuration commands, one per line. End with CNTL/Z.
LWX_d0n157c41(config)#tftp flash lwxb54.03
LWX_d0n157c41(config)#end
LWX_d0n157c41#
%SYS-5-CONFIG_I: Configured from console by console
LWX_d0n157c41#
LWX_d0n157c41#
LWX_d0n157c41#wr
Building configuration...
[OK]
LWX_d0n157c41#
Once the new application is configured as a TFTP server, prepare each
card to be upgraded (see Preparing the Card for a New Application Image
on page 4-2) and send a request for the application image from each card.
2. Ping the IP address of an active interface on the card acting as the
TFTP server.
Example 4-10Pinging the TFTP Server Card
LWX_d0n159c8#ping 10.1.1.101
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.101, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/2/4 ms
LWX_d0n159c8#flash dir
LWXG54 .03 7091984 @ 3
Flash space occupied = 9175040 bytes, free = 7602176 bytes
Upgrading the Application Using the PX3 Bootstrap Program
If the flash memory is empty, corrupted, or does not contain the LWX
application, you can upgrade the flash memory using the PX3 Bootstrap
program. You can upgrade the application using the boot menus either by
downloading the image from a PCMCIA card or by transferring the
image using FTP.
Upgrading from a
PCMCIA Card
Example 4-12Logging In to the PX3 Bootstrap Program
1 (PWD) PWD Print Working Directory
2 (DIR) Directory of files
3 (CD ) CD Change to Directory
4 (LIS) List a file
5 (DEL) Delete file
6 (COP) Copy a file
7 (REN) Rename a file
8 (MOU) Mount PCMCIA FLASH Device (/FLASH/1)
9 (DOS) DOS Fs Config Info
10 (CAL) Calculate Checksum for a File
11 (REA) Read Checksum Information in a file
* 12 (FIN) Finish - return to top menu
Enter> mou
The PCMCIA card is mounted as a file system (/flash/1).
5. Display the PCMCIA directory by entering pwd.
If you do not see the /flash/1 directory, type cd /flash/1 and press
Return to continue.
6. Copy the new image to flash memory by entering
copy<filename>.bin /flash/0/<filename>.bin, where <filename> is
the name of the image you are copying.
Make sure that the name you enter matches the image name exactly.
7. Return to the main menu by entering fin.
8. Make the copied image the boot image by entering mod to display the
Modify configuration menu, then entering set. You are prompted to
enter the filename of the image.
Example 4-15Setting the Boot Image from Bootstrap
PX3 BOOTSTRAP
Modify ...
1 (ACC) Access List of IP Addresses
2 (SET) Set Boot Image
3 (PAS) Password Set for Booter Login
4 (USE) User ID Set for Booter Login
* 5 (FIN) Finish
Enter> set
9. Return to the main menu; exit and restart the card by entering exi.
This resets and reloads the PX3 card with the new application.
New versions of the PX3 Bootstrap program, containing new features or
enhancements are released periodically. Bootstrap program upgrades
should normally be performed by qualified support personnel.
To upgrade the PX3 bootstrap program
1. Load the new bootstrap image into flash memory using the flash load
command.
2. Replace the older image with the new image loaded into flash
memory using the replacepx3bootstrapper command. The filename
specified in the command should already exist in /flash/0.
Caution: Do not enter an incorrect image name. Doing so could damage the
card and require factory service.
An example syntax is shown in Example 4-16:
replacepx3bootstrapper <filename>, where <filename> is the name of
the image being replaced.
Example 4-16Replacing the PX3 Bootstrapper Program
This chapter provides checklists for troubleshooting problems that can
occur during installation. These checklists are not intended to be in-depth
troubleshooting procedures.
The following problems are discussed in this section:
•If you cannot install a PX3 card on page 5-2
•If the PX3 card does not load the LWX code on page 5-2
•If you cannot connect to a PX3 card on page 5-2
You need to have the following information ready before contacting your
support organization for assistance:
•Promina software version
•LWX software version
•PX3 card hardware revision level
•Boot code revision level
•Location (node and card) of the problem
•Complete description of the problem and symptoms
•Modem number for remote login to the Promina node
Note: The first time you connect using the card connect and/or connect to PX
card feature you do not need a password. You can subsequently change the
configuration to set a password for the following types of connections: card
connections, console connections, and telnet connections.
The following checklists are not sequential; if one of the listed items
solves the problem, there is no need to follow the other items for that
problem.
If you cannot install a PX3 card
•Wait 30 seconds for hardware initialization to complete and retry
•Verify that the Promina software is at Release 1.x2 or later
•Verify that the power LED is steadily on
•Verify that the heartbeat LED is flashing once per second
•Reseat the PX3 card in the slot, wait 30 seconds, and reinstall the card
•Contact your support organization
If the PX3 card does not load the LWX code
•Check the Promina event log for PX3-related events
•Log in to the booter (see Upgrading the Application Using the PX3
Bootstrap Program on page 4-8)
•Verify that the boot image is correct
•Contact your support organization
If you cannot connect to a PX3 card
•Query the card (using the Promina Operator Interface) to verify it is
“active” and “up”, and running the correct version of LWX
•Verify connectivity to the node
Refer to the PX Platform Guide for more information on installing the
PX3 card, and to the Promina Series documentation set for information
on the Promina Operator Interface.
This section describes the events generated by the LWX application (type
90 events). The PX platform cards also generate type 27 events for events
that occur at the card level; see the Alarms and Events Manual in the
Promina Series document set for details on type 27 events.
Caution: Remove the front card before reseating the rear interface card to
prevent damage to the card.
90.1
Event Message<card ID> Ethernet back card failure
Alarm MessageENET I/F FAILURE
Default LevelMajor – this alarm requires urgent action.
1Chapter 6
DescriptionThe Ethernet interface card has experienced a failure. This may be caused
by a true hardware failure of the Ethernet card, or the Ethernet card has
become un-seated in its slot on the Promina shelf.
ActionRe-seat the front card (PX) and the Ethernet interface card and reboot the
code. If the condition persists, replace the Ethernet card and contact your
support organization.
Installation and Configuration Guide LAN/WAN Exchange Release 3.046 - 1
DescriptionThis event occurs whenever the PX card activates or deactivates one of
the eight internal HDLC ports attached to the card.
ActionNone
90.6
Event Message<Port ID> HDLC port de-activated
Alarm MessageNo alarm
Default LevelNone
DescriptionThis event occurs whenever the PX card activates or deactivates one of
the eight internal HDLC ports attached to the card.
ActionNone
90.7
Event Message<card ID> Network download failed
Alarm MessageDWNLD FAILURE
Default LevelMajor – this alarm requires urgent action.
DescriptionThis event occurs when the attempt to download the LWX code over the
network using TFTP has failed.
ActionTry another path to the card acting as the TFTP server. Make sure there is
a link up to the card. Contact your support organization for assistance.
90.8
Event Message<card ID> Loaded image does not match function
Alarm MessageIMAGE/FUNC MISMATCH
Default LevelMajor – this alarm requires urgent action.
DescriptionThe PX card can be configured for FRX and LWX code. This message
means that the card is configured for LWX, and the code that was loaded
onto the card is not LWX code (for example, FRX code loaded onto an
LWX-configured card.)
ActionMake sure that the correct code is loading. Contact your support
Default LevelCritical – requires immediate action to solve a network-affecting
problem.
DescriptionThe LWX card has restarted; this can occur for one of several reasons: the
card was removed from the slot and re-inserted, the Reset switch on the
front of the card was triggered, or the card had an internal failure causing
the restart.
ActionIf the operator restarted the card, then no action is necessary. If the card
restarts by itself frequently, contact your support organization.
90.10
Event MessageError in <operation> DLM <DLM <DLM name>: <reason>
Alarm MessageLWX ERRMS G
Default LevelMajor – this alarm requires urgent action.
DescriptionThe LWX had an error pertaining to a DLM (Dynamically Loadable
Module). The <operation> could be Loading, Unloading or Initializing,
depending on when the error occurred during the load process.
This message applies to the PX2 card only. It is not applicable to
LWX Release 3.01 and later.
ActionDifferent action is called for, depending on the reason displayed in the
<reason> field.
•For all errors, make sure that there is a valid path to the source of the
DLMs.
•If the error is Card options not enabled for this DLM, it means that the
option is not available on this LWX. Some options are not included in
the base LWX, including x.25 and Bridging. Contact your sales
representative to arrange for these options to be installed.
•If the <reason> is (internal error), this is a serious problem - call TAC.
This chapter provides an overview of the Simple Network Management
Protocol (SNMP) agents that are supported in the LWX application. This
chapter contains the following sections:
•Agent Description on page 7-2.
•Recommended Additional Documentation on page 7-4.
Note: This document assumes that the user is familiar with standard SNMP
concepts and it is intended to provide only LWX-specific details, rather than a
general explanation of SNMP principles. For a list of additional resources on
SNMP, see Recommended Additional Documentation on page 7-4.
Installation and Configuration Guide LAN/WAN Exchange Release 3.047 - 1
The SNMP agents allow the LWX application to be managed by an
SNMP manager, such as the netMS or PanaVue management system. The
LWX SNMP agents, together with netMS or PanaVue, provide a
powerful system for managing, configuring, and instrumenting the LWX
application across the multiple domains of a SuperWAN.
Two versions of SNMP are supported, SNMP version 1 (SNMPv1) and
SNMP version 3 (SNMPv3). Authorized managers now have a field to
specify the SNMP trap version (v1 or v3). The SNMPv1 authorized
managers utilize the already established community string method of
authentication. The SNMPv3 authorized managers may not specify a
USM user, which is used for more stringent authentication and security
for SNMP transactions.
For more information, see:
•SNMPv1, as described in SNMPv1 Overview on page 7-2.
•SNMPv3, as described in SNMPv3 Overview on page 7-3.
SNMPv1 Overview
The supported SNMPv1 capabilities include:
•get and getNext – An authorized SNMP manager can request
configuration or performance information by sending get request and
get next request messages to the agent. The agent returns the
requested information in a get response message.
•set – An authorized SNMP manager can alter configuration
information at an agent by sending set request messages to the agent.
The agent returns a get response message.
•getBulk– An authorized SNMP manager can query a network entity
efficiently for a tree of information by sending a get bulk request. If
the network entity encounters an error while processing the request,
an error packet will be returned and a message will be displayed,
helping the user to pinpoint why the request was malformed.
•traps – Each agent is configured to send event messages, known as
traps, to one or more authorized managers. The traps alert the
manager of changes at the agent or node, so that the manager can
decide what kind of corrective action, if any, is necessary.
Figure 7-1 illustrates the direction of messages sent between a manager
and agent.
SNMPv3 uses a User-based Security Model (USM) for advanced
authentication of users. Rather than having a community string assigned
to an incoming IP address, there are configured users. Each of these users
has an authentication key and a privacy key. The authentication key is a
MD5 or SHA encoded key, which provides encrypted communication
from the manager to the agent and vice versa. This replaces the SNMPv1
community string. In addition to this, there is a privacy key to encrypt the
PDU in the SNMP message using DES encryption providing another
layer of security.
As well as the above keys, each SNMP manager or agent has an assigned
engine ID that identifies that particular SNMP device. This is used in the
generation of the encrypted key so that the two communicating parties
can confirm they are talking to the right device. The engine ID in the
Promina is automatically assigned a value.
Traps within SNMPv3 follow the same mechanism as they do in
SNMPv1. However, they also use the new authentication and privacy
keys rather than the community string. Therefore when configuring an
authorized manager, a selection must be made as to whether to send
version 1 or version 3 traps.
This section lists recommended resources of additional information about
SNMP and TCP/IP.
BooksThere are many good books on the basics of SNMP and TCP/IP. Here are
just a few:
•Managing Internetworks with SNMP by Mark A. Miller, M&T Books
1993 (ISBN 1-55851-304-3) – A good blend of theory and practice,
very readable.
•SNMP, A Guide To Network Management by Dr. Sidnie Feit,
McGraw-Hill, Inc. 1995 (ISBN 0-07-020359-8) – An overview of
SNMPv1 and SNMPv2 principles.
•SNMP, SNMPv2, and RMON by William Stallings, Addison Wesley
Longman, Inc. Reading, MA 1996 (ISBN 0-201-63479-1) – A
practical introduction to SNMP that covers the major principles.
•TCP/IP Illustrated, Volume 1: The Protocols by W. Richard Stevens,
Addison-Wesley Professional Computing Series 1994 (ISBN
0-201-63346-9) – A solid conceptual introduction to SNMP, MIBs,
and related concepts.
Internet
Resources
•Understanding SNMP MIBs by David Perkins and Evan McGinnis,
Prentice-Hall New Jersey 1996 (ISBN 0-13-437708-7) – An
explanation of the MIB structure and ASN.1 format. It provides a
complete guide for using MIBs to manage network devices.
The internet contains hundreds of sites that contain documentation on
SNMP, and the following are good starting places to discover them:
•http://www.snmp.com – Contains basic information about SNMP,
along with links to other resources.
•http://www.snmpinfo.com - Contains basic information about SNMP
and miscellaneous tools.
•http://www.simple-times.org/pub/simple-times/issues – A newsletter
devoted to the promotion of SNMP.
Note: The internet “http” URL addresses given in this section were current as of
this manual’s publication date. However, given the rapidly changing nature of
the internet, these addresses can change at any time.
Installing and configuring an SNMP agent, either SNMPv1 or SNMPv3,
involves:
•Configuring the SNMP engineID
•Creating SNMP views to allow the user to access MIBs
•Creating SNMP groups to specify which view(s) that the user can use
as well as setting the level of authentication/privacy for the user
•Creating the SNMP users
After you have created the SNMP views and groups, and configured the
users, you can proceed with configuring the LWX application for SNMP
trap support. See Trap Support on page 9-1.
Operator InterfaceThe SNMP agents are configured on the LWX module using Cisco IOS
commands issued from the console interface provided when logging into
the card. This can be accomplished by connecting from another processor
on the Promina node or through the LWX card’s front serial console port.
The configuration parameters for an SNMP agent are installed for the
first time using the following commands:
Note: Ensure that you are in configuration mode prior to running the
following commands.
•snmp-server engineID: used to configure names for the local router
•snmp-server view: used to create and configure a new SNMP view
•snmp-server group: used to create and configure a new SNMP
group, or a table that maps SNMP users to SNMP views
•snmp-server user: used to configure a new user to an SNMP group
•snmp-server host: used to configure the recipient of an SNMP trap
operation.
Note: Ensure that you are out of configuration mode prior to running the
following commands.
•show snmp engineID: used to display information about the local
SNMP engineID
•show snmp group: used to display information about each SNMP
group configured on the device
•show snmp user: used to display information about each SNMP
username in the SNMP user’s table
You can configure an SNMP engineID for the local SNMP engine on the
router.
The following steps assume that a telnet session has been previously
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To configure an SNMP engineID
1. Ensure that you are in configuration mode. If not, enter configuration mode using conf t.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
3. Configure an SNMP EngineID by using snmp-server engineID. The
following example will configure an SNMP engineID of the local
agent called engineID_1.
Example 8-1Configuring an SNMP EngineID (local agent)
Router(config)# snmp-server engineID local engineID_1
The following steps assume that a telnet session has been previously
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To create an SNMP view
1. Enter configuration mode at the router prompt using conf t.
Example 8-2Entering configuration mode
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
Example 8-3Obtaining help with SNMP parameters
Router(config)# snmp-server view ?
WORD Name of the view
Router(config)# snmp-server view SNMP_user1 ?
WORD MIB view family name
Router(config)# snmp-server view SNMP_user1 1.3 ?
excluded MIB family is excluded from the view
included MIB family is included in the view
3. Create an SNMP view using snmp view. The following example will
create an SNMP view called SNMP_user1 and allow all access to the
associated MIB files.
Example 8-4Creating an SNMP view
Router(config)# snmp-server view SNMP_user1 1.3 included
The following steps assume that a telnet session has been previously
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To create an SNMP group
1. Ensure that you are in configuration mode. If not, enter configuration mode using conf t.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
Example 8-5Obtaining help with SNMP parameters
Router(config)# snmp-server group ?
WORD Name of the group
Router(config)# snmp-server group SNMP_group1 ?
v1 user using the v1 security model
v2c user using the v2c security model
v3 user using the v3 security model
Router(config)# snmp-server group SNMP_group1 v3 ?
auth group using the authNoPriv Security Level
noauth group using the noAuthNoPriv Security Level
priv group using SNMPv3 authPriv security level
Router(config)# snmp-server group SNMP_group1 v3 noauth ?
notify specify a notify view for the group
read specify a read view for the group
write specify a write view for the group
Router(config)# snmp-server group SNMP_group1 v3 noauth read ?
WORD read view name
Router(config)# snmp-server group SNMP_group1 v3 noauth read
SNMP_view1 ?
notify specify a notify view for the group
write specify a write view for the group
Router(config)#snmp-server group SNMP_group1 v3 noauth read
SNMP_view1
3. Create an SNMP group using snmp-server group. The following
example will create an SNMP view called SNMP_group1 with no
authentication, no privacy, but with read access to a view called
SNMP_view1.
Example 8-6Creating an SNMP group (no authentication)
Router(config)# snmp-server group SNMP_group1 v3 noauth read
SNMP_view1
4. The following example will create an SNMP view called
SNMP_group1 with authentication, no privacy, but with read access
to a view called SNMP_view1.
Example 8-7Creating an SNMP group (authentication, no privacy)
Router(config)# snmp-server group SNMP_group1 v3 auth read
SNMP_view1
5. The following example will create an SNMP view called
SNMP_group1 with authentication and privacy, but with read access
to a view called SNMP_view1.
Example 8-8Creating an SNMP group (authentication and privacy)
Router(config)# snmp-server group SNMP_group1 v3 priv read
SNMP_view1
The following steps assume that a telnet session has previously been
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To create an SNMP user
1. Ensure that you are in configuration mode. If not, enter configuration mode using conf t.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
Example 8-9Obtaining help with SNMP parameters
Router(config)# snmp-server user ?
WORD Name of the user
Router(config)#snmp-server user SNMP_user1 SNMP_group1 ?
remote Specify a remote SNMP entity to which the user belongs
v1 user using the v1 security model
v2c user using the v2c security model
v3 user using the v3 security model
Router(config)#snmp-server user SNMP_user1 SNMP_group1 V3 ?
auth authentication parameters for the user
encrypted specifying passwords as MD5 or SHA digests
<cr>
Router(config)#snmp-server user SNMP_user1 SNMP_group1 V3 ?
<cr>
Router(config)#snmp-server user SNMP_user1 SNMP_group1 V3
Adding an snmpv3 user could cause a bootup delay,
do you wish to continue? (y/n)[confirm]y
Router(config)#
3. Create an SNMP user using snmp-server user. The following
example will create an SNMP user called SNMP_user1.
Example 8-10Creating an SNMP user
Router(config)# snmp-server user SNMP_user1 SNMP_group1 V3
Adding an snmpv3 user could cause a bootup delay,
do you wish to continue? (y/n)[confirm]y
Router(config)#
4. The following example will create an SNMP user called
SNMP_user1 with authentication, default password set to password1.
Example 8-11Creating an SNMP user (authentication, no privacy)
Router(config)# snmp-server user SNMP_user1 SNMP_group1 V3 auth md5
password1
Adding an snmpv3 user could cause a bootup delay,
do you wish to continue? (y/n)[confirm]y
Router(config)#
5. The following example will create an SNMP user called
SNMP_user1 with authentication, default password set to password1,
privacy using DES56, and default privacy password set to password2.
Example 8-12Creating an SNMP user (authentication and privacy)
Router(config)# snmp-server user SNMP_user1 SNMP_group1 v3
encrypted auth md5 password1 priv des56 password2
Adding an snmpv3 user could cause a bootup delay,
do you wish to continue? (y/n)[confirm]y
Router(config)#
You can configure an SNMP host to be the recipient of an SNMP trap
operation.
The following steps assume that a telnet session has been previously
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To configure an SNMP host
1. Ensure that you are in configuration mode. If not, enter configuration mode using conf t.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
3. Configure an SNMP host by using snmp-server host. The following
example will configure an SNMP host at IP address 134.56.216.23 to
allow for the gathering of the following SNMP trap information:
config, frame-relay, and syslog.
You can display information regarding the SNMP engineID for the local
SNMP engine on the router.
The following steps assume that a telnet session has been previously
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To show an SNMP engineID
1. Ensure that you are not in configuration mode.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
3. Show an SNMP engineID by using show snmp engineID.
Example 8-14Showing an SNMP engineID
Router#show snmp engineID
Local SNMP engineID: 800000B1FF0000A10016B1BF
You can display information on each SNMP group on the network.
The following steps assume that a telnet session has been previously
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To show an SNMP group
1. Ensure that you are not in configuration mode.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
3. Show an SNMP group by using show snmp group.
Example 8-15Showing an SNMP group
Router#show snmp group
groupname: A_P security model:v3 priv
readview :ReadAll writeview: WriteAll
notifyview: <no notifyview specified>
row status: active
You can display information on each SNMP username in the SNMP
user’s table.
The following steps assume that a telnet session has been previously
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To show an SNMP host
1. Ensure that you are not in configuration mode.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
Traps are asynchronous messages that notify SNMP managers of
significant events that have occurred at the agent or node. Traps are sent
unsolicited to the SNMP managers that are configured to receive them.
SNMP traps that can be specified by the user are:
•authentication-failure
•linkup
•linkdown
•coldstart
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
You can configure an SNMP host to be the recipient of an SNMP trap
operation.
The following steps assume that a telnet session has been previously
established with the LWX application. See “Verifying Connections with
Telnet” on page 6.
To configure an SNMP host
1. Ensure that you are in configuration mode. If not, enter configuration mode using conf t.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
3. Configure an SNMP host by using snmp-server host. The following
example will configure an SNMP host at IP address 134.56.216.23 to
allow for the gathering of the following SNMP trap information:
config, frame-relay, and syslog.
Note: Ensure that you have configured the SNMP host. See Configuring
an SNMP Host
You can configure an SNMP host to be the recipient of an SNMP trap
operation.
The following steps assume that a telnet session has been previously
established with the LWX application. See Verifying Connections with Tel ne t on page 3-6.
To configure SNMP traps
1. Ensure that you are in configuration mode. If not, enter configuration mode using conf t.
2. To obtain help with SNMP parameters, you can enter a ? after the
parameter. Help information regarding the parameter is listed below
the command line prompt. A new command line prompt is displayed
allowing you to enter additional parameters.
on page 9-3.
Note: For detailed information about Cisco IOS Release 12.1 commands,
see the Cisco IOS Software Configuration document set.
3. Configure SNMP traps by using snmp-server enable traps snmp.
The following example will configure the system for SNMP trap
support.
This appendix describes the commands specific to the LWX application.
The Cisco IOS commands are documented in the Cisco IOS 11.2 Software Configuration document set.
Installation and Configuration Guide LAN/WAN Exchange Release 3.04 A - 1
NVRAM commands allow you to display the contents of the NVRAM
directory, rename a file, or even delete files. Table A-1 describes the
available commands. NVRAM commands are hidden; that is, they do not
appear in the Help facility.
Table A-1Working with NVRAM Commands
Command Function
nvram dirDisplays the NVRAM directory
nvram rename <old name> <new name>Renames a file in NVRAM
nvram delete <filename>Deletes a file in NVRAM
nvram display <filename>Displays a file in NVRAM (for example,
nvram display platform.dbs) This
command is intended for text files only.
Caution: NVRAM files contain system and configuration files, and diagnostic
data. Extreme caution should be used when making changes to these files.
Working with Flash Memory Files
Flash memory commands allow you to display the contents of the flash
memory, rename files, delete files, and specify which file to load into
flash memory from a TFTP server. Table A-2 describes the available
commands.
You must be running in ramloadmode (see Allocating Flash Memory on
page A-3) in order to write to or delete flash memory files.
Table A-2Working with Flash Memory Commands
Command Function
flash dirDisplays the directory of files in flash memory
flash rename <old filename> <new filename>Renames a file in flash memory
flash delete <filename>Deletes a file in flash memory and erases the
flash load Loads a file from a TFTP server into the flash
space occupied by the file flash load
memory. You are prompted for both the
filename and the IP address of the TFTP server
A - 2 LAN/WAN Exchange Release 3.04Installation and Configuration
Starting with Release 3.02.03, you can copy files into flash memory from
a PCMCIA card, or copy files from flash onto a PCMCIA card. Table A-3
describes the available commands.
See Downloading an Image from a PCMCIA Card on page 4-4 for a
description of upgrading the LWX application from a PCMCIA card.
Table A-3Working with PCMCIA Cards
CommandFunction
pcmcia copy from flash <fname> <pname>Copies a file <fname> from flash memory to the
PCMCIA card, and gives it a name, <pname>
pcmcia copy to flash <pname> <fname>Copies a file <pname> from the PCMCIA card
to flash, and gives it a name, <fname>
pcmcia delete <name>Deletes a file, <name>, residing on the
PCMCIA card
pcmcia dirLists the files on the PCMCIA card
pcmcia mountMounts the PCMCIA card’s filesystem
pcmcia rename <oldname> <newname>Renames a file on the PCMCIA card
pcmcia unmountUnmounts the PCMCIA card’s filesystem
Allocating Flash Memory
To load an application image into RAM memory, you must first allocate
enough memory to hold the image. Table A-4 describes these commands.
The application defaults to ramloadmode 0, running the working
application from flash memory.
Table A-4Allocating Flash Memory Commands
ramloadmode 0Sets the allocation to 0 MB. The application runs
ramloadmode <size>Sets the allocation to <size>, where <size> is the
Command Function
from flash memory, preventing the contents of the
flash from being modified or deleted.
number of megabytes of flash memory needed to
store the image. If the size of the image is not an
integer (for example, 5.2), increase <size> to the
next highest integer (6).
A copy of the application runs from RAM memory,
allowing the flash memory to be modified.
Installation and Configuration Guide LAN/WAN Exchange Release 3.04 A - 3
This command determines which image boots during the next reload.
Table A-5 provides a syntax example. See Upgrading the PX3 Bootstrap Program on page 4-12 for additional information.
Table A-5Setting the Boot Image
Command Function
setbootimage <filename>Specifies which LWX application image
should be used to boot the card during the
next reload
Showing the Active Version
This command displays information about the software and the PX3 card
the application is running on. Table A-6 describes this command.
Table A-6Displaying the Active Version
Command Function
show versionDisplays information about the software
versions of the LWX application and the
booter, available memory, and the PX3
card
A - 4 LAN/WAN Exchange Release 3.04Installation and Configuration
This appendix describes the configuration process necessary to establish
and support Secure Shell (SSH) connections to and from a LAN/WAN
Exchange (LWX) module.
This appendix contains the following sections:
•SSH Overview on page B-2.
•SSH Configuration on page B-3.
•Restricting Transport Protocol Access on page B-9.
Installation and Configuration Guide LAN/WAN Exchange Release 3.04 B - 1
SSH is a feature than enables the user to log into an LWX Module over a
network, to execute commands on a remote node, and to transfer files
from one node to another. SSH provides security (through encryption),
integrity, strong authentication, and secure communications over insecure
channels.
LWX Release 3.04 supports SSH Version 1 only. For this release, the
SSH package is imported from Cisco IOS Release 12.3.10. This
implementation utilizes DES encryption (56-bit) with password-based
authentication (no public key authentication support).
SSH provides for a secure alternative to the existing (non-secure)
standard accesses (rlogin and telnet) and standard file transfer accesses
(FTP) into and out of an LWX Module. The user will have the option of
disabling standard access and standard file transfer access through the
Operator Interface (OI).
B - 2 LAN/WAN Exchange Release 3.04Installation and Configuration
In order for SSH sessions to be supported on an LWX Module, the user
will need to perform an initial configuration of the SSH files on the LWX
Module. The SSH configuration process involves the following:
•Configure Host Name
•Configure Domain Name
•Generate RSA Keys
•Configure Timeout Value for User Authentication
•Enable SSH Transport Support for VTYS
•Verify Login Account and Password
•Verify SSH Server Configuration
•Enable SCP Server
•Restart LWX
Configure Host
Name
Example B-1Configuring Host Name for the LWX
LWX# configure
LWX (config) # hostname myhost
Note: Do not disable standard session and/or standard file transfer access until
you have completed the SSH configuration process and verified that SSH
sessions and secure file transfers are working correctly.
To configure for SSH, perform the following:
1. Configure host name for the LWX (Example B-1):
a. Enable Global configuration mode
b. Login into console using serial port
c. LWX (config) hostname <hostname>
Installation and Configuration Guide LAN/WAN Exchange Release 3.04 B - 3
Example B-2Configuring Domain Name on LWX for SSH Support
p202_lwxc7 (config)# ip domain-name mydomain
Generate RSA
Keys
Example B-3Generating RSA Key Pair
p202_lwxc7 (config)# crypto key generate rsa
2. Configure domain name needed for using SSH on LWX (Example
B-2). This creates a default domain name that the system software
uses to complete unqualified hostnames:
a. LWX (config)# ip domain-name <domain name>
3. Generate RSA key pair (Example B-3):
a. LWX (config)# crypto key generate rsa
b. Select 1024 bits; this process will take approximately five (5)
minutes to complete
Configure Timeout
Value for User
Authentication
Example B-4Configuring the Timeout Value for User Authentication
p202_lwxc7 (config)# ip ssh timeout 300
Enable SSH
Transport Support
for VTYS
Example B-5Enabling SSH Transport Support for the VTYS
p202_lwxc7 # config terminal
p202_lwxc7 (config term)# line vty 0
p202_lwxc7 (config-line)# login local
4. Configure the timeout value for user authentication. If the user fails to
authenticate within the configured time, the connection is aborted
(Example B-4):
a. LWX (config)# ip ssh timeout <seconds>
5. Enable SSH transport support for the virtual terminal (vtys),
(Example B-5):
B - 4 LAN/WAN Exchange Release 3.04Installation and Configuration
p202_lwxc7 # conf term
p202_lwxc7 (config-term)# username net password 0 net
p202_lwxc7 (config-term)# enable password net
p202_lwxc7 (config-term)# exit
p202_lwxc7 (config)# line
p202_lwxc7 (config-line)# vty 0
p202_lwxc7 (config-line)# password net
p202_lwxc7 (config-line)# login local
Verify SSH Server
Configuration
6. Verify login account and password are set (Example B-6):
a. Configure username/password with minimum privileges (0)
Enable SCP ServerEnable the SCP Server (Example B-8):
Example B-8Enabling the SCP Server
p202_lwxc7 # config terminal
p202_lwxc7 (config term)# ip scp server enable
Note: The SCP Server is disabled by default and operates only in server mode
on the LWX. There is no SCP support between cards.
Restart LWX8. After initializing the LWX Module with the SSH files, reboot the
node to restart the ssh daemon for SSH services to take effect. If you
are only changing the client key files, no reboot is required.
UNIX Server Setup
for SSH
The UNIX system used for network management (netMS) uses the
following directory for storage of the SSH keys and configuration files:
/var/NMS/tmp/s100/.ssh
The following files are placed in this directory when the user (nwkdata)
issues the following command: /usr/bin/ssh-keygen -t rsa1:
identity
identity.pub
authorized_keys
1. Verify that the keys are present in the directory listed above.
2. Ensure that the /var/NMS/tmp/s100 and /var/NMS/tmp/s100/.ssh
directories have the permissions set to 755 and are owned by nwkdata
3. Ensure that the identity.pub file has the permissions set to 644 and is
owned by nwkdata.
4. Ensure that the identity file has the permissions set to 600 and is
owned by nwkdata.
5. Ensure that the authorized_keys file has the permissions set to 644
and is owned by nwkdata.
B - 6 LAN/WAN Exchange Release 3.04Installation and Configuration
To initiate an SSH session from a UNIX server, execute the following
command:
ssh -c des -1 user namexx.xx.xx.xx (where user name represents the user
login and xx.xx.xx.xx represents the IP address of the NE).
B - 8 LAN/WAN Exchange Release 3.04Installation and Configuration
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.