I don't know if it works with VRF's but one hack could be to create
a second unique AS eigrp process for that interface(network). Use that
AS for
it's remote router. You can then redistribute between the two and
filter accordingly.
-Rich
-Message: 2
Date: Wed, 16 Jan 2008 01:10:50 -0800
Isnt't there some trick around this like putting no ip route-cache
under the interface to force the process switching. I suppose you only
want to do this for the short debugging time window.
-Rich
--
Hi,
On Fri, Jan 11,
-Original Message-
From: Collins, Richard (SNL US) [mailto:[EMAIL PROTECTED]
Sent: Friday, December 14, 2007 5:07 PM
To: cisco-nsp@puck.nether.net
Cc: [EMAIL PROTECTED]
Subject: RE: Re: [c-nsp] Bridging two VLANs together
Hello Frank,
I think that I will have a chance to lab this up next week.
I
here.
Rich
-Original Message-
From: ext Frank Bulk [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 13, 2007 7:21 PM
To: Collins, Richard (SNL US); cisco-nsp@puck.nether.net
Subject: RE: Re: [c-nsp] Bridging two VLANs together
The command bridge 2 protocol ieee is not available
Hello,
If I recall correctly, fall-back bridging is only for non-ip traffic.
Though I haven't tested it I believe your configuration with the
addition
of bridge 2 protocol ieee should work.
Rich
I believe what you propose (fall-back bridging) will work,
but will be performed in software.
I tried testing this with a 2 trunk etherchannel between two switches.
Host1 and Host2 connected to SW1 (3560)
Host3 connected to SW2 (3560)
I used the secondary VLAN 400 as community for all these hosts.
I found I could create a vlan filter list on SW2 which blocked Host1
Host3
but allowed
Looking at your IP addressing, I would say that you have to do your
natting
on the outside address of the ASA 5510 or Main router and not on the
1841.
Rich
From: Wycliffe Bahati [EMAIL PROTECTED]
Subject: Re: [c-nsp] Routing problem with Cisco 1841
To: cisco-nsp@puck.nether.net
Message-ID:
Yes I think that you have to use a standard access-list on the VTY. I
believe to only allow ssh you could just allow ssh as a transport.
router(config)#line vty 0 4
router(config-line)#transport input ?
acercon Remote console for ACE-based blade
all All protocols
lat DEC LAT
Hi Michael,
I was looking at the Cisco document - Nat on a stick.
I understand you should have the ip nat inside on your internal
interface and also the PBR.
The loopback2 will be the ip nat outside and not your WAN interface.
For example:
int eth0/0
ip nat inside
ip policy route-map
If you take the IRB approach I think that something like this would work
- and
only one bridge group.
Router A config:
hostname RouterA
!
ip cef
bridge irb
!
frame-relay switching
!
interface FastEthernet0/0
duplex auto
speed auto
bridge-group 1
!
interface Serial0/0
no ip address
You were right about the combination of commands. Here is a good link
ftp://ftpeng.cisco.com/ipmulticast/config-notes/upnp-note.txt
I wouldn't know about the last part of your question.
-Richard
Message: 6
Date: Mon, 23 Jul 2007 14:08:51 +0100
From: Phil Mayers [EMAIL PROTECTED]
Subject:
Yes I can confirm that I am seeing the same effect on our
Sup720/PFC3BX with SXF8. I am seeing all routes with community
1234:1002 and none with both 1234:1001 1234:1002
-Rich
Date: Fri, 13 Jul 2007 17:45:29 +0200 (CEST)
From: Blake Willis [EMAIL PROTECTED]
Subject: [c-nsp] route-map
Though it is not exactly your question you can always use the
neighbor x.x.x.x local-as 2ndAS [no-prepend] to spoof a different AS to
one peer.
Rich
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex Haan
Sent: Tuesday, July 03, 2007 10:34 AM
To:
It might be useful to see additional information such as:
c3845#show ip igmp interface gi0/1.180
c3845#show ip igmp groups
and maybe a debug of one of the host multicast groups:
c3845#debug ip igmp x.x.x.x
-Rich
Message: 2
Date: Wed, 27 Jun 2007 15:55:04 +0300
From: Matti Saarinen [EMAIL
So I suppose the opposite side was set at the same time to either
channel-group 10 mode [active or passive] for LACP?
What about additionally setting..
metro2.tor-Front[760(config-if)#channel-protocol lacp
I can't test this myself but saw the configuration option.
-Rich
Date: Sat, 05 May
On our 7600 I could run this manual command:
SUP720#redundancy force-switchover
I'm not sure about a permanent startup configuration.
-Rich
Message: 1
Date: Thu, 26 Apr 2007 14:26:26 +0800
From: Affandi Indraji [EMAIL PROTECTED]
Subject: [c-nsp] Catalyst 6500 Active and Standby Supervisor
16 matches
Mail list logo
