Sponsored Content
Full Discussion: Solaris LDOM IP conflict
Operating Systems Solaris Solaris LDOM IP conflict Post 303043670 by Michele31416 on Monday 3rd of February 2020 01:56:42 PM
Old 02-03-2020
Thanks! The ipadm command worked! I now have networking again at 192.168.0.78 on the LDOM. But now I have a new problem. When I start the LDOM console, it won't let me in. (But I can successfully ssh to the LDOM and also open a vncviewer to it).

Code:
root@hemlock:~# ldm start sol10
LDom sol10 started
root@hemlock:~# ldm list
NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  NORM  UPTIME
primary          active     -n-cv-  UART    32    16G      0.8%  0.8%  5d 23h 56m
sol10            active     -t----  5000    32    32G      0.6%  0.6%  2s
root@hemlock:~# telnet localhost 5000
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

Connecting to console "sol10" in group "sol10" ....
Press ~? for control options ..
Hostname: avon
Feb  3 12:39:14 svc.startd[11]: svc:/application/management/ocm:default: Method "/lib/svc/method/svc-ocm start" failed with exit status 95.
Feb  3 12:39:14 svc.startd[11]: application/management/ocm:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)

avon console login: You do not have write access
You do not have write access

(message repeats every time I press a key)

And in the LDOM (captured from an ssh window):
Code:
/export/home/michele$ svcs -xv
svc:/application/print/server:default (LP print server)
 State: disabled since Mon Feb 03 12:38:57 2020
Reason: Disabled by an administrator.
   See: http://sun.com/msg/SMF-8000-05
   See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
        svc:/application/print/rfc1179:default
        svc:/application/print/ipp-listener:default

svc:/application/management/ocm:default (Oracle Configuration Manager)
 State: maintenance since Mon Feb 03 12:39:14 2020
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
   See: http://sun.com/msg/SMF-8000-KS
   See: /var/svc/log/application-management-ocm:default.log
Impact: This service is not running.
/export/home/michele $ more /var/svc/log/application-management-ocm:default.log
...
[ Feb  3 12:38:57 Enabled. ]
[ Feb  3 12:39:13 Executing start method ("/lib/svc/method/svc-ocm start") ]
OCM is marked as disconnected.
Use emocmrsp -output /opt/ocm/ocm.rsp to create a response file and reconfigure
with configCCR -R /opt/ocm/ocm.rsp.
[ Feb  3 12:39:14 Method "start" exited with status 95 ]

Is this non-running service anything important?

--- Post updated at 02:56 PM ---

Quote:
Originally Posted by Neo
You might considering flushing your ARP cache(s), or simply waiting until the ARP entries to timeout.
Thanks. I didn't even know about that. That will be good to know for next time. In the end I went with the ipadm method.
 

8 More Discussions You Might Find Interesting

1. Solaris

Installing Solaris into LDom using DVD

Hi, I have issues installing Solaris into a LDom using a Solaris10u5/08 DVD. I have been troubleshooting for the past 2 days and I still cannot get it up. Here is the logs: root@eld-app2# ldm add-vdsdev /cdrom/sol_10_508_sparc/s0 cdrom0@primary-vds0 root@eld-app2# ldm add-vdisk cdrom0... (4 Replies)
Discussion started by: bolasutra
4 Replies

2. Solaris

Solaris 9 IP conflict

Hi Gurus I am in a strange situation. I have a SUN sparc server . The server was having an IP say X..... (this IP X is now being used by another server)..... I have just installed fresh solaris 9 OS on the same server and given new IP say Y. I also configured probe based IPMP with ce0 and... (2 Replies)
Discussion started by: ningy
2 Replies

3. Solaris

Installing Solaris OS on LDOM SAN Disk

I have viewed a few previous posts regarding this, but none of them quite described or worked with my issue. I am out of local disk space on my LDOM Manager but still have plenty of SAN vCPU and Memory available so I am trying to install a new LDOM OS on SAN. I have exposed the SAN to the... (0 Replies)
Discussion started by: MobileGSP
0 Replies

4. Solaris

ZFS LDOM problem on Solaris 10

Apologies if this is the wrong forum.. I have some LDOMs running on a Sparc server. I copied the disk0 file from one chassis over to another, stopped the ldom on the source system and started it on the 2nd one. All fine. Shut it down and flipped back. We then did a fair bit of work on the... (4 Replies)
Discussion started by: tommyq
4 Replies

5. Solaris

How can I install Solaris 10 on an LDom using an iso?

Hello, I am trying to install Solaris 10 on a newly created LDom. Here are the commands I ran to create the LDom: ldm add-domain ldg2 ldm add-vcpu 8 ldg2 ldm add-memory 2g ldg2 ldm add-vnet vnet2 primary-vsw0 ldg2 ldm add-vdsdev /dev/dsk/c0t5000CCA01535E20Cd0s0 vol2@primary-vds0 ldm... (8 Replies)
Discussion started by: bstring
8 Replies

6. Solaris

Virtual Switch in Solaris LDOM

Hi, Our existing environment is having primary domain and 3 guest domains are running over it. See the attached image. Now we want to add a new primary virtual switch and move LDOM3 to be connected with new primary switch. So, I am not sure how to achieve this because. If I remove the... (7 Replies)
Discussion started by: praveensharma21
7 Replies

7. Solaris

Ldom guest volumen problem t8 Solaris 11

hello to everyone. im new member here. i have a problem with a guest ldom on solaris 11 sparc in a T8. I need to access to disk vds assigned to guest domain but from control domain. I want to modify a parameter in inittab of the guest domain because start guest domain give me problems... (2 Replies)
Discussion started by: Liam_
2 Replies

8. UNIX for Beginners Questions & Answers

Solaris 11 LDOM guest network not working

I'm really stuck here. I've created an LDOM on a SPARC T4-1 with Solaris 11.4 to run a copy of Linux for SPARC. I got the Linux ISO installed and Linux itself installed and booted OK. The only thing is is that there's no networking available in the Linux guest. This question is basically the... (7 Replies)
Discussion started by: Michele31416
7 Replies
svcs(1) 							   User Commands							   svcs(1)

NAME
svcs - report service status SYNOPSIS
svcs [-aHpv?] [-o col[,col]]... [-R FMRI-instance]... [-sS col]... [FMRI | pattern]... svcs {-d | -D} [-Hpv?] [-o col[,col]]... [-sS col]... [FMRI | pattern] ... svcs -l [-v] [FMRI | pattern]... svcs -x [-v] [FMRI]... DESCRIPTION
The svcs command displays information about service instances as recorded in the service configuration repository. The first form of this command prints one-line status listings for service instances specified by the arguments. Each instance is listed only once. With no arguments, all enabled service instances, even if temporarily disabled, are listed with the columns indicated below. The second form prints one-line status listings for the dependencies or dependents of the service instances specified by the arguments. The third form prints detailed information about specific services and instances. The fourth form explains the states of service instances. For each argument, a block of human-readable text is displayed which explains what state the service is in, and why it is in that state. With no arguments, problematic services are described. Error messages are printed to the standard error stream. The output of this command can be used appropriately as input to the svcadm(1M) command. OPTIONS
The following options are supported: -? Displays an extended usage message, including column specifiers. -a Show all services, even disabled ones. This option has no effect if services are selected. -d Lists the services or service instances upon which the given service instances depend. -D Lists the service instances that depend on the given services or service instances. -H Omits the column headers. -l (The letter ell.) Displays all available information about the selected services and service instances, with one ser- vice attribute displayed for each line. Information for different instances are separated by blank lines. The following specific attributes require further explanation: dependency Information about a dependency. The grouping and restart_on properties are displayed first and are sepa- rated by a forward slash (/). Next, each entity and its state is listed. See smf(5) for information about states. In addition to the standard states, each service dependency can have the following state descrip- tions: absent No such service is defined on the system. invalid The fault management resource identifier (FMRI) is invalid (see smf(5)). multiple The entity is a service with multiple instances. File dependencies can only have one of the following state descriptions: absent No such file on the system. online The file exists. If the file did not exist the last time that svc.startd evaluated the service's dependencies, it can consider the dependency to be unsatisfied. svcadm refresh forces dependency re-evalua- tion. unknown stat(2) failed for a reason other than ENOENT. See smf(5) for additional details about dependencies, grouping, and restart_on values. enabled Whether the service is enabled or not, and whether it is enabled or disabled temporarily (until the next system reboot). The former is specified as either true or false, and the latter is designated by the presence of (temporary). A service might be temporarily disabled because an administrator has run svcadm disable -t, used svcadm milestone, or booted the system to a specific milestone. See svcadm(1M) for details. -o col[,col]... Prints the specified columns. Each col should be a column name. See COLUMNS below for available columns. -p Lists processes associated with each service instance. A service instance can have no associated processes. The process ID, start time, and command name (PID, STIME, and CMD fields from ps(1)) are displayed for each process. -R FMRI-instance Selects service instances that have the given service instance as their restarter. -s col Sorts output by column. col should be a column name. See COLUMNS below for available columns. Multiple -s options behave additively. -S col Sorts by col in the opposite order as option -s. -v Without -x or -l, displays verbose columns: STATE, NSTATE, STIME, CTID, and FMRI. With -x, displays extra information for each explanation. With -l, displays user-visible properties in property groups of type application and their description. -x Displays explanations for service states. Without arguments, the -x option explains the states of services which: o are enabled, but are not running. o are preventing another enabled service from running. OPERANDS
The following operands are supported: FMRI A fault management resource identifier (FMRI) that specifies one or more instances (see smf(5)). FMRIs can be abbreviated by specifying the instance name, or the trailing portion of the service name. For example, given the FMRI: svc:/network/smtp:sendmail The following are valid abbreviations: sendmail :sendmail smtp smtp:sendmail network/smtp The following are invalid abbreviations: mail network network/smt If the FMRI specifies a service, then the command applies to all instances of that service, except when used with the -D option. Abbreviated forms of FMRIs are unstable, and should not be used in scripts or other permanent tools. pattern A pattern that is matched against the FMRIs of service instances according to the "globbing" rules described by fnmatch(5). If the pattern does not begin with svc:, then svc:/ is prepended. The following is a typical example of a glob pattern: qexample% svcs *keyserv* STATE STIME FMRI disabled Aug_02 svc:/network/rpc/keyserv:default FMRI-instance An FMRI that specifies an instance. COLUMNS
Column names are case insensitive. The default output format is equivalent to "-o state,stime,fmri". The default sorting columns are STATE, STIME, FMRI. CTID The primary contract ID for the service instance. Not all instances have valid primary contract IDs. DESC A brief description of the service, from its template element. A service might not have a description available, in which case a hyphen (-) is used to denote an empty value. FMRI The FMRI of the service instance. INST The instance name of the service instance. NSTA The abbreviated next state of the service instance, as given in the STA column description. A hyphen denotes that the instance is not transitioning. Same as STA otherwise. NSTATE The next state of the service. A hyphen is used to denote that the instance is not transitioning. Same as STATE otherwise. SCOPE The scope name of the service instance. SVC The service name of the service instance. STA The abbreviated state of the service instance (see smf(5)): DGD degraded DIS disabled LRC legacy rc*.d script-initiated instance MNT maintenance OFF offline ON online UN uninitialized Absent or unrecognized states are denoted by a question mark (?) character. An asterisk (*) is appended for instances in transi- tion, unless the NSTA or NSTATE column is also being displayed. See smf(5) for an explanation of service states. STATE The state of the service instance. An asterisk is appended for instances in transition, unless the NSTA or NSTATE column is also being displayed. See smf(5) for an explanation of service states. STIME If the service instance entered the current state within the last 24 hours, this column indicates the time that it did so. Other- wise, this column indicates the date on which it did so, printed with underscores (_) in place of blanks. EXAMPLES
Example 1 Displaying the Default Output This example displays default output: example% svcs STATE STIME FMRI ... legacy_run 13:25:04 lrc:/etc/rc3_d/S42myscript ... online 13:21:50 svc:/system/svc/restarter:default ... online 13:25:03 svc:/milestone/multi-user:default ... online 13:25:07 svc:/milestone/multi-user-server:default ... Example 2 Listing All Local Instances This example lists all local instances of the service1 service. example% svcs -o state,nstate,fmri service1 STATE NSTATE FMRI online - svc:/service1:instance1 disabled - svc:/service1:instance2 Example 3 Listing Verbose Information This example lists verbose information. example% svcs -v network/rpc/rstat:udp STATE NSTATE STIME CTID FMRI online - Aug_09 - svc:/network/rpc/rstat:udp Example 4 Listing Detailed Information This example lists detailed information about all instances of system/service3. Additional fields can be displayed, as appropriate to the managing restarter. example% svcs -l network/rpc/rstat:udp fmri svc:/network/rpc/rstat:udp enabled true state online next_state none restarter svc:/network/inetd:default contract_id dependency require_all/error svc:/network/rpc/bind (online) Example 5 Listing Processes example% svcs -p sendmail STATE STIME FMRI online 13:25:13 svc:/network/smtp:sendmail 13:25:15 100939 sendmail 13:25:15 100940 sendmail Example 6 Explaining Service States Using svcs -x (a) In this example, svcs -x has identified that the print/server service being disabled is the root cause of two services which are enabled but not online. svcs -xv shows that those services are print/rfc1179 and print/ipp-listener. This situation can be rectified by either enabling print/server or disabling rfc1179 and ipp-listener. example% svcs -x svc:/application/print/server:default (LP print server) State: disabled since Mon Feb 13 17:56:21 2006 Reason: Disabled by an administrator. See: http://sun.com/msg/SMF-8000-05 See: lpsched(1M) Impact: 2 dependent services are not running. (Use -v for list.) (b) In this example, NFS is not working: example$ svcs nfs/client STATE STIME FMRI offline 16:03:23 svc:/network/nfs/client:default (c) The following example shows that the problem is nfs/status. nfs/client is waiting because it depends on nfs/nlockmgr, which depends on nfs/status: example$ svcs -xv nfs/client svc:/network/nfs/client:default (NFS client) State: offline since Mon Feb 27 16:03:23 2006 Reason: Service svc:/network/nfs/status:default is not running because a method failed repeatedly. See: http://sun.com/msg/SMF-8000-GE Path: svc:/network/nfs/client:default svc:/network/nfs/nlockmgr:default svc:/network/nfs/status:default See: man -M /usr/share/man -s 1M mount_nfs See: /var/svc/log/network-nfs-client:default.log Impact: This service is not running. EXIT STATUS
The following exit values are returned: 0 Successful command invocation. 1 Fatal error. 2 Invalid command line options were specified. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ Screen output is Uncommitted. The invocation is Committed. SEE ALSO
ps(1), svcprop(1), svcadm(1M), svccfg(1M), svc.startd(1M), stat(2), libscf(3LIB), attributes(5), fnmatch(5), smf(5) SunOS 5.11 6 Nov 2008 svcs(1)
All times are GMT -4. The time now is 07:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy