Corrected Problems in Release 3.0.5 35Corrected Problemsin Release 3.0.5This section discusses problems that pertain to switch fabric modules andthat have been corrected in software Release 3.0.5.Bridging n Spanning tree bridges that are attached to a Switch 4007 via GigabitEthernet interface module ports no longer experience topologychanges during a switch fabric module failover event. (29865)n If you want addresses to age more quickly after a link down event, youcan now enable the agingOnly option from the bridgespanningTree stpState menu. This option does not enable theSpanning Tree Protocol (STP); rather, it uses one of the STP values totemporarily age addresses more quickly after link down events.Prior to Release 3.0.5, if you did not have STP enabled, a Layer 2module would not flush MAC addresses after a link down event; itwould only age addresses according to the value set in bridgeagingTime. This situation can cause VLAN-assignment problems whenendstations are frequently plugged and unplugged into ports on themodule and the Transcend Enterprise VLAN Manager (EVM)application is used on the network. That is, if a new endstation (with anew MAC address) is plugged into a port prior to the aging out of theold MAC address on that port, EVM may assign the endstation to theVLAN to which the old MAC address belonged, which could be anincorrect VLAN for the new endstation. Now, with the agingOnlyoption, this problem is resolved. For more information about theagingOnly option, see the “Release Highlights” chapter of theserelease notes. (28875, 30198, 29697)Management n You can now configure or enable SNMP trap destinations from theAdministration Console with the snmp trap addModify command onswitch fabric modules or interface modules. However, we stronglyrecommend that you enable trap destinations only via the EMEinterface. (29770)n The value of entPhysicalClass that is returned for the instance of themodule itself (entPhysicalClasss.4) now correctly returns the value 9,which represents the value for the module.