Professional Documents
Culture Documents
Systems
MDRS 155
OSPF Functions and Commands
MDRS 155 S Release 4.3
MDRS 155 E Release 2.3 SR1
05PHA00065AEY CUA
Version: 0002; 07.2004
Contents
Contents
1
1.2
IP router ................................................................................................................................ 1-1
1.2.1
Brief description .............................................................................................................. 1-1
1.2.2
Router features ............................................................................................................... 1-2
1.2.3
Configuration................................................................................................................... 1-2
2.2
2.3
2.4
Commands of the "OSPF" command level ....................................................................... 2-3
2.4.1
General commands ........................................................................................................ 2-3
2.4.2
OSPF configuration memories........................................................................................ 2-3
2.4.2.1 OSPF Configuration Memory Management................................................................ 2-3
2.4.3
Commands for editing an area ....................................................................................... 2-4
2.4.4
Commands for editing interfaces .................................................................................... 2-4
2.4.5
Commands for editing static routes ................................................................................ 2-5
2.4.6
Commands for combining IP networks........................................................................... 2-6
2.4.7
Commands for configuring a "virtual link" ....................................................................... 2-6
2.4.8
Commands for changing the "Router ID"........................................................................ 2-7
2.4.9
Commands for AS statistics............................................................................................ 2-7
3.2
3.3
4.2
4.3
4.4
05PHA00065AEY CUA
Contents
5.1.4
5.1.5
5.2
Requesting statistics data................................................................................................... 5-3
5.2.1
Overview ......................................................................................................................... 5-3
5.2.2
Examples of system responses ...................................................................................... 5-3
5.2.2.1 Area overview.............................................................................................................. 5-3
5.2.2.2 Overview of external routes......................................................................................... 5-3
5.2.2.3 Overview of the router configuration ........................................................................... 5-4
5.2.2.4 Overview of the interface configuration....................................................................... 5-4
5.2.2.5 Overview of the link state database ............................................................................ 5-4
5.2.2.6 Analysis of a LSA ........................................................................................................ 5-5
5.2.2.7 Overview of OSPF neighbors...................................................................................... 5-5
5.2.2.8 Overview of the routing table....................................................................................... 5-6
II
05PHA00065AEY CUA
Figures
Figures
Fig. 1-1
Fig. 2-1
05PHA00065AEY CUA
III
Figures
IV
05PHA00065AEY CUA
Tables
Tables
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 2-7
Table 2-8
Table 2-9
Table 2-10
Table 5-1
Table 5-2
Table 5-3
Table 5-4
Table 5-5
Table 5-6
Table 5-7
Table 5-8
Table 5-9
Table 5-10
Table 5-11
05PHA00065AEY CUA
Tables
VI
05PHA00065AEY CUA
Abbreviations
Abbreviations
Abbreviation
10BaseT
ABR
AS
ASBR
DCC
DCCM
DCCR
ECC
IDU
IF
IP
IR
LAN
LMT
LSA
LSDB
MSP
noadv
OSPF
RFC (...)
SOA
SOH
STM-1
TCP
TOS
WAN
WS
05PHA00065AEY CUA
Meaning
Ethernet -Standard for local baseband networks, 10 Mbit/s
Autonomous Border Router
Autonomous System
Autonomous System Boundary Router
Data Communication Channel
Data Communication Channel in the MSOH
Data Communication Channel in the RSOH
Embedded Control Channel
Indoor Unit
Interface
Internet Protocol
Internal Router
Local Area Network
Local MaintenanceTerminal (Service PC)
Link State Advertisement
Link State Database
Modular Service PC
no advertisement
Open Shortest Path First
Request for Comment (on Internet Standard)
ServiceOn Access
Section Overhead
Synchronous Transport Module 155 Mbit/s
Transmission Control Protocol
Type of Service
Wide Area Network
Workstation
VII
Abbreviations
VIII
05PHA00065AEY CUA
1
1.1
This version of MDRS 155 S and MDRS 155 E Digital Microwave Radio Systems is equipped with a
dynamic IP router. These systems can be monitored and controlled via TCP/IP and are appropriate for
transmitting and routing IP data within TCP/IP networks.
The transmission bandwidth of the IP channel is about 170 kbit/s when using the DCCR and about
360 kbit/s when using the DCCM. The DCCR and DCCM are data channels for transporting management
data in the SOH included in the STM-1 data stream.
The implementation of OSPF is based on OSPF version V2 in compliance with RFC 2328. The IP
protocol is based on IPV4 in compliance with RFC 791.
1.2
1.2.1
IP router
Brief description
In TCP/IP networks, MDRS 155 S and MDRS 155 E Digital Microwave Radio Systems operate as OSPF
routers. Both sides of the Digital Microwave Radio System are working as an IP router each.
The IDU or ECC Gateway of the Digital Microwave Radio System is equipped with a LAN interface and
WAN interface. The LAN interface is made available at a RJ45 port located on the front panel. The WAN
interface is implemented via one of the ECCs over the radio link and is not accessible by the user.
In the OSPF network, the radio link set up via the selected ECC represents a so-called "unnumbered
point-to-point link without an own IP address. The static route via the radio link is established
automatically and does not appear in the OSPF routing table. The special feature is that both routers
know the LAN IP address of the far end. Thus, from the logic view a radio link can be considered as one
single router.
LAN
10BaseT
LAN
10BaseT
2
Radio side
DCCR/DCCM
(ECC)
Line side
DCCR/DCC M
QD2
RS-485
QD2
RS-485
Fig. 1-1
Line side
DCCR/DCCM
Router interface
05PHA00065AEY CUA
1-1
1.2.2
Router features
The routers available in the MDRS 155 S and MDRS 155 E are fully functional OSPF routers. They
interact with third-party systems without any problems. Some special features must be taken into
consideration as the MDRS 155 processor executes all management functions for the Digital Microwave
Radio System. The number of possible dynamic routing entries is limited to 2000. Entries exceeding this
maximum will be discarded.
The OSPF router in the MDRS 155 can manage two areas. In addition, static routing entries are possible
which are managed within the AS. The latter permits the OSPF router in the system to be used as
When used as ABR, this router also manages a stub area. In stub areas, AS-external LSAs are not
propagated. The OSPF router in the MDRS 155 can also be configured for a so-called "totally stubby
area. In this case, summary LSAs are no longer imported from the AS.
If static routes are configured despite OSPF, they can be individually assigned attributes determining their
handling and processing in the AS.
1.2.3
Configuration
The OSPF router in the MDRS 155 is configured via the TCP/IP network or serially using a so-called
"embedded" Telnet session in the LMT Operator software or MSP appplication via the serial interface.
Please note that the following parameters can be set both via the LMT and MSP Operator programs:
With MDRS 155 S, the passwort can be adjusted only via the SOA Network Management System. The
"User Name" does not have to be set. It is "marconi" in the as-delivered state.
1-2
05PHA00065AEY CUA
2
2.1
All "Telnet" commands must be entered in small letters. Confirm each entry by pressing the "Enter" key.
Enter a blank between the command, address and attributes.
Separate the status entry or attribute value by means of a "=" symbol. Do not enter any additional blanks
here.
2.2
05PHA00065AEY CUA
Description
Shows all available commands
2-1
2.3
Command
arp
exit
ifstat
netstat
ospf
ping
route
uptime
traceroute
Command syntax
(list of options)
arp
<ip adress>
[-a]
[-d]
[-s]
exit
ifstat
netstat [-a]
[-r]
[-s]
ospf
ping
<ip address>
[timeout]
ping
-s <ip address>
[count]
route -a
uptime
traceroute
[-m <maxhops>]
[-q <nqueries>]
version
reboot
[-f]
[-i initial_ttl]
[-l]
[-n]
[-Q maxquit]
[-r]
[-S]
[-v]
[-c stoptime]
[-p port]
[-s source_addr]
[-t tos]
[-w waittime]
<host>
[packetsize]
version
reboot now
ipnvconf
ipnvconf <cr>
[inet <ip-address>]
[netmask <netmask>]
[gw <standard-gateway>]
Table 2-2
2-2
Description
Assignment of the IP address to the MAC address
[-a] Displays the ARP table;
[-d] Deletes an entry, e.g. arp -d <ip_addr>;
[-s] Adds an entry, e.g. arp -s <ip_addr> <eth_addr>;
Closes a Telnet session (not embedded Telnet session "LMT).
Displays the list of all interfaces.
[-a]
Displays active connections;
[-r]
Displays the Routing table;
[-s]
Displays protocol statistics.
Changes over to the 'ospf' command level.
Sends an ICMP echo request to another IP subscriber.
[timeout] Maximum response time
[count] Number of ICMP requests
Outputs the Routing table.
Displays as to how long the system has been operating without
a reboot.
Outputs the route to a destination address.
[-m <maxhops>] Sets the "time to live" box (max. number of
hops) in the IP header (1-255);
[-q <nqueries>] Number of requests (in packets) to be sent;
Prevents fragmentation;
Set an initial 'time to live' (default: ttl=1);
Lists ttl values;
Outputs numeric addresses;
Maximum number of consecutive timeouts;
Bypasses normal routing;
Displays per hop statistics values;
Verbose mode: delivers more information;
Delay time between two requests sent to a Cisco router;
Specification of a special UDP port for requests;
Source IP address;
[-t tos] Sets the TOS field in the IP header (0-7);
Sets the waiting time for a response (default: 3 seconds);
Destination address;
Packet size of ICMP packets to be sent;
Displays the current software version.
Reboots the ECC Gateway. In consequence, the network
element logs off from the SOA for the duration of the reboot
process. The current Telnet connection is interrupted.
Please note that the OSPF router is also rebooted, i.e. all OSPF
routes will get lost temporarily.
STM-1 signal transmission is not affected.
Outputs the current setting of the IP address, sub-net mask and
standard Gateway.
Input of a new IP address, sub-net mask and standard Gateway.
The parameters can also be applied individually. To activate the
configuration, a "Reboot" must be performed (command: reboot
now).
Commands of the "Telnet" command level
05PHA00065AEY CUA
2.4
2.4.1
General commands
Command
activate
cancel
config
load
quit
restart
save
Command syntax
(list of options)
activate
cancel
config
load
quit
restart
save
Table 2-3
Description
Activates all entries and quits the configuration level.
Quits the configuration mode without saving entries made.
Changes over to the configuration mode.
Downloads the OSPF configuration data to the OSPF kernel.
Changes over to the OSPF command level.
Restarts the OSPF process and deletes the LSDB.
Saves all current settings.
Commands of the OSPF command level
2.4.2
2.4.2.1
Three memories are used for storing and managing OSPF configuration data (see Fig. 2-1):
1. The current operating configuration is contained in a volatile RAM.
2. For changing the current operating configuration, an independent configuration memory is available.
The latter is used to intermediately save the new configuration data to the volatile RAM before the
relevant changes are activated.
3. The non-volatile memory stores all configuration data saved and holds these even in case of a power
supply failure.
Command input
Command Line
Interface (CLI)
Current
1
operating configuration
(running config)
activate
RAM
config
2
load
Changed
configuration
(changed config)
save
Saved configuration
(saved config)
Non-volatile memory
Fig. 2-1
RAM
EEPROM
The transitions between the different OSPF configuration memories are managed by means of the
appropriate commands of the Command Line Interface (CLI).
05PHA00065AEY CUA
2-3
The configuration data for the current operating configuration are always uploaded from the non-volatile
memory after booting the processor. To ensure that only valid and tested OSPF configuration data are
saved to the non-volatile memory, only data of the currently running operating configuration can be saved
to this memory (command: "Save").
2.4.3
Command
area delete
area edit
attribute
area add
attribute
area show
2.4.4
Command
interface
delete
interface
edit
attribute
Command syntax
(list of options)
if delete<integer>
if edit
<integer>
[priority=<integer>]
[xmt=<integer>]
[rxmt=<integer>]
[hello=<integer>]
[cost=<integer>]
[poll=<integer>]
if add
<integer>
<area
address>
[priority=<integer>]
[xmt=<integer>]
[rxmt=<integer>]
[hello=<integer>]
[cost=<integer>]
[poll=<integer>]
[dead=<integer>]
[passive=(no|yes)]
interface
show
if show
Description
Deletes the interface at the OSPF level.
Edits an existing interface.
Router priority in the interface network;
Delay time for sending out LSAs;
Interval between the repetition of LSAs;
Hello interval in seconds;
Output-side costs of the interface;
Polling interval between Hello packets after a router has
been identified 'offline';
Dead time interval in seconds;
OSPF process at this interface ON/OFF.
Adds a new interface.
Router priority in the interface network;
Delay time for sending out LSAs;
Interval between the repetition of LSAs;
Hello interval in seconds;
Output-side costs of the interface;
Polling interval between Hello packets after a router has
been identified 'offline';
Dead time interval in seconds;
OSPF process at this interface ON/OFF.
Displays a list of all interfaces configured.
Table 2-5
2-4
Deletes an area.
Changes an existing area.
Configures the selected area as stub area.
Summary LSAs can be/must not be imported into the area.
Costs incurring within the stub area.
[dead=<integer>]
[passive=(no|yes)]
interface
add
attribute
Description
2.4.5
Command
Command syntax
(list of options)
route delete route delete
route edit
attribute
Description
route edit
<destination><mask>
[type2=(yes|no)]
[direct=(yes|no)]
[noadv=(yes|no)]
[<cost>]
[<if>]
route add
attribute
route show
Fixed costs.
If the destination address is part of a locally
attached subnet in which no OSPF runs, use
the direct=yes option. In the local routing
table, the static route is stored as a direct
route, but not distributed over OSPF.
Distributes a static route over OSPF;
no=distributing a static route
yes=not distributing a static route
Route costs
Interface to be used for routing
(1=LAN; 2=ECC)
Adds a static route.
route add
<destination><mask><gateway>
[type2=(yes|no)]
Assign fixed costs;
[direct=(yes|no)]
If the destination address is part of a locally
attached subnet in which no OSPF runs, use
the direct=yes option. In the local routing
table, the static route is stored as a direct
route, but not distributed over OSPF.
Distributes a static route over OSPF;
[noadv=(yes|no)]
no=distributing a static route
yes=not distributing a static route
Route costs
[<cost>]
Interface to be used for routing
[<if>]
(1=LAN; 2=ECC)
route show
Displays a list of all static routes.
Table 2-6
05PHA00065AEY CUA
2-5
2.4.6
Command syntax
(list of options)
net-range delete net-range delete
<area address>
<destination><mask>
net-range
net-range edit
edit
<area address>
<destination>
<mask>
[noadv=(yes|no)]
attribute
net-range add
attribute
net-range add
<area address>
<destination>
<mask>
[noadv=(yes|no)]
net-range show
net-range show
Table 2-7
2.4.7
Command
virtual
delete
virtual
edit
attribute
virtual
add
attribute
Command syntax
(list of options)
virtual delete
<area_id><virtual link
neighbor id>
virtual edit
<area_id><virtual link
neighbor id>
[xmt=<integer>]
[hello=<integer>]
[dead=<integer>]
virtual add
<area_id><virtual link
neighbor id>
[xmt=<integer>]
[rxmt=<integer>]
virtual
show
[rxmt=<integer>]
[hello=<integer>]
[dead=<integer>]
virtual show
Table 2-8
2-6
Description
Description
Deletes the virtual link.
Edits an existing virtual link.
05PHA00065AEY CUA
2.4.8
Command
Command syntax
(list of options)
routerid edit
<router id> oder <auto>
routerid
edit
routerid
show
Description
Edits the Router ID. The default value is 'auto. Thus, the
IP address of the LAN interface is used as Router ID. To
change the Router ID, the appropriate entry must be
made in the IP address format.
Displays the current value of the Router ID.
routerid show
Table 2-9
2.4.9
Command
stats area
stats asexternal
stats
general
stats if
stata lsa
stats lsdb
stats
neighbor
stats route
Command syntax
(list of options)
stats area
stats as-external
Description
Displays a table showing the current status of the area.
Displays LSAs of type 5.
stats general
stats if
Displays information on the interfaces.
Analyzes a certain LSA.
stats lsa <linkstate type>
<linkstate id>
<advertising router>
<area address>
stats lsdb <area address>
Displays the LSDB of an area including LSAs of
types 1-4.
stats neighbor
Displays a table of OSPF neighbors of the interfaces
available.
stats route
Displays the OSPF routing table.
Table 2-10
05PHA00065AEY CUA
2-7
2-8
05PHA00065AEY CUA
Router Connections
Router Connections
3.1
3.1.1
LMT
As from version 7.0 onwards, the "LMT Operator software supports the "embedded" Telnet session.
Using a serial cable (D-Sub to RJ45), connect your PC to the IDU of the Digital Microwave Radio System.
Start up the LMT and select the "serial" connection type option.
The LMT password is <lmt> (default).
The MDRS 155 S password is <marconi> (default).
In case of an online session, you can press the appropriate menu bar icon for activating the "Embedded"
Telnet session. To access the OSPF router from the LMT, you require no additional password. The main
menu will be displayed immediately.
3.1.2
MSP
From Application 1.23 onwards, the "MSP Operator software supports the "embedded" Telnet session.
Using a serial cable (D-Sub to D-Sub), connect your PC to the ECC Gateway in the OHAU of the MDRS
155 E. Start up the SISA network driver and then the Network Manager.
Select the MDRS 155 system and call up the Equipment View. Select the OHAU by mouse-click. In the
ECC Gateway module, call up the "Command input" menu item under "Management - Configuration". To
access the OSPF router from the MSP, you require no additional password. The main menu will be
displayed immediately.
3.2
The PC is connected to the TCP/IP network via a network port. If the required MDRS system is not
located in the same network as your PC, you must enter a route in the latter which indicates the Gateway
that can be used to address the MDRS.
Execute the following work steps:
1.
2.
3.
3.3
The workstation (WS) is connected to the TCP/IP network via a network port. If the required MDRS
system is not located in the same network as your workstation, you must enter a route in the latter which
indicates the Gateway that can be used to address the MDRS.
1.
2.
3.
4.
05PHA00065AEY CUA
3-1
Router Connections
3-2
05PHA00065AEY CUA
4
4.1
Configuration Help
Configuration Help
Introduction
First of all the following IP configurations must be made using the LMT or MSP Operator software:
IP address setting
Network mask setting
Gateway setting
The information required for these settings is supplied by your network administrator.
Note:
4.2
Logging in
Access to the MDRS router is possible serially using the LMT or MSP Operator software, via the TCP/IP
network using a PC (Windows, Linux) or via a workstation.
After setup of a connection to the MDRS router in a "Telnet" session, enter the user name "admin and
the password. The user name "admin cannot be changed. The default password is "marconi. This
password can be changed only by the network administrator from the SOA Network Management
System.
After completion of the login process, the prompt appears in the form of the IP address of the system and
the "Telnet" note. You are now in the main menu of the "Command Line Interface.
4.3
Static routes
Static routes can be entered only via the OSPF level. The MDRS router is an OSPF router. Static routes
also have OSPF attributes.
In the main menu, enter the command
<ospf>
to change over to the OSPF command level.
Here you only have read-only access.
Using the command
<config>
you can activate the configuration mode for the OSPF router.
Note:
Do not make any entries if you do not have a network plan or configuration order.
05PHA00065AEY CUA
4-1
Configuration Help
4.4
With OSPF routers, dynamic routes are entered and managed automatically. Using the OSPF
configuration parameters, the administrator only defines the way the router shall work in the AS and the
role it shall play.
Note:
Do not make any entries if you do not have a network plan or configuration order.
Start out from the OSPF command level as described in the "Static routes" section and activate the
configuration mode.
<ospf>
<config>
Work step 1
With the MDRS router, active OSPF by entering the following command:
<area add [A.B.C.D]>
An area 2 is - for example - described with area ID 0.0.0.2. The specification of one area is sufficient if the
router shall be used as "Internal Router" (IR).
To use the MDRS router as "Area Border Router" (ABR), a second area ID must be entered according to
the same principle.
Enter the
<area show>
command to call up a list of the areas entered.
To assign an area a certain attribute different from the default settings, this attribute can be edited by
means of the following command:
<area edit [A.B.C.D] [attribute]=yes/no>
4-2
05PHA00065AEY CUA
Configuration Help
Work step 2
Both interfaces of the MDRS router must now be assigned to the area(s). One IDU of the MDRS serves
two interfaces. Interface 1 is the LAN interface (RJ45), interface 2 the ECC channel. Since the latter is
physically served by the system, it cannot be accessed by the user.
Using the command
<if add 1 [A.B.C.D]>
the LAN interface is assigned to the area with ID <A.B.C.D>.
Using the command
<if add 2 [A.B.C.D]>
the ECC interface is assigned to the area with ID <A.B.C.D>.
Using the command
<if show>
you can request a list of all interfaces entered.
To assign an interface an attribute different from the default settings, this attribute can be changed - for
example - at the LAN interface by entering the following command:
<if edit 1 [attribute]=[value]>.
To activate your entries, use the
<activate>
command. Then click the
<save>
button to save all changes made. After the saving process, you are again at the OSPF command level
with read-only access.
If you want to quit the OSPF configuration mode without saving your entries, click the
<cancel>
button.
05PHA00065AEY CUA
4-3
Configuration Help
4-4
05PHA00065AEY CUA
Status Tables
Status Tables
5.1
5.1.1
Configurations in the AS
Interface assignment
Using the <if show> command, you can request a list of interface assignments. If the table displayed is
empty, the system has not yet been configured for the OSPF environment.
if
1
2
area_id
0.0.0.2
0.0.0.2
priority xmt
1
100
1
100
rxmt
100
100
Table 5-1
if:
area_id:
priority:
xmt:
rxmt:
hello:
cost:
dead:
poll:
passive:
5.1.2
hello
10
10
cost
5
1
dead
40
40
poll
60
60
passive
no
no
Interface assignments
Area parameters
Using the <area show> command, you can request a list of all areas configured. If the table displayed is
empty, the system has not yet been configured for the OSPF environment. Max. two area entries are
possible.
area_id
0.0.0.2
stub
No
Table 5-2
area_id:
stub:
stubcost
import_summs:
Stubcost
1
Import_summs
No
Area parameters
05PHA00065AEY CUA
5-1
Status Tables
5.1.3
Static routes
Using the <route show> command, you can request a list of all static routes configured.
net
0.0.0.0
191.3.0.0
mask
0.0.0.0
255.255.0.0
Gateway
0.0.0.0
172.28.138.4
Table 5-3
net:
mask:
gateway:
type2:
direct:
noadv:
cost:
if:
5.1.4
cost
60
60
if
0
1
Combined IP networks
Using the <net-range show> command, you can request a list of existing IP network combinations. If the
table displayed is empty, there are no 'net ranges'.
area_id
0.0.0.2
Net
191.0.0.0
mask
255.255.0.0
Table 5-4
area_id:
net
mask:
noadv:
5.1.5
noadv
no
Net range
Virtual links
Using the <virtual show> command, you can request a list of existing virtual links. If the table displayed
is empty, there are no virtual links configured.
area_id
0.0.0.2
router_id
191.1.2.3
Table 5-5
area_id:
xmt:
rxmt:
hello:
dead:
5-2
xmt
100
rxmt
100
hello
10
dead
40
Virtual links
05PHA00065AEY CUA
5.2
Status Tables
5.2.1
Overview
The overview supplies a list of all statistics data that can be requested.
stats area <area ID>
stats as-external
stats general
stats if
stats lsa <ls_type> <ls_id> <adv_rtr> <area_id>
stats lsdb <area-id>
stats neighbor
stats route
5.2.2
5.2.2.1
Area overview
Using the <stats area> command, you can request information on the area.
Area ID
0.0.0.2
#Ifcs
2
#Routers
4
Table 5-6
Area_ID:
#Ifc:
#Router:
#LSAs
10
Xsum
0x478e7
Comments
Area overview
#LSA
Xsum:
Area number
Interface of the router in this area
Number of routers available in an area (a Digital Microwave Radio System also being counted as a
router)
Number of LSAs of types 1-4 in this area
Checksum
5.2.2.2
Using the <stats as-external> command, you can request a list of all type 5 LSAs available.
Type
5
LS_ID
191.50.0.0
ADV_RTR Seqno
191.6.0.8
0x80000087
Table 5-7
Type:
LS_ID:
ADV_RTR:
Seqno:
Xsum:
Age:
Xsum
0x1d78
Age
585
AS-external LSAs
05PHA00065AEY CUA
5-3
Status Tables
5.2.2.3
Using the <stats general> command, you can request the system database of the router.
OSPF Router ID:
ASE checksum:
ASEs allowed:
# Areas:
MOSPF enabled:
Inter-AS multicast:
ospfd version:
5.2.2.4
191.3.0.4
0x30df6d
0
1
no
no
2.16
# AS-external-LSAs:
# ASEs originated:
# Dijkstras:
# Nbrs in Exchange:
Inter-area multicast:
In overflow state:
102
0
129
0
no
no
Using the <stats if> command, you can request a table showing all interface data.
Phy
LAN
ECC
Addr
191.3.0.4
0.0.0.0
Area
0.0.0.2
0.0.0.2
Table 5-8
Phy:
Addr.:
Area:
Type:
State:
#Nbr:
#Adj:
Cost:
5.2.2.5
Type
Bcast
P-P
State
DR
P-P
#Nbr
1
1
#Adj
1
1
Cost
1
1
Interface configuration
Using the <stats lsdb> command, you can request the LSDB (Link State Database) table.
Type
LS_ID
1
191.3.0.3
1
191.3.0.4
1
191.4.0.6
1
191.6.0.8
2
191.3.0.4
2
191.4.0.8
3
172.28.138.0
3
191.1.0.0
3
192.168.2.0
4
191.1.0.2
# LSAs: 10*
ADV_RTR
191.3.0.3
191.3.0.4
191.4.0.6
191.6.0.8
191.3.0.4
191.6.0.8
191.3.0.3
191.3.0.3
191.3.0.3
191.3.0.3
Table 5-9
5-4
Seqno
0x8000056a
0x80000439
0x8000009c
0x800005f1
0x80000096
0x8000013a
0x8000008b
0x80000087
0x80000087
0x8000008a
Xsum
0x782f
0x4db3
0x7322
0x4308
0x8703
0x4f7f
0xb4df
0x0822
0x8019
0xdf44
Age
210
540
1293
850
1540
850
210
210
210
210
05PHA00065AEY CUA
5.2.2.6
Status Tables
LSA type; 1=Router LSA, 2=IP network LSA, 3= Network summary LSA, 4=ASBR
Summary LSA; note: LSAs of type 5 are not displayed in the LSDB and can be requested
by means of the <stats as-external> command.
This LSA contains information on ....
This LSA has been sent by ...
Sequence no. of this LSA
Checksum of this LSA
Age of this LSA in seconds
Number of LSAs stored in the database
Analysis of a LSA
Using the <stats lsa [type] [LS_ID] [ADV_RTR] [area_ID]> command, you can request a table
displaying the contents of this LSA.
Note:
It is reasonable and recommended to request the overview of the LSDB first, in order
to be able to select a certain LSA.
5.2.2.7
191.3.0.3
191.3.0.3
0x8000056a
0x782f
36
0x1
1
191.3.0.4
191.3.0.3
2
0
5
Using the <stats neighbor> command, you can request a table giving an overview of the OSPF
neighbors of the interfaces.
Phy
LAN
ECC
Addr
191.3.0.3
191.4.0.6
ID
191.3.0.3
191.4.0.6
Table 5-10
Phy:
Addr:
ID:
State:
#DD:
#Rq:
#Rxmt:
State
Full
Full
#DD
0
0
#Rq
0
0
#Rxmt
0
0
OSPF neighbors
Physical interface
IP address of the neighbor of this interface
Router ID
Negotiation status with the OSPF neighbor
Full=complete (neighbor has the 'full adjacent' status)
Number of 'Database Description' LSAs still to be sent to the neighbor
Number of 'Link State Requests' still to be sent to the neighbor
Number of repetitions sent
05PHA00065AEY CUA
5-5
Status Tables
5.2.2.8
Using the <stats route> command, you can call up the OSPF routing table.
Prefix
172.28.138.0/24
191.5.0.0/16
191.50.0.0/16
Type
SPFIA
SPF
SPFE2
Table 5-11
Prefix:
Type:
Cost:
Ifc:
Next-hop:
Mpaths:
5-6
Cost
6
7
20
Ifc
LAN
ECC
ECC
Next-hop
191.3.0.3
0.0.0.2
0.0.0.2
Mpaths
05PHA00065AEY CUA
6
6.1
6.1.1
Complementary Explications
Complementary Explications
"Virtual link" using the MDRS 155 Digital Microwave Radio
System
"Unnumbered" interface
Each IDU of the MDRS 155 Digital Microwave Radio System operates as an independent router. Only the
LAN interface has an IP address. The WAN connection to the far end contained in the STM-1 data stream
is implemented via an "unnumbered IP connection in the ECC (see section 1.2.1).
When planning the "virtual link using the MDRS 155 system, please note that the path of the "virtual link"
is not routed via this "unnumbered point-to-point connection. This means that a LAN interface of the
MDRS 155 system is always adjacent to the "transit area". This only applies if the Digital Microwave
Radio System assumes the function of an ABR or ASBR.
6.1.2
"Demand circuit"
If a "virtual link" is configured between the MDRS 155 and a Cisco router, it represents a "demand circuit"
in compliance with RFC1793 between the two routers after termination of the negotiation.
Normally, "hello" packets whose frequency depends on the adjusted "hello" interval time are also sent out
on a "virtual link". In case of a "demand circuit", "hello packets" are no longer sent out after termination of
the negotiation of the two ABRs. This means that the setting of the "hello" interval time and "dead time"
interval time are relevant only during the initial negotiations necessary for generating the "virtual link".
This process is initiated automatically by a Cisco router and accepted and processed by the MDRS 155
Digital Microwave Radio System. The MDRS 155 Digital Microwave Radio System does not initiate a
"demand circuit".
6.1.3
Router ID
The router ID can be set in the MDRS 155 Digital Microwave Radio System. In the factory setting
(default), the router ID is "auto", i.e. the adjusted IP address is also used as router ID.
On configuration of the "virtual link", the "virtual link" neighbor is basically addressed with its router ID. If
the router ID is changed after configuration of a "virtual link", the link will not exist any longer.
05PHA00065AEY CUA
6-1
Complementary Explications
6.2
6.2.1
6.2.1.1
With MDRS 155 S, the router data are saved to the Master IDU MIB.
After connecting the LMT to MDRS 155 S, call up the Equipment view. Using the right mouse button, click
the CPU. From the menu displayed, select the "Database" and "Upload" menu items.
In the mask that appears, enter a filename and click the "Save" button. The upload window appears.
Choose the "Start" button. At the end of the upload process, the MIB is located in the required
destination.
6.2.1.2
The upload of the router configuration can also be executed locally using the MSP. In this case, the
backup is performed in the SISA-0 function group. From the list box displayed, select the "Management"
option. Then click the "File transfer" menu item.
In the mask that appears, click the "Upload" button. Then select the directory containing system software
2.3. Here you can find the ECCMDBUP.ctl. control file. Select this file and start up the upload process by
clicking the "Start" buttton. After completion of the upload process, close the window. A file named
mdb.zib is now contained in the system directory.
Note: If it is necessary to create individual filenames, the filename must be either edited directly or
changed already in the ECCMDBUP.ctl. When doing this, please note the convention of older Windows
Systems 8.3 (filename: max. 8 digits, file type: 3 digits). For making a download, an appropriately
changed ECCMDBDN.ctl must be available. We recommend a systematic archiving of router data by
means of SOA.
6.2.1.3
Uploading the router data from MDRS 155 S is remotely possible via SOA. Please note that the
configuration of the IP router must be included in the microwave radio system MIB.
In the QD2 address list or Topology view, call up the icon for the required MDRS 155 S system. Activate
the "Editing" mode in the "Admin" menu. Then select the "Configuration Basic functions" option. From
the menu items offered, select "MIB transfer".
In the mask displayed, highlight the "Upload" option and click the "Execute" button. The MIB is saved
automatically by SOA under the Ref-ID of the corresponding network element.
6.2.1.4
Uploading the router data from MDRS 155 E is possible remotely via SOA. Please note that only the IP
router configuration data are saved and no other system data.
In the QD2 address list or Topology view, call up the icon for the required MDRS 155 E system. Activate
the "Editing" mode in the "Admin" menu. Then select the "Configuration Basic functions" option. From
the menu items offered, select "MIB transfer".
In the mask displayed, highlight the "Upload" option and click the "Execute" button. The MIB is saved
automatically by SOA under the Ref-ID of the corresponding network element.
6-2
05PHA00065AEY CUA
6.2.2
6.2.2.1
Complementary Explications
With MDRS 155 S, router data are downloaded using the microwave radio system MIB.
After connecting the LMT to MDRS 155 S, call up the Equipment view. Using the right mouse button, click
the CPU. From the menu displayed, select the "Database" and "Download" menu items.
In the mask that appears, select the required filename and click the "Open" button. The download window
appears. Choose the "Start" button. At the end of the download process, the MIB is loaded in the network
element.
6.2.2.2
The download of the router configuration can also be executed locally using the MSP. In this case, the
transfer takes place in the SISA-0 function group. From the list box displayed, select the "Management"
option. Then click the "File transfer" menu item.
In the mask that appears, click the "Download" button. Then select the directory containing system
software 2.3. Here you can find the ECCMDBDN.ctl* control file. Select this file and start up the download
process by clicking the "Start" buttton. The download bar displayed shows the progress of the download
process. After completion of the download, close the window.
*or any individual control file
6.2.2.3
Downloading the router data to MDRS 155 S is possible remotely via SOA. Besides the router data, the
MDRS 155 S MIB also contains all other network element settings.
In the QD2 address list or Topology view, call up the icon for the required MDRS 155 S system. Activate
the "Editing" mode in the "Admin" menu. Then select the "Configuration Basic functions" option. From
the menu items offered, select "MIB transfer".
In the mask displayed, highlight the "Download" option and click the "Execute" button. The MIB is called
up automatically by SOA under the Ref-ID of the corresponding network element. If no file is available, a
"Not available" message appears.
6.2.2.4
Downloading the router data to MDRS 155 E is possible remotely via SOA. Please note that only the IP
router configuration data are downloaded and no other system data.
In the QD2 address list or Topology view, call up the icon for the required MDRS 155 E system. Activate
the "Editing" mode in the "Admin" menu. Then select the "Configuration Basic functions" option. From
the menu items offered, select "MIB transfer".
In the mask displayed, highlight the "Download" option and click the "Execute" button. The MIB is called
up automatically by SOA under the Ref-ID of the corresponding network element. If no file is available, a
"Not available" message appears.
05PHA00065AEY CUA
6-3
Complementary Explications
6-4
05PHA00065AEY CUA