Enterprise Edge Attendant Console User GuideP0908544 Issue 01
Page 3
Contents
Chapter 1Introducing Enterprise Edge 7
Routing and IP Services 7
System Software 8
Chapter 2Using Enterprise Edge Unified Manager 9
Understanding Unified Manager 9
Changing the appearance of Unified Manager 12
Adjusting Unified Manager views 12
Navigating between views 13
Changing column order 14
Generating statistics 15
Menu descriptions 16
Chapter 3Using Enterprise Edge Services 17
Enterprise Edge required parameters 17
Setting up an Enterprise Edge IP Address 18
Setting up web-based administration 19
Browser settings: 19
Logging on to Enterprise Edge 20
Logging off Enterprise Edge 21
Powering down the Enterprise Edge server 21
Rebooting the Enterprise Edge server 21
IP Routing 22
Enterprise Edge supports the following routing and IP Services:
•Routing Services
– IP Routing Protocol
– RAS Service and Dial In Capabilities for Management Purposes Only
– RIP
– Packet Filtering
•IP Services:
– DHCP
– DNS
– Web Caching
•VoIP (voice over IP) Service
1
VoIP is a term used in IP telephony for a set of facilities that manage voice
information delivery using Internet Protocol (IP). VoIP sends voice information
in digital form in discrete packets rather than in the traditional circuitcommitted protocols of the public switched telephone network (PSTN). A
major advantage of VoIP and Internet telephony is that it avoids ordinary telephone service tolls.
VoIP derives from the VoIP Forum which promotes the use of ITU-T H.323 as
the standard for sending voice (audio) and video using IP on the public Internet
and within intranets. The VoIP Forum also promotes the use of directory service
standards so that users can locate other users and the use of touch-tone signals
for automatic call distribution and voice mail.
In addition, VoIP uses the real-time protocol (RTP) over IP to help ensure that
packets get delivered in a timely way. Using public networks, it is currently
difficult to guarantee Quality of Service (QoS). Better service is possible with
private networks managed by an enterprise or by an Internet telephony service
provider (ITSP).
When using VoIP a business positions Enterprise Edge as a gateway. The
gateway receives packetized voice transmissions from users within the
company and then routes them to other parts of its intranet (local area or wide
area network) or sends them over the public switched telephone network.
Enterprise Edge provides services to end-users in a small office environment. The
following services are managed through Enterprise Edge Unified Manager, a webbased user interface:
•IP Services
•VoIP Service
•Telephony Functions:
– PBX Call Processing
– Voice Mail
– Call Center Solution with Auto-Attendant
As you navigate the menu tree shown in Unified Manager main view on page 9,
Unified Manager displays configuration screens. The screens contain settings that
you can edit to configure Enterprise Edge settings.
Enterprise Edge uses boxes and dialog boxes for configuring settings. Boxes let you
to edit and save data line by line. Each time you tab to the next line, the previous
line’s values are saved. See Unified Manager main view on page 9 for an example.
If a value is invalid, a beep sounds and an error message appears to alert you of the
error. The dialog box format allows you to enter text in boxes and save the settings
by clicking the Save button. See Unified Manager main view on page 9 for an
example.
The configuration screen contains:
•the title of the screen
•boxes
•scroll bars, when needed
•Save and Cancel buttons
To configure settings:
1. Click keys on the navigation tree or click commands on the menu.
The corresponding dialog box or screen appears.
2. Type the information in the appropriate box.
3. Click the Save button to save changes
or
click the Cancel button to close the configuration screen without saving any
changes.
The following figure shows boxes and a scroll bar:
boxes
To make changes to boxes:
1. Click keys on the navigation tree until the configuration screen appears.
See Unified Manager main view on page 9.
scroll
bar
2. Type the updates in the appropriate boxes and follow the syntax that appears
next to the box.
If there is an error, a beep sounds and an error message appears.
3. Press the Tab key to move to the next box.
Pressing the Tab key saves changes in the current box and moves the cursor to
the next box..
Note: In some instances you must press the Tab key several times to move the
Enterprise Edge provides statistical information on Enterprise Edge server
throughput and other performance-related information. The data is formatted in a
Statistical chart or Statistical table format.
For additional performance information and instructions, see Graphs and tables on
page 154.
You access Enterprise Edge functions using the menu. The menu is dynamic which
means that the menu commands change depending on the action a user takes.
Enterprise Edge menu
menu
Menu descriptions
UseTo
GroupView the system, resources, services, and management.
EditEdit parameters.
ConfigurationAccess configuration dialog boxes and screens
PerformanceAccess performance graphs and tables.
FaultAccess fault management settings.
ReportGenerate a report.
ToolsUse Enterprise Edge tools.
LogoffLog off the Enterprise Edge server.
ViewChange the appearance from Windows, Motif or Sun Swing.
HelpAccess online help.
The Enterprise Edge quick start module provides quick access to the parameters
necessary for the Enterprise Edge server to become active online. However, you
need to enter a minimum set of parameters within the quick start module. For more
information, see the Enterprise Edge Installation Guide.
Obtain the required parameter values from an Internet Service Provider (ISP) or
corporate network administrator.
Note: Nortel Networks recommends that after you powered on the Enterprise
Edge server and connect with either an RS-232 or an Ethernet port,
configure all the required parameters at the same time. After you configure
the parameters, reboot the Enterprise Edge server from either the console or
the graphical user interface (GUI).
•Fractional T1 channel numbers (if you are using fractional TI)
•System name
•WAN Link Protocol
•Frame Relay DLCI / CIR (if applicable)
•V.90 modem dial-up username and password (if applicable)
•V.90 modem dial-up phone number and optional alternate phone number (if
applicable)
The following table describes the Enterprise Edge server connectivity options.
FieldDefinition
HTTPYou can launch your JAVA-enabled browser to connect to the Enterprise Edge
server IP address that connects to your PC. This displays the log in screen. See
the Enterprise Edge log on screen
TTYYou can connect a dumb terminal to the console of the Enterprise Edge server
through an RS-232 cross-over cable, or, you can use Hyperterminal from Win95/
Win NT systems. Refer to the installation guide for console menus.
on page 20.
Setting up an Enterprise Edge IP Address
To manage the Enterprise Edge server using a web browser or a Telnet connection,
you must first set up the IP address. The Enterprise Edge server LAN interface is
shipped with default IP 10.10.10.1 and mask 255.255.255.0.
To set up the Enterprise Edge server initial IP address using a RS-232 port:
1. Turn on the Enterprise Edge server power switch.
2. Connect a PC or laptop computer to the Enterprise Edge server RS-232 port.
3. Start a hyper terminal on the PC or laptop computer.
4. Enter the LAN/WAN IP address and other parameters.
To set up the Enterprise Edge server IP address using a LAN:
1. Turn on the Enterprise Edge server power switch.
2. Connect a laptop to the Enterprise Edge server by Ethernet (back-to-back by
using a crossover cable to avoid disturbing the corporate LAN).
3. Set your PC or laptop computer IP address to 10.10.10.2 with a mask
255.255.255.0.
4. Start a web browser on your laptop with a URL 10.10.10.1.
Setting up web-based administration
To establish web-based administration, a workstation needs to be set up as an
Enterprise Edge client with Internet Explorer 4.0 or greater and a JAVA Virtual
Machine (JVM) 5.0.0.2922 or greater installed.
To install JVM on a workstation, search the Microsoft information web page for
instructions.
Using Enterprise Edge Services 19
This minimum PC requirements are discussed in Enterprise Edge specifications.
Note: The ideal display for a monitor attached to Enterprise Edge is 1280 x 1024.
Browser settings:
Set your browser as follows:
ProgramRequired Settings
Netscape Communicator 4.5
or greater
Internet Explorer 4.0 or
greater
Click Settings: Edit: Preferences
Category Advanced
set Enable Java: On
set Category: Cache
set Cached document comparison: Every Time
Choose Views: Internet Options Category: General: Temporary
Internet Files: Settings
click Check for newer versio ns of stored pages: Every vis it to t he
page
set Advanced Java VM
set Java JIT compiler enabled
Enterprise Edge OA&M allows multiple users to log on. If each user that logs on
attempts to configure the same or related subsystems, the most recent modification
remains in effect and overwrites changes by another administrator. Administrators
must be careful to not make any unintended changes.
Nortel Networks recommends that only one administrator user account is
maintained in Enterprise Edge and access is closely cont rolled. Administrators must
coordinate changes to avoid unintended changes.
Note: Do not use proxy servers while configuring Enterprise Edge using WEB
OA&M. You must disable proxies and directly access Enterprise Edge. The
configuration procedures depend on the browser and version.
Logging on to Enterprise Edge
To log on to Enterprise Edge:
1. Open a web browser.
2. In the address, type the Enterprise Edge IP Address in a web browser.
For example: HTTP://10.10.10.1
3. Press the Enter key.
The Enterprise Edge log on screen appears
4. In the Login box, type your log on name.
The default log on name is supervisor.
5. In the Password box, type your password.
The default password is super.
6. Click the Configure button.
The Enterprise Edge Unified Manager software starts. Consult your system
administrator for appropriate information. Depending on your system, Unified
Manager software can take up to several minutes to initialize.
LoginThe user name. The name can contain up to 50 case-sensitive alphanumeric
characters. The default log in name is supervisor.
PasswordThe Enterprise Edge password. The password name can contain up to 12 case-
sensitive alphanumeric characters. The default password is super.
Configurelets you access Enterprise Edge configuration.
Uploadlets you upload and apply Enterprise Edge settings and system settings.
Downloadlets you download and save Enterprise Edge settings and system settings.
Logging off Enterprise Edge
To log off Enterprise Edge:
1. Click the MSP icon on the left frame.
2. On the menu click Logoff and then click Logoff.
A message appears that asks you to confirm your request to log off.
Using Enterprise Edge Services 21
3. Click the Yes button to log off.
Powerin g d o wn the Enterpri s e E dge server
To power down the Enterprise Edge server:
1. From the menu of the console, quit Enterprise Edge.
2. Remove the power connection.
Rebooting the Enterprise Edge server
To reboot the Enterprise Edge server:
1. Click Logoff and then click Reboot.
A message appears that asks you to confirm your request to reboot.
•Packet Filtering
– source address
– destination address
– IP Protocol ID
– TCP Port
– UDP Port
– ICMP Type
– ICMP Code
•LAN to WAN routing
– managing traffic using Interrupt Modulation
•LAN to LAN routing
– Fast Path Routing
IP Routing Overview
The Internet Protocol (IP) is the protocol used on the Internet to send data is sent
from one computer to another. Each computer on the Internet, called a "host", has
at least one address that id entifies it from all other computers o n the Internet. When
you send or receive data (for example, an e-mail or a web page), the message gets
divided into units called packets. Each of these packets contains both the sender's
Internet address and the receiver's Internet address.
A packet is first sent to a router that understands reads the destination address and
forwards the packet to an adjacent router that reads the destination address.This
routing process continues across the Internet until one router recognizes the packet
as belonging to a computer in its immediate neighborhood or domain. That router
forwards the packet to the computer whose address is specified.
Because a message is divided into a number of packets, each packet can, if
necessary, be sent by a different route across the Internet. Packets can arrive in a
different order than the order they are sent. Another protocol, the Transmission
Control Protocol (TCP) to put the packets in the right order.
IP is a connectionless protocol, which means that there is no established connection
between the end points that communicate. Each packet that travels through the
Internet is treated as an independent unit of data without any relation to another unit
of data. The packets get put in the right order because TCP, the connection-oriented
protocol, keeps track of the packet sequence in a message. In the Open Systems
Interconnection (OSI) communication model, IP is in layer 3, the Networking
Layer.
Enterprise Edge IP routing specifics
Using Enterprise Edge Unified Manager, you can perform the following routing
configuration options:
•Add or delete the interfaces to routing protocols
•Configure routing protocol options
•Add and delete static routes
•Add or delete filters
•Set filter actions
For instructions on configuring routing options, see Routing on page 85.
The followings table shows the Enterprise Edge IP routing protocols and the
precedence order when conflict or redundant routes occur.
PrecedenceIP Routing Protocols
1.Static Routing
2.SNMP
3.RIP v1 and v2
IP Addressing Overview
IP addresses follow the format nnn.nnn.nnn.nnn, where nn is a number between 0
and 255. For example, 192.123.4.56 or 10.1.1.1. IP addresses enable computers to
communicate to each other. Both servers and workstations on a network must have
IP addresses. There are two types of IP addresses:
Dynamic – A dynamic IP address changes. Dynamic IP addresses are assigned
to computers by an IP address server as the computer needs it. Usually there is
a particular range or scope of IP addresses that your network uses. With
dynamic IP addressing, a computer can have a different IP address every time
it connects to the network. Other devices need to know the computer’s IP
address so that they can communicate with it. The IP address server manages
the assignment of IP addresses to the client workstations.
Static – A static or fixed IP address never changes. It is assigned to a computer
permanently. The computer has the same IP address every time it connects to
the network and is known to other devices on the network by that IP address.
Enterprise Edge users can add static routes to the IP routing table. These static
routes take precedence over those routes chosen by routing protocols, such as RIP.
To add a static route, see Static Route on page 94.Note: Ensure that users do not add a static route for default route 0.0.0.0 with mask
0.0.0.0. Enterprise Edge’s Net Link Manager automatically creates a default
route and adjusts it according to link status unless router or Net Link
Manager are running.
Routing Information Protocol (RIP)
RIP is a widely-used protocol for managing routing information in a self-contained
network such as a corporate intranet. RIP is classified by the Internet Engineering
Task Force (IETF) as one of several internal gateway protocols (IGPs).
A RIP router sends full updates, which list all the other hosts it knows about, to its
closest neighbor host every 30 seconds. The neighbor host sends the information to
its next neighbor, until all the hosts in the network know the routing paths, a state
known as network convergence. RIP uses a hop count to determine network
distance. Each host with a router in the network uses the routing table information
to determine the next host for the packet, until a specified destination is reached.
Enabling RIP on Network Interfaces
To run RIP on one or more network interfaces, go to the specific interface under
router and enable RIP. After you enable RIP for an interface, you do not have to
reboot the Enterprise Edge server for the changes to take effect.
Packet Filtering
A packet is a unit of data routed between an origin and a destination on the Internet
or on any other packet-switched network. When any file such as an e-mail message,
HTML file, GIF file or URL request, is sent on the Internet, the IP layer divides the
file into packets of an efficient size for routing. Each of these packets is numbered
and includes the Internet address of the destination.
Enterprise Edge supports basic (or stateless) packet filtering for IP. You can
configure the filter to pass only the packets from the routes they list, or to pass
everything except the packets for the routes they list.
Each route in the list can be any combination of the following packet filtering
features. By default, no packet filer is configured.
Enterprise Edge supports the following packet filtering features for IP:
Packet Filter FeatureComments
Source Addressthe source address field of the packet to be filtered.
Source Maskthe source address mask of the packet to be filtered.
Destination Addressthe destination address field of the packet to be filtered.
Destination Maskthe destination address mask of the packet to be filtered.
Protocolthe protocol type of the packet to be filtered.
Source Portthe source port of the packet to be filtered. This field applies
only if protocol value is TCP or UDP.
Destination Portthe destination port of the packet to be filtered. This field
applies only if protocol value is TCP or UDP.
ICMP Typethe ICMP type field of the packet to be filtered. This field
applies only if protocol value is ICMP.
ICMP Codethe ICMP type field of the packet to be filtered. This field
applies only if protocol value is ICMP.
Note: When you set filters, you must forward packets going to the RPC port (port
135 TCP or UDP) for correct Unified Manager operation.
LAN-to-LAN Fast Path Routing
Enterprise Edge provides an optional second 10/100 LAN interface. If the second
LAN interface is used, Enterprise Edge uses optimized software for high
performance routing. This includes an innovative design that speeds up the
performance for LAN-to-LAN routing by over three times the rate that is normally
achieved using traditional software architecture.
Dynamic Host Configuration Protocol (DHCP)
DHCP (Dynamic Host Configuration Protocol) is a protocol that lets network
administrators manage and automate the assignment of Internet Protocol (IP)
addresses in an organization's network. Using the Internet's set of protocols (TCP/
IP), each machine that can connect to the Internet needs a unique IP address. If an
organization sets up its computer users with a connection to the Internet, an IP
address must be assigned to each machine.
Without DHCP, the IP address must be entered manually at each computer. If
computers move to another location in another part of the network, a new IP address
must be entered. DHCP lets a network administrator supervise and distribute IP
addresses from a central point and automatically sends a new IP address if a
computer connects to a different place in the network.
You can set up Enterprise Edge to be your LAN’s DHCP server and let it assign IP
addresses to the workstations on your LAN as they need them. This is the
recommended configuration.
If you set up the Enterprise Edge server as a DHCP server, you must let all of your
workstations know that they will have their new IP addresses assigned by
Enterprise Edge. To do this, you may need to change the configuration of each
workstation individually.
If you already have a DHCP server, you must let it know that the Enterprise Edge
server is their gateway and DNS proxy for the workstations.
Your Enterprise Edge server can function as a DHCP server. You can use this
feature if you do not want to administer static IP addresses for every workstation on
your network. You can configure Enterprise Edge to assign IP addresses
dynamically.
Automatic Configuration using a DHCP server
To configure the DHCP server, you need to create a particular range (or scope) for
each LAN interface in Enterprise Edge and allocate a block of IP addresses for that
scope. The Enterprise Edge Auto-Configure system automatically creates a scope
using parameters inherited from the LAN interface.
Guidelines for Using DHCP
Since many default DHCP parameters are inherited from LAN interface
parameters, configure LAN interfaces before configuring DHCP.
If you are modifying the DHCP configuration on Enterprise Edge, follow the same
guidelines of your organization. In particular, you can perform one or more of the
tasks listed below to ensure proper operation of the networked system:
1. If a change in the DHCP configuration resulted in the change of ‘Router’ and
‘Subnet mask’ options in a scope, users must do one of the following to
ensure basic operation:
•Execute ipconfig /release and ipconfig /renew on each of the workstations.
For Windows 95 and Windows 98, use its equivalent, winipcfg.
•For clients that do not support ipconfig and winipcfg, reboot is required to
renew their IP addresses.
2. If change in DNS server or DNS name options happens, users need to repeat
the tasks in step 1 to ensure proper connectivity with the organization.
3. Always schedule a down time associated with these changes.
4. Nortel Networks recommends that you reboot Enterprise Edge to initialize
changes.
Using Enterprise Edge, you can define a DHCP scope for each LAN interface.
DHCP server parameters are divided into two categories: global and scope specific.
Global parameters apply to all scopes. Specific parameters apply to a specific
scope.
The domain name service (DNS) is the system within the Internet t hat maps names
of objects, usually host names, into IP numbers or other resource record values. The
name space of the Internet is divided into domains. The responsibility for managing
names in each domain is usually delegated to systems in each domain.
Enterprise Edge functions as both a gateway to the Internet and as a DNS proxy:
•Gateway: a system that links two different types of networks and enables them
to communicate with each other. Enterprise Edge is the gateway that links your
company’s network to the Intranet or Internet. Depending on your
configuration, you can let your workstations know that Enterprise Edge is your
Internet gateway.
Note:If your PC is a DHCP client under Enterprise Edge, you do not have to do
this.
•DNS Proxy – A Domain Name Service (DNS) proxy translates alphabetic
domain names into computer-readable IP addresses. For example, the domain
name www.nortelnetworks.com for the Nortel Networks web site can translate
to the IP address 192.177.5.18. After a domain name is translated into an IP
address, the workstations on your network can communicate with the web site.
Depending on the configuration of your system, you can let your workstations
know that Enterprise Edge is the DNS proxy.
Using Enterprise Edge Services 27
When Enterprise Edge receives DNS requests from clients, it first checks its local
cache for name entries and records. If found locally, Enterprise Edge immediately
responds to clients. Otherwise, Enterprise Edge creates a new DNS request to the
remote Primary or Secondary DNS servers on behalf of the client. If the remote
DNS server responds with the requested records, they are forwarded to clients and
cached in Enterprise Edge.
Note: If your PC is a DHCP client under Enterprise Edge, you do not have to let
your workstations know that Enterprise Edge is your DNS server.
Guidelines for Using DNS
Consider the following guidelines when using DNS:
•If the Enterprise Edge DNS service is enabled, make sure that clients always use
Enterprise Edge as their DNS server.
•When it is disabled, set the DNS Server field in DHCP configuration to the
remote DNS server IP address. If DHCP service is also disabled in Enterprise
Edge, tell all clients to set the DNS server in their IP configuration to the remote
DNS server.
•The DNS proxy carries security features because it keeps all of the internal IP
addresses from external web servers.
•You are required to fill in the remote Primary DNS server IP addres s. See DNS
on page 84 for instructions.
When you use Enterprise Edge as a web proxy, Enterprise Edge can store or
cache information downloaded from the Internet. A proxy is a server that acts on
behalf of another. Web caching allows LAN workstations to share common
information downloaded from the Internet.
Data is usually cached on individual workstations. Each time a workstation on the
LAN requests information from the Internet, the individual’s request is sent to the
Internet, and the information is returned to their workstation. If multiple LAN
workstations request common data, a web cache on the network reduces download
time from the Internet.
With Enterprise Edge configured as a web proxy with web caching:
•LAN workstations have shorter download times.
•Previously downloaded information is stored for future use by all workstations
on the LAN.
•Enterprise Edge retrieves information from the Internet only if it is not already
cached or if the cached file is out of date compared to the information on the
Internet.
•Cookie blocking protects users’ privacy.
You can configure the web caching settings through your web browser.
The web proxy also provides security features similarly to the DNS proxy because
it hides all of the internal browsers’ IP addresses from external web servers.
External web servers see Enterprise Edge’s IP address.
Guidelines for Using Web Caching/Proxy
The Enterprise Edge web proxy uses a web server for running in HTTP-Proxy
mode.
Consider the following guidelines when using web caching/proxy:
•A web server installed in Enterprise Edge can not be used as a general purpose
HTTP server. It is only used by the Enterprise Edge web-based management
client and web-cache services.
•If users need to run their web sites, they need to run the HTTP Server on another
system and make its IP address known to Enterprise Edge.
To set the web server as the web cache/proxy, refer to Web cache on page 126.
•Relationship between the QoS Module and the VoIP QoS monitor
•Enterprise Edge QoS restrictions and defaults
QoS overview
On the Internet, Quality of Service (QoS) is the methodology that transmission
rates, error rates, and other characteristics can be measured, improved, and, to some
extent, guaranteed in advance. QoS is of concern for the continuous transmission of
high-bandwidth voice and video multimedia informati on. Transmitting this content
dependably is difficult in public networks using ordinary “best effort” protocols.
Real-time applications that include voice and video are time-sensitive. Delivering
voice and video over the Internet requires bounded packet delay and jitter.
Differentiated Services (DiffServ) is a QoS framework standardized by IETF that
focuses on DiffServ standards for real-time and mission critical applications. The
DiffServ standards are evolving and vendors are starting to develop network
devices that support DiffServ.
The purpose of the Enterprise Edge QoS module is to prioritize IP traffic and to
provide an acceptable quality of service to delay and jitter sensitive applications
such as audio and video as well as mission critical applications.
The Enterprise Edge QoS module primarily serves two purposes:
•In a DiffServ network, it acts as an edge device and performs the packet
classification, marking, and prioritization.
•In a non-DiffServ or legacy network, it manages the WAN link to make sure
premium voice (and optional video) packets get high priority when crossing the
slow WAN link in both directions.
•Performs admission control based on the WAN link usage
•Marks the packets as premium once admitted
Enterprise Edge implements the DiffServ queuing model that includes a premium
queue and eight best-effort queues. The premium queue has a stricter high priority
than the best-effort queues. The eight best-effort queues are scheduled by a
weighted-fair-queuing (WFQ) algorithm. Since best-effort traffic is not shaped and
does not go through the admission control process, the WFQ is needed to avoid
starvation of low priority packets.
Currently, H.323 traffic is allowed to get into the premium queue. Users can allow
other traffic to be premium by setting up priority filters on the web-based GUI using
the following filter criteria:
•Source IP address (with mask)
•Destination IP address (with mask)
•IP protocol ID (e.g. TCP, UDP, or ICMP)
•Source port range
•Destination port range
•Incoming TOS field
Note: There is no traffic shaping mechanism implemented in this version. Be
cautious when setting up premium priority filters. If the traffic is high
volume and with high bursts, it may impact VoIP quality. Unless necessary,
Nortel Networks recommends that you allocate traffic to the high priority
best-effort queues instead of the premium queue.
Legacy Network
In a legacy network, Enterprise Edge assumes that network devices, such as routers
and switches, do not recognize the IP header TOS field (as defined by DiffServ) and
do not perform the corresponding priority processing. However, most of the current
installed routers, including those from Cisco and Nortel Networks, allow
administrators to set up priorities by IP addresses, port numbers or protocol types,
which is similar to the priority filters described above.
Note: This information is specific to H.323 traffic in legacy networks.
In this environment, Enterprise Edge allows H.323 voice (and optional video)
packets to travel across the WAN link with high priority in both directions using
existing router features.
An administrator needs to reserve a block of UDP port numbers and configure them
as high priority in both Enterprise Edge and the remote router at the other end of the
WAN link. Enterprise Edge forces all of the admitted H.323 streams to fall into the
reserved port range by using a proprietary technique so that these H.323 voice
(video) packets can get high priority. This is completely transparent to the end
H.323 terminals.
See Appendix B: Setting Up Remote Routers on page 167 for additional
information on setting UDP port ranges for remote routers.
Note: If an administrator configures all routers in their corporate network
with the same reserved port numbers (both in and out), admitted H.323
streams can get end-to-end high priority. However, routers connected
to WAN links are more critical because they are typically the
bottlenecks.
You can set up best-effort traffic priorities through the web-based Unified Manager
by using the following filter criteria:
•Source IP address (with mask)
•Destination IP address (with mask)
•IP protocol ID (e.g. TCP, UDP, or ICMP)
•Source port range
•Destination port range
•Incoming TOS field
There are a total of 8 priority classes for best-effort traffic in Enterprise Edge. By
default, all best-effort traffic is sent to Class 5 (queue 5), with Class 1 the highest
and Class 8 the lowest in priority.
Admission Control
Enterprise Edge allows users to set a certain percentage of the WAN bandwidth for
premium traffic. This traffic takes strict priority over best-effort traffic. In this
version, H.323 (VoIP) flows need to pass the admission control process to be
treated as premium traffic.
For admission control, Enterprise Edge uses the WAN Premium Bandwidth
parameter. Specifically, for each H.323 flow, QoS performs admission control
using the negotiated coding algorithm. A flow is admitted a s a premium flow if the
current total WAN premium usage plus the new flow is lower than the allocated
WAN premium bandwidth.
Otherwise, the flow is rejected and he flow is still delivered as best-effort traffic.
As a reference point: for a typical G.729 codec, each VoIP flow requires the
following WAN bandwidth, depending on the codec sample rate:
G.729Sample Rate
30 ms
No
Compression
Data
Compression
RTP Hdr Comp. 5.8 k6.8 k9.6 k
10.6 k14 k24 k
8 k10 k16 k
Sample Rate
20 ms
Sample Rate
10 ms
Note: The calculation is based on a full-duplex WAN link with HDLC overhead
and VoIP with silence suppression.
Nortel Networks recommends that for slow WAN links, such as a 56K leased line
or ISDN, H.323 video is not configured as premium traffic.
Packet Marking for DiffServ Networks
Enterprise Edge classifies traffic and marks packets by setting the IP header type of
service (TOS) field. By default, the following items are classified as premium
traffic:
•All VoIP flows
•RIP packets: routing packets are periodically exchanged between Enterprise
Edge and remote routers. These packets need higher priority than regular
packets to ensure that the routing protocol is working properly.
•ICMP packets: Enterprise Edge Net Link Manager uses the ‘ping’ command to
decide whether the primary WAN link is active or inactive. These packets are
not delayed by regular packets.
•UDP Port 5000 packets – Enterprise Edge VoIP QoS Monitor uses port 5000 in
a proprietary protocol to monitor the IP network delay and jitter. Since
Enterprise Edge assigns VoIP packets to the premium queue, it also gives these
monitor packets high traveling priority.
•Admitted RTP/RTCP packets.
In Enterprise Edge, there are two places a user can set up a TOS field in an IP
header:
TOS-for-Premium-Traffic – this field sets TOS bits for premium packets for
DiffServ networks. If this field is ignored, Enterprise Edge uses a default value
of 0xB8.
TOS-for-Priority-Filters– this field sets TOS for those packets matching a
specific priority filter.
Note: You can specify packets matched to a filter to go Priority Queue 0 – 8. The
Queue 0 is for premium packets, and Queue 1 – 8 correspond to best-effort
priority classes 1 – 8.
If you specify Queue 0 and a TOS bits for a filter, then this TOS takes
precedence over the TOS set for premium traffic for all packets tha t match this
filter.
The default TOS for all best-effort packets is 0x00, and the default queue for
best-effort packets is Queue 5.
WARNING
Premium flows that are specified by priority are not admission controlled. Unless
you know the behavioral characteristics of a flow, do not specify flows as premium.
Instead, you can specify them as the highest B-E traffic.
Consider the following guidelines when you set up priority filters
•The fewer the conditions to check for, the fewer CPU cycles are consumed.
Filter processing is faster if fewer conditions are specified, without
compromising the precision in selection.
•If you don’t need the value of a particular criterion, such as source port number,
don’t set a corresponding value for the filter.
•When you specify the layer 3 sub-protocols, use the port number/IP address
combinations and avoid specifying the protocol field. Nortel Networks
recommends that you specify a protocol field only if you manage an unusual
condition in your network. This reduces the consumption of CPU cycles.
•Users can configure the precedence of the filters. Packets are matched against
each filter sequentially until a match is found. Pay attention when specifying the
precedence of filters. Placing ‘popular’ filters ahead of ‘unpopular’ filters can
significantly speed up the processing.
Enterprise Edge uses UDP port ranges to provide high priority to VoIP packets in
existing legacy IP networks. These same port ranges must be reserved and set to
high priority on all routers that an administrator expects to have QoS support.
Reserving port ranges is not required for DiffServ networks.
You can select any port ranges that are not used by well-known protocols or
applications.
Each H.323 or VoIP RTP flow uses two ports. The total number of UDP port
numbers to be reserved depends on how many concurrent RTP flows are expected
to cross a router interface. In general:
•Backbone routers reserve more ports than edge routers.
•Edge routers’ port ranges are a subset of the backbone router port ranges.
•Add UPP 5000 to high priority.
•Enterprise Edge’s port ranges are a subset of the remote router’s port ranges.
•You must reserve two ports for each voice call you expect to carry over the
WAN. You need two ports for each video session if it is given premium
treatment.
•You can reserve multiple discontinuous ranges. Nortel Networks requires each
range meet the following conditions:
- Each range must start with an even number.
- There must be an even number of ports in a range.
See Appendix B: Setting Up Remote Routers on page 167 for additional
information on setting UDP port ranges for remote routers.
Relationship between the QoS Module and the VoIP QoS Monitor
The VoIP gateway in Enterprise Edge includes a Quality-of-Service Monitor
(QMON) that periodically monitors the delay and jitter of IP networks between two
peer gateways by using a proprietary protocol. These monitoring packets are
delivered at UDP port 5000.
The main objective of the QMON is to allow new VoIP calls to fa ll-ba ck to PSTN
if the IP network is detected as “bad”.
The QoS module discussed here complements QMON. While QMON passively
monitors the IP network, the QoS module actively improves the IP network by
giving VoIP packets higher priority to travel so that the chance for QMON to detect
“bad” is reduced.
Note: For a VoIP call, if a packet passes QMON but fails the QoS admission
control, it is delivered over IP but only as a best-effort flow. There is no fall
back to PSTN if a packet has passes QMON checking.
QMON packets travel at the same priority as VoIP packets or at higher priority than
normal IP packets. If VoIP packets travel at a premium level but QMON packets
travel at normal best-effort level, it is possible for QMON to report the IP network
as “bad” and start to PSTN fall-back, but the actual delay and jitter for VoIP packets
are still “good”, since VoIP packets have a higher priority. To avoid this add UDP
port 5000 to the high priority queue in all routers.
Enterprise Edge QoS Restrictions and Defaults
Enterprise Edge QoS includes the following restrictions and defaults:
•By default, the general bulk of traffic (not defined by priority filters) is routed
to best-effort Queue 5 (with Queue 1 the highest priority and Queue 8 the
lowest). An administrator can define four classes of traffic above the generic
traffic and three classes below it.
•A maximum of 31 priority filters for best-effort traffic can be created.
•The QoS module can be optionally turned ON or OFF. The default setting is on.
•The predetermined WAN bandwidth is always available to VoIP gateway
channels. That is, VoIP gateway calls are always admitted. The remaining
WAN premium bandwidth can be used by other H.323 streams, such as
Microsoft NetMeeting. If there is no VoIP gateway traffic, their WAN
bandwidth can be used only by best-effort traffic, not other premium traffic (for
example, Netmeeting). Enterprise Edge does not support preemption of
admitted premium streams.
•Currently packet prioritizing and priority filters apply only to outbound traffic
for specified interfaces. Inbound traffic is treated on a first in first out (FIFO)
priority.
•The maximum port numbers a user can reserve for premium traffic is 256.
The Enterprise Edge Ethernet / 802.3 interface supports IEEE 802.3 Ethernet frame
format. The Ethernet interface uses Carrier Sense Multiple Access with Collision
Detection (CSMA/CD) to manage the access to the physical media.
Enterprise Edge Ethernet interface supports the following features:
•100 BASE – TX with RJ-45 connector
•10 / 100 Auto Sense
•Full Duplex support
•Fast LAN-LAN routing
WAN Connections
This section includes information on:
•WAN overview
•Permanent WAN connections:
Using Enterprise Edge Services 37
– Frame Relay
– PPP
WAN overview
A WAN (wide area network) is a geographically dispersed data communication
network. The term WAN distinguishes a broader data communication structure
from a local area network (LAN). A WAN can be privately owned or rented, but
usually connotes the inclusion of public (shared user) networks.
Enterprise Edge includes two primary WAN links (WAN1, WAN2) and a backup
WAN dial up link (WAN3).
•The Primary WAN link is always a permanent link and it is a dedicated network
adapter. The primary link runs either Frame Relay or the PPP protocol at the
link layer.
The Enterprise Edge primary WAN connection is through a two-port card.
These two ports can be independently configured to run Frame Relay or PPP.
The card includes one serial sync port and one T1 port.
•The backup WAN link is always configured as dial-on-demand network adapter
by the router. The backup Wan link runs PPP only. Enterprise Edge provides
backup WAN connection through a V.90 modem.
The primary and backup link management is performed from Enterprise Edge.
There is a Net Link Manager running in Enterprise Edge that monitors the
primary link status and it starts the backup link when a break in primary link is
detected. Similarly, the backup link is automatically terminated when the
primary link becomes active.
Note: Net Link Manager can back up only one link, even though there are two
primary links. Net Link Manager backs up the link whose next hop address
is given to it.
•Net Link Manager manages the default route in Enterprise Edge. If a link
breaks, Net Link Manager removes all the default routes on the broken link and
adds the default route to the new link. This happens during switch over from
primary to secondary links and vice versa.
Permanent WAN Connections
This section includes information on the following topics:
•Frame Relay
•PPP
The permanent WAN connections are provided by a WAN card that supports PPP
and Frame Relay connections. Each port can be configured to run either of the
protocols independently.
The WAN cards are provided by one T1 port (with in-built CSU/DSU) and one
serial sync port or dual serial sync port versions.
The Enterprise Edge serial sync port supports the following:
•Interfaces: V.35, RS442, RS 323, X.21
•Maximum line speed:8 Mbit/sec
Frame Relay
Enterprise Edge supports Frame Relay in group mode. That is, for each physical
port (serial sync or T1 port), there is one IP address for all PVCs.
The available DLCI numbers are 0-1023, of which 16 are reserved. The maximum
number of PVC’s allowed is 1008.
For Frame Relay network, Enterprise Edge supports Frame Relay Forum standard
FRF.9 compression protocol with the standard STAC compression algorithm.
Software performs the compression and it can be enabled or disabled by using
Unified Manager.
PPP
Point-to-Point Protocol (PPP) is a protocol for communication between two
computers using a serial interface, typically a personal computer connected by
phone line to a server. For example, your Internet server provider may provide you
with a PPP connection so that the provider's server can respond to your requests,
pass them on to the Internet, and forward your requested Internet responses back to
you. PPP uses the Internet protocol (IP). PPP is sometimes considered a member of
the TCP/IP suite of protocols. Relative to the Open Systems Interconnection (OSI)
reference model, PPP provides layer 2 (data-link layer) service.
PPP is a full-duplex protocol that can be used on various physical media, including
twisted pair or fiber optic lines or satellite transmission. It uses a v ariation of High
Speed Data Link Control (HDLC) for packet encapsulation.
PPP can process synchronous as well as asynchronous communication. PPP can
share a line with other users and it has error detection.
PPP on the primary WAN link uses synchronous point-to-point communication.
Because the physical media is point-to-point, authentication attributes are not
supported in this mode.
Enterprise Edge supports PPP Compression Control Protocol (CCP) (RFC 1962)
with STAC compression algorithm.
This compression is done by software and can be enabled or disabled by using a
parameter in PPP configurations.
Backup Up WAN Connection
In Enterprise Edge, the back up WAN connection is a V.90 modem that is used as
a dial-up WAN link.
The modem is provided through an RJ-11 connector. The modem has the following
features:
•V.90 56 kbps ITU standard
•V.34 33.6 kbps ITU standard
•V.42/MNP 2-4 error control
•V.42 bis/MNP 5 data compression
•Compatible with ITU and Bell Standards from 56 kbps down to 1200 bps
Note: The modem is capable of receiving at up to 56 kbps and sending at up to
31.2 kbps. Because of FCC regulations, receiving speeds are limited to 53
kbps. The actual speed can vary, depending on factors such as current line
noise.
Enterprise Edge supports Microsoft Point-to-Point Compression (MPPC), RFC
2118 for traffic across dial-up links. The compression ratio of MPPC is
approximately 4-5 to 1.
For the remote backup, Enterprise Edge supports the following authentication
mechanisms:
•Password Authentication Protocol (PAP)
•Challenge Handshake Authentication Protocol (CHAP) is a more secure
procedure for connecting to a system than the PAP. The system attempts CHAP
before using PAP.
Software data compression on backup/dial up link is an optional feature in
Enterprise Edge. The default is set to ENABLE data compression.
Note: Remote user dial in as a RAS client is supported for administrative purposes
only.
Guidelines for Using Remote Dial In
Consider the following guidelines when using remote dial in:
•The same modem is shared between the remote dial-in for administration and
the backup WAN link. If a remote administration user is connected while the
primary link breaks, the automatic backup function does not occur.
•While using back up interface, Enterprise Edge always calls. Enterprise Edge
does not answer an incoming call from a router.
•Support for callback configuration is not provided.
Accessing system, resources, services and management settings on
Unified Mana ger
You can access Unified Manager system, resources, services and management
settings from:
•the menu
or
•the navigation tree
Configuring system settings
1. Click Group and then click Systems or Comprehensive.
2. On the navigation tree click the Enterprise Edge key and then click the
System key.
The screen displays the available Enterprise Edge item settings, resources and
configurable resource services.
3. Configure item settings using Unified Manager and the resource services from
the menu.
Scroll to see any settings that are not displayed.
System NameLets users specify the system name of the Enterprise Edge, Unified
Manager.
DescriptionShows a description of the Enterprise Edge Unified Manager installed
system.
ResourcesA configurable listing of all resources installed on the Enterprise Edge
Unified Manager system.
ServicesA configurable listing of services available for each resource on the
Enterprise Edge Unified Manager system.
The resources and resource services are:
ColumnDefinition
NameShows each configurable resource service.
StatusShows the status of each configurable resource service.
VersionShows the version of each configurable resource service.
DescriptionShows a brief description of each configurable resource service.
System name
Unified Manager often shows an example of how to format information to the right
of the box. Type the information in that format.
To enter the system name:
1. In the System Name box type the system name.
2. Press the Tab key to save your changes.
System resource services
1. In the Resource options, click the resource you want to configure.
2. In the Services options, click the resource service you want to configure.
Scroll to see any settings that are not displayed.
3. On the menu click Configuration and then click Modify Services.
The services dialog box appears.
4. From the Status list box enable or disable the resource service defined in the
Name box.
5. Click the Save button to return to Unified Manager.
6. Repeat this process to enable or disable:
•DHCP
•DNS
•Routing
•SNMP
•QoS
•VoIP Gateway
•Qos Monitor
•Web Cache
•Voice Record
•TAPI Service Provider
•Voice Service
•Alarm Service
•Voice Mail resource service
•Msc
•Telephony resource
If a resource service is not highlighted prior to prompting resource modification, an
error message appears that asks you to select a row in the table. Click the OK button
to continue.
Status fields, where available, are the accumulation of 'administrative' and
'operational' status’ of the component queried.
The three administrative statuses that can be assumed by a component are:
•Enabled: the component is enabled to operate in its normal mode, with all
normal parameters set. When the component is enabled, the component can
assume any of its operational statuses.
•Disabled: the component is disabled from operation. None of the component’s
operational statuses are valid in this state.
•Paused: the component is enabled and is running but is currently not accepting
additional service requests.
The two operational statuses that can be assumed by a component are:
•Up: the component is up and running normally
•Down: the component is down, due to some reason - normal or abnormal,
internal or external.
The Status column supports the combined list of these statuses:
•Up: This value is read-only. It indicates that the component is enabled and is
operating normally. For a component like a network interface, this means the
interface is enabled and connected to a valid link. For a service like DHCP, it
means that the service is enabled and is running normally.
•When the current status is 'Up', setting it to 'Enabled' or 'Continue' where
available, is a no-operation. Setting it to 'Disabled' disables the service, by
shutting it down and then disabling it. Where available, setting it to 'Paused'
pauses the service.
•Down: This value is read-only. This value indicates that the user has enabled the
component, and the component is unable to operate in an 'Up' state because of
normal or abnormal, internal or external errors. For example, if a network
interface is not in an 'Up' state because of no connection to an actual physical
link, it is a normal, external error. If a service like DHCP service is not in an 'Up'
state because of internal errors, it is an abnormal, internal error.
•When the current status is 'Down' setting it to 'Enabled' attempts to bring it to
'Up' state again. As a result it may stay at a 'Down' state. Setting it to 'Disabled'
disables the service. Where available, setting it to a 'Paused' or continued state
fail as the service is not yet running.
•Enabled: This value is write-only. This value never appears when read. For a
service that is enabled, one of its operational statuses (that is, Up or Down)
appears when its Status field is read.
•When this value is set, it indicates that the user wants to enable the
corresponding component and bring it to an 'Up' state. It is probable that the first
happens. The second action depends on the component. For a network interface,
the 'Up' state does not happen unless user connects a link to the interface. For a
service this may not happen only if the system encounters an error of some kind
during the requested action.
•Disabled: This value can be either read or set. When read, this indi cates that the
component is disabled from operation. When set, it indicates the same, in
addition to taking the component to a 'Down' state before disabling.
•Paused: This value can be either read or set. When read, this indicates that the
service is enabled and is given the command to pause. When set, it indicates the
same, pausing the service further.
•Continue: This value can only be set. It can be set only when the service in a
Paused state. It resumes paused service.
System performance graphs and tables
To access the system performance graphs and tables:
1. On the menu click Performance and then click System CPU Usage Graph.
The System CPU Usage Graph appears.
2. On the menu click Performance and then click System CPU Usage Table.
The System CPU Usage Table appears.
1. Click the System navigation key to expand the navigation tree.
The System Settings dialog box appears.
Clicking the System navigation key expands the navigation tree but doesn’t
display the summary of configurable Identification resources.
The System Settings are:
SettingDefinition
NameLets users specify the name for the Enterprise Edge system. The Enterprise
Edge system must have a unique name in the connected network (LAN or
WAN) so that no two Enterprise Edge servers that can reach each other
through IP network do not have the same name. The name mu st b e le ss than
15 characters in length, cannot contain special characters like “/;,” etc.
DateLets users set the current date for the Enterprise Edge system. Because the
value for the date changes, save the changes as soon as the new date is
entered.
TimeLets users set the current time for the Enterprise Edge system. Because the
value for the time keeps changing, save the ch anges as s oon as the n ew time
is entered. Use the 24-hour format to set the date. The seconds field is
optional.
2. On the navigation tree click Identification to view the available system
settings to configure.
The System Identification dialog box appears.
The columns that are displayed when the system, resources, services, or
management settings are activated are:
ColumnDefinition
NameThe name column lists the available configurable resources.
StatusThe status column lists the operating status of each configurable resource.
VersionThe version column lists the version of each configurable resource.
DescriptionThe description column gives a brief description of the interface for each
configurable resource.
LAN
You configure LAN resource settings from Unified Manager.
If your Enterprise Edge server has more than one LAN interface, multiple items
appear under LAN resources. To configure other LAN interfaces, follow the
instructions given here for LAN1.Choose LAN from the navigation tree to view the
available LAN resources to configure.
Note: Clicking the LAN navigation key expands the navigation tree, but
doesn’t display the summary of configurable LAN resources.
4. Click the LAN navigation key to expand the navigation tree.
5. On the navigation tree click LAN1.
Clicking the LAN1 navigation key causes the key to disappear. You must
click LAN1.
The LAN Summary screen appears.
The LAN Summary settings are:.
SettingDefinition
IP AddressLets users specify the IP address of the LAN interface in a valid dot format.
Type the address in the following format: 10.10.10.1.
The value for this field is valid only if the LAN interface is enabled.
SubNet MaskLets users specify the subnet mask of the LAN interface. Type the data in
the following dot format 255.255.255.0.
Physical AddressLets users to view the physical address of the LAN interface.
If the IP Address or subnet mask of the LAN interfaces changes, a DHCP
scope associated with the LAN interface is created in the DHCP server
running on the Enterprise Edge server. This scope contains all necessary
parameters to the clients of the DHCP server configured so that they use
Enterprise Edge as their default gateway and a WINS server. The scope also
contains default parameters for the range of the addresses, based on the
address of the Enterprise Edge interface and subnet mask. Navigate through
the services screen in the user interface to see DHCP settings for the scope.
DescriptionLets users view a description of the network interface card supporting the
LAN interface.
VersionLets users view the version indicator of the LAN interface.
SpeedLets users view the speed of the connection to the LAN interface.
The value for this field is valid only if the LAN interface is enabled.
You configure WAN resource settings from Unified Manager.
WAN Interfaces have names like WAN1 and WAN2. If your Enterprise Edge
server has a permanent WAN card, WAN1 and WAN2 are interfaces from this card.
They can run Frame Relay or PPP on a permanent WAN Link operating at T1
speed. Click on these interfaces to see their description.
If your Enterprise Edge server also contains a modem card with dial up interfaces,
they appear as WAN3, WAN4 and so on. Click on these interfaces to see their
description. If your Enterprise Edge server does not have a WAN card, dial-up
interfaces appear as WAN1, WAN2 and so on.
The configurable parameters and options are different for permanent WAN links
and for dial-up WAN links. In this document, it is assumed that WAN1 and WAN2
are permanent WAN links and WAN3 and others, are be dial-up interfaces.
To view the WAN primary links
1. Click WAN to view the available WAN resources to configure.
2. Click the WAN navigation key to expand the navigation tree.
Clicking the WAN navigation key expands the navigation tree but doesn’t
display the summary of configurable WAN resources.
3. On the navigation tree, click WAN1 or WAN2.
Clicking the WAN1 or WAN2 navigation key causes the key to disappear.
You must click WAN1 or WAN2.
The screen displays the WAN Summary, WAN Line Parameters, WAN Frame
Relay Parameters, WAN PPP Parameters, and PVC Congestion Control
settings.
Note: The WAN Frame Relay Parameters do not appear unless frame relay is
chosen as your link protocol in the WAN Summary. To display the
WAN frame relay parameters, from the Link Protocol list box select Frame Relay. Press the Tab key to update the screen. A configurable
WAN Frame Relay Parameters dialog does not appear unless the
current link protocol is PPP.
4. Scroll to view any settings that are not displayed.
5. Configure the WAN Summary, WAN Line Parameters, WAN Frame Relay
Parameters and WAN PPP Parameters screen from Unified Manager.
Configure the PVC congestion control screen using the menu.
If your current link protocol is Frame Relay, you may have to configure WAN
Frame Relay parameters and PVC Congestion Control entries. If your current link
protocol is PPP, you may have to configure WAN PPP Parameters.
If the WAN port you are configuring is a T1 Port, you may have to configure WAN
Line Parameters. If the port you are configuring is a synchronous (Sync) port, W AN
Link Parameters have no effect, and are ignored. See the description of the port in
WAN Summary section to see which port you are configuring.
IP AddressLets users specify the IP address of the WAN interface in a valid dot format.
Type the data in the following dot format: 10.10.10.1.
SubNet MaskLets users specify the subnet mask in a valid dot format of the WAN interface.
Type the data in the following dot format 255.255.255.0.
Physical Address Shows the physical address of the WAN interface.
DescriptionShows the description of the network interface card that supports the WAN
interface.
VersionShows the version indicator of the WAN interface.
SpeedShows the operational speed of the WAN interface.
StatusShows the current resource status of the WAN interface.
The possible states are:
Up: the resource is operational.
Down: the resource is not operational.
Link ProtocolLets users specify PPP or frame relay protocol.
If you change the link protocol, the configuration screen changes to include
fields corresponding to the link protocol you choose. To ensure proper
operation, always refresh the page by clicking
Compression
Speed
Frame SizeLets users specify the maximum frame size for the layer-2 packet carried on
Lets users specify fast, medium, normal, slow, or no data compression
configuration.
this port.
View
and then
Refresh
.
To modify the configuration of the WAN1 or WAN2 summary screen:
6. In the IP Address box type the IP address.
7. In the SubNet Mask box type the subnet mask.
8. From the Link Protocol list box choose Frame Relay or PPP.
Note: If you choose Frame Relay, press the Tab key to update the screen. A
configurable WAN Frame Relay Parameters screen appears.
9. From the Compression Speed list box select the compression speed.
Channel RateLets users set the data rate for each of the DS0 channels in the T1 line.
Clock SourceLets users set an internal or external T1 clock source.
Frame TypeLets users set the type of framing to be adopted in the T1 line.
You can select either SF(D4) or ESF for frame type. SF(D4) transmits
superframes consisting of 12 individual frames. ESF transmits superframes
consisting of 24 individual D4 frames and provides enhanced signaling and
synchronization.
ESF lets you testing the digital line while it is in use.
Always use the frame type that the equipment at the receiving end expects.
Line CodingLets users set the type of encoding used in the T1 line.
You can select either B8ZS or AMI for this parameter. B8ZS (Bipolar with 8
Zero Substitution) line coding replaces a block of eight consecutive binary zeros
with an 8-bit B8ZS code containing bipolar violations in the fourth and seventh
bit positions of the substituted code. In the receiving direction, the B8ZS code is
detected and replaced with eight consecutive binary zeros.
AMI line coding is also bipolar: a binary zero is transmitted as zero volts, and a
binary 1 is transmitted as either a positive or negative pulse, opposite in polarity
to the previous pulse.
Always use the line coding method that the equipment at the receiving end
expects.
Line PolarityLets users set normal or inverted line polarity in the T1 line. The option inverted
is meaningful only if LineCoding is AMI.
Pulse DensityLets users control whether the DSU/CSU maintains the minimum level of 1s on
the line for AMI encoding.
Channel ListLets users create a list of channels used in the T1 line.
You can specify multiple channel numbers in a comma-separated list. Each item
in the list can contain a range of channel numbers, with the limits of the range
separated by a hyphen character. For example, this is a valid value for channel
list: 3,5,6,10-15,18,20-23. If you use all of the channels, specify it by using the
string All.
LMI TypeLets users set the type of link management protocol used on this link.
This value must match the corresponding value set in the Frame Relay
service provider’s switch. Permitted values are ANSI, LMI, and
CCITT. The default setting is ANSI.
Polling IntervalLets users set a value, in seconds, as an interval between LMI status
inquiry messages. This v alue must match the corr espondi ng value set in
the Frame Relay provider’s switch. Permitted values are between 5-30
(in seconds). The default setting is 10.
Full Enquiry IntervalLets users set the maximum number of LMI Status Enquiry messages
sent before sending a Full Status Enquiry request. This value must
match the corresponding value set in the Frame Relay provider’s
switch. Permitted values are between 1 and 255 (in seconds). The
default setting is 6.
Error ThresholdLets users set the maximum number of consecutive failures permitted
in LMI Status Enquiry before marking the link non-operational. It is
also the number of successful consecutive LMI Status Enquiry
messages that must be received before marking a link as operational.
Permitted values are between 0 and MAXINT. The default setting is 3.
Monitored EventsLets users s et the number of even ts sampled for making decis ions about
the error threshold. Set the number higher than the values set in the
error threshold. Permitted values are a number between 0 and
MAXINT. The default setting is 4.
DS CodeLets users set the differentiated services code (DSCode) recognized by
the frame relay driver for prioritization. This value is used as a mask
value. When an IP packet is sent down, the frame-relay driver checks if
the packet's DSCode field (known as TOS byte in earlier documents)
has any of the bits specified in this field set (a bitwise AND operation is
performed between this field's value and the DSCode field of the IP
packet and the result is checked for 0). If any of the bits is set (result is
non-zero), the frame relay network is signaled to handle this packet
with priority by clearing the 'D/E' (discard eligibility) bit in the frame
relay packet header. If none of the bits specified in this field are set in
the IP packet header, 'D/E' bit is set in the frame-relay packet header,
marking the packet as a likely candidate for packet drop in case of
congestion in the frame relay network.
This field's value carries the same semantics as the 'differentiated
services codepoint' discussed in RFC2474. The least significant two
bits are ignored.
Compression Enabled
PVCs
Lists PVCs on which compression is enabled. If the compression field
is Disabled, the field does not have any meaning. If the compression
level Enabled, compression and decompression are performed on the
data going to and coming from the PVCs in this list.
The value can be a comma-separated list of DLCI numbers. You can
specify a range of DLCIs b y specify ing th e lower and u pper bound aries
by a hyphen. You can mix individual numbers and ranges.
Access RateLets users set, in kbps, the maximum access rate on the interface
running frame-relay. The frame-relay congestion control engine uses
this value to limit or shape traffic. Specify a value computed using the
T1 channels available for data communication on the port attached to
this interface and their data rates.
To modify the configuration of the WAN Frame Relay Parameters:
1. Scroll to locate the WAN Frame Relay Parameters screen.
2. From the LMI Type list box select the LMI type.
3. In the Polling Interval box type the polling interval in seconds.
4. In the Full Enquiry Interval box type the full enquiry interval.
5. In the Error Threshold box type the error threshold.
6. In the Monitored Events box type the appropriate monitored events.
7. In the DS Code box type the DS code.
8. In the Compression Enabled PVCs box type the compression.
9. In the Access Rate box type the access rate in kbps.
Entry (CC#)Uniquely identifies the congestion control entry on the interface. Use
the format specified for the entry identifier. It must include the prefix
'CC' followed by a unique number in the table. For example, 'CC2' is a
valid number. If you don't use consecutive numbers while adding the
entry, the system adjusts them to be consecutive. If you specify an
existing entry while adding an entry, the existing entry is modified with
new values. While modifying an entry, the name can't be changed.
DLCILets users set the DLCI number for the PVC to be congestion
controlled. If a DLCI is not configured, it is not congestion controlled.
Enterprise Edge uses one-second intervals to measure this parameter.
CIRLets users set, in kbits, the carrier guarantees the router transmits over a
specified time interval when congestion is not present.
Enterprise Edge uses one-second intervals to measure this parameter.
Committed Burst (bC)Lets users to define the number, in kbits, of bits the router transmits
over a specified time interval if congestion is present. Usually this value
is set for 1/4 the value of the CIR.
Enterprise Edge uses one-second intervals to measure this parameter.
Excess Burst (Be)Combined with the committed burst rate, lets users set, in kbits, the
maximum number of bits the router transmits over a specified time
interval if there is no congestion. Both Be and bC must be less than or
equal to the line speed.
To add PVC congestion control:
1. On the menu click Configuration and then click Add PVC Congestion Control.
The PVC Congestion Control dialog box appears.
If an entry range has not been selected an error message appears.
2. In the Entry (CC#) box type the entry that looks like “CCxx” where “xx” is a
unique integer.
WAN3 and WAN4 are dial up interfaces that are configured according to the V.90
modem in the Enterprise Edge server. You must click WAN3 to see its description.
Dial up WAN Links always use PPP as link-layer protocol. They must be connected
to PPP capable RAS Servers that can run RIP or can accept static routes for proper
operation.
1. On the navigation tree, click WAN3.
Clicking the WAN3 navigation key causes the key to disappear. You must
choose WAN3.
The WAN Summary, WAN Link Parameters, and WAN Access Parameters
screen appears.
2. Scroll to see any settings that are not displayed.
1. From the IP Address list box select the appropriate IP address assignment or
type a new value.
2. From the Status list box enable or disable the connection to the backup link.
IP AddressLets users set the IP address of the modem interf ace in a valid do t format when
it connects.
Users can set a fixed IP Address for the dial-up interface. If a fixed address is
specified, it is used by Enterprise Edge to connect to the receiving end.
Instead, users can choose RemoteAssigned to indicate that Enterprise Edge
must obtain an IP address from the remote end and use it. The address
obtained depends on the RAS server that the Enterprise Edge server connects
to.
DescriptionShows a description for the subsystem that is encapsulated by the DLL.
VersionShows the version for the subsystem that is encapsulated by the DLL.
StatusLets users set the modem interface resource status.
The possible states are:
Up: the auto WAN backup service is enabled and the d ial-up link is cu rrently
connected.
Down: the auto WAN backup service is enabled and the dial-up link is
currently
disconnected.
Enabled: the interface is enabled for use by the auto-backup server.
Disabled: the auto WAN backup service is disabled.
Telephone NumberLets users specify a telephone number to be used to connect using
the modem interface. If needed, include area codes, if any, and all
necessary digits to dial an external number.
Alternate Telephone
Number
Connect RateLets users specify the initial speed (in bits per second) for the
Dial RetriesLets users specify the number of tries the system attempts to make a
Dial IntervalLets users specify the interval, in seconds, between successive
Speaker ModeLets users enable or disable the speaker during initial link
IP Header CompressionLets users enable or disable IP header com pression. To function, the
Software CompressionLets users enable or disable data compression in the software,
Hardware CompressionLets users enable or disable data compression in the hardware
PPP LCP ExtensionsLets users specify whether or not to enable or disable PPP LCP
Lets users specify an alternate number to be used to connect using
the modem interface. Include area codes, if any, and all necessary
digits to dial an external number.
modem to connect. Set to the maximum permissible value for best
results. Permitted values: 57600, 38400, 19200, 9600, 4800. Note:
This is the initial rate, actual rate is always negotiated.
link operational before marking it non-operational. A positive
number must be used.
attempts to make a link operational.
establishment.
receiving end must utilize this feature to work.
instead of the modem. For dial-up connections, Unified Manager
uses Microstate Point-to-Point Compressio n algorithm (MPPC).
instead of the software.
extensions that include Time-Remaining, Identification, and
Callback features. The Callback feature is not supported even if
LCP extension is enabled.
1. Scroll to see the WAN Link Parameters settings.
AuthenticationLets users specify the authentication type for the link.
Users can choose AllowClearText or EncryptedOnly. If
EncryptedOnly is selected, only encrypted authentication such as
CHAP is used on this interface during PPP authentication protocol. If
AllowClearText is selected, CHAP is used first and if the receiving
end of the link declines, PAP is used to authenticate the link user.
Two Way Authentication Lets users enable or disable link authentication in both directions.
User ID (name password) Lets users specify a user name and a password that the link uses to
authenticate itself while dialing out to another router.
1. Scroll to find the WAN Access Parameters.
2. From the Authentication list box select the authentication type.
3. From the Two Way Authentication list box select the two-way
authentication type.
4. In the User ID (name password) box type the user ID, separating the user
name and password with a space.
5. Press the Tab key to save the settings.
6. Click the WAN navigation key to close the navigation tree.
1. On the navigation tree click DHCP to view the available resources to
configure.
Click the DHCP navigation key to expand the navigation tree, but clicking on
the key doesn’t display the summary of configurable DHCP services. You
must click DHCP.
The DHCP Global Options and Summary settings appear.
2. Scroll to view any settings not displayed on Unified Manager.
The settings in the DHCP Global Options and DHCP Summary screen are:
SettingDefinition
Domain NameLets users specify a domain name that is passed to the client when Enterprise
Edge responds to a client’s DHCP requests.
This setting is automatically set to 'Domain' field in 'DNS Summary' page.
This means that all the DHCP clients of an Enterprise Edge server are in the
same DNS domain as the Enterprise Edge server. This is also correct since
Enterprise Edge runs only a DNS cache and does not introduce another DNS
zone.
Change the Domain setting in the DNS Summary to make a change in this
setting. Occasionally you can change the value of Domain in DHCP. If you
do, first make any changes to Domain in the DNS Summary to avoid
overwriting your changes.
WINS Node
Type
DescriptionShows a description of the Enterprise Edge server.
VersionShows the version number of the Enterprise Edge server.
StatusLets users enable or disable the DHCP server. When disabled, clients need to
Lets users specify a clients WINS node type.
Enterprise Edge automatically sets this value to 8 (indicating H-Node) if the
IP Address is changed on any of the LAN interfaces. All DHCP clients of
Enterprise Edge are set to h-node type when they get their IP properties from
Enterprise Edge. This setting configures the DHCP client PCs to use p-node
name resolution before resor ting to b-n ode name res olution, which is effi cient
when there is a WINS server configur ed for the network. Enter prise Edge als o
includes a WINS server.
Other options available for this field are:
1: indicates a b-node that uses broadcast mechanism for NetBIOS name
resolution
2: indicates a p-node that uses point-to-point mechanism involving a WINS
Server for NetBIOS name resolution
4: indicates a m-node that first uses broadcast and then point-to-point
mechanism for NetBIOS name resolution.
be assigned static IP addresses.
3. In the Domain Name box type the appropriate domain name.
This is set in Enterprise Edge configuration. Use caution if you change it.
4. In the WINS Node Type box type the appropriate WINS Node Type.
This is set in Enterprise Edge configuration. Use caution if you change it.
5. From the Status list box select either enable or disable.
1. Click the DHCP navigation key to expand the navigation tree.
2. On the Navigation tree click LAN1.
Clicking the LAN1 navigation key causes the key to disappear. You must
choose LAN1 to display the configurable DHCP LAN1 services. If your
Enterprise Edge system has multiple LAN interfaces, if is possible that you
see multiple DHCP Scopes under DHCP. They are be named LAN1, LAN2.
This section describes configuring DHCP scope for LAN1. Follow the same
instructions to configure any of the parameters under scope for LAN2.
The screen displays the LAN Scope Specific Options, Address Range, and
Excluded Address Range dialog box.
3. Scroll to view settings not displayed on Unified Manager.
4. You configure the scope-specific options dialog box from Unified Manager.
The LAN address range and the LAN excluded address services screen is
configured through the menu.
Note: If the IP Address or subnet mask for a LAN interface is changed, the
corresponding DHCP scope is created or modified for the interface.
This operation also involves setting default values for some
parameters. By default, Enterprise Edge sets the IP Address of
corresponding LAN interface to DNS Server, WINS Server, Default
Gateway options of the scope. It also sets the lease time to 3 days,
creates a range of addresses for the scope. If the IP Address of the
LAN interface is in the lower half of the subnet, the address range set
for the scope includes all the address above the LAN interface address.
If the IP Address of the LAN interface is in the upper half of the
subnet, the address range set for the scope includes all the address
below the LAN interface address. By default, the scope is enabled.
The DHCP LAN1 Scope Specific Options, Address Range and Excluded Address
Range settings are:
SettingDefinition
DNS ServerLets users specify the clients’ DNS server.
The value for this parameter is automatically assigned by Enterprise Edge's
auto-configuration system. If the IP Address or subnet mask for the
corresponding LAN interface is changed, this value gets overwritten. Use
caution when changing this value.
WINS ServerLets users specify the client’s WINS server.
The value for this parameter is automatically assigned by Enterprise Edge's
auto-configuration system. If the IP Address or subnet mask for the
corresponding LAN interface is changed, this value gets overwritten. Use
caution when changing this value.
Default GatewayLets users specify the client’s default next-hop router.
The value for this parameter is automatically assigned by Enterprise Edge's
auto-configuration system. If the IP Address or subnet mask for the
corresponding LAN interface is changed, this value gets overwritten. Use
caution when changing this value.
Lease TimeLets users specify the time, in seconds, from an address assignment until
the client’s lease expires.
Scope StatusLets users enable or disable the scope.
Address RangeLets users specify the valid IP addresses that are assigned to DHCP clients.
Excluded AddressLets users specify IP addresses that are not available to DHCP clients.
1. On the menu click Configuration and then click Add Address Range.
The Address Range dialog box appears.
2. In the Range box type the range.
The range field uniquely identifies a range value in the scope. The value for
this field is used as key, and must follow certain conventions. It must always
start with the prefix 'R' followed by a unique number identifying the range in
the table. For example, 'R2' is a valid name.While adding, specify nonrecurring values for the unique number. While adding, if you specify an
existing range name, it modifies the existing range. Using non-sequential
numbers results in automatic reassignment of sequential numbers. When you
modify a range, you can't change the range name. The range name does not
have any significance other than identifying an entry.
3. In the Start Address box type the start address.
4. In the End Address box type the end address.
Scroll to see any fields that are not displayed.
Make sure the start address and end address are in the same subnet.
5. Click the Save button to return to Unified Manager.
To delete address ranges:
1. Click an address in the Address Range table.
2. On the menu click Configuration and then click Delete Address Ranges.
A message appears asking you to confirm the deletion.
3. Click the Yes button to confirm the deletion and return to Unified Manager.
Note: Deleting or modifying an IP Address range removes any excluded
addresses that are completely contained in the original address range
value.
1. Click an excluded address in the Excluded Address Range table.
2. On the menu click Configuration and then click Modify Excluded Address Ranges.
The Excluded Address Range dialog box appears.
3. In any box that requires modification type the necessary changes.
4. Click the Save button to return to Unified Manager.
To add excluded address ranges:
1. On the menu click Configuration and then click Add Excluded Address Range.
The Excluded Address Range dialog box appears.
2. In the Range box type the range.
Note: The range field uniquely identifies an excluded range value in the
scope. The value for this field is used as key, and must follow certain
conventions. It must always start with the prefix 'E' followed by a
unique number identifying the range in the table. For example, 'E2' is a
valid name. While adding, specify non-recurring values for the unique
number. While adding, if you specify an existing excluded range
name, it modifies the existing range. Using non-sequential numbers
results in automatic reassignment of sequential numbers. When you
modify an excluded range, you can't change the range name. The
excluded range name does not have any significance, other than
uniquely identifying an entry.
3. In the Start Address box type the start address.
4. In on the End Address box type the end address.
Scroll to see any fields that are not displayed.
Note: Make sure the start address and end address are in the same subnet,
and an excluded address range is completely contained in an IP
address range specified for the subnet.
5. Click the Save button to return to Unified Manager.
1. On the navigation tree click DNS.
Clicking the DNS navigation key causes the key to disappear. You must click
DNS to view the available configurable DNS services.
The DNS Summary screen appears.
The DNS Summary settings are:
SettingDefinition
DescriptionLets users view the description of the server in cache mode.
VersionLets users view the version of the software interface.
StatusLets users enable or disable the DNS cache proxy in Enterprise Edge.
DomainLets users specify the domain name that Enterprise Edge and its DHCP clients
uses. When modified, contents of this setting are automatically copied to
Domain Name global options (O15) under DHCP.
Primary ServerLets users specify the primary server IP address in a valid dot format. More
than one address can be specified separated by a space; DNS cache uses them
in the specified order to resolve names.
Forward Timeout Lets users specify the time-out, in seconds, used in r esolving queries us ing the
4. In the Primary Server box type the primary server.
5. In the Forward Timeout box type the forward timeout.
6. Press the Tab key to save the settings.
Routing
To configure routing services settings:
1. On the Navigation Tree click Routing to view the services to configure.
Clicking the Routing navigation key expands the navigation tree but doesn’t
display the summary of configurable routing services. You must click
Routing.
The Summary and Global Settings screen appears.
The LAN1 Summary and RIP Parameters Routing settings are:
SettingsDefinition
DescriptionShows a description of the router.
VersionShows the version of the router.
StatusLets users enable or disable the router.
Packet FilteringLets users enable or disable packet filtering.
When the system comes up the first time, this value is N/A, indicating that the
Management system cannot retrieve pertinent information. Set it to Disabled
or Enabled and valid values are displayed. Disabling packet filtering here
disables it on all interfaces. The router performs better when packet captur ing
is disabled.
RIP Log LevelLets users specify a log-level for the RIP routing protocol manager:
maximum generates the maximum log
warnings also, generates a log for warning conditions too
errors only, generates log errors only (for use during normal operations)
disabled disables logging (not recommended).
Triggered Update
Interval
Lets users specify the minimum interval between sending triggered updates.
1. From the Status list box enable or disable the router.
2. From the Packet Filtering list box enable or disable packet filtering.
3. From the RIP Log Level list box select the RIP log level.
4. In the Triggered Update Interval box type the triggered update interval.
5. Press the TAB key to save the settings.
LAN Routing
This section describes the instructions to configure LAN1 interfaces for routing. If
there are other existing LAN or WAN interfaces, they also appear in Routing.
Follow the same instructions to configure them.
1. On the navigation tree click the Routing navigation key to expand the menu.
2. On the navigation tree click LAN1.
Clicking the LAN1 navigation key causes the key to disappear. You must click
LAN1 to view the available services to configure.
The Summary, Input Filter, Output Filter, and Static Route screen appears.
Note: The RIP Parameters screen is not displayed unless you choose RIP as
your routing protocol in the LAN1 summary screen. To display the
RIP parameters, click the Routing Protocol list box and choose RIP.
Then press the Tab key to update the screen. A configurable RIP
screen appears.
You configure the Routing summary screen from Unified Manager.
The Input Filter, Output Filter, and Static Route screen is configured through
The LAN1 Routing Services Summary and RIP Parameters settings are:
SettingDefinition
Routing Protocol Lets users select the Routing protocol to run over the interface. Select RIP to
run RIP protocol or select NONE to disable running any routing protocol. If
RIP is selected, interface-specific RIP parameters appear in the bottom of the
screen. You can configure other RIP parameters on this interface
Input Filter
Action
Output Filter
Action
MetricSpecifies the associated metric value for the routes through this interface.
Routing Table
Update Mode
Route
Announcement
Type
Route Accept
Type
Route Expiration
Interval
Route Removal
Interval
Determines what action is performed for the packets that match the filter
criteria. You can either forward them to upper layer, possibly for further
routing or drop them.
You can select the action only if you have set any of the inpu t or output filter s.
Otherwise, they show up as N/A and you can't modify them.
Determines what action is performed for the packets that match the filter
criteria. You can either forward them to the next hop or drop them.
You can select the action only if you have set any of the inpu t or output filter s.
Otherwise, they show up as N/A and you can't modify them.
Metric values of all routes learned through this interface are incremented by
this value. The final value used in making routing decisions is forwarded to
other routes through RIP updates.
Lets users specify the routing table update mode for the interface. In On
Demand mode, the router sends its table when requested by another
established router. In Periodic mode, the router sends its table to other
established router at regular intervals.
Lets users specify the route-announcement type for the specified interface.
The choices are:
Disabled: sending RIP packets is disabled on this interface. This requires the
other routers in the subnet have static routes configured to access the
Enterprise Edge server.
RIP 1: sends RIP v1 packets in broadcast only.
RIP 1 Compatible: sends RIP v1 and RIP v2 packets in broadcast. Use this for
a mixed environment of RIP v1 and RIP v2
RIP 2: sends RIP v2 packets i n multicas t only. Use t his only i f all other routers
connected to the Enterprise Edge server are RIP v2 capable.
Lets users choose to accept announcements in either RIP1, RIP2, or both
formats.
The choices are:
Disabled: accepting RIP packets is disabled. If this choice is selected, the user
is prompted to create static routing entries in the Enterprise Edge server to
access other networks connected through this interface. This method is
preferable if you want to keep the routing table small in the Enterprise Edge
server.
RIP 1: accepts only RIP v1 packets
RIP 1 Compatible: accepts packets of both RIP v1 and RIP v2
RIP 2: accepts only RIP v2 packets.
Lets users specify, in seconds, the time interval to mark an established router
that has not updated its table eligible for removal.
Lets users specify, in seconds, the time interval between route expires and
when it is removed from the routing table.
Lets users specify, in seconds, the time interval between route
announcements.
interface. This helps identify route packets while debugging routing problems
using a network sniffer.
The choices are:
Actual: the actual, original RIP updates are performed over this interface. All
the routes learned through this interface are also included as is in the RIP
updates sent over this interface. This leads to mutually deceiving route
updates that require multiple routing updates that is termed 'counting to
infinity' in RIP terms.
Split: in the routing updates sent over this interface, router does not include
the routes learned over this interface. This mode performs better than Actual,
but still requires significant amount of time to converge routes. It requires all
routes corresponding to an unreachable ne twork exp ire befor e removing them
from the routing table
Poison Reverse: in the routing updates sent over this interface, the router
includes the routes learned over this interface, but 'poisoned metrics'. All
metric values are set to RIP infinity (16) for the routes learned through this
interface. This results in the fastest convergence.
Lets users enable triggered updates, or immediate route update
announcements whenever a metric or other parameter changes in the route
table entries.
If triggered updates are enabled, the changes are gathered for the interval
specified in the global parameter Triggered Update Interval and then s ent over
this interface. Triggered updates results in more frequent, smaller RIP
updates.
Lets users enable or disable announcing default routes in incoming route
announcements. Use caution when enabling this feature as improper
configuration causes a loss of network connectivity. Default routes are always
set statically on the router.
Lets users enable or disable accepting incoming default routes.
Set default routes as static routes. If you are run Net Link Manager to
automatically backup primary WAN link using a dial-up link, it manages the
default routes and the default routes that you add are non-operational as soon
as a link breaks or comes up.
To modify the configuration of the LAN1 routing summary screen:
1. From the Routing Protocol list box select NONE or RIP.
If you choose RIP, press the Tab key to update the screen.
A configurable RIP Parameters screen appears.
2. From the Input Filter Action list box select the input filter action.
3. From the Output Filter Action list box select the output filter action.
4. Press the Tab key to save the settings.
This operation fails if filters have not been added to the interface.
Input filterSpecifies the filter name and identifies an individual input filter on the
specified interface. Its value must fo llow certain conven tions. I t must have the
prefix IF followed by a unique number that identifies the input filter on the
interface. For example, IF2 is a valid value. While adding, specify nonrecurring values for the unique number.
While adding, if you specify an existing filter name, it modifies the existing
filter. Using non-sequential numbers results in automatic reass ignm ent of
sequential numbers. While modifying a f ilter, yo u can 't chan ge th e nam e. Th e
filter name does not have any significance other than to identify an entry.
Output filterSpecifies the filter name and uniquely identifies an individual output filter on
the specified interface. Its value must follow certain conventions. It must have
the prefix OF followed by a unique number that identifies the input filter on
the interface. For example, OF2 is a valid value. While adding, specify nonrecurring values for the unique number.
While adding, if you specify an existing filter name, it modifies the existing
filter. Using non-sequential numbers results in automatic reass ignm ent of
sequential numbers. While modifying a f ilter, yo u can 't chan ge th e nam e. Th e
filter name does not have any significance other than to identify an entry.
Source addressLets users specify the source IP address in a valid dot format.
If you don't want to match the source address field in your filter, leave this
setting and the source mask empty.
Source maskLets users specify the source mask for the IP address in a valid dot format.
If you specify a source address, you must specify the source mask. If you
don’t specify the source address, you must not specify the source mask. The
source address and source mask must match. Bitwise, the source address and
the source mask must be equal to the source address.
Destination
address
Destination mask Lets users specify the mask of the destination address in a valid dot format.
Lets users specify the destination IP address in a valid dot format.
If you are specifying a filter, this field specifies the destination address of the
IP packet that matches the filter. If you don't want to match the destination
address, leave this field empty.
If you are specifying a static route, this field must not be empty. It must be a
valid network or host address.The destination mask must match the address
specified in this setting.
If you specify a destination address, you must specify a destination mask. If
you don’t specify the destination address, you must not specify the source
mask. The destination address and destination mask must match; i.e. bitwise
AND of destination address and destination mask should be equal to
destination address.
ProtocolLets users specif y the protocol to match the filter.
The choices are:
TCP: look for the TCP protocol packets. You can specify source and
destination service port s in ot her f ield s. If you d on't sp eci fy any por t n umber s
all packets that match this protocol and other criteria, if any, match the filter.
UDP: look for UDP protocol packets. You can further specify source and
destination service port s in ot her f ield s. If you d on't sp eci fy any por t n umber s
all packets that match this protocol and other criteria, if any, match the filter.
ICMP: look for ICMP protocol packets. You can further specify the ICMP
message types and ICMP codes in ot her f ields. If y ou don 't specify any ICMP
types or codes all packets that match this protocol and other criteria, if any,
match the filter.
Source port/
ICMP type
Static RouteSpecifies the static route name and is used as a key to uniquely identify an
Next Hop Router Lets users specify the IP address in a valid dot format for the next hop router.
Metric ValueLets users specify the metric value associated with the interface. The metric is
If the protocol chosen is UDP or TCP, this lets users specify the source port to
match the filter. If the protocol chosen is ICMP, this field specifies the ICMP
code value to look for in the packet to match the filter.
Destination Port/ICMP Code: If the protocol chosen is UDP or TCP, this lets
users specify the additional destination service port to match the filter. If the
protocol chosen is ICMP, this field can contain the optional ICMP code.
individual static route on the specified interface. Its value must follow certain
conventions. It must have the prefix SR followed by a unique number that
identifies this static route on this interface. For example, SR2 is a valid value.
While adding, specify non-recurring values for the unique number.
While adding, if you specify an existing static route name, it modifies the
existing static route. Using non-sequential numbers results in automatic
reassignment of sequent ial numb ers. Wh ile modi fying a s tatic ro ute, you can't
change the name. The static route name does not have any significance other
than to identify an entry.
added to the hop count of the routes received through the interface.
Note: If input and output filters are not defined for the LAN1 interface,
modifying input filter action or output filter action in the summary
causes an error message.
1. Click a static route in the Static Route table.
2. On the menu, click Configuration and then click Delete Static Route.
3. Follow the steps for deleting output filters.
WAN Routing
To configure WAN routing services:
1. Click the Routing navigation key to expand the navigation tree.
2. On the navigation tree, click WAN1 or WAN2.
Clicking the WAN1 or WAN2 navigation key causes the key to disappear.
You must click WAN1 or WAN2 to view the configurable WAN resources.
The Summary, RIP Parameters, Input Filter, Output Filter, and Static Route
screen appears.
Note: The RIP Parameters screen is not displayed unless RIP is chosen as
your routing protocol in the WAN summary screen. To display the RIP
parameters, click the Routing Protocol list box and select RIP. Then
press the Tab key to update the screen. A configurable RIP screen
appears.
3. Use the scroll bars to locate any fields that are not displayed.
4. Configure the WAN1 or WAN2 routing summary and RIP Parameters screen
from Unified Manager.
Configure the input Filter, output filter, and static route dialog box from the
menu.