ARP PERMIT-NONCONNECTED IN CISCO FTD 6.2.3.x WORKAROUND

[Abheesh Kumar]

Symptoms

Getting error while creating arp permit-nonconnected as flex config in FTD running 6.2.3.x and can be able to create in earlier versions.

Work Around to fix this issue

Create a flex config text object and add variable as RP

Then create a flex config object " type A then insert the text object which we created earlier and type PERMIT-NONCONNECTED

then add this to flex config policy and assign to the device.

Tested this in 6.2.3.5 and its working.

Hope this will be useful for someone need to add this command when they needed to connect a non-connected subnet.

TAC submitted this issue as a defect with high-sev defect #CSCvn14276. so they can fix this in newer versions

-Abheesh

[sullivanr6@gmail.com]

Excellent find! thanks for sharing

[Marvin Rhoads]

Thanks for sharing. You might want to have a llok at the published bug and correct the syntax. It currently says:

Workaround:
1. Add a Text Object as rp.
Under to Objects > Object Management > Text Object.
2. Access to FlexConfig and insert the created variable to FlexConfig, it will be like the following;
r$rp permit-nonconnected

The last line should be:

a$rp permit-nonconnected

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvn14276

[Abheesh Kumar]

Hi Marvin,

I have created a$rp permit-nonconnected as flex config object and its working, shared feedback to TAC to correct syntax in bug portal for CSCvn14276 .

[Bill CARTER]

Great post. Worked for me!!