FreeBSD link aggregation no faster than single link

Question

I am using Angular 9 and Angular material 9.2.4 I am trying to use MatFormField. Below is my app.module.ts

@NgModule({
  declarations: [
    AppComponent,
    LoginComponent,
    RegisterComponent
  ],
  imports: [
    BrowserModule,
    AppRoutingModule,
    BrowserAnimationsModule,
    MatToolbarModule,
    MatFormFieldModule,
    MatInputModule

  ],
  providers: [],
  bootstrap: [AppComponent],
})
export class AppModule { }

and this is my component.html

<p>
    <mat-form-field appearance="standard">
      <mat-label>Standard form field</mat-label>
      <input matInput placeholder="Placeholder">
      <mat-hint>Hint</mat-hint>
    </mat-form-field>
</p>

But my form feild looks like

and I am having error in the console. Kindly suggest what I am missing in the configuration

Solution

What is the load balancing algorithm in use on both the system and the switch?

All my experience with this is on Linux and Cisco, not FreeBSD and SMC, but the same theory still applies.

The default load balancing mode on the Linux bonding driver's LACP mode, and on older Cisco switches like the 2950, is to balance based on MAC address only.

This means if all your traffic is going from one system (file server) to one other MAC (either a default gateway or a Switched Virtual Interface on the switch) then the source and destination MAC will be the same, so only one slave will ever be used.

From your diagram it doesn't look like you're sending traffic to a default gateway, but I'm not sure if the test servers are in 10.0.0.0/24, or if the test systems are in other subnets and being routed via a Layer 3 interface on the switch.

If you are routing on the switch, there's your answer.

The solution to this is to use a different load balancing algorithm.

Again I don't have experience with BSD or SMC, but Linux and Cisco can balance either based on L3 information (IP address) or L4 information (port number).

As each of your test systems must have a different IP, try balancing based on L3 information. If that still doesn't work, change a few IPs around and see if you change the load balancing pattern.

Comments

[Admin]

My initial guess would be it could be something related to the hashing algorithm being used, but would need to close inspect the packets. If that doesn't help, try to change the TCP window iperf uses to something bigger. The lagg(4) man page has something about disabling the hash offloading, you may want to try that.

[Chellappan வ]

Can you rebuild your application and check?

[Greenbox]

Thanks It Worked.But what is the point of rebuilding? I hav also used material toolbar. The changes got reflected instantly. Why not for form field component?

[Darpan]

Does this answer your question? mat-form-field must contain a MatFormFieldControl

[Chellappan வ]

@Greenbox sometime hot refresh will not for some reason.

[Greenbox]

No. It might be because MatInput Module. But I was getting this error even after importing the MatInputModule also. After rebuilding the errors are no more

[Warren Young]

Thanks, but your guess is incorrect. The HP switch configuration shown above says it's doing L3 balancing. Also, these are not L3 "switches," a.k.a. routers. They only have enough L3 smarts to do IGMP snooping and LACP. The only true router in the building is the one in the Internet gateway, which is off on a side leg from the perspective of the test diagram above.

[suprjami]

It doesn't matter if this is a L2 or L3 switch, this is the configuration which the bond uses to load balance which is a different thing. The switch itself might not have the smarts to route between VLANs or to manipulate traffic beyond L2, but the bond's load balancing algorithm (probably) can.

[suprjami]

I see above your switch says Load Balancing Method: L3-based (default). Try changing this.