Hi

First comment is you need to upgrade your firmware to the latest version.

You haven't enabled routing on the switch; this is fine if the device connected to port 47 is VLAN aware and has 802.1q enabled and can route between the three VLANs.

If not, then you will need to enable routing on the switch, and also set up the default route to point at the gateway/router...and you will need to set up a new VLAN for port 47...

config

ip routing

ip route 0.0.0.0 0.0.0.0 x.x.x.x                         where x.x.x.x is the IP address of the router/gateway

interface VLAN 10

ip address a.a.a.a /24                                     assign an IP address to VLAN 10 from the address rabge for that subnet, /24 is an example for a class C, adjust to match your subnet mask

routing

exit

interface vlan 20

ip address b.b.b.b /24

routing

exit

interface vlan 30

ip address c.c.c.c /24

routing

exit

vlan database

vlan 99

exit

interface vlan 99

ip address x.x.x.?? /24                                 give VLAN 99 an address in the subnet range for the gateway/router

routing

exit

interface 1/g47

switchport access vlan 99

exit

Thanks for replying.

1. Upgrading the firmware to the latest version, will be another task.

2. but....How to resolve this vlan interface error?

console(config-if-vlan10)#ip address 192.168.77.150 /24

ERROR: Routing is not allowed on the Management VLAN.

(googling in progress)

has this has to do with firmware version?

Trunk Port settings:

Port: 1/g47

VLAN Membership mode:General Mode

Operating parameters:

PVID: 1

Ingress Filtering: Enabled

Acceptable Frame Type: Admit All

Default Priority: 0

GVRP status:Enabled

Protected:Disabled

Port 1/g47 is member in:

VLAN    Name                              Egress rule   Type

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

10                                        Tagged        Static

20                                        Tagged        Static

30                                        Tagged        Static

Something that maybe hanging up things is you have PVID 1 set on the trunk/general mode port.  With this setting any possible untagged traffic coming into the trunk/general port is tagged as VLAN 1.  You can make changes to your settings on the trunk to add PVID 10 to match your native/management VLAN that you have set up on the switch.

Example

The following example shows how to configure the PVID for 1/g8, when the
interface is in general mode.

console(config)#interface ethernet 1/g8
console(config-if-1/g8)#switchport general pvid 10

It looks like your management vlan routing question was answered in another post.

Hope this helps,

Keep us updated if you can.

HI Willy. The suggested answer is not working at all. There were no progress at all.

@ pointB. I have managed to change PVID to 10 but when i plugged the ethernet cable to a VLAN10 port, there were no traffic at all (going to GW).

Expectation from the suggested solution:

I was kind of expecting that VLAN10 should be able to connect to my GW, but it didn't.

To check further, I should get an ip from my dhcp server? worst is it can't reach the GW. what did i missed from your advise? to make this simple; can you just post the answer.

2. Since 1/g47 is a trunk port ; will it be possible to add multiple of PVIDs 10,20,30 in an interface at general mode?

what i understood from your advise was; point PVID to a certain existing vlan would allow traffic to GW.

3. I hope you understand what i wanted to draw out from my initial post.

If this was also answered from another post, could you point me on that post so i can test that.

It's been days now since I am configuring this switch and no right path of fixing this. Dell LACKS! proper documentation!!!.

Point A. # console#show interfaces switchport ethernet 1/g47

Port: 1/g47

VLAN Membership mode:General Mode

Operating parameters:

PVID: 10

Ingress Filtering: Enabled

Acceptable Frame Type: Admit All

Default Priority: 0

GVRP status:Enabled

Protected:Disabled

Port 1/g47 is member in:

VLAN    Name                              Egress rule   Type

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

10                                        Tagged        Static

20                                        Tagged        Static

30                                        Tagged        Static

Static configuration:

PVID: 10

Ingress Filtering: Enabled

Acceptable Frame Type: Admit All

Port 1/g47 is statically configured to:

VLAN    Name                              Egress rule

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

10                                        Tagged

20                                        Tagged

30                                        Tagged

Forbidden VLANS:

VLAN    Name

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

Point B. console#show running-config

.

. (other interfaces truncated)

interface ethernet 1/g47

gvrp enable

switchport mode general

switchport general pvid 10

switchport general allowed vlan add 10,20,30 tagged

switchport general allowed vlan remove 1

exit

exit

i forgot to mentioned that I tried putting multiple PVID on a port in general mode, and the answer was - NO.

PVID is only good for 1 VLAN tag/name.

Again, How will it will route traffic VLAN20 and 30 through that 1/g47 if it has PVID:10 only?

Untagged packets entering the switch are tagged with the LAGs ID specified by the PVID on a general mode port.  Typically you would set this in order to tag any incoming untagged packets with the native/management VLAN.  This is not something that has to be done for communication between VLANs and the default gateway (next hop device toward internet).  On the 6248 switch the native VLAN in your case currently VLAN 10 is not allowed to be routed. VLAN 10 has to either be the native VLAN or a routed VLAN not both.

Let’s take a look at the output from this command

In order for the different VLANs to be routed to the outside internet device you will need a route designated.

Example if 10.10.10.1 is the next hop IP towards the internet connection.

Console (config)# ip route 192.168.77.245 255.255.255.0 10.10.10.1

Console (config)# ip route 10.10.10.1

Console (config)# ip route 10.10.10.1

Looking thru your first post again you do not have an IP set for VLAN 20, 30 have you added that since?

Here is an example of setting up routing:

console(config)# ip routing                           (enables routing globally)

console(config)# interface vlan 10

console(config-if-vlan100)# ip address 172.16.100.1 /24             (sets IP address for VLAN 10)

console(config-if-vlan100)# exit

console(config)# interface vlan 20

console(config-if-vlan200)# ip address 172.16.200.1 /24              (sets IP address for VLAN 20)

console(config-if-vlan200)# exit

console(config)# vlan database

console(config-vlan)# vlan routing 10                                (enables routing for VLAN 10)

console(config-vlan)# vlan routing 20                                (enables routing for VLAN 20)

console(config-vlan)# end

console#

Console (config)# ip route 192.168.77.245 255.255.255.0 10.10.10.1

- just to make it clear, the above should be the , right?

Yes, that is correct.

so before i made some configuration changes on the layer 3 switch. I decided to upgrade the firmware. 
as a result, i ended with an error. Right after boostrap, the system Un-compresses the OS to boot up  but unfortunately the switch went into some issues.

There was an error during decompression... resetting the switch

is there a way to restore this back and *please* could you point a working firmware!!!
For the record, I've read some advises and suggestion of which firmware version should be safe to start with and firmware version 3.2.1.3 was the best choice but it didn't  worked on my case.

I need a quick solution on this ASAP as my switch is a barely metal now. it doesn't function!!!.

CPU Card ID:   0x508541
/DskVol//  - disk check in progress ...
/DskVol//  - Volume is OK

          total # of clusters:  15,147
           # of free clusters:  5,368
            # of bad clusters:  0
             total free space:  10,736 Kb
     max contiguous free space:  10,985,472 bytes
                   # of files:  22
                 # of folders:  1
         total bytes in files:  19,531 Kb
             # of lost chains:  0
   total bytes in lost chains:  0

volume descriptor ptr (pVolDesc):       0xffeea80
cache block I/O descriptor ptr (cbio):  0xffeeb60
auto disk check on mount:               DOS_CHK_ONLY | DOS_CHK_VERB_2
max # of simultaneously open files:     22
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:           0x0
 - 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
 - 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:        10,993,664 bytes


Boot Menu Version: 20 September 2007
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 Jan 14 10:59:43 2011
Uncompressing.....

                       50%                     100%
|

There was an error during decompression... resetting the switch

























CPU Card ID:   0x508541
/DskVol//  - disk check in progress ...
/DskVol//  - Volume is OK

          total # of clusters:  15,147
           # of free clusters:  5,368
            # of bad clusters:  0
             total free space:  10,736 Kb
     max contiguous free space:  10,985,472 bytes
                   # of files:  22
                 # of folders:  1
         total bytes in files:  19,531 Kb
             # of lost chains:  0
   total bytes in lost chains:  0

volume descriptor ptr (pVolDesc):       0xffeea80
cache block I/O descriptor ptr (cbio):  0xffeeb60
auto disk check on mount:               DOS_CHK_ONLY | DOS_CHK_VERB_2
max # of simultaneously open files:     22
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:           0x0
 - 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
 - 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:        10,993,664 bytes


Boot Menu Version: 20 September 2007
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 Jan 14 10:59:43 2011
Uncompressing.....

                       50%                     100%
|

There was an error during decompression... resetting the switch

Once I have a solution on this then I'll go ahead with the configuration.
Oh! Dell......(sigh) 

from a verified Answer post!!!

en.community.dell.com/.../20115194.aspx

good there was a workaround for this problem.

- 11 - Activate Backup Image

this should boot up image1 (previous OS version)

then it should be back to normal.

on the second though, it didn't went back to normal.

Here is a recovery option for corrupt IOS image. I pulled this information from the User Guide page 100.

http://support.dell.com/support/edocs/network/PC62xx/en/UCG/ucg_en.zip

Load New Operational Code Using XMODEM

Use option 4 when a new software version must be downloaded to replace corrupted files, update, or

upgrade the system software.

To download software from the Boot menu:

1. On the Boot menu, select 4 and press .

The following prompt displays:

[Boot Menu] 4

Ready to receive the file with XMODEM/CRC....

Ready to RECEIVE File xcode.bin in binary mode

Send several Control-X characters to cancel before transfer starts.

2. When using HyperTerminal, click Transfer on the HyperTerminal menu bar.

3. From the Transfer menu, click Send File.

The Send File window displays.

4. Enter the file path for the file to be downloaded.

5. Ensure the protocol is defined as Xmodem.

6. Click Send.

The software is downloaded. Software downloading takes several minutes. The terminal emulation

application, such as HyperTerminal, may display the loading process progress.

ip address x.x.x.?? /24                                 give VLAN 99 an address in the subnet range for the gateway/router

console(config-if-vlan99)#ip address 192.168.77.253 /24

Subnet conflict between specified IP Address and current configuration.

All routing interfaces, service ports and network ports must be configured on different subnets.

i have not configured trunk port yet  -1/g47