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

Windows 2008 Event Log Servers detected by NSX as Win2K3 when added using GUI (76042)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 3814Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While setting up Event Log Scraping for Identity Firewall, you try to add a Windows 2008 Event Log Server from GUI. The Win2K8 server is detected by NSX as Win2K3.

Log scraping does not work. NSX is unable to capture the login events forwarded by the affected event log servers. Therefore, Identity Firewall does not work as needed.

Cause

When adding the event log server using UI, the code does not fetch the server type as it should. However, the API call to perform the same functionality fetches it correctly.

Resolution

This issue is resolved in VMware NSX Data Center for vSphere 6.4.7, available at VMware Downloads .

Workaround

Delete the event log server and then re-add it via API as below.

POST /api/1.0/directory/updateEventLogServer

Request Body:

<EventlogServer>
<domainId>1</domainId>
<hostName>eventlog_server_1.abc.com</hostName>
<enabled>true</enabled>
</EventlogServer>

(You can retrieve the domain id used above from GET /api/1.0/directory/listDomains.)

The API response should correctly show WIN2K8 in serverType, and you can also confirm it is WIN2K8 in GUI.

Related Information

NSX Manager logs (vsm.log) show that it's incorrectly treating the server as Windows 2003 when added from GUI.

2019-09-09 12:45:34.828 AST  INFO http-nio-127.0.0.1-7441-exec-20 DirectoryModificationObserver:158 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Event log server saved, event log server id: 31
2019-09-09 12:45:34.829 AST  INFO taskExecutor-12 RestartEventLogReaderEventLogServerListener:36 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] EventLogServer with id: 31 saved, restart event log reader.
2019-09-09 12:45:34.832 AST  INFO taskExecutor-12 EventLogComponent:183 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Restarting event log reader for event log server EventLogServer[id=31,hostname=eventlog_server_1.abc.com]
2019-09-09 12:45:34.834 AST  INFO taskExecutor-12 WinEventLogCIFSReader:75 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] CIFS reader for eventlog_server_1.abc.com is starting...
2019-09-09 12:45:34.842 AST  INFO taskExecutor-12 EventLogContext:87 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Widnows 2003 Server event log context for server eventlog_server_1.abc.com started.

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)

KB
•
ESXi を 6.7 にアップグレードした後で Linux 仮想マシンが再起動する (70813)

KB
•
誤ったアラームが VMware ESXi 6.5 および VMware ESXi 6.7 で実行している IPMI センサーからトリガーされる (76611)

KB
•
在使用 Qlogic 驱动程序的 ESXi 6.7 U2 上运行时，重新引导后不会保存暂存分区设置 (76503)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

Take Our Survey

Support Assistant