Re: HSRP on MSFCs with DECnet [7:34828]

2002-02-09 Thread Priscilla Oppenheimer

Sorry. It's not an answer. ;-) I was wondering if you found an answer to 
this interesting quesiton, however. There may be no other solution than to 
use the BIA and rely on gratuitous ARP? (Well, you could get rid of DECnet 
or try to isolate it to a pocket of the network. That could be a bit 
drastic, though. You probably have some important applications that use it.)

Priscilla

At 03:11 AM 2/8/02, Caplan M wrote:
>Hi,
>
>I'm working with the following scenario.
>
>
> msfc1 msfc2
> ip -10.1.1.1  ip 10.1.1.2
> DECnet - 1.1  DECnet 1.2
> |   HSRP - 10.1.1.3 |
> |   |
>-
>   |   |
>IP hosts DECnet hosts
>
>I'm putting together a design using 2 6509s each with MSFCs. I want to
>provide IP redundancy via HSRP, but also run DECnet on both VLAN interfaces.
>The virtual MAC address problem of HSRP interacting with DECnet can be
>solved using 'standby use-bia' command. However I would prefer not to rely
>on the 'gratuitous arp' solution for my IP hosts; I dont know if they are
>all compliant.
>
>A better solution for a normal router is to use sub interfaces and the scope
>command, say a 2620. That way, I could configure IP on one sub-interface,
>and DECnet on another sub-interface. This would mean DECnet hosts could talk
>happily to their DR using the DEC aa-00-04-00-xx-xx MAC address, while the
>IP hosts could talk to the Cisco OUI virtual mac address - ie HSRP would
>only be configured on one of the subinterfaces
>
>eg:
>
>int fa0.1
>ip addr 10.1.1.1 255.255.255.0
>standby 1 ip 10.1.1.3 pre
>
>int fa0.2
>decnet cost 10
>
>But I dont see how I can do this trick with an MSFC. You cant split a VLAN
>interface into sub-interfaces.
>
>So how do I make a VLAN interface talk DECnet with aa-00-04 MAC address, and
>also respond to the normal HSRP cisco MAC address.
>
>Any ideas ? I really dont want to rely on gratuitous ARP. I'm sure that
>anything you can do with a 2620, you should be able to to at least as good
>with 6500s and MSFC !!
>
>Thanks in advance
>
>Mark


Priscilla Oppenheimer
http://www.priscilla.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=34999&t=34828
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



HSRP on MSFCs with DECnet [7:34828]

2002-02-08 Thread Caplan M

Hi,

I'm working with the following scenario.


msfc1 msfc2
ip -10.1.1.1  ip 10.1.1.2
DECnet - 1.1  DECnet 1.2
|   HSRP - 10.1.1.3 |
|   |
-
  |   |
IP hosts DECnet hosts
  
I'm putting together a design using 2 6509s each with MSFCs. I want to
provide IP redundancy via HSRP, but also run DECnet on both VLAN interfaces.
The virtual MAC address problem of HSRP interacting with DECnet can be
solved using 'standby use-bia' command. However I would prefer not to rely
on the 'gratuitous arp' solution for my IP hosts; I dont know if they are
all compliant.

A better solution for a normal router is to use sub interfaces and the scope
command, say a 2620. That way, I could configure IP on one sub-interface,
and DECnet on another sub-interface. This would mean DECnet hosts could talk
happily to their DR using the DEC aa-00-04-00-xx-xx MAC address, while the
IP hosts could talk to the Cisco OUI virtual mac address - ie HSRP would
only be configured on one of the subinterfaces

eg:

int fa0.1
ip addr 10.1.1.1 255.255.255.0
standby 1 ip 10.1.1.3 pre

int fa0.2
decnet cost 10

But I dont see how I can do this trick with an MSFC. You cant split a VLAN
interface into sub-interfaces.

So how do I make a VLAN interface talk DECnet with aa-00-04 MAC address, and
also respond to the normal HSRP cisco MAC address.

Any ideas ? I really dont want to rely on gratuitous ARP. I'm sure that
anything you can do with a 2620, you should be able to to at least as good
with 6500s and MSFC !!

Thanks in advance

Mark



Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=34828&t=34828
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]