D-Link Forums
The Graveyard - Products No Longer Supported => Hubs and Switches => DGS-1224T => Topic started by: EthanQuix_ on January 27, 2017, 07:56:39 AM
-
Hi D-LINK gurus!
First of all, sorry about my English, i'm from France.
I request some help about VLAN on my switchs:
DGS-1210-24 and 1210-24P:
- Ports 1 to 4 are on VLAN 10
- Ports 5 to 12 are on VLAN 20
- Ports 13 to 24 are on VLAN 30
- Ports 25 to 28 wanted to be on all VLANs
DGS-1210-48:
- Ports 1 to 48 are on VLAN 30
- Ports 19 to 52 wanted to be on all the 3 VLANs
And i need to have 3 port (13, 38 and 39) on only one switch (1210-48) to be on all VLANs mentioned earlier.
How can i do? Can someone help me?
Thanks for all answers guys!
-
Hi,
I'm not sure what your scenario really is or should be: Are those 3 switches isolated or shall they become connected to each other? Or shall they be connected to some other switch or switches not mentioned?
I'll only focus on VLAN configuration. No matter what your scenario might be, consider the following:
First realize that the default state of any of your switches is all ports being members of VLAN 1, where Ethernet frames are sent untagged (egress). For any port its PVID value is set to 1, which means, that any untagged Ethernet frames received (ingress) are assigned to VLAN 1. In addition the management interface is assigned to VLAN 1, and hence if you configure all ports of a switch to be a member of any VLAN other than 1 (in your case: 10, 20 or 30), you will lose connectivity to the switch's management interface!
So, your first decision should be about how to manage the switch. You have two choices:
- If you want to leave the management interface assigned to VLAN 1, you have to reserve one port on any switch to be left in its default VLAN configuration as described above. The advantage is, that only one device attached to that port is allowed to manage the switch, and no other device attached to ports configured to be member of any number of VLANs other than 1 can reach the switch's management address. The disadvantage is, that you need an extra "admin" device to be connected to that port, that can not be used for other purposes. If you select this choice, you have to change your desired port grouping: E.g. take port 24 of any switch to be unchanged and used for administration of the switch only. Connect your admin device to port 24, enter the GUI and start the configuration as described below.
- Select one of our VLANs, say 30, to be the management VLAN. This means the switch can be managed from any device that is assigned to VLAN 30. If you want to select this choice, do the following: Connect to the switch (use any port other than port 24) and enter the GUI. Enter the 802.1Q VLAN configuration and add VLAN 30. Configure VLAN 30: Set port 24 to be an "untagged" member and leave all other ports unchanged (not member). For port 24 set PVID=30. Next configure "802.1Q Management VLAN": Set "Management VLAN" to "Enabled" and set VID=30. After clicking "Apply" you will lose connection to the switch, because the switch's management interface will now be reachable only via VLAN 30 while you are connected to a port configured for VLAN 1. Hence unplug your Admin device from the port and plug it to port 24. Now you should be able to reenter the GUI and continue to configure the switch. Enter the "System Setttings" and change the IP address of your switch to an address that fits the IP network you plan to use for VLAN 30. Again after clicking "Apply" you will lose connection, because your Admin device's IP settings do not fit the new network settings. Hence, configure your Admin device to use an IP address out of the network to be used for VLAN 30 (but different from the switch's management address, of course). Reconnect to the GUI and continue the configuration as described below.
At your two DGS-1210-24 switches:
- If you selected choice [1] above: Create VLAN 30. Configure VLAN 30. If you selected choice [2] above: Continue to configure VLAN 30: Set ports 13-23 to be an "untagged" member. Set ports 25-28 to be a "tagged" member. Leave ports 1-12 in state "Not member". Don't change the configuration of port 24 (the port you are connected to), which is either configured to be an untagged member of VLAN 1 (choice [1]) or VLAN 30 (choice [2]).
- Add VLAN 20. Configure VLAN 20: Set ports 5-12 to be an "untagged" member. Set ports 25-28 to be a "tagged" member. Leave all other ports in state "Not member"
- Add VLAN 10. Configure VLAN 10: Set ports 1-4 to be an "untagged" member. Set ports 25-28 to be a "tagged" member. Leave all other ports in state "Not member"
- Set the PVID of all ports as follows: Ports 1-4: PVID=10, Ports 5-12: PVID=20, Ports 13-23: PVID=30, Ports 25-28: PVID=1. Leave Port 24 as is: Either PVID=1 (choice [1]) or PVID=30 (choice [2])
For your DGC-1210-48 (where I think you meant port 49-52 to be on all VLANs):
- If you selected choice [1] above: Create VLAN 30. Configure VLAN 30. If you selected choice [2] above: Continue to configure VLAN 30: Set ports 1-12, 14-23, 25-37 and 40-48 to be an "untagged" member. Set ports 13, 38, 39 and 49-52 to be a "tagged" member. Don't change the configuration of port 24 (the port you are connected to), which is either configured to be an untagged member of VLAN 1 (choice [1]) or VLAN 30 (choice [2]).
- Add VLAN 20. Configure VLAN 20: Set ports 13, 38, 39 and 49-52 to be a "tagged" member. Leave all other ports in state "Not member"
- Add VLAN 10. Configure VLAN 10: Set ports 13, 38, 39 and 49-52 to be a "tagged" member. Leave all other ports in state "Not member"
- Set the PVID of all ports as follows: Ports 1-12, 14-23, 25-37, 40-48: PVID=30; Ports 13, 38, 39, 49-52: PVID=1. Leave Port 24 as is: Either PVID=1 (choice [1]) or PVID=30 (choice [2])
PT
-
The cost of custom software development varies depending on the size and complexity of your project. Complex applications require more time, planning, and analysis than simple ones. Also, they may require more dedicated developers. Complexity also affects the timeline of development. Fortunately, there are several methods to reduce the overall cost of your custom software project https://mlsdev.com (https://mlsdev.com)