Motorola 49901 Software Release Notes - Page 52

Single DLCI Multiplexing SNA/IP/IPX Causes Node Crash - All Products

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 52 highlights

Known Software Limitations Part No. T0001-42, Rev C October, 2002 Page 52 of 103 CTP Alarms Cause CLI To Lock Up - Vanguard 6400 Series When running a CLI script, the terminal locks up if an alarm comes out while that CLI operation is in progress. (DRFaa13008) Workaround: To avoid this, do not turn alarms on when CLI scripts are being run. If this lockup occurs in a node configured with APAD, press CONTROL+P and then type clr to escape from the CTP. If this lockup occurs in a node configured with ATPAD, type +++ath to escape from the CTP. FAX Statistics in Detailed Voice Port Statistics - Vanguard 6560 These FAX statistics on the second page of the Detailed Voice Port Statistics are not supported by the Voice Server Feature Card: • FAX Transmission • FAX Transmission Unsupported Format The value for these FAX statistics remains at 0. The number of FAX pages transmitted is provided by "FAX page transmitted" and "FAX page transmission" statistics. (DRCaa21172). Workaround: At present, there is no workaround. Encryption Channel Summary Statistics - Vanguard 6400, 6560 and 340 Encryption Channel Summary Statistics can display "DATA" when the channel claims to be in a "NONDATA" state. (DRFaa15846) Workaround: At present, there is no workaround. Single DLCI Multiplexing SNA/IP/IPX Causes Node Crash - All Products RFC1490 Single DLCI Multiplexing and De-Multiplexing SNA/IP/IPX will cause the node to crash. If you configure the string FRISNA-xSy as either a source or destination in the PVC Setup Table and then boot the node, the node will not come up. The node will repeatedly crash. Multiplexing IP and IPX in the same DLCI works fine. (DRFaa16306) Workaround: At present, there is no workaround. Vanguard 340 ALC Protocol only runs on V.24 interface for Port 3 When the ALC protocol is configured on port 3 of the Vanguard 340, only the V.24 interface is available. When ALC is configured on ports 1 or 2, options for V.21, V.24, V.35, or V.36 are available. (DRFaa15863) Workaround: At present, there is no workaround for port 3. If an X.21, V.35, or V.36 interface is required, you may use ports 1 or 2. G.723 Coder Type and 6.3k Compression Calls to a Vanguard 340 Voice Card may not work properly When making voice calls from a Vanguard 6455 to a Vanguard 340 using G.723.1 coder type and 6.3K compression on the 340 and 5.3K compression on the 6455 port, it is possible to get Voice Daughtercard communication Errors:32- and a failed daughtercard state on the 340. (DRCaa22258) Workaround: At present, there is no workaround.

  • 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 52 of 103
CTP Alarms Cause CLI To Lock Up - Vanguard 6400 Series
When running a CLI script, the terminal locks up if an alarm comes out while that
CLI operation is in progress. (DRFaa13008)
Workaround:
To avoid this, do not turn alarms on when CLI scripts are being run. If
this lockup occurs in a node configured with APAD, press CONTROL+P and then
type
clr
to escape from the CTP. If this lockup occurs in a node configured with
ATPAD, type
+++ath
to escape from the CTP.
FAX Statistics in Detailed Voice Port Statistics - Vanguard 6560
These FAX statistics on the second page of the Detailed Voice Port Statistics are not
supported by the Voice Server Feature Card:
•
FAX Transmission
•
FAX Transmission Unsupported Format
The value for these FAX statistics remains at 0.
The number of FAX pages transmitted is provided by “FAX page transmitted” and
“FAX page transmission” statistics. (DRCaa21172).
Workaround:
At present, there is no workaround.
Encryption Channel Summary Statistics - Vanguard 6400, 6560 and 340
Encryption Channel Summary Statistics can display “DATA” when the channel
claims to be in a “NONDATA” state. (DRFaa15846)
Workaround:
At present, there is no workaround.
Single DLCI Multiplexing SNA/IP/IPX Causes Node Crash - All Products
RFC1490 Single DLCI Multiplexing and De-Multiplexing SNA/IP/IPX will cause
the node to crash. If you configure the string FRISNA-xSy as either a source or
destination in the PVC Setup Table and then boot the node, the node will not come
up. The node will repeatedly crash. Multiplexing IP and IPX in the same DLCI
works fine. (DRFaa16306)
Workaround:
At present, there is no workaround.
Vanguard 340 ALC Protocol only runs on V.24 interface for Port 3
When the ALC protocol is configured on port 3 of the Vanguard 340, only the V.24
interface is available. When ALC is configured on ports 1 or 2, options for V.21,
V.24, V.35, or V.36 are available. (DRFaa15863)
Workaround:
At present, there is no workaround for port 3. If an X.21, V.35, or V.36
interface is required, you may use ports 1 or 2.
G.723 Coder Type and 6.3k Compression Calls to a Vanguard 340 Voice
Card may not work properly
When making voice calls from a Vanguard 6455 to a Vanguard 340 using G.723.1
coder type and 6.3K compression on the 340 and 5.3K compression on the 6455 port,
it is possible to get Voice Daughtercard communication Errors:32- and a failed
daughtercard state on the 340. (DRCaa22258)
Workaround:
At present, there is no workaround.