2.4.2. Interface settings¶

2.4.2.1. Interface default value¶

In the default settings, any value is not specified.

Port 2 is an interface to be used by the user.

Port 1 is reserved as a required port to offer this menu, and it isn't displayed.

2.4.2.2. Items required for interface configuration¶

The following items are required for interface configuration.

Item	Value	Description
Port	Port[2]	Port No. will be shown. For the WAF feature, Port 2 is shown; this cannot be edit.
Enable Port	✔ (Check)	Check for entering parameters. All values that you have entered will be deleted if you uncheck.
IP Address [CIDR]	XXX.XXX.XXX.XXX/24	Enter an IP address being allocated to a port. Enter the IP address made of that for the Network Id and Subnet Id selected below. Subnet mask should be entered in CIDR format.
MTU Size	1280-9000 [byte]	Specify the relevant MTU Size for the interface. Its default value is 1500 bytes.
Network Id	(select from the list)	Select a Network Id which you want to use from your network list.
Subnet Id	(select from the list)	Select a Subnet Id which you want to use from the list of available subnets on the selected network.
Port Id	(Auto-Assign)	This will be automatically assigned when the settings are applied; this cannot be edit.

Note

If routing is already set up, you can not disable the Enable Port setting. You must disable the Enable Port setting after deleting the routing configuration. The same is true when changing the IP address of the interface to a different subnet, and it is necessary to execute the interface configuration after deleting the routing setting.
If you create a logical network name under specific conditions, the created network will not be displayed. When creating a logical network, see here .

2.4.2.3. Prohibited IP address¶

The following IP addresses cannot be used for interfaces, routes, objects, or lists.

When using any of the IP addresses below are used, operations may not performed properly.

100.65.0.0/16
100.66.0.0/15
100.68.0.0/14
100.72.0.0/14
100.76.0.0/15
100.78.0.0/16
100.80.0.0/13
100.88.0.0/15
100.91.0.0/16
100.92.0.0/14
100.126.0.0/15

2.4.2.4. Preparing the required settings¶

Click [WAF Port Management] displayed on the [Workflows] on [WORKFLOWS] tab to open the [Network Management] details screen.

To enable the user network information to be referred to, click and select the device to be set, and then click [ Get Network Info ].

The Task Status is displayed. When the Get Network Info task turns green, it is successful. Click [Close] to close it.

On the WAF Port Management screen, click [ Manage Interfaces ].

Select "Port2" by clicking, and click [ Edit ].

By checking [ Enable Port ], you can enter values required for the settings.

Enter the setting values, and click [ Save ]. This action only would not apply the settings to the device.

Important

Please make sure to enter the value for "IP Address[CIDR]" in CIDR format as the following example shows.

e.g.)

192.168.2.100/24

[IP Address]+[/]+[Subnet]

After making the port settings, apply those with the procedures described in the following section "Applying the settings".

2.4.2.5. Applying the settings¶

When the necessary port settings have been made, click [ Run Now ] on the Manage Interfaces screen. It takes some times for completing.

The Task Status is displayed. When all the tasks turn green, it is completed normally. Click [Close] to close it.

When a problem occurs (when the status is "red") This will be displayed. Please refer to : ref:` interface - error` .

2.4.2.6. In case of correcting and retrying made on the setting values¶

Important

If the applying process is interrupted before the error is corrected, the user’s Managed WAF will keep its status being in shutdown, unconnected, no updated setting. Please make sure to check the details of the error and correct it before all tasks are completed.

Occurrence of an error results in display like this in [ Task Status ].

If [ Task Status ] has been closed, an error is indicated by [ Status ] of Port Management, and the buttons of Get Network Info and Manage Interface are disabled until the problem is solved.

As clicking on any space where the status and message are displayed, task histories appear.
In the task histories, the status of a process having an error is indicated with red-color, and the error details will be partially shown in the details column.
Click the [ ☰ (status detail indication) ] button located at the right-end of the table.

Regarding an error occurrence task, the [ Continue Task ] button is displayed to the right of Details.

Clicking the [ Continue Task ] button causes the problematic setting screen to be displayed. Refer to the message in Details and correct the setting values.
In the example here, the message says "Below IP Address/MTU inputs are Not OK. Please correct the values before running the Process again. IP Address 192.168.0.100 is not in CIDR format." and indicates the error is caused because the IP address wasn't written in CIDR format. Rewrite the IP address in CIRD format such as "192.168.0.100/24" and retry by clicking [ Run Now ].

You will be returned to the task status screen and the application will resume.

Please wait until the last task is completed normally.

2.4.2.7. Status, task and actions required for correcting errors¶

Here is the descriptions of task status.

Task color		Task status
	(blue)	Task in progress
	(green)	Task completed normally
	(red)	Task with error

The table below shows task name, description and action required for correcting errors. If you have any task having an error, please take appropriate actions such as making inquiries, correcting values and retrying.

Task name	Task description	Action required in case of error occurrence (red-color)
Verify IP Address , MTU Inputs	The allocated IP address (CIDR) will be verified.	An error was detected through verification of the IP address (CIDR). Check the input value, make corrections, and retry.If this task turns red and a message "Subnet xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx（ID number） does not exist." is displayed, there is a possibility that the latest network information could not be obtained, please inform us via the Enterprise Cloud 2.0 ticket system.
Stop Ping Monitoring	Ping Monitoring is temporarily halted before application of the port setting.	When temporary halt of Ping Monitoring fails, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Stop the WAF	When the setting applying process is started, your Managed WAF will be shutdown temporally. (It will kept being shutdown until the Start the WAF task is completed.)	An error occurred on the shutdown process, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Wait for WAF Ping unreachability from MSA	Your Managed WAF's connectivity termination will be checked.	An error occurred on the connection verification process, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Delete Ports	To apply the setting, delete the port firstly.	An error occurred on the deleting the ports, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Create Ports	New ports will be created.	An error occurred on the port create process, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Attach Ports	The created ports will be attached.	An error occurred on the port attachment process, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Start the WAF	Your Managed WAF will be booted.	An error occurred on the starting process, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Wait for WAF Ping Reachability from MSA	Your Managed WAF's connectivity will be checked.	An error occurred on the connection verification process, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Wait for WAF SSH Connectivity from MSA	Your Management WAF's SSH connectivity will be checked.	An error occurred on the SSH process, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Update WAF	Your Managed WAF settings will be refreshed.	An error occurred on the configuration updating process, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Device Backup	Save the changed settings to the system.	An error occurred on the system, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.
Start Ping Monitoring	Ping Monitoring is resumed after application of the port setting.	When resume Ping Monitoring fails, the indicator turns red. Please retry after 10 minutes or so. In case the error failed to be corrected, please inform us via the Enterprise Cloud 2.0 ticket system.

Note

If the applying process is interrupted before the error is corrected, the user’s Managed WAF will keep its status being in shutdown, unconnected, no updated setting.
If problems occur, refer to the above table and implement necessary measures.

2.4.1. Basic Settings

2.4.3. Routing settings