Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
jwh
Jun 12, 2002

Yeah, never try and navigate the Cisco web maze if you value your sanity.

Adbot
ADBOT LOVES YOU

ElCondemn
Aug 7, 2005


jwh posted:

Yeah, never try and navigate the Cisco web maze if you value your sanity.

To be fair they have made improvements in the past few years (downloading the right IOS is easier now), it's still pretty lovely though.

CrazyLittle
Sep 11, 2001





Clapping Larry

Erwin posted:

2960-S, version 12.2, which is weird because we just bought them, so I would have figured 15.2?

Nah, 2960 switches are still on the old catalyst OS 12.2 branch. It's the routers that are up to 15.2

jwh posted:

Yeah, never try and navigate the Cisco web maze if you value your sanity.

The worst is how it randomly logs me out while navigating the various pay-gates within their site.

bort
Mar 13, 2003

Sepist posted:

My coworker uses ASDM and I use CLI, I can confirm the eye bleeding.
My rule is, employees that use ASDM have to be extremely detail-oriented and name service and object groups properly. DM_INLINE_ANYTHING gets reprimanded. There are good arguments for both configuration approaches, but I will not have my CLI users be the have-nots.

I love Cisco docs

n0tqu1tesane
May 7, 2003

She was rubbing her ass all over my hands. They don't just do that for everyone.
Grimey Drawer

CrazyLittle posted:

Nah, 2960 switches are still on the old catalyst OS 12.2 branch. It's the routers that are up to 15.2


The worst is how it randomly logs me out while navigating the various pay-gates within their site.

The 3750-X and 3560-X switches are on 15 as well.

BurgerQuest
Mar 17, 2009

by Jeffrey of YOSPOS
We've got a buttload of 2960's out on sites and around the place, they're pretty solid for our purposes. What are you using them for?

Yeast Confection
Oct 7, 2005

n0tqu1tesane posted:

The 3750-X and 3560-X switches are on 15 as well.

Hmmm. We've ordered at almost 40 3560X/3750X in the last six months and they've all shipped with 12.2(55).

falz
Jan 29, 2005

01100110 01100001 01101100 01111010
But you can upgrade them if you want.

ragzilla
Sep 9, 2005
don't ask me, i only work here


VR Cowboy posted:

Hmmm. We've ordered at almost 40 3560X/3750X in the last six months and they've all shipped with 12.2(55).

Depends where they're coming from, if you order new from Cisco you can pick the software version when you place the order. If you're ordering from distribution (99% of the time you're buying fixed config devices, Cisco wants you buying from distribution, unless you're a distributor) you get whatever was current when the distributor ordered a truckload of switches.

Looks like you can get 3560/3750 -E and -X shipped new with 15.0 software in the current price list.

evil_bunnY
Apr 2, 2003

I'm cross-posting this from the enterprise storage thread since I figure most of you don't read that:

I'm having a routing(?) issue on my netapp system and our network team is being fantastically uncooperative (though the original issue is most probably my doing). Can any of you actually smart people spot any obvious mistakes? I don't understand why this wouldn't work. Right now I can't ping even my default GW.


I can't seem to route to our normal networks, only on my management interface/subnet/VLAN.

This is the cisco VPC/ports:

code:
interface port-channel1
  description netapp2240_1
  switchport mode trunk
  switchport trunk native vlan 731
  switchport trunk allowed vlan 731,738-739
  spanning-tree port type edge trunk
  speed 10000
  vpc 1

interface port-channel2
  description netapp2240_2
  switchport mode trunk
  switchport trunk native vlan 731
  switchport trunk allowed vlan 731,738-739
  spanning-tree port type edge trunk
  speed 10000
  vpc 2
  
  [...]
  
  interface Ethernet1/1
  switchport mode trunk
  switchport trunk native vlan 731
  switchport trunk allowed vlan 731,738-739
  channel-group 1 mode active

interface Ethernet1/2
  switchport mode trunk
  switchport trunk native vlan 731
  switchport trunk allowed vlan 731,738-739
  channel-group 2 mode active
  
Is there anything retarded I'm doing? Rest of the configs are in the original post too.

chestnut santabag
Jul 3, 2006

switchport trunk native vlan 731

Is there a setting in your netapp setting that recognises untagged traffic as being in vlan 731 like the above command?
If you don't then you got a native vlan mismatch and your netapp is receiving untagged traffic that it doesn't know belongs to vlan 731.

Nitr0
Aug 17, 2005

IT'S FREE REAL ESTATE
It should have also told you that in the syslog if you are getting a native vlan mismatch.

Erwin
Feb 17, 2006

BurgerQuest posted:

We've got a buttload of 2960's out on sites and around the place, they're pretty solid for our purposes. What are you using them for?

Was this a question for me? General switching for a small office - stack of 4 plus 1 PoE for phones and such. Maybe iSCSI, but I'll probably reuse the Procurves for that.

Begby
Apr 7, 2005

Light saber? Check. Black boots? Check. Codpiece? Check. He's more machine than kid now.
Ok, our internet is totally messed up and it has been for literally years. Typically when it rains a lot it will go to 10% packet loss, and/or the latency will go up. By the time charter sends out one of their redneck reps 2 days later it stops, so they run their little tests, replace the cable modem and leave.

This month they have replaced the cable modem 3 times and ran a new home run from the pole, and are now telling us we have an internal network issue. I am hesitant to believe them since last I checked it doesn't rain on our goddamn server racks. However, on the off chance they are right I need to look into this and apparently prove them wrong before they will show up to replace our cable modem again.

Right now our latency varies between 20ms up to 800ms and for the last hour it has been hovering around 400ms.

We have a cisco asa, some sort of cisco router, and then that router is plugged into their lovely modem. The ASA is set to fall back to DSL on failure of the cable modem (which it hardly ever does since its just packet loss, not a full on loss of connection).

Here is an incoming trace

code:
1 	  0 	  0 	  0 	     206.123.64.42	   -   
2 	  0 	  0 	  0 	     173.219.246.92	  173-219-246-92-link.sta.suddenlink.net  
3 	  0 	  0 	  1 	     66.76.104.38	  66-76-104-38.ukwn.suddenlink.net  
4 	  3 	  3 	  3 	     96.34.3.98	  bbr01ftwotx-tge-0-3-0-6.ftwo.tx.charter.com  
5 	  37 	  31 	  31 	     96.34.0.123	  bbr01blvlil-tge-0-2-0-12.blvl.il.charter.com  
6 	  39 	  35 	  35 	     96.34.1.119	  bbr01olvemo-tge-0-1-0-7.olve.mo.charter.com  
7 	  36 	  35 	  35 	     96.34.1.208	  bbr02chcgil-tge-0-3-0-5.chcg.il.charter.com  
8 	  40 	  35 	  35 	     96.34.0.188	  bbr01chcgil-tge-0-1-0-2.chcg.il.charter.com  
9 	  38 	  47 	  47 	     96.34.0.193	  bbr01aldlmi-tge-0-1-0-12.aldl.mi.charter.com  
10 	  37 	  39 	  39 	     96.34.2.175	  crr02aldlmi-tge-0-3-0-4.aldl.mi.charter.com  
11 	  38 	  39 	  39 	     96.34.40.45	  crr02trcymi-tge-0-0-0-0.trcy.mi.charter.com  
12 	  38 	  38 	  39 	     96.34.33.15	  dtr04trcymi-tge-0-1-0-1.trcy.mi.charter.com  
13 	  38 	  38 	  38 	     96.34.40.41	  cts01trcymi-tge-1-0-0.trcy.mi.charter.com  
14 	  380 	  401 	  473  	10.154.126.56	   -  
15 	  384 	  420 	  480	     71.83.3.122	  71-83-3-122.static.aldl.mi.charter.com  
Here is an outgoing trace to 8.8.4.4 with the hops after 8 omitted since they are all the same. In the last few minutes it has dropped back down to what looks like around 100ms.
code:
1  192.168.1.1 (192.168.1.1)  0.753 ms  0.609 ms  0.585 ms
 2  71-83-3-121.static.aldl.mi.charter.com (71.83.3.121)  1.106 ms  0.979 ms  1.472 ms
 3  10.154.126.1 (10.154.126.1)  107.541 ms  113.681 ms  116.863 ms
 4  dtr04trcymi-tge-0-1-0-13.trcy.mi.charter.com (96.34.40.40)  117.703 ms  124.686 ms  119.317 ms
 5  crr02trcymi-tge-0-7-0-5.trcy.mi.charter.com (96.34.33.14)  148.474 ms
    crr02trcymi-tge-0-7-0-4.trcy.mi.charter.com (96.34.33.12)  149.935 ms
    crr02trcymi-tge-0-7-0-5.trcy.mi.charter.com (96.34.33.14)  148.826 ms
 6  crr02aldlmi-tge-0-0-5-0.aldl.mi.charter.com (96.34.40.44)  134.008 ms  23.419 ms  19.746 ms
 7  bbr01aldlmi-tge-0-1-0-2.aldl.mi.charter.com (96.34.2.174)  26.336 ms  57.472 ms  71.689 ms
 8  bbr01chcgil-tge-0-1-0-8.chcg.il.charter.com (96.34.1.134)  75.384 ms  83.726 ms  84.072 ms
I am no internet wizard, but it looks like the 3rd hop on the way out is where it goes to hell, and the 14th hop on the way in is where it breaks down.

Could this still be an issue with our internal network given the info above? We do not have anything to do with the routers in the 10.0.0.1 subnet.

As far as internal problems, the issues happen at all hours when people are not here since I get text messages when some public IPs become unavailable. I also did show interfaces on the cisco router and it is showing a 5 minute average throughput of something like 1.2mbs and we have a 20mbs connection. I can download stuff quite quickly. I ran show conn on the ASA and didn't see anything suspicious or questionable outside ports open. I can ping our router and the cable router at about 1ms.

I have no idea what else to do to troubleshoot this or what I need to tell Charter cuz' apparently they cannot figure this out on their own.

ate shit on live tv
Feb 15, 2004

by Azathoth
Run continuous pings to 8.8.8.8 and to your first hop in the ISPs network. In your case it looks like 10.154.126.1. But use the 0/0 route that your ASA uses to leave your network.

What you'll find is that you can ping your first hop with <5ms latency, but 8.8.8.8 will go to hell. This demonstrates that the problem is taking place outside of your network. (It is most certainly an issue at the cable providers node).

Now the challenge is to convince your provider that the issue is on their side, not yours, do you have an official SLA in your Business contract? If not, make sure you work one in there when you re-up. Get your account manager involved and start seriously shopping around for other options, the issue won't be resolved unless you force the providers hand.

ragzilla
Sep 9, 2005
don't ask me, i only work here


Begby posted:

Ok, our internet is totally messed up and it has been for literally years. Typically when it rains a lot it will go to 10% packet loss, and/or the latency will go up. By the time charter sends out one of their redneck reps 2 days later it stops, so they run their little tests, replace the cable modem and leave.

Do you have any access to the cable modem's web pages which display SNR and output power? If so, start graphing them using Cacti or similar.

BelDin
Jan 29, 2001
Crossposting something that pisses me off... Cisco.

Backstory:
We bought 2x 5548Ps and 20x 2248s in order to converge our data and storage networks in our new datacenter. After carefuly reading the configuration limitations document and designing around the limitations for our migration, we pulled the trigger and bought the material. The document that I used as prep work for the actual deployment was Data Center Access Design with Cisco Nexus 5000 Series Switches and 2000 Series Fabric Extenders and Virtual PortChannels. I panned on being able to hook the Nexus up to our distribution switches and standalone iSCSI network for the migration process and to provide L3 services (because of the limitations with using the L3 routing modules)

Current:
The document states that you can configure per-interface MTU size. Why is this important you might ask? Our data network (dist./access switches) run a standard MTU size of 1500. Our iSCSI network, on the other hand, use jumbo frames with a MTU of 9000. After trying the steps outlined in the document, I have only been able to set the MTU globally on the Nexus to jumbo or non-jumbo. After contacting TAC, they have confirmed that the MTU qos policy can only be applied at the system level, not per interface.

So, any ideas other than not converging our networks and buying a standalone 4900/3750x series pair for our iSCSI network? If I take that approach, management will pretty much eat me alive. If I don't enable jumbo frames for storage traffic, the SAN admins will probably eat me alive. All the while, Cisco TAC shrugs and implies that it is my fault for believing their own documentation.

I'm currently waiting on suggestions of how to make it work.

In the meantime, I'm going home to break out the Glenlivet.

BelDin fucked around with this message at 02:37 on Sep 20, 2012

ate shit on live tv
Feb 15, 2004

by Azathoth
Whats wrong with enabling jumbo frames globally? The nexus isn't doing any layer 3 so it shouldn't respond to any maximum MTU ICMP requests, and your routers are going to stay using the normal 1500mtu.

Begby
Apr 7, 2005

Light saber? Check. Black boots? Check. Codpiece? Check. He's more machine than kid now.

Powercrazy posted:

Run continuous pings to 8.8.8.8 and to your first hop in the ISPs network. In your case it looks like 10.154.126.1. But use the 0/0 route that your ASA uses to leave your network.

What you'll find is that you can ping your first hop with <5ms latency, but 8.8.8.8 will go to hell. This demonstrates that the problem is taking place outside of your network. (It is most certainly an issue at the cable providers node).

Now the challenge is to convince your provider that the issue is on their side, not yours, do you have an official SLA in your Business contract? If not, make sure you work one in there when you re-up. Get your account manager involved and start seriously shopping around for other options, the issue won't be resolved unless you force the providers hand.

Thank you for this, we do not have one as far as I know, but I will get the contract pulled and check it out, then demand that we get one. I'll put together some info and send it off to them to make my case.

ragzilla posted:

Do you have any access to the cable modem's web pages which display SNR and output power? If so, start graphing them using Cacti or similar.

Also thank you. I do not have access to the cable modem as far as I know, it is owned by them and I have no idea how to get into it.


Edit: Goddamit. Got an email from them, finally, saying they got into our router to troubleshoot it and they are getting 30ms pings and no drops and that from their end its not an issue since they can't reproduce it. Well no poo poo, ITS NOT loving RAINING ANYMORE AND LIKE I KEEP loving SAYING IT ONLY HAPPENS WHEN IT RAINS. gently caress. Its like talking to my 4 year old.

Begby fucked around with this message at 00:42 on Sep 20, 2012

bort
Mar 13, 2003

A lot of cable modems listen on 192.168.100.1, if you can try it on the network the inside interface is on. It's often not configurable, but will give you the SNR metrics and whatnot.

edit: rain would also imply a problem at the physical layer. Maybe a splitter with a rusty or loose connection outside needs replacing or tightening?

bort fucked around with this message at 01:26 on Sep 20, 2012

BelDin
Jan 29, 2001

Powercrazy posted:

Whats wrong with enabling jumbo frames globally? The nexus isn't doing any layer 3 so it shouldn't respond to any maximum MTU ICMP requests, and your routers are going to stay using the normal 1500mtu.

The traffic with jumbo MTU going to a switch without it would be the problem as far as I can tell. My understanding is that fragmentation doesn't happen at L2, the frame is just dropped as too large.

The distribution switches are 1500, so if I enable jumbo on them, all 1g and 10g links would have that MTU. Then I would have to change on the L2 switches downstream, etc.

BelDin fucked around with this message at 02:39 on Sep 20, 2012

doomisland
Oct 5, 2004

I find MTR better than traceroute with figuring out network issues. Mostly because it'll give you packet drop % on each hop so you at least know where there may be congestion.

BurgerQuest
Mar 17, 2009

by Jeffrey of YOSPOS
Has anyone worked with the Cisco SRE modules and WAAS? Looking at a small integrated device (2911ish) that also runs a few apps off a Windows Server 2008R2 instance, and will be on the end of a satellite link (hence WAAS). Opinions? Worth it? Utter crap?

ofwolfandan
Aug 13, 2004

FACE THE PIE THAT SHOULD NOT BE
I've been having a hard time getting this 860 up. The config looks OK to me. What am I missing here? This is a very basic setup.

DHCP works fine. I can ping the inside global from a connected host, but nothing beyond that. I can also access it from the outside, and ping the outside from the console. This tells me it's probably a NAT issue but damned if I can find any problem with it.

code:
Building configuration...

Current configuration : 1390 bytes
!
! Last configuration change at 19:14:07 UTC Mon Jan 2 2006 by Admin
!
version 15.0
service config
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname ballsack
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 10
!
!
ip source-route
!
!
ip dhcp excluded-address 192.168.1.1
!
ip dhcp pool dhcp-pool
   network 192.168.1.0 255.255.255.0
   dns-server 8.8.8.8 8.8.4.4
   default-router 192.168.1.1
!
!
ip cef
!
!
license udi pid CISCO861-K9 sn 00000000000
!
!
username admin privilege 15 password 7 112B5D58251A1E18013A
!
!
!
!
!
!
!
!
!
interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface FastEthernet4
 ip address inside.global.ip.address 255.255.255.240
 ip nat outside
 ip virtual-reassembly
 duplex auto
 speed auto
!
interface Vlan1
 ip address 192.168.1.1 255.255.255.0
 ip nat inside
 ip virtual-reassembly
!
ip forward-protocol nd
no ip http server
ip http authentication local
no ip http secure-server
!
ip nat source list 1 interface FastEthernet4 overload
ip route 0.0.0.0 0.0.0.0 isp.gateway.ip.address
ip route 192.168.1.0 255.255.255.0 Vlan1
!
access-list 1 permit 192.168.1.0 0.0.0.255
!
control-plane
!
!
line con 0
 no modem enable
line aux 0
line vty 0 4
 login local
 transport input telnet
!
scheduler max-task-time 5000
end

Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0              unassigned      YES unset  down                  down
FastEthernet1              unassigned      YES unset  down                  down
FastEthernet2              unassigned      YES unset  down                  down
FastEthernet3              unassigned      YES unset  down                  down
FastEthernet4  inside.global.ip.address    YES NVRAM  up                    up
NVI0           inside.global.ip.address    YES unset  up                    up
Vlan1                      192.168.1.1     YES NVRAM  down                  down


bort
Mar 13, 2003

You missing an ip nat pool declaration?
I see the overload now.

bort fucked around with this message at 04:20 on Sep 20, 2012

ofwolfandan
Aug 13, 2004

FACE THE PIE THAT SHOULD NOT BE
The vlan network doesn't show up in the routing table. But I don't think that should matter since I can access the router with the inside global address from the LAN side. I tried adding it anyway but it still doesn't show up.

code:
Gateway of last resort is isp.gateway.ip.address to network 0.0.0.0

S*    0.0.0.0/0 [1/0] via isp.gateway.ip.address
      50.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        isp.gateway.ip.address /28 is directly connected, FastEthernet4
L        inside.global.ip.address /32 is directly connected, FastEthernet4

bort
Mar 13, 2003

I think what you want is:
ip nat inside source list 1 interface FastEthernet4 overload

e: I'd also remove:
ip route 192.168.1.0 255.255.255.0 Vlan1
That's a connected route on the router and shouldn't need to be static.

bort fucked around with this message at 05:36 on Sep 20, 2012

mezoth
Aug 7, 2006

BelDin posted:

The traffic with jumbo MTU going to a switch without it would be the problem as far as I can tell. My understanding is that fragmentation doesn't happen at L2, the frame is just dropped as too large.

The distribution switches are 1500, so if I enable jumbo on them, all 1g and 10g links would have that MTU. Then I would have to change on the L2 switches downstream, etc.

Remember, if you do not set your MTU on the NIC for the server it will not send out packets above 1500 anyway. If you did set it higher then 1500 on the server, then the packets would drop at the first switch that did not have jumbo frames enabled - be it the nexus or the next switch in line. The few NICs that "auto-discover" MTU all do path-mtu-discovery to at least the first L3 hop - so it will max out at 1500 if your router is still only 1500 MTU.

BelDin
Jan 29, 2001

Ok, I'm officially stupid. I've been focused on deploying this for so long that it didn't occur to me to just control the frame size at the host level. Will CDP throw errors that I have to supress? Also, I thought that mtu mismatches were detected and ok on layer 3 links, not layer 2.

BelDin fucked around with this message at 06:30 on Sep 20, 2012

ate shit on live tv
Feb 15, 2004

by Azathoth

ofwolfandan posted:

The vlan network doesn't show up in the routing table. But I don't think that should matter since I can access the router with the inside global address from the LAN side. I tried adding it anyway but it still doesn't show up.

code:
Gateway of last resort is isp.gateway.ip.address to network 0.0.0.0

S*    0.0.0.0/0 [1/0] via isp.gateway.ip.address
      50.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        isp.gateway.ip.address /28 is directly connected, FastEthernet4
L        inside.global.ip.address /32 is directly connected, FastEthernet4

It's a problem with NATing as you correctly determined. There are two ways to do NAT. One is to explicitly assign interfaces as either outside/inside (ip nat inside/ip nat outside) The other way is to simply assign interfaces as nat enabled ( ip nat enable).

Change your interface NAT statements to ip nat enable, and your config should work fine. Alternatively do what bort told you to do, both should work, but I think the new way of doing it requires less configuration.

ofwolfandan
Aug 13, 2004

FACE THE PIE THAT SHOULD NOT BE

bort posted:

I think what you want is:
ip nat inside source list 1 interface FastEthernet4 overload

e: I'd also remove:
ip route 192.168.1.0 255.255.255.0 Vlan1
That's a connected route on the router and shouldn't need to be static.

Ok that was it. Thank you. I'm retarded.

bort
Mar 13, 2003

Give a thought to Powercrazy's recommendation. I didn't know that was available, and anything that makes NAT simpler is okay in my book.

mezoth
Aug 7, 2006

BelDin posted:

Ok, I'm officially stupid. I've been focused on deploying this for so long that it didn't occur to me to just control the frame size at the host level. Will CDP throw errors that I have to supress? Also, I thought that mtu mismatches were detected and ok on layer 3 links, not layer 2.

MTU mismatchs will always cause a frame drop - every "layer 3" link is *also* a layer2 link, never forget that. At a "layer 3" router boundary, the router can fragment the packet if the outbound interface that it is sending the packet on has a lower configured MTU then the packet size it is trying to send (see: ATM). Technically, this is true for a host as well - we just never consider this as it is part of the normal behavior for an endpoint.

Also, unless the host sends out (properly formatted) CDP messages, you will no get any CDP log messages. All mismatch log messages from CDP are a result of receiving a CDP packet on the interface reporting the error that the router about the configuration of the other side of the link.

I do not know about the nexus platform, but on IOS platforms if you enabled "jumbo" frames it actually did not raise the outbound MTU for packets generated / routed by that device, it only allowed the router/switch to accept and switch packets above the configured MTU up to the jumbo maximum for that platform. This methodology was very confusing to people, however.

ragzilla
Sep 9, 2005
don't ask me, i only work here


mezoth posted:

I do not know about the nexus platform, but on IOS platforms if you enabled "jumbo" frames it actually did not raise the outbound MTU for packets generated / routed by that device, it only allowed the router/switch to accept and switch packets above the configured MTU up to the jumbo maximum for that platform. This methodology was very confusing to people, however.

This hasn't matched my experience, I've always had to drop ip mtu on interfaces after raising system MTU on platforms where MTU is system wide to restore OSPF adjacencies after the interface IP MTU matched the system MTU.

Erwin
Feb 17, 2006

Okay, another dumb question, but I want to confirm my understanding coming from the Procurve world:

I have a VLAN 10 for VOIP with Polycom phones. The phones are configured explicitly for that vlan, so they tag their traffic. On the Procurves, ports have a primary vlan, but can also be a member of other tagged vlans. Trunks are something entirely different (aggregated links).

With Cisco, it sounds like if I want to plug a computer into a port and have it be on vlan 1, then disconnect it and connect a phone tagged on 10, it needs to be a trunk, even though trunks are defined as connecting two switches in the Cisco world. Is that right? Is that the best way to handle it? We're not daisy-chaining the computer through the phone, so it doesn't need to recognize both at the same time, but I don't want to reconfigure anything if I swap a computer out for a phone, and I want the phones on their own VLAN. Not that that's the end of the world, but I'm lazy.

jwh
Jun 12, 2002

Well, yes, but in practice, not necessary: the switchport voice vlan command, when applied to an access port, will also allow the switch to accept that tagged traffic.

ragzilla
Sep 9, 2005
don't ask me, i only work here


Erwin posted:

Okay, another dumb question, but I want to confirm my understanding coming from the Procurve world:

I have a VLAN 10 for VOIP with Polycom phones. The phones are configured explicitly for that vlan, so they tag their traffic. On the Procurves, ports have a primary vlan, but can also be a member of other tagged vlans. Trunks are something entirely different (aggregated links).

With Cisco, it sounds like if I want to plug a computer into a port and have it be on vlan 1, then disconnect it and connect a phone tagged on 10, it needs to be a trunk, even though trunks are defined as connecting two switches in the Cisco world. Is that right? Is that the best way to handle it? We're not daisy-chaining the computer through the phone, so it doesn't need to recognize both at the same time, but I don't want to reconfigure anything if I swap a computer out for a phone, and I want the phones on their own VLAN. Not that that's the end of the world, but I'm lazy.

Set 'switchport voice vlan 10' on the port and set the Polycoms to auto negotiate their voice VLAN through CDP.

I think it should still work even if they don't negotiate voice VLAN using CDP, the 'switchport voice vlan 10' command should let the tagged VLAN 10 traffic come into the port.

Erwin
Feb 17, 2006

Ok, neat, everything I read about voice VLAN was for Cisco phones, but it was all Cisco documentation. The Cisco documentation for Polycom phones said to use trunks, but also assumed daisy chaining.

Zuhzuhzombie!!
Apr 17, 2008
FACTS ARE A CONSPIRACY BY THE CAPITALIST OPRESSOR
May also want to run auto qos voip trust at the interface level. It will auto config mls qos on the switch if it's compatible.

Adbot
ADBOT LOVES YOU

BelDin
Jan 29, 2001

mezoth posted:

MTU mismatchs will always cause a frame drop - every "layer 3" link is *also* a layer2 link, never forget that. At a "layer 3" router boundary, the router can fragment the packet if the outbound interface that it is sending the packet on has a lower configured MTU then the packet size it is trying to send (see: ATM). Technically, this is true for a host as well - we just never consider this as it is part of the normal behavior for an endpoint.

So in theory, if I have one switch with a default mtu setting and another with jumbo frames set, as long as the hosts on each switch are at or lower than the lowest mtu in use by the switches, they should talk fine. Kinda like a low water mark governed by the hosts communicating with each other.

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply