IP Phone System - Access From Another VLAN

[CHiLL]

A couple of years ago, we had our network upgraded by a third party. During that, we moved from a 10.122.xxx.xxx IP convention to 10.22.xxx.xxx, now utilising VLANs.

 

Our third party set up a VLAN specifically for the IPT system, which was VLAN 40 with an IP range of 10.22.40.0/24.

 

However the provider of the IPT did not (and will not) switch the IP convention to the new one. So it is still running on the old VLAN 40, with an IP address range of 10.122.40.xxx.

 

Our third party created some form of routing, so that any device on the new VLAN 40 was able to access the IP ranges 10.122.40.xxx.

 

Now, we have been advised by the IPT engineers that we can perform some changes ourselves, such as handset renaming/renumbering and save the call out cost. We just need to access the IPT controller, on 10.122.40.10. The only VLAN that can do it is VLAN 40, and I don't want to have to connect to a specific port which is configured only on VLAN 40 at the moment (plus access to the switch is limited, due to the room being in use). Nor do I want to change port VLANs on other switches if I can help it.

 

Ideally, I would like to browse from my own VLAN (10.22.100.xxx) to the IP address of the IPT controller (10.122.40.10).

 

Is this possible?

[Michael]

If you nominate a switch port which is tagged with both VLANs, then of course you can access the controller via your native range. This would be the easiest/logical solution to your issue.

[CHiLL]

Thanks for the info, though I'm not exactly sure how to go about that on out HP ProCurve switches.

[CHiLL]

I'm far too late to amend the original post, but I'm going to add a more detailed description of the issue:

 

Back in summer 2015, we had a third party contractor replace our wired and wireless networks, server infrastructure and a bunch of other things. Included in this was redesigning the network from scratch.

Our old network was on the 10.122.xxx.xxx IP range.

Our new network is on the 10.22.xxx.xxx IP range.

 

There is now nothing on 10.122.xxx.xxx, except for our IPT phone system, which has a controller on a static IP of 10.122.40.10, along with access points for the phones, also with static IP addresses in that range. However, the IPT system is not owned or controlled by us, it is leased and supported by a contractor, who charge for callouts.

 

Our main VLAN is 10.22.100.0/22 - however I cannot ping 10.122.40.10.

 

The contractor who upgraded our network created 'VLAN 40' on 10.22.40.0/24, with DHCP disabled (by design - as it causes major issues with our phone access points when it is enabled).

 

I have Port 4 on an edge switch untagged on VLAN 40. When I connect a laptop and set a static IP address of 10.122.40.50 (yes, that is 10.122.xxx.xxx - not 10.22.xxx.xxx), I can ping 10.122.40.10 and connect to its web interface.

 

My problem is that I do not always have physical access to that switch, as the cab is in a meeting room. Is it possible for me to access that web interface from any machine on VLAN 100? If so, how would I go about getting it to work?

 

Edit:

Upon checking the switch, it is true that port 4 of the edge switch is on VLAN, however I cannot determine the IP address range of that VLAN...I'm not sure how. I can ping 10.22.40.1 from my own workstation on VLAN 100, so it appears that VLAN 40 is configured as designed by the contractor. I just don't understand how a device on VLAN 40 is configured with 10.122.xxx.xxx instead of 10.22.xxx.xxx and still work.

 

Some steps that I have done:

1) Connected laptop to P4 on the edge switch. Configured the following IPV4 information:

Static IP: 10.122.40.50

Subnet: 255.255.0.0

Default Gateway: 10.122.40.1

I can successfully ping and connect to the IPT controller.

Note: The Ethernet controller displayed in 'Network Connections' shows this network as an 'Unrecognized network'.

 

2) Connected the same laptop to the same P4 on the same edge switch and configured the following IPV4 information:

Static IP: 10.22.40.50

Subnet: 255.255.0.0

Default Gateway: 10.22.40.1

I cannot ping or connect to the IPT controller.

Note: The Ethernet controller displayed in 'Network Connections' shows this network as recognized and shows our domain name.

[LytchettNM]

In answer to your first and main question can you connect to subnet 10.122.40.0/24 which is within VLAN 40 then yes, but you will need to make changes to the core router which could be a switch.

I would leave this alone and get the third party back in that setup your new core network as from the questioned you have asked you do not understand the way your network is setup and making changes without the basic understanding could disable your whole network.

The simplest thing to do would be to get VLAN 40 presented to a switch port on the switch that feeds your support location and have a dedicated computer that you make these changes from, this is a much simpler things to achieve with limited networking knowledge and understanding.

[CHiLL]

Thanks for the replies, though thanks to the borked VLAN implementation by our contractor and no possibility of backing from management to pay for the IPT system to be reconfired (makes sense as it is working...don't fix something that isn't broken)...looks like we're sticking with the way it is!