Rule Configuration failure is observed when multiple ports are configured for ALG Service
search cancel

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

book

Article ID: 325126

calendar_today

Updated On:

Products

VMware NSX Data Center for vSphere

Issue/Introduction

  • 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-###</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-c#</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 ########-####-####-####-########0c0f.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 ########-####-####-####-########0c0f.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 ########-####-####-####-########0c0f.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 ########-####-####-####-########6361.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 ########-####-####-####-########e1bd.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 ########-####-####-####-########e754.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 ########-####-####-####-########ad5b.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 ########-####-####-####-########c44

     
  • 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-c#
    2019-02-05T12:02:15.750Z cpu36:27543657)pf_rollback_rules: rs_num: 2, anchor: domain-c#
    2019-02-05T12:02:15.750Z cpu36:27543657)pf_rollback_rules: rs_num: 4, anchor: domain-c#
    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-c#
    2019-02-05T12:02:15.756Z cpu36:27543657)pf_rollback_rules: rs_num: 2, anchor: domain-c#
    2019-02-05T12:02:15.756Z cpu36:27543657)pf_rollback_rules: rs_num: 4, anchor: domain-c#
    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-c#
    2019-02-05T12:02:15.761Z cpu36:27543657)pf_rollback_rules: rs_num: 2, anchor: domain-c#
    2019-02-05T12:02:15.761Z cpu36:27543657)pf_rollback_rules: rs_num: 4, anchor: domain-c#
    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-c#
    2019-02-05T12:02:15.766Z cpu36:27543657)pf_rollback_rules: rs_num: 2, anchor: domain-c#
    2019-02-05T12:02:15.766Z cpu36:27543657)pf_rollback_rules: rs_num: 4, anchor: domain-c#
    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.



Environment

VMware NSX Data Center for vSphere 6.4.x

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 specify multiple ports for a single ALG firewall rule.

For example:

rule 1000 at 0 inout protocol tcp from addrset ip-securitygroup-## to addrset ip-securitygroup-## port {1521, 1522, 1525} with attribute addrset attr_###_#_APP_ID accept as oracle;

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.5.


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;

Powered by Wolken Software