Basics
In a Logical Domains environment, console I/O from all domains, except the primary domain, is redirected to a service domain running the virtual console concentrator (vcc) and virtual network terminal server (vntsd) services, instead of the systems controller.
The virtual console concentrator service functions as a concentrator for all domains, console traffic, and interfaces with the virtual network terminal server daemon and exports access to each console through a UNIX socket.
To create a virtual console concentrator or VCC service to provide console access to LDOMs :
primary # ldm add-vcc port-range=5000-5100 primary-vcc0 primary
The VCC service can be named freely anything other that “primary-vcc0”. We are using unused ports from 5000 to 5100 as our LDOM console ports. Based on the above port range, the Guest LDom will be allocated a VCC port id.
# ldm start ldom1 # ldm list Name State Flags Cons VCPU Memory Util Uptime primary active -t-cv SP 4 4G 0.6% 4h 8m ldom1 active -t—- 5000 4 4G 0.2% 2m
Now you can connect to the virtual console of your guest domain by using telnet and the console number specified under the Cons column from above:
# telnet localhost 5000 Trying 127.0.0.1... Connected to localhost. Escape character is ‘^]’. Connecting to console “ldom1” in group “ldom1” .... Press ~? for control options ..
As in the above example the next Guest LDom will be using the next available free port. Normally the ports are assigned in ascending order. The service available for the Virtual Network Console is svc:/ldoms/vntsd.
Troubleshooting
1. Check for vntsd service
Check the virtual network terminal server daemon is enabled :
# svcs -l vntsd fmri svc:/ldoms/vntsd:default name virtual network terminal server enabled true state online next_state none state_time Wed Oct 15 16:03:54 2008 logfile /var/svc/log/ldoms-vntsd:default.log restarter svc:/system/svc/restarter:default contract_id 57 dependency optional_all/error svc:/milestone/network (online) dependency optional_all/none svc:/system/system-log (online)
Below is the default configuration of the the vntsd service :
svc:> select ldoms/vntsd svc:/ldoms/vntsd> listprop vntsd application vntsd/listen_addr astring localhost vntsd/timeout_minutes integer 0 vntsd/vcc_device astring virtual-console-concentrator@0 network dependency network/entities fmri svc:/milestone/network network/grouping astring optional_all network/restart_on astring error network/type astring service syslog dependency syslog/entities fmri svc:/system/system-log syslog/grouping astring optional_all syslog/restart_on astring none syslog/type astring service general framework general/entity_stability astring Unstable start method start/exec astring /lib/svc/method/svc-vntsd start/timeout_seco
Check for the possible errors in the /var/svc/log/ldoms-vntsd:default.log as well as in /var/adm/messages :
# more /var/svc/log/ldoms-vntsd:default.log
# egrep -i "console|vntsd" /var/adm/messages*
Try to stop and start the vntsd service :
# svcadm disable svc:/ldoms/vntsd:default # svcadm enable svc:/ldoms/vntsd:default
2. Check VCONs setup in LDOM configuration
# ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME primary active -n-cv- UART 8 24G 0.1% 0.1% 21d 1h 18m ldom1 active -n---- 5000 10 2304M 0.0% 0.0% 20d 21h 39m -- lines omitted --
# ldm list -o console
NAME
primary
VCC
NAME PORT-RANGE
primary-vcc0 5000-5100
VCONS
NAME SERVICE PORT LOGGING
UART
------------------------------------------------------------------------------
NAME
guest1
VCONS
NAME SERVICE PORT LOGGING
guest1 primary-vcc0@primary 5000 on
------------------------------------------------------------------------------
-- lines omitted --
3. Check devices and permission
# ls -l /devices/virtual-devices@100/channel-devices@200/virtual-console-concentra* crw------- 1 root sys 317, 2047 Sep 18 06:47 /devices/virtual-devices@100/channel-devices@200/virtual-console-concentrator@0:ctl crw------- 1 root sys 317, 0 Sep 18 06:47 /devices/virtual-devices@100/channel-devices@200/virtual-console-concentrator@0:ldom-guest1 crw------- 1 root sys 317, 1 Sep 18 06:47 /devices/virtual-devices@100/channel-devices@200/virtual-console-concentrator@0:ldom-guest2 crw------- 1 root sys 317, 2 Sep 18 06:47 /devices/virtual-devices@100/channel-devices@200/virtual-console-concentrator@0:ldom-guest3
4. Check with netstat on the vcc port numbers
Check for the LDOM ports in netstat output. It should be in LISTEN mode when associated LDOM is started.
# netstat -a | egrep ".50[0-90-9]" controldomain.5000 *.* 0 0 128000 0 LISTEN controldomain.5001 *.* 0 0 128000 0 LISTEN controldomain.5002 *.* 0 0 128000 0 LISTEN controldomain.5003 *.* 0 0 128000 0 LISTEN
5. You might consider to remove and re-add the vcc
This might be the last option, you can try. Simply remove and re-add the vcc.
# ldm remove-vcc [-f] primary-vcc0 # ldm add-vcc port-range=5000-5100 primary-vcc0 primary
5. Contact support
If all above fails, contact the support team with the necessary data and logs.