The Network Monkey!: April 2012

Thursday, April 26, 2012

Are you playing with #ipv6 yet?

A couple guys from Ericcson posted this RFC

http://tools.ietf.org/html/rfc6586

Consider going to #HP #Discover in June

You can register here:

https://h30496.www3.hp.com/portal/newreg.ww?jumpid=

To get $300 off, use the special code PSLS

Some of the highlights of just the networking track are:

1. Keynote:

· Attend the HP Networking track keynote

TK2196 : HP Networking storm center: tracking the cloud from data center to user (Bethany Mayer, Senior Vice President and General Manager, HP Networking)

o Hear from Bethany Mayer how HP is shaping the industry, driving networking innovations and providing FlexNetwork architecture solutions that span the data center, campus, branch and extend to the cloud.

2. Visit the expo floor and talk to the experts

· Learn more about the HP Networking experience

3. Key topics of the Networking track include:

· FlexNetwork Architecture

· Virtual Application Networks

· OpenFlow Enabled Switches

4. Key Sub-tracks include:

o BB2940 : The Total Economic Impact of HP networking solutions; building the business case (ROI) for your data center deployment (co-presented with Forrester Research)

o TB2381: IPv6 Deployment: Understanding internal IPV6 protocols

o BB2372: What’s your dual vendor strategy? How to plan and deploy a dual-vendor network

o TB2374: Implementing Virtual Application Networks with FlexNetwork Architecture

o RT2389: OpenFlow Switching: The future of networking

o RT2388: Forging the way to a cloud network

5. Hands-on lab:

· Experience the technology first hand with 2 hour hands-on labs – THESE FILL UP FAST!!

HOL2029: Best practices lab for HP Virtual Connect FlexFabric and HP Networking switches

Wednesday, April 25, 2012

Is #Cisco code buggy beyond #comicrelief ?

http://packetpushers.net/brand-inertia-is-cisco-your-most-trusted-it-partner/

Monday, April 23, 2012

#HPN customers, you're invted to a party at #Interop

https://www.seeuthere.com/rsvp/invitation/registration.asp?id=/m1c9c3a7-82043QD3SGDP

Thursday, April 19, 2012

@etherealmind comments on #openflow and #sdn

http://etherealmind.com/openflow-doesnt-undermine-vendors-even-though-it-changes-everything/?utm_campaign=twitter&utm_medium=twitter&utm_source=twitter

@sherylcrow and @donhenley to provide entertainment at #HP #Discover

sweet!

@forrester says that #HP provides 47% #ROI with #networking

http://h30507.www3.hp.com/t5/HP-Networking/Get-the-facts-Independent-study-shows-HP-Networking-can-provide/ba-p/110577

Could #CLI be dead? #HP #IMC is starting to make that true

http://h30507.www3.hp.com/t5/HP-Networking/The-Beginning-of-the-End-for-CLI-Introducing-IMC-Virtual/ba-p/110789

Sflow on HP e4800g

Globally you need to do the following:

sflow agent ip 10.201.1.22 <ip address on the switch>
sflow collector 1 10.201.1.198 <ip address of the collector or nms>

Learn more about #HP #Cloud announcements

http://h30499.www3.hp.com/t5/Grounded-in-the-Cloud/Watch-This-Week-in-Cloud-1-of-6-Converged-Cloud-feat-with/ba-p/5621877

Wednesday, April 18, 2012

@cisco really has 3000 #UCS customers

I've know found the answer to the question I've been wondering for a long while. How many REA:L UCS customers are there. The answer, thanks to Padmasree Warrior is approximately 3,000.

Why does that differ from the 11,000 that Cisco has touted? 3,000 is the number of REPEAT customers that Cisco has.

Thats the customers that have purchased a second time. Why dont I count the first time? Easy... I'm in the business...I compete all the time with Cisco. They give away UCS all the time.. i.e. Its bundled into a larger deal. A repeat customer is one that has actually liked the free system the were given and now has bought more.

While the industry, including HP, should still be worried..and should take decisive action... it truly is not as bad as Cisco's marketing team has claimed. They are not as far ahead as they claim to be.

Hey..I get it...

I worked there...

Its simple...

People like winners.

People like to be popular.

Sound popular...sound like the winner...everyone want to hang out with you.

Its contagious.

It feeds upon itself.

It actually can become reality.

People can get excited and do the wrong things...just to be popular.

Friends dont let friends buy Cisco...

lol....

#HP #SPP and #SUM make managing your #c7000 a peice of cake

Recently, HP made really great strides in making managing your C7000 blade systems a ton easier!

First..and major..is that HP has now combined all of the software/firmware into a single service packed call SPP (Service Pack for Proliant)

Secondly... HP is now emphasizing a tool that has been around for a while called SUM that helps managed the software update process.

Keeping a C7000 up to date is no longer an issue...as I know from several customers I've talked to.

http://h18004.www1.hp.com/products/servers/management/spp/index.html

Tuesday, April 17, 2012

whats brewing in the #northbound api for #sdn networks?

http://www.sdncentral.com/blog/a-change-is-blowing-in-from-the-north-bound-api/2012/04/?utm_campaign=twitter&utm_medium=twitter&utm_source=twitter

@datacenteroverlords post on #SDN and #openflow

http://datacenteroverlords.com/2012/04/12/openflows-awkward-teen-years/

Don't be confused by the #virus reports on #HP #switches

Its really a non-event... you can get the facts by looking at our security advisory. Only 17 switches were affected and you would have to take great effort to get yourself into trouble

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03249176

Configuring #HP #IMC to collect #sflow from @Juniper

http://www.myteneo.net/articles/-/blogs/24062/maximized?p_p_auth=7lmodzSE&_33_returnToFullPageURL=%2Farticles%3Fp_p_id%3D2_WAR_knowledgebaseportlet%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_pos%3D1%26p_p_col_count%3D2%26_2_WAR_knowledgebaseportlet_mvcPath%3D%252Fdisplay%252Fview_article.jsp%26_2_WAR_knowledgebaseportlet_resourcePrimKey%3D24562

Using #HP #IMC to collect info from @Cisco #ASA vpn tunnels

Nice article on this...

http://www.myteneo.net/articles/-/blogs/24929/maximized?p_p_auth=7lmodzSE&_33_returnToFullPageURL=%2Farticles%3Fp_p_id%3D2_WAR_knowledgebaseportlet%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_pos%3D1%26p_p_col_count%3D2%26_2_WAR_knowledgebaseportlet_mvcPath%3D%252Fdisplay%252Fview_article.jsp%26_2_WAR_knowledgebaseportlet_resourcePrimKey%3D24562

#HP working with #Verizon on #SDN and #OpenFlow

SDN's and OpenFlow are gathering a LOT of momentum!

http://www.lightreading.com/document.asp?doc_id=219843&

Friday, April 13, 2012

Nice video that @IndianaU did on their #HP Network

Thursday, April 12, 2012

@Cisco #Nexus F2 Linecards dont support #FCOE on Sup1

http://www.netcraftsmen.net/resources/blogs/looking-at-the-cisco-nexus-7000-f2-card.html

Tuesday, April 10, 2012

#Cisco loses #router market share & #HP gains

http://seekingalpha.com/article/464551-cisco-s-declining-router-share-h-p-s-gain

Nice article on #HP #IMC on @packetpushers

http://packetpushers.net/review-hp-imc-intelligent-management-center/

#ECMP in #Comware

Configuring load sharing
A routing protocol can be configured with multiple equal-cost routes to the same destination. These routes
have the same preference and will all be used to accomplish load balancing if no route with a higher
preference is available.
Load sharing is implemented in the following ways:
• Bandwidth-based load sharing—Packets are forwarded based on the configurable bandwidths of
the interfaces. The greater bandwidth an interface has, the more packets it forwards.
• User-based load sharing—Load sharing based on the user information (source IP address) of
packets.

Configuring bandwidth-based load sharing

NOTE:
Before configuring this feature, disable fast forwarding. For more information about fast forwarding, see
the Layer 3—IP Services Configuration Guide.
If multiple outbound interfaces/next hops to a destination are found during packet forwarding:
• When bandwidth-based load sharing is enabled, the device calculates the packet forwarding
proportion for each interface based on the bandwidths of all the interfaces, and then determines
through which interfaces to forward subsequent packets based on both the interfaces’ packet
forwarding proportions and the number of packets each interface has forwarded.

• When bandwidth-based load sharing is disabled, all the interfaces are used for packet forwarding
in turn.

Follow these steps to configure bandwidth-based load sharing:
To do… Use the command… Remarks
Enter system view system-view —
Configure bandwidth-based load
sharing bandwidth-based-sharing
Optional
Disabled by default

Enter interface view
interface interface-type
interface-number —
Specify the load sharing
bandwidth of the interface load-bandwidth bandwidth
Optional
The default is the physical
bandwidth of the interface.
If you specify a value of 0 for the
bandwidth argument, routing is
disabled on the interface and the
interface will not be used for load
sharing. Other states of the
physical interface will not be
affected.

Return to user view return —
Display statistics about
bandwidth-based load sharing
display load-sharing ip address
ip-address { mask | mask-length }
[ | { begin | exclude | include }
regular-expression ]
Optional
Available in any view
Clear statistics about
bandwidth-based load sharing
reset load-sharing statistics ip
address ip-address { mask |
mask-length }
reset load-sharing statistics all
Optional

Configuring user-based load sharing
NOTE:
If both user-based load sharing and bandwidth-based load sharing are configured, user-based load
sharing applies.

Follow these steps to configure user-based load sharing:

To do… Use the command… Remarks
Enter system view system-view —
Enable user-based load sharing ip user-based-sharing enable Required
Enter interface view
interface interface-type
interface-number —
Enable user-based load sharing on ip user-based-sharing enable Required
6
To do… Use the command… Remarks
the interface
Specify the load sharing
bandwidth of the interface load-bandwidth bandwidth
Optional
The default is the physical
bandwidth of the interface.
If you specify a value of 0 for the
bandwidth argument, routing is
disabled on the interface and the
interface will not be used for load
sharing. Other states of the
physical interface will not be
affected.