- LG Software Innovations Coffeemaker User Manual
Table Of Contents
- Title Page
- Revision history
- Contents
- About this guide
- Description
- System requirements
- List of ITG ISDN components
- Ordering rules and guidelines
- ITG ISL Trunk card description
- ITG ISL Trunk card physical description
- ISDN Signaling Link
- Dialing plans
- Quality of Service
- Fallback to alternate facilities
- Type of Service
- Fax support
- Remote Access
- Per-call statistics support using RADIUS Client
- SNMP MIB
- Codec profiles
- Security passwords
- ITG Engineering Guidelines
- Introduction
- Network engineering guidelines overview
- ITG traffic engineering
- Configuration of Meridian 1 routes and network translation
- Assess WAN link resources
- QoS Evaluation Process Overview
- Set QoS
- Measure intranet QoS
- Implement QoS in IP networks
- ITG Trunk DSP profile settings
- Post-installation network measurements
- Estimate QoS level
- ITG MAT PC management configuration
- Install and configure ITG ISL Trunk node
- Before you begin
- Installation Procedure Summary
- Create the ITG Trunk Installation Summary Sheet
- Install and cable ITG trunk cards
- Install NTCW84JA Large System I/O Panel 50-Pin filter adapter
- Install NTMF94EA and NTCW84KA cables
- D-channel cabling for the NT0961AA 24-Port ITG Trunk card
- Set NT6D80 MSDL switches
- Install filter and NTND26 cable (for MSDL and DCHIP cards in same Large System equipment row)
- Install filter and NTND26 cable (for MSDL and DCHIP cards in different Large System equipment rows)
- Configure ITG Trunk data on the Meridian 1
- Configure dialing plans within the corporate network
- Configure ITG Trunk data on MAT
- Transmit ITG trunk card configuration data from MAT to the ITG trunk cards
- Set date and time for the ITG ISL Trunk node
- Change the default ITG shell password to maintain access security
- Change default ESN5 prefix for non-ESN5 IP telephony gateways
- Check card software
- Configure MAT Alarm Management to receive SNMP traps from ITG ISL Trunk cards
- Make test calls to the remote ITG nodes
- Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks
- Upgrade procedure summary
- Before you begin
- Install the DCHIP hardware upgrade kit
- Upgrade the 8-port ITG basic trunk software to ITG ISL trunk software
- Remove ITG 1.0 configuration data from Meridian 1
- Configure the Meridian 1 ITG ISL Trunk data: upgrade considerations
- Verify ROM-BIOS version
- Upgrade Troubleshooting
- OA&M using MAT applications
- OA&M using the ITG shell CLI and overlays
- Maintenance
- Appendix A: Calbe description and NT8D81BA cable replacement
- NTMF94EA E - LAN, T - LAN and Serial Port cable
- NTCW84KA E-LAN, T-LAN, DCH & Serial cable
- NTAG81CA Faceplate Maintenance cable
- NTAG81BA Maintenance Extender cable
- NTCW84EA DCH PC Card Pigtail cable
- NTMF04BA MSDL extension cable
- NTCW84LA and NTCW84MA upgrade cables
- Prevent ground loops on connection to external customer LAN equipment
- Replace cable NT8D81BA with NT8D81AA
- Tools list
- NT8D81BA cable removal procedures
- Appendix B: Environmental and electrical regulatory data
- Appendix C: Subnet mask conversion from CIDR to dotted decimal format
- Appendix D: Configure a Netgear RM356 modem router for remote access
- Index
- Back

Page 326 of 378 Maintenance
553-3001-202 Standard 1.00 April 2000
Log files, such as Alarm and Trace files, if any, are written to the Flash File
volume and not lost when the card fails. Operational Measurement files are
recorded hourly and need to be uploaded to the MAT PC or other external
device for generating weekly or monthly traffic reports.
MAT
MAT 6.6 has backup and restore procedures for all data downloaded from, or
to, the card. When a MAT terminal is connected to the card, user intervention
is necessary to transmit all lost data from the MAT terminal to the ITG card.
Command line interface
If MAT is temporarily unavailable, the ITG shell command line interface can
be used to retrieve configuration files from an FTP server or from a PC card.
Fault clearance procedures
DSP failure
In the case where one of the DSPs does not respond, a DSP reset is
automatically initiated by the host and an dspResetAttempted alarm is raised.
If the DSP fails to recover after the reset, a dspResetFailed alarm is raised and
that DSP is marked as unusable. Any channels associated with that DSP will
cease to respond to the Meridian 1 and are ultimately taken out of service by
the Meridian 1 background audit procedures.
If a DSP fails, the following can occur:
• A DSP fails when no channel on it is in use (that is, no existing call uses
that DSP). All channels associated with that DSP are marked as DISabled
until the DSP recovers. The leader card is notified so that no incoming
call is assigned to those channels.
• A DSP fails when at least one of its channels is in use. All calls associated
with that DSP are dropped and all its channels are put into the DISabled
state. The leader card is notified so that no incoming call is assigned to
those channels.
When the Meridian 1 initiates a call at a channel of a failed DSP, the DCHIP
card sends a “RELease COMplete” message in response to indicate that the
channel cannot be used. Then, the Meridian 1 generates the alarm “PRI0101”
and locks out the trunk by marking it “BUSY”. This mechanism is also used
to lock out a channel that does not have a corresponding DSP port.