Contents

Configuring object groups· 1

About object groups· 1

vSystem support for features· 1

Restrictions and guidelines: Object group configuration· 1

Configuring a MAC address object group· 1

Configuring an IPv4 address object group· 2

Configuring an IPv6 address object group· 3

Configuring a service object group· 3

Renaming an object group· 4

Configuring aging of DNS-resolved IP addresses from host names· 4

Display and maintenance commands for object groups· 5

 

Configuring object groups

About object groups

An object group is a group of objects that can be used by an ACL, object policy, or object group to identify packets. Object groups are divided into the following types:

·     MAC address object group—A group of MAC address objects used to match the MAC address in a packet.

·     IPv4 address object group—A group of IPv4 address objects used to match the IPv4 address in a packet or match the user from whom a packet comes.

·     IPv6 address object group—A group of IPv6 address objects used to match the IPv6 address in a packet or match the user from whom a packet comes.

·     Service object group—A group of service objects used to match the upper-layer service in a packet.

vSystem support for features

Non-default vSystems do not support configuring aging of DNS-resolved IP addresses from host names.

For information about the support of non-default vSystems for the commands, see object group command reference. For information about vSystem, see Virtual Technologies Configuration Guide.

Restrictions and guidelines: Object group configuration

You cannot edit an object group if the group is used by a global static NAT rule.

Address object groups and service object groups for a Yundi network can only use other existing object groups. You cannot create objects for Yundi address or service object groups.

Configuring a MAC address object group

1.     Enter system view.

system-view

2.     Create a MAC address object group and enter its view.

object-group mac-address object-group-name

The system has one default IPv4 address object group named any.

3.     (Optional.) Configure a description for the MAC address object group.

description text

By default, an object group does not have a description.

4.     (Optional.) Specify an alias and tenant ID for the MAC address object group in a Yundi network.

yundi alias alias tenant tenant-id

By default, the alias and tenant ID are not specified.

Typically, the alias and tenant ID are deployed by the remote controller to devices. As a best practice, do not perform this task manually on devices.

5.     Configure a MAC address object.

[ object-id ] mac { mac-address | group-object group-object-name }

6.     Configure a description for the MAC address object.

object object-id description text

By default, a MAC address object group does not have a description.

Configuring an IPv4 address object group

1.     Enter system view.

system-view

2.     Create an IPv4 address object group and enter its view.

object-group ip { address | address-yundi } object-group-name

The system has one default IPv4 address object group named any.

3.     (Optional.) Configure a description for the IPv4 address object group.

description text

By default, an object group does not have a description.

4.     (Optional.) Specify an alias and tenant ID for the IPv4 address object group in a Yundi network.

yundi alias alias tenant tenant-id

By default, the alias and tenant ID are not specified.

Typically, the alias and tenant ID are deployed by the remote controller to devices. As a best practice, do not perform this task manually on devices.

5.     Configure an IPv4 address object.

[ object-id ] network { host { address ip-address | name host-name [ vpn-instance vpn-instance-name ] } | subnet ip-address { mask-length | mask | wildcard wildcard } | range ip-address1 ip-address2 | group-object object-group-name | user user-name [ domain domain-name ] | user-group user-group-name [ domain domain-name ] }

6.     Configure a description for the IPv4 address object.

object object-id description text

By default, an IPv4 address object does not have a description.

7.     Exclude an IPv4 address from the IPv4 address object.

object-id network exclude  ip-address

By default, no IPv4 address in an IPv4 address object is excluded.

8.     Exclude an IPv4 address, range, or subnet from the IPv4 address object group.

exclude { host ip-address | range ip-address1 ip-address2 | subnet ip-address { mask-length | mask } }

By default, no IPv4 address is excluded from an IPv4 address object group.

9.     (Optional.) Specify a security zone for the IPv4 address object group.

security-zone security-zone-name

By default, no security zone is specified for an IPv4 address object group.

Configuring an IPv6 address object group

1.     Enter system view.

system-view

2.     Create an IPv6 address object group and enter its view.

object-group ipv6 { address | address-yundi } object-group-name

The system has one default IPv6 address object group named any.

3.     (Optional.) Configure a description for the IPv6 address object group.

description text

By default, an object group does not have a description.

4.     (Optional.) Specify an alias and tenant ID for the IPv6 address object group in a Yundi network.

yundi alias alias tenant tenant-id

By default, the alias and tenant ID are not specified.

Typically, the alias and tenant ID are deployed by the remote controller to devices. As a best practice, do not perform this task manually on devices.

5.     Configure an IPv6 address object.

[ object-id ] network { host { address ipv6-address | name host-name [ vpn-instance vpn-instance-name ] } | subnet ipv6-address prefix-length | range ipv6-address1 ipv6-address2 | group-object object-group-name | user user-name [ domain domain-name ] | user-group user-group-name [ domain domain-name ] }

6.     Configure a description for the IPv6 address object.

object object-id description text

By default, an IPv6 address object does not have a description.

7.     Exclude an IPv6 address from the IPv6 address object.

object-id network exclude  ip-address

By default, no IPv6 address in an IPv6 address object is excluded.

8.     Exclude an IPv6 address, range, or subnet from the IPv6 address object group.

exclude { host ipv6-address | range ipv6-address1 ipv6-address2 | subnet ipv6-address prefix-length }

By default, no IPv6 address is excluded from an IPv6 address object group.

9.     (Optional.) Specify a security zone for the IPv6 address object group.

security-zone security-zone-name

By default, no security zone is specified for an IPv6 address object group.

Configuring a service object group

1.     Enter system view.

system-view

2.     Create a service object group and enter its view.

object-group { service | service-yundi } object-group-name

The system has multiple default service object groups.

3.     (Optional.) Configure a description for the service object group.

description text

By default, an object group does not have a description.

4.     (Optional.) Specify an alias and tenant ID for the service object group in a Yundi network.

yundi alias alias tenant tenant-id

By default, the alias and tenant ID are not specified.

Typically, the alias and tenant ID are deployed by the remote controller to devices. As a best practice, do not perform this task manually on devices.

5.     Configure a service object.

[ object-id ] service { protocol [ { source { { eq | lt | gt } port | range port1 port2 } | destination { { eq | lt | gt } port | range port1 port2 } } * | icmp-type icmp-code | icmpv6-type icmpv6-code ] | group-object object-group-name }

6.     Configure a description for the service object.

object object-id description text

By default, a service object does not have a description.

Renaming an object group

1.     Enter system view.

system-view

2.     Rename an object group.

object-group rename old-object-group-name new-object-group-name

You can only rename non-default object groups.

Configuring aging of DNS-resolved IP addresses from host names

About this task

In load balancing scenarios where one host name maps to several IP addresses, DNS-resolved IP address for a host name changes between these mapping addresses. Upon every change, the object group module notifies relevant policies (such as security policy) of the change, which causes policies to submit changes frequently and consumes memory. To resolve this issue, you can enable aging of DNS-resolved IP addresses from host names.

With this feature enabled, the system maintains an IP address group for each host name. If a resolved IP address is not in the group, the system adds the address to the group and notifies relevant policies of the change. If a resolved IP address is in the group, the system does not notify relevant policies.

Restrictions and guidelines

As a best practice, set the aging time to be longer than the TTL of resolution records on the DNS server.

Procedure

1.     Enter system view.

system-view

2.     Enable aging of DNS-resolved IP addresses from host names.

object-group dns-aging [ time aging-time ]

By default, aging of DNS-resolved IP addresses from host names is disabled.

Display and maintenance commands for object groups

Execute display commands in any view.

 

Task	Command
Display information about object groups.	display object-group [ { { ip | ipv6 } address | mac-address | service } [ default ] [ name object-group-name ] | name object-group-name ]
Display IPv4 or IPv6 addresses for host names.	display object-group { ip | ipv6 } host { object-group-name object-group-name | name host-name [ vpn-instance vpn-instance-name ] } *

‌