Forum Discussion
R-Series Appliance No GUI ( host system gui ) after 1.7.0 upgrade
After running the 1.7.0 upgrade for the r-series 5000 appliance - the login screen does not display in a browsers.
Admin and Root passwords are as they were before upgrade.
mgmt-ip settings are the same.
Device can ping it's upstream router in the mgmt-ip network.
the device mgmt-ip address does not reply to ping ( or any request [ ssh, http...])
from the console I can see the whole running config - it is the same as before the upgrade
Any help is appreciated,
Dave Mehlberg
Update to problem. The GUI is accessible if your device is on the mgmt network. The traffic from any other network is ignored ( watching TCPDUMP proves this... ). This is exactly the same for SSH access and ICMP packets.
To refresh: Appliance was running 1.5.1 and was upgraded to 1.7.0 ( never will I ever again load a .0 ).
- a show running-config displays the full correct config
- Admin and Root passwords same as before upgrade
- devices shows 1.7.0 as current version
Any help or ideas appreciated.
Dave Mehlberg
You can see Overview of F5 rSeries system services and see if the service containers like "vanquish-gui" and "http-server" are running and restart them if needed. Also you log into them but I for rSeries most containers should mount the logs to the host var/log folder (you can just upload qkview to ihealth and take a look from there as it is the easiest for me 😃) and see their docker logs and use tools like ''docker inspect'' and '''docker logs'' to also see if there is an issue. Also just in case if docker commands do not work try ""crictl "" as in newer kubernetes versions it replaces docker runtime for container management. I also suggest checking the rSeries appliance.log file as I have shown in Knowledge sharing: Velos and rSeries (F5OS) basic troubleshooting, logs and commands | DevCentral
Oops...sorry I read too fast, I had seen i-Series in the title ! in fact F5OS is not based on TMOS :/
Hi,
Have you try a configuration check to verify if all is OK ? ( https://my.f5.com/manage/s/article/K53233552)tmsh load sys config verify partitions all
You can also check the httpd status and the log files /var/log/messages and /etc/httpd/logs
systemctl status httpd -l
Regards
Libdev,
I don't think tmsh is part of the f5OS ( i could be wrong - the r-series are proving difficult ). And apparently httpd isn't controlled by systemctl - when not in admin mode/su.
Dave
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com