10-03-2018
ifconfig usage is depreciated in solaris 11.
It still works tho, but ipadm should be used.
We need to have output of those commands, to see your configuration.
Otherwise, we can guess, and words are often misunderstood.
You can change the names, addresses or whatever you see as sensitive information.
In Solaris there are two general ways to configure zone network.
Basically :
exclusive ip stack - a layer 2 network, with vnics created for each zone, having isolated ip stack.
shared ip stack - a layer 3 network, with global zone doing all the network stuff.
In first case, network configuration will be done from inside zone using standard ipadm command.
In second case, network stack is handled by zone configuration, where you define ip address, and other IP parameters using zonecfg
If zone is created from default template, an exclusive ip stack will be used.
Hope that helps.
Regards
Peasant.
9 More Discussions You Might Find Interesting
1. Solaris
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
2. Solaris
How to check the global zone name from local zone. (6 Replies)
Discussion started by: fugitive
6 Replies
3. Solaris
Hello,
I am attempting to install a newly configured Solaris 9 zone using the flash archive image provided on the sun website. Each time I run the install I get a failure during the Postprocess: Creating mount points. Following is the log:
Log File: /var/tmp/s9-zone.install.25457.log... (0 Replies)
Discussion started by: brialt1
0 Replies
4. Solaris
Hi,
I am new to zone creations in solaris 10. When I try to create a zone with "set ip-type=exclusive" it gives the usage.
OS
==
Solaris 10 11/06 s10s_u3wos_10 SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license... (17 Replies)
Discussion started by: niman
17 Replies
5. Solaris
Dears,
I would like to convert solaris 10 x86 and solaris 10 sparc (Global Zones) physical servers into Local zones.
i found a document which seems to be helpful but i'm stuck @ the 1st step.
to test this i want to do it 1st on x86 system running under vmware ESXi and if it succeeds i will... (1 Reply)
Discussion started by: mduweik
1 Replies
6. Solaris
Hi, I'd like to discuss the subject of backing up / cloning Solaris zone.
I was trying to clone zone A to zone B (Solaris 10 11/06: Cloning a Non-Global Zone on the Same System (System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones)). The first test... (7 Replies)
Discussion started by: aixlover
7 Replies
7. Solaris
Hi,
A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well?
Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies
8. Solaris
Hello all,
I am having an issue with an NFS share I have created between two Solaris 10 boxes. I want the share to have read/write permissions, but for some reason it is coming up as read-only on the client side mount despite "rw" being specified in the mount options.
Here is what I have... (6 Replies)
Discussion started by: fallersaur
6 Replies
9. UNIX for Beginners Questions & Answers
I'm trying to migrate a Solaris 10 flar archive from a Sun M3000 to a T4-1. When I first created the zone I followed the Oracle instructions here: Transitioning an Oracle Solaris 10 Instance to an Oracle Solaris 11 System - Transitioning From Oracle Solaris 10 to Oracle Solaris 11 That worked... (6 Replies)
Discussion started by: Michele31416
6 Replies
LEARN ABOUT DEBIAN
atalkd
ATALKD(8) Netatalk 2.2 ATALKD(8)
NAME
atalkd - AppleTalk RTMP, NBP, ZIP, and AEP manager
SYNOPSIS
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/netatalk/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 fields 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.
EXAMPLES
Below is an example configuration file for a sun4/40. The machine has two interfaces, ``le0'' and ``le1''. The ``le0'' interface is
configured 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/netatalk/atalkd.conf configuration file
BUGS
On some systems, atalkd can not be restarted.
SEE ALSO
atalkd.conf(5)
Netatalk 2.2 06 Sep 2004 ATALKD(8)