Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Alarm - SP-REG-S

Status
Not open for further replies.
Nov 22, 2013
600
US
Hello all.

I have 2 new g430's both with a s8300d.

They are both running CM 6.3 SP11 Survivable Remote Embedded, with all the latest patches as of jun 8th 2015.

Neither server is plugged into the core yet or has ever been plugged into anything other than my laptop. The only thing I have done so far for configuration is configure the server role information to point to the core IP of the main CM (which it is not plugged into the network yet).

The weird thing is, one s8300 is giving the SP-REG-S alarm, and the other is not giving any alarms at all.

This makes me wonder what one is not working correctly, or if I misconfigured something.

The alarm states The Survivable Processor object monitors keep-alive message between the main server and
the survivable processor, which can be either:
● Local Survivable Processor (LSP)
● Enterprise Survivable Server (ESS)
The server exchanges keep-alive messages with each of the survivable processors. If the
server does not receive a predetermined number of those messages, both the server and the
survivable processor alarm.
Possible causes for SP-REG-S alarms include:
● The network is down.
● The server or survivable processor administration is incorrect


So from what I gather, if I plug this into the network and it sees the core and registeres, this alarm will go away. But why is my other s8300 not giving this alarm? they are both almost identical except for some different IP addresses. Is there a way to clear this alarm manually, or change the pre defined keel-alive?



 
I've had the same thing happen when building these off the network. They went away once it saw a network.
 
So think about it logically , the lsp is warning you it cant see the core , you really don't want to supress that in any way , the reason for your second not alarming is most probably a config issue , but as both servers currently don't have any translations , get them synced to core and then start worrying about alarms.


APSS (SME)
ACSS (SME)
ACIS (UC)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top