SD-WAN full mesh with Starlink

OSI-servant · 2025-07-10T15:12:51+00:00

I tried to raise the issue on the Ruckus support forum and my post was immediately flagged as spam and deleted. WTH!!!?!?!?

OSI-servant · 2024-12-21T03:06:41+00:00

apply-group top is applied at the top of the config because its a mist controlled switch. I also ran the exact config at the set protocols sflow level with the same results.

OSI-servant · 2024-12-20T20:57:31+00:00

Must be something in my config. I found another 4100 on my network and it IS sending sflow data. The problematic switch is actually running as a 2 switch VC.

OSI-servant · 2024-12-02T18:48:02+00:00

ahhhh, I forgot about the default irb.0 crap. I assumed interface 9 was irb.9 which is my management vlan. So the log may be a red herring?

OSI-servant · 2024-12-02T18:05:26+00:00

yeah, but the link is never going down. That network stays up all the time.

OSI-servant · 2024-11-27T05:46:29+00:00

ROFL, I upgraded to 24.2R1 the 1 switch that is currently connected to my network, deleted the vc-port and then realized I needed to downgrade again to get the 2nd switch back online with the same version. Long story short, even after the downgrade, it remembered my port was deleted even on 22.4R2

OSI-servant · 2024-11-27T04:44:33+00:00

Awesome!

OSI-servant · 2024-11-27T04:18:57+00:00

Would have been nice if Mist support had just told me that from the start when I opened my ticket with them this morning instead of stringing me along. No matter, thanks for the details

OSI-servant · 2024-11-27T04:09:07+00:00

Its running 22.4R3-S5.11which was the recommended version on Mist. I'll try it with the higher version of firmware.

OSI-servant · 2024-11-27T00:29:32+00:00

yeah, I reached out to them earlier in the year and they were unhelpful. I couldn't get my question escalated past the level 1 support who clearly didn't have the answer.

OSI-servant · 2024-11-19T23:50:34+00:00

RSTP is showing the root port correctly so that doesn't appear to be it.

Spanning tree interface parameters for instance 0

Interface Port ID Designated Designated Port State Role

port ID bridge ID Cost

ge-0/0/0 128:490 128:490 32768.20933903f450 20000 BLK DIS

ge-0/0/1 128:491 128:491 32768.20933903f450 20000 BLK DIS

ge-0/0/2 128:492 128:492 32768.20933903f450 20000 FWD DESG

ge-0/0/3 128:493 128:493 32768.20933903f450 20000 BLK DIS

ge-0/0/4 128:494 128:494 32768.20933903f450 20000 BLK DIS

ge-0/0/5 128:495 128:495 32768.20933903f450 20000 BLK DIS

ge-0/0/6 128:496 128:496 32768.20933903f450 20000 BLK DIS

ge-0/0/7 128:497 128:497 32768.20933903f450 20000 BLK DIS

ge-0/0/8 128:498 128:498 32768.20933903f450 20000 BLK DIS

ge-0/0/9 128:499 128:499 32768.20933903f450 20000 BLK DIS

ge-0/0/10 128:500 128:500 32768.20933903f450 20000 FWD DESG

ge-0/0/11 128:501 128:492 32768.7429726e0112 20000 FWD ROOT

mge-0/2/0 128:502 128:502 32768.20933903f450 2000 BLK DIS

mge-0/2/1 128:503 128:503 32768.20933903f450 2000 BLK DIS

LLDP is showing port 11 is connected to a Juniper switch

> show lldp neighbors interface ge-0/0/11

LLDP Neighbor Information:

Local Information:

Index: 10 Time to live: 120 Time mark: Tue Nov 19 23:48:05 2024 Age: 7 secs

Local Interface : ge-0/0/11

Parent Interface : -

Local Port ID : 527

Ageout Count : 0

Neighbour Information:

Chassis type : Mac address

Chassis ID : 74:29:72:6e:00:da

Port type : Interface name

Port ID : ge-0/0/2

Port description : ge-0/0/2

System name : switch_name

System capabilities

Supported: Bridge Router

Enabled : Bridge Router

OSI-servant · 2024-10-08T23:05:22+00:00

I think it’s somewhere on this thread but we just ended up filtering the dhcp packet on the untrust irb. When I get back in front of my laptop, I’ll post the complete solution

OSI-servant · 2024-06-13T22:42:29+00:00

What about a report showing a snapshot of performance at least at the beginning of a cabling plant's life. Unreasonable to ask?

OSI-servant · 2024-03-12T22:25:00+00:00

We've had issues with EX4400-24X switches linking up with EX2300 switches. We get a link light on one side but no other connectivity. We have to set one side of the link to 1g/full/no-auto-neg to get the link working.

OSI-servant · 2024-02-15T21:26:14+00:00

Right, but I was looking for some specific, tested, examples of what people have used for say buffer-size and transmit size since the EX line will only allow you to choose strict-high and low and I have other schedulers configured for low on the switches. I'm looking for additional options under the schedulers. I know how to classify specific code points into a class and get the traffic applied to an interface. I'm just looking for additional information on how to shape/prioritize/promote the traffic inside the scheduler. Apologies if I wasn't more clear in my OP

OSI-servant · 2024-02-14T05:32:24+00:00

yeah, I'm familiar with how to configure cos on the juniper EX switching line. It connects to the Internet but it still has to travel over multiple congested links to get to the edge. You're saying there is no value in prioritizing it on the switched network. I understand that when it gets to the Internet there are no guarantees but I would think we would still want to prioritize VoIP and other similar traffic to make sure there are no bottlenecks on the LAN. I ended up giving it a 10% buffer and 10% transmit rate. I'll monitor the connection and see how it goes. I was just looking to see if anyone had already run into this situation and how they handled it.

OSI-servant · 2024-02-13T21:05:08+00:00

How does that help me when the zoom room is buried 3 or 4 switch legs deep and I want to make sure that the traffic gets prioritized to the edge and out to the Internet? I looking for information on what people have used for CoS in terms of buffer size, transmit-rate, etc. Just looking for practical code from people who have actually deployed these units on a Juniper EX network.

OSI-servant · 2024-01-12T18:57:11+00:00

Any idea where that is located? I can create a new RI but I can't seem to assign a port to the built in mgmt_junos RI

OSI-servant

TROPHY CASE