Quantcast
Channel: PowerConnect Forum - Recent Threads
Viewing all 2954 articles
Browse latest View live
↧

Interface PC8024 with existing voice VLAN (100) on HP 2910 switches

April 24, 2015, 5:55 am
$
0
0

We've added our first Dell PowerConnect 8024 switch to an existing network consisting of HP 2910 switches.  We have only 2 VLANS configured:  the default (1) and voice (100).  On the HP switches all ports in the default VLAN are set to "untagged" and all ports in the voice VLAN are set to "tagged".

I need to configure the PC8024 to coexist with the existing network so that the Mitel phones can communicate.  We are not familiar with the PC8024 switch, are evaluating it as a potential solution for upgrading our backbone and DR subnet from 1Gb to 10Gb.  For the backbone we need the voice traffic to be handled properly, so we need to configure the 8024 to work with the existing voice VLAN.

What VLAN configuration settings do we need on the PC8024 to coexist with the existing network configuration for the voice (100) VLAN on the HP switches?

↧
Search

Transfer Ownership - Do Not Have Previous Owner's Information

April 24, 2015, 6:26 am
$
0
0

I'm trying to transfer the ownership of my company's Dell Powerconnect 2848. It was purchased 3 years ago via Ebay and we don't have any information regarding the previous owner (other than that the company was located in the UK).


How do we transfer ownership as the request form requires the company name? This is urgent for us as it restricts the tech support options we have available for the switch. We'd prefer not to have to call the UK tech support line.

Thanks for your help.

↧
↧

VLAN 3024 Switches

April 24, 2015, 9:34 am
$
0
0

Hi, Would someone be able to help a Switch newbie  please :-)

 

I am trying to VLAN and stack a pair of Dell N3000 series switches.

 

I have a Dell 3024F switch which I have stacked together with a 3024 switch using two stacking cables.

The stacking cables are arranged:

 

Cable 1: From 3024F Port 2 to 3024 Port 1

Cable 2: From 3024F Port 1 to 3024 Port 2

 

This seems to work and the two switches are reporting that they are stacked as one unit.

 

Next I needed to split them into 2 VLANs. (The site does not have enough rack space for separate switches in the rack room!)

So I created 2 VLANS:

 

VLAN ID = 2, Name: Thin Client Primary

VLAN ID = 3, Name: Cluster Primary

 

Now I needed to assign the ports, therefore I edited each port and changed it from "Access" to "General".

 

For the 3024F, I assigned Ports Gi1 to Gi12 to VLAN ID 2, by placing a "T" in the relevant box under each Port ID.I repeated this for ports Gi13 to Gi24 assigning them to VLAN ID 3.

I also assigned the Te1 port to VLAN 2 and the Te2 port to VLAN 3, so that I can run a fibre which would be dedicated to a VLAN.

 

For the 3024 switch, I repeated the above.

 

Therefore I should now have a stacked switch that has half its ports on 1 VLAN and half its ports on another. The Fibre ports are also segregated - meaning I can run independent fibres that are dedicated to a VLAN.

 

At the end of this two fibres I have another 3024 witch which I have setup in exactly the same way - so that I have 2 VLANs (ID 2 and 3).

 

This should mean that I now have two independent networks - running over two fibres.

 

Is this a correct configuration - is there a better way?

 

Many thanks for taking the time to read my question - much appreciated.

↧

X-Series X1018 Launch date, information and price?

April 26, 2015, 8:13 am
$
0
0

Didn't know where else to put this. Clearly Dell has branded the X-Series as a non-PowerConnect switch series.

Where can I find more information on them? Is it a Dell manufactured device or is it a re-branded switch? Is it going to be decent and what is the pricepoint going to be?


Thanks.

↧

Configure N4032 PFC for RoCE

April 27, 2015, 7:29 am
$
0
0

I am setting up a SMB Direct with Emulex OCE14102 RDMA Nics and have a N4032.  Technically all you need is DCB and PFC for RoCE to work on the switch.   How do I setup the N4032 to work with this scenario.

Thanks,

John 

↧
↧

Dell Networking N2048P Switch not Logging

April 24, 2015, 2:26 pm
$
0
0

Hello!  On my older Dell switches, the PowerConnect 5548P for example, I was able to telnet to the switch and view when a device was unplugged.  We use this for finding where various devices are plugged into the switch.  For example the switch displays:

29-Oct-2006 02:15:56 %LINK-W-Down:  gi1/0/33
29-Oct-2006 02:15:59 %LINK-I-Up:  gi1/0/33
29-Oct-2006 02:16:29 %STP-W-PORTSTATUS: gi1/0/33: STP status Forwarding

However, on the N2048P I am not able to see these messages.  I have tried several commands with no luck.  Is there a way to see similar messages in the telnet console?  These are the commands we tried:

At the Config Prompt:
 logging on
 logging buffered debugging
 logging monitor

At the Enable Prompt:
 terminal monitor

We have version 6.2.0.5 installed on the switch.

Thank you!

 

↧

Received ARP Request on interface Vl1 with bad target IP address - Ruckus Wireless

April 27, 2015, 9:20 am
$
0
0

Dear Dell Support Team,

We have installed our new Dell Networking N2048P with a very simple configuration: only add a new VLANs and configured all the ports as trunked. In this ports we have connected a Ruckus wireless AP that works well. But in RAM Log we have a lot of messages like this (all the IPs are from Ruckus AP):

WarningApr 27 00:03:22ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.116.66, sender MAC is 6c:aa:b3:2e:a6:d0.
WarningApr 27 00:02:06ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.116.66, sender MAC is 6c:aa:b3:2e:a6:d0.
WarningApr 27 00:02:05ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.93.119, sender MAC is 8c:0c:90:08:92:00.
WarningApr 27 00:01:27ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.221.64, sender MAC is 6c:aa:b3:30:6b:30.
WarningApr 26 21:06:38ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.212.41, sender MAC is 6c:aa:b3:30:98:00.
WarningApr 26 18:53:15ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.15.18, sender MAC is 58:93:96:1c:5f:00.
WarningApr 26 18:53:15ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.99.133, sender MAC is 8c:0c:90:0b:81:10.
WarningApr 26 18:52:33ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.88.177, sender MAC is 58:93:96:1c:a3:d0.
WarningApr 26 13:52:07ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.0.194, sender MAC is 8c:0c:90:08:94:30.
WarningApr 26 13:52:06ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.9.166, sender MAC is 8c:0c:90:08:f2:80.
WarningApr 26 13:52:04ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.144.156, sender MAC is 8c:0c:90:0b:0c:40.
WarningApr 26 13:51:58ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.245.38, sender MAC is 8c:0c:90:08:38:e0.
WarningApr 26 13:51:58ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.15.18, sender MAC is 58:93:96:1c:5f:00.
WarningApr 26 13:51:54ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.144.156, sender MAC is 8c:0c:90:0b:0c:40.
WarningApr 26 13:51:53ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.63.215, sender MAC is 8c:0c:90:0a:ae:80.
WarningApr 26 13:51:49ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.66.140, sender MAC is 8c:0c:90:0b:0a:d0.
WarningApr 26 13:51:18ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.116.66, sender MAC is 6c:aa:b3:2e:a6:d0.
WarningApr 26 13:51:16ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.93.119, sender MAC is 8c:0c:90:08:92:00.
WarningApr 26 13:50:38ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.221.64, sender MAC is 6c:aa:b3:30:6b:30.
WarningApr 26 04:57:20ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.202.115, sender MAC is 8c:0c:90:08:96:20.
WarningApr 26 04:57:20ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.15.18, sender MAC is 58:93:96:1c:5f:00.
WarningApr 26 04:57:19ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.63.50, sender MAC is 8c:0c:90:0a:76:10.
WarningApr 26 04:57:15ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.93.202, sender MAC is 8c:0c:90:0a:d4:10.
WarningApr 26 00:16:50ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.116.66, sender MAC is 6c:aa:b3:2e:a6:d0.
WarningApr 26 00:16:02ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.221.64, sender MAC is 6c:aa:b3:30:6b:30.
WarningApr 26 00:14:23ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.95.16, sender MAC is 6c:aa:b3:2c:81:f0.
WarningApr 26 00:14:16ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.116.66, sender MAC is 6c:aa:b3:2e:a6:d0.
WarningApr 26 00:13:17ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.221.64, sender MAC is 6c:aa:b3:30:6b:30.
WarningApr 26 00:11:41ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.6.161, sender MAC is 8c:0c:90:07:c2:b0.
WarningApr 26 00:11:26ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.103.130, sender MAC is 58:93:96:1c:a4:80.
WarningApr 26 00:11:25ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.251.135, sender MAC is 8c:0c:90:0a:cc:a0.
WarningApr 26 00:11:24ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.47.188, sender MAC is 8c:0c:90:0b:1c:10.
WarningApr 26 00:11:16ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.33.61, sender MAC is 8c:0c:90:07:c3:10.
WarningApr 26 00:11:15ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.126.197, sender MAC is 8c:0c:90:0b:1a:80.
WarningApr 26 00:11:12ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.63.213, sender MAC is 8c:0c:90:0b:7d:b0.
WarningApr 26 00:11:08ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.54.112, sender MAC is 8c:0c:90:09:48:90.
WarningApr 26 00:11:06ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.236.179, sender MAC is 24:c9:a1:12:ad:a0.
WarningApr 26 00:11:05ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.202.115, sender MAC is 8c:0c:90:08:96:20.
WarningApr 26 00:11:03ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.106.136, sender MAC is 2c:e6:cc:39:8b:20.
WarningApr 26 00:11:02ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.241.125, sender MAC is 8c:0c:90:0b:1c:50.
WarningApr 26 00:11:01ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.57.199, sender MAC is 8c:0c:90:08:3e:f0.
WarningApr 26 00:11:00ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.124.96, sender MAC is 54:3d:37:37:95:e0.
WarningApr 26 00:10:57ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.241.125, sender MAC is 8c:0c:90:0b:1c:50.
WarningApr 26 00:10:56ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.142.56, sender MAC is 8c:0c:90:08:96:60.
WarningApr 26 00:10:55ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.127.24, sender MAC is 8c:0c:90:0a:af:40.
WarningApr 26 00:10:46ARPReceived ARP Request on interface Vl1 with bad target IP address 255.255.255.255. Sender IP is 10.10.93.119, sender MAC is 8c:0c:90:08:92:00.

These messages appears when we restart the switch or when connect or restart an AP. We also have another 2048P with Ruckus AP and we have the same warning. I attached the switch configuration file. Can anyone help?

Thanks in advance,

René

↧

N2048P ECC error

April 28, 2015, 1:28 am
$
0
0

We just got 10 N2048P and we were going to try one of them in the current enviroment before deploying all of them, unfortuntaly we got those errors in the log:

Apr 28 09:58:08 SW-SPES-06-1 DRIVER[bcmDPC]: broad_hpc_drv.c(4428) 366 %% Unit: 0 #012 CDC RX FIFO entry 44 double-bit ECC error
Apr 28 09:58:08 SW-SPES-06-1 DRIVER[bcmDPC]: broad_hpc_drv.c(4428) 367 %% Unit: 0 #012 CDC RX FIFO table 0 entry 44 ECC error
Apr 28 09:59:50 SW-SPES-06-1 DRIVER[bcmDPC]: broad_hpc_drv.c(4428) 369 %% Unit: 0 #012 CDC RX FIFO entry 28 double-bit ECC error

our network monitor says that some of the devices attached are losing pings every now and then (even if we can't see any packet loss with a manual ping) and it gets this error from the switch via SNMP:

CRIT - [Unit: 1 Slot: 0 Port: 22 Gigabit - Level] (up) MAC: f8:b1:56:62:b2:fa, 10MBit/s, in: 57.19B/s, in-errors: 2.78%(!!) = 0.1, out: 4.68kB/s

Note that the device attached to the port 22 is NOT one that gave us warnings about pings

I've seen here that someone got the same problem on the same switch and it could be related to a memory problem, I upgraded the firmware from 6.1.0.6 to 6.2.0.5 but no luck, I decided to try another switch but I got the same problem (i copied the configuration), so it seems that the problem is not really related to the switch.

Before the N2048P we were using a small Netgear Prosafe FS116P without any apparent problem (it is unmanaged tho), any though on what it could be or on how can it debug the problem?

↧
Search

N4064 LAG not working

April 28, 2015, 7:03 am
$
0
0

we  moving from old PC6248 switch to new N4064 switch I got everything else is working fine. we have 2 LAG setup for our backup server and file deduplication box. after copy almost all setting from old switch to new switch I can't get to my backup server or deduplication box. I can't even ping. can some one help?

↧
↧

N Series Deployment Question

April 28, 2015, 7:49 am
$
0
0

We've recently purchased 3 N3000 series switches to replace our existing and aging Adtran switches.

I've configured them following the guides and the VOIP LLDP config guide. We have mitel phones with PCs connecting into them. I set up the stack initially in my office and plugged the port into an adtran that isn't setting the phones in the correct vlan. With the LLDP config the phone found the correct vlan and the laptop plugged into the phone found its correct vlan.

I unplugged the cable from the adtran switch and gave the data vlan the same IP as the current layer 3 Adtran and began planning the cutover however I ran into an issue and I need some guidance.

I can plug two laptops into the stack and they both pull IPs 2.61 and 2.62  and they can ping the vlan IP 2.11 and the voice vlan  IP 3.1 but they cannot ping eachother? Is that normal behavior or am I missing something?

↧

S4810 FTOS release note

April 28, 2015, 6:55 pm
$
0
0

Anyone has S4810 FTOS release note ? 

thanks

↧

Dell M8428-k support

April 29, 2015, 3:29 am
$
0
0

I have an Dell M8428-k plugged in to my m1000e chassis. I have 5 blade servers with

Fabric  AYes10 GbE KRBRCM 10GbE 2P 57810s bNDC

Should I be able to use these to get full 10gb? As at the moment my switches are only reporting 1gb speeds.

↧

dell switch 8024F - Front left LED is flashing red - no connect terminal

April 29, 2015, 6:38 am
$
0
0

Hello,
I have a DELL 8024F switch not connected console me.
The console cable is correct.
The LEDs on the switch are as follows:
LED right power source is green.
Left power source does not exist.
LED fans are green.

Front left LED is flashing red.

What can happen?

I have inserted several SFP + and are led as if they were not inserted.
I get the feeling as if you did not initiate the boot process.
Any suggestions?
regards

↧
↧

Dell PowerConnect 8024 - 802.3ad (Dynamic LACP) across 2 switches?

April 29, 2015, 8:18 am
$
0
0

We are evaluating the use of Dell PC8024 switches to upgrade our backbone to 10GbE.  We're currently using HP ProLiant servers with multiple NICs teamed.  The HP servers support 802.3ad dynamic link aggregation (LACP).  

Does the PC8024 switch support dynamic link aggregation across 2 different switches, or does it have to be on the same switch?

As a comparison, the HP2910 switches cannot support dynamic link aggregation (LACP) across multiple switches, while the HP2920 switches can.  So some can, some cannot.  Need to understand the capability of the PC8024 switch.

Thanks!

--Terry

↧

Is it possible to update firmware on a PowerConnect 35xx not using a server or network connection?

April 29, 2015, 12:53 pm
↧
Search

Low throughput in network

April 29, 2015, 1:48 pm
$
0
0

Hi In my company we have a 3500 Sonicwall which is then connected too Dell5548 power connect, and which is further connected to few 5548 and two 6248.

Users are getting low speed. I don't see any Packet drop on sonicwall or switch.

We have a 100 mb conection from ISP but users are getting around 30-40 and sometimes even lower then that.

Now I am unable to understand how to identify the segment which is bottleneck. Is it firewall or switch.

Please suggest me a way to figure this out as this is really critical.

↧

QOS/COS OIDs for Dell PowerConnect 5548

April 29, 2015, 3:17 pm
$
0
0

Hello,

Can anyone tell me the QOS OID's for a Dell PowerConnect 5548 series switch?

Thank you!

↧
↧

N2048P adding OUI

April 29, 2015, 7:29 pm
$
0
0

Hi,

I've stacked two N2048P switches and created and added a VLAN 10 to all ports. I have assigned the VoiceVLAN to VLAN 10.

I'm trying to add the Polycom OUI so the Polycom phones are automatically picked up and assigned to VLAN 10.

I've done this before on my 3524P devices easily via web console as there is an option specifically for this. There is no such option in the web interface for the N2048P though so I'm attempting to add it via CLI but get an error.

SW-STACK1(config)# voice vlan oui-table add 0004f2 PolycomTIPT

it puts the error marker at the "O" in "oui".

If anyone could point me in the right direction I'd really appreciate it. 

Thanks,

David.

↧

How to manage dell-2816 switch from remote network..?

April 30, 2015, 12:02 am
$
0
0

Hi,

According to below diagram how can i manage the dell-2816 switch from other network. It has management ip only worked on default vlan and default vlan is not editable also not routed ,we can only access the switch to connect laptop directly to switch port and if the port has default-vlan id-1 .

switch to switch trunk doing problem but when using the pvid as a access vlan ID then trunk is working between dell to juniper hope so cisco also work. But the major issue is remote manageability and also snmp , If switch does not getting ping from remotely then how the snmp will work ..?

Thanks

Mamdud

mamdud@biometrics-bd.com

↧

How to manage dell-2816 switch from remote network..?

April 30, 2015, 12:09 am
$
0
0

Hi,

According to below diagram how can i manage the dell-2816 switch from other network. It has management ip only worked on default vlan and default vlan is not editable also not routed ,we can only access the switch to connect laptop directly to switch port and if the port has default-vlan id-1 .

switch to switch trunk doing problem but when using the pvid as a access vlan ID then trunk is working between dell to juniper hope so cisco also work. But the major issue is remote manageability and also snmp , If switch does not getting ping from remotely then how the snmp will work ..?

Thanks

Mamdud

<ADMIN NOTE: Email id removed per privacy policy>

↧
Viewing all 2954 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>