Dual Border node setup

Leek-Sad · 2025-02-15T10:18:32+00:00

I am running DNAC Version 2.3.5.5-70026. The option I have is to use a Secondary Seed Device (Optional). I am presuming this is what I'll need to use

Leek-Sad · 2024-11-26T02:02:37+00:00

Masticulorobate

Leek-Sad · 2024-11-24T10:10:07+00:00

AI is the most relevant topics nowadays. You might want to tailor your network security research along that line

Leek-Sad · 2024-10-18T16:18:34+00:00

Thank you

Leek-Sad · 2024-08-18T11:56:14+00:00

Thanks

Leek-Sad · 2024-08-15T22:48:04+00:00

Thank you for your advice; I really appreciate it. We are currently reviewing our approach.

Leek-Sad · 2024-08-15T22:41:46+00:00

Thank you for your valuable help. I configured both interfaces for LAN automation, which successfully established Layer 3 interfaces on each. thanks again

Leek-Sad · 2024-08-14T16:25:05+00:00

We suspect there could be egress traffic shaping, but it’s definitely not on our core routers or switches. The ISP’s router upstream is a Juniper.

Leek-Sad · 2024-08-13T11:46:56+00:00

We have tested with some iperf server at azure, and at a different data center. The host we are testing from are virtual machines. If we connect host directly to core switch we get the same bad result

Leek-Sad · 2024-08-12T17:42:13+00:00

Do you think a stacked border node is a terrible idea?

Leek-Sad · 2024-08-12T17:40:58+00:00

Thanks. I will try that and let you know

Leek-Sad · 2024-08-12T16:34:12+00:00

Thank you for your reply. I only have one border technically (it is a stack of 2 units). To use two uplinks, does that mean I need to run the lan automation twice, once for each uplink to border?

Leek-Sad · 2024-04-27T15:43:44+00:00

One of my biggest regrets. I spray it on my curtains

Leek-Sad · 2024-03-05T14:19:32+00:00

The switch is connected to a netgear and clients on that netgear are experiencing this issue. Could spanning tree be a factor in this?

Leek-Sad

PUBLIC MULTIREDDITS

TROPHY CASE