Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support Solaris: Not able to access E2900 console Post 302743839 by solaris_1977 on Thursday 13th of December 2012 11:51:40 AM
Old 12-13-2012
Console IP is not pingable, earlier it used to ping. It was setup with static ip. Consoles connected to other ports on same switch are working, and there is no change on switch side.
I will try more to check, if there is any option to bounce lom, without reboot of server.
Thanks for trying helping me.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

console access via serial port - settings

looking for the answer to console port access via 25pin serial. Can i tip in from another unix box for access? (5 Replies)
Discussion started by: simplimarvelous
5 Replies

2. HP-UX

Access with console.

hi, is it possible to have a console access on a HP UX system without Web Console ? If yes, how ??? Many thanks in advance. :D (3 Replies)
Discussion started by: liliput
3 Replies

3. AIX

cant telnet to aix 5.2 and not even access through serial console

I have installed aix 5.2 on aix box through serial console connected to COM 1 . I even get a login prompt after the fresh installation . But as soon as i give a root & enter i again get a login prompt.i..e I am not able to logon after a fresh installation. and even i configured IP configuration... (0 Replies)
Discussion started by: linuxnightowl84
0 Replies

4. Solaris

USB Console access on Solaris 9 x86

Hi Guys, I installed solaris 9 on my laptop(x86). I want to access the solaris console by attaching another laptop to this. But i do not have a Serial Port on the laptop on which I installed Solaris. I was wondering whether there was an option of console access through a USB2USB or using... (1 Reply)
Discussion started by: com2com
1 Replies

5. AIX

Getting console access on freshly built AIX 5.2

Hi folks, I'm unfortunately only a Solaris/Linux guy and have a problem I can't solve. As part of an assessment of some network security software, I need to perform vulnerability scans and log (syslog event) collection from an AIX box. So I have a pSeries "B80" in front of me running AIX 5.2... (8 Replies)
Discussion started by: kaldek
8 Replies

6. Solaris

Sunfire V100 console access

Hi guys, My current set up is I have a Laptop running redhat linux. This acts as an SSH server, and i use it to console into the LOM-A port on my Sunfire V100 using minicom. The idea is that I can remotely access and test things out. This works great, but I've just bought another V100 server... (15 Replies)
Discussion started by: Stin
15 Replies

7. Shell Programming and Scripting

how to access console of a switch having rj45 on switch side to db 9 female on pc side console cable

hi, how to access console of a switch having rj45 on switch side to db 9 female on pc side console cable which needs to be connected to one console server having rj11 on its side and db 9 female on other end.i.e. on switch side,console cable has rj45 and db 9 pin female connector on other side of... (1 Reply)
Discussion started by: pankajd
1 Replies

8. AIX

P550 Unable to access Console

I have recently aquired the following machine: IBM,9113-550 Up until yesterday we could connect a dumb terminal to serial port 1 and get console login. However the dumb terminal died. We are now using a laptop with a null modem cable attached to serial port 1. This works perfectly for all of... (1 Reply)
Discussion started by: rsw7724
1 Replies

9. AIX

How to access root from console even if loginretries already reached

Hi, I wanted to know whether there is a setting in AIX to allow console login eventhough loginretries have already reached. What I mean is that loginretries applies to ssh/telnet connection but I can still login in console even after loginretries have been reached. Thanks. (2 Replies)
Discussion started by: depam
2 Replies

10. AIX

How to access console for P650 server.

Hi Everyone, we had a one IBM P650 standalone server, planning to install AIX OS on top of it, I don't have HMC, is their a way to access to console of the server using serial cable or any other option for installing OS on top of it. Thanks, (1 Reply)
Discussion started by: bobby320
1 Replies
vntsd(1M)						  System Administration Commands						 vntsd(1M)

NAME
vntsd - virtual network terminal server daemon for Logical Domains SYNOPSIS
/usr/lib/ldoms/vntsd DESCRIPTION
The vntsd daemon is a server that supports connections to the Logical Domains (LDoms) console by using telnet(1). When a telnet session starts, vntsd sends telnet options to the client indicating a willingness to remotely echo characters and to suppress go ahead. Consoles are organized into groups by the LDoms Manager. Each console group is assigned a unique group name and TCP port number. vntsd uses the group's port number to export access to the consoles within that group. To establish a connection with a console or console group, a user starts a telnet(1) session with the corresponding group's port number. Depending on the number of consoles within that group, vntsd does one of two things: o If there is only one console in the group, vntsd connects a session to that LDoms console. o If there are multiple consoles in the group, vntsd prompts the user to select the console to which they would like to connect, as shown in "Multiple-Console Options," below. For each console, vntsd provides write access only to the first user connecting to the console. Subsequent users connecting to the console are allowed only to read from the console and wait for write access. When the first user disconnects, write privileges are transferred to the next user waiting in the queue. If a user who does not have write privileges attempts to write to a console, the vntsd displays the following message: You do not have write access A user who has no write access can acquire write access forcibly by using the ~w special console command, described in "Special Console Commands," below. vntsd can be invoked only with superuser privileges or by someone in the Primary Administrator role. OPTIONS
The options for vntsd are divided into multiple-console options and console commands. Multiple-Console Options The options listed below are supported when there are multiple LDoms consoles in a group. The syntax for the use of these options is: <hostname>-vnts-<group-name>: <option> For example: myhost-vnts-salesgroup: h The h option invokes help, as described below. h Display the following help text: h -- this help l -- list of consoles q -- quit c{id}, n{name} -- connect to console of domain {id} or domain name l List all consoles in the group. For example: DOMAIN ID DOMAIN NAME DOMAIN STATE 0 ldg1 online 1 ldg2 connected ... ... ... The two domain states and their meanings are: online No one is connected to the console. connected At least one user is already connected to the console. q Disconnect from vntsd. c{id}, n{name} Connect to specified console. Upon connection, the following message is displayed: Connecting to console <domain-name> in group <group-name> Press ~? for control options .... Special Console Commands A tilde (~) appearing as the first character of a line is an escape signal that directs vntsd to perform a special console command. The tilde-tilde (~~) sequence outputs a tilde. In conjunction with the initial tilde, vntsd accepts the following special console commands: ~. Disconnect from the console or console group. ~w Force write access to the console. ~p Disconnect from this console, and connect to the console that precedes this console in the list of consoles. ~n Disconnect from this console, and connect to the console that follows this console in the list of consoles. ~# Send break. ~? Display vntsd help, as follows: ~# - Send break ~. - Exit from this console ~w - Force write access ~n - Console next ~p - Console previous ~? - Help FILES
/usr/lib/ldoms/vntsd Binary executable vntsd file. /usr/lib/ldoms/vntsd.xml Service management facility (smf(5)) manifest file for vntsd. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWldoms | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
telnet(1), svccfg(1M), usermod(1M), auth_attr(4), attributes(5), smf(5) NOTES
The vntsd is managed by the service management facility, smf(5), under the service identifier: svc:/ldoms/vntsd You can change the following properties using the svccfg(1M) command: vntsd/vcc_device Set an instance of the virtual console concentrator (vcc) driver to which vntsd is connected. vntsd/listen_addr Set the IP address to which vntsd listens, using the following syntax: vntsd/listen_addr:"xxx.xxx.xxx.xxx" ...where xxx.xxx.xxx.xxx is a valid IP address. The default value of this property is to listen on IP address 127.0.0.1. Users can con- nect to a guest console over a network if the value is set to the IP address of the control domain. Note - Enabling network access to a console has security implications. Any user can connect to a console and for this reason it is disabled by default. vntsd/timeout_minutes Set timeout in minutes. vntsd will timeout (close) telnet connection if there is no activity (input or output) on the console. The default value is 0, which disables timeout. vntsd/authorization Enable the authorization checking of users and roles for the domain console or consoles that are being accessed. The default value of this property is false to maintain backward compatibility. To enable authorization checking, use the svccfg(1M) command to set the property value to true. While this option is enabled, vntsd listens and accepts connections on localhost. If the listen_addr property specifies an alternate IP address when this option is enabled, vntsd ignores the alternate IP address and continues to listen on local- host. Connections that are initiated from other hosts will also fail. Authorizations are available to access all consoles or console groups, or to access specific consoles or console groups. When the vntsd service is enabled, the following authorization is added to the authorization description database, auth_attr(4): solaris.vntsd.consoles:::Access All LDoms Guest Consoles:: Add any fine-grained authorizations based on the name of the console group. For example, if the name of the console group to be autho- rized is ldg1, add the following entry to the auth_attr(4) file: solaris.vntsd.console-ldg1:::Access Specific LDoms Guest Console:: By default, the authorization to access all consoles is assigned to the root user or role. The Primary Administrator (superuser) can use the usermod(1M) command to assign the required authorization or authorizations to other users or roles. The following example gives user user1 the authorization to access all domain consoles: # usermod -A "solaris.vntsd.consoles" user1 The following example gives user user1 the authorization to access the console group named ldg1: # usermod -A "solaris.vntsd.console-ldg1" user1 SunOS 5.11 13 Feb 2009 vntsd(1M)
All times are GMT -4. The time now is 09:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy