Thaiio.com

Thaiio is the best of PC interfacing Electronic Hardware and Devices resource.

Today , 2007
March 24th, 2008

Network+ Exam Tutorial Network Interface Cards (NICs)

Part of the challenge of passing the Network+ exam is learning about all the different types of hardware a network requires. Today we’ll take a look at a vital part of network connectivity, the Network Interface Card (NIC, pronounced “nick”).

The NIC is the device, or card, that gives the host a physical connection to the network. The NIC is generally an internal device, but one that can be removed and replaced with a different NIC. NICs are considered Physical layer devices and work at Layer 1 of the OSI model.

Most issues involving NICs occur before the device is even added to the network - because the purchaser didn’t do their research. All NICs are not created equal. Some are for Ethernet networks, some for Token Ring, and speed capabilities vary as well. Don’t assume a given vendor’s NIC is going to fit your device and give you the results you want. A quick visit to the vendor’s website and a few minutes looking up NIC specifications can save you a lot of trouble later on.

One more NIC warning - take your time when you’re installing a new NIC. Make sure the device is off, and make sure you’re properly grounded by connecting the grounding strap to your wrist. Otherwise, you can send static electricity into places on the host where it’s only going to cause damage.

Your new NIC should also come with directions on how to download the drivers for that NIC. Drivers sound like something physical, but they’re not. Drivers are simply software files that are needed on the host in order for the NIC to work correctly. Vendors used to include drivers on CDs with their NICs, but the trend now is to include instructions on where to download the drivers from the vendor website.

That does lend itself to an occasional Catch-22: “If I don’t have this device on the Net yet, how can I download the drivers?” If the host has no network connectivity, you may need to download the drivers to a host that does, copy the files to CD, and then install the drivers from CD.

You’ll see two different lights on a typical NIC, one green and one amber. Depending on whether the host has network connectivity or not, the lights will be solid, flashing, or out. Sometimes flashing is good, sometimes it’s not! Here’s a guide to the colors you’ll see on a NIC:

A solid green light indicates connectivity is present. This link light is generally either green or off. Green is good, off is not! That light should stay a solid green. If you see it flashing green, that’s a sign of intermittent connectivity, which is a fancy way of saying “one minute the PC is on the network, the next minute it’s not”. Most likely, either the NIC or the cable connected to the NIC is going bad. With the green light, flashing is not desirable.

Flashing amber lights indicate collisions. You’ll see this flash occasionally even on a healthy network, but you don’t want to see it flash so often that it looks like a solid amber light!

If you have an Internet connection at home, you can see these lights in action for yourself. The green and amber lights will be right next to where the cable from your modem connects to your PC.

On occasion, you’ll have a PC that loses connectivity to the network. I advise you to always start network troubleshooting at the Physical layer of the OSI model, and that means checking both the NIC and the cable connected to it. I personally would swap the cable out first, since they seem to go bad more often than NICs, but that’s up to you. If you swap NICs and you still can’t get the PC on the network, try putting a new cable in.

Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage, home of over 100 free certification exam tutorials, including Security+,
Network +, CCNA, and CCNP topics.

You can also join his RSS feed and visit his blog, which is updated several times daily with new Cisco certification articles, free tutorials, and daily CCNA, Network+, Security+, A+, and CCNP certification exam practice questions!

For a FREE copy of his latest e-books, “How To Pass The CCNA” and “How To Pass The CCNP”, visit the website and download your free copies. You can also get FREE CCNA and CCNP exam questions every day! And now, you can earn your A + certification from The Bryant Advantage!

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

March 24th, 2008

Cisco CCNP BSCI Exam Tutorial The Passive Interface Command And OSPF

To pass the BSCI exam and become a CCNP, you have to be aware of the proper use of passive interfaces. You learned about passive interfaces in your CCNA studies, but here we’ll review the basic concept and clear up one misconception regarding passive interfaces and OSPF.

Configuring an interface as passive will still allow the interface to receive routing updates, but the interface will no longer transmit them. While the command itself would make you think this command will be applied at the interface level, that is not the case. Below, we’ll configure ethernet0 as a RIP passive interface.

R1(config)#router rip

R1(config-router)#passive-interface ethernet0

Ethernet0 will no longer send RIP routing updates, but will accept them.

The passive interface concept is clear enough with RIP, IGRP, and EIGRP - all protocols that send routing update packets. But OSPF doesn’t send routing update packets - OSPF sends link state advertisements. It’s the inability of the passive interface command to stop LSAs that lead many to think that passive interfaces cannot be used with OSPF.

Even though OSPF does not sent “routing updates” in the form that RIP, IGRP, and EIGRP do, you can still configure an OSPF-enabled interface as passive in order to prevent OSPF traffic from exiting or entering that interface. No OSPF adjacency can be formed if one of the interfaces involved is a passive interface, and if you configure an OSPF-enabled interface as passive where an adjacency already exists, the adjacency will drop almost immediately.

Let’s see that in action. R1 and R2 have an existing OSPF adjacency over their Ethernet interfaces. In an effort to reduce routing traffic, R1’s e0 interface is configured as passive. The adjacency drops right away.

R1(config)#router ospf 1

R1(config-router)#passive-interface ethernet0

18:31:11: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0 from FULL to DOWN, Neighbor Down: Interface down or detached

Knowing how to use the passive interface command is a vital part of being a CCNP, and of being a master networker. Good luck to you in both of these pursuits!

Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage, home of free CCNP and CCNA tutorials, The Ultimate CCNA Study Package, and Ultimate CCNP Study Packages.

You can also join his RSS feed and visit his blog, which is updated several times daily with new Cisco certification articles, free tutorials, and daily CCNA / CCNP exam questions! Details are on the website.

For a FREE copy of his latest e-books, “How To Pass The CCNA” and “How To Pass The CCNP”, just visit the website! You can also get FREE CCNA and CCNP exam questions every day! Pass the CCNP exam with The Bryant Advantage!

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

March 19th, 2008

Cisco CCNP BSCI Exam Tutorial RIP Update Packet Authentication

When you earned your CCNA, you thought you learned everything there is to know about RIP. Close, but not quite! There are some additional details you need to know to pass the BSCI exam and get one step closer to the CCNP exam, and one of those involves RIP update packet authentication.

You’re familiar with some advantages of using RIPv2 over RIPv1, support for VLSM chief among them. But one advantage that you’re not introduced to in your CCNA studies is the ability to configure routing update packet authentication.

You have two options, clear text and MD5. Clear text is just that - a clear text password that is visible by anyone who can pick a packet off the wire. If you’re going to go to the trouble of configuring update authentication, you should use MD5. The MD stands for “Message Digest”, and this is the algorithm that produces the hash value for the password that will be contained in the update packets.

Not only must the routers agree on the password, they must agree on the authentication method. If one router sends an MD5-hashed password to another router that is configured for clear-text authentication, the update will not be accepted. debug ip rip is a great command for troubleshooting authenticated updates.

R1, R2, and R3 are running RIP over a frame relay cloud. Here is how RIP authentication would be configured on these three routers.

R1#conf t

R1(config)#key chain RIP

< The key chain can have any name. >

R1(config-keychain)#key 1

< Key chains can have multiple keys. Number them carefully when using multiples. >

R1(config-keychain-key)#key-string CISCO

< This is the text string the key will use for authentication. >

R1(config)#int s0

R1(config-if)#ip rip authentication mode text

< The interface will use clear-text mode. >

R1(config-if)#ip rip authentication key-chain RIP

< The interface is using key chain RIP, configured earlier. >

R2#conf t

R2(config)#key chain RIP

R2(config-keychain)#key 1

R2(config-keychain-key)#key-string CISCO

R2(config)#int s0.123

R2(config-subif)#ip rip authentication mode text

R2(config-subif)#ip rip authentication key-chain RIP

R3#conf t

R3(config)#key chain RIP

R3(config-keychain)#key 1

R3(config-keychain-key)#key-string CISCO

R3(config)#int s0.31

R3(config-subif)#ip rip authentication mode text

R3(config-subif)#ip rip authentication key-chain RIP

To use MD5 authentication rather than clear-text, simply replace the word “text” in the ip rip authentication mode command with md5.

Here’s what a successfully authentication RIPv2 packet looks like, courtesy of debug ip rip. Clear-text authentication is in effect and the password is “cisco”.

3d04h: RIP: received packet with text authentication cisco

3d04h: RIP: received v2 update from 150.1.1.3 on Ethernet0

3d04h: 100.0.0.0/8 via 0.0.0.0 in 1 hops

3d04h: 150.1.2.0/24 via 0.0.0.0 in 1 hops

Here’s what it looks like when the remote device is set for MD5 authentication and the local router is set for clear-text. You’ll also see this message if the password itself is incorrect.

3d04h: RIP: ignored v2 packet from 150.1.1.3 (invalid authentication)

“Debug ip rip” may be a simple command as compared to the debugs for other protocols. but it’s also a very powerful debug. Start using debugs as early as possible in your Cisco studies to learn how router commands really work!

Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage, home of free CCNP and CCNA tutorials, The Ultimate CCNA Study Package, and Ultimate CCNP Study Packages.

For a FREE copy of his latest e-books, “How To Pass The CCNA” and “How To Pass The CCNP”, just visit the website! You can also get FREE CCNA and CCNP exam questions every day! Pass the CCNP exam with The Bryant Advantage!

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

March 15th, 2008

Cisco CCNP Certification BCMSN Exam Tutorial Writing QoS Policy

QoS - Quality of Service - is a huge topic on both the BCMSN exam and real-world networks. QoS is so big today that Cisco’s created separate specialist certifications that cover nothing but QoS! It can be an overwhelming topic at first, but master the fundamentals and you’re on your way to exam and job success.

If you work with QoS at any level - and sooner or later, you will - you’ve got to know how to write and apply QoS policies.

Creating and applying such a policy is a three-step process.

1. Create a QoS class to identify the traffic that will be affected by the policy.

2. Create a QoS policy containing the actions to be taken by traffic identified by the class.

3. Apply the policy to the appropriate interfaces.

If the phrase “identify the traffic” sounds like it’s time to write an access-list, you’re right! Writing an ACL is one of two ways to classify traffic, and is the more common of the two. Before we get to the less-common method, let’s take a look at how to use an ACL to classify traffic.

You can use either a standard or extended ACL with QoS policies. The ACL will be written separately, and then called from the class map.

SW1(config)#access-list 105 permit tcp any any eq 80

SW1(config)#class-map WEBTRAFFIC

SW1(config-cmap)#match access-group 105

Now that we’ve identified the traffic to be affected by the policy, we better get around to writing the policy! QoS policies are configured with the policy-map command, and each clause of the policy will contain an action to be taken to traffic matching that clause.

SW1(config)#policy-map LIMIT_WEBTRAFFIC_BANDWIDTH

SW1(config-pmap)#class WEBTRAFFIC

SW1(config-pmap-c)#police 5000000 exceed-action drop

SW1(config-pmap-c)#exit

This is a simple policy, but it illustrates the logic of QoS policies. The policy map LIMIT_WEBTRAFFIC_BANDWIDTH calls the map-class WEBTRAFFIC. We already know that all WWW traffic will match that map class, so any WWW traffic that exceeds the stated bandwidth limitation will be dropped.

Finally, apply the policy to the appropriate interface.

SW1(config-if)#service-policy LIMIT_WEBTRAFFIC_BANDWIDTH in

Getting your CCNP is a great way to boost your career, and learning QoS is a tremendous addition to your skill set. Like I said, learn the fundamentals, don’t get overwhelmed by looking at QoS as a whole, and you’re on your way to success!

Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage, home of free CCNP and CCNA tutorials, The Ultimate CCNA Study Package, and Ultimate CCNP Study Packages.

You can also join his RSS feed and visit his blog, which is updated several times daily with new Cisco certification articles, free tutorials, and daily CCNA / CCNP exam questions! Details are on the website.

For a FREE copy of his latest e-books, “How To Pass The CCNA” and “How To Pass The CCNP”, just visit the website! You can also get FREE CCNA and CCNP exam questions every day! Get your CCNP certification with The Bryant Advantage!

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

March 13th, 2008

Cisco CCNP BCSI Exam Tutorial Configuring EIGRP Packet Authentication

Configuring RIPv2 and EIGRP authentication with key chains can be tricky at first, and the syntax isn’t exactly easy to remember. But for BSCI and CCNP exam success, we’ve got to be able to perform this task.

In a previous tutorial, we saw how to configure RIPv2 packet authentication, with both clear-text and MD5 authentication schemes. EIGRP authentication is much the same, and has the text and MD5 authentication options as well. But EIGRP being EIGRP, the command just has to be a little more detailed!

As with RIPv2, the authentication mode must be agreed upon by the EIGRP neighbors. If one router’s interface is configured for MD5 authentication and the remote router’s interface is configured for text authentication, the adjacency will fail even if the two interfaces in question are configured to use the same password.

We’ll now configure link authentication on the adjacency over an Ethernet segment. Below, you’ll see how to configure a key chain called EIGRP on both routers, use key number 1, and use the key-string BSCI. Run show key chain on a router to see all key chains.

R2(config)#key chain EIGRP

R2(config-keychain)#key 1

R2(config-keychain-key)#key-string BSCI

R2#show key chain

Key-chain EIGRP:

key 1 — text “BSCI”

accept lifetime (always valid) - (always valid) [valid now]

send lifetime (always valid) - (always valid) [valid now]

R3(config)#key chain EIGRP

R3(config-keychain)#key 1

R3(config-keychain-key)#key-string BSCI

R3#show key chain

Key-chain EIGRP:

key 1 — text “BSCI”

accept lifetime (always valid) - (always valid) [valid now]

send lifetime (always valid) - (always valid) [valid now]

The EIGRP command to apply the key chain is a bit of a pain to remember, because the protocol and AS number is identified in the middle of the command, not the beginning. Also note that two commands are needed - one to name the key chain, another to define the authentication mode in use.

R2(config)#interface ethernet0

R2(config-if)#ip authentication key-chain eigrp 100 EIGRP

R2(config-if)#ip authentication mode eigrp 100 md5

5d07h: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.3 (Ethernet0) is down: keychain changed

R3(config)#interface ethernet0

R3(config-if)#ip authentication key-chain eigrp 100 EIGRP

R3(config-if)#ip authentication mode eigrp 100 md5

5d07h: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.23.2 (Ethernet0) is up:

As with RIPv2, the existing adjacency was torn down when one side was configured with authentication. If the key chain is correctly defined and applied on both sides, the adjacency will come back up. Always run show ip eigrp neighbor to make sure the adjacency is present. Learn the details of EIGRP key chains by configuring them on your home lab equipment, and you’ll be more than ready for BSCI exam success!

Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage, home of free CCNP and CCNA tutorials, The Ultimate CCNA Study Package, and Ultimate CCNP Study Packages.

For a FREE copy of his latest e-books, “How To Pass The CCNA” and “How To Pass The CCNP”, just visit the website! You can also get FREE CCNA and CCNP exam questions every day! Pass the CCNP exam with The Bryant Advantage!

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

March 9th, 2008

HL7 PMI - 7 Implementation Tips

HL7 is a health data communication standard. HL7 version 2 covers the exchange of patient demographics (otherwise known as Patient Master Index or PMI). HL7 V2 also covers other types of data such as admission details, scheduling, orders and results.

1. HL7 Interfaces are not plug and play

Unfortunately the HL7 V2 standard is interpreted in different ways by implementers and software developers. The outcome is two similar but not exactly matching interfaces that require analysis in order to identify the differences.

2. Translation of HL7 messages

Once the differences have been identified, the messages from one application needs to modified before they can be processed by the other application. Some translations may be relatively simple, such as moving a particular field from one place in the message to another.

For example the sending system may place an insurance number in the insurance segment (IN1). However another vendor may not support that segment and instead expects the insurance number to be placed in the patient identification segment (PID) or perhaps in a proprietary segment.

It is also common that fields may be needed to be moved based on business rules. Fortunately specialist software called interface engines are quire good at this task. For example the iCan Integrator software from Sun Microsystems (formally Seebeyond) provides this kind of functionality.

3.Code table mismatching

HL7 messages are littered with coded data. For example the martial status field contains a coded value such as ‘M’ for Married, ‘D’ for divorced and so on. However the receiving system may expect ‘1′ for married and ‘2′ for divorced. National standards have gone a long way to address this issue. Still, the odds are that one or more fields in your PMI message will need to be mapped. Fortunately interface engines are also good at this task.

4.HL7 PID Identifier List

The patient identification segment has three fields dedicated to identifiers. PID-2 Patient ID (external ID), PID-3 Patient ID (internal ID) and PID-4 Alternative Patient ID. The recommended use of these fields has changed with successive revisions of HL7 (HL7 V2.1, HL7 V2.2, HL7 V2.3, HL7 V2.3.1, HL7 V2.4). Different vendors have interpreted these fields differently. Almost everyone puts the patient’s medical record number (MRN) in PID-3.

If the scope of the interface is more than one hospital, then the MRN for one facility are distinguished from MRNs for other facilities by a facility code (passed as a subcomponent of the PID-3 field). The facility code may need mapping (see Tip 2!).

In another twist, the sending system may handle multiple hospitals (e.g. a patient administration system covering several hospitals) but the receiving system may only want to know about patients from just one facility. A typical example is a independent (but HL7 interfaced) applications such as an ICU clinical application. If the ICU system only manages patients from one hospital, it will only want HL7 messages for patients at that hospital. It may even only want HL7 messages for patients admitted to the ICU. Interface engines are good at the filtering, routing and translating of messages require to make this happen.

5.Repeating fields

Fields that repeat, such as the address field (PID-11) may also cause problems. The challenges include

  • Different systems support different numbers of repeats. For example the sending system may support 7 addresses and the receiving system may support only 2.
  • The sending system may add, update or delete the repeating field. Deleting a field can cause headaches for the downstream system. Sometimes this is overcome by the downstream system replacing the entire set of repeating fields each time.

6.Repeating segments

Segments that repeat, such as ‘Next of Kin’ (NK1) and alerts/allergies (AL1/IAM) pose similar challenges to repeating fields.

  • Different systems support different numbers of repeats. For example the sending system may support 7 patient contacts (sent as 7 NK1 segments) and the receiving system may support only 2.
  • The sending system may add, update or delete the repeating field. Deleting a field can cause headaches for the downstream system. Sometimes this is overcome by the downstream system replacing the entire set of repeating fields each time.

7.Shared fields

It is not unusual that the fields interfaced from the sending system can also be modified in the receiving system. Basically if the receiving system was not interfaced, then all of the information would need to have been duplicated by manually typing into the application. Unless the capability to edit data fields covered by the HL7 interface is ‘removed’ from the receiving system, changes made to the data (e.g. adding or changing an allergy, deleting a patient contact) by users in the receiving system, may be list with the next HL7 message received, process and stored for that patient.

Fortunately persistent and diligent interface analysis can overcome these and other challenges. HL7 PMI interfacing is one of the most common and best understood health application interfacing challenges. By applying these tips you will have made a good start along the road to a successful HL7 PMI interface implementation.

For more information on the HL7 standard and HL7 services please visit the Gillogley Services web site.

Peter Gillogley is the Director of Gillogley Services.

February 29th, 2008

Cisco CCNA Exam Tutorial Split Horizon And Hub-And-Spoke Networks

For CCNA exam success, you had better know what split horizon is, how to turn it off, and when to turn it off. Knowing when to turn split horizon off is also important in production networks, because it can cause a hub-and-spoke network to have incomplete routing tables on the spokes.

Split horizon exists for a very good reason - routing loop prevention. The rule of split horizon states that a router cannot send an advertisement for a route out the same interface that it came in on. Split horizon is on by default on all interfaces running RIP, IGRP, and EIGRP.

In this CCNA tutorial, R1 will serve, as the hub and R2 and R3 will be the spokes. We’ll first configure EIGRP over the 172.16.123.0 /24 network, the network connecting the three routers.

R1#conf t

R1(config)#router eigrp 100

R1(config-router)#no auto-summary

R1(config-router)#network 172.12.123.0 0.0.0.255

R2#conf t

R2(config)#router eigrp 100

R2(config-router)#no auto-summary

R2(config-router)#network 172.12.123.0 0.0.0.255

R3#conf t

R3(config)#router eigrp 100

R3(config-router)#no auto-summary

R3(config-router)#network 172.12.123.0 0.0.0.255

Running show ip eigrp neighbor on R1 shows that adjacencies to R2 and R3 are up.

R1#show ip eigrp neighbor

IP-EIGRP neighbors for process 100

H Address Interface Hold Uptime SRTT RTO Q Seq Type

(sec) (ms) Cnt Num

1 172.12.123.3 Se0/0 11 00:02:45 1 5000 0 1

0 172.12.123.2 Se0/0 161 00:03:01 1 5000 0 1

Each router will now advertise its loopback address via EIGRP.

R1#conf t

R1(config)#router eigrp 100

R1(config-router)#network 1.1.1.0 0.0.0.255

R2#conf t

R2(config)#router eigrp 100

R2(config-router)#network 2.2.2.0 0.0.0.255

R3#conf t

R3(config)#router eigrp 100

R3(config-router)#network 3.3.3.0 0.0.0.255

Running show ip eigrp route on each router shows that R1 has a route for both R2’s and R3’s loopback. R2 and R3 will only see R1’s loopback address, and not each other’s. Why?

R1#show ip route eigrp

2.0.0.0/24 is subnetted, 1 subnets

D 2.2.2.0 [90/2297856] via 172.12.123.2, 00:03:19, Serial0/0

3.0.0.0/24 is subnetted, 1 subnets

D 3.3.3.0 [90/2297856] via 172.12.123.3, 00:03:04, Serial0/0

R2#show ip route eigrp

1.0.0.0/24 is subnetted, 1 subnets

D 1.1.1.0 [90/2297856] via 172.12.123.1, 00:03:40, Serial0/0.123

R3#show ip route eigrp

1.0.0.0/24 is subnetted, 1 subnets

D 1.1.1.0 [90/2297856] via 172.12.123.1, 00:05:17, Serial0/0.31

EIGRP uses Split Horizon by default to prevent routing loops. In this lab, though, it prevents full network reachability. R2 and R3 both form neighbor relationships with R1’s Serial physical interface. R2 advertises its loopback address to R1’s Serial interface, as does R3. Split Horizon does not allow a route to be advertised back out the same interface it was received on. This prevents R1 from advertising R2’s loopback to R3, or R3’s loopback to R2.

Split Horizon must be disabled to allow full network reachability in this lab. To do so, run no ip split-horizon eigrp 100 on R1’s Serial interface. When Split Horizon is disabled, that will cause the neighbor
relationships to fail, and then reestablish. Run show ip route eigrp 100 on both R2 and R3. The appropriate route to the remote loopback address will now appear.

R1#conf t

R1(config)#int serial0

R1(config-if)#no ip split-horizon eigrp 100

10:02:23: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.123.2 (Serial0/0) down: split horizon changed

10:02:23: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.123.3 (Serial0/0) down: split horizon changed

10:02:27: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.123.3 (Serial0/0) ip: new adjacency

10:02:54: %DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 172.12.123.2 (Serial0/0) ip: new adjacency

R2#show ip route eigrp

1.0.0.0/24 is subnetted, 1 subnets

D 1.1.1.0 [90/2297856] via 172.12.123.1, 00:00:06, Serial0/0.123

3.0.0.0/24 is subnetted, 1 subnets

D 3.3.3.0 [90/2809856] via 172.12.123.1, 00:00:06, Serial0/0.123

R3#show ip route eigrp

1.0.0.0/24 is subnetted, 1 subnets

D 1.1.1.0 [90/2297856] via 172.12.123.1, 00:00:12, Serial0/0.31

2.0.0.0/24 is subnetted, 1 subnets

D 2.2.2.0 [90/2809856] via 172.12.123.1, 00:00:12, Serial0/0.31

Disabling split horizon should be done with care, but knowing when and where to do so shows that you truly understand how this technology works - and that’s a big step on the way to earning your CCNA!

Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage, home of free CCNA and CCNP tutorials, The Ultimate CCNA Study Package, and Ultimate CCNP Study Packages.

You can also join his RSS feed and visit his blog, which is updated several times daily with new Cisco certification articles, free tutorials, and daily CCNA / CCNP exam questions! Details are on the website.

For a FREE copy of his latest e-books, “How To Pass The CCNA” and “How To Pass The CCNP”, visit the website and download your free copies. You can also get FREE CCNA and CCNP exam questions every day! Get your CCNA study guide from The Bryant Advantage!

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

February 27th, 2008

Desktop Management Interface

Desktop Management Interface is a specialized system to manage many computers in a very large establishment. The basic component of Desktop Management Interface is the Management Information Format Database (MIFD). The database stores all information on a local computer. Experts say that Desktop Management Interface is nothing more than a set of application programming interfaces or APIs. Thanks to Desktop Management Interface, any computer system can exchange information.

Desktop Management Interface has three different components - service layer, management interface and component interface. The management interface is a text file that has information on hardware and software. The component interface is an application program interface (API). The service layer acts as a link between management interface and component interface.

Desktop Management Interface comes in handy when you are trying to identify and manage computer components, and is accepted as the ideal desktop methodology. The interface is the storehouse of all information on computers. Desktop Management Interface is the brainchild of a Distributed Management Task Force (DMTF), and has made the jobs of IT managers, technical experts and common users much easier. The innovative and sophisticated Desktop Management Interface helps people get information on processor category, installation dates, maintenance records, power sources, peripherals, etc.

Desktop Management Interface has some extremely advantageous aspects. Vendors and systems integrators can exchange information effectively, and you don’t have to install any particular hardware or operating system to have it running efficiently. You can run the management interface on a Simple Network Management Protocol (SNMP) and on non-network computers.

Desktop Management provides detailed information on Desktop Management, Desktop Management Interface, Remote Desktop Management, Desktop Management Software and more. Desktop Management is affiliated with 3D Desktop Wallpaper.

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

February 19th, 2008

Passing The Cisco CCNA Exam An Illustrated Guide To Router Modes

When you’re getting started on your CCNA studies, learning the different router modes is key to passing your Intro and ICND exams. But keeping those modes straight can be very difficult. (At least it was for me!) Let’s take a look at the various router modes you’ll need to know about to pass your CCNA, and use IOS Help to illustrate the different uses of each mode.

The first mode you’ll see on a router (if the person before you logged off as they should have) is user exec mode. This is also the default mode a user is placed into when using Telnet to connect to a router. The prompt will look like this:

R1>

You can’t write or add to a configuration in this mode, but you can run quite a few show commands. This is a good mode to have users in who need to see the configuration, but shouldn’t be allowed to change it.

To get to the next level, type enable at the user exec prompt:

R1>enable

R1#

Notice that the prompt changed. This mode has two names, the official one being privileged exec mode. It’s more commonly referred to as enable mode, since “enable” is what you type to get into this mode.

This mode gives you more options for show and other commands, but you still can’t configure anything. To configure global commands, use “configure terminal”, or “conf t”, to enter global configuration mode.

R1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

R1(config)#

The prompt has changed again, and now global configuration commands such as hostname and no ip domain-lookup can be entered.

From here, you’ve got a lot of options, but we’ll look at three you need to know for your CCNA exams. To apply configuration commands to an interface, enter interface configuration mode, as shown here:

R1(config)#interface serial0

R1(config-if)#

You must be in global config mode to get into interface config mode you cannot go from enable mode straight to interface configuration mode.

R1#interface serial0

^
% Invalid input detected at ‘^’ marker.

Interface configuration mode allows you to apply an IP address to the interface, as well as many other commands related to frame relay, ISDN, and dynamic routing protocols.

For the CCNA, you need to know about two other configuration modes. To configure console commands (such as password protection), enter line configuration mode as shown here:

R1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

R1(config)#line console 0

R1(config-line)#password cisco

R1(config-line)#login

The prompt “(config-line)” indicates that you’re in line configuration mode. Your console line is not the only line you’ll be configuring for the CCNA, though your vty lines are used for incoming telnet connections and must be configured in a similar fashion.

R1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

R1(config)#line console 0

R1(config-line)#password cisco

R1(config-line)#login

R1(config-line)#line vty 0 4

R1(config-line)#password cisco

R1(config-line)#login

Notice that you do not have to exit one interface mode to go to another one. Let’s say that you’ve configured your vty lines and now want to put an IP address on your Ethernet interface. You don’t have to go out with ctrl-z and then start again you can go straight to interface config mode from line config mode. Just make sure you see the prompt change!

R1(config-line)#line vty 0 4

R1(config-line)#password cisco

R1(config-line)#login

R1(config-line)#interface ethernet0

R1(config-if)#ip address 15.1.1.1 255.255.255.0

When you’re preparing for CCNA exam success, there’s a lot to absorb. Just take it one piece at a time, get some hands-on experience to go with your theory, and before you know it you’re moving around in the different Cisco router configuration modes without giving it a second thought. Keep studying and your CCNA exam success is assured!

Chris Bryant, CCIE #12933, is the owner of The Bryant Advantage, home of free CCNA and CCNP tutorials, The Ultimate CCNA Study Package, and Ultimate CCNP Study Packages.
For a FREE copy of his latest e-books, “How To Pass The CCNA” and “How To Pass The CCNP”, visit the website and download your free copies. You can also get FREE CCNA and CCNP exam questions every day! Pass the CCNA exam with The Bryant Advantage!

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

February 18th, 2008

On the Importance of Good User Interface Design

It seems obvious, but it’s often ignored. A good user interface design can spell the difference between acceptance of a software product and its failure in the marketplace. If the end-users find the software to be too cumbersome or difficult to understand, then an otherwise excellent product could be doomed to failure. The developer’s goal should be to make the software as professional-looking and easy to use as possible.

Sadly, I’ve found that a great many companiesespecially small or highly specialized software firmspay little attention to the mechanics of good user interface style. “As long as it works, that’s what matters!” seems to be their mantra, with little regard for the inconvenience that this imposes on the user.

Thankfully, that’s not how we operate at our company. Our team of developers invests considerable effort into making out user interfaces as intuitive and foolproof as possible, since we know that this is something our customers would appreciate. I’ve often commended my teammates for recognizing that excellence is worth pursuing.

Going back to the topic I can’t remember how many times I’ve encountered software that was designed to work, but with little regard for ease of use. If the software forces the operator to constantly consult a manual or a cheat sheet, then that’s a pretty good indication that the user interface needs improvement. Similarly, the software should allow the user to perform tasks quickly and efficiently, without sacrificing power and flexibility. This seems intuitive, and yet these considerations are so often lacking.

The sad part is that these shortcomings can often be cured using a few simple guidelines. For example, it helps if the user can enter data using buttons and list boxes, instead of typing it in by hand. It helps if the software provides pop-up dialog boxes, to guide the user along the way. Even the judicious choice of icons and other graphics can turn a steep learning curve into a short and gentle slope.

For that matter, even such trivial matters as spelling and grammar deserve attention. Poorly phrased instructions can severely hinder an operatorand even if they don’t, they do reflect poorly on the developers of that application.

There is much more that can be said about the mechanics of good user interface design, but that’s a topic on which entire book can be (and have been) written. Suffice to say that a company that strives for excellence should pay close attention to the elements of software usability and flexibility. These are critical elements of software excellence, and they are worth pursuing.

About The Author

V. Berba Velasco Jr., Ph.D. is a senior electrical and software engineer at Cellular Technology Ltd (http://www.immunospot.com, http://www.elispot-analyzers.de http://www.elispot.cn) where he serves with great pride. He has seen how proper attention to software usability, maintainability and elegance can spell the difference between mediocre products and great ones.

Tags: plc
pac
pc
port
vb
vc
c#
parallel
serial
com
usb

« Previous Entries |
cheapest online diazepam 24 hour delivery cheap levitra rx pills buy lorazepam cheap cialis buy cheapest generic valium purchase new report female zyban order oxazepam prescription cheapest generic xanax viagra order herbal klipal for woman levitra buy drugs online buy herbal tramadol cialis soft tabs levitra cialis best herbal viagra soft tabs uk cialis buy viagra on line viagra levitra women buy cialis online without prescription natural levitra substitutes cheapest generic viagra cyber pharmacy propecia viagra soft tabs studies women
Close
E-mail It