Jump to Content

Extended Information on PC-IP requests

Introduction

UniSA IPs are allocated only to devices that are registered for the network. The registration is done through the DIPAM database which captures the following information:
• Blue plate
• MAC address
• Location
• User
• Node Name (default is ORG2blueplate)
• Hardware/Vendor

The key piece of information is the MAC address as a DHCP server uses this information to allocate an IP to the individual machine.

Non-10gen IPs

ISTS allocate an IP, per campus, to the registered device on either staff, student or server subnets. It is important to specify on which subnet you need a device to be allocated. There are also filtered and unfiltered ranges (see below).All IPs are indefinitely bound to a MAC address and need to by physically re-allocated in DIPAM in order to change. Devices can have multiple MAC addresses recorded against them (such as a server with two network cards) or multiple IPs bound to a single MAC address, such as for a laptop that needs access at different campuses.

10gen: Dynamic IPs

Devices that do not require a static IP are registered in DIPAM and are allocated a dynamic IP from the DHCP server, the device location is not an issue. A registered device will receive an IP for different subnets depending on the network equipment it is connected to. If connected to a staff network point a staff IP will be allocated.  This provides maximum flexibility for users – simply move a machine to a different building or even campus with no interruption to service. ISTS require that you notify us of ownership and location changes so we can keep DIPAM current but you no longer need to wait for this to be processed to be able to action the change at your end.

 If the MAC address is incorrectly recorded in DIPAM the machine in question will not get an IP.

10gen: Static IPs

For devices such as servers/printers it may be necessary to have an IP address that does not change. In this case you need to specify that you require a static IP in your IP request.  It is particularly important that accurate location details are supplied.

The 10gen project provides better defined network address ranges than previously offered. There are pre-defined ranges for staff, student, servers, printers and security. The valid ranges are generally defined per building. You'll need to keep this in mind when requesting static IPs and when moving equipment. 10gen static IPs can be allocated in either the internal 10.220.* format or the “real world” 130.220.* format. The latter allows servers to “face outwards” and provide incoming requests from the internet.

Unfiltered vs. filtered IPs

IPs are allocated in a filtered range by default. This means that the firewall is in effect (most TCP and UDP ports are blocked to the outside world) and use of the proxy is required for internet access.  If you need to use particular ports or protocols then you will need to submit an Internet Policy Change Request. 

DIPAM Generation

From time to time you may hear that your network registration request will be available after the next "DIPAM generation". This is a manual process that takes a snapshot of the database and creates text files suitable for distribution to the DHCP and DNS servers. Any changes made to DIPAM are not "live" until this is done. DIPAM generations can take from 5-15 minutes and are normally done every few hours. If you do require an urgent change you will need to advise PC-IP so that a generation can be run immediately after the changes you requested have been made.

Vendor IP requests

For equipment purchased through designated suppliers the network registration and blue plate allocation are sent to PC-IP by the supplier before you receive the equipment. It is a requirement of the designated PC suppliers that this be done, any delays should be reported to the ISTS PC-IP team.
It is also important to report any inaccuracies to PC-IP. eg if a vendor's IP request includes an incorrect MAC address

top^