topic Re: DCNM 11.0 Installation - no webserver in Network Management

DCNM 11.0 Installation - no webserver

Danny Sandner — Mon, 05 Nov 2018 10:18:17 GMT

Hi Folks,

I've installed DCNM 11 via ISO on a bare metal server (Fujitsu), viewed by KVM console. Installation and automatic reboot was done. Normally there shall be an information screen like "open 'http://ipaddress:port' and continue installation". But I get a localhost login prompt, no information about the webgui.

I'll tried to find out the port of the webserver, but I didn't find anything about a webserver in the linux.

Does someone had such problems and solved it?

regards

/Hugo

Re: DCNM 11.0 Installation - no webserver

marce1000 — Mon, 05 Nov 2018 10:26:42 GMT

- Ref the below info's ; I don't think it supports linux KVM as a hypervisor solution :

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/11_0_1/release_notes/b_dcnm_release_notes_11_0_1/system_requirements.html

Cisco DCNM Release 11.0(1) supports the running of the Cisco DCNM Server on the following hypervisors:

VMware ESXi 5.5
VMware ESXi 6.0
VMware ESXi 6.5
VMware vCenter 6.0
VMware vCenter 6.5
M.

Re: DCNM 11.0 Installation - no webserver

Danny Sandner — Mon, 05 Nov 2018 10:31:19 GMT

Hi,

thanks a lot for the quick response. I don't want to use a hypervisor (ESX). I want to install "ISO Virtual Appliance (ISO) with integrated Operating System" on a bare metal server, no virtual server.

In the document, DCNM 11 is supported on Cisco C-series servers, but I think it shall work with other manufactures, too.

Otherwise the "ISO Virtual Appliance (ISO) with integrated Operating System" file is useless in my opinion :)

/Hugo

Re: DCNM 11.0 Installation - no webserver

marce1000 — Mon, 05 Nov 2018 10:42:20 GMT

- Did you try port 8080 ?

Re: DCNM 11.0 Installation - no webserver

Danny Sandner — Mon, 05 Nov 2018 11:21:07 GMT

Yes, I tried port 80,8080,443, 2080 (I saw this port in the demo video).

No success.

Re: DCNM 11.0 Installation - no webserver

Danny Sandner — Thu, 31 Jan 2019 10:16:02 GMT

I solved this problem by using a bigger hardware. Problem was, that the server just had 4 cores. Now I have one with 12 cores and the installation setup finish with the expected word (connect to http....).