[f-nsp] serveriron http on ports other than 80

[Kim Wall]

Yes, a maintenance contract is required to gain access to the code
download pages. You would normally purchase through a local sales team.
If you need assistance in locating a local SE, the following may be
useful:

Contact:
Technical Support Center
408-586-1881
1-877-TURBOCALL (1-877-887-2622)
support at foundrynet.com 

Also: from the web
http://www.foundrynet.com/services/support/index.html

Warranty customers may access Foundry's Technical Support section for up
to 90 days after shipment of your system. To obtain access to Foundry's
on-line service and support for the 90-day Software Warranty period,
please:

Locate the Part Number on your Foundry product:
Example: B15000


Locate the Serial Number label on the back of your Foundry product.
Example: F12345


Your User name = Part Number + Serial Number with no spaces
Example: B15000F12345


Your Password = Part Number
Example: B15000


Click on the Log In button below


Enter in the User name and Password which you determined above.


Click "OK" to log in.


Regards,

Kim

-----Original Message-----
From: foundry-nsp-bounces at puck.nether.net
[mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of
burnside at kattare.com
Sent: Friday, December 20, 2002 7:35 AM
To: Will Lowe
Cc: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] serveriron http on ports other than 80

Will,

    I appreciate the assistance.  After much reading and fandangling
with it I realized that the version of the OS I have is not the version
the docs on the site are for, and does not allow the protocol argument
when working with the given port.  This leaves me in a bit of a bind, as
I have all kinds of weird ports that I need to support.  (smtp on port
2525, pop3 on port 995, http on port 10000, etc.)

    To add to the confusion... I started off using the web based admin,
thinking it'd be an easier way to jump in and learn the concepts.  Turns
out that the SLB port management is broken in the web interface.  If you
manually add a port it automatically assumes it's an HTTP port and sets
it up to do the default "HEAD /" checks.  Cripes.  It took me quite a
while to figure out why the checks were failing.  There's no way to fix
it from the web interface.  Thank goodness the CLI is similar to IOS and
fixing it up wasn't too difficult.

    How does one go about getting the latest version of the OS?  I poked
around on their site briefly but could not find any downloads.  Are they
setup like Cisco where you have to get a service contract and pay for
bugfixes, security patches, and functionality that should have been
there in the first place?  ;-)

Cheers,

~Ethan B.



Quoting Will Lowe <harpo at thebackrow.net>:

> >     I've tried configuring TCP health checks on the high ports
> (10000,
> > 10010, etc.) via the TCP/UDP port config and it seems to fail the
> health
> > checks  on the real server every time.  (and thus serves nothing.) 
> If I
> > connect directly to the servers on the high ports I get the pages I
> expect.
> 
> You need something like:
> 
> server port 10000
> 	tcp keepalive protocol http
> 
> to force it to do http health-checks on a non-port-80 service.
> Foundry's docs are kinda confusing, but the relevant part of the
> manual is at 
> 
>
http://www.foundrynet.com/services/documentation/siug/ServerIron_health_
checks.html#41255
> 



--------------------------
Ethan Burnside - Founder
Kattare Internet Services
http://www.kattare.com
--------------------------

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.427 / Virus Database: 240 - Release Date: 12/6/2002
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.427 / Virus Database: 240 - Release Date: 12/6/2002