Manual Router AFR677

ABB Power Systems
Routing Configuration
Ruggedized ABB FOX Router AFR677
User Manual
User Manual - Routing Configuration
Ruggedized ABB FOX Router AFR677
Copyright and Confidentiality: Copyright in this document vests in ABB LTD. 

Manuals and software are protected by copyright. All rights reserved. The copying,
reproduction, translation, conversion into any electronic medium or machine scannable form
is not permitted, either in whole or in part. The contents of the manual may not be disclosed
by the recipient to any third party, without the prior written agreement of ABB. 
An exception is the preparation of a backup copy of the software for your own use. For
devices with embedded software, the end-user license agreement on the enclosed CD
applies.
This document may not be used for any purposes except those specifically authorised by
contract or otherwise in writing by ABB.
Disclaimer: ABB has taken reasonable care in compiling this document, however ABB accepts no liability
whatsoever for any error or omission in the information contained herein and gives no other
warranty or undertaking as to its accuracy.
ABB can accept no responsibility for damages, resulting from the use of the network
components or the associated operating software. In addition, we refer to the conditions of
use specified in the license contract.
ABB reserves the right to amend this document at any time without prior notice.
Blank pages: Any blank page present is to accommodate double-sided printing.
Document No.: 1KHD642916
ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © September 2010 by ABB Switzerland Ltd
Contents
About this Manual 3
Key 4
Configuration 5
1 Routing - Basics 7
1.1 ARP 9
1.2 CIDR 11
1.3 Net-directed Broadcasts 12
1.4 Multinetting 13
2 Static Routing 15
2.1 Port-based Router Interface 16
2.1.1 Configuration of the Router Interfaces 17
2.2 VLAN-based Router-Interface 19
2.3 Configuration of a Static Route 22
2.3.1 Configuration of a Static Route 22
2.3.2 Configuration of a redundant static route 23
2.3.3 Configuration of a redundant static route with load sharing 25
2.4 Static route tracking 26
2.4.1 Description of the static route tracking function 26
2.4.2 Application example for the static route tracking function 26
2.5 Adaptation for non-IP-compliant devices 29
3 Tracking 31
3.1 Interface tracking 32
3.2 Ping tracking 33
3.3 Logical tracking 35
3.4 Configuring the tracking 36
3.4.1 Configuring interface tracking 36
3.4.2 Application example for ping tracking 37
3.4.3 Application example for logical tracking 38
4 VRRP/E-VRRP 41
4.1 VRRP 42
4.1.1 Configuration of VRRP 44
4.2 E-VRRP 45
4.3 E-VRRP Domains 48
4.3.1 Configuration of E-VRRP domains 49
4.3.2 Example of configuration of E-VRRP domains 49
4.4 VRRP tracking 52
4.5 VRRP with load sharing 57
4.6 VRRP with Multinetting 58
5 RIP 59
5.1 Convergence 60
5.2 Maximum Network Size 62
ABB Web-based Interface Reference Manual 1

5.3 General Properties of RIP 63
5.4 Configuring the RIP 64
6 OSPF 67
6.1 OSPF-Topology 68
6.1.1 Autonomous System 68
6.1.2 Router ID 69
6.1.3 Areas 69
6.1.4 Virtual Link 70
6.1.5 OSPF Router 72
6.1.6 Link State Advertisement 72
6.2 General Operation of OSPF 74
6.3 Setting up the Neighbor Relationship 75
6.4 Synchronization of the LSD 77
6.5 Route Determination 78
6.6 Configuring OSPF 79
7 Protocol-based VLANs 83
7.1 General Configuration 84
7.2 Configuration of the Example 85
8 Multicast Routing 87
8.1 Multicast Addresses 88
8.1.1 IP Multicast Addresses 88
8.1.2 MAC Multicast Addresses 90
8.1.3 Mapping IP MAC Multicast Addresses 91
8.2 Multicast Group Registration 92
8.3 PIM-DM/DVMRP 93
8.4 Scoping 96
8.5 Multicast Configuration 97
8.5.1 Example with Layer 3 Redundancy 97
8.5.2 Example with Layer 2 Redundancy 100
8.5.3 Tips for the configuration 101
A Appendix 103
A.1 Abbreviations used 104
A.2 Underlying IEEE Standards 106
A.3 List of RFCs 107
A.4 Entering the IP Parameters 109
A.5 Copyright of Integrated Software 112
A.5.1 Bouncy Castle Crypto APIs (Java) 112
A.5.2 Broadcom Corporation 112
2 Web-based Interface Reference Manual ABB

ABOUT THIS MANUAL
About this Manual
The “Routing Configuration” user manual contains all the information you need to start operating the routing
function. It takes you step by step from a small router application through to the router configuration of a complex
network. 
The manual enables you to configure your router by following the examples.
The “Routing Configuration” user manual requires you to be familiar with the content of the “Basic Configuration”
user manual.
You can use this manual to configure simple networks without any special knowledge. The configuration of
complex networks requires well-founded knowledge on the subject of routing and of the protocols IP, RIP, OSPF,
IGMP and VRRP.
The “Installation” user manual contains a device description, safety instructions, a description of the display, and
the other information that you need to install the device.
The “Basic Configuration” user manual contains the information you need to start operating the device. It takes
you step by step from the first startup operation through to the basic settings for operation in your environment.
The “Redundancy Configuration” user manual contains the information you need to select a suitable redundancy
procedure and configure that procedure.
You will find detailed descriptions of how to operate the individual functions in the “Web-based Interface” and
“Command Line Interface” reference manuals.
The Network Management Software AFS View provides you with additional options for smooth configuration and
monitoring:
 Configuration of multiple devices simultaneously.
 Graphical interface with network layouts.
 Auto-topology discovery.
 Event log.
 Event handling.
 Client / Server structure.
 Browser interface
 ActiveX control for SCADA integration
 SNMP/OPC gateway
ABB Routing Configuration User Manual 3

KEY
Key
The designations used in this manual have the following meanings:
 List
 Work step
 Subheading
Link Indicates a cross-reference with a stored link
Note: A note emphasizes an important fact or draws your
attention to a dependency.
Courier ASCII representation in user interface
Execution in the Web-based Interface user interface
Execution in the Command Line Interface user interface
Symbols used:
WLAN access point
Router with firewall
Switch with firewall
Router
Switch
Bridge
Hub
A random computer
Configuration Computer
Server
4 Routing Configuration User Manual ABB

CONFIGURATION
1 Configuration
Because the configuration of a router is very dependent on the conditions in your network, you are first provided
with a general list of the individual configuration steps. To optimally cover the large number of options, this list is
followed by examples of networks that usually occur in the industry sector. The examples are selected so that the
configurations for other applications can be easily derived from them.
The configuration of the routing function usually contains the following steps:
 Drawing a network plan

Create a picture of your network so that you can clearly see the division into subnetworks and the related
distribution of the IP addresses. This step is very important. Good planning of the subnetworks with the
corresponding network masks makes the router configuration much easier.
 Router basic settings

Along with the global switching on of the routing function, the router basic settings also contain the assignment
of IP addresses and network masks to the router interfaces.
Note: Adhere to the sequence of the individual configuration steps so that the configuration computer has access
to all the layer 3 Switches throughout the entire configuration phase.
Note: When you assign an IP address from the subnetwork of the management IP address to a router interface,
the Switch deletes the management IP address. You access the Switch via the IP address of the router interface.
Activate the routing globally before you assign an IP address from the subnetwork of the management IP address
to a router interface.
Note: When you assign the VLAN ID of the management VLAN to a router interface, the Switch deactivates the
management IP address. You access the Switch via the IP address of the router interface. The management
VLAN is the VLAN by means of which you access the management of all the Switches.
Note: Depending on your configuration steps, it may be necessary to change the IP parameters of your
configuration computer to enable access to the layer 3 Switches.
 Selecting a routing procedure

On the basis of the network plan and the communication requirements of the connected devices, you select
the optimal routing procedure (static routes, RIP, OSPF) for your situation. In doing so, consider which routing
procedures the routers can use along a route.
 Configuring a routing procedure

Configure the selected routing procedure.

CONFIGURATION
1

ROUTING - BASICS
1 Routing - Basics
A router is a node for exchanging data on the layer 3 of the ISO/OSI layer model.
This ISO/OSI reference model had the following goals:
 To define a standard for information exchange between open systems;
 To provide a common basis for developing additional standards for open systems;
 To provide international teams of experts with functional framework as the basis for independent development
of every layer of the model;
 To include in the model developing or already existing protocols for communications between heterogeneous
systems;
 To leave sufficient room and flexibility for the inclusion of future developments.
The reference model consists of 7 layers, ranging from the application layer to the physical layer.
7 Application Access to communication services from an application program

6 Presentation Definition of the syntax for data communication
5 Session Set up and breakdown of connections by synchronization and organization of the dialog
4 Transport Specification of the terminal connection, with the necessary transport quality
3 Network Transparent data exchange between two transport entities
2 Data-Link Access to physical media and detection of transmission errors
1 Physical Transmission of bit strings via physical media
Table 1: OSI Reference Model
What does the data exchange on the layer 3 mean in comparison with the data exchange on the layer 2?
Layer 7 Layer-2-Switch Layer 7 Layer 7 Layer-3-Switch/ Layer 7

Layer 6 Layer 6 Layer 6 Router Layer 6
Layer 5 Layer 5 Layer 5 Layer 5
Layer 4 Layer 4 Layer 4 Layer 4
Layer 3 Layer 3 Layer 3 Layer 3 Layer 3
Layer 2 Layer 2 Layer 2 Layer 2 Layer 2 Layer 2
Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1
Figure 1: Data Transport by a Switch and a Router in the OSI Reference Model‘s Layers
On the layer 2, the MAC address signifies the destination of a data packet. The MAC address is an address tied
to the hardware of a device. The layer 2 expects the receiver in the connected network. The data exchange to
another network is the task of layer 3. Layer 2 data traffic is spread over the entire network. Every subscriber filters
the data relevant for him from the data stream. Layer 2 switches are capable of steering the data traffic that is
intended for a specific MAC address. It thus relieves some of the load on the network. Broadcast and multicast
data packets are forwarded by the layer 2 switches at all ports.

ROUTING - BASICS
1
IP is a protocol on the layer 3. IP provides the IP address for addressing data packets. The IP address is assigned
by the network administrator. By systematically assigning IP addresses, he can thus structure his network,
breaking it down into subnets (see on page 11 „CIDR“). The bigger a network gets, the greater the data volume.
Because the available bandwidth has physical limitations, the size of a network is also limited. Dividing large
networks into subnets limits the data volume on these subnets. Routers divide the subnets from each other and
only transmit the data that is intended for another subnet.
Figure 2: MAC Data Transmission: Unicast Data Packet (left) and Broadcast Data Packet (right)
This illustration clearly shows that broadcast data packets can generate a considerable load on larger networks.
You also make your network easier to understand by forming subnets, which you connect with each other using
routers and, strange as it sounds, also separate securely from each other.
A Switch uses the MAC destination address to transmit, and thus uses layer 2. 
A router uses the IP destination address to transmit, and thus uses layer 3.
The subscribers associate the MAC and IP addresses using the Address Resolution Protocol (ARP).

ROUTING - BASICS
ARP
1.1 ARP
The Address Resolution Protocol (ARP) determines the MAC address that belongs to an IP address. What is the
benefit of this?
Let's suppose that you want to configure your Switch using the Web-based interface. You enter the IP address of
your Switch in the address line of your browser. But which MAC address will your PC now use to display the
information in the Switch in your browser window?
If the IP address of the Switch is in the same subnet as your PC, then your PC sends what is known as an ARP
request. This is a MAC broadcast data packet that requests the owner of the IP address to send back his
MAC address. The Switch replies with a unicast data packet containing his MAC address. This unicast data packet
is called an ARP reply.
Query to everyone:
Whoever has the
IP address 149.218.112.101
please send me your MAC address.
149.218.112.159
00:80:63:10:11:12
149.218.112.101
00:80:63:10:11:25
Reply to PC:
My MAC address is
00:80:63:10:11:25.
Figure 3: ARP request and reply
If the IP address of the Switch is in a different subnet, then the PC asks for the MAC address of the gateway
entered in the PC. The gateway/router replies with its MAC address.
Now the PC packs the IP data packet with the IP address of the switch, the final destination, into a MAC frame
with the MAC destination address of the gateway/router and sends the data. 
The router receives the data and releases the IP data packet from the MAC frame, so that it can then forward it in
accordance with its transmission rules.

ROUTING - BASICS
1
ARP
Preabmle
MAC dest. address
MAC source address Layer 2
Type/length field
IP header with
IP source address and
IP destination address Layer 3
Data
Layer 4 and higher
Check field
Figure 4: Structure of a data packet from the ISO/OSI layer model perspective
All terminal devices still working with IPs of the first generation, for example, are not yet familiar with the term
'subnet'. They also send an ARP request when they are looking for the MAC address for an IP address in
a different subnet. They neither have a network mask with which they could recognize that the subnet is a different
one, nor do they have a gateway entry. In the example below, the left PC is looking for the MAC address of the
right PC, which is in a different subnet. In this example, it would normally not get a reply.
Because the router knows the route to the right PC, the proxy ARP function replies to this router interface on behalf
of the right PC with its own MAC address. Thus the left PC can address its data to the MAC address of the router,
which then forwards the data to the right PC.
Query to everyone:
Whoever has the
IP address 10.0.2.111.
10.0.1.159 10.0.2.111
00:80:63:10:11:12
Prox-ARP
00:80:63:10:22:25
Reply to PC:
The IP address 10.0.1.111
has the MAC address
00:80:63:10:22:25.
Figure 5: ARP proxy funktion
The proxy ARP function is available on the router interfaces on which you switch on the proxy ARP.

ROUTING - BASICS
CIDR
1.2 CIDR
The original class allocation of the IP addresses only planned for three address classes to be used by the users
(see “Basics of IP Parameters” in the basic configuration of the user manual).
Since 1992, five classes of IP address have been defined in the RFC 1340.
Class Network part Host part Address range

A 1 byte 3 bytes 1.0.0.0 to 126.255.255.255
B 2 bytes 2 bytes 128.0.0.0 to 191.255.255.255
C 3 bytes 1 byte 192.0.0.0 to 223.255.255.255
D 224.0.0.0 to 239.255.255.255
E 240.0.0.0 to 255.255.255.255
Table 2: IP address classes
Class C with a maximum of 254 addresses was too small, and class B with a maximum of 65534 addresses was
too large for most users, as they would never require so many addresses. This resulted in ineffective usage of the
class B addresses available.
Class D contains reserved multicast addresses. Class E is reserved for experimental purposes. A gateway not
participating in these experiments ignores datagrams with this destination address.
The Classless Inter-Domain Routing (CIDR) provides a solution to these problems. The CIDR overcomes these
class boundaries and supports classless address ranges.
With CIDR, you enter the number of bits that designate the IP address range. You represent the IP address range
in binary form and count the mask bits that designate the network mask. The network mask indicates the number
of bits that are identical for all IP addresses, the network part, in a given address range. Example:
IP address, decimal Network mask, IP address, hexadecimal
decimal
149.218.112.1 255.255.255.128 10010101 11011010 01110000 00000001
149.218.112.127 10010101 11011010 01110000 01111111
25 mask bits
CIDR notation: 149.218.112.0/25
Mask bits
The combination of a number of class C address ranges is known as “supernetting”. This enables you to subdivide
class B address ranges to a very fine degree.
Using mask bits simplifies the routing table. The router determines in that direction in which most of the mask bits
match (longest prefix match).

ROUTING - BASICS
1
Net-directed Broadcasts
1.3 Net-directed Broadcasts
A net-directed broadcast is an IP data packet that a device sends to a net‘s broadcast address1 to address all
receivers of that net. In a transfer network, a net-directed broadcast is sent as a MAC unicast frame. If the router
locally responsible for that network supports net-directed broadcasts, it sends these data packets as a MAC
broadcast frame to its local network.
If the router interface is VLAN based, the router sends the frame to all ports that are members of the router
interface VLAN.
This way, net-directed broadcasts can relieve your transfer network from multiple IP unicasts which would be
necessary as an alternative for a net-directed broadcast.
If the router does not support net-directed broadcasts, or if you deactivate this function for a router interface, the
router discards the received IP data packets which have been sent to the router interface‘s network broadcast
address. In case of multinetting, this applies also to the router interface‘s secondary IP addresses.
1. The net broadcast address is the topmost IP address of an IP network for which a router interface is
responsible. The device determines the broadcast address from its interface IP address and the corresponding
network mask. 
If a router interface has e.g. the IP address 192.168.1.1 and the network mask 255.255.255.0, it is responsible for
the network 192.168.1.0/24. The net broadcast address is in this case 192.168.1.255.

ROUTING - BASICS
Multinetting
1.4 Multinetting
Multinetting allows you to connect a number of subnets to one router port. Multinetting provides a solution for when
you want to connect existing subnets to a router within a physical medium. In this case you can use multinetting
to assign a number of IP addresses for the different subnets to the routing port to which you are connecting the
physical medium.
For a long-term solution, other network design strategies provide more advantages with regard to problem solving
and bandwidth management.
10.0.1.2/24 10.0.1.3/24
10.0.2.3/24
10.0.1.1/24
10.0.2.1/24 10.0.2.9/24
10.0.1.9/24
Figure 6: Example of multinetting

ROUTING - BASICS
1
Multinetting

STATIC ROUTING
2 Static Routing
Static routes are user-defined routes which the Switch uses to transmit data from one subnet to another. 
The user specifies to which router (next hop) the Switch forwards data for a particular subnet. Static routes are
kept in a table which is permanently stored in the Switch.
Compared to dynamic routing, the advantage of this transparent route selection is offset by the increased workload
involved in configuring the static routes. Static routing is therefore suited to very small networks or to selected
areas of larger networks. Static routing makes the routes transparent for the administrator and can be easily
configured in small networks.
If, for example, a line interruption causes the topology to change, the dynamic routing can react automatically to
this, in contrast to the static routing. If you combine static and dynamic routing, you can configure the static routes
in such a way that they have a higher priority than a route selected by a dynamic routing procedure.
The first step in configuring the router is to globally switch on the router function and configure the router interfaces.
The Switch allows you to define port-based and VLAN-based router interfaces (see fig. 7).
Example: Connecting two networks
Configuration PC Port-based VLAN-based
SN 10 A
SN 11
VLAN ID 2
Figure 7: Static routes

STATIC ROUTING
2
Port-based Router Interface
2.1 Port-based Router Interface
A characteristic of the port-based router interface is that a subnet is connected to a port (see fig. 7).
Special features of port-based router interfaces:

 If there is no active connection, then the entry from the routing table is omitted, because the router transmits
exclusively to those ports for which the data transfer is likely to be successful.
The entry in the interface configuration table remains.
 A port-based router interface does not recognize VLANs, which means that the router rejects tagged frames
which it receives at a port-based router interface.
 A port-based router interface rejects all the non-routable packets.
Below (see fig. 8) you will find an example of the simplest case of a routing application with port-based router
interfaces.

STATIC ROUTING
2.1.1 Configuration of the Router Interfaces
10.0.1.5/24 10.0.2.5/24
Interface 2.1 Interface 2.2
IP=10.0.1.1/24 IP=10.0.2.1/24
Figure 8: Simplest case of a route
enable Switch to the Privileged EXEC mode.

configure Switch to the Configuration mode.
ip routing Switch on the router function globally.
interface 2/1 Select the first port at which you want to enter the
router interface IP address.
ip address 10.0.1.1  Assign the IP parameters to the port.
255.255.255.0
routing Switch on the router function at this port.
exit Switch to the Configuration mode.
interface 2/2 Select the second port at which you want to enter
the router interface IP address.
ip address 10.0.2.1  Assign the IP parameters to the port.
255.255.255.0
ip netdirbcast Switch on the forwarding of net-directed
broadcasts at this port.
exit Switch to the privileged EXEC mode.
show ip interface brief Verify the entries.
Netdir Multi
Interface IP Address IP Mask Bcast CastFwd
--------- --------------- --------------- -------- --------
2/1 10.0.1.1 255.255.255.0 Disable Disable
2/2 10.0.2.1 255.255.255.0 Enable Disable
show ip interface 2/1 Verify the rest of the settings of interface 2/1.
Primary IP Address.......... ............ 10.0.1.1/255.255.255.0

Routing Mode............................. Enable
Administrative Mode...................... Enable
Forward Net Directed Broadcasts.......... Enable
Proxy ARP................................ Disable
Active State............................. Active
Link Speed Data Rate..................... 100 Full
MAC Address.............................. 00:80:63:51:74:0C
Encapsulation Type....................... Ethernet
IP MTU................................... 1500
show ip route Verify the routing table:
Total Number of Routes......................... 2

Network Subnet Next Hop Next Hop
Address Mask Protocol Intf IP Address
--------------- --------------- ------------ ------ ------------
10.0.1.0 255.255.255.0 Local 2/1 10.0.1.1
10.0.2.0 255.255.255.0 Local 2/2 10.0.2.1

STATIC ROUTING
2
show ip route bestroutes Check which routes the router actually uses for
the transmission.
Network Subnet Next Hop Next Hop

Address Mask Protocol Intf IP Address
--------------- --------------- ----------- --------- --------
10.0.1.0 255.255.255.0 Local 2/1 10.0.1.1
10.0.2.0 255.255.255.0 Local 2/2 10.0.2.1
Note: To be able to see these entries in the routing table, the port needs to have an active connection.

STATIC ROUTING
VLAN-based Router-Interface
2.2 VLAN-based Router-Interface
A characteristic of the VLAN-based router interface is that a number of devices in a VLAN are connected to
different ports. The devices within a subnet belong to one VLAN (see fig. 7).
Within a VLAN, the Switch exchanges data packets on layer 2. 

Terminal devices address data packets with a destination address in another subnet to the router as a gateway.
The router then exchanges the data packets layer 3.
Below you will find an example of the simplest case of a routing application with VLAN-based router interfaces.
For the VLAN 2, the router combines ports 3.1 and 3.2 into the VLAN router interface 9.1. A VLAN router interface
remains in the routing table until at least one port of the VLAN has a connection.
VLAN 1 10.0.2.6/24
10.0.1.5/24 Port 3.1
Interface 9.1 VLAN 2
A IP=10.0.2.1/24
Interface 2.1
IP=10.0.1.1/24 Port 3.2 10.0.2.5/24
Figure 9: VLAN-based router interface
Configuring a VLAN router interface:

vlan database Switch to the VLAN mode.
vlan 2 Create a VLAN by entering a VLAN ID. The VLAN
ID is in the range 1 to 4,042.
vlan name 2 Gerhard Assign the name “Gerhard” to the VLAN 2.
vlan routing 2 Create a virtual router interface and enable the
routing function for this interface.
show ip vlan Display the virtual router interface that the router
has set up for the VLAN.
show ip vlan 
Logical 
VLAN ID Interface IP Address Subnet Mask MAC Address 
------- ---------- ----------- ------------- ----------------- 
2 9/1 0.0.0.0 0.0.0.0 00:80:63:51:74:2C 
show ip interface brief Check the entry for the virtual router interface.
Netdir Multi
Interface IP Address IP Mask Bcast CastFwd
--------- --------------- --------------- -------- --------
9/1 0.0.0.0 0.0.0.0 Disable Disable

interface 9/1 Switch to the interface configuration mode of
interface 9/1.
ip address 10.0.2.1 Assign the IP parameters to the router interface.
255.255.255.0
routing Activate the router function at this interface.

STATIC ROUTING
2
ip netdirbcast Enable the transmission of net-directed

broadcasts for this interface.
interface 3/1 Change to the interface configuration mode of

interface 3/1.
vlan participation include 2 Include port 3.1 in VLAN 2.
vlan participation exclude 1 Exclude port 3.1 from VLAN 1. In the state of
delivery, every port is included in VLAN 1.
vlan pvid 2 Set the port VLAN-ID to 2, which means that data
packets that are received without a tag at that port
are assigned to VLAN 2 by the Switch.
interface 3/2 Change to the interface configuration mode of

interface 3/2.
vlan participation include 2 Include port 3.2 in VLAN 2.
vlan participation exclude 1 Exclude port 3.2 from VLAN 1. In the state of
delivery, every port is included in VLAN 1.
vlan pvid 2 Set the port VLAN-ID to 2, which means that data
packets that are received without a tag at that port
are assigned to VLAN 2 by the Switch.
show vlan 2 Check your entries in the static VLAN table.
VLAN ID: 2
VLAN Name: Gerhard
VLAN Type: Static
Interface Current Configured Tagging

---------- -------- ----------- --------
1/1 Exclude Autodetect Untagged
3/1 Include Include Untagged
3/2 Include Include Untagged
show vlan port all Check the VLAN-specific port setings.

STATIC ROUTING
Port Acceptable Ingress Default

Interface VLAN ID Frame Types Filtering Priority
--------- ------- ------------ ----------- --------
1/1 1 Admit All Disable 0
 Select the dialog Routing:Interfaces:Configuration.

 Click on “Assistant” at the bottom right to configure the VLAN router interface.
 Enter a number between 1 and 4,042 as the VLAN-ID, in this example: 2.

 Click on “Next” at the bottom.
 n the “VLAN Name” line above, enter a name with which you want to identify the VLAN.
 In the “Member” column of the table, you select the ports which will belong to this VLAN.
Click on “Next” at the bottom.
 In the “IP Address” line of the “Primary Address” frame, you enter the IP address for the VLAN.
 Enter the related network mask in the “Network mask” line.
 Click on “Close” to end the configuration of the VLAN-based router interface.
In the router interface table, the router interface 9.1 appears.
In the static VLAN table, the VLAN appears.
 Tick the box in the column „net-directed broadcasts“ for the router interface 9.1.
With “Delete“, you have the opportunity to delete a selected virtual router interface from the table or to reset
a physical router interface‘s entry.
Note: When you delete a VLAN router interface, the entry for the VLAN will remain in the VLAN table.
Deleting a VLAN deletes the VLAN router interface‘s entry in the router interface table.

STATIC ROUTING
2
Configuration of a Static Route
2.3 Configuration of a Static Route
In the example below, router A requires the information that it can reach the subnet 10.0.3.0/24 via the router B
(next hop). It can obtain this information via a dynamic routing protocol or via a static routing entry. With this
information, router A can transmit data from subnet 10.0.1.0/24 via router B into subnet 10.0.3.0/24.
Vice versa to be able to forward data of subnet 10.0.1.0/24 router B also needs an equivalent route.
Subnet 10.0.1.0/24 Subnet 10.0.3.0/24

Interface 2.1
10.0.1.5/24 IP=10.0.2.2 10.0.3.5/24
A B Interface 2.2
Interface 2.1
IP=10.0.1.1 Interface 2.2 IP=10.0.3.1
IP=10.0.2.1
Figure 10: Static Routing
You can enter static routing for port-based and VLAN-based router interfaces.
2.3.1 Configuration of a Static Route

Enter a static route for router A based on the configuration of the router interface in the previous example (see
fig. 8):

ip route 10.0.3.0 Create the static routing entry.
255.255.255.0 10.0.2.2
Total Number of Routes......................... 3

--------------- --------------- ------------ ------ -------------
10.0.1.0 255.255.255.0 Local 2/1 10.0.1.1
10.0.2.0 255.255.255.0 Local 2/2 10.0.2.1
10.0.3.0 255.255.255.0 Static 2/2 10.0.2.2
 Configure router B in the same way.

STATIC ROUTING
2.3.2 Configuration of a redundant static route

To ensure a reliable connection between the two routers, you can connect the two routers with two or more lines.
Subnet 10.0.1.0/24 Subnet 10.0.3.0/24

10.0.1.5/24 IP=10.0.4.1 IP=10.0.4.2 10.0.3.5/24
A B Interface 2.2
Interface 2.1
IP=10.0.1.1 Interface 2.2 Interface 2.1 IP=10.0.3.1
IP=10.0.2.1 IP=10.0.2.2
Figure 11: Redundant static route
You have the option of assigning importance (distance) to a route. If there are a number of routes to a destination,
then the router chooses the route with the highest importance. If you do not assign a value for the importance
during the configuration, the router takes the default value “1” for the importance. This is the highest importance.
 Configure router A.

interface 2/3 Select the port at which you want to connect the
redundant route.
ip address 10.0.4.1 Assign the port its IP parameters.
255.255.255.0
ip route 10.0.3.0 Create the static routing entry for the redundant
255.255.255.0 10.0.4.2 2 route. The “2” at the end of the command is the
importance value.
When both routes are available, the router uses
the route via subnetwork 10.0.2.0/24, because
this route has the higher importance (default
value = 1) (see on page 22 „Configuration of a
Static Route“).



Network Subnet Next Hop Next Hop
Address Mask Protocol Intf IP Address
--------------- --------------- ------------ ------ -------------
10.0.1.0 255.255.255.0 Local 2/1 10.0.1.1
10.0.2.0 255.255.255.0 Local 2/2 10.0.2.1
10.0.3.0 255.255.255.0 Static 2/2 10.0.2.2
10.0.3.0 255.255.255.0 Static 2/3 10.0.4.2
10.0.4.0 255.255.255.0 Local 2/3 10.0.4.1
the transmission.

STATIC ROUTING
2

--------------- --------------- ----------- --------- ---------
10.0.1.0 255.255.255.0 Local 2/1 10.0.1.1
10.0.2.0 255.255.255.0 Local 2/2 10.0.2.1
10.0.3.0 255.255.255.0 Static 2/2 10.0.2.2
10.0.4.0 255.255.255.0 Local 2/3 10.0.4.1
 Configure router B in the same way.

STATIC ROUTING
2.3.3 Configuration of a redundant static route with load sharing

The router shares the load between the two routes (load sharing), when the routes have the same importance
(distance).
ip route 10.0.3.0 assign the importance “2” to the existing static

255.255.255.0 10.0.2.2 2 routing entry (see on page 22 „Configuration of a
Static Route“).
When both routes are available, the router uses
both routes for the data transmission.

--------------- --------------- ------------ ------ -------------
10.0.1.0 255.255.255.0 Local 2/1 10.0.1.1
10.0.2.0 255.255.255.0 Local 2/2 10.0.2.1
10.0.3.0 255.255.255.0 Static 2/2 10.0.2.2
2/3 10.0.4.2
10.0.4.0 255.255.255.0 Local 2/3 10.0.4.1
the transmission.

--------------- --------------- ----------- --------- ---------
10.0.1.0 255.255.255.0 Local 2/1 10.0.1.1
10.0.2.0 255.255.255.0 Local 2/2 10.0.2.1
10.0.3.0 255.255.255.0 Static 2/2 10.0.2.2
2/3 10.0.4.2
10.0.4.0 255.255.255.0 Local 2/3 10.0.4.1

STATIC ROUTING
2
Static route tracking
2.4 Static route tracking
2.4.1 Description of the static route tracking function

With static routing, if there are a number of routes to a destination, the router chooses the route with the highest
importance. The router detects an existing route by the state of the router interface. While connection L 1 (see
fig. 12) on the router interface may be fine, the connection to remote router B at location L 2 may be interrupted.
In this case, the router continues transmitting via the interrupted route.
L1 L2
A B
L3
Figure 12: Example of static route tracking
With the static route tracking function, the router uses a tracking object such as a ping tracking object (see on
page 33 „Ping tracking“) to detect the connection interruption. The active static route tracking function then deletes
the interrupted route from the current routing table. If the tracking object returns to the “up” state, the router enters
the static route in the current routing table again.
2.4.2 Application example for the static route tracking function

The figure (see fig. 13) shows an example of the static route tracking function:
Router A monitors the best route via L 1 with ping tracking. If there is a connection interruption, router A transmits
via redundant connection L 3.
The following is known:
Parameter Router A Router B

IP address interface (IF) 1.1 10.0.4.1
IP address interface (IF) 1.2 10.0.2.1 10.0.4.2
Netmask 255.255.255.0 255.255.255.0

STATIC ROUTING
Prerequisities for further configuration:

 The IP parameters of the router interface are configured.
(see on page 17 „Configuration of the Router Interfaces“)
 The router function is activated globally and at the ports/router interface.
 Ping tracking at interface 1.2 of router A is configured (see on page 37 „Application example for ping tracking“).
10.0.2.0/24
IF 1.4 IF 1.2 IF 1.3 IF 2.2
A B
IF 1.1 IF 1.2
10.0.4.0/24
10.0.1.0/24 10.0.5.0/24
Figure 13: Configuring static route tracking
 Enter the two routes to destination network 10.0.5.0/24 in the static routing table of router A.
 Select the dialog 

Routing:Routing Table:Static.
 Click on “Create Entry”.
You thus open the input window for a new entry.
 Enter the data for the first static route:
“Destination Network” 10.0.5.0
“Destination Netmask” 255.255.255.0
“Next Hop” 10.0.2.53
“Track ID” 21
 Click on „OK“.
 Click on “Create Entry”.
You thus open the input window for a new entry.
 Enter the data for the first static route:
“Destination Network” 10.0.5.0
“Destination Netmask” 255.255.255.0
“Next Hop” 10.0.4.2
“Track ID” 0
 Click on „OK“.

ip route 10.0.5.0 Create the static routing entry with preference 1
255.255.255.0 10.0.2.53 1 and track ID 21.
track 21
ip route 10.0.5.0 Create the static routing entry with preference 2.
255.255.255.0 10.0.4.2 2

STATIC ROUTING
2

-------------- --------------- ------------ ------ -------------
10.0.1.0 255.255.255.0 Local 1/4 10.0.1.112
10.0.2.0 255.255.255.0 Local 1/2 10.0.2.1
10.0.5.0 255.255.255.0 Static 1/2 10.0.2.53
 On router B, create a ping tracking object with the track ID, for example 22, for IP address 10.0.2.1.
 Enter the two routes to destination network 10.0.1.0/24 in the static routing table of router B.
Destination Destination Next Hop Preference Track ID

Network Netmask
10.0.1.0 255.255.255.0 10.0.2.1 1 22
10.0.1.0 255.255.255.0 10.0.4.1 2
Table 3: Static routing entries for router B

STATIC ROUTING
Adaptation for non-IP-compliant devices
2.5 Adaptation for non-IP-compliant devices
Some devices use a simplfied IP stack that does not correspond to the IP standard. Without an ARP request, these
devices send their responses to the MAC address contained as the source address in the requesting packet (see
figure below, no MAC/IP address resolution). These devices exhibit this behavior with ping requests in particular
(ICMP echo request). Some of these devices also exhibit this behavior with other data packets.
As long as the router interface of the router to which such a device is connected is itself connected to the MAC
address of the physical port, the router can receive and transmit the packet.
However, if the physical port belongs to a VLAN, the VLAN router interface then has its own MAC address. Thus
the router rejects packets that are being sent to the port's MAC address.
A terminal device that performs the MAC/IP address resolution according to the IP standard starts an ARP request
to determine the correct MAC address before sending the reply to the determined VLAN MAC address (see figure
below: MAC/IP standard address resolution using ARP).
Source: 00:80:63:00:00:01 no MAC/IP

:01 address
: : 00 resolution
AC :00 Destination:00:80:63:00:00:01
M 3
rt :6
Po :80
00
A VLAN MAC:00:80:63:00:22:00
P
00 ort M
:8
0: AC Source: 00:80:63:00:00:02 MAC/IP address
63 :
:0 resolution via ARP
0:
00 complying with
:0 Destination:00:80:63:00:22:00
2 standard
Figure 14: Addressing with simplified IP stack and compliant with the standard
For you also to be able to connect devices with a simplified IP stack to a VLAN-based router interface, the router
provides you with the VLAN single MAC mode. 
In the VLAN single MAC mode, all VLAN interfaces and all physical ports use the same MAC address, with the
exception of the port-based router interface.
 Activating the VLAN single MAC mode:

ip vlan-single-mac Activating the VLAN single MAC mode.
show ip vlan Display the VLAN IP parameters

Logical
VLAN ID Interface IP Address Subnet Mask MAC Address
------- --------- ------------- ------------- -----------------
100 9/1 192.168.100.1 255.255.255.0 00:80:63:51:74:2B
200 9/2 192.168.200.1 255.255.255.0 00:80:63:51:74:2B

STATIC ROUTING
2
Adaptation for non-IP-compliant devices

TR A C K I N G
3 Tracking
The tracking function gives you the option of monitoring certain objects, such as the availability of an interface. 
A special feature of this function is that it forwards an object status change to an application, e.g. VRRP, which
previously registered as an interested party for this information.
Tracking can monitor the following objects:

 Link status of an interface (interface tracking)
 Accessibility of a device (ping tracking)
 Result of logical connections of tracking entries (logic tracking)
An object can have the following statuses:

 up (OK)
 down (not OK)
The definition of "up" and "down" depends on the type of the tracking object (e.g. interface tracking).
Tracking can forward the state changes of an object to the following applications:
 VRRP (see on page 52 „VRRP tracking“)
 Static routing (see on page 26 „Static route tracking“)

TR A C K I N G
3
Interface tracking
3.1 Interface tracking
With interface tracking the Switch monitors the link status of:
 physical ports
 link aggregation interfaces (interfaces 8.x)
 VLAN router interfaces (interfaces 9.x)
S1 S2
L1 L2
A PC B
PC A
VR
B
Figure 15: Monitoring a line with interface tracking
Ports/interfaces can have the following link statuses:

 interrupted physical link (link down) and
 existing physical link (link up).
A link aggregation interface has link status “down” if the link to all the participating ports is interrupted.
A VLAN router interface has link status “down” if the link is interrupted from all the physical ports/link aggregation
interfaces that are members of the corresponding VLAN.
Setting a delay time enables you to insert a delay before informing the application about an object status change.
An interface tracking object is given the “down” status if the physical link interruption remains for longer than the
“link down delay” delay time.
An interface tracking object is given the “up” status if the physical link holds for longer than the “link up delay” delay
time.
State on delivery: delay times = 0 seconds. 
This means that if a status changes, the registered application is informed immediately.
You can set the “link down delay” and “link up delay” delay times independently of each other in the range from 0
to 255 seconds.
You can define an interface tracking object for each interface.

TR A C K I N G
Ping tracking
3.2 Ping tracking
With ping tracking, the device uses ping requests to monitor the link status to other devices.
S2
L1 L2
A PC B
PC A
Figure 16: Monitoring a line with ping tracking
The device sends ping requests to the device with the IP address that you entered in the “IP Address” column.
The “Ping Interval” column allows you to define the frequency for sending ping requests, and thus the additional
network load.
If the response comes back within the time entered in the “Ping Timeout” column, this response is a valid “Ping
response received”.
If the response comes back after the time entered in the “Ping Timeout” column, or not at all, this response is
evaluated as “No ping response”.
Ping tracking objects can have the following statuses:

 the number of “No ping responses” is greater than the number entered (down) and
 the number of “Ping responses received” is greater than the number entered (up).
Entering a number for unreceived or received ping responses enables you to set the sensitivity of the ping behavior
of the device. The device informs the application about an object status change.
Ping tracking enables you to monitor the accessibility of defined devices. As soon as a monitored device can no
longer be accessed, the device can choose to use an alternative path.

TR A C K I N G
3
Ping tracking
Figure 17: Ping Tracking dialog

TR A C K I N G
Logical tracking
3.3 Logical tracking
Logical tracking enables you to logically link multiple tracking objects with each other and thus perform relatively
complex monitoring tasks.
You can use logical tracking, for example, to monitor the link status for a network node to which redundant paths
lead (see on page 38 „Application example for logical tracking“).
The device provides the following options for a logical link:

 AND
 OR
For a logical link, you can combine up to 8 operands with one operator.
Logical tracking objects can have the following statuses:

 The result of the logical link is incorrect (down).
 The result of the logical link is correct (up).
When a logical link delivers the result “incorrect”, the device can choose to use an alternative path.

TR A C K I N G
3
Configuring the tracking
3.4 Configuring the tracking
You configure the tracking by setting up tracking objects. The following steps are required to set up a tracking
object:
 Enter the tracking object ID number (track ID).
 Select a tracking type, e.g. interface.
 Depending on the track type, enter additional options such as “port” or “link up delay” in the interface tracking.
Note: The registration of applications (e.g. VRRP) to which the tracking function reports status changes is
performed in the application itself (see on page 52 „VRRP tracking“).
3.4.1 Configuring interface tracking
 Set up interface tracking at port 1.1 with a link down delay of 0 seconds and a link up delay of 3 seconds.
 In the Routing:Tracking:Configuration dialog, click on “Wizard” at the bottom right.
Select type:
 Enter the values you desire:
Track ID: 1
Type: interface
 Click on “Continue”.
Properties:
Module.Port: 1.1
Link up delay: 3
Link down delay: 0
 Click on “Finish” to leave the Wizard and save the entry temporarily in the configuration.

track 1 interface 1/1  Enter the tracking parameters and activate this tracking object.
link-down-delay 0 
link-up-delay 3
Tracking ID 1 created
Tracking type set to Interface
Target interface set to 1/1
Link Down Delay for target interface set to 0 sec
Link Up Delay for target interface set to 3 sec
Tracking ID 1 activated
show track Display the configured tracks

TR A C K I N G
Link Delay No. of

ID Type Intf Down Up Status Mode Changes Time since last change
-- ---- ---- ---- ----- ------ ------ ------- -------------------- 
1 Intf 1/1 0s 3s DOWN Enable 0 0 day(s), 00:00:29 
Unconfigured Track-IDs with registered applications: 
----------------------------------------------------
3.4.2 Application example for ping tracking

While the interface tracking monitors the directly connected link (see fig. 15), the ping tracking monitors the entire
link to Switch S2 (see fig. 16).
 Set up ping tracking at port 1.2 for IP address 10.0.2.53 with the preset parameters.
Select type:
Track ID: 21
Type: ping
Properties:
IP address: 10.0.2.53
Module.Port: 1.2
Ping interval [s]: 1
No ping response: 3
Ping responses received: 2
Ping timeout [ms]: 100

track 21 ping 10.0.2.53 interface 1/2 Enter the tracking parameters and activate this tracking object.
interval 1 miss 3 success 2 timeout 100
Tracking type set to Ping
Target IP address set to 10.0.2.53
Interface used for sending pings to target set to 1/2
Ping Interval for target set to 1 sec
Max. no. of missed ping replies from target set to 3
Min. no. of received ping replies from target set to 2
Timeout for ping replies from target set to 100 ms
Ping Tracking
No. of Time since
ID Type IP Address Intvl Status Mode Changes last change
--- ---- ----------- ----- ------ ------ ------- -----------------
21 Ping 10.0.2.53 1s DOWN Enable 1 0 day(s), 00:13:39

TR A C K I N G
3
3.4.3 Application example for logical tracking

The figure (see fig. 15) shows an example of monitoring the connection to a redundant ring.
By monitoring lines L 2 and L 4, you can detect a line interruption from router A to the redundant ring.
With a ping tracking object at port 1.1 of router A, you monitor the connection to Switch S2.
With an additional ping tracking object at port 1.1 of router A, you monitor the connection to Switch S4.
Only the OR link of both ping tracking objects delivers the precise result that router A has no connection to the ring.
One ping tracking object for Switch S3 could indicate an interrupted connection to the redundant ring, but in this
case there could be another reason for the lack of a ping response from Switch S3. For example, there could be
a power failure at Switch S3.
The following is known:
Parameter Value
Operand No. 1 (track ID) 21
Operand No. 2 (track ID) 22
Prerequisities for further configuration:

 The ping tracking objects for operands 1 and 2 are configured (see on page 37 „Application example for ping
tracking“).
S1 S2
L2
L1
PC B
L4 L3
A
PC A S4 S3
VR
B
S5
S6
Figure 18: Monitoring the accessibility of a device in a redundant ring
 Set up a logical tracking object as an OR link.

Select type:
Track ID: 31
Type: Logical
Properties:
Operator: or
Operand 1 (track ID): 21
Operand 2 (track ID): 22

TR A C K I N G

track 31 logical or 21 22 Enter the tracking parameters and activate this tracking object.
Tracking type set to Logical
Logical Operator set to or
Logical Instance 21 included
Logical Instance 1 included
Ping Tracking
--- ---- ----------- ----- ------ ------ ------- -----------------

Ping Tracking
--- ---- ----------- ----- ------ ------ ------- -----------------
Logical Tracking
No. of
ID Type Instances Status Mode Changes Time since last change
--- ---- ----------- ------ ------- ------- ----------------------
31 OR 21,22 DOWN Enable 0 0 day(s), 00:04:58

TR A C K I N G
3

VRRP/E-VRRP
4 VRRP/E-VRRP
Terminal devices usually give you the option of entering a default gateway for transmitting data packets in external
subnetworks. Here the term “Gateway” applies to a router by means of which the terminal device can communicate
in other subnetworks.
If this router fails, the terminal device cannot send any more data to external subnetworks. 
In this case, the Virtual Router Redundancy Protocol (VRRP) provides assistance. 
VRRP is a type of “gateway redundancy”. VRRP describes a process that groups multiple routers into one virtual
router. Terminal devices always address the virtual router, and VRRP ensures that a physical router belonging to
the virtual router takes over the data transmission.
Even if a physical router fails, VRRP ensures that another physical router takes over the distribution tasks as part
of the virtual router.
VRRP has typical switching times of 3 to 4 seconds when a physical router fails.
In many cases, such as Voice over IP, Video over IP, industrial controllers, etc., these long switching times are not
acceptable.
VRRP was further developed into the E-VRRP (Enhanced Virtual Router Redundancy Protocol).
With the appropriate configuration, E-VRRP guarantees maximum switching times of 400 milliseconds.
Thanks to this guaranteed switching time, E-VRRP enables the use of “gateway redundancy” in time-critical
applications. Even in tunnel controllers that require switching times of less than one second, the user can improve
the network availability with this form of “gateway redundancy”.

VRRP/E-VRRP
4
VRRP
4.1 VRRP
All the routers within a network on which VRRP is active specify among themselves which router is to be the
master. This router contains the IP and MAC address of the virtual router. All the devices in the network that have
entered this virtual IP address as the default gateway use the master as the default gateway.
Redundancy
through VRRP
10.0.1.13
10.0.1.12 10.0.1.1
Default Gateway A
10.0.1.254 10.0.1.11 10.0.1.254 VR
B
10.0.1.2
10.0.1.10
Figure 19: Illustration of the virtual router
If the master fails, then the remaining routers use the VRRP to specify a new master. This router then takes over
the IP and MAC address of the virtual router. Thus the devices find their route via their default gateway, as before.
The devices always only see the master with the virtual MAC and IP addresses, regardless of which router is
actually behind this virtual address. 
The virtual router IP address is assigned by the administrator. 
The VRRP specifies the virtual MAC address with: 
00:00:5e:00:01:<VRID>. 
The first 5 octets form the fixed part in accordance with RFC 2338. 
The last octet is the virtual router ID (VRID). It is a number between 1 and 255. On the basis of this, the
administrator can define 255 virtual routers within a network.
00:00:5e:00:01:xx
variable element = VRID

constant element
Figure 20: Virtual MAC address
The VRRP router sends IP Multicast messages to the IP Multicast address 224.0.0.18 in order to determine the
master. The router with the highest VRRP priority becomes the master. The VRRP priority is specified by the
administrator. If the VRRP priorities are the same, then the highest IP interface address of the VRRP routers is
decisive. If the virtual IP address is the same as the IP address of a router interface, then this router is the IP
address owner. VRRP sets the VRRP priority of an IP address owner to the value 255 and thus declares it the
master. If there is no IP address owner, then VRRP declares the router with the highest VRRP priority the master.
The master regularly sends IP Multicast messages (default: 1 s) to the other VRRP routers in order to signal that
it is ready for operation. If this message does not appear three times in a row, then the VRRP router with the
highest remaining VRRP priority declares itself the new master.

VRRP/E-VRRP
VRRP
1. The IP address owner as it has the highest VRRP priority (255) by definition.
2. The VRRP router with the highest VRRP priority.
3. If the priorities are the same, the VRRP router with the highest IP address.
Table 4: Who shall be the master?
VRRP terms:
 Virtual router
A virtual router is a router or group of routers that act as the default gateway in a network and use the Virtual
Router Redandancy Protocol.
 VRRP router
A VRRP router is a router that uses VRRP. It can be part of one or more virtual routers.
 Master router
The master router is the router within the virtual router that is currently responsible for forwarding data packets
and responding to ARP queries. The master router periodically sends messages (advertisements) to the other
VRRP routers (backup routers) to inform them about its existence.
 IP address owner
The IP address owner is the VRRP router whose IP address is identical to the IP address of the virtual router.
By definition, it has the highest VRRP priority (255) and is thus automatically the master router.
 Backup router
The backup router is a VRRP router that is not the master router. The backup router is ready to take over the
master role, should the master fail.
 VRRP priority
The VRRP priority is a number between 1 and 255. It is used to determine the master router. The value 255 is
reserved for the IP address owner.
 VRID
The VRID (virtual router ID) uniquely identifies a virtual router.
 Virtual router MAC address
The virtual router MAC address is the MAC address of the virtual router (see fig. 4).
 Virtual router IP address
The virtual router IP address is the IP address of the virtual router.
 Advertisement interval
The advertisement interval describes the frequency with which the master router sends its existence message
(advertisement) to all the VRRP routers of its virtual router. The values for the advertisement interval are
between 1 and 255 seconds. The default value is 1 second.
 Skew time
The skew time is the time, dependent on the VRRP priority, that specifies the time when the backup router
names itself the master router. 
Skew time = ((256 - VRRP priority) / 256) * 1 second
 Master down interval
The master down interval specifies the time when the backup router names itself the master router. 
Master down interval = 3 * advertisement interval + skew time

VRRP/E-VRRP
4
VRRP
4.1.1 Configuration of VRRP
The configuration of VRRP requires the following steps:

 Switch on routing globally (if this has not already been done).
 Switch on VRRP globally.
 Configure port - assign IP address and network mask.
 Switch on VRRP at the port.
 Create virtual router ID (VRID), because you have the option of activating a multiple virtual routers for each port.
 Assign virtual router IP address.
 Switch on virtual router.
 Assign VRRP priority.

ip vrrp Switch on VRRP globally.
interface 2/3 Select the port for setting up VRRP.

ip address 10.0.1.1 255.255.255.0 Assign the port its IP parameters.
ip vrrp 1 Create the VRID for the first virtual router at this port.
ip vrrp 1 mode Switch on the first virtual router at this port.
ip vrrp 1 ip 10.0.1.100 Assign virtual router 1 its IP address.
ip vrrp 1 priority 200 Assign virtual router 1 the router priority 200.
 You configure every port at which VRRP will be active in the same way.
 You also perform the same configuration on the redundant router.

VRRP/E-VRRP
E-VRRP
4.2 E-VRRP
E-VRRP provides a number of mechanisms for shortening the switching times or reducing the number of
Multicasts:
 shorter advertisement intervals
 link-down notification
 preempt delay
 Unicast advertisement
 domains
In compliance with RFC 2338, the master sends IP Multicast messages (advertisements) at intervals of one
second to the other VRRP routers. Only if this message does not appear three times do the remaining routers
select a new master. 
VRRP has typical switching times of 3 to 4 seconds.
3 * Advertisement Skew-Time
Interval
Router A Backup Router
Advertisement
Master Router
Router B Backup Router
Advertisement
Master Router
Router C
0 1 2 3 4 5 6 t [s]
Figure 21: Master router <-> backup router switching times according to RFC 2338
VRRP priority router A = 64
VRRP priority router B = 128
VRRP priority router C = 254
To be able to achieve faster switching times, ABB provides E-VRRP so that the cycle for sending the IP Multicast
message can be shortened to as little as 0.1 seconds. You can thus achieve switching times that are up to ten
times as fast.
The router supports up to 16 VRRP router interfaces with this shortened sending cycle.
 E-VRRP skew time

The E-VRRP skew time is the time, dependent on the VRRP priority, that specifies the time when the E-VRRP
backup router names itself the E-VRRP master router.
E-VRRP skew time = 
(256 - VRRP priority) / 256 * advertisement interval
Times shown in milliseconds

VRRP/E-VRRP
4
E-VRRP
 E-VRRP master down interval

The E-VRRP master down interval specifies the time when the E-VRRP backup router names itself the E-
VRRP master router. 
E-VRRP master down interval = 
3 * advertisement interval + E-VRRP skew time
Times shown in milliseconds
3 * Advertisement Skew-Time
Interval
Router A Backup Router
Advertisement
Master Router
Router B Backup Router
Advertisement
Master Router
Router C
0 0,1 0,2 0,3 0,4 0,5 0,6 t [s]
Figure 22: Master router <-> backup router switching times according to E-VRRP
VRRP priority router A = 64
VRRP priority router B = 128
VRRP priority router C = 254
Another option provided by E-VRRP for shortening the switching times dramatically is the link-down notification.
You can use this function when the virtual router consists of two VRRP routers. As two VRRP routers are
participating, it is sufficient to send the link-down notification in the form of a Unicast message. In contrast to the
Multicast message, the Unicast message travels beyond the boundaries of the subnetwork. This means that if the
link is down to your own subnetwork, the link-down notification can also travel via another subnetwork to reach the
second router of the virtual router.
As soon as E-VRRP detects that the link is down, it sends the link-down notification to the second router via a
different route. The second router takes over the master function immediately after receiving the link-down
notification.
In the preempt mode, the backup router can take over the master function from the master router as soon as the
backup router receives an advertisement from the master router for which the VRRP priority is lower than its own.
Thus the preempt mode, in collaboration with VRRP tracking (see page 52), can enable a switch to a better router.
However, dynamic routing procedures take a certain amount of time to react to changed routes and refill their
routing table.
To avoid the loss of packets during this time, delayed switching (preempt delay) from the master router to the
backup router enables the dynamic routing procedure to fill the routing tables.
E-VRRP provides an additional advantage for networks with devices that have problems with higher volumes of
Multicasts. Instead of sending advertisements in the form of Multicasts, E-VRRP can send the advertisements in
the form of Unicast data packets (VRRP destination address) when using up to two E-VRRP routers.

VRRP/E-VRRP
E-VRRP
Note: If you want to avail of the advantages of E-VRRP, then only use VRRP routers equipped with the E-VRRP
function from ABB as the virtual router.

VRRP/E-VRRP
4
E-VRRP Domains
4.3 E-VRRP Domains
In large, flat network structures, E-VRRP domains enable you to

 switch over all E-VRRP routers very quickly in the case of redundancy
 use the available bandwidth more effectively
 configure more than 16 VRRP router interfaces for each router using E-VRRP
 operate Multicast-sensitive terminal devices in large E-VRRP networks
A E-VRRP instance is a router interface configured as E-VRRP with functions that E-VRRP contains. In a E-VRRP
domain you combine multiple E-VRRP instances of a router into one administrative unit. You nominate one E-
VRRP instance as the supervisor of the E-VRRP domain. This supervisor regulates the behavior of all E-VRRP
instances in its domain.
 The supervisor sends its advertisements on behalf of all E-VRRP instances in its domain.
 The supervisor puts itself and the other E-VRRP instances together into the master role or the backup role.
See fig. 23 for an example of a flat network structure. All cross-VLAN data streams pass through the ring.
VLAN 1 + 2 + 3 + 4 E-VRRP 11 (+ 12 + 13 + 14)

E-VRRP- E-VRRP-
Domain 1 Domain 1
VR ID 11 Virtual Router 1 VR ID 11
A B
VLAN Router
Interfaces
Subnet A Subnet B Subnet C Subnet D

VLAN 1 VLAN 2 VLAN 3 VLAN 4
Figure 23: Example of how a E-VRRP domain is used

VRRP/E-VRRP
E-VRRP Domains
4.3.1 Configuration of E-VRRP domains

The configuration of E-VRRP domains consists of the following steps:
 Create VLANs
 Configure VLAN router interfaces
 Assign the IP addresses to the router interfaces
 Configure E-VRRP instances
– Activate VRRP instance (all instances)
– Assign IP address (all instances)
Within a router, you either configure all instances as IP address owners, or no instance as an IP address
owner.
– Assign priority (supervisor)
Assign the supervisors different priorities so that the VRRP routers can agree on a master router.
– Switch on E-VRRP (all instances)
– Assign to the domain (all instances)
– Specify sending interval (supervisor)
 Configure Ring-Redundancy (in applications as in the above example)
 Define the (Ring) ports as members of the VLANs
 Switch on routing and VRRP globally
4.3.2 Example of configuration of E-VRRP domains
Example of possible settings for the application in fig. 23:
Subnetwork IP address range VLAN VLAN ID

A 10.0.11.0/24 1 11
B 10.0.12.0/24 2 12
C 10.0.13.0/24 3 13
D 10.0.14.0/24 4 14
Table 5: Configuration of the Switches in the subnetwork
Virtual router VR ID IP address of the Router interface of Router interface of VLAN ID

virtual router router A: IP address router B: IP address
1 11 10.0.11.1/24 10.0.11.2/24 10.0.11.3/24 11
2 12 10.0.12.1/24 10.0.12.2/24 10.0.12.3/24 12
3 13 10.0.13.1/24 10.0.13.2/24 10.0.13.3/24 13
4 14 10.0.14.1/24 10.0.14.2/24 10.0.14.3/24 14
Table 6: Configuration of the two routers
 Configure VLAN router interface and assign IP address:

vlan 11 Create a VLAN by entering the VLAN ID.

VRRP/E-VRRP
4
E-VRRP Domains
vlan name 11 VLAN1 Assign the name “VLAN1” to VLAN 11.

vlan routing 11 Create a virtual router interface and activate the router function at this interface.
show ip vlan Display the virtual router interface that the router
has set up for the VLAN.
show ip vlan Logical
VLAN ID Interface IP Address Subnet Mask MAC Address
------- ---------- ----------- ------------- ------------
11 9/1 0.0.0.0 0.0.0.0 00:80:63:51:74:2C
show ip interface brief Check the entry for the virtual router interface.
Netdir Multi
--------- --------------- --------------- -------- --------
9/1 0.0.0.0 0.0.0.0 Disable Disable

interface 9/1 Switch to the interface configuration mode of interface 9/1.
ip address 10.0.11.2 Assign the interface its IP parameters.
255.255.255.0
 Set up virtual router and configure port
ip vrrp 1 domain 1 supervisor Assign the E-VRRP domain and the domain role to the interface.
ip vrrp 1 timers advertise Assign the E-VRRP notification interval to the interface.
milliseconds 100
show ip vrrp interface 9/1 1 Display the configuration of VLAN 11


Primary IP Address............................. 10.0.11.1
VMAC Address................................... 00:00:5e:00:01:01
Authentication Type............................ None
Base Priority.................................. 200
Advertisement Interval (milliseconds).......... 100
Pre-empt Mode.................................. Enable
Administrative Mode............................ Enable
State.......................................... Initialized
Current Priority............................... 200
Preeption Delay (seconds)...................... 0
Link Down Notification......................... Disabled
VRRP Domain.................................... 1
VRRP Domain Role............................... Supervisor
VRRP Domain State.............................. Supervisor is down
Advertisement Address.......................... 224.0.0.18
 Define the (Ring) port as a member of the VLAN
interface 2/1 Switch to the Interface Configuration mode of interface 2.1.

vlan participation include 11 Assign the interface to the VLAN.
show vlan 11 Display the configuration of VLAN 11

VRRP/E-VRRP
E-VRRP Domains

VLAN ID : 11
VLAN Name : VLAN1
VLAN Type : Static
VLAN Creation Time: 0 days, 00:00:06 (System Uptime)

Interface Current Configured Tagging
---------- -------- ----------- --------
1/1 Exclude Autodetect Untagged
2/1 Include Include Untagged
Switch on routing and VRRP globally


VRRP/E-VRRP
4
VRRP tracking
4.4 VRRP tracking
By monitoring certain router statuses (e.g. line interruption), VRRP tracking makes it possible to switch to a better
router when a link goes down.
If there is a line interruption between Switch S1 and router A (see fig. 25), router B takes over the master function
for virtual router 10.0.1.254. 
Router A remains the master for virtual router 10.0.2.254. However, router A no longer has a link to subnetwork
10.0.1.0. 
The virtual router interfaces are independent of each other.
Default Gateway Default Gateway

10.0.1.254 10.0.2.254
S1 Priority=200
10.0.1.20 10.0.1.1
A
10.0.1.254 VR VR 10.0.2.254
B
10.0.1.2
Priority=100
Figure 24: Typical VRRP application
As soon as the VRRP master router with the VRRP tracking function active detects the interruption of one of its
links, it lowers its VRRP priority and informs the other VRRP routers of this. 
Then another VRRP router, which now has the highest priority due to this change in the situation, can take over
the master function within the skew time.
Solution without tracking:

Configure router A with a static route to router B or with a dynamic routing procedure, so that router A finds a route
into subnetwork 10.0.1.0.
A direct link with preference 0 is the best route. 
The static route with preference 1 is the second-best route. Then comes the dynamic route.

VRRP/E-VRRP
VRRP tracking

10.0.1.100 10.0.2.100
S1 Master
PC A 10.0.1.1
A
10.0.1.254 VR VR 10.0.2.254
B PC B
10.0.1.2
Slave
Figure 25: Transmission path from PC B to PC A in the case of a line interruption without tracking
The data from PC B is then transferred to PC A via router A and router B.
Solution with tracking:

For an optimal route, you can now use the tracking function to also make router B the master for virtual router
10.0.2.254.
By "tracking" the interrupted link and registering the virtual routers for this tracking object (see on page 31
„Tracking“), router A decrements its VRRP priority. Thus when router B receives the next advertisement from
router A, router B detects that its own VRRP priority is higher than that of router A and takes over the master
function (see fig. 26).
Note: As the IP address owner has the fixed VRRP priority 255 by definition, the VRRP tracking function requires
the IP addresses of the VRRP router interfaces to differ from the virtual router IP address.
Note: For the backup router to be able to take over the master function from the master router with the lower
priority, the VRRP tracking function requires that the preempt mode is activated.

10.0.1.254 10.0.2.254
S1 Priority=150
10.0.1.20 10.0.1.1 10.0.2.1
Port 1.1 A Port 1.2
10.0.1.254 VR VR 10.0.2.254
Port 1.1 10.0.2.2
B
10.0.1.2 Port 1.2
Priority=200
Figure 26: VRRP tracking after a line interruption

VRRP/E-VRRP
4
VRRP tracking
Router A Router A Router B Router B

Interface 1.1 1.2 1.2 1.1
IP address 10.0.1.1/24 10.0.2.1/24 10.0.2.2/24 10.0.1.2/24
VRID 1 2 2 1
VRRP IP address 10.0.1.254 10.0.2.254 10.0.2.254 10.0.1.254
VRRP priority 250 250 200 200
VRRP preemption Enabled Enabled Enabled Enabled
Track ID 2 1 - -
Track decrement 100 100 - -
Table 7: VRRP tracking configuration for the example above
Router A Router A Router B Router B

Track ID 1 2 - -
Type Interface Interface - -
Interface 1.1 1.2 - -
Table 8: Tracking configuration for the example above
The configuration of VRRP tracking requires the following steps:

 Configure the tracking object 
(see on page 36 „Configuring the tracking“).
 Configure the VRRP.
 Add the track ID to the VRRP entry (= register the VRRP entry for the tracking object).
 Set up interface tracking at port 1.1 with a link down delay of 0 seconds and a link up delay of 3 seconds.

Select type:
Track ID: 1
Type: interface
Properties:
Module.Port: 1.1
Link up delay: 3
Link down delay: 0

track 1 interface 1/1 link-down-delay 0 link-up-delay Enter the tracking parameters and activate this tracking object.
3
 Switch on routing and VRRP globally.

VRRP/E-VRRP
VRRP tracking
 Select the Routing:Global dialog.

 Select “Routing”.
 Click “Set” to temporarily save the entry in the configuration.
 Select the dialog 
Redundancy:VRRP/E-VRRP:Configuration.
 Select “Operation”.
 Click “Set” to temporarily save the entry in the configuration.

 Configure the IP address and VRRP at port 1.2.
 In the Redundancy:VRRP/E-VRRP:Configuration dialog, click “Wizard” at the bottom right.

Create entry:
“Module”: 1
“Port”: 2
“VRID”: 2
Edit entry:
“VRRP IP address”: 10.0.2.254
“Priority”: 250
“Preempt mode”: 1
interface 1/2 Select the port for setting up VRRP.

ip address 10.0.2.1 255.255.255.0 Assign the port its IP parameters.
 Register VRRP for the tracking object.
Tracking
“Track ID”: 1
“Decrement”: 100
 Click on “Add”.

VRRP/E-VRRP
4
VRRP tracking
ip vrrp 2 track 1 decrement 100 Register the first VRRP entry for the tracking object.
show track applications Display the registered applications.
TrackId Application Changes Time since last change
------- ---------------------- ------- --------------------- 
1 VRRP 1/2 VRID: 2 0 0 day(s), 00:38:24
 You also perform the same configuration on the redundant router.

VRRP/E-VRRP
VRRP with load sharing
4.5 VRRP with load sharing
With the simple configuration, a router performs the gateway function for all terminal devices. The capacity of the
redundant router lies idle. VRRP allows you to also use the capacity of the redundant router. By setting up a
number of virtual routers, you can enter different default gateways on the connected terminal devices and thus
steer the data flow.
When both routers are active, the data flows via the router on which the IP address of the default gateway has the
higher VRRP priority. If a router fails, then all the data flows via the remaining routers.
IP=10.0.1.1:
10.0.1.13 VRID=1, VR-IP=10.0.1.100, Priority= 200
VRID=2, VR-IP=10.0.1.200, Priority=100
Default Gateway
10.0.1.100 10.0.1.12
A
10.0.1.11 10.0.1.100
10.0.1.200 VR
Default Gateway B
10.0.1.200 10.0.1.10
IP=10.0.1.2:
Figure 27: Virtual router with load sharing
To use load sharing, you perform the following configuration steps:

 Define a second VRID for the same router interface.
 Assign the router interface its own IP address for the second VRID.
 Assign the second virtual router a lower priority than the first virtual router.
 When configuring the redundant router, make sure that you assign the second virtual router a higher priority
than the first.
 Give the terminal devices one of the virtual router IP addresses as a default gateway.

VRRP/E-VRRP
4
VRRP with Multinetting
4.6 VRRP with Multinetting
The router allows you to combine VRRP with Multinetting.
10.0.1.13 IP=10.0.1.1
IP=10.0.2.1
Default Gateway
10.0.1.100 10.0.1.12
A
10.0.1.11 10.0.1.100
10.0.2.100 VR
B
Default Gateway
10.0.2.100 10.0.2.13
IP=10.0.1.2
IP=10.0.2.2
Figure 28: Virtual router with multinetting
To use VRRP with multinetting, you perform the following configuration steps on the basis of an existing VRRP
configuration (see fig. 19):
 Assign a second (secondary) IP address to the port.
 Assign a second (secondary) IP address to the virtual router.
interface 2/3 Select the port at which you want to configure multinetting.
ip address 10.0.2.1 255.255.255.0 secondary Assign the second IP address to the port.
ip vrrp 1 ip 10.0.2.100 secondary Assign the second IP address to the virtual router with the VR-ID 1.
 Perform the same configuration on the redundant router also.

RIP
5 RIP
The Routing Information Protocol (RIP) is a routing protocol based on the distance vector algorithm. It is used for
the dynamic creation of the routing table for routers.
When you start a router, the router only knows the networks directly connected to it, and it sends this routing table
to the neighboring routers. At the same time, it requests the routing tables of its neighboring routers. The router
adds this information to its routing table and thus learns which networks can be accessed via which routers, and
how much effort is involved in this. In order to detect changes in the network (when a router fails or starts), the
routers regularly repeat the exchange of all the routing tables, usually every 30 seconds. This involves a
considerable bandwidth requirement in large networks.
The costs, also known as the metric, refer to the work involved in reaching a particular network. RIP uses the hop
count for this, which describes the number of routers that are traversed along the path to the destination network.
The name 'distance vector' is derived from the fact that the distance (metric) is the criterion for determining the
route, and the direction is specified by the next hop (vector). The next hop refers to the neighboring router along
the path to the destination address.
An entry in the routing table consists of the address of the next hop, the destination address and the metric. The
RIP routing table always contains the most efficient route to the destination. This is the route with the smallest
metric and the longest suitable network mask prefix.
HC = 1 HC = 2
SN 11
SN 10 A B C
HC = 4
HC = 1
D E F
HC = 2 HC = 3
Figure 29: Counting Hops
Router A Router B Router D

Destination Next Hop Metric Destination Next Hop Metric Destination Next Hop Metric
SN 10 lokal 0 SN 10 Router A 1 SN 10 Router A 1
SN 11 Router B 2 SN 11 Router C 1 SN 11 Router E 3
Table 9: Routing table to the figure above
In contrast to OSPF, a RIP router regularly exchanges the content of its entire routing table with its direct neighbor.
Every router knows only its own routes and the routes of its direct neighbor. Thus it only has a local perspective.
When changes are made in the network, it takes a while until all the routers have the same uniform view of the
network. The process of achieving this condition is known as convergence.

RIP
5
Convergence
5.1 Convergence
How does RIP react to changes in the topography?

In the following example of a line interruption between router B and router C, you can see the resulting changes
in the address table:
Assumptions:
 The interruption occurs 5 seconds after B sent its routing table.
 The routers send their routing table every 30 seconds (= factory setting).
 There is an interval of 15 seconds between when router A sends its routing table and when router B sends its
routing table.
HC = 1 HC = 2
SN 11
SN 10 A B C
HC = 4
HC = 1
D E F
HC = 2 HC = 3
Figure 30: Hop Count
Time elapsing before convergence:
0 seconds:
Interruption
10 seconds
Router A sends its routing table:
Router A
Destination Next hop Metric
SN 10 local 0
SN 11 Router B 2

Using the routing table from router A, router B sees that router A knows a connection to destination SN 11 with a
metric of 2. Because it does not have its own connection to router C as the next hop to SN 11, router B changes
its entry to destination SN 11. It enters router A as the next hop and increases the metric from router A by 1 to 3
(distance = learned distance + 1).
25 secondsRouter B sends its routing table:

Router B
Destination Nex- Hop Metric
SN 10 Router A 1
SN 11 Router A 3

Using the routing table from router B, router A sees that router B knows a connection to SN 11 with a metric of 3.
So router A increases its metric for SN 11 by 1 to 4.
40 secondsRouter A sends its routing table:

RIP
Convergence
Router A
SN 10 local 1
SN 11 Router B 4

Using the routing table from router A, router B sees that router A knows a connection to destination SN 11 with a
metric of 4. So router B increases its metric for SN 11 by 1 to 5.
55 secondsRouter B sends its routing table

Router B
SN 10 Router A 1
SN 11 Router A 5

Using the routing table from router B, router A sees that router B knows a connection to SN 11 with a metric of 5.
So router A increases its metric for SN 11 by 1 to 6. Because router A can see in the routing table from router D
that router D has a connection to SN 11 with the smaller metric of 3, router A changes its entry for SN 11.
70 secondsRouter A sends its routing table:

Router A
SN 10 Router A 1
SN 11 Router D 4

After 70 seconds, convergence has been achieved again.

RIP
5
Maximum Network Size
5.2 Maximum Network Size
The biggest problem with RIP is that routers only know their neighbors directly. This results in long convergence
times and the count-to-infinity problem. Infinity refers to the inaccessibility of a destination, and it is designated by
hop count 16 in RIP. If the above example did not contain the parallel path via routers D, E and F, then routers A
and B would keep sending their routing tables until the metric reached a value of 16. Then the routers recognize
that the destination is inaccessible. 
Using the “split horizon” approach eliminates this looping problem between two neighboring routers. Split horizon
has two operating modes.
Simple split horizon Omits the entries known by a neighbor when sending the routing table to this neighbor.
Simple split horizon with poison reverse Sends the routing table to a neighbor with the entries known by this neighbor, but denotes these
entries with the infinity metric (=16).
Thus the hop count 16 specifies the maximum size of a network with RIP as the routing procedure. The longest
paths may use up to 15 routers.

RIP
General Properties of RIP
5.3 General Properties of RIP
The RFC 1058 from June 1988 specifies RIP version 1. Version 1 has the following restrictions:
 Use of broadcasts for protocol messages.
 Does not support subnetworks/CIDR.
 No authentification.
The standardization of RIP version 2 in the RFC 2453 in 1998 eliminates the above restrictions. 
RIP V2 sends its protocol messages as a multicast with the destination address 224.0.0.9, and supports
subnetwork masks and authentication. 
However, the restrictions relating to the size of the network remain.
Advantages Disadvantages
Easy to implement Routing tables in large networks very comprehensive
Easy to administrate Routing information is distributed slowly, because there are fixed sending intervals. This applies in
particular to connections that have elapsed, since the routing table only contains existing paths.
Count-to-infinity
Table 10: Advantages and disadvantages of Vector Distance Routing

RIP
5
Configuring the RIP
5.4 Configuring the RIP
The advantage of RIP is the simple configuration. After the router interface is defined and the RIP is switched on,
RIP automatically enters the required routes in the routing table.
Subnet 10.0.1.0/24 Subnet 10.0.3.0/24
IP = 10.0.1.5/24 Interface 2.1

GW =10.0.1.1 IP = 10.0.3.5/24
IP=10.0.2.2
GW = 10.0.3.1
A B Interface 2.2
Interface 2.1
IP=10.0.1.1 Interface 2.2 IP=10.0.3.1
IP=10.0.2.1
Figure 31: Example of the configuration of RIP
The configuration of RIP requires the following steps:

 Configure router interfaces - assign IP address and network mask.
 Switch on RIP on port.
 Switch on RIP globally.
 Configuration for Router B


ip address 10.0.3.1 255.255.255.0 Assign the IP parameters to the port.

ip rip Switch on RIP on this port.
show ip rip interface brief Verify the settings for the RIP configuration.
Send Receive RIP Link

Interface IP Address Version Version Mode State
--------- ------------- ----------- --------- --------- -----
2/1 0.0.0.0 RIP-2 Both Enable Down
The IP address entries remain at 0.0.0.0 as long as the routing function is switched off globally.
router rip Switch to the Router Configuration mode.

redistribute connected Instruct RIP to send the routes of the locally connected interfaces along with the
learned routes in the RIP information.
enable Switch on RIP globally.

RIP
Configuring the RIP

show ip rip interface brief Verify the settings for the RIP configuration.
Send Receive RIP Link

Interface IP Address Version Version Mode State
--------- ------------- ----------- --------- --------- -----
2/1 10.0.2.2 RIP-2 Both Enable Up

--------------- --------------- ------------ ------ ------------
10.0.1.0 255.255.255.0 RIP 2/1 10.0.2.1
10.0.2.0 255.255.255.0 Local 2/1 10.0.2.2
10.0.3.0 255.255.255.0 Local 2/2 10.0.3.1
 Perform the corresponding configuration on the other RIP routers also.

RIP
5
Configuring the RIP

OSPF
6 OSPF
Open Shortest Path First (OSPF) is a dynamic routing protocol based on the Link State Algorithm. This algorithm
is based on the link states between the routers involved.
The significant metric in OSPF is the “OSPF costs”, which is calculated from the available bit rate of a link.
OSPF was developed by IETF. OSPF is currently specified as OSPFv2 in RFC 2328. Along with many other
advantages of OSPF, the fact that it is an open standard has contributed to the wide usage of this protocol. OSPF
has replaced the Routing Information Protocol (RIP) as the standard Interior Gateway Protocol (IGP) in large
networks.
OSPF has a number of significant advantages to offer:

 Cost-based routing metrics: In contrast to RIP, OSPF provides clear metrics based on the bandwidth of each
individual network connection. OSPF provides major flexibility in designing a network, because the user can
simply change these costs.
 Routing via multiple paths (equal cost multiple path/ECMP): OSPF is able to support a number of equal paths
to a given destination. OSPF thus provides efficient utilization of the network resources (load distribution) and
improves the availability (redundancy).
 Hierarchical routing: By logically dividing the network into areas, OSPF shortens the time required to distribute
routing information. The messages about changes in a subnetwork remain within the subnetwork, without
putting any load on the rest of the network.
 Support of Classless Inter-Domain Routing (CIDR) and Variable Length Subnet Mask (VLSM): This allows the
network administrator to assign the IP address resources efficiently.
 Fast tuning time: OSPF supports the fast distribution of messages about route changes. This speeds up the
tuning time for updating the network topology.
 Saving network resources / bandwidth optimization: Because OSPF, in contrast to RIP, does not exchange the
routing tables at regular, short intervals, no bandwidth is unnecessarily “wasted” between the routers.
 Support of authentication: OSPF supports the authentication of all nodes that send routing information.
Advantages Disadvantages
Every router calculates its routes independently of the other routers. Complicated to implement
All the routers have the same basic information. Complex administration due to the large number of options.
Rapid detection of link interruptions and rapid calculation of alternative routes.
The data volume for router information is relatively small, because information is
only sent when it is required, and only the information that applies to the
immediate neighbors.
Optimal path selection through evaluation of the link quality.
Table 11: Advantages and disadvantages of Link State Routing
OSPF is a routing protocol based on the states of the links between the routers. 
Using the link states collected from all the routers and the Shortest Path First algorithm, an OSPF router
dynamically creates its routing table.

OSPF
6
OSPF-Topology
6.1 OSPF-Topology
OSPF is hierarchically structured in order to limit the scope of the OSPF information to be exchanged in large
networks. You divide up your network using what are known as areas.
6.1.1 Autonomous System

An Autonomous System (AS) is a number of routers that are managed by a single administration and use the same
Interior Gateway Protocol (IGP). Exterior Gateway Protocols (EGP), on the other hand, are used to connect a
number of autonomous systems. OSPF is an Interior Gateway Protocol.
Autonomous System
Area 2
Area 1
ABR ASBR
ABR
Backbone Area 0
RIP
Figure 32: Autonomous System
An AS uses an “Autonomous System Boundary Router” (ASBR) to connect with the outside world. An ASBR
understands multiple protocols and serves as a gateway to routers outside the areas. An ASBR is able to transfer
routes from different protocols into the OSPF. This process is known as redistribution.

OSPF
OSPF-Topology
6.1.2 Router ID
The router ID in the form of an IP address is used to uniquely identify every router within an autonomous system.
To improve the transparency, it is necessary to manually configure the router ID of every OSPF router. Thus there
is no automatic function that selects the router ID from the IP interfaces of the router.

router ospf Switch to the Router Configuration mode.
router-id 192.168.1.0 Assign Router-ID (e.g. 192.168.1.0).
enable Switch on OSPF globally.
6.1.3 Areas
Each area first forms its own database using the link states within the area. The data exchange required for this
remains within the area. Each area uses an Area Border Router (ABR) to link to other areas. The routing
information is summarized as much as possible between the areas (route summarization).
Every OSPF router must be a member of at least one area. 

An individual router interface can only be assigned to one area. In the state on delivery, every router interface is
assigned to the backbone area.
OSPF distinguishes between the following particular area types:

 Backbone-Area:
This is by definition the area 0 or 0.0.0.0. An OSPF network consists of at least the backbone area. It is the
central area, which is linked to all the other areas directly. The backbone area receives all the routing
information and is responsible for forwarding this information.
 Stub Area:
You define an area as a stub area if external LSAs are not to be flooded into the area. External means outside
the autonomous system. These external LSAs are the yellow and orange links in the illustration (see fig. 33).
Thus the routers within a stub area only learn internal routes (blue links – e.g. no routes that are exported into
OSPF from another log / redistributing). All the destinations outside the autonomous system are assigned to a
default route. Stub areas are thus generally used if only one route in the area has a link to outside the area.
The use of stub areas keeps the routing table small within the stub area.
Totally Stubby Area:
You define a totally stubby area if, along with the external (orange and yellow) LSAs, the LSAs of the internal
(blue) routes are also not to be sent into the area. Internal means between the areas of the autonomous
system. A router within a totally stubby area thus only knows the routes within its own area and the default route
out of the area.
Configuration notes:
 For a stub area, all the routers within the stub area must be defined as stub routers.
 A stub area does not allow passage for a virtual link.
 The backbone area cannot be defined as a stub area.
 Not So Stubby Area (NSSA): 
You define an area as NSSA if the external (yellow) routes of a system directly connected to the NSSA that is
outside your own autonomous system are to be led into the area (redistributed). These external (yellow) LSAs
then also lead from the NSSA to other areas in your own autonomous system. External (orange) LSAs within
your own autonomous system do not, on the other hand, lead into an NSSA.

OSPF
6
OSPF-Topology
By using NSSAs, you can integrate ASBRs into the area without foregoing the advantage of stub areas, namely
that external routes from the backbone are not flooded into the corresponding area.
Thus NSSAs have the advantage that external routes coming from the backbone are not all entered in the
routing tables of the internal routers. At the same time, however, a limited number of external networks (which
can be reached across the boundaries of the NSSA) can be propagated into the backbone area.
Area 1 Autonomous System
NSSA
ASBR
BGP
Area 0
BGP = Border
Gateway Protocol RIP
Totally Stubby
Stub
Figure 33: LSA distribution into the area types

area [area-id] Assign the area ID to the area.

area 2 nssa Defines area 2 as the NSSA.
area 3 stub Defines area 3 as the stub area.
area 3 default-cost 10 Instructs the ABR to inject the default route with the metric 10 into the stub area.
no area 3 stub summerylsa Makes stub area 3 the totally stubby area.
6.1.4 Virtual Link

OSPF requires that the backbone area can be passed through. However, if this is not actually possible, then OSPF
provides a virtual link (VL) to connect parts of the backbone area with each other (see fig. 35). A VL even allows
you to connect an area that is connected with the backbone area via another area.

OSPF
OSPF-Topology
Area 1 Area 2
Backbone Area 0 VL
ABR ABR
Figure 34: Linking a remote area to the backbone area with a virtual link (VL)
Router 2 Router 1
Router-ID: Router-ID:
2.2.2.2 1.1.1.1
Area 1
Backbone Area 0 VL Backbone Area 0
ABR ABR
Figure 35: Expanding the backbone area with a virtual link (VL)
Configuration for the expansion of the Backbone area (see fig. 35):
Router 1:
area 1 virtual-link 2.2.2.2 Enter the neighboring router ID for a virtual link to area 1.
Router 2:
area 1 virtual-link 1.1.1.1 Enter the neighboring router ID for a virtual link to area 1.

OSPF
6
OSPF-Topology
6.1.5 OSPF Router

OSPF distinguishes between the following router types:
 Internal Router:
All OSPF interfaces of an internal router are within the same area.
 Area Border Router (ABR):
ABRs have OSPF interfaces in a number of areas, including the backbone area. ABRs thus participate in
multiple areas. Where possible, you summarize a number of routes and send “Summary LSAs” to the
backbone area.
 Autonomous System Area Border Router (ASBR):
An ASBR is located on the boundary of an autonomous system and links OSPF to other autonomous systems
/ routing protocols. These external routes are transferred into OSPF using what is known as redistributing and
are then summarized as “AS-external LSAs” and flooded into the area.
Switch on the redistributing explicitly.
If you want to use subnetting, then you enter this explicitly. In OSPF, the following “routing protocols” can be
exported:
 connected (local subnetworks on which OSPF is not switched on),
 static (static routes),
 RIP.
6.1.6 Link State Advertisement

As a basis for building up a database via the link states, OSPF uses Link State Advertisements (LSA).
An LSA contains information about

 the router,
 the connected subnets,
 the routes that can be reached,
 the network masks and
 the metrics.
OSPF unterscheidet folgende LSA-Typen:

 Router LSAs (type 1 LSAs):
Every router sends a router LSA to all its connected areas. They describe the state and the costs of the router
links (router interfaces) that the router has in the corresponding area. Router LSAs are only flooded within the
area.
 Network LSAs (Type 2 LSAs):
These LSAs are generated by the designated router, DR (see on page 75 „Setting up the Neighbor
Relationship“) and are sent for every connected network/subnet within an area.
 Summary LSAs (type 3 /type 4 LSAs):
Summary LSAs are generated by ABRs and describe inter-area destinations, meaning destinations in different
areas of the same autonomous system.
Type 3 LSAs describe targets for IP networks (individual routes or summarized routes).
Type 4 LSAs describe routes to ASBRs.
 AS-external LSAs (type 5 LSAs):
These LSAs are generated by ASBRs and describe routes outside the autonomous system. These LSAs are
flooded everywhere apart from to stub areas and NSSAs.

OSPF
OSPF-Topology
 NSSA external LSAs (type 7 LSAs):

A stub area does not flood any external routes (represented by type 5 LSAs) and therefore does not support
any Autonomous System Border Routers (ASBRs) at its boundaries. Thus an ASBR cannot carry any routes
from other protocols into a stub area. 
RFC 1587 specifies the functioning of NSSAs. According to RFC 1587, ASBRs send type 7 LSAs instead of
type 5 LSAs for the external routes within an NSSA. These type 7 LSAs are then converted into type 5 LSAs
by an ABR and flooded into the backbone area. This “translator role” is negotiated among the ABRs in an NSSA
(the router with the highest router ID), but it can also be configured manually.

OSPF
6
General Operation of OSPF
6.2 General Operation of OSPF
OSPF was specially tailored to the needs of larger networks and provides a fast convergence and minimum usage
of protocol messages.
The concept of OSPF is based on the creation, maintenance and distribution of what is called the link state
database. This data basis describes
 all the routers within a routing domain (area) and
 their active interfaces and routes,
 how they are linked to each other and
 the costs of these links.
All the routers within an area have an identical data basis, which means that they all know the exact topology within
this area.
Every router plays its part in setting up the respective data basis by propagating its local viewpoint as Link State
Advertisements (LSAs). These LSAs are then flooded to all the other routers within an area.
OSPF supports a range of different network types such as point-to-point networks (for example, packet over
SONET/SDH), broadcast networks (Ethernet) or non-broadcast networks.
Broadcast networks are distinguished by the fact that a number of systems (terminal devices, switches, routers)
are connected to the same segment and thus can all be addressed simultaneously via broadcasts/multicasts.
OSPF generally performs the following three steps in carrying out its tasks in the network:
 Setting up the neighbor relationships (hello protocol)
 Synchronizing the link state database
 Route calculation

OSPF
Setting up the Neighbor Relationship
6.3 Setting up the Neighbor Relationship
When a router is started, it uses what are called hello packets to contact its neighboring routers. With these hello
packets, an OSPF router finds out which OSPF routers are near it and whether they are suitable for setting up a
neighbor relationship (adjacency).
In broadcast networks such as Ethernet, the number of neighbors increases with the number of routers connected,
as does the information exchange for clarifying and maintaining the neighbor relationships. To reduce these
volumes within an area, OSPF uses the hello protocol to determine a Designated Router (DR) within the
corresponding segment. Thus every router in an area only sets up the neighbor relationship with its designated
router, instead of with every neighbor. The designated router is responsible for the distribution of all the link state
information to its neighbor routers. 
For security reasons, OSPF provides for the selection of a Backup Designated Router (BDR), which takes over
the tasks of the DR if the DR fails. The OSPF router with the highest router priority is the DR. The router priority is
specified by the administrator. If two routers have the same priority, the router with the higher router ID is selected.
The router ID is the smallest IP address of a router interface. You configure this router ID manually when starting
up the OSPF router (see on page 69 „Router ID“).
DR BDR
Figure 36: LSA distribution with designated router and

backup designated router
To exchange information, OSPF uses reserved multicast addresses.
Destination Multicast IP address Mapped multicast MAC address

All OSPF routers 224.0.0.5 01:00:5E:00:00:05
Designated routers 224.0.0.6: OSPF 01:00:5E:00:00:06
Table 12: OSPF - multicast addresses
Hello packets are also used to check the configuration within an area (area ID, timer values, priorities) and to
monitor the neighbor relationships. Hello packets are sent cyclically (hello interval). If hello packets are not
received for a specific period (dead interval), the neighbor relationship is terminated and all the corresponding
routes are deleted.
The hello interval (default: 10 seconds) and the dead interval (default: 30 seconds) can be configured for each
router interface, but they must be uniform within an area.

OSPF
6
Setting up the Neighbor Relationship

interface 1/1 Switch to the Interface Configuration mode of interface 1/1.
ip ospf hello-intervall 20 Setzt Hello-Intervall auf 20 Sekunden.

ip ospf dead-intervall 60 Setzt Dead-Intervall auf 60 Sekunden.
show ip ospf neighbor brief all Displays the neighbor relationships of the router.
Router ID IP Address Neighbor Interface State

------------ ----------- ------------------- --------
192.168.1.1 10.0.1.1 1/1 Full
192.168.1.2 11.0.1.1 1/2 Full
192.168.1.3 12.0.1.1 1/3 Full
192.168.1.4 13.0.1.1 1/4 Full
The neighbor relationships can have the following states:
Down No hello packets received yet

Init Receiving hello packets
2-way Bidirectional communication, determination of the DR and the BDR
Exstart Determination of master/slave for LSA exchange
Exchange LSAs are exchanged or flooded
Loading Completion of the LSA exchange
Full Data basis completely uniform in the area. Routes can now be calculated.

OSPF
Synchronization of the LSD
6.4 Synchronization of the LSD
The central part of the OSPF is the Link State Database (LSD). This database contains a description of the
network and the states of all the routers. It is the source for calculating the routing table. It reflects the topology of
the network. It is set up after the designated router and backup designated router have been determined within an
area (broadcast networks).
To set up the LSD and update any topology changes, the OSPF router sends link status advertisements (LSA) to
all the directly accessible OSPF routers.
These link status advertisements consist of the interfaces and the neighbors of the sending OSPF router that can
be reached via these interfaces. OSPF routers put this information into their databases and flood the information
to all the ports.
If no topology changes occur, every router repeats its own LSAs every 30 minutes.
You can view the content of the Link State Database with the CLI command “show ip ospf database”, whereby the
entries are output in accordance with the areas.
show ip ospf database Displays the neighbor relationships of the router.
Router Link States (Area 0.0.0.0)
Link Id Adv Router Age Sequence Chksm Options Rtr Opt

--------------- --------------- ----- -------- ------ ------- -----
192.168.1.1 192.168.1.1 122 80000007 0x5380 -E---- ---E-
192.169.1.1 192.169.1.1 120 80000007 0xbf0e -E---- ---E-
Network Link States (Area 0.0.0.0)

--------------- --------------- ----- -------- ------ ------- -----
10.0.1.2 192.169.1.1 129 80000002 0xad5a -E----
11.0.1.2 192.169.1.1 135 80000002 0xa066 -E----
12.0.1.2 192.169.1.1 137 80000002 0x9372 -E----
13.0.1.2 192.169.1.1 132 80000002 0x867e -E----
AS External States

--------------- --------------- ----- -------- ------ ------- -----
192.169.0.0 192.169.1.1 178 80000002 0xca1c
The interpretation of the link ID presented depends on the corresponding LSA type:
Router Link States Link ID corresponds to router ID of source

Network Link States Link ID corresponds to interface IP address of the designated router
Network Summary States Link ID corresponds to the corresponding network
Summary ASBR States Link ID corresponds to router ID of described ASBR
AS External States Link ID corresponds to the external network

OSPF
6
Route Determination
6.5 Route Determination
After the LSDs are learned and the neighbor relationships go to the full state, every router calculates a path to
every destination using the Shortest Path First (SPF) algorithm. After the optimal path to every destination has
been determined, these routes are entered in the routing table. The route calculation is generally based on the
accessibility of a hop and the metric (costs). The costs are added up over all the hops to the destination.
The costs of an individual router interface are based on the available bandwidth of this link. The calculation for the
standard setting is based on the following formula:
Metric = 10 000 000 / bandwidth (bits/sec) .
For Ethernet, this leads to the following costs:

10 Mbit 10
100 Mbit 1
1000 Mbit 1 (0.1 rounded up to 1)
The table shows that this form of calculation in the standard configuration does not permit any distinction between
fast Ethernet and gigabit Ethernet.
You can change the standard configuration by assigning a different value for the costs to each OSPF interface.
This enables you to differentiate between fast Ethernet and gigabit Ethernet.

interface 1/1 Switch to the Interface Configuration mode of interface 1/1.
ip ospf cost 2 Assigns to port 1.1 the value 2 for the OSPF costs.

OSPF
Configuring OSPF
6.6 Configuring OSPF
In the state on delivery, the default values are selected so that you can configure simple OSPF functions in just a
few steps. 
After the router interface is defined and OSPF is switched on, OSPF automatically enters the required routes in
the routing table.
The example (see fig. 37) shows a simple OSPF configuration. Area 0 is already defined in the state on delivery.
The terminal devices do not have an OSPF function, so you do not have to activate OSPF on the corresponding
router interface. By activating the redistribute function, you can inject the routes to the terminal devices into the
OSPF.
Subnet 10.0.1.0/24 Subnet 10.0.3.0/24

IP=10.0.1.5/24 Interface 2.1
IP=10.0.3.5/24
GW=10.0.1.1 IP=10.0.2.2
GW=10.0.3.1
A B Interface 2.2
Interface 2.1
IP=10.0.1.1 Interface 2.2 IP=10.0.3.1
IP=10.0.2.1
Figure 37: Example of the configuration of OSPF
The configuration of OSPF requires the following steps:

 Configure router interfaces – assign IP address and network mask.
 Switch on OSPF at port.
 Switch on OSPF globally.

OSPF
6
Configuring OSPF
 Configuration for Router B

interface 2/1 Switch to the Interface Konfiguration mode of interface 2.1 to setup OSPF.
ip ospf Switch on OSPFat this port .

enable Switch on OSPF globally.
router-id 10.0.2.2 Assign to router B the router ID 10.0.2.2.
redistribute connected subnets Instruct OSPF to, 
- send the routes of the locally connected interfaces along with the learned
routes in the RIP information and 
- include subnets without OSPF in OSPF (CIDR).
show ip ospf Verify the settings for the global OSPF configuration.
Router ID...................................... 10.0.2.2

OSPF Admin Mode................................ Enable
ASBR Mode...................................... Enable
RFC 1583 Compatibility......................... Enable
ABR Status..................................... Disable
Exit Overflow Interval......................... 0
External LSA Count............................. 0
External LSA Checksum.......................... 0
New LSAs Originated............................ 0
LSAs Received.................................. 0
External LSDB Limit............................ No Limit
Default Metric................................. Not configured
Default Route Advertise........................ Disabled

Always......................................... FALSE
Metric.........................................
Metric Type.................................... External Type 2
Maximum Paths.................................. 4
Redistributing.................................
Source......................................... Connected
Metric......................................... Not Configured
--More-- or (q)uit
Metric Type.................................... 2
Tag............................................ 0
Subnets........................................ Yes
Distribute List................................ Not configured
show ip ospf interface brief Verify the settings for the OSPF interface configuration.
Router Hello Dead Retrax Retrax LSAAck

Interface AdminMode Area ID Priority Intval Intval Intval Delay
Intval
--------- --------- ----------- -------- ------ ------ ------ -----
2/1 Enable 0.0.0.0 1 10 40 5 1 1
2/2 Disable 0.0.0.0 1 10 40 5 1 1


OSPF
Configuring OSPF
 Perform the corresponding configuration on the other OSPF routers also.

show ip ospf neighbor brief Verify the OSPF neighbor relationships (e.g. for router B).
Router ID IP Address Neighbor Interface State

---------------- ----------- ------------------- ---------
10.0.2.1 10.0.2.1 2/1 Full

--------------- --------------- ------------ ------ -------------
10.0.1.0 255.255.255.0 OSPF Ext T2 2/1 10.0.2.1
10.0.2.0 255.255.255.0 Local 2/1 10.0.2.2
10.0.3.0 255.255.255.0 Local 2/2 10.0.3.1

OSPF
6
Configuring OSPF

PROTOCOL-BASED VLANS
7 Protocol-based VLANs
Along with port-based VLANs based on IEEE 802.1Q, the Switch also supports protocol-based VLANs based on
IEEE 802.1v.
With port-based VLANs, the Switch uses the port VLAN ID of the receiving port to determine which VLAN a data
packet belongs to if it is received without a VLAN tag.
With protocol-based VLANs, the Switch uses the protocol of the received data packet to determine which VLAN a
data packet belongs to if it is received without a VLAN tag. The Switch supports the protocols
 IP,
 ARP,
 IPX.
Data packets from other protocols received without a VLAN tag are assigned to a VLAN by the Switch in
accordance with the port VLAN ID.
For the VLAN assignment, the Switch takes into account

 firstly, the VLAN tag,
 then the protocol the data packet belongs to,
 and finally, the port VLAN ID.
Protocol-based VLANs enable you to transfer data packets not relevant to routing across IP subnetwork
boundaries. Data packets relevant to routing are IP and ARP data packets.
Ro2
VLAN 2
Ro1
PC1
VLAN 2
Port VLAN 2
2.3
VLAN 3
2.1 2.2 Se1
PC2 VLAN 4
SN "alpha" SN "beta"
IP: 10.0.1.0/24 IP: 10.0.2.0/24
Figure 38: Example of a protocol-based VLAN
In the example (see fig. 38), PC2 and Se1 communicate via IP. These data packets are routed.
The devices Ro1, Ro2 and PC1 communicate via other Ethernet-based protocols. These data packets are
switched in VLAN 2.
Thus all IP data packets remain in their subnetworks, apart from the IP data packets that are meant for a different
subnetwork.

7
General Configuration
7.1 General Configuration
 Create a VLAN protocol group for each subnetwork.

 Assign the protocols to the VLAN protocol group for each subnetwork.
 Create the VLANs.
 Switch on the VLAN routing in the VLANs affected and thus create the virtual router interfaces.
 Assign the VLAN protocol groups to the VLANs.
 Configure the port interfaces:
 VLAN membership
 Port VLAN ID for non-ARP/IP data packets
 Port of a VLAN protocol group and thus assign to a VLAN
 Configure virtual router interfaces:
 Assign IP address
 Switch on routing
 Switch on routing globally.

Configuration of the Example
7.2 Configuration of the Example

vlan protocol group alpha Create VLAN protocol group 1 for alpha subnetwork.
vlan protocol group beta Create VLAN protocol group 2 for beta subnetwork.
show protocol all Display the VLAN protocol groups created.
Group
Group Name ID Protocol(s) VLAN Interface(s)
---------------- ------ ----------- ---- ---------------------
alpha 1 0
beta 2 0

vlan protocol group add protocol 1 ip Add IP of VLAN protocol group 1.
vlan protocol group add protocol 1 arp Add ARP of VLAN protocol group 1.
vlan protocol group add protocol 2 ip Add IP of VLAN protocol group 2.
vlan protocol group add protocol 2 arp Add ARP of VLAN protocol group 2.
show protocol all Display the protocols assigned to the protocol groups.
Group
---------------- ------ ----------- ---- ------------------
alpha 1 IP,ARP 0
beta 2 IP,ARP 0

vlan 2 Create VLAN 2.
vlan routing 3 Create a virtual router interface and activate the routing function for this
interface.
vlan routing 4 Create a virtual router interface and activate the routing function for this
interface.
protocol group 1 3 Assign VLAN protocol group 1 to VLAN 3.
protocol group 2 4 Assign VLAN protocol group 2 to VLAN 4.
show protocol all Display the protocols and VLANs assigned to the VLAN protocol groups.
Group
---------------- ------ ----------- ---- ----------------------
alpha 1 IP,ARP 3
beta 2 IP,ARP 4
show ip vlan Display the assignment of the virtual router

interfaces to the VLANs.
Logical
VLAN ID Interface IP Address Subnet Mask MAC Address
------- ----------- --------------- --------------- -----------
3 9/1 0.0.0.0 0.0.0.0 00:80:63:51:74:2C
4 9/2 0.0.0.0 0.0.0.0 00:80:63:51:74:2D

vlan participation exclude 1 Remove port 2.1 from VLAN 1.

7
Configuration of the Example
vlan participation include 2 Declare port 2.1 a member of VLAN 2.

vlan pvid 2 Set the port VLAN ID to 2, which means that the Switch assigns non-IP/ARP data
packets to VLAN 2.
protocol vlan group 1 Assign VLAN protocol group 1 to interface 2.1, which means that the Switch
assigns IP/ARP data packets to VLAN 3.

vlan pvid 2 Set the port VLAN ID to 2, which means that the Switch assigns non-IP/ARP data
packets to VLAN 2.
protocol vlan group 2 Assign VLAN protocol group 2 to interface 2.2, which means that the Switch
assigns IP/ARP data packets to VLAN 4.

vlan pvid 2 Set the port VLAN-ID to 2, which means that data packets that are received
without a tag at that port are assigned to VLAN 2 by the Switch.

ip address 10.0.1.1 255.255.255.0 Assign the IP parameters to the router interface.

ip address 10.0.2.1 255.255.255.0 Assign the IP parameters to the router interface.
show ip interface brief Display the entries of the virtual router interface.
Netdir Multi
--------- --------------- --------------- -------- --------
9/1 10.0.1.1 255.255.255.0 Disable Disable
9/2 10.0.2.1 255.255.255.0 Disable Disable


MULTICAST ROUTING
8 Multicast Routing
Multicast data streams are data packets that a sender sends to multiple recipients. To reduce the network load,
the sender uses a Multicast address. He thus sends each packet only once to the Multicast address instead
of sending it to each recipient individually. The recipients recognise a Multicast data stream intended for them by
the Multicast address.
A common reason for introducing subnetworks is the restriction of broadcast data streams. Switches send
broadcast/Multicast data streams to all ports, while routers block broadcast/Multicast data streams. Multicast
routing enables you to accurately transmit Multicast data streams beyond the boundaries of subnetworks.
Accurate transmission means sending data streams with defined Multicast addresses exclusively to those devices
which want to receive the Multicast data stream.
IP: 10.0.3.0/24 IP: 10.0.4.0/24
Multicast
IP: 10.0.1.0/24 IP: 10.0.2.0/24

Figure 39: Multicast routing requires:
To the use of Multicast routing pertains:

 Defined Multicast addresses
 A protocol for Multicast group registration that organizes the exchange of information by means of Multicast
data streams (e.g. IGMP). This information relates to the reporting that network participants wish to receive
Multicast data streams and querying this wish by means of intermediate devices.
 A protocol that guides the Multicast data streams in accordance with the information on Multicast data streams
(e.g. PIM-DM, DVMRP).

MULTICAST ROUTING
8
Multicast Addresses
8.1 Multicast Addresses
8.1.1 IP Multicast Addresses

The IANA (Internet Assigned Numbers Authority) defines the IP addresses of the class D IP address space as
Multicast addresses. IP Multicast addresses are in the range from 224.0.0.0 to 239.255.255.255.
IP address range Assignment

224.0.0.0 Base address, reserved
224.0.0.1 - 224.0.0.255 Local Network Control Block, reserved for routing protocols, IGMP, etc. For example:
224.0.0.1 - all hosts of a subnetwork
224.0.0.2 - all routers of a subnetwork
224.0.0.4 - all DVMRP routers
224.0.0.5 - all OSPF routers
224.0.0.6 - all OSPF DR routers
224.0.0.9 - all RIP v2 routers
224.0.0.13 - all PIM routers
224.0.0.18 - all VRRP routers
224.0.0.22 - all IGMP v3 reports
224.0.1.0 - 224.0.1.255 Internetwork Control Block
224.0.2.0 - 224.0.255.255 AD HOC Block
224.1.0.0 - 238.255.255.255 Various organizations, protocols, applications, reservations. For example:
232.0.0.0-232.255.255.255 - Source-specific Multicasts
239.0.0.0 - 239.255.255.255 Administratively scoped IP v4 Multicast space 
These Multicast addresses are not transferred by any router beyond the local boundaries and into the
Internet. Therefore the administrator can assign these addresses any way he wants within these local
boundaries.
Table 13: Assignment of the IP Multicast address range
The administratively scoped IP v4 Multicast area is subdivided further by the IANA:
IP address range Assignment

239.000.000.000 - 239.191.255.255 Reserved [IANA]
239.192.000.000 - 239.251.255.255 Organization-local scope [Meyer, RFC2365]
239.252.000.000 - 239.254.255.255 Site-local scope (reserved) [Meyer, RFC2365]
239.255.000.000 - 239.255.255.255 Site-local scope [Meyer, RFC2365]
Table 14: Assignment of the administratively scoped IP v4 Multicast area
In the end, the following multicast IP adress ranges are left over for disposal by an organisation's administrator:
 239.192.000.000 - 239.251.255.255 
for an organisation's local areas.
 239.255.000.000 - 239.255.255.255 
for an organisation's entire area.

MULTICAST ROUTING
Multicast Addresses
Note: When selecting the Multicast IP addresses, ensure that they can be uniquely mapped onto MAC Multicast
addresses (see on page 91 „Mapping IP MAC Multicast Addresses“).

MULTICAST ROUTING
8
Multicast Addresses
8.1.2 MAC Multicast Addresses

The IEEE calls the 48-bit MAC address an “Extended Unique Identifier”. It is the unique identifier of a device. The
first 24 bits of the MAC address (Organizationally Unique Identifier, OUI) is assigned by the IEEE to the
manufacturer. The manufacturer uses the last 24 bits to uniquely identify their device interfaces.
A number of MAC addresses are reserved for specific applications:
MAC-Address Type Use

01-00-5E-00-00-00 0800 Internet Multicast [RFC1112]
01-80-C2-00-00-00 -802- Spanning tree (for bridges)
FF-FF-FF-FF-FF-FF 0806 ARP (for IP and CHAOS) as needed
FF-FF-FF-FF-FF-FF 8035 Reverse ARP
Table 15: Examples of reserved MAC addresses

MULTICAST ROUTING
Multicast Addresses
8.1.3 Mapping IP MAC Multicast Addresses

When IP data packets are sent via Ethernet, the IP address is assigned to a MAC address, and therefore IP
Multicast addresses are also mapped onto MAC Multicast addresses.
The 23 lower-value bits of the 32-bit IP Multicast address make up the 23 lower-value bits of the 48-bit MAC
Multicast address. 
Of the remaining 9 bits of the IP Multicast address, 4 bits are used as the class D identification for the Multicast
address.
The remaining 5 bits ensure that 32 IP Multicast addresses can be mapped onto one and the same MAC Multicast
address.
32-bit Multicast IP Address

239.192.112.159
239 192 112 159
1110 1111 1100 0000 0111 0000 1001 1111
Class D ignored
0 = Internet Multicast
1= reserviert
IEEE 802.3 Multicast-MAC-Address

0000 0001 0000 0000 0101 1110 0100 0000 0111 0000 1001 1111
0 1 0 0 5 E 4 0 7 0 9 F
48-bit Multicast MAC Address 01:00:5E:40:70:9F
Figure 40: Conversion of the IP address to the MAC address

MULTICAST ROUTING
8
Multicast Group Registration
8.2 Multicast Group Registration
The Internet Group Management Protocol (IGMP) describes the distribution of Multicast information between
routers and terminal devices on Layer 3.
Routers with an active IGMP function periodically send queries to find out which IP Multicast group members are
connected to the LAN, or to find out who is interested in becoming a group member.
Multicast group members reply with a Report message. This Report message contains all the parameters required
by the IGMP. The router records the IP Multicast group address from the Report message in its routing table.
The result of this is that it transfers frames with this IP Multicast group address in the target address field only in
accordance with the routing table.
Devices which no longer want to be members of a Multicast group can cancel their membership by means of a
Leave message (from IGMP version 2), and they do not transmit any more Report messages. The router removes
the routing table entry if it does not receive any Report messages within a specified period of time (aging time).
If there are multiple routers with an active IGMP function in the subnetwork, then
 for IGMP version 1, all routers in this subnetwork periodically send queries
 for IGMP versions 2 and 3, the routers decide which router takes over the query function (Querier Election).
Protocol Standard
IGMP v1 RFC 1112
IGMP v2 RFC 2236
IGMP v3 RFC 3376
Table 16: Standards which describe the Multicast Group Membership Discovery
An advantage that IGMP version 2 has over IGMP version 1 is that a Multicast recipient can cancel his
membership in a Multicast group, thus freeing up his bandwidth more quickly. Another advantage is the
introduction of the Querier Election.
IGMP version 3 provides more security with the Source Filtering option. Multicast recipients can define the sources
from which they want to receive Multicast data streams. The router blocks Multicast data streams with other source
addresses.
The different versions of IGMP are compatible downwards. 

This means that an IGMP version 3 router can also process version 1 and version 2. If there are different IGMP
versions in a subnetwork, the participating routers agree on the smallest version.

MULTICAST ROUTING
PIM-DM/DVMRP
8.3 PIM-DM/DVMRP
PIM-DM (Protocol Independent Multicast - Dense Mode) is a routing protocol that uses the available Unicast
routing table of other protocols to steer Multicast data streams.
This ability, and the fast convergence it enables, is the reason why PIM-DM is now very widely-used.
The DVMRP (Distance Vector Multicast Routing Protocol) is a routing protocol that uses its own distance vector
algorithm to create its own Multicast routing table. DVMRP works similarly to RIP and is limited to 32 hops.
In the past, DVMRP was very widely-used, and today it is used because of its compatibility with existing
applications.
Both protocols use what is known as the Implicit Join method, which means that a participant who has left the
Multicast data stream is not included in the data flow. To enable a participant who has left to receive Multicase
data streams again, the routers transmit to all participants again after the hold time has elapsed. For DVMRP, the
hold time is fixed at 2 hours. For PIM-DM, the variable hold time is set at 210 seconds. PIM-DM requires that you
set the hold time to the same value for all the participating routers.
DVMRP PIM-DM
Knows the topology better because DVMRP uses its own protocol. Fast convergence
Optimization through changeable timers
Table 17: Advantages of the protocols
In the first step for setting up the Multicast routes, a PIM-DM/DVMRP router floods Multicast data streams to all
ports, with the exception of the receiving port (= flooding).
IP: 10.0.3.0/24 IP: 10.0.4.0/24 IP: 10.0.5.0/24
Multicast
IP: 10.0.1.0/24 IP: 10.0.2.0/24

Figure 41: Multicast Flooding

MULTICAST ROUTING
8
PIM-DM/DVMRP
Routers that are not interested in the Multicast data stream send what are known as prune messages so that they
will not be sent any Multicast data streams from this source in the future.
The routers send the prune messages back in the direction from which they received the Multicast data streams
(upstream).
A router transmits a Multicast data stream until the hold time has elapsed,
 when it is using IGMP to determine a Multicast recipient which is connected to a port directly or via a switch or
 when a router that is connected to a Multicast recipient is connected directly to a port.
IP: 10.0.3.0/24 IP: 10.0.4.0/24 IP: 10.0.5.0/24
Multicast
IP: 10.0.1.0/24 IP: 10.0.2.0/24

Figure 42: Multicast Pruning
In the second step, PIM-DM/DVMRP calculates the shortest paths (SPT - Shortest Path Tree) between the
Multicast source and the Multicast recipients. The result is the source-routed Multicast distribution tree.
Source routed means that the calculation method is tracing back from the recipient to the source (RPF - Reverse
Path Forwarding). To avoid loops, RPF rejects all Multicast data streams received at a port that do not belong to
the shortest path.
The method of the shortest paths is very efficient with regard to the data paths. However, it does have the
disadvantage that, depending on the topology, the routers require a lot of memory space to store the many
Multicast trees.

MULTICAST ROUTING
PIM-DM/DVMRP
A participant who has left the Multicast data stream can return to the Multicast data stream again. This procedure
is known as Grafting. Grafting enables the participant to receive Multicast data streams again before the hold time
has elapsed.
IP: 10.0.3.0/24 IP: 10.0.4.0/24 IP: 10.0.5.0/24
Multicast
IP: 10.0.1.0/24 IP: 10.0.2.0/24
Figure 43: Multicast Grafting

MULTICAST ROUTING
8
Scoping
8.4 Scoping
In the Multicast transmission, the protocol provides two options for limiting the expansion of the Multicast data
stream:
 Multicast Address Scoping / Boundary
In the Multicast Address Scoping, the administrator assigns a Multicast IP address range to a router interface
(see table 14). The router interface blocks the Multicast data streams with addresses within this address range.
Example:
ip mcast boundary 239.193.122.0 255.255.255.0
In this example, the router interface blocks Multicast data streams with a Multicast IP address in the range
239.193.122.0-239.193.122.255.
 TTL Scoping
Every Multicast data packet contains a TTL (Time To Live). The TTL is a counter which each router de-
increments when it transmits a Multicast data packet.
In TTL Scoping, the administrator assigns a TTL threshold to an interface. The router interface blocks every
Multicast data packet for which the TTL is below the TTL threshold.
Example:
ip multicast ttl threshold 64
In this example, the router interface blocks Multicast data streams with a TTL whose value is less than 64.
TTL Scope
0 Restricted to the same host
1 Restricted to the same subnet
< 32 Restricted to a particular location, organization or department
< 64 Restricted to the same region
< 128 Restricted to the same continent
< 255 Unrestricted, global
Table 18: Usual scope for TTLs

MULTICAST ROUTING
Multicast Configuration
8.5 Multicast Configuration
Select the Multicast protocol that suits your application best.

As the Multicast routing protocols use different methods for the Multicast transmission, the router prevents you
from using more than one Multicast routing protocol at the same time. 
When one Multicast routing protocol is activated, the router deactivates any other active Multicast routing protocol.
8.5.1 Example with Layer 3 Redundancy

The Multicast configuration consists of the following steps:
 Configure the routing function on the participating routers - for example, with OSPF (see on page 79
„Configuring OSPF“).
 Specify Multicast addresses, if applicable.
 Configure router interfaces. This also includes
 specifying the Multicast boundaries,
 activating IGMP
 activating the selected Multicast routing protocol.
 Globally activate IGMP and therefore also IGMP Snooping.
 Globally activate the Multicast routing protocol.
 Activate Multicast transmission (forwarding).
IP: 10.0.3.2/24
GW: 10.0.3.1 IP: 10.0.4.2/24
GW: 10.0.4.1
Interface: 2.2
IP: 10.0.3.1/24 Interface: 2.1
IP: 10.0.4.1/24
Interface: 1.3 A Interface: 1.2
IP: 10.0.1.2/24 IP: 10.0.10.2/24 IP: 10.0.11.1/24
GW: 10.0.1.1
Interface: 1.2
Interface: 1.4 Interface: 1.2 IP: 10.0.11.2/24
IP: 10.0.1.1/24 IP: 10.0.10.1/24
C B
Interface: 1.3 Interface: 1.3 IP: 10.0.2.0/24
IP: 10.0.12.1/24 IP: 10.0.12.2/24
Figure 44: Multicast example configuration
 Configure router interfaces using the example of router A (see fig. 44):

MULTICAST ROUTING
8

ip multicast ttl-threshold 3 Set threshold for Multicast expansion (see on page 96 „Scoping“).
ip igmp Activate IGMP at port.
ip pimdm mode Activate PIM-DM as multicast protocol.

interface 1/3 Switch to the Interface Configuration mode of Interface 1/3.

 Globally activate IGMP using the example of router A (see fig. 44):
 Globally activate Multicast using the example of router A (see fig. 44):
ip pimdm Select the Multicast routing protocol in the configuration mode.
ip multicast Globally activate Multicast forwarding.
 Check the Multicast routing settings

#show ip pimdm
Admin Mode..................................... Enable
PIM-DM INTERFACE STATUS

Interface Interface Mode Protocol State
--------- --------------- ---------------
1/3 Enable Operational
#show ip mcast
Admin Mode..................................... Enable

Protocol State................................. Operational
Table Max Size ................................ 256
Number Of Packets For Which Source Not Found .. 0
Number Of Packets For Which Group Not Found ... 0
Protocol....................................... PIMDM
Entry Count ................................... 0
Highest Entry Count ........................... 0
#show ip mcast mroute summary
Multicast Route Table Summary

Incoming Outgoing
Source IP Group IP Protocol Interface Interface List
--------------- --------------- -------- --------- ---------------
10.0.1.159 239.192.1.1 PIMDM 1/3 2/1
10.0.1.159 239.192.1.1 PIMDM 1/3 2/2

MULTICAST ROUTING
#show ip igmp
IGMP Admin Mode................................ Enable
IGMP INTERFACE STATUS

Interface Interface Mode Protocol State
--------- --------------- ---------------
#show ip igmp interface 2/1
Slot/Port...................................... 2/1
IGMP Admin Mode................................ Enable
Interface Mode................................. Enable
IGMP Version................................... 2
Query Interval (secs).......................... 125
Query Max Response Time (1/10 of a second)..... 100
Robustness..................................... 2
Startup Query Interval (secs) ................. 1
Startup Query Count............................ 2
Last Member Query Interval (1/10 of a second).. 10
Last Member Query Count........................ 2
 Configure router B and router C in the same way as router A.

MULTICAST ROUTING
8
8.5.2 Example with Layer 2 Redundancy

VLAN 1 is assigned to the MRP or E-MRP-Ring.
 Assign other VLAN IDs to the connected VLANs and leave the MRP-/E-MRP-Ring on its own in VLAN 1. You
thus enable the transmission of the Multicast data streams on Layer 3.
If you assign multiple VLANs to the MRP-/E-MRP-Ring as transfer networks, then the Switch transmits the
Multicast data streams to every transfer network during the flood and prune phases. This means that the Switch
transmits the Multicast data streams to every VLAN and the network load is thus multiplied in the MRP-/E-MRP-
Ring.
IP: 10.0.3.12/24 VLAN 3

GW: 10.0.3.1 IP: 10.0.3.11/24
GW: 10.0.3.1
Interface: 9.2
IP: 10.0.3.1/24 Interface: 9.2
IP: 10.0.3.1/24
Interface: 9.1 A Interface: 9.1
IP: 10.0.10.3/24 IP: 10.0.10.3/24
IP: 10.0.1.2/24
GW: 10.0.1.1 E-MRP-Ring
VLAN 1
Interface: 9.2 Interface: 9.1 Interface: 9.1
VLAN 2 IP: 10.0.1.1/24 IP: 10.0.10.1/24 IP: 10.0.10.2/24
Interface: 9.1
C Interface: 9.1 IP: 10.0.10.2/24 B
IP: 10.0.10.1/24 RM
IP: 10.0.2.0/24
Figure 45: Multicast example configuration with E-MRP-Ring

MULTICAST ROUTING
8.5.3 Tips for the configuration
 Selection of the PIM-DM Multicast routing protocol

You select PIM-DM if your application requires fast switching times and is able to tolerate any packet
duplications during the switching time. You set fast switching times by reducing the “Hello Time”.
Packet duplications occur when multiple routers are connected to a subnetwork. In this case, the Assert
Process clarifies which router is permitted to send into the subnetwork. Until this is clarified, all routers send
into this subnetwork.
 Selection of the DVMRP Multicast routing protocol

You select DVMRP if your application does not tolerate packet duplications and is content with higher switching
times. 
DVMRP provides a big advantage when you are using subdivided subnetworks/VLANs in a MRP-/E-MRP-
Ring. Using its own Multicast routing tables, DVMRP already knows the topology and thus prevents packet
duplications.
 Reducing the switching times

With both DVMRP and PIM-DM you can reduce the switching times by reducing the IGMP Querier Interval on
the router interface. This reduction becomes effective when an inactive router to which Multicast recipients are
connected becomes active again.

ip igmp query-max-response-time 10 Set the Query Max Response Time smaller than the Query Interval 
In this example: 1 second,
Default setting: 10 seconds
ip igmp query-interval 5 Set the Query Interval
In this example: 5 seconds
Default setting: 125 seconds.
With PIM-DM, if you reduce the Hello Time, a router can detect more quickly when a downstream router
becomes inactive or active again.
ip pimdm query-interval 1 Set the PIM-DM Query Intervall (Hello Time) 

In this example: 1 second,
Default setting: 30 seconds
With PIM-DM, using a default route that has been entered can reduce the switching time. While the router is
gathering information about the path to the source (RPF), the router can use a default route that has been
entered.
ip route 10.0.3.0 255.255.255.0 10.0.2.2 Create the static default route.

 Special feature of VLAN routing

The router floods a Multicast data stream to all ports of a VLAN routing interface if
– the Multicast data stream comes from another subnetwork and
– at least one recipient on this VLAN interface has registered via IGMP for this Multicast data stream.

MULTICAST ROUTING
8
IGMP global = on VLAN-based VLAN-based

VLAN 1 VLAN 2
Subnet A Subnet B
IGMP-Report IGMP-Report
A
Figure 46: Registered Multicast data stream on the VLAN routing interface

APPENDIX
A Appendix

APPENDIX
A
Abbreviations used
A.1 Abbreviations used
ABR Area Border Router

AS Autonomous System
ASBR Autonomous System Border Router
BC Broadcast
BDR Backup designated Router
BGP Border Gateway Protocol
BOOTP Bootstrap Protocol
CIDR Classless Inter Domain Routing
CLI Command Line Interface
CRA Configuration Recovery Adapter
DHCP Dynamic Host Configuration Protocol)
DR Designated Router
DVMRP Distance Vector Multicast Routing Protocol
EUI Extended Unique Identifier
E-VRRP Enhanced Virtual Router Redundancy
Protocol
FDB Forwarding Database
GARP General Attribute Registration Protocol
GMRP GARP Multicast Registration Protocol
http Hypertext Transfer Protocol
IANA Internet Assigned Numbers Authority
ICMP Internet Control Message Protocol
IGMP Internet Group Management Protocol
IGP Interior Gateway Protocol
IP Internet Protocoll
LED Light Emitting Diode
LLDP Link Layer Discovery Protocol
LSA Link Status Advertisement
LSD Link State Database
MAC Media Access Control
MC Multicast
NSSA Not So Stubby Area
NTP Network Time Protocol
OSPF Open Shortest Path First
OUI Organizationally Unique Identifier
PC Personal Computer
PIM-DM Protocol Independent Multicast-Dense Mode
PIM-SM Protocol Independent Multicast-Sparse Mode
PTP Precision Time Protocol
RFC Request For Comment
RM Redundanz Manager
RSTP Rapid Spanning Tree Protocol
RIP Routing Information Protocol
RPF Reverse Path Forwarding
SFP Small Form-factor Pluggable
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SPT Shortest Path Tree
TCP Transfer Control Protocol
tftp Trivial File Transfer Protocol
TP Twisted Pair
TTL Time-to-live
UDP User Datagramm Protocol
URL Uniform Resourve Locator
UTC Coordinated Universal Time

APPENDIX
Abbreviations used
VL Virtual Link
VLAN Virtual Local Area Network
VLSM Variable Length Subnet Mask
VRID Virtual Router Identification
VRRP Virtual Router Redundancy Protocol

APPENDIX
A
Underlying IEEE Standards
A.2 Underlying IEEE Standards
 IEEE 802.1AB
Topology Discovery (LLDP)
 IEEE 802.1D
Switching, GARP, GMRP, Spanning Tree (Supported via 802.1S implementation)
 IEEE 802.1D-1998
Media Access Control (MAC) Bridges (includes IEEE 802.1p Priority and 
Dynamic Multicast Filtering, GARP, GMRP)
 IEEE 802.1Q-1998
Virtual Bridged Local Area Networks (VLAN Tagging, Port Based VLANs, 
GVRP)
 IEEE 802.1S
Multiple Spanning Tree
 IEEE 802.1v
Protocol Based VLANs
 IEEE 802.1 w.2001
Rapid Reconfiguration, Supported via 802.1S implementation
 IEEE 802.1 X
Port Authentication
 IEEE 802.3 - 2002
Ethernet
 IEEE 802.3 ac
VLAN Tagging
 IEEE 802.3 ad
Link Aggregation with Static LAG and LACP support
 IEEE 802.3 x
Flow Control

APPENDIX
List of RFCs
A.3 List of RFCs
 RFC 768 (UDP)

 RFC 783 (TFTP)
 RFC 791 (IP)
 RFC 792 (ICMP)
 RFC 793 (TCP)
 RFC 826 (ARP)
 RFC 854 (Telnet)
 RFC 855 (Telnet Option)
 RFC 951 (BOOTP)
 RFC 1112 (Host Extensions for IP Multicasting)
 RFC 1155 (SMIv1)
 RFC 1157 (SNMPv1)
 RFC 1212 (Concise MIB Definitions)
 RFC 1213 (MIB2)
 RFC 1493 (Dot1d)
 RFC 1542 (BOOTP-Extensions)
 RFC 1643 (Ethernet-like -MIB)
 RFC 1757 (RMON)
 RFC 1867 (HTML/2.0 Forms w/ file upload extensions)
 RFC 1901 (Community based SNMP v2)
 RFC 1905 (Protocol Operations for SNMP v2)
 RFC 1906 (Transport Mappings for SNMP v2)
 RFC 1907 (Management Information Base for SNMP v2)
 RFC 1908 (Coexistence between SNMP v1 and SNMP v2)
 RFC 1945 (HTTP/1.0)
 RFC 2068 (HTTP/1.1 protocol as updated by 
draft-ietf-http-v11-spec-rev-03)
 RFC 2131 (DHCP)
 RFC 2132 (DHCP-Options)
 RFC 2233 The Interfaces Group MIB using SMI v2
 RFC 2236 (IGMPv2)
 RFC 2246 (The TLS Protocol, Version 1.0)
 RFC 2271 (SNMP Framework MIB)
 RFC 2346 (AES Ciphersuites for Transport Layer Security)
 RFC 2362 (PIM-SM)
 RFC 2365 (Administratively Scoped Boundaries)
 RFC 2570 (Introduction to SNMP v3)
 RFC 2571 (Architecture for Describing SNMP Management Frameworks)
 RFC 2572 (Message Processing and Dispatching for SNMP)
 RFC 2573 (SNMP v3 Applications)
 RFC 2574 (User Based Security Model for SNMP v3)
 RFC 2575 (View Based Access Control Model for SNMP)
 RFC 2576 (Coexistence between SNMP v1,v2 & v3)
 RFC 2578 (SMI v2)
 RFC 2579 (Textual Conventions for SMI v2)
 RFC 2580 (Conformance statements for SMI v2)
 RFC 2613 (SMON)
 RFC 2618 (RADIUS Authentication Client MIB)
 RFC 2620 (RADIUS Accounting MIB)
 RFC 2674 (Dot1p/Q)
 RFC 2818 (HTTP over TLS)
 RFC 2851 (Internet Addresses MIB)
 RFC 2865 (RADIUS Client)
 RFC 2866 (RADIUS Accounting)
 RFC 2868 (RADIUS Attributes for Tunnel Protocol Support)

APPENDIX
A
List of RFCs
 RFC 2869 (RADIUS Extensions)

 RFC 2869bis (RADIUS support for EAP)
 RFC 2933 (IGMP MIB)
 RFC 3164 (The BSD Syslig Protocol)
 RFC 3376 (IGMPv3)
 RFC 3580 (802.1X RADIUS Usage Guidelines)
 RFC 4330 (SNTP, obsoletes RFCs 1769 and 2330)
 Routing
 RFC 826 Ethernet ARP
 RFC 894 Transmission of IP Datagrams over Ethernet Networks
 RFC 896 Congestion Control in IP/TCP Networks
 RFC 919 IP Broadcast
 RFC 922 IP Broadcast in the presence of subnets
 RFC 950 IP Subnetting
 RFC 1027 Using ARP to implement Transparent Subnet Gateways (Proxy ARP)
 RFC 1256 ICMP Router Discovery Messages
 RFC 1321 Message Digest Algorithm
 RFC 1519 CIDR
 RFC 1724 RIP v2 MIB Extension
 RFC 1765 OSPF Database Overflow
 RFC 1812 Requirements for IP Version 4 Routers
 RFC 1850 OSPF MIB Draft-ietf-ipv6-rfc2096-update-07.txt 
IP Forwarding Table MIB
 RFC 2082 RIP-2 MD5 Authentication
 RFC 2131 DHCP Relay
 RFC 2328 OSPF Version 2
 RFC 2453 RIP v2
 RFC 2787 VRRP MIB
 RFC 2863 The Interfaces Group MIB
 RFC 2932 IPv4 Multicast Routing MIB
 RFC 2934 PIM MIB for IPv4
 RFC 3046 DHCP/BootP Relay
 RFC 3101 The OSPF "Not So Stubby Area" (NSSA) Option
 RFC 3376 IGMPV3
 RFC 3768 VRRP, Virtual Router Redundancy Protocol
 Draft-holbrook-idmr-igmpv3-ssm-08.txt – IGMPv3 / MLDv2 for SSM
 Draft-ietf-idmr-dvmrp-mib-11.txt – DVMRP MIB
 Draft-ietf-idmr-dvmrp-v3-10 – DVMRP
 Draft-ietf-magma-igmpv3-and-routing-05.txt – IGMPv3 an Multicast Routing Protocol Interaction
 Draft-ietf-magma-mgmd-mib-03.txt – Multicast Group Membership Discovery MIB
 Draft-ietf-pim-v2-dm-03 – PIM-DM
 Draft-ietf-smm-arch-06.txt – Source -Specific Multicast for IP

APPENDIX
Entering the IP Parameters
A.4 Entering the IP Parameters
see OSPF
Area 0
see “Port-based Router-Interface” see “VLAN-based Router-Interface”
SN 10 SN 11
A VLAN ID 2
E-MRP-Ring
C B
VRRP SN 12
SN 13
see “VRRP”
SN 14
Figure 47: Network plan
To configure the layer 3 function, you require access to the management of the Switch, as described in the “Basic
Configuration” user manual.
Depending on your own application, you will find many options for assigning IP addresses to the devices. The
following example describes one option that often arises in practice. Even if you have other prerequisites, this
example shows the general method for entering the IP parameters and points out important things that you should
note.
The prerequisites for the following example are:

 All layer 2 and layer 3 switches have the IP address 0.0.0.0 
(= state on delivery)
 The IP addresses of the switches and router interfaces and the gateway IP addresses are defined in the
network plan.
 The devices and their connections are installed.
 Redundant connections are open (see VRRP and E-MRP-Ring). To avoid loops in the configuration phase,
close the redundant connections only after the configuration phase.

APPENDIX
A
IP = 10.0.200.11/24
IP = 10.0.100.10/24 Area 0 IP = 10.0.11.11/24

=> 10.0.10.10/24 GW: 10.0.11.1
GW: 10.0.100.1
=> 10.0.10.1
IP = 10.0.10.11/24 IP = 10.0.11.12/24
GW: 10.0.10.1 Management-IP= GW: 10.0.11.1
10.0.100.101
SN 10
10.0.10.0 A SN 11
IP = 10.0.10.13/24 10.0.11.0
GW: 10.0.10.1 VLAN ID 2
E-MRP-Ring
SN 100
10.0.100.0 Management-IP=
Management-IP= 10.0.100.102
10.0.100.103 VLAN ID 1
IP = 10.0.13.14/24 C B
GW: 10.0.13.1 SN 12
VRRP 10.0.12.0
SN 13
10.0.13.0
IP = 10.0.12.13/24
GW: 10.0.12.1
IP = 10.0.13.13/24
GW: 10.0.13.1
IP = 10.0.14.11/24
IP = 10.0.14.14/24 GW: 10.0.14.1
GW: 10.0.14.1
SN 14
10.0.14.0
IP = 10.0.14.13/24 IP = 10.0.14.12/24
GW: 10.0.14.1 GW: 10.0.14.1
Figure 48: Network plan with management IP addresses
 Assign the IP parameters to your configuration computer. During the configuration phase, the configuration
computer is located in subnet 100. This is necessary, so that the configuration computer has access to the
layer 3 switches throughout the entire configuration phase.
 Start AFS Finder on your configuration computer.
 Give all the layer 2 and layer 3 switches their IP parameters in accordance with the network plan.
You can access the devices in subnets 10 to 14 again when you have completed the following router
configuration.
 Configure the router function for the layer 3 switches.
Note the sequence:
1. Layer 3 switch C
2. Layer 3 switch B
The sequence is important; you thus retain access to the devices.
As soon as you assign an IP address from the subnet of the management IP address (= SN 100) to a router
interface, the Switch deletes the management IP address. You access the Switch via the IP address of the
router interface.

APPENDIX
IP = 10.0.200.11/24
Port 2.2:
IP = 10.0.200.10/24
Port 2.1: GW: 10.0.200.11
VLAN 1 (Management IP=10.0.100.101)
--> IP= 10.0.10.1/24
GW: 10.0.200.10 Port 3.1 - Port 3.4:
VLAN 2
Interface 9.2
A IP = 10.0.11.1/24
GW: 10.0.200.10
E-MRP-Ring
SN 100
Port 1.1: 10.0.100.0
VLAN 1 VLAN 1 Port 1.2:
Interface 9.1 VLAN 1
IP = 10.0.100.1/24 Interface 9.1
GW: 10.0.200.10 IP = 10.0.100.1/24
GW: 10 0 200 10
Figure 49: IP parameters for layer 3 switch A
 Configure the router function for layer 3 switch A.

You first configure the router interface at a port to which the configuration computer is connected. The result of
this is that in future you will access the layer 3 switch via subnet 10.
 Change the IP parameters of your configuration computer to the values for subnet 10. You thus access layer
3 switch A again, namely via the IP address of the router interface set up beforehand.
 Finish the router configuration for layer 3 switch A (see fig. 49).
After the configuration of the router function on all layer 3 switches, you have access to all the devices.

APPENDIX
A
Copyright of Integrated Software
A.5 Copyright of Integrated Software
A.5.1 Bouncy Castle Crypto APIs (Java)

The Legion Of The Bouncy Castle
Copyright (c) 2000 - 2004 The Legion Of The Bouncy Castle 
(http://www.bouncycastle.org)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
A.5.2 Broadcom Corporation

(c) Copyright 1999-2007 Broadcom Corporation. All Rights Reserved.

INDEX
B Index
A IGMP 92
ABR 69, 72 IGMP Querier Interval 101
Address Resolution Protocol 9 Implicit Join 93
Adjacency 75 Importance 23, 25, 26
Advertisement 43 Infinity 62
Advertisement interval 43 Interface tracking 31, 32, 36, 37, 54
AFS View 3 Interface tracking object 32
Aging time 92 Interner Router 72
Area Border Router 69, 72 Internet Group Management Protocol 92
ARP 9, 10, 29 IP 8
ARP data packet 83 IP address 42
ASBR 68, 72 IP address owner 42, 43
Assert process 101 IP data packet 83
Autonomous System Area Border Router 72 IP stack 29
Autonomous System Boundary Router 68 ISO/OSI layer model 7
B L
Backup Designated Router 75, 77 Leave message 92
Backup router 43 Link aggregation interface 32
BDR 75 Link down delay 32
Boundary 96 Link State Advertisement 72
Broadcast 7 Link State Database 77
Link up delay 32
C Link-down notification 46
CIDR 11, 67, 80 Load sharing 25
Classless Inter-Domain Routing 11, 67 Logic tracking 31
Convergence 59 Logical tracking 35, 38
Count-to-infinity 62 LSA 72, 77
D LSD 77
Default gateway 42, 43 M
Designated Router 75, 77 MAC address 7, 42
Distance 23, 25 MAC/IP address resolution 29
Distance vector algorithm 59 Master router 43
Distance Vector Multicast Routing Protocoll 93 Metric 59
DR 75 MRP 3
DVMRP 93 MRP-/E-MRP-Ring 101
E MRP-Ring 3
Multicast 7
E-VRRP 45
Multicast address 75, 87
Extended Unique Identifier 90
Multinetting 13
F N
Flooding 93
Neighbor relationship 75
G Netdirected Broadcasts 12
Grafting 95 Netdirected Broadcasts (Port-basiert) 17
Netdirected Broadcasts (VLAN-basiert) 20
H Network Management Software 3
Hello 75 Network plan 5
Hop count 59, 62 Next hop 59
I Not So Stubby Area 69
NSSA 69
IANA 88

INDEX
B
O Source routed 94
Open Shortest Path First 67 SPF 78
Operand 38 Split horizon 62
Operators 35 SPT 94
Organizationally Unique Identifier 90 Static route tracking 26
OSI layer model 7 Static routes 5
OSI reference model 7 Static routing 31
OSPF 5, 59, 67 Stub Area 69
OUI 90 Switching times 101
Symbol 4
P
Packet duplication 101 T
PIM-DM 93 Time To Live 96
Ping interval 33 Totally Stubby Area 69
Ping request 33 Tracking 26, 31
Ping response 33 Tracking (VRRP) 31
Ping timeout 33 TTL 96
Ping tracking 26, 31, 33
U
Port-based router Interface 16
Upstream 94
port-based router interface 29
Preempt delay 46 V
Preempt mode 46 Variable Length Subnet Mask 67
Preference 52 Virtual link 70
Protocol Independent Multicast - Dense Mode 93 Virtual MAC address 42
Protocol-based VLAN 83 Virtual router 43
Proxy ARP 10 Virtual router ID 42
Prune messages 94 Virtual router interface 84
Q Virtual router IP address 43
Virtual router MAC address 43
Querier Election 92
VL 70
R VLAN protocol group 84
Redistribute 69 VLAN router interface 32
Redistributing 69 VLAN routing 84
Redistribution 68 VLAN-based router interface 29
Redundancy 3 VLSM 67
Redundant static route 23 VRID 42, 43
Report message 92 VRRP 31
Reverse Path Forwarding 94 VRRP priority 42, 43
RFC 107 VRRP router 43
Ring/Network Coupling 3 VRRP Tracking 31
RIP 5, 59
Route Summarization 69
Route tracking 26
Router ID 75
Router priority 75
Routing Information Protocol 59
Routing Table 93
Routing table 18, 19, 26, 59
Routing tables 46
RPF 94
S
Scoping 96
Shortest Path First 78
Shortest Path Tree 94
Skew time 43
Source filtering 92

Contact us
1KHD642916 Printed in Switzerland (1011-0000-0)

ABB Switzerland Ltd
Power Systems
Bruggerstrasse 72
5400 Baden
Tel.: +41 58 585 77 44
+41 58 585 55 77
E-mail: [email protected]
www.abb.com/utilitycommunication

Manual Router AFR677

Uploaded by

Copyright:

Available Formats

Manual Router AFR677

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Router AFR677

Uploaded by

Copyright:

Available Formats

What are the main routing protocols discussed in the document?

What are the main routing protocols discussed in the document?

What is the difference between static and dynamic routing?

What is the difference between static and dynamic routing?

ABB Power Systems

Copyright and Confidentiality: Copyright in this document vests in ABB LTD. 

Blank pages: Any blank page present is to accommodate double-sided printing.

Document No.: 1KHD642916

ABB Switzerland Ltd

ABB Web-based Interface Reference Manual 1

2 Web-based Interface Reference Manual ABB

About this Manual

ABB Routing Configuration User Manual 3

The designations used in this manual have the following meanings:

WLAN access point

Router with firewall

Switch with firewall

4 Routing Configuration User Manual ABB

 Drawing a network plan

 Router basic settings

 Selecting a routing procedure

 Configuring a routing procedure

ABB Routing Configuration User Manual 5

6 Routing Configuration User Manual ABB

7 Application Access to communication services from an application program

Table 1: OSI Reference Model

Layer 7 Layer-2-Switch Layer 7 Layer 7 Layer-3-Switch/ Layer 7

ABB Routing Configuration User Manual 7

8 Routing Configuration User Manual ABB

Figure 3: ARP request and reply

ABB Routing Configuration User Manual 9

Layer 4 and higher

Figure 5: ARP proxy funktion

10 Routing Configuration User Manual ABB

Class Network part Host part Address range

Table 2: IP address classes

ABB Routing Configuration User Manual 11

1.3 Net-directed Broadcasts

12 Routing Configuration User Manual ABB

Figure 6: Example of multinetting

ABB Routing Configuration User Manual 13

14 Routing Configuration User Manual ABB

Example: Connecting two networks

Configuration PC Port-based VLAN-based

Figure 7: Static routes

ABB Routing Configuration User Manual 15

2.1 Port-based Router Interface

Special features of port-based router interfaces:

16 Routing Configuration User Manual ABB

2.1.1 Configuration of the Router Interfaces

Figure 8: Simplest case of a route

enable Switch to the Privileged EXEC mode.

show ip interface brief Verify the entries.

Primary IP Address.......... ............ 10.0.1.1/255.255.255.0

show ip route Verify the routing table:

Total Number of Routes......................... 2

ABB Routing Configuration User Manual 17

Network Subnet Next Hop Next Hop

Total Number of Routes......................... 2

18 Routing Configuration User Manual ABB