Information Technology

Network Service Requests

This webform is intended for UBC IT and department IT administrator use only.

Please direct any other requests and incidents, including those for ResNet service, to the UBC IT Service Centre who will ensure your request will be directed accordingly.

Service Request or Incident? How to distinguish between a service request and an incident.

Not sure how to fill out the form? If you require a consultation regarding your network requirements, choose the "Other" option from the drop down list of services and indicate you require a network consultation. Please provide as much information as possible.

For systems-related requests like virtual servers, storage and backup, please use the Systems Service Requests form.

* = Required Field

What is an INCIDENT?


An incident is an unplanned interruption to an IT service or reduction in the quality of an IT service. The service has already been provisioned and deployed, was working properly, but has suddenly stopped functioning.


Examples:

  • Cannot access wireless network
  • Intermittent connectivity problems
  • Was connected to network, but does not work
  • Network port does not work any longer

Report incidents to the Network Trouble Line at 604-822-1380 or create a ticket at http://www.it.ubc.ca/helpdesk. Please note that for incidents reported after hours, only critical incidents will receive immediate attention while others will be processed during regular business hours.



What is a SERVICE REQUEST?


A service request is a request for information, advice, a standard change (add/modify/delete), or access to an IT service.

Examples:


  • New employee requires access to Transmogrifier
  • Add, update, delete contact information in the network database
  • Need access through firewall
  • Add a VPN pool
  • Add, move or delete a VLAN
  • Apply for a new DNS subdomain
  • Migrate existing environment to a new virtual network
  • A need for network consultation service

Submit service requests through http://web.it.ubc.ca/forms/network/

Your Information

Requestor

If you are an external customer without a CWL login, please enter "guest"

Technical Contact



Request Details



Looking for systems related services?
  • Access Permissions
  • Contact information Database
  • Data Centre Networking
  • DNS
  • Firewall
  • Identity Based Wireless
  • Load Balancing
  • Network Security Scanning
  • Virtual Network
  • VLAN
  • VPN
  • VRF
  • General Inquiry
  • Other
  • Cable Installation
  • Construction Trailer IT Setup
  • Data Port Activation
  • IT Facilities
  • UBC Internet Installation
  • non-UBC Internet Installation
  • Shaw Cable TV
  • Wireless Access Points
  • Other
Add Modify Delete
Add Modify Delete
Add Modify Delete
Add
Add Delete
Add Modify Delete
Add Modify Delete
Add Modify Delete
Add Modify Delete
Add Modify Delete
Modify Delete
General Network Inquiry
Other Network Request
Request Network Security Scan
Fibre Copper Coax
Report a Problem
Install
Data TV
Add
New Upgrade
Install Remove
General Inquiry
Add Move Change
mm/dd/yy



How to determine the urgency

Please assist us in serving you better by advising us on the urgency of your request:

Low Request is not timely in nature; request follows standard fulfillment processes.
Medium Request is timely; request follows standard fulfillment processes.
High Request is urgent; request to be completed within the soonest possible timeframe.

The time required for provisioning is directly proportional to the scale, urgency and complexity of the request. Requests will be attended to as soon as possible. Due to high volumes, requests will be prioritized accordingly in consideration of all criteria.

Technical Details

Please provide us with the appropriate additional information to better respond to your request.

Administrative Contact



 

Subdomain Details

Please submit subdomain requests for third-level domains only, i.e. subdomains falling directly under ubc.ca, for example,yourorg.ubc.ca. Administrators have full access in myDNS to create lower-level domains, e.g. subdomain4.yourorg.ubc.ca.

Enter the fully qualified domain name e.g. xyz.ubc.ca
Department of Human Kinetics
Providing instruction in human kinetics. All correspondence and courses use the acronym "hkin" for this department.
CWL ID or myDNS group
For more information about subdomains, please visit the IT Service Catalogue.
For Subdomain Registration guidelines, please refer to our documentation here.

Nameserver Information

If UBC's nameservers will not be authoritative for the domain, please provide the names and IP addresses of the nameservers to be used.

NameIP
NameIP

 

Subdomain Details

Enter the fully qualified domain name e.g. xyz.ubc.ca
CWL ID or myDNS group

Nameserver Information

If UBC's nameservers will not be authoritative for the domain, please provide the names and IP addresses of the nameservers to be used.

NameIP
NameIP

 

Subdomain Details

Enter the fully qualified domain name e.g. xyz.ubc.ca
CWL ID or myDNS group

Nameserver Information

If UBC's nameservers will not be authoritative for the domain, please provide the names and IP addresses of the nameservers to be used.

NameIP
NameIP
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
Network name is 4 letters and 2 digits, e.g. MATH01
If this is to add to an existing VRF in Virtual Network, provide name of VRF (or N/A)
Name of the vlan/subnet to be added (maximum 16 characters) e.g. SERVERS
Maximum number of hosts to reside on this subnet (size of IP subnet required).


Private addresses are available to virtual networks only.


If not myDNS, please specify which IP addresses to relay to. (maximum two IP addresses)
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
Network name is 4 letters and 2 digits, e.g. MATH01
If this is in an existing VRF in Virtual Network, provide name of VRF (or N/A)
Name of the vlan/subnet to be added (maximum 16 characters) e.g. SERVERS
Maximum number of hosts to reside on this subnet (size of IP subnet required).




If not myDNS, please specify which IP addresses to relay to. (maximum two IP addresses)
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
Network name is 4 letters and 2 digits, e.g. MATH01
If this is in an existing VRF in Virtual Network, provide name of VRF (or N/A)
Name of the vlan/subnet to be removed (maximum 16 characters), e.g. SERVERS
x.x.x.x
Indicate the data centre network, e.g., GRID02, GRID03
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
If this is to add to an existing VRF in Virtual Network, provide name of VRF (or N/A)
Maximum number of hosts to reside on this subnet (size of IP subnet required).


Indicate the data centre network, e.g., GRID02, GRID03
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
If this is in an existing VRF in Virtual Network, provide name of VRF (or N/A)
Maximum number of hosts to reside on this subnet (size of IP subnet required).


Indicate the data centre network, e.g., GRID02, GRID03
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
If this is in an existing VRF in Virtual Network, provide name of VRF (or N/A)
x.x.x.x

Note: Please download the virtual network template and provide the necessary information, so that we may process your request more quickly. Attach the template to this request by uploading the document using the attachments field below.

Desired Name of new Virtual Network to be added.
Description of the intended usage of proposed new Virtual Network.
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
Provide name of VRF. Name of VRF should be in format XXXX-YYYYYYYY where XXX is your org unit 4 letter code and YYYYYYYY is an 8 letter max name string.
Only list out existing VLANs/Subnets to be routed behind new VRF. (If new VLANs/Subnets required for this new VRF, please also submit a VLAN add request and quote this new VRF request).
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
Provide name of VRF

Provide details of change requested

Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
Provide name of VRF
Confirm names of the VLANs/subnets to also remove or specify which to migrate to another VRF
Name of VPN Pool.
The suffix is what users will append to the end of their CWL usernames for myVPN logins.  Login format is [cwlusername].[suffix].  The suffix is usually an abbreviated faculty/departmental code.  Example login:  joesmith.ubcit or janedoe.chem.
Specify the maximum number of concurrent VPN clients expected. Please help conserve IP address space by only specifying what is needed.
(If applicable) Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
(If applicable) If this is to add to an existing VRF in Virtual Network, provide name of VRF (or N/A)
List CWL Account(s) to be given self-manage access to add/remove users from VPN pool usage.
Initial list of CWL Account(s) to allow VPN pool usage.
Indicate any unused subnets allocated to your department to be used for the VPN pool.
Please elaborate on any existing VPN you may have.
Name of VPN Pool.
The suffix is what users append to the end of their CWL usernames for myVPN logins.  Login format is [cwlusername].[suffix].  The suffix is usually an abbreviated faculty/departmental code.  Example login:  joesmith.ubcit or janedoe.chem.
x.x.x.x
Name of VPN Pool.
The suffix is what users append to the end of their CWL usernames for myVPN logins.  Login format is [cwlusername].[suffix].  The suffix is usually an abbreviated faculty/departmental code.  Example login:  joesmith.ubcit or janedoe.chem .
x.x.x.x

NMC only handles network related requests with respect to load balancers. The majority of client requests should be directed through the Systems Service Requests form.


Name of Virtual Network load balancer is to be added to.
Provide name of new or existing VRF where Virtual Load Balancer networks shall route behind.
Size of subnet required for public-facing Virtual IPs.
Size of subnet required for internal source-NAT private Virtual IPs.
List out any proposed names of new load balanced VRFs with this Virtual Network. VRF name should be in the format XXXX-YYYYYYYY, where XXXX is organizational unit and YYYYYYYY is any character string (max 8 characters). (e.g. MATH-DMZ, MATH-SERVERS, MATH-DESKTOPS).
List out existing or new VLANs/Subnets to be a part of new Virtual Load Balancer and indicate which load balanced VRF they will be a part of as per load balanced VRF Names listed above.

NMC only handles network related requests with respect to load balancers. The majority of client requests should be directed through the Systems Service Requests form.


Name of the Virtual Network where LB resides.

NMC only handles network related requests with respect to load balancers. The majority of client requests should be directed through the Systems Service Requests form.


Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01).
Provide name of existing VRF where Virtual Load Balancer networks route behind.
Confirm subnet of any public-facing Virtual IPs to remove
Confirm subnet of any internal source-NAT private Virtual IPs to remove.
Confirm names of VRFs to also remove.
Confirm names of the VLANs/subnets to also remove or specify which to migrate to another VRF.
e.g. 80, 443
e.g. 80, 443
e.g. HTTP, SFTP
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
If this is to add to an existing VRF in Virtual Network, provide name of VRF (or N/A)
Name of the vlan/subnet to be added (maximum 17 characters), e.g., MATH-SERVERS
Maximum number of hosts to reside on this subnet (size of IP subnet required).




If not myDNS, please specify which IP addresses to relay to. (maximum two IP addresses).
The suffix is what users will append to the end of their CWL usernames for myVPN logins.  Login format is [cwlusername].[suffix].  The suffix is usually an abbreviated faculty/departmental code.  Example login:  joesmith.ubcit or janedoe.chem.
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
If this is in an existing VRF in Virtual Network, provide name of VRF (or N/A)
Name of the vlan/subnet to be added (maximum 17 characters), e.g., MATH-SERVERS
Maximum number of hosts to reside on this subnet (size of IP subnet required).


Change the Internet access.


Change the DHCP requirement.
If not myDNS, please specify which IP addresses to relay to. (maximum two IP addresses)
The suffix is what users will append to the end of their CWL usernames for myVPN logins.  Login format is [cwlusername].[suffix].  The suffix is usually an abbreviated faculty/departmental code.  Example login:  joesmith.ubcit or janedoe.chem.
Name of the Virtual Network that encompasses all your vlans and VRFs (should be 4 letters and 2 digits, e.g., MATH01)
If this is in an existing VRF in Virtual Network, provide name of VRF (or N/A)
Name of the vlan/subnet to be added (maximum 17 characters), e.g., MATH-SERVERS
x.x.x.x
The suffix is what users will append to the end of their CWL usernames for myVPN logins.  Login format is [cwlusername].[suffix].  The suffix is usually an abbreviated faculty/departmental code.  Example login:  joesmith.ubcit or janedoe.chem.

Contact Information



Network name is 4 letters and 2 digits, e.g. MATH01
Specify which VLANs to add VLAN Manager to

Note: In order to obtain access to tools, you must already exist in our NMC Contacts DB and have a CWL ID. If applicable, please open a separate request to be added and arrange for a CWL ID before requesting access to these tools.

Tools


Note: This service is only available to SAQ C & D UBC merchants who require network scans to meet PCI compliance.

mm/dd/yy
When selecting a scan date/time, keep in mind that scans may take several hours or days to complete depending on the number of IPs scanned.
Name of the building.
Address of the building.
Specify rooms in which the installation is to take place.

UBC TV is a basic digital cable service which requires a digital box from Shaw Cable.

This trouble form is for issues that cannot be resolved by Shaw Support. Customers who are having issues with their Shaw digital box must contact Shaw directly for support at 604-310-SHAW (604-310-7429) or https://community.shaw.ca/welcome.

If you are having trouble with the Cablevision service, please change your Request Details above to:

  • Your Request Relates To: Network Management - DNS, Firewall, Load Balancing
  • Service: Other
Address of the construction site.

UBC IT can provide the base CATV connection which provide a bulk group of Shaw channels as well as digital capabilities. For further digital capabilities including activation of HD boxes please contact Shaw.

Name of the building.
Address of the building.
Specify rooms in which the installation is to take place.


Specify any labels on the CCT outlet
Name of the building.
Address of the building.
Specify rooms in which the installation is to take place.




Name of the building.
Address of the building.
Specify rooms in which the installation is to take place.
Name of the building.
Address of the building.
Specify rooms in which the installation is to take place.
Add
e.g. 80, 443



Select all that apply
Please enter details on the use or purpose of this new subdomain that would be helpful to reviewing this request.