Layer 2 Models

How switches process incoming frames

When a switch receives a frame (flowchart here):

 

• It compares the receiving port's type (trunk or access) to the frame's format.
  • It drops the frame if (any):
    • The port is an access port while the frame has a Dot1q encapsulation format.
    • The port is a trunk port and the frame is not a Dot1q frame.
  • Otherwise, continue to process the frame.
• It drops the frame if the receiving port is a blocking port and the frame is not an STP frame.
• It determines which VLAN the frame is destined.
  • If the receiving port is a trunk (and so the frame is a Dot1q frame):
    • It gets the frame's destination VLAN number from the VLAN tag in the Dot1q header.
    • It checks if the switch itself has that particular VLAN configured.
      • If that VLAN is configured, it refers to that VLAN's MAC table:
        • If the frame's source MAC address is in the MAC table, it resets the entry's timer.
        • If not, it creates a new MAC entry in the table and starts a timer for it. When the timer expires (5 min), it removes the entry.
      • If that VLAN is not configured, the switch broadcasts the frame to all trunk ports (except the receiving port) that allow that VLAN number.
  • If the receiving port is an access VLAN (the frame is destined for that VLAN), it continues to process it. It sends it to a higher process if (any):
    • The frame is an STP frame.
    • The frame's destination MAC address is a CDP multicast address.
    • The frame's destination MAC address is a broadcast MAC address.
    • The frame's destination MAC address matches the active VLAN interface's MAC address.

How switches send frames

When a switch wants to send a frame (flowchart here):

 

• If the frame came from a higher-level process:
  • It checks if the outgoing port is up.
    • If outgoing port is up, send the frame out.
    • If outgoing port is not up:
      • It tries to find the active VLAN interface that is up, and then sends it out that interface.
      • If it cannot find such an interface, it finds the first VLAN that is allowed in the trunk that is configured on the switch.
        • If it can find such an interface, it encapsulates the frame with a Dot1q header with that VLAN number tag and sends it out to the trunk.
        • If no such trunk is configured, it drops the frame.
• If the frame came from a same-level process:
  • If the outgoing port is not up (not configured), it drops the frame. Otherwise, it continues the process
• It checks if the frame's destination MAC address is a unicast. If so:
  • If the outgoing port is the same as the incoming port, it drops the frame.
  • If the outgoing port is not the incoming port:
    • If the outgoing port is a trunk port:
      • If the frame is a Dot1q frame:
        • If the trunk port allows the tag in the frame, it sends the frame.
        • If the trunk port does not allow the frame's tag, it drops the frame.
      • If the frame is not a Dot1q frame:
        • If the trunk port allows the VLAN that the frame is destined for:
          • The switch encapsulates the Ethernet frame with a Dot1q header and sends it out the trunk port.
        • If the trunk port does not allow the VLAN that the frame is destined for, it drops the frame.
    • If the outgoing port is an access port:
      • If the frame is a Dot1q frame:
        • If the frame's tag is the same as the port's VLAN, it de-encapsulates the frame (to an Ethernet frame) and sends it out.
        • If the frame's destination tag is different from the port's VLAN number, it drops the frame.
      • If the frame is a regular Ethernet frame:
        • If the receiving port's VLAN is the same as the outgoing port's VLAN, it forwards the frame.
      • If not, it drops the frame.
• If the frame's destination MAC address is a multicast address:
  • For each and every port (trunk and access):
    • It checks if the destination VLAN is allowed in that port. If so, it sends the frame out that port with the appropriate format (see the unicast frame sending logic).
    • If the destination VLAN is not allowed, or if the port is the same as the receiving port, the switch will not forward the frame out that port.

How CSMA/CD is modeled

Packet Tracer models only certain aspects of the CSMA/CD process.

 

• Packet Tracer does not implement the process where each station continuously senses the channel.
• The program assumes that if a jam signal is not received, the medium is available for transmission.
• The program does not fragment a CPDU. Therefore, the Ethernet process only has to remember the previous PDU in the case of retransmission due to collision.
• The program does not implement the propagation time t from one end of a medium to the other. This forces all frames to take 2t to send.
• The program implements the binary exponential back-off algorithm (IEEE 802.3):
  • In the first collision, each station chooses either the 0 or the 1 slot time.
  • In the event of a second collision, each station picks from four possible slot times: 0, 1, 2, 3.
  • In the event of a third collision, each station randomly chooses a slot time from 0 to (2^3 - 1), or 0 to 7.
  • In the event of further collisions (from the 4th to the 15th collision), each station randomly chooses a slot time from 0 to (2^i - 1), where i is the number of collisions.
  • The frame is discarded after the 16th retry

How switches utilize Spanning Tree Protocol (STP)

• The STP is a technology that allows switches and bridges to communicate with each other to prevent loops in the network.
• When a switch/bridge is added to a network, it sends out Bridge Protocol Data Units (BPDU) announcing itself as root.
• If the switch/bridge has the lowest ID, it becomes the root.
• The root marks its ports as designated ports.
• Non-root switches/bridges mark the port closest to the root as root port. Every non-root switch/bridge will select one root port.
• Each segment of the network will elect one designated port:
  • If the port has the lowest root ID, it becomes the designated port.
  • If the port has the lowest path cost to the root, it becomes the designated port.
  • If the port has the lowest send ID, it becomes the designated port.
  • If the port has the lowest port ID, it becomes the designated port.
• Ports not marked as root or designated are marked as blocked. Additionally, in RSTP mode, if a port on a switch is connected to the switch itself, it is marked as a backup port, otherwise it is marked as an alternate port.
• The root bridge in the STP will periodically send BPDUs out while non root bridges will forward these frames when it is received.
• In the RSTP, all bridges periodically send BPDUs out with their current information.

When a switch receives a STP frame (flowchart here):

 

• If STP is disabled on that port, it drops the frame.
• If the switch is running the RSTP, it starts the migration delay timer.
  • If the migration delay has expired, change the port to run in the STP mode.
• STP checks the frame type.
  • If the frame type is configuration BPDU:
    • If the frame does not contain superior information, the switch drops the frame. The information is superior if it contains lower root ID, lower root path cost, lower bridge ID, or lower port ID.
    • Records the superior information and selects new root bridge and designated port if necessary. If the device was the root, sends a TCN BPDU through the root port.
    • If the BPDU is received on the root port, forward the frame out through designated ports.
  • If the frame type is Topology Change Notification (TCN) BPDU:
    • If the frame is received on a non-designated port, the switch drops the frame.
    • If the device is the root, the switch sets topology change flag to true in the BPDU.
    • If the device is not the root, the switch forward the frame out through root port.

When a switch receives a RSTP frame (flowchart here):

• If the switch is running the STP, it drops the frame.
• If the frame is an agreement frame, set the port to forwarding state and make it designated.
• If the frame contains superior information:
  • If the port has root guard enabled, block this port and mark it as inconsistent.
  • Otherwise:
    • If the frame is from myself, block this port and mark it as a backup port.
    • Otherwise make the received port the new root port and block all other non edge ports.
      • Send out a reply with the same information as the received BPDU but with the agreement flag set.
• If the frame contains inferior information:
  • If the information is from our root port, check for a better root port.
  • Otherwise:
    • If my root path cost is lower than the received root path cost, set my port to be designated forwarding.
    • If my root path costs are the same:
      • If my bridge ID is lower than the received bridge ID, set my port to be designated forwarding.
      • If my bridge ID is the same as the received bridge ID:
        • If my port ID is lower than the received port ID, set my port to be designated forwarding.
        • If my port ID is higher than the received port ID, set my port to be backup blocking.
      • Otherwise set my port to be alternate blocking.

How port security works

When switch receives a frame (flowchart here):

• If port security is on and the receiving port is not in dynamic mode port security processes the frame.
• It sets the last source MAC address and VLAN on the port from the received frame information.
• If any Mac entry exists with the same source MAC address:
• If the interface of the MAC entry is the same as the receiving interface and same VLAN as the receiving interface, the frame passes port security.
• Otherwise
  • If the MAC entry is a dynamic entry then removes the dynamic entry and:
    • If the maximum allowed secure MAC addresses is reached it drops the frame and goes to the violation mode.
    • If the maximum allowed secure MAC addresses is not reached the frame passes the port security process.
  • If the MAC entry is a static entry then it applies the violation mode because another port in the same VLAN has the same static MAC address.
• If MAC entry with the same source MAC does not exist:
• If the maximum allowed secure MAC addresses is reached, drops the frame
• Otherwise frame passes the port security process.

If the frame passes the security process and the sticky MAC address is on, on the received interface, the MAC entry gets added to the MAC table as a static entry.

A switch port can be configured with secure MAC addresses even if the port's line protocol is down.

When the port's line protocol changes from down to up, if there is a list of secure MAC addresses for the port waiting to be added to the MAC table, the port security checks the MAC entries with the same VLAN address as the current port.

 

• If there is the same MAC address on the current port which is an sticky MAC, port security deletes the secure MAC from the list and does not add it to the MAC table.

• If the MAC address does not exist in the MAC table, then it adds a MAC entry for that secure MAC to the MAC table.

How DTP decides on the mode of the port

DTP has the responsibility of setting switch port's modes.

Each switch port sends a DTP frame out about its administration mode and operation mode on a regular basis

• If the port is configured with dynamic administrative mode and nonegotiate is not on.

When the switch port on the other side of the link receives the DTP update it (flowchart here):

 

• If there is a VTP domain name mismatch it drops the frame
• If the port is configured to be in access or trunk administrative mode it drops the frame.
• If the port is dynamic and is not in the nonegotiate state it processes the frame.
• If the same MAC entry (with the same source MAC address as the received frame) exists on the receiving port then restart the timer for that entry.
• DTP process updates the port's operational mode based on the received DTP port status.
• Otherwise it adds a new MAC entry to the MAC table and sets a timer for it.
• DTP process updates the port's operational mode based on the received DTP port status.

To update the port operational mode DTP (flowchart here):

 

• If the number of neighbors on that port which are sending DTP frames is more than one or is equal to zero
• Change the operational mode of the receiving port to static access.
• If the number of neighbors is equal to 1
• If local port's administrative mode is dynamic auto
• If remote neighbor's port is in the administrative mode of desirable or trunk set the operation mode of local port to trunk. Otherwise, set operation mode to static access.
• If local port's administrative mode is dynamic desirable
• If remote neighbor's port is in administrative mode of desirable or trunk or auto set the operation mode of local port to trunk. Otherwise, set operation mode to static access.
• If the local port's administrative mode is access then drop the frame and do not process any DTP frames.

How switches processing incoming VTP frames

When a switch receives a VTP frame (flowchart here):

 

• If the switch is in VTP Transparent mode:
  • Forwards VTP frame to all other trunk ports
• If the VTP frame is an Advertisement Request frame:
  • If the domain name on the VTP frame does not match the switch's, then drop the frame and stop.
  • Send out a Summary Advertisement frame.
  • Send out a Subset Advertisement frame.
• If the VTP frame is a Summary Advertisement frame:
  • If the switch's domain name is set and the one in the VTP frame is different, then drop the frame and stop.
  • If the switch's domain name is not set, then set the domain name to be the one in the VTP frame, and recalculate MD5.
  • If the MD5 in the VTP frame does not match the on the switch, then drop the frame and stop.
  • If the version is different, then take the one in the VTP frame.
  • If the config revision in the VTP frame is smaller than the one on the switch:
    • Send out a Summary Advertisement frame
  • If the config revision in the VTP frame is larger than the one on the switch:
    • If the followers field is 0:
      • Send out an Advertisement Request frame
    • Wait for the Subset Advertisement frames
  • If the config revision in the VTP frame is the same as the one on the switch:
    • Drop the frame
• If the VTP frame is a Subset Advertisement frame:
  • If the domain name on the VTP frame does not match the switch's, then drop the frame and stop.
  • If not expecting a Subset Advertisement, then drop the frame and stop.
  • If the config revision in the VTP frame is different than the expecting one, then drop the frame and stop.
  • If the sequence number in the VTP frame is different than the expecting one, then drop the frame and stop.
  • Add the subset to the reply
  • If the VTP frame is the last expecting subset:
    • Update the VLAN database with the received subsets
    • Send out a Summary Advertisement frame
    • Send out a Subset Advertisement frame

When do switches send out VTP frames

When do switches send out Advertisement Requests:

When the switch detects a VTP configuration change and it is in VTP Client mode

When receiving a Summary Advertisement but there is no subset following it

 

When do switches send out Summary Advertisements:

When a trunk port comes up and the switch is already advertising VTP

Every 5 minutes

When receiving a Summary Advertisement with its config revision smaller than the switch's

 

When do switches send out Subset Advertisements:

When a trunk port comes up and the switch is not already advertising VTP

When a local VLAN change is detected and the switch is in VTP Server mode

When the switch detects a VTP configuration change and it is in VTP Server mode

After updating VLAN database on the receiving of Subset Advertisements

When receiving a Advertisement Request How HDLC Works

• HDLC is the default data link protocol for serial interfaces.
• Sends keepalives periodically to the other end of the link.
• When it receives a keepalive, it brings up the line protocol.
• If it does not receive a keepalive from the other end for a certain period of time, it brings down the line protocol.
• If the interface is configured to not use keepalives, it would bring up the line protocol even if it does not receives keepalives from the other end.

 

How Etherchannel Works

When a multilayer switch receives a packet (flowchart here):

• Check if the port is active in etherchannel
• If the frame is LACP/PAgP
  • If the partnerDevice in the etherchannel portData matches the partnerDevice in the received frame
    • Negotiation is successful and the port is changed either to trunk or access mode
• If the port is not active in the etherchannel
  • Send the packer to the next highest layer for further processing

When a multilayer switch sends a packet: 

• A load balance method is selected depending on what user selects.
• If no method is selected, uses source Mac address as the load balance method.
• The frame is then sent to the lower layer for further processing.

How Multilayer Switching Works

• The new 3560 switch in Packet Tracer is a multilayer switch.
• It has switching as well as routing capabilities.
• It supports IPv4 and IPv6 routing protocols such as RIP, EIGRP, and OSPF.
• Each physical interface can be independently configured to be switched or routed ports. Switched ports are layer 2 ports that allow only layer 2 configurations and functionalities. Routed ports allow layer 3 functionalities just like a port on a router. They are switched ports by default.

 

How HDLC Works

• HDLC is the default data link protocol for serial interfaces.
• Sends keepalives periodically to the other end of the link.
• When it receives a keepalive, it brings up the line protocol.
• If it does not receive a keepalive from the other end for a certain period of time, it brings down the line protocol.
• If the interface is configured to not use keepalives, it would bring up the line protocol even if it does not receives keepalives from the other end.

How PPP Works

• PPP is a data link protocol for serial interfaces as well as modem connections.
• PPP requires authentication before a connection is made.  The authentication types available in Packet Tracer are none, PAP, and CHAP.
• Each side of the connection can use different authentication methods, but the other end must support them.
• The authentication type set on one side is the authentication type required on the other side.
• Setting authentication to none means allow the other side to authenticate without any username or password checking.
• Both PAP and CHAP use a username and password to authenticate the other side.  CHAP provides a stronger encryption and authentication method.

How PPPoE Works

The Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol for encapsulating Point-to-Point Protocol (PPP) frames inside Ethernet frames. By using PPPoE, users can virtually "dial" from one machine to another over an Ethernet network, establish a point to point connection between them and then transport data packets over the connection. (flowchart here):

• PPPoE is a client-server model.
• PPPoE has two distinct stages.
  • Discovery stage:
    • There are four steps to the Discovery stage. When it completes, both peers know the PPPoE SESSION_ID and the peer's Ethernet address, which together define the PPPoE session uniquely.
  • PPP Session stage
    • Server assigns an IP address from the configured pool to the client.
    • Based on the configuration on server side it may need to authenticate the client through:
      • AAA server authentication
      • Locally saved username/password database.
      • No authentication needed.
• Client uses the assigned IP address
  • When PPPoE client sending a packet out:
    • Encapsulates all the outgoing packets in the following packets:
      • PPP frame, PPPoE frame adding the session id to the id field of PPPoE header, and Ethernet frame (destination MAC address of server)
  • When Client receives a PPPoE packet:
    • If the session ID matches one of the client's that the server has negotiated with, it de-encapsulates the packet and send it to PPP for future processing.
• Server uses the session ID to distinguish between different clients:
  • When server receives a PPPoE frame, it checks the received PPPoE session ID and if session ID is known:
    • It removes PPPoE header and sends it to PPP for further processing
    • Otherwise it drops the packet
  • When server sends a packet:
    • If packet is destined for a particular client that a session has been negotiated with:
      • It encapsulates the packet in PPP and PPPoE frames with the particular session ID and sends it to the client
      • Otherwise, it drops the packet.

 

How Frame Relay Works

• Frame Relay provides connection-oriented data link layer communication. This means that a defined communication exists between each pair of devices and that these connections are associated with a connection identifier. This service is implemented by using a Frame Relay virtual circuit, which is a logical connection created between two data terminal equipment (DTE) devices across a Frame Relay packet-switched network. Virtual circuits provide a bidirectional communication path from one DTE device to another and are uniquely identified by a data-link connection identifier (DLCI). A number of virtual circuits can be multiplexed into a single physical circuit for transmission across the network. This capability often can reduce the equipment and network complexity required to connect multiple DTE devices.
• A Frame Relay PVC is a logical link whose endpoints and class of service are defined by network management. A PVC consists of the originating Frame Relay network element address, originating data-link control identifier, terminating Frame Relay network element address, and termination data-link control identifier. "Originating" refers to the access interface from which the PVC is initiated. "Terminating" refers to the access interface at which the PVC stops. Many data network customers require a PVC between two points. DTE that needs continuous communication uses PVCs.
• LMI virtual circuit status messages provide communication and synchronization between Frame Relay DTE and DCE devices. These messages are used to periodically report on the status of PVCs, which prevents data from being sent into black holes (that is, over PVCs that no longer exist).
• Frame Relay Inverse ARP can be used as a method of building dynamic routes in Frame Relay networks running IP. Inverse ARP allows the communication server to discover the protocol address of a device associated with the virtual circuit. Inverse ARP is used instead of the frame-relay map command which allows you to define the mappings between a specific protocol and address and a specific DLCI. Inverse ARP is not needed for a point-to-point interface because there is only a single destination and discovery is not required.
• Frame Relay subinterfaces provide a mechanism for supporting partially meshed Frame Relay networks. Most protocols assume transitivity on a logical network; that is, if station A can talk to station B, and station B can talk to station C, then station A should be able to talk to station C directly. Transitivity is true on LANs, but not on Frame Relay networks unless A is directly connected to C.
• Configuring Frame Relay subinterfaces ensures that a single physical interface is treated as multiple virtual interfaces, which allows you to overcome split horizon rules. Packets received on one virtual interface can be forwarded to another virtual interface, even if they are configured on the same physical interface. Subinterfaces address the limitations of Frame Relay networks by providing a way to subdivide a partially meshed Frame Relay network into a number of smaller, fully meshed (or point-to-point) subnetworks. Each subnetwork is assigned its own network number and appears to the protocols as if it is reachable through a separate interface.
• When a Frame Relay Cloud receives a frame, it looks up the connection created by the user. If a connection is found, the Cloud forwards the frame out the port specified in the connection. If the connection is not found, the frame is dropped. When a router receives a frame, it looks up the DLCI specified in the frame. If the DLCI is mapped to an interface, the frame is passed to that interface. If the DCLI is mapped to an interface, the frame is dropped by the router.

How Cable/DSL Works

• DSL
  • A digital subscriber line (DSL) connection is a high-speed connection that uses the same wires as a regular telephone line. DSL services are dedicated point-to-point network access over twisted-pair copper wire on the local loop between a network service provider's central office and the customer site.
  • DSL circuits connect DSL modems to a digital subscriber line access multiplexer (DSLAM) creating three data channels: a high-speed downstream channel, a low-speed upstream channel, and a basic telephone service channel. The DSLAM (the cloud) provides one of the main differences between DSL and cable modems. Because cable-modem users generally share a network loop that runs through a neighborhood, adding users means lowering performance in many instances. ADSL provides a dedicated connection from each user to the DSLAM. Therefore, users won't see a performance decrease as new users are added.
  • A DSL Modem can be used to connect to a modem port defined in the Cloud using telephone wire. Another device (such as a PC or a router) is connected to Ethernet port on the DSL Modem. The DSL Modem acts like a bridge forwarding traffic from one port to the other port.

Cable

• In a cable TV system, signals from the various channels are each given a 6-MHz slice of the cable's available bandwidth. When a cable company offers internet access over the cable, data can use the same cables because the cable modem system puts downstream data into a 6-MHz channel. Thus Internet downstream data takes up the same amount of cable space as any single channel of programming. Upstream data uses 2-MHz channel.
• Just like DSL, high-speed cable requires a modem at the customer end and a cable modem termination system (CMTS) at the provider end. CMTS (the Cloud) functions like DSLAM in a DSL environment. The CMTS takes the traffic coming in from a group of customers on a single channel and routes it to an Internet service provider for connection to the Internet. A CMTS enables many connections to the Internet through a single 6-MHz channel. A single channel is capable of up to 40 Megabits per second of total throughput.
• Unlike DSL, data channels to CMTS are shared. If these channels are saturated with user traffic, the theoretical bandwidth may not be achieved. However, this particular performance issue can be resolved by the cable company by adding a new channel and splitting the user base. Another difference between DSL and cable is that the downstream information flows to all connected users. It is up to the individual network connection to decide whether a particular block of data is intended for it or not. On the upstream side, information is sent from the user to the CMTS directly without other users seeing it.
• A Cable Modem can be used to connect to a coax port defined in the Cloud using coaxial wire. Another device (such as a PC or a router) is connected to an Ethernet port on the Cable Modem. The Cable Modem acts like a bridge forwarding traffic from one port to the other port.

ISP

• The Cloud under WAN Emulation is used to model an ISP.
• Multiple Ethernet ports can be added to the Cloud emulating ISP networks.
• Multiple modem ports can be added to the Cloud emulating a DSLAM.
• Multiple coax ports can be added to the Cloud emulating a CMTS.
• Multiple modem ports can be mapped to a single Ethernet port that is defined to use DSL as the provider network.
• Multiple coax ports can be mapped to a single Ethernet port that is defined to use Cable as the provider network.
• For DSL connections, traffic received on a modem port will be forwarded to the corresponding Ethernet port. Traffic received on an Ethernet DSL port will be forwarded to the correct DSL modem.
• For Cable connections, traffic received on a coax port will be forwarded to the corresponding Ethernet port. Traffic received on an Ethernet Cable port will be forwarded to all coax ports connected to that Ethernet port.

How REP Works

• Resilient Ethernet Protocol (REP) is a protocol used in order to replace the Spanning Tree Protocol (STP) in some specific Layer 2 network designs. REP is available in the Switch IE-2000.
• Segments
• REP uses the concept of segment. A segment ID is configured on switches's interfaces belonging in the same segment.
• Two edge ports are configured where the REP segment ends. They are not to connect with each other.
• One port is blocking in a segment, called the alternate port.
• Other ports are transit ports.
• REP Port Roles
• REP ports are either failed, open or alternate.
• All regular segment ports start out as failed ports.
• After adjacencies have been determined, ports move to Alternate state.
• After negotiations on Alternate port is done the remaining ports move to open state while one port stays in Alternate state.
• When a failure occurs on a link all ports move to failed state.
• When the Alternate port receives the notification it is moved to open state.
• REP Link Status Layer (LSL)
• Establishing connectivity with a unique neighbor.
• Periodically checking the integrity of the connection with the neighbor.
• Sending and receiving messages for higher-layer state machines.
• Acknowledging data received from the neighbor.
• Limiting rates of Protocol Data Units (PDUs).
• Hardware Flood Layer (HFL)
• HFL is the REP module that facilitates rapid convergence after link failures.
• HFL sends multicast PDUs to a special MAC address (0100.0ccc.ccce) on the REP administrative VLAN instead of sending PDUs to the BPDU MAC address like LSL.
• REP Operation
• When a port is line protocol up, REP sends out a LSL Hello Message and starts an election or a relection for port roles of all ports in the segment.
• Upon receiving a LSL, REP sends acknowlegment to indicate the port is functional.
• When a port is line protocol down,the port becomes a failed port. REP cancels the LSL Hello Message timer and flood the segment with a HFL topology change message.
• Upon receiving a HFL, REP will determined which role the receiving port will take on.

How PTP Works

• Precision Time Protocol (PTP) is a protocol used to synchronize the clocks in packet-based networks that include distributed device clocks of varying precision and stability.
• Adding PTP to a network can compensate for these latency and delay problems by correctly adjusting device clocks so they stay synchronized with one another.
• PTP works in IE-2000 switches.
• PTP Device Types
• Grandmaster Clock: is the most accurate master clock in the selection process.
• Ordinary Clock (PTP Client): a PTP client installed on servers, network-monitoring and performance-analysis devices, or other devices that want to use the precise timing information provided by PTP.
• Boundary Clock: on devices that have serveral physical ports, and each port is behaving like an ordinary clock. All ports in the same device shares the same local clock.
• Transparent Clock: forwards all messages like an ordinary clock but also measures the residence time of a packet in the switch. The residence time is the time that a packet takes to traverse the transparent clock.
• Supported MTP Modes
• Boundary Mode: A switch clock in boundary mode participates in the selection of the most accurate master clock. If more accurate clocks are not detected, that switch clock becomes the master clock. If a more accurate clock is found among the slave clocks, then the switch synchronizes to that clock and becomes a slave clock. After initial synchronization, the switch and the connected devices exchange timing messages to correct the changes caused by clock offsets and network delays.
• End-to-End Mode: A switch clock in end-to-end transparent mode synchronizes all switch ports with the master clock. This switch does not participate in master clock selection and uses the default PTP clock mode on all ports.
• Forward Mode: A switch clock in forward mode allows incoming PTP packets to pass-through the switch as normal multicast traffic. When the switch is in PTP forward mode, PTP configuration is not available except when changing PTP mode to another mode. You can only configure per-port PTP when the switch is in boundary mode.
• PTP Operation: The PTP process consists of two phases: establishing the master-slave hierarchy and synchronizing the clocks.
• The master-slave hierarchy: Within a PTP domain, each port of an ordinary or boundary clock follows this process to determine its state:
• Examines the contents of all received announce messages (issued by ports in the master state)
• Compares the data sets of the foreign master (in the announce message) and the local clock for priority, clock class, accuracy, and so on
• Based on this comparison, determines its own state as either master or slave
• Synchronizing the clocks:
• The master sends a synchronization message to the slave and notes the time it was sent.
• The slave receives the synchronization message and notes the time it was received.
• The slave sends a delay-request message to the master and notes the time it was sent.
• The master receives the delay-request message and notes the time it was received.
• The master sends a delay-response message to the slave.
• The slave uses these timestamps to adjust its clock to the time of its master.

How L2NAT Works

• Layer 2 Network Address Translation is a service that allows the assignment of a unique public IP address to an existing private IP address (end device), so that the end device can communicate on both the private and public subnets.
• Translation Tables: L2NAT has two translation tables where private-to-public and public-to-private subnet translations can be defined
• This implementation also supports multiple VLANs through the NAT boundary for enhanced network segmentation.
• IE 2000—Layer 2 NAT is included in the Enhanced LAN Base feature set, available for Cisco IOS 15.0(2)EB or later. Use the correct license enhancedlanbase.

How DHCP Server Port-Based Address Allocation Works

The DHCP protocol recognizes DHCP clients by the client identifier (ID) option in the DHCP packet. Clients who do not include the client ID option are identified by the client hardware address. The DHCP Server Port-Based Address Allocation feature introduces the capability to ensure that the same IP address is always offered to the replacement device as the device being replaced. This IP address is always offered to the same connected port even as the client ID or client hardware address (chaddr) changes in the DHCP messages received on that port.

If this feature is configured, the port name of the interface overrides the information the client sends and the actual point of connection. Then a port on the switch becomes the client ID.