Cisco srw224g4 Zusätzliches Handbuch
SRW224G4/SRW248G4 Firmware Revision History
Software version 1.2.2b
Software version 1.2.2b
12/03/2007
Boot version 102
17/08/2006
Hardware version 1.1
-----------------------------------------------
Known Issues in this release
=============================
1. SetupÆ Time
The prioritization between servers is not maintained when two servers are configured
simultaneously.
2. SNMP Æ Group Profile
(a) After editing an existing group, it is not possible to select a security model for a new
group.
Recommended Workaround: Refresh the page prior to attempting to add a new group,
after editing an existing one.
3. Admin Æ Firmware Upgrade
When downloading via tftp or http, performing Power off/on to the device may result in
requirement for downloading the image via XMODEM after the device recovers. When
downloading via XModem, the device recovers by itself.
Note: Avoid disconnecting the device from a power source during image upload
4. Timestamps
(a) The order of the month and day in the dates presented in syslog messages is the
European format (dd/mm/yy), and not the US format.
(b) SNMP traps are sent with a timestamp different from the actual time on the device,
since the timestamp depends on the NMS configuration. The sequence is preserved.
5. Virtual Cable Testing of Cable Length on FE Ports
Virtual Cable Testing cannot be executed on FE ports to determine the length of the port.
6. ACL Æ MAC Based ACL
Creating a MAC ACL with to permit ethertype 0800 causes all traffic to be forwarded.
Recommended Workaround: To avoid these situations, add a rule to deny any any.
7. QoS Æ Advanced Mode
(a) When configuring a policy with police - exceeded action - out of profile dscp, the
policy must have an action: trust cos-dscp or set dscp. If you configure a policy with
police - exceeded action - out of profile dscp without an action - the device configures the
action to trust cos-dscp. If you configure a policy with police - exceeded action - out of
profile dscp with an action set cos/queue, the device configures the action to set dscp 0.
-----------------------------------------------
Known Issues in this release
=============================
1. SetupÆ Time
The prioritization between servers is not maintained when two servers are configured
simultaneously.
2. SNMP Æ Group Profile
(a) After editing an existing group, it is not possible to select a security model for a new
group.
Recommended Workaround: Refresh the page prior to attempting to add a new group,
after editing an existing one.
3. Admin Æ Firmware Upgrade
When downloading via tftp or http, performing Power off/on to the device may result in
requirement for downloading the image via XMODEM after the device recovers. When
downloading via XModem, the device recovers by itself.
Note: Avoid disconnecting the device from a power source during image upload
4. Timestamps
(a) The order of the month and day in the dates presented in syslog messages is the
European format (dd/mm/yy), and not the US format.
(b) SNMP traps are sent with a timestamp different from the actual time on the device,
since the timestamp depends on the NMS configuration. The sequence is preserved.
5. Virtual Cable Testing of Cable Length on FE Ports
Virtual Cable Testing cannot be executed on FE ports to determine the length of the port.
6. ACL Æ MAC Based ACL
Creating a MAC ACL with to permit ethertype 0800 causes all traffic to be forwarded.
Recommended Workaround: To avoid these situations, add a rule to deny any any.
7. QoS Æ Advanced Mode
(a) When configuring a policy with police - exceeded action - out of profile dscp, the
policy must have an action: trust cos-dscp or set dscp. If you configure a policy with
police - exceeded action - out of profile dscp without an action - the device configures the
action to trust cos-dscp. If you configure a policy with police - exceeded action - out of
profile dscp with an action set cos/queue, the device configures the action to set dscp 0.