Professional Documents
Culture Documents
Mdrs
Mdrs
Mdrs
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
Marconi Communications GmbH
D-71520 Backnang
Telefon (07191) 13-0 Telefax (07191) 13-3212
http://www.marconi.com
Copyright 2004 by Marconi Communications GmbH
(hierin bezeichnet als Marconi)
Änderungen vorbehalten · Gedruckt in Deutschland
Contents
05PHA00065AEY CUA I
Contents OSPF Functions and Commands
II 05PHA00065AEY CUA
OSPF Functions and Commands Figures
Figures
Fig. 1-1 Router interface ................................................................................................................ 1-1
Fig. 2-1 OSPF configuration memory........................................................................................... 2-3
IV 05PHA00065AEY CUA
OSPF Functions and Commands Tables
Tables
Table 2-1 Commands of all command levels ................................................................................ 2-1
Table 2-2 Commands of the "Telnet" command level .................................................................. 2-2
Table 2-3 Commands of the OSPF command level ...................................................................... 2-3
Table 2-4 Commands for editing an area....................................................................................... 2-4
Table 2-5 Commands for interface editing .................................................................................... 2-4
Table 2-6 Commands for editing static routes.............................................................................. 2-5
Table 2-7 Commands for combining IP networks......................................................................... 2-6
Table 2-8 Commands for configuring a "virtual link"................................................................... 2-6
Table 2-9 Commands for changing the "Router ID" ..................................................................... 2-7
Table 2-10 Commands for AS statistics........................................................................................... 2-7
Table 5-1 Interface assignments..................................................................................................... 5-1
Table 5-2 Area parameters .............................................................................................................. 5-1
Table 5-3 Routing table of static routes......................................................................................... 5-2
Table 5-4 Net range .......................................................................................................................... 5-2
Table 5-5 Virtual links ...................................................................................................................... 5-2
Table 5-6 Area overview .................................................................................................................. 5-3
Table 5-7 AS-external LSAs ............................................................................................................ 5-3
Table 5-8 Interface configuration.................................................................................................... 5-4
Table 5-9 Link State Database ........................................................................................................ 5-4
Table 5-10 OSPF neighbors .............................................................................................................. 5-5
Table 5-11 OSPF routing table .......................................................................................................... 5-6
05PHA00065AEY CUA V
Tables OSPF Functions and Commands
VI 05PHA00065AEY CUA
OSPF Functions and Commands Abbreviations
Abbreviations
Abbreviation Meaning
10BaseT Ethernet -Standard for local baseband networks, 10 Mbit/s
ABR Autonomous Border Router
AS Autonomous System
ASBR Autonomous System Boundary Router
DCC Data Communication Channel
DCCM Data Communication Channel in the MSOH
DCCR Data Communication Channel in the RSOH
ECC Embedded Control Channel
IDU Indoor Unit
IF Interface
IP Internet Protocol
IR Internal Router
LAN Local Area Network
LMT Local MaintenanceTerminal (Service PC)
LSA Link State Advertisement
LSDB Link State Database
MSP Modular Service PC
noadv no advertisement
OSPF Open Shortest Path First
RFC (...) Request for Comment (on Internet Standard)
SOA ServiceOn Access
SOH Section Overhead
STM-1 Synchronous Transport Module 155 Mbit/s
TCP Transmission Control Protocol
TOS Type of Service
WAN Wide Area Network
WS Workstation
1.2 IP router
1.2.1 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 LAN
1 10BaseT 10BaseT
2
Radio side
Line side DCCR/DCCM Line side
DCCR/DCC M (ECC) DCCR/DCCM
QD2 QD2
RS-485 RS-485
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.
Prevents fragmentation;
[-f] Set an initial 'time to live' (default: ttl=1);
[-i initial_ttl] Lists ttl values;
[-l] Outputs numeric addresses;
[-n] Maximum number of consecutive ‘timeouts’;
[-Q maxquit] Bypasses normal routing;
[-r] Displays per hop statistics values;
[-S] Verbose mode: delivers more information;
[-v] Delay time between two requests sent to a Cisco router;
[-c stoptime] Specification of a special UDP port for requests;
[-p port] Source IP address;
[-s source_addr] [-t tos] Sets the TOS field in the IP header (0-7);
[-t tos] Sets the waiting time for a response (default: 3 seconds);
[-w waittime] Destination address;
<host> Packet size of ICMP packets to be sent;
[packetsize]
version version Displays the current software version.
reboot reboot now 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.
ipnvconf ipnvconf <cr> Outputs the current setting of the IP address, sub-net mask and
standard Gateway.
[inet <ip-address>] Input of a new IP address, sub-net mask and standard Gateway.
[netmask <netmask>] The parameters can also be applied individually. To activate the
[gw <standard-gateway>] configuration, a "Reboot" must be performed (command: reboot
now).
Table 2-2 Commands of the "Telnet" command level
Three memories are used for storing and managing OSPF configuration data (see Fig. 2-1):
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)
1 Current RAM
operating configuration
(running config)
activate config
2 Changed
configuration RAM save
(changed config)
load
3
Saved configuration
(saved config)
Non-volatile memory
EEPROM
The transitions between the different OSPF configuration memories are managed by means of the
appropriate commands of the Command Line Interface (CLI).
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").
[stubcost=<integer>]
area add area add <area Adds a new area.
attribute address> Configures the selected area as stub area.
[stub=(no|yes)] Summary LSAs can be/must not be imported into the area.
[importsum=(no|yes)] Costs incurring within the stub area.
[stubcost=<integer>]
area show area show Displays a list of all areas configured.
Table 2-4 Commands for editing an area
3 Router Connections
3.1 "Embedded" Telnet session
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.
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.
4 Configuration Help
4.1 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.
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“.
<ospf>
<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.
<activate>
<save>
button to save the changes you have 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.
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:
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>
To assign an area a certain attribute different from the default settings, this attribute can be edited by
means of the following command:
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.
<if show>
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:
<activate>
<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.
5 Status Tables
5.1 Configurations in the AS
5.1.1 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.
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.
Using the <route show> command, you can request a list of all static routes configured.
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'.
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.
The overview supplies a list of all statistics data that can be requested.
Using the <stats area> command, you can request information on the area.
Using the <stats as-external> command, you can request a list of all type 5 LSAs available.
Using the <stats general> command, you can request the system database of the router.
Using the <stats if> command, you can request a table showing all interface data.
Using the <stats lsdb> command, you can request the LSDB (Link State Database) table.
Type: 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.
LS_ID: This LSA contains information on ....
ADV_RTR: This LSA has been sent by ...
Seqno: Sequence no. of this LSA
Xsum: Checksum of this LSA
Age: Age of this LSA in seconds
* Number of LSAs stored in the database
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.
Using the <stats neighbor> command, you can request a table giving an overview of the OSPF
neighbors of the interfaces.
Using the <stats route> command, you can call up the OSPF routing table.
6 Complementary Explications
6.1 "Virtual link" using the MDRS 155 Digital Microwave Radio
System
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.