Hi Jamie, For the TCS issue.
I think you don't configure an ip on the serveriron so it will not be able to reach the caches for health checks so it will mark it down and it will not forward the requests to it. I think you need to give the serveriron an ip and try to ping from it on the cache servers. If no, please send me the outputs for # show cache-group Best Regards, Ahmed Rezk -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, February 23, 2009 7:00 PM To: [email protected] Subject: foundry-nsp Digest, Vol 73, Issue 18 Send foundry-nsp mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://puck.nether.net/mailman/listinfo/foundry-nsp or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of foundry-nsp digest..." Today's Topics: 1. Transparent cache problem (Jamie Orzechowski) 2. NSSA areas and default-information-originate (Clement Cavadore) ---------------------------------------------------------------------- Message: 1 Date: Sun, 22 Feb 2009 20:29:13 -0500 From: Jamie Orzechowski <[email protected]> Subject: [f-nsp] Transparent cache problem To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain;charset=ISO-8859-1;format=flowed Foundry I have installed a Foundry ServerIron XL in front of my caches. The problem is that I do not see any traffic going towards my caches and nothing on tcpdump. If I manually force the proxy it works fine. Any ideas why traffic is not being directed towards the cache? ... Here is my Config. I am directly connected to port 9 for testing. 10 is connected to my router server cache-name cacheA 66.78.96.10 port http port http url "HEAD /" server cache-group 1 cache-name cacheA server cache-router-offload ip policy 1 cache tcp http local interface e 1 port-name "Squid eth0" cache-group 1 interface e 9 port-name Workstation no cache-group interface e 10 port-name "To Router" no cache-group ip-policy 1 ------------------------------ Message: 2 Date: Mon, 23 Feb 2009 12:40:51 +0100 From: Clement Cavadore <[email protected]> Subject: [f-nsp] NSSA areas and default-information-originate To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-15 Hi, I have two areas in my network: 0.0.0.0 (backbone area) and 100 (NSSA area, in which I have two 3750 through which I don't want any backbone traffic in). On one side of the area, I have a Jetcore bigiron (SW ver: 08.0.01oT53), and on the other side, I have a Cisco 7k6. I don't want to set up static routes on the 3750 for the default gateway of this LAN, I'd really prefer to receive it through IGP. On cisco side, I can inject the default gw to the NSSA area, but the jetcore does not inject it on the NSSA area. Here is my config (on the Jetcore) router ospf (...) area 100 nssa 100 area 100 nssa default-information-originate (...) interface x/y (...) ip ospf area 100 (...) ! With that config, the OSPF adjency is correct between the 3750 and the Jetcore. But no default gateway... Did I miss out something ? Thanks, -- Cl?ment Cavadore ------------------------------ _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp End of foundry-nsp Digest, Vol 73, Issue 18 ******************************************* _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
