This is Powerpoint Presentation on IP addressing & Subnet masking. This presentation describes how IP address works, what its classes and how the subnet masking works and more.
This is Powerpoint Presentation on IP addressing & Subnet masking. This presentation describes how IP address works, what its classes and how the subnet masking works and more.
he Associate level of Cisco Certifications can begin directly with CCNA for network installation, operations and troubleshooting or CCDA for network design. Think of the Associate Level as the foundation level of networking certification.
This presentation by Westermo’s Technical Lead Engineers Dakota Diehl and Benjamin Campbell, is an integral part of the Westermo webinar on January 30th 2020, covering the basics of industrial networking. https://www.westermo.com/news-and-events/webinars/learn-the-basics-of-industrial-ethernet-communications
The webinar, including this presentation, aimed to teach the basics of industrial ethernet communications and computer networking. Starting from the ground up, it covered the basics of how network connections work, and how one computer talks to another.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
2. Topology 2
• A branch of mathematics concerned with those
properties of geometric configurations that are
unaltered by elastic deformations such as
stretching or twisting
• A term used in the computer networking field to
describe the structure of a network
4. Why Use a Hierarchical Model?
Reduces workload on network devices
Avoids devices having to communicate with too many other
devices (reduces “CPU adjacencies”)
Constrains broadcast domains
Enhances simplicity and understanding
Facilitates changes
Facilitates scaling to a larger size
4
5. Hierarchical Network Design 5
Enterprise WAN
Backbone
Campus A Campus B
Campus C
Building C-1 Building C-2
Campus C Backbone
Core Layer
Distribution
Layer
Access Layer
6. Cisco’s Hierarchical Design
Model
A core layer of high-end routers and switches that are optimized for
availability and speed
A distribution layer of routers and switches that implement policies
and segment traffic
An access layer that connects users via hubs, switches, and other
devices
6
7. Flat Versus Hierarchy 7
Flat Loop Topology
Headquarters in
Medford
Grants Pass
Branch Office
Ashland
Branch
Office
Klamath Falls
Branch Office
Headquarters in
Medford
Ashland
Branch
Office
Klamath Falls
Branch Office
Grants Pass
Branch
Office
White City
Branch Office
Hierarchical Redundant Topology
11. Avoid Chains and Backdoors 11
Core Layer
Distribution Layer
Access Layer
Chain
Backdoor
12. How Do You Know When You Have
a Good Design?
When you already know how to add a new
building, floor, WAN link, remote site, e-
commerce service, and so on
When new additions cause only local
change, to the directly-connected devices
When your network can double or triple in
size without major design changes
When troubleshooting is easy because there
are no complex protocol interactions to
wrap your brain around
12
14. Campus Topology Design
Use a hierarchical, modular approach
Minimize the size of bandwidth domains
Minimize the size of broadcast domains
Provide redundancy
Mirrored servers
Multiple ways for workstations to reach a router for off-net
communications
14
15. A Simple Campus Redundant
Design
15
Host A
Host B
LAN X
LAN Y
Switch 1 Switch 2
16. Bridges and Switches use Spanning-
Tree Protocol (STP) to Avoid Loops
16
X
Host A
Host B
LAN X
LAN Y
Switch 1 Switch 2
17. Bridges (Switches) Running STP
Participate with other bridges in the election of a single
bridge as the Root Bridge.
Calculate the distance of the shortest path to the Root
Bridge and choose a port (known as the Root Port) that
provides the shortest path to the Root Bridge.
For each LAN segment, elect a Designated Bridge and a
Designated Port on that bridge. The Designated Port is a
port on the LAN segment that is closest to the Root Bridge.
(All ports on the Root Bridge are Designated Ports.)
Select bridge ports to be included in the spanning tree.
The ports selected are the Root Ports and Designated
Ports. These ports forward traffic. Other ports block traffic.
17
18. Elect a Root 18
Bridge B Bridge C
Bridge A ID =
80.00.00.00.0C.AA.AA.AA
Bridge B ID =
80.00.00.00.0C.BB.BB.BB
Bridge C ID =
80.00.00.00.0C.CC.CC.CC
Port 1
Port 2
Port 1
Port 2
Port 1 Port 2
LAN Segment 2
100-Mbps Ethernet
Cost = 19
LAN Segment 1
100-Mbps Ethernet
Cost = 19
LAN Segment 3
100-Mbps Ethernet
Cost = 19
Root
Bridge A
Lowest Bridge ID
Wins!
19. Determine Root Ports 19
Bridge B Bridge C
Root
Bridge A
Bridge A ID =
80.00.00.00.0C.AA.AA.AA
Bridge B ID =
80.00.00.00.0C.BB.BB.BB
Bridge C ID =
80.00.00.00.0C.CC.CC.CC
Port 1
Port 2
Port 1
Port 2
Port 1 Port 2
LAN Segment 2
100-Mbps Ethernet
Cost = 19
LAN Segment 1
100-Mbps Ethernet
Cost = 19
LAN Segment 3
100-Mbps Ethernet
Cost = 19
Root Port Root Port
Lowest Cost
Wins!
20. Determine Designated Ports
20
Bridge B Bridge C
Root
Bridge A
Bridge A ID =
80.00.00.00.0C.AA.AA.AA
Bridge B ID =
80.00.00.00.0C.BB.BB.BB
Bridge C ID =
80.00.00.00.0C.CC.CC.CC
Port 1
Port 2
Port 1
Port 2
Port 1 Port 2
LAN Segment 2
100-Mbps Ethernet
Cost = 19
LAN Segment 1
100-Mbps Ethernet
Cost = 19
LAN Segment 3
100-Mbps Ethernet
Cost = 19
Root Port Root Port
Designated Port Designated Port
Designated Port
Lowest Bridge ID
Wins!
21. Bridge B Bridge C
Root
Bridge A
Bridge A ID =
80.00.00.00.0C.AA.AA.AA
Bridge B ID =
80.00.00.00.0C.BB.BB.BB
Bridge C ID =
80.00.00.00.0C.CC.CC.CC
Port 1
Port 2
Port 1
Port 2
Port 1 Port 2
LAN Segment 2
100-Mbps Ethernet
Cost = 19
LAN Segment 1
100-Mbps Ethernet
Cost = 19
LAN Segment 3
100-Mbps Ethernet
Cost = 19
Root Port Root Port
Designated Port Designated Port
Designated Port Blocked Port
X
Prune Topology into a Tree!
21
22. React to Changes
22
Bridge B Bridge C
Root
Bridge A
Bridge A ID =
80.00.00.00.0C.AA.AA.AA
Bridge B ID =
80.00.00.00.0C.BB.BB.BB
Bridge C ID =
80.00.00.00.0C.CC.CC.CC
Port 1
Port 2
Port 1
Port 2
Port 1 Port 2
LAN Segment 2LAN Segment 1
LAN Segment 3
Root Port Root Port
Designated Port Designated Port
Designated Port Becomes
Disabled
Blocked Port Transitions to
Forwarding State
23. Scaling the Spanning Tree Protocol
Keep the switched network small
It shouldn’t span more than seven switches
Use BPDU skew detection on Cisco switches
Use IEEE 802.1w
Provides rapid reconfiguration of the spanning tree
Also known as RSTP
23
24. Virtual LANs (VLANs)
An emulation of a standard LAN that allows data transfer
to take place without the traditional physical restraints
placed on a network
A set of devices that belong to an administrative group
Designers use VLANs to constrain broadcast traffic
24
25. VLANs versus Real LANs 25
Switch A
Station A1 Station A2 Station A3
Network A
Switch B
Station B1 Station B2 Station B3
Network B
26. A Switch with VLANs 26
Station A1 Station A2 Station A3
VLAN A
Station B1 Station B2 Station B3
VLAN B
27. VLANs Span Switches 27
Switch A
Station B1 Station B2 Station B3
Switch B
Station B4 Station B5 Station B6
Station A1 Station A2 Station A3 Station A4 Station A5 Station A6
VLAN B
VLAN A
VLAN B
VLAN A
28. WLANs and VLANs
A wireless LAN (WLAN) is often implemented as a VLAN
Facilitates roaming
Users remain in the same VLAN and IP subnet as they
roam, so there’s no need to change addressing
information
Also makes it easier to set up filters (access control lists) to
protect the wired network from wireless users
28
29. Workstation-to-Router
Communication
Proxy ARP (not a good idea)
Listen for route advertisements (not a great idea either)
ICMP router solicitations (not widely used)
Default gateway provided by DHCP (better idea but no
redundancy)
Use Hot Standby Router Protocol (HSRP) for redundancy
29
31. Multihoming the Internet Connection 31
Enterprise
Enterprise
Enterprise
ISP 1
ISP 1 ISP 2
ISP 1
ISP 1 ISP 2
Enterprise
Option A
Option B
Option C
Option D
Paris NY
Paris NY
34. Summary
Use a systematic, top-down approach
Plan the logical design before the physical design
Topology design should feature hierarchy, redundancy,
modularity, and security
34
35. Review Questions
Why are hierarchy and modularity
important for network designs?
What are the three layers of Cisco’s
hierarchical network design?
What are the major components of Cisco’s
enterprise composite network model?
What are the advantages and
disadvantages of the various options for
multihoming an Internet connection?
35
Editor's Notes
Did you know that according to topologists, a coffee cup and donut are the same shape? If they were made of clay, for example, consider how easy it would be to mold the one to look like the other, while retaining the most significant characteristics (such as the roundedness and the hole).
Just like with coffee and donuts made of clay, in the networking field, during the logical design phase, we are more concerned with the overall architecture, shape, size, and interconnectedness of a network, than with the physical details.
For more information regarding topology, coffee, and donuts, see:
http://en.wikipedia.org/wiki/Topology
Said by Dr. Peter Welcher, consultant and author of many networking articles in magazines, etc.
If all ports have equal distance to the Root Bridge, then the Designated Port is chosen by lowest sender Bridge ID. If the IDs are the same, then the port is chosen by lowest Port ID.
In general, STP checks for the best information by using these four criteria in the following order:
Lowest Root Bridge ID
Lowest path cost to the Root Bridge
Lowest sender Bridge ID
Lowest Port ID
See Top-Down Network Design for more details.
To understand VLANs, it helps to think about real (non-virtual) LANs first. Imagine two switches that are not connected to each other in any way. Switch A connects stations in Network A and Switch B connects stations in Network B,
When Station A1 sends a broadcast, Station A2 and Station A3 receive the broadcast, but none of the stations in Network B receive the broadcast, because the two switches are not connected. This same configuration can be implemented through configuration options in a single switch, with the result looking like the next slide.
Through the configuration of the switch there are now two virtual LANs implemented in a single switch, instead of two separate physical LANs. This is the beauty of VLANs. The broadcast, multicast, and unknown-destination traffic originating with any member of VLAN A is forwarded to all other members of VLAN A, and not to a member of VLAN B. VLAN A has the same properties as a physically separate LAN bounded by routers. The protocol behavior in this slide is exactly the same as the protocol behavior in the previous slide.
VLANs can span multiple switches. In this slide, both switches contain stations that are members of VLAN A and VLAN B. This design introduces a new problem, the solution to which is specified in the IEEE 802.1Q standard and the Cisco proprietary Inter-Switch Link (ISL) protocol. The problem has to do with the forwarding of broadcast, multicast, or unknown-destination frames from a member of a VLAN on one switch to the members of the same VLAN on the other switch.
In this slide, all frames going from Switch A to Switch B take the same interconnection path. The 802.1Q standard and Cisco's ISL protocol define a method for Switch B to recognize whether an incoming frame belongs to VLAN A or to VLAN B. As a frame leaves Switch A, a special header is added to the frame, called the VLAN tag. The VLAN tag contains a VLAN identifier (ID) that specifies to which VLAN the frame belongs.
Because both switches have been configured to recognize VLAN A and VLAN B, they can exchange frames across the interconnection link, and the recipient switch can determine the VLAN into which those frames should be sent by examining the VLAN tag. The link between the two switches is sometimes called a trunk link or simply a trunk.
Trunk links allow the network designer to stitch together VLANs that span multiple switches. A major design consideration is determining the scope of each VLAN and how many switches it should span. Most designers try to keep the scope small. Each VLAN is a broadcast domain. In general, a single broadcast domain should be limited to a few hundred workstations (or other devices, such as IP phones).