• Breaking News

    [Android][timeline][#f39c12]

    Sunday, April 29, 2018

    Undersea cable outage tracker? Networking

    Undersea cable outage tracker? Networking


    Undersea cable outage tracker?

    Posted: 29 Apr 2018 07:36 AM PDT

    Anyone know of a website that tracks the status of undersea cabling? Seems like there is always a few undersea cables down due to negligent fishermen or whatever.

    I know that sites like cablemap.info which list all the cables but it doesn't show anything about their current status.

    submitted by /u/gerrrrrrrrr
    [link] [comments]

    Cisco 9300 - Stackwise Virtual vs Stackwise 480

    Posted: 29 Apr 2018 11:41 AM PDT

    We are deploying 2 pairs of Catalyst 9300 as a Collapsed Core in 2 Regional Offices, replacing HP 3500yl. We are licensed for Network Essentials.

    Wondering what people's experience is with Stackwise Virtual. I've dealt with traditional Stackwise on 3750/X/3850 and VSS on 4500X, but haven't deployed Stackwise Virtual yet. We have purchased the 8x10G expansion modules for these switches as well, and will use Twinax to interconnect with new Access Switches (unsure if Meraki or Catalyst yet).

    For context, there isn't a lot of gear in these Offices:

    • 2-4AP's (Meraki MR32)
    • 1 WAN Circuit
    • 1 Audiocodes Telephony Gateway hosting 1 PRI
    • 1 Fortigate Firewall for Local Internet.
    • 1 UPS
    • 1 VM Host hosting File/Print, DC and SfB Survivable Branch Server
    submitted by /u/itguy9013
    [link] [comments]

    What's new in Network Monitoring in the last 12 months?

    Posted: 28 Apr 2018 08:52 PM PDT

    I would like to hear what people have to say about these network monitoring topics:

    1. New useful features and capabilities in PRTG, Solarwinds, and other monitoring tools in the last 12 months
    2. New monitoring tools that did not exist before the last 12 months
    3. What is one useful thing YOU have learned in network monitoring in the last 12 months (doesn't have to a be a new technology or feature).
    4. What's else has changed about network monitoring in 2018, versus say 2014 or 2015, if anything?
    submitted by /u/joshgoldeneagle
    [link] [comments]

    How much experience would you expect from a CCIE?

    Posted: 29 Apr 2018 10:43 AM PDT

    Firstly I apologise if this is against the rules. It's not really an early career question however I can see how it might not be permitted for the same reason

    I'm about to begin to pursue CCNP R&S exams having been operating at that level for a while in my career and having completed CCNP Route/Switch courses. I have about 8 years of Sysadmin experience and 5 really focused on networking. After this I'm planning to move jobs to get something more network focused (currently have a 50/50 split).

    What I'm trying to gauge is if I should be thinking about CCIE after acheiving the NP? The CCNP is the logical next step from the CCNA but is the IE the same for the NP? Or is it accepted that most don't go on to the IE and those that do should have more years under their belts?

    I have had dealings with a few CCIEs (especially security ones) where they've got some gaps in their general knowledge in networking and I've honestly been a bit disappointed.

    submitted by /u/FastEthernet
    [link] [comments]

    Libreswan to ASA 5500 Config

    Posted: 29 Apr 2018 10:51 AM PDT

    I have to create an IPSec tunnel from amazon to an ASA 5500. Below is the info I was provided on the ASA config:

    Support Key Exchanged for Subnets: ON IKE Encryption Method: AES256 SHA IKE Diffie-Hellman Groups for Phase 1: Group 2 (1024 bit) IKE (Phase-1) Timeout: 1440 Min IPSEC Encryption Method: AES256 SHA IPSEC (Phase-2) Timeout: 3600 Sec PFS (Perfect Forward Secrecy): Disabled Keepalive: Disabled 

    I setup libreswan on a centos 7 ec2 instance. This is what I have for Libreswan connection config:

    conn ipsec type=tunnel authby=secret remote_peer_type=cisco initial-contact=yes rekey=yes pfs=no ikelifetime=1440m salifetime=60m ike=aes256-sha1;dh2 phase2alg=aes256-sha1;modp1024 aggrmode=no 

    I've successfully created a tunnel to another libreswan instance in a separate aws vpn and can pass traffic but when I point to the ASA, I don't seem to be even getting past the IKE phase. based on this ipsec status:

    000 Total IPsec connections: loaded 1, active 0 000 000 State Information: DDoS cookies not required, Accepting new IKE connections 000 IKE SAs: total(1), half-open(0), open(1), authenticated(0), anonymous(0) 000 IPsec SAs: total(0), authenticated(0), anonymous(0) 000 000 #1: "ipsec":4500 STATE_MAIN_I3 (sent MI3, expecting MR3); EVENT_v1_RETRANSMIT in 12s; nodpd; idle; import:admin initiate 1: pending Phase 2 for "ipsec" replacing #0 

    I know the preshared key is correct but I'm at a loss. For starters, do I at least have the correct libreswan config based the ASA config?

    I'm banging my head against the wall here and am willing to pay if someone knowledgeable can give some direction.

    submitted by /u/somethingwitty11011
    [link] [comments]

    Vendors are jerking us around, switch stacking help. (xpost /sysadmins)

    Posted: 29 Apr 2018 01:49 PM PDT

    I'm no hardware guy and I'm not sure if the answer is based on the brand, but 4 vendors are contradicting each other and I'm starting to lose hope in finding a correct answer.We're installing new switches in a 7 floor building, each floor has around 4 - 5 switches running in stack configuration to appear as a single virtual switch, those stacked switches will all connected to an aggregation switch eventually. Problem is no one seems to figure out what are the hardware requirements to connect those stacked switches to an aggregation switch, I know that we need 2 SPF ports to configure stacking in a loop configuration, but what is the correct way to connect them to the aggregation switch?

    1. One Vendor says that every physical switch needs 3 SPF ports, 2 for loop and 1 to be connected to the aggregation switch using a direct cable, which is totally crazy and goes against the goal of stacking.
    2. Another says that all switches in the stack need only 2 SPF ports, and that I can close the stacking loop by taking one of the SPF ports in the first and last switches and connect them on the aggregation switch.
    3. Another says that all switches in the stack need 2 SPF ports to close the loop, but the first and last switches in the stack needs 1 additional SPF port to connect them to the aggregation switch.
    4. the last one says that all switches in the stack need 2 SPF ports to close the loop, but the first and last switches in the stack needs 2 additional SPF port instead of 1 to connect them to the aggregation switch.

    I'm leaning toward answer 4, but a confirmation from one the hardware masters here with a link that I can stick it to the vendor faces will be awesome.

    submitted by /u/Batmanzi
    [link] [comments]

    HP Procurve DHCP Server Comnection Issues

    Posted: 29 Apr 2018 09:54 AM PDT

    Hey All,

    I have a question about an HP Procurve 2824 switch. Anything that is not in the same subnet as the DHCP server is unable to connect to it. I have the IP helper address set as the DHCP server address. What else is needed to get it to connect to it?

    submitted by /u/thatfuckingotherguy
    [link] [comments]

    Need assistance F5 GTM config .

    Posted: 29 Apr 2018 01:35 PM PDT

    Hey all,

    I'm new to F5 and planning to install first F5 Big-ip LTM + GTM to load balance proxy traffic at two sites which will act as backup to each other. F5 is inline between users >> Proxy Servers >> Internet.

    Here is the network diagram of two sites. https://imgur.com/a/sSN8Q1L

    Goal is to set up LTM+GTM for traffic processing and failover as below: Normal operation: 1) When Site-A F5 receive DNS query from Site-A LDNS >> Send it to Site A Vip. When Site-A F5 receive DNS query from Site-B LDNS >> Send it to Site B Vip. 2) When Site-B F5 receive DNS query from Site-B LDNS >> Send it to Site B Vip. When Site-B F5 receive DNS query from Site-A LDNS >> Send it to Site A Vip Failover operation: 3) When Site-A F5 receive DNS Query >> If Site A Vip is Down >> Send it to Site-B Vip 4) When Site-B F5 Receive DNS Query >> If Site B Vip is Down >> Send it to Site-A Vip

    Here are the ips for example: Site-A Virtual Server= 10.1.1.100 Real server =10.1.2.10 & 20
    (10.1.1.100 =webproxy.technet.com 10.1.1.x = internal vlan 10.1.2.x=external vlan) Site-B Virtual Server= 10.2.1.100 Real server =10.2.2.10 & 20
    (10.2.1.100 =webproxy.technet.com 10.2.1.x = internal vlan 10.2.2.x=external vlan)

    I did the basic config for LTM like node, pool & virtual server. But I'm confused what ip to use for GTM and how to configure GTM to provide name resolution based on client DNS server and irules to divert traffic.

    What config do I need on LTM + GTM?? LTM: 1) Configure Node – Real servers ( 10.1.2.10& 20) 2) Configure Pool – Proxy Server Pool ( Add node + port) 3) Config Virtual Server – (webproxy.technet.com/10.1.1.100)

    GTM/DNS 1) Config Listener (Can I use Vip??? Or need new ip?? ) 2) Config Wide ip (Do I need different ip in same internal subnet 10.1.1.x??) Does the hostname should be webproxy.technet.com??) 3) Do I need GSLBPool?? What type, SRV, A, CNAME??? Which Member ip to add, wide ip of both site??? 4) Config Data Center- Site-A & site-B 5) Do I need GSLBServer?? Which server to add Vip or Real??? 6) Where do I apply rule to divert traffic?? Under Wide IP???

    When user send DNS request for webproxy.technet.com which ip will resolve it Wide ip?? Or Vip??

    Does anyone know hierarchy chart for GTM config? Like LTM (node >> pool >> Virtual server). Could someone provide a break down of the objects and config?

    Thanks in advance.

    submitted by /u/topshot29
    [link] [comments]

    About CAM lookup and how a frame is forwarded

    Posted: 29 Apr 2018 01:27 PM PDT

    I'm studying to take my CCNP Switch exam sometime soon, and am reading through the Cisco Press book. Only on chapter 2 so far, but I feel I've found an errata, or at least something that seems very misleading.

    In my copy of the book, page 34 and listed as a key topic,

    "Incoming frames also include the destination MAC address. Again, the switch looks up this address in the address table, hoping to find the switch port and VLAN where the destination address is attached. If found, the frame can be forwarded out the corresponding switch port."

    And then on page 36,

    "L2 forwarding table: The frame's destination MAC address is used as an index, or key, into the content-addressable memory (CAM), or address, table. If the address is found, the egress switch port and appropriate VLAN ID are read from the table."

    To me, this reads as if the destination MAC address determines the VLAN that the frame will be forwarded on, which to the best of my knowledge is absolutely not the case. A switch with multiple VLANs should keep either a separate table for every VLAN, or (more likely) use the VLAN and destination MAC together as the key in the lookup.

    I put together a lab in GNS3 that seems to support my understanding. I can share configs and more details if desired, but in short I have an IOSvL2 (layer 3 switch) node running without any SVIs (so just as a L2 switch) that is learning the same MAC address on 4 different VLANs across 4 different access ports, and I have no trouble forwarding either unicast or broadcast traffic within the correct VLAN, proving (in my mind) that the destination MAC does not have any influence on the VLAN.

    I can accept that I might be nitpicking a bit about the few quoted statements, but I want to be sure my understanding is good. Specifically, that the VLAN and MAC are used together as the key for a CAM lookup.

    If that understanding is not correct, is there any resource that gives more detail on what keeps a frame within its own VLAN in Cisco hardware?

    submitted by /u/internet_eq_epic
    [link] [comments]

    I just got a toiletpaperlink ipsec vpn working with a fortigate AMA

    Posted: 29 Apr 2018 02:15 AM PDT

    It only took me 5 or 6 hours of messing with it. (including setting it up on pfsense just to make sure it wasn't an issue between the 2 locations)

    I spent 3 hours messing with it, decided it might just be something between the 2 points so I loaded up a pfsense instance and in 10 minutes it was working. Whoever wrote the interface and manual for toiletpaper link should be shot. I don't how you would shoot google translate though...

    It was so bad and there is such a lack of documentation examples out there I might just make an ebook and sell it for a dollar /s

    I had never been in a tp link until today, I heard they were bad... wow. The logs are horrible, the interface is almost worse.

    The thruput isn't as bad as I thought it would be... was getting 2.5MB/s over the vpn with pfsense. around 1.3MB/s on the 2 ply.

    submitted by /u/remotefixonline
    [link] [comments]

    No comments:

    Post a Comment

    Fashion

    Beauty

    Travel