Motorola 49901 Software Release Notes - Page 49

Alarms when Doing Warm or Cold Boot of Release 5.5 - Vanguard 6455

Get Motorola 49901 - Vanguard 340 Router PDF manuals and user guides
UPC - 786523499018
View all Motorola 49901 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 49 highlights

Known Software Limitations Part No. T0001-42, Rev C October, 2002 Page 49 of 103 Alarms when Doing Warm or Cold Boot of Release 5.5 - Vanguard 6455 The alarm message "DBG-Error-Module:L3 Function:L3_Go Error:L3_Get_NLCB failed" may display when you boot the node during the handling of the T314_timer expiry. These alarms do not impact the node's functionality. (DRCaa22131) Workaround: At present, there is no workaround. T1 N. American ISDN B-Channels appear IDLE - Vanguard 6400 Series When you look at the detailed PRI statistics with the D-channel connected, all of the associated B-channels are shown to be in an IDLE state, even if some of the channels are not configured in the ISDN interface. (DRCaa22080) Workaround: At present, there is no workaround. Digital Voice Server Card - Vanguard 6400 Series T1/E1 Interface 5 will not get initialized if Interface 4 is not configured. T1/E1 Interface 7 will not get initialized if Interface 6 is not configured. (DRCaa21619) Workaround: Always configure both interfaces even if only the second interface on the card is used. Channelized Data is not Supported for Ports 7, 10 or 13 - 6400 Series Although the "Channelized" and "ISDN-PRI" data features are configurable under the "Format Type" parameter for T1/E1 daughter cards on the Vanguard 6400 Series products, these features are not supported, and their use can result in unpredictable behavior. (DRCaa22019) Workaround: Do not configure "Format Type" to "Channelized" or "ISDN-PRI". Be sure to set the default "Format Type" parameter to "Fractional". Packet Re-construction Statistic Running 8kbps is Inaccurate Vanguard 6400 Series When the time for packets to reach DSP exceeds the smoothing-delay time, DSP increments the reconstruct packet counter. With 60 voice ports configured and Voice Activity Detection (VAD) turned on, excessive reconstructed packets are reported. (DRCaa21596) Workaround: At present, there is no workaround. Alarms Can Indicate Poor Voice Quality - Vanguard 6400 Series If you are running G.729 (8kbps), you might see the MED level alarm reported: VOICE-125 DEBUG INFO: OP_ALARM_NFY: Error_indication 0, Error_code c. This could indicate poor voice quality. (DRCaa21755) Workaround: If this alarm message appears and you are experiencing voice quality problems, run G.723 (6.3kb). Inaccurate FXS Port Statistics Regarding Delay - All products On the FXS port statistics second page, the values presented for delay are not accurate and might erroneously indicate delay problems. (DRCaa20935) Workaround: To determine the actual delay, enable DELAY TRACE under the FXS port options.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
Part No. T0001-42, Rev C
October, 2002
Known Software Limitations
Page 49 of 103
Alarms when Doing Warm or Cold Boot of Release 5.5 - Vanguard 6455
The alarm message "DBG-Error-Module:L3 Function:L3_Go Error:L3_Get_NLCB
failed" may display when you boot the node during the handling of the T314_timer
expiry. These alarms do not impact the node's functionality. (DRCaa22131)
Workaround:
At present, there is no workaround.
T1 N. American ISDN B-Channels appear IDLE - Vanguard 6400 Series
When you look at the detailed PRI statistics with the D-channel connected, all of the
associated B-channels are shown to be in an IDLE state, even if some of the channels
are not configured in the ISDN interface. (DRCaa22080)
Workaround:
At present, there is no workaround.
Digital Voice Server Card - Vanguard 6400 Series
T1/E1 Interface 5 will not get initialized if Interface 4 is not configured. T1/E1
Interface 7 will not get initialized if Interface 6 is not configured. (DRCaa21619)
Workaround:
Always configure both interfaces even if only the second interface on
the card is used.
Channelized Data is not Supported for Ports 7, 10 or 13 - 6400 Series
Although the "Channelized" and "ISDN-PRI" data features are configurable under
the "Format Type" parameter for T1/E1 daughter cards on the Vanguard 6400 Series
products, these features are not supported, and their use can result in unpredictable
behavior. (DRCaa22019)
Workaround:
Do not configure "Format Type" to "Channelized” or “ISDN-PRI". Be
sure to set the default “Format Type” parameter to “Fractional”.
Packet Re-construction Statistic Running 8kbps is Inaccurate -
Vanguard 6400 Series
When the time for packets to reach DSP exceeds the smoothing-delay time, DSP
increments the reconstruct packet counter. With 60 voice ports configured and Voice
Activity Detection (VAD) turned on, excessive reconstructed packets are reported.
(DRCaa21596)
Workaround:
At present, there is no workaround.
Alarms Can Indicate Poor Voice Quality - Vanguard 6400 Series
If you are running G.729 (8kbps), you might see the MED level alarm reported:
VOICE-125 DEBUG INFO: OP_ALARM_NFY: Error_indication 0, Error_code c.
This could indicate poor voice quality. (DRCaa21755)
Workaround:
If this alarm message appears and you are experiencing voice quality
problems, run G.723 (6.3kb).
Inaccurate FXS Port Statistics Regarding Delay - All products
On the FXS port statistics second page, the values presented for delay are not
accurate and might erroneously indicate delay problems. (DRCaa20935)
Workaround:
To determine the actual delay, enable DELAY TRACE under the FXS
port options.