阿尔卡特7750配置模板

合集下载

7750 SR-Series 路由器基本系统配置指南说明书

7750 SR-Series 路由器基本系统配置指南说明书

PrefaceAbout This GuideThis guide describes system concepts and provides configuration explanations and examplesto configure SR-OS boot option file (BOF), file system and system management functions.This document is organized into functional chapters and provides concepts and descriptions ofthe implementation flow, as well as Command Line Interface (CLI) syntax and commandusage.AudienceThis manual is intended for network administrators who are responsible for configuring the7750 SR-Seriesrouters. It is assumed that the network administrators have an understanding ofnetworking principles and configurations. Protocols, standards, and processes described in thismanual include the following:•CLI concepts•File system concepts•Boot option, configuration, image loading, and initialization procedures•Basic system management functions such as the system name, router location andcoordinates, and CLLI code, time zones, Network Time Protocol (NTP), SimpleNetwork Time Protocol (SNTP), and synchronization properties7750 SR OS Basic System Configuration GuidePrefaceList of Technical PublicationsThe 7750 SR documentation set is composed of the following books:•7750 SR OS Basic System Configuration GuideThis guide describes basic system configurations and operations.•7750 SR OS System Management GuideThis guide describes system security and access configurations as well as event loggingand accounting logs.•7750 SR OS Interface Configuration Guide•7750 SR OS Router Configuration GuideThis guide describes logical IP routing interfaces and associated attributes such as an IPaddress, as well as IP and MAC-based filtering, and VRRP and Cflowd.•7750 SR OS Routing Protocols GuideThis guide provides an overview of routing concepts and provides configuration examplesfor RIP, OSPF, IS-IS, BGP, and route policies.•7750 SR OS MPLS GuideThis guide describes how to configure Multiprotocol Label Switching (MPLS) and LabelDistribution Protocol (LDP).•7750 SR OS Services GuideThis guide describes how to configure service parameters such as service distributionpoints (SDPs), customer information, and user services.•7750 SR OAM and Diagnostic Guide•This guide describes how to configure features such as service mirroring and Operations, Administration and Management (OAM) tools.•7750 SR OS Triple Play GuideThis guide describes Triple Play services and support provided by the 7750 SR andpresents examples to configure and implement various protocols and services.•7750 SR OS Quality of Service GuideThis guide describes how to configure Quality of Service (QoS) policy management.•OS Multi-Service ISA GuideThis guide describes services provided by integrated service adapters such as ApplicationAssurance, IPSec, ad insertion (ADI) and Network Address Translation (NAT).•7750 SR-OS RADIUS Attributes Reference GuideThis guide describes all supported RADIUS Authentication, Authorization andAccounting attributes.Page 127750 SR OS Basic System Configuration GuidePrefaceTechnical SupportIf you purchased a service agreement for your 7750 SR router and related products from adistributor or authorized reseller, contact the technical support staff for that distributor or resellerfor assistance. If you purchased an Alcatel-Lucent service agreement, contact your welcomecenter:/wps/portal/supportReport documentation errors, omissions and comments to:**************************************Include document name, version, part number and page(s) affected.7750 SR OS Basic System Configuration Guide Page 13PrefacePage 147750 SR OS Basic System Configuration Guide。

7750&7710产品介绍-v2

7750&7710产品介绍-v2

对承载网的可运营可管理要求
快速提供业务
智能故障、设备管理 智能业务统计流量分析 全面的安全管理
对承载网QoS的要求
端到端带宽保证 承载网时延≤40ms;最低要求≤100ms 承载网时延抖动≤10ms;最低要求≤20ms 丢包率≤0.1% ;最低要求≤1%
PE Router
Switch Fabric / CPU 模块架构
SF/CPM A
Switch Fabric A
FRMR
CPM complex A T Chip Q Chip
Alcatel 7750 SR: 模块化接口
模块化设计 混合-和-匹配式接口类型, 优化插槽利用率的 速率和传输范围 贯穿7750SR产品线的MDA/SFP的便利性最大限 度的保护了投资 热插拔MDA和光器件 丰富的连接性选项


领先的端口密度
丰富的 ATM, SONET/SDH 和 Ethernet MDA 连 接性的选择 任何 业务/任意接口
,Belgium
比利时安特卫普 Russia俄罗斯圣彼得堡 Canada加拿大渥太华
St Petersborg
Ottawa
Marcoussis,France
法国Marcoussis US美国普莱诺
Stuttgart,Germany
德国斯图加特
Plano
Shanghai,China 中国上海
Search/ Control Memory
Search/ Control Memory
Programmable Packet Processor
Programmable Packet Processor
CAM
P

7750介绍

7750介绍

7750 SR的设计超越了运营商对硬件和软 件可靠性最严格的要求。7750 SR具有以 下能提高网络可用性的特性:
> 领先的控制平面和转发平面性能:
• OSPF、ISIS和BGP的快速收敛 • 在同时部署数千条LSP的情况下实现
小于50ms的MPLS快速重路由 硬件特性 7750 SR是一个完全冗余的系统,没有单 点故障。 > 在所有通用的系统组件上提供1:1的冗 余
运作,且通常成本昂贵。与这些架构和 设计相比,NPA能为客户带来显著的价 值和投资保护。 FLEXIBLE FAST PATH转发技术的性能和功 能确保了7750 SR具有最快交换速度和密 度的同时,具备在IP/MPLS网络基础设施 上提供新的高级业务所需的可编程能力 和数据包处理智能。
• 1:16的交换矩阵组件冗余和graceful
统,能够使用向导或点击配置从单一应 用模板中提供端到端业务,而不必一步 步地逐个配置业务路径上的每个设备。 5620 SAM大大减少了复杂业务供应流 程。
7750 SR还支持针对多点虚拟专用以太网 (VPLS/H-VPLS)业务的草案draft-ppvpn。 vpls-ldp(先前的draft-lasserre-vkompella)
在入口上,7750 SR输入缓存业务,然后 将其流量整形成一个带有承诺信息速率 (CIR)和峰值信息速率(PIR)类型保证
基于业务的记帐和计费
通过FLEXIBLE FAST PATH,7750 SR支持 基于业务的队列功能,以及提供对全套 粒度统计的硬件支持。因此,7750 SR能 够对每个业务或每个数据流进行统计。 这通过将业务(或业务内的数据流)动 态分配到独有的队列来完成。所有计数 器对每个业务进行计数。7750 SR能够支 持对数千个并发业务的统计结果的收集, 而不影响系统性能。另外,本地数据存 储器可以保留几天的统计记录。对于复 杂的基于目的地址的计费方案,7750 SR 能够把路由表分成数个区域,并跟踪流 量的源和目的地址,从而能够进行区分 计费。

Alcatel-Lucent 7750 SERVICE ROUTER 接口配置指南说明书

Alcatel-Lucent 7750 SERVICE ROUTER 接口配置指南说明书

Alcatel-Lucent 7750SERVICE ROUTER | RELEASE 13.0.R4 INTERFACE CONFIGURATION GUIDEAlcatel-Lucent – Proprietary & ConfidentialContains proprietary/trade secret information which is the property of Alcatel-Lucent. Not to be made available to, or copied or used by anyone who is not an employee of Alcatel-Lucent except when there is a valid non-disclosure agreement in place which covers such information and contains appropriate non-disclosure and limited use obligations.Copyright 2015 © Alcatel-Lucent. All rights reserved.All specifications, procedures, and information in this document are subject to change and revision at any time without notice. The information contained herein is believed to be accurate as of the date of publication. Alcatel-Lucent provides no warranty, express or implied, regarding its contents. Users are fully responsible for application or use of the documentation.Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.Copyright 2015 Alcatel-Lucent.All rights reserved.DisclaimersAlcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent ofAlcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.。

SR配置规范

SR配置规范

7750SR路由器配置规范上海贝尔阿尔卡特股份有限公司互联网事业部二零零六年十一月目录1.概述阿尔卡特7750SR路由器是业内第一个专为高级互联网和虚拟专用网络(VPN)业务而设计和优化的IP/MPLS业务路由器。

阿尔卡特7750SR有三种尺寸可供选择:单槽、7槽和12槽,可提供具有卓越性能和高密度的各种接口。

作为目前业内最具扩展性的路由器平台,阿尔卡特7750SR具有为高效传送基于服务等级协议(SLA)的业务而设计的软件和硬件架构,因此阿尔卡特7750SR不仅仅是强大的互联网路由器,更是一个灵活、强大的业务供应平台。

为正确配置7750SR系列路由器,需完成引导文件配置,系统管理功能配置,IOM/MDA/Port等板卡端口配置,相关路由协议配置,以及7750SR定义的各种Service和QoS配置等。

本规范针对用户日常维护工作中常用的配置任务编写,并提供配置实例,未涉及的内容用户可参考7750SR配置指导手册,表1列出各配置任务对应的指导手册名称便于用户进行针对性查找。

2.3.硬件板卡配置7750SR路由器的IOM和MDA板卡只有在配置命令与板卡类型匹配后方可启动,可以事先将IOM和MDA板卡类型部署上,防止错误板卡插入;当板卡在未配置时插入后,可通过show card/mda命令查看板卡类型,此时板卡运行状态为down。

配置IOM模块,事先需确认IOM模块的准确类型:7750SR# configure card 37750SR>config>card# card-type ?- card-type <card-type>- no card-type<card-type> : iom-20g|iom2-20g|iom-20g-b7750SR>config>card# card-type iom-20g-b7750SR>config>card# no shutdown配置MDA模块,事先需确认MDA模块的准确类型:7750SR>config>card# mda 17750SR>config>card>mda# mda-type ?- mda-type <mda-type>- no mda-type<mda-type> : m60-10/100eth-tx|m10-1gb-sfp|m16-oc12/3-sfp|m8-oc12/3-sfp|m16-oc3-sfp|m8-oc3-sfp|m4-oc48-sfp|m1-oc192|m5-1gb-sfp|m12-chds3|m1-choc12-sfp|m1-10gb|m4-choc3-sfp|m2-oc48-sfp|m20-100eth-sfp|m20-1gb-tx|m2-10gb-xfp|m4-atmoc12/3-sfp|m16-atmoc3-sfp|m20-1gb-sfp|m4-chds3|m1-10gb-xfp|vsm-cca|m5-1gb-sfp-b|m10-1gb-sfp-b|m4-choc3-as-sfp7750SR>config>card>mda# mda-type m10-1gb-sfp7750SR>config>card>mda# back7750SR>config>card# info----------------------------------------------card-type iom-20g-bmda 1mda-type m10-1gb-sfpexit----------------------------------------------删除MDA模块:7750SR>config>card# mda 17750SR>config>card>mda# shutdown7750SR>config>card>mda# exit7750SR>config>card# no mda 1删除IOM模块(事先需确保该IOM下所有MDA模块均已删除): 7750SR>config>card# back7750SR>config# no card 32.4.设备名称配置配置内容:配置设备名称规范要求:设备名称要求符合配置有关命名规范;配置示例:#configure system name “R1-C-xxx-1”2.5.系统时间配置配置内容:配置系统时间;规范要求:系统时间要求采用标准北京时间;配置示例:#configure system time zone GMT8 08 10.1.1 key 2 preferserver 10.1.1.2 key 2no shutdown2.6.主备卡切换配置配置内容:配置系统引擎冗余模式规范要求:系统支持NSR功能配置示例在版本,配置了双SF/CPM的7750SR路由器在主备CPM切换时可保证不间断路由(Non stop routing)、不间断业务(Non stop service)Nonstop Routing (NSR)NSR可保证CPM切换时BGP,LDP,OSPF,ISIS等路由Session不终断,对端路由器不会感知到任何变化。

7750硬件介绍

7750硬件介绍


200809
SR系列
7750 SR-12
宽带 (全双工, 冗余) I/O 插槽 介质相关适配器 (MDAs) 400G 10 20 AC Power (1 + 1) DC Power (1 + 1) Cooling Fans (2 + 1) 交换矩阵/控制处理器模块 (SF/CPM) (1 + 1) 24.5”H x 17.5”W x 25.25”D

200809
Alcatel SR IOM – 流量管理器
Memory Memory
流量管理器(TM)
CAM
NP
NP
输入 输出
Ingress TM
Memory
Egress TM
NP
Memory CAM
Memory
F A
• • • • •
负责缓冲,管理,整形,和其他QoS功能 同一芯片集可用于输入和输出 8K输入和输出队列 每个队列计算器都用于计费政策 输入和输出上200 ms缓冲的排队率

200809
IOM架构 &数据包流
SF/CPM A MAC
MAC
M D A M D A
CAM MEM
NP
2 1
NP
MEM
4
Switch Fabric A
TM TM
SE
Fabric Access
5
3
CAM MEM CAM
NP NP NP
MEM
SE
Framer
CPU
CONTROL PLANE
SF/CPM
CPU FFPC CPU
• 10 Gb/s物理接口终 端 • 以太网, SONET/SDH, 信道化的 SONET/SDH • 可插拔接口模块和可 插拔光接口

阿尔卡特7750配置文档

阿尔卡特7750配置文档

上海贝尔阿尔卡特7750SR配置标准模板目录一、硬件配置 (5)1.1配置IOM卡 (5)1.1.1 查看已经插入的IOM卡的类型 (5)1.1.2正确配置IOM卡的类型 (5)1.2配置MDA卡 (5)1.2.1查看已经插入的MDA卡的类型 (5)1.2.2正确配置MDA卡的类型 (5)1.3配置MDA端口 (6)1.3.1 POS端口配置 (6)1.3.2 以太口配置 (6)1.3.3 查看port信息 (6)二、设备管理配置 (7)2.1配置路由器名称、LOCATION、CONTACT (7)2.2配置系统时间 (7)2.3配置SNTP (7)2.3.1 打开SNTP(简单网络时间协议) (7)2.3.2 配置SNTP地址 (7)2.4配置SR为TELNET服务器 (7)2.5配置TELNET登陆限制 (8)2.5.1 配置默认动作为允许,因为是所有上主控板的流量。

(8)2.5.2 配置允许IP段的ACL,配置源IP,协议,目的端口 (8)2.5.3 配置一条拒绝的ACL,拒绝其他IP段。

(8)2.6配置用户 (8)2.6.1 配置用户名 (8)2.6.2 配置用户密码 (8)2.6.3 配置用户登陆方式 (9)2.6.4 配置用户所属的组 (9)2.7配置LOG (9)2.7.1 配置log-id (9)2.7.2 配置log信息类型 (9)2.7.3 配置记录log的方式 (9)2.7.4 配置记录log方式的具体配置 (9)2.8配置SNMP (10)2.9配置主备板同步 (10)2.9.1 配置自动同步 (10)2.9.2 手工同步命令 (10)2.10配置空闲时间 (10)2.11配置ANTI-SPOOF (10)三、路由配置 (11)3.1配置路由器系统地址 (11)3.2配置网络接口 (11)3.2.2 配置IP地址 (11)3.2.3 配置关联端口 (11)3.2.4 查看配置的路由器接口 (11)3.3配置静态及OSPF路由协议 (12)3.3.1 配置静态路由 (12)3.3.2 配置OSPF区域 (12)3.3.3 配置ospf接口cost值 (12)3.3.4 配置一个stub区域 (12)3.3.5 配置NSSA区域 (12)3.3.6 配置虚链路 (13)3.3.7 配置认证 (13)3.3.8配置路由聚合 (13)3.3.9 配置静态路由注入到OSPF路由协议 (13)3.3.10 查看运行在ospf协议下的接口 (14)3.3.11 查看ospf邻居建立关系 (14)3.3.12 查看ospf路由表 (14)3.4配置IS-IS (14)3.4.1 配置区域ID (14)3.4.2 配置路由器等级能力 (15)3.4.3 配置IS-IS接口 (15)3.4.4 查看ISIS下的接口 (15)3.4.5 添加已经配置到ISIS的每个网络接口 (15)3.4.6 查看ISIS邻接关系 (15)3.4.7 查看ISIS路由表 (15)3.5BGP配置 (16)3.5.1 创建AS (16)3.5.2 配置路由器 ID5 (16)3.5.3 配置 BGP (16)3.6配置POLICY (16)3.6.1 配置policy名称 (16)3.6.2 配置从静态路由分布到ospf路由协议中的policy (17)3.6.3 配置commit使之生效 (17)3.6.4 应用policy (17)3.7IP F ILTER配置 (17)3.7.1创建ip filter (17)3.7.2 指定默认动作 (17)3. 7.3 创建条目,指定动作、源、目的IP (17)3.7.4 应用ip filter (18)四、 MPLS 配置以及业务配置 (19)4.1MPLS配置 (19)4.1.1 MPLS接口配置 (19)4.1.3 配置 MPLS LSP和主路径 (19)4.1.4 查看命令 (20)4.1.5 改变每个网络接口的最大传输单元(MTU)尺寸 (20)4.2 E P IPE 配置 (20)4.2.1 创建客户并将其与提供的业务相关联 (20)4.2.2 指向客户的接口(在我们的网络中由膝上电脑表示)称为“toCustomer”,必须配置为接入接口。

阿尔卡特AK7750业务配置总结

阿尔卡特AK7750业务配置总结
anti-spoof nh-mac
static-host ip 10.1.96.2 create
no shutdown
exit
的路由 发布
2、前缀列表中包含发布的精确路由。
3、配置一个策略,名称和前缀列表一致
4、策略的条目以10开始,并以10为步长以便后期插入策略。
5、明确配置路由的from和要导入的目标路由协议,并明确动作。
===================================================前提说明===============================================================================================
router
policy-statement "ies2bgp" // 创建策略
entry 10
from
prefix-list "ies2bgp"
exit
《说明:NMS业务本次不作为备份业务,在主用侧配置就行了。》
ies 101102 customer 10 create
subscriber-interface "LiShu-OLT-ONU-nms" create //subscriber-interface情况,名称为ip_IP地址,如ip_1.1.1.1/24,
description "YuXi_ZX_OLT"
ethernet
mode access // 配置端口模式
encap-type qinq //配置端口qinq模式
egress-scheduler-policy "egress" //业务接入接口引用接口队列调度策略

Alcatel-7750配置指南

Alcatel-7750配置指南

Alcatel 7750 SR 配置指南1.设备配置命令说明 (2)3.1 S YSTEM基本配置 (2)3.2 L OG配置 (3)3.3 P ORT配置 (3)3.4 ISIS协议配置 (5)3.5 M PLS、LDP协议配置 (6)3.6 S ECURITY 配置 (7)3.7 VPN-BGP配置 (9)3.8 P OLICY配置 (10)3.9 S ERVICE配置 (11)3.10 IES业务配置 (11)3.11 VPLS 业务配置 (13)3.12 VPRN业务配置 (15)2.故障排除方法说明 (17)2.1 光路正常但PORT端口DOWN (17)2.2 PING 不通对端地址 (17)2.3 ISIS邻接关系无法建立 (18)2.4 BGP邻居无法正常建立 (18)2.5 BGP表中有路由,但路由没有被放进VPN路由表中 (18)2.6 VPN中用户CE设备无法访问远端 (18)3.业务运行状态检查命令 (19)3.1 查看S ERVICE业务运行状态 (19)3.2 检查路由器接口运行状态 (19)3.3 查看设备P ORT端口运行状态 (20)3.4 查看设备MAC地址表信息 (21)4.删除SERVICE配置步骤 (22)1.设备配置命令说明3.1 System基本配置1.chassis-mode 要配置为C,以支持新的feature。

2.telnet 的session限制为设置为最大数7。

3.时区自定义为BEIJ 08。

配置示例:systemname "YZ-SYL-R-AC7750-01"chassis-mode csnmppacket-size 9216exitlogin-controltelnetinbound-max-sessions 7outbound-max-sessions 7exitno login-bannerexittimesntpshutdownexitzone BEIJ 08exitthresholdsrmonexitexitexit检查命令:show chassis 查看chassis mode是否为C。

Alcatel7750 确认单板指导

Alcatel7750 确认单板指导

Alcatel 7750 扩板操作指导三.设备相关操作(1).联机串口配置(需使用厂家的串口线,其它串口线均不能用)配置终端好后,因SR7750为双主控板SF/CPM,我们要插到主用主控板上的console口,才能登入设备。

辨别主用主控板还是备用主控板时,我们需要看主控板上的CTL灯,显示为绿色常亮为主用主控板,显示是绿色闪烁的为备用主控板。

主控板CPM的其它灯的显示说明,请参照另一个文档设备的有没有插及插了多少块IOM板及MDA板,通过主控板上的灯是看不出来的,本身它就不具备此功能。

(2)在扩容之前,为安全起见我们需做设备配置的保存: admin save保存好后,需采集目前设备配置:admin display-config 多按几下回车键,才能采完(3)插板顺序,先插IOM板,再插MDA板(4)在插IOM板时一定要注意,主控板和IOM板上有保护胶套要先卸下才能插入槽位,否则板卡是插不位的, 无法加电。

如图:大卡为IOM卡,小卡为MDA卡(5)按设计的槽位插入IOM板卡,插入设备后,需用命令确认能否工作正常A:7750SR12# show card state/查看刚插好的IOM单板具体型号及槽位号,其中的槽位号是从设备面板上看出来的,也可以用此命令看。

我们刚插上的IOM板的型号及槽位号,在此命令下是有显示的,只是该板的admin state和oper state的状态没有达到UP。

确认IOM板命令如下:A:7750SR12#configure card X card-type XXX/具体板卡情况依实际情况定义第一个X代表设备是槽位号,XXX代表IOM的具体型号.这里就是要用到show card state显示的结果了。

确认IOM板卡后,稍等片刻,可以查看其是否工作正常了,命令如下:A:7750SR12#show card state/查看新插入IOM单板的运行状态,待新插入的IOM单板的admin state和oper state为UP状态后进入下一步操作。

7750SR 设备介绍

7750SR 设备介绍
Combo IMMs
Presentation Title — 15
All rights reserved © 2011
FP3: 业务性能极大扩展
FP1 Scale
FP2 Scale
New!
FP3 Scale
IP Route Table
L3 Interfaces
VPRN Instances VPLS Instances
Alcatel-Lucent 7750 业务路由器
输入/输出 模块 (IOM-FP1)
每块IOM支持两 个可热插拔的 MDA
灵活的,完全可编程的转发体
以线速(10 Gb/s)进行处理
IOM2-20G
Ctrl. RAM
Ctrl. RAM
到交换矩阵的冗余连 接 (SR-7/12 )
M D
NPU ‘P’ Chip
Presentation Title — 6
All rights reserved © 2011
5Tbps 系统背板
•10 个20/50/100 G IOM •20个MDA
Alcatel-Lucent 7750 路由器 SR-7系统组成
灵活快速路径转发 阵列
10 MDA
5个输入/输出 模块(IOM))
All rights reserved © 2011
100G IMM 平台
100G IMM结构图
• 充分利用FP2 100G能力 • 在输入输出2个方向分别采用
P2/Q2 芯片组 • 采用2个T2 连接

12p 10GE IMM 1p 100GE IMM
.
XB200G Layout)
RLDRAM-II RLDRAM-II RLDRAM-II RLDRAM-II

7750 SR高级配置指南.pdf_1701706365.4593518说明书

7750 SR高级配置指南.pdf_1701706365.4593518说明书

ESM IPv4: Multicast in a Wholesale/RetailScenarioIn This ChapterThis section describes ESM IPv4 multicast configurations in a wholesale/retail scenario.Topics in this section include:•Applicability on page 2126•Overview on page 2127•Configuration on page 2129•Conclusion on page 21407750 SR Advanced Configuration Guide Page 2125ApplicabilityApplicabilityThis configuration example is applicable to the 7750 SR-7/12/12e with IOM3-XP and IMMs, the7450 ESS -7/12 chassis in mixed mode with IOM3-XP and IMMs, and also to the 7750 SR-c4/12platforms, and requires chassis mode C as a minimum. Note that the 7450 will only operate as anL2TP Access Concentrator (LAC) for L2TP services.The configuration was tested on release 11.0.R1 and covers both IPoE and PPPoE subscribers. Page 21267750 SR Advanced Configuration GuideESM IPv4: Multicast in a Wholesale/Retail Scenario OverviewAlcatel-Lucent’s Triple Play Service Delivery Architecture (TPSDA) allows operators to integrateHigh Speed Internet (HSI), voice and video services within a single network infrastructure. Thegoal of this configuration example is to provide a walk through of a wholesale/retail multicastsetup.There are two wholesale/retail models in TPSDA. In the first model, the retail service is co-locatedwith the wholesale service whereas in the second model, for PPP services only, the retail service ison a separate BNG. The network topology shown in Figure334 is the first model. It consists oftwo 7750s; BNG-1 is a wholesaler Broadband Network Gateway (BNG) with the retail service co-located and the second is a retailer router. Figure335 shows the second model where the retailservice is a separate router and the connection between the wholesale and retail utilizes L2TP. The7450 in both cases is used as an aggregation switch to aggregate all subscribers.Figure 334: Wholesale/Retail Model 1Figure 335: Wholesale/Retail Model 27750 SR Advanced Configuration Guide Page 2127OverviewThe second 7750 is connected directly to the multicast source. On the access side, the BNG isconnected to an aggregation switch aggregating both PPPoE and IPoE subscribers.There are two basic requirements for a subscriber to receive multicast streams. First, the groupinterface for the subscribers must have IGMP enabled. Second, the Enhanced SubscriberManagement (ESM) subscriber must be allowed to receive multicast streams by having IGMPenabled. When both requirements are met, the BNG will process the subscribers’ IGMP messages,otherwise, IGMP messages are dropped. All customer premise device (CPE) originated IGMPmessages are aggregated via the 7450 and passed onto the wholesale BNG. It is always the retailVPRN that processes the IGMP messages. The wholesale VPRN SAPs performs the forwardingof the actual multicast streams.Page 21287750 SR Advanced Configuration GuideESM IPv4: Multicast in a Wholesale/Retail Scenario ConfigurationNote that a basic knowledge of multicast and ESM is assumed.ESM Wholesale-Retail MulticastThere are various ways to provide wholesale and retail multicast function.•For the IPoE and PPPoE Layer 3 wholesale/retail model, the wholesale and the retailservices reside on separate VPRNs.•For the PPPoE Layer 2 wholesale/retail model, L2TP is used.ESM Layer 3 Wholesale-Retail MulticastFigure336 depicts a Layer 3 wholesale/retail scenario for both IPoE and PPPoE. The first BNGcontains both the wholesale and retail configuration. There are two options for the retail BNG todeliver the multicast streams to the wholesale BNG:1.MVPN between the BNGsor2.If using a routed interface between the BNGs, multicast routing is required.This example will use the second option for delivery of the multicast streams in order to keep theconfiguration simple.Figure 336: Layer 3 Wholesale/Retail7750 SR Advanced Configuration Guide Page 2129ESM Layer 3 Wholesale-Retail MulticastStep 1.Below is a configuration extract from the wholesale service on BNG-1 with the group interface added to IGMP. This configuration applies to both IPoE and PPPoE.*A:BNG-1> config>service>vprn>sub-if# info----------------------------------------------unnumbered “system”group-interface "wholesale-sub-int-1" createdhcpclient-applications dhcp pppno shutdownexitauthentication-policy "auth-policy-1"sap 1/1/5:1 createsub-sla-mgmtdef-sub-id use-sap-iddef-sub-profile "multicast-profile-1"def-sla-profile "sla-profile-1"sub-ident-policy "sub-ident-policy-1"multi-sub-sap 10no shutdownexitexitpppoesession-limit 10sap-session-limit 10no shutdownexitexitigmpgroup-interface "wholesale-group-int-1"no shutdownexitno shutdownexitStep 2.Also on BNG-1, a separate VPRN is configured for the retailer. The retail configuration is a little different from the wholesale configuration. Below is a configuration extract fromthe retail VPRN with IGMP enabled. This configuration is applicable to both IPoE andPPPoE. The multicast streams received in the retail VPRN are forwarded to the wholesaleVPRN. Other retail VPRNs can offer multicast streams as well, and the same multicastaddresses can be re-used as long as the address is assigned to a different retail VPRN.*A:BNG-1> config>service>vprn# info----------------------------------------------route-distinguisher 65536:2subscriber-interface "retail-sub-int-1" fwd-service 1fwd-subscriber-interface "wholesale-sub-int-1" createaddress 10.255.255.254/8dhcpserver 192.168.0.1client-applications dhcp pppgi-address 10.255.255.254lease-populate 10no shutdownPage 21307750 SR Advanced Configuration GuideESM IPv4: Multicast in a Wholesale/Retail Scenario exitexitigmpgroup-interface fwd-service 1 "wholesale-group-int-1no shutdownexitexitospf 192.168.2.2area 0.0.0.0interface "system"no shutdownexitinterface "retail-sub-int-1"no shutdownexitinterface "int-BNG-1-BNG-2"no shutdownexitexitexitpiminterface "int-BNG-1-BNG-2"exitexitStep 3.Per host replication is mandatory in a wholesale/retail scenario. A single wholesale SAP might be shared among different retailers. A wholesale host that has requested a multicastgroup will always have the multicast delivered directly. Other hosts on the SAPs mightbelong to a different retailer and therefore 1) retailers might not have the same multicastgroup and sources and 2) their bandwidth should not be impacted by other hosts’multicast. Per-host replication is configured in the igmp-policy igmp-policy-1. This ismandatory for both IPoE and PPPoE subscribers.*A:BNG 1> config>subscr-mgmt>igmp-policy# info----------------------------------------------per-host-replicationStep 4.The interfaces are added to OSPF and to PIM on the retail BNG that is connected to the multicast source.*A:BNG-2> config>service>vprn# info----------------------------------------------ospfarea 0.0.0.0interface "system"no shutdownexitinterface "int-BNG-2-BNG-1"no shutdownexitinterface “int-multicast-source”no shutdownexitexitexit7750 SR Advanced Configuration Guide Page 2131ESM Layer 3 Wholesale-Retail Multicastpiminterface "int-BNG-2-BNG-1"exitinterface "int-multicast-source"exitrpstaticaddress 192.168.4.1group-prefix 224.0.0.0/4exitexitexitexitWith the above the configuration, the wholesale/retail setup is ready to process IGMP messages.Now send an IGMPv3 request to the wholesale SAP. The (S,G) is (192.168.4.2, 239.255.1.1) andthe subscriber IP address is 10.0.0.2. The output below shows that the (S,G) is not registered in thewholesale VPRN but is in the retail VPRN.*A:BNG-1> show router 1 igmp group===============================================================================IGMP Interface Groups==============================================================================================================================================================IGMP Host Groups==============================================================================================================================================================IGMP SAP Groups===============================================================================No Matching Entries===============================================================================*A:BNG-1> show router 2 igmp group===============================================================================IGMP Interface Groups==============================================================================================================================================================IGMP Host Groups===============================================================================(192.168.4.2,239.255.1.1)Fwd List : 10.0.0.2 Up Time : 0d 00:13:01===============================================================================IGMP SAP Groups===============================================================================-------------------------------------------------------------------------------(*,G)/(S,G) Entries : 1===============================================================================Page 21327750 SR Advanced Configuration GuideESM IPv4: Multicast in a Wholesale/Retail ScenarioTo view all subscribers’ (S,G) pairs, use the following command.*A:BNG-1> show service active-subscribers igmp detail===============================================================================Active Subscribers Detail===============================================================================Subscriber IGMP-PolicyHostAddr GrpItf NumGroupsGrpAddr Type Up-Time ModeSrcAddr Type Blk/Fwd-------------------------------------------------------------------------------video_user_01 igmp-policy-110.0.0.2 whole-sale 1239.255.1.1 Dynamic 0d 01:37:55 Include192.168.4.2 Dynamic Fwd-------------------------------------------------------------------------------Number of Subscribers : 1===============================================================================Only the retail VPRN is responsible for processing the IGMP messages. Therefore to troubleshoota wholesale/retail setup, debug is only relevant on the retail router instance.debugrouter "2"igmpgroup-interface fwd-service "1" "whole-sale"host "10.0.0.2"packet mode egr-ingr-and-droppedexitexit7648 2013/05/24 16:59:41.02 EST MINOR: DEBUG #2001 vprn2 IGMP[14]"IGMP[14]: RX-PKT[013 07:56:53.680] IGMP host 10.0.0.2 V3 PDU: 10.0.0.2 -> 224.0.0.22 pduLen20Type: V3 REPORT maxrespCode 0x0 checkSum 0xddf6Num Group Records: 1Group Record 0Type: ALW_NEW_SRCS, AuxDataLen 0, Num Sources 1Mcast Addr: 239.255.1.1Source Address List192.168.4.2"7649 2013/05/24 16:59:41.02 EST MINOR: DEBUG #2001 vprn2 IGMP[vprn2 inst 14]"IGMP[vprn2 inst 14]: igmpIfGroupAddAdding 239.255.1.1 to IGMP host 10.0.0.2 database"7650 2013/05/24 16:59:41.02 EST MINOR: DEBUG #2001 vprn2 IGMP[vprn2 inst 14]"IGMP[vprn2 inst 14]: igmpProcessGroupRecProcess group rec ALW_NEW_SRCS received on host 10.0.0.2 for group 239.255.1.1 in mode INCLUDE. Num srcs 1"7750 SR Advanced Configuration Guide Page 2133ESM Layer 3 Wholesale-Retail Multicast7651 2013/05/24 16:59:41.02 EST MINOR: DEBUG #2001 vprn2 IGMP[vprn2 inst 14]"IGMP[vprn2 inst 14]: igmpIfSrcAddAdding i/f source entry for host 10.0.0.2 (192.168.4.2,239.255.1.1) to IGMP fwdListDatabase, redir if N/A"The same debug command can be used for troubleshooting IGMP leave messages as shownbelow.7652 2013/05/24 16:59:43.90 EST MINOR: DEBUG #2001 vprn2 IGMP[14]"IGMP[14]: RX-PKT[013 07:56:56.560] IGMP host 10.0.0.2 V3 PDU: 10.0.0.2 -> 224.0.0.22 pduLen20Type: V3 REPORT maxrespCode 0x0 checkSum 0xdcf6Num Group Records: 1Group Record 0Type: BLK_OLD_SRCS, AuxDataLen 0, Num Sources 1Mcast Addr: 239.255.1.1Source Address List192.168.4.2"7653 2013/05/24 16:59:43.90 EST MINOR: DEBUG #2001 vprn2 IGMP[vprn2 inst 14]"IGMP[vprn2 inst 14]: igmpProcessGroupRecProcess group rec BLK_OLD_SRCS received on host 10.0.0.2 for group 239.255.1.1 in mode INCLUDE. Num srcs 1"7654 2013/05/24 16:59:43.90 EST MINOR: DEBUG #2001 vprn2 IGMP[vprn2 inst 14]"IGMP[vprn2 inst 14]: igmpProcessIfSrcTimerExpSource Timer expired for IGMP host 10.0.0.2 (192.168.4.2,239.255.1.1)"7655 2013/05/24 16:59:43.90 EST MINOR: DEBUG #2001 vprn2 IGMP[vprn2 inst 14]"IGMP[vprn2 inst 14]: igmpIfSrcDelDeleting i/f source entry for host 10.0.0.2 (192.168.4.2,239.255.1.1) from IGMP Database. DeleteFromAvl: 1 !Redir 0"7656 2013/05/24 16:59:43.90 EST MINOR: DEBUG #2001 vprn2 IGMP[vprn2 inst 14]"IGMP[vprn2 inst 14]: igmpIfGroupDelDeleting 239.255.1.1 from IGMP host 10.0.0.2 database"Page 21347750 SR Advanced Configuration GuideESM IPv4: Multicast in a Wholesale/Retail ScenarioESM L2TP Wholesale/Retail MulticastAs previously mentioned, the other option for PPPoE wholesale/retail is to use an L2TPconnection as shown in Figure337. LAC-1 contains the wholesale configuration while LNS-1contains the retail configuration.Figure 337: L2TP Wholesale-Retail MulticastBelow is a configuration extract for the wholesale L2TP Access Concentrator (LAC) in thewholesale service. It is using the local database, under the pppoe user-db configuration, toauthenticate the subscriber. The wholesale LAC does not process any IGMP messages so it passesall messages to the retailer LNS.*A:LAC-1> config>service>vprn>sub-if# info----------------------------------------------description "L2TP"unnumbered “system”group-interface "LAC-sub-int-1" createsap 1/1/11:222 createsub-sla-mgmtdef-sub-id use-sap-iddef-sub-profile "multicast-profile-1def-sla-profile "sla-profile-1"sub-ident-policy "sub-ident-policy-1"multi-sub-sap 10no shutdownexitexitpppoesession-limit 10sap-session-limit 10user-db "ppp-db-1"no shutdownexitexitl2tpgroup "l2tp-group-1" create7750 SR Advanced Configuration Guide Page 2135ESM L2TP Wholesale/Retail Multicasttunnel "tunnel-1" createauto-establishlocal-name "LAC"peer 192.0.2.3no shutdownexitno shutdownexitno shutdownThe retailer BNG serves as the L2TP Network Server (LNS). Below is a configuration extract forthe LNS. IGMP must be enabled on the ESM group-interface in the retail service.*A:LNS-1> config>service>vprn>sub-if# info----------------------------------------------address 10.255.255.254/8group-interface "LNS-group-int-1" lns createsap-parameterssub-sla-mgmtdef-sub-id use-sap-iddef-sub-profile "multicast-profile-1def-sla-profile "sla-profile-1"sub-ident-policy "sub-ident-policy-1"multi-sub-sap 10no shutdownexitexitdhcpserver 192.168.0.1client-applications pppgi-address 10.255.255.254lease-populate 10no shutdownexitexitl2tpgroup "l2tp-group-1" createtunnel "tunnel-1" createlns-group 1pppauthentication-policy "auth-policy-1"default-group-interface "LNS-group-int-1" service-id 1mtu 1500proxy-authentication alwaysproxy-lcp alwaysexitremote-name "LAC"no shutdownexitno shutdownexitno shutdownigmpgroup-interface "LNS-group-int-1"no shutdownexitno shutdownPage 21367750 SR Advanced Configuration GuideESM IPv4: Multicast in a Wholesale/Retail Scenario With the above configuration applied, the wholesale/retail multicast setup can be verified. Firstly,send an IGMP message from the subscriber, the example below uses IGMPv3. The (S,G) sent is(192.168.4.2, 239.255.1.1) from the subscriber with IP address 10.0.0.2. The show commandsbelow can be used to verify the multicast group being sent to the subscriber.*A:LNS-1> show service active-subscribers igmp detail===============================================================================Active Subscribers Detail===============================================================================Subscriber IGMP-PolicyHostAddr GrpItf NumGroupsGrpAddr Type Up-Time ModeSrcAddr Type Blk/Fwd-------------------------------------------------------------------------------LNS1-pppoe-sub-01 igmp-policy-110.0.0.2 LNS 1239.255.1.1 Dynamic 0d 00:04:41 Include192.168.4.2 Dynamic Fwd-------------------------------------------------------------------------------Number of Subscribers : 1===============================================================================The IGMP group is not seen in the wholesale router instance (as shown by the first output belowon LAC-1), however, it is seen in the retail router instance (as shown by the second output belowon LNS-1).*A:LAC-1> show router 1 igmp group===============================================================================IGMP Interface Groups==============================================================================================================================================================IGMP Host Groups==============================================================================================================================================================IGMP SAP Groups===============================================================================No Matching Entries===============================================================================*A:LNS-1> show router 1 igmp group===============================================================================IGMP Interface Groups==============================================================================================================================================================IGMP Host Groups===============================================================================(192.168.4.2,239.255.1.1)Fwd List : 10.0.0.2 Up Time : 0d 00:08:27===============================================================================IGMP SAP Groups===============================================================================-------------------------------------------------------------------------------7750 SR Advanced Configuration Guide Page 2137ESM L2TP Wholesale/Retail Multicast(*,G)/(S,G) Entries : 1===============================================================================Only the retail BNG (LNS-1) is responsible for processing the IGMP messages. Therefore totroubleshoot ESM multicast for an L2TP service, the following debug commands are used on theLNS.debugrouter "1"igmpgroup-interface "LNS-01"host "10.0.0.2"packet mode egr-ingr-and-droppedexitexit7604 2013/05/24 16:55:49.46 EST MINOR: DEBUG #2001 vprn1 IGMP[8]"IGMP[8]: RX-PKT[013 07:53:02.120] IGMP host 10.0.0.2 V3 PDU: 10.0.0.2 -> 224.0.0.22pduLen 20Type: V3 REPORT maxrespCode 0x0 checkSum 0xddf6Num Group Records: 1Group Record 0Type: ALW_NEW_SRCS, AuxDataLen 0, Num Sources 1Mcast Addr: 239.255.1.1Source Address List192.168.4.2"7605 2013/05/24 16:55:49.46 EST MINOR: DEBUG #2001 vprn1 IGMP[vprn1 inst 8]"IGMP[vprn1 inst 8]: igmpIfGroupAddAdding 239.255.1.1 to IGMP host 10.0.0.2 database"7606 2013/05/24 16:55:49.46 EST MINOR: DEBUG #2001 vprn1 IGMP[vprn1 inst 8]"IGMP[vprn1 inst 8]: igmpProcessGroupRecProcess group rec ALW_NEW_SRCS received on host 10.0.0.2 for group 239.255.1.1 in modeINCLUDE. Num srcs 1"7607 2013/05/24 16:55:49.46 EST MINOR: DEBUG #2001 vprn1 IGMP[vprn1 inst 8]"IGMP[vprn1 inst 8]: igmpIfSrcAddAdding i/f source entry for host 10.0.0.2 (192.168.4.2,239.255.1.1) to IGMP fwdList Database, redir if N/A"The IGMP leave messages can also be seen in the debug, as shown below.7615 2013/05/24 16:58:06.38 EST MINOR: DEBUG #2001 vprn1 IGMP[8]"IGMP[8]: RX-PKT[013 07:55:19.040] IGMP host 10.0.0.2 V3 PDU: 10.0.0.2 -> 224.0.0.22pduLen 20Page 21387750 SR Advanced Configuration GuideESM IPv4: Multicast in a Wholesale/Retail Scenario Type: V3 REPORT maxrespCode 0x0 checkSum 0xdcf6Num Group Records: 1Group Record 0Type: BLK_OLD_SRCS, AuxDataLen 0, Num Sources 1Mcast Addr: 239.255.1.1Source Address List192.168.4.2"7616 2013/05/24 16:58:06.38 EST MINOR: DEBUG #2001 vprn1 IGMP[vprn1 inst 8]"IGMP[vprn1 inst 8]: igmpProcessGroupRecProcess group rec BLK_OLD_SRCS received on host 10.0.0.2 for group 239.255.1.1 in modeINCLUDE. Num srcs 1"7617 2013/05/24 16:58:06.38 EST MINOR: DEBUG #2001 vprn1 IGMP[vprn1 inst 8]"IGMP[vprn1 inst 8]: igmpProcessIfSrcTimerExpSource Timer expired for IGMP host 10.0.0.2 (192.168.4.2,239.255.1.1)"7618 2013/05/24 16:58:06.38 EST MINOR: DEBUG #2001 vprn1 IGMP[vprn1 inst 8]"IGMP[vprn1 inst 8]: igmpIfSrcDelDeleting i/f source entry for host 10.0.0.2 (192.168.4.2,239.255.1.1) from IGMPDatabase. DeleteFromAvl: 1 !Redir 0"7619 2013/05/24 16:58:06.38 EST MINOR: DEBUG #2001 vprn1 IGMP[vprn1 inst 8]"IGMP[vprn1 inst 8]: igmpIfGroupDelDeleting 239.255.1.1 from IGMP host 10.0.0.2 database"7750 SR Advanced Configuration Guide Page 2139ConclusionConclusionMulticast is an essential part of Triple Play Services. The SR/ESS TPSDA solution offering ismuch more than a baseline multicast delivery, it includes individual subscriber awareness andprovides each retailer a separate routing context to manage their own multicast content. Subscriberawareness allows for the fine tuning of each subscriber multicast experience and also fortroubleshooting on a per subscriber basis. This example provides a complete configuration walkthrough for multicast delivery for both IPoE and PPPoE in a wholesale/retail model.Page 21407750 SR Advanced Configuration Guide。

阿尔卡特7750培训资料1:路由配置

阿尔卡特7750培训资料1:路由配置
解决这种情形的方法被称为Proxy ARP(代理ARP) 。这个技术允许配置在本 地网之间的路由器代替D来响应设备A的广播。这个路由器不会将设备D的硬 件地址发送回给设备A。因为他们不在同一网络中,A不能直接发送给D。路 由器发送给A收到ARP请求的接口的硬件地址。A然后发送数据到路由器,路 由器发送这个数据到其他网络的D。这个路由器也代替A为D做相同的事情, 并且当广播包的目的地和ARP发起者不在同一物理网络上时,路由器为任何 在两个网络上的其他设备都采取相同的方法。
− L1, L 1-2,和L2 − 从其他协议分发进来的IPv4 的路由汇总 − 汇总路由所通告的量度比其他具体的IPv4 路由的量度要小。。
• 可基于每个消息类型和每个level,支持抑制IS-IS认证。提高与非 7750 IS-IS 部署的互操作性。
• 不间断路由
7750SR 路由和路由策略
Alcatel Proprietary, all rights reserved © 2005, Alcatel
• 出站路由过滤 (ORF) –BGP的一个特征:一个BGP 发送者请求他的
邻居不发送给它特定的路由。在 7750VPRN上支持。 • TTL 安全– 能够指定一个进入的BGP 信息包的最小TTL 值 。
− 多数eBGP对等体关系在邻近的路由器间建立。 − 假如一个信息包的TTL值不在指定的范围内,便丢弃这个信息包并产生一
7750 SR 业务实现R3.0
Alcatel University
代理-ARP
子网 20
主机 A IP add.=IP_A MAC add.= MAC_A
子网 10
主机C IP add.=IP_C MAC add.= MAC_C
接口 X

阿尔卡特7750配置文档

阿尔卡特7750配置文档

上海贝尔阿尔卡特7750SR配置标准模板目录一、硬件配置 (5)1.1配置IOM卡 (5)1.1.1 查看已经插入的IOM卡的类型 (5)1.1.2 正确配置IOM卡的类型 (5)1.2配置MDA卡 (5)1.2.1 查看已经插入的MDA卡的类型 (5)1.2.2 正确配置MDA卡的类型 (5)1.3配置MDA端口 (6)1.3.1 POS端口配置 (6)1.3.2 以太口配置 (6)1.3.3 查看port信息 (6)二、设备管理配置 (8)2.1配置路由器名称、LOCA TION、CONTACT (8)2.2配置系统时间 (8)2.3配置SNTP (8)2.3.1 打开SNTP (8)2.3.2 配置SNTP地址 (8)2.4配置SR为TELNET服务器 (8)2.5.1 配置默认动作为允许,因为是所有上主控板的流量。

(9)2.5.2 配置允许IP段的ACL,配置源IP,协议,目的端口 (9)2.5.3 配置一条拒绝的ACL,拒绝其他IP段。

(9)2.6配置用户 (9)2.6.1 配置用户名 (9)2.6.2 配置用户密码 (9)2.6.3 配置用户登陆方式 (10)2.6.4 配置用户所属的组 (10)2.7配置LOG (10)2.7.1 配置log-id (10)2.7.2 配置log信息类型 (10)2.7.3 配置记录log的方式 (10)2.7.4 配置记录log方式的具体配置 (10)2.8配置SNMP (11)2.9配置主备板同步 (11)2.9.1 配置自动同步 (11)2.9.2 手工同步命令 (11)2.10配置空闲时间 (11)2.11配置ANTI-SPOOF (11)三、路由配置 (13)3.1配置路由器系统地址 (13)3.2配置网络接口 (13)3.2.1 配置interface名字及描述 (13)3.2.2 配置IP地址 (13)3.2.3 配置关联端口 (13)3.2.4 查看配置的路由器接口 (13)3.3配置静态及OSPF路由协议 (14)3.3.1 配置静态路由 (14)3.3.2 配置OSPF区域 (14)3.3.3 配置ospf接口cost值 (14)3.3.4 配置一个stub区域 (14)3.3.5 配置NSSA区域 (14)3.3.6 配置虚链路 (15)3.3.7 配置认证 (15)3.3.8 配置路由聚合 (15)3.3.9 配置静态路由注入到OSPF路由协议 (15)3.3.10 查看运行在ospf协议下的接口 (16)3.3.11 查看ospf邻居建立关系 (16)3.3.12 查看ospf路由表 (16)3.4配置IS-IS (16)3.4.1 配置区域ID (16)3.4.2 配置路由器等级能力 (17)3.4.4 查看ISIS下的接口 (17)3.4.5 添加已经配置到ISIS的每个网络接口 (17)3.4.6 查看ISIS邻接关系 (17)3.4.7 查看ISIS路由表 (17)3.5BGP配置 (18)3.5.1 创建AS (18)3.5.2 配置路由器 ID5 (18)3.5.3 配置 BGP (18)3.6配置POLICY (18)3.6.1 配置policy名称 (18)3.6.2 配置从静态路由分布到ospf路由协议中的policy (19)3.6.3 配置commit使之生效 (19)3.6.4 应用policy (19)3.7IP F ILTER配置 (19)3.7.1 创建ip filter (19)3.7.2 指定默认动作 (19)3. 7.3创建条目,指定动作、源、目的IP (19)3.7.4 应用ip filter (20)四、 MPLS 配置以及业务配置 (21)4.1MPLS配置 (21)4.1.1 MPLS接口配置 (21)4.1.2 创建已命名的MPLS路径 (21)4.1.3 配置 MPLS LSP和主路径 (21)4.1.4 查看命令 (22)4.1.5 改变每个网络接口的最大传输单元(MTU)尺寸 (22)4.2 E P IPE 配置 (22)4.2.1 创建客户并将其与提供的业务相关联 (22)4.2.2 指向客户的接口(在我们的网络中由膝上电脑表示)称为“toCustomer”,必须配置为接入接口。

7750SR配置方法

7750SR配置方法
实用文案
7750SR 路由器配置规范
V2.1
标准文档
7750SR 路由器配置规范
上海贝尔阿尔卡特股份有限公司 互联网事业部
二零零六年十一月
第 2 页 共 68 页
7750SR 路由器配置规范
目录
1. 概述 ............................................................................................................................. 5 2. 系统基本配置 ............................................................................................................ 7
第 3 页 共 68 页
7750SR 路由器配置规范
5.3. FTP 配置 .................................................................................................3..3..... 5.4. SNMP .....................................................................................................3..3..... 5.5. SYSLOG .................................................................................................3..5..... 5.6. 配置备份 ................................................................................................3..6..... 5.7. SSH 配置 ................................................................................................3..6..... 5.8. NetFlow 备份 ........................................................................................3..7.... 6. 路由配置 ..........................................................................................................3..9...... 6.1. 黑洞路由配置 .........................................................................................3..9.... 6.2. 静态路由配置 .........................................................................................3..9.... 6.3. OSPF 配置 ..............................................................................................3..9.... 6.4. ISIS 配置 ................................................................................................4..4..... 6.5. BGP 配置 ...............................................................................................4..7..... 7. 业务配置 ..........................................................................................................5..4...... 7.1. 专线业务配置( IES 配置) ...................................................................5..4.. 7.2. MPLS VPN 业务配置 ............................................................................5..6...

7750SR配置方法

7750SR配置方法

实用文案7750SR路由器配置规范V2.1上海贝尔阿尔卡特股份有限公司互联网事业部二零零六年十一月目录1.概述 (5)2.系统基本配置 (7)2.1.层次化命令结构 (7)2.2.在CLI中获得帮助 (8)2.3.硬件板卡配置 (9)2.4.设备名称配置 (11)2.5.系统时间配置 (11)2.6.NTP配置 (11)2.7.主备卡切换配置 (12)2.8.AAA配置(登录用户) (14)3.端口配置 (16)3.1.Loopback端口配置 (16)3.2.GE端口配置 (16)3.3.POS端口配置 (17)3.4.端口镜像配置 (18)4.安全配置 (23)4.1.ACL配置 (23)4.2.防攻击配置 (24)5.网管配置 (31)5.1.网管地址配置 (31)5.2.TELNET配置 (32)5.3.FTP配置 (33)5.4.SNMP (33)5.5.SYSLOG (35)5.6.配置备份 (36)5.7.SSH配置 (36)Flow备份 (37)6.路由配置 (39)6.1.黑洞路由配置 (39)6.2.静态路由配置 (39)6.3.OSPF配置 (39)6.4.ISIS配置 (44)6.5.BGP配置 (47)7.业务配置 (54)7.1.专线业务配置(IES配置) (54)7.2.MPLS VPN业务配置 (56)7.2.1P路由器配置 (56)7.2.2PE路由器配置(VPRN) (60)7.2.3PE路由器配置(VPLS) (63)8.7750SR常用维护命令 (67)1.概述阿尔卡特7750SR路由器是业内第一个专为高级互联网和虚拟专用网络(VPN)业务而设计和优化的IP/MPLS业务路由器。

阿尔卡特7750SR有三种尺寸可供选择:单槽、7槽和12槽,可提供具有卓越性能和高密度的各种接口。

作为目前业内最具扩展性的路由器平台,阿尔卡特7750SR具有为高效传送基于服务等级协议(SLA)的业务而设计的软件和硬件架构,因此阿尔卡特7750SR不仅仅是强大的互联网路由器,更是一个灵活、强大的业务供应平台。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
ingress
exit
exit
exit
#--------------------------------------------------
echo "Port Configuration"
#--------------------------------------------------
ethernet
exit
no shutdown
exit
port 2/1/20
ethernet
exit
no shutdown
exit
port 2/2/1
ethernet
access console ftp
console
member "administrative"
exit
exit
user "yzg"
ethernet
exit
no shutdown
exit
port 2/1/6
ethernet
exit
no shutdown
exit
port 2/1/7
ethernet
ethernet
exit
no shutdown
exit
port 2/1/14
ethernet
exit
no shutdown
exit
port 2/1/15
exit
no shutdown
exit
port 2/1/8
description "to-QC-ZX-8908-4/2"
ethernet
mode access
encap-type dot1q
qos
exit
#--------------------------------------------------
echo "Card Configuration"
#--------------------------------------------------
card 2
log
exit
#--------------------------------------------------
echo "System Security Cpm Hw Filters Configuration"
#--------------------------------------------------
system
security
exit
exit
#--------------------------------------------------
echo "QoS Policy Configuration"
#--------------------------------------------------
ethernet
exit
no shutdown
exit
port 2/1/18
ethernet
exit
no shutdown
exit
port 2/1/19
ethernet
exit
no shutdown
exit
port 2/1/12
ethernet
exit
no shutdown
exit
port 2/1/13
port 2/1/1
description "to-HG-YZDL-7609-G9/3"
ethernet
no autonegotiate
exit
no shutdown
exit
port 2/1/2
ethernet
exit
no shutdown
exit
port 2/1/16
ethernet
exit
no shutdown
exit
port 2/1/17
system
security
telnet-server
ftp-server
user "admin"
password ".wwBSCf55BeJQsICA8BrJ." hash2
no autonegotiate
exit
no shutdown
exit
port 2/1/9
description "to-HG-QC-BRAR-7750-00"
ethernet
mtu 9192
echo "System Configuration"
#--------------------------------------------------
system
name "HG-QC-BRBAS-7750-01"
snmp
exit
description "to-HG-QC-ZX-8908-00"
ethernet
mode access
no autonegotiate
exit no shutdown Nhomakorabea exit
exit
mda 1
mda-type m20-1gb-xp-sfp
ingress
exit
exit
mda 2
mda-type m60-10/100eth-tx
exit
exit
#--------------------------------------------------
echo "System Security Configuration"
#--------------------------------------------------
card-type iom3-xp
fp 1
ingress
mcast-path-management
shutdown
exit
exit
exit
exit
per-peer-queuing
cpu-protection
policy 1 create
exit
exit
# Built on Tue Jan 20 13:16:25 PST 2009 by builder in /rel6.1/b1/R6/panos/main
# Generated MON NOV 02 06:46:26 2009 UTC
exit all
configure
#--------------------------------------------------
no autonegotiate
exit
no shutdown
exit
port 2/1/10
ethernet
exit
no shutdown
exit
port 2/1/11
exit
exit
#--------------------------------------------------
echo "Log Configuration"
#--------------------------------------------------
password "t7B6fupm/PH5RN2ll/B.hE" hash2
access console
console
member "default"
member "administrative"
# TiMOS-C-6.1.R6 cpm/hops ALCATEL SR 7750 Copyright (c) 2000-2009 Alcatel-Lucent.
# All rights reserved. All use subject to applicable license agreements.
no shutdown
exit
port 2/2/3
shutdown
ethernet
exit
exit
port 2/1/3
ethernet
exit
no shutdown
exit
port 2/1/4
ethernet
exit
no shutdown
exit
port 2/1/5
mode access
mtu 1500
exit
no shutdown
exit
port 2/2/2
ethernet
mode access
exit
login-control
telnet
inbound-max-sessions 7
outbound-max-sessions 7
exit
exit
time
sntp
shutdown
exit
zone UTC
exit
thresholds
rmon
exit
相关文档
最新文档