Dell Powerconnect 6248 - Interface configuration problem

Hello,

I have come across the same issue with the Dell PowerConnect 6248.  The switch crashed in the middle of uploading firmware 3.3.7.3 and was already running firmware and bootcode 3.3.1.10.  I had to power cycle it to get it to respond, but it would not boot properly.  I ended up having to delete all the configs and images because it could not load the images (bad CRC or something like that).  I re-uploaded the 3.3.1.10 image via XMODEM and it would at least boot into the operational code, but I am getting these errors on boot and none of the ports will work:

<187> APR 22 20:09:07 10.222.5.240-1 DRIVER[79462592]: l7_usl_bcm.c(1788) 419 %%

Db L3_INTF(15) sync failed, error code -4 elem L3 Intf= 0, MAC= 0f:ff:f9:a0:03:8d, VID= 4094 Tunnel info: Sip 0 Dip 0 type 0

<188> APR 22 20:09:07 10.222.5.240-1 DRIVER[110126192]: l7_usl_sm.c(2429) 420 %%

USL: Cold start on unit 1 failed, error code -4

<188> APR 22 20:09:07 10.222.5.240-1 UNITMGR[140495040]: unitmgr.c(2243) 421 %%
Power On Start complete on unit 1

Any help would be appreciated.  These were supposed to go into production on 12/10.  Looks like that's not gonna happen.

Don

Hi Daniel,

I will upload 3.3.8.2 and see what happens.  I do have two identical switches that were in the process of being stacked (I had just installed the stacking modules and connected them to each other recently).  However, I have cleared the config several times and even restored to "factory defaults" on the boot menu.  Also, I disconnected the stacking cables and powered down unit #2.  In this case, would the switch still think it was supposed to be part of a stack?

I need to drive into the data center and disconnect all the Ethernet cables that are currently connected to this switch, and then I will upload 3.3.8.2 and give it a shot.  If that does not work, what would the next steps be?  Thanks.

Don

Boot Menu 3.3.12.1

CPU Card ID:   0x508541

/DskVol//  - disk check in progress ...

/DskVol//  - Volume is OK

         total # of clusters:  15,147

          # of free clusters:  10,378

           # of bad clusters:  0

            total free space:  20,756 Kb

   max contiguous free space:  15,953,920 bytes

                  # of files:  16

                # of folders:  1

        total bytes in files:  9,517 Kb

            # of lost chains:  0

  total bytes in lost chains:  0

volume descriptor ptr (pVolDesc):    0x3903150

XBD device block I/O handle: 0x10001

auto disk check on mount:      DOS_CHK_REPAIR |DOS_CHK_VERB_2

volume write mode:         copyback (DOS_WRITE)

max # of simultaneously open files:    52

file descriptors in use:       0

# of different files in use:       0

# of descriptors for deleted files:    0

# of  obsolete descriptors:        0

current volume configuration:

- volume label:    NO LABEL ; (in boot sector:              )

- volume Id:       0xc0

- total number of sectors:   60,716

- bytes per sector:     512

- # of sectors per cluster: 4

- # of reserved sectors:    1

- FAT entry size:      FAT16

- # of sectors per FAT copy:    60

- # of FAT table copies:   2

- # of hidden sectors:      4

- first cluster is in sector #  136

- Update last access date for open-read-close = FALSE

- directory structure:         VFAT

- file name format:            8-bit (extended-ASCII)

- root dir start sector:               121

- # of sectors per root:               15

- max # of entries in root:            240

FAT handler information:

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

- allocation group size:       2 clusters

- free space on volume:        21,254,144 bytes

Boot Menu 3.3.12.1

Select an option. If no selection in 10 seconds then

operational code will start.

1 - Start operational code.

2 - Start Boot Menu.

Select (1, 2):

Operational Code Date: Fri Nov  7 10:36:26 2014

Uncompressing.....

Adding 0 symbols for standalone.

CPU: Motorola E500 : Unknown system version.  Processor #0.

Memory Size: 0x10000000.  BSP version 1.2/0.

Created: Nov  7 2014, 09:51:06

ED&R Policy Mode: deployed

/DskVol//  - disk check in progress ...

dosChkLib : CLOCK_REALTIME is being reset to FRI APR 22 11:43:46 2005

Value obtained from file system volume descriptor pointer: 0x3573490

The old setting was THU JAN 01 00:00:00 1970

Accepted system dates are greater than THU DEC 27 00:00:00 1990

/DskVol//  - Volume is OK

         total # of clusters:  15,147

          # of free clusters:  10,378

           # of bad clusters:  0

            total free space:  20,756 Kb

   max contiguous free space:  15,953,920 bytes

                  # of files:  16

                # of folders:  1

        total bytes in files:  9,517 Kb

            # of lost chains:  0

  total bytes in lost chains:  0

volume descriptor ptr (pVolDesc):    0x3573490

XBD device block I/O handle: 0x10001

auto disk check on mount:      DOS_CHK_REPAIR |DOS_CHK_VERB_2

volume write mode:         copyback (DOS_WRITE)

max # of simultaneously open files:    52

file descriptors in use:       0

# of different files in use:       0

# of descriptors for deleted files:    0

# of  obsolete descriptors:        0

current volume configuration:

- volume label:    NO LABEL ; (in boot sector:              )

- volume Id:       0xc0

- total number of sectors:   60,716

- bytes per sector:     512

- # of sectors per cluster: 4

- # of reserved sectors:    1

- FAT entry size:      FAT16

- # of sectors per FAT copy:    60

- # of FAT table copies:   2

- # of hidden sectors:      4

- first cluster is in sector #  136

- Update last access date for open-read-close = FALSE

- directory structure:         VFAT

- file name format:            8-bit (extended-ASCII)

- root dir start sector:               121

- # of sectors per root:               15

- max # of entries in root:            240

FAT handler information:

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

- allocation group size:       2 clusters

- free space on volume:        21,254,144 bytes

Timebase: 66.666666 MHz, MEM: 266.666664 MHz, PCI: 66.666666 MHz, CPU: 533.333328 MHz

PCI unit 0: Dev 0xb314, Rev 0x01, Chip BCM56314_A0, Driver BCM56314_A0

PCI unit 1: Dev 0xb314, Rev 0x01, Chip BCM56314_A0, Driver BCM56314_A0

SOC unit 0 attached to PCI device BCM56314_A0

SOC unit 1 attached to PCI device BCM56314_A0

Adding BCM transport pointers

Configuring CPUTRANS TX

Configuring CPUTRANS RX

hpc - No stack ports. Starting in stand-alone mode.

Instantiating /download as rawFs,  device = 0x20001

Formatting /download for DOSFS

Instantiating /download as rawFs, device = 0x20001

Formatting.../download: file system is marked clean, skipping check

OK.

<186> APR 22 11:43:59 0.0.0.0-1 UNKN[268434720]: bootos.c(233) 1 %% Event(0xaaaaaaaa)

Instantiating RamCP: as rawFs,  device = 0x30001

Formatting RamCP: for DOSFS

Instantiating RamCP: as rawFs, device = 0x30001

RamCP:/  - disk check in progress ...

RamCP:/  - Volume is OK

         total # of clusters:  1,975

          # of free clusters:  1,973

           # of bad clusters:  0

            total free space:  1,010,176

   max contiguous free space:  1,010,176 bytes

                  # of files:  0

                # of folders:  0

        total bytes in files:  0

            # of lost chains:  0

  total bytes in lost chains:  0

OK.

(Unit 1 - Waiting to select management unit)>

Applying Global configuration, please wait ...

Applying Interface configuration, please wait ...

console>

<187> APR 22 11:44:06 0.0.0.0-1 DRIVER[79418992]: l7_usl_bcm.c(1799) 419 %% Db L3_INTF(15) sync failed, error code -4 elem L3 Intf= 0, MAC= 0f:ff:f9:a0:03:8d, VID= 4094

Tunnel info: Sip 0 Dip 0 type 0

<188> APR 22 11:44:06 0.0.0.0-1 DRIVER[110085232]: l7_usl_sm.c(2429) 420 %% USL: Cold start on unit 1 failed, error code -4

Did you manage to resolve this issue?.  I´m having the same problem with a PC6248

Sorry For Resurrecting such an old thread, but I'm having this exact same issue, same error codes, and all.

The MAC address doesn't match the Sticker on the device. What should I do now?

I was finally able to fix this problem by running Flash Diagnostics and entering the correct MAC address, serial number, and service tag. If you're running v2.x.x.x of the firmware, the Flash Diagnostics option is available from the Boot Menu. However, if you're running v3.x.x.x, you'll have to follow these steps:

• - Enter the Boot Menu
• - Select option 30 (a super-secret, unlisted option)
• - Enter the password "pc62xxkinnick"
• - Select the Flash Diagnostics option

This should erase all sectors on the flash including where the MAC address is burned in. When the switch resets, make sure you enter the correct MAC address, serial number, and service tag which should all be printed on the back of the switch.

Once you're done with that, you should be able to flash the latest version of the firmware using XMODEM as normal.

This resolved the issue I was having with a PC6248 I recently purchased. Thanks, Nate!