The MALC supports IMA test pattern procedures to validate the status of the IMA link. A test pattern sent over a transmit link is looped back over all available receive interfaces. Test pattern procedures do not interrupt traffic.
The following table describes the test pattern procedure parameters in the ima-group-profile.
Testing the IMA link with a random test pattern
A test pattern procedure with a random pattern will run continuously until it is disabled. Use the imatppshow command to view the status of the test (as explained in Viewing test procedure status on page 157).
To test the IMA link with a randomly generated test link and pattern (the default):
1 Specify an interface to transmit the test over:
zSH> update ima-group-profile 1/1/1 Please provide the following: [q]uit.
groupSymmetry: ---> {symmetricoperation}:
minNumTxLinks: ---> {1}:
minNumRxLinks: ---> {1}:
Parameter Description
testLinkIfIndex Indicates the interface used to transmit the test pattern. The test pattern is looped back from the far end device over each active link in the IMA group. Note that this value is not the same as the txImaId value.
Values:
A valid interface on the system in the form
shelf-slot-port-subport/type This is the link whose link identifier (LID) value is inserted in the Tx LID field of the transmitted ICP cells.
Default: 0
testPattern Specifies the transmit Test Pattern in an IMA group loopback operation. A value in the range 0 to 254 designates a specific pattern.
Values:
–1 to 254 –1 indicates that the test pattern is randomly generated.
Default: –1
testProcStatus Enables or disables the Test Pattern Procedure.
Values:
disabled Deactivates the test pattern procedure.
operating Activates the test pattern procedure.
Default: disabled
txClkMode: ---> {ctc}:
txImaId: ---> {1}:
txFrameLength: ---> {m128}:
diffDelayMax: ----> {75}:
alphaValue: ---> {2}:
betaValue: ---> {2}:
gammaValue: ---> {1}:
testLinkIfIndex: -> {0}: 1-1-1-0/ds1 IMA link to test testPattern: ---> {-1}:
testProcStatus: --> {disabled}: operating txTimingRefLink: -> {0}:
rxTimingRefLink: -> {0}:
groupRestoreNumRetry: -> {3}:
groupRestoreNumDelay: -> {3600}:
...
Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
2 To disable the test:
zSH> update ima-group-profile 1/1/1 Please provide the following: [q]uit.
groupSymmetry: ---> {symmetricoperation}:
minNumTxLinks: ---> {1}:
minNumRxLinks: ---> {1}:
txClkMode: ---> {ctc}:
txImaId: ---> {1}:
txFrameLength: ---> {m128}:
diffDelayMax: ----> {75}:
alphaValue: ---> {2}:
betaValue: ---> {2}:
gammaValue: ---> {1}:
testLinkIfIndex: -> {1/1/1/0/ds1}:
testPattern: ---> {-1}:
testProcStatus: --> {enabled}: disabled txTimingRefLink: -> {0}:
rxTimingRefLink: -> {0}:
groupRestoreNumRetry: -> {3}:
groupRestoreNumDelay: -> {3600}:
...
Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Testing the IMA link with a specific test pattern
A test with a specified test pattern runs until it verifies link connectivity. Use the imatppshow command to view the status of the test (as explained in Viewing test procedure status on page 157).
1 To specify a particular test pattern (for example, 23):
zSH> update ima-group-profile 1/1/1 Please provide the following: [q]uit.
groupSymmetry: ---> {symmetricoperation}:
minNumTxLinks: ---> {1}:
minNumRxLinks: ---> {1}:
txClkMode: ---> {ctc}:
txImaId: ---> {1}:
txFrameLength: ---> {m128}:
diffDelayMax: ----> {75}:
alphaValue: ---> {2}:
betaValue: ---> {2}:
gammaValue: ---> {1}:
testLinkIfIndex: -> {0}: 1-1-1-0/ds1 IMA link to test testPattern: ---> {-1}: 23
testProcStatus: --> {disabled}: operating txTimingRefLink: -> {0}:
rxTimingRefLink: -> {0}:
groupRestoreNumRetry: -> {3}:
groupRestoreNumDelay: -> {3600}:
...
Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
To run the test again, update the ima-group-profile without making any changes.
2 To disable the test:
zSH> update ima-group-profile 1/1/1 Please provide the following: [q]uit.
groupSymmetry: ---> {symmetricoperation}:
minNumTxLinks: ---> {1}:
minNumRxLinks: ---> {1}:
txClkMode: ---> {ctc}:
txImaId: ---> {1}:
txFrameLength: ---> {m128}:
diffDelayMax: ----> {75}:
alphaValue: ---> {2}:
betaValue: ---> {2}:
gammaValue: ---> {1}:
testLinkIfIndex: -> {1/1/1/0/ds1}:
testPattern: ---> {-1}:
testProcStatus: --> {enabled}: disabled txTimingRefLink: -> {0}:
rxTimingRefLink: -> {0}:
groupRestoreNumRetry: -> {3}:
groupRestoreNumDelay: -> {3600}:
...
Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Viewing test procedure status
Use the imatppshow command to view the status of the test:
If the test is successful, imaGroupTestProcStatus displays OPERATING:
zSH> imatppshow 1
TestLink ...: 2 imaGroupTestPattern ...: 23
imaGroupTestProcStatus ...: OPERATING
If the test fails (if, for example, the remote link is down), imaGroupTestProcStatus displays LINKFAIL:
zSH> imatppshow 1
TestLink ...: 2 imaGroupTestPattern ...: 71
imaGroupTestProcStatus ...: LINKFAIL
After the test is disabled, the imaGroupTestProcStatus displays DISABLED:
zSH> imatppshow 1
TestLink ...: 2 imaGroupTestPattern ...: 23
imaGroupTestProcStatus ...: DISABLED
Loopbacks
The MALC support the following types of loopbacks:
• T1 loopbacks on page 159
• DS3 loopbacks on page 163
• SONET loopbacks on page 161
• ISDN loopbacks on page 165
• 802.3ah Ethernet OAM loopback on page 166
• SELT/DELT on MALC ADSL2+ Broadcom cards on page 169
T1 loopbacks
The loopback-config parameter in the ds1-profile controls T1 loopbacks.
The following table describes the loopback options.
Activating a T1 loopback
Note: Loopbacks disrupt traffic on the interface.
1 Specify the type of loopback:
zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit.
line-type: ---> {esf}:
line-code: ---> {b8zs}:
send-code: ---> {sendnocode}:
circuit-id: ---> {ds1}:
loopback-config: ---> {noloop}: lineloop
Parameter Description
loopback-config The loopback configuration of the DS1 interface.
Values:
noloop Not in the loopback state. A device that is not capable of performing a loopback on the interface always returns this as its value.
lineloop The received signal at this interface is looped through the device. Typically the received signal is looped back for retransmission after it has passed through the device's framing function.
payloadloop The received signal on this interface does not go through the device (minimum penetration) but is looped back out.
Default: noloop
signal-mode: ---> {robbedbit}:
fdl: ---> {fdlnone}:
dsx-line-length: ---> {dsx0}:
line-status_change-trap-enable: -> {enabled}:
channelization: ---> {enabledds0}:
ds1-mode: ---> {csu}:
csu-line-length: ---> {csu00}:
clock-source-eligible: ---> {noteligible}:
transmit-clock-source: ---> {throughtiming}
cell-scramble: ---> {false}
coset-polynomial: ---> {true}:
protocol-emulation: ---> {network}
signal-type: ---> {loopstart}
ds1-group-number: ---> {0}
line-power: ---> {disabled}
...
Save changes? [s]ave, [c]hange or [q]uit: s Record updated.
Note: Only one loopback can be active at a time. If there is a loopback running, a message similar to the following will appear when you attempt to run another loopback:
1/1: ds1rp: : l=3278: Please disable any active loopbacks on line 1:1:0:0
2 To stop the loopback:
zSH> update ds1-profile 1-1-1-0/ds1 Please provide the following: [q]uit.
line-type: ---> {esf}:
line-code: ---> {b8zs}:
send-code: ---> {sendlinecode}:
circuit-id: ---> {ds1}:
loopback-config: ---> {lineloop}: noloop signal-mode: ---> {robbedbit}:
fdl: ---> {fdlnone}:
dsx-line-length: ---> {dsx0}:
line-status_change-trap-enable: -> {enabled}:
channelization: ---> {enabledds0}:
ds1-mode: ---> {csu}:
csu-line-length: ---> {csu00}:
clock-source-eligible: ---> {noteligible}:
transmit-clock-source: ---> {throughtiming}
cell-scramble: ---> {false}
coset-polynomial: ---> {true}:
protocol-emulation: ---> {network}
signal-type: ---> {loopstart}
ds1-group-number: ---> {0}
line-power: ---> {disabled}
...
Save changes? [s]ave, [c]hange or [q]uit: s Record updated.