Software Version sb275a05 3
Version sb275a05
C613-10464-00 Rev H
Features in sb275a05
Software maintenance version sb275a05 includes all resolved issues and
enhancements in earlier 2.7.5A versions, and the resolved issues and
enhancements in the following tables.
Level 1
No level one issues
Level 2
CR Module Level Description
CR00009347 GUI 2 It was not possible to use the GUI to add untagged ports to the default
VLAN.
This issue has been resolved.
CR00010874 IP Gateway
OSPF
2Previously, the switch discarded multicast OSPF packets that it received on
unnumbered PPP interfaces. This prevented OSPF from working across
unnumbered PPP interfaces.
This issue has been resolved.
CR00013466 Switch 2 Previously, if a JDSU XFP was used in the AT-SB4541 10G line card, the
switch rebooted when executing the command show switch port.
This issue has been resolved.
Also, the XFP LED on the 10G line card used to flash amber when many
types of XFPs were installed without a link.
This issue has also been resolved. When an XFP is installed, enabled, and
without a link, the XFP LED is now solid green.
CR00013678 GUI
File System
2It was not always possible to save the switch configuration by using the
Save button on the GUI. Sometimes the GUI reported the following error
instead of saving the configuration:
"Save failed: SYSR busy, try create config file when transfer complete"
This issue has been resolved.
CR00013823 Switch 2 In very rare circum stances, a port coul d stop transmittin g traffic if its speed
was modified or it was reset while under heavy traffic load.
This issue has been resolved.
CR00013862 IP Gateway 2 If a network loop lasted for a day or longer, the switch ran out of memory
and rebooted.
This issue has been resolved. The switch now conserves memory in these
extreme circumstances.
CR00014124 Switch 2 When the master switch controller was in slot B and a slave controller was
in slot A, the Layer 2 multicast table for AT-SB4541 10G line cards could
become incorrect. This caused loss of connectivity.
This issue has been resolved. The Layer 2 multicast table now reflects the
correct configuration when the master controller is in slot A or slot B.