02-16-2017
sorry, i missed that you clear the stats.
so it looks like you have lpar to lpar traffic which does not go through physical network switch. PowerVM is forwarding traffic internally, so seastat counts the packets, however entstat will not count them since they do not actually go over physical interface.
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 OPENSOLARIS
ipfirewall
IPFW(4) BSD Kernel Interfaces Manual IPFW(4)
NAME
ipfw -- IP packet filter and traffic accounting
SYNOPSIS
To compile ipfw into the kernel, place the following option in the kernel configuration file:
options IPFIREWALL
Other kernel options related to ipfw which may also be useful are:
options IPFIREWALL_DEFAULT_TO_ACCEPT
options IPFIREWALL_FORWARD
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=100
To load ipfw as a module at boot time, add the following line into the loader.conf(5) file:
ipfw_load="YES"
DESCRIPTION
The ipfw system facility allows filtering, redirecting, and other operations on IP packets travelling through network interfaces.
The default behavior of ipfw is to block all incoming and outgoing traffic. This behavior can be modified, to allow all traffic through the
ipfw firewall by default, by enabling the IPFIREWALL_DEFAULT_TO_ACCEPT kernel option. This option may be useful when configuring ipfw for
the first time. If the default ipfw behavior is to allow everything, it is easier to cope with firewall-tuning mistakes which may acciden-
tally block all traffic.
To enable logging of packets passing through ipfw, enable the IPFIREWALL_VERBOSE kernel option. The IPFIREWALL_VERBOSE_LIMIT option will
prevent syslogd(8) from flooding system logs or causing local Denial of Service. This option may be set to the number of packets which will
be logged on a per-entry basis before the entry is rate-limited.
Policy routing and transparent forwarding features of ipfw can be enabled by IPFIREWALL_FORWARD kernel option.
The user interface for ipfw is implemented by the ipfw(8) utility, so please refer to the ipfw(8) manpage for a complete description of the
ipfw capabilities and how to use it.
SEE ALSO
setsockopt(2), divert(4), ip(4), ipfw(8), sysctl(8), syslogd(8), pfil(9)
BSD September 1, 2006 BSD