03-22-2021 12:04 AM
Dears,
We set up a MW P2P link between branch and HQ to get internet from HQ and it's working fine as per the topology attached.
My branch devices and Pcs are configured with IPs from subnet: 192.168.99.0/24 GW: 192.168.99.1 and all within vlan 1.
so the traffic from My PC is passing along the way to broadband modem GW:192.168.99.1 and then access the internet just fine and as you see we have simple design.
What I need to do is to be able to access the MW IPs for management from My PC and I am searching for the best practice. I am thinking about creating a new vlan for MW management traffic on L3-sw and change port F0/1 to trunk and then enable IP Routing. Would this configuration work with me?
Thanks ..
03-23-2021 06:29 AM
Dear Paul,
I tried configuring MW IP as secondary under vlan 1 but it didn't serve me good. I still need to change my pc ip to be within MW subnet then I can access. And what I understand by adding SVI on SW, it enables you to manage the SW and set the SW as GW. also SW needs to perform routing between 192.168.0.0/24 and 192.168.99.0/24 so how SW would do that when having two different subnets under vlan 1..
I am planning to do what Georg suggested that i add different vlan for MW even though I can't get my head around how it will work and how the tagging of vlan 1 and vlan 5 will occur on the trunk. but worth trying ..
03-23-2021 09:14 PM - edited 03-24-2021 01:27 AM
Hello
I tried configuring MW IP as secondary under vlan 1 but it didn't serve me good.
I would say thats because the switch is currently running as a host device - you need to enable ip routing , add the secondary ip and a default static route (instead of a default gateway) towards your modem then you could assign a host in vlan1 with a ip address of the mw subnet
Alternatively you can create an additional L2/L3 vlan of the mw subnet and assign a host to that subnet -either way I would say ip routing is required to be enabled on the switch.
03-24-2021 01:24 AM
On a side not, I think 'ip routing' is already enabled, looking at the configuration posted earllier in this thread...
no aaa new-model
ip subnet-zero
ip routing
!
vtp mode transparent
!
!
spanning-tree mode pvst
spanning-tree extend system-id
03-24-2021 05:13 AM - edited 03-24-2021 05:14 AM
Dear Paul,
your suggestion doesn't meet my requirement as I need to access MW subnet from Lan subnet. If I assign ip to my pc from MW subnet, it works well under vlan 1 without the need for another vlan.
Dear Georg,
I added the SVI of VLAN 2 for MW management and assign ip address to it from MW subnet. Also, I enabled trunk on interface connected to MW. then set default GW on my pc to the SW instead of modem as well as adding default route pointing to the modem from the SW. But it didn't work and i couldn't access MW subnet from my lan subnet.
I came to conclusion that MW linkra doesn't understand vlans and only understand native traffic since there is only one cable as there are other MW brands provide two cables for data and management.
For now I will keep changing my pc ip address whenever I need to..
Thank you all for the efforts and replies.
Best Regards
Asem
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide