| Sunday | |||
|---|---|---|---|
8:00 AM
5:00 PM
| TECCOM-2001 | Cisco Unified Computing System Technical Day | |
| Monday | |||
8:00 AM
9:30 AM
| BRKNMS-2658 | Securely Managing Your Networks with SNMPv3 | |
10:00 AM
12:00 PM
| BRKSEC-3021 | Maximizing Firewall Performance | |
1:00 PM
3:00 PM
| BRKRST-2335 | IS-IS Network Design and Deployment | |
| Tuesday | |||
8:00 AM
9:30 AM
| BRKRST-2310 | Deploying OSPF in a Large-Scale Network | |
10:00 AM
11:30 AM
| GENKEY-4346 | Keynote and Welcome Address | |
12:30 PM
2:30 PM
| BRKARC-3470 | Cisco Nexus 7000 Switch Architecture | |
4:00 PM
6:00 PM
| BRKSEC-4054 | DMVPN Deployment Models | |
| Wednesday | |||
8:00 AM
9:30 AM
| BRKSEC-3013 | Advanced IPSec with FlexVPN and IKEv2 | |
10:00 AM
11:30 AM
| GENKEY-4347 | Cisco Technology Keynote | |
12:30 PM
2:30 PM
| BRKSPG-2402 | Best Practices to Deploy High-Availability in Service Provider Edge and Aggregation Architectures | |
FabricPath is Cisco's proprietary, TRILL-based technology for encapsulating Ethernet frames across a routed network. Its goal is to combine the best aspects of a Layer 2 network with the best aspects of a Layer 3 network.
An article on FabricPath could go into a lot of detail and be many pages long but I'm going to concentrate on five facts that I found particularly interesting as I've learned more about FabricPath.
In my last article I discussed the components of Openflow and building blocks of a Software Defined Network. In this part, let me discuss some of the things people are doing to make it all work. One of the pieces that needs to be discussed beforehand is the various ways in which a packet can be matched against a flow and what kind of actions can be taken.
A flow is a simple mechanism to identify a group of packets on the wire. So a packets coming from a particular machine can be identified by the machines MAC or IP addresses which appears as source MAC in L2 header or source IP in L3 header. By putting a flow rule around either of those fields and just counting the packets going through the switch that hit that rule, we can determine the number of packets being sent by the machine. Its useful information. To make it more useful, one could add another flow to measure the packets going to our target machine. Adding a destination MAC or destination IP rule based on the machines Continue reading
One of the latest features on the Juniper MX-series devices is the BRAS functionality. The first functionality (automatically configuring interfaces) has been available since a long time, but most BRAS features have been introduced last year in JUNOS 11.x releases. With JUNOS 11.4 (also a Long-Term-Support release) the features matured as all major components are now available and (fingers crossed) stable.
This functionality can be named in different ways. BRAS or Broadband Remote Access Server is the most common name. Other names are Broadband Network Gateway (BNG) or Broadband Service Router (BSR).
This functionality is used in Internet Service Provider environments usually where DSL or Cable is used as the last mile access.
The following drawing demonstrates how the end-to-end path looks and where a BRAS/BSR is placed.
The CPE (DSL/Cable modem) is connected to the Multi-Service Access Node (MSAN), this MSAN is either a DSLAM in case of DSL networks or a CMTS in case of Cable networks. The DSLAM and CMTS devices convert the signal to Ethernet (or any other transport) and forward it to the rest of the network. This connection is then terminated on a BRAS device before it enters the rest of the Continue reading