Skip to content

Network Ninja

The Long Road to Cisco

  • Home
  • About
  • Legal Disclaimer
  • Archives

Less
More
Trim
Untrim
« Older
Home
Loading
Newer »

Tag Archive for 'CAPEX'

EMEA Cisco Recruiting

Published
by
Deon Botha
on July 3, 2008
in Cisco Systems and Vine
. 0 Comments

This may be old-ish news but I found this interesting. This is a Cisco initiative to help Channel Partners Address Technology Skills Shortfall with a new Partner Talent Portal in Middle East and Africa. Stories like this always lead me off the beaten track and thinking about interconnected things (I’m weird, that’s what makes me specials).

Demand and Supply

The management side of me finds this interesting, its probably more complex than this explanation but this is the basics of something called supply and demand (which is something I got drilled into my head when I was studying). The graph basically shows a single supply source for qualified individuals (that would be you and me) and a radical change in demand (market driven demand from Channel partners and even Cisco) and if you are wondering the other axis (not market) is generally what your pay might be as demand increases.

In times when there is growth (2010 World cup in South Africa, good economic conditions recently) there is a strong demand for “skilled” individuals (skill + experience), this creates a supply problem because there is then a short supply (due to (1) skill shortage in the form of certified individuals in this case (2) the certified individuals having no real world experience) to fill the demand.

This will always happens when there is a rapid upturn in the market, supply lags behind demand because oversupply is in most cases expensive (having certified individuals on staff with nothing to do) and counter productive (carrying the expense of certifying individuals when there is no work for them or need for them). There are many factors that play on this that I haven’t included because this can get overly complicated fairly quickly if you consider them for example in a South African context the massive skilled brain drain to other more developed markets, political factors, crime, local employment and training policies employed by companies, private sector willingness to skill and give experiential training, etc.

What is interesting and will be interesting about this scenario is what will happen in the short to long term future with the downturn in the global market, what I have already encountered (in the last couple of months) is that customers are less willing to undertake CAPEX spending (uncertainty about what will happen in the short to near term), which is bad as networking and network equipment is seen as a CAPEX spend.

If doom and gloom is on the horizon it doesn’t however mean the end of the world as OPEX spending to keep operations going will continue in the form of maintenance of currently installed equipment (which still needs certified skilled individuals to maintain) the only difference will be that the lifecycle of installed kit will be extended as customers will hold onto their kit longer to squeeze the Return on Investment ratio dry or the kit actually breaks.

Thanks goes to JP for the heads up.

Planning Voice on a Data Network

Published
by
Deon Botha
on May 21, 2008
in BCMSN, Certification, Cisco Systems and VoIP
. 0 Comments

There are numerous benefits to packet switched telephony:

  • More efficient use of bandwidth and kit: Traditional telephony networks use a 64-kbps (For argument lets say 1B Channel on a ISDN line) channel for every voice call. Packet telephony shares bandwidth among multiple logical connections and offloads traffic volumes from existing voice switches.
  • Lower costs for telephony network transmissions: A substantial amount of equipment is needed to combine 64-kbps (ISDN) channels into a high-speed link for transport across a network (Lets say an ISDN PRI). Packet telephony statistically multiplexes voice traffic alongside data traffic. This consolidation represents substantial savings on CAPEX and OPEX.
  • Consolidated voice and data network expenses: Data networks functioning separately from voice networks become major traffic carriers. The underlying voice networks can be converted to utilize the packet-switched architecture to create a single integrated communications network with a common switching and transmission system. The benefit is CAPEX and OPEX savings.
  • Increased revenues from new services: Packet telephony enables new integrated services, such as broadcast-quality audio, unified messaging, and real-time voice and data collaboration. These services increase employees productivity and profit margins well above those of basic voice services. In addition, these services enable companies and service providers to differentiate themselves and improve their market position.
  • Greater innovation in services: Unified communications use the IP infrastructure to consolidate communications methods that were previously independent (Fax, voicemail, email, wireline telephone, cellular phone, and the web). The IP Infrastructure provides users with a common method to access messages and initiate real-time communications – independent of time, location, or device.
  • Adding to new communications devices :P acket technology can reach devices that are largely inaccessible to the time-division multiplexing (TDM) infrastructures of today (pcs, wireless devices, household appliances, PDAs). Access to these devices enable companies and service providers to increase the volume of communications they deliver, the breadth of service they offer, and the number of subscribers they serve. Packet technology, therefore, enables companies to market new devices, including videophones, multimedia terminals, and advanced IP Phones.
  • Flexible new pricing structures: Companies and services providers with packet-switched networks can transform their service and pricing models. Because network bandwidth can be dynamically allocated, network usage no longer needs to be measured in minutes or distance. Dynamic allocation gives service providers the flexibility to meet the needs of their customers in ways that bring them the greatest benefits.

The basic components for voice on a IP network are as follows:

  • IP Phones: The end-device on desks
  • Gatekeeper: Provides Connection Admission Control (CAC), bandwidth control and management and address translation.
  • Gateway: Provides translation between voice over Internet Protocol (VoIP) and non-VoIP networks, such as the public switched telephone network (PSTN). It provides physical access for local analog and digital devices (telephones, fax machines, and PBXs)
  • Multipoint Control Unit: Provides real-time connectivity for participants in multiple locations to attend the same videoconference or meeting.
  • Call Agent: Provides call control for IP Phones, CAC, bandwidth control and management, and address translation.
  • Application Server: Provides services such as voicemail, unified messaging, and Cisco CallManager Attendant Console.
  • Videoconference Station: Provides access for end-users participation in videoconferencing. This station has a video camera and a microphone. The user can view video streams and hear the audio that originates from the remote user station.

There are other components not listed here like voice applications, interactive voice response (IVR) systems, and softphones that meet the specific needs of enterprise.

Voice and Data Traffic Characteristics

Voice traffic has extremely stringent QoS requirements (because it is extremely delay sensitive). Voice traffic generates a smooth demand on bandwidth and has minimal impact on other traffic (60 – 120 bytes), as long as voice traffic is managed. Because of the resulting time sensitive nature User Datagram Protocol (UDP) is used to package voice packets; TCP retransmit capabilities have no value (because if it needs to be retransmitted then there is delay in the actual conversation occuring NOW).

For voice quality, delay should be no more than 150ms (one-way) and less than 1% packet loss. A typical voice call requires 17 – 106 kbps of guaranteed priority bandwidth, plus additional 150bps per call for voice-control traffic. Multiplying this out for the maximum calls expected during busiest times the overall bandwidth requirements for voice traffic can be calculated.

Because Data traffic is not as delay sensitive and can tolearate high drop rates the restransmit capabilities of TCP has become important, as a result many applications use by default TCP.

In networks, important business critical applications are ussually easy to identify. Most applications can be identified based on TCP or UDP port numbers (HTTP, HTTPS, FTP, TELNET, SQL, ETC). Some application use dynamic port numbers that, to some extent, make classification more difficult. Cisco IOS software supports network-based application recognition (NBAR), which can be used to recognize dynamic port applications.

VoIP Call Flow

As I mentioned in a previous post (see HSRP Accross Trunk Links) and some other places its best practice to setup voice and data on separate VLANs (I did in my own network). This is done so that QoS can be applied to prioritize the VoIP traffic as it traverses the network. If this is not done then voice and data traffic contend for available traffic without consideration for other devices (one or the other is going to suffer).

A major component of designing a successful IP Telephony network is bandwidth provisioning. The bandwidth requirement is calculated by adding the total required bandwidth for voice, video and data together; the sum should not be more than 75% of the link total.

For a traffic perspective IP Telephony consists of two types of traffic:

  1. Voice Carrier Stream consists of Real-Time Transport Protocol (RTP) packets that contain actual voice samples.
  2. Call Control Signaling that contains packets belonging to one of several protocols used to set up, maintain, tear down, or redirect calls. Depending on the end-point this could be H.323 or Media Gateway Control Protocol (MGCP)

Auxiliary VLANs

Some Cisco Catalyst switches offer a unique feature called “Auxiliary VLAN“. This feature allows one to overlay a voice topology over an existing data network. One can segment phones into a separate logical network, even though the data and voice network are physically the same.

The auxiliary VLAN feature places the phones into their own VLANs without any end-user configuration. Additionally VLAN assignment can be maintained even if the phone is moved.

How this works is that when a phone is plugged into the switch (whichever port), the phone will request a DHCP address, and the phone is placed in a VLAN automatically. With phones in their own VLANs administrators can troubleshoot and identify problems easily. This also makes enforcement of QoS and security policies easier.

QoS

QoS is the application of features and functionality required to actively manage and satisfy the networking requirements of applications that are sensitive to loss, delay and delay variations (jitter). QoS allows preference to be given to critical application flows for the available bandwidth.

Cisco IOS implementations allows for QoS to provid these features:

  • Priority access to resources: QoS allows administrators to control which traffic it allows to access specific network resources such as bandwidth, kit, and WAN links.
  • Efficient management of network resources: If network management and accounting tools indicate that specific traffic is experiencing latency, jitter, and packet loss, then QoS tools can be used to adjust how traffic is handled.
  • Tailored service: The control provided by QoS enables Internet Service Providers to offer carefully tailored grades of service to their customers.
  • Coexistance of mission-citical applications: QoS technologies ensure that mission-critical applications receive priority access to network resources while providing adequate processing for applications that are not delay sensitive.

High Availability

Traditional Telephony networks strive to provide 99.999 (5.25 minutes) of downtime a year. This is less downtime than most data networks. To provide the same experience this means choosing hardware and software with a low mean time between failure (MTBF) or installing redundant links and hardware.

Availability is when a user wants to make a call the network is able to respond to that need. Efforts to ensure availability would include proactive management to predict failure and taking steps to correct problems in design of the network as it grows. When the converged network goes down things downtime can be minutes, hours or days. This is unacceptable in a converged network where downtime means no phone calls. Providing for uninterpretable power supplies (UPS), lighting arrestors and other means to ensure availability at all costs.

High Availability encompases many areas of a network. In a fully redundant network these components need to be duplicated:

  • Servers and call managers,
  • Acces layer devices (layer-2 switches)
  • Distribution layer devices (routers or Layer-3 switches)
  • Core layer devices (layer-3 switches)
  • Interconnections (WAN links, PSTN Gateways, ISP links)
  • Power supplies and UPSs

Notes and Notices:

This is a part of my personal BCMSN notes and research to assist myself in learning and understanding the concepts and theory for the BCMSN exam. I learn by making notes reading and writing things down and wish to file them where I can’t lose them. These notes are not to be seen, judged or mistaken for replacements to Cisco recognized and authorized training which I personally support and attend and suggest you undertake if you are going for the BCMSN Certification.

Intelligent Integrated Network and Service-Orientated Network Architecture

Published
by
Deon Botha
on April 2, 2008
in BCMSN, Certification, Cisco Systems, IIN and SONA
. 1 Comment

This post deals with two concepts that fit into one another or are parts of one another as the Cisco Service-Orientated Network Architecture (SONA) framework outlines the “how-to” for enterprises to evolve their Information Technology (IT) infrastructures into Intelligent Integrated Networks (IIN). The follow on to this post is the enterprise-wide architecture that explains the model a bit clearer.

Overview

The Cisco IIN Vision is one of network integration, intelligence and participation; while SONA is the three layered approach to achieving IIN namely the network services, interactive services and application layers respectively.

IIN Explained

Converged Networking requires a more integrated IT infrastructure (servers, data storage, workstations, etc) and networking infrastructure (switches, routers, etc). This is because of the needs and requirements of IP Protocol based applications that use voice, video and data network information in one interface (MS Dynamcs Applications could be an example iow CRM).

A standards based modular converged network provides for evolutionary (change over time) functionality addition (NAC, Security, voice, video) and IP-based applications (CRM, ERP, Web Applications, Software on Demand) capability. This by extension allows increased productivity by giving more information at once to employees, Information on demand when needed where needed, and reducing cost (long run allowing company to lower OPEX costs of IT; probably bring down IT IS costs and lowering of CAPEX expenditure year-on-year just for maintaining and upgrading) by allowing incremental changes to infrastructure (compared to wholesale replacements). I can go into skill sets, training expenses on new kit, learning curves, downtimes on installations etc.

By leveraging and applying built in component intelligence (ISR, Self Defending Network, etc) within the network components and extending those benefits end-to-end (from the core to the edge) intelligence and paid for features are spread accross the entire network.

With the participation of the network in service delivery; the added intelligence in network components mean active management, monitoring, and optimization by the network in service and application delivery end-to-end. The results is IT resources being pooled and shared or virtualized to changes in the network with the abliity to adapt to business needs and requirements. Through the use of Application-Orientated Networking (AON) the network can optimize performance and efficient delivery of networked application to end-user.

SONA

SONA

CISCO SONA FRAMEWORK LAYERS*

The path or “how-to” for IIN is SONA which explains how integrated systems can both allow for a dynamic, flexible architecture, and provide for operational efficiencies through standardization and virtualization.

This is very broad stroke overview and not in detail; for a more detailed explanation as to the how this all works see the ECNM or Enterprise Wide Architecture.

The Network Infrastructure Layer is where all IT resources (servers, storage, and clients) are interconnected (campus, branch, data centre, WAN, MAN, teleworker) across the converged network foundation. The objective of this layer is to enable anywhere and anytime connectivity.

The Interactive Services Layer enables efficient allocation of resources to applications and business processes that work together to create functionality that can be used by multiple applications and is delivered through the network infrastructure.

The Application layer includes applications (commercial off-the-shelf and homegrown software) and collaboration applications. This layer can also use network services such as presence and location to build innovative solutions that enhance user experience. The objective is to meet business requirements and achieve efficiencies by leveraging the interactive services layer.

Resources:

Cisco SONA Fact Sheet

Cisco SONA Website

Aragoen Celtdra over at Baby, You can Route my World! has a nice explanation on this for the BSCI course

Notes and Notices:

This is a part of my personal BCMSN notes and research to assist myself in learning and understanding the concepts and theory for the BCMSN exam. I learn by making notes reading and writing things down and wish to file them where I can’t lose them. These notes are not to be seen, judged or mistaken for replacements to Cisco recognized and authorized training which I personally support and attend and suggest you undertake if you are going for the BCMSN Certification.

*CISCO SONA FRAMEWORK LAYERS: Graphic taken from SONA Fact Sheet on the Cisco Website, Copyright Cisco Systems, Inc


Search

About

You are currently browsing the Network Ninja weblog archives for 'capex' tag.

Latest

RSS
  • Digital Growth with your Job
  • Open Shortest Path First – OSPF Fundamentals – Scenario
  • Open Shortest Path First – OSPF Fundamentals – Questions and Answers – Question 13
  • Open Shortest Path First – OSPF Fundamentals – Questions and Answers – Question 12
  • Open Shortest Path First – OSPF Fundamentals – Questions and Answers – Question 11
  • Open Shortest Path First – OSPF Fundamentals – Questions and Answers – Question 10
  • Open Shortest Path First – OSPF Fundamentals – Questions and Answers – Question 9
  • Open Shortest Path First – OSPF Fundamentals – Questions and Answers – Question 8
  • Open Shortest Path First – OSPF Fundamentals – Questions and Answers – Question 7
  • Open Shortest Path First – OSPF Fundamentals – Questions and Answers – Question 6

Archives

  • June 2009
  • April 2009
  • March 2009
  • February 2009
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008

Categories

  • 802.11 (7)
  • 802.1Q (1)
  • 802.1X (1)
  • AAA (1)
  • Access Point (7)
  • ACL (4)
  • Addressing (3)
  • Asides (31)
  • auto-summary (3)
  • AutoQoS (1)
  • Bandwidth (2)
  • BCMSN (55)
  • BDR (2)
  • BGP (1)
  • BPDU Filtering (1)
  • BPDU Guard (2)
  • BPDU Root Guard (1)
  • BSCI (67)
  • BSCI Notes (18)
  • BSCI Questions (48)
  • Business (1)
  • Cabling and Equiptment (3)
  • CAM (1)
  • CCDA (1)
  • CDP (1)
  • CEF (1)
  • Certification (123)
  • CIDR (2)
  • CIR (2)
  • Cisco Systems (144)
  • Concepts and Constructs (76)
  • CoS (1)
  • Cost (3)
  • DAI (1)
  • DDNS (1)
  • Debug (2)
  • DHCP Snooping (1)
  • DHCP Spoofing (1)
  • DR (3)
  • DUAL (1)
  • Dynamic ARP Inspection (1)
  • ECNM (5)
  • EIGRP (5)
  • Enterprise Architecture (7)
  • EtherChannel (1)
  • GLBP (1)
  • Hello Timer (2)
  • Hold Timer (2)
  • Hot Standby Router Protocol (1)
  • HSRP (1)
  • IGRP (1)
  • IIN (2)
  • Inter-Vlan Routing (1)
  • Interconnection Technologies (2)
  • IP Source Guard (1)
  • IS-IS (1)
  • ISL (1)
  • LACP (1)
  • Link State Advertisements (2)
  • Load Balancing (2)
  • Loop Guard (1)
  • MAC Address Flooding (1)
  • MLS (1)
  • MSTP (1)
  • NBAR (1)
  • NBMA (1)
  • Off-Topic (12)
  • OSPF (18)
  • PAgP (1)
  • passive-interface (1)
  • PoE (1)
  • Port Security (1)
  • Priority (2)
  • Proxy ARP (1)
  • PVC (1)
  • QoS (2)
  • RIP (1)
  • RIPv2 (1)
  • Root Guard (1)
  • RSTP (1)
  • Show (6)
  • Software (1)
  • SONA (2)
  • SSH (2)
  • STP (5)
  • Stub Router (3)
  • summary-address (1)
  • Support (4)
  • Switch Spoofing (1)
  • TCAM (1)
  • Telnet (2)
  • Troubleshooting (1)
  • Trunk (6)
  • Unidirectional Link Detection (1)
  • VACL (3)
  • VC (1)
  • Vine (20)
  • VLAN (11)
  • VLAN Hopping (1)
  • VLSM (1)
  • VoIP (1)
  • VRRP (1)
  • VTP (4)
  • VTY (1)
  • Wireless (7)


Styled with Sawchuk

Powered by WordPressabc and K21.0-RC7

Entries Feed and Comments Feed

44 queries. 1.2170 seconds.