Cisco Catalyst 6880-X Specifications Page 103

  • Download
  • Add to my manuals
  • Print
  • Page
    / 111
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 102
Core Layer April 2014
100
Step 1: Enable IP Multicast routing on the platform in the global configuration mode.
ip multicast-routing
Step 2: Configure a second loopback interface for RP functions on the core VSS switch. All routers point to this
IP address on loopback 1 for the RP. You configure the RP address from the core IP address space. Creating the
RP on a second loopback interface allows for flexibility for potential RP migrations using Anycast RP operation. In
the event you add a core layer to your existing network and the RP is currently configured on a distribution layer,
you may want to move the RP to the core.
interface Loopback 1
ip address 10.4.40.252 255.255.255.255
ip pim sparse-mode
Step 3: Configure AutoRP candidate RPs.
The send-rp-announce command in conjunction with the group-list option advertises the RP address, with the
multicast range the device is willing to serve, as a candidate RP to the AutoRP mapping agents.
access-list 10 permit 239.1.0.0 0.0.255.255
ip pim send-rp-announce Loopback1 scope 32 group-list 10
Step 4: Configure AutoRP mapping agent.
The AutoRP mapping agent listens for candidate RPs and then advertises to the rest of the network the list of
available RPs. The send-rp-discovery command enables the core switches to act as AutoRP mapping agents.
ip pim send-rp-discovery Loopback1 scope 32
Step 5: Configure devices to listen to AutoRP announcements.
All Layer 3 switches and routers in the organization, including the RP switches, must be configured to listen to
the AutoRP announcements from the mapping agents.
ip pim autorp listener
Devices other than the Cisco Catalyst 6800 and 6500 Series use the command ip pim auto-rp listener.
All Layer 3 interfaces in the network are enabled for sparse mode multicast operation.
C6500-VSS(config-if)#ip pim sparse-mode
Procedure 5 Connect to the distribution layer
In this design, links to the core VSS are configured as point-to-point Layer 3 routed EtherChannels. When using
Cisco Catalyst 6800 or 6500 Series VSS system in the campus, all peer-connected links are EtherChannel links,
with EtherChannel members distributed between the physical switches in the VSS. EtherChannel to the VSS
provides for optimal forwarding because a packet that is received on the switch will be forwarded out a link on
that same switch in normal operation instead of traversing the VSL connection.
Other benefits of EtherChannel to any single physical or logical device are that it makes it easier for bandwidth
growth without changing the topology. A single link failure uses EtherChannel recovery versus using ECMP or a
routing topology change to reroute the data flows for fastest recovery.
Since the core links are point-to-point routed links, use 30-bit IP address subnets and masks and do not use
Switched Virtual Interfaces (SVI).
Page view 102

Comments to this Manuals

No comments