26 May

E-OAM loopback on ASR9k

There are two things that we have to do to enable E-OAM: configure oam profile that will define way OAM will work and attach that profile to physical interface. OAM’s are not working on subinterfaces. In action section you define what action will router take when particular error occurs, in this example interface will be put in err-disable state.
Read More

11 May

Creating EoMPLS on ASR9k

Process of defining E-Line connections, either local or as EoMPLS, consists of two steps – creation of EFP’s (Ethernet Flow Point) and defining xconnect between them. Each EFP represents one customer service demarcation point and can be in example physical subinterface or bundle. Connection between EFP’s can be either local, if both ESP’s are in the same chassis (same or different line cards) or EoMPLS link.
Read More

29 Apr

Virtual IP, MgmtEth interfaces and switchover on ASR9k

On ASR9000 router you have two RSP’s, both with MgmtEth0 interfaces. Interfaces on both of RSP’s have to be in the same subnet, what more a Virtual IP address, that is in the same subnet as MgmtEth0’s interfaces have to be configured. So technically you may think that you have three out-of-band management entry points to the router. This is unfortunately false.
Read More

27 Apr

Getting familiar with IOS XR

I’m getting familiar with ASR9k routers and IOS XR right now at the training in Cisco HQ. IOS XR is different. It’s modular, it have slightly different fordesigns that traditional IOS or IOS XE, which is more or less IOS converted as a Linux process on ASR1k.
For those familiar with JunOS CLI and programming new IOS XR might be easier to use than traditional IOS CLI. You can prepare your configuration ahead, review it and commit all the changes at once. To bad Cisco didn’t implement commit check command like on JunOS that let you test if configuration that you’re going to commit is consistent. Another big disadvantage – when you execute show configuration changes diff you can see changes that will be made to running-config when you commit your changes. Diff looks quite similar to one you know from UNIX platforms. Except the fact that both lines that will be unchanged or removed are preceded with “-“, while lines that be added to configuration are preceded with “+”. Not really clear to tell what you remove and what not. But you can always perform show configuration changes to look how your configuration will look like after commit.