A Networker Blog

R4(config)#service password-encryption
R4(config)#username victor pass cappuccio
R4(config)#do show run | in username
username victor password 7 121A0407021E0F072324
R4(config)#!Huu so you are looking for something
R4(config)#!like
R4(config)#!http://bosondownload.com/utils/bos_getpass.exe
R4(config)#!or
R4(config)#key chain HOWCOOL
R4(config-keychain)#key 1
R4(config-keychain-key)#key-str 7 121A0407021E0F072324
R4(config-keychain-key)#do show key chain
Key-chain HOWCOOL:
key 1 — text “cappuccio”
accept lifetime (always valid) - (always valid) [valid now]
send lifetime (always valid) - (always valid) [valid now]
R4(config-keychain-key)#

Thanks Brian Dennis (Internetwork Expert Author and Owner) for this Tip

http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a00804435fc.html

Since BGP uses TCP session, there is no way to verify the presence of a BGP Neighbor, except when sending BGP Traffic, so BGP sends keepalives every 60 seconds

Keepalive interval value is not communicated in the BGP Open Message

Default Values:
Keepalive 60 Seconds
HoldTime 180 Seconds

NOTE:

BGP does not use any transport protocol-based keep-alive mechanism to determine if peers are reachable. Instead, KEEPALIVE messages are exchanged between peers often enough as not to cause the Hold Timer to expire. A reasonable maximum time between KEEPALIVE messages would be one third of the Hold Time interval. KEEPALIVE messages MUST NOT be sent more frequently than one per second. An implementation MAY adjust the rate at which it sends KEEPALIVE

Example of this:

R3 and R4 in AS 34

Smaller integer in relation to (holtime/3), if holdtime of neigh is used and keepalive > (holdtime/3)

R3#
router bgp 34
timers bgp 15 30

R3#show ip bgp neigh | in keep
Last read 00:00:06, last write 00:00:06, hold time is 30, keepalive interval i
s 10 seconds
Configured hold time is 30,keepalive interval is 15 seconds, Minimum holdtime
from neighbor is 0 seconds

R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:02, last write 00:00:02, hold time is 30, keepalive interval i
s 10 seconds

Notice the configured Keepalive (15) in R3 and the selected keepalive in R4 10 seconds, but R3 is using 10 as the keepalive, since is the lowest keepalive (holdtime /3)

Another example

R3(config-router)#timer bgp 20 30
R3(config-router)#do clear ip bgp *

R3(config-router)#do show ip bgp neigh | in keep
Last read 00:00:07, last write 00:00:07, hold time is 30, keepalive interval i
s 10 seconds
Configured hold time is 30,keepalive interval is 20 seconds, Minimum holdtime
from neighbor is 0 seconds

R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:05, last write 00:00:05, hold time is 30, keepalive interval i
s 10 seconds

Notice now that R3 had been configured with 20 of keepalive and 30 of holdtime
and the selected values are 30 and 10

if the holddtime interval of the neigbor is selected and the locally configured keepalive is less than a third of the holdtime intercal the peers use the locally configured keep alive

R3(config-router)#timer bgp 9 30
R3(config-router)#do clear ip bgp *
R3(config-router)#
*Nov 17 16:31:25.853: %BGP-5-ADJCHANGE: neighbor 1.1.1.4 Down User reset
R3(config-router)#
*Nov 17 16:31:27.885: %BGP-5-ADJCHANGE: neighbor 1.1.1.4 Up
R3(config-router)#do show ip bgp neigh | in keep
Last read 00:00:06, last write 00:00:06, hold time is 30, keepalive interval i
s 9 seconds
Configured hold time is 30,keepalive interval is 9 seconds, Minimum holdtime f
rom neighbor is 0 seconds
R3(config-router)#

R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:01, last write 00:00:08, hold time is 30, keepalive interval i
s 10 seconds

Another Example

R4(config-router)#timer bgp 7 60
R4(config-router)#do clear ip bgp *
R4(config-router)#
%BGP-5-ADJCHANGE: neighbor 1.1.1.3 Down User reset
%BGP-5-ADJCHANGE: neighbor 1.1.1.3 Up
R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:04, last write 00:00:05, hold time is 30, keepalive interval i
s 7 seconds
Configured hold time is 60,keepalive interval is 7 seconds, Minimum holdtime f
rom neighbor is 0 seconds
R4(config-router)#

R3(config-router)#do show run | in timer
timers bgp 9 30
R3(config-router)#do show ip bgp neigh | in keep
Last read 00:00:05, last write 00:00:03, hold time is 30, keepalive interval i
s 9 seconds
Configured hold time is 30,keepalive interval is 9 seconds, Minimum holdtime f
rom neighbor is 0 seconds
R3(config-router)#

R4(config-router)#timer bgp 11 60
R4(config-router)#do clear ip bgp *

%BGP-5-ADJCHANGE: neighbor 1.1.1.3 Down User reset
%BGP-5-ADJCHANGE: neighbor 1.1.1.3 Up
R4(config-router)#do show ip bgp

R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:07, last write 00:00:07, hold time is 30, keepalive interval i
s 10 seconds
Configured hold time is 60,keepalive interval is 11 seconds, Minimum holdtime
from neighbor is 0 seconds
R4(config-router)#

R4(config-router)#no timers bgp 11 60
R4(config-router)#do clear ip bgp *
%BGP-5-ADJCHANGE: neighbor 1.1.1.3 Down User reset
%BGP-5-ADJCHANGE: neighbor 1.1.1.3 Up
R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:04, last write 00:00:04, hold time is 30, keepalive interval i
s 10 seconds
R4(config-router)#

R3(config-router)#timers bgp 11 40
R3(config-router)#do clear ip bgp *

R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:03, last write 00:00:02, hold time is 40, keepalive interval i
s 13 seconds

R3(config-router)#do show ip bgp neigh | in keep
Last read 00:00:00, last write 00:00:09, hold time is 40, keepalive interval i
s 11 seconds
Configured hold time is 40,keepalive interval is 11 seconds, Minimum holdtime
from neighbor is 0 seconds

R3(config-router)#no timers bgp 11 40
R3(config-router)#do clear ip bgp *
R3(config-router)#
%BGP-5-ADJCHANGE: neighbor 1.1.1.4 Down User reset
%BGP-5-ADJCHANGE: neighbor 1.1.1.4 Up
R3(config-router)#do show ip bgp neigh | in keep
Last read 00:00:13, last write 00:00:13, hold time is 180, keepalive interval
is 60 seconds

R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:29, last write 00:00:29, hold time is 180, keepalive interval
is 60 seconds

R4(config-router)#timers bgp 10 59
R4(config-router)#do clear ip bgp *
R4(config-router)#
%BGP-5-ADJCHANGE: neighbor 1.1.1.3 Down User reset
R4(config-router)#
*Nov 17 16:43:13.489: %BGP-5-ADJCHANGE: neighbor 1.1.1.3 Up

R3(config-router)#do show ip bgp neigh | in keep
Last read 00:00:01, last write 00:00:01, hold time is 59, keepalive interval i
s 19 seconds

R4(config-router)#do show ip bgp neigh | in keep
Last read 00:00:12, last write 00:00:01, hold time is 59, keepalive interval i
s 10 seconds
Configured hold time is 59,keepalive interval is 10 seconds, Minimum holdtime
from neighbor is 0 seconds

Is there any more options you could see

Victor.-

In this topology We want to filter the 192.168.100.0 network from being redistributed into the OSPF topology. We also want to filter the other 192.168.x.0 networks with an odd third octet. We could use a route-map in our redistribution statement, but that is not the method that we are going to use here.

We need to permit several routes out to the OSPF neighbors. In order to filter these networks, we will need to be very specific with our access list. If we have two deny statements, the third statement can be a permit statement to allow all other networks to pass. The networks that we need to block are 192.168.100.0, 192.168.1.0, 192.168.3.0, and 192.168.5.0. We will block the 192.168.100.0 by itself, and we will need to block the .1, .3, and .5 networks in a single line. Let’s take a look at the binary for these three, and see how we can match all three in a single line.

1 – 0 0 0 0 0 0 0 1
3 – 0 0 0 0 0 0 1 1
5 – 0 0 0 0 0 1 0 1

The only bits that are different are the sixth and seventh bits. If we set these as don’t care bits, our mask will be:
0 0 0 0 0 1 1 0

This converts to 6 in decimal. Our second access list statement will deny 192.168.1.0 with a mask of 0.0.6.0

R5#conf ter
Enter configuration commands, one per line. End with CNTL/Z.
R5(config)#access-list 89 deny 192.168.100.0
R5(config)#access-list 89 deny 192.168.1.0 0.0.6.0
R5(config)#access-list 89 permit any
R5(config)#router ospf 1
R5(config-router)#distribute-list 89 out eigrp 55
R5(config-router)#red eigrp 55 sub
R5(config-router)#

Ordinarily, you would not use an outbound distribute list with OSPF, because all routers in the area need to have the same link-state information. Since R5 is a redistributing router, it will affect which routes are redistributed from EIGRP into OSPF.

R1#show ip route 192.168.2.0
Routing entry for 192.168.2.0/24
Known via “ospf 1″, distance 110, metric 20, type extern 2, forward metric 64
Last update from 143.2.153.5 on Serial0/0/0.1, 00:00:29 ago
Routing Descriptor Blocks:
* 143.2.153.5, from 100.5.5.5, 00:00:29 ago, via Serial0/0/0.1
Route metric is 20, traffic share count is 1

R1#show ip route 192.168.1.0
% Network not in table
Cheers!

Victor.-

******* GROUP NAME *******

CITE (Consortium of Information Technology Experts)

******* PURPOSE/OVERVIEW *******

To provide a technical support resource for all group members based on
real-life/real-world scenarios, and whose members consist of technical
experts with a primarily Cisco-based background. All members should exhibit
the highest standards of excellence, professionalism, and quality in regards
to posting/emails and other correspondence. The group will strive to
maintain the highest levels of integrity and exclusivity regarding group
member evaluation and acceptance.

LinkedIn provides the public aspect of the group’s identity, as well as an
association to an established and respected community.

Google Groups provides the vehicle by which the questions, answers, and
ideas are exchanged

******* MEMBER REQUIREMENTS *******

1. Certified as a CCNA or CCDA in the past *
2. 7 years or more of direct Cisco industry experience

* If candidate has not achieved CCxA status, then they must receive a
referral from at least two CCIEs verifying their Cisco technical
expertise/knowledge, in the form of an email to the group administrator

******* MEMBERSHIP PROCEDURES FOR NEW MEMBERS *******

1. If not already existing, create a LinkedIn profile containing full work
history

2. Follow this URL to request access to the group:
http://www.linkedin.com/e/gis/39670/694BBF19E9C9

3. On the ensuing page, click the “notify group manager” link to send an
email request for membership. You will receive an auto reply that will
contain further instructions on certification validation.

An idealist is a person who helps other people to be prosperous.

By Henry Ford.

TCL script that could also help in doing a shutdown to several interfaces UP and running

R3>en
R3#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#int lo0
R3(config-if)#no sh
R3(config-if)#exit
R3(config)#int lo1
R3(config-if)#exit
R3(config)#int lo2
R3(config-if)#exit
R3(config)#int lo3
R3(config-if)#exit
R3(config)#int lo4
R3(config-if)#exit
R3(config)#exit
R3#
*Nov  6 13:38:17.535: %SYS-5-CONFIG_I: Configured from console by console
R3#

R3>en
R3#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#exit
R3#t
*Nov  6 13:41:02.487: %SYS-5-CONFIG_I: Configured from console by console
R3#tclsh
R3(tcl)#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#foreach i {
+>(config)#lo0
+>(config)#lo1
+>(config)#lo2
+>(config)#} {
+>(config)#int $i
+>(config)#sh
+>(config)#exit
+>(config)#}

R3(config)#do show ip int brioe
*Nov  6 13:41: 35.451: %LINK-5-CHANGED: Interface Loopback1, changed state to adm
inistratively down
*Nov  6 13:41:35.463: %LINK-5-CHANGED: Interface Loopback2, changed state to adm
inistratively down
R3(config)#\

Enjoy

Victor Cappuccio
www.vcappuccio.wordpress.com

SW1#show ip ospf database external 2.2.2.0

OSPF Router with ID (9.9.9.9) (Process ID 1)

Type-5 AS External Link States

Routing Bit Set on this LSA
LS age: 58
Options: (No TOS-capability, DC)
LS Type: AS External Link
Link State ID: 2.2.2.0 (External Network Number )
Advertising Router: 4.4.4.4
LS Seq Number: 80000001
Checksum: 0xAC5A
Length: 36
Network Mask: /24
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 20
Forward Address: 192.168.24.2
External Route Tag: 0

Now If you do not know about 192.168.24.2

SW1#show ip route 192.168.24.2
% Network not in table

SW1#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address
Interface
4.4.4.4 1 FULL/BDR 00:00:32 192.168.14.4 Vlan14
1.1.1.1 255 FULL/DR 00:00:37 192.168.100.1
Vlan100
10.10.10.10 1 FULL/BDR 00:00:36 192.168.100.10
Vlan100

SW1#show ip ospf database

OSPF Router with ID (150.150.0.1) (Process ID 100)

OSPF Router with ID (9.9.9.9) (Process ID 1)

Router Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Link
count
1.1.1.1 1.1.1.1 86 0×80000142 0×00BB4E 4
4.4.4.4 4.4.4.4 20 0×80000005 0×00EA1B 1
6.6.6.6 6.6.6.6 897 0×8000012B 0×005A47 3
9.9.9.9 9.9.9.9 25 0×80000143 0×006822 4
10.10.10.10 10.10.10.10 87 0×8000002B 0×00766C 2

Net Link States (Area 0)

Link ID ADV Router Age Seq# Checksum
192.168.14.10 9.9.9.9 26 0×80000001 0×00DB84
192.168.100.1 1.1.1.1 70 0×80000002 0×00F71A

Type-5 AS External Link States

Link ID ADV Router Age Seq# Checksum Tag
2.2.2.0 4.4.4.4 16 0×80000001 0×00AC5A 0

Looking at the OSPF External database

SW1#show ip ospf database external 2.2.2.0

OSPF Router with ID (150.150.0.1) (Process ID 100)

OSPF Router with ID (9.9.9.9) (Process ID 1)

Type-5 AS External Link States

LS age: 23
Options: (No TOS-capability, DC)
LS Type: AS External Link
Link State ID: 2.2.2.0 (External Network Number )
Advertising Router: 4.4.4.4
LS Seq Number: 80000001
Checksum: 0xAC5A
Length: 36
Network Mask: /24
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 20
Forward Address: 192.168.24.2
External Route Tag: 0

SW1#show ip route 192.168.24.0
% Network not in table
SW1#ping 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
…..
Success rate is 0 percent (0/5)
SW1#
RTR-TS1#4
[Resuming connection 4 to R4 ... ]

*Mar 2 01:09:09.225: %OSPF-5-ADJCHG: Process 100, Nbr 2.2.2.2 on
Serial0.42 from LOADING to FULL, Lo
R4(config-router)#router ospf 100
R4(config-router)#
R4(config-router)#area 42 nssa translate type7 suppress-fa
R4(config-router)#
RTR-TS1#2
[Resuming connection 2 to sw1 ... ]

SW1#show ip ospf database external 2.2.2.0

OSPF Router with ID (150.150.0.1) (Process ID 100)

OSPF Router with ID (9.9.9.9) (Process ID 1)

Type-5 AS External Link States

Routing Bit Set on this LSA
LS age: 8
Options: (No TOS-capability, DC)
LS Type: AS External Link
Link State ID: 2.2.2.0 (External Network Number )
Advertising Router: 4.4.4.4
LS Seq Number: 80000002
Checksum: 0×2564
Length: 36
Network Mask: /24
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 20
Forward Address: 0.0.0.0 ———- Forwarding address modified
External Route Tag: 0

SW1#ping 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 59/62/67 ms
SW1#

SW1#show ip route 2.2.2.2
Routing entry for 2.2.2.0/24
Known via “ospf 1″, distance 110, metric 20, type extern 2, forward
metric 1
Last update from 192.168.14.4 on Vlan14, 00:02:09 ago
Routing Descriptor Blocks:
* 192.168.14.4, from 4.4.4.4, 00:02:09 ago, via Vlan14
Route metric is 20, traffic share count is 1

SW1#show ip route 0.0.0.0
% Network not in table
SW1#

So in short, if you do not know about the forwarding
address (192.168.24.2, above), possibly because of lsa type 3 filtering, you
can suppress the FA, this results in the FA being 0.0.0.0 which forces the
use of the ASBR to reach the destination in question.

Have Fun!

Victor Cappuccio.-

This configuration is based on this link

The requirement is to configure a Loopback0 on R3 and configure the following IPv6 Networks on R3 and R4.

The configuration on R3 is:

Loopback0    3:3:3:33::/64
Fast0/1    3:3:3:30::/64
Serial0/0/1    3:3:3:34::/64

The configuration on R4 is:
Fast0/0        3:3:3:40::/64
Serial0/0/1        3:3:3:34::/64

R3#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#
R3(config)#ipv6 unicast-routing
R3(config)#interface Loopback0
R3(config-if)#ipv6 address 3:3:3:33::/64 eui-64
R3(config-if)#interface FastEthernet0/1
R3(config-if)#ipv6 address 3:3:3:30::/64 eui-64
R3(config-if)#interface Serial0/0/1
R3(config-if)#ipv6 address 3:3:3:34::/64 eui-64
R3(config-if)#exit
R3(config)#^Z

R4#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R4(config)#
R4(config)#ipv6 unicast-routing
R4(config)#interface FastEthernet0/1
R4(config-if)#ipv6 address 3:3:3:40::/64 eui-64
R4(config-if)#interface Serial0/0/1
R4(config-if)#ipv6 address 3:3:3:34::/64 eui-64
R4(config-if)#

Now we are going to configure RIPng and make sure R3 and R4 can ping all IPv6 networks

R3#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#ipv6 unicast-routing
R3(config)#interface Loopback0
R3(config-if)#ipv6 rip Lab3 enable
R3(config-if)#interface FastEthernet0/1
R3(config-if)#ipv6 rip Lab3 enable
R3(config-if)#interface Serial0/0/1
R3(config-if)#ipv6 rip Lab3 enable
R3(config-if)#^Z

R4#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R4(config)#
R4(config)#ipv6 unicast-routing
R4(config)#interface FastEthernet0/1
R4(config-if)#ipv6 rip Lab3 enable
R4(config-if)#interface Serial0/0/1
R4(config-if)#ipv6 rip Lab3 enable
R4(config-if)#^Z
R4#

We can check the routing and then perform a test ping from R4’s LAN to R3’s loopback.

R3#sh ipv6 route
IPv6 Routing Table - 9 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
C   3:3:3:30::/64 [0/0]
via ::, FastEthernet0/1
L   3:3:3:30:217:EFF:FE64:5B19/128 [0/0]
via ::, FastEthernet0/1
C   3:3:3:33::/64 [0/0]
via ::, Loopback0
L   3:3:3:33:217:EFF:FE64:5B18/128 [0/0]
via ::, Loopback0
C   3:3:3:34::/64 [0/0]
via ::, Serial0/0/1
L   3:3:3:34:217:EFF:FE64:5B18/128 [0/0]
via ::, Serial0/0/1
R   3:3:3:40::/64 [120/2]
via FE80::216:C7FF:FEBE:6D58, Serial0/0/1
L   FE80::/10 [0/0]
via ::, Null0
L   FF00::/8 [0/0]
via ::, Null0
R3#

R4#sh ipv6 route
IPv6 Routing Table - 8 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
R   3:3:3:30::/64 [120/2]
via FE80::217:EFF:FE64:5B18, Serial0/0/1
R   3:3:3:33::/64 [120/2]
via FE80::217:EFF:FE64:5B18, Serial0/0/1
C   3:3:3:34::/64 [0/0]
via ::, Serial0/0/1
L   3:3:3:34:216:C7FF:FEBE:6D58/128 [0/0]
via ::, Serial0/0/1
C   3:3:3:40::/64 [0/0]
via ::, FastEthernet0/1
L   3:3:3:40:216:C7FF:FEBE:6D59/128 [0/0]
via ::, FastEthernet0/1
L   FE80::/10 [0/0]
via ::, Null0
L   FF00::/8 [0/0]
via ::, Null0

Now we are configuring R3 and R4 for IPv6 multicast-routing. Also, we are going to Configure R4 to join group FF04::40 using its Fast0/0 interface and make sure R3 is the PIM DR on the Serial network.

To configure a router to do IPv6 multicast routing we first need to configure the following command.

R3#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#ipv6 multicast-routing
R3(config)#^Z

R4#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R4(config)#ipv6 multicast-routing
R4(config)#^Z

The host to router signaling in IPv6 multicast is performed by a protocol called Multicast Lister Discovery (MLD). Cisco IOS supports MLDv1 (similar to IGMPv2) and MLDv2 (similar to IGMPv3). Below command will configure R4’s Fast0/0 to join the requested group.

R4#conf ter
Enter configuration commands, one per line.  End with CNTL/Z.
R4(config)#int f0/0
R4(config-if)#ipv6 mld join-group FF04::40

Note that unlike Ipv4 multicast, as soon as you configure IPv6 multicast routing all interfaces automatically run PIM-SM (IPv6 multicast only supports PIM-SM and PIM-SSM. No PIM-DM).

You can check your configuration using show ipv6 mroute

R4#show ipv6 mroute
Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group,
C - Connected, L - Local, I - Received Source Specific Host Report,
P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set,
J - Join SPT
Timers: Uptime/Expires
Interface state: Interface, State

(*, FF04::40), 00:00:06/never, RP ::, flags: SCLJ
Incoming interface: Null
RPF nbr: ::
Immediate Outgoing interface list:
FastEthernet0/1, Forward, 00:00:06/never

Now we need to make sure R3 is the PIM DR. The default DR priority is 1 one so we will configure R3’s Serial0/0/1 interface to have a priority of 2 and then check to make sure it is the DR.

R3(config)#int s0/0/1
R3(config-if)#ipv6 pim dr-priority 2
R3(config-if)#exit
R3(config)#do sh ipv6 pim interface Serial0/0/1
Interface          PIM  Nbr   Hello  DR
Count Intvl  Prior

Serial0/0/1        on   1     30     2
Address: FE80::217:EFF:FE64:5B18
DR     : this system

R3  is going to work as a candidate BSR and candidate RP for groups in the range FF00::/8 using Loopback0 address as an ID.

Cisco IOS doesn’t support Auto-RP or at least not until 12.4T. It only supports BSR routers that look at candidate RP advertisements and send the mapping to the rest of the multicast routers.

The range specified in the question is in fact the whole IPv6 multicast range because an IPv6 Multicast address is identified by the first 8 bits being set (FF).

We will configure the commands below for BSR and RD candidature. Note that we don’t need to configure the Loopback interface for PIM because this happens automatically as soon as we configure IPv6 multicast.

R3(config)#ipv6 pim bsr candidate bsr  3:3:3:33:217:EFF:FE64:5B18 !Lo0
R3(config)#ipv6 pim bsr candidate rp  3:3:3:33:217:EFF:FE64:5B18
R3(config)#

We can confirm the configuration on R3 itself using the commands below.

R3#show ipv6 pim bsr candidate-rp
PIMv2 C-RP information
Candidate RP: 3:3:3:33:217:EFF:FE64:5B18 SM
All Learnt Scoped Zones, Priority 192, Holdtime 150
Advertisement interval 60 seconds
Next advertisement in 00:00:45

R3#show ipv6 pim bsr election
PIMv2 BSR information

BSR Election Information
Scope Range List: ff00::/8
BSR Address: ::
Uptime: 00:00:00, BSR Priority: 0, Hash mask length: 0
RPF: ::,
BS Timer: 00:00:21
This system is candidate BSR
Candidate BSR address: 3:3:3:33:217:EFF:FE64:5B18, priority: 0, hash mask length: 126

R3#sh ipv6 pim group-map info-source bsr

FF00::/8*
SM, RP: 3:3:3:33:217:EFF:FE64:5B18
RPF: Tu2,3:3:3:33:217:EFF:FE64:5B18 (us)
Info source: BSR From: 3:3:3:33:217:EFF:FE64:5B18(00:02:23), Priority: 192
Uptime: 00:00:06, Groups: 1

Enjoy

Victor Cappuccio.-

Your allocated with AS 0×315, use the corresponding Glop address to set the router ID for each router

So 0×315 is AS 789

Our Multicast Range is from 233.3.21.001 to 233.3.21.254

03 in hex == 2 in dec
15 in hex == 21 in dec

so the address used as the router ID would be: 233.3.21.0/24

The IANA should allocate 233/8. The remaining 24 bits will be administered as described in RFC1797:

Glop bit representation:

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 233 | 16 bits AS | local bits |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Consider, for exampe, AS 5662. Written in binary, left padded with 0s, we get 0001011000011110 Mapping the high order octet to the second octet of the address, and the low order octect to the the third octet, we get 233.22.30/24.

RFC 2770 proposes that the 233.0.0.0/8 address range be reserved for statically defined addresses by organizations that already have an AS number reserved. The AS number of the domain is embedded into the second and third octets of the 233.0.0.0/8 range.

For example, the AS 62010 is written in hex as F23A. Separating out the two octets F2 and 3A, we get 242 and 58 in decimal. This would give us a subnet of 233.242.58.0 that would be globally reserved for AS 62010 to use.

http://www.shepfarm.com/multicast/glop.html

Enjoy

Victor Cappuccio

ter le 0
show mpls tra tu bri
foreach i {
Tunnel11121
Tunnel11131
Tunnel11141
Tunnel11151
Tunnel11161
Tunnel11171
Tunnel21100
Tunnel31110
} { show mpls tra tu $i }

foreach i {
Tunnel11121
Tunnel11131
Tunnel11141
Tunnel11151
Tunnel11161
Tunnel11171
Tunnel21100
Tunnel31110
} { show run int $i }
ter le 30
tclquit

Rou01#tclsh
Rou01(tcl)# foreach i {
+>Tunnel11121
+>Tunnel11131
+>Tunnel11141
+>Tunnel11151
+>Tunnel11161
+>Tunnel11171
+>Tunnel21100
+>Tunnel31110
+> } { show mpls tra tu $i | in active|Tunn }
Name: #Main Rou01-VAL01# (Tunnel11121) Destination: 10.19.111
State: dynamic path option 1 is active
FRR OutLabel : Tunnel31110, 526
Tunnel:
Name: #Main Rou01toPLC01# (Tunnel11131) Destination: 10.19.111
State: dynamic path option 1 is active
Tunnel:
Name: #Main Rou01toPOZ01# (Tunnel11141) Destination: 10.19.111
State: dynamic path option 1 is active
Tunnel:
Name: #Main Rou01toBTO01# (Tunnel11151) Destination: 10.19.111
State: dynamic path option 1 is active
Tunnel:
Name: #Main Rou01toSNC01# (Tunnel11161) Destination: 10.19.111
State: dynamic path option 1 is active
Tunnel:
Name: #Main Rou01toMBO01# (Tunnel11171) Destination: 10.19.111
State: dynamic path option 1 is active
Tunnel:
Name: #BackLink Rou01toIP1CAN01# (Tunnel21100) Destination: 10.19.110
State: dynamic path option 1 is active
Tunnel:
Name: #B COL02# (Tunnel31110) Destination: 10.19.110
State: dynamic path option 1 is active
Tunnel:
Enjoy

Victor Cappuccio