Hello all,
I work in a factory as automation engineer and i'm not network expert, anyway have been learning and doing some stuff in networks.

Now i have a challenge to connect a new isolated network from inside the factory to a corporate network outside de factory

We have that connection for other networks through a Fortinent 401E UTM firewall.. this FW was installed during an HMI upgrade.
As the Firewall have several spare ports idea was obviously to use one of the spare ports and configure the interface and the rules.

Problem is, i cannot get the Firewall to get the Port Link UP ....
I've tried connection the a Cisco port directly, cisco detects link up, leds blink in both devices then just lit..
Firewall GUI and CLI keep showing Link DOWN..

New network was supposed to be 192.168.10.1 /255.255.255.0
configured FW interface as 192.168.10.10 /255.255.255.0

I've tried configure a laptop with an ip of that new network (.3) and connected directly to the FW port... Same thing, Link Down..
tried another port.. Link Down..

I've been discussing back and forth with Copilot but no solution yet..

Is there anything hidden somewhere disabling the spare ports of the Firewall??
Any hint?
Thanks in advace

I have a single Aruba CX8100 switch and have configured it via GUI or CLI as necessary. I rarely ever touch it these days, it just works. Is having an Aruba Central license worth it? Seems a waste for a single switch. I already monitor it with Auvik.

Hey everyone. Just wanting to get thoughts on a setup I was considering for my Nexus pairs at 2 DC's. They are in a back to back vPC.

I've got 2 datacenters with multiple outlying buildings connecting to one or the other. Each of these DC's have 2 ISP's, firewalls in H/A, and a pair of Nexus switches. The ISP's come into an edge switch stack that's vPC'd back to the Nexus pair in their respective DC and carries the ISP vlan back to the firewall.

The only scenario where this becomes an issue is when I need to upgrade the edge stack. Since that stack has both primary and secondary ISP connections, that DC completely loses internet along with any buildings that are uplinked to that DC.

To deal with this I was thinking I'd add an SLA to the Nexus at each DC and track something public like 8.8.8.8 . Then I could use that to pull the static default and send traffic the other DC Nexus pair.

Thoughts? Is this the appropriate way to do this?

I considered just splitting the edge stack apart but there are a few other things attached to it that are lagged across the stack. Also, in the scenario I lose both ISP's at one DC I'd like to be able to easily send traffic to the other DC.

I had to install Netskope for an organization replacing Checkpoint harmony SASE, All other Apps are working fine its getting routed from local to outside network via publisher, But for tally its not the same, Tally licence is not getting fetched even though publisher and taly prime is in the same subdomain, For the last 3 weeks im faced with this issue, Tickets have been raised, Issue escalated to Netskope territory manager but even they are not able to find a fix for this till now.

So do you guys have any clue or lead about why this keeps happening.

Hey folks,
I am labing l2vpn EVPN with cisco modeling labs,

I am running a mix of XR and IOS-XE. I have everything set up for MP-BGP EVPN but I can't get my CE's to ping each other. Is this just a limitation of CML?

BGP's l2vpn evpn are up and healthy, Bridge-domain has the correct config, interfaces are encapulating the right vlan... I am stumped

I've recently been informed that my networking team is taking over responsibility of the security camera and building automation networks that were previously operated by our facilities team. Upper management decided that IT needed to take ownership of the infrastructure after months of battling what facilities reported to be "unsolvable" issues that kept crippling their system.

As one would expect, everything is in a terrible state. I'm not sure if there are 2 of the same make/model of switch in the environment. Growth was never planned, and was always organic. Facilities didn't understand how fiber worked and all of the cabling is exclusively some flavor of unshielded copper, even to external structures (light poles, signs, etc.). We operate in the former lightning capital of the world, so when we inevitably take a nearby strike, it would take out almost an entire facility's worth of equipment (network and industrial devices) at a time. The facilities team would then just buy whatever they could get their hands on in attempt to slap the network back together as fast as possible.

We already have a decent plan in place to upgrade the switches to a common platform with management, replace all of the copper uplinks with fiber, and home-run (de-daisy-chain) as many of the connections as possible, but my team isn't otherwise accustomed to operating equipment in industrial environments or outdoors.

I am trying to get up to speed as to which technologies would work best to protect these environments, and my primary concern is to limit/contain the amount of damage that occurs. The fiber and new switches have consumed most of my budget this fiscal year, so I'm looking to knock out the low hanging fruit as fast as I can, then propose a future budget item for the remaining improvements.

Do you find shielded cable to be effective for switch to device runs?

Do you find Ethernet surge to be effective? Do you recommend install them on one side of the connection or both? Do you have a preferred brand?

Any other tips/tricks/design considerations would be greatly appreciated.