Controllerless Networks

Hi, i have severals groups on my Airwave to push configurations to the remote Instant-Clusters around the globe. This was working fine all the time but for some reason i can't select my Instant-Cluster in one of my groups. When i navigate to Groups -> <Group-name> Instant-Config -> VC List the page remains empty, so it seems that I lost my Instant. All other groups are working well and Instant-Clusters are shown. When I log on to the assosiated VC at the remote site it shows that its still connected to Airwave. However, its not visible like descriped above. We use Airwave 8.2.2.1 as VM.

Any idea about what's going on there ? Should we may do a reboot of the Airwave server ?

Hi,

I understand that you are not seeing VC in instant config page, does the VC listed in APs/Devics>List page. If YES, does it showing any configuration error status in devices APs/Devices>monitor page?

 

If there is no error, message, try restart the Airwave services once and check the status.

To restart the service run #rd

Regards,

Pavan

Thanks for reply,

following output occurs in cli:

[root@denesvmaw01 mercury]# rd
failed to kill pid 2143
failed to kill pid 2487
Wed Apr 26 04:24:39 2017: Stopped VisualRF Engine...
[root@denesvmaw01 mercury]#

 

WebGui is't accessable right now :-( Anything else i have to do ?

OK, took some time to come back, but still the same issue. All remaining groups are back to normal.

Are you seeing any configuration error in APs/Devices>montior page of VC in Airwave and also any error in instant main page?

 

Regards,

Pavan

No, there are no configuration errors for the affected AP's. All devices in the mentioned group are up with configuration status "Good". I did a further test by navigating to the the "Basic" page ad  uncheck the Button "Enable Instant GIU Config",did a Save and select it again with urther Save. Didn't help.

You could try restarting only IGC service

 

#psk airwave.igc.jar

 

If that does not resolve the issue, try upgrade the server to latest code 8.2.3.1.

 

Regards,

Pavan

Wait for few minutes for all serivces to comeup and check the status. We could check the services status by running command

#wd

 

We need to see more than 30 services in the list.

 

Regards,

Pavan

Yes, confirmed, seems more than 30 services at all. I can see the Instant devices AP/Devices with configuration status "Good". But the VC is still not shown......strange.

Daemons:
  PID  PPID  PGID %CPU %MEM      RSS      ELAPSED CMD
 1901     1  1901  0.9  9.6  1572072  22-20:21:42 Daemon::AMONAggregator
 1930     1  1930  0.6  8.8  1446108  22-20:21:41 Daemon::APListCacher
 1934     1  1934  0.0  8.8  1430356  22-20:21:41 Daemon::APScanner
 1937     1  1937  1.6  8.9  1454912  22-20:21:40 Daemon::APWatcher
 1941     1  1941  0.0  8.8  1430024  22-20:21:40 Daemon::APWatcherPollNow
 1919     1  1919  0.0  8.8  1433360  22-20:21:41 Daemon::AlertD
21956     1 21956 11.0  9.9  1613852        11:14 Daemon::AsyncLoggerClient
 3061     1  3061  4.7 11.0  1801532     10:06:45 Daemon::AsyncLoggerClient
21992     1 21992  8.2  9.4  1533516        10:59 Daemon::AsyncLoggerClient
 1952     1  1952  0.0  8.8  1429964  22-20:21:40 Daemon::ConfigPusher
 1957     1  1957  0.0  8.8  1430084  22-20:21:39 Daemon::ConfigVerifier
 1965     1  1965  0.0  8.8  1438924  22-20:21:39 Daemon::ConfigWrangler
 2006     1  2006  0.2  8.8  1431180  22-20:21:38 Daemon::DNSFetcher
 1979     1  1979  0.0  8.8  1431596  22-20:21:39 Daemon::DeviceEvent
 1993     1  1993  0.0  8.8  1430408  22-20:21:39 Daemon::DeviceHTTPSHandler
 2345     1  2345  0.1  8.8  1437864  22-20:21:28 Daemon::ExecUIQuery
 2339     1  2339  0.0  8.8  1431136  22-20:21:28 Daemon::ExecUIQuery
 2140     1  2140  0.1  8.9  1446644  22-20:21:34 Daemon::InlineStatsProcessor
 1695     1  1695  0.1  0.2    27832  22-20:22:12 Daemon::LowLevelServiceWatcher
 2029     1  2029  0.6  9.7  1583512  22-20:21:38 Daemon::PEFProcessor
 2143     1  2143  0.0  8.8  1430756  22-20:21:34 Daemon::ParallelActionExecutor
 2013     1  2013  0.0  8.8  1430076  22-20:21:38 Daemon::PartialConfigPusher
 1911     1  1911  0.3 10.3  1687800  22-20:21:41 Daemon::PerfCollector
20939     1 20939  0.8  8.8  1439756        21:14 Daemon::RTLS
21254 21244 21244  0.0  0.2    39636        20:58 Daemon::RestAPIServer
21244     1 21244  0.0  0.3    41968        20:59 Daemon::RestAPIServer
21255 21244 21244  0.0  0.2    39824        20:58 Daemon::RestAPIServer
 2041     1  2041  0.0  8.8  1429752  22-20:21:37 Daemon::SNMPEnabler
 2044     1  2044  0.1  8.8  1430188  22-20:21:37 Daemon::SNMPFetcher
 2049     1  2049  3.7  9.2  1511256  22-20:21:37 Daemon::SNMPV2Fetcher
 2056     1  2056  3.1  8.8  1444956  22-20:21:36 Daemon::SNMPV2Fetcher
21122     1 21122  0.3  9.2  1503024   1-13:23:16 Daemon::Scriptorium
 2024  1711  1711  0.0  8.8  1428816  22-20:21:38 Daemon::ServiceWatcher
 1711     1  1711  0.5  8.8  1438860  22-20:21:45 Daemon::ServiceWatcher
 1905     1  1905  0.0  8.8  1433372  22-20:21:42 Daemon::SwarmHandler
 2060     1  2060  0.3  8.9  1450452  22-20:21:36 Daemon::SyncD
 2081     1  2081  0.0  0.4    59268  22-20:21:36 Daemon::TranslationServer
 1780     1  1780  0.0  8.8  1430068  22-20:21:43 Daemon::TupleScheduler
 1719     1  1719  0.0  8.8  1430056  22-20:21:43 Daemon::TupleSpaces
 2137     1  2137  0.0  8.8  1446044  22-20:21:34 Daemon::UCCProcessor
 2116     1  2116  0.0  8.8  1429752  22-20:21:35 Daemon::WepKeySetter
 2118     1  2117  0.1  2.3   382036  22-20:21:35 IGC
 2031  2030  1711  6.4  9.0  1474376  22-20:21:38 PAPI Message Handler
 1827     1  1826  4.1  0.5    76120  22-20:21:42 RabbitMQ
 2093  2092  2092 113.3 13.9  2274564  22-20:21:35 VisualRF
 1741     1  1741  0.4  0.1    21868  22-20:21:43 airbus
 1509     1  1509  0.0  8.8  1434344  22-20:24:28 httpd_
 1924  1923  1923  0.1  0.1    14728  22-20:21:41 pound
 1923     1  1923  0.0  0.0     1032  22-20:21:41 pound
 1810     1  1810 14.1  0.4    70564  22-20:21:42 redis
 1218     1  1218  0.2  0.1    15276  22-20:25:26 rrdcached
 2487     1  2487  0.0  0.7   117760  22-20:21:20 snmptrapd

You could try disable the Aruba Instant GuI option from Groups>Basic page and re-enable. Before we do this follow below steps

• Make sure the VC is in montior only, we could confim this by running below command

Sample output from my lab, It shows device is in manage mode(zero means manage mode).

[root@Aruba-Airwave mercury]# dbc "select monitor_only from ap where id = 38";
 monitor_only
--------------
            0
(1 row)

• Replace the device number with your VC, you could get the id from APs/Devices>montior page, if it returns '1', we are good to disable the IGC. If it returns '0', first need to place it in monitor mode from CLI and disalbe the instant.

To set the device in montior only mode from CLI

[root@Aruba-Airwave mercury]# dbc "update ap set monitor_only = 1 where id = 38";
UPDATE 1

• Before re-enabling it back, fetch the latest template of VC from Groups>Template page, to make sure we have latest template config, if we enable without fetching the latest template, re-enable the instant will push the old template configuraiton.

Regards,

Pavan

 

Sorry, I'm not so familiar with Aruba Airwave, how could i find the VC iD ?

Click on VC, it will take you to APs/Devices>monitor page, in URL , we can see ID.

https://<ip>/ap_monitoring?id=228

 

Regards

Pavan

I saw that my Template page is missing in the corruptive group, but the VC is in monitor mode, so next i would try to restart the IGC service.

When select "disable" Instant GUI config I have to apply it to the VC, right. O local save isn't enough I guess. Then restarting the IGC service, enable it and apply again, right ?

I now have an configuration error because the config change applied in Basic can't be pushed to the VC since we recocnized our issue.

Is there a possibility to disconnect the whole Instant-Cluster from Airwave and reconnect it again like we did in the past during the initial setup ?

I guess the local VC shouldn't lost its configuration and when reconnect it to Airwave it should sync its current configuration back to Airwave. I only struggeling because I can't find a way to get my Instant-Cluster disconnected from the Airwave server.

Any idea ?

Does VC is showing in instant config now? what error it showing in APs/Device>monitor page?

 

Regards,

Pavan

No config shown, but i see an configuration error right now. I guess this due to the issue that VC can’t become in sync with Airwave. So still the same problem.
Could we may disconnect the IAP cluster from Airwave and reconnect it ?
I guess the VC shouldn’t loose its configuration during this process, but I can’t delete the group since i merged the VC to the group several weeks ago.

No idea how I could get this VC back in sync with Airwave to go ahead with required config changes I need to do. And as long as the VC is connected to Airwave I can’t do
it manually on the Instant-Cluster, so i stuck for the moment.

If you are OK to loss the graph data of VC which is stored in Airwave then we could delete the device from Airwave and re-add. To delete the device from Airwave, first disable instant config from Groups>Basic page and then naviage to VC's AP's/Devices>manage page and click Delete option to remove the device from Airwave.

 

VC will automatically will get detected after few minute in new device page.

 

Note: If you have slave IAPs in the cluster try remove those devices aswell.

 

If you still have issue, give me your contact details I can assist you on call.

 

Regards,

Pavan

It’s working well now.
I disabled instant-config in Basic page and did a “Save and Apply”. After some minutes the config-error was gone. After re-enabling the instant-config the page content comes up again
And I’m now able to go ahead with my outstanding changes to push.
Not sure why it didn’t work yesterday but I guess I did some faults myself.

However, many Thanks for your help.

Best Regards, Holger
​​​​​

Great! finally you are able to make configuraiton changes from Airwave.

 

Regards,

Pavan

If my post addresses your query , accept as solution and  give kudos:)