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

Rule Configuration failure is observed when multiple ports are configured for ALG Service (67150)

Last Updated: 4/19/2019Categories: TroubleshootingTotal Views: 4435Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Rule configuration on the DFW fails.

The status on the MP is Rule Publish Failure for the hosts in question.

The API reports the status similar to:

API Status

<hostStatus>
<hostId>host-569096</hostId>
<hostName>example.local</hostName>
<status>publish_failed</status>
<errorMessage>errorcode.301034</errorMessage>
<errorCode>301034</errorCode>
<startTime>1548839862774</startTime>
<endTime>1549367457383</endTime>
<generationNumber>1548839861809</generationNumber>
<clusterId>domain-c7</clusterId>
<generationNumberObjects>1549350096435</generationNumberObjects>
</hostStatus

In the /var/log/vsfwd.log file of the ESXi host, you see entries similar to:

2019-02-05T12:02:15Z vsfwd: [WARN] ioctl failed, errno=22
2019-02-05T12:02:15Z vsfwd: [WARN] Failed to apply RuleSet 1549368134646 for vnic 503ea0ff-2248-8d8c-57b1-9a15912e0c0f.002
2019-02-05T12:02:15Z vsfwd: [WARN] ioctl failed, errno=22
2019-02-05T12:02:15Z vsfwd: [WARN] Failed to apply RuleSet 1549368134646 for vnic 503ea0ff-2248-8d8c-57b1-9a15912e0c0f.001
2019-02-05T12:02:15Z vsfwd: [WARN] ioctl failed, errno=22
2019-02-05T12:02:15Z vsfwd: [WARN] Failed to apply RuleSet 1549368134646 for vnic 503ea0ff-2248-8d8c-57b1-9a15912e0c0f.000
2019-02-05T12:02:15Z vsfwd: [WARN] ioctl failed, errno=22
2019-02-05T12:02:15Z vsfwd: [WARN] Failed to apply RuleSet 1549368134646 for vnic 503e8715-9a5a-219f-3240-3181901f6361.000
2019-02-05T12:02:15Z vsfwd: [WARN] ioctl failed, errno=22
2019-02-05T12:02:15Z vsfwd: [WARN] Failed to apply RuleSet 1549368134646 for vnic 503e7213-7735-a717-4e61-72dea359e1bd.000
2019-02-05T12:02:15Z vsfwd: [WARN] ioctl failed, errno=22
2019-02-05T12:02:15Z vsfwd: [WARN] Failed to apply RuleSet 1549368134646 for vnic 501659d1-6df1-2be5-02bb-e893ea52e754.000
2019-02-05T12:02:15Z vsfwd: [WARN] ioctl failed, errno=22
2019-02-05T12:02:15Z vsfwd: [WARN] Failed to apply RuleSet 1549368134646 for vnic 503e82f1-e291-c0d2-7f5d-0f76cf54ad5b.000
2019-02-05T12:02:15Z vsfwd: [WARN] ioctl failed, errno=22
2019-02-05T12:02:15Z vsfwd: [WARN] Failed to apply RuleSet 1549368134646 for vnic 503e7fc0-13d4-44ff-20c6-9b461e4ac44

In the /var/log/vmkernel.log file of the ESXi host, you see entries similar to:

2019-02-05T12:02:15.750Z cpu36:27543657)VSIPFixRuleCtrlPort: unsupported dst port op 10 for dynamic rule!
2019-02-05T12:02:15.750Z cpu36:27543657)pf_rollback_rules: rs_num: 1, anchor: domain-c7
2019-02-05T12:02:15.750Z cpu36:27543657)pf_rollback_rules: rs_num: 2, anchor: domain-c7
2019-02-05T12:02:15.750Z cpu36:27543657)pf_rollback_rules: rs_num: 4, anchor: domain-c7
2019-02-05T12:02:15.756Z cpu36:27543657)VSIPFixRuleCtrlPort: unsupported dst port op 10 for dynamic rule!
2019-02-05T12:02:15.756Z cpu36:27543657)pf_rollback_rules: rs_num: 1, anchor: domain-c7
2019-02-05T12:02:15.756Z cpu36:27543657)pf_rollback_rules: rs_num: 2, anchor: domain-c7
2019-02-05T12:02:15.756Z cpu36:27543657)pf_rollback_rules: rs_num: 4, anchor: domain-c7
2019-02-05T12:02:15.761Z cpu36:27543657)VSIPFixRuleCtrlPort: unsupported dst port op 10 for dynamic rule!
2019-02-05T12:02:15.761Z cpu36:27543657)pf_rollback_rules: rs_num: 1, anchor: domain-c7
2019-02-05T12:02:15.761Z cpu36:27543657)pf_rollback_rules: rs_num: 2, anchor: domain-c7
2019-02-05T12:02:15.761Z cpu36:27543657)pf_rollback_rules: rs_num: 4, anchor: domain-c7
2019-02-05T12:02:15.766Z cpu36:27543657)VSIPFixRuleCtrlPort: unsupported dst port op 10 for dynamic rule!
2019-02-05T12:02:15.766Z cpu36:27543657)pf_rollback_rules: rs_num: 1, anchor: domain-c7
2019-02-05T12:02:15.766Z cpu36:27543657)pf_rollback_rules: rs_num: 2, anchor: domain-c7
2019-02-05T12:02:15.766Z cpu36:27543657)pf_rollback_rules: rs_num: 4, anchor: domain-c7
2019-02-05T12:02:15.772Z cpu36:27543657)VSIPFixRuleCtrlPort: unsupported dst port op 10 for dynamic rule!

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs because while configuring FW Rules for ALG services such as FTP/ ORACLE/SUNRPC/DCERPC, multiple ports have been specified. It is not supported to specifiy multiple ports for a single ALG firewall rule.

For example:

rule 1000 at 0 inout protocol tcp from addrset ip-securitygroup-100 to addrset ip-securitygroup-200 port {1521, 1522, 1525} with attribute addrset attr_1000_1_APP_ID accept as oracle;

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.5, available at VMware Downloads.

Workaround

To work around this issue, specify only 1 port per ALG service.

For example:

rule 1000 at 0 inout protocol tcp from addrset ip-securitygroup-100 to addrset ip-securitygroup-200 port 1521 with attribute addrset attr_1000_1_APP_ID accept as oracle;
rule 1001 at 0 inout protocol tcp from addrset ip-securitygroup-100 to addrset ip-securitygroup-200 port 1522 with attribute addrset attr_1000_1_APP_ID accept as oracle;
rule 1002 at 0 inout protocol tcp from addrset ip-securitygroup-100 to addrset ip-securitygroup-200 port 1525 with attribute addrset attr_1000_1_APP_ID accept as oracle;

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX Data Center for vSphere

Related Versions:

VMware NSX Data Center for vSphere 6.4.x

Take Our Survey

Support Assistant