Re: [c-nsp] XR on GNS3

2018-05-31 Thread Tim Warnock
> XRv is simple control-plane of XR in a VM. This is why L2 forwarding isnt
> supported (though is configured).
> XRv9000 is full control- and data-plane and much tighter coupling of the two.
> L2 forwarding should work, but L2VPNs and such will fail miserably.
> 
> q.

XRv9000 6.4.1 works fine - the next issue is that the forwarding plane is 
limited to 128kbps without a licence...
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] XR on GNS3

2018-05-31 Thread quinn snyder
XRv is simple control-plane of XR in a VM. This is why L2 forwarding isnt 
supported (though is configured). 
XRv9000 is full control- and data-plane and much tighter coupling of the two. 
L2 forwarding should work, but L2VPNs and such will fail miserably.  

q. 

--
quinn snyder | snyd...@gmail.com

-= sent via iphone. please excuse spelling, grammar, and brevity =-

> On May 31, 2018, at 14:25, Aaron Gould  wrote:
> 
> I used XRv in GNS3 I think I used both 5.1.1 and 5.3.0 ... I recall getting
> some good use out of it.
> 
> I'm not a systems guy, so climbing the learning curve and asking for help
> from the communities online was what I had to do in order to figure out how
> to get it show up inside the GNS3 app (used virtual box, and recall ova,
> vmdk, qemu, etc, etc)  then it was useable and working.  I also did
> Juniper Olive/vMX.
> 
> A couple things
> 
> I don't think I ever got the Layer 2 forwarding to work.  L3 routing worked
> and packets would flow... but L2 bridging and MPLS Layer 2 type things I
> don't think I ever got to properly flow.
> 
> I also would have to bounce interfaces using a batch file anytime I
> restarted gns3 or even if I added a new instance of XRv... so because of
> that, I would never reboot my windows vm that it was all contained inside
> and tried not to close gns3 app
> 
> -Aaron
> 
> 
> ___
> cisco-nsp mailing list  cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] XR on GNS3

2018-05-31 Thread Aaron Gould
I used XRv in GNS3 I think I used both 5.1.1 and 5.3.0 ... I recall getting
some good use out of it.

I'm not a systems guy, so climbing the learning curve and asking for help
from the communities online was what I had to do in order to figure out how
to get it show up inside the GNS3 app (used virtual box, and recall ova,
vmdk, qemu, etc, etc)  then it was useable and working.  I also did
Juniper Olive/vMX.

A couple things

I don't think I ever got the Layer 2 forwarding to work.  L3 routing worked
and packets would flow... but L2 bridging and MPLS Layer 2 type things I
don't think I ever got to properly flow.

I also would have to bounce interfaces using a batch file anytime I
restarted gns3 or even if I added a new instance of XRv... so because of
that, I would never reboot my windows vm that it was all contained inside
and tried not to close gns3 app

-Aaron


___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


[c-nsp] XR on GNS3

2018-05-31 Thread Ahsan Rasheed
Hi All,

I am looking for help. I want to use XR IOS any router on GNS3.  Anyone
ever used & any issues? I would be really appreciate any prompt help. I
have Laptop Core i7 with 16 GB RAM on it.

Also What XR IOS need to use?

Much appreciate for prompt reply.


Thanks & Regards,
Ahsan Rasheed
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] 3750 and CVE-2018-0167

2018-05-31 Thread Brian Turnbow
Hi Sebastian,

We don't use lldp, but you can turn it off on an interface by interface
bassis.
Why run it on ports with devices outside of your control?


Brian




> -Original Message-
> From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of
> Sebastian Beutel
> Sent: mercoledì 30 maggio 2018 17:52
> To: cisco-nsp@puck.nether.net
> Subject: [c-nsp] 3750 and CVE-2018-0167
>
> Dear list,
>
> we're still having some Cat 3750 in operation and it will still take
some time
> till we can retire the last ones. We've asked Cisco whether they are
planning
> to publish a new software image for this platform that fixes
> CVE-2018-0167 despite the fact that the product is way beyond end of
> security and vulnerability support.
> Our Cisco representative stated that they are not planning to do so
despite
> the severity of the bug. He also said we're the only customer having
this issue.
> So my question is: If you're still running 3750s, how do you deal with
this?
>
> Best,
>Sebastian.
>
> P.S.: Cisco's advisory:
>
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisc
o-
> sa-20180328-lldp
> ___
> cisco-nsp mailing list  cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] 3750 and CVE-2018-0167

2018-05-31 Thread Antoine Monnier
we are not running LLDP so we should be ok on that platform

On Wed, May 30, 2018 at 5:52 PM, Sebastian Beutel <
sebastian.beu...@rus.uni-stuttgart.de> wrote:

> Dear list,
>
> we're still having some Cat 3750 in operation and it will still take
> some time till we can retire the last ones. We've asked Cisco whether they
> are planning to publish a new software image for this platform that fixes
> CVE-2018-0167 despite the fact that the product is way beyond end of
> security and vulnerability support.
> Our Cisco representative stated that they are not planning to do so
> despite the severity of the bug. He also said we're the only customer
> having
> this issue. So my question is: If you're still running 3750s, how do you
> deal with this?
>
> Best,
>Sebastian.
>
> P.S.: Cisco's advisory:
> https://tools.cisco.com/security/center/content/
> CiscoSecurityAdvisory/cisco-sa-20180328-lldp
> ___
> cisco-nsp mailing list  cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/