Wireless Access

 View Only
last person joined: 17 hours ago 

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

uncommunicative AP-375 -- how do I figure out if it's dead or alive?

Jump to Best Answer
This thread has been viewed 11 times
  • 1.  uncommunicative AP-375 -- how do I figure out if it's dead or alive?

    Posted Aug 15, 2022 05:15 PM
    We bought an AP-375 from ebay, and the seller advertised it as not knowing whether it was dead or alive and the price was low so we took a chance.

    We have one other AP-375, which is an HP-renew, and it works splendidly, however it doesn't have a working light. Which is not a big deal, as I can look in MobilityMaster and/or Airwave and see what it's doing. I think that the bulb might be broken, or not hooked up.

    When I plug the new 375 into my bench switch, I get lights on the switch port that look like there is an active AP plugged into the port -- the POE light is a nice solid green, and then the link light flashes like there is chatter going between the switch and the AP. There is no sign of life on the AP itself, though, and the MAC address doesn't show up anywhere on my controller.

    But I know from my works-great-except-for-the-light 375 that a working AP shows nothing besides the lights when it's working fine. Basically these two APs LOOK exactly the same when I plug them in.

    I also have an AP135 that got rained on, and when I plug it into my switch the POE light on the switch port comes on but the link light stays dark -- so I know what a dead AP looks like, and this guy doesn't look dead like that one does.

    I next found the console port and reset button, and tried to reset the AP. No sign that anything happened. I want to plug the console port and connect into my computer so that I can watch the console as it boots, but the instructions that came in the 375 box lead to an old dead link and direct you to the new support portal. Last week I was able to guess what looked like the right driver -- CP210x_Universal_Windows_Driver -- which I downloaded and tried to install, but I can't figure out what to do next. Do I run PuTTY and connect to COM1, 2, or 3? (The only other console cable I've used was for the 205H, and the real aruba cable is made of unobtanium, so my husband home-brewed one for me. We used the driver and instructions that came with the USB component that we bought on ebay and I was able to guess my way through it.)

    I don't have a lot of experience with the 3xx level APs, but this behaves kind of like when I had some Instant 205Hs and was trying to boot them as campus APs and I used the console to convert them. Since these are Universal, I would not be surprised if the problem is that they are in some controllerless mode and I'm not familiar enough with this to tell. Not having any lights certainly raises the level of difficulty!

    Anybody have more suggestions as to tricks to figure out if the AP is alive in there? And/or instructions on what to do to my windows computer to get the console to display there?


  • 2.  RE: uncommunicative AP-375 -- how do I figure out if it's dead or alive?
    Best Answer

    EMPLOYEE
    Posted Aug 15, 2022 05:32 PM
    Plug in the console cable, boot the access point.  In the control panel of your computer, see what com port shows up.  Use putty to connect to that com port and see if you can see anything.

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 3.  RE: uncommunicative AP-375 -- how do I figure out if it's dead or alive?

    Posted Aug 15, 2022 06:45 PM
    Brilliant!

    It came up and after awhile it said "i am master now" (this always makes me laugh -- cheeky AP!)

    So it's in Instant mode...

    Now that I have the console connection, is the process to convert to a campus-mode AP the same as what I did to convert my IAP205H's?
    If yes, is the username & password still admin/admin?
    once I get to the MAC-address prompt,

    mac-of-ap# enable
    mac-of-ap# convert-aos-ap CAP ip-of-controller




    APBoot 1.5.7.3 (build 68071)
    Built: 2018-12-04 at 18:34:29

    Model: AP-37x
    DRAM: 491 MB
    SF: Detected MX25U3235F with page size 64 kB, total 4 MB
    Flash: 4 MB
    NAND: 132 MiB
    PCIE0: link up
    PCIE1: link up
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000
    dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
    00 00 168c 0046 00002 00 00000004 00000000 00000000 00000000
    Power: 802.3af POE
    In: serial
    Out: serial
    Err: serial
    Net: eth0
    Radio: qca9990#0, qca9983#1
    Reset: cold
    FIPS: passed

    Hit <Enter> to stop autoboot: 0
    Checking image @ 0x0
    Copying image from 0x44000000

    Image is signed; verifying checksum... passed
    SHA2 Signature available
    Signer Cert OK
    Policy Cert OK
    RSA signature verified using SHA2.
    [ 0.000000]
    [ 0.000000] Aruba Networks
    [ 0.000000] ArubaOS Version 8.6.0.2-8.6.0.2 (build 73853 / label #73853)
    [ 0.000000] Built by p4build@pr-hpn-build09 on 2020-01-09 at 10:20:54 UTC (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) )
    [ 0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5387d
    [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
    [ 0.000000] Machine: IPQ806X wave-2 board
    [ 0.000000] Flash variant: default
    [ 0.000000] msm_reserve_memory: 0x44600000, 0x200000
    [ 0.000000] msm_reserve_memory: 0x44800000, 0x200000
    [ 0.000000] Memory policy: ECC disabled, Data cache writealloc
    [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 122666
    [ 0.075601] CPU1: Booted secondary processor
    [ 0.102374] clk_tbl_nss - loaded
    [ 0.227897] PCI: enabling device 0000:02:00.0 (0140 -> 0143)
    [ 0.228084] PCI: enabling device 0000:00:00.0 (0140 -> 0143)
    [ 0.256451] device tca9539 probe success
    [ 11.949547] [sched_delayed] sched: RT throttling activated
    [ 16.056357] m25p80 spi5.0: found mx25u3235f, expected s25fl512s
    [ 18.398375] Found AT97SC3203 on i2c-gpio0
    [ 18.470821] no pmic restart interrupt specified
    [ 19.110184]
    [ 19.110184] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
    [ 19.200562] Starting Kernel HMAC-SHA1 KAT ...Starting Kernel DES KAT ...Completed Kernel DES KAT
    [ 19.295720] Starting Kernel AES KAT ...Completed Kernel AES KAT
    [ 19.339456]
    [ 19.385254] Completed Kernel HMAC-SHA1 KAT
    [ 19.435238] Starting Kernel AESGCM KAT ...Completed Kernel AESGCM KAT
    Thu Jan 1 00:00:00 PST 1970
    Populate AP type info
    Domain Name: SetMeUp.arubanetworks.com
    Current OEM Name : Aruba Networks
    Disabling ipv6 for devices by default
    AP-type has_ble_support: ONBOARD.
    IPv6 capability is supported for devices
    No panic info available
    Writing /dev/ttyHSL2 into /tmp/ble_port
    Enabling ble_daemon and ble_relay via nanny
    octomore: Start hotplug
    Check backup ENV.
    [ 25.281037] nss_driver - fw of size 393280 bytes copied to load addr: 40000000, nss_id : 0
    [ 25.391221] nss_driver - Turbo Support 1
    [ 25.425741] Supported Frequencies - 110Mhz 550Mhz 733Mhz
    [ 25.504154] nss_driver - fw of size 190016 bytes copied to load addr: 40800000, nss_id : 1
    [ 45.704810] nss_crypto_module_init[273]:module loaded (platform - IPQ806x, build - Jan 9 2020:10:08:29)
    [ 45.908059] nss_crypto_process_event[388]:engine(0) opened successfully
    [ 45.974789] nss_crypto_process_event[388]:engine(1) opened successfully
    [ 46.053920] nss_crypto_process_event[388]:engine(2) opened successfully
    [ 46.133114] nss_crypto_process_event[388]:engine(3) opened successfully
    [ 46.525929] isl28022: Found i2c-gpio0
    Enter non-FIPS mode
    Cfg len is 2919
    factory default SSID detected...
    factory_ssid_present 1
    factory default change detected
    Mesh disabled
    Ethernet port 1 mode: active-standby
    [ 58.631458] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
    [ 58.704436] bonding: MII link monitoring set to 400 ms
    [ 59.174195] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 59.244267] ADDRCONF(NETDEV_UP): bond0: link is not ready
    [ 59.334832] bonding: bond0: enslaving eth0 as a backup interface with a down link.
    Info: use bonding and enslave eth1
    [ 59.450078] ADDRCONF(NETDEV_UP): eth1: link is not ready
    Starting watchdog process...
    Aruba watchdog daemon started [2 thread(s)]
    dual_uplink_default[ 59.579600] bonding: bond0: releasing backup interface eth0
    [ 59.693314] bonding: bond0: Warning: clearing HW address of bond0 while it still has VLANs.
    [ 59.793314] bonding: bond0: When re-adding slaves, make sure the bond's HW address matches its VLANs'.
    [ 59.905248] Kernel watchdog refresh ended on core 1.
    is 1
    [ 59.971665] bonding: bond0: enslaving eth1 as a backup interface with a down link.
    eth1 is enslaved into bond0
    [ 60.072789] bonding: bond0: Setting eth1 as primary slave.
    Preferred uplink is eth1
    [ 60.211527] Kernel watchdog refresh ended on core 0.
    Loading configuration file of length 2919...
    wifi uplink not present...
    extended ssid config detected...
    Terminal access enabled...
    factory default SSID detected...
    No valid ssid was found...
    extended ssid activate due to no valid ssid ...
    touching file /tmp/ip_mode_0
    [ 60.654670] ADDRCONF(NETDEV_UP): eth0: link is not ready
    do ethtool autoneg on for eth0[ 60.716494] eth0: Link down

    eth0 uplink enabled
    [ 63.158450] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 63.214807] eth0: 1000 Mbps Full Duplex
    eth0 uplink active
    init usb modem ...
    USB is not supported on this model
    [ 64.273508] Settng Jumbo MRU 2000
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    Ethernet uplink eth1 not active yet
    [ 95.002311] bonding: bond0: releasing backup interface eth1
    [ 95.070071] bonding: bond0: Warning: clearing HW address of bond0 while it still has VLANs.
    [ 95.170040] bonding: bond0: When re-adding slaves, make sure the bond's HW address matches its VLANs'.
    [ 95.288972] bonding: bond0: enslaving eth0 as a backup interface with a down link.
    Backup uplink eth0 not active yet
    Backup uplink eth0 not active yet
    Backup uplink eth0 not active yet
    [ 99.393502] eth0: 1000 Mbps Full Duplex
    Backup uplink eth0 not active yet
    [ 99.681505] bonding: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex.
    [ 99.774258] bonding: bond0: making interface eth0 the new active one.
    [ 99.852264] bonding: bond0: first active interface up!
    [ 99.912902] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
    set eth0 as select uplink
    Ethernet uplink active. Becoming Mesh Portal
    Mesh is DISABLED on this device.
    extended ssid is activated o[ 101.284379] bonding: bond0: enslaving eth1 as a backup interface with a down link.
    n the platform ...
    copying bootuplog ...
    [ 101.465010] uol: module license 'Proprietary' taints kernel.
    [ 101.548172] Disabling lock debugging due to kernel taint
    [ 101.613277] UOL ctf init done
    [ 101.647141] uol_hw_offload_enable:879 enable=1
    [ 101.700249] uol_set_cfg:810 cfg update: 0x140->0x143
    [ 101.759606] UOL nss init done
    [ 101.795064] init_uol_mod: offload cap: 0x143, mesh mode none, strapless_enabled 0, uplink_vlan 0
    [ 101.974476] AP xml model 109, num_radios 2 (jiffies 50983)
    [ 102.027647] apType 109 hw_opmode 0
    [ 102.068416] radio 0: band 1 ant 0 max_ssid 16
    [ 102.120337] radio 1: band 0 ant 0 max_ssid 16
    [ 102.172696] init_asap_mod: installation:0
    [ 102.220368] election init: rand=12 HZ=500
    [ 102.268384] IAP client match init
    [ 102.307997] ethernet_device_event: dev eth0 is up
    [ 102.364198] ethernet_device_event: dev eth1 is up
    [ 102.908840] anul_radio_bond_sysctl_init
    allow PAPI
    set device anul0 mtu to 2000
    notify asap_mod 3g no present...
    Starting update SBL2 ...
    SBL2 was updated already
    Done.
    apdot1x authentication is not enabled
    Starting DHCP
    Getting an IP address...
    Jan 1 00:01:23 udhcpc[4794]: udhcpc (v0.9.9-pre) started
    Jan 1 00:01:23 udhcpc[4794]: send_discover: pkt num 0, secs 0
    Jan 1 00:01:23 udhcpc[4794]: Sending discover...
    Jan 1 00:01:23 udhcpc[4794]: send_selecting: pkt num 0, secs 0
    Jan 1 00:01:23 udhcpc[4794]: Sending select for 10.10.16.240...
    Jan 1 00:01:23 udhcpc[4794]: Lease of 10.10.16.240 obtained, lease time 259200
    [ 107.271508] ip_time_handler: Got ip and packets on bond0 Started master election 130-0, rand 26
    [ 125.004373] bonding: bond0: releasing backup interface eth1
    [ 125.058794] ethernet_device_event: dev eth1 others: 9
    [ 125.120118] ethernet_device_event: dev eth1 is down
    [ 125.177507] ethernet_device_event: dev eth1 others: 8
    [ 125.243923] ethernet_device_event: dev eth1 others: 13
    [ 125.299562] ADDRCONF(NETDEV_UP): eth1: link is not ready
    [ 125.362792] ethernet_device_event: dev eth1 is up
    10.10.16.240 255.255.0.0 10.10.31.1
    Compressing all files in the /etc/httpd directory...
    Done.
    Starting Webserver
    bind: Transport endpoint is not connected
    bind: Transport endpoint is not connected
    bind: Transport endpoint is not connected
    Put ntpdate to the nannylist.
    [ 133.528053] ath_hal: 0.9.17.1 (AR5416, AR9380, WRITE_EEPROM, 11D)
    [ 133.618119] ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
    [ 133.724117] ath_dfs: Version 2.0.0
    [ 133.724117] Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
    [ 133.881568] ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
    [ 134.016119] ath_pci: (Atheros/multi-bss)
    [ 134.058263] PCI: enabling device 0000:01:00.0 (0140 -> 0142)
    [ 134.120056] ath_pci 0000:01:00.0: ath DEBUG: sc=0xc0f8f400
    [ 135.407341] Startup Mode-0 set
    [ 135.431708] htt_peer_map_timer_init Enter pdev dcad0000 hrtimer dcad29b0
    [ 135.511590]
    [ 135.511590] htt_alloc_peer_map_mem : Alloc Success : host q vaddr dc11a000 paddr 5d61a000
    [ 135.628397]
    [ 135.628428] htt_alloc_peer_map_mem : Flush Interval Configured to 256 pkts
    [ 135.730709] ol_txrx_pdev_attach: 2500 tx desc's allocated ; range starts from d6040000
    [ 135.825117]
    [ 135.825117] SERIAL NUMBER: : wifi1
    [ 135.825117]
    [ 135.901155] wmi_service_ready_event_rx: WMI UNIFIED SERVICE READY event
    [ 136.053920] wmi_ready_event_rx: WMI UNIFIED READY event
    [ 136.106154] target uses HTT version 2.2; host uses 2.2
    [ 136.112621] ol_ath_smart_ant_attach: Firmware doest not support Smart Antenna.
    [ 136.112652] ol_ath_smart_ant_attach: Hardware doest not support Smart Antenna.
    [ 136.213683] aruba_mods_radio_attach: dev:<wifi1> ic:d5f00540 osdev:c0f8f410 phy:2
    [ 136.213714] wifi1: Base BSSID 24:62:ce:d2:4b:c0, 16 available BSSID(s) processor ID: 0
    [ 136.213714] eth0 address=24:62:ce:c5:24:bc
    [ 136.213714] br0 address=24:62:ce:c5:24:bc
    [ 136.213714] wifi1: AP type AP-375, radio 1, max_bssids 16
    [ 136.213714] aruba_mods_radio_attach() INT setting antenna polarization to 1 radio 1
    [ 136.213745] Resetting spectral chainmask to Rx chainmask
    [ 136.319212] Resetting spectral chainmask to Rx chainmask
    [ 136.319493] Init the PCAP for radio1 offload 1.
    [ 136.319775] aruba_mods_radio_attach: radio: 1, init txq work cpu: core-1
    [ 136.319900] PCI: enabling device 0000:03:00.0 (0140 -> 0142)
    [ 136.320181] ath_pci 0000:03:00.0: ath DEBUG: sc=0xd6766800
    [ 142.039956] Startup Mode-0 set
    [ 142.064354] htt_peer_map_timer_init Enter pdev d6030000 hrtimer d60329b0
    [ 142.144204]
    [ 142.144204] htt_alloc_peer_map_mem : Alloc Success : host q vaddr d5dcc000 paddr 572cc000
    [ 142.260887]
    [ 142.260887] htt_alloc_peer_map_mem : Flush Interval Configured to 256 pkts
    [ 142.363542] ol_txrx_pdev_attach: 2500 tx desc's allocated ; range starts from d5de0000
    [ 142.457731]
    [ 142.457763] SERIAL NUMBER: : wifi0
    [ 142.457763]
    [ 142.533770] wmi_service_ready_event_rx: WMI UNIFIED SERVICE READY event
    [ 142.689784] wmi_ready_event_rx: WMI UNIFIED READY event
    [ 142.742018] target uses HTT version 2.2; host uses 2.2
    [ 142.880818] aruba_mods_radio_attach: dev:<wifi0> ic:d5700540 osdev:d6766810 phy:2
    [ 142.958075] wifi0: Base BSSID 24:62:ce:d2:4b:d0, 16 available BSSID(s) processor ID: 0
    [ 143.052827] eth0 address=24:62:ce:c5:24:bc
    [ 143.101874] br0 address=24:62:ce:c5:24:bc
    [ 143.149640] wifi0: AP type AP-375, radio 0, max_bssids 16
    [ 143.214245] aruba_mods_radio_attach() INT setting antenna polarization to 1 radio 0
    [ 143.307029] Resetting spectral chainmask to Rx chainmask
    [ 143.370477] Resetting spectral chainmask to Rx chainmask
    [ 143.434864] Init the PCAP for radio0 offload 1.
    [ 143.488503] aruba_mods_radio_attach: radio: 0, init txq work cpu: core-0
    [ 143.594189] pktlog_init: Initializing Pktlog for AR900B, pktlog_hdr_size = 16
    [ 143.670821] pktlog_init: Initializing Pktlog for AR900B, pktlog_hdr_size = 16
    AP rebooted caused by cold HW reset(power loss)
    shutting down watchdog process (nanny will restart it)...

    <<<<< Welcome to the Access Point >>>>>
    Completed SW FIPS KAT test

    Power supply mode is POE-AT:, USB Modem is not present.
    User: [ 146.681474] Starting Kernel HMAC SHA1 FIPS KAT ...
    [ 146.724586] Completed Kernel HMAC SHA1 FIPS KAT
    [ 147.331490] Kernel watchdog refresh ended on core 1.
    [ 147.335488] Kernel watchdog refresh ended on core 0.
    [ 148.687472] Starting Kernel HMAC SHA256 FIPS KAT ...
    [ 148.833020] Completed Kernel HMAC SHA256 FIPS KAT
    ble_ready NOT present @init ....
    [ 150.695470] Starting Kernel HMAC SHA384 FIPS KAT ...
    [ 150.759481] Completed Kernel HMAC SHA384 FIPS KAT
    [ 152.695470] Starting Kernel HMAC SHA512 FIPS KAT ...
    [ 152.760637] Completed Kernel HMAC SHA512 FIPS KAT
    [ 171.135707] VAP device aruba015 created osifp: (d5a22540) os_if: (d50b0000)
    [ 171.250546] VAP device aruba115 created osifp: (d4300540) os_if: (dd0a8000)
    [ 171.564104] ieee80211_ioctl_dbgreq received fips event 2 d4323f00 length 16
    Firmware AES-CCM Known Answer Test Passed
    [ 172.697438] wlan_mlme_app_ie_delete: appie is NULL. Do nothing.
    [ 173.826710] wlan_mlme_app_ie_delete: appie is NULL. Do nothing.
    [ 181.386098] i am master now
    [ 181.406966] (22:16:35) !!! Init ---> Master
    [ 181.456950] asap_send_elected_master: sent successfully
    [ 183.958356] asap_send_elected_master: sent successfully
    ble_ready is present @203 .... start processing msgs from APB


  • 4.  RE: uncommunicative AP-375 -- how do I figure out if it's dead or alive?

    EMPLOYEE
    Posted Aug 15, 2022 06:49 PM
    That is the correct command, yes.

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------