Array Setup and Networking
1748256 Members
3881 Online
108760 Solutions
New Discussion юеВ

Re: Nimble Heartbeats dropping

 
SOLVED
Go to solution
xpystchrisx82
New Member

Nimble Heartbeats dropping

We've had our CS260G in play for a number of months now and everything is awesome.  Love the performance, upgrades, pretty much everything has been exactly as we had expected.

We are encountering one issue which has me scratching my head.  Approximately once every week InfoSight sends a "Nimble Storage no longer recieving array heartbeats" in reference to our CS260G.  To date there has never been a single problem, and manually sending array autosupport connections always sends an automated ticket close.  Has anyone else experienced this?  We're scratching our heads.  All of our network gear shows the traffic to the InfoSight IP address (198.54.168.99) as having been allowed.  I've never had an issue downloading Nimble software or getting to InfoSight, Connect, or the Corporate website.

4 REPLIES 4
rugby0134
Esteemed Contributor

Re: Nimble Heartbeats dropping

I've seen this before and it ending being a network cable that was not seated. I would re-seat the cables of the standby controller, or replace them. Then fail-over and repeat.

xpystchrisx82
New Member

Re: Nimble Heartbeats dropping

Any chance we can perform the cable replacement without a fail over?  I have two cables plugged into the management ports of each node. 

rugby0134
Esteemed Contributor
Solution

Re: Nimble Heartbeats dropping

Yes - you can - but if you take too long - it's going to fail-over the ctrl as a network down. The alert should have info on which controller is having the issue. You can just fix the cables on that controller.

xpystchrisx82
New Member

Re: Nimble Heartbeats dropping

I believe we have some network congestion, or one of our security appliances is intermittently blocking the InfoSight IP address.  Yesterday I wasn't able to connect to InfoSight and on-queue I got an email saying that the system heartbeats were dropped.  Digging through our network to try and figure out where the issue actually lies.  I'll post up if/when I figure out the problem.