You completed a web site for your business about three months ago, but you are still not seeing very many people visiting your web site. You do a little research and find that your web site is buried about ten pages deep on all of the major search engines. It seems that you have created a very nice web site, but it is not optimized for search engines, so your page rank is very low. Search engine optimization has become a very large field for many different consultants all over the internet. However the techniques needed to optimize your web site for search engines are not very hard to implement on your web site all by yourself. Here are a few of the most important things that you can do for search engine optimization:
Use keywords throughout your web site. – Many people do a good job putting a good description and group of keywords in their meta tags, but they do not use these same keywords throughout the rest of their web site. You must continue to use your keywords throughout the content on the rest of your web site if you would like to get high search engine rankings.
Create a sitemap – Many search engines will try to index your site’s pages by following links to all of the different pages. However if a search engine is unable to follow a link, then a page might not get included in the search engine’s results. To make sure all of your pages get indexed, make sure that you have a text-based sitemap that includes all of the major pages of your web site.
Use Flash sparingly – Flash is a very neat technology and it has its place on the web. However you do not want to overuse Flash, because a search engine will not be able to read the text that is embedded in the Flash elements, which could hurt your ranking if you have keywords in that area.
Get inbound links – One of the best things that you can do for search engine optimization is to get inbound links to your web site. If you are able to get high quality web sites that relate to your business to link to your web site, then your search engine ranking is sure to climb.
Showing posts with label link. Show all posts
Showing posts with label link. Show all posts
Tuesday, December 30, 2008
Thursday, December 25, 2008
Cisco CCNP / BSCI Tutorial: Comparing OSPF and ISIS Hellos
While studying to pass the BSCI exam and preparing to earn your CCNP certification, you'll quickly notice that while OSPF and ISIS are both link-state protocols, there are a lot of differences between the two. One major difference is the way the two protocols handle hello packets.
Hello packets are imperative to keeping OSPF and ISIS adjacencies alive. Since they are both link-state protocols, neither of them will send updates at any specified time. Hello packets are the only method by which routers running OSPF and ISIS can see that a neighboring router is still available.
OSPF gives us some great options when it comes to keeping routing table size down via the use of stub and total stub areas, but to OSPF, a hello packet is a hello packet. ISIS routers are capable of sending two different types of hellos - Level 1 and Level 2.
ISIS routers are classified as Level 1 (L1), Level 2 (L2), and Level 1-2 (L1-L2). By default, Cisco routers are L1-L2 routers; this means that every ISIS-enabled interface will send out both L1 and L2 hellos.
If one of the interfaces is forming only an L1 or L2 adjacency, there's no reason to send out hellos for the other adjacency type. For example, if R1 is forming an L1 adjacency with R2 via its ethernet0 interface, there is no reason to allow the router to transmit L2 hellos. To hardcode a router interface to send only L1 or L2 hellos, use the isis circuit-type command.
R1(config)#interface ethernet0
R1(config-if)#isis circuit-type level-1
Note: To configure this interface to send only L2 hellos, the full command is "isis circuit-type level-2-only", not just "level-2".
This configuration would prevent L2 hellos from being transmitted out ethernet0. While this does save router resources and prevents unnecessary bandwidth usage, there is also no way an L2 adjacency can be formed - so double-check your network topology before using this command!
Hello packets are imperative to keeping OSPF and ISIS adjacencies alive. Since they are both link-state protocols, neither of them will send updates at any specified time. Hello packets are the only method by which routers running OSPF and ISIS can see that a neighboring router is still available.
OSPF gives us some great options when it comes to keeping routing table size down via the use of stub and total stub areas, but to OSPF, a hello packet is a hello packet. ISIS routers are capable of sending two different types of hellos - Level 1 and Level 2.
ISIS routers are classified as Level 1 (L1), Level 2 (L2), and Level 1-2 (L1-L2). By default, Cisco routers are L1-L2 routers; this means that every ISIS-enabled interface will send out both L1 and L2 hellos.
If one of the interfaces is forming only an L1 or L2 adjacency, there's no reason to send out hellos for the other adjacency type. For example, if R1 is forming an L1 adjacency with R2 via its ethernet0 interface, there is no reason to allow the router to transmit L2 hellos. To hardcode a router interface to send only L1 or L2 hellos, use the isis circuit-type command.
R1(config)#interface ethernet0
R1(config-if)#isis circuit-type level-1
Note: To configure this interface to send only L2 hellos, the full command is "isis circuit-type level-2-only", not just "level-2".
This configuration would prevent L2 hellos from being transmitted out ethernet0. While this does save router resources and prevents unnecessary bandwidth usage, there is also no way an L2 adjacency can be formed - so double-check your network topology before using this command!
Cisco CCNP / BSCI Exam Tutorial: A Guide To Ipv6 Addressing
Learning IPv6 is paramount in your efforts to pass the BSCI exam and go on to earn your CCNP, and it's going to help in your real-world networking career as well. IPv6 can be confusing at first, but it's like anything else in Cisco or networking as a whole - learn one part at a time, master the fundamentals, and you're on your way to success. In today's article we're going to take a look at IPv6 address types.
In IPv4, a unicast address is simply an address used to represent a single host, where multicast addresses represent a group of hosts and broadcasts represent all hosts.
In IPv6, it's not quite that simple. There are actually different types of unicast addresses, each with its own separate function. This allows IPv6 to get data where it's supposed to go quicker than IPv4 while conserving router resources.
IPv6 offers two kinds of local addresses, link-local and site-local. Site-local addresses allow devices in the same organization, or site, to exchange data. Site-local addresses are IPv6's equivalent to IPv4's private address classes, since hosts using them are able to communicate with each other throughout the organization, but these addresses cannot be used to reach Internet hosts.
Site-local and link-local addresses are actually derived from a host's MAC address. Therefore, if HostA has HostB's IPv6 address, HostA can determine HostB's MAC address from that, making ARP unnecessary.
Link-local addresses have a smaller scope than site-local. Link-local addresses are just that, local to a physical link. These particular addresses are not used at all in forwarding data. One use for these addresses is Neighbor Discovery, which is IPv6's answer to ARP.
You can identify these and other IPv6 addresses by their initial bits:
001 - Global address
(first 96 bits set to zero) - IPv4-compatible address
1111 1111 – Multicast
1111 1110 11 - Site local
1111 1110 10 - Link Local
As a future CCNP, you're more than familiar with the reserved IPv4 address classes. You also know that they're not exactly contiguous. The developers of IPv6 took a structured approach to IPv6 reserved addresses - any address that begins with "0000 0000" is an IPv6 reserved address. One of these is the IPv6 loopback address, and this will give you some practice with your zero compression!
IP v6 Loopback: 0000:0000:0000:0000:0000:0000:0000:0001
Using Leading Zero Compression Only: 0:0:0:0:0:0:0:1
Combining Leading Zero and Zero Compression: ::1
Zero compression looks pretty good now, doesn't it? You just have to get used to it and keep the rules in mind. You can use all the leading zero compression you want, but zero compression ("double-colon") can only be used once in a single address.
IPv6 is here to stay, not only on your BSCI and CCNP exams, but in the real world as well. Learning it now will not only aid you in passing your Cisco exams, but in supporting IPv6 in the future.
In IPv4, a unicast address is simply an address used to represent a single host, where multicast addresses represent a group of hosts and broadcasts represent all hosts.
In IPv6, it's not quite that simple. There are actually different types of unicast addresses, each with its own separate function. This allows IPv6 to get data where it's supposed to go quicker than IPv4 while conserving router resources.
IPv6 offers two kinds of local addresses, link-local and site-local. Site-local addresses allow devices in the same organization, or site, to exchange data. Site-local addresses are IPv6's equivalent to IPv4's private address classes, since hosts using them are able to communicate with each other throughout the organization, but these addresses cannot be used to reach Internet hosts.
Site-local and link-local addresses are actually derived from a host's MAC address. Therefore, if HostA has HostB's IPv6 address, HostA can determine HostB's MAC address from that, making ARP unnecessary.
Link-local addresses have a smaller scope than site-local. Link-local addresses are just that, local to a physical link. These particular addresses are not used at all in forwarding data. One use for these addresses is Neighbor Discovery, which is IPv6's answer to ARP.
You can identify these and other IPv6 addresses by their initial bits:
001 - Global address
(first 96 bits set to zero) - IPv4-compatible address
1111 1111 – Multicast
1111 1110 11 - Site local
1111 1110 10 - Link Local
As a future CCNP, you're more than familiar with the reserved IPv4 address classes. You also know that they're not exactly contiguous. The developers of IPv6 took a structured approach to IPv6 reserved addresses - any address that begins with "0000 0000" is an IPv6 reserved address. One of these is the IPv6 loopback address, and this will give you some practice with your zero compression!
IP v6 Loopback: 0000:0000:0000:0000:0000:0000:0000:0001
Using Leading Zero Compression Only: 0:0:0:0:0:0:0:1
Combining Leading Zero and Zero Compression: ::1
Zero compression looks pretty good now, doesn't it? You just have to get used to it and keep the rules in mind. You can use all the leading zero compression you want, but zero compression ("double-colon") can only be used once in a single address.
IPv6 is here to stay, not only on your BSCI and CCNP exams, but in the real world as well. Learning it now will not only aid you in passing your Cisco exams, but in supporting IPv6 in the future.
Cisco CCNP / BSCI Certification Exam: Five OSPF Details You Must Know
Preparing for your BSCI exam on your way to the Cisco CCNP certification, you can quickly get overwhelmed by the details! Here are five commonly overlooked points you should keep in mind when it comes to your OSPF studies.
The virtual link command includes the area number of the transit area, and if authentication is being used on Area 0, the virtual link command must include the authentication statement. Since the virtual link is a logical extension of Area 0, it stands to reason that it has to be configured with the authentication type and password configured on Area 0.
OSPF requires no seed metric when routes are being redistributed into an OSPF domain. The default cost for such routes is 20, but you do need to use the "subnets" option if you want to redistribute subnets into OSPF.
There are two kinds of external OSPF routes. The default, E2, reflects the cost of the path from the ASBR to the external destination. The other option, E1, has a cost reflecting the entire path from the local router to the external destination.
When configuring stub areas, each router in the area must agree that the area is stub. For a total stub area, only the ABR needs to be configured with the "no-summary" option, but all routers in the area still must agree that the area is stub.
Routers in a stub area will have a default route to use to reach external destinations; routers in total stub areas will have a default route to use in order to reach both external and inter-area networks.
The BSCI exam and CCNP certification require a great deal of dedication and hard work. Keep studying and paying attention to the details, and you will get there!
The virtual link command includes the area number of the transit area, and if authentication is being used on Area 0, the virtual link command must include the authentication statement. Since the virtual link is a logical extension of Area 0, it stands to reason that it has to be configured with the authentication type and password configured on Area 0.
OSPF requires no seed metric when routes are being redistributed into an OSPF domain. The default cost for such routes is 20, but you do need to use the "subnets" option if you want to redistribute subnets into OSPF.
There are two kinds of external OSPF routes. The default, E2, reflects the cost of the path from the ASBR to the external destination. The other option, E1, has a cost reflecting the entire path from the local router to the external destination.
When configuring stub areas, each router in the area must agree that the area is stub. For a total stub area, only the ABR needs to be configured with the "no-summary" option, but all routers in the area still must agree that the area is stub.
Routers in a stub area will have a default route to use to reach external destinations; routers in total stub areas will have a default route to use in order to reach both external and inter-area networks.
The BSCI exam and CCNP certification require a great deal of dedication and hard work. Keep studying and paying attention to the details, and you will get there!
Wednesday, December 24, 2008
Cisco CCNA Certification: Error Detection vs. Error Recovery
Passing the CCNA, Intro, and ICND exam is all about knowing and noticing the details. (Which makes perfect sense, since becoming a master networking administrator or engineer is also about noticing the details!) One such detail knows the difference between error detection and error recovery. While the terms are sometimes used interchangeably, they are not the same thing.
Error detection is just that - error detection only. Two common error detection methods are found at the Data Link layer of the OSI model, the FCS (Frame Check Sequence) and CRC (Cyclical Redundancy Check). A mathematical equation is run against the data in the frame, and the result is sent along with the data. The receiver runs the equation again, but this time. If the result is the same, the frame is considered valid; if the result is different, the frame is considered corrupt and is discarded.
Note that the FCS and CRC do nothing in regards to retransmission. They are strictly error detection schemes.
For an example of error recovery, we look to the Transport layer, where TCP runs. TCP performs reliable delivery, and the reason we call it "reliable" is that TCP uses sequence numbers to detect missing segments. If the sender determines from the sequence numbers that the remote host did not receive transmitted segments, the sender will retransmit the missing segments.
The key to keeping the terms straight in your head is to remember that while both error detection and error recovery both detect problems, only error recovery does anything about it. It's also worth reading an exam question twice when you see either term!
Error detection is just that - error detection only. Two common error detection methods are found at the Data Link layer of the OSI model, the FCS (Frame Check Sequence) and CRC (Cyclical Redundancy Check). A mathematical equation is run against the data in the frame, and the result is sent along with the data. The receiver runs the equation again, but this time. If the result is the same, the frame is considered valid; if the result is different, the frame is considered corrupt and is discarded.
Note that the FCS and CRC do nothing in regards to retransmission. They are strictly error detection schemes.
For an example of error recovery, we look to the Transport layer, where TCP runs. TCP performs reliable delivery, and the reason we call it "reliable" is that TCP uses sequence numbers to detect missing segments. If the sender determines from the sequence numbers that the remote host did not receive transmitted segments, the sender will retransmit the missing segments.
The key to keeping the terms straight in your head is to remember that while both error detection and error recovery both detect problems, only error recovery does anything about it. It's also worth reading an exam question twice when you see either term!
Subscribe to:
Posts (Atom)
