On Vlan in 6224

Similar Questions

• PowerConnect 6224 VLAN config / default gateway

  Hello

  I am new to configuring a VLAN and work with DELL going on so please forgive my ignorance.

  I joined a small agency that currently has a flat structure networking including 1 6224 linked to two 5548 one is connected to three 3548 (access), and the other is connected to a server. The 6224 connects to a proxy (default gateway), and then on the Web. All devices are currently on a 192.168.78.0 24 network with ip default gateway 192.168.80.1

  We want to segment the network using two VLAN initially. VLAN 1 user "80" and vlan 1 safety '70' and I want to clarify a few things before that I try:

  1. can you stay the ip on the network switch for vlan user ex: 192.168.80.123 or should I create a vlan separate management?

  2. I know in order for the inter - vlan, the ip of the gateway routing vlan must be on the 6224 and I then have to configure a default route to the proxy. The proxy must be on one VLAN separate or could I leave on VLAN 80 and change the ip address another que.1?

  Thanks in advance.

  I did it several times myself.  You can do almost an infinite number of ways, but it will be better to stick to certain typical networking practices.  Here is the version digest readers of what would be preferable to do so.

  1 enable routing on the switch stack.

  2. make a 80 VLAN for your network 24.80.  Assign the IP 192.168.80.1 to this VLAN.  In this way, customers will now be a ".". 1' default to the network gateway, they are on.

  3 make an another VLAN 70 for your network 24.70.  Assign the IP 192.168.70.1 to this VLAN.  This will be the default gateway for the network.  Repeat for however many VLANS / networks you want to.

  4. create a separate VLAN for his own 'bubble' network between the switch and the upstream proxy server.  (Lets call him a dummy VLAN 100 with an IP range x.x.100.x 29.  It can be just a little/29 block or something or 24 if this is confusing. Configuring the ports a few ports 'access' for this VLAN for that no marked traffic pass over this network.  Set x.x.100.1 to your Proxy Server and x.x.100.2 to your switch, then make sure you have directions on both sides about where traffic should go.

  5. save your configuration so that you have to rebuild it after a reboot.  :-)

  It will be best to set your expecations about it.  You want realistic during a weekend/maintenance window.  ARP cache and other issues can make for some downtime.  In addition, there are certainly other ways to do it, but that may be hurtful on the road when you need to increase or scale.  Two years on the road someone wondered why a default gateway is on a few eccentric IP, or there are errors of routing intermentent, etc..

  Powerconnect worldwide, just be clear what is the difference between a port of "access" to the port of 'general', and are a port 'trunk '.  Conditions may be different from the Lim to make, and if one comes to tell the world of Cisco, this may be a little different.

  Finally, don't forget to come up with a good procedure for this during your maintenance window.  Come up with a good plan documented and so well thought out, when run you it, it will be nothing more than a task in office project.

• 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

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

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

• configuration of VLAN 6224/5448

  Hello

  I intend to get ISP co-location services and I need some tips for simple diagram below that I'm not really good in network.

  

  L3 = 6224 switch

  Switch L2 = 5448

  VLAN blue = management

  VLAN = green KVM host. VM it will use to connect to the internet

  I created all three VLANs, but I have a few questions

  1. should I have 3 cables of L3 to L2? One for the connection of two switches, two others for vlan10 & 20?

  ' 2. If I set port 2 and port 1 to vlan10 vlan20, to the title of the page "belonging to a vlan" GUI set for each VLAN?

  3. How can I assign IPs 24 in vlan Green?

  Appreciate for any help I can get :)

  Thank you

  ETH.

  No need for 3 cables except if you create a GAP. To carry several VLANS through a connection, you use general parameters of the trunk.

  Example:

  Console (config) # interface ethernet 1/e7

  mode console # switchport general

  Console # switchport General allowed vlan add 2,3,4,5 tag

  Console # pvid General switchport 99

  It depends on what plug ports 1 and 2. If they connect to a server and that the server is not aware of VLAN, you would set it to not signposted. You can also accomplish this by setting the port to access the mode for the VLAN.

  Example:

  Console (config) # interface ethernet 1/e1

  Console # switchport mode access

  Console # switchport access vlan 2

  But if it connects to another network device VLAN aware, you might consider with label especially if there are several VLANs on the connection.

  On the 6224 assign you an address up to the VLAN with these commands.

  Example:

  Console (config) #interface vlan 5

  Console (config - vlan) #ip address 192.168.1.1 255.255.255.0

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

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

• VLAN routing when you use a dell computer 6224

  Hello

  I have a dell switch 6224 with 2 VLANS.

  Management-192.168.1.111/24 Ports 1/g1-1 / g12

  Vlan150-192.168.150.111/24 Ports 1/g13-1 / g24

  I have two ports on the router with the ip address to communicate with the switch (192.168.1.2 and 192.168.150.2). Vlan1 works very well without any problems. I can ping from 192.168.150.2 to 192.168.150.111. I set up the laptop with the ip 192.168.150.113 and plugged in the Vlan150 on port 1/g19. I can not ping to 192.168.150.113 192.168.150.2. The traffic is not going through the Vlan150 in the switch.

  What Miss me? This is my first time setting up a VLAN on these switches. Help, please.

  Config

  console #show running-config

  ! Current configuration:

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

  ! 3.3.8.2 system software version

  ! Passage mode is configured as disabled

  !

  Configure

  database of VLAN

  VLAN 150

  VLAN 150 1 routing

  subnet of VLAN association 192.168.150.0 255.255.255.0 150

  output

  battery

  1 1 member

  output

  192.168.1.111 IP address 255.255.255.0

  by default-gateway IP 192.168.1.2

  IP routing

  interface vlan 150

  name "VLAN150".

  Routing

  IP 192.168.150.111 255.255.255.0

  output

  level of 00436d6ae2ed27bbe87fa24b73b5a249 user name 'admin' password encrypted 15

  line of AAA authentication login "defaultList".

  the AAA authentication enable line 'enableList '.

  line console

  00436d6ae2ed27bbe87fa24b73b5a249 encrypted password

  output

  line telnet

  connection of authentication defaultList

  00436d6ae2ed27bbe87fa24b73b5a249 encrypted password

  output

  ssh line

  connection of authentication defaultList

  00436d6ae2ed27bbe87fa24b73b5a249 encrypted password

  output

  !

  interface ethernet 1/g1

  switchport mode general

  output

  !

  interface ethernet 1/g2

  switchport mode general

  output

  !

  interface ethernet 1/g3

  switchport mode general

  output

  !

  interface ethernet 1/g4

  switchport mode general

  output

  !

  interface ethernet 1/g5

  switchport mode general

  output

  !

  interface ethernet 1/g6

  switchport mode general

  output

  !

  interface ethernet 1/g7

  switchport mode general

  output

  !

  interface ethernet 1/g8

  switchport mode general

  output

  !

  interface ethernet 1/g9

  switchport mode general

  output

  !

  interface ethernet 1/g10

  switchport mode general

  output

  !

  interface ethernet 1/g11

  switchport mode general

  output

  !

  interface ethernet 1/g12

  switchport mode general

  output

  !

  interface ethernet 1/g13

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g14

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g15

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g16

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g17

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g18

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g19

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g20

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g21

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g22

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g23

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  !

  interface ethernet 1/g24

  switchport mode general

  VLAN allowed switchport General add 150

  switchport vlan allowed General remove 1

  output

  activate 00436d6ae2ed27bbe87fa24b73b5a249 encrypted password

  output

  Hello

  The laptop is probably sending unmarked packages and so you need to change the PVID on the interface so that the unmarked packages are assigned to 150 of VLAN.

  switchport General pvid 150

  FTP://FTP.Dell.com/manuals/all-products/esuprt_ser_stor_net/esuprt_powerconnect/PowerConnect-6248_Reference%20Guide_en-us.PDF page 600

• 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

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

• 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

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

• 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

  
  

• 6224 does not get to the internet on vlan-111

  Unable to get to the internet, ran tracert, and when it does respond it shows 192.168.98.254 as next hop.  not good.
  

  On switch port 8 is vlan-1  management port   192.168.2.0/24
  

  on switch port 5 is vlan-111  end-users             192.168.111.0/24
  

  on switch port 21 is vlan-98  Mitel voip phones  (not active yet)    192.168.98.0/24
  

  Unable to get to the internet when on a Win2k8R2 server on switch port 5 vlan-111
  

  running-config                                                                 !Current Configuration:!System Description "PowerConnect 6224, 3.3.1.10, VxWorks 6.5"!System Software Version 3.3.1.10!Cut-through mode is configured as disabled!configurevlan databasevlan 98,111vlan routing 98 1vlan routing 111 2exitsnmp-server location ""snmp-server contact ""hostname "TS-1"stackmember 1 1exitip address 192.168.2.1 255.255.255.0ip default-gateway 192.168.2.254ip domain-name xxxxxx.netip name-server 192.168.111.2ip name-server 216.136.95.2ip host fs-bafb01 192.168.111.2ip host ln-bafb 192.168.111.3ip host tl-bafb 192.168.111.4ip routingip route 0.0.0.0 0.0.0.0 192.168.111.1interface vlan 98name "MITEL"routingip address 192.168.98.254 255.255.255.0exitinterface vlan 111name "111-END-USERS"routingip address 192.168.111.254 255.255.255.0exitusername "admin" password fd358f7bed5ecdd318abe6b925e513cc level 15 encryptedvoice vlandhcp l2relay!interface ethernet 1/g1switchport voice detect autodescription 'To_SRX220'switchport access vlan 111exit!interface ethernet 1/g2switchport voice detect autodescription 'To_TS3_Port26'switchport mode generalswitchport general allowed vlan add 98,111 taggedexit!interface ethernet 1/g3switchport voice detect autodescription 'To_MITEL_SYSTEM'switchport access vlan 98switchport forbidden vlan add 111voice vlan 98exit!interface ethernet 1/g4switchport voice detect autodescription 'To_TS2_Port26'switchport mode generalswitchport general allowed vlan add 98,111 taggedexit!interface ethernet 1/g5switchport voice detect autoswitchport access vlan 111exit!interface ethernet 1/g6switchport voice detect autodescription 'To_LN_BAFB_ETH0'switchport access vlan 111exit!interface ethernet 1/g7switchport voice detect autodescription 'To_TL__PortETH0'switchport access vlan 111switchport forbidden vlan add 98exit!interface ethernet 1/g8switchport voice detect autoexit!interface ethernet 1/g9switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g10switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g11switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g12switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g13switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g14switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g15switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g16switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g17switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g18switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 111switchport general allowed vlan add 98 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g19switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 98,111 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g20switchport voice detect autoswitchport mode generalswitchport general pvid 111switchport general allowed vlan add 98,111 taggedswitchport general allowed vlan remove 1exit!interface ethernet 1/g21switchport voice detect autodescription 'To_FS__Port_ETH01_VLAN98'switchport access vlan 98exit!interface ethernet 1/g22no negotiationspeed 10switchport voice detect autodescription 'To_T4_Port10'switchport mode generalswitchport general allowed vlan add 98,111 taggedexit!interface ethernet 1/g23no negotiationspeed 10switchport voice detect autodescription 'To_W7_Port10'switchport mode generalswitchport general allowed vlan add 98,111 taggedexit!interface ethernet 1/g24no negotiationspeed 10switchport voice detect autodescription 'To_W6_Port10'switchport mode generalswitchport general allowed vlan add 98,111 taggedexit!interface ethernet 1/xg1switchport voice detect autoexit!interface ethernet 1/xg2switchport voice detect autoexit!interface ethernet 1/xg3switchport voice detect autoexit!interface ethernet 1/xg4switchport voice detect autoexit!interface port-channel 1switchport voice detect autoexit!interface port-channel 2switchport voice detect autoexit!interface port-channel 3switchport voice detect autoexit!interface port-channel 4switchport voice detect autoexit!interface port-channel 5switchport voice detect autoexit!interface port-channel 6switchport voice detect autoexit!interface port-channel 7switchport voice detect autoexit!interface port-channel 8switchport voice detect autoexit!interface port-channel 9switchport voice detect autoexit!interface port-channel 10switchport voice detect autoexit!interface port-channel 11switchport voice detect autoexit!interface port-channel 12switchport voice detect autoexit!interface port-channel 13switchport voice detect autoexit!interface port-channel 14switchport voice detect autoexit!interface port-channel 15switchport voice detect autoexit!interface port-channel 16switchport voice detect autoexit!interface port-channel 17switchport voice detect autoexit!interface port-channel 18switchport voice detect autoexit!interface port-channel 19switchport voice detect autoexit!interface port-channel 20switchport voice detect autoexit!interface port-channel 21switchport voice detect autoexit!interface port-channel 22switchport voice detect autoexit!interface port-channel 23switchport voice detect autoexit!interface port-channel 24switchport voice detect autoexit!interface port-channel 25switchport voice detect autoexit!interface port-channel 26switchport voice detect autoexit!interface port-channel 27switchport voice detect autoexit!interface port-channel 28switchport voice detect autoexit!interface port-channel 29switchport voice detect autoexit!interface port-channel 30switchport voice detect autoexit!interface port-channel 31switchport voice detect autoexit!interface port-channel 32switchport voice detect autoexit!interface port-channel 33switchport voice detect autoexit!interface port-channel 34switchport voice detect autoexit!interface port-channel 35switchport voice detect autoexit!interface port-channel 36switchport voice detect autoexit!interface port-channel 37switchport voice detect autoexit!interface port-channel 38switchport voice detect autoexit!interface port-channel 39switchport voice detect autoexit!interface port-channel 40switchport voice detect autoexit!interface port-channel 41switchport voice detect autoexit!interface port-channel 42switchport voice detect autoexit!interface port-channel 43switchport voice detect autoexit!interface port-channel 44switchport voice detect autoexit!interface port-channel 45switchport voice detect autoexit!interface port-channel 46switchport voice detect autoexit!interface port-channel 47switchport voice detect autoexit!interface port-channel 48switchport voice detect autoexitsnmp-server community public ro ipaddress 192.168.111.9exit
  

  I didn't imply that you need another switch.  In my example of switch 2 is your firewall.