# grep S34 logs
Mar 8 16:51:05 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 16:57:31 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 16:58:57 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 17:47:22 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 17:48:16 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 17:48:56 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 17:49:50 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 18:01:02 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 18:02:36 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 18:11:22 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 18:11:45 pm1.wlm portmaster: port S34 terminated - Lost Carrier
Mar 8 18:16:24 pm1.wlm portmaster: port S34 terminated - Lost Carrier
There were *NO* calls at all made on this particular port, but it keeps
spitting out "Lost Carrier" left and right for no particular reason.
The real way to get Lost Carrier reporting is of course radius.
RADIUS reporting:
Lost Carrier 7.84% 936/11942
SYSLOG reporting:
Lost Carrier 1.05% 111/10528
Note the difference in the number of total disconnects is almost exactly
what the difference between the number of Lost Carrier disconnects is.
There are a few other messages which loop sometimes.
This has happened to me for the longest time, even with the newest
ComOS's. MZ keeps telling me to call up and report it... but it really
is more annoying than anything else.
Jordan
-- Jordan Mendelson : http://jordy.wserv.com Web Services, Inc. : http://www.wserv.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>