Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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 NPM: Entry stating 'SM-EIO-Fatal I/O error' found in Smarts server log file (362168)

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

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

In BGP log:

Entry stating SM-EIO-Fatal I/O error found in Smarts BGP server log file
Following error is found in Smarts Border Gateway Protocol (Smarts BGP) Server log:

[24-Oct-2008 05:30:50+481ms MEST] t@48 Discovery #3
ASL-E-ERROR_LOSTSERVER-Lost contact with remote server -- terminating parser
ASL-ERROR_GET-While attempting to get property 'DisplayName' of object
'MR_Object::SNMPAgent-ip-raif-ch-use-r-001'
SM-EIO-Fatal I/O error

From SAM log:

March 29, 2016 8:40:54 PM GMT+00:00 +038ms 9141310 39848256 WARN SM_ProtocolEngine-175 7357 ICS_RSM SM_EIO SVIF-W-WRSTSRV_IO-AMER-ICR4 I/O Error in remote command 'invokeOperation(className, instanceName, opName, args)'; Reconnecting... CI-EWHILE-While executing function "write" CI-EFLOWKEEPALIVESEND-Flow closing due to inability to send keepalive at March 24, 2016 11:00:39 PM GMT+00:00 +587ms <SYS>-ECONNRESET-Connection reset by peer CI-EFLOWCLOSED-Flow has been closed; in file "/work/tancurrent/DMT-9.3.0.X/2/smarts/clsapi/ci_flow.c" at line 2750 SM-EIO-Fatal I/O error; in file "./SM_RemoteServer_.c" at line 3516

Cause

The Smarts BGP server has lost contact with the remote Smarts AM server in the middle of the discovery operation. This is most likely a system or network problem on the system which is running the Smarts BGP server. The SM-EIO-Fatal I/O error is from <sys/errno.h>, and the platform code is simply passing the strerror() return string. This means that although Smarts is registering an exception, the "Fatal I/O error" does not represent a fatality to the Smarts BGP thread or process.

SM-EIO-Fatal I/O error can occur any time that a domain cannot successfully connect to a subscribed domain.  Typically, it indicates some sort of network communication failure.

Resolution

Investigate whether there is system or network problem on the system which is running the Smarts BGP server, and resolve if found. The Smarts AM log file may contain clues to the cause of the system/network problem.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

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