|
|
You can use discrepancy reports and troubleshooting tips to help you interpret the information in the VlanDirector application:
To display discrepancy reports, select Reports>Discrepancies from the VlanDirector Names window.
The VLAN - Discrepancy window opens (Figure 6-1).
You can export the discrepancy report by following these steps:
Step 1 From the VlanDirector window, select Reports>Discrepancies.
Step 2 To export the report, select File>Export.
For assistance interpreting the results, see "Interpreting the Discrepancy Report."
The discrepancy report displays information on inconsistencies or irregularities in the VLANs in your network. Table 6-1 lists these irregularities and describes their meanings. The discrepancy report itself shows additional information about each discrepancy.
Keep in mind that configurations that you set up intentionally may appear as discrepancies. If you are aware that this is how you wanted to configure your network, then do not be overly concerned with the discrepancies.
| Discrepancy | Meaning |
|---|---|
Trunk VLANs Mismatch | Different ends of a trunk specify different VLANs. |
Native VLANs Mismatch | Different ends of a single VLAN link specify different VLANs. |
VLAN Name Conflict | VLANs with different ISL numbers have the same name in different domains. |
VLAN Index Conflict | VLANs with different names have the same ISL number in different domains. |
VLAN SAID Conflict | Different SAID numbers on the same VLAN in different domains. |
Link Duplex Mismatch | Full-duplex versus half-duplex on either side of a link. |
Link Speed Mismatch | Different link speed on either side of a link (for 10/100 ports or for any group of links). |
Trunk VLAN Protocol Mismatch | Protocol encapsulation differs across a trunk (ISL versus 802.1Q). |
Trunk/non Trunk Mismatch | Trunking ports versus non-trunking ports on either side of a link. |
VTP Disconnected Domain | A link in a VTP domain is not set to trunk. There are devices in this domain that do not communicate through any trunk. |
No VTP Server in Domain | There is no VTP server in the domain. |
EtherChannel Port Spanning Tree Enabled | Spanning Tree Protocol is not supported on Catalyst software release 2.3 and earlier. Spanning tree must be turned off for all active VLANs that go across the Fast EtherChannel connections. For Catalyst software release 3.1 and later, you can configure spanning tree on Fast EtherChannel links. |
LANE Configuration Server ATM Address Missing | LANE Configuration Server ATM address not found on the ATM switch. |
LANE Client VLAN/ATM-VLAN Misassociation | ATM-VLAN associated with a VLAN with a different name. |
LANE Client with no ATM-VLAN | A LANE client has no ATM-VLAN associated with it. |
LANE Broadcast Server with no ATM-VLAN | A LANE broadcast server has no ATM-VLAN. |
Use the information in these sections to help you troubleshoot problems with the VlanDirector application.
If you have difficulty creating and displaying VLANs in the VlanDirector application, use the information in these sections to answer some of your common questions:
The VlanDirector application requires VTP to be enabled. For most predictable results, Cisco recommends having at least one switch configured as a VTP server and the remaining switches configured as VTP clients.
If the two VTP servers are in the same domain and are connected by VTP trunks, it does not matter which switch the VlanDirector application changes. VTP ensures that the information on all VTP servers and clients in a single VTP domain are coordinated and share the same configuration.
If the servers are in different VTP domains, then they do not share VLAN states, and they are both known to the VlanDirector application. You must select the VTP domain in which you want to make the VLAN changes, and the corresponding VTP servers will reflect those changes.
If there are two servers with the same VTP domain that are not connected by trunks the configurations managed by the two servers may diverge. This configuration is not supported by the VlanDirector application, and it creates a discrepancy.
You can have VLANs with the same name provided that other characteristics, such as VLAN Index and SAID value are also identical. Discrepancies occur when there are identically named VLANs with other attributes that are different (such as index, and so on). If the two VLANs share identical definitions, no discrepancy is detected.
Attempting to drag a port to a VLAN may or may not work depending upon the definition of that particular VLAN on both the VTP server and the transparent switch. If the definitions are identical (including name, VLAN index, and so on), the dragging process will probably work fine. However, if the definitions are not identical, then the results are undefined: the process may or may not work. Therefore, to add VTP transparent switches to the same VLANs that are running on the VTP server, you must ensure that the VLAN definitions are consistent.
The VlanDirector application does not discover any VLANs configured on a switch in transparent mode. Thus, if the VLAN state of a transparent switch differs from the state reported by a server in the same domain, then the VlanDirector application will not properly handle VLAN changes to the transparent switch.
You can highlight the devices that participate in particular VLANs on the CWSI Campus map. Use the information in this section to resolve any problems you have doing this.
In the VlanDirector application you can select a VLAN, and the switches associated with that VLAN are highlighted on the CWSI Campus map. You can also highlight a switch in the CWSI Campus map to indicate which VLANs are active on that switch. However, if the switch has trunks that carry all VLANs, then the switch will be highlighted regardless which VLAN you select.
Use the information in this section to answer any questions you might have while adding ports to VLANs.
The lightning bolt on a port means that the port is part of a link (either a device-to-device link or a connection into a shared media).
The lightning bolt is used to differentiate between a port that is connected to another switch (linking) and a port that is configured as a user port. Cisco Discovery Protocol (CDP) has discovered a CDP peer out of this port.
The bolt indicates that you cannot manipulate the port for VLAN configuration by itself; you must configure it as part of its corresponding link. You do this by selecting the link from the CWSI Campus map and dragging the link to the appropriate VLAN.
The VlanDirector application enables you to configure LANE services. If you have difficulty configuring LANE services using the VlanDirector application, use the information in this section to assist you.
The following tables provides you with detailed troubleshooting information for resolving LANE configuration problems:
| Probable Cause | Possible Solution |
|---|---|
Devices do not have required software image versions. | Make sure that all devices are running the required software image version for LANE services. See the CWSI Campus release notes for the correct software image versions for your devices. |
Incorrect read community strings entered in CWSI Campus. | Verify that the SNMP community strings entered in CWSI Campus match the actual ones for all the devices on which LANE components are being configured. To check the community strings, select Edit>SNMP Communities from the CWSI Campus map. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the correct community strings. |
No SNMP connectivity on LANE devices. | Make sure that all LANE devices are reachable through SNMP. |
SNMP timeouts are occurring on the devices. | Check the CWSI Campus map to see if devices appear with a red X on them. Increase the SNMP time out for the devices and rediscover the devices or network. To lengthen the timeout, select Edit>SNMP Communities from the CWSI Campus map window. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the SNMP time out. |
LANE servers on devices that do not have enough memory. | If the configuration server resides on a Catalyst 5000 series switch, verify that the device has at least 16 MB of memory. |
Unable to discover the configuration servers. | Verify that the master configuration server has been discovered by selecting Edit>Configure Config Server from the VlanDirector Names window. Cisco does not recommend using more than one master configuration server in an ATM fabric. If there are multiple master configuration servers, CWSI Campus will randomly select one of them to use for discovery, and the others are ignored. See Chapter 5, "Modifying and Creating VLANs" in the Using the Campus VlanDirector Application publication for additional assistance. |
Unable to discover the LE servers. | You should have at least one active LE server for each ATM-VLAN. The configuration server database should reflect the correct master ship state of the LE severs. Use the CLI to check the configuration server database. A valid configuration server database is similar to the following: at-5000-4atm1#sh lane database LANE Config Server database table 'cwsiLecsDb' no default elan elan 'vlanElanTest': un-restricted server 47.00918100000000603E899701.00E01431A421.01 (prio 0) LANE Config Server database table 'lecsdb_57_87.3' bound to interface/s: ATM0 default elan: default elan 'default': un-restricted server 47.00918100000000603E899701.00E01431A421.01 (prio 0) active elan 'vlan9': un-restricted server 47.00918100000000603E899701.00E01431A421.09 (prio 0) active |
ATM-VLAN may be associated with VTP VLAN with a different name. | In the VlanDirector application, a VTP VLAN with an associated ATM-VLAN is represented under the VTP Domain folder as one entry with an ATM cloud icon beside it. For example, when a VTP VLAN with the name "X" is associated with an ATM-VLAN with the name "Y," it is represented as one entry under the VTP Domain folder as "X" with an ATM cloud icon beside it. The name "Y" does not appear anywhere. |
These solutions do not resolve the problem. | Enable trace and debug entering the following command: ani -trace frontend -debug vlad -debug lane -debug ilmi -trace pnni -debug vmpsadmin -trace devices -debug devices.C5K -debug devices.C5K.C5500 -debug devices.LS1010 -debug devices.Router -debug devices.C3K -debug devices.C2800 -logfile ani.log See "Enabling Trace or Debug" for assistance entering this command. |
| Probable Cause | Possible Solution |
|---|---|
Devices do not have required software image versions. | Make sure that all devices are running the required software image version for LANE services. See the CWSI Campus release notes for the correct software image versions for your devices. |
Incorrect read community strings entered in CWSI Campus. | Verify that the SNMP community strings entered in CWSI Campus match the actual ones for all the devices on which LANE components are being configured. To check the community strings, select Edit>SNMP Communities from the CWSI Campus map. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the correct community strings. |
No SNMP connectivity on LANE devices. | Make sure that all LANE devices are reachable through SNMP. |
SNMP timeouts are occurring on the devices. | Check the CWSI Campus map to see if devices appear with a red X on them. Increase the SNMP timeout for the devices and rediscover the devices or network. To lengthen the timeout, select Edit>SNMP Communities from the CWSI Campus map window. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the SNMP time out. |
No LANE clients exist for the ATM-VLAN. | Configure LANE clients for appropriate ATM-VLANs. See the Configuring and Monitoring LANE Services scenario in Chapter 7, "Scenarios---Managing Networks with CWSI Campus" in the Getting Started with CWSI Campus publication. See the software configuration guide for your specific device. |
LANE clients exist but are not discovered. | Make sure that devices are not timing out. |
LANE servers on devices that do not have enough memory. | If the configuration server resides on a Catalyst 5000 series switch, verify that the device has at least 16 MB of memory. |
No rediscovery done after configuring VLANs with LANE services enabled. | Step 1 From the CWSI Campus Map window, select View>Rediscover Map Step 2 Start the VlanDirector application by selecting Tools>VlanDirector from the CWSI Campus Map. Step 3 From the VlanDirector Names window, select File>Refresh. See the Using the Campus VlanDirector Application publication for additional assistance. |
These solutions do not resolve the problem. | Enable trace and debug entering the following command: ani -trace frontend -debug vlad -debug lane -debug ilmi -trace pnni -debug vmpsadmin -trace devices -debug devices.C5K -debug devices.C5K.C5500 -debug devices.LS1010 -debug devices.Router -debug devices.C3K -debug devices.C2800 -logfile ani.log See "Enabling Trace or Debug" for assistance entering this command. |
| Probable Cause | Possible Solution |
|---|---|
Devices do not have required software image versions. | Make sure that all devices are running the required software image version for LANE services. See the CWSI Campus release notes for the correct software image versions for your devices. |
Incorrect read community strings entered in CWSI Campus. | Verify that the SNMP community strings entered in CWSI Campus match the actual ones for all the devices on which LANE components are being configured. To check the community strings, select Edit>SNMP Communities from the CWSI Campus map. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the correct community strings. |
No SNMP connectivity on LANE devices. | Make sure that all LANE devices are reachable through SNMP. |
SNMP timeouts are occurring on the devices. | Check the CWSI Campus map to see if devices appear with a red X on them. Increase the SNMP time out for the devices and rediscover the devices or network. To lengthen the timeout, select Edit>SNMP Communities from the CWSI Campus map window. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the SNMP time out. |
Failed to create LE server. | Increase the time out for the device on which you have configured the LE server. |
Configuration server could not be configured. | The LE server ATM address already exists in the configuration server database. Make sure that the ATM address of the newly created LE server is not already present in the configuration server database. |
These solutions do not resolve the problem. | Enable trace and debug entering the following command: ani -trace frontend -debug vlad -debug lane -debug ilmi -trace pnni -debug vmpsadmin -trace devices -debug devices.C5K -debug devices.C5K.C5500 -debug devices.LS1010 -debug devices.Router -debug devices.C3K -debug devices.C2800 -logfile ani.log See "Enabling Trace or Debug" for assistance entering this command. |
| Probable Cause | Possible Solution |
|---|---|
Devices do not have required software image versions. | Make sure that all devices are running the required software image version for LANE services. See the CWSI Campus release notes for the correct software image versions for your devices. |
Incorrect read community strings entered in CWSI Campus. | Verify that the SNMP community strings entered in CWSI Campus match the actual ones for all the devices on which LANE components are being configured. To check the community strings, select Edit>SNMP Communities from the CWSI Campus map. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the correct community strings. |
No SNMP connectivity on LANE devices. | Make sure that all LANE devices are reachable through SNMP. |
SNMP timeouts are occurring on the devices. | Check the CWSI Campus map to see if devices appear with a red X on them. Increase the SNMP time out for the devices and rediscover the devices or network. To lengthen the timeout, select Edit>SNMP Communities from the CWSI Campus map window. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the SNMP time out. |
Failed to configure the configuration server database. | Increase the time out for the device on which you have configured the configuration server. |
Configuration server already exists. | Using the CLI, remove the existing configuration server database. The following is a sample configuration: interface ATM0 mut 1500 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi atm ilmi-keepalive 5 lange config database xxxx Remove the line: lange config database xxxx |
Could not assign ATM addresses to the configuration server. | Using the CLI, remove the ATM address association if it already exists. The following is a sample configuration: interface ATM0 mtu 1500 atm pvc 1 0 5 qsaal atm pvc 2 0 16 ilmi atm ilmi-keepalive 5 lane config fixed-config-atm-address lane config auto-config-atm-address lane config config-atm-address lane config database xxxx Remove these lines: lane config fixed-config-atm-address lane config auto-config-atm-address lane config config-atm-address lane config database xxxx |
Could not configure configuration server's ATM address on the ATM switches. | Verify the community strings and increase the SNMP timeout. To check the community strings and increase the SNMP timeout, select Edit>SNMP Communities from the CWSI Campus map. See Chapter 1, "Preparing for Network Discovery" of the Getting Started with CWSI Campus publication if you need additional assistance entering the correct community strings. |
These solutions do not resolve the problem. | Enable trace and debug entering the following command: ani -trace frontend -debug vlad -debug lane -debug ilmi -trace pnni -debug vmpsadmin -trace devices -debug devices.C5K -debug devices.C5K.C5500 -debug devices.LS1010 -debug devices.Router -debug devices.C3K -debug devices.C2800 -logfile ani.log See "Enabling Trace or Debug" for assistance entering this command. |
Some of the troubleshooting steps require that you enable trace or debug in ANI to gather additional information.
Enable trace and debug by following these steps:
Step 1 Open a command prompt or shell window.
Step 2 Enter stopcwsiserver to stop the CWSI Campus server processes.
Step 3 Start ANI and enable trace and debug by entering the following command:
ani -trace <subsystem> -logfile <logfile name>
The troubleshooting instructions provide you with the appropriate subsystem name. You can enter any name for the log file, and the log file will appear in the <CWSIROOT> directory, where <CWSIROOT> is the directory in which you installed CWSI Campus.
Step 4 To stop the process, press Ctrl-C from the command prompt or shell window.
Step 5 Contact your Cisco TAC representatives and provide them with this log file.
Posted: Thu Sep 30 12:11:03 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.