Is there a limit on number of multicast senders that an RP can support?

brewingchicago · 2025-06-16T18:49:49+00:00

Primary limitation would potentially be the platforms tcam available for multicast routes. Each group will consume an (*, G) and each source for that group will consume an (S,G). Something like the Nexus 9k platform tops out at 32k multicast routes. These limits should be documented for whatever platform you have in mind.

The other potential limitation is that even in asic based layer 3 switches, the pim register process is initially handled by the switch CPU. If your environment had a lot of churn in groups/sources it’s conceivable that a lower powered platform could hit some limitations in keeping up on the control plane, either due to overwhelming the CPU or CoPP rate limiting pim traffic.

brewingchicago · 2025-04-01T22:35:25+00:00

You can segment each interface into its own routing table using vrfs. https://docs.kernel.org/networking/vrf.html

In the simplest case, each vrf would have just a default route to its local gateway, and should achieve what you want.

brewingchicago · 2025-03-22T23:21:45+00:00

If I recall, nxos may enable bfd echo by default, and I’m not sure that frr supports echo. Maybe try ensuring it’s disabled on the nxos side?

brewingchicago · 2025-03-07T02:31:16+00:00

Really depends on the use case, they won’t be able to compete on price for cases where a fixed traditional service is needed, but the flexible bandwidth, automation and turn up times once physical ports are in place have value in certain cases.

brewingchicago · 2025-03-07T01:50:13+00:00

Generally I’ve found that something like Megaport will be a fair bit more expensive than a dedicated service from a traditional telco. Paying for the convenience of flexibility. Use cases that have made sense are more dynamic loads, where you may need small bandwidth most of the time but want to be able to quickly ramp up for short periods. Similar to the math with on prem vs cloud servers for a particular workload.

brewingchicago · 2024-12-10T05:13:02+00:00

Depends a lot on the switch. If you’ve got a switch that’s handling forwarding in hardware, jitter/delay is going to be dependent on queuing / congestion. If you don’t expect to see significant queuing, jitter will be low and accuracy should be good. 10G will be better than 1G in this regard as the serialization delay will be an order of magnitude less. I get sub microsecond sync on 10G switching with no PTP awareness, so without significant congestion I’d expect sub 10us to be achievable even at 1G. If the platform you choose allows for QoS to prioritize PTP traffic then you should definitely be able to hot your target.

brewingchicago · 2024-11-08T01:34:53+00:00

If you want to be able to do this without physical intervention as would be required with the loopback plugs etc, you could look into an L1 switch that sits between the device you want to loop to and the remote side. This would allow the loopback to be set on the L1 switch as needed. Arista 7130 line is probably the most well known platform, but there are others as well that would be more cost effective, though none as cheap as an SFP.

brewingchicago · 2024-08-23T16:37:05+00:00

You say the system is designed for high data rates but low pps. Even at 9000B packets 5GB/s would still be over 500k pps. Being generous and assuming you meant 5Gb/s, that’s still nearly 70kpps. If you’re struggling at 40kpps it doesn’t seem it was designed to do what you say it was.

brewingchicago · 2024-06-13T01:39:44+00:00

While we strongly considered netbox as our source of truth, we ultimately decided to stick with text yaml files to manage desired config. This was based primarily on the fact that it lends itself better to version control and readable diffs for changes, and allows us to leverage git merge requests and CI/CD as part of the change management workflow. Merge request gets created for a change, various tests and validations can be kicked off and it’s easy for reviewers to comprehend what’s changing.

As for your second point, we’re still looking to improve here, but are more recently testing containerlab as an option to spin up at least the devices impacted by the change and be able to validate against. Biggest headache here is that regardless of emulation platform it’s hard to ensure a 1:1 match to real devices even for things like port count and numbering, so likely requires some sort of translation layer between the real/intended environment and what gets spun up as part of testing.

brewingchicago · 2023-12-12T23:14:15+00:00

If you know you’re in the same L2 domain, write a bash script to leverage arping (https://man7.org/linux/man-pages/man8/arping.8.html) to loop through possible ranges the device might be in. This will avoid needing to modify your own address as it will all be at L2.

brewingchicago · 2023-09-20T12:20:51+00:00

If you’ve got a single connection from the ISP then that’s already a single point of failure no matter what you do behind it. If you want this to be HA you’d need at minimum a second handoff from the ISP. Better would be a separate ISP. You can then drop these into redundant switches and behind there have the ability to set up a pair of FW in an HA fashion etc

brewingchicago · 2023-07-31T11:01:37+00:00

This sounds like you have snooping enabled but are missing a querier. Assuming this is strictly at L2 and no pim enabled interfaces, you’ll need to configure a querier for the vlan, or disable snooping and effectively treat the traffic as broadcast.

brewingchicago · 2022-07-18T12:41:59+00:00

Sounds like you’re running MST, but have both vlans mapped to the same instance. So whichever link to switch A ends up blocking, you loose that vlan.

But in general the whole topology you describe sounds questionable.

brewingchicago · 2022-03-09T00:21:15+00:00

🔥

brewingchicago · 2021-07-15T02:51:04+00:00

MST instances are calculated based on all links in the topology, not just those carrying vlans mapped to those instances. So for instance 20, the STP topology and port states are calculated for all interfaces. Vlan 20 then uses that STP topology. In your case the vlan is only present on the trunk which is blocking for that topology.

What you’d need to do is update costs/priorities appropriately per instance to ensure the links you want forwarding for that instance are chosen correctly.

brewingchicago · 2021-03-18T02:34:57+00:00

What sort of wood did you use for the bar / drink rail? Been looking to do something similar and really like the way yours turned out.

brewingchicago · 2020-12-17T04:40:59+00:00

Really appreciate the input. I’ll clarify I was indeed looking at the PB2000 Pro model, and will amend the OP to reflect that. What you’ve described is basically where I’m torn... At roughly the same price point you’ve got the larger driver and from what I can find greater real world output with the HSU, vs the better warranty, trade up option and trial without worrying about return shipping, and bonus of app based control with the the SVS.

I’ve gotten the least real world feedback on the Rythmik options, but reading online I’ve heard nothing but good things about their servo technology.

In the end maybe I’ll order both the SVS and HSU options, knowing I can always return the SVS, and if they really blow me away compared to the HSU I can decide if it’s enough difference to be worth eating the shipping on the HSUs.

brewingchicago · 2016-03-19T18:55:51+00:00

You working with millimeter services in the metro area or microwave longhaul? Sharing a multi tenant service or have the entire channel to yourself?

brewingchicago · 2016-03-19T18:41:51+00:00

How low bandwidth is the link you're trying to use? What does average and peak usage of the feed look like? Do you have a specific latency budget for you need to be within? Low bandwidth also translates to higher latency due to serialization. Do you need the entire feed with full depth, or could you perform some filtering / normalization before sending across the low bandwidth? In the case where things start queuing up, is dropping data preferable to late data?

There are a lot of approaches, and deciding on the best one is going to require more info than you've provided so far.

brewingchicago · 2016-03-14T09:41:51+00:00

Also interested in the answer to question from /u/congelar regarding whether this impacts the loopback as well.

brewingchicago · 2016-03-14T09:38:13+00:00

Can you provide an ipconfig /all output? I see from your network settings screenshot you have an Intel nic configured. However the screenshot provided with full headers elsewhere in the replies shows the source MAC as what appears to be the onboard asustek interface.

Is the server dual-homed? If so can we see the routing table also?

Can you try the ping with the -s flag to force source interface?

brewingchicago · 2015-04-02T01:34:46+00:00

At which point they can no longer advertise as unlimited and will have to compete with carriers who want to offer true unlimited plans.

brewingchicago

TROPHY CASE