DX NetOps

Expand all | Collapse all

Tech Tip: Spectrum 9.3.0 release - fixes and enhancements

Jump to Best Answer
  • 1.  Tech Tip: Spectrum 9.3.0 release - fixes and enhancements

    Broadcom Employee
    Posted 12-09-2013 12:53 PM
    Tech Tip: Spectrum 9.3.0 release - fixes and enhancements
    CA Spectrum Tech Tip by Bill Wolforth, Senior Support Engineer for December 9, 2013
    Description:
    This knowledge document only lists the fixes and enhancements to pre-existing functionality that the Spectrum 9.3.0 release delivers. The full and final Software Release Notice (SRN) contains requirements, special considerations and installation instructions. Please read the full SRN which is part of the 9.3.0 documentation bookshelves.
    Solution:
    DETAILS OF 9.3.0 CONTENTS
    Fixes to Alarm Management
    Symptom: The Service model alarm title filter will not work if it is configured against the Resource Monitor.
    Resolution: The Service model alarm title filter will work fine if it is configured against the Resource Monitor.
    (9.3.0, 101811, 20971931-1)
    Symptom: Spectrum may generate an alarm on a port interface of type Atmvclnk having the "GeneratePortStatusAlarms" attribute set to "No".
    Resolution: Spectrum does not generate an alarm on a port interface of type Atmvclnk having the "GeneratePortStatusAlarms" attribute set to "No".
    (9.3.0, 120082, 21116550-1)
    Symptom: When the devices are unreachable, at times "Infinite Loop has been detected in the MIB" alarms are generated, which is misleading.
    Resolution: When the devices are unreachable the SpectroSERVER will not create "Infinite Loop has been detected in the MIB" alarms.
    (9.3.0, 189954, 21207705-1)
    Symptom: The SpectroSERVER doesn't clear the MAL alarms raised on Secondary when primary fails-back.
    Resolution: The SpectroSERVER now clears the MAL alarms raised on Secondary when primary fails-back.
    (9.3.0, 88906, 20890348-1)
    Symptom: ArchMgr crashing on startup due to stack buffer overflow.
    Resolution: Resolved issue causing stack overflow when model names exceed 1024 characters.
    (9.3.0, 221339, 21457513-1)
    Fixes to Alarm Notifier and SANM
    Symptom: AlarmNotifier crashes due to a Probable Cause passed as command line argument and very big environment variable string (>37767). Missing Clear Alarm Notification when AlarmNotifier has network connection problems with SpectroSERVERs. No dump file generated when there is an exception hit by AlarmNotifier exe on windows.
    Resolution: Alarm Notifier does not crash due to the memory being overrun due to command line parameter going beyond the defined limit. The environment variable size has been truncated to the OS limits size. Clear notifications will be regenerated which were missed because of disconnection after reconnection to SS. Added the Dump of AlarmNotifier process on exception in windows.
    (9.3.0, 201565)
    Fixes to AutoDiscovery
    Symptom: NRM_RunningFirmware attribute never work for HP Procurve J9079A devices.
    Resolution: NRM_RunningFirmware attribute now works for HP Procurve J9079A devices.
    (9.3.0, 197793, 21329989-1)
    Fixes to CA EEM
    Symptom: When Spectrum is integrated with SiteMinder and deployed as part of CA solution , the SMSESSSION that is passed by CA Spectrum has the value enclosed in double quotations, due to this the other CA products involved in the CA Solution is unable to validate the SMSESSION passed by Spectrum.
    Resolution: Added <remove-quotes-enabled> tag in the sso-system-config.xml file and the default value is set to false. The user has to set <remove-quotes-enabled> tag to true to remove the double quotes from SMSESSION.
    (9.3.0, 188979, 21235952-02)
    Fixes to CA Performance Center (NPC)
    Symptom: A Spectrum DSS is added as a data source of CA Performance Center that also has a Data Aggregator added as a data source. If Performance Center event polling has been enabled on the OneClick server CA Performance Center event display is slow.No new events from CA Performance Center are being seen in Spectrum.The CPU utilization of the CA Performance Center mysqld process is high.CA Performance Center event manager logs show that events are being lost because the queue is full.The results of the 'show full processlist' in MySQL on the CA Performance Center server shows many queries similar to the following:SELECT STRAIGHT_JOIN DISTINCT e.NPCEventID, ds.ConsoleName Source, et.TypeName Type, et.SubTypeName SubType, e.Category Category, e.OccurredOn, e.State, e.Description, i.ItemName, ei2.NPCItemID, i.ItemTypeName, IFNULL(i.ItemSubTypeName,'') AS ItemSubTypeName FROM events e FORCE INDEX (PRIMARY, Events_OccurredOn, Events_ReceivedOn) INNER JOIN event_items ei ON e.NPCEventID = ei.NPCEventID INNER JOIN item_members im on (im.ChildID = ei.NPCItemID) INNER JOIN group_scope gs on (im.ParentID=gs.DescendantID) INNER JOIN event_items ei2 ON e.NPCEventID = ei2.NPCEventID AND ei2.ItemIndex=0 INNER JOIN data_sources ds ON e.ProducerID = ds.SourceID INNER JOIN event_types et ON et.TypeID=e.SubTypeID INNER JOIN items i ON i.ItemID=ei2.NPCItemID WHERE gs.AncestorID=121219 AND e.ReceivedOn >= 1359078962 AND e.ReceivedOn < 1361179022 AND (e.TypeID IN ('6')) ORDER BY OccurredOn ASC;.
    Resolution: Spectrum now requests events for each landscape sequentially to avoid locking out new events.
    (9.3.0, 180419, 21289606)
    Symptom: .
    Resolution: .
    (9.3.0, 220063, 21481100-1)
    Symptom: Spectrum's launch back URL for Performance view always uses Performance Center' s "Device" view even if Spectrum's model under context is of type "Sever" or "Workstation-Server".
    Resolution: Spectrum's launch back URL for Performance view will launch "Server" view of Performance Center if Spectrum's model under context is of type "Server" or "Workstation-Server".
    (9.3.0, 92643, 20953977-1)
    Fixes to CA Service Operations Insight (SSA or SOI)
    Symptom: The Spectrum Catalyst (SOI) connector can expose a memory-related defect in the SpectroSERVER causing one of the two following symptoms: 1. If using the MTS version of the SpectroSERVER executable (default as of 9.2.2), , error messages like the one below is produced: ? mts free: (mts_page_gap::Vfree_memory) heap 1 out of bound address 0x1 on page nil (out of bound) 2. If using the non-MTS version of the SpectroSERVER executable, the SpectroSERVER process will crash.
    Resolution: ixed the memory-related coding flaw, preventing the problem from occurring.
    (9.3.0, 185136, 21315070-1)
    Symptom: SpectroSERVER crashes while reading the USMPrimaryIPV6 attribute when the device is unreachable or in maintenance.
    Resolution: Fixed SpectroSERVER to not crash while reading the attribute when the device is unreachable or in maintenance.
    (9.3.0, 193214)
    Fixes to CA eHealth Integration
    Symptom: "STALE EHEALTH SERVER IN EHEALTH CLUSTER" alarms are generated in eHealth even when there is no problem with the eHealth and spectrum integration.
    Resolution: The messages are now being sent to the stdout.log.
    (9.3.0, 190743, 21251019-1)
    Fixes to Certifications
    Symptom: The client has to generate some Reports and the information for HP Procurve devices is not generated correctly.
    Resolution: The NRM_RunningFirmware attribute now works for HP Procurve devices.
    (9.3.0, 180508, 21248880-1)
    Symptom: There is no graph displayed in the Performance tab if one of the performance attributes of the chart has invalid values, even for other performance attributes in that chart which have valid values.
    Resolution: Fixed Performance tab charts to show the graph for performance attributes which have valid values.
    (9.3.0, 189969, 21137217-1)
    Fixes to Condition Correlation
    Symptom: Interface condition remains critical and bad link alarm is not cleared when model is coming out from maintenance mode.
    Resolution: Interface condition is proper and bad link alarm is cleared, when model is coming out from maintenance mode.
    (9.3.0, 107946, 21057781-01)
    Fixes to Device Certification Manager
    Symptom: The devices listed in the Device Certification utility don't contain all of the unregistered models across all of the landscapes in a DSS.
    Resolution: The devices listed in the Device Certification utility will now correctly display all of the unregistered models across all of the landscapes in a DSS.
    (9.3.0, 211478)
    Fixes to Event Configuration (EC)
    Symptom: Sometimes the Details Pane of the EC Configure Conditional Alarm Severity Console shows incorrect severity mappings.
    Resolution: The details pane of the EC Configure Conditional Alarm Severity Console now shows correct severity mappings.
    (9.3.0, 178897, 21262336-1)
    Symptom: Delete button in the Navigation Panel of Event Configuration editor is disabled for customized events having Event Procedure.
    Resolution: Delete button in the Navigation Panel of Event Configuration editor is enabled for customized events having Event Procedure.
    (9.3.0, 193285, 21325978-1)
    Fixes to Event Management System
    Symptom: An EvFormat file does not exist for the DDM Table Error event (0x00010c1c).
    Resolution: An EvFormat file for the DDM Table Error event (0x00010c1c) is added.
    (9.3.0, 106695, 21059337-1)
    Symptom: When editing the event condition rule from the Event Configuration editor, commas are removed from event variable copy portion of event condition rule.
    Resolution: When editing the event condition rule from the Event Configuration editor, commas are retained and rule is saved properly.
    (9.3.0, 168691, 21149117-2)
    Symptom: When trying to map the web context url alarm attribute (0x12a63) directly in an alert map, the following alarm is generated:Internal error occurred: Incorrect alarm attribute type found when trying to copy alarm data to an alarm management alarm update event. The change event was generated but might not contain all the necessary information.
    Resolution: When assigning the web context url attribute the type is checked, and converted to text string when necessary.
    (9.3.0, 180670, 21300736-1)
    Symptom: SpectroSERVER crashes are behaves weirdly after processing an event which was specified multiple times in an event rule.
    Resolution: Event rule state machine code was changed to avoid problems when events are processed multiple times, one leading to a stop state. The SpectroSERVER will process such rules fine now.
    (9.3.0, 193293, 21325066-1)
    Fixes to Events and Alarms
    Symptom: Varying alarm counts on each OneClick client.
    Resolution: Landscape attribute added to the default set of required alarm attributes.
    (9.3.0, 204713, 21301021-1)
    Fixes to Global Collections
    Symptom: When an empty Global Collection is added to a Global Collection Hierarchy Folder, the List view of the empty Global Collection begins to show all the Global Collections defined.
    Resolution: When an empty Global Collection is added to a Global Collection Hierarchy Folder, the List view of the empty Global Collection will be empty.
    (9.3.0, 195780, 21158079-1)
    Symptom: When migrated Spectrum from Saratoga to Meadowlands, installation/migration was successful, but certain global collections has empty topology view on OneClick client, even though the GC has some models in it. But, the same GC lists all models that match the criteria in 'List' tab.Enabled Global Collections logs and observed exceptions when ever user click on 'Topology' tab, for certain global collections.
    Resolution: After applying this fix all Global Collections will show the Topology view properly as expected.
    (9.3.0, 210460)
    Fixes to Integrations
    Symptom: Spectrum's CORBA SDK is case-sensitive when specifying landscape names.
    Resolution: Spectrum's CORBA SDK is no longer case-sensitive with regards to landscapes names.
    (9.3.0, 204437, 21372077-1)
    Fixes to Juniper
    Symptom: Reconfiguring the Netscreen devices can cause wrong interface naming and status due to multiple interfaces with same interface number and interface type.
    Resolution: Reconfiguring the Netscreen devices will show appropriate interface name and status.
    (9.3.0, 183179, 21138959-02)
    Fixes to Modeling
    Symptom: The SpectroSERVER may not delete a stale interface during the interface reconfiguration even if the attribute HasStaleInterfaces is set to FALSE.
    Resolution: The SpectroSERVER deletes a stale interface during the interface reconfiguration even if the attribute HasStaleInterfaces is set to FALSE.
    (9.3.0, 124186, 21098416-1)
    Symptom: Uncertified models are being incorrectly identified as having a non-standard discovery and are therefore showing up Support Level as "Enhanced" and Author as "CA" in Device Certification Manager.So customer is unable to edit the Model Class entry in Device Certification Manager.
    Resolution: For uncertified models, it shows the correct Support Level as "Simple" and Author as "Unregistered" in Device Certification Manager. Now customer can be able to edit the Model Class in Device Certification Manager.
    (9.3.0, 186969, 21124408-1)
    Symptom: Vendor Name is displayed as "Unknown" because some MAC address and Vendor name mappings were missing in the SpectroSERVER database.
    Resolution: Added remaining MAC addresses and respective vendor names in the SpectroSERVER database.
    (9.3.0, 189998)
    Symptom: It is possible for a duplicate SNMP-enabled model to be created for a virtual machine when using the VHM option to "Upgrade ICMP-Only Devices".
    Resolution: Duplicate SNMP-enabled models will no longer be created by the VHM option to "Upgrade ICMP-Only Devices".
    (9.3.0, 191499, 21248259-1)
    Symptom: Extraction of the IP from the OID of ipNetToMediaPhysAddress was not proper.
    Resolution: Modified the extraction part of the IP from the OID of ipNetToMediaPhysAddress.
    (9.3.0, 200447, 21298070-1)
    Symptom: If VFI name contains any upper case characters, VFI models stay in initial state and Site models are not discovered after VPLS discovery.
    Resolution: VFI models and Site models are discovered properly and state of VFI models is normal.
    (9.3.0, 201205, 21219620-1)
    Fixes to Modeling Gateway
    Symptom: While importing through modeling gateway if any improper connection exists for a device then import process aborts, and will not import the rest of the connections.
    Resolution: While importing through modeling gateway if any improper connection exists for a device then it logs the details and will continue to import the rest of the connections.
    (9.3.0, 189893, 21130851-1)
    Symptom: Modeling gateway import process will fail if root node (<adisc_root_container>) is followed by a space or new line (XML text node).
    Resolution: Modeling gateway import will be successful even when root node (<adisc_root_container>) is followed by a space or new line (XML text node).
    (9.3.0, 189899, 21238625-1)
    Fixes to Network Configuration Management
    Symptom: Cisco devices with IOS version format XX.X(X.XX) are not getting added under the correct device family in Network Configuration Manager (NCM).
    Resolution: Cisco devices with IOS version format XX.X(X.XX) will get added under the correct device family in Network Configuration Manager (NCM).
    (9.3.0, 120367, 20993522-1)
    Symptom: NCM scripts run as root if the SpectroSERVER is running as a user configured for sradmin sudo access.
    Resolution: sradmin sudo configuration is now exclusively used only by the install process.
    (9.3.0, 127460, 21122567-1)
    Symptom: The View Violation button in Repair Devices part of Violation window for the NCM Devices does not show any error message in case if the violation is cleared.
    Resolution: Appropriate error message is displayed in case the violation is already cleared upon clicking View Violation button in Repair Devices section of Violation window for NCM Devices.
    (9.3.0, 189892, 20887551-1)
    Symptom: NCM Telnet/ FTP capture fails when the user goes to device privilege mode directly after the login.
    Resolution: NCM capture is successful with all modes.
    (9.3.0, 189895, 21299125-1)
    Fixes to Normalized Resources
    Symptom: Incorrect 'CONFLICTING RULESETS DETECTED' (PCause 0x23900020) alarms are generated, when no overlapping disks are seen in the currently attached rulesets.
    Resolution: The problem stems from restarting a server without loading a good saved database first, so that invalid ruleset data from previously attached GC/rulesets may be left over in the host resource application model attached to the device.Two cleanup actions have been provided to resolve the problem. Inquire with Spectrum support for details on how to invoke these actions, please.
    (9.3.0, 180119, 20910092-1)
    Symptom: The agent version seen in the general information view of the information tab for the nsm system agent model is blank.
    Resolution: Nsm system agent version is now seen under System Resources->System sub view.
    (9.3.0, 54373, 20749788-1)
    Fixes to OneClick
    Symptom: When saving SSL certificate file without a file from Administration page, proper error message is being displayed, but twice. Instead it should display only once.
    Resolution: In ssl-cert.jsp file the error message was printing twice. Removing one print statement should address this issue.
    (9.3.0, 150267)
    Symptom: Due to "new line feed" character, the value of couple of OIDs were not displayed properly in EntityView.
    Resolution: If the values of OIDs are not in readable format, converting them to readable string so that it will be displayed properly in the Entity view.
    (9.3.0, 177532, 21198114-1)
    Symptom: Mib tools could fail to launch due to deadlock.
    Resolution: Used a different data structure, designed for concurrency, to prevent the deadlock.
    (9.3.0, 182478, 21147404-1)
    Symptom: The alarm count values for VNM and Landscape models display negative values in OneClick.
    Resolution: The alarm count values for VNM and Landscape models display appropriate values in OneClick.
    (9.3.0, 183180, 21054564-1)
    Symptom: Email Configuration in OneClick Administration page does not allow entering of domain names starting with numbers.
    Resolution: Email Configuration page now allows entering of domain names starting with numbers.
    (9.3.0, 183300, 21306329-1)
    Symptom: Catalina log file is being filled up with thread dumps containing a warning message that reports "The event update queue size has reached 100".
    Resolution: Default warning queue size limit is enhanced to a higher value to handle more realistic scenarios.
    (9.3.0, 189897, 21100473-1)
    Symptom: Customer wants to assign troubleshooter to alarms and sent the message with additional information to him. But the problem is that the mail message cannot be edited - the part of the window looses focus every time when clicking in it.
    Resolution: After applying this fix the user should be able to Edit AlarmEmail as expected.Actually the AllowMessageEdit parameter of the AlarmEmailDialog class was disabled, enabled it to make it editable.
    (9.3.0, 197264, 21319247-1)
    Symptom: ConcurrentModificationException has been observed in logs.
    Resolution: ArrayList is being replaced by CopyOnWriteArrayList to make it safe in multi-threaded environment.
    (9.3.0, 200174, 21273330-6)
    Symptom: When using a load balancer and looking at the Client Log,the user logged in message notes the IP of the logged in client is from theload balancer, and not from the client itself. Since the load balancer isacutally making the request, the log shows the load balancer IP. This needs to show the actual IP of the client that makes the request.
    Resolution: 1. Load balancers should be configured by enabling to use "X-Forwarded-For" Http header field. 2. From Spectrum side fix has been provided which should be applied on Webserver.Once these above two steps are followed then this issue will be resolved.
    (9.3.0, 201654, 21248335-1)
    Symptom: RestFul request for models can create several instances of CursorExpirationThread until OuOfMemoryError.
    Resolution: A single instance of CursorExpirationThread is created and exists for the life of the tomcat process.
    (9.3.0, 204909, 21274466-1)
    Symptom: Tomcat could hang at startup if domains cannot be reached.
    Resolution: Tomcat contacts domains by direct connection only.
    (9.3.0, 204910, 20976687-1)
    Symptom: Requesting all alarm using the REST API can hurt tomcat performance including exhausting memory.
    Resolution: The request is throttled by limiting the number of concurrent domains.
    (9.3.0, 204911, 21311962-1)
    Symptom: High tomcat CPU from either high rate of alarms or alarms from RESTFul web services.
    Resolution: Disabled default debugging that has the potential to obtain locks on the alarm table. Created a thread pool to throttle RESTFul web service requests.
    (9.3.0, 204912, 21334129-1)
    Fixes to Performance Manager (SPM)
    Symptom: Test Name of a test created on Spectrum is changed while doing discover Tests for the test host when the value of "Use Tag Field as Test Name for CiscoTest Host Discovery" attribute is yes.
    Resolution: Test Name of a test created on Spectrum will not be changed while doing discover Tests for the test host even if the value of "Use Tag Field as Test Name for CiscoTest Host Discovery" attribute is yes.
    (9.3.0, 200463, 21311267-1)
    Symptom: Latency Threshold values are getting disabled when the device is reachable after getting disconnected.
    Resolution: If device is connected again after getting disconnected, Latency Threshold values will be present if they are not disabled before getting disconnected.
    (9.3.0, 201223, 21347652-1)
    Symptom: After a SpectroSERVER restart some traceroute tests are being duplicated.
    Resolution: Spectrum will update TesterMH attribute for the VPN Model and this will prevent the duplication of the traceroute tests.
    (9.3.0, 37768, 20527079-1)
    (9.3.0, 122855, 21101315-1)
    Fixes to QoS Manager
    Symptom: QOS Manager displays wrong traffic policing associations when same traffic class name is associated with different QOS policies.
    Resolution: Traffic classes are renamed to make them unique so they can be displayed correctly and be associated with correct traffic policing models.
    (9.3.0, 190324, 21062343-1)
    Fixes to Multicast Manager
    Symptom: Multicast discovery can cause excessive SpectroSERVER CPU utilization.
    Resolution: Improved the Multicast discovery algorithm so that it no longer uses excessive SpectroSERVER CPU resources.
    (9.3.0, 190200)
    Symptom: The SpectroSERVER may crash when performing a Multicast discovery.
    Resolution: Resolved a memory issue that could cause the SpectroSERVER to crash while running a Multicast discovery.
    (9.3.0, 202820)
    Fixes to Report Manager
    Symptom: If the trouble ticket ID does not contain service desk URLs, errors are thrown during alarm bucket processing. Also, sub reports will not be generated for some alarm reports where the trouble ticket id is displayed.
    Resolution: Alarm buckets will get processed. Sub reports of alarm reports where trouble ticket id is displayed will be generated.
    (9.3.0, 120621, 21107688-1)
    (9.3.0, 123703, 21117406-1)
    Symptom: Reports generated that are exported to PDF are not rendered correctly. The text in the PDF version of the report is unreadable.
    Resolution: All the reports exported to PDF are now readable.
    (9.3.0, 128688, 21141008-1)
    (9.3.0, 87849)
    Symptom: Report Manager stops event processing when a duplicate username is detected.
    Resolution: The Security handler will handle when a deleted OneClick username is recreated, therefore eliminating the issue.
    (9.3.0, 129192, 21104285-1)
    Symptom: "Alarm Count Trend: All" report displays the graphs with truncated values on vertical axis.
    Resolution: "Alarm Count Trend: All" report will display the graphs without truncating the values on vertical axis.
    (9.3.0, 131463, 21151914-1)
    Symptom: Exporting the reports to .CSV format shows repeated data.
    Resolution: Exporting the reports to .CSV format will show unique data.
    (9.3.0, 146439)
    Symptom: The text for some labels is garbled when exporting the availability reports to PDF format on some locale.
    Resolution: The text will be visible clearly for all the availability reports exported to PDF format on all the supported locales.
    (9.3.0, 153651)
    Symptom: Text in the header is missing when exporting the Alarm log reports to .CSV/.XLS (Data Only) format.
    Resolution: Exporting the Alarm log reports to .CSV/.XLS(Data Only) format will show the complete data in the header.
    (9.3.0, 154513, 21196861-1)
    Symptom: The Sub reports for Projected Monthly Availability : Group and Projected Monthly Availability: Selected Models shows incomplete data when the availability is 100%.
    Resolution: The Sub reports for Projected Monthly Availability : Group and Projected Monthly Availability: Selected Models will show complete data.
    (9.3.0, 161733)
    Symptom: Devices appears with negative outages in the availability reports when the time period chosen for reporting is before the creation of the device.
    Resolution: Device will not be shown in the report if the creation time of the device is after the reporting period.
    (9.3.0, 168258, 21250966-1)
    (9.3.0, 142858)
    Symptom: SRM NCM Handler is getting stopped with a MYSQL exception "data too long", because of "violate_policies and complaint_ policies" column of "ncm_config" table can hold only255 characters.
    Resolution: SRM NCM Handler can handle up to 3000 characters against "violate_ policies and complaint_ policies" of "ncm_config" table.
    (9.3.0, 175943, 21267395-1)
    Symptom: Report Manager Availability Group reporava.lang.String".
    Resolution: When the action 0x10474 is sent from CLI we get the response in the String type format. Currently only OctetString and Counter as response are handled. Added support to handle when the response is of String type.
    (9.3.0, 157973, 21226213-1)
    Symptom: Alarm subscription through Spectrum Restful Web Services is not sending the updates when an alarm attribute (e.g. "Trouble TicketID" or "Assignment") is changed for an existing alarm.
    Resolution: Alarm subscription through Spectrum Restful Web Services will send the updates when an alarm attribute (e.g. "Trouble TicketID" or "Assignment") is changed for an existing alarm.
    (9.3.0, 183205, 21209377-1)


  • 2.  RE: Tech Tip: Spectrum 9.3.0 release - fixes and enhancements

    Broadcom Employee
    Posted 12-12-2013 04:55 AM

    Thanks for this very informative and detailled Tips.
    Regards,
    Ollivier
     



  • 3.  RE: Tech Tip: Spectrum 9.3.0 release - fixes and enhancements
    Best Answer

    Broadcom Employee
    Posted 12-16-2013 11:43 AM

    Updating Status