Do both sides of a trunk need tagging with the same VLANS? Networking |
- Do both sides of a trunk need tagging with the same VLANS?
- How challenging was it for you when you first learned Networking?
- Signed Packet Capture?
- Connecting Cisco to Extreme via Transit VLAN
- Direct connect switch bypass
- Easter eggs!
- SNMP View Clarification
- fq_codel stats on everything?
| Do both sides of a trunk need tagging with the same VLANS? Posted: 03 Sep 2018 07:17 AM PDT I'm usually server admin so apologies for what might be a basic query. I think I understand but would like some clarification if possible. I have a particular port on a switch that is tagged in multiple VLANs. That port is connected to a port on another switch which has vlan 1 untagged. Does this mean anything on the tagged vlans can go down the trunk and when they get to the other end the vlan info is stripped and put into vlan one of the other side? How does this work going the other way? [link] [comments] |
| How challenging was it for you when you first learned Networking? Posted: 03 Sep 2018 12:36 PM PDT |
| Posted: 03 Sep 2018 11:19 AM PDT Hi, Does anyone know if there are commercial products that provide a signed network capture? It's easy to perform a ethernet packet capture but I am looking for something that will provide assurance that the packet capture has not been tampered with. Imagine that you had a situation where the other party denies a specific network behavior. I am looking for a commercial product that will sign the ethernet capture. [link] [comments] |
| Connecting Cisco to Extreme via Transit VLAN Posted: 03 Sep 2018 04:29 AM PDT Hello reddit, We have an Extreme x670_G2 switch running at a client, which we wish to manage remotely. For this we use a transit VLAN on a single port. The IP of the transit vlan (Cisco side) is configured as default gateway within the Extreme. The issue: I am succesfully connecting to the switch remotely via SSH, and from inside the cli we can access the devices on the VLANs. But, from the Cisco network we cannot access the devices directly (to for example, use RDP). We do not have access to the Cisco switches, nor do we have the configuration. Do there need to be static routes defined from the Cisco network to each devices to access those? If so, is it also an option to change the transit VLAN subnet mask to 255.255.254.0? The transit VLAN is configured as following: Extreme transit: 192.168.11.193 255.255.255.192 Cisco transit: 192.168.11.254 255.255.255.192 The default gateway on the Extreme is set to 192.168.11.254, ipforwarding is enabled on all VLANs. An example device we want to access: 192.168.10.5 A quick summary from the Cisco side: We can access 192.168.11.254, 192.168.11.193, but not 192.168.10.5 From the Extreme side: We can access all of the above IP's. [link] [comments] |
| Posted: 03 Sep 2018 02:20 PM PDT I'm pondering a thought experiment on a lab environment: I want to add a dedicated 10G link between a server and workstation to facilitate high speed transfers of vm images, and skirting round prohibitively expensive switch upgrades from 1G. Both devices have to remain connected to the switch. Server is running ESX so I toyed with just letting it do the switching, but it seems ESX won't do frame forwarding in the vswitch, so L2 connectivity upstream doesn't work. If I add a dedicated card to each machine and connect them up - is there a clean way to get them to talk without kippering up standard network access? My areas of confusion are (and showing how limited my networking knowledge is):
I'm sat here scratching my head thinking that this really isn't a possibility. I think it might be doable if you're doing an explicit connect to a service (e.g. a SCP transfer) where you can target the other nic, but otherwise it wouldn't really work. Any thoughts to aid my inevitable insomnia? [link] [comments] |
| Posted: 03 Sep 2018 11:11 AM PDT Anyone know any NOS easter eggs? One of my favorite JunOS gems is: show version and haiku [link] [comments] |
| Posted: 03 Sep 2018 07:44 AM PDT In the following Cisco command, I'm trying to understand the differences in views: notify, read and write. snmp-server group [groupname {v1 | v2c | v3{auth | noauth | priv}}] [read readview] [write writeview] [notify notifyview] [access access-list] I'm having a hard time finding a straightforward explanation so please correct me if I'm wrong: Notify: send only to SNMP server and won't respond to queries Read: notify and allow responses to queries Write: notify and read, but also allow configuration write [link] [comments] |
| Posted: 03 Sep 2018 12:43 AM PDT I see that a lot of folk here are now aware of bufferbloat, fq_codel, sch_cake and smart queue management (SQM). Universally (aside from running out of cpu), the reports are positive, which makes me happy (and happier still that y'all seem to "get" it). What I'm interested in finding out though, are what are the drop/marks per day people are seeing in their deployments? Recently I started calling these "debloats/day", because I know that every drop is preventing a 500+ms latency excursion on my campus network (3000/day inbound on just the main gateway, 12,000 on my wifi networks, 100+ outbound), and I feel good every time a packet is lost in this cause. How many drops/marks a day are y'all getting with normal traffic? (I monitor these with mrtg personally) In linux the command to see this is "tc -s qdisc show dev yourdevice" [link] [comments] |
| You are subscribed to email updates from Enterprise Networking news, blogs and discussion.. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment