VLAN Diagnostic Tools Guide

VLAN Diagnostic Tools Guide
Notice
Notice
Cabletron Systems reserves the right to make changes in specications and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, rmware, or software described in this manual is subject to change without notice. IN NO EVENT SHALL CABLETRON SYSTEMS BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF CABLETRON SYSTEMS HAS BEEN ADVISED OF, KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES.
Copyright September, 1998 by: Cabletron Systems, Inc. P.O. Box 5005 Rochester, NH 03866-5005 All Rights Reserved Printed in the United States of America Order Number: 9032369-02
Cabletron Systems, SPECTRUM, and SecureFast are registered trademarks and SmartSwitch is a trademark of Cabletron Systems, Inc. All other product names mentioned in this manual may be trademarks or registered trademarks of their respective companies.
Notice
FCC Notice
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment uses, generates, and can radiate radio frequency energy and if not installed in accordance with the operators manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause interference in which case the user will be required to correct the interference at his own expense. WARNING: Changes or modications made to this device which are not expressly approved by the party responsible for compliance could void the users authority to operate the equipment.
VCCI Notice
This equipment is in the 1st Class Category (information equipment to be used in commercial and/or industrial areas) and conforms to the standards set by the Voluntary Control Council for Interference by Information Technology Equipment (VCCI) aimed at preventing radio interference in commercial and/or industrial areas. Consequently, when used in a residential area or in an adjacent area thereto, radio interference may be caused to radios and TV receivers, etc. Read the instructions for correct handling.
Industry Canada Notice

This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications. Le prsent appareil numrique nmet pas de bruits radiolectriques dpassant les limites applicables aux appareils numriques de la class A prescrites dans le Rglement sur le brouillage radiolectrique dict par le ministre des Communications du Canada.
ii
Contents
Standard Command Line Arguments............................................................................2 Das.......................................................................................................................................4 DirGrep...............................................................................................................................8 DirStat ...............................................................................................................................12 GetTable............................................................................................................................17 MibPoller ..........................................................................................................................23 MibSet ...............................................................................................................................31 ShowVST ..........................................................................................................................34 TraceCnx ...........................................................................................................................38
iii
Contents
iv
Chapter 1
Diagnostic Tools
This chapter contains information about the SPECTRUM VLAN Diagnostic Tools. These tools help you to identify and resolve problems in the SFS network. They also give troubleshooters insight into the SFS system, by providing data that denes the state of the SecureFast Switch (SFS) network. Each command (except MibSet) offers two interfaces: Command Line Interface (CLI) - Runs faster but is less user-friendly Graphical User Interface (GUI) - Runs slower but is more user-friendly
The Diagnostic Tools have been ported and tested in the following operating systems: Windows NT Windows 95 Linux Solaris
The Diagnostic Tools are: Das DirGrep DirStat GetTable MibPoller MibSet ShowVST Discovers and displays all switches in a cloud. Searches the virtual directory for alias and node information. Searches for and identies any errant directory entries. Queries switches for a table dened by the specied atf le or base OID. Polls one or more switches for one or more MIB leaves. Sets one or more values for a single instance in a single MIB. Note that there is no GUI MibSet. Displays the virtual spanning tree.
1-1
Diagnostic Tools
TraceCnx
Searches for and displays all connection information for a given SA/DA address.
CAUTION
Use these tools with caution. Some of these tools allow you to manage the switch in ways that could potentially interject network problems. You should use these tools only when you are comfortable with their operation.
Standard Command Line Arguments

A subset of the following command line arguments are common to the Diagnostic Tools. Some arguments are mandatory for certain tools, some are optional, and some do not apply at all. These arguments ne tune a tools operation in a uniform manner.
-a
Use -a with -s to force a topology discovery. When used, the Diagnostic Tool will perform its task on all switches that were discovered. For more information about topology discovery, see the Das Diagnostic Tool.
-c <conguration lename>
For tools that use a conguration le, use -c to specify the conguration le name.
-h
-h displays the tools usage summary. This display includes a synopsis, a list of all mandatory command line input along with a brief description of each, and a list of all optional inputs along with a brief description. For optional command line arguments, the default value is displayed (where applicable).
-l <IP list lename>
-l is an alternative to using the -s argument. When using -l, specify the name of a le that contains a list of switches on which the Diagnostic Tool should act.
-n <SNMP community name>
Use -n to specify the SNMP community name for switches on which a Diagnostic Tool will act.
-o <output lename>
For tools that create output les (error logs, summary les), use -o to specify the output le name.
1-2
Diagnostic Tools
-rawTime
The default formatting for TimeTick elds is a calendar date and time stamp. This option disables the date format and displays TimeTick elds as days/hours/minutes/seconds.
-rt <# of retries in case of SNMP failure>
Use -rt to specify how many times the tool should re-attempt an SNMP request that failed.
-s <IP or hostname>
-s species which switch the tools should act upon. Specify either the switchs IP address or its host name.
-throttle <max # SNMP requests/second>
Use -throttle to control the management load placed upon the switches. When a Diagnostic Tool needs to query an SNMP MIB, the value of -throttle is used to throttle the rate at which SNMP requests are sent to the switches.
-to <SNMP time-out>
Use -to to specify how long the tool should wait for a response to an SNMP request. If this wait expires without a response, the tool records a timeout error and continues, if possible.
-v
-v displays the tools version.
1-3
Diagnostic Tools
Das
Das attempts to discover all switches in the fabric, given one switchs IP address as the seed. During this process, the following information is collected about the switches: It records the switchs system description, which consists of the switchs platform type, the switchs image name (version), and the images date and time of linkage. It determines which switches are attached to each other by INB connections in the same hub and groups them with a Das-generated chassis identication number. It records the switchs Ethernet address. It records all adjacency information for each switch. By default, this information is not displayed. Instead, you may choose to view it using the -long option.
The display consists of a listing of the following information for each switch (one switch per line): IP address Ethernet address Chassis number Chassis slot number the switch occupies in the chassis System description
Optionally, adjacency information, consisting of a neighbors IP address, local and remote port numbers and the link media type (INB, Ethernet, FDDI, etc.), can be viewed one neighbor per line following each switch. Switch displays are separated by lines indicating hub grouping. You may also choose to have all switch IP addresses written to a le, using the -o option, to be imported by other tools, using their standard -l argument, where applicable.
Syntax
Das -s X1 [options]
Description
-s X1
X1 is the IP address or host name of the seed switch in the cloud.
1-4
Diagnostic Tools
Options
-long X2
Displays neighbor information. The default is true.

-n X3
X3 is the community string. The default is public.

-o X4
X4 is the name of the le where the output is written.

-rt X5
X5 is the number of times to retry in case of SNMP failure. The default is 1.

-to X6
X6 is the SNMP timeout (in seconds). The default is 2.

-throttle X7
X7 is the number of SNMP requests per second. The default is 20.
1-5
Diagnostic Tools
Example
C:\sfstools\bin>das -s 134.146.176.3 -n public
Discovering cloud...done. Discovery took 8 seconds. Discovered 17 switches. -----------------------------------------------------------------------------------------134.146.176.3 0:0:1d:21:46:87 Hub-0 Slot-3 Cabletron 9E423-24 Rev 05.00.01 134.146.176.5 0:0:1d:24:41:51 Hub-0 Slot-5 Cabletron 9F426-02 Rev 03.03.01 134.146.176.6 0:0:1d:0:8:41 Hub-0 Slot-6 Cabletron 9H422-12 Rev 05.00.01 -----------------------------------------------------------------------------------------134.146.176.21 0:0:1d:62:3b:6a Hub-1 Slot-1 Cabletron 9A426-XX Rev 03.02.04 134.146.176.23 0:0:1d:37:fe:df Hub-1 Slot-3 Cabletron 9H422-12 Rev 03.03.01 134.146.176.24 0:0:1d:45:1b:5f Hub-1 Slot-4 Cabletron 9E423-36 Rev 03.03.01 134.146.176.26 0:0:1d:86:76:c Hub-1 Slot-6 Cabletron 9F426-03 Rev 03.03.01 -----------------------------------------------------------------------------------------134.146.176.41 0:0:1d:62:3b:71 Hub-2 Slot-1 Cabletron 9A426-XX Rev 03.02.04 134.146.176.42 0:0:1d:4a:5:2e Hub-2 Slot-2 Cabletron 9A426-XX Rev 03.02.04 134.146.176.43 0:0:1d:37:de:2f Hub-2 Slot-3 Cabletron 9H422-12 Rev 03.03.01 134.146.176.45 0:0:1d:37:13:df Hub-2 Slot-5 Cabletron 9F426-03 Rev 03.03.01 134.146.176.49 0:0:1d:37:bd:f7 Hub-2 Slot-9 Cabletron 9E423-36 Rev 03.03.01 -----------------------------------------------------------------------------------------134.146.176.31 0:0:1d:2f:b6:3e Hub-3 Slot-1 Cabletron 9A426-XX Rev 03.02.04 134.146.176.32 0:0:1d:43:d8:62 Hub-3 Slot-2 Cabletron 9A426-XX Rev 03.02.04 134.146.176.33 0:0:1d:2f:dd:af Hub-3 Slot-3 Cabletron 9H422-12 Rev 03.03.01 134.146.176.34 0:0:1d:37:fe:ef Hub-3 Slot-4 Cabletron 9H422-12 Rev 03.03.01 134.146.176.37 0:0:1d:37:13:f4 Hub-3 Slot-7 Cabletron 9F426-03 Rev 03.03.01
1-6
Diagnostic Tools
GUI Das
Starting the GUI Das

To start Das: 1. At c:\sfstools\bin> , enter toolbox and then press the Return key. 2. In the Seed Switch box, enter the IP address of the seed switch. 3. In the Community box, enter the same community name. 4. Select the Go icon.
1-7
Diagnostic Tools
DirGrep
DirGrep can be used to search through an SFS virtual directory for a particular end user, device. The search criteria can be one of the following: A node (specied by Ethernet address) An alias (specied by hostname, IP, NetBIOS, or AppleTalk address)
All information that is found to be related to the given search criteria is displayed. Each entry in the display consists of the following: Switch IP on which the directory resolve was done Switch IP on which the criteria was locally resolved Port number Ethernet address Any alias information found pertaining to the criteria Node Ages and States Alias Ages and States
Dirgrep is useful for nding a particular users location within the switch fabric and for troubleshooting directory-related problems pertaining to the criteria. Whether or not problems are found, you can choose to have dirgrep delete all directory information found pertaining to the specied search criteria.
Syntax
DirGrep { -s X1 | -l X2 } { -ip X3 | -node X4 | -netbios X5 | -atalk X6 } [ options ]
Description
-s X1

-l X2
X2 is the name of a list of IP addresses to be read.

-ip X3
Searches for alias information with X3 being an IP address.

-node X4
Searches for alias information with X4 being a MAC address.

-netbios X5
Searches for alias information with X5 being a NetBIOS address.
1-8
Diagnostic Tools
-atalk X6
Searches for alias information with X6 being an AppleTalk address.
Options
-k
Removes all information from directory regarding an address.

-a
Will discover all switches in the cloud. This option is only meaningful when using the -s ag.
-n X7

-throttle X8

-to X9

-rt X10
X10 is the number of times to retry in case of an SNMP failure. The default is 1.
-rawTime
Allows the user to display TimeTick elds without using Date values.
-lof X11
X11 is the name of the le where the list of switches this program used will be written.
1-9
Diagnostic Tools
Example
C:\sfstools\bin>dirgrep -s 134.146.176.3 -a -n public -ip 134.146.176.3
Discovering switches...done. Cloud has 17 switches. ***************************************************************************************** Alias Info: ----------------------------------------------------------------------------------------Src_Switch Home_Switch Port Node Node_Age Alias_Type ----------------------------------------------------------------------------------------134.146.176.3 134.146.176.3 39 0:0:1d:21:46:87 08/04/98_10:08:00 IP ***************************************************************************************** Node Info: ----------------------------------------------------------------------------------------Src_Switch Home_Switch Port Node Node_Age Alias_Type ----------------------------------------------------------------------------------------134.146.176.42 134.146.176.3 160 0:0:1d:21:46:87 07/31/98_16:17:29 VLAN 134.146.176.41 134.146.176.3 10 0:0:1d:21:46:87 07/31/98_16:17:31 VLAN 134.146.176.3 134.146.176.3 39 0:0:1d:21:46:87 08/04/98_10:08:01 VLAN
GUI DirGrep
1-10
Diagnostic Tools
Starting the GUI DirGrep

To start DirGrep: 1. From the toolboxs Tool Tray, select DirGrep. 2. Select a Protocol (Ethernet, IP, Hostname, AppleTalk, or NetBIOS). 3. In the Address box, enter the address to be searched for. 4. Select the Go icon.
1-11
Diagnostic Tools
DirStat
DirStat searches for and identies certain problems within the SFS virtual directory. It does this by collecting all directory information from the alias and node tables in the switches. Then, it examines this information while searching for the following error conditions:
Alias conditions
Is an alias bound to multiple base addresses? Does an alias reside locally in multiple locations? Was an alias resolved to more than one switch? Is VLAN information for any switch inconsistent with another switch?
Node conditions
Does a node reside locally in multiple locations? Was a node resolved to more than one switch? Does a node reside locally on a non-access port?
If any of these problems is discovered, a description of the problem and the directory entry (or entries) involved are logged to a le. Some basic directory statistics are also displayed: The number of end users in the fabric The number of ports that they are located on The number of nodes in the network
You may choose to have DirStat delete all nodes associated with the detected problems.
Syntax
DirStat { -s X1 | -l X2 } [ options ]
Description
-s X1

-l X2
1-12
Diagnostic Tools
Options
-k
Deletes all nodes associated with error conditions.

-skipa
Skips all alias processing.

-skipn
Skips all node processing.

-ipOnly
Skips non-IP alias processing.

-long
Writes all directory info to the log, instead of just errors.

-o X3
Writes directory info to a le named X3. The default is dirstat.log.

-a
-n X4

-throttle X5

-to X6

-rt X7

-rawTime
-lof X8
1-13
Diagnostic Tools
Example
C:\sfstools\bin>dirstat -s 134.146.176.3 -a -n public
Discovering switches...done. Cloud has 17 switches. Collected data from 17 of 17 switches for 164 aliases and 226 nodes. These addresses are located on 140 different ports throughout the SFS switch fabric. Starting inquiries. 0 directory related problems were detected in all. See 'dirstat.log.'
1-14
Diagnostic Tools
GUI DirStat
1-15
Diagnostic Tools
Starting the GUI DirStat

To start DirStat: 1. From the Tool Tray, select DirStat. 2. Select the Go icon.
1-16
Diagnostic Tools
GetTable
GetTable allows the user to get any table in an SNMP-manageable device(s) by specifying an ATF file or the tables base OID. With an OID, GetTable displays raw output. With an ATF file or prole, GetTable displays formatted output, along with the column headings, enumeration label substitutions, column width settings, and user-selected elds.
GetTable displays the table to standard output (usually the screen). There are options for sending database-friendly les to either the screen or a le. GetTable allows the user to specify a list of devices from which to retrieve the MIB table. GetTable can discover an SFS cloud and then retrieve the tables from all the switches belonging to it.
Syntax
GetTable { -s X1 | -l X2 } { -prof X3 | -atf X4 | -oid X5 } [ options ]
Description
-s X1

-l X2

-prof X3
X3 is the name of the prole for the desired MIB.

-atf X4
X4 is the name of the ATF le that denes a MIB branch. This is an old version of -prof. The -prof argument should be used instead of the -atf argument, as it is deprecated.
-oid X5
X5 is the base SNMP OID for the desired MIB branch.
1-17
Diagnostic Tools
Options
-vertical
Causes table rows to be displayed vertically.

-cFilter X6
X6 is a comma-separated list of eld names to lter from the MIB.

-showKeys
Shows the SNMP instance key for each row.

-dbof X7
Writes database import-friendly output to X7.csv.

-dbo
Writes database import-friendly output to screen.

-a
-n X8

-throttle X9

-to X10

-rt X11
-rawTime
-lof X12
1-18
Diagnostic Tools
Example
C:\sfstools\bin>gettable -s 134.146.176.3 -a -n public -prof std.sfs.sys.SystemConfig Discovering switches...done. Cloud has 17 switches. Profile found at systemresource:/ZIP7/+/profiles/std/sfs/sys/SystemConfig.prof Getting data from 17 devices... ***************************************************************************************** 134.146.176.43: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:58 07/31/98_15:27:58 ***************************************************************************************** 134.146.176.6: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 08/03/98_14:41:26 08/03/98_14:41:26 ***************************************************************************************** 134.146.176.37: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:27 07/31/98_15:27:27 ***************************************************************************************** 134.146.176.5: -----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:25 07/31/98_15:27:25 ***************************************************************************************** 134.146.176.42: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:20 07/31/98_15:27:20 ***************************************************************************************** 134.146.176.34: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:53 07/31/98_15:27:53 ***************************************************************************************** 134.146.176.3: -----------------------------------------------------------------------------------------
1-19
Diagnostic Tools
SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 08/03/98_17:38:16 08/03/98_17:38:16 ***************************************************************************************** 134.146.176.41: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:23 07/31/98_15:27:23 ***************************************************************************************** 134.146.176.33: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:51 07/31/98_15:27:51 ***************************************************************************************** 134.146.176.32: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:19 07/31/98_15:27:19 ***************************************************************************************** 134.146.176.26: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:21 07/31/98_15:27:21 ***************************************************************************************** 134.146.176.31: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:19 07/31/98_15:27:19 ***************************************************************************************** 134.146.176.23: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:48 07/31/98_15:27:48 ***************************************************************************************** 134.146.176.24: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:38:25 07/31/98_15:38:25 ***************************************************************************************** 134.146.176.45:
1-20
Diagnostic Tools
----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:32 07/31/98_15:27:32 ***************************************************************************************** 134.146.176.49: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:38:48 07/31/98_15:38:48 ***************************************************************************************** 134.146.176.21: ----------------------------------------------------------------------------------------SwId AdminStatus AdminReset OperStatus OperTime LastChange ----------------------------------------------------------------------------------------1 enabled other enabled 07/31/98_15:27:13 07/31/98_15:27:13
1-21
Diagnostic Tools
GUI GetTable
Starting the GUI GetTable

To start GetTable: 1. From the Tool Tray, select GetTable. 2. In the Seed Switch box, enter an IP address. 3. In the Community box, enter a community name. 4. In the Prole box, enter a prole name (or browse for one) or, if a shortcut exists for the desired table, click on the shortcut name. 5. Select the Go icon.
1-22
Diagnostic Tools
MibPoller
MibPoller polls, periodically, a list of switches for the MIB leaves specied in the mandatory conguration le. Each time the switches are polled, the data is tabulated in a master log le. As this master le is written to disk, it is also displayed to standard out. Each log entry includes a date and time of day stamp. If an SNMP request fails for any reason, such as a time-out error, the value(s) for that particular poll is logged as Err. Repeated Err entries for one or more switches usually indicate lack of connectivity to the switches. One conguration le is mandatory. This le (default name is mibPoller.cfg) lists all MIB leaves that are to be polled from the switches. Each listing contains the following: A name describing that MIB leaf The SNMP query method (GET or GET-NEXT) The data type for that leaf The display width The OID for that leaf
Syntax
MibPoller { -s X1 | -l X2 } [ options ]
Description
-s X1

-l X2
Options
-c X3
X3 is the name of the conguration le to use. The default is mibPoller.cfg.

-prof X4
X4 is the name of the prole to use.
1-23
Diagnostic Tools
-dh X5
Displays header every X5 number of rows (for -c) or every X5 number of tables (for -prof). The default is 0.
-o X6
X6 is the name of the master output le. The default is mibPoller.out.

-dbof X7
X7 is the name of a database-friendly output file.

-p X8
X8 is the period at which to poll, in seconds. The default is 10.

-st
Suppresses the totals display.

-t X9
X9 is the number of minutes to run (0 = forever). The default is 0.

-a
-n X10

-throttle X11
-to X12

-rt X13
-rawTime
-lof X14
1-24
Diagnostic Tools
Example
C:\sfstools\bin>mibpoller -s 134.146.176.3 -a -n public -t 0
Discovering switches...done. Cloud has 17 switches. Tue Aug 04 10:28:22 EDT 1998 ----------------------------------------------------------------------------------------Device IP Uptime CnxCnt AgeCnt LNode NCall RNode Alias ResReq ----------------------------------------------------------------------------------------134.146.176.43 07/31/98_15:27:58 14 0 2 1 1 2 1 134.146.176.42 07/31/98_15:27:20 20 0 2 1 22 2 26 134.146.176.41 07/31/98_15:27:23 1963 88919 1 1 217 5 8 134.146.176.6 08/03/98_14:41:26 25 0 3 3 15 19 2580 134.146.176.5 07/31/98_15:27:25 7 0 1 1 0 1 0 134.146.176.37 07/31/98_15:27:27 12 0 1 1 0 1 0 134.146.176.3 08/03/98_17:38:16 24 0 2 1 16 18 330 134.146.176.34 07/31/98_15:27:53 15 0 2 1 2 2 5 134.146.176.33 07/31/98_15:27:51 16 0 3 1 3 3 9159 134.146.176.32 07/31/98_15:27:19 17 0 3 1 2 1 7 134.146.176.31 07/31/98_15:27:19 27 0 1 1 8 6 0 134.146.176.26 07/31/98_15:27:20 10 0 1 1 0 1 0 134.146.176.24 07/31/98_15:38:25 7573 51587 61 1 135 61 20760 134.146.176.23 07/31/98_15:27:48 30 0 2 1 15 17 3 134.146.176.21 07/31/98_15:27:12 4104 9870 1 1 211 20 8 134.146.176.49 07/31/98_15:38:48 7568 65963 76 1 120 76 20678 134.146.176.45 07/31/98_15:27:31 12 0 1 1 0 1 0 ----------------------------------------------------------------------------------------Device IP Uptime CnxCnt AgeCnt LNode NCall RNode Alias ResReq ----------------------------------------------------------------------------------------Totals: 0 21437 216339 163 19 767 236 53565
Tue Aug 04 10:28:34 EDT 1998 ----------------------------------------------------------------------------------------Device IP Uptime CnxCnt AgeCnt LNode NCall RNode Alias ResReq ----------------------------------------------------------------------------------------134.146.176.43 07/31/98_15:27:58 14 0 2 1 1 2 1 134.146.176.42 07/31/98_15:27:20 20 0 2 1 22 2 26 134.146.176.41 07/31/98_15:27:24 1963 88919 1 1 217 5 8 134.146.176.6 08/03/98_14:41:27 25 0 3 1 15 19 2585 134.146.176.5 07/31/98_15:27:25 7 0 1 1 0 1 0 134.146.176.37 07/31/98_15:27:27 12 0 1 1 0 1 0 134.146.176.3 08/03/98_17:38:16 24 0 2 1 16 18 330 134.146.176.34 07/31/98_15:27:53 15 0 2 1 2 2 5 134.146.176.33 07/31/98_15:27:51 16 0 3 1 3 3 9159 134.146.176.32 07/31/98_15:27:20 17 0 3 1 2 1 7 134.146.176.31 07/31/98_15:27:19 27 0 1 1 8 6 0 134.146.176.26 07/31/98_15:27:21 10 0 1 1 0 1 0 134.146.176.24 07/31/98_15:38:25 7573 51587 61 1 135 61 20760 134.146.176.23 07/31/98_15:27:48 30 0 2 1 15 17 3
1-25
Diagnostic Tools
134.146.176.21 07/31/98_15:27:12 4104 9870 1 1 211 20 8 134.146.176.49 07/31/98_15:38:48 7568 65963 76 1 120 76 20678 134.146.176.45 07/31/98_15:27:31 12 0 1 1 0 1 0 ----------------------------------------------------------------------------------------Device IP Uptime CnxCnt AgeCnt LNode NCall RNode Alias ResReq ----------------------------------------------------------------------------------------Totals: 0 21437 216339 163 17 767 236 53570
GUI MibPoller
Starting the GUI MibPoller

To start MibPoller: 1. From the Tool Tray, select MibPoller. 2. In the Cfg File box, enter the name of a conguration le (or browse). 3. In the Poll interval (sec) box, specify the interval between polls. 4. Select the Go icon.
1-26
Diagnostic Tools
GUI MibPoller Fields

The following information briey explains each MibPoller output le eld (listed in alphabetical order).
AgeCnt
The number of aging passes (currently 1 pass equals 100 connections). Each aging pass is made up of smaller (10 at a time) subpasses. Therefore, reaping 100 connections doesn't happen instantaneously. Switches that are constantly aging are an indication that design changes are needed to add alternative paths.
Alias
The number of entries in the alias table (includes everything). Alias represents the layer 3 IDs and VLAN mappings of all users in the node table. The maximum value of the alias table is platform dependent and can be found by searching on the OID: 1.3.6.1.4.1.52.4.2.4.2.2.3.11.18.
ChgCt
The number of times a VSTP "topology change" event occurred. Once the fabric is stable, this number should not increase. If ChgCt is incrementing and Lost count is not, the control channel may be oversubscribed. To verify, examine the switch throttle count (ThCnt).
CnxCnt
The number of bi-directional VLAN connections present in the switch connection table. CnxCnt includes lter connections created for local conversations between users on the same port. If CnxCnt reaches 95% of the connection table capacity, the oldest 100 connection entries will be aged. If connection aging occurs at an excessive rate (for example, a rate of more than 50 per hour) the switch has a fullyutilized connection table and network design changes should be considered to add more possible paths and/or switches. The connection table's capacity is platform dependent and can be viewed by searching on the OID: 1.3.6.1.4.1.52.4.2.4.2.1.3.4.1. SFS 1.8 includes activity-based aging for SS6000/2000 platforms, however this has not been fully tested to date. The CnxCnt attribute yields a -1 for all switch modules operating as Uplink switches.
DBlks
The number of entries in the Destination Blocker Table. Blocked devices are limited to one resolve request per minute. In most cases, the blocker is holding back ARP storms to unresolved devices. If you have many blocked entries (up to 32), there may be a conguration issue, such as secondary IP addresses may need to be added to the alias table. Five minutes of inactivity causes an entry within the Destination Blocker Table to be deleted.
1-27
Diagnostic Tools
Found
Indicates a new switch neighbor, and impacts the ChgCt.

LNode
The number of nodes (MAC addresses) physically connected (or bridged in) to the switch. The maximum value of local nodes on a switch is determined by subtracting the number of nodes reserved for Remotes from the maximum size of the Node table. These quantities are platform dependent. The size of the Node table can be found for any given switch by searching on the OID: 1.3.6.1.4.1.52.4.2.4.2.2.3.11.16. The amount of nodes reserved for remotes can be found by searching on the OID: 1.3.6.1.4.1.52.4.2.4.2.2.3.11.27. Local nodes are not aged.
Lost
Lost indicates a lost switch neighbor, and is related to ChgCt.

MobQuit
The number of times new user messages (NUSent or NASent) have exceeded the retry count without an acknowledgement for all switches in the domain.
NASent
The number of inter-switch "new user" and "new alias" (Layer 3 address) messages sent. This number, used in conjunction with NUSent, usually determines if there much user mobility within the fabric. If it is known that users are not moving and there shouldn't be much user mobility at all, a high NASent count determines that more than one user is trying to use the same Layer 3 address, such as an IP address.
NCall
The number of calls currently being set-up by the switch. One call is always reserved for control messages. This number peaks at switch startup. A daily average of 40 indicates that too many user are attached to that switch or that the users are extremely active and the call processing capabilities of the switch may be exceeded. To verify this condition, execute a GetTable on the CallTableStats.atf le and examine the TotMisses attribute. If this number is high (approximately 1000 TotMisses per day), users should be distributed to other switches.
NUnRes
The number of entries in the "UnResolve Table." The UnResolve Table stores the AO's (addresses) for resolves resulting in a "Resolve Unknown" answer. This table is limited to 128 entries (when this count jumps to 128 or thereabout, there is usually a high level of unresolvable ARP request trafc).
1-28
Diagnostic Tools
This condition is typically caused by either of the following: HP Jet Admin Missing internal and/or external IP network denitions
This attribute ages every 5 minutes based on inactivity.

NUSent
The number of inter-switch "new user" and "new alias" messages sent (Layer 2). This number should approximate the number of local nodes. Numbers exceeding the local node count indicate user mobility. Excessive NUSent counts could indicate that two users are actively transmitting frames with the same MAC address.
NViol
The number of address violations caused by the invalid IP network use as well as port and user restriction violations. The Violation table may be viewed and managed through SPECTRUM VLAN Manager. The Violation Types are: Invalid IP address User restricted Port restricted IP not learned Restricted mobility
ResAck
The number of resolve responses that were ACKs (successful). A resolve will be successful when the fabric knows the destination user.
ResReq
The number of resolve requests issued. Each time a connection is required and the switch does not have information about the destination device, this counter is incremented. ResReq is an indication that an ARLD message has been sent.
RNode
The number of remote nodes (nodes on other switches) learned. RNode represents the cached information about destination devices for the local users. If the Rnode + Lnode counts equals the value of the OID described in LNode, the switch has reached or exceeded its maximum directory size. Additional network analysis is required. Perform a GetTable on the DirStats.atf le and examine the RemotesReplaced attribute. If this attribute is increasing at a rate of 5000/day, the directory has been exceeded and is rolling. Determine whether additional memory may be added to the switch .
1-29
Diagnostic Tools
SBlk
The number of entries in the Source Block Table. Entries in this table are not aged and must be manually removed. Users are entered into the Source Blocker Table based on the following criteria: 250 packets in 1 second or 750 packets in 30 seconds (by default). These parameters are congurable. Source Blocker learn mode allows all switches to identify users exceeding the Source Block broadcast level parameters without preventing the users from communicating. SPECTRUM VLAN Manager should be used to view and manage the Source Blocker Table.
Switch_IP
The IP address of the switch.

ThrotCnt
The number of control messages dropped in order to maintain operation. This is normal in limited numbers. Excessive counts indicate the host CPU is being asked to process more than it can. Possible causes include high ood rates and topology changes. If this condition occurs, perform a GetTable on the Unresolve Table and determine whether IP networks may be dened. Dening IP external or internal IP networks lowers the level of ooding occuring on the SFS control channel.
Uptime
The number of days, hours, minutes, and seconds this switch has been up and running.
VlspCT
The number of times the VLSP topology converged. This number should not change after start-up until new switch neighbors are either added or removed for the domain. This attribute always yields a -1 on a a switch operating in Uplink mode.
1-30
Diagnostic Tools
MibSet
MibSet allows the user to set one or more leaves within the same MIB to userspecied values. This tools arguments facilitate specifying OIDs by breaking them up into multiple components and letting each one be dened separately. From left to right, the components are: 1. The branch (dened with -branch option) is the rst component used in forming the OID for the leaf. 2. The MIBs OID minus the branch. 3. The leafs column number within the MIB. Since this component must be different for each leaf being set, it is specied as the rst parameter to the one, or more, -varbind arguments. 4. The last component is optional. It allows the user to specify the MIB instances OID key (dened with the -key option) that uniquely identies the single instance within the MIB whose leaves are to be set. This component is appended onto each leafs OID. Usually, this option need only be used in the case of multiple-instance MIBs.
Syntax
MibSet { -s X1 | -l X2 } { -oid X3 | -prof X4 } -varbind X51 X52 [ options ]
Description
-s X1

-l X2

-oid X3
X3 is the base OID for all varbinds.

-prof X4
X4 is the prole to use.

-varbind X51 X52
X51 is the leaf (column) number and X52 is the value to assign to the leaf. Notes
1-31
Diagnostic Tools
When using the -oid ag, X5s value must be preceded by one of the supported format descriptors: [i]<int>, [s]<str>, [ip]<ip>, [mac]<enet>, or [h]<hex> The [i] tag can also be specied as a colon/comma delimited range, such as 1:4,7 which would equal 1,2,3,4,7. Examples: -varbind 4 [i]5 -varbind 7 [s]RED_VLAN -varbind 2 [i]3:7,10 -varbind 11 [ip]134.141.43.2 -varbind 2 [mac]0:0:1d:1:2:3
When using the -prof ag, X51 must be the name of the leaf you want to set. If the leaf has an enumeration (such as a verb leaf), you must specify the string version of the enumeration, not the integer version. Example: -prof VlanAPI -varbind VlanName RED_VLAN -varbind Verb add-vlan Leaf name and enumeration values are case sensitive. Do not use spaces within X52.
Options
-key X6
Sets values for varbinds keyed by X6.

-branch X7
X7 is the oid branch to use. The default is 1.3.6.1.4.1.52.4.2.4 .

-a
-n X8

-throttle X9

-to X10

-rt X11
X11 is the number of times to retry in case of SNMP failure. The default is 1.
1-32
Diagnostic Tools
-rawTime
-lof X12
Example
D:\sfstools\bin>mibset -n public -s 134.141.42.156 -branch 1.3.6.1.4.1 -oid 52.4.2.12.1.1 -varbind 3 [s]ENTREE -varbind 1 [i]2 The following OIDs will be set: ************************************************* 1.3.6.1.4.1.52.4.2.12.1.1.3 ---> [s]ENTREE 1.3.6.1.4.1.52.4.2.12.1.1.1 ---> 2 ************************************************* Sending SNMP set requests to switch(es)... Varbinds have been set.
1-33
Diagnostic Tools
ShowVST
ShowVST displays the virtual spanning tree ood path for a switch cloud. It will determine the root switch, and then walk the tree from there. The default settings will only display information about ports that are forwarding to other switches. ShowVST -long displays information about all network ports on each switch in the cloud. ShowVST supports topologies with shared media and/or topologies running the uplink model.
Syntax
ShowVst -s X1 [ options ]
Description
-s X1
Options
-long
Displays all relevant spanning tree information about ports.

-n X2

-o X3
X3 is the name of the le to write the output.

-throttle X4

-to X5

-rt X6
1-34
Diagnostic Tools
-lof X7
Example
C:\sfstools\bin>showvst -s 134.146.176.3 -n public Discovering cloud...Done Downloading Control Channel Information... ROOT SWITCH: 134.146.176.6 [11](ethernet) -> [11] 134.146.176.23 [13](inb) -> [162] 134.146.176.21 [10](atm-forum-svc) -> [9] 134.146.176.31 [161](inb) -> [160] 134.146.176.32 [162](inb) -> [13] 134.146.176.33 [163](inb) -> [13] 134.146.176.34 [166](inb) -> [4] 134.146.176.37 [11](atm-forum-svc) -> [11] 134.146.176.41 [161](inb) -> [160] 134.146.176.42 [162](inb) -> [13] 134.146.176.43 [164](inb) -> [4] 134.146.176.45 [168](inb) -> [37] 134.146.176.49 [16](inb) -> [39] 134.146.176.24 [18](inb) -> [6] 134.146.176.26 [15](inb) -> [30] 134.146.176.3 [17](inb) -> [8] 134.146.176.5
1-35
Diagnostic Tools
GUI ShowVST
1-36
Diagnostic Tools
Starting the GUI ShowVST

To start ShowVST from the GUI: 1. From the Tool Tray, select ShowVST. 2. Determine how much information you want to see. a. By default, ShowVST displays limited information. If that is what you want, go to step 3. b. For detailed information, click on Learn all spanning tree information. 3. Select the Go icon.
1-37
Diagnostic Tools
TraceCnx
TraceCnx searches the SFS connection table(s) for a connection with the userspecied source and destination. The source and destination may be specied by an Ethernet address, or by an IP address (or corresponding hostname). You can choose to have tracecnx delete any connection information found for the SA/DA pair. The tool searches through the connection tables of all switches for entries with the specied SA/DA pair. All connection hops found are displayed. A continuity check is also performed to verify that an end-to-end connection exists. The hops are then ordered from the ingress switch, the switch on which the SA is local, to the egress switch. TraceCnx can be helpful when troubleshooting connectivity between two end users. If tracecnx detects any problems (that may or may not cause a lack of connectivity between the source and the destination), the tool performs a series of investigations in an attempt to provide a possible explanation of the problem. These investigations include, but may not be limited to: VLAN policy checks Source and/or destination resolve blocks Proper ood path conguration Directory violations
The information is presented to you as potential sources of a problem, and should only be interpreted as such. Many times, such information may not indicate a connectivity problem, but rather a customized VLAN conguration.
Syntax
TraceCnx { -s X1 | -l X2 } { -s X3 | -l X4 } -src X5 -dest X6 [ options ]
Description
-s X1

-l X2
X2 is the name of a list of IP addresses to read.

-s X3
X3 is the IP address or hostname of the seed switch.

-l X4
X4 is the name of a list of IP addresses to read.
1-38
Diagnostic Tools
-src X5
Searches for connections with X5 being the source address. Specify the address as [enet]xx:xx:xx:xx:xx:xx, [ip]x.x.x.x, or [ip]hostname .
-dest X6
Searches for connections with X6 being the destination address. Specify the address as [enet]xx:xx:xx:xx:xx:xx, [ip]x.x.x.x, [ip]hostname .
Options
-a
-n X7

-throttle X8

-to X9

-rt X10
-rawTime
-lof X11
-k
Deletes the specied connection, if it exists.

-inq
Forces inquiries to run. Normally, inquiries run only if a problem is detected. Note that inquiries will always run in GUI mode.
1-39
Diagnostic Tools
Example
C:\sfstools\bin>tracecnx -s 134.141.42.14 -a -n sfpslab -src [ip]dallas -dest [ip]necrosis Running Unicast Connection Tracer... Discovering switches...done. Cloud has 19 switches. * Attempting to resolve source and destination addresses to their respective ethernet forms... Resolved 134.141.42.134 to the following address(es): 0:20:af:d2:eb:24 Resolved 134.141.43.213 to the following address(es): 8:0:20:f:48:7f * Searching for the connection in the cloud...Done Connection was found on 3 switches. * Attempting to find local switches of source and dest... Source: 134.141.42.134 (0:20:af:d2:eb:24) is local on 134.141.42.14, port 12 Destination: 134.141.43.213 (8:0:20:f:48:7f) is local on 134.141.45.205, port 5 * Ordering connection information... * The following ordered information was found: Hop Switch IP Source Destination In(1) Out(1) In(2) Out(2) ***************************************************************************************** 0 134.141.42.14 0:20:af:d2:eb:24 8:0:20:f:48:7f 12 26 26 12 1 134.141.45.196 0:20:af:d2:eb:24 8:0:20:f:48:7f 4 17 17 4 2 134.141.45.205 0:20:af:d2:eb:24 8:0:20:f:48:7f 48 5 5 48 * * * * Checking VLAN Policy for this connection... Vlan Policy Inquiry (0:20:af:d2:eb:24 <--> 8:0:20:f:48:7f) found no problems. Vlan Sync Inquiry (0:20:af:d2:eb:24) found no problems. Vlan Sync Inquiry (8:0:20:f:48:7f) found no problems.
Conection Trace Complete.
1-40
Diagnostic Tools
GUI TraceCnx
Starting the GUI TraceCnx

To start TraceCnx from the GUI: 1. From the Tool Tray, select TraceCnx. 2. In the Source box, select Ethernet, IP, or Hostname. 3. Specify an address or host name. 4. In the Destination box, select Ethernet, IP, or Hostname. 5. Specify an address or host name. 6. Select the Go icon. Note that inquiries always run in GUI mode.
1-41
Diagnostic Tools
1-42

VLAN Diagnostic Tools Guide

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

VLAN Diagnostic Tools Guide

Transféré par

Droits d'auteur :

Formats disponibles

VLAN Diagnostic Tools Guide

Industry Canada Notice

Standard Command Line Arguments

-v displays the tools version.

X1 is the IP address or host name of the seed switch in the cloud.

Displays neighbor information. The default is true.

X3 is the community string. The default is public.

X4 is the name of the le where the output is written.

X5 is the number of times to retry in case of SNMP failure. The default is 1.

X6 is the SNMP timeout (in seconds). The default is 2.

X7 is the number of SNMP requests per second. The default is 20.

Starting the GUI Das

X1 is the IP address or host name of the seed switch in the cloud.

X2 is the name of a list of IP addresses to be read.

Searches for alias information with X3 being an IP address.

Searches for alias information with X4 being a MAC address.

Searches for alias information with X5 being a NetBIOS address.

Searches for alias information with X6 being an AppleTalk address.

Removes all information from directory regarding an address.

X7 is the community string. The default is public.

X8 is the number of SNMP requests per second. The default is 20.

X9 is the SNMP timeout (in seconds). The default is 2.

Starting the GUI DirGrep

X1 is the IP address or host name of the seed switch in the cloud.

X2 is the name of a list of IP addresses to be read.

Deletes all nodes associated with error conditions.

Skips all alias processing.

Skips all node processing.

Skips non-IP alias processing.

Writes all directory info to the log, instead of just errors.

Writes directory info to a le named X3. The default is dirstat.log.

X4 is the community string. The default is public.

X5 is the number of SNMP requests per second. The default is 20.

X6 is the SNMP timeout (in seconds). The default is 2.

X7 is the number of times to retry in case of an SNMP failure. The default is 1.

Starting the GUI DirStat

X1 is the IP address or host name of the seed switch in the cloud.

X2 is the name of a list of IP addresses to be read.

X3 is the name of the prole for the desired MIB.

X5 is the base SNMP OID for the desired MIB branch.

Causes table rows to be displayed vertically.

X6 is a comma-separated list of eld names to lter from the MIB.

Shows the SNMP instance key for each row.

Writes database import-friendly output to X7.csv.

Writes database import-friendly output to screen.

X8 is the community string. The default is public.

X9 is the number of SNMP requests per second. The default is 20.

X10 is the SNMP timeout (in seconds). The default is 2.

Starting the GUI GetTable

X1 is the IP address or host name of the seed switch in the cloud.

X2 is the name of a list of IP addresses to be read.

X3 is the name of the conguration le to use. The default is mibPoller.cfg.

X4 is the name of the prole to use.

X6 is the name of the master output le. The default is mibPoller.out.

X7 is the name of a database-friendly output file.

X8 is the period at which to poll, in seconds. The default is 10.

Suppresses the totals display.

X9 is the number of minutes to run (0 = forever). The default is 0.

X10 is the community string. The default is public.

X12 is the SNMP timeout (in seconds). The default is 2.

Starting the GUI MibPoller

GUI MibPoller Fields