11.1.4. Firewall Instance Status Description¶
11.1.4.1. Status check¶
The method for checking the status of a created Firewall instance is described in this section.
The status of each instance can be checked with customer portal, as shown below.
Operation status
Status
11.1.4.2. Status description¶
The status of a Firewall instance is described in this section. The following two kinds of status are present:
Operation status: Shows the status of operations which are performed for a Firewall instance.
Status: Shows the latest monitoring result from a specific meter, as status. For the outline of the monitoring services, refer to Service Description (Monitoring) .
Operation status¶
The operation status is described below: Operation status is composed of the following request type and status:
Request type
Request type |
Description |
| Create | Creating Firewall |
| Update | Editing Firewall |
| Action | Performing start, stop, restart and password reset of Firewall |
| Delete | Deleting Firewall |
Status
Status |
Description |
Measure to be taken |
Completed |
Request processing for Firewall is completed. |
|
Processing in progress |
Request processing for Firewall is in progress. |
|
Processing halt |
Request processing for Firewall has been halted on the way. |
Make an inquiry with the ticket. |
ERROR |
Request processing for Firewall is not yet completed. |
Wait for a while, and make a request again. |
Note
When status is “processing in progress” or “processing halt”, a new request cannot be made for the Firewall.
Status¶
Each status is described below: Status shows monitoring results from the following three types of meter:
Monitoring status (OS Monitoring Status)
Login status (OS Login Status)
Virtual server status (VM Status)
Monitoring status (OS Monitoring Status)¶
Regarding Firewall (vSRX) OS, monitoring with SNMP is performed by the controller of NTT Communications, via a network for management communications. Transition to the status below occurs depending on responses from Firewall (vSRX) OS.
Status |
Description |
Measure to be taken |
| ACTIVE | A normal SNMP response is returned. |
|
| MONITORING_UNAVAILABLE | A normal SNMP response is not returned. Or, time-out occurred. |
The platform provided by NTT Communications may have failure. Or, the service provider’s settings needed for monitoring may have been deleted or altered by the customer. Check with maintenance and failure information on services of NTT Communications and ‘Descriptions about configurations set by the service provider <https://ecl.ntt.com/en/documents/tutorials/rsts/vSRX/providerconfiguration/providerconfiguration.html>’_ to see if inappropriate operations have been performed for the service provider’s configuration settings whose deletion has been inhibited. |
Login status (OS Login Status)¶
Regarding Firewall (vSRX) OS, monitoring with REST API is performed in terms of login allowance/no-allowance, by the controller of NTT Communications, via a network for management communications. Transition to the status below occurs depending on responses from Firewall (vSRX) OS.
Status |
Description |
Measure to be taken |
| ACTIVE | Login can be normally performed with REST API. |
|
| PROVIDER_LOGIN_UNAVAILABLE | Login cannot be performed with the service provider’s account which is used for login processing. |
The service provider’s settings needed for monitoring may have been deleted or altered by the customer. Check with maintenance and failure information on services of NTT Communications and ‘Descriptions about configurations set by the service provider <https://ecl.ntt.com/en/documents/tutorials/rsts/vSRX/providerconfiguration/providerconfiguration.html>’_ to see if inappropriate operations have been performed for the service provider’s configuration settings whose deletion has been inhibited. |
| MONITORING_UNAVAILABLE | A normal response is not returned. Or, time-out occurred. |
The platform provided by NTT Communications may have failure. Or, the service provider’s settings needed for monitoring may have been deleted or altered by the customer. Check with maintenance and failure information on services of NTT Communications and ‘Descriptions about configurations set by the service provider <https://ecl.ntt.com/en/documents/tutorials/rsts/vSRX/providerconfiguration/providerconfiguration.html>’_ to see if inappropriate operations have been performed for the service provider’s configuration settings whose deletion has been inhibited. |
Virtual server status (VM Status)¶
Status monitoring is performed by the controller of NTT Communications, in terms of a virtual server on which the Firewall (vSRX) OS has been installed. Transition to the status below occurs depending on responses from a virtual server. The status does not indicate that the Firewall (vSRX) OS is running. For operation status on the Firewall (vSRX) OS layer, check with the monitoring status and login status.
Status |
Description |
Measure to be taken |
| ACTIVE | The virtual server is in operation. |
|
| SHUTOFF | The virtual server has been halted. |
|
| ERROR | The virtual server is not in normal status. |
The platform provided by NTT Communications may have failure, temporarily causing malfunction on the virtual server. Stop and start the Firewall (vSRX) and check if the status of the virtual server recovers from ERROR. |
| MONITORING_UNAVAILABLE | A normal response is not returned. Or, time-out occurred. |
The platform provided by NTT Communications may have failure, temporarily causing malfunction on the virtual server. Wait for a while and then check if status recovery occurs. |
Note
The initial value of each status is “initial”. When status is “initial”, the service is not charged.