Brocade Multi-Service IronWare Administration Guide (Supporting R05.6.00) User Manual
Page 75
Multi-Service IronWare Administration Guide
57
53-1003028-02
Configuring profiles with a zero-size IPv4 or IPv6 ACL
2
NOTE
You must write this command to memory and perform a system reload for this command to take
effect.
Configuring profiles with a zero-size IPv4 or
IPv6 ACL
When a profile is configured to a zero-size IPv4 or IPv6 ACL, the minimum value of 512 for IPv4, and
the minimum value of 128 for IPv6 is disabled.
If the system-max value for multicast is configured, and you select a value of 0 for IPv4 or IPV6 ACL,
the system-max value will be ignored. There is minimal checking for errors. The following warning
message is displayed.
NOTE
You must write this command to memory and perform a system reload for this command to take
effect.
The system-max value is retained in the configuration so that it can be reused later when you want
to change the CAM profile.
Maintaining system-max configuration with
available system resources
When system-max values are configured, the Brocade system checks for available system
resources. The system resources are required in order to maintain dynamic memory allocation.
System-max values are checked at the configuration time, and at the bootup time. If there are
insufficient system resources available on the Management Module, this will cause the
configuration to be rejected during card bootup. On the Interface Module, insufficient system
resources will lead to failure in booting up the card.
Brocade(config)#system-max ipv6-mcast-cam 1000
Reload required. Please write memory and then reload or power cycle.
Failure to reload could cause system instability on failover.
Newly configured system-max will not take effect during hitless-reload.
Brocade(config)#cam-partition profile mpls-vpls-2
Warning - Changing to a profile with zero Ipv6 ACL CAM size, ignoring system-max
value check and minimum-guarantee checks.
Reload required. Please write memory and then reload or power cycle.
Failure to reload could cause system instability on failover.
Newly configured system-max will not take effect during hitless-reload.