IPSla or Track in Cisco ASA 5516x in Context

[Alex Ribas]

Hi all

I tried use ipla or track in context Cisco ASA 5516x

But I didn't find solution

My idea is;

We have 2 outside to Internet in the same context (internet)

I know it is working in Firewall Mode (Single) but in Context I didn't find solution

thank you

Any clue?

Alex

[Rob Ingram]

Hi @Alex Ribas 

IP SLA/Track is supported in multi-context, so I see no reason why it would be any different to normal.

What exact error do you get? Please provide your configuration.

What ASA software version are you running?

[Alex Ribas]

I Just changed the IP address to outside

But I didn't have option to ip sla or track (command that I mean)

Thank you

: Hardware: ASA5516
:
ASA Version 9.15(1)1 <context>
!
 

!
interface Port-channel1.27
no nameif
no security-level
no ip address

interface Port-channel1.400
nameif outside
security-level 0
ip address 1.1.1.10 255.255.255.0 standby 1.1.1.11
!
interface Port-channel1.450
nameif outside2
security-level 0
ip address 2.2.2.10 255.255.255.0 standby 2.2.2.11
!
pager lines 24
mtu outside 1500
mtu outside2 1500
no monitor-interface outside
no monitor-interface outside2
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
route outside 0.0.0.0 0.0.0.0 1.1.1.12 1
route outside2 0.0.0.0 0.0.0.0 2.2.2.12 10
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 sctp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
timeout conn-holddown 0:00:15
timeout igp stale-route 0:01:10
user-identity default-domain LOCAL
aaa authentication login-history
no snmp-server location
no snmp-server contact
crypto ipsec security-association pmtu-aging infinite
telnet timeout 5
ssh stricthostkeycheck
ssh timeout 5
ssh version 2
no threat-detection statistics tcp-intercept
dynamic-access-policy-record DfltAccessPolicy
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
no tcp-inspection
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect ip-options
inspect netbios
inspect rsh
inspect rtsp
inspect skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect tftp
inspect sip
inspect snmp
!
service-policy global_policy global
Cryptochecks

Cisco Adaptive Security Appliance Software Version 9.15(1)1 <context>
SSP Operating System Version 2.9(1.131)
Device Manager Version 7.15(1)150

Compiled on Fri 20-Nov-20 18:47 GMT by builders

FW03   up 20 hours 26 mins
failover cluster up 7 days 3 hours

Hardware: ASA5516

Licensed features for this user context:
Failover : Active/Active perpetual
Encryption-DES : Enabled perpetual
Encryption-3DES-AES : Enabled perpetual
Carrier : Disabled perpetual
AnyConnect Premium Peers : 0 perpetual
Other VPN Peers : 0 perpetual
AnyConnect for Mobile : Disabled perpetual
AnyConnect for Cisco VPN Phone : Disabled perpetual
Advanced Endpoint Assessment : Disabled perpetual
Botnet Traffic Filter : Disabled perpetual
Cluster : Enabled perpetual
Cluster Members : 2 perpetual
VPN Load Balancing : Enabled perpetual

Failover cluster licensed features for this user context:
Failover : Active/Active perpetual
Encryption-DES : Enabled perpetual
Encryption-3DES-AES : Enabled perpetual
Carrier : Disabled perpetual
AnyConnect Premium Peers : 0 perpetual
Other VPN Peers : 0 perpetual
AnyConnect for Mobile : Disabled perpetual
AnyConnect for Cisco VPN Phone : Disabled perpetual
Advanced Endpoint Assessment : Disabled perpetual
Botnet Traffic Filter : Disabled perpetual
Cluster : Enabled perpetual
VPN Load Balancing : Enabled perpetual

[Rob Ingram]

So you cannot configure something like this.........

sla monitor 1 
 type echo protocol ipIcmpEcho 1.1.1.12 interface outside
 threshold 1
 frequency 5
 sla monitor schedule 1 life forever start-time now
track 10 rtr 1 reachability
route outside 0.0.0.0 0.0.0.0 1.1.1.12 1 track 10

[Alex Ribas]

Nops

sla monitor 1

ERROR: % Invalid input detected at '^' marker

Not exist this commando in Context

[Rob Ingram · Accepted solution]

Actually I've re-checked the configuration guide Static route tracking is not supported in Multi-context mode.

Refer to the Unsupported features...

https://www.cisco.com/c/en/us/td/docs/security/asa/asa915/configuration/general/asa-915-general-config/ha-contexts.html?bookSearch=true#ID-2171-0000015b

[Alex Ribas]

Yes I read couple of times

thank you