Contents

Configuring common container and open application parameters· 1

About configuring common container and open application parameters· 1

Configuring common container parameters· 1

Backing up container data· 1

Configuring common open application parameters· 1

Specifying a source IP address for open applications· 1

Reserving port numbers for open client applications· 2

Reserving port numbers for open server applications· 3

Preconditioning incoming IP packets· 3

 

Configuring common container and open application parameters

About configuring common container and open application parameters

Comware V9 supports deploying the Guest Shell container and Docker containers as well as applications based the containers or RPM on the device. The container applications and RPM applications can run on the device if only they are compliant with the packaging, orchestration, and running requirements of the containers or RPM. These applications feature high openness and are hereinafter referred to as "open applications" in this chapter.

Container applications are isolated from Comware applications. You can use container applications as supplements to Comware, without affecting the operating of Comware.

This chapter describes how to configure common parameters for the previously mentioned containers and open applications.

Configuring common container parameters

Backing up container data

About this task

This task backs up Guest shell container data and Docker container data to the standby MPU so the containers can continue to use the data after an active/standby switchover.

Procedure

1.     Enter system view.

system-view

2.     Back up Guest Shell container data and Docker container data.

tpa data sync

Configuring common open application parameters

Specifying a source IP address for open applications

About this task

For the following applications to communicate with indirectly connected networks, you must specify a source IPv4 or IPv6 address for their outgoing packets:

·     RPM applications.

·     Guest Shell container applications.

·     Open applications in containers that share the network namespace of Comware.

The applications will use the specified address as the source address for packets that they send.

Open applications in containers that do not share the network namespace of Comware uses interface Virtual-Eth-Group 0 to communicate with indirectly connected networks. You do not need to configure a source IP address for such open applications.

Restrictions and guidelines

Make sure the specified interface has an IP address and is in up state, and a connection is available between the interface and the destination device.

As a best practice, specify a loopback interface as the source interface. The physical layer status of a loopback interface is always up unless the loopback interface is manually shut down.

The specified source IPv6 address must be an IPv6 global unicast address.

Procedure

1.     Enter system view.

system-view

2.     Specify a source IP address for open applications.

IPv4:

Specify a source interface in system view to use the primary IPv4 address of the interface as the source IPv4 address.

tpa ip source interface interface-type interface-number

By default, the primary IPv4 address of interface Loopback 0 is used as the source IPv4 address.

IPv6:

Specify a source interface or source IPv6 address in system view.

tpa ipv6 source { interface interface-type interface-number | ipv6 ipv6-address }

By default, an IPv6 address of interface Loopback 0 is used as the source IPv6 address.

Reserving port numbers for open client applications

About this task

The device forwards received packets to applications based on the destination port numbers in the packets. To avoid port conflicts and to correctly forward packets destined for open client applications, you must reserve port numbers for the open client applications.

Restrictions and guidelines

As a best practice, configure this feature before running open applications.

The number of reserved port numbers must be an even number.

The reserved port numbers cannot include the port numbers being used by Comware client applications. Before reserving port numbers for open client applications, execute the following commands to identify the TCP and UDP port numbers that Comware applications are using:

·     display system internal tcp port-info

·     display system internal udp port-info

To change the reserved port number range while one or more open client applications are running:

1.     Identify whether the new range includes the port numbers that the open client applications are using.

2.     If not, stop the open client applications that are using an out-of-range port number. You can restart the applications after you change the reserved port number range.

Procedure

1.     Enter system view.

system-view

2.     Specify the range of port numbers to be reserved for open client applications.

tpa socket client-port-range start-port end-port

By default, no port numbers are reserved for open client applications.

Reserving port numbers for open server applications

About this task

The device forwards received packets to applications based on the destination port numbers in the packets. To avoid port conflicts and to correctly forward packets destined for open server applications, you must reserve port numbers for the open server applications.

Restrictions and guidelines

The reserved port numbers cannot include the port numbers being used by Comware client applications. Before reserving port numbers for open server applications, execute the following commands to identify the TCP and UDP port numbers that Comware applications are using:

·     display system internal tcp port-info

·     display system internal udp port-info

Procedure

1.     Enter system view.

system-view

2.     Specify the range of port numbers to be reserved for open server applications.

tpa socket server-port port-id1 [ to port-id2 ]

By default, no port numbers are reserved for open server applications.

Preconditioning incoming IP packets

About this task

By default, the device processes received open application packets as follows:

·     Unicast packets that are destined for the device itself—Sends the packets to CPUs.

·     Broadcast packets—Sends the packets to CPUs.

·     Multicast packets—Does not send the packets to CPUs.

You can configure the device to precondition open application packets that match certain rules and then send the packets to its CPUs. Preconditioning actions include rate limiting packets to prevent open application packets from using too many CPU resources.

Restrictions and guidelines

If you configure this feature in interface view, the configuration applies to the current interface. If you configure this feature in system view, the configuration applies to all interfaces. If you configure this feature in both interface view and system view, the device preconditions open application packets that match the rules configured in either view.

Procedure

1.     Enter system view.

system-view

2.     Configure the device to precondition certain incoming IPv4 packets of open applications and send the packets to its CPUs.

IPv4:

¡     Configure the device to precondition incoming IPv4 open application packets and send the packets to its CPUs in system view.

tpa ip send-to-cpu protocol protocol-number [ destination-port destination-port-number | source-port source-port-number ] * [ destination-ip destination-ip-address ]

By default, the device processes incoming open application IPv4 packets as follows:

-     Unicast packets that are destined for the device itself—Sends the packets to CPUs.

-     Broadcast packets—Sends the packets to CPUs.

-     Multicast packets—Does not send the packets to CPUs.

¡     Execute the following commands in sequence to enter interface view and configure the device to precondition incoming IPv4 open application packets and send the packets to its CPUs.

interface interface-type interface-number

tpa ip send-to-cpu protocol protocol-number [ destination-port destination-port-number | source-port source-port-number ] * [ destination-ip destination-ip-address ]

By default, the configuration in system view is used.

IPv6:

¡     Configure the device to precondition incoming IPv6 open application packets and send the packets to its CPUs in system view.

tpa ipv6 send-to-cpu protocol protocol-number [ destination-port destination-port-number | source-port source-port-number ] * [ destination-ipv6 destination-ipv6-address ]

By default, the device processes incoming open application IPv6 packets as follows:

-     Unicast packets that are destined for the device itself—Sends the packets to CPUs.

-     Multicast packets—Does not send the packets to CPUs.

¡     Execute the following commands in sequence to enter interface view and configure the device to precondition incoming IPv6 open application packets and send the packets to its CPUs.

interface interface-type interface-number

tpa ipv6 send-to-cpu protocol protocol-number [ destination-port destination-port-number | source-port source-port-number ] * [ destination-ipv6 destination-ipv6-address ]

By default, the configuration in system view is used.