赫斯曼交换机配置说明-TTT_00_04_MC-HandsOn
赫斯曼交换机的配置和使用资料

赫斯曼系列交换机配置及使用说明一.M ACH4002系列模块化核心交换机MACH4002 48G-L3P:全千兆模块化工业以太网核心交换机。
设备自带16个千兆端口,其中8个为光、电互换Combo端口。
最多支持4个介质模块,可再扩展出32个千兆端口,最多可达48个千兆端口。
该交换机支持三层路由功能,220V AC冗余供电,0~70℃工作范围。
MACH4002 48+4G-L3P:千兆模块化工业以太网核心交换机。
设备自带4个千兆光、电互换Combo 端口和16个百兆电缆端口。
最多支持4个介质模块,可再扩展出32个百兆端口,最多可达48个百兆端口和4个千兆端口。
该交换机支持三层路由功能,220V AC冗余供电,0~70℃工作范围。
1.设备的安装和拆卸:MACH4002系列核心交换机:该交换机采用标准的19寸机架式安装方式,4个介质模块及设备风扇均支持带电热插拔。
MACH4002 48G-L3P MACH4002 48+4G-L3P 下图为设备正面图示,其中包括有设备的连接端口、风扇、LED显示灯、报警输出节点、RJ11配置端口及USB配置端口。
LED显示灯位于正面左下方,如下图所示:交换机的背面为基本电源模块安装位置,如下图所示:2.设备的配置:设置IP地址的方法:1.通过超级终端的命令行(需要有专用的线缆:串口转V.24);2.通过HiDiscovery 软件,搜索所有的网络设备,设置其IP地址和子网掩码;3.使用BOOTP和DHCP服务器来设置IP地址。
(本方法不推荐在这里使用); 4.使用自动设置适配器ACA21(USB接口)常用的配置方法:1.通过超级终端的命令行(同上);2.通过WEB界面(需要IE5.5以上,并且要装有JA V A 1.3以上),在IE地址栏里输入交换机的IP地址,即可访问设置界面。
每次更改设置需要点击“SET”按键,并选择保存; 3. 使用网管软件HiVision进行配置,每次的修改同样需要进行SET和保存。
赫斯曼交换机配置产品安装配置

P1/P2-电源1/2LED: 绿色-该路电源供电正常 熄灭-该路电源低于18V
R1/R2-信号触点LED: 红色-故障信号触点输出,故障报警 黄色-故障信号触点输出,人工定义 熄灭-故障信号触点关闭
RM-冗余状态LED: 绿色-环网管理生效,环网无断点 黄色-环网管理生效,环网断开 熄灭-环网管理关闭 闪烁-错误的环网配置 RUN-运行/启动LED: 绿色-设备系统就位,正在运行 黄色-设备系统正在启动过程 熄灭-设备系统重启
1 2 3 4 5 6 RM Ring Port Stand-by HIPER-Ring DIP ON Service
20
交换机配置简介
21
IP地址分配
• HiDiscovery软件配置IP属性 – 以太网连接配置PC和交换机 – 开启HiDiscovery软件 – 自动安装WinPcap3.0 – 软件自动扫描后于主页面添加扫描到的交换机 – 使用Singal按键定位交换机 • 按下Singal按键后,主页面高亮交换机LED会反复交替闪烁
拧紧固定螺丝,固定扩展底板。
7
MS交换机电源接线
正极连接1接线柱 负极连接2接线柱。 单路电源供电时,交换机RL指示灯亮,有报警 输出,必要时用软件关闭交换机电源报警或短 接两路电源正极。 缺省时如下情况3、4接线柱输出故障信息 至少一路电压低于18V 内部电压问题造成的故障 至少一个端口连接状态异常 环网断开与恢复 Coupling控制线短接,Coupling功能启动 1 - MS20/30 交换机基本模块,支持18 ~ 60 VDC 供电 2 – 电源/信号触点 1: Pin 1 =+24 V (P1), Pin 2 =0 V, Pin 3, 4 =Relay 1 3 – 电源/信号触点 2: Pin 1 =+24 V (P2), Pin 2 =0 V, Pin 3, 4 =Relay 2 4 - MS20/30 交换机基本模块,支持18 ~ 32 VDC 供电 5 - 电源/信号触点 1: Pin 1 =+24 V (P1), Pin 2 =0 V, Pin 3, 4 =Relay 1 6 - 电源/信号触点 2: Pin 1 =+24 V (P2), Pin 2 =0 V, Pin 3, 4 =Relay 2
赫斯曼交换机的配置和使用(同名12603)

赫斯曼系列交换机配置及使用说明一.M ACH4002系列模块化核心交换机MACH4002 48G-L3P:全千兆模块化工业以太网核心交换机。
设备自带16个千兆端口,其中8个为光、电互换Combo端口。
最多支持4个介质模块,可再扩展出32个千兆端口,最多可达48个千兆端口。
该交换机支持三层路由功能,220V AC冗余供电,0~70℃工作范围。
MACH4002 48+4G-L3P:千兆模块化工业以太网核心交换机。
设备自带4个千兆光、电互换Combo 端口和16个百兆电缆端口。
最多支持4个介质模块,可再扩展出32个百兆端口,最多可达48个百兆端口和4个千兆端口。
该交换机支持三层路由功能,220V AC冗余供电,0~70℃工作范围。
1.设备的安装和拆卸:MACH4002系列核心交换机:该交换机采用标准的19寸机架式安装方式,4个介质模块及设备风扇均支持带电热插拔。
MACH4002 48G-L3P MACH4002 48+4G-L3P 下图为设备正面图示,其中包括有设备的连接端口、风扇、LED显示灯、报警输出节点、RJ11配置端口及USB配置端口。
LED显示灯位于正面左下方,如下图所示:交换机的背面为基本电源模块安装位置,如下图所示:2.设备的配置:设置IP地址的方法:1.通过超级终端的命令行(需要有专用的线缆:串口转V.24);2.通过HiDiscovery 软件,搜索所有的网络设备,设置其IP地址和子网掩码;3.使用BOOTP和DHCP服务器来设置IP地址。
(本方法不推荐在这里使用); 4.使用自动设置适配器ACA21(USB接口)常用的配置方法:1.通过超级终端的命令行(同上);2.通过WEB界面(需要IE5.5以上,并且要装有JA V A 1.3以上),在IE地址栏里输入交换机的IP地址,即可访问设置界面。
每次更改设置需要点击“SET”按键,并选择保存; 3. 使用网管软件HiVision进行配置,每次的修改同样需要进行SET和保存。
赫斯曼交换机同一IP段不同网口设置说明

试用范围:一段IP地址分配给不同的网柜 样例:手动线会将一个IP段分配给不同的NK中,有两种解决方案: 1、新增一个IP段,保证赫斯曼交换机按照正常标准设计; 2、需要将一段IP划分成不同的段重新设置定义网关。重新定义的 段只能是16的倍数。
例如:172.30.179.34~64这段地址,对应网柜端口3.3,网关为 172.30.179.33.子网掩码为255.255.255.224。 说明:子网掩码224定义为224~255有32位有效,从网关的33开始增加32 位有效,有效值到64。以此类推。
按照如上思路对侧围内板进行IP分配:
侧围内板右侧线接入交换机3.1口,IP地址范围定义为172.30.36.(33-64); 侧围内板右侧线接入交换机3.3口,IP地址范围定义为172.30.36.(2-31); 说明:侧围内板左右各13个设备,因此这里左右每侧各设计32的地址的预留量, 侧围外板接入交换机3.2口, IP地址范围定义为172.30.37.(2-254)。 (注明:IP地址中的第一位和最后一位为无效位,严禁分配地址) 设置方法如下页:
设置交换机的地址为172.30.44.40
通过VLAN设置3个虚拟网络地址命名为100,102,103
通过VLAN100,102,103分别于实际接线的3.2,3.1,3.3对应上。
Routing Global 中的Opertion中选项选为“on”
VLAN100对应的为3.2口,所以3.2口按正 常方式设置网管和子网掩码即可; VLAN102对应的为3.1口,3.1口设置 网管为172.30.36.33,如上图; VLAN103对应的为3.3口, 3.1口设置 网管为172.30.36.1。如果将网络分为 32位,那么其子网掩码的D为应设置 为224(255-32+1),如果不需要分 配,则子网掩码的D位设置为0(255256+1)。同时给VLAN100,102, 103设置一个虚拟网关地址(任意即 可),但不能与车间的任何一个设备 重复,子网掩码=配置网络口子网掩 码。
赫斯曼交换机配置说明-TTT_00_04_MC-HandsOn

Notes: Content❑Hands-on L2 multicasting❑Hands-on L3 multicasting (routing)Tasks:T k❑Build up a tree structure without and with IGMP and check the behavior❑Build up a HIPER Ring structure without and with IGMP …❑Build up a routed network with DVMRP and check the behavior❑Build up a routed network with PIM-DM and check the behavior❑Build up a HIPER Ring with routed networks …B ild HIPER Ri ith t d t k© Hirschmann Automation and Control GmbHThis presentation, and the material here in, have been prepared for the purposes of education and training. These slides are the sole property of Hirschmann and of education and training These slides are the sole property of Hirschmann and its subsidiaries, and are not to be altered, duplicated or distributed in any way without express written permission by Hirschmann.❑Microsoft Windows 95 and NT 4.0 support IGMPv1.Notes:❑Microsoft Windows 98 and 2000 support IGMPv2.❑Microsoft Windows XP supports IGMPv3. But there are stilla lot other devices in a network with v2 only. Thus IGMPv2should be configured on devices (default of Hirschmanng(platform). A XP host receiving a v2 packet automaticallychanges to v2 till a timer expires.❑The IGMP snooping release can be configured globally only, thus it is identical in all VLANs.❑On HIPER Ring ports “Forwarding All” should be configured.In HIPER Ring one querier is enough❑In HIPER Ring one querier is enough.❑Querier selection is available as of IGMPv2. Pleaseremember the flooding problem mentioned in the appendixof last presentation.Local workaround is to configure static query ports indirection of the MC source segment.❑Querier interval by default = 125 s. Minimum accepted in Querier interval by default=125s Minimum accepted in3.0.03 = 2 s (depending on max response time)(Config)# set igmp querier tx-interval <seconds>Notes:Commands:❑> enable❑# show igmpsnooping❑# show running-config [all]#fiactivates IGMPsnooping ❑# config ❑(Config)# set igmp❑(Config)# set igmp querier tx-interval <seconds>❑Max response time must be less than querier interval. Default: 10 s(Config)# set igmp querier max-response-time <sec>activates IGMPsnooping(g)g p q p ❑Note:a Windows XP notebook connected to v1 and v2 queriers changed from v3 to v1 after 83 minutes.After changing querier version to v2 the XP client changed from v1to v2after 4:35minutes from v1 to v2 after 4:35 minutes.The next change from v2 to v1 happened after a couple of seconds.Notes:1.Build up a tree structure and produce a MC streama)no IGMP: check behavior if producer is located in sameand in different branch of consumerb)IGMPv1: check behavior if producer is located in sameand in different branch of consumerand in different branch of consumerc)IGMPv2: check behavior if producer is located in sameand in different branch of consumerd)IGMPv3: check behavior if producer is located in sameand in different branch of consumer2.Build up a HIPER Ring structure …a)no IGMP: check behavior if producer is located in sameand in different branch of consumerb)IGMPv1: check behavior if producer is located in sameand in different branch of consumerc)IGMPv2: check behavior if producer is located in sameand in different branch of consumerd)IGMPv3: check behavior if producer is located in sameand in different branch of consumer❑Due to its fast recovery time HIPER Ring is widely used asNotes: link redundancy solution on layer 2 combined with routedVLANs (VRRP for UCs).❑Thus regard special rules for MC routing over HIPER Ring.,❑There should be no distributed VLANs, thus broadcasts need not be propagated over the backbone. The backboneis a separate VLAN with separate subnet. This backboneVLAN is routed (VLAN routing) to the other subnetsconnected redundantly to router ports with VRRP.❑In the displayed application the use of DVMRP as MCIn the displayed application the use of DVMRP as MCrouting protocol is better than PIM-DM, because it uses itsown routing protocol and thus can detect …❑Please note: an IGMP enabled Hirschmann switch new connected first sends out querier packets to get allregistrations thus the next querier interval needs not toregistrations thus the next querier interval needs not toexpire.❑If a router port receives an IGMP packet with lower versionNotes: than globally configured then this port changes to that lowerrelease.❑IGMP snooping release should be configured same as IGMP release!Please note: by default both are v2. IGMP snooping releasecan be configured by web, IGMP release by CLI only (perinterface).❑Because IGMP snooping can be configured globally only IGMP snooping release is identical in all VLANs.CLI commands:❑> enable❑# show igmpsnooping❑# show ip igmp interface <slot/port>Example of configuration:Notes:❑(R1)> enable❑(R1)# configure❑(R1) (Configure)# ip igmp❑(R1) (Configure)# interface 1/1❑(R1) (Interface 1/1)# ip igmp(R1)(Interface1/1)#ip igmp❑(R1) (Interface 1/1)# ip igmp version <1|2|3>❑(R1) (Interface 1/1)# exit❑(R1)# show ip igmpOptional:No.of Group Specific Queries sent(2default):❑No. of Group Specific Queries sent (2 default):(R1) (Interface 1/1)# ip igmp last-member-query-count <1…20>❑Group Specific Query interval ( default):❑Query interval (125 s default):(R1) (Interface 1/1)# ip igmp query-interval <1…3600>❑Query max response time (100 1/10 s):(R1) (Interface 1/1)# ip igmp query-max-response-time <0…255>❑IGMP robustness (2 default):(R1) (Interface 1/1)# ip igmp robustness <0…255>(R1)(I t f1/1)#i i b t0255❑IGMP startup query count (2 default)(R1) (Interface 1/1)# ip igmp startup-query-count <1…20>❑IGMP startup query interval (1 s default):(R1) (Interface 1/1)# ip igmp startup-query-interval <1…300>❑IGMP snooping and thus the snooping querier is a globalNotes: function of a device.❑If the snoop-querier (IGMPv2 or v3) on a switch between two routers is active and the routers have a higher IPaddress than the switch, the switch will win the querierelection and thus the snoop queriers of the connectedrouters are disabled. As a result other switched ports at therouters will loose their querier, if there is no other availableand thus multicasting doesn’t work anymore.❑GMRP cannot be used simultaneously to IGMP, thus itNotes: cannot be used together with dynamic multicast routing.CLI commands:❑(Config) # set gmrp adminmode or # no set…(Config)#set gmrp adminmode or#no set❑(Config) # set gmrp interfacemode❑(Config) # set gmrp forward-all-groups❑(Interface x/y) #set gmrp interfacemode❑(Interface x/y) #set gmrp forward-all-groups❑> show gmrp configuration all>show gmrp configuration all❑> show gmrp configuration <slot/port>Notes: Multicast routing protocols are available in L3P firmwarepackage only!Which MC routing protocol should be selected?❑DVMRP uses its own routing protocol while PIM-DM uses DVMRP uses its own routing protocol while PIM DM usesthe UC protocol in operation. DVMRP knows better thetopology with advantage in routed switched networksespecially together with HIPER Ring, static routes withECMP.❑The opt-out protocols DVMRP and PIM-DM start flooding, asa result devices receive faster the streams.a result devices receive faster the streams.❑As opt-out solutions after expiration of the hold timer MCs are flooded again thus producing high load condition tillprunes are sent again.Holdtime DVMRP 2 h, fixedHoldtime PIM-DM 210 s, configurable till 18 h.❑Convergence after topology changes is faster at PIM DM.Convergence after topology changes is faster at PIM-DM.❑PIM offers configurable timers and thus a higher flexibility if necessary.❑DVMRP is limited to 32 hops.❑Enable unicast routing:Notes: (R1) (Configure)# ip routing❑Enable multicast routing(R1) (Configure)# ip multicast❑Note: if first “ip multicast” is entered with IGMP disabled and error message is displayed, but after “ip igmp” command theconfiguration is o.k.❑To route MCs over one single PIM-DM router there is no need for unicast routing but for routing MCs over cascadedneed for unicast routing, but for routing MCs over cascadedrouters a UC routing protocol is needed (usually OSPF).Notes: Example of configuration:❑(R1)> enable❑(R1)# configure❑(R1) (Configure)# ip igmp(R1)(C fi)#i i❑(R1) (Configure)# ip multicast❑(R1) (Configure)# ip dvmrp❑(R1) (Configure)# interface 1/1❑(R1) (Interface 1/1)# ip igmp❑(R1) (Interface 1/1)# ip dvmrp(R1)(Interface1/1)#ip dvmrp❑(R1) (Interface 1/1)# exit❑(R1) (Configure)# exit❑(R1)# show ip dvmrpNote:For training purposes it’s sufficient to disableDVMRP globally while it’s still enabled on theinterfaces andthen configure PIM-DM (see next slide).Example of configuration:Notes:❑(R1)> enable❑(R1)# configure❑(R1) (Configure)# ip igmp()(g)p❑(R1) (Configure)# ip multicast❑(R1) (Configure)# ip pimdm❑(R1) (Configure)# interface 1/1❑(R1) (Interface 1/1)# ip igmp❑(R1) (Interface 1/1)# ip pimdm mode❑(R1) (Interface 1/1)# exit❑(R1) (Configure)# exit(R1)(C fi)#i❑(R1)# show ip pimdm❑(R1)# show ip mcast❑(R1)# show ip igmpOptional:❑Configuration of holdtime in seconds (210 s default):(R1) (Configure)# ip pimdm holdtimes <30…64800>❑Configuration of hello time in seconds:(Interface s/p)# ip pimdm hello-interval <1…3600>Notes:Consecutive order of minimum configuration:❑Configure and enable router interfaces ❑Set prompt for a better orientation ❑Enable routingCLI command sequence:(replace x by router number)> enable# set prompt R x # configure(Config)# ip routing (Config)#show ip brief ❑Configure UC routing protocol globally❑Enable IGMP globally (automatically enables MC routing and IGMP snooping)❑Enable multicast forwarding (routing)Enable PIM SM globally (Config)# show ip brief (Config)# router ospf(Config-router)# router-id x .1.1.1(Config-router)# enable(Config-router)# redistribute connected [subnets](Config-router)# exit (Config)# ip igmp (Config)# ip multicast (Config)#ip pimsm ❑Enable PIM-SM globally ❑Set static Rendezvous Point ❑Configure routing interfaces❑Configure UC routing protocol per interface ❑Enable IGMP per interface, and set version Optionally change version (default =2)(Config)# ip pimsm(Config)# ip pimsm rp-address <ip-@> <MC @>…(Config)# interface <s/p>(Interface s/p)# ip address <ip-@> <mask>(Interface s/p)# routing(Interface s/p)# ip ospf area-id 0.0.0.0(Interface s/p)# ip ospf (Interface s/p)# ip igmp(Interface s/p)#ip igmp version <1|❑Optionally change version (default = 2)❑Enable PIM-SM on respective interfaces(Interface s/p)# ip igmp version <1|2|3>(Interface s/p)# ip pimsm mode (Interface s/p)# exit (Config)# exit # show ip pimsm# copy system:running-config nvram:startup-config # logoutThe IGMP version by default is 2.Notes: Please note that a Rendezvous Point must be configured on all PIM-SM enabled routers, even at the RP itself.The alternative is to define at least one Bootstrap router(BSR) and at least one RP candidate. At a customer site it’sgrecommended to configure 2 candidate RPs and 2 candidate BSRs for redundancy.Further commands:❑(Interface s/p)# show❑# show ip pimsm❑# show ip mcast#show ip mcast❑# show ip igmpOptional:❑Configuration of DR priority:(Interface s/p)# ip pimsm dr-priority <0…2,147,483,647>Configuration of hello interval in seconds(30s default):❑Configuration of hello interval in seconds (30 s default): (Interface s/p)# ip pimsm hello-interval <0…18000>❑Pre-requisite of PIM-SM is a correctly running UC routingNotes: protocol like OSPF.❑MC routing between 2 IFs on one router works if on this router an RP is defined. But the RP needs not to beconfigured itself.❑MC routing between 2 IFs on two routers only works if RP is defined on both routers and on the RP itself.❑For MC routing protocols at neighbor expiry only a trap is defined. For IGMP there is no trap implemented.❑Instead of statically define RPs, now BSR and RPNotes: candidates are configured from which a BSR and RP areelected.❑CLI commands:❑(Config)# ip pimsm bsr-candidate interface <slot/port>❑(Config)# ip pimsm rp-candidate interface <slot/port>Notes:1.Build up a routed network with DVMRPa)check behavior if producer is located in same and indifferent branch of consumer2.Build up a routed network with PIM-DM and check the2Build up a routed network with PIM DM and check thebehaviora)check behavior if producer is located in same and indifferent branch of consumer3.Build up a HIPER Ring with routed networks …a)check behavior if producer is located in same and indifferent branch of consumerAll MC packets with a TTL value less than the definedNotes: threshold were discarded at the specific interface.。
赫思曼交换机网络管理指南-最新

赫思曼交换机网络管理指南1、交换机初始IP设置一般刚出厂的交换机或者恢复到出厂设置的交换机的IP地址是空白的,必须通过以下方式来设置。
¾首先安装HiDiscovery软件。
打开随机配备光盘在根目录下找到HiDiscovery目录。
¾运行HiDiscovery目录下的HiDiscoverySetup.exe安装文件。
安装完成之后桌面出现图标。
¾利用HiDiscovery软件为交换机分配IP地址,双击HiDiscovery桌面图标进入其操作界面。
在1框处选择合适的网络适配器,然后在2框处点击“重新扫描”来搜索交换机。
赫思曼交换机在出厂的默认配置中,交换机的默认IP地址为0.0.0.0,其子网掩码也为0.0.0.0。
如果要对交换机进行配置,必须先为每台交换机分配一个不同的管理IP地址双击其中的一台设备,可以在弹出的窗口中为其分配IP地址、子网掩码和默认网关等参数。
注:左键选中一台设备后,再点击Signal按钮后,该交换机的所有LED灯会开始闪烁,可使用此方法用于区别每台设备。
如果错误的将两台交换机设置为相同的IP地址,HiDiscovery 软件会提示有冲突的地址。
2、交换机Web配置管理2.1 Web配置界面运行环境。
交换机的Web配置管理界面需在JAVA环境下运行,因此必须先给配置电脑安装JAVA运行环境。
安装JAVA运行环境,在随机配置的光盘根目录下找到Java文件夹,打开该文件夹。
运行安装文件jre‐6u20‐windows‐i586.exe。
安装成功后检查计算机内是否有其他版本的JAVA 软件,如果有的话考虑卸载了,该JAVA软件安装后无需升级。
2.2 登陆交换机Web配置界面安装完JAVA运行环境,就可以登陆交换机的Web配置界面,登陆时只需要在IE浏览器的地址中输入目的交换机的IP地址并进行连接,或通过HiDiscovery软件的“WWW”按钮直接跳转到交换机的Web界面。
赫思曼交换机操作说明-网络部蔡翔

19
路由设置
7.配置完成后 保存路由配 置,在 routing>global中 routing打上勾 点击set就可以 使路由的设置 生效
20
Industrial HiVision界面配置
1.打开程序
21
Industrial HiVision界面配置
1.打开程序 2.连接设备
22
Industrial HiVision界面配置
17
路由设置
1.routing-> interface-> Configuration 界面中点击 Wizard 2.进入基于 VLAN路由向导 3.选定VLAN1, 这里一定要注 意,进行VLAN 路由设置时一 定要将vlan1先 配置相应的路 由接口
18
路由设置
4.确认所对应 的vlan端口 5.输入对应的 路由接口IP地 址,可以输入 更多的IP地址 -通过second address来进行 添加 6.添加完路由 接口后的端 口,及附加端 口
33
基本操作流程
3. 划分VLAN ,设置核心交换机路由
34
基本操作流程
4.安装HiVision系列软件,并调试运行。
35
特色
Built-in misconfiguration insurance
36
特色
–LEDs –Web or management systems –relay contact –SFP diagnostic (temperature, optical power) –RMON statistics, history, alarms, events –Port mirroring –Logfile
9
赫斯曼交换机网络配置

资料范本本资料为word版本,可以直接编辑和打印,感谢您的下载赫斯曼交换机网络配置地点:__________________时间:__________________说明:本资料适用于约定双方经过谈判,协商而共同承认,共同遵守的责任与义务,仅供参考,文档可直接下载或修改,不需要的部分可直接删除,使用时请详细阅读内容赫斯曼交换机网络配置本网络系统包含一台万兆以太网交换机(MACH 4002)作为核心交换机,两台模块化交换机(MS4128)作为次级交换机。
网络系统要求划分为两个VLAN,两个VLAN之间需要通讯。
1、 Vlan配置核心交换机(MACH 4002)的管理地址分别为172.16.8.251。
两台次级交换机(MS 4128)的管理地址分别为172.16.8.252,172.16.8.253。
第一步:连接好所有设备,不考虑Port口位置。
第二步:VLAN规划本网络划分了两个VLAN,第一个名称为VLAN1,第二个名称为VLAN2,还有一个默认VLAN,名称为Defult。
Port口详细划分如下:MACH4002:VLAN1 Port口:4.1~4.6, 6.3~6.14VLAN2 Port口:3.1~3.8上联Port口:4.7,4.8,6.15,6.16管理Port口:6.1,6.2MS4128:(两台配置一样)VLAN1 Port口:2.3~1.4,3.1~3.4,4.1~4.4,5.1~5.4VLAN2 Port口:无上联Port口:1.1,1.2,2.1,2.2第三步:划分VLAN使用HiDiscovery扫描到网络内所有的交换机设备,对交换机的管理地址进行设置。
使用HiVision,在Configration-Preference中添加交换机管理地址的扫描网段,可以扫描到网络内的所有交换机如图:单击Vlan-Manager选项卡,选择Agent list,如图:选择Discovered devices中的所有设备并单击添加按钮将它们添加到Participating agents 中,并点击OK按钮,如图:选择“Edit”下拉菜单中的“Groups”,空白处右击选择“New”,在“Name”中输Vlan名称“Vlan1”,单击“Members”选项卡,选中需要添加的Port口,点击OK,如图:按照相同的步骤,创建第二个VLAN,名称为VLAN2,添加相应的Port口,点击OK。
- 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。
Notes: Content❑Hands-on L2 multicasting❑Hands-on L3 multicasting (routing)Tasks:T k❑Build up a tree structure without and with IGMP and check the behavior❑Build up a HIPER Ring structure without and with IGMP …❑Build up a routed network with DVMRP and check the behavior❑Build up a routed network with PIM-DM and check the behavior❑Build up a HIPER Ring with routed networks …B ild HIPER Ri ith t d t k© Hirschmann Automation and Control GmbHThis presentation, and the material here in, have been prepared for the purposes of education and training. These slides are the sole property of Hirschmann and of education and training These slides are the sole property of Hirschmann and its subsidiaries, and are not to be altered, duplicated or distributed in any way without express written permission by Hirschmann.❑Microsoft Windows 95 and NT 4.0 support IGMPv1.Notes:❑Microsoft Windows 98 and 2000 support IGMPv2.❑Microsoft Windows XP supports IGMPv3. But there are stilla lot other devices in a network with v2 only. Thus IGMPv2should be configured on devices (default of Hirschmanng(platform). A XP host receiving a v2 packet automaticallychanges to v2 till a timer expires.❑The IGMP snooping release can be configured globally only, thus it is identical in all VLANs.❑On HIPER Ring ports “Forwarding All” should be configured.In HIPER Ring one querier is enough❑In HIPER Ring one querier is enough.❑Querier selection is available as of IGMPv2. Pleaseremember the flooding problem mentioned in the appendixof last presentation.Local workaround is to configure static query ports indirection of the MC source segment.❑Querier interval by default = 125 s. Minimum accepted in Querier interval by default=125s Minimum accepted in3.0.03 = 2 s (depending on max response time)(Config)# set igmp querier tx-interval <seconds>Notes:Commands:❑> enable❑# show igmpsnooping❑# show running-config [all]#fiactivates IGMPsnooping ❑# config ❑(Config)# set igmp❑(Config)# set igmp querier tx-interval <seconds>❑Max response time must be less than querier interval. Default: 10 s(Config)# set igmp querier max-response-time <sec>activates IGMPsnooping(g)g p q p ❑Note:a Windows XP notebook connected to v1 and v2 queriers changed from v3 to v1 after 83 minutes.After changing querier version to v2 the XP client changed from v1to v2after 4:35minutes from v1 to v2 after 4:35 minutes.The next change from v2 to v1 happened after a couple of seconds.Notes:1.Build up a tree structure and produce a MC streama)no IGMP: check behavior if producer is located in sameand in different branch of consumerb)IGMPv1: check behavior if producer is located in sameand in different branch of consumerand in different branch of consumerc)IGMPv2: check behavior if producer is located in sameand in different branch of consumerd)IGMPv3: check behavior if producer is located in sameand in different branch of consumer2.Build up a HIPER Ring structure …a)no IGMP: check behavior if producer is located in sameand in different branch of consumerb)IGMPv1: check behavior if producer is located in sameand in different branch of consumerc)IGMPv2: check behavior if producer is located in sameand in different branch of consumerd)IGMPv3: check behavior if producer is located in sameand in different branch of consumer❑Due to its fast recovery time HIPER Ring is widely used asNotes: link redundancy solution on layer 2 combined with routedVLANs (VRRP for UCs).❑Thus regard special rules for MC routing over HIPER Ring.,❑There should be no distributed VLANs, thus broadcasts need not be propagated over the backbone. The backboneis a separate VLAN with separate subnet. This backboneVLAN is routed (VLAN routing) to the other subnetsconnected redundantly to router ports with VRRP.❑In the displayed application the use of DVMRP as MCIn the displayed application the use of DVMRP as MCrouting protocol is better than PIM-DM, because it uses itsown routing protocol and thus can detect …❑Please note: an IGMP enabled Hirschmann switch new connected first sends out querier packets to get allregistrations thus the next querier interval needs not toregistrations thus the next querier interval needs not toexpire.❑If a router port receives an IGMP packet with lower versionNotes: than globally configured then this port changes to that lowerrelease.❑IGMP snooping release should be configured same as IGMP release!Please note: by default both are v2. IGMP snooping releasecan be configured by web, IGMP release by CLI only (perinterface).❑Because IGMP snooping can be configured globally only IGMP snooping release is identical in all VLANs.CLI commands:❑> enable❑# show igmpsnooping❑# show ip igmp interface <slot/port>Example of configuration:Notes:❑(R1)> enable❑(R1)# configure❑(R1) (Configure)# ip igmp❑(R1) (Configure)# interface 1/1❑(R1) (Interface 1/1)# ip igmp(R1)(Interface1/1)#ip igmp❑(R1) (Interface 1/1)# ip igmp version <1|2|3>❑(R1) (Interface 1/1)# exit❑(R1)# show ip igmpOptional:No.of Group Specific Queries sent(2default):❑No. of Group Specific Queries sent (2 default):(R1) (Interface 1/1)# ip igmp last-member-query-count <1…20>❑Group Specific Query interval ( default):❑Query interval (125 s default):(R1) (Interface 1/1)# ip igmp query-interval <1…3600>❑Query max response time (100 1/10 s):(R1) (Interface 1/1)# ip igmp query-max-response-time <0…255>❑IGMP robustness (2 default):(R1) (Interface 1/1)# ip igmp robustness <0…255>(R1)(I t f1/1)#i i b t0255❑IGMP startup query count (2 default)(R1) (Interface 1/1)# ip igmp startup-query-count <1…20>❑IGMP startup query interval (1 s default):(R1) (Interface 1/1)# ip igmp startup-query-interval <1…300>❑IGMP snooping and thus the snooping querier is a globalNotes: function of a device.❑If the snoop-querier (IGMPv2 or v3) on a switch between two routers is active and the routers have a higher IPaddress than the switch, the switch will win the querierelection and thus the snoop queriers of the connectedrouters are disabled. As a result other switched ports at therouters will loose their querier, if there is no other availableand thus multicasting doesn’t work anymore.❑GMRP cannot be used simultaneously to IGMP, thus itNotes: cannot be used together with dynamic multicast routing.CLI commands:❑(Config) # set gmrp adminmode or # no set…(Config)#set gmrp adminmode or#no set❑(Config) # set gmrp interfacemode❑(Config) # set gmrp forward-all-groups❑(Interface x/y) #set gmrp interfacemode❑(Interface x/y) #set gmrp forward-all-groups❑> show gmrp configuration all>show gmrp configuration all❑> show gmrp configuration <slot/port>Notes: Multicast routing protocols are available in L3P firmwarepackage only!Which MC routing protocol should be selected?❑DVMRP uses its own routing protocol while PIM-DM uses DVMRP uses its own routing protocol while PIM DM usesthe UC protocol in operation. DVMRP knows better thetopology with advantage in routed switched networksespecially together with HIPER Ring, static routes withECMP.❑The opt-out protocols DVMRP and PIM-DM start flooding, asa result devices receive faster the streams.a result devices receive faster the streams.❑As opt-out solutions after expiration of the hold timer MCs are flooded again thus producing high load condition tillprunes are sent again.Holdtime DVMRP 2 h, fixedHoldtime PIM-DM 210 s, configurable till 18 h.❑Convergence after topology changes is faster at PIM DM.Convergence after topology changes is faster at PIM-DM.❑PIM offers configurable timers and thus a higher flexibility if necessary.❑DVMRP is limited to 32 hops.❑Enable unicast routing:Notes: (R1) (Configure)# ip routing❑Enable multicast routing(R1) (Configure)# ip multicast❑Note: if first “ip multicast” is entered with IGMP disabled and error message is displayed, but after “ip igmp” command theconfiguration is o.k.❑To route MCs over one single PIM-DM router there is no need for unicast routing but for routing MCs over cascadedneed for unicast routing, but for routing MCs over cascadedrouters a UC routing protocol is needed (usually OSPF).Notes: Example of configuration:❑(R1)> enable❑(R1)# configure❑(R1) (Configure)# ip igmp(R1)(C fi)#i i❑(R1) (Configure)# ip multicast❑(R1) (Configure)# ip dvmrp❑(R1) (Configure)# interface 1/1❑(R1) (Interface 1/1)# ip igmp❑(R1) (Interface 1/1)# ip dvmrp(R1)(Interface1/1)#ip dvmrp❑(R1) (Interface 1/1)# exit❑(R1) (Configure)# exit❑(R1)# show ip dvmrpNote:For training purposes it’s sufficient to disableDVMRP globally while it’s still enabled on theinterfaces andthen configure PIM-DM (see next slide).Example of configuration:Notes:❑(R1)> enable❑(R1)# configure❑(R1) (Configure)# ip igmp()(g)p❑(R1) (Configure)# ip multicast❑(R1) (Configure)# ip pimdm❑(R1) (Configure)# interface 1/1❑(R1) (Interface 1/1)# ip igmp❑(R1) (Interface 1/1)# ip pimdm mode❑(R1) (Interface 1/1)# exit❑(R1) (Configure)# exit(R1)(C fi)#i❑(R1)# show ip pimdm❑(R1)# show ip mcast❑(R1)# show ip igmpOptional:❑Configuration of holdtime in seconds (210 s default):(R1) (Configure)# ip pimdm holdtimes <30…64800>❑Configuration of hello time in seconds:(Interface s/p)# ip pimdm hello-interval <1…3600>Notes:Consecutive order of minimum configuration:❑Configure and enable router interfaces ❑Set prompt for a better orientation ❑Enable routingCLI command sequence:(replace x by router number)> enable# set prompt R x # configure(Config)# ip routing (Config)#show ip brief ❑Configure UC routing protocol globally❑Enable IGMP globally (automatically enables MC routing and IGMP snooping)❑Enable multicast forwarding (routing)Enable PIM SM globally (Config)# show ip brief (Config)# router ospf(Config-router)# router-id x .1.1.1(Config-router)# enable(Config-router)# redistribute connected [subnets](Config-router)# exit (Config)# ip igmp (Config)# ip multicast (Config)#ip pimsm ❑Enable PIM-SM globally ❑Set static Rendezvous Point ❑Configure routing interfaces❑Configure UC routing protocol per interface ❑Enable IGMP per interface, and set version Optionally change version (default =2)(Config)# ip pimsm(Config)# ip pimsm rp-address <ip-@> <MC @>…(Config)# interface <s/p>(Interface s/p)# ip address <ip-@> <mask>(Interface s/p)# routing(Interface s/p)# ip ospf area-id 0.0.0.0(Interface s/p)# ip ospf (Interface s/p)# ip igmp(Interface s/p)#ip igmp version <1|❑Optionally change version (default = 2)❑Enable PIM-SM on respective interfaces(Interface s/p)# ip igmp version <1|2|3>(Interface s/p)# ip pimsm mode (Interface s/p)# exit (Config)# exit # show ip pimsm# copy system:running-config nvram:startup-config # logoutThe IGMP version by default is 2.Notes: Please note that a Rendezvous Point must be configured on all PIM-SM enabled routers, even at the RP itself.The alternative is to define at least one Bootstrap router(BSR) and at least one RP candidate. At a customer site it’sgrecommended to configure 2 candidate RPs and 2 candidate BSRs for redundancy.Further commands:❑(Interface s/p)# show❑# show ip pimsm❑# show ip mcast#show ip mcast❑# show ip igmpOptional:❑Configuration of DR priority:(Interface s/p)# ip pimsm dr-priority <0…2,147,483,647>Configuration of hello interval in seconds(30s default):❑Configuration of hello interval in seconds (30 s default): (Interface s/p)# ip pimsm hello-interval <0…18000>❑Pre-requisite of PIM-SM is a correctly running UC routingNotes: protocol like OSPF.❑MC routing between 2 IFs on one router works if on this router an RP is defined. But the RP needs not to beconfigured itself.❑MC routing between 2 IFs on two routers only works if RP is defined on both routers and on the RP itself.❑For MC routing protocols at neighbor expiry only a trap is defined. For IGMP there is no trap implemented.❑Instead of statically define RPs, now BSR and RPNotes: candidates are configured from which a BSR and RP areelected.❑CLI commands:❑(Config)# ip pimsm bsr-candidate interface <slot/port>❑(Config)# ip pimsm rp-candidate interface <slot/port>Notes:1.Build up a routed network with DVMRPa)check behavior if producer is located in same and indifferent branch of consumer2.Build up a routed network with PIM-DM and check the2Build up a routed network with PIM DM and check thebehaviora)check behavior if producer is located in same and indifferent branch of consumer3.Build up a HIPER Ring with routed networks …a)check behavior if producer is located in same and indifferent branch of consumerAll MC packets with a TTL value less than the definedNotes: threshold were discarded at the specific interface.。