Wired Intelligent Edge (Campus Switching and Routing)

Reply
Occasional Contributor II

Configuration review for Aruba 2930F switches

Hi there,

 

I have 3 Aruba 2930F switches (1 x 28-port and 2 x 48-port).

 

I have configured all the switches with the same configuration (see attached). the only differences being the model, no. of ports,switch name and the ip addresses for each switch on the 2 vlans.

 

I have had the 2 48 port switches running on the network for a number of weeks now and I have been getting regular "Warnings and Info" entries in the log for the following;

 

1) Port "x" PD MPS Absent Indication

2) Port "x" is now offline. followed by Port "x" blocked by STP, followed by Port "x" is now online. - Where "x" is the same number in all of the notifications. This is happening for multiple ports? Am I correct this has something to with the switch not being able to "initially" detect the end-point device?

3) Port "x" PD MPS Absent Indication - the switch no longer detects a device on port "x". Device has been disconnected, powered down or stopped functioning.

The above is happening on all of the switches for different ports.

 

Some further info...

 

1) I can ping all the switches on each of their assigned vlan IP addresses. The only exception is the switch zeus (10.1.0.23/10.1.1.5) but I am pretty sure this is because the cable has been removed which links it to the network so not too concerned about that just yet.

2) I can connect to all the switches via web gui and putty (telnet) with the exception of zeus (10.1.0.23/10.1.1.5 and 10.1.0.14/10.1.1.3). as mentioned before ignore the 10.1.0.23 device for now as it isn't connected to the network. I am stumped by not being able to connect to the 10.1.0.14 switch because i know for a fact the server I'm logging into is connected directly to it so it is obviously working, I just can't connect via the webgui or putty (telent).

 

My real query here though is.... what is the best way to connect these switches together. Refer to attached diagram, My intention is to have one connection going from each switch to 10.1.0.23 (intended "Core switch") so there will be an uplink to each of these switches rather then daisy chaining the switches together... from what I've read daisy chaining is not recommended.

 

If you have any thoughts on the configuration file, network design and potential improvements, recommendations on making things better that would be appreciated.

 

Thanks,

 

 

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

Are you sure you dont have a link connected between any of the 3 edge switches? This could be a genuine STP event. If you run the command "show lldp i r" from each of the 3 edge switches what output do you see? Also what is the output of "show span"?

 

The way you have the switches connected in the diagram is Ok except it doesnt provide any redundancy for uplink failure. You could connect edge 1 & 3 to 2 and let STP (assuming configured correctly) block these links under normal opperation. Then if an uplink fails STP will reconverge and unblock the relevant port.

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

I have reviewed the port configs on the 3Com switch which is the core switch for the network and discovered that some of the ports weren't configured for both VLANs. I moved the connections to ports which I reconfigured for both vlans. I ran show lldp i r prior to this but forgot to save the output in the text file. Now that the connections have been moved here is the output from show lldp i r.... I am pretty sure the output is different from the first time I ran show lldp i r  as there are fewer entries but I am still not able to connect to the 10.1.0.23 switch. I need to go to the client site and check the switch physically.

 

10.1.0.14
 
 LLDP Remote Devices Information

  LocalPort | ChassisId          PortId             PortDescr SysName
  --------- + ------------------ ------------------ --------- ------------------
  6         | 00 23 24 cf 4d 5a  00 23 24 cf 4d 5a
  23        | 00 23 24 f9 f8 0f  00 23 24 f9 f8 0f
  40        | e0 4f 43 5a 61 08  e0 4f 43 5a 61 08
 
10.1.0.20

  LLDP Remote Devices Information

  LocalPort | ChassisId          PortId             PortDescr SysName
  --------- + ------------------ ------------------ --------- ------------------
 
10.1.0.21
 
 LLDP Remote Devices Information

  LocalPort | ChassisId          PortId             PortDescr SysName
  --------- + ------------------ ------------------ --------- ------------------
  25        | MOFA_DIST_SW01     GigabitEthernet0/3 

 

The switch connection under 10.1.0.21 is a switch in another rack connecting all the servers to the network, I am pretty sure there is only 1 connection going from this switch to the switches in the other rack but I suspect that this is "daisy-chained" to one of the downstream switches rather than the core switch so will need to check that as well.

 

Any insight on the above would be appreciated.

 

Thanks,

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

I will review the above but when you say you cant connect to 10.1.0.23 are you doing this remotely? Via VPN? What if you first SSH to 10.1.0.20 and then initiate a session to 10.1.0.23? does this work?

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

The output varies between the switches are they all the same type? Do they all have hostnames configured?

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

I will review the above but when you say you cant connect to 10.1.0.23 are you doing this remotely? Via VPN? What if you first SSH to 10.1.0.20 and then initiate a session to 10.1.0.23? does this work?

 

Yes I connect remotely via VPN which was never a problem until last weekend when we tried to replace the 3Com unit with the new 28 port Aruba as the Core. I have not tried the SSH option from one of the other switches to the 10.1.0.23 unit so will give that a shot.

 

The output varies between the switches are they all the same type? Do they all have hostnames configured?

 

3Com 4500 PWR 24 port PoE (Core switch) connected to

   HP 2530G 48 port PoE

   Aruba 2930F 48 Port PoE

   Aruba 2930F 48 Port PoE

   Aruba 2930F 28 port PoE (this is intedned to be the new core switch replacing the 3Com unit above)

HP V1910-24G - This is the switch labelled as MOFA in the lldp out put above. I don't know the Ip address of this... waiting for that info. I need to replace this unit with another HP 2530G switch which I have yet to configure.

To the best of my knowledge the Aruba's and HP switches have a single connection to the 3Com unit.

 

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

What if you first SSH to 10.1.0.20 and then initiate a session to 10.1.0.23? does this work?

 

I can ssh from 10.1.0.20 to 10.1.0.21 and 10.1.0.14 but ssh to the core switch 10.1.0.13 doesn't work there is a key exchange failure... but i think this is because of the way it has been setup... i don't want to spend too much time fiddling with this time because it is going to be replaced... once I fix the other issues.

 

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

So you cant SSH to .23 from the other switches? What about telnet? or PING? 

 

Can you please summarize what your actual issue is? Is it just that you cannot manage .23 via your remote session?

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

I had 2 concerns;

 

Firstly;

 

When we migrated all the connections off the old 3Com, we lost connectivity to our PBX for VoIP. This was eventually remedied by reconnecting the 3Com unit back to the network.

 

What I couldn't understand about this was that the new Aruba's were configured for both VLAN's on every port which was a change from the way the 3Com was setup which was a per port config, that resulted in us having to plug specific devices into specific ports on the 3Com unit. So I was surprised the migration to the new Aruba did not work. Upon migrating back to the 3Com core I was then not able to connect to the 10.1.0.23 unit. I double checked the connections and they "physically" appear to be fine.

 

Secondly, I wasn't too sure whether the configurations I had in place for the Aruba and HP switches was in fact correct....

 

My intention was to have the new 28 port Aruba operate as a layer 3 core switch and then have all the others route and transmit traffic (layer 2) through this switch... I had my reservations that this was in fact the correct config because that would mean the core switch would be doing all the work which is why I changed the config of all the switches to match that of the 28 port Aruba Core switch.

 

The last thing I was not sure about was correct was the interconnection between the core switch and all the other switch, googling did however confirm that the way I had them connected was in fact correct which is an uplink from each downstream switch to the Core switch. I will at some point add redundancy to the interlinks but I first want to get things working with the new Aruba Core switch in place.

 

I just don't know what I'm doing wrong in terms of the config assuming of course it is the config... which appears to be correct because the two 48 port Arubas and the 48 port HP switch are working fine and there have been no complains from users etc.

I've only just recently taken on networking at this level and my only previous experience was just basic knowledge of networks, subnets, routing etc.

Occasional Contributor II

Re: Configuration review for Aruba 2930F switches

Ok so i discovered that the new Aruba switch has gone back to a factory deault? I have no idea how this happened. Anyway I have uploaded the config and the switch is running ok.

 

The problem I now have is nothin on the VoIP network is contactable (servers) and none of the VoIP phones are getting an IUP address from the DHCP server.

 

All the switches are configured with ip addresses for both voice and data vlans, but I cannot ping anything on the voip vlan... which I could do with the old switch?

So I'm assuming there is some kind of routing issue on the new core switch... any ideas?

 

I've attached the config for the core switch. this is the same for all the switches except the model names, ip addresses etc for the vlans.

 

Thanks,

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: