2.1.16.2. HA Configuration Network Management

2.1.16.2.1. Interface Settings

2.1.16.2.1.1. Default Value : Interface

By default, any interface has been set up.

Port 1 is reserved in advance as a necessary port for this menu. This is not shown.
Port 2 and 3 are necessary ports for HA Configuration. The message indicates these ports have been set in advance; the user cannot change this setting.
[ Port 4 - Port 10 ] are interfaces available for customers.

2.1.16.2.1.2. Setting Items : Interface

Following are the setting items as described follows:

Items

Values

Description

Port

[ Port 4- Port 10 ]

Port number is shown. Edit is unable.

Enable Port

[ ✔ ] (Marking to the checkbox)

Marking to the [ Enable Port ] box allows you to input parameters.
On the other hand, if you have unmarked to the checkbox, the inpute value will clear.
MTU Size 100-1500 [byte]
Specify MTU size of the interface
Default is 1500 bytes.

Device ID

UTM-XXXXXX
The user's device name for each HA pair device name is shown.
The user cannot edit.
IP Address [CIDR] XXX.XXX.XXX.XXX/24
Input an IP Address being assigned to a port.
You need to specify any IP address, by selecting from the following IP address range of the Subnet ID & the Network ID.
For subnet masks, you need to input ones in CIDR format.

For HA Configuration, IP address will be allocated to each HA pair device.

Network ID

( Select from the List )

Select any Network ID, which you want to use, from your Network list.

Subnet ID

( Select from the List )

Select a specific Subnet ID from the available Subnet list in your selected Logical Network.

VRRP Group ID

( Select from the List )

Select VRRP Group ID

Use the same Group ID to all interfaces.
All interfaces under the same Group ID will operate in synchronism to match Master-Slave. For example, when the External side of an interface fails over, the Internal side of the interface under the same Group ID will fails over.
VRRP ID

( Select from the List )

Select VRRP ID.

Each interface requires individual VRRP ID.
If the user employs VRRP to the other device used in a pair, it is necessary to select a different VRRP ID for it.
VRRP IP XXX.XXX.XXX.XXX
Enter IP address of VRRP.
Subnet mask is not required.
Virtual MAC XX:XX:XX:XX:XX:XX
After the user completes the setting of Manage Interfaces, a Virtual MAC address is automatically allocated.
The user cannot edit.
Preempt

[ ✔ ] (Marking to the checkbox)

The user can choose whether applying the Preempt mode or not. By marking the checkbox, the Preempt mode turns on.

With the Preempt mode, fail back is automatically performed at the timing when the device recognizes the preconditions for it.
If devices are under the same Group ID, the Preempt mode status of those should be matched.
Comment

(Half-width alphabetic characters & half-width numbers)

The user can put comments.
Fill in your comment by using less than 225 letters. You can NOT utilize any two-bytes characters, such as Japanese.

Note

  • When using VRRP, "enable" the DHCP function (address setting function) of the logical network to be connected.
    If the DHCP function has been "disabled", an ARP request is executed with source address 0.0.0.0 with respect to the network of NTT Com.
    It has been confirmed through an NTT-supplied Load Balancer, Managed FW/UTM, and others that an ARP reply is not returned in this case. Redundancy by VRRP is affected and communication disconnection may be continued when switching is made.

2.1.16.2.1.3. Unauthorized IP addresses

The following IP addresses are not available for Interface, Routing, Address objects, Destination NAT and Source NAT.
When using these IP addresses, the operation may cause an error.
  • 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.1.16.2.1.4. Prohibit VRRP ID

Following VRRP ID cannot be used as Managed Firewall/UTM and the devices connected to Managed Firewall/UTM.
  • ID 11(Virtual MAC address00:00:5e:00:01:0b)


2.1.16.2.1.5. Preparing for a New Settings

  1. Click [ Cluster Port Management ] at the [ Network Management ], the details in the [ Network Management ] will appear.
    In case of HA Configuration, [UTM Port Managemen] is not used.
    TOP

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

  1. [ Task Status ] is displayed. When completed normally, the task status of "Get Network Info" turns green. Click [x] to close the window.
    Task Status

  1. Select the target HA pair for setting by clicking, and click [ Manage Interfaces ].
    The user can click any port number as they open the same screen.
    デバイス選択

  1. The [ Manage Interface ] screen will be opened. In the screen, Port 2 and 3 are not shown.
    Select the target port for setting, then click [ Edit ].
    Manage Interfaces

  1. Enter the setting value by ticking [ Enable Port ].
    ポート設定

  1. Select each device and press [Edit].
    各デバイス選択

  1. Enter the real IP address to be set for each device, and click [Save].
    各デバイスの実IP設定

Note

The [IP Address[CIDR]]needs to be input with the CIDR style as the example below.
Example:
192.168.2.100/24
[IP Address]+[/]+[Subnet]

  1. Enter the setting value.
    各デバイスのネットワークID等を入力

Note

Please remind the issues below when entering the setting value.
  • Actual IP Address and Virtual IP Address (VRRP IP) for Each Device
    As the example below shows, allocate an actual IP address to each device. And set a virtual IP address (VRRP) for it as well.
    Example:
    Enter 192.168.2.101/24 for the first device.
    Enter 192.168.2.102/24 for the second device.

    If there is the indication as IP Address[CIDR], use the CIDR style.
    Format in the CIDR style: IP address/subnet (prefix length)
    For VRRP IP address, enter the IP address simply without using the CIDR style.
  • VRRP Group ID
    VRRP Group ID is used to track the status (Master and Slave) on all interfaces using the same Group ID.
    Use the same Group ID for the interface setting VRRP, which allocated to Port 4 - 10 in the same device (within a HA pair). If any different Group ID is used, operation may fail in case failover or relevant problem occurs.
  • VRRP ID
    VRRP ID is linked with virtual MAC address. VRRP ID and the allocated virtual MAC to the ID is commonly defined among companies in accordance with the rules below:
    VRRP ID

    Virtual MAC Address

    1 00:00:5e:00:01:01
    2 00:00:5e:00:01:02
    ... ...
    10 00:00:5e:00:01:0a
    ... ...
    20 00:00:5e:00:01:14
    ... ...
    70 00:00:5e:00:01:46
    If VRRP is used at the other device in pair of Managed Firewall and Managed UTM, each device needs different VRRP ID independently. When both devices use the same VRRP ID, they cannot communicate normally.
  • ID 11 (virtual MAC address 00: 00: 5e: 00: 01: 0b) can not be used as the VRRP ID of the Managed Firewall / UTM and adjacent devices.

  1. After inputting the setting value, click the [ Save ] button. The saved data is not applied to the device with only this action.

    ポート設定保存

Once you have prepared for the port settings, please accordingly apply for the new settings by following the procedure of [ Applying configuration ].


2.1.16.2.1.6. Applying the new Settings

The process for setting applying is commonly used for single configuration and HA configuration.

  1. Once you have prepared a port being utilized, click [ NOW RUN ] at the Manage Interface screen.
    ポート設定適用

  1. [ Task Status ] is displayed.
    ポート設定適用3

    Following describes respective task statuses.

    Task Colors

     

    Task Status

    Gray

    [ Gray ]

    Unexcuted Task

    Blue

    [ Blue ]

    Processing Task

    Green

    [ Green ]

    Task completed normally

    Red

    [ Red ]

    Task with Unknown-Issues.


  1. When completed normally, all statuses turn green. Click [x] to close the window.
    ポート設定適用4

2.1.16.2.1.7. Task Status and Error Solution (Red)

Note

Any error (red status) caused at applying the interface setting may negative impacts on the user's communication. 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.
ステータスエラー

If clicking the area which show [ Status ] and [ Message ], the history is displayed. On the history, the status of an error occurrence process turns red, and part of the error information is displayed in [ Details ] area.
To recover from the error, click [ Status Detail Display ] at the right end, followed by display of [ Task Status ].
ポート設定適用4

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 above where "Below IP Address / MTU inputs are Not OK. Please correct the values before running the Process again. IP Address XXX.XX.XX.XX is not in CIDR format." is shown, click the [ Continue Task ] button, correct the IP address, and then click [ Run Now ] again.

Note

In case of the example above, the error message was brought because IP Address[CIDR] was not in the CIDR style.
The [IP Address[CIDR]]needs to be input with the CIDR style as the example below.
Example:
192.168.2.100/24
[IP Address]+[/]+[Subnet]

Click [ Run Now ] after your updating settings, then Tasks Status screen will get back. [ Applying Configuration ] will resume.
Wait for a moment until the last task is completed normally.
実行ステータス3

Click [ × ] at the [ Task Status ] screen as shown below:
実行ステータス4

This section explains task status. When a red status appears, check the task's name (status), details and necessary actions on incident occurrence in the table below. Then, execute retry.

Note

  • If the applying process is interrupted before the error is corrected, the user's Managed Firewall/UTM will keep its status being in shutdown, unconnected, no updated setting.

  • In case the error failed to be corrected by retrying, please inform us via the Enterprise Cloud 2.0 ticket system.


Task Name

Task Description

Necessary Action at Incident Occurrence (Red Status)

Set Context for First UTM

In the case of HA configuration, the environment for the first unit is prepared. The same tasks are executed in terms of the procedures from Verify to Attach Ports and the procedures from Start the UTM to Update UTM Proxy ARP.

When an error occurs during environment preparation, 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.
Set Context for Second UTM

In the case of HA configuration, the environment for the second unit is prepared. The same tasks as for the first unit are executed in terms of the procedures from Verify to Attach Ports and the procedures from Start the UTM to Update UTM Proxy ARP.

When an error occurs during environment preparation, 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.
Verify IP Address Inputs
The IP address (CIDR) to be set is verified. In the case of HA configuration, it is also verified that DHCP is effective on the connected network.
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 "Logical Network connecting to Managed Firewall/UTM must be [DHCP ON]." is displayed with respect to HA configuration, check the network environment of the user. Then, if DHCP is found to be ineffective, make it effective 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.
Verify VRRP, MTU Inputs

VRRP and MTU to be set are verified.

When an error is detected through verification, the indicator turns red. Check the input value, make corrections, and retry.

Import Ports

In case of HA Configuration, import ports information at the beginning of the process.

An error occurred on the port setting 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.
Stop the UTM
When starting the setting applying process, the user's Managed Firewall/UTM is temporally shutdown. (It will keep being in shutdown until Start the UTM 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.

Please wait for UTM Ping Reachability from MSA.

Verify the connection status of the user's Managed Firewall/UTM.

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.
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.
Delete Ports

Ports will be deleted in order to apply the settings.

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

Create a new port.

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

Attach the created ports.

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 UTM

Start the user's Managed Firewall/UTM.

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.

Please wait for UTM Ping Reachability from MSA.

Verify the connection status of the user's Managed Firewall/UTM.

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.
Update UTM (Interfaces)

Update configuration of Managed Firewall / UTM interfaces.

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.
Update UTM Proxy ARP

In HA Configuration, update Proxy ARP configuration of Managed Firewall / UTM.

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 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.

Confirm all tasks have been completed normally (green status).

2.1.16.2.2. Routing Settings

Set up a static route for each device.
For HA Configuration, routing is made at the [ Network Management ].
Click [ Cluster Route Management ].
For HA Configuration, the user can see the setting details, which are made at [ Cluster Route Management ] in the [ Network Management ], at [ Routing ] in the [ Device Management ].
Cluster Route Management

2.1.16.2.2.1. Routing Default Value

At the default setting, any routing for the user network is not made.
By default, any gateway have not been set up. You need to set up a default gateway depending on your own environment.

2.1.16.2.2.2. Routing : Setting Items

The following items are necessary for the routing settings.

Items

Values

Description

ID

(Auto-Assign)

This ID is automatically assigned.

Destination IP Address

xxx.xxx.xxx.xxx

Input a Destination IP Address with decimal notation.

Mask xxx.xxx.xxx.xxx

Input the Destination Subnet mask with decimal notation.

Gateway

xxx.xxx.xxx.xxx

Input the Routing Gateway IP Address with decimal notation.

Interface

[ Port 4- Port 10 ]

You need to select a port to which this Routing will be set up.

Comment

(Half-width alphabetic characters & half-width numbers)

Fill in your comment if you like.
Fill in your comment by using less than 225 letters. You can NOT utilize any two-bytes characters, such as Japanese.

Note

Default Gateway

  • If you would like to set up a new default gateway, you need to firstly input {Destination IP 0.0.0.0] & [ Mask 0.0.0.0] to specify the Gatewaty address and an Interface.


2.1.16.2.2.3. Unauthorized IP addresses

The following IP addresses are not available for Interface, Routing, Address objects, Destination NAT and Source NAT.
When using these IP addresses, the operation may cause an error.
  • 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.1.16.2.2.4. Creating Additional Routing

  1. Click [ Manage Routes ] of [ Cluster Route Management ] shown in the [ Network Management ].
    Cluster Route Management

  1. Click [ Add ].
    Manage Routes

  1. Enter the setting value, and click [ Save ].
    For the details of setting items, please refer to Routing : Setting Items.
    parameters

  1. When the setting is ready, click [ Run Now ] to start applying.
    For the details of applying methods, please refer to Applying the new Settings.
    parameters

2.1.16.2.2.5. Routing Modification

  1. Click [ Manage Routes ] of [ Cluster Route Management ] shown in the [ Network Management ].
    Cluster Route Management

  1. Select the target lines to be modified, and click the relevant button for operation.
    Manage Routes

    Descriptions of each button's function at the [ Manage Routes ]

    Buttons

    Description

    Edit

    The user can modify the routing setting value that has already entered.

    Remove

    The user can delete the selected routing setting.


  1. When the setting is ready, click [ Run Now ] to start applying.
    For the details of applying methods, please refer to Applying the new Settings.
    parameters

2.1.16.2.3. Configure Proxy ARP

Configure Proxy ARP to a device.
Proxy ARP is configured at [Cluster Port Management] screen of [Network Management].

Configuration that is required Proxy ARP setting

Configuration that is not required Proxy ARP setting``

If NAT setting IP address is in the same as the network which interface connected to
in HA Configuration,
Proxy ARP setting is required.
.
If NAT setting IP address is not in the same as the network to which interface connected
even in HA Configuration,
Proxy ARP setting is NOT required.
.
Example:
Proxy ARP Setting

When using .100 as the IP address of NAT from the network 192.168.1.0/24 to which the interface is connected
Example:
Proxy ARP No Setting

When using an address different from the network 192.168.1.0/24 to which the interface is connected 192.168.2. × as the IP address of the NAT

2.1.16.2.3.1. Default value of Proxy ARP

By default, any interface has been set up.
Please configure according to customer's environment.

2.1.16.2.3.2. Configure items of Proxy ARP

Proxy ARP need to be configured per Interface(Port).
Following shows the list of setting items in Proxy ARP.

Items

Values

Description

ID

(Auto-Assign)

This ID is automatically assigned.

IP Address xxx.xxx.xxx.xxx
It is the IP address to be checked against the virtual MAC (VMAC) by the proxy ARP function.
Specify with a single IP address or range. For a range, you can connect the start address and the end address with a hyphen.
  • Example of a single IP address) 192.168.2.100

  • Example of a range IP address) 192.168.2.101-192.168.2.130

Up to 100 ID can be created per one interface.
The maximum number of IP addresses is 256 per interface. Even when specifying by range, the number within that range is counted.
In following example, the ID is counted as 2 and the IP address is counted as 31.
Example:
ID1: 192.168.2.100
ID2: 192.168.2.101-192.168.2.130

2.1.16.2.3.3. Add Proxy ARP

  1. Click [ Manage Proxy ARP ] of [ Cluster Port Management ] shown in the [ Network Management ].
    Cluster Route Management

  1. Select configure target interface (Port), then click [Edit].
    Manage Proxy ARP

  1. Click [ Add ].
    Add Proxy ARP

  1. Enter the setting value, and click [ Save ].
    For the details of setting items, please refer to Configure items of Proxy ARP .

  1. When the setting is ready, click [ Run Now ] to start applying.
    For the details of applying methods, please refer to Applying the new Settings.

2.1.16.2.3.4. Change Proxy ARP

  1. Click [ Manage Proxy ARP ] of [ Cluster Port Management ] shown in the [ Network Management ].
    Cluster Route Management

  1. Select configure target interface (Port), then click [Edit].
    Manage Proxy ARP

  1. Click on the line you want to change and click on one of the change operation buttons.
    Change Proxy ARP

    Descriptions of each button's function at [ Manage Proxy ARP ].

    Buttons

    Description

    Edit

    Update parameter of Proxy ARP already configured.

    Remove

    Delete configuration of selected Proxy ARP.


  1. Change or delete parameter, then click [Save].
    For the details of setting items, please refer to Configure items of Proxy ARP .

  1. When the setting is ready, click [ Run Now ] to start applying.
    For the details of applying methods, please refer to Applying the new Settings .

2.1.16.2.4. Device Stop / Start

It is a procedure to stop or start the customer's Managed FW/UTM of HA configuration plan.
In the HA configuration plan, Stop and Start the First Unit or Second Unit separately.

On the Cluster Port Management screen, click [Stop / Start UTM] that you want to stop / start.
StopStart1 HA

Since the Stop/Start First Unit (Stop/Start Second Unit) screen is displayed, click [ Run Now ].
The image is for First Unit, but it is the same for Second Unit.
StopStart2 HA

The Tasks status screen is displayed. It does not start automatically after stop. "Pause" turns yellow.
If you want to start the device, click [ Continue Task ].
StopStart TaskStatus1 HA
If "Pause" is yellow and the task status is closed, you can restart from "Live Console".

Since the Stop/Start First Unit (Stop/Start Second Unit) screen is displayed, click [ Run Now ].
StopStart TaskStatus2 HA

"Pause" turns green and device startup starts. Please wait until "Start Ping Monitoring" turns green.
StopStart TaskStatus3 HA

Close the Tasks status screen with [x].

2.1.16.2.5. Other features

Status
Click the [ Status ] on the [ Network Management ] - [ Service Details ] screens to display the execution histories of Management Interfaces and Refresh Interfaces.
Port Management2

At the history screen, when you click [ task status ], the [ Task Status ] screen will display, showing the history of executed tasks.
ステータス画面

In the history at [ Tasks status ], the light of the task icon with any problem turns red. In this case, you can retry the task after completely modifying and resolving problems. By doing so, you can also make sure that the task has correctly restart to complete if the task icon light turns green, as below:
タスク履歴

Live Console
Click the [ Live Console ] on the [ Network Management ] - [ Service Details ] screens to open [ Task Status ] directly.
ライブコンソール

Details
Click the [ Details ] on the [ Network Management ] - [ Service Details ] screens to display/hide the lower section.
詳細表示

Dashboard
Click the graph button on the [ Network Management ] - [ Service Details ] screens to display the process history and the status history by graph.
プロセス履歴

On the Dashboard screen, the user can choose either [ a week ago ] or [ a month ago ].
Click [ Port Management ] at the left pane to the previous screen.
プロセスタイムライン

Narrowing down display
Devices to be displayed can be narrowed down by inputting a device name into the Search field shown by selecting [ Network Management ] - [ Service Details ].
The numeric value shown for Max rows indicates the number of lines for display. After finishing input and changes, move the cursor outside the field (the Enter key does not serve for execution).
絞り込み

2.1.16.2.6. Ping Execution

In [Ping Execution] , customer can ping to any IPaddress from customer's Managed Firewall/UTM/WAF instance.

Click on [Network Management] - [Ping Execution].
Ping Execution

Click on [Execute Ping].
Execute Ping

Select Ping target device by [Device ID] and input target IPaddress, then click [Execute Now].
Execute Ping

Once Ping is completed, the result will appear.
Ping Status

Detail of result can be checked at [Live Console].
Tasks status

2.1.16.2.7. Device Config Export

[Device Config Export] can output the contents set by Device Management to the CSV file for each device.

Click the [ Device Config Export ] on the [ Network Management ] screen
../../../../_images/nw_config_export01.png

Click [Export Config].
../../../../_images/nw_config_export02.png

Select target device by [Device ID] , and click [ Run Now ].
../../../../_images/nw_config_export03.png

The Tasks status screen is displayed.Please wait until "Export Config" turns green.Close the Tasks status screen with [x].
../../../../_images/nw_config_export04.png

For the created file, you can check it at : doc: 2000_doc .
../../../../_images/nw_config_export05.png

Note

  • By reloading the browser it will be reflected in : doc: 2000_doc .

Please refer to doc: 2000_doc about how to download documents.
For information on how to read the created file, please see : doc: 8110_config_export .

Note

  • The contents set with :doc: 3000_nw are not output.