02-19-2016
Hey Gull04 thanks for your concern, please find below answer to your qurry:
Yes both the cables are attached to the same switch.
Can you please describe 2nd point as I am new to this dladm part and configuration is done by our automatic installer team I might need their help to clarify this.
Regarding 3rd point, does it really effect how we configured vnics in zones?
Regards,
Amithreat
9 More Discussions You Might Find Interesting
1. Solaris
Hi there
I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question
Ive seen multiple websites that say the following
Does this also mean that if the... (2 Replies)
Discussion started by: hcclnoodles
2 Replies
2. UNIX for Advanced & Expert Users
Hi there
I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question
Ive seen multiple websites that say the following
Does this also mean that if the... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
3. AIX
Hi,
I need to setup a hacmp cluster (my first one, we usually use VCS on AIX), but I require more network bandwith than a normal gigabit etherchannel setup can provide, so I am thinking about using linkaggregation - 2 active adapters to one switch and a single backup adapter to another switch... (4 Replies)
Discussion started by: zxmaus
4 Replies
4. Solaris
Me again :)
I'm trying to find a page describing the L2, L3 und L4 modes of dladm.
It's nice to read "hashed by ip header", but how should I use that?
On the file-server it's ok to have the six interfaces serving six clients each on it's own. But an rsync connection via switch between two... (8 Replies)
Discussion started by: PatrickBaer
8 Replies
5. Solaris
I have need for a reliable and easy way to get from within a script, or a java class, the status of the network interface cards (whether the link is up, or down).
I believe the kernel status would be quicker to know if they were up or down rather than if a ping simply didnt respond back.
... (2 Replies)
Discussion started by: mrmurdock
2 Replies
6. Red Hat
Hi All,
RHEL4 on VM cannot get status network link down.
when I unplug network cable.
- ESX found interface down
- but VM RHEL4 not detect that !, It show still up (mii-tool)
Please help share you idea for my case.
ESXi 5.1.0, RHEL4
Thank you, (3 Replies)
Discussion started by: arm_naja
3 Replies
7. Solaris
Hi,
I'm not from the Solaris world and some of these things are new to me. Can someone tell me if it is possible to configure link aggregation without using LACP?
I am told etherchannel was setup without LACP. (3 Replies)
Discussion started by: techy1
3 Replies
8. IP Networking
Hi
ihave three link of internet and iwant to put one linux front of a firewall that this three linux speard firewall such az load balance and fialover but dont close any port and protocol and only firewall have been internet what way can i use for it ?
are there any script and services do that... (0 Replies)
Discussion started by: mnnn
0 Replies
9. Solaris
Hi,
I have Solaris-10 server and link aggregation is configured on this in below way
# dladm show-aggr
key: 1 (0x0001) policy: L4 address: 3c:d9:2b:ee:a8:a (auto)
device address speed duplex link state
bnx1 3c:d9:2b:ee:a8:a... (8 Replies)
Discussion started by: solaris_1977
8 Replies
LEARN ABOUT OPENSOLARIS
native
native(5) Standards, Environments, and Macros native(5)
NAME
native - native branded zone
DESCRIPTION
The native brand uses the branded zones framework described in brands(5) to run zones installed with the same software as is installed in
the global zone. The system software must always be in sync with the global zone when using a native brand.
SUB-COMMANDS
The following native brand-specific subcommand options are supported in zoneadm(1M).
attach [-u] [-b patchid]...
For native zones, zoneadm checks package and patch levels on the machine to which the zone is to be attached. If the packages/patches
that the zone depends on from the global zone are different (have different revision numbers) from the dependent packages/patches on
the source machine, zoneadm reports these conflicts and does not perform the attach. If the destination system has only newer dependent
packages/patches (higher revision numbers) than those on the source system, you can use the -u option to update the attached zone to
match the -revision packages and patches that exist on the new system. With -u, as in the default behavior, zoneadm does not perform an
attach if outdated packages/patches are found on the target system.
For native zones, one or more -b options can be used to specify a patch ID for a patch installed in the zone. These patches will be
backed out before the zone is attached or, if -u was also specified, updated.
install [-a archive] | [-d path] [-p] [-s] [-u] [-v] [-b patchid]...
The native brand installer supports installing the zone from either the software already installed on the system or from an image of an
installed system running the same release. This can be a full flash archive (see flash_archive(4)) or a cpio(1) or pax(1) "xustar" ar-
chive. The cpio archive be compressed with gzip or bzip2. The image can also be a level 0 ufsdump(1M), a path to the top-level of a
system's root tree, or a pre-existing zone path.
With no options the zone is installed using same software as is running the global zone.
To install the zone from a system image either the -a or -d is required. Either the -u or -p option is also required in this case.
-a archive
The path to a flash_archive(4), cpio(1), or pax(1) "xustar" archive, or a level0 ufsdump(1M), of an installed system. cpio archives
may be compressed using gzip or bzip2.
-b patchid
One or more -b options can be used to specify a patch ID for a patch installed in the system image. These patches will be backed
out during the installation process.
-d path
The path to the root directory of an installed system. If path is a hyphen (-), the zonepath is presumed to be already populated
with the system image.
-p
Preserve the system configuration after installing the zone.
-s
Install silently.
-u
Run sys-unconfig(1M) on the zone after installing it.
-v
Verbose output from the install process.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Uncommitted |
+-----------------------------+-----------------------------+
SEE ALSO
cpio(1), pax(1), zlogin(1), zonename(1), sys-unconfig(1M), ufsdump(1M), zoneadm(1M), zonecfg(1M), flash_archive(4), attributes(5),
brands(5), privileges(5), zones(5), lx_systrace(7D)
SunOS 5.11 13 Feb 2009 native(5)