Operaton not applicable錯誤處理

本文介绍了一种解决在使用Delphi2009开发的系统中出现的Operatonnotapplicable错误的方法。该问题通常由电脑上存在多个版本的midas.dll文件引起。解决步骤包括:卸载旧版midas.dll,从9.9下载最新版本的midas.dll并将其放置于c:/windows/system32目录下,最后重新注册该dll文件。

       最近有發現個極個別的電腦在使用Delphi 2009開發的系統時會出現Operaton not applicable的錯誤,
經研究發現出現此問題的主要原因是該電腦上有多個版本的midas.dll文件所造成的問題,
經測試可以按以下方法解決

1、regsver32 /u midas.dll      
2、從9.9上下載最新的midas.dll到c:/windows/system32目錄下
3、cd c:/windows/system32
4、regsver32 midas.dll

◆ cpssDxChPclRuleSet() GT_STATUS cpssDxChPclRuleSet ( IN GT_U8 devNum, IN GT_U32 tcamIndex, IN CPSS_DXCH_PCL_RULE_FORMAT_TYPE_ENT ruleFormat, IN GT_U32 ruleIndex, IN CPSS_DXCH_PCL_RULE_OPTION_ENT ruleOptionsBmp, IN CPSS_DXCH_PCL_RULE_FORMAT_UNT * maskPtr, IN CPSS_DXCH_PCL_RULE_FORMAT_UNT * patternPtr, IN CPSS_DXCH_PCL_ACTION_STC * actionPtr ) The function sets the Policy Rule Mask, Pattern and Action. Note APPLICABLE DEVICES: xCat3; AC5; Lion2; Bobcat2; Caelum; Aldrin; AC3X; Bobcat3; Aldrin2; Falcon; AC5P; AC5X; Harrier; Ironman; AAS. NOT APPLICABLE DEVICES: None. Parameters [in] devNum - device number [in] tcamIndex - index of the TCAM unit. (APPLICABLE DEVICES AC5) (APPLICABLE RANGES 0..1) [in] ruleFormat - format of the Rule. [in] ruleIndex - index of the rule in the TCAM. The rule index defines order of action resolution in the cases of multiple rules match with packet's search key. Action of the matched rule with lowest index is taken in this case With reference to Standard and Extended rules indexes, the partitioning is as follows: For DxCh and DxCh2 devices: Standard rules. Rule index may be in the range from 0 up to 1023. Extended rules. Rule index may be in the range from 0 up to 511. Extended rule consumes the space of two standard rules: Extended rule with index 0 <= n <= 511 is placed in the space of two standard rules with indexes n and n + 512. For DxCh3 device: The TCAM has up to 3.5K (3584) rows. See datasheet of particular device for TCAM size. Each row can be used as: 4 standard rules 2 extended rules 1 extended and 2 standard rules 2 standard and 1 extended rules The TCAM partitioning is as follows: Standard rules. Rule index may be in the range from 0 up to 14335. Extended rules. Rule index may be in the range from 0 up to 7167. Extended rule consumes the space of two standard rules: Extended rule with index 0 <= n < 3584 is placed in the space of two standard rules with indexes n and n + 3584. Extended rule with index 3584 <= n < 7168 is placed in the space of two standard rules with indexes n + 3584, n + 7168. For xCat3 and above devices: See datasheet of particular device for TCAM size. For example describe the TCAM that has 1/4K (256) rows. Each row can be used as: 4 standard rules 2 extended rules 1 extended and 2 standard rules 2 standard and 1 extended rules The TCAM partitioning is as follows: Standard rules. Rule index may be in the range from 0 up to 1K (1024). Extended rules. Rule index may be in the range from 0 up to 0.5K (512). Extended rule consumes the space of two standard rules: Extended rule with index 2n (even index) is placed in the space of two standard rules with indexes 4n and 4n + 1. Extended rule with index 2n+1 (odd index) is placed in the space of two standard rules with indexes 4n+2 and 4n + 3. [in] ruleOptionsBmp - Bitmap of rule's options. The CPSS_DXCH_PCL_RULE_OPTION_ENT defines meaning of each bit. Samples: [in] ruleOptionsBmp = 0 - no options are defined. Rule state is valid. [in] ruleOptionsBmp = CPSS_DXCH_PCL_RULE_OPTION_WRITE_INVALID_E - write all fields of rule to TCAM but rule's state is invalid (no match during lookups). [in] maskPtr - rule mask. The rule mask is AND styled one. Mask bit's 0 means don't care bit (corresponding bit in the pattern is not using in the TCAM lookup). Mask bit's 1 means that corresponding bit in the pattern is using in the TCAM lookup. The format of mask is defined by ruleFormat [in] patternPtr - rule pattern. The format of pattern is defined by ruleFormat [in] actionPtr - Policy rule action that applied on packet if packet's search key matched with masked pattern. For AAS and above devices actionPtr->egressPolicy is input field containing direction. Return values GT_OK - on success GT_BAD_PARAM - on wrong parameters GT_BAD_PTR - on null pointer GT_OUT_OF_RANGE - one of the parameters is out of range GT_HW_ERROR - on hardware error GT_TIMEOUT - after max number of retries checking if PP ready GT_NOT_APPLICABLE_DEVICE - on not applicable device Note The pattern and mask input structures should be set to zero by an application before assignment of fields. The function places all muxed fields to rule patern and mask by using bitwise OR operation. The function does not check validity of muxed (overlapped) fields. cpssDxChPclRuleSet()函数的主要功能是什么
最新发布
09-23
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值