湖南广电7750SR-BRAS功能测试手册-xiaohe
7750BRAS维护与配置(SR功能篇)

7750SR/BRAS维护与配置(SR功能篇)1.设备配置命令说明 (4)1.1.S YSTEM基本配置 (4)1.2.L OG配置 (7)1.3.P ORT配置 (9)1.3.1 上行端口和互联PORT端口配置 (9)1.3.2下联端口配置 (10)1.4.IGP协议配置 (14)1.4.1 OSPF协议配置 (14)1.4.2 ISIS协议配置 (17)1.5.M PLS、LDP协议配置 (19)1.6.设备安全配置(SECURITY) (24)1.6.1 设备访问安全 (24)1.6.2 主CPU 保护 (28)1.7.VPN-BGP配置 (35)1.8.P OLICY配置 (38)1.9.业务配置 (40)1.9.1 IES业务配置 (41)1.9.2二层VPN vpls业务配置 (45)1.9.3三层VPN VPRN业务配置 (48)1.10.SNMP配置 (52)1.11.C FLOWD配置 (53)2.业务运行状态检查命令 (55)2.1查看设备P ORT端口运行状态 (55)2.1.1 查看设备所有Port端口运行状态 (55)2.1.2 查看设备单个Port端口运行状态 (57)2.2查看S ERVICE业务运行状态 (60)2.3检查路由器接口运行状态 (62)2.3.1 查看所有接口状态 (62)2.3.1 查看单个业务的接口状态 (64)2.4查看设备MAC地址表信息 (66)2.4.1 查看所有MAC地址表 (66)2.4.2 查看单个业务的MAC地址表 (69)2.5查看设备路由表信息 (70)2.5.1 查看所有路由表地址表 (70)2.5.2 查看某个业务的路由表 (71)3.故障排除方法说明 (73)3.1光路正常但PORT端口DOWN (73)3.2PING 不通对端地址 (73)3.3ISIS邻接关系无法建立 (73)3.4BGP邻居无法正常建立 (73)3.5BGP表中有路由,但路由没有被放进VPN路由表中 (73)3.6VPN中用户CE设备无法访问远端 (74)3.7VPLS故障分析 (74)3.7.1 按照下列配置做mac-filter (74)3.7.2 在VPLS中应用MAC-FILTER (75)3.8.3 通过分析LOG找出问题 (75)4 删除SERVICE配置步骤 (76)4.1删除单个SAP S ERVICE配置步骤 (76)4.2删除多个SAP S ERVICE配置步骤 (76)1.设备配置命令说明1.1. System基本配置1.chassis-mode 要配置为C,以支持新的feature。
7750BRAS业务开局手册

7750BRAS业务开局手册1. PPPOE拓扑通常将7750部署在城域网边缘,上联至城域网汇聚/核心路由器,下联通过二层汇聚网或直挂接入层DSLAM/PON设备,运营商典型的组网图如下;PPPOE业务典型拓扑RADIUSACCOUNTING城域网BAS二层汇聚网DSLAM/PONHGW/MODEMHGW/MODEM2. 详细的工作列表分类准备工作工作项获取radius参数工作列表 authentication server IP地址1authentication server 通讯端口 authertication server 通讯密匙 accounting server IP地址 accounting server 通讯端口 accounting server 通讯密匙 DNS参数DNS服务器地址 subscriber ID sub-profile-string radius返回7750私有属性需求sla-profile-string MSAP-serv-id MSAP-profile-string MSAP-interface DHCP server 需求 DHCP配置 dhcp server地址,一般使用system接口 IP pool地址 IP pool配置将DHCP server绑定到system接口 Authenticaton policy Radius accounting policy Sub-ident-policy 策略配置 Sub-profile Sla-profile PPPOE policy 配置工作 MSAP policy Local-user-db 配置物理接口配置VPLS 接口配置配置IES业务并创建对应interface 绑定IP pool 绑定相关策略接入internet 针对地址池创建黑洞路由创建策略,并export到BGP 21) IP地址池配置IP地址池(ip pool)通常配置在BAS本地,认证通过后BAS从IP地址池中选择一个IP地址分配给终端用户,并且生成一条32位掩码的路由,所以在此之前,在BAS必须将IP地址池所在的网段宣告出去,以便终端用户得到IP地址后能够正常通讯。
7750SR配置方法

7750SR路由器配置规范V2.1上海贝尔阿尔卡特股份有限公司互联网事业部二零零六年十一月目录1.概述 (4)2.系统基本配置 (6)2.1.层次化命令结构 (6)2.2.在CLI中获得帮助 (7)2.3.硬件板卡配置 (8)2.4.设备名称配置 (9)2.5.系统时间配置 (9)2.6.NTP配置 (9)2.7.主备卡切换配置 (10)2.8.AAA配置(登录用户) (11)3.端口配置 (13)3.1.Loopback端口配置 (13)3.2.GE端口配置 (13)3.3.POS端口配置 (14)3.4.端口镜像配置 (15)4.安全配置 (18)4.1.ACL配置 (18)4.2.防攻击配置 (18)5.网管配置 (24)5.1.网管地址配置 (24)5.2.TELNET配置 (24)5.3.FTP配置 (25)5.4.SNMP (25)5.5.SYSLOG (26)5.6.配置备份 (27)5.7.SSH配置 (27)Flow备份 (28)6.路由配置 (29)6.1.黑洞路由配置 (29)6.2.静态路由配置 (29)6.3.OSPF配置 (29)6.4.ISIS配置 (33)6.5.BGP配置 (35)7.业务配置 (40)7.1.专线业务配置(IES配置) (40)7.2.MPLS VPN业务配置 (41)7.2.1P路由器配置 (41)7.2.2PE路由器配置(VPRN) (44)7.2.3PE路由器配置(VPLS) (46)8.7750SR常用维护命令 (49)1.概述阿尔卡特7750SR路由器是业内第一个专为高级互联网和虚拟专用网络(VPN)业务而设计和优化的IP/MPLS业务路由器。
阿尔卡特7750SR有三种尺寸可供选择:单槽、7槽和12槽,可提供具有卓越性能和高密度的各种接口。
作为目前业内最具扩展性的路由器平台,阿尔卡特7750SR具有为高效传送基于服务等级协议(SLA)的业务而设计的软件和硬件架构,因此阿尔卡特7750SR不仅仅是强大的互联网路由器,更是一个灵活、强大的业务供应平台。
7750BRAS pppoe配置脚本

新增端口的pppoe配置:config port 1/1/5端口根据需求更改description "tes" 描述ethernetmode accessno autonegotiateencap-type qinqexitno shutdownexitconfig service ies 3000subscriber-interface "pppoe" 名字根据现网配置为准group-interface "ge-1/1/5" create 端口号根据现场情况变化arp-populatedhcpserver 20.1.1.1指定本接口使用的DHCP servertrusted 保证在dhcp-request中携带gi地址client-applications pppoe 指定使用DHCP用户业务类型 lease-populate 32767 允许分配的用户数no shutdownexitauthentication-policy "auth-pppoe-1" 调用预设置的验证模板 pppoepppoe-policy "pppoe-policy-1" 调用预设置的PPPoE模板 session-limit 32767 session数量限制开到最大 sap-session-limit 32767 session数量限制开到最大 no shutdownexitexitexitexitconfig servicevpls 2011 customer 1 create 为交换机所在接口创建VPLS sap 1/1/5:*.* capture-sap create 接受本端口所有Q-tag,并捕获PPPoE报文 trigger-packet pppoe 配置何种业务触发端口 pppoe-policy "pppoe-policy-1" 调用PPPOE-policy模板 msap-defaultsgroup-interface "ge-1/1/5" 关联到group-interface policy "msap-pppoe" 调用MSAP-policy模板 service 3000 关联到IES号exitauthentication-policy "auth-pppoe-1"exitno shutdownexit注意:蓝色字体必须更换新增地址池配置:config service ies 3000subscriber-interface "pppoe"address10.1.1.1/24 指定新增网段网关exitexitconfig router policy-optionsbeginprefix-list "toospf"prefix 10.1.1.0/24 exact 将新增地址池地址导入OSPF exitcommit 策略生效命令exitconfig router dhcplocal-dhcp-server "pppoe"进入本地DHCP配置,名字根据现网配置为准pool "pppoe_1" create 名字根据现网配置为准subnet 10.1.1.0/24 create 在地址池里添加1个网段 address-range 10.1.1.2 10.1.1.254指定可分配的地址范围 exitexitexit注意:蓝色字体必须更换添加网管命令:config port 1/1/6端口根据需求更改description "tes" 描述ethernetmode accessno autonegotiate 根据现场情况修改encap-type dot1qexitno shutdownexitconfig service ies 5000interface "ge-1/1/6:10" createaddress 172.29.7.254/24 配置网管地址sap 1/1/6:10 createexitexitexitconfig router policy-optionsbeginprefix-list "toospf"prefix 172.29.7.0/24exitcommit 策略生效命令exit基本查看命令:1,检查IP pool 的地址占用情况show router dhcp local-dhcp-server pppoe summary2、测试7750BRAS与radius互通性命令tools perform security authentication-server-check server-address 221.6.4.135 port 1645 user-name 0515******** password 123456 secret jstx显示结果为成功或者超时3、常用show 命令show subscriber-mgmt authentication "auth-pppoe-1"show subscriber-mgmt radius-accounting-policy "acc-pppoe-1"show service active-subscribers summaryshow service active-subscribers detailshow service active-subscribers subscriber "0515********" detailshow service id 3000 pppoe session (后面可选择mac xxx、ip-address xxx、detail)show service id 3000 subscriber-hostsshow service id 3000 pppoe session interface "ge-1/2/5" statistics4、清除pppoe用户session命令clear service id 3000 pppoe session allclear service id 3000 pppoe session interface ge-1/1/5 (后面可选mac xxx、ip-address xxx)clear service id 3000 pppoe session sap 1/1/5:100.50 (后面可选mac xxx、ip-address xxx)。
7750扭矩测试仪显示器说明

扭矩测试仪显示器7750使用说明
显示器7750(图1)设计紧凑,功能多样,适用于在多种场合与扭矩传感器搭配使用。
按键功能:
Off :关机
On :开机
Unit :切换单位(包括N m , ft.lb , in.lb )
Tare :清零
Clear :清除记录的扭矩值
Mode :模式切换(track-跟踪;peak hold-峰值保持;first
peak-第一峰值,适用于手动模式)
连接方式:
显示器7750的底部有安装柄,通过连接座固定在扭矩测试仪
支架上。
左侧第一个孔为电源输入,接电源适配器输
出,左侧其余为数据输入孔,通过数据电缆(图2)
连接扭矩传感器。
使用方法:
按照以上描述连接好所有元件后按 on 键开机,屏幕
首先显示产品编号和软件版本,然后设备自动进入测
量模式。
通过 Mode 和Unit 键选择所需测量模式和单位之后把扭矩扳
手装入扭矩测试仪,旋转扭矩测试仪摇把,至发扭矩扳手到达预设扭矩
发出脱锁响声或发生变形时立即停止旋转,此时屏幕显示值即为扭矩传感器检测到的测量值。
7750 SR OS 基本系统配置指南.pdf_1701713446.1597066说明书

Configuration CommandsFile System CommandsshutdownSyntax[no] shutdown [active] [standby][no] shutdown [cflash-id]Context fileDescription This command shuts down (unmounts) the specified CPM(s).Use the no shutdown [active] [standby] command to enable one or both CPM.Use the no shutdown [cflash-id] command to enable a compact flash (cf1:, cf2:, or cf3:) on the SF/CPMcard. The no shutdown command can be issued for a specific slot when no compact flash is present. Whena flash card is installed in the slot, the card will be activated upon detection.In redundant systems, use the no shutdown command on cf3: on both SF/CPMs in order to facilitate syn-chronization. See the synchronize command on page 408.NOTE: The shutdown command must be issued prior to removing a flash card. If no parameters are speci-fied, then the drive referred to by the current working directory will be shut down.LED Status Indicators — The following states are possible for the compact flash:Operational:If a compact flash is present in a drive and operational (no shutdown), the respective LED is lit green.The LED flickers when the compact flash is accessed.NOTE: Do not remove the compact flash during a read/write operation.State:admin = up, operational = up, equippedFlash defective:If a compact flash is defective, the respective LED blinks amber to reflect the error condition and a trapis raised.State:admin = up/down, operational = faulty, equipped = noFlash drive shut down:When the compact flash drive is shut down and a compact flash present, the LED is lit amber. In thisstate, the compact flash can be ejected.State:admin = down, operational = down, equipped = yesNo compact flash present, drive shut down:If no compact flash is present and the drive is shut down the LED is unlit.State:admin = down, operational = down, equipped = noNo compact flash present, drive enabled:If no compact flash is present and the drive is not shut down the LED is unlit.State:admin = up, operational = down, equipped = noEjecting a compact flash:The compact flash drive should be shut down before ejecting a compact flash card. The LED shouldturn to solid (not blinking) amber. This is the only mode to safely remove the flash card.If a compact flash drive is not shut down before a compact flash is ejected, the LED blinks amber forapproximately 5 seconds before shutting off.State:admin = down, operational = down, equipped = yesThe shutdown or no shutdown state is not saved in the configuration file. Following a reboot all compactflash drives are in their default state.Default no shutdown — compact flash device administratively enabledParameters cflash-id — Enter the compact flash slot ID to be shut down or enabled. When a specific cflash-id is speci-fied, then that drive is shutdown. If no cflash-id is specified, the drive referred to by the current workingdirectory is assumed. If a slot number is not specified, then the active CPM is assumed.Default The current compact flash deviceValues cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:active — If active is selected, then all drives on the active CPM are shutdown or enabled.standby — If standby is selected, then all drives on the standby CPM are shutdown or enabled.Note: When both active and standby keywords are specified, then all drives on both CPM are shut-down.File CommandsattribSyntax attrib [+r | -r]file-urlattribContext fileDescription This command sets or clears/resets the read-only attribute for a file in the local file system. To list all files and their current attributes enter attrib or attrib x where x is either the filename or a wildcard (*).When an attrib command is entered to list a specific file or all files in a directory, the file’s attributes are dis-played with or without an “R” preceding the filename. The “R” implies that the +r is set and that the file isread-only. Files without the “R” designation implies that the -r is set and that the file is read-write-all. Forexample:ALA-1>file cf3:\ # attribcf3:\bootlog.txtcf3:\bof.cfgcf3:\boot.ldrcf3:\sr1.cfgcf3:\testcf3:\bootlog_prev.txtcf3:\BOF.SAVParameters file-url — The URL for the local file.Values local-url | remote-url:255 chars maxlocal-url:[cflash-id/][file-path]remote-url[ftp://login:pswd@remote-locn/][file-path]cf1:,cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:+r — Sets the read-only attribute on the specified file.-r — Clears/resets the read-only attribute on the specified file.cdSyntax cd [file-url]Context fileDescription This command displays or changes the current working directory in the local file system.Parameters file-url — Syntax: [local-url | remote-url (255 chars max)local-url - [cflash-id/][file-path]remote-url - [{ftp://|tftp://}login:pswd@remote-locn/][file-path]cf1,cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:<none> — Displays the current working directory... — Signifies the parent directory. This can be used in place of an actual directory name in a directory-url.directory-url — The destination directory.copySyntax copy source-file-url dest-file-url [force]Context fileDescription This command copies a file or all files in a directory from a source URL to a destination URL. At least one of the specified URLs should be a local URL. The optional wildcard (*) can be used to copy multiple filesthat share a common (partial) prefix and/or (partial) suffix.When a file is copied to a destination with the same file name, the original file is overwritten by the new filespecified in the operation. The following prompt appears if the destination file already exists:“Overwrite destination file (y/n)?”For example:To copy a file named srcfile in a directory called test on cf2 in slot B to a filecalled destfile in a directory called production on cf1 in slot A, the syntax is:sr1>file cf2:\ # copy cf2-B/test/srcfile cf1-A/production/destfileTo FTP a file named 121201.cfg in directory mydir stored on cf1 in slot A to a networkFTP server with IP address 131.12.31.79 in a directory called backup with a destinationfile name of 121201.cfg, the FTP syntax is:copy cf1-A/mydir/121201.cfg 131.12.31.79/backup/121201.cfgParameters source-file-url — The location of the source file or directory to be copied.dest-file-url — The destination of the copied file or directory.force — Forces an immediate copy of the specified file(s).file copy force executes the command without displaying a user prompt message.deleteSyntax delete file-url[force]Context fileDescription This command deletes the specified file.The optional wildcard “*” can be used to delete multiple files that share a common (partial) prefix and/or(partial) suffix. When the wildcard is entered, the following prompt displays for each file that matches thewildcard:“Delete file <filename> (y/n)?”file-url — The file name to delete.Values local-url | remote-url:255 chars maxlocal-url:[cflash-id/][file-path]remote-url[ftp://login:pswd@remote-locn/][file-path]cf1:,cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:force — Forces an immediate deletion of the specified file(s).file delete*force deletes all the wildcard matching files without displaying a user prompt message.dirSyntax dir [file-url] [sort-order { d | n | s}] [reverse]Context fileDescription This command displays a list of files and subdirectories in a directory.Parameters file-url — The path or directory name.Use the file-url with the optional wildcard (*) to reduce the number of files to list.Default Lists all files in the present working directorysort-order { d | n | s — Specifies the sort order.Values d — daten — names — sizereverse — Specifies to reverse the sort order.Sample OutputA:cses-E12>file cf3:\ # dir- dir [<file-url>] [sort-order { d | n | s}] [reverse]<file-url> : <local-url>|<remote-url>local-url - [<cflash-id>/][<file-path>]200 chars max, including cflash-iddirectory length 99 chars max eachremote-url - [ftp://<login>:<pswd>@<remote-locn>/][<file-path>]255 chars maxdirectory length 99 chars max eachremote-locn - [ <hostname> | <ipv4-address> |"["<ipv6-address>"]" ]ipv4-address - a.b.c.dipv6-address - x:x:x:x:x:x:x:x[-interface]x:x:x:x:x:x:d.d.d.d[-interface]x - [0..FFFF]Hd - [0..255]Dinterface - 32 chars max, for linklocal addressescflash-id - cf1:|cf1-A:|cf1-B:|cf2:|cf2-A:|cf2-B:|cf3:|cf3-A:|cf3-B:< d | n | s> : Sort order: d - date, n - name, s - size<reverse> : keyword - reverse orderA:cses-E12>file cf3:\ # dirfileSyntax fileContext rootDescription The context to enter and perform file system operations. When entering the file context, the prompt changes to reflect the present working directory. Navigating the file system with the cd.. command results in achanged prompt.The exit all command leaves the file system/file operation context and returns to the <ROOT> CLI context.The state of the present working directory is maintained for the CLI session. Entering the file commandreturns the cursor to the working directory where the exit command was issued.formatSyntax format cflash cflash-id [reliable]Context root>fileDescription This command formats the compact flash. The compact flash must be shutdown before starting the format. Parameters cflash-id — The compact flash type.cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:reliable — Enables the reliance file system and dis-ables the default DOS file system. This option is valid only on compact flashes 1 and 2.mdSyntax md file-urlContext fileDescription This command creates a new directory in a file system.Directories can only be created one level at a time.Parameters file-url — The directory name to be created.Values local-url | remote-url:255 chars maxlocal-url:[cflash-id/][file-path]remote-url[ftp://login:pswd@remote-locn/][file-path]cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:moveSyntax move old-file-url new-file-url [force]Context fileDescription This command moves a local file, system file, or a directory. If the target already exists, the command fails and an error message displays.The following prompt appears if the destination file already exists:“Overwrite destination file (y/n)?”Parameters old-file-url — The file or directory to be moved.Values local-url | remote-url:255 chars maxlocal-url:[cflash-id/][file-path]remote-url[ftp://login:pswd@remote-locn/][file-path]cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:new-file-url — The new destination to place the old-file-url.Values local-url | remote-url:255 chars maxlocal-url:[cflash-id/][file-path]remote-url[ftp://login:pswd@remote-locn/][file-path]cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:force — Forces an immediate move of the specified file(s).file move force executes the command without displaying a user prompt message.rdSyntax rd file-url rfrd file-url [force]Context fileDescription The rd command is used to delete a directory.If a directory has files and no sub-directories, the force option must be used to force delete the directory andfiles it contains.If a directory has sub-directories, then the force option will fail and the rf parameter should be used insteadto force delete that directory including the sub-directories.Example:A:nE1>file cf1:\ # rd alcateltestAre you sure (y/n)? yDeleting directory cf1:\alcateltest ..MINOR: CLI Cannot delete cf1:\alcateltest.A:nE1>file cf1:\ # rd alcateltest forceDeleting directory cf1:\alcateltest .MINOR: CLI Cannot delete cf1:\alcateltest.A:nE1>file cf1:\ # rd hussein rfDeleting all subdirectories and files in specified directory. y/n ?yDeleting directory cf1:\hussein\hussein1 ..OKDeleting directory cf1:\alcateltest .OKParameters file-url — The directory to be removed.local-url | remote-url:255 chars maxlocal-url:[cflash-id/][file-path]remote-url[ftp://login:pswd@remote-locn/][file-path]cf1:, cf1-A:,cf1-B:,cf2:,cf2-A:,cf2-B:,cf3:,cf3-A:,cf3-B:rf — The parameter forces a recursive delete.force — Forces an immediate deletion of the specified directory.For example, rd file-url force executes the command without displaying a user prompt message.repairSyntax repair [cflash-id]Context fileDescription This command checks a compact flash device for errors and repairs any errors found.Parameters cflash-id — Specify the compact flash slot ID to be shut down or enabled. When a specific cflash-id is spec-ified, then that drive is shutdown. If no cflash-id is specified, the drive referred to by the current work-ing directory is assumed. If a slot number is not specified, then the active SF/CPMCFM is assumed.Default The current compact flash deviceValues cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:scpSyntax scp local-file-url destination-file-url [router router-instance] [force]Context fileDescription This command copies a local file to a remote host file system. It uses ssh for data transfer, and uses the same authentication and provides the same security as ssh. The following prompt appears:“Are you sure (y/n)?” The destination must specify a user and a host.Parameters local-file-url — The local source file or directory.Values[cflash-id/][file-path]: Up to 256 characters.destination-file-url — The destination file.Values user@hostname:destination-fileuser — The SSH user.host — The remote host IP address of DNS name.file-path — The destination path.router-instance — Specify the router name or service ID.Values router-name: Base , managementservice-id: 1 — 2147483647Default Baseforce — Forces an immediate copy of the specified file.file scp local-file-url destination-file-url[router] force executes the command without displaying auser prompt message.typeSyntax type file-urlContext fileDescription Displays the contents of a text file.Parameters file-url — The file contents to display.Values file-url<local-url>|<remote-url>local-url [<cflash-id>/][<file-path>]200 chars max, including cflash-iddirectory length 99 chars max eachremote-url[{ftp://|tftp://}<login>:<pswd>@<remote-locn>/][<file-path>] 255 chars maxdirectory length 99 chars max eachremote-locn [ <hostname> | <ipv4-address> |<ipv6-address> ]ipv4-address a.b.c.dipv6-address x:x:x:x:x:x:x:x[-interface]x:x:x:x:x:x:d.d.d.d[-interface]x - [0..FFFF]Hd - [0..255]Dinterface - 32 chars max, for linklocal addressescflash-id cf1:, cf1-A:, cf1-B:versionSyntax version file-url [check]Context fileDescription This command displays the version of an SR OS *.tim file.Parameters file-url — The file name of the target file.Values local-url | remote-url:255 characters maximumlocal-url:[cflash-id/][file-path]remote-url: [{ftp://|tftp://}login:pswd@remote-locn/][file-path]cflash-id:cf1:, cf1-A:, cf1-B:check — Validates the .tim file.Sample OutputA:Redundancy>filecf3:\#versionftp://test:************.xxx.xx/usr/global/images/6.1/R4/cpm.timTiMOS-C-6.1.R4 for 7750Thu Oct 30 14:21:09 PDT 2008 by builder in /rel6.1/b1/R4/panos/mainA:Redundancy>filecf3:\#versioncheckftp://test:************.xxx.xx/usr/global/images/6.1/R4/cpm.timTiMOS-C-6.1.R4 for 7750Thu Oct 30 14:21:09 PDT 2008 by builder in /rel6.1/b1/R4/panos/mainValidation successfulA:Redundancy>file cf3:\ #viSyntax vi local-urlContext fileDescription Edit files using the vi editor. Refer to VI Editor on page 45.Parameters local-url — Specifies the local source file or directory.Values[cflash-id>/]file-pathcflash-id: cf1:, cf2:, cf3:。
7750BRAS业务PPPOE开局配置手册

未经公司书面授权,任何人不得擅自传播、复制、交流与使用本文档的部分或全部内容。
A l l r i g h t s r e s e r v e d . P a s s i n g o n a n d c o p y i n g o f t h i s d o c u m e n t , u s e a n d c o m m u n i c a t i o n o f i t s c o n t e n t s n o t p e r m i t t e d w i t h o u t a u t h o r i z a t i o n f r o m A l c a t e l S h a n g h a iB e l l .未经公司书面授权,任何人不得擅自传播、复制、交流与使用本文档的部分或全部内容。
A l l r i g h t s r e s e r v e d . P a s s i n g o n a n d c o p y i n g o f t h i s d o c u m e n t , u s e a n d c o m m u n i c a t i o n o f i t s c o n t e n t s n o t p e r m i t t e d w i t h o u t a u t h o r i z a t i o n f r o m A l c a t e l S h a n g h a iB e l l .未经公司书面授权,任何人不得擅自传播、复制、交流与使用本文档的部分或全部内容。
A l l r i g h t s r e s e r v e d . P a s s i n g o n a n d c o p y i n g o f t h i s d o c u m e n t , u s ea n d c o m m u n i c a t i o n o f i t s c o n t e n t s n o t p e r m i t t e d w i t h o u t a u t h o r i z a t i o n f r o m A l c a t e l S h a n g h a i B e l l .未经公司书面授权,任何人不得擅自传播、复制、交流与使用本文档的部分或全部内容。
7750SR-BRAS业务配置手册

7750SR BRAS业务配置手册上海贝尔股份有限公司广东分公司2009-6-4林常键目录PPPOE业务概述 (3)BRAS业务的硬件需求 (3)静态VLAN方式的PPPOE业务流程 (3)静态VLAN方式的PPPOE业务配置流程 (5)动态VLAN方式的PPPOE业务流程 (9)动态VLAN方式的PPPOE业务配置流程 (10)动态VLAN方式的L2TP业务流程 (15)动态VLAN方式的L2TP业务配置流程 (17)静态VLAN方式接入的PPPOE业务debug信息 (21)动态VLAN方式接入的PPPOE业务debug信息 (21)动态VLAN方式接入的L2TP业务debug信息 (21)附录:7750SR Release7.0 Radius 属性 (21)PPPOE业务概述7750SR在6.0版本开始正式支持PPPOE业务,6.1版本添了Radius认证PPPOE用户功能,7.0版本将PPPOE与L2TP业务关联,7750SR可以支持L2TPv2的LAC功能。
PPPOE业务可以在7750SR的IES、VPRN三层业务上实现,用户可以是静态VLAN配置的方式接入,也可以通过msap实现是动态VLAN配置的方式接入。
静态VLAN相对配置而言会更为繁锁,适用于少量VLAN的配置,动态VLAN配置的方式适用于per user per vlan的方式下接入大量PPPOE用户。
对于PPPOE业务可以在Null、Dot1q和 QinQ封装下均支持。
L2TP业务可以在7750SR的PPPOE拔号接入条件下为企业远端用户提供从用户终端到用户路由器的二层VPN隧道业务,其典型组网拓扑如下:BRAS业务的硬件需求7750SR路由器的PPPOE业务将在IOM2-20G和IOM3-XP上支持。
7750SR路由器的L2TP业务将需要有IOM3-XP为作L2TP业务出接口。
静态VLAN方式的PPPOE业务流程1、PPPOE客户端通过PPPOE拔号程序发送PADI报文来发现二层网络内的PPPOE-Server2、二层以太网内的PPPOE-Server收到PADI报文后回应PADO报文。
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。
湖南广电7750SR-BRAS功能测试手册-xiaohe

1测试环境1.1 设备信息1.2 链路信息2测试案例2.1 用户正常拨号测试步骤:1. 用户通过测试机器PPPOE拨号。
2.BAS向RADIUS Server发起认证请求,RADIUS Server响应认证请求报文。
3.BAS向用户授权,并向RADIUS Server 发起计费开始报文。
(1)Local-DCHP配置//配置router Interfacerouterinterface "dhcp"address 220.249.143.206/32loopbacklocal-dhcp-server "server-1"//配置dhcp 地址池routerdhcplocal-dhcp-server "server-1" createuse-gi-addresspool "pool-2" createoptionsdns-server 58.20.127.170exitsubnet 10.240.5.0/24 createaddress-range 10.240.5.10 10.240.5.100exitexitno shutdownexitexitexit(2)Radius配置//配置router Interfaceinterface "to-radius"address 192.168.0.34/30port 1/2/2exit//配置认证模板subscriber-mgmtauthentication-policy "knock-door" createdescription "RADIUS policy"//配置radius server属性,IP及Keyradius-authentication-serversource-address 192.168.0.34server 1 address 172.16.1.2 secret "/ND.T9I/ID3lmtEMVxSCuE" hash2exitexitexit//配置PPPoE报文属性,报文公共及扩展属性user-name-format circuit-idaccept-authorization-changepppoe-access-method pap-chapinclude-radius-attributecircuit-idremote-idnas-port-idnas-identifierpppoe-service-namemac-addressexitexit报文属性可参考数据字典://配置account server属性,IP及Keyradius-accounting-policy "GiveMeMoney"radius-accounting-serversource-address 192.168.0.34server 1 address 172.16.1.2 secret "/ND.T9I/ID3lmtEMVxSCuE" hash2 exitexit//配置account server属性,报文公共及扩展属性radius-accounting-policy "GiveMeMoney" createupdate-interval 10include-radius-attributeframed-ip-addrframed-ip-netmasksubscriber-idcircuit-idremote-idnas-port-idnas-identifiersub-profilesla-profileexitsession-id-format numberuse-std-acct-attributes(3)Subscriber-mgmt用户模板配置//配置sub-profile模板,配合用户QoS属性下发sub-profile "ipd" createingress-scheduler-policy "upstream"exitegress-scheduler-policy "downstream"exitradius-accounting-policy "GiveMeMoney"sla-profile-mapuse-direct-map-as-defaultentry key "default" sla-profile "default"exitexit//配置sla-profile模板,配合sap Qos拥塞管理sla-profile "ipd" createingressqos 10 multipoint-sharedexitexitegressqos 20exitexitexit//配置sub-ident-policy模板,配合用户QoS属性下发sub-ident-policy "sub_ident_all" createsub-profile-mapuse-direct-map-as-defaultexitsla-profile-mapuse-direct-map-as-defaultexitexit(4)QoS模板配置//sub-profile/sla-profile模板,关联的qos模板qos//配置QoS下行预留带宽scheduler-policy "downstream" createtier 1scheduler "downstream" create rate 100000 cir 100000exitexitexit//配置QoS上行预留带宽scheduler-policy "upstream" createtier 1scheduler "upstream" createrate 512 cir 512exitexitexit//配置ingress Qos策略sap-ingress 10 createqueue 1 createparent "upstream"rate 500 cir 500exitqueue 11 multipoint createrate 10 cir 10exitexit//配置egress Qos策略sap-egress 20 createqueue 1 createparent "downstream"exitexitexit(5)PPPoE模板配置//配置IES接口及IPies 100 customer 100 createsubscriber-interface "test" create description "Routed CO"address 10.240.5.1/24//配置group-interface接口group-interface "pppoe-radius" createarp-populate//指定本地DHCP及下发属性dhcpserver 220.249.143.206trustedlease-populate 32767gi-address 10.240.5.1client-applications dhcp pppoeno shutdownexit//指定关联的认证属性authentication-policy "knock-door"//用户下线检测host-connectivity-verify interval 1 action remove//PPPoE client接口配置:VLAN 100sap 1/1/8:100 createsub-sla-mgmt//关联subscriber-mgt属性def-sub-id string "test"def-sub-profile "ipd"def-sla-profile "ipd"sub-ident-policy "sub_ident_all"multi-sub-sap 200no shutdownexitexit//配置pppoe属性pppoesession-limit 32767sap-session-limit 32500no shutdownexitexit2.2 用户正常断线测试步骤:用户通过PPPoE拨号连接成功后,正常断开拨号连接,BAS向RADIUS发起计费结束报文,RADIUS计费并生成上网记录。
7750 SR OS 基本系统配置指南说明书

Boot Option FilesConfiguring Boot File Options with CLIThis section provides information to configure BOF parameters with CLI.Topics in this section include:•Configuring Boot File Options with CLI on page 173•BOF Configuration Overview on page 174•Basic BOF Configuration on page 175•Common Configuration Tasks on page 176•Configuring BOF Parameters on page 181•Service Management Tasks on page 182→Viewing the Current Configuration on page 182→Modifying and Saving a Configuration on page 184→Saving a Configuration to a Different Filename on page 186→Rebooting on page 186BOF Configuration OverviewAlcatel-Lucent 7750 SR-Series routers do not contain a boot EEPROM. The boot loader code isloaded from the boot.ldr file. The BOF file performs the following tasks:1.Sets up the CPM/ Ethernet port (speed, duplex, auto).2.Assigns the IP address for the CPM/Ethernet port.3.Creates static routes for the CPM/ Ethernet port.4.Sets the console port speed.5.Configures the Domain Name System (DNS) name and DNS servers.6.Configures the primary, secondary, tertiary configuration source.7.Configures the primary, secondary, and tertiary image source.8.Configures operational parameters.Boot Option FilesBasic BOF ConfigurationThe parameters which specify location of the image filename that the router will try to boot fromand the configuration file are in the BOF.The most basic BOF configuration should have the following:•Primary addressPrimary image location•Primary configuration locationFollowing is a sample of a basic BOF configuration.A:SR-45# show bof===============================================================================BOF (Memory)===============================================================================primary-image cf3:/4.0.R20primary-config cf3:/ospf_default.cfgaddres 138.120.189.53/24 activestatic-route 138.120.0.0/16 next-hop 138.120.189.1static-route 172.0.0.0/8 next-hop 138.120.189.1autonegotiateduplex fullspeed100wait3persist onconsole-speed 115200===============================================================================A:SR-45#Common Configuration TasksThe following sections are basic system tasks that must be performed.•Searching for the BOF on page 177→Accessing the CLI on page 179−Console Connection on page 179•Configuring BOF Parameters on page 181For details about hardware installation and initial router connections, refer to the specific 7750 SR-Series hardware installation guide.Boot Option FilesSearching for the BOFThe BOF should be on the same drive as the boot loader file. If the system cannot load or cannotfind the BOF then the system checks whether the boot sequence was manually interrupted. Thesystem prompts for a different image and configuration location.The following example displays an example of the output when the boot sequence is interrupted.. . .Hit a key within 3 seconds to change boot parms...You must supply some required Boot Options. At any prompt, you can type:"restart" - restart the query mode."reboot" - reboot."exit" - boot with with existing values.Press ENTER to begin, or 'flash' to enter firmware update...Software Location-----------------You must enter the URL of the TiMOS software.The location can be on a Compact Flash device,or on the network.Here are some examplescf3:/timos1.0R1ftp://user:**************.xx.xxx/./timos1.0R1tftp://192.168.xx.xxx/./timos1.0R1TheexistingImageURLis'ftp://vxworks:***************.xx.xxx/./rel/0.0/xx'Press ENTER to keep it.Software Image URL:Using:'ftp://vxworks:***************.xx.xxx/./rel/0.0/xx'Configuration File Location---------------------------You must enter the location of configurationfile to be used by TiMOS. The file can be ona Compact Flash device, or on the network.Here are some examplescf1:/config.cfgftp://user:**************.xx.xxx/./config.cfgtftp://192.168.xx.xxx/./config.cfgThe existing Config URL is 'cf3:/config.cfg'Press ENTER to keep it, or the word 'none' forno Config URL.Config File URL:Using: 'cf3:/config.cfg'Network Configuration---------------------You specified a network location for either thesoftware or the configuration file. You need toassign an IP address for this system.The IP address should be entered in standard dotted decimal form with a network length. example: 192.168.xx.xxx/24Displays on no n-Redun-dant Models l The existing IP address is 192.168.xx.xxx/20. Press ENTER to keep it. Enter IP Address:Using: 192.168.xx.xxx/20Display on Redundant models The existing Active IP address is 192.168.xx.xxx/20. Press ENTER to keep it. Enter Active IP Address:Using: 192.168.xx.xxx/20The existing Standby IP address is 192.168.xx.xxx/20. Press ENTER to keep it. Enter Standby IP Address (Type 0 ifno ne desired):Using: 192.168.xx.xxx/20Would you like to add a static route? (yes/no) yStatic Routes-------------You specified network locations which requirestatic routes to reach. You will be asked toenter static routes until all the locations becomereachable.Static routes should be entered in the following format:prefix/mask next-hop ip-addressexample: 192.168.xx.xxx/16 next-hop 192.168.xx.xxxEnter route: 1.x.x.0/24 next-hop 192.168.xx.xxxOKWould you like to add another static route? (yes/no) nNew Settings------------primary-imageftp://vxworks:***************.xx.xx/./rel/0.0/xxprimary-config cf3:/config.cfgaddress 192.168.xx.xx/20 activeprimary-dns 192.168.xx.xxdns-domain static-route 1.x.x.0/24 next-hop 192.168.xx.xxxautonegotiateduplex fullspeed 100wait 3persist offDo you want to overwrite cf3:/bof.cfg with the new settings? (yes/no): y Successfully saved the new settings in cf3:/bof.cfgBoot Option FilesAccessing the CLITo access the CLI to configure the software for the first time, follow these steps:•When the SF/CPM is installed and power to the chassis is turned on, the 7750 SR OS7750 SR OS MG software automatically begins the boot sequence.•When the boot loader and BOF image and configuration files are successfully located, establish a router connection (console session).Console ConnectionTo establish a console connection, you will need the following:•An ASCII terminal or a PC running terminal emulation software set to the parameters shown in the table below.• A standard serial cable with a male DB9.Table 19: Console Configuration Parameter ValuesData Bits8Parity NoneStop Bits1Flow Control NoneFigure 10 displays an example of the Console port on a 7750 SR-1 front panel.Console PortSR10001AFigure 10: 7750 SR-1 Front Panel Console PortTo establish a console connection:Step 1Connect the terminal to the Console port on the front panel using the serial cable. Step 2Power on the terminal.Step 3Establish the connection by pressing the <Enter> key a few times on your terminal keyboard.Step 4At the router prompt, enter the login and password.The default login is admin.The default password is admin.Boot Option FilesConfiguring BOF ParametersThe following output displays a BOF configuration:A:ALA-1>bof# show bof==================================================================Memory BOF==================================================================no autonegotiateduplex fullspeed 100address 10.10.xx.xx/20 activewait 3primary-image cf3:\both.timprimary-config cf3:\test123.cfgprimary-dns 192.168.xx.xxpersist ondns-domain ==================================================================A:ALA-1>bof#Service Management TasksThis section discusses the following service management tasks:•System Administration Commands on page 182→Viewing the Current Configuration on page 182→Modifying and Saving a Configuration on page 184→Deleting BOF Parameters on page 185→Saving a Configuration to a Different Filename on page 186System Administration CommandsUse the following administrative commands to perform management tasks.CLI Syntax:A:ALA-1# admindisplay-configreboot [active|standby] [now]save [file-url] [detail] [index]Viewing the Current ConfigurationUse one of the following CLI commands to display the current configuration. The detail optiondisplays all default values. The index option displays only the persistent indices. The infocommand displays context-level information.CLI Syntax:admin# display-config [detail|index]info detailThe following displays an example of a configuration file:A:7750-3>admin# display-config# TiMOS B-1.0.Ixxx - Copyright (c) 2000-2007 Alcatel, Inc.# Built on Tues Jan 21 21:39:07 2007 by builder in /rel1.0/xx/panos/main# Generated WED Jan 31 06:15:29 2007 UTCexit allconfigure#--------------------------------------------------echo "System Configuration"#--------------------------------------------------systemname "7750-3"contact "Fred Information Technology"Boot Option Files location "Bldg.1-floor 2-Room 201"clli-code "abcdefg1234"coordinates "N 45 58 23, W 34 56 12"ccm 1exitsnmpexitlogin-controlidle-timeout 1440motd text "7750-3"exittimesntpshutdownexitzone UTCexitthresholdsrmonexitexitexit......#--------------------------------------------------echo "Redundancy Configuration"#--------------------------------------------------redundancysynchronize boot-envexit...exit all# Finished FRI Nov 21 15:06:16 2008 UTCA:7750#Modifying and Saving a ConfigurationIf you modify a configuration file, the changes remain in effect only during the current powercycle unless a save command is executed. Changes are lost if the system is powered down or therouter is rebooted without saving.•Specify the file URL location to save the running configuration. If a destination is not specified, the files are saved to the location where the files were found for that bootsequence. The same configuration can be saved with different file names to the samelocation or to different locations.•The detail option adds the default parameters to the saved configuration.•The index option forces a save of the index file.•Changing the active and standby addresses without reboot standby CPM may cause aboot-env sync to fail.The following command saves a configuration:CLI Syntax:bof# save [cflash-id]Example:A:ALA-1# bofA:ALA-1>bof# save cf3:A:ALA-1>bof#The following command saves the system configuration:CLI Syntax:admin# save[file-url] [detail][index]Example:A:ALA-1# admin save cf3:\test123.cfgSaving config.# Saved to cf3:\test123.cfg... completeA:ALA-1#NOTE: If the persist option is enabled and the admin save file-url command is executedwith an FTP path used as the file-url parameter, two FTP sessions simultaneously open to theFTP server. The FTP server must be configured to allow multiple sessions from the same login,otherwise, the configuration and index files will not be saved correctly.Boot Option FilesDeleting BOF ParametersYou can delete specific BOF parameters. The no form of these commands removes the parameterfrom configuration. The changes remain in effect only during the current power cycle unless asave command is executed. Changes are lost if the system is powered down or the router isrebooted without saving.Deleting a BOF address entry is not allowed from a Telnet session.Use the following CLI syntax to save and remove BOF configuration parameters:CLI Syntax:bof# save [cflash-id]Example:A:ALA-1# bofA:ALA-1>bof# save cf3:A:ALA-1>bof#CLI Syntax:bof#no address ip-address/mask [active | standby]no autonegotiateno console-speedno dns-domainno li-local-saveno li-separateno primary-configno primary-dnsno primary-imageno secondary-configno secondary-dnsno secondary-imageno static-route ip-address/mask next-hop ip-addressno tertiary-configno tertiary-dnsno tertiary-imageSaving a Configuration to a Different FilenameSave the current configuration with a unique filename to have additional backup copies and to editparameters with a text editor. You can save your current configuration to an ASCII file.Use either of the following CLI syntax to save a configuration to a different location:CLI Syntax:bof# save [cflash-id]Example:A:ALA-1# bofA:ALA-1>bof# save cf3:A:ALA-1>bof#orCLI Syntax:admin# save [file-url] [detail][index]Example:A:ALA-1>admin# save cf3:\testABC.cfgSaving config.# Saved to cf3:\testABC.cfg... completeA:ALA-1#RebootingWhen an admin>reboot command is issued, routers with redundant CPM are rebooted as well asthe IOMs. Changes are lost unless the configuration is saved. Use the admin>save file-url com-mand to save the current configuration. If no command line options are specified, the user isprompted to confirm the reboot operation.Use the following CLI syntax to reboot:CLI Syntax:admin# reboot [active|standby] [now]Example:A:ALA-1>admin# rebootA:DutA>admin# rebootAre you sure you want to reboot (y/n)? yResetting...OKAlcatel 7xxx Boot ROM. Copyright 2000-2007 Alcatel-Lucent.All rights reserved. All use is subject to applicablelicense agreements.....。
7750_BRAS介绍_v1

7750系列宽带接入服务器特点及裨益
T比特可扩展性 高可用性
多业务接入 业务专业化 业务感知型管理
T比特交换容量及业务高扩展性,大幅增加资 产回报率(ROI) 不中断IP/MPLS业务,改进客户满意度
在同一边缘业务接入平台上整合多种业务,从 而降低OPEX(运营成本) 拓展差异化创新业务,进一步挖掘增收潜能
▪ 应用业内领先的节能硬件技术,显著提高节能水平,减 低制冷要求
▪ 使用集成业务适配器(ISA)减少所需网内设备数量,将 运营成本、占地面积、能耗及制冷的需求降至最低
▪ 就地平台升级方案,有助于促进长期的可持续性发展, 显著减少资源浪费和空间使用
▪ 兼具高可用性先进性能,最大限度降低网络冗余需求, 进而达到改善环境效率、降低网络成本的目的
• 5个I/O槽位,含10个 MDA/ISA子槽
• 插槽50 Gb/s传输速率,可升 级至100Gb/s(未来)
• 高可用性及ISSU
• 可扩展的家用、企业及移动多 业务路由
• 90Gb/s 系统容量
• 含6个 MDA/ISA槽位,或2个 MDA+8个CMA槽位
• 插槽10 Gb/s传输速率
• 高可用性及ISSU
All Rights Reserved © Alcatel-Lucent 2009
运营商面临的商业挑战
商业挑战
收入增长 市场竞争力
盈利能力 运营成本减少
资本性支出 客户维系
开辟新业务 监管环境 负债减少 0%
48%
45%
34%
31%
31%
28%
21%
17%
20%
40%
受访者评分介于6-7之间的百分比
11 | 7750 SR Overview
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设备的配置,能够通过快速的配置达到开通一些常用的业务。
7750 BRAS配置指导规范

Abstract ......................................................................................................................... II 2 7750BRAS 和 RADIUS 互通原理 ...........................................................................3
- II -
工程实施文档
目
摘 1
录
要 .......................................................................................................................... I 宽带接入服务器(BRAS)与 RADIUS 综述 .........................................................1 2.1 7750BRAS 和 RADIUS 消息交互过程 .........................................................3 2.2 7750BRAS 和 RADIUS 交互信息说明 .........................................................4
3.1.3 SUB-IDENT-POLICY 策略 .............................................................. 10 3.1.4 SUB-PROFILE 策略 ......................................................................... 11 3.2 7750BRAS 配置 .......................................................................................... 13 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 4 用户服务 SLA-PROFILE 配置 ......................................................... 13 拨号策略 PPPOE-POLICY 配置....................................................... 13 动态 SAP 策略 MSAP-POLICY 配置 ...............................................14 本地用户数据库配置........................................................................ 14 本地 DHCP 地址池配置 ................................................................... 15
7750 SR 路由器操作、管理和诊断指南说明书

PrefaceAbout This GuideThis guide describes service mirroring and Operations, Administration and Management (OAM)and diagnostic tools provided by the router and presents examples to configure and implementvarious tests.This guide is organized into functional chapters and provides concepts and descriptions of theimplementation flow, as well as Command Line Interface (CLI) syntax and command usage.AudienceThis guide is intended for network administrators who are responsible for configuring the 7750 SRrouters. It is assumed that the network administrators have an understanding of networkingprinciples and configurations. Concepts described in this guide include the following:•Service mirroring and Lawful Interception•Operation, Administration and Maintenance (OAM) operationsPrefaceList of Technical PublicationsThe 7750 SR documentation set is composed of the following guides: Table 1: List of Technical PublicationsPreface Table 1: List of Technical PublicationsSearching for InformationYou can use Adobe Reader, Release 6.0 or later, to search one or more PDF files for a term.To search for specific information in this guide1. From the Adobe Reader main menu, choose Edit > Search or Advanced Search. The Searchpanel opens.2. Click on the In the current document radio button.3. Enter the term to search for.4. Select the following search criteria, if required:Preface•Whole words only•Case-Sensitive•Include Bookmarks•Include Comments5. Click on the Search button. Adobe Reader displays the search results.You can expand the entries by clicking on the + symbol.To search for specific information in multiple documentsNote: The PDF files that you search must be in the same folder.1. From the Adobe Reader main menu, choose Edit > Search or Advanced Search. The Searchpanel opens.2. Click on the All PDF Documents in radio button.3. Choose the folder in which to search using the drop-down menu.4. Enter the term to search for.5. Select the following search criteria, if required:•Whole words only•Case-Sensitive•Include Bookmarks•Include Comments6. Click on the Search button. Adobe Reader displays the search results.You can expand the entries for each file by clicking on the + symbol.PrefaceTechnical 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, follow this link to contact anAlcatel-Lucent support representative and to access product manuals and documentation updates:https:///portal/olcsHome.doPreface。
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的时候就得注意。
7750SR现场操作规范手册

江苏7750SR现场操作规范手册作者姓名:张海亮部门、职位:江苏分公司、技术经理产品:IP 7750SR完成日期: 2013年12月创新沟通方式,缔造多彩生活目录1.总体概述 (3)2.常用软件操作 (5)2.1.通过Console线缆连接路由器 (6)2.2.SR系列路由器配置过程 (8)2.3.设备重启 (9)2.4.路由引擎切换 (9)2.5.TiMOS软件升级步骤............................................ 错误!未定义书签。
2.5.1.软件升级相关文件............................................... 错误!未定义书签。
2.5.2.升级步骤............................................................... 错误!未定义书签。
2.6.密码恢复............................................................... 错误!未定义书签。
2.7.在CLI中获取帮助 (12)3.7750SR硬件结构 (14)3.1.7750SR结构 (14)3.1.1.设备描述 (14)3.1.2.硬件结构 (14)3.1.3.组件描述 (22)3.2.硬件更换步骤 (26)3.2.1.SF/CPM模块更换 (26)3.2.2.IOM模块更换 (29)3.2.3.MDA模块更换 (31)3.2.4.空气过滤网拆卸 (32)3.2.5.电源模块更换 (34)4.设备日常维护 (38)4.1.日常维护步骤 (38)4.2.LED说明 (39)4.3.常见硬件状态检查 (44)4.4.常见协议和业务命令 (51)4.5.常见状态检查命令和日志查看 (56)附1:7750板卡PCHIP error说明.............................................. 错误!未定义书签。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
1 测试环境1.1 设备信息上海贝尔7750SR 6.1R6凌亚科技RADIUS Server V1.3 1.2 链路信息2 测试案例2.1 用户正常拨号测试步骤:1. 用户通过测试机器PPPOE拨号。
2.BAS向RADIUS Server发起认证请求,RADIUS Server响应认证请求报文。
3.BAS向用户授权,并向RADIUS Server 发起计费开始报文。
(1)Local-DCHP配置//配置router Interfacerouterinterface "dhcp"address 220.249.143.206/32loopbacklocal-dhcp-server "server-1"//配置dhcp 地址池routerdhcplocal-dhcp-server "server-1" createuse-gi-addresspool "pool-2" createoptionsdns-server 58.20.127.170exitsubnet 10.240.5.0/24 createaddress-range 10.240.5.10 10.240.5.100 exitexitno shutdownexitexitexit(2)Radius配置//配置router Interfaceinterface "to-radius"address 192.168.0.34/30port 1/2/2exit//配置认证模板subscriber-mgmtauthentication-policy "knock-door" createdescription "RADIUS policy"//配置radius server属性,IP及Keyradius-authentication-serversource-address 192.168.0.34server 1 address 172.16.1.2 secret "/ND.T9I/ID3lmtEMVxSCuE" hash2exitexitexit//配置PPPoE报文属性,报文公共及扩展属性user-name-format circuit-idaccept-authorization-changepppoe-access-method pap-chapinclude-radius-attributecircuit-idremote-idnas-port-idnas-identifierpppoe-service-namemac-addressexitexit报文属性可参考数据字典://配置account server属性,IP及Keyradius-accounting-policy "GiveMeMoney"radius-accounting-serversource-address 192.168.0.34server 1 address 172.16.1.2 secret "/ND.T9I/ID3lmtEMVxSCuE" hash2exitexit//配置account server属性,报文公共及扩展属性radius-accounting-policy "GiveMeMoney" createupdate-interval 10include-radius-attributeframed-ip-addrframed-ip-netmasksubscriber-idcircuit-idremote-idnas-port-idnas-identifiersub-profilesla-profileexitsession-id-format numberuse-std-acct-attributes(3)Subscriber-mgmt用户模板配置//配置sub-profile模板,配合用户QoS属性下发sub-profile "ipd" createingress-scheduler-policy "upstream"exitegress-scheduler-policy "downstream"exitradius-accounting-policy "GiveMeMoney"sla-profile-mapuse-direct-map-as-defaultentry key "default" sla-profile "default"exitexit//配置sla-profile模板,配合sap Qos拥塞管理 sla-profile "ipd" createingressqos 10 multipoint-sharedexitexitegressqos 20exitexitexit//配置sub-ident-policy模板,配合用户QoS属性下发sub-ident-policy "sub_ident_all" createsub-profile-mapuse-direct-map-as-defaultexitsla-profile-mapuse-direct-map-as-defaultexitexit(4)QoS模板配置//sub-profile/sla-profile模板,关联的qos模板qos//配置QoS下行预留带宽scheduler-policy "downstream" create tier 1scheduler "downstream" create rate 100000 cir 100000exitexitexit//配置QoS上行预留带宽scheduler-policy "upstream" createtier 1scheduler "upstream" createrate 512 cir 512exitexitexit//配置ingress Qos策略sap-ingress 10 createqueue 1 createparent "upstream"rate 500 cir 500exitqueue 11 multipoint createrate 10 cir 10exitexit//配置egress Qos策略sap-egress 20 createqueue 1 createparent "downstream"exitexitexit(5)PPPoE模板配置//配置IES接口及IPies 100 customer 100 createsubscriber-interface "test" createdescription "Routed CO"address 10.240.5.1/24//配置group-interface接口group-interface "pppoe-radius" create arp-populate//指定本地DHCP及下发属性dhcpserver 220.249.143.206trustedlease-populate 32767gi-address 10.240.5.1client-applications dhcp pppoeno shutdownexit//指定关联的认证属性authentication-policy "knock-door"//用户下线检测host-connectivity-verify interval 1 action remove//PPPoE client接口配置:VLAN 100 sap 1/1/8:100 createsub-sla-mgmt//关联subscriber-mgt属性 def-sub-id string "test"def-sub-profile "ipd"def-sla-profile "ipd"sub-ident-policy"sub_ident_all"multi-sub-sap 200no shutdownexitexit//配置pppoe属性pppoesession-limit 32767sap-session-limit 32500no shutdownexitexit2.2 用户正常断线测试步骤:用户通过PPPoE拨号连接成功后,正常断开拨号连接,BAS向RADIUS发起计费结束报文,RADIUS计费并生成上网记录。
(1)配置Debug//配置debug 观察认证及计费消息show debugdebugserviceid 100pppoepacketmode dropped-onlydetail-level mediumdiscoverypppdhcp-clientexitexitexitexitradius detailexit2.3 用户异常断线流程测试步骤:1. 用户通过测试机器登录后等待10秒后直接断开网线。
2.BAS向RADIUS Server发起计费结束报文。
3.RADIUS Server计费并生成上网记录。
(1)配置pppoe-policy//配置pppoe-policy,设置检测时长pppoe-policy "test" createkeepalive 10 hold-up-multiplier 3exit//在pppoe属性中应用pppoepppoe-policy "test"(2)配置后,异常掉线用户在20内可重新拨号上网。
2.4 会话超时断线流程测试步骤:1. 用户通过测试机器PPPOE拨号成功。
2.180秒后BAS迫使用户下线,并向RADIUS Server发送计费结束报文,RADIUS Server计费并生成上网记录。
(1)由Radius下发属性控制。
radius下发session timeout 属性2.5 计费开始、结束流程测试步骤:1. BAS关闭或手工发起Accounting-Off报文,RADIUS Server收到计费结束报文,下线所有在线用户,并生成上网记录。