Cisco Cisco Traffic Anomaly Detector XT 5600A Information Guide

Page of 4
Traffic Anomaly Detector and Guard (Riverhead
Networks) FAQ
Document ID: 63559
Contents
Introduction
What is the default password for the Cisco Traffic Anomaly Detector and Guard?
I changed the date information from 08062004 to a future date of 12012004 using the "date 12012004" CLI
command. I then tested the date change to a zone via the SNMP OID rhZoneLastChangeTime. This worked
well except when the date is changed to a date earlier than the last changed date. Next, I changed the date
back to 08062004 on the CLI. However, the SNMP OID response to query for rhZoneLastChangeTime
remained 12012004 (the old date). After a reload, the OID response showed the correct (last) date change. Is
this a bug?
What is the difference between TCP Reset and TCP Safe−Reset?
After an upgrade I receive the "Can't connect to management module; SYSTEM IS NOT FULLY
OPERATIONAL: Connection refused Can't write to socket" error message. How do I fix this?
When I configure a Zone using the default template, I am unable to find the HTTP policy template under the
zone when I issue the "show policies" command. I see every other policy template except for HTTP. How can
I find it?
How do I perform root user password recovery?
Can I import custom SSL certificates to Cisco Anomaly Guard?
I received this error message. How can I resolve the issue?
RHWatchdog: RHWatchdog: Hardware Monitoring card reports HW errors.
Related Information
Introduction
This document addresses the most frequently asked questions (FAQs) related to the Cisco Traffic Anomaly
Detector and Guard (Riverhead Networks).
Refer to the Cisco Technical Tips Conventions for more information on document conventions.
Q. What is the default password for the Cisco Traffic Anomaly Detector
and Guard?
A. The default password for the Cisco Traffic Anomaly Detector and Guard is
admin/rhadmin.
Q. I changed the date information from 08062004 to a future date of
12012004 using the "date 12012004" CLI command. I then tested the date
change to a zone via the SNMP OID rhZoneLastChangeTime. This
worked well except when the date is changed to a date earlier than the
last changed date. Next, I changed the date back to 08062004 on the CLI.
However, the SNMP OID response to query for rhZoneLastChangeTime