Dislikes: 0
i UNDERSTAND. I have been thru it. You can watch some You Tube Videos on Scan to SMB and Email by typing in keywords like, Bizhub C308 scan to email set up. Prestige office solutions has several awesome you tube videos that will help you. They are there for newbies. Good Luck! -Mike G.Originally Posted by BillyCarpenter
I really didn't; know what I was getting myself into when I signed up for this routing and switching course. I don't think anyone knows what they're getting themselves into when they sign up for the course. Not really.
There have been times where I've asked myself if I was smart enough to learn this stuff. It can be really complicated and there's a mountain of information to learn. It can be overwhelming.
Here's the good news.....
As long as you don't give up, things will start to settle down. Light bulbs will begin to come on and it'll start to make sense. Above all else, trust the process. Learn the course in the order that it's given to you. Don't jump around. That's a big no-no.
I'd like to share something before I end this post:
In networking, everything is about "rules". In networking "rules" are referred to as "protocols." When you read "protocols", it's just another word for "rules." You can't play the game until you know the rules. The "game" in this case is "routers" and routers have rules. Once you know the rules, you can make the router do what you want them to do. And it's pretty amazing what you can get them to do.
Let me give an example of one of the rules in routing.....
Lets say that I enter the following 2 routes in the routing table:
ip route 10.1.0.0 255.255.252.0
ip route 10.1.0.0 255.255.255.0
The first route that I entered (10.1.0.0 255.255.252.0) is a summary route.
The 2nd ip address that I entered is a direct static route (10.1.0.0 255.255.255.0)
It's not important whether or not you understand the difference between the 2 routes. What is important is to understand the rules:
The rule is this: The longest prefix wins.
10.1.0.0 255.255.255.0 has the longest prefix thus that's the route that will be chosen.
Longest prefix match (also called Maximum prefix length match) refers to an algorithm used by routers in Internet Protocol (IP) networking to select an entry from a forwarding table.[1]
Because each entry in a forwarding table may specify a sub-network, one destination address may match more than one forwarding table entry. The most specific of the matching table entries — the one with the longest subnet mask — is called the longest prefix match. It is called this because it is also the entry where the largest number of leading address bits of the destination address match those in the table entry. [2]
For example, consider this IPv4 forwarding table (CIDR notation is used):
192.168.20.16/28
192.168.0.0/16
When the address 192.168.20.19 needs to be looked up, both entries in the forwarding table "match". That is, both entries contain the looked up address. In this case, the longest prefix of the candidate routes is 192.168.20.16/28, since its subnet mask (/28) is longer than the other entry's mask (/16), making the route more specific.
Forwarding tables often contain a default route, which has the shortest possible prefix match, to fall back on in case matches with all other entries fail.
It's becoming harder to share my progress and that's because the concepts that I've learned are more advanced and thus wouldn't make any sense to anyone who's never studied routers to this degree.
When I first started this thread many months back, I knew NOTHING about routers or switches, or even computers. It was all a mystery to me. Knowing what I know now, I honestly wonder how many people truly understand routing on a production level. I wonder who could actually explain how routers forward packets across the different networks?
Currently I'm working on Dynamic Routing Protocols. This is a breath of fresh air. I'll give an update on those in the next couple of days.
Someone may find this interesting. Or not. Either way I'm gonna share.
Imagine a network at a college campus. Now imagine that there's 20-30 routers that separate all the individual networks. And there's a couple of edge routers that connect to the internet.
In order for connectivity to be possible across the different networks, "routes" must be entered in the "routing table." There's 2 ways to accomplish this:
1. Static Routes. (Manually entering.)
2. Dynamic Routes (A routing protocol is used. Routing tables are built without help from an administrator.)
I learned all about building static routes for a network with hands on experience. This is time consuming and the level of difficulty is high. It's also not scalable. The experience taught me a lot. The knowledge gained is invaluable to networking.
But now I'm on Dynamic Routing Protocols. There are about 4 protocols that are used. Each one is different than the next but all accomplish the same goal.
One protocol only takes into consideration how many "hops" need to be taken to reach the destination. The route with the least amount of hops will win and thus be entered into the routing table. Sounds great, right? Well, there's a problem with that. This protocol doesn't take "bandwidth" into consideration. So, while it may have the least amount of "hops", the lack of bandwidth may make it a slower alternative to a route with more hops but has a higher bandwidth.
Did anyone follow that?
Who wants to learn about the "gateway of last resort"?
Let's say that we have a topology that consists of the following 4 networks:
1. 192.168.1.0/24
2. 192.168.2.0/24
3. 10.0.0.0/24
4. 10.0.1.0/24
Lets say that all the networks are divided by a router. In order for us to have connectivity between the 4 networks, we must configure 4 routes on all the routers. That's great, now we can communicate across all 4 networks.
But how do we get out to the internet? How to we get to google.com that has an IP address of 8.8.8.8 ?
We must configure the following IP route on ALL of the routers: 0.0.0.0 0.0.0.0 ---- This is our gateway of last resort. Basically all the 0's tell the routers to forward any unknown IP addresses to the edge router...which is connected to the ISP router.
Now you know.
When you get into production networks, there will be multiple paths to reach the same destination (i.e., your computer). In other words, fault tolerance is built in. That's where Routing Protocols play a big role.
There are competing routing protocols:
a). OSPF
b.) EIGRP
c.) IS-IS
d). RIP
All of these routing protocols have one thing in common: they all advertise their routing tables to the other routers in the network. From there each router decides for itself what's the best route to take to get to a destination. Moreover, if a link happens to go down, the router will delete that route from it's routing table and build a new link if one exists. In other words...it's self-healing.
That concludes today's update on Dynamic Routing Protocols.
Yesterday I put in about a 10-hour intense study session on RIP (Routing Information Protocol). I can do the long study sessions but it really takes its toll mentally. I'm not as young as I used to be.
Anyway, while RIP isn't really used anymore (except in small networks), the fundamentals behind RIP are important to learn. Once I learned the fundamentals, I had to go to the virtual lab and verify what I learned. It's intense learning. I can promise you that. CCNA goes very deep on these topics. I can see why 90% fail the CCNA test on the first attempt. It's really not about memorization, it's about understanding how it all works and troubleshooting.
Basically RIP only takes the number of hops into account when building it's routing table. That's a major flaw and the chief reason it's not used. Other routing protocols such as OSPF are more commonly used. OSPF takes "bandwidth" into consideration when deciding the best path to take. It's much more efficient.
Last but not least:
Routers use RIP and OSPF to build a routing "database". This is not to be confused with a routing "table". The "database" is a complete list of all the routes in a network. The routing "table" is a list of the BEST network paths and these are the ones that will be used. If a link goes down, that route will be deleted from the routing table and replaced by a slower route from the routing database.
Hope that made sense.
You lost me several pages ago. It's still interesting reading though, thanks. =^..^=
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
Shame on me. +1 BC said.
A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
Blessed are they who can laugh at themselves, for they shall never cease to be amused.
I don't reply to private messages from end users.
It would be a huge time commitment, but I think you're the type of person that would be great at networking. Just judging by your work ethic/habits, this would be right up your alley.
Thanks: 
Likes: 
Reply With Quote
Bookmarks