Posts tagged Cisco

Cisco Router as a DHCP Server for Avaya IP Phones

4
February 22, 2011
by Alex in

Here’s a sample configuration detailing how to configure a Cisco router as a DHCP server for Avaya (formerly Nortel) IP phones including the Avaya/Nortel specific DHCP options 128 and 191. I thought I would share this information with the Nortel/Avaya users in case they are utilizing (or wish to utilize) the DHCP server functionality built-in to the Cisco IOS platform. The key is to configure the Cisco router to reply with the correct DHCP vendor options so the IP phone will boot properly.

!
no aaa new-model
!
ip routing
ip subnet-zero
no ip source-route
no ip finger
no ip domain-lookup
ip cef
!
!
!### 1) SET UP EXCLUSIONS FOR STATIC IP DEVICES ###
!### START ADDRESS (SPACE) END ADDRESS ###
!
!### VLAN2 DATA EXCLUSIONS ###
ip dhcp excluded-address 10.10.10.1 10.10.10.30
ip dhcp excluded-address 10.10.10.200 10.10.10.254
!
!### VLAN701 VOICE EXCLUSIONS ###
ip dhcp excluded-address 192.168.1.1 192.168.1.30
ip dhcp excluded-address 192.168.1.200 192.168.1.254
!
!### VLAN702 VOICE EXCLUSIONS ###
ip dhcp excluded-address 192.168.2.1 192.168.2.30
ip dhcp excluded-address 192.168.2.200 192.168.2.254
!
!
!### 2) SET UP DHCP FOR FOR DATA VLAN/SUBNET ###
!
ip dhcp pool Nortel_Data_VLAN2
network 10.10.10.0 255.255.255.0
default-router 10.10.10.1
option 128 ascii Nortel-i2004-A,192.168.1.21:4100,1,10.
option 191 ascii VLAN-A:701+702.
!
!
!### 3) SET UP DHCP FOR FOR VOIP-PHONES VLAN/SUBNET ###
!
!
ip dhcp pool Nortel_Voice_VLAN701
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
option 128 ascii Nortel-i2004-A,192.168.1.21:4100,1,10.
option 191 ascii VLAN-A:701+702.
!
!
ip dhcp pool Nortel_Voice_VLAN702
network 192.168.2.0 255.255.255.0
default-router 192.168.2.1
option 128 ascii Nortel-i2004-A,192.168.1.21:4100,1,10.
option 191 ascii VLAN-A:701+702.
!
!
!
!### 4) SET UP INTERFACES ###
!
!
interface fast 0/0
description ### VLAN TRUNK & ROUTE LINK TO LAN SWITCH ###
no ip address
speed 100
full-duplex
no shutdown
!
!
int fast 0/0.2
desc ### VLAN 2 DATA SUBNET ###
ip add 10.10.10.1 255.255.255.0
no ip red
no ip dir
no shut
!
int fast 0/0.701
desc ### VLAN 701 VOIP PHONES SUBNET ###
ip add 192.168.1.1 255.255.255.0
no ip red
no ip dir
no shut
!
!
int fast 0/0.702
desc ### VLAN 702 VOIP PHONES SUBNET ###
ip add 192.168.2.1 255.255.255.0
no ip dir
no ip red
no shut
!
ip route 0.0.0.0 0.0.0.0 10.10.10.254 name DEFAULT-ROUTE
!

Cheers!
Alex

-Editor, Thanks to Alex for writing this post and allowing me to re-post it here. -Michael

Cisco Nexus Switch Backups with Perl SNMP

24
September 1, 2010
by Michael McNamara in

I’ve spent some time over the past few days trying to get our home grown Perl script designed to backup all our network switches to work with the Cisco Nexus 7010 and 5010 switches.

With previous Cisco switches such as the 6509, 3750, 2960, etc we know that the following commands (when sent via a Perl script using the Net-SNMP Perl module) would instruct the switch to copy it’s running-config to a TFTP server.

snmpset -v1 -c$COMMUNITY $HOST ccCopyProtocol.$RANDOM i 1
snmpset -v1 -c$COMMUNITY $HOST ccCopySourceFileType.$RANDOM i 4
snmpset -v1 -c$COMMUNITY $HOST ccCopyDestFileType.$RANDOM i 1
snmpset -v1 -c$COMMUNITY $HOST ccCopyServerAddress.$RANDOM a "10.1.1.50"
snmpset -v1 -c$COMMUNITY $HOST ccCopyFileName.$RANDOM s "sw-train-acme.cfg"
snmpset -v1 -c$COMMUNITY $HOST ccCopyEntryRowStatus.$RANDOM i 1
sleep 5
snmpget -v1 -c$COMMUNITY $HOST ccCopyState.$RANDOM
#if not successful sleep 3 and re-check ccCopyState else continue and destroy table entry
snmpset -v1 -c$COMMUNITY $HOST ccCopyEntryRowStatus.$RANDOM i 6

I know that the both the Cisco Nexus 7010 and 5010 both balk at the SNMP OIDS/MIBS used above. So I’m searching for a set of equivalent SNMP OIDS/MIBS as those in CISCO-CONFIG-COPY-MIB for NX-OS. I’m not sure that such a OID/MIB even exists for NX-OS but it doesn’t hurt to search and ask.

I’m curious if anyone else has come across this issue? I know that there is an XML interface available but I would prefer to keep using the PERL/SNMP script that I’ve already developed. In the interim I’ll probably write an Expect script (or add some Expect code to my existing Perl script) to remotely connect to the switches and issue the appropriate copy commands.

Cheers!

Updated: Monday June 27, 2011

I’ve finally found the issue and now I’m able to backup the Cisco Nexus switches as expected.

Avaya and Cisco Interoperability Technical Configuration Guide

6
June 20, 2010
by Michael McNamara in ,

Avaya has release an updated technical configuration guide geared towards the interoperability between Cisco and Avaya equipment.The document covers a lot of information including EtherChannel to MLT interoperability, Spanning Tree interoperability, Nortel IP phones connecting to Cisco switches and Cisco IP phones connecting to Nortel switches.

It’s definitely well worth the time to review.

Cheers!

Go to Top