внимание на это и обращено =)
вопрос в том, что с этим делать? не сталкивался ли кто с таким?
не совсем понятно как интерпритировать эти сообщения. за 4 секунды voltage статус возвращается в норму. нестабильное напряжение в сети? или же это неисправность блока питания?
Приветствую.
В user-log такие сообщения:
2014-09-22 08:51:39 | WARN | CPU #000 | Abnormal raise in interior temperature.
2014-09-22 08:51:39 | INFO | CPU #000 | trap:temprature alarm on status value 3
2014-09-22 08:51:39 | WARN | CPU #000 | SE Control Module: A problem occurred. Please report to Cisco's customer support
2014-09-22 08:51:39 | WARN | CPU #000 | The SE status changed to Warning
2014-09-22 08:51:39 | INFO | CPU #000 | trap:warning status
2014-09-22 08:51:43 | INFO | CPU #000 | Temperature is back to normal
2014-09-22 08:51:43 | INFO | CPU #000 | trap:temprature alarm off status value 2
2014-09-22 08:51:43 | INFO | CPU #000 | The SE status changed to Operational
2014-09-22 08:51:43 | INFO | CPU #000 | trap:operational status
2014-09-22 09:29:08 | WARN | CPU #000 | Abnormal raise in interior temperature.
2014-09-22 09:29:08 | INFO | CPU #000 | trap:temprature alarm on status value 3
2014-09-22 09:29:08 | WARN | CPU #000 | SE Control Module: A problem occurred. Please report to Cisco's customer support
2014-09-22 09:29:08 | WARN | CPU #000 | The SE status changed to Warning
2014-09-22 09:29:08 | INFO | CPU #000 | trap:warning status
2014-09-22 09:29:11 | INFO | CPU #000 | Temperature is back to normal
2014-09-22 09:29:11 | INFO | CPU #000 | trap:temprature alarm off status value 2
2014-09-22 09:29:11 | INFO | CPU #000 | The SE status changed to Operational
2014-09-22 09:29:11 | INFO | CPU #000 | trap:operational status
2014-09-22 09:52:15 | WARN | CPU #000 | HW failure due to voltage problem.
2014-09-22 09:52:15 | INFO | CPU #000 | trap:voltage alarm on status value 3
2014-09-22 09:52:15 | WARN | CPU #000 | SE Control Module: A problem occurred. Please report to Cisco's customer support
2014-09-22 09:52:15 | WARN | CPU #000 | The SE status changed to Warning
2014-09-22 09:52:15 | INFO | CPU #000 | trap:warning status
2014-09-22 09:52:19 | INFO | CPU #000 | Voltage is OK
2014-09-22 09:52:19 | INFO | CPU #000 | The SE status changed to Operational
2014-09-22 09:52:19 | INFO | CPU #000 | trap:operational status
2014-09-22 10:32:09 | WARN | CPU #000 | Abnormal raise in interior temperature.
2014-09-22 10:32:09 | INFO | CPU #000 | trap:temprature alarm on status value 3
2014-09-22 10:32:09 | WARN | CPU #000 | SE Control Module: A problem occurred. Please report to Cisco's customer support
2014-09-22 10:32:09 | WARN | CPU #000 | The SE status changed to Warning
2014-09-22 10:32:09 | INFO | CPU #000 | trap:warning status
2014-09-22 10:32:12 | INFO | CPU #000 | Temperature is back to normal
2014-09-22 10:32:12 | INFO | CPU #000 | trap:temprature alarm off status value 2
2014-09-22 10:32:12 | INFO | CPU #000 | The SE status changed to Operational
2014-09-22 10:32:12 | INFO | CPU #000 | trap:operational status
2014-09-22 10:37:36 | INFO | CPU #000 | A Telnet session from 10.128.15.2 was established.
Версия ПО 4.1.0.
Кроме SCE, в помещении находится немало оборудования. Ни у кого таких проблем нет. Температура и напряжение соответсвует требованиям. Сервисного контракта cisco — нет.
Что посоветуете?
