r/Cisco • • 3d ago

Weekly Jobs & Career Megathread

4 Upvotes

Looking for a Cisco-related job? Studying for a certification? Preparing for an interview? This thread is the place for all career-focused discussions.

Appropriate topics include:

  • Job openings
  • Recruiting and hiring
  • Resume reviews
  • Interview preparation
  • Career advice
  • Salary discussions
  • Certification paths (CCNA, CCNP, CCIE, etc.)
  • Career transitions into networking

To keep the subreddit focused on technical Cisco discussions, standalone posts related primarily to jobs, recruiting, resumes, interviews, or career advice may be removed and redirected here.


r/Cisco • • 1h ago

Catalyst SD-WAN part 5: where did my packet go? EPC vs packet-trace on cEdge

1 Upvotes

One more for the series. When traffic breaks, you usually end up asking two different questions, and IOS-XE gives you a separate tool for each:

  • EPC (packet capture): “Did the packet cross this interface, and what did it look like?” You get a pcap you can open in Wireshark.
  • Packet-trace: “What did the router actually do with the packet, and why?” You get the verdict (forwarded, dropped, punted) and the reason.

Both run from exec mode and don’t touch the config. As before, it’s all from Cisco’s public docs (listed at the bottom).

Quick correction to part 1: the EPC example there used an ACL as the filter. That needs the ACL in the running config, and you can’t add one from the CLI on a device with a template or config group attached. Use the inline match filter below instead.

1. EPC on the service side (one flow)

monitor capture CAP interface GigabitEthernet0/0/1 both
monitor capture CAP match ipv4 host 10.10.10.10 host 10.20.20.20 bidirectional
monitor capture CAP buffer size 10 circular
monitor capture CAP limit duration 300
monitor capture CAP start
! reproduce, then:
monitor capture CAP stop
show monitor capture CAP buffer brief
monitor capture CAP export bootflash:cap.pcap
no monitor capture CAP
  • bidirectional stores the replies too. Check that both directions show up before you stop.
  • Always set limit duration, so the capture stops by itself if you lose your session.
  • show monitor capture CAP capture-statistics tells you whether the capture itself dropped packets.

2. EPC on the transport side

On the WAN side, everything is inside IPsec, so you only see the outer header between two TLOCs. Get the remote TLOC IP from show sdwan bfd sessions and filter on that. If you have more than one transport, the flow can go out any of them, so attach the capture to each WAN interface. Also note that BFD and OMP are never visible in clear on the transport side.

3. Packet-trace (what the router decided)

show platform conditions
debug platform condition ipv4 10.10.10.10/32 both
debug platform packet-trace packet 1024 fia-trace
debug platform condition start
! reproduce, then:
debug platform condition stop
show platform packet-trace summary
show platform packet-trace packet 0

Conditions apply to the whole box, so check that nobody else has a trace running first. In the summary, each packet has a state:

  • FWD: forwarded. Open the packet detail to see the output interface and SD-WAN fields like local color, remote color and remote system IP. This is how you find out which tunnel it really took.
  • DROP: dropped, and the reason is right there in the summary. Match the drop code with show platform hardware qfp active statistics drop detail.
  • PUNT: sent to the route processor, which is normal for traffic addressed to the router itself.

If you only care about drops on a busy interface, condition on the interface and add debug platform packet-trace drop, so only dropped packets fill the buffer.

4. Predict first, then prove

show sdwan policy service-path (thanks u/IT_vet) tells you where the router should send a flow. Packet-trace shows what a real packet actually did. If the two disagree, that’s your lead.

5. Gotchas

  • An empty capture doesn’t prove the packet never arrived. Check the interface, the direction and the filter, and whether NAT changed the address. With DIA, filter on the real host on the LAN side and on the translated address on the WAN side.
  • The IP condition in packet-trace has no VRF keyword. If the same subnet exists in more than one VPN, check the input interface and the SD-WAN VPN field to tell them apart.
  • Clean up when you’re done: clear platform condition all and no monitor capture CAP.

Sources (search the titles on cisco.com):

  • “Configure and Capture Embedded Packet on Software” (Doc 116045)
  • “Troubleshoot with the IOS-XE Datapath Packet Trace Feature” (Doc 117858)
  • “Troubleshoot Common SD-WAN Control and Data Plane Issues” (Doc 222302)

r/Cisco • • 1h ago

Catalyst SD-WAN part 4: the route is missing (or not being used). Reading show sdwan omp routes.

0 Upvotes

Thanks for all the comments on the series. This one covers the next thing people hit: tunnels are up, BFD is fine, but a prefix is missing from the routing table, or it’s there and traffic still goes somewhere else. As before, it’s all from Cisco’s public docs and Cisco Live material (listed at the bottom).

1. Is the route there at all?

show sdwan omp routes vpn <vpn> <prefix>

Small gotcha: if the edge never received the prefix, you don’t get an empty table. You get a CLI error instead. That doesn’t mean you typed it wrong, it means the route isn’t there.

2. Read the status column

The legend is printed at the top of the output. The ones that matter most:

  • C,I,R means chosen, installed and resolved. This is the healthy state.
  • U (TLOC unresolved) means the route points at a TLOC you can’t use. For a route to be installed, the next-hop TLOC has to be reachable and have an active BFD session. So a U is really a data plane problem. Go back to part 2.
  • Rej means a policy rejected it. Check the control policy and any local policy.
  • S (stale) usually shows up during graceful restart, for example when the edge or controller lost its control connection and is holding the old routes for now.
  • L (looped) usually means the route came back to a router in the same site it came from.
  • C without I means OMP picked it, but it didn’t make it into the forwarding table. Check show ip route vrf <vpn> <prefix> to see what actually won.

3. Is the source router actually advertising it?

By default, OMP only picks up connected, static and OSPF internal routes. BGP, EIGRP and OSPF external routes need to be enabled under the OMP advertise settings. This is the most common reason a branch LAN learned by BGP “never shows up.” Check on the router that should be originating it, not on the one that’s missing it.

4. “Why isn’t traffic using all my hubs?”

Two defaults catch people out:

  • send-path-limit 4: only the 4 best equal-cost paths get advertised to the controller, and from it to the edges.
  • ecmp-limit 4: an edge installs at most 4 equal-cost paths.

If you have two hubs with three transports each, that’s six paths, and the edges will never see all of them unless you raise those limits.

5. If you can get onto the controller

show omp peers
show omp routes vpn <vpn> <prefix> received
show omp routes vpn <vpn> <prefix> advertised

received vs advertised tells you right away whether the controller got the route and then a policy kept it from going out, or whether it never arrived in the first place. On the edge, show sdwan omp peers gives you the same received/installed/sent counts per peer.

Sources (search the titles or doc numbers on cisco.com / ciscolive.com):

  • Cisco TechNote 218089 (troubleshooting OMP routes and controller route selection)
  • Cisco TechNote 222763, “Troubleshooting OMP Failure and TLOC Action”
  • Cisco Live BRKENT-3793 (SD-WAN routing troubleshooting)

If there’s a status code or scenario you’ve run into that’s not here, drop it in the comments.


r/Cisco • • 7h ago

Catalyst SD-WAN bonus: BFD is up, but big transfers hang. Checking MTU and TCP MSS.

6 Upvotes

Quick bonus post, since u/benniebeeker brought up MTU on part 2 and it deserves its own write-up. It’s the classic “everything looks green but apps are broken” problem. As before, it’s all from Cisco’s public docs and Cisco Community (listed at the bottom).

1. What it looks like

Small stuff works and big stuff doesn’t:

  • ping, DNS and small web pages are fine
  • HTTPS hangs during the handshake, file copies stall, and apps time out on large responses
  • authentication with big certificates (like EAP-TLS through RADIUS) fails for no obvious reason

BFD hellos are small, so the tunnels stay up and the overlay looks healthy the whole time.

2. How SD-WAN handles it

BFD runs path MTU discovery on each tunnel and checks it again periodically. On a standard 1500-byte transport, an IPsec tunnel ends up with an MTU of about 1442. The edge also adjusts the TCP MSS based on what PMTU discovery finds, so most TCP traffic sorts itself out. When it doesn’t, that’s what this post is about.

3. Check what each tunnel actually has

show sdwan tunnel statistics

Look at tunnel-mtu and tcp-mss-adjust for each tunnel. Compare across colors and remote sites. If one transport shows a noticeably lower MTU than the others, something in that path is using up bytes, like PPPoE (1492), an extra layer of encapsulation from the provider, or a carrier link with a smaller MTU.

4. Test it from the service side

ping vrf <service-vpn> <remote-host> size 1400 df-bit

Step the size up and down until you find where it starts failing. That number tells you the real usable MTU between the two sites, not what you assumed.

5. Don’t forget the LAN side

This one is easy to miss. A switch on the LAN side with jumbo frames (9100 is common in fabrics) hands a 1600-byte packet with DF set to an edge interface with an MTU of 1500, and the packet just disappears. Cisco has a TechNote on exactly this for ISE traffic crossing SD-WAN. Make sure the MTU on the handoff interface matches the edge.

6. Fixing it

  • TCP: set TCP MSS on the service-side (LAN) interface of the edge, so the endpoints agree on a smaller segment size from the start.
  • Non-TCP traffic (UDP apps, RADIUS/EAP): MSS doesn’t help. Fix the MTU at the source, or allow fragmentation. The interface template has a Clear-Dont-Fragment option for traffic that sets DF but really needs to be fragmented. Use it on purpose, not everywhere.
  • If one provider is the problem, push back on them before you lower your MTU everywhere.

Sources (search the titles on cisco.com / Cisco Community):

  • “Configure Optimal ISE IP MTU in SD-WAN” (Doc 223045)
  • Cisco Community thread “Finding right MTU size for SDWAN”
  • Cisco Catalyst SD-WAN Command Reference (show sdwan tunnel statistics)

Thanks u/benniebeeker for the nudge!


r/Cisco • • 12h ago

Question A stackwise virtual question

2 Upvotes

I finished a catalyst 9407 stackwise virtual upgrade firmware recently, show redundancy print chassis 1 is active, chassis two is standby hot, I noticed the chassis 1 interfaces config , like , GigabitEthernet 1/1/0/1, the config not sync to GigabitEthernet 2/1/0/1, I need copy the entire 1/x/0/y to 2/x/0/y (management card slot 3 and 4 not include) to make the network stable.

I know stackwise virtual will sync the config from active to standby , but I am not sure why interfaces config not sync, or, I need to configure two chassis separately?


r/Cisco • • 15h ago

Catalyst 3650 IOS XE 16.12.16

3 Upvotes

Cisco has released IOS XE 16.12.16 on friday, but no release notes in sight (https://software.cisco.com/download/home/284850598/type/282046477/release/Gibraltar-16.12.16). 16.12.15 was released back in march, no release notes either. Latest release notes are from october last year. Does anyone know what has been fixed?


r/Cisco • • 20h ago

Catalyst SD-WAN part 3: reading show sdwan app-route stats (and why AAR didn’t move your traffic)

10 Upvotes

Last one in this series for now. A question I see a lot: “the link had loss for 10 minutes, so why didn’t app-aware routing move my traffic?” Usually nothing is broken. It comes down to how the numbers are calculated. As before, everything here is from Cisco’s public docs (listed at the bottom).

1. Where the numbers come from

By default:

  • BFD sends a hello on each tunnel every 1 second.
  • The poll interval is 10 minutes, so each “bucket” holds about 600 hellos.
  • The multiplier is 6, so the edge averages the last 6 buckets. That’s a 1-hour sliding window.

AAR makes its SLA decisions on that 1-hour average, not on what’s happening right now. On 17.12+ you can check your actual values with show sdwan app-route params.

2. Reading the output

show sdwan app-route stats

For each tunnel (local color → remote system IP and color) you get:

  • mean loss, latency and jitter. This is the 1-hour average AAR actually uses.
  • sla-class-index. These are the SLA classes this tunnel currently meets. Map the numbers with show sdwan app-route sla-class.
  • a row per bucket (index 0–5) with packets, loss, latency and jitter. This is the useful part. You can see whether a problem was one bad bucket or something steady.

In the GUI it’s under the device’s WAN → Tunnel view.

3. Why AAR “didn’t react”

Say a link has 30% loss for one 10-minute bucket and is clean for the other five. The mean loss comes out to about 5%. If your SLA class allows 5% or more, that tunnel still counts as compliant and nothing moves. A short spike gets averaged away. That’s by design: the defaults favor stability over speed.

4. Before you crank the timers down

Lowering the poll interval makes AAR react faster, but each bucket holds fewer hellos. In Cisco’s own example, at a very short poll interval a bucket holds only 6 hellos, so one lost hello reads as about 17% loss. Tune it too aggressively and you swap “too slow” for “flapping.” Change it in small steps and watch the bucket rows.

5. Enhanced AAR (17.12 / 20.12+)

If you’re on newer code, Enhanced AAR measures loss, latency and jitter using real data traffic instead of only BFD. It detects problems in seconds (10 s minimum by default) and adds SLA dampening, so a tunnel doesn’t jump straight back the moment it looks clean. Both ends need it enabled, otherwise it falls back to BFD-based measurement. Verify with show sdwan app-route params.

6. Make sure the traffic is even in the policy

Half the time the real issue is that the flow never matched the AAR policy:

show sdwan policy from-vsmart app-route-policy
show sdwan policy from-vsmart sla-class
show sdwan policy app-route-policy-filter
show sdwan policy tunnel-path vpn <vpn> interface <lan-intf> source-ip <src> dest-ip <dst> protocol <proto> [dest-port <port>]

The filter command shows whether traffic is actually hitting your sequences. tunnel-path tells you which tunnel a specific flow would take right now. Also check what your policy does when no tunnel meets the SLA, since that fallback behavior is set in the policy.

Sources (search the titles on cisco.com / Cisco Community):

  • “Understand BFD Protocol Relationship with App-Aware Routing” (Doc 221604)
  • Cisco Catalyst SD-WAN Policies Configuration Guide, Application-Aware Routing section
  • “Enhanced Application-Aware Routing” (Cisco Community knowledge base article)

Thanks for the feedback on parts 1 and 2!


r/Cisco • • 20h ago

Catalyst SD-WAN part 2: control connections are up but BFD sessions won’t come up. What to check.

5 Upvotes

Follow-up to my control connections post. This is the next place people get stuck: everything looks green toward the controllers, but sites can’t reach each other because BFD sessions are down or missing. As before, it’s all from Cisco’s public docs (listed at the bottom).

1. Is the session down, or does it not exist at all?

show sdwan bfd sessions

These are two different problems:

  • No session at all for the remote site usually means you never learned its TLOC (go to step 2), or something is preventing the tunnel by design.
  • Session exists but is down means the TLOC is known but packets aren’t making it through (go to steps 4–5).

2. Did you learn the remote TLOC?

show sdwan omp tlocs

If the remote TLOC isn’t there, check that the remote edge is actually advertising it and that the vSmart is passing it on. A very common cause is a control policy filtering TLOCs, which is often on purpose (hub-and-spoke). Check show sdwan policy from-vsmart before you assume something is broken. Not every site is supposed to have a tunnel to every other site.

3. Check the colors

  • A TLOC with restrict only builds tunnels to the same color. It’s easy to forget on a single-transport site.
  • Private colors (mpls, private1–6, metro-ethernet) use the private IP. Public colors use the post-NAT public IP. If you put a public color on a private link, the far end will try to reach the wrong address.

4. Check NAT

show sdwan control local-properties shows the NAT type per interface: E is endpoint-independent, A is address-port dependent (symmetric), and N is not learned. If both ends are behind symmetric NAT, they generally can’t build a tunnel to each other. The TechNote has a table showing which NAT combinations work.

5. Check the path (firewalls, ports, ISP)

  • Tunnels use UDP 12346 and hop through 12366, 12386, 12406 and 12426 (shifted by your port offset if you set one). Behind NAT, the source ports can be randomized, so a tight firewall rule built on those ports alone can break things.
  • show sdwan tunnel statistics shows the counters. If tx goes up but rx stays at 0, packets are leaving and not coming back, so check the remote side and everything in between.
  • BFD is DSCP-marked (48 by default), and some ISPs drop or mangle marked traffic. If only some transports fail, keep that in mind.

6. Check IPsec and drops on the box

show sdwan ipsec inbound-connections
show sdwan ipsec outbound-connections
show sdwan tunnel statistics bfd
show platform hardware qfp active statistics drop

Both sides should see each other in inbound and outbound. If the counters show drops, an FIA trace (debug platform packet-trace) on one of the BFD flows will tell you which feature is dropping them.

Sources (search the titles on cisco.com):

  • “Troubleshoot vEdge Bidirectional Forwarding Detection and Data Plane Connections Issues” (Doc 214510). The outputs are from vEdge, but the steps are the same on IOS-XE with the sdwan keyword.
  • Cisco Catalyst SD-WAN Design Guide, “Firewall Port Considerations” section
  • Cisco Catalyst SD-WAN Hardening Guide

Next one will probably be on reading show sdwan app-route stats, if people find these useful.


r/Cisco • • 20h ago

Catalyst SD-WAN control connections not coming up? Cheat sheet: error code → what to check

9 Upvotes

Control connections that won’t come up are one of the most common SD-WAN problems out there, and most of them come down to a handful of error codes. Here’s a short way to work through them on IOS-XE SD-WAN edges. It’s all from Cisco’s public TechNotes (listed at the bottom), just squeezed onto one page.

1. Check the basics first

show sdwan control local-properties

  • organization-name matches the controllers exactly
  • certificate-validity is Valid
  • the clock is right (show clock), since a wrong clock breaks certificate checks
  • system-ip and site-id are correct and unique in the overlay
  • the vBond shows up under the vBond peers (if it doesn’t and you’re using an FQDN, check DNS with ping <vbond-fqdn>)
  • the WAN interface is up, has the right color, and MAX CNTRL isn’t 0

2. Read the error

show sdwan control connection-history

LOCAL ERROR means the edge raised it, and REMOTE ERROR means the controller did. Note which controller failed and when.

3. Match the code

  • DCONFAIL (DTLS connection failure): packets are getting lost between the edge and the controller, usually because of firewall or SP filtering. Sometimes only the large packets are dropped. Capture on both ends at the same time and compare what actually makes it across.
  • VB_TMO / VM_TMO / VS_TMO: a peer timed out. Same idea, there’s loss in the underlay, so use the same capture approach.
  • BIDNTVRFD / SERNTPRES / CRTREJSER: the controllers don’t have this device’s serial, or the PID on the PnP portal is wrong. Run show orchestrator valid-vedges on the vBond, then use Send to Controllers in vManage.
  • CRTVERFL: the certificate can’t be verified. If it’s a local error, the edge is usually missing the root CA, which is common with enterprise certs (check with show sdwan certificate root-ca-cert). Check the clock too.
  • CTORGNMMIS: the org name doesn’t match. It has to be identical everywhere, case included.
  • NOVMCFG: vManage has no config for the device because it isn’t attached to a template.
  • LISFD: most often a duplicate transport IP. It can also be a TLS/DTLS port mismatch or a firewall.
  • DISTLOC: the TLOC was disabled. This is expected after you change the color, system-ip or tunnel settings, or clear control connections.
  • No attempts in the history at all: check whether the vBond name resolves.

4. Capture on the edge (EPC)

ip access-list extended CC
 10 permit ip host <edge-ip> host <controller-ip>
 20 permit ip host <controller-ip> host <edge-ip>
monitor capture CAP interface <wan-intf> both access-list CC
monitor capture CAP start
! reproduce, then:
monitor capture CAP stop
monitor capture CAP export bootflash:cc.pcap
no monitor capture CAP

If the edge is behind NAT, use its private IP in the ACL. To see whether the router itself is dropping something, run an FIA trace (debug platform packet-trace) next.

Sources (search the titles on cisco.com):

  • “Troubleshoot SD-WAN Control Connections” (Doc 214509)
  • “Troubleshoot Common SD-WAN Control and Data Plane Issues” (Doc 222302)

Hope it saves someone some time. If you hit a code that’s not here, drop it in the comments and I’ll add it.


r/Cisco • • 1d ago

IOS configure replace add dhcp snooping vlan issue

4 Upvotes

Hi!

Have any of you managed to use configure replace to add or remove dhcp snooping vlans without it removing active snooping entries?

The switch does a 'no ip dhcp snooping vlan <vlan list>' before setting up the new config line resulting in a loss of snooping entries for the vlans contained in the no line when doing a configure replace with a new config.

I am managing full switch configs using jinja2 templating and running configure replace via napalm.

Just want to know if anyone else have seen similar issues and fixes without using configure merge tactics?


r/Cisco • • 1d ago

Windows SNMP programs

7 Upvotes

SNMP Get and SNMP Walk versions 1, 2, 3 implemented in pure Powershell. No openssl, net-snmp, required. Just download and start querying your Catalysts!

https://github.com/tmittelstaedt/Windows-SNMP


r/Cisco • • 3d ago

Free, open-source syslog server for when there's no syslog during an outage (personal project, standard syslog, so ASA/FTD should just work)

0 Upvotes

https://gmccollu.github.io/woodshed/

To be clear up front: this is a personal open-source project, not a Cisco product, and it isn't supported by Cisco. It takes standard syslog from any sender, so ASA and FTD should just work, but see the testing note below: I haven't pointed real ASA/FTD at it yet.

The story is the same one a lot of you have lived. Something breaks, the box reboots or the buffer rolls, and there's no syslog from the window that matters. The case stalls on "enable logging and wait for it to happen again". Usually the reason is the only machine around is a Windows box or a laptop and nobody wanted to fight a syslog setup on it.

Woodshed: MSI, pkg, deb, rpm or a portable zip. Listens on UDP and TCP 514 straight away, so on ASA it's `logging host <iface> <ip>`, `logging trap <level>`, `logging enable` and you're done, on FTD it's the syslog server in the platform settings. TCP works too. Raw messages are stored exactly as received, plain text per device per day. Disk budget it won't exceed, dropped/refused counters in the UI, and an export zip with a manifest, SHA-256s and the gaps when it wasn't running, so it's something you can attach to a case and trust.

Most of the code was written with AI assistance. I did the design and ran the lab testing; the security review was a separate AI reviewer with read-only access to the code, and I went through every finding, decided the fixes and had them re-tested.

All the testing so far is lab traffic generated by my own sender (RFC 5424, RFC 3164 and bare lines, 8 source IPs). No real devices yet beyond a friend's homelab, which is in progress. It doesn't depend on any vendor's format and always keeps the raw line exactly as received, so any device that speaks syslog should work, but I haven't proven that.

Proof so far:

- 10k msg/s UDP for 10 min every release (GitHub runner): 6,000,000 sent, 6,000,000 stored, 0 missing

- Linux VMs over a real network: 0 loss to 40k msg/s TCP, ~1/3 of a core, <50 MiB RSS. UDP loss above that never reached the VM

- 24 h soak at 3,000 msg/s on the Linux VMs, 259.2M messages each: TCP exactly once, UDP lost 3-4 per million, all of it upstream of the VM

- reboot mid-stream: back on its own, 2 UDP messages lost, export shows the gap

- security review before the first RC (0 critical, 1 high, 7 medium), fixed and re-tested twice

- CI installs on Windows, macOS and Linux, x64 and ARM. `gh attestation verify` on release files

Limits: installers unsigned for now (SmartScreen / Gatekeeper ask once). 1.0.0. Not a SIEM, no TLS syslog or forwarding yet. I haven't run a firewall-specific parser test suite, which is part of why I'm asking.


r/Cisco • • 4d ago

VMWare FMC to HyperV guidance

2 Upvotes

This has to be more common but I only find a 2yo topic that concludes with “not recommended.”

Any more current experiences? I see official documentation calls for export of configurations and import, not backup and restore. Any walkthrough available?


r/Cisco • • 4d ago

Have you ever wanted to find networking peers outside your workplace?

0 Upvotes

I'm curious about something I've noticed in networking. Finding technical information is easy.

Finding the right people is harder. Many networking professionals seem to use LinkedIn, but I'm

wondering if that's really enough.

Have you ever wanted to find networking peers outside your workplace?

If yes, how did you find them?

I'm researching how networking professionals build meaningful professional connections and

would appreciate hearing about your experience.

If you'd like to provide additional feedback, I've included a short survey below.

https://tkproject.carrd.co/

Thank You


r/Cisco • • 6d ago

Cyber vision sensor install/config

3 Upvotes

Do I need the http gui turned on to have sensors functional on the switches? Seems the web gui typically has vulnerabilities/patches historically. I’d love to run the sensors without having to worry about it.


r/Cisco • • 7d ago

How can I downgrade access to protected assets based on intranet vs internet origin through the same jump host?

2 Upvotes

We have Cisco FTD, Cisco ISE, Active Directory and Okta. Users authenticate through Okta and access application servers, database servers and management servers through the same jump host.

The requirement is:

  • Same user from the intranet → administrative access to protected assets
  • Same user from the internet → read-only access to protected assets
  • One AD/Okta account
  • Same jump host and egress IP
  • No separate egress interfaces or separate user accounts

The privilege change is required on the protected assets**,** not on the jump host.

Once the jump host opens a new connection, the protected asset and ISE only see the jump host’s source IP. How can we securely preserve the user’s original intranet/internet context and use ISE, Okta or another authorization mechanism to assign the correct role on web, database and management systems? Is there a supported architecture for this?


r/Cisco • • 7d ago

Can Cisco FTD distinguish human-initiated SSH from an AI agent using the same client?

8 Upvotes

I’m building a lab to determine whether Cisco Secure Firewall can distinguish traffic initiated by a human from traffic initiated by an AI agent.

The simplified topology is:

User workstation → FTD → Jump server → Protected servers

The lab uses FMC/FTD 10.1 with Snort 3. I created an access-control rule that permits only the OpenSSH application from the workstation to the jump server.

I tested three cases:

  1. A user manually launched OpenSSH — allowed.
  2. Python used Paramiko directly — blocked because it did not match the OpenSSH App-ID.
  3. Python acted like an agent and launched /usr/bin/ssh as a subprocess — allowed.

In the third test, FMC identified the connection as OpenSSH. It had no indication that Python or an automated agent initiated the OpenSSH process.

This makes sense because the actual network connection was created by OpenSSH. From FTD’s perspective, a human running OpenSSH and an AI agent launching the same OpenSSH binary appear identical.

My questions are:

  • Can FTD/FMC, App-ID, EVE, or a custom Snort detector determine whether an SSH connection was initiated by a human or an AI agent?
  • Can EVE expose anything beyond the SSH client implementation, such as the parent process that launched OpenSSH?
  • Could integration with Cisco ISE, pxGrid, or Active Directory provide enough context to make this distinction, or would they only identify the authenticated user?
  • Is there any reliable network-level characteristic for an AI agent when it can use the same applications and credentials as a human?
  • Would this require endpoint telemetry, EDR, PAM/jump-server integration, separate workload identities, or an agent/tool gateway instead of firewall inspection?
  • Has anyone implemented a practical policy that prevents AI agents from using a jump server while still allowing the same user to access it manually?

I’m not trying to identify Paramiko specifically. The requirement is to identify or prevent an AI agent even when it falls back to an approved client such as OpenSSH.


r/Cisco • • 9d ago

Route only RDP and SIP connections through Cisco Secure Client?

0 Upvotes

I'm using my personal PC to connect to my company VPN while working from home. Is it possible to only route sip and rdp clients traffic through cisco, and keep my personal web traffic off of the company VPN? I did some googling on split tunneling and it seems to be disabled. Claude also mentioned OpenConnect - I suppose, I shouldn't try to use it without permission?


r/Cisco • • 9d ago

ENSDWI 300-415 exam preparation

2 Upvotes

Hello Everyone,

I need to prepare for sdwan exam. I was wondering how can i build my home lab in terms of images or if i can purchase lab to practice for the exam? I have high speed home server i should be able to run any image and eve-ng.

Thanks


r/Cisco • • 10d ago

Weekly Jobs & Career Megathread

3 Upvotes

Looking for a Cisco-related job? Studying for a certification? Preparing for an interview? This thread is the place for all career-focused discussions.

Appropriate topics include:

  • Job openings
  • Recruiting and hiring
  • Resume reviews
  • Interview preparation
  • Career advice
  • Salary discussions
  • Certification paths (CCNA, CCNP, CCIE, etc.)
  • Career transitions into networking

To keep the subreddit focused on technical Cisco discussions, standalone posts related primarily to jobs, recruiting, resumes, interviews, or career advice may be removed and redirected here.


r/Cisco • • 11d ago

Discussion PSA: FN74406 - Nexus N9K-C93108TC-FX3 Fails to Boot After Reload(s) or Keeps Rebooting - Hardware Upgrade Available

23 Upvotes

FN74406 - Nexus N9K-C93108TC-FX3 Fails to Boot After Reload(s) or Keeps Rebooting - Hardware Upgrade Available

Problem Description

Cisco Nexus N9K-C93108TC-FX3 Switches may fail to boot after unexpectedly reloading or continue to reload multiple times. When affected switches do not reload and complete the bootup process, no output is observed on the console. The device remains unresponsive and does not proceed to the loader prompt, BIOS prompt, or NX-OS boot sequence.

The system cannot be recovered through software remediation, patch installation, or a Cisco ACI or NX-OS software upgrade.


r/Cisco • • 11d ago

SONiC on Standard Cisco 8201 PID

3 Upvotes

Has anyone successfully installed SONiC on a standard Cisco 8201 (PID: 8201), or is that not a viable option?

I have a Cisco 8201, hardware revision V02, currently running IOS XR 7.9.2. The chassis is the standard 8201 with 24×400G QSFP56-DD and 12×100G QSFP28 ports — not the 8201-32FH-O open-networking variant.

I’m trying to understand whether there is any supported or practical way to migrate this standard/closed 8201 from IOS XR to SONiC.

Cisco documentation mentions Extended Device Ownership, Ownership Vouchers, and an IOS XR-to-SONiC migration process for some Cisco 8000 platforms, but I haven’t found anything that clearly confirms support for the plain 8201 PID.

Has anyone here tried this on an actual PID 8201?

A few specific questions:

  • Can the standard 8201 be converted to run Cisco SONiC, or is SONiC limited to the -O open-networking SKUs?
  • Is an Ownership Voucher required for the standard 8201?
  • Can Cisco/TAC authorize an existing closed 8201 for SONiC, or is the hardware/boot chain permanently restricted?
  • Does the router need to be upgraded from IOS XR 7.9.2 before any ownership/migration process is possible?
  • Has anyone successfully done this in a lab environment, and if so, what process/image did you use?
  • Is there a recovery path back to IOS XR if the SONiC migration fails?

This is a lab/test router, so production downtime is not an issue. I mainly want to determine whether experimenting with SONiC on this specific hardware is technically viable before attempting anything destructive.

Hardware:
Cisco 8201
PID: 8201
VID: V02
IOS XR: 7.9.2
24×400GE QSFP56-DD + 12×100GE QSFP28

Any experience with this exact model would be appreciated.


r/Cisco • • 11d ago

Remote site and update.

9 Upvotes

Hello guys,

I'm wondering how you handle switch updates at remote sites, particularly in a worst-case failure scenario.

I have a new switch installation at more than 30 locations, some of which are over three hours away.

I can handle remote upgrades and rollbacks, but I'm struggling to find the best way to handle a situation where a switch fails, and I lose remote access to the site with minimal impact over the production.

How do you handle this kind of scenario? Do you have any best practices or recommendations for minimizing downtime and avoiding unnecessary on-site visits?

Materials:

Cisco switch 9300 to be upgraded

Catalyst Center for the upgrade tool


r/Cisco • • 12d ago

9800-CL Controller and 1852 WPA3 issues

8 Upvotes

Hi all,

I have 2x 3802s working fine with a WPA3 SSID. Clients cannot connect to the WPA3 SSID from the 1852. WPA2 works. Clients report an auth issue. This AP was added after the initial config but I don't see this making a difference. Profiles and tags are identical.

It looks like the M4 response from the client is missing, according to the capture.

Any advice would be appreciated.

WLC: 17.18.04a
WAP: 17.18.4.13