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

FS#3849 — switch bug trouvé

Attached to Project— Serveurs dédiés
Amélioration
ALL
CLOSED
100%
Pour faire booter les switchs en DHCP et recuperer la configuration
en TFTP, il suffit d'ajouter "boot host dhcp" dans la configuration
du switch. Le switch boote sur sa configuration minimaliste, se
configure au niveau du reseau et doit recuperer sa configuration
sur le serveur tftp. Ceci permet de gerer les configurations très
longe, trop longe pourque la configuration puisse être sauvée sur
la nvram ... domage ...

Nous avons eu de crashs de switchs dans ce type de configuration:

%Software-forced reload

16:25:04 UTC Wed Feb 3 2010: Unexpected exception to CPUvector 2000, PC = 117813C
-Traceback= 117813C 1178100 11742C4 11231DC BB48C4 BB872C BB8220 BF4FD4 BF5568 CF8E88 CF26C0 CE9F04 CF52DC CF557C CF56EC EEBE18

Writing crashinfo to flash:/crashinfo_ext/crashinfo_ext_4

=== Flushing messages (16:25:08 UTC Wed Feb 3 2010) ===

Buffered messages:

00:02:45: %SYS-6-STACKLOW: Stack for process Boot HostDHCP running low, 0/6000
Cisco IOS Software, C2960 Software (C2960-LANBASE-M), Version 12.2(52)SE, RELEASE SOFTWARE (fc3)
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Fri 25-Sep-09 03:14 by sasyamal

Debug Exception (Could be NULL pointer dereference) Exception (0x2000)!
SRR0 = 0x0068016C SRR1 = 0x00029230 SRR2 = 0x0067F254 SRR3 = 0x00021000
ESR = 0x00000000 DEAR = 0x00000000 TSR = 0x8C000000 DBSR = 0x10000000

CPU Register Context:
Vector = 0x00002000 PC = 0x0117813C MSR = 0x00029230 CR = 0x33005053
LR = 0x01178100 CTR = 0x00E8C678 XER = 0xC000005F
R0 = 0x01178100 R1 = 0x0330DD08 R2 = 0x00000000 R3 = 0x031F570C
R4 = 0xFFFFFFFE R5 = 0x00000000 R6 = 0x0330DCF0 R7 = 0x00000000
R8 = 0x00000000 R9 = 0x00000000 R10 = 0x018F0000 R11 = 0x031F5708
R12 = 0x00028AA5 R13 = 0x00110000 R14 = 0x0000040F R15 = 0x00000001
R16 = 0x00000001 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000
R20 = 0x00000000 R21 = 0x00000000 R22 = 0x00000000 R23 = 0x00000000
R24 = 0x00000000 R25 = 0x01849024 R26 = 0x00000000 R27 = 0x00000000
R28 = 0x00000000 R29 = 0x01C50000 R30 = 0x00000000 R31 = 0x00000000

Stack trace:
PC = 0x0117813C, SP = 0x0330DD08
Frame 00: SP = 0x0330DD18 PC = 0x01178100
Frame 01: SP = 0x0330DD30 PC = 0x01173DC8
Frame 02: SP = 0x0330DD50 PC = 0x011742C4
Frame 03: SP = 0x0330DD68 PC = 0x011231DC
Frame 04: SP = 0x0330DD90 PC = 0x00BB48C4
Frame 05: SP = 0x0330DDF8 PC = 0x00BB872C
Frame 06: SP = 0x0330DE30 PC = 0x00BB8220
Frame 07: SP = 0x0330DE80 PC = 0x00BF4FD4
Frame 08: SP = 0x0330DEC0 PC = 0x00BF5568
Frame 09: SP = 0x0330DEF0 PC = 0x00CF8E88
Frame 10: SP = 0x0330DF18 PC = 0x00CF26C0
Frame 11: SP = 0x0330DF30 PC = 0x00CE9F04
Frame 12: SP = 0x0330E000 PC = 0x00CF52DC
Frame 13: SP = 0x0330E008 PC = 0x00CF557C
Frame 14: SP = 0x0330E010 PC = 0x00CF56EC
Frame 15: SP = 0x0330E178 PC = 0x00EEBE18

Après quelques dizaines d'heure, nous avons trouvé l'origine du
probleme: ce genre de boot n'aime pas les commandes vtp. Il
faut donc les supprimer des configurations enregistrés sur
le tftp. Dans notre cas, on utilise pas le vtp et donc on le
desactive avec
vtp domain <domaine>
vtp mode transparent

Voilà :) Un probleme de moins :) Yeah !
Date:  Wednesday, 10 February 2010, 18:42PM
Reason for closing:  Done
Comment by OVH - Wednesday, 10 February 2010, 18:42PM

le 2950 n'a pas cette option. donc on le fera "à la main".