user: 你是一名网络工程师，请分析这台交换机的日志FIB/2/hwLCfwdResourceOverload_active: The board forwarding engine resources were overloaded. (EntityPhysicalIndex=[EntityPhysicalindex], EntPhysicalIndex=[EntPhysicalindex], EntPhysicalName=[EntPhysicalName], Slot=[SlotStr], Reason=[ReasonId], ReasonDescription=[Reason]) VS模式下，该日志仅在Admin VS支持。

assistant: 单板转发引擎资源过载。可能原因
·原因1：The number of established MPLS connections (TE) exceeded the specification of the forwarding engine resources（建立的MPLS连接（TE）数量超过了转发引擎资源的规格。）
·原因2：The number of IPv4 FIBs exceeded the specification of the forwarding engine resources（FIB V4数量超过了转发引擎资源的规格。）
·原因3：The number of IPv6 FIBs exceeded the specification of the forwarding engine resources（FIB V6数量超过了转发引擎资源的规格。）
·原因4：The number of ARPs exceeded the specification of the forwarding engine resources（ARP表数量超过转发引擎资源的规格。）
·原因5：The number of IPv6 NDs exceeded the specification of the forwarding engine resources（IPv6 ND数量超过了转发引擎资源的规格。）
·原因6：The number of enabled statistics exceeded the specification of the forwarding engine resources（已经使能的统计规格超过了转发引擎资源的规格。）
·原因7：The numbers of the applied traffic classification-based policies and CARs exceeded the specification of the forwarding resources（应用的流分类策略、CAR超过转发引擎资源的规格。）
·原因8：The number of established L2VPN connections exceeded the specifications of the forwarding engine resources（建立的L2VPN连接数量超过了转发引擎资源的规格。）
·原因9：The number of multicast replication downstream interfaces exceeded the specification of the forwarding engine resources（建立的组播复制出接口数量超过了转发引擎资源的规格。）
·原因10：The number of BFD ACLs exceeded the specification of the forwarding engine resources（BFD申请ACL数量超过了转发引擎资源的规格。）
·原因11：The number of IPv4 multicast FIBs exceeded the specification of the forwarding engine resources（组播FIB V4数量超过了转发引擎资源的规格。）
·原因12：The number of IPv6 multicast FIBs exceeded the specification of the forwarding engine resources（组播FIB V6数量超过了转发引擎资源的规格。）
·原因13：The number of forward tokens in the board space exceeded the specifications of the forwarding engine resources（单板空间token的数量超过了转发引擎的规格。）
·原因14：The number of FVRFs exceeded the specifications of the forwarding engine resources（转发FVRF的数量超过了转发引擎的规格。）
·原因15：The number of NDIndex exceeded the specifications of the forwarding engine resources（ND索引的数量超过了转发引擎的规格。）
·原因16：The number of Tunnel Index exceeded the specifications of the forwarding engine resources（Tunnel索引的数量超过了转发引擎的规格。）
·原因17：The number of BFD Index exceeded the specifications of the forwarding engine resources（BFD索引的数量超过了转发引擎的规格。）
·原因18：The number of VPLS LearnId exceeded the specifications of the forwarding engine resources（VPLS LearnId的数量超过了转发引擎的规格）
·原因19：The number of broadcast domain Index exceeded the specifications of the forwarding engine resources（广播域索引的数量超过了转发引擎的规格）
·原因20：The number of NS indexes exceeded the specifications of the forwarding engine resources（Ns索引的数量超过了转发引擎的规格）
·原因21：The number of Ring Index exceeded the specifications of the forwarding engine resources（Ring索引的数量超过了转发引擎的规格）
·原因25：The number of MLID exceeded the specification of the forwarding engine resources.（组播叶子ID的数量超过了转发引擎的规格）
·原因26：The number of trill nhpIndex exceeded the specifications of the forwarding engine resources（Trill下一跳资源的数量超过了转发引擎的规格。）
·原因27：The host table prefix resource usage has exceeded 90%.（接口板上主机表资源使用率达到90%。）
·原因28：The route table prefix resource usage has exceeded 90%.（接口板上路由表资源使用率达到90%。）
·原因29：The next hop resource usage for equal-cost routes has exceeded 90%.（接口板上ECMP资源使用率达到90%。）
·原因30：The Layer 3 interface table resource usage has exceeded 90%.（接口板上三层接口表资源使用率达到90%。）
·原因31：The next hop resource usage has exceeded 90%.（接口板上下一跳资源使用率达到90%。）
·原因32：The tunnel decapsulation table resource usage has exceeded 90%.（接口板上隧道解封装表资源使用率达到90%。）
·原因33：The number of QINQ tag pairs exceeds the specification of the forwarding engine resources.（Qinq终结子接口数目超过转发引擎资源的规格。）
·原因35：Certain IPv4 full rules cannot be delivered, resulting in interruption of some services refer to ipv4 full rulse lose efficacy.（IPv4精确规则空间不足。）
·原因36：Certain IPv4 mask rules cannot be delivered, causing involved services to fail to take effect.（IPv4掩码规则空间不足。）
·原因37：Certain IPv6 full rules cannot be delivered, causing involved services to fail to take effect.（IPv6精确规则空间不足。）
·原因38：Certain IPv6 mask rules cannot be delivered, causing involved services to fail to take effect.（IPv6掩码规则空间不足。）
·原因39：Certain characteristic code rules cannot be delivered, causing involved services to fail to take effect.（特征码规则空间不足。）
·原因40：Certain complex rules cannot be delivered, causing involved services to fail to take effect.（复合规则规则空间不足。）
·原因41：Certain Tcp Flag rules cannot be delivered, causing involved services to fail to take effect.（TCP Flag规则空间不足。）
·原因42：The number of enabled ccm send numbers exceeded the specifications of the forwarding engine resources（使能的CCM发送实例数目超转发引擎资源规格。）
·原因43：The number of enabled ccm receive numbers exceeded the specifications of the forwarding engine resources（使能的CCM接收实例数目超转发引擎资源规格。）
·原因44：The number of enabled slm instance numbers exceeded the specifications of the forwarding engine resources（使能的1731单端丢包统计实例数目超转发引擎。）
·原因45：The number of enabled 1dm instance numbers exceeded the specifications of the forwarding engine resources（使能的1731单向时延统计实例数目超转发引擎资源规格。）
·原因46：The number of enabled 2dm instance numbers exceeded the specifications of the forwarding engine resources（使能的1731双向时延统计实例数目超转发引擎资源规格。）
·原因47：The IPv6 route table prefix resource usage has exceeded 90%.（接口板上IPv6路由表资源使用率达到90%。）
·原因48：The number of IPv4 multicast group flow statistic ID exceeded the specifications of the forwarding engine resources（IPv4 组播流量统计ID数量超过了转发引擎的规格。）
·原因49：The number of IPv6 multicast group flow statistic ID exceeded the specifications of the forwarding engine resources（IPv6 组播流量统计ID数量超过了转发引擎的规格。）
·原因50：The number of nhp numbers exceeded the specifications of the forwarding engine resources（申请的负载分担表数量超过转发引擎资源的规格。）
·原因51：The number of netstream Index numbers exceeded the specifications of the forwarding engine resources（申请的NetStream接口数量超过硬件资源的规格。）
·原因52：The number of enabled dlm instance numbers exceeded the specifications of the forwarding engine resources（使能的1731双端丢包检测实例数量超转发引擎资源规格。）
·原因53：The number of IPv4 BGP statistic ID exceeded the specifications of the forwarding engine resources（IPv4 BGP属性表过载。）
·原因54：The number of IPv6 bgp statistic ID exceeded the specifications of the forwarding engine resources（IPv6 BGP属性表过载。）
·原因55：The number of Link Layer Encapsulation database exceeded the specification of the forwarding engine resources（链路层封转表资源过载。）
·原因57：The number of Large Exactly Match database exceeded the specification of the forwarding engine resources（精确匹配表资源过载。）
·原因58：The number of Logical Interfaces exceeded the specification of the forwarding engine resources（逻辑接口表资源过载。）
·原因59：The number of Mac Multicast Index exceeded the specification of the forwarding engine resources（MAC组播复制索引表资源过载。）
·原因61：The number of applied BGPFLOW VTCAM resources exceeded the specification of the forwarding engine resources（BGPFLOW TCAM资源不足）
·原因62：The number of ACL Group exceeded the specification of the forwarding engine resources（ACL组资源不足。）
·原因63：The number of Meter exceeded the specification of the forwarding engine resources（meter资源过载。）
·原因64：The number of Counter exceeded the specification of the forwarding engine resources（Counter资源过载。）
·原因65：The number of Outbound ACL Entry exceeded the specification of the forwarding engine resources（下行ACL规则资源不足。）
·原因66：The number of Outbound ACL Group exceeded the specification of the forwarding engine resources（下行ACL组资源不足。）
·原因67：The number of Outbound Meter exceeded the specification of the forwarding engine resources（下行meter资源过载。）
·原因68：The number of Outbound Counter exceeded the specification of the forwarding engine resources（下行Counter资源过载。）
·原因69：The number of Multicast Index exceeded the specification of the forwarding engine resources（组播复制表索引资源过载。）
·原因70：The number of IPFPM loss-measure continual enable or delay-measure continual enable numbers exceeded the specifications of the forwarding engine resources.（系统配置的IPFPM统计规格减少到低于系统支持的规格。）
·原因71：The number of bind table exceeded the specifications of the forwarding engine resources.（DHCP SNOOPING 绑定表的数量超过了转发引擎的规格。）
·原因72：ACL failed to be delivered.（ACL下发失败。）
·原因73：The number of ARP entries exceeded 95% of the forwarding engine's resource specification.（ARP数量超过了转发引擎资源的规格的95%。）
·原因103：The number of AT indexes exceeds the specifications of the forwarding engine resources.（AT索引的数量超过了转发引擎的规格。）
·原因104：The number of flexible access sub-interfaces exceeds the specification of the forwarding engine resources.（Flex灵活接入子接口数目超过转发引擎资源的规格。）
·原因105：The number of Inbound flow-wred exceeded the specification of the forwarding engine resources（flow-wred 上行表项资源不足。）
·原因106：The number of Outbound flow-wred exceeded the specification of the forwarding engine resources（flow-wred 下行表项资源不足。）
·原因109：The number of Inbound flow-queue wfq exceeded the specification of the forwarding engine resources.（flow-queue wfq 上行资源不足。）
·原因110：The number of Outbound flow-queue wfq exceeded the specification of the forwarding engine resources.（flow-queue wfq 下行资源不足。）
·原因111：The number of Inbound flow-queue cbs exceeded the specification of the forwarding engine resources.（flow-queue cbs 上行资源不足。）
·原因112：The number of Outbound flow-queue cbs exceeded the specification of the forwarding engine resources.（flow-queue cbs 下行资源不足。）
·原因113：The number of Inbound flow-queue pbs exceeded the specification of the forwarding engine resources.（flow-queue pbs 上行资源不足。）
·原因114：The number of Outbound flow-queue pbs exceeded the specification of the forwarding engine resources.（flow-queue pbs 下行资源不足。）
·原因115：The number of Inbound user-queue exceeded the specification of the forwarding engine resources.（user-queue 上行资源不足。）
·原因116：The number of Outbound user-queue exceeded the specification of the forwarding engine resources.（user-queue 下行资源不足。）
·原因117：The number of Inbound user-queue template exceeded the specification of the forwarding engine resources.（user-queue template 上行模板资源不足。）
·原因118：The number of Outbound user-queue template exceeded the specification of the forwarding engine resources.（user-queue template 下行模板资源不足。）
·原因119：The number of Inbound service-template exceeded the specification of the forwarding engine resources.（service-template 上行模板资源不足。）
·原因120：The number ...处理步骤
·原因1：The number of established MPLS connections (TE) exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因2：The number of IPv4 FIBs exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因3：The number of IPv6 FIBs exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因4：The number of ARPs exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因5：The number of IPv6 NDs exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因6：The number of enabled statistics exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因7：The numbers of the applied traffic classification-based policies and CARs exceeded the specification of the forwarding resources 
请联系技术支持工程师。
·原因8：The number of established L2VPN connections exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因9：The number of multicast replication downstream interfaces exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因10：The number of BFD ACLs exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因11：The number of IPv4 multicast FIBs exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因12：The number of IPv6 multicast FIBs exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因13：The number of forward tokens in the board space exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因14：The number of FVRFs exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因15：The number of NDIndex exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因16：The number of Tunnel Index exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因17：The number of BFD Index exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因18：The number of VPLS LearnId exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因19：The number of broadcast domain Index exceeded the specifications of the forwarding engine resources 
请检查广播域配置的数量是否超过业务规格。
·原因20：The number of NS indexes exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因21：The number of Ring Index exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因25：The number of MLID exceeded the specification of the forwarding engine resources. 
请联系技术支持工程师。
·原因26：The number of trill nhpIndex exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因27：The host table prefix resource usage has exceeded 90%. 
请联系技术支持工程师。
·原因28：The route table prefix resource usage has exceeded 90%. 
请联系技术支持工程师。
·原因29：The next hop resource usage for equal-cost routes has exceeded 90%. 
请联系技术支持工程师。
·原因30：The Layer 3 interface table resource usage has exceeded 90%. 
请联系技术支持工程师。
·原因31：The next hop resource usage has exceeded 90%. 
请联系技术支持工程师。
·原因32：The tunnel decapsulation table resource usage has exceeded 90%. 
请联系技术支持工程师。
·原因33：The number of QINQ tag pairs exceeds the specification of the forwarding engine resources. 
请联系技术支持工程师。
·原因35：Certain IPv4 full rules cannot be delivered, resulting in interruption of some services refer to ipv4 full rulse lose efficacy. 
请联系技术支持工程师。
·原因36：Certain IPv4 mask rules cannot be delivered, causing involved services to fail to take effect. 
请联系技术支持工程师。
·原因37：Certain IPv6 full rules cannot be delivered, causing involved services to fail to take effect. 
请联系技术支持工程师。
·原因38：Certain IPv6 mask rules cannot be delivered, causing involved services to fail to take effect. 
请联系技术支持工程师。
·原因39：Certain characteristic code rules cannot be delivered, causing involved services to fail to take effect. 
请联系技术支持工程师。
·原因40：Certain complex rules cannot be delivered, causing involved services to fail to take effect. 
请联系技术支持工程师。
·原因41：Certain Tcp Flag rules cannot be delivered, causing involved services to fail to take effect. 
请联系技术支持工程师。
·原因42：The number of enabled ccm send numbers exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因43：The number of enabled ccm receive numbers exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因44：The number of enabled slm instance numbers exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因45：The number of enabled 1dm instance numbers exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因46：The number of enabled 2dm instance numbers exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因47：The IPv6 route table prefix resource usage has exceeded 90%. 
请联系技术支持工程师。
·原因48：The number of IPv4 multicast group flow statistic ID exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因49：The number of IPv6 multicast group flow statistic ID exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因50：The number of nhp numbers exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因51：The number of netstream Index numbers exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因52：The number of enabled dlm instance numbers exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因53：The number of IPv4 BGP statistic ID exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因54：The number of IPv6 bgp statistic ID exceeded the specifications of the forwarding engine resources 
请联系技术支持工程师。
·原因55：The number of Link Layer Encapsulation database exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因57：The number of Large Exactly Match database exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因58：The number of Logical Interfaces exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因59：The number of Mac Multicast Index exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因61：The number of applied BGPFLOW VTCAM resources exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因62：The number of ACL Group exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因63：The number of Meter exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因64：The number of Counter exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因65：The number of Outbound ACL Entry exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因66：The number of Outbound ACL Group exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因67：The number of Outbound Meter exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因68：The number of Outbound Counter exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因69：The number of Multicast Index exceeded the specification of the forwarding engine resources 
请联系技术支持工程师。
·原因70：The number of IPFPM loss-measure continual enable or delay-measure continual enable numbers exceeded the specifications of the forwarding engine resources. 
请联系技术支持工程师。
·原因71：The number of bind table exceeded the specifications of the forwarding engine resources. 
请联系技术支持工程师。
·原因72：ACL failed to be delivered. 
请联系技术支持工程师。
·原因73：The number of ARP entries exceeded 95% of the forwarding engine's resource specification. 
请联系技术支持工程师。
·原因103：The number of AT indexes exceeds the specifications of the forwarding engine resources. 
请联系技术支持工程师。
·原因104：The number of flexible access sub-interfaces exceeds the specification of the forwarding engine resources. 
请联系技术支持工程师。
·原因105：The number of Inbound flow-wred exceeded the specification of the forwarding engine resources 
检查flow-wred 的配置，对照规格，查看是否超规格。
·原因106：The number of Outbound flow-wred exceeded the specification of the forwarding engine resources 
检查flow-wred 的配置，对照规格，查看是否超规格。
·原因109：The number of Inbound flow-queue wfq exceeded the specification of the forwarding engine resources. 
检查flow-queue wfq 的配置，对照规格，查看是否超规格。
·原因110：The number of Outbound flow-queue wfq exceeded the specification of the forwarding engine resources. 
检查flow-queue wfq 的配置，对照规格，查看是否超规格。
·原因111：The number of Inbound flow-queue cbs exceeded the specification of the forwarding engine resources. 
检查flow-queue cbs 的配置，对照规格，查看是否超规格。
·原因112：The number of Outbound flow-queue cbs exceeded the specification of the forwarding engine resources. 
检查flow-queue cbs 的配置，对照规格，查看是否超规格。
·原因113：The number of Inbound flow-queue pbs exceeded the specification of the forwarding engine resources. 
检查flow-queue pbs的配置，对照规格，查看是否超规格。
·原因114：The number of Outbound flow-queue pbs exceeded the specification of the forwarding engine resources. 
检查flow-queue pbs 的配置，对照规格，查看是否超规格。
·原因115：The number of Inbound user-queue exceeded the specification of the forwarding engine resources. 
检查user-queue的配置，对照规格，查看是否超规格。
·原因116：The number of Outbound user-queue exceeded the specification of the forwarding engine resources. 
检查user-queue 的配置，对照规格，查看是否超规格。
·原因117：The number of Inbound user-queue template exceeded the specification of the forwarding engine resources. 
检查user-queue template的配置，对照规格，查看是否超规格。
·原因118：The number of Outbound user-queue template exceeded the specification of the forwarding engine resources. 
检查user-queue template 的配置，对照规格，查看是否超规格。
·原因119：The number of Inbound service-template exceeded the specification of the forwarding engine resources. 
检查service-template 的配置，对照规格，查看是否超规格。
·原因120：The number of Outbound service-template exceeded the specification of the forwarding engine resources. 
检查service-template 的配置，对照规格，查看是否超规格。
·原因121：The number of Inbound user-group-queue exceeded the specification of the forwarding engine resources. 
检查user-group-queue 的配置，对照规格，查看是否超规格。
·原因122：The number of Outbound user-group-queue exceeded the specification of the forwarding engine resources. 
检查user-g...