saisei

/Tag: saisei

Saisei STM Update 7.2 9617

  • Improvements to configuration wizard – added the setting of Ubuntu and STM passwords to the default accounts for increased security.
  • Password security improvements: config wizard forces CLI/GUI/Rest and shell passwords to be changed, to something not readily guessable.
  • Fix problems with changing system name, which could lead to the system becoming inconsistent.
  • Support history collection and analysis for all users, up to 20,000.
  • Improve built-in packet capture facility.
  • Fix some problems with traffic accounting in complex configurations, which could lead to traffic being counted twice and to limits being applied incorrectly.
  • Allow 32 bit Autonomous System numbers, previously the STM only handled 16 bit values
  • Correct the flow counts associated with policy entries
  • P2P applications were being incorrectly identified and placed in other application groups, this has been corrected.
  • FTP transfers were being incorrectly identified, the initial handshake was correct however the data transfer phase was not, this has now been corrected
  • Heavy traffic loads together with heavy REST usage triggered system reloads, this is now fixed
  • The behavior for packet forwarding when using a LAG interface has been changed, originally packets were “rebumped” and could perhaps be sent out on an interface not associated with the BITW port pair that the inbound packet was accepted on. The behavior is now changed to always send packets on the egress interface linked directly to the ingress interface.
  • Correct an error when creating user specific applications. The REST documentation allows a user to create a wildcarded application to capture all applicaations containing the wild carded string, perhaps there are several entries in the application tables containing the string “dstv.com”, the user merely needs to create a new application with the server string dstv.com to capture all such entries. This was not working correctly and has been corrected.
  • Due to a cabling error where Internal and External cables were swapped a crash was observed which was discovered to be associated with the system running out of Egress Flow Class table entries, the software was found not to return an error state and hence caused a crash. The error return has now been corrected.
  • Poor REST API performance has been observed at an installation and found to be associated with an excessive number of internal hosts being created, partially due to inbuilt processing
By |2018-06-20T20:25:22+00:002018 June 15th|Changelog|0 Comments