Let’s set the PVID for each port to the proper VLAN;
vlan port 1/1-47,2/1-47 pvid 10 vlan port 1/48,2/48 pvid 200
Let’s associate the management interface to a specific VLAN;
vlan mgmt 200
Let’s configure SNMP with the appropriate SNMP strings and trap host;
snmp-server authentication-trap disable snmp-server community rostring ro snmp-server community rwstring rw snmp-server host 10.11.11.11 rostring
Let’s configure local logging to overwrite older events and setup a SYSLOG destination;
logging volatile overwrite logging enable logging remote address 10.103.24.50 logging remote level informational logging remote enable
Let’s configure the timezone and SNTP with the appropriate Daylight Saving Time information;
clock source sntp clock summer-time recurring 2 Sunday March 02:00 1 Sunday November 02:00 60 clock time-zone EST -5 0 sntp server primary address 10.11.11.10 sntp server secondary address 10.11.11.11 sntp enable
Let’s setup the MultiLink Trunk (MLT) which will bond the 802.1Q trunk ports together. Since we are using an SMLT topology we need to disable Spanning Tree from running between the core and edge switches.
mlt 1 disable mlt 1 name "SMLT-8600" mlt 1 learning disable mlt 1 member 1/48,2/48 mlt 1 enable
Let’s give the stack an IP address through which we can manage it; (this IP needs to be in VLAN previous defined by vlan mgmt)
ip address stack 10.11.11.75 netmask 255.255.255.0 default-gateway 10.11.11.1
Let’s enable forced-stack mode and configure the stack monitor feature. In past software releases you had to configure a different IP address depending if the switch was in a stack or a standalone switch. If one switch failed the stack would become a standalone switch and the IP address configured as the “stack IP” would stop responding and the “switch IP” would start responding. The “stack forced-mode” forces the “stack IP” address to always respond whether there is a single switch or multiple switches in a stack.
stack forced-mode stack-monitor stack-size 2 stack-monitor trap-interval 300 stack-monitor enable
Let’s configure ADAC so we can deploy our IP phones. We’ll clear the MAC address table because we’ll be using LLDP to detect the presence of an IP phone but you could use the MAC feature to detect non-LLDP or even non-Avaya IP phones.
adac voice-vlan 11 adac op-mode tagged-frames adac uplink-port 1/48 no adac mac-range-table adac enable
Let’s configure the port type for the end-user ports and enable ADAC, LLDP, BPDU filtering, Spanning Tree and FastStart;
vlan port 1/1-47,2/1-47 tagging untagpvidOnly interface fastEthernet 1/1-47,2/1-47 vlan ports 1/1-47,2/1-47 filter-unregistered-frames disable lldp tx-tlv local-mgmt-addr port-desc sys-cap sys-desc sys-name lldp status txAndRx config-notification lldp tx-tlv med extendedPSE med-capabilities network-policy poe poe-priority medium spanning-tree learning fast spanning-tree bpdu-filtering timeout 12000 spanning-tree bpdu-filtering enable adac detection lldp no adac detection mac adac enable exit
We shutdown the remaining unused SFP ports as a standard in case we might need them in the future;
interface fastEthernet 1/47,2/47 shutdown exit