Jump to content
Калькуляторы

Нужна помощь. SE 100 ALARM Controller power-on diagnostic failed

Доброго времени суток. Господа Гуру, требуется помощь в определении критичности ошибки.

 

Предыстория: SE100 верой и правдой трудился в стойке, пока не глюкнул UPS и не сделал кратковременное отключение питания

 

Последствия: Сейчас имею красный ALARM и

[local]se100#show system alarm all

Timestamp Type Source Severity Description

--------------------------------------------------------------------------------

Dec 5 20:32:20 xcrp 1 Major Controller power-on diagnostic failed

 

Собственно вопрос - насколько все плохо и как это лечить?

 

Заранее благодарен.

Share this post


Link to post
Share on other sites

Есть что-нибудь фатальное в выводах ?

 

#sh card

 

#sh diag pod

 

Наверно вот это можно назвать фатальным :(

[local]se100#sh diag pod

 

Slot Type POD Status (Enabled)

---- -------------------------------- ----------------------

N/A backplane

N/A fan tray

1 xcrp FAIL

2 carrier PASS

MIC1: ge-2-port

MIC2: ge-2-port

 

У меня абоненты на PPPoE (всего активных сессий около 400). Визуально все совершенно нормально работает...

Я правильно понимаю, что "дело пахнет керосином"?

 

Добавлю, что #sh card, ответ вроде вполне рабочий...

 

--------------------------------------------------------------------

Slot number : 1

Configured-type : xcrp

Installed-type : xcrp

Initialized : Yes

Active Crossconnect Card : Yes

Standby Crossconnect Card : No

Chassis Entitlement : All (0x0)

Memory : Max

 

--------------------------------------------------------------------

Slot number : 2

Configured-type : carrier

Installed-type : carrier

Initialized : Yes

Card Admin State : No Shut

IPPA running : Yes

EPPA running : Yes

Card PPAs Up : Yes

Default Line Card : Yes

MIC 1 : Config: ge-2-port Install: ge-2-port

MIC 2 : Config: ge-2-port Install: ge-2-port

Chassis Entitlement : All (0x0)

Ports Entitled : All

Share this post


Link to post
Share on other sites

Покажите полный лог загрузки + sh tech-support и "вероятно" добро пожаловать в клуб -

se100.jpg?1400082925

 

П.С. Просите доступ к закрытой группе по Ericsson SmartEdge.

Share this post


Link to post
Share on other sites

Покажите полный лог загрузки + sh tech-support и "вероятно" добро пожаловать в клуб -

 

П.С. Просите доступ к закрытой группе по Ericsson SmartEdge.

 

Я извиняюсь, но есть варианты получить лог загрузки, не перегружая SE?

На sh log startup, отдает наверно не совсем то....

 

 

 

[local]se100#sh log startup

Redback Log

Redback SmartEdge

Context ID 0x40080001

Dec 5 20:30:54: %ISP-6-INFO: [isp_heartbeat_register] is called on ACTIVE

Dec 5 20:31:22: %LOG-6-DROP: Drop Event

Dec 5 20:30:55: %PM-6-INFO: Normal reboot

Dec 5 20:31:06: %SYSLOG-6-INFO: /netbsd: VX Redundancy state: ### VERSION B3 TRUE ###

Dec 5 20:31:06: %SYSLOG-6-INFO: /netbsd: VX Redundancy state: ### VX_IS_ACTIVE TRUE ###

Dec 5 20:31:06: %SYSLOG-6-INFO: /netbsd: Notifying all processes of ACTIVE status

Dec 5 20:31:06: %SYSLOG-6-INFO: /netbsd: VX Redundancy state: ### VX_ACTSTB_DECIDED TRUE ###

Dec 5 20:31:09: %ISSU-6-INFO: [metad/256] metalib_endian_shm_create:metalib endian SHM created OK (0x458b8000/0x474b0000)

Dec 5 20:31:09: %ISSU-6-INFO: [metad/256] Can't open file /usr/siara/config/issu_debug.conf

Dec 5 20:31:09: %ISSU-6-INFO: [metad/256] Failed to parse file /usr/siara/config/issu_debug.conf

Dec 5 20:31:09: %ISSU-6-INFO: [metad/256] ISSU init ok [metah=1, meta_name=rbos, m=M, p=rbos_meta.xml.gze:0, c=rbos_meta.xml.gze:6071]

Dec 5 20:31:14: %SYSLOG-6-INFO: /netbsd: VX Redundancy state: ### VX_AL_UP TRUE ###

Dec 5 20:31:16: %ISSU-6-INFO: [metad/253] walk_all_bit_fields_frommeta:error getting size/bitlen(8/2/ra_enable

Dec 5 20:31:16: %ISSU-6-INFO: [metad/253] [schema=0, d=0x1871000, dlen= 40] id=nd_cfg_gen_t/3482/40

Dec 5 20:31:16: %ISSU-6-INFO: [metad/253] Callstack=0x41dab850/0x41db8f3c/0x41d9c618/0x1803988

[0000] 00000002 01DE0000 0000FFFF 0000FFFF 0000FFFF 0000FFFF 0000FFFF 0000FFFF

[0020] 0000FFFF 01000000 00000000 00000000 00000000 00000000 00000000 00000000

Dec 5 20:31:24: %PUBSUB-6-INF: CSM [rbnl_cache_initialize]: initializing PUBSUB, pid(259)

Dec 5 20:31:29: %CSM-6-CARD: card carrier INSERTED in slot 2

Dec 5 20:31:30: %CSM-6-CARD: MIC number 1 ge-2-port INSERTED in slot 2

Dec 5 20:31:30: %CSM-6-CARD: MIC number 2 ge-2-port INSERTED in slot 2

Dec 5 20:31:32: %ISSU-6-INFO: [csm/259] ISSU daemon is not running

Dec 5 20:31:33: %SHMM-6-INFO: ism2: Attaching to existing shared memory instance for key 10 in main(0x19c1000)

Dec 5 20:31:33: %RCM-6-INFO: RCM main has started in main(0x2ef3000)

Dec 5 20:31:33: %SHMM-6-INFO: rcm: Creating a new shared memory instance for key 1994 in main(0x2ef3000)

Dec 5 20:31:33: %SHMM-6-INFO: rcm: Creating a new shared memory instance for key 2506 in main(0x2ef3000)

Dec 5 20:31:34: %ISM-6-STATE_TOGGLE: This ISM going active.

Dec 5 20:31:34: %ISSU-6-INFO: [issud/263] Starting the active ISSU

Dec 5 20:31:34: %PUBSUB-6-INF: RCM [rbnl_cache_initialize]: initializing PUBSUB, pid(260)

Dec 5 20:31:35: %SYSLOG-1-ALERT: sysmond: checking vxWorks status...

Dec 5 20:31:37: %SHMM-6-INFO: ism2: Creating a new shared memory instance for key 4874 in main(0x19c1000)

Dec 5 20:31:37: %PUBSUB-6-INF: ISM [rbnl_cache_initialize]: initializing PUBSUB, pid(261)

Dec 5 20:31:38: %PUBSUB-6-INF: RIB [rbnl_cache_initialize]: initializing PUBSUB, pid(266)

Dec 5 20:31:39: %LM-3-SM: LM detached from ISSU metadata!

Dec 5 20:31:40: %SHMM-6-INFO: pemd: Attaching to existing shared memory instance for key 10 in main(0x1888000)

Dec 5 20:31:40: %LM-3-SM: LM checkpoint registered successfully!

Dec 5 20:31:40: %PUBSUB-6-INF: CLASSIFIER [rbnl_cache_initialize]: initializing PUBSUB, pid(270)

Dec 5 20:31:40: %PUBSUB-6-INF: LBLMGR [rbnl_cache_initialize]: initializing PUBSUB, pid(274)

Dec 5 20:31:40: %LM-3-SM: LM attached to DDL metadata!

Dec 5 20:31:40: %LM-3-SM: LM shared memory: 30 segments

Dec 5 20:31:45: %SHMM-6-INFO: arpd: Attaching to existing shared memory instance for key 4874 in sds-ipcc(0x18d7800)

Dec 5 20:31:45: %IPCPACK-6-INFO: [rcm/260] multiple calls to init

Dec 5 20:31:46: %SHMM-6-INFO: ldpd: Attaching to existing shared memory instance for key 4874 in sds-ipcc(0x19a1800)

Dec 5 20:31:47: %SHMM-6-INFO: flowd: Attaching to existing shared memory instance for key 10 in main(0x18b9000)

Dec 5 20:31:47: %SHMM-6-INFO: aaad: Attaching to existing shared memory instance for key 10 in main(0x1f0e000)

Dec 5 20:31:47: %RTDB-6-INFO: rcm: [rtdbFileHandlerMain] File handler thread started. in rtdbFileHandler(0x3016800)

Dec 5 20:31:47: %RTDB-6-INFO: rcm: rtdbFileInit() in rtdbFileHandler(0x3016800)

Dec 5 20:31:47: %RTDB-6-INFO: rcm: [rtdbFileDeviceCheck] Device is no longer available in rtdbFileHandler(0x3016800)

Dec 5 20:31:47: %RTDB-6-INFO: rcm: [rtdbFileHandlerMain] File handler thread for startup exiting... in rtdbFileHandler(0x3016800)

Dec 5 20:31:47: %RTDB-6-INFO: rcm: [rtdbFileSyncMain] Recovery callback with recovered ver:-1 in rtdbFileSync(0x3018000)

Dec 5 20:31:47: %SHMM-6-INFO: rcm: Attaching to existing shared memory instance for key 10 in main(0x2ef3000)

Dec 5 20:31:47: %SHMM-6-INFO: rcm: Attaching to existing shared memory instance for key 74 in main(0x2ef3000)

Dec 5 20:31:48: %LIM-CLIENT-3-ERR_GEN: IPC error in limmd message send

Dec 5 20:31:48: %LIMM-3-ERR_GEN: LIMM - Client Type = 0x100 client_id 0x1 is coming up

Dec 5 20:31:48: %SHMM-6-INFO: limmd: Attaching to existing shared memory instance for key 10 in main(0x18b3000)

Dec 5 20:31:49: %IPC-3-ERR: RCM(Thread 7f000205:e963000c): ipcSendCommon(): EP 0:0 is dead

Dec 5 20:31:49: %RTDB-6-INFO: rcm: [rtdbFileSyncMain] File sync thread started in rtdbFileSync(0x3018000)

Dec 5 20:31:49: %RCM-3-ERR: [rcm_db_extop_callback] Cannot start epsc-oam backend process, error 7107 in rdb_extop_thread(0x3019000)

Dec 5 20:31:52: %SHMM-6-INFO: pppd: Attaching to existing shared memory instance for key 10 in pkt-in(0x1ad6000)

Dec 5 20:31:53: %SHMM-6-INFO: ntpd: Attaching to existing shared memory instance for key 10 in main(0x19bd000)

Dec 5 20:31:55: %SHMM-6-INFO: pimd: Attaching to existing shared memory instance for key 4874 in sds-ipcc(0x1a27000)

Dec 5 20:31:57: %SHMM-6-INFO: igmpd: Attaching to existing shared memory instance for key 4874 in sds-ipcc(0x1cbe800)

Dec 5 20:31:58: %SHMM-6-INFO: qosd: Attaching to existing shared memory instance for key 2506 in main(0x1a41000)

Dec 5 20:31:58: %SHMM-6-INFO: atmd: Attaching to existing shared memory instance for key 1994 in main(0x1845000)

Dec 5 20:31:58: %SHMM-6-INFO: atmd: Attaching to existing shared memory instance for key 10 in main(0x1845000)

Dec 5 20:31:58: %SHMM-6-INFO: dot1qd: Attaching to existing shared memory instance for key 10 in main(0x1d26000)

Dec 5 20:31:59: %SHMM-6-INFO: l2tpd: Attaching to existing shared memory instance for key 10 in initial thread(0x19f5000)

Dec 5 20:31:59: %SHMM-6-INFO: dhcpd: Attaching to existing shared memory instance for key 10 in main(0x190d000)

Dec 5 20:31:59: %SHMM-6-INFO: pppoed: Attaching to existing shared memory instance for key 10 in main(0x1916000)

Dec 5 20:31:59: %L2TP-6-WARN:

Fault at l2tp_pl_io.c:849 (gbl_init_io)

Problem: res < 0

System Error: No buffer space available [gbl_init_io]

Dec 5 20:31:59: %L2TP-6-WARN: Message: Can't rbos_setsockopt() for SO_RCVBUF [gbl_init_io]

Dec 5 20:32:00: %SHMM-6-INFO: atmd: Attaching to existing shared memory instance for key 10 in main(0x1845000)

Dec 5 20:32:00: %SHMM-6-INFO: dot1qd: Attaching to existing shared memory instance for key 10 in main(0x1d26000)

Dec 5 20:32:01: %SHMM-6-INFO: clipsd: Attaching to existing shared memory instance for key 10 in main(0x19e1000)

Dec 5 20:32:02: %DHELPER-3-FILE_ERR: Save file device is no longer available.

Dec 5 20:32:02: %DHELPER-3-FILE_ERR: Save file unavailable

Dec 5 20:32:02: %SHMM-6-INFO: dhcpv6d: Attaching to existing shared memory instance for key 10 in main(0x193c000)

Dec 5 20:32:02: %SYSLOG-2-CRIT: /netbsd: xcrp_output() - returning ENETDOWN, fwd_cap = 4, lc_hash_fails = 0

Dec 5 20:32:03: %AAAHELPER-3-FILE_ERR: Save file device is no longer available.

Dec 5 20:32:03: %AAAHELPER-3-FILE_ERR: Save file unavailable

Dec 5 20:32:03: %LDP-6-INFO: no config, ask PM to kill the process

Dec 5 20:32:05: %DHELPERV6-3-FILE_ERR: Save file device is no longer available.

Dec 5 20:32:05: %DHELPERV6-3-FILE_ERR: Save file unavailable

Dec 5 20:32:05: [1300]: %IPFIX-3-ERR_FLOW: Collector 185.78.130.205 not reachable

Dec 5 20:32:05: %CSM-6-CARD: Card in slot 1 entering In Service state.

Dec 5 20:32:07: %RDB-6-INFO: rcm: Database is locked ('Backend Bulk Download' ) - No commits allowed at this time for tid 1054 in rcm_session_thread_han

Dec 5 20:32:08: %CSM-6-CARD: Card in slot 2 entering In Service state.

Dec 5 20:32:09: %CSM-6-CARD: MIC number 1 ge-2-port INSERTED in slot 2

Dec 5 20:32:09: %CSM-6-CARD: MIC number 2 ge-2-port INSERTED in slot 2

Dec 5 20:32:09: %LOG-4-NOINIT: mgd (pid 308) logged 1 msgs prior to initializing logger. Last event code: 0x63180000

Dec 5 20:32:09: {002}: %IPCPACK-6-INFO: [mgd/308] multiple calls to init

Dec 5 20:32:11: %RDB-6-INFO: rcm: Database is locked ('Backend Bulk Download' ) - No commits allowed at this time for tid 1054 in rcm_session_thread_han

Dec 5 20:32:17: %CSM-6-PORT: ethernet 1/1 link state UP service state UP, overall admin is UP

Dec 5 20:32:17: %RDB-6-INFO: rcm: Database is unlocked - Resuming commit for tid 1054 in rcm_session_thread_handler_255(0x3392800)AAA_main_callback

Dec 5 20:32:17: %SYSLOG-6-INFO: /netbsd: Set BSD Redundancy state: ### BSD_PROV_DONE TRUE ###

Dec 5 20:32:20: %PM-5-GEN: PM Received Process ISM state ready

Dec 5 20:32:20: %ISM-6-PPA_REG1: Switchover is complete and can process PPA registration now.

Dec 5 20:32:21: %PPAINFRA-6-ISTART_INFO: 72abf4cd/0000000005/092700000:02/IPPA/EU00:Ready to receive packets

Dec 5 20:32:21: %QOS-6-INFO: qos info: iPPA reg on slot 2

Dec 5 20:32:21: %PPAINFRA-6-ISTART_INFO: 7b5cd765/0000000005/486800000:02/EPPA/EU00:Ready to receive packets

Dec 5 20:32:21: %CSM-6-CARD: MIC number 1 ge-2-port INSERTED in slot 2

Dec 5 20:32:21: %QOS-6-INFO: qos info: ePPA reg on slot 2

Dec 5 20:32:21: %CSM-6-CARD: MIC number 2 ge-2-port INSERTED in slot 2

Dec 5 20:32:21: %CSM-6-CARD: card carrier INSERTED in slot 2 READY

Dec 5 20:32:21: %CSM-6-CARD: Card in slot 2 entering In Service state.

Dec 5 20:32:23: %CSM-6-PORT: ethernet 2/1 link state UP service state UP, overall admin is UP

Dec 5 20:32:23: %CSM-6-PORT: ethernet 2/3 link state UP service state UP, overall admin is UP

Dec 5 20:32:23: %CSM-6-PORT: ethernet 2/15 link state UP service state UP, overall admin is UP

Dec 5 20:32:23: %CSM-6-PORT: ethernet 2/16 link state UP service state UP, overall admin is UP

Dec 5 20:32:30: %ISM-6-SENT_EVENT: Sent event: XC RESYNC, to MBE: dot1q

Dec 5 20:32:30: %ISM-6-SENT_EVENT: Sent event: XC RESYNC, to MBE: aaa

Dec 5 20:32:30: %ATM-6-INFO: ATMd is verifying CCOD circuits.

Dec 5 20:32:30: %SYSLOG-6-INFO: /netbsd: VX Redundancy state: ### VX_INIT_DONE TRUE ###

Dec 5 20:32:32: %PPAINFRA-6-IFACE_INFO: aaea7765/0000000019/251100000:02/IPPA/EU00:ROUTING_READY sent to CSM

Dec 5 20:32:32: %SYSLOG-6-INFO: aaad: Radius Authentication srv 185.78.130.205/1812 (1812) received response (user BILL0000345).Marked Alive

Dec 5 20:32:37: %SYSLOG-6-INFO: aaad: Radius Accounting srv 185.78.130.205/1813 (1812) received response (user no username).Marked Alive

Dec 5 20:32:47: %SYSLOG-6-INFO: /netbsd: Notify all processes of change in redundancy state

Dec 5 20:32:47: %DLM-6-INFO: Starting release sync server

Dec 5 20:33:30: %NETOPD-6-INFO: netopd_ok_to_start_config: Unable to retrieve netop configuration, rdb rc: -2; using default (no netop)

 

 

Вывод sh tech-support вложил файлом. Несмотря на то, что убрал все 100% не относящиеся к сути вопроса, получилось много.

 

Изучив оба вывода, у меня возникло два вопроса:

 

1. Что такое Shark и как бороться с ошибкой

 

 

1 xcrp FAIL

 

Start at 20:31:30 12/05/2016 PASS

DRAM SPD EEPROM PASS

PPC Short DRAM PASS

System Controller Short SRAM PASS

System Controller SRAM ECC PASS

System Controller Register PASS

PPC L2 Cache PASS

RTC PASS

NVRAM PASS

Minnow FPGA Register PASS

Shark Download PASS

Shark Functional FAIL

ID EEPROM PASS

Environmental Limit PASS

Compact Flash Access PASS

Compact Flash Sector Buffer PASS

PPC-1 L2 Cache PASS

Card Type Valid PASS

 

 

2. В куске вывода ниже, он пытается спросить issu_debug.conf , однако я такого файла не нашел, как будто его и не было.

 

 

Dec 5 20:31:09: %ISSU-6-INFO: [metad/256] Can't open file /usr/siara/config/issu_debug.conf

Dec 5 20:31:09: %ISSU-6-INFO: [metad/256] Failed to parse file /usr/siara/config/issu_debug.conf

 

 

Спасибо за совет, в закрытую часть форума и попросился, и доступ получил.

sh_tech-support.txt

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.