without the factory default), all switch ports are in VLAN 1. Out of the box, or with the configure factory-default command, the ASA 5505 is configured thusly: VLAN

If the traffic needs to go to another VLAN, the ASA applies the security policies (ACLs, interface security levels etc) to decide whether or not to forward the traffic to the destination VLAN. Switch ports on the same VLAN can communicate with each other. You assign the switch ports to logical VLAN interfaces. There are 8 FastEthernet switch ports that forward traffic at Layer 2. If the customerвЂ™s asking for failover and content checking or IPS, then weвЂ™re already looking at a network with more traffic than a 5505 can handle.Д¬onfiguration of the 5505вЂ™s interfaces is a wee bit different from the bigger models because the 5505 is basically a switch with VLANs. The deciding factors are usually price and capacity. In larger businesses with hub-and-spoke VPN topologies, I tend to deploy the higher-end ASA models at the main office (the hub), and only use the 5505 model at the remote offices (the spokes). Firewall for customer rack at a colo so that the redundant servers at the colo can establish a site-to-site VPN with the main office.Firewall for remote usersвЂ™ home offices so that they can establish a site-to-site VPN with the main office.Firewall for branch offices that need to have a site-to-site VPN with the main office.Usually just a simple topology that can be divided into LAN/DMZ/Public. Firewall for small businesses that need packet filtering and VPN capability for remote users.Typical scenarios where IвЂ™ve deployed 5505 models: The material differences between the 5505 and its larger brethren are really price, traffic capacity and physical expansion (number of ports, add-on cards etc). Small footprint, good price point for SoHo environments. The Cisco ASA 5505 is the lowest-end ASA.

Configuration cisco asa 5505