topic Re: migrating 5505 to 5506-X in Network Security

migrating 5505 to 5506-X

med.rebou — Fri, 21 Feb 2020 16:40:31 GMT

I would like to change my cisco asa 5505 (ios 7.4) with another cisco asa 5506-x, and I can not configure it is quite different,can you help me please

here is the config of my ASA 5505:

!
hostname xxx
domain-name xxxx
enable password 1234
passwd 1234
names
!
interface Vlan1
nameif inside
security-level 100
ip address x.x.x.1 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address y.y.y.2 255.255.255.0
!
interface Vlan3
shutdown
no forward interface Vlan1
nameif dmz
security-level 50
no ip address
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
boot system disk0:/asa724-k8.bin
ftp mode passive
dns server-group DefaultDNS
domain-name xxxx
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object-group network obj_any
access-list inside_access_in extended permit ip any any log debugging
access-list outside_access_in extended permit icmp any any log debugging
access-list outside_access_in extended permit ip any any

access-list outside_nat_static_9 extended permit ip host y.y.y.210 x.x.0.0 255.255.255.0
access-list outside_nat_static_10 extended permit ip host y.y.y.200 x.x.0.0 255.255.255.0
access-list outside_nat_static_11 extended permit ip host y.y.y.220 x.x.0.0 255.255.255.0
access-list outside_nat_static_12 extended permit ip host y.y.y.240 x.x.0.0 255.255.255.0
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
mtu dmz 1500
icmp unreachable rate-limit 1 burst-size 1
icmp permit any inside
icmp permit any outside
asdm image disk0:/asdm-524.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0

static (inside,outside) y.y.y.20 x.x.x.2 netmask 255.255.255.255
static (inside,outside) y.y.y.32 x.x.x.32 netmask 255.255.255.255
static (outside,inside) z.z.z.150 access-list outside_nat_static_9
static (outside,inside) z.z.z.10 access-list outside_nat_static_10
static (inside,outside) y.y.y.33 x.x.x.33 netmask 255.255.255.255
static (outside,inside) z.z.z.140 access-list outside_nat_static_11
static (outside,inside) z.z.z.151 access-list outside_nat_static_12
access-group inside_access_in in interface inside
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 y.y.y.4 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 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
aaa authentication ssh console LOCAL
http server enable
http x.x.x.0 255.255.255.0 inside
http y.y.y.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
telnet 0.0.0.0 0.0.0.0 outside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 5
console timeout 0
dhcpd auto_config outside
!
dhcpd address x.x.x.2-x.x.x.33 inside
dhcpd dns y.y.y.210 y.y.y.140 interface inside
dhcpd wins y.y.y.210 y.y.y.150 interface inside
dhcpd lease 691200 interface inside
dhcpd domain xxx interface inside
dhcpd enable inside
!

class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp

crypto key generate rsa modulus 512

Re: migrating 5505 to 5506-X

balaji.bandi — Fri, 18 Jan 2019 06:25:05 GMT

Since this is device to device migration.

Copy the configuraiton to new device in test Environment and compare all the configuration is same like old one. move the device to next to old device, in the change windows accepted by business, swap the cables and test it. if any issues capture the all the logs in related to the issue in the given maintenance window. role back to old device to restore the services.

if all working, keep monitoring next couple of days no incident reported. do not remove old device until all stable.

here is another good guide for reference :

https://www.petenetlive.com/KB/Article/0001091

Re: migrating 5505 to 5506-X

Marius Gunnerud — Fri, 18 Jan 2019 11:41:33 GMT

This is not a simle copy paste of the configuration. ASA5506 does not support SVI so if you are using the ASA5505 as a switch also, you would need to configure BVI interfaces on the ASA5506 instead of VLAN interfaces. You will also need to change the NAT statements to object based NAT statements (XLATE) and the access lists need to specify the real destination IP not the NATed IP.

Re: migrating 5505 to 5506-X

balaji.bandi — Fri, 18 Jan 2019 08:49:27 GMT

Appologies i may not have made clear in the last post.

when i mean copy to new device ( convert from old to new by changing the syntax, and checking the compatable commands work on new device)

@Marius Gunnerud thanks for correting this.

Re: migrating 5505 to 5506-X

Marvin Rhoads — Fri, 18 Jan 2019 11:26:31 GMT

I would simply manually convert each relevant section. There are only two active interfaces - outside and inside, a couple of static NATs and a dynamic interface NAT.

The source config looks like it might be a lab. I say that because it has an acl outside_in to allow ip any any. If that's the case then it's a good learning experience.

Re: migrating 5505 to 5506-X

vsurresh — Fri, 18 Jan 2019 14:58:09 GMT

Adding to Marius comments, If you are going to use the new ASA 5506 for pure firewall purposes then BVI is not needed.
In regards to NAT conversion, please refer to this link https://www.tunnelsup.com/nat-converter/
Also, a good idea to disable telnet and change the console timeout to anything other than 0 (0 timeout - unlimited)

Let me know if you need further help.

Regards

Re: migrating 5505 to 5506-X

med.rebou — Fri, 18 Jan 2019 22:56:31 GMT

I tried to convert the config but I can not connect to the EXCHANGE server.
pinging the ip address of the server is done without problem but I can not
ping the server name. it may be a dns or nat problem.

Re: migrating 5505 to 5506-X

Marvin Rhoads — Sat, 19 Jan 2019 02:37:46 GMT

First off, ping (icmp echo request and reply) is not a good way to test firewall connectivity since it is a stateless protocol.

Second, the ping failure can be due to a couple of things. Your original config had:

access-list inside_access_in extended permit ip any any log debugging
access-list outside_access_in extended permit icmp any any log debugging
access-list outside_access_in extended permit ip any any

So there is only ip (not icmp) on the insice_access_in ACL. Either add an entry to allow icmp or remove that ACL altogether since it really doesn't do anything (except inadvertently block non-IP traffic).

You should also add "inspect icmp" to your default class-map.

Re: migrating 5505 to 5506-X

med.rebou — Sat, 19 Jan 2019 08:29:27 GMT

I tried to convert the config but I can not connect to the EXCHANGE server.

pinging the ip address of the server is done without problem but I can not ping the server name. it may be a dns or nat problem.

Re: migrating 5505 to 5506-X

Marius Gunnerud — Mon, 21 Jan 2019 09:01:45 GMT

What do you get if you do an nslookup <server name> (replace server name with the actual name of the server) from the command prompt on your PC? If it resolves to the correct IP then there is an issue with NAT, if it does not resolve to the correct IP or does not resolve at all, then this is an issue with DNS.

Re: migrating 5505 to 5506-X

balaji.bandi — Mon, 21 Jan 2019 17:00:03 GMT

yes post the full configuration or check the DNS allowed list and DNS configuration, make sure you should be able to resolve the DNS names. as suggested.

Re: migrating 5505 to 5506-X

med.rebou — Fri, 01 Feb 2019 17:11:21 GMT

thank you for your reply?

can you translate a line of access list and nat please?

Re: migrating 5505 to 5506-X

med.rebou — Fri, 01 Feb 2019 17:45:51 GMT

when I enter nslookup <exchange server name> I get the ip from my AD server

Re: migrating 5505 to 5506-X

med.rebou — Fri, 01 Feb 2019 17:56:43 GMT

thank you for your advice, I am totally blocked. when i copy the config to my new asa, i correctly configured the interfaces inside and outside but the nat commands give me error i can not convert them

Re: migrating 5505 to 5506-X

Marvin Rhoads — Fri, 01 Feb 2019 18:03:44 GMT

Can you share what you have so far as a running-config on the new device?

Then show us what error you receive when trying to configure your nat statements.

Re: migrating 5505 to 5506-X

med.rebou — Sat, 02 Mar 2019 17:12:00 GMT

please excuse me, I could not solve the problem. I found a solution that is based on the migration of cisco asa 5505 8.2 to 8.3

this solution allowed me to transform my configuration from 8.2 to 8.3 which is compatible with ASA 5506 but I still have one problem: I can not yet connect to my exchange server,

Re: migrating 5505 to 5506-X

Marvin Rhoads — Sun, 03 Mar 2019 03:54:27 GMT

@med.rebou

Please summarize your problem with the detail needed to troubleshoot.

a. What's the Exchange server address.

b. What's the source address (or addresses in the case of public Internet access) from which you expect to be able to reach it?

Please attach the current running-config of your ASA 5506.