From: mgt@NIC.DDN.MIL (MGT)
Newsgroups: ddn.mgt-bulletin
Subject: MILNET PSN SCHEDULED SERVICE INTERRUPTIONS
Date: 6 Oct 92 23:14:13 GMT
Reply-To: mgt@nic.ddn.mil
Distribution: ddn
Organization: The Defense Data Network


************************************************************************ 
DDN MGT Bulletin #102             DISA DDN Defense Communications System   
6 October 1992                    Published by: DDN Network Info Center
                                  (NIC@NIC.DDN.MIL)  (800) 365-3642

                        DEFENSE  DATA  NETWORK
                         MANAGEMENT  BULLETIN

  The DDN MANAGEMENT BULLETIN is distributed online by the DDN Network
  Information Center under DISA contract as a means of communicating
  official policy, procedures and other information of concern to
  management personnel at DDN facilities. Back issues may be read
  through the TACNEWS server ("@n" command at the TAC) or may be
  obtained by FTP (or Kermit) from the NIC.DDN.MIL host [192.112.36.5]
  using login="anonymous" and password="guest". The pathname
  for bulletins is ddn-news/ddn-mgt-bulletin-nn.txt (where "nn" is the
  bulletin number).
************************************************************************
 
                MILNET PSN SCHEDULED SERVICE INTERRUPTIONS

This DDN Management Bulletin is provided as guidance on how to submit
requests for DDN MILNET PSN Scheduled Service Interruption requests
for approval.  In the past few months DISA/DODM has received numerous
requests for scheduled downtime at DDN MILNET PSN facilities without
proper coordination and end user validation.  Further, DISA/DODM has
received requests thru the CONUS MILNET Monitoring Center (CMMC) from
Node Site Coordinators.  The CMMC is not authorized to approve Scheduled
Service Interruption requests without prior approval from DONC/DODM.
Also requests for Scheduled Service Interruptions should not be submitted
to the CMMC, unless as INFORMATION ONLY.

Procedures and guidelines for DDN MILNET PSN Scheduled Service
Interruptions are in DISA (DCA) Circular 310-70-1*, DCS Systems Control,
Volume II, Operational Procedures TCF/PTF/MTC's, Change 1, 22 December
1989, Chapter 8. Data Switched Networks, paragraph 2.r, pages 8-16 thru
8-19.  This DISA Circular applies to military departments (MilDeps), and
other activities of DOD or governmental agencies responsible for 
operation, maintenance and management of the DCS (Defense Communications
System), which includes DDN MILNET PSNs and its Interswitch Trunks (ISTs).

Request all future requests for DDN MILNET PSNs Scheduled Service
Interruptions be submitted as directed by DISA Circular referenced above.
If your DDN MILNET PSN site does not have a copy of this DISA Circular,
please check with your local Techincal Control Facility (TCF), Patch and
Test Facility (PTF) or Nodal and Access Switch Monitoring and Test Centers
(MTCs), they are required to have copy of this DISA Circular, which you
could use for your scheduled service interruption request.  This DISA 
Circular can also be ordered thru your local Publication Distribution 
Office (PDO) or Base administration office.  All Node Site Coordinators
should either have this DISA Circular on hand or be made available from
your local Technical Control Facility.

The following excert from 310-70-1, DISA(DCA) Circular 310-70-1, Volume II,
Chapter 8, Data Switched Networks, paragraph 2.r, pages 8-16 thru 8-19 is
quoted for your guidance:

QUOTE.
r.  SCHEDULED SERVICE INTERRUPTIONS. Chapter 4 of this
Circular estabilishes the policy and procedures for scheduling
DCS service interupptions.  For DDN, all PSN interruptions are
scheduled according to chapter 4, paragraph 2c, "Interruption of
user service (other than complete DCS station)".  All other
facilities supporting the DDN backbone are scheduled as directed
in chapter 4, paragraph 2h, "Interruption of user service (DCS
tail station)".  Paragraphs referenced in chapter 4 only task 
the TCF/PTF of the station being interrupted to take action.
For DDN, this tasking is expanded to any DCS supporting agency
requesting a DDN facility be taken out of service.  The
following exceptions to chapter 4 apply to DDN:

    (1)  Interruption of service of one (1) hour or less.
Requests for service interruption will be verbally passed to the
appropriate area DOCC element when the projected service
interruption is expected to be one (1) hour or less and impairs
the operational capability of any DDN backbone element.

         (a)  This coordination shall be accomplished no
later than 24 hours prior to the start of the outage.

         (b)  All approved service interruption requests
will be documented in the master station log in each affected
DOCC element.
 
         (c)  The appropriate MC (Monitoring Center) will notify
affected node site coordinator (NSC) no later than 18 hours prior to an
approved outage.  Any downtime adjustments will be made during
this coordination and final downtime will be set.

         (d)  Thirty minutes prior to the actual outage, the
person(s) taking the element(s) out of service will telephone
the appropriate DOCC element for final approval.  This is
necessary to confirm current network posture and avoid any
operational conflicts caused by real-time operating problems.

     (2)  MC directed cancellations.  Any service
interruption request which may cause or contribute to a problem
which will seriously impact the operational capability of the
respective DDN backbone, will be cancelled by the respective
area DOCC element.  The appropriate MC(s) will immediately
notify the service interruption requestor of any cancellations.
The affected NSC will be notified of cancellations, as time
permits.

    (3)  Inter-area outages.  Service interruptions
impacting inter-area connectivity will be requested of an
approved by the responsible area DOCC element.  The responsible
DOCC element will coordinate all inter-area outages with the
distant-end area DOCC element prior to granting final approval.

    (4)  Interruption of service to tail PSN(s).  PSN's
which are connected to the DDN backbone through a single IST,
are considered tail PSN's (commonly referred to as "stub" or
 "string" PSN's).  Tail PSN's will follow procedures outlined in
chapter 4, paragraph 2c although chapter 4, para 2h, refers to
minimum requirements for tail stations.

    (5)  Relocation of PSN(s).  To accomodate changes at
the local site level, relocation of a PSN is occasionally
required.  Due to the lead-time needed to move the PSN equipment
and supporting telecommunications, a one year notification is
required in addition to the notification identified in chapter
4.

         (a)  One year advance notice of a proposed PSN
equipment relocation is required to properly plan, schedule,
survey, and accomplish the relocation.  Notice will be made by
the PSN sponsoring command or agency via AUTODIN message to DCA
Washington DC//DDO// with an information copy to the appropriate
DCA area and O&M command.  This message will contain, as a 
minimum, the following information:

                  1.  Node name and number.

                  2.  Node site coordinator (NSC):  Name, DSN
and commercial phone numbers, AUTODIN plain language address
(PLA) and E-mail address.

                  3.  Current node location:  Building, room,
address.

                  4.  Proposed node location:  Building, room,
address.

                  5.  Date relocation must be completed.

                  6.  Reason relocation required:  Include
impact if not accomplished by date specified.

                  7.  TSR actions:  Explain, in detail, all
circuit actions.

                  8.  Proposed  schedule:  Begin with proposed
site survey date and show complete sequence of required
actions.  Include resource requirements (i.e. local
communications unit, engineering and installation units, DDN
contractor, etc.) proposed for accomplishing the relocation.

                  9.  Office of primary responsibility:  Name,
DSN and commercial phone numbers, AUTODIN and E-mail address.

              (b)  Exceptions to the 1 year advance notice will
be made on a case by case basis.  For example, a shorter lead
time may be possible if all actions can be accomplished by the
sponsoring command or agency and only record TSR(s) are
needed.  Minimum lead time will be 21 days required for a
service interruption request.  The service interruption request
will be modified to include the information above.

              (c)  Headquarters, DCA, code DDO in concert with
the appropriate DCA area, will review and approve all relocation
request.  When approved, the responsible DCA DDN Installation
Management Branch will issue scheduled service interruption
request notifications, following the procedures identified
chapter 4, paragraph 2c.

              (d)  At no time, is the site authorized to move
equipment without prior DCA approval.  Normally, a site survey
will be performed and relocations accomplished with DCA,
sponsoring O&M service agency, local command, and support
contractor participation.  Additionally, the requesting
organization may be required to provide funding to support the
cost of the site survey.
UNQUOTE.

If your organization is unable to comply with Chapter 8, above, due
to EMERGENCY notification of a scheduled service interruption, then
please contact DISA/DODM DSN 222-7582, commercial 703-692-7582,
immediately for verbal approval of the scheduled service interruption.
However, pleaee remember this only be done on a case by case basis and
IS NOT to be used for ROUTINE scheduled service interruptions.  Don't
forget, that DDN direct connect users to the PSN's also must concur
with the scheduled serivce interruption time frame.  Also for EMERGENCY
type scheduled service interruptions (CONUS Only) they can be 
submitted via E-mail to the following addresses:

Action:       milnetmgr@ddn-conus.ddn.mil
              cmcmgr@ddn-conus.ddn.mil
              aopsmgr@ddn-conus.ddn.mil

Information:  dca-mmc@cmsc.ddn.mil

For Pacific and European sites, please forward these requests for
scheduled serivce interruptions to the appropriate DOCC area element.

DISA/DODM point of contact is Mr McDaniel, CONUS Monitoring Center,
Manager, DSN 222-7582, commercial (703) 692-7582, email address:
cmcmgr@ddn-conus.ddn.mil.
Newsgroups: ne.housing