Demand test descriptions and error codes - Avaya Support

SN-CONF (Switch Node Configuration)
c. Error Type 6000: no neighbor link is administered, but the SNI has one. If the Aux Data is 1,
an EI is connected as a neighbor link. If the Aux Data is 2, an SNI is connected as a
neighbor link.
To resolve Error Type 6000 with Aux Data 1, refer to FAIL code 133 for Configuration Audit
(#759). To resolve Error Type 6000 with Aux Data 2, refer to FAIL code 134 for the
Configuration Audit (#759).
d. Error Type 6001: no neighbor link exists between the SNI and its neighbor, but a neighbor
link (that is, fiber link) is administered.
To resolve this error, refer to FAIL code 135 for Configuration Audit (#759).
e. Error Type 6002: the physical neighbor type does not match administration. The associated
Aux Data value is the location reported by the neighbor SNI that did not match the fiber link
administration. If the aux data is 1, the type of neighbor administered is an SNI and the type
of neighbor connected is an EI. If the aux data is 2, the type neighbor administered is an EI
and the type of neighbor connected is an SNI.
To resolve Error Type 6002 with aux data 1, refer to FAIL code 136 for Configuration Audit
(#759). To resolve Error Type 6002 with aux data 2, refer to FAIL code 137 for
Configuration Audit (#759)
f. Error Type 6003: the neighbor location does not match administration. To resolve this error,
refer to FAIL code 138 for Configuration Audit (#759).
g. Error Type 6004: a peer link does not exist to another equipped SNI. The Aux Data equals
the slot number of the SNI to which this SNI or SNC does not have a peer link. To resolve
this error, refer to the FAIL code for Configuration Audit (#759) corresponding to the Aux
Data on the following table:
Aux Data
(slot no.)
2 102
3 103
4 104
5 105
6 106
7 107
8 108
9 109
13 113
Test 759
FAIL Code
1 of 2
Issue 5 May 2009 845