02-16-2017
Thank you. That could be a good explanation, however, did you mean the reverse:
i.e
seastat counts only packets going in/out physical interface
while
entstat counts all packets, even those forwarded internally?
Because I see entstat values are higher than seastat values.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Gurus!
I recently got my shell account (HP UX v11) created by our sysadmin and am having problem deleting with the backspace key.
After doing some reading, I believe I need to enter a custom "STTY..." statement in my profile.
Can someone please help me with the correct "STTY" sequence... (3 Replies)
Discussion started by: alan
3 Replies
2. AIX
I am trying to create a SEA on a LHEA port and it gives me error
lsdev -Cc adapter:
ent0 logical host ethernet port (l-hea)
ent1 virtual I/O ethernet adapter
mkvdev -sea ent0 -vadapter ent1 -default ent1 -defaultid 199
method error (/usr/lib/methods/cfgsea):
Failed to configure SEA... (0 Replies)
Discussion started by: filosophizer
0 Replies
3. AIX
Hello All, at our client VIOS Server there is shared ethernet adapter ent6,
when I run lsattr -El ent6 the output shows real adapter ent1 lsattr -El ent6
accounting disabled Enable per-client accounting of network statistics True
ctl_chan ent5 Control Channel... (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies
4. AIX
Hi Guys,
I'm getting the below error while trying to create a SEA adapter in VIOS
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1
... (4 Replies)
Discussion started by: kkeng808
4 Replies
5. AIX
Hi all,
I set up the following configuration on my system:
- An LPar with a virtual adapter, first one with a vlan id=703 and id port=13.
- The first adapter have to connect to a VIOS in which i configured an SEA.
So, the VA is set up on interface ent2, SEA on ent29 (by linking a... (0 Replies)
Discussion started by: idro
0 Replies
6. AIX
Why are the MAC addresses duplicated in the "seastat" command output for all the LPARs? I can't figure out why one stanza has the LPAR information (hostname and IP) while the other stanza does not? Why the two separate sections and two separate sets of usage information (Bytes and Packets)?... (1 Reply)
Discussion started by: kah00na
1 Replies
7. AIX
Hi all,
We are receiving huge number of "Receive Errors" on our database server on AIX. Any pointers to troubleshoot would be really appreciated.
oslevel:
AIX 5.3.0.0
ifconfig -a
en6: flags=4e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,PSEG,LARGESEND,CHAIN>
... (3 Replies)
Discussion started by: sam_78_nyc
3 Replies
8. AIX
Hi experts, i got a 4-port Adapter card on VIOS and would like to configure 4SEA for 4 difference segment IP client's LPAR use, first SEA succeed to be configured on ent0 but once second SEA configured, first SEA fail to be connected. Any issues i need to be concerned in order to configure 4 SEA on... (8 Replies)
Discussion started by: polar
8 Replies
9. AIX
I am trying to install a VIOS pair with a load-sharing SEA adapter, following this recipe from Developerworks. Without load-sharing everything went fine and worked as expected, but somehow i am a bit lost and the first tries with "ha_mode=sharing" didn't work at all.
Here is the situation:
I... (6 Replies)
Discussion started by: bakunin
6 Replies
10. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
LEARN ABOUT NETBSD
bridge
BRIDGE(4) BSD Kernel Interfaces Manual BRIDGE(4)
NAME
bridge -- network bridge device
SYNOPSIS
pseudo-device bridge
DESCRIPTION
The bridge driver creates a logical link between two or more IEEE 802 networks that use the same (or ``similar enough'') framing format. For
example, it is possible to bridge Ethernet and 802.11 networks together, but it is not possible to bridge Ethernet and Token Ring together.
To use bridge, the administrator must first create the interface and configure the bridge parameters. The bridge is created using the
ifconfig(8) create subcommand. The learning and forwarding behavior and other parameters of a bridge are configured by the brconfig(8) util-
ity.
A bridge can be used to provide several services, such as a simple 802.11-to-Ethernet bridge for wireless hosts, and traffic isolation.
A bridge works like a switch, forwarding traffic from one interface to another. Multicast and broadcast packets are always forwarded to all
interfaces that are part of the bridge. For unicast traffic, the bridge learns which MAC addresses are associated with which interfaces and
will forward the traffic selectively.
The bridge driver implements the IEEE 802.1D Spanning Tree protocol (STP). Spanning Tree is used to detect and remove loops in a network
topology.
Transparent filtering for IP and IPv6 packets can be added with the kernel configuration option options BRIDGE_IPF.
When filtering is enabled, bridged packets will pass through the filter inbound on the originating interface and outbound on the appropriate
interfaces. ARP and REVARP packets are forwarded without being filtered and others that are not IP nor IPv6 packets are not forwarded when
filtering is enabled.
Note that packets to and from the bridging host will be seen by the filter on the interface with the appropriate address configured as well
as on the interface on which the packet arrives or departs.
SEE ALSO
etherip(4), options(4), brconfig(8), ipf(8)
HISTORY
The bridge driver first appeared in NetBSD 1.6.
AUTHORS
The bridge driver was originally written by Jason L. Wright <jason@thought.net> as part of an undergraduate independent study at the Univer-
sity of North Carolina at Greensboro.
This version of the bridge driver has been heavily modified from the original version by Jason R. Thorpe <thorpej@wasabisystems.com>.
BUGS
The bridge driver currently supports only Ethernet and Ethernet-like (e.g. 802.11) network devices, with exactly the same interface MTU size
as the bridge device.
The bridge driver currently does not support snooping via bpf(4).
BSD
January 9, 2010 BSD