Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 8 of 8
  1. #1

    Question Assign IP address to each switch

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Hello,

    I have a bunch of TL-SG2210P & TL-SG2424 (T1600G-28TS 2.0) and I would like to administer them from my desk without having to physically plug on each.

    I created a VLAN dedicated to administration and configured this VLAN (to spread) on every switches

    From one switch, I assigned 192.168.33.2 IP address to the VLAN:
    Name:  vlan33.png
Views: 0
Size:  16.7 KB

    The problem is when accessing 192.168.33.2, I get on the "nearest" switch but not the one I set the IP on.

    I guess it was not the solution to assign the IP address to the VLAN: How to correctly assign an IP address each switch?

  2. #2
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    Quote Originally Posted by rakotomandimby View Post
    I have a bunch of TL-SG2210P & TL-SG2424 (T1600G-28TS 2.0) and I would like to administer them from my desk without having to physically plug on each.
    Assign each switch a different IP in the System (Default) VLAN. For example, my five switches have IPs 192.168.1.250, .251, .252. .253 and .254. I have no idea why you think that you would have to physically connect to the switch to reach its web UI. Of course the web UI can be accessed from any device which is also connected to the subnet the switch is in.

    If you use a management VLAN different from the System VLAN, make sure to set the management VLAN on the switches requiring it. As for the T1600G you set the management IP(s) in menu "Routing" (where you did create the IPs for VLANs). Just enable or disable Admin status according to your needs.

    See also http://www.tp-link.com/no/faq-956.html
    Last edited by R1D2; 11-05-2017 at 10:11.

  3. #3
    Thank you for your answer, but that doesnt work.
    I dont use 192.168.0.0/24 anywhere on my network, and I cant figoure out how to route the traffic for 1 IP address to get to one switch

  4. #4
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    Sure it does work. I do this all the day. A switch is not a router and you can use any IP to go to the switch independent of your network addressing scheme.

    But I wonder why you don't just assign free static IPs from your network to the switches? What exactly is the problem in doing so?

  5. #5
    In recent switches, you wont assign an IP address to the switch but to the VLAN.
    But the VLAN is spread across 6 switch here.
    If I assign the IP address to the VLAN, the whole VLAN, spread across the whole 6 switch has this IP address
    And I dont get in the right switch! (couldnt find on which one I get yet)

  6. #6
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    I still don't get your problem.

    In recent switches you assign an IP to the switch's interface of a VLAN. So, if you use VLAN 6 you assign the first switch's IP to the first interface on the first switch, the second switch's IP to the second interface on the second switch and so on.

    For example, I use 192.168.1.250 for the first switch on VLAN 1, which is spread to all other switches. The second switch has 192.168.1.251 on its own interface for VLAN 1, the third switch has 192.168.1.252 on its interface for VLAN 1 and so on. I can easily address each switch from any member of VLAN 1.

    Maybe, confusion did arise because you think that the VLAN has an IP. A VLAN never has an IP. It's the switch - more precisely: the switch's interface - which has an IP. You need this IP only for routing into a VLAN (if you use Inter-VLAN routing at all) or for accessing a particular switch over this VLAN.

    Just imagine that the VLAN is a separate subnet, then it should become very clear that two interfaces on the same subnet never can share the same IP.
    Last edited by R1D2; 11-08-2017 at 12:56.

  7. #7
    Let me explain more, I hope it will be clearer.

    Step 1:

    Initial configuration is this way:
    Name:  vlan33-00.png
Views: 0
Size:  12.7 KB
    I have 2 switches:
    8 port manageable
    24 ports manageable

    Factory settings are 192.168.0.1 / admin / admin

    I created Vlan 33, tagged, on one port of each switch.

    Step 2:
    I I plug on the 8 ports get into it via 192.168.0.1 and setup an IP to Vlan 33, as this is the recommended way according to http://www.tp-link.com/no/faq-956.html
    Name:  vlan33-01.png
Views: 0
Size:  17.2 KB

    Step3:

    I want to do the same on the 24 port. I plug on the 24 ports, get into it respectively via 192.168.33.5 and 192.168.0.1: I notice the setting Vlan33 has propagated and Vlan33 has already the IP address I assigned through the 8port!
    Name:  vlan33-02.png
Views: 0
Size:  18.4 KB

    Among that, when I access 192.168.33.5 when plugin either on the 8 ports or the 24 ports: I always get on the 24 ports! (I can see the 24 ports in the web interface)

    So the question is: How to assign IP address to the switch, not to the Vlan?

  8. #8
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    Again: you are not assigning IPs to a VLAN. You cannot assign IPs to a VLAN, that's impossible.

    You assign IPs to an interface into a VLAN. A switch's interface is not the VLAN, it's an interface, albeit this interface can be a "door" into a VLAN.

    The solution is simply to assign different IPs (192.168.0.1, 192.168.0.2, 192.168.0.3 etc.) to different switch interfaces to be able to reach them.
    Of course, if you assign the same IP to different switch interfaces, this cannot work. How should a switch know which one you want to reach?

    See your picture in post #1: it's a list of interfaces, it is not a list of VLANs. The VLAN ID, Mode, IP and so on belong to the interface. Maybe it helps if you give those interfaces a distinct name such as "switch1", "switch2", "switch3" etc. on the different switches to realize the difference.

    Also, 192,168,0,1 isn't a valid IP: change commas into dots to make it an IP.
    Last edited by R1D2; 11-14-2017 at 17:36.


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.