|
|
|
||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||
|
CLydeNET Change Control Procedures |
|
|
||||||||||||||||||||||||
Introduction
It is inevitable
that from time to time sites may wish changes to be made to their ClydeNET
connection infrastructure e.g., ·
Request a
change to the inbound or outbound security acl’s ·
Remove the
inbound and outbound security acl’s due to a local firewall performing the
tasks ·
Request
changes to the IP address information ‘routed’ for the site ·
Request a
change with the router interface connecting to the site LAN ·
Etc If a site wishes
to have a ‘change’ implemented by the ClydeNET operating member then it
should submit a formal request, in writing, to the ClydeNET operations desk.
This procedure will ensure that the ‘change request’ is handled in a timely
manner and that all parties understand the full implications of the ‘change’
e.g., support, operational or cost implications. The ClydeNET operations desk
will only accept a ‘change request’ from a ‘nominated representative’ or other
senior manager: for convenience a
‘change request’ template is provided:
|
|||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||
|
|
|
|
|||||||||||||||||||||||||