dsw has it right. You can see the VLANs of virtual network adapters even if they are inside an etherchannel. My ent0 is on VLAN 10 and my ent1 is on VLAN 20. Here is an example from one of my boxes.
hi,
i tried to configure an VLAN interface on my SF280 based on the documentation on docs.sun.com
# ifconfig eri1000 plumb up
Oct 21 13:41:26 cmsmaster ip: ip_rput_dlpi(eri1000): DL_ERROR_ACK for DL_ATTACH_REQ(11), errno 8, unix 0
ifconfig: SIOCSLIFNAME for ip: eri1000: no such interface... (2 Replies)
Hi all,
so server: FreeBSD 7.0 release,
interfaces on it DLINK DGE-528T with support of vlans :))
so first interface looks to LAN second to ISP.
I created vlan1 with id 1 and gave to it ip address and plug it in
tagged port of swith for vlan 1. so client from vlan1 reaches the server.
it... (2 Replies)
Hi all
My application is a monitoring application that monitors the incoming udp packet when ever required. When ever a particular source ip and port and dest ip and port is provided the filter will be framed based them. For eg,
char filterExpr;
filterExpr = "udp and src host 192.168.16.100... (0 Replies)
Hello. I want to Communicate 2 VLAN with router like this solution:
http://8pic.ir/images/83m0ouih8mmm9s1sfl56.jpg
For this purpose I'm configuring 2 Linux system as a switch and connect 4 host to them. Then a router is added to scenario.
The configuration of the switches is:
On DUT1(Linux):... (1 Reply)
Hi,
Is it possible to VLAN tag with a ce interface on Solaris 9? Link speed is gb.
ce:0:ce0:link_speed 1000
I have a ce0 interface I would need to have access to another VLAN as well as the one it's currently on.
What commands would I need to run?
Thanks.;) (2 Replies)
We have two hosts in same vlan with same route rules.
One of them is not able to connect to an outside IP while in another I get "failed: Connection timed out" while testing the connectivity through netcat.
I have tried mtr /traceroute and it gives me the same results.
Is there a netcat... (1 Reply)
Have 2 nics on physical system
net0 phys 1500 up --
net1 phys 1500 up --
1. I want to create a link aggregation with LACP enabled with above 2 nics
2. Create port-group(Like we create on ESXi) with VLAN-ID 2141
3. And assign this... (0 Replies)
Hi Guys,
Our lpars is currently running on 2 different vlans (20, 30). Now we have a requirement that vlan 30 needs to be change to vlan 31 at the same subnet. I'm not sure on what is the best approach for this or what change is involve on the AIX side.
This is our setup.
Network switch -... (5 Replies)
Hi Folks,
I am currently moving systems to a new environment, with some changes to the network requirements on the systems.
One of these changes is moving from just standard IPMP to using IPMP on top of a VLAN, I have used VLAN tagging befor without issue - however not with IPMP.
What I... (2 Replies)
Discussion started by: gull04
2 Replies
LEARN ABOUT DEBIAN
fipvlan
FIPVLAN(8) Open-FCoE Tools FIPVLAN(8)NAME
fipvlan - Fibre Channel over Ethernet VLAN Discovery
SYNOPSIS
fipvlan [-c|--create] [-s|--start] interfaces
fipvlan -a|--auto [-c|--create] [-d|--debug] [-s|--start] [-l|--link-retry <num>]
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 to be not enabled by the time the program runs. 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
-f, --suffix <suffix string>
Append the specified string <suffix string> to VLAN interface names.
-l, --link-retry <number of retries>
Retry check for link up up to <number of retries> times. The link state is retried every 500 ms. The default is 20.
-h, --help
Display a help message with basic usage instructions
-v, --version
Display the fipvlan version string
VLAN NAMING CONVENTIONS
The default VLAN device name is dev.vlan; where dev is the name of the Ethernet parent device and vlan is the discovered VLAN ID number. An
optional suffix can be appended to this with -f commandline 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-fcoe 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 10/06/2011 FIPVLAN(8)