Rule Description
The rules that appear in the following table apply to Internet Protocol version 4 (IPv4) addresses unless mentioned otherwise.
ID |
Detection |
Rule |
---|---|---|
2001 |
Incorrect configuration |
An IP address must be configured except if the value of the attribute is true (check box selected).For NOC communication modules, IP address A is optional. |
2002 |
Alert |
IP addresses must be associated to a valid logical network except if the value of the attribute is true (check box selected). |
2003 |
Incorrect configuration |
IP addresses must satisfy the following rules to be valid:
|
2004 |
Incorrect configuration (Alert for BMENUA0100 and BMENUA100.2 modules) |
An IP address must be valid for the configured logical network. |
An IP address cannot be equal to the subnet address or broadcast address. |
||
When the NTP service of a module is configured as , the primary and secondary NTP server IP addresses must satisfy the following rules:
NOTE: The rules
do not apply to BMENOC03?1 communication
modules.
NOTE: The value 0.0.0.0 is
accepted.
|
||
The IP address of either SNMP manager is invalid if it ends with the following value regardless of the value of the subnet mask:
|
||
2005 |
Incorrect configuration |
An IP address must be unique in the logical network. |
2006 |
Alert |
The same IP address must not be used in different logical networks of a system project. |
2007 |
Incorrect configuration |
For the following modules, when IPv6 addresses are enabled and/or selected, the IPv6 addresses of the embedded interface and of the primary and secondary NTP servers cannot be null.
|
2008 |
Alert |
An IPv6 address must be unique within the system project. The rule applies to the following modules:
|
2009 |
Incorrect configuration |
The IP address of each CRA adapter module in an M580 PAC must be unique . |