|
Xanadu
|
No updates for this release.
|
|
Yokohama
|
- **[Pattern-based direct discovery using CLI and SNMP](https://www.servicenow.com/docs/access?context=telecom-discovery-tsom-visibility&family=yokohama&ft:locale=en-US)**
Use pattern-based direct discovery to do the following tasks:
- Support deep network discovery of your physical network elements by using CLI and SNMP.
- Enable pattern-based discovery for any network elements that support SNMP standard MIBs.
- Provide a framework to enable custom Management Information Base \(MIB\)-based discovery.
- Enable both scheduled and quick discovery of standalone network elements.
- Support the following Cisco and Juniper routers and switches:
- Cisco ASR1K
- Cisco 7613
- Cisco Nexus 9000
- Cisco Nexus 3548
- Juniper Mx80
- Juniper MX104
- Juniper MX240
- Juniper MX480
- **[Nokia Altiplano SGC integration](https://www.servicenow.com/docs/access?context=service-graph-connector-for-nokia-altiplano&family=yokohama&ft:locale=en-US)**
With Nokia Altiplano SGC integration, you can:
- Support discovery of physical Gigabit Passive Optical Network \(GPON\) network information by integrating with the Nokia Altiplano Service Graph Connector.
- Enable scheduled and on-demand discovery.
- Support the multi-instance integration of the Nokia Altiplano Service Graph Connector.
- **[Discrepancy identification and reconciliation](https://www.servicenow.com/docs/access?context=telecom-reconciliation&family=yokohama&ft:locale=en-US)**
Identify the discrepancies between your inventoried and discovered data in the following cases:
- - Model mismatch.
- Model relationship mismatch.
- Entities not discovered in the current run but discovered in the previous run.
- Slots-occupied discrepancy.
- Most recent discovery not updated.
- Incorrect number of relationships.
- Support a framework to automatically create tasks for reconciling discrepancies.
|
|
Zurich
|
- **[Fault Management: Events and alerts](https://www.servicenow.com/docs/access?context=fault-management-events-and-alerts&family=zurich&ft:locale=en-US)**
You can monitor your SD-WAN network health and resolve issues faster with automated alerts and event detection.
- Detect and resolve SD-WAN network issues faster with automated alerts and event monitoring.
- Configure customizable event rules to detect SD-WAN device issues in real time.
- **[Added Service Graph Connector for Cisco Meraki and Fortinet](https://www.servicenow.com/docs/access?context=configuring-cisco-meraki-service-graph-connector&family=zurich&ft:locale=en-US)**
The following capabilities have been added to Cisco Meraki and Fortinet:
- Provides a centralized management of physical infrastructure and logical network relationships within the ServiceNow AI Platform®.
- Supports automated, telecom-aware discovery and real-time CMDB synchronization, along with visual network mapping, guided setup, and a dashboard for monitoring integration health.
- **[Granular admin roles](https://www.servicenow.com/docs/access?context=exploring-the-telco-generic-schema-etl-framework&family=zurich&ft:locale=en-US)**
The granular admin role enables developers and administrators to complete administrative configuration tasks for TSOM without requiring the full admin role.
- **[Telecom Discovery Builder framework](https://www.servicenow.com/docs/access?context=exploring-the-telco-generic-schema-etl-framework&family=zurich&ft:locale=en-US)**
Leverage a standardized Extract, Transform, Load \(ETL\) framework to streamline the processing and storage of telecom network data on the ServiceNow AI Platform.
This reusable framework simplifies implementation by removing the need to manually build ETLs. It enables you to focus on connectivity logic while confirming consistent and reliable mapping of network elements such as equipment, cards, ports, LAGs, logical ports, and logical connections into predefined CMDB structures.
Use Telecom Discovery Builder Framework to do the following:
- Simplify data transformation tasks by duplicating the common ETL and configuring essential fields and settings for specific connector applications.
- Deploy new Service Graph Connector \(SGC\) using existing ETLs to maintain consistent data transformation practices.
- Help to ensure data integrity and support the automatic creation of TNI Entities through configured Before and After scripts.
- The standardized CMDB/TNI data model enables ETL reusability across multiple connectors.
- Allocate predefined storage locations for both physical and logical inventory elements.
- Maintain consistent data model hierarchies across connectors to support unified network inventory management.
- Improve Discovery SGC quality by providing an OOTB Data Source Validation tools.
- **[Identify and reconcile discrepancies](https://www.servicenow.com/docs/access?context=exploring-telecom-reconciliation&family=zurich&ft:locale=en-US)**
Use enhanced discrepancy identification and reconciliation features to keep your discovery data accurate and up to date on the ServiceNow AI Platform. These features give you better control over detected changes and improve overall audit performance.
- Identify attribute value mismatches during discovery, such as bandwidth changes on ports \(for example, from 10 Mbps to 100 Mbps\).
- Display previous and current attribute values, enabling you to decide whether to accept the new value, retain the old one, or manually raise a remediation task.
- Detect discrepancies in logical entities alongside physical entities for comprehensive discrepancy management for newly discovered logical network elements.
- Generate audit results using filtering conditions—such as specific IP ranges, device vendors, or port types—to focus on relevant subsets of data and significantly enhance audit performance and usability.
|
|
Australia
|
- **[Granularity support for pull connectors](https://www.servicenow.com/docs/access?context=pull-connector-granularity&family=australia&ft:locale=en-US)**
Configure granularity and polling schedule constraints on Meraki and Fortinet pull connector instances to reduce API call volume and align data sampling with source system capabilities. Per-connector validation prevents unsupported values for metrics collection schedules and granularity windows. For valid values per connector and API type, see [Pull connector granularity constraints](https://www.servicenow.com/docs/access?context=pull-connector-granularity-constraints&family=australia&ft:locale=en-US).
- **[Discover VeloCloud SD-WAN inventory from both Partner \(MSP\) and Operator accounts](https://www.servicenow.com/docs/access?context=telecom-discovery-via-arista-velocloud&family=australia&ft:locale=en-US)**
The Service Graph Connector automatically detects whether the supplied credentials belong to an Enterprise Proxy \(partner\) account or a direct operator account. The same scheduled import works for either topology without configuring the discovery mode.
- **[Pagination for Meraki metrics requests](https://www.servicenow.com/docs/access?context=meraki-pull-connector-pagination&family=australia&ft:locale=en-US)**
Meraki pull connector metrics requests now follow API pagination links automatically. This verifies complete data retrieval for large organizations.
- **[Metric aggregation scripted extension](https://www.servicenow.com/docs/access?context=metric-aggregation-scripted-extension&family=australia&ft:locale=en-US)**
Define custom KPI calculations on top of raw metrics using the `TSOMMetricAggregator` scripted extension point. Formulas can combine raw and transformed metrics, apply temporal aggregation operators \(`avg`, `max`, `min`, `p95`\) and spatial aggregation across matching resources, and attach user-defined labels to calculated KPIs.
- **[Elastic connector for MPN alerts](https://www.servicenow.com/docs/access?context=set-up-connector-instance-nokia-mpn&family=australia&ft:locale=en-US)**
Collect fault management alarm data from a Mobile Private Network \(MPN\) Elastic index and forward events to Event Management by configuring a connector instance.
- **[Elastic connector for MPN metrics](https://www.servicenow.com/docs/access?context=configure-mpn-connectors-for-events-and-metrics&family=australia&ft:locale=en-US)**
The MPN connector now supports flexible metrics collection and network-level aggregation for MPN environments.
- **[MPN data model](https://www.servicenow.com/docs/access?context=mpn-data-model&family=australia&ft:locale=en-US)**
Model your MPN topology in the CMDB with new CI classes and relationships for physical hardware and virtual network functions. The expanded data model captures connectivity between physical objects \(servers, firewalls, and appliances\) and virtual network functions \(UPF, UDM, and 5G core functions\). MPN infrastructure can be represented, related, and reported on alongside your telecom service operations data.
- **[Network Packet Broker CI class](https://www.servicenow.com/docs/access?context=telecom-data-model&family=australia&ft:locale=en-US)**
Model network packet broker devices in the CMDB with the new Network Packet Broker class \(`cmdb_ci_network_packet_broker`\), a child of Telco Equipment \(`cmdb_ci_telco_equipment`\). Network packet brokers sit between network TAPs or SPAN ports and your security and monitoring tools. They aggregate, filter, and distribute traffic so each tool receives only the data it needs. Example devices include the Iris Packet Broker IPB220 and IPB420, and APCON IntellaFlex XR monitoring switches.
- **[Bind MPN metrics to configuration items automatically](https://www.servicenow.com/docs/access?context=metric-to-ci-binding-tsom-sgc&family=australia&ft:locale=en-US)**
The MPN pull connector now ships with a preconfigured event field mapping rule that binds collected metrics to CMDB configuration items automatically. The rule uses a scripted extension to resolve the CI from event fields such as name, distinguished name, serial number, and hardware ID.
- **[KPI aggregation capability](https://www.servicenow.com/docs/access?context=nokia-mpn-formula-engine&family=australia&ft:locale=en-US)**
Use the Formula Engine to process raw KPI formulas into formatted expressions. The expressions are stored in the Formatted KPI Formula field and validated for balanced parentheses before the metric calculation engine references them.
- **[Customize Fortinet license expiration date storage using scripted extension points](https://www.servicenow.com/docs/access?context=configure-fortinet-allowlist&family=australia&ft:locale=en-US)**
By default, the Fortinet SD-WAN connector stores license expiration dates as separate CI key value pairs per device. You can override this behavior and implement alternative storage logic by using a scripted extension point.
- **[Configure allowlists to scope connector polling](https://www.servicenow.com/docs/access?context=configuring-allowlist&family=australia&ft:locale=en-US)**
Limit polling to specific organizations or ADOMs through allowlists on connector instances for Cisco Meraki and Fortinet.
- **[ServiceNow product tiers](https://www.servicenow.com/docs/access?context=ai-native-sku-overview&family=australia&ft:locale=en-US)**
The ServiceNow AI Platform now brings you a new AI experience with three licensing tiers available:
- Foundation: AI basics to deliver insights
- Advanced: AI to boost productivity across relevant use cases
- Prime: Act autonomously with all AI assets, and create your own
Depending on your license, you will have access to certain application features, generative AI skills, agentic workflows, and AI agents.
|