05-19-2016
I'm sure the picture is wrong.
You just need to add a vnet to a new ldom. You don't add vsw to ldoms.
Is your VSW an aggregation perhaps, created over an aggregated interface ?
If not, then you will not be redundant in case of NIC or switch failure.
Best regards
Peasant.
8 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have issues installing Solaris into a LDom using a Solaris10u5/08 DVD. I have been troubleshooting for the past 2 days and I still cannot get it up.
Here is the logs:
root@eld-app2# ldm add-vdsdev /cdrom/sol_10_508_sparc/s0 cdrom0@primary-vds0
root@eld-app2# ldm add-vdisk cdrom0... (4 Replies)
Discussion started by: bolasutra
4 Replies
2. Solaris
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies
3. Solaris
Apologies if this is the wrong forum..
I have some LDOMs running on a Sparc server. I copied the disk0 file from one chassis over to another, stopped the ldom on the source system and started it on the 2nd one. All fine. Shut it down and flipped back. We then did a fair bit of work on the... (4 Replies)
Discussion started by: tommyq
4 Replies
4. Solaris
Hello,
I am trying to install Solaris 10 on a newly created LDom. Here are the commands I ran to create the LDom:
ldm add-domain ldg2
ldm add-vcpu 8 ldg2
ldm add-memory 2g ldg2
ldm add-vnet vnet2 primary-vsw0 ldg2
ldm add-vdsdev /dev/dsk/c0t5000CCA01535E20Cd0s0 vol2@primary-vds0
ldm... (8 Replies)
Discussion started by: bstring
8 Replies
5. Solaris
I have an Oracle VM set up with 1 virtual disk. I am trying to add 2 new disks to it. I was able to successfully add 1 (it appears when I run "format" in the VM) but when I add the second and third disks they do not appear in my VM.
Here are the commands I ran:
ldm add-vdsdev... (3 Replies)
Discussion started by: unblockable
3 Replies
6. Solaris
hello, I have a problem when configuring the network at the LDOM level, on a SPARC-Enterprise-T5120 machine
The network goes through VLAN 503 (level, network tagget)
And I need to give network to the guest domain: madarrwebsol10
I hope someone can bring some light ....
Excuse my English ...
... (4 Replies)
Discussion started by: Wittman
4 Replies
7. UNIX for Beginners Questions & Answers
Hello Guys,
Can some help me with a configuration from 2x10g cards to 4 Ldoms and a Vlan configuration,
Solaris 11
dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
net0 Ethernet up 1000 full ixgbe0
net1 Ethernet ... (2 Replies)
Discussion started by: roly
2 Replies
8. Solaris
I have a Sun T4-1 running Solaris 11.4 with a static IP 192.168.0.183. On this machine is a Solaris 10 LDOM with a static IP of 192.168.0.78. The other day I had to stop the LDOM to do a memory reconfigure. When I rebooted it I got an error that the IP 192.168.0.78 was already in use and so... (4 Replies)
Discussion started by: Michele31416
4 Replies
LEARN ABOUT NETBSD
xbdback
XBDBACK(4) BSD/xen Kernel Interfaces Manual XBDBACK(4)
NAME
xbdback -- Xen backend paravirtualized block device interface
SYNOPSIS
pseudo-device xbdback
DESCRIPTION
The xbdback interface forms the backend part of the paravirtualized drivers used by Xen domains to offer a block device interface, similar to
a hard disk. xbdback interfaces are backed either by a physical device directly, or an image file mounted through vnd(4).
All xbdback interfaces follow the ``xbdbackXiY'' naming convention, where 'X' represents the guest domain identifier, and 'Y' an arbitrary
identifier. This identifier is usually associated to the device node as seen by the guest using major(3) and minor(3) numbers. For example,
identifier ``769'' (0x301) means major 3 and minor 1, identified as ``hda1'' under Linux convention. For NetBSD, the guest device name spec-
ified in the guest configuration file does not matter, and can be chosen arbitrarily.
A xbdback interface will appear as a xbd(4) block device inside a NetBSD guest domain. In the XenStore, xbd and xbdback are identified by
``vbd'' (virtual block device) entries.
DIAGNOSTICS
xbd backend: attach device %s (size %d) for domain %d Gives the device used as xbdback interface for the given guest domain, and its size,
in bytes.
xbd backend 0x%x for domain %d using event channel %d, protocol %s Gives the backend identifier, guest domain ID, event channel ID, and pro-
tocol used for block level communication.
xbdback %s: can't VOP_OPEN device 0x%x: %d When this message appears in the system message buffer with error 16 (EBUSY), the device is
likely to be already mounted. It must be unmounted first, as the system will refuse to open it a second time.
SEE ALSO
vnd(4), xbd(4), xenbus(4)
HISTORY
The xbdback driver first appeared in NetBSD 4.0.
AUTHORS
The xbdback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.
BSD
June 7, 2011 BSD