cisco_configuration_ttl
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cisco_configuration_ttl [2016/09/23 13:21] – walkeradmin | cisco_configuration_ttl [2016/09/23 13:45] (current) – walkeradmin | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ==== Cisco 3560 Configuration Guide for iSIS8000 Systems==== | ==== Cisco 3560 Configuration Guide for iSIS8000 Systems==== | ||
| \\ | \\ | ||
| - | Introduction | + | Introduction |
| \\ | \\ | ||
| \\ | \\ | ||
| Line 21: | Line 21: | ||
| ---- | ---- | ||
| + | ==== Switch Types ==== | ||
| + | \\ | ||
| + | Cisco switches can be used in nCompass Control to carry broadcast traffic over IP. nCompass can currently control specific Cisco switch models for device redundancy. The operation of the switch is controlled by SNMP. | ||
| + | \\ | ||
| + | \\ | ||
| + | nCompass can currently support the following switches for device control:- | ||
| + | * Cisco 3550/60 Series (3560 for iSIS8000) | ||
| + | * Cisco 4500 Series | ||
| + | \\ | ||
| + | There are currently two software versions available on the Cisco 3550/60. There is no difference in hardware between an SMI and EMI switch. The two software versions are Enhanced Multilayer Image (EMI) and Standard Multilayer Image (SMI). EMI provides more features such as enhanced security, Quality of Service (QoS), OSPF Routing and Protocol Independent Multicast (PIM). IP streamer and encoder systems can use an SMI switch unless specified otherwise. | ||
| + | \\ | ||
| + | \\ | ||
| + | Cisco 2950 switches are used for Management network redundancy only. | ||
| + | ---- | ||
| + | ==== Initial Switch Configuration (3560) ==== | ||
| + | \\ | ||
| + | The following is intended as a guide to configure Cisco catalyst switches to work with nCompass. If a GigE switch (i.e. Cisco 3560G) is being used the replace all instances of fa0/? With gi0/? | ||
| + | \\ | ||
| + | * <R> denotes the Return key. | ||
| + | * Switch> Prompt is the base menu. | ||
| + | * Switch# Prompt is the enable menu (type ‘en’ and password (if one is set) to get to this point from initial prompt). Type end to return to Switch> | ||
| + | * Switch(Config) Prompt is the configure mode. Type ‘conf t’ from enable menu, type ‘end’ to exit to enable menu. | ||
| + | * Switch(Config-IF) Prompt is a typical sub configuration menu. Type int fa0/1 to get to this point type ‘exit’ to return to Switch (Config) or ‘end’ to return to enable menu (Switch#) | ||
| + | * In the enable menu (Switch#) type ‘sh ru’ to view the existing configuration. | ||
| + | * The TAB key can be used to complete words i.e. sw <TAB> will complete to switchport etc. | ||
| + | * The up or down curser can be used to recall earlier commands for that menu. (Hyperterminal may prevent this if not set correctly. This feature will always work with Telnet). | ||
| + | * To cancel a command type ‘no [command]’ <R>. | ||
| + | |||
| + | ---- | ||
| + | ==== TS Data Switch setup ==== | ||
| + | The following gives a brief set of instructions for setting up a Cisco 3560 as a TS Data switch. | ||
| + | Clearing the Current Configuration | ||
| + | \\ | ||
| + | \\ | ||
| + | This is recommended if the switch has been previously used. | ||
| + | \\ | ||
| + | \\ | ||
| + | - Connect to switch using console port on rear of unit. | ||
| + | - Open a HyperTerminal session for 9600 8N1N. | ||
| + | - Type ‘en’ <R> for enable. | ||
| + | - Enter the enable password (default ‘cisco’) if applicable then <R>. | ||
| + | - Type ‘erase startup’ <R> | ||
| + | - You will be given a warning about erasing the nvram press <R> to confirm | ||
| + | - Press <R> again. | ||
| + | - Type ‘reload’ to reboot switch. | ||
| + | - You will be asked to “Proceed with reload” press <R> to confirm | ||
| + | - 1The switch should now start in the default configuration this will take a few minutes and will involve the reloading of flash. | ||
| + | - After reload is complete you will be asked to press <R> to begin, once this is done you will be asked to type “yes” or “no” to enter the initial configuration dialog, type “no” <R> | ||
| + | - This will then put you at the switch> prompt | ||
| + | - Type “en” <R> this will put you at the switch# prompt where commands can be entered | ||
| + | - Type “show ru” this will show the current config, which should look like the following text (comments are in capitals and brackets) | ||
| + | \\ | ||
| + | \\ | ||
| + | < | ||
| + | Current configuration : 1312 bytes | ||
| + | ! | ||
| + | version 12.2 | ||
| + | no service pad | ||
| + | service timestamps debug uptime | ||
| + | service timestamps log uptime | ||
| + | no service password-encryption | ||
| + | ! | ||
| + | hostname Switch (DEFAULT HOSTNAME) | ||
| + | ! | ||
| + | ! | ||
| + | no aaa new-model | ||
| + | ip subnet-zero | ||
| + | ! | ||
| + | ! | ||
| + | no file verify auto | ||
| + | spanning-tree mode pvst | ||
| + | spanning-tree extend system-id | ||
| + | ! | ||
| + | vlan internal allocation policy ascending | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | ! | ||
| + | interface Vlan1 | ||
| + | no ip address | ||
| + | ! | ||
| + | ip classless | ||
| + | ip http server | ||
| + | ! | ||
| + | ! | ||
| + | control-plane | ||
| + | ! | ||
| + | ! | ||
| + | line con 0 | ||
| + | line vty 5 15 | ||
| + | ! | ||
| + | end | ||
| + | Switch# | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Typing in the TS Data Switch Configuration ==== | ||
| + | \\ | ||
| + | |||
| + | - At the “switch# | ||
| + | - At the “switch(config)# | ||
| + | \\ | ||
| + | < | ||
| + | interface GigabitEthernet0/ | ||
| + | switchport access vlan 10 | ||
| + | switchport mode access | ||
| + | spanning-tree portfast | ||
| + | no cdp enable | ||
| + | </ | ||
| + | <color red> | ||
| + | \\ | ||
| + | \\ | ||
| + | \\ | ||
| + | <color darkblue> | ||
| + | \\ | ||
| + | \\ | ||
| + | interface range GigabitEthernet 0/1-12 | ||
| + | \\ | ||
| + | \\ | ||
| + | < | ||
| + | ! | ||
| + | interface GigabitEthernet0/ | ||
| + | no switchport | ||
| + | ip address 10.1.4.245 255.255.255.0 | ||
| + | ! | ||
| + | interface Vlan1 | ||
| + | no ip address | ||
| + | shutdown | ||
| + | ! | ||
| + | interface Vlan10 | ||
| + | description Multicast Source | ||
| + | ! | ||
| + | ! | ||
| + | ip classless | ||
| + | ! | ||
| + | ip route 0.0.0.0 0.0.0.0 10.1.4.254 | ||
| + | OPTIONAL GATEWAY ADDRESS FOR VLAN 10 | ||
| + | ! | ||
| + | ! | ||
| + | snmp-server community public RO | ||
| + | snmp-server community private RW | ||
| + | ! | ||
| + | control-plane | ||
| + | ! | ||
| + | ! | ||
| + | line con 0 | ||
| + | line vty 0 4 | ||
| + | password cisco | ||
| + | line vty 5 15 | ||
| + | password cisco | ||
| + | ! | ||
| + | end | ||
| + | </ | ||
| + | \\ | ||
| + | After typing “end” above you will be returned to the “switch# | ||
| + | The final thing to do is to enable IGMP snooping on the switch | ||
| + | \\ | ||
| + | \\ | ||
| + | IGMP snooping can be enabled on a switch to prevent a particular port being exposed to all multicasts on a network. For example suppose there where 100 5MBits multicast streams on the back plane of the switch and you connect a device with only a 10/100 baseT port then it will be unable to tune into a multicast since it will just see a mass of packets (broadcast storm). In order to prevent this the switch can listen into multicast joins and hosts and only allow specific multicast traffic to a port if a receiver attached requests it. | ||
| + | \\ | ||
| + | \\ | ||
| + | IGMP snooping is normally configured as a global command but can be assigned to specific interfaces. | ||
| + | To configure IGMP on for the entire switch. | ||
| + | \\ | ||
| + | - Enter the enable menu by typing ‘en’ <R> to get to the “switch# | ||
| + | - Type ‘conf t’ <R> to enter configure mode and enter a password if needed | ||
| + | - Type ‘ip igmp snooping’ <R> This enables IGMP snooping on all ports | ||
| + | \\ | ||
| + | \\ | ||
cisco_configuration_ttl.1474636896.txt.gz · Last modified: (external edit)
