Hello!
I have a great switch Dell PowerConnect 8132 with 2 power supply. But second (or left) not activated.
I'm rotate power supply one on over, no result. Both power supply is working (green light on back).
In picture you can see a problem.
I'm update firmware, now 5.1.1.7.
Maybe exist command or something to re-initialize\re-scan switch components ?
HI all,
Ok so we have 2 separate WAN circuits coming into our Business.
I would like to try and setup redundancy for these 2 circuits.
Currently both routers are managed by the Telco companies.
We currently have 2 PIX firewalls, one from each circuit.
I have a Dell PowerConnect 6024 sitting here not being used.
Can I; Setup 2 interfaces on the 6024 using VRRP to plug both Pixs into and get redundancy?
Hi there!
I want one of the switches PC8164 to always be the root for different VLANs that are configured.
How to made it?
on cisco switches this could be done by command:
Spanning Tree VLAN 1 root primary
Regards!
Hi there,
I already spent a day and half trying to solve this problem but I am not getting anywhere. Here is the basic breakdown of the test setup.
Port 1: Connected to the existing network (so I can get to the ESXi host from my PC)
Port 3: My ESXi host is connect to this
VMs are tagged with VLAN via ESXi Port Group properties.
All VLANs have 1 VM except VLAN 10 which has 2.
All VLANs have IP address ending with .1 with /24 subnet mask.
All VMs have the corresponding default gateway pointing to the VLAN's IP (x.x.x.1)
I am able to get the IP from DHCP server from different VLANs.
Things that work:
From any VM, I can ping to any VLAN's IP (so VMs in VLAN 10 can ping VLAN 20's IP)
From console, I can ping any VLAN's IP
Things that DO NOT work:
From console, I cannot ping any VM's IP.
From any VM, I cannot ping any address (including VMs in the same VLAN)
Here is my running config:
!Current Configuration:
!System Description "PowerConnect 6248, 3.3.7.3, VxWorks 6.5"
!System Software Version 3.3.7.3
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 10,20,30,40,50,300
vlan routing 10 1
vlan routing 20 2
vlan routing 30 3
vlan routing 40 4
vlan routing 50 5
vlan routing 300 6
exit
sntp unicast client enable
sntp client poll timer 1024
sntp server 0.north-america.pool.ntp.org
clock timezone -7 minutes 0
stack
member 1 2
exit
ip address 192.168.8.250 255.255.255.0
ip default-gateway 192.168.8.230
ip routing
ip helper-address 10.80.10.10 dhcp
interface vlan 10
name "Server"
routing
ip address 10.80.10.1 255.255.255.0
exit
interface vlan 20
name "Printer - Switch"
routing
ip address 10.80.20.1 255.255.255.0
ip helper-address 10.80.10.10
exit
interface vlan 30
name "Workstation"
routing
ip address 10.80.30.1 255.255.255.0
ip helper-address 10.80.10.10
exit
interface vlan 40
name "Phones"
routing
ip address 10.80.40.1 255.255.255.0
ip helper-address 10.80.10.10
exit
interface vlan 50
name "Camera"
routing
ip address 10.80.50.1 255.255.255.0
ip helper-address 10.80.10.10
exit
interface vlan 300
name "Router"
routing
ip address 192.168.1.250 255.255.255.0
exit
username "root" password XXXXXXX level 15 encrypted
dhcp l2relay
dhcp l2relay vlan 10,20,30,40,50
!
interface ethernet 1/g1
switchport mode general
exit
!
interface ethernet 1/g2
switchport mode general
exit
!
interface ethernet 1/g3
spanning-tree portfast
switchport mode general
switchport general allowed vlan add 10,20,30,40 tagged
exit
exit
I'm looking at installing a new core network for two small server rooms and using Powerconnect 7048's in a stack in each room. I'm not sure how best to connect them though. The two server rooms are about 40m apart and I am assuming fiber would be preferential over copper at that distance and it would be less susceptible to interference. I'm thinking I can put the optional 10gb Modules with SFP+ ports in the 7048's but I'm not sure which transceivers or fibre cable I should use for a 10gb connection?, any idea's or recommendation please? Or if I should be doing something else.
Customer has 2 x 2 PC8024F Stacks which are linked. When upgrading the firmware to 5.1.1.7 it appears that all 4 switches upgrade correctly. When they start the config the switches "lock up" and there is no external access (ping etc). Internal access appears to be fine. Searched the forums but cannot find even a hint of this problem. Can anyone shed some light.
Thanks.
Hello,
i'm having a huge problem that i'm finding near impossible to crack:
on a large spine-leaf netwok i have 3 core PC6224 switches connected via their 10Gbit ports(there's no STP/mesh/nothing, a single connection).
All the gigabit ports of those switches in turn connect to distribution switches
thing is that during DDoS attacks or "high" traffic conditions(relative.., it happens when there's ~1.5/2Gbit/s on a 10Gbit port) all the sudden a server in one switch(gig port) starts losing packets to the server in the 10Gb port(the one with traffic), a simple ping command shows lost packets.
Viceversersa as well, and a ping from the 10gbe server to the switch virtual IP also shows dropped packets.
this shouldn't be happening at all, utilization is nowhere near HALF of peak!.
switches are configured default essentially, there's no VLAN, no routing, no qos, flow control enabled globally
i've checked statistics using RMON(sadly PC6224 lacks a simple "show how many BW is used RIGHT NOW in realtime in every port") and all i see are several thousand pause frames on the XG interfaces and GB but nothing alarming(like 20K pause frames in 10 millon packets).
Port errors are also very very low and happen on the gigabit ports mainly.
Also something curious i've found in the address tables is that some ports(specially the 10gbe ones) have a LARGE number of consecutive MAC addresses, that smells like an ARP attack:
| aa:00:00:15:00:04 | 1/xg1 | |||
| VLAN 1 | aa:00:00:15:00:05 | 1/xg1 | ||
| VLAN 1 | aa:00:00:15:00:06 |
Can this be nuking the switches?
how do i prevent that?, i can't use portsec as this is not a "closed" network(more like a large ISP) and every port connects to another switch, since there's no DHCP i can't use dhcp spoofing or anything of the sort...
ideas?, i'm about to turn off flow control globally in all switches to see if that makes a difference
We have a variety of 5448 switches in our network right now, all ports are configured as such (simplified of course, but this is the gist of it):
| 1 | interface range ethernet g(1-48) |
| 2 | switchport trunk native vlan 2 |
| 3 | exit |
| 4 | switchport trunk allowed vlan add 12 |
| 5 | exit |
Our SIP phones plug into the switch, computers plug into the phones. The phones grab a DHCP response which tells them to switch the VOIP traffic to vlan 12 tagged (where they request a dhcp address from a server on that network), the computer sends untagged traffic via vlan 2 on the office network.
I'm trying to configure our 6248 switch to do the same thing, but some of the command structure has changed. Tagged ports can no long have an untagged native vlan on them, so I'm not sure how to achieve the same setup. When I set the ports to general mode, set the pvid to 2 and add port 12, I'm unable to get a dhcp address or do anything even bypassing the phone and plugging directly into the switch with a laptop.
Setting the port to access mode and dropping it into vlan 2 works fine for office traffic via my test laptop, but setting the voice vlan to 12 isn't allowing any tagged traffic to move over vlan 12 (dhcp request is never seen at the dhcp server from the phone).
Any help would be appreciated.
Hi everyone, i need help.
link aggregation its not works. The example shown below use the switches 6224 and 6224f
6224
interface ethernet 1/g23
channel-group 1 mode auto
description 'Ether_Conection'
spanning-tree disable
switchport mode trunk
switchport trunk allowed vlan add 3
switchport trunk allowed vlan add 4
switchport trunk allowed vlan add 5
switchport trunk allowed vlan add 6
switchport trunk allowed vlan add 8
switchport trunk allowed vlan add 9
switchport trunk allowed vlan add 10
switchport trunk allowed vlan add 11
switchport trunk allowed vlan add 12
switchport trunk allowed vlan add 50
interface ethernet 1/g23
channel-group 1 mode auto
description 'Ether_Conection'
spanning-tree disable
switchport mode trunk
switchport trunk allowed vlan add 3
switchport trunk allowed vlan add 4
switchport trunk allowed vlan add 5
switchport trunk allowed vlan add 6
switchport trunk allowed vlan add 8
switchport trunk allowed vlan add 9
switchport trunk allowed vlan add 10
switchport trunk allowed vlan add 11
switchport trunk allowed vlan add 12
switchport trunk allowed vlan add 50
and
6224F
interface ethernet 1/g4
description 'Ether_Conection'
spanning-tree disable
switchport mode trunk
switchport trunk allowed vlan add 3-6,8-12,50-51
exit
!
interface ethernet 1/g5
description 'Ether_Conection'
spanning-tree disable
switchport mode trunk
switchport trunk allowed vlan add 3-6,8-12,50-51
exit
!
I appreciate your help
Thank
I need some help sorting out a routing issue on a 6224 we have configured to act as a transit vlan for one of our locations. The general idea is 8.143 is the transit vlan, 8.144 is our PC LAN, 8.145 will be our VOIP lan.
We installed this switch with our WAN provided last week but had to back out. Seemed traffic arriving at the WAN providers interface to our transit VLAN (172.22.143.254) was not going anywhere. These were the symptoms
1) We could ping from 172.22.144.x to 172.22.145.x and 172.22.143.x
2) We could ping from 172.22.145.x to 172.22.143.x and 172.22.144.x
3) We could ping from 172.22.143.x to 172.22.144.x and 172.22.145.x
4) If I was plugged into the 6224 on with a 143.x address I could ping our remote site at 172.22.8.x no problem but not from 144.x or 145.x
5) From 172.22.8.x I could not ping 144.x or 145.x or 143.1 (I could ping 143.254 which was the WAN providers interface to our switch)
Here is the running config for the switch. Any suggestions would be greatly appreciated:
console>enable
console#show running
!Current Configuration:
!System Description "PowerConnect 6224, 3.3.6.4, VxWorks 6.5"
!System Software Version 3.3.6.4
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 143-145
vlan routing 143 1
vlan routing 144 2
vlan routing 145 3
vlan association subnet 172.22.143.0 255.255.255.0 143
vlan association subnet 172.22.144.0 255.255.255.0 144
vlan association subnet 172.22.145.0 255.255.255.0 145
exit
stack
member 1 1
exit
ip address dhcp
ip routing
ip route 0.0.0.0 0.0.0.0 172.22.143.254
interface vlan 143
name "Transit"
routing ip address 172.22.143.1 255.255.255.0
exit
interface vlan 144
name "TWLAN"
routing ip address 172.22.144.1 255.255.255.0
exit
interface vlan 145
name "VOIP" routing
ip address 172.22.145.1 255.255.255.0
exit
username "admin" password 746f7a78621059d80fdc538acc40cbf2 level 15 encrypted
!
interface ethernet 1/g1
switchport mode general
switchport general allowed vlan add 143
exit
!
interface ethernet 1/g2
switchport mode general
switchport general allowed vlan add 143
exit
!
interface ethernet 1/g3
switchport mode general
switchport general allowed vlan add 144
exit
!
interface ethernet 1/g4
switchport mode general
switchport general allowed vlan add 144
exit
!
interface ethernet 1/g5
switchport mode general
switchport general allowed vlan add 145
exit
!
interface ethernet 1/g6 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g7 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g8 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g9 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g10
switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g11 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g12 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g13 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g14 switchport mode general
switchport general allowed vlan add 145 exit ! interface ethernet 1/g15 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g16 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g17 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g18 switchport mode general switchport general allowed vlan add 145
exit ! interface ethernet 1/g19 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g20 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g21 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g22 switchport mode general switchport general allowed vlan add 145 exit
! interface ethernet 1/g23 switchport mode general switchport general allowed vlan add 145 exit ! interface ethernet 1/g24 switchport mode general switchport general allowed vlan add 145 exit exit
console#
Hi, I am wanting to configure the 3424 over a LAN connection by using this serial Ethernet converter. Does anybody have any experience or recommendations with using such a setup? I assume that I would have to install some kind of COM port drivers on my computer that the converter can use.
Hi, I havea problem with theconfiguration of anLACPport channel
Force10: (System image file is "flash://FTOS-CB-8.4.2.6.bin)
interface Port-channel 2
no ip address
switchport
no shutdown
interface GigabitEthernet 7/45
no ip address
!
port-channel-protocol LACP
port-channel 2 mode active
no shutdown
interface GigabitEthernet 7/47
no ip address
!
port-channel-protocol LACP
port-channel 2 mode active
no shutdown
interface Vlan 10
description VLAN10
ip address xxx.xxx.xxx.xxx
tagged GigabitEthernet 2/22
untagged GigabitEthernet 0/0-47
untagged GigabitEthernet 1/1-47
untagged GigabitEthernet 2/0-21,23-47
untagged GigabitEthernet 3/0-47
untagged GigabitEthernet 4/0-27,34-43
untagged TenGigabitEthernet 4/44-45
untagged TenGigabitEthernet 6/4-5
untagged GigabitEthernet 7/0-44,46
untagged Port-channel 1-2,10-11
no shutdown
Cisco 6509 (CATOS)
#channelprotocol
set channelprotocol lacp 1
set channelprotocol lacp 2
set channelprotocol lacp 3
set channelprotocol lacp 4
set channelprotocol lacp 5
set channelprotocol lacp 6
set channelprotocol lacp 7
set channelprotocol lacp 8
!
#port channel
set port lacp-channel 5/1-8 888
!
# default port status is enable
!
!
#module 1 : 48-port 10/100/1000BaseT Ethernet
!
#module 2 : 48-port 10/100/1000BaseT Ethernet
!
#module 3 : 48-port 10/100/1000BaseT Ethernet
!
#module 4 : 48-port 10/100/1000BaseT Ethernet
!
#module 5 : 9-port 1000BaseX Supervisor
set trunk 5/1 desirable dot1q 1-4094
set trunk 5/2 desirable dot1q 1-4094
set trunk 5/3 desirable dot1q 1-4094
set trunk 5/4 desirable dot1q 1-4094
set trunk 5/5 desirable dot1q 1-4094
set trunk 5/6 desirable dot1q 1-4094
set trunk 5/7 desirable dot1q 1-4094
set trunk 5/8 desirable dot1q 1-4094
set port lacp-channel 5/1-8 mode active
!
#module 6 : 9-port 1000BaseX Supervisor
!
#module 7 : 48-port 10/100/1000BaseT Ethernet
!
#module 8 : 16-port 1000BaseX Ethernet
!
#module 9 empty
!
#module 15 empty
!
#module 16 empty
end
Output on Force 10:
slssw-01-01#11w2d15h: %RPM0-P:CP %IFMGR-5-OSTATE_UP:
Changed interface state to up: Gi 7/45
11w2d15h: %RPM0-P:CP %LACP-5-PORT-GROUPED: PortChannel-050-Grouped: Interface
Gi 7/45 joined port-channel 50
11w2d15h: %RPM0-P:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Po 50
11w2d15h: %RPM0-P:CP %LACP-5-PORT-UNGROUPED: PortChannel-050-Ungrouped:
Interface Gi 7/45 exited port-channel 50
11w2d15h: %RPM0-P:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Po 50
11w2d15h: %RPM0-P:CP %LACP-5-PORT-GROUPED: PortChannel-050-Grouped: Interface
Gi 7/45 joined port-channel 50
I have a recently deployed stack of 3 5548P switches. I'm having some issues when trying to supply power to Ruckus 7372 wireless APs: in some ports, the APs will power on, and transit data exactly as expected. In other ports, the APs never show power.
In most of the ports that will not power a Ruckus AP, I can power a Meraki MR12. Except for one tested port: where the experience is that the MR12 power light does a very rapid flicker, and none of the port's lights on the switch light up. (Switches are in production, not all ports can be tested for PoE)
This power problem was first observed under firmware 4.0.1.11, and continues through an upgrade to 4.1.0.8.
I have carefully compared PoE configuration between working and non-working ports, and see no difference. No Power Limit threshold that could be exceeded, no port locking, Green Ethernet Config is the same.
The only PoE devices attached to the stack are 2 other Ruckus 7372s, each pulling 3Watts, from different switches. This is not a total power budget problem.
With a 7273 plugged into a port, I can refresh System: General PoE: <that port> and see the Invalid Signature Counter steadily increasing.
Can anyone provide some troubleshooting ideas to help my 5548 and Ruckus gear get along properly?
POE52024M Web smart managed PoE switch which is based on new generation of high performance BROADCOM IC is carrier-class layer 2 management switch with 2 gigabit uplink interface. It can increase the extensibility and manageability for customers. It also has excellent light protection function.
The device has rich management method mode including SNMP, WEB, TELENET, CLI. Also has the function of QOS, RSETMSTP, IGMP,etc, RADIUS, 802.1X authentication make the network secure and reliable. It can be applied more convenient by conforming to IEEE802.3af and support Green PoE saving power mode. Uses can configure power supply of PoE port via SNMP, WEB, TELENET, CLI
�
does anyone know where i can find the info for my Dell PowerConnect 6224 and if it supports jumbo frames.
I am trying to get the most out of my switch and it seems when I set my device to jumbo frames MTU 9000 it doesnt work right.
Hi,
I have 4 6248 units. connected according to page 5 here :
http://www.dell.com/downloads/global/products/pwcnt/en/pwcnt_stacking_switches.pdf
the manual states that the units has to be brought up in a certain order master be turned on first and then the rest of the units .
what happens when I have power failure ?
from the little experience I had, it took several times of restarts to the units until all the network was reachable (sometimes other units took over as master etc etc.)
Thank you for any clarification.
Nedz.
Hi,
I'm running a stack of 6224/6248 switches in a windows 2008R2 environment. They are configured to control access through 802.1 (auto-mode) and to get the authentication information, including vlan assignment from my primary NPS server (RADIUS). Everything seemed to be running ok at first, but at random times, clients are dropped and are no longer able to access the network. However, when I look at the port status at that time, the port still shows up as 'authenticated'; however no packets can flow. Sometimes it helps to disable and enable the network adapter or to physically disconnect the cable. However, that is not a good solution for 100+ PCs
I've checked the NPS logs, but everything seems fine there; it indicates that users are granted access and put into the right VLAN. Looking at the remote syslog of the switch stack, I get entries like these throughout the day :
8 192.168.100.100-1 TRAPMGR[152722416]: traputil.c(611) 4735 %% Link on 6/0/16 is failed
2012-01-06 09:53:31 Local7.Notice 192.168.100.100 JAN 06 09:53:18 192.168.100.100-1 TRAPMGR[152722416]: traputil.c(611) 4736 %% 6/0/16 is transitioned from the Forwarding state to the Blocking state in instance 0
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4737 %% Notification(2) received for entry(4400) not present
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4738 %% Notification(2) received for entry(4416) not present
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4739 %% Notification(2) received for entry(4432) not present
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4740 %% Notification(2) received for entry(4448) not present
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4741 %% Notification(2) received for entry(4544) not present
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4742 %% Notification(2) received for entry(4560) not present
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4743 %% Notification(2) received for entry(4656) not present
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4744 %% Notification(2) received for entry(4800) not present
2012-01-06 09:53:31 Local7.Error 192.168.100.100 JAN 06 09:53:19 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(853) 4745 %% Notification(2) received for entry(4816) not present
2012-01-06 09:53:35 Local7.Notice 192.168.100.100 JAN 06 09:53:22 192.168.100.100-1 TRAPMGR[152722416]: traputil.c(611) 4746 %% 6/0/16 status is Unauthorized
2012-01-06 09:53:35 Local7.Notice 192.168.100.100 JAN 06 09:53:22 192.168.100.100-1 TRAPMGR[152722416]: traputil.c(611) 4747 %% Link Up: 6/0/16
At other times, the log is filled with entries like these
0 JAN 06 09:53:44 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(827) 4780 %% Notification(1) received for entry(4432) already present
2012-01-06 09:53:56 Local7.Error 192.168.100.100 JAN 06 09:53:44 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(827) 4781 %% Notification(1) received for entry(4448) already present
2012-01-06 09:53:56 Local7.Error 192.168.100.100 JAN 06 09:53:44 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(827) 4782 %% Notification(1) received for entry(4544) already present
2012-01-06 09:53:56 Local7.Error 192.168.100.100 JAN 06 09:53:44 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(827) 4783 %% Notification(1) received for entry(4560) already present
2012-01-06 09:53:56 Local7.Error 192.168.100.100 JAN 06 09:53:44 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(827) 4784 %% Notification(1) received for entry(4656) already present
2012-01-06 09:53:56 Local7.Error 192.168.100.100 JAN 06 09:53:44 192.168.100.100-6 DOT1X[140205616]: dot1x_nsf.c(827) 4785 %% Notification(1) received for entry(4800) already present
Does anyone have any idea what could be going wrong ? As I said, the state of the port remains 'authenticated' in the switch. I've tried raising the re-authentication period to no avail.
Thanks
Regards,
Peter
How do I copy the config of one 6224 and upload this config to another 6224. NOT using command line.
Hi there!
i've two different stacks, in two different location
Location01
STack01 -> with dell switched PC8164-01 and PC8164-02
Location02
STack02 -> with dell switched PC8164-03 and PC8164-04
On all of the switches, i use the same ports for stacking
Now, suppose this scenario:
If the switch PC8164-02, that is member of stack01 located in Location01 is damaged, and i remove switch PC8164-04 from location02, and plug it to location01, will it be function normally, and receive configuration from other switch in stack PC8164-01, and it will be a member???
Regards!