IT Certification CCIE,CCNP,CCIP,CCNA,CCSP,Cisco Network Optimization and Security Tips
IBM, Cisco help networks help themselves
Pinpointing the causes of failures and solving the root problems takes up a lot of IT staff time, a resource that has become more scarce as budgets tighten, according to the companies, which announced a drive toward self-diagnostic and self-healing networks on Friday. The combination of networks and systems is also becoming more complex, so simplifying and automating that process is increasingly important, they said.
Self-diagnosis and self-healing are key parts of IBM's broader autonomic computing initiative, aimed at creating systems and networks that in many respects run themselves, said Ric Telford, director of architecture and technology in the autonomic computing business of Armonk, New York-based IBM. Companies can never remove the human administrator from the picture completely, but Cisco and IBM's steps should make life easier even when people have to get involved, he said.
For example, if a transaction goes wrong, the cause might lie in any one of many applications or devices that come into play across the infrastructure, Telford said. Narrowing it down can be hard.
"The growing complexity of infrastructure is causing more and more of these hard-to-diagnose problems," he said.
Initial aims of IBM's and Cisco's program include coming up with a common way for parts of the system to log events and providing software for an administrator to see and analyze problems. The two companies plan to offer these and other technologies over time, but they also are making all the technology available openly to other players and will seek to have it adopted by industry standards bodies, Telford said.
Between technical and political disagreements, it's unlikely all vendors will sign on with the two vendors' approach, but even having coordination among some systems should save IS departments time and money, said Amy Wohl, an industry analyst at Wohl Associates, in Narberth, Pennsylvania.
"It's unrealistic to think that anything new is going to cover every single thing," Wohl said.
The IBM-developed Common Base Event (CBE) specification defines a standard format for event logs, which devices and software use to keep track of transactions and other activity.
All the components of systems typically have different formats for the information they collect about events, Telford said. For example, if an IS team needs to figure out where something went wrong with an e-business application, they may need to understand 40 different event log formats, he said. Root cause analysis of the problem could require several different administrators -- database, network and so on -- getting involved.
As a common format, CBE can simplify that process, Telford said. Future products should use CBE as their native log format, but "log adapters" can define mappings between current proprietary log formats and CBE, he said. IBM now has a team of about 24 engineers developing log adapters for core IBM products, including hardware, software and storage products, according to the company.
In August, IBM proposed CBE as a standard to the Organization for the Advancement of Structured Information Standards (OASIS), Telford said.
Another piece of the puzzle is a log and trace analyzer, a visual tool for administrators to study log files in various views. IBM has already made a log and trace analyzer available in its WebSphere Studio application development platform, where developers can use it to work out problems before a product is deployed. For IS administrators using production versions of software, IBM probably will ship a log and trace analyzer as part of its Tivoli system management software, at an undetermined future date, Telford said.
Other things that could be standardized include correlation mechanisms -- ways of associating events with one another -- and filters for sifting out the events that are relevant, Telford said. Depending on who at IBM, Cisco or other companies develops methods of doing that, such methods could be proposed to OASIS or another standards body for approval, he said.
In the second phase of the initiative, San Jose, California-based Cisco will integrate the technologies into its products. The hope is to be able to correlate events in a router with those in middleware, for example.
With large networks involved, one challenge that lies ahead is collecting and working with event data even if one company doesn't control the whole network or the whole transaction, Telford said.
The kinds of capabilities IBM and Cisco are pushing are likely to become pervasive, but there are sure to be competitive offerings, analyst Wohl said. Hewlett-Packard Co. and Sun Microsystems Inc. already offer some software that does things similar to IBM's autonomic computing concept. And as is typical, political battles may loom on the path to industry standards, she said.
However, Wohl sees such technology ultimately benefiting most users, consumer as well as enterprise. Any place with a stretched IS staff or none at all should welcome the idea of a system fixing itself, she said.
Self-diagnosis and self-healing are key parts of IBM's broader autonomic computing initiative, aimed at creating systems and networks that in many respects run themselves, said Ric Telford, director of architecture and technology in the autonomic computing business of Armonk, New York-based IBM. Companies can never remove the human administrator from the picture completely, but Cisco and IBM's steps should make life easier even when people have to get involved, he said.
For example, if a transaction goes wrong, the cause might lie in any one of many applications or devices that come into play across the infrastructure, Telford said. Narrowing it down can be hard.
"The growing complexity of infrastructure is causing more and more of these hard-to-diagnose problems," he said.
Initial aims of IBM's and Cisco's program include coming up with a common way for parts of the system to log events and providing software for an administrator to see and analyze problems. The two companies plan to offer these and other technologies over time, but they also are making all the technology available openly to other players and will seek to have it adopted by industry standards bodies, Telford said.
Between technical and political disagreements, it's unlikely all vendors will sign on with the two vendors' approach, but even having coordination among some systems should save IS departments time and money, said Amy Wohl, an industry analyst at Wohl Associates, in Narberth, Pennsylvania.
"It's unrealistic to think that anything new is going to cover every single thing," Wohl said.
The IBM-developed Common Base Event (CBE) specification defines a standard format for event logs, which devices and software use to keep track of transactions and other activity.
All the components of systems typically have different formats for the information they collect about events, Telford said. For example, if an IS team needs to figure out where something went wrong with an e-business application, they may need to understand 40 different event log formats, he said. Root cause analysis of the problem could require several different administrators -- database, network and so on -- getting involved.
As a common format, CBE can simplify that process, Telford said. Future products should use CBE as their native log format, but "log adapters" can define mappings between current proprietary log formats and CBE, he said. IBM now has a team of about 24 engineers developing log adapters for core IBM products, including hardware, software and storage products, according to the company.
In August, IBM proposed CBE as a standard to the Organization for the Advancement of Structured Information Standards (OASIS), Telford said.
Another piece of the puzzle is a log and trace analyzer, a visual tool for administrators to study log files in various views. IBM has already made a log and trace analyzer available in its WebSphere Studio application development platform, where developers can use it to work out problems before a product is deployed. For IS administrators using production versions of software, IBM probably will ship a log and trace analyzer as part of its Tivoli system management software, at an undetermined future date, Telford said.
Other things that could be standardized include correlation mechanisms -- ways of associating events with one another -- and filters for sifting out the events that are relevant, Telford said. Depending on who at IBM, Cisco or other companies develops methods of doing that, such methods could be proposed to OASIS or another standards body for approval, he said.
In the second phase of the initiative, San Jose, California-based Cisco will integrate the technologies into its products. The hope is to be able to correlate events in a router with those in middleware, for example.
With large networks involved, one challenge that lies ahead is collecting and working with event data even if one company doesn't control the whole network or the whole transaction, Telford said.
The kinds of capabilities IBM and Cisco are pushing are likely to become pervasive, but there are sure to be competitive offerings, analyst Wohl said. Hewlett-Packard Co. and Sun Microsystems Inc. already offer some software that does things similar to IBM's autonomic computing concept. And as is typical, political battles may loom on the path to industry standards, she said.
However, Wohl sees such technology ultimately benefiting most users, consumer as well as enterprise. Any place with a stretched IS staff or none at all should welcome the idea of a system fixing itself, she said.
cisco, network, network securty
daha iyi hizmet verebilmek için asrastirma calismalar devam etmektedir. cisco, network, network securty
Data Encryption Standard (DES)
Data Encryption Standard (DES)
Data Encryption Standard (DES) is an encryption method that uses a secret key. It is
so hard to break (it provides 72 quadrillion possible keys) that the U.S. government
forbids its exportation to other countries. It is tough to break because the key is
randomly chosen from an enormous pool.
DES applies a 56-bit key to each 64-bit block of data. This is considered strong
encryption. Of course strong is a relative term, and if someone is really determined and
has the resources, it is possible to crack DES. Many organizations employ triple DES,
which applies three keys in succession.
Advanced Encryption Standard (AES)
Advanced Encryption Standard (AES) is poised to become the de facto encryption
standard. AES applies 128-, 192-, or 256-bit keys to 128-, 192-, or 256-bit blocks of
data.
As of 2004, there had been no reported cracks of AES, and it is the first time that the
U.S. Government’s National Security Agency (NSA) authorized an encryption tool for
transmission of top-secret, classified information.
Other Resources
• University of California, Berkeley Internet Security, Applications,
Authentication and Cryptography (ISAAC) Report on WEP insecurity
http://www.isaac.cs.berkeley.edu/isaac/wep-faq.html
• Wi-Fi Alliance
http://www.wi-fi.org/
• National Institute of Standards and Technology
http://www.nist.gov
Data Encryption Standard (DES) is an encryption method that uses a secret key. It is
so hard to break (it provides 72 quadrillion possible keys) that the U.S. government
forbids its exportation to other countries. It is tough to break because the key is
randomly chosen from an enormous pool.
DES applies a 56-bit key to each 64-bit block of data. This is considered strong
encryption. Of course strong is a relative term, and if someone is really determined and
has the resources, it is possible to crack DES. Many organizations employ triple DES,
which applies three keys in succession.
Advanced Encryption Standard (AES)
Advanced Encryption Standard (AES) is poised to become the de facto encryption
standard. AES applies 128-, 192-, or 256-bit keys to 128-, 192-, or 256-bit blocks of
data.
As of 2004, there had been no reported cracks of AES, and it is the first time that the
U.S. Government’s National Security Agency (NSA) authorized an encryption tool for
transmission of top-secret, classified information.
Other Resources
• University of California, Berkeley Internet Security, Applications,
Authentication and Cryptography (ISAAC) Report on WEP insecurity
http://www.isaac.cs.berkeley.edu/isaac/wep-faq.html
• Wi-Fi Alliance
http://www.wi-fi.org/
• National Institute of Standards and Technology
http://www.nist.gov
WPA2
WPA2
As you might deduce from its name, WPA2 is the second and latest version of WPA.
The most important difference between the two is the method of encryption. WPA uses
RC4, whereas WPA2 uses AES. Not only is the AES encryption method much stronger,
it is also a requirement for some government and industry users.
WPA2 is backward compatible with WPA, and many WPA-certified products can be
upgraded with software to WPA2. However, some products might require hardware
upgrades. WPA was designed to be a software upgrade to WEP. However, WPA2 didn’t
have such a design goal. As such, in many cases a hardware upgrade will be necessary
to update to WPA2.
Other Resources 79
Encryption
Scrambling a WLAN’s data as it leaves the AP, and then unscrambling it when it arrives
at the client, requires an encryption method. The popular RC4 has already been
discussed, but sturdier, stronger encryption methods are out there and in use in WLAN
systems, as described next.
As you might deduce from its name, WPA2 is the second and latest version of WPA.
The most important difference between the two is the method of encryption. WPA uses
RC4, whereas WPA2 uses AES. Not only is the AES encryption method much stronger,
it is also a requirement for some government and industry users.
WPA2 is backward compatible with WPA, and many WPA-certified products can be
upgraded with software to WPA2. However, some products might require hardware
upgrades. WPA was designed to be a software upgrade to WEP. However, WPA2 didn’t
have such a design goal. As such, in many cases a hardware upgrade will be necessary
to update to WPA2.
Other Resources 79
Encryption
Scrambling a WLAN’s data as it leaves the AP, and then unscrambling it when it arrives
at the client, requires an encryption method. The popular RC4 has already been
discussed, but sturdier, stronger encryption methods are out there and in use in WLAN
systems, as described next.
Subscribe to:
Posts (Atom)