Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts AM: VLAN information is missing in Smarts AM for a switch connected to a router with sub-interface (372285)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3140Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

VLAN information is missing in Smarts AM for a switch connected to a router with sub-interface

VLAN information is missing in Smarts AM for router configured with the following sub-interface:

Interface GigabitEthernet0/1.11
description RouterName VLAN 11
encapsulation dot1Q 11
ip vrf forwarding INTERNET
ip address x.x.x.x 255.255.255.248
standby 11 ip z.z.z.z
standby 11 priority 120
!

Cause

This problem has been seen when a sub-interface is configured GigabitEthernet0/1.11 but the VLAN is not configured on any neighboring switching systems (all the neighboring systems are Routers), and there is no cable created with this interface. Therefore, the VLAN is associated with the sub-interface GigabitEthernet0/1.11, but this was only for the encapsulation and  does not mean that the VLAN is available in the required router.
The VLAN probe collects VLAN information for the bridges and switches, including VLAN identifiers, trunk ports, and VLAN port memberships. Based on the encapsulation dot1Q 11 configuration line, VLAN 11 is expected to be linked to the interface in Smarts, and the switch is configured as a trunk. Therefore, strictly speaking the VLAN terminates/originates on the PE sub-interface through the encapsulation command. If the VlAN is the mode access on the switch, the encapsulation command should not be required on the PE route. The VLAN information is missing in Smarts because VLANs are port-based or MAC-based and are created in Switches, not for Routers. Quite often there is an Encapsulation to route the VLAN to the router through an Ethernet interface. VLANs are not composed of the Required interface in Routers. A router cannot be composed of VLANs without connection to a switch .

Resolution

To resolve this issue, ensure that a router composed of VLANs is connected to a switch.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant