Skip to main content

SP-REG-M Alarm Troubleshooting

Jeremy Boilard

Problem Statement

The SP-REG-M alarm indicates a Survivable Processor registration or keep-alive issue between the main server and a survivable processor, such as a Survivable Remote Server or Survivable Core Server.

Impact

If the server does not receive the expected keep-alive messages from a survivable processor, both the server and survivable processor can alarm. Affected survivable processor clusters may be unregistered. If an LSP does not register with an ESS, it may register with the main server or another ESS, and alarms may not be raised.

Alarm

SP-REG-M

Troubleshooting Steps

  1. Identify the SP-REG-M error type and review any Aux Data associated with the alarm.
  2. For error type 1, interpret the condition as no keep-alive signal from a Survivable Core Server. The Aux Data value indicates the number of unregistered and alarmed Survivable Core Server clusters, from 0 to 63.
  3. Run the command `status ess-cluster` to determine which survivable processor or ESS cluster is not registered.
  4. Verify whether the main server is reachable and operational.
  5. Check for network connectivity issues between the main server and the affected survivable processor.
  6. Review survivable processor and server administration for incorrect or inconsistent configuration.
  7. For error type 769, interpret the condition as an invalid or incorrect NIC address, where the system is unable to access the IP address of the native NIC.
  8. For error type 769, use the Maintenance Web Page to verify or configure the NIC address under `Server Configuration > Configure Server > Configure Individual Services > Configure Interfaces`.
  9. After correcting any network, server availability, NIC, or administration issue, verify that the survivable processor registers successfully and that the SP-REG-M alarm clears.

Resolution

Resolve the underlying registration failure by correcting network outages, main server availability issues, survivable processor or server administration errors, or an invalid native NIC address. Use `status ess-cluster` to identify unregistered survivable processors and use the Maintenance Web Page interface configuration path to correct NIC address issues when error type 769 is present.