mgmt09_tif09

Functional changes from version 2 to version 3:●Support for DOS only systems and Windows 3.1/DOS only systems has beenterminated. The PCB and PCM IDE's have been discontinued. CCSC.EXE isnow a 32 bit application and now has a full set of command line options.PCW and CCSC fully operate on Windows 95,98,ME,NT4, and 2000. Customerswho buy or have PCB or PCM must use MPLAB as an IDE or their own editor.●All DLL files used by the compilers are in a DLL directory directly underthe directory with the EXE files. All .DLL files in the same directoryas the EXE are no longer used and may be deleted. The PC.DEF file andPCINCLUDES environment variable (in AUTOEXEC.BAT) are also no longer used.●CCSC now has the following command format:CCSC Valid Options:options cfilename options cfilename+FB Select PCB (12 bit)-D Do not create debug file +FM Select PCM (14 bit)+DS Standard .COD formatdebug file+FH Select PCH (PIC18)+DM.MAP format debug file +F7Select PC7 (PIC17)+DC Expanded .COD formatdebug file+FS Select PCS (SX)+Yx Optimization level x (0-9)+ES Standard error file+T Create call tree (.TRE) +EO Old error file format+A Create stats file (.STA)-J Do not create PJT file-M Do not create symbolfileCCSC Valid Options: (The xxx in the following are optional. If included, it sets the file extension.) options cfilename options cfilename+LNxxx Normal list file+O8xxx8 bit Intel HEX outputfile+LSxxx MPASM format list file+OWxxx16 bit Intel HEX outputfile+LOxxx Old MPASM list file+OBxxx Binary output file+LYxxx Symbolic list file-O Do not create object file -L Do not create list file+P Keep compile status window up after compile+Pxx Keep status window up for xx seconds after compile+PN Keep status window up only if there are no errors+PE Keep status window up only if there are errors+Z Keep scratch and debug files on disk after compileI="..."Set include directory search path, for example:I="c:\picc\examples;c:\picc\myincludes"If no I= appears on the command line the .PJT file willbe used to supply the include file paths.#xxx="yyy"Set a global #define for id xxx with a value of yyy, example:#debug="true"+STDOUT Outputs errors to STDOUT (for use with third party editors)+SETUP Install CCSC into MPLAB (no compile is done)+V Show compiler version (no compile is done)+Q Show all valid devices in database (no compile is done)●PCW has a new "Global Defines" window to allow compile time #defines tobe entered, saved in a separate file and loaded.● A new preprocessor directive #LOCATE has been added. #LOCATE works like#BYTE however in addition it prevents C from using the area. For example:float x;#locate x=0x50Will locate the float variable at 50-53 and C will not use this memoryfor other variables automatically located.●New byte wide I/O functions have been added that follow the normal rules formaintaining the TRIS register (unlike memory mapped port access). Examples:OUTPUT_B(3);X = INPUT_A();●New built-in function to restart the processor:RESET_CPU();Will jump to location 0 on 12 and 14 bit parts and also reset theregisters to power-up state on the PIC18.●PCW IDE changes:View Data Sheet and View Valid Fuses have moved to the View menuView|Valid Interrupts has been added to show a chips valid interrupts●The device .h file format has been updated. Information about device specificfunctions available is now in the .h file. The following defines supported forcompatibility with the old C71 compiler are no longer in the .h file. Use thenewer names:RTCC_ZERO use INT_RTCCEXT_INT use INT_EXTADC_DONE use INT_AD●#DEVICE must now be the first non-comment line in the program. Some pre-processordirectives may appear before this like #include and #define. Previous versionsof the compiler did not require a #device (it defaulted to a '71 in PCM).●The function EXT_INT_EDGE now accepts two parameter. The first parameter isthe external interrupt number (0,1 or 2) for the PIC18. If used it has no effecton 14 bit parts. If there is only one parameter the function works asit used to on external interrupt 0.●The functions SETUP_COUNTERS(), SET_RTCC() and GET_RTCC are still accepted bythe compiler however newer functions will provide better compatibility acrossfamilies. The newer functions are: SETUP_TIMER0(), SETUP_WDT(), SET_TIMER0()and GET_TIMER0(). Note that the PIC18 SETUP_WDT() only allows the WDT to beturned on or off, the time is set with #FUSES. The other PICs are the opposite.The TIMER0 is 16 bit on the PIC18 by default but can be setup to 8 bit.●For the PIC18 the READ/WRITE_PROGRAM_EEPROM accept a byte address and the readreturns a byte result. The WRITE will only work if a programming voltage isapplied to the chip.●The previously undocumented function ISAMOUNG is documented in this version.ISAMOUNG returns true if a character is one of the characters in a constantstring. For example:if( ISAMOUNG( x, "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ") )...●Quoted strings now accept inserted hex numbers via \x. For example:printf("Hi There\x0D\x0A");●By default the compiler treats SHORT as one bit, INT as 8 bits and LONG as16 bits. The traditional C convention is to have INT defined as the mostefficient size for the target processor. This is why it is 8 bits on the PIC.In order to help with code compatibility a new directive has been added thatwill allow these types to be changed. #TYPE can redefine these keywords.For example:#TYPE SHORT=8, INT=16, LONG=32Note that the commas are optional. Since #TYPE may render some sizesinaccessible (like a one bit int in the above) four new keywords havebeen added to represent the four ints: INT1, INT8, INT16 and INT32.Be warned CCS example programs and include files may not work right ifyou use #TYPE in your program.●The ABS, LABS and FABS functions were implemented as simple C functionsin stdlib.h. ABS() is now built into the compiler and accepts any typeas a parameter. It returns the same type as the argument. For compatibilityLABS and FABS are #defined to ABS in stdlib.h.●The debug file (.COD) has been expanded from the Microchip definition toto include information to permit advanced debugging. This includes allC data types and better tracking information. CCS now provides a .DLL thatmay be used by debuggers to use this information. For example it is possibleto have a watch expression like: TABLE[I].LAST-TABLE[I].FIRSTThe new .DLL knows how to evaluate the expression and provide a properlyformatted string back to the debugger. Arrays and structures are alsoproperly formatted. The stack frame may be viewed along with the parameterspassed at each level and function return values may be traced. CCS is workingwith emulator manufactures to make use of these new capabilities.●The PCW help filename has been changed from PCW.HLP to CCSC.HLP. The samehelp file is used for PCB, PCM, and PCH.●The PCW context sensitive help has been enhanced. Placing the cursor on anyC keyword, preprocessor directive or built in function and pressing F1 willbring up help on that item. In addition pressing F1 when a red error messageis being shown will bring up additional help with that error.●The PCW IDE now allows the toolbar to be customized.● A number of internal compiler limits have been increased. For example thelimitation of a macro expansion being less than 256 characters is now 32768. Changes not documented in the May-2001 manual:●If @filename appears on the CCSC command line command line options willbe read from the specified file. Parameters may appear on multiplelines in the file.●If the file CCSC.INI exists in the same directory as CCSC.EXE then commandline parameters are read from that file before they are processed on the command line.●printf() now accepts both 16 and 32 bit variables for %LU and %LD●#define macros now accept the ANSI operators # and ##. In summary the#idx will be replaced with "paramx" and idx##idy is replaced withparamxparamy and is expanded if a new macro name is formed.●#elif is now supported. For example:#if __device__==71#define adc_pin PIN_A0#elif __device__==74#define adc_pin PIN_A2#elif __device__==874#define adc_pin PIN_E0#else#define adc_pin PIN_A1#endif●#IF directives now support: defined(id)This expression evaluates to 1 if id is a preprocessor id and0 otherwise. For example:#ifdef __PCB__#include <16c54.h>#elif defined(__PCM__)#include <16c74.h>#elif defined(__PCH__)#include <18c658.h>#endif●printf() now supports %s to insert a constant or variable string.●Three functions have been added to make manipulation of byteswithin variables easier.i8 = MAKE8(var,offset)Extracts the byte at offset from var.Same as: i8 = (((var >> (offset*8)) & 0xff)except it is done with a single byte move.i16 = MAKE16(varhigh,varlow)Makes a 16 bit number out of two 8 bit numbers.If either parameter is 16 or 32 bits only the lsbis used.Same as: i16 = (int16)(varhigh&0xff)*0x100+(varlow&0xff)except it is done with two byte moves.i32 = MAKE32(var1,var2,var3,var4)Makes a 32 bit number out of any combinationof 8 and 16 bit numbers. Note that the numberof parameters may be 1 to 4. The msb is first.If the total bits provided is less than 32 thenzeros are added at the msb.●#asm now accepts a parameter to prevent the compiler from doing automaticbank switching and optimization in the ASM code. For example:#byte x = 0xa0#asmclrf x#endasmWill generate a bank switch to bank 1 and a clear of location 20 in that bank.#asm ASISclrf x#endasmWill just generate the clear of location 20 and ignore the bank.●The READ_ADC() function always defaults to a 8 bit result. This maybe different from previous versions where the defualt was differentdepending on the chip. Use #DEVICE ADC=xx to specify the desired resolution.●Constant strings are now concatinated when they appear separated by whitespace. For example:printf("hi" "there"); is the same as printf("hithere");Changes not documented in the July-2001 manual:●Arrays may be defined with [] in many cases. For example:const char id[] = {"Hi There"}; // Same as [9]int x[]; // Same as *xint x[] = {1,2,3}; // Same as [3]●The #USE I2C option NOFORCE_SW is still accepted however the new FORCE_HWis what will appear in future documentation.●#INT_ directives now allow a NOCLEAR option to prevent the compilerfrom clearing the interrupt. For example:#INT_RTCC NOCLEARisr() {...}。

算法实现FSK来电软件解码
张俊华
【期刊名称】《电脑编程技巧与维护》
【年(卷),期】2012(000)012
【摘要】比较了来电显示硬件解码和软件解码,详细介绍了算法FSK来电解码的数学原理和程序实现,解释了在实际实现中要注意的关键环节,在实际的交换机系统中实现了理想的解码效果和高度的系统集成度,达到了预期的良好效果.
【总页数】3页(P124-126)
【作者】张俊华
【作者单位】杭州亿利通信器材有限公司,杭州310012
【正文语种】中文
【相关文献】
1.FSK制式来电信息采集器的研究与设计 [J], 赵羿然;陈玮;邹光远;刘桂红;伍子健;刘宇杰;杨海严;崔泽华;罗敏
2.FSK制式来电显示功能的FPGA实现 [J], 刘永恩;邱里鑫;刘中友
3.一种基于FSK制式的智能来电显示模块的设计与实现 [J], 赵伟;顾霞萍;王宜怀
4.FSK来电识别软解码算法研究 [J], 赵书朵;陈云生;颜恒
5.FSK与DTMF来电显示通信终端的设计 [J], 蒋晖
因版权原因，仅展示原文概要，查看原文内容请购买。

Femto设备参数设置
目录
1、参数查询 (1)
2、Femto常用参数（飞烽设备） (3)
密闭模式设置 (3)
网关地址 (3)
博威设备设置 (4)
1、参数查询
选取设备管理->设备信息查询，在设备ID中数据设备IMSI。

选中选取的设备，右键选中配置管理
点击业务模版中的配置信息，会出现相关的参数信息
在设备方法中点击获取参数值，选中编辑，并输入参数号，点击√确认
点击获取参数值，可以查看现网的配置
在参数设置中可以输入参数的值，并点击下面的参数设置，修改参数。

2、Femto常用参数（飞烽设备）
备注：
由于密闭模式博威的设备查不到相关参数，所有参数按照飞烽的进行设置，不用另外查询
3、密闭模式设置
1、将用户IMSI号加入白名单（如果有多个IMSI号，用英文逗号隔开），博威的需分别设置.
2、将接入模式由Open Access 修改为Close Access（注意首字母大写，中间有空格）
4、网关地址
femto网管地址： 10.39.214.46
用户名：daixuef 密码daixuef
5、博威设备设置
1、封闭模式：由Open Access 改为Close Access，在Close和Access之间有一个空格，
首写字母均需大写。

2、封闭模式IMIS添加：将对应的IMSI添加到detail IMSI里，且对应的Enable都修改为1，然后提交.。

DALSTAR DS-1x-01M15 November 25, 2002 Basics about thecameraCamera Descriptions§ 1024 × 1024 × 12-bit @ 15 fps.§ Single channel RS-422 digital video output.§ Progressive scan.§ Internal (separate) sync.§ Internal and external exposure control.§ 20 MHz pixel clock rate.Mode of operations as per Matrox Imaging (in parentheses as per camera manufacturer)Interface Modes§ Continuous (no binning, binning)§ Asynchronous reset (no binning, binning)Basics about theinterface modesCamera Interface BriefsMode 1: Continuous (no binning)§ 1024 × 1024 × 12-bit @ 15 fps.§ Single channel RS-422 digital video.§ Progressive scan.§ Matrox Meteor-II/Digital receiving HSYNC, VSYNC, PIXEL CLOCK (@ 20MHz) and video signals from camera.§DCF: 1M15C1.DCFMode 2: Continuous (Binning)§ Up to 512 × 512 × 12-bit @ 30 fps.§ Single channel RS-422 digital video.§ Progressive scan.§ Matrox Meteor-II/Digital receiving HSYNC, VSYNC, PIXEL CLOCK (@ 10MHz) and video signals from camera.§DCF used: 1M15C2.DCFDALSTAR DS-1x-01M15 November 25, 2002 Basics about theCamera Interface Briefs (cont.)interface modesMode 3: Asynchronous reset (no binning)§ 1024 × 1024 × 12-bit.§ Single channel RS-422 digital video.§ Progressive scan.§ Matrox Meteor-II/Digital receiving TTL external trigger signal.§ Matrox Meteor-II/Digital sending EXPOSURE2 (TRIGGER IN) signal tocamera to initiate and control exposure time.§ Matrox Meteor-II/Digital receiving HSYNC, VSYNC, PIXEL CLOCK (@ 20MHz) and video signals from camera.§ DCF used: 1M15A1.DCFMode 4: Asynchronous reset (binning)§ 512 × 512 × 12-bit.§ Single channel RS-422 digital video.§ Progressive scan.§ Matrox Meteor-II/Digital receiving TTL external trigger signal.§ Matrox Meteor-II/Digital sending EXPOSURE2 (TRIGGER IN) signal tocamera to initiate and control exposure time.§ Matrox Meteor-II/Digital receiving HSYNC, VSYNC, PIXEL CLOCK (@ 10MHz) and video signals from camera.§ DCF used: 1M15A2.DCFDALSTAR DS-1x-01M15 November 25, 2002 Specifics about theCamera Interface Detailsinterface modesModes 1 and 2: Continuous§Frame Rate: Matrox Meteor-II/Digital receives the continuous video fromthe camera at 15/30 frames per second (no binning/binning).§Exposure time: Exposure time is inversely proportionate to the framerate or determined by the shutter setting. Refer to the camera manual formore information.§Camera Control: Camera control settings are made using DALSA’scontrol software. Contact DALSA for more information.Modes 3 and 4: Asynchronous Reset§Frame rate: The frame rate is determined by the frequency of theexternal trigger signal.§Exposure time: The width (rising edge to falling edge) of theEXPOSURE2 (TRIGGER IN)* signal is the exposure time. The exposuretime can be modified in the DCF using Matrox Intellicam or with the MILMdigControl() function. Refer to the respective manual for moreinformation.§Camera Control: External Trigger Mode/Integrate checkbox must bechecked in DALSA’s control software. Refer to the camera manual formore information.§Timing diagram:*SMA ConnectorDALSTAR DS-1x-01M15 November 25, 2002 Cabling details for thisinterface modeCabling Requirements – PCI VersionModes 1 and 2: Continuous§Cable: DBHD100-TO-OPEN (open ended) cable required for video,synchronization and control signals.§Connection: Connections between the 60-pin quad row connectors(DATA1) of the camera and the 100-pin connector of the Matrox Meteor-II/Digital are as follows:DALSTAR D1-1x-01M15(60-pin quad row connector- DATA 1) METEOR2-DIG/4/R (100-pin connector)Pin name Pin no.Pin name Pin no. D1A0+ 01 →DATA, INPUT, 0+ 01D1A0- 02 →DATA, INPUT, 0- 02D1A1+ 03 →DATA, INPUT, 1+ 03D1A1- 04 →DATA, INPUT, 1- 04D1A2+ 05 →DATA, INPUT, 2+ 05D1A2- 06 →DATA, INPUT, 2- 06D1A3+ 07 →DATA, INPUT, 3+ 07D1A3- 08 →DATA, INPUT, 3- 08D1A4+ 09 →DATA, INPUT, 4+ 09D1A4- 10 →DATA, INPUT, 4- 10D1A5+ 11 →DATA, INPUT, 5+ 11D1A5- 12 →DATA, INPUT, 5- 12D1A6+ 13 →DATA, INPUT, 6+ 13D1A6- 14 →DATA, INPUT, 6- 14D1A7+ 17 →DATA, INPUT, 7+ 15D1A7- 18 →DATA, INPUT, 7- 16D1A8+ 19 →DATA, INPUT, 8+ 17D1A8- 20 →DATA, INPUT, 8- 18D1A9+ 21 →DATA, INPUT, 9+ 19D1A9- 22 →DATA, INPUT, 9- 20D1A10+ 23 →DATA, INPUT, 10+ 21D1A10- 24 →DATA, INPUT, 10- 22D1A11+ 25 →DATA, INPUT, 11+ 23D1A11- 26 →DATA, INPUT, 11- 24D1HSYNC+ 58 →HSYNC, INPUT, + 33D1HSYNC - 57 →HSYNC, INPUT, - 34D1VSYNC+ 56 →VSYNC, INPUT, + 35D1VSYNC - 55 →VSYNC, INPUT, - 36D1GND 45 →GROUND 37D1GND 46 →GROUND 38D1PCLK- 59 →CLOCK, INPUT, + 39D1PCLK + 60 →CLOCK, INPUT, - 40 Continued…DALSTAR DS-1x-01M15 November 25, 2002 Cabling details for thisinterface modeCabling Requirements – PCI version (cont.)Modes 3 and 4: Asynchronous Reset§Cable: DBHD100-TO-OPEN (open ended) cable required for video,synchronization and control signals.§External Trigger: TTL external trigger source should be connected to thepin 2 and 7 (OPTO TRIG+/-) of the 9-pin Trigger Input connector locatedon the Matrox Meteor-II/Digital secondary RS-232/Trigger Input bracket.§Connection: Connections between the SMA/BNC connector of thecamera and the 100-pin connector of the Matrox Meteor-II/Digital are asin Modes 1 and 2: Continuous including the following:DALSTAR D1-1x-01M15 (SMA/BNC connector) METEOR2-DIG/4/R (100-pin connector)Pin name Pin no.Pin name Pin no. SMA or BNC -- ←EXPOSURE2, OUTPUT, TTL 88GND -- -- GROUND 38Cabling Requirements – PC/104-PLUS versionModes 1 and 2: Continuous§Cable:(A)* For a Matrox Meteor-II/Digital PC/104-PLUS frame grabber installed in a Matrox 4Sight-II, the VHDCI-TO-OPEN (open ended) cable is required to connect to the Matrox 4Sight-II’s expanded video input connectors. (B)* For connecting directly to a Matrox Meteor-II/DigitalPC/104-PLUS frame grabber, a custom ribbon cable can be built using the included low profile IDC mating connectors included with the board. §Connections: Connections between the 60-pin quad row connectors (DATA1) of the camera and the 68-pin connector of the Matrox Meteor-II/Digital are as follows.DALSTAR D1-1x-01M15(60-pin quad row connector- DATA 1) MET2-DIG+/L(68-pin connector)(A)* (B)*Pin name Pin no.Pin name Pin no.Pin no. D1A0+ 01 →DATA, INPUT, 0+ 34 01 D1A0- 02 →DATA, INPUT, 0- 68 02 D1A1+ 03 →DATA, INPUT, 1+ 33 03 D1A1- 04 →DATA, INPUT, 1- 67 04 D1A2+ 05 →DATA, INPUT, 2+ 32 05 D1A2- 06 →DATA, INPUT, 2- 66 06 D1A3+ 07 →DATA, INPUT, 3+ 31 07 D1A3- 08 →DATA, INPUT, 3- 65 08 D1A4+ 09 →DATA, INPUT, 4+ 30 09 D1A4- 10 →DATA, INPUT, 4- 64 10 Continued…*Note: column A represents connections via the Matrox 4Sight-II’s expanded video input connector and column B represents connections directly to the Matrox Meteor-II/Digital PC/104-Plus low profile IDC video input connector.DALSTAR DS-1x-01M15 November 25, 2002 Cabling details for thisinterface modeCabling Requirements – PC/104-PLUS version (cont.)Modes 1 and 2: ContinuousDALSTAR D1-1x-01M15(60-pin quad row connector- DATA 1) MET2-DIG+/L(68-pin connector)(A)* (B)*Pin name Pin no.Pin name Pin no.Pin no. D1A5+ 11 →DATA, INPUT, 5+ 29 11 D1A5- 12 →DATA, INPUT, 5- 63 12 D1A6+ 13 →DATA, INPUT, 6+ 28 13 D1A6- 14 →DATA, INPUT, 6- 62 14 D1A7+ 17 →DATA, INPUT, 7+ 27 15 D1A7- 18 →DATA, INPUT, 7- 61 16 D1A8+ 19 →DATA, INPUT, 8+ 08 53 D1A8- 20 →DATA, INPUT, 8- 42 54 D1A9+ 21 →DATA, INPUT, 9+ 07 55 D1A9- 22 →DATA, INPUT, 9- 41 56 D1A10+ 23 →DATA, INPUT, 10+ 06 57 D1A10- 24 →DATA, INPUT, 10- 40 58 D1A11+ 25 →DATA, INPUT, 11+ 05 59 D1A11- 26 →DATA, INPUT, 11- 39 60 D1HSYNC+ 58 →HSYNC, INPUT, + 26 17 D1HSYNC - 57 →HSYNC, INPUT, - 60 18 D1VSYNC+ 56 →VSYNC, INPUT, + 24 21 D1VSYNC - 55 →VSYNC, INPUT, - 58 22 D1GND 45 →GROUND 43 52 D1GND 46 →GROUND 43 52 D1PCLK- 59 →CLOCK, INPUT, + 22 25 D1PCLK + 60 →CLOCK, INPUT, - 56 26 *Note: column A represents connections via the Matrox 4Sight-II’s expanded video input connector and column B represents connections directly to the Matrox Meteor-II/Digital PC/104-Plus low profile IDC video input connector.Modes 3 and 4: Asynchronous Reset§Cable:(A)* For a Matrox Meteor-II/Digital PC/104-PLUS frame grabber installed in a Matrox 4Sight-II, the VHDCI-TO-OPEN (open ended) cable is required to connect to the Matrox 4Sight-II’s expanded video input connectors. (B)* For connecting directly to a Matrox Meteor-II/DigitalPC/104-PLUS frame grabber, a custom ribbon cable can be built using the included low profile IDC mating connectors included with the board. §External Trigger: TTL external trigger source should be connected to OPTOTRIG, INPUT pin 11 (A)* or pin 47 (B)* and OPTOTRIG COM (Ground) pin 10 (A)* or pin 49 (B)*.Continued…DALSTAR DS-1x-01M15 November 25, 2002Cabling details for thisinterface mode Cabling Requirements – PC/104-PLUS version (cont.)Modes 3 and 4: Asynchronous Reset§ Connection: Connections between the two 60-pin quad row connectors(DATA1) of the camera and the 68-pin connector of the Matrox Meteor-II/Digital are as in Modes 1 and 2: Continuous (PC/104-PLUS version )including the following:DALSTAR D1-1x-01M15 (SMA connector)MET2-DIG+/L (68-pin connector) (A)* (B)*Pin name Pin no. Pin name Pin no. Pin no.SMA or BNC -- ← EXPOSURE2, OUTPUT, TTL 46 88GND -- -- GROUND 43 38 *Note: column A represents connections via the Matrox 4Sight-II’s expanded video inputconnector and column B represents connections directly to the Matrox Meteor-II/DigitalPC/104-Plus low profile IDC video input connector.The DCF(s) mentioned in this application note can be found on the MIL CD or our FTP site (). The information furnished by Matrox Electronics System, Ltd. is believed to be accurate and reliable. Please verify all interface connections with camera documentation or manual. Contact your local sales representative or Matrox Sales office or Matrox Imaging Applications at 514-822-6061 for assistance. Corporate headquarters:Canada and U.S.A.Matrox Electronic Systems Ltd.1055 St. Regis Blvd.Dorval, Quebec H9P 2T4CanadaTel: (514) 685-2630Fax: (514) 822-6273。

UEFI Awareness Manual TianoCoreRelease 09.2023UEFI Awareness Manual TianoCoreTRACE32 Online HelpTRACE32 DirectoryTRACE32 IndexTRACE32 Documents ......................................................................................................................UEFI Awareness Manuals .............................................................................................................UEFI Awareness Manual TianoCore (1)History (4)Overview (4)Brief Overview of Documents for New Users5 Supported Versions5Configuration (6)ARM 32-Bit6 ARM 64-Bit7 Hooks & Internals in TianoCore7Features (8)Display of UEFI Resources8 Symbol Autoloader9 Autoloader Configuration9 Scan the UEFI Module Table10 Display the Autoloader Table11 TianoCore Specific Menu12Debugging UEFI Phases of TianoCore (13)Debugging from Reset Vector13 SEC Phase13 PEI Phase13 DXE Phase13 BDS Phase14TianoCore Commands (15)EXTension.ConfigTab Display DXE configuration table15 EXTension.DXEDRiVer Display loaded DXE drivers15 EXTension.DXEModule Display DXE modules16 EXTension.FV Display firmware volumes17 EXTension.HOB Display HOBs17 EXTension.Option Set awareness options18 EXTension.PEIModule Display PEI modules19 EXTension.PEISvc Display PEI services19EXTension.POST Display POST code20 EXTension.PROTocol Display installed protocols20TianoCore PRACTICE Functions (21)EXT.DXEDRV.ENTRY()Entry address for DXE driver21 EXT.DXEDRV.MAGIC()Magic of DXE driver21 EXT.DXEDRV.PATH()Build path for DXE driver21 EXT.DXEFILE.PATH()Build path for DXE module22 EXT.PEIM.ENTRY()Entry address for PEI module22 EXT.PEIM.MAGIC()Magic of PEI module22 EXT.PEIM.PATH()Build path for PEI module22UEFI Awareness Manual TianoCoreVersion 09-Oct-2023 History28-Aug-18The title of the manual was changed from “UEFI <x> Debugger” to “UEFI Awareness Manual <x>”.OverviewThe UEFI Awareness for TianoCore contains special extensions to the TRACE32 Debugger. This chapter describes the additional features, such as additional commands and debugging approaches.Brief Overview of Documents for New UsersArchitecture-independent information:•“Training Basic Debugging” (training_debugger.pdf): Get familiar with the basic features of a TRACE32 debugger.•“T32Start” (app_t32start.pdf): T32Start assists you in starting TRACE32 PowerView instances for different configurations of the debugger. T32Start is only available for Windows.•“General Commands” (general_ref_<x>.pdf): Alphabetic list of debug commands.Architecture-specific information:•“Processor Architecture Manuals”: These manuals describe commands that are specific for the processor architecture supported by your Debug Cable. T o access the manual for your processorarchitecture, proceed as follows:-Choose Help menu > Processor Architecture Manual.•“OS Awareness Manuals” (rtos_<os>.pdf): TRACE32 PowerView can be extended for operating system-aware debugging. The appropriate OS Awareness manual informs you how to enable theOS-aware debugging.•“UEFI Awareness Manuals” (uefi_<x>.pdf): TRACE32 PowerView can be extended for UEFI-aware debugging. The appropriate UEFI manual informs you how to enable the UEFI-awaredebugging.Supported VersionsCurrently TianoCore is supported for the following versions:•TianoCore on ARM32 and ARM64 architecturesConfigurationThe UEFI Awareness for TianoCore is configured by loading an extension definition file called “tiano.t32”from the demo directory with the EXTension.CONFIG command. The command takes two parameters that specify the memory base address and size of the UEFI package. See the file <board>Pkg/<board>Pkg.dsc of your UEFI implementation. “PcdSystemMemoryBase” rsp. “PcdSystemMemorySize” are the needed values.Additionally, load the “tiano.men” menu file (see “TianoCore specific Menu”) and configure the Symbol Autoloader.ARM 32-BitA full configuration for ARM 32-bit can look like this (the path prefix ~~ expands to the system directory ofTRACE32.):; Specify the memory base address and size,; see <board>Pkg/<board>Pkg.dsc:; PcdSystemMemoryBase = 0x80000000; PcdSystemMemorySize = 0x08000000; Load the TianoCore Awareness:EXTension.CONFIG ~~/demo/arm/bootloader/uefi/tiano/tiano.t32 \0x80000000 0x08000000; In a TrustZone/Hypervisor environment, you may need to; specify the access class where the UEFI BIOS runs.; E.g. if TianoCore runs in hypervisor zone:EXTension.ACCESS H:; Load the additional menu:MENU.ReProgram ~~/demo/arm/bootloader/uefi/tiano/tiano.men; Configure symbol autoloader:sYmbol.AutoLOAD.CHECKUEFI "do ~~/demo/arm/bootloader/uefi/tiano/autoload "See also the example scripts in ~~/demo/arm/bootloader/uefi/tianoARM 64-BitA full configuration for ARM 64-bit can look like this (the path prefix ~~ expands to the system directory ofTRACE32.):; Specify the memory base address and size,; see <board>Pkg/<board>Pkg.dsc:; PcdSystemMemoryBase = 0x80000000; PcdSystemMemorySize = 0x08000000; Load the TianoCore Awareness:EXTension.CONFIG ~~/demo/arm/bootloader/uefi/tiano/tiano.t32 \0x80000000 0x08000000; In a TrustZone/Hypervisor environment, you may need to; specify the access class where the UEFI BIOS runs.; E.g. if TianoCore runs in hypervisor zone:EXTension.ACCESS H:; Load the additional menu:MENU.ReProgram ~~/demo/arm/bootloader/uefi/tiano/tiano.men; Configure symbol autoloader:sYmbol.AutoLOAD.CHECKUEFI "do ~~/demo/arm/bootloader/uefi/tiano/autoload "See also the example scripts in ~~/demo/arm/bootloader/uefi/tianoHooks & Internals in TianoCoreIMPORTANT:When using GCC on ARM:The ELF->COFF converter (GenFw) may spoil the debug information when using several text/data sections (check with "-v"). The linker must combine all sections into one text section and one data section. The edk2/BaseT ools/Scripts directory contains a suitable linker script (GccBase.lds or previously gcc4.4-ld-script). Please ensure that this script is used when linking a module, e.g. by adding it to the linker flags in the edk2/BaseT ools/Conf/tools_def.template:--script=$(EDK_TOOLS_PATH)/Scripts/GccBase.ldsFeaturesThe UEFI Awareness for TianoCore supports the following features.Display of UEFI ResourcesThe extension defines new commands to display various UEFI resources. Information on the following UEFI components can be displayed:PEI phase:EXTension.FV PEI PEI firmware volumesEXTension.PEIModule PEI modules in FVsEXTension.HOB PEI PEI HOBsDXE phase:EXTension.FV DXE DXE firmware volumesEXTension.DXEModule DXE modules in FVsEXTension.DXEDRiVer Loaded DXE driversEXTension.HOB DXE DXE HOBsEXTension.PROTocol DXE Installed DXE protocolsEXTension.ConfigTab DXE configuration tableFor a description of the commands, refer to chapter “TianoCore Commands”.If you want to display the UEFI objects “On The Fly” while the target is running, you need to have access to memory while the target is running. Enable SYStem.MemAccess or SYStem.CpuAccess (CPUdependent), but be aware of the limitations (no cache reading, real-time intrusion).Symbol AutoloaderThe UEFI code is provided by the boot FLASH, but debugging becomes more comfortable when debug symbols are available.TRACE32 contains an “Autoloader”, which can be set up for automatic loading of symbol files. TheAutoloader maintains a list of address ranges, corresponding UEFI components and the appropriate load command. Whenever the user accesses an address within an address range known to the Autoloader, the debugger invokes the load associated command. The command is usually a call to a PRACTICE script, that handles loading the symbol file.The TRACE32 Autoloader has to be set up. This includes the following steps:1.Autoloader configuration.2.Scan of the UEFI module table to the Autoloader table.3.Display of the Autoloader table.Autoloader ConfigurationThe command sYmbol.AutoLOAD.CHECKUEFI <load_command> specifies the command that isautomatically used by the Autoloader to load the symbol information. T ypically the script autoload.cmm provided by Lauterbach is called.The command sYmbol.AutoLOAD.CHECKUEFI implicitly also defines the parameters that TRACE32 uses internally for the Autoloader.The script is provided in the TRACE32 demo directory:•32-bit: ~~/demo/arm/bootloader/uefi/tiano/autoload.cmm.•64-bit: ~~/demo/arm/bootloader/uefi/tiano/autoload.cmm.Example:; Configure symbol Autoloader for 32-bit TianoCoresYmbol.AutoLOAD.CHECKUEFI "DO ~~/demo/arm/bootloader/uefi/tiano/autoload.cmm"Scan the UEFI Module TableWhen the Autoloader is configured, the command sYmbol.AutoLOAD.CHECK can be used to scan the UEFI module table into the Autoloader table and to activate the Autoloader.Since the UEFI module table is updated by UEFI a re-scan might be necessary.The point of time at which the UEFI module table is re-scanned can be set very flexibly: sYmbol.AutoLOAD.CHECK [ON | OFF | ONGO]The default setting is sYmbol.AutoLOAD CHECK OFF. With this setting TRACE32 re-scans the UEFI module table only on request by using the sYmbol.AutoLOAD.CHECK command.With sYmbol.AutoLOAD.CHECK ON, TRACE32 re-scans the UEFI module table after every single step and whenever the program execution is stopped. This significantly slows down the speed of TRACE32.With sYmbol.AutoLOAD.CHECK ONGO, TRACE32 re-scans the UEFI module table whenever the program execution is stopped.NOTE:The Autoloader can load the symbol information for the SecCore, the PeiCore, allPEI modules and the DXE core as soon as the memory mode (e.g. 32-bit protectedmode) used by UEFI is activated.The Autoloader can only load symbol information for DXE modules that arealready loaded.Display the Autoloader TableThe command “sYmbol.AutoLOAD.List ” shows a list of all known address ranges/components and their symbol load commands.Autoload context menu Touch Advise TRACE32 to load the symbols for the selected module now.Set Mark selected module as loaded.ClearDelete symbols for the selected module in TRACE32.Module address range Module nameModule status dyn: (no meaning)load: symbols for module are loadedLoad command Parameters for load commandTianoCore Specific MenuThe menu file “tiano.men” contains a menu with TianoCore specific menu items. Load this menu with the MENU.ReProgram command.Y ou will find a new menu called TianoCore.•Use the PEI submenu to launch windows displaying PEI specific resources.•Use the DXE submenu to launch windows displaying DXE specific resources.•Use the Symbol Autoloader submenu to configure the symbol autoloader.See also chapter “Symbol Autoloader”.-List Components opens a sYmbol.AutoLOAD.List window showing all components currently active in the autoloader.-Check Now! performs a sYmbol.AutoLOAD.CHECK and reloads the autoloader list.-Set Loader Script allows you to specify the script that is called when a symbol file load is required. Y ou may also set the automatic autoloader check.Debugging UEFI Phases of TianoCoreUEFI runs in several “phases”. It starts with the “Security” (SEC) phase which immediately switches to the “Pre-EFI Initialization Environment” (PEI) phase. After this phase ended, control is given to the “Driver Exe-cution Environment” (DXE) phase. Shortly, before the OS is booted, the “Boot Device Selection” (BDS) phase is running.Each of this phases needs a different debugging environment. See below for a detailed description of each phase.Debugging from Reset VectorTRACE32 is a JT AG-based debugging tool and, as such, allows the user to start debugging their system right from the reset vector. It is possible to walk through the very first steps of the start-up to detect FLASH problems or faulty reset behavior.Shortly after reset, the system switches into the SEC phase.SEC PhaseTianoCore itself does not provide an SEC phase. It is up to the developer to implement a custom SEC phase, and as such out of the scope of this documentPEI PhaseIf you want to debug the PEI phase right from the start, halt the system at the reset vector. Then load the symbols of your PEI core module with the symbol autoloader, and go until the desired entry point, e.g: sYmbol.AutoLOAD.CHECKsYmbol.AutoLOAD.Touch "ArmPlatformPrePiUniCore"Go PrePiMainInspect the PEI resources with the menu items in the “PEI” submenu.DXE PhaseAfter PEI phase completed, it hands off control to the DXE core. T o debug the DxeCore from start, load the symbols of “DxeCore” just before PEI jumps into the DxeCore and set a breakpoint at “DxeMain”. DxeMain then starts the DXE dispatcher.For debugging a DXE driver from its entry point, a special script “go_dxedrv” is available in the ~~/demo directory. Call this script with the name of the DXE module before the module is started. E.g. to debug the DXE driver “Metronome”:DO go_dxedrv MetronomeThis script sets a breakpoint in the DXE core code and waits until the specified DXE module is loaded. Then it sets a breakpoint onto the module entry point and halts there. Y ou can then start debugging the module from scratch.BDS PhaseTianoCore implements the BDS phase as DXE driver. T o debug the BDS phase, debug the “ArmPlat-formBds” module like shown in “DXE Phase”.TianoCore CommandsEXTension.ConfigTabDisplay DXE configuration tableDisplays the DXE configuration table.EXTension.DXEDRiVerDisplay loaded DXE driversDisplays a table with all DXE drivers that DxeCore already loaded into the system.Y ou can sort the window to the entries of a column by clicking on the column header.“magic” is a unique ID, used by the UEFI Awareness to identify a specific driver.Format:EXTension.ConfigTabFormat:EXTension.DXEDRiVerEXTension.DXEModuleDisplay DXE modulesDisplays a table with all DXE modules found in the system (firmware volumes or HOBs).Y ou can sort the window to the entries of a column by clicking on the column header.“magic” is a unique ID, used by the UEFI Awareness to identify a specific module.The “magic” fields are mouse sensitive. Right-click on them to get a local menu. Double-clicking on them opens appropriate windows.Format:EXTension.DXEModuleEXTension.FVDisplay firmware volumesDisplays a table with the firmware volumes of the PEI or DXE phase.If an address of a firmware volume is specified, the command displays the contents of this FV .“magic” is a unique ID used by the UEFI Debugger to identify a specific firmware volume or file.The “magic” fields are mouse sensitive, double clicking on them opens appropriate windows. Right-clickingon them will show a context menu.The debugger tries to detect the address of the boot firmware volume automatically . If this fails, specify the address of the boot FV manually with the EXTension.Option BOOTFV command.EXTension.HOBDisplay HOBsDisplays a table with the hand off blocks of the PEI or DXE phase.Format:EXTension.FV [PEI | DXE [<fv_address >]]Format:EXTension.HOB [PEI | DXE ]The “address” fields are mouse sensitive, double-clicking them opens appropriate windows. Right-clicking on them will show a context menu.EXTension.OptionSet awareness optionsSets various options to the awareness. Format:EXTension.Option<option> <option>:BOOTFV <address>PEIHOBS <address>SYSTABLE <address>UCODE <address>BOOTFV Set the base address of the boot firmware volume.PEIHOBS Set the base address of the HOB list in PEI phase.SYSTABLE Set the base address of the EFI System Table UCODESet the base address of the microcode table.EXTension.PEIModuleDisplay PEI modulesDisplays a table with all PEI modules found in the system.Y ou can sort the window to the entries of a column by clicking on the column header.“magic” is a unique ID, used by the UEFI Awareness to identify a specific module.The “magic” fields are mouse sensitive. Right-click on them to get a local menu. Double-clicking on them opens appropriate windows.EXTension.PEISvcDisplay PEI servicesDisplays a table with all available PEI services.Format:EXTension.PEIModuleFormat:EXTension.PEISvcEXTension.POSTDisplay POST code(Only available on x86/x64 targets.)Displays the Power-On Self-Test code.EXTension.PROTocolDisplay installed protocolsDisplays the list of installed DXE protocols.Format:EXTension.POSTFormat:EXTension.PROTocolTianoCore PRACTICE FunctionsThere are special definitions for TianoCore specific PRACTICE functions.EXT.DXEDRV.ENTRY()Entry address for DXE driver Syntax:EXT.DXEDRV.ENTRY(<dxedrv_magic>)Returns the entry address for the specified DXE driver.Parameter Type: Decimal or hex or binary value.Return Value Type: Hex value.EXT.DXEDRV.MAGIC()Magic of DXE driver Syntax:EXT.DXEDRV.MAGIC("<dxedrv_name>")Returns the “magic” of the specified loaded DXE driver.Parameter Type: String (with quotation marks).Return Value Type: Hex value.EXT.DXEDRV.PATH()Build path for DXE driver Syntax:EXT.DXEDRV.PATH(<dxedrv_magic>)Returns the build path for the specified DXE driver.Parameter Type: Decimal or hex or binary value.Return Value Type: String.EXT.DXEFILE.PATH()Build path for DXE module Syntax:EXT.DXEFILE.PATH(<dxem_magic>)Returns the build path for the specified DXE module.Parameter Type: Decimal or hex or binary value.Return Value Type: String.EXT.PEIM.ENTRY()Entry address for PEI module Syntax:EXT.PEIM.ENTRY(<peim_magic>)Returns the entry address for the specified PEI module.Parameter Type: Decimal or hex or binary value.Return Value Type: Hex value.EXT.PEIM.MAGIC()Magic of PEI module Syntax:EXT.PEIM.MAGIC("<peim_name>")Returns the “magic” of the specified PEI module.Parameter Type: String (with quotation marks).Return Value Type: Hex value.EXT.PEIM.P ATH()Build path for PEI module Syntax:EXT.PEIM.PATH(<peim_magic>)Returns the build path for the specified PEI module.Parameter Type: Decimal or hex or binary value.Return Value Type: String.。

凌华科技发布ATCA刀片服务器
佚名
【期刊名称】《测控技术》
【年(卷),期】2009(28)12
【摘要】2009年11月17日，凌华科技发布ATCA服务器等级产品aTCA-6100，此款产品搭载双英特尔64位四核Xeon处理器L5518、英特尔5520芯片组、支持6个DDR3-1066 VLP RDIMM内存插槽，最高容量达48GB、并可选配PICMG标准规范AdvancedMC（AMC）卡扩展槽。

【总页数】1页(P96-96)
【关键词】凌华科技;刀片服务器;ATCA;Xeon处理器;CA服务器;PICMG;内存插槽;标准规范
【正文语种】中文
【中图分类】TP273;TP368.5
【相关文献】
1.凌华科技发布首款双四核、双AMC插槽的ATCA刀片服务器——aTCA-6900
提供电信和网通设备绝佳运算性能、10Gigabit网络整合型解决方案 [J], 无
2.凌华科技发布首款双四核、双AMC插槽的ATCA刀片服务器 [J],
3.凌华科技领先发布支持双英特尔XeonL5518处理器与AMC插槽的ATCA刀片服务器 [J],
4.凌华科技领先发布支持双英特尔Xeon~L5518处理器与AMC插槽的ATCA
刀片服务器 [J],
5.凌华科技发布电信与网络设备专用的高端ATCA刀片服务器 [J],
因版权原因，仅展示原文概要，查看原文内容请购买。

H3C 防火墙多插卡高性能组网典型配置举例Copyright © 2013 杭州华三通信技术有限公司版权所有，保留一切权利。

非经本公司书面许可，任何单位和个人不得擅自摘抄、复制本文档内容的部分或全部，并不得以任何形式传播。

本文档中的信息可能变动，恕不另行通知。

目录1 使用版本 (1)2 特性简介 (1)3 应用场合 (1)4 注意事项 (1)5 配置前提 (2)6 路由模式配置举例 (2)6.1 组网需求 (2)6.2 配置思路 (3)6.3 配置步骤 (3)6.3.1 S9508E的配置 (3)6.3.2 SecBlade FW1的配置 (7)6.3.3 SecBlade FW2的配置 (9)6.3.4 SecBlade FW3的配置 (9)6.3.5 SecBlade FW4的配置 (10)6.4 配置文件 (11)6.4.1 S9508E (11)6.4.2 SecBlade FW1的配置 (14)6.4.3 SecBlade FW2的配置 (14)6.4.4 SecBlade FW3的配置 (15)6.4.5 SecBlade FW4的配置 (15)6.5 注意事项 (15)7 NAT模式配置举例 (16)7.1 组网需求 (16)7.2 配置思路 (16)7.3 配置步骤 (17)7.3.1 S9508E的配置 (17)7.3.2 SecBlade FW1的配置 (21)7.3.3 SecBlade FW2的配置 (23)7.3.4 SecBlade FW3的配置 (24)7.3.5 SecBlade FW4的配置 (24)7.4 注意事项 (25)7.5 配置文件 (25)7.5.1 S9508E的配置 (25)7.5.3 SecBlade FW2的配置 (26)7.5.4 SecBlade FW3的配置 (27)7.5.5 SecBlade FW4的配置 (27)8 透明模式配置举例 (28)8.1 组网需求 (28)8.2 配置思路 (28)8.3 配置步骤 (29)8.3.1 S9508E的配置 (29)8.3.2 SecBlade FW1的配置 (31)8.3.3 SecBlade FW2的配置 (32)8.3.4 SecBlade FW3的配置 (32)8.3.5 SecBlade FW4的配置 (33)8.4 配置文件 (33)8.4.1 S9508E (33)8.4.2 SecBlade FW1的配置 (34)8.4.3 SecBlade FW2的配置 (35)8.4.4 SecBlade FW3的配置 (35)8.4.5 SecBlade FW4的配置 (35)9 双机IRF组网路由/NAT模式配置举例 (35)9.1 组网需求 (35)9.2 配置思路 (36)9.3 配置步骤 (37)9.3.1 S12500的配置 (37)9.3.2 宿主交换机 1的SecBlade FW1的配置 (42)9.3.3 宿主交换机 1的SecBlade FW2的配置 (44)9.3.4 宿主交换机 1的SecBlade FW3的配置 (45)9.3.5 宿主交换机 2的SecBlade FW1的配置 (46)9.3.6 宿主交换机 2的SecBlade FW2的配置 (48)9.3.7 宿主交换机 2的SecBlade FW3的配置 (49)9.4 配置文件 (50)9.4.1 S12500的配置 (50)9.4.2 宿主交换机1的SecBlade FW1的配置 (55)9.4.3 宿主交换机1的SecBlade FW2的配置 (56)9.4.4 宿主交换机1的SecBlade FW3的配置 (57)9.4.5 宿主交换机2的SecBlade FW1的配置 (58)9.4.7 宿主交换机2的SecBlade FW3的配置 (60)10 双机IRF组网透明模式配置举例 (61)10.1 组网需求 (61)10.2 配置思路 (61)10.3 配置前提 (62)10.4 配置步骤 (62)10.4.1 S9508E的配置 (62)10.4.2 宿主交换机1的SecBlade FW1的配置 (65)10.4.3 宿主交换机1的SecBlade FW2的配置 (66)10.4.4 宿主交换机1的SecBlade FW3的配置 (67)10.4.5 宿主交换机2的SecBlade FW1的配置 (67)10.4.6 宿主交换机2的SecBlade FW2的配置 (68)10.4.7 宿主交换机2的SecBlade FW3的配置 (69)10.5 验证配置 (70)10.6 配置文件 (73)10.6.1 S9508E的配置 (73)10.6.2 宿主交换机1的SecBlade FW1的配置 (76)10.6.3 宿主交换机1的SecBlade FW2的配置 (77)10.6.4 宿主交换机1的SecBlade FW3的配置 (77)10.6.5 宿主交换机2的SecBlade FW1的配置 (78)10.6.6 宿主交换机2的SecBlade FW2的配置 (79)10.6.7 宿主交换机2的SecBlade FW3的配置 (79)10.7 注意事项 (80)11 FAQ (80)11.1 路由交换机如何实现流量负载分担？ (80)11.2 目前路由交换机最大支持多少条等价路由？ (80)11.3 路由交换机等价路由负载分发算法是否可以修改？ (81)11.4 S9500E、S12500路由交换机的等价路由是如何选择下一跳地址的？ (81)11.5 S5800、S7500E、S10500路由交换机的等价路由是如何选择下一跳地址的？ (82)11.6 S5800、S7500E、S10500链路聚合的具体算法是什么？在什么情况下会有限制？ (83)11.7 S9500E、S12500链路聚合是如何选择转发链路的？ (83)11.8 各个系列交换机可以配置的链路聚合的流量分担方式： (83)11.9 目前S9500E GRE Tunnel有哪些使用限制？ (83)11.10 多SecBlade FW插卡组网，是否适用于VRRPE部署？ (84)11.11 路由交换机是否已经支持带vpn-instance的策略路由？ (84)11.12 IRF方案中，IRF-Port要求最少几条链路连接（链路聚合方式），以增加IRF可靠性、避免IRF单链路故障和避免IRF单链路性能瓶颈？ (84)11.13 当组网采用多SecBlade FW插卡时，出接口做NAT Outbound，是否要求每个SecBlade FW插卡出接口配置不重叠的NAT地址池？ (84)11.14 当组网采用多SecBlade FW插卡负载分担N+1备份方式时，当其中有一块SecBalde FW故障时，网络是否会重新收敛，排除故障的SecBalde FW插卡，所有会话重新建立？ (84)11.15 IRF方案中，由于路由交换机存在本地链路优先转发的特性，故在组网中，有什么需要注意的地方？ (84)12 相关资料 (84)1 使用版本本举例是在H3C SecBladeII-CMW5.20-F3171P17版本上进行配置和验证的。