[c-nsp] cisco-nsp Digest, Vol 177, Issue 30

[MuBeX]

ee

On Aug 24, 2017 12:00 PM, <cisco-nsp-request at puck.nether.net> wrote:

Send cisco-nsp mailing list submissions to
        cisco-nsp at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://puck.nether.net/mailman/listinfo/cisco-nsp
or, via email, send a message with subject or body 'help' to
        cisco-nsp-request at puck.nether.net

You can reach the person managing the list at
        cisco-nsp-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-nsp digest..."


Today's Topics:

   1. Etherchannel QOS support on ISR4K (Chuck Church)
   2. Policy based routing on tag interfaces
      (Arne Larsen  / Region Nordjylland)
   3. cisco 3850 eigrp - sending goodbye - can't ping any
      224.0.0.10 (Aaron Gould)


----------------------------------------------------------------------

Message: 1
Date: Thu, 24 Aug 2017 08:55:46 -0400
From: Chuck Church <chuckchurch at gmail.com>
To: NSP - Cisco <cisco-nsp at puck.nether.net>, Chuck Church
        <chuck.church_ext at michelin.com>
Subject: [c-nsp] Etherchannel QOS support on ISR4K
Message-ID:
        <CAGG7VudttYMBM01TEqiNaGWu+QFEd3N8d_coyJ8ZtQdb1wZMUA at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

All,

       I've been looking everywhere for a definitive doc on Ingress QOS
service-policy support.  All the docs I've found on Cisco's site seem to
mentions IOS-XE 3, but seem to be ASR1K specific.  Can't seem to find any
etherchannel docs for ISR4K specifically.  Upon trying to apply an ingress
policy on a 4K port channel int (main int has IP address, no subints), the
error message "service-policy input COS-IN not supported on this target" is
displayed. It's a 4451-X running 3.13.3. Port channel config looks like
this:
interface Port-channel1 description HJ102530 Customer LAN ip address
10.x.y.2 255.255.255.252 no ip proxy-arp ip flow monitor netflow input ip
flow monitor netflow output ip tcp adjust-mss 1432 no negotiation auto

Now I did find in this doc:
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_mqc/
configuration/xe-3s/qos-mqc-xe-3s-book/qos-eth-int.html#
GUID-AD7EB461-CAD5-463F-9F0D-4486D327D049

reference to these commands: port-channel load-balancing vlan-manual
or load-balancing
vlan (on interface)

This router is ISP-owned so I'd like to find out the definitive answer
prior to having them try something.  Anyone know the real deal with QOS and
4K?

Thanks,

Chuck


------------------------------

Message: 2
Date: Thu, 24 Aug 2017 15:16:32 +0000
From: "Arne Larsen  / Region Nordjylland" <arla at rn.dk>
To: "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>
Subject: [c-nsp] Policy based routing on tag interfaces
Message-ID:
        <27D6442795536C4487F130C87A9F9F269642FCFE at ithexc02.aas.its.nja.dk>
Content-Type: text/plain; charset="us-ascii"

Hi all

Can someone give me a hint about how to do policy based routing on PE node
in and MPLS network.
We have to change our internet access to a new service provider, and we
would like to do it as smoothly as possible.
The problem is that our old firewalls are located in an mpls vpn and all
ingress interfaces is tag switched.
Is there a way to do PBR on an incoming mpls interface.
Any suggestions would be appreciated
The setup is like the drawing

                                                          (P.node)
                              (P.node)

               |
                         |

               |
                         |

               |                                                        |

               |
                         |


           (PE.node)                                      (PE.node)

           vrf0| hsrp               vrf0 | hsrp

                |                         Same Layer2     |

                -----------------------

                |
                          |

           (Old.fw)                                        (New.fw)

               |
                         |

               |
                         |

           (Old. at net)                                  (New. at net)



/Arne



------------------------------

Message: 3
Date: Thu, 24 Aug 2017 10:47:35 -0500
From: "Aaron Gould" <aaron1 at gvtc.com>
To: <cisco-nsp at puck.nether.net>
Subject: [c-nsp] cisco 3850 eigrp - sending goodbye - can't ping any
        224.0.0.10
Message-ID: <001301d31cf0$4e97db20$ebc79160$@gvtc.com>
Content-Type: text/plain;       charset="us-ascii"

I was just working with a customer that has a 3850 - 24 port that
continually sends goodbye tlv every 80 seconds



He also has a 3850 48 port that works fine



The 3850 24 port can NOT ping 224.0.0.10 at all

The 3850 48 port can ping 224.0.0.10 and gets responses from all the eigrp
neighbors on the vlan



Router eigrp 1 configs are same



- Aaron Gould





------------------------------

Subject: Digest Footer

_______________________________________________
cisco-nsp mailing list
cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp

------------------------------

End of cisco-nsp Digest, Vol 177, Issue 30
******************************************