nulticant no tiene sentido utilizar TCP

· siusamos

Utiliza UDP
se
= Siempre

The naming of copyrighted trademarks in this manual, even when not specially indicated, should not
Notes:
be taken to mean that these names may be considered as free in the sense of the trademark and
tradename protection law and hence that they may be freely used by anyone.

© 2015 Hirschmann Automation and Control GmbH

Manuals and software are protected by copyright. All rights reserved. The copying, reproduction,
translation, conversion into any electronic medium or machine scannable form is not permitted, either
in whole or in part. An exception is the preparation of a backup copy of the software for your own
use. For devices with embedded software, the end-user license agreement on the enclosed CD/DVD
applies.

The performance features described here are binding only if they have been expressly agreed when
the contract was made. This document was produced by Hirschmann Automation and Control GmbH
according to the best of the company's knowledge. Hirschmann reserves the right to change the
contents of this document without prior notice. Hirschmann can give no guarantee in respect of the
correctness or accuracy of the information in this document.

Hirschmann can accept no responsibility for damages, resulting from the use of the network
components or the associated operating software. In addition, we refer to the conditions of use
specified in the license contract.

Printed in Germany
Hirschmann Automation and Control GmbH
Stuttgarter Str. 45-51
72654 Neckartenzlingen
Germany
Tel.: +49 1805 141538

1
 Notes:
 Multicast data streams are data packets that a sender sends to multiple
recipients. To reduce the network load, the sender uses a Multicast address.
He thus sends each packet only once to the Multicast address instead of
sending it to each recipient individually. The recipients recognize a Multicast
data stream intended for them by the Multicast address.

 A common reason for introducing subnetworks is the restriction of Broadcast

data streams. Switches flood Broadcast/Multicast data streams to all ports,
while routers block Broadcast/Multicast data streams. Multicast routing enables
you to accurately transmit Multicast data streams beyond the boundaries of
subnetworks. Accurate transmission means sending data streams with defined
Multicast addresses exclusively to those devices that want to receive the
Multicast data stream.

2
 Notes:
 To the use of Multicast routing pertains:
 Defined Multicast addresses
 A protocol for Multicast group registration that organizes the exchange of
information by means of Multicast data streams (e.g. IGMP). This
information relates to the reporting that network participants wish to receive
Multicast data streams and querying this wish by means of intermediate
devices.
 A protocol that guides the Multicast streams through a routed network in
accordance with the information on Multicast streams.

3
 Notes:
 The source based tree is the simplest form for a multicast distribution tree. The
tree is built up from the source through the routed network to the receivers.
Because the shortest path through the network is used, it is also called
Shortest Path Tree (SPT).

 The example above shows the device 10.0.0.10 sending a multicast stream to
the address 239.1.1.1with the devices 192.168.0.20 and 172.16.0.30 as the
receivers.

 The notation (S, G) specifies a SPT where S is the IP address of the source
and G is the multicast address. In the above example the notation for this SPT
is (10.0.0.10, 239.1.1.1).

 The method of the shortest paths is very efficient with regard to the data paths.
However, it does have the disadvantage that, depending on the topology, the
routers require a lot of memory space to store the many Multicast trees.

4
 Notes:
 In unicast routing the routers forwards an IP packet through the routed network
using the destination IP address inside the IP packets. They do not take care
about the source IP addresses. Based on the information in the routing table a
single copy of the IP packet is forwarded to the destination.

 Using multicasts a single source sends a the date to an arbitrary group of

devices. To avoid duplication of multicast packets the multicast routers needs
to determine in which direction the upstream is towards the source of the
multicast stream and in which direction or directions the multicast streams
needs to be forwarded (downstream). If there are multiple path in downstream
direction the multicast router replicates the packets and forwards them in
downstream direction. The result is the source-routed Multicast distribution
tree. Source-routed means that the calculation method is tracing back from the
recipient to the source (RPF - Reverse Path Forwarding).

 To avoid loops, the multicast router will perform an RPF check on a multicast
packet it receives. If the multicast packet belongs to a longer path in direction
to the source the multicast router will drop the packets. Otherwise the packet
will be forwarded.

5
 Notes:
 If a router has no local connected receivers and no downstream routers with
registrations, it can signal to other routers via Prune message, that it doesn’t
want to receive a certain MC stream for a given time (Prune Lifetime). Thus
bandwidth in the network is spared. After Prune Lifetime, periodically, flooding
is reactivated, to facilitate the reception at newly connected devices. When
flooding starts again it lasts – dependent on the used devices – only a couple of
seconds till the load is reduced by renewed pruning.

6
 Notes:
 Once a tree branch has been pruned from a multicast delivery tree, packets
from the corresponding (S, G) pair will no longer be forwarded.

 Since IP multicast supports dynamic group membership (e.g. IGMP Reports),

hosts may join a multicast group at any time. In this case, a multicast router will
send a Graft message to its upstream neighbor if a group join occurs for a
group that the router has previously sent a prune. Separate Graft messages
must be sent to the appropriate upstream neighbor for each source network
that has been pruned.

 Since there would be no way to tell if a Graft message sent upstream was lost
or the source simply quit sending traffic, it is necessary to acknowledge each
Graft message with a Graft ACK message.

 If an acknowledgment is not received within a Graft Time-out period, the Graft

message should be retransmitted.

7
 Notes:
 The DVMRP (Distance Vector Multicast Routing Protocol) is a routing protocol
that uses its own distance vector algorithm to create its own Multicast routing
table. DVMRP works similarly to RIP and is limited to 32 hops.

 In the past, DVMRP was very widely-used, and it is used today because of its
compatibility with existing applications.

 DVMRP assume that very many participants are interested in the Multicast
groups. Therefore, at the start of the communication, DVMRP flood the
information about available Multicast groups into the entire network.
Participants who are not interested in a Multicast group unsubscribe from this
group explicitly.

 You select DVMRP if your application does not tolerate packet duplications and
is content with higher switching times. DVMRP provides a big advantage when
you are using divided subnetworks/VLANs in a redundant Layer-2 network.
Because DVMRP has its own unicast routing table, it already knows the
topology and thus prevents packet duplications.

8
 utiliza muchos suscriptores pero
se en topologías con
pocos emisores,
·

9 la aplicación soporte duplicidad de paquetes .

Notes:
 PIM-DM (Protocol Independent Multicast - Dense Mode) is a routing protocol
that uses the available Unicast routing table of other protocols like RIP, OSPF
or static routes to steer Multicast data streams.

 This ability, and the fast convergence it enables, is the reason why PIM-DM is
now very widely-used.

 PIM-DM assume that very many participants are interested in the Multicast
groups. Therefore, at the start of the communication, PIM-DM flood the
information about available Multicast groups into the entire network.
Participants who are not interested in a Multicast group unsubscribe from this
group explicitly.

 You select PIM-DM if your application requires fast switching times and is able
to tolerate any packet duplications during the switching time. You set fast
switching times by reducing the “Hello Time”. Packet duplications occur when
multiple routers are connected to a subnetwork. In this case, the Assert
Process clarifies which router is permitted to send into the subnetwork. Until
this is clarified, all routers send into this subnetwork.

9
 Notes:
 While source based trees built up their tree based on the source, shared trees
use a central transmission point, called Rendezvous Point (RP).

 The Router connected to the multicast sources register the multicast group at a
rendezvous point and send the data exclusively to this rendezvous point, which
forwards the data to the Multicast receivers. There is exactly one rendezvous
point for each multicast group.

 Because all sources of multicasts use a common shared tree via the
Rendezvous Point, the notation (*, G) is used. The * means all sources and G
is the multicast address. In the example above the shared tree is written as (*,
239.1.1.1)

 With this procedure, the amount of stored tree information in the routers is
reduced and thus reduces the processor load for the devices.

 The disadvantage is, that depending on the application, there are shorter paths
between the Multicast recipients and the Multicast source than the rendezvous
point tree which increases the latency of the multicast streams.

10
 Notes:
 You select PIM-SM if your application has few participants and you can tolerate
longer paths for your application. In this case, PIM-SM has the advantage
that the data volume created in the routers remains small.

 When using PIM-SM, you have the option of defining a router as a rendezvous
point candidate for a Multicast group. To do this, you specify the Multicast
group for which the router can be used as the rendezvous point.

11
 Notes:
 Depending on the application, there are shorter paths between the Multicast
recipients and the Multicast source than the rendezvous point tree.

 In these cases, PIM-SM enables a switch to the direct path (SBT). If the data
rate for the Multicast transmission via the RP exceeds a configurable
threshold value, the router of the Multicast recipient unsubscribes from the
rendezvous point. Instead, the router of the Multicast recipient creates a direct
link to the last router before the Multicast source.

12
 Notes:
 PIM-SM provides two procedures for selecting the rendezvous point for a
Multicast group:
 Static RP configuration
In this procedure, one of the routers in the network is fixed as the
rendezvous point for a Multicast group. The other routers contain the IP
address of this router and the address of the related Multicast group in their
configuration.
 Dynamic RP configuration based on the Bootstrap Router procedure
(BSR)
In this procedure, the routers in the network determine the rendezvous point
dynamically. A router has the option to offer itself as a candidate for the task
of rendezvous point. The dynamic procedure uses bootstrap messages to
select the rendezvous point for a Multicast group. The bootstrap messages
also inform the other routers in the PIM-SM domain about the router
selected as the rendezvous point. The PIM-SM routers forward the
Bootstrap messages within the PIM-SM domain. The PIM-SM domain
consists of all the reachable routers with an activated PIM-SM protocol. An
active PIM-SM router has the option of limiting the domain as a BSR border.
A router configured in this way drops the received BSR messages.

13
 Ejemplo practico
· Conf .
de IPS 10 .
0 .
0
.
102 255 255 .
253 O .
.

"
.
103 7 3 "O

10 0 0 100 . . .
1 II "
.
8
10 . 0 .
0 101 .
vi Il 14 .
O

·
Para cambiar de password : Clic derecho sobre el switch y Change Password
· HiVision : 1 .
Scan Network .

.
2 Autotopology

· Cerrar anillo en Ring Manager

debe habilitar
·
En todos los
puertos q van a intervencio en el anillo se

el MRP y deshabilitar el stpen los puertos de 4switch .

101 102
·
y
. -> vamos a crear
m
subring .
VLAN 200
13.
y .

· El ler amillo : VLAN 100 · 100,. 101 y . 102

HiVisión
·
Seleccione todos los
equipos Clie derecho/Multiconfig/ULANS ITable
=> Puedo configurar la VLAN de control en todos los switches
YLAN 1000