|
The Newsroom started off with Cisco in season 1 and then moved to Avaya in season 2 and 3, sometimes with uncomfortably long pauses on the phones.
|
#
?
Jan 11, 2016 00:31
|
|
|
|
| # ? Apr 19, 2024 23:54 |
|
|
wolrah posted:We used 7940/60s everwhere when I started, but the terrible support for non-CUCM SIP in the 79x1s made us stop caring about Cisco and we've never looked back since. It's this. These are the phones that will not die, and will be shuffled from office to office in a never ending cycle of refurbishment until there's nothing but rats and roaches on this gay earth. ... and Norstar ICS key systems.
|
|
#
?
Jan 11, 2016 03:03
|
|
|
CrazyLittle posted:It's this. These are the phones that will not die, and will be shuffled from office to office in a never ending cycle of refurbishment until there's nothing but rats and roaches on this gay earth. edit: Also just remembered that most of the missing ones are from one site where the PoE switch decided the phones might want to try a lot more voltage. wolrah fucked around with this message at 03:59 on Jan 11, 2016 |
|
#
?
Jan 11, 2016 03:56
|
|
|
I still have poly501's in service. Kill me.
|
|
#
?
Jan 11, 2016 04:24
|
|
|
CrazyLittle posted:I still have poly501's in service. Kill me. Oh god, with that terrible special cord with the power socket in the middle. gently caress those things to hell and beyond. I went off on one of my sales guys once for selling a new site with those things years after the HD models were out, slimy fucker would do anything to make a sale. To make it worse this was a site where the customer supposedly already had a good network. I arrive to install and find ethernet cables dangling from the ceiling plugged in to computers. wolrah fucked around with this message at 15:29 on Jan 11, 2016 |
|
#
?
Jan 11, 2016 15:27
|
|
|
So, Cisco pages aren't entirely clear about this, but can I take an ASA OS (9.1.4 in this case) off a 5525X and drop it onto a 5510 without bricking it?
|
|
#
?
Jan 11, 2016 17:57
|
|
|
Slickdrac posted:So, Cisco pages aren't entirely clear about this, but can I take an ASA OS (9.1.4 in this case) off a 5525X and drop it onto a 5510 without bricking it? If you don't delete the existing image, it should be recoverable. The old ASAs are incompatible with the smp images used by the 5580 and X series.
|
|
#
?
Jan 11, 2016 18:22
|
|
|
Some older ASAs may need RAM upgrades to run newer code, there should almost certainly be a link with info about this and compatibility info (required ram/flash). For routers this is on the download page under the platform you're looking for. Edit: first Google hit for "ASA 5510 download" lists 9.1.6, but doesn't talks about ram/flash. Should be easily findable. falz fucked around with this message at 19:02 on Jan 11, 2016 |
|
#
?
Jan 11, 2016 19:00
|
|
|
falz posted:Some older ASAs may need RAM upgrades to run newer code, there should almost certainly be a link with info about this and compatibility info (required ram/flash). For routers this is on the download page under the platform you're looking for. The 5510 requires a RAM and flash upgrade to run 9.1.6.
|
|
#
?
Jan 11, 2016 20:04
|
|
|
CrazyLittle posted:I still have poly501's in service. Kill me. 
|
|
#
?
Jan 12, 2016 01:36
|
|
|
The 79x2/79x5 phones are fine, but the 79x1s can do wideband on later firmware. Good luck getting recent firmware to work on 3rd party SIP. Choose your poison, either bad hookswitches on the old ones, or bad flash on the new ones. I'd recommend the 8800 series but not sure what to say for 3rd party call control. 7800 Aka 'snoopy' is poo poo.
|
|
#
?
Jan 12, 2016 02:17
|
|
|
Slickdrac posted:So, Cisco pages aren't entirely clear about this, but can I take an ASA OS (9.1.4 in this case) off a 5525X and drop it onto a 5510 without bricking it? We've been upgrading our 5510s at work to 9.1(6)10 w/out any issues. Just use the non-smp version and make sure you have 1gig of ram in it. Also, the ASA-X 8.6 flash bug is the worst when there are hundreds spread across data centers still running that code ver.
|
|
#
?
Jan 12, 2016 05:41
|
|
|
Slickdrac posted:So, Cisco pages aren't entirely clear about this, but can I take an ASA OS (9.1.4 in this case) off a 5525X and drop it onto a 5510 without bricking it? ragzilla posted:If you don't delete the existing image, it should be recoverable. The old ASAs are incompatible with the smp images used by the 5580 and X series. I think ragzilla is saying the same thing, but you cannot take an image off a 5525-X and run it on a 5510. They will both run 9.1.x code, however the 5525-X and brethren run an image compiled specifically with SMP support.
|
|
#
?
Jan 12, 2016 18:27
|
|
|
So I'm not 100% comfortable with Juniper yet, still a lot of things it does that I am not sure about, so for any Juniper dudes itt help me out. We have two ex4550 setup as a collapsed core. We are running OSPF, have several SVI's with VRRP running and are running MSTP. A person added a new link between these switches which we will eventually bundle with the existing link. The interface he plugged the cable into was in the default vlan, with no configuration whatsoever. And when the link came up, we ended up with VRRP split brain scenario and we also lost our OSPF neighbors between the switches. So this caused a lot of issues, but what I want to know is "why." Yes I know he should have shut the interfaces, blah blah, he is a bad engineer. But why did that cause an issue?
|
|
#
?
Jan 13, 2016 18:07
|
|
|
Which spanning-tree are you running? Sounds like you had a layer 2 reconvergence.
|
|
#
?
Jan 13, 2016 20:54
|
|
|
chestnut santabag posted:Which spanning-tree are you running? Sounds like you had a layer 2 reconvergence. This sounds a likely culprit. A port flipped into blocking could kill the VRRP advertisements. Edit: As stated below me, having MSTP separating VLANs into different instances is a good idea. ChubbyThePhat fucked around with this message at 21:38 on Jan 13, 2016 |
|
#
?
Jan 13, 2016 20:59
|
|
|
Powercrazy posted:So I'm not 100% comfortable with Juniper yet, still a lot of things it does that I am not sure about, so for any Juniper dudes itt help me out. Only thing I can figure is default VLAN is on the same spanning tree instance as everything else and for whatever reason it blocked the actual trunk with the VLANs. Are your costs screwy between links? Or is the trunk multi 1-gig and he plugged in a 10GbE link? edit: If the links came back up then yes it was absolutely a reconvergence. I wasn't sure if that was the case or if you had him undo it to bring things online. Either way run your default VLAN on a separate instance of spanning tree to avoid this.
|
|
#
?
Jan 13, 2016 21:17
|
|
|
I called him and told him to unplug the link, then I shut the ports about 4 minutes later. During the time they were both up VRRP flapped a few times. I thought if you had two switches in the same MSTP domain, they automatically did per-vlan spanning tree port-states? Only difference is instead of sending a BPDU per vlan, they sent one BPDU per MSTP instance, however port-states are independent per vlan, so that a trunk that is blocking on one VLAN isn't blocking on all VLANs? Am I incorrect? For more detail about the specific situation. There is currently a single 10G port between the switches (xe-0/0/15 on both) that is trunking a specific list of vlans. The "default" vlan doesn't show up on this list, but I assume it's trunking it anyway. Two unconfigured ports were connected together, xe-0/0/13 and xe-0/0/21 but the problems started as soon as the link on 13 came up. user@ds1a.nj01> show log messages.0.gz | find "Jan 12 13:41:59" Jan 12 13:41:59 ds1a.nj01 chassism[1244]: link 13 SFP receive power low alarm set Jan 12 13:41:59 ds1a.nj01 chassism[1244]: link 13 SFP receive power low warning set Jan 12 13:43:04 ds1a.nj01 chassism[1244]: link 13 SFP receive power low alarm cleared Jan 12 13:43:04 ds1a.nj01 chassism[1244]: link 13 SFP receive power low warning cleared Jan 12 13:43:04 ds1a.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.172 (local address 172.16.7.254) became VRRP master for group 172 with master reason masterNoResponse Jan 12 13:43:04 ds1a.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.901 (local address x.x.x.x) became VRRP master for group 92 with master reason masterNoResponse Jan 12 13:43:04 ds1a.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.900 (local address y.y.y.y) became VRRP master for group 91 with master reason masterNoResponse Jan 12 13:43:24 ds1a.nj01 chassism[1244]: phy_nlp2042_10g_mode_cfg: 10G mode init for MACSEC PHY of port 21 Jan 12 13:43:26 ds1a.nj01 chassism[1244]: link 21 SFP receive power low alarm set Jan 12 13:43:26 ds1a.nj01 chassism[1244]: link 21 SFP receive power low warning set Jan 12 13:43:37 ds1a.nj01 rpd[1267]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.3.255.253 (realm ospf-v2 vlan.50 area 0.0.0.0) state changed from Full to Down due to InActiveTimer (event reason: neighbor was inactive and declared dead) Jan 12 13:46:55 ds1a.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.172 (local address 172.16.7.254) became VRRP backup for group 172 Jan 12 13:46:56 ds1a.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.901 (local address x.x.x.x) became VRRP backup for group 92 Jan 12 13:46:56 ds1a.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.900 (local address y.y.y.y) became VRRP backup for group 91 Jan 12 13:46:56 ds1a.nj01 mib2d[1266]: SNMP_TRAP_LINK_DOWN: ifIndex 584, ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/13 Jan 12 13:47:02 ds1a.nj01 rpd[1267]: RPD_OSPF_NBRUP: OSPF neighbor 10.3.255.253 (realm ospf-v2 vlan.50 area 0.0.0.0) state changed from Init to ExStart due to 2WayRcvd (event reason: neighbor detected this router) Jan 12 13:47:03 ds1a.nj01 rpd[1267]: RPD_OSPF_NBRUP: OSPF neighbor 10.3.255.253 (realm ospf-v2 vlan.50 area 0.0.0.0) state changed from Exchange to Full due to ExchangeDone (event reason: DBD exchange of slave completed) Jan 12 13:47:03 ds1a.nj01 chassism[1244]: link 13 SFP receive power low alarm set Jan 12 13:47:03 ds1a.nj01 chassism[1244]: link 13 SFP receive power low warning set It's peer. These are synced via so NTP Jan 12 13:43:03 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.122 (local address 10.13.122.253) became VRRP master for group 124 with master reason masterNoResponse Jan 12 13:43:04 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.122 (local address 10.10.122.253) became VRRP master for group 123 with master reason masterNoResponse Jan 12 13:43:04 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.900 (local address y.y.y.y) became VRRP master for group 90 with master reason masterNoResponse Jan 12 13:43:04 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.160 (local address 10.99.162.253) became VRRP master for group 162 with master reason masterNoResponse Jan 12 13:43:04 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.160 (local address 10.99.161.253) became VRRP master for group 160 with master reason masterNoResponse Jan 12 13:43:04 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.122 (local address 10.99.122.253) became VRRP master for group 122 with master reason masterNoResponse Jan 12 13:43:04 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_MASTER: Interface vlan.50 (local address 10.3.255.253) became VRRP master for group 50 with master reason masterNoResponse Jan 12 13:43:39 ds1b.nj01 chassism[1244]: link 13 SFP receive power low alarm cleared Jan 12 13:43:39 ds1b.nj01 chassism[1244]: link 13 SFP receive power low warning cleared Jan 12 13:43:39 ds1b.nj01 rpd[1267]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.3.255.254 (realm ospf-v2 vlan.50 area 0.0.0.0) state changed from Full to Down due to InActiveTimer (event reason: neighbor was inactive and declared dead) Jan 12 13:43:47 ds1b.nj01 chassism[1244]: xcvr_cache_eeprom XCVR link 24 pic_slot 0 unplugged Jan 12 13:43:47 ds1b.nj01 chassism[1244]: Return code 1 not EOK: ethswitch_eth_link_state (340) Jan 12 13:43:47 ds1b.nj01 chassism[1244]: : 24 command type 103 failed, for ethswitch_eth_getinfo Jan 12 13:43:47 ds1b.nj01 chassism[1244]: ETH:if_ethgetinfo() returns error Jan 12 13:43:47 ds1b.nj01 chassism[1244]: Return code 1 not EOK: ethswitch_eth_link_state (340) Jan 12 13:43:47 ds1b.nj01 chassism[1244]: : 24 command type 103 failed, for ethswitch_eth_getinfo Jan 12 13:43:47 ds1b.nj01 chassism[1244]: ETH:if_ethgetinfo() returns error Jan 12 13:43:47 ds1b.nj01 chassism[1244]: Return code 1 not EOK: ethswitch_eth_link_state (340) Jan 12 13:43:47 ds1b.nj01 chassism[1244]: : 24 command type 103 failed, for ethswitch_eth_getinfo Jan 12 13:43:47 ds1b.nj01 chassism[1244]: ETH:if_ethgetinfo() returns error Jan 12 13:43:47 ds1b.nj01 chassism[1244]: validate_configuration (625) config validation failed pic 0xf04b port 24 xcvr_type 0 AN 0 speed 3 duplex 0 Jan 12 13:43:47 ds1b.nj01 chassism[1244]: ifcm_ifd_remove_vector: ifd xe-0/0/24 is_vcp 0 peer master Jan 12 13:43:58 ds1b.nj01 chassism[1244]: phy_nlp2042_10g_mode_cfg: 10G mode init for MACSEC PHY of port 21 Jan 12 13:44:25 ds1b.nj01 chassism[1244]: link 21 SFP receive power low alarm set Jan 12 13:44:25 ds1b.nj01 chassism[1244]: link 21 SFP receive power low warning set Jan 12 13:46:55 ds1b.nj01 mib2d[1266]: SNMP_TRAP_LINK_DOWN: ifIndex 580, ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/13 Jan 12 13:46:55 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.160 (local address 10.99.161.253) became VRRP backup for group 160 Jan 12 13:46:55 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.50 (local address 10.3.255.253) became VRRP backup for group 50 Jan 12 13:46:56 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.122 (local address 10.10.122.253) became VRRP backup for group 123 Jan 12 13:46:56 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.900 (local address y.y.y.y) became VRRP backup for group 90 Jan 12 13:46:56 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.122 (local address 10.99.122.253) became VRRP backup for group 122 Jan 12 13:46:56 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.160 (local address 10.99.162.253) became VRRP backup for group 162 Jan 12 13:46:56 ds1b.nj01 vrrpd[1268]: VRRPD_NEW_BACKUP: Interface vlan.122 (local address 10.13.122.253) became VRRP backup for group 124 Jan 12 13:46:58 ds1b.nj01 chassism[1244]: link 13 SFP receive power low warning set Jan 12 13:47:04 ds1b.nj01 chassism[1244]: link 13 SFP receive power low alarm set ate shit on live tv fucked around with this message at 22:36 on Jan 13, 2016 |
|
#
?
Jan 13, 2016 22:05
|
|
|
Nope, the whole point of MTSP is to have one tree for a whole bunch of VLANs assigned to a domain - there's nothing per-VLAN about it as it's all per-domain. If you want to selectively block VLANs on an interface, then you have to put those VLANs into a different domain and manipulate spanning-tree costs etc. for that domain.
|
|
#
?
Jan 13, 2016 22:51
|
|
|
chestnut santabag posted:Nope, the whole point of MTSP is to have one tree for a whole bunch of VLANs assigned to a domain - there's nothing per-VLAN about it as it's all per-domain. This sounds wrong. Because if you want lots of vlans assigned to a switch, you could just use 802.1w (up to the switch maximum). The disadvantage is that whenever one vlan needs to reconverge, all vlans need to reconverge. This was solved by Cisco in a non-scalable way by PVST+ (A separate STP instance per vlan). Now as datacenters increase in the number of vlans and decrease in the number of switches you can't have 1000+ instances of spanning tree running, thus MSTP was invented so that the amount of control traffic (BPDUs) was decreased, you are running a single spanning tree process, and you still get the advantage of having one misbehaving VLAN not affecting the other 1000.
|
|
#
?
Jan 13, 2016 23:37
|
|
|
How do I tell how many subnets of length x I could make within a given IP range? Do I just have to divide the total length by the subnet length, or is there a quicker way to do it?
|
|
#
?
Jan 14, 2016 00:53
|
|
|
Let's say you want to know how many /24 networks are in a /18. 24 - 18 = 6. The largest number you can create with six bits is 63 (1+2+4+8+16+32), so there are 64 /24 networks in a /18. Basically, just figure out how many bits you have between your network mask (/18), your subnet mask is (/24), and how big of a number you can make with the difference.
|
|
#
?
Jan 14, 2016 03:31
|
|
|
Well that's certainly a lot simpler. Thanks.
|
|
#
?
Jan 14, 2016 03:33
|
|
|
Filthy Lucre posted:Let's say you want to know how many /24 networks are in a /18. 24 - 18 = 6. The largest number you can create with six bits is 63 (1+2+4+8+16+32), so there are 64 /24 networks in a /18. Stated another way, the number of subnets of length x in a prefix of length y is 2(x-y). Applied to your example of an /18 divided into /24s: 2(24-18) = 26 = 64. No need to count in binary  This works exactly the same for IPv6 as it does for IPv4.
|
|
#
?
Jan 14, 2016 04:33
|
|
|
i just count on my fingers.
|
|
#
?
Jan 14, 2016 04:34
|
|
|
Powercrazy posted:So I'm not 100% comfortable with Juniper yet, still a lot of things it does that I am not sure about, so for any Juniper dudes itt help me out. I'd check the MST configuration on those two switches. To me it sounds like you have an inconsistency and thus spanning-tree is operating using the CST with the two switches thinking they are in separate MST regions. This works fine until someone makes a change (like connecting a link...). It's been a long time and I can't find reference to it, but if I recall the CST operates like 802.1d as it is responsible for, among other things, backwards compatibility.
|
|
#
?
Jan 14, 2016 05:12
|
|
|
adorai posted:i just count on my fingers. v4 on your fingers, v6 on the toes. count em if you got em
|
|
#
?
Jan 14, 2016 05:19
|
|
|
Just deal with subnetting for so long you memorize all of them
|
|
#
?
Jan 14, 2016 09:12
|
|
|
cheese-cube posted:v4 on your fingers, v6 on the toes. count em if you got em v6 just standardize on nibble length subnets, hooray everything's the same! /48 to the org, /52 to the region, /60 to the site. Move middle region boundary as appropriate (but most people don't have more than 16 regions, or 256 sites in a region). Sometimes you might assign a site an extra /60 but it's fairly rare unless you do a whole lot of point-to-point where you're reserving the whole /64.
|
|
#
?
Jan 14, 2016 15:41
|
|
|
abigserve posted:I'd check the MST configuration on those two switches. To me it sounds like you have an inconsistency and thus spanning-tree is operating using the CST with the two switches thinking they are in separate MST regions. This works fine until someone makes a change (like connecting a link...). This sounds correct based on my understanding of MSTP interacting with switches in non-mstp domains. Now what are best practices for putting switches in an MSTP region? Lets say I have 2 core switches and 6 leaf switches. Should they all be in the same MSTP region assuming they are compatible? What attributes need to match on each switch to make sure they are in the same MSTP domain. How do I verify?
|
|
#
?
Jan 14, 2016 18:08
|
|
|
ragzilla posted:v6 just standardize on nibble length subnets, hooray everything's the same! /48 to the org, /52 to the region, /60 to the site. Move middle region boundary as appropriate (but most people don't have more than 16 regions, or 256 sites in a region). Sometimes you might assign a site an extra /60 but it's fairly rare unless you do a whole lot of point-to-point where you're reserving the whole /64. I thought /64 P2P links was the recommended way to do it especially with gear that may have CAM table limitations with v6 addresses.
|
|
#
?
Jan 14, 2016 18:11
|
|
|
Powercrazy posted:I thought /64 P2P links was the recommended way to do it especially with gear that may have CAM table limitations with v6 addresses. Unless you have SeND (RFC3971) I wouldn't configure /64 on an Internet accessible interface, my practice is to reserve the /64 and configure a /126 (because I like to use ::1 and ::2), but I also have a /32 worth of space so I can afford some profligate wastage on p2ps when I'm assigning a /48 per PE. This advice may vary if you have platforms like 3560/3750 classic which behave oddly with >/64 masks.
|
|
#
?
Jan 14, 2016 18:56
|
|
|
I have a core switch with like 16 edge switches plugged into it. I have a MAC address of a device pulling a huge amount of bandwidth. What would be the most efficient commands to find out which port the mac address is on?
|
|
#
?
Jan 15, 2016 16:49
|
|
|
Zero VGS posted:I have a core switch with like 16 edge switches plugged into it. I have a MAC address of a device pulling a huge amount of bandwidth. What would be the most efficient commands to find out which port the mac address is on? show mac-address-table
|
|
#
?
Jan 15, 2016 16:51
|
|
|
Er, I should specify it's HP Procurves... I don't see a mac-address-table command. I did "show mac-address [the mac address I want]" and it returns Port 19 and VLAN 16, I assume then there's a command to figure out the IP of whatever switch is on Port 19 so I can then Telnet into that and run show mac again?
|
|
#
?
Jan 15, 2016 16:56
|
|
|
Zero VGS posted:Er, I should specify it's HP Procurves... I don't see a mac-address-table command. I did "show mac-address [the mac address I want]" and it returns Port 19 and VLAN 16, I assume then there's a command to figure out the IP of whatever switch is on Port 19 so I can then Telnet into that and run show mac again? Well, on Cisco devices you'd use "show arp" (maybe "show ip arp" depending on OS, don't remember) to see that. I don't know about Procurves. 
|
|
#
?
Jan 15, 2016 17:04
|
|
|
I figured it out, "show lldp info remote" tells me the names of all the switches in the ports, then I was able to telnet into the edge switch and find the true port that MAC was connected to.
|
|
#
?
Jan 15, 2016 17:17
|
|
|
Zero VGS posted:I figured it out, "show lldp info remote" tells me the names of all the switches in the ports, then I was able to telnet into the edge switch and find the true port that MAC was connected to. TIL
|
|
#
?
Jan 15, 2016 17:45
|
|
|
Zero VGS posted:I figured it out, "show lldp info remote" tells me the names of all the switches in the ports, then I was able to telnet into the edge switch and find the true port that MAC was connected to. Many devices don't speak lldp and so in that case you want to get the layer 2 to layer 3 mapping. Show mac-address then show arp on the router of the network the host you are interested in. Find the MAC that and match it to the arp entry.
|
|
#
?
Jan 15, 2016 18:05
|
|
|
|
| # ? Apr 19, 2024 23:54 |
|
|
HP switches should have their own analogous command that displays the mac address table from the switch. On Dell it's something ridiculous like "show bridge address-table". Meanwhile "show arp" may only show the arp table from devices that have directly tried to talk to the switch's IP fabric instead of the switching fabric.
|
|
#
?
Jan 15, 2016 21:42
|
|