11-04-2019
That's a good point. There's just one Ethernet cable connected to the T4 so I don't need the ETH1 interface in the guest at all.
Thanks again for your help My next project is to port a Solaris 10 installation from an M3000 onto the T4. My plan at the moment is to make a flar archive of the M3000 and then load that into a new zone on the T4. Does that sound reasonable?
8 More Discussions You Might Find Interesting
1. Solaris
Hi,
Need help for the network configuration on Solaris 10 5/8.
My NIC's dirver was loaded after Solaris installation and is configured using static ip address for a local network: 172.16.1.12
I have configured set of files as: /etc/hosts :
172.16.1.12 ls12
/etc/hostname.iprb0:... (7 Replies)
Discussion started by: dn100
7 Replies
2. Virtualization and Cloud Computing
Howdy
I am using Fedora12 with KVM, with XP64pro as a guest. Everything seems to be working just fine, BUT I can't Save. When I do instruction KVM to save, I get a continuing Saving display, but it continues for a long time until I finally terminate it due to boredom :) I have let it run for... (0 Replies)
Discussion started by: TJMan
0 Replies
3. Solaris
Hi Folks,
I am used to writing scripts to get info by running commands at local zones level from their respective global zone by using zlogin <localzone> "command>" while remaining at the global zone level.
Can the same be done with Guest LDoms while remaining at the control LDOM level?
... (4 Replies)
Discussion started by: momin
4 Replies
4. Solaris
Solaris for Sparc 11.1 with the latest patches. Created a Guest LDOM with two vnet's net0 and net1, installed a guest whole root, ip exclusive zone that I want to be able to utilize DHCP. I have been able to create the zone but unable to get it to boot because I am unable to assign an anet to it.... (4 Replies)
Discussion started by: os2mac
4 Replies
5. UNIX for Dummies Questions & Answers
Hi!
I am not sure if this is the right place to post this question. What I did was to download vmware onto my laptop, them install a linux distro as a guest O.S., on VM network configuration I have used "bridge", them I used Virtual Network Editor to chose the network interface, but as I write... (4 Replies)
Discussion started by: fretagi
4 Replies
6. Solaris
Hi,
There is LDOM Guest where I need to expand /u02 file systems on it.
It is residing on a Solaris 11 Hypervisor (Primary Domain).
The storage is expanded on vdisk presented to Hypervisor.
I need steps to expand the /u02 on LDOM Guest. (2 Replies)
Discussion started by: vidya_sagar2003
2 Replies
7. 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
8. Solaris
hello to everyone. im new member here.
i have a problem with a guest ldom on solaris 11 sparc in a T8. I need to access to disk vds assigned to guest domain but from control domain.
I want to modify a parameter in inittab of the guest domain because start guest domain give me problems... (2 Replies)
Discussion started by: Liam_
2 Replies
EPAIR(4) BSD Kernel Interfaces Manual EPAIR(4)
NAME
epair -- A pair of virtual back-to-back connected Ethernet interfaces.
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device epair
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_epair_load="YES"
DESCRIPTION
The epair is a pair of Ethernet-like software interfaces, which are connected back-to-back with a virtual cross-over cable.
Each epair interface pair is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or
using the cloned_interfaces variable in rc.conf(5). While for cloning you only give either epair or epair<n> the epair pair will be named
like epair<n>[ab]. This means the names of the first epair interfaces will be epair0a and epair0b.
Like any other Ethernet interface, an epair needs to have a network address. Each epair will be assigned a locally administered address by
default, that is only guaranteed to be unique within one network stack. To change the default addresses one may use the SIOCSIFADDR ioctl(2)
or ifconfig(8) utility.
The basic intend is to provide connectivity between two virtual network stack instances. When connected to a if_bridge(4) one end of the
interface pair can also be part of another (virtual) LAN. As with any other Ethernet interface one can configure vlan(4) support on top of
it.
SEE ALSO
ioctl(2), altq(4), bpf(4), if_bridge(4), vlan(4), loader.conf(5,) rc.conf(5), ifconfig(8)
HISTORY
The epair interface first appeared in FreeBSD 8.0.
AUTHORS
The epair interface was written by Bjoern A. Zeeb, CK Software GmbH, under sponsorship from the FreeBSD Foundation.
BSD
July 26, 2009 BSD