21 Systems Infrastructure Switch Compliance Standards
Orachk Systems Infrastructure Switch Best Practices For Oracle Exadata Database Machine
The compliance rules for the Orachk Systems Infrastructure Switch Best Practices For Oracle Exadata Database Machine standard follow.
Exadata Critical Issue Ib1-Ib3
Description: Exadata Critical Issue IB1-IB3
Severity: Critical
Rationale:
Exadata Software Version Compatibility With Infiniband Software Version
Description: Exadata software version compatibility with infiniband software version
Severity: Critical
Rationale:
Exadata Software Version Compatibility With Infiniband Software Version
Description: Exadata software version compatibility with infiniband software version
Severity: Critical
Rationale:
Hostname In /Etc/Hosts
Description: The Impact of verifying that the InfiniBand switch name is properly configured in the /etc/host file is minimal. To correct a mis-configuration requires editing the /etc/hosts file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If the InfiniBand Switch name is not properly configured in the /etc/hosts file, certain switch connection methods may fail.
Infiniband Switch Ntp Configuration
Description: Synchronized timestamps are important to switch operation and message logging, both within an InfiniBand switch between the InfiniBand switches. There is little impact to correctly configure the switches.
Severity: Warning
Rationale: If the InfiniBand switches are not correctly configured, there is a risk of improper operation and disjoint message timestamping.
Infiniband Subnet Manager Status
Description: Enable SM on a limited number of switches as follows:-1 rack to 4 racks - SM enabled on all (service opensmd status should show it as running)4 racks and above - SM enabled only on the spine switches (On other switches,run disablesm to disable the SM and service opensmd status should show it is not running)
Severity: Warning
Rationale:
Infiniband Subnet Manager Status For Spine
Description: Enable SM on a limited number of switches as follows:-1 rack to 4 racks - SM enabled on all (service opensmd status should show it as running)4 racks and above - SM enabled only on the spine switches (On other switches,run disablesm to disable the SM and service opensmd status should show it is not running)
Severity: Warning
Rationale:
Infiniband Subnet Manager Status On Leaf
Description: Enable SM on a limited number of switches as follows:-1 rack to 4 racks - SM enabled on all (service opensmd status should show it as running)4 racks and above - SM enabled only on the spine switches (On other switches,run disablesm to disable the SM and service opensmd status should show it is not running)
Severity: Warning
Rationale:
Infiniband Switch Hostname Configuration
Description: Infiniband switch HOSTNAME configuration
Severity: Warning
Rationale:
Infiniband Switch Controlled_Handover Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Log_Flags Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Polling_Retry_Number Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Polling_Retry_Number Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Routing_Engine Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Sminfo_Polling_Timeout Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Sminfo_Polling_Timeout Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Is Orachk Configured
Description: Verify whether ORAchk is configured for this target.
Severity: Warning
Rationale: ORAchk must be configured before associating compliance content. Else, ORAchk results will not be available for compliance evaluation.
Switch Firmware Version
Description: The Impact of verifying that the InfiniBand switch software is at version 1.3.3-2 or higher is minimal. The impact of upgrading the InfiniBand switch(s) to 1.3.3-2 varies depending upon the upgrade method chosen and your current InfiniBand switch software level.
Severity: Critical
Rationale: InfiniBand switch software version 1.3.3-2 fixes several potential InfiniBand fabric stability issues. Remaining on an InfiniBand switch software version below 1.3.3-2 raises the risk of experiencing a potential outage.
Verify Average Ping Times To Dns Nameserver [Ib Switch]
Description: Secure Shell (SSH) remote login procedures require communication between the remote target device and the DNS nameserver. Minimal average ping times to the DNS nameserver improve SSH login times and help to avoid problems such as timeouts or failed connection attempts.The impact of verifying average ping times to the DNS nameserver is minimal. The impact required to minimize average ping times to the DNS nameserver varies by configuration and cannot be estimated here.
Severity: Warning
Rationale: Long ping times between remote SSH targets and the active DNS server may cause remote login failures, performance issues, or dropped application connections.
Verify No Ib Switch Ports Disabled Due To Excessive Symbol Errors
Description: Notification of a disabled port enables quick repair and redundancy restoration.
Severity: Critical
Rationale: Quick repair from a disabled port ensures the node will not be inaccessible if a secondary IB failure occurs (ie remaining ports fails or down due to switch reboot).
Verify Switch Localtime Configuration Across Switches
Description: Verify switch localtime configuration across switches
Severity: Critical
Rationale:
Verify Switch Version Consistency Across Switches
Description: Verify switch version consistency across switches
Severity: Critical
Rationale:
Sm_Priority Configuration On Infiniband Switch
Description: Configure SM failover timeout at 5 seconds, controlled_handover to TRUE, sm_priority to 5(8 for spine switch) and log_max_size to 8 which is the correct opensm configuration for the Infiniband Switch
Severity: Warning
Rationale: These are recommended values for the Infiniband Switch for best practices for sm_priority
Orachk Systems Infrastructure Switch Best Practices For Recovery Appliance
The compliance rules for the Orachk Systems Infrastructure Switch Best Practices For Recovery Appliance standard follow.
Exadata Software Version Compatibility With Infiniband Software Version
Description: Exadata software version compatibility with infiniband software version
Severity: Critical
Rationale:
Exadata Software Version Compatibility With Infiniband Software Version
Description: Exadata software version compatibility with infiniband software version
Severity: Critical
Rationale:
Infiniband Switch Ntp Configuration
Description: Synchronized timestamps are important to switch operation and message logging, both within an InfiniBand switch between the InfiniBand switches. There is little impact to correctly configure the switches.
Severity: Warning
Rationale: If the InfiniBand switches are not correctly configured, there is a risk of improper operation and disjoint message timestamping.
Infiniband Subnet Manager Status
Description: Enable SM on a limited number of switches as follows:-1 rack to 4 racks - SM enabled on all (service opensmd status should show it as running)4 racks and above - SM enabled only on the spine switches (On other switches,run disablesm to disable the SM and service opensmd status should show it is not running)
Severity: Warning
Rationale:
Infiniband Subnet Manager Status For Spine
Description: Enable SM on a limited number of switches as follows:-1 rack to 4 racks - SM enabled on all (service opensmd status should show it as running)4 racks and above - SM enabled only on the spine switches (On other switches,run disablesm to disable the SM and service opensmd status should show it is not running)
Severity: Warning
Rationale:
Infiniband Subnet Manager Status On Leaf
Description: Enable SM on a limited number of switches as follows:-1 rack to 4 racks - SM enabled on all (service opensmd status should show it as running)4 racks and above - SM enabled only on the spine switches (On other switches,run disablesm to disable the SM and service opensmd status should show it is not running)
Severity: Warning
Rationale:
Infiniband Switch Hostname Configuration
Description: Infiniband switch HOSTNAME configuration
Severity: Warning
Rationale:
Infiniband Switch Controlled_Handover Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Log_Flags Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Polling_Retry_Number Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Polling_Retry_Number Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Routing_Engine Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Sminfo_Polling_Timeout Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Infiniband Switch Sminfo_Polling_Timeout Configuration
Description: The Impact of verifying key parameters in the InfiniBand switch /etc/opensm/opensm.conf file is minimal. To correct a mis-configuration requires editing the /etc/opensm/opensm.conf file and rebooting the InfiniBand switch.
Severity: Warning
Rationale: If key parameters in the InfiniBand switch /etc/opensm/opensm.conf file are not correct, the InfiniBand switch may be unstable or performance may be sub-optimal.
Is Orachk Configured
Description: Verify whether ORAchk is configured for this target.
Severity: Warning
Rationale: ORAchk must be configured before associating compliance content. Else, ORAchk results will not be available for compliance evaluation.
Switch Firmware Version
Description: The Impact of verifying that the InfiniBand switch software is at version 1.3.3-2 or higher is minimal. The impact of upgrading the InfiniBand switch(s) to 1.3.3-2 varies depending upon the upgrade method chosen and your current InfiniBand switch software level.
Severity: Critical
Rationale: InfiniBand switch software version 1.3.3-2 fixes several potential InfiniBand fabric stability issues. Remaining on an InfiniBand switch software version below 1.3.3-2 raises the risk of experiencing a potential outage.
Verify Average Ping Times To Dns Nameserver [Ib Switch]
Description: Secure Shell (SSH) remote login procedures require communication between the remote target device and the DNS nameserver. Minimal average ping times to the DNS nameserver improve SSH login times and help to avoid problems such as timeouts or failed connection attempts.The impact of verifying average ping times to the DNS nameserver is minimal. The impact required to minimize average ping times to the DNS nameserver varies by configuration and cannot be estimated here.
Severity: Warning
Rationale: Long ping times between remote SSH targets and the active DNS server may cause remote login failures, performance issues, or dropped application connections.
Verify No Ib Switch Ports Disabled Due To Excessive Symbol Errors
Description: Notification of a disabled port enables quick repair and redundancy restoration.
Severity: Critical
Rationale: Quick repair from a disabled port ensures the node will not be inaccessible if a secondary IB failure occurs (ie remaining ports fails or down due to switch reboot).
Verify Switch Localtime Configuration Across Switches
Description: Verify switch localtime configuration across switches
Severity: Critical
Rationale:
Verify Switch Version Consistency Across Switches
Description: Verify switch version consistency across switches
Severity: Critical
Rationale:
Sm_Priority Configuration On Infiniband Switch
Description: Configure SM failover timeout at 5 seconds, controlled_handover to TRUE, sm_priority to 5(8 for spine switch) and log_max_size to 8 which is the correct opensm configuration for the Infiniband Switch
Severity: Warning
Rationale: These are recommended values for the Infiniband Switch for best practices for sm_priority