nzschooltech
IS-IT--Management
This is an interesting technical point, I'd be interested in comments.
When we started out with our IP500, our internal network consisted of a 510 address subnet on 192.168.0.0 through to 192.168.1.255. As you know, under the old classful addressing system that was originally defined for IPv4, the netmask is always a minimum of 24 bits and thus this range of addresses has a minimum of 256 subnets, from 192.168.0.0 to 192.168.15.0 and each subnet has 254 addresses (allowing for .0 and .255 not being useable).
Before we got the IP500 we had started with 192.168.0.0 as our network with the 24 bit netmask, later on we had two DHCP servers so each was set up for one half of a subnet of 510 addresses with a 23 bit netmask. Everything worked on it except one printer, after all Classful addressing was abolished in 1994? and this is 15 years later so you would think so.
Then along comes the IP500 and they want IP addressing for the system unit and the phones, so I said "We will change the netmask to 20 bits and give you 192.168.2.0 as the netmask should give us all the way up to 192.168.15.0 in one big subnet if we want to". And so, that was set up, except that there were a lot of problems with the Phone Managers on some PCs that wouldn't communicate with the IP Office, and the IP Office Manager configuration application kept throwing errors.
To cut a long story short we arranged to move every single device on our network to 172.x.x.x private addressing range which can have a netmask of only 16 bits minimum and a subnet of up to 65534 addresses. Then all the error messages and non working functionality problems magically ceased.
I guess you could presume, like our printer manufacturer (Xerox), this is one feature that Avaya haven't bothered to address in the hardware (which still prints out "Network Alchemy" messages in places).
When we started out with our IP500, our internal network consisted of a 510 address subnet on 192.168.0.0 through to 192.168.1.255. As you know, under the old classful addressing system that was originally defined for IPv4, the netmask is always a minimum of 24 bits and thus this range of addresses has a minimum of 256 subnets, from 192.168.0.0 to 192.168.15.0 and each subnet has 254 addresses (allowing for .0 and .255 not being useable).
Before we got the IP500 we had started with 192.168.0.0 as our network with the 24 bit netmask, later on we had two DHCP servers so each was set up for one half of a subnet of 510 addresses with a 23 bit netmask. Everything worked on it except one printer, after all Classful addressing was abolished in 1994? and this is 15 years later so you would think so.
Then along comes the IP500 and they want IP addressing for the system unit and the phones, so I said "We will change the netmask to 20 bits and give you 192.168.2.0 as the netmask should give us all the way up to 192.168.15.0 in one big subnet if we want to". And so, that was set up, except that there were a lot of problems with the Phone Managers on some PCs that wouldn't communicate with the IP Office, and the IP Office Manager configuration application kept throwing errors.
To cut a long story short we arranged to move every single device on our network to 172.x.x.x private addressing range which can have a netmask of only 16 bits minimum and a subnet of up to 65534 addresses. Then all the error messages and non working functionality problems magically ceased.
I guess you could presume, like our printer manufacturer (Xerox), this is one feature that Avaya haven't bothered to address in the hardware (which still prints out "Network Alchemy" messages in places).