Cisco Data Fabric Setup
Prerequisites
| Tool or access |
Purpose |
Verify |
| Bash and Python 3 |
Run bundled setup and validation helpers |
bash --version && python3 --version |
| Required product/platform access |
Inspect or configure the selected target |
Complete the documented preflight |
| Credential files for live modes |
Keep secrets out of chat |
Verify paths only |
Workflow Overview
┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘
When to Activate
- Users need Cisco Data Fabric architecture, feature or product coverage, readiness assessments, gap analysis,
machine-data activation, federation targets, storage tiering, AI-ready data, or AgenticOps data foundation
requests. Distinguish.
- Preview and review the cisco data fabric setup workflow before any live apply phase.
- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.
Scope
Follow the documented read-only or render-first path whenever it is available.
This skill does not imply permission to mutate live systems. Require explicit
apply flags, protected credentials, and operator review for state changes.
Examples
Inspect the supported setup modes before selecting one:
bash skills/cisco-data-fabric-setup/scripts/setup.sh --help
Expected output: usage, supported modes, and required arguments are displayed
without changing the target environment.
Inspect validation modes before running completion checks:
bash skills/cisco-data-fabric-setup/scripts/validate.sh --help
Expected output: offline, live, and completion options are displayed when the
skill supports them; help exits without mutation.
Troubleshooting
| Issue |
Cause |
Resolution |
| Preflight fails |
A required tool or access path is missing |
Resolve it before rendering or applying |
| Rendered assets are incomplete |
Required non-secret inputs are absent |
Complete intake and render again |
| Apply is blocked |
Review, credentials, or explicit acceptance is missing |
Use the documented handoff |
| Validation is incomplete |
Live evidence is unavailable |
Record the gap and keep completion open |
Treat Cisco Data Fabric as the architecture powered by the Splunk Platform,
not as a single installer, SKU, API, or storage product. Render a complete
coverage packet first, then execute only reviewed child-skill plans whose
public contracts and required non-secret inputs are available.
Decision Workflow
- Read
references/feature-matrix.md for the architecture, feature stages,
product owners, and boundaries.
- Read
references/research-ledger.md before changing availability claims,
federation targets, model status, or product naming.
- Collect a non-secret intake from
template.example.
- Render and validate the packet.
- Review
gap-register.md, doctor-report.md, and the product and federation
matrices before executing delegated renders.
- Apply or validate state through the owning child skill, never through a
fabricated Cisco Data Fabric API.
Architecture Lanes
- Data access and management: collect, inspect, filter, shape, redact,
route, tier, and monitor machine data with supported Splunk ingestion,
Edge Processor, Ingest Processor, SPL2, and Ingest Monitoring workflows.
- Federation: route Splunk-to-Splunk and current Splunk Cloud Data
Management connection/dataset work to
splunk-federated-search-setup.
Track Amazon S3, Microsoft Azure, Azure Databricks, Snowflake, DDSS, and
Amazon Security Lake separately; do not infer equal stage or entitlement.
Product lifecycle and tenant access are separate fields: for example,
Amazon S3 federation and Federated Analytics can be GA while still requiring
sales activation, scan entitlement, a premium add-on, or topology gates.
- Storage and catalog: distinguish the real-time Splunk index, external
stores, DDSS/DDAA/SmartStore adjacencies, and the alpha Machine Data Lake.
Built-in Data Catalog and Machine Data Lake remain readiness handoffs until
stable public administration contracts exist.
- Context and governance: cover schema and catalog metadata, knowledge
objects, CIM/OCSF, ITSI/business context, RBAC, lineage, audit, human
approval, and downstream data-readiness evidence.
- AI activation and action: delegate AI Toolkit/PSC/DSDL, hosted-model
readiness, and MCP Server. Distinguish the available open Cisco Time Series
Model 1.0 from the GA hosted Cisco Deep Time Series Model integration, keep Agent
Launchpad at its documented GA boundary with its region, egress, connection,
and enabled-agent gates, and keep AI Canvas at its CA boundary.
- Cross-domain experience: represent SecOps, ITOps, Engineering/DevOps,
NetOps, Splunk Enterprise Security, ITSI, Observability Cloud, Cisco Cloud
Control, AI Canvas, and Cisco product telemetry as consumers or handoffs,
not as interchangeable Data Fabric components.
Safe First Command
bash skills/cisco-data-fabric-setup/scripts/setup.sh --help
Primary Workflow
Render and validate the complete evidence-backed packet:
bash skills/cisco-data-fabric-setup/scripts/setup.sh \
--render --validate \
--spec skills/cisco-data-fabric-setup/template.example \
--output-dir cisco-data-fabric-rendered
Run the gap/readiness doctor:
bash skills/cisco-data-fabric-setup/scripts/setup.sh \
--doctor \
--spec skills/cisco-data-fabric-setup/template.example \
--output-dir cisco-data-fabric-rendered
Preview delegated commands without writing or executing:
bash skills/cisco-data-fabric-setup/scripts/setup.sh \
--execute data-management,federation,ai-activation,context-governance \
--dry-run --json \
--spec skills/cisco-data-fabric-setup/template.example
Execute only reviewed delegated render/doctor commands:
bash skills/cisco-data-fabric-setup/scripts/setup.sh \
--execute data-management,ai-activation \
--accept-execute \
--spec skills/cisco-data-fabric-setup/template.example \
--output-dir cisco-data-fabric-rendered
CLI Contract
setup.sh supports --render, --validate, --doctor,
--execute SECTION[,SECTION], --accept-execute, --dry-run, --json,
--spec PATH, and --output-dir DIR.
Delegated sections:
data-management
federation
ai-activation
context-governance
Handoff-only sections, which refuse explicit execution:
storage-catalog
experience
Child commands are render, doctor, or plan operations. Applying their output
requires the child skill's own explicit approval gates. A missing child spec,
tenant URL, MCP URL, entitlement, or public API is reported as a gap rather
than silently converted into a successful apply.
Non-dry-run delegation fails before any child command when gap-register.json
contains an error, a selected section is handoff-only, or any selected
executable section has no reviewed command. This prevents partial execution
when a later lane is missing required intake.
Non-Negotiable Boundaries
- Do not claim a direct Cisco Data Fabric management API.
- Do not call Machine Data Lake or its built-in Data Catalog GA; current
public material identifies Machine Data Lake as alpha.
- Do not collapse store-specific federation stage, region, role, catalog, and
entitlement requirements into a generic "Federated Search is GA" claim.
- Do not use
activation_required as a product lifecycle. Record lifecycle in
product_stage and tenant/commercial gates in access_requirement.
- Do not create new legacy Amazon S3 federated providers on Splunk Cloud
10.5; the old provider/index path is deprecated and migrated to the Data
Management connection/dataset model.
- Do not promote announcement dates to current availability. Cisco Time Series
Model 1.0 is published as an open Apache-2.0 model and the hosted Cisco Deep
Time Series Model integration is generally available since AI Toolkit
6.0.0,
but they remain separately governed layers and neither one settles the other.
- Do not pair AI Toolkit
6.0.2 with a PSC release below 4.3.4. The audited
baseline is 6.0.2 with PSC 4.3.4 on Python 3.13; PSC 4.3.2 only
applies back at AI Toolkit 5.7.4.
- Do not describe Splunk AI Toolkit Agent Launchpad as alpha, private preview,
or a Fall 2026 GA target. Current AI Toolkit documentation makes it generally
available since
6.0.0. Report it as unreachable only when a readiness gate
actually fails: an unsupported AWS region or a missing region egress IP in
the stack apiAllowlistIP, no supported LLM connection, or no enabled agent.
Splunk Enterprise reaches it through the Splunk Cloud Connect app rather than
being unsupported.
- Do not treat Cisco Security Analytics and Logging (SAL) as Splunk Machine
Data Lake or as an automatically configured federation target.
- For AI Canvas with Splunk, require Cloud Control enablement, Splunk Cloud
10.5.2605.3, current AI Assistant and MCP Server, and
mcp_tool_execute; retain the 100-row-per-card and forbidden-SPL-command
limitations in the production handoff.
- Never accept raw tokens, passwords, API keys, client secrets, or private
keys in chat, argv, specs, or rendered artifacts.
Validation
bash skills/cisco-data-fabric-setup/scripts/validate.sh \
--output-dir cisco-data-fabric-rendered
python3 -m py_compile \
skills/cisco-data-fabric-setup/scripts/render_assets.py
Read reference.md for the rendered artifact contract and delegated owner
map.
1---2name: cisco-data-fabric-setup3description: "Use when users need Cisco Data Fabric architecture, feature or product coverage, readiness assessments,4 gap analysis, machine-data activation, federation targets, storage tiering, AI-ready data, or AgenticOps5 data foundation requests. Distinguish this architecture from a single product, package, entitlement, or6 direct API. Research, map, render, doctor, validate, and safely delegate complete Cisco Data Fabric7 adoption plans across Splunk data management, Edge Processor, Ingest Processor, SPL2, Federated Search,8 Machine Data Lake, Data Catalog, Splunk indexes and external stores, AI Toolkit and hosted models, Agent9 Builder, MCP Server, AI Canvas, context, governance, and cross-domain consumers."10compatibility: "Splunk Cloud Platform 10.5.2605: conditional. Follow documented package, entitlement, topology, and customer-managed runtime guardrails; self-managed paths remain on the public 10.4 baseline."11metadata:12 source: https://skillmd.com/skills/chambear2809/cisco-data-fabric-setup13 splunk_cloud_10_5: "conditional"14 compatibility_verified: "2026-08-20"15---1617# Cisco Data Fabric Setup1819## Prerequisites2021| Tool or access | Purpose | Verify |22|---|---|---|23| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |24| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |25| Credential files for live modes | Keep secrets out of chat | Verify paths only |2627## Workflow Overview2829```text30┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐31│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │32└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘33```3435## When to Activate3637- Users need Cisco Data Fabric architecture, feature or product coverage, readiness assessments, gap analysis,38 machine-data activation, federation targets, storage tiering, AI-ready data, or AgenticOps data foundation39 requests. Distinguish.40- Preview and review the cisco data fabric setup workflow before any live apply phase.41- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.4243## Scope4445Follow the documented read-only or render-first path whenever it is available.46This skill does not imply permission to mutate live systems. Require explicit47apply flags, protected credentials, and operator review for state changes.4849## Examples5051Inspect the supported setup modes before selecting one:5253```bash54bash skills/cisco-data-fabric-setup/scripts/setup.sh --help55```5657Expected output: usage, supported modes, and required arguments are displayed58without changing the target environment.5960Inspect validation modes before running completion checks:6162```bash63bash skills/cisco-data-fabric-setup/scripts/validate.sh --help64```6566Expected output: offline, live, and completion options are displayed when the67skill supports them; help exits without mutation.6869## Troubleshooting7071| Issue | Cause | Resolution |72|---|---|---|73| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |74| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |75| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |76| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7778Treat Cisco Data Fabric as the architecture powered by the Splunk Platform,79not as a single installer, SKU, API, or storage product. Render a complete80coverage packet first, then execute only reviewed child-skill plans whose81public contracts and required non-secret inputs are available.8283## Decision Workflow84851. Read `references/feature-matrix.md` for the architecture, feature stages,86 product owners, and boundaries.872. Read `references/research-ledger.md` before changing availability claims,88 federation targets, model status, or product naming.893. Collect a non-secret intake from `template.example`.904. Render and validate the packet.915. Review `gap-register.md`, `doctor-report.md`, and the product and federation92 matrices before executing delegated renders.936. Apply or validate state through the owning child skill, never through a94 fabricated Cisco Data Fabric API.9596## Architecture Lanes97981. **Data access and management**: collect, inspect, filter, shape, redact,99 route, tier, and monitor machine data with supported Splunk ingestion,100 Edge Processor, Ingest Processor, SPL2, and Ingest Monitoring workflows.1012. **Federation**: route Splunk-to-Splunk and current Splunk Cloud Data102 Management connection/dataset work to `splunk-federated-search-setup`.103 Track Amazon S3, Microsoft Azure, Azure Databricks, Snowflake, DDSS, and104 Amazon Security Lake separately; do not infer equal stage or entitlement.105 Product lifecycle and tenant access are separate fields: for example,106 Amazon S3 federation and Federated Analytics can be GA while still requiring107 sales activation, scan entitlement, a premium add-on, or topology gates.1083. **Storage and catalog**: distinguish the real-time Splunk index, external109 stores, DDSS/DDAA/SmartStore adjacencies, and the alpha Machine Data Lake.110 Built-in Data Catalog and Machine Data Lake remain readiness handoffs until111 stable public administration contracts exist.1124. **Context and governance**: cover schema and catalog metadata, knowledge113 objects, CIM/OCSF, ITSI/business context, RBAC, lineage, audit, human114 approval, and downstream data-readiness evidence.1155. **AI activation and action**: delegate AI Toolkit/PSC/DSDL, hosted-model116 readiness, and MCP Server. Distinguish the available open Cisco Time Series117 Model 1.0 from the GA hosted Cisco Deep Time Series Model integration, keep Agent118 Launchpad at its documented GA boundary with its region, egress, connection,119 and enabled-agent gates, and keep AI Canvas at its CA boundary.1206. **Cross-domain experience**: represent SecOps, ITOps, Engineering/DevOps,121 NetOps, Splunk Enterprise Security, ITSI, Observability Cloud, Cisco Cloud122 Control, AI Canvas, and Cisco product telemetry as consumers or handoffs,123 not as interchangeable Data Fabric components.124125## Safe First Command126127```bash128bash skills/cisco-data-fabric-setup/scripts/setup.sh --help129```130131## Primary Workflow132133Render and validate the complete evidence-backed packet:134135```bash136bash skills/cisco-data-fabric-setup/scripts/setup.sh \137 --render --validate \138 --spec skills/cisco-data-fabric-setup/template.example \139 --output-dir cisco-data-fabric-rendered140```141142Run the gap/readiness doctor:143144```bash145bash skills/cisco-data-fabric-setup/scripts/setup.sh \146 --doctor \147 --spec skills/cisco-data-fabric-setup/template.example \148 --output-dir cisco-data-fabric-rendered149```150151Preview delegated commands without writing or executing:152153```bash154bash skills/cisco-data-fabric-setup/scripts/setup.sh \155 --execute data-management,federation,ai-activation,context-governance \156 --dry-run --json \157 --spec skills/cisco-data-fabric-setup/template.example158```159160Execute only reviewed delegated render/doctor commands:161162```bash163bash skills/cisco-data-fabric-setup/scripts/setup.sh \164 --execute data-management,ai-activation \165 --accept-execute \166 --spec skills/cisco-data-fabric-setup/template.example \167 --output-dir cisco-data-fabric-rendered168```169170## CLI Contract171172`setup.sh` supports `--render`, `--validate`, `--doctor`,173`--execute SECTION[,SECTION]`, `--accept-execute`, `--dry-run`, `--json`,174`--spec PATH`, and `--output-dir DIR`.175176Delegated sections:177178- `data-management`179- `federation`180- `ai-activation`181- `context-governance`182183Handoff-only sections, which refuse explicit execution:184185- `storage-catalog`186- `experience`187188Child commands are render, doctor, or plan operations. Applying their output189requires the child skill's own explicit approval gates. A missing child spec,190tenant URL, MCP URL, entitlement, or public API is reported as a gap rather191than silently converted into a successful apply.192193Non-dry-run delegation fails before any child command when `gap-register.json`194contains an `error`, a selected section is handoff-only, or any selected195executable section has no reviewed command. This prevents partial execution196when a later lane is missing required intake.197198## Non-Negotiable Boundaries199200- Do not claim a direct Cisco Data Fabric management API.201- Do not call Machine Data Lake or its built-in Data Catalog GA; current202 public material identifies Machine Data Lake as alpha.203- Do not collapse store-specific federation stage, region, role, catalog, and204 entitlement requirements into a generic "Federated Search is GA" claim.205- Do not use `activation_required` as a product lifecycle. Record lifecycle in206 `product_stage` and tenant/commercial gates in `access_requirement`.207- Do not create new legacy Amazon S3 federated providers on Splunk Cloud208 10.5; the old provider/index path is deprecated and migrated to the Data209 Management connection/dataset model.210- Do not promote announcement dates to current availability. Cisco Time Series211 Model 1.0 is published as an open Apache-2.0 model and the hosted Cisco Deep212 Time Series Model integration is generally available since AI Toolkit `6.0.0`,213 but they remain separately governed layers and neither one settles the other.214- Do not pair AI Toolkit `6.0.2` with a PSC release below `4.3.4`. The audited215 baseline is `6.0.2` with PSC `4.3.4` on Python `3.13`; PSC `4.3.2` only216 applies back at AI Toolkit `5.7.4`.217- Do not describe Splunk AI Toolkit Agent Launchpad as alpha, private preview,218 or a Fall 2026 GA target. Current AI Toolkit documentation makes it generally219 available since `6.0.0`. Report it as unreachable only when a readiness gate220 actually fails: an unsupported AWS region or a missing region egress IP in221 the stack `apiAllowlistIP`, no supported LLM connection, or no enabled agent.222 Splunk Enterprise reaches it through the Splunk Cloud Connect app rather than223 being unsupported.224- Do not treat Cisco Security Analytics and Logging (SAL) as Splunk Machine225 Data Lake or as an automatically configured federation target.226- For AI Canvas with Splunk, require Cloud Control enablement, Splunk Cloud227 `10.5.2605.3`, current AI Assistant and MCP Server, and228 `mcp_tool_execute`; retain the 100-row-per-card and forbidden-SPL-command229 limitations in the production handoff.230- Never accept raw tokens, passwords, API keys, client secrets, or private231 keys in chat, argv, specs, or rendered artifacts.232233## Validation234235```bash236bash skills/cisco-data-fabric-setup/scripts/validate.sh \237 --output-dir cisco-data-fabric-rendered238239python3 -m py_compile \240 skills/cisco-data-fabric-setup/scripts/render_assets.py241```242243Read `reference.md` for the rendered artifact contract and delegated owner244map.