Troubleshooting Issues with Virtual Network Terminal Server Daemon vntsd(1M)
(Doc ID 1590708.1)
Last updated on DECEMBER 19, 2023
Applies to:
Solaris Operating System - Version 10 6/06 U2 and laterOracle Solaris on SPARC (64-bit)
Purpose
This document provides information on troubleshooting issues with Virtual Network Terminal Server Daemon (vntsd(1M)) in LDom configurations.
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Troubleshooting Steps |
| Confirm SMF service svc:/ldoms/vntsd:default is running and in state 'online' |
| Check VCONS setup in LDom configuration |
| Report error messages during invocation of 'telnet localhost' |
| Collect and check the output of /var/svc/log/ldoms-vntsd:default.log |
| Try to restart the vntsd SMF service |
| Check the loopback interface and make sure it is marked UP |
| Check console log and /var/adm/messages* for any console or vntsd error messages on primary domain |
| Check the status of the Domains |
| Get pfiles output of the PID of vntsd |
| Check devices and permission |
| Try to recreate VCC devices manually in case the device for a Guest domain is missing |
| Collect a truss on the PID of vntsd |
| Check with netstat on the vcc port numbers |
| vntsd collects console logs in Solaris 11 primary domains with LDom 3.0 and higher |
| You might consider to remove and re-add the vcc |
| Additional info to item 'Using Console Groups' |
| Possible error messages |
| vntsd goes to State: maintenance due to missing /var/log/vntsd |
| Troubleshooting issues with console input/output to/from Guest Domain |
| Check whether the guest domain is still running |
| References |