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

Cable Connection not being created between Arista switches and Hosts (501548)

Last Updated: 12/17/2018Categories: TroubleshootingTotal Views: 3995Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Cable connections are not being built during discovery for connections between Arista switches and some Hosts and other devices.

Cause

In this case, the Host did not support LLDP neighbor protocol.  Since there was no neighbor protocol to use, discovery was forced to use the industry standard bridging protocol to try to build connections.  Unfortunately for many of the Arista switches, this information is not populated in their MIB.  This causes the discovery to fail to find bridging information that would allow the cable connection to be built.

Resolution

The current work around is to add a line to the Arista certification by essentially creating a field certification for affected Arista devices.  I will use .1.3.6.1.4.1.30065.1.3011.7280.3714.72 as an example.

The default certification for this device is:

#  Arista Arista 7280SE-64
.1.3.6.1.4.1.30065.1.3011.7280.3714.72 {
TYPE = Switch
VENDOR = Arista
MODEL = Arista-7280SE-64
CERTIFICATION = CERTIFIED
CONT = Arista-Switch
HOSTRESRCS = MIB2
VLAN = AristaDot1q
NEIGHBOR = LLDP

INSTRUMENTATION:
Environment                         = AristaEntityFRU:DeviceID
Card-Fault                          = EntityState:DeviceID
Interface-Fault                     = MIB2
Interface-Performance               = MIB2
Port-Fault                          = MIB2
Port-Performance                    = MIB2
}

By adding the option 'BRIDGE = Dot1q', we can add the required functionality to build many of these connections.  The modified certification will look like this:

#  Arista Arista 7280SE-64
.1.3.6.1.4.1.30065.1.3011.7280.3714.72 {
TYPE = Switch
VENDOR = Arista
MODEL = Arista-7280SE-64
CERTIFICATION = CERTIFIED
CONT = Arista-Switch
BRIDGE=Dot1q <------------ Added
HOSTRESRCS = MIB2
VLAN = AristaDot1q
NEIGHBOR = LLDP

INSTRUMENTATION:
Environment                         = AristaEntityFRU:DeviceID
Card-Fault                          = EntityState:DeviceID
Interface-Fault                     = MIB2
Interface-Performance               = MIB2
Port-Fault                          = MIB2
Port-Performance                    = MIB2
}

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