112 Avid Networking - Final Version

WG112 Avid Networking
112
An Introduction to Networking Concepts Used in

Avid Workgroup and Storage Environments
Avid Training Services Copyright 2007, Avid Technology, Inc.

Knowledge Path & Pre-requisites
Unity MediaNet Customers

ISIS/Unity ACSR accepted on a case-by-case basis
Maintenance and Troubleshooting

112 WG213 Interplay Admin
WG112 Avid Networking
Installation and Support
WG433 Interplay ACSR

Table of Contents
• Module 1 Objectives/Overview
• Module 2 Elements of Network Design
• Module 3 Serial Connectivity and Switch Commands
– Exercise 1: Logging In to Switches via HyperTerminal
• Module 4 Ethernet
– Exercise 2: Configuring a VLAN via HyperTerminal
–
112 –
Exercise 3: Using Telnet & FTP to Backup and Restore Switch Configurations
Exercise 4: Viewing and Modifying a Configuration File in WordPad
– Exercise 5: Creating VLANs and Connecting Switches Via a Common VLAN
• Module 5 Internet Protocol (IP)
– Exercise 6: Calculating IP Subnets
– Exercise 7: Creating Dedicated and Virtual Router Interfaces
– Exercise 8: Creating Static Routes
• Module 6 Transport
• Module 7 Client Configuration Guidelines
• Module 8 Network Troubleshooting
• Module 9 Appendix

Module 1
112
Objectives/Overview

Overall Objectives
• Provide solid foundation in networking theory
• Provide hands on experience implementing and troubleshooting

networks
112
• Provide enough knowledge to ask the right questions
Module 1
Objectives
Overview

Overview
• Network Design & Implementation

• Serial Connection
• Network Layers
• Physical
• Ethernet
112
• TFTP
Module 1 • IP
Objectives
• Switches and Configuration
Overview • UDP
• TCP
• Troubleshooting

Before We Start: About Network Design
• The design is the blueprint of how the network is “supposed” to be

configured
• When doing “networky” things, always understand the design before

starting anything
112
• Knowing the design should reduce the amount of time for setup and
Module 1 troubleshooting – and reduce the risk of breaking stuff
Objectives
Overview

Network Design Example with Avid Components
•Small ISIS Workgroup

•Supported Zone 4 Clients:
•Core Switch •Media Manager Select
•Edge Switch •Interplay Assist

•Instinct
•ISIS “Zone Definitions”
•DV25
•MPEG2 Proxy
112
Module 1 •Media Manager Select
•Airspeed Ingest
•Interplay Assist
•Airspeed Playout (No PWT)
Objectives •Newscutter
•Editors
Overview •DV25
•Interplay
•DV50/IMX50
•Media Manager
•MPEG2 Proxy
.10 LAN .20 LAN

•Airspeed Playout
•Transfer Manager

112
Module 1
Objectives
Overview

112
Module 1
Objectives
Overview
10

112
Module 1
Objectives
Overview
11

112
Module 1
Objectives
Overview
12

112
Module 1
Objectives
Overview
13

112
Module 1
Objectives
Overview
14

112
Module 1
Objectives
Overview
15

112
Module 1
Objectives
Overview
16

112
Module 1
Objectives
Overview
17

Module 2
112
Elements of Network Design

Elements of Network Design
•Logical • Physical
• Devices (switches, cables, NICs)
• Ethernet networks/broadcast domains
• Connectivity – what plugs into what
• IP subnets
• Routing configs between subnets
• IP address for each device
112
Module 2
Elements of
Network Design
19

Networking Layers
• Networking has many types of protocols (e.g. TCP or Ethernet) &
standards
• Many of these protocols layer & interconnect with each other
• Understanding the nature of each layer and how they interact is

112 fundamental to working with networks
Module 2
Elements of
Network Design
20

Networking Layers – The OSI Model
• Physical – hardware, cables, connectors, NICs, copper, optical, electrical
and light signals, radio/wireless
• Link – Ethernet connects devices to each other in a LAN
• Network – IP allows connectivity between different networks – moves

the data across networks
112
Module 2
• Transport – TCP/UDP – a standard way for applications to talk across
the network
Elements of
Network Design
• Session (not discussed)
• Presentation (not discussed)
• Application – (e.g. HTTP, ISIS) – the information the software needs

moved across the network
21

Networking Layers – OSI Model - The Stack
Layer Function Unit #
Host Application (Flock, Interplay, HTTP)

Network process
to application Data L7
Layers
112 Transport TCP UDP
End-to-end connections
and reliability Segments L4
Module 2
Network: IP
Path determination and
logical addressing Packets L3
Elements of Media
Network Design
Layers
Link: Ethernet Physical addressing Frames L2
Physical Media, signal and binary
transmission Bits L1
22

Networking Layers – Encapsulation View
Physical/L1
Ethernet/Link/L2
IP/Network/L3
112
TCP or UDP/Transport/L4
Module 2
Elements of
Network Design
L5-L7
Payload/Application +
23

Physical Layer – Layer 1
• Cables & Connectors (e.g. Cat 5e, RJ45 or Multi-Mode Fiber, LC)
• Signaling specifications – electrical voltages, laser strength,

112 frequencies
Module 2
• Hardware – switches
Elements of
Network Design
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
24

Physical Layer – Layer 1 - Connectors
• RJ45: Copper 8-pin
• SC: Fiber Optical
112 Large connector
Module 2 • LC: Fiber Optical

Elements of Small connector
Network Design
• CX-4: Infiniband Copper

Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1 •Connectors are not cables! For example, different fiber types can use the same type of connector.
25

• For 1 gigabit Ethernet:
– Category 5e (Cat5e) or better cable for up to at 100 meters runs (328 feet) – all 8 wires
(4 pair) are used
– RJ 45 connectors
– Media adapter – copper to optical – allows distance up to 20KM (12.4 miles)
112
Module 2
Elements of
Network Design
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2 There is a minimum recommended cable length of 2 meters.
Physical L1 Shorter cables are known to cause network issues.

26

• For 10 gigabit Ethernet Short Range (SR)
– 62.5 micron Multi-Mode Fiber (26 meters/85 feet)
– 50 micron Multi-Mode Fiber (85 meters/279 feet)
– ISS & Foundry uses LC connector & XFPs
– Cisco 4948 uses SC connector & X2
112
Module 2
Elements of
• Long range (LR)
Network Design – 9 micron Single-Mode Fiber up to 10KM/6.2 miles)
– Requires long range XFPs &/or X2s
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
27

• Switches
(2) 10gb optical XFPs w/LC connector
Foundry X424
112
(24) 1gb copper ports w/RJ45 connectors
Module 2
Elements of
Network Design (2) 10gb optical X2 w/SC connector
Application L7
Transport L4
Cisco 4948
Network: IP L3
Link: Ethernet L2
Physical L1 (48) 1gb copper ports w/RJ45 connectors

28

Physical Layer - Switches
• ISIS Switches
Integrated Storage Switch Integrated Expansion Switch

ISS IXS
CX-4 Chassis Interconnect

112 Gb Management Port
Gb Management Port
Module 2
Elements of
Network Design
Application L7
(8) Gb Client Ports
Transport L4 (7) CX-4 Chassis Interconnects
Network: IP L3
Link: Ethernet L2
Slot for 10Gb XFP
Physical L1
29

Module 3
112
Serial Connectivity and Switch Commands

Serial Connectivity
• About
• The physical ports
112 • Terminal software – HyperTerminal

Module 3
• Connecting the ports
Serial
Connectivity
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
31

Serial Connections
• All managed network equipment has a serial port
• Serial ports should always “just work”
112 • Required when attaching to a switch with a blank or unknown

configuration
Module 3
Serial • Only two wires required for serial communications – “pins” 2 & 3
Connectivity
– (Cisco also requires pins 5 & 6. They include a cable with their switches.)
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
32

Serial Connections
Where to plug in…
RJ-45 Serial
DB-9 Male
RS-232
Serial – RS-232
112
Module 3
Serial
Connectivity
DB-9 Male
Serial – RS-232
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
•SR2400s also have a serial port!
Physical L1
33

Serial Connections
• Just because the cables fit does not mean they are the correct cables –
the wires may be swapped around in the cable
• The cables that come with the switches should work

112
• To terminal/console in, connect the console port of the switch to COM
Module 3
port of the PC/Laptop
Serial
Connectivity
• DO NOT connect the serial ports to the Ethernet ports
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
34

Terminal Software
• Hyper Terminal comes with Windows and is good enough to get the job done
– Start -> Programs -> Accessories -> Communications -> Hyper Terminal
• Select a COM port to connect with – make sure it is the one you have the cable
plugged into
• Port Settings (these work for most devices):

– Bits per second (a.k.a baud): 9600
112
– Data bits: 8
– Parity: none
Module 3
– Stop bits: 1
Serial – Flow control: none
Connectivity
• Notice the “connected” counter in the bottom left of the window – this tells you the
PC is active on the COM port – does not necessarily mean there is something on the
Application L7
other end
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
35

How to Test a PC Com Port
• Enable the serial connection
• Short/connect pins 2 and 3 on the COM port – you can use a

paperclip to do this or a piece of wire
• Type on the keyboard within the terminal program – you should see
112 what you type appear within the terminal program – the system is
talking to itself -- the COM port works!
Module 3
Serial
• If you don’t see anything when you type
Connectivity – The COM port is not active
– You have the wrong COM port
– You’re not connecting pins 2 & 3 together correctly
Application L7
Transport L4
Network: IP L3
2-3 Male 2-3 Female
Link: Ethernet L2
Physical L1
36

What Else Can Go Wrong?
• The switch is not on
• You have the wrong cable (if you don’t absolutely know you have the
right cable – then it probably is the wrong one)
112
• Did you check the PC COM port?
Module 3
Serial
Connectivity
• You are plugged into the wrong physical port (on one end, the other, or
both)
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
37

Switch Login and Navigation
• There are two basic ways to log in to a switch
– Telnet over the network

• Need network connectivity to the switch
• Need the switch password(s)
• Need to know the IP address of the switch
112 • Switch has to allow telnet access
Module 3
– Serial/terminal connection (RS-232)
Serial • Need physical access to the switch to connect a serial cable
Connectivity
• Need the right serial cable – not all cables and switch com ports are created equal
• Need a “terminal” device that has a RS-232 COM port – most computers will do
• Need the switch password(s)
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
38

Connected! Now What?
• Managed switches/routers typically have three modes
• User mode – starting mode when logged into the switch – can’t do
anything
112
• Privileged/“enable” mode – Management mode (e.g. restart, show stats)
Module 3
Serial
Connectivity • Global config – most switch configuration is done in this mode
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
39

Command Line Modes and Prompts
• Navigation Flow
configure terminal
enable conf t
Serial
112 Console
Privilege
User Config
Module 3 “enable”
Hostname> (config)#
Hostname#
Serial
Connectivity Telnet,
SSH exit exit
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
40

Using the Command Line
• List of commands (current mode): “ #? ”
• Commands starting with XYZ: “ #c? ”
• Next possible options of a command: “ #show ? ” – notice the space

between the word and the ?
112
• Command history – Up and Down Arrow keys
Module 3
• Next page in a list: Space bar
Serial
Connectivity
• Break out of a list: Control+c

Application L7
Transport L4
• Auto complete command: Tab
Network: IP L3
Link: Ethernet L2 • To disable configs in Config mode: no [command]

Physical L1 – For example, you can use the no command to remove an IP address
41

Exercise 1: Logging In to Switches via HyperTerminal
1. Break into two teams (Cisco Team and Foundry Team)
2. Connect serially to switches

• Cisco: RJ-45 MGMT port
• Foundry: DB-9 MGMT port
• Client: DB-9 or USB-Serial converter
1. Open HyperTerminal and select appropriate com port
112
2. 9600 | 8 | none | 1 | none
Module 3
3. Modes:
Serial
Connectivity
• > User mode granted on connection to switch
• # Privileged Mode “enable”
• (conf)# Config Mode “conf t”
Application L7
Transport L4 4. show running-config

Network: IP L3
Link: Ethernet L2
Physical L1
42

Module 4
112
Ethernet

Ethernet
• Layers
• Broadcast domains
• MAC address
• Ethernet header and trailer
• VLAN
• Default VLAN
112 • Frame size
Module 4
• Spanning tree
Ethernet
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
44

Physical Diagram
• Ethernet Connectivity
Port 35
Port 5
Port 48 to 1
112
Module 4 Port 18 Port 38

Port 48 to 1
Ethernet
Application L7
Transport L4
Network: IP L3
Port 2 Port 16
Link: Ethernet L2
Physical L1
45

Ethernet - Network Layer
• The Stack View

Network process
Layers

Module 4 Network: IP
Media
Ethernet
Layers
Application L7 Physical Media, signal and binary

Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
46

Ethernet – Network Layer
• Encapsulation View
Physical/L1
Ethernet/Link/L2
112 IP/Network/L3
Module 4
Ethernet
L5-L7
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
47

Ethernet – Network Layer
• Bit Order “on the wire”
112
Module 4 Ethernet
Ethernet IP TCP App/Payload
Checksum
Ethernet 1st 2nd 3rd 4th
Last
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
48

Ethernet (Link/Layer 2)
• Ethernet a Link Layer or Layer 2 protocol (L2)
• Link refers to getting data from one end of a cable to the other
112
• A Frame is a unit of Ethernet data, contains:
Module 4
Ethernet
– Destination Ethernet Address
– Source Ethernet Address
– Payload (IP packet)
Application L7 – CRC Checksum
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
49

• Ethernet Addresses (a.k.a Media Access Control, MAC, Physical)
– Examples:00-0C-F1-70-BE-98 or 00:0C:F1:70:BE:98
• Each network interface has a unique MAC address burned in (some
devices have configurable MAC addresses)
• Broadcast MAC address: FF:FF:FF:FF:FF:FF
• To check MAC (Physical) address on Windows:
112 – ipconfig /all
Module 4
Ethernet
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
50

• Ethernet is used only for communication within a LAN
• Not between LANs – forwarding/routing required (L3)
LAN “B”
112
Two separate
LAN “A” Ethernet
Module 4
networks
Ethernet
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
51

ISIS Ethernet LANs
ISIS has two separate Ethernet LANs
192.168.10.0(Left) 192.168.20.0(Right)
Left: “Dot 10”
Right: “Dot 20”
112
Module 4
Ethernet
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
52

ISIS Ethernet LANs
• The two LANs provide network redundancy
• Benefits
– Failure of switches or connections on one network does not impact the other
– Broadcast storms or “bad” Ethernet chatter are limited to one network
112
.10
Module 4
Ethernet
Application L7 .20
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
53

Ethernet Switches
• Ethernet (layer 2) switches connect devices within a broadcast domain
• Connecting multiple switches together can create a larger broadcast
domain
• Switches keep a table of MAC addresses and port associations and send
frames only out the port with the associated MAC address
• To see a switches MAC table:
112 “#show mac-address”
Shows a list of MAC addresses the
Module 4 switch knows about and which
Ethernet port it will use to send traffic
Ethernet
destined for that MAC
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
54

MAC Learning
Dst: D
A Src: A B
1 Switch 2
112 Dst: D MAC A: Port 1
Empty
MACMAC table
A: Port 1
Src: A MAC D: Port 4
Module 4
3 4
Ethernet
Dst: A
Application L7 Src: D
C D
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
55

Connecting Switches
• One big broadcast domain
112
Module 4
Ethernet
Broadcast Domain A Broadcast Domain B
Application L7
Transport L4
Network: IP L3 Assume each switch is one broadcast domain

Link: Ethernet L2
Physical L1
56

Virtual LAN = VLAN
• VLAN-ing allows a single switch to be divided into multiple broadcast domains
• In the simple case, network ports can be grouped into separate broadcast domains
• Untagged Ethernet is the type of VLAN implemented via the switches in an ISIS
112 environment (no modification to the Ethernet Frames)
Module 4
• Tagged Ethernet unsupported (pass through only)
Ethernet
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
57

Virtual LAN = VLAN
• Foundry and Cisco switches default config

is 3 separate networks/broadcast domains
• Foundry Ports:
• Left VLAN 1-12,25 •VLAN “40” – Port 23
• Right VLAN 13-22,26
112
• Corp uplink 24
Module 4 25 26 1-12 13-22
Ethernet • Cisco Ports:
• Left VLAN 1-24,49
•VLAN “40” – Port 47
• Right VLAN 25-46,50
Application L7 • Corp uplink 48 49
Transport L4
Network: IP L3
50
Link: Ethernet L2 1-24 25-46
Physical L1
58

Default VLAN
• On most switches there is a default VLAN, also known as VLAN 1
• Any Ethernet port not explicitly assigned to a VLAN is a member of

VLAN 1
• You can create additional VLANs which may or may not be able to
112 communicate with your other VLANs. It depends on you!
Module 4
Ethernet
?
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
59

Exercise 2 - Configuring a VLAN via HyperTerminal
• Foundry (from config mode)

– Create VLAN: vlan 30
– Assign ports to VLAN: untagged ethe 21 to 23
• Cisco (from config mode)

– Create VLAN: vlan 30
– Configure interface to join VLAN:
112 • interface gigabitethernet1/46
• switchport access vlan 30
Module 4 • switchport mode access
Ethernet
• interface gigabitethernet1/47
• switchport access vlan 30
• switchport mode access
Application L7
Transport L4 • To see VLAN config: show vlan

Network: IP L3
Link: Ethernet L2
Physical L1
60

Exercise 3 - Using Telnet to connect to switchs
1. Assign client IP address (192.168.10.100, 255.255.255.0)

2. Plug into VLAN 10 port on switch
3. Open command prompt (start > run … “cmd”)
– ping 192.168.10.1 (confirm connectivity to switch)
– telnet 192.168.10.1
• You should get a command prompt that looks like:
– Cisco: [switch name]>
112 – Foundry: telnet@[switch name]>
Module 4
Ethernet
By default Cisco will refuse connections if
there is no “Privilege” mode password set!
1. (conf)# line vty 0 5

Application L7
2. (conf)# enable password avid
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
61

Exercise 4 - Using Telnet & FTP to Backup and Restore Switch Configurations
(TFTP Install and Copy Config)
1. Install TFTP Server (Pumpkin) on client machine
2. Run Pumpkin and click on options

• Change share directory
• Grant full access (read and write)
112
Module 4
Ethernet 3. Upload running config to server

• Foundry: copy running-config tftp 192.168.10.100 running-config
• Cisco: copy running-config tftp
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
62

Exercise 4 - Using Telnet & FTP to Backup and Restore Switch Configurations
(TFTP Save Config File)
1. Open config file with wordpad

• Change hostname
• Change port allocation
• Cisco: Ports 1-15 VLAN 10
Ports 16-30 VLAN 20
Ports 31-47 VLAN 30
Port 48 VLAN 40
• Foundry Ports 1-8 VLAN 10

112 Ports 9-16 VLAN 20
Ports 17-23 VLAN 30
Module 4 Port 24 VLAN 40
2. Copy client file back to running config
Ethernet
• Cisco: copy tftp running-config
• Foundry: copy tftp running-config 192.168.10.100 running-config
3. show running-config
Application L7 4. show starting-config
Transport L4
5. copy running-config startup-config
Network: IP L3
6. write mem
Link: Ethernet L2
Physical L1
7. reload
63

Our Current Topology - Physical Diagram
IP Address: 192.168.10.100
112
VLAN 10 – ports 1-15 IP Address: 192.168.10.100
Module 4
VLAN 20 – ports 16-30
Ethernet VLAN 30 – ports 31-47
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
64

Exercise 5: Trunking switches via common VLAN
IP Address: 192.168.10.100
112
VLAN 10 – ports 1-15 IP Address: 192.168.10.200
Module 4
Ethernet VLAN 30 – ports 31-47
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
65

Spanning-Tree Protocol
• Spanning-Tree Protocol (STP) is used to prevent Ethernet loops
Switch 2
LAN A
112
Switch 1
Module 4
LAN A
Ethernet
Switch 3
LAN A
Application L7
Transport L4
Network: IP L3 All switches in this example are part of the same broadcast domain.
Link: Ethernet L2
Physical L1
66

Spanning-Tree Protocol
• Ethernet loops cause nasty problems
– No connectivity
– Intermittent connectivity
– Capacity impact – all traffic out all ports
• Spanning Tree Protocol allows a switch to detect when it has multiple
paths to the same location (a loop)
• All ports involved in the loop but one are “blocked”
112
• See STP state
Module 4 – Cisco:
show spanning-tree
Ethernet
– Foundry:
show interface brief
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
67

ISIS & Spanning-Tree Protocol
• As of ISIS version v1.2, ISS/IXS will pass through spanning-tree

information
• Prior versions of ISIS (ISS/IXS) do not support Spanning Tree!!!!
112 • An incorrectly connected cable can create an Ethernet loop and bring
down an ISIS VLAN
Module 4
Ethernet
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
68

ISIS & Spanning-Tree Protocol
• What NOT to do
“Left” Network “Right” Network
112
Module 4
Ethernet
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
69

Module 5
112
Internet Protocol (IP)

IP
• Behavior
• Subnets & masks
• Binary
• CIDR
• Netmask exercise
• IP config lab
112 • IP header
Module 5
• IP Fragments
• Routing
IP
• TTL
• ICMP
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
71

IP - Network Layer
• The Stack View
Host Application (Flock, Interplay, HTTP) Network process

Layers
Module 5
Network: IP
IP
Media
Layers
L1
Application L7
transmission Bits
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
72

IP – Network Layer
• Encapsulation View
Physical/L1
Ethernet/Link/L2
112 IP/Network/L3
Module 5
IP
L5-L7
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
73

IP– Network Layer
• Bit Order “on the wire”
112
Module 5 Ethernet
Checksum
IP 1st 2nd 3rd 4th
Last
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
74

IP (Network/Layer 3)
• IP (Internet Protocol) is used for moving data within and BETWEEN

networks
112
• Without IP you could not communicate from one LAN to another
Module 5
IP • IP is a layer 3 (L3) protocol, also known as the network layer
• Each IP device has at least one unique IP address

Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
75

IP Behavior
• Responsible for trying to deliver IP packets to their destinations
• Does NOT guarantee reliable delivery of packets – will not resend lost
packets
• Does NOT guarantee in order delivery of packets

112
• Connectionless – no end point set up required
Module 5
IP
• Duplicate packets may occur
Application L7
• Best effort
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
76

IP Addresses
• IP addresses contain four numbers ranging from 0-255,

each separated by periods.
– (0-255).(0-255).(0-255).(0-255)
• IP addresses have several uses and meanings:

112 – Unique identifier for a device (host) on a network
– Defining the subnet of a LAN
Module 5
– Part of defining an arbitrary range of addresses
– Know which context you are using it in!!!!
IP
• Each number is a decimal representation of an 8-bit binary octet

Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
77

Network Mask (Subnet)
• Network Mask, Net Mask, Netmask, Subnet mask, Mask
• An IP address for a host or network is never complete without a net mask
• Net masks allow routers to forward packets between networks
112 • Net masks have a limited number of IP addresses valid for its subnet
Module 5
• To find the IP address range for a given net mask, you have to look at the
IP
binary numbers…
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
78

Special Addresses in a Subnet
• Example subnet: 192.168.10.0/24
• Network Address: first valid IP address in subnet

– Network ID for the whole subnet
– The starting subnet address (192.168.10.0)
– Not for use by any physical device
– Always even
112
Module 5
• Broadcast address: last valid IP address in subnet
– Used by network to broadcast mass communications
IP
– The highest subnet address (192.168.10.255)
– Not for use by any device
– Always odd
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
79

IP Addressing Notes
• Smallest usable subnet subnet is /30
– Example: 255.255.255.252
– 4 total addresses
– Start address reserved for Net ID
– End address reserved for broadcast
– 2 addresses available for devices/hosts
112 • All devices on the same IP subnet MUST

– have the same subnet mask
Module 5 – have an IP address in the same network address range
IP
– direct connectivity to the same broadcast domain (Ethernet LAN)
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
80

Exercise 6: Calculating Net Masks
• Calculate total number of addresses using a subnet calculator

• Subnet starting IP (network address)
• Subnet ending IP (broadcast address)
1. 155.203.11.99 /27
112
2. 199.5.7.243 255.255.254.0
Module 5
3. 203.73.52.128 /25
IP
4. 67.43.227.5 /23
Application L7
Transport L4 5. 211.256.3.198 255.255.246.0

Network: IP L3
Link: Ethernet L2
Physical L1
81

Creating Router Interfaces
• Dedicated router interface

– This port is no longer part of a VLAN on the switch – it is unique and separate
• Virtual routing interface

– This interface is associated with a VLAN not a single port
112 – All interfaces that are part of the VLAN can directly reach the virtual routing interface
Module 5
IP
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
82

Exercise 7: Creating Dedicated and Virtual Router Interfaces
(Virtual)
1. Connect a new client to a VLAN 30 port and assign an IP address (192.168.30.100 or

192.168.30.200) (Subnet 255.255.255.0)
2. Configure VLAN 30’s IP address (Virtual Router Interface)
• Foundry (config mode)
1. vlan 30
2. router-interface ve 30
3. interface ve 30
4. ip address 192.168.30.1
• Cisco (config mode)
112 1. vlan 30
2. interface vlan 30
3. ip address 192.168.30.1
Module 5 4. no shutdown
3. Assign each of the .10 and .30 clients a default gateway (the VLAN IP address)
IP
4. Have the clients ping each other on your switch
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2 .10 ping .30 .10 ping .30

Physical L1
83

(Virtual)
• Start of Day 2: Reconfigure or verify switches to this diagram:
IP Address: 192.168.10.100 /24 IP Address: 192.168.40.100 /24
112
Module 5
IP
VLAN 10 – ports 1-15 VLAN 10 – ports 1-8

VRI - 192.168.10.1 /24 VRI - 192.168.40.1 /24
Application L7 VLAN 20 – ports 16-30 VLAN 20 – ports 9-16
Transport L4 VRI - 192.168.20.1 /24 VRI - 192.168.50.1 /24
Network: IP L3 VLAN 30 – ports 31-47 VLAN 30 – ports 17-23
Link: Ethernet L2 VRI - 192.168.30.1 /24 VRI - 192.168.60.1 /24
Physical L1
84

(Dedicated)
• Make port 48 / 24 uplink to each switch

• Foundry (config mode)
1. interface ethernet 24
2. route-only
3. ip address 192.168.10.2 255.255.255.0
112 • Cisco (config mode)

1. interface gigabitethernet 1/48
Module 5
2. no switchport
3. ip addresses 192.168.40.2 255.255.255.0
IP
4. no shutdown
– Connect the two switches between dedicated router ports and

Application L7
respective VLANs
Transport L4
Network: IP L3
– Ping your router interface
Link: Ethernet L2 – Try to ping other switches client on that subnet/VLAN
Physical L1
85

Exercise 8: Creating Static Routes
• Start of Day 2: Reconfigure or verify switches to this diagram:
112
Module 5
IP
VLAN 10 – ports 1-15 VLAN 10 – ports 1-8

VRI - 192.168.10.1 /24 VRI - 192.168.40.1 /24
Application L7 VLAN 20 – ports 16-30 VLAN 20 – ports 9-16
Transport L4 VRI - 192.168.20.1 /24 VRI - 192.168.50.1 /24
Network: IP L3 VLAN 30 – ports 31-47 VLAN 30 – ports 17-23
Link: Ethernet L2 VRI - 192.168.30.1 /24 VRI - 192.168.60.1 /24
Physical L1 DRI - Port 48 - 192.168.40.2 /24 DRI - Port 24 - 192.168.10.2 /24
86

Exercise 8: Creating Static Routes (Continued)
• Setup client pings

– From Cisco VLAN 10 client:
• ping -t 192.168.40.2 (Router interface on your router)
• ping -t 192.168.40.1 (Router interface on Foundry)
• ping -t 192.168.40.100 (Client on Foundry’s VLAN 40)
– From Foundry VLAN 40 client:
• ping -t 192.168.10.2 (Router interface on your router)
112 • ping -t 192.168.10.1 (Router interface on Cisco)
• ping -t 192.168.10.100 (Client on Cisco’s VLAN 10)
Module 5
• Foundry: (config mode)
IP
1. ip route 192.168.10.0 255.255.255.0 192.168.10.1
2. show ip route
Application L7 • Cisco: (config mode)

Transport L4 1. ip route 192.168.40.0 255.255.255.0 192.168.40.1
Network: IP L3 2. show ip route
Link: Ethernet L2
Physical L1
87

Address Resolution Protocol
• a.k.a ARP
• To discover the MAC address of a device on the same IP subnet a host

will use ARP
112
• 192.168.10.100/24 wants to send to 192.168.10.203/24
Module 5
IP
• 192.168.10.100 sends out a broadcast packet (192.168.10.255,
FF:FF:FF:FF:FF:FF) with a request “who has 192.168.10.203”
Application L7 • 192.168.10.203 hears the request and replies back to 192.168.10.100

Transport L4 with its MAC address
Network: IP L3
Link: Ethernet L2
Physical L1
88

IP Routing
IP Packet A device needs to be told how

Dest: 192.168.20.203 to “forward” packets destined
for other networks.
112
Module 5 This is usually done by setting

IP the default gateway on a client
(a.k.a, default route, route of
Workstation IP last resort).
Application L7
192.168.10.166/24
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
89

IP Routing: Default Gateway
In this case any traffic that the

workstation sends that is not on its
IP Packet local network will be forwarded to
Dest: 192.168.20.203 the router (or Layer 3 switch).
112
Module 5
IP
Router IPs
192.168.10.2/24
Application L7
Workstation IP 192.168.20.2/24
Transport L4
192.168.10.166/24
Network: IP L3
Default Gateway
Link: Ethernet L2
Physical L1
192.168.10.2
90

IP Routing
• Each IP device (workstation, server, router) makes a routing decision on
each packet it handles
• Every IP device in the chain/path from source to destination needs to

know how to route each packet
112 • Route definition: [destination network address], [destination netmask],

[next hop address/gateway]
Module 5 – 192.168.50.0 255.255.255.0 192.168.30.2
– 0.0.0.0 0.0.0.0 192.168.30.1
IP
• 0.0.0.0 0.0.0.0 means default route – all subnets, all netmasks

Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
91

Routing: Getting There…
IP Packet
Dst:192.168.50.92
Network:
192.168.20.0/24
Addr: 192.168.10.166/24
Def GW: 192.168.10.2 Addr: 192.168.10.2/24
192.168.20.2/24
Network 192.168.30.2/24
112 192.168.10.0/24 Routes
192.168.40.0 255.255.255.0 192.168.30.3
192.168.50.0 255.255.255.0 192.168.30.4
Module 5 0.0.0.0 0.0.0.0 192.168.30.1
192.168.30.3
IP
Network
Addr: 192.168.50.92/24 192.168.30.0/24
192.168.30.1
Application L7
Transport L4
Network Addr: 192.168.30.4/24
192.168.50.0/24 192.168.50.1/24
Network: IP L3
Routes
Link: Ethernet L2
0.0.0.0 0.0.0.0 192.168.30.1
Physical L1
92

Routing: …And Back
Network:
192.168.20.0/24
Addr: 192.168.10.166/24 Addr: 192.168.10.2/24
Def GW: 192.168.10.2 192.168.20.2/24
Network 192.168.30.2/24
192.168.10.0/24 Routes
112 192.168.40.0 255.255.255.0 192.168.30.3
192.168.50.0 255.255.255.0 192.168.30.4
Module 5 0.0.0.0 0.0.0.0 192.168.30.1
IP
IP Packet
Packet 192.168.30.3
IP Dst:192.168.10.166
Dst:192.168.50.92 Network
192.168.30.0/24 192.168.30.1
Application L7
Addr: 192.168.50.92/24
Def GW: 192.168.50.1 Addr: 192.168.30.4/24
Transport L4 192.168.50.1/24
Network: IP L3
Network Routes
192.168.50.0/24 0.0.0.0 0.0.0.0 192.168.30.1
Link: Ethernet L2
Physical L1 192.168.10.0 255.255.255.0 192.168.30.2

93

“Assymetric” Routing
• Don’t assume packets travel the same way to and from two points.
112
Module 5
IP
Net A Net B
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
94

Windows Routing Table
Windows systems: “route print”, “netstat –r”

Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x20003 ...00 13 ce e9 ea e9 ...... Intel(R) PRO/Wireless 2200BG Network Connect
ion - Deterministic Network Enhancer Miniport
0x30005 ...00 15 60 ae a8 a4 ...... Broadcom NetXtreme Gigabit Ethernet - Deterministic
Network Enhancer Miniport
===========================================================================
112 ===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.103 30
Module 5 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.103 192.168.1.103 30
IP
192.168.1.103 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.1.255 255.255.255.255 192.168.1.103 192.168.1.103 30
224.0.0.0 240.0.0.0 192.168.1.103 192.168.1.103 30
255.255.255.255 255.255.255.255 192.168.1.103 192.168.1.103 1
Default Gateway: 192.168.1.1
===========================================================================
Application L7 Persistent Routes:
Transport L4
None
Network: IP L3
Link: Ethernet L2
Physical L1
95

Configure Default Gateway
• Enter the IP
address of the
112 router/gateway to
get off the
Module 5
network.
IP
• Needs to be an
address that is in
Application L7 the same subnet as
Transport L4
the client.
Network: IP L3
Link: Ethernet L2
Physical L1
96

Router Routing Tables- Cisco
• Cisco: show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 172.20.52.1 to network 0.0.0.0

112
172.20.0.0/16 is variably subnetted, 10 subnets, 4 masks
R 172.20.74.192/26 [120/1] via 172.20.78.3, 00:00:25, Vlan30
Module 5 R 172.20.75.192/26 [120/1] via 172.20.78.3, 00:00:25, Vlan30
C 172.20.52.0/22 is directly connected, GigabitEthernet7/1
IP
S 172.20.96.0/24 [1/0] via 172.20.78.2
S 172.20.97.0/24 [1/0] via 172.20.78.2
S 172.20.98.0/24 [1/0] via 172.20.78.2
C 172.20.88.0/22 is directly connected, Vlan10
Application L7 C 172.20.92.0/22 is directly connected, Vlan20
Transport L4
Network: IP L3 S* 0.0.0.0/0 [1/0] via 172.20.52.1
Link: Ethernet L2
Physical L1
97

Router Routing Tables - Foundry
• Foundry: show ip route

Total number of IP routes: 5
Start index: 1 B:BGP D:Connected R:RIP S:Static O:OSPF *:Candidate default
Destination NetMask Gateway Port Cost Type
1 172.20.52.0 255.255.252.0 0.0.0.0 24 1 D
2 172.20.74.128 255.255.255.192 0.0.0.0 v10 1 D
3 172.20.75.128 255.255.255.192 0.0.0.0 v20 1 D
112 4 172.20.78.24 255.255.255.248 172.20.54.57 24 1 S
5 0.0.0.0 0.0.0.0 172.20.52.1 24 1 S
Module 5
IP
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
98

Adding a Static Route
Switch to be
IP
configured
Unknown
112 In-between
Address of Networks
Module 5 next hop

router Destination
IP Network
Application L7
Transport L4
ip route [dest network] [dest netmask] [next hop IP]
Network: IP L3
Link: Ethernet L2
Physical L1
99

Adding a Static Route
Switch to be
IP
configured
Unknown
112
In-between
Networks
Module 5
172.168.5.0
IP 10.3.29.2
255.255.255.0
Application L7
Transport L4
Network: IP L3
ip route [dest network] [dest netmask] [next hop IP]
Link: Ethernet L2
ip route 172.168.5.0 255.255.255.0 10.3.29.2
Physical L1
100

Exercise 8: Creating Static Routes
• Routing Between Different VLANs on Multiple Switches/Routers
– From “conf t” mode (configure terminal)
– ip route [dest net address] [dest net mask] [next hop address]
112 – Works for both Cisco and Foundry
Module 5 – Don’t forget to save the changes to the startup-config
IP
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
101

Static & Dynamic Routing
• Static routes: routing table entries that are made manually by the user.
They do not change automatically
• Dynamic routes: routing table entries that are updated automatically

112 based on route information learned from other routers/devices (requires a
routing protocol)
Module 5
IP
• Routing protocols: networking protocols that routers use to share
information about routes
– Examples: RIP, OSPF, EIGRP
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
102

Routing Failures
• Reasons why routing may fail on one of the devices in the chain
– No route configured for the packet
– Network mis-configuration
• IP address, subnet mask, cabling, disable interfaces
– Incorrect route for the packet
112 – No Ethernet connectivity to the next hop
– Routing loop
Module 5 – Too many hops
IP
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
103

Some Client Routing Failures
Addr: 192.168.10.166/25
Def GW: 192.168.10.2
Addr: 192.168.10.166/23
Def GW: 192.168.10.3
Addr: 192.168.20.166/24
Def GW: 192.168.10.2
112
Addr: 192.168.10.166/24 Addr: 192.168.10.166/24
Module 5
Def GW: Def GW: 192.168.10.2
IP
Application L7
Addr: 192.168.10.2/24
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
104

TTL
• TTL: Time to Live
• Number of routing hops a packet can take before being dropped
• Each IP packet has TTL set by the sender
112 • Every time a router forwards a packet it decrements the TTL counter by
1
Module 5
IP
• When the counter reaches zero, the router drops the packet and sends a
message (ICMP) to the sender
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
105

TTL: Too Many Hops/Time Exceeded
IP Packet
TTL:
TTL: 12
0
112
Source
Module 5
IP
Application L7
L4
Destination
Transport
Switch sends an ICMP message (Time Exceeded) back to
Network: IP L3
source IP
Link: Ethernet L2
Physical L1
106

ICMP
• Internet Control Message Protocol
• ICMP is part of IP – it is a special type of IP packet carrying an ICMP

payload as opposed to TCP or UDP
• Typically used for reporting back to sender when on IP packet can’t be

112 delivered:
– TTL exceeded
Module 5 – Destination unreachable
IP
• Also used for network diagnostics
– Ping (echo request/reply)
– Sometimes used for traceroute
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
107

Ethernet Diagram
VLAN D: 1 -24
Port 35 VLAN E: 25-48
Port 5
BD-I BD-J
Port 48 to 1
112
Port 18 Port 38
Module 5 Port 48 to 1 BD-H
VLAN A: All Ports
IP
BD-G VLAN B: 1 -16

VLAN C: 17-47
Application L7
Port 48
Transport L4
Network: IP L3 Port 2 Port 16 BD = Broadcast Domain

Link: Ethernet L2
Physical L1
108

IP Diagram
Port 35 VLAN D: 1 -32, RTR: 192.168.203.1/24

Port 5 7.16.8.11/24 VLAN E: 25-48, RTR: 10.10.10.1/24
73.5.180.18/24
192.168.203.0/24 10.10.10.0/24
Port 48 to 1
112
Module 5
VLAN A: All Ports 7.16.8.0/24 Port 38
10.10.10.6/24
IP
Port 48 to 1
73.5.180.0/24 VLAN B: 1 -16,

RTR: 73.5.180.1/24
----------------------------
Application L7
VLAN C: 17-47 Port 18
Transport L4 ---------------------------- 192.168.203.51/24
Network: IP L3 Port 48,
RTR: 192.168.203.2/24
Link: Ethernet L2 Port 2 Port 16
Physical L1
73.5.180.19/24 73.5.180.20/24
109

Module 6
112
Transport

Network Layers - The Stack

Network process
Layers
112
Transport TCP UDP
Module 6
Network: IP
Media
Transport
Layers
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
111

Network Layers – Encapsulation View
Physical/L1
Ethernet/Link/L2
IP/Network/L3
112 TCP or UDP/Transport/L4
Module 6
Transport L5-L7
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
112

Bit Order “on the Wire”
112
Module 6 Ethernet
Checksum
Transport 1st 2nd 3rd 4th
Last
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
113

TCP
• Transmission Control Protocol

• Transport Layer Protocol (Layer 4/L4)
• Creates virtual connections between two devices
112
• Guarantees in order delivery of packets
Module 6 • There are connection startup, data transmission, connection
shutdown modes
Transport
• Connection lasts as long as the application (e.g. web browser) keeps
it open
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
114

TCP Connection
• Each TCP connection is defined by:
– Source IP address
– Source port number
– Destination IP address
– Destination port number
• TCP port numbers – these are port numbers that do not relate to anything
112 else other than the TCP protocol
Module 6
• These should not be confused with Ethernet switch ports, NIC ports,
Transport
UDP ports
• There are some port numbers that are commonly used for a defined
Application L7
purpose: TCP/80 = HTTP(web), TCP/25= SMTP(mail), TCP/23= Telnet
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
115

TCP Connection Startup
Client trying to Server running web

1) Syn: Synchronize server TCP/80 waiting to
connect to web
Request service connections
server
2) Syn/Ack: Acknowledge
112 Syn Request
192.168.10.201 TCP/3305 172.205.5.156 TCP/80

Module 6
Transport
3) Ack: Acknowledge
Syn/Ack
Application L7
Transport L4
Connection Established
Network: IP L3
HTTP web session can start
Link: Ethernet L2
Physical L1
117

TCP Connection Established
• Once a connection is established both sides can send and receive data
• The receiver “acks” all data received
• If sender does not get an “ack” it will resend data
112
Connected to web server Connected to client
Module 6
Transport Send data & acknowledge

received packets
Application L7
Transport L4 Send data & acknowledge

Network: IP L3 received packets
Link: Ethernet L2
192.168.10.201 TCP/3305 172.20.5.156 TCP/80
Physical L1
118

TCP, MTU, & MSS
• TCP negotiates Maximum Segment Size (MSS) for each TCP connection
• The segment size is based on the lower of MTUs of the source &
destination devices (ignores the switches and routers in between)
112
• Each TCP packet will be the same size or smaller than the MSS
Module 6
Transport
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
119

UDP
• User Datagram Protocol
• Does not guarantee delivery
• Does not guarantee ordering
112 • Stateless – the protocol does not track what packets have been sent
Module 6
• Connectionless – there is no network session start up or tear down
Transport
• Much simpler than TCP

Application L7
Transport L4 • Does not negotiate Maximum Segment Size

Network: IP L3
Link: Ethernet L2
Physical L1
120

UDP Packet
• Each UDP packet is defined by
– Source IP address
– Source port number
– Destination IP address
– Destination port number
• UDP port numbers – these are port numbers that do not relate to
112 anything else other than the UDP protocol
Module 6
• These should not be confused with Ethernet switch ports, NIC ports,
Transport
TCP ports
• There are some port numbers that are commonly used for a defined
Application L7
purpose: UDP/53 = DNS, UDP/161= SNMP(Simple Network
Transport L4
Network: IP L3
Management Protocol), UDP/69 = TFTP
Link: Ethernet L2
Physical L1
121

UDP Send
Client Sending SNMP server listening

message to SNMP for UDP messages
server
UDP Packet
112
Module 6
192.168.10.201 UDP/2578 172.20.5.156 UDP/161
Transport
UDP is a one way, one time protocol. Applications that use UDP for stateful
communication need to track messages at the application level.
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
122

How It All Goes Together
• Example of the step-by-step process of how an application connects over the
network
• We will see how a web browser connects to a web server
112
Module 6 .1 Route Entry:

.1 .2 Route Entry:
.1
Transport
.181 172.20.3.0/24
81.6.201.2
5.11.8.0/24
81.6.201.1 .253
Def GW:.1 Def GW:.1
Application L7 Net: 5.11.8.0/24 Net: 81.6.201.0/24 Net: 172.20.3.0/24

Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
123

How It All Goes Together
Client with a web browser

Web server listening
opening an HTTP
for HTTP connections
(TCP/80) connection to
on TCP/80
server at 172.20.3.253
112
Module 6 .1 Route Entry:

.1 .2 Route Entry:
.1
Transport
.181 172.20.3.0/24
81.6.201.2
5.11.8.0/24
81.6.201.1 .253
Def GW:.1 Def GW:.1
Application L7 Net: 5.11.8.0/24 Net: 81.6.201.0/24 Net: 172.20.3.0/24

Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
124

Open Connection
Client App • Start: web browser initiates request Server App

to view a web page TCP/80
Open Connection
• First step is to open a TCP
TCP: src port 1147:
dst port 80
connection/socket to the web
Syn server (172.20.3.253)
112
Module 6
Transport Route Entry: Route Entry:

.1 .1 .2 .1
172.20.3.0/24 5.11.8.0/24
.181 .253
81.6.201.2 81.6.201.1
Def GW:.1 Def GW:.1
Application L7 Net: 172.20.3.0/24

Net: 5.11.8.0/24 Net: 81.6.201.0/24
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
125

Create Packet
Client App Server App

• An IP packet gets created TCP/80
Open Connection with the TCP/App payload
TCP: src port 1147: • Based on the default gateway
dst port 80
Syn
configuration IP figures that
the next hop is the router
IP: src 5.11.8.181: 5.11.8.1
112 dst 172.20.3.253
Module 6
Transport
Route Entry: Route Entry:
.1 .1 .2 .1
172.20.3.0/24 5.11.8.0/24
.181 .253
81.6.201.2 81.6.201.1
Def GW:.1 Def GW:.1
Application L7
Net: 81.6.201.0/24 Net: 172.20.3.0/24
Transport L4 Net: 5.11.8.0/24
Network: IP L3
Link: Ethernet L2
Physical L1
126

Start Journey

TCP/80
• If the client does not know the
Open Connection
MAC address of 5.11.8.1, it
TCP: src port 1147: will use an ARP broadcast to
dst port 80
Syn find out
• An Ethernet frame gets created
IP: src 5.11.8.181:
dst 172.20.3.253
and is sent to the gateway
112 (bb:bb:bb:bb:bb:bb)
Ethe:
Dst bb:bb:bb:bb:bb:bb
Src aa:aa:aa:aa:aa:aa
Module 6
Transport
Route Entry: Route Entry:

.1 .1 .2 .1
172.20.3.0/24 5.11.8.0/24
.181 .253
Application L7 81.6.201.2 81.6.201.1
Def GW:.1 Def GW:.1
Transport L4
Network: IP L3
Net: 5.11.8.0/24 Net: 81.6.201.0/24 Net: 172.20.3.0/24
Link: Ethernet L2
Physical L1
127

1st Router Handles Packet

•Router receives frame
TCP/80
Open Connection •Removes old Ethernet header
•Decrements the TTL field in the IP packet
TCP: src port 1147: (not shown)
dst port 80
•Looks in the routing table for the next hop
Syn (81.6.201.2)
112 IP: src 5.11.8.181: •ARPs to find the MAC address of
81.6.201.2 if not already known
dst 172.20.3.253
•Creates new Ethernet header and sends it
Module 6 Ethe:
on its way
Transport
Application L7 Route Entry: Route Entry:

.1 172.20.3.0/24 .1 .2 .1
Transport L4 5.11.8.0/24
.181 81.6.201.2 .253
81.6.201.1
Network: IP L3 Def GW:.1 Def GW:.1
Link: Ethernet L2
Net: 5.11.8.0/24 Net: 81.6.201.0/24 Net: 172.20.3.0/24

Physical L1
128

2nd Router Handles Packet

TCP/80
Open Connection
TCP: src port 1147:

• Router receives frame dst port 80
• Removes old Ethernet header Syn
112 •
•
Decrements the TTL field in the IP packet (not shown)
Router has interface on destination network IP: src 5.11.8.181:
• ARPs to find the MAC address of 172.20.3.253
• Creates new Ethernet header and sends it to the server
dst 172.20.3.253
Module 6 Ethe:
Transport Src aa:aa:aa:aa:aa:aa

.1 172.20.3.0/24 .1 .2 5.11.8.0/24 .1
Transport L4 .181 .253
81.6.201.2 81.6.201.1
Link: Ethernet L2
Physical L1
129

Server Receives Packet

TCP/80
Open Connection
•Server NIC receives the Ethernet frame TCP: src port 1147:
•Ethernet header is removed and packet is handed off to the IP dst port 80
layer Syn
112 •IP sees the packet is at the destination and hands the payload to
TCP IP: src 5.11.8.181:
•TCP sees it is a SYN packet for port 80 – the Server App has a dst 172.20.3.253
Module 6 listening socket on this port
Ethe:
•TCP sends back a SYN/ACK Dst bb:bb:bb:bb:bb:bb

.1 172.20.3.0/24 .1 .2 5.11.8.0/24 .1
81.6.201.2 81.6.201.1
Link: Ethernet L2
Physical L1
130

Response Created

TCP/80
Open Connection
•TCP gives the Syn/Ack to IP layer TCP: src port 1147:

dst port 80
•IP creates packet and gives to Ethernet Syn/Ack
112 layer
IP: src 5.11.8.181:
•Ethernet creates frame and it all happens dst 172.20.3.253
Module 6 again in reverse Ethe:

.1 172.20.3.0/24 .1 .2 5.11.8.0/24 .1
81.6.201.2 81.6.201.1
Link: Ethernet L2
Physical L1
131

Response Created

TCP/80
Open Connection
•TCP gives the Syn/Ack to IP layer TCP: src port 1147:

dst port 80
•IP creates packet and gives to Ethernet Syn/Ack
112 layer
IP: src 5.11.8.181:
•Ethernet creates frame and it all happens dst 172.20.3.253
Module 6 again in reverse Ethe:

.1 172.20.3.0/24 .1 .2 5.11.8.0/24 .1
81.6.201.2 81.6.201.1
Link: Ethernet L2
Physical L1
132

Connected

•TCP SYN/ACK arrives at the TCP/80
Open Connection client TCP layer
TCP: src port 1147: •Client TCP responds back with TCP: src port 1147:
dst port 80 an ACK dst port 80
Ack Syn/Ack
112 •Connection is now established
IP: src 5.11.8.181:
dst 172.20.3.253
Module 6
Ethe:
Transport

.1 172.20.3.0/24 .1 .2 5.11.8.0/24 .1
81.6.201.2 81.6.201.1
Link: Ethernet L2
Physical L1
133

Module 7
112
Client Configuration Guidelines

Ethernet Frame Size
• “Standard” Ethernet frame size, or Maximum Transmission Unit

(MTU) is 1500 (1518) bytes. 64 bytes is the smallest frame size.
• Many switches and NICs support larger frame sizes (Jumbo

Frames). This has to be explicitly set.
112 • The only official IEEE Jumbo Frame size is 9000 (9018) bytes –
there are other sizes (4000, 16000 bytes) that are vendor specific.
Module 7
Client
Configuration
Guidelines
• Jumbo Frames can be processed more efficiently than standard
frames.
Application L7
• ISIS does NOT support Jumbo Frames – things may/will break if
Transport L4
there is a frame size mismatch.
Network: IP L3
Link: Ethernet L2
Physical L1
135

Ethernet Frame Size
• Maximum Transmission Unit (MTU) - the size (in bytes) of the largest packet
a given layer of a communications protocol can pass on
Host A NIC Host B NIC

Switch
9000 9000
MTU 1500 MTU
112 MTU
Module 7
Client 9000 9000
Configuration
Guidelines 1500 MTU MTU
MTU
Application L7
9000
Transport L4
Network: IP L3
1500 MTU 1500
Link: Ethernet L2
Physical L1 MTU MTU

136

Ethernet Frame Size
• If less than a full frame is sent, frame size mismatch may not be a
problem for that frame
• TCP negotiates segment size to be the lowest of the two end points
• Ping is a useful tool to test the effective frame size for the end to end
112 path:
– Ping –l [size] –f [dest ip address/name]
Module 7 – -l indicates size of packet
Client
Configuration
– -f means do not fragment the packet into smaller packets
Guidelines
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
137

Ethernet Flow Control
• Flow control lets the receiver tell the sender when to send and not send
data
• Ethernet flow control is only for the link (wire) not over multiple links
112
Module 7 No Flow Control

Client
Configuration
Guidelines
Flow control Flow control
` `
ISIS Client ISIS Client
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
138

ISIS Client NIC settings
• The official tested/supported NIC for most devices is the Intel Pro
1000 MT Server (single or dual).
• Specific recommended settings:
– Frame size 1500 (or disabled)
– Receive Transcriptors 1024
– Send Transcriptors 1024
– Flow control: Generate and Respond
112
Module 7
Client
Configuration • HP 4300 cannot use the Intel Pro 1000 MT NIC – onboard NIC is
Guidelines
supported
• Avid Low Res Encoder uses 100mb on a Zone 2 switch
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
139

Module 8
112
Network Troubleshooting

Network Troubleshooting
112
• There are two major types of network problems:
Module 8
– Connectivity – device “A” and “B” cannot communicate reliably over the
Network
Troubleshooting network
– Network service failure. Examples, DHCP service, DNS, Active

Application L7 Directory. Service could be configured wrong or is broken
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
141

Connectivity Problems
• Four general types of connectivity problems
– Hardware failures: bad cables, connectors, NIC, switches routers, drivers, power
– Configuration:
• Logical: misconfigured IP addresses (wrong IP addresses, duplicate IP addresses),
net masks, routes, VLANs, disabled interfaces/ports
112 • Physical: things are not plugged in the right places
Module 8 – Capacity: the load on the network is more than the network can handle
Network
Troubleshooting – Blocked traffic: Firewalls or Access Control Lists (ACLs) are specifically
preventing the desired traffic
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
142

Network Service Problems
• Four general types of network service problems:
– Client is not configured correctly to access the network service
– Client is not making the request properly
112 – Service is not configured to allow the client access
Module 8 – Service is not providing correct or desired information
Network
Troubleshooting
•Troubleshooting network service problems

Application L7
requires a solid understanding of how the
Transport L4
Network: IP
service works
L3
Link: Ethernet L2
Physical L1
143

Troubleshooting 101
• Identify the symptom: When I do “X”, “Y” happens (or not)
• Isolate the problem –

– Where is the underlying failure happening, what device, what network
layer?
– Do I have a connectivity or a network service problem?
– Where on the network and/or which service?
112
• Identify the cause & fix
Module 8
Network
• Test and confirm problem is resolved
Troubleshooting
• Need to know the network and

Application L7 the network services involved –
Transport L4 if you don’t have the information, get it.
Network: IP L3 Avoid making assumptions.
Link: Ethernet L2
Physical L1
144

Troubleshooting Tools
• Ping
• Traceroute
• System status/statistics
112 – Ipconfig/ifconfig
– Netstat
Module 8 – Print route/show ip route
– Arp
Network
Troubleshooting
– Switch interface statistics/status
• Path Diag/Perfmeter – Unity

Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
145

Ping
• Ping, the networking Swiss Army knife -- it is useful for isolating
most network connectivity problems – it is your friend
• Ping sends an ICMP echo request to a target system and waits for
an ICMP echo reply
• Receiving an ICMP echo reply indicates basic physical and IP

112 connectivity is correct – although this does not rule out
intermittent network problems
Module 8
Network
• Ping failure when success is expected/desired requires
Troubleshooting investigation
Application L7
• Ping is sometimes blocked by firewalls or router ACLs (Access
Control Lists)
Transport L4
Network: IP L3
Link: Ethernet L2 • Syntax: ping [destination host name or IP address]

Physical L1
146

Ping Responses (Windows)
• “Ping request could not find host [NAME]. Please check the name and
try again.”
– Name cannot be resolved. DNS, hosts files, and NetBios failed to resolve the name.
Could be a client or server config problem. You may not be able to connect to the
name server
– Try the IP address instead of the name
112 • TTL/Time to Live exceeded – There where too many hops and a router
expired the echo request. Usually indicates a routing loop
Module 8
Network
Troubleshooting
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
147

Ping: Echo and Request Reply
• From 192.168.10.201: ping 172.20.5.156

• “Reply from 172.20.5.156: bytes=32 time<1ms TTL=253”
– Indicates network connectivity is working properly
– Note the response time “<1ms” – on average should expect 3ms or less – just a
rule of thumb
– Point of reference – on a good network, lightly loaded, 100 miles round trip
distance takes ~1ms
112 – If the network or target system is busy, replies may take longer or fail all
together – ICMP has lower priority than other types of traffic
Module 8 Source: Destination:
192.168.10.201 172.20.5.156
Network
Troubleshooting E ch
st oR
Echo R eq ue eq u
Requ o est
es t Ech uest
eq
Echo R
ly
h o Rep Ec h
Application L7
Ec oR
Echo R eply
eply
Transport L4 Net A Net B Net C Echo Net D
Reply
Network: IP L3
Link: Ethernet L2
Physical L1
148

Ping: Unreachable
• From 192.168.10.201: ping 172.20.5.156

• “Destination host (or network) unreachable”
– Indicates a device (not the destination) received the ICMP request, could not move it to
the next hop and sent back a message to the source
– Sometimes the IP address of the device sending failure message will appear in the
output
112
Module 8 Source: Router doesn’t know Destination:

192.168.10.201 how to get to Net 172.20.5.156
Network
Troubleshooting
“D”
est
Echo eq u
Requ
es t Ec ho R
b le
Application L7
e a cha
Unreac
hable Un r
Transport L4
Network: IP L3 Net A Net B Net C Net D

Link: Ethernet L2
Physical L1
149

Ping: Request Timed Out
• From 192.168.10.201: ping 172.20.5.156
• “Request timed out”
– No response received at all – no echo reply, no error response within the timeout
period
– Indicates at least one of three things
• The destination device is not available on the network
• Routing back towards the source is broken – could be a router or the default gateway
112 on the destination host
• Something is blocking ICMP/ping (e.g. firewall or ACLs)
Module 8 Source:
Destination:
Router doesn’t know 172.20.5.156
192.168.10.201
how to get to net “A”
Network
Troubleshooting
Echo q uest
Requ o Re Ec h
es t Ech oR
equ qu est
est Echo Re
Ech
Application L7 o Rep
ly
Transport L4 Net A Net B
Net C
Network: IP
Echo Reply
L3 Net D
Link: Ethernet L2
Physical L1
150

Troubleshooting Ping Timeouts
• From source, Ping a known good device on Net D (X)
– Success indicates a problem with destination device, ip, net mask, gateway, cable, etc.
– Failure may mean a routing issue
• From source, Ping the Net “D” ip address of the router (Y)
– Success means routing to from destination router is good
• From source, Ping the Net “B” ip address of routers (Z)
– Success most likely means source and first hop router configured correctly
– Failure means problem with Net A client or router
112 • Continue to ping the different routers in the network path until the problem is
isolated.
Module 8
Source: Destination:
Network
192.168.10.201 172.20.5.156
Troubleshooting
Application L7 Z
Transport L4
Y
Net B Net C
Network: IP L3 Net A
Link: Ethernet L2 Net D X
Physical L1
151

Ping Options
• Test Jumbo Frames (MTU 9000)
– Jumbo Frames can be used with TMs, AirSpaces for performance
improvement
– Ping can be used to test if the end to end network path can handle a certain
frame size
– -l: size of payload
– -f: Don’t fragment (DF) – tells network devices to not fragment the packet
– Ping –l [size] –f [dest IP address]
112
– Ping –l 8972 –f 172.20.5.156
Module 8
• Test reliability (quick and dirty)
Network
Troubleshooting – Ping –t 172.20.5.156
– Continuous ping – doesn’t stop until you hit Ctrl+C
– Some may fail, some may succeed – usually expect no failures except the first
Application L7 one or two. 1 out 20 failures or worse are definitely something to be
Transport L4
concerned about
Network: IP L3
Link: Ethernet L2
Physical L1
152

Traceroute
• Traceroute maps the network path a packet will take from source to
destination
• Traceroute starts by sending a packet with a TTL of one towards the
destination – the first router expires the packet and sends back a TTL
expired to the source – this is how the client learns about each hop
• This is repeated, incrementing the TTL by one each time
112
Source:
Module 8 192.168.10.201 Destination:
172.20.5.156
Network TTL
TTL 2 TTL 3 TTL
Troubleshooting
TT L 1 Expires
4
w
TTL
it h I P TTL
Ms g
xpire Expire Msg with IP
Application L7 ExpiEre Expires Expires
Reply – no TTL expire
Msg w
Transport L4 i th I P
Network: IP L3
Net A Net B Net C
Link: Ethernet L2 Net D
Physical L1
153

Traceroute/Tracert
•Windows command: tracert [name or IP]
IP address returned from routers that
expired the packet
112 TTL
Module 8
Network
Troubleshooting Reverse name resolution of the IP address returned
by router via expire msg
Application L7 Each TTL is tried three times and the round trip
times are reported Response from the destination device
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
154

Ipconfig /all
•Great way to get info about most of the interesting network configurations
•Quick overview of all network interface configs and status
•If you don’t have link, the interface will show as “Media Disconnected”
112 **
*
Module 8
Network
Troubleshooting
*
*
Application L7
**
**
Transport L4
*
Network: IP L3
Link: Ethernet L2
*
Physical L1
155

Netstat –se (Windows)
• Used for checking network statistics (activity & errors) for Ethernet, IP,
TCP, UDP
In/Out Ethernet activity
Bad Ethernet packets - problem
112 IP activity
Module 8 Reassembly failures: indicates

not all fragments received –
Network takes ~60 seconds for counter
Troubleshooting
to increment from time of
packet drop
ISIS uses UDP for
Application L7
reads/writes – useful for
finding potential ISIS
Transport L4 problems due to packet drops
Network: IP L3
Link: Ethernet L2
Physical L1
156

ARP = Address Resolution Protocol
• Systems remember/cache IP to MAC address mappings (ARP) for up to 15
minutes on Windows)
• Incorrect/stale or nonexistent arp information can prevent communication

with devices on the LAN
• arp –a :shows the contents of the arp cache
112 • arp –d :clears the contents of the arp cache. The system will try to
repopulate the cache the next time it tries to connect to a device
Module 8
Network
Troubleshooting
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
157

Switch Interface Statistics
• Log in to switch -> enable mode.

– “show interface”
112
Module 8
Network
Troubleshooting
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
158

Switch Status
• Show vlan” – summary shows configuration and status of vlans
• “Show interfaces summary” – shows packet statistics for all interfaces
• “Show interfaces status” – shows current state of interfaces
112
Module 8
Network
Troubleshooting
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
159

PathDiag & Perfmeter
• PathDiag(ISIS) and Perfmeter(MN) are great tools for eliminating the network
as a suspect.
• If you can achieve the performance benchmarks, this is a strong indication that
the network is sound
112 •Some issues are related

to number of clients, you
may need to run
Module 8
PathDiag on multiple
clients at the same time
Network
Troubleshooting •Failures/poor
performance may
indicate a network,
software, hardware,
Application L7 or configuration problem
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
160

IP Fragments
• When an IP datagram is too large to go on the network (e.g. > 1500
bytes) it must be fragmented
• ISIS frequently uses large datagrams – over 50,000 bytes
• All fragments within an IP datagram must reach the destination and be

112 reassembled or all fragments will be dropped
Module 8
Network
Troubleshooting
Application L7
Transport L4
Network: IP L3
Link: Ethernet L2
Physical L1
161

IP Fragmentation/Reassembly
IP Payload Sender
Length 4000 bytes
IP Packet IP Packet IP Packet

ID, Offset 0, ID, Offset 1480, ID, Offset 2960,
More fragments More fragments No More Frag
112 MTU: 1500
Module 8
General Network
Network
Troubleshooting
Application L7
Transport L4
IP Payload
Network: IP L3 Length 4000 bytes
Link: Ethernet L2 Receiver
Physical L1
162

Module 9
112
Appendix

Foundary Switch Configuration “A”
ver 02.3.01T3e3
!Avid version 1.1 5/01/2006 #Comment
!
global-stp
!
!
vlan 1 name DEFAULT-VLAN by port #Any port not explicitly assigned to a VLAN
is ! # implicitly part of
VLAN 1
112 vlan 10 by port
untagged ethe 1 to 12 ethe 25 #Associates ports 1-12, 25 with VLAN 10
router-interface ve 10 #Creates a virtual router interface for all of VLAN 10
Module 9 !
vlan 20 by port
Appendix
untagged ethe 13 to 22 ethe 26 #similar to VLAN 10
router-interface ve 20
!
vlan 40 by port #Optional VLAN 40
untagged ethe 23
router-interface ve 40
164

Foundary Switch Configuration “A” (continued)
qos mechanism strict #Quality of Service strict – first come first served
hostname avidconfiga #Name of the switch
interface ethernet 1 #Configuration for Ethernet port nuumber
one
priority 7 #Which queue traffic from this port gets put into
no flow-control #Turns flow control off
!
112 interface ethernet 2
priority 7
no flow-control
Module 9
…
Appendix
interface ethernet 23
priority 7
no flow-control
165

Foundary Switch Configuration “A” (continued)
interface ethernet 24 #Config for port number 24 – this is used for corporate uplink
port-name CorpUplink #Port name – optional
route-only #Treat this interface as a router interface only – no switched Ethernet
ip address 10.10.10.10 255.255.255.0 #Sets the IP address for this port and this port only
priority 7
no flow-control
!
interface ethernet 25 #Ten gig port config
priority 7
!
112 interface ethernet 26 #Ten gig port config
priority 7
!
Module 9
interface ve 10 #Configuration for virtual interface “10”-associated with VLAN 10 in the beginning of
config
Appendix
ip address 192.168.10.2 255.255.255.0
!
interface ve 20 #Configuration for virtual interface “20”-associated with VLAN 20 in the beginning of
config
ip address 192.168.20.2 255.255.255.0
!
interface ve 40
ip address 192.168.40.2 255.255.255.0
!
end
166

Cisco Switch Configuration “A”
!Avid version 1.1 5/01/2006

version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service compress-config
112 !
hostname avidconfiga #Set hostname to “avidconfiga”
!
Module 9 boot-start-marker
boot-end-marker
Appendix
!
no aaa new-model
vtp mode transparent
ip subnet-zero
!
no file verify auto
spanning-tree mode pvst
spanning-tree extend system-id
power redundancy-mode redundant
167

Cisco Switch Configuration “A” (continued)
vlan internal allocation policy ascending
!
vlan 10,20,40 #Defines what VLANs exist
!
interface GigabitEthernet1/1 #Configuration for port 1
switchport access vlan 10 #Associates this port with VLAN 10
switchport mode access #Sets port mode to access – only hosts should be connected to this port, not
switches
spanning-tree portfast #Speeds up spanning tree cycle to several seconds from about 30 seconds
112 !
interface GigabitEthernet1/25
switchport access vlan 20 #Associates this port with VLAN 20
Module 9 switchport mode access
spanning-tree portfast
Appendix
!
interface GigabitEthernet1/47
switchport access vlan 40
switchport mode access
spanning-tree portfast
!
168

Cisco Switch Configuration “A” (continued)
interface GigabitEthernet1/48 #Configuration for corporate uplink port
no switchport #Turns off Ethernet switching for this port – makes it a dedicated port
ip address 10.10.10.10 255.0.0.0
no ip proxy-arp
!
interface TenGigabitEthernet1/49 #10 gig port config
switchport access vlan 10
switchport mode access
interface Vlan1 #Default VLAN – usually has no members

112 no ip address
!
interface Vlan10 #VLAN 10 config
Module 9 ip address 192.168.10.2 255.255.255.0
!
Appendix interface Vlan20 #VLAN 20 config
ip address 192.168.20.2 255.255.255.0
!
interface Vlan40
ip address 192.168.40.2 255.255.255.0
!
no ip http server
• …
169

Switch Command Cheat Sheet - Foundry
Create VLAN/Enter VLAN config mode
SwitchHostName(config)#vlan [#]
SwitchHostName(config-vlan-#)#
Add ports into VLAN
SwitchHostName(config-vlan-x)#untagged ethernet [y] to [z]
Create VLAN routing interface (From VLAN config mode)
112 SwitchHostName(config-vlan-x)#router-interface ve [VLAN int #]
Enter VLAN interface config mode
Module 9 SwitchHostName(config)#interface ve [vlan int #]
SwitchHostName(config-vif-int #)#
Appendix
Assign IP address to VLAN routing interface
SwitchHostName(config-vif-int #)# ip address [IP] [mask]
Configure port to be routing interface & assign IP address
SwitchHostName(config)#interface ethernet [port #]
SwitchHostName(config-if-e1000-#)#route-only
SwitchHostName(config-if-e1000-#)# ip address [IP] [mask]
170

Switch Command Cheat Sheet - Cisco
Create VLAN/Enter VLAN config mode
SwitchHostName(config)#vlan [#]
SwitchHostName(config-vlan)#
Add ports into VLAN (do for each port)
SwitchHostName(config)#interface gigabitethernet 1/[port #]
SwitchHostName(config-if)#switchport access vlan [vlan #]
SwitchHostName(config-if)#switchport mode access
112 Enter VLAN interface config mode (do not need to create the VLAN
interface separately)
Module 9
SwitchHostName(config)# interface vlan [VLAN int #]
Appendix SwitchHostName(config-if)#
Assign IP address to VLAN routing interface
SwitchHostName(config-if)# ip address [IP] [mask]
Configure port to be routing interface & assign IP address
SwitchHostName(config)#interface gigabitethernet 1/#
SwitchHostName(config-if)#no switchport
SwitchHostName(config-if)# ip address [IP] [mask]
171

Eight Fallacies of Distributed Computing
• 1-The network is reliable
– What zone are you?
– Anyone else down? Where are they connected? Switches fail!
• 2-Latency is zero
– Be patient this is client/server architecture!
• 3-Bandwidth is infinite
– You have bandwidth management capabilities
112
• 4-The network is secure
– Only for the naïve…but security is not a common Avid problem
Module 9
• 5-Topology doesn't change
Appendix
– Your IT Dept will make changes that affect your Avid network
• 6-There is one administrator
– (administrator/avid is common in our world)
• 7-Transport cost is zero
– Getting from the application to the transport layer takes resources
• 8-The network is homogeneous
– It is for us…for now anyway. Windows. Linux, Mac. Protocols. Interop.
172

Recommended Reading – Wikipedia Links
• Recommended reading:
• http://en.wikipedia.org/wiki/Ethernet
• http://en.wikipedia.org/wiki/Gigabit_Ethernet
• http://en.wikipedia.org/wiki/10_gigabit_Ethernet
• http://en.wikipedia.org/wiki/Duplex_%28telecommunications%29
• http://en.wikipedia.org/wiki/Multimode_fibre
• http://en.wikipedia.org/wiki/Singlemode_fibre
• http://en.wikipedia.org/wiki/Category_5_cable
• http://en.wikipedia.org/wiki/Registered_jack
• http://en.wikipedia.org/wiki/SC_connector
• http://en.wikipedia.org/wiki/RS-232
• http://www.taltech.com/resources/intro-sc.html
• http://en.wikipedia.org/wiki/Telnet
• http://en.wikipedia.org/wiki/LAN
• http://en.wikipedia.org/wiki/Wide_area_network
112
• http://en.wikipedia.org/wiki/Media_access_control
• http://en.wikipedia.org/wiki/MAC_address
• http://en.wikipedia.org/wiki/OSI_model
• http://en.wikipedia.org/wiki/Vlan
• http://en.wikipedia.org/wiki/Maximum_transmission_unit
• http://en.wikipedia.org/wiki/Ping
Module 9 • http://en.wikipedia.org/wiki/Spanning_tree_protocol
• http://en.wikipedia.org/wiki/Address_Resolution_Protocol
• http://en.wikipedia.org/wiki/Ipv4
Appendix • http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing
• http://en.wikipedia.org/wiki/Subnet_mask
• http://www.swansontec.com/sbinary.htm
• http://en.wikipedia.org/wiki/Routing
• http://en.wikipedia.org/wiki/Router
• http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol
• http://en.wikipedia.org/wiki/Tftp
• http://en.wikipedia.org/wiki/Ftp
• http://en.wikipedia.org/wiki/Http
• http://en.wikipedia.org/wiki/Smtp
• http://en.wikipedia.org/wiki/Dns
• http://en.wikipedia.org/wiki/Transmission_Control_Protocol
• http://en.wikipedia.org/wiki/User_Datagram_Protocol
• http://en.wikipedia.org/wiki/Traceroute
173

Avid Supported Switches (as of 4/20/07)
• Foundry FESX424
• Cisco 4948-10GE
• SMC 8724ML3
• Extensive testing has been done with the chassis based Cisco 4500 and
6500 switches as well. Here is a list of the blades we support for those
units:
112
Module 9
Appendix
WS-X4506-GB-T WS-X6708-10GE
174

Online Subnet & CIDR Calculators
• www.subnet-calculator.com/
• www.subnet-calculator.com/cidr.php
– For those of us who are mathematically-
challenged!
112
Module 9
Appendix
•Results of the CIDR calculation provides the •Results of the subnet calculation provide the
wildcard mask, for use with ACL (Access Control hexadecimal IP address, the wildcard mask, for use
Lists), CIDR network address (CIDR route), with ACL (Access Control Lists), subnet ID,
network address in CIDR notation and the CIDR broadcast address, the subnet address range for the
address range for the resulting CIDR network. resulting subnet network and a subnet bitmap.
175

IP Packet Header
+ Bits 0 - 3 4-7 8 - 15 16 - 18 19 - 31
Type of Service
Version Header
0 (Diffserv and Total Length
(IPv4) length
ECN)
32 Identification Flags (DF, MF) Fragment Offset
112 64 Time to Live (TTL)

Protocol (e.g.
Header Checksum
UDP,TCP)
Module 9
96 Source Address
Appendix
128 Destination Address
160 Options

160/192+ Data

176

Ethernet
• Ethernet Frame Header
• The most common Ethernet Frame format, type II
112
Module 9
Appendix
177

TCP Packet Header
+ Bits 0–3 4–9 10–15 16–31

0 Source Port Destination Port
32 Sequence Number
64 Acknowledgment Number
112 96
Data
Offset
Reserved Flags Window
128 Checksum Urgent Pointer

Module 9 160 Options (optional)
Appendix
160/192
+ Data

178

IP Fields of Interest
• Header length: total length in of the header in 32 bit words
• Total length: total length of datagram including header and data (8 bit bytes)
• ID field: unique number for each full datagram
• Fragment flags: don’t fragment, more fragments
• Fragment offset: used for determining order of fragments
• TTL: Time to Live, number of hops
• Protocol: what type of data is in the packet (e.g. UDP, IP, ICMP)
112 • Source and destination IP addresses
• Header length: total length in of the header in 32 bit words
Module 9 • Total length: total length of datagram including header and data (8 bit bytes)
• ID field: unique number for each full datagram
Appendix
• Fragment flags: Don’t fragment, more fragments
• Fragment offset: used for determining order of fragments
• TTL: Time to Live, number of hops
• Protocol: What type of data is in the packet (e.g. UDP, IP, ICMP)
• Source and destination IP addresses
179

TCP Field Description
• Source port: This field identifies the sending port.
• Destination port: This field identifies the receiving port.
• Sequence number: The sequence number has a dual role. If the SYN flag is present then
this is the initial sequence number and the first data byte is the sequence number plus 1.
Otherwise if the SYN flag is not present then the first data byte is the sequence number.
• Acknowledgement number: If the ACK flag is set then the value of this field is the
sequence number the sender expects next.
• Data offset: This 4-bit field specifies the size of the TCP header in 32-bit words. The
minimum size header is 5 words and the maximum is 15 words thus giving the minimum
size of 20 bytes and maximum of 60 bytes. This field gets its name from the fact that it is
also the offset from the start of the TCP packet to the data.
112 • Reserved: 6-bit reserved field for future use and should be set to zero.
• Flags (a.k.a Control bits)
– This field contains 6 bit flags:
Module 9
– URG: Urgent pointer field is significant
Appendix
– ACK: Acknowledgement field is significant
– PSH: Push function
– RST: Reset the connection
– SYN: Synchronize sequence numbers
– FIN: No more data from sender
• Window: The number of bytes the sender is willing to receive starting from the
acknowledgement field value.
• Checksum: The 16-bit checksum field is used for error-checking of the header and data.
• Options
180

UDP Fields
•Source port: This field identifies the sending port when meaningful and
should be assumed to be the port to reply to if needed. If not used then it
should be zero.
•Destination port: This field identifies the destination port and is required.
•Length: A 16-bit field that specifies the length in bytes of the entire
datagram: header and data. The minimum length is 8 bytes since that's the
112 length of the header. The field size sets a theoretical limit of 65,527 bytes for
the data carried by a single UDP datagram.
Module 9 •Checksum: The 16-bit checksum field is used for error-checking of the
Appendix
header and data.
+ Bits 0 - 15 16 - 31
0 Source Port Destination Port
32 Length Checksum

64 Data

181

Endnote
• This course was developed from material provided by Christopher

112 Quinones, Principal Systems Engineer at Avid Technology Inc. and the
Avid Training Services Consortium: Joseph Barneson, Ryan Nadeau,
Module 9 Stacy Saveall, and Michael Zwieg.
Appendix
182

112 Avid Networking - Final Version

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

112 Avid Networking - Final Version

Uploaded by

Copyright:

Available Formats

WG112 Avid Networking

An Introduction to Networking Concepts Used in

Avid Training Services Copyright 2007, Avid Technology, Inc.

Unity MediaNet Customers

Maintenance and Troubleshooting

WG112 Avid Networking

Installation and Support

WG433 Interplay ACSR

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

• Provide solid foundation in networking theory

• Provide hands on experience implementing and troubleshooting

Avid Training Services Copyright 2007, Avid Technology, Inc.

• Network Design & Implementation

Avid Training Services Copyright 2007, Avid Technology, Inc.

• The design is the blueprint of how the network is “supposed” to be

• When doing “networky” things, always understand the design before

Avid Training Services Copyright 2007, Avid Technology, Inc.

•Small ISIS Workgroup

•Edge Switch •Interplay Assist

.10 LAN .20 LAN

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Elements of Network Design

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

• Many of these protocols layer & interconnect with each other

• Understanding the nature of each layer and how they interact is

Avid Training Services Copyright 2007, Avid Technology, Inc.

• Link – Ethernet connects devices to each other in a LAN

• Network – IP allows connectivity between different networks – moves

• Session (not discussed)

• Presentation (not discussed)

• Application – (e.g. HTTP, ISIS) – the information the software needs

Avid Training Services Copyright 2007, Avid Technology, Inc.

Layer Function Unit #

Host Application (Flock, Interplay, HTTP)

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

• Signaling specifications – electrical voltages, laser strength,

Avid Training Services Copyright 2007, Avid Technology, Inc.

• RJ45: Copper 8-pin

• SC: Fiber Optical

112 Large connector

Module 2 • LC: Fiber Optical

• CX-4: Infiniband Copper

Avid Training Services Copyright 2007, Avid Technology, Inc.

Link: Ethernet L2 There is a minimum recommended cable length of 2 meters.

Physical L1 Shorter cables are known to cause network issues.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Avid Training Services Copyright 2007, Avid Technology, Inc.

Physical L1 (48) 1gb copper ports w/RJ45 connectors

Avid Training Services Copyright 2007, Avid Technology, Inc.

Integrated Storage Switch Integrated Expansion Switch