The NT1 or first BRITE CU that is connected to the U-card does not match the type of service assigned to the
customer at line card provisioning time. An example is if the customer subscribes to AMI U-DSL services, but
an
ANSI
NT1 is installed at the customer's premises. This is an NT1 mismatch.
The automatic mismatch test runs an electrical test on the U-card tip and ring, applying voltages and measuring
currents, to determine what might (or might not) be connected to the U-card loop. The goal is to prevent
mismatches, namely, to have
ANSI
Standard U-cards connected to
ANSI
Standard NT1s or CUs, and to have AMI
U-cards connected to AMI NT1s or CUs. On an hourly basis, the automatic mismatch test runs on all U-cards that
have D-channel port status indicating that ISDN layer 1 is not established at the 2-wire U-interface. Layer 1 may not
be established because of a mismatch condition. When the automatic mismatch test detects a mismatch, then the
D-channel port status supplementary information is updated to MSMTCH to indicate the mismatch condition, and a
summary report is printed to the ROP for all U-DSLs that are found with a mismatch condition.
There are several office parameters that provide control of the automatic mismatch test, and the automatic
mismatch test report. They are mismatch detection enable and report parameters found under RC/V view 8.1.
ENABLE:
This parameter allows or inhibits the automatic mismatch test from running in the entire office.
REPORT:
This parameter allows or inhibits the automatic mismatch test report from printing in the entire office.
There are additional controls for automatic mismatch and its report. These controls are on an SM/SM-2000 basis
and can be used to inhibit or allow the automatic mismatch mechanism. This is controlled through the input
messages
INH:MISMATCH
and
ALW:MISMATCH
. However, the SM/SM-2000 controls are subordinate to the
office parameters. This means that if the office parameter is set to no, then the SM/SM-2000 controls have no
affect.
3.6 FILE AND FILE SYSTEM MANAGEMENT
3.6.1 INTRODUCTION
Maintaining the file system includes the following:
Checking file system resources
Manipulating files
Using the file system audits
File system corruption detection [system integrity verification (SIV)]
Backing up and restoring file systems.
3.6.2 GENERAL
This subject lists and briefly describes the input messages and reports used in managing files and the file system.
These messages and responses are used in performing various actions such as reporting the contents of a file or
directory and copying a file from an active disk to an off-line or out-of-service disk.
The input/output messages are categorized according to the function performed on the file or file system and how
they are used (Type). The different functions and the corresponding tables are as follows:
File System Control
Table 3-1
235-105-210
October 1999
Copyright © 1999
Page 14
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...