All rights reserved. No part of this publication may be reproduced without prior written permission
from Inalp Networks AG.
Inalp Networks AG reserves the right to make changes in specifications and other information
contained in this document without prior notice. The information provided is subject to change
without notice.
In no event shall Inalp Networks AG or its employees and associated companies be liable for any
incidental, special, indirect or consequential damages whatsoever, including but not limited to lost
profits, arising out of or related to this manual or the information contained within it, even if Inalp
Networks AG has been advised of, known, or should have known, the possibility of such damages.
Inalp, the Inalp Logo, and SmartNode are registered trademarks of Inalp Networks AG. SmartWare
and SmartView are trademarks of Inalp Networks AG. All other trademarks mentioned in this
document are property of their respective owners.
EU Declaration of Conformity
The EU Directives covered by this Declaration
89/336/EEC Electromagnetic Compatibility Directive, amended by 92/31/EEC & 93/68/EEC
72/23/EEC Low Voltage Equipment Directive, amended by 93/68/EEC
Note: During the transition period, products may not comply with the Low Voltage Directive.
The Products covered by this Declaration
The products covered by this declaration are the SmartNode 1000 and 2000 family series devices.
The Basis on which Conformity is being Declared
The products identified above comply with the requirements of the above EU directives by meeting
the following standards:
• Safety compliance: EN 60950
• EMC compliance: EN 55022, EN 55024
• ETSI TBR3 (BRI)
• TBR4 (PRI)
The CE mark was first applied in 2000.
Inalp Networks AG
Meriedweg 7
CH-3172 Niederwangen
Software Configuration Guide, Revision 1.03
4 Table of Contents
TABLE OF CONTENTS
1Terms and Definitions ........................................................................................................................... 14
24.3 ISDN Port Configuration Task List.............................................................................................. 233
24.4 Shutdown and Enable ISDN Ports............................................................................................... 233
24.5 Configure Common BRI and PRI Parameters............................................................................ 234
24.6 Configure BRI port parameters .................................................................................................... 235
24.7 Configure PRI Port Parameters .................................................................................................... 236
24.8 Example ........................................................................................................................................... 238
26.10 Show VoIP Profile Configuration and Assign it to a VoIP gateway....................................... 261
26.11 Example ........................................................................................................................................... 263
26.11.1 Home Office in an Enterprise Network .......................................................................... 263
30Appendix A ........................................................................................................................................ 299
31.1 Internetworking Terms and Acronyms ...................................................................................... 315
32Appendix C ........................................................................................................................................ 320
32.1 Used IP Ports in SmartWare 2.0................................................................................................... 320
32.2 Available Voice Codecs in SmartWare 2.00................................................................................ 321
Software Configuration Guide, Revision 1.03
12 About This Guide
ABOUT THIS GUIDE
Objectives
The objective of SmartWare Software Configuration Guide is to provide information concerning the
software configuration and setting into service of SmartNode devices and their interface cards. The
aim is to enable you to install such devices, alone or under supervision.
For detailed descriptions of the commands in the SmartWare Revision 2.00 command set, see the
SmartWare Command ReferenceGuide.
For hardware configuration information refer to the SmartNode Hardware Installation Guide.
Audience
The guide is intended primarily for the following audiences:
• Technical staff who are familiar with electronic circuitry, networking theory and have
experience as an electronic or electromechanical technician.
• System administrators with a basic networking background and experience, but who might
not be familiar with the SmartNode.
• System administrators who are responsible for installing and configuring networking
equipment and who are familiar with the SmartNode.
Document Conventions
Inalp documentation uses the conventions listed in the Table 1-1 through Table 1-3 below to express
instructions and information.
Notice Description
Note
Warning
Caution
Table 1-1: Notice Conventions
Command Description
boldface Commands and keywords are in boldface font.
boldface italic Parts of commands, which are related to elements already named by the
Helpful suggestions or references to materials not contained in this
manual.
Situation that could cause bodily injury, or equipment damage or data
loss
Situation that could put equipment or data at risk
user, are in boldface italic font.
node The leading IP address or nodename of a SmartNode is substituted with
node in boldface italic font.
italicVariables for which you supply values are in italic font
Software Configuration Guide, Revision 1.03
About This Guide 13
Command Description
[ ] Elements in square brackets ([ ]) are optional.
{a | b | c}
Table 1-2: Command Description
Example Description
SN
boldface screen
screen
< > Nonprinting characters are in angle brackets (< >), e.g. <?> which shows
# An hash sign at the beginning of a line indicates a comment line.
Table 1-3: Example Description
Alternative but required keywords are grouped in braces ({ }) and are
separated by vertical bars ( | ).
The leading SN on a command line represents the nodename of the
SmartNode
Information you enter is in boldface screen font.
Terminal sessions and information the system displays are in screen
font.
the available commands in any mode or necessary arguments of a
command.
How to Read this Guide
SmartWare is a complex and multifaceted operating system running on your SmartNode. Without
the necessary theoretical background you will not be able to understand and consequently use all the
features available. Therefore we recommend reading at least the chapters listed below to get a
general idea about SmartWare and the philosophy of contexts used for IP and circuit switching
related configuration.
• Chapter 1, “Terms and Definitions”,
• Chapter 3, “System Overview”,
• Chapter 11, “IP Context Overview” and
• Chapter 20, “CS Context Overview”
We at Inalp Networks AG, hope you find this guide useful, whether you are a novice or professional
working with SmartNode devices and SmartWare responsible for convergent telephony and
networking solutions.
E-mail your comments to the following address:
documentation@inalp.com
Software Configuration Guide, Revision 1.03
14 Terms and Definitions
1 TERMS AND DEFINITIONS
This chapter contains the terms and their definitions that are used throughout the Software
Configuration Guide for SmartWare, Release 2.00.
This chapter includes the following sections:
• Introduction
• SmartWare Architecture Terms and Definitions
1.1 Introduction
The Software Configuration Guide for SmartWare, Release 2.00 contains many terms that are relate to
specific networking technologies areas such as LAN protocols, WAN technologies, routing, Ethernet,
and Frame Relay. Moreover various terms are related to telecommunication areas, such as the
Integrated Services Digital Network (ISDN), Public Switched Telephone Network (PSTN), and Plain
Old Telephone Service (POTS).
Because a glossary for these technologies exists in Appendix B, "Internetworking Terms and
Acronyms", of this document, and because including every term for all related technologies would
prove unrealistic and burdensome, only those terms which are in some way related to the
SmartWare-specific architecture are included here.
1.2 SmartWare Architecture Terms and Definitions
In Table 1-1 terms or definitions used to describe the SmartWare architecture are alphabetically
sorted.
Term or Definiton Meaning
Administrator The person who has priviledged access to the SmartWare
CLI.
Application Download A application image is downloaded from a remote TFTP
server to the persistent memory (flash:) of a SmartNode.
Application Image The binary code of SmartWare stored in the persistent
memory (flash:) of a SmartNode.
Batchfile Script file containing instructions to download one or more
software component from a TFTP server to the persistent
memory (flash: or nvram:) of a SmartNode.
Bootloader The bootloader is a “mini” application performing basic
system checks and starting the SmartWare application. The
bootloader also provides minimal network services allowing
the SmartNode to be accessed and upgraded over the
network even if the SmartWare application should not start.
The bootloader is installed in the factory and is in general
never upgraded.
Bootloader Image The binary code of the Bootloader stored in the persistent
memory (flash:) of a SmartNode.
Software Configuration Guide, Revision 1.03
Terms and Definitions 15
Term or Definiton Meaning
Bootstrap The starting-up of a SmartNode, which involves checking
the Reset button, loading and starting the application image,
and starting other software modules, or—if no valid
application image is available—the bootloader.
Build The released software is organized as builds. Each build has
its unique identification. A build is part of a release and is
responsible to fix software bugs. See also release.
Call Routing Calls through SmartNode can be routed based on a set of
routing criteria. See also Session Router.
Call Signaling The call signaling specifies how to set up a call to the
destination SmartNode or 3
Circuit A communication path between two or more devices.
Circuit Port Physical port connected to a switching system or used for
circuit switching.
Circuit Switching The switching system in which a dedicated physical circuit
path must exist between the sender and the receiver for the
duration of the "call." Used in the conventional telephone
network.
rd
party equipment.
Codec Abbreviation for the word construct Coder and Decoder.
Voice channels occupy 64 kbps using PCM (pulse code
modulation) coding. Over the years, compression techniques
were developed allowing a reduction in the required
bandwidth while preserving voice quality. Such compression
techniques are implemented witin a Codec.
Comfort Noise Comfort noise is generated at the remote end of the silent
direction to avoid the impression that the connection is dead.
See also Silence Compression.
Command Line Interface An interface that allows the user to interact with the
SmartWare operating system by entering commands and
optional arguments. Other operating systems like UNIX or
DOS also provide CLIs.
Configuration Download A configuration file is downloaded from a remote TFTP
server via TFTP to the persistent memory (nvram:) or volatile
memory (system:)of a SmartNode.
Configuration File The configuration file contains SmartWare CLI commands,
which are used to configure the software modules of
SmartWare performing a certain functionality of the
SmartNode.
Configuration Server A central server used as a store for configuration files, which
are downloaded to or uploaded from a SmartNode using
TFTP.
Configuration Upload A configuration file is uploaded from the persistent memory
(nvram:) or volatile memory (system:) of a SmartNode via
TFTP to a TFTP server.
Software Configuration Guide, Revision 1.03
16 Terms and Definitions
Term or Definiton Meaning
Context A SmartWare context represents one specific networking
technology or protocol, e.g. IP or circuit switching.
Data Port Physical port connected to a network element or used for
data transfer.
Dejitter Buffer To compensate variable network delays, SmartWare includes
a dejitter buffer. Storing packets in a dejitter buffer before
they are transferred to the local ISDN equipment, e.g.
telephone, SmartWare converts a variable delay into a fixed
delay, giving voice a better quality. See also Jitter.
Digit Collection SmartWare supports overlap dialling. Some of the connected
devices (PBX, ISDN network, remote gateways and
gatekeepers) may however require bloc sending of the dialed
number. SmartWare collects the overlap dialed digits and
forwards them in a single call setup message
Driver Software Download A driver software image is downloaded from a remote TFTP
server to the persistent memory (flash:) of a SmartNode.
Driver Software Image The software used for peripheral chips on the main board
and optional PMC interface cards is stored in the persistent
memory (flash:) of a SmartNode.
DTMF Relay DTMF relay solves the problem of DTMF distortion by
transporting DTMF tones over low-bit-rate codecs out-ofband or separate from the encoded voice stream
Echo Canceller Some voice devices unfortunately have got an echo on their
wire. Echo cancelation provides near-end echo compensation
for this device.
Factory Configuration The factory configuration (factory-config) represents the
system default settings and is stored in the persistent
memory (nvram:) of a SmartNode.
Fast Connect A “normal” call setup with H.323 requires several TCP
segments to be transmitted, because various parameters are
negotiated. Since a normal call setup is often too slow, fast
connect is a new method of call setup that bypasses some
usual steps in order to make it faster.
Flash Memory Persistent memory section of a SmartNode containing the
Application Image, Bootloader Image and the driver
software Image.
flash: A region in the persistent memory of a SmartNode. See also
flash memory.
Gatekeeper Gatekeepers manage H.323 zones, which are logical
collections of devices such as all H.323 devices within an IP
subnet. For example gatekeepers provide address translation
(routing) for the devices in their zone.
Software Configuration Guide, Revision 1.03
Terms and Definitions 17
Term or Definiton Meaning
Gateway In SmartWare terminology a gateway refers to a special
purpose component that connects two contexts of different
types, for example the CS and the IP context. It handles
connections between different technologies or protocols.
SmartWare includes an H.323 and IsoIP gateway.
equipment and services for multimedia communication over
Local Area Networks (LAN) which do not provide a
guaranteed quality of service. H.323 terminals and
equipment may carry real-time voice, data and video, or any
combination, including videotelephony.
H.323 RAS H.323 registration authentication service (RAS) is a sub
protocol of H.323. The RAS signaling protocol performs
registration, admissions, and bandwidth changes and
disengage procedures between the VoIP gateway and the
gatekeeper.
High-Pass Filter A high-pass filter is normally used to cancel noises at the
voice coder input. See also post filter
Host Computer system on a network. Similar to node, except that
host usually implies a PC or workstation, whereas node
generally applies to any networked system, including access
servers and routers. See also node.
Hostname Name given to a computer system, e.g. a PC or workstation.
Hunt Group In the SmartNode terminology, a hunt groups allows you to
apply the interface configuration to multiple physical ports.
Within the hunt groups free channels for outgoing calls are
hunted on all available ports. In general a hunt group
represents a group of trunk lines as used for direct dialing in
(DDI).
Interface In SmartWare an interface is a logical construct that provides
higher-layer protocol and service information. An Interface
is configured as a part of a context, and is independent of a
physical port or circuit.
Interface Card An optional plug-in card offering one or more ports of a
specific physical standard for connecting the SmartNode to
the outside world.
ISDN Integrated Services Digital Network
ISDN Services ISDN Services comprise voice, data, video and
supplementary services. Supplementary services are services
available in the ISDN network, such as calling line
identification presentation (CLIP) or call waiting (CW). See
also Q.SIG
ISoIP ISDN over IP is patent pending solution of Inalp Networks
to carry ISDN services over IP networks.
Software Configuration Guide, Revision 1.03
18 Terms and Definitions
Term or Definiton Meaning
Jitter Jitter is the variation on packets arriving on a SmartNode.
See also dejitter buffer.
Mode The SmartWare CLI is comprised of modes. There are two
basic mode groups, the execution mode group and the
configuration mode group. See Chapter 5, “Command Line
Interface” for more details.
Network Management System System responsible for managing at least part of a network.
An NMS is generally a reasonably powerful and wellequipped computer, such as an engineering workstation.
NMSs communicate with agents to help keep track of
network statistics and resources.
Node Endpoint of a network connection or a junction common to
two or more lines in a network. A Node can be a router, e.g.
a SmartNode. Nodes, which vary in routing and other
functional capabilities, can be interconnected. Node
sometimes is used generically to refer to any entity that can
access a network, and frequently is used interchangeably
with device.
Nodename Name given to a SmartNode or network element.
nvram: Persistent memory section of a SmartNode containing the
startup configuration, the factory configuration and used
defined configurations.
Operator The person who has limited access to the SmartWare CLI.
PCI Local Bus The PCI Local Bus is a high performance, 32-bit or 64-bit bus
with multiplexed address and data lines. The bus is intended
for use as an interconnect mechanism between highly
integrated peripheral controller components, peripheral addin boards, and processor/memory systems.
PCM Highway A 30 channel interface connecting the switching engine with
optional interface cards containg circuit ports.
PMC The optional interface cards for SmartNode 2000 series
which are compatible to the PCI Mezzanine Card standards.
PMC Driver Software PMC driver software performs the runtime tasks on the PMC
interface card mounted in SmartNode 2000 series devices.
The PMC drivers are interface card specific and also have
build numbers. Refer to the SmartWare release notes for
PMC driver software compatibility. The PMC drivers may be
upgraded together with the SmartWare release or they can
be downloaded individually into the persistent memory
(flash:) of a SmartNode.
PMC Loader The PMC loader initialises the PMC interface card mounted
in SmartNode 2000 series of devices. It checks hardware
versions and determines if compatible PMC drivers are
available. The PMC loader may be upgraded together with
the SmartWare release.
Software Configuration Guide, Revision 1.03
Terms and Definitions 19
Term or Definiton Meaning
Port In SmartWare a port represents a physical connector on the
SmartNode.
Port Address A port address can be assigned to a CS interface to realize a
virtual voice tunnel between two nodes.
Post Filter The voice decoder output is normally filtered using a
perceptual post-filter to improve voice quality. See also
High-Pass Filter.
POTS Plain Old Telephone Service
Profile A profile provides configuration shortcutting. A profile
contains specific settings which can be used on multiple
contexts, interfaces or gateways.
PSTN Public Switched Telephone Network. Contains ISDN and
POTS
Q.931 Tunneling Q.931 tunneling is able to support ISDN services and Q.SIG
over an IP network.
Q.SIG ISDN Services comprise additional services for the Private
ISDN network such as CNIP (Calling Name Identification
Presentation), CNIR (Calling Name Identification
Restriction) etc. See also ISDN Services.
Release SmartWare is organized in releases that define the main
voice and data features of a SmartNode. Several builds can
be available from ca ertain release. See also build.
Routing Engine In SmartWare the routing engine handles the basic IP
routing.
Running Configuration The currently running configuration (running-config) for
SmartWare, which is executed from the volatile memory
(system:) on the SmartNode.
Session Router Calls through SmartNode can be routed based on a set of
routing criteria. The entity that manages call routing is called
Session Router.
Silence Compression Silence supression (or compression) detects the silent periods
in a phone conversation and stops the sending of media
packets during this periods.
Software Configuration Guide, Revision 1.03
20 Terms and Definitions
Term or Definiton Meaning
SmartNode The SmartNode is Inalp Networks networking product
available in two series:
• The SmartNode 1000 series are compact integrated
access devices for applications in SOHO or branch
office environments. They are available in a various
interface configurations supporting up to 4 voice
channels.
• The SmartNode 2000 series are modular integrated
services network nodes designed for medium and
large enterprise applications. Multiple PMC based
interface slots and a range of interface cards
provides flexibility for both LAN and WAN interface
configuration.
SmartView SmartView is a suite of element and network management
applications that enable the management integration of the
SmartNode platforms in a provider service and network
management system. SmartView ensures efficient operations
for SmartNode networks growing in size and complexity.
SmartWare SmartWare is the application software running on the
SmartNode hardware platforms. SmartWare is available in
several releases that in general support all currently available
SmartNode models.
Startup Configuration The startup configuration is stored in the persistent memory
(nvram:) and is always copied for execution to the running
configuration in the volatile memory (system:) after a system
start-up.
Switching Engine Part of the SmartNode hardware which allows software
controlled circuit switching of circuit ports.
System Image A collective term for application images and interface card
driver software, excluding configuration files.
System Memory The volatile memory, that includes the system: region,
holding the running-config for SmartWare during operation
of a SmartNode.
system: A region in the volatile memory of a SmartNode. See also
system memory.
TFTP Server A central server used for configuration up- and download,
download of application and interface card driver software,
that is accessed using TFTP.
tftp: Identification of a remote storing location used for
configuration up- and download, download of application
and interface card driver software, that is accessed using
TFTP.
Table 1-1: SmartWare Architecture Terms and Definitions
Software Configuration Guide, Revision 1.03
Applications 21
2 APPLICATIONS
This chapter provides an overview of SmartNode applications and the main elements in a
SmartNode network.
The chapter includes the following sections:
• Introduction
• Carrier networks
• Enterprise networks
• LAN telephony
2.1 Introduction
The Inalp SmartNode product family consists of highly flexible multi-service IP network devices,
which fit a range of networking applications.
To simplify the description of these applications they have grouped into three application scenarios:
1. Applications in carrier networks in which the SmartNodes are used as customer gateways or
integrated access devices at the customer premises. These applications are also called
Integrated Service Access (ISA).
2. Applications in enterprise networks in which the SmartNodes are used as WAN routers and
voice gateways for inter-site networking. These applications are also called Multiservice
Intranets (MSI).
3. Applications in LAN telephony in which the SmartNodes serve as gateways between the
LAN and the local PBX or PSTN access. These applications are also called LAN voice
gateway (LVG).
2.2 Carrier Networks
The network termination (NT) device in a multi-service IP based provider network plays a vital role.
It provides the service access point for the subscriber with respect to physical connectivity and
protocol interoperability.
Since the access bandwidth in most cases represents a network bottleneck, the NT must also ensure
traffic classification and the enforcement of service level agreements (SLA) on the access link. In
broadband access networks this NT is also called an Integrated Access Device (IAD) or customer
gateway.
The Inalp SmartNode products offer unique features as customer gateways for business services. It
provides amongst others full ISDN feature support, local switching and breakout options and mass
provisioning support.
Software Configuration Guide, Revision 1.03
22 Applications
Figure 2-1: Typical Carrier Network Application
Figure 2-1 shows the deployment of SmartNodes in carrier networks. Each subscriber site is
equipped with a SmartNode that connects the subscriber CPE on one side with the provider network
and services on the other.
Typical services in these networks are softswitch based telephony, PSTN access through V5.2
gateways, PBX networking services, and LAN interconnection.
Typical access technologies for these networks include xDSL, WLL, PowerLine and conventional
leased lines. With the use on an external modem (M) the SmartNode can connect to leased lines or
any bridged-Ethernet broadband access.
2.3 Enterprise Networks
In company owned and operated wide are networks SmartNodes can be used to converge voice and
data communications on the same IP link.
In combination with centralized services such as groupware and unified messaging the SmartNodes
provide migration and investment protection for legacy telephony systems.
Software Configuration Guide, Revision 1.03
Applications 23
Figure 2-2: Typical Enterprise Network
Figure 2-2 shows the deployment of SmartNodes in enterprise networks. Each site (headquarter,
branch or home office) is equipped with a SmartNode that connects the local LAN and telephony
infrastructure with the IP WAN and the local PSTN carrier.
2.4 LAN Telephony
With its Voice-over-IP gateway features the SmartNode can be used as a standalone gateway for
H.323 LAN voice systems such as LAN based PBXs or call centers.
A standalone gateway has performance reliability and scalability advantages compared with PC based gateway cards. In this application the SmartNode also offers a migration path to enterprise or
carrier networking.
Figure 2-3 shows the deployment of a SmartNode as a LAN voice gateway.
The PSTN connections can be scaled from a single ISDN basic rate access to multiple primary rate
lines. With Q.SIG integration in private PBX networks is also supported.
Software Configuration Guide, Revision 1.03
24 Applications
Figure 2-3: Typical LAN Telephony System
Software Configuration Guide, Revision 1.03
System Overview 25
3 SYSTEM OVERVIEW
This chapter provides an overview of the main elements of a SmartNode system.
The chapter includes the following sections:
• Introduction
• SmartNode hardware platforms
• SmartWare embedded software
• SmartView management tools
3.1 Introduction
A complete SmartNode system or network, as installed in any of the application scenarios
introduced in Chapter 2, “Applications”, is composed of three main elements plus a third-party
network infrastructure:
• The first and most obvious element is the SmartNode devices (also referred to as hardware
platforms or network nodes) that provide the physical connectivity, the CPU and DSP
resources. Throughout the range of SmartNode models all have the common characteristics
of supporting packet-routed and circuit-switched traffic equally well.
• The second, and in many aspects core element, is the embedded software running on the
SmartNode hardware platforms. The software designed by Inalp Networks AG for the
SmartNodes is termed SmartWare. This software is handled as a separate element because it
is as far as possible platform-independent and so provides the same features and
functionality throughout the complete SmartNode model range.
• The third element is the set of SmartView management tools provided to configure and
control SmartWare and SmartNodes in a network. The focus of the SmartView tools is on
assisting network administrators and operators in handling large numbers of SmartNode
devices. This complements the standard element management interfaces provided in
SmartWare.
• Finally the third-party IP network and transmission infrastructure provides IP connectivity
between the above elements. This infrastructure can range from a simple Ethernet hub or
switch to highly complex networks including multiple access technologies, backbone
transmission and services nodes.
Figure 3-1 illustrates these four elements.
Software Configuration Guide, Revision 1.03
26 System Overview
Figure 3-1: System Overview
3.2 SmartNode Hardware Platforms
The SmartNode series of devices covers a performance range varying from that suitable for small
office/home office (SOHO) applications to large corporate sites, or in terms of voice channels from 2
channels (one BRI/So) to 60 (two PRI/S2m). The SmartNodes comprise two classes:
• The SmartNode 1000 series compact devices with fixed configured on-board ports
• The SmartNode 2000 series with on-board ports plus expansion slots for individual interface
configurations using a range of optional interface cards (IC).
The basic system model of an Inalp SmartNode is depicted in Figure 3-2. Both the SmartNode 1000
and the 2000 series have three main components:
• 64k circuit switching is supported between on-board ISDN ports and on and between ISDN
and PSTN interface cards. The circuit switching engine uses dedicated hardware resources
and therefore can bypass the VoIP gateway and packet routing engine.
• Gateway (GW), which converts 64k circuits into Internet protocol (IP) packet streams and
vice versa. Voice over IP is supported according the H.323 standard and via Inalp Networks’
patented ISDN over IP (ISoIP) protocol.
• IP Router, with on-board ports and optional data interface cards. The router is QoS enabled
allowing classification, shaping and scheduling of multiple service classes.
Software Configuration Guide, Revision 1.03
System Overview 27
Figure 3-2: SmartNode System Model
For more detailed hardware information refer to the SmartNode Hardware Installation Guide.
3.3 SmartWare Embedded Software
SmartWare is the application software that runs on the SmartNode hardware platforms. SmartWare
is available in several releases that support all available SmartNode models. Refer to the SmartWare
release notes for detailed information about hardware support.
For each SmartWare release there are platform-specific build numbers. There may be more than one
build per release and platform as updates become available. Refer to the SmartWare release notes for
build numbers and build-specific enhancements and limitations.
A SmartWare build is a binary image file. A SmartWare build is usually divided into several
checksum-protected download files to improve download efficiency and security. The download to
the SmartNode is handled in sequence using a download batchfile. Refer to Chapter 8, “System Image
Handling”, for details on SmartWare image downloads.
In addition to the actual SmartWare images there are several additional embedded software
components that you will encounter:
• The boot loader is a “mini” application that performs basic system checks and which starts the
SmartWare application. The boot loader also provides minimal network services, allowing
the SmartNode to be accessed and upgraded over the network even if the SmartWare
application should not start. The boot loader is installed in the factory and is never
upgraded.
• The PMC loader initializes PMC interface cards when mounted in SmartNode 2000 series
devices. It checks hardware versions and determines whether compatible PMC drivers are
available. The PMC loader may be upgraded together with a SmartWare release.
Software Configuration Guide, Revision 1.03
28 System Overview
• PMC driver software performs the runtime tasks on PMC interface cards mounted in
SmartNode 2000 series devices. The PMC drivers are interface card specific and also have
build numbers. Refer to the SmartWare release notes for PMC driver software compatibility.
The PMC drivers may be upgraded together with a SmartWare release or they can be
downloaded individually onto the device flash memory file system.
3.4 SmartView Management Tools
SmartWare provides two standard element management interfaces:
• The Command Line Interface (CLI), which supports full online configuration and monitoring
access for the operator
• The SNMP agent and MIB, with an emphasis on inventory and alarm management for
integration in a 3
With the aid of configuration files and TFTP up and downloads, the SmartNodes can also be
managed offline using standard text editors and file systems.
A number of host-based management applications are available to facilitate the generation, editing
and maintenance of configuration files. Tools are also available for the integration of SmartNode
management into standard network management platforms such as HP OpenView.
rd
party Network Management System (NMS)
Figure 3-3: SmartNode Management System
Software Configuration Guide, Revision 1.03
Configuration Concepts 29
4 CONFIGURATION CONCEPTS
This chapter introduces the basic SmartWare configuration concepts. A good understanding of these
concepts is vital for the configuration tasks explained in the remaining chapters of this guide.
Even if you do not like to read manuals and user guides, nevertheless we strongly recommend that
you read through this chapter because it introduces the fundamental ideas behind the structure of
the command line interface. Once you understand and know this structure you will find it much
more intuitive to navigate through the CLI and configure specific features.
The chapter includes the following sections:
• Introduction and Overview
• Contexts and Gateways
• Interfaces Ports and Bindings
• Profiles and use commands
4.1 Introduction and Overview
The Inalp SmartNodes are multi-service network devices that offer high flexibility for the interworking of circuit switched and packet routed networks and services. In order to consistently
support a growing set of functions, protocols and applications, SmartWare configuration is based on
a number of abstract concepts that represent the various SmartWare components.
Figure 4-1: Configuration Concept Overview
Figure 4-1 illustrates the various elements of a complete SmartNode configuration. Each of these
elements implements one of the configuration concepts described in this chapter. The figure also
shows the relationships and associations between the different elements. The relations are specified
through bind (arrow) and use (bullet-lines) commands. For example, you need bind commands to
bind a physical port to a logical interface, and use commands to assign profiles to contexts.
Software Configuration Guide, Revision 1.03
30 Configuration Concepts
The chapter sections that follow refer to Figure 4-1 and describe the concepts and elements in more
detail.
4.2 Contexts and Gateways
4.2.1 Context
A SmartWare context represents one specific networking technology or protocol, namely IP (Internet
Protocol) or CS (circuit-switching). A context can be seen as ”virtual dedicated equipment” within
the SmartNode. For example:
• A CS context contains the circuit-switching functions of the SmartNode. It can be seen as an
embedded multiplexer or cross-connect within the SmartNode
• An IP context contains the routing functions of the SmartNode. It can be seen as a embedded
router within the SmartNode
The contexts are identified by a name, and contain the configuration commands that are related to
the technology that they represent. By means of the context concept a separate configuration can be
built for newly supported network layer technologies without complicating the configuration
methods of existing features. For example, as bridging, ATM or FR switching become available so
can a bridging, ATM; or FR context be introduced.
Each context contains a number of interfaces, which build the connections to other SmartWare
elements and the outside world. Figure 4-1 shows two contexts: one of type IP named “router”, and
one of type CS named “switch”. This corresponds to the default configuration of all SmartNodes.
Note
SmartWare currently supports only one instance of the CS and IP context types.
Examples
The IP context named “router” can contain static routes, RIP and NAT configuration parameters. The
circuit-switching context named “switch” can contain number translations, local breakout conditions
and least-cost routing parameters.
4.2.2 Gateway
For the communication between contexts of different types the concept of a gateway is introduced. A
gateway handles connections between different technologies or protocols. For example: an H.323Gateway can connect an IP context to a circuit-switching context.
The gateways are each of a specific type and are identified by a name. Each named gateway contains
its configuration parameters. With this concept, a separate gateway can be built for newly-supported
technology such as MGCP or SIP without complicating the configuration methods of existing
software parts. Figure 4-1 shows two gateways, one of type h323 named “h323gw” and one of type
ISoIP named “isoipgw”.
Example
An H.323 gateway named “h323-gw” has an H.323 gateway ID and an associated gatekeeper
configuration. It is connected to the interface “ip-trunk” on the circuit-switch context “switch” and
the interface “global-wan” on the IP context “router”.
4.3 Interfaces, Ports and Bindings
4.3.1 Interfaces
The concept of an interface in SmartWare differs from that in traditional networking devices. The
traditional use of the term interface is often synonymous with port or circuit, which are physical
Software Configuration Guide, Revision 1.03
Loading...
+ 291 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.