Cisco Design

CCDA-CCDP-CCDE-BSCI-BCMSN-ARCH

CCDP Syllabus

Mar 3rd

Posted by Johnny in Cisco Design | 1 views

No comments

Syllabus
? Certification:The certification indicates advanced knowledge of intelligent network design concepts and principles.A credentialed network professional can discuss, design, and create advanced addressing and routing, security, network management, data center, and IP multicast complex multi-layered enterprise architectures that include virtual private networking and wireless domains.


Prerequisites: Valid CCNA and CCDA
Exams & Recommended Training More >

Popularity: 2% [?]

, , , , , , , , ,

CCIE & CCDE Statistics

Oct 21st

Posted by Johnny in CCIE Training | 99 views

No comments

CURRENT TRACKS:
Total of Routing and Switching CCIEs: 6561 (36.81 % of Cisco’s official statistic)
Total of Security CCIEs: 834 (35.82 % of Cisco’s official statistic)
Total of Service Provider CCIEs: 448 (28.21 % of Cisco’s official statistic)
Total of Storage Networking CCIEs: 63 (42.57 % of Cisco’s official statistic)
Total of Voice CCIEs: 489 (45.4 % of Cisco’s official statistic)
Total of Wireless CCIEs: 5 (35.71 % of Cisco’s official statistic)

RETIRED TRACKS:
Total of Design CCIEs: 3
Total of ISP Dial CCIEs: 73
Total of SNA IP CCIEs: 16
Total of WAN Switching CCIEs: 36

Total with 1 certification: 6713
Total with multiple certifications: 782 (34.83 % of Cisco’s official statistic)
Total with 2 certifications: 599
Total with 3 certifications: 138
Total with 4 certifications: 31
Total with 5 certifications: 12
Total with 6 certifications: 2

Total Dutch CCIEs on the list: 152 (73.43 % of Cisco’s official statistic)

Total Inactive CCIEs: 425 (5.67 % of verifiable CCIEs listed on this website)
Total Suspended CCIEs: 233 (3.11 % of verifiable CCIEs listed on this website)

Not verifiable: 723

 

Popularity: 2% [?]

, ,

CCDE Hall of Fame

Oct 21st

Posted by Johnny in Cisco Design | 79 views

No comments

Total on the list = 15 (includes active, inactive, and suspended).
All statistics are based upon actual verification with the Cisco CCIE/CCDE Verification Tool.

20070001 – RUSS WHITE
20070002 – JOHN CAVANAUGH
20070003 – BRUCE PINSKY
20070004 – KHALID RAZA
20070005 – WILLIAM PARKHURST
20070006 – ALVARO RETANA
20070007 – MOSADDAQ TURABI
20070008 – STEVE BARNES
20080001 – RYAN HICKS
20080002 – MICHAEL MORRIS
20080003 – REINHOLD FISCHER
20090001 – THOMAS WHALEY
20090002 – RADU HAMBASAN
20090003 – JEREMY FILLIBEN
20090004 – CLAUS HOLBECH

 

Popularity: 2% [?]

, ,

multiple LLQ Low Latency Queues / bandwith (remaining) percent

May 15th

Posted by Johnny in CCSP Training | 39 views

No comments

LLQ means priority a queue, to forward voice and video traffic before all other traffic.

If you have multiple LLQ queues, the difference between the single and multiple queue configuration is, that if you have at least two priority queues, both get policed. So if configured in a single police-map command, you will always policed the traffic at a maximum rate. Even if more bandwidth will be available, in case one queue fills up and the other still is not yet. The traffic will strictly be policed at the maximum rate.

The bandwidth percent gives the option to reserve a percentage of a link, also in case the link speed will change in the future. It will be calculated dependent on the actual link speed for the interface. This is changeable with the “bandwidth” command on the interface.

The bandwidth remaining percent gives the option, to configure a remaining bandwidth on the actual link. If the link for example has a bandwidth of 1000 kbps and there is already different LLQ’s (100,200), then this is added to 300 kbps being already reserved. “max reserved-bandwidth” will be per default 75% on an interface, which is 750 kpbs. So if you configure a reservation from the remaining percent, it will be calculated from

750 kbps

-300 kbps

_______

450 kbps.

So if you configure “bandwidth remaining percent 50″ you will get 225 kbps from the bandwidth of the interface.

Source:

Cisco Qos, Exam Certification Guide, Second Edition, Wendell Odom

Popularity: 1% [?]

, , , , ,

QoS and what to manage with what

May 11th

Posted by Johnny in CCNP Training | 22 views

No comments

There are many different kind of QoS techniques around at Cisco. All of them are like a tollbox for managing traffic. Each technique has it’s preferred operational area. So here are some scenarios in which you would use a certain technique.

  • Classification

You want to provide a prefered service to a type of traffic. The packet may be marked or not. Classification don only on one device, without marking the packet is described as a per-hop based classification. PQ (priority queing) and CQ (custom queing) are techniques used for this. Possible methods to identify certain traffic are ACL’s, policy based routing, comiited acces rate (CAR) or network-based application recognistion (NBAR).

  • Congestion Management

What if an interface is accessed above it’s given bandwidth? Congestion occurs and priority queuing (PQ), custom queuing (CQ), weighted fair queuing (WFQ), and class-based weighted fair queuing (CBWFQ) are tools to mangage congestion.

  • Queue Management

If a queue does fill up and buffers are flowing over, packets must be dropped. Which packets to drop, maybe packets with lower priority, to be able to deliver higher priority, this is done with Weighted early random detect (WRED).

  • Link Efficiency

Some packets might be to large for efficent transport and it might be neccessary to compress these packets. RTP header compression (Compressed Real-Time Protocol header) can be used for this.

  • Traffic shaping and policing

When shaping traffic, you would take care of a certain link not to exceed the configured bandwitdh or maybe another certain . Traffic is buffered then, with poicing it’s just discarded as other functions are similar for policing.

Queuing techniques, algorithms and when to use them.

  • FIFO, First-in, first-out

Is the default queuing algorithm, and delivers packet in the same row it receives them, but could buffer them in between

  • PQ, Priority queuing

PQ gives priority to traffic over other traffic, each packet is placed into one of four queues: high, medium, normal, low. There is absolut preferential treatment over low-priority queues.

  • CQ, Custom queuing

is used to provide a garantied bandwidth, leaving the remaining bandwidth to other traffic. CQ does this by assigning a specific amount of queue space to each class of packet and then servicing the queues round-robin. PQ and CQ are statically configured. They don’t adapt network changes automatically.

  • WFQ, Flow-based weighted fair queuing

provides consistent response time to congested networks, each queue ist serviced on a bye counted base. Each time 1000 bytes are serviced, one stream with 2×500 bytes it qually serviced, like the 1×1000 byte packet. It’s mostly used on serial interfaces. WFQ is IP-precedence aware

  • CBWFQ, Class-based weighted fair queuing

CBWFQ is used to provide a minimum of bandwidth to a certain flow. It’s a garanteed amount of bandwidth. If it’s not used by the class other applications can use it.

Tools for congestion avoidance:

  • WRED  Weighted random early detection is to avoid congestion before it becomes a problem. It’s an algorithm to drop packets if congestion is about to occuring. Senders themself then slows down transmitions speed.

Sources:

http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/qos.htm

Popularity: 1% [?]

, , ,

ACE design / implementation / GNU

Feb 28th

Posted by Johnny in Cisco Design | 22 views

No comments

Most difficult thing is to implement the device into the customer network. This needs a lot of planning and discussions about the design and how it should be implemented.

The logic is, that you will mostly try to implement the ACE in between. From one VLAN into the other. The ACE will provide for VIP and VLAN interfaces to be the gateway for traffic back to the clients. Even bypassing the ACE is possible. This should be planned before and it should be clear at what point the device will be implemented.  It might be a good idea to have a good look at grown network struktures. While implementing the ACE it all depends on good understanding of te traffic flow and the current network infrastructure. The best is to communicate possible problems and catches.

ACE booting messages. Here you can see, there is some Linux/GNU code included in the ACE…

Unmounting done…
INIT: Switching to runlevel: 6
INIT: Sending processes the KILL signal
Rebooting… Rest
System Bootstrap, Version 12.2[120],
Copyright (c) 1994-2006 by Cisco Systems, Inc.
Slot 3 : Running DEFAULT rommon image …

ACE platform with 1048576 Kbytes of main memory

Loading disk0:c6ace-t1k9-mz.3.0.0_A1_6_2a.bin. Please wait ….
Uncompressing Linux…
Starting the kernel…
INIT: version 2.78 booting
Mounting Second Ramdisk ….
Second Ramdisk successfully mounted
Starting periodic command scheduler: cron.
Configuring network interfaces.
CF dump: Register callback functions
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/cf: 8 files, 24304/62532 clusters
FAT FS is ok
Compact Flash size 1000512(in 1k blocks) …
Core file size 204800
Available free size in cf is 611648 (in 1k blocks) …
set_coredump 2.11, 12 Mar 2005, FAT32, LFN
first_cluster = 0×608c num_cluster = 0×40 (64)
inserting procfs
inserting isan_kthread
inserting wiremod
inserting klib
inserting resdrv
inserting tlv
inserting sse
inserting kpss
inserting sdwrap
creating sdwrap device
inserting klm_tl
creating tl device
inserting klm_scp
inserting klm_mts
creating mts0 device
creating mtscfg0 device
inserting utaker
creating utaker0 device
creating utaker1 device
inserting sysmgr-hb
creating sysmgr-hb device
inserting modlock
creating modlock device
inserting bufmgr
inserting pkt_fifo
inserting encdec
creating encdec device
inserting pseudo
inserting drammap mod
creating drammap device
inserting ixp_dnld
creating ixp_dnld device
inserting sysdrv
creating sysdrv device
New registry installed.
INIT: Entering runlevel: 3
inserting i2c module
inserting ssa driver
inserting cde driver
inserting bf_dnld driver
inserting pfm_drv driver
inserting regaccess driver
inserting bf_nvram driver

Firmware compiled 24-Aug-07 17:47 by integ Build [26368]

ACE Daughter boards DB1 not present DB2 not present.
downloading fpga to cde 1

Read 3262456 bytes from ./cde1_core.bit
FPGA Date: 2007/ 9/13 Time: 3:38: 5

CDE 1 download successful
downloading fpga to cde 2

Read 2377744 bytes from ./cde2_core.bit
FPGA Date: 2007/ 8/15 Time: 20:59:47

CDE 2 download successful
FPGA Programming Done

CDE 1 revision ID 0403
CDE 2 revision ID 0402
enabling cde 0 interrupts
finished CDE setup

Configuring NP 1 Memory
Configuring NP 2 Memory
………………………..
Downloading NP 1 Image
………………………..
Downloading NP 2 Image
….. 0×40b214 (4239892) bytes downloaded

….. 0×40b214 (4239892) bytes downloaded

Loading Nitrox driver.
Writing register at address 3838 with e00
size = 8148
Ctx memory range(0×0000000-0×10000000)
Cleared 262144 1024-byte blocks in 5 requests.
Writing register at address 3898 with 1
Writing register at address 38b8 with 1

N2 SPI INIT PROGRAM.

Initializing Nitrox SPI1
configuring using falling clocks
Initializing CDE SPI registers
Nitrox init completed.
inserting IPCP klm
n2_perf_stats loaded
Waiting for NP handshake ……………………………………… Done
inserting IPCP klm
inserting cpu_util klm
Sleeping 10 secs… Done
Waiting for 3 seconds to enter setup mode…
No licenses installed…

Starting sysmgr processes.. Please wait…Done!!!

switch login:

Popularity: 1% [?]

, , ,
wordpress visitor