Management of VLANS on switches PowerConnect 28XX

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

• Need help to configure the VLAN on a powerconnect 5448

  Hello world

  I am currently working on 2 switches PowerConnect 5448 but I'm completely lost in configuring VLAN.

  My bow:

  

  My needs are:

  -J' have 2 different networks that need to be isolated in different VLANS

  -I want to port 11-14 to use for network backup, all others must be used for the production network.

  -This 2 networks must pass through the port 48 (fiber)

  How can I configure this kind of network on the powerconnect interface (or via telnet)?

  My understood are the following, I have to create 2 different VLAN tag all ports, switch to safe mode all ports of the entitlement each port to the VLAN voted. Am I wrong?

  How the fiber port?

  Thanks in advance for your help on this matter.

  Since your 2 VLAN need not communicate with each other, you should be able to get this working.

  The easiest way to do this would be to have your production on VLAN 1 and VLAN 2 second network.

  Assign an IP address to the switch with the command IP #.

  Assign a default gateway with the # ip default-gateway command.

  Create a VLAN 2:

  Database console (config) # vlan

  Console (config - vlan) # vlan 2

  Set 11-14 ports to access the mode for VLAN 2

  Console # switchport mode access

  Console # switchport access vlan 2

  Set 48 on trunk or general mode ports.

  Console # switchport mode Trunk

  console # permit trunk switchport vlan add 2

  You should get pretty close to a work environment. You may encounter some problem with VLAN 2 contacting 192.168.1.0, maybe just need to put it up and test.

  Here are a few links to software packages and manuals that can help.

  Firmware.

  http://Dell.to/1tz8tW0

  Manuals.

  http://Dell.to/1yqV4DJ

  Keep us on how will your configuration.

• Has anyone set up a trunk between switches PowerConnect 2716 and Intellinet 523554?

  I have a client who has three switches Intellinet 523554 in the core switches and various on the edge, including a PowerConnect 2716 switch. The firewall is a Sonicwall, which is plugged into one of the Intellinet switches, and there are three new SonicPoints that plug in the PowerConnect switch. To the best of my knowledge, even if X 0 (LAN) and X 2 (WLAN) are related to the SonicWall, I need to keep these separate networks. If I plug them both in the VLAN 1, network crashes (I presume due to a storm of broadcasting). On all switches, I created 2 VLANS, left 1 VLAN not identified and configured the appropriate access and if necessary junction ports. Two types of switches use the web-based configuration and it is just not a lot of parameters to be set. VLAN 1 traffic goes OK on the trunk, but VLAN 2 does not work. I'm not familiar with the configuration of the Intellinet switches, so I sent an email into their support. Unfortunately, for the chutes, that's what the rest of the world calls aggregation of links, so I have no help from them yet. I am quite confident that the configuration is as good as it can get.

  Has anyone else tried this and been successful? Any thoughts? The PowerConnect switch runs 1.0.1.07 firmware. Thank you

  The marking of VLAN is the feature you're looking for, 802. q. 1, Page 10 of the user guide describes in detail the configuration of VLANS on switches Intellinet.

  Assets.mhint.S3.amazonaws.com/.../523554_manual.pdf

  Page 50 of guide the user to the 2716

  FTP.Dell.com/.../PowerConnect-2716_User%27s%20Guide_en-US.pdf

  Hope this helps

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

• DHCP server press PowerConnect 28xx series / address pool by VLAN

  Hello

  I am reading the manual of the PowerConnect 2824.

  I am considering buying this switch, but I have a question related to the functionality of the DHCP server.

  Here my question: I want to have different VLAN and use the feature of DHCP server on each of them. Then can I have different address DHCP pools by VLAN?

  Example:

  1-16 ports VLAN1: IP subnet 192.168.1.0/24

  VLAN 2 ports 17-24: IP subnet 192.168.2.0/24

  The manual is not clear on this.

  Your help is welcome.

  Kind regards

  Tom

  Daniel,

  Thanks for the reply. Another question does this mean that the 28xx series switch DHCP server, recover the IP address (from the range configured) on all the VLANS configured? So if a device on VLAN 2 issued a request DHCP, it will get an IP address from the same pool as for example a device on VLAN 1.

  Kind regards

  Tom

• PowerConnect 2824: Can't access web management using VLAN TAG 1?

  Let's say I have port 20, which is a member with LABEL of VLAN 1, 10 and 20.

  If I try to access web management to help interface VLAN 1 TAG, it is not accessible.  However, if I remove the tag VLAN (and the default PVID value of 1), then it works fine.

  Is this a known limit?

  In addition, change the management VLAN on my 2824?  (what I read, it is not possible)

  You're right about the two statements.  The Web GUI is accessible only through the untagged VLAN 1 and it is not possible to change the management VLAN on the 2800 Series switches.  On the other upper level switches, you can use the ip address command vlan xx to move the management VLAN in the VLAN specified in the statement.

  I hope this helps.

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

• 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

• management of VLANs 5224

  Hello

  I need to split my 5224 into 2 VLANS.

  I created a second VLAN (222) and configure the ports for it (11-16)

  However, I can not then remove these ports in vlan 1. The web interface won't let me mark it as white

  They must be completely separated from each other. clearly, I don't want ports (11-16) in the two VLANS.

  any suggestions?

  Hello

  This command help me solve the problem. I group the switch in blocks of ports and used the above command for a group of ports with the same command to vlan 222 for the other game. I left 1 port on the vlan by default for management purposes.

• traffic on PowerConnect 28XX series

  Anyone know if there is any parameter to specify traffic on the Dell PowerConnect 2816 or 2824 manageable web?

  The 2800 is a low access of range switch.  It doesn't have the ability to limit traffic on a connection.  The CoS allows allows you to set priority on different traffic that's different levels.

  If that connection and traffic is not managed correctly you will need to look for a switch upgrade which has more than a full set of features that allows the specific traffic shaping.

• Management and Vlan native in different subnet?

  Can I have a management ip and vlan native in a different on AIR-1242 switch subnet and 2960?

  Native on switch = 1.

  The interface vlan 100 = 10.10.1.25X 24

  BVI ip to the vlan 100 = 10.10.1.25X 24

  -HM-

  Hello

  As far as I know, the management and the native will be the same... I guess... You have Vlan native as 1 on the switch and Int Vlan 100 on routing switch? Am I wrong? Let me know what are your needs... which will help me to help out you!

  for your question...

  Normally, we specify him vlan native on the switch and the AP so that communication happens... communication won't happen if there is a match of...

  Looking forward to hear from you!

  Let me know if that answers your question...

  Concerning
  Surendra
  ====
  Please do not forget to note positions that answered your question and mark as answer or was useful

• How the Apple Watch manages activities when I switch the time zone?

  How the Apple Watch is managing the activities and objectives when I change the time zone?

  On a long distance flight with a time zone difference of nine hours, what would be the best time to switch to the time zone of the airport of destination, so that the objective of settlement can be completed, even if there is a shorter nine hour day?

  I did mine on the plane, he took no effect until he got a signal when we arrived at the airport. I guess you must ensure that your rings are made before you change the time zone.

  I found that you had to get all your exercises in the hours that were left in your day shortened to your destination.

• This should be easy but... VLANS and switches

  I have 2 switches Dell 6224 is in Vlan35 and the other is vlan110 - I have an Ethernet cable connecting a switch to another - the port on the vlan 110 arrives but the port on the vlan 35 does not work - I want to access the vlan switch 110 of vlan 35 - what should I add to my config so that it works?

  Thank you very much

  Eric

  When you need two different VLANS to communicate with each other if you have enabled an L3 device on the network to perform routing. Your 6224 ToR may already setup for VIRTUAL LAN routing. In the config, it will have the command # ip Routing. Then the switch should just an IP address for each VIRTUAL local area network, and can then route between the VLANS.

  Example of possible configuration:

  6224 ToR

  VLAN 1 = 192.168.1.1
  VLAN 35 = 192.168.35.1
  VLAN 110 = 192.168.110.1
  # ip Routing
  # int port-channel 1
  switchport mode trunk #.
  # permit switchport trunk vlan add 35 110

  6220

  VLAN 1 = 192.168.1.2
  VLAN 35 only = no IP address
  VLAN 110 no = no IP address

  port-channel int # 1 (connection to ToR 6224)
  switchport mode trunk #.
  # permit switchport trunk vlan add 35 110

  port-channel int # 2 (connection iSCSI 6224)
  switchport mode access #.
  # switchport access vlan 110

  iSCSI 6224

  VLAN 1 = 192.168.1.3
  VLAN 35 only = no IP address
  VLAN 110 no = no IP address

  port-channel int # 1 (connection to 6220)
  switchport mode access #.
  # switchport access vlan 110

  You can also try to continue in the way of the use of the static routes for everything, I don't know how this will work.

• Config port / VLAN on switch MXL

  I'm not a network engineer, but I try to set a port to my MXL switch to a VLAN that will route traffic on virtual machines on a local network of calculation.

  This is the port Te 0/52 on the back of the MXL and I am running ESXi on servers in my m1000e.  In fact, I have two MXLs in the tissue A of the m1000e configured with VLT via the interfaces of the FourtyGig.  This part has been implemented by people of Dell Tech Services, making the installation.

  Here's what looked like the config to start:

  dsa1 #show vlan

  Codes: *-Default VLAN - VLAN, GVRP, R - G remote control Port Mirroring VLAN, P - primary, C - community, I - isolated
  O Openflow
  Q: U - no identified, the T - tag
  x - unidentified Dot1x, X - Dot1x tag
  o - unidentified OpenFlow, O - OpenFlow tag
  G - GVRP tag, M - Vlan-stack, H - VSN tagged
  i unidentified intern, I - labeled internal, untagged, V v - VLT - VLT tag

  Ports Status Description Q NUM
  * 1 U active Po33 (0/33.37 Fo)
  U Po41 (Te 0/41-44)
  Te U 0/1-32
  115 active Mgmt T Po41(Te 0/41-44)
  V Po33 (0/33.37 Fo)
  Te T 0/1-32
  486 active VMGuest T Po41(Te 0/41-44)
  V Po33 (0/33.37 Fo)
  Te T 0/1-32
  Te U 0/49-50

  And I wanted to add VLAN 1000 to calculate, so I did the following:

  dsa1 #conf

  dsa1 (conf) #interface Te 0/52
  dsa1 (conf-if-you-0/52) #show config
  !
  interface TenGigabitEthernet 0/52
  no ip address
  MTU 12000
  hybrid portmode
  switchport
  FlowControl rx tx off
  spanning tree rstp edge port bpduguard stop-on-violation
  no downtime

  dsa1 vlan (conf) #interface 1000
  dsa1 (conf-if-vl-1000) #show config
  !
  interface Vlan 1000
  Description information
  name computer
  no ip address
  Tagged TenGigabitEthernet 0/1-32
  Unmarked TenGigabitEthernet 0/52
  no downtime

  VLAN now looks like:

  dsa1 #show vlan

  Codes: *-Default VLAN - VLAN, GVRP, R - G remote control Port Mirroring VLAN, P - primary, C - community, I - isolated
  O Openflow
  Q: U - no identified, the T - tag
  x - unidentified Dot1x, X - Dot1x tag
  o - unidentified OpenFlow, O - OpenFlow tag
  G - GVRP tag, M - Vlan-stack, H - VSN tagged
  i unidentified intern, I - labeled internal, untagged, V v - VLT - VLT tag

  Ports Status Description Q NUM
  * 1 U active Po33 (0/33.37 Fo)
  U Po41 (Te 0/41-44)
  Te U 0/1-32
  115 active Mgmt T Po41(Te 0/41-44)
  V Po33 (0/33.37 Fo)
  Te T 0/1-32
  486 active VMGuest T Po41(Te 0/41-44)
  V Po33 (0/33.37 Fo)
  Te T 0/1-32
  Te U 0/49-50
  1000 active Compute T Te 0/1-32
  Te U 0/52

  But I wanted to add THAT VLT Po33 tag to the new VLAN because there is in others, not because I really understand what it does.  In my view, it is used for load balancing?  If I label it with the command 'tag Po33' in the config of vlan, out with the status "T" instead of "V".

  Here are the details of the VLT:

  dsa1 #show vlt detail
  Local LAG Id counterpart LAG Id status Local Peer status Active VLAN
  ------------  -----------  ------------  -----------  -------------
  41 41 UP UP 1, 115, 486
  dsa1 #show brief vlt
  VLT area in brief
  ------------------
  Domain ID: 100
  Role: secondary
  Primary role: 4096
  ICL Link Status: to the top
  Status of heart rate: upward
  VLT Peer status: to the top
  The local unit ID: 0
  Version: 6 (4)
  Local system MAC address: f8:b1:56:09:70:b1
  MAC address of the remote system: f8:b1:56:09:70:fd
  Configured the system MAC address: 00:01:00:01:00:01
  Version of the remote system: 6 (4)
  Restore delay timer: 90 seconds
  Delay-restore Abort threshold: 60 seconds
  Routing peer: disabled
  By the peer-routing-Timeout timer: 0 seconds
  Multicast peer-routing timeout: 150 seconds

  So my questions are, I'm on the right track?  It will do what I want it to do is send traffic on port 0/52 Te which is labeled in ESXi with 1000 VLAN?  Should I worry the VLT marking stuff and if yes, how should I do the VLT marking rather than normal marking?

  The connection only 1 port of MXL 1 to a device, this device is considered a switch/host an orphan. A VLT connection will have 1 port each MXL placed in a port channel and connected to a device.

  Here is a good article that covers the VLT in use with different Topologies.

  http://Dell.to/1wfDl3n

  And the User Guide is a good source to have as well.

  http://Dell.to/1Hy70bb