Dell Powerconnect 6224 Default VLAN VLAN reference and management

Similar Questions

• How to access the management of VLANs with a different virtual LAN (Dell powerconnect 6224)

  Hello

  DELL powerconnect 6224 reference.

  I want to access the management of a different VIRTUAL LAN VLAN.

  The management of VLANS is 100 of VLAN. not the routing

  My computer is vlan 60 (192.168.60.10) and I want to connect via ssh or http (192.168.100.1) to manage my switch.

  Thank you for your help on the command line

  The management of VLANS on the 6224 is not routable. So, you will not be able to access VLAN 100 from any other VLAN. However, you can manage the switch from other VLAN IP addresses. So if VLAN 60 has an IP of 192.168.60.1 you can http and ssh to it. And if the VLAN routing is enabled you have access to 192.168.60.1 on the other VLAN.

  See you soon

• How Reboot/restart Dell Powerconnect 6224

  Hello

  My company has 2 powerconnect 6224, 1 is the master and 1 slave, do I know how could restart/reboot my switch in the GUI?

  Can I use the cli to restart/reboot command and what is the command line.

  Thank you

  Using the CLI to recharge the battery, you must use the # reload command. You can add the number of the switch in the command reload members of chimneys. charge # 1, # reload 2.

  You can also use the command console (config-battery) #initiate failover. This command forces a warm restart of the battery. The unit of backup succeeds the new management unit without clear status of material on the stack members. The original management unit restarts.

  In the graphical user interface, you can reboot the switch with entering the system > general > reset. You can also start a recovery using System > stacking > NSF summary. Initiate failover will begin a warm reboot of the switch.

• Proxy-arp or local proxy arp? Reference Dell Powerconnect 6224

  We need allow some customers to resolve the mac address of a server that is located in a different range of addresses, VLAN and IP.

  I thought that the addition of the ip proxy-arp interface command vlan should do the job, but this command seems to be activated by default according to the reference guide, after that I tried to add the command he always show up on a running show. Which confirmed my thoughts. While I was looking for the solution that I saw another command that does not appear in the cli reference guide: local-proxy-arp ip. But since I'm not sure of what will make this command I am careful to hit just the command on the interface VLAN.

  How others send their arp on powerconnect 6224 requests?

  After reading my own source again, I realized that the thing that I want is not possible. It goes beyond the need to divide the network into segments. If all the query arp is transferred to other networks, there is a benefit less: you want to limit the broadcast domain.

  Static ARP is the thing I'm going to need to be implemented to solve this problem.

  Thanks for the clarification anyway.

• Reference Dell powerconnect 5524 cannot ping between coelio and trunk port

  Hello...

  We set up a new switch of 5524 I untagged on vlan 20 and access ports where vlan 20 I allowed. I created a computer on the access port on the same trunk port ip net... cant ping beween them. I'm no expert of switch, so I wonder what I missed. I did the same thing on a dell old 3524 and it works directly...

  Here's the port config I tried to do a ping beween is 6 and 10 ports

  (Another thing, how how to remove):

  switchport mode trunk
  switchport access vlan none)

  Any help would be greatly appreciated!

  interface vlan 1
  IP 88.131.90.252 255.255.255.240
  !
  interface vlan 5
  the name 'SCE CJA'
  !
  interface vlan 6
  the name "out of Tele2.
  !
  interface vlan 7
  name "Outside Telenor"
  !
  interface vlan 8
  name "TDC Multivrf"
  !
  interface vlan 20
  TDC-CISCO-LAN name
  !
  [0mMore: , quit: q or CTRL + Z, one line: interface vlan 21]
  the name "FW inside."
  !
  interface vlan 99
  name «FW sync»
  !
  gigabitethernet1/0/1 interface
  Description CPE1
  switchport access vlan 5
  !
  interface gigabitethernet1/0/2
  Description CPE2
  switchport access vlan 5
  !
  interface gigabitethernet1/0/3
  Df description
  spanning tree portfast
  switchport mode trunk
  switchport access vlan no
  !
  interface gigabitethernet1/0/4
  Description Oupps-cb2
  [0mMore: , quit: q or CTRL + Z, a single line: spanning tree portfast]
  switchport mode trunk
  switchport access vlan no
  !
  interface gigabitethernet1/0/5
  Upp-ccm1 description
  spanning tree portfast
  switchport access vlan 20
  !
  interface gigabitethernet1/0/6
  Oupps-ccm2 description
  spanning tree portfast
  switchport access vlan 20
  !
  interface gigabitethernet1/0/7
  Tdc-multivrf1 description
  switchport access vlan 8
  !
  interface gigabitethernet1/0/8
  TDC-multivrf2 description
  switchport access vlan 8
  !
  [0mMore: , quit: q or CTRL + Z, one line: interface gigabitethernet1/0/9]
  Description Oupps-cb-tq03
  spanning tree portfast
  switchport mode trunk
  !
  interface gigabitethernet1/0/10
  Description Oupps-cb-tq04
  spanning tree portfast
  switchport mode trunk
  !
  interface gigabitethernet1/0/11
  Tele2-outside description
  switchport access vlan 6
  !
  interface gigabitethernet1/0/12
  Tele2-outside description
  switchport access vlan 6
  !
  interface gigabitethernet1/0/13
  Telenor-outside description
  switchport access vlan 7
  !
  [0mMore: , quit: q or CTRL + Z, one line: interface gigabitethernet1/0/14]
  Telenor-outside description
  switchport access vlan 7
  !
  interface gigabitethernet1/0/15
  Description Word-Oupps-fw-tq01-inside
  switchport mode trunk
  !
  interface gigabitethernet1/0/16
  Description Word-Oupps-fw-tq02-inside
  switchport mode trunk
  !
  interface gigabitethernet1/0/17
  FW-sync description
  switchport access vlan 99
  !
  interface gigabitethernet1/0/18
  FW-sync description
  switchport access vlan 99
  !
  interface gigabitethernet1/0/19
  Description Word-Oupps-fw-tq01-outside
  [0mMore: , quit: q or CTRL + Z, a single line: switchport mode trunk]
  !
  interface gigabitethernet1/0/20
  Description Word-Oupps-fw-tq02-outside
  switchport mode trunk
  !
  interface gigabitethernet1/0/22
  FW-Sync description
  switchport access vlan 99
  !
  interface gigabitethernet1/0/23
  Description Word-Oupps-FW-tq01-outside
  192.168.11.1 IP address 255.255.255.0
  switchport mode trunk
  !
  interface gigabitethernet1/0/24
  Description Word-AIN-LAN-SW
  switchport access vlan 20
  !
  IP route 0.0.0.0 0.0.0.0 88.131.90.241

  [0mMore: , quit: q or CTRL + Z, a single line:]

  Information of VLAN

  The name of the VLAN Tag Ports Ports unmarked Type permission
  ---- ------------ ------------------ ------------------ --------- -------------
  1 1 article gi1/0/3-4, default required
  Article gi1/0/9-10
  item in gi1/0/15-16,
  item in gi1/0/19-21,
  item in gi1/0/23,
  item in gi1/0/25-48,
  TE1/0/1-2.
  GI2/0/1-48.
  TE2/0/1-2.
  IG3/0/1-48.
  TE3/0/1-2.
  IG4/0/1-48.
  TE4/0/1-2.
  IG5/0/1-48.
  TE5/0/1-2.
  GI6/0/1-48.
  TE6/0/1-2.
  gi7/0/1-48.
  TE7/0/1-2.
  gi8/0/1-48.
  TE8/0/1-2, m 1-32
  5 CPE TDC article gi1/0/3-4, item in gi1/0/1-2 permanent required
  [0mMore: , quit: q or CTRL + Z, one line: article gi1/0/9-10]
  item in gi1/0/15-16,
  item in gi1/0/19-20,
  item in gi1/0/23
  6 outside section gi1/0/3-4, item in gi1/0/11-12 permanent required
  Tele2 item in gi1/0/9-10,
  item in gi1/0/15-16,
  item in gi1/0/19-20,
  item in gi1/0/23
  7 outside article gi1/0/3-4, item in gi1/0/13-14 required permanent
  Telenor item in gi1/0/9-10,
  item in gi1/0/15-16,
  item in gi1/0/19-20,
  item in gi1/0/23
  8 TDC Multivrf item in gi1/0/3-4, item in gi1/0/7-8 permanent required
  Article gi1/0/9-10
  item in gi1/0/15-16,
  item in gi1/0/19-20,
  item in gi1/0/23
  TDC-CISCO-LA 20, article gi1/0/3-4, item in gi1/0/5-6, item in gi1/0/24 required permanent
  N item in gi1/0/9-10,
  item in gi1/0/15-16,
  [0mMore: , quit: q or CTRL + Z, one line: item in gi1/0/19-20,]
  item in gi1/0/23

  In safe mode the PVID is 1 VLAN by default. You can do this by entering the command #switchport trunk vlan native {number of vlan}. If Cisco is configured to accept and send the marked packets and has an IP address in the subnet of VLAN 20, it should be able to communicate with other devices in VLAN 20.

• Reference Dell PowerConnect 2848 OID for CPU time and memory

  Hi all

  This is my first post in this forum. I searched all the messages that can solve my problems, but I could not find so if there is already an existing post and I couldn't find it please guide me to it.

  My case is. We have a few Dell PowerConnect 28xx switches in our network. We want to monitor things like the CPU, the temperature, the use of the RAM usage. We use Solarwinds IpMonitor monitoring tool. I downloaded the MIB, I could find the download of Firmware from Dell drivers and downloads page. I went through the entire MIB, but I couldn't find an OID for the foregoing.

  So if anyone can help me please what OID is used for usage of CPU and RAM temperature it will really help me.

  Please let us know in case we need more information on my side.

  Thank you

  Frank Moreau

  I did use SNMP on the 28xx but here are some various sensor OID, I used for the N-series, as well as some older models Powerconnect.  I don't know if they will work for the 2xxx, but you can try one or two and see if they work.

  N - Series (FW 6.2 and later versions) temperature OID
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.5.1.0
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.5.1.1

  62xx (3.0.x.x firmware or later-, some may also work with 2.x firmware)
  Temperature OID
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.2
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.3
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.8.1.4

  Are the OID to use CPU for N-Series switches
  1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.1 (total free memory)
  1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.2 (total memory)
  1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.3 (table for the following...)
  1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.3.1.1 (index)
  1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.3.1.2 (name of the process using CPU)
  1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.3.1.2 (% CPU used by the corresponding process)
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.4.0 (cumulation of all the activity of the CPU)
  1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.9 (CPU utilization shows 5 s, 60 s and 300s).

  OIDs memory
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.1
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.1.4.2
  Power supply OID
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.7.1.2
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.7.1.3
  OIDs of fan
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.2
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.3
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.4
  . 1.3.6.1.4.1.674.10895.5000.2.6132.1.1.43.1.6.1.5

  35xx (2.0.x.x or later firmware)
  Temperature OID
  . 1.3.6.1.4.1.89.53.15.1.9
  . 1.3.6.1.4.1.89.53.15.1.10
  OIDs of CPU
  . 1.3.6.1.4.1.89.1.6
  . 1.3.6.1.4.1.89.1.7
  . 1.3.6.1.4.1.89.1.8
  . 1.3.6.1.4.1.89.1.9
  OIDs memory
  . 1.3.6.1.4.1.89.29.11.1
  . 1.3.6.1.4.1.89.29.11.2
  P.S. The OID
  . 1.3.6.1.4.1.89.35.5.1.1.2
  . 1.3.6.1.4.1.89.83.1.2.1.2
  . 1.3.6.1.4.1.89.83.1.2.1.3
  . 1.3.6.1.4.1.89.83.1.2.1.4
  . 1.3.6.1.4.1.89.53.15.1.3
  . 1.3.6.1.4.1.89.53.15.1.3
  OIDs of fan
  . 1.3.6.1.4.1.89.83.1.1.1.2
  . 1.3.6.1.4.1.89.83.1.1.1.3
  . 1.3.6.1.4.1.89.53.15.1.4
  . 1.3.6.1.4.1.89.53.15.1.5
  . 1.3.6.1.4.1.89.53.15.1.6
  . 1.3.6.1.4.1.89.53.15.1.7
  . 1.3.6.1.4.1.89.53.15.1.8

  for old firmware - if the 35xx above does not work:
  Temperature
  1.3.6.1.4.1.674.10895.5000.2.89.53.15.1.9 (Celsius)
  1.3.6.1.4.1.674.10895.5000.2.89.53.15.1.10

  I hope this helps.

  B

• Dell PowerConnect 6248 10 GB ports reference works do not

  Hello

  We have recently installed a module SFP + (part # c107d) in our Dell PowerConnect 6248 switch. The switch does not seem to see the module because before install us the plug-in, it showed a port xg3 xg4, and after the addition of the module, it shows that these ports.

  So I have a few questions:

  Is the SFP + above compatible with this model of switch?

  If so, how can verify us that the ports are active?

  Here is the result of the port details:

  #show interface ethernet 1/xg3 in detail

  Port Type Duplex speed Neg Admin link

  A State

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

  1/xg3 10G - level s/o unknown Auto Up Down

  Port description

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

  1/xg3

  Flow control: enabled

  Port: 1/xg3

  Belonging to a VLAN: access mode Mode

  Operating parameters:

  PVID: 1

  Capture filtering: enabled

  Acceptable frame type: no label

  Default priority: 0

  GVRP status: Disabled

  Protected: disabled

  -Other - or ITU (q)

  Port 1/xg3 is a member of:

  Rule of VLAN name evacuation Type

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

  1 by default not marked by default

  Static configuration:

  PVID: 1

  Capture filtering: enabled

  Acceptable frame type: no label

  Port 1/xg3 is configured statically:

  Output name rule of VLAN

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

  Prohibition of VLAN:

  Name of VLAN

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

  Port 1/xg3 Enabled

  Status: Disabled role: disabled

  -Other - or ITU (q)

  Identification of the port: 128.51 shipping cost: 0

  Fast port: No. (configured: no) root Protection: No.

  Designated the bridge priority: 32768 address: 80:00:00:25:64:19:92:1 C

  Identification of the designated port: 0.0 cost of access road designated: 0

  Root regional CSE: 80:00:00:25:64:19:92:1 C CSE Port cost: 0

  BPDU: 0 sent, received 0

  Yes, this module is listed as compatible with the switch. It seems that you install in Bay 2? He may have listed these ports but they probably do not appear as active. Have you tried to make a connection with ports?

• Slave keeps restarting after unstacking-Dell PowerConnect 6224 switch

  Hello everyone;

  I have 2 switches (PowerConnect 6224) on the other. Because we are them stacked like we got new switches, we decided to remove the cables from the battery and use them as individual switches.

  So I tried to unstacking the first switches using CLI, but it does not, simply, nothing happens. So I took the cards accumulation off both switches and removed the stacking cables.

  Switch works fine, but the slave is restarted.

  I correct the following:

  Startup options, tried to reset, restore the production parameters, format... They look successful the config looks like this is done and once the switch starts it asks me if I want to run the Setup Wizard, but it will just freeze and restart.

  is there a way to fix it? or the switch is dead?

  All ideas are welcome

  Thank you

  I would like to download the latest firmware.

  www.Dell.com/.../drivers

  Disconnect all other devices from the switch and follow the instructions of XMODEM that are included in the download to Flash the firmware.

• Management VLan in Dell Powerconnect 6224

  Hello

  I have power supply dell switch connect 6224. I created 3 vlan, Vlan 10,20 and 30. different ip network given to all the vlan...

  The problem, he can access via telnet or Http from the IP two vlan 3...  I want that she needs to access from only a single IP address not all the...

  should what additional configuration I do on switch?

  I will seek to implement the ACL to deny access to the address IP of the VLAN.

  This is a good, white page that covers the ACLs on the 6224.

  http://www.Dell.com/downloads/global/products/PWCNT/en/pwcnt_ip_acls.PDF

  To help control access to the switch, one of the first things I suggest you do allows SSH and HTTPS, then disable Telnet and HTTP.

• Connect 6224 VLAN routing and management VLAN

  Happy holidays all the world-

  I read several posts here and elsewhere on the inability of the 6224 to deliver its own management interface. OK, enough, I get it. But what I don't understand is a practical solution to what seems to be a huge problem if you want to use the network to connect to the device to manage (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. for the network A, b and C. Let's just ignore shifts and redundant connections to do this.

  The management VLAN can not be assigned to one of these networks, right? He said in the documentation, and it turns out if you try to do it on the configuration of the switch. It doesn't let you do.

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

  So what then? A dedicated computer for D who cannot reach the other thing than the switch management port? What about another completely separate router (I have a Cisco ASA with some ports to spare, or a hint of irony, an another 6224!) to provide a connection between D and a networks normally used? This is crazy.

  Of course, missing me something here. I can't believe that the answer is, 'If you enable routing, the management interface is essentially unusable"but that's what it looks like, from my possibly twisted point of view. I want to have my laptop computer and any other computer, sitting on a network that can be put to rout by the 6224, and for that same laptop also be able to reach this same 6224 management interface.

  Someone please help me understand this?

  Thank you

  Chris

  PS: I have an email address. It is almost unique on the entire planet. I use it to connect to this forum. But Dell, like so many others, insists on ignoring these facts and let me create an another unique identifier while playing a game of 20 questions. That's why my remarkably stupid random username.

  Thanks again, and I hope that someone gets at least a good laugh over this.

  Vlan management can be considered as a port OOB. If the intention is that it be separated from the rest of the traffic and on its own dedicated network. However, you are not limited to manage the switch through just the interface vlan management. Each VLAN with an IP address can be used by customers in this vlan to manage the switch.

  For example, if you assign a VLAN 2 address and ip 192.168.2.1. Customers in VLAN 2 with and the 192.168.2.x subnet ip address can access 192.168.2.1 to manage the switch, while being able to communicate with clients in other VLANs.

  I hope this helps some, let me know if you need help on your config, or to specify anything.

  Thank you

• Reference Dell Powerconnect 6224 DVLAN-mining (Q in Q)

  I have two sites, one is our data center and the other is our office.

  I want to be able to access the data center to the office network, I need access for 2 VLANs, the ISP has already installed it is fine for this and now there's only the part configuration

  At the office, there is a PC5548 and data center, there is one PC6224.

  Office on the incoming port configuration is:

  tengigabitethernet1/0/1 interface
  switchport mode trunk

  The port for outgoing data center conf is:

  interface ethernet 1/g22
  Description "TELEV6RK".
  switchport mode general
  VLAN allowed switchport General add 3000
  dvlan-tunnel mode

  This does not work, how do I configure ports, do I have to configure all ports or only 1 port IDE oucederomsurlesecondport 5548 and 1 on 6224?

  I got an answer from Dell technical support, on how to do it:

  1. If the marking through ISP is different from DOT1Q then you must change it on the two switches using the command global dvlan-tunnel ethertype and options there are (dot1q, vman or custom)

  2 port 1 and 2 must be port trunk who accept only the 3000 VLAN. Here are the ports that are connected to the ISP.

  3 ports 3 and 4 should be dvlan-tunnel mode configured on them and configured as switchport access VIRTUAL 3000 LAN mode. These are ports that are connected to switches that are for production at both sites.

  4 ports 5 and 6 on other switches must be configured as trunk with tagged VLANs you want to transfer through ISP in VLAN 3000. These are the ports located on the switch of production.

  The topology is here: www.upload.ee/.../Topology-change.png

  I hope that now everyone will have its operation :) Thanks for the help.

• Reference Dell Powerconnect 6224

  Hello, we need help to choose the right device of balancing of affordable to work with dell switches load 6224 we have two switches with two dedicated company comcast internet (2 5 static IP gateways each) low 100meg 20up we have a load of 400 traffic +, we see that there is Load Balancer ADC like Barracuda, Kemp etc. have no need for security with a cost of one year to the next we have just need a good load balancer with some security as ddos to effectively distribute traffic while ensuring high performance for games & voice servers hosting we have a large community make world wide everything is free... What would you use? Thank you

  Sonicwall Dell devices provide failover and load balancing. Not sure that they meet all of your requirements, but interesting look in.

  http://www.SonicWALL.com/us/en/products/failover-failback.html

  Your post on Spiceworks had some excellent feedback from the community.

  See you soon

• VLAN between 2 powerconnect 6224 using XFP modules

  Dear friends,

  I have 2 switches powerconnect 6224 interconnected using optical fiber and XFP ports on the rear panel of the switch.

  There is no configuration of the battery between them.

  The distance between the two switches is 500 metres and they both work correctly when you use the vlan by default (use of the LAN)

  I created a virtual LAN using 2 ports on a firewall and I created the same vlan on the second firewall, but I can't see a VLAN traffic goes to the other.

  Also, I tried to configure the port as trunk but same result.

  The vlan works very well in a single switch, but traffic is not able to flow to the second switch.

  You have an idea why does not?

  Maybe is not posible to have VLANs using xfp connections...

  Any idea would be greatly popular.

  Thanks in advance!

  Rear ports are labeled xg1, 2, 3, 4. So, if the connection is made using the xg1 on a single switch for xg1 on the other switch. Then you enter interface 1/xg1 and make configuration changes.

• VLANs for PowerConnect 6224

  Hello

  I bought Dell PowerConnect 6224 & I'm newbie for VLAN management. To put it simply, how can I create two VLANs (vlan 10 - 192.168.10.x/24 & vlan 20 - 192.168.20.x/24) that can communicate with each other without defining the point of gateway for the network servers and workstations to the ip address of vlan?

  Thank you.

  Here is a link to the manuals available for the Dell PowerConnect 62xx:

  support.Dell.com/.../index.htm

  Creation of VLANS

  Console > activate

  Console # config

  Console (config) # vlan database

  VLAN console(config-VLAN) # 10

  output console(config-VLAN) #.

  Console (config) # interface vlan 10

  # Ip address 255.255.255.0 192.168.10.x console

  Console # name Marketing

  Console # end

  console # show vlan

  Creating Ports for PC to connect as a ignorant guest VLAN.

  Console > activate

  Console # config

  Console (config) # interface ethernet 1/e1

  Console # switchport mode access

  Console # switchport access vlan 10

  Console # end

  Enable routing

  To globally enable IPv4 routing on the router, use the command "ip Routing".

  in Global Configuration mode.

  Console (config) #ip Routing

  You will need to create the VLAN as described above.  Then, set the access mode for a port VLAN particular then set the PC with an IP address in the range of the subnet for the VLAN and the gateway as the IP address of the address that you provided for the VLAN on the port.

  Then once the routing is enabled in the world it should allow communication between VLANs and configured different subnets.

  Hope this helps,

• PowerConnect 6224: Dell SFP + port supports combine Dell SFP?

  I have a Dell Powerconnect 6224 switch and I installed a Dual Port SFP + Module of adaptation for PowerConnect
  6200 series at bay2 at the rear of the switch. I inserted a transceiver, SFP 1000BASE-LX, wavelength 1310nm 10km Reach in the SFP slot + and the other end is connected to a connector SFP 1gbe. I don't have any link. My question is if Dell SFP ports + supports SFP transceivers or it only supports SFP transceivers +?

  I checked the ports to help an SFP + SFP +, 10GbE, copper Direct Attach cable Twinaxial, and link LEDs are lighting up.

  I believe that the SFP ports + back work with SFP transceivers. Ports before combo will work with SFP transceivers. Another thing to look at is the cable being used. Don't forget that there are specifications that are compatible with transceivers FPS are you wanting to use. A SFP + SFP connection would require that the SFP transceiver + supports a connection of 1 GB.

  Hope this info helps.