Brocade MLX Series and NetIron Family (Supporting Multi-Se Manual de usuario descargar pdf (Pagina 13)

Brocade MLX Series and NetIron Family Documentation Updates 5

53-1003301-07

Telemetry Solutions

The following section is an update to the Telemetry Solutions Chapter in the Multi-Service Ironware

Administration Guide.

The update provides information about recommended baseline configuration and scaling

limitations for telemetry solutions.

Scaling limitations

• 400 (IPv4 and IPv6 combined) route-map instances per interface.

- Valid instance is a route-map instance with the permit option and with a valid ACL (ACL is

present in configuration).

- Exceeding this limit results in first come first applied behavior on the port.

- User should redesign their route-map if this limit is exceeded for proper functioning.

• 200 IPv6 ACLs

- 20480 IPv6 clauses that can be present in the configuration.

• IPv4 ACL limitations have not changed.

• At maximum scale, this configuration may take up to 30 to 45 minutes to bind ACLs used in the

route-maps to the ingress interfaces. Traffic is flooded to all VLAN 1 ports during that time.

• User should execute the show cam-partition usage command under the Rule item, to check if it

will accommodate the application of the route-map on the desired number of ports on each

tower.

• Usage of transparent-hw-flooding (TVF) and transparent-hw-flooding lag-load-balancing (TVF

LAG LDB) is best effort, and may result in data loss for bursty streams.

• Usage of per-packet load balancing on LAGs used for TVF LAG LDB is not supported.

• Dynamic and keep-alive LAGs are not supported with TVF LAG LDB.

• If the SFMs are operating in “normal mode”, the number of TVF LAG LDB instances must not

exceed the following values. Run the show vlan tvf-lag-lb command:

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 61 62

Sin comentarios

Brocade MLX Series and NetIron Family (Supporting Multi-Se Manual de usuario Pagina 13