cc/td/doc/product/iaabu/csids
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

NetRanger Version 2.2.1 Release Notes

NetRanger Version 2.2.1 Release Notes

March 2000

These release notes discuss late changes, enhancements, and upgrade information for NetRanger version 2.2.1.

Contents

Note For the latest changes, enhancements, and upgrade information regarding the NetRanger 2.2.1 release, refer to the README.txt file on the NetRanger CD-ROM.

Documentation Late Changes

This section describes late changes to the NetRanger User Guide Version 2.2.1 after it went to press, and discusses the following topics:

EMC Compliance Statements

The following EMC compliance statements apply to NetRanger:

Caution Modifying the equipment without Cisco's authorization may result in the equipment no longer complying with FCC requirements for Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense.
Note Use of shielded cables is required to comply with the Class B limits of FCC part 15.

Laplink/File Transfer Cable

For NetRanger version 2.2.1, a DB-9 to DB-9 laplink/file transfer cable has been provided to allow access to the Sensor via its COM1 port.

To use the laplink/file transfer cable, follow these steps:

Step 1 Plug one end of the laplink/file transfer cable to your laptop's COM port, and the other end to the Sensor's COM1 port (illustrated in Figure 1).


Figure 1: Back of Sensor Appliance

Step 2 On your laptop, start your HyperTerminal software.

Step 3 Configure the following settings in the communications package:

Step 4 After you initiate the connection, you should see the following prompt:

ttya login:

Step 5 Log in as user netrangr.

Oracle - NetRanger Synchronization

The NetRanger DMP subsystem produces event/alarm reports from queries against its Oracle database. Some of the queries join data from the alarm database with the configuration information found in the /usr/nr/etc/organizations and /usr/nr/etc/signatures files. If a user updates the information in these files, it will create a mismatch with the Oracle representation of this configuration information.

This synchronization problem can be solved with periodic updates of the Oracle tables with current configuration information. This can be done in the following ways:

    1. Manually, by executing the /usr/nr/bin/updateOracleTables script from the command line.

    2. Every hour via a regularly scheduled condition-action trigger, by adding the following lines to the /usr/nr/etc/sapd.conf configuration file:

    FM_Action OracleInfoUpdate /usr/nr/bin/updateOracleTables /usr/nr/var/message.oracle
FM_IdleTime OracleInfoUpdate 60 /usr/nr OracleInfoUpdate
Note If you are installing NetRanger version 2.2.1 on a new system instead of upgrading to 2.2.1, this trigger will be configured automatically.

Exporting Log Files to a Remote FTP Server

NetRanger 2.2.1 supports exporting log files to a remote FTP server. The NetRanger log files can then be processed and reports generated on the data in them. For this feature to work, you need to complete the following tasks:

    1. Configure the FTP Server Software on the Remote Host.

    2. Configure NetRanger to Send Files to the FTP Server.

Note Exporting log files to an FTP server is only supported on the Director. A sapd update will be available in March 2000 that will allow exporting of log files to an FTP server, which will be supported in the Sensor. Check CCO to download the update and for instructions on installing and configuring sapd.

Configure the FTP Server Software on the Remote Host

Refer to your FTP server documentation for installation and configuration of the FTP server software.

Configure NetRanger to Send Files to the FTP Server

To configure NetRanger to send files to the FTP server, follow these steps:

Step 1 On the Director, start nrConfigure by clicking Configure on the Security menu.

Step 2 Double-click the name of your Director machine on the displayed list.

Step 3 Double-click the currently applied configuration version (the one that is bolded).

Step 4 Double-click Data Management.

The Data Management dialog box opens.

Step 5 Click the Database tab.

Step 6 Type the FTP Server username and password for User 2.

Step 7 For Auxiliary 1, type in ftp.

Step 8 For Auxiliary 2, type in the name or IP address of the FTP server.

Step 9 Optionally, you can type a directory name for Auxiliary 3.

Note You will not need to perform Step 9 if you set a base FTP directory when you configured the FTP server software. Leave the field blank if you want to use the default home directory of the FTP user login. Otherwise, the file transfer mechanism will write to the directory specified in this field.

Step 10 Under Database Shell Scripts, click the Run field and type /usr/nr/bin/sap/load_run.ftp.sh as the name of the script.

Step 11 Click the Triggers tab.

Step 12 Click each Condition Name that begins with "Report_" one at a time and click Delete.

Note If the Condition Name "OracleInfoUpdate" exists, delete it also.

Step 13 Click Add to add a new trigger.

The Add New Trigger dialog box appears.

Step 14 Under Condition Name, type Telemate_SysFiles.

Step 15 Under Directory, type /usr/nr.

Step 16 Under Condition Type, click Idle Time and type 60 in the Minutes field.

Step 17 Click the Actions tab.

Note Leave Action Type as Block/Archive (the default).

Step 18 Under Script, type:

/usr/nr/bin/sap/pushSystemFiles.sh

Step 19 Under Parameters, type:

/usr/nr/var/messages.sapd

Step 20 Click OK.

Step 21 Click the trigger titled "Oracle_Load" and click Modify.

Step 22 Change the Condition Name from Oracle_Load to Telemate_Load.

Step 23 Click OK.

Step 24 Select the Condition Name "Telemate_SysFiles" and click Up until this trigger is above the Condition Name "Telemate_Load."

Step 25 Click OK to close the Data Management dialog box.

Step 26 Select the newly created transient version of the configuration and click Apply.

Modifying List Items in nrConfigure

If you want to edit or modify a list item in any nrConfigure panel, you must first select the item and then click Modify.

Upgrading Signatures

When you upgrade a Sensor's signature list by installing a NetRanger update or upgrading to a new version, the next time you use nrConfigure to manage that Sensor, nrConfigure informs you that the configuration files on the Sensor are different than the ones currently stored on the Director.

To update the configuration files stored on the Director, click Yes to download the new signature files from the Sensor. This will update nrConfigure's database of stored configuration files.

To verify that the new signatures are present, double-click Intrusion Detection under the Sensor's bolded (current) configuration version. Then click Modify Sensor and scroll to the bottom of the list. The new signatures appear at the bottom of the list.

Note The currently applied version has the new signatures and any version created from this version will have the signatures, but older versions of the configuration files will not have the new signatures. These older configurations will either have to be deleted or manually updated.

A few things to be aware of follow:

    1. The update or new version must be applied on the Director and each of the Sensors. Applying the update or new version only on the Director might add the signatures to the packetd.conf files of Sensors using profiling, but because the Sensors have not been updated to the new version they will ignore the new signature entries.

    2. You must click Yes when prompted to download the configuration changes.

    3. Older configurations will not have the new signatures.

    4. When Modify Sensor is selected, the new signatures will appear at the bottom of the list. When the update or new version is installed, the new signatures are added to the bottom of the packetd.conf file. Only if the window is sorted by Signature ID field or if profiling is used will the signatures be sorted by Signature ID.

The following notes have to do with profiling:

Example: If you have profiling on and have disabled Windows NT signatures, then any new Windows NT signatures will not be added to the packetd.conf file.
A script compares the entries between a template signatures file and the currently applied signatures file, and makes sure that these two lists correspond. The script cannot identify new signatures, it only looks for which signatures are not currently contained in the file.
The script then checks to see if the missing signature should be added based on what profiles were applied. In the past, some users disabled signatures by physically removing them from the /usr/nr/etc/packetd.conf file; the script now puts the deleted signatures back into the packetd.conf file, which is not what some users might expect.
To disable signatures, you need to use either profiling or set the signature severity levels to zero. Manually deleting signatures is no longer allowed.

NetRanger Signature Updates

NetRanger customers can now use the Proactive Field Notice Tool on CCO to receive updates on changes to NetRanger Signatures.

This section discusses the following topics:

Creating a Signature Update

To create a signature update, follow these steps:

Step 1 Go to the following URL:

http://www.cisco.com/warp/customer/770/index.shtml

Step 2 Click Proactive Field Notice.

Step 3 Click Create New Alert Agent.

Step 4 Under Agent Name, type a name for the agent.

Step 5 Click a product name in the Products drop-down list.

Step 6 Click either fax or e-mail under Delivery Method.

Step 7 Confirm that your User Information is correct.

Step 8 Click Create Agent.

Step 9 Click OK.

Editing or Deleting a Signature Update

To edit or delete the agent, select the name of the agent and follow these steps:

Step 1 Go to the following URL:

http://www.cisco.com/warp/customer/770/index.shtml

Step 2 Click Proactive Field Notice.

Step 3 Click the name of the agent you want to edit or delete.

Step 4 If you are editing the agent, enter your changes and click Update Agent.

If you are deleting the agent, click Delete Agent.

Step 5 Click OK.

Configuring the IDS Feature of the Cisco Secure Integrated Software Feature Set on the NetRanger Director

To allow communication between the NetRanger Director and Cisco routers running the Cisco Secure Intrusion Detection System feature of the Cisco Secure Integrated Software feature set, follow these steps:

Step 1 On the Director, start nrConfigure by clicking Configure on the Security menu.

Step 2 Double-click the name of your Director machine on the displayed list.

Step 3 Double-click the currently applied configuration version (the one that is bolded).

Step 4 Double-click System Files.

Step 5 Double-click Hosts.

The Hosts dialog box opens.

Step 6 Click Add and type the host name, host ID, and organization ID for the IDS router.

Step 7 Click OK.

The Hosts dialog box closes.

Step 8 Double-click Routes.

The Routes dialog box opens.

Step 9 Click Add and type in the route to the IDS router.

Step 10 Click OK.

The Routes dialog box closes.

Step 11 Select the newly created transient version of the configuration and click Apply.

Changing the Default Port for postofficed Communication

The default port that the postofficed service uses for NetRanger communication is UDP 45000. You have the following options for changing the default UDP port:

Change the Default Port on all NetRanger Hosts

To change the postofficed UDP port on all NetRanger hosts, follow these steps:

Step 1 On each NetRanger host, use a text editor to change the following line in the /usr/nr/etc/postofficed.conf file:

PortNumberOfNetCommmunications port_number

where port_number is the number of the UDP port that you want to use for NetRanger communication.

Step 2 On each NetRanger host, use a text editor to change each NetRanger host's UDP port number designation in the /usr/nr/etc/routes file. For example:

director.cisco 1 10.1.1.1 port_number 1 5
sensor.cisco 1 10.1.1.100 port_number 1 5

where port_number is the number of the UDP port that you want to use for NetRanger communication.

Note Make sure that the UDP port numbers in the preceding step matches the UDP port number established in Step 1.

Step 3 On each NetRanger host, stop and restart NetRanger services with the following commands:

nrstop
nrstart

Step 4 On each Director, use the nrconns command to ensure that communications are up and running between the Director and all Sensors.

Step 5 On the Director interface, click the Director icon and click Configure on the Security menu.

nrConfigure displays a message stating that the postofficed.conf and routes files have changed, and prompts you to download the files.

Step 6 Click Yes to download the current files.

Step 7 Click Close.

Step 8 Select each Sensor from nrConfigure's list and download their configuration files, repeating Steps 6 and 7.

Step 9 Click Exit on the File menu to close nrConfigure.

Step 10 Repeat Steps 5 through 9 for each Director.

Change the Default Port on the Director Only

To change the postofficed UDP port on the Director only, follow these steps:

Step 1 On the Director, use a text editor to add the following token in the /usr/nr/etc/postofficed.conf file:

PortNumberOfNetCommmunications port_number

where port_number is the number of the UDP port that you want to use for NetRanger communication.

Step 2 On the Director, use a text editor to change the Director's UDP port number designation in the /usr/nr/etc/routes file. For example:

director.cisco 1 10.1.1.1 port_number 1 5

where port_number is the number of the UDP port that you want to use for NetRanger communication.

Note Make sure that the UDP port number in the preceding step matches the UDP port number established in Step 1.

Step 3 On each NetRanger host communicating with the Director, use a text editor to change the Director's UDP port number designation in the /usr/nr/etc/routes file. For example:

director.cisco 1 10.1.1.1 port_number 1 5

where port_number is the number of the UDP port that you want to use for NetRanger communication.

Note Make sure that the UDP port number in the preceding step matches the UDP port number established in Step 1.
Caution To make sure communications still operate properly, only change the Director's UDP port designation. Changing the Sensor's (or other Director's) UDP port designation may cause a communication breakdown between NetRanger hosts.
Caution If you are using multiple routes between Sensors and Directors, change the UDP port designation on the direct routes between a Sensor and Director. For more information on routes, refer to the "routes" section of NetRanger Internal Architecture.

Step 4 On each NetRanger host, stop and restart NetRanger services with the following commands:

nrstop
nrstart

Step 5 On the Director, use the nrconns command to ensure that communications are up and running between the Director and all NetRanger hosts.

Step 6 On the Director interface, click the Director icon and click Configure on the Security menu.

nrConfigure displays a message stating that the postofficed.conf and routes files have changed, and prompts you to download the files.

Step 7 Click Yes to download the current files.

Step 8 Click Close.

Step 9 Select each Sensor from nrConfigure's list and download their configuration files, repeating Steps 7 and 8.

Step 10 Click Exit on the File menu to close nrConfigure.

Note If you want to make further changes to configuration files, be sure to stop and restart nrConfigure.

Step 11 If there are any other Directors communicating with the modified Director, follow Steps 6 through 10 on each Director.

Change the Default Port on a Sensor Only

To change the postofficed UDP port on a Sensor only, follow these steps:

Step 1 On the Sensor, use a text editor to add the following token in the /usr/nr/etc/postofficed.conf file:

PortNumberOfNetCommmunications port_number

where port_number is the number of the UDP port that you want to use for NetRanger communication.

Step 2 On the Sensor, use a text editor to change the Sensor's UDP port number designation in the /usr/nr/etc/routes file. For example:

sensor.cisco 1 10.1.1.1 port_number 1 5

where port_number is the number of the UDP port that you want to use for NetRanger communication.

Note Make sure that the UDP port number in the preceding step matches the UDP port number established in Step 1.

Step 3 On each NetRanger host communicating with the Sensor, use a text editor to change the Sensor's UDP port number designation in the /usr/nr/etc/routes file. For example:

sensor.cisco 1 10.1.1.1 port_number 1 5

where port_number is the number of the UDP port that you want to use for NetRanger communication.

Note Make sure that the UDP port number in the preceding step matches the UDP port number established in Step 1.
Caution To make sure communications still operate properly, only change the Sensor's UDP port designation. Changing the Director's (or other Sensor's) UDP port designation may cause a communication breakdown between NetRanger hosts.
Caution If you are using multiple routes between Sensors and Directors, change the UDP port designation on the direct routes between a Sensor and Director. For more information on routes, refer to the "routes" section of the NetRanger Internal Architecture.

Step 4 On each NetRanger host, stop and restart NetRanger services with the following commands:

nrstop
nrstart

Step 5 On the Director, use the nrconns command to ensure that communications are up and running between the Director and all NetRanger hosts.

Step 6 On the Director interface, click the Director icon and click Configure on the Security menu.

nrConfigure displays a message stating that the postofficed.conf and routes files have changed, and prompts you to download the files.

Step 7 Click Yes to download the current files.

Step 8 Click Close.

Step 9 Select the modified Sensor from nrConfigure's list and download their configuration files, repeating Steps 7 and 8.

Step 10 Click Exit on the File menu to close nrConfigure.

Note If you want to make further changes to configuration files, be sure to stop and restart nrConfigure.

Step 11 If there are any other Directors communicating with the modified Sensor, follow Steps 6 through 10 on each Director.

Documentation Updates

The following errors were noted in Chapter 3, "Installation and Configuration" of the NetRanger User Guide Version 2.2.1:

    1. In the section, "Assemble the Sensor," part of the text under Figure 3-1 appears incorrectly. In the second bullet under "For a FDDI network configuration," ptpci0 should be ptpci.

    2. In the section, "Initialize the Sensor," the sysconfig-sensor main menu listed under Step 2 is incorrect, as the COM1 port option has been removed. The menu should appear as follows:

    NetRanger Sensor Initial Configuration Utility
 
Choose a value to configure one of the following parameters:
 
1 - IP Address
2 - IP Netmask
3 - IP Hostname
4 - Default Route
5 - Network Access Control
6 - NetRanger Communications Infrastructure
7 - System Date, Time and Timezone
8 - Passwords
x - Exit
 
Selection:

    3. In the section, "Initialize the Sensor," Table 3-1 is incorrect, as the COM1 port option has been removed in sysconfig-sensor. Disregard this row and renumber the options in the table starting with "Network Access Control" as option number 5, and so on through "Passwords," which is option number 8.

    4. In the section, "Complete the Sensor Configuration," the text under Step 12 describing legal device names appears incorrectly. The text should read:

Legal device names are /dev/spwr0 (Ethernet/Fast Ethernet), /dev/ptpci (FDDI), and /dev/mtok36 (Token Ring).

    5. In the section, "Building a Sensor," Step 4 should read:

If the CD-ROM is not listed as a mounted filesystem, manually mount the CD-ROM drive:
mount -F hsfs -r /dev/dsk/c0d0s0 /mnt
where /dev/dsk/c0d0s0 is the device name of the system's CD-ROM drive and /mnt is an existing mount point.




 Recommended Keyboards and Monitors

 
 Some keyboards and monitors are not compatible with the Sensor. This incompatibility could cause the Sensor not to boot properly. Cisco Systems recommends that you use the following keyboards and monitors with the Sensor:








Caution The NetRanger Sensor will not function properly with some HP keyboards and with IBM model G50 monitors. 









Note This section will be updated as more monitors and keyboards are discovered with incompatibilities to the NetRanger Sensor.




 Changes in NetRanger Version 2.2.1

 
 This section discusses the following topics:



 Token Ring Adapter Device Name Change


 For Token Ring Sensors with the part numbers NRS-TR-DM and NRS-TR the adapter device name is still mtok. For Token Ring Sensors with the part number IDS-4220-TR the adapter device name has changed from mtok to mtok36.


 nrConfigure Enhancements


 The following enhancements have been made in the NetRanger version 2.2.1 nrConfigure tool:



 Installation Utilities Enhancements


 The following enhancements have been made to the NetRanger version 2.2.1 installation utilities:



 Director Enhancements


 This section lists the enhancements made to the NetRanger version 2.2.1 Director, and includes the following topics:



 HP OpenView 6.x Support


 The NetRanger version 2.2.1 Director now supports HP OpenView 6.0, 6.01, and 6.10. 







Note HP OpenView 6.x has different menu functions than HP OpenView 4.x/5.x. Refer to Table 2 found later in this document for a list of menu changes that affect NetRanger Director operation.




 During installation the following message appears for machines with OpenView 6.01 or 6.10, but the installation program assumes a yes answer and continues the installation without user intervention:


 Warning! HP OpenView version 06.XX is not supported!


 Continue anyway (y/n)?


 The XX represents 01 or 10 for 6.01 or 6.10.


 Solaris 2.7 Support


 The NetRanger version 2.2.1 Director now supports Solaris 2.7.


 During installation the following message appears for machines with Solaris 2.7, but the installation program assumes a yes answer and continues the installation without user intervention:


 Warning! NetRanger does not support version 2.7 of Solaris!


 Continue anyway (y/n)?


 Multi-User Support


 The NetRanger version 2.2.1 Director now supports access to NetRanger data by users other than user netrangr. For more information, refer to Chapter 9, "Advanced Director Functions" of the NetRanger User Guide Version 2.2.1.


 Cisco Secure Integrated Software Feature Set Support


 The Director can accept alarms from a Cisco IOS router running the Intrusion Detection System feature of the Cisco Secure Integrated Software feature set. Alarms deriving from the Cisco Secure Integrated Software feature set appear in an IOS-IDS alarm submap.


 New and Changed Director Menu Functions


 The following list describes new and changed Director menu functions in NetRanger version 2.2.1:



  

Table 1: Director Menu Name Changes




Previous Menu Name
Current Menu Name



 Security>Show>Context


 Security>Show>Context Buffer




 Security>Save to File


 Security>Create>Text File




 Security>Advanced>Shunning>Enable


 Security>Advanced>Shunning>Enable Future Shuns




 Security>Advanced>Shunning>Disable


 Security>Advanced>Shunning>Disable Future Shuns















  

Table 2: HP OpenView 4.x/5.x to 6.x Menu Changes




HP OpenView 4.x/5.x Menu Name
HP OpenView 6.x Menu Name



 Map>Maps>Describe/Modify


 Map>Properties




 Map>Submap>Describe/Modify


 Map>Submap>Properties




 Fault>Events


 Fault>Alarms




 Edit>Describe/Modify


 Edit>Object Properties




 Locate>Objects


 Edit>Find>Object




 Edit>Hide


 View>Hidden Objects>Hide




 Edit>Show Hidden Objects


 View>Hidden Objects>Show Hidden














 Japanese Solaris 2.6 Support for NetRanger


 NetRanger version 2.2.1 now supports Japanese Solaris 2.6 support for the Director. You will need to install the HP OpenView Network Node Manager 5.01 with patch PSOV_02090.


 Network Security Database (NSDB) Enhancements


 The NetRanger version 2.2.1 NSDB has a substantially improved look-and-feel and more intuitive navigation.


 New Signatures


 The following Signatures are new in NetRanger version 2.2.1:



 BorderGuard Support


 In NetRanger version 2.2.1, the following BorderGuard router support is present:



 Upgrading Sensors

 
 The NetRanger CD contains software to install the NetRanger Sensor application on either an x86 or SPARC Solaris workstation running Solaris version 2.5.1 or 2.6.


 To install the Sensor software, follow these steps:



Step 1	 Log on to the Sensor as user root.



Step 2	 Insert the CD-ROM in the CD-ROM drive.



Step 3	 Manually mount the CD-ROM drive:


mount -F hsfs -r /dev/dsk/c0d0s0 /mnt 
 

 where /mnt is an existing mount point.







Caution You must mount the CD-ROM manually, because VOLD will fail to correctly mount it. 





Step 4	 Change directories to the mount point with the cd command.



Step 5	 To install NetRanger, type:


./install

 Related Documentation

 
 Use these release notes in conjunction with the following documents:



 Obtaining Documentation

 
 World Wide Web


 You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com,  http://www-china.cisco.com,  or http://www-europe.cisco.com.
  

 Documentation CD-ROM


 Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.


 Ordering Documentation


 Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
  

 Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).


 Obtaining Technical Assistance

 
 Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.


 Cisco Connection Online


 Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.


 CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.


 Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.


 You can access CCO in the following ways:



 You can e-mail questions about using CCO to cco-team@cisco.com.


 Technical Assistance Center


 The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.


 To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.


 To contact by e-mail, use one of the following:


  



Language
E-mail Address



 English


 tac@cisco.com




 Hanzi (Chinese)


 chinese-tac@cisco.com




 Kanji (Japanese)


 japan-tac@cisco.com




 Hangul (Korean)


 korea-tac@cisco.com




 Spanish


 tac@cisco.com




 Thai


 thai-tac@cisco.com














 In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
  

 Documentation Feedback


 If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.


 You can e-mail your comments to bug-doc@cisco.com.


 To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:


 Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883


 


 


 


 


 


 


 


 


 


 


 


 


 


 


 


 This document is to be used in conjunction with the NetRanger User Guide Version 2.2.1 publication.


 Access Registrar, AccessPath, Any to Any, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, ConnectWay, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, Kernel Proxy, MGX, MultiPath Data, MultiPath Voice, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, ScriptShare, Secure Script, ServiceWay, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, ViewRunner, Virtual Loop Carrier System, Virtual Service Node, Virtual Voice Line, VisionWay, VlanDirector, Voice LAN, WaRP, Wavelength Router, Wavelength Router Protocol, WebViewer, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any of its resellers. (9912R)


 Copyright © 2000, Cisco Systems, Inc.


 All rights reserved.





hometocprevnextglossaryfeedbacksearchhelp


Posted: Wed Jul 19 14:18:41 PDT 2000

Copyright 1989-2000©Cisco Systems Inc.