No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Insufficient slice resource on interface

Publication Date:  2018-09-27 Views:  63 Downloads:  0
Issue Description

Customer configured IPv6 ACL with 20 rules and wanted to apply on physical interfaces. After applying IPv6 ACL on 20 interfaces he received this message: 

Fail to apply SACL 'traffic-filter inbound acl ipv6 name cust-iACL-IPv6-filter', insufficient slice resource on interface XGigabitEthernet0/0/37 of slot 0.


Alarm Information

Fail to apply SACL 'traffic-filter inbound acl ipv6 name cust-iACL-IPv6-filter', insufficient slice resource on interface XGigabitEthernet0/0/37 of slot 0.

Handling Process

1. Every feature is occupying some slices and a slice can have 256 or 512 resources. From the output provided, customer only has one slice available for this feature: traffic filter.

Output below:

  [Poplar-R1-LNPOP-10GEI-AGG-6]display acl resource

Slot  0

XGigabitEthernet0/0/1 to XGigabitEthernet0/0/48

40GE0/0/1

40GE0/0/2

                   Used          Free         Total

----------------------------------------------------------------------------

  VACL             9             1015         1024

 

  IACL Unallocated -             -            256

  IACL Allocated   -             -            3840

    IPv4   ACL     5             251          256

    IPv6   ACL     1050          998          2048

    Srv    ACL     9             503          512

    Sec    ACL     210           814          1024

 

  EACL Unallocated -             -            512

  EACL Allocated   -             -            512

    IPv6   ACL     6             506          512

 

  Ingress Meter    52            4044         4096

  Egress  Meter    0             1024         1024

  Ingress Counter  173           3923         4096

  Egress  Counter  0             1024         1024

 

  Ingress UDF      0             8            8

----------------------------------------------------------------------------

2. In order to check what other features are occupying slices I asked for the below command: 

 [huawei]diagnose

[huawei-diagnose] display fpi resource slot 0 acl group-info create-group

Root Cause

There are many interfaces in which you have applied  traffic-filter; every time when traffic-filter is applied, some ACL resources will be used. So the acl resoures for this feature are not enough; 

Solution

There are many interfaces in which you have applied  traffic-filter; every time when traffic-filter is applied, some ACL resources will be used. So the acl resoures for this feature are not enough.


 



 

Ifp Group[46]:created  Group-pri:22 DelFlag:1 Group mod:Double

               Group All Num:512 Free Num:8 Default Entry Num:0

               Group-Bitmap:00000000 00000000 0000005c 19c83dfb 83c3eea8

               Fp-Info:6-3-2-1 0-0-0-0

               Service-Info:SACL_PORT[GID:153]

 

Customer can remove all the ‘traffic-filter’ commands, and configure traffic policy, below is the example:

 

//configure traffic classifier IPv6_filter_policy

traffic classifier IPv6_filter_policy

         if-match ipv6 acl cust-iACL-IPv6-filter

 

//configure traffic behavior IPv6_filter_policy

traffic behavior IPv6_filter_policy

 

//configure traffic policy IPv6_filter_policy

traffic policy IPv6_filter_policy

         classifier IPv6_filter_policy behavior IPv6_filter_policy

 

//apply the traffic policy IPv6_filter_policy

interface GigabitEthernet0/0/X

         traffic-policy IPv6_filter_policy inbound


END