Cloud Managed Networks

Hi, sorry for my question, i am a newbie.

We have renewed a Stack (3x 2930f) in our Office and a single Switch (2930f) in our Branch.

Our old switches was Cisco SG 500.

The switches works well but the VOIP Phones in our Branch are not working.

Can anywone translate the cisco config for me?

config-file-header

switch5aa59b

v1.3.0.62 / R750_NIK_1_3_647_260

CLI v1.0

set system mode router queues-mode 8

file SSD indicator encrypted

@

ssd-control-start

ssd config

ssd file passphrase control unrestricted

no ssd file integrity control

ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0

!

no cdp run

vlan database

vlan 130,300

exit

voice vlan oui-table add 0001e3 Siemens_AG_phone________

voice vlan oui-table add 00036b Cisco_phone_____________

voice vlan oui-table add 00096e Avaya___________________

voice vlan oui-table add 000fe2 H3C_Aolynk______________

voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone

voice vlan oui-table add 00d01e Pingtel_phone___________

voice vlan oui-table add 00e075 Polycom/Veritel_phone___

voice vlan oui-table add 00e0bb 3Com_phone______________

no lldp run

bonjour interface range vlan 1

hostname switch5aa59b

no passwords complexity enable

username cisco password encrypted 7af78c911d5b48bea1dc2449d9d89513abeb4be5 privi                     lege 15

ip ssh server

!

interface vlan 1

 ip address 10.11.10.101 255.255.255.0

 no ip address dhcp

!

interface vlan 130

 name LKH

 ip address 10.130.60.235 255.255.255.0

!

interface gigabitethernet1/1/6

 switchport trunk native vlan 130

!

interface gigabitethernet1/1/9

 switchport trunk native vlan 130

!

interface gigabitethernet1/1/10

 switchport trunk native vlan 130

!

interface gigabitethernet1/1/14

 switchport trunk native vlan 130

!

interface gigabitethernet1/1/20

 switchport trunk native vlan 130

!

interface gigabitethernet1/1/25

 switchport trunk native vlan 130

!

exit

ip default-gateway 10.11.10.254

switch5aa59b#

Thanks a lot!

Renzi

Hi Rene!

What is the configuration of VLAN tagging on uplink/downlink involved ports? In other terms the 3xAruba 2930F (VSF stack) and the single Aruba 2930F at branch location are supposed to be connected through an uplink (single link? aggregated ports?)...how involved ports are tagged?

Perform a show vlan port <x> detail (x could be a single physical interface if the link is a single link or it could be the logical aggregated interface if the link is made of aggregated single links as in case of Port Trunking) on both ends.

The Cisco had VLAN 1 (Default) with SVI of Subnet 10.11.10.0/24, VLAN 130 with SVI of Subnet 10.130.60.0/24 and also a VLAN 300 (with no reference on the configuration you posted), I presume no IPv4 routing enabled (but I'm not a Cisco expert)...I say that because specifying the default gateway (sitting on the VLAN 1) generally means a simple Layer 2 approach where the routing happens elsewhere (at Core).

On Aruba side the voice dedicated VLAN should be set as "voice" but without having a sanitized configurations of both peers it's difficult to say if there are errors/mis-configurations.

Hi Davide

The Branch Switch have this VLAN´s

OK, so port 24 (used for the uplink to one of your three stacked Aruba 2930F) is:

Status and Counters - VLAN Information - for ports 24
 
VLAN ID Name                 | Status     Voice Jumbo Mode
------- -------------------- + ---------- ----- ----- --------
1       DEFAULT_VLAN         | Port-based No    No    Untagged
130     LKH                  | Port-based Yes   No    Tagged

And VLAN 130 "LKH" is set to be a voice VLAN.

Ports 14 and 18 are untagged in VLAN 130...but, AFAIK, ports where VoIP Terminals are connected should be configured to be tagged members of voice VLAN (have you tried?).

If I were you I would try (example for port 18 on the Branch):

vlan 130
tagged 18
exit
vlan 1
untagged 18
exit

then, as usual, check with show vlan port 18 detail command.

So the next question is: is the above matching the VLAN settings on the corresponding peer port? If so you're OK from the VLAN tagging standpoint because core and branch are permitting the VLAN 1 to flow untagged and VLAN 130 to flow tagged.

The only other layer to check is the Layer 3 (IP) to see if packets are routed correctly.