However the other issue what I have right now is the interface is not getting up automatically. I mean even though in zone I check autoboot = true after rebbot zone is not booting automatically, I mean after every reboot zone goes to installed stage and I start gatting error for zone interface like below [/FONT]
Hi,
I am attempting to configure my ethernet interface on a Sun Blade 1500. I am testing out my network interface my connecting a crossover cable from my blade to a windows box. I would like to assign an ip address of 10.0.0.2 to "bge0" and netmask of "255.0.0.0". I have typed the following:
... (1 Reply)
Dear all,
I am a newbie in solaris and I need your advice.
I have a Solaris version 5.9 installed on Sunfire V240.
I am able to ssh the machine from putty remotely.
My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
We got a network card(e1000g0) with 1gb of speed and working with global zone. We got a new network interface card, we have to place that in slot and we have to use that card as dedicated network interface to the non-global zone(hyd_app) in V890.
As i never done this before, please explain me... (2 Replies)
Hi all
I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface?
If you have any ideas, please tell me then. Thank you (2 Replies)
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)
We have a Solaris 10 system with a solaris 9 branded zone. Trying to create a new lo interfaces i ended up rebooting the zone. The zone will not come up, it ran fine before i tried this. When i run the zoneadm -z zone-s9 boot command i get
"zoneadm: zone 'zone-s9': lo0:2: could not bring... (4 Replies)
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)
Is anyone aware of a method of configuring the boot order of zones and or LDOMS? (2 Replies)
Discussion started by: os2mac
2 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)