Wireless Access

Hello,

I need help.

I am planning a network using 7008, 274.
Please look at my picture.

1. In 7008 i create a mesh cluster.

2. Configuration-Access point

I choose a point in the list. Pointing as mesh portal. It is displayed in MashAPs.
I choose another point. Pointing as mesh point. The point disappears. The ping does not go to the registered static address.

In the help section of the Secure Corporate Mesh, I cannot exactly understand the sequence of actions.

Can you write me step by step actions in order to implement the network shown in the picture.

What should I do next. How to find mesh point?

Thank you.

The mesh point needs to build its connection to the controller over the wireless link. It is currently able to communicate with the mesh portal? What antennas are being used with the AP-274s? 

mesh portal - ANTENNA KIT ANT-3X3-5712 point- to-multipoint

mesh point - ANTENNA KIT ANT-2X2-5314 point-to-point

Where I see communication with the mesh portal?

Will it be a notification?

The AP274 will get the same ip address that it had before when it connected to the controller on the wired network.  On the controller, type "show ap database" to see what ip addres the AP-274 had before and try to do a constant ping to it while booting it.  That is the earliest way to see if the mesh point has come up.

At the time of setting the mesh point, I set the static address 192.168.0.24/24.
I carry out a constant ping. There is no point in the wired network.

As I understand it, when I assign a AP as a mesh point, it will only connect via a wireless network and it will have an address of 192.168.0.24/24.
In the wired network, I can’t see the point because the port AP in the mesh cluster is configured as a bridge.

I need to figure out why the mesh portal does not see the mesh point.

Do I understand everything correctly?

Did you configure the mesh profiles before provisioning the mesh point? 

Did you configure a mesh portal?

What ip address did the mesh point have before you set the static ip address?  You should not set a static ip address, because it is error prone, and you have to set other parameters like serverip/masterip to make sure the mesh point registers with the controller.

Yes, I configured everything.

If I use 2x2 antenna but I do not use a terminator, this will work or not.

I think I have a problem with 2x2 antenna and AP 274

Ok,

Please see my pictures.

For the test, I use:
AP 274
ANT-3X3-5712
ANT-2X2-5314
Aruba os 8.3
7008 controller

All settings for the cluster mesh are configured by default.
pic 4, AP wo-33 need to make a mesh point.
pic 14 - when I click apply, the point disappears.

I do not understand where to look.

I configured the WLAN with AP 207, everything works fine.

Mesh cluster does not work. I have deadlines for the project, but I can't configure the mesh cluster.

Is it possible that you connect to me remotely and help me with the configuration? 

Attachment(s)

img.zip   2.01 MB 1 version

Your configuration does not look wrong, but those antennas are very close.  Please put them across the room from each other. 

Did you receive a console cable with th AP-274 (usb cable)?  You would need to download the driver for it and install it on your computer and use putty to connect to the AP-274.  You will then be able to see if there are any console messages coming from the AP-274.

Set points at a distance of 3 meters.

Connect the console mesh point. I understand there is an error, but where?

The console asks for a password, where can I get it?

 What should I do next?

APBoot 1.5.5.7 (build 56398)
Built: 2016-09-08 at 14:04:05

Model: AP-27x
CPU0: P1020E, Version: 1.1, (0x80ec0011)
Core: E500, Version: 5.1, (0x80212051)
Clock:
CPU0: 800 MHz
CPU1: 800 MHz
CCB: 400 MHz
DDR: 333.333 MHz (666.667 MT/s data rate) (Asynchronous)
LBC: 25 MHz
L1: D-cache 32KB enabled
I-cache 32KB enabled
I2C: ready
DRAM: Configuring DDR for 666.667 MT/s data rate
DDR: 512 MB (DDR3, 32-bit, CL=5, ECC off)
POST1: memory passed
Flash: 32 MB
L2: 256 KB enabled
Power: 802.3at POE
PCIe1: RC, link up, x1
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 14e4 4360 00002 03 80000004 00000000 00000000 00000000
PCIe2: RC, link up, x1
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 14e4 4360 00002 03 a0000004 00000000 00000000 00000000
Net: eth0, eth1
Radio: bcm43460#0, bcm43460#1
FIPS: passed

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

Image is signed; verifying checksum... passed
SHA2 Signature available
Signer Cert OK
Policy Cert OK
RSA signature verified using SHA2.
[ 0.000000] Flash variant: default
[ 0.000000]
[ 0.000000] Aruba Networks
[ 0.000000] ArubaOS Version 8.3.0.0 (build 64659 / label #64659)
[ 0.000000] Built by p4build@pr-hpn-build09 on 2018-04-27 at 21:20:01 UTC (gcc version 4.5.1)
[ 0.000000]
[ 0.000000] Memory: 507788k/524288k available (10676k kernel code, 16500k reserved, 652k data, 472k bss, 7092k init)
[ 0.003001] Processor 1 found.
[ 0.113044] Brought up 2 CPUs
[ 0.190241] PCI: Probing PCI hardware
[ 0.233395] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[ 0.296389] pci 0001:02:00.0: PCI bridge to [bus 03-ff]
[ 0.358607] pci 0000:00:00.0: enabling device (0106 -> 0107)
[ 0.425702] pci 0001:02:00.0: enabling device (0106 -> 0107)
[ 5.619420] ee000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank
[ 5.694480] Amd/Fujitsu Extended Query Table at 0x0040
[ 5.756004] number of CFI chips: 1
[ 5.811238] fsl-gianfar ethernet.2: enabled errata workarounds, flags: 0x4
[ 5.894794] /proc/gfar_eth0_stats created
[ 5.945086] fsl-gianfar ethernet.3: enabled errata workarounds, flags: 0x4
[ 6.028641] /proc/gfar_eth1_stats created
[ 6.167235] ad7418 1-0048: cannot read configuration register
[ 6.236387] ad7418 1-0049: cannot read configuration register
[ 6.305801] Enabling watchdog on CPU 0
[ 6.305810] Enabling watchdog on CPU 1
[ 6.395644] Masking ICV Error interrupt
[ 6.447005] ramzswap: num_devices not specified. Using default: 1
[ 6.519958] ramzswap: Creating 1 devices ...
[ 6.821703]
[ 6.821708] Starting Kernel SHA1 KAT ...Starting Kernel HMAC SHA1 FIPS KAT ...Completed Kernel HMAC SHA1 FIPS KAT
[ 6.830614] Starting Kernel HMAC SHA256 FIPS KAT ...Completed Kernel HMAC SHA256 FIPS KAT
[ 6.831350] Starting Kernel HMAC SHA384 FIPS KAT ...Completed Kernel HMAC SHA384 FIPS KAT
[ 6.831870] Starting Kernel HMAC SHA512 FIPS KAT ...Completed Kernel HMAC SHA512 FIPS KAT
[ 6.832435] Starting Kernel AES-CBC FIPS KAT ...Completed Kernel AES-CBC FIPS KAT
[ 6.867606] Starting Kernel AES-CCM FIPS KAT ...Completed Kernel AES-CCM FIPS KAT
[ 6.868062] Starting Kernel 3DES-CBC FIPS KAT ...Completed Kernel 3DES-CBC FIPS KAT
[ 7.534328] Completed Kernel SHA1 KAT
[ 7.579145] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
[ 7.687753] Starting Kernel DES KAT ...Completed Kernel DES KAT
[ 7.759711] Starting Kernel AES KAT ...Completed Kernel AES KAT
[ 7.803509]
Populate AP type info
Domain Name: arubanetworks.com
No panic info available
[ 24.904955] p1020_soc: P1020 Misc Utils Driver version 1
Ethernet port 1 mode: active-standby
[ 40.402796] init_phy: PHY interface is SGMII
[ 40.456920] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 40.532898] ADDRCONF(NETDEV_UP): bond0: link is not ready
[ 40.621512] init_phy: PHY interface is SGMII
[ 40.675613] bonding: bond0: enslaving eth0 as a backup interface with a down link.
[ 40.838326] init_phy: PHY interface is SGMII
[ 40.892590] bonding: bond0: enslaving eth1 as a backup interface with a down link.
[ 41.253992] AP xml model 74, num_radios 2 (jiffies 20423)
[ 41.318630] apType 74 hw_opmode 0
[ 41.358241] radio 0: band 1 ant 1 max_ssid 16
[ 41.410362] radio 1: band 0 ant 1 max_ssid 16
[ 41.462478] init_asap_mod: installation:2
[ 41.510433] ethernet_device_event: dev eth0 is up
[ 41.567636] PHY: eth0 (mdio@ffe24000:00) - Link is Up - 1000/Full
[ 41.642984] ethernet_device_event: dev eth0 is changed, carrier: 1
[ 41.726766] firewall cpu: core-1
[ 41.810014] bonding: bond0: link status definitely up for interface eth0.
[ 41.891319] bonding: bond0: making interface eth0 the new active one.
[ 41.968498] bonding: bond0: first active interface up!
[ 42.030251] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
set device anul0 mtu to 2000
Starting watchdog process...
Aruba watchdog daemon started [2 thread(s)]
LLDP not sent yet, DHCP is waiting
Starting DHCP
net.ipv4.conf.all.arp_notify = 1
net.ipv4.conf.all.arp_notify = 0
net.ipv4.conf.br0.arp_notify = 1
[ 49.935418] wifi0: AP type AP-274, radio 0, max_bssids 16
[ 50.587010] wifi1: AP type AP-274, radio 1, max_bssids 16
Clearing P1020 PCIe Error Status
shutting down watchdog process (nanny will restart it)...

<<<<< Welcome to the Access Point >>>>>

password: [ 57.703709] wl0: set MESH_ID(Bridge1, 7)
[ 59.059266] asap_vap_gone: Got vap gone notification on unknown vap:0:1
[ 60.215535] asap_vap_gone: Got vap gone notification on unknown vap:0:0
[ 61.310306] Got MTU config but no tunnel to AAC yet

[ 110.803574] aruba_enable_usb_block:556 Enabled USB
[ 110.860901] aruba_usb_power_control:1144 Enable USB power control for 224/225
[ 110.946402] ardmore_usb_power_control:1055 enabled the USB interface
[ 111.022488] Enabling eth1 due to power change [power profile 1]
[ 425.568115] wl0: set MESH_ID(RecoverySauy4UJbawglY4vf, 24)

I connect the power point through the PoE port on the controller.
Using 5314 and 5712 antennas, will I give everything correctly or do I need to connect points to the AC power interface or PoE midspan injector 48VDC?

I would like to exclude the option of not properly connecting the power for points with 5314 and 5712 antennas.

changed regulatory domain to chaina.

added value to channel 40 in RF Management

mesh works