|
|
This chapter provides a full description of the commands presented in Chapter 1, including command syntax and usage guidelines. Commands are presented in alphabetical order.
To define the action for access checks that apply to zones, use the access-list
additional-zones global configuration command.
access-list-number | Number of the access list. This is a decimal number from 600 to 699. |
deny | Denies access if the conditions are matched. |
permit | Permits access if the conditions are matched. |
To deny access
Global configuration
The access-list additional-zones command defines the action to take for access checks not explicitly defined with the access-list zone command. If you do not specify this command, the default action is to deny access.
The following example creates an access list based on AppleTalk zones:
access-list 610 deny zone Twilight
access-list 610 permit additional-zones
access-list cable-range
access-list includes
access-list network
access-list other-access
access-list within
access-list zones
To define an AppleTalk access list for a cable range (for extended networks only), use the access-list cable-range global configuration command. To remove an access list, use the no form of this command.
access-list access-list-number {deny | permit} cable-range cable-range
access-list-number | Number of the access list. This is a decimal number from 600 to 699. |
deny | Denies access if the conditions are matched. |
permit | Permits access if the conditions are matched. |
cable-range | Cable range value. The argument specifies the start and end of the cable range, separated by a hyphen. These values are decimal numbers from 1 to 65279. The starting network number must be less than or equal to the ending network number. |
There is no AppleTalk access list defined by default for a cable range.
Global configuration
The access-list cable-range command affects matching on extended networks only. The conditions defined by this access list are used only when the packet's cable range exactly matches the cable range specified in the access-list network command. The conditions are never used to match a network number (for a nonextended network) even if the cable range has the same starting and ending number as the nonextended network number.
To delete an access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-numberTo delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} cable-range cable-rangeThe access list created by the following commands allows all packets to be forwarded except those destined to cable range 10 to 20:
access-list 600 deny cable-range 10-20
access-list 600 permit other-access
access-list additional-zones
access-list includes
access-list network
access-list other-access
access-list within
access-list zone
To define an AppleTalk access list that overlaps any part of a range of network numbers or cable ranges (for both extended and nonextended networks), use the access-list includes global configuration command. To remove an access list, use the no form of this command.
access-list access-list-number {deny | permit} includes cable-range
access-list-number | Number of the access list. This is a decimal number from 600 to 699. |
deny | Denies access if the conditions are matched. |
permit | Permits access if the conditions are matched. |
cable-range | Cable range or network number. The argument specifies the start and end of the cable range, separated by a hyphen. These values are decimal numbers from 1 to 65279. The starting network number must be less than or equal to the ending network number. To specify a network number, set the starting and ending network numbers to the same value. |
There is no AppleTalk access list defined by default that overlaps any part of a range of network numbers or cable ranges.
Global configuration
The access-list includes command affects matching on extended and nonextended AppleTalk networks. The conditions defined by this access list are used when the packet's cable range or network number overlaps, either partially or completely, one (or more) of those specified in the access-list network command.
To delete an access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-numberTo delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} includes cable-rangeThe following example defines an access list that permits access to packets destined to any nonextended or extended network whose network number or cable range overlaps any part of the range 10 to 20. This means, for example, that packets whose cable ranges are 13 to 16 and 17 to 25 will be forwarded. This access list also allows all other packets to be forwarded.
access-list 600 permit includes 10-20
access-list 600 permit other-access
access-list additional-zones
access-list cable-range
access-list network
access-list other-access
access-list within
access-list zone
To define an AppleTalk access list for a single network number (that is, for a nonextended network), use the access-list network global configuration command. To remove an access list, use the no form of this command.
access-list access-list-number {deny | permit} network network
access-list-number | Number of the access list. This is a decimal number from 600 to 699. |
deny | Denies access if the conditions are matched. |
permit | Permits access if the conditions are matched. |
network | AppleTalk network number. |
There is no AppleTalk access list for a single network number defined by default.
Global configuration
The access-list network command affects matching on nonextended networks only. The conditions defined by this access list are used only when the packet's network number matches a network number specified in one of the access-list network commands. The conditions are never used to match a cable range (for an extended network) even if the cable range has the same starting and ending number.
To delete an access list, specify the minimum number of keywords and arguments needed to delete the desired access list. For example, to delete an entire access list, use the following command:
no access-list access-list-numberTo delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} network networkThe following example defines an access list that forwards all packets except those destined for networks 1 and 2:
access-list 650 deny network 1
access-list 650 deny network 2
access-list 650 permit other-access
access-list additional-zones
access-list cable-range
access-list includes
access-list other-access
access-list within
access-list zone
To define the action to take for access checks that apply to networks or cable ranges, use the
access-list other-access global configuration command.
access-list-number | Number of the access list. This is a decimal number from 600 to 699. |
deny | Denies access if the conditions are matched. |
permit | Permits access if the conditions are matched. |
To deny other access
Global configuration
The access-list other-access command defines the action to take for access checks not explicitly defined with an access-list network, access-list cable-range, access-list includes, or access-list within command. If you do not specify this command, the default action is to deny other access.
The following example defines an access list that forwards all packets except those destined for networks 1 and 2:
access-list 650 deny network 1
access-list 650 deny network 2
access-list 650 permit other-access
access-list additional-zones
access-list cable-range
access-list includes
access-list network
access-list within
access-list zone
To define an AppleTalk access list for an extended or a nonextended network whose network number or cable range is included entirely within the specified cable range, use the access-list within global configuration command. To remove this access list, use the no form of this command.
access-list access-list-number {deny | permit} within cable-range
access-list-number | Number of the access list. This is a decimal number from 600 to 699. |
deny | Denies access if the conditions are matched. |
permit | Permits access if the conditions are matched. |
cable-range | Cable range or network number. The argument specifies the start and end of the cable range, separated by a hyphen. These arguments are decimal numbers from 1 to 65279. The starting network number must be less than or equal to the ending network number. To specify a network number, set the starting and ending network numbers to the same value. |
There is no AppleTalk access list defined by default for an extended or a nonextended network whose network number or cable range is included entirely within the specified cable range.
Global configuration
The access-list within command affects matching on extended and nonextended AppleTalk networks. The conditions defined by this access list are used when the packet's cable range or network number is completely included in one (or more) of those specified in the access-list network command.
To delete an access list, specify the minimum number of keywords and arguments needed to delete the desired access list. For example, to delete the entire access list, use the following command:
no access-list access-list-numberTo delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} within cable-rangeThe following example defines an access list that permits access to packets destined to any nonextended or extended network whose network number or cable range is completely included in the range 10 to 20. This means, for example, that packets whose cable range is 13 to 16 will be forwarded, but those whose cable range is 17 to 25 will not be forwarded. The second line of the example causes all other packets to be forwarded.
access-list 600 permit within 10-20
access-list 600 permit other-access
access-list additional-zones
access-list cable-range
access-list includes
access-list network
access-list other-access
access-list zone
To define an AppleTalk access list that applies to a zone, use the access-list zone global configuration command. To remove an access list, use the no form of this command.
access-list access-list-number {deny | permit} zone zone-name
access-list-number | Number of the access list. This is a decimal number from 600 to 699. |
deny | Denies access if the conditions are matched. |
permit | Permits access if the conditions are matched. |
zone-name | Name of the zone. The name can include special characters from the Apple Macintosh character set. To include a special character, type a colon followed by two hexadecimal numbers. The zone name cannot have leading or trailing space characters. |
There is no AppleTalk access list applied to a zone by default.
Global configuration
To delete an access list, specify the minimum number of keywords and arguments needed to delete the proper access list. For example, to delete the entire access list, use the following command:
no access-list access-list-numberTo delete the access list for a specific network, use the following command:
no access-list access-list-number {deny | permit} zone zone-nameUse the access-list additional-zones command to define the action to take for access checks not explicitly defined with the access-list zone command.
The following example creates an access list based on AppleTalk zones:
access-list 610 deny zone Twilight
access-list 610 permit additional-zones
access-list additional-zones
access-list cable-range
access-list includes
access-list network
access-list other-access
access-list within
To enable nonextended AppleTalk on an interface, use the appletalk address interface configuration command. To disable nonextended AppleTalk, use the no form of this command.
appletalk address network.node
network.node | AppleTalk network address assigned to the interface. The argument network is the 16-bit network number in the range 0 to 65280. The argument node is the 8-bit node number in the range 0 to 254. Both numbers are decimal. |
Disabled
Interface configuration
You must enable AppleTalk on the interface before assigning zone names.
Specifying an address of 0.0, 0.node, or network.0 puts the interface into discovery mode. When in this mode, the communication server attempts to determine network address information from another communication server or router on the network. You can also enable discovery mode with the appletalk discovery command. Note that discovery mode does not run over synchronous serial lines.
The following example enables nonextended AppleTalk on Ethernet interface 0:
appletalk service
interface ether 0
appletalk address 1.129
appletalk cable-range
appletalk discovery
appletalk zone
To assign a range of networks to a cable, use the appletalk cable-range interface configuration command. Use the no form of this command to disable a cable-range setting.
appletalk cable-range cable-range [network.node]
cable-range | Cable range or network number. The argument specifies the start and end of the cable range, separated by a hyphen. These arguments are decimal numbers from 1 to 65279. The starting network number must be less than or equal to the ending network number. |
network.node | (Optional.) Suggested AppleTalk address for the interface. The argument network is the 16-bit network number, and the argument node is the 8-bit node number. Both numbers are decimal. The suggested network number must fall within the specified range of network numbers. |
Disabled
Interface configuration
The communication server needs both a valid cable range and a zone list to use AppleTalk. This command must be entered before the appletalk zone command.
Whenever you change the cable range, the communication server clears the internal zone list and you must enter a new zone list.
Configure the communication server for discovery mode if you want to find out what the current cable range is. To configure the communication server for discovery mode, use the appletalk cable-range 0-0 0.0 command. This causes the communication server to learn about the AppleTalk network. After saving the command in your configuration file, log back in and enable configuration mode. When you display the configuration, will see the AppleTalk cable range and the AppleTalk zone variables. Then, add those two entries to the configuration and save the configuration file.
The following example shows how to use discovery mode:
appletalk service
interface ether 0
appletalk cable-range 0-0 0.0
line 5 6
modem inout
speed 38400
arap enabled
autoselect
After you learn the cable range values, add them to the configuration file. For example:
appletalk cable-range 105-105 105.222
appletalk zone Marketing
username arauser password arapasswd
The following example assigns a cable range of 2-2 to the interface:
interface async 1
appletalk cable-range 2-2
appletalk address
appletalk service
appletalk zone
To enable the generation and verification of checksums for all AppleTalk packets, use the appletalk checksum global configuration command. To disable checksum generation and verification, use the no form of this command.
appletalk checksumThis command has no arguments or keywords.
Enabled
Global configuration
When the appletalk checksum command is enabled, the communication server discards incoming DDP packets when the checksum is nonzero and is incorrect and when the communication server is the final destination for the packet.
You might want to disable checksum generation and verification if you have older LaserWriter printers or other devices that cannot receive packets that contain checksums.
The following example disables the generation and verification of checksums:
no appletalk checksum
To put an interface into discovery mode, use the appletalk discovery interface configuration command. To disable discovery mode, use the no form of this command.
appletalk discoveryThis command has no arguments or keywords.
Disabled
Interface configuration
If an interface is connected to a network that has at least one other operational AppleTalk communication server or router, you can dynamically configure the interface using discovery mode. In discovery mode, an interface acquires network address information about the attached network from an operational communication server or router and then uses this information to configure itself.
If you enable discovery mode on an interface, that interface must configure itself by acquiring information from another operational communication server or router on the attached network when the communication server is starting up that interface. If no operational communication server or router is present on the connected network, the interface will not start up.
If you do not enable discovery mode, the interface must acquire its configuration from memory when the communication server is starting up. If the stored configuration is not complete, the interface will not start up. If there is another operational communication server on the connected network, the communication server will verify the stored interface configuration with that communication server. If there is any discrepancy, the interface will not start up. If there are no neighboring operational communication servers, the communication server will assume the stored interface configuration is correct and will start up.
Once an interface is operational, it can seed the configurations of other communication servers on the connected network regardless of whether you have enabled discovery mode on any of the communication servers.
If you enable appletalk discovery and the interface is restarted, you must have another operational communication server or router on the directly connected network or the interface will not start up.
It is not advisable to have all communication servers and routers on a network configured with discovery mode enabled. If all communication servers were to restart simultaneously (for instance, after a power failure), the network would become inaccessible until at least one communication server or router were restarted with discovery mode disabled.
You also can enable discovery mode by specifying an address of 0.0. in the appletalk address command or a cable range of 0-0 in the appletalk cable-range command.
Discovery mode is useful when you are changing a network configuration or when you are adding a communication server to an existing network.
Discovery mode does not run over synchronous serial lines.
Use the no appletalk discovery command to disable discovery mode and allow the interface to be a seed port. If the interface is not operational when you issue this command, you must configure the zone name before the interface will be operational. If you are reconfiguring an operational interface by issuing the no appletalk discovery command, the command will have no effect because the network configuration is already established.
The following example enables discovery mode on Ethernet interface 0:
interface ethernet 0
appletalk cable-range 0-0
appletalk discovery
appletalk address
appletalk cable-range
appletalk zone
show appletalk interface
To allocate IP addresses to dynamic MacIP clients, use the appletalk macip dynamic global configuration command. To delete a MacIP dynamic address assignment, use the no form of this command.
appletalk macip dynamic ip-address [ip-address] zone server-zone
ip-address | IP address, in four-part dotted decimal notation. To specify a range, enter two IP addresses, which represent the first and last addresses in the range. |
server-zone | Zone in which the MacIP server resides. The argument server-zone can include special characters from the Apple Macintosh character set. To include a special character, specify a colon followed by two hexadecimal numbers. For a list of Macintosh characters, refer to the Apple Computer, Inc. specification Inside AppleTalk. Zone names cannot have leading or trailing space characters. |
No IP addresses are allocated to dynamic MacIP clients.
Global configuration
Use the appletalk macip dynamic command when configuring MacIP.
Dynamic clients are those that accept any IP address assignment within the dynamic range specified.
In general, it is recommended that you do not use fragmented address ranges in configuring ranges for MacIP. However, if this is unavoidable, use the appletalk macip dynamic command to specify as many addresses or ranges as required and use the appletalk macip static command to assign a specific address or address range.
To shut down all running MacIP services, use the following command:
no appletalk macipTo delete a particular dynamic address assignment from the configuration, use the following command:
no appletalk macip dynamic ip-address [ip-address] zone server-zoneThe following example illustrates MacIP support for dynamically addressed MacIP clients with IP addresses in the range 131.108.1.28 to 131.108.1.44.
! This global statement specifies the MacIP server address and zone:
appletalk macip server 131.108.1.27 zone Engineering
!
! This global statement identifies the dynamically addressed clients:
appletalk macip dynamic 131.108.1.28 131.108.1.44 zone Engineering
!
! These statements assign the IP address and subnet mask for Ethernet
! interface 0:
interface ether 0
ip address 131.108.1.27 255.255.255.0
!
! This global statement enables AppleTalk on the communication server.
appletalk service
!
! These statements enable AppleTalk on the interface and
! set the zone name for the interface
interface ether 0
appletalk cable-range 69-69 69.128
appletalk zone Engineering
A dagger () indicates that the command is documented in the Communication Server Command Reference publication.
appletalk macip server
appletalk macip static
ip address
show appletalk macip-servers
To establish a MacIP server for a zone, use the appletalk macip server global configuration command. To shut down a MACIP server, use the no form of this command.
appletalk macip server ip-address zone server-zone
ip-address | IP address, in four-part dotted decimal notation. It is suggested that this address match the address of an existing IP interface. |
server-zone | Zone in which the MacIP server resides. The argument server-zone can include special characters from the Apple Macintosh character set. To include a special character, specify a colon followed by two hexadecimal numbers. For a list of Macintosh characters, refer to the Apple Computer, Inc. specification Inside AppleTalk. Zone names cannot have leading or trailing space characters. |
No MacIP servers are established for a zone.
Global configuration
Use the appletalk macip server command when configuring MacIP.
You can configure multiple MacIP servers for a communication server, but you can assign only one MacIP server to a particular zone and only one IP interface to each MacIP server. In general, you must be able to establish an alias between the IP address you assign with the appletalk macip server command and an existing IP interface. For implementation simplicity, it is suggested that the address specified in this command match an existing IP interface address.
A MacIP server is not registered using NBP until at least one MacIP resource is configured.
To shut down all active MacIP servers, use the following command:
no appletalk macipTo delete a specific MacIP server from the MacIP configuration, use the following command:
no appletalk macip server ip-address zone server-zoneThe following example establishes a MacIP server on Ethernet interface 0 in AppleTalk zone Engineering. It then assigns an IP address to the Ethernet interface and enables AppleTalk on the communication server and the Ethernet interface.
appletalk macip server 131.108.1.27 zone Engineering
ip address 131.108.1.27 255.255.255.0
appletalk service
interface ether 0
appletalk cable-range 69-69 69.128
appletalk zone Engineering
A dagger () indicates that the command is documented in the Communication Server Command Reference publication.
appletalk macip dynamic
appletalk macip static
ip address
show appletalk macip-servers
To allocate an IP address to be used by a MacIP client that has reserved a static IP address, use the appletalk macip static global configuration command. To delete a MacIP static address assignment, use the no form of this command.
appletalk macip static ip-address [ip-address] zone server-zone
ip-address | IP address, in four-part dotted decimal format. To specify a range, enter two IP addresses, which represent the first and last addresses in the range. |
server-zone | Zone in which the MacIP server resides. The argument server-zone can include special characters from the Apple Macintosh character set. To include a special character, specify a colon followed by two hexadecimal numbers. For a list of Macintosh characters, refer to the Apple Computer, Inc. specification Inside AppleTalk. Zone names cannot have leading or trailing space characters. |
No IP addresses are allocated.
Global configuration
Use the appletalk macip static command when configuring MacIP.
Static addresses are for users who require fixed addresses for IP name domain name service and for administrators who do want addresses to change so they can always know who has what IP address.
In general, it is recommended that you do not use fragmented address ranges in configuring ranges for MacIP. However, if this is unavoidable, use the appletalk macip dynamic command to specify as many addresses or ranges as required, and then use the appletalk macip static command to assign a specific address or address range.
To shut down all running MacIP services, use the following command:
no appletalk macipTo delete a particular static address assignment from the configuration, use the following command:
no appletalk macip static ip-address [ip-address] zone server-zoneThe following example illustrates MacIP support for MacIP clients with statically allocated IP addresses. The IP addresses range is from 131.108.1.50 to 131.108.1.66. The three nodes that have the specific addresses are 131.108.1.81, 131.108.1.92, and 131.108.1.101.
! This global statement specifies the MacIP server address and zone:
appletalk macip server 131.108.1.27 zone Engineering
!
! These global statements identify the statically addressed clients:
appletalk macip static 131.108.1.50 131.108.1.66 zone Engineering
appletalk macip static 131.108.1.81 zone Engineering
appletalk macip static 131.108.1.92 zone Engineering
appletalk macip static 131.108.1.101 zone Engineering
!
! These statements assign the IP address and subnet mask for Ethernet
! interface 0:
interface ether 0
ip address 131.108.1.27 255.255.255.0
!
! This global statement enables AppleTalk on the communication server.
appletalk service
!
! These statements enable AppleTalk on the interface and
! set the zone name for the interface
interface ethernet 0
appletalk cable-range 69-69 69.128
appletalk zone Engineering
A dagger () indicates that the command is documented in the Communication Server Command Reference publication.
appletalk macip dynamic
appletalk macip server
ip address
show appletalk macip-servers
This command has no arguments or keywords.
Disabled
Global configuration
The following example enables AppleTalk protocol processing on the communication server:
appletalk service
appletalk cable-range
appletalk zone
To set the zone name for the connected AppleTalk network, use the appletalk zone interface configuration command. To delete a zone, use the no form of this command.
appletalk zone zone-name
None
Interface configuration
The communication server needs both a valid cable range and zone list to use AppleTalk.
The appletalk cable-range command must be entered before the appletalk zone command.
The first zone specified in the list is the default zone.
The appletalk zone command accepts spaces in zone names. Do not use quotation marks in the command entry. When you have completed the entry, use the show configuration command to display the configuration file.
The no form of the command deletes a zone name from a zone list or, if you do not specify a zone name, it deletes the entire zone list. Before configuring a new zone list, delete any existing zone-name list using the no appletalk zone command.
The internal zone list is cleared automatically when you issue an appletalk cable-range command. The list is also cleared if you issue the appletalk zone command on an existing network.
AppleTalk communication servers maintain a complete list of zone names and associated network numbers. AppleTalk network protocols assume that the list of zones is stable as long as the associated networks remain reachable. The only way to make an old zone name disappear throughout your network is to cause the associated routes to disappear. If you change a zone name and keep the network numbers the same, you might need to wait for the next general power failure for parts of your network to acquire new zone lists and flush the old entry.
The following example assigns the zone name Twilight to an interface:
interface ether 0
appletalk cable-range 10-20
appletalk zone Twilight
The following example uses a colon and two hexadecimal numbers to specify a Macintosh special character in the zone name Cisco·Zone.
appletalk zone Cisco:A5Zone
A dagger () indicates that the command is documented in the Communication Server Command Reference publication.
appletalk cable-range
show appletalk zone
show configuration
To configure a line to be used only as an ARA connection, use the arap dedicated line configuration command. Use the no form of the command to return the line to interactive mode.
arap dedicatedThis command has no arguments or keywords.
Disabled
Line configuration
The following example configures line 3 to be used only for ARA connections:
line 3
arap dedicated
To enable ARA for a line, use the arap enable command. Use the no form of this command to disable ARA.
arap enableThis command has no arguments or keywords.
Disabled
Line configuration
The following example enables ARA on a line:
line 3
arap enable
autoselect
To control Macintosh access to networks, use the arap net-access-list line configuration command. Use the no form of this command to return to the default setting.
arap net-access-list net-access-list-number
net-access-list-number | One of the list values configured using the AppleTalk access-list cable-range, access-list includes, access-list network, access-list other-access, and access-list within, commands. |
Disabled. The Macintosh has access to all networks.
Line configuration
You can use the arap net-access-list command to apply access lists defined by the access-list cable-range, access-list includes, access-list network, access-list other-access, and access-list within commands.
You cannot use the arap net-access-list command to apply access lists defined by the access-list zone and access-list additional-zones commands.
In the following example, ARA is enabled on line 3 and the Macintosh will have access to the AppleTalk access list numbered 650.
line 3
arap enable
arap net-access-list 650
access-list cable-range
access-list includes
access-list network
access-list other-access
access-list within
arap zonelist
To prevent Macintosh guests from logging in to the communication server, use the arap noguest line configuration command. Use the no form of this command to remove this restriction.
arap noguestThis command has no arguments or keywords.
Disabled
Line configuration
A guest is a person who connects to the network without having to give a name or a password.
 | Caution Do not use the arap noguest command if TACACS is enabled. |
The following example prohibits guests from logging in to the communication server:
line 3
arap enable
arap noguest
minutes | (Optional.) Maximum length of time, in minutes, for a session. |
Unlimited session length
Line configuration
After the specified length of time, the session will be terminated.
The following example specifies a maximum length of 20 minutes for ARA sessions:
line 3
arap enable
arap timelimit 20
arap warningtime
minutes | (Optional.) Amount of time, in minutes, before the configured session time limit. At the configured amount of time before a session is to be disconnected, the communication server sends a message to the Macintosh client, which causes a warning message to appear on the user's screen. |
Disabled
Line configuration
This command can only be used if a session time limit has been configured on the line.
The following example shows a line configured for 20-minute ARA sessions, with a warning 17 minutes after the session is started:
line 3
arap enable
arap dedicated
arap timelimit 20
arap warningtime 3
arap timelimit
To control what zones the Macintosh client sees, use the arap zonelist line configuration command. Use the no form of this command to disable the default setting.
arap zonelist zone-access-list-number
zone-access-list-number | One of the list values configured using the AppleTalk access-list zone or access-list additional-zones commands. |
Disabled. The Macintosh will see all defined zones.
Line configuration
You can use the arap zonelist command to apply access lists defined by the access-list zone and access-list additional-zones command.
You cannot use the arap zonelist command to apply access lists defined by the access-list network command.
In the following example, ARA is enabled on line 3 and the Macintosh will see only zones permitted by access list 650.
line 3
arap enable
arap zonelist 650
access-list additional-zones
access-list zone
arap net-access-list
To configure a line to automatically start either an ARA session or an EXEC session, use the autoselect line configuration command. Use the no form of this command to disable this function on a line.
autoselectThis command has no arguments or keywords.
Disabled. Ignores any character other than 13, which starts an EXEC session.
Line configuration
This command eliminates the need for Macintosh users to enter an EXEC command to start an ARA session. The autoselect command configures the communication server to identify the type of connection being requested. In other words, when a user on a Macintosh running ARA presses the Connect button, the communication server automatically starts an ARA session. If, on the other hand, the user is running SLIP or PPP, the communication server starts an EXEC session that requires the user to enter the slip or ppp command to start a session. This command is used on lines used for making different types of connections.
The autoselect command is required on all lines configured with arap enabled, except for lines configured for arap dedicated or lines configured for TACACS logins. A line that does not have autoselect configured will see an attempt to open an ARA connection as noise and the communication server will not respond and the user client will time out.
| Caution Do not use the autoselect command if TACACS is enabled. |
Example
The following example enables ARA on a line:
line 3
arap enable
autoselect
internal | Debug internal ARA packets. |
memory | Debug memory allocation for ARA. |
mnp4 | Debug low-level asynchronous serial protocol. |
v42bis | Debug compression. |
Disabled
Privileged EXEC
The following example activates debugging internal ARA packets on line 3:
CS# debug arap internal
To configure your communication server to use TACACS user authentication, use the login tacacs line configuration command. The no form of this command disables TACACS user authentication for a line.
login tacacsThis command has no arguments or keywords.
Disabled
Line configuration
You can use TACACS security if you have configured a TACACS server and you have a CCL script that allows you to use TACACS security. See the "Configure TACACS Security" section in Chapter 1 for information about using files provided by Cisco to modify CCL scripts to support TACACS user authentication.
In the following example, lines 1 through 16 are configured for TACACS user authentication:
line 1 16
login tacacs
To display the entries in the AppleTalk Address Resolution Protocol (AARP) cache, use the show appletalk arp EXEC command.
show appletalk arpThis command has no arguments or keywords.
EXEC
AARP establishes associates between network addresses and hardware (MAC) addresses. This information is maintained in the communication server's AARP cache.
The following is sample output from the show appletalk arp privileged EXEC command:
CS# show appletalk arp
Address Age (min) Type Hardware Addr Encap Interface
2000.1 - Hardware 0000.0c04.1111 SNAP Ethernet1
Table 2-1 describes the fields shown in the display.
| Field | Description |
|---|---|
Address | AppleTalk network address of the interface. |
Age (min) | Time, in minutes, that this entry has been in the ARP table. Entries are purged after they have been in the table for 240 minutes (4 hours). A hyphen indicates that this is a new entry. |
Type | Indicates how the ARP table entry was learned. It can be one of the following: Dynamic—Entry was learned using AARP. Hardware—Entry was learned from an adapter in the communication server. Pending—Entry for a destination for which the communication server does not yet know the address. When a packet requests to be sent to an address for which the communication server does not yet have the MAC-level address, the communication server creates an AARP entry for that AppleTalk address, then sends an AARP Resolve packet to get the MAC-level address for that node. When the communication server gets the response, the entry is marked "Dynamic." A pending AARP entry times out after one minute. |
Hardware Addr | MAC address of this interface. |
Encap | Encapsulation type. It can be one of the following:
|
Interface | Type and number of the interface. |
To display the status of the AppleTalk interfaces and the parameters configured on each interface, use the show appletalk interface EXEC command.
show appletalk interface [brief] [interface unit]
| brief | (Optional.) Displays a brief summary of the status of the AppleTalk interfaces. |
interface unit | (Optional.) Interface and unit identifiers. The argument interface can be one of the following types: asynchronous, dialer, Ethernet (IEEE 802.3), loopback, null, serial, or tunnel. The argument unit is the number of the interface. For example, ethernet 0 specifies the first Ethernet interface. |
EXEC
The show appletalk interface command is particularly useful for discovering the status of the interface when you first enable AppleTalk.
The following is sample output from the show appletalk interface command for an extended AppleTalk network:
CS# show appletalk interface
Ethernet0 is up, line protocol is up
AppleTalk cable range is 111-111
AppleTalk address is 111.188, Valid
AppleTalk zone is Cisco Interop Demo
AppleTalk port configuration verified by 111.59
AppleTalk route cache is not supported by hardware
Table 2-2 describes the fields shown in the display as well as some fields not shown but that might also be displayed.
| Field | Description |
|---|---|
Ethernet0 is up | Type of interface and whether it is currently active and inserted into the network (up) or inactive and not inserted (down). |
line protocol is up | Indicates whether the software processes that handle the line protocol believe the interface is usable (that is, whether the keepalives are successful). |
AppleTalk cable range is start-end | Cable range of the interface. |
AppleTalk address is address, Valid | Address of the interface, and whether the address conflicts with any other address on the network ("valid" means it does not). |
AppleTalk zone is zone. | Name of the zone that this interface is in. |
AppleTalk port configuration verified by address (name) | Indicates whether the interface was configured in discovery mode. If it was, this line shows which communication server provided the configuration information. |
AppleTalk route cache is not supported by hardware | Indicates whether fast switching is enabled on the interface. |
Port configuration mismatch | Indicates that the communication server is misconfigured. |
Interface violates Internet compatibility | Usually indicates that extended and nonextended AppleTalk nodes are incorrectly sharing the same network. |
The following is sample output from the show appletalk interface command for a nonextended AppleTalk network:
CS# show appletalk interface e0
Ethernet0 is up, line protocol is up
AppleTalk address is 666.128, Valid
AppleTalk zone is Underworld
Table 2-3 describes the fields shown in the display.
| Field | Description |
|---|---|
Ethernet 0 is up | Type of interface and whether it is currently active and inserted into the network (up) or inactive and not inserted (down). |
line protocol is up | Indicates whether the software processes that handle the line protocol believe the interface is usable (that is, whether keepalives are successful). |
AppleTalk address is address, Valid | Address of the interface, and whether the address conflicts with any other address on the network ("valid" means it does not). |
AppleTalk zone is zone. | Name of the zone that this interface is in. |
The following is sample output from the show appletalk interface brief command:
CS# show appletalk interface brief
Interface Address Config Status/Line Protocol Atalk Protocol
Ethernet0 10.82 Extended up up
Async 0 unassigned not config'd administratively down n/a
Table 2-4 describes the fields shown in the display.
| Field | Description |
|---|---|
Interface | Interface and unit identifiers. |
Address | Address assigned to the interface. |
Config | How the interface is configured. Possible values are extended, nonextended, and not configured. |
Status/Line Protocol | Whether the software processes that handle the line protocol believe the interface is usable (that is, whether keepalives are successful). |
Atalk Protocol | Whether AppleTalk is up and running on the interface. |
To display status information about all known MacIP clients, use the show appletalk macip-clients EXEC command.
show appletalk macip-clientsThis command has no arguments or keywords.
EXEC
The following is sample output from the show appletalk macip-clients command:
CS# show appletalk macip-clients
131.108.199.1@[27001n,69a,72s] 45 secs 'S/W Test Lab'
Table 2-5 describes the fields shown in the display.
| Field | Description |
|---|---|
131.108.199.1@ | Client IP address. |
[2700ln,69a,72s] | DDP address of the registered entity, showing the network number, node address, and socket number. |
45 secs | Time, in seconds, since the last NBP confirmation was received. |
`S/W Test Lab' | Name of the zone to which the MacIP client is attached. |
show appletalk traffic
To display status information about a communication server's servers, use the show appletalk macip-servers EXEC command.
show appletalk macip-serversThis command has no arguments or keywords.
EXEC
The information in the show appletalk macip-servers display can help you quickly determine the status of your MacIP configuration. In particular, the STATE field can help identify problems in your AppleTalk environment.
The following is sample output from the show appletalk macip-servers command:
CS# show appletalk macip-servers
MACIP SERVER 1, IP 131.108.199.221, ZONE 'S/W Test Lab' STATE is server_up
Resource #1 DYNAMIC 131.108.199.1-131.108.199.10, 1/10 IP in use
Resource #2 STATIC 131.108.199.11-131.108.199.20, 0/10 IP in use
Table 2-6 describes the fields shown in the display.
| Field | Description |
|---|---|
MACIP SERVER 1 | Number of the MacIP server. This number is assigned arbitrarily. |
IP 131.108.199.221 | IP address of the MacIP server. |
ZONE `S/W Test Lab' | AppleTalk server zone specified with the appletalk macip server command. |
STATE is server_up | State of the server. Table 2-8 lists the possible states. If the server remains in the "resource_wait" state, check that resources have been assigned to this server with either the appletalk macip dynamic or the appletalk macip static command. |
Resource #1 DYNAMIC | Resource specifications defined in the appletalk macip dynamic and appletalk macip static commands. This list indicates whether the resource address was assigned dynamically or statically, identifies the IP address range associated with the resource specification, and indicates the number of active MacIP clients. |
Use the show appletalk macip-servers command with show appletalk interface to identify AppleTalk network problems, as follows:
Step 2 Determine the status of AppleTalk and the specific interface using the show appletalk interface command.
Step 3 If the protocol and interface are up, check the MacIP configuration commands for inconsistencies in the IP address and zone.
The STATE field of the show appletalk macip-servers command indicates the current state of each configured MacIP server. Each server operates according to the finite-state machine table in
Table 2-7. Table 2-8 describes the state functions listed in Table 2-7. These are the states that are displayed by the show appletalk macip-servers command.
| State | Event | New State | Notes |
|---|---|---|---|
initial | ADD_SERVER | resource_wait | Server configured |
resource_wait | TIMEOUT | resource_wait | Wait for resources |
resource_wait | ADD_RESOURCE | zone_wait | Wait for zone seeding |
zone_wait | ZONE_SEEDED | server_start | Register server |
zone_wait | TIMEOUT | zone_wait | Wait until seeded |
server_start | START_OK | reg_wait | Wait for server register |
server_start | START_FAIL | del_server | Could not start (possible configuration error) |
reg_wait | REG_OK | server_up | Registration successful |
reg_wait | REG_FAIL | del_server | Registration failed (possible duplicate IP address) |
reg_wait | TIMEOUT | reg_wait | Wait until register |
server_up | TIMEOUT | send_confirms | NBP confirm all clients |
send_confirms | CONFIRM_OK | server_up |
|
send_confirms | ZONE_DOWN | zone_wait | Zone or IP interface down; restart |
* | ADD_RESOURCE | * | Ignore, except resource_wait |
* | DEL_SERVER | del_server | "No server" statement (HALT) |
* | DEL_RESOURCE | ck_resource | Ignore |
ck_resource | YES_RESOURCES | * | Return to previous state |
ck_resource | NO_RESOURCES | resource_wait | Shutdown and wait for resources |
| State | Description |
|---|---|
ck_resource | The server makes sure at least one client range is available. If not, it deregisters NBP names and returns to the resource_wait state. |
del_server | State at which all servers end. In this state, the server deregisters all NBP names, purges all clients, and deallocates server resources. |
initial | State at which all servers start. |
resource-wait | The server waits until a client range for the server has been configured. |
send_confirms | The server requests a response from active clients every minute, deletes clients that have not responded within the last 5 minutes, and checks IP and AppleTalk interfaces used by MacIP server. If the interfaces are down or have been reconfigured, the server restarts. |
server_start | The server registers configured IPADDRESS and registers as IPGATEWAY. It then opens an ATP socket to listen for IP address assignment requests, sends NBP lookup requests for existing IPADDRESSes, and automatically adds clients with addresses within one of the configured client ranges. |
server_up | Server has registered. This enables routing to client ranges. The server now responds to IP address assignment requests. |
zone_wait | The server waits until the configured AppleTalk zone name for the server is up. The server will remain in this state if no such zone has been configured or if AppleTalk is not enabled. |
* | An asterisk in the first column represents any state. An asterisk in the second column represents a return to the previous state. |
appletalk macip dynamic
appletalk macip server
appletalk macip static
show appletalk interface
show appletalk traffic
To display statistics about MacIP traffic through the communication server, use the show appletalk macip-traffic EXEC command.
show appletalk macip-trafficThis command has no arguments or keywords.
EXEC
Use the show appletalk macip-traffic command to obtain a detailed breakdown of MacIP traffic that is sent through a communication server from an AppleTalk to an IP network. The output from this command differs from that of the show appletalk traffic command, which shows normal AppleTalk traffic generated, received, or routed by the communication server.
The following is sample output from the show appletalk macip-traffic command:
CS# show appletalk macip-traffic
-- MACIP Statistics
MACIP_DDP_IN: 11062
MACIP_DDP_IP_OUT: 10984
MACIP_DDP_NO_CLIENT_SERVICE: 78
MACIP_IP_IN: 7619
MACIP_IP_DDP_OUT: 7619
MACIP_SERVER_IN: 62
MACIP_SERVER_OUT: 52
MACIP_SERVER_BAD_ATP: 10
MACIP_SERVER_ASSIGN_IN: 26
MACIP_SERVER_ASSIGN_OUT: 26
MACIP_SERVER_INFO_IN: 26
MACIP_SERVER_INFO_OUT: 26
Table 2-9 describes the fields shown in the display.
| Field | Description |
|---|---|
MACIP_DDP_IN | Number of DDP packets received by the communication server. |
MACIP_DDP_IP_OUT | Number of DDP packets received by the communication server that were sent to the IP network. |
MACIP_DDP_NO_CLIENT_SERVICE | MacIP servers are configured to serve a specific range of IP addresses. If a client (Macintosh) has been assigned an IP address that is not in the server range, and then tries to route a packet thru the MacIP server, the packet is dropped and this statistic is incremented. This situation usually arises when the server is restarted after being configured with a different range of addresses, because the client Macintosh must reboot and obtain a new address. |
MACIP_IP_IN | Number of IP packets received by the communication server. |
MACIP_IP_DDP_OUT | Number of IP packets received by the communication server that were sent to the AppleTalk network. |
MACIP_SERVER_IN | Number of packets destined for MacIP servers. |
MACIP_SERVER_OUT | Number of packets sent by MacIP servers. |
MACIP_SERVER_BAD_ATP | This statistic is incremented if MacIP receives a badly formated AppleTalk ATP packet. |
MACIP_SERVER_ASSIGN_IN | Counts the total number of assignment request packets received by MacIP. |
MACIP_SERVER_ASSIGN_OUT | Counts the total number of assignment request packet replies sent by MaciP. It should be equal to the MACIP_SERVER_ASSIGN_IN statistic. |
MACIP_SERVER_INFO_IN | This statistic counts the total number of information request packets received by MacIP. The information request is sent by MacIP clients after it has received its address assignment. |
MACIP_SERVER_INFO_OUT | This statistic counts the total number of information request packets sent by macip. The information response contains the IP subnet mask, the IP broadcast address, the default IP router, the default domain name, and the IP address of the configured domain name server. |
show appletalk traffic
To display statistics about AppleTalk traffic, including MacIP traffic, use the show appletalk traffic EXEC command.
show appletalk trafficThis command has no arguments or keywords.
EXEC
For MacIP traffic, an IP alias is established for each MacIP client and for the IP address of the MacIP server if it does not match an existing IP interface address. To display the client aliases, use the show ip aliases command.
The following is sample output from the show appletalk traffic command:
CS# show appletalk traffic
AppleTalk statistics:
Rcvd: 357471 total, 0 checksum errors, 264 bad hop count
321006 local destination, 0 access denied
0 for MacIP, 0 bad MacIP, 0 no client
13510 port disabled, 2437 no listener
0 ignored, 0 martians
Bcast: 191881 received, 270406 sent
Sent: 550293 generated, 66495 forwarded, 1840 fast forwarded
0 forwarded from MacIP, 0 MacIP failures
436 encapsulation failed, 0 no route, 0 no source
DDP: 387265 long, 0 short, 0 macip, 0 bad size
NBP: 302779 received, 0 invalid, 0 proxies
57875 replies sent, 59947 forwards, 418674 lookups, 432 failures
RTMP: 108454 received, 0 requests, 0 invalid, 40189 ignored
90170 sent, 0 replies
ATP: 0 received
ZIP: 13619 received, 33633 sent, 32 netinfo
Echo: 0 received, 0 discarded, 0 illegal
0 generated, 0 replies sent
Responder: 0 received, 0 illegal, 0 unknown
0 replies sent, 0 failures
AARP: 85 requests, 149 replies, 100 probes
84 martians, 0 bad encapsulation, 0 unknown
278 sent, 0 failures, 29 delays, 315 drops
Lost: 0 no buffers
Unknown: 0 packets
Discarded: 130475 wrong encapsulation, 0 bad SNAP discriminator
Table 2-10 describes the fields shown in the display.
| Field | Description |
|---|---|
Rcvd: | This section describes the packets that the communication server has received. |
357741 total | Total number of packets the communication server received. |
0 checksum errors | Number of packets that were discarded because their DDP checksum was incorrect. The DDP checksum is verified for packets that are directed to the communication server. It is not verified for forwarded packets. |
264 bad hop count | Number of packets discarded because they had traveled too many hops. |
321006 local destination | Number of packets addressed to the local communication server. |
0 access denied | Number of packets discarded because they were denied by an access list. |
0 for MacIP | Number of AppleTalk packets the communication server received that were encapsulated within an IP packet. |
0 bad MacIP | Number of bad MacIP packets the communication server received and discarded. These packets may have been malformed or may not have included a destination address. |
0 no client | Number of packets discarded because they were directed to a nonexistent MacIP client. |
13510 port disabled | Number of packets discarded because routing was disabled for that port (extended AppleTalk only). This is the result of a configuration error or a packet being received while the communication server is in verification/discovery mode. |
2437 no listener | Number of packets discarded because they were directed to a socket that had no services associated with it. |
0 ignored | Number of routing update packets ignored because they were from a misconfigured neighbor or because routing was disabled. |
0 martians | Number of packets discarded because they contained bogus information in the DDP header. What distinguishes this error from the others is that the data in the header is never valid as opposed to not being valid at a given point in time. |
Bcast: | Number of broadcast packets sent and received by the communication server. |
Sent: | This section describes the packets that the communication server has transmitted. |
550293 generated | Number of packets sent that were generated by the communication server. |
66495 forwarded | Number of packets sent that were forwarded by the communication server. |
1840 fast forwarded | Number of packets sent using routes from the fast-switching cache. |
0 forwarded from MacIP | Number of IP packets the communication server forwarded that were encapsulated within an AppleTalk DDP packet. |
0 MacIP failures | Number of MacIP packets sent that were corrupted during the MacIP encapsulation process. |
436 encapsulation failed | Number of packets the communication server could not send because encapsulation failed. This can happen because encapsulation of the DDP packet failed or because AARP address resolution failed. |
0 no route | Number of packets the communication server could not send because it knew of no route to the destination. |
0 no source | Number of packets the communication server sent when it did not know its own address. This should happen only if something is seriously wrong with the communication server or network configuration. |
DDP: | This section describes DDP packets seen by the communication server. |
387265 long | Number of DDP long packets. |
0 short | Number of DDP short packets. |
0 macip | Number of IP packets encapsulated in an AppleTalk DDP packet that the communication server sent. |
0 bad size | Number of packets whose physical packet length and claimed length differed. |
NBP: | This section describes NBP packets. |
302779 received | Total number of NBP packets received. |
0 invalid | Number of invalid NBP packets received. Causes include invalid op code and invalid packet type. |
0 proxies | Number of NBP proxy lookup requests received by the communication server when it was configured for NBP proxy transition usage. |
57875 replies sent | Number of NBP replies the communication server has sent. |
59947 forwards | Number of NBP forward requests the communication server has received. |
418674 lookups | Number of NBP lookups the communication server has received. |
432 failures | Generic counter that increments any time the NBP process experiences a problem. |
RTMP: | This section describes RTMP packets. |
108454 received | Total number of RTMP packets the communication server has received. |
0 requests | Number of RTMP requests the communication server has received. |
0 invalid | Number of invalid RTMP packets received. Causes include invalid op code and invalid packet type. |
40189 ignored | Number of RTMP packets the communication server ignored. One reason for this is that the interface is still in discovery mode and is not yet initialized. |
90170 sent | Number of RTMP packets the communication server has broadcast. |
0 replies | Number of RTMP replies the communication server has sent. |
ATP: | This section describes ATP packets. |
0 received | Number of ATP packets the communication server received. |
ZIP: | This section describes ZIP packets. |
13619 received | Number of ZIP packets the communication server has received. |
33633 sent | Number of ZIP packets the communication server has sent. |
32 netinfo | Number of packets that requested port configuration via ZIP GetNetInfo requests. These are commonly used during node startup and are occasionally used by some AppleTalk network management software packages. |
Echo: | This section describes AEP packets. |
0 received | Number of AEP packets the communication server received. |
0 discarded | Number of AEP packets the communication server discarded. |
0 illegal | Number of illegal AEP packets the communication server received. |
0 generated | Number of AEP packets the communication server generated. |
0 replies sent | Number of AEP replies the communication server sent. |
Responder: | This section describes Responder Request packets. |
0 received | Number of Responder Request packets the communication server received. |
0 illegal | Number of illegal Responder Request packets the communication server received. |
0 unknown | Number of Responder Request packets the communication server received that it did not recognize. |
0 replies sent | Number of Responder Request replies the communication server sent. |
0 failures | Number of Responder Request replies the communication server could not send. |
AARP: | This section describes AARP packets. |
85 requests | Number of AARP requests the communication server received. |
149 replies | Number of AARP replies the communication server received. |
100 probes | Number of AARP probe packets the communication server sent. |
84 martians | Number of AARP packets the communication server did not recognize. If you start seeing an inordinate number of martians on an interface, check whether a bridge has been inserted into the network. When a bridge is starting up, it floods the network with AARP packets. |
0 bad encapsulation | Number of AARP packets received that had an unrecognizable encapsulation. |
0 unknown | Number of AARP packets the communication server did not recognize. |
278 sent | Number of AARP packets the communication server sent. |
0 failures | Number of AARP packets the communication server could not send. |
29 delays | Number of AppleTalk packets delayed while waiting for the results of an AARP request. |
315 drops | Number of AppleTalk packets dropped because an AARP request failed. |
Lost: 0 no buffers | Number of packets lost due to lack of buffer space. |
Unknown: 0 packets | Number of packets whose protocol could not be determined. |
Discarded: | This section describes the number of packets that were discarded. |
130475 wrong encapsulation | Number of packets discarded because they had the wrong encapsulation.That is, nonextended AppleTalk packets were on an extended AppleTalk network, or vice versa. |
0 bad SNAP discrimination | Number of packets discarded because they had the wrong SNAP discriminator. This occurs when another AppleTalk device has implemented an obsolete or incorrect packet format. |
A dagger () indicates that the command is documented in the Communication Server Command Reference publication.
show appletalk macip-traffic
show ip aliases
To display the entries in the zone information table, use the show appletalk zone EXEC command.
show appletalk zone [zone-name]
no argument | Displays all entries in the zone information table. |
zone-name | (Optional.) Displays the entry for the specified zone. |
EXEC
You can use this command on extended and nonextended networks.
A zone name can be associated with multiple network addresses or cable ranges, or both. This means that a zone name will effectively replace multiple network addresses in zone filtering. This is reflected in the output of the show appletalk zone command. For example, the zone named Mt. View 1 in the sample display below is associated with two network numbers and four cable ranges.
The following is sample output from the show appletalk zone command:
CS# show appletalk zone
Name Network(s)
Gates of Hell 666-666
Engineering 3 29-29 4042-4042
customer eng 19-19
CISCO IP 4140-4140
Dave's House 3876 3924 5007
Narrow Beam 4013-4013 4023-4023 4037-4037 4038-4038
Low End SW Lab 6160 4172-4172 9555-9555 4160-4160
Tir'n na'Og 199-199
Mt. View 1 7010-7010 7122 7142 7020-7020 7040-7040 7060-7060
Mt. View 2 7152 7050-7050
UDP 1112-12
Empty Guf 69-69
Light 80
europe 2010 3010 3034 5004
Bldg-13 4032 5026 61669 3012 3025 3032 5025 5027
Bldg-17 3004 3024 5002 5006
Table 2-11 describes the fields shown in the display.
| Field | Description |
|---|---|
Name | Name of the zone. |
Network(s) | Cable ranges or network numbers assigned to this zone. |
The following is sample output from the show appletalk zone command when you specify a zone name:
CS# show appletalk zone CISCO IP
AppleTalk Zone Information for CISCO IP:
Valid for nets: 4140-4140
Not associated with any interface.
Not associated with any access list.
Table 2-12 describes the fields shown in the display.
| Field | Description |
|---|---|
AppleTalk Zone Information for CISCO IP: | Name of the zone. |
Valid for nets: 4140-4140 | Cable range(s) or network numbers assigned to this zone. |
Not associated with any interface. | Interfaces that have been assigned to this zone. |
Not associated with any access list. | Access lists that have been defined for this zone. |
appletalk zone
To display information about a running ARAP connection, use the show arap EXEC command.
show arap [line-number]
line-number | (Optional.) Number of the line on which an ARAP connection is established and active. |
User-level EXEC
Use the show arap command with no arguments to display a summary of the ARAP traffic since the communication server was last booted.
The following is sample output from the show arap command:
CS# show arap
Statistics are cumulative since last reboot
Total ARAP connections: 2
Total Appletalk packets output: 157824
Total Appletalk packets input: 12465
These fields refer to the sum of all of the ARA connections since the box was last reloaded.
The following example results in a display of information about ARA activity on a specific line (line 3):
CS# show arap 3
Active for 23 minutes
"Unlimited time left" or "22 minutes left"
"Doing smartbuffering" or "Smartbuffering disabled"
Appletalk packets output: 157824
Appletalk packets input: 12465
Appletalk packets overflowed: 1642
Appletalk packets dropped: 586
V42bis compression efficiency (incoming/outgoing): {percentage/percentage}
MNP4 packets received: 864
MNP4 packets sent: 1068
MNP4 garbled packets received: 4
MNP4 out of order packets received: 0
MNP4 packets resent: 0
MNP4 nobuffers: 0
Table 2-13 describes the fields shown in the display.
| Field | Description |
|---|---|
Active for {integer} minutes | Number of minutes since ARAP started on the line. |
Unlimited time left or {integer} minutes left | Remaining time limit on the line, if applicable on the line. |
Doing smartbuffering or Smartbuffering disabled | Obsolete. Always says Doing smartbuffering |
Appletalk packets output:
| Number of AppleTalk packets that have been received from the macintosh and out to the network during this connection. |
Appletalk packets input: | Number of AppleTalk packets have been received from the network and sent to the macintosh during this connection. |
Appletalk packets overflowed: | Number of packets from the network that have been dropped because the link to the macintosh was congested. |
Appletalk packets dropped: | Number of packets from the network that have been dropped because it was unnecessary to pass them (frequently RTMP). |
V42bis compression efficiency (incoming/outgoing): | Performance of the v42bis protocol underneath ARA, expressed as percentage of incoming/percentage outgoing. If the efficiency is low, a network user is probably copying already compressed files across the link. Generally, low efficieny means slow performance. |
MNP4 packets received: | Number of link-level packets that have been received from the macintosh. |
MNP4 packets sent: | How many link-level packets have been sent to the macintosh. |
MNP4 garbled packets received: MNP4 out of order packets received: MNP4 packets resent: | Number of garbled packets that have been received from the macintosh. Number of out-of-order packets that have been received from the macintosh. Number of times packets have been resent. Each of these fields indicates line noise. The higher the value, the higher the noise. |
MNP4 nobuffers: | How many times MNP4 has run out of buffers. This field should be zero. |
Posted: Sun Aug 19 00:08:24 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.