SR配置规范

合集下载

JuniperSR防火墙简明配置手册

Juniper SRX防火墙简明配置手册卞同超Juniper 服务工程师Juniper Networks, Inc.北京市东城区东长安街1号东方经贸城西三办公室15层1508室邮编:100738电话:目录Juniper SRX防火墙简明配置手册SRX系列防火墙是Juniper公司基于JUNOS操作系统的安全系列产品,JUNOS集成了路由、交换、安全性和一系列丰富的网络服务;目前Juniper公司的全系列路由器产品、交换机产品和SRX安全产品均采用统一源代码的JUNOS操作系统,JUNOS是全球首款将转发与控制功能相隔离,并采用模块化软件架构的网络操作系统;JUNOS作为电信级产品的精髓是Juniper真正成功的基石,它让企业级产品同样具有电信级的不间断运营特性,更好的安全性和管理特性,JUNOS软件创新的分布式架构为高性能、高可用、高可扩展的网络奠定了基础;基于NP架构的SRX系列产品产品同时提供性能优异的防火墙、NAT、IPSEC、IPS、SSL VPN和UTM等全系列安全功能,其安全功能主要来源于已被广泛证明的ScreenOS操作系统;本文旨在为熟悉Netscreen防火墙ScreenOS操作系统的工程师提供SRX防火墙参考配置,以便于大家能够快速部署和维护SRX防火墙,文档介绍JUNOS操作系统,并参考ScreenOS配置介绍SRX防火墙配置方法,最后对SRX防火墙常规操作与维护做简要说明;一、JUNOS操作系统介绍层次化配置结构JUNOS采用基于FreeBSD内核的软件模块化操作系统,支持CLI命令行和WEBUI两种接口配置方式,本文主要对CLI命令行方式进行配置说明;JUNOS CLI使用层次化配置结构,分为操作operational和配置configure两类模式,在操作模式下可对当前配置、设备运行状态、路由及会话表等状态进行查看及设备运维操作,并通过执行config或edit命令进入配置模式,在配置模式下可对各相关模块进行配置并能够执行操作模式下的所有命令run;在配置模式下JUNOS采用分层分级模块下配置结构,如下图所示,edit命令进入下一级配置类似unix cd命令,exit命令退回上一级,top命令回到根级;JunOS配置管理JUNOS通过set语句进行配置,配置输入后并不会立即生效,而是作为候选配置Candidate Config等待管理员提交确认,管理员通过输入commit命令来提交配置,配置内容在通过SRX语法检查后才会生效,一旦commit通过后当前配置即成为有效配置Active config;另外,JUNOS允许执行commit命令时要求管理员对提交的配置进行两次确认,如执行commit confirmed 2命令要求管理员必须在输入此命令后2分钟内再次输入commit以确认提交,否则2分钟后配置将自动回退,这样可以避免远程配置变更时管理员失去对SRX的远程连接风险;在执行commit命令前可通过配置模式下show命令查看当前候选配置Candidate Config,在执行commit后配置模式下可通过run show config命令查看当前有效配置Active config;此外可通过执行show | compare比对候选配置和有效配置的差异;SRX上由于配备大容量硬盘存储器,缺省按先后commit顺序自动保存50份有效配置,并可通过执行rolback和commit命令返回到以前配置如rollback 0/commit可返回到前一commit配置；也可以直接通过执行save 手动保存当前配置,并执行load override / commit调用前期手动保存的配置;执行load factory-default / commit命令可恢复到出厂缺省配置;SRX可对模块化配置进行功能关闭与激活,如执行deactivate security nat/comit命令可使NAT 相关配置不生效,并可通过执行activate security nat/commit使NAT配置再次生效;SRX通过set语句来配置防火墙,通过delete语句来删除配置,如delete security nat和edit security nat / delete一样,均可删除security防火墙层级下所有NAT相关配置,删除配置和ScreenOS不同,配置过程中需加以留意;SRX主要配置内容部署SRX防火墙主要有以下几个方面需要进行配置：System：主要是系统级内容配置,如主机名、管理员账号口令及权限、时钟时区、Syslog、SNMP、系统级开放的远程管理服务如telnet等内容;Interface:接口相关配置内容;Security:是SRX防火墙的主要配置内容,安全相关部分内容全部在Security层级下完成配置,如NAT、Zone、Policy、Address-book、Ipsec、Screen、Idp等,可简单理解为ScreenOS防火墙安全相关内容都迁移至此配置层次下,除了Application自定义服务;Application：自定义服务单独在此进行配置,配置内容与ScreenOS基本一致;routing-options：配置静态路由或router-id等系统全局路由属性配置;二、SRX防火墙配置对照说明初始安装2.1.1 登陆Console口通用超级终端缺省配置连接SRX,root用户登陆,密码为空login: rootPassword:--- JUNOS built 2009-07-16 15:04:30 UTCroot% cli /进入操作模式/root>root> configureEntering configuration mode /进入配置模式/editRoot2.1.2 设置root用户口令设置root用户口令root set system root-authentication plain-text-passwordroot new password : root123root retype new password: root123密码将以密文方式显示root show system root-authenticationencrypted-password "$1$xavDeUe6$"; SECRET-DATA注意：强烈建议不要使用其它加密选项来加密root和其它user口令如encrypted-password加密方式,此配置参数要求输入的口令应是经加密算法加密后的字符串,采用这种加密方式手工输入时存在密码无法通过验证风险;注：root用户仅用于console连接本地管理SRX,不能通过远程登陆管理SRX,必须成功设置root 口令后,才能执行commit提交后续配置命令;2.1.3 设置远程登陆管理用户root set system login user lab class super-user authentication plain-text-password root new password : lab123root retype new password: lab123注：此lab用户拥有超级管理员权限,可用于console和远程管理访问,另也可自行灵活定义其它不同管理权限用户;2.1.4 远程管理SRX相关配置run set date /设置系统时钟/set system time-zone Asia/Shanghai/设置时区为上海/set system host-name SRX3400-A/设置主机名/set system name-server 1.1.1.1 /设置DNS服务器/set system services ftpset system services telnetset system services web-management http/在系统级开启ftp/telnet/http远程接入管理服务/set interfaces ge-0/0/ family inet address 10.1.1.1/24或set interfaces ge-0/0/0 unit 0 family inet address 10.1.1.1/24set interfaces ge-0/0/1 unit 0 family inet address 10.1.2.1/24set routing-options static route 0.0.0.0/0 p 10.1.1/配置逻辑接口地址及缺省路由,SRX接口要求IP地址必须配置在逻辑接口下类似ScreenOS的子接口,通常使用逻辑接口0即可/set security zones security-zone untrust interfaces ge-0/0//将ge-0/0/接口放到untrust zone去,类似ScreenOS/set security zones security-zone untrust host-inbound-traffic system-services ping set security zones security-zone untrust host-inbound-traffic system-services http set security zones security-zone untrust host-inbound-traffic system-services telnet /在untrust zone打开允许远程登陆管理服务,ScreenOS要求基于接口开放服务,SRX要求基于Zone开放,从SRX主动访问出去流量开启服务,类似ScreenOS/PolicyPolicy配置方法与ScreenOS基本一致,仅在配置命令上有所区别,其中策略的允许/拒绝的动作Action需要额外配置一条then语句将ScreenOS的一条策略分解成两条及以上配置语句;Policy 需要手动配置policy name,policy name可以是字符串,也可以是数字与ScreenOS的policy ID 类似,只不过需要手工指定;set security zones security-zone trust address-book address pc1 10.1.1.10/32set security zones security-zone untrust address-book address server1 10.0.2.1/32 /与ScreenOS一样,在trust和untrust zone下分别定义地址对象便于策略调用,地址对象的名称可以是地址/掩码形式/set security zones security-zone trust address-book address-set addr-group1 address pc1/在trust zone下定义名称为add-group1的地址组,并将pc1地址放到该地址组中/set security policies from-zone trust to-zone untrust policy 001 match source-address addr-group1 destination-address server1 application anyset security policies from-zone trust to-zone untrust policy 001 then permit/定义从trust 到untrust方向permit策略,允许addr-group1组的源地址访问server1地址any服务/NATSRX NAT较ScreenOS在功能实现方面基本保持一致,但在功能配置上有较大区别,配置的主要差异在于ScreenOS的NAT与policy是绑定的,无论是MIP/VIP/DIP还是基于策略的NAT,在policy 中均要体现出NAT内容除了缺省基于untrust接口的Souec-NAT模式外,而SRX 的NAT则作为网络层面基础内容进行独立配置独立定义地址映射的方向、映射关系及地址范围,Policy中不再包含NAT相关配置信息,这样的好处是易于理解、简化运维,当网络拓朴和NAT映射关系发生改变时,无需调整Policy配置内容;SRX NAT和Policy执行先后顺序为：目的地址转换－目的地址路由查找－执行策略检查－源地址转换,结合这个执行顺序,在配置Policy时需注意：Policy中源地址应是转换前的源地址,而目的地址应该是转换后的目的地址,换句话说,Policy中的源和目的地址应该是源和目的两端的真实IP地址,这一点和ScreenOS存在区别,需要加以注意;SRX中不再使用MIP/VIP/DIP这些概念,其中MIP被Static静态地址转换取代,两者在功能上完全一致；DIP被Source NAT取代；基于Policy的目的地址转换及VIP被 Destination NAT取代;ScreenOS中基于Untrust zone接口的源地址转换被保留下来,但在SRX中不再是缺省模式SRX中Trust Zone接口没有NAT模式概念,需要手工配置;类似ScreenOS,Static属于双向NAT,其他类型均属于单向NAT,此外,SRX还多了一个proxy-arp概念,如果定义的IP Pool可用于源或目的地址转换与接口IP 在同一子网时,需配置SRX对这个Pool内的地址提供ARP代理功能,这样对端设备能够解析到IP Pool地址的MAC地址使用接口MAC地址响应对方,以便于返回报文能够送达SRX;下面是配置举例及相关说明：2.3.1 Interface based NATNAT：set security nat source rule-set 1 from zone trustset security nat source rule-set 1 to zone untrustset security nat source rule-set 1 rule rule1 match source-address 0.0.0.0/0 destination-address security nat source rule-set 1 rule rule1 then source-nat interface上述配置定义NAT源地址映射规则,从Trust Zone访问Untrust Zone的所有流量用Untrust Zone 接口IP做源地址转换;Policy:set security policies from-zone trust to-zone untrust policy 1 match source-address 10.1.2.2set security policies from-zone trust to-zone untrust policy 1 match destination-address anyset security policies from-zone trust to-zone untrust policy 1 match application anyset security policies from-zone trust to-zone untrust policy 1 then permit上述配置定义Policy策略,允许Trust zone 10.1.2.2地址访问Untrust方向任何地址,根据前面的NAT配置,SRX在建立session时自动执行接口源地址转换;2.3.2 Pool based Source NATNAT：set security nat source pool pool-1 address to security nat source rule-set 1 from zone trustset security nat source rule-set 1 to zone untrustset security nat source rule-set 1 rule rule1 match source-address 0.0.0.0/0 destination-address security nat source rule-set 1 rule rule1 then source-nat pool pool-1set security nat proxy-arp interface ge-0/0/2 address to 上述配置表示从trust方向any到untrust方向any访问时提供源地址转换,源地址池为pool1 ,同时ge-0/0/2接口为此pool IP提供ARP代理;需要注意的是：定义Pool时不需要与Zone及接口进行关联;配置proxy-arp目的是让返回包能够送达SRX,如果Pool与出接口IP不在同一子网,则对端设备需要配置指向的Pool地址路由;Policy：set security policies from-zone trust to-zone untrust policy 1 match source-address 10.1.1.2set security policies from-zone trust to-zone untrust policy 1 match destination-address anyset security policies from-zone trust to-zone untrust policy 1 match application any set security policies from-zone trust to-zone untrust policy 1 then permit上述配置定义Policy策略,允许Trust zone 10.1.2.2地址访问Untrust方向任何地址,根据前面的NAT配置,SRX在建立session时自动执行源地址转换;2.3.3 Pool base destination NATNAT：set security nat destination pool 111 address security nat destination rule-set 1 from zone untrustset security nat destination rule-set 1 rule 111 match source-address 0.0.0.0/0set security nat destination rule-set 1 rule 111 match destination-address security nat destination rule-set 1 rule 111 then destination-nat pool 111上述配置将外网any访问地址映射到内网地址,注意：定义的Dst Pool是内网真实IP地址,而不是映射前的公网地址;这点和Src-NAT Pool有所区别;Policy：set security policies from-zone trust to-zone untrust policy 1 match source-address anyset security policies from-zone trust to-zone untrust policy 1 match destination-address security policies from-zone trust to-zone untrust policy 1 match application anyset security policies from-zone trust to-zone untrust policy 1 then permit上述配置定义Policy策略,允许Untrust方向任何地址访问Trust方向,根据前面的NAT配置,公网访问时,SRX自动执行到的目的地址转换;ScreenOS VIP功能对应的SRX Dst-nat配置：set security nat destination pool 222 address port 8000set security nat destination rule-set 1 from zone untrustset security nat destination rule-set 1 rule 111 match source-address 0.0.0.0/0set security nat destination rule-set 1 rule 111 match destination-address security nat destination rule-set 1 rule 111 match destination-port 8000set security nat destination rule-set 1 rule 111 then destination-nat pool 222上述NAT配置定义：访问地址8000端口映射至地址8000端口,功能与ScreenOS VIP端口映射一致;2.3.4 Pool base Static NATNAT：set security nat static rule-set static-nat from zone untrustset security nat static rule-set static-nat rule rule1 match destination-address security nat static rule-set static-nat rule rule1 then static-nat prefix security policies from-zone trust to-zone untrust policy 1 match source-address anyset security policies from-zone trust to-zone untrust policy 1 match destination-address security policies from-zone trust to-zone untrust policy 1 match application anyset security policies from-zone trust to-zone untrust policy 1 then permitStatic NAT概念与ScreenOS MIP一致,属于静态双向一对一NAT,上述配置表示访问时转换为,当访问Internet时自动转换为;IPSEC VPNSRX IPSEC VPN支持Site-to-Site VPN 和基于NS-remote的拨号VPN,和ScreenOS一样,site-to-site VPN也支持路由模式和Policy模式,在配置方面也和ScreenOS基本一致;SRX 中的加密/验证算法在命名上和ScreenOS存在一些区别,配置过程中建议选择ike和ipsec的proposal为 standard模式,standard中包含SRX支持的全部加密/验证算法,只要对端设备支持其中任何一种即可;SRX中通道接口使用st0接口,对应ScreenOS中的tunnel虚拟接口;下面是图中左侧SRX基于路由方式Site-to-site VPN配置：set interfaces st0 unit 0 family inet address 10.2.0.1/24set security zones security-zone untrust interfacesset routing-options static route 10.1.2.0/24 next-hop定义st0 tunnel接口地址/Zone及通过VPN通道到对端网络路由set security ike policy ABC mode mainset security ike policy ABC proposal-set standardset security ike policy ABC pre-shared-key ascii-text juniper定义IKE Phase1 policy参数,main mode,standard proposal及预共享密钥方式set security ike gateway gw1 ike-policy ABCset security ike gateway gw1 address 10.0.2.1set security ike gateway gw1 external-interface ge-0/0/定义IKE gaeway参数,预共享密钥认证,对端网关10.0.2.1,出接口ge-0/0/1位于untrust zoneset security ipsec policy AAA proposal-set standardset security ipsec vpn vpn1 bind-interfaceset security ipsec vpn vpn1 ike gateway gw1set security ipsec vpn vpn1 ike ipsec-policy AAAset security ipsec vpn vpn1 establish-tunnels immediately定义ipsec Phase 2 VPN参数：standard proposal、与接口绑定,调用Phase 1 gw1 ike网关; set security policies from-zone untrust to-zone trust policy vpn-policy match source-address anyset security policies from-zone untrust to-zone trust policy vpn-policy match destination-address anyset security policies from-zone untrust to-zone trust policy vpn-policy match application anyset security policies from-zone untrust to-zone trust policy vpn-policy then permitset security policies from-zone trust to-zone untrust policy vpn-policy match source-address anyset security policies from-zone trust to-zone untrust policy vpn-policy match destination-address anyset security policies from-zone trust to-zone untrust policy vpn-policy match application anyset security policies from-zone trust to-zone untrust policy vpn-policy then permit 开启双向policy以允许VPN流量通过Application and ALGSRX中自定义服务及ALG使用方法与ScreenOS保持一致,系统缺省开启FTP ALG,为TCP 21服务提供FTP应用ALG;自定义服务如果属于FTP类应用,需要将此自定义服务非TCP 21端口与FTP 应用进行关联;下面举例定义一个FTP类服务ftp-test,使用目的端口为TCP 2100,服务超时时间为3600秒,并将此自定义服务与FTP应用关联ALG,系统将识别此服务为FTP应用并开启FTPALG来处理该应用流量;set applications application ftp-test protocol tcp destination-port 2100 inactivity-timeout 3600set applications application ftp-test application-protocol ftpJSRPJSRP是Juniper SRX的私有HA协议,对应ScreenOS的NSRP双机集群协议,支持A/P和A/A模式,JSRP对ScreenOS NSRP协议和JUNOS Cluster集群技术进行了整合集成,熟悉NSRP协议有助于对JSRP协议的理解;JSRP和NSRP最大的区别在于JSRP是完全意义上的Cluster概念,两台设备完全当作一台设备来看待,两台设备的接口板卡顺序编号、运维变更将对两台设备同时进行操作,无需额外执行ScreenOS的配置和会话同步等操作,而ScreenOS NSRP可看作在同步配置和动态对象session基础上独立运行的两台单独设备;JSRP要求两台设备在软件版本、硬件型号、板卡数量、插槽位置及端口使用方面严格一一对应;由于SRX 是转发与控制层面完全分裂架构,JSRP需要控制层面配置同步和数据层面Session同步两个平面的互联,建议控制和数据层面互联链路使用光纤链路直连部分平台强制要求光纤链路直连;JSRP接口命名方式采用多个机箱抽象成一个逻辑机箱之后再统一为各个槽位进行编号,如上所示的SRX5800,每个SRX5800机箱有12个业务槽位,节点0槽位号从0开始编号,节点1槽位号从12开始往后编;整个JSRP配置过程包括如下7个步骤配置Cluster id和Node id 对应ScreenOS NSRP 的cluster id并需手工指定设备使用节点id指定Control Port 指定控制层面使用接口,用于配置同步及心跳指定Fabric Link Port 指定数据层面使用接口,主要session等RTO同步配置Redundancy Group 类似NSRP的VSD group,优先级与抢占等配置每个机箱的个性化配置单机无需同步的个性化配置,如主机名、带外管理口IP地址等配置Redundant Ethernet Interface 类似NSRP的Redundant冗余接口配置Interface Monitoring 类似NSRP interface monitor,是RG数据层面切换依据SRX JSRP配置样例：配置Cluster id和Node idSRX-A>set chassis cluster cluster-id 1 node 0 reboot注意该命令需在operational模式下输入,Cluster ID取值范围为1 – 15,当Cluster ID = 0时将unsets the clusterSRX-B>set chassis cluster cluster-id 1 node 1 reboot指定Control Port如果主控板RE上有固定control-ports,则无需指定：set chassis cluster control-ports fpc 11 port 0set chassis cluster control-ports fpc 23 port 0指定Fabric Link Portset interfaces fab0 fabric-options member-interfaces ge-1/0/0set interfaces fab1 fabric-options member-interfaces ge-13/0/0注：Fabric Link中的Fab0固定用于node 0,Fab1固定用于node 1配置Redundancy GroupRG0固定用于主控板RE切换,RG1以后用于redundant interface切换,RE切换独立于接口切换set chassis cluster reth-count 10 指定整个Cluster中redundant ethernet interface 最多数量set chassis cluster redundancy-group 0 node 0 priority 200高值优先,与NSRP相反set chassis cluster redundancy-group 0 node 1 priority 100set chassis cluster redundancy-group 1 node 0 priority 200高值优先,与NSRP相反set chassis cluster redundancy-group 1 node 1 priority 100每个机箱的个性化配置,便于对两台设备的区分与管理set groups node0 system host-name SRX-Aset groups node0 interfaces fxp0 unit 0 family inet address 1.1.1.1/24 带外网管口名称为fxp0,区别ScreenOS的MGT口set groups node1 system host-name SRX-Bset groups node1 interfaces fxp0 unit 0 family inet address 1.1.1.2/24set apply-groups ${node} 应用上述groups配置配置Redundant Ethernet InterfaceRedundant Ethernet Interface类似ScreenOS里的redundant interface,只不过Redundant Ethernet interface是分布在不同的机箱上这一特性又类似ScreenOS 的VSI接口;Set interface ge-0/0/0 gigether-options redundant-parent reth0 node 0的ge-0/0/0接口Set interface ge-13/0/0 gigether-options redundant-parent reth0 node 1的ge-0/0/0接口Set interface reth0 redundant-ether-options redundancy-group 1 reth0属于RG1 Set interface reth0 unit 0 family inet address 配置Interface Monitoring,被监控的接口Down掉后,RG1将自动进行主备切换与ScreenOS类似,Set cluster redundancy-group 1 interface-monitor ge-0/0/0 weight 255Set cluster redundancy-group 1 interface-monitor ge-0/0/1 weight 255Set cluster redundancy-group 1 interface-monitor ge-13/0/0 weight 255Set cluster redundancy-group 1 interface-monitor ge-13/0/1 weight 255 JSRP维护命令a)手工切换JSRP Master,RG1 原backup将成为Masterrootsrx5800a> request chassis cluster failover redundancy-group 1 node 1b)手工恢复JSRP状态,按照优先级重新确定主备关系高值优先rootsrx5800b> request chassis cluster failover reset redundancy-group 1c)查看cluster interfacerootrouter> show chassis cluster interfacesd)查看cluster 状态、节点状态、主备关系labsrx5800a run show chassis cluster statuse)取消cluster配置srx5800aset chassis cluster disable rebootf)升级JSRP软件版本SRX目前暂不支持软件在线升级ISSU,升级过程会中断业务;升级步骤如下：1.升级node 0,注意不要重启系统2.升级node 1,注意不要重启系统.3.同时重启两个系统g)恢复处于disabled状态的node当control port或fabric link出现故障时,为避免出现双master split-brain现象,JSRP 会把出现故障前状态为secdonary的node设为disabled状态,即除了RE,其余部件都不工作;想要恢复必须reboot该node;三、SRX防火墙常规操作与维护设备关机SRX因为主控板上有大容量硬盘,为防止强行断电关机造成硬件故障,要求设备关机必须按照下面的步骤进行操作：1.管理终端连接SRX console口;2.使用具有足够权限的用户名和密码登陆CLI命令行界面;3.在提示符下输入下面的命令：userhost> request system halt…The operating system has halted.Please press any key to reboot除非需要重启设备,此时不要敲任何键,否则设备将进行重启4.等待console输出上面提示信息后,确认操作系统已停止运行,关闭机箱背后电源模块电源;3.2设备重启SRX重启必须按照下面的步骤进行操作：1.管理终端连接SRX console口;2.使用具有足够权限的用户名和密码登陆CLI命令行界面;3.在提示符下输入下面的命令：userhost> request system reboot4.等待console设备的输出,操作系统已经重新启动;3.3操作系统升级SRX操作系统软件升级必须按照下面的步骤进行操作：1.管理终端连接SRX console口,便于升级过程中查看设备重启和软件加载状态;2.SRX上开启FTP服务,并使用具有超级用户权限的非root用户通过FTP客户端将下载的升级软件介质上传到SRX上;3.升级前,执行下面的命令备份旧的软件及设定：userhost> request system snapshot4.加载新的SRX软件：userhost>request system software add validate reboot5.软件加载成功后, SRX将自动重启,重启完成后检查系统当前软件版本号：userhost> show system software3.4密码恢复SRX Root密码丢失,并且没有其他的超级用户权限,那么就需要执行密码恢复,该操作需要中断设备正常运行,但不会丢失配置信息,这点与ScreenOS存在区别;要进行密码恢复,请按照下面操作进行：1.Console口连接SRX,然后重启SRX;2.在启动过程中,console上出现下面的提示的时候,按空格键中断正常启动方式,然后再进入单用户状态,并输入：boot -sLoading /boot/defaults//kernel data=…… syms=……Hit Enter to boot immediately, or space bar for command prompt.loader>loader> boot -s3.执行密码恢复：在以下提示文字后输入recovery,设备将自动进行重启Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh: recovery4.进入配置模式,删除root密码,并重现设置root密码：userhost> configureEntering configuration modeuserhost delete system root-authenticationuserhost set system root-authentication plain-text-passworduserhostNew password:userhostRetype new password:userhost commitcommit complete3.5常用监控维护命令下列操作命令在操作模式下使用,或在配置模式下run show…Show system software 查看当前软件版本号show system uptime 查看系统启动时间Show chassis haredware 查看硬件板卡及序列号show chassis environment 查看硬件板卡当前状态show chassis routing-engine 查看主控板RE资源使用及状态show route 查看路由表show arp 查看ARP表show log messages 查看系统日志show interface terse 查看所有接口运行状态show interface ge-x/y/z detail 查看接口运行细节信息monitor interface ge-x/y/z 动态统计接口数据包转发信息monitor traffic interface ge-x/y/z 动态报文抓取Tcpdump,类似ScreenOSsnoop命令show security flow session summary 查看当前防火墙并发会话数show security flow session 查看当前防火墙具体并发会话clear security flow session all 清除当前sessionshow security alg status 检查全局ALG开启情况SRX对应ScreenOS debug flow basic跟踪报文处理路径的命令：set security flow traceoptions flag basic-datapath 开启SRX基本报文处理Debugset security flow traceoptions file 将输出信息记录到指定文件中set security flow traceoptions file size <file-size> 设置该文件大小,缺省128kset security flow traceoptions packet-filter filter1 destination-prefix 5.5.5.2设置报文跟踪过滤器run file show 查看该Log输出信息SRX对应ScreenOS get tech命令,开Case时需要抓取的信息：request support information。

sr policy策略配置

sr policy策略配置
SR（Segment Routing）策略配置是指在网络设备中配置特定的路由策略，以实现分段路由的功能。

分段路由是一种新型的路由技术，它将路由信息分解为多个段（Segment），每个段对应网络路径中的一个特定节点或者特定的服务。

SR策略配置可以从以下几个方面进行详细的讨论：
1. 配置目的，首先需要明确配置SR策略的目的是什么，比如是为了提高网络的性能、实现流量工程、改善服务质量（QoS）等。

不同的目的会对策略的具体配置产生影响。

2. 策略制定，在进行SR策略配置之前，需要制定详细的策略方案，包括需要应用策略的网络设备、策略的生效范围、具体的路由转发规则等。

这些都需要在制定策略时充分考虑。

3. 设备配置，针对不同的网络设备，SR策略的配置方式可能会有所不同，比如在Cisco、Juniper等厂商的设备上配置SR策略的命令会有所差异。

需要根据具体设备的要求进行相应的配置。

4. 策略参数，在配置SR策略时，需要设置一些参数，比如
Segment Identifier（SID）的分配、策略的优先级、策略的生存时间（TTL）等。

这些参数的设置会直接影响到策略的实际效果。

5. 策略验证，配置完成后，需要进行策略的验证和测试，确保策略能够按照预期的方式进行路由转发，同时不会对网络造成不必要的影响。

总的来说，SR策略配置是一个复杂而又关键的网络配置任务，需要充分考虑各种因素才能够保证配置的正确性和有效性。

在实际操作中，建议在专业人士的指导下进行配置，以确保网络的稳定和安全。

广东移动IP城域网SR业务配置规范7750分册V1.0(试行稿)

广东移动IP城域网SR业务配置规范上海贝尔7750分册－试行稿（V1.0）中国移动通信集团广东有限公司2010年1月编制说明为保证城域网的运行质量，必须在设备能力、网络设计、网络配置、维护流程、支撑系统等环节予以保障。

网络配置主要是指通过在设备上实施具体配置命令，开启设备控制层面和转发层面的功能，实现网络的互通，保证网络具备预期的业务承载能力。

同样的物理网络在不同的配置下所提供的业务承载能力可能差距甚远，此外，由于网络规模不断扩大，设备特性不断变化，配置工作正日益变得复杂，全网配置发生错误的概率也在增加，因此很有必要对城域网网络设备的网络配置予以规范。

本课题涉及的对象就是城域网网络设备配置的相关规范标准，目的是为城域网维护人员提供实用维护工具。

考虑到城域网网络设备维护分工明确，配置规范按分册进行编写，本篇只针对阿尔卡特7750设备制定相关业务配置规范。

版本变更记录目录1. 概述 (5)1.1 目标网络结构 (5)1.2 配置原则 (6)1.3 说明 (6)2. 基本业务介绍及配置 (6)2.1 固定IP专线业务概述 (6)2.2固定IP专线业务配置 (6)3.1VPN业务概述 (12)3.2 VPN业务配置 (12)3.2.1 MPLS-VPN配置方式接入 (12)3.2.2 VPLS配置方式接入 (15)3. 业务常用检查命令 (22)3.1 IES 业务 (22)3.2 vprn 业务 (22)3.3 vpls 业务 (22)1. 概述1.1 目标网络结构IP 城域网的定位：1、网络定位：IP 城域网是位于用户驻地网和CMnet 网之间的网络，既要满足用户的需求也需要适应企业未来的发展。

IP 城域网与城域传送网共同构成了我公司城域综合业务承载平台。

2、业务定位：(1)为公司内部业务应用系统 (营业厅、OA 、BOSS 等)提供接入以及实现自有机楼数据互连等。

(2)为用户提供互联网接入、集团客户接入、VPN 接入等业务。

SR配置规范

password xxx hash 1/1/31/1/31/1/42.5G1/2/11/1/31/1/31/1/3p
1/1/31/1/110.1.1
Idp
keep-alive
shutdow n
exit
no shutdow n
exit
exit
2）配置Mirror目的，指向本地创建的SDP（如是本地镜像则指向本地端口）
在当前环境下列出所有命令。
stri ng?
列出所有在当前环境下可用的以string开头的
命令。
Comma nd?
显示命令标识符及相关关键词。
Comma nd
keyword?
在comma nd中列出与keyword相关的自变量
stri ng<Tab>
输出未完全输入的命令（自动完成功能）或列示
stri ng<Space>
remote-source 10.1.1 ing-svc-label 3001 exit sap 1/1/3:0 create p 10.0.0.…
entry 100 All use subject to applicable lice nse agreeme nts.
Built o n Tue Aug 29 11:54:54 PST 2006 by builder in /b1/R5/pa nos/main
7750SR>c on fig>card# card-type iom-20g-b
7750SR>c on fig>card# no shutdow n
配置MDA模块，事先需确认MDA模块的准确类型：
7750SR>co nfig>card# mda 1

SR基本配置

SRX 300配置上网（WLAN与VLAN都为内部IP）环境介绍设备ge-0/0/0口为外网口,即第一个口，地址，下一跳地址设备ge-0/0/2口为内网口即第三个口，地址，内网口作为PC网关来用，设置DHCP，DHCP设置参数如下：地址段网关DNS ；设置源NAT，用、两个地址做转换NAT地址设置策略允许内网上网创建超级用户root 密码TS…….具体步骤用串口线连接设备console口，设置参数如下：这台设备是有配置的，所以要先清空设备配置，清空完设备配置，需要直接设备初始超级用户的密码，然后保存，才可以完成恢复出厂设置登入设备出现以下root@root>root@root>configure进入配置模式Entering configuration mode[edit]root@root# load factory-default恢复出厂设备warning: activating factory configuration[edit]root@root# set system root-authentication plain-text-password设置超级用户密码New password:Retype new password:[edit]root@root# commitcommit complete[edit]此时回复出厂设置完成，下一步开始配置login: root输入默认用户名rootPassword:输入重置设备前输入的密码root@root% cli敲入cli进入执行模式root@root> configure敲入configure进入配置模式，执行模式代表符号“>”Entering configuration mode[edit]root@root#配置模式“#”root@root# set system login user lvlin class super-user authentication plain-text-password建立用户名为“wangjian”的超级用户New password:为用户“root”设置密码Retype new password:重复输入密码[edit]root@root# delete interfaces ge-0/0/删除接口相关配置，接口默认处于交换[edit]模式Ethernet-switching模式下，要想设置成三层必须先把这个属root@root# delete interfaces fe-0/0/2 unit 0性删除，“.0”和unit0在意义上一样[edit]wangjian# set interfaces ge-0/0/ family inet address 设置ge-0/0/为三层接口地址set interfaces ge-0/0/ family inet address set interfaces fe-0/0/ family inet address 设置Ge-0/0/为三层接口地址 set routing-options static route next-hop routing-options static route next-hop 设置默认路由wangjian# set security zones security-zone untrust interfaces ge-0/0/[edit]设置ge-0/0/口为untrust安全域接口wangjian# set security zones security-zone trust interfaces ge-0/0/[edit]设置fe-0/0/口为trust安全域接口wangjian# delete security nat source rule-set trust-to-untrust[edit]删除系统自带的源nat规则wangjian# set security nat source pool wangjian address to 设置源nat地址池set security nat source pool wangjian address to set security nat sourcerule-set wangjiannat from zone trust[edit]设置nat源安全域wangjian# set security nat source rule-set wangjiannat to zone untrust[edit]设置nat目的安全域wangjian# set security nat source rule-set wangjiannat rule wangjiannat1match source-address 设置nat源地址[edit]wangjian# set security nat source rule-set wangjiannat rule wangjiannat1 then source-nat pool wangjian设置nat关联地址池[edit]wangjian# set security zones security-zone untrust interface ge-0/0/ host-inbound-traffic system-services http[edit]打开接口http管理wangjian# set system services web-management http[edit]打开http全局开关wangjian# delete security policies from-zone trust to-zone untrust policytrust-to untrust删除系统自带策略delete security policies from-zone trust to-zone untrust policy trust-to untrust[edit]wangjian# set security policies from-zone trust to-zone untrust policy wangjian match source-address any[edit]配置策略源地址wangjian# set security policies from-zone trust to-zone untrust policy wangjian match destination-address any配置策略目的地址[edit]wangjian# set security policies from-zone trust to-zone untrust policy wangjian match application any配置策略应用[edit]wangjian# set security policies from-zone trust to-zone untrust policy wangjian then permit配置策略动作[edit]wangjian# set security policies from-zone trust to-zone untrust policy wangjian then log session-init开启策略日志—会话开始[edit]wangjian# set security policies from-zone trust to-zone untrust policy wangjian then log session-close开启策略日志—会话结束[edit]wangjian# delete system services dhcp[edit]删除系统默认dhcpwangjian# set system services dhcp router DHCP参数默认网关wangjian# set system services dhcp pool address-range low DHCP参数地址池开始地址[edit]wangjian# set system services dhcp pool address-range high DHCP参数地址池结束地址[edit]wangjian# set system services dhcp maximum-lease-time 95[edit]DHCP参数分配地址租约时间wangjian# set system services dhcp name-server[edit]DHCP参数DNS服务器wangjian# set system services dhcp name-server[edit]DHCP参数DNS服务器wangjian# set system services dhcp propagate-settings ge-0/0/[edit]设置DHCP信号发散端口wangjian# delete interfaces ge-0/0/[edit]删除接口fe-0/0/所有属性wangjian# set security zones security-zone trust interfaces ge-0/0/ host-inbound-traffic system-services all[edit]设置接口ge-0/0/接口为trust安全域wangjian# set security nat proxy-arp interface ge-0/0/0 address to nat地址池地址在外网接口上做arp代理set security nat proxy-arp interface ge-0/0/0 address to delete interfaces vlan[edit]删除vlan接口wangjian# delete interfaces ge-0/0/3[edit]删除物理接口属性wangjian# delete interfaces fe-0/0/4[edit]wangjian# delete interfaces fe-0/0/5[edit]wangjian# delete interfaces fe-0/0/6[edit]wangjian# delete interfaces fe-0/0/7[edit]wangjian# delete interfaces ge-0/0/1[edit]wangjian# delete vlans[edit]删除vlan这样就可以了，DHCP获取到地址Ping外网附加show命令wangjian# run show interfaces terse查看物理接口属性InterfaceAdmin Link ProtoLocalRemotege-0/0/0upupge-0/0/upupinetupupip-0/0/0upuplsq-0/0/0upuplt-0/0/0upupmt-0/0/0upupsp-0/0/0upupsp-0/0/upupinetsp-0/0/upupinet--> --> 0/0 --> --> 0/0ge-0/0/1updownfe-0/0/2upupfe-0/0/upupinetfe-0/0/3updownfe-0/0/4updownfe-0/0/5updownfe-0/0/6updownfe-0/0/7updownfxp2upupupuptnp0x1greupupipipupupirbupuplo0upupupupinet--> 0/0upupinet--> 0/0--> 0/0--> 0/0--> 0/0--> 0/0upuplsiupupmtunupuppimdupuppimeupuppp0upupppd0upupppe0upupst0upuptapupupvlanupup[edit]wangjian# show | compare跟上次commit前对比敲过的命令[edit security zones security-zone untrust interfaces] ge-0/0/ { ... }+ge-0/0/;[edit]wangjian# rollback 0返回上次commit时的配置load complete[edit]。

CR.BRAS.SR配置示例

四川电信IPTV城域网一平面设备配置模板中国电信股份有限公司四川分公司2011年9 月目录第一章实施规范 (2)1.1 设备命名规范 (2)1.2 端口描述规范 (2)1.2.1 环回接口描述 (2)1.2.2 物理接口描述 (3)1.3 ISIS规范 (4)第二章CR基础配置模板 (6)2.1 系统基本配置.................................................................................... 错误!未定义书签。

2.2 功能配置............................................................................................ 错误!未定义书签。

第三章SR配置模板 (18)3.1 华为ME60配置................................................................................ 错误!未定义书签。

3.1.1 系统基础配置......................................................................... 错误!未定义书签。

3.1.2 功能配置................................................................................. 错误!未定义书签。

3.2 中兴M6000 ....................................................................................... 错误!未定义书签。

3.2.1 系统基本配置......................................................................... 错误!未定义书签。

e4国联通城域网BAS、SR设备配置规范(试行)

内部资料注意保密中国联通城域网BAS/SR设备配置规范（试行）中国联通集团网络公司运维部二零一一年九月目录说明 (3)1.基本配置 (3)1.1 设备名称 (3)1.2 系统时间配置 (4)1.3 NTP配置 (4)1.4文件管理 (4)1.5 Banner配置 (4)2．网管配置 (5)2.1登录AAA (5)2.2 SNMP (5)2.3用户 (6)2.4 SYSLOG (6)2.5 TELNET (7)2.6 SSH (7)2.7 NETFLOW/NETSTREAM (7)2.8带外网管 (8)3．端口配置规范 (8)3.1端口命名格式描述 (8)3.2 loopback (9)3.3 GE/TG (9)3.4端口捆绑 (9)3.5POS (9)4. 路由配置 (10)4.1 静态路由配置 (10)4.2 OSPF配置 (10)4.3 ISIS配置 (11)4.4 BGP配置 (11)4.5 MPLS配置 (12)4.6 BFD配置 (12)5．安全配置 (13)5.1 ACL (13)5.2服务管理 (13)5.3引擎防护 (14)6. 业务实现 (14)6.1 PPPOE业务 (14)6.2 专线业务 (14)6.3 VPDN业务 (15)6.4 WLAN业务 (15)6.5 MPLS VPN 业务 (16)6.6 VPLS业务 (16)6.7 VRRP (16)附录：配置规范执行要求 (17)说明为了加强对城域网设备的管理，规范城域网主要设备的配置，避免人为操作造成的网络故障，集团网络公司组织相关省级分公司，制定了《中国联通城域网BAS/SR设备配置规范（试行）》。

考虑到各省业务发展可能存在的差异性，规范对具体配置要求进行了分级，按照执行的强度分为A、B、C等3级，分别为全国统一、省内统一、可选配置，详见附录“配置规范执行要求”。

1.基本配置1.1 设备名称【配置描述】: 配置设备名称【规范要求】:1.1.1 设备名称要求符合命名规范；要求格式为AAAA-BBBB-CCCC-DE。

H3C SR8800 万兆核心路由器接口管理配置指导-整本手册

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

H3C、、Aolynk、、H3Care、、TOP G、、IRF、NetPilot、Neocean、NeoVTL、SecPro、SecPoint、SecEngine、SecPath、Comware、Secware、Storware、NQA、VVG、V2G、V n G、PSPT、XGbus、N-Bus、TiGem、InnoVision、HUASAN、华三均为杭州华三通信技术有限公司的商标。

对于本手册中出现的其它公司的商标、产品标识及商品名称，由各自权利人拥有。

由于产品版本升级或其他原因，本手册内容有可能变更。

H3C保留在没有任何通知或者提示的情况下对本手册的内容进行修改的权利。

本手册仅作为使用指导，H3C尽全力在本手册中提供准确的信息，但是H3C并不确保手册内容完全没有错误，本手册中的所有陈述、信息和建议也不构成任何明示或暗示的担保。

前言H3C SR8800万兆核心路由器配置指导共分为十三本手册，介绍了SR8800万兆核心路由器各软件特性的原理及其配置方法，包含原理简介、配置任务描述和配置举例。

《接口管理配置指导》主要介绍了以太网端口、WAN接口、POS接口、CPOS接口、E-CPOS接口、Loopback接口和Null 接口等内容。

前言部分包含如下内容：z读者对象z本书约定z产品配套资料z资料获取方式z技术支持z资料意见反馈读者对象本手册主要适用于如下工程师：z网络规划人员z现场技术支持与维护人员z负责网络配置和维护的网络管理员本书约定1.命令行格式约定格式意义粗体命令行关键字（命令中保持不变、必须照输的部分）采用加粗字体表示。

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。

SR7750配置步骤-自己总结滴

SR7750配置步骤一、基本配置1、在config-system 视图下，1）起名字标示此设备：name liaocheng-842-7750-ar1SystemPort 有两种模式network和access 又都分为输入、输出两个方向ingress egressconfig>system>security>profile 默认为none 不授权修改默认启动文件，确保下次依然生效vrrp配置时要注意主地址和vrrp地址一定要在同一子网下。

掩码要正确。

2、在config-router 视图下，在router 视图下做autonomous-system 200 AS号，否则bgp邻居无法建立配置习惯为进config—router ，，interface，bgp，isis等在此视图下。

而不是router bgp 100 ，这个设备的treeRouter id 必配。

Family ipv4 router>bgp# info----------------------------------------------group "to-h3c"type externallocal-as 200peer-as 100neighbor 10.10.10.2exitexitgroup "to-3528"local-address 10.10.20.1type externalpeer-as 100neighbor 10.10.20.2exit端口的典型配置接用户的端口port 1/2/5description "GE1/2/5 To SDLC-T600-1 GE1/0/0->OMC&Signal"ethernetmode accessencap-type dot1qmtu 9192no autonegotiateexitno shutdown接上行设备端口port 1/1/1description "POS1/1/1 To SDJN-YXS-N5KE-B1 POS12/0/2 155M JN-LC S-1N7002(backup)"networkegresspoolslope-policy "CU-WRED"exitexitexitsonet-sdhframing sdhhold-time up 30 down 1speed oc3pathmtu 9180scramblenetworkqueue-policy "CU-NetworkEgressQ"exitno shutdownexitexitno shutdown都分为全局配置，具体配置在什么视图下建立的，show的时候就得注意。

华为SR及交换机qinq配置节省IP地址案例

华为SR及交换机qinq配置节省IP地址案例一、网络拓扑图如下二、目的：1、节约IP地址使用，各PC分配同一网段IP地址，使用相同网关。

2、各PC实现两层隔离，三层互通。

三、具体配置：1、SR上下行接口A主接口配置：mode user-terminationportswitch下行接口A子接口配置：control-vid （外层vlan号）qinq-terminationqinq termination pe-vid （外层vlan号）ce-vid （内层vlan号）ip address （网关IP地址）arp broadcast enable2、S9312上全局配置：Vlan （外层vlan号）上行接口B配置实现外层vlan透传上联口：port link-type trunkundo port trunk allow-pass vlan 1port trunk allow-pass vlan （外层vlan号）（1）接口C下如需要挂PC，配置如下：全局配置，实现用户IP地址与vlan绑定：user-bind static ip-address（分配给PC的IP地址）vlan（外层vlan号）ce-vlan（内层vlan号）下行接口C配置：undo port hybrid vlan 1port hybrid untagged vlan （外层vlan号）port vlan-stacking untagged stack-vlan （外层vlan号）stack-inner-vlan （内层vlan号）ip source check user-bind enableport-isolate enable group 1（2）S9312下挂S3528后再接PCA、S9312下行接口D配置，实现透传port hybrid untagged vlan （外层vlan号）port vlan-stacking vlan （内层vlan号）stack-vlan（外层vlan号）B、S5328上全局配置：Vlan （内层vlan号）user-bind static ip-address（分配给PC的IP地址）vlan（内层vlan号）上行接口E配置：port link-type trunkundo port trunk allow-pass vlan 1port trunk allow-pass vlan （内层vlan号）下行用户口F配置：port link-type accessport default vlan （内层vlan号）ip source check user-bind enable。

武汉电信iptv二平面srne40ex配置规范v3.5(11扩2期)

华为SR NE40E-X配置规范地址池分担:每对SR 两个地址池，地址池1在SR1主用，地址池2在SR2主用域名：创建两个不同的域，域tv01绑定地址池1，域tv02绑定地址池2.接口绑定：在绑定到不同的下行接口路由发布：通过BGP引入UNR路由发布业务地址，发布时设置策略:地址池1，SR1优先，地址池2，SR2上优先。

隧道采用 lsp隧道，优选SR之间链路bfd名称:vrrp1001,vrrp1002...bfd标识符：local和remote 设置相同1001,1002,1003,1004...vrrp id: 同一台交换机设置不同101,102；不同交换机可以重复使用，vrrp ID由于设备限制，相同的ID 只能重复16次，操作16个就无法配置，依次增加。

remote-backup-profile名称：按交换机机名称+链路组的英文（first，second）地址池名称：TV01 TV02 TV03 TV04....域名：TV01与TV02绑定到不同下行口实现分担，TV01在SR1上主用，TV02在SR2上主用#clock timezone BJT add 08:00:00 本地时区信息进行设置，配置信息里看不见//该配置表示把ME60的时区配置成东八区（即是北京时间）#sysname WH-WH-YFC-SR-1.M2N.NE40E#multicast routing-enable 使能组播路由#multicast load-splitting source-group组播负载分担#user-group iptv 配置IPTV用户组#slot 1 启用单板BAS功能bas enable#Bfd 启用BFD#super password level 3 cipher djttdkl#info-center source default channel 2 log level warning 配置把warning等级以上的日志信息送往日志主机info-center loghost source LoopBack0info-center loghost 58.53.191.132 facility local4info-center loghost 58.53.191.131 facility local4info-center loghost 221.232.247.45 facility local2info-center loghost 202.103.28.3##radius-server source interface LoopBack0radius-server group telnet_authradius-server authentication 202.103.28.138 1645 weight 0radius-server authentication 202.103.28.139 1645 weight 0radius-server accounting 202.103.28.138 1646 weight 0radius-server accounting 202.103.28.139 1646 weight 0radius-server shared-key whdxwlb123undo radius-server user-name domain-included＃ip vpn-instance hbitmsroute-distinguisher 4809:26000vpn-target 4809:2600001 export-extcommunityvpn-target 4809:2600000 import-extcommunity#mpls lsr-id 221.235.39.249 本设备的LoopBack0地址mpls 全局模式下使能mpls，进入MPLS视图lsp-trigger host // 只对32 位地址分配MPLS LDP 标签#mpls ldp 全局使能LDP，并创建LDP的公网实例#isis 27graceful-restartis-level level-2cost-style widetimer lsp-generation 1 1 20 配置定时器flash-flood level-2network-entity 86.5125.0027.2212.3503.9249.00 LOOPBACK地址is-name WH-WH-YFC-SR-1.M2N.NE40E打开IS-IS 动态主机名交换功能preference 150timer spf 1 50 100log-peer-change 记录邻居变化maximum load-balancing 8 最大ECMP 路径数设为8 条timer lsp-max-age 65535 配置LSP 定时器timer lsp-refresh 32768 配置LSP 定时器set-overload on-startup 300#acl number 2000 telnet访问控制列表rule 0 permit source 202.103.24.0 0.0.0.255rule 1 permit source 202.103.29.0 0.0.0.255rule 2 permit source 202.103.26.0 0.0.0.255rule 3 permit source 202.103.28.0 0.0.0.255rule 4 permit source 219.140.254.0 0.0.0.255rule 5 permit source 59.175.240.0 0.0.15.255rule 6 permit source 221.232.248.0 0.0.7.255rule 7 permit source 202.103.37.0 0.0.0.255rule 9 permit source 10.16.0.0 0.15.255.255rule 10 permit source 111.175.224.0 0.0.3.255rule 11 permit source 111.175.232.0 0.0.7.255rule 12 permit source 111.175.240.0 0.0.15.255rule 13 permit source 58.49.0.0 0.0.7.255rule 14 permit source 58.49.8.0 0.0.0.255rule 15 permit source 58.49.9.0 0.0.0.255rule 16 permit source 58.53.191.58 0rule 17 permit source 221.232.247.45 0rule 18 permit source 61.183.6.22 0rule 19 permit source 221.235.39.0 0.0.0.255rule 100 deny#acl number 2001 snmp访问控制列表rule 0 permit source 202.103.24.0 0.0.0.255rule 1 permit source 219.140.254.0 0.0.0.255rule 2 permit source 202.103.28.0 0.0.0.255rule 3 permit source 202.103.37.16 0.0.0.15rule 100 deny#acl number 2005 snmp访问控制列表rule 10 permit source 202.103.28.0 0.0.0.15rule 20 permit source 202.103.37.16 0.0.0.15rule 30 permit source 58.53.191.0 0.0.0.255rule 100 deny#acl number 3030rule 10 permit ip destination 239.254.96.0 0.0.0.255#acl number 3100rule 5 permit tcp destination-port eq echorule 10 permit tcp destination-port eq CHARgenrule 15 permit udp destination-port eq 19rule 20 permit tcp destination-port eq finger＃acl number 6030 针对用户组iptv的允许访问控制列表rule 5 permit ip source ip-address 121.60.244.0 0.0.3.255 destination user-group iptv rule 10 permit ip source ip-address 121.60.248.0 0.0.3.255 destination user-group iptv rule 15 permit ip source ip-address 121.60.252.0 0.0.3.255 destination user-group iptv rule 20 permit ip source ip-address 121.60.236.0 0.0.3.255 destination user-group iptv rule 25 permit ip source ip-address 121.60.240.0 0.0.3.255 destination user-group iptv rule 30 permit ip source ip-address 116.210.252.0 0.0.0.255 destination user-group iptv rule 35 permit ip source ip-address 116.210.253.0 0.0.0.255 destination user-group iptv rule 40 permit ip source ip-address 27.29.255.0 0.0.0.255 destination user-group iptv #rule 5 permit ip destination user-group iptv# 定义流traffic classifier permitiptv operator or //定义类（类的作用是匹配数据流）if-match acl 6030traffic classifier denyiptv-internet operator orif-match acl 6031# 定义动作默认为permit traffic behavior permit 定义一个流行为,名字是permit（流行为的名字是可以随便取的，如果该流行为下什么也不配，默认的动作是permit)traffic behavior denydeny# 定义策略traffic policy 1share-modeclassifier permitiptv behavior permitclassifier denyiptv-internet behavior deny#traffic-policy 1 inboundtraffic-policy 1 outbound#slot 1cpu-defend policy 4 适用于LPUG 单板（policy4-10）＃cpu-defend policy 4 适用于LPUG 单板（policy4-10）blacklist acl 3100#slot 2cpu-defend policy 14 适用于LPUF-20 单板（policy14-20）＃cpu-defend-policy 14blacklist acl 3100#dhcp-server group tv01 SR1上主用dhcp-server 61.183.4.146dhcp-server source interface LoopBack0dhcp-server giaddr ip-address 27.29.24.1#dhcp-server group tv02 SR2上主用，本期暂时不用创建dhcp-server 61.183.4.146dhcp-server source interface LoopBack0dhcp-server giaddr ip-address 27.29.28.1#ip pool tv01 bas remote SR1上主用gateway 27.29.24.1 255.255.252.0#ip pool tv02 bas remote SR2上主用，本期暂时不用创建gateway 27.29.28.1 255.255.252.0dhcp-server group tv02＃ip pool itms0 bas localvpn-instance hbitmsgateway 10.65.48.1 255.255.252.0section 0 10.65.48.2 10.65.51.254dns-server 192.168.0.42 192.168.0.47aaamulticast-list group1 index 0 group-address 239.254.96.1multicast-list group2 index 1 group-address 239.254.96.2multicast-list group3 index 2 group-address 239.254.96.3multicast-list group4 index 3 group-address 239.254.96.4multicast-list group5 index 4 group-address 239.254.96.5multicast-list group6 index 5 group-address 239.254.96.6multicast-list group7 index 6 group-address 239.254.96.7multicast-list group8 index 7 group-address 239.254.96.8multicast-list group9 index 8 group-address 239.254.96.9multicast-list group10 index 9 group-address 239.254.96.10 multicast-list group11 index 10 group-address 239.254.96.11 multicast-list group12 index 11 group-address 239.254.96.12 multicast-list group13 index 12 group-address 239.254.96.13 multicast-list group14 index 13 group-address 239.254.96.14 multicast-list group15 index 14 group-address 239.254.96.15 multicast-list group16 index 15 group-address 239.254.96.16 multicast-list group17 index 16 group-address 239.254.96.17 multicast-list group18 index 17 group-address 239.254.96.18 multicast-list group19 index 18 group-address 239.254.96.19 multicast-list group20 index 19 group-address 239.254.96.20 multicast-list group21 index 20 group-address 239.254.96.21 multicast-list group22 index 21 group-address 239.254.96.22 multicast-list group23 index 22 group-address 239.254.96.23 multicast-list group24 index 23 group-address 239.254.96.24 multicast-list group25 index 24 group-address 239.254.96.25 multicast-list group26 index 25 group-address 239.254.96.26 multicast-list group27 index 26 group-address 239.254.96.27 multicast-list group28 index 27 group-address 239.254.96.28 multicast-list group29 index 28 group-address 239.254.96.29 multicast-list group30 index 29 group-address 239.254.96.30 multicast-list group31 index 30 group-address 239.254.96.31 multicast-list group32 index 31 group-address 239.254.96.32 multicast-list group33 index 32 group-address 239.254.96.33 multicast-list group34 index 33 group-address 239.254.96.34multicast-list group38 index 37 group-address 239.254.96.38 multicast-list group39 index 38 group-address 239.254.96.39 multicast-list group40 index 39 group-address 239.254.96.40 multicast-list group41 index 40 group-address 239.254.96.41 multicast-list group42 index 41 group-address 239.254.96.42 multicast-list group43 index 42 group-address 239.254.96.43 multicast-list group44 index 43 group-address 239.254.96.44 multicast-list group45 index 44 group-address 239.254.96.45 multicast-list group46 index 45 group-address 239.254.96.46 multicast-list group47 index 46 group-address 239.254.96.47 multicast-list group48 index 47 group-address 239.254.96.48 multicast-list group49 index 48 group-address 239.254.96.49 multicast-list group50 index 49 group-address 239.254.96.50 multicast-list group51 index 50 group-address 239.254.96.51 multicast-list group52 index 51 group-address 239.254.96.52 multicast-list group53 index 52 group-address 239.254.96.53 multicast-list group54 index 53 group-address 239.254.96.54 multicast-list group55 index 54 group-address 239.254.96.55 multicast-list group56 index 55 group-address 239.254.96.56 multicast-list group57 index 56 group-address 239.254.96.57 multicast-list group58 index 57 group-address 239.254.96.58 multicast-list group59 index 58 group-address 239.254.96.59 multicast-list group60 index 59 group-address 239.254.96.60 multicast-list group61 index 60 group-address 239.254.96.61 multicast-list group62 index 61 group-address 239.254.96.62 multicast-list group63 index 62 group-address 239.254.96.63 multicast-list group64 index 63 group-address 239.254.96.64 multicast-list group65 index 64 group-address 239.254.96.65 multicast-list group66 index 65 group-address 239.254.96.66 multicast-list group67 index 66 group-address 239.254.96.67 multicast-list group68 index 67 group-address 239.254.96.68 multicast-list group69 index 68 group-address 239.254.96.69 multicast-list group70 index 69 group-address 239.254.96.70 multicast-list group71 index 70 group-address 239.254.96.71 multicast-list group72 index 71 group-address 239.254.96.72 multicast-list group73 index 72 group-address 239.254.96.73 multicast-list group74 index 73 group-address 239.254.96.74 multicast-list group75 index 74 group-address 239.254.96.75 multicast-list group76 index 75 group-address 239.254.96.76 multicast-list group77 index 76 group-address 239.254.96.77 multicast-list group78 index 77 group-address 239.254.96.78 multicast-list group79 index 78 group-address 239.254.96.79 multicast-list group80 index 79 group-address 239.254.96.80multicast-list group84 index 83 group-address 239.254.96.84multicast-list group85 index 84 group-address 239.254.96.85multicast-list group86 index 85 group-address 239.254.96.86multicast-list group87 index 86 group-address 239.254.96.87multicast-list group88 index 87 group-address 239.254.96.88multicast-list group89 index 88 group-address 239.254.96.89multicast-list group90 index 89 group-address 239.254.96.90multicast-list group91 index 90 group-address 239.254.96.91multicast-list group92 index 91 group-address 239.254.96.92multicast-list group93 index 92 group-address 239.254.96.93multicast-list group94 index 93 group-address 239.254.96.94multicast-list group95 index 94 group-address 239.254.96.95multicast-list group96 index 95 group-address 239.254.96.96multicast-list group97 index 96 group-address 239.254.96.97multicast-list group98 index 97 group-address 239.254.96.98multicast-list group99 index 98 group-address 239.254.96.99multicast-list group100 index 99 group-address 239.254.96.100 multicast-list group101 index 100 group-address 239.254.96.101 multicast-list group102 index 101 group-address 239.254.96.102 multicast-list group103 index 102 group-address 239.254.96.103 multicast-list group104 index 103 group-address 239.254.96.104 multicast-list group105 index 104 group-address 239.254.96.105 multicast-list group106 index 105 group-address 239.254.96.106 multicast-list group107 index 106 group-address 239.254.96.107 multicast-list group108 index 107 group-address 239.254.96.108 multicast-list group109 index 108 group-address 239.254.96.109 multicast-list group110 index 109 group-address 239.254.96.110 multicast-list group111 index 110 group-address 239.254.96.111 multicast-list group112 index 111 group-address 239.254.96.112 multicast-list group113 index 112 group-address 239.254.96.113 multicast-list group114 index 113 group-address 239.254.96.114 multicast-list group115 index 114 group-address 239.254.96.115 multicast-list group116 index 115 group-address 239.254.96.116 multicast-list group117 index 116 group-address 239.254.96.117 multicast-list group118 index 117 group-address 239.254.96.118 multicast-list group119 index 118 group-address 239.254.96.119 multicast-list group120 index 119 group-address 239.254.96.120 multicast-list group121 index 120 group-address 239.254.96.121 multicast-list group122 index 121 group-address 239.254.96.122 multicast-list group123 index 122 group-address 239.254.96.123 multicast-list group124 index 123 group-address 239.254.96.124 multicast-list group125 index 124 group-address 239.254.96.125 multicast-list group126 index 125 group-address 239.254.96.126multicast-list group130 index 129 group-address 239.254.96.130 multicast-list group131 index 130 group-address 239.254.96.131 multicast-list group132 index 131 group-address 239.254.96.132 multicast-list group133 index 132 group-address 239.254.96.133 multicast-list group134 index 133 group-address 239.254.96.134 multicast-list group135 index 134 group-address 239.254.96.135 multicast-list group136 index 135 group-address 239.254.96.136 multicast-list group137 index 136 group-address 239.254.96.137 multicast-list group138 index 137 group-address 239.254.96.138 multicast-list group139 index 138 group-address 239.254.96.139 multicast-list group140 index 139 group-address 239.254.96.140 multicast-list group141 index 140 group-address 239.254.96.141 multicast-list group142 index 141 group-address 239.254.96.142 multicast-list group143 index 142 group-address 239.254.96.143 multicast-list group144 index 143 group-address 239.254.96.144 multicast-list group145 index 144 group-address 239.254.96.145 multicast-list group146 index 145 group-address 239.254.96.146 multicast-list group147 index 146 group-address 239.254.96.147 multicast-list group148 index 147 group-address 239.254.96.148 multicast-list group149 index 148 group-address 239.254.96.149 multicast-list group150 index 149 group-address 239.254.96.150 multicast-list group151 index 150 group-address 239.254.96.151 multicast-list group152 index 151 group-address 239.254.96.152 multicast-list group153 index 152 group-address 239.254.96.153 multicast-list group154 index 153 group-address 239.254.96.154 multicast-list group155 index 154 group-address 239.254.96.155 multicast-list group156 index 155 group-address 239.254.96.156 multicast-list group157 index 156 group-address 239.254.96.157 multicast-list group158 index 157 group-address 239.254.96.158 multicast-list group159 index 158 group-address 239.254.96.159 multicast-list group160 index 159 group-address 239.254.96.160 multicast-list group161 index 160 group-address 239.254.96.161 multicast-list group162 index 161 group-address 239.254.96.162 multicast-list group163 index 162 group-address 239.254.96.163 multicast-list group164 index 163 group-address 239.254.96.164 multicast-list group165 index 164 group-address 239.254.96.165 multicast-list group166 index 165 group-address 239.254.96.166 multicast-list group167 index 166 group-address 239.254.96.167 multicast-list group168 index 167 group-address 239.254.96.168 multicast-list group169 index 168 group-address 239.254.96.169 multicast-list group170 index 169 group-address 239.254.96.170 multicast-list group171 index 170 group-address 239.254.96.171 multicast-list group172 index 171 group-address 239.254.96.172multicast-list group176 index 175 group-address 239.254.96.176 multicast-list group177 index 176 group-address 239.254.96.177 multicast-list group178 index 177 group-address 239.254.96.178 multicast-list group179 index 178 group-address 239.254.96.179 multicast-list group180 index 179 group-address 239.254.96.180 multicast-list group181 index 180 group-address 239.254.96.181 multicast-list group182 index 181 group-address 239.254.96.182 multicast-list group183 index 182 group-address 239.254.96.183 multicast-list group184 index 183 group-address 239.254.96.184 multicast-list group185 index 184 group-address 239.254.96.185 multicast-list group186 index 185 group-address 239.254.96.186 multicast-list group187 index 186 group-address 239.254.96.187 multicast-list group188 index 187 group-address 239.254.96.188 multicast-list group189 index 188 group-address 239.254.96.189 multicast-list group190 index 189 group-address 239.254.96.190 multicast-list group191 index 190 group-address 239.254.96.191 multicast-list group192 index 191 group-address 239.254.96.192 multicast-list group193 index 192 group-address 239.254.96.193 multicast-list group194 index 193 group-address 239.254.96.194 multicast-list group195 index 194 group-address 239.254.96.195 multicast-list group196 index 195 group-address 239.254.96.196 multicast-list group197 index 196 group-address 239.254.96.197 multicast-list group198 index 197 group-address 239.254.96.198 multicast-list group199 index 198 group-address 239.254.96.199 multicast-list group200 index 199 group-address 239.254.96.200 multicast-list group201 index 200 group-address 239.254.96.201 multicast-list group202 index 201 group-address 239.254.96.202 multicast-list group203 index 202 group-address 239.254.96.203 multicast-list group204 index 203 group-address 239.254.96.204 multicast-list group205 index 204 group-address 239.254.96.205 multicast-list group206 index 205 group-address 239.254.96.206 multicast-list group207 index 206 group-address 239.254.96.207 multicast-list group208 index 207 group-address 239.254.96.208 multicast-list group209 index 208 group-address 239.254.96.209 multicast-list group210 index 209 group-address 239.254.96.210 multicast-list group211 index 210 group-address 239.254.96.211 multicast-list group212 index 211 group-address 239.254.96.212 multicast-list group213 index 212 group-address 239.254.96.213 multicast-list group214 index 213 group-address 239.254.96.214 multicast-list group215 index 214 group-address 239.254.96.215 multicast-list group216 index 215 group-address 239.254.96.216 multicast-list group217 index 216 group-address 239.254.96.217 multicast-list group218 index 217 group-address 239.254.96.218multicast-list group222 index 221 group-address 239.254.96.222multicast-list group223 index 222 group-address 239.254.96.223multicast-list group224 index 223 group-address 239.254.96.224multicast-list group225 index 224 group-address 239.254.96.225multicast-list group226 index 225 group-address 239.254.96.226multicast-list group227 index 226 group-address 239.254.96.227multicast-list group228 index 227 group-address 239.254.96.228multicast-list group229 index 228 group-address 239.254.96.229multicast-list group230 index 229 group-address 239.254.96.230multicast-list group231 index 230 group-address 239.254.96.231multicast-list group232 index 231 group-address 239.254.96.232multicast-list group233 index 232 group-address 239.254.96.233multicast-list group234 index 233 group-address 239.254.96.234multicast-list group235 index 234 group-address 239.254.96.235multicast-list group236 index 235 group-address 239.254.96.236multicast-list group237 index 236 group-address 239.254.96.237multicast-list group238 index 237 group-address 239.254.96.238multicast-list group239 index 238 group-address 239.254.96.239multicast-list group240 index 239 group-address 239.254.96.240multicast-list group241 index 240 group-address 239.254.96.241multicast-list group242 index 241 group-address 239.254.96.242multicast-list group243 index 242 group-address 239.254.96.243multicast-list group244 index 243 group-address 239.254.96.244multicast-list group245 index 244 group-address 239.254.96.245multicast-list group246 index 245 group-address 239.254.96.246multicast-list group247 index 246 group-address 239.254.96.247multicast-list group248 index 247 group-address 239.254.96.248multicast-list group249 index 248 group-address 239.254.96.249multicast-list group250 index 249 group-address 239.254.96.250multicast-list group251 index 250 group-address 239.254.96.251multicast-list group252 index 251 group-address 239.254.96.252multicast-list group253 index 252 group-address 239.254.96.253multicast-list group254 index 253 group-address 239.254.96.254multicast-profile stbprofilemulticast-list list-index 0 254authentication-scheme default0authentication-scheme default1authentication-scheme defaultauthentication-mode radius localauthentication-scheme none 设置认证计费模版为不认证、不计费authentication-mode noneauthentication-scheme telnet_authauthentication-mode radius localauthorization-scheme defaultauthorization-mode if-authenticated local#accounting-scheme default0accounting-scheme default1accounting-scheme defaultaccounting-scheme noneaccounting-mode noneaccounting-scheme telnet_accaccounting start-fail online#vlanpvc-to-username standard 设置ME60上送RADIUS服务器的Nas-Port-Id属性的格式#domain default_adminauthentication-scheme telnet_authaccounting-scheme telnet_accadminuser-priority 1radius-server group telnet_auth#domain tv01 创建IPTV域绑定奇数地址池authentication-scheme none 邦定不认证模版accounting-scheme none 邦定不计费模版ip-pool tv01 绑定IPTV远端地址池multicast-profile stbprofile 绑定组播频道模版user-priority upstream 5user-priority downstream 5user-group iptv 绑定IPTV用户组#domain tv02 创建IPTV2域绑定偶数地址池，本期暂时不用创建authentication-scheme none 邦定不认证模版accounting-scheme none 邦定不计费模版ip-pool tv02 绑定IPTV远端地址池multicast-profile stbprofile 绑定组播频道模版user-priority upstream 5user-priority downstream 5user-group iptv 绑定IPTV用户组#domain hbitmsauthentication-scheme noneaccounting-scheme nonevpn-instance hbitmsip-pool itms0#热备备份隧道配置：tunnel-policy rui01备份隧道策略tunnel select-seq lsp load-balance-number 1#热备模板：remote-backup-service tv rui备份服务设置peer 221.235.39.249 source 221.235.39.250 port 20000 SR loopback地址作为源地址track interface GigabitEthernet1/0/0 SR上行接口track interface GigabitEthernet8/0/0 SR上行接口protect tnl-policy rui01 peer-ip 221.235.39.249 interface gigabitethernet 1/0/1 SR之间接口ip-pool tv01绑定主用地址池，SR1上绑定tv01，SR2上绑定tv02#remote-backup-profile hzl-8505-2KD-F rui备份模版，hzl-8505-2KD交换机设备名称，F（first）代表第一组链路service-type brasbackup-id 101 remote-backup-service tvpeer-backup hotvrrp-id 101 interface GigabitEthernet1/0/2.4093#remote-backup-profile hzl-8505-2KD-S rui备份模版，hzl-8505-2KD交换机设备名称，S（second）代表第二组链路service-type brasbackup-id 102 remote-backup-service tvpeer-backup hotvrrp-id 102 interface GigabitEthernet1/0/3.4094#local-aaa-serveruser wlb321 password cipher AD^MJRF%^(7Q=^Q`MAF4<1!! authentication-type T MSR上行接口配置：#interface GigabitEthernet1/0/0 //SR上行到CR接口配置control-flapmtu 4470description uT:WH-WH-HS-CR-1.M2N.NE5000E:(F0812500036)10GE9/0/0 F0812500036为光路编码，找工程局要，大小写不能错。

7750 SR OS 路由器配置指南.pdf_1701712574.009497说明书

Common CLI Command DescriptionsIn This ChapterThis section provides information about common Command Line Interface (CLI) syntax andcommand usage.Topics in this chapter include:•SAP syntax on page 616Common CLI Command DescriptionsCommon Service CommandssapSyntax[no] sap sap-idDescription This command specifies the physical port identifier portion of the SAP definition.Parameters sap-id — Specifies the physical port identifier portion of the SAP definition.The sap-id can be configured in one of the following formats:null[port-id | bundle-id| bpgrp-id | lag-id | aps-id]port-id: 1/1/3bundle-id: bundle-ppp-1/1.1bpgrp-id: bpgrp-ima-1lag-id: lag-63aps-id: aps-1dot1q[port-id | bundle-id| bpgrp-id | lag-id | aps-id]:qtag1port-id:qtag1: 1/1/3:100bundle-id: bundle-ppp-1/1.1bpgrp-id: bpgrp-ima-1lag-id:qtag1:lag-61:102aps-id:qtag1: aps-1:27qinq[port-id |bundle-id| bpgrp-id | lag-id]:qtag1.qtag2port-id:qtag1.qtag2: 1/1/3:100.10bundle-id: bundle-ppp-1/1.1bpgrp-id: bpgrp-ima-1lag-id:qtag1.qtag2:lag-10:atm[port-id | aps-id | bundle-id | bpgrp-id][:vpi/vci |vpi |vpi1.vpi2]port-id: 1/1/1aps-id: aps-1bundle-id: bundle-ima-1/1.1bundle-ppp-1/1.1bpgrp-id: bpgrp-ima-1vpi/vci: 16/26vpi: 16vpi1.vpi2: 16.200frame-relay [port-id| aps-id]:dlci port-id: 1/1/1:100aps-id: aps-1dlci: 16cisco-hdlc slot/mda/port.channel port-id: 1/1/3.1Common CLI Command Descriptions Values:sap-id null[port-id | bundle-id | bpgrp-id | lag-id | aps-id]dot1q [port-id | bundle-id | bpgrp-id | lag-id | aps-id]:qtag1qinq[port-id | bundle-id | bpgrp-id | lag-id]:qtag1.qtag2atm [port-id | aps-id][:vpi/vci|vpi| vpi1.vpi2]frame [port-id | aps-id]:dlcicisco-hdlc slot/mda/port.channelcem slot/mda/port.channelima-grp [bundle-id[:vpi/vci|vpi|vpi1.vpi2]port-id slot/mda/port[.channel]bundle-id bundle-type-slot/mda.bundle-numbundle keywordtype ima, fr, pppbundle-num 1 — 336bpgrp-id bpgrp-type-bpgrp-numbpgrp keywordtype ima, fr, pppbpgrp-num 1 — 2000aps-id aps-group-id[.channel]aps keywordgroup-id 1 — 64ccag-id ccag-id.path-id[cc-type]:cc-idccag keywordid 1 — 8path-id a, bcc-type .sap-net, .net-sapcc-id 0 — 4094lag-id lag-idlag keywordid 1 — 200qtag1 0 — 4094qtag2 *, 0 — 4094vpi NNI: 0 — 4095UNI: 0 — 255vci 1, 2, 5 — 65535dlci 16 — 1022ipsec-id ipsec-id.[private | public]:tagipsec keywordid 1 — 4tag 0 — 4094bundle-id — Specifies the multilink bundle to be associated with this IP interface. The bundle keyword must be entered at the beginning of the parameter.The command syntax must be configured as follows:bundle-id:bundle-type-slot-id/mda-slot.bundle-numbundle-id value range: 1 — 336For example:Common CLI Command Descriptions*A:ALA-12>config# port bundle-ppp-5/1.1*A:ALA-12>config>port# multilink-bundlebgprp-id — Specifies the bundle protection group ID to be associated with this IP interface. The bpgrp keyword must be entered at the beginning of the parameter.The command syntax must be configured as follows:bpgrp-id: bpgrp-type-bpgrp-numtype:imabpgrp-num value range: 1 — 2000For example:*A:ALA-12>config# port bpgrp-ima-1*A:ALA-12>config>service>vpls$ sap bpgrp-ima-1qtag1, qtag2 — Specifies the encapsulation value used to identify the SAP on the port or sub-port. If this parameter is not specificially defined, the default value is 0.Values qtag1: * | 0 — 4094qtag2 : * | 0 — 4094The values depends on the encapsulation type configured for the interface. The following tabledescribes the allowed values for the port and encapsulation types.Ethernet Dot1q0 — 4094The SAP is identified by the 802.1Q tag on the port.Note that a 0 qtag1 value also accepts untagged packetson the dot1q port.Ethernet QinQ qtag1: 0 — 4094qtag2: 0 — 4094The SAP is identified by two 802.1Q tags on the port. Note that a 0 qtag1 value also accepts untagged packets on the Dot1q port.SONET/SDH IPCP-The SAP is identified by the channel. No BCP isdeployed and all traffic is IP.SONET/SDH TDM BCP-Null0The SAP is identified with a single service on thechannel. Tags are assumed to be part of the customerpacket and not a service delimiter.SONET/SDHTDMBCP-Dot1q0 — 4094The SAP is identified by the 802.1Q tag on the channel.SONET/SDH TDM Frame Relay16 — 991The SAP is identified by the data link connectionidentifier (DLCI).SONET/SDH ATM ATM vpi (NNI) 0 — 4095vpi (UNI) 0 — 255vci 1, 2, 5 — 65535The SAP is identified by port or by PVPC or PVCCidentifier (vpi, vpi/vci, or vpi range)Common CLI Command Descriptions sap ipsec-id.private|public:tag — This parameter associates an IPSec group SAP with this interface. This is the public side for an IPSec tunnel. Tunnels referencing this IPSec group in the private side may be created if their local IP is in the subnet of the interface subnet and the routing context specified matches with the one of the interface.This context will provide a SAP to the tunnel. The operator may associate an ingress and egress QoS policies as well as filters and virtual scheduling contexts. Internally this creates an Ethernet SAP that will be used to send and receive encrypted traffic to and from the MDA. Multiple tunnels can beassociated with this SAP. The “tag” will be a dot1q value. The operator may see it as an identifier. The range is limited to 1 — 4095.Common CLI Command Descriptions。

7750SR路由器快速配置手册

阿尔卡特7750SR路由器快速配置手册上海贝尔阿尔卡特股份有限公司7750SR 路由器日常维护手册第 2 页共 55 页 2 目录1. 总体概述 (4)2.新增板卡配置 (6)2.1. IOM 模块配置 (7)2.2. MDA 模块配置 (8)3. 新增链路配置 (10)3.1. 物理端口配置 (10)3.1.1. Pos 口配置 (10)3.1.2. Ethernet 口配置 (11)3.2. 逻辑接口配置 (12)3.2.1. 配置逻辑接口 (12)3.2.2. 检查接口状态 (12)3.3. 与Cisco 、Huawei 配置的比较 (13)4. 系统管理配置 (15)4.1基本信息配置 (15)4.1.1 配置系统名称 (15)4.1.2 配置系统时间 (15)4.1.3配置登陆信息 (15)4.2 安全配置 (16)4.2.1 启用服务 (16)4.2.2 创建用户 (16)4.2.3配置对上送系统CPU 报文的控制cpm-filter (16)4.3 Log 配置 (17)5. 路由器基本配置 (18)5.1 配置逻辑接口 (18)5.1.1 系统管理地址 (18)5.1.2 网络接口地址 (18)5.2 配置Router ID (18)5.3 配置自治系统号 (19)5.4 过滤器ip-filter 配置 (19)5.4.1 配置ip-filter (19)5.4.2 将ip-filter 应用到逻辑接口 (19)5.5 用ip-filter 来抓包 (20)6. 路由协议配置 (20)6.1 静态路由 (20)6.2 OSPF 协议 (20)6.2.1 基本配置 (20)6.2.2 配置路由再分配 (21)6.3 ISIS 协议 (22)6.3.1 基本配置 (22)6.3.2 配置路由再分配 (23)6.4 BGP 协议 (23)6.5 MPLS 协议 (24)7750SR 路由器日常维护手册第 3 页共 55 页 36.6 LDP 协议 (24)6.7 路由策略配置 (25)7. VPN 配置 (26)8. Qos 配置 (27)8.1 QOS 实现模型 (27)8.2 QoS 配置 (28)8.2.1网络口出队列策略 (28)8.2.2网络口出队列QoS 的应用 (29)8.2.3网络口进队列策略 (29)8.2.4网络口进队列QoS 的应用 (31)8.2.5网络口QoS 策略 (31)8.2.6网络口QoS 策略的应用 (33)8.2.7业务口进队列策略和策略应用 (34)8.2.8业务口出队列策略和策略应用 (39)8.2.9业务限速策略 (44)9.设备日常维护 (45)9.1日常维护步骤 (45)9.2 LED 说明 (45)9.3设备主备用引擎状态和配置的检查 (48)9.4检查设备内存和CPU 的利用率 (49)9.5检查设备的环境参数 (51)9.6检查交换结构的冗余状态 (52)9.7设备的日志检查 (53)9.8链路流量及状态的监测 (54)9.9板卡状态的监测 (55)7750SR-12 7750SR-77750SR-17750SR 路由器日常维护手册第 5 页共 55 页 5本文档针对7750在中国移动IP 承载网中的具体应用，为了使用户尽快熟悉7750设备的配置，能够通过快速的配置达到开通一些常用的业务。

JuniperSR防火墙Web配置手册

J u n i p e r S R防火墙W e b配置手册The latest revision on November 22, 2020Juniper SRX防火墙配置手册1系统配置1.1配置root帐号密码首次登陆设备时，需要采用console方式，登陆用户名为：root，密码为空，登陆到cli下以后，执行如下命令，设置root帐号的密码。

root# set system root-authentication plain-text-passwordroot# new password : root123root# retype new password: root123密码将以密文方式显示。

注意：必须要首先配置root帐号密码，否则后续所有配置的修改都无法提交。

SRX系列低端设备在开机后，系统会加载一个默认配置，设备的第一个接口被划分在trust区域，配置一个ip地址，允许ping、telnet、web等管理方式，可以通过该地址登陆设备。

登陆后显示页面如下：在该页面上，可以看到设备的基本情况，在左边的chassis view中可以看到端口up/down情况，在system identification中可以看到设备序列号、设备名称、软件版本等信息，在resource utilization中可以看到cpu、menory、session、存储空间等信息，在security resources中可以看到当前的会话统计、策略数量统计等信息。

1.2配置用户名和密码平时配置设备时，建议不要使用root帐号，可以建立1个拥有配置权限的用户名，首先点击页面上方的“configure”，进入“system properties-user management”，点击“edit”后，出现用户帐号编辑对话框，点击“add”，添加一个新帐号。

配置方式如下：必须要填的选项包括：user name、password、confirm password、login class，完成后点击“ok”。

(整理)湖北电信IP城域网SR路由器(华为NE40E)配置规范V1.0

湖北电信城域网SR路由器华为NE40E设备配置规范中国电信湖北分公司2011年7月版本更新说明V1.0版本为文档定稿版，后期的版本为修订版，版本的序号为《湖北电信城域网SR路由器华为NE40E-X16设备配置规范-VX.X-YYYYMMDD》，修订说明填写在“主要更新内容”中。

目录第1章概述 (1)1.1 术语和缩写语表 (1)1.2 网络结构说明 (3)第2章IP城域网网络设备命名及链路描述规范 (4)2.1 设备命名规范 (4)2.1.1适用范围 (4)2.1.2设备命名规范格式 (4)2.2 端口描述规范 (5)2.2.1环回接口描述 (5)2.2.2网络接口描述规范 (6)2.2.3用户端口 (7)2.2.4空闲端口 (8)第3章华为SR设备基本配置规范 (9)3.1 系统基本配置规范 (9)3.1.1设备名称配置 (9)3.1.2Banner配置 (9)3.1.3设备自身时间及NTP (9)3.1.4Telnet配置 (11)3.1.5AAA配置 (13)3.1.6VRF配置 (16)3.1.7系统高可靠性配置 (17)3.2 端口配置规范 (18)3.2.1MTU值设计 (18)3.2.2Loopback接口配置 (18)3.2.3GE接口配置 (18)3.2.4GE子接口接口配置 (21)3.2.5端口镜像配置 (22)3.3 路由协议配置规范 (22)3.3.1城域网路由架构概述 (22)3.3.2路由优先级/管理距离 (23)3.3.3静态路由配置 (23)3.3.4ISIS配置 (24)3.3.5BGP配置 (30)3.4 MPLS标签配置规范 (35)3.4.1MPLS全局配置 (35)3.4.2LDP协议配置 (36)3.5 网管配置 (38)3.5.1SNMP管理代理配置 (38)3.5.2故障管理配置 (40)3.6 Q O S配置规范 (43)3.6.1QOS体系 (43)3.6.2采取的QOS策略 (43)3.6.3配置举例 (44)3.7 组播配置规范 (45)3.7.1组播概述 (45)3.7.2组播配置 (45)第1章概述为保证城域网的运行质量，实现易维护、可管理、集中维护的需要，必须在设备能力、网络设计、网络配置、维护流程、支撑系统等环节予以保障。

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不仅仅是强大的互联网路由器，更是一个灵活、强大的业务供应平台。

CR.BRAS.SR配置示例

2.2 功能配置.......................................................................................... 错误！未定义书签。

第三章SR配置模板 (18)3.1 华为ME60配置.............................................................................. 错误！未定义书签。

3.1.1 系统基础配置....................................................................... 错误！未定义书签。

3.1.2 功能配置............................................................................... 错误！未定义书签。

3.2 中兴M6000 ..................................................................................... 错误！未定义书签。

3.2.1 系统基本配置....................................................................... 错误！未定义书签。