Not able to access the UI of the site. The grapevine services are running...
I get no response when attempting the first URL and this when access the dev console:
There is 64 Gb or RAM allocated to this server, but only 6 vCPU. The CPU has only peaked at 27% the past week.
log into the console and do a "reset_grapevine".
This should restart all of the services. Given you have not used the controller, you can say "y" to the questions you get asked.
It will also show all of the services starting up (or why they failed).
Port 14141 is no longer used in 1.3 and later and there is just a redirect in place now.
Afterwards, when attempting to access the site, this is what I get:
Capturing the traffic in Wireshark shows the server resetting the connection:
Added one NIC (which we gave the internal address) and the grape-br0 interface has the address 169.254.0.1. Does this interface need a usable IP. Is this what the UI uses.
Check is there any firewall protecting the APIC-EM subnet.
The grape-bro interface is internal to the device. You do not want to reach that externally. it is for E-W message bus communication between the grapevine services.
try the following on the APIC-EM console.
$ curl -k https://localhost
You should see something like this
- <!doctype html>
- <meta http-equiv="content-type" content="text/html; charset=utf-8">
- <meta charset="utf-8" />
- <title>Login - APIC - Enterprise Module</title>
If all the services were up after the "reset_grapevine". you should see a screen like the following.
Can you run
$ dd if=/dev/zero of=/tmp/foo bs=1M count=512 conv=fdatasync
512+0 records in
512+0 records out
536870912 bytes (537 MB) copied, 23.7006 s, 22.7 MB/s
Here is the result..
Disk IO is meant to be 200MB/s.
You can get away with less if you up cpu in a lab.
Once you drop below 30MB/s bad things happen.
if all of the services started.It is likely taking forever to start them up after a reset_grapevine.
Yes, the reset took quite a while. How would I go about increasing the disk IO?
Depends... is the storage local to the server, Is the raid controller working correctly,
Are there other high I/O workloads running on the same server.
It would be interesting to know why the IO is so slow... is it your server or is there a server admin..