Groups include different objects that are added both statically and dynamically, and can be used as the source and destination of a firewall rule.

Groups can be configured to contain a combination of virtual machines, IP sets, MAC sets, segment ports, segments, AD user groups, and other groups. Dynamic inclusion of groups can be based on tag, machine name, OS name, or computer name.

Note: If you create a group in the API using LogicalPort based criteria, you cannot edit the group in the UI using the AND operator between SegmentPort criteria.

If Malicious IP Feed is enabled, a list of known malicious IPs are downloaded from NTICS cloud service. You can create groups to include these downloaded IPs and configure firewall rules to block access to them. Note that you can convert a Generic or IP Addresses Only groups to IP Addresses Only group with malicious IPs, but cannot convert the other way round.

Groups can also be excluded from firewall rules, and there are a maximum of 100 groups that can be on the list. IP sets, MAC sets, and AD groups cannot be included as members in a group that is used in a firewall exclusion list. See Manage a Firewall Exclusion List for more information.

A single group can be used as the source only within a distributed firewall rule. If IP and Active Directory groups are needed at the source, create two separate firewall rules.

Groups consisting of only IP addresses or MAC Addresses cannot be used in the Applied to text box.

Note: When a host is added to or removed from a vCenter Server, the external ID of the VMs on the host changes. If a VM is a static member of a group and the VM's external ID changes, the NSX Manager UI will no longer show the VM as a member of the group. However, the API that lists the groups will still show that the group contains the VM with its original external ID. If you add a VM as a static member of a group and the VM's external ID changes, you must add the VM again using its new external ID. You can also use dynamic membership criteria to avoid this issue.

For Policy Groups containing IPs, MAC addresses, and Identity Groups the listing API will NOT display the ‘members’ attribute. This applies to Groups containing a combination of static members also. For example, a Policy Group containing IP and VMs, will not display the the members attribute.

For Policy Groups not containing IPs, MAC addresses, or Identity Groups, the member attribute will be displayed in the NSGroup response. However new members and criteria introduced in NSX (such as DVPort and DVPG) will not be included in the MP group definition. Users can view the definition in Policy.

Tags in NSX are case-sensitive, but a group that is based on tags is "case- insensitive." For example, if the dynamic grouping membership criterion is VM Tag Equals 'quarantine', the group includes all VMs that contain either the tags 'quarantine' or 'QUARANTINE'.

If you are using NSX Cloud, see Group VMs using NSX and Public Cloud Tags for information on the how to use public cloud tags to group your workload VMs in NSX Manager.


  1. Select Inventory > Groups from the navigation panel.
  2. Click Add Group, then enter a group name.
  3. If you are adding a group from a Global Manager for NSX Federation, either accept the default region selection, or select a region from the drop-down menu. Once you create a group with a region, you cannot edit the region selection. However, you can change the span of the region itself by adding or removing locations from it. You can create customized regions before you create the group. See Create a Region from Global Manager.
    For groups added from a Global Manager in an NSX Federation environment, selecting a region is mandatory. This text box is not available if you are not using the Global Manager.
  4. Click Set.
  5. In the Set Members window, select the Group Type.
    Group Type Description

    This group type is the default selection. A Generic group definition can consist of a combination of membership criteria, manually added members, IP addresses, MAC addresses, and Active Directory groups.

    Generic groups with only manually added IP address members are not supported for use in the Applied To field in DFW rules. It is possible to create the rule, but it will not be enforced.

    When you define membership criteria in the group, the members are dynamically added in the group based on one or more criteria. Manually added members include objects, such as segment ports, distributed ports, distributed port groups, VIFs, virtual machines, and so on.

    IP Addresses Only

    This group type contains only IP addresses (IPv4 or IPv6). IP Addresses Only groups with only manually added IP address members are not supported for use in the Applied To in DFW rules. It is possible to create the rule, but it will not be enforced.

    If the group type is Generic, you can edit its type to IP Addresses Only group or IP Addresses Only with malicious IPs group. In this case, only the IP addresses are retained in the group. All the membership criteria and other group definitions are lost. After a group of type IP Addresses Only or IP Addresses Only with malicious IPs is realized in NSX, you cannot edit the group type to Generic.

    IP Addresses Only group type is functionally similar to NSGroups with IP Set tag-based criterion in the Manager mode of earlier NSX releases.

    IP Addresses Only with malicious IPs

    If you have enabled Malicious IP Feeds, you can create an IP Addresses Only group with malicious IPs by switching on Add Pre-Defined Malicious IPs. For more information about configuring the feature, see Configure Malicious IP Feeds.

    You can also specify IPs and IP addresses only groups that should be treated as exceptions and must not be blocked.

    Note that once you have switched on the toggle Add Pre-Defined Malicious IPs, you cannot turn it off while editing the group.


    This group type is available only when your NSX environment has one or more Antrea Kubernetes clusters registered to it.

    For more information, see Antrea Groups and Add an Antrea Group.

  6. (Optional) On the Membership Criteria page, click Add Criterion to add members in the generic group dynamically based on one or more membership criteria.

    Starting in NSX 4.1, you can create generic groups with Kubernetes member types in dynamic membership criteria to match traffic entering into or leaving from registered Antrea Kubernetes clusters.

    A membership criterion can have one or more conditions. The conditions can use the same member type or a mix of different member types. In a single membership criterion, conditions based on NSX member types cannot be mixed with conditions based on Kubernetes member types. However, you can have one criterion based on only NSX member types, and another criterion based on only Kubernetes member types, and then join both criteria with an OR operator.

    Some restrictions apply to adding multiple conditions with mixed NSX member types or mixed Kubernetes member types in a membership criterion. To learn more about membership criteria, see Overview of NSX Group Membership Criteria.

    Note: In a multi-tenant NSX environment, Kubernetes cluster resources are not exposed to the project inventory. Therefore, inside a project, you cannot create generic groups with Kubernetes member types in dynamic membership criteria.
  7. (Optional) Click Members to add static members in the group.
    The available member types are:
    • Groups - If you are using NSX Federation, you can add a group as a member that has an equal or smaller span than the region you selected for the group you are creating from the Global Manager, see Security in NSX Federation
    • NSX Segments - IP addresses assigned to a gateway interface, and NSX load balancer virtual IP addresses are not included as segment group members.
    • Segment Ports
    • Distibuted Port Groups
    • Distributed Ports
    • VIFs
    • Virtual Machines
    • Physical Servers
    • Cloud Native Service Instances
  8. (Optional) Click IP/MAC Addresses to add IP and MAC addresses as group members. IPv4 addresses, IPv6 addresses, and multicast addresses are supported.
    Click Action > Import to import IP/MAC Addresses from a TXT file or a CSV file containing comma-separated IP/MAC values.
  9. (Optional) Click AD Groups to add Active Directory Groups. Groups with Active Directory members can be used in the source text box of a distributed firewall rule for Identity Firewall. Groups can contain both AD and compute members.
    Note: If you are using NSX Federation, you cannot create groups from the Global Manager to include AD user groups.
  10. (Optional) Enter a description and tag.
  11. Click Apply
    Groups are listed, with an option to view the members and where the group is used.