Wireless Access

last person joined: 23 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Aruba 7210 copying flash using SCP

This thread has been viewed 9 times
  • 1.  Aruba 7210 copying flash using SCP

    Posted May 08, 2014 05:03 PM

    Hello,

    I am trying to copy all of my configs from my Aruba devices. To do this I log in and do a "backup flash" then initiate a file transfer using "copy flash". This works perfectly for my mobility switches, but the controllers are disagreeing with the process. The seem to start transferring and then I get the message "error copying file:" which I would expect to say the file it had an error copying, but it's blank.

     

    This is copying to a Ubuntu 12.04 Linux server.  Below is what I type and recieve. Any direction would be appreciated. 

     

    (Aruba7210) #backup flash
    Please wait while we tar relevant files from flash...
    Please wait while we compress the tar file...
    File flashbackup.tar.gz created successfully on flash.
    Please copy it out of the switch and delete it when done.
    
    (Aruba7210) #copy flash: flashbackup.tar.gz scp: 10.10.10.20 network Aruba7210.tar.gz
    Password:************
    
    Secure file copy:................................................................
    Error copying file:
    
    (Aruba7210) #

     

     


    #7210


  • 2.  RE: Aruba 7210 copying flash using SCP

    EMPLOYEE
    Posted May 08, 2014 05:45 PM

    Strange.  That would normally happen if it was unreachable or something.

     

    Try this command, then try again.

     

    delete ssh-host-addr 10.10.10.20

     


    #7210


  • 3.  RE: Aruba 7210 copying flash using SCP
    Best Answer

    Posted May 08, 2014 06:01 PM

    I wish I could give you all the credit. However, deleting the ssh-host did not change anything.

     

    LUCKILY, it for some reason made my brain click and wonder if my Firewall was blocking it. I logged in to my firewall and saw no traffic between the controller and the server. Realized I didn't have a rule to allow traffic on port 22 between them. 

     

    ICMP was allowed, but SSH was not. Which explains why I could ping, but not much else. A quick policy change and I am in business. 

     

     

    So in the long run, thanks for jogging my brain in the right direction!


    #7210