Hello,

What happens if you just try connecting to https://myhostname.local/ ? There is a known issue loading this onto CentOS/RedHat that the webadmin sub-directory doesn't work to access it. It has been fixed in code, but not in the 3.0 installer file.

from netsus.

I agree the webadmin interface does not really work. I currently installed it (v3.0.1) on centos server and it did not work. I got the OVA which is ubuntu and it does not work. All you have to do is go to the IP/webadmin as stated on their entry page (on the OVA ) and it does not work

from netsus.

Are you getting an error? How are you determining the IP address? If you cannot even get to the login page using the OVA, I suspect that there is a network problem.

What is the reported IP address?

from netsus.

this is the error I get

Not Found

The requested URL /webadmin was not found on this server.
Apache/2.2.15 (CentOS) Server at 172.20.9.232 Port 80

The URL I got from the OVA is http://172.20.9.232/webadmin

Apache/httpd works fine just by doing http://172.20.9.232/ and also if I did http://172.20.9.232/content I could see a folder named catalogs so basically the webadmin is not working. I do not see any where in the conf files where it is specifying webadmin.

from netsus.

@henrycoule
Make sure you are typing https://172.20.9.232/webadmin
The s on https is important.

from netsus.

Like magic! this works for my own installation but never for the OVA. I don't care about the OVA anymore as long as this works. but where on the file system do I place my .nbi files ?

from netsus.

I figured that out but strangely when I click on Enable NetBoot button, the page reloads and thats it. it never gets enabled

from netsus.

Are you running version 3? Try version 3.01. This is a bug that, I believe, was fixed in this version.

from netsus.

Yes I am running version 3.0.1 and it doesn't work

from netsus.

Hmm.. this is strange, you cannot have more than two subnets defined in there, when you do it will not start. If this is the case then why not the form ensures you do not add more than one subnet mask?

from netsus.

I'm going to try to replicate your issues so that I can fix them. Please let me know what setup you're using. I believe CentOS. Version? What configuration did you choose when you installed? Minimal? Basic server?

If you're able to say: what networks, with netmask, are you trying to enable?

from netsus.

System: CentOS release 6.5 (Final)
This is the base installation.

Is this a standalone installation?
Answer yes unless you are creating an image of the appliance to deploy in multiple locations

Standalone? (y/n): y

The following will be installed

• Appliance Web Interface
• NetBoot Server
• Software Updates Server

Proceed? (y/n): y

The NetSUS has been installed.
If you are upgrading NetSUS, you can simply start using it.
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
Shutting down SMB services: [ OK ]
Starting SMB services: [ OK ]
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
Shutting down Netatalk services:
Stopping afpd: [ OK ]
Stopping cnid_metad: [ OK ]

Starting Netatalk services:
Starting cnid_metad: [ OK ]
Starting afpd: [ OK ]

I was enabling network for 172.16.0.0/12

from netsus.

Additionally, when I get it to work, it will not boot up my image. I tested my procedure by using bsdpy server on a different server using the same image source and it works fine. I realized the NetSUS tries to use its own DHCP which doesn't give out any leases.

Jun 17 11:32:20 localhost dhcpd: DHCPDISCOVER from 00:0c:29:60:96:fc via eth1: network 192.168.3.0/24: no free leases
Jun 17 11:32:23 localhost dhcpd: DHCPDISCOVER from 00:0c:29:60:96:fc via eth1: network 192.168.3.0/24: no free leases

Jun 17 11:32:31 localhost dhcpd: DHCPDISCOVER from 00:0c:29:60:96:fc via eth1: network 192.168.3.0/24: no free leases

We have a DHCP server which forwards boot requests to the NetSUS server and it does not honour the request. I see the packets it gets there but nothing happens and booting fails. This same procedure works fine with bsdpy server.

from netsus.

The server is on the 172.16.0.0/12 network and you have enabled that subnet (subnet: 172.16.0.0, netmask: 255.240.0.0), in addition to the subnet you're attempting to boot a client machine on, enabled in the NetSUS?

from netsus.

I figured if the subnet is wrong, it will add it but netboot cannot be enabled. As long as you have in there a good subnet you can add as many as you want and it will be up. so 192.168.3.0/24 (192.168.3.0 & 255.255.255.0 ...... 192.168.2.0 & 255.255.255.0 can be added and it will work. The DHCP part is what i do not understand now. I have DHCP setup somewhere else which forwards to NetSUS. Now, if NetSUS is on a network with a production DHCP server, is NetSUS also going to be issuing DHCP requests or it will only do so for clients which queries it for netboot?

from netsus.

It will only do it for Mac OS clients that issue NetBoot requests. DHCP services will be unaffected. NetBoot request packets are actually specially formed DHCP requests.

It does not play well with other NetBoot servers, however. If you have the NetSUS handling NetBoot requests on a subnet, no other NetBoot servers can be handling requests in that same subnet.

from netsus.

I am unable to login to the webadmin of the netsus/netboot server. it is no longer accepting the default credentials. Nothing has changed.

https://IP_OF_NETSUS/webadmin/index.php

from netsus.

Solved! The NetSUS update filled up the disk space which was the issue.

from netsus.