ISIS Switch Reference Guide V 1.

Avid ISIS Ethernet Switches

Reference Guide

V 1.2 Page 1 6/25/2007

 ISIS Switch Reference Guide V 1.2

Table of Contents

I. Introduction
II. Avid ISIS Default Configuration for Avid Production Network Switch
A. Access for Configuring Switches
1. Accessing the Switch Through Telnet
2. Accessing the Switch Through Hyperterminal
B. TFTP Application
C. Default Passwords
III. Foundry X424
A. Loading a Configuration
B. Upgrading Firmware and Boot ROM
C. Changing the IP Address associated with a VLAN
D. Changing the IP Address associated with the Corporate Uplink
E. Changing Buffer Pool to support Zone 3 clients
F. Removing/Adding ports associated to a VLAN
G. Enabling or Disabling IP Routing
H. Creating Trunked ports (link aggregation)
I. Setting up IP-Helper Addresses for DHCP

IV. Cisco 4948

A. Loading a Configuration
B. Upgrading IOS
C. Changing the IP Address associated with a VLAN
D. Changing the IP Address associated with the Corporate Uplink
E. Removing/Adding ports associated to a VLAN
F. Enabling or Disabling IP Routing
G. Creating an EtherChannel (link aggregation)
H. Setting up IP-Helper Addresses for DHCP

V. SMC 8724ML3
A. Loading a Configuration
B. Upgrading Firmware and Boot Code
C. Changing the IP Address associated with a VLAN
D. Changing the IP Address associated with the Corporate Uplink
E. Removing/Adding ports associated to a VLAN
F. Enabling or Disabling IP Routing
G. Setting up IP-Helper Addresses for DHCP
VI. Appendix
A. Sample Configurations and Associated Files by switch vendor
1. Configuration A: Single L3 APN Switch Supports Zones 1 & 2
and limited Zone 3
2. Configuration B: Single L3 APN switch for support of Zone 1 and
2 plus Zone 3 support via GigE link aggregation
3. Configuration C: Single L2 APN Switch dual 10 Gb connections
4. Configuration D: Single L2 APN Switch single 10 Gb
connections
5. Configuration E: Dual L3 switches with Router Redundancy
B. Table of Command Similarities/Differences Between Vendors

V 1.2 Page 2 6/25/2007

 ISIS Switch Reference Guide V 1.2

I. Introduction

The purpose of this document is to provide ISIS Administrators with a single reference regarding
the implementation, configuration and troubleshooting of all Avid ISIS qualified Ethernet switches.
The switches covered in this documented are outlined in Table 1. A switch that is listed has been
fully qualified by Avid in the configurations presented in this document.

Table 1: Supported Switch Revisions

Manufacturer Model Firmware/IOS Description

Cisco 4948 10GE Rommon: 48 GigE (RJ-45),
12.2(31r)SGA 2-10 Gb (X2/SC)
recommended

IOS: 12.2 (25)

EWA9 recommended
Foundry X424 Firmware Version 24 GigE (RJ-45),
03.1.00dT3e3 4 GigE (SFP),
BootROM Version 2-10 Gb (XFP/LC)
03.1.00dTe6
or
Firmware Version
02.3.01T3e3
BootROM Version
02.3.01Te6
or
Firmware Version
02.5.00aT3e3*
BootROM Version
02.5.00Te6*
SMC 8724ML3 Loader Version: 24 GigE (RJ-45)
3.1.0.0 4 GigE (SFP)
Boot ROM Version:
3.1.0.0
Operation Code
Version: 3.1.1.56

*RoHS version requires this level of code.

II. Avid ISIS Default Configuration for Avid Production Network Switch

Each vendor’s switch, when purchased from Avid, comes configured with an Avid Default
configuration outlined in Configuration A. If the default configuration is not compatible with your
system use one of the configurations provided to create a compatible file. The configuration has
to be applied using the same procedure outlined later, by vendor, in this document. The Avid
Default Configuration has a provision for one port to connect to the House Network for Zone 3
support. That port is 24 for Foundry and SMC, and 48 for Cisco. Table 3 shows the default port
allocations by zone.

V 1.2 Page 3 6/25/2007

 ISIS Switch Reference Guide V 1.2

Table 2: Switch Matrix

Model RU GigE Ports 10 Gb Ports Mgmt. Ports Comments

Cisco 4948 1 48 RJ-45 2 X2 (SC) 2 RJ-45 Avid Supports both SR
(One Serial, One Ethernet) (850 nm) and LR (1310
nm) X2s in 10 Gb ports.

Ethernet Mgmt. Port used

in Rommon mode only.
Foundry X424 2XG 2 24 RJ-45 2 XFP (LC) 1 DB-9 serial Avid Supports both SR
4 SFP (850 nm) and LR (1310
nm) XFPs in 10 Gb ports.

Optical GigE SFP Ports 1F

– 4F can be used in place
of RJ-45 Ports 1 – 4.
SMC 8724ML3 1 24 RJ-45 None Supported 1 DB-9 serial Optical GigE SFP Ports 21
4 SFP – 24 can be used in place
of RJ-45 Ports 21 – 24.

Table 3: Avid Factory Default port allocations

Model VLAN 10 VLAN 20 VLAN 40 House Network

Zone 3 Test Port Uplink
Cisco 4948 Ports 1-24 Ports 25-46 47 Port 48
Foundry X424 Ports 1-12 Ports 13-22 23 Port 24
SMC Ports 1-12 Ports 13-23 N/A Port 24
8724ML3

A. Access for Configuring Switches

There are two methods for accessing the switches. The following sections describe the
two processes.

1. Accessing the Switch Through Telnet

You can access the switch console using remote systems on the network. Telnet
is a common way to remotely access the switch using a network client system.
You need to know the IP address of the target switch channel.

To access your Switch using Telnet:

1. Make sure your switch is powered on.
2. Connect the Ethernet port on your switch to your network.
3. From a network client system, click Start > Run.
4. Type Telnet < switch IP> and press Enter.

2. Accessing the Switch Through HyperTerminal

Each vendor’s switch provided by Avid is accompanied with the proper serial
cable. You can access the switch configuration settings using HyperTerminal
through the serial connection. You need to set the following serial protocol:
Baud Rate — 9600
Data Bits — 8
Parity — None
Stop Bits — 1
Flow Control — None

V 1.2 Page 4 6/25/2007

 ISIS Switch Reference Guide V 1.2

To access your switch using HyperTerminal:

Make sure your switch is powered on.
Connect the serial COM port on your computer to the serial connector on the
switch. The correct serial cable is supplied with each vendor’s switch. For Cisco
4948, the top RJ-45 port (next to 10 Gb port 49) marked “Con” is the serial
connection.
From a Windows system, click Start > Programs > Accessories >
Communications > HyperTerminal.
Type a name for the connection, select the COM port, and configure the
connection using the serial protocol previously listed.

B. TFTP
In order to copy firmware and configuration files from the Host to the switch you need a
TFTP application. You can find several on the Internet. The most common application
used at Avid is called TFTPD32.exe. You can download a copy of this program at the
following URL: http://tftpd32.jounin.net/.
When configuring the TFTP application make sure that the IP of the Server Interface is
on the same subnet as the switch with which you are attempting to communicate. Also,
make sure that the files you are trying to transfer are in the directory designated as the
root for the TFTP application. This is sometimes referred to as the Base Directory.
C. Default Passwords

It should also be noted that the following default passwords exist in order for one to
access enable mode on the switches. Table 4 outlines the passwords for each vendor.

Table 4: Default Enable Passwords

Manufacturer Model Password Comments

Cisco 4948 Not Set by Default In order to get into enable mode via a
Telnet session you must create an
enable password via the serial
connection. This can be done in
Global Configure Mode by using the
“Enable Secret” command.
Foundry X424 Not Set by Default Press enter to access enable mode.
SMC 8724ML3 User: admin
Password: admin

III. Foundry X424 2XG

A. Loading the Avid Default Configuration

Note: Refer to Section IIA and IIB for setup related to this procedure

This procedure assumes that you are using the Avid default IP for VLAN 10 (Ports 1 – 12
for Foundry or SMC, or 1 – 24 for Cisco) on the switch with a Interface IP of
192.168.10.2. If not, change the IPs written in the procedure to match your IP scheme. If
you received a Foundry switch that has not been configured with the Avid file then it is
likely that the IP address for VLAN 1 is 209.157.22.154.

V 1.2 Page 5 6/25/2007

 ISIS Switch Reference Guide V 1.2

1. Connect the Host PC to VLAN 10 of the switch (See Table 2)

2. Establish a connection to the switch’s CLI (See Section IIA)
3. Launch the TFTP application. Make sure you choose the proper NIC for
the Server Interface and that the file you are uploading is in the Base
Directory.
4. SwitchHostName >en
5. SwitchHostName #: copy tftp startup-config [tftp server IP] [config file
name]
6. Click on the TFTP window that you placed into the background, and check
to see if any errors occurred during the copy.
7. SwitchHostName#reload
8. Choose “y” to confirm the reload
9. Choose “y” to reload without saving changes to the running configuration.
If you choose “no” you will overwrite the startup configuration you just
loaded.
Note: If you connected to the CLI via telnet you may have to change the IP of
your Host’s interface to re-establish a telnet connection to the switch.

B. Upgrading Firmware

This upgrade should only apply to a small number of switches that were shipped to
customers prior to the official 1.0 release of ISIS. However, it is included in this
document for reference because much of the procedure applies to normal upgrade
process. The unique part about this upgrade procedure is that because it involves
moving up three revisions, from 2.0 to 2.3, the procedure requires an interim 2.2
upgrade.

This procedure explains how to load Firmware and Boot ROM for the Foundry X424
(X424) switch. Because this update involves moving from the 2.0 to the 2.3 code an
interim 2.2 update is necessary. This procedure assumes that you are using the Avid
default IP for VLAN 10 (Ports 1 – 12) on the switch of 192.168.10.2. If not, change
the IPs written in the procedure to match your IP scheme. If you received a switch
that has not been configured with the Avid file then it is likely that the IP address for
VLAN 1 is 209.157.22.154.

Note: If you are using the System Director (not a laptop) to perform the operation, be
aware that you need to write down the original NIC card address. You will need to
change it back after you complete the loading of the configuration file.

Pre-requisites for loading the Firmware and Boot ROM

TFTP loaded on the system you are using (can get from net)
Copy of the Firmware and Boot ROM files for both the 2.2 and 2.3 releases to the
root of the C drive (or to the path at which your TFTP program is defaulting).
Those files are the following:
o fexz02000B1.bin
o FEXR02200b74.bin
o fexz02301.bin
o SXR02301.bin

To load the Firmware and Boot ROM from a system:

1. SwitchHostName#copy tftp fl 192.168.10.1 fexz02000b1.bin bootrom

Note: See flash memory write, when finished will say Flash Done
2. SwitchHostName#copy tftp fl 192.168.10.1 fexr02200b74.bin pri

V 1.2 Page 6 6/25/2007

 ISIS Switch Reference Guide V 1.2

3. SwitchHostName#copy tftp fl 192.168.10.1 fexr02200b74.bin sec

4. SwitchHostName#b s f p (this will cause you to lose connection with the
telnet session. Wait 1 minute for the switch to reboot)
5. Type: telnet 192.168.10.2
6. SwitchHostName#en
7. SwitchHostName#copy tftp fl 192.168.10.1 fexz02301.bin bootrom
8. SwitchHostName#dm skip
9. SwitchHostName#copy tftp fl 192.168.10.1 sxr02301.bin pri
10. SwitchHostName#copy tftp fl 192.168.10.1 sxr02301.bin sec
11. SwitchHostName#b s f p (this will cause you to lose connection with the
telnet session. Wait 1 minute for the switch to reboot)
12. Type: telnet 192.168.10.2
13. SwitchHostName#en, Press Enter.
14. SwitchHostName#show flash

You should now see the following:

Compressed Pri Code size = 3276169, Version 02.3.01T3e3 (sxr02301.bin)

Compressed Sec Code size = 3276169, Version 02.3.01T3e3 (sxr02301.bin)
Compressed BootROM Code size = 381202, Version 02.3.01Te6
!
Note: If you used the System Director (not a laptop) to perform the above operation,
you need to change the address of the NIC board (or onboard NIC) address back to
the proper address.

C. Changing the IP Address associated with a VLAN

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName#(config)#int ve ww (where ww equals 10 for the router-
interface on VLAN 10, or 20 for the router-interface on VLAN 20)
4. SwitchHostName(config-vif-10)#no ip address 192.168.Xx.2 255.255.255.0
(Where XX is 10 or 20)
5. SwitchHostName(config-vif-10)#ip address xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy
(Where XX is 10 or 20) (where x's equals ip address and y's equals subnet
mask)
6. SwitchHostName(config-vif-10)#exit
7. SwitchHostName#(config)#exit
8. SwitchHostName#write mem
9. SwitchHostName#exit

D. Changing the IP Address associated with the Corporate Uplink

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)#int ethe 24
4. SwitchHostName(config-if-e1000-24)#no ip address 10.10.10.10
255.255.255.0
5. SwitchHostName(config-if-e1000-24)#ip address xxx.xxx.xxx.xxx
yyy.yyy.yyy.yyy
(where x's equals ip address and y's equals subnet mask)
6. SwitchHostName(config-if-e1000-24)#exit
7. SwitchHostName(config)#exit
8. SwitchHostName#write mem
9. SwitchHostName#exit

V 1.2 Page 7 6/25/2007

 ISIS Switch Reference Guide V 1.2

E. Changing Buffer Pool to support Zone 3 clients

With the Foundry switch only, if you need support for Zone 3 clients you must make
changes to the buffers on the ports that will connect to Zone 3. For example by default
the port 24 is designated to connect to the House Network. However, the default buffers
are not set up to support Video/Audio playback through that link. The following
procedure explains how to make that change.

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)#qd 24 4095
4. SwitchHostName(config)#qd 24 4095 7
5. SwitchHostName(config)#exit
6. SwitchHostName#wr mem
7. SwitchHostName#exit

F. Removing/Adding ports associated to a VLAN

In the Foundry switch you must remove a port from a given VLAN before you can add it
to another. The following procedure shows how to do both:

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)#vlan x (where x is the VLAN #)
4. SwitchHostName(config-vlan-x)#no untagged ethernet x to y
5. SwitchHostName(config-vlan-x)#vlan y (where y is the other VLAN #)
6. SwitchHostName(config-vlan-y)#untagged ethernet x to y
7. SwitchHostName(config-vlan-y)#exit
8. SwitchHostName(config)#exit
9. SwitchHostName#wr mem
10. SwitchHostName#exit

G. Enabling or Disabling IP Routing

Unlike the Cisco or SMC switches, there is no “ip routing” command in the Foundry
switch. If you do not want the switch to perform Layer 3 operations (i.e., routing between
subnets) then you must remove IP addresses associated to all but one router interface.
Once there is more than one subnet defined in the switch configuration the switch will
route between them.

Use the procedure outlined in section C to remove the IP address associated to a router
interface. You may also choose to disable a router interface. To do so do the following:

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)#int ve x (where x is the router #)
4. SwitchHostName(config-vif-x)#disable
5. SwitchHostName(config-vif-x)#exit
6. SwitchHostName(config)#exit
7. SwitchHostName#wr mem
8. SwitchHostName#exit

V 1.2 Page 8 6/25/2007

 ISIS Switch Reference Guide V 1.2

H. Creating Trunked ports (link aggregation)

With the Foundry switch you can trunk (aggregate) up to four ports. The default
configuration from Avid that supports trunking includes a trunk of ports 21 to 24. You can
create multiple four port trunks.

Keep in mind that depending on to what you are connecting the trunk you may have to
change the load balancing algorithm of the switch on the other end. For example, if you
are connecting to a Cisco EtherChannel you want to change the load balancing to
support source-destination IP address.

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)#trunk ethe x to y
4. SwitchHostName(config)#trunk deploy
5. SwitchHostName(config)#exit
6. SwitchHostName#wr mem
7. SwitchHostName#exit

I. Setting up IP-Helper Addresses for DHCP

If you want to use DHCP on the clients that are connected to the Avid Production switch
you will need to add an IP Helper Address to each VLAN. The IP Helper Address points
the hosts to the DHCP Server that is on the house network.
1. SwitchHostName#conf t
2. SwitchHostName(config)#int ve n (where n is the router-interface #)
3. SwitchHostName(config-vif-n)#ip helper-address 1 xxx.xxx.xxx.xxx (where
x's equals the ip address of the DHCP Server)
4. SwitchHostName(config-vif-n)#exit
5. SwitchHostName(config)#exit
6. SwitchHostName#wr mem
Note: Repeat this for each VLAN that requires it.

IV. Cisco 4948

A. Loading the Avid Default Configuration

Note: Refer to Section IIA and IIB for setup related to this procedure

This procedure assumes that you are using the Avid default IP for VLAN 10 on the switch
with a Router interface IP of 192.168.10.2. If not, change the IPs written in the
procedure to match your IP scheme. In the event that you have received a switch that
does not have the Avid Default Configuration loaded, then you will need to apply an IP
address to VLAN 1 of the switch so you can transfer the configuration file via TFTP.
Please follow the steps outlined in section IV. C. of this document to accomplish that.

1. Connect the Host PC to VLAN 10 of the switch (See Table 2)

2. Establish a connection to the switch’s CLI (See Section IIA)
3. Launch the TFTP application. Make sure you choose the proper NIC for
the Server Interface and that the file you are uploading is in the Base
Directory.
4. SwitchHostName>en (enter password if required)
5. SwitchHostName#: copy tftp startup-config
Address or name of remote host []? Insert IP of TFTP server
Source filename []? Insert Config File Name
Destination filename [startup-config]? Hit Return

V 1.2 Page 9 6/25/2007

 ISIS Switch Reference Guide V 1.2

6. Click on the TFTP window that you placed into the background, and check
to see if any errors occurred during the copy.
7. SwitchHostName#reload
8. Choose “y” to confirm the reload
9. Choose “y” to reload without saving changes to the running configuration.
If you choose “no” you will overwrite the startup configuration you just
loaded.
Note: If you connected to the CLI via telnet you may have to change the IP of
your Host’s interface to re-establish a telnet connection to the switch.

B. Upgrading IOS

Please note that this procedure differs slightly from that of the one documented by Cisco.
Cisco 4948 switches supplied by Avid are configured with a Configuration Register value
of 0x2101, which means the switch will boot from the first IOS that appears in bootflash.
Cisco instructs you to set the Configuration Register to 0x2102, which means the switch
will look for a boot string that points to the IOS from which to boot. In order to remain
consistent with what we ship we have chosen to document a procedure based on our
current shipping product.

1. Use the dir bootflash: command to ensure that there is sufficient space in
Flash memory to store the PROM upgrade image. In most cases there will
only be one file in bootflash, which leaves plenty of space for the new file. If
there is insufficient space, delete one or more images, and then issue the
squeeze bootflash: command to reclaim the space.

Example:
Switch#delete bootflash:cat4000-i9s-mz.122-25.EWA4.bin
Switch#squeeze bootflash:

2. Download the cat4000-ios-promupgrade-122_25r_EWA program into

Flash memory using the copy tftp command.

Example:
Switch# copy tftp: bootflash:
Address or name of remote host [172.20.58.78]?
Source filename [cat4000-i9s-mz.122-25.EWA8.bin]?
Destination filename [cat4000-i9s-mz.122-25.EWA8.bin]?

3. Use the config-register command to set the configuration register to

0x2101.

Example:
Switch# configure terminal
Switch(config)# config-register 0x2101
Switch(config)# exit
Switch# write
Building configuration...
Compressed configuration from 3723 to 1312 bytes [OK]
Switch#

V 1.2 Page 10 6/25/2007

 ISIS Switch Reference Guide V 1.2

4. Archive the previous IOS image in case you need to re-apply at a later time.

Example:

Switch#copy bootflash: tftp:

Source filename []? cat4000-i9s-mz.122-25.EWA4.bin
Address or name of remote host []? 172.20.98.3
Destination filename [cat4000-i9s-mz.122-25.EWA4.bin]?

5. Delete the old IOS image(s), and then issue the squeeze bootflash:
command to reclaim the space.

Example:
Switch#delete bootflash:cat4000-i9s-mz.122-25.EWA4.bin
Switch#squeeze bootflash:

6. Once the squeeze is complete (it will take a few minutes), enter the reload
command to reset the switch and load the software.

Example:

Switch# reload

Use the show version command to verify that the new Cisco IOS release
is operating on the switch.

C. Changing the IP Address associated with a VLAN

1. SwitchHostName>enable
2. SwitchHostName#conf t
3. SwitchHostName(config)#int vlan ww (where ww equals 10 for vlan10, or
20 for vlan20)
4. SwitchHostName(config-if)# ip address xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy
(where x's equals ip address and y's equals subnet mask)
5. SwitchHostName(config-if)#no shut
6. SwitchHostName(config-if)#exit
7. SwitchHostName(config)#exit
8. SwitchHostName#copy run start
9. SwitchHostName#exit

D. Changing the IP Address associated with the Corporate Uplink

1. SwitchHostName> en
2. SwitchHostName#conf t
3. SwitchHostName(config)#interface Gi 1/48
4. SwitchHostName(config-if)#no switchport
5. SwitchHostName(config-if)#ip address xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy
(where x's equals ip address and y's equals subnet mask)
6. SwitchHostName(config-if)#no shut
7. SwitchHostName(config-if)#end
8. SwitchHostName#copy run start
9. SwitchHostName#exit

V 1.2 Page 11 6/25/2007

 ISIS Switch Reference Guide V 1.2

E. Adding ports associated to a VLAN

For Range of Ports

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)# int range gigabitEthernet 1/x-y (where x and y
are starting and ending ports)
4. SwitchHostName(config-if-range)#switchport mode access
5. SwitchHostName(config-if-range)#switchport access vlan x (where x is the
vlan to which you want to assign)
6. SwitchHostName(config-if-range)#exit
7. SwitchHostName(config)#exit
8. SwitchHostName#copy run start

For Single Port

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)# int gigabitEthernet 1/x (where x is the port
number)
4. SwitchHostName(config-if-range)#switchport mode access
5. SwitchHostName(config-if)#switchport access vlan x (where x is the vlan to
which you want to assign)
6. SwitchHostName(config-if-range)#exit
7. SwitchHostName(config)#exit
8. SwitchHostName#copy run start

F. Enabling IP Routing

If the "No IP Routing" command does not show up in the show run output then IP Routing
is enabled. This would be located in the upper portion of the show run output. Here is a
simple example from a Cisco 4948 where IP Routing is Disabled:

!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service compress-config
!
hostname Switch
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
vtp mode transparent
ip subnet-zero
no ip routing

V 1.2 Page 12 6/25/2007

 ISIS Switch Reference Guide V 1.2

Do the following to enable IP routing:

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)#ip routing
4. SwitchHostName(config)#exit
5. SwitchHostName#copy run start

G. Creating an EtherChannel (link aggregation)

With the Cisco switch you can create EtherChannels (link aggregation) with up to eight
ports. The default configuration from Avid that supports and EtherChannel that includes
a ports 45 to 48. You can create multiple eight port EtherChannels.

Keep in mind that depending on to what you are connecting the EtherChannel you may
have to change the load balancing algorithm of the switch on the other end. For
example, if you are connecting to a Cisco EtherChannel you want to change the load
balancing to support source-destination IP address.

In this example a range of ports is assigned to a VLAN and an Ether Channel (Layer 2)
created.

Note: Use the same procedure for creating 10 Gb Etherchannel groups that connect to
ISIS.

1. SwitchHostName>en
2. SwitchHostName#conf t
3. SwitchHostName(config)#int port-channel x (where x is the port-channel #)
4. SwitchHostName(config-if)#switchport mode access
5. SwitchHostName(config-if)#switchport access vlan n (where n is the vlan
#)
6. SwitchHostName(config-if)#exit
7. SwitchHostName(config)#int range GigabitEthernet 1/a-b (where a and b
are a range of ports)
8. SwitchHostName(config-if-range)#channel-group x mode on (where x is
the port-channel #)
9. SwitchHostName(config-if-range)#exit
10. SwitchHostName(config)#port-channel load-balance src-dst-ip
11. SwitchHostName(config)#exit
12. SwitchHostName#copy run start
13. SwitchHostName#exit

H. Setting up IP-Helper Addresses for DHCP

If you want to use DHCP on the clients that are connected to the Avid Production switch
you will need to add an IP Helper Address to each VLAN. The IP Helper Address points
the hosts to the DHCP Server that is on the house network.

7. SwitchHostName#conf t
8. SwitchHostName(config)#int vlan n (where n is the vlan #)
9. SwitchHostName(config-if)#ip helper-address xxx.xxx.xxx.xxx (where x's
equals the ip address of the DHCP Server)
10. SwitchHostName(config-if)#exit
11. SwitchHostName(config)#exit
12. SwitchHostName#copy run start
Note: Repeat this for each VLAN that requires it.

V 1.2 Page 13 6/25/2007

 ISIS Switch Reference Guide V 1.2

V. SMC 8724 ML3

A. Loading a Configuration
Note: Refer to Section IIA and IIB for setup related to this procedure.

This procedure assumes that you are using the Avid default IP for VLAN 10 on the switch
with a Router interface IP of 192.168.10.2. If not, change the IPs written in the
procedure to match your IP scheme. In the event that you have received a switch that
does not have the Avid Default Configuration loaded, then you will need to apply an IP
address to VLAN 1 of the switch so you can transfer the configuration file via TFTP.
Please follow the steps outlined in section V. C. of this document to accomplish that.

1. Connect the Host PC to VLAN 10 of the switch (See Table 2)

2. Establish a connection to the switch’s CLI (See Section IIA)
3. Launch the TFTP application. Make sure you choose the proper NIC for
the Server Interface and that the file you are uploading is in the Base
Directory.
4. Log into the switch
5. SwitchHostName#copy tftp startup-config
6. Enter the IP Address of the TFTP Server Interface
7. Enter the name of the configuration file you would like to load
8. Click on the TFTP window that you placed into the background, and check
to see if any errors occurred during the copy.
9. SwitchHostName#reload
10. Choose “y” to confirm the reload
11. Once rebooted, log back into the switch to confirm the changes

Note: If you connected to the CLI via telnet you may have to change the IP of
your Host’s interface to re-establish a telnet connection to the switch.

B. Upgrading Firmware and Boot Code

(At this time no Firmware or Boot ROM upgrade is required. This procedure will be
documented when that is necessary.)

C. Changing the IP Address associated with a VLAN

1. SwitchHostName#configure
2. SwitchHostName(config)#int vlan ww (where ww equals 10 for vlan10, or
20 for vlan20)
3. SwitchHostName(config-if)#ip address xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy
(where x's equals ip address and y's equals subnet mask)
4. SwitchHostName(config-if)#exit
5. SwitchHostName(config)#exit
6. SwitchHostName#copy run start
7. SwitchHostName#exit

V 1.2 Page 14 6/25/2007

 ISIS Switch Reference Guide V 1.2

D. Changing the IP Address associated with the Corporate Uplink

1. SwitchHostName#configure
2. SwitchHostName(config)#interface ethernet 1/24
3. SwitchHostName(config-if)#ip address xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy
(where x's equals ip address and y's equals subnet mask)
4. SwitchHostName(config-if)#end
5. SwitchHostName#copy run start
6. SwitchHostName#exit

E. Removing/Adding ports associated to a VLAN

1. SwitchHostName#configure
2. SwitchHostName(config)# interface ethernet 1/x-y (where x and y is a
range of ports)
3. SwitchHostName(config-if)# switchport native vlan n (where n is the vlan #)
4. SwitchHostName(config-if)# switchport allowed vlan remove o (where o is
the VLAN from which the ports are being removed)
5. SwitchHostName(config-if)#switchport allowed vlan add n untagged (where
n is the vlan # you used in step 3)
6. SwitchHostName(config-if)#exit
7. SwitchHostName#copy run start
8. SwitchHostName#exit

F. Enabling or Disabling IP Routing

The SMC switch is similar to Cisco in that if the "no ip routing" command does not show
up in the show run output then IP Routing is enabled. However, on SMC the “no ip
routing” setting would be found near the bottom of the show run output (after the router
interface IP designations) rather than the top. If ip routing is disabled, do the following to
enable it:

1. SwitchHostName#configure
2. SwitchHostName(config)#ip routing
3. SwitchHostName(config)#exit
4. SwitchHostName#copy run start

G. Setting up IP-Helper Addresses for DHCP

If you want to use DHCP on the clients that are connected to the Avid Production switch
you will need to add an IP Helper Address to each VLAN. The IP Helper Address points
the hosts to the DHCP Server that is on the house network.

13. SwitchHostName#configure
14. SwitchHostName(config)#int vlan n (where n is the vlan #)
15. SwitchHostName(config-if)#ip dhcp relay server xxx.xxx.xxx.xxx (where x's
equals the ip address of the DHCP Server)
16. SwitchHostName(config-if)#exit
17. SwitchHostName(config)#exit
18. SwitchHostName#copy run start
Note: Repeat this for each VLAN that requires it.

V 1.2 Page 15 6/25/2007

 ISIS Switch Reference Guide V 1.2

VI. Appendix

A. Sample Configurations and Associated Files by switch vendor

The configuration files that correspond to each of the configurations outlined in the Appendix can
be found on the ISIS kit CD (version 1.1) in the following path:

DVD Drive Letter:\Drivers and Firmware\Avid Sample Switch Configs

They are also available on the Avid web site at the following URL:

http://www.avid.com/onlineSupport/supportcontent.asp?browse=&productID=172&contentID=929
2

Keep in mind that configurations A through E do not apply to every vendor. For example, there
are no configurations B through E for SMC.

1. Configuration A: Single L3 APN Switch Supports Zones 1 & 2 and limited Zone 3

This configuration consists of a single Layer 3 Avid Production Network switch. The
switch can be either a switch that supports Video and Audio playback (e.g., Foundry or
Cisco), or Command and Control only (e.g., SMC). In the case of the SMC, only Zone 1
Video/Audio clients are supported and the VLAN 10/20 connections to ISIS are via GigE.

It is important to note that if this configuration consists of a Foundry switch and Zone 3
clients are planned that buffer changes must be made to the port that is used for the
uplink to the House Network. Those changes are explained in section III. E. In the
example following those changes are incorporated on port 24.

V 1.2 Page 16 6/25/2007

 ISIS Switch Reference Guide V 1.2

Table 5: Configuration A Port allocations

Model VLAN 10 VLAN 20 VLAN 40 House Network

Zone 3 Test Port Uplink
Cisco 4948 Ports 1-24 Ports 25-46 47 Port 48
Foundry X424 Ports 1-12 Ports 13-22 23 Port 24
SMC Ports 1-12 Ports 13-23 N/A Port 24
8724ML3

Figure 1: Configuration A

V 1.2 Page 17 6/25/2007

 ISIS Switch Reference Guide V 1.2

2. Configuration B: Single L3 APN switch for support of Zone 1 and 2 plus Zone 3
support via GigE link aggregation.

Table 6: Configuration B Port allocations

Model VLAN 10 VLAN 20 VLAN 30 VLAN 40

House Network Zone 3 Test Port
Uplink (Link
Aggregation)
Cisco 4948 Ports 1-22 Ports 23-43 Ports 45 to 48 44
(Ether Channel)
Foundry X424 Ports 1-10 Ports 11-19 Ports 21 to 24 20
(Trunk)

Figure 2: Configuration B

V 1.2 Page 18 6/25/2007

 ISIS Switch Reference Guide V 1.2

3. Configuration C: Single L2 APN Switch dual 10 Gb connections Supports Zones

1, 2 only. No IP Routing

Table 7: Configuration C Port allocations

Model VLAN 10 VLAN 20

Cisco 4948 Ports 1-24 Ports 25-48
Foundry X424 Ports 1-12 Ports 13-24

Figure 3: Configuration C

V 1.2 Page 19 6/25/2007

 ISIS Switch Reference Guide V 1.2

4. Configuration D: Single L2 APN Switch single 10 Gb connections Supports

Zones 1, 2 only. No IP Routing

Table 8: Configuration D Port allocations

Model VLAN 10
Cisco 4948 Ports 1-48
Foundry X424 Ports 1-24

Figure 4: Configuration D

V 1.2 Page 20 6/25/2007

 ISIS Switch Reference Guide V 1.2

5. Configuration E: L3 switches with Router Redundancy (HSRP for Cisco and

VRRP for Foundry).

Table 9: Configuration E Port allocations

Model VLAN 10 VLAN 20 VLAN 30 VLAN 40 Notes

House Network Zone 3 Test Port
Uplink (Link
Aggregation)
Cisco 4948 Ports 1-22 Ports 23-43 Ports 45 to 48 (Ether 44 Two configs provided, one
for each switch. Switch 1
Channel)
Master on VLAN 10 and
Backup on VLAN 20.
Switch 2 Master on VLAN
20 and Backup on VLAN
10.
Foundry X424 Ports 1-10 Ports 11-19 Ports 21 to 24 20 Two configs provided, one
for each switch. Switch 1
(Trunk)
Master on VLAN 10 and
Backup on VLAN 20.
Switch 2 Master on VLAN
20 and Backup on VLAN
10.

V 1.2 Page 21 6/25/2007

 ISIS Switch Reference Guide V 1.2

Figure 5: Configuration E

V 1.2 Page 22 6/25/2007

 ISIS Switch Reference Guide V 1.2

B. Table of Command Similarities/Differences Between Vendors

Foundry Cisco SMC

Entering Enable Mode en en Logging in
automatically puts you
in this mode
Entering Global conf t conf t configure
Config Mode
Enabling IP Routing Automatic if more than ip routing ip routing
one router interface is
defined
Changing IP You must remove the old New IP address New IP address
addresses IP address first using the automatically replaces automatically replaces
“no ip address” old old
command

V 1.2 Page 23 6/25/2007