is-is中Level和area的关系

时间: 2024-01-13 18:04:21 浏览: 26
"IS-IS" 是一个路由协议,用于在计算机网络中动态地确定最优的数据传输路径。在 IS-IS 中,Level 和 area 是两个不同的概念。 Level 是指 IS-IS 协议中的层级,它代表着网络中的不同的拓扑结构。IS-IS 支持三个层级:Level 1、Level 2 和 Level 1-2。Level 1 是指本地区域内的路由器之间的通信,Level 2 是指不同区域之间的路由器之间的通信,而 Level 1-2 是指同时支持 Level 1 和 Level 2 的路由器。不同的 Level 之间需要通过 Level 2 路由器进行通信。 Area 是指 IS-IS 协议中的区域,它代表着网络中的逻辑分组。一个区域内的路由器可以通过一个共同的区域标识符(Area ID)进行标识。在 IS-IS 中,一个区域内的路由器可以直接通信,而不同区域之间的路由器需要通过 Level 2 路由器进行通信。 因此,Level 和 area 是两个不同的概念,它们之间没有直接的关系。在 IS-IS 中,Level 2 路由器可以连接不同的区域,在 Level 2 范围内进行路由选择。而 Level 1 路由器只能在本地区域内进行路由选择。
相关问题

ospf和is详解 pdf

### 回答1: OSPF(Open Shortest Path First)和IS-IS(Intermediate System to Intermediate System)是两种用于路由选择的内部网关协议(Interior Gateway Protocol,简称IGP)。 OSPF是一种基于链路状态的路由选择协议,它将整个网络拓扑信息传播给所有的路由器,使得每个路由器可以维护一个完整的拓扑数据库。通过计算最短路径树来选择最佳路径,OSPF可以提供快速的收敛性和高度可靠的路径选择。OSPF通过使用不同的链路成本和路由优先级来实现灵活的路由策略,支持VLSM(Variable Length Subnet Mask)和分层的网络设计。此外,OSPF还能够支持IPv4和IPv6,并且具备安全性的机制,如认证和区域边界路由器。 IS-IS是一种基于SPF(Shortest Path First)算法的路由选择协议,主要用于大型的企业和服务提供商网络。它使用了类似于OSPF的链路状态数据库的概念,但是IS-IS使用自己的TLV(Type-Length-Value)格式来交换链路状态信息。IS-IS可以支持IPv4和IPv6,并且具有IP和非IP路由的能力。IS-IS将网络划分为不同的区域,通过区域之间的边界路由器进行路由信息交换。IS-IS还支持快速收敛和冗余路径选择,以提高网络的可靠性。 总结来说,OSPF和IS-IS都是用于内部网关路由选择的协议,它们都具备快速收敛、高度可靠和灵活路由策略的功能。然而,OSPF更常用于企业网络和小型网络,而IS-IS适用于大型网络和运营商网络。 ### 回答2: OSPF和IS-IS是两种常用的内部网关协议(IGP),用于在企业网络中实现路由控制和故障容错。 OSPF是开放最短路径优先(Open Shortest Path First)的缩写。它通过建立链路状态数据库的方式,收集所有路由器的拓扑信息,并根据该信息计算出最短路径来进行路由选择。它使用了Dijkstra算法来计算最短路径,通过将网络划分为区域(Area)来减少计算复杂性。OSPF通过使用HELLO消息来发现邻居路由器,并通过LSA(链路状态消息)来更新和维护路由表。OSPF支持分层的设计,可实现快速收敛和容错,适用于中大型企业网络。 IS-IS是Intermediate System to Intermediate System的缩写,它也是一种运行在OSI第二层的链路状态协议。IS-IS被广泛用于ISP和大型企业网络中,以提供稳定可靠的路由控制。IS-IS使用了自己的链路状态数据库,并使用SPF(Shortest Path First)算法来计算最短路径。与OSPF类似,IS-IS也使用HELLO消息来发现邻居,并通过LSP(链路状态报文)来传播和更新路由信息。与OSPF不同的是,IS-IS没有区域的概念,而是将网络划分为区域无关(Level 1)和区域内(Level 2)两个层级。 总之,OSPF和IS-IS是两种常见的内部网关协议,用于实现企业网络的路由控制和故障容错。它们通过建立链路状态数据库、使用HELLO消息发现邻居、使用LSA或LSP传播和更新路由信息等方式来实现路由选择和维护。它们在设计理念和功能上有一些差别,但都能在中大型企业网络中提供高效可靠的路由服务。

SELECT DISTINCT ( A.DATA_TYPE ) AS DATA_TYPE, A.DATA_VALUE AS TSL, IFNULL(( SELECT B.DATA_VALUE FROM YXDDZH_MIDDLE.GZ_SCREEN_JGSY_SDHJ_SPFW_CITY_AREA_DATA B WHERE B.IS_DELETED = 0 AND B.DATA_DIMENSION = '期末' AND B.LEVEL = 2 AND B.DATA_NAME = '举报' AND B.DATA_AREA = '市级' AND B.DATA_TYPE = A.DATA_TYPE AND B.DATA_TIME = ( SELECT MAX( DATA_TIME ) FROM YXDDZH_MIDDLE.GZ_SCREEN_JGSY_SDHJ_SPFW_CITY_AREA_DATA WHERE IS_DELETED = 0 AND DATA_DIMENSION = '期末' AND DATA_NAME = '举报' AND LEVEL = 2 AND DATA_AREA = '市级' ) ), 0 ) AS JBL, CURRENT_ID FROM YXDDZH_MIDDLE.GZ_SCREEN_JGSY_SDHJ_SPFW_CITY_AREA_DATA A WHERE A.IS_DELETED = 0 AND A.DATA_DIMENSION = '期末' AND A.LEVEL = 2 AND A.DATA_NAME = '投诉' AND A.DATA_AREA = '市级' AND A.DATA_TIME = ( SELECT MAX( DATA_TIME ) FROM YXDDZH_MIDDLE.GZ_SCREEN_JGSY_SDHJ_SPFW_CITY_AREA_DATA WHERE IS_DELETED = 0 AND DATA_DIMENSION = '期末' AND DATA_NAME = '投诉' AND LEVEL = 2 AND DATA_AREA = '市级')这个sql 优化

对于这个SQL查询语句的优化,可以考虑以下几点: 1. 使用JOIN语句代替子查询:将子查询转换为JOIN语句,可以提高查询性能。 2. 添加适当的索引:根据查询条件和连接条件,为相关表添加合适的索引,以加快查询速度。 3. 减少重复的条件判断:在子查询和主查询中,有一些条件判断是重复的,可以将它们提取出来,避免重复计算。 4. 使用表别名:为表和字段使用简短的别名,提高查询语句的可读性。 下面是对原始SQL查询语句进行优化的示例: SELECT DISTINCT A.DATA_TYPE AS DATA_TYPE, A.DATA_VALUE AS TSL, IFNULL(B.DATA_VALUE, 0) AS JBL, A.CURRENT_ID FROM YXDDZH_MIDDLE.GZ_SCREEN_JGSY_SDHJ_SPFW_CITY_AREA_DATA A LEFT JOIN ( SELECT DATA_TYPE, DATA_VALUE FROM YXDDZH_MIDDLE.GZ_SCREEN_JGSY_SDHJ_SPFW_CITY_AREA_DATA WHERE IS_DELETED = 0 AND DATA_DIMENSION = '期末' AND DATA_NAME = '举报' AND LEVEL = 2 AND DATA_AREA = '市级' AND DATA_TIME = ( SELECT MAX(DATA_TIME) FROM YXDDZH_MIDDLE.GZ_SCREEN_JGSY_SDHJ_SPFW_CITY_AREA_DATA WHERE IS_DELETED = 0 AND DATA_DIMENSION = '期末' AND DATA_NAME = '举报' AND LEVEL = 2 AND DATA_AREA = '市级' ) ) B ON A.DATA_TYPE = B.DATA_TYPE WHERE A.IS_DELETED = 0 AND A.DATA_DIMENSION = '期末' AND A.LEVEL = 2 AND A.DATA_NAME = '投诉' AND A.DATA_AREA = '市级' AND A.DATA_TIME = ( SELECT MAX(DATA_TIME) FROM YXDDZH_MIDDLE.GZ_SCREEN_JGSY_SDHJ_SPFW_CITY_AREA_DATA WHERE IS_DELETED = 0 AND DATA_DIMENSION = '期末' AND DATA_NAME = '投诉' AND LEVEL = 2 AND DATA_AREA = '市级' ); 请注意,具体的优化策略可能需要根据实际情况进行调整和测试,以达到最佳的查询性能。

相关推荐

The LULC simulation data we utilized to create future EN maps was produced by X. Liu et al. (2017), which was conducted at the national level. The reason we apply national-level simulated data to a local area is as follows. Firstly, China has a top-down land use planning system (also known as spatial planning) with five levels. The quantitative objectives in national plans are handed down to county-level plans through provincial and prefectural level plans (Zhong et al., 2014). That means land use patterns of nine cities in WUA are required to reflect relevant upper-level plans, for example, to satisfy the land use quota made by Hubei provincial plans and the national plans. Secondly, there are interdependencies across places so what happens in one region produces effects not only on this location but on other regions (Overman et al., 2010). And the increase of construction land in one place will shift protection pressure on natural ecosystems elsewhere for a sustainable goal. The land use simulation at the national level allocated land resources from a top-down perspective and links land use changes in a region to events taking place in other locations through global simulation. However, the Kappa coefficient of the simulated data in WUA is 0.55 and the overall accuracy is 0.71, which is lower than the statistic value at the national-level data. Although the Kappa between 0.4~0.6 is moderate and at an acceptable level (Appiah et al., 2015; Ding et al., 2013; Ku, 2016), the simulated accuracy of the land use data needs to be improved. Future work on exploring the impact of LULC dynamics on EN will develop based on the high-accuracy simulated data and updating the initial simulated time to 2020, by integrating the impacts of socioeconomic factors, climate change, regional planning, land use policy, etc.

改为pgsql select c.* from ( select a.* from ( SELECT t.PROJ_ID,t.PROJ_CODE,t.PROJ_NAME,t.CLIENT_CODE,t.CLIENT_NAME,t.SPEC_CODE,t.SPEC_NAME,t.BUS_UNIT_CODE,t.BUS_UNIT,t.PROJ_DEP_CODE,t.PROJ_DEP,t.PROJECT_MANAGER_CODE,t.PROJECT_MANAGER,t.PROJECT_DEP_MANAGER_CODE,t.PROJECT_DEP_MANAGER,t.IS_SUB_PROJ,t.SUB_PROJ_TYPE_CODE,t.SUB_PROJ_TYPE,t.PARENT_CODE,t.PROJ_GROSS,t.CLIENT_AREA_CODE,t.CLIENT_AREA,t.CLIENT_TYPE_FULL_PATH_CODE,t.CLIENT_TYPE_PULL_PATH,t.BUSINESS_TYPE_CODE,t.BUSINESS_TYPE,t.BUSINESS_LEVEL_CODE,t.BUSINESS_LEVEL,t.BUSINESS_AREA_CODE,t.BUSINESS_AREA_NAME,t.IS_CLOSE,t.IS_IN_COO,t.TAX_RATE,t.IS_AUTHORIZED,t.AUTHORIZED_AMOUNT,t.IS_VIRTUAL,t.INCOME_BUDGET,t.EXPENDITURE_BUDGET,t.P_VALUE,t.CREATE_TIME,t.P_BUD_VALUE,t.P1_BUD_VALUE,t.P2_BUD_VALUE,t.ORG_CODE,t.ORG_NAME,t.PROD_RES_TYPE,t.IS_TECH_COO,t.COO_UNIT_RATIO,t.PROJ_ACHIEVEMENTS_BUD,t.REIMBURSEMENT_COST_BUD,t.COO_COST_BUD,t.MATERIAL_COST_BUD,t.PERFORMANCE_PERCENT,t.SCHE_START_TIME,t.SCHE_END_TIME,t.PROJECT_ACCOUNT_CODE,t.CUSTOMER_TYPE_CODE,t.CUSTOMER_TYPE,t.IS_PURE_OUT_PROJ,t.PROJECT_CREATE_TIME,t.IS_RELATE,t.IS_QUOTA,t.MAIN_PROJECT_CODE,t.PROJ_STATUS,t.IS_LARGE_PROJECT,t.MARKET_DIS_COUNT_RATE,t.PROJECT_CAT,t.MGR_PER_FORMANCE_RATIO,t.P1_VALUE,t.S_VALUE,t.COOP_VALUE,t.H_VALUE,t.DEVICE_BUDGET_COST,t.SUR_FEE_DIS_COUNT_RATE,t.DES_FEE_DIS_COUNT_RATE, (select listagg(p.coo_unit_code, ',') within group(order by p.coo_unit_code) from ( select distinct coo_unit_code from t_spdi_proj where is_sub_proj = 'Y' and sub_proj_type_code = 'wbhz' and PROJ_STATUS != 'P_5' AND PROJ_STATUS != 'P_4' and parent_code = t.proj_code )p ) coo_unit_code, (select listagg(to_char(p.coo_unit), ',') within group(order by p.coo_unit) from ( select distinct coo_unit from t_spdi_proj where is_sub_proj = 'Y' and sub_proj_type_code = 'wbhz' and PROJ_STATUS != 'P_5' AND PROJ_STATUS != 'P_4' and parent_code = t.proj_code )p ) coo_unit from T_SPDI_PROJ t where -- and t.PARENT_CODE=#{parentCode:VARCHAR} t.IS_SUB_PROJ='Y' and t.SUB_PROJ_TYPE_CODE='zz' and t.PROJ_STATUS NOT IN ('E','H','W') order by t.proj_id )a )c

为什么下面的sql语句会输出重复的结果:SELECT tp.parent_production_orders AS parent_production_orders, tp.production_orders AS production_orders, tp.work_order AS work_order, tp.contract AS contract, tp.sbbh AS sbbh, tp.batch_num AS batch_num, tp.product_code AS product_code, tp.product_number AS product_number, tp.product_name AS product_name, to_char( middle.create_date, 'yyyy-mm-dd' ) AS issued_date, to_char( to_timestamp( tp.delivery_time / 1000 ), 'yyyy-mm-dd' ) AS delivery_time, middle.line_code AS work_area_code, middle.line_name AS work_area_name, tp.workorder_number AS workorder_number, tp.complete_number AS complete_number, tp.part_unit AS part_unit, middle.work_time_type AS work_time_type, middle.process_time AS process_time, CASE WHEN sc.totalSubmitHours IS NULL THEN 0 ELSE sc.totalSubmitHours END AS submit_work_hours, CASE WHEN middle.process_time > 0 AND sc.totalSubmitHours IS NOT NULL THEN round( ( sc.totalSubmitHours / middle.process_time ), 2 ) * 100 ELSE 0 END plan_achievement_rate, CASE WHEN sc.totalSubmitHours IS NULL THEN 0 ELSE round( CAST ( sc.totalSubmitHours AS NUMERIC ) / CAST ( 60 AS NUMERIC ), 1 ) END AS submit_work_hours_h, round( CAST ( middle.process_time AS NUMERIC ) / CAST ( 60 AS NUMERIC ), 1 ) AS process_time_h, pinfo.material_channel AS material_channel FROM hm_model_work_order_report_middle middle LEFT JOIN hm_model_trc_plan tp ON middle.work_order = tp.work_order LEFT JOIN ( SELECT oro.work_order AS orderNo, oro.work_area_code AS lineCode, SUM ( submit_work_hours ) AS totalSubmitHours, '自制' AS workHourType FROM hm_model_trc_order_report_operation_u orou LEFT JOIN hm_model_trc_order_report_operation oro ON orou.work_order_process_id = oro.ID WHERE orou.work_order_process_id IS NOT NULL AND oro.work_area_code IS NOT NULL GROUP BY oro.work_order, oro.work_area_code UNION all SELECT ohs.work_order_no AS orderNo, ohs.line_code AS lineCode, SUM ( receiving_hour ) AS totalSubmitHours, '外委' AS workHourType FROM hm_model_outsourcing_hour_statistics ohs GROUP BY ohs.work_order_no, ohs.line_code ) sc ON middle.work_order = sc.orderNo AND middle.line_code = sc.lineCode AND middle.work_time_type = sc.workHourType LEFT JOIN hm_model_part_info AS pinfo ON tp.product_number = pinfo.part_code WHERE middle.process_time > 0 AND tp.delivery_time IS NOT NULL AND tp.production_orders LIKE'FJ2023051100286' ORDER BY to_char( to_timestamp( tp.delivery_time / 1000 ), 'yyyy-mm-dd' ) DESC, tp.parent_production_orders DESC, tp.node_level ASC

最新推荐

recommend-type

微软内部资料-SQL性能优化3

An isolation level determines the degree to which data is isolated for use by one process and guarded against interference from other processes. Prior to SQL Server 7.0, REPEATABLE READ and ...
recommend-type

微软内部资料-SQL性能优化5

The leaf level of an index is the only level that contains every key value, or set of key values. For a clustered index, the leaf level is the data itself, so in reality, a clustered index ALWAYS ...
recommend-type

基于SpringBoot框架的中小企业完全开源的ERP.zip

基于springboot的java毕业&课程设计
recommend-type

基于Springboot的健身信息系统.zip

基于springboot的java毕业&课程设计
recommend-type

zigbee-cluster-library-specification

最新的zigbee-cluster-library-specification说明文档。
recommend-type

管理建模和仿真的文件

管理Boualem Benatallah引用此版本:布阿利姆·贝纳塔拉。管理建模和仿真。约瑟夫-傅立叶大学-格勒诺布尔第一大学,1996年。法语。NNT:电话:00345357HAL ID:电话:00345357https://theses.hal.science/tel-003453572008年12月9日提交HAL是一个多学科的开放存取档案馆,用于存放和传播科学研究论文,无论它们是否被公开。论文可以来自法国或国外的教学和研究机构,也可以来自公共或私人研究中心。L’archive ouverte pluridisciplinaire
recommend-type

实现实时数据湖架构:Kafka与Hive集成

![实现实时数据湖架构:Kafka与Hive集成](https://img-blog.csdnimg.cn/img_convert/10eb2e6972b3b6086286fc64c0b3ee41.jpeg) # 1. 实时数据湖架构概述** 实时数据湖是一种现代数据管理架构,它允许企业以低延迟的方式收集、存储和处理大量数据。与传统数据仓库不同,实时数据湖不依赖于预先定义的模式,而是采用灵活的架构,可以处理各种数据类型和格式。这种架构为企业提供了以下优势: - **实时洞察:**实时数据湖允许企业访问最新的数据,从而做出更明智的决策。 - **数据民主化:**实时数据湖使各种利益相关者都可
recommend-type

SQL怎么实现 数据透视表

SQL可以通过使用聚合函数和GROUP BY子句来实现数据透视表。 例如,假设有一个销售记录表,其中包含产品名称、销售日期、销售数量和销售额等信息。要创建一个按照产品名称、销售日期和销售额进行汇总的数据透视表,可以使用以下SQL语句: ``` SELECT ProductName, SaleDate, SUM(SaleQuantity) AS TotalQuantity, SUM(SaleAmount) AS TotalAmount FROM Sales GROUP BY ProductName, SaleDate; ``` 该语句将Sales表按照ProductName和SaleDat
recommend-type

JSBSim Reference Manual

JSBSim参考手册,其中包含JSBSim简介,JSBSim配置文件xml的编写语法,编程手册以及一些应用实例等。其中有部分内容还没有写完,估计有生之年很难看到完整版了,但是内容还是很有参考价值的。
recommend-type

"互动学习:行动中的多样性与论文攻读经历"

多样性她- 事实上SCI NCES你的时间表ECOLEDO C Tora SC和NCESPOUR l’Ingén学习互动,互动学习以行动为中心的强化学习学会互动,互动学习,以行动为中心的强化学习计算机科学博士论文于2021年9月28日在Villeneuve d'Asq公开支持马修·瑟林评审团主席法布里斯·勒菲弗尔阿维尼翁大学教授论文指导奥利维尔·皮耶昆谷歌研究教授:智囊团论文联合主任菲利普·普雷教授,大学。里尔/CRISTAL/因里亚报告员奥利维耶·西格德索邦大学报告员卢多维奇·德诺耶教授,Facebook /索邦大学审查员越南圣迈IMT Atlantic高级讲师邀请弗洛里安·斯特鲁布博士,Deepmind对于那些及时看到自己错误的人...3谢谢你首先,我要感谢我的两位博士生导师Olivier和Philippe。奥利维尔,"站在巨人的肩膀上"这句话对你来说完全有意义了。从科学上讲,你知道在这篇论文的(许多)错误中,你是我可以依