7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
System management
• A chunk is allocated for use by SAP ingress ACL entries that use ipv6-64-bit criteria when the user
associates an ingress ACL policy (with ipv6-64-bit-criteria entries defined) with a SAP. Because the max
keyword is specified, the system can allocate more chunks, if a chunk is available for use.
In this example, as there are no more chunks available, ipv6-64-bit criteria cannot allocate more than
1 chunk (even if the max keyword is specified). The system fails the configuration when the number of
ACL entries with ipv6-64-bit criteria exceeds the limit of one chunk allocated to SAP ingress ACL match
(that is, the system does not allocate more than the configured limit of 3 chunks = 1 for mac-criteria + 1
for ipv4-criteria + 1 for ipv6-64-bit criteria).
• The system fails any attempt to use SAP ingress ACLs with ipv6-128 bit match criteria (and the other
combinations listed above), because the user has disabled these criteria.
In Example: 2, the user can run no ipv4-match-enable command to disable the use of ipv4-criteria. The
system checks for SAPs that use ipv4-criteria and if found, fails the command; otherwise, the chunk freed
for use with either mac-criteria or ipv6-64-bit criteria. The entire chunk is allocated to mac-criteria if the first
SAP that needs resources requests for mac-criteria and no entries in the chunk are already allocated to
mac-criteria, which leaves no resources for use by ipv6-64-bit criteria. In the same way, the entire chunk is
allocated to ipv6-64-bit criteria, if the first SAP that needs resources requests for ipv6-64-bit criteria and no
entries in the chunk are already allocated to ipv6-64-bit criteria, which leaves no resources for use by mac-
criteria.
6.8.4 7210 SAS-R6 and 7210 SAS-R12 configuration guidelines for system resource
profile
The following configuration guidelines apply to 7210 SAS-R6 and 7210 SAS-R12:
• The user can change the system-resource policy attached to a card/IMM in the following cases:
– when the card/IMM state is unprovisioned
– when the card/IMM is provisioned but not equipped
– when the card/IMM is provisioned and equipped, but there is a mismatch between the two
• Upon provisioning the card, subsequent to attaching a new system-resource policy, the parameters
specified in the policy are used (including any boot-time parameters).
• If the card is provisioned and equipped, and any boot-time parameter is changed in the system-
resource policy, the user must issue the card reset command for all cards that are using the policy or
reboot the chassis, for the policy change to take effect.
6.9 System configuration process overview
The following figure shows the process to provision basic system parameters.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
291
SPACER TEXT
To Next Page
Loading...