| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
A customer has enabled port security on a DECrepeater 900TM to disable port from an intruding MAC address. Say the port locks out after a few days. Then we look at the intrusion log (by clicking on the broken lock ICON) and we see actual date and time of break-in detection. Where does this actual time come from? In out case it is OFF by about 10 or 12 hours roughly ? So we see the month/day/year hh:mm:ss - the actual time in the intrusion log and the intruding MAC address as well. I can't see anywhere in the DEChub 900 Management Module Menu where you can set date and time on the DEChub 900, in which are DECrepeater 900 is plugged in. Nor can I see any place where I can set date and time on the DECrepeater 900TM Module Menu. Alphonse
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4368.1 | Repeater keeps sysUpTime only...not time-of-day | NETCAD::PAGLIARO | Rich Pagliaro, Networks BU, HPN | Mon Apr 21 1997 10:54 | 18 |
Neither the repeater nor the DEChub 900 use internal time-of-day
clocks. The repeater itself logs only the value of sysUpTime at the
time the intrusion violation occured. sysUpTime is defined as "the time
(in hundredths of a second) since the network management portion of the
system was last re-initialized".
While I am very familiar with how the repeater works, I am less
familiar with how clearVISN MCM displays the information. I assume MCM
uses the time-of-day clock of the system on which it is running and
combines this information with the intrusion log sysUpTime timestamp
(as well as the current value of sysUpTime) to display the time and
date of the break-in detection.
I would first verify that the time-of-day clock on your system running
clearVISN is set correctly. Perhaps someone on the clearVISN team can
provide more details.
-Rich
| |||||
| 4368.2 | NETCAD::GALLAGHER | Tue Apr 22 1997 10:06 | 12 | ||
Rich's suggestion of looking at the clock on the station running clearVISN is a good one, but for what it's worth, some repeaters have a bug which causes their sysUpTime to lag by about 2%. This bug will be fixed in future firmware releases. This error can account for a 1.5 hour lag in three days. If you're looking at the log right after the port locks, then never mind. If you're looking after "a few days" then "a few days" would have to be about 20 days in order for your problem to be explained by this bug. -Shawn | |||||