06-07-2011
Quote:
Originally Posted by
DGPickett
Network link saturation is usually 2-3 big file transfers, unless the disk is slower (first cat the file to dev null to get it in cache?).
I see...those will have to be really large files(?) to saturate these GigE links?
Quote:
It seems like the load balancing originally set up was linked to the old IP addresses, and you need to redo whatever that was.
The weird thing is that this machine has moved 2-3 times already and have had to change IPs on it every single time and the last time I did it, everything went smooth and was a non-issue. This time, I did the same thing but am faced with this issue and I don't remember doing anything special. I just assumed that when the interfaces are connected to the network directly, they pass traffic directly
You're right, this DOES look relevant. Unfortunately this is a restricted version of Solaris delivered by the vendor of this appliance and does not have
svcadm or
routeadm as commands. Maybe I'll have to see if I can find them on the net somewhere but finding anything for Solaris-8 is becoming harder and harder.
So now I have to figure out how to do what this article says without the svcadm or routeadm commands. I know there's a file that stores the ip forwarding info etc. Can't remember which one, also
ndd might help?
10 More Discussions You Might Find Interesting
1. IP Networking
Hi,
I have problems with my SCO unix network interfaces.
Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot.
Installed driver using SCO Software manager - successfully
Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies
2. SCO
Hi,
I have problems with my SCO unix network interfaces.
Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot.
Installed driver using SCO Software manager - successfully
Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies
3. UNIX for Dummies Questions & Answers
How do I find out what the primary network interface is on an AIX system..
Found commands to display information on the various interfaces but nothing that guides me to how to tell which one is the primary network interface.
Thanks,
~D (1 Reply)
Discussion started by: djlerman
1 Replies
4. AIX
Hi all, this is my first post on this forum. My main problem is this:
I have a NIM server that I am trying to configure two interfaces on. One interface is for an internal Admin VLAN, the other is so that the server can use SUMA to pull updates. The problem is that I need help w/ the routing.... (0 Replies)
Discussion started by: snakernetb
0 Replies
5. AIX
Hi all, this is my first post on this forum. My main problem is this:
I have a NIM server that I am trying to configure two interfaces on. One interface is for an internal Admin VLAN, the other is so that the server can use SUMA to pull updates. The problem is that I need help w/ the routing.... (1 Reply)
Discussion started by: snakernetb
1 Replies
6. Shell Programming and Scripting
Hi All,
OS:AIX 5.3 L
My shell script using ssh remains connected at primary site and ssh doesn't get disconnected.What should be typed and where in the shell script below to do it.
Shell script
========
#!/usr/bin/ksh
v_standby=`sqlplus -s /nolog <<END
@standby.sql
END`
echo... (5 Replies)
Discussion started by: a1_win
5 Replies
7. Solaris
I got second IOU in my M5000 but not able bring internal network interfcae .. ike i don't get link on those 2 interfaces .. and the same network cable plugged in PCI network card it works like a charm Is there any special way to enable the internal IOU interfaces or i have bad nics ? (8 Replies)
Discussion started by: fugitive
8 Replies
8. Debian
Hello
i am configuring a debian lenny sever ,/etc/network/interfaces is modified so that eth1 takes a static IP address
then i save it wq!
then i restart the networking , /etc/init.d/networking restart .
but after reboot ,the file is reset ,note that the interfaces had by defauklt IPv6 address... (5 Replies)
Discussion started by: learn82
5 Replies
9. UNIX for Dummies Questions & Answers
i need a one liner command that writes in /var/log/net.log the date when i connect to the network and when i disconect ..i know that i need to write somethin in /etc/network/interfaces but idk what ! please help (1 Reply)
Discussion started by: g0dlik3
1 Replies
10. AIX
Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket.
Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B.
Box B has two network interfaces, X and Y. Interface X has the... (4 Replies)
Discussion started by: RonBowater
4 Replies
LEARN ABOUT OPENSOLARIS
quagga
quagga(8) System Administration Commands quagga(8)
NAME
quagga - advanced routing protocol suite from www.quagga.net
SYNOPSIS
Quagga is an advanced routing software package that provides a suite of TCP/IP based routing protocols.
Quagga supports protocols such as RIPv1, RIPv2, RIPng, OSPFv2, OSPFv3, BGP-4, and BGP-4+. This document is provided for informational pur-
poses to help users configure quagga under Solaris specifically. Further documentation on quagga configuration in general is provided at
http://www.quagga.net.
DESCRIPTION
Quagga consists of the following packages:
o SUNWquaggar - Quagga root files
o SUNWquagga-daemons - Quagga daemons
o SUNWquagga-libs - Quagga private shared libraries
o SUNWquagga-dev - Quagga private shared library headers
o SUNWquaggaS - Quagga sources
More defailed Quagga documentation is available from http://www.quagga.net/docs, or in the GNU Info format Quagga documentation installed
in /usr/sfw/share/info.
The Quagga routing protocol suite replaces SUNWzebra, and detection of SUNWzebra configuration during boot will lead to automatic transfer
of configuration to quagga. If manual upgrade (without reboot) is required, configuration files under /etc/sfw/zebra should be transferred
to /etc/quagga, and "routeadm -u" should be run. This will enable the appropriate quagga services, and run the daemons if those services
dependencies are met.
In Solaris, quagga daemons are managed by the following smf(5) services:
svc:/network/routing/zebra:quagga zebra routing manager daemon
svc:/network/routing/rip:quagga RIPv2 routing daemon
svc:/network/routing/ripng:quagga RIPng routing daemon
svc:/network/routing/bgp:quagga BGP routing daemon
svc:/network/routing/ospf:quagga OSPF routing daemon
svc:/network/routing/ospf6:quagga OSPF6 routing daemon
Quagga daemons can be configured either via the smf(5) framework, or via routeadm(1M), the global dynamic routing management utility.
Note that quagga was built without the vtysh (unified vty shell) utility, as it depends on a package not currently distributed with
Solaris.
COMMANDS
By default, in.routed and in.ripngd, managed by the svc:/network/routing/route and svc:/network/routing/ripng services respectively, are
configured as default IPv4/IPv6 routing services. To disable these, either utilize routeadm(1M) or svcadm(1M) as follows:
# routeadm -d route
# routeadm -d ripng:default
disables in.routed and in.ripngd respectively using routeadm(1M).
# svcadm disable route:default
# svcadm disable ripng:default
disables in.routed and in.ripngd respectively using smf(1).
Note that these services must be disabled or their quagga counterparts (rip:quagga, ripng:quagga) will not run, since they services specify
to the smf framework that they and their quagga counterparts cannot run simultaneously.
To enable quagga services, again either routeadm(1M) or svcadm(1M) can be used. Note that quagga services, like in.routed and in.ripngd,
specify dependencies on ipv4(6)-routing(forwarding) services, so as with all smf(1) services, ensure the appropriate dependencies are
enabled or the services will not start.
For example,
# routeadm -e rip:quagga
# routeadm -e ipv4-routing -u
enables quagga's RIPv2 daemon (the -u option above is required, as global ip routing/forwarding settings are not applied to the system
until next reboot unless the -u is issued).
To do the same via smf(1),
# svcadm enable -r rip:quagga
The "-r" option recursively enables rip:quagga's dependencies, which include the ipv4-routing service.
The status of all routing daemon services can be displayed via routeadm(1M), run without options, or, through smf(1), via the svcs(1) com-
mand.
Commandline arguments to the quagga daemons can be altered by modifying the routing/daemon-args property, again either via routeadm(1M) or
svccfg(1M):
# routeadm -m rip:quagga daemon-args="-s"
or
# svccfg -s rip:quagga setprop routing/daemon-args="-s"
# svcadm refresh rip:quagga
The "refresh" is required to ensure the daemon re-reads its configuration.
DIAGNOSTICS
To see status of all routing services, run routeadm(1M) without options.
SEE ALSO
ripngd(8), ospfd(8), ospf6d(8), bgpd(8), zebra(8), routeadm(1M), svcadm(1M), svcs(1), svccfg(1M), smf(5)
AUTHORS
See <http://www.quagga.net>, or the Info file for an accurate list of authors.
SunOS 5.11 01 Aug 2006 quagga(8)