In this spirit, I decided to take another look at the Q208 TPSA Service 50 data.  This time, though, I wanted to get a quick but still comprehensive impression of what companies were performing the best in terms of total financial performance.  It's easy enough to rank the Service 50 in terms of net operating income percentage.  But what if there's a devil in the details, where this Net OI percentage is masked by poor margin efficiency ... that is ... ability to drop gross margin dollars to the operating bottom line?  What if a company with a blended portfolio (product and services) is posting big margins in the product business, but thin margins in the growing services part of the portfolio?  In short, I wanted to come up with a quick way to create a blended financial performance index, if you will, that would put into the mix all of the key measures that we track in the Service 50.  To this end I assigned ranking scores to the 50 companies for 4 margin performance measures that we already track.  In addition, I created a new measure:  margin efficiency, which is essentially the proportion of gross margin dollars that a company is able to drop to the operating bottom line.  The measures in this quick and dirty index, then are the following:

I then simply assigned a ranking (1 = best, 50 = worst) for each company along each measure, averaged the metrics for each company and sorted the list from lowest average (best overall performance) to highest average (worst overall performance).  The clear expectation and hypothesis here is that the companies that rise to the top in an index that combines all of these financial performance measures should be relatively well positioned to ride the wave that we're currently experiencing.  So ... drumroll please ... the 10 best performers are:

Consistent with many previous analyses, Software companies continue to show by far the strongest financial performance, with Intuit and Oracle rising to the very top as they often do.  In all, 8 of the top 10 average scores for overall financial performance are delivered by Software companies.  Only one company is a services company (Infosys) and only one company is a Hardware company (Cisco), which also happens to be the 10th ranked company in a list of 10 companies.  And not unexpectedly, the Software companies in the Service 50 fare a lot better as a whole in our financial performance index than both Hardware companies and Software companies.  The average index ranking for all Software companies is 15, while the average ranking for Hardware and Services companies is 26.  Honorable mention, though, should be given to Juniper from the Hardware category (just outside of the overall top 10 and second to Cisco amongst all Hardware companies.  The same designation goes to Cognizant, Wipro, and TCS from the Services category.  All three of these Indian IT services providers also landed just outside of the overall top 10 and were just behind another Indian firm, Infosys, in the services category. 

So, which companies appear to be the best positioned "surfers" today?  Look no further than a solid list of stalwart Software vendors, a couple of tried and true internet plumbing Hardware vendors, and pretty much the entire cohort of major Indian offshore IT services providers.  I love it when intuition, common sense and the data all line up with the sun, the moon and the stars!

login block-for 300 attempts 5 within 50
#apply specified ACl to VTY line when above event occurs, it is meant to exempt
#your managemnt IP form being blocked. After timed block expires this ACL gets removed
#from VTY and previous ACL that was applied before the event is reapplied back

login quiet-mode access-class anti-DOS

#Logging rate-limitation to prevent cluttering logs with failed attempts
login on-failure log every 10

ip access-list standard anti-DOS
 permit 193.193.193.33
 remark Deny VTY access to anyone else if brute-force logins take up all VTY lines
 
!

Theo Maximum PC (08/2008), Cisco đã từ chối hỗ trợ chính phủ Trung Quốc trong việc ngăn chặn các thông tin "độc hại". Mục tiêu của chính phủ TQ được trích dẫn trong bài báo đó như sau:

"...to stop networkrelated crimes, guarantee the security and services of a public network, and combat Falun Gong evil religion and other hostiles.”

 

Theo bài báo này, Cisco đã khẳng định họ không muốn thay đổi sản phẩm của mình để phục vụ lợi ích của bất cứ một quốc gia nào cũng như không muốn kiểm soát các chức năng ngăn chặn đó. Điều này khác hẳn với một số các công ty dịch vụ trên mạng đã từng phải chịu hợp tác với chính phủ Trung Quốc. Tuy vậy, có một câu hỏi ở đây là bất cứ một kỹ sư mạng nào cũng biết, nếu chỉ thực hiện ngăn chặn tội phạm mạng, duy trì tính bảo mật và các dịch vụ công cộng thì đó đã là mục tiêu của bất cứ nhà sản xuất thiết bị mạng nào chứ không riêng gì Cisco. Kể cả trong trường hợp cần ngăn chặn các thông tin chống phá chính phủ thì các kỹ sư mạng của chính phủ cũng hoàn toàn có thể cấu hình để làm chuyện đó. Vậy tại sao, TQ nhất quyết cần Cisco can thiệp? Đặt backdoor vào đồ Cisco được bán trên toàn TQ chăng?

I won't be able to take the lab again until 2009.  I need to build up more vacation time (I accrue PTO (personal time off) at a rate of one day every two weeks) as well as catch up on a pile of work - not to mention end-of-the-year changes. 

I'm in the midst of putting together a training plan.  I had initially decided to take two weeks off but I'm going to start studying again tonight.  Initially I won't be doing a lot of full-scale labs.  I'm going to do a LOT of reading and plan to work though all of the new IE Volume I labs.  In the past I had concentrated most of my study time on weekends because that was when I could set aside blocks of 8 - 12 hours for labs.  I'll eventually get back to doing full-scale labs on the weekend, but since a lot more of my time will be spent reading the Cisco documentation, I am going to commit to at least an hour of study each weeknight as well.  I'll also be reading as much documentation during the lulls at work.  I would like to personally thank the Minnesota Twins, Vikings, and Timberwolves for making sure that I am not tempted to waste any time on sports during this time.

Things I need to work on:

1) Documentation, documentation, documentation.  I need to read as much of the Cisco documentation as is possible so that I can recognize keywords and descriptions that Cisco uses for each technology.  I also need to familiarize myself better with the documentation for technologies that I know well.  I was very aware of where everything is for technologies like multicast, but I never really familiarized myself with the OSFP or QoS (that cost me 3 points!) because I felt very comfortable with those technologies.

2) No weaknesses.  I went into my first attmept very prepared, but there were some technologies that I felt that I was not 100% on and I will use the next 3 months to close the gaps on those.

3) Time management.  I need to cut down on my time creating initial diagrams and reading the lab.  I also need to be able to quickly implement a workaround and move on if I find that I am spending more than 15 minutes on a single task.  I would estimate that the average task value on my lab was around 2.75 points.  I am setting a target of finishing the lab within 6 hours with an initial read-through and diagram creation period of 40 minutes (hopefully less).  (360-40)/(100/2.75) is about 9 minutes per task.  If I have two hours left in the lab I can even make changes to the core (hopefully I don't need to) if needed and have time to identify and fix any other tasks that may be affected by those changes.

4) Utilize the proctor.  Anytime I hit a task that I am not sure how to configure or that I need more clarification, I am going to stop and create a list of questions to ask the proctor.  I'll try to formulate questions that can be answered simply (hopefully with a 'yes' or 'no') that also will not look like fishing expeditions.

5) No last minute review/cramming.  Nuff said.

6) Emulate the testing environment on all practice exams.  I plan to buy a bunch of plastic sleeves and binders.  I'll print out the labs and put them in the sleeves in the binders.  During the lab I will not allow myself to write on the lab at all (a bad habit that I only tried to break one week before the lab).

Things that I though would be an issue but turned out not to be:

1) Telnet client.  I thought that this would be a bigger issue than it turned out to be.  I downloaded a copy of SecureCRT and did my last few practice labs using it.  As long as highlighting text automatically copies it to the clipboard and right-clicking pastes it, I'm fine.  I didn't bother changing any of the defaults other than the colors during the lab.

2) Sleep.  I had very little problem sleeping soundly before the lab.  I was in the Navy and learned to sleep anywhere at anytime (my rack used to be 20 feet under the point that fighter jets landed on a carrier so I can sleep through anything).  I made the mistake of waking up to review, but I had plenty of rest before the lab and was very alert.

3) Vacation on either side of the lab.  This was the thing that I figured would lead to divorce.  :-)  I managed to push the lab out of my mind before my date.  I did get a little nervous the day before and asked my wife to get back to the hotel and study the night before.  After my failure I was still in good enough spirits that I enjoyed the rest of the vacation.  I figured that I would be nervous and grumpy before the lab and despondent and grumpy after failing.  I will note that I did put in the better part of 3 straight weeks of hardcore studying before embarking on this adventure so that may have contributed to my state of mind.

4) Noise in the lab.  I forgot to include this in my lab review, but noise was not an issue for me.  I brought in a pair of earplugs but never used them.  In San Jose, the Voice candidates are located away from the other candidates.  I remember hearing phones ringing, but there was not a lot of this and the sound was easy to ignore.  The dull hum of equipment covered any keyboard or other noise from the other candidates.  I was so locked into my own experience that I didn't even notice anybody else.  I did talk to myself at one point and hopefully I didn't throw off any other candidates with my insane muttering.  :-)

5) Mean proctors.  The proctor was very cool and approachable.  I sensed that he was helping me as much as he could.  I tried to phrase my inquiries as "yes or no" questions and started out each question by reading the part of the task that confused me followed by my interpretation of the task and THEN the question.  As stated before, I am going to work on this process during my review.

Besides the obvious benifits of passing the exam on your first trip is this one: not being haunted by the questions that you missed.  I've been obsessing about the three question run that sank me on the lab.  This is worse than any damned ghost or demon.  I don't remember the details of most of the test but I can remember those three questions nearly word for word.

Well, enough typing.  Time to get back to studying.  After all of this I am still very confident that I can get my digits on my next attempt.  I would like to once again thank all of you for your words of encouragement and well wishes.  I would also like to thank IE for all of their support.  Josh at IE was extremely helpful and I really appreciate all that they've done for me.  Both Brians have reached out to me at different points and offered guidance.  Now if I could just talk one of them into taking the lab for me.  :-)  I would also like to say how much respect and admiration I have for anyone with digits after their names.  Until you actually sit the lab it's hard to understand how mentally and psychologically difficult the test is.  Hopefully I'll be joining their ranks in January.

The following are the key takeaways I extracted:

• Juniper is standards-oriented. In the area of NAC, e.g., they are co-chairing with Symantec the Trusted Computing Group's Trusted Network Connect (TNC) effort. It's not (yet) clear to me how the TCG interplays with the IETF ... And speaking of IETF, Juniper's Network and Security Manager (NSM) makes use of IETF's NetConf standard in, e.g., simplifying the provisioning of new devices on the network.
• Juniper has a comprehensive portfolio of offerings at the intersection of security and networking. Interestingly, Juniper's Security Threat Response Manager (STRM) OEMs technology from Q1Labs.
• 802.1x is a solid bet. Based on a number of trends, and a variety of requirements, Juniper promotes use of 802.1x. Even though this is a path we've already identified, it's good to have it independently validated ...
• Security, and other services, can be offloaded to purpose-built devices in the core. Instead of inserting, e.g., a FWSM into a device (e.g., a Cisco 65xx) that is primarily providing routing and switching services, Juniper has recently introduced a new paradigm with its SRX series. Touted as a services gateway for the core, the purpose of the SRX is to offload from the routing/switching devices various services - e.g., firewall, VPN, etc. As I understand it, the SRX runs JUNOS with various enhancements from ScreenOS (their O/S from their firewall devices). Even if you don't make use of Juniper solutions, it may make sense to understand and potentially apply the offloading-of-services concept/paradigm in your core.
• Juniper allows for the virtualization of switches. Juniper Virtual Chassis (VC) is currently only available for their EX 4200 platform. With VC, it's possible to virtualize up to 10 physically distinct EX 4200s into one. Within the next year, Juniper plans to provide VC on, e.g., their EX 8200 platform. Because vmWare's vMotion requires layer-2 adjacency, server virtualization may prove to be a significant driver for switch virtualization. I expect that this will prove, e.g., to be particularly relevant in providing failover services (at the networking layer) between multiple, physically distinct, and geographically separated locations.

Even though the event appeared to be more of the sales-y/marketing-y variety, there was substantial technical content in evidence.

This topic provides link to configuration notes for Cisco Unified Communications Manager 6.0 that have been created and tested by Microsoft . When Microsoft or a partner deploys Exchange 2007 Unified Messaging with a new IP gateway and PBX or IP PBX configuration, the prerequisites and configuration settings are documented. This information is used to create a configuration note.

PBX configuration note contains information about how to deploy Exchange 2007 Unified Messaging with a specific telephony configuration including the manufacturer, model, and firmware version for the IP gateways, IP PBXs or PBXs. In addition, each PBX configuration note also includes other information such as:

• Contributors in authoring the configuration note.
• Detailed prerequisites, including the following:
  • Features that have to be enabled or disabled on the PBX.
  • Specialized hardware that has to be installed.
  • Is an IP gateway required?
  • Features that must be present on the IP gateway if one is needed.
  • Specific cabling requirements between an IP gateway and a PBX.
  • A list of Unified Messaging features that may not be available with a given telephony configuration

This topic provides link to configuration notes for Cisco Call Manager 5.1 that have been created and tested by Microsoft . When Microsoft or a partner deploys Exchange 2007 Unified Messaging with a new IP gateway and PBX or IP PBX configuration, the prerequisites and configuration settings are documented. This information is used to create a configuration note.

PBX configuration note contains information about how to deploy Exchange 2007 Unified Messaging with a specific telephony configuration including the manufacturer, model, and firmware version for the IP gateways, IP PBXs or PBXs. In addition, each PBX configuration note also includes other information such as:

• Contributors in authoring the configuration note.
• Detailed prerequisites, including the following:
  • Features that have to be enabled or disabled on the PBX.
  • Specialized hardware that has to be installed.
  • Is an IP gateway required?
  • Features that must be present on the IP gateway if one is needed.
  • Specific cabling requirements between an IP gateway and a PBX.
  • A list of Unified Messaging features that may not be available with a given telephony configuration

Congratulations Jo...and good luck with telling your wife about the Voice track.  :-)

"Patient-centred care implies seamless healthcare delivery between different healthcare industry sectors. To ensure this, any patient-related data has to be available “just in time”.'

Essays provide a nice mix of policy and practicum and though this is a 120pg report, it can be read quite quickly.

There are certainly some lessons for the US tucked within these essays as several EU countries are farther along in rolling out HIT. That is not to say all is easy as they do struggle with many of the same issues as we do here. For example, the aforementioned German essay has an interesting Table on pg 68 comparing the Government's HIT strategy, which puts control of medical records into the hands of the consumer, to that of independent healthcare providers who wish to maintain continuity of the record and apparently, control. This challenge is similar to what we face today in the US, particularly with the adven entrance of Google and Microsoft into the market. A common refrain from the provider community is:

If we give consumers control of their records, will we be able to trust the record at some future point of time? Will the record be truly representative of the consumer's complete health record? What liabilities might I be subjected to if I make decisions based on the PHR?

Sean Nolan, Microsoft HealthVault's chief architect (and certainly many others at HealthVault), struggle with this issue on nearly a daily basis and today, there are no easy answers.

In a couple of short weeks at the Connected for Health Symposium here in Boston, I'll be moderating a panel that takes a good hard look at where we are today with the major personal health platforms (Dossia, Google & HealthVault) and WebMD on the panel. As the symposium audience is strongly represented by large providers, this is one issue that I'll be looking to explore further with the panel.

Simple script to backup Cisco devices configurations.

Features:

Automatically copy configuration via tftp.
Compare previous configurations with new downloaded with "diff" command.
Send email alert if configuration change and attach to alert new and old configurations.
Always keep a backup copy.

Configuration:

Uncompress the archive in a place like /opt/ciscobk.
Take a look to ciscobk.sh in order to correct paths according to your configuration.
Open etc/ciscobk/ciscobk.conf and put ip addresses of your Cisco device.
Open etc/ciscobk.mail and type here mail addresses that'll receive mail alert.

HowTo configure Cisco device:

First of all I'm assuming that you know what you're doing…I'm not responsible if you destroy your running config then "wr"…
Ok, we're ready, go in enable mode and simply type

myrouter# conf t
myrouter# tftp-server nvram:startup-config
myrouter# wr

Now your Cisco device is ready to serve his configuration to anyone; I recommend to use ACL's to prevent somebody hack your router…

Click here to download CiscoBk V 0.5 ]]> http://cciepursuit.wordpress.com/?p=937 Wed, 08 Oct 2008 05:22:18 +0000 cciepursuit http://cciepursuit.tr.wordpress.com/2008/10/07/my-lab-experience-part-ii/ The Lab

The proctor pointed out a clock on the wall and proclaimed that to be the official lab time.  The clock on my PC was 9 minutes faster than that clock.  :-)  With that we were off and running.

I removed all of the plastic sleeves and created an L3 and L2 map.  To be honest, the L3 map in the lab is very complete.  As mentioned in the IE Mock Lab Workshop, you'll still want to have your own version that you can mark up to your heart's content.

I created a task tracking grid and then I read the lab from start to finish.  As I read each question I put a smiley face in the notes section of my task grid for each task that I knew how to finish.  I placed a question mark for tasks that seemed doable yet might need more clarification.  A frowny face was recorded for each task that I knew would be troublesome.  After reading through the lab I felt that I had a very good chance at passing it.  About 75% of the tasks had smiley faces and only 3 tasks bore the dread frowny face (I feel really silly typing "frowny face" right now).

By the time that I typed my first line of configuration nearly an hour had already passed.  This is something that I need to speed up.  This really should have been a 30 - 40 minute process.  I really could have used an extra 20 minutes at the end of the lab.

I worked through all of the switching tasks and half of the IGP tasks before lunch.  Lunch comes 3 hours into the lab in San Jose.  This threw me off a bit as I am used to trying to get through IGP redistribution before lunch.  Of course, it means that you have 5 hours on the other side of lunch but I was still thrown off.

I did not leave my seat during the first 3 hours.  I ended up asking only one (dumb) question of the proctor.  Even though I read the lab I really only read it to look for pitfalls and whether or not I knew how to configure the tasks.  I missed some basic information that lead to me asking one dumb question and almost lead to another stupid one (not to mention some time lost doing some unnecessary troubleshooting). 

Lab Tip: Read your lab carefully (but quickly).  There may be information in the lab that is presented well after when you need to use it.

Lab Tip: Use your lunch break to your advantage.  I configured right up until the lab break (I wrote my configs right before lunch).  I should have reread a couple of tasks that I had tagged with question marks and used the lunch time to think about them.

Lunch

We lined up at the door and marched across the campus to the cafeteria.  You are given a $10 voucher for lunch.  This reminded me of the Brian Dennis joke about the lab being "a $1390 rack rental with a $10 lunch voucher".  I was absolutely not hungry.  I grabbed some watermelon juice and some salad.  Neither were very good but I was too worried about how far along I was in the lab to taste anything.  :-)

As we sat (mostly speechless) at the table we noticed that one of the candidates was missing.  You guessed it, Mr. Handshake was not among us.  The proctor had to get up and hunt him down again.

You get 30 minutes for lunch along with 10 minutes for the march to the cafeteria and back.

The Proctors

I should say the proctor.  I don't know if there was another proctor in the lab (I think that there was but he was near the voice candidates) as I only went to one proctor.  I probably ended up asking about a half dozen questions.  The proctor was very cool and I got the sense that he was helping out as much as he could.  There was one line in a task that I just couldn't make sense out of and I asked him about it until he finally told me that I had all of the information that I needed.

The Final Lap

I sat down and started back up with a pronounced sense of urgency.  I was the last few IGP tasks that absolutely sank me.  I had two tasks that I could not figure out what the hell the task required.  I had two other tasks that I could complete most of the task but not one sub task of each task.

By the time I got done with IGP I was down to just over 3 hours remaining.  I had to finally eat 6 points and move on.  That was the lowest moment of the exam for me.  I got full reachability, but I knew that I had missed at least 6 points and possibly 12 points.  Plus my damned "frowny faces" were still ahead of me.

I decided that I was not going to pass at that point.  I was so disheartened that I even thought that I would never do the lab again.  I had prepared like hell for a year straight and I tripped up on a couple of stupid questions.  I decided to just plow through the rest of the test because it was a better choice than crying.  :-)

So with a bemused disposition I carried on.  Somehow I managed to finish with about an hour left.  I was still convinced that I had failed the lab until I took a look at the points that I either skipped or had not finished because I needed more clarification.  I added those points up and they totaled 25 points.  Hope made an unexpected return to the party.  I had an hour left and I needed to get at least 6 points to have a snowball's chance in hell of passing the lab. 

I hit the documentation and managed to knock out all but 3 tasks.  One was a task that I couldn't get my head around and was obviously going to take too long to configure even if I could figure it out.  The one that bothered me the most was the 3 points that I lost due to a QoS feature that I couldn't remember and didn't know the QoS documentation well enough to find it.  Colossal brainfart.  I can't remember the other task.  I would make a really bad braindumper.

So basically I had about 15 minutes left and was looking at 85 points (9 points lost for the uncompleted tasks and 6 points lost for the IGP tasks).  I could either make another stab at the IGP tasks and possibly screw up a end-to-end reachability or I could try to mine the documentation for at least one of the uncompleted tasks - or - I could review at least part of the lab.  I chose the third option and found one boneheaded mistake (really boneheaded since I had already "fixed" the issue once).

With the few minutes remaining I stripped out all of the configuration that I added like "logg sync" and "no ip domain-lookup" plus my ping macros on my switches.

At 5:10 pm the proctor called the lab and we were free to wander out of the building.  I grabbed my $1400 Diet Mt Dew and walked out.  There were a few candidates gathered outside.  Only one thought that they had passed.  The rest echoed my "I'll be back" comment.

You know the rest of the story.  I did go take another look at my score report and I was probably closer to passing than I thought.  I didn't memorize the points for each section so I can't be sure of my final score.  I guess that I can take solace in the fact that there were no sections where I scored 0%.  I scored high in switching.  I had a mid-range score in IGP.  The rest of the sections ranged from 25% to 75% with the exception of the 100% in Security (my weakest section).  I obviously could have benefited from time to review the full lab as I missed a some points in sections which I was confident that I had got all of the points.

Post Mortem

So what do I feel were my reasons for failure:

1) Speed.  This was minor because my "speed" suffered from my wasting time on the IGP tasks that I eventually had to forfeit the points.  I could have sped up the initial lab read and diagram making.

2) Question interpretation.  This was the big one.  A majority of the questions would not come out and tell you what technology to use, but would rather use a description of that technology.  Sometimes these descriptions were either foreign to me or they concentrated on a minor feature of said technology.  This threw me.  Sometimes I could mine the documentation using some of the keywords to figure out what the technology was, but there were a couple of descriptions that just did not make sense to me.

3) The ability to move on.  I was actually pretty good at this.  I have this problem with skipping tasks if I have some idea how to complete them (which was 95% of this lab).  I actually skipped some tasks, but I wasted way too much time on those IGP tasks.  I convinced myself that I could not pass the lab without getting those points.  The truth is that I should have moved on much earlier.  I could have probably picked up the 3 extra points in QoS with more time and possibly figured out those IGP tasks.

4) Familiarity with the documentation.  I am pretty familiar with the documentation for the tasks that I have trouble with.  I've always been pretty good at QoS so I did not really use that section too often.  This bit me in the ass when I brainfarted on the QoS issue.

5) Utilizing the proctor.  This relates to the question interpretation issue.  It's also a psychological issue - especially after my first question was a dumb one.  I didn't want to come off as stupid or to keep bugging the proctor until he tired of me.  I should have continued to ask questions to try to clarify the tasks.  My goal should be to pass the test, not to impress the proctor.

So these certifications are a distinct advantage for job seekers. www.certified-easy.com
Prepared all top online exam details such as number of questions, exam duration, price etc. So you can decide which exams you want do after going thru the details.

Additionally, www.certified-easy.com has a large base of E-Books links that collected from the web. So if you decided to do one exam, there are lots of references and exam guide links on that site. So this is a very good site for students and job seekers who need help.
The owner of this site is working to collect visitor’s book request, So that ebook links will be publish in near future.

As experts compare today's troubles to the 1930s, it's helpful to remember that back then, various safety nets didn't exist. There was no swift action from the Fed. There was no FDIC. And there was no Treasury Secretary as proactive as Paulson. (Nor were there effective anti-depressants and other drugs to get us through this mess!) These are just a few reassuring points to come out of the Most Powerful Women Summit. A few other random bits of hope:

Buffett professed his faith in the government folks on the spot: "I hope whoever is elected keeps Hank Paulson on," the Berkshire Hathaway (BRK.B) CEO said. "I have enormous admiration for what he's doing." Buffett, the world's most successful investor, also expressed admiration for FDIC Chairman Sheila Bair. This week, she's taken flak for her role in the Citigroup vs. Wells Fargo (WFC) battle for Wachovia (WB), but Buffett said she "stands above" most any CEO and "she won't get a golden parachute when she leaves." (Click here for yesterday's Postcard post that will link you to various Buffett video segments.)

PepsiCo (PEP) CEO Indra Nooyi showed how, amidst gyrating commodity costs, consumer-goods managers deliver healthy profit increases quarter after quarter. Nooyi, who is No. 1 on Fortune's 2008 Most Powerful Women list, also talked about tackling the obesity epidemic. As PepsiCo's volumes have gone up over the past decade, the calories that the company puts into the global marketplace have actually gone down dramatically. Credit goes to innovation with diet drinks, Baked Lays potato chips, and replacement of trans-fats. PepsiCo rates executives according to "human sustainability scorecards" and ties compensation to the scores. As Nooyi told us, if every food company did this, imagine how much healthier the world would be.

Our panel called "The Internet 10 Years Later" (a reprise of a panel at our very first MPWomen Summit) delivered positive signals for growth. Cisco (CSCO) CTO Padmasree Warrior noted that "every second on earth, four babies are born and 20 mobile devices are sold." The session -- including Morgan Stanley (MS) analyst Mary Meeker, former eBay (EBAY) chief Meg Whitman, and Facebook COO Sheryl Sandberg -- revealed other interesting stats: China recently surpassed the U.S. in Internet usage. And though the U.S. has lagged in mobile Internet usage, Apple's (APPL) and Google's (GOOG) focus on mobile suggests that the U.S. will lead in that market.

The Summit's closing panel, "The Road to the White House" had Citi CMO Lisa Caputo (on one hour's sleep, she said) interviewing two ace political journalists -- Time's Karen Tumulty and Fortune's Nina Easton -- plus Obama national finance chair Penny Pritzker and Meg Whitman, who is co-chairing the McCain campaign. The panelists believe that voter turnout could reach 80% in November, vs. 64% in the 2004 Presidential election. That level of commitment to revive the U.S. might be the most encouraging sign of all. - Jessica Shambora

TextBox "Ver Carta" filtra pelo ifDescr do interface de rede. Se tiver o checkbox selecionado apenas são exibidos os filtros e omitidos eventuais alertas pontuais.

EN: TextBOX "Ver Carta" filters by Interface Description of upstream interface if checkbox is selected then only the filtered items are shown everything else is ommited.

link: http://netcrash.no.sapo.pt/Software/snr.zip
Readme: http://netcrash.no.sapo.pt/Software/README.txt

Hago gran énfasis en certifican, porque es importante resaltar que es la forma en que pueden demostrar que lo que han aprendido, realmente lo pueden llevar a la práctica. Es la forma en que los Partners de Cisco seleccionan a sus candidatos a ocupar un puesto en su empresa. Es la forma en la que los, ahora estudiantes, pueden sentirse seguros de pedir lo que realmente vale una persona con certificación. La diferencia entre un certificado y no certificado lo es TODO. 

A todos los estudiantes les pedimos que aprovechen la oportunidad que se les da en sus Universidades, pregunten a sus instructores cómo obtener los vouchers de descuento para el examen de certificación.

Asi pues aquellos que estaremos en la concentración de redes para que vean que necesitamos certificarnos al salir, digo no es trabajo seguro pero a lo menos suena como oportunidad.

Artículo Editorial del boletín de México sin brecha digital. Para suscribirse enviar tu mail a redaccion@mexicosbd.org diciendo que perteneces a la academia "ITESM Campus Mazatlán"

Aqui esta el link del boletín si le quieren dar una leida completa: http://www.mexicosbd.org/Newsletter/Septiembre/MSBDNews_Septiembre08.html

Aprovechando para Felicitar a Laura que hoy es su cumple, te queremos Lau te queremos xD

What I wanted to achieve was to connect two 7600 routers over an Ethernet pseudowire (E-Line, EoMPLS circuit, AToM circuit, Martini circuit - whatever it's called these days).   The reason I needed to do so was that the interveninig 6500 routers were only getting a default route via BGP from the 7600s.

The network looks a bit like this:

The routers R1 and R2 have a full internet routing table, and they send only a default route to the 6500s (because the supervisor on these switches can't handle all the routes).

Configure a full iBGP mesh and everyone's happy, right?   That's what I thought, but it didn't work out that way.

The customer implemented this and found that when the transit peerings on R1 were down, there was a routing loop.  The reason is that although R1 still has the full routing table from R2 via the peering they have, when packets are sent by R1 to the left-hand 6500, it only has a default route.  That default route is coming in from R1 - so it just sends the packets back to R1!

So, short of investing in a new circuit to connect the two routers up directly, there were several options available:

1. Configure the site inter-link as a layer-2 one, and run VLAN tags across it

2. Configure an EoMPLS circuit between new sub-interfaces on R1 and R2
We didn't like the sound of option 1, because to make the VLAN resilient would require spanning-tree.  So we went for option 2 instead.

The interfaces on the 6500s were trunk links, so I thought to make this new interface I'd need to configure a VLAN and an SVI.  Then put the MPLS "xconnect" command on the SVI.  This didn't work though - the command "show mpls l2transport vc detail" was coming up with "Invalid NEXT HOP" or something like that.   So I thought the plan was dead in the water.  However, the following 6500 config worked very nicely:

interface GigabitEthernet2/1
 switchport
 switchport trunk allowed vlan 101
 switchport mode trunk
interface GigabitEthernet2/1.100
 encapsulation dot1Q 100
 no snmp trap link-status
 xconnect 192.168.201.2 100 encapsulation mpls

This is the configuration of the 6500 port facing the R1.  VLAN 101 is the one that carries OSPF for iBGP peerings between R1 and the two 6500s.  Sub-interface Gig2/1.100 is the start of an EoMPLS circuit that runs across to the other 6500.   Packets received with VLAN tag 100 are encapsulated in MPLS and transported across the network.  R1 and R2 now have a direct connection.

Don't forget what most Cisco MPLS books don't tell you - if you're running MPLS and configuring EoMPLS, the MTU on the MPLS-enabled interfaces needs to be increased by 8 bytes.  This is to cope with the TWO MPLS labels that are applied to the packets.  The outer label is used for hop-by-hop forwarding of the packet to the egress PE, while the inner label is used to tell the egress PE which VPN the packet belongs to (based in this case on the VC ID).   The VC ID (in this case the number 100 on the xconnect command) needs to agree at both ends and be unique.

Anyone who feels less confident about their chances of passing the lab based on my failure - don't.  The lab that I took was eminently passable.  I almost wish that I had received a really tough lab as my ego would be a little less bruised.  The reason for failure lies completely with me. 

Which leads to my second caveat: I am not an authority.  Don't feel that because I didn't pass that means your chances are diminished.  If you're using IE's workbook then just know that my lab only had two technologies not present in the Volume II/III workbooks* - both of which were fairly easy to find in the documentation.  At the end of the day I'm not a Brian or Petr or Marvin or Jared or Scott or [insert favorite vendor instructor here] but rather just some dude on the Internet posting about my personal quest for the holy digits.  You should NOT let my failure affect your preparation strategy.  Again, the lab I received was passable and you may not trip on the same tasks that I did.

*I did not complete all of the labs Volume II labs.  I completed all of the labs except the ones with a difficulty rating of 10.  Also, my memory is not perfect so these technologies may be present in the IE labs.  My point is that there was very little in the way of "surprise features" on my lab.

Finally, I need to respect the NDA.  If you have any questions about the lab feel free to leave a comment with your question.  I will answer it to the best of my ability but if doing so would break the NDA then I will not be able to answer it. 

Anyhoo...here's my lab experience.

The Night Before

You may want to read this part with your eyes closed.  :-)  My wife and I flew into SFO on Monday and proceeded to have a blast in the city.  Either the streets in Chinatown have gotten a lot steeper or I'm more out of shape than I realized.  :-)  On Wednesday we picked up a car and drove down to Monterey.  We were back in San Jose by 6 pm.  I had brought along a bunch of my IE labs and solution guides and read through a number of them for review.  By 9 pm I was exhausted.  I still had not reviewed the CCIE Routing and Switching Practice Labs so I decided that I would get up at 3 am and review until I left for the exam.  That would give me 6 hours of sleep and I really did not think that I would be able to sleep.  I slept like a baby.  A baby who dreams about IOS.  The hotel I stayed was ill-staffed (to say the least) and when I tried to call for a wake up call, I was promted to page out the front desk...at 8:30 pm!  Screw it, my wife set the (piece of crap) clock radio for 3 am.

3 am rolled around and I woke up to a barely perceptible blast of radio static.  I got up and took a shower.  While in the shower I remembered that I had set the alarm on my phone to go off at 3 am as well.  I quickly finished my shower in an attempt to stop that alarm from waking my wife.  I picked up my phone and looked at the time.  It was a few minutes past 1 am!  I looked at the clock radio and it read 2:15 am.  WTF?  My wife later told me that she set the alarm for 2 am instead of 3 am and that the clock must have been an hour ahead of local time.  Oh well, more time for study.

I read through the CCIE Routing and Switching Practice Labs as well as a number of my IE labs and notes.  At 5 am I crawled back into bed to nab another 1.5 hours of sleep.  I woke up again (still no problem sleeping) at 6:30 am and went through a few notes as well as reviewing the location (we had driven to the location the night before) and time of the lab.  At 7:45 we were on our way.

Lab Tip #1:  Bring your own alarm clock.

Lab Tip #2:  Don't bother with any last minute review.  I gained absolutely nothing by doing this and lost some sleep time.  The sad thing is that I'm wired for shit like this.  I had gone a few days without any review and didn't want to fail the lab and regret not doing "one last review".  If you're wired the same way as I am (I've done this from college on) then try to convince yourself that sleep is more important than any last minute review.

Lab Tip #3:  Drive to the testing location the night before the lab.  The hotel that I stayed at (Extended StayAmerica San Jose - Santa Clara) was located on Gold Street (basically Lafayette Street about the 237).  Lafayette drive passes BENEATH Tasman Drive so you need get off on Calle del Mundo and follow that street to Tasman Drive.  If we hadn't noticed that the night before I would have been pooping myself on the morning of the exam.  :-)

Quick Hotel Review

Extended StayAmerica San Jose - Santa Clara  is located about 2 miles from the testing center (right across from some Foundry Networks buildings).  It's a walkable distance, but you really don't want to worry about getting to the test center on time so you'll probably want a car or hire a cab.  The hotel did not offer a shuttle to the Cisco campus.

The hotel was relatively cheap ($120 per night with taxes) and was serviceable.  It has a kitchenette and there is a Safeway nearby.  The hotel must be going through renovations.  The room we stayed in was clean but the hallways were pretty filthy.  I didn't really care.  The only issue I had was that the hotel "upgraded" us to a double rather than a king.  I asked if the room was the same size and was told that it was.  I then asked how they considered the extra bed to be an "upgrade"?  No answer.  :-)

Wireless Internet is available for $4.95 per stay.  That was the cheapest and most stable WiFiconnection I had on my entire trip.  That just tells you how expensive and crappy the WiFi experience was at the various other hotels and airports. 

I won't recommend the place for your honeymoon but I felt that it was okay for a night or more before your lab.  I'll probably stay there for my next attempt.

Arrival

I arrived at Building C around 8 am.  You'll need to check in with the security guard and present a government issued ID (a driver's license is fine) and then wait for the proctor to come down around 8:15.  There is a notice on the door stating that the building access hours are 7:30 am - 5 pm so you probably do not want to arrive before 7:30 am.

There were about 10 candidates that day.  Everyone was on time.  Around 8:15 a proctor will come down and call out your name.  You'll need to present your ID once again and the proctor will give you a name tag.  One of the candidates came forward when his name was called and offered his hand to the proctor.  This confused everyone as he was one of the last candidates called and should have seen that everyone else was showing their ID.  Eventually the confusion was cleared and we followed the proctor to the lab.  All along the way there were signs on the wall with "CCIE" on them so it would be very hard to get lost.

We arrived outside the lab and quickly found that one of the candidates was missing.  Somehow Mr. Handshake had separated himself from the group.  The proctor left us outside the lab and went back to get him.  This took about five minutes and needless to say the proctor was not happy and did not hide the fact.  Wonderful, this jackass had the proctor in a foul mood already.

We were told to turn off our cellphones and place them and any bags on a bench.  We were then split into two groups: voice candidates and non-voice candidates.  At that point the second proctor arrived (I'm horrible with names - I think that the first proctor's name was Tom but I completely forgot the second guy's name).  You will be assigned a station (the station number will be important for your exam).  The proctor asked how many first-timers there were and me and two other guys raised our hands.  The proctor went through a very quick tutorial on the workstation.  The guys who had been to the lab before took this opportunity to start their labs while this was happening.

The Lab Station

The exam room is large.  There are stacks of equipment throughout the room and there is a constant buzz of fans.  It's like being in a small data center without the ice cold air conditioning.  I wore a short-sleeved shirt with slacks and was comfortable [to be honest once you're locked into the lab it could be absolute zero with live rounds being fired at your head and you most likely would not notice].  A couple of the candidates showed up in tshirts and shorts so dress comfortably and don't worry about any type of dress code. 

We were not allowed to bring any food or drinks into the lab.  I didn't ask whether or not gum was considered food (I chewed gum the entire time).  There is a break room around the corner that has a cooler stocked with sodas (Diet Mt Dew was in full effect!) and juices as well as coffee and tea.  The men's restroom was direct across the hallway from the lab.  If you need to use the restroom or the break room you need to use an access card.  There is only one access card.  Only one candidate could leave the room at a time.  Well, you could leave the room without the card but you would not be able to get back in.  :-) 

Each station had a container with a number of highlighters, markers, and pens.  I didn't bring anything into the lab except my wallet and a pair of ear plugs.  I don't remember hearing whether or not you are allowed to bring in any pens/markers/highlighters of your own and no one asked about it.  The writing implements at my station seemed to be a collection of hotel pens, decent highlighters (pink, yellow, and blue) as well as some colored pencils.  Nothing outstanding, but all usable.

You are given a single sheet of paper.  You can ask for one additional sheet at a time, but you need to present your paper to the proctor when doing so.  I only used one sheet as it was huge.  It was probably 16 inches by 8 inches.  I folded it in half and used one quadrant each for my L3 drawing, L2 drawing, and task tracking grid.  This left a full quadrant for notes.  You are told not to rip off pieces of the paper (your sheet must be intact).  I did not ask if you could tear the sheet in half - which I wanted to do - but the few times that I needed to unfold/flip the paper presented no problems.

Your desktop will be set up with individual shortcuts for telnetting to each device.  There is also a shortcut for a terminal server if you want to go that route (I did).  You'll have access to Notepad and the Windows calculator.

A quick note about the Windows calculator.  For some reason mine was set to hexadecimal view.  I couldn't figure out whether I should use qword, dword, word, or byte.  :-)  I didn't realize until after the lab that I should have changed the view to decimal mode.  I don't know if the hexadecimal setting was just the previous candidate being a douche-bag or if it was the proctors making the lab a bit more challenging, but let my embarrassing calculator skills be a warning.  :-)

[caption id="attachment_931" align="aligncenter" width="480" caption="Windows Calculator in Decimal Mode"][/caption]

 

[caption id="attachment_933" align="aligncenter" width="475" caption="Windows Calculator Settings for Decimal Mode"][/caption]

 

Your lab binder will be on your station.  The lab pages are enclosed in clear plastic sleeves.  You are allowed to remove the plastic sleeves but you are NOT allowed to remove the lab papers nor to mark the papers or plastic sleeves in any manner.  The proctors are VERY serious about this.

Remember that the following points pertain to my station in the San Jose location on 02 October, 2008.  I have heard that each location (and perhaps each station) may be different. 

1) You are allowed to save configurations to the desktop with Notepad.  I asked about this and used this method to save out my TCL scripts.

2) I could not open any PDFs (well I could, but it would open in Notepad and good luck reading that mess).  I tried saving a PDF to the desktop and then opening it, but I could not even save the PDF.  A quick look at the installed programs showed that Adobe Reader was NOT installed on my machine.

3) The version of SecureCRT was older and did not support tabs.  I am a Tera Term Pro baby so I was a little worried about cut and paste features in SecureCRT.  It was not an issue.  Any highlighted text was copied to the clipboard and pasted with a right-click.  The experience was very similar to using the Windows CMD window with QuickEdit and Insert modes selected.  The only change that I made was to change the background and text colors.

4) The browser is version 6 of Internet Explorer.  There was no tab functionality.

I did not ask if you could save configurations to flash.  The proctors never brought it up and it was not addressed in the lab.  I had no need to do so, but I have heard rumors that you can do this as well as rumors that this will cause you to fail the lab.

Google

CIA

Cisco

Rogers

Este "Megaplan de formación profesional ‘Becas Control F’” destinará una inversión de aproximadamente $20 millones gracias (¿?) a un acuerdo firmado entre el Estado y corporaciones como Microsoft, IBM, Sun Microsystems, Cisco y Oracle.

Mas allá de estar en desacuerdo en este tipo de prácticas y me refiero a las negociaciones por parte del Gobierno con empresas que proveen software privativo en su mayoría (exceptuando el caso de Sun, claro está) creo que no es un plan demasiado ambicioso teniendo en cuenta que con esos 20 millones se capacitarán a 12000 personas durante los 18 meses que durará dicho Plan, lo que dá algo menos de $100 por mes/persona a capacitar. Cualquier persona dentro del mundillo de la informática sabe que con tan poco dinero mensual es muy difícil dar formación técnica relevante a alguien que se pretende insertar en este ámbito laboral.

Lo peor de todo esto es que el gobierno sigue haciendo negociados con Microsoft para lograr su "alfabetización tecnológica e integración" en este ambiente, cuando por otro lado los gobiernos de paises muchos mas avanzados tecnológicamente prefieren hacer acuerdos con compañias proveedoras de Software Libre...

Por eso es que no me queda claro si el plan deberia llamarse "Control F", "Control K" o "Control ALT DEL"

Imagen de los teclados que se usarían para el Plan Control F

IP Address adalah alamat yang diberikan ke jaringan dan peralatan jaringan yang menggunakan protokol TCP/IP. IP Address terdiri atas 32 bit (biary digit atau bilangan duaan) angka biner yang dibagi dalam 4 oket (byte) terdiri dari 8 bit. Setiap bit mempresentasikan bilangan desimal mulai dari 0 sampai 255.

Jenis-jenis IP Address terdiri dari :

1. IP Public

Public bit tertinggi range address bit network address
kelas A 0 0 – 127* 8
kelas B 10 128 – 191 16
kelas C 110 192 – 223 24
kelas D 1110 224 – 239 28

2. Privat

IP Privat ini dapat digunakan dengan bebas tetapi tidak dikenal pada jaringan internet global. Karena itu biasa dipergunakan pada jaringan tertutup yang tidak terhubung ke internet, misalnya jaringan komputer ATM.

10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255

Kesimpulan
1.0.0.0 - 126.0.0.0 : Kelas A.
127.0.0.0 : Loopback network.
128.0.0.0 - 191.255.0.0 : Kelas B.
192.0.0.0 - 223.255.255.0 : Kelas C.
224.0.0.0 = 240.0.0.0 : Class E, reserved.
3. Ipv6
terdiri dari 16 oktet, contoh :
A524:72D3:2C80:DD02:0029:EC7A:002B:EA73

Subneting

Seorang Network Administrator sering kali membutuhkan pembagian network dari suatu IP Address yang telah diberikan oleh Internet Service Provider (ISP). Dikerenakan persedian IP Address pada saat ini sangat terbatas akibat menjamurnya situs-situs di internet. Cara untuk membagi network ini disebut dengan subneting dan hasil dari subneting disebut subnetwork. Langkah-langkah subneting adalah sbb :

contoh 2:
Suatu perusahaan mendapatkan IP adress dari suatu ISP 160.100.0.0/16, perusahan tersebut mempunyai 30 departemen secara keseluruhan, dan ingin semua departemen dapat akses ke internet. Tentukan network tiap departemen ?

Solusi ;
1. Tentukan berada dikelas mana ip tersebut ? B
2. Berapa jumlah network yang dibutuhkan ?
dengan rumus 2n > network yang dibutuhkan
25 > 30
3. Ubah menjadi biner

network-portion host-portion
10100000 01100100 00000000 00000000
11111111 11111111 00000000 00000000

4. Ambil bit host-portion sesuai dengan kebutuhkan network, sehingga

network-portion host-portion
10100000 01100100 _ _ _ _ _ 000 00000000
11111111 11111111 1 1 1 1 1 000 00000000

perhatikan oktet ketiga
_ _ _ _ _ 000
1 1 1 1 1 000

Cara 1
Dengan mengkombinasikan bit

00001 000 = 8
00010 000 = 16
00011 000 = 24
00100 000 = 32
00101 000 = 40
00110 000 = 48
...............
11111 000 = 248

Cara 2
Mengurangi subnet mask dgn bilangan 256

11111 000 = 248

256 – 248 = 8 maka subnetwork adalah kelipatan 8

No Depertemen Subnetwork (255.255.248.0)
1 Pertama 160.100.8.0
2 Kedua 160.100.16.0
3 Ketiga 160.100.24.0
4 Keempat 160.100.32.0
5 Kelima 160.100.40.0
6 Keenam 160.100.48.0
7 Ketujuh 160.100.56.0
.. .............
30 Ketigapuluh 160.100.248.0
Maka

Network Broadcast Range-Hoat
160.100.8.0 160.100.15.255 160.100.8.1 - 160.100.15.254
160.100.16.0 160.100.23.255 160.100.16.1 - 160.100.23.254
160.100.24.0 160.100.31.255 160.100.24.1 - 160.100.31.254
160.100.32.0 160.100.39.255 160.100.32.1 - 160.100.39.254
160.100.40.0 160.100.47.255 160.100.40.1 - 160.100.47.254
160.100.48.0 160.100.55.255 160.100.48.1 - 160.100.55.254
160.100.56.0 160.100.63.255 160.100.56.1 - 160.100.63.254
160.100.64.0 160.100.71.255 160.100.64.1 - 160.100.71.254
160.100.72.0 160.100.79.255 160.100.72.1 - 160.100.79.254
........ .......... .............
160.100.248.0 160.100.255.255 160.100.248.1 - 160.100.255.254

VLSM (Variable Leght Subnet Mask)

Konsep subneting memang menjadi solusi dalam mengatasi jumlah pemakaian IP Address. Akan tetapi kalau diperhatikan maka akan banyak subnet. Penjelasan lebih detail pada contoh :

contoh 2:
Pada suatu perusahaan yang mempunyai 6 departemen ingin membagi networknya, antara lain :
1. Departemen A = 100 host
2. Departemen B = 57 host
3. Departemen C = 325 host
4. Departemen D = 9 host
5. Departemen E = 500 host
6. Departemen F = 25 host

IP Address yang diberikan dari ISP adalah 160.100.0.0/16

Apabila kita menggunakan subneting biasa maka akan mudah di dapatkan akan tetapi hasil dari subneting (seperti contoh 1) tersebut akan terbuang sia-sia karena hasil dari subneting terlalu banyak daripada jumlah host yang dibutuhkan. Maka diperlukan perhitingan VLSM yaitu :

1. Urut kebutuhan host yang diperlukan
1. Departemen E = 500 host
2. Departemen C = 325 host
3. Departemen A = 100 host
4. Departemen B = 57 host
5. Departemen F = 25 host
6. Departemen D = 9 host

2. Ubah menjadi biner

network-portion host-portion
10100000 01100100 00000000 00000000
11111111 11111111 00000000 00000000
Jika pada subneting dimabil dari network maka pada VLSM diambil pada dari host

l Untuk 500 host
network-portion host-portion
10100000 01100100 00000000 00000000
11111111 11111111 00000000 00000000

Untuk 500 host dimabil 9 bit dari host-portion karena
2n-2 > jumlah host

Hasilnya 160.100.0.0/23

Network Broadcast Range-Hoat
160.100.0.0/23 160.100.0.255 160.100.0.1 - 160.100.1.254
160.100.2.0/23 160.100.2.255 160.100.2.1 - 160.100.3.254
160.100.4.0/23 160.100.4.255 160.100.4.1 - 160.100.5.254
160.100.6.0/23 160.100.6.255 160.100.6.1 - 160.100.7.254
160.100.8.0/23 160.100.8.255 160.100.8.1 - 160.100.9.254
........ .......... .............
160.100.254.0/23 160.100.254.255 160.100.254.1 - 160.100.255.254

l Untuk 325 host kita masih dapat menggunakan subnet dari 500 host karena masih dalam arena 29 dan pilihlah subnet yang belum digunakan.
l Untuk 100 host menggunakan 28 > 100 dan ambil salah satu dari subnet sebelumnya yang belum terpakai.
misal 160.100.2.0/24

network-portion host-portion
10100000 01100100 00000010 00000000
11111111 11111111 00000010 00000000

maka
Network Broadcast Range-Hoat
160.100.2.0/24 160.100.2.255 160.100.2.1 - 160.100.2.254
160.100.3.0/24 160.100.3.255 160.100.3.1 - 160.100.3.254

l Untuk 57 host menggunakan 26 >57 dan ambil salah satu dari subnet sebelumnya yang belum terpakai.
misal 160.100.3.0/24

network-portion host-portion
10100000 01100100 00000010 00000000
11111111 11111111 00000011 00000000

maka
Network Broadcast Range-Hoat
160.100.3.0/26 160.100.3.91 160.100.3.1 - 160.100.3.90
160.100.3.64/26 160.100.3.63 160.100.3.65 - 160.100.3.126
160.100.3.128/26 160.100.3.127 160.100.3.129 - 160.100.3.190
160.100.3.192/26 160.100.3.191 160.100.3.193 - 160.100.3.254

l Untuk 25 host menggunakan 25 > 25 dan ambil salah satu dari subnet sebelumnya yang belum terpakai.
misal 160.100.3.192/25

network-portion host-portion
10100000 01100100 00000010 00000000
11111111 11111111 00000011 00000000
maka

Network Broadcast Range-Hoat
160.100.3.192/27 160.100.3.223 160.100.3.193 - 160.100.3.222
160.100.3.224/27 160.100.3.255 160.100.3.225 - 160.100.3.254

l Untuk 9 host menggunakan 24 > 16 dan ambil salah satu dari subnet sebelumnya yang belum terpakai.
misal 160.100.3.224/25

network-portion host-portion
10100000 01100100 00000010 00000000
11111111 11111111 00000011 00000000

maka
Network Broadcast Range-Hoat
160.100.3.224/28 160.100.3.239 160.100.3.225 - 160.100.3.227
160.100.3.240/28 160.100.3.255 160.100.3.241 - 160.100.3.254

Artikel by: Gindo Ariefman
Note: Penulis adalah Asisten CNAP (Cisco Networking Academy Program) di Lab Komp Fisika UI, Jika ada pertanyaan silahkan dapat menghubungi beliau, thx :-)

Suatu perusahaan mendapatkan IP Address Public dari suatu ISP 160.100.0.0/16, perusahan tersebut mempunyai 30 Departemen secara keseluruhan, dan ingin semua Departemen dapat akses ke internet dengan IP Public. Tentukan network tiap departemen ?

Solusi ;
1. Tentukan berada dikelas mana IP Address tersebut ? B
2. Berapa jumlah network yang dibutuhkan ?
Dengan rumus 2n > network yang dibutuhkan ( n = bit yang dibutuhkan )
25 > 30
3. Ubah menjadi biner

network-portion host-portion
10100000 01100100 00000000 00000000
11111111 11111111 00000000 00000000

4. Ambil bit host-portion sesuai dengan kebutuhkan network, sehingga

network-portion host-portion
10100000 01100100 _ _ _ _ _ 000 00000000
11111111 11111111 1 1 1 1 1 000 00000000

perhatikan oktet ketiga
_ _ _ _ _ 000
1 1 1 1 1 000

Cara 1
Dengan mengkombinasikan bit

00001 000 = 8
00010 000 = 16
00011 000 = 24
00100 000 = 32
00101 000 = 40
00110 000 = 48
...............
11111 000 = 248

Cara 2
Mengurangi subnet mask dgn bilangan 256

11111 000 = 248

256 – 248 = 8 maka subnetwork adalah kelipatan 8

No Depertemen Subnetwork (255.255.248.0)
1 Pertama 160.100.8.0
2 Kedua 160.100.16.0
3 Ketiga 160.100.24.0
4 Keempat 160.100.32.0
5 Kelima 160.100.40.0
6 Keenam 160.100.48.0
7 Ketujuh 160.100.56.0
.. .............
30 Ketigapuluh 160.100.248.0
Maka

Network Broadcast Range-Hoat
160.100.8.0 160.100.15.255 160.100.8.1 - 160.100.15.254
160.100.16.0 160.100.23.255 160.100.16.1 - 160.100.23.254
160.100.24.0 160.100.31.255 160.100.24.1 - 160.100.31.254
160.100.32.0 160.100.39.255 160.100.32.1 - 160.100.39.254
160.100.40.0 160.100.47.255 160.100.40.1 - 160.100.47.254
160.100.48.0 160.100.55.255 160.100.48.1 - 160.100.55.254
160.100.56.0 160.100.63.255 160.100.56.1 - 160.100.63.254
160.100.64.0 160.100.71.255 160.100.64.1 - 160.100.71.254
160.100.72.0 160.100.79.255 160.100.72.1 - 160.100.79.254
........ .......... .............
160.100.248.0 160.100.255.255 160.100.248.1 - 160.100.255.254

Artikel by: Gindo Ariefman
Note: Penulis adalah Asisten CNAP (Cisco Networking Academy Program) di Lab Komp Fisika UI, Jika ada pertanyaan silahkan dapat menghubungi beliau, thx :-)