Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Istanbul Patch 10a Hot Fix 1

Istanbul Patch 10a Hot Fix 1

The Istanbul Patch 10a Hot Fix 1 release contains fixes to the following problems.

For Istanbul Patch 10a Hot Fix 1:
Build date: 01-30-2018_1149
Build tag: glide-istanbul-09-23-2016__patch10a-hotfix1-01-29-2018

ServiceNow QPP targets and patches are immediately available. Users do not need to request an entitlement to schedule an upgrade to these versions.

For more information about how to upgrade an instance, refer to Upgrade to Istanbul.

For more information about the release cycle, see the ServiceNow Release Cycle. For a downloadable, sortable version of Istanbul fixed problems, see KB0598935.
Note: This version is approved for FedRAMP.

Fixed problem in Istanbul Patch 10a Hot Fix 1

Problem Short description Description Steps to reproduce



Unable to discover VLAN data from Cisco switches that require the SNMPv3 context When users try to discover Cisco switches, they see the message "SNMP - Switch - ForwardingTable: 0 OIDs".



Discovery probes with use_getbulk set to true disregard the SNMP v3 only discovery schedule setting, which cause unwanted queries of the target If Discovery (via schedule) runs a probe with use_getbulk set to true and the SNMPv3 credential(s) fail (including but not limited to the use case in PRB1236541), the system cycles through any community string credentials. These string credentials include 'public' unless the MID config parameter mid.snmp.enable_auto_public is disabled, since it is enabled by default. When a credential is tested, the user will see requests for 'sysDescr' made to their device(s).
  1. Configure a Discovery schedule to use SNMPv3 only.
  2. Add an IP to the schedule that will respond to SNMPv3 queries only.
  3. Add an invalid (with respect to the target device) SNMPv3 discovery credential.
  4. Add an SNMP community string credential.
  5. Add the probe parameter use_getbulk=true to the SNMP - Classify probe. You can also use a valid credential against a device where the credential will fail during exploration due to PRB1236541.
  6. Turn on debugging and/or observe SNMP traffic in Wireshark.
  7. Discover the device.

After the SNMPv3 credential fails, the system falls back to available community strings, including 'public'.

Fixes included with Istanbul Patch 10a Hot Fix 1

* Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.