SmartConsole showing incorrect "recommended jumbo" for one device

[D_TK]

Happy Monday everyone.

I have a bunch of R82 devices (physical gateways, VM log, VM log and smartevent, management), and all are running the latest take 44.  And as you can see, for all the R82 devices except one, it shows them as "up to date".    The device highlighted below is the management vm - any idea why it's showing an older take as recommended?

thanks.

[the_rock]

I always fix things like that either by cprestart on mgmt or simply rebooting. Never failed me. Mind you, as a quick try, you can install database and wait few mins, that also may do the trick.

[D_TK]

Management was just rebooted a few days ago when it applied hf 44.  All of the folks running the latest version of sc see the same, and i just did a install database on it...issue remains.  i guess i'll open a tac for it

[the_rock]

Does it happen to anyone, regardless who logs in?

[D_TK]

yeah, i have 3 admins (including me).  We all have our own logins, and are all running the latest build of r82 SC.  We all see the same incorrect "recommended jumbo" for the management vm when we all log on.

[the_rock · Accepted solution]

Just checked my lab, looks good. Btw, I thought web smart console would show the same, but does not. If server was rebooted and no luck, I know it may sound silly, but I would definitely still try cprestart. If no luck, yes, definitely open TAC case.

I found these steps online, though never tried them myself:

• Connect to the Management Server via SSH.

• Navigate to the directory $FWDIR/log/amonStatusFiles/.

• Delete the files in this directory (e.g., rm *).

• Restart the FWM daemon using the command fw stop ; fw start (or a full cpstop ; cpstart if needed).

 

[D_TK · Accepted solution]

So...i found sk168572 which was more or less on point.  It mentioned to check CPUSE as a comparison to what SC is showing, and sure enough, CPUSE said that take 19 was pending because at one point i downloaded it but never installed it.  deleted that install package and now SC and CPUSE show the correct information...

[the_rock]

Great! More less same commands I sent?

[the_rock]

@D_TK 

Ironically enough, had client emailed me anout 15 mins ago showing me that exact same issue and I told them about below commands I posted and they said that fixed it, Slightly different than the sk, but since its an official CP sk, I also sent them that as well.

• Navigate to the directory $FWDIR/log/amonStatusFiles/.

• Delete the files in this directory (e.g., rm *).

• Restart the FWM daemon using the command fw stop ; fw start (or a full cpstop ; cpstart if needed).

[the_rock]

Though, I recall once customer told me they fixed problem like this by reinstalling smart console. Not the most common way I would say, but it did work. Personally though, I would try things I mentioned in my first reply.

Hope that helps.