I am setting up a basic service on my CSS but it is showing as DOWN even though I can reach it fine directly and from the CSS.
I'd appreciate any hints on why. I am running sg0810106 (08.10.1.06) on a CSS 11501. Other services on the same backend subnet are working fine.
Here is the service definition and status:
CSS11501# sh run service vmi-82-100-8000
!************************** SERVICE ************************** service vmi-82-100-8000 ip address 10.10.82.100 protocol tcp port 8000 keepalive type tcp keepalive port 8000 active
CSS11501# sh service vmi-82-100-8000
Name: vmi-82-100-8000 Index: 37 Type: Local State: Down Rule ( 10.10.82.100 TCP 8000 ) Session Redundancy: Disabled Redirect Domain: Redirect String: Keepalive: (TCP-8000 5 3 5 ) Keepalive Encryption: Disabled Last Clearing of Stats Counters: 10/21/2010 07:24:59 Mtu: 1500 State Transitions: 0 Total Local Connections: 0 Total Backup Connections: 0 Current Local Connections: 0 Current Backup Connections: 0 Total Connections: 0 Max Connections: 65534 Total Reused Conns: 0 Weight: 1 Load: 255 Weight Reporting: None
Debugging in the CSS seems to indcate the service should be up:
CSS11501(debug)# icp probe service vmi-82-100-8000 Probing 10.10.82.100:8000(-) KeepAlive probe.. IP Address: 10.10.82.100 Port: 8000 URL: / HTTP Version: 1.1 Server Model: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h Server Date: Thu, 21 Oct 2010 16:11:37 GMT HEAD Response: 404 Not Found HEAD Support: Yes Persistence: Yes Keep-Alive: Yes Request Depth: 100 TBR: 5 Connect Time: 1 ms Rqst/Rsp Time: 4 ms Pipeline: No SSL: No
CSS11501(debug)# icp probe host 10.10.82.100 Probing 10.10.82.100:80(-) KeepAlive probe.. IP Address: 10.10.82.100 Port: 80 URL: / HTTP Version: 1.1 Server Model: Apache/2.2.3 (Unix) mod_ssl/2.2.3 OpenSSL/0.9.8h Server Date: Thu, 21 Oct 2010 16:12:34 GMT HEAD Response: 403 Forbidden HEAD Support: Yes Persistence: Yes Keep-Alive: Yes Request Depth: 100 TBR: 5 Connect Time: 1 ms Rqst/Rsp Time: 13 ms Pipeline: No SSL: No
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...