Finished IEWB IP Routing
by David Sudjiman ~ June 30th, 2009Well, finished IEWB IP Routing, moving forward to RIP…
Well, finished IEWB IP Routing, moving forward to RIP…
I thought I was going to use this for one of the client but unfortunately it is only available for IOS above 12.4(20)T.
Object-Group gives you a solution to make your ACL looks much cleaner and nicer and easier to read by substituting those IP addresses and even the services into an object.
Finished IEWB Frame Relay and moving to IP Routing.
There is a command we need to apply to switch the card module to E1 or T1 and this is the first thing you need to do before configuring the interface.
Router(config)#control? control-plane Router(config)#card type ? e1 E1 t1 T1 Router(config)#card type e1 ? <0-2> Card slot number (always 0 for 1800 series & 2801 routers) Router(config)#card type e1 0 1 Router(config)#control? control-plane controller Router(config)#controller E1 ? <0-0> Controller slot number Router(config)#controller E1 0/1/0 Router(config-controller)#
and it was REALLY hard to find this info if you using words like “configure vwic-1mft-t1/e1 2821″ and without knowing that you need to apply this command.
I was impressed with the presentation of Cisco WCS 6.0 today. The WCS has a lot of enhancements including heaps of configurable reporting and web page presentation. The web page presentation feels like an iGoogle on steroids and fully customizable on what kind of information you want to present. You can even use Google Earth combined with the Location feature.
For this particular web design, I think Cisco just get it right. Compare this WCS 6.0 with Cisco CallManager!
Apart from the presentation upgrade, there are lots of new feature included OfficeExtend that enables you to bring the Cisco AP home and this AP will remotely connect to office thus giving you an encrypted tunnel from the CIsco AP to office.
ClientLink is also a great feature to automatically focus the RF beam to particular area to increase performance.
Complete new features below (taken from Cisco.com)
Source:
Release Notes for Cisco Wireless Control System 6.0.132.0 for Windows or Linux
I’ve done Frame-Relay IEWB a really long time ago yet I keep forgetting why I should use frame-relay interface-dlci or frame-relay map. Reading the Cisco IOS Wide-Area Networking Configuration Guide, Release 12.4T gives you the explanation and I decided to post it here to help me remember.
For point-to-point subinterfaces, the destination is presumed to be known and is identified or implied in the frame-relay interface-dlci command. For multipoint subinterfaces, the destinations can be dynamically resolved through the use of Frame Relay Inverse ARP or can be statically mapped through the use of the frame-relay map command.
We know that on Frame Relay relies on the mapping between DLCI to IP Address and this is done by using Inverse ARP. We also know that without using dynamic mapping, we can also use static mapping using command frame-relay interface-dlci or frame-relay map.
The different between the two is that frame-relay interface-dlci is used for point-to-point subinterfaces and frame-relay mapis used for multipoint subinterfaces.
The logic behind it is basically in point-to-point network the next-hop is always known and whatever the interface thrown at will be passed to the next-hop. All we need to do is to define what the interface DLCI number is.
For multipoint subinterfaces, the situation is different. One subinterface faces multiple end-points. Therefore, there is a need to define which DLCI mapped to which IP Address.
Frame Relay does not natively support features such as authentication, link quality monitoring, and reliable transmission. Based on this it is sometimes advantageous to encapsulate an additional PPP header between the normal layer 2 Frame Relay encapsulation and the layer 3 protocol. By running PPP over Frame Relay (PPPoFR) we can then implement authentication of Frame Relay PVCs, or even bind multiple PVCs together using PPP Multilink.
PPPoFR is configure in Cisco IOS through the usage of a Virtual-Template interface. A Virtual-Template is a PPP encapsulated interface that is designed to spawn a “template” of configuration down to multiple member interfaces. The traditional usage of this interface has been on dial-in access servers, such as the AS5200, to support multiple PPP dialin clients terminating their connection on a single interface running IP.
Complete article from Internetwork Expert.
Below are a couple example configurations for PPPoE. Note that you can run into MTU issues when trying to use OSPF over PPPoE. This can easily be resolved by using the “ip ospf mtu-ignore” command as the dialer interface’s MTU is 1492 while the virtual-template’s (virtual-access) MTU is 1500.
Well, kinda finished. I need to redo some weak spots such as dot1q tunneling, MST, PPPoE, Protected Ports, Flex Link, Fallback Bridging, and Private Vlan which I couldn’t really do it because the remote lab is full booked until Saturday.
I’ve been spending 7 6-hour sessions just to practice over and over for this workbook. I know, It’s kind of over doing it but I’m glad that I’m making sure I got a good grab for each subjects on the workbook.
Every Saturday I dedicated to 12-hour lab and for each day I dedicated at least 2-hour for reading or doing another lab.
I’ve read most of the subjects on Catalyst 3750-E and 3560-E Switch Software Configuration Guide, 12.2(50)SE. I actually intended to read all of them but I think I would be better of reading from another sources for subjects like DHCP, EEM, QOS, etc. I can always go back to this doco when I need them. At least I’ve read all of the Layer 2 subjects on this doco.
And yes, I had those moments when my brain just couldn’t take anything anymore. Well, a 12-hour sleep will do the trick to rest it, at least for now.
Moving on to the next chapter, Frame Relay.
My mind is not getting any satisfaction tonight. This is actually my cooling down after 6 days of working and study and I really can’t take it anymore. I’ve been resuming my study starting it all over again since the last three weeks yet seems It’s getting harder just to read few more pages of Cisco Documentation.
For the last three weeks I’ve been reading 3750 Software Configuration Guide and trying to nail down anything that seems unknown for me. I guess that’s just pretty much reading cover to cover for everything.
I don’t know how I can recover from burning out yet a day of not doing study scares me as I can’t afford to forget something.
Sleeping doesn’t help and ceasing to study is not an option. I guess I just have to keep pressing on…