|
|
This chapter describes how to configure LAN emulation (LANE) in Cisco 7500, Cisco 7000, and Cisco 4500 series routers containing an ATM Interface Processor (AIP) and connected to a LightStream 100 ATM switch (formerly known as the Cisco HyperSwitch A100 switch) or LightStream 1010 ATM 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 (LANE) Commands" chapter of the Wide-Area Networking Command Reference.
The following sections contain information relevant to implementation:
In this release, Cisco supports the following networking features:
This release of LANE is supported on Cisco 7500 and Cisco 7000 routers contain an ATM Interface Processor (AIP); it requires a Cisco LightStream 100 workgroup ATM switch or a Cisco LightStream 1010 ATM switch.
Cisco's AIP provides a single ATM network interface for the Cisco 7000 family of routers. Network interfaces 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 Transparent Asynchronous Transmitter/Receiver Interface (TAXI) interfaces, or one Synchronous Optical Network (SONET) and one E3, or one SONET and one lightly used SONET, or five E3s.
For a complete description of the Cisco 7000 router and AIP, refer to the Cisco 7000 Hardware Installation and Maintenance.
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. It consists of the following:
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 7500 series, Cisco 7000 series, and Cisco 4500 series 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 is 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 for address templates of 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 Interim Local Management Interface (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:
Before you begin to configure LANE, you must decide whether you want to set up one or multiple emulated LANs. If you set up multiple emulated LANs, you must also decide where the servers and clients will be located, and whether to restrict the clients that can belong to each emulated LAN. Bridged emulated LANs are configured just like any other LAN, in terms of commands and outputs. 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 or Cisco 4500 routers, you must configure the Cisco LightStream 100 switch of Cisco LightStream 1010 ATM 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 tasks 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 |
To set the ATM address prefix on the Cisco LightStream 1010, complete the following tasks on the Cisco switch, starting in global configuration mode:
You can display the current prefix by using the show network command.
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 participates in LANE.
Complete this task only once for a major interface. You do not need to 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 steps, beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify the major ATM interface and enter interface configuration mode. | interface atm slot/port1 (for the Cisco 7000) or interface atm number1 (for the Cisco 4500) |
| 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 qsaal2 |
| 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 ilmi2 |
You can display the LANE default addresses to make configuration easier. Complete this task for each router that participates in LANE. This command will display default addresses for all ATM interfaces present on the router. Write down the displayed addresses on your worksheet.
To display the default LANE addresses, complete the following step, beginning in global configuration mode:
| Task | Command |
|---|---|
| Display the LANE default addresses. | show lane default atm addresses |
You must enter the configuration server's ATM address into the LightStream 100 ATM switch or LightStream 1010 ATM swithc and save it permanently, so that the value will be not lost when the switch is reset or powered off.
You must specify the full 40-digit ATM address. Use the addresses on your worksheet that you obtained from the previous task.
Depending on which type of switch you are using, perform one of the following tasks:
On the Cisco LightStream 1010 ATM switch, the configuration server address can be specified for a port or for the entire switch.
To enter the configuration server addresses on the Cisco LightStream 1010 ATM switch for the entire switch, perform the following tasks, beginning in global configuration mode:
To enter the configuration server addresses on the Cisco LightStream 1010 ATM switch per port, perform the following tasks, beginning in interface configuration mode:
To enter the configuration server's ATM address into the Cisco LightStream 100 ATM switch and save it there permanently, perform the following tasks in privileged command mode:
| Task | Command |
|---|---|
| Step 1 Specify the LANE configuration server's ATM address. | set configserver atm-address |
| Step 2 Save the configuration value permanently. | save |
After you have set up all servers, broadcast-and-unknown servers, and clients on all ATM subinterfaces on all routers that will participate in LANE, and have displayed their ATM addresses, you can use the information to populate the configuration server's database.
You can set up a default emulated LAN, whether or not 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 tasks in the following sections as appropriate for your emulated LAN plan and scenario:
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:
| Task | Commands |
|---|---|
| Step 1 Create a named database for the LANE configuration server | lane database database-name |
| Step 2 In the configuration database, bind the name of the emulated LAN to the ATM address of the LANE server. | name elan-name server-atm-address atm-address |
| Step 3 In the configuration database, provide a default name for the emulated LAN. | default-name elan-name |
| Step 4 Exit from database configuration mode and return to global configuration mode. | exit1 |
In Step 2, enter the ATM address of the server for the specified emulated LAN, as noted in your worksheet and obtained in the "Display LANE Default Addresses" section.
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:
| Task | Command |
|---|---|
| Step 1 Create a named database for the LANE configuration server. | lane database database-name |
| Step 2 In the configuration database, bind the name of the first emulated LAN to the ATM address of the LANE server for that emulated LAN. | name elan-name1 server-atm-address atm-address |
| Step 3 In the configuration database, bind the name of the second emulated LAN to the ATM address of the LANE server.
Repeat this step, providing a different emulated LAN name and an ATM address, for each additional emulated LAN in this switch cloud. | name elan-name2 server-atm-address atm-address |
| Step 4 (Optional) Specify a default emulated LAN for LANE clients not explicitly bound to an emulated LAN. | default name elan-name1 |
| Step 5 Exit from database configuration mode and return to global configuration mode. | exit1 |
In Steps 2 and 3, enter the ATM address of the server for the specified emulated LAN, as noted in your worksheet and obtained in the "Display LANE Default Addresses" section.
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. 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 steps 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 by completing the following steps:
| 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/port1 (for the Cisco 7000) or interface atm number1 (for the Cisco 4500) |
| 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. | exit1 |
| Step 5 Return to EXEC mode. | Ctrl-Z |
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.
Where you put the clients is important, 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 (optionally) clients 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-number1 (for the Cisco 7000) or interface atm number...2 (for the Cisco 4500) |
| 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 mask2 |
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-number1 (for the Cisco 7000) or interface atm number...1 (for the Cisco 4500) |
| 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.
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 steps 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 that was described earlier 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 32. This example does not restrict membership in the emulated LANs.
In this example, shown in Figure 32, 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, 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 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 33, 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 requests information from the configuration server about 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, the server and broadcast-and-unknown server for the Engineering emulated LAN, 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 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
|
|