This post is more than 5 years old
1 Rookie
•
41 Posts
0
74551
August 20th, 2014 01:00
Webinterface not working on management well known address
TLDR:
- opening webinterface on group management ip -> does not work / does ping
- opening webinterface on eql management ip -> does work
- opening webinterface on group management ip -> suddenly does work
- why?
Yesterday I've updated SanHQ from 2.2 to 3.0.1 in preparation to running the upgrade path to FW 7.x. As of yesterday I'm getting the following warning:
[ID: 1.6] The group eql-grp01 was added using non-management well known address (MWKA) address. Remove and add the group using the Group management well known address 172.16.0.9.
The group eql-grp01 contains a single EQL (eql01 / 172.16.3.15) and has a dedicated management port. The range is a /16, as such both the group management IP and the EQL management IP are in the same (unrouted) network.
I'm able to reach the eql01 webinterface on 172.16.3.15 without problems for years. Trying to reach the webinterface on 172.16.0.9 has always given problems (timeout, ping does work however) untill I've requested the webinterface on 172.16.3.15, after that I can reach the webinterface w/o problems on 172.16.0.9.
Up untill now I didn't bother to look into it but as I will be addding another member to the group in a couple of weeks and SanHQ is 'nagging' about not using the well known management IP I tought I might give it a try here, perhaps this is known behaviour?
Edit: Adjusted the subject as the non-MWKA does work but the MWKA does (subject sugested otherwise)
0 events found


hkraal
1 Rookie
•
41 Posts
0
August 20th, 2014 08:00
Hi Don,
Thanks for your reply, I'm not sure I'm following you correctly so for certainty as screen shots sometimes can tell more than words:
www.dropbox.com/.../AAD8D_Q69FaaVnyq8STnCk-sa
172.16.0.0/16 is our management network
172.16.16.0/16 is our iSCSI network
Please correct me if I'm wrong;
- Dedicated Mgmt for eql01 is enabled (on eth4)
- The management IP of eql01 is 172.16.3.15
- The group management IP of eql-grp01 is 172.16.0.9 and this IP should be used to maintain the group as well as adding it to SanHQ
Currently the group has been added to SanHQ with 172.16.3.15 (which isn't the group IP but the eql01 IP). I should fix this by removing it from SanHQ and adding it with the Mgmt IP 172.16.0.9.
If I'm correct sofar I re-ask my first question; What could be the reason that the webinterface on the group Mgmt address (http://172.16.0.9) is not working untill I've opened the webinterface on the management IP of the member (http://172.16.3.15) first.
- Henk