SilverCreek Change Logs

What’s New (SilverCreek Version History)

Release 2024.241228 (Date: 2024-12-28)

  • SilverCreek failed to launch on newer Linux distributions such as Ubuntu 24.04. The MIB loading got stuck in an infinite progress loop.
  • On Fedora 41, the SilverCreek installer GUI couldn’t be launched to complete the installation due to missing dependent libraries.
  • Decoding a Counter64 value may result in an unexpected byte, ‘5C’, being added before converting the hex sequence to a multi-precision integer value. As a result, incorrect integer values are displayed in the MIB browser and various SNMP command outputs.
  • Test 17.1.3 could report a false failure because the tcpConnectionTable is a dynamic table, and the comparison may differ at the time the test runs.
  • Tests 1.1.2.2, 2.1.2.3, and 3.1.2.3 could report unnecessary inconsistent MIB walking result warnings.
  • Updated SilverCreek counter tests using Scapy to support both Python 2.7 and Python 3.
  • When receiving SNMPv3 authenticated traps, if engine time synchronization has not been done via separate SNMP requests, SilverCreek now uses the engine time and boots from the first trap received as the baseline.
  • Updated the command snmptcl::listen{} to snmptcl::listen {timeToWaitInSeconds 0}. The default behavior is now to wait indefinitely for incoming traps.
  • When selecting SNMP over DTLS, if the agent handshaking fails, SilverCreek unexpectedly switches to normal SNMPv3 mode in the New-Agent Setup dialog, causing subsequent connection attempts to always fail.
  • Miscellaneous bug fixes and improvements

Release 2023.230528 (Date: 2023-05-28)

  • Added SNMP over DTLS Support (RFC 6353) SilverCeek now supports RFC6353, SNMPv3 over Datagram Transport Layer Security (DTLS) Transport Model.
  • When clicking on the test entry to view the result of test2.1.2.3 and test 3.1.2.3 on SilverCreek GUI may get frozen.
  • Changed test3.3.1.5 to issue an “untested” result if the counter snmpUnknownContexts and others are customized as not-implemented.
  • Test3.1.4.4 may issue a “NORESULT” grade if no error was detected during testing.
  • Test11.1.13 an empty hrSWRunPath string and 0 byte hrSWRunPerfMem should be allowed. It  may generate an error “expr signals a bareword error”
  • Automatically recalculating readwrite and readonly variables used in protocol tests by invoking readyReadWriteVars and readyReadOnlyVars so that customers don’t need to rerun MIB walking test1.1.2, 2.1.2.1, and 3.1.2.1 after customizing MIB definitions and changing the ignore writable objects definitions in Test Fine-tuning configuration.
  • “Test | Fine-Tune Testing Options” now includes an option selecting all other writable objects except the one specified. In CLI the variable snmptest (ignoreobjects_all_except) can be set to 1.
  • SNMP Notification Monitor Enhancement: added a new configuration field “SNMPv3 agent port” so the SNMP engine time synchronizing requests can be sent to a custom port.
  • SilverCreek BSCM2 (v1v2c only) edition was generating an error when switching to SNMPv3 Diffie-hellman page. The trap monitor is also generating errors about various SNMPv3 buttons due to disabled SNMPv3.
  • Miscellaneous bug fixes and improvements
Scroll to Top