<div>
thanks joopv, 
 
What is PIX? Private Internet Exchange? A firewall? 
 
thanks donjohnston, 
I will post the show adjacencies.
</div>

<div>
PIX is what Cisco used to call their firewalls. Now they're called ASA's (Adaptive Security Appliances). 

</div>

<div>
I don't understand what the numbers in the parentheses mean under the sh adj command. ex (5) 
 
Does the adjacency table mean that a device with ip xx.xxx.24.209 is physically adjacent and can be reached by sending the packets to vlan interface 500? 
 
What do the receive and attached under the sh ip cef command mean? 
 
Does a packet have to match 10.xxx.9.0/24 exactly to be sent to GigabitEthernet9/48 
 
#sh ip int br | ex unassigned 
Interface &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;IP-Address &nbsp; &nbsp; &nbsp;OK? Method Status &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Protocol 
Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;xx.xxx..1.2 &nbsp; &nbsp; &nbsp;YES NVRAM &nbsp;up &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;up 
Vlan900 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;yyy.yy.192.2 &nbsp; &nbsp;YES NVRAM &nbsp;up &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;up 
GigabitEthernet9/47 &nbsp; &nbsp; &nbsp; &nbsp;10.xxx.8.10 &nbsp; &nbsp; YES NVRAM &nbsp;down &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;down 
GigabitEthernet9/48 &nbsp; &nbsp; &nbsp; &nbsp;10.xxx.9.10 &nbsp; &nbsp; YES NVRAM &nbsp;up &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;up 
 
#sh run 
interface Vlan1 
&nbsp;no ip address 
&nbsp;shutdown 
! 
interface Vlan500 
&nbsp;ip address xx.xxx.1.2 255.255.0.0 
! 
interface Vlan900 
&nbsp;ip address yyy.yy.xxx.2 255.255.255.0 
! 
router ospf 777 
&nbsp;log-adjacency-changes 
&nbsp;network xx.xxx.0.0 0.0.255.255 area 500 
&nbsp;network yyy.yy.xxx.0 0.0.0.255 area 500 
! 
ip nat inside source list 10 interface Vlan500 overload 
ip classless 
ip route 0.0.0.0 0.0.0.0 10.xxx9.1 
ip route 0.0.0.0 0.0.0.0 10.xxx.8.1 
ip route xx.0.0.0 255.0.0.0 xx.xxx.1.1 
ip route yyy.yy.0.0 255.255.0.0 yyy.yy.192.1 
 
 
#sh adjacency 
Protocol Interface &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Address 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..24.209(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..144.89(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..44.229(5) 
IP &nbsp; &nbsp; &nbsp; GigabitEthernet9/48 &nbsp; &nbsp; &nbsp; 10.xxx.9.1(7) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..72.65(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..24.17(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..56.49(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..44.36(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..144.152(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..45.37(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..72.71(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..45.34(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..44.34(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..16.30(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..73.71(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..27.21(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..144.158(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..72.69(5) 
IP &nbsp; &nbsp; &nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; xx.xxx..46.35(5) 
IP &nbsp; &nbsp; &nbsp; GigabitEthernet9/48 &nbsp; &nbsp; &nbsp; 10.xxx.9.4(5) 
 
#sh ip cef 
Prefix &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Next Hop &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interface 
0.0.0.0/0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 10.xxx.9.1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GigabitEthernet9/48 
0.0.0.0/32 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;receive 
10.192.9.0/24 &nbsp; &nbsp; &nbsp; attached &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GigabitEthernet9/48 
10.192.9.0/32 &nbsp; &nbsp; &nbsp; receive 
10.192.9.1/32 &nbsp; &nbsp; &nbsp; 10.xxx.9.1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GigabitEthernet9/48 
10.192.9.4/32 &nbsp; &nbsp; &nbsp; 10.xxx.9.4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GigabitEthernet9/48 
10.192.9.10/32 &nbsp; &nbsp; &nbsp;receive 
10.192.9.13/32 &nbsp; &nbsp; &nbsp;10.xxx.9.13 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;GigabitEthernet9/48 
10.192.9.255/32 &nbsp; &nbsp; receive 
11.0.0.0/8 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;11.xxx.1.1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Vlan500 
11.128.0.0/16 &nbsp; &nbsp; &nbsp; yyy.yy.192.1 &nbsp; &nbsp; &nbsp; &nbsp; Vlan900 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; yyy.yy.192.3 &nbsp; &nbsp; &nbsp; &nbsp; Vlan900 
11.136.0.0/16 &nbsp; &nbsp; &nbsp; yyy.yy.192.3 &nbsp; &nbsp; &nbsp; &nbsp; Vlan900 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 172.25.192.4 &nbsp; &nbsp; &nbsp; &nbsp; Vlan900 
11.192.0.0/16 &nbsp; &nbsp; &nbsp; attached &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Vlan500 
11.192.0.0/32 &nbsp; &nbsp; &nbsp; receive 
11.192.1.1/32 &nbsp; &nbsp; &nbsp; xx,xxx.1.1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Vlan500
</div>

<div>
Your output is different than I'm used to seeing. 
 
&gt;I don't understand what the numbers in the parentheses mean under the sh adj command. ex (5) 
 
The only thing I think of is the number in parentheses is the time remaining 
 
<a href="http://www.ciscosystems.com/en/US/docs/routers/7600/ios/12.1E/command/reference/r1.html#wp1080156" rel="ugc">http://www.ciscosystems.com/en/US/docs/routers/7600/ios/12.1E/command/reference/r1.html#wp1080156</a> 
 
&gt;Does the adjacency table mean that a device with ip xxx.xx.24.209 is &nbsp;physically adjacent and can be reached by sending the packets to vlan &nbsp;interface 500? 
 
Yes. 
 
&gt;What do the receive and attached under the sh ip cef command mean? 
 
Attached means the interface is attached to that network.&lt;br&gt;Receive is the network, broadcast and IP address for the attached network. 
 
&gt;Does a packet have to match 10.xxx9.0/24 exactly to be sent to GigabitEthernet9/48 
 
No. That's (in your case) a network. There will never be a packet with a destination address of 10.xxx.9.0 

</div>

<div>
I don't know if it is time remaining because the (5) never changes when I re-enter the comand &quot;show adjacency&quot;. 
 
I looked at the link you sent me and it had a show adjacency summary command: 
 
#sh adj summary 
Adjacency Table has 511 adjacencies 
&nbsp; Table epoch: 0 (511 entries at this epoch) 
 
&nbsp; Interface &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Adjacency Count 
&nbsp; EOBC0/0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1 
&nbsp; GigabitEthernet9/48 &nbsp; &nbsp; &nbsp; 3 
&nbsp; Vlan500 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 504 
&nbsp; Vlan900 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3 
 
What is interface EOBC0/0? 
 
I did not mean the packet had to match the network...I meant to ask does it have to match exactly the first 24 bits. Ex: 10.192.9.X
</div>

<div>
Routing table, CEF, it doesn't matter. It's always longest match first. 

</div>

<div>
<div class="content wysiwyg-content">
My understanding of routers is that they can use Distributed CEF, CEF, Fast switching and Process switching. 
 
Is the above routing or switching? 
 
If you use CEF then you need a FIB and AT tables? No CEF then no FIB or AT? 
 
A FIB appears to me to be a combination of the Route Table and the ARP cache. 
 
The AT table is confusing but the name seems to imply it is similar to a mac-address-table. 
 
I have tried reading about CEF many times but it is confusing because I don't understand the basics...The router starts off routing and then determines distinct flows of data and then starts switching using CEF? 
 
If a Router does not have CEF then no FIB and AT and all packets are Routed but not switched? 
 
I have looked at the FIB using the show ip cef and it makes sense but when I try to look at the AT table it appears blank or does not make sense to me. Maybe I am running the wrong command; I have ran something like sh ip cef adjacencies or something similar. 
 
Is CEF just offloading the routing from the CPU to the switching ASICS?
</div>
</div>

My understanding of routers is that they can use Distributed CEF, CEF, Fast switching and Process switching. 

Is the above routing or switching?

If you use CEF then you need a FIB and AT tables? No CEF then no FIB or AT?

A FIB appears to me to be a combination of the Route Table and the ARP cache.

The AT table is confusing but the name seems to imply it is similar to a mac-address-table.

I have tried reading about CEF many times but it is confusing because I don't understand the basics...The router starts off routing and then determines distinct flows of data and then starts switching using CEF?

If a Router does not have CEF then no FIB and AT and all packets are Routed but not switched?

I have looked at the FIB using the show ip cef and it makes sense but when I try to look at the AT table it appears blank or does not make sense to me. Maybe I am running the wrong command; I have ran something like sh ip cef adjacencies or something similar.

Is CEF just offloading the routing from the CPU to the switching ASICS?

What is the purpose of CEF and the FIB and AT tables

A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.

Switches / Hubs

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.

Routers

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.