We typically do loaded 2 post racks with Cat 3k's in 4 or 6 member stacks. We used to do 2' cables and Neat Patches but lately have been doing 6" cables with no organizers (more dense, works pretty well, very easy to trace when vetting documentation). It get us about 6 switches per rack, 100% patched. There's an idea to do chassis based switches in the IDFs now (Cat9400) and I'm interested in hearing from folks on the contrast between the two. Seems like a lot of cables but we can always hire someone to do that. Which do you like more and why? If going chassis, what are some things to keep in mind or avoid?
Wednesday, February 7, 2018
Looking at NCCM
We recently went into a merger and we now have around 300 sites to manage with about 30k end users. Boss man seems to "finally" understand that we are a big shop now and says that we have budget for enterprise level tools.
The network is made up of different vendors (Cisco, Brocade, HP, etc.)
What do you guys recommend for NCCM (Network configuration and change management)?
In the past I've used Cisco Prime Infrastructure and liked it but that's not multi vendor better tools are possibly be out there.
I know of SolarWinds and ManageEngine solutions but I've been out of the loop since we never had the funds for these types of solutions.
What is out there and what do you recommend?
Cisco 7600 VPLS Configuration Help
At my shop we're trying to setup VPLS on our Cisco 7600 series (Yes they are EOL as fuck but support is still good and cheap spare parts are aplenty). We use OSPF for our MPLS core and already just do straight L2 xconnects so VPLS didn't seem that far off of a dream. Unfortunately that dream has seemed to died.
I'm setting up between three 7600's to create this tunnel with the following:
7600 1.1.1.1 l2 vfi Phones manual vpn id 231 neighbor 1.1.1.3 encapsulation mpls neighbor 1.1.1.6 encapsulation mpls
7600 1.1.1.6 l2 vfi Phones manual vpn id 231 neighbor 1.1.1.3 encapsulation mpls neighbor 1.1.1.1 encapsulation mpls
7600 1.1.1.3 l2 vfi Phones manual vpn id 231 neighbor 1.1.1.1 encapsulation mpls neighbor 1.1.1.6 encapsulation mpls
On each 7600 we have this in the interface VLAN config:
interface Vlan231 description Phones no ip address xconnect vfi Phones end
Then we trunk that out to the ports needed as a standard VLAN. The Xconnect comes up and everything shows fine that I can diag.
1.1.1.1_7609#show mpls l2transport vc 231 Local intf Local circuit Dest address VC ID Status ------------ -------------------- --------------- ---------- ---------- VFI Phones VFI 1.1.1.3 231 UP VFI Phones VFI 1.1.1.6 231 UP 1.1.1.1_7609#show vfi name Phones Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No VFI name: Phones_DVS, state: up, type: multipoint VPN ID: 231 Local attachment circuits: Vlan231 Neighbors connected via pseudowires: Peer Address VC ID S 1.1.1.3 231 Y 1.1.1.6 231 Y
Now on the switches at each location, we've tried running a ping between but getting failures. Also if I throw a VLAN on the int vlan on two of the 7600's, it fails to reach the other 7600.
Any ideas and suggestions would be appreciated, thank you!
How to send a custom packet?
I want to cheat in a simple multiplayer game, and I have 2 qestions.
-
- I found the packet I want to send to the server using wireshark, but how do I send it?
-
- can I make a pyton code that does it?
-
I use linux
OSPF LFA instead of RSVP-TE for FRR
Is anyone running OSPF LFA in their MPLS core instead of RSVP-TE? I'm curious if you've come across any caveats or problems... or is it working well? We're currently using RSVP-TE, only for the Fast ReRoute capabilities. I've done some basic testing in the lab and it's working as expected, but I haven't pushed it very hard yet. Would love to hear some real world experiences.... We're doing L3VPN, VPLS and will be adding Label Switch Multicast (mLDP) to the mix soon.
AT&T to Release “dNOS” Software Framework Into Open Source to Accelerate Network White Box Adoption
Couldn't see this posted here even though it's 8 days old.
Has anybody used dNOS? Is it Vyatta like syntax? Where does this put VyOS in the open source networking world?
Tuesday, February 6, 2018
Anyone plan on getting the EVE-NG pro version coming out soon?
https://www.youtube.com/watch?v=aLZJXwZN0fk&t=1s
Trailer looks wicked, the dev's been putting some serious work into this thing. Worlds beyond VIRL and GNS3.
I heard from a source itll be like $100.
SD-WAN packet fixing & Optimisation,.. does it really work
Hi All, So I've been going back and forth with some people in my team over SD-WAN & Optimisation tech and wearing my Admin type hat,.. well tbh, I don't believe that it actually works as described. Far too many times I've been told about product bla that will do this amazing thing and make my life amazing & simple only for management of my workplace to fall for it, we put it in and then it does a mediocre job at best. Essentially we have one guy in our team who is pushing Silver-Peak massively (to the point where I think he must be getting a kick back) saying that it will make our Office 365 run so much better bla bla bla, however this guy has questionable knowledge on how the inner working of tech works and generally just know what current buzz works to say.
So mini rant over, does this stuff actually work? If i put in a silver peak router & server in azure will it somehow magically use less bandwidth when downloading files from SharePoint? Will it somehow make all of my emails smaller and allow us to de-dupe email traffic,.. even though said traffic is encrypted? Also the whole SD-WAN premise looks to be geared towards businesses with multiple offices that want links in-between them, however everything of ours is in the cloud so I don't really see any benefit with that. The only thing I can see is that it can repair dropped packets through parity information in the packets that did arrive. however thats not an issue that we really have.
So I guess what I'm asking is, does anyone use this stuff that can honestly tell me if it works as described who doesn't work for the company selling said product. Every review I've read that says it works all looks to be written by someone who works for the company of the product they are reviewing.
thanks in advance for anyone that has the time to comment.
Bought a router, Speeds over wireless abysmal, speedtest.net said something about port 8080
So, I'm assuming that port 8080 is somehow blocked, and to my knowledge port forwarding directs traffic to a specific computer.
I'm using this router, which I got for the new place, since it has to be in the main room, and it was attractive. So far I have to say I'm very unimpressed.
I'm not a network guru or anything, but I'm techy enough. This piece of shit is blocking 8080, which is basically option 2 for web traffic. 80 being the primary.
What gives? Is there a setting somewhere I can change? Port forwarding doesn't seem like the right choice. Only getting .29 of my 50 mb down right now. Getting full upload.
So confused.
Nat route-map question.
I'm trying to understand what the following command is doing:
ip nat inside source route-map MAP1 interface GigabitEthernet0 vrf INET overload
Here is route-map MAP1:
route-map MAP1 permit 10 match ip address NAT_LOCAL match interface GigabitEthernet0
Here's NAT_LOCAL ACL:
ip access-list extended NAT_LOCAL permit ip 192.168.1.0 0.0.0.255 any permit ip 10.0.0.0 0.0.0.255 any
And then there's also another route map:
route-map MAP2 permit 10 match ip address LOCAL set vrf INET
And LOCAL ACL:
(Bunch of (what looks like to me) random deny statements.) permit ip any any
And finally
VRF definition INET
and our Tunnel0 has "tunnel vrf INET"
So, my question is, are both route maps being applied? What I think is happening (please correct me if I'm wrong) is both route-maps are being applied, but the IP of the traffic depends on which map is applied? For example if a packet comes in that's not in the 192.168.1 subnet or the 10.0.0 subnet, the route map MAP1 will be applied?
Subscribe to:
Posts (Atom)