LAN BASED FAILOVER - problem pinging interfaces

Unanswered Question
Dec 19th, 2008
User Badges:

hi there

im trying to configure lan based failover on ASA 5510 (which ive sucessfully created in test lab using asa5510) but there is this strange issue where i cant ping the e0/3 interface prior to confiuring the failover.


So far, ive created a vlan 41 on a cisco 2960switch and placed inter g0/12 (which is conencted to primary ASA e0/3 which i will used as the failover interface into that vlan. the ip add of e0/3 is 192.168.254.1/24


Then, ive placed inter g0/11 (which is connect to secondary asa inter e0/3) into vlan 41 with interface ip of 192.168.254.2/24.


Now prior to entrering the relevant failover commands, i should be able to ping at least the e0/3 interfaces on both ASA's? well i cant.


Ive checked the speed and duplex settings on asa's and switch and all set to 100MB full.


any ideas?


sh vlan brief output:

41 VOICE_FAILOVER active Gi0/11,Gi0/12


sh interface status


Gi0/11 connected to SupAS connected 41 full 100 10/100/1000BaseTX


Gi0/12 connected to SuppA connected 41 full 100 10/100/1000BaseTX


sh interface e0/3 (ASA 1)

Interface Ethernet0/3 "", is up, line protocol is up

Hardware is i82546GB rev03, BW 100 Mbps

Full-Duplex(Full-duplex), 100 Mbps(100 Mbps)

Available but not configured via nameif

MAC address 001e.f762.c8b3, MTU not set

IP address 192.168.254.1, subnet mask 255.255.255.0

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

0 L2 decode drops

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 babbles, 0 late collisions, 0 deferred

0 lost carrier, 0 no carrier

input queue (curr/max blocks): hardware (4/0) software (0/0)

output queue (curr/max blocks): hardware (0/0) software (0/0)



sh interface e0/3 (ASA sec)

Interface Ethernet0/3 "", is up, line protocol is up

Hardware is i82546GB rev03, BW 100 Mbps

Full-Duplex(Full-duplex), 100 Mbps(100 Mbps)

Available but not configured via nameif

MAC address 001e.f762.9c8b, MTU not set

IP address 192.168.254.1, subnet mask 255.255.255.0

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

0 L2 decode drops

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 late collisions, 0 deferred

0 input reset drops, 0 output reset drops

input queue (curr/max packets): hardware (0/16)

output queue (curr/max packets): hardware (0/0)


Also, ive noticed that although the interfaces are up and up, the 192.168.254.0/24 network is not showing as connected under the sh route command.


what other info would be needed? As i said the failover conmmands havent been entered yet, i want to undastand why i cant ping the interfaces e0/3.


thanks




  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
solpandor Fri, 12/19/2008 - 08:19
User Badges:

hi all


got it. It was to do with the fact that I didnt enter the nameif command on the e0/3 interfaces. i thought that was optional (apparantly not )


so looks like you need the nameif command as well for the network to show as connected under sh route





Actions

This Discussion