If you want someone to help you, try reading Jeremy Stretch's great advice before posting:
http://packetlife.net/blog/2011/feb/17/ ... lp-online/Here's a brief summary (with some additions):
Don't1. Don't be clingyQuote:
Can someone help me configure EIGRP?
Understand that any support for which you have not paid is ad-hoc and best effort; in other words, there is no guarantee you will be helped. And if someone does help, there is no guarantee that he or she will continue to help until the problem has been solved to your satisfaction.
2. Don't claim urgencyQuote:
HELP!!!! VERY URGENT!!!1 TWITTER KEEPS TIMING OUT AND I HAVE SOMETHING IMPORTANT I NEED TO TWEET!!!!11
Don't use all capitals either
3. Don't double-postOnce is enough - and don't ask "How Do I Do x" in the HOWTOs forum. That's where you write articles like this that tell you "How To"
4. Don't ask for things you know you shouldn't...like a copy of IOS
5. Don't post images on other sites. Upload your image directly to your post and place it inline. I'm not going to go downloading your image to view it, or visiting some hosting site.
6. Don't zip files unless you have toIf you are uploading a whole project, go ahead - zip the folder and upload it. But if it is just your topology.net configuration, or part of a router config, copy and paste it into a
Code:
code block
like this
Do1. First ask yourself how someone else would know the answerQuote:
"How can I determine whether an 1841 supports MPLS?"
is much better than:
Quote:
Does an 1841 support MPLS?
You'll find people are far more willing to loan you a fishing rod than to catch you a fish.
2.Provide sufficient detail and contextThe more you provide the better your chance of receiving a productive response will be. A picture tells a thousand words - (remember point 5 in the Don'ts)
3. Include your configurations where applicableRemember to enclose configuration snippets in code blocks for easy readability. Attach really long configs as separate text files
4. Show your workTell us what you've tried and the outcome
5. Provide closureIf the problem is solved (even by you with no extra help) be sure to return to your initial query and record the solution. This helps others, gives a sense of closure for those who helped and gives you a place where you can find the answer should you come across the same problem in the future.
If you like this summary - I urge you to read Jeremy's article in full
http://packetlife.net/blog/2011/feb/17/ ... lp-online/ which also has some interesting follow up discussion as well.
_________________
RedNectarhttp://rednectar.net@rednectarchrisGNS3 WorkBench-a VMware image of Ubuntu with GNS3 and VPCS installed and a collection of exercises/labs