|
|
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 Cisco IOS Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Command Reference publication. 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 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).
For the network address 5fe.1293c in Figure 2, 5fe identifies a physical network and 1293c identifies a host.
To configure Apollo Domain routing, perform the tasks in the following sections.
See the "Apollo Domain Configuration Examples" section at the end of this chapter for configuration examples.
You configure Apollo Domain routing by first enabling it on the router, then configuring it on each interface.
To configure the Apollo Domain routing protocol, perform the tasks in the following sections:
To enable Apollo Domain routing, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
apollo routing host |
For an example of how to enable Apollo Domain routing, see the "Apollo Domain Routing Example" section at the end of this chapter.
To enable Apollo Domain routing on an interface, use the following command in interface configuration mode:
| Command | Purpose |
|---|---|
apollo network number |
For an example of how to enable Apollo Domain routing, see the "Apollo Domain Routing Example" section at the end of this chapter.
You can route Apollo Domain on some interfaces and transparently bridge it on other interfaces simultaneously. To enable this type of routing, 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.
|
NoteWhen Apollo Domain routing protocol is enabled, fast switching of Apollo packets is not supported. Therefore, in most cases, configuring an interface for bridging can provide enhanced packet transfer performance. |
To enable concurrent routing and bridging, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
bridge crb |
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. Theconditions defined in access lists are applied to outgoing routed packets.
Remember the following when you configure Apollo Domain network access control:
To create an access list, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
apollo access-list access-list-name |
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 |
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.
To tune Apollo Domain network performance, perform one or more of the following tasks:
The Cisco IOS software uses metrics to determine the best path over which packets should be sent. 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 routing table, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
apollo route destination-network network.host |
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.
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.
To monitor an Apollo Domain network, use one or more of the following commands in EXEC mode:
Use the configuration examples in the following sections to help in configuring Apollo Domain routing:
The following example shows how to configure Apollo Domain routing on a router with two Ethernet interfaces. The first set of commands does the following:
The second set of commands does the following:
Create an access list called doc that denies access to networks 2a through 2f, and apply this access list to Ethernet interface 1. In this example, packets destined for these networks that are sent out Ethernet interface 1 will be blocked.
apollo routing 23d5a interface ethernet 0 apollo network 5f interface ethernet 1 apollo network 4e ! apollo route 35 23d5a apollo maximum-paths 4 interface ethernet 0 apollo update-time 40 apollo access-list doc deny 2a-2f interface ethernet 1 apollo access-group doc
The following example shows how to create 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 ! interface ethernet 0 apollo access-group eng
The following example shows how to set the update times on two interfaces in the router. The update timer granularity would be 20 seconds, because this is the lowest value specified.
interface serial 0 apollo update-time 40 interface ethernet 0 apollo update-time 20 interface ethernet 1 apollo update-time 25
Posted: Mon Jul 17 13:09:06 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.