Forum Discussion

zchriss's avatar
zchriss
Icon for Altostratus rankAltostratus
May 23, 2019

Big-IQ stats last collection date stuck at unix epoch?

Hi,

 

The set-up is over 3 data centers:

1x Big-IQ in DC1

3x DCD (one in each DC)

6x Big-IP (two in each DC in HA).

 

The Big-IQ and DCDs are in a cluster that reports healthy.

 

I'm having a strange issue where I am not receiving statistics in Big-IQ for two devices (both from the same DC). Looking at Devices > BIG-IP DEVICES in Big-IQ, the 'Stats Last Collection Date' for these two devices is set to the Unix epoch (Jan 01 1970). Collection status is enabled and they are assigned the correct Data Collection Device.

 

This is a bit of a head-scratcher because it has the same configuration as the other two DCs...

 

I can't seem to find any information on this in documentation or online help. Any ideas if anyone has seem something simliar to this before?

 

Cheers,

 

3 Replies

  • Hi zchris,

     

    This sounds like a known issue that is being tracked under ID 716070. I believe it is planned to be fixed in v7 of BIG-IQ though that is always subject to change. The only workaround I am aware of currently is to remove and then rediscover each of the devices that are showing the incorrect date. That said, it may be worth opening a ticket with Support to confirm whether or not that ID is causing your issue.

  • DeeJz's avatar
    DeeJz
    Icon for Nimbostratus rankNimbostratus

    I've had similar issues,

    Couple things to try,

    My first suggestion would be raise memory on DCD to 32 GIG. seems high but seemed to help.

    Make sure AVR is provisioned on big-iq,

    F5 says this is required, but I have had devices work without it, so not sure about this. But might try it.

     

    Also, once you've done that - remove and rediscover the devices.

  • I also have this issue with the following conditions:

    1xBIG-IQ (v7.1.0.3)

    2xDCDs

    1xBIG-IP cluster (15.1.2.1), where one BIG-IP shows correct stats date, but the other stucks at 01.01.1970

    Both BIG-IPs have AVR provisioned.

    Both BIG-IPs can be pinged and telneted (on port 443) from both DCDs

    Running a tcpdump on both DCDs with filter on the failed BIG-IP shows NO packets, where in comparison to the working BIG-IP I see packets initiated from the DCD.

    I've already removed the affected device from BIG-IQ and rediscovered it again, but no success.

     

    Do you have any other idea, what could be the reason/issue here? Or anything else I can try for troubleshooting to further investigate this issue?

    Thank you!

     

    Regards Stefan :)