David J. Hughes wrote: > > On 12/11/2004, at 11:01 AM, David J. Hughes wrote: > >> Wow! I've seen some "odd" things on the SI's but that one just about >> takes the cake. Logic, useability, and firmware development >> strategies are obviously mutually exclusive :) > > > It's not every day I reply to my own posts ;-) > > But, on this "well known tcp port" business, I just remembered that when > we did our initial testing of using master-port configuration we did it > using dummy SMTP servers running on port 26 - and it worked just fine. > Now, TCP 26 doesn't appear to be too well known to me. That was on a > pair of SI-100's running WSR08100m. Might be worth actually trying it > before discarding the idea.
I think the "well-known" stuff is bullshit, they just didn't implement it for UDP for reasons unbeknownst (doesn't appear in the tab completion list of "udp keepalive", typing it in manually results in "Invalid input"). best regards, michael From [EMAIL PROTECTED] Fri Nov 12 12:23:51 2004 From: [EMAIL PROTECTED] (Cliff Fogle) Date: Fri Nov 12 12:24:04 2004 Subject: [f-nsp] dns keepalive checks on "unknown" ports Message-ID: <[EMAIL PROTECTED]> Have you first tried the following from the "server port 153" config, thereby setting 153 to be udp protocol dns?: [EMAIL PROTECTED](config-port-153)#udp keepalive DECIMAL Number protocol protocol used for keepalive [EMAIL PROTECTED](config-port-153)#udp keepalive proto dns [EMAIL PROTECTED](config-port-153)#udp keepalive proto dns -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Renner Sent: Thursday, November 11, 2004 10:49 AM To: [email protected] Subject: [f-nsp] dns keepalive checks on "unknown" ports Hi, I currently have a "Many-to-one" setup [1] on a Foundry ServerIron XL running 07.4.00T12, with 2 virtual servers pointing to 3 real servers, but I'm not able to enable keepalive on the "aliased" port as suggested in the documentation [2]. [EMAIL PROTECTED](config-rs-www1)#port 153 addr_query "www.domain.com" Invalid command, zone only applies to DNS port, not 153 Is this intended behaviour for alias ports when not using HTTP (since HTTP is IIRC the only protocol which supports Virtualhosts)? Currently the foundry seems to do dns checks on the "real" and the "aliased" port using the configured hostname (i see 2 queries every 3 seconds, opposed to 1 query every 3 seconds, when no alias port is used), deactivating both ports when the dns server is down. [1] http://www.foundrynet.com/services/documentation/siug/ServerIron_Server_Load_Balancing.html#22178 [2] http://www.foundrynet.com/services/documentation/siug/ServerIron_health_checks.html#53798 Current setup looks something like that: --- server port 53 udp keepalive 3 2 server port 153 udp keepalive 3 2 udp keepalive protocol 53 server real www1 1.1.1.1 port 153 port 153 keepalive port dns port dns keepalive port dns addr_query "www.domain.com" [repeat for www2 and www3] server virtual a.ns.domain.com 1.2.1.1 port dns bind dns www1 dns www2 dns www3 dns server virtual b.ns.domain.com 1.3.1.1 port dns no port dns translate bind dns www1 153 www2 153 www3 153 --- -- best regards, Michael Renner - Network services Preisvergleich Internet Services AG Obere Donaustra?e 63/2, A-1020 Wien Tel: +43 1 5811609 80 Fax: +43 1 5811609 55 _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
