1. Juniper Networks Enterprise Routing Certification Track

Là hệ thống chứng chỉ về Routing. Có 3 cấp độ: JNCIA (tương đương CCNA), JNCIS (tương đương CCNP) và JNCIE (tương đương CCIE).

Thông tin về các môn thi:

2. Enterprise Switching Certification Track

Thông tin môn thi:

Alice, Arabella, Bedelia, Clementine, Clover, Cordelia, Daisy, Esme, Eleanor, Flora, Fern, Hazel, Hannah, Imogen, Ida, Iris, Josephine, Jemima, Juniper, Lucinda, Madeleine, Margaret, Nola, Olive, Poppy, Pippa, Polly, Penelope, Primrose, Rose, Sally, Stella, Shiloh, Matilda, Tallulah, Theodora, Thomasina, Violet, Zipporah, Amelia, Annora, Maude, Clara.

Arthur, Bertram, Bartholomew, Baxter, Bruno, Bramwell, Chester, Cassius, Cato, Dexter, Dominic, Emerson, Emmett, Elliot, Fergus, Felix, Gregor, Gulliver, Isidore, Jasper, Ned, Orlando, Quentin, Rupert, Rafferty, Samson, Toby, Thomas, Theodore.

Thoughts? Suggestions?

It’s so beautiful, I can barely concentrate on walking. I only want to smell juniper berries.

—Finn Trommer, 5 years old

The day was not finished, not quite—

still walking the old mining road toward tonight—

when a boy in the forest inhales juniper,

grabs his mother’s hand and dances her

close to the boughs—how she beams and

O, breaks with his joy. How lightly she holds

his gloved hand. She inhales, blue pungency,

constellations of berries, swathes of feathery evergreen.

And inside her, the rupture, the rapture, the place

where she held him so long, so short.

Some part of her wants to fold him so small

she could slip him back into her core—that close!

And another part leans toward his brightening voice.

Her flesh, but not hers. His wonder,

her wonder, they twine in the dim. She is missing,

what, nothing. Still the smooth stone of loss.

There is more. She is rift. She stows berries and boughs

in the deepening hole where he was.

It must feel a bit like being in the movie Groundhog Day over at Cisco as they continue to face increasing competition from both large and small challengers.  However, unlike the past, consolidation and the rise of the next generation datacenter (Cloud Computing) has dramatically raised the stakes.  Cisco cannot simply use their superior channel, army of certified engineers and sales people, partnerships, and market power to eliminate or marginalize the competition.  Further complicating matters is the delicate balance between companies that both cooperate and compete within the same market.

As Cisco marches forward with their Unified Computing strategy, they’ll need more than organic development and growth to unseat the likes of HP, IBM, Dell, and Sun.  I was highly disappointed with Cisco’s UCS B-Series Blade Servers as they weren’t as innovative or as tied into the Nexus products as I had hoped.  To that end, it is time for Cisco to shake up the server market with an acquisition (or two) of their own.

One such acquisition target is Liquid Computing headquartered in Ottawa, Ontario, Canada.  Liquid Computing has built a unified computing system called LiquidIQ that is made up of both hardware and software.  From a hardware perspective, Liquid Computing is innovative, dense, and creates a “datacenter in a rack”.  From a software perspective, Liquid Computing has created a central point for management with their LiquidView software including server, storage, and network configuration and management. 

With one brush of Cisco’s checkbook, they would instantly change the game and rock the IT industry.  An acquisition of Liquid Computing could be as important to Cisco as it was when they purchased Kalpana in 1994.  While Liquid Computing has been branded a “Visionary” in Gartner’s 2009 Magic Quadrant, an acquisition by Cisco would certainly elevate them into the Magic Quadrant (Upper Right-Hand Corner).

Imagine re-branding and integrating Liquid Computing with Cisco’s Nexus and Unified Computing product lines.  Virtually overnight, this new solution based on Liquid Computing would be injected into the Cisco machine and made available to customers worldwide.  Over time, Cisco would strengthen Liquid Computing’s ties to EMC and VMware, while injecting more and more core Nexus technology into the solution.

Cisco is on the cusp of not only redefining themselves but also an entire industry.  To complete this transformation, Cisco must bold and move out of their comfort zone.  The game has definitely changed as Cisco’s greatest competitive threats do not necessarily come from classic networking providers or start-ups such as Juniper, Brocade, or Riverbed; instead, it comes from the likes of HP, IBM, Dell, Huawei, and more. 

Instead of simply watching HP buy 3Com, Dell and IBM OEM Juniper equipment, Oracle buying Sun, and awaiting Huawei’s entrance into the U.S Market (possibly with the purchase of Motorola), Cisco must launch an offensive on the server vendors via a visionary acquisition. 

Could this visionary acquisition be Liquid Computing?  Perhaps Groundhog Day may be coming to an end.

Unlike ScreenOS, adding EX-Switch running JUNOS procedure is different.

Following steps I took to successfully add the switches:

Before you can add a JUNOS device to NSM, the device must be installed and configured, and logon credentials for an NSM administrator must be configured for it. Perform the following steps:

1. Connect the device to the network and configure one of the interfaces so that the device can reach the NSM device server.
2. Add a user for NSM that has full administrative rights.

For complete details on installing and configuring JUNOS devices, see the
documentation for the specific device,

Add the Device in NSM
To add the device in the NSM UI, follow these steps:
1. From the domain menu, select the domain in which you want to import the device.
2. In Device Manager, select Devices.
3. Click the Add icon and select Device to open the Add Device wizard.
4. Select Device Is Not Reachable, and then click Next.
5. On the Specify Name, Color, OS Name, Version, and Platform screen:
¦ Enter a name and select a color to represent the device in the UI.
¦ From the OS Name list, select JUNOS.

The JUNOS OS Type list appears.
¦ Select the JUNOS OS type for the device you want to add:
¦ To add a J-series or SRX-series device, select J-series from the list.
¦ To add an EX-series device or virtual chassis, select EX-series.
¦ To add an M-series or MX-series device, select M/MX-series.
¦ From the Platform list, select the device platform name.
¦ Check the Virtual Chassis box if you are adding an EX-series virtual chassis made up of several EX-series switches (EX-4200 series only).
¦ From the Managed OS Version list, select the version of the operating system that runs on the device.

set system services outbound-ssh client nsm device-id F79821 (auto-generated)
set system services outbound-ssh client nsm secret
set system services outbound-ssh client nsm 10x.xxx.xxx.xxx port 7804
set system services outbound-ssh client nsm services netconf
commit

The device will immediately attempt to connect to NSM.

I wrote about Juniper about six months ago, and her incredible story of surviving 9 months of intense neglect.

Her story is sad and powerful, and her crooked legs make us all feel powerless, I think. She doesn’t have much interest in human interaction, which is understandable, and yet she’s not afraid of us either. So, if you have come armed with bribes, like carrots, you have a chance at some incredibly precious interaction. I captured a very short video of this last weekend.

You can see her sweet face, you can see how gentle she is when she takes the carrots, and you can see that she’s balancing on the tip-toes of her front hooves. That is, indeed, as straight as her legs will go. And you can see that she does not appear to feel any pain. It is what it is, and she’s got shelter, food, and water, as well as the company of some of the less rowdy goats, so she’s happy about life, all in all.

This resilience amazes me. And it’s the common story when it comes to abused and neglected animals who find their way to the sanctuary. That amazes me most of all.

They need so little from us, when all is said and done. Mostly they just need us to not hurt them.

A tip of the cap to the management and M&A teams at HP, as they continue to acquire the necessary pieces to challenge Cisco’s core business.  With HP’s acquisition of 3Com for $2.7 billion, HP has gained a portfolio of modern architected networking products that span switching, routing, and network security.  Additionally, HP expanded access to overseas markets, including the ever expanding market in China, through 3Com’s H3C unit. 

While some will laugh at the reach and capabilities of 3Com, HP understands that 3Com’s products are solid, modern, and good-enough when put under the HP ProCurve brand and backed by the power of HP and their Services Division.  Furthermore, while Cisco continues to date the likes of EMC and VMware, HP is in full control of their destiny.  They have built a strong portfolio that spans storage, servers, virtualization, networking, security, applications, and management.

While Cisco isn’t going to be losing any sleep over this acquisition, they will take note of how aggressive HP is going to be to not only defend their own turf but also to expand into Cisco’s bread and butter.  However, IBM, Juniper, Brocade, and Dell may be tossing and turning tonight as they contemplate the future.  If IBM continues to wait to purchase the necessary pieces to compete with HP and Cisco, their choices will be limited.  If Dell does not shore up their portfolio, then they face the reality of falling further behind and severely limiting their growth potential.  Finally, both Juniper and Brocade must weigh the possibility that organic growth may not be possible as we are nearing a major inflection point for all of IT.

One quick note, don’t underestimate Huawei or ZTE as they are both hungry and flush with cash.  Additionally, Oracle remains a wildcard as they may jump into this race.

Updated: HP (s hpq) said today that it plans to buy router and switching gear maker 3Com (s coms) for $2.7 billion — a deal that seeks to put HP on better competitive footing against Cisco (s csco) and its server efforts. HP and the rest of the computing industry have struggled to come up with an answer to what Cisco calls unified computing systems, which combine servers and networking into one box, and in doing so have tended to lean on partnerships with networking providers such as Brocade (s brcd) and Juniper (s jnpr).

With its No. 2 line of Pro Curve networking gear, HP  was seen by the industry as being in the best position to compete, so this deal looks like an admission from HP that it has some holes in its networking portfolio that Cisco could exploit.  The boards of both companies have approved the deal. HP will pay $7.90 per share in cash for 3Com. My question is: Why didn’t it buy Brocade?

Update: Cisco has posted a comment in response to the deal, basically saying that HP is welcome to follow its industry leadership in unified computing.

Update2: Dan Primack over at peHUB has raised some legitimate questions about the price HP paid, and noted how 3Com’s stock has been steadily rising in the last couple of weeks. He pulled some Bloomberg data that shows how trading volume shot up today before the deal was announced, leading him and other blogs to suspect insider trading may be at work.

As for today one of the most complicated tasks for a person is a problem of searching of specific information. As for me as a technical engineer working with network equipment of such vendors as Cisco and Juniper, it had been a problem too.

It seems to me that today I was able to find all the whitepapers on the site juniper.net. It was possible due to order of document placement on this site. On the cisco.com on contemporary, there is a complete mess of whitepapers – you can find them in all parts of the side.

In order to find all of them, you can use google search – simple things are really the best things

Just try to search the following: filetype:pdf site:http://www.juniper.net/solutions/literature/white_papers/
and you’ll be surprised what you find

Juniper berries and venison are a match made in heaven and are well seeking out.

Buttery mashed potatoes, parsnip game chips, carrots and gravy

Serves 4 people

Note
Discard the parsley stalks, celery leaves, peppercorns and juniper berries before serving.

Cisco has unveiled their latest Unified Communications/Cloud Computing move by strengthening their relationship with VMware to develop new products and forming a new Joint Venture, Arcadia, with EMC, VMware, and Intel. In-other-words, Cisco is on a giant group date.

 Cisco has been dating EMC for many years as they resell EMC’s storage gear. In fact, Cisco purchased EMC some nice lake front property when they invested, and bet, heavily on VMware. Yesterday, Cisco and EMC decided to move-in-together by forming Arcadia. Meanwhile, Intel has decided to play chaperone for a while and make sure these two giants play nice.

Let’s face it; for Cisco to match/defend against rival HP’s one-stop-shop strategy they need to unravel the delicate cooperation/competition agreements with the likes of HP, IBM, and more. While HP has a formidable portfolio of hardware and software, Dell and IBM have beefed up agreements with the likes of Brocade and Juniper. Juniper may be in the enviable position of being courted by multiple companies but eventually they’ll have to tie-the-knot.

 The combination of Cisco and EMC would send shockwaves across the IT industry. Cisco would gain instant access and credibility to the storage, virtualization, and management worlds. However, the aftershocks would be just as powerful as HP, Dell, and IBM would surely take forceful and definitive actions.

What would you pay to be a fly-in-the-wall of a conference room with Chambers and Tucci? Or, better yet, to be in Ellison’s office when he read the news of the merger? Clearly, Oracle is becoming a wild card within the IT industry and they could really mess things up by acquiring BMC, Brocade, or even Juniper.

While JV’s, partnerships, and investments are cute, it’s time for a more serious relationship. Cisco needs to take advantage of this moment, pull out that ring in the safe, get down one knee, and ask EMC for its hand in marriage. In that moment the world would be holding its breath…yes or no.

“The NetScreen Redundancy Protocol (NSRP) is a proprietary protocol originally developed by NetScreen Technologies Inc. The goal of NSRP is to ensure that the firewall and virtual private network (VPN) services are available at all times. There are three primary components of NSRP: gateway failover, session synchronization, and failure detection. The first component is relatively straightforward. Much like the Internet Engineering Task Force (IETF) standard protocol, the Virtual Router Redundancy Protocol (VRRP), NSRP provides a virtual Media Access Control (MAC) address and IP address to the network so that hosts and routers can point statically to a gateway IP. In NSRP terms, a virtual interface is known as a Virtual Security Interface (VSI). When a failure condition is detected, the MAC/IP pair for each interface is “migrated” from one device to the other via the use of gratuitous Address Resolution Protocol (ARP) messages. These ARP messages update the switch’s forwarding database so that traffic destined to the virtual MAC is forwarded to the port to which the new “master” is connected. From the network’s point of view, VRRP and NSRP in most cases use identical mechanisms to signal failover to the rest of the network. At this point, the similarities between the two protocols disappear.” ScreenOS Cookbook

Well following steps will help to change ownership between Primary and backup firewalls running on High-availability mode.

Basic Active/Passive Firewall Configuration:
=========Primary=============================
set interface “ethernetx/x” zone “HA”
set nsrp cluster id 1
set nsrp cluster name NAME-of-Cluster
set nsrp rto-mirror sync
set nsrp vsd-group id 0 priority 50
set nsrp vsd-group id 0 preempt
set nsrp vsd-group id 0 preempt hold-down 10
=============================================
========Secondary============================
set nsrp cluster id 1
set nsrp cluster name NAME-of-Cluster
set nsrp vsd-group id 0 priority 100
=============================================

Once both devices are sync’d then we proceed to following command on Primary firewall to take the role as backup and Backup firewall as Master:

set nsrp vsd-group id 0 priority 120
exec nsrp vsd-group id 0 mode backup

After we intiate the command the primary box will be backup and vice versa. To revert back we only need to lower the priority of old Primary box i.e. from 120 to 50 and after couple of seconds the old box will resume mastership of the cluster.

“The NetScreen Redundancy Protocol (NSRP) is a proprietary protocol originally developed by NetScreen Technologies Inc. The goal of NSRP is to ensure that the firewall and virtual private network (VPN) services are available at all times. There are three primary components of NSRP: gateway failover, session synchronization, and failure detection. The first component is relatively straightforward. Much like the Internet Engineering Task Force (IETF) standard protocol, the Virtual Router Redundancy Protocol (VRRP), NSRP provides a virtual Media Access Control (MAC) address and IP address to the network so that hosts and routers can point statically to a gateway IP. In NSRP terms, a virtual interface is known as a Virtual Security Interface (VSI). When a failure condition is detected, the MAC/IP pair for each interface is “migrated” from one device to the other via the use of gratuitous Address Resolution Protocol (ARP) messages. These ARP messages update the switch’s forwarding database so that traffic destined to the virtual MAC is forwarded to the port to which the new “master” is connected. From the network’s point of view, VRRP and NSRP in most cases use identical mechanisms to signal failover to the rest of the network. At this point, the similarities between the two protocols disappear.” ScreenOS Cookbook

Well following steps will help to change ownership between Primary and backup firewalls running on High-availability mode.

Basic Active/Passive Firewall Configuration:
=========Primary=============================
set interface “ethernetx/x” zone “HA”
set nsrp cluster id 1
set nsrp cluster name NAME-of-Cluster
set nsrp rto-mirror sync
set nsrp vsd-group id 0 priority 50
set nsrp vsd-group id 0 preempt
set nsrp vsd-group id 0 preempt hold-down 10
=============================================
========Secondary============================
set nsrp cluster id 1
set nsrp cluster name NAME-of-Cluster
set nsrp vsd-group id 0 priority 100
=============================================

Once both devices are sync’d then we proceed to following command on Primary firewall to take the role as backup and Backup firewall as Master:

set nsrp vsd-group id 0 priority 120
exec nsrp vsd-group id 0 mode backup

After we intiate the command the primary box will be backup and vice versa. To revert back we only need to lower the priority of old Primary box i.e. from 120 to 50 and after couple of seconds the old box will resume mastership of the cluster.

The front yard landscaping is complete! I am really happy with the turnout. Daryle thinks it is too sparse, but I love the “white space” (mulch) that separates each plant. Slowly, all of the plants will sprawl out while remaining low to the ground. Instead of using lava rock as decoration interspersed with the plants; we used large pieces of quartz that were in the backyard. The flat pebbles that line the bottom of the hill above the side-walk were also from the backyard. It’s nice to use items from our house and not have to buy more of things.

The yard will be relatively low-maintenance. I do have to water it twice a week and fertilize it twice a year. The juniper and spruce will need pruning, but that won’t need to happen for more than a year. I think the hardest maintenance will be keeping the ivy from the neighbor’s yard out of ours. Alas, it is done. Now to the backyard!

shades of green

I love this combination of plants! The shapes, textures and colors all compliment each other so beautifully. The shiny blue-green glaze of the pot in the foreground and the barely visible natural stone fountain in the background make this a Sunset Magazine/Garden Design-worthy image, if I do say so myself! This little vignette is part of a garden I designed and planted about a year ago that had an Asian-inspired theme. Now that I’m done gloating, if anyone’s still with me, here’s a list of the plants:

- Echeveria imbricata (Hens & Chicks)

- Juniperus procumbens ‘Nana’ (Dwarf Japanese Juniper)

- Bamboo (can’t remember which, but definitely ‘clumping’ type!)

- Chondropetalum tectorum (Cape Rush)

BTW, the fountain is from Fabbri Home & Garden in Half Moon Bay and the pot is from AW Pottery in Berkeley. Isn’t it great when a plan comes together??

Photo by Glen
Location: Moab, UT
In the tree: Blue and gold macaw “Merlin”

I’ve gotten a few questions about why I have quite the collection of “birds in trees” photos and a few people started to catch on that they are all Moab trees!

The reason is, your freeflight bird is bound to try a tree out whether it’s on accident, out of breath and desperately needing a spot to land or just curious among other reasons. The bummer about them landing in a lot of the trees in Moab is that they have juniper berries in them and the birds soon find out that they LOVE them! The good thing about them, is that they give your bird really great breath, haha.

They won’t harm your bird and they are safe for your bird to eat, so there are no concerns there. Just make sure you have a strong enough recall (with a good enough treat) to get your bird back out of the tree!

Backup and restore program is used to backup the current configuration of Checkpoint R70. This is a very important step need to be followed in order to restore all the Checkpoint configuration in an event of failure.

This backup will also copy out current rules (Policy) available in you firewall.

Backup R70 Configuration (Machine A)

Steps to backup checkpoint configuration as follow.

1. Login to the Checkpoint R70 as expert mode.

2. Navigate to the “/var/CPBackup/backup/backups” folder in your unix environment.

3. Run “backup”.

4. The earlier command will run for few minutes and create a file starting with “BACKUP…” in your backup directory.

5. Copy and save this file in safe place. You will need this file during the restore process.

Restore CheckpointR70 Configuration (Machine B)

Steps to backup checkpoint configuration as follow.

1. Login to the Checkpoint R70 as expert mode.

2. Navigate to the “/var/CPBackup/backup/backups” folder in your unix environment.

3. In the backups folder run “restore <backupfilename>”.

Note <backupfilename> is the Checkpoint configuration backup file which we have earlier backup.

4. Wait for few minutes, this process can take a while since it will start restoring every each configuration including routing, licensing and etc.

5. Use the Checkpoint provided Smart Dashboard to verify the rules (policy). Alternatively if you have install the Chekpoint R70 portal. You may login to the portal and check the routing table and licensing information.

Note: In order to login to the Smart Dashboard you will need to add in your machine current IP address in GUI Client menu as well in the Checkpoint R70 rules.

Se pare că da . Nu am reușit să găsim un proiect care să urmărească numai cele 2 domenii decise de noi.

Există proiecte/site-uri ce acoperă mai multe domenii din IT & C:

• http://www.ajaxmatters.com/

Este un blog despre tehnologia AJAX, înființat în 2004. Conține articole foarte interesante, foarte bine explicate și exemplificate.

• http://websitetips.com/

Scopul site-ului este de a ajuta oamenii să găsească resurse de mare calitate din domeniul Web – design și development. Conține tutoriale, articole, recomandări de cărți și multe altele. A fost pus pe picioare încă de acum 13 ani și continuă să facă oameni fericiți.

• http://w3schools.com/

Site-ul este binecunoscut și folosit drept bibliografie și în cadrul labortatorului de Interfețe Om Calculator. Este cea mai mare sursă de tutoriale web de pe Internet.

Oferă ceritifcări w3schools:

• HTML Developer
• JavaScript Developer
• XML Developer
• ASP Developer
• PHP Developer

Prezintă:

• HTML
• XML
• Browser Scripting
• Server Scripting
• Multimedia
• Web Building

• http://www.networkcomputing.com/

Oferă suport și informații pentru cei pasionați de networking.

Domeniile acoperite sunt:

• Backup & Recovery
• Data Center
• Data Protection
• Networking & management
• Servers & Storage
• UC & VoIP
• Virtualization
• WAN
• Wireless

• http://www.cisco.com/

Nu mai are nevoie de prea multă introducere. Este o companie foarte mare și importantă ce se ocupă de networking și o face destul de bine. Site-ul oferă suport, documentații și un portal pentru oamenii ce doresc să urmeze una dintre academiile sale.

• http://www.juniper.net/us/en/

O altă putere în domeniul networking-ului cu o structură a site-ului asemănătoare cisco.

Acestea sunt unele dintre nenumăratele site-uri ce se ocupă ori de networking, ori de Web. Ultimele 2 nu se ocupă de tutoriale sau de articole de mare valoare, fiind mai mult site-uri de prezentare și suport, dar fără ele networking-ul de azi nu ar mai fi fost unde este .

Nu putem decât să sperăm că vom ajunge și noi un site de referință în cele 2 domenii . Wish us luck!

Moving towards JNCIE is not very easy. Alot of things to cover, many milestones to achieve, needs to practice alot of things. Well so far i have started as usual i did in JNCIP just following the book and practicing as much as i can.

1. Network Discovery
2. MPLS  and Traffic Engineering
3. Firewall Filters and Traffic Sampling
4. Multicast
5. IPV6
6. Class of Servic
7. VPNS

Two Parts from start are almost covered. Anyone have any suggestion and tips about everything is welcome.