Оценок - 2, средний балл: 4
(
)
)
|
Фрагмент инструкции
Workaround: There is no known workaround at this time. PR 107530 When using the Netscape browser to access the WebView > Policy > Policy > Ports page after clicking on either "Previous" or "Next" buttons and then clicking on the "Refresh" button, a "method not allowed" error is displayed. Workaround: Click on the "Ports" menu to refresh. Layer 2 Autonegotiation Problem Reports PR 86826 On an OS6800/OS9000, when autonegotiation is disabled and speed is forced to 10 Mbps, copper ports may confuse with a forced 100Mbps link partner and can detect a false link UP. Traffic may not pass in this condition. Workaround: Enable autonegotiation for this copper port and configure desired speed and duplex settings. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 53 Open Problem Reports and Feature Exceptions Bridging Problem Reports PR 86261 On an OS6800, Ethernet SNAP packets with non-zero Organizationally Unique Identifiers (OUI) will not be classified using port-protocol rule. Workaround: If applicable, other rules should be used to classify such packets. PR 94269 The OmniSwitch 9000 counts all error packets as unicast packets in the packets received and error counters, regardless of whether the packet is a unicast packet or a multicast packet. An oversized packet is defined as a packet longer than 9216 bytes. This causes the following behavior in the switch: 1) Received packets longer than 9216 bytes are counted as unicast packets AND as error packets even if the packet is a broadcast or multicast packet. 2) For ports operating at speeds of 10 Mbps or 100 Mbps, a packet is not counted as an error packet unless it is longer than 9216 bytes. Workaround: There is no known workaround at this time. PR 94866 Invalid Packets with SA or DA set to all 0's continue to get bridged by the system. Workaround: There is no known workaround at this time. PR 99331 On an OS6800, when protocol or subnet based mobility rules are deleted and created after a VLAN delete, the traffic coming in after this is not classified correctly. Workaround: Delete the rule first before deleting the VLAN. PR 99899 On an OS6800/OS6850, binding rules that require a port number to be specified as part of the rule can no longer be deleted if the port is not set to be mobile. Workaround: Make the port mobile before deleting the rule. page 54 OmniSwitch 6800/6850/9000—Release 6.1.3.R01 Open Problem Reports and Feature Exceptions Ethernet Interfaces Problem Reports PR 93114 It is not possible to broadcast or multicast oversized ingress packets. Therefore, ingressing oversized layer 2 multicast packets are treated as unicast packets. Workaround: There is no known workaround at this time. PR 94866 Invalid packets with SA or DA set to all 0s continue to be bridged by system. Workaround: There is no known workaround at this time. PR 95125 On an OS9000, the throughput on a 1 Gbps or 10 Gbps port might be 99.998%. This is due to a variance in the oscillator; the clocking can differ by a few PPM. This variance is accepted by the IEEE standard. Workaround: There is no known workaround at this time. PR 95526 On an OS9000, if the admin status of the physical interface is toggled while sending high rates of traffic on the 10G interface, some CRC errors are reported on the host connected to the interface. Workaround: There is no known workaround at this time. PR 105079 On OS6850 combo copper ports, the link will toggle once when the SFP is plugged in the corresponding fiber cage. Workaround: There is no known workaround at this time. PR 105080 If a Gig Copper SFP is plugged into a combo port on an OS6850, then those combo ports can be used in forced mode only. To use a copper combo port, then set the mode to Forced-Copper. To use the Gig copper SFP in the corresponding copper port, then set the mode of the port to Forced-Fiber. Workaround: There is no known workaround at this time. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 55 Open Problem Reports and Feature Exceptions PR 105789 The ifMauTable returns object with out of range values for 10 Gig ports on an OS9000. A get call to IETF_MAU MIB ifMauAutoNegSupported object returns a value of 0 (zero) for 10 Gig ports. Value 0 (zero) is out of range because only two values 1 (Autoneg supported) and 2 (Autoneg not supported) are part of this object. Workaround: There is no known workaround at this time. PR 105847 On OS6850-U24x board combo ports with default media preference (i.e. Preferred-Fiber) and with 100M Fiber SFP (Avago HFBR-57E0PZ), the link on fiber combo ports doesn't come up if copper cable is plugged in the corresponding copper ports and the copper link is UP. Workaround: On OS6850-U24x board combo ports, 100M Fiber SFP (Avago HFBR-57E0PZ) can get a link with fiber cable in Forced-Fiber mode only. PR 106041 On OS6850-U24x combo ports, if two OS6850-U24x boxes are connected back to back in Preferred-Fiber mode with copper cable on copper combo ports and no cable on corresponding fiber ports then if the mode ...
Эта инструкция также подходит к моделям:Сетевое оборудование - 6850 (422.93 kb)
Сетевое оборудование - 9000 (422.93 kb)