Table Of Contents

Discrepancy Reporting

Understanding Discrepancy Reporting

Physical Discrepancies

High Availability Not Enabled on Switches

CDP Enabled on Access Ports

BackboneFast Not Enabled on all Switches

Uplink Fast Not Enabled on Switches

UDLD Not Enabled on Link Ports

Spanning Tree Enabled on Access Ports

BPDUGuard Not Enabled on Access Ports

Logical Discrepancies

Channel Discrepancies

Trunk Discrepancies

Using Discrepancy Reporting

Configuring Discrepancy Reporting and Syslog Message Generation

Viewing Physical Discrepancy Reports

Viewing Logical Discrepancy Reports

Interpreting Discrepancies

Interpreting Physical Discrepancies

Interpreting Logical Discrepancies

Discrepancy Reporting

---

The Discrepancy Reporting module allows you to view the physical and logical discrepancies in your network. This chapter contains the following:

•Understanding Discrepancy Reporting

•Using Discrepancy Reporting

•Interpreting Discrepancies

Understanding Discrepancy Reporting

This feature offers reports on network inconsistencies, anomalies or misconfiguration in the physical and logical layout in the discovered network. This makes it easy to identify configuration errors such as line-speed mismatches on either end of a connection. This chapter contains the following:

•Physical Discrepancies

•Logical Discrepancies

Physical Discrepancies

The physical discrepancies reported by Campus Manager are:

•Channel Discrepancies

•CDP Enabled on Access Ports

•BackboneFast Not Enabled on all Switches

•Uplink Fast Not Enabled on Switches

•UDLD Not Enabled on Link Ports

•Spanning Tree Enabled on Access Ports

•BPDUGuard Not Enabled on Access Ports

High Availability Not Enabled on Switches

Enabling High availability on switches is applicable only for Cisco Catalyst 6000 devices.

High availability:

•Is a critical requirement for most networks. Switch downtime must be minimal to ensure maximum productivity in a network.

•Allows you to minimize the switch-over time from active supervisor engine to the standby supervisor engine, if the active supervisor engine fails.

•Allows the active supervisor engine to communicate with the standby supervisor engine, keeping feature protocol states synchronized.

•Provides a versioning option that allows you to run different software images on the active and standby supervisor engines.

---

Note Campus Manager reports a discrepancy, when there are two supervisor engines in Catalyst 6000 device and if you have not enabled High availability.

---

You can enable High availability using Command Line Interface (CLI).

As a general practice with redundant supervisors, we recommend you to enable High availability feature for normal operation.

---

Step 1 To enable High availability on Catalyst Operating System, enter the command:

set system highavailability enable

Step 2 To verify High availability, enter the command:

show system highavailability

Step 3 To enable High availability versioning, enter the command:

set system highavailability versioning enable

---

CDP Enabled on Access Ports

Cisco Discovery Protocol (CDP) is a Layer 2 protocol on all Cisco routers, bridges, access servers, and switches.

Cisco Discovery Protocol:

•Allows network management applications to discover Cisco devices that are neighbors of already known devices, especially neighbors running lower-layer transparent protocols.

•Enables network management applications to learn the device type and SNMP agent address of neighboring devices. Applications can send SNMP queries to neighboring devices with CDP enabled on them.

•Runs on all LAN and WAN media that support Subnetwork Access Protocol (SNAP).

Each CDP-enabled device sends periodic messages to a multicast address. Each device advertises at least one address at which it can receive SNMP messages.

These advertisements also contain the time-to-live, or holdtime information. These indicate the duration for which a receiving device should hold CDP information before discarding it.

---

Note Campus Manager reports a discrepancy for a switch port if CDP is enabled on the access port of a switch,

---

Access port is a port that Campus Manager learns as the one connected to the end host.

To disable CDP on Catalyst Operating System:

---

Step 1 Enter the command:

set cdp disable

Step 2 To disable CDP on port, enter the command:

set cdp disable mod/port

---

To disable CDP on Cisco IOS:

---

Step 1 Enter the command:

no cdp run

Step 2 To disable CDP on port, enter the command:

no cdp enable

---

BackboneFast Not Enabled on all Switches

When BackboneFast is enabled on all switches of a bridge network, it can save a switch upto 20 seconds while recovering from an indirect link failure.

BackboneFast is initiated when a root port or blocked port on a switch receives inferior Bridge Protocol Data Units (BPDU) from its designated bridge.

An inferior BPDU identifies a switch as both the root bridge and the designated bridge. Under normal Spanning Tree rules, the switch ignores inferior BPDUs for the configured maximum aging time.

•If the inferior BPDU arrives on a blocked port, the root port and other blocked ports on the switch become alternate paths to the root bridge. If the inferior BPDU arrives on the root port, all blocked ports become alternate paths to the root bridge.

•If the inferior BPDU arrives on the root port of a switch that has no blocked ports, the switch takes the maximum aging time on the root to expire. This is because it assumes that it has lost connectivity to the root bridge. This becomes the root switch according to normal Spanning Tree rules.

•If all the alternate paths to the root bridge indicate that the switch has lost connectivity to the root bridge, the switch causes the maximum aging time on the ports on which it received an inferior BPDU, to expire.

•If one or more alternate paths can connect to the root bridge, the switch will change all ports, on which it received an inferior BPDU, to its designated ports and move them out of blocking state to the forwarding state.

---

Note•Campus Manager reports a discrepancy, when BackboneFast is enabled on one of the switches and not enabled on all other switches in a switch cloud.

•It will not report a discrepancy, if BackboneFast is not enabled on any of the switches in a switch cloud.

---

---

Step 1 To enable BackboneFast Globally on Catalyst Operating System, enter the command:

set spantree backbonefast enable

Step 2 To check the status, enter the command:

show spantree backbonefast

---

To enable BackboneFast Globally on IOS:

---

Step 1 Enter the command:

spanning-tree backbonefast

Step 2 To check the status, enter the command:

show spanning-tree backbonefast

---

Uplink Fast Not Enabled on Switches

Uplink Fast is a Spanning Tree optimization feature. It:

•Improves the convergence time of the Spanning-Tree Protocol (STP) if an uplink fails when it is enabled on an access switch.

•Provides fast convergence after a Spanning Tree topology change and achieves load balancing between redundant links using uplink groups.

An uplink group is a set of ports where only one port will be in forwarding state at any given time. The uplink group provides an alternate path if the current forwarding link fails.

---

Note Campus Manager reports a discrepancy, if Uplink Fast is not enabled on switches. This discrepancy might not be applicable if the device is not an access layer switch.

---

When you enable Uplink Fast, it affects all VLANs on the Catalyst 6000 family switch. You cannot configure Uplink Fast on an individual VLAN.

To enable Uplink Fast on Catalyst OS:

---

Step 1 Enter the command:

set spantree uplinkfast enable

Step 2 To check the status, enter the command:

show spantree uplinkfast

---

To enable Uplink Fast on IOS:

---

Step 1 Enter the command:

spanning-tree uplinkfast

Step 2 To check the Status, enter the command:

show spanning-tree uplinkfast

---

UDLD Not Enabled on Link Ports

The Unidirectional Link Detection Protocol (UDLD) allows devices connected through fiber-optic or copper Ethernet cables to monitor the physical configuration of the cables and detect a unidirectional link. When a unidirectional link is detected, UDLD shuts down the affected port and alerts you.

UDLD performs tasks that cannot be performed by auto negotiation. When both auto negotiation and UDLD are enabled, Layer 1 and Layer 2 detection features work together to prevent physical and logical unidirectional connections and malfunctioning of other protocols.

The switch periodically transmits UDLD messages to neighboring devices with UDLD enabled ports. Devices on both ends of the link must support UDLD for the protocol to successfully identify and disable unidirectional links.

---

Note Campus Manager reports a discrepancy if UDLD is disabled on link ports.

---

Link port is a port that Campus Manager learns as the one connected to another device.

With supervisor engine you can specify the message interval between UDLD messages. Earlier, the message interval was fixed at 60 seconds. With a configurable message interval, UDLD reacts much faster to link failures.

To enable UDLD on Catalyst Operating System:

•To enable Globally, enter the command:

set udld enable

•To check UDLD status, enter the command:

show udld

•To enable UDLD on interface, enter the command:

set udld enable mod/port

•To check UDLD interface status, enter the command:

show udld mod/port

•To change the message interval, enter the command:

set udld interval interval

To enable UDLD on Cisco IOS:

•To enable Globally, enter the command:

udld enable

•To check UDLD status, enter the command:

show udld

•To enable UDLD on interface, enter the command:

udld enable

•To check UDLD interface status, enter the command:

show udld interface

•To change the message interval, enter the command:

udld message time time

Spanning Tree Enabled on Access Ports

You must enable BPDUFilter in order to disable Spanning Tree advertisements. If Spanning Tree is enabled on access ports Campus Manager will report a discrepancy. The BPDUFilter allows you to prevent a port from sending and receiving BPDUs.

BPDUFilter is enabled on a port, if:

•BPDUFilter is enabled on the specified ports

or

•Portfast is enabled on the port with BPDUFilter set to default and BPDUFilter global mode enabled.

---

Note Campus Manager reports a discrepancy if:

•BPDUFilter is enabled Globally and is disabled on the specified port.

•BPDUFilter is disabled Globally. (This is a discrepancy when the device does not support configuring BPDUFilter on the specified ports).

•BPDUFilter is disabled Globally and the BPDUFilter on the port is set to default.

•BPDUFilter is enabled Globally, PortFast is disabled and the BPDUFilter on the port is set to default.

---

To enable BPDUFilter on Catalyst Operating System:

•To enable BPDUFilter Globally, enter the command:

set spantree portfast bpdu-filter enable

•To enable BPDUFilter on port, enter the command:

set spantree portfast bpdu-filter mod/port enable

To enable BPDUFilter on Cisco IOS:

•To enable BPDUFilter Globally, enter the command:

spanning-tree portfast bpdufilter default

•To enable BPDUFilter on interface, enter the command:

spanning-tree bpdufilter enable

BPDUGuard Not Enabled on Access Ports

BPDUGuard enhances network reliability, manageability, and security.

Spanning Tree Protocol (STP) configures meshed topology into a loop-free, tree-like topology.

When the link on a bridge port goes up, STP calculates and moves the port to a forwarding or blocking state. This process depends on STP parameters, and the location of the port in the network. The process takes 30-50 seconds. During this period, no user data will pass through the port and some applications might time-out.

Enabling STP PortFast allows fast transition of the port into forwarding state. The port still participates in STP, so that if the port is a part of the loop, it can move into STP blocking mode.

When you disable a portfast-configured port that receives BPDU on a device, the device is not allowed to influence the STP topology. The port changes to errdisable state and displays a message on the console.

---

Note Campus Manager reports a discrepancy if portfast is enabled and the BPDUGuard is not enabled on the port.

---

Although the PortFast feature is configured on an individual port, the PortFast BPDUGuard option is configured Globally.

To disable BPDUGuard use the keyword no. The BPDUGuard becomes inactive when you disable PortFast on a port.

To enable BPDUGuard on Catalyst OS:

•To enable Globally, enter the command:

set spantree portfast bpdu-guard enable

•To enable on port, enter the command:

set spantree portfast bpdu-guard mod/port enable

•To re-enable from errdisable state, enter the commands:

errdisable recovery cause bpduguard

errdisable recovery interval interval

To enable BPDUGuard on IOS:

•To enable Globally, enter the command:

spanning-tree portfast bpduguard default

•To re-enable from errdisable state, enter the commands:

set errdisable recovery ause bpduguard

errdisable recovery interval interval

Logical Discrepancies

The new logical discrepancies reported by Campus Manager are the following:

•Channel Discrepancies

•Trunk Discrepancies

See Product Command Reference for your device on Cisco.com for the latest commands on the features discussed below.

Channel Discrepancies

EtherChannel bundles individual Ethernet links into a single logical link that provides higher bandwidth. Cisco EtherChannel technology is a trunking technology based on grouping several full-duplex 802.3

Ethernet links provide fault-tolerant, high-speed links between switches, routers, and servers. They provide load sharing across multiple fast Ethernet links while providing redundancy and subsecond convergence time.

EtherChannel includes four user-configurable modes: on, off, auto, and desirable.

Mode	Description
on	Forces the port to channel. A usable EtherChannel exists only when a port group in on mode is connected to another port group in on mode.
off	Prevents the port from channeling.
auto	Places a port in a passive negotiating state
desirable	Places a port in an active negotiating state in which the port initiates negotiations with other ports.

---

Note Campus Manager reports a discrepancy, when:

•Channel mode is desirable and the channel is not operational.

•Channel mode is auto and the channel is operational.

---

To set EtherChannel mode, enter the command:

set port channel mod/ports... [admin_group]

set port channel mod_num/port_num mode

{on | off | desirable | auto} [silent | non-silent]

Trunk Discrepancies

A trunk is a point-to-point link, carrying several VLANs. A trunk saves ports when creating a link between two devices that implement VLANs, typically two switches.

Trunking is hence a type of configuration on an interface that allows VLANs to span the entire network, instead of only one switch. The trunked interface that connects to another network device, is allowed to pass traffic for multiple VLANs, instead of only one VLAN as on a non-trunked interface on a switch.

For more details on Trunking, see:

•Reporting Trunk Discrepancies

•Understanding Trunking

•Dynamic Trunking Protocol (DTP)

•Trunk Encapsulation

•Trunk Characteristics

•Encapsulation Types

•Trunk Negotiation Enabled

Reporting Trunk Discrepancies

---

Note Campus Manager reports a discrepancy, when:

•Trunk mode is desirable and the trunk is not operational.

•Trunk mode is auto and trunk is operational.

•Trunk is operational at one end of the link, and not operational at the the other end.

---

For example, in the following table, column 1 represents the trunk mode on one end of a link, and row 1 represents the trunk mode on the other end of the link.

Table 7-1 lists all possible combinations of trunk mode configurations where the above scenarios can occur.

Table 7-1 Trunking Discrepancy Displayed  ¹

Modes	on	auto	desirable	nonegotiate	off
on	None. (Trunking)	Reports discrepancy. (Trunking)	None. (Trunking)	None. (Trunking)	Reports discrepancy. (Not Trunking)
auto	Reports discrepancy. (Trunking)	None. (Not Trunking)	Reports discrepancy. (Trunking)	Reports discrepancy. (Not Trunking)	None. (Not Trunking)
desirable	None. (Trunking)	Reports discrepancy. (Trunking)	None. (Trunking)	Reports discrepancy. (Not Trunking)	Reports discrepancy. (Not Trunking)
nonegotiate	None. (Trunking)	Reports discrepancy. (Not Trunking)	Reports discrepancy. (Not Trunking)	None. (Trunking)	Reports discrepancy. (Not Trunking)
off	Reports discrepancy. (Not Trunking)	None. (Not Trunking)	Reports discrepancy. (Not Trunking)	Reports discrepancy. (Not Trunking)	None. (Not Trunking)

1 Information in brackets indicate the trunking state of the interface.

Encapsulation Types

The encapsulation type allows you to specify whether ISL or 802.1q should be used for trunking. The encapsulation type parameter is only relevant if the module you are using is able to use both types of encapsulation.

The parameter can have three different values as shown in Table 7-2.

Table 7-2 Encapsulation Type Parameter 

Encapsulation Type	Description and Trunking
ISL	Sets the port encapsulation to ISL.
802.1Q	Sets the port encapsulation to 802.1q.
negotiate	Only available in auto or desirable trunking modes: •If the neighboring interface has encapsulation type set to negotiate, the trunk will eventually be set up with ISL. •If the interface is configured for ISL or 802.1q or only able to use ISL or 802.1q, the trunking encapsulation used will be the same as the neighboring interface.

Trunk Negotiation Enabled

Dynamic Trunking Protocol (DTP) cannot be used for trunk negotiation across VTP domain boundary. This occurs when trunk mode on both sides has the following combination:

•on/auto

•on/desirable

•desirable/auto

•desirable/desirable

•off-desirable

---

Note Campus Manager reports a discrepancy when trunk mode combination is one among the above said combinations.

---

Using Discrepancy Reporting

Campus can automatically identify two types of discrepancies on network devices:

•Physical discrepancies

Physical discrepancies include mismatches in line speed, trunk configuration, or duplex mode on two ends of a link.

For example, full duplex configured on one side of a link and half duplex configured on the other side.

•Logical discrepancies

Logical discrepancies include inconsistent or incorrect settings in VTP domains, VLANs, and ATM LANE components.

For example, an ATM VLAN that has no entry in the LECS or if there is a VTP client and no VTP server. You do not need a VTP server, if the network uses only transparent nodes in the domain.

Configuring Discrepancy Reporting and Syslog Message Generation

You can customize the Discrepancy Report to display only those discrepancies about which you want to be notified.

To customize the reports:

---

Step 1 Select Campus Manager > Administration > Network Discrepancies.

The Configuring Network Discrepancies window appears.

•To include a discrepancy in the Discrepancy Reports, check the box next to it.

Checking all the boxes results in a report displaying all discrepancies in the network.

•To exclude a discrepancy from the Discrepancy Reports, uncheck the box.

Step 2 To generate syslog messages for the selected discreapancies, select the Configure Syslog check box and click Next.

The list of selected discrepancies appears.

Step 3 Select the Send Syslogs check box and enter the name of the server in the Syslog Server field.

Step 4 Select the discrepancies for which you want to generate syslog messages and click Next.

A summary of the selected discrepancies appears.

Step 5 Click Finish.

---

You can use the filters to display discrepancy reports for specific devices, link or network types. This makes it easy to find a particular discrepancy for a particular type.

You can use more than one filter at the same time, but results will vary. If you select more than one filter in the same top-level category, Boolean OR is used. For example, if you select Duplex, Speed under Link, any link or port that fulfils at least one filter criteria will be displayed in the report. If you select more than one filter from different top-level categories, Boolean AND is used.

For example, if you select both a Link type and a Port type filter from the Physical discrepancy filter, any link that fulfils both filter criteria will appear in the report.

Table 7-3 Logical Discrepancies 

Field	Description
General > DuplicateSysName	More than one device with the same sysname (SystemName) on the Network
LANE > ATM-VLAN > NoEntryInLECS	ATM-VLAN with no entry in LE Config Server
LANE > ATM-VLAN > NoLESBUSEntryInLECS	ATM-VLAN with LE Server having no entry in LE Config Server
LANE > ATM-VLAN > Partitioned	Partitioned ATM-VLAN
LANE > LECS > MultiMaster	More than one LE Config Server in a single ATM Domain
Physical > CDPEnabledOnAccessPort	Access port with CDP enabled
Physical > Device > BackboneFastDisabled	Devices with BackboneFast not enabled
Physical > Device > UplinkFastDisabled	Devices with UplinkFast not enabled
Physical > HighAvailabilityDisabled	High Availability not enabled when multiple Supervisors are in a device
Physical > Link > Duplex	Link Duplex Mismatch
Physical > Link > Speed	Link Speed Mismatch
Physical > Link > Trunk	Trunk/nonTrunk Mismatch
Physical > Port > AutoChannel	Port Channel mode set to Auto, but port is part of a channel
Physical > Port > AutoTrunk	Trunk mode set to Auto, but port is Trunking
Physical > Port > BPDUGuardDisabled	Port with BPDU guard feature is disabled
Physical > Port > ErrDisabled	Port in Error disabled state
Physical > Port > NoChannel	Port channel mode is desirable, but it is not part of Channel
Physical > Port > NoTrunk	Trunk mode is desirable, but it is not trunking
Physical > Port > PortFastEnabled	Trunk Port in PortFast enabled state
Physical > Port > STPEnabledOnAccessPorts	Access port with STP enabled
Physical > Port > UDLDDisabled	Port with UDLD disabled
VLAN > Domain > Disconnect	VTP Disconnected Domain
VLAN > Domain > NoServerWithClients	No VTP Server in Domain
VLAN > DripEnabled	DRiP enabled VLAN
VLAN > EtherChannelPort > SpanningTree	EtherChannel Port Spanning Tree not disabled
VLAN > Link > Multi	Trunk VLANs Mismatch
VLAN > Link > Protocol	Trunk VLAN Protocol Mismatch
VLAN > Link > Single	Native VLANs Mismatch
VLAN > Link > TrunkNegotiationEnabled	DTP enabled on trunk port across VTP boundary
VLAN > Pair > Index	VLAN Index Conflict
VLAN > Pair > Name	VLAN Name Conflict

Viewing Physical Discrepancy Reports

Discrepancy reports can be viewed using either of the following methods:

•From the CiscoWorks Homepage:

Select Campus Manager > Discrepancy Reports > Physical Discrepancy Report.

Or

•From a network topology view:

To view physical discrepancies for the entire network, from the LAN Edge or Layer 2 Network View window, select Reports > Discrepancies. It displays any link-setting mismatches that might need to be corrected on devices.

You can also display physical discrepancies for a specific ATM or VTFI domain by selecting the discrepancy filters within the Network View window for that domain.

Viewing Logical Discrepancy Reports

You can display logical discrepancies to identify inconsistencies in the logical setup of the VTP Domains, VLANs, and LANE components in your network.

To display these discrepancies, you can do one of the following:

•Select the Discrepancy Reports application from the CiscoWorks Homepage

•Follow this procedure inTopology Services:

---

Step 1 From Topology Services , select Reports > Discrepancies. The Logical Discrepancy report appears.

•To print this report, select File > Print from Discrepancy Report menu.

•To save the summary of discrepancies as a file, select File > Export > Summary from the Discrepancy Report menu bar.

•To save the summary and details of discrepancies as a file, select File > Export > Details from the Discrepancy Report menu.

Step 2 Select a discrepancy and click Details for more information.

---

Interpreting Discrepancies

When interpreting the discrepancy report, consider that some configurations may appear as discrepancies. If you had planned to configure your network in this way, you can ignore the discrepancies.

Interpreting Physical Discrepancies

Physical discrepancies are potential misconfigurations in the physical layout of your network. For more details, see Table 7-4.

Table 7-4 Physical Discrepancies 

Discrepancy	Description
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/nonTrunk Mismatch	Trunking ports versus nontrunking ports on either side of a link
Port in ErrorDisabled State	Port is in Error Disabled state caused by erroneous traffic
PortFastEnabled on Trunk Port	A port configured for trunk is in Spanning Tree PortFastEnabled state
High Availability Disabled	High Availability Feature is disabled in a device when it has more than one Supervisor Card
CDP Enabled on Access Port	An access port of a device is enabled for CDP
BackboneFast Disabled	BackboneFast feature is disabled on a device
UplinkFast Disabled	UplinkFast feature is disabled on a device
UDLD Disabled	Unidirectional Link Detection feature is disabled on a device
STP Enabled on Access Port	An access port of a device in which STP is enabled
BPDU Guard Disabled	BPDU Guard Feature is disabled on a port
Auto Channel	A port is configured for auto mode, and it is part of channel
No Channel	A port is configured for desirable mode, and it is not part of channel

Interpreting Logical Discrepancies

Logical discrepancies identify inconsistencies in the logical setup of the VTP Domains, VLANs, and LANE components in your network. For more details, see Table 7-5.

Table 7-5 Logical Discrepancies 

Discrepancy	Description
Trunk VLANs Mismatch	Different ends of trunk specify different VLANs.
Native VLANs Mismatch	Different ends of single VLAN link specify different VLANs.
VLAN Name Conflict	VLAN in a VTP server domain has the same name as a VLAN on a VTP transparent switch with a different ISL number.
VLAN Index Conflict	VLAN in a VTP server domain has the same ISL number as a VLAN on a VTP transparent switch with a different VLAN name.
Trunk VLAN Protocol Mismatch	Protocol encapsulation differs across a trunk (ISL versus IEEE 802.1Q).
VTP Disconnected Domain	Link in a VTP domain is not set to trunk. Some devices in this domain do not communicate through any trunk.
No VTP Server in Domain	No VTP server in the domain.
EtherChannel Port Spanning Tree Not Disabled	Spanning Tree Protocol is not supported with Catalyst software release 2.3 and lower. Therefore, disable Spanning Tree on switches with active VLANs that span Fast EtherChannel connections. For Catalyst software release 3.1 and higher, configure Spanning Tree on Fast EtherChannel links.
ATM-VLAN with no entry in LE Config Server	ATM-VLAN has no entry in LE Config Server.
ATM-VLAN with LE Server having no entry in LE Config Server	LE Server in ATM-VLAN does not have any entry in LE Config Server.
More than one LE Config Server present in a single ATM Domain	There are multiple LE Config Servers in a single ATM domain.
Partitioned ATM-VLAN	ATM-VLAN has clients going to more than one LE Server.
DRiP enabled VLAN	DRiP protocol, which can disable certain ports, is enabled on this VLAN.
Trunk Negotiation Enabled	Ports of the devices in two different VTP domains configured for DTP Negotiation
Auto Trunk	A port is configured for auto mode, and it is trunking
No Trunk	A port is configured for desirable mode, and it is not trunking