Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have a CSS (WebNS 8.20.5.01) in front of an Apache server which is the front end to Oracle Fusion SOA.When a web browser connects directly to the Apache server using HTTP on port 41778, and submits a POST for a transaction, the client receves a 200...
In older versions of the NAM software and CATOS, it was possible to collect statistics on an individual layer 2 switch port, so that one could see utilization of that particular link over time.I cannot find a way to do that after my upgrade to Sup720...
I know that it's possible on the CSS to handle multiple incoming HTTP requests that terminate on the same IP address and port and balance them to various servers based on the url. For instance, I can set up www.cats.com and www.dogs.com at the same...
I've got several sites with IPSEC tunnels built between PIX firewalls to encrypt/sign the traffic moving between the "inside" networks on those firewalls. These sites use identity nat where every inside address is directly natted to the same address...
I've got a CSS 11506 and am supposed to be planning the refresh of this device in the future to something that will support IPv6 and do everything the CSS does.I'd originally planned for the ACE module, but I now see there is a Content Switching Modu...
We took the captures (using our NAM) because when we run a scenario where we put SSL in the front of it (Browser-HTTPS-CSS-HTTP-Apache) we do get an error message back, and in that case we get the "extra" POST twice.I am sure of what I saw because it...
I notice that you don't appear to specify a specific uri for your HTTP head requests to the servers.This can sometimes cause issues if your web server doesn't have a default web page set. The CSS when it makes keepalive http request is looking for...
Sorry, you still don't understand that there is no DEVICE at 10.164.2.100. The actual DEVICE is on the "outside" network and it's NATed to the inside network.More explicitly, the "inside" and "outside" networks here refer to the security levels of t...
We don't control the router, so the configuration is sort of stuck as it is.I was hoping that since the 10.164.2.100 is not a physical device, but a NAT of the actual server we are trying to reach, that the tunnel would work.The connection flow would...
