Archive

Category Archives for "Networking"

Episode 13 – A Look In The Mirror

In episode 13, the Network Collective hosts go it alone and take an introspective look at the engineering community, warts and all. We dig into topics relating to ego, hero mentality, overconfidence, short memories, and the negative side of the hype cycle.

 


Jordan Martin
Co-Host
Eyvonne Sharp
Co-Host
Phil Gervasi
Co-Host

Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/

The post Episode 13 – A Look In The Mirror appeared first on Network Collective.

Episode 13 – A Look In The Mirror

In episode 13, the Network Collective hosts go it alone and take an introspective look at the engineering community, warts and all. We dig into topics relating to ego, hero mentality, overconfidence, short memories, and the negative side of the hype cycle.

 


Jordan Martin
Co-Host
Eyvonne Sharp
Co-Host
Phil Gervasi
Co-Host

Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/

The post Episode 13 – A Look In The Mirror appeared first on Network Collective.

Optical-to-acoustic microchip could boost data-center efficiency

Optical data can be too fast for its own good. While the speeds obtained are great for carrying information over distances and into chips, when the light-carried data lands there it’s often moving too fast to be thoroughly processed and analyzed. Data can need slowing down for intense number-crunching and routing.Solutions to this apparent dichotomy have been attempted. They include the obvious one — speeding up microprocessors themselves. However, there’s a problem with that: Faster chips using electronics create more heat, generate interference and use more energy. All bad for data centers.Using sound waves to speed up networks Scientists say sound waves, though, could present a solution. They say one should convert the light zooming into the chip to sound — creating a kind of acoustic buffer (sound waves travel slower than light waves) — then process the data and turn it back into zippy light again, to be sent on its way.To read this article in full or to leave a comment, please click here

Faster networks may come from optics converted to sound

Optical data can be too fast for its own good. While the speeds obtained are great for carrying information over distances and into chips, when the light-carried data lands there it’s often moving too fast to be thoroughly processed and analyzed. Data can need slowing down for intense number-crunching and routing.Solutions to this apparent dichotomy have been attempted. They include the obvious one — speeding up microprocessors themselves. However, there’s a problem with that: Faster chips using electronics create more heat, generate interference and use more energy. All bad for data centers.Using sound waves to speed up networks Scientists say sound waves, though, could present a solution. They say one should convert the light zooming into the chip to sound — creating a kind of acoustic buffer (sound waves travel slower than light waves) — then processes the data and turn it back into zippy light again, to be sent on its way.To read this article in full or to leave a comment, please click here

Optical-to-acoustic microchip could boost data-center efficiency

Optical data can be too fast for its own good. While the speeds obtained are great for carrying information over distances and into chips, when the light-carried data lands there it’s often moving too fast to be thoroughly processed and analyzed. Data can need slowing down for intense number-crunching and routing.Solutions to this apparent dichotomy have been attempted. They include the obvious one — speeding up microprocessors themselves. However, there’s a problem with that: Faster chips using electronics create more heat, generate interference and use more energy. All bad for data centers.Using sound waves to speed up networks Scientists say sound waves, though, could present a solution. They say one should convert the light zooming into the chip to sound — creating a kind of acoustic buffer (sound waves travel slower than light waves) — then process the data and turn it back into zippy light again, to be sent on its way.To read this article in full or to leave a comment, please click here

Not Your Mama’s Security Architecture (Thwack)

It puts a firewall at the edge of the network or it gets the hose again. Think that’s still how security works? I don’t think so, my friend.

On the Solarwinds Thwack Geek Speak blog I look at how security architectures have changed from when our Mama used to create them, and I even take a moment to mention Greg Ferro (because, well, why not). Please do take a trip to Thwack and check out my post, “Not Your Mama’s Security Architecture“.

Not Your Mama's Security Architecture

 

Please see my Disclosures page for more information about my role as a Solarwinds Ambassador.

If you liked this post, please do click through to the source at Not Your Mama’s Security Architecture (Thwack) and give me a share/like. Thank you!

DNS OARC 27

The DNS OARC meetings are an instance of a meeting that concentrates on the single topic of the DNS, and in this case it delves as deep as anyone is prepared to go! It's two days where too much DNS is barely enough!

IDG Contributor Network: Is U.S. business ready for a 5G rollout?

America’s insatiable appetite for snazzy new gadgets and the powerful networks required to run them seems ever growing. It’s only natural, then, that demand for a 5G network capable of keeping pace with tomorrow’s dizzying innovations grows, too. So how prepared is the U.S. for a 5G rollout, and what steps are today's top companies taking now to profit from the network of the future?A brief look into the early plans for a nationwide adoption of 5G shows just how much is on the plate when it comes to delivering the next generation of wireless networks. All is not lost, however; handled skillfully, the US can successfully redefine wireless network infrastructure like it has so many times before.To read this article in full or to leave a comment, please click here

Former Intel CEO Paul Otellini remembered

Former Intel CEO Paul Otellini died in his sleep on Monday at the age of 66. His tenure was marked by a significant comeback for the company, dealing with a number of business and technological issues, making the company a massive player in the data center but a fumbled opportunity for the mobile market. Unlike his predecessors, Otellini was not an engineer but had a MBA from the University of California, Berkeley. He joined Intel in 1974 right out of Berkeley and spent his entire career at Intel, eventually becoming chief operating officer in 2002 and CEO in 2005, a position he held until his retirement in 2012. "We are deeply saddened by Paul’s passing,” CEO Brian Krzanich said in a statement. “He was the relentless voice of the customer in a sea of engineers, and he taught us that we only win when we put the customer first." To read this article in full or to leave a comment, please click here

Former Intel CEO Paul Otellini remembered

Former Intel CEO Paul Otellini died in his sleep on Monday at the age of 66. His tenure was marked by a significant comeback for the company, dealing with a number of business and technological issues, making the company a massive player in the data center but a fumbled opportunity for the mobile market. Unlike his predecessors, Otellini was not an engineer but had a MBA from the University of California, Berkeley. He joined Intel in 1974 right out of Berkeley and spent his entire career at Intel, eventually becoming chief operating officer in 2002 and CEO in 2005, a position he held until his retirement in 2012. "We are deeply saddened by Paul’s passing,” CEO Brian Krzanich said in a statement. “He was the relentless voice of the customer in a sea of engineers, and he taught us that we only win when we put the customer first." To read this article in full or to leave a comment, please click here

CCDE Practical Exam Dates 2018

Below is the CCDE Practical/Lab exam dates for 2018.   As you might know there are four exam yearly. You can attend maximum four times. You don’t have to pass any exam other than CCDE Written Qualification exam to be able to attend CCDE Practical/Lab exam.   For the cost, registration process , refund and […]

The post CCDE Practical Exam Dates 2018 appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.

Server downtime is bad. Server slowness is worse

I've worked at my fair share of large corporations in my life, and like most of you, I've experienced more network and server outages than I can shake a stick at. Sometimes these outages are small and only mildly disruptive (a file server going down for a few minutes). Other times, an outage can cause massive, widespread work stoppages (such as when an email server goes offline for multiple hours — or days). These outages are, at least for the company, bad things. If your employees can no longer communicate, work all but grinds to a halt. One hour of total downtime multiplied by the average hourly pay of your employees can equal a pretty big amount of lost moolah.To read this article in full or to leave a comment, please click here

Server downtime is bad. Server slowness is worse

I've worked at my fair share of large corporations in my life, and like most of you, I've experienced more network and server outages than I can shake a stick at. Sometimes these outages are small and only mildly disruptive (a file server going down for a few minutes). Other times, an outage can cause massive, widespread work stoppages (such as when an email server goes offline for multiple hours — or days). These outages are, at least for the company, bad things. If your employees can no longer communicate, work all but grinds to a halt. One hour of total downtime multiplied by the average hourly pay of your employees can equal a pretty big amount of lost moolah.To read this article in full or to leave a comment, please click here

Introduction to PAT- Port Address Translation


Today I am going to talk about PAT- Port Address Translation or so called as NAT overloading. Before we start with the PAT, please check the facts of NAT in the below mentioned link which i explained earlier.

NAT- Network Address Translation 

Well with the above mentioned article link, let me brief you about the NAT is short bullet points
  • Enables intra-networks that use private IP addresses to connect to the Internet by translating the address to a globally registered IP address.
  • Stores mapping of local to global address in NAT table
  • Increases network security by hiding internal IP addresses
  • Typically operates at the border of a stub network (single connection to neighbor network)
  • Private inside addresses = inside local
  • Public addresses = inside global
Now let's talk about the PAT- Port Address Translation, below are the points about PAT
  • NAT configured to advertise only one address for the entire internal network to the outside world “static PAT” or “address overloading” or “many-to-one”
  • Appends a unique source port number to each translation to outside IP address
  • Total number available internal addresses per 1 outside address is 65,536 ports
  • Attempts to assign first available port number, if already allocated assigns Continue reading

Reducing the Number of Transported Routes

One of my friends sent me this design challenge:

Assume you’re migrating from another WAN transport technology to MPLS. The existing network has 3000 routes but the MPLS carrier is limiting you to 1000 routes. How could you solve this with MPLS?

Personally, I think MPLS is a red herring.

A better question would be “how do you reduce the number of routes transported across your WAN network” or “how do you reduce the routing interaction with your MPLS service providers” (particularly intriguing if you use more than one of them).

As always, there are several options and it’s impossible to recommend the best one:

  • Readdressing is usually out of question (or at least too messy to try). It might also break numerous firewall rules and other hard-coded stuff… unless you automated everything, but then it wouldn’t be hard to readdress, would it?
  • The usual answer would be to summarize the routes. The usual challenge is that you might not be able to do it (because random addressing). Furthermore, summarization is a lossy compression, and loss of forwarding information might result in black holes.
  • RFC 1925 states that there’s nothing that cannot be solved with another layer Continue reading