cc/td/doc/product/software/ssr83
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Router Products Release Notes for Software Release 8.3

Router Products Release Notes for Software Release 8.3

This release note describes the features, modifications, and caveats for Software Release 8.3, including 8.3(1) through 8.3(9). Refer to the Router Products and Configuration Reference publication, dated October 1991, for complete router product documentation for Release 8.3. A list and description of the current software versions available from Cisco Systems is included in the "Software Version Levels" section in this document.


Note Release 8.3(9) is the last maintenance Release for 8.3. Maintenance customers will continue to receive phone support from CE, but fixes will be made only to Release 9.0 and higher releases. As of August 2, 1993, Release 9.1(5) is the preferred upgrade path for a Release 8.3 user.

Note This release note no longer contains the microcode release notes. Information about system cards and microcode versions is contained in the Cisco publication Microcode Release Note, part number 78-1069.

Introduction

This release note covers the following topics:

Software Version Levels

The table that follows describes the software versions for Cisco router and TRouter software. Refer to these descriptions when ordering software updates for Software Release 8.3.

Versions

System

Description

ROMs

8.3(1-9) GS3 CSC/3 Gateway Server Sets:
GS3-F
GS3-BF
GS3-FX
GS3-BFX

8
8
8
8
8.3(1-9) GS2 CSC/2 Gateway Server Sets:
GS2-R
GS2-BR
GS2-RX
GS2-BRX

8
8
8
8
8.3(1-9) TR3 CSC/3 TRouter Sets:
TR3-X

4
8.3(1-9) TR2 CSC/2 TRouter Sets:
TR2-RX

8
8.3(1-9) IGS IGS Server Sets:
IGS-R
IGS-BR
IGS-RX
IGS-BPRX
IGS-BRX

8
8
8
8
8

Letter Key:
B--Bridging software
F--Standard system software with ciscoBus complex
P--Protocol translation software
R--Standard system software which executes out of ROM
X--Standard and Commercial/DDN X.25 software

The software images that run on a CSC/2 processor have been expanding as new feature code has been added for each software release. Some of these images (GS2-R, GS2-BR, GS2-RX, GS2-BRX, TR2-RX) have now exceeded the 1-MB ROM capacity of the current CSC/2 processor boards. As a result, as of Software Release 8.3 these images are shipped on 2-MB ROMs. This change requires an accompanying PAL change to support the addressing of the added megabyte. The new PAL (Cisco Part Number 17-0987-01) that Cisco provides for this support is compatible only with 2-MB ROMs and does not support the use of 1-MB ROMs.

Refer to the Cisco Systems publication Modular Products Hardware Installation and Reference for the procedures for updating your system with the latest software version, including procedures for EPROM replacement.

New Hardware Features

Release 8.3 introduces support for the High-Speed Serial-Port Communications Interface (HSCI) complex, which provides a connection for two new interfaces: HSA and ULA. HSA provides connection for the High-Speed Serial Interface (HSSI) specification, and ULA provides connection to UltraNet network environments.

The HSA interface provides a single, full-duplex synchronous serial connection capable of transmitting and receiving data at up to 52 Mbps. The HSSI specification is a de facto industry standard, providing connectivity to DS3, E3, Frame Relay at DS3, and other high-speed wide-area services through a DSU or line termination unit.

The ULA interface product, which is available exclusively from Ultra Network Technologies, provides a fiber or coax interface to supercomputer environments through an Ultra Network Technologies hub at rates of up to 125 Mbps.


Note Use of these devices requires installation of new microcode levels. Refer to the Cisco publication Microcode Release Note, part number 78-1069, for information about the mandatory upgrades required for these new Release 8.3 features.

New Software Features for Software Release 8.3(1)

This section describes the major functions introduced in Release 8.3(1) of the router software.

System and Interface Configuration Features

Release 8.3(1) includes the following enhancements and changes to its interface configuration capabilities.

ultranet address ultranet-mac-address [no] loopback {applique|dte|line|remote}

Old Format New Format

service domain ip domain-lookup

service ipname ip ipname-lookup

service subnet-zero ip subnet-zero


Note The old formats for the service commands are accepted in configuration input, but the output of the write terminal or show config commands displays the new forms.

New Routing Configuration Features

Software Release 8.3(1) includes enhancements to Cisco's routing configuration capabilities. These modifications are described in the Router Products Configuration and Reference publications.

Internet Protocol (IP) Routing

The following enhancements have been made to Cisco's IP routing implementation:

The new command follows:
[no] ip route-cache [cbus]
Note Customers who want to use autonomous switching must upgrade the microcode on their MEC, FDDI, and CCTL cards. (The Cisco publication Microcode Release Note, part number 78-1069, provides more information about this.) Because a significant number of components needs to be replaced on these boards, we recommend that users take advantage of Cisco's advance board replacement service to implement these upgrades. For more details on this service, contact Customer Service at 800-553-NETS (6387).
[no] ip tcp header-compression [passive] ip probe proxy

AppleTalk Routing

Cisco's AppleTalk protocol implementation has undergone the following modifications:

[no] apple strict-rtmp [no] apple send-rtmp [no] apple proxy-nbp appletalk iptalk-baseport
appletalk timers (documented on page 10-15 of the Router Products Configuration and Reference publication)
appletalk iptalk (documented on page 10-13 of the (Router Products Configuration and Reference publication)
[no] apple distribute-list {in | out}
appletalk discovery (documented on page 10-13 of the Router Products Configuration and Reference publication)
clear apple neighbors clear apple route

ISO CLNS Routing

Release 8.3(1) includes the following modifications to Cisco's ISO CLNS protocol implementation:

clns router igrp tag level2

Apollo Routing

Banyan VINES Routing

Release 8.3(1) includes the following changes to Cisco's Banyan VINES protocol implementation:

IBM Connectivity Features

There are several new additions to Cisco's support for IBM connectivity environments with Release 8.3(1). (For information on source-route bridging, refer to the "Bridging" part of the reference manual.)

SDLC Transport (Serial Tunnel)

Software Release 8.3(1) introduces support for serial tunnel (STUN) functionality, also known as SDLC Transport, for encapsulating SDLC-framed traffic into IP packets and routing them over any IP-supported media through use of the TCP transport mechanism.

[no] stun peer-name ip-address [no] stun poll-interval milliseconds [no] stun primary-pass-through seconds [no] stun protocol-group group-number protocol [no] stun schema name offset constant-offset length address-length
format format-keyword
encapsulation stun [no] stun group group-number [no] stun proxy-poll address address modulus modulus {primary|secondary} [no] stun proxy-poll address address discovery [no] stun route all tcp ip-address [no] stun route all interface serial interface-number [no] stun route all interface serial interface-number direct [no] stun route address address-number tcp ip-address [no] stun route address address-number interface serial interface-number [no] stun route address address-number interface serial interface-number direct

NetBIOS

[no] netbios access-list host name {permit|deny} pattern [no] netbios input-access-filter-host name [no] netbios output-access-filter-host name [no] netbios access-list bytes name {permit|deny} offset pattern [no] netbios input-access-filter bytes name [no] netbios output-access-filter-bytes name

WAN Features

With Software Release 8.3(1), Cisco introduces new and enhanced support for WANs.

[no] backup delay {enable-delay|ever} {disable-delay |never} [no] backup interface interface-name [no] backup load {enable-threshold|never} {disable-load|never} encapsulation smds [no] smds address smds-address [no] smds att-mode [no] smds enable-arp [no] smds multicast protocol-type smds-group-address [no] smds static-map protocol-type protocol-address smds-address

Network Management Features

SNMP

Cisco's SNMP support has undergone several changes.

Miscellaneous Enhancements

Bridging Features

Cisco has added new bridging support with Release 8.3(1), including enhancements to transparent bridging and source-route bridging (SRB).

Transparent Bridging

Release 8.3(1) includes the following changes to Cisco's software support for transparent bridging:

bridge group domain domain-number
Global:
bridge group lat-service-filtering
Interface:
bridge-group number input-lat-service-deny grouplist bridge-group number input-lat-service-permit grouplist bridge-group number output-lat-service-deny grouplist bridge-group number output-lat-service-permit grouplist

Source-Route Bridging

Following is a list of the Release 8.3(1) changes to Cisco's source-route bridging software.

[no] source-bridge tcp-queue-max number
The show source-bridge EXEC command now displays the queue length.

Documentation Enhancements

As of Software Release 8.3(1), Cisco's documentation set has a new format that includes the following changes:

Obsolete Commands and Capabilities

This section lists the commands and capabilities of the Cisco router software that are no longer supported as of Release 8.3(1).

New Software Features for Software Release 8.3(2)

This section describes new software features and enhancements that were added to the software with Release 8.3(2).

Enable and Console Passwords and the SNMP Community String

With Software Release 8.3(2), the software no longer allows the enable password or the console password to be used as the community string for SNMP.

New Routing Configuration Features in Release 8.3(2)

Software Release 8.3(2) includes enhancements to Cisco's routing configuration capabilities. These modifications are described in the Router Products Configuration and Reference publication.

Internet Protocol (IP) Routing

Enhancements have been made to Cisco's IP routing implementation.

ip proxy arp no arp probe ip probe proxy

Changes in HP Probe Proxy Behavior

Because the defaults are now the no arp probe and no ip proxy arp commands, you must specifically configure the arp probe command on all interfaces that support HP Probe Proxy. Other changes include the following:

New Software Features for Software Release 8.3(5)

This section describes new software features and enhancements that were added to the software with Release 8.3(5).

IGS/TR Functionality Supported

Software Release 8.3(5) adds the ability to perform remote source-route bridging over X.25 on the IGS/TR platform.

The operational ring speed for the ISG Token Ring connector is set with the following configuration command:

ring-speed speed

The argument speed is 4 for 4 Mbps, or 16 for 16 Mbps.

Additional User Notes

This section provides technical notes that supplement information found in the software and hardware manuals.

Token Ring Restarts

If the system receives an indication of a cabling problem from a CSC-R16 Token Ring interface, that interface is placed in a reset state. The system does not attempt to restart the interface. To restart the interface, correct the cabling problem and use the clear interface command to reset it.

The system functions in this manner because periodic attempts to restart the Token Ring interface have drastic effects on the stability of routing tables, and sometimes on the stability of Token Ring networks themselves.

Netboot Restrictions

Netbooting over X.25 or Frame Relay is not allowed to a broadcast address. You must specify the address of a server host to successfully netboot the system files. Use an off-net map entry of the destination. This means that you cannot simply have an X.25 or Frame Relay map entry for the next hop router. You need a map entry (use the x25 map or frame-relay map commands) for the host from which you will boot, even if that host is not on a directly connected network.

X.25 Example

The x25 map command is used to map an IP address into an X.121 address. There must be an x25 map command which matches the IP address given on the boot system command line. In order to netboot over X.25, the address of the system from which to netboot must be given explicitly, and an x25 map entry must exist for that site, as the following example illustrates.

boot system gs3-bfx.83-2.0 131.108.13.111 ! interface Serial 1 ip address 131.108.126.200 255.255.255.0 encapsulation X25-DCE x25 address 10004 x25 map IP 131.108.13.111 10002 BROADCAST lapb n1 12040 clockrate 56000
Frame Relay Example

If file gs3-bfx is to be booted from a host with IP address 131.108.126.2, the following would need to be in the configuration:

boot system gs3-bfx 131.108.126.2 ! interface Serial 0 encapsulation frame-relay frame-relay map IP 131.108.126.2 100 broadcast

SMDS Interoperability

Routers running software version 8.3(1) cannot interoperate over SMDS with routers running version 8.3(2) or later.

Subnetting the Same IP Address across X.25

In order to configure load sharing across multiple X.25 serial lines, the entries for all the adjacent interface IP addresses need to be included in the x25 map command for each serial interface.

As an example, two routers, Cisco A and Cisco B, each with two serial interfaces, would require the following configuration files to allow subnetting the same IP address:

--------- --------- | |------/-----------| | | | S1 S0 | | | Cisco | | Cisco | | A |------/-----------| B | | | S2 S3 | | --------- ---------
Cisco A
interface serial 1 ip 131.108.170.1 255.255.255.0 x25 address 11 x25 map ip 131.108.170.3 13 x25 map ip 131.108.170.4 13 interface serial 2 ip 131.108.170.2 255.255.255.0 x25 address 12 x25 map ip 131.108.170.4 14 x25 map ip 131.108.170.3 14
Cisco B
interface serial 0 ip 131.108.170.3 255.255.255.0 x25 address 13 x25 map ip 131.108.170.1 11 x25 map ip 131.108.170.2 11 interface serial 3 ip 131.108.170.4 255.255.255.0 x25 address 14 x25 map ip 131.108.170.2 12 x25 map ip 131.108.170.1 12

AppleTalk over FDDI

There is an interaction between AppleTalk and FDDI when mixing system version 8.2(4) (only) and later versions. If a router has both MCI Ethernet and FDDI interfaces while running 8.2(4), runts may be generated by the MCI interfaces when packets are sent from a router running a version later than 8.2(4) across the FDDI to the 8.2(4) router and forwarded via the MCI Ethernet interface(s).

The solution is to upgrade all 8.2(4) routers with FDDI and MCI Ethernet interfaces before upgrading any other routers on the FDDI ring in question. A workaround is to disable AppleTalk fast switching on the MCI Ethernet interfaces of the affected 8.2(4) routers. This is done with the command no apple route-cache.

Novell IPX Packet Sizes

With Release 8.3(2), Cisco's Novell IPX implementation supports packet sizes of more than 576 bytes on media that are capable of carrying packets of that size. Until recently, no Novell end node would send or accept a packet larger than this size; this has changed in newer Novell software. The software now accepts Novell IPX packets up to the maximum size allowed on the media. [CSCdi04193]

Novell SAP Update Delays

When applying a SAP update delay to a Novell interface, Novell indicates that the delay should not exceed 120 ms and recommends that it be much smaller than 120 ms. Delay values in the range of 2 to 8 ms are common. If you need to use a larger SAP update delay time, you should increase the size of the input hold queue using the hold-queue length in interface subcommand.

XNS Ungermann-Bass

On page 19-7 in the section "Configuring Ungermann-Bass Net/One XNS," it states that netbooting does not work in the current Cisco software. However, there is a workaround for this restriction. Because Ungermann-Bass devices can boot from another protocol that cannot be routed, you can use bridging to pick up the network identifier (ID). The steps for this workaround follow:

Step 1: In order for the NIU to netboot correctly across a Cisco router, you need to bridge 0x7000 (etype 7000) to 0x7005 inclusively.

Step 2: The download server (DLS) on the NetDirector has to run with the -Bytes option on. This option causes the NIUs to receive their XNS network ID as it is configured in their LC file. The default startup for a download server causes an NIU to use the same XNS network ID as the download server.

Step 3: To locate service names not on the same segment, the users must type *service_name instead of just service_name, so that the NIU will do an all-xns-net-broadcast instead of just a local-xns-net broadcast (XNS type 4 destined to -1.ffff.ffff.ffff).

8.3(9) Caveats

This section describes possibly unexpected behavior by Release 8.3(9). Unless otherwise noted, these caveats apply to all 8.3 releases up to and including 8.3(9).

AppleTalk

Basic System Services

Interfaces and Bridging

IP Routing

Booting gs3-k.91 from 223.255.254.254: !O.OO.O.......... [timed out]

IP Routing Protocols

ISO CLNS

VINES

Wide-Area Networking

XNS/Novell IPX/Apollo Domain

8.3(8) Caveats/8.3(9) Modifications

This section describes possibly unexpected behavior by Release 8.3(8). Unless otherwise noted, these caveats apply to all 8.3 releases up to and including 8.3(8). For additional caveats applicable to Release 8.3(9), see the caveats sections for newer 8.3 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 8.3(9).

AppleTalk

EXEC and Configuration Parser

IP Routing

XNS/Novell IPX/Apollo Domain

8.3(7) Caveats/8.3(8) Modifications

This section describes possibly unexpected behavior by Release 8.3(7). Unless otherwise noted, these caveats apply to all 8.3 releases up to and including 8.3(7). For additional caveats applicable to Release 8.3(7), see the caveats sections for newer 8.3 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 8.3(8).

AppleTalk

DECnet

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

IP Routing

IP Routing Protocols

ISO CLNS

TCP/IP Host-Mode Services

VINES

XNS/Novell IPX/Apollo Domain

In the 9.1 release, fast switching was enhanced to allow communication to FDDI and serial end hosts. Before 9.1, the router did not fast switch Novell frames to a Novell FDDI end host, but would always process switch them instead, so communication between actual end hosts was always effective.
The older release Novell fast switching code wrote packets sent to next-hop remote routers on FDDI and serial links with extra padding bytes, in such a way that it guaranteed that Novell frames output on Ethernet interfaces by the remote router would always have at least 64 bytes of data (plus 4 bytes of checksum).
The 9.1 fast switching code generates correctly formatted frames on FDDI and serial interfaces. However, the older releases of software will misinterpret these frames when fast switching, and generate output frames on Ethernet that, while valid frames, are smaller than 64 bytes.
Some versions of PC Ethernet drivers seem to require a 64 byte minimum frame size (plus 4 bytes of checksum). As such, if they are in a setting where a 9.1 and previous release router are running in series, they will not be able to accept the smaller frames.
This patch allows 8.3 and 9.0 to operate correctly with both correctly formatted input frames from release 9.1, or incorrectly formatted input frames from previous releases, on both FDDI or serial.
Note 1: The problem in 8.3 and 9.0 can be worked around by turning off fast switching on the 9.1 router's FDDI or serial interface.
Note 2: This patch will also fix problems where 8.3 or 9.0 cannot correctly forward frames sent by a PC FDDI end host onto an Ethernet. [CSCdi09754]

8.3(6) Caveats/8.3(7) Modifications

This section describes possibly unexpected behavior by Release 8.3(6). Unless otherwise noted, these caveats apply to all 8.3 releases up to and including 8.3(6). For additional caveats applicable to Release 8.3(8), see the caveats sections for newer 8.3 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 8.3(7).

AppleTalk

Basic System Services

DECnet

IBM Connectivity

Interfaces and Bridging

IP Routing

IP Routing Protocols

ISO CLNS

Local Services

IP-3-Desthost:src=200.2.3.1 dst=0.0.0.0 Null desthost Process="SNMP Server",level=0,pid=28 Traceback=23628 23364 2500e 26a14 269ae 26c00 391da 81bbc

TCP/IP Host-Mode Services

VINES

[no] multiring {protocol | all} [all-routes | spanning]

The trailing all-routes and spanning keywords specify the explorer type to be used. The default is to use spanning tree explorers. [CSCdi09091]

XNS/Novell IPX/Apollo Domain

8.3(5) Caveats/8.3(6) Modifications

This section describes possibly unexpected behavior by Release 8.3(5) that has been resolved in Release 8.3(6). Unless otherwise noted, these caveats applied to all 8.3 releases up to and including 8.3(5).

All the caveats listed in this section are resolved in Release 8.3(6).

AppleTalk

"% One of "probe" or "request""

This message can be ignored. [CSCdi05694]

Basic System Services

DECnet

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

Note: The only action that is required for the interface to come back up is to turn off keepalives. Turning them back on is optional, but doing this will correctly turn off "line protocol" if the line goes down in the future. [CSCdi05172]

IP Routing Protocols

ISO CLNS

Local Services

TCP/IP Host-Mode Services

!!!!!!.O.........[timeout] !!!!!!OOOOOOOOO!OOOOOOOOOO!OOOOOOOOOO!OOOO....[timeout] !!!!!!.!O...... [timeout]

VINES

4 routes, next update 77 seconds Codes: R - RTP derived, C - connected, S - static RN Net 0027AF9A [2] via 0027AF9A:1, 10 sec, 0 uses, Ethernet0 C Net 30004355 is this router's network, 0 uses R Net 002ABFAA [2] via 002ABFAA:1, 10 sec, 0 uses, Ethernet0 R Net 3000FB06 [1] via 3000FB06:1, 8 sec, 0 uses, Fddi0

where the capital letter "N" indicates that this server is the nearest server, and it is on the local network. The lowercase letter "n" is used to indicate that this server is considered the nearest server, but it is not on the local network. [CSCdi02868]

X.25

%X25-3-INTIMEQ Interface [chars], LCN [dec] already in timer queue, new time [dec]
is used as a diagnostic aid; although an unexpected condition was detected and reported, the operation of the router and the X.25 protocol are not affected. If this message is produced, contact Cisco Systems and include the text and traceback of this message as well as the information from the show version command. [CSCdi07238]

XNS/Novell IPX/Apollo Domain

8.3(4) Caveats/8.3(5) Modifications

This section describes possibly unexpected behavior by Release 8.3(4). Unless otherwise noted, these caveats apply to all 8.3 releases up to and including 8.3(4). For additional caveats applicable to Release 8.3(4), see the caveats sections for newer 8.3 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 8.3(5).

AppleTalk

IP Routing Protocols

8.3(3) Caveats/8.3(4) Modifications

This section describes possibly unexpected behavior by Release 8.3(3). Unless otherwise noted, these caveats apply to all 8.3 releases up to and including 8.3(3). For additional caveats applicable to Release 8.3(3), please see the caveats sections for newer 8.3 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 8.3(4).

AppleTalk

Basic System Services

buffers small min-free 20 buffers middle min-free 10 buffers big min-free 5
Extra lines of default buffers clutter the NVRAM listing. If a user does a write memory command, it will save this config to the NVRAM. This will cause them to stay permanently in your configuration even in future releases. A user must use the no commands for each line to clear the extra messages. [CSCdi04904]

EXEC and Configuration Parser

IBM Connectivity

%TR-3-RESETFAIL: Unit 0, reset failed, error code 00007F32. -Traceback= 97F84 97CFA 970A2 96FBE 9C5E8 12766 37F8 1D1E
may appear, indicating that the token ring interface was unable to reset itself. [CSCdi05644]

Interfaces and Bridging

%SYS-2-LINKED: Bad enqueue of 26BFE8 in queue 1E5450 -Process= "Net Background", ipl= 4, pid= 9 -Traceback= 7442 323F8 2EFF2 13ABA 10FF6 2434

IP Routing

IP Routing Protocols

ISO CLNS

LAT

Local Services

TCP/IP Host-Mode Services

VINES

X.25

XNS/Novell IPX/Apollo Domain

8.3(2) Caveats/8.3(3) Modifications

This section describes possibly unexpected behavior by Release 8.3(2). Unless otherwise noted, these caveats apply to all 8.3 releases up to and including 8.3(2). For additional caveats applicable to Release 8.3(2), please see the caveats sections for newer 8.3 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 8.3(3).

AppleTalk

Basic System Services

DECnet

EXEC and Configuration Parser

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Local Services

TCP/IP Host-Mode Services

X.25

XNS/Novell IPX/Apollo Domain

8.3(1) Caveats/8.3(2) Modifications

This section describes possibly unexpected behavior by Release 8.3(1). Unless otherwise noted, these caveats apply to all 8.3 releases up to and including 8.3(1). For additional caveats applicable to Release 8.3(1), see the caveats sections for newer 8.3 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 8.3(2).

AppleTalk

Basic System Services

DECnet

IBM Connectivity

Interfaces and Bridging

IP Routing Protocols

ISO CLNS

Local Services

TCP/IP Host-Mode Services

VINES

X.25

XNS/Novell IPX/Apollo Domain

Customer Information Online

Cisco Systems' Customer Information Online (CIO) system provides online information and electronic services to Cisco direct customers and business partners. Basic CIO services include general Cisco information, product announcements, descriptions of service offerings, and download access to public or authorized files or software. Maintenance customers receive a much broader offering, including technical notes, the bug database, and electronic mail access to the TAC. (Maintenance customers must have authorization from their Cisco contract administrators to receive these privileges.)

For dialup or Telnet users, CIO supports Zmodem, Kermit, Xmodem, FTP PUT, Internet e-mail, and fax download options. Internet users also can use FTP to retrieve files from CIO.

Registration for CIO is handled on line. To reach CIO via the Internet, use Telnet or FTP to cio.cisco.com (131.108.89.33). To reach CIO by dialup, phone 415 903-8070 (Mountain View, CA), or 331 64 464082 (Paris, France).

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.