Table Of Contents
Configuring Apollo Domain
Apollo Domain Addresses
Apollo Domain Configuration Task List
Enable Apollo Domain Routing
Enable Apollo Domain Routing
Enable Apollo Domain Routing on an Interface
Enable Concurrent Routing and Bridging
Control Access to the Apollo Domain Network
Tune Apollo Domain Network Performance
Configure Static Routes
Set Routing Table Update Timers
Set the Maximum Paths
Configure Apollo Domain over WANs
Monitor the Apollo Domain Network
Apollo Domain Configuration Examples
Apollo Domain Routing Example
Access List Example
Routing Table Update Timer Example
Configuring Apollo Domain
The Apollo Domain routing protocol is the native-mode networking protocol for Apollo workstations. This chapter describes how to configure Apollo Domain routing and provides configuration examples. For a complete description of the Apollo Domain commands discussed in this chapter, refer to the "Apollo Domain Commands" chapter in the Network Protocol Command Reference, Part 3. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
Note
Not all Cisco access servers support the Apollo Domain protocol. For more information, refer to the release notes for the current Cisco IOS release.
Apollo Domain Addresses
Apollo Domain network addresses are 32-bit quantities represented in hexadecimal numbers in the format network.host. Each host has a single address that is used for all its network connections.
The network number is a 12-bit number, expressed in hexadecimal, that identifies a physical network. Network numbers must be unique throughout an Apollo Domain internetwork.
The host number is a 20-bit quantity expressed in hexadecimal. An Apollo Domain host can have interfaces on more than one physical network (Ethernet, Domain Token Ring, serial line, and so on).
In the network address below 5fe identifies a physical network and 1293c identifies a host. See :
Figure 2 Apollo Domain Addresses
Apollo Domain Configuration Task List
To configure Apollo Domain routing, complete the tasks in the following sections. At a minimum, you must enable routing.
•
Enable Apollo Domain Routing
•
Control Access to the Apollo Domain Network
•
Tune Apollo Domain Network Performance
•
Configure Apollo Domain over WANs
•
Monitor the Apollo Domain Network
See the "Apollo Domain Configuration Examples" section at the end of this chapter for configuration examples.
Enable Apollo Domain Routing
To enable the Apollo Domain routing protocol, first enable it on the router, then configure each interface for Apollo Domain. These are the only tasks you must perform when configuring Apollo Domain routing.
You can route Apollo Domain on some interfaces and transparently bridge it on other interfaces simultaneously. To do this, you must enable concurrent routing and bridging. To configure an interface for concurrent routing and bridging, you use the bridge crb command to enable concurrent routing and bridging on the router.
Enable Apollo Domain Routing
To enable Apollo Domain routing, use the following command in global configuration mode:
Command
|
Purpose
|
apollo routing host
|
Enable Apollo Domain routing.
|
For an example of how to enable Apollo Domain routing, see the "Apollo Domain Routing Example" section at the end of this chapter.
Enable Apollo Domain Routing on an Interface
To enable Apollo Domain routing on an interface, use the following command in interface configuration mode:
Command
|
Purpose
|
apollo network number
|
Enable Apollo Domain routing on an interface.
|
For an example of how to enable Apollo Domain routing, see the "Apollo Domain Routing Example" section at the end of this chapter.
Enable Concurrent Routing and Bridging
To enable concurrent routing and bridging, use the following command in global configuration mode:
Command
|
Purpose
|
bridge crb
|
Enable concurrent routing and bridging.
|
Control Access to the Apollo Domain Network
To control access to Apollo Domain networks, you create access lists and then apply them to individual interfaces. Apollo Domain access lists control access based on a range of network numbers. The conditions defined in access lists are applied to outgoing routed packets.
Keep the following in mind when configuring Apollo Domain network access control:
•
Access list entries are evaluated in the order you enter them, and the first matching entry is used. To improve performance, place the most commonly matched entries near the beginning of the access list.
•
An implicit deny everything entry is defined at the end of an access list unless you include an explicit permit everything entry at the end of the list.
•
All new entries to an existing list are placed at the end of the list. You cannot add an entry to the middle of a list. This means that if you have previously included an explicit permit everything entry, new entries will never be scanned. The solution is to delete the access list and retype it with the new entries.
To create an access list, use the following command in global configuration mode:
Command
|
Purpose
|
apollo access-list access-list-name {deny | permit} [firstnet-]lastnet.host [wildcard-mask]
|
Create an Apollo Domain access list.
|
To apply an access list to an interface and activate it on that interface, use the following command in interface configuration mode:
Command
|
Purpose
|
apollo access-group access-list-name
|
Apply an access list name to an interface.
|
For an example of creating and applying an access list, see the "Access List Example" section at the end of this chapter.
Use the show apollo interface command to display the filters defined on an interface.
Tune Apollo Domain Network Performance
To tune Apollo Domain network performance, perform one or more of the following tasks:
•
Configure Static Routes
•
Set Routing Table Update Timers
•
Set the Maximum Paths
Configure Static Routes
The Cisco IOS software uses metrics to determine the best path over which packets should be transmitted. However, you may want to add static routes to the routing table to explicitly specify paths to certain destinations. Static routes always override any paths determined by metrics.
Be careful when assigning static routes. When links associated with static routes are lost, traffic may stop being forwarded, or traffic may be forwarded to a nonexistent destination, even though an alternative path might be available.
To add a static route to the Cisco IOS software's routing table, use the following command in global configuration mode:
Command
|
Purpose
|
apollo route destination-network network.host
|
Add a static route to the routing table.
|
Set Routing Table Update Timers
You can set how often the entries in the routing table are updated. Note, however, that you should set this interval only in a configuration in which all routers are Cisco routers.
To set how often the entries in the routing table are updated, use the following command in interface configuration mode:
Command
|
Purpose
|
apollo update-time interval
|
Set the interval after which the routing table should be updated.
|
For an example of setting routing table update timers, see the "Routing Table Update Timer Example" section at the end of this chapter.
Set the Maximum Paths
You can set the maximum number of equal-cost, parallel paths to a destination. (Note that when paths have differing costs, the Cisco IOS software chooses lower-cost routes in preference to higher-cost routes.) The software distributes output on a packet-by-packet basis in round-robin fashion. That is, the first packet is sent along the first path, the second packet along the second path, and so on. If the final path is reached before all packets are sent, the next packet is sent to the first path, the next to the second path, and so on. This round-robin scheme is used regardless of whether fast switching is enabled.
Limiting the number of equal-cost paths can save memory on routers with limited memory or very large configurations. Additionally, in networks with a large number of multiple paths and systems with limited ability to cache out-of-sequence packets, performance might suffer when traffic is split between many paths.
To set the maximum number of paths, use the following command in global configuration mode:
Command
|
Purpose
|
apollo maximum-paths paths
|
Set the maximum number of equal-cost paths to a destination.
|
For an example of setting the maximum number of equal-cost, parallel paths to a destination, see the section "Apollo Domain Routing Example" later in this chapter.
Configure Apollo Domain over WANs
You can configure Apollo Domain over X.25 networks. To do this, configure the appropriate address mappings as described in the "Configuring X.25 and LAPB" chapter in the Wide-Area Networking Configuration Guide.
Monitor the Apollo Domain Network
To monitor an Apollo Domain network, use one or more of the following commands at the EXEC prompt:
Command
|
Purpose
|
show apollo arp
|
List the entries in the Apollo Domain ARP table.
|
show apollo interface [type number]
|
Display the status of the Apollo Domain interfaces configured in the Cisco IOS software and the parameters configured on each interface.
|
show apollo route [network]
|
List the entries in the Apollo Domain routing table.
|
show apollo traffic
|
Display information about the Apollo Domain packets transmitted and received.
|
Apollo Domain Configuration Examples
Use the configuration examples in the following sections to help in configuring Apollo Domain routing:
•
Apollo Domain Routing Example
•
Access List Example
•
Routing Table Update Timer Example
Apollo Domain Routing Example
The following is an example of configuring Apollo Domain routing on a router with two Ethernet interfaces. The first set of commands does the following:
•
Enables the Apollo Domain routing protocol.
•
Assigns an Apollo Domain network address.
•
Assigns network numbers to two Ethernet interfaces.
The second set of commands does the following:
•
Assigns the router whose host number is 23d5a to handle all traffic routed over network 35.
•
Allows traffic to be routed over a maximum of four paths.
•
Sets the timer to update the routing table for Ethernet interface 0 every 40 seconds.
Create an access list called doc that denies access to networks 2a through 2f, and apply this access list to Ethernet interface 1. This means that packets destined for these networks that are sent out Ethernet interface 1 will be blocked.
apollo access-list doc deny 2a-2f
Access List Example
The following example creates an Apollo Domain access list and applies it to Ethernet interface 0. In this example, the first line denies access to networks 3a through 3f, the second line denies access to the host 5fe.1293.c, and the third line permits access to all other networks and hosts. The access list conditions will be applied to all routed packets going out Ethernet interface 0.
apollo access-list eng deny 3a-3f.0 ffff
apollo access-list eng deny 5fe.1293c
apollo access-list eng permit -1.0 ffff
Routing Table Update Timer Example
The following example sets the update times on two interfaces in the router. The update timer granularity would be 20 seconds, because this is the lowest value specified.