Table Of Contents
Provisioning Cards
6.1 How Do I Provision Cards?
6.2 Common Cards
6.3 DWDM Cards
6.3.1 Provisioning Pluggable Entities on DWDM Cards
6.4 Electrical Cards
6.4.1 Converting DS1-14 Cards from 1:1 to 1:N Protection
6.4.2 Converting DS3-12 Cards from 1:1 to 1:N Protection
6.4.3 Converting E1-N-14 Cards from 1:1 to 1:N Protection
6.4.4 Converting DS3i-N-12 Cards from 1:1 to 1:N Protection
6.4.5 Resetting NE Thresholds to the Default Values
6.5 Ethernet Cards
6.5.1 Provisioning E-Series Ethernet Ports for VLAN Membership
6.5.2 Specifying the ML-Series Card Username and Password
6.5.3 Modifying Configuration Settings for the ML-Series Cards—ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15454 SONET, and ONS 15454 SDH
6.5.4 Creating RMON Thresholds
6.5.5 E-Series Spanning Tree Protocol (IEEE 802.1D)
6.6 FC_MR-4 Card
6.7 FMEC Cards
6.8 Optical Multirate Cards
6.9 Optical Cards
6.9.1 Provisioning an OC-N Card for ONS 15454 SONET
6.9.2 Resetting NE Thresholds to the Default Values
6.10 Transponder Cards
6.11 MGX Voice Gateway Cards
6.11.1 RPM Management Limitation
6.11.2 How Do I Provision AXSM Cards?
6.11.3 How Do I Provision VXSM Cards?
6.11.4 Configuring Stream Control Transmission Protocol for H.248 Traffic
6.11.5 Configuring H248.11
6.11.6 Configuring Voice Quality Trigger Metric and Threshold Parameters
6.11.7 How Do I Provision RPM Cards?
6.11.8 How Do I Provision VISM-PR Cards?
Provisioning Cards
This chapter provides instructions on how to provision a subset of CTM-supported cards. For more information on card provisioning, see the NE-related documentation.
This chapter contains the following sections:
•
How Do I Provision Cards?
•Common Cards
•DWDM Cards
•Electrical Cards
•Ethernet Cards
•FC_MR-4 Card
•FMEC Cards
•Optical Multirate Cards
•Optical Cards
•Transponder Cards
•MGX Voice Gateway Cards
6.1 How Do I Provision Cards?
Where supported, use the NE Explorer to view and provision card settings.
Step 1 Select an NE in the Domain Explorer and choose Configuration > NE Explorer.
Step 2 In the tree view of the NE Explorer window, select the card that you want to provision.
Step 3 In the slot properties pane, click the tab or subtab that corresponds to the settings that you want to modify. For detailed information on the different tabs and subtabs available for each card, see:
•Appendix C, "Slot Property Information—Common, DWDM, Electrical, and Ethernet Cards"
•Appendix D, "Slot Property Information—FC_MR-4, FMEC, Multirate, Optical, and Transponder Cards"
Step 4 Modify the settings. For drop-down lists, select an item from the list. For numerics, double-click the field and type the new number.
Step 5 Click Apply.
6.2 Common Cards
The following table lists the common cards supported in CTM and the NEs that contain the common card.
Table 6-1 Common Cards
Card Type
|
NE
|
For Slot Property Information, See
|
AIC
|
ONS 15327 and ONS 15454 SONET
|
C.1.1 Slot Properties—AIC, page C-2
|
AIC-I
|
ONS 15454 SONET and ONS 15454 SDH
|
C.1.2 Slot Properties—AIC-I, page C-6
|
AIU
|
ONS 15808
|
C.1.3 Slot Properties—AIU, page C-10
|
CMP
|
ONS 15808
|
C.1.4 Slot Properties—CMP, page C-12
|
CMP-W
|
ONS 15800 and ONS 15801
|
C.1.5 Slot Properties—CMP-W, page C-13
|
CTX-2500
|
ONS 15310 MA SONET and ONS 15310 MA SDH
|
C.1.6 Slot Properties—CTX-2500, page C-15
|
CTX-CL600
|
ONS 15310 CL
|
C.1.7 Slot Properties—CTX-CL600, page C-31
|
CXC
|
ONS 15600 SONET and ONS 15600 SDH
Note In NE releases earlier than release 5.0, the SSXC card is called the CXC card.
|
C.1.24 Slot Properties—SSXC, page C-98
|
EOI-W
|
ONS 15800 and ONS 15801
|
C.1.8 Slot Properties—EOI-W, page C-64
|
Filler
|
ONS 15600 SONET and ONS 15600 SDH
|
C.1.9 Slot Properties—FILLER, page C-65
|
IOC-W
|
ONS 15800 and ONS 15801
|
C.1.10 Slot Properties—IOC-W, page C-65
|
LSM-W
|
ONS 15800 and ONS 15801
|
C.1.11 Slot Properties—LSM-W, page C-67
|
MIC
|
ONS 15327
|
C.1.12 Slot Properties—MIC-28-3-A and MIC-28-3-B, page C-70
|
MMU
|
ONS 15454 SONET and ONS 15454 SDH
|
C.1.13 Slot Properties—MMU (ONS 15454 SONET and ONS 15454 SDH), page C-71
|
OCP
|
ONS 15808
|
C.1.14 Slot Properties—OCP, page C-75
|
OSCM
|
ONS 15454 SONET and ONS 15454 SDH
|
C.1.15 Slot Properties—OSCM (ONS 15454 SONET and ONS 15454 SDH), page C-78
|
OSCM
|
ONS 15808
|
C.1.16 Slot Properties—OSCM (ONS 15808), page C-83
|
OSU-W
|
ONS 15800 and ONS 15801
|
C.1.17 Slot Properties—OSU-W, page C-86
|
PLF
|
ONS 15808
|
C.1.18 Slot Properties—PLF, page C-89
|
RBU
|
ONS 15800 and ONS 15801
|
C.1.19 Slot Properties—RBU, page C-90
|
SCF
|
ONS 15800 and ONS 15801
|
C.1.20 Slot Properties—SCF, page C-91
|
SCU
|
ONS 15808
|
C.1.21 Slot Properties—SCU, page C-93
|
SNH
|
ONS 15808
|
C.1.22 Slot Properties—SNH, page C-95
|
SNS
|
ONS 15808
|
C.1.23 Slot Properties—SNS, page C-96
|
SSXC
|
ONS 15600 SONET and ONS 15600 SDH
Note In NE releases earlier than release 5.0, the SSXC card is called the CXC card.
|
C.1.24 Slot Properties—SSXC, page C-98
|
TCC+
|
ONS 15327 and ONS 15454 SONET
|
C.1.25 Slot Properties—TCC+, page C-99
|
TCC-I
|
ONS 15454 SDH
|
C.1.26 Slot Properties—TCC-I, page C-100
|
TCC2
|
ONS 15454 SONET and ONS 15454 SDH
|
C.1.27 Slot Properties—TCC2, page C-101
|
TCC2P
|
ONS 15454 SONET and ONS 15454 SDH
|
C.1.28 Slot Properties—TCC2P, page C-102
|
TSC
|
ONS 15600 SONET and ONS 15600 SDH
|
C.1.29 Slot Properties—TSC, page C-104
|
UDC
|
ONS 15808
|
C.1.30 Slot Properties—UDC, page C-105
|
XC
|
ONS 15327 and ONS 15454 SONET
|
C.1.37 Slot Properties—XC, page C-109
|
XC-VXL-10G
|
ONS 15454 SONET and ONS 15454 SDH
|
C.1.38 Slot Properties—XC-VXL-10G, page C-111
|
XC10G
|
ONS 15454 SONET and ONS 15454 SDH
|
C.1.39 Slot Properties—XC10G, page C-112
|
XCVT
|
ONS 15327 and ONS 15454 SONET
|
C.1.40 Slot Properties—XCVT, page C-114
|
XCVXC
|
ONS 15454 SONET and ONS 15454 SDH
|
C.1.41 Slot Properties—XCVXC, page C-115
|
XTC
|
ONS 15305 CTC
|
C.1.42 Slot Properties—XTC (ONS 15305), page C-117
|
XTC
|
ONS 15327
|
C.1.43 Slot Properties—XTC (ONS 15327), page C-117
|
6.3 DWDM Cards
The following table lists the DWDM cards supported in CTM and the NEs that contain the DWDM card.
Table 6-2 DWDM Cards
Card Type
|
NE
|
For Slot Property Information, See
|
2.5G_DM
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.1 Slot Properties—2.5G_DM, page C-128
|
2.5G DMP
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.2 Slot Properties—2.5G_DMP, page C-141
|
2.5G Multirate Transponder
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.3 Slot Properties—2.5G Multirate Transponder, page C-154
|
32DMX—32-Channel Demultiplexer
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.4 Slot Properties—32DMX, page C-175
|
32DMX-L—32-Channel Demultiplexer L-Band
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.5 Slot Properties—32DMX-L, page C-182
|
32 DMX-O—32-Channel Demultiplexer 100 GHz-Odd
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.6 Slot Properties—32DMX_O, page C-189
|
40-DMX-C—40-Channel Demultiplexer C-Band
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.7 Slot Properties—40-DMX-C, page C-194
|
32 MUX-O—32-Channel Multiplexer 100 GHz-Odd
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.8 Slot Properties—32MUX_O, page C-200
|
40-MUX-C—40-Channel Multiplexer C-Band
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.9 Slot Properties—40-MUX-C, page C-205
|
32WD-IR—32-Channel Wavelength Demultiplexer-Infrared Band
|
ONS 15800 and ONS 15801
|
C.2.10 Slot Properties—32WD-IR, page C-212
|
32-WSS—32-Channel Wavelength Selective Switch
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.11 Slot Properties—32WSS, page C-214
|
32WSS-L—32-Channel Wavelength Selective Switch L-Band
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.12 Slot Properties—32WSS-L, page C-221
|
40-WSS-C—40-Channel Wavelength Selective Switch C-Band
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.13 Slot Properties—40-WSS-C, page C-228
|
40-WXC-C—40-Channel Wavelength Cross-Connect C-Band
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.14 Slot Properties—40-WXC-C, page C-236
|
4MD-xx.x—4-Channel Multiplexer/Demultiplexer
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.15 Slot Properties—4MD_xx.x, page C-244
|
AD-1B-xx.x—1-Band OADM
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.16 Slot Properties—AD_1B_xx.x, page C-249
|
AD-1C-xx.x—1-Channel OADM
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.17 Slot Properties—AD_1C_xx.x, page C-253
|
AD-2C-xx.x—2-Channel OADM
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.18 Slot Properties—AD_2C_xx.x, page C-258
|
AD-4B-xx.x—4-Band OADM
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.19 Slot Properties—AD_4B_xx.x, page C-263
|
AD-4C-xx.x—4-Channel OADM
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.20 Slot Properties—AD_4C_xx.x, page C-267
|
ADA—Add/Drop Amplifier
|
ONS 15800 and ONS 15801
|
C.2.21 Slot Properties—ADA, page C-272
|
ADM_10G
|
ONS 15454 SONET (MSTP) and ONS 15454 SDH
|
C.2.22 Slot Properties—ADM-10G, page C-276
|
BBA—Blue-Band Booster Amplifier
|
ONS 15800 and ONS 15801
|
C.2.23 Slot Properties—BBA, page C-297
|
BBA/RBA—Blue-Band Booster Amplifier/Red-band Booster Amplifier
|
ONS 15800 and ONS 15801
|
C.2.24 Slot Properties—BBA/RBA, page C-300
|
BCS-ELH—Band Combiner and Splitter Extended Long Haul
|
ONS 15808
|
C.2.25 Slot Properties—BCS-ELH, page C-304
|
BCS-LH—Band Combiner and Splitter Long Haul
|
ONS 15808
|
C.2.26 Slot Properties—BCS-LH, page C-307
|
40MD-CO-D—40-channel Demultiplexer unit-C band-Odd channels
40MD-CE-D—40-channel Demultiplexer unit-C band-Even channels
20MD-LO-D—20-channel Demultiplexer unit-L band-Odd channels
20MD-LE-D—20-channel Demultiplexer unit-L band-Even channels
8MD-C—8-channel Mux/Demux unit-C band-OADM Application
|
ONS 15808
|
C.2.27 Slot Properties—Demultiplexer, page C-309
|
IRBA—Infrared-Band Booster Amplifier
|
ONS 15800 and ONS 15801
|
C.2.28 Slot Properties—IRBA, page C-312
|
GE_XP, 10GE_XP
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.29 Slot Properties—GE_XP and 10GE_XP, page C-316
|
Multiplexer
|
ONS 15808
|
C.2.30 Slot Properties—Multiplexer, page C-339
|
MXP_2.5G_10E
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.31 Slot Properties—MXP_2.5G_10E, page C-341
|
MXP_2.5G_10G Muxponder
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.32 Slot Properties—MXP_2.5G_10G, page C-359
|
MXP_MR_10DME Muxponder
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.33 Slot Properties—MXP_MR_10DME, page C-372
|
OA-ELH—Optical Amplifier-Extended Long Haul
|
ONS 15808
|
C.2.34 Slot Properties—OA-ELH, page C-393
|
OAD-8-C—Optical Add/Drop Unit-Passive 4-Channel-C Band
|
ONS 15808
|
C.2.35 Slot Properties—OAD-8-C, page C-399
|
OADM-P4—Optical Add/Drop Multiplexer-Passive-4 Channel
|
ONS 15800 and ONS 15801
|
C.2.36 Slot Properties—OADM-P4, page C-401
|
OBA-C—Optical Booster Amplifier
|
ONS 15808
|
C.2.37 Slot Properties—OBA-C, page C-403
|
OECP—Odd/Even Channel Processor-Passive
|
ONS 15808
|
C.2.38 Slot Properties—OECP, page C-407
|
OEP-C—Optical Extra Pump Amplifier
|
ONS 15808
|
C.2.39 Slot Properties—OEP-C, page C-409
|
OP-ELH—Optical External Pump-Extended Long Haul
|
ONS 15808
|
C.2.40 Slot Properties—OP-ELH, page C-412
|
OPA—Optical Preamplifier
|
ONS 15808
|
C.2.41 Slot Properties—OPA-C, page C-416
|
OPT-AMP-17-C, OPT-AMP-C
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.42 Slot Properties—OPT-AMP-17-C and OPT-AMP-C, page C-420
|
OPT-AMP-L
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.43 Slot Properties—OPT-AMP-L, page C-429
|
OPT-BST—Optical Booster Amplifier Module
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.45 Slot Properties—OPT-BST, page C-443
|
OPT-BST-E—Enhanced Optical Booster Amplifier
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.46 Slot Properties—OPT-BST-E, page C-449
|
OPT-BST-L
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.47 Slot Properties—OPT-BST-L, page C-454
|
OPT-PRE—Optical Preamplifier Module
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.48 Slot Properties—OPT-PRE, page C-460
|
OPT-RAMP-C
|
ONS 15454 MSTP
|
C.2.44 Slot Properties—OPT-RAMP-C, page C-435
|
ORP-ELH—Optical Raman Pump-Extended Long Haul
|
ONS 15808
|
C.2.49 Slot Properties—ORP-ELH, page C-465
|
OSC-CSM—Optical Service Channel Combiner and Separator Module
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.50 Slot Properties—OSC-CSM, page C-468
|
PRE-L—Pre-Line Amplifier
|
ONS 15800 and ONS 15801
|
C.2.52 Slot Properties—PRE-L, page C-491
|
PRE-L-IR—Pre-Line Amplifier-Infrared band
|
ONS 15800 and ONS 15801
|
C.2.53 Slot Properties—PRE-L-IR, page C-494
|
TPA—Transmit Power Amplifier
|
ONS 15800 and ONS 15801
|
C.2.55 Slot Properties—TPA, page C-504
|
TXP_MR_10E
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.56 Slot Properties—TXP_MR_10E, page C-507
|
TXP_MR_10G
|
ONS 15454 SONET and ONS 15454 SDH
|
C.2.57 Slot Properties—TXP_MR_10G, page C-530
|
8WD-B—8-channel Wavelength Demultiplexer-Blue band module
24WD-R—24-channel Wavelength Demultiplexer-Red band module
24WD-LLR—24-channel Wavelength Demultiplexer-Low Loss-Red band module
|
ONS 15800 and ONS 15801
|
C.2.58 Slot Properties—WD, page C-542
|
6.3.1 Provisioning Pluggable Entities on DWDM Cards
Step 1 Select a CTC-based NE in the Domain Explorer tree and choose Configuration > NE Explorer.
Step 2 In the tree view of the NE Explorer window, select the DWDM card that you want to provision and click the PPM tab.
Step 3 Click Create. Depending on the selection context, one of the following dialog boxes opens; fields vary accordingly:
•Create PPM
•Create Port
Step 4 In the PPM No. field, select the PPM number from the drop-down list.
Step 5 In the PPM Type field, select the type of PPM from the drop-down list. (This field is not visible in the Create Port dialog box.)
Step 6 In the Port Rate field, select the port rate from the drop-down list. (This field is not visible in the Create PPM dialog box.)
Step 7 Click OK.
6.4 Electrical Cards
The following table lists the electrical cards supported in CTM and the NEs that contain the electrical card. It also provides links to the provisioning tasks that you can perform for some of the cards.
Table 6-3 Electrical Cards
Card Type
|
NE
|
Electrical Card Task
|
For Slot Property Information, See
|
DS-N
|
ONS 15327 and ONS 15454 SONET
|
—
|
C.3.10 Slot Properties—DS-N, page C-628
|
DS1-14
|
ONS 15327 and ONS 15454 SONET
|
Converting DS1-14 Cards from 1:1 to 1:N Protection
|
C.3.1 Slot Properties—DS-1-14, page C-544
|
DS1-28/DS3- EC1-3
|
ONS 15310 MA SONET
|
—
|
C.3.2 Slot Properties—DS1-28/DS3-EC1-3, page C-552
|
DS1-84/DS3- EC1-3
|
ONS 15310 MA SONET
|
—
|
C.3.3 Slot Properties—DS1-84/DS3-EC1-3, page C-576
|
DS1N-14
|
ONS 15327 and ONS 15454 SONET
|
—
|
C.3.4 Slot Properties—DS-1N, page C-600
|
DS1_E1_56
|
ONS 15454 SONET
|
—
|
C.3.11 Slot Properties—DS1_E1_56, page C-629
|
DS3-12
|
ONS 15327 and ONS 15454 SONET
|
Converting DS3-12 Cards from 1:1 to 1:N Protection
|
C.3.5 Slot Properties—DS-3-12, page C-604
|
DS3_EC1_48
|
ONS 15454 SONET
|
—
|
C.3.12 Slot Properties—DS3_EC1_48, page C-638
|
DS3E
|
ONS 15327 and ONS 15454 SONET
|
—
|
C.3.6 Slot Properties—DS-3E, page C-607
|
DS3i
|
ONS 15454 SDH
|
—
|
C.3.7 Slot Properties—DS-3i, page C-611
|
DS3i-N-12
|
ONS 15454 SONET
|
Converting DS3i-N-12 Cards from 1:1 to 1:N Protection
|
C.3.8 Slot Properties—DS-3i-N-12, page C-617
|
DS3XM-6
|
ONS 15454 SONET
|
—
|
C.3.9 Slot Properties—DS-3XM-6, page C-621
|
DS3XM-12
|
ONS 15454 SONET
|
—
|
C.3.13 Slot Properties—DS3XM-12, page C-653
|
E-1
|
ONS 15454 SDH
|
—
|
C.3.14 Slot Properties—E-1, page C-666
|
E1-42
|
ONS 15454 SDH
|
—
|
C.3.16 Slot Properties—E1-42, page C-693
|
E1-63
|
ONS 15305 CTC
|
—
|
C.3.17 Slot Properties—E1-63 (ONS 15305 CTC), page C-700
|
E1-8
|
ONS 15305 CTC
|
—
|
C.3.18 Slot Properties—E1-8 (ONS 15305 CTC), page C-702
|
E1-N-14
|
ONS 15454 SDH
|
Converting E1-N-14 Cards from 1:1 to 1:N Protection
|
C.3.19 Slot Properties—E1-N-14, page C-704
|
E1_21_E3_DS3_3 and E1_63_E3_DS3_3
|
ONS 15310 MA SDH
|
—
|
C.3.15 Slot Properties—E1_21_E3_DS3_3 and E1_63_E3_DS3_3, page C-670
|
E3
|
ONS 15454 SDH
|
—
|
C.3.20 Slot Properties—E3-12, page C-711
|
E3T3-6
|
ONS 15305 CTC
|
—
|
C.3.21 Slot Properties—E3T3_6 (ONS 15305 CTC), page C-716
|
EC1-12
|
ONS 15327 and ONS 15454 SONET
|
—
|
C.3.22 Slot Properties—EC1-12, page C-718
|
FMEC-E3/DS3
|
ONS 15454 SDH
|
—
|
C.3.23 Slot Properties—FMEC-E3/DS-3, page C-723
|
STM-1E-12
|
ONS 15454 SDH
|
—
|
D.4.16 Slot Properties—STM-1E-12, page D-173
|
6.4.1 Converting DS1-14 Cards from 1:1 to 1:N Protection
Note This procedure assumes that DS1-14 cards are installed in slots 1 through 6 and/or slots 12 through 17. The DS1-14 cards in slots 3 and 15, which are the protection slots, will be replaced with DS1N-14 cards. The ONS 15454 must run CTC Release 2.0 or later. The procedure also requires at least one DS1N-14 card and a protection group with DS1-14 cards.
Step 1 Select the NE in the Domain Explorer; then, choose Configuration > NE Explorer.
Step 2 In NE node property sheet, click the Protection tab.
Step 3 In the Protection Groups subtab, select the protection group containing slot 3 or slot 15 (where the DS1N-14 card will be installed).
Step 4 Be sure that the slot that is being upgraded is not carrying working traffic. In the Operations tab, look at the Protection Groups Details. The protect slot must be Protect/Standby and not Protect/Active. If the protect slot status is Protect/Active, complete the following steps to switch traffic to the working card:
a. In the Protection Group Details list, click the protect card.
b. In the Switch Commands area, click Switch.
The working slot should change to Working/Active and the protect slot should change to Protect/Standby. If they do not change, do not continue. Troubleshoot the working card and slot to determine why the card cannot carry working traffic.
c. In the Switch Commands area, click Clear.
Step 5 Repeat Step 1 to Step 4 for each protection group that you want to convert.
Step 6 Verify that no standing alarms exist for any of the DS1-14 cards that will be converted. If alarms exist that cannot be cleared, contact the next level of support.
Step 7 Click the Protection Groups subtab.
Step 8 Click the 1:1 protection group that contains the cards that will be moved into the new protection group.
Step 9 Click Delete.
Step 10 When the confirmation dialog box opens, click OK.
Note Deleting the 1:1 protection groups will not disrupt service. However, no protection bandwidth exists for the working circuits until the 1:N protection procedure is completed. Therefore, complete this procedure as quickly as possible.
Step 11 If needed, repeat Step 6 to Step 10 for any other protection groups.
Step 12 Physically remove the DS1-14 card from slot 3 or slot 15. This generates an improper removal alarm.
Step 13 In the node view, right-click the slot that held the removed card and choose Delete card from the drop-down list. Wait for the card to disappear from the node view.
Step 14 Physically insert a DS1N-14 card into the same slot.
Step 15 Verify that the card boots up properly.
Step 16 Choose Configuration > CTC-Based SONET NEs > Equipment Inventory Table and verify that the new card appears as a DS1N-14 card.
Step 17 Click the node view in the NE Explorer tree.
Step 18 Click the Protection tab; then, click the Protection Groups subtab.
Step 19 Click Create. The Create Protection Group dialog box opens.
Step 20 (Optional) In the Name field, enter a name for the protection group.
Step 21 In the Type field, choose 1:N (card) from the drop-down list.
Step 22 In the Protect Module field, choose the protection slot from the drop-down list.
The Create Protection Group dialog box shows the protect card in the Protect Card field and the available cards in the Available Cards field.
Step 23 Verify that the DS1N-14 card appears in the Protect Card field.
Step 24 In the Available Cards list, highlight the card that will be included in the protection group. Click the arrow (>>) to move the card to the Working Cards list.
Step 25 In the Reversion Time field, choose the reversion time from the drop-down list.
Step 26 Click OK.
Step 27 When the confirmation dialog box opens, click Yes.
The protection group should appear in the Protection Groups list on the Protection subtab.
6.4.2 Converting DS3-12 Cards from 1:1 to 1:N Protection
Note This procedure assumes that DS3-12 cards are installed in slots 1 through 6 and/or slots 12 through 17. The DS3-12 cards in slots 3 and 15, which are the protection slots, will be replaced with DS3N-12 cards. The ONS 15454 must run CTC Release 2.0 or later. This procedure also requires at least one DS3N-12 card and a protection group with DS3-12 cards.
Step 1 Select the NE in the Domain Explorer; then, choose Configuration > NE Explorer.
Step 2 In the NE node property sheet, click the Protection tab.
Step 3 In the Protection Groups subtab, select the protection group containing slot 3 or slot 15 (where the DS3N-12 card will be installed).
Step 4 Be sure that the slot that is being upgraded is not carrying working traffic. In the Operations tab, look at the Protection Groups Details. The protect slot must be Protect/Standby and not Protect/Active. If the protect slot status is Protect/Active, complete the following steps to switch traffic to the working card:
a. In the Protection Group Details list, click the protect card.
b. In the Switch Commands area, click Switch.
The working slot should change to Working/Active and the protect slot should change to Protect/Standby. If they fail to change, do not continue. Troubleshoot the working card and slot to determine why the card cannot carry working traffic.
c. In the Switch Commands area, click Clear.
Step 5 Repeat Step 1 to Step 4 for each protection group that you want to convert.
Step 6 Verify that no standing alarms exist for any of the DS3-12 cards that are being converted. If alarms exist that cannot be cleared, contact the next level of support.
Step 7 Click the Protection Groups subtab.
Step 8 Click the 1:1 protection group that contains the cards that will be moved into the new protection group.
Step 9 Click Delete.
Step 10 When the confirmation dialog box opens, click OK.
Note Deleting the 1:1 protection groups will not disrupt service. However, no protection bandwidth exists for the working circuits until the 1:N protection procedure is completed. Therefore, complete this procedure as quickly as possible.
Step 11 If needed, repeat Step 6 to Step 10 for each protection group.
Step 12 Physically remove the DS3-12 card from slot 3 or slot 15. This generates an improper removal alarm.
Step 13 In the node view, right-click the slot that held the removed card and choose Delete card from the drop-down list. Wait for the card to disappear from the node view.
Step 14 Physically insert a DS3N-12 card into the same slot.
Step 15 Verify that the card boots up properly.
Step 16 Choose Configuration > CTC-Based SONET NEs > Equipment Inventory Table and verify that the new card appears as a DS3N-12 card.
Step 17 Click the node view in the NE Explorer tree.
Step 18 Click the Protection tab; then, click the Protection Groups subtab.
Step 19 Click Create. The Create Protection Group dialog box opens.
Step 20 (Optional) In the Name field, enter a name for the protection group.
Step 21 In the Type field, choose 1:N (card) from the drop-down list.
Step 22 In the Protect Module field, choose the protection slot from the drop-down list.
The Create Protection Group dialog box shows the protect card in the Protect Card field and the available cards in the Available Cards field.
Step 23 Verify that the DS3N-12 card appears in the Protect Card field.
Step 24 In the Available Cards list, highlight the card that will be included in the protection group. Click the arrow (>>) to move the card to the Working Cards list.
Step 25 In the Reversion Time field, choose a reversion time from the drop-down list.
Step 26 Click OK.
Step 27 When the confirmation dialog box opens, click Yes.
The protection group should appear in the Protection Groups list on the Protection subtab.
6.4.3 Converting E1-N-14 Cards from 1:1 to 1:N Protection
Note•This procedure assumes that E1-N-14 cards are installed in slots 1 through 6 and/or slots 12 through 17. The E1-N-14 cards in slots 3 and 15, which are the protection slots, will be converted from 1:1 to 1:N protection. (E1-N-14 cards can work in 1:1 and 1:N protection schemes.)
•Be sure that the slot containing the E1-N-14 card is not carrying working traffic. Also, be sure that there are no existing alarms for the E1-N-14 card that you are converting.
Complete the following steps to convert E1-N-14 cards from 1:1 to 1:N protection:
Step 1 Select the NE in the Domain Explorer; then, choose Configuration > NE Explorer.
Step 2 In NE node property sheet, click the Protection tab.
Step 3 In the Protection Groups subtab, select the protection group containing slot 3 or slot 15 (where the E1-N-14 card will be installed).
Step 4 Be sure that the slot that is being upgraded is not carrying working traffic. In the Operations tab, look at the Protection Groups Details. The protect slot must be Protect/Standby and not Protect/Active. If the protect slot status is Protect/Active, complete the following steps to switch traffic to the working card:
a. In the Protection Group Details list, click the protect card.
b. In the Switch Commands area, click Switch.
The working slot should change to Working/Active and the protect slot should change to Protect/Standby. If they fail to change, do not continue. Troubleshoot the working card and slot to determine why the card cannot carry working traffic.
c. In the Switch Commands area, click Clear.
Step 5 Repeat Step 1 to Step 4 for each protection group that you want to convert.
Step 6 Verify that no standing alarms exist for any of the E1-N-14 cards that are being converted. If alarms exist that cannot be cleared, contact the next level of support.
Step 7 Click the Protection Groups subtab.
Step 8 Click the 1:1 protection group that contains the cards that will be moved into the new protection group.
Step 9 Click Delete.
Step 10 When the confirmation dialog box opens, click OK.
Note Deleting the 1:1 protection groups will not disrupt service. However, no protection bandwidth exists for the working circuits until the 1:N protection procedure is completed. Therefore, complete this procedure as quickly as possible.
Step 11 If needed, repeat Step 6 to Step 10 for each protection group.
Step 12 Click Create. The Create Protection Group dialog box opens.
Step 13 (Optional) In the Name field, enter a name for the protection group.
Step 14 In the Type field, choose 1:N (card) from the drop-down list.
Step 15 Verify that the E1-N-14 card appears in the Protect Card field.
Step 16 In the Available Cards list, highlight the card that will be included in the protection group. Click the arrow (>>) to move the card to the Working Cards list.
Step 17 Click OK.
Step 18 When the confirmation dialog box opens, click Yes.
The protection group should appear in the Protection Groups list on the Protection subtab.
6.4.4 Converting DS3i-N-12 Cards from 1:1 to 1:N Protection
Note This procedure assumes that DS3i-N-12 cards are installed in slots 1 to 6 and/or slots 12 to 17.
Step 1 Select the NE in the Domain Explorer; then, choose Configuration > NE Explorer.
Step 2 In NE node property sheet, click the Protection tab.
Step 3 In the Protection Groups subtab, select the protection group containing slot 3 or slot 15 (where the DS3i-N-12 card will be installed).
Step 4 Be sure that the slot that is being upgraded is not carrying working traffic. In the Operations tab, look at the Protection Groups Details. The protect slot must be Protect/Standby and not Protect/Active. If the protect slot status is Protect/Active, complete the following steps to switch traffic to the working card:
a. In the Protection Group Details list, click the protect card.
b. In the Switch Commands area, click Switch.
The working slot should change to Working/Active and the protect slot should change to Protect/Standby. If they fail to change, do not continue. Troubleshoot the working card and slot to determine why the card cannot carry working traffic.
c. In the Switch Commands area, click Clear.
Step 5 Repeat Step 1 to Step 4 for each protection group that you want to convert.
Step 6 Verify that no standing alarms exist for any of the DS3i-N-12 cards that are being converted. If alarms exist that cannot be cleared, contact the next level of support.
Step 7 Click the Protection Groups subtab.
Step 8 Click the 1:1 protection group that contains the cards that will be moved into the new protection group.
Step 9 Click Delete.
Step 10 When the confirmation dialog box opens, click OK.
Note Deleting the 1:1 protection groups will not disrupt service. However, no protection bandwidth exists for the working circuits until the 1:N protection procedure is completed. Therefore, complete this procedure as quickly as possible.
Step 11 If needed, repeat Step 6 to Step 10 for each protection group.
Step 12 Verify that the card boots up properly.
Step 13 Click the node view in the NE Explorer tree.
Step 14 Click the Protection tab; then, click the Protection Groups subtab.
Step 15 Click Create. The Create Protection Group dialog box opens.
Step 16 (Optional) In the Name field, enter a name for the protection group.
Step 17 In the Type field, choose 1:N (card) from the drop-down list.
Step 18 Verify that the DS3i-N-12 card appears in the Protect Card field.
Step 19 In the Available Cards list, highlight the card that will be included in the protection group. Click the arrow (>>) to move the card to the Working Cards list.
Step 20 Click OK.
Step 21 When the confirmation dialog box opens, click Yes.
The protection group should appear in the Protection Groups list on the Protection subtab.
Note When a manual OC-N protection switch is performed incorrectly, a warning message indicates that CTM cannot perform the operation.
6.4.5 Resetting NE Thresholds to the Default Values
You can reset NE thresholds on electrical and optical cards.
Step 1 Select the NE in the Domain Explorer; then, choose Configuration > NE Explorer.
Step 2 Open the card slot property sheet for the electrical or optical card.
Step 3 Click the Line or STS tab.
Step 4 Click the threshold subtab that contains the values that you want to revert to the default.
Step 5 In the threshold subtab, click the Reset to Default button.
Step 6 At the confirmation prompt, click Yes.
6.5 Ethernet Cards
The following table describes the Ethernet cards supported in CTM and the NEs that contain the Ethernet card. It also provides links to the provisioning tasks that you can perform for some of the cards.
Table 6-4 Ethernet Cards
Card Type
|
NE
|
Ethernet Card Tasks
|
For Slot Property Information, See
|
CE-100T-8
|
ONS 15310 CL, ONS 15310 MA SONET, and ONS 15310 MA SDH
|
Creating RMON Thresholds
|
C.4.1 Slot Properties—CE-100T-8 (ONS 15310 CL, ONS 15310 MA SONET, and ONS 15310 MA SDH), page C-725
|
CE-100T-8
|
ONS 15454 SONET
|
Creating RMON Thresholds
|
C.4.2 Slot Properties—CE-100T-8 (ONS 15454 SONET), page C-731
|
CE-100T-8
|
ONS 15454 SDH
|
C.4.3 Slot Properties—CE-100T-8 (ONS 15454 SDH), page C-738
|
CE-1000-4
|
ONS 15454 SONET and ONS 15454 SDH
|
Creating RMON Thresholds
|
C.4.4 Slot Properties—CE-1000-4 (ONS 15454 SDH and ONS 15454 SONET), page C-745
|
CE-MR-6
|
ONS 15310 MA SONET and ONS 15310 MA SDH
|
Creating RMON Thresholds
|
C.4.5 Slot Properties—CE-MR-6, page C-752
|
CE-MR-10
|
ONS 15454 SONET and ONS 15454 SDH
|
Creating RMON Thresholds
|
C.4.6 Slot Properties—CE-MR-10, page C-761
|
E10/100T-4
|
ONS 15327
|
Provisioning E-Series Ethernet Ports for VLAN Membership
E-Series Spanning Tree Protocol (IEEE 802.1D)
|
C.4.7 Slot Properties—E10/100T-4, page C-769
|
E1000-2
|
ONS 15454 SONET and ONS 15454 SDH
|
C.4.8 Slot Properties—E1000-2, page C-773
|
E1000-2-G
|
ONS 15454 SONET and ONS 15454 SDH
|
C.4.9 Slot Properties—E1000-2-G, page C-776
|
E100T-12
|
ONS 15454 SONET and ONS 15454 SDH
|
C.4.10 Slot Properties—E100T-12, page C-779
|
E100T-G
|
ONS 15454 SONET and ONS 15454 SDH
|
C.4.11 Slot Properties—E100T-G, page C-783
|
E100-8
|
ONS 15305 CTC
|
Provisioning E-Series Ethernet Ports for VLAN Membership
|
C.4.12 Slot Properties—E100-8 (ONS 15305 CTC), page C-785
|
E100-WAN-8
|
ONS 15305 CTC
|
Provisioning E-Series Ethernet Ports for VLAN Membership
|
C.4.13 Slot Properties—E100-WAN-8 (ONS 15305 CTC), page C-788
|
ETH1000
|
ONS 15327, ONS 15454 SONET, and ONS 15454 SDH
|
Provisioning E-Series Ethernet Ports for VLAN Membership
E-Series Spanning Tree Protocol (IEEE 802.1D)
|
C.4.14 Slot Properties—ETH1000, page C-791
|
G1000-2
|
ONS 15327
|
—
|
C.4.15 Slot Properties—G1000-2, page C-793
|
G1000-4
|
ONS 15327, ONS 15454 SONET, and ONS 15454 SDH
|
—
|
C.4.16 Slot Properties—G1000-4, page C-796
|
GE-2
|
ONS 15305 CTC
|
Provisioning E-Series Ethernet Ports for VLAN Membership
|
C.4.17 Slot Properties—GE-2 (ONS 15305 CTC), page C-802
|
GigE-WAN-2
|
ONS 15305 CTC
|
Provisioning E-Series Ethernet Ports for VLAN Membership
|
C.4.18 Slot Properties—GigE-WAN-2 (ONS 15305 CTC), page C-804
|
ML-100T-8
|
ONS 15310 CL, ONS 15310 MA SONET, and ONS 15310 MA SDH
|
Specifying the ML-Series Card Username and Password
Modifying Configuration Settings for the ML-Series Cards—ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15454 SONET, and ONS 15454 SDH
|
C.4.19 Slot Properties—ML-100T-8, page C-807
|
ML1000-2
|
ONS 15454 SONET and ONS 15454 SDH
|
Specifying the ML-Series Card Username and Password
Modifying Configuration Settings for the ML-Series Cards—ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15454 SONET, and ONS 15454 SDH
Creating RMON Thresholds
|
C.4.20 Slot Properties—ML1000-2, page C-813
|
ML100T-12
|
ONS 15454 SONET and ONS 15454 SDH
|
C.4.21 Slot Properties—ML100T-12, page C-823
|
ML100X-8
|
ONS 15454 SONET and ONS 15454 SDH
|
Specifying the ML-Series Card Username and Password
|
C.4.22 Slot Properties—ML100X-8, page C-833
|
ML-MR-10
|
ONS 15454 SONET and ONS 15454 SDH
|
Specifying the ML-Series Card Username and Password
|
C.4.23 Slot Properties—ML-MR-10, page C-842
|
MS-ISC-100T
|
ONS 15454 SONET and ONS 15454 SDH
|
—
|
C.4.24 Slot Properties—MS-ISC-100T, page C-850
|
RAN-SVC
|
ONS 15454 SONET and ONS 15454 SDH
|
—
|
C.4.25 Slot Properties—RAN-SVC, page C-852
|
6.5.1 Provisioning E-Series Ethernet Ports for VLAN Membership
Caution The ONS 15305 CTC, ONS 15454 SONET, and ONS 15454 SDH propagate VLANs whenever a node appears on the same network view as another node, regardless of whether or not the nodes connect through data communication channels (DCCs). For example, if two ONS 15454 SONETs or ONS 15454 SDHs without DCC connectivity belong to the same Login Node Group, whenever CTC is launched from within this login node group, VLANs propagate from one to the other. This happens even though the ONS 15454 SONETs or ONS 15454 SDHs do not belong to the same ring.
Caution If a node is unreachable or out of service, and if the DCC connections used to reach the NE still exist, CTM does not allow the deletion of a VLAN on the NE. You must delete the DCC connections before deleting a VLAN.
The ONS 15305 CTC, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH allow configuration of the VLAN membership and Q-tag handling of individual Ethernet ports.
Step 1 Select an ONS 15305 CTC, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE in the Domain Explorer tree and choose Configuration > NE Explorer.
Step 2 In the tree view of the NE Explorer window, select the card that you want to provision and click the VLAN tab.
Step 3 To put a port in a VLAN, click the port and choose Tagged or Untag.
If a port is a member of only one VLAN, go to the row of that VLAN and choose Untag from the Port column. Choose -- for all the other VLAN rows in that Port column. The VLAN with Untag selected can connect to the port, but other VLANs cannot access that port.
If a port is a trunk port, it connects multiple VLANs to an external device, such as a switch, that also supports trunking. A trunk port must have tagging (802.1Q) enabled for all the VLANs that connect to that external device. Choose Tagged at all VLAN rows that need to be trunked. Choose Untag at one or more VLAN rows in the trunk port column that do not need to be trunked; for example, the default VLAN. Each Ethernet port must be attached to at least one untagged VLAN. The following table describes the port settings.
Table 6-5 Port Settings
Setting
|
Description
|
--
|
A port marked with this symbol does not belong to the VLAN.
|
Untag
|
The node will tag ingress frames and strip tags from egress frames.
|
Tagged
|
The node will handle ingress frames according to VLAN ID; egress frames will not have their tags removed.
|
Step 4 After each port is in the appropriate VLAN, click Apply.
Note If Tagged is chosen, the attached external devices must recognize IEEE 802.1Q VLANs.
Note Both ports on an individual E1000-2 or E1000-2-G card cannot be members of the same VLAN.
6.5.2 Specifying the ML-Series Card Username and Password
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 Click Security Properties; then, click one of the following:
•CTC-Based SDH tab > ONS 15454 SDH, ONS 15600 SDH, ONS 15305 CTC, or ONS 15310 MA SDH subtab
•CTC-Based SONET tab > ONS 15454, ONS 15600, ONS 15327, ONS 15310 CL, or ONS 15310 MA subtab
Step 3 In the CTM Server - ML Series Card Connection area, enter the username and password. Retype the password as confirmation.
Note The CTM barebone Cisco IOS configuration file uses CTM123+ as the predefined password. By default, the same password is set in the Control Panel at installation.
Step 4 Click Save.
6.5.3 Modifying Configuration Settings for the ML-Series Cards—ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15454 SONET, and ONS 15454 SDH
Full Cisco IOS configuration synchronization is performed automatically by CTM to keep the NE and the CTM Data Provisioning Service synchronized. Full configuration resynchronization might be delayed depending on the usage of the CTM server. For the CTM server deployed as the monitoring server, the recommended value for the delay parameter is 120 seconds. For the CTM server deployed as the provisioning server, the recommended value for the delay parameter is 10 minutes (for example, 600 seconds). The default value is provided in the Control Panel > NE Service > CTC-Based SONET NEs or CTC-Based SDH NEs > NE Service pane > L2 Service Resync Delay field. For example, for the CTC-based SONET or CTC-based SDH network service, the default L2 Service Resync Delay value is 600 seconds.
To upload or download a configuration file for the ML-series card:
Step 1 Select an ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15454 SONET, or ONS 15454 SDH NE in the Domain Explorer and choose Configuration > NE Explorer.
Step 2 In the tree view of the NE Explorer window, select the ML card.
Step 3 Click the Configuration tab. The following parameters are displayed:
•Source—Source of the configuration file.
•Host—Host machine where the configuration file is stored or the location where the file will be downloaded.
•Filename—Name of the configuration file.
•Directory—Directory on the host machine for the configuration file.
•Time Stamp—Date and time of the file upload or download.
Note These parameters are initially grayed out or disabled. When a file download or upload is completed, the fields display the parameters of the download or upload. These parameters are related to the newly loaded barebone configuration file. Once a change is made to the barebone configuration file, the fields are cleared.
Step 4 To download the file from the Timing Communications and Control (TCC) card to the host machine:
a. In the Configuration subtab, click TCC>>File. The Download from TCC dialog box opens.
b. Select the location of the file to download. Click either the Local or the Server radio button.
Step 5 To upload the file from the host machine to the TCC card:
a. In the Configuration subtab, click File>> TCC. The Upload to TCC dialog box opens.
b. Select the location of the file to upload. Click either the Local or Server radio button.
Note If you select Local, the file is first copied to the CTM server and then uploaded to the TCC card. The host refers to the server; the directory refers to the directory on the server where the file resides.
Step 6 Be sure to reset the ML-series cards after uploading a Cisco IOS startup config file to a TCC card.
Step 7 To launch the command-line interface (CLI), click Launch CLI.
6.5.4 Creating RMON Thresholds
Step 1 Select an NE in the Domain Explorer and choose Configuration > NE Explorer.
Step 2 In the tree view of the NE Explorer window, select the card.
Step 3 Depending on the card selected, click the Thresholds tab or Line tab > RMON Thresholds or RPR Span subtab.
Step 4 Click Create. The Create RMON Thresholds dialog box opens. The following table provides descriptions. Fields shown depend on the type of NE that is selected.
Step 5 Click OK.
Table 6-6 Field Descriptions for the Create RMON Thresholds Dialog Box
Field
|
Description
|
Slot
|
Choose the appropriate card.
|
Port
|
Choose the applicable port on the card you selected.
|
Variable
|
Choose the MIB variable to monitor.
|
Alarm Type
|
Indicate whether the event will be triggered by the rising threshold, falling threshold, or both the rising and falling thresholds.
|
Sample Type
|
Depending on the type of data module used by the NE, choose Relative, Absolute, or Delta.
•Relative restricts the threshold to use the number of occurrences in the user-set sample period.
•Absolute sets the threshold to use the total number of occurrences, regardless of time period.
•Delta tests the delta between samples.
|
Sample Period
|
Specify the sample period, in seconds.
|
Rising Thresholds
|
Enter the appropriate number of occurrences for the rising threshold.
Note For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a falling threshold of 400 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
|
Falling Thresholds
|
Enter the appropriate number of occurrences for the falling threshold. In most cases, the falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 minutes subsides and creates only 799 collisions in 15 minutes, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over 1000 per 15 minute period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
|
6.5.5 E-Series Spanning Tree Protocol (IEEE 802.1D)
The ONS 15327, ONS 15454 SONET, and ONS 15454 SDH operate Spanning Tree Protocol (STP) according to IEEE 802.1D when an Ethernet card is installed. STP operates over all packet-switched ports, including Ethernet and ONS 15327, ONS 15454 SONET, or ONS 15454 SDH ports. On Ethernet ports, STP is disabled by default and can be enabled by checking the check box under the Port subtab of the Provisioning tab at the card-level view. On ONS 15327, ONS 15454 SONET, or ONS 15454 SDH interface ports, STP is active by default and cannot be disabled.
The Ethernet card can enable STP on the Ethernet ports to allow redundant paths to the attached Ethernet equipment. STP spans cards so that both equipment and facilities are protected against failure.
STP detects and eliminates network loops. When STP detects multiple paths between any two network hosts, STP blocks ports until only one path exists between any two network hosts. The single path eliminates possible bridge loops. This is crucial for shared packet rings, which naturally include a loop.
To remove loops, STP defines a tree that spans all of the switches in an extended network. STP forces certain redundant data paths into a standby (blocked) state. If one network segment in the STP becomes unreachable, the spanning-tree algorithm reconfigures the spanning-tree topology and reactivates the blocked path to reestablish the link. STP operation is transparent to end stations, which do not discriminate between connections to a single LAN segment and a switched LAN with multiple segments. The ONS 15327, ONS 15454 SONET, and ONS 15454 SDH support one STP instance per circuit and a maximum of eight STP instances per ONS 15327, ONS 15454 SONET, or ONS 15454 SDH.
Note When an Ethernet card is provisioned, the STP state might need to be updated. Click the Update button in the NE Explorer to update the STP state.
The ONS 15327, ONS 15454 SONET, or ONS 15454 SDH can operate multiple instances of STP to support VLANs in a looped topology. Separate circuits can be dedicated across the SONET ring for different VLAN groups (that is, one for private TLS services and one for Internet access). Each circuit runs its own STP to maintain VLAN connectivity in a multiring environment.
6.5.5.1 Viewing E-Series Spanning-Tree Configurations
Step 1 Select an ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE in the Domain Explorer tree and choose Configuration > NE Explorer.
Step 2 Click the EtherBridge tab.
Step 3 Click the Spanning Tree Config subtab. The spanning-tree configuration parameters are listed in the following table.
Table 6-7 Spanning-Tree Configuration Parameters
Parameter
|
Cisco Default Value
|
Value Range
|
Priority
|
32768
|
0-65535
|
Bridge Max Age
|
20 seconds
|
6-40 seconds
|
Bridge Hello Time
|
2 seconds
|
1-10 seconds
|
Bridge Forward Delay
|
15 seconds
|
4-30 seconds
|
6.5.5.2 Viewing E-Series Spanning-Tree Parameters
Step 1 Select an ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE in the Domain Explorer tree and choose Configuration > NE Explorer.
Step 2 Click the EtherBridge tab.
Step 3 Click the Spanning Tree Status subtab. The spanning-tree parameters are listed in the following table.
Table 6-8 Spanning-Tree Parameters
Parameter
|
Description
|
BridgeID
|
Unique identifier that transmits the configuration bridge protocol data unit (BPDU); the bridge ID is a combination of the bridge priority and the NE MAC address.
|
Topo Age
|
Amount of time in seconds since the last topology change.
|
Topo Changes
|
Number of times the spanning-tree topology has been changed since the node booted up.
|
Designated Root
|
The designated root of the spanning tree for a particular spanning-tree instance.
|
Root Cost
|
The total path cost to the designated root.
|
Root Port
|
Port used to reach the root.
|
Max Age
|
Maximum time that received-protocol information is retained before it is discarded.
|
Hello Time
|
Time interval, in seconds, between the transmission of configuration BPDUs by a bridge that is the spanning-tree root or is attempting to become the spanning-tree root.
|
Hold Time
|
Minimum time period, in seconds, that elapses during the transmission of configuration information about a given port.
|
Forward Delay
|
Time spent by a port in the listening state and the learning state.
|
6.6 FC_MR-4 Card
The following table lists the NEs that contain the FC_MR-4 card.
6.7 FMEC Cards
The following table lists the FMEC cards supported in CTM and the NEs that contain the FMEC card.
6.8 Optical Multirate Cards
The following table lists the optical multirate cards supported in CTM and the NEs that contain the optical multirate card.
6.9 Optical Cards
The following table lists the optical cards supported in CTM and the NEs that contain the optical card. It also provides links to the provisioning tasks that you can perform for some of the cards.
Table 6-12 Optical Cards
Card Type
|
NE
|
Optical Card Task
|
For Slot Property Information, See
|
OC12 IR/STM4 SH 1310
|
ONS 15327 and ONS 15454 SONET
|
Provisioning an OC-N Card for ONS 15454 SONET
|
D.4.1 Slot Properties—OC12 IR/STM4 SH 1310, page D-85
|
OC12 IR/STM4 SH 1310-4
|
ONS 15327 and ONS 15454 SONET
|
Provisioning an OC-N Card for ONS 15454 SONET
|
D.4.2 Slot Properties—OC12-4 IR/STM4 SH 1310, page D-91
|
OC192
|
ONS 15454 SONET, ONS 15454 SDH, and ONS 15600 SONET
|
—
|
D.4.3 Slot Properties—OC192 LR/STM64 LH 1550, page D-98
|
OC-192/STM64 XFR-based
|
ONS 15454 SONET and ONS 15454 SDH
|
—
|
D.4.4 Slot Properties—OC192/STM64 XFR-Based, page D-105
|
OC3 IR 4 1310
|
ONS 15327 and ONS 15454 SONET
|
Provisioning an OC-N Card for ONS 15454 SONET
|
D.4.5 Slot Properties—OC3 IR 4 1310, page D-121
|
OC3 IR/STM1 SH 1310-8
|
ONS 15454 SONET and ONS 15454 SDH
|
—
|
D.4.6 Slot Properties—OC3 IR/STM1 SH 1310-8, page D-127
|
OC48
|
ONS 15600
|
—
|
D.4.7 Slot Properties—OC48, page D-135
|
OC48 IR 1310
|
ONS 15327 and ONS 15454 SONET
|
Provisioning an OC-N Card for ONS 15454 SONET
|
D.4.8 Slot Properties—OC48 IR 1310, page D-141
|
OC48 LR 1310
|
ONS 15327 and ONS 15454 SONET
|
Provisioning an OC-N Card for ONS 15454 SONET
|
D.4.9 Slot Properties—OC48 LR 1550, page D-148
|
OECP-L
|
ONS 15808
|
—
|
D.4.10 Slot Properties—OECP-L, page D-157
|
S1.1-2-LC
|
ONS 15305 CTC
|
—
|
D.4.11 Slot Properties—S1.1-2-LC (ONS 15305 CTC), page D-160
|
S1.1-8-LC
|
ONS 15305 CTC
|
—
|
D.4.12 Slot Properties—S1.1-8-LC (ONS 15305 CTC), page D-162
|
S16.1-1-LC
|
ONS 15305 CTC
|
—
|
D.4.13 Slot Properties—S16.1-1-LC (ONS 15305 CTC), page D-164
|
STM-1
|
ONS 15454 SDH
|
—
|
D.4.14 Slot Properties—STM-1, page D-166
|
STM-1 S1.1-2-LC/E1-21
|
ONS 15305 CTC
|
—
|
D.4.15 Slot Properties—STM-1 S1.1-2-LC/E1-21 (ONS 15305 CTC), page D-171
|
STM1E-12
|
ONS 15454 SDH
|
—
|
D.4.16 Slot Properties—STM-1E-12, page D-173
|
STM-16
|
ONS 15454 SDH
|
—
|
D.4.17 Slot Properties—STM-16 (ONS 15454 SDH), page D-178
|
STM-16
|
ONS 15600 SDH
|
—
|
D.4.18 Slot Properties—STM-16 (ONS 15600 SDH), page D-184
|
STM-4
|
ONS 15454 SDH
|
—
|
D.4.19 Slot Properties—STM-4 IR/STM4 SH 1310, page D-191
|
STM-4 L4.2-2-LC
|
ONS 15305 CTC
|
—
|
D.4.20 Slot Properties—STM-4 L4.2-2-LC (ONS 15305 CTC), page D-196
|
STM-16 L16.2-1-LC
|
ONS 15305 CTC
|
—
|
D.4.21 Slot Properties—STM-16 L16.2-1-LC (ONS 15305 CTC), page D-198
|
STM-64
|
ONS 15454 SDH
|
—
|
D.4.22 Slot Properties—STM-64 LH 1550 (ONS 15454 SDH), page D-200
|
STM-64
|
ONS 15600 SDH
|
—
|
D.4.23 Slot Properties—STM-64 LR/LH 4 (ONS 15600 SDH), page D-205
|
STM-64_4_DWDM
|
ONS 15600 SDH
|
—
|
D.4.24 Slot Properties—STM-64_4_DWDM (ONS 15600 SDH), page D-212
|
OC192_4_DWDM
|
ONS 15600 SONET
|
—
|
D.4.25 Slot Properties—OC192_4_DWDM (ONS 15600 SONET), page D-222
|
6.9.1 Provisioning an OC-N Card for ONS 15454 SONET
ONS 15454 SONET OC-3, OC-12, and OC-48 cards can be provisioned to support either SONET or SONET over SDH signals.
Step 1 Select an ONS 15454 SONET NE in the Domain Explorer tree and choose Configuration > NE Explorer.
Step 2 In the tree view of the NE Explorer window, select the OC-N card.
Step 3 Click the Line tab; then, click the Line Config subtab.
Step 4 In the EnableSyncMsg column, uncheck the check box.
Step 5 Be sure that the Admin state of the port is selected as OOS (only then can the SONET port be configured as SDH).
Step 6 In the Type column, choose SDH.
Step 7 Click Apply.
6.9.2 Resetting NE Thresholds to the Default Values
See Resetting NE Thresholds to the Default Values.
6.10 Transponder Cards
The following table lists the transponder cards supported in CTM and the NEs that contain the transponder card.
Table 6-13 Transponder Cards
Card Type
|
NE
|
For Slot Property Information, See
|
BT10E-LCxx/BT10E-LLxx—Bidirectional Line Transponder
|
ONS 15808
|
D.5.1 Slot Properties—BT10E-LCxx and BT10E-LLxx, page D-233
|
FEC-LEM—Forward Error Correction Line Extender Module
|
ONS 15800 and ONS 15801
|
D.5.2 Slot Properties—FEC-LEM, page D-238
|
LEM—Line Extender Module
|
ONS 15800 and ONS 15801
|
D.5.3 Slot Properties—LEM, page D-242
|
LEM-10-B1—Line Extender Module-10 Gb/s B1
|
ONS 15800 and ONS 15801
|
D.5.4 Slot Properties—LEM-10-B1, page D-245
|
LEM-10G-Nxx—Line Extender Module-10 Gb/s-Normal
|
ONS 15800 and ONS 15801
|
D.5.5 Slot Properties—LEM-10G-Nxx, page D-249
|
LEM-EM-M—Line Extender Module-Externally Modulated-B1 Monitoring
|
ONS 15800 and ONS 15801
|
D.5.6 Slot Properties—LEM-EM-M, page D-252
|
LT—Line Transponder
|
ONS 15808
|
D.5.7 Slot Properties—LT, page D-255
|
RT—Receiver Transponder
|
ONS 15808
|
D.5.8 Slot Properties—RT, page D-260
|
RXT—Receive Transponder
|
ONS 15800 and ONS 15801
|
D.5.9 Slot Properties—RXT, page D-264
|
RXT-10G-N—Receive Transponder-10 Gb/s-Normal
|
ONS 15800 and ONS 15801
|
D.5.10 Slot Properties—RXT-10G-N, page D-266
|
RXT_10H-M—Receive Transponder-10 Gb/s High Sensitivity-B1 Monitoring
|
ONS 15800 and ONS 15801
|
D.5.11 Slot Properties—RXT-10H-M, page D-269
|
RXT-B1 Monitoring—Receive Transponder-B1 Monitoring
|
ONS 15800 and ONS 15801
|
D.5.12 Slot Properties—RXT-B1, page D-272
|
RXT-FEC—Receive Transponder-Forward Error Correction
|
ONS 15800 and ONS 15801
|
D.5.13 Slot Properties—RXT-FEC, page D-276
|
TT-25G-Cxx—Transmit Transponder-2.5 Gb/s-C band-FEC Coding
TT-10G-Cxx—Transmit Transponder-10 Gb/s-C band-FEC Coding
TT-10G-SCxx—Transmit Transponder-10 Gb/s-C band-Single Slot-FEC Coding
TT-10G-SLxx—Transmit Transponder-10 Gb/s-L band-Single Slot-FEC Coding
|
ONS 15808
|
D.5.14 Slot Properties—Transmitter Transponder, page D-279
|
WCM—Wavelength Converter Module
|
ONS 15800 and ONS 15801
|
D.5.15 Slot Properties—WCM, page D-284
|
WCM-10G-Nxx—Wavelength Converter Module-10 Gb/s-Normal
|
ONS 15800 and ONS 15801
|
D.5.16 Slot Properties—WCM-10G-Nxx, page D-287
|
WCM-FEC—Wavelength Converted Module-Forward Error Correction
|
ONS 15800 and ONS 15801
|
D.5.17 Slot Properties—WCM-FEC, page D-290
|
WCM-EM-Fxx—Wavelength Converted Module-Externally Modulated-Forward Error Correction
|
ONS 15800 and ONS 15801
|
D.5.18 Slot Properties—WCM-EM-Fxx, page D-294
|
WCM-EM-Mxx—Wavelength Converted Module-Externally Modulated-B1 Monitoring
|
ONS 15800 and ONS 15801
|
D.5.19 Slot Properties—WCM-EM-Mxx, page D-299
|
WCM10—Wavelength Converted Module-10 Gb/s
|
ONS 15800 and ONS 15801
|
D.5.20 Slot Properties—WCM10, page D-303
|
6.11 MGX Voice Gateway Cards
The following table lists the MGX Voice Gateway modules and cards that CTM manages.
Table 6-14 MGX Voice Gateway Modules and Cards
Module
|
Front Card
|
Back Card
|
PXM45
|
PXM45/B
|
PXM-UI-S3
|
PXM-HD
|
PXM45/C
|
PXM-UI-S3/B
|
PXM-HD
|
PXM1E
|
PXM1E-4-155
|
MGX-MMF-4-155/C
|
MGX-SMFIR-4-155/C
|
MGX-SMFLR-4-155/C
|
PXM1E-8-T3E3
|
SMB-8-T3
|
SMB-8-E3
|
PXM1E-8-155
|
SFP-8-155
|
MCC-8-155
|
PXM1E-16-T1E1
|
MCC-16-E1
|
RBBN-16-T1E1
|
PXM1E-COMBO
|
MGX-T3E3-155
|
RPM-PR
|
MGX-RPM-PR-256
MGX-RPM-PR-512
|
MGX-RJ45-4E/B
|
MGX-RJ45-FE
|
MGX-MMF-FE
|
MGX-RPM-1FE-CP
|
5E/FE/GE_RJ45
|
RPM-XF
|
MGX-RPM-XF-512
|
MGX-1OC12POS-IR
|
MGX-1GE
|
MGX-2GE
|
MGX-2OC12POS
|
AXSM-XG
|
AXSM-16-155-XG
|
SFP-8-155
|
SMFIR-1-155-SFP
|
SMFLR-1-155-SFP
|
MMF-1-155-SFP
|
MCC-8-155
|
AXSM-8-622-XG
|
SFP-4-622
|
AXSM/B
|
AXSM-16-T3E3/B
|
SMB-8-T3
|
SMB-8-E3
|
AXSM-16-155/B
|
MMF-8-155-MT/B
|
SMFIR-8-155-LC/B
|
SMFLR-8-155-LC/B
|
SMB-4-155
|
AXSM-4-622/B
|
SMFIR-2-622/B
|
SMFLR-2-622/B
|
AXSM-1-2488/B
|
SMFSR-1-2488/B
|
SMFLR-1-2488/B
|
AXSME
|
AXSM-32-T1E1-E
|
MCC-16-E1
|
RBBN-16-T1E1
|
VXSM
|
MGX-VXSM-155
|
VXSM-BC-4-155
|
MGX-VXSM-T1E1
|
VXSM-BC-24T1E1
|
MGX-VXSM-6-T3
|
VXSM-BC-3T3
|
VXSM redundant back card
|
—
|
VXSM-R-BC
|
RCON-1TO5-8850
|
—
|
—
|
VISM-PR
|
MGX-VISM-PR-8T1
|
AX-RJ48-8T1
|
AX-R-RJ48-8T1
|
MGX-VISM-PR-8E1
|
AX-RJ48-8E1
|
AX-R-RJ48-8E1
|
AX-SMB-8E1
|
AX-R-SMB-8E1
|
SRME/B
|
MGX-SRME/B
|
MGX-SMFIR-1-155
|
MGX-STM1-EL-1
|
MGX-BNC-3T3-M
|
SRME
|
MGX-SRME
|
MGX-SMFIR-1-155
|
MGX-STM1-EL-1
|
MPSM
|
MPSM-8-T1E1
|
AX-RJ48-8T1
|
AX-RJ48-8E1
|
MPSM-16-8T1E1
|
RBBN-16-T1E1-1N
|
MCC-16-E1-1N
|
MPSM-T3E3-155
|
BNC-3T3E3
|
SFP-2-155
|
MPSM redundant back card
|
—
|
RED-16-T1E1
|
This section also describes how to provision cards on MGX Voice Gateway devices. It contains the following information:
•RPM Management Limitation
•How Do I Provision AXSM Cards?
•How Do I Provision VXSM Cards?
•Configuring Stream Control Transmission Protocol for H.248 Traffic
•Configuring H248.11
•Configuring Voice Quality Trigger Metric and Threshold Parameters
•How Do I Provision RPM Cards?
•How Do I Provision VISM-PR Cards?
6.11.1 RPM Management Limitation
RPM-PR is not supported on MGX modules managed by the Chassis View. MGX modules cannot monitor the RPM-PR back cards because an applicable trap is missing. The hardware and firmware revisions are also not available in the database for RPM and RPM-PR cards.
Note For the RPM-PR card, the front card shows "RPM" instead of "RPM-PR."
Support for the RPM back card is disabled by default. To obtain the RPM back card information, edit the emd.conf file before starting CTM.
Step 1 Go to /opt/svplus/config.
Step 2 Open the emd.conf file using a text editor.
Step 3 Search for "RPM_BC_Support" and replace it with one of the following values:
•RPM_BC_Support 0—Indicates that support for the RPM back card is disabled.
•RPM_BC_Support 1—Indicates that support for the RPM back card is enabled. If enabled, the RPM back card information is polled from the MGX switch.
Step 4 Save all changes to the emd.conf file.
After starting CTM, any changes to the emd.conf file will not be updated until CTM is restarted.
CTM does not distinguish between Ethernet back card versions installed with the MGX-RPM-128M/B or RPM-PR card. There is no functionality difference between the two cards.
6.11.2 How Do I Provision AXSM Cards?
Figure 6-1 Process for Provisioning AXSM Cards
The ATM Switch Service Module (AXSM) card can be provisioned in CTM as follows:
1. Enable the AXSM line—See the following sections:
–For an OC-type AXSM card, see Enabling SONET Lines for AXSM.
–For a T1-type AXSM card, see Enabling DS-1 Lines for AXSM.
–For a T3-type AXSM card, see Enabling DS3 Lines for AXSM.
2. (Optional) Create or modify APS—See Creating or Modifying AXSM Sonet Line APSs.
3. Create a port—See Creating a Port for AXSM.
4. Create a resource partition—See Creating a Resource Partition for AXSM.
5. Create a connection—See Chapter 7, "Provisioning Services and Connections."
6.11.2.1 Enabling SONET Lines for AXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, expand the node; then, double-click an AXSM (OC) card.
Step 3 Click the Lines tab. Click the line that you want to enable; then, click Details. The Line Config tab opens, with the Sonet Line Config category selected by default. The following table provides descriptions.
Step 4 Choose the Up option from the Enable drop-down list.
Step 5 (Optional) Verify or modify additional fields as necessary.
Table 6-15 Field Descriptions for the AXSM Line Config Tab, Sonet Line Config Category
Field
|
Description
|
Speed
|
An estimate of the interface's current bandwidth in units of 1,000,000 bits per second.
|
Enable
|
Desired state of the interface:
•up—Enables the line.
•down—Disables the line.
|
Loopback Type
|
Desired loopback mode configuration of the line:
•noLoopback—Specifies no loopback state.
•lineLocal—Signal sent at the line is looped back through the device.
•lineRemote—Signal sent does not go through the device but is looped back out.
|
Clock Source
|
Specifies the source of the transmit clock.
|
Frame Scramble
|
Enables or disables the scrambling option in the line.
|
Line Type
|
Configured line type.
|
Descriptor
|
Line descriptor.
|
6.11.2.1.1 Provisioning Sonet Medium Config
Step 1 Under the Line Config tab, choose the Sonet Medium Config option from the Category drop-down list. The following table provides descriptions.
Step 2 From the Medium Type drop-down list, choose the appropriate option.
Step 3 Click Apply.
Table 6-16 Field Descriptions for the AXSM Line Config Tab, Sonet Medium Config Category
Field
|
Description
|
Medium Type
|
Identifies whether a SONET or SDH signal is used across the interface.
|
Time Elapsed
|
Number of seconds (including partial seconds) elapsed since the beginning of the current measurement period.
|
Valid Intervals
|
Number of previous 15-minute intervals for which data was collected.
|
Line Coding
|
Describes the line coding for the interface signals:
•sonetMediumOther
•sonetMediumB3ZS
•sonetMediumCMI
•sonetMediumNRZ
•sonetMediumRZ
Note B3ZS and CMI are used for electrical SONET/SDH signals (STS-1 and STS-3). NRZ is used for the optical SONET/SDH signals.
|
Line Type
|
Describes the line type for this interface:
•sonetOther
•sonetShortSingleMode
•sonetLongSingleMode
•sonetMultimode
•sonetCoax
•sonetUTP
Note The line types are short- and long-range, single-mode fiber or multimode fiber interfaces; coax; and UTP for electrical interfaces.
|
Circuit ID
|
The transmission vendor's circuit identifier, for facilitating troubleshooting.
Note The circuit identifier, if available, is also represented by ifPhysAddress.
|
6.11.2.1.2 Provisioning the Sonet Line Alarm
Step 1 Under the Line Config tab, choose the Sonet Line Alarm option from the Category drop-down list. The following table provides descriptions.
Step 2 Choose the appropriate option from the Alarm Severity drop-down list. Enter data into the other fields as necessary.
Step 3 Click Apply.
Note The following thresholds are the same for the far end and the near end.
Table 6-17 Field Descriptions for the AXSM Line Config Tab, Sonet Line Alarm Category
Field
|
Description
|
Alarm Severity
|
Setting this option to major or minor generates a corresponding severity alarm when any statistical threshold is exceeded.
Note For alarm severity definitions, see Chapter 9, "Managing Faults."
|
ESs Threshold
|
Threshold value for errored seconds detection for the current 15-minute interval, above which an alarm is generated.
|
Total ESs Threshold
|
Threshold value for errored seconds detection for the 24-hour interval, above which an alarm is generated.
|
SESs Threshold
|
Severely errored seconds threshold for the current 15-minute interval, above which an alarm is generated.
|
Total SESs Threshold
|
Severely errored seconds threshold for the 24-hour interval, above which an alarm is generated.
|
CVs Threshold
|
Coding violations threshold for the current 15-minute interval, above which an alarm is generated.
|
Total CVs Threshold
|
Coding violations threshold for the 24-hour interval, above which an alarm is generated.
|
UASs Threshold
|
Unavailable seconds threshold for the current 15-minute interval, above which an alarm is generated.
|
Total UASs Threshold
|
Unavailable seconds threshold for the 24-hour interval, above which an alarm is generated.
|
Line Alarm State
|
Current alarm status of the line.
|
Line Stat Alarm State
|
Indicates the line stat alarm status.
|
6.11.2.1.3 Provisioning the Sonet Section Alarm
Step 1 Under the Line Config tab, choose the Sonet Section Alarm option from the Category drop-down list. The following table provides descriptions.
Step 2 Choose the appropriate option from the Alarm Severity drop-down list. Enter data into the other fields as necessary.
Step 3 Click Apply.
Note The following thresholds are the same for the far end and the near end.
Table 6-18 Field Descriptions for the AXSM Line Config Tab, Sonet Section Alarm Category
Field
|
Description
|
Alarm Severity
|
Setting this option to major or minor generates a corresponding severity alarm when any statistical threshold is exceeded.
Note For alarm severity definitions, see Chapter 9, "Managing Faults."
|
ESs Threshold
|
Threshold value for errored seconds detection for the current 15-minute interval, above which an alarm is generated.
|
Total ESs Threshold
|
Threshold value for errored seconds detection for the 24-hour interval, above which an alarm is generated.
|
SESs Threshold
|
Severely errored seconds threshold for the current 15-minute interval, above which an alarm is generated.
|
Total SESs Threshold
|
Severely errored seconds threshold for the 24-hour interval, above which an alarm is generated.
|
SEFSs Threshold
|
Severely errored framing seconds threshold for the current 15-minute interval, above which an alarm is generated.
|
Total SEFSs Threshold
|
Severely errored framing seconds threshold for the 24-hour interval, above which an alarm is generated.
|
CVs Threshold
|
Coding violations threshold for the current 15-minute interval, above which an alarm is generated.
|
Total CVs Threshold
|
Coding violations threshold for the 24-hour interval, above which an alarm is generated.
|
Section Alarm State
|
Current alarm status of the section.
|
Section Stat Alarm State
|
Indicates the section stat alarm status of the interface.
|
6.11.2.1.4 Provisioning the Sonet Path Alarm
Step 1 Under the Line Config tab, choose the Sonet Path Alarm option from the Category drop-down list. The following table provides descriptions.
Step 2 Choose the appropriate option from the Alarm Severity drop-down list. Enter data into the other fields as necessary.
Step 3 Click Apply.
Note The following thresholds are the same for the far end and the near end.
Table 6-19 Field Descriptions for the AXSM Line Config Tab, Sonet Path Alarm Category
Field
|
Description
|
Alarm Severity
|
Setting this option to major or minor generates a corresponding severity alarm when any statistical threshold is exceeded. By default, TCA crossing does not generate an alarm.
For alarm severity definitions, see Chapter 9, "Managing Faults."
|
ESs Threshold
|
Threshold value for errored seconds detection for the current 15-minute interval, above which an alarm is generated.
|
Total ESs Threshold
|
Threshold value for errored seconds detection for the 24-hour interval, above which an alarm is generated.
|
SESs Threshold
|
Severely errored seconds threshold for the current 15-minute interval, above which an alarm is generated.
|
Total SESs Threshold
|
Severely errored seconds threshold for the 24-hour interval, above which an alarm is generated.
|
CVs Threshold
|
Coding violations threshold for the current 15-minute interval, above which an alarm is generated.
|
Total CVs Threshold
|
Coding violations threshold for the 24-hour interval, above which an alarm is generated.
|
UASs Threshold
|
Unavailable seconds threshold for the current 15-minute interval, above which an alarm is generated.
|
Total UASs Threshold
|
Unavailable seconds threshold for the 24-hour interval, above which an alarm is generated.
|
Path Alarm State
|
Current alarm status of the path.
|
Path Stat Alarm State
|
Indicates the path stat alarm status of the interface.
|
6.11.2.1.5 Provisioning the ATM Cell Layer
Step 1 Under the Line Config tab, choose the ATM Cell Layer option from the Category drop-down list. The following table provides descriptions.
Step 2 Choose the appropriate options from the HEC Coset Enable and Payload Scrambling drop-down lists.
Step 3 Click Apply.
Table 6-20 Field Descriptions for the AXSM Line Config Tab, ATM Cell Layer Category
Field
|
Description
|
Cell Layer Description
|
This string should include the name of the manufacturer, the product name, and the version of the hardware interface.
|
Status
|
Current operational state of the interface. The testing state indicates that no operational packets can be passed.
|
Null Cell Header
|
The first four bytes of the ATM header to be used for null cells.
|
Null Cell Payload
|
Null cell payload definition. The Cisco default value is 106 (0x6A).
|
HEC Coset Enable
|
If enabled, the algorithm of Coset Polynomial Addition is applied to perform header error check calculations. It applies to transmitted as well as received cells.
|
Payload Scrambling
|
Indicates whether or not payload scrambling is enabled.
|
6.11.2.2 Enabling DS-1 Lines for AXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, expand the node; then, double-click an AXSM (T1E1) card.
Step 3 Click the Lines tab. Click the line that you want to enable; then, click Details. The Line Config tab opens. The following table provides descriptions.
Step 4 From the Admin Status drop-down list, choose the Up option.
Step 5 (Optional) Verify or modify additional fields as necessary.
Table 6-21 Field Descriptions for the AXSM DS1 Line Config Tab
Field
|
Description
|
Admin Status
|
Desired state of the interface.
|
Time Elapsed
|
Number of seconds that have elapsed since the beginning of the near-end current error measurement period.
|
Valid Intervals
|
Number of previous near-end intervals for which data was collected.
|
Line Type
|
Configured line type.
|
Line Coding
|
Type of zero code suppression used on this interface.
|
Loopback Config
|
Desired loopback configuration.
|
Line Status
|
Line status of interface.
|
Transmit Clock Source
|
Source of the transmit clock.
|
Line Length (meters)
|
Length of the DS-1 line. This value is useful only if the interface has configurable, line build-out circuitry.
|
Loopback Status
|
Current state of the loopback on the DS-1 interface.
|
Descriptor
|
Line descriptor.
|
6.11.2.3 Enabling DS3 Lines for AXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, expand the node; then, double-click an AXSM (T3E3) card.
Step 3 Click the Lines tab. Click the line that you want to enable; then, click Details. The Line Config tab opens, with the Line Config category selected by default. The following table provides descriptions.
Step 4 Choose the Up option from the Interface Status drop-down list.
Step 5 (Optional) Verify or modify additional fields as necessary.
Table 6-22 Field Descriptions for the AXSM DS3 Line Config Tab, Line Config Category
Field
|
Description
|
CDSX3 Line Type
|
Type of DS3 C-bit or E3 application implementing this interface.
|
DSX3 Line Type
|
Type of DS3 C-bit or E3 application implementing this interface.
|
Interface Status
|
State of the interface.
|
Alarm Indication Signal Bits
|
When check is set, the Alarm Indication Signal (AIS) is declared when "1010..."b is found and C-bits are all zero. When ignore is set, an AIS condition is declared when "1010..."b is detected regardless of the state of the C-bits.
|
Rcv FEAC Validation
|
Specifies the Far-End Alarm and Control (FEAC) code validation criteria.
|
Out of Frame Criteria
|
Specifies the Out of Frame decision criteria.
|
Time Elapsed Seconds
|
Number of seconds that have elapsed since the beginning of the near-end current error measurement period.
|
Valid Intervals
|
Number of previous near-end intervals for which data was collected. This value is 96 unless the interface was brought online within the last 24 hours, in which case the value is the number of complete 15-minute near-end intervals since the interface has been online.
|
Line Coding
|
Type of zero code suppression used on this interface.
|
Send Code Type
|
Type of code that the device sends across the DS3/E3 interface.
|
Circuit Identifier
|
Variable that contains the transmission vendor's circuit identifier, to facilitate troubleshooting.
|
Loopback Configuration
|
Represents the desired loopback configuration of the DS/E3 interface. dsx3NoLoop means not in the loopback state. Additional values include:
•dsx3PayLoadLoop
•dsx3LineLoop
•dsx3OtherLoop
•dsx3InwardLoop
•dsx3DualLoop
|
Interface Line Status
|
Line status of the interface.
|
Transmit Clock Source
|
Source of the transmit clock.
|
Invalid Intervals
|
Number of intervals in the range from 0 to dsx3ValidIntervals for which no data is available.
|
Line Length (meters)
|
Length of the DS3 line.
|
Descriptor
|
Line descriptor.
|
6.11.2.3.1 Setting Up Statistical Alarm Severity
Step 1 Under the AXSM DS3 Line Config tab, select the 15 Min Alarm Config option from the Category drop-down list.
Step 2 Choose the Statistical Alarm Severity level from the drop-down list. Values include:
•none
•minor
•major
Step 3 Provision additional fields as necessary. The following table provides descriptions.
Step 4 Click Apply to set up the statistical alarm severity.
Table 6-23 Field Descriptions for the AXSM DS3 Line Config Tab, 15 Min Alarm Config Category
Field
|
Description
|
Statistical Alarm Severity
|
Sets up the severity of any of the statistical alarms.
|
DS3 Line Statistics Alarm
|
Bitmap of the DS3 line statistical alarms.
|
15 Min LCV Threshold
|
If this value is exceeded in a 15-minute window, a statistical alarm is declared.
|
15 Min LES Threshold
|
15 Min PCV Threshold (only for T3)
|
15 Min PES Threshold (only for T3)
|
15 Min PSES Threshold (only for T3)
|
15 Min SEFS Threshold
|
15 Min UAS Threshold
|
15 Min CCV Threshold (only for T3)
|
15 Min CES Threshold (only for T3)
|
15 Min CSES Threshold (only for T3)
|
6.11.2.3.2 Setting Up the DSX3 24-Hour Alarm
Step 1 Under the AXSM DS3 Line Config tab, choose the Dsx3 24 Hr Alarm Config option from the Category drop-down list.
Step 2 Configure the fields; the following table provides descriptions.
Step 3 Click Apply to set up the DSX3 24-hour alarm configuration.
Table 6-24 Field Descriptions for the AXSM DS3 Line Config Tab, Dsx3 24 Hr Alarm Config Category
Field
|
Description
|
24 Hr LCV Threshold
|
If this value is exceeded in a sliding 24-hour window, a statistical alarm is declared. The threshold is checked every 15 minutes for the preceding 24-hour interval.
|
24 Hr LES Threshold
|
24 Hr PCV Threshold (only for T3)
|
24 Hr PES Threshold (only for T3)
|
24 Hr PSES Threshold (only for T3)
|
24 Hr SEFS Threshold
|
24 Hr UAS Threshold
|
24 Hr CCV Threshold (only for T3)
|
24 Hr CES Threshold (only for T3)
|
24 Hr CSES Threshold (only for T3)
|
6.11.2.3.3 Setting Up the ATM Cell Layer
Step 1 Under the AXSM DS3 Line Config tab, choose the ATM Cell Layer option from the Category drop-down list.
Step 2 Configure the fields; the following table provides descriptions.
Step 3 Click Apply to set up the ATM cell layer configuration.
Table 6-25 Field Descriptions for the AXSM DS3 Line Config Tab, ATM Cell Layer Category
Field
|
Description
|
Cell Layer Description
|
This string should include the name of the manufacturer, the product name, and the version of the hardware interface.
|
Status
|
Current operational state of the interface. The testing state indicates that no operational packets can be passed.
|
Null Cell Header
|
First four bytes of the ATM header to be used for null cells.
|
Null Cell Payload
|
Null cell payload definition. The Cisco default value is 0x6A.
|
HEC Coset Enable
|
If set to true, the algorithm of Coset Polynomial Addition is applied to perform header error check calculations. It applies to transmitted and received cells.
|
Payload Scrambling
|
Indicates whether or not payload scrambling is enabled.
|
6.11.2.3.4 Setting Up the Plcp Statistical Alarm Severity
Step 1 Under the AXSM DS3 Line Config tab, choose the Plcp Alarm option from the Category drop-down list.
Step 2 From the drop-down list, choose the Plcp Statistical Alarm Severity level. Values include:
•none
•minor
•major
Step 3 Provision additional fields as necessary. The following table provides descriptions.
Step 4 Click Apply to set up the Plcp statistical alarm severity.
Table 6-26 Field Descriptions for the AXSM DS3 Line Config Tab, Plcp Alarm Category
Field
|
Description
|
Plcp Statistical Alarm Severity
|
Severity of Plcp statistical alarm.
|
15 Min BIP8Cv Threshold
|
If this value is exceeded in a 15-minute or sliding 24-hour window, a statistical alarm is declared.
|
24 Hr BIP8Cv Threshold
|
15 Min BIP8ES Threshold
|
24 Hr BIP8ES Threshold
|
15 Min BIP8SES Threshold
|
24 Hr BIP8SES Threshold
|
15 Min BIP8SEFS Threshold
|
24 HR BIP8SEFS Threshold
|
15 Min BIP8UAS Threshold
|
24 Hr BIP8UAS Threshold
|
Plcp Line Alarm Status
|
Bitmap of the DS3 line alarms.
|
Plcp Line Stat Alarm State
|
Bitmap of the DS3 Plcp line statistical alarms.
|
6.11.2.4 Creating or Modifying AXSM Sonet Line APSs
You can provision the SONET line to have Automatic Protection Switching (APS). SRM or AXSME cards can be provisioned for APS.
If you are setting up APS on multiple cards, you must first set up an APS connector and then set up redundancy on the node. For details on setting up redundancy, see 4.5.11 Configuring Card Redundancy—MGX Voice Gateway Devices, page 4-92.
Note This tab is applicable only for OC-type AXSM cards, and not T3 or T1-type AXSM cards.
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Double-click an AXSM card.
Step 3 Click the AXSM Sonet Line APS tab. Under the Sonet Line APS tab, you can:
•Click Create to create a new SONET line APS
•Select the line that you want to modify and click Details
Step 4 Configure the fields; the following table provides descriptions.
Step 5 Click Apply to save any changes.
Table 6-27 Field Descriptions for the AXSM Sonet Line APS Tab
Field
|
Description
|
Working Bay
|
Working bay number.
|
Working Line
|
Working line number.
|
Protection Slot
|
Protection slot number.
|
Protection Bay
|
Protection bay number.
|
Protection Line
|
Protection line number.
|
Active Line
|
Indicates which line is active.
|
APS Mode
|
Provisions APS architecture mode on the working/protection line pairs.
|
Signal Fault BER
|
Contains the bit error rate threshold for signal fault detection on the working line.
|
Signal Degrade BER
|
Contains the bit error rate threshold for signal degrade detection on the working line.
|
Switch Back Time
|
Contains the interval (in minutes) to wait before attempting to switch back to the working line.
|
Switching Direction
|
Provisions the switching direction supported by this APS line.
|
APS Revertive
|
Provisions the APS revertive or nonrevertive option.
|
APS Operational Direction
|
Shows the actual APS direction that is implemented on the near-end terminal.
|
APS Operational Mode
|
Shows the actual APS architecture mode that is implemented on the near-end terminal.
|
Channel Protocol
|
Allows configuration of APS channel protocol to be implemented at the near-end terminal.
|
Line Failure Status
|
APS line failure status.
|
Line Switch Reason
|
APS line switch reason.
|
Working Section
|
Indicates which working section is the APS primary section.
|
6.11.2.5 Creating a Port for AXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, expand the node, and expand the AXSM card. Double-click the line that you want to create a port under.
Step 3 Click the Ports tab; then, click Create. The Port Config tab opens.
Step 4 Complete the active fields as necessary. The following table provides descriptions.
Step 5 Click Apply.
Table 6-28 Field Descriptions for the AXSM Port Config Tab
Field
|
Description
|
Virtual Port
|
Unique value for the ATM virtual interface.
|
Row Status
|
Status of the row.
|
Max Cell Rate
|
ATM virtual interface's max cell rate.
|
Min Cell Rate
|
ATM virtual interface's guaranteed cell rate.
|
SCT ID
|
ID of the file that holds module-specific configuration parameters for this ATM virtual interface.
|
Interface Type
|
Type of ATM virtual interface that can be provisioned within a physical interface. Values include:
•uni
•nni
•vnni
•vuni
•evuni
•evnni
|
Vpi No (VUNI/VNNI)
|
VPI number.
|
Min Vpi No (EVUNI/EVNNI)
|
Minimum VPI number.
|
Max Vpi No (EVUNI/EVNNI)
|
Maximum VPI number.
|
Descriptor
|
Port descriptor.
|
6.11.2.6 Creating a Resource Partition for AXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, expand the node, the AXSM card, and the AXSM line. Double-click the port that you want to create a resource partition on.
Step 3 Click the Resource Partitions tab; then, click Create. The following table provides descriptions.
Step 4 Enter or modify the data as necessary; then, click Apply.
Table 6-29 Field Descriptions for the AXSM Resource Partitions Tab, ATM Resource Partition Category
Field
|
Description
|
Resource Partition ID
|
Resource partition identifier.
|
Controller ID
|
Controller identifier.
|
Egress Guaranteed BW
|
Guaranteed percentage of bandwidth reserved for the resource partition in the egress direction. The range is from 0 to 1000000.
|
Egress Max BW
|
Maximum percentage of bandwidth for the resource partition in the egress direction. The range is from 0 to 1000000.
|
Ingress Guaranteed BW
|
Guaranteed percentage of bandwidth reserved for the resource partition in the ingress direction. The range is from 0 to 1000000.
|
Ingress Max BW
|
Maximum percentage of bandwidth for the resource partition in the ingress direction. The range is from 0 to 1000000.
|
Min VPI
|
Beginning of the VPI range for this partition.
|
Max VPI
|
End of the VPI range for this partition.
|
Min VCI
|
Beginning of the VCI range for this partition.
|
Max VCI
|
End of the VCI range for this partition.
|
Min Connections
|
Guaranteed number of connections that can be provisioned on this partition.
|
Max Connections
|
Maximum number of connections that can be provisioned on this partition.
|
Egress BW Used
|
Percentage of bandwidth used by the resource partition in the egress direction.
|
Egress BW Avail
|
Percentage of bandwidth available on the resource partition in the egress direction.
|
Ingress BW Used
|
Percentage of bandwidth used by the resource partition in the ingress direction.
|
Ingress BW Avail
|
Percentage of bandwidth available on the resource partition in the ingress direction.
|
Used Connections
|
Number of connections currently in use on this partition.
|
Avail Connections
|
Number of connections available that can be added on this partition.
|
6.11.2.6.1 Modifying the ILMI Configuration
Step 1 Under the AXSM Resource Partitions tab, choose the ILMI Configuration option from the Category drop-down list. The following table provides descriptions.
Step 2 Choose the appropriate options from the ILMI Enabled and ILMI Trap Enable drop-down lists, and modify data as necessary. Click Apply.
Table 6-30 Field Descriptions for the AXSM Resource Partitions Tab, ILMI Configuration Category
Field
|
Description
|
ILMI Enabled
|
Indicates whether ILMI signaling is enabled or disabled.
|
Signaling Vpi
|
VPI on which signaling cells arrive.
|
Signaling Vci
|
VCI on which signaling cells arrive.
|
ILMI Trap Enable
|
Indicates whether ILMI trap generation is enabled or disabled.
|
ILMI Est Conn Poll Intervals
|
Time S between successive transmissions of ILMI messages on this interface for detecting establishment of ILMI connectivity.
|
ILMI Connect Poll Intvl
|
Time T between successive transmissions of ILMI messages on this interface for detecting loss of ILMI connectivity.
|
ILMI Poll Conn Inact Factor
|
Number K of consecutive polls on this interface for which no ILMI response message is received before ILMI connectivity is declared lost.
|
6.11.3 How Do I Provision VXSM Cards?
Tip For detailed information on VXSM provisioning, refer to the Cisco Voice Switch Service Module (VXSM) Configuration Guide.
The Cisco MGX 8880, 8850, and 8830 support the Voice Switch Service Module (VXSM) card, which functions as a media gateway (MG) and can be provisioned to meet the requirements of a variety of applications. For VoIP switching applications, the voice Time Division Multiplexed (TDM) interface, the packet network interface, and the interface to the media gateway controller (MGC) or call agent must be provisioned.
Figure 6-2 Process for Provisioning VXSM Cards
To provision VXSM cards:
1. Create a resource partition—See Creating a Resource Partition for VXSM.
2. Create AAL5+control VXSM connections—See Chapter 7, "Provisioning Services and Connections."
3. (Optional, for OC3 cards only) Enable the mapping mode—See Enabling the Mapping Mode for VXSM.
4. Create and assign an IP address for the connection—See Creating and Assigning an IP Address for the Connection.
5. Provision the TDM interface—See Provisioning the Time-Division Multiplexing Interface for VXSM.
6. Provision voice interfaces (VIs)—See Provisioning Voice Interfaces.
7. Provision the MG and MGC interface using H.248 or XGCP protocol—See Provisioning MG-MGC Interfaces.
8. (Optional) Provision VXSM features—See How Do I Provision VXSM Features?.
9. Configure Media Security—See Configuring Media Security.
10. Create an IP Security Tunnel—See Creating an IP Security Tunnel.
6.11.3.1 Creating a Resource Partition for VXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, within the node, double-click the VXSM card.
Step 3 Click the Port tab to display the entries of the port table.
Step 4 Select the port entry.
Step 5 Click Details.
Step 6 Click the Resource Partitions tab to display the resource partitions table.
Step 7 Click Create. The Create Resource Partitions window opens.
Step 8 Configure the fields; the following table provides descriptions.
Step 9 Click Apply to create the resource partition.
Table 6-31 Field Descriptions for the VXSM Create Resource Partitions Window
Field
|
Description
|
Resource Partition ID
|
Value for the resource partition identifier. The range is from 1 to 10. The value 1 is reserved for PNNI.
|
Controller ID
|
Value for the controller identifier. The range is from 2 to 255. The value 2 is reserved for PNNI.
|
Egress Guaranteed BW
|
Guaranteed percentage of bandwidth reserved for the resource partition in the egress direction. The range is from 0 to 1000000.
|
Egress Max BW
|
Maximum percentage of bandwidth for the resource partition in the egress direction. The range is from 0 to 1000000.
|
Ingress Guaranteed BW
|
Guaranteed percentage of bandwidth reserved for the resource partition in the ingress direction. The range is from 0 to 1000000.
|
Ingress Max BW
|
Maximum percentage of bandwidth for the resource partition in the ingress direction. The range is from 0 to 1000000.
|
Min VPI
|
Beginning of the VPI range for this partition. For RPM VCC partitions, the range is from 0 to 0. For RPM VPC partitions, the range is from 1 to 255. For VXSM, the range is from 0 to 255.
|
Max VPI
|
End of the VPI range for this partition. For RPM VCC partitions, the range is from 0 to 0. For RPM VPC partitions, the range is from 1 to 255. For VXSM, the range is from 0 to 255.
|
Min VCI
|
Beginning of the VCI range for this partition. For VXSM, the range is from 1 to 65535.
|
Max VCI
|
End of the VCI range for this partition. For VXSM, the range is from 1 to 65535.
|
Min Connections
|
Guaranteed number of connections that can be provisioned on this partition. For VXSM, the range is from 1 to 8100.
|
Max Connections
|
Maximum number of connections that can be provisioned on this partition. For VXSM, the range is from 1 to 8100.
|
Egress BW Used
|
Percentage of bandwidth used by the resource partition in the egress direction.
|
Egress BW Avail
|
Percentage of bandwidth available on the resource partition in the egress direction.
|
Ingress BW Used
|
Percentage of bandwidth used by the resource partition in the ingress direction.
|
Ingress BW Avail
|
Percentage of bandwidth available on the resource partition in the ingress direction.
|
Used Connections
|
Number of connections currently in use on this partition.
|
Avail Connections
|
Number of connections available that can be added on this partition.
|
6.11.3.2 Enabling the Mapping Mode for VXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, within the node, double-click the VXSM card.
Step 3 Click the Media Gateway tab.
Step 4 Choose the Gateway Capabilities option from the Category drop-down list. The following table provides descriptions.
Step 5 Set the VT Mapping Mode to standard or titan.
Note For additional information on this field, refer to the Cisco Voice Switch Services (VXSM) Configuration and Command Reference Guide, Release 5.
Step 6 Click Apply to enable the mapping mode.
Table 6-32 Field Descriptions for the VXSM Media Gateway Tab, Gateway Capabilities Category
Field
|
Description
|
Gateway Domain Name
|
Domain name under which the media gateway can also be registered in a DNS name server.
|
VT Mapping Mode
|
Represents the VT mapping mode, which can be either:
•standard—Standard mapping mode.
•titan—Titan 5500 mapping mode. Only valid if SONET line medium type is SONET and SONET path payload type is VT1.5.
|
CM Gateway Source Filter Enabled
|
Enables or disables the source IP and port filtering. Values are:
•True—Source IP and port filter are enabled.
•False—Source IP and port filter are disabled.
|
Total Number of DSPs
|
Total number of DSPs in the card.
|
6.11.3.3 Creating and Assigning an IP Address for the Connection
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, expand the node; then, double-click the VXSM card that contains the connection you created.
Step 3 Click the Media Gateway tab.
Step 4 Choose the PVC IP Address option from the Category drop-down list.
Step 5 Click Create to display the Create PVC IP Address window.
Step 6 Configure the fields; the following table provides descriptions. Be sure to use the same VPI/VCI combination entered when you created the connection.
Step 7 Click Apply to add the IP address for the connection.
Table 6-33 Field Descriptions for the VXSM Create PVC IP Address Window
Field
|
Description
|
Index
|
Unique index to identify each media gateway IP address.
|
Interface
|
Virtual port associated to the media gateway IP address.
|
VPI
|
Represents the VPI of the PVC associated to the IP address.
|
VCI
|
Represents the VCI of the PVC associated to the IP address.
|
IP Address
|
Configured IP address of the media gateway.
|
Prefix Length
|
Specifies the number of leading one bits from the mask to be logical and-ed with the media gateway address before being compared to the value in cmgwIpCofigAddress.
|
IP Address Type
|
IP address type.
|
Default Gateway IP
|
Specifies the IP address of the entry, which will become the default gateway address.
|
6.11.3.4 Provisioning the Time-Division Multiplexing Interface for VXSM
The TDM network consists of a number of DS-1s that each contain DS-0 voice circuits, which interface with the VXSM card either through the 4-port OC-3 back card or the 24-port T1/E1 back card.
These tasks describe how to provision the TDM interface:
1. (Optional) Change the line type to SDH (by default, the line type is set to SONET)—See Changing the VXSM Line Type to SDH.
2. Complete one of the following options:
–Enable SONET lines and paths—See Enabling SONET Lines and Paths for VXSM.
–Enable SDH lines and paths—See Enabling SDH Lines and Paths for VXSM.
3. (Optional) Configure VXSM circuit identifiers—See Configuring VXSM Circuit Identifiers.
6.11.3.4.1 Changing the VXSM Line Type to SDH
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, within the node, expand the VXSM card, and double-click the first VXSM line. The Line Config tab opens.
Step 3 Choose the Sonet Medium Config option from the Category drop-down list. The following table provides descriptions.
Step 4 In the Medium Type field, click the drop-down list to choose SDH.
Step 5 Click Apply to change the line type to SDH.
Note Changing the line type to SDH on the first line trickles down to the other lines.
Table 6-34 Field Descriptions for the VXSM Line Config Tab, Sonet Medium Config Category
Field
|
Description
|
Medium Type
|
Identifies whether a SONET or SDH signal is used across the interface.
|
Time Elapsed
|
Number of seconds (including partial seconds) elapsed since the beginning of the current measurement period.
|
Valid Intervals
|
Number of previous 15-minute intervals for which data was collected.
|
Circuit ID
|
Transmission vendor's circuit identifier, for facilitating troubleshooting.
Note The circuit identifier, if available, is also represented by ifPhysAddress.
|
6.11.3.4.2 Enabling SONET Lines and Paths for VXSM
If you are using SONET, you must enable the lines and paths in the following order:
1. SONET line
2. STS path
3. DS-1/E1 line
Complete the following steps:
Step 1 Enable the SONET line:
a. Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
b. Under the Elements tab, within the node, double-click the VXSM OC3 card.
c. Click the Lines tab.
d. Click the SONET line that you want to enable; then, click Details. The Line Config tab opens, with the Sonet Line Config category selected by default. Table 6-35 provides descriptions.
e. From the Enable drop-down list, choose the up option to enable the SONET line.
f. Click Apply.
Step 2 Enable the STS path:
a. Under the Elements tab, within the node, expand the VXSM OC3 card; then, double-click the SONET line that contains the STS path you want to enable.
b. Click the STS Paths tab.
c. Click the STS path that you want to enable; then, click Details. The Path Config tab opens, with the Paths category selected by default. Table 6-36 provides descriptions.
d. (Optional) Change the channelization type to DS3, DS1, or E1 in the Path Payload field.
e. From the Enable drop-down list, choose the up option to enable the STS path.
f. Click Apply.
Step 3 Enable the DS-1/E1 line:
a. Under the Elements tab, within the node, expand the VXSM OC3 card and expand the SONET line, STS path, and VT path that contain the DS-1/E1 line you want to enable. Double-click the DS-1/E1 line. The DS1/E1 Path tab opens, with the DS1/E1 Line Info option selected by default. Table 6-37 provides descriptions.
b. From the Admin Status drop-down list, choose the up option to enable the STS path.
c. Click Apply.
Table 6-35 Field Descriptions for the VXSM Line Config Tab, Sonet Line Config Category
Field
|
Description
|
Speed
|
An estimate of the interface's current bandwidth in units of 1,000,000 bits per second.
|
Enable
|
Desired state of the interface:
•up—Enables the line.
•down—Disables the line.
|
Loopback Type
|
Desired loopback mode configuration of the line:
•noLoopback—Specifies no loopback state.
•lineLocal—Signal sent at the line is looped back through the device.
•lineRemote—Signal sent does not go through the device but is looped back out.
|
Clock Source
|
Specifies the source of the transmit clock.
|
Frame Scramble
|
Enables or disables the scrambling option in the line.
|
Line Type
|
Configured line type.
|
Descriptor
|
Line descriptor.
|
RDIV Type
|
Specifies the type of Remote Defect Indication - Virtual Tributary/Container (RDI-V) sent by this NE to the remote NE. Values include:
•onebit—(Cisco default) Specifies 1-bit RDIV.
•threebit—Specifies 3-bit enhanced RDIV.
|
RDIP Type
|
Specifies the type of Remote Defect Indication - Path (RDI-P) sent by this NE to the remote NE. Values include:
•onebit—(Cisco default) Specifies 1-bit RDIP.
•threebit—Specifies 3-bit enhanced RDIP.
|
Table 6-36 Field Descriptions for the VXSM Path Config Tab, Paths Category
Field
|
Description
|
Path Number
|
Path number.
|
Enable
|
Desired state of the interface:
•up—Enables the path.
•down—Disables the path.
|
Path Width
|
Value that indicates the type of SONET/SDH path. For SONET, the assigned types are the STS-Nc SPEs, where N equals 1, 3, 12, 24, 48, 192, or 768. STS-1 is equal to 51.84 Mb/s. For SDH, the assigned types are the STM-Nc VCs, where N equals 1, 4, 16, 64, or 256.
|
Path Payload
|
Specifies the payload carried by the SONET/SDH path. Values are:
•ds3
•vt15vc11 (DS1)
•vt2vc12 (E1)
|
Path Status
|
Indicates the status of the interface.
|
Table 6-37 Field Descriptions for the VXSM DS1/E1 Path Tab, DS1/E1 Line Info Category
Field
|
Description
|
Admin Status
|
Desired state of the interface.
|
Time Elapsed
|
Number of seconds that have elapsed since the beginning of the near-end current error measurement period.
|
Valid Intervals
|
Number of previous near-end intervals for which data was collected.
|
Line Type
|
Indicates the variety of DS-1 line implementing this circuit. Values include:
•For T1 interfaces only:
–dsx1ESF—Extended Superframe DS-1 (T1.107)
–dsx1D4—AT&T D4 format DS-1 (T1.107)
•For E1 interfaces only:
–dsx1E1—ITU-T Recommendation G.704 (Table 4a)
–dsx1E1CRC—ITU-T Recommendation G.704 (Table 4b)
–dsx1E1MF—G.704 (Table 4a) with TS16 multiframing enabled
–dsx1E1CRCMF—G.704 (Table 4b) with TS16 multiframing enabled
–dsx1Unframed—DS-1 with No Framing
–dsx1E1Unframed—E1 with No Framing (G.703)
–dsx1E1Q50—ITU-T G.704, Table 14
–dsx1E1Q50CRC—E1Q50 with CRC
|
Line Coding
|
Describes the variety of zero code suppression used in the DS-1/E1 interface, which affects the number of its characteristics.
|
Loopback Config
|
Desired loopback configuration of the DS-1/E1 interface.
|
Line Status
|
Status of the line.
|
Transmit Clock Source
|
Source of the transmit clock.
|
Line Length (Meters)
|
Length of the DS1 line in meters. This object provides information for line buildout circuitry. This object is useful only when the interface has a configurable line buildout circuitry.
|
Loopback Status
|
Current loopback state on the DS-1/E1 interface.
|
Send Code
|
Indicates what type of code is being sent across the DS-1/E1 interface. Setting this variable causes the interface to send the code requested.
|
Signal Mode
|
Signal options used by the DS-1 line for the media gateway. Values include:
•none—Indicates no bits are reserved for signaling on this channel.
•robbedBit—Indicates the DS-1 Robbed Bit Signaling is in use. This option applies only to the T1 interface.
•messageOriented—Indicates that Common Channel Signaling (CCS) is used either on channel 16 of an E1 link or channel 24 of a DS-1 link.
|
DS1 Loopback Code Detection
|
Enables or disables the detection of far-end loopback requests (inband or out-of-band ESF).
|
DS1 Repetition
|
Used to repeatedly apply the writable objects of dsx1ConfigTable and cds1ConfigTable specified in the same SNMP PDU.
|
DSx1 Circuit Identifier
|
Contains the transmission vendor's circuit identifier, which is used to facilitate troubleshooting.
|
6.11.3.4.3 Enabling SDH Lines and Paths for VXSM
If you are using SDH, you must enable the lines and paths in the following order:
1. SDH line
2. STM path
3. DS-1/E1 line
Complete the following steps:
Step 1 Enable the SDH line:
a. Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
b. Under the Elements tab, within the node, expand the VXSM OC3 card and double-click the SDH line. The Line Config tab opens.
c. From the Enable drop-down list, choose the up option to enable the SDH line.
Step 2 Enable the STM path:
a. Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
b. Under the Elements tab, within the node, expand the VXSM OC3 card and double-click the AU-3 path. The Path Config tab opens.
c. From the Enable drop-down list, choose the up option to enable the STS path.
d. (Optional) From the Tributary Grouping Type drop-down list, choose one of the following options:
•au3Grouping—Channelization appears as follows: AU-3 > TU > DS-1
•au4Grouping—Channelization appears as follows: AU-3 > TUG3 >TU > DS-1
e. Click Apply to enable the STM path.
Step 3 Enable the DS-1/E1 line:
a. Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
b. Under the Elements tab, within the node, expand the VXSM OC3 card and double-click the DS-1/E1 line. The DS1/E1 Path tab opens.
c. From the Admin Status drop-down list, choose the up option to enable the DS-1/E1 line.
6.11.3.4.4 Configuring VXSM Circuit Identifiers
CTM allows you to configure the circuit identifier on the following cards:
•VXSM T1E1, DS1 line
•VXSM T3E3, DS3 line
•VXSM OC3, SONET line
•VXSM OC3, SONET path
Complete the following steps to configure the VXSM circuit identifier:
Step 1 Select an MGX node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Do the following to configure the VXSM circuit identifier on the DS-1 line:
a. Under the Elements tab, within the MGX node, expand the VXSM T1E1 card.
b. Double-click the DS-1 line. The DS1 Path tab opens.
c. Choose DS1 Line Info from the Category drop-down list.
d. Configure the dsx1CircuitIdentifier field.
e. Click Apply.
Step 3 Do the following to configure the VXSM circuit identifier on the DS-3 line:
a. Under the Elements tab, within the MGX node, expand the VXSM T3E3 card.
b. Double-click the DS-3 line. The Line Config tab opens.
c. Choose Line Config from the Category drop-down list.
d. Configure the Circuit Identifier field.
e. Click Apply.
Step 4 Do the following to configure the VXSM circuit identifier on the SONET line:
a. Under the Elements tab, within the MGX node, expand the VXSM OC3 card.
b. Double-click the SONET line. The Line Config tab opens.
c. Choose SONET Line Config from the Category drop-down list.
d. Configure the sonetMediumCircuitIdentifier field.
e. Click Apply.
Step 5 Do the following to configure the VXSM circuit identifier on the SONET path:
a. Under the Elements tab, within the MGX node, expand the VXSM OC3 card.
b. Double-click the SONET STS path. The Path Config tab opens.
c. Choose Paths from the Category drop-down list.
d. Configure the cspSonetCircuitIdentifier field.
e. Click Apply.
6.11.3.4.5 Configuring the VXSM DS-1 Path Service State
Complete the following steps to configure the DS-1 path service state on VXSM cards:
Step 1 Select an MGX node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, within the MGX node, expand the VXSM T1E1 or VXSM OC3 card.
Step 3 Double-click the DS-1 path. The DS1 Path tab opens.
Step 4 Choose Service State Management from the Category drop-down list.
Step 5 Configure the following fields:
•cicServiceOperState—Indicates the current operating state of the service in the interface.
•cicServiceAdminState—Changes the service state of the interface. The operational service state of the interface is indicated by cicServiceOperState.
•cicServiceGraceTime—Specifies the amount of time, in seconds, before the existing call connection is shut down gracefully in the interface when cicServiceAdminState is set to gracefulOutOfService. This field is not applicable if cicServiceAdminState is set to forcefulOutOfService. A value of 0 indicates that the service on the interface will not be placed out of service until the call connection over the interface is terminated.
Use the cicServiceGraceTime field to configure the service state of the path or line to down, even if a TDM configuration exists for that particular path or line. In this way, you can prevent the VXSM card from detecting and generating statistical alarms on the TDM.
•cicServiceRepetition—Changes the service state for multiple interfaces by repeatedly applying the writable objects of cicServiceTable. The order of operation is iterated through the local order of the interface. Whether or not the iteration is applied across the physical boundary depends on the system implementation. The GET operation on this object always returns 1.
Step 6 Click Apply.
6.11.3.5 Provisioning Voice Interfaces
A voice interface (VIF) is a set of parameters applied to a group of DS-0s within a DS-1 in the TDM voice network. To provision voice interfaces:
1. Check to see if there are existing VIFs—See Checking for Existing VIFs for VXSM.
If there are no existing VIFs, proceed to Step 2. If there are existing VIFs, skip Step 2.
2. (Optional) Create a VIF—See Creating a VIF for VXSM.
3. (Optional) View or modify the VIF configuration—See Viewing or Modifying the VIF Configuration.
6.11.3.5.1 Checking for Existing VIFs for VXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, within the node, expand the VXSM card until you see the DS-1 path that you want to view VIFs under. Double-click the DS-1 path. The DS1 Path tab opens.
Step 3 Choose DSX0 Group from the Category drop-down list. Any available VIFs appear in the table. To proceed, see Provisioning Voice Interfaces.
6.11.3.5.2 Creating a VIF for VXSM
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, within the node, expand the VXSM card until you see the DS-1 path that you want to view VIFs under. Double-click the DS-1 path. The DS1 Path tab opens.
Step 3 Choose DSX0 Group from the Category drop-down list.
Step 4 Click Create. The Create DSX0 Group window opens.
Step 5 Configure the fields; the following table provides descriptions.
Step 6 Click Apply to add the VIF.
Table 6-38 Field Descriptions for the VXSM Create DSX0 Group Window
Field
|
Description
|
DSX0 Grp Index
|
Value that identifies the DS-0 group in the T1/E1 interface. The T1 range is from 0 to 23; the E1 range is from 0 to 30.
|
DS0 Channels
|
Bitmap of the selected DS-0 channels to be added into this group. The T1 range is from 1 to 24; the E1 range is from 1 to 31.
|
DSX0 Service Type
|
Specifies the service type of the CAS/DS-0 group. Values include:
•xgcp—Specifies the xgcp (tgcp) protocol.
•h248—Specifies the ITU H2.48 protocol media gateway control service type that is used when the DS-0 is provisioned for null signaling.
|
DS0 Group Repetition
|
Applicable range is from 1 to 1152 for single DS-0 configuration and from 1 to 48 for multiple DS-0 configuration.
|
6.11.3.5.3 Viewing or Modifying the VIF Configuration
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, within the node, expand the VXSM card until you see the DS-1 path that you want to view VIFs under. Double-click the DS-1 path. The DS1 Path tab opens.
Step 3 From the Category drop-down list, choose DSX0 Voice Parameters or Extended DSX0 Voice Parameters. Table 6-39 and Table 6-40 provide descriptions.
Step 4 Click a VIF; then, click Details.
Step 5 View or modify the fields.
Step 6 (Optional) Click Apply to save any changes.
Table 6-39 Field Descriptions for the VXSM DS1 Path, DSX0 Voice Parameters Category
Field
|
Description
|
DSX0 Grp Index
|
Index that uniquely identifies a DS-0 group in a T1/E1.
|
Noise Reg Enable
|
Indicates whether or not the background noise should be played to fill gaps if voice activity detection (VAD) is activated.
|
Non Linear Proc Enable
|
Indicates whether or not nonlinear processing is enabled for this interface.
|
Music On Hold Threshold
|
Music on hold threshold for this interface.
|
In Gain
|
Amount of gain inserted at the receiver side of the interface.
|
Tx Attenuation
|
Amount of attenuation inserted at the transmit side of the interface.
|
Echo Cancel Enable
|
Specifies whether or not echo cancellation is enabled for the interface.
|
Echo Cancel Coverage
|
Echo canceller coverage for the interface.
|
Initial Digit timeout
|
Initial digit timeout that indicates the amount of time the managed system waits for an initial input digit from the caller.
|
Inter Digit timeout
|
Interdigit timeout that indicates the amount of time the managed system waits for a subsequent input digit from the caller.
|
Table 6-40 Field Descriptions for the VXSM DS1 Path, Extended DSX0 Voice Parameters Category
Field
|
Description
|
DSX0 Grp Index
|
Index that uniquely identifies a DS-0 group in a T1/E1.
|
LIF Number
|
Logical interface number associated with this voice interface.
|
Call Control Profile
|
Index of call control profile used by this DS-0 group.
|
VAD Enable
|
Indicates whether or not VAD is enabled for the compression DSPs of this interface.
|
CoT 1
|
First frequency tone to be sent between the terminating and originating gateways in the continuity test.
|
CoT 2
|
Second frequency tone to be sent between the terminating and originating gateways in the continuity test.
|
Repetition
|
Used to repeatedly apply the writable objects of ccasIfExtVoiceCfgTable specified in the same SNMP PDU.
|
VAD Timer
|
Hangover time for VAD.
|
ICS Enable
|
Specifies whether or not the Idle Channel Suppression is enabled for an ATM adaptation layer 2 (AAL2) connection.
|
ICS Integration Timer
|
Specifies a timeout value for the ICS integration timer.
|
Tone Plan
|
Specifies which tone plan the DS-0 group uses for playing the tones.
|
Gateway Link ID
|
Specifies the H.248 media gateway link that this DS-0 group belongs to. This object is applicable only if the value of Service Type is h248.
|
H.248 Pkg IDs
|
H.248 packages supported in this DS-0 group.
|
Event Mapping Index
|
Specifies the actions of the voice band data signal event handling in this DS-0 group.
|
CAS Profile Index
|
Specifies the index of CAS profile that is used by this DS-0 group.
|
CAS Variant Index
|
Specifies the index of CAS variant that is used by this DS-0 group.
Note Index 26 is applicable only for VXSM T1 lines with the ServiceType set to xGCP.
|
6.11.3.6 Provisioning MG-MGC Interfaces
VXSM cards support both the ITU H.248 and the XGCP protocols. Depending on which protocol you are using, the procedure to provision the MG-MGC interface differs.
For each protocol type, the procedure consists of two phases. The first phase provisions the MGC and the MGC groups. The second phase provisions the protocol and protocol profile details that are used for the VXSM and the MGC to communicate.
Figure 6-3 Process for Provisioning MG-MGC Interfaces
Before you can provision MG-MGC interfaces, be sure you have completed the following tasks:
1. Add a resource partition to the node—See Creating a Resource Partition for VXSM.
2. Add an AAL5+control VXSM connection—See Chapter 7, "Provisioning Services and Connections."
3. Create and assign an IP address for the connection—See Creating and Assigning an IP Address for the Connection.
To provision the interface between the MG and the MGC for either protocol, complete the following tasks:
1. Set up the MGC and the MGC groups—See Setting Up MGCs and MGC Groups.
2. Provision H.248 or XGCP protocol—See Provisioning H.248 Protocol and Profiles or Provisioning XGCP Protocol.
3. Provision the MGC profile—See Provisioning H.248 Protocol and Profiles or Provisioning MGC XGCP Profiles.
4. (Optional) Provision MGC redundancy—See Provisioning MGC Redundancy.
6.11.3.6.1 Setting Up MGCs and MGC Groups
Figure 6-4 Process for Setting Up MGCs and MGC Groups
Step 1 Create an MGC by assigning it a domain name, and specify how the domain name is to be resolved:
a. Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
b. Under the Elements tab, within the node, double-click the VXSM card.
c. Click the MG Controller tab. The Domain Names category opens by default.
d. Click Create. The Create MGC Domain Names window opens.
e. Configure the fields; Table 6-41 provides descriptions.
f. Click Apply to create the domain name.
Step 2 Change the IP address resolution and (optionally) create an IP address for the domain:
a. Under the Elements tab, within the node, double-click the VXSM card.
b. Click the MG Controller tab.
c. From the Category drop-down list, choose the Media Gateway Controllers option.
d. Click an MGC entry; then, click Details. The Media Gateway Controllers tab opens. Table 6-42 provides descriptions.
e. Configure the IP Address Resolution field.
f. Click Apply.
g. If you selected internalOnly, proceed to substep h to create an IP address for the domain. If you selected externalOnly, skip the rest of these substeps and proceed to Step 3.
h. Under the MG Controller tab, from the Category drop-down list, choose the MGC IP Addresses option.
i. Click Create. The Create MGC IP Addresses window opens.
j. Configure the fields; Table 6-43 provides descriptions.
k. Click Apply to create the MGC IP address.
Step 3 (XGCP only: skip to Step 4 if you are using H.248) Provision the MGC group for XGCP:
a. Under the Elements tab, within the node, double-click the VXSM card.
b. Click the XGCP tab.
c. From the Category drop-down list, choose the XGCP MGC Association option.
d. Configure the fields; Table 6-44 provides descriptions.
e. Click Apply to provision the MGC group for XGCP.
Step 4 Add an MGC to an MGC group:
a. Under the Elements tab, within the node, double-click the VXSM card.
b. Click the MG Controller tab.
c. From the Category drop-down list, choose the MGC Groups option.
d. Click Create. The Create MGC Groups window opens.
e. Configure the fields; Table 6-45 provides descriptions.
f. Click Apply to add a specific MGC to a particular MGC group.
Table 6-41 Field Descriptions for the VXSM Create MGC Domain Name Window
Field
|
Description
|
Domain Index
|
Enter an integer to identify an MGC domain name. The following values are valid:
•For MGC, the range is from 1 to 4.
•For a gateway, the value is 13.
•For dnsServer, the value is 14.
|
Domain Name Type
|
Choose from the following types to indicate the entity for the domain name:
•gateway
•dnsServer
•mgc
|
Domain Name
|
Enter the domain name. You can enter up to 64 characters.
|
Table 6-42 Field Descriptions for the VXSM Media Gateway Controllers Tab
Field
|
Description
|
MGC Index
|
Unique index to identify each MGC that will communicate with this MG.
|
Domain Name
|
This name is the same as the name in the cMgcDomainName object of the associated entry in cMediaGwDomainNameConfigTable.
|
Number of MGC Groups
|
Number of MGC groups with which this MGC is associated. A zero value means this MGC is not associated with any MGC group.
|
Number of IP Addresses
|
Indicates the number of IP addresses associated with this MGC. A zero value means there is no IP address associated with this MGC. The MGC cannot be deleted if the value of this object is nonzero and if the IP Address Resolution field is set to internalOnly.
|
IP Address Resolution
|
Determines the type of resolution applied to this MGC. Values are:
•internalOnly—(Cisco default) Specifies the internal resolution. If the internalOnly option is chosen, the IP address associated with the file server is determined according to the IP address of the server.
•externalOnly—Specifies the external resolution.
|
Table 6-43 Field Descriptions for the VXSM Create MGC IP Address Window
Field
|
Description
|
MGC Index
|
Unique index value to identify each MGC that will communicate with this media gateway. The range is from 1 to 4.
|
IP Address Index
|
Unique index value to identify the address of a specific MGC. The MGC is represented by cMgcIndex. The range is from 1 to 4.
|
IP Address
|
Configured IP address.
|
IP Address Type
|
IP address type for the MGC (call agent):
•unknown
•ipv4
•ipv6
•ipv4z
•ipv6z
•dns
|
Preference
|
Preference value of the IP address for the specific MGC (call agent). If the value is lower, the preference of the IP address is higher. For example, the value 1 has a higher preference than the value 2. If several IP addresses have the same preference value, the media gateway selects them one at a time. The range is from 1 to 4; the Cisco default value is 1.
|
Table 6-44 Field Descriptions for the VXSM XGCP Tab, XGCP MGC Association Category
Field
|
Description
|
MGC Group Number
|
Specifies which MGC redundant group will be used in XGCP. The value of this object refers to the object cMgcGrpIndex from the MGC Redundant Group table, cMgcGrpParamTable.
|
MGC IP Addr Type
|
Specifies the address type of MGC (object cXgcpMgcConfigAddress), either ipv4 or ipv6.
|
MGC IP Address
|
Specifies the address of MGC (call agent) the gateway used to communicate within call setup.
|
Protocol Index
|
Specifies which protocol the MG should use to communicate with MGC when it attempts to set up the call.
|
cXgcpMgcConfigGatewayUdpPort
|
The UDP port of the MG that is used to communicate with the call agent in MGCP.
|
Table 6-45 Field Descriptions for the VXSM Create MGC Groups Window
Field
|
Description
|
MGC Grp Index
|
Unique index value to identify the particular MGC group. The range is from 1 to 12.
|
MGC Index
|
Unique index value to identify each MGC (call agent) that communicates with the media gateway. The range is from 1 to 4.
|
Preference
|
Preference value of the IP address for the specific MGC (call agent). If the value is lower, the preference of the IP address is higher. For example, the value 1 has a higher preference than the value 2. If several IP addresses have the same preference value, the media gateway selects them one at a time. The range is from 1 to 12; the Cisco default value is 1.
|
UDP Port
|
Value to represent the UDP port of the MGC in the MGC group. A value of 0 means that no UDP port is specified. Therefore, the UDP port that is already in the protocol table is used. The range is from 1024 to 65535.
|
6.11.3.6.2 Provisioning H.248 Protocol and Profiles
An MG communicates with a group of MGCs through an MG link. Both the MG and MGC group form an H.248 association.
Once you have completed the steps in Setting Up MGCs and MGC Groups, complete the steps shown in the following figure to provision H.248 protocol and profiles.
Figure 6-5 Process for Provisioning H.248 Protocol and Profiles
Step 1 Add an MG and MGC association:
a. Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
b. Under the Elements tab, expand the node; then, double-click the VXSM card that contains the connection you created.
c. Click the H.248 tab.
d. Choose the MG-MGC Association option from the Category drop-down list.
e. Click Create to display the Create MG-MGC Association window.
f. Configure the fields; Table 6-46 provides descriptions.
g. Click Apply to add an H.248 association between the MG and MGC. Once you have created an MG-MGC association, an entry will appear in the H.248 tab, Extended Association category.
Step 2 Provision a port for the MG-MGC link:
a. Under the Elements tab, expand the node; then, double-click the VXSM card that contains the connection you created.
b. Click the H.248 tab.
c. Choose the Extended Association option from the Category drop-down list.
d. Click a link entry; then, click Details. The Extended Association tab opens.
e. Configure the Gateway Port and other fields as necessary. Table 6-47 provides descriptions.
f. Click Apply to provision the port for the MG-MGC link.
Step 3 Add an H.248 profile:
a. Under the H.248 tab, choose the Profile Properties option from the Category drop-down list.
b. Click Create. The Create H.248 Profile Properties window opens.
c. Configure the fields. Table 6-48 provides descriptions.
d. Click Apply to create the H.248 profile.
Step 4 Provision terminations for the switch circuit network (SCN) side of VXSM:
a. Add a voice interface (VIF)—See Provisioning Voice Interfaces.
b. Associate the Gateway Link ID and H.248 package ID by completing the Gateway Link ID and H.248 Pkg IDs fields—See Viewing or Modifying the VIF Configuration.
Step 5 Provision terminations for the packet data network (PDN) side of VXSM:
a. Under the H.248 tab, choose the Termination Types option from the Category drop-down list.
b. Click Create. The Create H.248 Termination Types window opens.
c. Configure the fields; Table 6-49 provides descriptions.
d. Click Apply to create the H.248 termination type.
Table 6-46 Field Descriptions for the VXSM Create MG-MGC Association Window
Field
|
Description
|
Gateway Link ID
|
Unique link ID that identifies the signaling link this gateway uses to communicate with the gateway controllers to form an H.248 association. Enter the value of 1 to identify the MG to MGC link in the Gateway Link ID field. Only one link is supported.
|
MGC Group Index
|
Unique index value to identify the particular MGC group. The range is from 1 to 12.
|
Gateway IP Address Index
|
Index value for the IP address of the media gateway. The range is from 1 to 16.
|
Association ID
|
Unique identification of the H.248 association assigned by the H.248 stack.
|
Transport Protocol
|
From the Transport Protocol drop-down list, choose one of the following options for the signaling traffic associated with the H.248 protocol:
•tcp—(Cisco default) Transport Control Protocol (TCP)
•udp—User Datagram Protocol (UDP)
•sctp—Stream Control Transmission Protocol (SCTP)
|
TCP/UDP Port Number
|
TCP/UDP port number that the media gateway controller will use to communicate with the media gateway.
|
Active MGC Address
|
Address of the currently active MGC in this media gateway link.
|
Active MGC Port Number
|
Transport layer port number of the currently active MGC in this media gateway link.
|
Enable Dynamic TPKT Version
|
Specifies the TPKT version that is dynamically assigned based on the size of the packet presented to the TCP layer.
|
Command Maximum Message Size
|
Maximum message size on the gateway link for an H248 transaction containing the media gateway-initiated commands.
|
Reply Maximum Message Size
|
Maximum message size on the gateway link for an H248 transaction containing the media gateway reply messages to the MGC.
|
SCTP Association Id.
|
SCTP association ID related to the H.248 association. If the value is 0, it means that there is no SCTP association.
|
Media Gateway Service Change Profile
|
Name used in the profile parameter of the Service Change message to specify the attributes and behaviors of the media gateway. The default is the Cisco_TGW profile.
|
Media Gateway Service Change Profile Version
|
Version of the profile indicated in the cmedxGatewaySRVChgProfile.
|
MG Provision Rsp Time
|
Time to expect a pending response if a transaction cannot be completed in the media gateway and in the MGCs of the media gateway link.
|
MGC Provision Rsp Time
|
Time to expect a pending response from the MGC if a transaction cannot be completed.
|
MG Transaction Pending Limit
|
Number of transactions pending that MG will send.
|
MGC Transaction Pending Limit
|
Number of transactions pending that MG expects to receive.
|
Table 6-47 Field Descriptions for the VXSM Extended Association Tab
Field
|
Description
|
Gateway Link ID
|
Unique link ID that identifies the signaling link this gateway uses to communicate with the gateway controllers to form an H.248 association.
|
Gateway IP Address Index
|
MG IP address index.
|
Gateway IP Address
|
IP address that the MGC uses to communicate with the MG.
|
Gateway Port
|
TCP/UDP port number that the MGC uses to communicate with the MG.
|
Encoding Scheme
|
Used to encode the H.248 messages that are sent/received to/from the gateway controller.
|
Control Protocol
|
Control protocol type in use.
|
Maximum Contexts
|
Maximum number of contexts allowed in this media gateway link.
|
Maximum Terminations
|
Maximum number of terminations per context in this media gateway link.
|
Gateway Execution Time
|
Interval within which the MGC expects a response to any transaction from the MG (exclusive of network delay specified by the object cmedxGatewayInitialRtt).
|
MGC Execution Time
|
Interval within which the MG expects a response to any transaction from the MGC (exclusive of network delay specified by the object cmedxGatewayInitialRtt).
|
Pending Response Time
|
Time within which to expect a pending response if a transaction cannot be completed in the MG and in the MGCs of the media gateway link.
|
Retries Before Disconnect
|
Number of times the MG retries to connect to the MGC before it sends out a disconnect command.
|
Max Waiting Delay
|
Maximum amount of time to wait after powering on an MG before initiating a restart timer. This value is a random value, uniformly distributed between zero and the value specified in this object.
|
Restart Delay
|
Time delay before the MG accepts any call from MGC after it sends the service change command with a restart.
|
Response Retention Time
|
Amount of time for which responses should be retained before they are sent, if they receive a repetition of a transaction that is still being executed.
|
Initial Round Trip Time
|
Initial round-trip time for the H.248 transaction to be responded to. Reflects the network delay time.
|
Inactivity Time
|
Period of silence between messages from the MGC.
|
H.248 Header IP Address Type
|
Address type in the H.248 message header.
|
Grace Period for Service Down
|
Grace period before the media gateway link is taken out of service.
|
Active MGC Domain Name
|
Domain name of the currently active MGC in this media gateway link.
|
Operational State Change Reason
|
Reason for the operational state change (cmedGatewayOperStatus) in the media gateway link.
|
Operational State Change Method
|
Method for the operational state change (cmedGatewayOperStatus) in the media gateway link.
|
Gateway Link Service State
|
Actions for modifying the media gateway link service state.
|
Gateway Link Operational State
|
Operational status of media gateway link.
|
Table 6-48 Field Descriptions for the VXSM Create H.248 Profile Properties Window
Field
|
Description
|
H.248 Profile Index
|
Unique identifier for the H.248 profile.
|
Inter CP Tone Duration (milliseconds)
|
Duration for playing a list of call-progressing tones between two call-progressing signals.
|
Digit On Duration (milliseconds)
|
Duration of the active dual-tone multifrequency (DTMF) digit during DTMF playout from the gateway.
|
Digit Pause Duration (milliseconds)
|
Duration of the pause after an active DTMF digit during DTMF playout from the gateway.
|
Transmit COT Frequency
|
Tone frequency to be transmitted between gateways in the continuity test.
|
Receive COT Frequency
|
Tone frequency to be received between gateways in the continuity test.
|
COT Duration (milliseconds)
|
Duration for the continuity test tone to be played when the gateway initiates a continuity test tone.
|
Response COT Method
|
Method for responding to a continuity test tone when the gateway detects the continuity test signal.
|
Detect Long CP Tone Duration (milliseconds)
|
Duration for detecting a long call-progressing tone.
|
Detect Long Digit Duration (milliseconds)
|
Duration for detecting a long digit tone signal.
|
Echo Cancellation
|
Specifies whether or not the echo cancellation is enabled.
|
Echo Canceller Tail
|
Echo canceller coverage.
|
Input Gain
|
Amount of gain inserted at the receiver side of the interface.
|
Output Attenuation
|
Amount of attenuation inserted at the transmit side of the interface.
|
VoIP VAD
|
Voice Activity Detection is enabled for the compression DSPs of this interface when the application is VoIP.
|
VoIP VAD Timer (milliseconds)
|
Hangover time for VAD in the VoIP application.
|
AAL2 VAD Timer (milliseconds)
|
Hangover time for VAD in the VoATM over AAL2 application.
|
ATM Bearer Type
|
ATM bearer type.
|
AAL Partial Fill
|
Fill level of cells in case of AAL adaptation.
|
AAL Type
|
Adaption layer of ATM.
|
Suppress Bearer Digit
|
Controls whether or not the digits should be suppressed from the voice media stream.
|
Transmitted COT, Originating
|
Specifies the continuity test tone to be transmitted from the originating gateway in the continuity test.
|
Received COT, Originating
|
Specifies the continuity test tone to be received from the originating gateway in the continuity test.
|
Profile Undotted Notation
|
Supports the MIB object cmedxProfileUndottedNotation, which enables or disables the undotted notation for the coder-decoder (codec). This object is used to set codec notation to "dotted" or "undotted" in Session Description Protocol (SDP) between the gateway and the call agent. For example, G.723 is dotted, while G723 is undotted.
|
Profile Annexab Enabled
|
Supports the MIB object cmedxProfileAnnexabEnabled, which specifies the format for parsing or generating G.723 or G.729 codec in SDP messages for the media gateway. A value of true means you are using Annex A and B in the FMTP line to comply with RFC 3555. A value of false means you are using Annex A and B in the SDP attribute codec string.
|
Table 6-49 Field Descriptions for the VXSM Create H.248 Termination Types Window
Field
|
Description
|
Termination Type ID
|
Unique identification number that is assigned to the termination type by the manager.
|
H.248 Packages Applied
|
H.248 packages applied to this termination type.
|
Termination Type
|
Type of a group of ephemeral terminations.
|
Profile ID
|
Property profile identifier with which the terminations within this termination type will be associated.
|
6.11.3.6.3 Provisioning XGCP Protocol
Once you have completed the steps in Setting Up MGCs and MGC Groups, complete the following steps to provision the XGCP (TGCP) protocol:
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, within the node, double-click the VXSM card.
Step 3 Click the XGCP tab. The Media Gateway XGCP Configuration option opens by default in the Category drop-down list.
Step 4 Configure the fields; the following table provides descriptions.
Step 5 Click Apply to provision the XGCP (TGCP) protocol.
Table 6-50 Field Descriptions for the VXSM XGCP Tab, Media Gateway XGCP Configuration Category
Field
|
Description
|
Request Timeout (milliseconds)
|
Period that the XGCP (TGCP) protocol waits before retransmitting an unacknowledged message. It is the responsibility of the requesting entity to provide suitable timeouts for all outstanding commands, and to retry commands when timeouts are exceeded.
|
MG Max Exp Retry Timeout (milliseconds)
|
Specifies the maximum timeout for exponential command retry by the media gateway.
|
Max Waiting Delay Timeout (milliseconds)
|
Value used for the media gateway to send the first restart in progress to the MGC in an implementation-dependent manner. This value is based on the call volume of the system.
|
Restart Delay (seconds)
|
Specifies the restart delay timeout for the restart process for a gateway to send a RestartInProgress when it is powered on or reset.
|
Default Package
|
Represents the default capability package supported in the gateway.
|
Supported Packages
|
Represents the bit map of MGCP supported packages.
|
Simple SDP Enabled
|
Used to enable or disable building of s, t, and o lines in the Sessions Description Protocol (SDP) message. The o field indicates the owner/creator and session identifier. The s field indicates the session name field. The t field indicates the duration while a session is valid. A value of true (enabled) means that SDP will NOT include the fields s, t, and o. A value of false (disabled) means that the o, s, and t lines will be built before sending SDP.
|
AckSDP Enabled
|
Specifies whether the ACK SDP is enabled or disabled. If the value is true (enabled), it sends ADP with ACK when codec or reportable NTE delta changes, or an attempt is made to change codec, VAD, packet-period, or echo cancellation in FAX/modem mode.
|
Undotted Notation Enabled
|
Enables or disables the undotted notation for codec. This object is used to set codec notation to dotted or undotted in SDP between the gateway and the call agent.
|
Process Quarantine Events
|
Determines how to handle persistent events. If the value is true, the quarantined events are processed; otherwise the quarantined events are discarded.
|
Quarantine Loop Enabled
|
Controls the default quarantine mode. If the value is true, the default quarantine mode is loop and not step. The gateway is expected to generate multiple notifications (loop).
|
Bypass Quarantine Buffer
|
Specifies how the persistent events will be handled in quarantine processing. If the value is true, the persistent events bypass the quarantine buffer. If the value is set to false, this object will be ignored.
|
Piggyback Message Enabled
|
Enables or disables the piggyback message generation. If the value is true, a call agent can send several MGCP messages in the same UDP packets to the gateway.
|
Max XGCP Msg Size (bytes)
|
Specifies the maximum XGCP (TGCP) message size that is supported by the call agent via an AuditEndPoint response. A value of zero means there is no limit to the size of the XGCP message.
|
Dtmf Relay
|
When the value is true, the digits are sent as peer-to-peer packets in the bearer. When the value is false, the digits are sent as regular voice packets in the bearer.
|
Calea Enabled
|
CALEA, or Communication Assistance for Law Enforcement Act, is a feature that allows for a lawful intercept of the details and contents of a call originating or terminating on specific terminals. A value of true indicates that CALEA is enabled; a value of false indicates that CALEA is disabled.
|
Gateway Service State
|
Defines the service state of the media gateway.
|
Gateway Admin State
|
Defines the administrative state of the media gateway.
|
Grace Time (seconds)
|
Represents the grace period (restart delay in RSIP message), in seconds. It indicates how soon the gateway will be taken out of service. A value of -1 indicates that the grace period time is disabled.
|
6.11.3.6.4 Provisioning MGC XGCP Profiles
To provision MGC XGCP profiles, you must create a call control profile.
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, within the node, double-click the VXSM card.
Step 3 Click the XGCP tab.
Step 4 Choose the XGCP Call Control Profile Configuration option from the Category drop-down list.
Step 5 Click Create. The Create XGCP Call Control Profile window opens.
Step 6 Configure the fields; the following table provides descriptions.
Step 7 Click Apply to create the XGCP (TGCP) call control profile.
Table 6-51 Field Descriptions for the VXSM Create XGCP Call Control Profile Window
Field
|
Description
|
Profile Index
|
Uniquely identifies the call control profile.
|
Profile Name
|
Unique name for the profile. This cannot be modified once it is created.
|
Total VIFs Associated
|
Total number of voice interfaces (DS-0 group) associated with this call control profile. A value of zero means there are no voice interfaces associated with the profile.
|
Protocol Index
|
Specifies the protocol that the MG should use to communicate with the MGC during call setup.
|
Suspicious Error Threshold
|
Contains the suspicious error threshold for signaling messages.
|
Max1 DNS Lookup Enabled
|
Enables or disables the Max1 DNS query operation when Max1 expires.
|
Disconnect Error Threshold
|
Contains the disconnect error threshold for signaling messages.
|
Max2 DNS Lookup Enabled
|
Enables or disables the Max2 DNS query operation when Max2 expires.
|
Message Waiting Indicator Timeout (milliseconds)
|
Timeout value for the message waiting indicator (MWI) tone. The MWI tone is used with message waiting services, and indicates that the MG is not ready to accept address information or other information from an access line.
|
Retransmission Removal Timeout (seconds)
|
Timeout value for retransmission removal.
|
Initial Waiting Delay Timeout (seconds)
|
The voice interface (DS-0 group) becomes disconnected when the MG tries to communicate with the call agent and the retransmission procedure times out after retrying.
|
Min Waiting Delay Timeout (seconds)
|
The DS-0 group (voice interface) becomes disconnected when the MG tries to communicate with the call agent and the retransmission procedure times out after retrying.
|
Max Waiting Delay Timeout (seconds)
|
Maximum waiting delay (Tdmax) timeout value used by the MG to send the restart in progress with the restart method as RM:disconected to the call agent when the voice interface-associated ds0-group disconnection condition occurs.
|
Critical Timer Timeout (seconds)
|
Represents the timeout value for the critical timer.
|
Partial Dial Timeout (seconds
|
Represents the partial dial timeout and is used along with a digit map as the interdigit timer.
|
History Timeout (seconds)
|
The value of cxeCcProfileThisTimeout, which specifies the number of seconds for which responses to old transactions must be kept. The MGCP protocol is organized as a set of transactions, each of which is composed of a command and a response. In the absence of a timely response, commands are repeated. The MG must keep in memory a list of the responses it has sent to recent transactions, and a list of the transactions that are currently being executed.
|
Local Ring Back Tone Timeout (seconds)
|
The time for which the local ring-back tone (toward the TDM) will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
Remote Ring Back Tone Timeout (seconds)
|
Specifies the time for which the remote ring-back tone (toward the packet network) will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
Congestion Tone Timeout (seconds)
|
Specifies the time for the network congestion tone to be generated. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
Busy Tone Timeout (seconds)
|
Specifies the time for which the busy tone will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
Dial Tone Timeout (seconds)
|
Specifies the time for which the dial tone will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
Confirmation Dial Tone Timeout (seconds)
|
Specifies the time for which the stutter or confirmation dial tone will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
Ringing Cadence Tone Timeout (seconds)
|
Specifies the time for which the ringing cadence will be generated toward the basic PBX unless interrupted. A value of zero indicates that the cadence will be generated indefinitely unless interrupted.
|
Reorder Tone Timeout (seconds)
|
Specifies the time for which the reorder tone or fast busy tone will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
COT1 Timeout (seconds)
|
Specifies time for which the continuity test tone 1 will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
COT2 Timeout (seconds)
|
Specifies time for which the continuity test tone 2 will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
|
6.11.3.6.5 Provisioning MGC Redundancy
MGCs provisioned in an MGC group form a set of redundant MGCs, up to a maximum of four. The order in which MGCs are added to the group is the order of preference for selecting the MGC to use. Besides having up to four MGCs in a group, each MGC can have up to four IP addresses.
The tasks involved in provisioning MGC redundancy are:
1. Create an MGC by assigning it a domain name, and specify how the domain name is to be resolved (see Step 1 in Setting Up MGCs and MGC Groups).
2. Change the IP address resolution and (optionally) create an IP address for the domain (see Step 2 in Setting Up MGCs and MGC Groups).
3. Add another MGC to an MGC group (see Step 4 in Setting Up MGCs and MGC Groups).
6.11.4 Configuring Stream Control Transmission Protocol for H.248 Traffic
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, expand the node; then, double-click the VXSM card.
Step 3 Click the H.248 tab.
Step 4 Choose the SCTP Config option from the Category drop-down list.
Step 5 Click a configuration entry; then, click Details. The H.248 tab opens.
Step 6 Configure the fields; the following table provides descriptions.
Step 7 Click Apply.
Table 6-52 Field Descriptions for the H.248 Tab, SCTP Config Category
Field
|
Description
|
Config Index
|
Index that uniquely identifies an entry in the csctpConfigTable.
|
Init Retransmission Interval
|
Upper-bound retransmission timeout for initialization and cookie chunks to be transmitted before reporting failure for association request. Changing this value does not affect the existing association because this parameter is used during association initialization. If this value is changed after the association initialization, the new value is used when restarting the association.
|
Max Init Retransmission
|
Maximum number of times that the SCTP initialization and cookie chunks are retransmitted before reporting failure for association request. Changing this value does not affect the existing association because this parameter is used during association initialization. If this value is changed after the association initialization, the new value will be used when restarting the association.
|
Min Retransmission Timeout
|
Lower-bound for retransmission timeout.
|
Max Retransmission Timeout
|
Upper-bound for retransmission timeout.
|
Max Association Retransmissions
|
Maximum number of association retransmissions of MEGACO. This value is sent to the SCTP, and if the number of retransmissions go over this value, the association will fail.
|
Keep Alive Interval
|
Heartbeat timeout interval for the IP.
|
Path Retransmission for Remote IP
|
SCTP path retransmission for the remote IP. The remote IP is considered inactive after retransmitting the value specified.
|
Type of Service
|
Type of Service (ToS) of IP header for the SCTP.
|
Inbound Streams
|
Number of inbound streams according to the negotiation at association startup.
|
Outbound Streams
|
Number of outbound streams according to the negotiation at association startup.
|
6.11.5 Configuring H248.11
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Under the Elements tab, expand the node; then, double-click the VXSM card.
Step 3 Click the H.248 tab.
Step 4 Choose the H248.11 (Overload Control Configuration) option from the Category drop-down list.
Step 5 Configure the fields; the following table provides descriptions.
Step 6 Click Apply.
Table 6-53 Field Descriptions for the H.248 Tab, H248.11 (Overload Control Configuration) Category
Field
|
Description
|
Overload Control Enable
|
Indicates whether the H.248 overload package and its features are applied to the media gateway.
|
Overload Notify State
|
Indicates the state of the current media gateway overload notifications. Values are:
•true—When the media gateway is overloaded, it notifies the MGC.
•false—When the media gateway is overloaded, it does not notify the MGC.
|
Notify Enabled Bitmap
|
Indicates the bitmap representation of the H248 association index number, which indicates whether the gateway overload notification is enabled.
|
6.11.6 Configuring Voice Quality Trigger Metric and Threshold Parameters
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Under the Elements tab, expand the node; then, double-click a VXSM (T1E1) card.
Step 3 Click the H248.30 (Voice Quality Monitoring) tab.
Note The H248.30 (Voice Quality Monitoring) tab is available only when you select a VXSM card version 3.0 or later. The tab displays alert triggers for DS1 levels.
Step 4 Specify the DSP management voice parameters:
a. Choose the DSP Management Voice Parameter option from the Category drop-down list.
b. Configure the fields described in Table 6-54 > DSP Management Voice Parameter Category.
c. Click Apply.
Step 5 Create the RTCP profile:
a. Choose the RTCP Profiles option from the Category drop-down list.
b. Click Create and configure the fields described in Table 6-54 > RTCP Profiles Category.
c. Click Apply.
Step 6 Configure the RTCP:
a. Choose the RTCP Configuration option from the Category drop-down list.
b. Configure the fields described in Table 6-54 > RTCP Configuration Category.
c. Click Apply.
Step 7 Specify the Gateway RTCP alert triggers:
a. Choose the Gateway RTCP Alert Triggers option from the Category drop-down list.
b. Configure the fields described in Table 6-54 > Gateway RTCP Alert Triggers Category.
c. Click Apply.
d. To view the virtual gateway RTCP alert triggers, choose the Virtual Gateway RTCP Alert Triggers option from the Category drop-down list.
Step 8 Specify the media gateway DSP voice parameters:
a. In the H248.30 (Voice Quality Monitoring) tab, click the Media Gateway subtab.
b. Choose the DSP Voice Parameters option from the Category drop-down list.
c. Configure the fields described in Table 6-54 > Media Gateway Tab > DSP Voice Parameters Category.
d. Click Apply.
Table 6-54 Field Descriptions for the H248.30 (Voice Quality Monitoring) Tab
Field
|
Description
|
DSP Management Voice Parameter Category
|
VQM Control
|
Enables or disables the voice quality monitor (VQM) feature. If disabled, DSP does not measure the voice quality, and H.248.30 packages cannot be configured.
|
RTCPXR Enable
|
Controls the Real-time Control Protocol Extended Report (RTCPXR). If enabled, both transmission and receipt of RTCPXR packets are enabled. If disabled, the transmission of RTCPXR packets is disabled, and any receipt of RTCPXR packets is ignored.
|
RTCPXR Report Frequency
|
Used to configure the RTCPXR report frequency. If set to 0, the RTCPXR report is not sent to the remote gateway.
|
Default Minimum Gap Value
|
Default minimum gap value configured for the IP stream.
|
External R Factor Metric Value
|
A value of 127 means that the object is not applicable.
|
VQM Threshold SES Value
|
Specifies the threshold, in milliseconds, for severely errored seconds (SESs) on the VQM.
|
RTCP Profiles Category
|
Index
|
Index that uniquely identifies an entry in the cMediaGwTable.
|
Profile Index
|
Index for RTCP profiles. An index value of 1 implies the system default profile. You can modify the default profile, but you cannot delete it.
|
Packet Loss Rate Threshold Reference
|
Reference value of the packet loss rate threshold for voice. A quality alert is triggered when the measured value exceeds the cRtcpXrProfPktLossRateVoiceQA percentage of this value.
|
Packet Loss Rate VoIP Metric
|
Threshold percentage for the packet loss rate VoIP metric. This voice profile entry contains a reference value of packet loss rate for the voice phase. A voice quality alert is triggered when the measured value of the packet loss rate for voice phase exceeds the reference value—given by cRtcpXrProfPktLossRateVoiceRef—by at least the percentage given by cRtcpXrProfPktLossRateVoiceQA.
|
VBD Quality Alert
|
Quality alert threshold percentage of packet loss rate for the Voice Band Data (VBD) phase in this voice profile entry. A voice quality alert is triggered when the measured value of the packet loss rate for the VBD phase exceeds the reference value—given by cRtcpXrProfPktLossRateVbdRef—by at least the percentage given by cRtcpXrProfPktLossRateVbdQA.
|
RTCP Configuration Category
|
Alert Throttle Rate
|
Maximum number of quality alerts sent to an MGC in a specific time interval.
|
Alert Throttle Interval
|
Time interval used to identify the alert throttle rate.
|
Notification Throttle Rate
|
Maximum number of VQM notifications sent to the SNMP manager in a specific time interval.
|
Notification Throttle Interval
|
Time interval used to identify the notification throttle rate.
|
Notification Enable
|
Enables or disables RTCPXR-related notifications.
|
Gateway RTCP Alert Triggers Category
|
Trigger Index
|
Index of the table, which can be used to represent a specific interface or gateway.
|
Trigger Index Type
|
Type of index.
|
Trigger Index Name
|
Index name for the cRtcpXrAlertTriggerIndex object.
|
Voice Trigger Type
|
Type of voice trigger.
|
VBD Trigger Type
|
Type of VBD trigger.
|
Alert Provide Index
|
Identifies which profile will be used. The value should be equal to cRtcpXrProfileIndex.
|
Media Gateway Tab > DSP Voice Parameters Category
|
SID Payload Type
|
Specifies the Real Time Protocol (RTP) payload type of the Silence Insertion Descriptor (SID) packet that is sent to the remote endpoint at the onset of silence suppression.
|
RTCP Control
|
Controls whether Real Time Control Protocol (RTCP) is enabled.
|
RTCP Interval
|
Specifies the RTCP report interval, as defined in RFC 1889.
|
RTCP Interval Multiplier
|
Specifies how many times the RTCP reports can fail before an exception condition activity can be performed.
|
VAD Adaptive
|
Enables or disables the adaptive VAD knob of the VAD algorithm.
|
DTMF Power Level
|
Specifies the power level of the low-frequency component.
|
DTMF Power Twist
|
Specifies the relative power level of the high-frequency component of DTMF.
|
RTCP Timer Control
|
Specifies when the RTCP receive timer is started. Values are:
•disabled—RTCP receive timer is disabled.
•startImmediately—RTCP receive timer starts immediately after RTCP is enabled on the call.
•startRtpOrRtcpPktRcvd—RTCP receive timer starts upon receiving the first RTP or RTCP packet.
•startRtcpPktRcvd—RTCP receive timer starts upon receiving the first RTCP packet.
|
Non-transcoding IP-IP Conn Mode
|
Configures the MIB object cdspVoiceModeIPIP for DSP voice parameters. VXSM as a transcoding gateway depends on a set of bearer properties on the IP terminations. If the bearer properties are different between the two terminations of the IP gateway, the VXSM is a transcoding type. If the bearer properties are the same, the VXSM is a nontranscoding type. The values for the Non-transcoding IP-IP Conn Mode field are:
•fastRoute—If the IP-IP connection is established such that the bit exactness of the payload is maintained, the call is established in Fast Routing mode.
•transparent—If the bit exactness of both the payload and the associated header is maintained, the call is established in Transparent mode.
•normal—In a nontranscoding type of connection, if the bit exactness of both the header and the payload is not maintained, the call is established in Normal mode. In Normal mode, even if the bearer properties are the same, the IP packets are converted to linear samples and then encoded back to IP packets. This conversion adds to the processing overhead but offers advantages over Transparent and Fast Routing mode.
|
6.11.6.1 How Do I Provision VXSM Features?
This section contains the following information:
•Setting up an RUDP Session
•Creating an MGC Session Set
•Creating an MGC Session Group
•Creating an RUDP Session
•Provisioning Voiceband Data
•Creating PRI-BH
•Provisioning Announcement Control Parameters
•Provisioning the CAS Feature
•Creating a Gateway Instance
•Modifying a Gateway Instance
•Deleting a Gateway Instance
•Creating a Gateway Point Code
•Modifying a Gateway Point Code
•Deleting a Gateway Point Code
•Creating a GSP Linkset
•Modifying a GSP Linkset
•Deleting a GSP Linkset
•Creating a GSP Link
•Modifying a GSP Link
•Deleting a GSP Link
•Creating a GSP Profile Timer
•Modifying a GSP Profile Timer
•Deleting a GSP Profile Timer
•Creating a Gateway Route
•Modifying a Gateway Route
•Deleting a Gateway Route
•Creating a MTP3/SCCP User Adaption (XUA)
•Modifying a MTP3/SCCP User Adaption (XUA)
•Deleting a MTP3/SCCP User Adaption (XUA)
•Creating an XUA Local IP
•Modifying an XUA Local IP
•Deleting an XUA Local IP
•Creating an XUA ASP
•Modifying an XUA ASP
•Deleting an XUA ASP
•Creating an XUA QOS
•Deleting an XUA QOS
•Creating an XUA ASP Remote IP
•Modifying an XUA ASP Remote IP
•Deleting an XUA ASP Remote IP
•Creating an XUA AS
•Modifying an XUA AS
•Deleting an XUA AS
•Creating an XUA ASP AS
•Modifying an XUA ASP AS
•Deleting an XUA ASP AS
•Creating an XUA AS Route
•Deleting an XUA AS Route
•Creating an XUA AS Route AS
•Modifying an XUA AS Route AS
•Deleting an XUA AS Route AS
•Creating a GTT Selector
•
