User manual 3COM LS-3100-52P-OVS-H3

[. . . ] H3C S5500-EI Series Ethernet Switches Operation Manual Hangzhou H3C Technologies Co. , Ltd. http://www. h3c. com Manual Version: 20090108-C-1. 01 Product Version: Release 2202 Copyright © 2008-2009, Hangzhou H3C Technologies Co. , Ltd. and its licensors All Rights Reserved No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Hangzhou H3C Technologies Co. , Ltd. Trademarks H3C, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL, SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT, XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co. , Ltd. All other trademarks that may be mentioned in this manual are the property of their respective owners. Notice The information in this document is subject to change without notice. [. . . ] Enter system view Enter PIM view Configure the SSM group range Use the command. . . system-view pim ssm-policy acl-number -- -- Optional 232. 0. 0. 0/8 by default Remarks Make sure that the same SSM group range is configured on all routers in the entire domain. Otherwise, multicast information cannot be delivered through the SSM model. When a member of a multicast group in the SSM group range sends an IGMPv1 or IGMPv2 report message, the device does not trigger a (*, G) join. Configuring PIM Common Features For the functions or parameters that can be configured in both PIM view and interface view described in this section: Configurations performed in PIM view are effective to all interfaces, while configurations performed in interface view are effective to the current interface only. If the same function or parameter is configured in both PIM view and interface view, the configuration made in interface view has preference over the configuration made in PIM view, regardless of the configuration sequence. PIM Common Feature Configuration Task List Complete these tasks to configure PIM common features: Task Configuring a Multicast Data Filter Configuring a Hello Message Filter 1-29 Remarks Optional Optional Task Configuring PIM Hello Options Configuring PIM Common Timers Configuring Join/Prune Message Sizes Optional Optional Optional Remarks Configuration Prerequisites Before configuring PIM common features, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the network layer. Before configuring PIM common features, prepare the following data: An ACL rule for filtering multicast data An ACL rule defining a legal source address range for hello messages Priority for DR election (global value/interface level value) PIM neighbor timeout time (global value/interface value) Prune delay (global value/interface level value) Prune override interval (global value/interface level value) Hello interval (global value/interface level value) Maximum delay between hello message (interface level value) Assert timeout time (global value/interface value) Join/prune interval (global value/interface level value) Join/prune timeout (global value/interface value) Multicast source lifetime Maximum size of join/prune messages Maximum number of (S, G) entries in a join/prune message Configuring a Multicast Data Filter No matter in a PIM-DM domain or a PIM-SM domain, routers can check passing-by multicast data based on the configured filtering rules and determine whether to continue forwarding the multicast data. These filters can help implement traffic control on one hand, and control the information available to receivers downstream to enhance data security on the other hand. Enter system view Enter PIM view Configure a multicast group filter Use the command. . . system-view pim source-policy acl-number -- -- Required No multicast data filter by default Remarks 1-30 Generally, a smaller distance from the filter to the multicast source results in a more remarkable filtering effect. This filter works not only on independent multicast data but also on multicast data encapsulated in register messages. Configuring a Hello Message Filter Along with the wide applications of PIM, the security requirement for the protocol is becoming more and more demanding. The establishment of correct PIM neighboring relationships is the prerequisite for secure application of PIM. You can configure a legal source address range for hello messages on interfaces of routers to ensure the correct PIM neighboring relationships, and thus to guard against PIM message attacks. Enter system view Enter interface view Configure a hello message filter Use the command. . . system-view interface interface-type interface-number pim neighbor-policy acl-number -- -- Required No hello message filter by default. Remarks With the hello message filter configured, if hello messages of an existing PIM neighbor fail to pass the filter, the PIM neighbor will be removed automatically when it times out. Configuring PIM Hello Options No matter in a PIM-DM domain or a PIM-SM domain, the hello messages sent among routers contain many configurable options, including: DR_Priority (for PIM-SM only): priority for DR election. You can configure this parameter on all the routers in a multi-access network directly connected to multicast sources or receivers. When this timer times out, if the router has received no hello message from a neighbor, it assumes that this neighbor has expired or become unreachable. LAN_Prune_Delay: the delay of prune messages on a multi-access network. This option consists of LAN-delay (namely, prune delay), override-interval, and neighbor tracking flag. If the LAN-delay or override-interval values of different PIM routers on a multi-access subnet are different, the 1-31 largest value will take effect. If you want to enable neighbor tracking, the neighbor tracking feature should be enabled on all PIM routers on a multi-access subnet. The LAN-delay setting will cause the upstream routers to delay processing received prune messages. [. . . ] For the detailed description of the UDP Helper function, refer to UDP Helper Configuration in the IP Services Volume. Executing the Configuration File Upon successfully obtaining the configuration file, the device removes the temporary configuration and executes the obtained configuration file; otherwise, it removes the temporary configuration and starts up without loading the configuration file. After the device executes the configuration file obtained, the configuration file will be deleted. Therefore, you are recommended to save the configuration using the save command; otherwise, the device needs to perform the automatic configuration function after system reboot. For the detailed description of the save command, refer to File System Management Configuration in the System Volume. 1-7 Table of Contents 1 IPC Configuration ······································································································································1-1 IPC Overview ··········································································································································1-1 Introduction to IPC···························································································································1-1 Enabling IPC Performance Statistics ······································································································1-2 Displaying and Maintaining IPC ··············································································································1-3 i 1 IPC Configuration When configuring IPC, go to these sections for information you are interested in: IPC Overview Enabling IPC Performance Statistics Displaying and Maintaining IPC IPC Overview Introduction to IPC Inter-Process Communication (IPC) is a reliable communication mechanism among different nodes. The following are the basic concepts in IPC. Node An IPC node is an entity supporting IPC; it is an independent processing unit. [. . . ]