Lectures notes for 2010 - KTH
Lectures notes for 2010 - KTH Lectures notes for 2010 - KTH
Cisco’s NetFlow Switching Routing Table Access List Queuing Prioity Accounting Data 1st Packet Switching Tasks Security Tasks Queuing Tasks Accounting Tasks 2nd, 3rd, … Packets NetFlow Cache NetFlow Switching Tasks NetFlow Statistics NetFlow Data Export Figure 17: Cisco’s NetFlow Switching Maguire Cisco’s NetFlow Switching 7: 61 of 70 maguire@kth.se 2010.03.21 Internetworking/Internetteknik
Flows A flow is defined as a “uni-directional stream of packets between a given source network-layer address and port number and a specific destination network-layer address and port number”. Since many application use well known transport-layer port numbers, it is possible to identify flows per user per application basis. There is a well defined Netflow Switching Developer’s Interface which allows you to get the statistics concerning the NetFlow cache and the per flow data (the later gives you essentially billing records). A general introduction to NetFlow Switching is available at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/switch_c/xcprt3/xcovntfl.htm Maguire Flows 7: 62 of 70 maguire@kth.se 2010.03.21 Internetworking/Internetteknik
- Page 437 and 438: Routing Algorithms • Static vs. D
- Page 439 and 440: Routing Information Protocol (RIP)
- Page 441 and 442: When are routes sent? Solicited res
- Page 443 and 444: Count to Infinity C network 1 netwo
- Page 445 and 446: Triggered updates and Hold-Downs To
- Page 447 and 448: Why would anyone use RIP? After all
- Page 449 and 450: IGRP Metrics • a vector of metric
- Page 451 and 452: IGRP Default Gateway Rather than us
- Page 453 and 454: Open Shortest Path First (OSPF) OSP
- Page 455 and 456: OSPF building blocks 1. Hello proto
- Page 457 and 458: Hello packet 0 7 8 15 16 23 24 31 V
- Page 459 and 460: Link State Announcement (LSA) heade
- Page 461 and 462: Link state update packet 0 7 8 15 1
- Page 463 and 464: Link state acknowledgement packet 0
- Page 465 and 466: Exterior Gateway Protocol (EGP) an
- Page 467 and 468: Local vs. Transit traffic Local tra
- Page 469 and 470: BGP does not transmit metrics. Howe
- Page 471 and 472: Redistribution of Route Information
- Page 473 and 474: • Open • Update • Keepalive
- Page 475 and 476: BGP Update Message 0 7 8 15 16 23 2
- Page 477 and 478: BGP Notification Message 0 7 8 15 1
- Page 479 and 480: Federal Internet eXchange (FIX) A t
- Page 481 and 482: Global Internet eXchange (GIX) Glob
- Page 483 and 484: Network Access Points (NAPs) At the
- Page 485 and 486: Router Arbiter Project Router Arbit
- Page 487: Euro6IX The European IPv6 Internet
- Page 491 and 492: A Tag Edge router labels a packet b
- Page 493 and 494: Creating tags Since tag switching d
- Page 495 and 496: Summary This lecture we have discus
- Page 497 and 498: [14] R. Hinden (Editor), “Applica
- Page 499 and 500: • Multicast • IGMP • RSVP Out
- Page 501 and 502: Broadcast and Multicast Traditional
- Page 503 and 504: Broadcasting • Limited Broadcast
- Page 505 and 506: Alternative centralized model CU-Se
- Page 507 and 508: IP Multicast scales well • End-no
- Page 509 and 510: Steve Deering’s Multicast Dynamic
- Page 511 and 512: Multicasting IP addresses Multicast
- Page 513 and 514: Converting Multicast Group to Ether
- Page 515 and 516: Problems Unfortunately many links d
- Page 517 and 518: How does IGMP fit into the protocol
- Page 519 and 520: IGMP Implementation Details In orde
- Page 521 and 522: IGMP Version 2 [3] Allows a host to
- Page 523 and 524: IGMP - ethereal Figure 7: IGMP pack
- Page 525 and 526: Frame 2: IGMP v2 Membership Report
- Page 527 and 528: Frame 15: IGMP v2 Leave Group Ether
- Page 529 and 530: Therefore a Multicast Router • Li
- Page 531 and 532: Multicast Routing - Flooding • ma
- Page 533 and 534: Multicast Routing - Spanning Trees
- Page 535 and 536: Reverse -Path Forwarding (RPF) RPF
- Page 537 and 538: Reverse Path Broadcast (RPB) • We
Flows<br />
A flow is defined as a “uni-directional stream of packets between a given source<br />
network-layer address and port number and a specific destination network-layer<br />
address and port number”.<br />
Since many application use well known transport-layer port numbers, it is possible<br />
to identify flows per user per application basis.<br />
There is a well defined Netflow Switching Developer’s Interface which allows<br />
you to get the statistics concerning the NetFlow cache and the per flow data (the<br />
later gives you essentially billing records).<br />
A general introduction to NetFlow Switching is available at<br />
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/switch_c/xcprt3/xcovntfl.htm<br />
Maguire Flows 7: 62 of 70<br />
maguire@kth.se <strong>2010</strong>.03.21 Internetworking/Internetteknik
Change language