cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1731
Views
0
Helpful
9
Replies

Routing issue. Please help me

KakaoTalk_20191002_134537442.jpg

 

The ASA does not seem to be doing ROUTING.

OA and FA are Track config of each other. But in FA, sla is down.

The IP 94 and 247 bands must be able to communicate with each other.

I attach the CONFIG_SCRIPT.

Do you know the cause ??

Please help me.

I did not find the cause.

I only believe you.

2 Accepted Solutions

Accepted Solutions

I solved the problem.

I set ROUTING to 32BIT so that the TRACK state could be UP.

ip route 192.168.94.1 255.255.255.255 192.168.247.11


But I don't know if this is a normal solution.


Because OA does not have a problem with TRACK even if 32BIT ROUTING is not done.

View solution in original post

Hello,

 

odd indeed. I could not find anywhere that the SLA needs a static host route. I also could not find any bugs. Either way, if it works that way, leave it as is, obviously...

View solution in original post

9 Replies 9

Deepak Kumar
VIP Alumni
VIP Alumni

Hi,

 

Regards,
Deepak Kumar,
Don't forget to vote and accept the solution if this comment will help you!

We should use Reduntdent.

 

I think there must be another reason.

Hello,

 

looking at your configurations, I cannot figure out what you are trying to accomplish with your IP SLA, and what you are actually tracking. I guess it would help if you could fill in the blanks below:

 

Incheon_OA_BB_1

Primary route to where (IP and device) ?

Secondary route to where (IP and device) ?

SLA ping to where (IP and device) ?

!

Incheon_OA_BB_2

Primary route to where (IP and device) ?

Secondary route to where (IP and device) ?

SLA ping to where (IP and device) ?

!

Incheon_FA_BB_1

Primary route to where (IP and device) ?

Secondary route to where (IP and device) ?

SLA ping to where (IP and device) ?

!

Incheon_FA_BB_2

Primary route to where (IP and device) ?

Secondary route to where (IP and device) ?

SLA ping to where (IP and device) ?

 

 

Hello,

 

post the output of:

 

Incheon-Dis-FW(config)# show interface redundant 1

 

and 

 

Incheon-Dis-FW(config)# show interface redundant 2

Incheon-Dis-FW# sh int redundant 1
Interface Redundant1 "OA", is up, line protocol is up
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
Input flow control is unsupported, output flow control is off
MAC address 683b.78df.0bb4, MTU 1500
IP address 192.168.94.11, subnet mask 255.255.255.0
196966197 packets input, 16759102077 bytes, 0 no buffer
Received 1331718 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
665681 L2 decode drops
195222292 packets output, 30260296858 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (3972/1912)
output queue (blocks free curr/low): hardware (4094/2019)
Traffic Statistics for "OA":
193579464 packets input, 13216079152 bytes
195222292 packets output, 26722007944 bytes
69398 packets dropped
1 minute input rate 610 pkts/sec, 40347 bytes/sec
1 minute output rate 613 pkts/sec, 84346 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 611 pkts/sec, 40393 bytes/sec
5 minute output rate 613 pkts/sec, 84422 bytes/sec
5 minute drop rate, 0 pkts/sec
Redundancy Information:
Member GigabitEthernet1/1(Active), GigabitEthernet1/2
Last switchover at 11:33:00 KST Sep 27 2019

Incheon-Dis-FW# sh int redundant 2
Interface Redundant2 "FA", is up, line protocol is up
Hardware is Accelerator rev01, BW 1000 Mbps, DLY 10 usec
Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
Input flow control is unsupported, output flow control is off
MAC address 683b.78df.0bba, MTU 1500
IP address 192.168.247.11, subnet mask 255.255.255.0
202562162 packets input, 30431700651 bytes, 0 no buffer
Received 3272516 broadcasts, 0 runts, 0 giants
9996 input errors, 0 CRC, 9996 frame, 0 overrun, 0 ignored, 0 abort
0 pause input, 0 resume input
1678544 L2 decode drops
192926602 packets output, 16662263481 bytes, 0 underruns
0 pause output, 0 resume output
0 output errors, 0 collisions, 0 interface resets
0 late collisions, 0 deferred
0 input reset drops, 0 output reset drops
input queue (blocks free curr/low): hardware (3952/1909)
output queue (blocks free curr/low): hardware (4094/2047)
Traffic Statistics for "FA":
196737483 packets input, 26754857183 bytes
192926602 packets output, 13178004997 bytes
77696 packets dropped
1 minute input rate 619 pkts/sec, 84032 bytes/sec
1 minute output rate 609 pkts/sec, 40226 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 617 pkts/sec, 84060 bytes/sec
5 minute output rate 609 pkts/sec, 40260 bytes/sec
5 minute drop rate, 0 pkts/sec
Redundancy Information:
Member GigabitEthernet1/8(Active), GigabitEthernet1/7
Last switchover at 11:34:37 KST Sep 27 2019

Hello,

 

the FA devices seem to be 3850 switches with IP routing enabled, what are the OA devices ?

OA = C4507

I solved the problem.

I set ROUTING to 32BIT so that the TRACK state could be UP.

ip route 192.168.94.1 255.255.255.255 192.168.247.11


But I don't know if this is a normal solution.


Because OA does not have a problem with TRACK even if 32BIT ROUTING is not done.

Hello,

 

odd indeed. I could not find anywhere that the SLA needs a static host route. I also could not find any bugs. Either way, if it works that way, leave it as is, obviously...