Hi; I'm working on the CUCM and have installed Cisco IP Communicator 8.6 on my laptop. my IP Communicator tries to register to the CUCM, but it is unsuccessful, because of the lack of knowledge about the TFTP server. my IP Communicator shows the wrong IP address as "default TFTP Server" and does not allow me to change the TFTP server IP address. actually all of the settings on the "Network" tab of the IP Communicator program is unchangable. why can't I configure the IP address of the TFTP server on IP Communicator Network tab? 

and another thing; can I configure CUCM (with the help of CUCM GUI, at the "System" Menu) as my DHCP and TFTP servers too? tnx. 

Today I passed my lab in Brussels... One of the greatest feeling of my life...

Ferenc Kuris

CCIE #46451

On AT Labs in the BGP communities. I dont think I understand why we need to configure R1, R3 and R6 with the route-map. After you configure R5 to send the community to neighbor R4. R4 will send that update with a local pref of 200 to R1 who is the RR and sends the best path to 6. Becuase the defualt local pref is 100 in ASN100 there isnt even a need to send the community to R3 from R5 and advertise that back into R1 with a Localpref of 100. It seems the minimal configureation that is needed here is to configure R5 to mark the communtiy and send that to R4. Then have R4 match with a community list and set the local pref to 200 and that should be it.

Becuase R5 does not need to send the comunity to R3 as the default local pref is 100 no other configuration is needed right? Am I missing something here? I think you would only need the route-map on R1, R3, and R6 if you wanted to perfer a lower than default local pref (for example 50) on the link between R4 and R5. This would force you to pass the communitiy to R3 so you can mark it lower than 50 and send that to R1 and thereby perfer the link between R4 and R5 right?

 R1

     Network          Next Hop            Metric LocPrf Weight Path

 *>i 112.0.0.0        155.1.45.5               0    200      0 200 54 50 60 i

 *                    155.1.13.3                             0 200 54 50 60 i

 *>i 113.0.0.0        155.1.45.5               0    200      0 200 54 50 60 i

 *                    155.1.13.3                             0 200 54 50 60 i

R6

     Network          Next Hop            Metric LocPrf Weight Path

  *   112.0.0.0        155.1.67.7                             0 300 54 50 60 i

 *>i                  155.1.45.5               0    200      0 200 54 50 60 i

 *   113.0.0.0        155.1.67.7                             0 300 54 50 60 i

 *>i                  155.1.45.5               0    200      0 200 54 50 60 i

R4

     Network          Next Hop            Metric LocPrf Weight Path

 *>  112.0.0.0        155.1.45.5                    200      0 200 54 50 60 i

 *>  113.0.0.0        155.1.45.5                    200      0 200 54 50 60 i

Hi,

Look at the image below people,i have set two static default routes on R3 overwriting the routes wich were installed by dhcp,my routes are like that:

ip route 0.0.0.0 0.0.0.0 189.20.0.1

ip route 0.0.0.0 0.0.0.0 200.200.200.1

R1 has the address 8.8.8.8 

R2 has the address  4.4.4.4

And dont have NAT configured on R3.

The problem: When i ping from R3 to 8.8.8.8 it works,but when i ping 4.4.4.4 from R3 it doesnot work because through debug i realised that the data are just flowing through R1 but the two routes with the same AD are on the routing table what is happening??

Image may be NSFW.
Clik here to view.

If i make the two routes like below the problem keeps on:

ip route 0.0.0.0 0.0.0.0 f0/0 189.20.0.1

ip route 0.0.0.0 0.0.0.0 f0/1 200.200.200.1

Enjoying i am making this post,when should i create static routes specifing the outgoing interface and the next hop as these last routes?

Dear All,

I have been using INE CCIE DC Rackrental for practicing UCS technology Labs but I am not able to finish the all the sections in the lab time allocated for me. For example my time ended after I finished the LAN connectivity section. Incase if I book the Lab, I do not want to start doing initial labs again that I did in my last rack session to continue doing other topics like SAN connectvity, creating Service profiles, OS installation, boot from SAN etc. 

Is there any way I can load the configs till the LAN connectivity section and then start working on rest of the lab sections during my rack time.

Hi guys,

I wanted to run capture on the R&S rack rental devices and export them to Wireshark. Same way as per Training videos either to VM host or my PC at home.

I tried to clear this with the INE support Team but think it was was getting lost in "translation".

A couple of questions if anyone knows please:

- Can you access the Whireshark VM host in the Rack rentals?

if not

- Is there a way to export the pcap files from the Rack rental devices to your PC at home. I dont think the labs are routable out to internet.

- Any other method is wellcome.

Thanks

Goncalo

going over ipsec nat-t

topology is simple

r1-------------r2-----------------r3

r2 does PAT for the ip address of r1.

I was trying to see the effect of disabling nat transversal on either r1 and r3, as per the documentation, since esp is stateless nat won't be done for it and r2 will drop the trafiic. But to my utmost surprise, the packet went true.

This is the show ip nat trans on r2

R2(config)#do sh ip nat tr
Pro Inside global      Inside local       Outside local      Outside global
esp 10.0.23.2:0        10.0.12.1:0        10.0.23.3:0        10.0.23.3:D8774F8A
esp 10.0.23.2:0        10.0.12.1:97FDBBBC 10.0.23.3:0        10.0.23.3:0

Is this expected? why is esp being natted. I though this was the motivation of tunneling esp over udp accross nat.

thanks.

Hello,

I have this setup:

PE1 router is connected to P1 router via single 1G Intf. P1 router is in turn connected to the P2 router via 8xSTM-1, and finally P2 is connected to PE2 via single 1G Intf

PE1--P1==P2--PE2

Now, this is how PE1 is seeing P1's MPLS-TE topology tree:

pe1#sh isis database verbose p1

  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.77
    Neighbor IP Address: 192.168.10.78
    Physical BW: 155520 kbits/sec
    Reservable Global Pool BW: 0 kbits/sec
    Global Pool BW Unreserved:
      [0]:        0 kbits/sec, [1]:        0 kbits/sec
      [2]:        0 kbits/sec, [3]:        0 kbits/sec
      [4]:        0 kbits/sec, [5]:        0 kbits/sec
      Image may be NSFW.
Clik here to view.:        0 kbits/sec, [7]:        0 kbits/sec

  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.81
    Neighbor IP Address: 192.168.10.82
    Physical BW: 155520 kbits/sec
    Reservable Global Pool BW: 0 kbits/sec
    Global Pool BW Unreserved:
      [0]:        0 kbits/sec, [1]:        0 kbits/sec
      [2]:        0 kbits/sec, [3]:        0 kbits/sec
      [4]:        0 kbits/sec, [5]:        0 kbits/sec
      Image may be NSFW.
Clik here to view.:        0 kbits/sec, [7]:        0 kbits/sec

  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.93
    Neighbor IP Address: 192.168.10.94
    Physical BW: 155520 kbits/sec
    Reservable Global Pool BW: 0 kbits/sec
    Global Pool BW Unreserved:
      [0]:        0 kbits/sec, [1]:        0 kbits/sec
      [2]:        0 kbits/sec, [3]:        0 kbits/sec
      [4]:        0 kbits/sec, [5]:        0 kbits/sec
      Image may be NSFW.
Clik here to view.:        0 kbits/sec, [7]:        0 kbits/sec

  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.85
    Neighbor IP Address: 192.168.10.86
    Physical BW: 155520 kbits/sec
    Reservable Global Pool BW: 0 kbits/sec
    Global Pool BW Unreserved:
      [0]:        0 kbits/sec, [1]:        0 kbits/sec
      [2]:        0 kbits/sec, [3]:        0 kbits/sec
      [4]:        0 kbits/sec, [5]:        0 kbits/sec
      Image may be NSFW.
Clik here to view.:        0 kbits/sec, [7]:        0 kbits/sec

  Metric: 13000      IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.15.61
    Neighbor IP Address: 192.168.15.62
    Physical BW: 1000000 kbits/sec
    Reservable Global Pool BW: 145000 kbits/sec
    Global Pool BW Unreserved:
      [0]:   145000 kbits/sec, [1]:   145000 kbits/sec
      [2]:   145000 kbits/sec, [3]:   145000 kbits/sec
      [4]:   145000 kbits/sec, [5]:   145000 kbits/sec
      Image may be NSFW.
Clik here to view.:   145000 kbits/sec, [7]:    15000 kbits/sec

  Metric: 13000      IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.189
    Neighbor IP Address: 192.168.10.190
    Physical BW: 1000000 kbits/sec
    Reservable Global Pool BW: 145000 kbits/sec
    Global Pool BW Unreserved:
      [0]:   145000 kbits/sec, [1]:   145000 kbits/sec
      [2]:   145000 kbits/sec, [3]:   145000 kbits/sec
      [4]:   145000 kbits/sec, [5]:   145000 kbits/sec
      Image may be NSFW.
Clik here to view.:   145000 kbits/sec, [7]:     5000 kbits/sec

  Metric: 10         IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.245
    Neighbor IP Address: 192.168.10.246
    Physical BW: 1000000 kbits/sec
    Reservable Global Pool BW: 145000 kbits/sec
    Global Pool BW Unreserved:
      [0]:   145000 kbits/sec, [1]:   145000 kbits/sec
      [2]:   145000 kbits/sec, [3]:   145000 kbits/sec
      [4]:   145000 kbits/sec, [5]:   145000 kbits/sec
      Image may be NSFW.
Clik here to view.:   145000 kbits/sec, [7]:    10000 kbits/sec

  Metric: 13000      IS-Extended p2
    Affinity: 0x00000000
    Interface IP Address: 192.168.10.161
    Neighbor IP Address: 192.168.10.162
    Physical BW: 1000000 kbits/sec
    Reservable Global Pool BW: 145000 kbits/sec
    Global Pool BW Unreserved:
      [0]:   145000 kbits/sec, [1]:   145000 kbits/sec
      [2]:   145000 kbits/sec, [3]:   145000 kbits/sec
      [4]:   145000 kbits/sec, [5]:   145000 kbits/sec
      Image may be NSFW.
Clik here to view.:   145000 kbits/sec, [7]:   145000 kbits/sec

As you see, 5 STM-1 with metric of 10 and 3 STM-1 with metric of 13000.

I'm trying to build up a TE tunnel with a BW of 125M from PE1 toward PE2:

pe1#sh run int tu12

Building configuration...

Current configuration : 319 bytes
!
interface Tunnel12
 ip unnumbered Loopback0
 tunnel source Loopback0
 tunnel destination 2.2.2.2
 tunnel mode mpls traffic-eng
 tunnel mpls traffic-eng priority 7 7
 tunnel mpls traffic-eng bandwidth  125000
 tunnel mpls traffic-eng path-option 1 dynamic
 tunnel mpls traffic-eng path-selection metric te
end

However, the tunnel doesn't come up because of this:

pe1#sh mpls traffic-eng tunnels tunnel 12
Name: pe1                 (Tunnel12) Destination: 2.2.2.2
  Status:
    Admin: up         Oper: down   Path: not valid   Signalling: Down
    path option 1, type dynamic

  Config Parameters:
    Bandwidth: 125000   kbps (Global)  Priority: 7  7   Affinity: 0x0/0xFFFF
    Metric Type: TE (interface)
    AutoRoute:  disabled  LockDown: disabled  Loadshare: 125000   bw-based
    auto-bw: disabled

  Shortest Unconstrained Path Info:
    Path Weight: 2010 (TE)
    Explicit Route: 192.168.10.17 192.168.10.246 192.168.50.74 2.2.2.2
  History:
    Tunnel:
      Time since created: 17 hours, 25 minutes
      Time since path change: 6 seconds
    Prior LSP:
      ID: path option 1 [6410]
      Removal Trigger: path error

Jan 21 12:25:18 CLT: Outgoing Path:
Jan 21 12:25:18 CLT:   version:1 flags:0000 cksum:DCAB ttl:255 reserved:0 length:212
Jan 21 12:25:18 CLT:  SESSION              type 7 length 16:
Jan 21 12:25:18 CLT:   Tun Dest:   2.2.2.2  Tun ID: 12  Ext Tun ID: 1.1.1.1
Jan 21 12:25:18 CLT:  HOP                  type 1 length 12:
Jan 21 12:25:18 CLT:   Hop Addr: 192.168.10.18 LIH: 0x36000418
Jan 21 12:25:18 CLT:  TIME_VALUES          type 1 length 8 :
Jan 21 12:25:18 CLT:   Refresh Period (msec): 30000
Jan 21 12:25:18 CLT:  EXPLICIT_ROUTE       type 1 length 36:
Jan 21 12:25:18 CLT:   192.168.10.17 (Strict IPv4 Prefix, 8 bytes, /32)
Jan 21 12:25:18 CLT:   192.168.10.162 (Strict IPv4 Prefix, 8 bytes, /32)
Jan 21 12:25:18 CLT:   192.168.50.74 (Strict IPv4 Prefix, 8 bytes, /32)
Jan 21 12:25:18 CLT:   2.2.2.2 (Strict IPv4 Prefix, 8 bytes, /32)
Jan 21 12:25:18 CLT:  LABEL_REQUEST        type 1 length 8 :
Jan 21 12:25:18 CLT:   Layer 3 protocol ID: 2048
Jan 21 12:25:18 CLT:  SESSION_ATTRIBUTE    type 7 length 28:
Jan 21 12:25:18 CLT:   Setup Prio: 7, Holding Prio: 7
Jan 21 12:25:18 CLT:   Flags: SE Style
Jan 21 12:25:18 CLT:   Session Name: pe1
Jan 21 12:25:18 CLT:  SENDER_TEMPLATE      type 7 length 12:
Jan 21 12:25:18 CLT:   Tun Sender: 1.1.1.1  LSP ID: 6412
Jan 21 12:25:18 CLT:  SENDER_TSPEC         type 2 length 36:
Jan 21 12:25:18 CLT:   version=0, length in words=7
Jan 21 12:25:18 CLT:   Token bucket fragment (service_id=1, length=6 words
Jan 21 12:25:18 CLT:     parameter id=127, flags=0, parameter length=5
Jan 21 12:25:18 CLT:     average rate=15625000 bytes/sec, burst depth=1000 bytes
Jan 21 12:25:18 CLT:     peak rate   =15625000 bytes/sec
Jan 21 12:25:18 CLT:     min unit=0 bytes, max pkt size=2147483647 bytes
Jan 21 12:25:18 CLT:  ADSPEC               type 2 length 48:
Jan 21 12:25:18 CLT:  version=0  length in words=10
Jan 21 12:25:18 CLT:  General Parameters  break bit=0  service length=8
Jan 21 12:25:18 CLT:                                          IS Hops:1
Jan 21 12:25:18 CLT:               Minimum Path Bandwidth (bytes/sec):125000000
Jan 21 12:25:18 CLT:                      Path Latency (microseconds):0
Jan 21 12:25:18 CLT:                                         Path MTU:1600
Jan 21 12:25:18 CLT:  Controlled Load Service  break bit=0  service length=0

Jan 21 12:25:18 CLT: Incoming PathError:
Jan 21 12:25:18 CLT:   version:1 flags:0001 cksum:0000 ttl:255 reserved:0 length:132
Jan 21 12:25:18 CLT:  SESSION              type 7 length 16:
Jan 21 12:25:18 CLT:   Tun Dest:   2.2.2.2  Tun ID: 12  Ext Tun ID: 1.1.1.1
Jan 21 12:25:18 CLT:  ERROR_SPEC           type 1 length 12:
Jan 21 12:25:18 CLT:   Error Node: 192.168.10.17
Jan 21 12:25:18 CLT:   Error Code: 24 (Routing Problem)
Jan 21 12:25:18 CLT:   Error Value: 0x5  (No route available toward destination)
Jan 21 12:25:18 CLT:   Flags: 0x0
Jan 21 12:25:18 CLT:  SENDER_TEMPLATE      type 7 length 12:
Jan 21 12:25:18 CLT:   Tun Sender: 1.1.1.1  LSP ID: 6412
Jan 21 12:25:18 CLT:  SENDER_TSPEC         type 2 length 36:
Jan 21 12:25:18 CLT:   version=0, length in words=7
Jan 21 12:25:18 CLT:   Token bucket fragment (service_id=1, length=6 words
Jan 21 12:25:18 CLT:     parameter id=127, flags=0, parameter length=5
Jan 21 12:25:18 CLT:     average rate=15625000 bytes/sec, burst depth=1000 bytes
Jan 21 12:25:18 CLT:     peak rate   =15625000 bytes/sec
Jan 21 12:25:18 CLT:     min unit=0 bytes, max pkt size=2147483647 bytes
Jan 21 12:25:18 CLT:  ADSPEC               type 2 length 48:
Jan 21 12:25:18 CLT:  version=0  length in words=10
Jan 21 12:25:18 CLT:  General Parameters  break bit=0  service length=8
Jan 21 12:25:18 CLT:                                          IS Hops:1
Jan 21 12:25:18 CLT:               Minimum Path Bandwidth (bytes/sec):125000000
Jan 21 12:25:18 CLT:                      Path Latency (microseconds):0
Jan 21 12:25:18 CLT:                                         Path MTU:1600
Jan 21 12:25:18 CLT:  Controlled Load Service  break bit=0  service length=0

Jan 21 12:25:18 CLT: Outgoing PathTear:
Jan 21 12:25:18 CLT:   version:1 flags:0000 cksum:E674 ttl:255 reserved:0 length:132
Jan 21 12:25:18 CLT:  SESSION              type 7 length 16:
Jan 21 12:25:18 CLT:   Tun Dest:   2.2.2.2  Tun ID: 12  Ext Tun ID: 1.1.1.1
Jan 21 12:25:18 CLT:  HOP                  type 1 length 12:
Jan 21 12:25:18 CLT:   Hop Addr: 192.168.10.18 LIH: 0x36000418
Jan 21 12:25:18 CLT:  SENDER_TEMPLATE      type 7 length 12:
Jan 21 12:25:18 CLT:   Tun Sender: 1.1.1.1  LSP ID: 6412
Jan 21 12:25:18 CLT:  SENDER_TSPEC         type 2 length 36:
Jan 21 12:25:18 CLT:   version=0, length in words=7
Jan 21 12:25:18 CLT:   Token bucket fragment (service_id=1, length=6 words
Jan 21 12:25:18 CLT:     parameter id=127, flags=0, parameter length=5
Jan 21 12:25:18 CLT:     average rate=15625000 bytes/sec, burst depth=1000 bytes
Jan 21 12:25:18 CLT:     peak rate   =15625000 bytes/sec
Jan 21 12:25:18 CLT:     min unit=0 bytes, max pkt size=2147483647 bytes
Jan 21 12:25:18 CLT:  ADSPEC               type 2 length 48:
Jan 21 12:25:18 CLT:  version=0  length in words=10
Jan 21 12:25:18 CLT:  General Parameters  break bit=0  service length=8
Jan 21 12:25:18 CLT:                                          IS Hops:0
Jan 21 12:25:18 CLT:               Minimum Path Bandwidth (bytes/sec):2147483647
Jan 21 12:25:18 CLT:                      Path Latency (microseconds):0
Jan 21 12:25:18 CLT:                                         Path MTU:-1
Jan 21 12:25:18 CLT:  Controlled Load Service  break bit=0  service length=0

However, you can see that P1=P2 connections has an interface which is 192.168.10.161 that can accomodate this BW requirement.

Do anyone has any idea?

Hi Please help me out regarding the difference between RD and RT.

As per documents they state RD will be mapped to bgp attribute to avoid duplicity of ip address because mp-bgp is the best protocol to carry routes between ce and pe.

RT is used to push the concerned routes into the proper VRF.

Here are my doubts:

Cant we use RD alone since it is also avoiding duplicity and making routes unique.

Please specify any good document for my basic understanding,how much ever i put in but i am getting lost some where.

any good document which refers packet level exposure.I am really thankfull.

I'm running ESXi ver 5.1 on a Dell with 2 Xeon quadcore 5530 with 72Gb of RAM.

I'm running two CSR1000v versions from my CCO download to try to get them to work:

csr1000v-universalk9.03.12.00.S.154-2.S-std.ova

csr1000v-universalk9.03.14.00.S.155-1.S-std.ova

Both of them boot properly, I can telnet in with SecureCRT.  Now the problem I have is when I type "?", it sits there.  I have to hit ENTER, then it just gives about 22 commands (through "dir") and goes back to privilege exec mode.

Another weird thing is if I type a command then ENTER, hit the UP arrow to recall the command I get this:

^[[A

I don't know what is going on with this.  Any suggestions are appreciated.  Thanks.

Hoping to get some expert advice regarding BGP filtering:

     neighbor x.x.x.x filter-list<as-path acl 1-500> in/out
     neighbor x.x.x.xprefix-list<prefix name> in/out
     neighbor x.x.x.x route-map<route-map name> in/out

I have become accustom to making route-maps for just about any filtering requirement.

I am wondering if there is a reason to prefer one of these other commands (filter-list or prefix-list), besides the convenience of less steps.   Order-of-operations?  Other considerations?     

Thanks for any clarification or reminders of issues to consider.

Hello folks, 

I have been running CSR1000v downloaded as a trial from cisco.com.

It really seems the initial setup and boot process was easy. I am using it with GNS3 v1.2.1.

However I have been running into lot of inconsistencies and crashes.

On VirtualBox, sometimes I launch the CSR1000v, I use GNS3 to  connect it via a link to Linux box for example and I can't ping each other no matter what I do (occasionally that works great).

On VMWare Workstation 10.0 (without GNS3), I ran the CRS1000v image "NATed" to  a Linux box. Connectivity is great, I can consistely ping each other fine. However after few minutes the CSR1000v reboots itself.

Anyone there has any better luck? Which Virtualization tool is more recommended to run the CSR1000v, VM Worstation or VirtualBox?

csr1000v-universalk9.03.14.00.S.155-1.S-std

I am slight confused by the default behaviour of OSPF when it comes to setting the on an Type7 LSA. My understanding is that when the P bit is set then the LSA7 can be translated back to LSA5 by any other ABR's further upstream. However in some videos I have watched I have seen it both set and turned off in examples where the NSSA-ONLY command hasnt been applied. So the question is -> Is the default behaviour to set P bit and allow LSA7 to LSA5 re-advertisement, or is the default behaviour to turn this off so that LSA7 cant be translated back to LSA5 to prevent loops?

Regards

Hello everyone,

Since the last changed introduced in the lab retake policy, if you fail 2 times a lab attempt you have to wait for 3 months to be able to sit again on your 3rd attempt; I have a question related to this.

Last year I tried (and failed) my first attempt on the CCIE Voice lab. After the change into collaboration I waited to feel prepared again and I'll take the collaboration lab next month. If I failed (I hope I won't ) would I have to wait 3 months or I'd be considered my first attempt since I have never tried to pass the collaboration lab before? Thanks,

Regards.

Hi I have gone through the ATC and looking for suggestions on my next step working towards my CCIE labs. I took the v4 Written exams last year. I plan on more reading and videos along the way but looking for ideas on starting with my practice labs. 

I have access to the following labs;

v4 Vol I - Advanced Technology Labs (Online)

v4 Vol II - Full-Scale Practice Labs (Online)

v4 Lab Workbook Vol III

v4 Lab Workbook Vol IV

v5 Lab Workbook

and will be using rack rentals from INE.

Any recommendations on how anyone worked towards their labs....I have seen discussions on Mock Lab and know that is probably needed further down the road when i am comfortable with the above labs and have scheduled an exam etc...Looking for some guidelines or ideas at this point. 

Thanks 

I just started working with a client that has an office in the US and an office in China. They are having issues with Chinas big firewall :) blocking access back to some of their sites.  Right now they have a site to site vpn setup from a Cisco ASA in China back to a Sonicwall in the US, and the interesting traffic defined to go over the vpn is the LAN to LAN traffic. 

Would it be as simple as adding internet networks to the interesting traffic acl on the China side to circumvent the China restrictions and have this traffic go over the vpn back to the US.  I don't think we would want all the Internet traffic, but at least include the sites they are having issues with.

I have been doing some quick google searches but I thought I would throw it out here as well to see how many others have run into this problem.

Hi; I'm working on the new "route-tag list" command. I have created this route-tag list to group all the tags between 10.10.10.0 to 10.10.10.255 and use it while redistribution. besides I have some routers to inject routes with other tags outside of this range. but it seems that the above rote-tag list does not work at all, because all of the routes are redistributed despite having different tags. my IOS version is "C7200-ADVENTERPRISEK9-M, Version 15.2(4)S". is it a bug on this version or I misunderstood the route-tag list command?!

route-tag list LIST1 seq 5 permit 10.10.10.0 0.0.0.255

this is a reference link for route-tag list command:

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_eigrp/configuration/xe-3s/ire-xe-3s-book/ire-en-rou-tags.html

I just started on the AT RIP labs, and noticed that the provided initial configs (initial rip & basic rip) use 169.254.100.0/24 addresses for the dmvpn cloud.  Not a huge problem, since we can either add that network to the rip configuration, or change the interface addresses.  Just thought I should point it out, since the lab workbook doesn't make it clear which approach is appropriate.

I'm having a great deal of difficulty with it, not in the sense of having trouble with the material, but in the sense "these configs are broken, and the text doesn't match either the starting configs, or the diagrams, and sometimes both". So I'm wondering if I'm doing it wrong, somehow or if this workbook was just rushed out the door.

In general, between this and cancelling my scheduled class at the very last minute (seriously the last minute, when I spoke to customer service on Friday afternoon they didn't tell me that the class had been cancelled, even though it turns out the email went out at 11:00am CT) I'm more and more concerned about the reliablity of this material. INE has an excellent reputation, but I'm aside from the video course itself I've had nothing but problems and disappointments (and in the case of the cancelled class, behavior that is so unprofessional I find it hard to forgive: I can't concieve of any circumstances or difficulties that make that last minute notification and extensive delay in providing a replacement acceptable; besides the cost of the class I'm out my consulting income for the time I took of, which is a non-trivial amount of money).

Hi All,

I just had to install some new DRAM for a 2951.  After installation, I just have some queries from the #sh cmd's.  I have put two 2GB DRAM sticks in (i.e. 4GB total).

So in the sh ver output, I added the bold figures together and got 2097152 Kilobit's = 256MB's.  I don't really understand why it would only show 256MB when 4 gig is installed?

Router#sh ver | i mem

Cisco CISCO2951/K9 (revision 1.1) with 2054144K/43008K bytes of memory.

255K bytes of non-volatile configuration memory.

In the below output, the bold numbers is about 2 GB.  Am I missing something here?  Where is the full 4GB?

Router#sh mem sum

                Head    Total(b)     Used(b)     Free(b)   Lowest(b)  Largest(b)

Processor   139C5BFC   1849181188   61152812   1788028376   680470312   1049089444

      I/O   3D600000    44040192    38044280     5995912     5955060     5941244