set public-interface

Application Scenarios

When the bandwidth of a virtual system is limited based on the resource class, the traffic statistics of the virtual system are based on the public interface.

The public interface is not the interface connecting the FW to the Internet. It is the interface on which the set public-interface command is run. A private interface is the interface on which the set public-interface command is not run.

• Inbound traffic: The traffic from a public interface to a private interface. It is limited by the inbound bandwidth. The command for configuring the inbound bandwidth resources is resource-item-limit bandwidth bandwidth inbound.
• Outbound traffic: The traffic from a private interface to a public interface. It is limited by the outbound bandwidth. The command for configuring the outbound bandwidth resources is resource-item-limit bandwidth bandwidth outbound.
• Entire traffic: Total traffic on a virtual system = Inbound traffic + Outbound traffic + Traffic from a private interface to a private interface + Traffic from a public interface to a public interface. The entire traffic is limited by the entire bandwidth. The command for configuring the entire bandwidth resources is resource-item-limit bandwidth bandwidth entire.

Therefore, when limiting the bandwidth of a virtual system based on the inbound and outbound bandwidths of the resource class, you must run the set public-interface command to specify the public interface for the virtual system.

If the bandwidth of a virtual system is only limited by the entire bandwidth of the resource class, you may not specify the public interface for the virtual system. When no public interface is specified, all traffic flows from a private interface to a private interface, and the traffic is counted in the entire traffic.

Precautions

In inter-virtual system forwarding scenarios, the Virtual-IF interface is a public interface by default.