cisco packet switching order

This Lab setup i was trying to understand the Routing TCP/IP vol 1 - cisco packet switching order.



In this setup if we enable the debug ip packet on the R1 and see whether packet transferred between Host 1 &  Host 2 ? lets ping from Host2 to Host1
mm execpt some broadcast packet nothing in the debugging output why ?

R1#debug ip packet
IP packet debugging is on
R1#
*Mar 1 00:15:00.823: IP: s=0.0.0.0 (FastEthernet0/0),
d=255.255.255.255, len 576, rcvd 2
R1#
*Mar 1 00:15:03.835: IP: s=0.0.0.0 (FastEthernet0/0),
d=255.255.255.255, len 576, rcvd 2
R1#
*Mar 1 00:15:06.839: IP: s=0.0.0.0 (FastEthernet0/0),
d=255.255.255.255, len 576, rcvd 2
R1#
*Mar 1 00:15:29.907: IP: s=0.0.0.0 (FastEthernet0/0),
d=255.255.255.255, len 576, rcvd 2
R1#
*Mar 1 00:15:32.911: IP: s=0.0.0.0 (FastEthernet0/0),
d=255.255.255.255, len 576, rcvd 2
R1#
*Mar 1 00:15:35.911: IP: s=0.0.0.0 (FastEthernet0/0),
d=255.255.255.255, len 576, rcvd 2


answer is
ip packet debugging only shows the packet transferred through packet switching.

Lets try further:
Lets change the processing to process switching on the R1 fa0/0 which is facing 192.168.1.2 Host. to disable cef we can use following command.


R1(config)#int fa0/0
R1(config-if)#no ip route-cache ?
cef Enable Cisco Express Forwarding
flow Enable Flow fast-switching cache
policy Enable fast-switching policy cache for outgoing

packets
same-interface Enable fast-switching on the same interface
R1(config-if)#no ip route-cache cef
R1(config-if)#no ip route-cache

Lets try to ping from 192.168.3.2 to 192.168.3.1


R1#
*Mar 1 00:36:30.131: IP: tableid=0, s=192.168.1.2 (FastEthernet0/0), d=192.168.3.2 (FastEthernet0/1), routed via FIB
*Mar 1 00:36:30.131: IP: s=192.168.1.2 (FastEthernet0/0), d=192.168.3.2 (FastEthernet0/1), g=192.168.2.2, len 84, forward
R1#
R1#
R1#
R1#


mmm .. only one packet shown here others ? above output shows two behaviors:

when the inbound is Process switching and outboud CEF / fast switching the resulting switching method will be Fastswitching that is the output shown here the first packet process switched as the expected behavior for fast switching

there is not packet shown as the src 192.168.3.2 because that stage the processing will happen via CEF( if inbound CEF & outbound process / Fast switching method CEF)

summary :

1) If the inbound is CEF switching method will be CEF
2) if the inbound is Process and the outbound is CEF / Fast resulting switching will be Fastswitching
3) if the inbound is Fast and outbound is CEF resulting will be Fast
4) if the inbound is Fast and outbound is Process resulting will be Process

There are exemption list we need to consider.

Reference : Table 3.1 Chapter 3 - routing tcp/ip vol 1 2nd edition.

Comments

Post a Comment

Popular posts from this blog

l2tpv3 configuration reference

Image
Reference Comparing , Designing and Deploying VPNs chap - 02 : L2TPv3 is the enhanced version of L2TPv2 protocol. Mikrotik uses L2TPv2 i suppose but it offer another similar tunneling mechanism as EOIP. L2TPv3 in cisco provides Pseudo-wire services to the customer. L2TPv3 only require the IP connectivity between peers but it can transport Ethernet, 802.1Q , HDLC, PPP framerelay etc. Advantage over MPLS is the customer having the full control of their routing domain. L2TP depolyment methods having 3 topologies LAC - LNS , LNS - LNS , LAC - LAC Following Diagram explain simple LAC - LAC L2TPv3 setup. It uses two types of messages: control connection messages - used for signaling between LCEs session data messages - Used to transport layer 2 protocols and connections Data channel Message Header having Session ID & cookie to correctly associate with the tunnel Deploying dynamic Pseudowires session 1) configure CEF - Its default in IOSs now. 2) configure a loopback in
Read more

mikrotik queue tree - Per connection queuing.

Image
One of the cool feature on Mikrotik queuing is Per Connection Queuing . we can equally distribute the bandwidth among Number of users.[1] This setup explores the per connection queuing in the congestion situation and how to utilize the priority queuing features. [Please note Mikrotik Queue lowest priority value have highest priority eg: queue priority 7 traffic gets highest preference over queue priority 8  ] In this test setup 192.168.92.50 and 51 given 512Kbps per connection queuing(PCQ) Priority 6 . 192.168.52 and 54 placed under 256Kbps PCQ (Priority 8) and further youtube users given 384Kbps irrespective to the queue they are currently placed ( FIFO) . 1) Bridge setup - " Don't forget to enable the bridge firewall :) " /interface bridge add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes comment="" disabled=no forward-delay=15s l2mtu=1522 \ max-message-age=20s mtu=1500 name=br_traffic_shaper priority=0x8000 protocol-mode=none
Read more

Decoding BGP Notification Error

Following Log messages are normal in the IX scenario but decode the error message is quite interesting: We will see why this error message popped up : : %BGP-3-NOTIFICATION: sent to neighbor 10.10.194.236 2/7 (unsupported/disjoint capability) 0 bytes  FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0039 0104 xx0D 00B4 C06A 1102 1C02 0601 0400 0200 0102 0280 0002 0202 0002 0246 0002 0641 0400 00C4 0D its a raw hex out  of the BGP open message and starts from the marker  16byte FF so the actual output starts from 0039  2 byte length value : 00 39 - 57 1 byte Type : 01 open message 1 byte Version : 04 2 byte ASN : xx0D  [ modified to remove the relevant information ] 2 byte holdtime : 00 B4 - 180 Seconds 4 byte BGP identifier : C06A 1102 [ modified ] 1 byte Optional parameter length : 1C   - 28 bytes Refer RFC: http://tools.ietf.org/html/rfc5492 http://tools.ietf.org/html/draft-ietf-idr-ext-opt-param-02 http://www.iana.org/assignments/capability-codes/capability-c
Read more