rssLink RSS for all categories
 
icon_blue
icon_green
icon_green
icon_orange
icon_red
icon_green
icon_green
icon_orange
icon_red
icon_red
icon_green
icon_green
icon_green
icon_blue
icon_orange
icon_red
icon_green
icon_blue
icon_red
icon_green
icon_green
icon_red
icon_red
icon_blue
icon_orange
icon_green
icon_green
icon_red
icon_green
icon_blue
icon_green
icon_green
 

FS#5274 — rbx-1-6k/rbx-2-6k

Attached to Project— Reseau Internet et Baies
Maintenance
Tout le réseau
CLOSED
100%
Nous allons mettre à jour le 2 routeurs de RBX1
rbx-1-6k et rbx-2-6k.

Le but est d'avoir l'IPv6 stable.

On commence par rbx-1-6k


rbx-1-6k uptime is 32 weeks, 5 days, 12 minutes
rbx-2-6k uptime is 1 year, 9 weeks, 4 days, 11 hours, 4 minutes

Date:  Monday, 28 March 2011, 11:56AM
Reason for closing:  Done
Comment by OVH - Monday, 28 March 2011, 06:22AM

rbx-1-6k fait


Comment by OVH - Monday, 28 March 2011, 06:28AM

c'est parti pour rbx-2-6k


Comment by OVH - Monday, 28 March 2011, 06:47AM

fini


Comment by OVH - Monday, 28 March 2011, 07:24AM

suite à la mise à jour, nous detectons de erreurs sur certaines cartes
DFC de cartes dans ces 2 routeurs.

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/configuration/guide/diagtest.html#wp1014355

rbx-2
Mar 28 05:53:55 GMT: %DIAG-SP-3-TEST_FAIL: Module 8: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)
Mar 28 05:59:04 GMT: %DIAG-SP-3-TEST_FAIL: Module 6: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)
Mar 28 06:04:11 GMT: %DIAG-SP-3-TEST_FAIL: Module 9: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)
Mar 28 06:09:23 GMT: %DIAG-SP-3-TEST_FAIL: Module 9: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)
Mar 28 06:14:31 GMT: %DIAG-SP-3-TEST_FAIL: Module 8: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)
Mar 28 06:19:34 GMT: %DIAG-SP-3-TEST_FAIL: Module 9: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)

rbx-1
Mar 28 06:08:26 GMT: %DIAG-SP-3-TEST_FAIL: Module 9: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)
Mar 28 06:13:58 GMT: %DIAG-SP-3-TEST_FAIL: Module 8: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)
Mar 28 06:19:23 GMT: %DIAG-SP-3-TEST_FAIL: Module 9: TestMacNotification{ID=13} has failed. Error code = 0x3C (DIAG_L2_ADD_ENTRY_ERROR)


Comment by OVH - Monday, 28 March 2011, 07:33AM

bon on a 5 DFC à changer ... on a gagné la journée ...

en attandant, on va desactiver ce monitoring. de
toute facon il faut changer les cartes.

A/I - Monitoring is active / Monitoring is inactive

13) TestMacNotification -------------> M**N****A*** 000 00:00:15.00 10

rbx-2-6k(config)#no diagnostic monitor module 6 test 13
rbx-2-6k(config)#no diagnostic monitor module 8 test 13
rbx-2-6k(config)#no diagnostic monitor module 9 test 13
rbx-1-6k(config)#no diagnostic monitor module 8 test 13
rbx-1-6k(config)#no diagnostic monitor module 9 test 13

13) TestMacNotification -------------> M**N****I*** 000 00:00:15.00 10


Comment by OVH - Monday, 28 March 2011, 10:55AM

Mar 28 09:49:10 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:49:28 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:49:39 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000
Mar 28 09:49:44 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:50:02 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:50:13 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000
Mar 28 09:50:17 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:50:36 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:50:50 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:50:50 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000
Mar 28 09:51:09 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:51:21 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:51:25 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000
Mar 28 09:51:43 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:51:59 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:52:03 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000
Mar 28 09:52:26 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:52:31 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:52:36 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000
Mar 28 09:52:58 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:53:07 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000
Mar 28 09:53:07 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:53:37 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:53:37 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000
Mar 28 09:53:37 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:54:13 GMT: %IPC-DFC8-5-WATERMARK: 4621 messages pending in rcv for the port Card8/0:Request(2080000.7) seat 2080000
Mar 28 09:54:13 GMT: %IPC-DFC9-5-WATERMARK: 4621 messages pending in rcv for the port Card9/0:Request(2090000.7) seat 2090000
Mar 28 09:54:17 GMT: %IPC-DFC6-5-WATERMARK: 4621 messages pending in rcv for the port Card6/0:Request(2060000.7) seat 2060000


Comment by OVH - Monday, 28 March 2011, 10:56AM

rbx-2-6k(config)#no power enable module 6
%Power admin state updated
rbx-2-6k(config)# power enable module 6
%Power admin state updated


Comment by OVH - Monday, 28 March 2011, 11:02AM

rbx-1-6k(config)#no mls flow ipv
rbx-1-6k(config)#no mls flow ipv6
rbx-2-6k(config)#no mls flow ip
rbx-2-6k(config)#no mls flow ipv


Comment by OVH - Monday, 28 March 2011, 11:37AM

rbx-2-6k(config)#no power enable module 8
%Power admin state updated
rbx-2-6k(config)# power enable module 8
%Power admin state updated
rbx-2-6k(config)#


Comment by OVH - Monday, 28 March 2011, 11:48AM

le fait de desactiver le netflow fixe le probleme. ceci
nous donnera quelques jours pour preparer les replacements
hardware.