03-05-2020
On aggr0 you can only define IP address from native VLAN on those ports.
If you wish to define a tagged IP on the hypervisor, you need to create vlan interface, then define IP on that.
If you wish to use the interface for virtual machines, you define a VSW with aggr0 link.
Then you add a vnet via ldm command using that VSW.
You can have both on the hypervisor, vlan interfaces and VSW above aggr0, but of course with different IP addresses (vm and hypervisor).
I would recommend reading about Oracle VM server for SPARC and a bit about networking as well
Looks like you are mixing hypervisor and vm part regarding network.
Regards
Peasant.
These 2 Users Gave Thanks to Peasant For This Post:
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. IP Networking
Hello,
I've been using mode 4 with four slaves, however looking at ifconfig showed that the traffic was not balanced correctly between the interfaces, the outgoing traffic has been alot higher on the last slave.
Example:
eth0 RX 123.2 GiB TX 22.5 GiB
eth1 RX 84.8 GiB TX 8.3 GiB
eth2... (3 Replies)
Discussion started by: TehOne
3 Replies
6. Solaris
Hi All, I am trying to aggregate the NIC's,(igb2 and igb3) (igb0 is used by the physical system and igb1 is used by primary-vsw0) to create the domains on that for faster data transfer, I followed the process for creating the aggregation, dladm create-aggr -d igb2 -d igb3 1
after creating the... (2 Replies)
Discussion started by: buildscm
2 Replies
7. Solaris
I have setup link aggregation with 3 interfaces on my solaris 10 system.
All looks good but my problem is that the traffic is only going out bge0 and not the other 2 links.
bash-4.3# dladm show-aggr -s
key:33 ipackets rbytes opackets obytes %ipkts %opkts
... (3 Replies)
Discussion started by: primeaup
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,
This is Solaris-10 x86 platform.
I am not able to ping gateway associated with aggr50001. I am not getting idea, where could be issue. Please advise.
# netstat -nr
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
--------------------... (10 Replies)
Discussion started by: solaris_1977
10 Replies
LEARN ABOUT CENTOS
fipvlan
FIPVLAN(8) Open-FCoE Tools FIPVLAN(8)
NAME
fipvlan - Fibre Channel over Ethernet VLAN Discovery
SYNOPSIS
fipvlan [-c|--create] [-s|--start] [-m|--mode fabric|vn2vn] interfaces
fipvlan -a|--auto [-c|--create] [-d|--debug] [-s|--start] [-m|--mode fabric|vn2vn] [-l|--link-retry count]
fipvlan -h|--help
fipvlan -v|--version
DESCRIPTION
The fipvlan command performs Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) VLAN Discovery over Ethernet interfaces.
fipvlan can be used as a diagnostic tool to determine which VLANs have FCoE services available on a network, prior to configuring VLAN
interfaces and the Open-FCoE initiator. fipvlan can also be used to create VLAN interfaces as they are discovered, and to start the
Open-FCoE initiator. The --create and --start options are primarily intended to be used as part of an Open-FCoE boot solution. FCoE
instances started in this way cannot be destroyed or reset by fcoeadm.
fipvlan takes a list of network interface names to run the VLAN discovery protocol over, or the --auto option to use all available Ethernet
interfaces.
fipvlan will enable any interface which is found disabled. If no response is received on that interface it will be shutdown again when
fipvlan terminates.
OPTIONS
-a, --auto
Use all Ethernet interfaces currently available
-c, --create
Create network interfaces for discovered FCoE VLANs. If a VLAN device already exists for a discovered VLAN, a new VLAN device will not
be created.
-d, --debug
Enable debugging output
-s, --start
Start the Open-FCoE initiator on discovered FCoE VLANs
-m, --mode
fabric|vn2vn Specify whether VLAN discovery is performed in the default fabric mode, or in VN2VN mode.
-f, --suffix suffix
Append the specified string suffix to VLAN interface names.
-l, --link-retry count
Retry check for link up to count times. The link state is checked every 500 ms. The default number of retries is 20.
-h, --help
Display a help message with basic usage instructions
-v, --version
Display the fipvlan version string
VLAN NAMING CONVENTIONS
If a new VLAN device is created, it will have the name dev.vlan; where dev is the name of the Ethernet parent device and vlan is the
discovered VLAN ID number. An optional suffix may be appended to this with the the -f command line option.
EXAMPLES
Display all discoverable VLANs with FCoE services
fipvlan --auto
Discover FCoE VLANs on interface eth2, create VLAN devices and start the Open-FCoE initiator
fipvlan --create --start eth2
In this example if FCoE services were available on VLAN 101 of network interface eth2, then a VLAN interface eth2.101 would be created and
used as the parent device for the initiator.
SEE ALSO
fcoeadm(8) fcoemon(8)
SUPPORT
fipvlan is part of the fcoe-utils package, maintained through the Open-FCoE project. Resources for both developers and users can be found
at the Open-FCoE website http://open-fcoe.org/
Open-FCoE 03/18/2013 FIPVLAN(8)