DX NetOps

Hi all,

I have some issues with my Spectrum.

Two good examples of my problems are the next ones:

1. As you can see in the picture below postfix master process has recovered on the centos-test (1.), but in Navigation panel centos-test is still red (2.), Service Testni postfix is in Initial status (3.), and in the Contents Panel, under Alarm tab, there is no active alarms (4.).

2. In my spectrum model, centos-demo-spectrum, I can see that there is lot of the alarms (1.), but I can't see those alarms or  list of them neither in Navigation panel (2.), nor Alarms, Cleared Alarms History, Events Tab of this model.

Before that I had issues with creating of SLA services, more precisely, I created SLA normally, but I couldn’t see it under Services until I restarted the Spectrum.

Sometimes problems like this are resolved with the restart of the Spectrum and OneClick, but that is not acceptable solution for me.

Am I doing something wrong? Do you have any idea what could be a couse of this behavior?

What version of CA Spectrum is this?

Thanks

Jay

10.0

If nobody else posts with a suggestion/solution I would open a case.

Cheers

Jay

Are SS and OC on different systems?

Yes they are. They are on two VMs (cenos 7), but on the same host.

When no alarms are seen in OneClick, it normally points to one of the two:

1. An Alarm Filter. Check the Alarm Filters to ensure the alarms are not being filtered out

2. No connection to port 14001 from the SS to the OC. On the SS and OC systems, start a bash shell (bash -login) and run "netstat -an | grep 14001". Check for an established connection from the SS to the OC on port 14001.

1. I deleted all alarm filters, but that didn't help.

2.

[root@centos-demo-oneclick ~]# netstat -na | grep 14001

tcp6       0      0 :::14001                :::*                    LISTEN

[root@centos-demo-spectrum ~]# netstat -na | grep 14002

tcp6       0      0 :::14002                :::*                    LISTEN

tcp6       0      0 10.20.1.117:14002       10.20.1.116:59266       ESTABLISHED

So it looks like the root cause is there no established connection on port 14001. So the next step is to find out why.

Is there are firewall rule?

Thanks Joseph!

Firewalld service was running on the one click server and that was the problem.

I will add a rule for the port 14001 into the firewalld configuration on CentOS 7.

Do you maybe know to which zone should I add that rule.

When I start the firewalld by default is active only public zone.

Sorry do not know which zone.