PowerConnect 6224 VLAN config / default gateway

Similar Questions

• PowerConnect 6224 VLAN created, but impossible to do a ping between customers

  1 created vlan 2 with two ports 17.19 with ip 10.0.1.2/24

  2 created vlan 3 with two ports 13.15 with ip 10.0.2.2/24

  attempt to create inter routing vlan

  1 pc windows connected with ip 10.0.1.3/24 and a gateway to port 17 10.0.1.2

  2 connected windows pc with ip 10.0.2.3/24 and a gateway 10.0.2.2 to port 15

  Unable to get the Ping between two clients any help would be much appreciated, thank you in advance and running config pasted below

  coresw1 #show running-config
  ! Current configuration:
  ! Description of the system "PowerConnect 6224, 3.3.7.3, VxWorks 6.5.
  ! 3.3.7.3 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 2-3, 5
  VLAN 2 1 routing
  VLAN 3 2 routing
  output
  location of SNMP Server "Data Center"
  contact SNMP Server «»
  hostname "coresw1".
  unicast SNTP client enable
  10.0.0.1 SNTP server
  clock timezone 5 minutes 30 zone 'IST '.
  battery
  1 1 member
  output
  IP 10.0.0.193 255.255.255.0

  by default-gateway IP 10.0.0.1
  IP - peekaygroup.com domain name
  name-server IP 10.0.0.1
  without enabling ipv6
  IP routing
  interface vlan 2
  name "LAN1.
  Routing
  10.0.1.2 IP address 255.255.255.0
  bandwidth 10000
  IP mtu 1500
  output
  interface vlan 3
  name "LAN2.
  Routing
  IP 10.0.2.2 255.255.255.0
  bandwidth 10000
  IP mtu 1500
  output
  interface vlan 5
  name "RIL Internet"

  output
  level of 8a9f2a72d65baf40b48108874cd50592 user name 'admin' password encrypted 15
  !
  interface ethernet 1/g13
  switchport access vlan 3
  output
  !
  interface ethernet 1/g15
  switchport access vlan 3
  output
  !
  interface ethernet 1/g17
  switchport access vlan 2
  output
  !
  interface ethernet 1/g19
  switchport access vlan 2
  output
  !
  interface ethernet 1/g20
  switchport access vlan 5

  output
  !
  interface ethernet 1/g22
  switchport access vlan 5
  output
  SNMP-server community public rw
  output

  This blog does a good job of showing the different firewall rules to add. You said that you have already tweaked the firewall some, I would just check the measures taken.

  http://www.sysprobs.com/enable-ping-reply-Windows-7

  If there is no antivirus software installed, try a break/disabling it to test and see if it makes a difference.

  I don't see anything on the config which would prevent pings happen.

• PowerConnect 6224 VLAN Routing, unable to connect out of VLAN but able to connect by entering.

  To set up a new VIRTUAL local network to separate the common workstation network and obtain new DHCP scope, I had a few questions and found advice in the post of http://en.community.dell.com/support-forums/network-switches/f/866/t/19370806.aspx?PageIndex=3 but now I find that my traffic is not going through properly so I'm starting a new thread to get help shows all of working.

  Current primary network 192.168.1.0/24 (192.168.1.200 DHCP server). Adding new perspectives to the server for 192.168.3.0/24 active.

  Gateway default 192.168.1.0/24 is 192.168.1.254 (Cisco ASA, it was set up like that when I arrived and no room to insert the dedicated router). Adding route to 192.168.3.0/24 > 192.168.1.253 (PC6224 and VLAN 1 management interface). I also added exceptions NAT asa for the 192.168.3.0 network.

  I was still having some problems of scathing to the 192.168.3.0 network from the DHCP server and I added a static route on the server for this network, bypassing the ASA for routing to the switch.

  From the DHCP server, I am able to ping 192.168.1.253, 192.168.3.254 but not a laptop that runs Windows XP configured with 192.168.3.1 address connected to port 22 of the 6224.

  The XP laptop, I am able to ping 192.168.3.254 but not 192.168.1.253 or any other address in the 192.168.1.0 network.

  The switch CLI, I am able to ping on both networks destinations.

  Here is my config of switch. I have it set to scrape factory reset so there is no buried old ACL inside.

  console #show run
  ! Current configuration:
  ! Description of the system «PowerConnect 6224P, 3.3.5.5, VxWorks 6.5»
  ! 3.3.5.5 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 2
  VLAN 2 1 routing
  output

  IP 192.168.1.253 255.255.255.0
  by default-gateway IP 192.168.1.254
  IP - domain.local domain name
  name-server IP 192.168.1.11
  name-server IP 192.168.1.200
  IP routing
  IP helper-address 192.168.1.200 dhcp

  interface vlan 2
  name 'common '.
  Routing
  192.168.3.254 IP address 255.255.255.0
  IP netdirbcast
  bandwidth 10000
  business assistance-address IP 192.168.1.11
  field of IP helper-address 192.168.1.200
  IP helper-address 192.168.1.200 dhcp
  IP mtu 1500
  output

  l2relay DHCP
  DHCP l2relay vlan 2
  !
  interface ethernet 1/g21
  switchport access vlan 2
  output
  !
  interface ethernet 1/g22
  switchport access vlan 2
  output
  !
  interface ethernet 1/g23
  switchport access vlan 2
  output
  !
  interface ethernet 1/g24
  switchport access vlan 2
  output

  
  

• PowerConnect 6224 VLAN down?

  I just created a new 51 VLAN on my core 6224 switch.

  I have assigned an IP address, configured routing, he attributed to multiple trunks, and I attributed to a port of access to him as well. VLAN 8, I'll set up, have had no problems with others.

  Here's what I see when I show ip interface vlan 51

  PHX_Core_Switch #show ip interface vlan 51

  State of the Routing Interface... Down
  Primary IP address... 10.200.51.1/255.255.255.0
  Routing mode... Enable
  Administrative mode... Enable
  NET before realized emissions... Disable
  Proxy ARP...................................... Enable
  Local Proxy ARP... Disable
  Statement of assets... Inactive
  MAC address... 5C26.0AF9.9E8C
  Type of encapsulation... Ethernet
  IP MTU......................................... 1500
  Bandwidth...................................... 10000 Kbps
  Destination unreachable... Activated
  ICMP redirects... Activated

  Why the interface is down? Help? I'm going nuts here!

  Just got off the phone with Dell technical support. They could not understand either, we have created a new 60 VLANS and it came fine and worked exactly as planned.

  Maybe it's a bug in the Firmware 3.3.3.3.

• Dell Powerconnect 6224 Default VLAN VLAN reference and management

  Hello

  two questions-

  1. what exactly he wants to tell the VLAN by default is not routable or VLAN 1 is not routable? I can connect to my 6224 a different subnet and its got nothing configured except default values and an IP address to this VLAN

  2. I have a stack of 2 x 6224 s, 95% completed and all on the default VLAN 1. I won't use VLAN 1. So I create a VLAN 10 and "range Ethernet all interface ' followed ' switchport access vlan 10"»

  Now I can not connect on the network. That's happened? How can I move everything cleanly on VLAN 10 and it is possible via the network or must it be done with a cable from the console?

  Thank you

  Hello, by default, the management interface is in VLAN 1, if you want to she be changed to VLAN 10 please use the command 'ip address vlan 10' in the Setup mode and check the status of management interface using the command 'show ip interface '.

• 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,

• 7048 config as default gateway. Next internet and Juniper at the break.

  Hi, we have a stack of 2 x 7048 s who are (is?) configured as a default gateway for a number of VLAN from some Dell blade chassis. I won't go into too much detail because it's more of a conceptual thing I need to know

  8 x VLANS, which are all x.x.x.254 255.255.255.0. Large. All the internal stuff works a treat.

  Now, I would like to take 48 port and plug a juniper firewall and have all the internal stuff in access internet. safely.

  I can put in place the Juniper and access the internet separately and everything works fine also. How can I join the two together? How to configure port 48 to be the gateway to the internet for all the VLANS?

  of the outside external internet connection has (internally) is 192.168.1.254. He my Juniper with 192.168.1.92 APS (UnTrust pronounced by the external router DHCP). IP of confidence of Juniper is negotiable, but currently I put like 192.168.2.1 (static) and he would have the port defined as 192.168.2.254

  Therefore, the conceptual bit to get all VLAN.254 see port 48 as the output to the internet, so I'm lokoing. Then, I need to set up DNS etc. internally and on the Gin that is the next challenge.

  Thanks in advance

  The command to enter a lane that will direct traffic to the firewall is.

  console (config) #IP 0.0.0.0 route 0.0.0.0 192.168.2.1

  The IP address 192.168.2.254 should be for VLAN 10 on the 7048. And then no other VLAN must be in the 192.168.2.x broadcast domain.

  Console (config) #interface vlan 10

  Console (config - vlan) #ip address 192.168.2.254 255.255.255.0

  Then, to relay DHCP packets to the DHCP server, you would add the command ip assistance

  Console (config) #ip helper-address 192.168.1.92 dhcp

• 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.

• 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

• Transit VLAN on the PowerConnect 6224

  I need help to sort out a problem with routing on a 6224 we have configured to act as a vlan transit for one of our branches.  The general idea is 8.143 is the vlan of transit, of 8.144 is our PC LAN 8.145 will be our VOIP lan.

  We have installed this switch with our WAN provided last week, but had to get out. Traffic seemed to happen to the WAN providers to our transit interface VLAN (172.22.143.254) wasn't going anywhere.  It's 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 an address 143.x I could ping our remote control does site at 172.22.8.x no problem but not 144.x or 145.x

  (5) 172.22.8.x, I couldn't ping 144.x or 145.x or 143.1 (I could ping 143.254 which is EXTENDED to suppliers to our switch network interface)

  Here's the running to the switch configuration.  Any suggestions would be greatly appreciated:

  Console > activate

  Console execution #show

  ! Current configuration:

  ! Description of the system "PowerConnect 6224, 3.3.6.4, VxWorks 6.5.

  ! 3.3.6.4 system software version

  ! Passage mode is configured as disabled

  !

  Configure

  database of VLAN

  VLAN 143-145

  VLAN routing 143 1

  VLAN routing 144 2

  VLAN routing 145 3

  subnet of VLAN association 172.22.143.0 255.255.255.0 143

  subnet of VLAN association 172.22.144.0 255.255.255.0 144

  subnet of VLAN association 172.22.145.0 255.255.255.0 145

  output

  battery

  1 1 member

  output

  DHCP IP address

  IP routing

  IP route 0.0.0.0 0.0.0.0 172.22.143.254

  interface vlan 143

  Name the "Transit".

  routing ip address 172.22.143.1 255.255.255.0

  output

  interface vlan 144

  name "TWLAN".

  routing ip address 172.22.144.1 255.255.255.0

  output

  interface vlan 145

  the name "VOIP" routing

  IP 172.22.145.1 255.255.255.0

  output

  level of 746f7a78621059d80fdc538acc40cbf2 user name 'admin' password encrypted 15

  !

  interface ethernet 1/g1

  switchport mode general

  VLAN allowed switchport General add 143

  output

  !

  interface ethernet 1/g2

  switchport mode general

  VLAN allowed switchport General add 143

  output

  !

  interface ethernet 1/g3

  switchport mode general

  VLAN allowed switchport General add 144

  output

  !

  interface ethernet 1/g4

  switchport mode general

  VLAN allowed switchport General add 144

  output

  !

  interface ethernet 1/g5

  switchport mode general

  VLAN allowed switchport General add 145

  output

  !

  interface ethernet 1/g6 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g7 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/8 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g9 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g10

  switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g11 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g12 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g13 switchport mode General General switchport vlan allowed output adds 145! General mode of interface ethernet 1/g14 switchport

  switchport general allowed vlan add exit 145! interface ethernet 1/g15 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g16 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g17 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g18 switchport mode General switchport General allowed vlan add 145

  output! interface ethernet 1/g19 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g20 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g21 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g22 switchport mode General switchport General allowed vlan add exit 145

  ! interface ethernet 1/g23 switchport mode General General switchport vlan allowed output adds 145! interface ethernet 1/g24 switchport mode General switchport General allowed vlan add to exit 145

  Console #.

  It seems that port 1 must be in the VLAN 143, not general mode access mode. You already have a static route in place on the PowerConnect switch which directs traffic to the next break in the network. But it may be necessary for a place on the Cisco that allows to direct traffic to the PowerConnect switch.

  Here is a good post to look through also.

  http://en.community.Dell.com/support-forums/network-switches/f/866/t/19506015.aspx

• VKernel default gateway - VLAN

  Hi guys

  If I understand well here it is recommended to have vmotion and traffic management on different VLANS, which means that different gateways

  http://www.yellow-bricks.com/2011/03/22/ESXi-management-network-resiliency/

  I created 25 VLANS for traffic management and the gateway 10.10.25.1

  and VLAN 28 for Vmotion gateway 10.10.28.1

  But how do I managed to get this to work with different gateways tw2? Since there is only a single default gateway of vkernel.

  Thank you very much

  You do not use a gateway for the subnet of vMotion.  Practically vMotion traffic should not be routed you don't need a gateway.  When you configure the vMotion VMkernel port, it will show the default gateway for the other subnet.  You can ignore that.

• Reference Dell 6248P - Guest Wifi VLAN config

  I am trying to retrieve all upward of a VLAN. The VLAN is comments wireless traffic going through our main switches and on an ADSL router but I'm running into some difficulties.

  We have 3 points of access for model AP - AC Unifi. Each access point has a connection of physical network of 1 of 4 Dell 6248 switches which are currently in a single stack managed as follows.

  AP 1-> Port of the Switch 1 40

  AP 2-> Port of the Switch 2 36

  AP 3-> Port of the Switch 3 17

  The managed pile and AP are currently using the 192.168.1.0/24 on VLAN 1 - default and I created a VLAN 10 - guest.

  The APs have two SSID WLAN, 'corporate', which is also on the 192.168.1.0/24 range and 'guest' that is located on 192.168.99.0/24. I put the "guest" to mark its traffic with VLAN 10 and no DHCP is defined.

  I put the 3 above general Mode ports, allowing all managers and VLAN - 1 that are not marked and VLAN - 10 they are labeled.

  I also put a Zyxell router with a static address of 192.168.99.254 in Switch 4 Port 24 and set the access mode for VLAN 10.

  The router is configured to provide DHCP for the beach of 192.168.99.0/24.

  Now when I connect a laptop to our 'coporate' WLAN, everything works fine. I get a DHCP address from our server and I can reach everything as usual.

  When I connect to the "guest" WLAN, I do not receive a DHCP address, in addition, I am able to ping on subnet 1 hardware VLAN I thought would not be possible.

  Can someone take a look at this config and I would like to know what is the problem with him?

  ! Current configuration:
  ! Description of the system «PowerConnect 6248P, 3.3.12.1, VxWorks 6.5»
  ! 3.3.12.1 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 10
  VLAN 10 1 routing
  subnet of VLAN association 192.168.99.0 255.255.255.0 10
  output
  unicast SNTP client enable
  192.168.1.18 SNTP server
  battery
  1 5 Member
  2 5 Member
  3-5 Member
  4-5 Member
  output
  switch priority 1 12
  IP 192.168.1.212 255.255.255.0
  default IP gateway - 192.168.1.227
  IP - my.domain domain name
  name of the IP-server 192.168.1.18
  name of the IP-server 192.168.1.19
  name of the IP-server 192.168.140.2
  IP routing
  IP route 192.168.99.0 255.255.255.0 192.168.99.254
  interface vlan 10
  name of the "Guest".
  Routing
  IP 192.168.99.212 255.255.255.0
  bandwidth 10000
  IP helper-address 192.168.99.254 dhcp
  IP mtu 1500
  output
  level of a8e64cdc85228f4c837da747958ffd74 user name 'admin' password encrypted 15
  l2relay DHCP
  DHCP l2relay vlan 2.10
  !
  interface ethernet 1/g7
  Auto mode channel-group 2
  output
  !
  interface ethernet 1/g8
  Auto mode channel-group 1
  output
  !
  interface ethernet 1/g40
  switchport mode general
  switchport general allowed vlan add 10 tag
  output
  !
  interface ethernet 2/g36
  switchport mode general
  switchport general allowed vlan add 10 tag
  output
  !
  interface ethernet 3/g2
  Auto mode channel-group 2
  output
  !
  interface ethernet 3/g17
  switchport mode general
  switchport general allowed vlan add 10 tag
  output
  !
  interface ethernet 3/g48
  Auto mode channel-group 1
  output
  !
  interface ethernet 4/g24
  switchport access vlan 10
  output
  output

  I was looking back through the configuration, and on the 24 port setting, I see there is a command to access in place, but the port is not set to enter the mode. Can you try to put the port in access mode?

  interface ethernet 4/g24
  switchport mode access

  During the test with the laptop plugged on the switch, we should test it first with a static IP address. This is to ensure that we have a connection established. Then you can move on to DHCP.

  The router will appear in the output of one of these two commands?

  console switch arp #show

  #show bridge console table address

• LACP LAG POWERCONNECT 6224

  Hi I m ussing a powerconnect 6224, I have equipment that works as a switch and it has two ports glued with LACP, when I connect this device to the POWERCONNECT and send a ping there is no answer, one that with a laptop computer connected to this port, it responds to the ping command. Can help you with this? Here is the configuration of the POWERCONNECT. Thanks in advance.

  Console (config) #interface vlan 32

  Console (config-if-vlan10) #ip address 10.163.101.4 255.255.255.252

  Console (config-if-vlan10) #routing

  Console (config) #interface ethernet 1/g3

  mode console (config-if-1/g1) #switchport general

  Console (config-if-1/g1) #switchport general allowed vlan add 31

  Close, more like this.

  Console (config) # interface range ethernet g2

  Console # channel - group 1 automatic mode

  output console #.

  Console (config) # interface range ethernet g3

  Console # channel - group 1 automatic mode

  output console #.

  Console (config) # interface port-channel 1

  Console # switchport mode general

  Console # switchport general allowed vlan 201 tagged

  Make sure that there are at least two ports in each LAG.

• Pwerconnect 6224: vlan client computers do not receive the ip address of DHCP server on a different VLAN

  Hello

  I have a prolem routing dhcp requests between the vlan management where DHCP server resides and the other VLANs.

  I have the scenario of base with three VLANS: vlan 10 (management vlan), 20, 30, configured on a Powerconnect 6224 switch L2 mode. This switch is connected to a pfsense router. The router is configured at the package of road between the VLANS and it does it well.

  In Vlan 10, I have a configured DHCP server to use the ip addresses of all the VLANS (10, 20, 30). VLAN 10 client computers receive ip address but not others from other VLANs.

  When I put the ip address in the appropriate range of VLANs manually on computers, I ping the server and I have connectivity.

  This suggests that the problem is with the dhcp package.

  The following is the configuration of the switch:

  Configure
  database of VLAN
  VLAN 10,20,30
  VLAN 1 1 routing
  VLAN 20 2 routing
  VLAN 30 3 routing
  output
  SNTP server time.nist.gov
  clock timezone 1 minutes 0
  battery
  1 1 member
  2 2 Member
  output
  DHCP IP address
  IP address vlan 10
  name of the IP-server 172.16.10.1

  bootpdhcprelay cidridoptmode
  interface vlan 1
  Routing
  IP 172.16.1.1 255.255.255.0
  output
  interface vlan 20
  Routing
  address 172.16.20.1 IP 255.255.255.0
  output
  interface vlan 30
  Routing
  IP 172.16.30.1 255.255.255.0
  output
  level of 20fc49459a1898b923ed3ec7b3e81276 user name 'admin' password encrypted 15
  No spanning tree
  spanning tree priority 0
  l2relay DHCP
  DHCP l2relay VLANs 10, 20-30
  DHCP l2relay circuit-id VLANs 10, 20-30
  !
  interface ethernet 1/g2

  l2relay DHCP
  switchport access vlan 20
  output
  !
  interface ethernet 1/g3
  l2relay DHCP
  switchport access vlan 30
  output
  !
  interface ethernet 1/g21
  switchport access vlan 10
  output
  !
  interface ethernet 1/g22
  switchport access vlan 10
  output
  !
  interface ethernet 1/g23
  switchport access vlan 10
  output
  !

  interface ethernet 1/g24
  switchport mode trunk
  switchport trunk allowed vlan add 10,20,30
  output
  Server SNMP community EyesOfNetwork ro
  SNMP-server community public ro
  output

  I followed the instructions in the powerconnect 6224 user guide, but no progress on this issue.

  Any help will be be grateful.

  Thank you

  Zoubeir

  The DHCP server stores information that could be useful? May need to configure monitoring ports and something as wireshark to monitor DHCP packets. This would help determine where the package is stopping.

  example:

  Console (config) #monitor session 1 source interface 1/g8

  Console (config) #monitor session 1 destination interface 1/g10

  session mode 1 #monitor console (config)

  right now I don't see anything in the config of the switch that stands out. If the DHCP server is configured for option 82, then you will need to include the following command on the switch.

  Example:

  Trust l2relay console #dhcp (config-if-1/g1)

  But I don't think that's our scenario here.

• 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.