Solved

Connecting HP Switch with Fiber

Posted on 2014-04-03
10
1,004 Views
Last Modified: 2014-04-08
I am connecting a new switch to our Core Switch with a single Fiber / Mini GBIC  / LC Connectors.

I can see the uplink is live on the ports and show int shows that there is broadcast traffic pinging around.

I have given the DEFAULT VLAN an ip and ip default gateway.

On the Core switch the 4 x Modules are trunked, i trunked the 4 x modules on the new switch (Although only one module is in place)

I cannot seem to connect the switch to our network or ping the new one.

If i only have one Fiber Uplink is a trunk needed?

Cheers
0
Comment
Question by:zander1
  • 5
  • 5
10 Comments
 
LVL 25

Expert Comment

by:Zephyr ICT
ID: 39974791
On HP trunking is needed if you want VLANs to be available on the new switch, are you sure the same VLANs are available on the new switch?

If you connect your new switch on the core switch with a patch cable in a normal port, can you then ping the core switch from the new switch? (disconnect fiber first) ...
0
 

Author Comment

by:zander1
ID: 39975039
I connected with a Lan Cable and both switches can Ping each other. I setup the Vlan and assigned an IP but cannot ping the IP of the vlan.

A little confused which should be tagged on untagged

Cheers
0
 
LVL 25

Expert Comment

by:Zephyr ICT
ID: 39975537
If you trunk 2 switches together you should set the VLANs tagged to transfer them to the other switch, if VLAN1 is untagged you can leave it untagged on the trunk as well ... If you really get stuck you can post the config of the switch (sanitised) so we can take a look at it.
0
 

Author Comment

by:zander1
ID: 39982673
Thanks for you help.

So Tagged for Switch to Switch and Untagged for the ports to the end devices?..

Here is the rc on the two switches.

I connected the them with a Cat5e patch cable and just trunked the two interfaces (H15/2)

Core Switch       trunk H15 Trk5 LACP
Switch 2             trunk 2 Trk5 LACP


I am not sure why it would not work with the fiber.

Question - I had four trunks on the Core switch so called the new Trunk Trk5 on both switches. Do i need to match the trk no. Could I not name the btrunk Trk1 on Switch 2?

Question - Did the Trunk not work on fiber because it was as follows: (I.E 4 x interface ports on the Core but only 1 x on Switch 2)

Core Switch       trunk J21-J24 Trk4 LACP
Switch 2             trunk 2 Trk4 LACP


Thanks in advance.
ZND



###Running Configs###



Core Switch

; J8698A Configuration Editor; Created on release #K.15.02.0005

hostname "###"
module 1 type J8702A
module 2 type J8705A
module 3 type J8702A
module 4 type J8705A
module 6 type J8705A
module 8 type J8705A
module 10 type J8705A
module 11 type J9538A
module 12 type J9538A
interface H21
   disable
exit
interface H22
   disable
exit
interface H23
   disable
exit
interface H24
   disable
exit
trunk B21-B24 Trk1 LACP
trunk D21-D24 Trk2 LACP
trunk F21-F24 Trk3 LACP
trunk J21-J24 Trk4 LACP
trunk H15 Trk5 LACP
ip routing
snmpv3 enable
snmpv3 restricted-access
vlan 1
   name "DEFAULT_VLAN"
   untagged F13-F20,H21-H24
   ip address 172.31.31.2 255.255.255.0
   tagged L1,Trk1-Trk5
   no untagged A1-A24,B1-B20,C1-C24,D1-D20,F1-F12,H1-H14,H16-H20,J1-J20,K1-K8,L2
-L8
   exit
vlan 134
   name "HAR Servers"
   untagged A1-A24,B1,B3-B20,C1-C24,H1-H14,H16-H20,J1-J20,K1-K8,L2-L8
   ip helper-address 192.168.135.212
   ip helper-address 192.168.135.219
   ip address 192.168.134.2 255.255.255.0
   tagged L1,Trk1-Trk5
   exit
vlan 3
   name "LND Servers"
   untagged F1-F12
   ip address 192.168.135.2 255.255.255.0
   tagged L1,Trk1-Trk5
   exit
vlan 1000
   name "1G Internet"
   untagged D1-D20
   ip address ###.###.###.### 255.255.255.224
   exit
vlan 143
   name "HAR Avaya Phones"
   ip address 192.168.143.1 255.255.255.0
   tagged L1,Trk1-Trk5
   exit
vlan 137
   name "Wireless"
   untagged B2
   ip helper-address 192.168.135.219
   ip address 192.168.137.3 255.255.255.0
   tagged L1,Trk1-Trk5
   exit
ip route 0.0.0.0 0.0.0.0 192.168.135.190 distance 150
ip route 0.0.0.0 0.0.0.0 192.168.135.192
ip route 10.100.100.0 255.255.255.0 192.168.135.1
ip route 172.17.3.0 255.255.255.0 192.168.135.1
ip route 192.168.0.0 255.255.255.0 192.168.135.134
ip route 192.168.1.0 255.255.255.0 192.168.135.134
ip route 192.168.2.0 255.255.255.0 192.168.135.134
ip route 192.168.3.0 255.255.255.0 192.168.135.134
ip route 192.168.5.0 255.255.255.0 192.168.135.134
ip route 192.168.8.0 255.255.255.0 192.168.135.134
ip route 192.168.9.0 255.255.255.0 192.168.135.134
ip route 192.168.16.0 255.255.252.0 192.168.135.134
ip route 192.168.24.0 255.255.255.0 192.168.135.134
ip route 192.168.32.128 255.255.255.128 192.168.135.134
ip route 192.168.100.0 255.255.255.0 192.168.135.134
ip route 192.168.136.0 255.255.255.0 192.168.135.134
ip route 192.168.137.0 255.255.255.0 192.168.135.1
ip route 192.168.138.0 255.255.255.0 192.168.135.1
ip route 192.168.139.0 255.255.255.0 192.168.135.1
ip route 192.168.140.0 255.255.255.0 192.168.135.1
ip route 192.168.141.0 255.255.255.128 192.168.135.1
ip route 192.168.141.128 255.255.255.192 192.168.135.1
ip route 192.168.141.192 255.255.255.192 192.168.135.1
ip route 192.168.142.0 255.255.255.0 192.168.135.1
ip route 192.168.143.0 255.255.255.0 192.168.135.1
ip route 192.168.144.0 255.255.255.0 192.168.135.1
ip route 192.168.160.0 255.255.224.0 192.168.135.134
ip route 192.168.176.0 255.255.254.0 192.168.135.134
ip route 192.168.178.0 255.255.255.0 192.168.135.134
ip route 192.168.232.0 255.255.255.128 192.168.135.134
ip route 192.168.233.0 255.255.255.0 192.168.135.134
snmp-server community "public" unrestricted
snmpv3 user "initial"
snmpv3 user "rn"
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4
spanning-tree Trk4 priority 4
spanning-tree Trk5 priority 4
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
password operator



Switch 2

hostname "Switch Avaya"
module 1 type J86xxA
module 3 type J8694A
trunk 2 Trk5 LACP
ip default-gateway 172.31.31.1
vlan 1
   name "DEFAULT_VLAN"
   untagged A1-A4
   ip address 172.31.31.5 255.255.255.0
   tagged 1,Trk5
   no untagged 3-24
   exit
vlan 143
   name "HAR Avaya Phones"
   untagged 1,3-24
   ip helper-address 192.168.135.212
   tagged Trk5
   no ip address
   exit
snmp-server community "public" unrestricted
spanning-tree Trk5 priority 4
0
 
LVL 25

Accepted Solution

by:
Zephyr ICT earned 500 total points
ID: 39982718
Question - I had four trunks on the Core switch so called the new Trunk Trk5 on both switches. Do i need to match the trk no. Could I not name the btrunk Trk1 on Switch 2?

No, the trunk name is just that, trunk name, they don't need to match.

Question - Did the Trunk not work on fiber because it was as follows: (I.E 4 x interface ports on the Core but only 1 x on Switch 2)

well, that could be a problem, if you have 4 connections on the one switch in the same LACP group and only 2 on the other (unless 2 of the 4 ports were not connected to something maybe) ... You should try to mimic the setup/config of the ethernet trunks and keep the amount of ports in the trunk the same.
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Author Comment

by:zander1
ID: 39985610
Think we are almost there.

The Existing Trunk is in place (Trk5) this is just patched to the core switch.

Issue: When the existing trunk is in place and then the Fiber is plugged in to Switch 2 our network goes down. Like completely!... I have no idea why....?????

It was a mix up when the tech the other end connected it.

Any ideas?
0
 
LVL 25

Expert Comment

by:Zephyr ICT
ID: 39985637
Is the other connection (ethernet) still connected? ... Might be creating a loop somewhere, make sure atleast STP (spanning-tree) is enabled ...
0
 

Author Comment

by:zander1
ID: 39985649
Yes the ethernet was still connected.

The Trunk was still in place on the Core Switch

trunk J21-J24 Trk4 LACP

But not on Switch 2. I thought it would have been a benign connection being that the trunk was not configured on the other end.

Clearly not.
0
 
LVL 25

Expert Comment

by:Zephyr ICT
ID: 39985655
Well, there seemed to be some traffic going over the trunk, causing the loop ... So, yes, be carefull with that ;-)
0
 

Author Closing Comment

by:zander1
ID: 39985695
Thanks
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

Suggested Solutions

This is an article about my experiences with remote access to my clients (so that I may serve them) and eventually to my home office system via Radmin Remote Control. I have been using remote access for over 10 years and have been improving my metho…
Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now