Sponsored Content
Operating Systems Solaris Can not use zone in LDoms on T4-1 Post 302839765 by os2mac on Friday 2nd of August 2013 04:48:58 PM
Old 08-02-2013
so you need a new vnet device for each new zone

so in the primary LDOM:

you need to do

Code:
ldm add-vnet
Usage:
        ldm add-vnet [mac-addr=<num>] [mode=hybrid] [pvid=<pvid>]
                [alt-mac-addrs=auto|<num1>[,auto|<num2>,...]]
                [vid=<vid1,vid2,...>] [mtu=<mtu>] [linkprop=phys-state]
                [id=<networkid>] <if_name> <vswitch_name> <ldom>

for each zone you want to have an interface for...

Then in the LDOM:

prior to zone startup you need to do
Code:
ipadm remove-ip "netname"

That will free up the network interface on the vswitch for the zone.

then either in the zoneconfig set the network physical property or
after boot do
Code:
ipadm create-ip "netname"

then do
Code:
ipadm create-addr
usage:
        create-addr     [-t] [-T static] [-d] -a {local|remote}=addr[/prefixlen]
                                <addrobj>
        create-addr     [-t] -T dhcp [-w <seconds> | forever] [-h <hostname>]
                                <addrobj>
        create-addr     [-t] -T addrconf [-i {local|remote}=interface-id]
                                [-p {stateful|stateless}={yes|no}] <addrobj>

---------- Post updated at 12:23 PM ---------- Previous update was at 12:18 PM ----------

I would also like to add that if these are Solaris 10 zones in a Solaris 11 LDOM the procedure changes.

---------- Post updated at 12:48 PM ---------- Previous update was at 12:23 PM ----------

I reread your original post, yes the problems appear to be related because you don't have a network adapter configured on your config.
This User Gave Thanks to os2mac For This Post:
 

9 More Discussions You Might Find Interesting

1. Solaris

Bind zone transfer recategorises zone file?

Hi, I have a primary/slave Bind 9 setup running on a Solaris 10 platform. Everything is hunky dorey, except for when I make a zone file change and up the serial the file that is transferred to the slave looses all its comments, and the entries are place in alphabetical order. I administer many... (1 Reply)
Discussion started by: fulhamfcboy
1 Replies

2. Solaris

Solaris Zone : Non global Zone check failed

Hi All , I try to install some packages in my global zone... On the execution of the installion of the script it quits by saying the error "Non global zone check failed" Kindly help me in this regard Thanks in advance, jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies

3. Solaris

Not able to ping global zone from local zone

Hi Gurus I am not able to ping the local zone from global zone when i am trying to ping i am getting below ICMP Host Unreachable from gateway zone ( 192.268.35.210) for icmp from zone ( 192.168.35.210) to sun1 ( 192.168.35.210) However i can ping local zone from global please... (12 Replies)
Discussion started by: kumarmani
12 Replies

4. Solaris

how to add a default gateway in a zone of different VLAN of global zone

Hi Greetings... I have an issue in connecting the zone from outside the network and it is because of default gateway. I can ping default gateway from inside the zone and not able to ping from global zone due to different VLAN issue. If i add two different gateways and restart network services,... (2 Replies)
Discussion started by: vvpotugunta
2 Replies

5. Solaris

Zone failes to boot due to mount issue, dir exists in zone.

I have two physical servers, with zones that mount local storage. We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point). It failed to mount on every boot because the directory existed in the zone. I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies

6. Solaris

showing 2 different time zones in global zone and nonglobal zone

can some one help me out as it is showing 2 different time zones in global zone and nonglobal zone .In global zone it is showing in GMT while in nonglobal zone i it showing as PDT. System in running with solaris 10 (3 Replies)
Discussion started by: ravijanjanam12
3 Replies

7. Solaris

Scripting changes to multiple zone configurations in the same Global Zone

So this is Solaris 11.1. I have a Global zone that has several non-global zones running in it. I want to change the capped-memory.physical resources setting in ALL the zone configs of the running zones. if I were to do this manually here's what I would do: zonecfg -z zone1 select... (2 Replies)
Discussion started by: os2mac
2 Replies

8. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

Dear all, recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes. I did the following: host1: $ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed $ zpool export zone1 host2: $ zpool... (2 Replies)
Discussion started by: custos
2 Replies

9. Solaris

Solaris 11 zone has no external network access (except to Global Zone)

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)
Discussion started by: GazinLincoln
2 Replies
ATALKD(8)						      System Manager's Manual							 ATALKD(8)

NAME
atalkd - AppleTalk RTMP, NBP, ZIP, and AEP manager SYNOPSIS
/usr/sbin/atalkd [ -f configfile ] [ -1 | -2 ] DESCRIPTION
atalkd is responsible for all user level AppleTalk network management. This includes routing, name registration and lookup, zone lookup, and the AppleTalk Echo Protocol (similar to ping(8)). atalkd is typically started at boot time, out of /etc/rc. It first reads from its configuration file, /etc/atalk//atalkd.conf. If there is no configuration file, atalkd will attempt to configure all available interfaces and will create a configuration file. The file consists of a series of interfaces, one per line. Lines with `#' in the first column are ignored, as are blank lines. The syntax is interface [ -seed ] [ -phase number ] [ -net net-range ] [ -addr address ] [ -zone zonename ] ... Note that all field except the interface are optional. The loopback interface is configured automatically. If -seed is specified, all other fields must be present. Also, atalkd will exit during bootstrapping, if a router disagrees with its seed information. If -seed is not given, all other information may be overriden during auto-configuration. If no -phase option is given, the default phase as given on the command line is used (the default is 2). If -addr is given and -net is not, a net-range of one is assumed. The first -zone directive for each interface is the ``default'' zone. Under Phase 1, there is only one zone. Under Phase 2, all routers on the network are configured with the default zone and must agree. atalkd maps ``*'' to the default zone of the first interface. Note: The default zone for a machine is determined by the configuration of the local routers; to appear in a non-default zone, each service, e.g. afpd, must individually specify the desired zone. See also nbp_name(3). ROUTING
If you are connecting a netatalk router to an existing AppleTalk internet, you should first contact your local network administrators to obtain appropriate network addresses. atalkd can provide routing between interfaces by configuring multiple interfaces. Each interface must be assigned a unique net-range between 1 and 65279 (0 and 65535 are illegal, and addresses between 65280 and 65534 are reserved for startup). It is best to choose the smallest useful net-range, i.e. if you have three machines on an Ethernet, don't chose a net-range of 1000-2000. Each net-range may have an arbitrary list of zones associated with it. EXAMPLE
Below is an example configuration file for a sun4/40. The machine has two interfaces, ``le0'' and ``le1''. The ``le0'' interface is con- figured automatically from other routers on the network. The machine is the only router for the ``le1'' interface. le0 le1 -seed -net 9461-9471 -zone netatalk -zone Argus atalkd automatically acts as a router if there is more than one interface. FILES
/etc/atalk//atalkd.conf configuration file BUGS
On some systems, atalkd can not be restarted. netatalk 1.3 17 Nov 1995 ATALKD(8)
All times are GMT -4. The time now is 11:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy