Messages

I've been away for awhile.

At this point we have decided no to use IWAN. We are currently planning a PoC with Versa. I'm going to be doing an onsite hands session with them to go over design, operation, configuration, troubleshooting, etc. If things don't work out we discussed taking the time to do a full lab of IWAN. Also there is a book coming out from Cisco Press on IWAN next month. I pre-ordered figuring it can't hurt whether we use it or not.

Hmm I must have missed them.

Pretty cool. You guys need an access switch lineup so I can play too.

Wasn't on my goal list but my previous employer had me scheduled to go to LogRhythm training a couple months ago. So I took the test a few weeks back and I'm a LogRhythm Certified Professional now 

We did a look at those vendors, I think we settled on Riverbed.

Do you know what product you guys got? We weren't very impressed with them. Especially when they laughed at being priced higher than Cisco for WAN Op.

Interesting. We talked to Riverbed and thought they were way to young. The product they showed us last week was acquired earlier this year.

IWAN makes sense for us because we already have two routers at each location  (MPLS & DMVPN). Cisco is supposed to be getting us some demo gear in a couple weeks. I'm hoping to get a working config using the CSR1000V before that though. If I can get it working we have a site going live at the end of the month that I have proposed using it on.

Versa is being pitched to us by two different companies we do business with, one as a manage service and the other as a managed service with us having access. So we are looking at them on our own as well.

Talari meeting is in an hour so I'll know more about them soon but I keep reading that they are the only proven name with over 100 site deployments.

Currently involved in Phase 1 of a POC with Cisco IWAN using APIC-EM and Cisco Prime/LiveAction.  Phase 2 would add WAAS.  About to also POC Riverbed.  We spoke with Talari and Fatpipe before deciding to POC Riverbed.  We should be getting our Riverbed POC hardware tomorrow but I won't be able to see until later in the week nor have we come up with a network digram of where everything should be placed yet.  So it might be next week before I can speak more about it.

How are you liking IWAN? I hear so many negative things about how long it takes to configure but once you do it seems to be cookie cutter. Did you not like Talari?

So I've been absent from here for a bit. I got a new job a month ago. Former employer that had no upward mobility 8 years ago, cleaned house and is bringing network support in house for the first time ever. I'm the first engineer on board with two network admins that handle the servers with maybe more engineers later on. Gets me back home too, I'm moving back to Oregon this week and couldn't be happier 

Anyways I've had to do some research into SD WAN at a previous place so I've got some exposure to it. Right now looking through vendors, doing demos, etc. We have about 130 sites and growing. Management is sure they want some sort of SD WAN solution. Problem I have is most of them are young unproven companies. I've looked at Silver Peak, Versa, Riverbed, waiting on a demo with Talari. I've started working on an IWAN lab to look into it. Anyone else doing the same or already done it?

I fired the VM back up and here is my routing table on DSW1.

Code Select Expand

SW1#show ipv6 route
IPv6 Routing Table - default - 8 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
       B - BGP, M - MIPv6, R - RIP, I1 - ISIS L1
       I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
       EX - EIGRP external, ND - Neighbor Discovery
       O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
R   2026::1:0/122 [120/3]
     via FE80::A8BB:CCFF:FE00:410, Ethernet0/1
C   2026::2:0/122 [0/0]
     via Ethernet0/1, directly connected
L   2026::2:2/128 [0/0]
     via Ethernet0/1, receive
C   2026::3:0/122 [0/0]
     via Ethernet0/0, directly connected
L   2026::3:1/128 [0/0]
     via Ethernet0/0, receive
R   2026::12:0/122 [120/3]
     via FE80::A8BB:CCFF:FE00:410, Ethernet0/1
R   2026::34:0/122 [120/3]
     via FE80::A8BB:CCFF:FE00:410, Ethernet0/1
L   FF00::/8 [0/0]
     via Null0, receive


I replicated the setup in IOU and am able to ping both ways from R1 to DSW2 and from DSW2 to R1. My configs are very basic and not any different from what I see you have. Redistribution is setup the same as you have. My routing table is below, it looks like you are missing routes form Area 12 as well on R3.

Code Select Expand

R3#show ipv6 route
IPv6 Routing Table - default - 8 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
       B - BGP, M - MIPv6, R - RIP, I1 - ISIS L1
       I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
       EX - EIGRP external, ND - Neighbor Discovery
       O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
C   2026::1:0/122 [0/0]
     via Ethernet0/1, directly connected
L   2026::1:2/128 [0/0]
     via Ethernet0/1, receive
OE2 2026::2:0/122 [110/20]
     via FE80::A8BB:CCFF:FE00:400, Tunnel0
OE2 2026::3:0/122 [110/20]
     via FE80::A8BB:CCFF:FE00:400, Tunnel0
OI  2026::12:0/122 [110/20]
     via FE80::A8BB:CCFF:FE00:210, Ethernet0/1
C   2026::34:0/122 [0/0]
     via Tunnel0, directly connected
L   2026::34:1/128 [0/0]
     via Tunnel0, receive
L   FF00::/8 [0/0]
     via Null0, receive


Can you post the relevant config?

This link might also have something to go on https://supportforums.cisco.com/discussion/10499076/vrf-importexport-how-filter-routes

This is a good doc for comparison.
http://www.cisco.com/c/en/us/support/docs/quality-of-service-qos/qos-policing/19645-policevsshape.html

Something else to keep in mind are the byte sizes of the packets. They can affect how the policy works. On some platforms a smaller byte size packet can actually far exceed the policer. On most Cisco platforms I've found it to be fairly accurate though.

Completely awesome!

Maybe we can rename this forum to ciscowritesshittysoftwarewhathappenedtotheirQA.com

I think you misspelled bradreese.com. 

LOL

I've had a few recruiters like this and it drives me crazy. If the job and technology are worth it to you stick it out.