Happy holidays everyone - 

I've been reading through several posts here and elsewhere about the 6224's inability to route its own management interface. Ok, enough, I get it. But what I don't get is a practical solution to what seems like a huge problem if you want to use the network to connect to the device to manage it (instead of the serial console port).

Let's say I want to have three networks A, B, and C, on the 6224 and configure it to route between any combination of them. Let's call them VLANs 1, 2, and 3. Three ethernet cables will connect to three ports on the 6224. one for network A, one for B, and one for C. Let's just ignore LAGs and redundant connections for this.

The management VLAN cannot be assigned to any of those networks, right? It says so in the documentation, and it's proven if you try to do it on the switch configuration. it doesn't let you do it.

So how do you reach the 6224 for management? Create a fourth network D, VLAN 4? That seems to be the general theme of answers to questions like this, but how do you reach this apparently isolated network? By definition it cannot be routed. Any computer that you normally use on A, B, or C, can't reach D.

So what then? A dedicated computer on D which can't reach anything but the management port of the switch? How about another completely separate router (I've got a Cisco ASA with some spare ports, or for a touch of irony, another 6224!) to provide a connection between D and one of the normally used networks? This is insane. 

Obviously I'm missing something here. I can't believe that the answer is, "if you turn on routing, the management interface is basically unusable" but that's how it looks from my possibly twisted perspective. I want to have my laptop, and any other computer, sit on a network that can be routed by the 6224, and also for that same laptop be able to reach the management interface of that same 6224. 

Will someone please help me understand this?

Thanks

Chris 

PS: I have an email address. It's pretty much unique on across the entire planet. I use it to log into this forum. But Dell, like so many others, insists on ignoring those facts and making me create another unique identifier by playing a game of 20 questions. Hence my remarkably stupid random user name.

Thanks again, and I hope someone at least gets a good laugh out this whole thing.

Hello,

I need OID for CPU load of PowerConnect switch 5424 and 5524 to configure CPU load in Nagios System. Please help me on the same.

Thanks,

Imran Khan.  

I have two N30xx switches at two different  locations running as layer 3 switches. Both are performing well as routing switch running static and ospf.. 

However, I cannot access the switches such as ping or telnet the switches using its vlan IP addresses outside of the local networks. I can access withing its networks (i.e. both my computer and the switch on the same subnet)

I have a few 6248 switches and checked configuration and don't seem to have anything missing. Is it something I am missing or I must use the Out of Band interface to access the switch?

Both switches are running firmware 6.1.2.4. Belwo is a traceroute from one of the switches trying to access a host on the network.

netxxxswtdc01#traceroute 10.10.10.10

Traceroute to 10.10.10.10 ,30 hops max 0 byte packets:

1 0.0.0.0 * * *
2 0.0.0.0 * *

Hop Count = 2 Last TTL = 2 Test attempt = 5 Test Success = 0

Thanks a lot!

John

Was purchased 2 Dell VRTX with the same equipment - (R1-2401, 2xM620). VRTX first went into production immediately after unpacking: installed ESXi 5.5. Update2 (VMware-VMvisor-Installer-5.5.0.update02-2068190.x86_64-Dell_Customized-A01.iso).

Within two or three days started having problems with the network: packet loss, temporary disable the internal network interfaces R1-2401.

VRTX with servers replaced with a spare. Migrated virtual machines and it worked on the new hardware without errors.

Problem vrtx servers and update the software on the latest from the site of Dell.

Started load testing dell vrtx with a generator TCP / UDP traffic iperf. It was suggested that a number of different test configurations:

1. Server with iperf (ubuntu 14.04) is connected to the external port R1-2401 at 1 Gbit / s. Both Dell M620 installed ESXi 5.5 Update2. Iperf client part running on virtual machines c Ubuntu 14.04.

2. Server with iperf (ubuntu 14.04) is connected to the external port R1-2401 at 1 Gbit / s. On one of the Dell M620 running Windows 2012 Server, on the second M620 by ESXi 5.5 Update2. Iperf client part running on virtual machines c Ubuntu 14.04, Windows Server 2012.

3. Iperf server running on Windows Server 2012 (M620 №1), a client on a virtual machine with Ubuntu 14.04 on M620 №2. R1-2401 switch is disconnected from the external network.

Use different operating systems due to excluding the impact of drivers under Windows / ESXi.

Switch log:

31-Dec-2014 08:02:15 %LINK-W-Down: gi1/1

31-Dec-2014 08:02:15 %LINK-I-Up: gi1/1

31-Dec-2014 08:02:15 %LINK-W-Down: gi1/1

31-Dec-2014 08:02:15 %LINK-I-Up: gi1/1

31-Dec-2014 08:02:15 %LINK-W-Down: gi1/1

31-Dec-2014 08:02:15 %LINK-I-Up: gi1/1

31-Dec-2014 08:02:16 %LINK-W-Down: gi1/1

31-Dec-2014 08:02:16 %LINK-W-Down: gi1/2

31-Dec-2014 08:02:16 %LINK-I-Up: gi1/1

31-Dec-2014 08:02:16 %LINK-I-Up: gi1/2

31-Dec-2014 08:02:16 %LINK-W-Down: gi4/1

31-Dec-2014 08:02:16 %LINK-W-Down: gi4/2

31-Dec-2014 08:02:16 %LINK-I-Up: gi4/1

31-Dec-2014 08:02:16 %LINK-I-Up: gi4/2

31-Dec-2014 08:02:17 %LINK-W-Down: gi4/1

31-Dec-2014 08:02:17 %LINK-W-Down: gi4/2

31-Dec-2014 08:02:17 %LINK-I-Up: gi4/1

31-Dec-2014 08:02:17 %LINK-I-Up: gi4/2

31-Dec-2014 08:02:17 %LINK-W-Down: gi4/2

31-Dec-2014 08:02:17 %LINK-I-Up: gi4/2

31-Dec-2014 08:02:17 %LINK-W-Down: gi4/2

console#sh interfaces counters GigabitEthernet 1/1

      Port       InUcastPkts  InMcastPkts  InBcastPkts    InOctets

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

     gi1/1        799019045       2265         4110     115722558417

                                                        2

      Port       OutUcastPkts OutMcastPkts OutBcastPkts  OutOctets

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

     gi1/1        483922423     1230188       943567    583945537894

Alignment Errors: 0

FCS Errors: 4

Single Collision Frames: 0

Multiple Collision Frames: 0

SQE Test Errors: 0

Deferred Transmissions: 0

Late Collisions: 0

Excessive Collisions: 0

Carrier Sense Errors: 0

Oversize Packets: 0

Internal MAC Rx Errors: 13718

Symbol Errors: 0

Received Pause Frames: 0

Transmitted Pause Frames: 0

Question: What can fail in this situation?

Greetings --  I'm a new owner of a PowerConnect 2824.  I'm trying to configure two VLANs, one for the 'clean' side of my network (VLAN 1) and one for the dirty side of my  network (outside the firewall) (VLAN 500).   VLAN 1 works just fine; all ports inside this VLAN can talk to one another.   Not so much so, for VLAN 500.

-----------

When I view the ports in the WebGUI, all the ports that are in VLAN 1, show "U" (untagged).   The two ports that I've put in VLAN 500 show "T"  (tagged).   **I can't get them to show "U"ntagged**.   Nothing I plug into the VLAN 500 ports can see each other!   It seems that the two VLAN 500 ports are sending/receiving tagged packets (essentially in Trunk Mode) to use Cisco terminology.

-----------

I need my two VLAN 500 ports to be 'Access Ports'  and not  'Trunk Ports'.  The only thing I'm trying to do here, is have two segregated layer-2 switches, in a single chassis.   What am I doing wrong?

Hi, starting from a factory-reset configuration and adding a couple of vlans, and enabling routing between them, it looks like the switch is allowing STP traffic to cross the vlan boundaries. This is both counter-intuitive, and not surprising, since STP was conceived before the concept of vlans.

Anyways is this actually the expected behavior without MSTP? I think this is occurring because another switch in the system, a 2824, is blocking ports that are attaching to the 62xx when I connect more than one port, each on a separate vlan, from the 2824 to the 62xx.

Basic configuration is vlan 1 untagged, vlan 4 tagged, on both switches. one cable between vlan 1 ports on the two switches, one cable between the vlan 4 ports on the two switches.

i.e. the 62xx is expected to act as a router between the subnets of the two vlans.

Thanks

Chris

Hello everyone, 

I'm trying to configure one of the ports of a relatively old 6224 to accept both tagged and untagged packets. Ideally a Linux workstation should be configured with a default IP address but if I chose to, I should be able to configure additional 802.1q interfaces (e.g. using "vconfig"). On a Cisco this is straightforward: 

#swithport mode trunk

#switchport native vlan xx

I have attempted the equivalent for the 6224:

console(config-if-1/g11)#switchport mode general
console(config-if-1/g11)#switchport general allowed vlan add 299 untagged
console(config-if-1/g11)#switchport general allowed vlan add 242,269 tagged
console(config-if-1/g11)#switchport general allowed vlan remove 1

...at which point all looks OK

console#show interfaces switchport ethernet 1/g11

Port: 1/g11
VLAN Membership mode:General Mode

Operating parameters:
PVID: 1
Ingress Filtering: Enabled
Acceptable Frame Type: Admit All
Default Priority: 0
GVRP status:Disabled
Protected:Disabled

Port 1/g11 is member in:

VLAN Name Egress rule Type
---- --------------------------------- ----------- --------
242 Tagged Static
269 Tagged Static
299 Untagged Static


Static configuration:
PVID: 1
Ingress Filtering: Enabled
Acceptable Frame Type: Admit All

Port 1/g11 is statically configured to:

VLAN Name Egress rule
---- --------------------------------- -----------
242 Tagged
269 Tagged
299 Untagged

... except it doesn't work. I mean tagged packets from the Linux workstation will go through to the respective vlans but the "299 untagged" doesn't seem to have any effects: untagged packets never reach VLAN 299. :-o

Of course, setting the port "access vlan 299" works like a charm but that's not what I want. 

Looking through the "6200 series manual" it would seem as if the trick should be possible with "trunk" mode also e.g. page 745 of the said manual reads:

Syntax
switchport trunk {allowed vlan vlan–list | native vlan vlan–id }

... but at leas on PCT6224 with the 3.3.11.1 firmware, that's not possible: switchport trunk can only be followed by "allowed" NOT by "native". 

Any advice?

Hi,

I currently have a network with 7 Powerconnect 6248 with 10G fibre uplinks to a Powerconnect 8024F.

I need to do firmware upgrades on the 6248 and 8024F. The 8024 switch is currently on version  3.1.4.5

and the 6248's are on ver 3.3.1.10. What are the latest versions and can they be updated safely from the web gui?

Hi All,

I am using PowerConnect 5548 firmware 4.1.0.8

I  want to get a port description configured over SNMP.

Ex:

SW conf:

interface gigabitethernet1/0/1
description testtest
spanning-tree portfast
switchport access vlan 172
!

I tried flowing oid's and i did not got required result:

1. IF-MIB::ifDescr.1 = STRING: gigabitethernet1/0/1

2. SNMPv2-SMI::enterprises.89.53.3.1.2.1 = STRING: "gi1/0/1"

Is there a way to get a description configured on port? 

Good Day PowerConnect fans

I currently have a Dell 2950 with a dual port BCM5708 and dual port BCM5709 NICs. I want to use the BACS 4 LACP teaming option toi connect these ports over two 5448's that are connected using LACP. I created a port-channel on each switch and have two Gig  ports assigned to the port channel. the set up is

interface port-channel 7
description NIC_Team_IOFSPROD001

interface range ethernet g(17-18)
channel-group 7 mode auto

I have not set a mode to the Port-channel, I am not sure what it should be

I have a connection one from each NIC to each switch so one connection from the BCM5708 and one from the BCM5709 to switch one and the same to switch two

I have all 4 NIC ports in the BACS 4 team using LACP

What do I need to configure to get it to work properly?

Hello! I recently set up a network that I am having trouble with and need someone to scan through my switch configs and tell me if they see anything that I have done wrong.

The network consists of an M1000 blade - fully populated, 2 Equalogic's, 2 Powerconnect 7048's, and 2 Powerconnect 8024-K's (in the blade enclosure). I have everything configured for redundancy. Each blade server has 4 NIC's, two are for iSCSI traffic and the other 2 are for VM network traffic.

The 7048's are stacked. I have gotten everything configured so that I can unplug any of the four NIC's (one at a time) on a blade, and the server will remain connected to storage and the VM network. I also can pull any of the 2 (one at a time) 8024K switches, and the servers will remain connected to the storage and VM network. However, when I unplug one of the 2 7048s, either one, I loose storage and VM network access, these whole network goes down. There is a lag configured for the uplink from the 7048's to a Meraki switch, so I should be able to still pass traffic but the network is going down.

Attached are the switch configs and a Visio diagram, I'm hoping someone can pick out the problem right away. My goal is full redundancy, so when I lose a 7048 the network stays up. Thanks in advance!

Hi,

I am working as Networking engineer at Aschere Energy Dallas.

I have configured a switch through the network, But it is showing networking error while accessing on the PC.

Please suggest to get rid from error.

Hello,

So we have a (7024) switch that has a connection from one of our routers carrying a network and all others ports are access ports and sit on VLAN1 and connect to some hosts. I have added a second switch (6248) that will have a second connection from our routers coming in carrying a second network. On the 6248 I have one access port setup on VLAN2 and one access port setup on VLAN3. I then have a third trunk port setup to allow VLAN 2-3 that I will connect to our ESXi host. I am able to pass traffic from the second network that I have assigned to VLAN3 on the ESXi host so the trunk port seems to work. When I connect the 7024 switch to the port on the 6248 configured for VLAN2 after a few seconds I lose connectivity to all hosts on that switch. I don't think there is a network loop as there is only the one cable connecting the two switches and the rest terminate in hosts. I am not sure if there is a configuration step that I am missing for connecting the two switches together. Does the port on the 7024 that is connecting to the 6248 have to be set to General Mode?

Thanks,

Drew

Thanks,

Andrew

under switching, vlan, and port settings if I click on edit I get a blank screen. Turns out it was the compatibility setting in IE. Just thought I would mention it if anyone was having the same problem.

How would you stack a total of 4 7048 switches with 2 switches on each floor?  Both groups of 2 switches are located 1 floor apart from each other.  What additional modules and cables are required?

thanks.

Hello,

I am now designing inter Vlan routing where Dell 8132F as a default gateway for internal which will connecting to others L2 switch.

8132F will hold multi secondary IP like following.


I have a question now.

1) All clients in the network what even connected to L3 or L2 switch should be able to connected their subnet gateway IP which owned by 8132F now?

2) Still need to setup anything at 8132F to allow inter VLAN routing?  I would like to allow inter route between vlan 1, 20, 30 & 50?

3) Is it can transfer traffic to default next gateway - 192.168.250.1 (vlan 50) which is my firewall by just add "ip route default 192.168.250.1"?   Of course my firewall will setup VLAN 50 as well.

-------
interface vlan 1

ip address 192.168.101.1 255.255.255.0
ip address 192.168.102.1 255.255.255.0 secondary
ip address 192.168.103.1 255.255.255.0 secondary
....
interface vlan 20
ip address 192.168.20.1 255.255.255.0
ip address 192.168.21.2 255.255.255.0 secondary
.....
interface vlan 30
ip address 192.168.200.1 255.255.255.0
ip address 192.168.201.1 255.255.255.0 secondary

interface vlan 50
ip address 192.168.250.254 255.255.255.0


ip route default 192.168.250.1

-------

Thanks!

I am now designing inter Vlan routing where Dell 8132F as a default gateway for internal which will connecting to others L2 switch.

8132F will hold multi secondary IP like following.


I have a question now.

1) All clients in the network what even connected to L3 or L2 switch should be able to connected their subnet gateway IP which owned by 8132F now?

2) Still need to setup anything at 8132F to allow inter VLAN routing?  I would like to allow inter route between vlan 1, 20, 30 & 50

3) Is it can transfer traffic to default next gateway - 192.168.250.1 (vlan 50) which is my firewall by just add "ip route default 192.168.250.1"?   Of course my firewall will setup VLAN 50 as well.


interface vlan 1

ip address 192.168.101.1 255.255.255.0
ip address 192.168.102.1 255.255.255.0 secondary
ip address 192.168.103.1 255.255.255.0 secondary
....
interface vlan 20
ip address 192.168.20.1 255.255.255.0
ip address 192.168.21.2 255.255.255.0 secondary
.....
interface vlan 30
ip address 192.168.200.1 255.255.255.0
ip address 192.168.201.1 255.255.255.0 secondary

interface vlan 50
ip address 192.168.250.254 255.255.255.0


ip route default 192.168.250.1

Thanks!

Posted this over at Spiceworks as well.

Looking for suggestions on how to setup the following between a Dell PowerConnect 3448P switch and a Sonicwall NSA220.

We are switching over to a hosted phone system, using the Polycom 335 phones.

I purchased a dedicated POE switch for the phones only, PC3448P.

I've setup the Sonicwall NSA220 to use X4 interface from the switch.

I've setup the Sonicwall NSA220 to provide DHCP to X4 interface, for the phones.

This will all work just fine if I choose not to add another connection to my main network switch to manage the switch. When I do that, the phones try to get an IP address from my main DHCP server, which I do dot want. So I decided to try setting up vlans on the switch where the phones and sonicwall plug into.

I used ports 13 to 24 for the phones and Sonicwall, created a new vlan 100 and assigned those ports to them.

On port 13, I have a connection to/from the sonicwall x4 interface.

I currently only have one of the news phones on port 24.

With this setup, I have a connection from the POE switch port 1 to my main network switch, that port is on the default vlan 1.

So, with that, I have both the phone and the connection up to interface X4 on the sonicwall within the vlan 100 ports.

However, with the connection from the POE switch port 1 to my main network switch, the phone is getting an IP address from my main network DHCP server, and not the Sonicwall.

I ran across this site, could this be causing my issue?

http://www.bauer-power.net/2013/06/how-to-change-default-vlan-on-dell.html#.VK01_3s2V6A

My department recently purchased a PC8024F (F/W 5.1.2.3) which will need VLAN routing. From what I can tell the 8024F is suppose to have VLAN routing but this one is without.

Is there something I am missing, a particular F/W version, or anything that is preventing this 8024F from having this feature? VLAN routing is not listed in the web menu, and is not recognized when entered in the vlan interface via CLI.

Any suggestions or advice is greatly appreciated! 

I'm having the hardest time getting a 6248 switch to work with vlans. I originally hooked up two 5448's and got vlan2 going nicely between them. I stuck the 6248 in between the two 5400's thinking there wouldn't be much more to it. But it doesn't work at all. Even to where I can't ping the vlan interface on the 6248 that's configured on itself! Any ideas are welcomed. Thanks

The physical ports and wiring goes like so:

Switch A (port 1/0/47) <-> (port 1/g28) Switch C (port 1/xg4) <-> (port 1/0/2) Switch B

Here are the configs for each switch. I pulled a few things out but this should cover the primary configs as they relate. If I make the uplink ports on Switch C, the 6248, trunk ports, it just stops talking to the switch on the other end entirely. General seems to only way to keep it working.

Switch A (5548)

vlan database
vlan 2,10
exit

!
interface vlan 1
ip address 10.88.16.59 255.255.255.0
!
interface vlan 2
ip address 10.16.1.3 255.255.255.0
!
interface gigabitethernet1/0/1
switchport access vlan 2
!
interface gigabitethernet1/0/47
switchport mode trunk
!
ip route 0.0.0.0 0.0.0.0 10.88.162.29

Switch B (5548)

vlan database
vlan 2,10,20
exit

!
interface vlan 1
ip address 10.88.16.25 255.255.255.0
ip address 172.16.16.25 255.255.255.0
!
interface vlan 2
ip address 10.16.1.25 255.255.255.0
!
interface tengigabitethernet1/0/2
description uplinkto.5
switchport mode trunk

ip route 0.0.0.0 0.0.0.0 10.88.16.1 

Switch C (6248)

vlan database
vlan 2,10-11
vlan routing 2 1
exit

ip address 10.88.162.5 255.255.255.0

ip default-gateway 10.88.162.1

interface vlan 2
routing
ip address 10.16.1.5 255.255.255.0
exit

interface ethernet 1/g28
switchport mode general
switchport general allowed vlan add 2
exit

interface ethernet 1/xg4
description '1stflBack'
switchport mode general
switchport general allowed vlan add 2,10
exit