GS728TP which router to use to route data and VOIP
Accepted Solutions
All Replies
Hi again. We did buy the two switches as I said earlier but I am still tryiing to get things to work. What I fail to understand is why Netgear have created a Voice VLAN on VLAN 2 and yet the documentation the support person gave me encourages me to create a Voice VLAN! I have done this and made it VLAN 10 and called it VOIP (to have a different name to the VLAN 2 one. I have also changed the Voice VLAN in the relevant page from 2 to 10. We tried it this morning and the VOIP phones did not work, but then tonight I discovered that somehow the switch had lost the route for the phones even though it was there last night. I shall try it again on Thursday this week.
I have noticed that I need to do the latest firmware upgrade because the documentation talk about "Units" and this is not called that on mine.
The documentation seems to imply that all you need to do is plug your phones into the ports and Auto-Voip just prioritises the traffic. It is not that simple. The documentation does not say to set the port as a tagged member of VLAN2, neither does it say you need to remove it as an untagged member of the default VLAN (VLAN 1). It also does not say the PVID needs setting on the port to the VLAN ID of the VOIP VLAN. So I have the phone ports set as tagged onto VLAN 10, the PVID set to 10 and removed the untagged membership of the default VLAN (1).
Because the TP-Link router is not a Layer 3 router I am using static routes which I have proved to work at home on mine in a test environment using a cisco switch, but Smart Switches are new to me. It seems. Also the TP-Link is the only DHCP server on the network and so only provides IP addresses in the default 192.168.1.* range. I have configured the VOIP phones with fixed addresses in the 172.16.1.* range. The VLAN 10 ip address has been set to 172.16.1.1 and the static route on the router points to this address.
I need some time to put a client in the VOIP VLAN and check I can ping the phones from both switches. Attached is a diagram of the configuration so far. I welcome any comments on this setup.
Hi
I spent a whole day on this and could not get it to work - I rang technical support and fair enough he wanted a network diagram but again he could not fix it. I then took the switch home to start again. It took me about 6 hours to program, test and learn how to download the config off the switch and work out how to upload it. This was necessary because I kept losing contact with the switch when I tried to put it in it's own VLAN. So now I can upload the config from a factory reset and carry on where I left off.
I finally got it working yesterday! I had a new Grandstream telephone on the VLAN2 working correctly and two laptops on two other VLANs both getting on the internet. Yes!!
I did manage to work out what was wrong:
1. The documentation you gave me was not as clear as it appeared and right at the end there are two major statements which needed to be mentioned at the beginning! The first of these was "The IP address of the switch must be on a subnet different from the subnets of the VLANs." However this is confusing because what it means is "The IP address of the switch must be set on a VLAN that is different to all other VLANs". In other words I had to create a VLAN just to manage the switch. The second of these was "The IP address of the switch must be on a subnet different from the local subnet of the router." Again another majorly important point put at the end! Until I followed this I had problems
2. Also until I upgraded the firmware to the latest version, Version 6.0.1.18 because when I tried to follow your instructions the screenshots you gave me did not match what I was seeing.
Also I worked out that there is possibly a fault with the firmware of the switch. This is the procedure I followed and this error was repeated each time:
- With my laptop plugged into a port in the default VLAN (VLAN1) I created a VLAN 300 which I untagged on Port g23 only - I then clicked "Apply". The IP of this VLAN was 192.168.150.1. I then changed the PVID for Port g23 to 300 - and I clicked "Apply"
- I then created a static route to 192.168.150.0, 255.255.255.0 - and clicked "Apply"
- I then changed the fixed IP address of the switch to be 192.168.150.2 - and clicked "Apply"
- So far so good I thought. In thoery then when I move my laptop connection into port g23 and change the fixed IP address to be in the same subnet it should be able to contact the switch right?
- No! I had installed the Smart Control Centre Manager software on the laptop, so I ran discover with that and it found the IP address of the switch as 192.168.150.1 - which is the IP address of the subnet! How strange! I had not made a mistake because I re-did this about four times on Thursday and then had to factory reset the switch and start again. I also did this after factory resetting the switch on Friday and after firmware upgrading the switch as described above. Now that I expected this to fail I factory reset the switch and then uploaded my saved configure to avoid having to go through re-creating all the VLANs, routing, port membership and PVID details again.
It seemed that every time I changed the IP address of the switch to go in the Switch Management VLAN it took on the IP of the VLAN. Once I knew that I could log into the switch and change the IP address to 192.168.150.2. I suggest someone from Netgear might like to test this themselves!
Once I followed the golden rules (firmware upgrade the switch before you do anything! and create a VLAN for the switch which is unique to all other VLANs with a static route configured to it on the switch.) I was then able to progress normally.
In the small hours of Saturday morning I went to bed with everything working, I could ping the gateway of the router - I could even ping www.bbc.co.uk and get the friendly name resolved to an IP address but I got no reply - you should get a reply from this website.
After taking a long break I had another re-read of your documentation and someone along the line of resets I had forgotten to re-create the default route which for my router was 0.0.0.0 0.0.0.0 192.168.2.1
It all worked! Then I tried setting up my Grandstream phone on VLAN2 and Untagged the port. This did not work. With my laptop in the same subnet I could not ping the IP of the phone. I tried changing it to Tagged on the port and suddenly it all worked! Strangely it sis not seem to matter whethr I set the VLAN membership on the phone of not, but I left it configured to VLAN 2 on the phone. I was able call and internal call to my sons number which re-directs to his mobile and he was able to call the phone back so traffice was definitely going both ways.
Once I discovered I could print out the running-config file I was much happier. All I have to do now is take the switch back and change the default gateway settings from 192.168.2.1 to 192.168.1.254 which is what it needs to be. This was easy with a print out to read!
I cannot believe how long this has taken to fix. I found it easier configuring a Cisco switch which was a fully managed one.
There are two other things I discovered which I would like changed and that is on the screen to download the configuration it seems to make no sense to me. If I click "Download" I would expect to download the file to my PC. However it downloads the file from the PC to the switch! If I click "Upload" I would expect it to upload a file to my PC but no, it uploads the file from my PC to the switch. This seems to me to be the wrong way round and had me puzzling for ten minuted wondering what was happening.
I also found that with my router I had to set a static route for every VLAN which needed internet access. My router is a TP-Link TD-W9980 and costs arond £70. I have included a screen shot of the working static routes which all point to the VLAN IP address of the VLAN which is untagged in VLAN10 and to which the router is untagged in as well.
I am going to write a PDF document of the exact procedure from beginning to end so when I come back to this later I do not have to go through this learning curve again. I will then upload it to this forum to help anyone else who needs it.
Here is the network diagram of my test arrangement that worked. Note that the switch is on its own VLAN.
