|
|
This chapter describes how to configure LAN emulation (LANE) in Cisco 7000 series routers containing an ATM Interface Processor (AIP) and connected to a LightStream 100 ATM switch (formerly known as the Cisco HyperSwitch A100 switch). LANE requires software version 3.1 or later on the LightStream 100 ATM switch.
For a complete description of the commands in this chapter, refer to the "LAN Emulation Commands" chapter of the Router Products Command Reference publication.
Cisco's implementation of LANE makes an ATM interface look like one or more Ethernet interfaces.
LANE is an ATM service defined by the ATM Forum specification "LAN Emulation over ATM," ATM_FORUM 94-0035. This service emulates the following LAN-specific characteristics:
LANE service provides connectivity between ATM-attached devices and connectivity with LAN-attached devices. This includes connectivity between ATM-attached stations and LAN-attached stations and also connectivity between LAN-attached stations across an ATM network.
Because LANE connectivity is defined at the MAC layer, upper protocol layer functions of LAN applications can continue unchanged when the devices join emulated LANs. This feature protects corporate investments in legacy LAN applications.
An ATM network can support multiple independent emulated LAN networks. Membership of an end system in any of the emulated LANs is independent of the physical location of the end system. This characteristic enables easy hardware moves and location change. In addition the end systems can also move easily from one emulated LAN to another, independent of whether or not the hardware moves.
LAN emulation in an ATM environment provides routing between emulated LANs for supported routing protocols and high-speed, scalable switching of local traffic.
In this release, Cisco supports the following networking features:
This release of LANE is supported on Cisco 7000 routers each containing an ATM Interface Processor (AIP); it requires a Cisco LightStream 100 workgroup ATM switch.
Cisco's AIP provides a single ATM network interface for the Cisco 7000 series router. Network interfaces for the Cisco 7000 reside on modular interface processors, which provide a direct connection between the high-speed Cisco Extended Bus (CxBus) and the external networks. The maximum number of AIPs that the Cisco 7000 supports depends on the bandwidth configured. The total bandwidth through all the AIPs in the system should be limited to 200 Mbps full duplex (two TAXI interfaces, or one SONET and one E3, or one SONET and one lightly used SONET, or five E3s).
For a complete description of the Cisco 7000 and AIP, refer to the Cisco 7000 Hardware Installation and Maintenance publication.
Any number of emulated LANs can be set up in an ATM switch cloud. A router can participate in any number of these emulated LANs.
LANE is defined on a LAN client-server model. The following components are implemented in this release:
Communication among LANE components is ordinarily handled by several types of switched virtual circuits (SVCs). Some SVCs are unidirectional; others are bidirectional. Some are point-to-point and others are point-to-multipoint. Figure 11-1 illustrates the various virtual circuits that are mentioned. In this figure, LECS stands for the LANE configuration server, and BUS stands for the LANE broadcast-and-unknown server.
The following section describes various processes that occur, starting with a client requesting to join an emulated LAN after the component routers have been configured.
The following process normally occurs after a LANE client has been enabled on a router:
As communication occurs on the emulated LAN, each client dynamically builds a local LANE ARP (LE ARP) table. A client's LE ARP table can also have static, preconfigured entries. The LE ARP table maps MAC addresses to ATM addresses.
When a client first joins an emulated LAN, its LE ARP table has no dynamic entries and the client has no information about destinations on or behind its emulated LAN. To learn about a destination when a packet is to be sent, the client begins the following process to find the ATM address corresponding to the known MAC address:
For unknown destinations, the client sends a packet to the broadcast-and-unknown server, which forwards the packet to all clients; that is, it floods the packet. The broadcast-and-unknown server floods the packet because the destination might be behind a bridge that has not yet learned this particular address.
When a LANE client has broadcast or multicast traffic, or unicast traffic with an unknown address to send, the following process occurs:
On a LAN, packets are addressed by the MAC-layer address of the destination and the sources stations. To provide similar functionality for LANE, MAC-layer addressing must be supported. Every LANE client must have a MAC address. In addition, every LANE component (server, client, broadcast-and-unknown server, and configuration server) must have an ATM address that is different from that of all the other components.
In this release, all LANE clients on the same interface have the same, automatically assigned MAC address. That MAC address is also used as the end-system identifier (ESI) part of the ATM address, as explained in the following section. Although client MAC addresses are not unique, all ATM addresses are unique.
A LANE ATM address has the same syntax as an NSAP, but it is not a network-level address:
Cisco provides the following standard method of constructing and assigning ATM and MAC addresses for use in a LANE configuration server's database. A pool of MAC addresses is assigned to each ATM interface on the router. On the Cisco 7000 routers, the pool contains eight MAC addresses. For constructing ATM addresses, the following assignments are made to the LANE components:
For example, if the MAC addresses assigned to an interface are 0800.200C.1000 through 0800.200C.1007, the ESI part of the ATM addresses are assigned to LANE components as follows:
Refer to the "Multiple Emulated LANs with Unrestricted Membership Example" and the "Multiple Emulated LANs with Restricted Membership Example" sections for examples using MAC address values as ESI field values in ATM addresses and for examples using subinterface numbers as Selector field values in ATM addresses.
ATM address templates can be used in many LANE commands that assign ATM addresses to LANE components (thus overriding automatically assigned ATM addresses) or that link client ATM addresses to emulated LANs. The use of templates can greatly simplify the use of these commands. The syntax of address templates, the use of address templates, and the use of wildcard characters within an address template for LANE are very similar to those of address templates for ISO CLNS.
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character, and an ellipsis (...) to match any number of leading or trailing characters.
In LANE, a prefix template explicitly matches the prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector. The following table indicates how the values of unspecified bytes are determined when an ATM address template is used:
| Unspecified Digits In | Value Is |
|---|---|
| Prefix (first 13 bytes) | Obtained from ATM switch via ILMI |
| ESI (next 6 bytes) | Filled with the slot MAC address1 plus
|
|
Selector field (last 1 byte) | Subinterface number, in the range 0 through 255. |
The following rules apply to assigning LANE components to the major ATM interface and its subinterfaces in a given router:
In typical LANE cases, one or more Cisco 7000 routers are attached to a Cisco LightStream 100 ATM switch. The LightStream 100 switch provides connectivity to the broader ATM network switch cloud. The routers are configured to support one or more emulated LANs. One of the routers is configured to perform the LANE configuration server functions. A router is configured to perform the server function and the broadcast-and-unknown server function for each emulated LAN. (One router can perform the server function and the broadcast-and-unknown server function for several emulated LANs.) In addition to these functions, each router also acts as a LANE client for one or more emulated LANs.
This section presents two scenarios using the same Cisco 7000 routers and the same Cisco LightStream 100 workgroup ATM switch. Figure 11-2 illustrates this typical layout of one Cisco LightStream 100 ATM switch and multiple Cisco 7000 routers, and is used to illustrate both the single and the multiple emulated LAN cases.
The physical layout and the physical components of an emulated network might not differ for the single and the multiple emulated LAN cases. The differences are in the software configuration for the number of emulated LANs and the assignment of LANE components to the different physical components.
In a single emulated LAN scenario, the LANE components might be assigned as follows:
In the multiple LAN scenario, the same switch and routers are used, but multiple emulated LANs are configured. In the following scenario, three emulated LANs are configured on four routers.
The LANE components are assigned as follows:
In this scenario, once routing is enabled and network level addresses are assigned, Router 1 and Router 2 can route between the man and the eng emulated LANs, and Router 3 and Router 4 can route between the man and the mkt emulated LANs.
Before you begin to configure LANE, you must decide whether you want to set up one or multiple emulated LANs and, if multiple, where the servers and clients will be located, and whether to restrict the clients that can belong to each emulated LAN. Once you have made those basic decisions, you can proceed to configure LANE.
To configure LANE, complete the tasks in the following sections:
You can configure some emulated LANs with unrestricted membership and some emulated LANs with restricted membership. You can also configure a default emulated LAN, which must have unrestricted membership.
Once LANE is configured, you can monitor and maintain the components in the participating routers by completing the tasks in the following section:
See the "LANE Configuration Examples" section at the end of this chapter.
It might help you to begin by drawing up a plan and a worksheet for your own LANE scenario, showing the following information and leaving space for noting the ATM address of each of the LANE components on each subinterface of each participating router:
The last three items in this list are very important; they determine how you set up each emulated LAN in the configuration server's database.
Before you configure LANE components on any Cisco 7000 routers, you must configure the Cisco LightStream 100 switch with the ATM address prefix to be used by all LANE components in the switch cloud.
To set the ATM address prefix, complete the following steps on the Cisco LightStream 100 switch:
| Task | Command |
|---|---|
| Set the local node ID (prefix of the ATM address). | set local name ip-address mask prefix1 |
| Save the configuration values permanently. | save |
On the Cisco LightStream 100 switch, you can display the current prefix by using the show network command.
For each router that will participate in LANE, set up the necessary servers and clients for each emulated LAN; then display and record the server and client ATM addresses. Be sure to keep track of the router interface where the LANE configuration server will eventually be located.
If you are going to have only one default emulated LAN, you will have only one server to set up. If you are going to have multiple emulated LANs, you can set up the server for another emulated LAN on a different subinterface on the same interface of this router--or you can place it on a different router.
When you set up a server and broadcast-and-unknown server on a router, you can combine it with a client on the same subinterface, a client on a different subinterface, or no client at all on the router.
It is important where you put the clients, because any router with clients for multiple emulated LANs can route frames between those emulated LANs.
To set up the server, broadcast-and-unknown server, and a client on the same subinterface, complete the steps in the following sections:
To set up only a client on a subinterface, complete the steps in the following sections:
Once you have set up the components, you can display their ATM addresses by completing the task in the following section:
You must set up the signaling PVC and the PVC that will communicate with the ILMI on the major ATM interface of any router that will participate in LANE.
Complete this task only once for a major interface. You do not need repeat this task on the same interface even though you might configure LANE servers and clients on several of its subinterfaces.
To set up these PVCs, complete the following tasks, beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify the major ATM interface and enter interface configuration mode. | interface atm slot/port |
| Step 2 Set up the signaling PVC that sets up and tears down SVCs; the vpi and vci values are usually set to 0 and 5, respectively. | atm pvc vcd vpi vci qsaal1 |
| Step 3 Set up a PVC to communicate with the ILMI; the vpi and vci values are usually set to 0 and 16, respectively. | atm pvc vcd vpi vci ilmi1 |
To set up the server and broadcast-and-unknown server for an emulated LAN, perform the following steps beginning in interface configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify the subinterface for the first emulated LAN on this router. | interface atm slot/port.subinterface-number |
| Step 2 Enable a LANE server and a LANE broadcast-and-unknown server for the first emulated LAN. | lane server-bus ethernet elan-name1 |
| Step 3 (Optional) Enable a LANE client for the first emulated LAN. | lane client ethernet [elan-name1] |
| Step 4 Provide a protocol address for the client. | protocol address mask1 |
If the emulated LAN in Step 3 is intended to have restricted membership, consider carefully whether you want to specify its name here. You will specify the name in the LANE configuration server's database when it is set up. However, if you link the client to an emulated LAN in this step, and through some mistake it does not match the database entry linking the client to an emulated LAN, this client will not be allowed to join this emulated LAN or any other. You might consider that to be either a nice check that the configuration is correct or a problem to overcome.
If you do decide to include the name of the emulated LAN linked to the client in Step 3 and later want to associate that client with a different emulated LAN, make the change in the configuration server's database before you make the change for the client on this subinterface.
Each emulated LAN is a separate subnetwork. In Step 4 make sure that the clients of the same emulated LAN are assigned protocol addresses on the same subnetwork and that clients of different emulated LANs are assigned protocol addresses on different subnetworks.
On any given router, you can set up one client for one emulated LAN or multiple clients for multiple emulated LANs. You can set up a client for a given emulated LAN on any routers you choose to participate in that emulated LAN. Any router with clients for multiple emulated LANs can route packets between those emulated LANs.
You must first set up the signaling and ILMI PVCs on the major ATM interface, as described earlier in the "Set up the Signaling and ILMI PVCs" section before you set up the client.
To set up only a client for an emulated LANs, perform the following steps beginning in interface configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify the subinterface for an emulated LAN on this router. | interface atm slot/port.subinterface-number |
| Step 2 Provide a protocol address for the client on this subinterface. | protocol address mask1 |
| Step 3 Enable a LANE client for the first emulated LAN. | lane client ethernet elan-name1 |
Each emulated LAN is a separate subnetwork. In Step 2, make sure that the clients of the same emulated LAN are assigned protocol addresses on the same subnetwork and that clients of different emulated LANs are assigned protocol addresses on different subnetworks.
Once you have set up the server, broadcast-and-unknown server, and clients as needed on the subinterfaces of an ATM interface on a router, you can display their ATM addresses by completing the following step in EXEC mode:
| Task | Command |
|---|---|
| Display the server, broadcast-and-unknown server, and client ATM addresses. | show lane |
The output of this command shows all subinterfaces configured for LANE. For each subinterface, the command displays and clearly labels the ATM addresses that belong to the server, the broadcast-and-unknown server, and the client.
When you look at each ATM address, you will notice that the prefix is the one you set up on the switch, the ESI field reflects the base address of the pool of MAC addresses assigned to the ATM interface plus a value that represents the specific LANE component, and the Selector byte is the same number as the subinterface. This automatic assignment of ATM address values was explained in the "Cisco's Method of Automatically Assigning ATM Addresses" section earlier in this chapter.
Repeat this step on each router before you proceed to set up the servers and clients on the next router.
Print the display or make a note on your LANE worksheet of these ATM addresses so you can use it when you set up the configuration server's database.
At this time, the clients are not operational. That is normal for this stage of LANE configuration.
After you have set up all the servers, broadcast-and-unknown servers, and clients on all the ATM subinterfaces on all routers that will participate in LANE and displayed their ATM addresses, you can use the information to populate the configuration server's database.
You can set up a default emulated LAN, no matter whether you set up any other emulated LANs. You can also set up some emulated LANs with restricted membership and others with unrestricted membership.
To set up the database, complete the steps in the following sections as appropriate for your emulated LAN plan and scenario:
If you have already set up the signaling and ILMI PVCs on this interface, skip to the next section.
You must set up the signaling PVC and the PVC that will communicate with the ILMI on the major ATM interface of any router that will participate in LANE.
Complete this task only once for a major interface. You do not need repeat this task on the same interface even though you might configure LANE servers and clients on several of its subinterfaces.
To set up these PVCs, complete the following tasks, beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify the major ATM interface and enter interface configuration mode. | interface atm slot/port |
| Step 2 Set up the signaling PVC that sets up and tears down SVCs; the vpi and vci values are usually set to 0 and 5, respectively. | atm pvc vcd vpi vci qsaal1 |
| Step 3 Set up a PVC to communicate with the ILMI; the vpi and vci values are usually set to 0 and 16, respectively. | atm pvc vcd vpi vci ilmi1 |
When you configure a router as the configuration server for one default emulated LAN, you provide a name for the database, the ATM address of the server for the emulated LAN, and a default name for the emulated LAN. In addition, you indicate that the configuration server's ATM address is to be computed automatically.
When you set up a database of only a default, unrestricted emulated LAN, you do not have to specify where the LANE clients are located. That is, when you set up the configuration server's database for a single default emulated LAN, you do not have to provide any database entries that link the ATM addresses of any clients with the emulated LAN name.
To set up the configuration server for the default emulated LAN, complete the following steps beginning in global configuration mode:
In Step 2, enter the ATM address of the server for the specified emulated LAN, as noted in your worksheet.
If you are setting up only a default emulated LAN, the elan-name value in Step 2 is the same as the default emulated LAN name you provide in Step 3.
When you set up a database for unrestricted emulated LANs, you create database entries that link the name of each emulated LAN to the ATM address of its server.
However, you may choose not to specify where the LANE clients are located. That is, when you set up the configuration server's database, you do not have provide any database entries that link the ATM addresses or MAC addresses of any clients with the emulated LAN name.
To configure a router as the configuration server for multiple emulated LANs with unrestricted membership, complete the following steps beginning in global configuration mode:
In Steps 2 and 3, enter the ATM address of the server for the specified emulated LAN, as noted in your worksheet.
When you set up the database for restricted-membership emulated LANs, you create database entries that link the name of each emulated LAN to the ATM address of its server.
However, you also must specify where the LANE clients are located. That is, for each restricted-membership emulated LAN, you provide a database entry that explicitly links the ATM address or MAC address of each client of that emulated LAN with the name of that emulated LAN.
Those client database entries specify the clients that are allowed to join the emulated LAN. When a client requests that the configuration server indicate which emulated LAN it is to join, the configuration server consults its database and then responds as configured.
When clients for the same restricted-membership emulated LAN are located in multiple routers, each client's ATM address or MAC address must be linked explicitly with the name of the emulated LAN. As a result, you must configure as many client entries (at Step 5, in the following procedure) as you have clients for emulated LANs in all the routers. Of course, each client will have a different ATM address in the database entries.
To set up the configuration server for emulated LANs with restricted membership, perform the following tasks beginning in global configuration mode:
Once you have created the database entries as appropriate to the type and the membership conditions of the emulated LANs, you can enable the configuration server on the selected ATM interface and router, and then display its ATM address by completing the following tasks:
| Task | Command |
|---|---|
| Step 1 If you are not currently configuring the interface, specify the major ATM interface where the configuration server is located. | interface atm slot/port |
| Step 2 Link the configuration server's database name to the specified major interface and enable the configuration server. | lane config database-name |
| Step 3 Specify that the configuration server's ATM address will be computed by our automatic method. | lane auto-config-atm-address |
| Step 4 Exit interface configuration mode. | exit |
| Step 5 Return to EXEC mode. | Ctrl-Z |
| Step 6 Display the configuration server's ATM address. | show lane config |
Make a note of the configuration server's ATM address so you can configure it on each ATM subinterface where a server and broadcast-and-unknown server is configured.
You must enter the configuration server's ATM address into the LightStream 100 ATM switch and save it permanently, so that the value will be not lost when the switch is reset or powered off.
To enter the configuration server's ATM address into the LightStream 100 switch and save it there permanently, complete the following steps on the LightStream 100 switch:
| Task | Command |
|---|---|
| Step 1 Specify the LANE configuration server's ATM address. | set configserver atm-address 1 |
| Step 2 Save the configuration value permanently. | save |
In Step 1, you must specify the full 40-digit ATM address.
After configuring LANE components on an interface or any of its subinterfaces, on a specified subinterface, or on an emulated LAN, you can display their status. To show LANE information, perform the following tasks in EXEC mode:
The examples in the following sections illustrate how to configure LANE for the following cases:
All examples use the automatic ATM address assignment method described in the "Cisco's Method of Automatically Assigning ATM Addresses" section earlier in this chapter.
These examples show the resulting configuration, not the process of determining the ATM addresses and entering them appropriately, as described in this chapter.
The following example configures four Cisco 7000 routers for one emulated LAN. Router 1 contains the configuration server, the server, the broadcast-and-unknown server, and a client. The remaining routers each contain a client for the emulated LAN. This example accepts all default settings that are provided. For example, it does not explicitly set ATM addresses for the different LANE components that are co-located on the router. Membership in this LAN is not restricted.
lane database example1 name eng server-atm-address 39.0000014155551211.0800.200c.1001.01 default-name eng interface atm 1/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi lane auto-config-atm-address lane config example1 interface atm 1/0.1 ip address 172.16.0.1 lane server-bus ethernet eng lane client ethernet
interface atm 1/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi interface atm 1/0.1 ip address 172.16.0.3 lane client ethernet
interface atm 2/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi interface atm 2/0.1 ip address 172.16.0.4 lane client ethernet
interface atm 1/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi interface atm 1/0.3 ip address 172.16.0.5 lane client ethernet
The following example configures the Cisco 7000 router for three emulated LANS for Engineering, Manufacturing, and Marketing, as illustrated in Figure 11-3. This example does not restrict membership in the emulated LANs.
In this example, shown in Figure 11-3, Router 1 has the following LANE components:
Router 2 has the following LANE components:
Router 3 has the following LANE components:
Router 4 has the following LANE components:
For the purposes of this example, the four routers are assigned the following ATM address prefixes and base ESI (the ESI part of the ATM address is derived from the first MAC address of the AIP shown in the example):
| Router | ATM Address Prefix | ESI Base |
|---|---|---|
| Router 1 | 39.0000014155551211 | 0800.200c.1000 |
| Router 2 | 39.0000014155551211 | 0800.200c.2000 |
| Router 3 | 39.0000014155551211 | 0800.200c.3000 |
| Router 4 | 39.0000014155551211 | 0800.200c.4000 |
Router 1 has the configuration server and its database, the server and broadcast-and-unknown server for the Manufacturing emulated LAN, and the server and broadcast-and-unknown server for the Engineering emulated LAN, a client for Manufacturing, and a client for Engineering. Router 1 is configured as follows:
!The following lines name and configure the configuration server's database. lane database example2 name eng server-atm-address 39.0000014155551211.0800.200c.1001.02 name man server-atm-address 39.0000014155551211.0800.200c.1001.01 name mkt server-atm-address 39.0000014155551211.0800.200c.4001.01 default-name man ! ! The following lines bring up the configuration server and associate ! it with a database name. interface atm 1/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi lane auto-config-atm-address lane config example2 ! ! The following 3 lines configure the "man" server, broadcast-and-unknown server, ! and the client on atm subinterface 1/0.1. The client is assigned to the default ! emulated lan. interface atm 1/0.1 ip address 172.16.0.1 255.255.255.0 lane server-bus ethernet man lane client ethernet ! ! The following 3 lines configure the "eng" server, broadcast-and-unknown server, ! and the client on atm subinterface 1/0.2. The client is assigned to the ! engineering emulated lan. Each emulated LAN is a different subnetwork, so the "eng" ! client has an IP address on a different subnetwork that the "man" client. interface atm 1/0.2 ip address 172.16.1.1 255.255.255.0 lane server-bus ethernet eng lane client ethernet eng
Router 2 is configured for a client of the Manufacturing emulated LAN and a client of the Engineering emulated LAN. Because the default emulated LAN name is man, the first client is linked to that emulated LAN name by default.
interface atm 1/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi interface atm 1/0.1 ip address 172.16.0.2 255.255.255.0 lane client ethernet interface atm 1/0.2 ip address 172.16.1.2 255.255.255.0 lane client ethernet eng
Router 3 is configured for a client of the Manufacturing emulated LAN and a client of the Marketing emulated LAN. Because the default emulated LAN name is man, the first client is linked to that emulated LAN name by default.
interface atm 2/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi interface atm 2/0.1 ip address 172.16.0.3 255.255.255.0 lane client ethernet interface atm 2/0.2 ip address 172.16.2.3 255.255.255.0 lane client ethernet mkt
Router 4 is has the server and broadcast-and-unknown server for the Marketing emulated LAN, a client for Marketing, and a client for Manufacturing. Because the default emulated LAN name is man, the second client is linked to that emulated LAN name by default. Router 4 is configured as follows:
interface atm 3/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi interface atm 3/0.1 ip address 172.16.2.4 255.255.255.0 lane les-bus ethernet mkt lane client ethernet mkt interface atm 3/0.2 ip address 172.16.0.4 255.255.255.0 lane client ethernet
The following example, illustrated in Figure 11-4, configures the Cisco 7000 router for three emulated LANS for engineering, manufacturing, and marketing.
The same components are assigned to the four routers as in the previous example. The ATM address prefixes and MAC addresses are also the same as in the previous example.
However, this example restricts membership in the emulated LANs. In this example, the LANE configuration server's database has explicit entries binding the ATM addresses of LANE clients to specified, named emulated LANs. In such cases, the client asks the configuration which emulated LAN it belongs to; the configuration server checks its database and informs the client which emulated LAN it belongs to.
Router 1 has the configuration server and its database, the server and broadcast-and-unknown server for the Manufacturing emulated LAN, and the server and broadcast-and-unknown server for the Engineering emulated LAN, and a client for Manufacturing, and a client for Engineering. It also has explicit database entries binding the ATM addresses of LANE clients to specified, named emulated LANs. Router 1 is configured as follows:
! The following lines name and configure the configuration server's database. lane database example3 name eng server-atm-address 39.0000014155551211.0800.200c.1001.02 restricted name man server-atm-address 39.0000014155551211.0800.200c.1001.01 name mkt server-atm-address 39.0000014155551211.0800.200c.4001.01 restricted default-name man ! ! The following lines add database entries binding specified client ATM ! addresses to emulated LANs. In each case, the Selector byte corresponds ! to the subinterface number on the specified router. ! The next command binds the client on Router 1's subinterface 2 to the eng ELAN. client-atm-address 39.0000014155551211.0800.200c.1000.02 name eng ! The next command binds the client on Router 2's subinterface 2 to the eng ELAN. client-atm-address 39.0000014155551211.0800.200c.2000.02 name eng ! The next command binds the client on Router 3's subinterface 2 to the mkt ELAN. client-atm-address 39.0000014155551211.0800.200c.3000.02 name mkt ! The next command binds the client on Router 4's subinterface 1 to the mkt ELAN. client-atm-address 39.0000014155551211.0800.200c.4000.01 name mkt ! ! The following two lines bring up the configuration server and associate ! it with a database name. interface atm 1/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi lane auto-config-atm-address lane config example3 ! ! The following 3 lines configure the "man" server/broadcast-and-unknown server, ! and the client on atm subinterface 1/0.1. The client is assigned to the default ! emulated lan. interface atm 1/0.1 ip address 172.16.0.1 255.255.255.0 lane server-bus ethernet man lane client ethernet ! ! The following 3 lines configure the "eng" server/broadcast-and-unknown server ! and the client on atm subinterface 1/0.2. The configuration server assigns the ! client to the engineering emulated lan. interface atm 1/0.2 ip address 172.16.1.1 255.255.255.0 lane server-bus ethernet eng lane client ethernet
Router 2 is configured for a client of the Manufacturing emulated LAN and a client of the Engineering emulated LAN. Because the default emulated LAN name is man, the first client is linked to that emulated LAN name by default.
interface atm 1/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi ! This client is not in the configuration server's database, so it will be ! linked to the "man" ELAN by default. interface atm 1/0.1 ip address 172.16.0.2 255.255.255.0 lane client ethernet ! A client for the following interface is entered in the configuration ! server's database as linked to the "eng" ELAN. interface atm 1/0.2 ip address 172.16.1.2 255.255.255.0 lane client ethernet
Router 3 is configured for a client of the Manufacturing emulated LAN and a client of the Marketing emulated LAN. Because the default emulated LAN name is man, the first client is linked to that emulated LAN name by default. The second client is listed in the database as linked to the mkt emulated LAN.
interface atm 2/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi ! The first client is not entered in the database, so it is linked to the ! "man" ELAN by default. interface atm 2/0.1 ip address 172.16.0.3 255.255.255.0 lane client ethernet ! The second client is explicitly entered in the configuration server's ! database as linked to the "mkt" ELAN. interface atm 2/0.2 ip address 172.16.2.3 255.255.255.0 lane client ethernet
Router 4 is has the server and broadcast-and-unknown server for the Marketing emulated LAN, a client for Marketing, and a client for Manufacturing. The first client is listed in the database as linked to the mkt emulated LANs. The second client is not listed in the database, but is linked to the man emulated LAN name by default. Router 4 is configured as follows:
interface atm 3/0 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi ! The first client is explicitly entered in the configuration server's ! database as linked to the "mkt" ELAN. interface atm 3/0.1 ip address 172.16.2.4 255.255.255.0 lane les-bus ethernet mkt lane client ethernet ! The following client is not entered in the database, so it is linked to the ! "man" ELAN by default. interface atm 3/0.2 ip address 172.16.0.4 255.255.255.0 lane client ethernet
|
|