11-22-2024 04:50 AM
Hi all,
Scenario:
Problem:
After changing the Catalyst 2960 switches with the MS130-48Ps, I started having problems with the desk phones. All but two phones in the offices are either showing 'Phone not registered' or Network not available'. I have included the the mac address of the 3945 to the allowed DHCP list on the DHCP Servers list on the Meraki.
On the Meraki dashboard, all the phones show that they are connected with the right IP Address. However, from the 3945 ISR, I do not see the list of the devices when I use show ip dhcp binding.
Any help is welcome to solve the issue I face of the devices showing 'Phone not registered' or Network not available'.
11-22-2024 07:32 AM
Am I understanding correctly that the network was using 2960 switches and was working correctly? And that you replaced these switches with MS130-48P and now most phones are not working? It sure sounds like there is some issue on MS130-48P. Can you verify their configuration?
Are there any log messages on the 3850 or on the 3945 that might relate to this issue? Or messages on MS130-48P?
Are you sure that the 3850 and MS130-48P agree on vlan assignment, etc?
11-23-2024 10:27 AM
Yes the network was ok when it had the 2960 switches. ANd after changing them to the MEraki MS130-48P switches the phones are all off bar two.
The Management VLAN on the Meraki is VLAN 10. This was changed from VLAN 1 since when its on VLAN 1 the Meraki uses dynamic DHCP even though it is configured to use static IP Address.
Below is the config on the 3850.
BACKBONE-SW#sh config
version 15.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
service compress-config
!
hostname BACKBONE-SW
!
boot-start-marker
boot-end-marker
!
!
vrf definition Mgmt-vrf
!
address-family ipv4
exit-address-family
!
address-family ipv6
exit-address-family
!
enable secret 5
!
username admin privilege 15 password 7
aaa new-model
!
!
aaa session-id common
switch 1 provision ws-c3850-24t
!
!
ip name-server 172.16.0.2
ip name-server 172.16.0.3
!
!
qos queue-softmax-multiplier 100
vtp mode transparent
!
!
spanning-tree mode mst
spanning-tree extend system-id
!
spanning-tree mst configuration
name OfficeHQ
revision 1
instance 1 vlan 1-30
!
spanning-tree mst 0-2 priority 16384
hw-switch switch 1 logging onboard message level 3
!
redundancy
mode sso
!
!
vlan 5
name VOICEVLAN
!
vlan 10
name DATAVLAN
!
vlan 15
!
!
class-map match-any non-client-nrt-class
!
!
interface GigabitEthernet0/0
vrf forwarding Mgmt-vrf
no ip address
negotiation auto
!
interface GigabitEthernet1/0/1
description "SERVER ACCESS PORT"
switchport access vlan 10
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/0/2
description "SERVER ACCESS PORT"
switchport access vlan 10
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/0/3
description "SERVER ACCESS PORT"
switchport access vlan 10
switchport mode access
spanning-tree portfast
!
!
interface GigabitEthernet1/0/20
description "UPLINK TO ACCESS SW"
switchport mode trunk
!
interface GigabitEthernet1/0/21
description "UPLINK TO ACCESS SW"
switchport mode trunk
!
interface GigabitEthernet1/0/22
description "UPLINK TO ACCESS SW"
switchport mode trunk
!
interface GigabitEthernet1/0/23
description "UPLINK TO ACCESS SW"
switchport mode trunk
!
interface GigabitEthernet1/0/24
description "UPLINK TO ACCESS SW"
switchport mode trunk
!
!
interface Vlan1
ip address dhcp
!
interface Vlan10
ip address 172.16.0.10 255.255.254.0
!
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
!
!
!
line con 0
password 7
stopbits 1
line aux 0
stopbits 1
line vty 0 4
password 7
transport input telnet ssh
line vty 5 15
transport input telnet ssh
!
ntp server 172.16.0.1
wsma agent exec
profile httplistener
profile httpslistener
!
wsma agent config
profile httplistener
profile httpslistener
!
wsma agent filesys
profile httplistener
profile httpslistener
!
wsma agent notify
profile httplistener
profile httpslistener
!
!
wsma profile listener httplistener
transport http
!
wsma profile listener httpslistener
transport https
!
ap group default-group
end
11-22-2024 02:44 PM
Hello
do your ports require poe? and if so is the new meraki capable
11-23-2024 10:32 AM
The Meraki MS130-48P switches are PoE capable and my APs are connected to them using PoE and so are the deskphones.
11-23-2024 07:58 PM
on the MS130 make sure the STP root is correct, if not fix it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide