9500 MXC User Manual
3DB 23063 ADAA - Rev 004 July 2007
Vol. IV-7-53
• Ports with a higher priority have their traffic accepted by the queue
controller ahead of traffic from lower priority ports on a 8:4:2:1
weighted basis where, for example, 8 high priority packets will be sent
for every one low priority packet. Refer to Step 10, Priority Mapping,
for more information on traffic prioritization.
5.6
Port Up
: An arrow indicates detection of valid Ethernet framing at the
local port connection. Unconnected ports or ports with invalid framing
are red-flagged. This status indicator is derived from the auto-negotiation
process.
5.7
Resolved
: A tick in a resolved box indicates that the DAC ES module
has determined the presence of valid Ethernet data from the locally
connected equipment. It also indicates that auto-negotiation has
configured the port for Duplex-Speed and/or Mdi/MdiX where auto is
selected for these options. If the port is not connected or is physically
connected but not resolved, the tick box will be empty and the associated
Port Up arrow will normally be red-flagged. Until resolved, the port is
not traffic-accepting. This auto-negotiation process only acts and reports
on data sensed from the locally connected equipment, it does not respond
to data received from the other end of the DAC ES link.
6.
Maximum Frame Size
sets the maximum frame size for the interface, which
determines the largest datagram (packet) than can be transmitted without it
being broken down into smaller units (fragmented)
3
. A setable range from 64
to 1536 bytes is indicated, but if the value selected is less than or equal to
1522, the maximum frame size is set to 1522, otherwise it is set to 1536. For
a typical 1500 byte packet the frame size for an untagged frame is 1518 bytes.
If the frame is VLAN tagged the frame size increases by four bytes to 1522.
The default setting is 1522 bytes.
7.
Enable Flow Control
: Flow control is applicable to full-duplex links only. It
is implemented by the IEEE 802.3x pause frame mechanism, which tells the
remote node to stop or restart transmission to ensure that the amount of data
in the receive buffer does not exceed a ‘high water mark’.
• The receiver signals to the transmitter to stop transmitting until sufficient
data has been read from the buffer, triggered by a ‘low water mark’, at which
point the receiver signals to the transmitter to resume transmission.
• To be effective, flow control must be established from the originating source
through to the end point, and vice versa, which means the equipment
connected to the DAC ES / IDU ES ports and beyond must also be enabled
for flow control.
8.
Address Learning
: Address Learning is default implemented to support
efficient management of Ethernet traffic in multi-host situations. The option
3
The setting only supports this interface. Some other link/interface in the path may have a smaller MTU,
at which point the datagram will be fragmented if its size is greater.
Содержание 9500 MXC
Страница 5: ......
Страница 6: ......
Страница 28: ......
Страница 29: ...Volume I 9500 MXC Health and Safety Requirements...
Страница 30: ......
Страница 39: ...Volume II 9500 MXC System Description...
Страница 40: ......
Страница 56: ...Chapter 1 9500 MXC System Overview Vol II 1 16 Alcatel Lucent...
Страница 94: ...Chapter 2 9500 MXC Terminals Vol II 2 38 Alcatel Lucent...
Страница 218: ...Chapter 4 Outdoor Units Vol II 4 4 Alcatel Lucent...
Страница 236: ...Chapter 6 9500 MXC Performance and Diagnostic Features Vol II 6 14 Alcatel Lucent...
Страница 237: ...Volume III 9500 MXC Installation...
Страница 238: ......
Страница 268: ...Chapter 2 Outdoor Installations Vol III 2 26 Alcatel Lucent Figure 2 16 BGXZ Surge Suppressor...
Страница 282: ...Chapter 2 Outdoor Installations Vol III 2 40 Alcatel Lucent...
Страница 300: ...Chapter 4 Installing the IDU Vol III 4 6 Alcatel Lucent...
Страница 321: ...Volume IV 9500 MXC CT...
Страница 322: ......
Страница 326: ...Chapter 1 9500 MXC CT Introduction Vol IV 1 4 Alcatel Lucent Figure 1 3 Standardized 9500 MXC Logos...
Страница 332: ...Chapter 1 9500 MXC CT Introduction Vol IV 1 10 Alcatel Lucent...
Страница 362: ...Chapter 2 Setting Up 9500 MXC CT Vol IV 2 30 Alcatel Lucent...
Страница 368: ...Chapter 3 Installation and Configuration Process Vol IV 3 6 Alcatel Lucent Figure 3 1 9500 MXC CT Menu Bar Menus...
Страница 374: ...Chapter 3 Installation and Configuration Process Vol IV 3 12 Alcatel Lucent...
Страница 384: ...Chapter 4 Licensing Vol IV 4 10 Alcatel Lucent...
Страница 388: ......
Страница 390: ......
Страница 508: ...Chapter 8 Protection Vol IV 8 26 Alcatel Lucent...
Страница 542: ...Chapter 10 Networking Configuration Vol IV 10 18 Alcatel Lucent...
Страница 546: ......
Страница 550: ...Chapter 12 Date and Time Configuration Vol IV 12 4 Alcatel Lucent...
Страница 558: ...Chapter 13 Software Management Vol IV 13 8 Alcatel Lucent...
Страница 561: ...9500 MXC User Manual 3DB 23063 ADAA Rev 004 July 2007 Vol IV 14 3 Figure 14 2 Login Screen for Admin...
Страница 562: ......
Страница 632: ...Chapter 15 Diagnostics Vol IV 15 70 Alcatel Lucent Figure 15 27 Example Parts Screen...
Страница 636: ...Chapter 15 Diagnostics Vol IV 15 74 Alcatel Lucent...
Страница 637: ...Volume V Commissioning and Troubleshooting...
Страница 638: ......
Страница 688: ...Chapter 2 9500 MXC Troubleshooting Vol V 2 32 Alcatel Lucent Terminal FAN Alarm Hierarchy FAN Hardware Fan Failure FAN...
Страница 699: ...Volume VI Appendices...
Страница 700: ......
Страница 706: ...Vol VI A 6 Alcatel Lucent Figure A 2 Excerpt from a Circuit Allocation Sheet for the Example Ring in Figure A 1...
Страница 791: ...9500 MXC User Manual 3DB 23063 ADAA Rev 004 July 2007 Vol VI B 65...
Страница 792: ......
Страница 826: ......
Страница 836: ...Vol VI D 10 Alcatel Lucent Figure D 3 Static Routing Screen for Node B in Figure D 2 3 192 168 2 1 Lyons Dpt...
Страница 846: ...Vol VI D 20 Alcatel Lucent...
Страница 856: ...Vol VI E 10 Alcatel Lucent...
Страница 873: ...9500 MXC User Manual 3DB 23063 ADAA Rev 004 July 2007 Vol VI F 17...
Страница 874: ......