From: Scott Morris (swm@xxxxxxxxxx)
Date: Wed May 15 2002 - 08:32:39 GMT-3
Well...
First, your BGP isn't going to do all that much because you have no
neighbor statements...
Second, your OSPF isn't going to do anything because there's nothing in
common! You have one link between the routers (192.168.1.0/24) and OSPF
is running on only one side of that. You haven't put this network into
OSPF on the second router.
So with those two things in mind, I don't think this is going to do all
that much. :) And I'm not quite sure I understand the logic behind
your redistribution loop and associated route-map. But that's a minor
point at the moment with no other routing working.
When configuring things like this, "show ip ospf interfaces" can be a
valuable command to tell you what interfaces WILL be playing with OSPF.
And telling you about things you may have missed!
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Jason Sinclair
Sent: Wednesday, May 15, 2002 3:22 AM
To: Jason Sinclair; 'ccielab@groupstudy.com'
Subject: RE: POP Quiz - Answers
All,
Guys,
For pop quiz 1 I have the following configs. I have not labbed them due
to time constraints, however I believe they are correct. If you see any
mistakes please advise.
Configs are:
RtrA
Int lo0
Ip address 1.1.1.1 255.255.255.255
Int s0
Ip address 192.168.1.1 255.255.255.0
Router ospf 100
Network 192.168.1.0 0.0.0.255 area0
Redistribute bgp 100 subnets
Router bgp 100
Network 1.1.1.1 mask 255.255.255.255
Redistribute ospf 100 route-map tags
No auto-summary
No synchronization
Route-map tags permit 10
Set as-path tag
Rtrb
Int s0
Ip address 192.168.1.2 255.255.255.0
Clock rate 64000
Int s1
Ip address 172.16.1.1 255.255.255.0
Clock rate 64000
Router ospf 100
Network 192.168.1.0 0.0.0.255 area 0
Network 172.16.1.0 0.0.0.255 area 0
Rtrc
Int lo0
Ip address 3.3.3.3 255.255.255.255
Int s0
Ip address 172.16.1.2 255.255.255.0
Router ospf 100
Network 172.16.1.0 0.0.0.255 area0
Redistribute bgp 100 subnets
Router bgp 100
Redistribute ospf 100 route-map tags
Network 3.3.3.3 mask 255.255.255.255
No auto-summary
No synchronization
Route-map tags permit 10
Set as-path tag
Cheers,
Jason Sinclair CCIE #9100
Manager, Network Control Centre
POWERTEL
Ground Level, 55 Clarence Street,
SYDNEY NSW 2000
AUSTRALIA
office: + 61 2 8264 3820
mobile: + 61 416 105 858
* sinclairj@powertel.com.au
-----Original Message-----
From: Jason Sinclair
[mailto:sinclairj@powertel.com.au]
Sent: Wednesday, 8 May 2002 13:32
To: 'ccielab@groupstudy.com'
Subject: POP Quiz
All,
I am proposing to regularly post little scenarios to
this forum. If you see
any benefit in this, the first is below:
Quick Scenario 1:
A quick scenario - should take 10 minutes to achieve.
Topology is:
RtrA-----rtrB-------rtrC
Rules:
1. You can run BGP on rtrA and rtrC, but NOT rtrB.
2. Any IGP can be run on rtrA, rtrB, rtrC.
3. Create a loopback on rtrA and rtrC and ensure
that
the opposite
route to the loopback is visible to the remote router
via BGP.
4. You cannot peer rtrA and rtrC with respect to
BGP
5. The origin code for your route must be the same
as
the original
origin code when the route was injected into BGP
6. 10 minutes to complete
I will post answers in 5 days time.
Cheers,
Jason Sinclair CCIE #9100
Manager, Network Control Centre
POWERTEL
Ground Level, 55 Clarence Street,
SYDNEY NSW 2000
AUSTRALIA
office: + 61 2 8264 3820
mobile: + 61 416 105 858
* sinclairj@powertel.com.au
**********************************************************************
PowerTel Limited, winners of
Broadband Wholesale Carrier of the year, CommsWorld
Telecomms Awards 2001
Best Emerging Telco, Australian Telecom Awards 2001
**********************************************************************
This email (including all attachments) is intended
solely
for the named
addressee. It is confidential and may contain
commercially sensitive
information. If you receive it in error, please let us
know by reply email,
delete it from your system and destroy any copies.
This email is also subject to copyright. No part of it
should be reproduced,
adapted or transmitted without the prior written consent
of the copyright owner.
Emails may be interfered with, may contain computer
viruses or other defects
and may not be successfully replicated on other systems.
We give no
warranties in relation to these matters. If you have any
doubts about
the authenticity of an email purportedly sent by us,
please contact us
immediately.
**********************************************************************
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:57 GMT-3