Cloud Managed Networks

last person joined: yesterday 

Forum to discuss all things related to HPE Aruba Networking Central and UXI Network Management, including deployment of managed networks, configuration, best practices, APIs, Cloud Guest, AIOps, Presence Analytics, and other included Applications
Back to discussions
Expand all | Collapse all

Empty CSV file downloaded from Central

This thread has been viewed 1 times

  • 1.  Empty CSV file downloaded from Central

    Posted Jan 02, 2020 06:54 PM

    Hi, I'm trying to get a CSV file from central regarding a VC's clients. The information is displayed in Central, but when I download that information as a CSV file I get an empty 0 byte .csv file.

     

    I've tried with other screens and I do get data within those other .csv files.

     

    Does anyone have a clue about what might be happening?

     

    Thanks in advance.

     

    Edit: IAP's firmware version is 8.4.0.6_73542 (in compliance with February 7th certificate's issue).



  • 2.  RE: Empty CSV file downloaded from Central
    Best Answer

    EMPLOYEE
    Posted Jan 15, 2020 05:40 PM

    i have tried it and get the correct CSV file.

    my IAP version is 8.5.0.3



  • 3.  RE: Empty CSV file downloaded from Central

    Posted Jan 15, 2020 05:45 PM

    Thank you for your reply.

     

    Are you aware that 8.5.0.3 needs to be updated to 8.5.0.5 if you use Central, Activate or Airwave for IAP?

     

    The certificate expiry error bug is fixed in following software patches of all the supported release versions:

    Instant Patch

    Release Date

    6.4.4.8-4.2.4.16

    19-Dec-2019 (Posted)

    6.5.4.15

    20-Dec-2019 (Posted)

    8.3.0.11

    21-Dec-2019 (Posted)

    8.4.0.6

    17-Dec-2019 (Posted)

    8.5.0.5

    09-Dec-2019 (Posted)

    8.6.0.2

    07-Jan-2020

    I will see if I can upgrade to 8.5 or 8.6 to see if the issue is fixed.



  • 4.  RE: Empty CSV file downloaded from Central
    Best Answer

    Posted Jan 18, 2020 05:03 PM
    I upgraded to 8.6.0.2 and the issue was fixed, thank you for your sugestion.