TYPICAL NET CC CHANGES

Map Branches

• RISK SEVERITY Color Key.
  • Major Change. (H)
  • Major Change. (H)
  • Minor Change. (L)
• HARDWARE CHANGES
  • DNS/DHCP server installation.
    • No immediate effect on current Network
      • LOW RISK IF DNS IS NOT CONFIGURED AT INSTALL
        • Complexity of implementation min. None/Min Business risk.
      • HIGH RISK IF SERVER IS CONFIGURED
        • Complexity of implementation med High Business risk.
  • DNS/DHCP server decom.
    • Normally occurs some time after server has stopped service.
      • LOW RISK
        • Complexity of implementation min. None/Min Business risk.
  • DNS/DHCP server move.
    • A server move can have high risks for service
      • HIGH RISK OF SERVICE INTERRUPTION TO USERS.
        • Complexity of implementation high. High Business risk.
  • Console connection addition.
    • Console connection is possible without service interruption
      • WOULD BE SUITABLE FOR WED CC WINDOW
  • Hardware addition.
    • New network card/interface/Increase memory/Add hard disk
      • IF SERVICE FAILS WILL NEED BREAK FIX
        • Complexity of implementation high. High Business risk.
  • Disk Copies
    • Backup process.
      • REQUIRES SERVER OUTAGE TIME
        • Complexity of implementation high. High Business risk.
• DNS SERVER CHANGES
  • Bulk Dns add/changes/deletes.
    • Various Risk Severity
      • MEDIUM RISK AT REMOTE SITE WITH SITE SIGNED APPROVAL
      • HIGH RISK AT DATA-CENTERS IN TOP LEVEL DOMAINS
      • LOW RISK IF SITE OR SUBNETS ARE DECOM STATE
  • Server failure/ Rebuilds.
    • DNS/DHCP will failover and users are not be affected.
  • SSL Certificate updates.
    • Web Interface Service has to be taken off line for 30 mins
      • ONLY EFFECTS WEB INTERFACE
        • Complexity of implementation medium. Low Business risk.
      • RESTRICTS DNS/DHCP CHANGES
        • (untitled branch)
  • DNS ACL/Bogon updates.
    • External Security updates. Requires HUP to DNS daemon
      • LOW RISK, NEVER PREVIOUSLY FAILED
        • Complexity of implementation med. Low Business risk.
  • Subnet creation.
    • Creating Subnets per planners request during migrations.
      • LOW RISK, CAN PUT LOAD ON DATABASE.
        • Complexity of Implementation med. Low Business risk.
  • Patching QIP.
    • Updating QIP versions and . updates.
      • REQUIRES OUTAGE OF SERVER AND SERVICE
  • Move DNS zones from one server to another.
    • Server load management.
      • NORMALLY REQUIRES OUTAGE TIME FOR USERS
        • Complexity of Implementation high. High Business risk.
• DHCP SERVER CHANGES
  • Create New DHCP scopes.
    • Low risk as new scopes are not live, preparation work.
  • Alter existing DHCP scopes.
    • Sizing scope, increasing size, no impact on existing users.
      • Low risk and normally associated with an emergency request from the site/domain.
        • Complexity of change medium. Low Business risk.
    • Change attached template (Wins\Voice\DNS\) configuration.
      • Normally low risk as lease times are currently set at 14 days. This means very few clients will get change if it's incorrect and can be backed out very quickly.
        • Complexity of change low. Low Business risk.
    • Alter lease time attached to scope template.
      • LOW RISK
        • Complexity of implementation min. Low Business risk
  • Remove Scopes.
    • Normally occurs some time after server has stopped service.
      • LOW RISK
        • Complexity of implementation min. Low Business risk
  • DHCP failover install.
    • Low risk, has no direct effect on clients.
      • LOW RISK
        • Complexity of imlementation min. Low Business risk.
• DATABASE CHANGES
  • Update statistics.
    • Acceptable load on database.
      • Good option for Wednesday evening CC windows.
        • Complexity of implementation min. Low Business risk.
  • Re-indexing.
    • Heave load on database.
      • Database experiences hight CPU levels.
        • Complexity of implementation min Medium Business risk.
  • Audit data cleanup.
    • Heavy load on database.
      • Database must come off line.
        • Complexity of implementation high. High Business risk.
  • Database size changes.
    • Heavy load on database.
      • Database must come off line.
        • (untitled branch)
• MISC CHANGES
  • Disk space repairs etc.
    • High risk level.
      • Database downtime.
        • Complexity of impementation high. High Business risk.
  • Password changes to all servers.
    • qpman, qipaudit, password updates.
      • Should be spread out in much bigger time span than Window.
        • Complexity of implementation high. Medium Buiness risk.
  • Depot changes of replaced or fixed servers.
    • Responding to Girs generated tickets.

Comments