• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

EIGRP Advertisement Problem

M

Mabrito

Supreme [H]ardness
Joined
Dec 24, 2004
Messages
7,004
Working on setting up my learning environment with and I have 3 layer 3 switches.

I have two switches as the "Distribution" layer (SW1 and SW2) and then the final switch for the "Access" layer (SW3).

On SW1 and SW2 I created 3 VLAN's via VLAN interfaces (10,20,30) and have them in a HSRP configuration between SW1 and SW2. SW2 contains a connection to a ASA for outside internet access and is on its own link.

I am having issues advertising the default route from SW2 to SW1. Basically on SW2, I created the 3 VLAN interfaces and gave them there assigned IP and the global standby IP for HSRP. I also created the same 3 VLAN interfaces on SW1 with there own assigned IP and the same global standby IP. I then created a trunk setup on a physical interface on both switches and trunked the 3 VLAN's.

On SW2, I then have a interface for the connection to the ASA and created a default static route to the IP on the ASA.

In the EIGRP configuration, I am advertising the 3 assigned IP's of the VLAN interfaces (network x.x.x.x 0.0.0.0) and then have a Redistribute Static command as well. I am not advertising the Standby IP as I know your now suppose to.

SW1 in return is receiving a Gateway of Last Resort of one of the assigned VLAN interface IP's of SW2. In the routing table, it has 3 entries for the static 0.0.0.0 any route and they are the 3 assigned VLAN interface IP's on SW2. I do not see any routing table entries for the IP subnet of the ASA link.

Not sure whats going on here...would anyone have any input?
 
Here is my answer... ASA's suck donkey balls and I mean. Crap.

Okay now before going further into why ASA sucks monkey sack please upload your configuration, sterilized of course, and we can further assist you as a community. Be forewarned however [HF] can be a real intersting challenge to get even the most LIMITED amount of Cisco knowledge out of.

I will do my best as I can when I check the site.
 
You must log in or register to reply here.
Back
Top