Gre: Number of the GRE interface that we should receive data from this router (gre0, gre1.)īind: Address that we are binding our socket to, to send packets to this router (Our from / source address) Rtr: Router information for this nexus - duplicated for nexii on the same routerįd: File descriptor of the socket to send packets to this router ReceiveID: Receive ID increments on each successful ISY. Outst_HIA: Number of HIAs we have sent, but not received an ISY to. : WCCP negotiation is complete and WSA + router agree on capabilitues wccp: STATE: rstate=0, outst_HIA=0, receiveID=0 : WCCP negotiation is complete and WCCP is 'Active' : Agreed upon forwarding redirection method (L2 / GRE) : Router Not responding / haven't used it yet Rtr_changer#: Number of times the router believes the view has changed ISY: Last saw an ISY from this router in this service group (nexus router) Rtr_mention: Router last mentioned itself Sent_key: Our address + key_chg number when we were the DWC wccp: STATE: rtr_change#= 0 refs=0 Recvd_key: Address of the DWC that sent the RA, the keychg number the DWC sent (incremental) Nexus: For each service, for each router, there is one nexus (Can be thought as a virtual basket where data is kept) When using web-cache the ports are left blank, but port 80 will be redirected. Ports: Ports to be redirected to the web cache (WC). Proto: Protocol this service is asking to redirect. ISY: "I See You (ISY)" packets we've received HIA: "Here I Am (HIA)" packets we've sent This period: In the last 10 seconds (standard tick), how many: Keychg: Number of times we have generated a different hash / mask table to send out wccp: STATE: this period:( HIAs=0, ISYs=0) proto=6 Viewused: The last change number that we notified the router of. Viewchg: The number of times this service has had any change (routers join / leave, wc added / removed, so forth) (If this value were 115, the RA would be sent in 15 The timestamp of the last received "I See You (ISY)" for this service. The timestamp scheduled to send the RA in the future.Only the DWC sends RAs - at this point we don't know if we are the DWC).If 1 = Something in this service view has changed. Wccp: STATE: viewchg=0, viewused=0, keychg=0 Hashing / masking is based on the client address Hashing / masking is based on the server address Redirection is based on destination port Designated Web Cache (DWC) is unknown at this time GRE / L2 return method negotion is complete GRE for return redirection method is allowed L2 for return redirection method is allowed Return redirection method is undetermined at this time (L2 vs. Masking / hashing negotiation is complete Load balancing method is undetermined at this time (hashing vs. ID: Service ID number (0 - 255) wccp: STATE: 1 = Standard IDĬurrently web-cache (service ID 0) is the only existing pre-defined ID Type: 0 = Pre-defined ID (such as web-cache). Index: Position of this service in the list of all configured services on the WSA - Starts at 0 and increments +1 The exact example below is from a real scenario. The following below is an explanation of the possible values you can find in the WCCP trace logging level. Nexus : Nexus data - For each service, for each router, there is one nexus (Can be thought as a virtual basket where data is kept) The logs can be broken into a few different areas (separated by space indentation) after the CONFIG is printed: Information seen in logs at the configured log levelĮrrors, CONFIG, INFO, STATE, CHANGE (state changes) The logging levels will show the following data: 7.1 log level (CLI) On AsyncOS version 7.5 and above: The logging level for WCCP logs and/or proxy logs can be changed in GUI under "System Administration > Log Subscriptions > " In AsyncOS version 7.1 and below: The WCCP logging level can be changed by entering the following CLI command: wsa01> advancedproxyconfigĮnter values for the various "wccp" options: In AsynOS version 7.5 and above: WCCP messages is seen in WCCP logs along with the proxy logs.Ĭheck your "Log Subscriptions" (under GUI > System Administration > Log Subscriptions) to make sure the proxy and/or WCCP logs are enabled. In AsyncOS version 7.1 and below: WCCP messages are logged in the Proxy Logs. How do I read or interpret the WCCP logs on Cisco Web Security appliance?Ĭisco Web Security Appliance (WSA), all versions of AsyncOS
0 kommentar(er)
