cancel
Showing results for 
Search instead for 
Did you mean: 

OmniStack issue

 
Highlighted
Occasional Advisor

OmniStack issue

hi 

currently in our premises we have two Omnicube box

box1:  Simplivity CN-3000 0.150.5.179

(OmniStack: 10.150.5.183 )

box2:  Simplivity CN-3000 10.150.5.180

(OmniStack2: 10.150.5.184 )

Recently I noticed that the OmniStack 2 show me in status bar are failty as below

Screen Shot 2019-11-20 at 4.18.29 PM.png

also found that
OmniStack1 183 takeover the storage/Federation IP (10.10.10.5) which is related to the second OmniStack2 184

Screen Shot 2019-11-21 at 11.31.42 AM.png

 

OmniStack 184 without storage/Federation IP (10.10.10.5)

Screen Shot 2019-11-21 at 11.32.01 AM.png

and from OmniStack1: 10.150.5.183 not show me the IP 10.10.10.5 when run the ifconfig 

svtcli@omnicube-ip5-183:$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:56:91:2e:7a  
          inet addr:10.150.5.183  Bcast:10.150.5.255  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:39780994 errors:0 dropped:280 overruns:0 frame:0
          TX packets:22413674 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:53677947553 (53.6 GB)  TX bytes:21929231084 (21.9 GB)

eth1      Link encap:Ethernet  HWaddr 00:50:56:91:68:2a  
          inet addr:10.10.20.1  Bcast:10.10.20.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:35129 errors:0 dropped:9 overruns:0 frame:0
          TX packets:49565 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3236505 (3.2 MB)  TX bytes:3928890 (3.9 MB)

eth2      Link encap:Ethernet  HWaddr 00:50:56:91:0f:35  
          inet addr:10.10.10.3  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:89300704 errors:0 dropped:10 overruns:0 frame:0
          TX packets:72590486 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:407611000150 (407.6 GB)  TX bytes:1016900675265 (1.0 TB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2759898 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2759898 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:791648775 (791.6 MB)  TX bytes:791648775 (791.6 MB)

 

Now Issue if I've login to the(OmniStack: 10.150.5.184 ) CLI .. and when I run most command is not responding and shows me the below errors , without any reason

 

svtcli@omnicube-ip5-184:~$ svt-hardware-show
Error: TSSLSocket: Could not connect to 10.150.5.184:9190 (Connection refused)

 

 

I also notice somthing when I reboot the OmniStack 10.150.5.184 and booting up 

 

Screen Shot 2019-11-19 at 9.51.44 AM.png

 

since the (OmniStack: 10.150.5.183 ) working properly

 I don't how to figure out of this ..  Should be rebuilt OmniStack2 184  again and how?  or I can fix it,

1 REPLY 1
Highlighted
HPE Pro

Re: OmniStack issue

Hi @jmeshal 

Thanks for using the forum, and for the detail.

The node is obviouly in a faulty state. This can have many different causes, most likely an underlying hardware issue. A support engineer would need to connect here and take a closer look.

The forum in this specific scenario would not give us the level of information we would need to troubleshoot this accurately.

If you create a support ticket, I'm sure one of our engineers will be able to assist.

Thanks,

DeclanOR  #I am a HPE Employee

Accept or Kudo



I am an HPE Employee