Motorola 49901 Software Release Notes - Page 45

Known Software Limitations, Vanguard 340 DCE INT --> VG6560/VG320/VG64xx EXT at 1.5 Mbps

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

Known Software Limitations Part No. T0001-42, Rev C October, 2002 Page 45 of 103 Known Software Limitations Introduction Clocking Limitations Vanguard 340 This section lists limitations known to exist in Release 6.1.R000 Applications Ware software. Clocking Limitations (Port 3) (DRFaa16033, DRFaa16038) These are the clocking issues relating to Port 3 of the Vanguard 340: Vanguard 340 DCE INT --> VG6560/VG320/VG64xx EXT at 1.5 Mbps When a Vanguard 340 Port 3 is configured as internally clocked and is connected to a 6560/320/64xx which is configured as EXT clocked, and the Vanguard 340 internal clock is configured at 1.5 Mbps, the link will have clock slippage and CRC errors. Workaround: Configure the VG6560/VG320/VG64xx port "Invert TX Clock" to "YES". Vanguard 340 DCE INT --> VG6560 SDB2 EXT When a Vanguard 340 Port 3 is configured as internally clocked and is connected to a SDB2 card on a Vanguard 6560 which is configured as EXT clocked, the link will not come up. Workaround: Configure the Vanguard 6560 SDB2 port as INT clocked and the Vanguard 340 as EXT clocked. Connect the ports with a crossover cable. The DIM on the Vanguard 6560 SDB2 port should be in the DCE position. Vanguard 340 DCE EXTLP --> VG6560 SDB2 or SDB INT When a Vanguard 340 Port 3 is configured as EXTLP clocked and is connected to a SDB2 or SDB card in a Vanguard 6560, the link will not come up. Workaround: Configure the Vanguard 6560 SDB2 or SDB port as INT clocked and the Vanguard 340 as EXTLP clocked. Connect the ports with crossover cable. The DIM on the Vanguard 6560 SDB2 or SDB port should be in the DCE position. In general, configuring a DTE device as Internally clocked or a DCE device as externally clocked or EXTLP are not recommended configurations. Vanguard 7300 Default Value for the W Window Packet Parameter In release 6.1 the default value for the W Packet Window parameter for FRI AnnexG station configuration has been changed from 2 to 7. When a 6.1 release software loaded node is connected to a 6.0 release software loaded node is connected to each other via FRI AnnexG with default settings, this causes mismatch in packet layer window size and the connection does not work properly causing large delays or no data going through. (DRFaa20377) Workaround: This is a matter of mismatched configuration and setting the W Packet Window parameter to be the same in the two nodes will allow the connection to work properly.

  • 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 45 of 103
Known Software Limitations
Introduction
This section lists limitations known to exist in Release 6.1.R000 Applications Ware
software.
Clocking
Limitations
Vanguard 340
Clocking Limitations (Port 3)
(DRFaa16033, DRFaa16038)
These are the clocking issues relating to Port 3 of the Vanguard 340:
Vanguard 340 DCE INT --> VG6560/VG320/VG64xx EXT at 1.5 Mbps
When a Vanguard 340 Port 3 is configured as internally clocked and is connected to
a 6560/320/64xx which is configured as EXT clocked, and the Vanguard 340 internal
clock is configured at 1.5 Mbps, the link will have clock slippage and CRC errors.
Workaround:
Configure the VG6560/VG320/VG64xx port "Invert TX Clock" to
"YES".
Vanguard 340 DCE INT --> VG6560 SDB2 EXT
When a Vanguard 340 Port 3 is configured as internally clocked and is connected to
a SDB2 card on a Vanguard 6560 which is configured as EXT clocked, the link will
not come up.
Workaround:
Configure the Vanguard 6560 SDB2 port as INT clocked and the
Vanguard 340 as EXT clocked. Connect the ports with a crossover cable. The DIM
on the Vanguard 6560 SDB2 port should be in the DCE position.
Vanguard 340 DCE EXTLP --> VG6560 SDB2 or SDB INT
When a Vanguard 340 Port 3 is configured as EXTLP clocked and is connected to a
SDB2 or SDB card in a Vanguard 6560, the link will not come up.
Workaround:
Configure the Vanguard 6560 SDB2 or SDB port as INT clocked and
the Vanguard 340 as EXTLP clocked. Connect the ports with crossover cable. The
DIM on the Vanguard 6560 SDB2 or SDB port should be in the DCE position.
In general, configuring a DTE device as Internally clocked or a DCE device as
externally clocked or EXTLP are not recommended configurations.
Vanguard 7300 Default Value for the W Window Packet Parameter
In release 6.1 the default value for the W Packet Window parameter for FRI AnnexG
station configuration has been changed from 2 to 7. When a 6.1 release software
loaded node is connected to a 6.0 release software loaded node is connected to each
other via FRI AnnexG with default settings, this causes mismatch in packet layer
window size and the connection does not work properly causing large delays or no
data going through. (DRFaa20377)
Workaround:
This is a matter of mismatched configuration and setting the
W Packet Window parameter to be the same in the two nodes will allow the
connection to work properly.