entstat (under AIX)
use "entstat -r en#" to reset the stats, then just use the "entstat en#" to
get current stats...
root@tsmsrv03/ > entstat en2 | more
-------------------------------------------------------------
ETHERNET STATISTICS (en2) :
Device Type: Gigabit Ethernet-SX PCI Adapter (14100401)
Hardware Address: 00:02:55:9a:22:b4
Elapsed Time: 21 days 19 hours 7 minutes 54 seconds
Transmit Statistics: Receive Statistics:
-------------------- -------------------
Packets: 954537493 Packets: 4177836998
Bytes: 848272877985 Bytes: 5717486542176
Interrupts: 3284008 Interrupts: 431961324
Transmit Errors: 0 Receive Errors: 0
Packets Dropped: 0 Packets Dropped: 16
Bad Packets: 0
<stuff deleted>
root@tsmsrv03/ > entstat en0 | more
-------------------------------------------------------------
ETHERNET STATISTICS (en0) :
Device Type: IBM 10/100 Mbps Ethernet PCI Adapter (23100020)
Hardware Address: 00:20:35:12:1a:af
Elapsed Time: 46 days 22 hours 7 minutes 45 seconds
Transmit Statistics: Receive Statistics:
-------------------- -------------------
Packets: 6419303284 Packets: 15409604134
Bytes: 2076400039013 Bytes: 18539862880185
Interrupts: 16428549 Interrupts: 14105675593
Transmit Errors: 789 Receive Errors: 0
Packets Dropped: 0 Packets Dropped: 0
Bad Packets: 0
<stuff deleted>
-----Original Message-----
From: Jeff Bach [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 9:27 AM
To: [EMAIL PROTECTED]
Subject: Re: One server, two ip-addresses
What measurement tools do you use to determine this throughput number?
Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.
WAL-MART CONFIDENTIAL
-----Original Message-----
From: Cook, Dwight E (SAIC) [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 8:20 AM
To: [EMAIL PROTECTED]
Subject: Re: One server, two ip-addresses
We have one that uses three (3).
Two fast ethernet & one GB.
You have to remember that your standard TCP/IP routing is what
determines
how these boxes talk !
Client traffic will go in which ever interface you point to and will
return
out to the client based on standard routing in the system (but will
go back
to the ip in the received packets).
Back when we built our environments "SAN" wasn't really around so we
built a
sudo-SAN. Works great !
Our busiest S70 TSM server (just 2 processors & 1 GB memory) seems
to max
out at about 60-ish GB/hr of inbound compressed client data
(actually kind
of hard to find enough clients to push more than that ;-) but I need
to
check recent #'s )
(so during DB backups, that is about 240 GB/hr of client
file spaces
being backed up)
Is this good or bad ? ? ?
It is just what we see and it serves our needs !
Dwight
-----Original Message-----
From: Wouter V [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 6:49 AM
To: [EMAIL PROTECTED]
Subject: One server, two ip-addresses
Hello,
Does anybody know if a single TSM server can listen on different
ip-adresses
(on different nic's) ? Or do you need to run multiple instances on
one
machine ?
TSM Server Config example :
Listening for backup data on NIC1 : 192.168.10.10:1500
and on NIC2 : 10.10.10.10:1500
+ other nic for normal lan traffic
Just wondering if adding extra LAN cards in every client to increase
the
total bandwith, is a
cheap alternative for SAN environments.
For example : client config with 3 NIC's :
NIC1 : regular client traffic
NIC2 : for online database backup
(scheduler
1) (backup lan 1)
NIC3 : for backup of regular file
(scheduler
2) (backup lan 2)
2 x 100 Mbit bandwith to backup
Any remarks about this ? I agree, it isn't a good alternative, but
I was
just wondering if this is possible ?
Thanks !
Wouter Verschaeve
**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed. If you have received this email
in error destroy it immediately.
**********************************************************************
