Remove anet from zone configuration and then try add network interface explicity. You must have unused network interface in your LDOM. I assume that net1 is not used in your LDOM, so you can use it in your zone.
Hi Folks,
I am used to writing scripts to get info by running commands at local zones level from their respective global zone by using zlogin <localzone> "command>" while remaining at the global zone level.
Can the same be done with Guest LDoms while remaining at the control LDOM level?
... (4 Replies)
Hi,
There is LDOM Guest where I need to expand /u02 file systems on it.
It is residing on a Solaris 11 Hypervisor (Primary Domain).
The storage is expanded on vdisk presented to Hypervisor.
I need steps to expand the /u02 on LDOM Guest. (2 Replies)
T4-2 issues meant replacing motherboard.
I thought the ldom config was automatically saved? Got the oracle document here.
At the moment, unable to get ldoms back - here is the output from a few commands:-
ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME... (4 Replies)
Need assitance in troubleshooting steps . Below is the issue
I have LDOM which has 4 zones on it . One zone logging into the server takes 13sec where as other zones are quick .
Troubleshooting steps which I did
- Checked /var/tmp . Not many files
- We have LDAP but thought that wouldnt be... (7 Replies)
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
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)
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
LEARN ABOUT CENTOS
zone2ldap
zone2ldap(1) General Commands Manual zone2ldap(1)NAME
zone2ldap /- Load BIND 9 Zone files into LDAP Directory
SYNOPSIS
zone2ldap [-D Bind DN] [-w Bind Password] [-b Base DN] [-z Zone] [-f Zone File ] [-h Ldap Host] [-cd] [-v]
DESCRIPTION
zone2ldap will parse a complete BIND 9 format DNS zone file, and load the contents into an LDAP directory, for use with the LDAP sdb back-
end.
If the zone already exists, zone2ldap will exit succesfully. If the zone does not exists, or partially exists, zone2ldap will attempt to
add all/missing zone data.
Options
-b LDAP Base DN. LDAP systems require a "base dn", which is generally considered the LDAP Directory root. If the zone you are loading
is different from the base, then you will need to tell zone2ldap what your LDAP base is.
-v Print version information, and immediatly exit.
-f Zone file. Bind 9.1 compatible zone file, from which zone information will be read.
-d Dump debug information to standard out.
-w LDAP Bind password, corresponding the the value of "-b".
-h LDAP Directory host. This is the hostname of the LDAP system you wish to store zone information on. An LDAP server should be lis-
tening on port 389 of the target system. This may be ommited, and will default to "localhost".
-c This will create the zone portion of the DN you are importing. For instance, if you are creating a domain.com zone, zone2ldap should
first create "dc=domain,dc=com". This is useful if you are creating multiple domains.
-z This is the name of the zone specified in the SOA record.
EXAMPLES
Following are brief examples of how to import a zone file into your LDAP DIT.
Loading zone domain.com, with an LDAP Base DN of dc=domain,dc=com
zone2ldap -D dc=root -w secret -h localhost -z domain.com -f domain.com.zone
This will add Resource Records into an ALREADY EXISTING dc=domain,dc=com. The final SOA DN in this case, will be dc=@,dc=domain,dc=com
Loading customer.com, if your LDAP Base DN is dc=provider,dc=net.
zone2ldap -D dc=root -w secret -h localhost -z customer.com -b dc=provider,dc=net -f customer.com.zone -c
This will create dc=customer,dc=com under dc=provider,dc=net, and add all necessary Resource Records. The final root DN to the SOA will be
dc=@,dc=customer,dc=com,dc=provider,dc=net.
SEE ALSO named(8)ldap(3) http://www.venaas.no/ldap/bind-sdb/
BUGS
Send all bug reports to Jeff McNeil <jeff@snapcase.g-rock.net>
AUTHOR
Jeff McNeil <jeff@snapcase.g-rock.net>
8 March 2001 zone2ldap(1)